On Thu, Oct 30, 2014 at 10:27:50AM +0100, Hans wrote: > Dear maintainers, > > completely without starting any flamewars: > > I am using systemd and I have /usr mounted on a separate partition as well as > /var, /home, /boot and /. > > Additionally /usr, /var and /home are luks encrypted. > > Due to this profile, I get a lot of annoying errors, as systemd does not find > /usr when it is started, because it produces an error and then switches to > verbose mode. This is very annoying! > > For a new installation it might be ok, to put /usr on the root partition, but > I guess, there are a lot of systems in the world running a partition profile > like mine. > > Besides of the mentioned problem systemd is running well. > > I thought about this problem. Might it be possible, to change systemd in that > way, that it will start after all partitions are mounted? I know, it must be > done in the source code, but as I am no coder, I cannot do it myself. I don't think this is possible because, for complex setups, you run into a chicken-and-egg system. People are getting more and more "creative" with where they put data and are wanting that data to become available at boot. In the "good old days", your file systems were on a local disk and looking at /dev/hd* would be enough to find everything you wanted. Then along came network file systems, and now you need the network to be up before you can mount the file system. Then there are network block devices (NBD, iSCSI etc), which you probably want to fsck before you mount. There there are device-mappers (RAID, LVM etc) whereby those network block devices might be agglomerated into a larger device (maybe with local devices, maybe with other hosts which are also still booting). And so on and so on. Systemd, Upstart and other "event-based" init systems try to sidestep most of this mess by not explicitly saying "Mount local filesystems, then bring up the network, then mount network filesystems", but rather, they start some tasks (such as 'mount all' and 'start network') and as pieces of the puzzle become available, this allows other tasks to continue. So, it's not *really* about "This one arbitrary file system must be on your root filesystem" but rather "All the programs needed to get any system booted (because the design should accommodate as many people as possible), should be available in a single place". > > So I ask the developers hereby, maybe it wil be possible to do that. > > Again, I do not want to start any flamewars! IMO each user should decide for > himself, what he wants to use. I want to use systemd, and I just intend with > this message to improve systemd. > > Thank you very much for reading this and any help. > > Best regards > > Hans > > > > > > -- > To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org > Archive: [🔎] 2169479.eyGDWmysPc@protheus7">https://lists.debian.org/[🔎] 2169479.eyGDWmysPc@protheus7 >
Attachment:
signature.asc
Description: Digital signature