Date: Sun, 12 Jan 1997 18:03:59 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: DEVFS permissions &c. Message-ID: <Mutt.19970112180359.j@uriah.heep.sax.de> In-Reply-To: <199701121444.BAA14336@godzilla.zeta.org.au>; from Bruce Evans on Jan 13, 1997 01:44:33 %2B1100 References: <199701121444.BAA14336@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
As Bruce Evans wrote: > >> I've exchanged a couple of thoughts with Bruce about it. Maybe we > >> could teach mtree(8) to help in this step. > > > >Yes, that would certainly be the way to do it. > > Not really. Things it doesn't do right include: > - wildcards. The equivalent of `chmod 666 /dev/tty[pqrs][PQRS]*' is a > huge list. Very simple. Perform your above chmod, and reboot the system. :) I don't suppose the devfs.init mtree description should primarily be maintained manually. > - futures. When a new disk with lots of slices and partitions on it > is detected, how is its mode and group changed so that a member of > group operator can access it? /usr/sbin/sysinstall -diskSetup can do this on behalf of the admin, or if he prefers to run all the disklabel, newfs, and chmods himself, he is free to do so. For the rest, see previous paragraph. ;-) > I expect a tree of devices would be overkill too. You would need evil > symlinks to reduce /dev/disks/raw/scsi/bus0/id0/lun0/slice2/partitionh > to something like /dev/rsd0h :-). This somehow reminds me of SIEMENS/Nixdorf's SINIX system. :) Though i think some ``commonly known'' alias names would come very handy, like /dev/[r]root, /dev/rtape etc. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19970112180359.j>