| 1 |
Dale: |
| 2 |
... |
| 3 |
[ re separate /usr, initramfs/initrd ] |
| 4 |
> You may can do it the way you are wanting to but for how long is the |
| 5 |
> question. Odds are high that at some point, you will have a system that |
| 6 |
> won't boot because something that's needed isn't there. |
| 7 |
... |
| 8 |
|
| 9 |
initrd/initramfs is there to make life easier for the distribution. |
| 10 |
It is needed when your / is on a device with dynamic minor numbers. |
| 11 |
Otherwise, you don't gain much from it. |
| 12 |
|
| 13 |
Separate /usr is a complication mostly for laptop systems where strange |
| 14 |
things are needed during boot. |
| 15 |
It is also a complications for programs depending on libs in /usr. E.g. |
| 16 |
$ ldd /bin/getsubids | grep /usr |
| 17 |
libsubid.so.4 => /usr/lib64/libsubid.so.4 (0x00007f2ea07ad000) |
| 18 |
libcrypt.so.2 => //usr/lib64/libcrypt.so.2 (0x00007f2ea0578000) |
| 19 |
So if getsubids is needed for boot, you either have to move thoose libs |
| 20 |
to /lib or use a merged /usr. |
| 21 |
|
| 22 |
The best way to avoid the problems above i make you system simple, |
| 23 |
but that seems to against the no prevalent misconception that things |
| 24 |
have to be complex. |
| 25 |
|
| 26 |
Regards, |
| 27 |
/Karl Hammar |
Archives