Date: Mon, 1 Jun 1998 12:16:37 +0400 (MSD) From: bag@sinbin.demos.su (Alex G. Bulushev) To: eivind@yes.no (Eivind Eklund) Cc: sepotvin@videotron.ca, current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... Message-ID: <199806010816.MAA12889@sinbin.demos.su> In-Reply-To: <19980531001525.36883@follo.net> from "Eivind Eklund" at "May 31, 98 00:15:25 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sat, May 30, 1998 at 05:02:14PM -0400, Stephane E. Potvin wrote: > > Maybe this will seems a stupid question but why in the first place would > > someone want to delete a device from a devfs /dev? Or put differently why is > > not devfs append-only so someone would be able to make new links but not able > > to delete existing devices? > > For use in a chroot()'ed environment. there are several problems with dev's in a chroot'ed enviroment, for example a real system (we use it): 1. about 500 chroot'ed "virtual mashines", the /dev containes only necessary devices (tty??) for each VM (created by mknod when VM created) 2. users fs (on main server) with VM (end /dev for each VM) mounted via nfs on several hosts where users realy work (chroot on nfs) 3. each VM can created or deleted while system working on main server and what about future of this scheme with new devfs ideas? mount devfs for each VM on main server and hosts where users work? and unmount devfs on each host before VM deleted? Alex. > > Eivind. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806010816.MAA12889>