bin, sbin, etc as seperate LVM volumes 666
On Tuesday 21 March 2006 19:48, Floyd L. Davidson stood up and spoke the following words to the mbuttes incomp.os.linux.misc...:
Putting *-mnt* on a different filesystem would be really awkward. ;-)
On the other hand, *-root* can be placed on a different filesystem. That shouldn't be a problem as long as the mountpoint exists, i.e. it must not be a symbolic link to e.g. *-home-root.*
In most distributions, *-usr-tmp* already is a symbolic link to *-var-tmp.*
As for *-tmp,* if the OP so desires and has enough RAM, he could make that atmpfs. That way, he would be sure that *-tmp* is empty again upon each boot, regardless of whether he installedtmpwatchor of the presence or absence of...
rm -rftmp-*
... in hisinitscripts.
True, but it doesn't *have* to be on the root filesystem. It's just a lot easier to typemnt-floppy than it is to typeelsewhere-mnt-floppy, and serves...
I also have that one as a separate filesystem, but it's not really recommended in most distributions unless the user is going to install lots of packages from sources. Most distributions just put everything under *-usr* and *-opt.* ;-)
That would most certainly exclude Windows Admins, considering that Microsoft has a tendency to rewrite the definitions of certain concepts
-- With kind regards,
*Aragorn* (Registered GNU-Linux user #223157)
bin, sbin, etc as seperate LVM volumes 667
Linux groups from Newsgroups