[Bug 243094] reboot problem

2020-01-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 --- Comment #11 from b.l.ber...@t-online.de --- (In reply to Jack from comment #10) It makes little sense to have two different programs for rebooting FreeBSD. Reasons: Double the effort! And one (shutdown) is developed further and the othe

[Bug 243094] reboot problem

2020-01-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 Jack changed: What|Removed |Added CC||xxjack1...@gmail.com --- Comment #10 from J

Re: [Bug 243094] reboot problem

2020-01-05 Thread Kelly Alger
Call me crazy, but it seems like the real question is why you would want a command called, "reboot," to NOT execute /etc/rc.shutdown, no? Sure, maybe with some extra param. it would just force a shutdown without executing /etc/rc.shutdown, but certainly not as the default. Of course, if it's sp

[Bug 243094] reboot problem

2020-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 --- Comment #9 from Bernhard Berger --- like this, and that's it. No more discussion. I'm very upset. Overwork reboot or don't. No more bug reports from me, that upsets me too much. -- You are receiving this mail because: You are the as

[Bug 243094] reboot problem

2020-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 --- Comment #8 from Bernhard Berger --- (In reply to Conrad Meyer from comment #7) I'll give you an example: If it says "bread" on the package, then any reasonable person would assume that there is bread inside. This is also the case with

[Bug 243094] reboot problem

2020-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 Conrad Meyer changed: What|Removed |Added Severity|Affects Many People |Affects Some People Vers

[Bug 243094] reboot problem

2020-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 --- Comment #6 from Bernhard Berger --- (In reply to Conrad Meyer from comment #5) I am a user and use FreeBSD as a server system for a home server. What I really liked about FreeBSD was the ports system. Of course, between ports that are

[Bug 243094] reboot problem

2020-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 --- Comment #5 from Conrad Meyer --- So AFAICT, this command isn't specified by POSIX; we're not constrained by a standard, just history. What Linux has done is make reboot more like 'shutdown', unless you specify "--force" (and maybe ther

[Bug 243094] reboot problem

2020-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 --- Comment #4 from Bernhard Berger --- (In reply to Mark Johnston from comment #3) Yes, there are four alternatives: 1. replace reboot with a script that executes "shutdown -r now 2. reboot to make sure that it restarts the system in acco

[Bug 243094] reboot problem

2020-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org --- Comment #3 f

[Bug 243094] reboot problem

2020-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 --- Comment #2 from Bernhard Berger --- "reboot" does the same thing in name as "shutdown -p -now"! No, it doesn't, it doesn't call "/etc/rc.shutdown" and that's a big mistake in my eyes because the programmers of rc.d/scripts assume that

[Bug 243094] reboot problem

2020-01-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 --- Comment #1 from Conrad Meyer --- I agree it's a confusing distinction, but I think it's pretty baked in at this point. The documentation for reboot(8) could be better about pointing at shutdown. -- You are receiving this mail because

[Bug 243094] reboot problem

2020-01-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 Bug ID: 243094 Summary: reboot problem Product: Base System Version: 12.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Many People