Date: Fri, 25 Aug 2000 11:15:35 +0930 From: Greg Lehey <grog@lemis.com> To: j mckitrick <jcm@freebsd-uk.eu.org> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: read only / filesystem Message-ID: <20000825111535.F548@wantadilla.lemis.com> In-Reply-To: <20000824130404.A51338@dogma.freebsd-uk.eu.org>; from jcm@freebsd-uk.eu.org on Thu, Aug 24, 2000 at 01:04:04PM %2B0100 References: <20000824002732.A45983@dogma.freebsd-uk.eu.org> <20000824101341.D66923@wantadilla.lemis.com> <20000824130404.A51338@dogma.freebsd-uk.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, 24 August 2000 at 13:04:04 +0100, j mckitrick wrote: > On Thu, Aug 24, 2000 at 10:13:41AM +0930, Greg Lehey wrote: >> On Thursday, 24 August 2000 at 0:27:32 +0100, j mckitrick wrote: >>> >>> i've decided so try a suggestion i heard here: >>> i'm going to make / read only. when i booted, i saw a bunch of messages >>> about / being read only. is there anything i need to do special to prevent >>> problems from this setting? >> >> Obviously. Read the messages, decide what to do, and do it. > > i didn't want to break anything in the process. the commands causing the > messages must be there for a reason. Right, they're there in case the permissions were changed earlier. That won't happen on a read-only file system. > also, are there any benefits to doing this, or is the noatime option > good enough? There are certainly benefits. It makes the system a lot more crash resistant. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000825111535.F548>