From devfsuser@yahoo.com Mon Jan 6 19:21:25 2003 Received: with ECARTIS (v1.0.0; list devfs); Mon, 06 Jan 2003 19:22:00 -0800 (PST) Received: from web14707.mail.yahoo.com (web14707.mail.yahoo.com [216.136.224.124]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h073K23v020427 for ; Mon, 6 Jan 2003 19:21:25 -0800 Message-ID: <20030107032534.35872.qmail@web14707.mail.yahoo.com> Received: from [202.188.158.195] by web14707.mail.yahoo.com via HTTP; Mon, 06 Jan 2003 19:25:34 PST Date: Mon, 6 Jan 2003 19:25:34 -0800 (PST) From: Arindam Dey Subject: Anybody alive To: devfs@oss.sgi.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-archive-position: 61 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: devfsuser@yahoo.com Precedence: bulk X-list: devfs Testing whether the mailing is active also if anybody reads this where are the archives. __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com From lembark@wrkhors.com Mon Jan 6 22:35:55 2003 Received: with ECARTIS (v1.0.0; list devfs); Mon, 06 Jan 2003 22:36:01 -0800 (PST) Received: from getz.wrkhors.com (jeeves.wrkhors.com [207.227.243.17]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h076Y33v022329 for ; Mon, 6 Jan 2003 22:35:55 -0800 Received: from [192.168.200.4] (dizzy.wrkhors.com [192.168.200.4]) by getz.wrkhors.com (8.12.1/8.12.1) with ESMTP id h076QYhm004442 for ; Tue, 7 Jan 2003 00:26:34 -0600 Date: Tue, 07 Jan 2003 00:47:37 -0600 From: Steven Lembark Reply-To: lembark@wrkhors.com To: devfs@oss.sgi.com Subject: Re: Anybody alive Message-ID: <438080000.1041922057@[192.168.200.4]> In-Reply-To: <20030107032534.35872.qmail@web14707.mail.yahoo.com> References: <20030107032534.35872.qmail@web14707.mail.yahoo.com> X-Mailer: Mulberry/3.0.0b10 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-archive-position: 62 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: lembark@wrkhors.com Precedence: bulk X-list: devfs > Testing whether the mailing is active also if anybody reads this where > are the archives. The list is alive, just not much to report on devfs -- which is probably good news since it tends to mean things are stable. Last time I looked the stuff was on kernel.org. -- Steven Lembark 2930 W. Palmer Workhorse Computing Chicago, IL 60647 +1 773 252 1080 From Thomas.Duffy.99@alumni.brown.edu Tue Jan 7 13:36:41 2003 Received: with ECARTIS (v1.0.0; list devfs); Tue, 07 Jan 2003 13:37:14 -0800 (PST) Received: from pheriche.sun.com (pheriche.sun.com [192.18.98.34]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h07LYm3v000393 for ; Tue, 7 Jan 2003 13:36:41 -0800 Received: from engmail1mpk.Eng.Sun.COM ([129.146.1.45]) by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA17033 for ; Tue, 7 Jan 2003 14:40:26 -0700 (MST) Received: from phys-ha1sun-1 (phys-ha1sun-1.Eng.Sun.COM [129.144.135.11]) by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h07LePXq021799 for ; Tue, 7 Jan 2003 13:40:26 -0800 (PST) Received: from biznatch (biznatch.Eng.Sun.COM [129.144.24.170]) by ha1sun-mail1.eng.sun.com (iPlanet Messaging Server 5.2 (built Feb 21 2002)) with ESMTP id <0H8D00LX05JD1E@ha1sun-mail1.eng.sun.com> for devfs@oss.sgi.com; Tue, 07 Jan 2003 13:40:25 -0800 (PST) Date: Tue, 07 Jan 2003 13:40:31 -0800 From: Thomas Duffy Subject: Re: Anybody alive In-reply-to: <438080000.1041922057@[192.168.200.4]> To: devfs@oss.sgi.com Message-id: <1041975631.6493.24.camel@biznatch> Organization: MIME-version: 1.0 X-Mailer: Ximian Evolution 1.2.1 Content-type: text/plain Content-transfer-encoding: 7BIT References: <20030107032534.35872.qmail@web14707.mail.yahoo.com> <438080000.1041922057@[192.168.200.4]> X-archive-position: 63 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: Thomas.Duffy.99@alumni.brown.edu Precedence: bulk X-list: devfs On Mon, 2003-01-06 at 22:47, Steven Lembark wrote: > > Testing whether the mailing is active also if anybody reads this where > > are the archives. > Last time I looked the stuff was on kernel.org. looks like the archives at http://oss.sgi.com/projects/devfs/archive/ are 404. P.S. please fix your sig delimiter > -- ^^ > Steven Lembark 2930 W. Palmer > Workhorse Computing Chicago, IL 60647 > +1 773 252 1080 -- Thomas Duffy From racsw@frontiernet.net Tue Jan 14 07:12:57 2003 Received: with ECARTIS (v1.0.0; list devfs); Tue, 14 Jan 2003 07:13:04 -0800 (PST) Received: from relay01.roc.frontiernet.net (relay01.roc.frontiernet.net [66.133.131.34]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0EFCu3v004237 for ; Tue, 14 Jan 2003 07:12:57 -0800 Received: (qmail 24113 invoked from network); 14 Jan 2003 15:19:00 -0000 Received: from unknown (HELO [192.168.1.100]) ([65.37.13.251]) (envelope-sender ) by relay01.roc.frontiernet.net (FrontierMTA 2.3.2) with SMTP for ; 14 Jan 2003 15:19:00 -0000 Subject: Error on boot and host0 business From: Robert To: Devfs Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Om9aoSjC0xeaprOF6r7F" Organization: Message-Id: <1042557538.2868.6.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.1 Date: 14 Jan 2003 10:18:59 -0500 X-archive-position: 64 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: racsw@frontiernet.net Precedence: bulk X-list: devfs --=-Om9aoSjC0xeaprOF6r7F Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi folks, Two questions. I'm receiving this error on startup, but I'm not sure why or where to look for the problem. Any suggestions? Jan 14 09:00:01 localhost devfsd: Started device management daemon v1.3.25 for /dev=20 Jan 14 09:00:02 localhost devfsd: error calling: symlink in GLOBAL=20 Jan 14 09:00:02 localhost devfsd[65]: error calling: "unlink" in "GLOBAL" Secondly, in /dev, there is the common host0, host1 business. I still haven't figured out the logic for determining the hostx business. Is it something I can visually see on the motherboard, or is it something I can query my system about that will provide the answer? Thanks, --=20 Robert --=-Om9aoSjC0xeaprOF6r7F Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA+JCpiF23RCf3MxjoRAsiwAJ0WAFnzci1457qHLI39ju/XxqKH6wCgkpAy +WJ04QLTKxIeJyEpT59bk4Q= =hcF6 -----END PGP SIGNATURE----- --=-Om9aoSjC0xeaprOF6r7F-- From lembark@wrkhors.com Tue Jan 14 11:57:40 2003 Received: with ECARTIS (v1.0.0; list devfs); Tue, 14 Jan 2003 11:57:45 -0800 (PST) Received: from getz.wrkhors.com (jeeves.wrkhors.com [207.227.243.17]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0EJvd3v015319 for ; Tue, 14 Jan 2003 11:57:40 -0800 Received: from [192.168.200.4] (dizzy.wrkhors.com [192.168.200.4]) by getz.wrkhors.com (8.12.1/8.12.1) with ESMTP id h0EJowhm024041; Tue, 14 Jan 2003 13:50:59 -0600 Date: Tue, 14 Jan 2003 14:12:13 -0600 From: Steven Lembark Reply-To: lembark@wrkhors.com To: Robert , Devfs Subject: Re: Error on boot and host0 business Message-ID: <199790000.1042575133@[192.168.200.4]> In-Reply-To: <1042557538.2868.6.camel@localhost.localdomain> References: <1042557538.2868.6.camel@localhost.localdomain> X-Mailer: Mulberry/3.0.0b10 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-archive-position: 65 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: lembark@wrkhors.com Precedence: bulk X-list: devfs -- Robert > Hi folks, > Two questions. > I'm receiving this error on startup, but I'm not sure why or where to > look for the problem. Any suggestions? > > Jan 14 09:00:01 localhost devfsd: Started device management daemon > v1.3.25 for /dev > Jan 14 09:00:02 localhost devfsd: error calling: symlink in GLOBAL > Jan 14 09:00:02 localhost devfsd[65]: error calling: "unlink" in > "GLOBAL" Bug in your devfsd.comf file. Have you modified/added any entries to it? -- Steven Lembark 2930 W. Palmer Workhorse Computing Chicago, IL 60647 +1 773 252 1080 From racsw@frontiernet.net Tue Jan 14 14:36:34 2003 Received: with ECARTIS (v1.0.0; list devfs); Tue, 14 Jan 2003 14:36:36 -0800 (PST) Received: from relay04.roc.frontiernet.net (relay04.roc.frontiernet.net [66.133.131.37]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0EMaX3v020553 for ; Tue, 14 Jan 2003 14:36:34 -0800 Received: (qmail 5219 invoked from network); 14 Jan 2003 22:42:41 -0000 Received: from unknown (HELO [192.168.1.100]) ([65.37.13.251]) (envelope-sender ) by relay04.roc.frontiernet.net (FrontierMTA 2.3.2) with SMTP for ; 14 Jan 2003 22:42:41 -0000 Subject: Re: Error on boot and host0 business From: Robert To: lembark@wrkhors.com Cc: Devfs In-Reply-To: <199790000.1042575133@[192.168.200.4]> References: <1042557538.2868.6.camel@localhost.localdomain> <199790000.1042575133@[192.168.200.4]> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-t5BnyxAO8vpqK0qnyCEY" Organization: Message-Id: <1042584159.3198.88.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.1 Date: 14 Jan 2003 17:42:40 -0500 X-archive-position: 66 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: racsw@frontiernet.net Precedence: bulk X-list: devfs --=-t5BnyxAO8vpqK0qnyCEY Content-Type: text/plain Content-Transfer-Encoding: quoted-printable > Bug in your devfsd.comf file. Have you modified/added any > entries to it? >=20 Nope, not at all. I had trouble with another issue before, and someone tol= d me that I had to modify this file, but when I looked at it, it was so cryptic = that I knew I didn't understand it well enough, and left it alone. Robert --=-t5BnyxAO8vpqK0qnyCEY Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA+JJJfF23RCf3MxjoRAqAHAJsE7cxvk7PVjpCFSRNmY7RJ94wD8QCeKjOf /zgGOi9uoAaiyQM+dmVwRuY= =xxII -----END PGP SIGNATURE----- --=-t5BnyxAO8vpqK0qnyCEY-- From lembark@wrkhors.com Tue Jan 14 20:37:23 2003 Received: with ECARTIS (v1.0.0; list devfs); Tue, 14 Jan 2003 20:37:26 -0800 (PST) Received: from getz.wrkhors.com (jeeves.wrkhors.com [207.227.243.17]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0F4bM3v027644 for ; Tue, 14 Jan 2003 20:37:23 -0800 Received: from [192.168.200.4] (dizzy.wrkhors.com [192.168.200.4]) by getz.wrkhors.com (8.12.1/8.12.1) with ESMTP id h0F4Ujhm026942; Tue, 14 Jan 2003 22:30:45 -0600 Date: Tue, 14 Jan 2003 22:52:00 -0600 From: Steven Lembark Reply-To: lembark@wrkhors.com To: Robert cc: Devfs Subject: Re: Error on boot and host0 business Message-ID: <71280000.1042606320@[192.168.200.4]> In-Reply-To: <1042584159.3198.88.camel@localhost.localdomain> References: <1042557538.2868.6.camel@localhost.localdomain> <199790000.1042575133@[192.168.200.4]> <1042584159.3198.88.camel@localhost.localdomain> X-Mailer: Mulberry/3.0.0b10 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-archive-position: 67 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: lembark@wrkhors.com Precedence: bulk X-list: devfs -- Robert > >> Bug in your devfsd.comf file. Have you modified/added any >> entries to it? >> > > Nope, not at all. I had trouble with another issue before, and someone > told me that I had to modify this file, but when I looked at it, it was > so cryptic that I knew I didn't understand it well enough, and left it > alone. :-) Less cryptic than it might seem at first glance. Trick is to start from a working example. e.g., here is the entry for my tape drive. "/dev/tapes/tape0/mt" is what I want "/dev/tape" to look like. Paths are relative to /dev/ (or whatever your mount point is). You can LOOKUP a new device, REGISTER the "real" device as the "standard" device or UNREGISTER the device. From there the logic is not all that complicated: LOOKUP ^tape$ CFUNCTION GLOBAL symlink tapes/tape0/mt tape REGISTER ^tapes/tape0/mt$ CFUNCTION GLOBAL symlink tapes/tape0/mt tape UNREGISTER ^tapes/tape0/mt$ CFUNCTION GLOBAL unlink tape Either way, you still have a bug in your devfsd.conf file. -- Steven Lembark 2930 W. Palmer Workhorse Computing Chicago, IL 60647 +1 773 252 1080 From racsw@frontiernet.net Wed Jan 15 13:31:43 2003 Received: with ECARTIS (v1.0.0; list devfs); Wed, 15 Jan 2003 13:31:51 -0800 (PST) Received: from relay02.roc.frontiernet.net (relay02.roc.frontiernet.net [66.133.131.35]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0FLVg3v010429 for ; Wed, 15 Jan 2003 13:31:43 -0800 Received: (qmail 29984 invoked from network); 15 Jan 2003 21:37:52 -0000 Received: from unknown (HELO [192.168.1.100]) ([65.37.13.251]) (envelope-sender ) by relay02.roc.frontiernet.net (FrontierMTA 2.3.2) with SMTP for ; 15 Jan 2003 21:37:52 -0000 Subject: Re: Error on boot and host0 business From: Robert To: lembark@wrkhors.com Cc: Devfs In-Reply-To: <71280000.1042606320@[192.168.200.4]> References: <1042557538.2868.6.camel@localhost.localdomain> <199790000.1042575133@[192.168.200.4]> <1042584159.3198.88.camel@localhost.localdomain> <71280000.1042606320@[192.168.200.4]> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-uHQElfMUQCnE2RfANpbZ" Organization: Message-Id: <1042666670.2853.2.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.1 Date: 15 Jan 2003 16:37:51 -0500 X-archive-position: 68 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: racsw@frontiernet.net Precedence: bulk X-list: devfs --=-uHQElfMUQCnE2RfANpbZ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2003-01-14 at 23:52, Steven Lembark wrote: > -- Robert >=20 > > > >> Bug in your devfsd.comf file. Have you modified/added any > >> entries to it? > >> > > > > Nope, not at all. I had trouble with another issue before, and someone > > told me that I had to modify this file, but when I looked at it, it was > > so cryptic that I knew I didn't understand it well enough, and left it > > alone. >=20 > :-) >=20 >=20 > Less cryptic than it might seem at first glance. Trick > is to start from a working example. e.g., here is the > entry for my tape drive. "/dev/tapes/tape0/mt" is what > I want "/dev/tape" to look like. Paths are relative to > /dev/ (or whatever your mount point is). You can LOOKUP > a new device, REGISTER the "real" device as the "standard" > device or UNREGISTER the device. From there the logic is > not all that complicated: >=20 > LOOKUP ^tape$ CFUNCTION GLOBAL symlink tapes/tape0/mt tape > REGISTER ^tapes/tape0/mt$ CFUNCTION GLOBAL symlink tapes/tape0/mt tape > UNREGISTER ^tapes/tape0/mt$ CFUNCTION GLOBAL unlink tape >=20 >=20 > Either way, you still have a bug in your devfsd.conf file. >=20 > -- > Steven Lembark 2930 W. Palmer > Workhorse Computing Chicago, IL 60647 > +1 773 252 1080 I know I didn't modify anything, but with your information, let me look that file over and get back to you. Thanks for helping out, regardless. --=20 Robert --=-uHQElfMUQCnE2RfANpbZ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA+JdSuF23RCf3MxjoRAu2oAKDA9NYFG/Nn6OnP8g4n1/LwJdpiuACfWWKq qGub3xjfatKVP4xTPBriCW8= =ho1W -----END PGP SIGNATURE----- --=-uHQElfMUQCnE2RfANpbZ-- From brettholcomb@charter.net Wed Jan 15 15:00:30 2003 Received: with ECARTIS (v1.0.0; list devfs); Wed, 15 Jan 2003 15:00:33 -0800 (PST) Received: from dc-mx12.cluster1.charter.net (dc-mx12.cluster1.charter.net [209.225.8.22]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0FN0T3v022008 for ; Wed, 15 Jan 2003 15:00:30 -0800 Received: from [68.115.236.214] (HELO strider) by dc-mx12.cluster1.charter.net (CommuniGate Pro SMTP 3.5.9) with SMTP id 68920556 for devfs@oss.sgi.com; Wed, 15 Jan 2003 18:06:36 -0500 Date: Wed, 15 Jan 2003 18:09:43 -0500 From: "Brett I. Holcomb" To: devfs@oss.sgi.com Subject: SCSI Tapes and devfs Message-Id: <20030115180943.1bc7048e.brettholcomb@charter.net> Organization: Holcomb & Associates X-Mailer: Sylpheed version 0.8.6claws (GTK+ 1.2.10; ) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-archive-position: 69 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs I am new to devfs - it came with the Gentoo distribution of Linux I am now using. I have a Cybernetics 15 slot tape library with drive that has worked successfully on other distros. I'm really confused with devfs. I spent yesterday reading docs and working with devfs to get the thing working and kind of succeded - once. When I started the system I had no /dev/st - just /dev/sg, sd, sr. Sometime during the afternoon I did an ls /dev/st again and there was the st directory. Using mt I managed to test communciations and could talk to the tape drive under /dev/st. How or why the /dev/st suddenly appeared I have no idea. I shutdown the system and when I rebooted - no /dev/st anymore! My original kernel was built with SCSI support built in as I have an entirely SCSI system and did not want to mess with initrd. I could not get /dev/st to show up again. At that point I decided to build st support as a module and autoload it. Did that and there was /dev/st with my tape devices! At this point I'm confused. My understanding of devfs is that upon startup (Gentoo boots with devfs running) devfs will find the devices and create the necessary directories under /dev/. The devices ARE in /proc/scsi/scsi. I can see that the module loading will cause devfs to see a device added and create the directories. But why didn't devfs see the devices when st support was built into the kernel?? Do I have to manually edit /etc/devfsd.conf to tell it to find my tape and autochanger? I thought that devfs would find them by itself. I've read man pages, the FAQ at the devfs author's site and asked on the Gentoo and other Linux newsgroups but am still confused. In fact the deafing silence on the mailing lists and newsgroups shows me not many people understand devfs or so it appears. Any help in unconfusing me would be appreciated. Thank you. -- Brett I. Holcomb From Andrey.Borzenkov@siemens.com Thu Jan 16 07:56:26 2003 Received: with ECARTIS (v1.0.0; list devfs); Thu, 16 Jan 2003 07:56:29 -0800 (PST) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0GFuO3v001818 for ; Thu, 16 Jan 2003 07:56:25 -0800 Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.11.6/8.11.6) with ESMTP id h0GG2c429699; Thu, 16 Jan 2003 17:02:38 +0100 (MET) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id h0GG2bV18416; Thu, 16 Jan 2003 17:02:37 +0100 (MET) Received: by MOWD019A with Internet Mail Service (5.5.2653.19) id ; Thu, 16 Jan 2003 19:16:38 +0300 Received: from mw2b210c (163.242.193.12 [163.242.193.12]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id DATB5KMR; Thu, 16 Jan 2003 19:16:33 +0300 From: Borzenkov Andrey To: "'Robert'" , "'Devfs'" Subject: RE: Error on boot and host0 business Date: Thu, 16 Jan 2003 19:02:26 +0300 Message-ID: <6134254DE87BD411908B00A0C99B044F03A0B5D8@MOWD019A> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: <1042557538.2868.6.camel@localhost.localdomain> Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h0GFuO3v001818 X-archive-position: 70 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: Andrey.Borzenkov@siemens.com Precedence: bulk X-list: devfs [...]> > Secondly, in /dev, there is the common host0, host1 business. /dev/ide or /dev/scsi? I still > haven't figured out the logic for determining the hostx business. Is it > something I can visually see on the motherboard, or is it something I > can query my system about that will provide the answer? > Not likely. Both for IDE and SCSI system enumerates adapters and assigns them numbers, this happens dynamically. These are the numbers you get in /dev/ide/hostN or /dev/scsi/hostN. For IDE the system reserves first two entries for bootable IDE controllers which usually means "controller on motherboard" unless you have configured your system with CONFIG_BLK_DEV_OFFBOARD in which case also PCI cards may be bootable. So your first onboard controller is host0 and next PCI is host2. But if you happen to have bootable PCI controller it may well be host0. For SCSI it is just the order SCSI hosts are enumerated which depends on order in which modules for particular hardware is loaded. First found SCSI controller gets 0, next 1 etc. For IDE you can assign host number by using ideN=ports and for SCSI by using scshosts=driver1,driver2,... but you have no easy way to specify relative order of hosts sharing the same driver. In general physical<->logical device numbers in Linux sucks. Even Solaris manages it better in most respects. Hopefully it will change in 2.5 with devicefs. -andrey From marton.kadar@mail.com Thu Jan 16 08:08:01 2003 Received: with ECARTIS (v1.0.0; list devfs); Thu, 16 Jan 2003 08:08:04 -0800 (PST) Received: from spf1.us.outblaze.com (205-158-62-139.outblaze.com [205.158.62.139]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0GG803v001944 for ; Thu, 16 Jan 2003 08:08:01 -0800 Received: (qmail 21427 invoked from network); 16 Jan 2003 16:14:09 -0000 Received: from unknown (205.158.62.68) by spf1.us.outblaze.com with QMQP; 16 Jan 2003 16:14:09 -0000 Received: (qmail 34026 invoked from network); 16 Jan 2003 16:14:05 -0000 Received: from unknown (HELO ws1-9.us4.outblaze.com) (205.158.62.37) by 205-158-62-153.outblaze.com with SMTP; 16 Jan 2003 16:14:05 -0000 Received: (qmail 36136 invoked by uid 1001); 16 Jan 2003 16:14:05 -0000 Message-ID: <20030116161405.36135.qmail@mail.com> Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Mailer: MIME-tools 5.41 (Entity 5.404) Received: from [193.68.46.75] by ws1-9.us4.outblaze.com with http for marton.kadar@mail.com; Fri, 17 Jan 2003 00:14:05 +0800 From: "Marton Kadar" To: "Brett I. Holcomb" Cc: devfs@oss.sgi.com Date: Fri, 17 Jan 2003 00:14:05 +0800 Subject: Re: SCSI Tapes and devfs X-Originating-Ip: 193.68.46.75 X-Originating-Server: ws1-9.us4.outblaze.com X-archive-position: 71 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: marton.kadar@mail.com Precedence: bulk X-list: devfs Hi, I understand your confusion, but if you think about it there are some possibilities that could explain it, like: - some little bug in st support makes it behave differently if compiled in the kernel vs. as a module - Gentoo devfsd.conf not properly set up for st module loading - Your newly compiled kernel is not the same version as the one installed by your distro, and some bugfix occurred... ...whatever... things aren't perfect. You didn't phrase things very clearly, and you should be aware that it is possible to have SCSI support without SCSI tape support, so your SCSI host adapter will enumerate the device, but you have no driver for it in the kernel, so you can see it in /proc but not in /dev. At this moment, (noting that I know NOTHING about tape drives or Gentoo, and that you omitted many important bits from your message) the most likely to me seems that your previous kernel did have SCSI disk, cd-rom and generic support compiled in, but tape support only as a module, and the module was not loaded on bootup, only later by some script, which might not be perfect. You should note that if you do an 'ls /dev/*' it does not specifically ask for entry /dev/st#, therefore a LOOKUP event does not occur, and devfsd does not load the module. If you do 'ls /dev/st#' specifically, then you do get the module loaded. (as much as I understand) Hope the above is of some help, Marton BTW, devfs is way cool. Is there anyone though who can help me understand what sysfs, procfs, devfs and driverfs are intended for and what are the overlaps/differences between them? ----- Original Message ----- From: "Brett I. Holcomb" Date: Wed, 15 Jan 2003 18:09:43 -0500 To: devfs@oss.sgi.com Subject: SCSI Tapes and devfs > I am new to devfs - it came with the Gentoo distribution of Linux I am > now using. I have a Cybernetics 15 slot tape library with drive that > has worked successfully on other distros. I'm really confused with > devfs. > > I spent yesterday reading docs and working with devfs to get the thing > working and kind of succeded - once. When I started the system I had no > /dev/st - just /dev/sg, sd, sr. Sometime during the afternoon I did an > ls /dev/st again and there was the st directory. Using mt I managed to > test communciations and could talk to the tape drive under /dev/st. How > or why the /dev/st suddenly appeared I have no idea. > > I shutdown the system and when I rebooted - no /dev/st anymore! My > original kernel was built with SCSI support built in as I have an > entirely SCSI system and did not want to mess with initrd. I could not > get /dev/st to show up again. > > At that point I decided to build st support as a module and autoload it. > Did that and there was /dev/st with my tape devices! > > At this point I'm confused. My understanding of devfs is that upon > startup (Gentoo boots with devfs running) devfs will find the devices > and create the necessary directories under /dev/. The devices ARE in > /proc/scsi/scsi. I can see that the module loading will cause devfs to > see a device added and create the directories. But why didn't devfs see > the devices when st support was built into the kernel?? > > Do I have to manually edit /etc/devfsd.conf to tell it to find my tape > and autochanger? I thought that devfs would find them by itself. > > I've read man pages, the FAQ at the devfs author's site and asked on the > Gentoo and other Linux newsgroups but am still confused. In fact the > deafing silence on the mailing lists and newsgroups shows me not many > people understand devfs or so it appears. Any help in unconfusing me > would be appreciated. > > Thank you. > > > > > -- > > Brett I. Holcomb > > -- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup Meet Singles http://corp.mail.com/lavalife From Andrey.Borzenkov@siemens.com Thu Jan 16 08:27:43 2003 Received: with ECARTIS (v1.0.0; list devfs); Thu, 16 Jan 2003 08:27:47 -0800 (PST) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0GGRf3v003120 for ; Thu, 16 Jan 2003 08:27:42 -0800 Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.11.6/8.11.6) with ESMTP id h0GGXu415209; Thu, 16 Jan 2003 17:33:56 +0100 (MET) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id h0GGXuV09976; Thu, 16 Jan 2003 17:33:56 +0100 (MET) Received: by MOWD019A with Internet Mail Service (5.5.2653.19) id ; Thu, 16 Jan 2003 19:47:57 +0300 Received: from mw2b210c (163.242.193.12 [163.242.193.12]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id DATB5LWY; Thu, 16 Jan 2003 19:47:54 +0300 From: Borzenkov Andrey To: "'Brett I. Holcomb'" , devfs@oss.sgi.com Subject: RE: SCSI Tapes and devfs Date: Thu, 16 Jan 2003 19:33:47 +0300 Message-ID: <6134254DE87BD411908B00A0C99B044F03A0B5D9@MOWD019A> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: <20030115180943.1bc7048e.brettholcomb@charter.net> Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h0GGRf3v003120 X-archive-position: 72 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: Andrey.Borzenkov@siemens.com Precedence: bulk X-list: devfs > > I am new to devfs - it came with the Gentoo distribution of Linux I am > now using. I have a Cybernetics 15 slot tape library with drive that > has worked successfully on other distros. I'm really confused with > devfs. > > I spent yesterday reading docs and working with devfs to get the thing > working and kind of succeded - once. When I started the system I had no > /dev/st - just /dev/sg, sd, sr. Sometime during the afternoon I did an > ls /dev/st again and there was the st directory. Using mt I managed to > test communciations and could talk to the tape drive under /dev/st. How > or why the /dev/st suddenly appeared I have no idea. > > I shutdown the system and when I rebooted - no /dev/st anymore! My > original kernel was built with SCSI support built in as I have an > entirely SCSI system and did not want to mess with initrd. I could not > get /dev/st to show up again. > > At that point I decided to build st support as a module and autoload it. > Did that and there was /dev/st with my tape devices! > /dev/st are just compatibility names. Do you have /dev/scsi/hostX/busY/targetZ/lunW/mt* for your device? > At this point I'm confused. My understanding of devfs is that upon > startup (Gentoo boots with devfs running) devfs will find the devices > and create the necessary directories under /dev/. No. Devfs does not find any device. Devfs is just a repository where drivers can register devices they have found or created. The devices ARE in > /proc/scsi/scsi. Which does not mean driver has told devfs anything about it. I can see that the module loading will cause devfs to > see a device added and create the directories. But why didn't devfs see > the devices when st support was built into the kernel?? > because something went differently and driver did not tell devfs about existence of this tape. Besides the process has more than one step. Drivers usually register canonical names that are selected to be hierarchical to avoid possible confusion. The names you are talking about (specifically, /dev/st directory) are created by devfsd program. So the reason why you did not see /dev/st may be also devfsd malfunction. > Do I have to manually edit /etc/devfsd.conf to tell it to find my tape > and autochanger? Usually not. I thought that devfs would find them by itself. > Devfs does not find anything. It is very dumb. It sits there and waits until somebody tells it "hey, I have SCSI tape, please show it to user now". > I've read man pages, the FAQ at the devfs author's site and asked on the > Gentoo and other Linux newsgroups but am still confused. In fact the > deafing silence on the mailing lists and newsgroups shows me not many > people understand devfs or so it appears. I guess silence means Devfs works as expected :))) Any help in unconfusing me > would be appreciated. > Please show /etc/devfsd.conf, /etc/modules.devfs, explain how and when devfsd is loaded in Gentoo and show dmesg output for the case /dev/st does not appear. -andrey From brettholcomb@charter.net Thu Jan 16 09:50:35 2003 Received: with ECARTIS (v1.0.0; list devfs); Thu, 16 Jan 2003 09:50:38 -0800 (PST) Received: from dc-mxdb04.cluster1.charter.net (dc-mxdb04.cluster1.charter.net [209.225.8.79]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0GHoX3v004414 for ; Thu, 16 Jan 2003 09:50:34 -0800 Received: from [158.158.240.230] (account ) by dc-mxdb04.cluster1.charter.net (CommuniGate Pro WebUser 3.5.9b) with HTTP id 1837187 for ; Thu, 16 Jan 2003 12:56:44 -0500 From: "brett holcomb" Subject: Re: SCSI Tapes and devfs To: devfs@oss.sgi.com X-Mailer: CommuniGate Pro Web Mailer v.3.5.9b Date: Thu, 16 Jan 2003 12:56:44 -0500 Message-ID: In-Reply-To: <6134254DE87BD411908B00A0C99B044F03A0B5D9@MOWD019A> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format="flowed" Content-Transfer-Encoding: 8bit X-archive-position: 73 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs Okay. Thank you for the explanations. Things are a little clearer now. More comments inline. On Thu, 16 Jan 2003 19:33:47 +0300 Borzenkov Andrey wrote: > >> >> At that point I decided to build st support as a module >>and autoload it. >> Did that and there was /dev/st with my tape devices! >> > >/dev/st are just compatibility names. Do you have >/dev/scsi/hostX/busY/targetZ/lunW/mt* for your device? Not that I remember. >> At this point I'm confused. My understanding of devfs >>is that upon >> startup (Gentoo boots with devfs running) devfs will >>find the devices >> and create the necessary directories under /dev/. > >No. Devfs does not find any device. Devfs is just a >repository where drivers >can register devices they have found or created. Okay - the light is starting to dawn. Something has to trigger devfs into seeing the device. I assume that can be a module loading (such as I did with st in the current system) or by some other means - whatever that is? >will cause devfs to >> see a device added and create the directories. But why >>didn't devfs see >> the devices when st support was built into the kernel?? >> > >because something went differently and driver did not >tell devfs about >existence of this tape. That's what I thought. >Besides the process has more than one step. Drivers >usually register >canonical names that are selected to be hierarchical to >avoid possible >confusion. The names you are talking about (specifically, >/dev/st directory) >are created by devfsd program. So the reason why you did >not see /dev/st may >be also devfsd malfunction. > >> Do I have to manually edit /etc/devfsd.conf to tell it >>to find my tape >> and autochanger? > >Usually not. > > I thought that devfs would >find them by itself. >> > >Devfs does not find anything. It is very dumb. It sits >there and waits until >somebody tells it "hey, I have SCSI tape, please show it >to user now". Okay, then what is supposed to tell devfs that there is now a scsi tape drive/changer ready to use. In the case of st being a module and me loading it at startup time causes devfs to see it. But what SHOULD trigger this if the st support is built into a kernel - what is the mechanism there for Linux? >> I've read man pages, the FAQ at the devfs author's site >>and asked on the >> Gentoo and other Linux newsgroups but am still confused. >> In fact the >> deafing silence on the mailing lists and newsgroups >>shows me not many >> people understand devfs or so it appears. > >I guess silence means Devfs works as expected :))) As long as you don't try and do what I'm doing . I think devfs is a neat concept and from what I've read has a lot of advantages although my knowledge of devices under Linux has been limited to createing entries in /dev under the old system and making that work. I don't know what distros use it (not Caldera's old WS 3.1 or RH 7.3) so maybe most of the people I see aren't running distros with it. > Any help >in unconfusing me >> would be appreciated. >> > > >Please show /etc/devfsd.conf, /etc/modules.devfs, explain >how and when >devfsd is loaded in Gentoo and show dmesg output for the >case /dev/st does >not appear. I'll get them when I get back to the machine. I'll create a kernel with st in the kernel and get that data. Thank you. From marton.kadar@mail.com Thu Jan 16 10:11:42 2003 Received: with ECARTIS (v1.0.0; list devfs); Thu, 16 Jan 2003 10:11:48 -0800 (PST) Received: from spf1.us.outblaze.com (205-158-62-139.outblaze.com [205.158.62.139]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0GIBe3v004749 for ; Thu, 16 Jan 2003 10:11:42 -0800 Received: (qmail 27872 invoked from network); 16 Jan 2003 18:17:51 -0000 Received: from unknown (205.158.62.68) by spf1.us.outblaze.com with QMQP; 16 Jan 2003 18:17:51 -0000 Received: (qmail 77073 invoked from network); 16 Jan 2003 18:17:49 -0000 Received: from unknown (HELO ws1-7.us4.outblaze.com) (205.158.62.57) by 205-158-62-153.outblaze.com with SMTP; 16 Jan 2003 18:17:49 -0000 Received: (qmail 53542 invoked by uid 1001); 16 Jan 2003 18:17:47 -0000 Message-ID: <20030116181747.53541.qmail@mail.com> Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Mailer: MIME-tools 5.41 (Entity 5.404) Received: from [193.68.46.75] by ws1-7.us4.outblaze.com with http for marton.kadar@mail.com; Fri, 17 Jan 2003 02:17:47 +0800 From: "Marton Kadar" To: racsw@frontiernet.net Cc: devfs@oss.sgi.com Date: Fri, 17 Jan 2003 02:17:47 +0800 Subject: Re: Error on boot and host0 business X-Originating-Ip: 193.68.46.75 X-Originating-Server: ws1-7.us4.outblaze.com X-archive-position: 74 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: marton.kadar@mail.com Precedence: bulk X-list: devfs Just a wild idea... what kernel are you using? Is this a problem you always had or something new? I had the idea that the thread on this list started by David Fokkema on the 17th of December might be related to your problem. At the end of the thread David reported that kernel 2.4.20 solved his problem of not being able to refer to the disc0 device link as root device, only the ide/host0/.../... full specification. In 2.4.18 only the full path can be specified, but in 2.4.20 the simplified name could be used too. I haven't seen 2.4.20 yet so can't tell, but it is possible that the simplified symlink is not behaving exactly the way it used to and this way the symlink and unlink actions of devfsd will fail. Again, this was just a wild idea. Ignore it if you want to. Marton ----- Original Message ----- > > > > > > Less cryptic than it might seem at first glance. Trick > > is to start from a working example. e.g., here is the > > entry for my tape drive. "/dev/tapes/tape0/mt" is what > > I want "/dev/tape" to look like. Paths are relative to > > /dev/ (or whatever your mount point is). You can LOOKUP > > a new device, REGISTER the "real" device as the "standard" > > device or UNREGISTER the device. From there the logic is > > not all that complicated: > > > > LOOKUP ^tape$ CFUNCTION GLOBAL symlink tapes/tape0/mt tape > > REGISTER ^tapes/tape0/mt$ CFUNCTION GLOBAL symlink tapes/tape0/mt tape > > UNREGISTER ^tapes/tape0/mt$ CFUNCTION GLOBAL unlink tape > > > > > > Either way, you still have a bug in your devfsd.conf file. > > > > -- > > Steven Lembark 2930 W. Palmer > > Workhorse Computing Chicago, IL 60647 > > +1 773 252 1080 > > I know I didn't modify anything, but with your information, let me look > that file over and get back to you. Thanks for helping out, regardless. > > -- > Robert -- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup Meet Singles http://corp.mail.com/lavalife From brettholcomb@charter.net Thu Jan 16 10:29:46 2003 Received: with ECARTIS (v1.0.0; list devfs); Thu, 16 Jan 2003 10:29:48 -0800 (PST) Received: from dc-mxdb03.cluster1.charter.net (dc-mxdb03.cluster1.charter.net [209.225.8.78]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0GITi3v004836 for ; Thu, 16 Jan 2003 10:29:45 -0800 Received: from [158.158.240.230] (account ) by dc-mxdb03.cluster1.charter.net (CommuniGate Pro WebUser 3.5.9) with HTTP id 1727129 for ; Thu, 16 Jan 2003 13:35:55 -0500 From: "brett holcomb" Subject: Re: SCSI Tapes and devfs To: devfs@oss.sgi.com X-Mailer: CommuniGate Pro Web Mailer v.3.5.9 Date: Thu, 16 Jan 2003 13:35:55 -0500 Message-ID: In-Reply-To: <6134254DE87BD411908B00A0C99B044F03A0B5D9@MOWD019A> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format="flowed" Content-Transfer-Encoding: 8bit X-archive-position: 75 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs Gentoo starts with devfs running. We have to check the boot mount option yes in the kernel config. On Thu, 16 Jan 2003 19:33:47 +0300 Borzenkov Andrey wrote: > >Please show /etc/devfsd.conf, /etc/modules.devfs, explain >how and when >devfsd is loaded in Gentoo and show dmesg output for the >case /dev/st does >not appear. > >-andrey From racsw@frontiernet.net Thu Jan 16 17:46:36 2003 Received: with ECARTIS (v1.0.0; list devfs); Thu, 16 Jan 2003 17:46:39 -0800 (PST) Received: from relay03.roc.frontiernet.net (relay03.roc.frontiernet.net [66.133.131.36]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0H1kY3v010386 for ; Thu, 16 Jan 2003 17:46:35 -0800 Received: (qmail 26815 invoked from network); 17 Jan 2003 01:52:49 -0000 Received: from unknown (HELO [192.168.1.100]) ([65.37.13.251]) (envelope-sender ) by relay03.roc.frontiernet.net (FrontierMTA 2.3.2) with SMTP for ; 17 Jan 2003 01:52:49 -0000 Subject: RE: Error on boot and host0 business From: Robert To: Borzenkov Andrey Cc: Devfs In-Reply-To: <6134254DE87BD411908B00A0C99B044F03A0B5D8@MOWD019A> References: <6134254DE87BD411908B00A0C99B044F03A0B5D8@MOWD019A> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-UVotKypNhHHgZ2OwUWbl" Organization: Message-Id: <1042768348.3127.20.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.1 Date: 16 Jan 2003 20:52:28 -0500 X-archive-position: 76 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: racsw@frontiernet.net Precedence: bulk X-list: devfs --=-UVotKypNhHHgZ2OwUWbl Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Truthfully, I'm not, nor have ever been a hardware guy, only software. That's why I asked if there's something specific I can see, count, etc to determine whether something belongs to host0, host1 or host2. I'm just confused, that's all. This all started because I was trying to help a guy install his internal zip drive. I have one also, and devfs screwed up my system, so I had to pund the books until I finally found a workaround by creating the necessary directories and block devices. It was quite an experience. He had host0 and host2 on his system, and I couldn't figure out where to put the block device on his system. We both finally gave up, I think. Anyhow, thanks for the information, and BTW, it's for IDE Robert On Thu, 2003-01-16 at 11:02, Borzenkov Andrey wrote: > [...]>=20 > > Secondly, in /dev, there is the common host0, host1 business.=20 >=20 > /dev/ide or /dev/scsi? >=20 > I still > > haven't figured out the logic for determining the hostx business. Is i= t > > something I can visually see on the motherboard, or is it something I > > can query my system about that will provide the answer? > >=20 >=20 > Not likely. Both for IDE and SCSI system enumerates adapters and assigns > them numbers, this happens dynamically. These are the numbers you get in > /dev/ide/hostN or /dev/scsi/hostN. >=20 > For IDE the system reserves first two entries for bootable IDE controller= s > which usually means "controller on motherboard" unless you have configure= d > your system with CONFIG_BLK_DEV_OFFBOARD in which case also PCI cards may= be > bootable. So your first onboard controller is host0 and next PCI is host2= .. > But if you happen to have bootable PCI controller it may well be host0. >=20 > For SCSI it is just the order SCSI hosts are enumerated which depends on > order in which modules for particular hardware is loaded. First found SCS= I > controller gets 0, next 1 etc. >=20 > For IDE you can assign host number by using ideN=3Dports and for SCSI by = using > scshosts=3Ddriver1,driver2,... but you have no easy way to specify relati= ve > order of hosts sharing the same driver. >=20 > In general physical<->logical device numbers in Linux sucks. Even Solaris > manages it better in most respects. Hopefully it will change in 2.5 with > devicefs. >=20 > -andrey --=20 Robert --=-UVotKypNhHHgZ2OwUWbl Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA+J2HcF23RCf3MxjoRAsTiAJ9megScA96IzbNM7m2Y2S2oIt8ITgCgpptl t+/dp+Ar0AAbrjE268CeWKY= =dn4M -----END PGP SIGNATURE----- --=-UVotKypNhHHgZ2OwUWbl-- From racsw@frontiernet.net Thu Jan 16 17:49:23 2003 Received: with ECARTIS (v1.0.0; list devfs); Thu, 16 Jan 2003 17:49:26 -0800 (PST) Received: from relay04.roc.frontiernet.net (relay04.roc.frontiernet.net [66.133.131.37]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0H1nL3v010464 for ; Thu, 16 Jan 2003 17:49:23 -0800 Received: (qmail 6968 invoked from network); 17 Jan 2003 01:55:37 -0000 Received: from unknown (HELO [192.168.1.100]) ([65.37.13.251]) (envelope-sender ) by relay04.roc.frontiernet.net (FrontierMTA 2.3.2) with SMTP for ; 17 Jan 2003 01:55:37 -0000 Subject: Re: Error on boot and host0 business From: Robert To: Marton Kadar Cc: Devfs In-Reply-To: <20030116181747.53541.qmail@mail.com> References: <20030116181747.53541.qmail@mail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-aJVFWL+hJlPE+EqsK5Wc" Organization: Message-Id: <1042768523.3128.24.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.1 Date: 16 Jan 2003 20:55:23 -0500 X-archive-position: 77 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: racsw@frontiernet.net Precedence: bulk X-list: devfs --=-aJVFWL+hJlPE+EqsK5Wc Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I never ignore any advice ;-) My kernel is 2.4.18-8.1 I downloaded 2.4.20 a few days ago, but haven't had time to install it. I might as well do it and see if your idea pans out. Thanks, Robert On Thu, 2003-01-16 at 13:17, Marton Kadar wrote: > Just a wild idea... what kernel are you using? > Is this a problem you always had or something new? > I had the idea that the thread on this list started > by David Fokkema on the 17th of December might be > related to your problem. > At the end of the thread David reported that kernel > 2.4.20 solved his problem of not being able to refer > to the disc0 device link as root device, only the > ide/host0/.../... full specification. In 2.4.18 > only the full path can be specified, but in 2.4.20 > the simplified name could be used too. > I haven't seen 2.4.20 yet so can't tell, but it is > possible that the simplified symlink is not behaving > exactly the way it used to and this way the symlink > and unlink actions of devfsd will fail. > Again, this was just a wild idea. > Ignore it if you want to. >=20 > Marton > ----- Original Message ----- > > >=20 > > >=20 > > > Less cryptic than it might seem at first glance. Trick > > > is to start from a working example. e.g., here is the > > > entry for my tape drive. "/dev/tapes/tape0/mt" is what > > > I want "/dev/tape" to look like. Paths are relative to > > > /dev/ (or whatever your mount point is). You can LOOKUP > > > a new device, REGISTER the "real" device as the "standard" > > > device or UNREGISTER the device. From there the logic is > > > not all that complicated: > > >=20 > > > LOOKUP ^tape$ CFUNCTION GLOBAL symlink tapes/tape0/mt tape > > > REGISTER ^tapes/tape0/mt$ CFUNCTION GLOBAL symlink tapes/tape0/mt tap= e > > > UNREGISTER ^tapes/tape0/mt$ CFUNCTION GLOBAL unlink tape > > >=20 > > >=20 > > > Either way, you still have a bug in your devfsd.conf file. > > >=20 > > > -- > > > Steven Lembark 2930 W. Palmer > > > Workhorse Computing Chicago, IL 60647 > > > +1 773 252 1080 > >=20 > > I know I didn't modify anything, but with your information, let me look > > that file over and get back to you. Thanks for helping out, regardless= .. > >=20 > > --=20 > > Robert --=20 Robert --=-aJVFWL+hJlPE+EqsK5Wc Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA+J2KKF23RCf3MxjoRAlv3AJ9TGjrv9SG6r8UY5kW1SMkH7gT+HwCfXXxs 0l+W2HBUWCIIifg0YGqZKq8= =c48G -----END PGP SIGNATURE----- --=-aJVFWL+hJlPE+EqsK5Wc-- From brettholcomb@charter.net Thu Jan 16 18:09:26 2003 Received: with ECARTIS (v1.0.0; list devfs); Thu, 16 Jan 2003 18:09:28 -0800 (PST) Received: from dc-mx10.cluster1.charter.net (dc-mx10.cluster1.charter.net [209.225.8.20]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0H29P3v011110 for ; Thu, 16 Jan 2003 18:09:26 -0800 Received: from [68.115.236.214] (HELO strider) by dc-mx10.cluster1.charter.net (CommuniGate Pro SMTP 3.5.9) with SMTP id 55090364 for devfs@oss.sgi.com; Thu, 16 Jan 2003 20:55:31 -0500 Date: Thu, 16 Jan 2003 20:58:35 -0500 From: "Brett I. Holcomb" To: devfs@oss.sgi.com Subject: Re: SCSI Tapes and devfs Message-Id: <20030116205835.2993b742.brettholcomb@charter.net> In-Reply-To: <6134254DE87BD411908B00A0C99B044F03A0B5D9@MOWD019A> References: <20030115180943.1bc7048e.brettholcomb@charter.net> <6134254DE87BD411908B00A0C99B044F03A0B5D9@MOWD019A> Organization: Holcomb & Associates X-Mailer: Sylpheed version 0.8.6claws (GTK+ 1.2.10; ) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-archive-position: 78 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs Thank you for your help. I've included the requested information and an update below. On Thu, 16 Jan 2003 19:33:47 +0300 Borzenkov Andrey wrote: > > Please show /etc/devfsd.conf, /etc/modules.devfs, explain how and when > devfsd is loaded in Gentoo and show dmesg output for the case /dev/st > does not appear. Gentoo is a distro that uses a superset of the BDS ports system instead of rpms. It has to have devfs and boots with it - I have to select the option in menuconfig to include devfs and boot with it when building a kernel or it warns me that it's not there. From this I conclude devfs is started during the boot. Okay, I set out to do build a kernel that would show the case where /dev/st did not appear. The system I was on had the kernel built with st as a module. I then built another kernel with NO modules for st (sg is built in also). This time it found them all (dmesg excerpt below). I must have messed something up on the kernel I built before with st and sg built in. Let me work with this kernelfor a while and see what happens. Now, where does /etc/modules.conf fit into the devfs scheme - what is it used for? I thought that was only for modules yet it's included in /etc/modules.devfs? If I create some symlinks such as ln -s /dev/tape0 /dev/st/c1b0t0u0m0 ln -s /dev/tape0 /dev/st/c1b0t0u0m0n ls -s /dev/sg/dev/auto_changer0 /dev/sg/c1b0t1u0 do I have to do anything to make them be restored on the next system reboot? According to my /etc/devfsd.conf (see below) it should, if I understand it, copy all the devices and restore them next time - correct? And when do I modify /etc/devfsd.conf - or do I ever. I understand I need to modify it for the cdrw but what else would I have to do with it as it seems setup to cover everything necessary? I'm including /etc/devfsd.conf, /etc/modules.devfs, and a portion of dmesg. ****** My /etc/devfsd.conf # Sample /etc/devfsd.conf configuration file. # Richard Gooch 3-JUL-2000 # # The Gentoo Linux Team - http://www.gentoo.org/ # - Many fixes, etc # # $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/devfsd.conf,v 1.13 2002/12/01 08:52:55 azarah Exp $ # Enable full compatibility mode for old device names. You may comment these # out if you don't use the old device names. Make sure you know what you're # doing! REGISTER .* MKOLDCOMPAT UNREGISTER .* RMOLDCOMPAT # You may comment out the above and uncomment the following if you've # configured your system to use the original "new" devfs names or the really # new names #REGISTER vc/.* MKOLDCOMPAT #UNREGISTER vc/.* RMOLDCOMPAT #REGISTER pty/.* MKOLDCOMPAT #UNREGISTER pty/.* RMOLDCOMPAT #REGISTER misc MKOLDCOMPAT #UNREGISTER misc RMOLDCOMPAT # You may comment these out if you don't use the original "new" names REGISTER .* MKNEWCOMPAT UNREGISTER .* RMNEWCOMPAT # Enable module autoloading. You may comment this out if you don't use # autoloading LOOKUP .* MODLOAD # Uncomment the following if you want to set the group to "tty" for the # pseudo-tty devices. This is necessary so that mesg(1) can later be used to # enable/disable talk requests and wall(1) messages. REGISTER ^pty/s.* PERMISSIONS -1.tty 0600 REGISTER ^pts/.* PERMISSIONS -1.tty 0600 # Uncomment this if you want permissions to be saved and restored # NB: Do NOT change the following! # Do not do this for pseudo-terminal devices REGISTER ^pt[sy]/.* IGNORE CHANGE ^pt[sy]/.* IGNORE CREATE ^pt[sy]/.* IGNORE DELETE ^pt[sy] IGNORE REGISTER .* COPY /lib/dev-state/$devname $devpath CHANGE .* COPY $devpath /lib/dev-state/$devname CREATE .* COPY $devpath /lib/dev-state/$devname DELETE .* CFUNCTION GLOBAL unlink /lib/dev-state/$devname RESTORE /lib/dev-state # You can force default like this : # PERMISSIONS owner_and_group access_mode # Video4Linux devices REGISTER v4l/.* PERMISSIONS root.video 660 # ALSA/OSS stuff # Comment/change these if you want to change the permissions on # the audio devices LOOKUP snd MODLOAD ACTION snd LOOKUP dsp MODLOAD LOOKUP mixer MODLOAD LOOKUP midi MODLOAD REGISTER sound/.* PERMISSIONS root.audio 660 REGISTER snd/.* PERMISSIONS root.audio 660 # Uncomment this to let PAM manage devfs #REGISTER .* CFUNCTION /lib/security/pam_console_apply_devfsd.s o pam_console_apply_single $devpath # Autoload the sg module if generic scsi driver compiled as module. #LOOKUP ^sg$ MODLOAD ACTION sg # Give the cdrw group write permissions to /dev/sg0 # This is done to have non root user use the burner (scan the scsi bus) REGISTER ^scsi/host.*/bus.*/target.*/lun.*/generic PERMISSIONS root.cd rw 660 # General note for the following auto creation of symlinks: # # If you change the device that the symlink points to, # you should also remove the symlink before restarting # devfsd # Create /dev/cdrom for the first cdrom drive LOOKUP ^cdrom$ CFUNCTION GLOBAL mksymlink cdroms/cdrom0 cdrom REGISTER ^cdroms/cdrom0$ CFUNCTION GLOBAL mksymlink $devname cdrom UNREGISTER ^cdroms/cdrom0$ CFUNCTION GLOBAL unlink cdrom # Create /dev/dvd for the second cdrom drive # (change 'cdroms/cdrom1' to suite your setup) # NOTE: We add the fully qualified path here, else some apps # have problems to resolve the true device (drip comes to mind) LOOKUP ^dvd$ CFUNCTION GLOBAL mksymlink ${mntpnt}/cdroms/cdro m1 dvd REGISTER ^cdroms/cdrom1$ CFUNCTION GLOBAL mksymlink ${devpath} dvd UNREGISTER ^cdroms/cdrom1$ CFUNCTION GLOBAL unlink dvd # Create /dev/cdrw for the first cdrom on the scsi bus # (change 'sr0' to suite your setup) LOOKUP ^cdrw$ CFUNCTION GLOBAL mksymlink sr0 cdrw REGISTER ^sg3$ CFUNCTION GLOBAL mksymlink $devname cdrw UNREGISTER ^sg3$ CFUNCTION GLOBAL unlink cdrw # Create /dev/mouse LOOKUP ^mouse$ CFUNCTION GLOBAL mksymlink misc/psaux mouse REGISTER ^misc/psaux$ CFUNCTION GLOBAL mksymlink $devname mouse UNREGISTER ^misc/psaux$ CFUNCTION GLOBAL unlink mouse # Manage USB mouse REGISTER ^input/mouse0$ CFUNCTION GLOBAL mksymlink $devname usbmouse UNREGISTER ^input/mouse0$ CFUNCTION GLOBAL unlink usbmouse REGISTER ^input/mice$ CFUNCTION GLOBAL mksymlink $devname usbmouse UNREGISTER ^cdroms/cdrom1$ CFUNCTION GLOBAL unlink dvd # Create /dev/cdrw for the first cdrom on the scsi bus # (change 'sr0' to suite your setup) LOOKUP ^cdrw$ CFUNCTION GLOBAL mksymlink sr0 cdrw REGISTER ^sg3$ CFUNCTION GLOBAL mksymlink $devname cdrw UNREGISTER ^sg3$ CFUNCTION GLOBAL unlink cdrw # Create /dev/mouse LOOKUP ^mouse$ CFUNCTION GLOBAL mksymlink misc/psaux mouse REGISTER ^misc/psaux$ CFUNCTION GLOBAL mksymlink $devname mouse UNREGISTER ^misc/psaux$ CFUNCTION GLOBAL unlink mouse # Manage USB mouse REGISTER ^input/mouse0$ CFUNCTION GLOBAL mksymlink $devname usbmouse UNREGISTER ^input/mouse0$ CFUNCTION GLOBAL unlink usbmouse REGISTER ^input/mice$ CFUNCTION GLOBAL mksymlink $devname usbmouse UNREGISTER ^input/mice$ CFUNCTION GLOBAL unlink usbmouse # Support additional config installed by packages ... INCLUDE /etc/devfs.d # devfsd.conf ends here my /etc/modules.devfs ****# /etc/modules.devfs # Richard Gooch 24-MAR-2002 # # THIS IS AN AUTOMATICALLY GENERATED FILE. DO NOT EDIT!!! # THIS FILE WILL BE OVERWRITTEN EACH TIME YOU INSTALL DEVFSD!!! # Modify /etc/modules.conf instead. # This file comes with devfsd-v1.3.25 which is available from: # http://www.atnf.csiro.au/~rgooch/linux/ # or directly from: # ftp://ftp.atnf.csiro.au/pub/people/rgooch/linux/daemons/devfsd-v1.3.25.tar.gz ####################################################################### ######## # Sample configurations that you may want to place in /etc/modules.conf # #alias sound-slot-0 sb #alias /dev/v4l bttv #alias /dev/misc/watchdog pcwd #alias gen-md raid0 #alias /dev/joysticks joystick #probeall scsi_hostadapter sym53c8xx ####################################################################### ######## # Generic section: do not change or copy # # All HDDs probeall /dev/discs scsi_hostadapter sd_mod ide-probe-mod ide-disk i de-floppy DAC960 alias /dev/discs/* /dev/discs # All CD-ROMs probeall /dev/cdroms scsi_hostadapter sr_mod ide-probe-mod ide-cd cdr om alias /dev/cdroms/* /dev/cdroms alias /dev/cdrom /dev/cdroms # All tapes probeall /dev/tapes scsi_hostadapter st ide-probe-mod ide-tape alias /dev/tapes/* /dev/tapes # All SCSI devices probeall /dev/scsi scsi_hostadapter sd_mod sr_mod st sg # All IDE devices probeall /dev/ide ide-probe-mod ide-disk ide-cd ide-tape ide-flopp y # Video capture devices alias /dev/video* /dev/v4l alias /dev/vbi* /dev/v4l # agpgart alias /dev/agpgart agpgart alias /dev/dri* agpgart # Irda devices alias /dev/ircomm ircomm-tty alias /dev/ircomm* /dev/ircomm # Raw I/O devices alias /dev/rawctl /dev/raw # Pull in the configuration file. Do this last because modprobe(8) processes in # per^H^H^Hreverse order and the sysadmin may want to over-ride what is in the # generic file include /etc/modules.conf ***** Here's the dmesg portion st: Version 20020205, bufsize 32768, wrt 30720, max init. bufs 4, s/g segs 16 Attached scsi tape st0 at scsi1, channel 0, id 0, lun 0 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 SCSI device sda: 286744576 512-byte hdwr sectors (146813 MB) Partition check: /dev/scsi/host0/bus0/target0/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 > Attached scsi CD-ROM sr0 at scsi1, channel 0, id 4, lun 0 sr0: scsi3-mmc drive: 0x/0x dvd-ram cd/rw xa/form2 cdda tray Attached scsi generic sg2 at scsi1, channel 0, id 1, lun 0, type 8 -- Brett I. Holcomb From brettholcomb@charter.net Thu Jan 16 19:33:49 2003 Received: with ECARTIS (v1.0.0; list devfs); Thu, 16 Jan 2003 19:33:53 -0800 (PST) Received: from dc-mx01.cluster1.charter.net (dc-mx01.cluster1.charter.net [209.225.8.11]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0H3Xm3v011817 for ; Thu, 16 Jan 2003 19:33:49 -0800 Received: from [68.115.236.214] (HELO strider) by dc-mx01.cluster1.charter.net (CommuniGate Pro SMTP 3.5.9) with SMTP id 33403217 for devfs@oss.sgi.com; Thu, 16 Jan 2003 22:40:01 -0500 Date: Thu, 16 Jan 2003 22:43:05 -0500 From: "Brett I. Holcomb" To: devfs@oss.sgi.com Subject: Re: SCSI Tapes and devfs Message-Id: <20030116224305.14135e68.brettholcomb@charter.net> In-Reply-To: <6134254DE87BD411908B00A0C99B044F03A0B5D9@MOWD019A> References: <20030115180943.1bc7048e.brettholcomb@charter.net> <6134254DE87BD411908B00A0C99B044F03A0B5D9@MOWD019A> Organization: Holcomb & Associates X-Mailer: Sylpheed version 0.8.6claws (GTK+ 1.2.10; ) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-archive-position: 79 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs > Okay, I hit a problem. > > The /dev/tape0 symlink to my /dev/st/c1... works fine. > > However, if I create > > ln -s /dev/sg/c1b0t1u0 /dev/auto_changer0 > > or > > ln -s /dev/sg2 /dev/auto_changer0 > > and then run my tape program (supplied by the backup program vendor) I > have problems. > > I create the link, use ls to show it's there, then run the program - I > get an error "can't find /dev/auto_changer0". I ls /dev/auto* and > /dev/auto_changer0 is not there! > > cat/proc/scsi/scsi shows it's there (the Spectra) as does dmesg > (Attached scsi generic sg2 at scsi1, channel 0, id 1, lun 0, type 8) > > What's happening here? The symlinks for /dev/tape0 and /dev/tape0n > don't disappear. Do I need to do something to the /etc/devfsd.conf or > /etc/modules.conf files?? > > Thank you. > > > bash-2.05b$ cat /proc/scsi/scsi > Attached devices: > Host: scsi0 Channel: 00 Id: 00 Lun: 00 > Vendor: ADAPTEC Model: RAID-5 Rev: 370F > Type: Direct-Access ANSI SCSI revision: 02 > Host: scsi1 Channel: 00 Id: 00 Lun: 00 > Vendor: EXABYTE Model: Mammoth2 Rev: v04b > Type: Sequential-Access ANSI SCSI revision: 02 > Host: scsi1 Channel: 00 Id: 01 Lun: 00 > Vendor: SPECTRA Model: 215 Rev: 1008 > Type: Medium Changer ANSI SCSI revision: 02 > Host: scsi1 Channel: 00 Id: 04 Lun: 00 > Vendor: MATSHITA Model: DVD-RAM LF-D200 Rev: A120 > Type: CD-ROM ANSI SCSI revision: 04 > > > ***** > > Here's the dmesg portion > > st: Version 20020205, bufsize 32768, wrt 30720, max init. bufs 4, > > s/g segs 16 > > Attached scsi tape st0 at scsi1, channel 0, id 0, lun 0 > > Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 > > SCSI device sda: 286744576 512-byte hdwr sectors (146813 MB) > > Partition check: > > /dev/scsi/host0/bus0/target0/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 > > > > > Attached scsi CD-ROM sr0 at scsi1, channel 0, id 4, lun 0 > > sr0: scsi3-mmc drive: 0x/0x dvd-ram cd/rw xa/form2 cdda tray > > Attached scsi generic sg2 at scsi1, channel 0, id 1, lun 0, type 8 > From Andrey.Borzenkov@siemens.com Thu Jan 16 22:09:38 2003 Received: with ECARTIS (v1.0.0; list devfs); Thu, 16 Jan 2003 22:09:41 -0800 (PST) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0H69a3v014162 for ; Thu, 16 Jan 2003 22:09:38 -0800 Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.11.6/8.11.6) with ESMTP id h0H6Fro04338; Fri, 17 Jan 2003 07:15:54 +0100 (MET) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail2.siemens.de (8.11.6/8.11.6) with ESMTP id h0H6FqS26517; Fri, 17 Jan 2003 07:15:53 +0100 (MET) Received: by MOWD019A with Internet Mail Service (5.5.2653.19) id ; Fri, 17 Jan 2003 09:29:55 +0300 Received: from mw2b210c (163.242.193.12 [163.242.193.12]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id DC48SK72; Fri, 17 Jan 2003 09:29:52 +0300 From: Borzenkov Andrey To: "'brett holcomb'" , devfs@oss.sgi.com Subject: RE: SCSI Tapes and devfs Date: Fri, 17 Jan 2003 09:15:44 +0300 Message-ID: <6134254DE87BD411908B00A0C99B044F03A0B5DC@MOWD019A> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-archive-position: 80 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: Andrey.Borzenkov@siemens.com Precedence: bulk X-list: devfs > > > >I guess silence means Devfs works as expected :))) > > As long as you don't try and do what I'm doing . I > think devfs is a neat concept and from what I've read has > a lot of advantages although my knowledge of devices under > Linux has been limited to createing entries in /dev under > the old system and making that work. I don't know what > distros use it (not Caldera's old WS 3.1 or RH 7.3) so > maybe most of the people I see aren't running distros with > it. > Mandrake was one of the first distros to use it (in 8.0 IIRC). The first attempt was a disaster, but since then we learned a bit :) It is easy to screw up things when you use devfs. Basically, you should not mess up with /dev unless _absolutely_ necessary and you _do_ know what you are doing. -andrey From Andrey.Borzenkov@siemens.com Thu Jan 16 22:21:27 2003 Received: with ECARTIS (v1.0.0; list devfs); Thu, 16 Jan 2003 22:21:29 -0800 (PST) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0H6LP3v014292 for ; Thu, 16 Jan 2003 22:21:26 -0800 Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.11.6/8.11.6) with ESMTP id h0H6RgO10046; Fri, 17 Jan 2003 07:27:42 +0100 (MET) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail2.siemens.de (8.11.6/8.11.6) with ESMTP id h0H6RfS00500; Fri, 17 Jan 2003 07:27:41 +0100 (MET) Received: by MOWD019A with Internet Mail Service (5.5.2653.19) id ; Fri, 17 Jan 2003 09:41:44 +0300 Received: from mw2b210c (163.242.193.12 [163.242.193.12]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id DC48SK8N; Fri, 17 Jan 2003 09:41:40 +0300 From: Borzenkov Andrey To: "'brett holcomb'" , devfs@oss.sgi.com Subject: RE: SCSI Tapes and devfs Date: Fri, 17 Jan 2003 09:27:32 +0300 Message-ID: <6134254DE87BD411908B00A0C99B044F03A0B5DD@MOWD019A> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h0H6LP3v014292 X-archive-position: 81 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: Andrey.Borzenkov@siemens.com Precedence: bulk X-list: devfs > > Okay, then what is supposed to tell devfs that there is > now a scsi tape drive/changer ready to use. This is the sole responsibility of corresponding driver. If we speak about SCSI tape, this happens in driver attach method. In the case > of st being a module and me loading it at startup time > causes devfs to see it. But what SHOULD trigger this if > the st support is built into a kernel - what is the > mechanism there for Linux? > The same modulo bugs. St's attach should run in exactly the same fashion and register tape (if found). Are you sure you have not built driver for your SCSI adapter as module? Then when st is initialized at boot time it can't find any tapes because there is no adapter yet. This would perfectly explain why tape was not there initially but appeared later (due to module autoloading). -andrey From lembark@wrkhors.com Thu Jan 16 22:23:11 2003 Received: with ECARTIS (v1.0.0; list devfs); Thu, 16 Jan 2003 22:23:13 -0800 (PST) Received: from getz.wrkhors.com (jeeves.wrkhors.com [207.227.243.17]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0H6NA3v014320 for ; Thu, 16 Jan 2003 22:23:10 -0800 Received: from [192.168.200.4] (dizzy.wrkhors.com [192.168.200.4]) by getz.wrkhors.com (8.12.1/8.12.1) with ESMTP id h0H6Glhm006685 for ; Fri, 17 Jan 2003 00:16:47 -0600 Date: Fri, 17 Jan 2003 00:36:11 -0600 From: Steven Lembark Reply-To: lembark@wrkhors.com To: devfs@oss.sgi.com Subject: RE: SCSI Tapes and devfs Message-ID: <52210000.1042785371@[192.168.200.4]> In-Reply-To: <6134254DE87BD411908B00A0C99B044F03A0B5DC@MOWD019A> References: <6134254DE87BD411908B00A0C99B044F03A0B5DC@MOWD019A> X-Mailer: Mulberry/3.0.0b10 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-archive-position: 82 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: lembark@wrkhors.com Precedence: bulk X-list: devfs -- Borzenkov Andrey >> > >> > I guess silence means Devfs works as expected :))) >> >> As long as you don't try and do what I'm doing . I >> think devfs is a neat concept and from what I've read has >> a lot of advantages although my knowledge of devices under >> Linux has been limited to createing entries in /dev under >> the old system and making that work. I don't know what >> distros use it (not Caldera's old WS 3.1 or RH 7.3) so >> maybe most of the people I see aren't running distros with >> it. >> > > Mandrake was one of the first distros to use it (in 8.0 IIRC). The first > attempt was a disaster, but since then we learned a bit :) > > It is easy to screw up things when you use devfs. Basically, you should > not mess up with /dev unless _absolutely_ necessary and you _do_ know > what you are doing. If you updated /dev/tape to magically appear the changerizer uses the same basic sequence. Another way to put it: let devfsd manaqge /dev, that's what it IS there for. Instead of ln -fs in /dev update /etc/devfsd.conf using, say, "tape" as a template for the changer device -- all you really need to do is hack "tape" for "changer" (whatever) and "tape/0/mt" for the device path to the changerizer. -- Steven Lembark 2930 W. Palmer Workhorse Computing Chicago, IL 60647 +1 773 252 1080 From Andrey.Borzenkov@siemens.com Thu Jan 16 22:34:25 2003 Received: with ECARTIS (v1.0.0; list devfs); Thu, 16 Jan 2003 22:34:28 -0800 (PST) Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0H6YO3v014417 for ; Thu, 16 Jan 2003 22:34:25 -0800 Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.11.6/8.11.6) with ESMTP id h0H6ef509346; Fri, 17 Jan 2003 07:40:41 +0100 (MET) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail2.siemens.de (8.11.6/8.11.6) with ESMTP id h0H6eeS06348; Fri, 17 Jan 2003 07:40:40 +0100 (MET) Received: by MOWD019A with Internet Mail Service (5.5.2653.19) id ; Fri, 17 Jan 2003 09:54:43 +0300 Received: from mw2b210c (163.242.193.12 [163.242.193.12]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id DC48SK0J; Fri, 17 Jan 2003 09:54:40 +0300 From: Borzenkov Andrey To: "'Brett I. Holcomb'" , devfs@oss.sgi.com Subject: RE: SCSI Tapes and devfs Date: Fri, 17 Jan 2003 09:40:32 +0300 Message-ID: <6134254DE87BD411908B00A0C99B044F03A0B5DE@MOWD019A> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 In-Reply-To: <20030116205835.2993b742.brettholcomb@charter.net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h0H6YO3v014417 X-archive-position: 83 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: Andrey.Borzenkov@siemens.com Precedence: bulk X-list: devfs > > Now, where does /etc/modules.conf fit into the devfs scheme - what is it > used for? I thought that was only > for modules yet it's included in /etc/modules.devfs? > /etc/modules.devfs _is_ for modules. The main problem with devfs is, you need driver to be loaded for devices to show up under /dev. But how should kernel know it has to load, say, st when you try to access /dev/tapes/tape0? With static /dev kernel autoloads modules based on major numbers. You have /dev/st0, it has major - forgot - there is as yet no driver that registered this major number, so look it up and load. But with devfs there is _no_ /dev/st0 until st has been loaded. You have chicken and egg problem. Here devfsd helps. When path under /dev is not found devfsd gets notified and tries to load module that may provide support for this device. /etc/modules.devfs includes /etc/modules.conf because /etc/modules.devfs is expected to be generic. If you have local changes (like, say, NVidia driver) you edit /etc/modules.conf as usual. > If I create some symlinks such as > > ln -s /dev/tape0 /dev/st/c1b0t0u0m0 > ln -s /dev/tape0 /dev/st/c1b0t0u0m0n > ls -s /dev/sg/dev/auto_changer0 /dev/sg/c1b0t1u0 > I hope you mean ln -s st/c1b0t0u0m0 /dev/tape0. /dev/st is managed by devfsd internally - do not mess up with it! > do I have to do anything to make them be restored on the next system > reboot? According to my /etc/devfsd.conf (see below) it should, if I > understand it, copy all the devices and restore them next time - > correct? > Looks like it should work, with comment above. > And when do I modify /etc/devfsd.conf - or do I ever. I understand I > need to modify it for the cdrw but what else would I have to do with it > as it seems setup to cover everything necessary? > If you want to change names, change permissions or whatever and make absolutely sure they persist across reboots even if /lib/dev-state is wiped out (that is the first thing you must do if you have problem with names under /dev :)))) -andrey From Andrey.Borzenkov@siemens.com Thu Jan 16 22:41:23 2003 Received: with ECARTIS (v1.0.0; list devfs); Thu, 16 Jan 2003 22:41:26 -0800 (PST) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0H6fL3v014504 for ; Thu, 16 Jan 2003 22:41:23 -0800 Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.11.6/8.11.6) with ESMTP id h0H6ldO20794; Fri, 17 Jan 2003 07:47:39 +0100 (MET) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail2.siemens.de (8.11.6/8.11.6) with ESMTP id h0H6lcS09139; Fri, 17 Jan 2003 07:47:39 +0100 (MET) Received: by MOWD019A with Internet Mail Service (5.5.2653.19) id ; Fri, 17 Jan 2003 10:01:41 +0300 Received: from mw2b210c (163.242.193.12 [163.242.193.12]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id DC48SLA6; Fri, 17 Jan 2003 10:01:40 +0300 From: Borzenkov Andrey To: "'Brett I. Holcomb'" , devfs@oss.sgi.com Subject: RE: SCSI Tapes and devfs Date: Fri, 17 Jan 2003 09:47:31 +0300 Message-ID: <6134254DE87BD411908B00A0C99B044F03A0B5DF@MOWD019A> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 In-Reply-To: <20030116224305.14135e68.brettholcomb@charter.net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h0H6fL3v014504 X-archive-position: 84 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: Andrey.Borzenkov@siemens.com Precedence: bulk X-list: devfs Sorry, cannot say anything. Strace your backup program, if this does not give any clue - run devfsd in debug mode to see if somebody removes this link. -andrey > > > Okay, I hit a problem. > > > > The /dev/tape0 symlink to my /dev/st/c1... works fine. > > > > However, if I create > > > > ln -s /dev/sg/c1b0t1u0 /dev/auto_changer0 > > > > or > > > > ln -s /dev/sg2 /dev/auto_changer0 > > > > and then run my tape program (supplied by the backup program vendor) I > > have problems. > > > > I create the link, use ls to show it's there, then run the program - I > > get an error "can't find /dev/auto_changer0". I ls /dev/auto* and > > /dev/auto_changer0 is not there! > > Is canonical name still there? /dev/scsi/host1/bus0/target1/lun0/generic. Is sg still loaded at this point? > > cat/proc/scsi/scsi shows it's there (the Spectra) as does dmesg > > (Attached scsi generic sg2 at scsi1, channel 0, id 1, lun 0, type 8) > > > > What's happening here? The symlinks for /dev/tape0 and /dev/tape0n > > don't disappear. Do I need to do something to the /etc/devfsd.conf or > > /etc/modules.conf files?? > > > > Thank you. > > > > > > bash-2.05b$ cat /proc/scsi/scsi > > Attached devices: > > Host: scsi0 Channel: 00 Id: 00 Lun: 00 > > Vendor: ADAPTEC Model: RAID-5 Rev: 370F > > Type: Direct-Access ANSI SCSI revision: 02 > > Host: scsi1 Channel: 00 Id: 00 Lun: 00 > > Vendor: EXABYTE Model: Mammoth2 Rev: v04b > > Type: Sequential-Access ANSI SCSI revision: 02 > > Host: scsi1 Channel: 00 Id: 01 Lun: 00 > > Vendor: SPECTRA Model: 215 Rev: 1008 > > Type: Medium Changer ANSI SCSI revision: 02 > > Host: scsi1 Channel: 00 Id: 04 Lun: 00 > > Vendor: MATSHITA Model: DVD-RAM LF-D200 Rev: A120 > > Type: CD-ROM ANSI SCSI revision: 04 > > > > > ***** > > > Here's the dmesg portion > > > st: Version 20020205, bufsize 32768, wrt 30720, max init. bufs 4, > > > s/g segs 16 > > > Attached scsi tape st0 at scsi1, channel 0, id 0, lun 0 > > > Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 > > > SCSI device sda: 286744576 512-byte hdwr sectors (146813 MB) > > > Partition check: > > > /dev/scsi/host0/bus0/target0/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 > > > > > > > Attached scsi CD-ROM sr0 at scsi1, channel 0, id 4, lun 0 > > > sr0: scsi3-mmc drive: 0x/0x dvd-ram cd/rw xa/form2 cdda tray > > > Attached scsi generic sg2 at scsi1, channel 0, id 1, lun 0, type 8 > > From brettholcomb@charter.net Fri Jan 17 04:37:49 2003 Received: with ECARTIS (v1.0.0; list devfs); Fri, 17 Jan 2003 04:37:53 -0800 (PST) Received: from dc-mxdb03.cluster1.charter.net (dc-mxdb03.cluster1.charter.net [209.225.8.78]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0HCbm3v004962 for ; Fri, 17 Jan 2003 04:37:49 -0800 Received: from [158.158.240.230] (account ) by dc-mxdb03.cluster1.charter.net (CommuniGate Pro WebUser 3.5.9) with HTTP id 1729830 for ; Fri, 17 Jan 2003 07:44:02 -0500 From: "brett holcomb" Subject: Re: SCSI Tapes and devfs To: devfs@oss.sgi.com X-Mailer: CommuniGate Pro Web Mailer v.3.5.9 Date: Fri, 17 Jan 2003 07:44:02 -0500 Message-ID: In-Reply-To: <6134254DE87BD411908B00A0C99B044F03A0B5DD@MOWD019A> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format="flowed" Content-Transfer-Encoding: 8bit X-archive-position: 85 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs On Fri, 17 Jan 2003 09:27:32 +0300 Borzenkov Andrey wrote: >This is the sole responsibility of corresponding driver. >If we speak about >SCSI tape, this happens in driver attach method. > > In the case >> of st being a module and me loading it at startup time >> causes devfs to see it. But what SHOULD trigger this if >> the st support is built into a kernel - what is the >> mechanism there for Linux? >> > >The same modulo bugs. St's attach should run in exactly >the same fashion and >register tape (if found). Are you sure you have not built >driver for your >SCSI adapter as module? Then when st is initialized at >boot time it can't >find any tapes because there is no adapter yet. This >would perfectly explain >why tape was not there initially but appeared later (due >to module >autoloading). No, the adapter is built into the kernel - I verified that. >-andrey From brettholcomb@charter.net Fri Jan 17 04:44:41 2003 Received: with ECARTIS (v1.0.0; list devfs); Fri, 17 Jan 2003 04:44:43 -0800 (PST) Received: from dc-mxdb03.cluster1.charter.net (dc-mxdb03.cluster1.charter.net [209.225.8.78]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0HCie3v005000 for ; Fri, 17 Jan 2003 04:44:41 -0800 Received: from [158.158.240.230] (account ) by dc-mxdb03.cluster1.charter.net (CommuniGate Pro WebUser 3.5.9) with HTTP id 1729845 for ; Fri, 17 Jan 2003 07:50:54 -0500 From: "brett holcomb" Subject: Re: SCSI Tapes and devfs To: devfs@oss.sgi.com X-Mailer: CommuniGate Pro Web Mailer v.3.5.9 Date: Fri, 17 Jan 2003 07:50:54 -0500 Message-ID: In-Reply-To: <52210000.1042785371@[192.168.200.4]> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format="flowed" Content-Transfer-Encoding: 8bit X-archive-position: 86 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs Hmm, let me think about this one. On Fri, 17 Jan 2003 00:36:11 -0600 Steven Lembark wrote: > > >If you updated /dev/tape to magically appear the >changerizer >uses the same basic sequence. > >Another way to put it: let devfsd manaqge /dev, that's >what it IS there for. Instead of ln -fs in /dev update >/etc/devfsd.conf using, say, "tape" as a template for >the changer device -- all you really need to do is hack >"tape" for "changer" (whatever) and "tape/0/mt" for the >device path to the changerizer. > >-- >Steven Lembark 2930 W. >Palmer >Workhorse Computing Chicago, IL >60647 > +1 773 252 >1080 > From brettholcomb@charter.net Fri Jan 17 04:48:18 2003 Received: with ECARTIS (v1.0.0; list devfs); Fri, 17 Jan 2003 04:48:24 -0800 (PST) Received: from dc-mxdb03.cluster1.charter.net (dc-mxdb03.cluster1.charter.net [209.225.8.78]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0HCmH3v005039 for ; Fri, 17 Jan 2003 04:48:17 -0800 Received: from [158.158.240.230] (account ) by dc-mxdb03.cluster1.charter.net (CommuniGate Pro WebUser 3.5.9) with HTTP id 1729855 for ; Fri, 17 Jan 2003 07:54:31 -0500 From: "brett holcomb" Subject: Re: SCSI Tapes and devfs To: devfs@oss.sgi.com X-Mailer: CommuniGate Pro Web Mailer v.3.5.9 Date: Fri, 17 Jan 2003 07:54:31 -0500 Message-ID: In-Reply-To: <6134254DE87BD411908B00A0C99B044F03A0B5DF@MOWD019A> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format="flowed" Content-Transfer-Encoding: 8bit X-archive-position: 87 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs n Fri, 17 Jan 2003 09:47:31 +0300 Borzenkov Andrey wrote: >Sorry, cannot say anything. Strace your backup program, >if this does not >give any clue - run devfsd in debug mode to see if >somebody removes this >link. Okay, will do. >-andrey > >> >> > Okay, I hit a problem. >> > >> > The /dev/tape0 symlink to my /dev/st/c1... works fine. >> > >> > However, if I create >> > >> > ln -s /dev/sg/c1b0t1u0 /dev/auto_changer0 >> > >> > or >> > >> > ln -s /dev/sg2 /dev/auto_changer0 >> > >> > and then run my tape program (supplied by the backup >>program vendor) I >> > have problems. >> > >> > I create the link, use ls to show it's there, then run >>the program - I >> > get an error "can't find /dev/auto_changer0". I ls >>/dev/auto* and >> > /dev/auto_changer0 is not there! >> > > >Is canonical name still there? >/dev/scsi/host1/bus0/target1/lun0/generic. Is >sg still loaded at this point? I believe so but I'll double check. However, if I understand yours and Stephen's emails I shouldn't be making symlinks in /dev - I should setup /etc/devfsd.conf to Lookup?, register, etc. these devices? From brettholcomb@charter.net Fri Jan 17 11:12:51 2003 Received: with ECARTIS (v1.0.0; list devfs); Fri, 17 Jan 2003 11:12:53 -0800 (PST) Received: from mx08.cluster1.charter.net (dc-mx08.cluster1.charter.net [209.225.8.18]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0HJCn3v000308 for ; Fri, 17 Jan 2003 11:12:50 -0800 Received: from [10.10.101.108] (HELO dc-mxdb08.cluster1.charter.net) by mx08.cluster1.charter.net (CommuniGate Pro SMTP 3.5.9) with ESMTP id 22655181 for devfs@oss.sgi.com; Fri, 17 Jan 2003 14:19:05 -0500 Received: from [158.158.240.230] (account ) by dc-mxdb08.cluster1.charter.net (CommuniGate Pro WebUser 3.5.9b) with HTTP id 3138204 for ; Fri, 17 Jan 2003 14:19:06 -0500 From: "brett holcomb" Subject: Re: SCSI Tapes and devfs To: devfs@oss.sgi.com X-Mailer: CommuniGate Pro Web Mailer v.3.5.9b Date: Fri, 17 Jan 2003 14:19:06 -0500 Message-ID: In-Reply-To: <52210000.1042785371@[192.168.200.4]> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format="flowed" Content-Transfer-Encoding: 8bit X-archive-position: 88 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs All I really did was create a symlink in /dev from the tape device (/st/c1...) to /dev/tape0 or /dev/tape0n. For some reason this symlink persists. There are no entries for tapes in /etc/devfsd.conf. Do I understand you to say that I should put events in /etc/devfsd.conf that deal with the tape devices? What events do I need - Lookup, register, unregister? Copy should be covered by the copy .* and restore portions of the /etc/devfsd.conf file already to give me persistance across boots. Is that what the /etc/devfsd.conf file is for - to put additional devices in so that devfsd will see them/ Thanks. On Fri, 17 Jan 2003 00:36:11 -0600 Steven Lembark wrote: > >If you updated /dev/tape to magically appear the >changerizer >uses the same basic sequence. > >Another way to put it: let devfsd manaqge /dev, that's >what it IS there for. Instead of ln -fs in /dev update >/etc/devfsd.conf using, say, "tape" as a template for >the changer device -- all you really need to do is hack >"tape" for "changer" (whatever) and "tape/0/mt" for the >device path to the changerizer. > >-- >Steven Lembark 2930 W. >Palmer >Workhorse Computing Chicago, IL >60647 > +1 773 252 >1080 > From brettholcomb@charter.net Fri Jan 17 11:16:26 2003 Received: with ECARTIS (v1.0.0; list devfs); Fri, 17 Jan 2003 11:16:28 -0800 (PST) Received: from mx08.cluster1.charter.net (dc-mx08.cluster1.charter.net [209.225.8.18]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0HJGP3v000343 for ; Fri, 17 Jan 2003 11:16:25 -0800 Received: from [10.10.101.108] (HELO dc-mxdb08.cluster1.charter.net) by mx08.cluster1.charter.net (CommuniGate Pro SMTP 3.5.9) with ESMTP id 22656673 for devfs@oss.sgi.com; Fri, 17 Jan 2003 14:22:40 -0500 Received: from [158.158.240.230] (account ) by dc-mxdb08.cluster1.charter.net (CommuniGate Pro WebUser 3.5.9b) with HTTP id 3138205 for ; Fri, 17 Jan 2003 14:22:41 -0500 From: "brett holcomb" Subject: Re: SCSI Tapes and devfs To: devfs@oss.sgi.com X-Mailer: CommuniGate Pro Web Mailer v.3.5.9b Date: Fri, 17 Jan 2003 14:22:41 -0500 Message-ID: In-Reply-To: <6134254DE87BD411908B00A0C99B044F03A0B5DE@MOWD019A> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format="flowed" Content-Transfer-Encoding: 8bit X-archive-position: 89 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs On Fri, 17 Jan 2003 09:40:32 +0300 Borzenkov Andrey wrote: > >> If I create some symlinks such as >> >> ln -s /dev/tape0 /dev/st/c1b0t0u0m0 >> ln -s /dev/tape0 /dev/st/c1b0t0u0m0n >> ls -s /dev/sg/dev/auto_changer0 /dev/sg/c1b0t1u0 >> > >I hope you mean ln -s st/c1b0t0u0m0 /dev/tape0. /dev/st >is managed by devfsd >internally - do not mess up with it! Yes, I messed up and had these backwards. Sorry. But from your previous email I should NOT be doing this anyway - I need to say out of /dev and do the work through /etc/devfsd.conf - correct/ >Looks like it should work, with comment above. > >> And when do I modify /etc/devfsd.conf - or do I ever. I >>understand I >> need to modify it for the cdrw but what else would I >>have to do with it >> as it seems setup to cover everything necessary? >> > >If you want to change names, change permissions or >whatever and make >absolutely sure they persist across reboots even if >/lib/dev-state is wiped >out (that is the first thing you must do if you have >problem with names >under /dev :)))) From brettholcomb@charter.net Fri Jan 17 18:57:56 2003 Received: with ECARTIS (v1.0.0; list devfs); Fri, 17 Jan 2003 18:57:58 -0800 (PST) Received: from dc-mx10.cluster1.charter.net (dc-mx10.cluster1.charter.net [209.225.8.20]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0I2vt3v008710 for ; Fri, 17 Jan 2003 18:57:56 -0800 Received: from [68.115.236.214] (HELO strider) by dc-mx10.cluster1.charter.net (CommuniGate Pro SMTP 3.5.9) with SMTP id 55640767 for devfs@oss.sgi.com; Fri, 17 Jan 2003 22:04:11 -0500 Date: Fri, 17 Jan 2003 22:07:14 -0500 From: "Brett I. Holcomb" To: devfs@oss.sgi.com Subject: Re: SCSI Tapes and devfs Message-Id: <20030117220714.5a5db443.brettholcomb@charter.net> In-Reply-To: <6134254DE87BD411908B00A0C99B044F03A0B5DD@MOWD019A> References: <6134254DE87BD411908B00A0C99B044F03A0B5DD@MOWD019A> Organization: Holcomb & Associates X-Mailer: Sylpheed version 0.8.6claws (GTK+ 1.2.10; ) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-archive-position: 90 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs I double checked - the SCSI adapter is built into the kernel so it's not a question of the module not loading. On Fri, 17 Jan 2003 09:27:32 +0300 Borzenkov Andrey wrote: > In the case > > of st being a module and me loading it at startup time > > causes devfs to see it. But what SHOULD trigger this if > > the st support is built into a kernel - what is the > > mechanism there for Linux? > > > > The same modulo bugs. St's attach should run in exactly the same > fashion and register tape (if found). Are you sure you have not built > driver for your SCSI adapter as module? Then when st is initialized at > boot time it can't find any tapes because there is no adapter yet. > This would perfectly explain why tape was not there initially but > appeared later (due to module autoloading). -- Brett I. Holcomb From brettholcomb@charter.net Fri Jan 17 19:45:31 2003 Received: with ECARTIS (v1.0.0; list devfs); Fri, 17 Jan 2003 19:45:33 -0800 (PST) Received: from dc-mx11.cluster1.charter.net (dc-mx11.cluster1.charter.net [209.225.8.21]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0I3jU3v008950 for ; Fri, 17 Jan 2003 19:45:31 -0800 Received: from [68.115.236.214] (HELO strider) by dc-mx11.cluster1.charter.net (CommuniGate Pro SMTP 3.5.9) with SMTP id 26618606 for devfs@oss.sgi.com; Fri, 17 Jan 2003 22:51:46 -0500 Date: Fri, 17 Jan 2003 22:54:49 -0500 From: "Brett I. Holcomb" To: devfs@oss.sgi.com Subject: Re: SCSI Tapes and devfs Message-Id: <20030117225449.71bae8ab.brettholcomb@charter.net> In-Reply-To: <6134254DE87BD411908B00A0C99B044F03A0B5DF@MOWD019A> References: <20030116224305.14135e68.brettholcomb@charter.net> <6134254DE87BD411908B00A0C99B044F03A0B5DF@MOWD019A> Organization: Holcomb & Associates X-Mailer: Sylpheed version 0.8.6claws (GTK+ 1.2.10; ) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-archive-position: 91 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs It's the backup program. I created the symlink ln -s /dev/sg/c1b0t1u0 /dev/auto_changer0 and it stays UNTIL I run the backup program an then the link disappears. As long as I tell the backup program to use /dev/sg2 for the changer device everything works! I'll contact the backup people to see what they are doing. However, let me summarize my lack of knowledge here so I don't get too far off track. 1. Don't mess with dev (don't create symlinks in it manually) 2. I THINK I use /etc/devfsd.conf to create the entries in /dev when the device has an event happen to it?. So what I should do to create the autochanger is go to /etc/devfsd.conf and put in something like the CD line to create a symlink. I should have done that for the tape, too but somehow it got created anyway. Is this correct - use /etc/devfsd.conf for creating /dev entries. 3. What have I missed? Thank you. On Fri, 17 Jan 2003 09:47:31 +0300 Borzenkov Andrey wrote: > Sorry, cannot say anything. Strace your backup program, if this does > not give any clue - run devfsd in debug mode to see if somebody > removes this link. > > -andrey > > > > > > Okay, I hit a problem. > > > > > > The /dev/tape0 symlink to my /dev/st/c1... works fine. > > > > > > However, if I create > > > > > > ln -s /dev/sg/c1b0t1u0 /dev/auto_changer0 > > > > > > or > > > > > > ln -s /dev/sg2 /dev/auto_changer0 > > > > > > and then run my tape program (supplied by the backup program > > > vendor) I have problems. > > > > > > I create the link, use ls to show it's there, then run the program > > > - I get an error "can't find /dev/auto_changer0". I ls /dev/auto* > > > and/dev/auto_changer0 is not there! > > > > > Is canonical name still there? > /dev/scsi/host1/bus0/target1/lun0/generic. Is sg still loaded at this > point? > > > > cat/proc/scsi/scsi shows it's there (the Spectra) as does dmesg > > > (Attached scsi generic sg2 at scsi1, channel 0, id 1, lun 0, type > > > 8) > > > > > > What's happening here? The symlinks for /dev/tape0 and > > > /dev/tape0n don't disappear. Do I need to do something to the > > > /etc/devfsd.conf or/etc/modules.conf files?? > > > > > > Thank you. > > > > > > > > > bash-2.05b$ cat /proc/scsi/scsi > > > Attached devices: > > > Host: scsi0 Channel: 00 Id: 00 Lun: 00 > > > Vendor: ADAPTEC Model: RAID-5 Rev: 370F > > > Type: Direct-Access ANSI SCSI revision: 02 > > > Host: scsi1 Channel: 00 Id: 00 Lun: 00 > > > Vendor: EXABYTE Model: Mammoth2 Rev: v04b > > > Type: Sequential-Access ANSI SCSI revision: 02 > > > Host: scsi1 Channel: 00 Id: 01 Lun: 00 > > > Vendor: SPECTRA Model: 215 Rev: 1008 > > > Type: Medium Changer ANSI SCSI revision: 02 > > > Host: scsi1 Channel: 00 Id: 04 Lun: 00 > > > Vendor: MATSHITA Model: DVD-RAM LF-D200 Rev: A120 > > > Type: CD-ROM ANSI SCSI revision: 04 > > > > > > > ***** > > > > Here's the dmesg portion > > > > st: Version 20020205, bufsize 32768, wrt 30720, max init. bufs > > > > 4, s/g segs 16 > > > > Attached scsi tape st0 at scsi1, channel 0, id 0, lun 0 > > > > Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 > > > > SCSI device sda: 286744576 512-byte hdwr sectors (146813 MB) > > > > Partition check: > > > > /dev/scsi/host0/bus0/target0/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 > > > > p10 > > > > > > > > > Attached scsi CD-ROM sr0 at scsi1, channel 0, id 4, lun 0 > > > > sr0: scsi3-mmc drive: 0x/0x dvd-ram cd/rw xa/form2 cdda tray > > > > Attached scsi generic sg2 at scsi1, channel 0, id 1, lun 0, > > > > type 8 > > > > -- Brett I. Holcomb From lembark@wrkhors.com Sat Jan 18 15:21:17 2003 Received: with ECARTIS (v1.0.0; list devfs); Sat, 18 Jan 2003 15:21:19 -0800 (PST) Received: from getz.wrkhors.com (jeeves.wrkhors.com [207.227.243.17]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0INLG3v023705 for ; Sat, 18 Jan 2003 15:21:17 -0800 Received: from [192.168.200.4] (dizzy.wrkhors.com [192.168.200.4]) by getz.wrkhors.com (8.12.1/8.12.1) with ESMTP id h0INF5hm009872 for ; Sat, 18 Jan 2003 17:15:05 -0600 Date: Sat, 18 Jan 2003 17:34:31 -0600 From: Steven Lembark Reply-To: lembark@wrkhors.com To: devfs@oss.sgi.com Subject: Re: SCSI Tapes and devfs Message-ID: <69530000.1042932871@[192.168.200.4]> In-Reply-To: <20030117225449.71bae8ab.brettholcomb@charter.net> References: <20030116224305.14135e68.brettholcomb@charter.net> <6134254DE87BD411908B00A0C99B044F03A0B5DF@MOWD019A> <20030117225449.71bae8ab.brettholcomb@charter.net> X-Mailer: Mulberry/3.0.0b10 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-archive-position: 92 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: lembark@wrkhors.com Precedence: bulk X-list: devfs -- "Brett I. Holcomb" > It's the backup program. I created the symlink > > ln -s /dev/sg/c1b0t1u0 /dev/auto_changer0 Look at the devfsd.conf entry for, say, "cdrom" and just change the 3 event lines from "tape" to "auto_changer0" and "tapes/0/mt" to "sg/c1b0tiu0". Filesystem operatins behave differently in /dev than you are used to (or /proc for that matter) because the filesystem are not on the disk they are in kernel memory where persistent soft links don't really mean anything. It is a semantic issue, not syntax. -- Steven Lembark 2930 W. Palmer Workhorse Computing Chicago, IL 60647 +1 773 252 1080 From brettholcomb@charter.net Sat Jan 18 15:55:23 2003 Received: with ECARTIS (v1.0.0; list devfs); Sat, 18 Jan 2003 15:55:25 -0800 (PST) Received: from mx08.cluster1.charter.net (dc-mx08.cluster1.charter.net [209.225.8.18]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0INtM3v023878 for ; Sat, 18 Jan 2003 15:55:22 -0800 Received: from [68.115.236.214] (HELO strider) by mx08.cluster1.charter.net (CommuniGate Pro SMTP 3.5.9) with SMTP id 23203889 for devfs@oss.sgi.com; Sat, 18 Jan 2003 19:01:42 -0500 Date: Sat, 18 Jan 2003 19:04:45 -0500 From: "Brett I. Holcomb" To: devfs@oss.sgi.com Subject: Re: SCSI Tapes and devfs Message-Id: <20030118190445.7b44f5ab.brettholcomb@charter.net> In-Reply-To: <69530000.1042932871@[192.168.200.4]> References: <20030116224305.14135e68.brettholcomb@charter.net> <6134254DE87BD411908B00A0C99B044F03A0B5DF@MOWD019A> <20030117225449.71bae8ab.brettholcomb@charter.net> <69530000.1042932871@[192.168.200.4]> Organization: Holcomb & Associates X-Mailer: Sylpheed version 0.8.7claws (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-archive-position: 93 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs Okay, I think I understand (some ). I need to use the cdrom entry as a model but change cdrom to tape or auto_ changer0 - correct. I've found out that the backup software tries to find an sg device for the library and then create a symlink to it - which doesn't work under devfs. I've got the library working by using /dev/sg2 as the device instead of auto_changer0. So /etc/devfsd.conf is where we create these links that we want to have and the copy lines make sure they are persistant?? On Sat, 18 Jan 2003 17:34:31 -0600 Steven Lembark wrote: > > > -- "Brett I. Holcomb" > > > It's the backup program. I created the symlink > > > > ln -s /dev/sg/c1b0t1u0 /dev/auto_changer0 > > Look at the devfsd.conf entry for, say, "cdrom" and > just change the 3 event lines from "tape" to > "auto_changer0" and "tapes/0/mt" to "sg/c1b0tiu0". > > Filesystem operatins behave differently in /dev than > you are used to (or /proc for that matter) because the > filesystem are not on the disk they are in kernel memory > where persistent soft links don't really mean anything. > It is a semantic issue, not syntax. > > > > -- > Steven Lembark 2930 W. Palmer > Workhorse Computing Chicago, IL 60647 > +1 773 252 1080 > -- Brett I. Holcomb From lembark@wrkhors.com Sat Jan 18 16:32:29 2003 Received: with ECARTIS (v1.0.0; list devfs); Sat, 18 Jan 2003 16:32:31 -0800 (PST) Received: from getz.wrkhors.com (jeeves.wrkhors.com [207.227.243.17]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0J0WS3v024023 for ; Sat, 18 Jan 2003 16:32:29 -0800 Received: from [192.168.200.4] (dizzy.wrkhors.com [192.168.200.4]) by getz.wrkhors.com (8.12.1/8.12.1) with ESMTP id h0J0QIhm009980 for ; Sat, 18 Jan 2003 18:26:18 -0600 Date: Sat, 18 Jan 2003 18:45:44 -0600 From: Steven Lembark Reply-To: lembark@wrkhors.com To: devfs@oss.sgi.com Subject: Re: SCSI Tapes and devfs Message-ID: <90980000.1042937144@[192.168.200.4]> In-Reply-To: <20030118190445.7b44f5ab.brettholcomb@charter.net> References: <20030116224305.14135e68.brettholcomb@charter.net> <6134254DE87BD411908B00A0C99B044F03A0B5DF@MOWD019A> <20030117225449.71bae8ab.brettholcomb@charter.net> <69530000.1042932871@[192.168.200.4]> <20030118190445.7b44f5ab.brettholcomb@charter.net> X-Mailer: Mulberry/3.0.0b10 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-archive-position: 94 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: lembark@wrkhors.com Precedence: bulk X-list: devfs -- "Brett I. Holcomb" > Okay, I think I understand (some ). > > I need to use the cdrom entry as a model but change cdrom to tape or > auto_ changer0 - correct. > > I've found out that the backup software tries to find an sg device for > the library and then create a symlink to it - which doesn't work under > devfs. I've got the library working by using /dev/sg2 as the device > instead of auto_changer0. > > So /etc/devfsd.conf is where we create these links that we want to have > and the copy lines make sure they are persistant?? Suggestion: Find the backup software authors and a cattle prod or baseball bat... perhaps you can then convince them that the installation code should not be munging your system unless you ask it to (or it at least asks first). If the install is #! code hack the ln -fs out of it. -- Steven Lembark 2930 W. Palmer Workhorse Computing Chicago, IL 60647 +1 773 252 1080 From brettholcomb@charter.net Sat Jan 18 16:49:56 2003 Received: with ECARTIS (v1.0.0; list devfs); Sat, 18 Jan 2003 16:49:58 -0800 (PST) Received: from mx07.cluster1.charter.net (dc-mx07.cluster1.charter.net [209.225.8.17]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0J0nt3v024104 for ; Sat, 18 Jan 2003 16:49:56 -0800 Received: from [68.115.236.214] (HELO strider) by mx07.cluster1.charter.net (CommuniGate Pro SMTP 3.5.9) with SMTP id 21869720 for devfs@oss.sgi.com; Sat, 18 Jan 2003 19:55:46 -0500 Date: Sat, 18 Jan 2003 19:59:18 -0500 From: "Brett I. Holcomb" To: devfs@oss.sgi.com Subject: Re: SCSI Tapes and devfs Message-Id: <20030118195918.7bef153b.brettholcomb@charter.net> In-Reply-To: <90980000.1042937144@[192.168.200.4]> References: <20030116224305.14135e68.brettholcomb@charter.net> <6134254DE87BD411908B00A0C99B044F03A0B5DF@MOWD019A> <20030117225449.71bae8ab.brettholcomb@charter.net> <69530000.1042932871@[192.168.200.4]> <20030118190445.7b44f5ab.brettholcomb@charter.net> <90980000.1042937144@[192.168.200.4]> Organization: Holcomb & Associates X-Mailer: Sylpheed version 0.8.7claws (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-archive-position: 95 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs It's commerical - only because they can do bare iron recovery of windows as well as linux systems and I've got both otherwise I'd be using open source. I've talked to them - they look for a /dev/sg that has the changer and then try making the link. I'll suggest to them they don't do that! Am I correct in thinking that any links I want to create are done in /etc/devfsd.conf - that's my tool for getting devfs to do what I want? On Sat, 18 Jan 2003 18:45:44 -0600 Steven Lembark wrote: > > > -- "Brett I. Holcomb" > > > Okay, I think I understand (some ). > > > > I need to use the cdrom entry as a model but change cdrom to tape or > > auto_ changer0 - correct. > > > > I've found out that the backup software tries to find an sg device > > for the library and then create a symlink to it - which doesn't work > > under devfs. I've got the library working by using /dev/sg2 as the > > device instead of auto_changer0. > > > > So /etc/devfsd.conf is where we create these links that we want to > > have and the copy lines make sure they are persistant?? > > Suggestion: Find the backup software authors and a > cattle prod or baseball bat... perhaps you can then > convince them that the installation code should not > be munging your system unless you ask it to (or it > at least asks first). > > If the install is #! code hack the ln -fs out of it. > > > > -- > Steven Lembark 2930 W. Palmer > Workhorse Computing Chicago, IL 60647 > +1 773 252 1080 > -- Brett I. Holcomb From Andrey.Borzenkov@siemens.com Mon Jan 20 00:22:43 2003 Received: with ECARTIS (v1.0.0; list devfs); Mon, 20 Jan 2003 00:22:46 -0800 (PST) Received: from thoth.sbs.de (thoth.sbs.de [192.35.17.2]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0K8Mf3v011573 for ; Mon, 20 Jan 2003 00:22:42 -0800 Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by thoth.sbs.de (8.11.6/8.11.6) with ESMTP id h0K8TCH07894; Mon, 20 Jan 2003 09:29:12 +0100 (MET) Received: from MOWD019A.mow.siemens.ru ([163.242.196.119]) by mail3.siemens.de (8.11.6/8.11.6) with ESMTP id h0K8TBZ18812; Mon, 20 Jan 2003 09:29:11 +0100 (MET) Received: by mowd019a.mow.siemens.ru with Internet Mail Service (5.5.2653.19) id ; Mon, 20 Jan 2003 11:29:52 +0300 Received: from mw2b210c (163.242.193.12 [163.242.193.12]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id DF6KQ9D5; Mon, 20 Jan 2003 11:29:47 +0300 From: Borzenkov Andrey To: "'Brett I. Holcomb'" , devfs@oss.sgi.com Subject: RE: SCSI Tapes and devfs Date: Mon, 20 Jan 2003 11:29:01 +0300 Message-ID: <6134254DE87BD411908B00A0C99B044F03A0B5E2@mowd019a.mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 In-Reply-To: <20030117225449.71bae8ab.brettholcomb@charter.net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h0K8Mf3v011573 X-archive-position: 96 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: Andrey.Borzenkov@siemens.com Precedence: bulk X-list: devfs > However, let me summarize my lack of knowledge here so I don't get too > far off track. > > 1. Don't mess with dev (don't create symlinks in it manually) > No quite. Once upon a time the only way to restore /dev state after reboot (i.e. your own files, permissions etc) was to copy it over from some backing store. It proved to lead to many problems. Now devfsd properly preserves and restores those links and special files you create in /dev. So, it really does not matter. For most people creating a symlink is much more easier. What you should never do - is manually create any device name or symlink that are managed by devfs(d). This includes any compatibility names like /dev/hdc etc. They must just work. If they do not it means a bug in devfs, devfsd or in the way they are used on your system. But because the distinction is quite obscure for average user the best advice is to simply do not touch it at all. > 2. I THINK I use /etc/devfsd.conf to create the entries in /dev when > the device has an event happen to it?. So what I should do to create > the autochanger is go to /etc/devfsd.conf and put in something like the > CD line to create a symlink. I should have done that for the tape, too > but somehow it got created anyway. Is this correct - use > /etc/devfsd.conf for creating /dev entries. > See above. If you absolutely need to do with devfsd.conf as exercise: REGISTER ^scsi/host1/bus0/target1/lun0/generic$ CFUNCTION GLOBAL mksymlink $devname auto_changer0 Replace numbers with your real numbers of course. In your case it would have benefit of recreating autochanger on reboot, which just proves my point - if it does not work there is a bug lurking somewhere :) -andrey From brettholcomb@charter.net Mon Jan 20 10:12:28 2003 Received: with ECARTIS (v1.0.0; list devfs); Mon, 20 Jan 2003 10:12:31 -0800 (PST) Received: from mx08.cluster1.charter.net (dc-mx08.cluster1.charter.net [209.225.8.18]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0KICR3v032736 for ; Mon, 20 Jan 2003 10:12:28 -0800 Received: from [10.10.101.108] (HELO dc-mxdb08.cluster1.charter.net) by mx08.cluster1.charter.net (CommuniGate Pro SMTP 3.5.9) with ESMTP id 23881333 for devfs@oss.sgi.com; Mon, 20 Jan 2003 13:18:55 -0500 Received: from [158.158.240.230] (account ) by dc-mxdb08.cluster1.charter.net (CommuniGate Pro WebUser 3.5.9b) with HTTP id 3145331 for ; Mon, 20 Jan 2003 13:18:57 -0500 From: "brett holcomb" Subject: Re: SCSI Tapes and devfs To: devfs@oss.sgi.com X-Mailer: CommuniGate Pro Web Mailer v.3.5.9b Date: Mon, 20 Jan 2003 13:18:57 -0500 Message-ID: In-Reply-To: <20030120172300.23455.qmail@mail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format="flowed" Content-Transfer-Encoding: 8bit X-archive-position: 97 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs Yes, it's an Initio A100u2w and the support is built into the kernel. On Tue, 21 Jan 2003 01:23:00 +0800 "Marton Kadar" wrote: >You again phrase it in a way that gives me doubts. > >The SCSI _host_adapter_ support is ONE element in the >kernel. >The SCSI _tape_ support is ANOTHER. > >These two, the host adapter and the tape drive, are also >two very distinct pieces of hardware in your box. > >You can have host adapter support without tape support. >Are you sure it is not the case? > >Marton >----- Original Message ----- >From: "Brett I. Holcomb" >Date: Fri, 17 Jan 2003 22:07:14 -0500 >To: devfs@oss.sgi.com >Subject: Re: SCSI Tapes and devfs > >> I double checked - the SCSI adapter is built into the >>kernel so it's not >> a question of the module not loading. >> >> >> On Fri, 17 Jan 2003 09:27:32 +0300 >> Borzenkov Andrey wrote: >> >> > In the case >> > > of st being a module and me loading it at startup >>time >> > > causes devfs to see it. But what SHOULD trigger >>this if >> > > the st support is built into a kernel - what is the >> > > mechanism there for Linux? >> > > >> > >> > The same modulo bugs. St's attach should run in >>exactly the same >> > fashion and register tape (if found). Are you sure you >>have not built >> > driver for your SCSI adapter as module? Then when st >>is initialized at >> > boot time it can't find any tapes because there is no >>adapter yet. >> > This would perfectly explain why tape was not there >>initially but >> > appeared later (due to module autoloading). >> >> >> -- >> >> Brett I. Holcomb >> >> > >-- >__________________________________________________________ >Sign-up for your own FREE Personalized E-mail at Mail.com >http://www.mail.com/?sr=signup > >Meet Singles >http://corp.mail.com/lavalife > From proski@gnu.org Mon Jan 20 10:53:03 2003 Received: with ECARTIS (v1.0.0; list devfs); Mon, 20 Jan 2003 10:53:05 -0800 (PST) Received: from fencepost.gnu.org (fencepost.gnu.org [199.232.76.164]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0KIr23v000636 for ; Mon, 20 Jan 2003 10:53:03 -0800 Received: from proski by fencepost.gnu.org with local (Exim 4.10) id 18ah8x-00070X-00; Mon, 20 Jan 2003 13:59:35 -0500 Date: Mon, 20 Jan 2003 13:59:34 -0500 (EST) From: Pavel Roskin X-X-Sender: proski@marabou.research.att.com To: Steven Lembark cc: Robert , Devfs Subject: Re: Error on boot and host0 business In-Reply-To: <199790000.1042575133@[192.168.200.4]> Message-ID: References: <1042557538.2868.6.camel@localhost.localdomain> <199790000.1042575133@[192.168.200.4]> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 98 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: proski@gnu.org Precedence: bulk X-list: devfs Hello! > > Jan 14 09:00:01 localhost devfsd: Started device management daemon > > v1.3.25 for /dev > > Jan 14 09:00:02 localhost devfsd: error calling: symlink in GLOBAL > > Jan 14 09:00:02 localhost devfsd[65]: error calling: "unlink" in > > "GLOBAL" Another random idea - maybe your devfsd is linked statically? Or maybe you did something unusual with libc or libdl, e.g. stripped it? -- Regards, Pavel Roskin From brettholcomb@charter.net Mon Jan 20 13:25:33 2003 Received: with ECARTIS (v1.0.0; list devfs); Mon, 20 Jan 2003 13:25:35 -0800 (PST) Received: from dc-mxdb07.cluster1.charter.net (dc-mxdb07.cluster1.charter.net [209.225.8.82]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0KLPW3v005893 for ; Mon, 20 Jan 2003 13:25:33 -0800 Received: from [158.158.240.230] (account ) by dc-mxdb07.cluster1.charter.net (CommuniGate Pro WebUser 3.5.9b) with HTTP id 3528701 for ; Mon, 20 Jan 2003 16:32:01 -0500 From: "brett holcomb" Subject: Re: SCSI Tapes and devfs To: devfs@oss.sgi.com X-Mailer: CommuniGate Pro Web Mailer v.3.5.9b Date: Mon, 20 Jan 2003 16:32:01 -0500 Message-ID: In-Reply-To: <20030120183908.38332.qmail@mail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format="flowed" Content-Transfer-Encoding: 8bit X-archive-position: 99 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs Thank you for the detailed explanation. I'll read through it tonight. On Tue, 21 Jan 2003 02:39:07 +0800 "Marton Kadar" wrote: >Hi, > >Just to share my own idea of things in devfs/devfsd: > >If a program needs to talk to a device, it opens a device >node in the filesystem. The question is, what is the link >between the device node and the driver code? >There is a reference file in the linux kernel sources: >Documentation/devices.txt. This contains the assigned >numbers of all devices. This file is a layer of >conventions from before devfs. >There was another layer of conventions, (I think it is >also more or less documented in devices.txt) that of the >device node names under /dev. So there was a convention, >that your 2nd SCSI cd-rom drive has major number X and >minor number Y, and another convention, that it should be >represented by node sr1 under /dev. >The number convention is used by the device drivers in >the kernel. If you wanted to write a device driver for an >scsi cdrom drive, you had to look up the major and minor >numbers in this table, and let your code register itself >under these numbers. >The node-name convention is used by user space programs. >So if you wanted to write a user space program which >needed to talk to the 2nd SCSI cdrom drive, it had to >look for it at /dev/sr1. > >But in fact, you could create a device node ANYWHERE in >your disk-based filesystem, and assign some device major >and minor numbers to it, and then you could configure >your user application to use that device node. When the >program opens the device node for communication, the >kernel takes the major number and checks which device >driver registered itself under that number, and lets that >driver handle things. > >There were two changes that devfs mainly introduced: >- allowed for not using device numbers at all, as there >were problems with all the numbers being used up >- changed the device node naming convention to better >reflect the tree-like structure of interfaces, buses, >adapters etc. >We refer to the new node naming convention as the devfs >namespace. > >So a modern kernel device driver may choose to register >itself only by the path and name of the devices it will >handle. >A modern user space program should be ready to find the >device nodes also under their new filesystem location. >The link between drivers and device nodes is no longer >established by the major and minor numbers, but the >device node NAME ITSELF is the link. > >Up till now there's been no word about devfsd. In an >utopistic world >- all your device drivers register themselves by name in >the devfs namespace, >- the kernel mounts the devfs filesystem under /dev at >boot time, thus making the device nodes available to >programs, >- and all your programs know where to find them. > >In the real world there are old device drivers (less and >less the case) and for some time to come there will be >old user space programs. Old programs expect the device >nodes at the old locations, but they are no longer there. >To handle this issue, devfsd was invented. >If you look at the file names in a mounted devfs >filesystem, you notice one thing which is not a device, >the devfsd control socket. When a device driver in the >kernel registers itself, two things happen: the device >node is created in the filesystem, AND an event signal >(REGISTER) is sent through the devfsd control socket. IF >devfsd is running, attached to the socket, it catches the >signal, looks at /etc/devfsd.conf, and carries out the >specified helper action(s). > >One special helper action is MAKEOLDCOMPAT which means >that a symlink has to be created according to the OLD >/dev device node naming conventions, which points to the >NEW ("real") devfs-compliant device node location. This >allows old programs find the newly registered device >where they expect it. > >Another kind of signal arrives from the kernel (LOOKUP >event), when it is asked to open a file(device node) in >the devfs filesystem, but the file is not there. This is >typically the case when a kernel module has not been >loaded yet, so the driver could not register itself yet >under that path. So devfsd can try to load the desired >module if it finds such instructions (MODLOAD action) in >/etc/devfsd.conf. > >OK, this was rather lengthy. It just wanted to be a >framework for your thinking. There are lots of details >and particulars that you need to check yourself. > >Marton > >----- Original Message ----- >From: "Brett I. Holcomb" >Date: Fri, 17 Jan 2003 22:54:49 -0500 >To: devfs@oss.sgi.com >Subject: Re: SCSI Tapes and devfs > >> It's the backup program. I created the symlink >> >> ln -s /dev/sg/c1b0t1u0 /dev/auto_changer0 >> >> and it stays UNTIL I run the backup program an then the >>link disappears. >> As long as I tell the backup program to use /dev/sg2 >>for the changer >> device everything works! I'll contact the backup people >>to see what >> they are doing. >> >> However, let me summarize my lack of knowledge here so I >>don't get too >> far off track. >> >> 1. Don't mess with dev (don't create symlinks in it >>manually) >> >> 2. I THINK I use /etc/devfsd.conf to create the entries >>in /dev when >> the device has an event happen to it?. So what I should >>do to create >> the autochanger is go to /etc/devfsd.conf and put in >>something like the >> CD line to create a symlink. I should have done that >>for the tape, too >> but somehow it got created anyway. Is this correct - >>use >> /etc/devfsd.conf for creating /dev entries. >> >> 3. What have I missed? >> >> Thank you. >> >-- >__________________________________________________________ >Sign-up for your own FREE Personalized E-mail at Mail.com >http://www.mail.com/?sr=signup > >Meet Singles >http://corp.mail.com/lavalife > From brettholcomb@charter.net Fri Jan 24 17:45:10 2003 Received: with ECARTIS (v1.0.0; list devfs); Fri, 24 Jan 2003 17:45:12 -0800 (PST) Received: from dc-mx12.cluster1.charter.net (dc-mx12.cluster1.charter.net [209.225.8.22]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0P1j93v018557 for ; Fri, 24 Jan 2003 17:45:09 -0800 Received: from [68.115.236.214] (HELO strider) by dc-mx12.cluster1.charter.net (CommuniGate Pro SMTP 3.5.9) with SMTP id 73520977 for devfs@oss.sgi.com; Fri, 24 Jan 2003 20:51:55 -0500 Date: Fri, 24 Jan 2003 20:54:49 -0500 From: "Brett I. Holcomb" To: devfs@oss.sgi.com Subject: Fw: More devfs questions Message-Id: <20030124205449.7e748e44.brettholcomb@charter.net> Organization: Holcomb & Associates X-Mailer: Sylpheed version 0.8.7claws (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-archive-position: 100 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs Thanks to all who answered my questions on SCSI tapes and devfs. Things are a lot more clear now. I did get my autochanger link working. It is formed when a test program (moves tapes, etc.) accesses the changer. Now I need to get my tape working properly. However, I have three scsi cards and the FAQ mentions that I can use scsishost= to force the order of detection. Where do I put this parameter - in the lilo.conf file as an append option? Also, since the tape drive appears in both /dev/st (devfs namespace0 and /dev/tapes (kernel namespace) is there any advantage, disadvantage to making the link to one over the other. Thank you. -- Brett I. Holcomb -- Brett I. Holcomb From brettholcomb@charter.net Fri Jan 24 20:02:05 2003 Received: with ECARTIS (v1.0.0; list devfs); Fri, 24 Jan 2003 20:02:08 -0800 (PST) Received: from dc-mx15.cluster1.charter.net (dc-mx15.cluster0.charter.net [209.225.8.25] (may be forged)) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0P4233v020282 for ; Fri, 24 Jan 2003 20:02:04 -0800 Received: from [68.115.236.214] (HELO strider) by dc-mx15.cluster1.charter.net (CommuniGate Pro SMTP 3.5.9) with SMTP id 27884620 for devfs@oss.sgi.com; Fri, 24 Jan 2003 23:08:50 -0500 Date: Fri, 24 Jan 2003 23:11:44 -0500 From: "Brett I. Holcomb" To: devfs@oss.sgi.com Subject: Re: Fw: More devfs questions Message-Id: <20030124231144.1ec78241.brettholcomb@charter.net> In-Reply-To: <20030124205449.7e748e44.brettholcomb@charter.net> References: <20030124205449.7e748e44.brettholcomb@charter.net> Organization: Holcomb & Associates X-Mailer: Sylpheed version 0.8.7claws (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-archive-position: 101 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs Another question What is the pro/con of linking to /dev/sg3 vs /sg/c1....? They both end up in the same place but I'm wondering what ramifications there are for each method. -- Brett I. Holcomb From franza@free.fr Mon Jan 27 10:43:00 2003 Received: with ECARTIS (v1.0.0; list devfs); Mon, 27 Jan 2003 10:43:05 -0800 (PST) Received: from postfix3-2.free.fr (postfix3-2.free.fr [213.228.0.169]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0RIgw3v022986 for ; Mon, 27 Jan 2003 10:42:59 -0800 Received: from imp4-1.free.fr (imp4-1.free.fr [213.228.0.57]) by postfix3-2.free.fr (Postfix) with ESMTP id 0927FC10C for ; Mon, 27 Jan 2003 19:50:02 +0100 (CET) Received: by imp4-1.free.fr (Postfix, from userid 33) id C9A2E5583; Mon, 27 Jan 2003 19:50:01 +0100 (CET) To: devfs@oss.sgi.com Subject: Configuring USB port with devfs Message-ID: <1043693401.3e357f5983c75@imp.free.fr> Date: Mon, 27 Jan 2003 19:50:01 +0100 (CET) From: franza@free.fr MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.6 X-Originating-IP: 80.13.108.109 X-archive-position: 102 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: franza@free.fr Precedence: bulk X-list: devfs Hi, I use a Linux Mandrake 9.0 with devfs. I'd like to link my usb port with devfs and know which path to /dev Has anybody an idea about the configuration files to update dealing with the boot process ? FYI: I use a VIA chipset as USB port. Thanx in advance ... From Andrey.Borzenkov@siemens.com Tue Jan 28 01:20:53 2003 Received: with ECARTIS (v1.0.0; list devfs); Tue, 28 Jan 2003 01:20:58 -0800 (PST) Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0S9Kp3v016375 for ; Tue, 28 Jan 2003 01:20:53 -0800 Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by goliath.siemens.de (8.11.6/8.11.6) with ESMTP id h0S9RtN21236; Tue, 28 Jan 2003 10:27:55 +0100 (MET) Received: from MOWD019A.mow.siemens.ru ([163.242.196.119]) by mail3.siemens.de (8.11.6/8.11.6) with ESMTP id h0S9Rs510087; Tue, 28 Jan 2003 10:27:55 +0100 (MET) Received: by mowd019a.mow.siemens.ru with Internet Mail Service (5.5.2653.19) id ; Tue, 28 Jan 2003 12:28:50 +0300 Received: from mw2b210c (163.242.193.12 [163.242.193.12]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id D5CN6Q1V; Tue, 28 Jan 2003 12:28:48 +0300 From: Borzenkov Andrey To: "'Brett I. Holcomb'" , devfs@oss.sgi.com Subject: RE: More devfs questions Date: Tue, 28 Jan 2003 12:27:46 +0300 Message-ID: <6134254DE87BD411908B00A0C99B044F03A0B605@mowd019a.mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal In-Reply-To: <20030124205449.7e748e44.brettholcomb@charter.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-archive-position: 103 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: Andrey.Borzenkov@siemens.com Precedence: bulk X-list: devfs > Thanks to all who answered my questions on SCSI tapes and devfs. > Things are a lot more clear now. I did get my autochanger link working. > It is formed when a test program (moves tapes, etc.) accesses the > changer. Now I need to get my tape working properly. > > However, I have three scsi cards and the FAQ mentions that I can use > scsishost= to force the order of detection. Where do I put this > parameter - in the lilo.conf file as an append option? > like with all other parameters it depends upon scsi_mod being built in or mnodule. > Also, since the tape drive appears in both /dev/st (devfs namespace0 and > /dev/tapes (kernel namespace) is there any advantage, disadvantage to > making the link to one over the other. > /dev/st gives you permanent (module SCSI host number) address. /dev/tapes name float. Add another tape and all numbers may be off. -andrey From Andrey.Borzenkov@siemens.com Tue Jan 28 01:21:22 2003 Received: with ECARTIS (v1.0.0; list devfs); Tue, 28 Jan 2003 01:21:24 -0800 (PST) Received: from thoth.sbs.de (thoth.sbs.de [192.35.17.2]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0S9LK3v016382 for ; Tue, 28 Jan 2003 01:21:21 -0800 Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by thoth.sbs.de (8.11.6/8.11.6) with ESMTP id h0S9SQG28392; Tue, 28 Jan 2003 10:28:26 +0100 (MET) Received: from MOWD019A.mow.siemens.ru ([163.242.196.119]) by mail3.siemens.de (8.11.6/8.11.6) with ESMTP id h0S9SP510698; Tue, 28 Jan 2003 10:28:26 +0100 (MET) Received: by mowd019a.mow.siemens.ru with Internet Mail Service (5.5.2653.19) id ; Tue, 28 Jan 2003 12:29:21 +0300 Received: from mw2b210c (163.242.193.12 [163.242.193.12]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id D5CN6QFA; Tue, 28 Jan 2003 12:29:16 +0300 From: Borzenkov Andrey To: "'Brett I. Holcomb'" , devfs@oss.sgi.com Subject: RE: Fw: More devfs questions Date: Tue, 28 Jan 2003 12:28:15 +0300 Message-ID: <6134254DE87BD411908B00A0C99B044F03A0B606@mowd019a.mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal In-Reply-To: <20030124231144.1ec78241.brettholcomb@charter.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-archive-position: 104 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: Andrey.Borzenkov@siemens.com Precedence: bulk X-list: devfs > Another question > > What is the pro/con of linking to /dev/sg3 vs /sg/c1....? They both end > up in the same place but I'm wondering what ramifications there are for > each method. > compatibility ... or should I call it legacy? > > > > -- > > Brett I. Holcomb From brettholcomb@charter.net Tue Jan 28 04:42:05 2003 Received: with ECARTIS (v1.0.0; list devfs); Tue, 28 Jan 2003 04:42:12 -0800 (PST) Received: from dc-mxdb06.cluster1.charter.net (dc-mxdb06.cluster1.charter.net [209.225.8.81]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0SCg43v000898 for ; Tue, 28 Jan 2003 04:42:05 -0800 Received: from [158.158.240.230] (account ) by dc-mxdb06.cluster1.charter.net (CommuniGate Pro WebUser 3.5.9b) with HTTP id 709677 for ; Tue, 28 Jan 2003 07:49:06 -0500 From: "brett holcomb" Subject: Re: Fw: More devfs questions To: devfs@oss.sgi.com X-Mailer: CommuniGate Pro Web Mailer v.3.5.9b Date: Tue, 28 Jan 2003 07:49:06 -0500 Message-ID: In-Reply-To: <6134254DE87BD411908B00A0C99B044F03A0B606@mowd019a.mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format="flowed" Content-Transfer-Encoding: 8bit X-archive-position: 105 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs About what I thought - I'll link to the actual stuff. On Tue, 28 Jan 2003 12:28:15 +0300 Borzenkov Andrey wrote: > >> Another question >> >> What is the pro/con of linking to /dev/sg3 vs >>/sg/c1....? They both end >> up in the same place but I'm wondering what >>ramifications there are for >> each method. >> > >compatibility ... or should I call it legacy? > >> >> >> >> -- >> >> Brett I. Holcomb > > From brettholcomb@charter.net Tue Jan 28 04:43:35 2003 Received: with ECARTIS (v1.0.0; list devfs); Tue, 28 Jan 2003 04:43:37 -0800 (PST) Received: from dc-mxdb06.cluster1.charter.net (dc-mxdb06.cluster1.charter.net [209.225.8.81]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0SChY3v000909 for ; Tue, 28 Jan 2003 04:43:35 -0800 Received: from [158.158.240.230] (account ) by dc-mxdb06.cluster1.charter.net (CommuniGate Pro WebUser 3.5.9b) with HTTP id 709729 for ; Tue, 28 Jan 2003 07:50:30 -0500 From: "brett holcomb" Subject: Re: More devfs questions To: devfs@oss.sgi.com X-Mailer: CommuniGate Pro Web Mailer v.3.5.9b Date: Tue, 28 Jan 2003 07:50:30 -0500 Message-ID: In-Reply-To: <6134254DE87BD411908B00A0C99B044F03A0B605@mowd019a.mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format="flowed" Content-Transfer-Encoding: 8bit X-archive-position: 106 X-ecartis-version: Ecartis v1.0.0 Sender: devfs-bounce@oss.sgi.com Errors-to: devfs-bounce@oss.sgi.com X-original-sender: brettholcomb@charter.net Precedence: bulk X-list: devfs On Tue, 28 Jan 2003 12:27:46 +0300 Borzenkov Andrey wrote: > >>that I can use >> scsishost= to force the order of detection. Where do I >>put this >> parameter - in the lilo.conf file as an append option? >> > >like with all other parameters it depends upon scsi_mod >being built in or >mnodule. It is built in so I assume append scsihost=xxx >> Also, since the tape drive appears in both /dev/st >>(devfs namespace0 and >> /dev/tapes (kernel namespace) is there any advantage, >>disadvantage to >> making the link to one over the other. >> > >/dev/st gives you permanent (module SCSI host number) >address. /dev/tapes >name float. Add another tape and all numbers may be off. Good point. I'll link to the st stuff. >-andrey >