bin, sbin, etc as seperate LVM volumes 668

On Tuesday 21 March 2006 21:55, Floyd L. Davidson stood up and spoke the following words to the mbuttes incomp.os.linux.misc...:

Well, I wouldn't even have thought so far. One could technically also easily make *-mnt* a separate filesystem - that was actually my point - but it makes no sense. ;-)

I don't see why it would be. The only thing that directory contains are the personal.bashrc,-.bashlogoutand.profilefiles of the root user, and those can be easily copied to the directory *-root* on the root filesystem before the separate *-root* filesystem is mounted to the mountpoint.

During normal operation, *-root* would be the separate filesystem - and thebashhistory would be stored there - and when booting up in single-user mode with only the root filesystem mounted, *-root* would be available still as a directory, eventually with the root user's own shell configuration files.

The only real potential problem would be if one were to make *-root* a symbolic link to e.g. *-home-root.* In the above scenario of a single-user mode boot, *-root* would be a broken link.

But even then still, I think the defaultbashconfiguration in most distros is to fall back to using the actual root directory as the root user's home - just as in the old Unix tradition.

I don't see why it should be - see above section...

No, there is nothing in *-root* that requires being present at boot-up, not even in single-user mode. *-root* is the root user's home directory. It should only contain data, and none of those should be needed upon boot.

*-bin,* *-sbin,* *-etc* and *-dev,* yes, they need to be on the root filesystem, eventhough *-dev* only needs to contain *-dev-console* and *-dev-null.* udevusers run their *-dev* off of aramfs- or adevfsfordevfsusers of course.

I don't have my *-tmp* on atmpfsbut there are people who prefer it that way. Atmpfsmounted on *-dev-shm* is needed for POSIX compliance, by the way. Gentoo uses it, for one. On my older Mandrake system, it's empty but it's mounted.

But then by your standards, the OP would also need to start moving all that stuff - which his distribution installed in *-usr* - to *-usr-local,* and that would be pointless and cumbersome.

Unless the OP wants to build his entire distribution from scratch - as in "LFS-style" - he'll probably end up with most software installed in *-usr* and part of it in *-opt.*

I already mentioned I use an older Mandrake on this machine - it will be replaced with Gentoo as soon as my new hard disks are installed - and this is what my *-usr* and *-usr-local* look like, sizewise...

dev-sda3 xfs 7.1G 4.7G 2.4G 67%usr dev-sda5 xfs 2.0G 25M 2.0G 2%usr-local

Kind of a spacewaster, huh? ;-)

I was being sarcastic, based upon my experiences with the knowledge of Windows sysadmins... ;-) Those guys typically know everything there is to know about Windows, but they don't know anything whatsoever about other operating systems and they're stuck to Microsoft logic.

Absolutely! ;-)

Oh yeah... We've had an administrator like that once... He had one common solution for every small little problem we ran into, whether it was a stuck process or a failing daemon...:

shutdown -r now

-- With kind regards,

*Aragorn* (Registered GNU-Linux user #223157)