From owner-devfs@oss.sgi.com Mon Jan 1 02:18:50 2001 Received: by oss.sgi.com id ; Mon, 1 Jan 2001 02:18:41 -0800 Received: from snark.wizard.com ([209.170.216.3]:51460 "EHLO snark.wizard.com") by oss.sgi.com with ESMTP id ; Mon, 1 Jan 2001 02:18:27 -0800 Received: from bellicha.wizard.com (root@dyn40.nas6.vegas.viawest.net [209.170.209.40]) by snark.wizard.com (8.9.3/8.9.3) with ESMTP id CAA07396; Mon, 1 Jan 2001 02:18:21 -0800 (PST) Received: (from bradl@localhost) by bellicha.wizard.com (8.11.0/8.10.2) id f01A7l612617; Mon, 1 Jan 2001 02:07:47 -0800 Date: Mon, 1 Jan 2001 02:07:47 -0800 From: A Guy Called Tyketto To: Sasha Howard Cc: devfs@oss.sgi.com Subject: Re: devfs and the 2.2.18 kernel Message-ID: <20010101020747.A12357@wizard.com> References: <200012312212.eBVMC4i15305@madlinux.commercialventvac.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="G4iJoqBmSsgzjUCe" Content-Disposition: inline User-Agent: Mutt/1.3.12i In-Reply-To: <200012312212.eBVMC4i15305@madlinux.commercialventvac.com>; from sasha@madlinux.net on Sun, Dec 31, 2000 at 02:12:04PM -0800 X-Operating-System: Linux/2.2.17 (i586) X-uptime: 1:54am up 25 days, 6:07, 3 users, load average: 0.06, 0.04, 0.00 X-RSA-KeyID: 0xE9DF4D85 X-DSA-KeyID: 0xE319F0BF X-PGP-Keys: see http://www.omnilinx.net/~tyketto/pgp.html Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing --G4iJoqBmSsgzjUCe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 31, 2000 at 02:12:04PM -0800, Sasha Howard wrote: > Has anyone had any experience with devfs and the 2.2.18 kernel? When I do= a=20 > "make menuconfig" with the 2.2.18 kernel the option "devfs filesystem" do= es > not show up under the filesystem menu. However, it appears that devfs is = in > fact in the kernel source tree: /usr/src/linux/include/linux/devfs_fs.h. > Could it be that devfs was left out in the menuconfig script this time ar= ound? >=20 > -- Alexander=20 Actually, no. According to the release notes sent out by Alan Cox about 2.2.18,= =20 there is no mention of devfs mentioned at all. Also, doing a tar -tzvf on t= he=20 source tarball, I see no directory tree for devfs. there are header files,= =20 yes, but no actual source code. Also, devfs had started to be included in t= he=20 early stages of the 2.3 tree, but still was excluded for 2.2. There hasn't= =20 been a patch released for 2.2.18, for devfs either, and I don't think there= =20 will, with Linus pre-releasing 2.4.0. 2.4 is close around the corner, so yo= u=20 may be stuck with 2.2.17 until 2.4 comes out. The devfs patch for 2.2.17 wi= ll=20 not apply cleanly to the 2.2.18 tree, so YMMV if you try to patch manually. BL. --=20 Brad Littlejohn | Email: tyketto@wizard.com Unix Systems Administrator, | tyketto@ozemail.com.au Web + NewsMaster, BOFH.. Smeghead! :) | http://www.wizard.com/~tyketto PGP: 1024D/E319F0BF 6980 AAD6 7329 E9E6 D569 F620 C819 199A E319 F0BF --G4iJoqBmSsgzjUCe Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4c (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6UFbyyBkZmuMZ8L8RAnsdAJ9zY9KWYcPR3L38JMiIWpaipASoEQCfcBWB IrzxXwVrNO3VvfoERIncriI= =bXkD -----END PGP SIGNATURE----- --G4iJoqBmSsgzjUCe-- From owner-devfs@oss.sgi.com Thu Jan 4 19:12:58 2001 Received: by oss.sgi.com id ; Thu, 4 Jan 2001 19:12:39 -0800 Received: from demai05.mw.mediaone.net ([24.131.1.56]:58268 "EHLO demai05.mw.mediaone.net") by oss.sgi.com with ESMTP id ; Thu, 4 Jan 2001 19:12:27 -0800 Received: from deimos.ceddec.com (nic-30-c64-170.mw.mediaone.net [24.30.64.170]) by demai05.mw.mediaone.net (8.8.7/8.8.7) with ESMTP id WAA14165 for ; Thu, 4 Jan 2001 22:12:25 -0500 (EST) Received: (from nobody@localhost) by deimos.ceddec.com (8.9.3/8.9.3) id WAA00615 for devfs@oss.sgi.com; Thu, 4 Jan 2001 22:12:24 -0500 Date: Thu, 4 Jan 2001 22:12:23 -0500 From: Tom Zerucha To: devfs@oss.sgi.com Subject: IDE-SCSI? Won't come up on mine... Message-ID: <20010104221223.A611@deimos.mw.mediaone.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing I used to use IDE as modules, until there was a problem with initrds, but even then many times ide-scsi wouldn't load (I had to unload and reload ide-probe and ide-scsi). With devfs on, it won't come up, so I can't use my CD Writer as anything other than a normal CD. Does anyone have this working or have an idea why it wouldn't? From owner-devfs@oss.sgi.com Sat Jan 6 02:13:18 2001 Received: by oss.sgi.com id ; Sat, 6 Jan 2001 02:13:08 -0800 Received: from smtp-out.netactive.net ([196.22.160.30]:33543 "HELO smtp-out.netactive.net") by oss.sgi.com with SMTP id ; Sat, 6 Jan 2001 02:12:55 -0800 Received: (qmail 30411 invoked from network); 6 Jan 2001 10:21:49 -0000 Received: from ctpm31-72.netactive.co.za (HELO chippo.chippo.org) (196.22.170.72) by smtp-out.netactive.net with SMTP; 6 Jan 2001 10:21:49 -0000 Received: from netactive.co.za (localhost.localdomain [127.0.0.1]) by chippo.chippo.org (8.9.3/8.8.7) with ESMTP id MAA08924; Sat, 6 Jan 2001 12:12:39 +0200 Message-ID: <3A56EF96.18D7021D@netactive.co.za> Date: Sat, 06 Jan 2001 12:12:39 +0200 From: Chris the Elder Reply-To: chippo@netactive.co.za X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16 i686) X-Accept-Language: en MIME-Version: 1.0 To: A Guy Called Tyketto CC: devfs@oss.sgi.com Subject: Re: devfs and the 2.2.18 kernel References: <200012312212.eBVMC4i15305@madlinux.commercialventvac.com> <20010101020747.A12357@wizard.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing A Guy Called Tyketto wrote: > The devfs patch for 2.2.17 will > not apply cleanly to the 2.2.18 tree, so YMMV if you try to patch manually. Does that mean it's going to be easy or not? I'm about to try anyway, 'cos I really need devfs _and_ 2.2.18. Cheers, chippo From owner-devfs@oss.sgi.com Sat Jan 6 15:46:03 2001 Received: by oss.sgi.com id ; Sat, 6 Jan 2001 15:45:53 -0800 Received: from snark.wizard.com ([209.170.216.3]:7185 "EHLO snark.wizard.com") by oss.sgi.com with ESMTP id ; Sat, 6 Jan 2001 15:45:40 -0800 Received: from bellicha.wizard.com (root@dyn119.nas8.vegas.viawest.net [209.170.209.119]) by snark.wizard.com (8.9.3/8.9.3) with ESMTP id PAA32472; Sat, 6 Jan 2001 15:45:39 -0800 (PST) Received: (from bradl@localhost) by bellicha.wizard.com (8.11.2/8.10.2) id f06Na4k04808; Sat, 6 Jan 2001 15:36:04 -0800 Date: Sat, 6 Jan 2001 15:36:04 -0800 From: A Guy Called Tyketto To: Chris the Elder Cc: devfs@oss.sgi.com Subject: Re: devfs and the 2.2.18 kernel Message-ID: <20010106153604.A4780@wizard.com> References: <200012312212.eBVMC4i15305@madlinux.commercialventvac.com> <20010101020747.A12357@wizard.com> <3A56EF96.18D7021D@netactive.co.za> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="KsGdsel6WgEHnImy" Content-Disposition: inline User-Agent: Mutt/1.3.13i In-Reply-To: <3A56EF96.18D7021D@netactive.co.za>; from chippo@netactive.co.za on Sat, Jan 06, 2001 at 12:12:39PM +0200 X-Operating-System: Linux/2.4.0-ac2 (i586) X-uptime: 3:32pm up 13:44, 1 user, load average: 0.12, 0.05, 0.10 X-RSA-KeyID: 0xE9DF4D85 X-DSA-KeyID: 0xE319F0BF X-PGP-Keys: see http://www.omnilinx.net/~tyketto/pgp.html Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing --KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 06, 2001 at 12:12:39PM +0200, Chris the Elder wrote: > A Guy Called Tyketto wrote: >=20 > > The devfs patch for 2.2.17 will > > not apply cleanly to the 2.2.18 tree, so YMMV if you try to patch manua= lly. >=20 > Does that mean it's going to be easy or not? I'm about to try anyway, > 'cos I really need devfs _and_ 2.2.18. From what I had tried, it wasn't real easy. there were a slewful of= =20 rejections. parts of the patch that failed. You may try to piece the right= =20 parts of the patch into the 2.2.18 source manually, but I think it would be= =20 harder to do. On another note, I found it quite easy to jump from 2.2.17 (where I= =20 was), straight to 2.4.0. DevFS is already in the source, and makes things T= ONS=20 easier. Once again, YMMV. BL. --=20 Brad Littlejohn | Email: tyketto@wizard.com Unix Systems Administrator, | tyketto@ozemail.com.au Web + NewsMaster, BOFH.. Smeghead! :) | http://www.wizard.com/~tyketto PGP: 1024D/E319F0BF 6980 AAD6 7329 E9E6 D569 F620 C819 199A E319 F0BF --KsGdsel6WgEHnImy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4c (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6V6vjyBkZmuMZ8L8RAp+tAKCBe6aJns6nUGqvod8JmDnxNGFHqACeOWmc +gfp4OpeKZ0mndUV82YYQMY= =L0Rw -----END PGP SIGNATURE----- --KsGdsel6WgEHnImy-- From owner-devfs@oss.sgi.com Wed Jan 10 21:53:48 2001 Received: by oss.sgi.com id ; Wed, 10 Jan 2001 21:53:38 -0800 Received: from [200.222.195.217] ([200.222.195.217]:5263 "EHLO pervalidus.dyndns.org") by oss.sgi.com with ESMTP id ; Wed, 10 Jan 2001 21:53:18 -0800 Received: from pervalidus by pervalidus.dyndns.org with local (Exim 3.20 #1) id 14Gaff-00066q-00 for devfs@oss.sgi.com; Thu, 11 Jan 2001 03:53:11 -0200 Date: Thu, 11 Jan 2001 03:53:11 -0200 From: =?iso-8859-1?Q?Fr=E9d=E9ric_L_=2E_W_=2E?= Meunier <0@pervalidus.net> To: devfs@oss.sgi.com Subject: Switching to devfs Message-ID: <20010111035311.G1130@pervalidus> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.3.12i X-Mailer: Mutt/1.3.12i - Linux 2.4.0 Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Hi. I'd like to know what you recommend to switch (yes, move and never return) to devfs. What should I do? rm -rf /dev is safe? But when? I know mounting devfs in /dev won't show my old entries, but if you won't boot with a Kernel without this support, I see no reason to keep it. -- 0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR) From owner-devfs@oss.sgi.com Tue Jan 16 11:17:48 2001 Received: by oss.sgi.com id ; Tue, 16 Jan 2001 11:17:38 -0800 Received: from user1.hushmail.com ([64.40.111.41]:5640 "EHLO user1.hushmail.com") by oss.sgi.com with ESMTP id ; Tue, 16 Jan 2001 11:17:35 -0800 Received: (from root@localhost) by user1.hushmail.com (8.9.3/8.9.3) id LAA17986; Tue, 16 Jan 2001 11:16:46 -0800 From: corleyja@hushmail.com Message-Id: <200101161916.LAA17986@user1.hushmail.com> Content-type: multipart/mixed; boundary="Hushpart_boundary_AkpzBCzcdRuOPkPmGYmxtimwsykBfQkR" Subject: persistence across reboots Mime-version: 1.0 To: devfs@oss.sgi.com Date: Tue, 16 Jan 2001 14:14:01 -0500 (EST) Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing --Hushpart_boundary_AkpzBCzcdRuOPkPmGYmxtimwsykBfQkR Content-type: text/plain I apologize if this is not the correct forum for this question, but I have been unable to find an answer to my questions anywhere else. I have the 2.4.0 kernel running with devfs enabled. I have followed the instructions found at http://www.atnf.csiro.au/~rgooch/linux/docs/devfs.html to a tee, and yet I still cannot get devfs to save permissions across a reboot. For example, if I chown user /dev/sound/* and reboot, when the box comes back up, I see that the files are owned by root again. I have added the following to my /etc/rc.d/rc.sysinit file: mount --bind /dev /dev-state mount -t devfs none /dev /sbin/devfsd /dev I've also edited my /etc/devfsd.conf file as follows: # Sample /etc/devfsd.conf configuration file. # Richard Gooch 3-JUL-2000 # # 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 this if you want permissions to be saved and restored REGISTER .* COPY /dev-state/$devname $devpath CHANGE .* COPY $devpath /dev-state/$devname CREATE .* COPY $devpath /dev-state/$devname Is there something I'm missing/not understanding? Well, there's obviously a fair amount I'm not understanding, but is it because I'm misreading the documents, looking at the wrong source, etc.? Any help anyone can offer would be greatly appreciated. Jason Free, encrypted, secure Web-based email at www.hushmail.com --Hushpart_boundary_AkpzBCzcdRuOPkPmGYmxtimwsykBfQkR-- IMPORTANT NOTICE: If you are not using HushMail, this message could have been read easily by the many people who have access to your open personal email messages. Get your FREE, totally secure email address at http://www.hushmail.com. From owner-devfs@oss.sgi.com Tue Jan 16 12:11:09 2001 Received: by oss.sgi.com id ; Tue, 16 Jan 2001 12:10:59 -0800 Received: from user1.hushmail.com ([64.40.111.41]:37643 "EHLO user1.hushmail.com") by oss.sgi.com with ESMTP id ; Tue, 16 Jan 2001 12:10:44 -0800 Received: (from root@localhost) by user1.hushmail.com (8.9.3/8.9.3) id MAA22280; Tue, 16 Jan 2001 12:10:01 -0800 From: corleyja@hushmail.com Message-Id: <200101162010.MAA22280@user1.hushmail.com> Content-type: multipart/mixed; boundary="Hushpart_boundary_AOVodaulhxClyAdIlELUGhyFauoxruWm" Subject: Re: about devfsd Mime-version: 1.0 To: "Ernesto CEDILLO-ARIAS" Date: Tue, 16 Jan 2001 15:11:16 -0500 (EST) Cc: devfs@oss.sgi.com Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing --Hushpart_boundary_AOVodaulhxClyAdIlELUGhyFauoxruWm Content-type: text/plain I thought the rc.devfs was an older (translation unused in the 2.4.0) script... I could definitely be mistaken. How have you invoked it? Also, I think the RTLD errors can be fixed by compiling devfsd with `make CC=kgcc install` under RH 7.0 (I'm not super positive about this, I'm running RH 6.2). Also, you may need to make sure that you have the updated modutils, e2fsprogs, util-linux, etc. mentioned in /wherever/you/untarred/kernel/src/Documentation/Changes. Thanks, Jason At Tue, 16 Jan 2001 13:23:26 -0600, "Ernesto CEDILLO-ARIAS" wrote: > >Hello > >There is a file called rc.devfs which I think does the job. You must >set it >up in your init scripts. By the way I had problems compiling devfsd >under >2.4.0 and glibc-2.2. I had to compile it on another RH6.1 and then copy >the >exec to my newer system. >I got RTLD_NEXT undeclared error. Do you have any idea about this? > > >----- Original Message ----- >From: >To: >Sent: Tuesday, January 16, 2001 1:14 PM >Subject: persistence across reboots > > >> >> I apologize if this is not the correct forum for this question, but >I have >> been unable to find an answer to my questions anywhere else. I have >the >> 2.4.0 kernel running with devfs enabled. I have followed the instructions >> found at http://www.atnf.csiro.au/~rgooch/linux/docs/devfs.html to >a tee, >> and yet I still cannot get devfs to save permissions across a reboot. >> For example, if I chown user /dev/sound/* and reboot, when the box >comes >> back up, I see that the files are owned by root again. I have added >the >> following to my /etc/rc.d/rc.sysinit file: >> >> mount --bind /dev /dev-state >> mount -t devfs none /dev >> /sbin/devfsd /dev >> >> I've also edited my /etc/devfsd.conf file as follows: >> >> # Sample /etc/devfsd.conf configuration file. >> # Richard Gooch 3-JUL-2000 >> # >> # 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 this if you want permissions to be saved and restored >> REGISTER .* COPY /dev-state/$devname $devpath >> CHANGE .* COPY $devpath /dev-state/$devname >> CREATE .* COPY $devpath /dev-state/$devname >> >> Is there something I'm missing/not understanding? Well, there's obviously >> a fair amount I'm not understanding, but is it because I'm misreading >the >> documents, looking at the wrong source, etc.? Any help anyone can >offer >> would be greatly appreciated. >> >> Jason >> Free, encrypted, secure Web-based email at www.hushmail.com > Free, encrypted, secure Web-based email at www.hushmail.com --Hushpart_boundary_AOVodaulhxClyAdIlELUGhyFauoxruWm-- IMPORTANT NOTICE: If you are not using HushMail, this message could have been read easily by the many people who have access to your open personal email messages. Get your FREE, totally secure email address at http://www.hushmail.com. From owner-devfs@oss.sgi.com Tue Jan 16 18:59:40 2001 Received: by oss.sgi.com id ; Tue, 16 Jan 2001 18:59:20 -0800 Received: from user1.hushmail.com ([64.40.111.41]:5893 "EHLO user1.hushmail.com") by oss.sgi.com with ESMTP id ; Tue, 16 Jan 2001 18:59:04 -0800 Received: (from root@localhost) by user1.hushmail.com (8.9.3/8.9.3) id SAA22788; Tue, 16 Jan 2001 18:58:24 -0800 From: corleyja@hushmail.com Message-Id: <200101170258.SAA22788@user1.hushmail.com> Content-type: multipart/mixed; boundary="Hushpart_boundary_hDEcwFKRQjIRHBbHRELcMKeRKYzpBaoo" Subject: Re: about devfsd Mime-version: 1.0 To: "Ernesto CEDILLO-ARIAS" Date: Tue, 16 Jan 2001 21:48:13 -0500 (EST) Cc: devfs@oss.sgi.com Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing --Hushpart_boundary_hDEcwFKRQjIRHBbHRELcMKeRKYzpBaoo Content-type: text/plain Having looked further into the rc.devfs script, it basically looks like a script to tar up the entries in /dev. I qoute Richard Gooch's devfs page (http://www.atnf.CSIRO.AU/~rgooch/linux/docs/devfs.html#persistence) on using this methodology. "Although effective, many consider this approach a kludge." He goes on to say: "A much better approach is to use devfsd to save and restore permissions." Which I've followed to the letter (minus the fact that "mount -t bind" has changed to "mount --bind", and yet I find when I reboot the permissions I have manually set have indeed been reset to the defaults. I'm stumped. Plenty of people on this list have this working, is there something not written into Richard's documents that has changed? Thanks, Jason At Tue, 16 Jan 2001 13:23:26 -0600, "Ernesto CEDILLO-ARIAS" wrote: > >Hello > >There is a file called rc.devfs which I think does the job. You must >set it >up in your init scripts. By the way I had problems compiling devfsd >under >2.4.0 and glibc-2.2. I had to compile it on another RH6.1 and then copy >the >exec to my newer system. >I got RTLD_NEXT undeclared error. Do you have any idea about this? > > >----- Original Message ----- >From: >To: >Sent: Tuesday, January 16, 2001 1:14 PM >Subject: persistence across reboots > > >> >> I apologize if this is not the correct forum for this question, but >I have >> been unable to find an answer to my questions anywhere else. I have >the >> 2.4.0 kernel running with devfs enabled. I have followed the instructions >> found at http://www.atnf.csiro.au/~rgooch/linux/docs/devfs.html to >a tee, >> and yet I still cannot get devfs to save permissions across a reboot. >> For example, if I chown user /dev/sound/* and reboot, when the box >comes >> back up, I see that the files are owned by root again. I have added >the >> following to my /etc/rc.d/rc.sysinit file: >> >> mount --bind /dev /dev-state >> mount -t devfs none /dev >> /sbin/devfsd /dev >> >> I've also edited my /etc/devfsd.conf file as follows: >> >> # Sample /etc/devfsd.conf configuration file. >> # Richard Gooch 3-JUL-2000 >> # >> # 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 this if you want permissions to be saved and restored >> REGISTER .* COPY /dev-state/$devname $devpath >> CHANGE .* COPY $devpath /dev-state/$devname >> CREATE .* COPY $devpath /dev-state/$devname >> >> Is there something I'm missing/not understanding? Well, there's obviously >> a fair amount I'm not understanding, but is it because I'm misreading >the >> documents, looking at the wrong source, etc.? Any help anyone can >offer >> would be greatly appreciated. >> >> Jason >> Free, encrypted, secure Web-based email at www.hushmail.com > Free, encrypted, secure Web-based email at www.hushmail.com --Hushpart_boundary_hDEcwFKRQjIRHBbHRELcMKeRKYzpBaoo-- IMPORTANT NOTICE: If you are not using HushMail, this message could have been read easily by the many people who have access to your open personal email messages. Get your FREE, totally secure email address at http://www.hushmail.com. From owner-devfs@oss.sgi.com Wed Jan 17 14:40:56 2001 Received: by oss.sgi.com id ; Wed, 17 Jan 2001 14:40:46 -0800 Received: from user1.hushmail.com ([64.40.111.41]:1040 "EHLO user1.hushmail.com") by oss.sgi.com with ESMTP id ; Wed, 17 Jan 2001 14:40:20 -0800 Received: (from root@localhost) by user1.hushmail.com (8.9.3/8.9.3) id OAA15452; Wed, 17 Jan 2001 14:39:28 -0800 From: corleyja@hushmail.com Message-Id: <200101172239.OAA15452@user1.hushmail.com> Content-type: multipart/mixed; boundary="Hushpart_boundary_vqwmBJaePaPAYXLnEDXWNNdQzQoIdDJV" Subject: devfs persistance across reboots Mime-version: 1.0 To: devfs@oss.sgi.com Date: Wed, 17 Jan 2001 17:31:40 -0500 (EST) Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing --Hushpart_boundary_vqwmBJaePaPAYXLnEDXWNNdQzQoIdDJV Content-type: text/plain I figured out my persistance across reboots issue with devfs and the 2.4 kernel. DO NOT enable CONFIG_DEVFS_MOUNT within the kernel. What's happening is the kernel is set to mount the devfs tree at boot, so it goes ahead and does that before any of your save/restore/bind stuff that you put into the /etc/devfsd.conf and /etc/rc.d/rc.sysinit takes effect. So when you try to remount the devfs tree and bind it from the /dev-state directory, mount will tell you the file system is already mounted. I tried everything with the kernel I have and the "devfs=nomount" passed to lilo and it worked fine, restored my permission settings and everything. Hope this helps someone else. Jason Free, encrypted, secure Web-based email at www.hushmail.com --Hushpart_boundary_vqwmBJaePaPAYXLnEDXWNNdQzQoIdDJV-- IMPORTANT NOTICE: If you are not using HushMail, this message could have been read easily by the many people who have access to your open personal email messages. Get your FREE, totally secure email address at http://www.hushmail.com. From owner-devfs@oss.sgi.com Thu Jan 18 21:29:25 2001 Received: by oss.sgi.com id ; Thu, 18 Jan 2001 21:29:16 -0800 Received: from nwcst337.netaddress.usa.net ([204.68.23.82]:47255 "HELO convert rfc822-to-8bit nwcst337.netaddress.usa.net") by oss.sgi.com with SMTP id ; Thu, 18 Jan 2001 21:29:16 -0800 Received: (qmail 26038 invoked by uid 60001); 19 Jan 2001 05:26:01 -0000 Message-ID: <20010119052601.26037.qmail@nwcst337.netaddress.usa.net> Received: from 204.68.23.82 by nwcst337 for [24.27.250.226] via web-mailer(34FM.0700.15A.01) on Fri Jan 19 05:26:00 GMT 2001 Date: 19 Jan 2001 00:26:00 EST From: Brian Rossmeisl To: devfs@oss.sgi.com Subject: devfs and PCMCIA scripts X-Mailer: USANET web-mailer (34FM.0700.15A.01) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing I am running slackware 7.2beta, and a 2.4.0 kernel, I am running devfs and loving it, I have migrated most everything over to the new nameing scheme, except my /etc/pcmcia directory, the files in there make specific calls to /dev/$device and such. So how do I get around this? any suggestions? I was thinking about making a /dev-stable/? directory and putting the devices I specificly need in there, but I figured someone would know of a better way so if I set it up on something other than my personal laptop I wouldn't have to be a super sleuth :) ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=1 From owner-devfs@oss.sgi.com Fri Jan 19 16:09:23 2001 Received: by oss.sgi.com id ; Fri, 19 Jan 2001 16:09:03 -0800 Received: from nwcst330.netaddress.usa.net ([204.68.23.75]:63984 "HELO convert rfc822-to-8bitN =?ISO-8859-1?Q?ORCPTq=0E=01?= nwcst330.netaddress.usa.net") by oss.sgi.com with SMTP id ; Fri, 19 Jan 2001 16:09:01 -0800 Received: (qmail 23779 invoked by uid 60001); 20 Jan 2001 00:08:59 -0000 Message-ID: <20010120000859.23778.qmail@nwcst330.netaddress.usa.net> Received: from 204.68.23.75 by nwcst330 for [24.27.250.226] via web-mailer(34FM.0700.15A.01) on Sat Jan 20 00:08:59 GMT 2001 Date: 19 Jan 2001 19:08:59 EST From: Brian Rossmeisl To: devfs@oss.sgi.com Subject: Re: [Re: devfs and PCMCIA scripts] X-Mailer: USANET web-mailer (34FM.0700.15A.01) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing I don't mind you ranting. I appreaciate the info on the pcmcia-cs stuff, it was right in front of my face and I didn't think about it :), but to get devices to appear after a reboot you have to add a couple of lines of options to the /etc/devfsd.conf. REGISTER .* COPY /dev-state/$devname $devpath CHANGE .* COPY $devpath /dev-state/$devname CREATE .* COPY $devpath /dev-state/$devname this will copy any custom devices you have made in the /dev-state directory to the dev directory when devfsd starts, I could do that for my specific PCMCIA devices I have on my laptop, but I am still interested in seeing if I can get it working automaticaly, since I change machines & hardware quite often. corleyja@hushmail.com wrote: > > I don't mean to sidestep your point here, but could you do me a favor if > it's not too much trouble? It'll confirm a suspicion of mine. Create a > symlink, character device, whatever in /dev while devfs is running. Reboot. > If it's still there when the box comes back up, tell me everything you've > done to set up devfs. Otherwise, I suspect you are like I was, in that > you think devfs is working until you need to do something (VMware is a great > example of something that won't work across reboots due to this /dev mangling). > I'm not bashing devfs, I really like it, but I think a lot of people (myself > at the very head of this list) think they have it running when in fact they > don't. > > Having not run PCMCIA on a box (no laptop) I would hazard a guess that you > need to enable the hotplug stuff in the kernel and then change all the device > names manually, if possible. The PCMCIA web page (http://pcmcia-cs.sourceforge.net) > might be a good place to look for compatibility issues with devfs. > > Sorry for ranting at you, > Jason > > At 19 Jan 2001 00:26:00 EST, Brian Rossmeisl wrote: > > > > >I am running slackware 7.2beta, and a 2.4.0 kernel, I am running devfs > >and > >loving it, I have migrated most everything over to the new nameing scheme, > >except my /etc/pcmcia directory, the files in there make specific calls > >to > >/dev/$device and such. So how do I get around this? any suggestions? > >I was > >thinking about making a /dev-stable/? directory and putting the devices > >I > >specificly need in there, but I figured someone would know of a better > >way so > >if I set it up on something other than my personal laptop I wouldn't > >have to > >be a super sleuth :) ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=1 From owner-devfs@oss.sgi.com Fri Jan 19 17:46:14 2001 Received: by oss.sgi.com id ; Fri, 19 Jan 2001 17:45:54 -0800 Received: from nwcst283.netaddress.usa.net ([204.68.23.28]:48005 "HELO convert rfc822-to-8bitm nwcst283.netaddress.usa.net") by oss.sgi.com with SMTP id ; Fri, 19 Jan 2001 17:45:51 -0800 Received: (qmail 5372 invoked by uid 60001); 20 Jan 2001 01:45:50 -0000 Message-ID: <20010120014550.5371.qmail@nwcst283.netaddress.usa.net> Received: from 204.68.23.28 by nwcst283 for [24.27.250.226] via web-mailer(34FM.0700.15A.01) on Sat Jan 20 01:45:50 GMT 2001 Date: 19 Jan 2001 20:45:50 EST From: Brian Rossmeisl To: devfs@oss.sgi.com Subject: Re: [Re: [Re: devfs and PCMCIA scripts]] X-Mailer: USANET web-mailer (34FM.0700.15A.01) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing After you added those lines to your /etc/devfsd.conf , or uncommented them, did you then do a mknod of the various character devices that VMware makes, and others, into the /dev-state directory? ie, mknod /dev-stat/crazy-vmware-char-dev [{bc} p] major minor corleyja@hushmail.com wrote: > > Sadly, those lines are in my /etc/devfsd.conf file. No dice, especially > with the devices VMware creates (various character devices) and no luck > if I create, say a /dev/pilot symlink which points to /dev/usb/tts/1. Don't > know what the deal is, but it saves permissions just fine. Just won't save > new devices. Oh well. I stand by my assertion that devfs is poorly documented. > Do you know how long it took me to figure out that "mount -t devfs" is > no longer correct? Probably longer than it should've I'll admit, but I > figured the guy knew what he was talking about, he wrote the freaking thing. > *sigh* > Jason > > At 19 Jan 2001 19:08:59 EST, Brian Rossmeisl wrote: > > > > >I don't mind you ranting. I appreaciate the info on the pcmcia-cs stuff, > > it > >was right in front of my face and I didn't think about it :), but to > >get > >devices to appear after a reboot you have to add a couple of lines of > >options > >to the /etc/devfsd.conf. > > > >REGISTER .* COPY /dev-state/$devname $devpath > >CHANGE .* COPY $devpath /dev-state/$devname > >CREATE .* COPY $devpath /dev-state/$devname > > > >this will copy any custom devices you have made in the /dev-state directory > >to > >the dev directory when devfsd starts, I could do that for my specific > >PCMCIA > >devices I have on my laptop, but I am still interested in seeing if > >I can get > >it working automaticaly, since I change machines & hardware quite often. > > > >corleyja@hushmail.com wrote: > >> > >> I don't mean to sidestep your point here, but could you do me a favor > >if > >> it's not too much trouble? It'll confirm a suspicion of mine. Create > >a > >> symlink, character device, whatever in /dev while devfs is running. > > Reboot. > > > >> If it's still there when the box comes back up, tell me everything > >you've > >> done to set up devfs. Otherwise, I suspect you are like I was, in > >that > >> you think devfs is working until you need to do something (VMware > >is a great > > > >> example of something that won't work across reboots due to this /dev > >mangling). > >> I'm not bashing devfs, I really like it, but I think a lot of people > >(myself > >> at the very head of this list) think they have it running when in > >fact they > > > >> don't. > >> > >> Having not run PCMCIA on a box (no laptop) I would hazard a guess > >that you > >> need to enable the hotplug stuff in the kernel and then change all > >the > >device > >> names manually, if possible. The PCMCIA web page > >(http://pcmcia-cs.sourceforge.net) > >> might be a good place to look for compatibility issues with devfs. > >> > >> Sorry for ranting at you, > >> Jason > >> > >> At 19 Jan 2001 00:26:00 EST, Brian Rossmeisl > >wrote: > >> > >> > > >> >I am running slackware 7.2beta, and a 2.4.0 kernel, I am running > >devfs > >> >and > >> >loving it, I have migrated most everything over to the new nameing > >scheme, > >> >except my /etc/pcmcia directory, the files in there make specific > >calls > >> >to > >> >/dev/$device and such. So how do I get around this? any suggestions? > >> >I was > >> >thinking about making a /dev-stable/? directory and putting the devices > >> >I > >> >specificly need in there, but I figured someone would know of a better > >> >way so > >> >if I set it up on something other than my personal laptop I wouldn't > >> >have to > >> >be a super sleuth :) ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=1 From owner-devfs@oss.sgi.com Sat Jan 20 18:57:52 2001 Received: by oss.sgi.com id ; Sat, 20 Jan 2001 18:57:43 -0800 Received: from nwcst282.netaddress.usa.net ([204.68.23.27]:57038 "HELO convert rfc822-to-8bit nwcst282.netaddress.usa.net") by oss.sgi.com with SMTP id ; Sat, 20 Jan 2001 18:57:30 -0800 Received: (qmail 9731 invoked by uid 60001); 21 Jan 2001 02:57:28 -0000 Message-ID: <20010121025728.9730.qmail@nwcst282.netaddress.usa.net> Received: from 204.68.23.27 by nwcst282 for [24.27.250.226] via web-mailer(34FM.0700.15A.01) on Sun Jan 21 02:57:28 GMT 2001 Date: 20 Jan 2001 21:57:28 EST From: Brian Rossmeisl To: devfs@oss.sgi.com Subject: Re: [Re: [Re: [Re: devfs and PCMCIA scripts]]] X-Mailer: USANET web-mailer (34FM.0700.15A.01) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Hmm, I dunno, maybe Richard Gooch might be able to help us out on this one. corleyja@hushmail.com wrote: > > No, but /dev-state and /dev are bound at bootup so they contain the same > devices at any given time. Is this method even recommended anymore? I've > added the following lines into my /etc/rc.d/rc.sysinit script as per Richard > Gooch's homepage on devfs: > /bin/mount --bind /dev /dev-state > /bin/mount -t devfs none /dev > /sbin/devfsd /dev > I did this in order to preserve permissions across reboots, which it does. > It just doesn't keep devices I've created in /dev. > Jason > > At 19 Jan 2001 20:45:50 EST, Brian Rossmeisl wrote: > > > > >After you added those lines to your /etc/devfsd.conf , or uncommented > >them, > >did you then do a mknod of the various character devices that VMware > >makes, > >and others, into the /dev-state directory? ie, > > > >mknod /dev-stat/crazy-vmware-char-dev [{bc} p] major minor > > > >corleyja@hushmail.com wrote: > >> > >> Sadly, those lines are in my /etc/devfsd.conf file. No dice, especially > >> with the devices VMware creates (various character devices) and no > >luck > >> if I create, say a /dev/pilot symlink which points to /dev/usb/tts/1. > > Don't > > > >> know what the deal is, but it saves permissions just fine. Just won't > >save > > > >> new devices. Oh well. I stand by my assertion that devfs is poorly > >documented. > >> Do you know how long it took me to figure out that "mount -t devfs" > >is > >> no longer correct? Probably longer than it should've I'll admit, > >but I > >> figured the guy knew what he was talking about, he wrote the freaking > >thing. > > > >> *sigh* > >> Jason > >> > >> At 19 Jan 2001 19:08:59 EST, Brian Rossmeisl > >wrote: > >> > >> > > >> >I don't mind you ranting. I appreaciate the info on the pcmcia-cs > >stuff, > >> > it > >> >was right in front of my face and I didn't think about it :), but > >to > >> >get > >> >devices to appear after a reboot you have to add a couple of lines > >of > >> >options > >> >to the /etc/devfsd.conf. > >> > > >> >REGISTER .* COPY /dev-state/$devname $devpath > >> >CHANGE .* COPY $devpath /dev-state/$devname > >> >CREATE .* COPY $devpath /dev-state/$devname > >> > > >> >this will copy any custom devices you have made in the /dev-state > >directory > > > >> >to > >> >the dev directory when devfsd starts, I could do that for my specific > >> >PCMCIA > >> >devices I have on my laptop, but I am still interested in seeing > >if > >> >I can get > >> >it working automaticaly, since I change machines & hardware quite > >often. > >> > > >> >corleyja@hushmail.com wrote: > >> >> > >> >> I don't mean to sidestep your point here, but could you do me a > >favor > >> >if > >> >> it's not too much trouble? It'll confirm a suspicion of mine. > > Create > >> >a > >> >> symlink, character device, whatever in /dev while devfs is running. > >> > Reboot. > >> > > >> >> If it's still there when the box comes back up, tell me everything > >> >you've > >> >> done to set up devfs. Otherwise, I suspect you are like I was, > > in > >> >that > >> >> you think devfs is working until you need to do something (VMware > >> >is a great > >> > > >> >> example of something that won't work across reboots due to this > >/dev > >> >mangling). > >> >> I'm not bashing devfs, I really like it, but I think a lot of > >people > >> >(myself > >> >> at the very head of this list) think they have it running when > >in > >> >fact they > >> > > >> >> don't. > >> >> > >> >> Having not run PCMCIA on a box (no laptop) I would hazard a guess > >> >that you > >> >> need to enable the hotplug stuff in the kernel and then change > >all > >> >the > >> >device > >> >> names manually, if possible. The PCMCIA web page > >> >(http://pcmcia-cs.sourceforge.net) > >> >> might be a good place to look for compatibility issues with devfs. > >> >> > >> >> Sorry for ranting at you, > >> >> Jason > >> >> > >> >> At 19 Jan 2001 00:26:00 EST, Brian Rossmeisl > >> >wrote: > >> >> > >> >> > > >> >> >I am running slackware 7.2beta, and a 2.4.0 kernel, I am running > >> >devfs > >> >> >and > >> >> >loving it, I have migrated most everything over to the new nameing > >> >scheme, > >> >> >except my /etc/pcmcia directory, the files in there make specific > >> >calls > >> >> >to > >> >> >/dev/$device and such. So how do I get around this? any suggestions? > >> >> >I was > >> >> >thinking about making a /dev-stable/? directory and putting the > >devices > > > >> >> >I > >> >> >specificly need in there, but I figured someone would know of > >a better > >> >> >way so > >> >> >if I set it up on something other than my personal laptop I wouldn't > >> >> >have to > >> >> >be a super sleuth :) ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=1 From owner-devfs@oss.sgi.com Tue Jan 23 16:46:32 2001 Received: by oss.sgi.com id ; Tue, 23 Jan 2001 16:46:12 -0800 Received: from mg01.austin.ibm.com ([192.35.232.18]:19336 "EHLO mailgate1.austin.ibm.com") by oss.sgi.com with ESMTP id ; Tue, 23 Jan 2001 16:46:10 -0800 Received: from austin.ibm.com (netmail.austin.ibm.com [9.53.250.98]) by mailgate1.austin.ibm.com (AIX4.3/8.9.3/8.9.3) with ESMTP id SAA19946; Tue, 23 Jan 2001 18:46:24 -0600 Received: from popmail.austin.ibm.com (popmail.austin.ibm.com [9.53.247.178]) by austin.ibm.com (AIX4.3/8.9.3/8.9.3) with ESMTP id SAA46698; Tue, 23 Jan 2001 18:46:07 -0600 Received: from us.ibm.com (grimm.austin.ibm.com [9.53.216.106]) by popmail.austin.ibm.com (AIX4.3/8.9.3/8.7-client1.01) with ESMTP id SAA21628; Tue, 23 Jan 2001 18:46:04 -0600 Message-ID: <3A6E257E.E522FD37@us.ibm.com> Date: Tue, 23 Jan 2001 18:44:46 -0600 From: Jon Grimm Organization: IBM X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: devfs , jgrimm@us.ibm.com Subject: non-DevFS behavior of devfs_register returns NULL; seems backwords Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Hi, Working a new driver and am using the devfs_* APIs right from the start. I like the inlined compatibility functions that are provided when the kernel is not configured to build devfs support, however ..... I noticed that the inlined devfs_register API returns a NULL. Unfortunately, this return code matches the error condition of devfs_register. So my error routines kick in on a non-DevFS build. Could devfs_register ever fail? I don't see many examples of checking the returned handle in other driver source, but I'm try hard to check advertised failure behavior. I could put #ifdef CONFIG_DEVFS_FS in my code, but this would seem to defeat the purpose of the compatibility macros, as well as, introduce a (minor) future maintenance issue if CONFIG_DEVFS_FS goes away with DevFS becoming mainstream. Would there be other side-effects to returning a non-NULL return code. Is it worth the trouble? Any opinions? Regards, Jon Grimm jgrimm@us.ibm.com From owner-devfs@oss.sgi.com Tue Jan 23 17:05:52 2001 Received: by oss.sgi.com id ; Tue, 23 Jan 2001 17:05:32 -0800 Received: from mr14.vic-remote.bigpond.net.au ([24.192.1.29]:53445 "EHLO mr14.vic-remote.bigpond.net.au") by oss.sgi.com with ESMTP id ; Tue, 23 Jan 2001 17:05:15 -0800 Received: from mobilix.atnf.CSIRO.AU (CPE-61-9-177-149.vic.bigpond.net.au [61.9.177.149]) by mr14.vic-remote.bigpond.net.au (Pro-8.9.3/8.9.3) with ESMTP id MAA05310; Wed, 24 Jan 2001 12:05:01 +1100 (EDT) Received: (from rgooch@localhost) by mobilix.atnf.CSIRO.AU (8.10.0/8.10.0) id f0O16B401031; Wed, 24 Jan 2001 12:06:11 +1100 Date: Wed, 24 Jan 2001 12:06:11 +1100 Message-Id: <200101240106.f0O16B401031@mobilix.atnf.CSIRO.AU> From: Richard Gooch To: Jon Grimm Cc: devfs Subject: Re: non-DevFS behavior of devfs_register returns NULL; seems backwords In-Reply-To: <3A6E257E.E522FD37@us.ibm.com> References: <3A6E257E.E522FD37@us.ibm.com> Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Jon Grimm writes: > Hi, > Working a new driver and am using the devfs_* APIs right from the > start. I like the inlined compatibility functions that are provided > when the kernel is not configured to build devfs support, however ..... > > I noticed that the inlined devfs_register API returns a NULL. > Unfortunately, this return code matches the error condition of > devfs_register. So my error routines kick in on a non-DevFS build. > > Could devfs_register ever fail? I don't see many examples of > checking the returned handle in other driver source, but I'm try > hard to check advertised failure behavior. I could put #ifdef > CONFIG_DEVFS_FS in my code, but this would seem to defeat the > purpose of the compatibility macros, as well as, introduce a (minor) > future maintenance issue if CONFIG_DEVFS_FS goes away with DevFS > becoming mainstream. devfs_register() could fail for a number of reasons, including lack of memory. It should generate a message on error. > Would there be other side-effects to returning a non-NULL return code. > Is it worth the trouble? The devfs API is designed to ignore NULL entry pointers, so it's safe to call devfs_register() and pass the result to another function. So don't generate your own message if you get NULL. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Wed Jan 24 06:41:05 2001 Received: by oss.sgi.com id ; Wed, 24 Jan 2001 06:40:56 -0800 Received: from e21.nc.us.ibm.com ([32.97.136.227]:38134 "EHLO e21.nc.us.ibm.com") by oss.sgi.com with ESMTP id ; Wed, 24 Jan 2001 06:40:45 -0800 Received: from southrelay01.raleigh.ibm.com (southrelay01.raleigh.ibm.com [9.37.3.208]) by e21.nc.us.ibm.com (8.9.3/8.9.3) with ESMTP id JAA31340; Wed, 24 Jan 2001 09:36:50 -0600 Received: from d04nm202.raleigh.ibm.com (d04nm202.raleigh.ibm.com [9.67.228.39]) by southrelay01.raleigh.ibm.com (8.8.8m3/NCO v4.95) with ESMTP id JAA36266; Wed, 24 Jan 2001 09:40:27 -0500 Importance: Normal Subject: Re: non-DevFS behavior of devfs_register returns NULL; seems backwords To: Richard Gooch Cc: devfs X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000 Message-ID: From: "Jon Grimm" Date: Wed, 24 Jan 2001 08:39:06 -0600 X-MIMETrack: Serialize by Router on D04NM202/04/M/IBM(Release 5.0.3 (Intl)|21 March 2000) at 01/24/2001 09:40:41 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Richard, I do not believe I described my dilema sufficiently. DevFS works just fine. When I am _not_ building with CONFIG_DEVFS_FS, the 'devfs_fs_kernel.h' defines some inline functions for compatibility. The inline function for devfs_register returns NULL. So for example: handle = devfs_register(NULL, "myname", DEVFS_FL_NONE, major, 0, S_IFCHR|S_IRUGO, &fops, NULL); if(!handle) goto err_register; Building with CONFIG_DEVFS_FS, the code works fine, building without does not. I think the inline compat. function for devfs_register should return something non-NULL. Otherwise, it seems to defeat the purpose of having those compatibility functions. Thanks for the response. I does seem from your note, that there can be situations were this routine will fail. Jon Grimm, (or better known as the goof who did not spellcheck 'backwords') jgrimm@us.ibm.com To: Jon Grimm/Austin/IBM@IBMUS cc: devfs Subject: Re: non-DevFS behavior of devfs_register returns NULL; seems backwords Jon Grimm writes: > Hi, > Working a new driver and am using the devfs_* APIs right from the > start. I like the inlined compatibility functions that are provided > when the kernel is not configured to build devfs support, however ..... > > I noticed that the inlined devfs_register API returns a NULL. > Unfortunately, this return code matches the error condition of > devfs_register. So my error routines kick in on a non-DevFS build. > > Could devfs_register ever fail? I don't see many examples of > checking the returned handle in other driver source, but I'm try > hard to check advertised failure behavior. I could put #ifdef > CONFIG_DEVFS_FS in my code, but this would seem to defeat the > purpose of the compatibility macros, as well as, introduce a (minor) > future maintenance issue if CONFIG_DEVFS_FS goes away with DevFS > becoming mainstream. devfs_register() could fail for a number of reasons, including lack of memory. It should generate a message on error. > Would there be other side-effects to returning a non-NULL return code. > Is it worth the trouble? The devfs API is designed to ignore NULL entry pointers, so it's safe to call devfs_register() and pass the result to another function. So don't generate your own message if you get NULL. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Wed Jan 24 07:08:46 2001 Received: by oss.sgi.com id ; Wed, 24 Jan 2001 07:08:36 -0800 Received: from sog.britgas.co.uk ([193.133.101.2]:33430 "HELO sog.service.britgas.co.uk") by oss.sgi.com with SMTP id ; Wed, 24 Jan 2001 07:08:08 -0800 Received: by sog.service.britgas.co.uk (Postfix, from userid 5) id 88B682D23; Wed, 24 Jan 2001 15:11:04 +0000 (GMT) Received: from unknown(10.16.26.118) by sog.service.britgas.co.uk via smap (V5.5) id xma028054; Wed, 24 Jan 01 15:10:53 GMT Received: from phx.mjr.org (phx.service.britgas.co.uk [93.224.233.12]) by cenproxy-tc.service.britgas.co.uk (Postfix) with ESMTP id 4EB8632BE6 for ; Wed, 24 Jan 2001 15:08:25 +0000 (GMT) Received: by phx.mjr.org (Postfix, from userid 997) id 9AD61A884; Wed, 24 Jan 2001 15:07:44 +0000 (GMT) Date: Wed, 24 Jan 2001 15:07:44 +0000 From: Paul Hedderly To: devfs Subject: devfs for 2.2.18 - any chance? Message-ID: <20010124150744.E25328@phx.mjr.org> Mail-Followup-To: devfs Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.12i Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing The subject says it all. I couldn't get devfs working with 2218. -- Regards, Paul From owner-devfs@oss.sgi.com Wed Jan 24 07:22:56 2001 Received: by oss.sgi.com id ; Wed, 24 Jan 2001 07:22:46 -0800 Received: from e23.nc.us.ibm.com ([32.97.136.229]:40643 "EHLO e23.nc.us.ibm.com") by oss.sgi.com with ESMTP id ; Wed, 24 Jan 2001 07:22:31 -0800 Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.ibm.com [9.37.3.209]) by e23.nc.us.ibm.com (8.9.3/8.9.3) with ESMTP id KAA10674; Wed, 24 Jan 2001 10:17:40 -0600 Received: from d04nm202.raleigh.ibm.com (d04nm202.raleigh.ibm.com [9.67.228.39]) by southrelay02.raleigh.ibm.com (8.11.1/NCO v4.95) with ESMTP id f0OFMKN29462; Wed, 24 Jan 2001 10:22:20 -0500 Importance: Normal Subject: Re: non-DevFS behavior of devfs_register returns NULL; seems backwords To: devfs Cc: rgooch@atnf.csiro.au X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000 Message-ID: From: "Jon Grimm" Date: Wed, 24 Jan 2001 09:20:53 -0600 X-MIMETrack: Serialize by Router on D04NM202/04/M/IBM(Release 5.0.3 (Intl)|21 March 2000) at 01/24/2001 10:22:20 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing On a similar note: How would one programatically know that devfs_register_series failed? I can't very well take any sort of action if I don't know there is a problem. I have another module (doesn't actually drive hardware), that if this or other similar initialization steps were to fail it really would have no point in continuing and should fail to init/load. Since devfs_register_series works on a whole series of entries, I'm not quite sure what could be returned; maybe the parent dir with NULL on error? maybe an rc? Regards, Jon Grimm jgrimm@us.ibm.com To: Jon Grimm/Austin/IBM@IBMUS cc: devfs Subject: Re: non-DevFS behavior of devfs_register returns NULL; seems backwords Jon Grimm writes: > Hi, > Working a new driver and am using the devfs_* APIs right from the > start. I like the inlined compatibility functions that are provided > when the kernel is not configured to build devfs support, however ..... > > I noticed that the inlined devfs_register API returns a NULL. > Unfortunately, this return code matches the error condition of > devfs_register. So my error routines kick in on a non-DevFS build. > > Could devfs_register ever fail? I don't see many examples of > checking the returned handle in other driver source, but I'm try > hard to check advertised failure behavior. I could put #ifdef > CONFIG_DEVFS_FS in my code, but this would seem to defeat the > purpose of the compatibility macros, as well as, introduce a (minor) > future maintenance issue if CONFIG_DEVFS_FS goes away with DevFS > becoming mainstream. devfs_register() could fail for a number of reasons, including lack of memory. It should generate a message on error. > Would there be other side-effects to returning a non-NULL return code. > Is it worth the trouble? The devfs API is designed to ignore NULL entry pointers, so it's safe to call devfs_register() and pass the result to another function. So don't generate your own message if you get NULL. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Wed Jan 24 12:00:47 2001 Received: by oss.sgi.com id ; Wed, 24 Jan 2001 12:00:27 -0800 Received: from crux.tip.CSIRO.AU ([130.155.194.32]:58884 "EHLO crux.tip.CSIRO.AU") by oss.sgi.com with ESMTP id ; Wed, 24 Jan 2001 12:00:00 -0800 Received: from mobilix.atnf.CSIRO.AU (insomniax.atnf.CSIRO.AU [130.155.200.3]) by crux.tip.CSIRO.AU (8.9.3/8.9.3/TIPAT-1.1e) with ESMTP id GAA03200; Thu, 25 Jan 2001 06:59:50 +1100 (EST) Received: (from rgooch@localhost) by mobilix.atnf.CSIRO.AU (8.10.0/8.10.0) id f0OJxl701579; Thu, 25 Jan 2001 06:59:47 +1100 Date: Thu, 25 Jan 2001 06:59:47 +1100 Message-Id: <200101241959.f0OJxl701579@mobilix.atnf.CSIRO.AU> From: Richard Gooch To: Paul Hedderly Cc: devfs Subject: Re: devfs for 2.2.18 - any chance? In-Reply-To: <20010124150744.E25328@phx.mjr.org> References: <20010124150744.E25328@phx.mjr.org> Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Paul Hedderly writes: > The subject says it all. I couldn't get devfs working with 2218. Wait. I'll be producing a patch. NOTE to John Grimm (?). The email I sent to you was lost. Just ignore error codes. That should work for both cases. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Wed Jan 24 12:32:57 2001 Received: by oss.sgi.com id ; Wed, 24 Jan 2001 12:32:47 -0800 Received: from e24.nc.us.ibm.com ([32.97.136.230]:16102 "EHLO e24.nc.us.ibm.com") by oss.sgi.com with ESMTP id ; Wed, 24 Jan 2001 12:32:28 -0800 Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.ibm.com [9.37.3.209]) by e24.nc.us.ibm.com (8.9.3/8.9.3) with ESMTP id PAA23520; Wed, 24 Jan 2001 15:33:28 -0600 Received: from d04nm202.raleigh.ibm.com (d04nm202.raleigh.ibm.com [9.67.228.39]) by southrelay02.raleigh.ibm.com (8.11.1/NCO v4.95) with ESMTP id f0OKWPN25230; Wed, 24 Jan 2001 15:32:25 -0500 X-Priority: 3 (Normal) Importance: Normal Subject: Ignoring devfs_register return codes To: Richard Gooch Cc: devfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000 Message-ID: From: "Jon Grimm" Date: Wed, 24 Jan 2001 14:31:02 -0600 X-MIMETrack: Serialize by Router on D04NM202/04/M/IBM(Release 5.0.3 (Intl)|21 March 2000) at 01/24/2001 03:32:25 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Richard, I got your stealth comment below: However...... I believe you said there times when devfs_register could return NULL (e.g. out of memory??). In some cases, this would be an indicator to back out/unload. I have a module that matches that criteria. No use having the module loaded (and using up some variety of resources) if an application cannot access it. Depending on the envinonment, this may or may not be highly theoretical. As a workaround, I did just as you suggested, ignoring the return code. Looking at the drivers in the kernel source, they all seem to do this anyway. I'll just comment this caveat in the drivers' code. Regards, Jon Grimm jgrimm@us.ibm.com Sent by: owner-devfs@oss.sgi.com To: Paul Hedderly cc: devfs Subject: Re: devfs for 2.2.18 - any chance? Paul Hedderly writes: > The subject says it all. I couldn't get devfs working with 2218. Wait. I'll be producing a patch. NOTE to John Grimm (?). The email I sent to you was lost. Just ignore error codes. That should work for both cases. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Thu Jan 25 13:45:19 2001 Received: by oss.sgi.com id ; Thu, 25 Jan 2001 13:45:10 -0800 Received: from smtppop2pub.gte.net ([206.46.170.21]:1561 "EHLO smtppop2pub.verizon.net") by oss.sgi.com with ESMTP id ; Thu, 25 Jan 2001 13:44:57 -0800 Received: from cherrycoke.gte.net (1Cust69.tnt2.fort-wayne.in.da.uu.net [63.25.79.69]) by smtppop2pub.verizon.net with SMTP for ; id PAA86330215 Thu, 25 Jan 2001 15:44:32 -0600 (CST) Received: (qmail 677 invoked by uid 1000); 25 Jan 2001 21:50:17 -0000 From: "Kurt V. Hindenburg" Date: Thu, 25 Jan 2001 16:50:17 -0500 To: DevFS Subject: psmouse Message-ID: <20010125165017.A657@amdk7.gte.net> Reply-To: k.hindenburg@gte.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.9i Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing I can't get my ps mouse to work under devfs (w/o devfsd). The mouse was normally /dev/psmouse. Should devfs automatically create psmouse? Kurt From owner-devfs@oss.sgi.com Thu Jan 25 13:52:50 2001 Received: by oss.sgi.com id ; Thu, 25 Jan 2001 13:52:31 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:60686 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 25 Jan 2001 13:52:27 -0800 Received: from cthulhu.engr.sgi.com (gate3-relay.engr.sgi.com [130.62.1.234]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id NAA16628 for ; Thu, 25 Jan 2001 13:51:29 -0800 (PST) mail_from (tduffy@engr.sgi.com) Received: from dbear.engr.sgi.com (dbear.engr.sgi.com [163.154.18.85]) by cthulhu.engr.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id NAA32954; Thu, 25 Jan 2001 13:51:10 -0800 (PST) Date: Thu, 25 Jan 2001 13:49:14 -0800 (PST) From: Tom Duffy To: "Kurt V. Hindenburg" cc: DevFS Subject: Re: psmouse In-Reply-To: <20010125165017.A657@amdk7.gte.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing On Thu, 25 Jan 2001, Kurt V. Hindenburg wrote: > I can't get my ps mouse to work under devfs (w/o devfsd). The mouse was > normally /dev/psmouse. Should devfs automatically create psmouse? no, it creates /dev/misc/psaux -tduffy From owner-devfs@oss.sgi.com Sat Jan 27 18:28:44 2001 Received: by oss.sgi.com id ; Sat, 27 Jan 2001 18:28:35 -0800 Received: from Huntington-Beach.Blue-Labs.org ([208.179.0.198]:5948 "EHLO Huntington-Beach.Blue-Labs.org") by oss.sgi.com with ESMTP id ; Sat, 27 Jan 2001 18:28:13 -0800 Received: from linux.com (david@localhost [127.0.0.1]) by Huntington-Beach.Blue-Labs.org (8.11.0/8.11.0) with ESMTP id f0S2S3c09925; Sun, 28 Jan 2001 02:28:05 GMT Message-ID: <3A7383B2.19DDD006@linux.com> Date: Sun, 28 Jan 2001 02:28:03 +0000 From: David Ford Organization: Blue Labs Software X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.0-ac12 i686) X-Accept-Language: en MIME-Version: 1.0 To: devfs@oss.sgi.com, rgooch@atnf.csiro.au CC: LKML Subject: [PATCH] devfsd, compiling on glibc22x Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing This patch is simple, defines RTLD_NEXT if not previously defined. --- devfsd.c.orig Sat Jan 27 18:14:19 2001 +++ devfsd.c Sat Jan 27 18:15:46 2001 @@ -165,6 +165,7 @@ Last updated by Richard Gooch 3-JUL-2000: Added "-C /etc/modules.devfs" when calling modprobe(8). Fail if a configuration line has EXECUTE modprobe. + Updated by David Ford 27-JAN-2001: Added RTLD_NEXT define */ #include @@ -221,6 +222,10 @@ #define AC_MKNEWCOMPAT 8 #define AC_RMOLDCOMPAT 9 #define AC_RMNEWCOMPAT 10 + +#ifndef RTLD_NEXT +# define RTLD_NEXT ((void *) -1l) +#endif struct permissions_type { -- There is a natural aristocracy among men. The grounds of this are virtue and talents. Thomas Jefferson The good thing about standards is that there are so many to choose from. Andrew S. Tanenbaum From owner-devfs@oss.sgi.com Sat Jan 27 22:54:45 2001 Received: by oss.sgi.com id ; Sat, 27 Jan 2001 22:54:25 -0800 Received: from smtp-rt-5.wanadoo.fr ([193.252.19.159]:28394 "EHLO bassia.wanadoo.fr") by oss.sgi.com with ESMTP id ; Sat, 27 Jan 2001 22:54:21 -0800 Received: from mahonia.wanadoo.fr (193.252.19.58) by bassia.wanadoo.fr; 28 Jan 2001 07:54:18 +0100 Received: from wanadoo.fr (193.250.128.17) by mahonia.wanadoo.fr; 28 Jan 2001 07:54:18 +0100 Message-ID: <3A73C1D8.578AEEE@wanadoo.fr> Date: Sun, 28 Jan 2001 07:53:12 +0100 From: Pierre Rousselet Organization: Home PC X-Mailer: Mozilla 4.76 [fr] (X11; U; Linux 2.4.1-pre10 i686) X-Accept-Language: en MIME-Version: 1.0 To: David Ford CC: devfs@oss.sgi.com, rgooch@atnf.csiro.au, LKML Subject: Re: [PATCH] devfsd, compiling on glibc22x References: <3A7383B2.19DDD006@linux.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing David Ford wrote: > > This patch is simple, defines RTLD_NEXT if not previously defined. > > --- devfsd.c.orig Sat Jan 27 18:14:19 2001 > +++ devfsd.c Sat Jan 27 18:15:46 2001 > @@ -165,6 +165,7 @@ > Last updated by Richard Gooch 3-JUL-2000: Added "-C > /etc/modules.devfs" > when calling modprobe(8). Fail if a configuration line has EXECUTE > modprobe. > > + Updated by David Ford 27-JAN-2001: Added RTLD_NEXT define > > */ > #include > @@ -221,6 +222,10 @@ > #define AC_MKNEWCOMPAT 8 > #define AC_RMOLDCOMPAT 9 > #define AC_RMNEWCOMPAT 10 > + > +#ifndef RTLD_NEXT > +# define RTLD_NEXT ((void *) -1l) > +#endif > > struct permissions_type > { for me : make CFLAGS='-O2 -I. -D_GNU_SOURCE' compiles without any patch. is it correct ? -- ------------------------------------------------ Pierre Rousselet ------------------------------------------------ From owner-devfs@oss.sgi.com Sat Jan 27 23:28:46 2001 Received: by oss.sgi.com id ; Sat, 27 Jan 2001 23:28:26 -0800 Received: from runyon.cygnus.com ([205.180.230.5]:21969 "EHLO cygnus.com") by oss.sgi.com with ESMTP id ; Sat, 27 Jan 2001 23:27:54 -0800 Received: from otr.mynet (dialin-sv-02.cygnus.com [205.180.231.52]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id XAA13209; Sat, 27 Jan 2001 23:27:34 -0800 (PST) Received: by otr.mynet (Postfix, from userid 500) id A337230BD; Sat, 27 Jan 2001 23:27:56 -0800 (PST) To: Pierre Rousselet Cc: David Ford , devfs@oss.sgi.com, rgooch@atnf.csiro.au, LKML Subject: Re: [PATCH] devfsd, compiling on glibc22x References: <3A7383B2.19DDD006@linux.com> <3A73C1D8.578AEEE@wanadoo.fr> Reply-To: drepper@cygnus.com (Ulrich Drepper) X-fingerprint: BE 3B 21 04 BC 77 AC F0 61 92 E4 CB AC DD B9 5A From: Ulrich Drepper Date: 27 Jan 2001 23:27:56 -0800 In-Reply-To: Pierre Rousselet's message of "Sun, 28 Jan 2001 07:53:12 +0100" Message-ID: Lines: 13 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Capitol Reef) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Pierre Rousselet writes: > for me : > make CFLAGS='-O2 -I. -D_GNU_SOURCE' > compiles without any patch. is it correct ? Yes. RTLD_NEXT is not in any standard, it's an extension available via -D_GNU_SOURCE. -- ---------------. ,-. 1325 Chesapeake Terrace Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com `------------------------ From owner-devfs@oss.sgi.com Sun Jan 28 02:10:36 2001 Received: by oss.sgi.com id ; Sun, 28 Jan 2001 02:10:27 -0800 Received: from Huntington-Beach.Blue-Labs.org ([208.179.0.198]:31299 "EHLO Huntington-Beach.Blue-Labs.org") by oss.sgi.com with ESMTP id ; Sun, 28 Jan 2001 02:10:01 -0800 Received: from linux.com (david@localhost [127.0.0.1]) by Huntington-Beach.Blue-Labs.org (8.11.0/8.11.0) with ESMTP id f0SA9jc12648; Sun, 28 Jan 2001 10:09:46 GMT Message-ID: <3A73EFE8.3FB7BEC0@linux.com> Date: Sun, 28 Jan 2001 10:09:44 +0000 From: David Ford Organization: Blue Labs Software X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.0-ac12 i686) X-Accept-Language: en MIME-Version: 1.0 To: Ulrich Drepper CC: Pierre Rousselet , devfs@oss.sgi.com, rgooch@atnf.csiro.au, LKML Subject: Re: [PATCH] devfsd, compiling on glibc22x References: <3A7383B2.19DDD006@linux.com> <3A73C1D8.578AEEE@wanadoo.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Ulrich Drepper wrote: > Pierre Rousselet writes: > > > for me : > > make CFLAGS='-O2 -I. -D_GNU_SOURCE' > > compiles without any patch. is it correct ? > > Yes. RTLD_NEXT is not in any standard, it's an extension available > via -D_GNU_SOURCE. Ok, how about we all tag Richard until he adds that to the makefile? :) -d -- There is a natural aristocracy among men. The grounds of this are virtue and talents. Thomas Jefferson The good thing about standards is that there are so many to choose from. Andrew S. Tanenbaum From owner-devfs@oss.sgi.com Sun Jan 28 18:20:25 2001 Received: by oss.sgi.com id ; Sun, 28 Jan 2001 18:20:04 -0800 Received: from saturn.cs.uml.edu ([129.63.8.2]:6665 "EHLO saturn.cs.uml.edu") by oss.sgi.com with ESMTP id ; Sun, 28 Jan 2001 18:19:34 -0800 Received: (from acahalan@localhost) by saturn.cs.uml.edu (8.11.0/8.10.0) id f0T2JCF439854; Sun, 28 Jan 2001 21:19:12 -0500 (EST) From: "Albert D. Cahalan" Message-Id: <200101290219.f0T2JCF439854@saturn.cs.uml.edu> Subject: Re: [PATCH] devfsd, compiling on glibc22x To: drepper@cygnus.com Date: Sun, 28 Jan 2001 21:19:12 -0500 (EST) Cc: pierre.rousselet@wanadoo.fr (Pierre Rousselet), david@linux.com (David Ford), devfs@oss.sgi.com, rgooch@atnf.csiro.au, linux-kernel@vger.kernel.org (LKML) In-Reply-To: from "Ulrich Drepper" at Jan 27, 2001 11:27:56 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Ulrich Drepper writes: > Pierre Rousselet writes: > >> for me : >> make CFLAGS='-O2 -I. -D_GNU_SOURCE' >> compiles without any patch. is it correct ? > > Yes. RTLD_NEXT is not in any standard, it's an extension available > via -D_GNU_SOURCE. This isn't a HURD feature. This isn't even a C library feature. This is a Linux feature. So the _GNU_SOURCE thing is just plain wrong. Quit trying to rename the OS. Since there are so many standards to choose from, putting all features into the default would be most obvious. Else what, pure C89 maybe? Dang new-fangled standards might break something. Normal UNIX systems don't make developers jump through hoops to get access to stuff; they instead provide clean namespaces upon request.