possible solutions: make FHS-compliance part of msec 5 or make FHS-compliance a boot choice
Bob Walker ([EMAIL PROTECTED]) wrote*: > >According to the File Hierarchy Specification (V2.2), '/usr' is supposed to be >shareable, read-only data. R/W support for '/usr' should be put in '/var'. >For FHS-compliant filesystems: > >/usr = static, shareable >/opt = static, shareable >/etc = static, unshareable >/boot = static, unshareable >/var = variable, shareable/unshareable > >bob > > >On Wednesday 09 October 2002 10:21 pm, Ben Reser wrote: >> On Wed, Oct 09, 2002 at 03:03:30PM -0700, Todd Lyons wrote: >> > Hmmm, I thought this whole thread was about being unable to export a >> > /usr share as ro since things wrote to it by default. Apparently I >> > mixed this up with some other thread. Sorry. >> >> It is and it isn't. It's about not being able to mount /usr ro (NFS or >> not) because it writes to /usr. :) > > -- SI Reasoning [EMAIL PROTECTED] gpg public key ftp://ftp.p-p-i.com/pub/si-mindspring-pubkey.asc "What is bountiful?" the ancients asked. True bounty was not the treasury of the emperor, but the generosity of the earth." - Deng Ming-Dao
