From owner-freebsd-hackers Wed Jun 10 14:03:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15440 for freebsd-hackers-outgoing; Wed, 10 Jun 1998 14:03:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14870 for ; Wed, 10 Jun 1998 14:01:35 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id OAA15845; Wed, 10 Jun 1998 14:01:31 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd015824; Wed Jun 10 14:01:27 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id OAA11432; Wed, 10 Jun 1998 14:01:23 -0700 (MST) From: Terry Lambert Message-Id: <199806102101.OAA11432@usr01.primenet.com> Subject: Re: new config To: dhw@whistle.com (David Wolfskill) Date: Wed, 10 Jun 1998 21:01:23 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199806101806.LAA21481@pau-amma.whistle.com> from "David Wolfskill" at Jun 10, 98 11:06:54 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >My personal opinion is that the device name should map precisely > >and *invariantly* to the controller/target/LUN. That is, that > >what you want to do is technically undesirable. > > Well... here, I'm less certain that saying that what the person who is > using the machine wants to do "is technically undesirable" -- I recall > supporting folks using software that has some bizarre tie-in to a > specific (set of) device name(s). > > Now, granted, I think it's stupid to "design" software like that -- but > not everyone has the luxury of always using software for which the > source is available (and readily mungable). > > Given that, might it be worth considering "an additional level of > indirection"? One possibility, for example, is to symlink a device name > to a controller/target/LUN/slice, for example. Yes, this is similar to > SysV; no, I'm not convinced that it's desirable to go quite as far as > the SysV folks did. I just don't see much to be gained by contracting a > rabid case of NIH. You can get this by renaming and hard-linking in the /dev directory to modify the existing devfs image presented to the user. Basically, you use rc.local (or rc.devfs, if you think a period is a better subdirectory delimiter than a slash, and are dead-set against rc.d because of anti-SysV sentiment). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message