From owner-devfs@oss.sgi.com Mon Jul 1 20:16:24 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g623GOnC025027 for ; Mon, 1 Jul 2002 20:16:24 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g623GOE6025026 for devfs-outgoing; Mon, 1 Jul 2002 20:16:24 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f Received: from mobilix.ras.ucalgary.ca (h-207-228-73-44.gen.cadvision.com [207.228.73.44]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g623GInC025018 for ; Mon, 1 Jul 2002 20:16:18 -0700 Received: (from rgooch@localhost) by mobilix.ras.ucalgary.ca (8.10.0/8.10.0) id g5UNuBl00803; Sun, 30 Jun 2002 17:56:11 -0600 Date: Sun, 30 Jun 2002 17:56:11 -0600 Message-Id: <200206302356.g5UNuBl00803@mobilix.ras.ucalgary.ca> From: Richard Gooch To: "Luo, Ling" Cc: devfs@oss.sgi.com Subject: Re: Devfs & /dev permission persistence In-Reply-To: References: Sender: owner-devfs@oss.sgi.com Precedence: bulk Ling Luo writes: > According to the devfs.readme, I disabled the devfs automount at > boot time to enable dev file permission persistence to work( with > /dev-state etc, etc). However doing that brought up the "Unable to > open initial console" warning message, it also messed up my serial > console output( undecipherable symbols jam the whole screen while > rebooting). I tried the proposed solution: a hack to the init > program( I have initctl file under /dev before). It didn't change > the outcome. I'll update the FAQ about this. It looks like you don't have a valid /dev/console entry in your root file-system. Make one. > Alternatively, I reenabled the automounting devfs at boot time, > commented out "mount --bind /dev-state /dev" in the rc scripts, and You've got that reversed! It's: mount --bind /dev /dev-state Did you mean what you wrote, or is that a typo? If you meant that, it's no wonder you have a problem! > left the permission persistence configurations enabled in the > devfsd.conf. Everything seem to work fine now: dev file permission > persistence is working, "Unable to open initial console" warning is > gone, and my serial console output is back to normal. Since this is > different from what was suggested in the readme, just want to make > sure this won't have other side effects. This is safe, just not as tidy and convenient, as you can't switch back and forth between devfs and non-devfs without having to move entries between /dev and /dev-state (I'm assuming you made a typo above). Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Fri Jul 5 03:59:55 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g65AxtRw017621 for ; Fri, 5 Jul 2002 03:59:55 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g65AxsGY017620 for devfs-outgoing; Fri, 5 Jul 2002 03:59:54 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f Received: from blue.net4u.hr (qmailr@blue.net4u.hr [193.110.68.3]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g65AxgRw017587 for ; Fri, 5 Jul 2002 03:59:46 -0700 Received: (qmail 11763 invoked by uid 104); 5 Jul 2002 11:03:33 -0000 Received: from mr.tvrtko@inet.hr by blue.net4u.hr by uid 101 with qmail-scanner-1.10 (F-PROT: 3.11 fsecure: 4.11/3190/2002-07-03/2002-07-03. 2002-07-02/. Clear:0. Processed in 0.607047 secs); 05 Jul 2002 11:03:33 -0000 Received: from unknown (HELO green.net4u.hr) (193.110.68.8) by blue.net4u.hr with SMTP; 5 Jul 2002 11:03:32 -0000 Received: (qmail 17673 invoked from network); 5 Jul 2002 11:03:36 -0000 Received: from unknown (HELO equinoxe.tin-labs.hr) (193.110.70.156) by green.net4u.hr with SMTP; 5 Jul 2002 11:03:36 -0000 Received: from equinoxe (localhost [127.0.0.1]) by equinoxe.tin-labs.hr (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id g659hroc020147 for ; Fri, 5 Jul 2002 11:43:53 +0200 Content-Type: text/plain; charset="us-ascii" From: Tvrtko Ursulin Organization: Tin-Labs Ltd. To: devfs@oss.sgi.com Subject: devfs fails to start Date: Fri, 5 Jul 2002 11:43:53 +0200 User-Agent: KMail/1.4.1 MIME-Version: 1.0 Message-Id: <200207051143.53574.mr.tvrtko@inet.hr> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id g65AxoRw017603 Sender: owner-devfs@oss.sgi.com Precedence: bulk Hi! I get this error when starting devfsd under SuSE 8.0 : equinoxe:~ # devfsd /devfs Started device management daemon v1.3.23 for /devfs error loading: "/lib/security/pam_console_apply_devfsd.so" /lib/security/pam_console_apply_devfsd.so: cannot open shared object file: No such file or directory I have the following packages installed: pam-0.75-180.i386.rpm pam-modules-2002.3.9-11.i386.rpm Recompiling for devfsd latest source does not help, the error is the same. How can I solve this? Also, on the other subject: Somewhere I found an article on using init wrapper script for full devfs compatibilit/usability. Is this still necessary or this is outdated? Thanks, Tvrtko From owner-devfs@oss.sgi.com Fri Jul 5 04:11:12 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g65BBCRw018130 for ; Fri, 5 Jul 2002 04:11:12 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g65BBCru018129 for devfs-outgoing; Fri, 5 Jul 2002 04:11:12 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f 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 g65BB7Rw018126 for ; Fri, 5 Jul 2002 04:11:08 -0700 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 g65BFDD09394; Fri, 5 Jul 2002 13:15:13 +0200 (MEST) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g65BFCP22423; Fri, 5 Jul 2002 13:15:12 +0200 (MEST) Received: by mowd019a.mow.siemens.ru with Internet Mail Service (5.5.2653.19) id <3209MFTN>; Fri, 5 Jul 2002 15:23:06 +0400 Received: from MW2B210C ([163.242.193.63]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 3209MFTM; Fri, 5 Jul 2002 15:23:01 +0400 From: Borsenkow Andrej To: "'Tvrtko Ursulin'" , devfs@oss.sgi.com Subject: RE: devfs fails to start Date: Fri, 5 Jul 2002 15:15:05 +0400 Message-ID: <6134254DE87BD411908B00A0C99B044F03A0B339@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.3416 In-Reply-To: <200207051143.53574.mr.tvrtko@inet.hr> x-mimeole: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: owner-devfs@oss.sgi.com Precedence: bulk > I get this error when starting devfsd under SuSE 8.0 : > > equinoxe:~ # devfsd /devfs > Started device management daemon v1.3.23 for /devfs > error loading: "/lib/security/pam_console_apply_devfsd.so" > /lib/security/pam_console_apply_devfsd.so: cannot open shared object file: > No > such file or directory > > I have the following packages installed: > > pam-0.75-180.i386.rpm > pam-modules-2002.3.9-11.i386.rpm > > Recompiling for devfsd latest source does not help, the error is the same. > > How can I solve this? > add required module or remove it from devfsd.conf. -andrej From owner-devfs@oss.sgi.com Fri Jul 5 23:43:42 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g666hgRw017329 for ; Fri, 5 Jul 2002 23:43:42 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g666hg2P017328 for devfs-outgoing; Fri, 5 Jul 2002 23:43:42 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f Received: from blue.net4u.hr (qmailr@blue.net4u.hr [193.110.68.3]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g666hcRw017325 for ; Fri, 5 Jul 2002 23:43:39 -0700 Received: (qmail 22990 invoked by uid 104); 6 Jul 2002 06:47:43 -0000 Received: from mr.tvrtko@inet.hr by blue.net4u.hr by uid 101 with qmail-scanner-1.10 (F-PROT: 3.11 fsecure: 4.11/3190/2002-07-05/2002-07-05. 2002-07-05/. Clear:0. Processed in 1.170661 secs); 06 Jul 2002 06:47:43 -0000 Received: from unknown (HELO green.net4u.hr) (193.110.68.8) by blue.net4u.hr with SMTP; 6 Jul 2002 06:47:41 -0000 Received: (qmail 10346 invoked from network); 6 Jul 2002 06:47:43 -0000 Received: from unknown (HELO equinoxe.tin-labs.hr) (193.110.71.45) by green.net4u.hr with SMTP; 6 Jul 2002 06:47:43 -0000 Received: from equinoxe (localhost [127.0.0.1]) by equinoxe.tin-labs.hr (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id g666jdoc030560; Sat, 6 Jul 2002 08:45:39 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Tvrtko Ursulin Organization: Tin-Labs Ltd. To: Borsenkow Andrej , devfs@oss.sgi.com Subject: Re: devfs fails to start Date: Sat, 6 Jul 2002 08:45:39 +0200 User-Agent: KMail/1.4.1 References: <6134254DE87BD411908B00A0C99B044F03A0B339@mowd019a.mow.siemens.ru> In-Reply-To: <6134254DE87BD411908B00A0C99B044F03A0B339@mowd019a.mow.siemens.ru> MIME-Version: 1.0 Message-Id: <200207060845.39094.mr.tvrtko@inet.hr> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id g666heRw017326 Sender: owner-devfs@oss.sgi.com Precedence: bulk > > /lib/security/pam_console_apply_devfsd.so: cannot open shared object > > add required module or remove it from devfsd.conf. What doead this module do? And why it its in default config file when module is not available by deafault also? From owner-devfs@oss.sgi.com Sat Jul 6 02:04:12 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g6694CRw018021 for ; Sat, 6 Jul 2002 02:04:12 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g6694Cpe018020 for devfs-outgoing; Sat, 6 Jul 2002 02:04:12 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f 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 g66947Rw018017 for ; Sat, 6 Jul 2002 02:04:08 -0700 Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.sbs.de (8.11.6/8.11.6) with ESMTP id g6698Hv11506; Sat, 6 Jul 2002 11:08:17 +0200 (MEST) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g6698GP29952; Sat, 6 Jul 2002 11:08:16 +0200 (MEST) Received: by mowd019a.mow.siemens.ru with Internet Mail Service (5.5.2653.19) id <3LBSF8RZ>; Sat, 6 Jul 2002 13:16:11 +0400 Received: from [163.242.193.99] (163.242.193.99 [163.242.193.99]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 3LBSF8RY; Sat, 6 Jul 2002 13:16:09 +0400 From: Borsenkow Andrej To: Tvrtko Ursulin Cc: devfs mailing list Subject: Re: devfs fails to start In-Reply-To: <200207060845.39094.mr.tvrtko@inet.hr> References: <6134254DE87BD411908B00A0C99B044F03A0B339@mowd019a.mow.siemens.ru> <200207060845.39094.mr.tvrtko@inet.hr> Content-Type: text/plain; charset=KOI8-R X-Mailer: Ximian Evolution 1.0.8-1mdk Date: 06 Jul 2002 13:08:09 +0400 Message-Id: <1025946495.2497.14.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id g66948Rw018018 Sender: owner-devfs@oss.sgi.com Precedence: bulk ÷ óÂÔ, 06.07.2002, × 10:45, Tvrtko Ursulin ÎÁÐÉÓÁÌ: > > > > /lib/security/pam_console_apply_devfsd.so: cannot open shared object > > > > add required module or remove it from devfsd.conf. > > What doead this module do? It sets permissions on newly registered device nodes according to pam_console configuration. And why it its in default config file when module > is not available by deafault also? > Should not you ask SuSE about it? In default devfsd.conf this is commented out to my best knowledge. -andrej From owner-devfs@oss.sgi.com Sun Jul 14 10:33:58 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g6EHXwRw012257 for ; Sun, 14 Jul 2002 10:33:58 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g6EHXwRk012256 for devfs-outgoing; Sun, 14 Jul 2002 10:33:58 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f Received: from hotmail.com (f114.law15.hotmail.com [64.4.23.114]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g6EHXrRw012253 for ; Sun, 14 Jul 2002 10:33:53 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 14 Jul 2002 10:38:35 -0700 Received: from 195.92.168.166 by lw15fd.law15.hotmail.msn.com with HTTP; Sun, 14 Jul 2002 17:38:34 GMT X-Originating-IP: [195.92.168.166] From: "David Gilbert" To: devfs@oss.sgi.com Subject: Newbie question: running devfsd forces implicit mount of /proc? Date: Sun, 14 Jul 2002 18:38:34 +0100 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 14 Jul 2002 17:38:35.0649 (UTC) FILETIME=[47CEE710:01C22B5D] Sender: owner-devfs@oss.sgi.com Precedence: bulk Hi there, I've just started playing around with devfs and encountered an odd thing (to me anyway)... Once running, I noticed errors from the init scripts about trying to mount /proc. I've disabled the explict mount of /proc to work around the problem. But what's going on? It seems that once devfsd is running there is an implicit mounting of /proc? Is this normal behaviour? BTW - versions are: devfs: v1.10 (20020120) kernel: v2.4.18 devfsd: v1.3.25 Thanks in advanceDavid _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com From owner-devfs@oss.sgi.com Sun Jul 14 12:05:14 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g6EJ5ERw013216 for ; Sun, 14 Jul 2002 12:05:14 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g6EJ5Emk013215 for devfs-outgoing; Sun, 14 Jul 2002 12:05:14 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f Received: from tsv.sws.net.au (tsv.sws.net.au [203.36.46.2]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g6EJ58Rw013189 for ; Sun, 14 Jul 2002 12:05:09 -0700 Received: from lyta.coker.com.au (localhost [127.0.0.1]) by tsv.sws.net.au (Postfix) with ESMTP id 5616192462; Mon, 15 Jul 2002 05:09:52 +1000 (EST) Received: from there (localhost [127.0.0.1]) by lyta.coker.com.au (Postfix) with SMTP id D8109693; Sun, 14 Jul 2002 21:09:41 +0200 (CEST) Content-Type: text/plain; charset="iso-8859-1" From: Russell Coker Reply-To: Russell Coker To: "David Gilbert" , devfs@oss.sgi.com Subject: Re: Newbie question: running devfsd forces implicit mount of /proc? Date: Sun, 14 Jul 2002 21:09:41 +0200 X-Mailer: KMail [version 1.3.2] References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020714190941.D8109693@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk On Sun, 14 Jul 2002 19:38, David Gilbert wrote: > I've just started playing around with devfs and encountered an odd thing > (to me anyway)... > > Once running, I noticed errors from the init scripts about trying to mount > /proc. I've disabled the explict mount of /proc to work around the problem. > But what's going on? It seems that once devfsd is running there is an > implicit mounting of /proc? Is this normal behaviour? You don't mention which distribution you're using, it's probably a distribution issue. My start script for Debian mounts /proc because that's the only way to determine whether it's already running. Why is this a problem? -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the >From field. From owner-devfs@oss.sgi.com Mon Jul 15 11:18:16 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g6FIIGRw007424 for ; Mon, 15 Jul 2002 11:18:16 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g6FIIGe3007423 for devfs-outgoing; Mon, 15 Jul 2002 11:18:16 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g6FII8Rw007420 for ; Mon, 15 Jul 2002 11:18:09 -0700 Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101]) by mail-blue.research.att.com (Postfix) with ESMTP id 86CD04CFF4; Mon, 15 Jul 2002 14:22:55 -0400 (EDT) Received: from dhcp-new174.research.att.com (dhcp-new174.research.att.com [135.207.19.174]) by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id OAA27512; Mon, 15 Jul 2002 14:22:53 -0400 (EDT) Date: Mon, 15 Jul 2002 14:22:53 -0400 (EDT) From: Pavel Roskin X-X-Sender: proski@marabou.research.att.com To: Russell Coker Cc: David Gilbert , Subject: Re: Newbie question: running devfsd forces implicit mount of /proc? In-Reply-To: <20020714190941.D8109693@lyta.coker.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-devfs@oss.sgi.com Precedence: bulk Hello! > > Once running, I noticed errors from the init scripts about trying to mount > > /proc. I've disabled the explict mount of /proc to work around the problem. > > But what's going on? It seems that once devfsd is running there is an > > implicit mounting of /proc? Is this normal behaviour? I don't know the exact reasons, but that's what I see as well (I looked a few months ago). Personally, I have no problems with kernel mounting all the supported "internal" filesystems (procfs, devfs, devptf, usbdevfs) at startup. But the interdependency between devfs and procfs being mounted is indeed weird. Since this feature seems to be undocumented and can go away, I prefer not to rely on it and use the following command to mount procfs if it needs to be mounted: mount -a -t procfs This command doesn't generate any errors if /proc is already mounted. > You don't mention which distribution you're using, it's probably a > distribution issue. It may be a distribution issue, because some distributions try mounting filesystems explicitly at startup, whike others more or less rely on "-a" option to mount. > My start script for Debian mounts /proc because that's the only way to > determine whether it's already running. I don't understand. What is running? To check if /proc is mounted, one can check existance of /proc/mounts - if it's missing, /proc is not mounted. But "mount -a -t procfs" is much more graceful in my opinion. > Why is this a problem? I understand that an error message is a problem - the system should not report errors if everything is Ok. -- Regards, Pavel Roskin From owner-devfs@oss.sgi.com Mon Jul 15 11:28:13 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g6FISCRw007680 for ; Mon, 15 Jul 2002 11:28:13 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g6FISCRq007679 for devfs-outgoing; Mon, 15 Jul 2002 11:28:12 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f Received: from hotmail.com (f222.law15.hotmail.com [64.4.23.222]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g6FIS4Rw007646 for ; Mon, 15 Jul 2002 11:28:04 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 15 Jul 2002 11:32:51 -0700 Received: from 195.92.168.165 by lw15fd.law15.hotmail.msn.com with HTTP; Mon, 15 Jul 2002 18:32:50 GMT X-Originating-IP: [195.92.168.165] From: "David Gilbert" To: russell@coker.com.au, devfs@oss.sgi.com Subject: Re: Newbie question: running devfsd forces implicit mount of /proc? Date: Mon, 15 Jul 2002 19:32:50 +0100 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 15 Jul 2002 18:32:51.0138 (UTC) FILETIME=[06A4DA20:01C22C2E] Sender: owner-devfs@oss.sgi.com Precedence: bulk On 18:31 15/07/02 +0100, Russell Coker wrote: >On Sun, 14 Jul 2002 19:38, David Gilbert wrote: >>I've just started playing around with devfs and encountered an odd thing >>(to me anyway)... >> >>Once running, I noticed errors from the init scripts about trying to mount >>/proc. I've disabled the explict mount of /proc to work around the >>problem. >>But what's going on? It seems that once devfsd is running there is an >>implicit mounting of /proc? Is this normal behaviour? > > >You don't mention which distribution you're using, it's probably a >distribution issue. No, I didn't mention which distro I use because I'm not using a 'packaged' distro - mine is based on Linux from Scratch (yes, I am probably mad ;-) Anyway, I've setup the init script so that running devfsd is the first thing that happens on boot. Oh, I also mount devfs at boot time (CONFIG_DEVFS_MOUNT=y). Finally, I'm not using any compatibility mode in devfsd - just banging the kernel namespace directly (even madder...) >My start script for Debian mounts /proc because that's the only way to >determine whether it's already running. > > >Why is this a problem? Whoops! I wasn't suggesting it was a problem - I'm just trying to understand better what's going on. I have a theory but I dont know how the mechanics work: When devfsd runs, it still creates some symlinks. This happens even though I dont have any REGISTER .* MK[NEW|OLD]COMPAT entries in my devfsd.conf. The key symlink in question is /dev/fd which is a symlink to /proc/self/fd. Now, I assume to make the symlink the target must exist (is this right?), therefore /proc needs to be mounted. So, 'magically' (Hmmm), /proc is mounted. Unfortunately, this is where I run out of it.. I can't find any references to mount(2) in the devfsd code. So how is magic happening?? (I'm also an aetheist...) Just to be sure I wasn't imagining things, I booted my kernel with the 'init=/bin/bash' option to bypass _all_ the init stuff. A quick check of /proc proved that it was not mounted and a check of /dev showed no /dev/fd. I then ran devfsd /dev and sure enough /dev/fd -> /proc/self/fd appeared and /proc was mounted and ready. Any ideas?? _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com From owner-devfs@oss.sgi.com Mon Jul 15 11:42:55 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g6FIgtRw007969 for ; Mon, 15 Jul 2002 11:42:55 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g6FIgtZO007968 for devfs-outgoing; Mon, 15 Jul 2002 11:42:55 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f Received: from hotmail.com (f105.law15.hotmail.com [64.4.23.105]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g6FIgjRw007965 for ; Mon, 15 Jul 2002 11:42:45 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 15 Jul 2002 11:47:32 -0700 Received: from 195.92.168.165 by lw15fd.law15.hotmail.msn.com with HTTP; Mon, 15 Jul 2002 18:47:30 GMT X-Originating-IP: [195.92.168.165] From: "David Gilbert" To: proski@gnu.org Cc: devfs@oss.sgi.com Subject: Re: Newbie question: running devfsd forces implicit mount of /proc? Date: Mon, 15 Jul 2002 19:47:30 +0100 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 15 Jul 2002 18:47:32.0692 (UTC) FILETIME=[14175140:01C22C30] Sender: owner-devfs@oss.sgi.com Precedence: bulk Pavel, Thanks for reassuring me that I'm not losing my marbles. Ditto about the kernel mounting all "internal" filesystems (I kernel mount devfs at boot time) Your point about 'undocumented' is somthing that I had forgotten. It might be time to reinstate the explicit mount of /proc (maybe before running devfsd??) And, yes my 'distro' was doing an explict mount of /proc not 'mount -a -t procfs'. Hence the error message. At the end of the day, I'm not about to go all wobbly about using devfs - I think it is a huge improvement over paging through screens of unused /dev nodes, plus netboot roots and.. (insert all of Richard's reasons here). Cheers David ----Original Message Follows---- From: Pavel Roskin To: Russell Coker CC: David Gilbert , Subject: Re: Newbie question: running devfsd forces implicit mount of /proc? Date: Mon, 15 Jul 2002 14:22:53 -0400 (EDT) Hello! > > Once running, I noticed errors from the init scripts about trying to mount > > /proc. I've disabled the explict mount of /proc to work around the problem. > > But what's going on? It seems that once devfsd is running there is an > > implicit mounting of /proc? Is this normal behaviour? I don't know the exact reasons, but that's what I see as well (I looked a few months ago). Personally, I have no problems with kernel mounting all the supported "internal" filesystems (procfs, devfs, devptf, usbdevfs) at startup. But the interdependency between devfs and procfs being mounted is indeed weird. Since this feature seems to be undocumented and can go away, I prefer not to rely on it and use the following command to mount procfs if it needs to be mounted: mount -a -t procfs This command doesn't generate any errors if /proc is already mounted. > You don't mention which distribution you're using, it's probably a > distribution issue. It may be a distribution issue, because some distributions try mounting filesystems explicitly at startup, whike others more or less rely on "-a" option to mount. > My start script for Debian mounts /proc because that's the only way to > determine whether it's already running. I don't understand. What is running? To check if /proc is mounted, one can check existance of /proc/mounts - if it's missing, /proc is not mounted. But "mount -a -t procfs" is much more graceful in my opinion. > Why is this a problem? I understand that an error message is a problem - the system should not report errors if everything is Ok. -- Regards, Pavel Roskin _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com From owner-devfs@oss.sgi.com Mon Jul 15 11:59:30 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g6FIxURw008127 for ; Mon, 15 Jul 2002 11:59:30 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g6FIxUSf008126 for devfs-outgoing; Mon, 15 Jul 2002 11:59:30 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g6FIxORw008123 for ; Mon, 15 Jul 2002 11:59:25 -0700 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g6FJ4B232697; Mon, 15 Jul 2002 13:04:11 -0600 Date: Mon, 15 Jul 2002 13:04:11 -0600 Message-Id: <200207151904.g6FJ4B232697@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: "David Gilbert" Cc: russell@coker.com.au, devfs@oss.sgi.com Subject: Re: Newbie question: running devfsd forces implicit mount of /proc? In-Reply-To: References: Sender: owner-devfs@oss.sgi.com Precedence: bulk David Gilbert writes: > Whoops! I wasn't suggesting it was a problem - I'm just trying to > understand better what's going on. I have a theory but I dont know how > the mechanics work: > > When devfsd runs, it still creates some symlinks. This happens even > though I dont have any REGISTER .* MK[NEW|OLD]COMPAT entries in my > devfsd.conf. The key symlink in question is /dev/fd which is a symlink > to /proc/self/fd. Now, I assume to make the symlink the target must > exist (is this right?), therefore /proc needs to be mounted. So, > 'magically' (Hmmm), /proc is mounted. Nope. You can make a symlink even without the destination existing/being mounted. > Unfortunately, this is where I run out of it.. I can't find any > references to mount(2) in the devfsd code. Indeed, there isn't. > So how is magic happening?? (I'm also an aetheist...) > > Just to be sure I wasn't imagining things, I booted my kernel with the > 'init=/bin/bash' option to bypass _all_ the init stuff. A quick check of > /proc proved that it was not mounted and a check of /dev showed no > /dev/fd. I then ran devfsd /dev and sure enough /dev/fd -> /proc/self/fd > appeared and /proc was mounted and ready. Do you have any kind of module autoloading enabled? Whether in the kernel config or in /etc/devfsd.conf ? Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Tue Jul 16 10:18:11 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g6GHIBRw007521 for ; Tue, 16 Jul 2002 10:18:11 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g6GHIBEn007520 for devfs-outgoing; Tue, 16 Jul 2002 10:18:11 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f Received: from hotmail.com (f143.law15.hotmail.com [64.4.23.143]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g6GHI2Rw007513 for ; Tue, 16 Jul 2002 10:18:03 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 16 Jul 2002 10:22:54 -0700 Received: from 195.92.168.164 by lw15fd.law15.hotmail.msn.com with HTTP; Tue, 16 Jul 2002 17:22:53 GMT X-Originating-IP: [195.92.168.164] From: "David Gilbert" To: rgooch@ras.ucalgary.ca Cc: devfs@oss.sgi.com Subject: Re: Newbie question: running devfsd forces implicit mount of /proc? Date: Tue, 16 Jul 2002 18:22:53 +0100 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 16 Jul 2002 17:22:54.0070 (UTC) FILETIME=[6B68D960:01C22CED] Sender: owner-devfs@oss.sgi.com Precedence: bulk Richard, Yes I have module autoloading enabled. devfsd.conf has 'LOOKUP .* MODLOAD' and my kernel config has the kernel module loader (CONFIG_KMOD=Y). The modules.devfs is bog standard as per the devfsd v1.2.25 tarball and my local modules.conf only has a few alias entries - one for the cdrom, one for ppp and two for ppp compression modules. Anyway so much for the symlink theory - I should have remembered how many times I've created dangling symlinks... ;-) Cheers David ----Original Message Follows---- From: Richard Gooch To: "David Gilbert" CC: russell@coker.com.au, devfs@oss.sgi.com Subject: Re: Newbie question: running devfsd forces implicit mount of /proc? Date: Mon, 15 Jul 2002 13:04:11 -0600 David Gilbert writes: > Whoops! I wasn't suggesting it was a problem - I'm just trying to > understand better what's going on. I have a theory but I dont know how > the mechanics work: > > When devfsd runs, it still creates some symlinks. This happens even > though I dont have any REGISTER .* MK[NEW|OLD]COMPAT entries in my > devfsd.conf. The key symlink in question is /dev/fd which is a symlink > to /proc/self/fd. Now, I assume to make the symlink the target must > exist (is this right?), therefore /proc needs to be mounted. So, > 'magically' (Hmmm), /proc is mounted. Nope. You can make a symlink even without the destination existing/being mounted. > Unfortunately, this is where I run out of it.. I can't find any > references to mount(2) in the devfsd code. Indeed, there isn't. > So how is magic happening?? (I'm also an aetheist...) > > Just to be sure I wasn't imagining things, I booted my kernel with the > 'init=/bin/bash' option to bypass _all_ the init stuff. A quick check of > /proc proved that it was not mounted and a check of /dev showed no > /dev/fd. I then ran devfsd /dev and sure enough /dev/fd -> /proc/self/fd > appeared and /proc was mounted and ready. Do you have any kind of module autoloading enabled? Whether in the kernel config or in /etc/devfsd.conf ? Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com From owner-devfs@oss.sgi.com Tue Jul 16 18:37:03 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g6H1b3Rw008412 for ; Tue, 16 Jul 2002 18:37:03 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g6H1b3OH008408 for devfs-outgoing; Tue, 16 Jul 2002 18:37:03 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g6H1axRw008388 for ; Tue, 16 Jul 2002 18:36:59 -0700 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g6H1fmR26805; Tue, 16 Jul 2002 19:41:48 -0600 Date: Tue, 16 Jul 2002 19:41:48 -0600 Message-Id: <200207170141.g6H1fmR26805@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: "David Gilbert" Cc: devfs@oss.sgi.com Subject: Re: Newbie question: running devfsd forces implicit mount of /proc? In-Reply-To: References: Sender: owner-devfs@oss.sgi.com Precedence: bulk David Gilbert writes: > Richard, > > Yes I have module autoloading enabled. devfsd.conf has 'LOOKUP .* > MODLOAD' and my kernel config has the kernel module loader > (CONFIG_KMOD=Y). The modules.devfs is bog standard as per the devfsd > v1.2.25 tarball and my local modules.conf only has a few alias > entries - one for the cdrom, one for ppp and two for ppp compression > modules. On second thought, there should be nothing that causes procfs to be automatically mounted. That's unrelated to module autoloading. So somewhere something is mounting procfs behind your back. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Thu Jul 18 17:22:12 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g6J0MCRw011296 for ; Thu, 18 Jul 2002 17:22:12 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g6J0MCIP011295 for devfs-outgoing; Thu, 18 Jul 2002 17:22:12 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g6J0M7Rw011292 for ; Thu, 18 Jul 2002 17:22:08 -0700 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g6J0MZr28197; Thu, 18 Jul 2002 18:22:35 -0600 Date: Thu, 18 Jul 2002 18:22:35 -0600 Message-Id: <200207190022.g6J0MZr28197@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: Keith Owens Cc: "'linux-kernel@vger.kernel.org'" , "'devfs@oss.sgi.com'" Subject: Re: Inexplicable disk activity trying to load modules on devfs In-Reply-To: <19231.1025128989@ocs3.intra.ocs.com.au> References: <200206260338.g5Q3cmc19214@mobilix.ras.ucalgary.ca> <19231.1025128989@ocs3.intra.ocs.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk Keith Owens writes: > On Tue, 25 Jun 2002 23:38:48 -0400, > Richard Gooch wrote: > >Daniel Jacobowitz writes: > >> For the curious, the reason is that modprobe writes even failed > >> attempts to a log in /var/log/ksymoops, and calls fdatasync() on > >> that file afterwards. There is no way to disable this without > >> removing that directory, as a design decision. I don't personally > >> see the point in logging attempts which fail because there is no > >> driver... > > > >Sounds like the behaviour of modprobe needs to be fixed. > > People wanted to know what was invoking modprobe and with what > parameters, especially for failed attempts. The call to fdatasync() > is to "ensure" that the log data hits the disk _before_ the module > is loaded, otherwise debugging data is lost if the module init > routine oopses. Then there needs to be a way of enabling/disabling this. Maybe a run-time config option? Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Sun Jul 21 17:48:39 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g6M0mdRw030028 for ; Sun, 21 Jul 2002 17:48:39 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g6M0mdqD030027 for devfs-outgoing; Sun, 21 Jul 2002 17:48:39 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g6M0mWRw030024 for ; Sun, 21 Jul 2002 17:48:32 -0700 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g6M0ms602584; Sun, 21 Jul 2002 18:48:54 -0600 Date: Sun, 21 Jul 2002 18:48:54 -0600 Message-Id: <200207220048.g6M0ms602584@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: Russell Coker Cc: devfs@oss.sgi.com Subject: Re: bug report on devfs In-Reply-To: <20020620124800.2C720411@lyta.coker.com.au> References: <20020620124800.2C720411@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk Russell Coker writes: > This one was first discovered on my SE Linux play box, but has been > reproduced on normal machines too. > Log into a devfs-enabled box remotely with ssh, or with gnome-terminal, > or possibly others (haven't checked) > > Do not issue any comands in that shell > > Open another shell, and look at "w" output. Idle time is absurd. > > use stat on the pts from the first shell, notice the atime is 1970. OK, that's because the atime is initialised to zero (the Epoch, aka. 1970). This is the case for all device nodes in devfs, and is a convenient way of seeing if something has been changed from the default. The old "tar kludge" method of saving permissions depends on this (well, it looks at the ctime, not the atime). > People say this doesn't happen with devpts. I guess devpts initialises the atime to the current time when the device node is created. So devpts pretends that the user was active in that login when the login was created. That's not strictly true, since the user was never active in that terminal. Devfs is more honest, and shows (effectively) that the user was never active in that login. Which is true! Either way, does it really matter? I could change this, but it would require more code, and in some ways, what is there now is more "correct". Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Wed Jul 24 22:38:08 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g6P5c8Rw023627 for ; Wed, 24 Jul 2002 22:38:08 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g6P5c84I023626 for devfs-outgoing; Wed, 24 Jul 2002 22:38:08 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g6P5c1Rw023623 for ; Wed, 24 Jul 2002 22:38:01 -0700 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g6P5chV29917; Wed, 24 Jul 2002 23:38:43 -0600 Date: Wed, 24 Jul 2002 23:38:43 -0600 Message-Id: <200207250538.g6P5chV29917@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: linux-kernel@vger.kernel.org, devfs-announce-list@vindaloo.ras.ucalgary.ca Subject: [PATCH] devfs v199.15 available Sender: owner-devfs@oss.sgi.com Precedence: bulk Content-Length: 752 Lines: 25 Hi, all. Version 199.15 of my devfs patch is now available from: http://www.atnf.csiro.au/~rgooch/linux/kernel-patches.html The devfs FAQ is also available here. Patch directly available from: ftp://ftp.??.kernel.org/pub/linux/kernel/people/rgooch/v2.4/devfs-patch-current.gz AND: ftp://ftp.atnf.csiro.au/pub/people/rgooch/linux/kernel-patches/v2.4/devfs-patch-current.gz This is against 2.4.19-rc3. Highlights of this release: - Switched to ISO C structure field initialisers - Switch to set_current_state() and move before add_wait_queue() - Updated README from master HTML file - Fixed devfs entry leak in when *readdir fails Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Wed Jul 24 22:38:48 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g6P5cmRw023662 for ; Wed, 24 Jul 2002 22:38:48 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g6P5cmU9023661 for devfs-outgoing; Wed, 24 Jul 2002 22:38:48 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g6P5ciRw023657 for ; Wed, 24 Jul 2002 22:38:44 -0700 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g6P5dkU29950; Wed, 24 Jul 2002 23:39:46 -0600 Date: Wed, 24 Jul 2002 23:39:46 -0600 Message-Id: <200207250539.g6P5dkU29950@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: linux-kernel@vger.kernel.org, devfs-announce-list@vindaloo.ras.ucalgary.ca Subject: [PATCH] devfs v214 available Sender: owner-devfs@oss.sgi.com Precedence: bulk Content-Length: 808 Lines: 27 Hi, all. Version 214 of my devfs patch is now available from: http://www.atnf.csiro.au/~rgooch/linux/kernel-patches.html The devfs FAQ is also available here. Patch directly available from: ftp://ftp.??.kernel.org/pub/linux/kernel/people/rgooch/v2.5/devfs-patch-current.gz AND: ftp://ftp.atnf.csiro.au/pub/people/rgooch/linux/kernel-patches/v2.5/devfs-patch-current.gz NOTE: kernel 2.5.1 and later require devfsd-v1.3.19 or later. This is against 2.5.27. Highlights of this release: - Switched to ISO C structure field initialisers - Switch to set_current_state() and move before add_wait_queue() - Updated README from master HTML file - Fixed devfs entry leak in when *readdir fails Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Fri Jul 26 01:30:40 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g6Q8UeRw011011 for ; Fri, 26 Jul 2002 01:30:40 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g6Q8UeG7011010 for devfs-outgoing; Fri, 26 Jul 2002 01:30:40 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f Received: from prodvw07.cmsg.nl (prodvw07.cmsg.nl [194.151.108.131]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g6Q8UQRw011005 for ; Fri, 26 Jul 2002 01:30:27 -0700 X-Internal-ID: 3D1A91BB0016F0F4 Received: from mailrelay01.cmsg.nl (194.151.108.138) by prodvw07.cmsg.nl (NPlex 2.0.119) for devfs@oss.sgi.com; Fri, 26 Jul 2002 10:31:29 +0200 Received: from 145.45.5.7 by mailrelay01.cmsg.nl with ESMTP (ESMTP Service Ready (MMS v4.7);); Fri, 26 Jul 2002 10:31:29 +0200 X-Server-Uuid: c4c492e4-0681-11d5-8dad-00508bb858bc X-Internal-ID: 3D3FE1340000BF38 Received: from prodvw10.cmsg.nl (145.45.5.8) by prodvw06.cmsg.nl (NPlex 5.5.015) id 3D3FE1340000BF38 for devfs@oss.sgi.com; Fri, 26 Jul 2002 10:31:28 +0200 Received: by prodvw10 with Internet Mail Service (5.5.2650.21) id ; Fri, 26 Jul 2002 10:26:20 +0200 Message-ID: <1FEE21DC1054D5119FCC0002A5517B2476F741@rws-mdi-dt2-01.mdi.rws.minvenw.nl> From: "Vaessen, E.M.J. (Ed)" To: "'devfs@oss.sgi.com'" Subject: devfs not enabled by kernel? Date: Fri, 26 Jul 2002 10:31:25 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) X-WSS-ID: 115FD7E71539623-23-03 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-devfs@oss.sgi.com Precedence: bulk Content-Length: 2975 Lines: 85 I experience problems in trying to make devfs work. I have a very ordinary PC on which SuSE Linux 8.0 is installed, kernel 2.4.18-4GB. Following very closely the instructions written down in a few articles by Daniel Robbins (Advanced filesystems implementors guide, http://www-106.ibm.com/developerworks/library/l-fs4.html) I changed the kernel to make it support devfs. So in file .config the options CONFIG_EXPERIMENTAL=y, CONFIG_DEVFS_FS=y, CONFIG_DEVFS_MOUNT=n, CONFIG_DEVFS_DEBUG=n, and CONFIG_DEVPTS_FS=n were used. The next line in /etc/fstab I commented out: #devpts /dev/pts devpts defaults 0 0 After booting, a few things happened that I don't understand. In file /var/log/kdm.log the following lines were present that suggest things were not quite all right: /sbin/init: devfsd: command not found Usage: init.system 0123456SsQqAaBbCcUu fs type devfs not supported by kernel In directory /dev, the entry .devfs was not present. That program devfsd could not be found is surprising, because simply typing this command showed it was present (in /sbin to be exact). In /var/log/boot.msg I found the following lines that suggest that devfs was enabled somehow: devfs: v1.10 (20020120) Richard Gooch (rgooch@atnf.csiro.au) devfs: boot_options: 0x0 Before I try to go any further and start to edit boot scripts to mount devfs (in fact I tried that once but I was left with a system in which only the proc filesystem and a read-only / were mounted), I would like to know what is going on here. Are the messages above somehow familiar to anyone? I went through many internet pages to find out more about this but so far without result. Ed Vaessen Besides: a bit annoying is the fact that in /etc/mtab the line devpts /dev/pts devpts rw 0 0 is present. Looking through a few boot scripts I see that several of them indeed like to mount this filesystem. It is very strange that they seem to succeed in this, since both disabling devpts in the kernel AND commenting out the corresponding line in /etc/fstab should be enough to prevent this filesystem from showing up in /etc/mtab ?? =============================== E.M.J. Vaessen Senior Systeemspecialist Afdeling Remote Sensing en Fotogrammetrie (GAR) Meetkundige Dienst van Rijkswaterstaat Postbus 5023, 2600 GA Delft Kanaalweg 3b, 2628 EB Delft Telefoon: (015) 26 91 277 E-mail e.m.j.vaessen@mdi.rws.minvenw.nl =============================== Disclaimer ************************************************************************ Aan dit bericht kunnen geen rechten worden ontleend. Dit bericht is uitsluitend bestemd voor de geadresseerde. Als u dit bericht per abuis hebt ontvangen, wordt u verzocht het te vernietigen en de afzender te informeren. Wij adviseren u om bij twijfel over de juistheid of de volledigheid van de mail contact met afzender op te nemen. ************************************************************************ From owner-devfs@oss.sgi.com Fri Jul 26 10:03:29 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g6QH3TRw032562 for ; Fri, 26 Jul 2002 10:03:29 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g6QH3Tqo032561 for devfs-outgoing; Fri, 26 Jul 2002 10:03:29 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g6QH3IRw032558 for ; Fri, 26 Jul 2002 10:03:19 -0700 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g6QH4ON10945; Fri, 26 Jul 2002 11:04:24 -0600 Date: Fri, 26 Jul 2002 11:04:24 -0600 Message-Id: <200207261704.g6QH4ON10945@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: "Vaessen, E.M.J. (Ed)" Cc: "'devfs@oss.sgi.com'" Subject: Re: devfs not enabled by kernel? In-Reply-To: <1FEE21DC1054D5119FCC0002A5517B2476F741@rws-mdi-dt2-01.mdi.rws.minvenw.nl> References: <1FEE21DC1054D5119FCC0002A5517B2476F741@rws-mdi-dt2-01.mdi.rws.minvenw.nl> Sender: owner-devfs@oss.sgi.com Precedence: bulk Content-Length: 1924 Lines: 50 E. M. J. Vaessen writes: > I experience problems in trying to make devfs work. > I have a very ordinary PC on which SuSE Linux 8.0 is installed, kernel > 2.4.18-4GB. > Following very closely the instructions written down in a few articles by > Daniel Robbins (Advanced filesystems implementors guide, > http://www-106.ibm.com/developerworks/library/l-fs4.html) I changed the > kernel to make it support devfs. So in file .config the options > CONFIG_EXPERIMENTAL=y, CONFIG_DEVFS_FS=y, CONFIG_DEVFS_MOUNT=n, > CONFIG_DEVFS_DEBUG=n, and CONFIG_DEVPTS_FS=n were used. > > The next line in /etc/fstab I commented out: > > #devpts /dev/pts devpts defaults 0 0 > > > After booting, a few things happened that I don't understand. > > In file /var/log/kdm.log the following lines were present that suggest > things were not quite all right: > > /sbin/init: devfsd: command not found > Usage: init.system 0123456SsQqAaBbCcUu > fs type devfs not supported by kernel > > > In directory /dev, the entry .devfs was not present. > That program devfsd could not be found is surprising, because simply typing > this command showed it was present (in /sbin to be exact). > > In /var/log/boot.msg I found the following lines that suggest that devfs was > enabled somehow: > > devfs: v1.10 (20020120) Richard Gooch (rgooch@atnf.csiro.au) > devfs: boot_options: 0x0 > > Before I try to go any further and start to edit boot scripts to > mount devfs (in fact I tried that once but I was left with a system > in which only the proc filesystem and a read-only / were mounted), I > would like to know what is going on here. Are the messages above > somehow familiar to anyone? I went through many internet pages to > find out more about this but so far without result. Please read the devfs FAQ. It has a question&answer section. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Sun Jul 28 11:01:56 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g6SI1iRw011954 for ; Sun, 28 Jul 2002 11:01:45 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g6SI1TDp011949 for devfs-outgoing; Sun, 28 Jul 2002 11:01:29 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g6SI1ARw011937 for ; Sun, 28 Jul 2002 11:01:17 -0700 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g6SI1xr28889; Sun, 28 Jul 2002 12:01:59 -0600 Date: Sun, 28 Jul 2002 12:01:59 -0600 Message-Id: <200207281801.g6SI1xr28889@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: linux-kernel@vger.kernel.org, devfs-announce-list@vindaloo.ras.ucalgary.ca Subject: [PATCH] devfs v215 available Sender: owner-devfs@oss.sgi.com Precedence: bulk Content-Length: 785 Lines: 26 Hi, all. Version 215 of my devfs patch is now available from: http://www.atnf.csiro.au/~rgooch/linux/kernel-patches.html The devfs FAQ is also available here. Patch directly available from: ftp://ftp.??.kernel.org/pub/linux/kernel/people/rgooch/v2.5/devfs-patch-current.gz AND: ftp://ftp.atnf.csiro.au/pub/people/rgooch/linux/kernel-patches/v2.5/devfs-patch-current.gz NOTE: kernel 2.5.1 and later require devfsd-v1.3.19 or later. This is against 2.5.28. Highlights of this release: - Created - Switched many functions from to - Switched many functions from to Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Sun Jul 28 12:18:08 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g6SJI5Rw012454 for ; Sun, 28 Jul 2002 12:18:05 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g6SJI26B012453 for devfs-outgoing; Sun, 28 Jul 2002 12:18:02 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-devfs@oss.sgi.com using -f Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g6SJHnRw012450 for ; Sun, 28 Jul 2002 12:17:51 -0700 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g6SJIgr30557; Sun, 28 Jul 2002 13:18:42 -0600 Date: Sun, 28 Jul 2002 13:18:42 -0600 Message-Id: <200207281918.g6SJIgr30557@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: linux-kernel@vger.kernel.org, devfs-announce-list@vindaloo.ras.ucalgary.ca Subject: [PATCH] devfs v216 available Sender: owner-devfs@oss.sgi.com Precedence: bulk Content-Length: 712 Lines: 24 Hi, all. Version 216 of my devfs patch is now available from: http://www.atnf.csiro.au/~rgooch/linux/kernel-patches.html The devfs FAQ is also available here. Patch directly available from: ftp://ftp.??.kernel.org/pub/linux/kernel/people/rgooch/v2.5/devfs-patch-current.gz AND: ftp://ftp.atnf.csiro.au/pub/people/rgooch/linux/kernel-patches/v2.5/devfs-patch-current.gz NOTE: kernel 2.5.1 and later require devfsd-v1.3.19 or later. This is against 2.5.29. Highlights of this release: - Switched arch/ia64/sn/io/hcl.c from to - Removed deprecated Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca