Date: Wed, 22 Dec 2004 00:25:35 +0100 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Kris Kennaway <kris@obsecurity.org> Cc: Scott Long <scottl@freebsd.org> Subject: Re: Forcefully unmounting devfs... Message-ID: <91427.1103671535@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 21 Dec 2004 15:23:54 PST." <20041221232354.GA28374@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20041221232354.GA28374@xor.obsecurity.org>, Kris Kennaway writes: > >--W/nzBZO5zC0uMSeA >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline >Content-Transfer-Encoding: quoted-printable > >On Tue, Dec 21, 2004 at 02:32:34PM -0700, Scott Long wrote: > >> >Either disable forceful unmount of devfs, which makes sense from >> >KISS and many other principles, and then jail wardens will have to >> >find other ways to clean up their jails > >> >The more I think about it, the more I lean towards the first option. >> > >>=20 >> I think that I'd agree here from the point of view of finding an=20 >> expedient way to keep from shooting off feet. > >Unfortunately that's going to cause me a fair amount of pain, unless >there's a simple way to kill all processes running in a given chroot >(NB: I don't currently use jails because a number of ports won't build >in a jail) so I can free up the devfs and then unmount it. But unmounting it forcefully is not guaranteed to clean up your chroot today... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?91427.1103671535>