From owner-devfs@oss.sgi.com Thu Feb 1 13:06:56 2001 Received: by oss.sgi.com id ; Thu, 1 Feb 2001 13:06:35 -0800 Received: from msgbas1tx.cos.agilent.com ([192.6.9.34]:48341 "HELO msgbas1t.cos.agilent.com") by oss.sgi.com with SMTP id ; Thu, 1 Feb 2001 13:06:33 -0800 Received: from msgrel1.cos.agilent.com (msgrel1.cos.agilent.com [130.29.152.77]) by msgbas1t.cos.agilent.com (Postfix) with ESMTP id 79C701FC for ; Thu, 1 Feb 2001 14:06:32 -0700 (MST) Received: from axcsbh4.cos.agilent.com (axcsbh4.cos.agilent.com [130.29.152.145]) by msgrel1.cos.agilent.com (Postfix) with SMTP id 17A34D9 for ; Thu, 1 Feb 2001 14:06:32 -0700 (MST) Received: from 130.29.152.145 by axcsbh4.cos.agilent.com (InterScan E-Mail VirusWall NT); Thu, 01 Feb 2001 14:06:30 -0700 (Mountain Standard Time) Received: by axcsbh4.cos.agilent.com with Internet Mail Service (5.5.2653.19) id ; Thu, 1 Feb 2001 14:06:28 -0700 Message-ID: From: hiren_mehta@agilent.com To: devfs@oss.sgi.com Subject: Date: Thu, 1 Feb 2001 14:06:22 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Hi All, I applied the devfs patch to the kernel 2.2.16-22 (RedHat Linux 7) installed the new kernel, modified lilo.conf, ran lilo and rebooted the system with the option "devfs=nomount". The system is able to mount the root file system in readonly mode. But after that when it tries to do fsck to the root file system before mounting it in "rw" mode, it fails. Looks like devfs seems to be having a problem with my /etc/fstab. My /etc/fstab has device names specified in the "LABEL=.." format. Does devfs understand LABEL=.. format ? or I need to change the device names to something like /dev/sdd.. ? Any help is appreciated. -hiren From owner-devfs@oss.sgi.com Thu Feb 1 18:06:27 2001 Received: by oss.sgi.com id ; Thu, 1 Feb 2001 18:06:08 -0800 Received: from [200.222.195.81] ([200.222.195.81]:54658 "EHLO pervalidus.dyndns.org") by oss.sgi.com with ESMTP id ; Thu, 1 Feb 2001 18:05:52 -0800 Received: from pervalidus by pervalidus.dyndns.org with local (Exim 3.22 #1) id 14OVbL-0000GR-00 for devfs@oss.sgi.com; Fri, 02 Feb 2001 00:05:27 -0200 Date: Fri, 2 Feb 2001 00:05:27 -0200 From: =?iso-8859-1?B?RnLpZOlyaWMgTC4gVy4=?= Meunier <0@pervalidus.net> To: devfs@oss.sgi.com Subject: /etc/securetty problem Message-ID: <20010202000527.I160@pervalidus.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.3.14i X-Mailer: Mutt/1.3.14i - Linux 2.4.1 Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Hi. For the first time I installed devfs (Kernel 2.4.1). It's working without any major problems, but I can't log as root on any console if I change /etc/securetty to use vc/1 (I also tried with 1) instead of tty1. What I actually want is to change all system archives to at least boot without devfsd. /etc/rc.d/rc.local: gpm -m /dev/tts/0 -t ms /etc/fstab: /dev/ide/host0/bus0/target0/lun0/part2 swap swap defaults 0 0 /dev/ide/host0/bus0/target0/lun0/part1 / ext2 defaults 1 1 /dev/ide/host0/bus0/target0/lun0/part3 /usr/local/src ext2 defaults 1 2 /dev/ide/host0/bus0/target0/lun0/part4 /home/ftp/pub ext2 defaults 1 2 /etc/inittab: c1:1235:respawn:/sbin/agetty 38400 vc/1 linux c2:1235:respawn:/sbin/agetty 38400 vc/2 linux c3:1235:respawn:/sbin/agetty 38400 vc/3 linux c4:12345:respawn:/sbin/agetty 38400 vc/4 linux I also changed /etc/wvdial.conf and /etc/ppp/options to use tts/1. Any other changes? Note that I use util-linux 2.10s, but without PAM (Slackware), so login isn't built and I use the one from shadow-20000902. -- Frédéric L. W. Meunier - http://www.pervalidus.net/ 0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR) From owner-devfs@oss.sgi.com Sat Feb 3 00:22:05 2001 Received: by oss.sgi.com id ; Sat, 3 Feb 2001 00:21:55 -0800 Received: from h-207-228-73-44.gen.cadvision.com ([207.228.73.44]:18948 "EHLO mobilix.ras.ucalgary.ca") by oss.sgi.com with ESMTP id ; Sat, 3 Feb 2001 00:21:52 -0800 Received: (from rgooch@localhost) by mobilix.ras.ucalgary.ca (8.10.0/8.10.0) id f138Lah02314; Sat, 3 Feb 2001 01:21:36 -0700 Date: Sat, 3 Feb 2001 01:21:36 -0700 Message-Id: <200102030821.f138Lah02314@mobilix.ras.ucalgary.ca> From: Richard Gooch To: linux-kernel@vger.kernel.org, devfs-announce-list@mobilix.ras.ucalgary.ca Subject: [PATCH] devfs v99.19 available Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Hi, all. Version 99.19 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.2/devfs-patch-current.gz AND: ftp://ftp.atnf.csiro.au/pub/people/rgooch/linux/kernel-patches/v2.2/devfs-patch-current.gz NOTE: the devfs-patch-v99.x patches are maintenance patches for the 2.2.x production kernels. Devfs development is done against recent development kernels. Occasionally, the latest devfs patch for the development kernels may be backported to 2.2.x series, but this happens rarely. This is against 2.2.18. Highlights of this release: - Ported devfs-patch-v99.18 to kernel 2.2.18 - 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 Feb 4 22:32:33 2001 Received: by oss.sgi.com id ; Sun, 4 Feb 2001 22:32:23 -0800 Received: from vindaloo.ras.ucalgary.ca ([136.159.55.21]:43414 "EHLO vindaloo.ras.ucalgary.ca") by oss.sgi.com with ESMTP id ; Sun, 4 Feb 2001 22:32:13 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id f156Vje04234; Sun, 4 Feb 2001 23:31:45 -0700 Date: Sun, 4 Feb 2001 23:31:45 -0700 Message-Id: <200102050631.f156Vje04234@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: drepper@cygnus.com (Ulrich Drepper) Cc: Pierre Rousselet , David Ford , devfs@oss.sgi.com, LKML Subject: Re: [PATCH] devfsd, compiling on glibc22x In-Reply-To: References: <3A7383B2.19DDD006@linux.com> <3A73C1D8.578AEEE@wanadoo.fr> Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Ulrich Drepper writes: > Pierre Rousselet writes: > > > for me : > > make CFLAGS='-O2 -I. -D_GNU_SOURCE' > > compiles without any patch. is it correct ? > > Yes. RTLD_NEXT is not in any standard, it's an extension available > via -D_GNU_SOURCE. So why do old binaries (compiled with glibc 2.1.3) segfault when they call dlsym() with RTLD_NEXT? Even newly compiled binaries (with glibc 2.2) still segfault. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Sun Feb 4 22:52:52 2001 Received: by oss.sgi.com id ; Sun, 4 Feb 2001 22:52:33 -0800 Received: from runyon.cygnus.com ([205.180.230.5]:7665 "EHLO cygnus.com") by oss.sgi.com with ESMTP id ; Sun, 4 Feb 2001 22:52:07 -0800 Received: from otr.mynet (dialin-sv-02.cygnus.com [205.180.231.52]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id WAA27342; Sun, 4 Feb 2001 22:51:54 -0800 (PST) Received: by otr.mynet (Postfix, from userid 500) id BC79D30BD; Sun, 4 Feb 2001 22:51:41 -0800 (PST) To: Richard Gooch Cc: Pierre Rousselet , David Ford , devfs@oss.sgi.com, LKML Subject: Re: [PATCH] devfsd, compiling on glibc22x References: <3A7383B2.19DDD006@linux.com> <3A73C1D8.578AEEE@wanadoo.fr> <200102050631.f156Vje04234@vindaloo.ras.ucalgary.ca> Reply-To: drepper@cygnus.com (Ulrich Drepper) X-fingerprint: BE 3B 21 04 BC 77 AC F0 61 92 E4 CB AC DD B9 5A From: Ulrich Drepper Date: 04 Feb 2001 22:51:41 -0800 In-Reply-To: Richard Gooch's message of "Sun, 4 Feb 2001 23:31:45 -0700" Message-ID: Lines: 12 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Capitol Reef) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Richard Gooch writes: > So why do old binaries (compiled with glibc 2.1.3) segfault when they > call dlsym() with RTLD_NEXT? Even newly compiled binaries (with glibc > 2.2) still segfault. What do you ask me? You wrote the code. -- ---------------. ,-. 1325 Chesapeake Terrace Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com `------------------------ From owner-devfs@oss.sgi.com Sun Feb 4 23:02:03 2001 Received: by oss.sgi.com id ; Sun, 4 Feb 2001 23:01:53 -0800 Received: from vindaloo.ras.ucalgary.ca ([136.159.55.21]:48534 "EHLO vindaloo.ras.ucalgary.ca") by oss.sgi.com with ESMTP id ; Sun, 4 Feb 2001 23:01:39 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id f1571TH04804; Mon, 5 Feb 2001 00:01:29 -0700 Date: Mon, 5 Feb 2001 00:01:29 -0700 Message-Id: <200102050701.f1571TH04804@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: drepper@cygnus.com (Ulrich Drepper) Cc: Pierre Rousselet , David Ford , devfs@oss.sgi.com, LKML Subject: Re: [PATCH] devfsd, compiling on glibc22x In-Reply-To: References: <3A7383B2.19DDD006@linux.com> <3A73C1D8.578AEEE@wanadoo.fr> <200102050631.f156Vje04234@vindaloo.ras.ucalgary.ca> Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Ulrich Drepper writes: > Richard Gooch writes: > > > So why do old binaries (compiled with glibc 2.1.3) segfault when they > > call dlsym() with RTLD_NEXT? Even newly compiled binaries (with glibc > > 2.2) still segfault. > > What do you ask me? You wrote the code. But you wrote dlsym(), right I have a debug trace from someone which shows that the call to dlsym() segfaults. It's being called thusly: dlsym (RTLD_NEXT, "symlink"); This doesn't fail with libc 5 nor with glibc 2.1.3. But it does with glibc 2.2. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Mon Feb 5 04:43:13 2001 Received: by oss.sgi.com id ; Mon, 5 Feb 2001 04:43:04 -0800 Received: from harpo.it.uu.se ([130.238.12.34]:7403 "EHLO harpo.it.uu.se") by oss.sgi.com with ESMTP id ; Mon, 5 Feb 2001 04:42:51 -0800 Received: (from mikpe@localhost) by harpo.it.uu.se (8.8.5/8.8.5) id NAA13138; Mon, 5 Feb 2001 13:42:38 +0100 (MET) Date: Mon, 5 Feb 2001 13:42:38 +0100 (MET) From: Mikael Pettersson Message-Id: <200102051242.NAA13138@harpo.it.uu.se> To: drepper@cygnus.com, rgooch@ras.ucalgary.ca Subject: Re: [PATCH] devfsd, compiling on glibc22x Cc: david@linux.com, devfs@oss.sgi.com, pierre.rousselet@wanadoo.fr Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Ulrich Drepper wrote: >Richard Gooch writes: > >> So why do old binaries (compiled with glibc 2.1.3) segfault when they >> call dlsym() with RTLD_NEXT? Even newly compiled binaries (with glibc >> 2.2) still segfault. > >What do you ask me? You wrote the code. Richard is correct -- RTLD_NEXT seems to have been mutilated beyond recognition in glibc-2.2. Observe: > Script started on Mon Feb 5 13:19:19 2001 > stout_1_cat bug.c > #define _GNU_SOURCE /* wtf?! RTLD_NEXT is undefined otherwise */ > #include > int main(void) { dlsym(RTLD_NEXT, "sigaction"); return 0; } Nothing fancy here. > stout_2_gcc bug.c -ldl > stout_3_./a.out > Segmentation fault (core dumped) Oh dear. > stout_4_echo where | gdb a.out core > GNU gdb 5.0 > Copyright 2000 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-redhat-linux"... > Core was generated by `./a.out'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /lib/libdl.so.2...done. > Loaded symbols for /lib/libdl.so.2 > Reading symbols from /lib/libc.so.6...done. > Loaded symbols for /lib/libc.so.6 > Reading symbols from /lib/ld-linux.so.2...done. > Loaded symbols for /lib/ld-linux.so.2 > #0 0x4000dc38 in _dl_signal_error (errcode=0, objname=0x0, > errstring=0x4013ef00 "RTLD_NEXT used in code not dynamically loaded") > at dl-error.c:79 > 79 dl-error.c: No such file or directory. > (gdb) Hangup detected on fd 0 > error detected on stdin Note the errstring. "RTLD_NEXT used in code not dynamically loaded". WTF is this? I have successfully used RTLD_NEXT from the main app for several years, as I know many others have too. Solaris & Linux. If RTLD_NEXT is now limited to be called only from within .so objects, then that's a major step in the wrong direction. > stout_5_rpm -q glibc > glibc-2.2-12 >From the RH7.0 updates directory. /Mikael (. not cc:d to lkml .) From owner-devfs@oss.sgi.com Mon Feb 5 08:27:54 2001 Received: by oss.sgi.com id ; Mon, 5 Feb 2001 08:27:45 -0800 Received: from runyon.cygnus.com ([205.180.230.5]:6909 "EHLO cygnus.com") by oss.sgi.com with ESMTP id ; Mon, 5 Feb 2001 08:27:30 -0800 Received: from otr.mynet (dialin-sv-02.cygnus.com [205.180.231.52]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id IAA22712; Mon, 5 Feb 2001 08:23:56 -0800 (PST) Received: by otr.mynet (Postfix, from userid 500) id DF43930BD; Mon, 5 Feb 2001 08:23:39 -0800 (PST) To: Mikael Pettersson Cc: rgooch@ras.ucalgary.ca, david@linux.com, devfs@oss.sgi.com, pierre.rousselet@wanadoo.fr Subject: Re: [PATCH] devfsd, compiling on glibc22x References: <200102051242.NAA13138@harpo.it.uu.se> Reply-To: drepper@cygnus.com (Ulrich Drepper) X-fingerprint: BE 3B 21 04 BC 77 AC F0 61 92 E4 CB AC DD B9 5A From: Ulrich Drepper Date: 05 Feb 2001 08:23:39 -0800 In-Reply-To: Mikael Pettersson's message of "Mon, 5 Feb 2001 13:42:38 +0100 (MET)" Message-ID: Lines: 22 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Capitol Reef) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Mikael Pettersson writes: > Richard is correct -- RTLD_NEXT seems to have been mutilated > beyond recognition in glibc-2.2. > > Observe: > > > Script started on Mon Feb 5 13:19:19 2001 > > stout_1_cat bug.c > > #define _GNU_SOURCE /* wtf?! RTLD_NEXT is undefined otherwise */ > > #include > > int main(void) { dlsym(RTLD_NEXT, "sigaction"); return 0; } > > Nothing fancy here. Dammit, no. You people simply cannot program. This code is broken. If it worked before this is only by accident. -- ---------------. ,-. 1325 Chesapeake Terrace Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com `------------------------ From owner-devfs@oss.sgi.com Mon Feb 5 17:43:48 2001 Received: by oss.sgi.com id ; Mon, 5 Feb 2001 17:43:28 -0800 Received: from vindaloo.ras.ucalgary.ca ([136.159.55.21]:33408 "EHLO vindaloo.ras.ucalgary.ca") by oss.sgi.com with ESMTP id ; Mon, 5 Feb 2001 17:43:13 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id f161gw701607; Mon, 5 Feb 2001 18:42:58 -0700 Date: Mon, 5 Feb 2001 18:42:58 -0700 Message-Id: <200102060142.f161gw701607@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: drepper@cygnus.com (Ulrich Drepper) Cc: Mikael Pettersson , david@linux.com, devfs@oss.sgi.com, pierre.rousselet@wanadoo.fr Subject: Re: [PATCH] devfsd, compiling on glibc22x In-Reply-To: References: <200102051242.NAA13138@harpo.it.uu.se> Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Ulrich Drepper writes: > Mikael Pettersson writes: > > > Richard is correct -- RTLD_NEXT seems to have been mutilated > > beyond recognition in glibc-2.2. > > > > Observe: > > > > > Script started on Mon Feb 5 13:19:19 2001 > > > stout_1_cat bug.c > > > #define _GNU_SOURCE /* wtf?! RTLD_NEXT is undefined otherwise */ > > > #include > > > int main(void) { dlsym(RTLD_NEXT, "sigaction"); return 0; } > > > > Nothing fancy here. > > Dammit, no. You people simply cannot program. This code is broken. > If it worked before this is only by accident. No need to be rude! I can code just fine, thank you. The problem lies in the (lack of) documentation. The man page for dlsym() says nothing, and /usr/include/dlfcn.h isn't sufficiently explicit. Adding a single sentence: Use of RTLD_NEXT from outside a shared library context will result in undefined behaviour would help. Reading the Solaris 2.6 man page, I don't see a similar warning. So, according to the sources available to me, RTLD_NEXT is fine. Furthermore, under libc 5 there *is no* RTLD_DEFAULT, so it's hardly surprising that RTLD_NEXT is what people have been using. Does glibc still claim to be binary compatible with libc 5? If so, what will happen to a libc 5 compiled programme which can only use RTLD_NEXT? Do you have special casing to prevent breakage in that case? Finally, why don't you have error checking in your library? If the usage is in fact wrong, isn't is cleaner to return NULL from dlsym(), rather than having it segfault? Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Mon Feb 5 18:00:19 2001 Received: by oss.sgi.com id ; Mon, 5 Feb 2001 17:59:58 -0800 Received: from runyon.cygnus.com ([205.180.230.5]:11157 "EHLO cygnus.com") by oss.sgi.com with ESMTP id ; Mon, 5 Feb 2001 17:59:57 -0800 Received: from otr.mynet (dialin-sv-02.cygnus.com [205.180.231.52]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id RAA22906; Mon, 5 Feb 2001 17:56:20 -0800 (PST) Received: by otr.mynet (Postfix, from userid 500) id B6F1430BD; Mon, 5 Feb 2001 17:56:03 -0800 (PST) To: Richard Gooch Cc: Mikael Pettersson , david@linux.com, devfs@oss.sgi.com, pierre.rousselet@wanadoo.fr Subject: Re: [PATCH] devfsd, compiling on glibc22x References: <200102051242.NAA13138@harpo.it.uu.se> <200102060142.f161gw701607@vindaloo.ras.ucalgary.ca> Reply-To: drepper@cygnus.com (Ulrich Drepper) X-fingerprint: BE 3B 21 04 BC 77 AC F0 61 92 E4 CB AC DD B9 5A From: Ulrich Drepper Date: 05 Feb 2001 17:56:03 -0800 In-Reply-To: Richard Gooch's message of "Mon, 5 Feb 2001 18:42:58 -0700" Message-ID: Lines: 24 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Capitol Reef) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Richard Gooch writes: > The problem lies in the (lack of) documentation. Then why don't you write any if you want to see it? > Furthermore, under libc 5 there *is no* RTLD_DEFAULT, so it's hardly > surprising that RTLD_NEXT is what people have been using. Does glibc > still claim to be binary compatible with libc 5? What are you talking about? Glibc never was compatible with libc 5. > Finally, why don't you have error checking in your library? If the > usage is in fact wrong, isn't is cleaner to return NULL from dlsym(), > rather than having it segfault? You completely misunderstand the concept of a runtime library. It is assumed that programs are correct and have to be executed as fast as possible. There are no checks for programmer errors. -- ---------------. ,-. 1325 Chesapeake Terrace Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com `------------------------ From owner-devfs@oss.sgi.com Mon Feb 5 18:11:29 2001 Received: by oss.sgi.com id ; Mon, 5 Feb 2001 18:11:19 -0800 Received: from [136.159.55.21] ([136.159.55.21]:39552 "EHLO vindaloo.ras.ucalgary.ca") by oss.sgi.com with ESMTP id ; Mon, 5 Feb 2001 18:11:10 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id f1629cx07951; Mon, 5 Feb 2001 19:09:38 -0700 Date: Mon, 5 Feb 2001 19:09:38 -0700 Message-Id: <200102060209.f1629cx07951@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: drepper@cygnus.com (Ulrich Drepper) Cc: Mikael Pettersson , david@linux.com, devfs@oss.sgi.com, pierre.rousselet@wanadoo.fr Subject: Re: [PATCH] devfsd, compiling on glibc22x In-Reply-To: References: <200102051242.NAA13138@harpo.it.uu.se> <200102060142.f161gw701607@vindaloo.ras.ucalgary.ca> Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Ulrich Drepper writes: > Richard Gooch writes: > > > The problem lies in the (lack of) documentation. > > Then why don't you write any if you want to see it? ??? The problem was in the lack of documentation when the code was written! Thus, your claim of people not being able to programme was unwarranted. And in my previous message I sent you a suggested line that could be added to /usr/include/dlfcn.h to clarify things. Hopefully that will be added. > > Furthermore, under libc 5 there *is no* RTLD_DEFAULT, so it's hardly > > surprising that RTLD_NEXT is what people have been using. Does glibc > > still claim to be binary compatible with libc 5? > > What are you talking about? Glibc never was compatible with libc 5. Really? I recall statements that libc 5-compiled programmes should be able to work with glibc. Perhaps I'm mistaken. I do recall that glibc 2.0 was supposed to be compatible with glibc 2.1, but I note that hasn't been the case (both source and binaries). > > Finally, why don't you have error checking in your library? If the > > usage is in fact wrong, isn't is cleaner to return NULL from dlsym(), > > rather than having it segfault? > > You completely misunderstand the concept of a runtime library. It > is assumed that programs are correct and have to be executed as fast > as possible. There are no checks for programmer errors. So when you changed the behaviour, you couldn't afford a simple if test? Compared to all the other work that's being done, it's a trivial amount of code. Sigh. You didn't actually break this intentionally, did you? Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Mon Feb 5 18:46:38 2001 Received: by oss.sgi.com id ; Mon, 5 Feb 2001 18:46:29 -0800 Received: from runyon.cygnus.com ([205.180.230.5]:49046 "EHLO cygnus.com") by oss.sgi.com with ESMTP id ; Mon, 5 Feb 2001 18:46:01 -0800 Received: from otr.mynet (dialin-sv-02.cygnus.com [205.180.231.52]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id SAA26861; Mon, 5 Feb 2001 18:42:32 -0800 (PST) Received: by otr.mynet (Postfix, from userid 500) id 7653430BD; Mon, 5 Feb 2001 18:42:16 -0800 (PST) To: Richard Gooch Cc: Mikael Pettersson , david@linux.com, devfs@oss.sgi.com, pierre.rousselet@wanadoo.fr Subject: Re: [PATCH] devfsd, compiling on glibc22x References: <200102051242.NAA13138@harpo.it.uu.se> <200102060142.f161gw701607@vindaloo.ras.ucalgary.ca> <200102060209.f1629cx07951@vindaloo.ras.ucalgary.ca> Reply-To: drepper@cygnus.com (Ulrich Drepper) X-fingerprint: BE 3B 21 04 BC 77 AC F0 61 92 E4 CB AC DD B9 5A From: Ulrich Drepper Date: 05 Feb 2001 18:42:16 -0800 In-Reply-To: Richard Gooch's message of "Mon, 5 Feb 2001 19:09:38 -0700" Message-ID: Lines: 20 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Capitol Reef) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Richard Gooch writes: > ??? The problem was in the lack of documentation when the code was > written! Thus, your claim of people not being able to programme was > unwarranted. Crap. If you want to use it you have to inform yourself. There is source code available which helps if there is no other documentation. If nobody has interest to write documentation this is the way to go. > And in my previous message I sent you a suggested line that could be > added to /usr/include/dlfcn.h to clarify things. Hopefully that will > be added. System headers are no documentation. -- ---------------. ,-. 1325 Chesapeake Terrace Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com `------------------------ From owner-devfs@oss.sgi.com Mon Feb 5 22:27:20 2001 Received: by oss.sgi.com id ; Mon, 5 Feb 2001 22:27:10 -0800 Received: from vindaloo.ras.ucalgary.ca ([136.159.55.21]:11904 "EHLO vindaloo.ras.ucalgary.ca") by oss.sgi.com with ESMTP id ; Mon, 5 Feb 2001 22:26:41 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id f166QGu02080; Mon, 5 Feb 2001 23:26:16 -0700 Date: Mon, 5 Feb 2001 23:26:16 -0700 Message-Id: <200102060626.f166QGu02080@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: linux-kernel@vger.rutgers.edu, devfs-announce-list@vindaloo.ras.ucalgary.ca Subject: devfsd-v1.3.11 available Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Hi, all. I've just released version 1.3.11 of my devfsd (devfs daemon) at: http://www.atnf.csiro.au/~rgooch/linux/ This works with devfs-patch-v130 and devfs-patch-v99.7 (or later). The main changes are: - Workaround changes in glibc 2.2 - Handle cases where fds [0:2] are closed already. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Mon Feb 5 22:31:20 2001 Received: by oss.sgi.com id ; Mon, 5 Feb 2001 22:31:01 -0800 Received: from vindaloo.ras.ucalgary.ca ([136.159.55.21]:14464 "EHLO vindaloo.ras.ucalgary.ca") by oss.sgi.com with ESMTP id ; Mon, 5 Feb 2001 22:30:52 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id f166UO002259; Mon, 5 Feb 2001 23:30:24 -0700 Date: Mon, 5 Feb 2001 23:30:24 -0700 Message-Id: <200102060630.f166UO002259@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: linux-kernel@vger.kernel.org, devfs-announce-list@vindaloo.ras.ucalgary.ca Subject: devfsd-v1.3.11 available Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Hi, all. I've just released version 1.3.11 of my devfsd (devfs daemon) at: http://www.atnf.csiro.au/~rgooch/linux/ This works with devfs-patch-v130 and devfs-patch-v99.7 (or later). The main changes are: - Workaround changes in glibc 2.2 - Handle cases where fds [0:2] are closed already. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Mon Feb 12 15:11:09 2001 Received: by oss.sgi.com id ; Mon, 12 Feb 2001 15:10:48 -0800 Received: from e31.co.us.ibm.com ([32.97.110.129]:35566 "EHLO e31.bld.us.ibm.com") by oss.sgi.com with ESMTP id ; Mon, 12 Feb 2001 15:10:23 -0800 Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.99.132.206]) by e31.bld.us.ibm.com (8.9.3/8.9.3) with ESMTP id SAA90144 for ; Mon, 12 Feb 2001 18:03:19 -0500 Received: from localhost.localdomain (w-mikeand.des.sequent.com [138.95.12.8]) by westrelay03.boulder.ibm.com (8.8.8m3/NCO v4.95) with ESMTP id QAA43458 for ; Mon, 12 Feb 2001 16:10:41 -0700 Received: (from mikeand@localhost) by localhost.localdomain (8.9.3/8.9.3) id PAA31975 for devfs@oss.sgi.com; Mon, 12 Feb 2001 15:09:52 -0800 Date: Mon, 12 Feb 2001 15:09:52 -0800 From: Mike Anderson To: devfs@oss.sgi.com Subject: Question on device VPD and devfs Message-ID: <20010212150952.A31389@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-Operating-System: Linux 2.0.32 on an i486 Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing I have a question about registering device vital product data or a pseudo device identifier with devfs to facilitate device alias resolution. scsidev can use similar data obtained from the device in aliasing names. I had seen some traffic a while back, but that was on the linux-scsi alias concerning this capability. Is this on a TODO list? Has anyone looked into this? or ??? Thanks, -Mike From owner-devfs@oss.sgi.com Thu Feb 15 07:38:59 2001 Received: by oss.sgi.com id ; Thu, 15 Feb 2001 07:38:38 -0800 Received: from ldhb041.lss.emc.com ([168.159.59.41]:6916 "EHLO mobilix.atnf.CSIRO.AU") by oss.sgi.com with ESMTP id ; Thu, 15 Feb 2001 07:38:34 -0800 Received: (from rgooch@localhost) by mobilix.ras.ucalgary.ca (8.10.0/8.10.0) id f1ELFVV00392; Thu, 15 Feb 2001 08:15:31 +1100 Date: Thu, 15 Feb 2001 08:15:31 +1100 Message-Id: <200102142115.f1ELFVV00392@mobilix.ras.ucalgary.ca> From: Richard Gooch To: =?iso-8859-1?B?RnLpZOlyaWMgTC4gVy4=?= Meunier <0@pervalidus.net> Cc: devfs@oss.sgi.com Subject: Re: /etc/securetty problem In-Reply-To: <20010202000527.I160@pervalidus.dyndns.org> References: <20010202000527.I160@pervalidus.dyndns.org> Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing 0@pervalidus.net writes: > Hi. For the first time I installed devfs (Kernel 2.4.1). It's > working without any major problems, but I can't log as root on > any console if I change /etc/securetty to use vc/1 (I also > tried with 1) instead of tty1. Check the FAQ. It talks about enabling root logins at the console. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Thu Feb 15 21:01:56 2001 Received: by oss.sgi.com id ; Thu, 15 Feb 2001 21:01:46 -0800 Received: from [200.216.82.254] ([200.216.82.254]:22692 "EHLO pervalidus.dyndns.org") by oss.sgi.com with ESMTP id ; Thu, 15 Feb 2001 21:01:35 -0800 Received: from pervalidus by pervalidus.dyndns.org with local (Exim 3.22 #1) id 14Td0D-0004LF-00; Fri, 16 Feb 2001 03:00:17 -0200 Date: Fri, 16 Feb 2001 03:00:17 -0200 From: =?iso-8859-1?B?RnLpZOlyaWMgTC4gVy4=?= Meunier <0@pervalidus.net> To: Richard Gooch Cc: devfs@oss.sgi.com Subject: Re: /etc/securetty problem Message-ID: <20010216030017.X1922@pervalidus.dyndns.org> References: <20010202000527.I160@pervalidus.dyndns.org> <200102142115.f1ELFVV00392@mobilix.ras.ucalgary.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.3.14i In-Reply-To: <200102142115.f1ELFVV00392@mobilix.ras.ucalgary.ca>; from rgooch@ras.ucalgary.ca on Thu, Feb 15, 2001 at 08:15:31AM +1100 X-Mailer: Mutt/1.3.14i - Linux 2.4.1 Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Hi Richard. On Thu, Feb 15, 2001 at 08:15:31AM +1100, Richard Gooch wrote: > 0@pervalidus.net writes: > > Hi. For the first time I installed devfs (Kernel 2.4.1). It's > > working without any major problems, but I can't log as root on > > any console if I change /etc/securetty to use vc/1 (I also > > tried with 1) instead of tty1. > > Check the FAQ. It talks about enabling root logins at the console. I checked both Documentation/filesystems/devfs/README and http://www.atnf.csiro.au/~rgooch/linux/docs/devfs.html Are you talking about http://www.atnf.csiro.au/~rgooch/linux/docs/devfs.html#quick-start, the 'System Libraries ... /etc/securetty' part? I use glibc 2.2.2 but don't have Linux-PAM installed (Slackware uses shadow). I can use agetty from util-linux without any problems (I set /etc/inittab to use vc/1 -> vc/4). The problem is login. I can't use the one from util-linux because it needs PAM. I have to use all authentication programs from shadow. If I set /etc/securetty to use 1 or vc/1 root can't log in. It works if I use tty1. The problem seems to be with login from shadow. I'd appreciate any reports from Slackware users. Unfortunately, I think 99% are using a distribution with PAM. My system: Linux Kernel 2.4.1 on x86 shadow-20000902: login util-linux-2.10s: agetty -- Frédéric L. W. Meunier - http://www.pervalidus.net/ 0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR) From owner-devfs@oss.sgi.com Sat Feb 17 10:36:07 2001 Received: by oss.sgi.com id ; Sat, 17 Feb 2001 10:35:57 -0800 Received: from p5.usnyc1.stsn.com ([199.106.216.5]:61962 "EHLO nychoteldns01.stsn.com") by oss.sgi.com with ESMTP id ; Sat, 17 Feb 2001 10:35:40 -0800 Received: from mobilix.atnf.CSIRO.AU ([10.0.209.160]) by nychoteldns01.stsn.com (8.11.0/8.11.0) with SMTP id f1HIb8n08810 for ; Sat, 17 Feb 2001 13:37:09 -0500 Received: (from rgooch@localhost) by mobilix.atnf.CSIRO.AU (8.10.0/8.10.0) id f1HIZ9n12590; Sun, 18 Feb 2001 05:35:09 +1100 Date: Sun, 18 Feb 2001 05:35:09 +1100 Message-Id: <200102171835.f1HIZ9n12590@mobilix.atnf.CSIRO.AU> From: Richard Gooch To: =?iso-8859-1?B?RnLpZOlyaWMgTC4gVy4=?= Meunier <0@pervalidus.net> Cc: devfs@oss.sgi.com Subject: Re: /etc/securetty problem In-Reply-To: <20010216030017.X1922@pervalidus.dyndns.org> References: <20010202000527.I160@pervalidus.dyndns.org> <200102142115.f1ELFVV00392@mobilix.ras.ucalgary.ca> <20010216030017.X1922@pervalidus.dyndns.org> Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing 0@pervalidus.net writes: > Hi Richard. > > On Thu, Feb 15, 2001 at 08:15:31AM +1100, Richard Gooch wrote: > > 0@pervalidus.net writes: > > > Hi. For the first time I installed devfs (Kernel 2.4.1). It's > > > working without any major problems, but I can't log as root on > > > any console if I change /etc/securetty to use vc/1 (I also > > > tried with 1) instead of tty1. > > > > Check the FAQ. It talks about enabling root logins at the console. > > I checked both Documentation/filesystems/devfs/README and > http://www.atnf.csiro.au/~rgooch/linux/docs/devfs.html > > Are you talking about > http://www.atnf.csiro.au/~rgooch/linux/docs/devfs.html#quick-start, > the 'System Libraries ... /etc/securetty' part? Yes. > I use glibc 2.2.2 but don't have Linux-PAM installed > (Slackware uses shadow). I can use agetty from util-linux > without any problems (I set /etc/inittab to use vc/1 -> vc/4). > The problem is login. I can't use the one from util-linux > because it needs PAM. I have to use all authentication > programs from shadow. OK. So it looks like shadow is broken. > If I set /etc/securetty to use 1 or vc/1 root can't log in. > It works if I use tty1. So perhaps the shadow code is hard-wired to use tty#, or perhaps it's broken the same way other code was and assumes that the devices are in /dev and not a subdirectory of /dev. > The problem seems to be with login from shadow. I'd appreciate > any reports from Slackware users. Unfortunately, I think 99% > are using a distribution with PAM. > > My system: > > Linux Kernel 2.4.1 on x86 > shadow-20000902: login > util-linux-2.10s: agetty Can you please check through the shadow code to find out what's going wrong, and then send a patch to the shadow maintainer? Let me know if there are any workarounds (or fixed versions of shadow that can be installed), so I can update the FAQ. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Mon Feb 19 13:20:37 2001 Received: by oss.sgi.com id ; Mon, 19 Feb 2001 13:20:27 -0800 Received: from charcot.informed.net ([205.167.80.72]:40198 "EHLO notes.informed.net") by oss.sgi.com with ESMTP id ; Mon, 19 Feb 2001 13:20:12 -0800 Subject: Linux From Scratch To: devfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.4a July 24, 2000 Message-ID: From: mclinden@informed.net Date: Mon, 19 Feb 2001 15:31:04 -0500 X-MIMETrack: Serialize by Router on notes.informed.net/informed dot net(Release 5.0.5 |September 22, 2000) at 02/19/2001 03:31:10 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Has anyone successfully configured a system to use devfs under LFS. I'm running: Linux 2.4.1, Glibc 2.1.3, GCC 2.95.2, Modutils 2.4.2, Shadow 20000902, and Net-Kit 0.17. depmod, modinfo and insmod give me segmentation fault when I am running with devfs (and devfsd). telnetd gives getpeername: Socket operation on non-socket. I've read the FAQ, configured the system accordingly, and can boot into single user mode but I cannot bring up most daemons and it seems that a great many of the /dev entries that this kernel and software require are not created by devfsd. Thanks in advance. I have been playing with the configuration for four days, now, and nothing I do seems to make things better or worse. Sean From owner-devfs@oss.sgi.com Mon Feb 19 22:54:33 2001 Received: by oss.sgi.com id ; Mon, 19 Feb 2001 22:54:23 -0800 Received: from orion.dwf.com ([204.134.2.19]:19072 "EHLO orion.dwf.com") by oss.sgi.com with ESMTP id ; Mon, 19 Feb 2001 22:54:03 -0800 Received: from orion.dwf.com (reg@localhost) by orion.dwf.com (8.11.0/8.11.1) with ESMTP id f1K6rvl01365 for ; Mon, 19 Feb 2001 23:53:57 -0700 Message-Id: <200102200653.f1K6rvl01365@orion.dwf.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: devfs@oss.sgi.com Subject: What does this error message mean? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Feb 2001 23:53:57 -0700 From: reg@dwf.com Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Linux kernel 2.4.1, Iomega Zip250. Ive had this working with earlier kernels (and devfs?), but am trying to move to 2.4.1 and I dont know what to make of the following error message. [root@orion reg]# mount /dev/ide/host0/bus1/target1/lun0/part4 /mnt/zip4 /dev/ide/host0/bus1/target1/lun0/part4: Input/output error mount: /dev/ide/host0/bus1/target1/lun0/part4 has wrong major or minor number Listing /dev/ide/host0/bus1/target1/lun0 shows [root@orion reg]# ls -lai /dev/ide/host0/bus1/target1/lun0 total 0 355 drwxr-xr-x 1 root root 0 Dec 31 1969 . 354 drwxr-xr-x 1 root root 0 Dec 31 1969 .. 880 brw------- 1 root root 22, 64 Dec 31 1969 disc 881 brw------- 1 root root 22, 65 Dec 31 1969 part1 882 brw------- 1 root root 22, 66 Dec 31 1969 part2 883 brw------- 1 root root 22, 67 Dec 31 1969 part3 884 brw------- 1 root root 22, 68 Dec 31 1969 part4 Im really not sure what 'wrong major or minor number' implies here. Any thoughts to get me on track? -- Reg.Clemens reg@dwf.com From owner-devfs@oss.sgi.com Tue Feb 20 05:21:35 2001 Received: by oss.sgi.com id ; Tue, 20 Feb 2001 05:21:25 -0800 Received: from p5.usnyc1.stsn.com ([199.106.216.5]:3853 "EHLO nychoteldns01.stsn.com") by oss.sgi.com with ESMTP id ; Tue, 20 Feb 2001 05:21:04 -0800 Received: from mobilix.atnf.CSIRO.AU ([10.0.209.160]) by nychoteldns01.stsn.com (8.11.0/8.11.0) with SMTP id f1KDMEn14567 for ; Tue, 20 Feb 2001 08:22:24 -0500 Received: (from rgooch@localhost) by mobilix.atnf.CSIRO.AU (8.10.0/8.10.0) id f1KDJpw10090; Wed, 21 Feb 2001 00:19:51 +1100 Date: Wed, 21 Feb 2001 00:19:51 +1100 Message-Id: <200102201319.f1KDJpw10090@mobilix.atnf.CSIRO.AU> From: Richard Gooch To: reg@dwf.com Cc: devfs@oss.sgi.com Subject: Re: What does this error message mean? In-Reply-To: <200102200653.f1K6rvl01365@orion.dwf.com> References: <200102200653.f1K6rvl01365@orion.dwf.com> Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing reg@dwf.com writes: > Linux kernel 2.4.1, Iomega Zip250. > Ive had this working with earlier kernels (and devfs?), but am trying to move > to > 2.4.1 and I dont know what to make of the following error message. > > [root@orion reg]# mount /dev/ide/host0/bus1/target1/lun0/part4 /mnt/zip4 > /dev/ide/host0/bus1/target1/lun0/part4: Input/output error > mount: /dev/ide/host0/bus1/target1/lun0/part4 has wrong major or minor > number That looks like a bogus message. Make sure you have mount-2.10p or later (mount --version). > Im really not sure what 'wrong major or minor number' implies here. > Any thoughts to get me on track? I think the I/O error is more meaningful. Do you get any kernel messages? What happens if you strace mount? Any clues? Are you able to use dd on the block device directly? Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Tue Feb 20 19:58:51 2001 Received: by oss.sgi.com id ; Tue, 20 Feb 2001 19:58:31 -0800 Received: from vindaloo.ras.ucalgary.ca ([136.159.55.21]:25994 "EHLO vindaloo.ras.ucalgary.ca") by oss.sgi.com with ESMTP id ; Tue, 20 Feb 2001 19:58:18 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id f1L3wGK24936; Tue, 20 Feb 2001 20:58:16 -0700 Date: Tue, 20 Feb 2001 20:58:16 -0700 Message-Id: <200102210358.f1L3wGK24936@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: devfs@oss.sgi.com Subject: Ignore Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Testing email problems. Please ignore. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Sun Feb 25 06:48:19 2001 Received: by oss.sgi.com id ; Sun, 25 Feb 2001 06:48:10 -0800 Received: from mailgate.rz.uni-karlsruhe.de ([129.13.64.97]:49935 "EHLO mailgate.rz.uni-karlsruhe.de") by oss.sgi.com with ESMTP id ; Sun, 25 Feb 2001 06:47:53 -0800 Received: from nce2.hadiko.de (hadince2.hadiko.uni-karlsruhe.de [172.20.32.2]) by mailgate.rz.uni-karlsruhe.de with esmtp (Exim 3.16 #1) id 14X2Sg-0005eg-00; Sun, 25 Feb 2001 15:47:46 +0100 Received: from panorama.hadiko.de (hadii309.hadiko.uni-karlsruhe.de [172.20.44.69]) by nce2.hadiko.de (8.9.3/8.9.3) with SMTP id PAA01213 for ; Sun, 25 Feb 2001 15:47:45 +0100 (MET) Received: (qmail 23345 invoked from network); 25 Feb 2001 14:46:14 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 25 Feb 2001 14:46:14 -0000 To: devfs@oss.sgi.com Subject: EXPORT_SYMBOL(devfs_get_name); From: Robert Siemer X-Mailer: Mew version 1.94b25 on Emacs 20.5 / Mule 4.0 (HANANOEN) Reply-To: Robert Siemer Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010225154613G.siemer@panorama.hadiko.de> Date: Sun, 25 Feb 2001 15:46:13 +0100 X-Dispatcher: imput version 990425(IM115) Lines: 12 Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Hi! Richard, don't forget to add an EXPORT_SYMBOL(devfs_get_name); to linux/fs/devfs/base.c! Ciao, Robert From owner-devfs@oss.sgi.com Wed Feb 28 00:47:49 2001 Received: by oss.sgi.com id ; Wed, 28 Feb 2001 00:47:39 -0800 Received: from sis.com.tw ([203.67.208.2]:64891 "EHLO maillog.sis.com.tw") by oss.sgi.com with ESMTP id ; Wed, 28 Feb 2001 00:47:21 -0800 Received: from fw11.sis.com.tw (fw11-hme1 [192.168.48.251]) by maillog.sis.com.tw (8.9.3+Sun/8.9.3) with ESMTP id QAA11970 for ; Wed, 28 Feb 2001 16:39:38 +0800 (CST) Received: from sismg.sis.com.tw (sismg.sis.com.tw [192.9.200.2]) by fw11.sis.com.tw (8.9.3+Sun/8.9.3) with ESMTP id QAA15484 for ; Wed, 28 Feb 2001 16:46:57 +0800 (CST) Received: from twhqm01.sis.com.tw (mail [192.168.33.1]) by sismg.sis.com.tw (8.9.3+Sun/8.9.1) with ESMTP id QAA29626 for ; Wed, 28 Feb 2001 16:43:39 +0800 (CST) Received: from sis.com.tw ([172.19.209.230]) by twhqm01.sis.com.tw (Lotus Domino Release 5.0.5) with ESMTP id 2001022816472462:3944 ; Wed, 28 Feb 2001 16:47:24 +0800 Message-ID: <3A9CBC50.62DD63CD@sis.com.tw> Date: Wed, 28 Feb 2001 16:52:32 +0800 From: "LC. Chang" X-Mailer: Mozilla 4.72 [zh_TW] (X11; U; Linux 2.4.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: devfs@oss.sgi.com CC: ollie@sis.com.tw, erick@sis.com.tw, kmliu@sis.com.tw Subject: devfsd device name question.. X-MIMETrack: Itemize by SMTP Server on twhqm01/HQ/SiS(Release 5.0.5 |September 22, 2000) at 02/28/2001 04:47:24 PM, Serialize by Router on twhqm01/HQ/SiS(Release 5.0.5 |September 22, 2000) at 02/28/2001 04:47:25 PM, Serialize complete at 02/28/2001 04:47:25 PM Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=big5 Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Hi, I have linux-2.4.0 kernel compiled with devfs support, and start devfsd (v1.3.11) in my boot script. I have put devfsd.conf & modules.devfs in /etc , what else should I do to mount my IDE dvdrom as /dev/dvd? (I build cdrom and IDE driver as modules) thanks, L.C. Chang From owner-devfs@oss.sgi.com Wed Feb 28 08:05:20 2001 Received: by oss.sgi.com id ; Wed, 28 Feb 2001 08:05:10 -0800 Received: from electre.pasteur.fr ([157.99.64.120]:50705 "EHLO electre.pasteur.fr") by oss.sgi.com with ESMTP id ; Wed, 28 Feb 2001 08:05:00 -0800 Received: from Baldrick (dial-ip-82.dial.pasteur.fr [157.99.10.82]) by electre.pasteur.fr (8.11.3/8.11.3) with ESMTP id f1SG4uF25991 for ; Wed, 28 Feb 2001 17:04:57 +0100 (CET) Received: from duncan by Baldrick with local (Exim 3.22 #1 (Debian)) id 14Y8ps-00008w-00 for ; Wed, 28 Feb 2001 16:48:16 +0100 Date: Wed, 28 Feb 2001 16:48:16 +0100 To: devfs@oss.sgi.com Subject: cpuid/msr don't create /dev/cpu/0/stuff Message-ID: <20010228164816.A551@Baldrick> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.12i From: Duncan Sands Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Hi, I'm using the 2.4.0 kernel with devfs. I compiled in cpuid and msr. I expected /dev/cpu/0/cpuid and /dev/cpu/0/msr to be created automagically, but they are not. (This causes the powertweak daemon to spew out many error messages at boot time because it tries to read from /dev/cpu/0/cpuid, which is what got me looking into this). I don't know if this is a problem with cpuid/msr, devfs or my expectations. Any ideas? Thanks for your help. Duncan Sands. From owner-devfs@oss.sgi.com Wed Feb 28 08:13:50 2001 Received: by oss.sgi.com id ; Wed, 28 Feb 2001 08:13:40 -0800 Received: from vindaloo.ras.ucalgary.ca ([136.159.55.21]:53386 "EHLO vindaloo.ras.ucalgary.ca") by oss.sgi.com with ESMTP id ; Wed, 28 Feb 2001 08:13:27 -0800 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id f1SGD0P01080; Wed, 28 Feb 2001 09:13:00 -0700 Date: Wed, 28 Feb 2001 09:13:00 -0700 Message-Id: <200102281613.f1SGD0P01080@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: Duncan Sands Cc: devfs@oss.sgi.com Subject: Re: cpuid/msr don't create /dev/cpu/0/stuff In-Reply-To: <20010228164816.A551@Baldrick> References: <20010228164816.A551@Baldrick> Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing Duncan Sands writes: > Hi, I'm using the 2.4.0 kernel with devfs. I compiled in > cpuid and msr. I expected /dev/cpu/0/cpuid and > /dev/cpu/0/msr to be created automagically, but they are > not. (This causes the powertweak daemon to spew out many > error messages at boot time because it tries to read from > /dev/cpu/0/cpuid, which is what got me looking into this). > I don't know if this is a problem with cpuid/msr, devfs or > my expectations. Any ideas? Check the sources for these drivers. I bet they don't make calls to devfs_register(). Add them and send a patch to HPA. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca From owner-devfs@oss.sgi.com Wed Feb 28 13:12:52 2001 Received: by oss.sgi.com id ; Wed, 28 Feb 2001 13:12:43 -0800 Received: from electre.pasteur.fr ([157.99.64.120]:62222 "EHLO electre.pasteur.fr") by oss.sgi.com with ESMTP id ; Wed, 28 Feb 2001 13:12:21 -0800 Received: from Baldrick (dial-ip-66.dial.pasteur.fr [157.99.10.66]) by electre.pasteur.fr (8.11.3/8.11.3) with ESMTP id f1SLC8F91994; Wed, 28 Feb 2001 22:12:09 +0100 (CET) Received: from duncan by Baldrick with local (Exim 3.22 #1 (Debian)) id 14Y9VV-0000Fm-00; Wed, 28 Feb 2001 17:31:17 +0100 Date: Wed, 28 Feb 2001 17:30:57 +0100 To: Richard Gooch Cc: devfs@oss.sgi.com Subject: Re: cpuid/msr don't create /dev/cpu/0/stuff Message-ID: <20010228173057.A928@Baldrick> References: <20010228164816.A551@Baldrick> <200102281613.f1SGD0P01080@vindaloo.ras.ucalgary.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.12i In-Reply-To: <200102281613.f1SGD0P01080@vindaloo.ras.ucalgary.ca>; from rgooch@ras.ucalgary.ca on Wed, Feb 28, 2001 at 09:13:00AM -0700 From: Duncan Sands Sender: owner-devfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;devfs-outgoing > > Hi, I'm using the 2.4.0 kernel with devfs. I compiled in > > cpuid and msr. I expected /dev/cpu/0/cpuid and > > /dev/cpu/0/msr to be created automagically, but they are > > not. (This causes the powertweak daemon to spew out many > > error messages at boot time because it tries to read from > > /dev/cpu/0/cpuid, which is what got me looking into this). > > I don't know if this is a problem with cpuid/msr, devfs or > > my expectations. Any ideas? > > Check the sources for these drivers. I bet they don't make calls to > devfs_register(). Add them and send a patch to HPA. You are right. I will do it. Thanks, Duncan.