> From: Vratislav Podzimek [mailto:vpodzime@xxxxxxxxxx] > Sent: 28 March 2012 12:25 > > On Tue, 2012-03-27 at 16:34 -0400, Chris Lumens wrote: > > --- > > pyanaconda/storage/__init__.py | 2 +- > > 1 files changed, 1 insertions(+), 1 deletions(-) > > > > diff --git a/pyanaconda/storage/__init__.py > b/pyanaconda/storage/__init__.py > > index c7cc81e..8483eca 100644 > > --- a/pyanaconda/storage/__init__.py > > +++ b/pyanaconda/storage/__init__.py > > @@ -1165,7 +1165,7 @@ class Storage(object): > > errors = [] > > > > mustbeonlinuxfs = ['/', '/var', '/tmp', '/usr', '/home', > '/usr/share', '/usr/lib'] > > - mustbeonroot = ['/bin','/dev','/sbin','/etc','/lib','/root', > '/mnt', 'lost+found', '/proc'] > > + mustbeonroot = ['/bin','/dev','/sbin','/etc','/lib','/root', > '/mnt', 'lost+found', '/proc', '/usr'] > > > > filesystems = self.mountpoints > > root = self.fsset.rootDevice > Correct me if I am wrong, but isn't the whole /usr move stuff about > allowing having /usr shared between more machines and read-only etc. > thus as a separate partition? Shall we really disable this > functionality > so strictly? I myself have separate /usr on one of my machines (/usr on > SSD and / on HDD). > > -- I'm not a developer and don't know the code; is this talking about mountpoints, or the actual contents of /usr? After all, the /dev and /proc mountpoints are physically on root but the actual filesystems are not. Moray. “To err is human; to purr, feline.” _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
