Technological advantages over Linux

[Ralf Mardorf]

On Fri, 14 Feb 2020 13:01:30 -0600, Valeri Galtsev wrote:
>On 2020-02-14 12:54, Ralf Mardorf via freebsd-questions wrote:
>> Hi,
>> 
>> what is better, a doorbell, a car or a watering can?
>> It's not the best analogy, since regarding operating systems the
>> answer not only depends on the use case, but also on the skills of
>> the user.
>> 
>> On Fri, 14 Feb 2020 08:03:06 -0600, Valeri Galtsev wrote:  
>>> Add to that binary logs  
>> 
>> "Tip: While the journal is stored in a binary format, the content of
>> stored messages is not modified. This means it is viewable with
>> strings, for example for recovery in an environment which does not
>> have systemd installed, e.g.:
>> 
>> $ strings
>> /mnt/arch/var/log/journal/af4967d77fba44c6b093d0e9862f6ddd/system.journal
>> | grep -i message " -
>> https://wiki.archlinux.org/index.php/Systemd/Journal  
>
>Thanks for the tip Ralf! As always, your brilliance brings me, lazy 
>person, right to what I need without learning new everchanging
>commands ;-)
>
>This (using strings here) reminds me a comedy clip about machintosh: 
>"sometimes you need to trick mac into doing what you actually want him 
>to do" ;-)

IMO a real pitfall of systemd are race conditions during startup.
It's not an issue for those of us, who run a machine 24/7.

Another PITA on Linux machines are drop directories, overriding sane
configs, providing everything in one place.

IOW a user might rely on /etc/foo.conf , but an update despotic installs

/etc/foo.d/10-bar.conf

and

/etc/foo.d/20-bra.conf

overriding all the values chosen for bar and bra by the admin, stored
in /etc/foo.conf .

An update never ever would replace /etc/foo.conf . On Arch Linux it
would be stored as /etc/foo.conf.pacnew , almost all Linux distros
provide such a solution, but the admin is screwed, if an update does
add a file to /etc/foo.d/ .