Date: Sun, 09 Apr 2006 14:43:14 -0500 (CDT) From: Sergey Babkin <babkin@verizon.net> To: Mike Meyer <mwm-keyword-freebsdhackers.102a7e@mired.org>, Scott Long <scottl@samsco.org> Cc: Ceri Davies <ceri@submonkey.net>, hackers@freebsd.org Subject: Re: Re: Using any network interface whatsoever Message-ID: <9399827.1657341144611794358.JavaMail.root@vms070.mailsrvcs.net>
next in thread | raw e-mail | index | archive | help
>From: Mike Meyer >In <443811EF.2020509@samsco.org>, Scott Long <scottl@samsco.org> typed: >> Youre' saying that >> instead of /dev/da0, we should have >> /dev/HITACHI-HUS103073FL3800-SA19-B0T1L0 > >That's a ridiculous extreme. All I advocated was that we be able to >easily identify the devices connected to the system, *not* that we be >able identify every device in the world. Sun solved disk device naming >back in the 80s. I think this is a problem consisting of multiple parts: 1. Identify physical devices and be able to access them. 2. Identify some stable "logical" names by device type, that stay fixed when the configuration changes. 3. Be able to find the mapping easily between these two. 4. Be able to change that mapping. USB is probably the subsystem that has a particular need in this kind of stuff. So, since we have devfs nowadays, why don't we just have multiple names (dev files) for the same device? For example, the same device can be named by driver aha0b0t0d0 and by logical type disk0. The 3rd part can be solved by using symlinks in devfs: i.e. disk0 would be a symlink to aha0b0t0d0, and you can do "ls" and find out what is linked to what. The 4th part can be solved by allowing the sysadmin to create symlinks in devfs. The network driver subsystem would obviously have to be changed to consult devfs for the device names. The next interesting question is how to keep these links persistent between boots. -SB
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9399827.1657341144611794358.JavaMail.root>