From owner-devfs@oss.sgi.com Mon Mar 4 00:04:53 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2484rF05612 for devfs-outgoing; Mon, 4 Mar 2002 00:04:53 -0800 Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2484f905609 for ; Mon, 4 Mar 2002 00:04:43 -0800 Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by david.siemens.de (8.11.6/8.11.6) with ESMTP id g2474cd20274 for ; Mon, 4 Mar 2002 08:04:38 +0100 (MET) Received: from mowp002a.mowp.siemens.ru (mowp002a.mowp.siemens.ru [149.202.148.230]) by mail3.siemens.de (8.11.6/8.11.6) with ESMTP id g2474bk12775 for ; Mon, 4 Mar 2002 08:04:37 +0100 (MET) Received: by mowp002a.mowp.siemens.ru with Internet Mail Service (5.5.2653.19) id ; Mon, 4 Mar 2002 10:07:50 +0300 Received: from mw1g17c (mw1g17c.mow.siemens.ru [149.202.201.33]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id GDPF8CF4; Mon, 4 Mar 2002 10:08:33 +0300 From: Borsenkow Andrej To: "'Marc Lijour (Responsable Informatique)'" , "'devfs mailing list'" Cc: "'Pixel'" , "'Thierry Vignaud'" Subject: RE: [Cooker] Backpack (6) Date: Mon, 4 Mar 2002 10:08:01 +0300 Message-ID: <000901c1c34b$523fc900$21c9ca95@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 x-mimeole: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <20020304064243.99B3FFB454F@spitfire.velocet.net> Importance: Normal Sender: owner-devfs@oss.sgi.com Precedence: bulk > > > > > > $ls -l /dev/pcd* > > > brw-rw---- 1 marc cdwriter 46, 0 Feb 10 13:59 /dev/pcd0 > > > brw-rw---- 1 marc cdwriter 46, 1 Feb 10 13:59 /dev/pcd1 > > > brw-rw---- 1 marc cdwriter 46, 2 Feb 10 13:59 /dev/pcd2 > > > brw-rw---- 1 marc cdwriter 46, 3 Feb 10 13:59 /dev/pcd3 > > > > 1. what version of Mandrake are you running? > > I run currently 8.1 on this machine (laptop). > > > 2. Do you use devfs? Do you mount devfs? > > Yes I use devfs and I pass devfs=mount as a kernel parameter at boot time > (as > Mandrake set it up). > > > 3. who created these files? They must not exist with mounted devfs > > I don't remember having created these files. > I surely used this script taken from this howto : > http://www.torque.net/parport/paride.html > > #!/bin/bash > # Oh :( Well, Marc, the bad news are it is not going to work out-of-the-box. My question - would you help in testing it? You will have to update to current cooker (or at least beta4 - I have heard it is out) because testing on 8.1 is pretty useless, devfs support there is largely broken and I do not have time to test old versions anyway. You also have to apply patch to kernel and compile it. I'll tell you what to do so here is no problem. O.K. several points: - currently pcd has very poor devfs support. It registers only vanilla /dev/cdroms/ entry; it does not register anything else. It means with devfs no /dev/pcd* are created that violates devices.txt :-) - everything else in paride (pg = generic, pd = disk, pt = tape) seems to register corresponding /dev/{pg,pd,pt}/* entries and devfsd knows how to create compatibility links for them So to (fully) support paride with devfs we need - patch kernel pcd.c to create correct device entries; in which case "correct" means /dev/pcd/pcd* IMHO and /dev/cdroms/ links - patch devfsd to create compatibility links - think about modules.devfs configuration. We have to deal with both interface+device here much like for SCSI. Pixel is it possible to autodetect paride devices (assuming, they are connected on install) like for SCSI ppa/imm? My concern is, loading more than one parport driver may not be transparent. I.e. adding paride to standard modules.devfs may accidentally trigger loading of paride that may break other modules (lp or ppa/imm). Anybody knows about it? -andrej From owner-devfs@oss.sgi.com Mon Mar 4 06:51:10 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g24EpAh14466 for devfs-outgoing; Mon, 4 Mar 2002 06:51:10 -0800 Received: from watson.wustl.edu (watson.wustl.edu [128.252.233.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g24Ep1914462 for ; Mon, 4 Mar 2002 06:51:01 -0800 Received: from linus00 (mail@linus00 [10.0.1.203]) by watson.wustl.edu (8.9.3/8.9.3) with ESMTP id HAA10485 for ; Mon, 4 Mar 2002 07:50:55 -0600 (CST) Received: from ddooling by linus00 with local (Exim 3.34 #1 (Debian)) id 16hsrf-00084U-00 for ; Mon, 04 Mar 2002 07:50:55 -0600 Date: Mon, 4 Mar 2002 07:50:55 -0600 From: David Dooling To: devfs@oss.sgi.com Subject: mounting large number of NFS filesystems Message-ID: <20020304135055.GC26138@watson.wustl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i X-Organization: Washington University Genome Sequencing Center X-URL: http://www.genome.wustl.edu/gsc/ Sender: owner-devfs@oss.sgi.com Precedence: bulk Summary ------- I am currently unable to mount more than 256 NFS filesystems under Linux. I have tried several ways to get around this, but they have all failed. After reading up on devfs, I decided to try it. However, I am still unable to mount any more partitions. Is there any way devfs can be used to do this?. Details ------- I am currently running Debian GNU/Linux 3.0 (Woody), 2.4.17 kernel on a dual Athlon 1800+ (1.5 GHz) machine with 256 MB of RAM and a 20 GB IDE HDD. I have devfsd package installed: $ dpkg -l devfsd ii devfsd 1.3.24-1 Daemon for the device filesystem I have enabled the mounting of devfsd during boot (not using the boot option, but in the startup scripts): $ grep devfs /proc/mounts none /dev devfs rw 0 0 The current limitation on the number of NFS mounts has to do with the major/minor number scheme currently in use by the kernel. Since the minor numbers are only 8-bit and only a single major number is assigned to NFS (UNNAMED_MAJOR), you can only mount about 256 NFS partitions. Since one of the goals of devfs is to get away from the 8-bit major/minor limitation, I had hoped I could just use it and it would allow me to mount as many NFS partitions as I want. This didn't work, but I am not exactly sure where the problem lies. Here a couple guesses: - Since devfs still must export major and minor numbers to the userspace it does not by default totally ignore kernel major/minor limitations - perhaps I need a patched mount program that understands devfs Whether it is one of these (or both) or something else, I am at a loss as to how to go forward. Other Attempts to Fix --------------------- - Using automount doesn't work on my system because in our current environment many of the NFS mount points are at /. Therefore they each require a separate automount process. Each automount process also seems to take up a minor from UNNAMED_MAJOR (and when its mounted it will take up another, making the situation even worse). - Currently there is an experimental patch to the kernel (and mount and nfsd) which allows the mounting of more NFS partitions by increasing the number of major numbers assigned to UNNAMED_MAJOR from 1 to 4 (256 mounts -> 1024 mounts). While this may work, it seems to me that devfs would be a more elegant and long term solution. Any help would be greatly appreciated. We are trying to move from Sun to Linux and this is a major (pun intended?) sticking point since the Sun machine happily mount our 300 NFS filesystems. dd -- David Dooling From owner-devfs@oss.sgi.com Mon Mar 4 21:40:48 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g255em210861 for devfs-outgoing; Mon, 4 Mar 2002 21:40:48 -0800 Received: from spitfire.velocet.net (spitfire.velocet.net [216.138.223.227]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g255ee910849 for ; Mon, 4 Mar 2002 21:40:40 -0800 Received: from there (H139.C195.tor.velocet.net [216.138.195.139]) by spitfire.velocet.net (Postfix) with SMTP id 5DB6AFB4538; Tue, 5 Mar 2002 04:40:34 +0000 (GMT) Content-Type: text/plain; charset="iso-8859-1" From: Marc Lijour To: Borsenkow Andrej Subject: Re: [Cooker] Backpack (6) Date: Mon, 4 Mar 2002 23:43:56 -0500 X-Mailer: KMail [version 1.3.2] References: <000901c1c34b$523fc900$21c9ca95@mow.siemens.ru> In-Reply-To: <000901c1c34b$523fc900$21c9ca95@mow.siemens.ru> Cc: pixel@mandrakesoft.com, "'Thierry Vignaud'" , "'devfs mailing list'" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020305044034.5DB6AFB4538@spitfire.velocet.net> Sender: owner-devfs@oss.sgi.com Precedence: bulk > Oh :( > > Well, Marc, the bad news are it is not going to work out-of-the-box. My > question - would you help in testing it? You will have to update to > current cooker (or at least beta4 - I have heard it is out) because > testing on 8.1 is pretty useless, devfs support there is largely broken > and I do not have time to test old versions anyway. You also have to > apply patch to kernel and compile it. I'll tell you what to do so here > is no problem. > > O.K. several points: > > - currently pcd has very poor devfs support. It registers only vanilla > /dev/cdroms/ entry; it does not register anything else. It means with > devfs no /dev/pcd* are created that violates devices.txt :-) > > - everything else in paride (pg = generic, pd = disk, pt = tape) seems > to register corresponding /dev/{pg,pd,pt}/* entries and devfsd knows how > to create compatibility links for them > > So to (fully) support paride with devfs we need > > - patch kernel pcd.c to create correct device entries; in which case > "correct" means /dev/pcd/pcd* IMHO and /dev/cdroms/ links > > - patch devfsd to create compatibility links > > - think about modules.devfs configuration. We have to deal with both > interface+device here much like for SCSI. > > Pixel is it possible to autodetect paride devices (assuming, they are > connected on install) like for SCSI ppa/imm? > > My concern is, loading more than one parport driver may not be > transparent. I.e. adding paride to standard modules.devfs may > accidentally trigger loading of paride that may break other modules (lp > or ppa/imm). Anybody knows about it? > > -andrej Hi Andrej, I'm OK to test it. I currently run 8.1 on my laptop but I could also use other hosts to do the tests. I work as a sysadmin in a french school and I have plenty of PC to play with! I have one host running beta2 and another running beta3 (it's not smart but after I got it work with the SiS620 based pc I wanted to try my scsi HP laserjet 4c with scannerdrake as well as a cdwriter). The backpack is a portable cdwriter then I could try that easily in a couple of different pcs. But you may have to direct me with all that because I'm not familiar with devfs. But I'm ready to work! 1. to upgrade to cooker is it enough to run the Mandrake software manager and install the cooker's rpm? Other simpler way? 2. send me the kernel patchs and the command line instructions I'm ready. Regards, marc From owner-devfs@oss.sgi.com Tue Mar 5 16:23:41 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g260Nf227096 for devfs-outgoing; Tue, 5 Mar 2002 16:23:41 -0800 Received: from tsv.sws.net.au (tsv.sws.net.au [203.36.46.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g260NZ927093 for ; Tue, 5 Mar 2002 16:23:35 -0800 Received: from lyta.coker.com.au (localhost [127.0.0.1]) by tsv.sws.net.au (Postfix) with ESMTP id 7F19E92445; Wed, 6 Mar 2002 10:23:24 +1100 (EST) Received: from there (lyta [127.0.0.1]) by lyta.coker.com.au (Postfix) with SMTP id 15D571BBC; Wed, 6 Mar 2002 00:23:02 +0100 (CET) Content-Type: text/plain; charset="us-ascii" From: Russell Coker Reply-To: Russell Coker To: SE Linux Subject: NSA SE enabled devfsd Date: Wed, 6 Mar 2002 00:23:02 +0100 X-Mailer: KMail [version 1.3.2] Cc: devfs@oss.sgi.com, Debian Devel MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020305232303.15D571BBC@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk I have hacked support for SE Linux into devfsd. For example the following line in a devfsd config will set the SID of /dev/null: REGISTER ^null SELINUX system_u:object_r:null_device_t If the devfsd sees that you are not running an SE kernel, or if you compile the devfsd without SE Linux support then the SELINUX "what" actions will be silently ignored for compatability. The file selinux-config on my site has all the sample /dev policy converted to the format my hacked devfsd uses. The file devfsd-se.diff is the diff between the non-SE and the SE versions of devfsd, it was created against the Debian patched devfsd package, but should apply to a clean devfsd tree. There is also full source to devfsd, Debian package source, and a Debian package. The URL is http://www.coker.com.au/selinux/devfsd/ To the NSA people: please do not put any of this code on your site or take any formal notice of it yet. Richard should be given a chance to review it before we go any further (he may require small but problematic changes such as a different "what" keyword). At the moment this is just a proof of concept. -- If you send email to me or to a mailing list that I use which has >4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. From owner-devfs@oss.sgi.com Tue Mar 5 22:34:42 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g266Ygi06550 for devfs-outgoing; Tue, 5 Mar 2002 22:34:42 -0800 Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g266Yd906546 for ; Tue, 5 Mar 2002 22:34:39 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g265YaT02500; Tue, 5 Mar 2002 22:34:36 -0700 Date: Tue, 5 Mar 2002 22:34:36 -0700 Message-Id: <200203060534.g265YaT02500@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: David Dooling Cc: devfs@oss.sgi.com Subject: Re: mounting large number of NFS filesystems In-Reply-To: <20020304135055.GC26138@watson.wustl.edu> References: <20020304135055.GC26138@watson.wustl.edu> Sender: owner-devfs@oss.sgi.com Precedence: bulk David Dooling writes: > Summary > ------- > I am currently unable to mount more than 256 NFS filesystems under > Linux. I have tried several ways to get around this, but they have > all failed. After reading up on devfs, I decided to try it. However, > I am still unable to mount any more partitions. Is there any way > devfs can be used to do this?. Yes, but you need to modify the NFS client code in the kernel to support multiple majors. The function can be used to safely allocate extra majors as required. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Wed Mar 6 05:17:03 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g26DH3V17362 for devfs-outgoing; Wed, 6 Mar 2002 05:17:03 -0800 Received: from tsv.sws.net.au (tsv.sws.net.au [203.36.46.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g26DGs917356 for ; Wed, 6 Mar 2002 05:16:54 -0800 Received: from lyta.coker.com.au (localhost [127.0.0.1]) by tsv.sws.net.au (Postfix) with ESMTP id ABD7B92445; Wed, 6 Mar 2002 23:16:51 +1100 (EST) Received: from there (lyta [127.0.0.1]) by lyta.coker.com.au (Postfix) with SMTP id 699FC2158; Wed, 6 Mar 2002 13:16:39 +0100 (CET) Content-Type: text/plain; charset="iso-8859-1" From: Russell Coker Reply-To: Russell Coker To: SE Linux Subject: Re: NSA SE enabled devfsd Date: Wed, 6 Mar 2002 13:16:38 +0100 X-Mailer: KMail [version 1.3.2] Cc: devfs@oss.sgi.com MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020306121639.699FC2158@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk On Wed, 6 Mar 2002 00:23, Russell Coker wrote: > I have hacked support for SE Linux into devfsd. I have found one problem with my current code. devfsd wants to re-apply it's permissions to device nodes whenever it's restarted and whenever you do "killall -1 devfsd" to tell it to reload it's config. During the course of a login session the SID of the pty device will change. It starts as devpts_t, goes to sshd_devpts_t (for a ssh session - an equivalent type for a non-ssh session), then goes to user_t (or an appropriate type for the user). So if devfsd is restarted when someone is logged in then the result is likely to be a logout for them (which is tough if you've logged in to change the devfsd config). Currently I've got my devfsd config matching on ^pts$ and using domain transition rules for the rest. For the /dev/vc/* devices (devfs equivalent to /dev/tty[0-9]*) the only solution I get think of right now is to have the devfs_contexts file specify them. Also this is not an issue that is restricted to SE Linux. Currently if I run "killall -1 devfsd" it will be equivalent to "mesg n" for all users! -- If you send email to me or to a mailing list that I use which has >4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. From owner-devfs@oss.sgi.com Wed Mar 6 09:32:49 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g26HWnO25291 for devfs-outgoing; Wed, 6 Mar 2002 09:32:49 -0800 Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g26HWi925288 for ; Wed, 6 Mar 2002 09:32:44 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g26GWCB12634; Wed, 6 Mar 2002 09:32:12 -0700 Date: Wed, 6 Mar 2002 09:32:12 -0700 Message-Id: <200203061632.g26GWCB12634@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: Russell Coker Cc: SE Linux , devfs@oss.sgi.com, Debian Devel Subject: Re: NSA SE enabled devfsd In-Reply-To: <20020305232303.15D571BBC@lyta.coker.com.au> References: <20020305232303.15D571BBC@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk Russell Coker writes: > I have hacked support for SE Linux into devfsd. > > For example the following line in a devfsd config will set the SID of > /dev/null: > REGISTER ^null SELINUX system_u:object_r:null_device_t > > If the devfsd sees that you are not running an SE kernel, or if you compile > the devfsd without SE Linux support then the SELINUX "what" actions will be > silently ignored for compatability. > > The file selinux-config on my site has all the sample /dev policy converted > to the format my hacked devfsd uses. > > The file devfsd-se.diff is the diff between the non-SE and the SE versions of > devfsd, it was created against the Debian patched devfsd package, but should > apply to a clean devfsd tree. > > There is also full source to devfsd, Debian package source, and a Debian > package. > > The URL is http://www.coker.com.au/selinux/devfsd/ > > To the NSA people: please do not put any of this code on your site > or take any formal notice of it yet. Richard should be given a > chance to review it before we go any further (he may require small > but problematic changes such as a different "what" keyword). Even though there's not an awful lot of code to support this, I'm still unhappy about the #ifdef's. As I said back in January: I'd much rather see this done using an extension and GNUmakefile magic to automatically compile the extension as appropriate. Why not do it that way? BTW: why "FLASK"? Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Wed Mar 6 09:39:39 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g26Hdda25433 for devfs-outgoing; Wed, 6 Mar 2002 09:39:39 -0800 Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g26HdZ925429 for ; Wed, 6 Mar 2002 09:39:35 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g26GdN312918; Wed, 6 Mar 2002 09:39:23 -0700 Date: Wed, 6 Mar 2002 09:39:23 -0700 Message-Id: <200203061639.g26GdN312918@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: Russell Coker Cc: SE Linux , devfs@oss.sgi.com Subject: Re: NSA SE enabled devfsd In-Reply-To: <20020306121639.699FC2158@lyta.coker.com.au> References: <20020306121639.699FC2158@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk Russell Coker writes: > On Wed, 6 Mar 2002 00:23, Russell Coker wrote: > > I have hacked support for SE Linux into devfsd. > > I have found one problem with my current code. devfsd wants to > re-apply it's permissions to device nodes whenever it's restarted > and whenever you do "killall -1 devfsd" to tell it to reload it's > config. I'm open to (clean) suggestions on what to do about this. Perhaps a separate signal to reload the config file but don't generate the synthetic events? But before I make such a change, tell me why you're reloading the config file, but don't want to change permissions? Normally, you just send SIGHUP when /var is mounted (if that's where your permissions have been saved). > Also this is not an issue that is restricted to SE Linux. Currently > if I run "killall -1 devfsd" it will be equivalent to "mesg n" for > all users! But in general devfsd should be configured to *not* touch permissions for PTY's, so this shouldn't be a problem. What are you doing? Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Wed Mar 6 12:10:23 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g26KANx28929 for devfs-outgoing; Wed, 6 Mar 2002 12:10:23 -0800 Received: from tsv.sws.net.au (tsv.sws.net.au [203.36.46.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g26KAH928925 for ; Wed, 6 Mar 2002 12:10:17 -0800 Received: from lyta.coker.com.au (localhost [127.0.0.1]) by tsv.sws.net.au (Postfix) with ESMTP id 70B9C92445; Thu, 7 Mar 2002 06:10:15 +1100 (EST) Received: from there (lyta [127.0.0.1]) by lyta.coker.com.au (Postfix) with SMTP id 948291F082; Wed, 6 Mar 2002 20:10:08 +0100 (CET) Content-Type: text/plain; charset="iso-8859-1" From: Russell Coker Reply-To: Russell Coker To: Richard Gooch Subject: Re: NSA SE enabled devfsd Date: Wed, 6 Mar 2002 19:06:41 +0100 X-Mailer: KMail [version 1.3.2] Cc: SE Linux , devfs@oss.sgi.com References: <20020306121639.699FC2158@lyta.coker.com.au> <200203061639.g26GdN312918@vindaloo.ras.ucalgary.ca> In-Reply-To: <200203061639.g26GdN312918@vindaloo.ras.ucalgary.ca> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020306191008.948291F082@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk On Wed, 6 Mar 2002 17:39, Richard Gooch wrote: > > > I have hacked support for SE Linux into devfsd. > > > > I have found one problem with my current code. devfsd wants to > > re-apply it's permissions to device nodes whenever it's restarted > > and whenever you do "killall -1 devfsd" to tell it to reload it's > > config. > > I'm open to (clean) suggestions on what to do about this. Perhaps a > separate signal to reload the config file but don't generate the > synthetic events? Sounds reasonable. > But before I make such a change, tell me why you're reloading the > config file, but don't want to change permissions? Normally, you just > send SIGHUP when /var is mounted (if that's where your permissions > have been saved). If you decide to change your policy or add support for some type of device node that was not previously supported then you have to reload the config. Changing the policy does not necessarily require that existing permissions need to be changed. > > Also this is not an issue that is restricted to SE Linux. Currently > > if I run "killall -1 devfsd" it will be equivalent to "mesg n" for > > all users! > > But in general devfsd should be configured to *not* touch permissions > for PTY's, so this shouldn't be a problem. What are you doing? The following is in my devfsd.conf to change the group of the pts devices to group tty: REGISTER ^pts/.* PERMISSIONS -1.tty 0600 Is there any better way to do this? -- If you send email to me or to a mailing list that I use which has >4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. From owner-devfs@oss.sgi.com Wed Mar 6 23:13:01 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g277D1615506 for devfs-outgoing; Wed, 6 Mar 2002 23:13:01 -0800 Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g277Cp915492 for ; Wed, 6 Mar 2002 23:12:51 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g276CgI22751; Wed, 6 Mar 2002 23:12:42 -0700 Date: Wed, 6 Mar 2002 23:12:42 -0700 Message-Id: <200203070612.g276CgI22751@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: Russell Coker Cc: devfs@oss.sgi.com Subject: Re: NSA SE enabled devfsd In-Reply-To: <20020306191008.948291F082@lyta.coker.com.au> References: <20020306121639.699FC2158@lyta.coker.com.au> <200203061639.g26GdN312918@vindaloo.ras.ucalgary.ca> <20020306191008.948291F082@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk Russell Coker writes: > On Wed, 6 Mar 2002 17:39, Richard Gooch wrote: > > > > I have hacked support for SE Linux into devfsd. > > > > > > I have found one problem with my current code. devfsd wants to > > > re-apply it's permissions to device nodes whenever it's restarted > > > and whenever you do "killall -1 devfsd" to tell it to reload it's > > > config. > > > > I'm open to (clean) suggestions on what to do about this. Perhaps a > > separate signal to reload the config file but don't generate the > > synthetic events? > > Sounds reasonable. OK. How about SIGUSR1? If you have a better signal, let me know. > > But before I make such a change, tell me why you're reloading the > > config file, but don't want to change permissions? Normally, you just > > send SIGHUP when /var is mounted (if that's where your permissions > > have been saved). > > If you decide to change your policy or add support for some type of > device node that was not previously supported then you have to > reload the config. > > Changing the policy does not necessarily require that existing permissions > need to be changed. Fair enough. > > > Also this is not an issue that is restricted to SE Linux. Currently > > > if I run "killall -1 devfsd" it will be equivalent to "mesg n" for > > > all users! > > > > But in general devfsd should be configured to *not* touch permissions > > for PTY's, so this shouldn't be a problem. What are you doing? > > The following is in my devfsd.conf to change the group of the pts > devices to group tty: > REGISTER ^pts/.* PERMISSIONS -1.tty 0600 > > Is there any better way to do this? That's fine. In fact, this is sufficient: REGISTER ^pts/ PERMISSIONS -1.tty 0600 and is actually the same, since "pts/" matches ^pts/.* and may be more efficient than having the trailing .* in the regexp. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Thu Mar 7 05:43:53 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g27DhrI27695 for devfs-outgoing; Thu, 7 Mar 2002 05:43:53 -0800 Received: from tsv.sws.net.au (tsv.sws.net.au [203.36.46.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g27Dhk927684 for ; Thu, 7 Mar 2002 05:43:46 -0800 Received: from lyta.coker.com.au (localhost [127.0.0.1]) by tsv.sws.net.au (Postfix) with ESMTP id 0DFDB92454; Thu, 7 Mar 2002 23:43:43 +1100 (EST) Received: from there (lyta [127.0.0.1]) by lyta.coker.com.au (Postfix) with SMTP id 0EA651F2E2; Thu, 7 Mar 2002 13:43:35 +0100 (CET) Content-Type: text/plain; charset="iso-8859-1" From: Russell Coker Reply-To: Russell Coker To: Richard Gooch Subject: Re: NSA SE enabled devfsd Date: Thu, 7 Mar 2002 13:33:35 +0100 X-Mailer: KMail [version 1.3.2] Cc: devfs@oss.sgi.com References: <20020306121639.699FC2158@lyta.coker.com.au> <20020306191008.948291F082@lyta.coker.com.au> <200203070612.g276CgI22751@vindaloo.ras.ucalgary.ca> In-Reply-To: <200203070612.g276CgI22751@vindaloo.ras.ucalgary.ca> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020307124335.0EA651F2E2@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk On Thu, 7 Mar 2002 07:12, Richard Gooch wrote: > > > > > I have hacked support for SE Linux into devfsd. > > > > > > > > I have found one problem with my current code. devfsd wants to > > > > re-apply it's permissions to device nodes whenever it's restarted > > > > and whenever you do "killall -1 devfsd" to tell it to reload it's > > > > config. > > > > > > I'm open to (clean) suggestions on what to do about this. Perhaps a > > > separate signal to reload the config file but don't generate the > > > synthetic events? > > > > Sounds reasonable. > > OK. How about SIGUSR1? If you have a better signal, let me know. Sounds fine, SIGUSR1 is free for whatever you want... > > > > Also this is not an issue that is restricted to SE Linux. Currently > > > > if I run "killall -1 devfsd" it will be equivalent to "mesg n" for > > > > all users! > > > > > > But in general devfsd should be configured to *not* touch permissions > > > for PTY's, so this shouldn't be a problem. What are you doing? > > > > The following is in my devfsd.conf to change the group of the pts > > devices to group tty: > > REGISTER ^pts/.* PERMISSIONS -1.tty 0600 > > > > Is there any better way to do this? > > That's fine. In fact, this is sufficient: > REGISTER ^pts/ PERMISSIONS -1.tty 0600 > > and is actually the same, since "pts/" matches ^pts/.* and may be more > efficient than having the trailing .* in the regexp. True. But I still have the issue of a restart changing the mode. Maybe I should write a .so for managing pts/*? -- If you send email to me or to a mailing list that I use which has >4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. From owner-devfs@oss.sgi.com Thu Mar 7 09:29:47 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g27HTlE04426 for devfs-outgoing; Thu, 7 Mar 2002 09:29:47 -0800 Received: from vador.mandrakesoft.com (office.mandrakesoft.com [195.68.114.34]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g27HTe904420 for ; Thu, 7 Mar 2002 09:29:40 -0800 Received: from vador.mandrakesoft.com (localhost.localdomain [127.0.0.1]) by vador.mandrakesoft.com (Postfix) with ESMTP id 67577776E; Thu, 7 Mar 2002 17:30:36 +0100 (CET) To: Marc Lijour Cc: Borsenkow Andrej , pixel@mandrakesoft.com, "'devfs mailing list'" Subject: Re: [Cooker] Backpack (6) References: <000901c1c34b$523fc900$21c9ca95@mow.siemens.ru> <20020305044034.5DB6AFB4538@spitfire.velocet.net> X-URL: Date: Thu, 07 Mar 2002 17:30:36 +0100 In-Reply-To: <20020305044034.5DB6AFB4538@spitfire.velocet.net> (Marc Lijour's message of "Mon, 4 Mar 2002 23:43:56 -0500") Message-ID: Lines: 34 User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.2.50 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-devfs@oss.sgi.com Precedence: bulk be careful about anti-spamers filters: X-SpamBouncer: 1.4 (10/07/01) X-SBRule: Free Email site X-SBClass: Blocked i only saw your message because one a week i look at spam-bouncer blocked and spam queues :-( Marc Lijour writes: > 1. to upgrade to cooker is it enough to run the Mandrake software > manager and install the cooker's rpm? Other simpler way? either: - network installation from remote site (dangerous if the server synced with main mirrors while you install your box; you'll see lost packages) - download (ftp client, fmirror, rsync or whatever you prefer) current cooker, redo a sync after to be sure there's been no changes while you download it. * burn cds that you can make with cooker/misc/MakeCD * dump a boot image on a floppy from cooker/images and do a network installation using the box where you downloaded cooker as a ftp/http or nfs server * dump a boot image on a floppy from cooker/images and do a disc installation (rebooting the box where you download cooker and say using it hard disk as source) see http://www.linux-mandrake.com/fr/cookerdevel.php3 for a mirror list From owner-devfs@oss.sgi.com Thu Mar 7 10:58:40 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g27Iweq13036 for devfs-outgoing; Thu, 7 Mar 2002 10:58:40 -0800 Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g27IwX913030 for ; Thu, 7 Mar 2002 10:58:33 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g27HwH431128; Thu, 7 Mar 2002 10:58:17 -0700 Date: Thu, 7 Mar 2002 10:58:17 -0700 Message-Id: <200203071758.g27HwH431128@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: Russell Coker Cc: devfs@oss.sgi.com Subject: Re: NSA SE enabled devfsd In-Reply-To: <20020307124335.0EA651F2E2@lyta.coker.com.au> References: <20020306121639.699FC2158@lyta.coker.com.au> <20020306191008.948291F082@lyta.coker.com.au> <200203070612.g276CgI22751@vindaloo.ras.ucalgary.ca> <20020307124335.0EA651F2E2@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk Russell Coker writes: > On Thu, 7 Mar 2002 07:12, Richard Gooch wrote: > > > > > > I have hacked support for SE Linux into devfsd. > > > > > > > > > > I have found one problem with my current code. devfsd wants to > > > > > re-apply it's permissions to device nodes whenever it's restarted > > > > > and whenever you do "killall -1 devfsd" to tell it to reload it's > > > > > config. > > > > > > > > I'm open to (clean) suggestions on what to do about this. Perhaps a > > > > separate signal to reload the config file but don't generate the > > > > synthetic events? > > > > > > Sounds reasonable. > > > > OK. How about SIGUSR1? If you have a better signal, let me know. > > Sounds fine, SIGUSR1 is free for whatever you want... I was thinking more of whether to re-use some other signal, so as to conserve signals. But I guess it doesn't matter. I've coded it up to use SIGUSR1. > > > > > Also this is not an issue that is restricted to SE Linux. Currently > > > > > if I run "killall -1 devfsd" it will be equivalent to "mesg n" for > > > > > all users! > > > > > > > > But in general devfsd should be configured to *not* touch permissions > > > > for PTY's, so this shouldn't be a problem. What are you doing? > > > > > > The following is in my devfsd.conf to change the group of the pts > > > devices to group tty: > > > REGISTER ^pts/.* PERMISSIONS -1.tty 0600 > > > > > > Is there any better way to do this? > > > > That's fine. In fact, this is sufficient: > > REGISTER ^pts/ PERMISSIONS -1.tty 0600 > > > > and is actually the same, since "pts/" matches ^pts/.* and may be more > > efficient than having the trailing .* in the regexp. > > True. But I still have the issue of a restart changing the mode. Fixed in my tree. Use SIGUSR1. > Maybe I should write a .so for managing pts/*? Is there a need, now that SIGUSR1 is available? What would this .so do? Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Thu Mar 7 15:10:11 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g27NABI22130 for devfs-outgoing; Thu, 7 Mar 2002 15:10:11 -0800 Received: from tsv.sws.net.au (tsv.sws.net.au [203.36.46.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g27NA4922126 for ; Thu, 7 Mar 2002 15:10:04 -0800 Received: from lyta.coker.com.au (localhost [127.0.0.1]) by tsv.sws.net.au (Postfix) with ESMTP id 6199E92454; Fri, 8 Mar 2002 09:10:01 +1100 (EST) Received: from there (lyta [127.0.0.1]) by lyta.coker.com.au (Postfix) with SMTP id 1F80622B30; Thu, 7 Mar 2002 23:09:39 +0100 (CET) From: Russell Coker Reply-To: Russell Coker To: devfs@oss.sgi.com Subject: devfsd module for SE Linux Date: Thu, 7 Mar 2002 23:07:38 +0100 X-Mailer: KMail [version 1.3.2] Cc: SE Linux MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="------------Boundary-00=_QSIMC8981PGHU4V9YPTM" Message-Id: <20020307220939.1F80622B30@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk --------------Boundary-00=_QSIMC8981PGHU4V9YPTM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit I've attached the source to a devfsd module for SE Linux security settings with a sample config file (which mostly matches the settings in file_contexts for /dev). Let me know what you think. -- If you send email to me or to a mailing list that I use which has >4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. --------------Boundary-00=_QSIMC8981PGHU4V9YPTM Content-Type: application/x-gzip; name="devfsd-flask.tgz" Content-Transfer-Encoding: base64 Content-Description: devfsd-flask.tgz Content-Disposition: attachment; filename="devfsd-flask.tgz" H4sIADDhhzwCA+1YbXOjNhD2V/Mrtq5ztXOxgRjbU+fSdprmbjxzTTq59FPTYzAIWxdAjCTSuE3+ e1eAneDDl3wg7suwMwmwEs+zenYlJPf1xoubYVjGeDjEq2GOh6a6GsboMLtm1jDGlmWOR4ZlKf94 NBo1YNjYgSVCOhygwT+5X+yH3Xy/8b+zvu6RG194PZdFfkDki+TfxHRb1rb8W+PBYJ1/w8R+5uHQ HDTAqPP/4nZx+m764fL0Aj5GSRA0m82Tt7+enVxOz89ATwTXAzpbVYgfOOK6LxgIIu30wRbUgzY2 R05IQCyFJKGdTNjsE3GlzScK0sZm6hJbag9UfxLOKqZSkGVUWNaCBaRashy0jK9zHZLwTv3FjMtu pbSIyviyjDX5njuRx8Jqh5lhlvFJuaw4f9iCoI9JdI8Kt10xjU9viWcj8nXJsPTY4fI3o/ft76/b O6RNGXXXq5iTY7XcOLPyMvUDFsdLfYeMIWZT59KteCYGzC3T9CONqHRlUC1bDlogCti8+qmAoAWS mNNIEi4qTlgOuyFcnEi9E7JEkLsQZb0jNySqeiVT6FurJBZOctvcDeE8DisvkwyzmEAZ3lZcJgqy wCFYEnkVV0iKWaabM4/nuFpWy4agZVwep1VPMU63Vp8Th/aMMlHx0HLUjaoQ7eoXD0RFFk175v7/ Z+ea+DQgL3j++/L+3zDxsJft/4fjQwvvTXMwGNX7/13Y++mPcAwb5aZpG45JsYerNeeuC73zQ+j5 v0xPoCcWDice9Bi0f4D2G+gFgrgJJ5rmBsSJJlqTh9gX2h0k7GqN2v5t5/88s//A/McpP87n/6E1 GA/U+d8yrXr+78K+ppEbJB6BN/gtwW1nf/GdVvDpchkT8bkb9ZBFbxJRIb2NntKj7POX8aDlhBtu EtAoudWFKPdnX79E0mBLu7CzJUc1a/o+XC4I+CwI2B80msOCOB7hQAX6OAjJE1fmi5odMUn9pZ07 9/VH6Bl22s/208i0lIXiWZV6tgR1JKBOkH6Wj6FnHmka7qmL3+uOi6sj7Ksv9gFk9+i11XNX+0sD KEJi25FyZuEonWGW+MqlfneQOUL+sOLHJ0luJcbQKt0UYPyyhcEBUL9DRR4cidRxzet0u9igIkmb FWUuZicL+hUGgP8xsrTnqi9AVjSd9+fv7NOLiwNonTjRN3nQe2ICe2HrANKBHuVvcCITHoGRPd+v OAs6KiGLPCqqlUj5UG3JUnFLGrobquQgcKBEDUjU2WjvwmswHzq9ehRMPt6HSErGPHM8lbQJXLX2 xFWrfxXhoDcpjtbvFxVYabBWQinw1fHjwtoq+fTs7TnynzEs1T0BTsCxypewcPB+XVSwKo0eREwV TzQnz0zKNslX1bvWc13OSsjnFUqpaGucJwJzFyqMPISnuQjnOOnToau14MP0p3QVyAo0JX6C9F5N nAf3fb2Bqa222mqrrbbaaqutttpqq+2/ZX8DPL6S/wAoAAA= --------------Boundary-00=_QSIMC8981PGHU4V9YPTM-- From owner-devfs@oss.sgi.com Thu Mar 7 16:38:15 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g280cFa31634 for devfs-outgoing; Thu, 7 Mar 2002 16:38:15 -0800 Received: from tsv.sws.net.au (tsv.sws.net.au [203.36.46.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g280cC931631 for ; Thu, 7 Mar 2002 16:38:12 -0800 Received: from lyta.coker.com.au (localhost [127.0.0.1]) by tsv.sws.net.au (Postfix) with ESMTP id 2619E92454; Fri, 8 Mar 2002 10:38:10 +1100 (EST) Received: from there (lyta [127.0.0.1]) by lyta.coker.com.au (Postfix) with SMTP id A26D91F321; Fri, 8 Mar 2002 00:37:53 +0100 (CET) Content-Type: text/plain; charset="iso-8859-1" From: Russell Coker Reply-To: Russell Coker To: Richard Gooch Subject: Re: NSA SE enabled devfsd Date: Fri, 8 Mar 2002 00:36:44 +0100 X-Mailer: KMail [version 1.3.2] Cc: devfs@oss.sgi.com References: <20020306121639.699FC2158@lyta.coker.com.au> <20020307124335.0EA651F2E2@lyta.coker.com.au> <200203071758.g27HwH431128@vindaloo.ras.ucalgary.ca> In-Reply-To: <200203071758.g27HwH431128@vindaloo.ras.ucalgary.ca> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020307233753.A26D91F321@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk On Thu, 7 Mar 2002 18:58, Richard Gooch wrote: > > Maybe I should write a .so for managing pts/*? > > Is there a need, now that SIGUSR1 is available? What would this .so > do? Allow changing the group without changing the permission mode. Probably no need now though. -- If you send email to me or to a mailing list that I use which has >4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. From owner-devfs@oss.sgi.com Thu Mar 7 23:29:56 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g287Tuc10822 for devfs-outgoing; Thu, 7 Mar 2002 23:29:56 -0800 Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g287Tq910812 for ; Thu, 7 Mar 2002 23:29:52 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g286S5311927; Thu, 7 Mar 2002 23:28:05 -0700 Date: Thu, 7 Mar 2002 23:28:05 -0700 Message-Id: <200203080628.g286S5311927@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: Russell Coker Cc: devfs@oss.sgi.com Subject: Re: devfsd module for SE Linux In-Reply-To: <20020307220939.1F80622B30@lyta.coker.com.au> References: <20020307220939.1F80622B30@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk Russell Coker writes: > I've attached the source to a devfsd module for SE Linux security > settings with a sample config file (which mostly matches the > settings in file_contexts for /dev). What a huuuuuuuge config file! > Let me know what you think. Looks reasonable. Needs a copyleft notice, and can you put together a GNUmakefile rule so that it can be automatically built if the headers are available, and not built otherwise? Also, the devfsd shared objects are supposed to live in /lib/devfsd, not in /usr/lib. Finally, can you change the name from flask to something more meaningful? Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Fri Mar 8 07:27:00 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g28FR0e31618 for devfs-outgoing; Fri, 8 Mar 2002 07:27:00 -0800 Received: from tsv.sws.net.au (tsv.sws.net.au [203.36.46.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g28FQs931606 for ; Fri, 8 Mar 2002 07:26:55 -0800 Received: from lyta.coker.com.au (localhost [127.0.0.1]) by tsv.sws.net.au (Postfix) with ESMTP id D8F3692454; Sat, 9 Mar 2002 01:26:51 +1100 (EST) Received: from there (lyta [127.0.0.1]) by lyta.coker.com.au (Postfix) with SMTP id 552FA39B72; Fri, 8 Mar 2002 15:26:42 +0100 (CET) Content-Type: text/plain; charset="iso-8859-1" From: Russell Coker Reply-To: Russell Coker To: Richard Gooch Subject: Re: devfsd module for SE Linux Date: Fri, 8 Mar 2002 14:10:13 +0100 X-Mailer: KMail [version 1.3.2] Cc: devfs@oss.sgi.com References: <20020307220939.1F80622B30@lyta.coker.com.au> <200203080628.g286S5311927@vindaloo.ras.ucalgary.ca> In-Reply-To: <200203080628.g286S5311927@vindaloo.ras.ucalgary.ca> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020308142642.552FA39B72@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk On Fri, 8 Mar 2002 07:28, Richard Gooch wrote: > Russell Coker writes: > > I've attached the source to a devfsd module for SE Linux security > > settings with a sample config file (which mostly matches the > > settings in file_contexts for /dev). > > What a huuuuuuuge config file! > > > Let me know what you think. > > Looks reasonable. Needs a copyleft notice, and can you put together a > GNUmakefile rule so that it can be automatically built if the headers > are available, and not built otherwise? Actually I'm planning to ask the NSA to include it in their selinux-small archive, having that implies that you have the headers. > Also, the devfsd shared objects are supposed to live in /lib/devfsd, > not in /usr/lib. Good point, it needs to be in the root file system. As /lib/devfsd is the official place, could you make devfsd check "/lib/devfsd/%s", name first if the name doesn't include a '/'character? That'll cut down the size of the config files. > Finally, can you change the name from flask to something more > meaningful? OK. For the next version s/flask/se/g -- If you send email to me or to a mailing list that I use which has >4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. From owner-devfs@oss.sgi.com Fri Mar 8 08:14:11 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g28GEBb00759 for devfs-outgoing; Fri, 8 Mar 2002 08:14:11 -0800 Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g28GE6900754 for ; Fri, 8 Mar 2002 08:14:06 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g28FDt016894; Fri, 8 Mar 2002 08:13:55 -0700 Date: Fri, 8 Mar 2002 08:13:55 -0700 Message-Id: <200203081513.g28FDt016894@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: Russell Coker Cc: devfs@oss.sgi.com Subject: Re: devfsd module for SE Linux In-Reply-To: <20020308142642.552FA39B72@lyta.coker.com.au> References: <20020307220939.1F80622B30@lyta.coker.com.au> <200203080628.g286S5311927@vindaloo.ras.ucalgary.ca> <20020308142642.552FA39B72@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk Russell Coker writes: > On Fri, 8 Mar 2002 07:28, Richard Gooch wrote: > > Russell Coker writes: > > > I've attached the source to a devfsd module for SE Linux security > > > settings with a sample config file (which mostly matches the > > > settings in file_contexts for /dev). > > > > What a huuuuuuuge config file! > > > > > Let me know what you think. > > > > Looks reasonable. Needs a copyleft notice, and can you put together a > > GNUmakefile rule so that it can be automatically built if the headers > > are available, and not built otherwise? > > Actually I'm planning to ask the NSA to include it in their > selinux-small archive, having that implies that you have the > headers. OK, that's probably better. > > Also, the devfsd shared objects are supposed to live in /lib/devfsd, > > not in /usr/lib. > > Good point, it needs to be in the root file system. > > As /lib/devfsd is the official place, could you make devfsd check > "/lib/devfsd/%s", name first if the name doesn't include a '/'character? > That'll cut down the size of the config files. Done. > > Finally, can you change the name from flask to something more > > meaningful? > > OK. For the next version s/flask/se/g How about "nsa_se"? Or even "nsa_selinux"? Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Fri Mar 8 08:25:15 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g28GPFl01222 for devfs-outgoing; Fri, 8 Mar 2002 08:25:15 -0800 Received: from tsv.sws.net.au (tsv.sws.net.au [203.36.46.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g28GPC901215 for ; Fri, 8 Mar 2002 08:25:12 -0800 Received: from lyta.coker.com.au (localhost [127.0.0.1]) by tsv.sws.net.au (Postfix) with ESMTP id D9C3C92454; Sat, 9 Mar 2002 02:25:09 +1100 (EST) Received: from there (lyta [127.0.0.1]) by lyta.coker.com.au (Postfix) with SMTP id C3E3C3D490; Fri, 8 Mar 2002 16:25:01 +0100 (CET) Content-Type: text/plain; charset="iso-8859-1" From: Russell Coker Reply-To: Russell Coker To: Richard Gooch Subject: Re: devfsd module for SE Linux Date: Fri, 8 Mar 2002 16:25:01 +0100 X-Mailer: KMail [version 1.3.2] Cc: devfs@oss.sgi.com References: <20020307220939.1F80622B30@lyta.coker.com.au> <20020308142642.552FA39B72@lyta.coker.com.au> <200203081513.g28FDt016894@vindaloo.ras.ucalgary.ca> In-Reply-To: <200203081513.g28FDt016894@vindaloo.ras.ucalgary.ca> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020308152501.C3E3C3D490@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk On Fri, 8 Mar 2002 16:13, Richard Gooch wrote: > > > Finally, can you change the name from flask to something more > > > meaningful? > > > > OK. For the next version s/flask/se/g > > How about "nsa_se"? Or even "nsa_selinux"? The "linux" part is redundant. The "nsa" part is probably redundant, "se" tells it all I think. -- If you send email to me or to a mailing list that I use which has >4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. From owner-devfs@oss.sgi.com Fri Mar 8 09:38:56 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g28HcuP03427 for devfs-outgoing; Fri, 8 Mar 2002 09:38:56 -0800 Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g28Hcp903424 for ; Fri, 8 Mar 2002 09:38:51 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g28GcRD18372; Fri, 8 Mar 2002 09:38:27 -0700 Date: Fri, 8 Mar 2002 09:38:27 -0700 Message-Id: <200203081638.g28GcRD18372@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: Russell Coker Cc: devfs@oss.sgi.com Subject: Re: devfsd module for SE Linux In-Reply-To: <20020308152501.C3E3C3D490@lyta.coker.com.au> References: <20020307220939.1F80622B30@lyta.coker.com.au> <20020308142642.552FA39B72@lyta.coker.com.au> <200203081513.g28FDt016894@vindaloo.ras.ucalgary.ca> <20020308152501.C3E3C3D490@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk Russell Coker writes: > On Fri, 8 Mar 2002 16:13, Richard Gooch wrote: > > > > Finally, can you change the name from flask to something more > > > > meaningful? > > > > > > OK. For the next version s/flask/se/g > > > > How about "nsa_se"? Or even "nsa_selinux"? > > The "linux" part is redundant. The "nsa" part is probably > redundant, "se" tells it all I think. Unless someone else comes up with a "security enhanced" Linux... Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Sun Mar 10 19:55:35 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2B3tZ316715 for devfs-outgoing; Sun, 10 Mar 2002 19:55:35 -0800 Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2B3tN916701 for ; Sun, 10 Mar 2002 19:55:23 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g2B2t6C26959; Sun, 10 Mar 2002 19:55:06 -0700 Date: Sun, 10 Mar 2002 19:55:06 -0700 Message-Id: <200203110255.g2B2t6C26959@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: Denis Zaitsev Cc: devfs@oss.sgi.com Subject: Re: [PATCH] a little strings-aware code change In-Reply-To: <20020225204212.B5954@natasha.zzz.zzz> References: <200202180612.g1I6C4L25410@vindaloo.ras.ucalgary.ca> <20020219030003.D1639@zzz.zzz.zzz> <200202191840.g1JIeKt18971@vindaloo.ras.ucalgary.ca> <20020225204212.B5954@natasha.zzz.zzz> Sender: owner-devfs@oss.sgi.com Precedence: bulk Denis Zaitsev writes: > Ok, I'm sorry for such a delay... > > On Tue, Feb 19, 2002 at 11:40:20AM -0700, Richard Gooch wrote: > > Denis Zaitsev writes: > > > This little patch does nothing with the functionality of devfsd, but > > > with the C code. There are a number of constructions like: > > > > > > [PFXLEN = strlen(prefix);] > > > if (strncmp(str, prefix, PFXLEN) == 0) > > > do_something_with(str + PFXLEN); > > > > > > It is not the best way to do such a things. The idea is to implement > > > the special function, which will test the string for some prefix and > > > return the address of a place of the string after that prefix or NULL > > > in case of an absence of the success. The construction above becomes > > > better: > > > > > > if (ptr= strtry(str, prefix)) > > > do_something_with(ptr); > > > > > > And the new function itself is more lightweight than alone strncmp, > > > and just much more effective than in a couple. It > > > is good again. So, all the idea seems to be healthy. I call this > > > function "strtry", as it tries its arg for the given prefix. > > > > Apart from not really liking this approach, you've made the strtry() > > function inlined. Any saving you might make with removing code from > > the callers is probably more than lost due to all the extra inlined > > code. > > > > Did you compare the sizes of the stripped binary to see what the > > effect of your patch is? > > > > Yes, of course, I did. The new binary is 672 bytes smaller...) But > it's not the answer for your question, because I compile devfsd with > all the string functions inlined. Inlining is generally a bad idea. It bloats the object code and increases the icache footprint. Inlining should only ever be done in a critical path, where you're trying to save cycles. Nothing in devfsd is that critical. > And the difference includes all the throwned out strrchr's calls. > And I haven't done any "pure" measurements. But I think, they > aren't really needed. I prefer hard numbers to speculation, particularly when justifying a change. > strtry should be inlined, because it is very small - something like > 14 inline bytes on x86, plus, say 5 bytes for loading the prefix's > addr into the reg. > At the same time, the outlined call for strncmp takes: > call itself - 5 bytes, > stack cleanup - 3 bytes, > stack loading - something like 2 + 1 + 6 bytes > - i.e. it's generally just equal for the inlined strtry. So, inlined > strtry is better than outlined strncmp even without the cons of a > inline size... And strtry's cycle is more effective, than strncmp's > one, but I've already written about. And when strncmp is used in the > couple with strlen, than strtry is more than twice faster, as it scans > the prefix only once vs. twice. And strtry's stuff looks good in C > (as for me, of course). So, that are the reasons, why strtry is "a > good choice"... > > > > Richard, please, apply this patch, if you find it useful. It is > > > against devfsd-1.3.22. By the way, I've arranged the > > > strrchr (devname, '/') + 1 > > > stuff, so this thing to be done once instead of multiply times in the > > > original. > > > > But you've inserted calls to strrchr in cases where it's not really > > needed. > > Yes, I agree, I was thinking about this... Probably, just another > special function will be healthy here, as that fragment of code is > repeated often. If you don't reject the whole idea about strtry, I > will remove these changes from the patch. Well, like I said earlier, I'm not enthusiastic about strtry(). It looks like there is little if no benefit, and it adds another non-standard function that requires the reader to check the API. Everyone understands strncmp(). I don't plan on using strtry() unless I see some real benefit. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Tue Mar 12 23:12:53 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2D7CrR00686 for devfs-outgoing; Tue, 12 Mar 2002 23:12:53 -0800 Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2D7Cg900679 for ; Tue, 12 Mar 2002 23:12:42 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g2D6Cbl05869; Tue, 12 Mar 2002 23:12:37 -0700 Date: Tue, 12 Mar 2002 23:12:37 -0700 Message-Id: <200203130612.g2D6Cbl05869@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: Juan Quintela Cc: Borsenkow Andrej , "'Thierry Vignaud'" , kernel@mandrakesoft.com, "'devfs mailing list'" , "'Frederic Lepied'" Subject: Re: [kernel] char/raw.c devfs support In-Reply-To: References: <000601c1b56b$241be2e0$21c9ca95@mow.siemens.ru> <200202141750.g1EHo2G12220@vindaloo.ras.ucalgary.ca> Sender: owner-devfs@oss.sgi.com Precedence: bulk I'm still hoping to track down the problem that was reported a month ago. I'm waiting for devfsd straces to help me track down the problem. Juan Quintela writes: > >>>>> "richard" == Richard Gooch writes: > > > richard> Um, what do you mean you failed to explain it? > > 1) that I explain myself badly :( > > 2) that you didn't understand the problem from my explanation :( > > Here are the traces that I had at the moment: > > I still has that bug with 2.4.18-pre7, and it has this patch applied. > > stack traces again (in kernel land). > > p1: > schedule() > devfs_de_revalidate_wait() > cached_lookup() > lookup_hash() > sys_unlink() > system_call() > > p2: > > schedule() > wait_for_devfsd_finished() > devfs_lookup(() > lookup_hash() > unix_bind() > sys_bind() > sys_socketcall() > system_call() > > the thing that they are tring to create/remove is /dev/log. > > And devfsd is already running in that state: > > __schedule() > __down() > __down_failed() > __text_lock_namei() > > This has worked normally until now, it has beggining to fail yesterday. > > What the tasks are doing: > > the task does basically: > > unlink("/dev/log"); > bind("/dev/log") -> type AF_LOCAL, we have already did the socket() > listen() > if (fork) > exit(); > else { > stat(/dev/log); > > stat(/dev/log); (we need to make sure that nobody has changed the > link under our toes > exit(); > } > > As you can see, the user space does something that looks normal to do, > and the kernel handling that part looks strange. > > Other thing that is perhaps a bug in our setup is that we are storing > /dev/log in /lib/dev-state, and probably we shouldn't(this was Andrej > discovery), but that is a different story, i.e. I think that: > > create unix socket > reboot > devfsd recreate socket > unlink socket > create socket again > stat the name of the socket > > should not hang devfsd. > > I hope that this time I has been clearer, I the info is not enough, I > will try to get an userspace trace of devfsd while this is happening, > but I don't have a good idea on how to do it yet. Just edit the system boot scripts and send the output of strace somewhere. I really need this strace of devfsd. I need to know exactly what it's doing and how it got to that state. Perhaps you have a work-around for this hanging, but I'd really prefer to get the underlying problem understood and fixed. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Thu Mar 14 06:52:55 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2EEqtk05313 for devfs-outgoing; Thu, 14 Mar 2002 06:52:55 -0800 Received: from tsv.sws.net.au (tsv.sws.net.au [203.36.46.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2EEqq905310 for ; Thu, 14 Mar 2002 06:52:52 -0800 Received: from lyta.coker.com.au (localhost [127.0.0.1]) by tsv.sws.net.au (Postfix) with ESMTP id E23CC92443 for ; Fri, 15 Mar 2002 01:54:17 +1100 (EST) Received: from there (lyta [127.0.0.1]) by lyta.coker.com.au (Postfix) with SMTP id 933B127913 for ; Thu, 14 Mar 2002 15:54:10 +0100 (CET) Content-Type: text/plain; charset="us-ascii" From: Russell Coker Reply-To: Russell Coker To: devfs@oss.sgi.com Subject: patch for close on exec Date: Thu, 14 Mar 2002 15:54:10 +0100 X-Mailer: KMail [version 1.3.2] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020314145410.933B127913@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk The following patch for devfsd.c makes it close the .devfsd file on exec. At the moment the only problem that the open file handle causes is that it's against my security policy for the domain insmod_t to read devfs_t domain character devices. But there could be more serious issues that I haven't considered. @@ -557,6 +561,8 @@ fprintf (stderr, "Error opening file: \".devfsd\"\t%s\n", ERRSTRING); exit (1); } + if(fcntl(fd, F_SETFD, FD_CLOEXEC)) + fprintf(stderr, "Error setting close on exec for .devfsd\n"); if (ioctl (fd, DEVFSDIOC_GET_PROTO_REV, &proto_rev) != 0) { fprintf (stderr, "Error getting protocol revision\t%s\n", ERRSTRING); -- If you send email to me or to a mailing list that I use which has >4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. From owner-devfs@oss.sgi.com Thu Mar 14 08:14:03 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2EGE3V08697 for devfs-outgoing; Thu, 14 Mar 2002 08:14:03 -0800 Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2EGDt908689 for ; Thu, 14 Mar 2002 08:13:55 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g2EGF6S30855; Thu, 14 Mar 2002 09:15:06 -0700 Date: Thu, 14 Mar 2002 09:15:06 -0700 Message-Id: <200203141615.g2EGF6S30855@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: Russell Coker Cc: devfs@oss.sgi.com Subject: Re: patch for close on exec In-Reply-To: <20020314145410.933B127913@lyta.coker.com.au> References: <20020314145410.933B127913@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk Russell Coker writes: > The following patch for devfsd.c makes it close the .devfsd file on exec. > > At the moment the only problem that the open file handle causes is > that it's against my security policy for the domain insmod_t to read > devfs_t domain character devices. But there could be more serious > issues that I haven't considered. Well, I can't think of any problems, but since the .devfsd file isn't needed by anything else, it's probably a good idea to close it. Done. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Thu Mar 14 08:23:35 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2EGNZ409677 for devfs-outgoing; Thu, 14 Mar 2002 08:23:35 -0800 Received: from tsv.sws.net.au (tsv.sws.net.au [203.36.46.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2EGNV909674 for ; Thu, 14 Mar 2002 08:23:32 -0800 Received: from lyta.coker.com.au (localhost [127.0.0.1]) by tsv.sws.net.au (Postfix) with ESMTP id 8BF8492443; Fri, 15 Mar 2002 03:24:57 +1100 (EST) Received: from there (lyta [127.0.0.1]) by lyta.coker.com.au (Postfix) with SMTP id 4100C21E; Thu, 14 Mar 2002 17:24:11 +0100 (CET) Content-Type: text/plain; charset="iso-8859-1" From: Russell Coker Reply-To: Russell Coker To: Richard Gooch Subject: Re: patch for close on exec Date: Thu, 14 Mar 2002 17:24:10 +0100 X-Mailer: KMail [version 1.3.2] Cc: devfs@oss.sgi.com References: <20020314145410.933B127913@lyta.coker.com.au> <200203141615.g2EGF6S30855@vindaloo.ras.ucalgary.ca> In-Reply-To: <200203141615.g2EGF6S30855@vindaloo.ras.ucalgary.ca> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020314162411.4100C21E@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk On Thu, 14 Mar 2002 17:15, Richard Gooch wrote: > Russell Coker writes: > > The following patch for devfsd.c makes it close the .devfsd file on exec. > > > > At the moment the only problem that the open file handle causes is > > that it's against my security policy for the domain insmod_t to read > > devfs_t domain character devices. But there could be more serious > > issues that I haven't considered. > > Well, I can't think of any problems, but since the .devfsd file isn't > needed by anything else, it's probably a good idea to close it. Done. It should be pretty safe as devfsd only spawns non-hostile processes where the user can't control the parameters or the environment, (by default it's only modprobe). Also the kernel appeared to have some enforcement for only one open file handle anyway. -- If you send email to me or to a mailing list that I use which has >4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. From owner-devfs@oss.sgi.com Thu Mar 21 11:55:14 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2LJtES09609 for devfs-outgoing; Thu, 21 Mar 2002 11:55:14 -0800 Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2LJt7q09606 for ; Thu, 21 Mar 2002 11:55:08 -0800 Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.11.6/8.11.6) with ESMTP id g2LIt2R29940 for ; Thu, 21 Mar 2002 19:55:02 +0100 (MET) Received: from mowp002a.mowp.siemens.ru (mowp002a.mowp.siemens.ru [149.202.148.230]) by mail2.siemens.de (8.11.6/8.11.6) with ESMTP id g2LIt1g00871 for ; Thu, 21 Mar 2002 19:55:01 +0100 (MET) Received: by mowp002a.mowp.siemens.ru with Internet Mail Service (5.5.2653.19) id ; Thu, 21 Mar 2002 21:44:11 +0300 Received: from [149.202.201.201] (149.202.201.201 [149.202.201.201]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id HKT0V1YF; Thu, 21 Mar 2002 21:59:40 +0300 From: Borsenkow Andrej To: devfs mailing list , linux-kernel list Subject: PATCH: support for IDE devices in ide-scsi with devfs Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2-4mdk Date: 21 Mar 2002 21:54:51 +0300 Message-Id: <1016736897.3113.5.camel@localhost.localdomain> Mime-Version: 1.0 Sender: owner-devfs@oss.sgi.com Precedence: bulk Currently using ide-scsi with devfs does not allow you to use hdparm interface because no IDE nodes (block devices) are created. The patch adds this. Related patch for devfsd that creates old compatibility links is going to devfs list. I do not think spcial new compatibility links are needed. -andrej --- linux-2.4.18-4mdk/drivers/scsi/ide-scsi.c.orig Tue Mar 5 06:08:04 2002 +++ linux-2.4.18-4mdk/drivers/scsi/ide-scsi.c Thu Mar 21 21:21:31 2002 @@ -95,6 +95,7 @@ unsigned long flags; /* Status/Action flags */ unsigned long transform; /* SCSI cmd translation layer */ unsigned long log; /* log flags */ + devfs_handle_t de; /* pointer to IDE device */ } idescsi_scsi_t; /* @@ -502,6 +503,8 @@ */ static void idescsi_setup (ide_drive_t *drive, idescsi_scsi_t *scsi, int id) { + int minor = (drive->select.b.unit) << PARTN_BITS; + DRIVER(drive)->busy++; idescsi_drives[id] = drive; drive->driver_data = scsi; @@ -516,6 +519,10 @@ set_bit(IDESCSI_LOG_CMD, &scsi->log); #endif /* IDESCSI_DEBUG_LOG */ idescsi_add_settings(drive); + scsi->de = devfs_register(drive->de, "generic", DEVFS_FL_DEFAULT, + HWIF(drive)->major, minor, + S_IFBLK | S_IRUSR | S_IWUSR, + ide_fops, NULL); } static int idescsi_cleanup (ide_drive_t *drive) @@ -524,6 +531,8 @@ if (ide_unregister_subdriver (drive)) return 1; + if (scsi->de) + devfs_unregister(scsi->de); drive->driver_data = NULL; kfree (scsi); return 0; From owner-devfs@oss.sgi.com Thu Mar 21 11:18:11 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2LJIB410696 for devfs-outgoing; Thu, 21 Mar 2002 11:18:11 -0800 Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2LJI7q10692 for ; Thu, 21 Mar 2002 11:18:07 -0800 Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.11.6/8.11.6) with ESMTP id g2LJKTR08266 for ; Thu, 21 Mar 2002 20:20:29 +0100 (MET) Received: from mowp002a.mowp.siemens.ru (mowp002a.mowp.siemens.ru [149.202.148.230]) by mail2.siemens.de (8.11.6/8.11.6) with ESMTP id g2LJKSg06998 for ; Thu, 21 Mar 2002 20:20:28 +0100 (MET) Received: by mowp002a.mowp.siemens.ru with Internet Mail Service (5.5.2653.19) id ; Thu, 21 Mar 2002 22:09:38 +0300 Received: from [149.202.201.201] (149.202.201.201 [149.202.201.201]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id HKT0V1ZD; Thu, 21 Mar 2002 22:25:05 +0300 From: Borsenkow Andrej To: devfs mailing list Subject: Re: PATCH: support for IDE devices in ide-scsi with devfs In-Reply-To: <1016736897.3113.5.camel@localhost.localdomain> References: <1016736897.3113.5.camel@localhost.localdomain> Content-Type: text/plain; charset=KOI8-R X-Mailer: Evolution/1.0.2-4mdk Date: 21 Mar 2002 22:20:09 +0300 Message-Id: <1016738424.3236.13.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id g2LJI7q10693 Sender: owner-devfs@oss.sgi.com Precedence: bulk ÷ þÔ×, 21.03.2002, × 21:54, Borsenkow Andrej ÎÁÐÉÓÁÌ: > Currently using ide-scsi with devfs does not allow you to use hdparm > interface because no IDE nodes (block devices) are created. The patch > adds this. > > Related patch for devfsd that creates old compatibility links is going > to devfs list. I do not think spcial new compatibility links are needed. > Here it is. -andrej diff -u devfsd-mdk/compat_name.c devfsd/compat_name.c --- devfsd-mdk/compat_name.c Thu Mar 21 21:02:57 2002 +++ devfsd/compat_name.c Thu Mar 21 21:04:48 2002 @@ -234,6 +234,12 @@ get_old_ide_name (major, minor) ); compat_name = buffer; } + else if (strcmp (devname + namelen - 7, "generic") == 0) + { + sprintf ( buffer, "hd%c", + get_old_ide_name (major, minor) ); + compat_name = buffer; + } return (compat_name); } else if ( (strncmp (devname, "ida/", 4) == 0) && Common subdirectories: devfsd-mdk/examples and devfsd/examples From owner-devfs@oss.sgi.com Thu Mar 21 21:45:28 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2M5jSR07550 for devfs-outgoing; Thu, 21 Mar 2002 21:45:28 -0800 Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2M5jKq07546 for ; Thu, 21 Mar 2002 21:45:20 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g2M5cDW22953; Thu, 21 Mar 2002 22:38:13 -0700 Date: Thu, 21 Mar 2002 22:38:13 -0700 Message-Id: <200203220538.g2M5cDW22953@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: Borsenkow Andrej Cc: devfs mailing list Subject: Re: PATCH: support for IDE devices in ide-scsi with devfs In-Reply-To: <1016738424.3236.13.camel@localhost.localdomain> References: <1016736897.3113.5.camel@localhost.localdomain> <1016738424.3236.13.camel@localhost.localdomain> Sender: owner-devfs@oss.sgi.com Precedence: bulk Borsenkow Andrej writes: > ÷ þÔ×, 21.03.2002, × 21:54, Borsenkow Andrej ÎÁÐÉÓÁÌ: > > Currently using ide-scsi with devfs does not allow you to use hdparm > > interface because no IDE nodes (block devices) are created. The patch > > adds this. > > > > Related patch for devfsd that creates old compatibility links is going > > to devfs list. I do not think spcial new compatibility links are needed. I'd prefer to not add this patch to devfsd unless there is some indication from Marcelo and Linus that this patch will be applied (otherwise devfsd would grow with unused cruft). Have you had any response about the kernel patch? Please let me know if you get word back, or when the patch is available in either 2.4.x or 2.5.x. Then re-send the patch to devfsd to me, and I'll apply it. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Fri Mar 22 01:35:20 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2M9ZKJ12912 for devfs-outgoing; Fri, 22 Mar 2002 01:35:20 -0800 Received: from master.linux-ide.org (astound-64-85-224-253.ca.astound.net [64.85.224.253]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2M9ZAq12908 for ; Fri, 22 Mar 2002 01:35:10 -0800 Received: from localhost (andre@localhost) by master.linux-ide.org (8.9.3/8.9.3) with ESMTP id BAA10033; Fri, 22 Mar 2002 01:23:40 -0800 Date: Fri, 22 Mar 2002 01:23:40 -0800 (PST) From: Andre Hedrick To: Borsenkow Andrej cc: devfs mailing list , linux-kernel list Subject: Re: PATCH: support for IDE devices in ide-scsi with devfs In-Reply-To: <1016736897.3113.5.camel@localhost.localdomain> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-devfs@oss.sgi.com Precedence: bulk Thankyou sir I have been working towards that direction, but glad and happy you have assisted ! Cheers, Andre Hedrick LAD Storage Consulting Group On 21 Mar 2002, Borsenkow Andrej wrote: > Currently using ide-scsi with devfs does not allow you to use hdparm > interface because no IDE nodes (block devices) are created. The patch > adds this. > > Related patch for devfsd that creates old compatibility links is going > to devfs list. I do not think spcial new compatibility links are needed. > > -andrej > > --- linux-2.4.18-4mdk/drivers/scsi/ide-scsi.c.orig Tue Mar 5 06:08:04 2002 > +++ linux-2.4.18-4mdk/drivers/scsi/ide-scsi.c Thu Mar 21 21:21:31 2002 > @@ -95,6 +95,7 @@ > unsigned long flags; /* Status/Action flags */ > unsigned long transform; /* SCSI cmd translation layer */ > unsigned long log; /* log flags */ > + devfs_handle_t de; /* pointer to IDE device */ > } idescsi_scsi_t; > > /* > @@ -502,6 +503,8 @@ > */ > static void idescsi_setup (ide_drive_t *drive, idescsi_scsi_t *scsi, int id) > { > + int minor = (drive->select.b.unit) << PARTN_BITS; > + > DRIVER(drive)->busy++; > idescsi_drives[id] = drive; > drive->driver_data = scsi; > @@ -516,6 +519,10 @@ > set_bit(IDESCSI_LOG_CMD, &scsi->log); > #endif /* IDESCSI_DEBUG_LOG */ > idescsi_add_settings(drive); > + scsi->de = devfs_register(drive->de, "generic", DEVFS_FL_DEFAULT, > + HWIF(drive)->major, minor, > + S_IFBLK | S_IRUSR | S_IWUSR, > + ide_fops, NULL); > } > > static int idescsi_cleanup (ide_drive_t *drive) > @@ -524,6 +531,8 @@ > > if (ide_unregister_subdriver (drive)) > return 1; > + if (scsi->de) > + devfs_unregister(scsi->de); > drive->driver_data = NULL; > kfree (scsi); > return 0; > > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > From owner-devfs@oss.sgi.com Sat Mar 23 06:43:14 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2NEhE511171 for devfs-outgoing; Sat, 23 Mar 2002 06:43:14 -0800 Received: from thoth.sbs.de (thoth.sbs.de [192.35.17.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2NEh7q11168 for ; Sat, 23 Mar 2002 06:43:08 -0800 Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by thoth.sbs.de (8.11.6/8.11.6) with ESMTP id g2NEjTX11465 for ; Sat, 23 Mar 2002 15:45:29 +0100 (MET) Received: from mowp002a.mowp.siemens.ru (mowp002a.mowp.siemens.ru [149.202.148.230]) by mail2.siemens.de (8.11.6/8.11.6) with ESMTP id g2NEjSg17739 for ; Sat, 23 Mar 2002 15:45:28 +0100 (MET) Received: by mowp002a.mowp.siemens.ru with Internet Mail Service (5.5.2653.19) id ; Sat, 23 Mar 2002 17:34:40 +0300 Received: from [149.202.201.201] (149.202.201.201 [149.202.201.201]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id H3XG6236; Sat, 23 Mar 2002 17:50:08 +0300 From: Borsenkow Andrej To: devfs mailing list Cc: Thierry Vignaud , Vojtech Pavlik Subject: Why ACM driver disables devfs support? Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2-4mdk Date: 23 Mar 2002 17:45:16 +0300 Message-Id: <1016894722.3011.8.camel@localhost.localdomain> Mime-Version: 1.0 Sender: owner-devfs@oss.sgi.com Precedence: bulk This has been posted in Mandrake newsgroup: =============== Hello! I've just installed MD8.2 but can't find any ttyACM0 in /dev lib. The acm modules is up and running. How do I create the ttyACM0 device so yhat I can get my usb modem (isdn) working ??? Any reply will be welcome! =============== for all I can tell, ACM devices should be registered as /dev/ucb/acm/%d (drivers/usb/acm.c) but devfs support is explicitly disabled: static struct tty_driver acm_tty_driver = { magic: TTY_DRIVER_MAGIC, driver_name: "acm", name: "usb/acm/%d", major: ACM_TTY_MAJOR, minor_start: 0, num: ACM_TTY_MINORS, type: TTY_DRIVER_TYPE_SERIAL, subtype: SERIAL_TYPE_NORMAL, flags: TTY_DRIVER_REAL_RAW | TTY_DRIVER_NO_DEVFS, ^^^^^^^^^^^^^^^^^^^^ any reason for it? -andrej From owner-devfs@oss.sgi.com Sat Mar 23 06:55:11 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2NEtBL11285 for devfs-outgoing; Sat, 23 Mar 2002 06:55:11 -0800 Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2NEt7q11282 for ; Sat, 23 Mar 2002 06:55:07 -0800 Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.11.6/8.11.6) with ESMTP id g2NEvTd13706 for ; Sat, 23 Mar 2002 15:57:30 +0100 (MET) Received: from mowp002a.mowp.siemens.ru (mowp002a.mowp.siemens.ru [149.202.148.230]) by mail2.siemens.de (8.11.6/8.11.6) with ESMTP id g2NEvTg19093 for ; Sat, 23 Mar 2002 15:57:29 +0100 (MET) Received: by mowp002a.mowp.siemens.ru with Internet Mail Service (5.5.2653.19) id ; Sat, 23 Mar 2002 17:46:41 +0300 Received: from [149.202.201.201] (149.202.201.201 [149.202.201.201]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id H3XG62P1; Sat, 23 Mar 2002 18:02:07 +0300 From: Borsenkow Andrej To: Borsenkow Andrej Cc: devfs mailing list , Thierry Vignaud , Vojtech Pavlik Subject: Re: Why ACM driver disables devfs support? In-Reply-To: <1016894722.3011.8.camel@localhost.localdomain> References: <1016894722.3011.8.camel@localhost.localdomain> Content-Type: text/plain; charset=KOI8-R X-Mailer: Evolution/1.0.2-4mdk Date: 23 Mar 2002 17:57:15 +0300 Message-Id: <1016895441.3711.2.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id g2NEt8q11283 Sender: owner-devfs@oss.sgi.com Precedence: bulk ÷ óÂÔ, 23.03.2002, × 17:45, Borsenkow Andrej ÎÁÐÉÓÁÌ: > > This has been posted in Mandrake newsgroup: > > =============== > Hello! > I've just installed MD8.2 but can't find any ttyACM0 in /dev lib. The > acm > modules is up and running. How do I create the ttyACM0 device so yhat I > can > get my usb modem (isdn) working ??? > Any reply will be welcome! > =============== > > for all I can tell, ACM devices should be registered as /dev/ucb/acm/%d > (drivers/usb/acm.c) but devfs support is explicitly disabled: > > flags: TTY_DRIVER_REAL_RAW | > TTY_DRIVER_NO_DEVFS, > ^^^^^^^^^^^^^^^^^^^^ > Sorry, I was stupid today. Of course it does register device name, I do not know why I thought differently. So, the question is - people obviously expect /dev/ttyACM%d for it, should compatibility link go into devfsd? -andrej From owner-devfs@oss.sgi.com Sat Mar 23 07:02:23 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2NF2Nl11775 for devfs-outgoing; Sat, 23 Mar 2002 07:02:23 -0800 Received: from twilight.ucw.cz (root@twilight.ucw.cz [195.39.74.230]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2NF2Gq11772 for ; Sat, 23 Mar 2002 07:02:17 -0800 Received: (from vojtech@localhost) by twilight.ucw.cz (8.10.2/8.9.3) id g2NF1IE05145; Sat, 23 Mar 2002 16:01:18 +0100 Date: Sat, 23 Mar 2002 16:01:18 +0100 From: Vojtech Pavlik To: Borsenkow Andrej Cc: devfs mailing list , Thierry Vignaud , Vojtech Pavlik Subject: Re: Why ACM driver disables devfs support? Message-ID: <20020323160118.A5140@ucw.cz> References: <1016894722.3011.8.camel@localhost.localdomain> <1016895441.3711.2.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1016895441.3711.2.camel@localhost.localdomain>; from Andrej.Borsenkow@mow.siemens.ru on Sat, Mar 23, 2002 at 05:57:15PM +0300 X-MIME-Autoconverted: from 8bit to quoted-printable by twilight.ucw.cz id g2NF1IE05145 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id g2NF2Iq11773 Sender: owner-devfs@oss.sgi.com Precedence: bulk On Sat, Mar 23, 2002 at 05:57:15PM +0300, Borsenkow Andrej wrote: > ÷ óÂÔ, 23.03.2002, × 17:45, Borsenkow Andrej ÎÁÐÉÓÁÌ: > > > > This has been posted in Mandrake newsgroup: > > > > =============== > > Hello! > > I've just installed MD8.2 but can't find any ttyACM0 in /dev lib. The > > acm > > modules is up and running. How do I create the ttyACM0 device so yhat I > > can > > get my usb modem (isdn) working ??? > > Any reply will be welcome! > > =============== > > > > for all I can tell, ACM devices should be registered as /dev/ucb/acm/%d > > (drivers/usb/acm.c) but devfs support is explicitly disabled: > > > > flags: TTY_DRIVER_REAL_RAW | > > TTY_DRIVER_NO_DEVFS, > > ^^^^^^^^^^^^^^^^^^^^ > > > > Sorry, I was stupid today. Of course it does register device name, I do > not know why I thought differently. > > So, the question is - people obviously expect /dev/ttyACM%d for it, > should compatibility link go into devfsd? It may be worth adding it, yes, though I've never needed it. -- Vojtech Pavlik SuSE Labs From owner-devfs@oss.sgi.com Sun Mar 24 01:37:14 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2O9bEa29706 for devfs-outgoing; Sun, 24 Mar 2002 01:37:14 -0800 Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2O9b6q29701 for ; Sun, 24 Mar 2002 01:37:06 -0800 Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by david.siemens.de (8.11.6/8.11.6) with ESMTP id g2O9dTd06163; Sun, 24 Mar 2002 10:39:29 +0100 (MET) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail3.siemens.de (8.11.6/8.11.6) with ESMTP id g2O9dSk10533; Sun, 24 Mar 2002 10:39:28 +0100 (MET) Received: by mowd019a.mow.siemens.ru with Internet Mail Service (5.5.2653.19) id ; Sun, 24 Mar 2002 12:44:15 +0300 Received: from [149.202.201.201] (149.202.201.201 [149.202.201.201]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id H3XG6287; Sun, 24 Mar 2002 12:44:08 +0300 From: Borsenkow Andrej To: Todd Lyons Cc: future@mandrakesoft.com, Thierry Vignaud , devfs mailing list Subject: Symlinks and autoloading (was: Re: [Future] 8.2 errata) In-Reply-To: <20020324001649.GA2114@mandrakesoft.com> References: <20020323005920.GD974@mandrakesecure.net> <20020324001649.GA2114@mandrakesoft.com> Content-Type: text/plain; charset=KOI8-R X-Mailer: Evolution/1.0.2-4mdk Date: 24 Mar 2002 12:39:15 +0300 Message-Id: <1016962761.2954.6.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id g2O9b7q29702 Sender: owner-devfs@oss.sgi.com Precedence: bulk ÷ ÷ÓË, 24.03.2002, × 03:16, Todd Lyons ÎÁÐÉÓÁÌ: > Vincent Danen wrote on Fri, Mar 22, 2002 at 05:59:20PM -0700 : > > If anyone has 8.2 errata that needs to go up (I see Tom has posted > > some problem reports, but I haven't read them all), please send me the > > text to go on the page in the same format as was used for the 8.1 > > errata, specificly: > > > Error Scenario: No version of X works on i815 chipset (Compaq desktop > is what I was using). > Why: devfs interference > Solution: Reboot with devfs=nomount and then both X 4.2.0 and 3.3.6 > work. > Has nothing to do with chipset. ... > (EE) GARTInit: AGPIOC_INFO failed (Invalid argument) > (EE) I810(0): AGP GART support is not available. Make sure your kernel > has > agpgart support or that the agpgart kernel module is loaded. > (EE) Screen(s) found, but none have a usable configuration. > ... > > Note that it complains about the agpgart module, but the module _was_ > loaded automatically. > No it was not unless you prove different (there was no lsmod output). I happen to have i815e motherboard (ASUS CUSL2) and it works ... in "normal" case. The above happens if somebody manually creates link /dev/agpgart -> misc/agpgart _or_ updates from Mandrake 8.1. What happens is devfsd restores (dangling) symlink so no LOOKUP is ever generated by devfs and no module is ever loaded. Just create the above link manually, reboot and you get exactly the same problem. Somewhat trivial but working fix is to always provide aliases for both compatibility and canonical names. I.e. in our case (verified): --- /etc/modules.devfs.orig Sun Mar 17 21:38:23 2002 +++ /etc/modules.devfs Sun Mar 24 12:30:23 2002 @@ -122,6 +122,7 @@ # agpgart alias /dev/agpgart agpgart +alias /dev/misc/agpgart agpgart alias /dev/dri* agpgart # Irda devices > Hopefully the guys in hardware can repeat this and publish a workaround > more elegant than disabling devfs. > This should ideally be done for _all_ devices (listed in modules.devfs) and I actually expect it to be in stock modules.devfs as dirributed with devfsd. -andrej From owner-devfs@oss.sgi.com Sun Mar 24 11:03:22 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2OJ3MV11032 for devfs-outgoing; Sun, 24 Mar 2002 11:03:22 -0800 Received: from arm.mrball.net (mrball.net [209.85.130.137]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2OJ3Hq11029 for ; Sun, 24 Mar 2002 11:03:17 -0800 Received: from extmail.mandrakesoft.com ([67.115.223.2]) by arm.mrball.net (8.11.2/8.11.2) with ESMTP id g2OJ5dx04813; Sun, 24 Mar 2002 11:05:40 -0800 Received: from fiji.mandrakesoft.com (fiji.mandrakesoft.com [192.168.3.88]) by extmail.mandrakesoft.com (8.11.3/8.11.3) with ESMTP id g2ON73o08468; Sun, 24 Mar 2002 18:07:03 -0500 Received: by fiji.mandrakesoft.com (Postfix, from userid 501) id 57F571C7FD; Sun, 24 Mar 2002 11:05:19 -0800 (PST) Date: Sun, 24 Mar 2002 11:05:19 -0800 From: Todd Lyons To: Borsenkow Andrej Cc: future@mandrakesoft.com, Thierry Vignaud , devfs mailing list Subject: Re: Symlinks and autoloading (was: Re: [Future] 8.2 errata) Message-ID: <20020324190519.GA21703@mandrakesoft.com> Mail-Followup-To: Borsenkow Andrej , future@mandrakesoft.com, Thierry Vignaud , devfs mailing list References: <20020323005920.GD974@mandrakesecure.net> <20020324001649.GA2114@mandrakesoft.com> <1016962761.2954.6.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline In-Reply-To: <1016962761.2954.6.camel@localhost.localdomain> User-Agent: Mutt/1.3.27i Organization: MandrakeSoft USA Sender: owner-devfs@oss.sgi.com Precedence: bulk --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Borsenkow Andrej wrote on Sun, Mar 24, 2002 at 12:39:15PM +0300 : > =20 > The above happens if somebody manually creates link /dev/agpgart -> > misc/agpgart _or_ updates from Mandrake 8.1. What happens is devfsd > restores (dangling) symlink so no LOOKUP is ever generated by devfs and Good call, this was an upgrade from 8.1. I'll go remove the symlink and let it create the link that is supposed to be there. Thanks Andrej. Regards... Todd --=20 Todd Lyons -- MandrakeSoft, Inc. http://www.mandrakesoft.com/ UNIX was not designed to stop you from doing stupid things, because=20 that would also stop you from doing clever things. -- Doug Gwyn Cooker Version mandrake-release-8.3-0.2mdk Kernel 2.4.18-7mdk --M9NhX3UHpAaciwkO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8niNvlp7v05cW2woRApsuAJ9cBckrKQi4lZIqMv5BlcqJocYv4wCgnSKp cpnXnjZa0I0wULT+bn0aU3E= =8I/c -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO-- From owner-devfs@oss.sgi.com Sun Mar 24 16:09:51 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2P09pW14604 for devfs-outgoing; Sun, 24 Mar 2002 16:09:51 -0800 Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2P09Sq14601 for ; Sun, 24 Mar 2002 16:09:28 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g2P02Di18158; Sun, 24 Mar 2002 17:02:13 -0700 Date: Sun, 24 Mar 2002 17:02:13 -0700 Message-Id: <200203250002.g2P02Di18158@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: Borsenkow Andrej Cc: Todd Lyons , future@mandrakesoft.com, Thierry Vignaud , devfs mailing list Subject: Re: Symlinks and autoloading (was: Re: [Future] 8.2 errata) In-Reply-To: <1016962761.2954.6.camel@localhost.localdomain> References: <20020323005920.GD974@mandrakesecure.net> <20020324001649.GA2114@mandrakesoft.com> <1016962761.2954.6.camel@localhost.localdomain> Sender: owner-devfs@oss.sgi.com Precedence: bulk Borsenkow Andrej writes: > ÷ ÷ÓË, 24.03.2002, × 03:16, Todd Lyons ÎÁÐÉÓÁÌ: > > Vincent Danen wrote on Fri, Mar 22, 2002 at 05:59:20PM -0700 : > > > If anyone has 8.2 errata that needs to go up (I see Tom has posted > > > some problem reports, but I haven't read them all), please send me the > > > text to go on the page in the same format as was used for the 8.1 > > > errata, specificly: > > > > > Error Scenario: No version of X works on i815 chipset (Compaq desktop > > is what I was using). > > Why: devfs interference > > Solution: Reboot with devfs=nomount and then both X 4.2.0 and 3.3.6 > > work. > > > > Has nothing to do with chipset. > > ... > > (EE) GARTInit: AGPIOC_INFO failed (Invalid argument) > > (EE) I810(0): AGP GART support is not available. Make sure your kernel > > has > > agpgart support or that the agpgart kernel module is loaded. > > (EE) Screen(s) found, but none have a usable configuration. > > > ... > > > > Note that it complains about the agpgart module, but the module _was_ > > loaded automatically. > > > > No it was not unless you prove different (there was no lsmod output). I > happen to have i815e motherboard (ASUS CUSL2) and it works ... in > "normal" case. > > The above happens if somebody manually creates link /dev/agpgart -> > misc/agpgart _or_ updates from Mandrake 8.1. What happens is devfsd > restores (dangling) symlink so no LOOKUP is ever generated by devfs and > no module is ever loaded. Just create the above link manually, reboot > and you get exactly the same problem. > > Somewhat trivial but working fix is to always provide aliases for both > compatibility and canonical names. I.e. in our case (verified): > > --- /etc/modules.devfs.orig Sun Mar 17 21:38:23 2002 > +++ /etc/modules.devfs Sun Mar 24 12:30:23 2002 > @@ -122,6 +122,7 @@ > > # agpgart > alias /dev/agpgart agpgart > +alias /dev/misc/agpgart agpgart > alias /dev/dri* agpgart > > # Irda devices > > > Hopefully the guys in hardware can repeat this and publish a workaround > > more elegant than disabling devfs. > > > > This should ideally be done for _all_ devices (listed in > modules.devfs) and I actually expect it to be in stock modules.devfs > as dirributed with devfsd. Yes. Care to send a patch? ;-) My current modules.devfs is appended, for your convenience. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca # /etc/modules.devfs # Richard Gooch 24-MAR-2002 # # THIS IS AN AUTOMATICALLY GENERATED FILE. DO NOT EDIT!!! # THIS FILE WILL BE OVERWRITTEN EACH TIME YOU INSTALL DEVFSD!!! # Modify /etc/modules.conf instead. # This file comes with devfsd-vDEVFSD-VERSION which is available from: # http://www.atnf.csiro.au/~rgooch/linux/ # or directly from: # ftp://ftp.atnf.csiro.au/pub/people/rgooch/linux/daemons/devfsd-vDEVFSD-VERSION.tar.gz ############################################################################### # Sample configurations that you may want to place in /etc/modules.conf # #alias sound-slot-0 sb #alias /dev/v4l bttv #alias /dev/misc/watchdog pcwd #alias gen-md raid0 #alias /dev/joysticks joystick #probeall scsi_hostadapter sym53c8xx ############################################################################### # Generic section: do not change or copy # # All HDDs probeall /dev/discs scsi_hostadapter sd_mod ide-probe-mod ide-disk ide-floppy DAC960 alias /dev/discs/* /dev/discs # All CD-ROMs probeall /dev/cdroms scsi_hostadapter sr_mod ide-probe-mod ide-cd cdrom alias /dev/cdroms/* /dev/cdroms alias /dev/cdrom /dev/cdroms # All tapes probeall /dev/tapes scsi_hostadapter st ide-probe-mod ide-tape alias /dev/tapes/* /dev/tapes # All SCSI devices probeall /dev/scsi scsi_hostadapter sd_mod sr_mod st sg # All IDE devices probeall /dev/ide ide-probe-mod ide-disk ide-cd ide-tape ide-floppy # IDE CD-ROMs alias /dev/ide/*/cd ide-cd # SCSI HDDs probeall /dev/sd scsi_hostadapter sd_mod alias /dev/sd* /dev/sd # SCSI CD-ROMs probeall /dev/sr scsi_hostadapter sr_mod alias /dev/sr* /dev/sr alias /dev/scsi/*/cd sr_mod # SCSI tapes probeall /dev/st scsi_hostadapter st alias /dev/st* /dev/st alias /dev/nst* /dev/st # SCSI generic probeall /dev/sg scsi_hostadapter sg alias /dev/sg* /dev/sg alias /dev/scsi/*/generic /dev/sg alias /dev/pg /dev/sg alias /dev/pg* /dev/sg # Floppies alias /dev/floppy floppy alias /dev/fd* floppy # RAMDISCs alias /dev/rd rd alias /dev/ram* rd # Loop devices alias /dev/loop* loop # Meta devices alias /dev/md* gen-md # Parallel port printers alias /dev/printers* lp alias /dev/lp* /dev/printers # Soundcard alias /dev/sound sound-slot-0 alias /dev/audio /dev/sound alias /dev/mixer /dev/sound alias /dev/dsp /dev/sound alias /dev/dspW /dev/sound alias /dev/midi /dev/sound # Joysticks alias /dev/js* /dev/joysticks # Serial ports alias /dev/tts* serial alias /dev/ttyS* /dev/tts alias /dev/cua* /dev/tts # Input devices alias /dev/input/mouse* mousedev # Miscellaneous devices alias /dev/misc/atibm atixlmouse alias /dev/misc/inportbm msbusmouse alias /dev/misc/logibm busmouse alias /dev/misc/rtc rtc alias /dev/misc/agpgart agpgart alias /dev/rtc /dev/misc/rtc # PPP devices alias /dev/ppp* ppp_generic # Video capture devices alias /dev/video* /dev/v4l alias /dev/vbi* /dev/v4l # agpgart alias /dev/agpgart agpgart alias /dev/dri* agpgart # Irda devices alias /dev/ircomm ircomm-tty alias /dev/ircomm* /dev/ircomm # Raw I/O devices alias /dev/rawctl /dev/raw # Pull in the configuration file. Do this last because modprobe(8) processes in # per^H^H^Hreverse order and the sysadmin may want to over-ride what is in the # generic file include /etc/modules.conf From owner-devfs@oss.sgi.com Sun Mar 24 16:22:20 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2P0MKB14713 for devfs-outgoing; Sun, 24 Mar 2002 16:22:20 -0800 Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2P0MHq14707 for ; Sun, 24 Mar 2002 16:22:17 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g2P0OWl18486; Sun, 24 Mar 2002 17:24:32 -0700 Date: Sun, 24 Mar 2002 17:24:32 -0700 Message-Id: <200203250024.g2P0OWl18486@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: Juan Quintela Cc: Borsenkow Andrej , "'Thierry Vignaud'" , kernel@mandrakesoft.com, "'devfs mailing list'" , "'Frederic Lepied'" Subject: Unresolved devfs/devfsd hang References: <000601c1b56b$241be2e0$21c9ca95@mow.siemens.ru> <200202141750.g1EHo2G12220@vindaloo.ras.ucalgary.ca> <200203130612.g2D6Cbl05869@vindaloo.ras.ucalgary.ca> Sender: owner-devfs@oss.sgi.com Precedence: bulk Juan, I note that the problem reported last month with a pair of minilogd's and devfsd apparently deadlocking still doesn't have a solution. I'm still waiting for an strace of devfsd so that I can figure out what's going wrong. Merely delaying the start of devfsd may simply be hiding a deadlock in the devfs code. Please take a little time to reproduce the deadlock and strace devfsd. I want to resolve this issue. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Sun Mar 24 22:56:54 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2P6ush19288 for devfs-outgoing; Sun, 24 Mar 2002 22:56:54 -0800 Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2P6uiq19285 for ; Sun, 24 Mar 2002 22:56:44 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g2P6wjt23915; Sun, 24 Mar 2002 23:58:45 -0700 Date: Sun, 24 Mar 2002 23:58:45 -0700 Message-Id: <200203250658.g2P6wjt23915@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: linux-kernel@vger.kernel.org, devfs-announce-list@vindaloo.ras.ucalgary.ca Subject: devfsd-v1.3.25 available Sender: owner-devfs@oss.sgi.com Precedence: bulk Hi, all. I've just released version 1.3.25 of my devfsd (devfs daemon) at: http://www.atnf.csiro.au/~rgooch/linux/ Tarball directly available from: ftp://ftp.??.kernel.org/pub/linux/daemons/devfsd/devfsd.tar.gz AND: ftp://ftp.atnf.csiro.au/pub/people/rgooch/linux/daemons/devfsd/devfsd.tar.gz This works with devfs-patch-v130, kernel 2.3.46 and devfs-patch-v99.7 (or later). The main changes are: - Minor GNUmakefile tweak for newer versions of sort(1) - Added signal handler for SIGUSR1 (re-read config but don't generate synthetic events) - Make /lib/devfsd the default directory for shared objects - Set close-on-exec flag for .devfsd control file - Set umask so that mknod(2) open(2) and mkdir(2) have complete control over permissions - Added sample entries to devfsd.conf for USB mouse - Added ide-floppy to modules.devfs list for /dev/discs - Added /dev/pg and /dev/pg* to modules.devfs list for SCSI generic driver - Added entry to modules.devfs for AGPGART driver - Added entry to modules.devfs for raw I/O driver. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Mon Mar 25 07:25:49 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2PFPn217364 for devfs-outgoing; Mon, 25 Mar 2002 07:25:49 -0800 Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2PFPfq17356 for ; Mon, 25 Mar 2002 07:25:42 -0800 Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.11.6/8.11.6) with ESMTP id g2PFS3d05925 for ; Mon, 25 Mar 2002 16:28:04 +0100 (MET) Received: from mowp002a.mowp.siemens.ru (mowp002a.mowp.siemens.ru [149.202.148.230]) by mail2.siemens.de (8.11.6/8.11.6) with ESMTP id g2PFS2C06876 for ; Mon, 25 Mar 2002 16:28:03 +0100 (MET) Received: by mowp002a.mowp.siemens.ru with Internet Mail Service (5.5.2653.19) id ; Mon, 25 Mar 2002 18:17:17 +0300 Received: from [149.202.201.201] (149.202.201.201 [149.202.201.201]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id H3XG63ZK; Mon, 25 Mar 2002 18:32:45 +0300 From: Borsenkow Andrej To: devfs mailing list Subject: [Fwd: PATCH: modules.devfs scd fix] Content-Type: text/plain; charset=ISO-8859-1 X-Mailer: Evolution/1.0.2-4mdk Date: 25 Mar 2002 18:27:50 +0300 Message-Id: <1017070076.3775.4.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id g2PFPgq17358 Sender: owner-devfs@oss.sgi.com Precedence: bulk To prove that it is needed: {vc/1}:~%> ll /dev/scsi/host1/bus0/target3/lun0/cd brw------- 1 bor cdrom 11, 0 ñÎ× 1 1970 /dev/scsi/host1/bus0/target3/lun0/cd {vc/1}:~%> sudo rmmod ide-scsi {vc/1}:~%> ll /dev/scsi/host1/bus0/target3/lun0/cd ls: /dev/scsi/host1/bus0/target3/lun0/cd: No such file or directory {vc/1}:~%> sudo mv /etc/modules.devfs /etc/modules.devfs.orig {vc/1}:~%> sudo mv /etc/modules.devfs.new /etc/modules.devfs {vc/1}:~%> ll /dev/scsi/host1/bus0/target3/lun0/cd brw------- 1 bor cdrom 11, 0 ñÎ× 1 1970 /dev/scsi/host1/bus0/target3/lun0/cd regards -andrej --- /etc/modules.devfs.orig Sun Mar 17 21:38:23 2002 +++ /etc/modules.devfs Sun Mar 17 21:41:39 2002 @@ -54,7 +54,7 @@ # SCSI CD-ROMs probeall /dev/scd scsi_hostadapter sr_mod alias /dev/scd* /dev/scd -alias /dev/scsi/*/cd sr_mod +alias /dev/scsi/*/cd /dev/scd # SCSI tapes probeall /dev/st scsi_hostadapter st From owner-devfs@oss.sgi.com Mon Mar 25 10:15:46 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2PIFkC23782 for devfs-outgoing; Mon, 25 Mar 2002 10:15:46 -0800 Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2PIFeq23778 for ; Mon, 25 Mar 2002 10:15:41 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g2PI8ED29878; Mon, 25 Mar 2002 11:08:14 -0700 Date: Mon, 25 Mar 2002 11:08:14 -0700 Message-Id: <200203251808.g2PI8ED29878@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: Borsenkow Andrej Cc: devfs mailing list Subject: Re: [Fwd: PATCH: modules.devfs scd fix] In-Reply-To: <1017070076.3775.4.camel@localhost.localdomain> References: <1017070076.3775.4.camel@localhost.localdomain> Sender: owner-devfs@oss.sgi.com Precedence: bulk Borsenkow Andrej writes: > To prove that it is needed: > > {vc/1}:~%> ll /dev/scsi/host1/bus0/target3/lun0/cd > brw------- 1 bor cdrom 11, 0 ñÎ× 1 1970 > /dev/scsi/host1/bus0/target3/lun0/cd > {vc/1}:~%> sudo rmmod ide-scsi > {vc/1}:~%> ll /dev/scsi/host1/bus0/target3/lun0/cd > ls: /dev/scsi/host1/bus0/target3/lun0/cd: No such file or directory > {vc/1}:~%> sudo mv /etc/modules.devfs /etc/modules.devfs.orig > {vc/1}:~%> sudo mv /etc/modules.devfs.new /etc/modules.devfs > {vc/1}:~%> ll /dev/scsi/host1/bus0/target3/lun0/cd > brw------- 1 bor cdrom 11, 0 ñÎ× 1 1970 > /dev/scsi/host1/bus0/target3/lun0/cd > > regards > > -andrej > > > --- /etc/modules.devfs.orig Sun Mar 17 21:38:23 2002 > +++ /etc/modules.devfs Sun Mar 17 21:41:39 2002 > @@ -54,7 +54,7 @@ > # SCSI CD-ROMs > probeall /dev/scd scsi_hostadapter sr_mod > alias /dev/scd* /dev/scd > -alias /dev/scsi/*/cd sr_mod > +alias /dev/scsi/*/cd /dev/scd OK, I've done this (except that I use the official /dev/sr name instead of the renegade /dev/scd name). BTW: your line: probeall /dev/scd scsi_hostadapter sr_mod is wrong in any case, because that line is supposed to be for the "new compatibility" names (i.e. /dev/sr/c0b0t6u0) that devfsd creates. So you've broken autoloading using the new compatibility names. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Tue Mar 26 21:47:56 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2R5luo25130 for devfs-outgoing; Tue, 26 Mar 2002 21:47:56 -0800 Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2R5lqq25125 for ; Tue, 26 Mar 2002 21:47:52 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g2R5nwa14492; Tue, 26 Mar 2002 22:49:58 -0700 Date: Tue, 26 Mar 2002 22:49:58 -0700 Message-Id: <200203270549.g2R5nwa14492@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: linux-kernel@vger.kernel.org, devfs-announce-list@vindaloo.ras.ucalgary.ca Subject: [PATCH] devfs v199.10 available Sender: owner-devfs@oss.sgi.com Precedence: bulk Hi, all. Version 199.10 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-pre4. Highlights of this release: - Changed to allow later additions if not yet empty - Added calls to in drivers/block/blkpc.c and - Updated README from master HTML file - Fixed bug in : was clearing beyond bitfield - Fixed bitfield data type for - Made major bitfield type and initialiser 64 bit safe Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Fri Mar 29 02:30:38 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2TAUcV06265 for devfs-outgoing; Fri, 29 Mar 2002 02:30:38 -0800 Received: from bunny.shuttle.de (bunny.shuttle.de [193.174.247.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2TAUOq06257; Fri, 29 Mar 2002 02:30:24 -0800 Received: by bunny.shuttle.de (Postfix, from userid 112) id 59B2E4E567; Fri, 29 Mar 2002 11:32:44 +0100 (CET) Date: Fri, 29 Mar 2002 11:32:44 +0100 To: linux-mips@oss.sgi.com Cc: devfs@oss.sgi.com Subject: broken devfs-support in SGI Zilog8530 serial driver Message-ID: <20020329103244.GA15765@bunny.shuttle.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="mYCpIKhGyMATD0i+" Content-Disposition: inline User-Agent: Mutt/1.3.28i From: raoul@shuttle.de (Raoul Borenius) Sender: owner-devfs@oss.sgi.com Precedence: bulk --mYCpIKhGyMATD0i+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, I'm not sure if this is a devfs or mips problem so I'm sending it to both lists. I just compiled my own mips-kernel from oss.sgi.com:/cvs to get devfs-support. Unfortunately there seems to be a problem with the serial-driver at least in the linux_2_4 branch: SGI Zilog8530 serial driver version 1.00 devfs_register(ttyS): could not append to parent, err: -17 devfs_register(cua): could not append to parent, err: -17 tty00 at 0xbfbd9830 (irq = 29) is a Zilog8530 tty01 at 0xbfbd9838 (irq = 29) is a Zilog8530 The result is that the directories /dev/tts and /dev/cua are missing. There are only the files /dev/ttS and /dev/cua which can be used to get access to the first serial port. I have attached the full dmesg output at the end. Regards Raoul --mYCpIKhGyMATD0i+ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=dmesg ARCH: SGI-IP22 PROMLIB: ARC firmware Version 1 Revision 10 CPU: MIPS-R4600 FPU ICACHE DCACHE CPU revision is: 00002020 FPU revision is: 00002020 Primary instruction cache 16kb, linesize 32 bytes. Primary data cache 16kb, linesize 32 bytes. Linux version 2.4.18-cvs-mips-20020328 (root@testserv) (gcc version 2.95.4 20011002 (Debian prerelease)) #1 Thu Mar 28 21:59:35 CET 2002 MC: SGI memory controller Revision 3 Determined physical RAM map: memory: 00001000 @ 00000000 (reserved) memory: 00001000 @ 00001000 (reserved) memory: 0020d000 @ 08002000 (usable) memory: 0000d000 @ 0820f000 (reserved) memory: 00524000 @ 0821c000 (usable) memory: 000c0000 @ 08740000 (ROM data) memory: 09800000 @ 08800000 (usable) On node 0 totalpages: 73728 zone(0): 73728 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: root=/dev/sda1 console=/dev/ttyS0 ro auto Calibrating system timer... 665000 [133.00 MHz CPU] NG1: Revision 6, 8 bitplanes, REX3 revision B, VC2 revision A, xmap9 revision A, cmap revision D, bt445 revision D NG1: Screensize 1024x768 Console: colour SGI Newport 128x48 zs0: console input Console: ttyS0 (Zilog8530), 9600 baud Calibrating delay loop... 132.71 BogoMIPS Memory: 156664k/163012k available (1370k kernel code, 6348k reserved, 164k data, 68k init, 0k highmem) Dentry-cache hash table entries: 65536 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) Mount-cache hash table entries: 8192 (order: 4, 65536 bytes) Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes) Page-cache hash table entries: 131072 (order: 7, 524288 bytes) Checking for 'wait' instruction... available. POSIX conformance testing by UNIFIX Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Starting kswapd VFS: Diskquotas version dquot_6.4.0 initialized Journalled Block Device driver loaded devfs: v1.10 (20020120) Richard Gooch (rgooch@atnf.csiro.au) devfs: boot_options: 0x1 initialize_kbd: Keyboard reset failed, no ACK keyboard: Timeout - AT keyboard not present?(ed) keyboard: Timeout - AT keyboard not present?(f4) pty: 256 Unix98 ptys configured DS1286 Real Time Clock Driver v1.0 streamable misc devices registered (keyb:150, gfx:148) block: 128 slots per queue, batch=32 sgiseeq.c: David S. Miller (dm@engr.sgi.com) eth0: SGI Seeq8003 08:00:69:0b:17:50 SCSI subsystem driver Revision: 1.00 wd33c93-0: chip=WD33c93B/13 no_sync=0xff no_dma=0 debug_flags=0x00 setup_args=,,,,,,,,, Version 1.25 - 09/Jul/1997, Compiled Mar 28 2002 at 22:18:11 scsi0 : SGI WD93 sending SDTR 0103013f0csync_xfer=2c Vendor: IBM Model: DORS-32160 Rev: WA6A Type: Direct-Access ANSI SCSI revision: 02 sending SDTR 0103013f0csync_xfer=2c Vendor: SGI Model: SEAGATE ST51080N Rev: 0950 Type: Direct-Access ANSI SCSI revision: 02 Attached scsi disk sda at scsi0, channel 0, id 1, lun 0 Attached scsi disk sdb at scsi0, channel 0, id 2, lun 0 SCSI device sda: 4226725 512-byte hdwr sectors (2164 MB) Partition check: /dev/scsi/host0/bus0/target1/lun0: p1 p2 p3 p4 p5 SCSI device sdb: 2070235 512-byte hdwr sectors (1060 MB) /dev/scsi/host0/bus0/target2/lun0: p1 p2 p3 p4 SGI Zilog8530 serial driver version 1.00 devfs_register(ttyS): could not append to parent, err: -17 devfs_register(cua): could not append to parent, err: -17 tty00 at 0xbfbd9830 (irq = 29) is a Zilog8530 tty01 at 0xbfbd9838 (irq = 29) is a Zilog8530 NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 2048 buckets, 16Kbytes TCP: Hash tables configured (established 32768 bind 32768) VFS: Mounted root (ext2 filesystem) readonly. Mounted devfs on /dev Freeing prom memory: 768kb freed Freeing unused kernel memory: 68k freed NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. Adding Swap: 262176k swap-space (priority -1) --mYCpIKhGyMATD0i+-- From owner-devfs@oss.sgi.com Fri Mar 29 02:59:44 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2TAxif07120 for devfs-outgoing; Fri, 29 Mar 2002 02:59:44 -0800 Received: from thoth.sbs.de (thoth.sbs.de [192.35.17.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2TAxdq07117; Fri, 29 Mar 2002 02:59:39 -0800 Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by thoth.sbs.de (8.11.6/8.11.6) with ESMTP id g2TB20X25723; Fri, 29 Mar 2002 12:02:00 +0100 (MET) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail2.siemens.de (8.11.6/8.11.6) with ESMTP id g2TB1wC17247; Fri, 29 Mar 2002 12:01:58 +0100 (MET) Received: by mowd019a.mow.siemens.ru with Internet Mail Service (5.5.2653.19) id ; Fri, 29 Mar 2002 14:06:55 +0300 Received: from MW1G17C ([163.242.193.31]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id H6D31HL1; Fri, 29 Mar 2002 14:06:53 +0300 From: Borsenkow Andrej To: "'Raoul Borenius'" , linux-mips@oss.sgi.com Cc: devfs@oss.sgi.com Subject: RE: broken devfs-support in SGI Zilog8530 serial driver Date: Fri, 29 Mar 2002 14:01:54 +0300 Message-ID: <000001c1d711$2492f070$1fc1f2a3@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 Importance: Normal In-Reply-To: <20020329103244.GA15765@bunny.shuttle.de> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-devfs@oss.sgi.com Precedence: bulk > I'm not sure if this is a devfs or mips problem so I'm sending it > to both lists. > > I just compiled my own mips-kernel from oss.sgi.com:/cvs to get > devfs-support. Unfortunately there seems to be a problem with the > serial-driver at least in the linux_2_4 branch: > > SGI Zilog8530 serial driver version 1.00 > devfs_register(ttyS): could not append to parent, err: -17 This means that somebody else registered ttyS (and cua) before Zilog8530 driver attempted to do it. The possible reason could be that driver calls tty_register_devfs itself in this case it must set TTY_DRIVER_NO_DEVFS flag to prevent the same nodes registered by tty_register_driver. -andrej > devfs_register(cua): could not append to parent, err: -17 > tty00 at 0xbfbd9830 (irq = 29) is a Zilog8530 > tty01 at 0xbfbd9838 (irq = 29) is a Zilog8530 > > The result is that the directories /dev/tts and /dev/cua are missing. > > There are only the files /dev/ttS and /dev/cua which can be used to get > access to the first serial port. > > I have attached the full dmesg output at the end. > > Regards > > Raoul From owner-devfs@oss.sgi.com Fri Mar 29 05:25:55 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2TDPtV15905 for devfs-outgoing; Fri, 29 Mar 2002 05:25:55 -0800 Received: from bunny.shuttle.de (bunny.shuttle.de [193.174.247.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2TDOSq15886; Fri, 29 Mar 2002 05:24:28 -0800 Received: by bunny.shuttle.de (Postfix, from userid 112) id 4C6264E567; Fri, 29 Mar 2002 14:26:50 +0100 (CET) Date: Fri, 29 Mar 2002 14:26:50 +0100 To: Borsenkow Andrej Cc: "'Raoul Borenius'" , linux-mips@oss.sgi.com, devfs@oss.sgi.com Subject: Re: broken devfs-support in SGI Zilog8530 serial driver Message-ID: <20020329132650.GA16905@bunny.shuttle.de> References: <20020329103244.GA15765@bunny.shuttle.de> <000001c1d711$2492f070$1fc1f2a3@mow.siemens.ru> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline In-Reply-To: <000001c1d711$2492f070$1fc1f2a3@mow.siemens.ru> User-Agent: Mutt/1.3.28i From: raoul@shuttle.de (Raoul Borenius) Sender: owner-devfs@oss.sgi.com Precedence: bulk --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi Andrej, On Fri, Mar 29, 2002 at 02:01:54PM +0300, Borsenkow Andrej wrote: > > I'm not sure if this is a devfs or mips problem so I'm sending it > > to both lists. > > > > I just compiled my own mips-kernel from oss.sgi.com:/cvs to get > > devfs-support. Unfortunately there seems to be a problem with the > > serial-driver at least in the linux_2_4 branch: > > > > SGI Zilog8530 serial driver version 1.00 > > devfs_register(ttyS): could not append to parent, err: -17 > > This means that somebody else registered ttyS (and cua) before Zilog8530 > driver attempted to do it. The possible reason could be that driver > calls tty_register_devfs itself in this case it must set > TTY_DRIVER_NO_DEVFS flag to prevent the same nodes registered by > tty_register_driver. Yeah, but I think the serial ports should be placed under /dev/tts/* and /dev/cua/*, shouldn't they? Which driver could have registered /dev/ttyS? if I search the kernel-sources under arch/mips I get testserv (raoul) ~/linux_2_4/linux/arch/mips> find . -name \*.c | xargs grep ttyS ./arc/arc_con.c: "ttyS", ./au1000/common/serial.c: printk("Testing ttyS%d (0x%04lx, 0x%04x)...\n", state->line, ./au1000/common/serial.c: serial_driver.name = "ttyS"; ./au1000/common/serial.c: printk(KERN_INFO "ttyS%02d%s at 0x%04lx (irq = %d) is a %s\n", ./au1000/common/serial.c: printk(KERN_INFO "ttyS%02d at %s 0x%04lx (irq = %d) is a %s\n", ./au1000/common/serial.c: name: "ttyS", ./au1000/pb1000/setup.c: strcat(argptr, " console=ttyS0,115200"); ./au1000/pb1500/setup.c: strcat(argptr, " console=ttyS0,115200"); ./baget/vacserial.c: serial_driver.name = "ttyS"; ./baget/vacserial.c: printk(KERN_INFO "ttyS%02d%s at 0x%04x (irq = %d) is a %s\n", ./baget/vacserial.c: name: "ttyS", ./baget/vacserial.c: autoconfig(info); /* autoconfigure ttyS0, whatever that is */ ./cobalt/setup.c:char arcs_cmdline[CL_SIZE] = { "console=ttyS0,115200 root=/dev/hda1" }; ./dec/promcon.c: name: "ttyS", ./galileo-boards/ev64120/promcon.c: "ttyS", ./galileo-boards/ev64120/setup.c:char arcs_cmdline[CL_SIZE] = { "console=ttyS0,115200 " ./galileo-boards/ev96100/setup.c: strcat(argptr, " console=ttyS0,115200"); ./ite-boards/generic/it8172_setup.c: strcat(argptr, " console=ttyS0,115200"); ./jmr3927/rbhma3100/setup.c: strcat(argptr, " console=ttyS1,115200"); ./kernel/gdb-stub.c: * (gdb) target remote /dev/ttyS1 ./mips-boards/atlas/atlas_setup.c: if ((argptr = strstr(argptr, "console=ttyS0")) == NULL) { ./mips-boards/atlas/atlas_setup.c: strcpy(serial_console, "ttyS0,"); ./mips-boards/atlas/atlas_setup.c: if ((argptr = strstr(argptr, "kgdb=ttyS")) != NULL) { ./mips-boards/atlas/atlas_setup.c: argptr += strlen("kgdb=ttyS"); ./mips-boards/atlas/atlas_setup.c: printk("KGDB: Uknown serial line /dev/ttyS%c, " ./mips-boards/atlas/atlas_setup.c: "falling back to /dev/ttyS1\n", *argptr); ./mips-boards/atlas/atlas_setup.c: printk("KGDB: Using serial line /dev/ttyS%d for session\n", ./mips-boards/atlas/atlas_setup.c: prom_printf("KGDB: Using serial line /dev/ttyS%d for session, " ./mips-boards/malta/malta_setup.c: strcat(argptr, " console=ttyS0,38400"); ./mips-boards/malta/malta_setup.c: if ((argptr = strstr(argptr, "kgdb=ttyS")) != NULL) { ./mips-boards/malta/malta_setup.c: argptr += strlen("kgdb=ttyS"); ./mips-boards/malta/malta_setup.c: printk("KGDB: Uknown serial line /dev/ttyS%c, " ./mips-boards/malta/malta_setup.c: "falling back to /dev/ttyS1\n", *argptr); ./mips-boards/malta/malta_setup.c: printk("KGDB: Using serial line /dev/ttyS%d for session\n", ./mips-boards/malta/malta_setup.c: prom_printf("KGDB: Using serial line /dev/ttyS%d for session, " ./philips/nino/prom.c: strcpy(arcs_cmdline, "console=tty0 console=ttyS0,115200"); ./sgi-ip22/ip22-setup.c: console_setup ("ttyS1"); ./sgi-ip22/ip22-setup.c: console_setup ("ttyS0"); ./sgi-ip22/ip22-setup.c: console_setup("ttyS0"); testserv (raoul) ~/linux_2_4/linux/arch/mips> but I have not compiled support for arc console (when do you need that btw?) and all other drivers do not apply to IP22 AFAIK. My .config is attached below. Regards Raoul --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="config-2.4.18-cvs-mips-20020328" # # Automatically generated make config: don't edit # CONFIG_MIPS=y CONFIG_MIPS32=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Machine selection # # CONFIG_ACER_PICA_61 is not set # CONFIG_ALGOR_P4032 is not set # CONFIG_BAGET_MIPS is not set # CONFIG_MIPS_COBALT is not set # CONFIG_DECSTATION is not set # CONFIG_DDB5074 is not set # CONFIG_MIPS_EV64120 is not set # CONFIG_MIPS_EV96100 is not set # CONFIG_MIPS_ATLAS is not set # CONFIG_MIPS_MALTA is not set # CONFIG_NINO is not set # CONFIG_SIBYTE_SB1250 is not set # CONFIG_MIPS_MAGNUM_4000 is not set # CONFIG_MOMENCO_OCELOT is not set # CONFIG_DDB5476 is not set # CONFIG_DDB5477 is not set # CONFIG_NEC_OSPREY is not set # CONFIG_OLIVETTI_M700 is not set CONFIG_SGI_IP22=y # CONFIG_SNI_RM200_PCI is not set # CONFIG_MIPS_ITE8172 is not set # CONFIG_MIPS_IVR is not set # CONFIG_MIPS_PB1000 is not set # CONFIG_MIPS_PB1500 is not set # CONFIG_TOSHIBA_JMR3927 is not set # CONFIG_HP_LASERJET is not set # CONFIG_HIGHMEM is not set CONFIG_RWSEM_GENERIC_SPINLOCK=y # CONFIG_RWSEM_XCHGADD_ALGORITHM is not set # CONFIG_MCA is not set # CONFIG_SBUS is not set CONFIG_ARC32=y CONFIG_BOARD_SCACHE=y CONFIG_IRQ_CPU=y CONFIG_PC_KEYB=y CONFIG_SGI=y CONFIG_NEW_IRQ=y CONFIG_NEW_TIME_C=y CONFIG_NONCOHERENT_IO=y # CONFIG_ISA is not set # CONFIG_EISA is not set # # Loadable module support # CONFIG_MODULES=y # CONFIG_MODVERSIONS is not set CONFIG_KMOD=y # # CPU selection # # CONFIG_CPU_R3000 is not set # CONFIG_CPU_TX39XX is not set # CONFIG_CPU_R6000 is not set # CONFIG_CPU_VR41XX is not set # CONFIG_CPU_R4300 is not set CONFIG_CPU_R4X00=y # CONFIG_CPU_TX49XX is not set # CONFIG_CPU_R5000 is not set # CONFIG_CPU_R5432 is not set # CONFIG_CPU_RM7000 is not set # CONFIG_CPU_NEVADA is not set # CONFIG_CPU_R10000 is not set # CONFIG_CPU_SB1 is not set # CONFIG_CPU_MIPS32 is not set # CONFIG_CPU_MIPS64 is not set # CONFIG_64BIT_PHYS_ADDR is not set # CONFIG_CPU_ADVANCED is not set CONFIG_CPU_HAS_LLSC=y CONFIG_CPU_HAS_LLDSCD=y # CONFIG_CPU_HAS_WB is not set # # General setup # # CONFIG_CPU_LITTLE_ENDIAN is not set CONFIG_KCORE_ELF=y CONFIG_ELF_KERNEL=y # CONFIG_BINFMT_IRIX is not set CONFIG_FORWARD_KEYBOARD=y # CONFIG_ARC_CONSOLE is not set # CONFIG_BINFMT_AOUT is not set CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=m CONFIG_NET=y # CONFIG_HOTPLUG is not set # CONFIG_PCMCIA is not set # CONFIG_HOTPLUG_PCI is not set CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # # CONFIG_PARPORT is not set # # Block devices # # CONFIG_BLK_DEV_FD is not set # CONFIG_BLK_DEV_XD is not set # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set CONFIG_BLK_DEV_LOOP=m CONFIG_BLK_DEV_NBD=m CONFIG_BLK_DEV_RAM=m CONFIG_BLK_DEV_RAM_SIZE=4096 # CONFIG_BLK_DEV_INITRD is not set # # Multi-device support (RAID and LVM) # CONFIG_MD=y CONFIG_BLK_DEV_MD=m CONFIG_MD_LINEAR=m CONFIG_MD_RAID0=m CONFIG_MD_RAID1=m CONFIG_MD_RAID5=m CONFIG_MD_MULTIPATH=m CONFIG_BLK_DEV_LVM=m # # Networking options # CONFIG_PACKET=m CONFIG_PACKET_MMAP=y CONFIG_NETLINK_DEV=m # CONFIG_NETFILTER is not set CONFIG_FILTER=y CONFIG_UNIX=m CONFIG_INET=y CONFIG_IP_MULTICAST=y # CONFIG_IP_ADVANCED_ROUTER is not set # CONFIG_IP_PNP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_IP_MROUTE is not set # CONFIG_ARPD is not set # CONFIG_INET_ECN is not set CONFIG_SYN_COOKIES=y CONFIG_IPV6=m # CONFIG_KHTTPD is not set # CONFIG_ATM is not set # CONFIG_VLAN_8021Q is not set # # # # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_DECNET is not set # CONFIG_BRIDGE is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_LLC is not set # CONFIG_NET_DIVERT is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set # CONFIG_NET_FASTROUTE is not set # CONFIG_NET_HW_FLOWCONTROL is not set # # QoS and/or fair queueing # # CONFIG_NET_SCHED is not set # # Telephony Support # # CONFIG_PHONE is not set # CONFIG_PHONE_IXJ is not set # CONFIG_PHONE_IXJ_PCMCIA is not set # # SCSI support # CONFIG_SCSI=y # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=y CONFIG_SD_EXTRA_DEVS=40 CONFIG_CHR_DEV_ST=m # CONFIG_CHR_DEV_OSST is not set CONFIG_BLK_DEV_SR=m # CONFIG_BLK_DEV_SR_VENDOR is not set CONFIG_SR_EXTRA_DEVS=2 CONFIG_CHR_DEV_SG=m # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # # CONFIG_SCSI_DEBUG_QUEUES is not set CONFIG_SCSI_MULTI_LUN=y CONFIG_SCSI_CONSTANTS=y # CONFIG_SCSI_LOGGING is not set # # SCSI low-level drivers # CONFIG_SGIWD93_SCSI=y # CONFIG_SCSI_7000FASST is not set # CONFIG_SCSI_ACARD is not set # CONFIG_SCSI_AHA152X is not set # CONFIG_SCSI_AHA1542 is not set # CONFIG_SCSI_AHA1740 is not set # CONFIG_SCSI_AACRAID is not set # CONFIG_SCSI_AIC7XXX is not set # CONFIG_SCSI_AIC7XXX_OLD is not set # CONFIG_SCSI_DPT_I2O is not set # CONFIG_SCSI_ADVANSYS is not set # CONFIG_SCSI_IN2000 is not set # CONFIG_SCSI_AM53C974 is not set # CONFIG_SCSI_MEGARAID is not set # CONFIG_SCSI_BUSLOGIC is not set # CONFIG_SCSI_DMX3191D is not set # CONFIG_SCSI_DTC3280 is not set # CONFIG_SCSI_EATA is not set # CONFIG_SCSI_EATA_DMA is not set # CONFIG_SCSI_EATA_PIO is not set # CONFIG_SCSI_FUTURE_DOMAIN is not set # CONFIG_SCSI_GDTH is not set # CONFIG_SCSI_GENERIC_NCR5380 is not set # CONFIG_SCSI_INITIO is not set # CONFIG_SCSI_INIA100 is not set # CONFIG_SCSI_NCR53C406A is not set # CONFIG_SCSI_NCR53C7xx is not set # CONFIG_SCSI_PAS16 is not set # CONFIG_SCSI_PCI2000 is not set # CONFIG_SCSI_PCI2220I is not set # CONFIG_SCSI_PSI240I is not set # CONFIG_SCSI_QLOGIC_FAS is not set # CONFIG_SCSI_SIM710 is not set # CONFIG_SCSI_SYM53C416 is not set # CONFIG_SCSI_T128 is not set # CONFIG_SCSI_U14_34F is not set # CONFIG_SCSI_DEBUG is not set # # Network device support # CONFIG_NETDEVICES=y # # ARCnet devices # # CONFIG_ARCNET is not set CONFIG_DUMMY=m # CONFIG_BONDING is not set # CONFIG_EQUALIZER is not set # CONFIG_TUN is not set # CONFIG_ETHERTAP is not set # # Ethernet (10 or 100Mbit) # CONFIG_NET_ETHERNET=y # CONFIG_SUNLANCE is not set # CONFIG_SUNBMAC is not set # CONFIG_SUNQE is not set # CONFIG_SUNGEM is not set # CONFIG_NET_VENDOR_3COM is not set # CONFIG_LANCE is not set # CONFIG_NET_VENDOR_SMC is not set # CONFIG_NET_VENDOR_RACAL is not set # CONFIG_NET_ISA is not set # CONFIG_NET_PCI is not set # CONFIG_NET_POCKET is not set CONFIG_SGISEEQ=y # # Ethernet (1000 Mbit) # # CONFIG_ACENIC is not set # CONFIG_DL2K is not set # CONFIG_MYRI_SBUS is not set # CONFIG_NS83820 is not set # CONFIG_HAMACHI is not set # CONFIG_YELLOWFIN is not set # CONFIG_SK98LIN is not set # CONFIG_FDDI is not set # CONFIG_HIPPI is not set # CONFIG_PLIP is not set # CONFIG_PPP is not set # CONFIG_SLIP is not set # # Wireless LAN (non-hamradio) # # CONFIG_NET_RADIO is not set # # Token Ring devices # # CONFIG_TR is not set # CONFIG_NET_FC is not set # CONFIG_RCPCI is not set # CONFIG_SHAPER is not set # # Wan interfaces # # CONFIG_WAN is not set # # Amateur Radio support # # CONFIG_HAMRADIO is not set # # IrDA (infrared) support # # CONFIG_IRDA is not set # # ISDN subsystem # # CONFIG_ISDN is not set # # Old CD-ROM drivers (not SCSI, not IDE) # # CONFIG_CD_NO_IDESCSI is not set # # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y # CONFIG_SERIAL is not set # CONFIG_SERIAL_EXTENDED is not set # CONFIG_SERIAL_NONSTANDARD is not set CONFIG_UNIX98_PTYS=y CONFIG_UNIX98_PTY_COUNT=256 # # I2C support # # CONFIG_I2C is not set # # Mice # # CONFIG_BUSMOUSE is not set # CONFIG_MOUSE is not set # # Joysticks # # CONFIG_INPUT_GAMEPORT is not set # # Input core support is needed for gameports # # # Input core support is needed for joysticks # # CONFIG_QIC02_TAPE is not set # # Watchdog Cards # CONFIG_WATCHDOG=y # CONFIG_WATCHDOG_NOWAYOUT is not set # CONFIG_SOFT_WATCHDOG is not set # CONFIG_WDT is not set # CONFIG_WDTPCI is not set # CONFIG_PCWATCHDOG is not set # CONFIG_ACQUIRE_WDT is not set # CONFIG_ADVANTECH_WDT is not set # CONFIG_EUROTECH_WDT is not set # CONFIG_IB700_WDT is not set # CONFIG_I810_TCO is not set # CONFIG_MIXCOMWD is not set # CONFIG_60XX_WDT is not set # CONFIG_W83877F_WDT is not set # CONFIG_MACHZ_WDT is not set CONFIG_INDYDOG=m # CONFIG_INTEL_RNG is not set # CONFIG_NVRAM is not set # CONFIG_RTC is not set # CONFIG_DTLK is not set # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # # Ftape, the floppy tape device driver # # CONFIG_FTAPE is not set # CONFIG_AGP is not set # CONFIG_DRM is not set # # Multimedia devices # # CONFIG_VIDEO_DEV is not set # # SGI Character devices # CONFIG_SGI_NEWPORT_CONSOLE=y CONFIG_FONT_8x16=y # # File systems # CONFIG_QUOTA=y # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set # CONFIG_REISERFS_FS is not set # CONFIG_REISERFS_CHECK is not set # CONFIG_REISERFS_PROC_INFO is not set # CONFIG_ADFS_FS is not set # CONFIG_ADFS_FS_RW is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_BFS_FS is not set CONFIG_EXT3_FS=y CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set # CONFIG_FAT_FS is not set # CONFIG_MSDOS_FS is not set # CONFIG_UMSDOS_FS is not set # CONFIG_VFAT_FS is not set # CONFIG_EFS_FS is not set # CONFIG_JFFS_FS is not set # CONFIG_JFFS2_FS is not set # CONFIG_CRAMFS is not set CONFIG_TMPFS=y # CONFIG_RAMFS is not set CONFIG_ISO9660_FS=m CONFIG_JOLIET=y CONFIG_ZISOFS=y # CONFIG_MINIX_FS is not set # CONFIG_VXFS_FS is not set # CONFIG_NTFS_FS is not set # CONFIG_NTFS_RW is not set # CONFIG_HPFS_FS is not set CONFIG_PROC_FS=y CONFIG_DEVFS_FS=y CONFIG_DEVFS_MOUNT=y # CONFIG_DEVFS_DEBUG is not set # CONFIG_DEVPTS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_QNX4FS_RW is not set # CONFIG_ROMFS_FS is not set CONFIG_EXT2_FS=y # CONFIG_SYSV_FS is not set # CONFIG_UDF_FS is not set # CONFIG_UDF_RW is not set # CONFIG_UFS_FS is not set # CONFIG_UFS_FS_WRITE is not set # # Network File Systems # # CONFIG_CODA_FS is not set # CONFIG_INTERMEZZO_FS is not set CONFIG_NFS_FS=m CONFIG_NFS_V3=y # CONFIG_ROOT_NFS is not set CONFIG_NFSD=m CONFIG_NFSD_V3=y CONFIG_SUNRPC=m CONFIG_LOCKD=m CONFIG_LOCKD_V4=y # CONFIG_SMB_FS is not set # CONFIG_NCP_FS is not set # CONFIG_NCPFS_PACKET_SIGNING is not set # CONFIG_NCPFS_IOCTL_LOCKING is not set # CONFIG_NCPFS_STRONG is not set # CONFIG_NCPFS_NFS_NS is not set # CONFIG_NCPFS_OS2_NS is not set # CONFIG_NCPFS_SMALLDOS is not set # CONFIG_NCPFS_NLS is not set # CONFIG_NCPFS_EXTRAS is not set CONFIG_ZISOFS_FS=m CONFIG_ZLIB_FS_INFLATE=m # # Partition Types # CONFIG_PARTITION_ADVANCED=y # CONFIG_ACORN_PARTITION is not set # CONFIG_OSF_PARTITION is not set # CONFIG_AMIGA_PARTITION is not set # CONFIG_ATARI_PARTITION is not set # CONFIG_MAC_PARTITION is not set CONFIG_MSDOS_PARTITION=y # CONFIG_BSD_DISKLABEL is not set # CONFIG_MINIX_SUBPARTITION is not set # CONFIG_SOLARIS_X86_PARTITION is not set # CONFIG_UNIXWARE_DISKLABEL is not set # CONFIG_LDM_PARTITION is not set CONFIG_SGI_PARTITION=y # CONFIG_ULTRIX_PARTITION is not set # CONFIG_SUN_PARTITION is not set # CONFIG_SMB_NLS is not set CONFIG_NLS=y # # Native Language Support # CONFIG_NLS_DEFAULT="iso8859-1" # CONFIG_NLS_CODEPAGE_437 is not set # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set # CONFIG_NLS_CODEPAGE_850 is not set # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set # CONFIG_NLS_ISO8859_1 is not set # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set # CONFIG_NLS_ISO8859_15 is not set # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set # CONFIG_NLS_UTF8 is not set # # Console drivers # # CONFIG_VGA_CONSOLE is not set # CONFIG_MDA_CONSOLE is not set # # Frame-buffer support # # CONFIG_FB is not set # # Sound # CONFIG_SOUND=m # CONFIG_SOUND_BT878 is not set # CONFIG_SOUND_CMPCI is not set # CONFIG_SOUND_EMU10K1 is not set # CONFIG_MIDI_EMU10K1 is not set # CONFIG_SOUND_FUSION is not set # CONFIG_SOUND_CS4281 is not set # CONFIG_SOUND_ES1370 is not set # CONFIG_SOUND_ES1371 is not set # CONFIG_SOUND_ESSSOLO1 is not set # CONFIG_SOUND_MAESTRO is not set # CONFIG_SOUND_MAESTRO3 is not set # CONFIG_SOUND_ICH is not set # CONFIG_SOUND_RME96XX is not set # CONFIG_SOUND_SONICVIBES is not set CONFIG_SOUND_HAL2=m # CONFIG_SOUND_TRIDENT is not set # CONFIG_SOUND_MSNDCLAS is not set # CONFIG_SOUND_MSNDPIN is not set # CONFIG_SOUND_VIA82CXXX is not set # CONFIG_MIDI_VIA82CXXX is not set # CONFIG_SOUND_OSS is not set # CONFIG_SOUND_TVMIXER is not set # # SGI devices # CONFIG_SGI_SERIAL=y CONFIG_SERIAL_CONSOLE=y CONFIG_SGI_DS1286=y # CONFIG_SGI_NEWPORT_GFX is not set # # USB support # # CONFIG_USB is not set # # USB Controllers # # CONFIG_USB_UHCI is not set # CONFIG_USB_UHCI_ALT is not set # CONFIG_USB_OHCI is not set # # USB Device Class drivers # # CONFIG_USB_AUDIO is not set # CONFIG_USB_BLUETOOTH is not set # CONFIG_USB_STORAGE is not set # CONFIG_USB_STORAGE_DEBUG is not set # CONFIG_USB_STORAGE_DATAFAB is not set # CONFIG_USB_STORAGE_FREECOM is not set # CONFIG_USB_STORAGE_ISD200 is not set # CONFIG_USB_STORAGE_DPCM is not set # CONFIG_USB_STORAGE_HP8200e is not set # CONFIG_USB_STORAGE_SDDR09 is not set # CONFIG_USB_STORAGE_JUMPSHOT is not set # CONFIG_USB_ACM is not set # CONFIG_USB_PRINTER is not set # # USB Human Interface Devices (HID) # # # Input core support is needed for USB HID # # # USB Imaging devices # # CONFIG_USB_DC2XX is not set # CONFIG_USB_MDC800 is not set # CONFIG_USB_SCANNER is not set # CONFIG_USB_MICROTEK is not set # CONFIG_USB_HPUSBSCSI is not set # # USB Multimedia devices # # # Video4Linux support is needed for USB Multimedia device support # # # USB Network adaptors # # CONFIG_USB_PEGASUS is not set # CONFIG_USB_KAWETH is not set # CONFIG_USB_CATC is not set # CONFIG_USB_CDCETHER is not set # CONFIG_USB_USBNET is not set # # USB port drivers # # CONFIG_USB_USS720 is not set # # USB Serial Converter support # # CONFIG_USB_SERIAL is not set # CONFIG_USB_SERIAL_GENERIC is not set # CONFIG_USB_SERIAL_BELKIN is not set # CONFIG_USB_SERIAL_WHITEHEAT is not set # CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set # CONFIG_USB_SERIAL_EMPEG is not set # CONFIG_USB_SERIAL_FTDI_SIO is not set # CONFIG_USB_SERIAL_VISOR is not set # CONFIG_USB_SERIAL_IPAQ is not set # CONFIG_USB_SERIAL_IR is not set # CONFIG_USB_SERIAL_EDGEPORT is not set # CONFIG_USB_SERIAL_KEYSPAN_PDA is not set # CONFIG_USB_SERIAL_KEYSPAN is not set # CONFIG_USB_SERIAL_KEYSPAN_USA28 is not set # CONFIG_USB_SERIAL_KEYSPAN_USA28X is not set # CONFIG_USB_SERIAL_KEYSPAN_USA28XA is not set # CONFIG_USB_SERIAL_KEYSPAN_USA28XB is not set # CONFIG_USB_SERIAL_KEYSPAN_USA19 is not set # CONFIG_USB_SERIAL_KEYSPAN_USA18X is not set # CONFIG_USB_SERIAL_KEYSPAN_USA19W is not set # CONFIG_USB_SERIAL_KEYSPAN_USA49W is not set # CONFIG_USB_SERIAL_MCT_U232 is not set # CONFIG_USB_SERIAL_KLSI is not set # CONFIG_USB_SERIAL_PL2303 is not set # CONFIG_USB_SERIAL_CYBERJACK is not set # CONFIG_USB_SERIAL_XIRCOM is not set # CONFIG_USB_SERIAL_OMNINET is not set # # USB Miscellaneous drivers # # CONFIG_USB_RIO500 is not set # # Input core support # # CONFIG_INPUT is not set # CONFIG_INPUT_KEYBDEV is not set # CONFIG_INPUT_MOUSEDEV is not set # CONFIG_INPUT_JOYDEV is not set # CONFIG_INPUT_EVDEV is not set # # Kernel hacking # # CONFIG_CROSSCOMPILE is not set # CONFIG_DEBUG is not set CONFIG_MAGIC_SYSRQ=y # CONFIG_MIPS_UNCACHED is not set --envbJBWh7q8WU6mo-- From owner-devfs@oss.sgi.com Fri Mar 29 05:36:28 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2TDaSJ16089 for devfs-outgoing; Fri, 29 Mar 2002 05:36:28 -0800 Received: from tsv.sws.net.au (tsv.sws.net.au [203.36.46.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2TDaPq16086; Fri, 29 Mar 2002 05:36:25 -0800 Received: from lyta.coker.com.au (localhost [127.0.0.1]) by tsv.sws.net.au (Postfix) with ESMTP id B187B92452; Sat, 30 Mar 2002 00:38:45 +1100 (EST) Received: from there (lyta [127.0.0.1]) by lyta.coker.com.au (Postfix) with SMTP id 377B1237BB; Fri, 29 Mar 2002 14:38:36 +0100 (CET) Content-Type: text/plain; charset="iso-8859-1" From: Russell Coker Reply-To: Russell Coker To: raoul@shuttle.de (Raoul Borenius), Borsenkow Andrej Subject: Re: broken devfs-support in SGI Zilog8530 serial driver Date: Fri, 29 Mar 2002 14:38:35 +0100 X-Mailer: KMail [version 1.3.2] Cc: "'Raoul Borenius'" , linux-mips@oss.sgi.com, devfs@oss.sgi.com References: <20020329103244.GA15765@bunny.shuttle.de> <000001c1d711$2492f070$1fc1f2a3@mow.siemens.ru> <20020329132650.GA16905@bunny.shuttle.de> In-Reply-To: <20020329132650.GA16905@bunny.shuttle.de> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020329133836.377B1237BB@lyta.coker.com.au> Sender: owner-devfs@oss.sgi.com Precedence: bulk You need some code similar to the following in the serial driver: #ifdef CONFIG_DEVFS_FS serial_driver.name = "tts/%d"; #else serial_driver.name = "ttyS"; #endif Of course if the original device nodes were named /dev/ttyZ0 etc then you want "tts/Z%d". Look at the Cyclades and Stallion drivers for examples of it being done correctly. Or tell me exactly the details of what you want and I'll send you a patch. -- If you send email to me or to a mailing list that I use which has >4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. From owner-devfs@oss.sgi.com Fri Mar 29 23:36:43 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2U7ahK08205 for devfs-outgoing; Fri, 29 Mar 2002 23:36:43 -0800 Received: from dea.linux-mips.net (localhost [127.0.0.1]) by oss.sgi.com (8.11.2/8.11.3) with ESMTP id g2U7acv08202; Fri, 29 Mar 2002 23:36:38 -0800 Received: (from ralf@localhost) by dea.linux-mips.net (8.11.6/8.11.1) id g2U7Zx131264; Fri, 29 Mar 2002 23:35:59 -0800 Date: Fri, 29 Mar 2002 23:35:59 -0800 From: Ralf Baechle To: Raoul Borenius Cc: linux-mips@oss.sgi.com, devfs@oss.sgi.com Subject: Re: broken devfs-support in SGI Zilog8530 serial driver Message-ID: <20020329233559.A31160@dea.linux-mips.net> References: <20020329103244.GA15765@bunny.shuttle.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020329103244.GA15765@bunny.shuttle.de>; from raoul@shuttle.de on Fri, Mar 29, 2002 at 11:32:44AM +0100 X-Accept-Language: de,en,fr Sender: owner-devfs@oss.sgi.com Precedence: bulk On Fri, Mar 29, 2002 at 11:32:44AM +0100, Raoul Borenius wrote: > I'm not sure if this is a devfs or mips problem so I'm sending it > to both lists. > > I just compiled my own mips-kernel from oss.sgi.com:/cvs to get > devfs-support. Unfortunately there seems to be a problem with the > serial-driver at least in the linux_2_4 branch: > > SGI Zilog8530 serial driver version 1.00 > devfs_register(ttyS): could not append to parent, err: -17 > devfs_register(cua): could not append to parent, err: -17 At this time we don't even claim to have proper devfs support in the Indy serial drivers ... Ralf From owner-devfs@oss.sgi.com Sat Mar 30 05:29:56 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2UDTuC16142 for devfs-outgoing; Sat, 30 Mar 2002 05:29:56 -0800 Received: from bunny.shuttle.de (bunny.shuttle.de [193.174.247.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2UDTav16138; Sat, 30 Mar 2002 05:29:36 -0800 Received: by bunny.shuttle.de (Postfix, from userid 112) id 436994E567; Sat, 30 Mar 2002 14:28:56 +0100 (CET) Date: Sat, 30 Mar 2002 14:28:56 +0100 To: Ralf Baechle Cc: Raoul Borenius , linux-mips@oss.sgi.com, devfs@oss.sgi.com Subject: Re: broken devfs-support in SGI Zilog8530 serial driver Message-ID: <20020330132856.GA24305@bunny.shuttle.de> References: <20020329103244.GA15765@bunny.shuttle.de> <20020329233559.A31160@dea.linux-mips.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020329233559.A31160@dea.linux-mips.net> User-Agent: Mutt/1.3.28i From: raoul@shuttle.de (Raoul Borenius) Sender: owner-devfs@oss.sgi.com Precedence: bulk Hi Ralf, On Fri, Mar 29, 2002 at 11:35:59PM -0800, Ralf Baechle wrote: > On Fri, Mar 29, 2002 at 11:32:44AM +0100, Raoul Borenius wrote: > > > I'm not sure if this is a devfs or mips problem so I'm sending it > > to both lists. > > > > I just compiled my own mips-kernel from oss.sgi.com:/cvs to get > > devfs-support. Unfortunately there seems to be a problem with the > > serial-driver at least in the linux_2_4 branch: > > > > SGI Zilog8530 serial driver version 1.00 > > devfs_register(ttyS): could not append to parent, err: -17 > > devfs_register(cua): could not append to parent, err: -17 > > At this time we don't even claim to have proper devfs support in the > Indy serial drivers ... But it would be nice to have ;-) Especially because you only need the small change pointed out by Russell Coker: --- sgiserial.c.orig Sat Mar 30 10:51:03 2002 +++ sgiserial.c Sat Mar 30 10:54:28 2002 @@ -1875,7 +1875,11 @@ memset(&serial_driver, 0, sizeof(struct tty_driver)); serial_driver.magic = TTY_DRIVER_MAGIC; +#ifdef CONFIG_DEVFS_FS + serial_driver.name = "tts/%d"; +#else serial_driver.name = "ttyS"; +#endif serial_driver.major = TTY_MAJOR; serial_driver.minor_start = 64; serial_driver.num = NUM_CHANNELS; @@ -1911,7 +1915,11 @@ * major number and the subtype code. */ callout_driver = serial_driver; +#ifdef CONFIG_DEVFS_FS + callout_driver.name = "cua/%d"; +#else callout_driver.name = "cua"; +#endif callout_driver.major = TTYAUX_MAJOR; callout_driver.subtype = SERIAL_TYPE_CALLOUT; It works for my Indy and I just love devfs. All other drivers used on my box also work fine with devfs (sound, watchdog, rtc etc.). Regards Raoul From owner-devfs@oss.sgi.com Sat Mar 30 11:18:12 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2UJICd18635 for devfs-outgoing; Sat, 30 Mar 2002 11:18:12 -0800 Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2UJI9v18632 for ; Sat, 30 Mar 2002 11:18:09 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id g2UJHAp07198; Sat, 30 Mar 2002 12:17:10 -0700 Date: Sat, 30 Mar 2002 12:17:10 -0700 Message-Id: <200203301917.g2UJHAp07198@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: linux-kernel@vger.kernel.org, devfs-announce-list@vindaloo.ras.ucalgary.ca Subject: [PATCH] devfs v199.11 available Sender: owner-devfs@oss.sgi.com Precedence: bulk Hi, all. Version 199.11 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-pre5. Highlights of this release: - Ported to kernel 2.4.19-pre5 - Updated README from master HTML file Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Sun Mar 31 07:01:13 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2VF1DU03254 for devfs-outgoing; Sun, 31 Mar 2002 07:01:13 -0800 Received: from bunny.shuttle.de (bunny.shuttle.de [193.174.247.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2VF14v03238; Sun, 31 Mar 2002 07:01:04 -0800 Received: by bunny.shuttle.de (Postfix, from userid 112) id B90384E567; Sun, 31 Mar 2002 17:00:23 +0200 (CEST) Date: Sun, 31 Mar 2002 17:00:23 +0200 To: Ralf Baechle Cc: linux-mips@oss.sgi.com, devfs@oss.sgi.com Subject: Re: broken devfs-support in SGI Zilog8530 serial driver Message-ID: <20020331150023.GA30224@bunny.shuttle.de> References: <20020329103244.GA15765@bunny.shuttle.de> <20020329233559.A31160@dea.linux-mips.net> <20020330132856.GA24305@bunny.shuttle.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020330132856.GA24305@bunny.shuttle.de> User-Agent: Mutt/1.3.28i From: raoul@shuttle.de (Raoul Borenius) Sender: owner-devfs@oss.sgi.com Precedence: bulk Hi Ralf, On Sat, Mar 30, 2002 at 02:28:56PM +0100, raoul wrote: > Especially because you only need the small change pointed out by > Russell Coker: > > --- sgiserial.c.orig Sat Mar 30 10:51:03 2002 > +++ sgiserial.c Sat Mar 30 10:54:28 2002 > @@ -1875,7 +1875,11 @@ > > memset(&serial_driver, 0, sizeof(struct tty_driver)); > serial_driver.magic = TTY_DRIVER_MAGIC; > +#ifdef CONFIG_DEVFS_FS > + serial_driver.name = "tts/%d"; > +#else > serial_driver.name = "ttyS"; > +#endif > serial_driver.major = TTY_MAJOR; > serial_driver.minor_start = 64; > serial_driver.num = NUM_CHANNELS; Thanks for including the changes fr the ttyS's. But it seems you forgot the callout-devices: > @@ -1911,7 +1915,11 @@ > * major number and the subtype code. > */ > callout_driver = serial_driver; > +#ifdef CONFIG_DEVFS_FS > + callout_driver.name = "cua/%d"; > +#else > callout_driver.name = "cua"; > +#endif > callout_driver.major = TTYAUX_MAJOR; > callout_driver.subtype = SERIAL_TYPE_CALLOUT; > Could you commit that too? Thanx Raoul From owner-devfs@oss.sgi.com Sun Mar 31 13:54:56 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2VLsuG11895 for devfs-outgoing; Sun, 31 Mar 2002 13:54:56 -0800 Received: from mailhost.uni-koblenz.de (root@mailhost.uni-koblenz.de [141.26.64.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2VLsqv11891; Sun, 31 Mar 2002 13:54:52 -0800 Received: from eddie (eddie.uni-koblenz.de [141.26.64.59]) by mailhost.uni-koblenz.de (8.11.6/8.11.6/SuSE Linux 0.5) with SMTP id g2VLsBt03917; Sun, 31 Mar 2002 23:54:11 +0200 Received: from dea.linux-mips.net by eddie (SMI-8.6/KO-2.0) id XAA20174; Sun, 31 Mar 2002 23:54:10 +0200 Received: (from ralf@localhost) by dea.linux-mips.net (8.11.6/8.11.1) id g2UKIBt02122; Sat, 30 Mar 2002 12:18:11 -0800 Date: Sat, 30 Mar 2002 12:18:11 -0800 From: Ralf Baechle To: Raoul Borenius Cc: linux-mips@oss.sgi.com, devfs@oss.sgi.com Subject: Re: broken devfs-support in SGI Zilog8530 serial driver Message-ID: <20020330121811.A2049@dea.linux-mips.net> References: <20020329103244.GA15765@bunny.shuttle.de> <20020329233559.A31160@dea.linux-mips.net> <20020330132856.GA24305@bunny.shuttle.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020330132856.GA24305@bunny.shuttle.de>; from raoul@shuttle.de on Sat, Mar 30, 2002 at 02:28:56PM +0100 X-Accept-Language: de,en,fr X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) Sender: owner-devfs@oss.sgi.com Precedence: bulk On Sat, Mar 30, 2002 at 02:28:56PM +0100, Raoul Borenius wrote: > > > I just compiled my own mips-kernel from oss.sgi.com:/cvs to get > > > devfs-support. Unfortunately there seems to be a problem with the > > > serial-driver at least in the linux_2_4 branch: > > > > > > SGI Zilog8530 serial driver version 1.00 > > > devfs_register(ttyS): could not append to parent, err: -17 > > > devfs_register(cua): could not append to parent, err: -17 > > > > At this time we don't even claim to have proper devfs support in the > > Indy serial drivers ... > > But it would be nice to have ;-) > > Especially because you only need the small change pointed out by > Russell Coker: Ok :-) Applied to 2.4 and 2.5. Ralf From owner-devfs@oss.sgi.com Sun Mar 31 14:16:34 2002 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g2VMGYf14748 for devfs-outgoing; Sun, 31 Mar 2002 14:16:34 -0800 Received: from mailhost.uni-koblenz.de (root@mailhost.uni-koblenz.de [141.26.64.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g2VMGUv14743; Sun, 31 Mar 2002 14:16:30 -0800 Received: from eddie (eddie.uni-koblenz.de [141.26.64.59]) by mailhost.uni-koblenz.de (8.11.6/8.11.6/SuSE Linux 0.5) with SMTP id g2VMFnt05948; Mon, 1 Apr 2002 00:15:49 +0200 Received: from dea.linux-mips.net by eddie (SMI-8.6/KO-2.0) id AAA20250; Mon, 1 Apr 2002 00:15:48 +0200 Received: (from ralf@localhost) by dea.linux-mips.net (8.11.6/8.11.1) id g2VMFkK12765; Sun, 31 Mar 2002 14:15:46 -0800 Date: Sun, 31 Mar 2002 14:15:45 -0800 From: Ralf Baechle To: Raoul Borenius Cc: linux-mips@oss.sgi.com, devfs@oss.sgi.com Subject: Re: broken devfs-support in SGI Zilog8530 serial driver Message-ID: <20020331141545.A12756@dea.linux-mips.net> References: <20020329103244.GA15765@bunny.shuttle.de> <20020329233559.A31160@dea.linux-mips.net> <20020330132856.GA24305@bunny.shuttle.de> <20020331150023.GA30224@bunny.shuttle.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020331150023.GA30224@bunny.shuttle.de>; from raoul@shuttle.de on Sun, Mar 31, 2002 at 05:00:23PM +0200 X-Accept-Language: de,en,fr X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) Sender: owner-devfs@oss.sgi.com Precedence: bulk On Sun, Mar 31, 2002 at 05:00:23PM +0200, Raoul Borenius wrote: > Thanks for including the changes fr the ttyS's. But it seems you forgot the > callout-devices: That's what you get for submitting patches that don't apply ;) Did you do cut'n'paste or similiar cruelties to that poor little patch? > > @@ -1911,7 +1915,11 @@ > > * major number and the subtype code. > > */ > > callout_driver = serial_driver; > > +#ifdef CONFIG_DEVFS_FS > > + callout_driver.name = "cua/%d"; > > +#else > > callout_driver.name = "cua"; > > +#endif > > callout_driver.major = TTYAUX_MAJOR; > > callout_driver.subtype = SERIAL_TYPE_CALLOUT; > > > > Could you commit that too? Sure. Ralf