Re: deprecating /usr as a standalone filesystem?
Henrique de Moraes Holschuh <email@example.com> writes:
> On Mon, 11 May 2009, Goswin von Brederlow wrote:
>> > A separate /usr *is* the way to go if you don't want any writes in
>> > that filesystem 99.9% of the time (i.e. when you're not doing an
>> > upgrade).
>> A read-only / does the trick just as well. And if you don't want
>> writes to /usr you probably don't want writes to /bin or /sbin
>> either. So read-only / is really the way to go. Not a strong argument
>> for a seperate /usr.
> No, RO / is a lot more difficult to pull off (remember: some of us don't
> want initrds), while RO /usr is really just a three-char change on fstab
> (and if you want apt to remount things automatically, two lines in a config
Why would you need an initrd for a read-only /?
A read-only / should work out of the box just like a read-only /usr. I
haven't installed a fresh one in a long while though so if you know of
problems speak up so bugs can be filed and packages can be fixed.