>On Sat, 26 Jan 2013 16:07:55 -0600
>Bruce Dubbs <[email protected]> wrote:
> systemd uses binary log files that can't use standard tools like
> grep. Myth or fact?
Big no-no.
> systemd solves problems encountered by many/most LFS users. Myth or
> fact?
Interesting point: I have no memmory of the last time I changed the
bootscripts.
> systemd has/needs over 100 pages of documentation. Myth or fact?
I went to see what other posts are on the authors blog and the first
thing I see is "systemd for administrators, part XX". Next is part XIX,
followed by part XVIII and so on...
Compare and contrast with LFS bootscripts which I was able to parse and
grok with only the begginers understanding of shell. Years back. Point
1 for sysvinit+udev.
* * *
I read a little of the "systemd for administrators" saga (part XX) and
then I ran into this little line which was quite enlightening:
"[I'll explain how to derp...]Or in other words, how you can drive up
the density of customer sites on a system while spending less on new
hardware."
For me, this sentence points the finger to the systemd's goal, and also
to the reason this whole hakoohah about /dev and booting has been going
on for years^H^H^H^H^Hdecades. Virtualization, or something such.
People appear in a need for a good abstraction of both the hardware and
(more importantly) the boot process.
--
You don't need an AI for a robot uprising.
Humans will do just fine.
--Skynet
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
