[zfs-discuss] zfs-discuss Digest, Vol 9, Issue 48

Mikko Tanner mikko.tanner at gmail.com
Tue Jan 19 04:13:55 EST 2016

This is only true of systemd-infested distros. Things have been working 
perfectly well for as long as I remember with separate filesystems. It 
is only until systemd's lazy coding and invented problems that this has 
become an issue.

Not supporting separate filesystems (aka stuffing most of the system in 
/usr) is a faulty design choice. There is no compelling reason at all 
why /usr should be necessary for early boot -- /bin and /sbin are there 
for a reason. Diverting from the basic POSIX assumptions just for the 
sake of appeasing a certain distro's design choices is fundamentally broken.

TL;DR - the issue here is systemd, nothing else.

Mikko Tanner

On 19.1.2016 9:37, zfs-discuss-request at list.zfsonlinux.org wrote:
> From:
> Gordan Bobic <gordan.bobic at gmail.com>
> Date:
> 19.1.2016 7:07
> To:
> "General discussion - ask questions, receive answers and advice from 
> other ZFS users" <zfs-discuss at list.zfsonlinux.org>
> On your distro, is /sbin a symlink to /usr/sbin?
> If so, having a separate /usr simply isn't going to work, as I 
> explained before. Initrd will get your rootfs mounted and perform a 
> switchroot, but once it gets there, there will be no way to do 
> anything because the new rootfs has no systemd, no mount.zfs, no zfs, 
> or anything else. Even if the distro version you are running now isn't 
> laid out like this (because it is an older version), all major distros 
> are heading in this direction. Separate /usr is becoming completely 
> unsupportable.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.zfsonlinux.org/pipermail/zfs-discuss/attachments/20160119/7fc90995/attachment.html>

More information about the zfs-discuss mailing list