Recent Features
| |||||||||||||
This is sheer fantasy...This is sheer fantasy...Posted Dec 9, 2011 10:14 UTC (Fri) by khim (subscriber, #9252)In reply to: Distribution quote of the week by dlang Parent article: Distribution quote of the week
the issue here is that /sbin is supposed to be all you need to get the system to the state that will allow you to then mount other filesystems (and fix them if needed) This is strange fantasy - I'm not sure if it was ever true. Without /bin/sh most systems can reach the state where they can mount anything else. Sure, it's possible that at some point Solaris have enough tools in /sbin to actually start the system in emergency more, but I doubt that very much. And in any case this discussion is entirely theoretical because today /sbin is symlink to /usr/sbin in Solaris...
(Log in to post comments)
This is sheer fantasy... Posted Dec 9, 2011 10:39 UTC (Fri) by mpr22 (subscriber, #60784) [Link] And even on Solaris 9, where /sbin was still a real directory on the root filesystem (but /bin and /lib were symlinks to /usr/bin and /usr/lib), the contents of /sbin would certainly not be enough by themselves to fix a system whose separate /usr volume had been mangled.
This is sheer fantasy... Posted Dec 9, 2011 17:29 UTC (Fri) by drag (subscriber, #31333) [Link]
> This is strange fantasy - I'm not sure if it was ever true.
It was true. A very long time ago it was true.
Back when the easiest way to get your PC running Linux was to first boot your PC into Windows and use Window's "device manager" to take notes on your hardware configuration so that you could then get a working kernel config going.
Since then, of course, things have changed.
I was around back then, you know... Posted Dec 10, 2011 7:08 UTC (Sat) by khim (subscriber, #9252) [Link] Back when the easiest way to get your PC running Linux was to first boot your PC into Windows and use Window's "device manager" to take notes on your hardware configuration so that you could then get a working kernel config going. I'm pretty sure back then you had no need for anything is /sbin to boot your system: you only needed files in /boot (well, initially they were placed in the root of the filesystem) and one program (initially sash, later busybox) on a floppy drive. I'm pretty sure you can do the same today and even with Fedora's "grand unification" it should still be possible. Except for a floppy drive: often contemporary systems just don't include the necessary hardware...
I was around back then, you know... Posted Dec 10, 2011 8:05 UTC (Sat) by drag (subscriber, #31333) [Link]
> I'm pretty sure back then you had no need for anything is /sbin to boot your system: you only needed files in /boot (well, initially they were placed in the root of the filesystem) and one program (initially sash, later busybox) on a floppy drive. I'm pretty sure you can do the same today and even with Fedora's "grand unification" it should still be possible. Except for a floppy drive: often contemporary systems just don't include the necessary hardware...
That seems to agree with the reasoning to get rid of /sbin /bin, etc in modern times.
The initrd will have everything you need to mount a remote /usr/ directory. You can use busybox with initrds, for example.
|
|||||||||||||