Date: Fri, 28 Jul 2000 06:54:36 -0700 (PDT) From: Matthew Jacob <mjacob@feral.com> To: Adrian Chadd <adrian@FreeBSD.ORG> Cc: freebsd-arch@FreeBSD.ORG Subject: Re: How much do we need the all-singing, all-dancing devfs? Message-ID: <Pine.BSF.4.10.10007280644380.60544-100000@beppo.feral.com> In-Reply-To: <20000728123730.C71137@ywing.creative.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> So why not just call make_dev with the wwnXXXXXX as the device name ? > (Assuming that the device nodes exist in /dev, I don't see this as being > a problem even now, and if you wanted to you could make a script to query > the FC controllers in your system and create devices in /dev/ (or /dev/dsk/, > /dev/fc/, whatever you wanted ..) Ummm..... That's a thought- but that requires a devfs so that they'll show up in /dev won't it? Without that, it's also a question of /dev pollution. Again, I think everyone's missing a point here. I can create /dev node called /dev/wwn/XXXXXX or whatever- by doing that it's the same thing as the solaris symlink thing- at the time of creation, this then would have to point to, say, the *current* da instance #. At the next reboot, this is out of date. Tra la. But now that I think about it, if I just beef up camcontrol (and CAM, slightly) to spit out WWWns like it now spits out serial #'s, I could have an rc script do the right thing about (re)making all /dev/wwn/XXXXXs (hells bells- I can even make /dev/wwn an MFS filesystem)). Hmm. Let me think about this! This might be an adequate interim solution that does not require teaching mount about WWNs or Serial#s. It wouldn't work for the root filesystem, but, frankly, all the folks running around asking to boot off their SAN (like was the requirement for the new Solaris FC4 layer coming out just now in 2.8.1 (it was worked on in 1997!) are completely in cloud cukoo land- I mean, ATA drives are just peachy, and if it's a large shop maintenance type problem, netbooting is fine, thank you. Hmm! Thanks! This might have pointes me in the right direction for an interim solution. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10007280644380.60544-100000>