[Bug 197921] scheduler: Allow non-migratable threads to bind to their current CPU

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197921 Zhenlei Huang changed: What|Removed |Added CC||z...@freebsd.org --- Comment #3

[Bug 197921] scheduler: Allow non-migratable threads to bind to their current CPU

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197921 Mark Linimon changed: What|Removed |Added Flags|mfc-stable12?, | |mfc-stable11?

[Bug 272536] 'make buildworld -j 8' fails: pid 79018 (clang), jid 0, uid 0, was killed: a thread waiting too long to allocate a page

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272536 --- Comment #5 from Yuri Victorovich --- (In reply to Mark Millard from comment #4) > Being in a VirtualBox VM the /dev/ada0p2 may not indicate > much about the actual media involved. The physical medium is a traditional spinning HD

[Bug 272536] 'make buildworld -j 8' fails: pid 79018 (clang), jid 0, uid 0, was killed: a thread waiting too long to allocate a page

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272536 --- Comment #4 from Mark Millard --- (In reply to Yuri Victorovich from comment #2) Being in a VirtualBox VM the /dev/ada0p2 may not indicate much about the actual media involved. Microsd card and spinning rust media are more likely than

[Bug 272536] 'make buildworld -j 8' fails: pid 79018 (clang), jid 0, uid 0, was killed: a thread waiting too long to allocate a page

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272536 --- Comment #3 from Yuri Victorovich --- (In reply to Mark Millard from comment #1) > Do you have anything specific for what controls getting [...]. This is a generic install. No specific options of any kind were set. -- You are

[Bug 272536] 'make buildworld -j 8' fails: pid 79018 (clang), jid 0, uid 0, was killed: a thread waiting too long to allocate a page

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272536 --- Comment #2 from Yuri Victorovich --- (In reply to Mark Millard from comment #1) Swap is on /dev/ada0p2. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 272536] 'make buildworld -j 8' fails: pid 79018 (clang), jid 0, uid 0, was killed: a thread waiting too long to allocate a page

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272536 Mark Millard changed: What|Removed |Added CC||marklmi26-f...@yahoo.com ---

[Bug 272536] 'make buildworld -j 8' fails: pid 79018 (clang), jid 0, uid 0, was killed: a thread waiting too long to allocate a page

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272536 Yuri Victorovich changed: What|Removed |Added URL||https://people.freebsd.org/

[Bug 254698] RC4 from RC3 shutdown/reboot regression

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254698 Andrey Fesenko changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 254698] RC4 from RC3 shutdown/reboot regression

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254698 --- Comment #3 from Mark Millard --- (In reply to Andrey Fesenko from comment #2) I was only commenting on the reference to "installer panic", not on other aspects of the overall behavior. No panic is shown in the picture, just a

[Bug 254698] RC4 from RC3 shutdown/reboot regression

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254698 --- Comment #2 from Andrey Fesenko --- (In reply to Mark Millard from comment #1) PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 127494 root 20 0 2557332 1.0g 18732 S 100.0 53.8 1:25.97

[Bug 254698] RC4 from RC3 shutdown/reboot regression

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254698 Mark Millard changed: What|Removed |Added CC||marklmi26-f...@yahoo.com ---

[Bug 254698] RC4 from RC3 shutdown/reboot regression

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254698 Bug ID: 254698 Summary: RC4 from RC3 shutdown/reboot regression Product: Base System Version: 13.0-STABLE Hardware: Any OS: Any Status: New

[Bug 254395] bsdinstall: fail script install after BETA3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 Nathan Whitehorn changed: What|Removed |Added Resolution|--- |FIXED Status|New

[Bug 254395] bsdinstall: fail script install after BETA3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 --- Comment #15 from commit-h...@freebsd.org --- A commit in branch releng/13.0 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=3ef46634cd5a6ba0e156d5da095bbee5f63ec1cd commit 3ef46634cd5a6ba0e156d5da095bbee5f63ec1cd

[Bug 254395] bsdinstall: fail script install after BETA3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 --- Comment #14 from commit-h...@freebsd.org --- A commit in branch stable/13 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=4601382e1362352f17a33e4ed38db5dcfe3f6be5 commit 4601382e1362352f17a33e4ed38db5dcfe3f6be5

[Bug 254395] bsdinstall: fail script install after BETA3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 --- Comment #13 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=c2f16c595eb51c6e0cb6ece3f6f078d738019059 commit c2f16c595eb51c6e0cb6ece3f6f078d738019059 Author:

[Bug 254395] bsdinstall: fail script install after BETA3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 --- Comment #12 from Nathan Whitehorn --- Related things: https://reviews.freebsd.org/D29380 <- patch in review here https://github.com/libarchive/libarchive/issues/1516 <- libarchive issue here -- You are receiving this mail because:

[Bug 254395] bsdinstall: fail script install after BETA3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 --- Comment #11 from Nathan Whitehorn --- (In reply to Warner Losh from comment #10) It's pretty tricky, since it touches code in a lot of places, has to be conditional on platform, and runs a risk of breaking interactive installs just

[Bug 254395] bsdinstall: fail script install after BETA3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 --- Comment #10 from Warner Losh --- (In reply to Ryan Moeller from comment #8) Oh! I like this idea better, I think, but I don't know how hard it is to do. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 254395] bsdinstall: fail script install after BETA3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 --- Comment #9 from Nathan Whitehorn --- (In reply to Ryan Moeller from comment #8) We could delay it, but it's harder and less-localized than the other solutions. It also completely breaks PowerPC and other systems with analagous but

[Bug 254395] bsdinstall: fail script install after BETA3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 --- Comment #8 from Ryan Moeller --- Would it be possible to defer mounting the ESP until after the tarballs have been extracted? We don't actually have anything in /boot/efi in the base archive. My understanding is that it's just there to

[Bug 254395] bsdinstall: fail script install after BETA3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 --- Comment #7 from Warner Losh --- #4 sounds good for 13.0. Of the hacks, it's the most localized and least hacky, imho. I'd prefer #5, honestly, longer term but I've not thought through all the implictions. We should loop in cem@ since

[Bug 254395] bsdinstall: fail script install after BETA3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 Nathan Whitehorn changed: What|Removed |Added Severity|Affects Only Me |Affects Some People

[Bug 254395] bsdinstall: fail script install after BETA3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 Andrey Fesenko changed: What|Removed |Added Blocks||231027 Referenced Bugs:

[Bug 254395] bsdinstall: fail script install after BETA3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 --- Comment #5 from Andrey Fesenko --- (In reply to Nathan Whitehorn from comment #3) If possible, it is also worth mentioning in the release notes that you no longer need to specify the efi and boot partitions, but is it possible to make

[Bug 254395] bsdinstall: fail script install after BETA3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 --- Comment #4 from Andrey Fesenko --- (In reply to Nathan Whitehorn from comment #1) Installer fail, if set PARTITIONS="$DISKSLICE GPT { auto freebsd-ufs / }" fail too

[Bug 254395] bsdinstall: fail script install after BETA3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 --- Comment #3 from Nathan Whitehorn --- Well, I found the issue and there's even a nice comment in the relevant code that an older, smarter version of me put in in 2018 describing exactly why this is going to break: # Unpack

[Bug 254395] bsdinstall: fail script install after BETA3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 Ryan Moeller changed: What|Removed |Added CC||freql...@freebsd.org --- Comment

[Bug 254395] bsdinstall: fail script install after BETA3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 Nathan Whitehorn changed: What|Removed |Added CC||nwhiteh...@freebsd.org ---

[Bug 254395] bsdinstall: fail script install after BETA3

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 Bug ID: 254395 Summary: bsdinstall: fail script install after BETA3 Product: Base System Version: 13.0-STABLE Hardware: Any OS: Any Status: New

[Bug 197921] scheduler: Allow non-migratable threads to bind to their current CPU

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197921 Kubilay Kocak changed: What|Removed |Added Keywords|patch |needs-patch

[Bug 197921] [patch] [sched] Allow non-migratable threads to bind to their current CPU.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197921 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org --- Comment #1 from

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 --- Comment #24 from Kubilay Kocak --- (In reply to Slava from comment #22) Alternatively, one can apply the commit that was merged to stable/12 in base r342278, and rebuild/reinstall the kernel -- You are receiving this mail because:

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 --- Comment #23 from Kubilay Kocak --- (In reply to Slava from comment #22) The fix has been committed and merged to the stable/12 branch, and will be part of the next (12.1) FreeBSD release cut from that branch. If you would not like to

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 Slava changed: What|Removed |Added CC||sl...@planetslav.ca --- Comment #22 from

[Bug 208275] Kernel panic when reading from /dev/cd0 with a damaged dvd

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208275 Oleksandr Tymoshenko changed: What|Removed |Added CC||go...@freebsd.org

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 Kubilay Kocak changed: What|Removed |Added Flags|mfc-stable12? |mfc-stable12+

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 Andriy Gapon changed: What|Removed |Added Resolution|--- |FIXED Status|In

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 --- Comment #21 from commit-h...@freebsd.org --- A commit references this bug: Author: avg Date: Thu Dec 20 08:45:41 UTC 2018 New revision: 342278 URL: https://svnweb.freebsd.org/changeset/base/342278 Log: MFC r341632:

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 Andriy Gapon changed: What|Removed |Added Assignee|a...@freebsd.org|a...@freebsd.org

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 --- Comment #20 from commit-h...@freebsd.org --- A commit references this bug: Author: avg Date: Thu Dec 6 12:34:34 UTC 2018 New revision: 341632 URL: https://svnweb.freebsd.org/changeset/base/341632 Log:

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 --- Comment #19 from Andriy Gapon --- I am curious if anyone who had this problem before still has it. Especially, I am curious if they had an error message like in comment#1 and if that message went way. In addition to the prior analysis

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 --- Comment #18 from Matías Pizarro --- I was still having this problem on 13-CURRENT r340703 ( https://svnweb.freebsd.org/base?view=revision=340703 ). But that was nearly 6 days ago, I have not tested further down the 13-CURRENT

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 --- Comment #17 from Mark Johnston --- (In reply to Matías Pizarro from comment #16) There have been several ACPICA updates since the bug was filed, but 13-CURRENT and 12.0 should be in sync. Which revision of 13-CURRENT did you test?

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 --- Comment #16 from Matías Pizarro --- Hi all, FYI, I had the same issue with 13-CURRENT but it now works fine in today';s stable/12 | 12-PRERELEASE which I understand should be the same as 12-RC2. Thanks for your work on this, All the

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 Kubilay Kocak changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 Kubilay Kocak changed: What|Removed |Added Component|kern|bin

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 --- Comment #4 from Kyle Evans --- (In reply to Kubilay Kocak from comment #3) Hi, Sorry, I should have been informative. =) The commit for this that rewrote the offending parser predated stable/12, r335642; it was merged to stable/11 in

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 Kubilay Kocak changed: What|Removed |Added Flags|mfc-stable10- | --- Comment #3 from Kubilay

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 Kyle Evans changed: What|Removed |Added Resolution|--- |FIXED Status|In Progress

[Bug 227191] Cannot check battery status after upgrading to 12-CURRENT after r330957 (ACPI _STA method removed)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191 Kubilay Kocak changed: What|Removed |Added Summary|Cannot check battery status |Cannot check battery status

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Nicolas Hainaux changed: What|Removed |Added CC||nh.te...@gmail.com --- Comment

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 Kyle Evans changed: What|Removed |Added Assignee|b...@freebsd.org|kev...@freebsd.org -- You are

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 Kyle Evans changed: What|Removed |Added Flags||mfc-stable10-, |

[Bug 227259] accept()/poll() and shutdown()/close() - not work as in FreeBSD10, may broke many apps

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227259 Conrad Meyer changed: What|Removed |Added CC|freebsd-current@FreeBSD.org |c...@freebsd.org

[Bug 227259] accept()/poll() and shutdown()/close() - not work as in FreeBSD10, may broke many apps

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227259 --- Comment #3 from rozhuk...@gmail.com --- Why close() does not wakes thread that sleep on accept()? -- You are receiving this mail because: You are on the CC list for the bug. ___

[Bug 227259] accept()/poll() and shutdown()/close() - not work as in FreeBSD10, may broke many apps

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227259 --- Comment #2 from rozhuk...@gmail.com --- I do not understand why shutdown() does not generates POLLHUP/EV_EOF (EV_ERROR then add shutdowned socket) for poll() and kqueue(). -- You are receiving this mail because: You are on the CC list

[Bug 227259] accept() does not wakeup on shutdown()/close()

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227259 rozhuk...@gmail.com changed: What|Removed |Added CC||freebsd-current@FreeBSD.org

[Bug 227259] accept()/poll() and shutdown()/close() - not work as in FreeBSD10, may broke many apps

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227259 rozhuk...@gmail.com changed: What|Removed |Added Summary|accept() does not wakeup on |accept()/poll() and

[Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226700 --- Comment #6 from Charlie Li --- Also could someone remove current@ again? I accidentally used a cached page to comment and didn't pay attention to the CC list. -- You are receiving this mail because: You are

[Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226700 w.schwarzenf...@utanet.at changed: What|Removed |Added CC|freebsd-current@FreeBSD.org

[Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226700 Charlie Li changed: What|Removed |Added CC|

[Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226700 Conrad Meyer changed: What|Removed |Added CC|freebsd-current@FreeBSD.org |c...@freebsd.org

[Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226700 Charlie Li changed: What|Removed |Added CC|

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 jtkoert...@gmail.com changed: What|Removed |Added CC||jtkoert...@gmail.com ---

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #29 from Joe Barbish --- Today I submitted PR# 219421. This handbook patch removes all ezjail documentation from the handbook jail chapter and adds an political correct entry which is fair to all the

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #28 from Miroslav Lachman <000.f...@quip.cz> --- (In reply to Jonathan Anderson from comment #27) I think the opposite way. Or we end up with the same problems as with ezjail, portupgrade, portmaster etc. now. Some features in

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Jonathan Anderson changed: What|Removed |Added CC|

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #26 from Miroslav Lachman <000.f...@quip.cz> --- (In reply to Thomas Steen Rasmussen / Tykling from comment #25) Are you serious? Then why Joe provided the idea how to make ezjail survive this code removal? Did you read the

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Thomas Steen Rasmussen / Tykling changed: What|Removed |Added CC|

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Jamie Gritton changed: What|Removed |Added CC|

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #23 from Miroslav Lachman <000.f...@quip.cz> --- (In reply to Warner Losh from comment #22) I think it turns in to bikeshed now. Are we talking about rc.conf variables to configure jails or about this as dependency for ezjail?

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Warner Losh changed: What|Removed |Added CC||i...@freebsd.org

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #21 from Miroslav Lachman <000.f...@quip.cz> --- (In reply to Julian Elischer from comment #20) Why? To miss the opportunity to remove deprecated code for the next major release again? Then why we even put warnings to outdated

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #20 from Julian Elischer --- previous comment shoudl have read "I strongly request that the bug be closed again". -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Julian Elischer changed: What|Removed |Added CC|

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Ngie Cooper changed: What|Removed |Added Status|Closed |Open

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Brooks Davis changed: What|Removed |Added Resolution|--- |Works As

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #16 from Joe Barbish --- This is my objection to waiting for 12.0 before doing this. When 10.0 came out the removal of the rc.conf method was scheduled to happen at 11.0. Now 3+ years later 11.0 is out

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #15 from Mathieu Arnold --- (In reply to Joe Barbish from comment #9) > I see no benefit to dropping rc.conf jail support on a major release over a > minor release. I both cases you are going to suffer the

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #14 from rai...@ultra-secure.de --- I think the PTB (powers that be) ultimately decided that it's not in the interest of the project to have a tool and (and possibly an API) in base to create jails a la ezjail. At least, that's

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 erdge...@erdgeist.org changed: What|Removed |Added CC||erdge...@erdgeist.org ---

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #12 from Ngie Cooper --- For the sake of maintaining POLA, I recommend not breaking it on a dot-release and instead throw the switch on ^/head. I am very much in agreement there with grembo@. I think it would

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Conrad Meyer changed: What|Removed |Added CC||c...@freebsd.org

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #10 from Michael Gmelin --- (In reply to Joe Barbish from comment #9) I tried to give you feedback from real world installations and real world upgrade procedures, as you claimed ezjail isn't relevant any

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #9 from Joe Barbish --- I see no benefit to dropping rc.conf jail support on a major release over a minor release. I both cases you are going to suffer the same consequences of NOT heeding the warning

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #8 from Michael Gmelin --- (In reply to Joe Barbish from comment #7) As maintainer of sysutils/qjail you might look at this like it. I just know that we run hundreds of jails using ezjail and breaking that

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #7 from Joe Barbish --- In reply to comment # 3 which states "But I believe the number of ezjail-jails is significant." This is un-true, since 10.0 was published many ezjail users have been moving to

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Michael Gmelin changed: What|Removed |Added CC|

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Chris Hutchinson changed: What|Removed |Added CC|

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #4 from Miroslav Lachman <000.f...@quip.cz> --- There is nothing special on jails created by ezjail so the configuration can be converted very easily. I have my own solution for jails with very similar structure and nullfs mount

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 --- Comment #3 from rai...@ultra-secure.de --- Fair enough. But I believe the number of ezjail-jails is significant. Also, as you can see, until now (11.0) it's the 3rd-party tool recommended by the FreeBSD project itself (if you take the

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Miroslav Lachman <000.f...@quip.cz> changed: What|Removed |Added CC|

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 rai...@ultra-secure.de changed: What|Removed |Added CC||rai...@ultra-secure.de

[Bug 218849] Remove rc.conf jail configuration via jail_* variables

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 Bug ID: 218849 Summary: Remove rc.conf jail configuration via jail_* variables Product: Base System Version: 11.0-RELEASE Hardware: Any OS: Any Status: New

[Bug 217994] Kernel panic in native_lapic_setup with 12-CURRENT on EC2 machine

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217994 Konstantin Belousov changed: What|Removed |Added CC|freebsd-current@FreeBSD.org | -- You

[Bug 217994] Kernel panic in native_lapic_setup with 12-CURRENT on EC2 machine

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217994 Sylvain Garrigues changed: What|Removed |Added CC|

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 Mark Linimon changed: What|Removed |Added Keywords||patch -- You

[Bug 208938] usr.sbin/config does not preserve whitespace in static env

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208938 Sylvain Garrigues changed: What|Removed |Added Attachment #169494|0

  1   2   >