❦ 4 janvier 2016 00:03 +1300, Daniel Reurich <daniel@centurion.net.nz> :
>>> Then why is it that since the introduction of systemd is having /usr on
>>> a separate partition suddenly considered evil and systemd complains
>>> loudly about it. It always has worked and does work fine for me with
>>> sysvinit
>>
>> systemd complains if it has to mount /usr itself. This is because
>> mounting of local filesystems generally depends on various services and
>> udev hooks that may themselves depend on /usr. This is also true when
>> using sysvinit. Some services go through contortions to work before
>> /usr is mounted; others may behave subtly differently if it's a
>> separate filesystem. We really need a simplified code path for
>> mounting /usr early on, and that is now provided by the initramfs.
>
> Ah, so it's actually packages that don't separate device configuration
> logic from the application or daemons properly that has caused the
> brokenness. Can we identify and fix the packages that cause this
> issue?
The merge is also here to not have to fix those subtle issues and reduce
the amount of code needed to boot (more reliability, less
bugs). Manpower is limited.
The amount of brokenness of a separate /usr can also be witnessed by the
number of executables that had to migrate from /usr/bin to /bin. 115 on
my system (counting the symlinks).
Also, what other distributions do matter. Hard-coded path for
executables are a reality and once other distributions will have merged
/usr, people may start invoking /bin/wget instead of /usr/bin/wget and
this won't work on Debian. For the end user, this will just be something
that works on Fedora, but not on Debian and the blame will be put on
Debian.
--
10.0 times 0.1 is hardly ever 1.0.
- The Elements of Programming Style (Kernighan & Plauger)
Attachment:
signature.asc
Description: PGP signature