Date: 18 Sep 2002 11:18:25 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.no-ip.com> To: freebsd-questions@freebsd.org Subject: Re: Monunting /etc read-only was Re: mount read only ... Message-ID: <441y7rxr5q.fsf@be-well.ilk.org> In-Reply-To: <5.1.0.14.0.20020918121808.00be1e30@mail.lusidor.com> References: <5.1.0.14.0.20020917103713.032c3950@mail.lusidor.nu> <5.1.0.14.0.20020917103713.032c3950@mail.lusidor.nu> <5.1.0.14.0.20020918121808.00be1e30@mail.lusidor.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jimmy Lantz <jimmy.lantz@lusidor.com> writes: > ><snip> > > > I'm looking for away to write protect > > > some files whats the pros and cons > > > with having the file on a seperate partition and mount that read-only > > > or use the chflags schg and go to kernel security level 2? > > > >*Either* way you probably want to raise the security level. A > >read-only mount doesn't help if it can be re-mounted writeable. If > >the files *have* to be in the same directory with writeable files (as > >for many systems is true of /etc), schg can be a very good solution. > What in /etc needs to writeable? I was just thinking to mount it read-only. That's perfectly possible; you just have to work on it a bit, especially if you have a large user base. 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?441y7rxr5q.fsf>