From owner-freebsd-hackers Thu Apr 20 07:57:50 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA29590 for hackers-outgoing; Thu, 20 Apr 1995 07:57:50 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA29584 for ; Thu, 20 Apr 1995 07:57:35 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id AAA19553; Fri, 21 Apr 1995 00:52:45 +1000 Date: Fri, 21 Apr 1995 00:52:45 +1000 From: Bruce Evans Message-Id: <199504201452.AAA19553@godzilla.zeta.org.au> To: bde@zeta.org.au, peter@bonkers.taronga.com Subject: Re: [DEVFS] your opinions sought! Cc: hackers@FreeBSD.org, julian@freefall.cdrom.com Sender: hackers-owner@FreeBSD.org Precedence: bulk >> > sd0 is the first scsi disk >> > c0t0l0 is the disk at scsi bus 0 target 0 lun 0 >> This would defeat one advantage of devfs - reduction of clutter in /dev. >Why? Only the one you're using would be symlinked into dev. If you're running >an unattended machine you don't want disks drifting to new locations when one >goes down. Always reference c0t0l0 to avoid drift. >> Why decides how h/w/ devices are mapped to ttys? ^^^oops, I meant `Who' >So if your COM2 board goes out you don't find your unattended SLIP connection >trying to talk to your Postscript laser printer and you've got a non-callbacked >getty suddenly talking to your V.34 modem. In an unattended machine the BSD >"device drift" problem is a real concern. Again, always reference an unambiguous device-specific name. I think it would be easier to teach ps (etc.) to handle such names than to map everything to tty* since the mapping would have to be site-specific. Bruce