Re:3 Advantages to Running FreeBSD as Your Server Operating ...
by hn8305823 on Tuesday August 15, 2023 @11:12AM
(#37134962)
> shutdown -r now
I know this is in lots of textbook examples but I didn't think anyone ever actually typed this. I've always used 'halt' or 'reboot'
Re:3 Advantages to Running FreeBSD as Your Server Operating ...
by rjsw on Tuesday August 15, 2023 @11:42AM
(#37135325)
Using 'halt' or 'reboot' won't run all the scripts needed to shut down cleanly, the correct command to use is 'shutdown -r now'.
Re:3 Advantages to Running FreeBSD as Your Server Operating ...
by red-iron-pine on Tuesday August 15, 2023 @04:24PM
(#37138895)
IIRC, 'reboot' is aliased to 'shutdown -r now' in several modern distros
Re:3 Advantages to Running FreeBSD as Your Server Operating ...
by toast0 on Tuesday August 15, 2023 @11:39AM
(#37135296)
reboot and halt have a history of being less graceful on some systems, and I've been bitten. For FreeBSD, I think reboot skips shutdown scripts, doesn't notify all terminals, etc; just kill everything, sync the disk and reboot.
That's not ungraceful, but it's not exactly pleasant.
OTOH, my openwrt device doesn't have a shutdown binary, just a reboot binary.
Re:3 Advantages to Running FreeBSD as Your Server Operating ...
by JohnFen on Tuesday August 15, 2023 @01:02PM
(#37136375)
I use "shutdown -r now" instead of "reboot" because "halt" or "reboot" is not universally available, but shutdown mostly is.
Re:3 Advantages to Running FreeBSD as Your Server Operating ...
by kevans91 on Tuesday August 15, 2023 @03:19PM
(#37138114)
> [...] But if you use pkg, and the new point release added a syscall, you will have problems installing new packages (or upgrading) once the package builders update; I don't quite remember the timeline, but it's usually a few months after the point release. [...]
The previous release in the branch gets dropped after ~3 months, probably aligned to the end of the month that its EOL lands in; then pkg builders switch to the newer release in the branch.
In modern times, point releases tend to be about once a year, which doesn't seem too frequent to me? But if you use pkg, and the new point release added a syscall, you will have problems installing new packages (or upgrading) once the package builders update; I don't quite remember the timeline, but it's usually a few months after the point release. (Although, I think there was a time where pkg would default to a faster updating repository, and you might see problems sooner)
My upgrade process is a bit laborious (freebsd-update -r ... upgrade; freebsd-update install; shutdown -r now; freebsd-upgrade install; pkg update; pkg upgrade; reboot). Might be another pkg command I forgot, but it will likely prompt you.
If you're not interested in upgrading everything together at once, ports is probably a better choice. Sometimes after an OS upgrade, you'll need to install a compat port to continue to run old software; it's possible to do that with pkg, but IMHO, it's difficult to get the compat package installed without upgrading other packages, and then you may as well upgrade everything.
Personally, I don't find docker-compose simple. Probably from lack of experience, but I find it hides so much that makes it much more difficult to debug. Most of the time, I'd rather run everything in a single host, but I'm encouraged to use docker-compose by my workplace, so...