zlacker

[parent] [thread] 8 comments
1. j16sdi+(OP)[view] [source] 2022-05-11 07:43:10
> There's no actual REASON for any of it anymore.

No reason to do it on embedded system. Lots of backward compatibility reason on servers/desktops.

replies(3): >>pilif+W >>usrbin+Kf >>moffka+cn
◧
2. pilif+W[view] [source] 2022-05-11 07:50:58
>>j16sdi+(OP)
it's my understanding that most distros by now have moved to have their stuff in /usr, though there might still be backwards compatibility symlinks of course.
replies(1): >>hulitu+v5
◧◩
3. hulitu+v5[view] [source] [discussion] 2022-05-11 08:30:32
>>pilif+W
Good luck mounting /usr when mount is in /usr/bin. Not everybody uses a ramdisk to boot the system.
replies(2): >>pabs3+D5 >>colonw+Cf
◧◩◪
4. pabs3+D5[view] [source] [discussion] 2022-05-11 08:33:20
>>hulitu+v5
Not using an initrd is unsupported on lots of distros these days.
replies(1): >>bluefl+R5
◧◩◪◨
5. bluefl+R5[view] [source] [discussion] 2022-05-11 08:35:30
>>pabs3+D5
You mean initramfs, initrd is unsupported on lots of distros these days.
replies(1): >>pabs3+66
◧◩◪◨⬒
6. pabs3+66[view] [source] [discussion] 2022-05-11 08:37:57
>>bluefl+R5
Right.
◧◩◪
7. colonw+Cf[view] [source] [discussion] 2022-05-11 10:21:16
>>hulitu+v5
Just don't put /usr on its own partition. What is the point anyway after we have merged /bin into /usr/bin, /lib into /usr/lib etc. Just put your operating system on a single partition and be happy.
◧
8. usrbin+Kf[view] [source] 2022-05-11 10:22:25
>>j16sdi+(OP)
Backward compatibility can be ensured with a couple of symlinks.
◧
9. moffka+cn[view] [source] 2022-05-11 11:34:02
>>j16sdi+(OP)
> backward compatibility

You're kidding me right? Nobody ever bothers with that for anything else and the company I work at spends like more than half the time resolving stupid install breaking changes that nobody asked for. This would just be one minor extra thing on that pile, but at least it would make sense for once.

[go to top]