Re: linux-kernel-digest V1 #616
Shawn Rutledge (ecloud@goodnet.com)
Tue, 19 Nov 1996 09:49:09 -0700 (MST)
>
>
> linux-kernel-digest Tuesday, 19 November 1996 Volume 01 : Number 616
>
> In this issue:
>
> Re: Possible /etc/hosts parsing bug?
> Re: mmap() question.
> Kernel Panic
> Re: cyclom Y(pci)
> Problem compiling 2.0.25
> Message status - undeliverable
> NFS-Root problems
> Message status - undeliverable
> __start___ex_table undefined reference
> Re: Problem compiling 2.0.25
> CDROM and Intel VX M/B Problem
> Message status - undeliverable
> Message status - undeliverable
> Can't compile 2.1.7 plus
> Re: CDROM and Intel VX M/B Problem
> Re: "Exception at ..." with 2.1.9 and 2.1.10 kernels
> Configuracion de DNS
> Message status - undeliverable
> wait_queue bug ??
> Re: Wanted: Logitec Scanner - Any suport
> IP Checksumming
> Re: Modules 2.1.8 problem report
> Re: 2.0.0/2.0.25 oopses with buslogic 956C and two 4G seagates ...
> Re: Glitch in sys_chroot()
> Re: Linux & ECC memory
> Re: Message status - undeliverable
> Re: Printer on fire - I feel like an idiot
> Re: Possible /etc/hosts parsing bug?
> real POSIX.1b semaphores
> Anybody having IDE-CD problems with 2.1.10?
> Re: Configuracion de DNS
> Re: Can't compile 2.1.7 plus
> EIDE more reliable than SCSI?
> Re: Problem compiling 2.0.25
> FYI: I2O Architecture
> Cyrix 6x86
> Re: real POSIX.1b semaphores
> 2.1.x doesn't boot
> Re: real POSIX.1b semaphores
> Re: real POSIX.1b semaphores
> Re: real POSIX.1b semaphores
> Re: real POSIX.1b semaphores
> Re: Anybody having IDE-CD problems with 2.1.10?
> Re: FYI: I2O Architecture
> trouble with modules in 2.1.11
> [PATCH] to allow seagate.c to compile properly
> Re: Cyrix 6x86
> Bug in sysklogd v1.3-0
> 2.1.11 breaks module support (long)
> Re: CLONE_PID (was: POSIX.1b semaphores)
> Re: unlink system call on directories - Bug + fix
> Re: wait_queue bug ?
>
> See the end of the digest for information on subscribing to the linux-kernel
> or linux-kernel-digest mailing lists.
>
> ----------------------------------------------------------------------
>
> From: de_smet@lurpa.ens-cachan.fr (DE SMET Olivier)
> Date: Mon, 18 Nov 96 17:17:30 GMT
> Subject: Re: Possible /etc/hosts parsing bug?
>
> Hi,
>
> Think about the scanf 'C' function:
>
> a number beging with 0 is in OCTAL base :)
>
> so 016(octal) = 14(dec)....
>
> Olivier
>
> de_smet@lurpa.ens-cachan.fr
>
> ------------------------------
>
> From: David Howells <d.howells@nexor.co.uk>
> Date: Mon, 18 Nov 1996 16:08:16 +0000
> Subject: Re: mmap() question.
>
> It is standard UNIX stuff, I believe, that mmap() can only map those portions
> of the file that actually exist when the call is made, and the mapping won't
> change unless you tell it to.
>
> The only case where this is different is when the mapping is on a character
> device file.
>
> David Howells
>
> ------------------------------
>
> From: Bill Perkins <perk@iag.net>
> Date: Mon, 18 Nov 1996 11:38:47 -0500 (EST)
> Subject: Kernel Panic
>
> Hello, All,
>
> I am trying to set up a boot disk as well as a root disk for Linux 2.0.24
> (Slackware '96). I've created a minimal kernel with floppy, ramdisk, IDE,
> CDROM, and printing support, but no modules. It is also set up with appropriate
> file systems: e2fs and minix; don't care about DOS in this case. My system boots
> OK, but after it asks for the root disk and crunches on that for a few moments,
> I get the following message:
>
> Kernel panic: VFS: Unable to mount root fs on 02:00
>
> Any ideas on what I'm doing wrong? This is probably an easy one, but I haven't
> seen any mention of it in the news groups, the HOWTO's, or anywhere else.
>
> TIA,
>
> Bill Perkins <perk@iag.net>
>
>
> ------------------------------
>
> From: lutz@as-node.jena.thur.de (Lutz Donnerhacke)
> Date: 18 Nov 1996 09:01:24 GMT
> Subject: Re: cyclom Y(pci)
>
> * Herbert Rosmanith (herp@wildsau.idv.uni-linz.ac.at) wrote:
> > > Cyclom-Y PCI host card with no Serial-Modules at 0xc8000.
> > ^^^^^^^^^^^^^^^^^
> > I was then unable to access ttyC?
>
> Yes.
>
> > > Cyclom-Y/PCI #1: 0xc8000-0xcbfff, IRQ15, 16 channels starting from port 0.
> > which means that all ttyC? are now accessible.
>
> Yes.
>
> If you can't fix the problem, return the card.
>
> - --
> | Lutz Donnerhacke +49/3641/380259 voice, -60 ISDN, -61 V.34 und Fax |
> | I have a full-time real job. My current project is figuring how to |
> | allocate unique 16-bit UIDs to more than 65536 university users. |
> | It keeps me quite busy. |
> +--------------------------------------------------------------Marcus Watts-+
>
> ------------------------------
>
> From: "Jaime G. Ghirelli" <jaime@ba.net>
> Date: Mon, 18 Nov 1996 14:29:03 -0600 (CST)
> Subject: Problem compiling 2.0.25
>
> I get the following error message when compiling the kernel 2.0.25 on an
> elf system 1.2.13 (slakware)
>
> make[1]: Entering directory `/usr/src/linux-2.0.25/arch/i386/kernel'
> gcc -D__KERNEL__ -I/usr/src/linux-2.0.25/include -Wall
> - -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe
> - -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -c
> - -o time.o time.c
> {standard input}: Assembler messages:
> {standard input}:768: Error: no such 386 instruction: `rdmsr'
> {standard input}:770: Error: no such 386 instruction: `wrmsr'
> make[1]: *** [time.o] Error 1
> make[1]: Leaving directory `/usr/src/linux-2.0.25/arch/i386/kernel'
> make: *** [linuxsubdirs] Error 2
>
>
> Please send any ideas or pointers to jaime@ba.net (I'm not
> suscribed to the list)
>
> Regards from Argentina,
> Jaime
>
>
> - ---------------------------------------------------------------------
> Ing. Jaime Garcia Ghirelli Argentina On-line S.A.
> E-mail: jaime@ba.net Bernardo de Irigoyen 546, Piso 6
> Buenos Aires (1072)
> http://www.ba.net Tel.(541) 343-9999 Fax. 334-0509
>
>
>
>
> ------------------------------
>
> From: Mailer-Daemon@novell.com
> Date: Mon, 18 Nov 1996 14:13:52 +0000
> Subject: Message status - undeliverable
>
> The message that you sent was undeliverable to the following:
> rganesan@blr.novell.com
>
> Transcript of session follows:
> novidc.blr.novell.com
> 450 MX lookup failure
>
> Possibly truncated original message follows:
>
> Received: from INET-UKB-Message_Server by novell.com
> with Novell_GroupWise; Tue, 12 Nov 1996 18:05:13 +0000
> Received: from nic.funet.fi by ns.Novell.COM (4.1/SMI-4.1)
> id AA07964; Tue, 12 Nov 96 11:03:52 MST
> X-Warning: Original message contained 8-bit characters, however during
> the SMTP transport session the receiving system was unable to
> announce capability of receiving 8-bit SMTP (RFC 1425-1428),
> and as this message does not have MIME headers (RFC 1341) to
> enable encoding change, we had very little choices.
> X-Warning: We ASSUME it is less harmfull to add the MIME headers, and
> convert the text to Quoted-Printable, than not to do so,
> and to strip the message to 7-bits.. (RFC 1428 Appendix A)
> Received: from vger.rutgers.edu ([128.6.190.2]) by nic.funet.fi with ESMTP id <62725-20782>; Tue, 12 Nov 1996 18:49:05 +0200
> Received: by vger.rutgers.edu id <156747-11039>; Tue, 12 Nov 1996 11:41:20 -0500
> Precedence: bulk
> Message-Id: <s288bc59.046@novell.com>
>
> ------------------------------
>
> From: Shane DeRidder <shane@together.net>
> Date: Mon, 18 Nov 1996 13:01:19 -0500 (EST)
> Subject: NFS-Root problems
>
> I'm not sure if I'm sending this to the appropriate lists, but I'm having
> a bit of trouble with an NFS-mounted root filesystem.
>
> I have a DEC Alpha UDB with 64mb of memory running Linux 2.0.25 (with
> axp-diffs from 2.0.21) and the RedHat 4.0 distribution. The machine the
> root filesystem is mounted from is a Sun Sparc 20 clone running Solaris
> 2.5 with the recommended patch cluster from Sun Microsystems.
>
> If I execute 'ncftp' then quit and run 'ncftp' again, I immediately get
> "NFS server (ip address here) not responding." Moments later, *every*
> machine connected to that same Solaris machine via NFS get the same
> message. Basically, the NFS server on the Solaris machine becomes totally
> unusable and locks up tighter than a drum. I can't even kill the NFS
> server daemon and restart it. The only way to recover is to reboot the
> Solaris machine.
>
> This only happens when I'm using the Alpha box. I've tried a similar
> setup on an i386-based machine and experienced no problems whatsoever.
> I've tried Solaris 2.5 with and without the patches installed. I've even
> tried different machines. The same thing happens every time. I can't
> seem to produce this problem with anything other than ncftp.
>
> Doing an strace on ncftp shows it trying to write to an flock()'ed file
> called ~/.ncftp/i.am.running just as the NFS server crashes.
>
> Has anyone else experimented with NFS-root on the Linux/axp platform?
>
>
> Shane-
>
> - --
> Shane DeRidder | System Admin / Webmaster | Love doesn't make
> shane@together.net | Together Networks | the world go 'round,
> http://blah.together.net/ | http://www.together.net/ | but it makes the
> (802)860-5166 | (802)862-2030 | ride worthwhile...
>
>
> ------------------------------
>
> From: Mailer-Daemon@novell.com
> Date: Sun, 17 Nov 1996 12:28:16 +0000
> Subject: Message status - undeliverable
>
> The message that you sent was undeliverable to the following:
> rganesan@blr.novell.com
>
> Transcript of session follows:
> novidc.blr.novell.com
> 450 MX lookup failure
>
> Possibly truncated original message follows:
>
> Received: from INET-UKB-Message_Server by novell.com
> with Novell_GroupWise; Tue, 12 Nov 1996 17:05:38 +0000
> Received: from nic.funet.fi by ns.Novell.COM (4.1/SMI-4.1)
> id AA07738; Tue, 12 Nov 96 10:04:23 MST
> Received: from vger.rutgers.edu ([128.6.190.2]) by nic.funet.fi with ESMTP id <62817-31090>; Tue, 12 Nov 1996 18:58:36 +0200
> Received: by vger.rutgers.edu id <156951-11040>; Tue, 12 Nov 1996 11:53:24 -0500
> Precedence: bulk
> Message-Id: <s288ae62.079@novell.com>
> Date: Sat, 09 Nov 1996 21:21:51 +0000
> From: <linux-kernel@vger.rutgers.edu>
> To: linux-kernel-digest@vger.rutgers.edu,
> owner-linux-kernel-digest@vger.rutgers.edu
> Subject: linux-kernel-digest V1 #596
>
>
> linux-kernel-digest Saturday, 9 November 1996 Volume 01 : Number 596
>
> In this issue:
>
> Re: RSH problem is back
> restore_flags(unsigned int) correct?
> where to get the latest kernel patches/sources?
> Re: NFS client permission bug
> 2.0.25: X performance probs solved
> Re: dev
> Problem with HP-SCSI disk & NCR53C810 & 2.0.24
>
> ------------------------------
>
> From: Luca Bolognese <black@tnt.it>
> Date: Mon, 18 Nov 1996 19:29:56 +0100
> Subject: __start___ex_table undefined reference
>
> Hello, I'm trying to compile 2.1.10
> but I got that :
>
> arch/i386/mm/mm.o: In function `search_exception_table':
> arch/i386/mm/mm.o(.text+0xbd8): undefined reference to `__start___ex_table'
> arch/i386/mm/mm.o(.text+0xbdd): undefined reference to `__stop___ex_table'
> arch/i386/mm/mm.o(.text+0xbe2): undefined reference to `__start___ex_table'
> arch/i386/mm/mm.o(.text+0xbec): undefined reference to `__start___ex_table'
> arch/i386/mm/mm.o(.text+0xbf7): undefined reference to `__stop___ex_table'
> make: *** [vmlinux] Error 1
>
> What is the problem ?
> Thank for help
> Luca
>
> /+-----Don't follow leaders, just watch the parkingmeters ( B.Dylan) ----+
> | ||
> | Bolognese Luca E-mail: black@tnt.it |
> | Via Pirandello 1A/30 ||
> | Savona 17100 Phone: 039 19 805978 |
> | Italy ||
> | |
> +-----You don't need a wheaterman to know the way the wind blows---+
>
> ------------------------------
>
> From: "Erik Walthinsen (Omega)" <omega@sequent.com>
> Date: Mon, 18 Nov 1996 10:23:40 -0800 (PST)
> Subject: Re: Problem compiling 2.0.25
>
> On Mon, 18 Nov 1996, Jaime G. Ghirelli wrote:
>
> > I get the following error message when compiling the kernel 2.0.25 on an
> > elf system 1.2.13 (slakware)
>
> This is because you are running old versions of binutils, gcc, libc, etc.
> You need to upgrade all these by either installing "Slackware96" or a
> recent RedHat, or compiling/installing them manually. For more info, read
> /usr/src/linux/Documentation/Changes. But from what I've heard, doing it
> manually can be very painful.
>
> Good luck,
> Omega
>
> Erik Walthinsen - Programmer, webmaster, 3D artist, etc. __
> __ / /\
> / \ omega@sequent.com Work: (503)578-5314 / / \
> | | M E G A omega@teleport.com Home: (503)281-4281 / / /\ \
> _\ /_ psu12113@odin.cc.pdx.edu Majoring in CS / / /\ \ \
> / /_/__\ \ \
> Omega Station: http://www.teleport.com/~omega/ /________\ \ \
> Info on Linux, Graphics, Descent, Laptops, etc. \___________\/
>
>
>
> ------------------------------
>
> From: RICHARD <rviennea@ee.ryerson.ca>
> Date: Mon, 18 Nov 1996 13:19:55 -0500 (EST)
> Subject: CDROM and Intel VX M/B Problem
>
> I have just replaced my motherboard with the new Intel VX chipset
> motherboard and cannot use my Sanyo H94 CDROM (connected to a
> MediaVision JAZZ 16 sound card) anymore. The problem is that the Linux
> support requires that the soundcard/cdrom be initialized in dos/win
> followed by a soft reboot into Linux (kernel 2.0.18). The new M/B however
> Resets the card during a soft reboot since it has added support for
> booting directly from a cdrom (atleast it appears that way!). I am
> wondering if there is a way around this? Any help would be much
> appreciated!
>
> Richard Vienneau
>
>
> ------------------------------
>
> From: Mailer-Daemon@novell.com
> Date: Sun, 17 Nov 1996 21:19:14 +0000
> Subject: Message status - undeliverable
>
> The message that you sent was undeliverable to the following:
> rganesan@blr.novell.com
>
> Transcript of session follows:
> novidc.blr.novell.com
> 450 MX lookup failure
>
> Possibly truncated original message follows:
>
> Received: from INET-UKB-Message_Server by novell.com
> with Novell_GroupWise; Tue, 12 Nov 1996 17:25:24 +0000
> Received: from nic.funet.fi by ns.Novell.COM (4.1/SMI-4.1)
> id AA07803; Tue, 12 Nov 96 10:24:08 MST
> Received: from vger.rutgers.edu ([128.6.190.2]) by nic.funet.fi with ESMTP id <62825-23826>; Tue, 12 Nov 1996 18:59:30 +0200
> Received: by vger.rutgers.edu id <164094-11039>; Tue, 12 Nov 1996 11:53:24 -0500
> Precedence: bulk
> Message-Id: <s288b304.092@novell.com>
> Date: Thu, 07 Nov 1996 22:09:47 +0000
> From: <linux-kernel@vger.rutgers.edu>
> To: linux-kernel-digest@vger.rutgers.edu,
> owner-linux-kernel-digest@vger.rutgers.edu
> Subject: linux-kernel-digest V1 #592
>
>
> linux-kernel-digest Thursday, 7 November 1996 Volume 01 : Number 592
>
> In this issue:
>
> Re: Load balancing over Ethernet ...
> 2.0.24: tty->count(1) != #fd's(2)
> Re: X much slower in 2.0.24 than in 1.2.13
> An implementors wishes...
> 2.0.2[1-4] _and_ SMP: unresolved symbols in nfs.o !
> Re: 64 Bits from Larry McVoy
> Re: 64 Bits from Larry McVoy
>
> ------------------------------
>
> From: Mailer-Daemon@novell.com
> Date: Sun, 17 Nov 1996 22:29:28 +0000
> Subject: Message status - undeliverable
>
> The message that you sent was undeliverable to the following:
> rganesan@blr.novell.com
>
> Transcript of session follows:
> novidc.blr.novell.com
> 450 MX lookup failure
>
> Possibly truncated original message follows:
>
> Received: from INET-UKB-Message_Server by novell.com
> with Novell_GroupWise; Tue, 12 Nov 1996 17:19:12 +0000
> Received: from nic.funet.fi by ns.Novell.COM (4.1/SMI-4.1)
> id AA07775; Tue, 12 Nov 96 10:18:03 MST
> X-Warning: Original message contained 8-bit characters, however during
> the SMTP transport session the receiving system was unable to
> announce capability of receiving 8-bit SMTP (RFC 1425-1428),
> and as this message does not have MIME headers (RFC 1341) to
> enable encoding change, we had very little choices.
> X-Warning: We ASSUME it is less harmfull to add the MIME headers, and
> convert the text to Quoted-Printable, than not to do so,
> and to strip the message to 7-bits.. (RFC 1428 Appendix A)
> Received: from vger.rutgers.edu ([128.6.190.2]) by nic.funet.fi with ESMTP id <62973-31090>; Tue, 12 Nov 1996 19:11:52 +0200
> Received: by vger.rutgers.edu id <183182-11040>; Tue, 12 Nov 1996 12:04:25 -0500
> Precedence: bulk
> Message-Id: <s288b190.089@novell.com>
>
> ------------------------------
>
> From: Brian Blackmore <bnb@looking-glass.org>
> Date: Mon, 18 Nov 1996 19:20:16 -0000
> Subject: Can't compile 2.1.7 plus
>
> Ever since the exception code was added any attempt I make to compile the
> kernel for my 386SX results in the following compile errors
>
> ld -m elf_i386 -Ttext 0xC0100000 -e stext arch/i386/kernel/head.o init/main.o init/version.o \
> arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o net/network.a \
> fs/filesystems.a \
> drivers/block/block.a drivers/char/char.a drivers/net/net.a arch/i386/math-emu/math.a \
> /usr/src/linux/arch/i386/lib/lib.a /usr/src/linux/lib/lib.a /usr/src/linux/arch/i386/lib/lib.a -o vmlinux
> arch/i386/mm/mm.o: In function `search_exception_table':
> arch/i386/mm/mm.o(.text+0xbd0): undefined reference to `__start___ex_table'
> arch/i386/mm/mm.o(.text+0xbd5): undefined reference to `__stop___ex_table'
> arch/i386/mm/mm.o(.text+0xbda): undefined reference to `__start___ex_table'
> arch/i386/mm/mm.o(.text+0xbe4): undefined reference to `__start___ex_table'
> arch/i386/mm/mm.o(.text+0xbef): undefined reference to `__stop___ex_table'
> make: *** [vmlinux] Error 1
>
> A quick look through the source find no definition of __start__ex_table but a definition of
> a segment __ex_table, so my guess is this is a "tools" problem, or possibly something
> that only works on a 486 or above. The kernel was compiled on a 2.1.6 machine, with
> gcc 2.7.2, as 2.7 (BFD 2.7.0.3) and ld 2.7 (BFD 2.7.03).
>
> - --
> Brian Blackmore
>
>
> ------------------------------
>
> From: Nathan Bryant <nathan@burgessinc.com>
> Date: Mon, 18 Nov 1996 14:35:54 -0500 (EST)
> Subject: Re: CDROM and Intel VX M/B Problem
>
> Check out the Loadlin program. This is a DOS command-line program which
> allows you to load a linux kernel straight from DOS.
>
> On Mon, 18 Nov 1996, RICHARD wrote:
>
> >
> >
> > I have just replaced my motherboard with the new Intel VX chipset
> > motherboard and cannot use my Sanyo H94 CDROM (connected to a
> > MediaVision JAZZ 16 sound card) anymore. The problem is that the Linux
> > support requires that the soundcard/cdrom be initialized in dos/win
> > followed by a soft reboot into Linux (kernel 2.0.18). The new M/B however
> > Resets the card during a soft reboot since it has added support for
> > booting directly from a cdrom (atleast it appears that way!). I am
> > wondering if there is a way around this? Any help would be much
> > appreciated!
> >
> > Richard Vienneau
> >
>
> +-----------------------+----------------------------------+
> | Nathan Bryant | Resident Unix Geek |
> | nathan@burgessinc.com | Burgess Business Solutions, Inc. |
> +-----------------------+----------------------------------+
>
>
> ------------------------------
>
> From: alan@lxorguk.ukuu.org.uk (Alan Cox)
> Date: Sun, 17 Nov 1996 23:58:35 +0000 (GMT)
> Subject: Re: "Exception at ..." with 2.1.9 and 2.1.10 kernels
>
> > Sorry, I'm still not buying that. Getname comes from linux/fs/namei.c. In
>
> Thats a pity cos he's right and you are wrong.
>
> > the code, it says that it is copying from user-space to kernel-space for
> > "efficiency." Exactly how is this a user problem? User code doesn't know
> > about kernel space.
>
> User code passed a garbage pointer to the kernel. The kernel didnt like that
> and returned -EFAULT. The exception tracking is just debug stuff while this
> bit of 2.1.x is polished up.
>
> Alan
>
>
> ------------------------------
>
> From: Antonio Villarreal <avilla@dns.gapsnet.com>
> Date: Mon, 18 Nov 1996 13:41:15 -0600 (CST)
> Subject: Configuracion de DNS
>
> Hola a todos !!
>
> Les pido ayuda en lo siguiente :
>
> Tengo un servidor Cyrix 686 con LINUX 2.0.17 con enlace dedicado a
> Internet; necesito registrar en el DNS un dominio de internet; por
> ejemplo : "www.zzz.com.es" pero no dispongo de direcciones IP, de hecho
> esta pagina web estara en Otro servidor que esta en otra red.
>
> Lo que necesito es : Como configuro mi DNS para que una direccion IP
> - -actualmente utilizada por un dominio - apunte a "www.uno.com/nuevo"
> donde nuevo debe tener el nombre "www.nuevo.com" por ejemplo.
>
> MMm, no se si me explique:
>
> Si alguien me puede ayudar...Gracias
>
> - --- GapsNet -------------------------------
> ATTE. Lic. Antonio Villarreal Yáñez.
> Grupo Asociado de Profesionales en Sistemas
> www.gapsnet.com avilla@mail.gapsnet.com
> Tels./Fax: +(525) 524 2965 +(525) 534 3688
> Módem : +(525) 524 9015 México, D.F. 1996
> - -------------------------------------------
>
>
>
> ------------------------------
>
> From: Mailer-Daemon@novell.com
> Date: Sun, 17 Nov 1996 04:53:00 +0000
> Subject: Message status - undeliverable
>
> The message that you sent was undeliverable to the following:
> rganesan@blr.novell.com
>
> Transcript of session follows:
> novidc.blr.novell.com
> 450 MX lookup failure
>
> Possibly truncated original message follows:
>
> Received: from INET-UKB-Message_Server by novell.com
> with Novell_GroupWise; Tue, 12 Nov 1996 17:09:20 +0000
> Received: from nic.funet.fi by ns.Novell.COM (4.1/SMI-4.1)
> id AA07742; Tue, 12 Nov 96 10:08:03 MST
> Received: from vger.rutgers.edu ([128.6.190.2]) by nic.funet.fi with ESMTP id <62600-23826>; Tue, 12 Nov 1996 18:39:00 +0200
> Received: by vger.rutgers.edu id <156338-11039>; Tue, 12 Nov 1996 11:33:25 -0500
> Precedence: bulk
> Message-Id: <s288af40.081@novell.com>
> Date: Sun, 10 Nov 1996 14:00:50 +0000
> From: <linux-kernel@vger.rutgers.edu>
> To: linux-kernel-digest@vger.rutgers.edu,
> owner-linux-kernel-digest@vger.rutgers.edu
> Subject: linux-kernel-digest V1 #598
>
>
> linux-kernel-digest Sunday, 10 November 1996 Volume 01 : Number 598
>
> In this issue:
>
> Re: Tape Problems Redux
> ipv6 structure alignment?
> Re: RANT: serial console
> Re: SMP and Threads
> Re: 2.1.8: Kernel Panic upon IDE Drive Mount
> Re: Kernel Makefiles
> Re: Linux-2.0.25 and 2.1.8
> Re: Linux-2.0.25 and 2.1.8
> Re: modules and 2.1.8
>
> ------------------------------
>
> From: Andreas Schultz <aschultz@hppool.cs.uni-magdeburg.de>
> Date: Mon, 18 Nov 1996 20:59:29 +0100 (MEZ)
> Subject: wait_queue bug ??
>
> Hi,
>
> There seems to be a bug in the wait_queue handling. Imagin the following
> situation:
>
> struct {
> ulong test_value;
> struct wait_queue *my_wait_queue;
> } my_struct;
>
> A "sleep_on(&my_struct.my_wait_queue);" overwrites than the value
> of test_value, causing all kind of havoc.
>
> It seems that the bug has been introduced in 2.0.16. Have a look at
> following pice of code from include/linux/sched.h:
>
> extern inline void __add_wait_queue(struct wait_queue ** p, struct
> wait_queue *wait)
> {
> struct wait_queue *head = *p;
> struct wait_queue *next = WAIT_QUEUE_HEAD(p);
>
> if (head)
> next = head;
> *p = wait;
> wait->next = next;
> }
>
> and from include/linux/wait.h:
>
> #define WAIT_QUEUE_HEAD(x) ((struct wait_queue *)((x)-1))
>
> The assignment of WAIT_QUEUE_HEAD to *next goes to an illegal address !!
>
> Andreas
> - --
> aschultz@cs.uni-magdeburg.de
>
>
> ------------------------------
>
> From: Julian Sassenscheidt <julian@lav.de>
> Date: Mon, 18 Nov 1996 21:25:20 +0100 (MET)
> Subject: Re: Wanted: Logitec Scanner - Any suport
>
> On Mon, 18 Nov 1996 linuxsys@ssg.com wrote:
>
> >
> > Davids Lists writes:
> > > Is there any way to input images from a Logitech Pagescan Color from Linux?
> > [...]
> >
> > Me, too.
> >
> > Rick
> >
>
> Me, too :-)
> Julian Sassenscheidt / Hamburg / Germany / Linux-Kernel 2.0.0
> Internet E-Mail: julian@spitfire.lav.de
> WWW-Homepage: http://www.lavielle.com/~julian/julian.html
> Phone: +49 40 2807089 | Pager (only in .de): 01681-9938572
>
>
>
> ------------------------------
>
> From: "Richard B. Johnson" <root@analogic.com>
> Date: Mon, 18 Nov 1996 17:49:02 -0500 (EST)
> Subject: IP Checksumming
>
> I can't figure out the %)&^$ GNU pseudo assembly that thinks that
> all assembly is written like a 68k (source->dest). However, using
> Intel numonics, the following checksums an IP packet the fastest.
> It can also copy while checksumming.
>
> It minimizes the number of jumps which flush prefetch buffers and
> messes up the speed.
>
> I have watched Linux use different checksum methods throughout the
> years and it seems that things are getting worse.
>
> If someone could convert this to the GNU stuff without breaking the
> logic, I know it would perform MUCH better than the present kernel
> IP checksums even though it uses words for memory access. The present
> checksum routines try several tricks. However, every time a branch
> on compare occurs, there is an enormous penality because the prefetch
> buffer must be flushed. Further, the present routines in ../../asm
> don't take advantage of the Intel architecture. These routines should
> not be 'portable', but should be put into ../../i386/lib to take advantage
> of the string primatives built into the Intel devices. Other machines
> often have other built-in primatives that could help them also.
>
> I have used this in a TCP/IP "stack" for about 4 years here at
> Analogic and I can get over 90 percent of 10-base-t bandwidth with
> a 33MHz machine!
>
> Contrary to the documentation written in /i386/lib/checksum.c, the
> pentium does not suffer from lack of alignment as long as you use
> the internal routines.
>
> I am sure that if someone takes the time to convert this stuff, they
> will be very pleasantly suprised.
>
> ;
> ;
> ; inst dest, source
> ;
> mov esi,offset source_addr ; Get location of string
> IFDEF COPY_WHILE_CHKSUM
> mov edi,offset dest_addr ; Where to copy
> ENDIF
> mov ecx,string_length ; Get string word length
> xor eax,eax ; Zero register, clear CY
> mov edx,eax ; Zero register
> cld ; Forwards
> ;
> l0: lodsw ; Get word, source_addr++
> IFDEF COPY_WHILE_CHKSUM
> stosw ; Put word dest_addr++
> ENDIF
> adc edx,eax ; Sum to accumulator + CY
> loop l0
> ;
> adc edx,0 ; Possible last carry
> IFDEF GONNA_SUM_INTO_WHAT_YOU_CHECKSUMMED
> not edx ; Invert all bits
> ENDIF
> mov eax,edx ; To return in eax
> ;
> ; That's all folks!
> ;
>
>
> ------------------------------
>
> From: Keith Owens <kaos@edison.dialix.com.au>
> Date: Tue, 19 Nov 1996 10:23:47 +1100 (EST)
> Subject: Re: Modules 2.1.8 problem report
>
> On Mon, 18 Nov 1996, Richard Gooch wrote:
> > Hi. I just tried modules 2.1.8, built with the 2.0.0 include files,
> > running on 2.0.22. I can install "sr_mod", but when I try installing
> > "isofs" I get a segmentation fault. Is this a known problem (i.e. is
> > modules 2.1.8 known to not work with 2.0.22)? If not, is there any
> > further information I can supply?
>
> The patch below from Rob Glover <potato@dsnet.com> lets modules-2.1.8 work
> with 2.0 kernels. Warning, this came from a mailing list archive and has
> no tabs in it, I had to patch with --ignore-whitespace.
>
> - --- modules-2.1.8/insmod/load_elf.c~ Mon Nov 4 07:56:58 1996
> +++ modules-2.1.8/insmod/load_elf.c Sun Nov 10 20:47:21 1996
> @@ -366,7 +366,8 @@
> }
>
> /* JEJB: zero the bss (now it's actually allocated) */
> - - memset(secref[bss_seg], 0, bss_size);
> + if (bss_size)
> + memset(secref[bss_seg], 0, bss_size);
>
> for (spnt = sections, i = 0; i < epnt->e_shnum; ++i, ++spnt) {
> #ifdef __i386__
> @@ -622,7 +623,9 @@
> }
>
> loaded = (char *)(((int)loaded + 3) & ~3);
> - - bss_size = loaded - secref[bss_seg];
> + /* yur: don't change bss_size if no bss in the module */
> + if (secref[bss_seg])
> + bss_size = loaded - secref[bss_seg];
> progsize = codesize = loaded - textseg;
> aout_flag = 0; /* i.e.: if it's not a.out, it _has_ to be ELF... */
> if (defsym(strncmp, "_GLOBAL_OFFSET_TABLE_", loaded - textseg, N_BSS | N_EXT, TRANSIENT))
>
>
>
>
> ------------------------------
>
> From: Matthias Urlichs <smurf@smurf.noris.de>
> Date: Tue, 19 Nov 1996 00:57:14 +0100
> Subject: Re: 2.0.0/2.0.25 oopses with buslogic 956C and two 4G seagates ...
>
> In linux.dev.kernel, article <199611171459.OAA10524@oboe.it.uc3m.es>,
> "Peter T. Breuer" <ptb@oboe.it.uc3m.es> writes:
> >
> > This works - i.e. it mounts a separate rootdisk into ram - but it doesn't
> > know how to decomopress the image. So I just decompressed a rootdisk and
> > it goes. I'd like to know the decompress trick ..
> >
> Hmm. IMHO, reading a RAM disk image from a separate floppy is not
> necessary. You can just as easily use the initial RAM disk stuff.
>
> IMHO, it also doesn't make sense to use a Minix file system for booting.
> You do save a few bytes on the boot floppy, but the ext2 overhead seems
> compressible and the Minix file system code then lies around in memory
> doing nothing.
>
> This is the script I'm using to build a complete boot floppy. Actually, a
> bunch of boot floppies. Adapt to taste.
>
>
> #!/bin/sh
>
> PATH=/usr/src/BUILD/bin:/usr/sbin:/sbin:$PATH
>
> usage() {
> cat >&2 <<END
> Usage: $0
> [ -f | -F /dev/fd0 | -I(mage) ]
> [ -s ramdisksize ] [ -S imagesize ]
> [ -l(ilo) ] [ -v Kernelversion ]
> [ -n(et) -d(ebug) -w X (serial wire X, usually 1) ]
> [ -r(un without stop in linuxrc) ]
> kernel (smurf, test, ...)
> END
> exit 1
> }
>
> cd /usr/src || die "No sources"
>
> if test $# -eq 0 ; then usage ; fi
>
> size=4500
> imgsize=1440
> fifo=/tmp/pipe.$$
> fd=
> run=
> net=
> ver=
> debug=
> serial=
> if test -f BUILD/done/kernel:lilo ; then
> wherelilo=done
> else
> wherelilo=legacy
> fi
>
> set -- $(getopt dfF:Ilns:S:rv: $*)
> if test $? != 0
> then
> usage
> fi
> for i
> do
> case "$i"
> in
> -w)
> serial=$2; shift; shift;;
> -d)
> debug=y; shift;;
> -I)
> fd=IMAGE; shift;;
> -F)
> fd=$2; shift; shift;;
> -v)
> ver=$2; shift; shift;;
> -f)
> fd=/dev/fd0; shift;;
> -r)
> run=y; shift;;
> -S)
> imgsize=$2; shift; shift;;
> -s)
> size=$2; shift; shift;;
> -n)
> net="net-"; shift;;
> -l)
> lilo=y; shift;;
> --)
> shift; break;;
> esac
> done
>
> if test -z "$1"; then usage; fi
> sys=$1
> disk=/tmp/disk-$sys
> diskfile=/tmp/diskfile-$sys
>
> set -e
>
> if test -z "$ver" ; then
> rm -f $fifo; mkfifo $fifo
> ( cd /lib/modules-$sys; /bin/ls -r1 | while read a ; do if test -d $a; then echo $a; fi; done > $fifo ) &
> read ver <$fifo ; rm $fifo
> fi
>
> if test "$fd" = "IMAGE" ; then
> fd=/boot-$sys/floppy-$net$ver
> fi
>
> echo 'Unmounting..?'
> umount $disk || true
> rm -rf $disk $diskfile
>
> dd bs=1024 count=$size if=/dev/zero of=$diskfile
> yes y | /sbin/mkfs -t ext2 $diskfile $size
> mkdir $disk
> echo Mounting disk file
> mount -t ext2 -o loop $diskfile $disk
>
> while read a ; do echo /$a; mkdir $disk/$a; done <<END
> bin
> dev
> etc
> etc/terminfo
> lib
> mnt
> mnt1
> mnt2
> mnt3
> proc
> sbin
> usr
> usr/lib
> usr/sbin
> cd
> var
> var/run
> END
>
> if test -n "$net" ; then ## Netz
> cpio -pvd $disk <<END
> /sbin/route
> /sbin/ifconfig
> /usr/sbin/portmap
> /usr/sbin/rpc.mountd
> /usr/sbin/rpc.nfsd
> /lib/libnss_files-1.97.so
> /lib/libnss_files.so.1
> END
> echo 'hosts: files' >$disk/etc/nsswitch.conf
> else
> cpio -pvd $disk <<END
> /sbin/fdisk
> /sbin/fs/mkfs.ext2
> /sbin/fs/fsck.ext2
> /sbin/swapon
> /sbin/mkswap
> /sbin/update
> END
> fi
>
> cpio -pvd $disk <<END
> /bin/ls
> /bin/ln
> /bin/cat
> /bin/cp
> /bin/rm
> /bin/mv
> /bin/mount
> /bin/umount
> /sbin/insmod
> /sbin/ldconfig
> END
>
> find $disk/bin $disk/sbin -type f -print|xargs strip
>
> cpio -pvd $disk <<END
> /dev/zero
> /dev/null
> /dev/tty
> /dev/tty1
> /dev/ttyS0
> /dev/ttyS1
> /dev/sda
> /dev/sda1
> /dev/sda2
> /dev/sda3
> /dev/sda4
> /dev/sda5
> /dev/sda6
> /dev/sda7
> /dev/sda8
> /dev/sdb
> /dev/sdb1
> /dev/sdb2
> /dev/sdb3
> /dev/sdb4
> /dev/sdb5
> /dev/sdb6
> /dev/sdb7
> /dev/sdb8
> /dev/sdc
> /dev/sdc1
> /dev/sdc2
> /dev/sdc3
> /dev/sdc4
> /dev/sdc5
> /dev/sdc6
> /dev/sdc7
> /dev/sdc8
> /dev/sdd
> /dev/sdd1
> /dev/sdd2
> /dev/sdd3
> /dev/sdd4
> /dev/sdd5
> /dev/sdd6
> /dev/sdd7
> /dev/sdd8
> /dev/fd0
> /dev/fd1
> /dev/scd0
> /etc/fstab
> END
>
> mkdir -p $disk/etc/terminfo/l
> cp -v /usr/lib/terminfo/l/linux $disk/etc/terminfo/l
>
> (
> (
> if test -f BUILD/out/gnu:libc ; then
> cat BUILD/out/gnu:libc
> else
> cat <<END
> /lib/ld.so.1
> /lib/libc-1.97.so
> /lib/libc.so.6
> END
> fi
> cat BUILD/out/gnu:readline
> cat BUILD/out/lib:ncurses
> cat BUILD/out/lib:shadow
> ) | grep ^/lib/ |
> while read a ; do
> if test -L $a ; then
> echo $a
> elif test -f $a ; then
> b=/tmp/$$.$(basename $a)
> cp -a $a $b
> ls -l $b >&2
> strip --strip-debug $b || true
> ls -l $b >&2
> cp -a $b $disk/$a
> rm $b
> else
> echo $a
> fi
>
> done
> grep ^/bin/ < BUILD/out/gnu:bash
>
> ) | cpio -pvd $disk
>
> cat <<END > $disk/etc/ld.so.conf
> /lib
> /usr/lib
> /cd/lib
> /cd/usr/lib
> /cd/usr/X11R6/lib
> /mnt/lib
> /mnt/usr/lib
> END
>
> sync
> echo ldconfig ...
> LD_PRELOAD="" chroot $disk /sbin/ldconfig -v
>
> mkdir $disk/modules
>
> if test -n "$net" ; then ## Netz
> while read a ; do
> if test -f /lib/modules-$sys/$ver/$a ; then
> b=/tmp/$$.$(basename $a)
> cp -a /lib/modules-$sys/$ver/$a $b
> ls -l $b >&2
> strip --strip-debug $b || true
> ls -l $b >&2
> cp -a $b $disk/modules/$(basename $a)
> rm $b
> fi
> done <<END
> net/3c503.o
> net/3c507.o
> net/3c509.o
> net/3c59x.o
> net/8390.o
> net/eepro.o
> net/eexpress.o
> net/ewrk3.o
> net/ne.o
> net/wd.o
> net/de4x5.o
> net/depca.o
> net/smc-ultra.o
> net/smc9194.o
> net/tulip.o
> fs/nfs.o
> block/floppy.o
> END
>
> else ## kein Netz
>
> while read a ; do cp -v /lib/modules-$sys/$ver/$a $disk/modules || true; done <<END
> scsi/scsi_mod.o
> scsi/aha1542.o
> scsi/53c7,8xx.o
> scsi/aha152x.o
> scsi/aic7xxx.o
> scsi/sd_mod.o
> scsi/sr_mod.o
> fs/isofs.o
> block/floppy.o
> fs/binfmt_aout.o
> END
> fi
>
> ln -s /proc/mounts $disk/var/run/mtab
>
> echo ">> $disk/linuxrc"
> cat <<END >$disk/linuxrc
> #!/bin/sh
>
> set -xv
> PATH=/bin:/sbin
> END
>
> if test -z "$serial" ; then
> echo "exec </dev/tty1 >/dev/tty1 2>&1" >>$disk/linuxrc
> else
> echo "exec </dev/ttyS$serial >/dev/ttyS$serial 2>&1" >>$disk/linuxrc
> fi
>
> cat <<END >>$disk/linuxrc
> echo "Dies ist die Bootdiskette für $sys..."
> > /etc/mtab
>
> END
>
> if test -n "$net" ; then
> cp /usr/src/BUILD/bin/doinstall.1 $disk/bin/install
> cat <<END >>$disk/linuxrc
> insmod /modules/8390.o
> insmod /modules/ne.o io=0x300
> insmod /modules/wd.o io=0x240
> insmod /modules/nfs.o
> END
>
> else ## kein Netz
>
> cat <<END >>$disk/linuxrc
> insmod /modules/scsi_mod.o
> insmod /modules/53c7,8xx.o
> insmod /modules/aha1542.o
> insmod /modules/aic7xxx.o
> insmod /modules/aha152x.o
> insmod /modules/sd_mod.o
> insmod /modules/floppy.o
> insmod /modules/binfmt_aout.o
> END
> fi
>
> cat <<END >>$disk/linuxrc
>
> mount -n /proc
> echo 0x801 >/proc/sys/kernel/real-root-dev
> END
> if test -z "$run" ; then
> cat <<END >>$disk/linuxrc
> /bin/sh -i
> END
> fi
> cat <<END >>$disk/linuxrc
> umount -n /proc
>
> END
>
> chmod +x $disk/linuxrc
>
>
> du -s $disk/.
> if test -n "$debug" ; then
> echo "disk ready for compressing."
> ( cd $disk; /bin/sh -i )
> fi
>
> echo Unmounting disk file
> umount $disk
> sync
> if test -n "$fd" ; then
> dest=/tmp/cdisk.$$
> else
> dest=/boot-$sys/disk-$net$ver
> fi
>
> echo "Compressing $diskfile ($disk) to $dest"
> gzip < $diskfile > $dest &
>
> if test -n "$fd" ; then
>
> sleep 1
> if test -b "$fd" ; then
> echo /sbin/fs/mkfs.ext2 -i 50000 $fd $imgsize
> /sbin/fs/mkfs.ext2 -i 50000 $fd $imgsize
> mount -t ext2 $fd $disk
> else
> dd bs=1024 count=$imgsize if=/dev/zero of=$fd
> echo /sbin/fs/mkfs.ext2 -i 50000 $diskfile $imgsize
> yes y | /sbin/fs/mkfs.ext2 -i 50000 $diskfile $imgsize
> mount -t ext2 -o loop $fd $disk
> fi
>
>
> while read a ; do echo /$a; mkdir $disk/$a; done <<END
> boot
> dev
> etc
> END
>
> (
> grep ^/boot/ < BUILD/out/kernel:lilo | fgrep -v .old
> cat <<END
> /dev/null
> /dev/fd0
> END
> ) | cpio -pvd $disk
>
> echo $disk/boot/message
> cat <<END >$disk/boot/message
> Dies ist die Bootfloppy fuer $sys, Kernel $ver.
>
> Erstellt via Buildsystem: $(date)
>
> END
> if test -n "$net" ; then
> echo "Konfiguration: NETZ."
> else
> echo "Konfiguration: STANDARD."
> fi >>$disk/boot/message
>
> echo $disk/etc/lilo.conf
> cat <<END >$disk/etc/lilo.conf
> boot = /dev/fd0
> install = /boot/boot.b
> compact
> delay = 10
> read-only
> END
>
> if test -n "$serial" ; then
> cat <<END >>$disk/etc/lilo.conf
> append="ramdisk=$size console=$serial,9600 reboot=hard,bios"
> serial = 1,9600n8
> END
> else
> cat <<END >>$disk/etc/lilo.conf
> append="ramdisk=$size reboot=hard,bios"
> END
> fi
> cat <<END >>$disk/etc/lilo.conf
> root = /dev/fd0
> message = /boot/message
> ### IMAGES ###
> image = /boot/linux-$ver
> initrd = /boot/disk-$net$ver
> label = $ver
> END
>
> ls -l /boot-$sys/linux-$ver
> cp /boot-$sys/linux-$ver $disk/boot/linux-$ver
> wait ## RAM-Disk wird evtl. noch gepackt...
> ls -l $dest
> cp $dest $disk/boot/disk-$net$ver
> echo Running LILO...
> lilo -r $disk
>
> echo Unmount real disk
> umount $disk
>
> else # keine Bootfloppy
>
> echo Compressing the boot disk...
> wait
>
> fi
>
>
> if test -n "$lilo" ; then
> if test ! -f /boot/message ; then
> cat <<END
> Dies ist die Bootplatte für $sys, Kernel $ver.
>
> Erstellt via Buildsystem: $(date)
> Die nd-*-Kernels booten ohne initrd.
>
> END
> fi
> if test -z "$net" -a /boot/disk-$ver -ef /boot-$sys/disk-$ver ; then
> echo " *** LILO kann ich hier nicht für $sys starten -- lebensmüde??? *** "
> else
> /sbin/mklilo
> fi
> fi
>
> if test -n "$fd" ; then
> rm $dest
> fi
> rm $diskfile
> rmdir $disk
>
> - --
> Matthias Urlichs \ noris network GmbH / Xlink-POP Nürnberg
> Schleiermacherstraße 12 \ Linux+Internet / EMail: urlichs@noris.de
> 90491 Nürnberg (Germany) \ Consulting+Programming+Networking+etc'ing
> PGP: 1024/4F578875 1B 89 E2 1C 43 EA 80 44 15 D2 29 CF C6 C7 E0 DE
> Click <A HREF="http://info.noris.de/~smurf/finger">here</A>. 42
>
> ------------------------------
>
> From: kris@koehntopp.de (Kristian =?ISO-8859-1?Q?K=F6hntopp?=)
> Date: Mon, 18 Nov 96 18:49 MET
> Subject: Re: Glitch in sys_chroot()
>
> In linux.dev.kernel you write:
> >Just to show exactly HOW stupid this whole discussion is, here's inane
> >argument #1: "The suid/sgid bits are the main source of security holes, so
> >why don't we disable those altogether, and then we'll have a secure
> >system".
>
> Windows NT does that. :-)
>
> Kristian
>
>
> ------------------------------
>
> From: kris@koehntopp.de (Kristian =?ISO-8859-1?Q?K=F6hntopp?=)
> Date: Mon, 18 Nov 96 18:54 MET
> Subject: Re: Linux & ECC memory
>
> In linux.dev.kernel you write:
> >To my knowledge, there are not any "modern" computers that handle memory
> >errors this well.
>
> There was an Alpha 3000/500 at one place where I used to work.
> The machine had 160 MB of memory and regularly reported ECC
> corrected memory errors in the syslog without crashing.
>
> Kristian
>
>
> ------------------------------
>
> From: Bernhard Rosenkraenzer <linux@startrek.in-trier.de>
> Date: Tue, 19 Nov 1996 00:22:36 +0100 (MET)
> Subject: Re: Message status - undeliverable
>
> On Sun, 17 Nov 1996 Mailer-Daemon@novell.com wrote:
>
> > The message that you sent was undeliverable to the following:
> > rganesan@blr.novell.com
> >
> > Transcript of session follows:
> > novidc.blr.novell.com
> > 450 MX lookup failure
>
> What's that? Majordomo is incapable of handling Mailer-Daemon messages if
> the sender isn't capitalized? Funny...
>
> LLaP
> bero
>
>
>
>
> ------------------------------
>
> From: "Marko Siladin" <msiladin@athos.mas.vcu.edu>
> Date: Mon, 18 Nov 1996 21:01:21 -0500 (EST)
> Subject: Re: Printer on fire - I feel like an idiot
>
> >
> > In article <9611172030.AA16550@athos.mas.vcu.edu>,
> > "Marko Siladin" <msiladin@athos.mas.vcu.edu> writes:
> > >
> > >Sorry guys I really must appolagize to post something to this mailinglist
> > >without enough investigation. Anyway the reason I got that strange kernel
> > >error message was that the "Pause" button on my printer was pressed.
> > >The front of my printer is hidden under my desk so I don't see it (
> > >it's an Epson LQ-570 btw). . Anyway to cut the story short pressing
> > >the pause butten solved the problem. Maybe there should be some
> > >better messageing - like not on-line?? Sorry again for
> > >the unnecessary posting.
> > >Regards and happy linuxing
> > >--
> >
> > `lp0 on fire' is a age-old UNIX joke. It was in the earliest kernels
> > of UNIX. Linux is just trying to conform ;)
> >
> > Seriously, it's for unknown errors - off line is reported when the
> > printer is off-line, out of paper is reported when the printer is out
> > of paper, on fire is reported when the kernel doesn't know.
> >
> > See .../linux/drivers/char/lp.c at around line 250 (assuming 2.0.24;
> > I expect it's about the same for other versions but I don't know)
> >
> But the problem is that my printer was - off-line and that the driver
> did not detect that. Now I understand that there are many printers out
> there and that it is not easy to write an universal driver. But the
> point is that lp did not recognize that my printer was off-line.
> The pause button on the printer is the closest thing I
> can see to an off-line (except the power switch :) )
>
> - --
> ...Marko
> - ------------------------///////////-\\\\\\\\\\\--------------------------
> (O) ^ ^ (O)
> Marko Siladin | | | VCU, Dept. of Math. Science
> msiladin@athos.mas.vcu.edu \ / Division of Computer Science
> http://www.mas.vcu.edu/grad/marko/home.html
> - ------------------------\\\\\\\\\\\-///////////--------------------------
>
> ------------------------------
>
> From: Neil Moore <amethyst@pcc-uky.campus.mci.net>
> Date: Mon, 18 Nov 1996 21:38:16 -0500
> Subject: Re: Possible /etc/hosts parsing bug?
>
> >
> >
> > I have found something that may be a small parsing bug, but may
> > also be within the specs of its functionality... In my hosts file
> > I had a few entries:
> >
> > 172.16.2.1 Atomic.shocking.com
> > 172.16.2.2 Nuclear.shocking.com
> > 172.16.2.3 Fusion.shocking.com
> >
> > In an effort to line everything up and make it look pretty I modified the
> > previous lines to the following:
> >
> > 172.016.002.001 Atomic.shocking.com
> > 172.016.002.002 Nuclear.shocking.com
> > 172.016.002.003 Fusion.shocking.com
> >
> > Numerically, these have the same values, but when I tried to ping fusion,
> > the IP that it was using was 172.14.2.3. When the extra '0's were deleted
> > ping worked fine. Is this within the operating specs? Just curious,
>
> Any number beginning with `0' is usually considered to be in octal.
> 016(base 8)==14(base 10), hence the problems you were experiencing.
>
> - --
> Version: 3.12
> GCS/M/L d- s-:+ a--- C+++(++)>$ UL+(++)>++++$ P+++ L+++>++++$ E++ W-(--)
> N++ o-- K-- w--- O- M-- V-- PS+++? PE Y+ PGP-- t+* 5- X R tv--? b+>+++ DI
> D--- G e-(*)>++++ h r++>+++ y?
>
> ------------------------------
>
> From: Ulrich Drepper <drepper@myware.rz.uni-karlsruhe.de>
> Date: 19 Nov 1996 04:56:43 +0100
> Subject: real POSIX.1b semaphores
>
> Hi,
>
> I thought a bit about real POSIX.1b semaphores. Since the defined
> interface allows global semaphores we clearly need kernel support.
>
> For the sake of speed we should try to be able to handle as much
> as possible on user level. The both kinds a POSIX semaphore can
> be reduced to one form. I thought about the following but please
> don't take this as a well-thought design. I have not much experience
> with kernel programming.
>
> - - reserve two pages in the mmap area of each process. The first page
> is for global locks, ie.e., the very same page is shared by all
> processes. The second page is shared between all threads of a
> process (i.e., clone needs another flag).
>
> The pages should be write protected.
>
> - - each semaphore uses sizeof(unsigned int) bytes, normally 4.
>
> - - one possibility to create a semaphore is to call sem_init(). This
> will have to be a syscall. It returns a pointer to an address in
> either of the semaphore spaces, depending on the value of the PSHARED
> argument. The initial value is given by the third parameter.
>
> - - removing the semaphore need not be explained. There must in any case
> be an allocation bitmap or something like this. This function again
> needs a syscall.
>
> - - Creating a semaphore using sem_open() requires to have another resource,
> a pseudo file system where the names are allocated. The standard leaves
> it open whether this names are visible in the normal filesystem but I
> think it is very useful.
>
> Would it be difficult to extend the proc/ filesystem to dynamically
> create a hierachy of dirs for the semaphores?
>
> In any case each known name must reference an address in the global
> semaphore page. Using sem_open() with an unknown semaphore and O_CREAT
> will allocate a new semaphore, just like sem_init(). The return value
> of this function is again a pointer and so all the other sem_*()
> functions can handle semaphores created by sem_init() and sem_open()
> in the same way.
>
> - - calling sem_close() will of course decrement the reference count, but
> not from the pseudo-filesystem if it is zero. There is another function
> sem_unlink() which will remove the semaphore.
> This again requires a syscall or two.
>
> - - the function sem_getvalue() is implemented trivially by reading the
> addressed memory location of the semaphore. No kernel action is
> required.
>
> - - the function sem_wait(), sem_trywait(), and sem_post() will write to
> the memory for the semaphore and cause a bus error. Now the action
> can be performed be the kernel.
>
> I don't know whether it is possible to work with one single memory
> location for the action and decode the instruction or (unlikely).
> Perhaps using two or three word for each semaphores is necessary.
> So it could be decided based on the address chosen. It would be up
> to the library to choose the correct location.
>
>
> Would this be reasonable? Does anybody plan to do something like
> this? We really should have this soon now that multi-threading
> only has limits in the kernel. The libpthread and the libc (=glibc)
> are ready.
>
> If anybody has interest I could provide the informations from
> the standard. Thanks to RedHat I now have the full POSIX.1 standard.
>
>
> (PS: A second *very* important task would be to implement CLONE_PID.)
>
> Thanks,
>
> - -- Uli
> - --------------. drepper@cygnus.com ,-. Rubensstrasse 5
> Ulrich Drepper \ ,--------------------' \ 76149 Karlsruhe/Germany
> Cygnus Support `--' drepper@gnu.ai.mit.edu `------------------------
>
> ------------------------------
>
> From: andersee@et.byu.edu (Erik B. Andersen)
> Date: Mon, 18 Nov 1996 13:56:14 -0700 (MST)
> Subject: Anybody having IDE-CD problems with 2.1.10?
>
> In Linux kernel 2.1.9 the ide-cd driver underwent major changes. I have
> had a couple of reports of the cdrom door remaining locked on boot until IO
> occurs, at which point the drive door becomes unlocked. This problem may
> (or may not) be a simple hardware misconfiguration due to the removal of a
> jumper on the drive.
>
> Could people test out the ide-cd driver for me under 2.1.10 and let me know
> of any problems (or successes). Do not test things under 2.1.9 since there
> is a ide-cd module bug. Thanks for your help.
>
> -Erik
>
> -- The Linux Kernel ide-cd guy --
>
> - --
> Erik B. Andersen Web: http://www.et.byu.edu/~andersee/
> 2485 South State St. email: andersee@et.byu.edu or andersee@debian.org
> Springville, Ut 84663 phone: (801) 489-1231
> - --This message was written using 73% post-consumer electrons--
>
> ------------------------------
>
> From: G Sumner Hayes <sumner+@cmu.edu>
> Date: Mon, 18 Nov 1996 15:54:40 -0500 (EST)
> Subject: Re: Configuracion de DNS
>
> [This is not a kernel question; you should direct questions to the
> Usenet group comp.os.linux.setup.]
>
> [Este no es una pregunta del kernel; debe preguntar en el grupo de
> Usenet comp.os.linux.setup. No he hablado espan~ol desde hace cuatro
> an~os; ojala que mi espan~ol todavia este bastante bien que vd. puede
> comprenderlo. Por favor, responda por e-mail a sumner@cmu.edu y no al
> Linux Kernel Mailing List.]
>
> Antonio Villarreal <avilla@dns.gapsnet.com> writes:
> > Hola a todos !!
> >
> > Les pido ayuda en lo siguiente :
> >
> > Tengo un servidor Cyrix 686 con LINUX 2.0.17 con enlace dedicado a
> > Internet; necesito registrar en el DNS un dominio de internet; por
> > ejemplo : "www.zzz.com.es" pero no dispongo de direcciones IP, de hecho
> > esta pagina web estara en Otro servidor que esta en otra red.
> >
> > Lo que necesito es : Como configuro mi DNS para que una direccion IP
> > -actualmente utilizada por un dominio - apunte a "www.uno.com/nuevo"
> > donde nuevo debe tener el nombre "www.nuevo.com" por ejemplo.
> >
>
> ?Solamente tienes que cambiar el direccion para WWW o para todos los
> acciones del red? Si el primer, puede usar la abilidad de apache a
> usar servidores virtuales(??). Si el segundo, no se la solucion pero
> es posible que puede usar "IP forwarding", "IP aliasing", o "IP
> masquerading"; ?puede explicar exactamente lo que quieres hacer?
>
> Lo siento si he matado su lengua en esta carta.
>
> Cordialmente,
>
> Sumner
>
> - --
> Respond by post or email, but please don't CC: postings to me; my mailbox
> is already quite full.
>
> ------------------------------
>
> From: Richard Henderson <richard@atheist.tamu.edu>
> Date: Mon, 18 Nov 1996 14:46:40 -0600 (CST)
> Subject: Re: Can't compile 2.1.7 plus
>
> > The kernel was compiled on a 2.1.6 machine, with
> > gcc 2.7.2, as 2.7 (BFD 2.7.0.3) and ld 2.7 (BFD 2.7.03).
>
> You've got an old version of ld hanging out somewhere on your
> system that is being found before the 2.7.0.3 version.
>
>
> r~
>
> ------------------------------
>
> From: Hubert Mantel <mantel@suse.de>
> Date: Mon, 18 Nov 1996 22:32:50 +0100 (MET)
> Subject: EIDE more reliable than SCSI?
>
> Hello,
>
> we used the following system for writing CDs:
>
> P100 with 32MB RAM, an EIDE hard drive and a 4x speed Yamaha CD-ROM writer
> with 8MB connected to a NCR53C810 SCSI adaptor. The system was very
> stable. We could compile a kernel, transfer another iso9660-image over the
> 100MB net and write a CD at 4x speed without any problems. All
> simultanously.
>
> Then the harddisk died and we modified the system. Now it's a P133 with
> 32MB, and we replaced the disk with a SCSI disk connected to the same NCR
> controller to which the writer is connected. Lots of problems when writing
> CDs. So we inserted a second SCSI Adapter (DPT) and attached the hard disk
> to it. But still we may not "touch" the machine whilst writing a CD. There
> is only one device attached to every of the both SCSI adaptors! Besides of
> that, the system is absolutely reliable and rock solid even under highest
> loads.
>
> Why is writing from an EIDE disk to the SCSI writer so much more reliable
> than writing from a SCSI disk to the writer? Any hints?
>
> Hubert mantel@suse.de
>
> Oh, almost forgot: Kernel is 2.0.25 of course ;-) Same software on both
> systems.
>
>
> ------------------------------
>
> From: chris@stallion.oz.au
> Date: 19 Nov 1996 08:10:34 +1000
> Subject: Re: Problem compiling 2.0.25
>
> - -----BEGIN PGP SIGNED MESSAGE-----
>
> "Jaime G. Ghirelli" <jaime@ba.net> moved upon the face of the 'Net and spake thusly:
>
> > make[1]: Entering directory `/usr/src/linux-2.0.25/arch/i386/kernel'
> > gcc -D__KERNEL__ -I/usr/src/linux-2.0.25/include -Wall
> > -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe
> > -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -c
> > -o time.o time.c
> > {standard input}: Assembler messages:
> > {standard input}:768: Error: no such 386 instruction: `rdmsr'
> > {standard input}:770: Error: no such 386 instruction: `wrmsr'
> > make[1]: *** [time.o] Error 1
> > make[1]: Leaving directory `/usr/src/linux-2.0.25/arch/i386/kernel'
> > make: *** [linuxsubdirs] Error 2
> >
> >
> I got this too on my 486. For a quick fix, go into menuconfig and
> turn on character devices/advanced-power-management.
>
> <digression>
> To those who have said "upgrade your binutils":
>
> These instructions are pentium only. IMHO this is NOT a consequence
> of old binutils, but a bug in the code---this code should be inside
> #ifdef CONFIG_M586.
> </digression>
>
> Works for me.
>
> cjb.
> - - --
> __
> / \
> / \
> /MORONS\
> / \
> \ next /
> \ 15 /
> \msgs/
> \__/
> ||
> ||
> ||chris@stallion.oz.au
> One more infobahn cliche couldn't hurt...
>
>
> - -----BEGIN PGP SIGNATURE-----
> Version: 2.6.2i
> Comment: Send mail with 'Subject: sendpgpkey' for my public key.
>
> iQCVAwUBMpDe2JyEgW3JSqnhAQG4eAP/SRa5a+hzNg07iEXu8QmCxybPC3jwm6pB
> nfkAd5fM3RMTeRk10V9V4ttDf2R6Um9MV2O71kkJUB4suKw0TOTWw6UkilK81RYw
> ANcsB3bunVR0eZZqruGliFEeT6LV7ZNNfKW5qZabEERW7EZjUtmdV2GGhSBNRzKW
> UDAnX6uVBmA=
> =G9v+
> - -----END PGP SIGNATURE-----
>
> ------------------------------
>
> From: Mark Hemment <markhe@nextd.demon.co.uk>
> Date: Mon, 18 Nov 1996 21:46:19 +0000 (GMT)
> Subject: FYI: I2O Architecture
>
> I haven't seen anything on this mailing list about I2O, so I thought I'd
> drop a pointer.
> The I20 architecture is suppose to allow the distribution of I/O functions
> over multiple processors. A lot of major companies appear to be behind this.
> Unfortunately, to receive the spec. you need to sign a NDA (no idea how
> restricting it is).
> Have a look at;
> http://www.i2osig.org/
>
> markhe
>
> ------------------------------
>
> From: Agus Budy Wuysang <fswmis@rad.net.id>
> Date: Tue, 19 Nov 1996 08:08:29 +0700
> Subject: Cyrix 6x86
>
> I have a Cyrix 6x86 P166+ overclocked to P200+ :)
>
> Now, should I recompile my kernel (and/or other programs) with
> 486, Pentium, or PPro optimization?
>
> - --
> +---| Netscape Navigator 3.x |---| Powered by Linux 2.0.x |---+
> |/v\ Agus Budy Wuysang MIS Department |
> | | Phone: +62-21-344-1316 x317 GSM: +62-816-91-7066 |
> +------| http://www.rad.net.id/users/personal/s/supes |-------+
>
> ------------------------------
>
> From: "David S. Miller" <davem@jenolan.rutgers.edu>
> Date: Mon, 18 Nov 1996 23:23:31 -0500
> Subject: Re: real POSIX.1b semaphores
>
> From: Ulrich Drepper <drepper@myware.rz.uni-karlsruhe.de>
> Date: 19 Nov 1996 04:56:43 +0100
>
> (PS: A second *very* important task would be to implement CLONE_PID.)
>
> In the kernel of libc? Last I checked the CLONE_PID flag exists in
> the kernel and works just fine.
>
> - --------------------------------------------////
> Yow! 10.49 MB/s remote host TCP bandwidth ////
> over 100Mb/s ethernet. Beat that! ////
> - -----------------------------------------////__________ o
> David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ ><
>
> ------------------------------
>
> From: jrm@poboxes.com
> Date: Mon, 18 Nov 1996 20:10:16 -0800 (PST)
> Subject: 2.1.x doesn't boot
>
> 2.0.x kernels work great(i'm running 2.0.25) but with any of the
> 2.1.x kernels( I've tried up through 2.0.10), I only get the
> following:
>
> Uncompressing Linux...Done.
> Now booting the Kernel
>
>
> At this point my computer freezes and I have to use the reset button.
> What did I forget to do?
>
> 486 PCI motherboard with Pentium OD 83, 16MB RAM, and 2 IDE drives
>
> Gnu C: 2.7.2.1
> Binutils: 2.7.0.3
> Libc: 5.4.11
> libc++: 2.7.2.1
>
>
> Jon McPhillips
>
> ------------------------------
>
> From: Ulrich Drepper <drepper@myware.rz.uni-karlsruhe.de>
> Date: 19 Nov 1996 05:32:48 +0100
> Subject: Re: real POSIX.1b semaphores
>
> "David S. Miller" <davem@jenolan.rutgers.edu> writes:
>
> > In the kernel of libc? Last I checked the CLONE_PID flag exists in
> > the kernel and works just fine.
>
> Oops, really? If yes, Xavier do you have plans to support this?
>
> - -- Uli
> - --------------. drepper@cygnus.com ,-. Rubensstrasse 5
> Ulrich Drepper \ ,--------------------' \ 76149 Karlsruhe/Germany
> Cygnus Support `--' drepper@gnu.ai.mit.edu `------------------------
>
> ------------------------------
>
> From: "David S. Miller" <davem@jenolan.rutgers.edu>
> Date: Mon, 18 Nov 1996 23:38:18 -0500
> Subject: Re: real POSIX.1b semaphores
>
> From: Ulrich Drepper <drepper@myware.rz.uni-karlsruhe.de>
> Date: 19 Nov 1996 05:32:48 +0100
>
> Oops, really? If yes, Xavier do you have plans to support this?
>
> Yes I just checked, and it is there, from kernel/fork.c:
>
> static int get_pid(unsigned long flags)
> {
> struct task_struct *p;
>
> if (flags & CLONE_PID)
> return current->pid;
>
> [ ... ]
> }
>
> - --------------------------------------------////
> Yow! 10.49 MB/s remote host TCP bandwidth ////
> over 100Mb/s ethernet. Beat that! ////
> - -----------------------------------------////__________ o
> David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ ><
>
> ------------------------------
>
> From: "David S. Miller" <davem@jenolan.rutgers.edu>
> Date: Mon, 18 Nov 1996 23:54:09 -0500
> Subject: Re: real POSIX.1b semaphores
>
> From: Ulrich Drepper <drepper@myware.rz.uni-karlsruhe.de>
> Date: 19 Nov 1996 05:44:58 +0100
>
> OK, and does signal delivery works as expected? I.e., can one
> thread send a signal to another in the same process? I don't know
> much about this but haven't found a sign of a thread ID.
>
> Hmmm, maybe it does not act as expected. And you are correct that a
> thread_id mechanism is not there.
>
> Linus spoke some time ago on this on some linux-kernel thread.
> Basically his consensus was that adding a thread_id that was seperate
> from the normal pid was asking for trouble and a stupid idea.
>
> He instead postulated an idea of encoding the thread_id within the
> pid itself, using the high order bits of the pid value or something
> similar. The nice results of this are that nothing breaks, like
> /proc/pid etc.
>
> - --------------------------------------------////
> Yow! 10.49 MB/s remote host TCP bandwidth ////
> over 100Mb/s ethernet. Beat that! ////
> - -----------------------------------------////__________ o
> David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ ><
>
> ------------------------------
>
> From: Ulrich Drepper <drepper@myware.rz.uni-karlsruhe.de>
> Date: 19 Nov 1996 05:44:58 +0100
> Subject: Re: real POSIX.1b semaphores
>
> "David S. Miller" <davem@jenolan.rutgers.edu> writes:
>
> > Yes I just checked, and it is there, from kernel/fork.c:
>
> OK, and does signal delivery works as expected? I.e., can one
> thread send a signal to another in the same process? I don't know
> much about this but haven't found a sign of a thread ID.
>
> - -- Uli
> - --------------. drepper@cygnus.com ,-. Rubensstrasse 5
> Ulrich Drepper \ ,--------------------' \ 76149 Karlsruhe/Germany
> Cygnus Support `--' drepper@gnu.ai.mit.edu `------------------------
>
> ------------------------------
>
> From: Mike Wangsmo <wanger@fubar.cs.montana.edu>
> Date: Mon, 18 Nov 1996 22:50:54 -0700 (MST)
> Subject: Re: Anybody having IDE-CD problems with 2.1.10?
>
> On Mon, 18 Nov 1996, Erik B. Andersen wrote:
>
> > Could people test out the ide-cd driver for me under 2.1.10 and let me know
> > of any problems (or successes). Do not test things under 2.1.9 since there
> > is a ide-cd module bug. Thanks for your help.
>
> Yes, I can confirm that is exactly what happens. From a fresh boot, the
> cdrom door remains "frozen" until the drive is mounted or otherwise
> accessed after which the door operates normally.
>
> Mike
> _______________________________________________________________________
> Mike Wangsmo, Graduate Student wanger@fubar.cs.montana.edu
> Montana State University http://www.cs.montana.edu/~wanger
> 602 Peter Koch (406) 586-0690
> Bozeman, MT 59715
>
> "May the Force be with you, always"
>
>
> ------------------------------
>
> From: mjacob@feral.com (Matthew Jacob)
> Date: Mon, 18 Nov 96 22:05:52 PST
> Subject: Re: FYI: I2O Architecture
>
> >I haven't seen anything on this mailing list about I2O, so I thought I'd
> >drop a pointer.
> >The I20 architecture is suppose to allow the distribution of I/O functions
> >over multiple processors. A lot of major companies appear to be behind this.
> >Unfortunately, to receive the spec. you need to sign a NDA (no idea how
> >restricting it is).
>
> And pony up 250$.
>
> Serious technology dope smokers funded by their corporate handlers
> only, please. :-)
>
> The backgrounder page makes I2O look like quite a lot of similar
> efforts that I've seen over the last N years- perhaps with some
> better aspects than others. Such efforts have ranged from the
> DDI/DKI to OBIOS (open BIOS specification) to CDDE (common
> device driver environment) to (and this I kind of am tickled by)
> someone saying that SunLABS has done a Java Class library for
> writing device drivers.
>
> What will be more interesting is what the producers of hardware
> will go with- they're the ones who will probably drive the standards-
> not the other way around. Having been part of efforts in the past to come
> up with grand scheme solutions, I am somewhat doubtful of the ability
> of hierarchical software models for abstracting hardware, no matter how
> well designed and enticingly offered, to ultimately win.
>
> Note, btw, the inbound/outbound message queues- I suspect that DEC
> might have offered that one (it fits *very* nicely with the I/O hose
> stuff they have for their high end machines).
>
>
> ------------------------------
>
> From: Trevor Johnson <trevor@jpj.org>
> Date: Mon, 18 Nov 1996 22:14:16 -0800 (PST)
> Subject: trouble with modules in 2.1.11
>
> I'm unable to use modules under Linux 2.1.11. They worked fine with
> 2.1.10.
>
> # depmod -a
>
> *** Unresolved symbols in module /lib/modules/2.1.11/net/3c509.o
> *** Unresolved symbols in module /lib/modules/2.1.11/net/8390.o
> *** Unresolved symbols in module /lib/modules/2.1.11/net/eexpress.o
> *** Unresolved symbols in module /lib/modules/2.1.11/net/ppp.o
>
> # insmod -V
> Version 2.1.8
>
> # insmod ppp
> slhc_free: wrong version or undefined
> slhc_init: wrong version or undefined
> slhc_toss: wrong version or undefined
> skb_put_errstr: wrong version or undefined
> slhc_uncompress: wrong version or undefined
> slhc_remember: wrong version or undefined
> slhc_compress: wrong version or undefined
> Loading failed! The module symbols (from linux-2.1.11) don't match your linux-2.1.11
>
> # insmod 3c509
> skb_put_errstr: wrong version or undefined
> Loading failed! The module symbols (from linux-2.1.11) don't match your linux-2.1.11
>
> # insmod sound
> init_module: Bad font file format
>
> # insmod floppy
> init_module: File locking deadlock error
>
> Here's the kernel configuration I'm using:
>
> CONFIG_EXPERIMENTAL=y
> CONFIG_MODULES=y
> CONFIG_MODVERSIONS=y
> CONFIG_KERNELD=y
> CONFIG_NET=y
> CONFIG_SYSVIPC=y
> CONFIG_BINFMT_ELF=y
> CONFIG_M486=y
> CONFIG_VIDEO_SELECT=y
> CONFIG_BLK_DEV_FD=m
> CONFIG_BLK_DEV_IDE=y
> CONFIG_BLK_DEV_IDEDISK=y
> CONFIG_BLK_DEV_LOOP=m
> CONFIG_BLK_DEV_RAM=m
> CONFIG_INET=y
> CONFIG_IP_NOSR=y
> CONFIG_SKB_LARGE=y
> CONFIG_SCSI=m
> CONFIG_BLK_DEV_SD=m
> CONFIG_CHR_DEV_ST=m
> CONFIG_BLK_DEV_SR=m
> CONFIG_BLK_DEV_SR_VENDOR=y
> CONFIG_CHR_DEV_SG=m
> CONFIG_SCSI_CONSTANTS=y
> CONFIG_SCSI_AHA1542=m
> CONFIG_SCSI_AIC7XXX=m
> CONFIG_SCSI_BUSLOGIC=m
> CONFIG_NETDEVICES=y
> CONFIG_DUMMY=m
> CONFIG_NET_ETHERNET=y
> CONFIG_NET_VENDOR_3COM=y
> CONFIG_EL3=m
> CONFIG_NET_ISA=y
> CONFIG_EEXPRESS=m
> CONFIG_NE2000=m
> CONFIG_PPP=m
> CONFIG_CD_NO_IDESCSI=y
> CONFIG_SBPCD=m
> CONFIG_MINIX_FS=m
> CONFIG_EXT2_FS=y
> CONFIG_FAT_FS=m
> CONFIG_MSDOS_FS=m
> CONFIG_VFAT_FS=m
> CONFIG_UMSDOS_FS=m
> CONFIG_PROC_FS=y
> CONFIG_NFS_FS=m
> CONFIG_SMB_FS=m
> CONFIG_SMB_LONG=y
> CONFIG_ISO9660_FS=m
> CONFIG_UFS_FS=m
> CONFIG_BSD_DISKLABEL=y
> CONFIG_SERIAL=y
> CONFIG_PRINTER=m
> CONFIG_WATCHDOG=y
> CONFIG_WATCHDOG_NOWAYOUT=y
> CONFIG_SOFT_WATCHDOG=y
> CONFIG_SOUND=m
> CONFIG_SB=y
> CONFIG_ADLIB=y
> CONFIG_YM3812=y
> SBC_BASE=220
> SBC_IRQ=10
> SBC_DMA=3
> SB_DMA2=5
> SB_MPU_BASE=330
> SB_MPU_IRQ=-1
> ___
> Trevor Johnson <trevor@jpj.org>
>
>
> ------------------------------
>
> From: celestra@ix.netcom.com (Arthur D. Jerijian)
> Date: Mon, 18 Nov 1996 22:23:23 -0800 (PST)
> Subject: [PATCH] to allow seagate.c to compile properly
>
> Hi all,
>
> I tried to build Linux 2.1.11 with just about everything built as modules.
> It turns out that some of the drivers have #warning directives, but since
> this is a 2.1.x kernel, they don't bother me much. I did find, however,
> a boo-boo that prevents seagate.c from compiling. Here is a patch to
> fix it, although I'm pretty sure that the other #warning's in that same
> file will be fixed over time.
>
> Thanks.
>
> --Arthur
>
> - --- linux/drivers/scsi/seagate.c.orig Mon Nov 18 22:19:17 1996
> +++ linux/drivers/scsi/seagate.c Mon Nov 18 22:19:21 1996
> @@ -345,7 +345,7 @@
>
> if (base_address)
> {
> - - st0x_cr_sr = base_address + (controller_type == SEAGATE ? 0x1a00 : 0x1c00));
> + st0x_cr_sr = base_address + (controller_type == SEAGATE ? 0x1a00 : 0x1c00);
> st0x_dr = st0x_cr_sr + 0x200;
> #ifdef DEBUG
> printk("%s detected. Base address = %x, cr = %x, dr = %x\n", tpnt->name, base_address, st0x_cr_sr, st0x_dr);
>
> ------------------------------
>
> From: "B. James Phillippe" <bryan@terran.org>
> Date: Mon, 18 Nov 1996 22:27:10 -0800 (PST)
> Subject: Re: Cyrix 6x86
>
> On Tue, 19 Nov 1996, Agus Budy Wuysang wrote:
>
> >
> > I have a Cyrix 6x86 P166+ overclocked to P200+ :)
> >
> > Now, should I recompile my kernel (and/or other programs) with
> > 486, Pentium, or PPro optimization?
>
> I've been building for PPro under recommendation of Cyrix. Also, there
> are some really excellent Cyrix patches floating around this mailing list
> that do great things for this chip. If you have trouble finding any, I
> can send you the one I'm using (by Mike Jagdis; thanks Mike!!). For what
> it's worth, I'd really, really... _really_ like to see some of these Cyrix
> patches getting into the 2.1 kernel.
>
> - -bp
> - --
> # B. James Phillippe # System Administrator <Terran.ORG>
> # <bryan@terran.org> # http://w3.terran.org/~bryan
> # Finger for PGP key # Member since 1.1.59
>
>
>
> ------------------------------
>
> From: "Andrew E. Mileski" <aem@ott.hookup.net>
> Date: Tue, 19 Nov 1996 01:33:41 -0500 (EST)
> Subject: Bug in sysklogd v1.3-0
>
> I just checked the LATEST sysklogd package (v1.3-0) available from
> sunsite and tsx-11, and it _still_ has the version bug :-(
>
> To patch the sysklogd source code, edit the function CheckVersion()
> in the file ksym.c, and change line 406 from:
> auto char vstring[6];
> to:
> auto char vstring[9];
> Which is plenty of room for versions like v255.255.255 :-)
> (v255.255.255 = 0xffffff = 16777215 which is a 9 character string)
>
> This bug affects all v2.*.* kernels.
> (v2.0.0 = 0x20000 = 131072 which is a 7 character string)
>
> - --
> Andrew E. Mileski mailto:aem@ott.hookup.net
> Linux Plug-and-Play Kernel Project http://www.redhat.com/linux-info/pnp/
> XFree86 Matrox Team http://www.bf.rmit.edu.au/~ajv/xf86-matrox.html
>
> ------------------------------
>
> From: Ion Badulescu <ionut@moisil.wal.rhno.columbia.edu>
> Date: Tue, 19 Nov 1996 01:41:31 -0500 (EST)
> Subject: 2.1.11 breaks module support (long)
>
> Several functions throughout kernel/module.c expect get_mod_name() to
> return 0 on success, while it in fact returns the length of the name or
> - -EFAULT if the pointer is bogus. The result is funny messages from
> insmod, like:
>
> init_module: Bad font file format
>
> The fix is obvious, simply change `!= 0' to `< 0' wherever the result of
> get_mod_name() is being tested in module.c
>
> HOWEVER, this does not fix the modules on my system, and I'd like to know
> why, as it doesn't make any sense. get_mod_name() supposedly returns a
> number between 0 and 64 on success; how in the *** can it return the
> number of characters in the name minus 64?!?! I tested it by changing the
> function to:
>
> inline int
> get_mod_name(char *user_name, char *buf)
> {
> /* Should return -EBIG instead of -EFAULT when the name
> is too long, but that we couldn't detect real faults then.
> Maybe strncpy_from_user() should return -EBIG, when
> the source string is too long. */
> int result;
> result = strncpy_from_user(buf, user_name, MOD_MAX_NAME);
> printk("Module name: %s, result: %d", buf, result);
> return result;
> }
>
> and this is what I get in the logs:
>
> Nov 19 00:42:24 moisil kernel: Module name: floppy, result: 6
> Nov 19 00:42:24 moisil kernel: Module name: floppy, result: -58
> Nov 19 00:42:24 moisil kernel: Module name: floppy, result: 6
> Nov 19 00:42:24 moisil kernel: Module name: floppy, result: 6
> Nov 19 00:42:24 moisil kernel: Module name: floppy, result: -58
> Nov 19 00:42:24 moisil kernel: Module name: floppy, result: 6
> Nov 19 00:42:25 moisil kernel: Module name: sound, result: 5
> Nov 19 00:42:25 moisil kernel: Module name: sound, result: -59
> Nov 19 00:42:25 moisil kernel: Module name: sound, result: 5
> Nov 19 00:42:25 moisil last message repeated 2 times
> Nov 19 00:42:25 moisil kernel: Module name: sound, result: -59
> Nov 19 00:42:25 moisil kernel: Module name: sound, result: 5
>
> Moreover, it does not appear to be a gcc/as bug, as the code dissasembled
> from vmlinux looks ok to me (this is get_mod_name with the inlined
> strncpy_from_user):
>
> c0114800 <get_mod_name> pushl %ebp
> c0114801 <get_mod_name+1> pushl %edi
> c0114802 <get_mod_name+2> pushl %esi
> c0114803 <get_mod_name+3> pushl %ebx
> c0114804 <get_mod_name+4> movl 0x14(%esp,1),%ecx
> c0114808 <get_mod_name+8> movl 0x18(%esp,1),%ebp
> c011480c <get_mod_name+c> movl $0x40,%edx
> c0114811 <get_mod_name+11> movl $0xfffffff2,%ebx
> c0114816 <get_mod_name+16> movl 0xc01a815c,%eax
> c011481b <get_mod_name+1b> testb $0x3,0x314(%eax)
> c0114822 <get_mod_name+22> je c011482c <get_mod_name+2c>
> c0114824 <get_mod_name+24> cmpl $0xbfffffff,%ecx
> c011482a <get_mod_name+2a> ja c0114841 <get_mod_name+41>
> c011482c <get_mod_name+2c> movl %edx,%ebx
> c011482e <get_mod_name+2e> movl %ecx,%esi
> c0114830 <get_mod_name+30> movl %ebp,%edi
> c0114832 <get_mod_name+32> testl %edx,%edx
> c0114834 <get_mod_name+34> je c0114841 <get_mod_name+41>
> c0114836 <get_mod_name+36> lodsb %ds:(%esi),%al
> c0114837 <get_mod_name+37> stosb %al,%es:(%edi)
> c0114838 <get_mod_name+38> testb %al,%al
> c011483a <get_mod_name+3a> je c011483f <get_mod_name+3f>
> c011483c <get_mod_name+3c> decl %edx
> c011483d <get_mod_name+3d> jne c0114836 <get_mod_name+36>
> c011483f <get_mod_name+3f> subl %edx,%ebx
> c0114841 <get_mod_name+41> pushl %ebx
> c0114842 <get_mod_name+42> pushl %ebp
> c0114843 <get_mod_name+43> pushl $0xc0181de7
> c0114848 <get_mod_name+48> call c0112d30 <printk>
> c011484d <get_mod_name+4d> movl %ebx,%eax
> c011484f <get_mod_name+4f> addl $0xc,%esp
> c0114852 <get_mod_name+52> popl %ebx
> c0114853 <get_mod_name+53> popl %esi
> c0114854 <get_mod_name+54> popl %edi
> c0114855 <get_mod_name+55> popl %ebp
> c0114856 <get_mod_name+56> ret
> c0114857 <get_mod_name+57> nop
>
> How can ebx be -58 or -59 at the time printk gets called remains a mistery
> to me...
>
> Now the funny part: inserting a printk into strncpy_from_user (a painful
> thing to do, since the function is called _a_lot_), which basically
> duplicates the sequence calling printk (yes, I did disassemble it) makes
> everything work just fine! Modules get inserted and removed like a charm..
>
>
> Ionut
>
> - --
> Ionut Badulescu - Columbia College '98 E-mail:ib42@columbia.edu
> Phone: (212)853-7875 Snail mail: 4A4 Wallach Hall
> Fax: (212)695-5560 1116 Amsterdam Ave
> PGP key available on request New York, NY 10027
> It is better to keep your mouth shut and be thought a fool,
> than to open it and remove all doubt.
>
>
>
> ------------------------------
>
> From: Xavier Leroy <Xavier.Leroy@inria.fr>
> Date: Tue, 19 Nov 1996 10:29:15 +0100 (MET)
> Subject: Re: CLONE_PID (was: POSIX.1b semaphores)
>
> > From: Ulrich Drepper <drepper@myware.rz.uni-karlsruhe.de>
> > Date: 19 Nov 1996 04:56:43 +0100
> >
> > (PS: A second *very* important task would be to implement CLONE_PID.)
> >
> > In the kernel of libc? Last I checked the CLONE_PID flag exists in
> > the kernel and works just fine.
>
> Well, it works but it's not usable in a thread library. What's missing
> is the ability to send a signal to a particular "thread", i.e. one of
> several processes having the same PID. LinuxThreads needs this feature
> because it implements suspend thread/restart thread with signals.
>
> Linus proposed a scheme whereas the high bits of the pid argument to
> kill(2) would encode the "thread" number. That's all right, but still
> needs to be implemented.
>
> But wait, there's a second half to the problem. What happens if we do
> kill(p, sig) when p is a regular PID (high bits 0) and there are
> several processes with PID p ? Which one(s) get the signal?
> The first process with PID p encountered while searching the process
> table? No, because that process may block the signal while others with
> the same PID don't. The first process with PID p that does not block
> the signal? All right, sounds reasonable.
>
> But what happens if all processes with PID p block the signal? Shall
> we queue the signal on one of those processes chosen at random?
> This does not sound very good, because if another thread unblocks the
> signal later, it will not receive it since it's been queued on another
> thread. If I understand the POSIX threads spec correctly, the signal
> should be queued for the whole set of threads, and delivered to
> whichever unblocks the signal later.
>
> One approach would be to have an extra option to clone, say
> CLONE_SIGPENDING, to share the set of pending signals between several
> processes. That would be fairly close to the POSIX semantics, but then
> we also need a per-thread set of pending signals for delivery of
> signals to one thread in particular...
>
> As you can see, this CLONE_PID flag, although working fine, opens a
> whole can of worms in the area of signal delivery. If anyone has ideas
> on how to approach this problem, please let me know.
>
> - - Xavier Leroy
>
>
>
> ------------------------------
>
> From: "Andrew M. Bishop" <amb@gedanken.demon.co.uk>
> Date: Mon, 18 Nov 1996 07:23:09 GMT
> Subject: Re: unlink system call on directories - Bug + fix
>
> Kenneth Albanowski <kjahds@kjahds.com> wrote:
> > On Fri, 15 Nov 1996, Andrew M. Bishop wrote:
> >
> > > Even worse for NFS, the unlink() call will succeed on directories.
> > > The inode will disapear, only to be found in lost+found on the
> > > file server next time it is fsck'd.
> >
> > This can't be right. If this does occur, it is the server's fault, not the
> > client.
>
> The same filesystem, exported from SunOS 4.1.1, mounted on SunOS 4.1.4
> does not allow directories to be unlinked. So I conclude that the
> server is not wrong. The Linux kernel should know that the file is a
> directory and not even try to unlink it since it knows it is not
> allowed.
>
> - --
> Andrew.
> - ----------------------------------------------------------------------
> Andrew M. Bishop amb@gedanken.demon.co.uk
> http://www.gedanken.demon.co.uk/
>
> ------------------------------
>
> From: Linus Torvalds <torvalds@ev5.linux.s.xgw.fi>
> Date: Tue, 19 Nov 1996 11:25:42 +0200 (EET)
> Subject: Re: wait_queue bug ?
>
> On Mon, 18 Nov 1996, Andreas Schultz wrote:
> >
> > There seems to be a bug in the wait_queue handling. Imagin the following
> > situation:
> >
> > struct {
> > ulong test_value;
> > struct wait_queue *my_wait_queue;
> > } my_struct;
> >
> > A "sleep_on(&my_struct.my_wait_queue);" overwrites than the value
> > of test_value, causing all kind of havoc.
>
> Hmm.. Have you initialized the wait queues with
>
> init_wait_queue(&my_struct.my_wait_queue);
>
> which should set up the wait queue correctly?
>
> > It seems that the bug has been introduced in 2.0.16. Have a look at
> > following pice of code from include/linux/sched.h:
>
> It's rather ugly, yes.
>
> > extern inline void __add_wait_queue(struct wait_queue ** p,
> > struct wait_queue *wait)
>
> [ obscene code removed: I wrote it, I never want to see it again ;-]
>
> > and from include/linux/wait.h:
> >
> > #define WAIT_QUEUE_HEAD(x) ((struct wait_queue *)((x)-1))
> >
> > The assignment of WAIT_QUEUE_HEAD to *next goes to an illegal address !!
>
> The code really does assign a pointer to the "previous" word into the
> wait-queue, but that pointer should never be dereferenced directly. It
> should always be referenced through the "->next" entry, which will cancel
> the effect of the "-1" done in WAIT_QUEUE_HEAD.
>
> Now, I agree that it's not pretty, but if you have a weak stomach you
> shouldn't have looked at the implementation ;)
>
> My approach to code cleanliness: the real C code should be readable, but
> header files are allowed to hide ugly details if the interface to those
> ugly details is clean. In this case the "interface" is
>
> init_wait_queue(&wait_q_pointer)
> sleep_on(&wait_q_pointer);
> wake_up(&wait_q_pointer);
> ... etc ...
>
> and the ugly details are just implementation details that you should never
> see..
>
> There could certainly be a bug there somewhere, but I don't see it
> immediately. I did walk through all this when I wrote it, but right now
> I'd rather forget it ;)
>
> Linus
>
>
> ------------------------------
>
> End of linux-kernel-digest V1 #616
> **********************************
>
> To subscribe to linux-kernel-digest, send the command:
>
> subscribe linux-kernel-digest
>
> in the body of a message to "Majordomo@Majordomo.vger.rutgers.edu". If you want
> to subscribe something other than the account the mail is coming from,
> such as a local redistribution list, then append that address to the
> "subscribe" command; for example, to subscribe "local-linux-kernel":
>
> subscribe linux-kernel-digest local-linux-kernel@your.domain.net
>
> A non-digest (direct mail) version of this list is also available; to
> subscribe to that instead, replace all instances of "linux-kernel-digest"
> in the commands above with "linux-kernel".
>
--
_______ KB7PWD @ KC7Y.AZ.US.NOAM ecloud@goodnet.com
(_ | |_) Shawn T. Rutledge on the web: http://www.goodnet.com/~ecloud
__) | | \__________________________________________________________________
* alternative energy * IEEE * techno * let freedom ring * X window * PIC *