User Details
- User Since
- Oct 2 2015, 1:24 PM (416 w, 5 d)
Today
gstat -C (CSV mode)
Thu, Aug 31
Tue, Aug 29
Aug 8 2023
Jul 9 2023
Jul 3 2023
Jun 13 2023
Apr 27 2023
Mar 21 2023
Feb 26 2023
Feb 4 2023
Jan 10 2023
Dec 12 2022
Dec 10 2022
Dec 3 2022
Jul 21 2022
Dec 16 2021
Dec 12 2021
Nov 1 2021
Oct 24 2021
Oct 23 2021
Oct 19 2021
Oct 18 2021
Oct 17 2021
Sep 15 2021
Jul 1 2021
Jun 29 2021
Jun 3 2021
Jun 2 2021
Abandon it due to existing patch: D28892
I've found that I have reimplemented this patch by myself (due to lack of internet access):
https://reviews.freebsd.org/D30609
May 28 2021
May 5 2021
Apr 26 2021
Mar 11 2021
Jan 20 2020
Jan 14 2020
Thanks, Lutz!
Jan 13 2020
Sep 25 2019
Sep 11 2019
Sep 4 2019
Aug 25 2019
Thank you, @kevans! fixed.
Aug 22 2019
Fix regression found thanks to tests:
- "jail -r jailname" returned error: jail not found.
Add basic jail tests:
- create/stop/list/restart jails
- create/list nested jail
- execute commands prestart and prestop
Aug 20 2019
Fix SEGFAULT on uninitialized jails_byname.
Aug 19 2019
Jun 20 2019
May 27 2019
May 2 2019
Apr 29 2019
Mar 21 2019
Generally looks good. Please fix easy remarks.
Jan 24 2019
Dec 16 2018
I prefer to deprecate chips / sub-arch, but not removal. Honestly approach with "unimplementable" atomic_64_swap looks too aggressive.
I and @yamori813_yahoo.co.jp have boards with mips4k SoCs and to be honest such chips do their job well.
Another point: I saw plenty of emails with information that 8Mb is very slow. If it looks small for certain group of people, it doesn't mean that it's small in wide audience. I see that firmware with kernel, modules, 20Mb of uncompressed UFS/CD9660 filesystem is powerful to handle plenty of tasks: routing, monitoring of sensors, graphical output to LCD, keyboard/IR control and so on.
Nov 28 2018
Nov 26 2018
Nov 16 2018
Nov 13 2018
Nov 12 2018
Thank you for submission!
Phabricator highlights style(9) issues like spacing/tabs, so it's easy to fix it.
Nov 10 2018
Oct 8 2018
Oct 2 2018
Sep 8 2018
Aug 29 2018
Thank you for review, @mat !
Patch has been corrected according to comment. :) Hope it's OK now.