Forcefully unmounting devfs...

[Poul-Henning Kamp]

In message <20041221232354.GA28374 at 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 at 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.