Date: Sun, 11 Mar 2001 20:37:14 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: Matthew Jacob <mjacob@feral.com> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, Dag-Erling Smorgrav <des@ofug.org>, "Niels Chr. Bank-Pedersen" <ncbp@bank-pedersen.dk>, current@FreeBSD.ORG, Greg Lehey <grog@lemis.com> Subject: Re: how's vinum these days with DEVFS? Message-ID: <20010311203714.L18351@fw.wintelcom.net> In-Reply-To: <Pine.LNX.4.21.0103111218150.29879-100000@zeppo.feral.com>; from mjacob@feral.com on Sun, Mar 11, 2001 at 12:19:24PM -0800 References: <20010311121337.J18351@fw.wintelcom.net> <Pine.LNX.4.21.0103111218150.29879-100000@zeppo.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Matthew Jacob <mjacob@feral.com> [010311 12:19] wrote: > On Sun, 11 Mar 2001, Alfred Perlstein wrote: > > > * Poul-Henning Kamp <phk@critter.freebsd.dk> [010311 12:02] wrote: > > > In message <Pine.LNX.4.21.0103111157200.29879-100000@zeppo.feral.com>, Matthew Jacob writes: > > > > > > > >> Lastly make_dev_alias() is undocumented. > > > > > > Right, just like most of the rest of the kernel. > > > > > > >Really? That's a deficiency. It should be. > > > > > > Yes, ideally, yes. > > I've updated the man page. > > > > > The problem with make_dev_alias() not being documented is that it would > > have been an effort to figure out if duplicate make_dev_alias() calls > > were idempotent, done with refcounts or a good way to panic your > > machine. > > ...I'm not following this. Too many dime or more expensive words! What you at? > > > > > There's also no destroy_dev_alias() that I can see. So when vinum > > goes away I didn't realize how one unpopulates the /dev/vinum/ tree. > > The destroy_dev destroys all aliases. Yeah... don't really need that. :) In vinum's case there's a directory /dev/vinum/drive that points to the device backing the vinum device: /dev/vinum % ls -lR total 7 brwx------ 1 root wheel 25, 0x40000001 Sep 26 1999 Control brwx------ 1 root wheel 25, 0x40000002 Sep 26 1999 control brwx------ 1 root wheel 25, 0x40000000 Sep 26 1999 controld drwxr-xr-x 2 root wheel 512 Sep 26 1999 drive drwxr-xr-x 2 root wheel 512 Sep 26 1999 plex drwxr-xr-x 2 root wheel 512 Sep 26 1999 rplex drwxr-xr-x 2 root wheel 512 Sep 26 1999 rsd crwxr-xr-- 1 root wheel 91, 0 Sep 26 1999 rvinum0 drwxr-xr-x 2 root wheel 512 Sep 26 1999 rvol drwxr-xr-x 2 root wheel 512 Sep 26 1999 sd brwxr-xr-- 1 root wheel 25, 0 Sep 26 1999 vinum0 drwxr-xr-x 3 root wheel 512 Sep 26 1999 vol ./drive: total 0 lrwxr-xr-x 1 root wheel 9 Sep 26 1999 vinumdrive0 -> /dev/da1e lrwxr-xr-x 1 root wheel 11 Sep 26 1999 vinumdrive1 -> /dev/da2s1e Ok, now is there a way to get rid of these symlinks when vinum goes away? Ok, if there isn't a way to delete them, what if I unload and reload vinum then try to make them again? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] 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?20010311203714.L18351>