On 11/04/2013 11:55 PM, Jan Engelhardt wrote:
On Monday 2013-11-04 23:48, ScotXW wrote:
Hi,
I created this [1] scheme. Can you help fill in the blank? I know there is very
extensive documentation about systemd, it is way too extensive for my purposes,
the home user.
[1] https://commons.wikimedia.org/wiki/File:Linux_startup_process_wip.svg
Seems rather strange to find GRUB and Linux in "BIOS".
And if you talk about Uboot and Redboot and whatever else, then
marking the orange section as "GRUB" is sorta outta place.
Linux kernel and GNU GRUB can be payloads to coreboot. That is why they
are on that level in their own color.
However, the y-axis is the time from the connection to power. Does it
make more sense now?
The distinction of GNU GRUB is shurely important in a scheme about the
start up process. It is the bootstraploader.
It's also wrong on so many accounts.
-initramfs is not mounted, because it is not a filesystem.
AFAIK ramfs = ram file system, so I assumed it is being mounted. How
else to epress it? Was initrd "mounted", is that at least correct? Will
tmpfs be "mounted"?
-kernel does not execute /usr/bin/systemd but /init from the initramfs,
or in case none was used, /sbin/init.
Hö? You lost me.
-/usr/lib/systemd/system is a directory, not an executable entity
So "system processes the declarative files in /../"?
-you already have systemd, so having systemd again in "user interfaces"
is sort of inside out
Yeah, there is alink missing between them, because systemd gets startet
and then remains available as a daemon.
Regards,
ScotX
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
