----- Transcript of session follows -----
Executing: /usr/lib/mail/surrcmd/smtpqer -n -B -C -u npvsrv1.NapervilleIL.NCR.COM!ncrhub4!ncrgw1!vger.rutgers.edu!linux-kernel frsos.napervilleil.attgis.com jejb@frsos.napervilleil.attgis.com
smtpqer: Binary contents cannot be sent via SMTP
server "/usr/lib/mail/surrcmd/smtpqer" failed - unknown mailer error 1
----- Unsent message follows -----
>From ncrgw1!vger.rutgers.edu!linux-kernel Tue Jul 18 07:47 EDT 1995 remote from ncrhub4
Received: by ncrhub4.ATTGIS.COM; 18 Jul 95 07:47:10 EDT
Received: by ncrgw1.ATTGIS.COM; 18 Jul 95 01:55:54 EDT
Received: (from majordomo@localhost) by vger.rutgers.edu (8.6.12/8.6.12) id EAA05062 for linux-kernel-digest-outgoing; Mon, 17 Jul 1995 04:28:38 -0400
Date: Mon, 17 Jul 1995 04:28:38 -0400
Message-Id: <199507170828.EAA05062@vger.rutgers.edu>
From: owner-linux-kernel-digest@vger.rutgers.edu
To: linux-kernel-digest@vger.rutgers.edu
Subject: linux-kernel-digest V1 #118
Reply-To: linux-kernel@vger.rutgers.edu
Errors-To: owner-linux-kernel-digest@vger.rutgers.edu
Precedence: bulk
linux-kernel-digest Monday, 17 July 1995 Volume 01 : Number 118
----------------------------------------------------------------------
From: Kenneth Albanowski <kjahds@kjahds.com>
Date: Sun, 16 Jul 1995 01:09:36 -0400 (EDT)
Subject: Re: Login strangeness
On Wed, 12 Jul 1995, Harik A'ttar wrote:
> Reply-to: ind00621@pegasus.cc.ucf.edu
>
> Ok, since the change from default of console to default of linux
> In the kernel, a lot of strange things have happened.
> First off - logout no longer clears the screen like it used to
> (I fixxed that by prepending clear to it. :) but mostly, a lot
> of backspace errors are occuring. I.E. login prints the house
> char ^? <- that it? Instead of backspacing. However, if I fail
> the password, it dosn't clear but it does backspace. I assume
> this is because login was forced to reload and changed somethign
> but I have no idea what it is.
>
> A _LOT_ of backspace strangeness everywhere -- login, talk,
> people telnet in, using ^H, sometimes it works, sometimes not.
> telnet out, same thing 50% chance it will be right.
>
> stty erase will fix it, but I don't like having to figure
> out what one it wants each time.
>
> I did change the console entery in /etc/termcap to linux,
> but this strangeness goes beyond that. Any pointers
> on where to get more information?
Check /etc/profile, ~/.profile, ~/.ksrc, etc., for code that sets up your
terminal mode by checking for a $TERM of "console". That needs to be
changed to "linux" now, as well.
> Dan Merillat Guess what? I really _DO_ speak for my system.
> Harik A'ttar And if you share my opinions, you should seek
> Dam Mad God! professional help.
- --
Kenneth Albanowski (kjahds@kjahds.com, CIS: 70705,126)
------------------------------
From: Andreas Koppenhoefer <koppenas@koppenas.informatik.uni-stuttgart.de>
Date: Sun, 16 Jul 1995 10:17:43 +0200 (MET DST)
Subject: Re: Archive of the mailing list
- -----BEGIN PGP SIGNED MESSAGE-----
> Eric DUMAS was rumored to have said:
>
> > Is it a ftp site which has made an archive of this list ?
> >
> > Thanks !
>
> If there isn't, let me know. I have a personal archive from when I
> subscribed, and I could move that over to our ftp site if people
> want it.
- - From Majordomo help text (you can get it by sending 'help' to
Majordomo@vger.rutgers.edu):
It understands the following commands:
...
get <list> <filename>
Get a file related to <list>.
index <list>
Return an index of files you can "get" for <list>.
...
So one can send 'index linux-kernel' to Majordomo@vger.rutgers.edu to
see what's there. Later you can use get commands to retrive those
files. But remember, you must have subscribed to the list to get
files or index.
Some days ago I've managed to get an index by switching temporarily to
a list by
subscribe linux-kernel-digest
index linux-kernel-digest
unsubscribe linux-kernel-digest
and later
subscribe linux-kernel-digest
get linux-kernel-digest some-file-name
get linux-kernel-digest another-file-name
unsubscribe linux-kernel-digest
That worked!
- - - Andreas
- - --
Andreas Koppenhoefer, Student der Universitaet Stuttgart, BR Deutschland
prefered languages: German, English, C, perl ("Just another Perl hacker,")
SMTP: koppenas@informatik.uni-stuttgart.de (university address)
Andreas.Koppenhoefer@studbox.uni-stuttgart.de (my home address)
privat: Belaustr. 5/3, D-70195 Stuttgart, Germany,
Earth, Sector ZZ9 plural Z alpha
phone: +49 711 694111 and +49 711 6999006 (19-22h MEZ=GMT+1)
- -----BEGIN PGP SIGNATURE-----
Version: 2.6
iQBVAgUBMAjLJkVdjNvyndGpAQHLIQIAkjEsWzanGwxyXO1zt5TyLijOLCuISw0R
cp60ldflWOyyO9Ddurf7qIZvgtRFx9LORy85OIIJKqWDdiVUS6Zxvw==
=CD4O
- -----END PGP SIGNATURE-----
------------------------------
From: Luca Spada <skyluke@sun.skylink.it>
Date: Sun, 16 Jul 1995 14:40:46 +0200 (MET DST)
Subject: IP forwarding broken in 1.3.10
Hi...
just installed 1.3.10 and IP forwarding/gatewaying is no longer working
on my Linux. Any idea or is a bug ?
Bye
Luca Spada (skyluke@sun.skylink.it)
------------------------------
From: urlichs@smurf.noris.de (Matthias Urlichs)
Date: 16 Jul 1995 12:47:07 +0200
Subject: Re: Nested interrupts problem, not SA_INTERRUPT
Hi,
Richard Black <Richard.Black@cl.cam.ac.uk> writes:
>
> In case its relevant this is slackware 2.3.0 linux 1.2.8 HP Vectra 386/33U,
> /proc/interrupts shows:
> 0: 866007 timer
> 5: 42555849 EATM Interface
You are processing 5000 interrupts per second on a 386/33?
Congratulations...
No wonder the clocks gets bogged down -- from here, it looks like the
system is severely overloaded.
Why can't you poll the card?
- --
Compliments or congratulations are always kindly taken, and cost nothing
but pen, ink, and paper. I consider them as draughts upon good
breeding, where the exchange is always greatly in favor of the drawer.
-- Chesterfield
- --
Matthias Urlichs \ XLink-POP N|rnberg | EMail: urlichs@smurf.noris.de
Schleiermacherstra_e 12 \ Unix+Linux+Mac | Phone: ...please use email.
90491 N|rnberg (Germany) \ Consulting+Networking+Programming+etc'ing 42
PGP: 1B 89 E2 1C 43 EA 80 44 15 D2 29 CF C6 C7 E0 DE
Click <A HREF="http://smurf.noris.de/~urlichs/finger">here</A>.
------------------------------
From: Carlo Emilio Prelz <fluido@telepac.pt>
Date: Sun, 16 Jul 1995 10:28:44 +0200 (MET DST)
Subject: Re: Null pointer dereference - 1.3.10/pppd
Hi again. I restarted ppp & the file transfer that I was running. pppd
crashed again, but in a different routine. Details follow.
I will now reboot, link to send this message, and try to transfer the
file I was trying to transfer without doing anything else at the same
time.
(ps I was sending two files to two different addresses - one was the
previous mail message to the list)
Jul 16 10:09:16 pimpinel linux: general protection: 0000
Jul 16 10:09:16 pimpinel linux: EIP: 0010:001a8ad2
Jul 16 10:09:16 pimpinel linux: EFLAGS: 00010206
Jul 16 10:09:16 pimpinel linux: eax: f000e000 ebx: 00000014 ecx: 00000033 edx: 00000000
Jul 16 10:09:16 pimpinel linux: esi: 001dffe8 edi: 00010b60 ebp: 00000010 esp: 01358f20
Jul 16 10:09:16 pimpinel linux: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Jul 16 10:09:16 pimpinel linux: Process pppd (pid: 2221, process nr: 31, stackpage=01358000)
Jul 16 10:09:16 pimpinel linux: Stack: 00000000 00000000 00000000 00000014 001dffe8 ffffffff 001a9e21 001dffe8
Jul 16 10:09:16 pimpinel linux: 00ee4000 00cf8700 00897a20 00000010 0010a1fc 0019049c 00ee4000 00897a20
Jul 16 10:09:16 pimpinel linux: 00010b50 00000010 00897a20 00cf8700 00000010 00010b50 001203b4 00cf8700
Jul 16 10:09:16 pimpinel linux: Call Trace: 001a9e21 0010a1fc 0019049c 001203b4 0010a6c1
Jul 16 10:09:16 pimpinel linux: Code: ff d0 01 86 bc 00 00 00 83 c4 10 39 d8 75 37 56 e8 91 29 00
001a8a28 t _ppp_dev_ioctl
001a8ab8 t _ppp_kick_tty
001a8b68 t _ppp_write_wakeup
...
001a97d8 t _ppp_read
001a9b88 t _ppp_write
001aa0b8 t _ppp_ioctl
...
00109f5c T _sys_sigreturn
0010a12c T _setup_frame
0010a26c T _do_signal
...
001902d0 t _tty_read
001903c0 t _tty_write
00190510 t _init_dev
...
00120268 T _sys_read
00120318 T _sys_write
00120400 t _insert_inode_free
...
0010a658 t reschedule
0010a668 T _system_call
0010a708 T ret_from_sys_call
- --
* ...Ma appena fuori tutto e' gomma,
* K * Carlo E. Prelz - fluido@telepac.pt tutto e' cicca impiastricciata...
* (Marco Zappa-Niente cicca nella scuola)
------------------------------
From: Chris Patti <feoh@wyn.hq.org>
Date: Sun, 16 Jul 1995 12:45:41 -0400 (EDT)
Subject: Memory keeps trickling away in >1.1.59
Hello all.
I've been having a rather serious problem recently which perhaps one of you
could toss me some pointers to help solve.
In every kernel I've run >1.1.59, there seems to be a hole in Linux's memory
management infrastructure :)
i.e. on a 32 meg machine, I run X, it uses a big blob of RAM, I run clients,
they use ram, I exit X, the RAM stays allocated! I run gcc a few times, yet
more RAM down the tubes.
This process continues until the system becomes almost unusably slow.
It's not uncommon for me to be running with a working pool of only 4-6M free
on a 32 meg system with only a single VT, no X, and a bash running!!
Is there any way I can track down who's munching all these resources?
Thanks,
- -Chris Patti
------------------------------
From: Carlo Emilio Prelz <fluido@telepac.pt>
Date: Sun, 16 Jul 1995 11:02:03 +0200 (MET DST)
Subject: Re: Null pointer dereference - 1.3.10/pppd
Hep. Even when the file transfer is the only active user, ppd crashed at
the same spot as in the first message that I sent. I then tried to boot with
1.2.10, but I got another crash. This happens always after transferring
~150k. Maybe there's a limit at the receiving side - will try to find out,
but this should not cause null references...
I am including the messages from the 1.2.10 kernel, but I cannot add the
procedure references, because I don't have the system map for it
anymore (not even the sources - lack of disk space). Hope this is of some
help. It appears as if this is the same error...
Jul 16 10:42:27 pimpinel linux: Unable to handle kernel NULL pointer dereference at virtual address c0000000
Jul 16 10:42:27 pimpinel linux: Unable to handle kernel NULL pointer dereference at virtual address c0000000
Jul 16 10:42:28 pimpinel linux: current->tss.cr3 = 00e97000, %cr3 = 00e97000
Jul 16 10:42:28 pimpinel linux: current->tss.cr3 = 00e97000, %cr3 = 00e97000
Jul 16 10:42:28 pimpinel linux: *pde = 00102067
Jul 16 10:42:28 pimpinel linux: *pde = 00102067
Jul 16 10:42:28 pimpinel linux: *pte = 00000027
Jul 16 10:42:28 pimpinel linux: *pte = 00000027
Jul 16 10:42:28 pimpinel linux: Oops: 0002
Jul 16 10:42:28 pimpinel linux: EIP: 0010:001a31d3
Jul 16 10:42:28 pimpinel linux: EFLAGS: 00010246
Jul 16 10:42:28 pimpinel linux: eax: 00000000 ebx: 001d82c8 ecx: 000000ff edx: 00000007
Jul 16 10:42:28 pimpinel linux: esi: 0000000f edi: 00010b51 ebp: 00000010 esp: 00e98f44
Jul 16 10:42:28 pimpinel linux: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Jul 16 10:42:28 pimpinel linux: Process pppd (pid: 101, process nr: 26, stackpage=00e98000)
Jul 16 10:42:28 pimpinel linux: Stack: 00f19000 0117bee0 0008b180 00010b50 000000ff 0018ba3c 00f19000 0008b180
Jul 16 10:42:28 pimpinel linux: 00010b50 00000010 0008b180 0117bee0 00000010 001255f8 0117bee0 0008b180
Jul 16 10:42:28 pimpinel linux: 00010b50 00000010 00f02000 00010b50 00010920 bfffd498 0008b180 00010068
Jul 16 10:42:28 pimpinel linux: Call Trace: 0018ba3c 001255f8 0011074d
Jul 16 10:42:28 pimpinel linux: Code: 88 08 ff 43 68 66 8b 53 38 66 c1 ea 08 8a 44 24 10 32 43 38
Ciao
Carlo
- --
* ...Ma appena fuori tutto e' gomma,
* K * Carlo E. Prelz - fluido@telepac.pt tutto e' cicca impiastricciata...
* (Marco Zappa-Niente cicca nella scuola)
------------------------------
From: Jim Lynch <jimlynch@netcom.com>
Date: Sun, 16 Jul 1995 02:56:39 -0700 (PDT)
Subject: Re: FTP fs possible? worthwile?
You just invented NFS. Now you need to debug and implement it...
- -Jim Lynch aka enOne (jimlynch@netcom.com)
------------------------------
From: Carlo Emilio Prelz <fluido@telepac.pt>
Date: Sun, 16 Jul 1995 10:03:18 +0200 (MET DST)
Subject: Null pointer dereference - 1.3.10/pppd
Hi. Was using pppd with a few TCP connections going on (the only
strange thing is that I was uploading a file to an ftp site (I
generally don't do that). The error message came out and the telephone
link fell immediately.
I don't know whether this is reproducible. Will see later. Using
1.3.10 with GCC 1.6.3, a.out. PS No crash, no need to reboot. I will
now try to link again to send this message.
Jul 16 09:51:20 pimpinel linux: Unable to handle kernel NULL pointer dereference at virtual address c0000000
Jul 16 09:51:20 pimpinel linux: Unable to handle kernel NULL pointer dereference at virtual address c0000000
Jul 16 09:51:20 pimpinel linux: current->tss.cr3 = 0129f000, %cr3 = 0129f000
Jul 16 09:51:20 pimpinel linux: current->tss.cr3 = 0129f000, %cr3 = 0129f000
Jul 16 09:51:20 pimpinel linux: *pde = 00102067
Jul 16 09:51:20 pimpinel linux: *pde = 00102067
Jul 16 09:51:21 pimpinel linux: *pte = 00000027
Jul 16 09:51:21 pimpinel linux: *pte = 00000027
Jul 16 09:51:21 pimpinel linux: Oops: 0002
Jul 16 09:51:21 pimpinel linux: EIP: 0010:001a9d7f
Jul 16 09:51:21 pimpinel linux: EFLAGS: 00010246
Jul 16 09:51:21 pimpinel linux: eax: 00000000 ebx: 001dffe8 ecx: 000000ff edx: 00000007
Jul 16 09:51:21 pimpinel linux: esi: 0000000f edi: 00010b51 ebp: 00000010 esp: 00063f40
Jul 16 09:51:21 pimpinel linux: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Jul 16 09:51:21 pimpinel linux: Process pppd (pid: 2112, process nr: 25, stackpage=00063000)
Jul 16 09:51:21 pimpinel linux: Stack: 00e43000 00cf8700 00897cc0 00000010 0010a1ff 0019049c 00e43000 00897cc0
Jul 16 09:51:21 pimpinel linux: 00010b50 00000010 00897cc0 00cf8700 00000010 00010b50 001203b4 00cf8700
Jul 16 09:51:21 pimpinel linux: 00897cc0 00010b50 00000010 01257000 00010b50 00010920 bfffd48c 00897cc0
Jul 16 09:51:21 pimpinel linux: Call Trace: 0010a1ff 0019049c 001203b4 0010a6c1
Jul 16 09:51:21 pimpinel linux: Code: 88 08 ff 43 6c 66 8b 53 3c 66 c1 ea 08 8a 44 24 10 32 43 3c
Kernel references:
001a97d8 t _ppp_read
001a9b88 t _ppp_write
001aa0b8 t _ppp_ioctl
...
00109f5c T _sys_sigreturn
0010a12c T _setup_frame
0010a26c T _do_signal
...
001902d0 t _tty_read
001903c0 t _tty_write
00190510 t _init_dev
...
00120268 T _sys_read
00120318 T _sys_write
00120400 t _insert_inode_free
...
0010a658 t reschedule
0010a668 T _system_call
0010a708 T ret_from_sys_call
Ciao
Carlo
- --
* ...Ma appena fuori tutto e' gomma,
* K * Carlo E. Prelz - fluido@telepac.pt tutto e' cicca impiastricciata...
* (Marco Zappa-Niente cicca nella scuola)
------------------------------
From: "Michael H. Price II" <mhp1@Ra.MsState.Edu>
Date: Sun, 16 Jul 1995 10:04:35 -0500
Subject: sbpcd.c suggestion
In pretty much all kernel versions, the driver for Sound Blaster CD's
(drivers/block/sbpcd.c) contains the following code segment (portion below
taken from 1.3.10):
- -----CODE SEGMENT-----
#if DISTRIBUTION
static int sbpcd_debug = (1<<DBG_INF);
#else
static int sbpcd_debug = ((1<<DBG_INF) |
(1<<DBG_TOC) |
(1<<DBG_MUL) |
(1<<DBG_UPC));
#endif DISTRIBUTION
- -----END CODE SEGMENT-----
My suggestion is to change the '#if DISTRIBUTION' to '#if !(DISTRIBUTION)'
since in all other places (as specified in README.sbpcd) setting
DISTRIBUTION to 0 causes less output to the screen. In this one case,
however, setting it to 0 causes more output. This seems a little odd to
me.
Michael
------------------------------
From: Albert Cahalan <albert@ccs.neu.edu>
Date: Sun, 16 Jul 1995 12:57:13 -0400
Subject: Serial driver
> I'm in the (ugly) process of porting the x86 serial driver
> to the 680x0 version of Linux. (I'm working on a prototype ISA->Zorro
> board). Aside from the obvious problem, that x86 linux hasn't yet
> incorportated the mach-ind extensions found in 1.2pl1 (680x0),
> I'm wondering if there is a way to get rid of the static rs_table
> arrays, which probably take up a decent chunk of memory.
Perhaps you should write a 680x0-only driver.
> Can someone please critique this? Things definitely can't stay the
> way they are...especially with the Mac and PPC ports on the horizon.
You can use that driver for a PC (x86 or Alpha), but I think it might
be easier to write from scratch for 680x0 hardware. You don't even
use the same UARTs, do you?
------------------------------
From: awpguy@acs.ucalgary.ca
Date: Mon, 10 Jul 1995 13:39:04 -0600
Subject: using "core" as directory name
I have recently got the 1.3.8 kernel sources - it uses the name "core"
for a directory (linux/net/core), I use cvs and this causes it some
problems because it ignores some files this can be changed on the
command line etc (although cvs is being stubborn at the moment) but it
would make life easier if the name was changed (I've used "ncore").
Andy.
------------------------------
From: root <root@succubus.madhouse.com>
Date: Sun, 16 Jul 1995 16:21:10 -0400
Subject: Re: WFW shares
I most certainly would refrain from using 1.3 as a provider. it's a
development kernel.
On Sat, 15 Jul 1995 Muleba@aol.com wrote:
> I have 1.3.10 and the system for mounting WFW shared drives won't compile on
> my system. I can compile without difficulty without saying yes to support
> for the file system in my config file. I'm in the process of becoming an
> internet provider, and I only have 2.75 Gigabytes on my local system. The
------------------------------
From: hpa@trantor.storm.net (H. Peter Anvin)
Date: 16 Jul 1995 20:34:28 GMT
Subject: Re: FTP fs possible? worthwile?
In article <Pine.LNX.3.91.950712101815.6078A-100000@chaos.sub.ucf.edu>,
Harik A'ttar <harik@chaos.sub.ucf.edu> wrote:
>Reply-to: ind00621@pegasus.cc.ucf.edu
>
>Ok: I had a thought the other day on an FTP fs, similar to NFS and the
>/proc system. Essentally: All it would be is a directory structure.
>I.E. /ftp/dotted.ip.of.host/structure
>
Someone already implemented this on top of userfs (due to the nature
of FTP, you do *not* want to implement this in user space).
Unfortunately, userfs hasn't been updated lately -- which IMHO is a
major bummer.
In fact, FSP may be a better protocol than either FTP or NFS for
across-WAN file sharing; it was popular for a while but then sort of
became obscurized. Big bummer, IMHO.
/hpa
- --
PGP public key available - finger hpa@yggdrasil.com
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
------------------------------
From: invid@optera.com (Joshua M. Thompson)
Date: Sun, 16 Jul 1995 15:15:14 -0500
Subject: Re: IP forwarding broken in 1.3.10
>just installed 1.3.10 and IP forwarding/gatewaying is no longer working
>on my Linux. Any idea or is a bug ?
>
>Bye
>
>Luca Spada (skyluke@sun.skylink.it)
It seems to be a bug in the 1.3.10 net code, because I had the same problem
last night when I tried to upgrade from 1.3.6 to 1.3.10.
- --
invid@msen.com "Excuse me, Potty Emergency!"
http://www.optera.com/~invid - Wakko Warner
------------------------------
From: lk <lk@cyberflunk.com>
Date: Sun, 16 Jul 1995 11:39:33 -0700 (PDT)
Subject: Re: FTP fs possible? worthwile?
this has been done..
it's called 'arcfs' and was distributed with userfs.. which I am not
sure if it still works in newer kernels (i wish it did!)...
kernel support for userfs's would be very very cool
On Wed, 12 Jul 1995, Harik A'ttar wrote:
> Reply-to: ind00621@pegasus.cc.ucf.edu
>
> Ok: I had a thought the other day on an FTP fs, similar to NFS and the
> /proc system. Essentally: All it would be is a directory structure.
> I.E. /ftp/dotted.ip.of.host/structure
>
> This would be held in files: probably gzipped ls -lR
>
> if you read a file, it would attempt to connect, and fetch the file
> (into a definable size cache) I.E. you could
> cd /ftp/ftp.cc.gatech.edu/pub/Linux/kernel
> ls
> (provides most recent ls of the directory)
> cat README
> fetches README from the correct dir into buffer, and then cat's it.
>
> Connect-on-demand is supported (lynx, ncftp, etc) so that wouldn't be
> too hard to do. For administratiors: Since, while browsing directory
> listings, they arn't actually CONNECTED to the site, only to fetch a
> file, how much would this reduce load?
>
> Anyway, I havn't more then started looking into this project,
> (mostly looking for a skeleton fs device to pick apart)
> but I would be glad to try my hand at it if people
> thought it was a good idea.
>
------------------------------
From: "William M. Perkins" <bill@grnwood.cais.com>
Date: Sun, 16 Jul 1995 11:46:39 -0400 (EDT)
Subject: Re: Error trying to compile 1.3.9 kernel
> I received the following kerenl compilation error while trying to
> compile the 1.3.9 version. I normally compile the kernel to use
> only the ncr53c810 scsi disk driver. However, this kernel required
> that I compile in one of the ide disk drivers before it would
> produce a zImage file.
>
> >...... much deleted compiler output
Much more deleted compiler output
> > ld -qmagic -Ttext 0xfffe0 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 drivers/scsi/scsi.a drivers/sound/sound.a drivers/pci/pci.a \
> > /usr/src/linux-1.3.9/arch/i386/lib/lib.a /usr/src/linux-1.3.9/lib/lib.a /usr/src/linux-1.3.9/arch/i386/lib/lib.a -o vmlinux
> > genhd.o(.text+0x2ee): undefined reference to `ide_xlate_1024'
> > genhd.o(.text+0x32c): undefined reference to `ide_xlate_1024'
> > make: *** [vmlinux] Error 1
>
> I checked the ./drivers/block/genhd.c file and compared it againist the
> original same file used in 1.3.8 and found some new code for a 'Disk
> Manager'. This code included a few lines simular to the following:
>
> > ide_xlate_1024(dev); /* harmless if not an IDE drive */
>
> Harmless, maybe, but it would not compile for my configuration.
> So, I added the IDE driver to my configuration, and it compiled just
> fine.
>
> Bill
The 1.3.10 kernel patch appears to fix this problem. I patched and recompiled
and now the IDE driver is not required.
Bill
- --
William M. Perkins Internet - bill@cais.cais.com
The Greenwood or - bill@grnwood.cais.com
Commodore is dead. Long lives the Amiga! (AmigaOS/Linux/NetBSD)
------------------------------
From: "Theodore Ts'o" <tytso@MIT.EDU>
Date: Sun, 16 Jul 1995 18:04:31 +0500
Subject: Re: [bug report] umsdos ruins ext2 file system
Date: Mon, 10 Jul 1995 12:41:16 +0200 (MSZ)
From: Michael Weller <eowmob@exp-math.uni-essen.de>
> I think either mount or the kernel should check wether a DOS FAT file system
> is present when mounting a partition as umsdos.
This is easier said as done. mke2fs doesn't touch the devices boot sector.
This is required as mke2fs's job is not to think about booting. Actually
it might be required to not look there as some partition info might lurk
there. The bootsector is simply not part of a partition.
Actually, due to complaints about this issue, 0.5b mke2fs will zap the
boot sector when creates the filesystem.
- Ted
------------------------------
From: Jeff Newbern <jnewbern@babar.mit.edu>
Date: Sun, 16 Jul 1995 17:04:57 EDT
Subject: Take a trip on the Way-Back Machine(tm)
Do you remember those heady days in December '92 when 0.99 was released?
I am compiling a timeline of important events in the development of Linux
for the Linux Publicity Project. 0.99 was released in December of 92.
At that time, Linux had an X server and basic TCP/IP connectivity. Linux
1.0 was not released until March 1994. So what went on for that year?
As I recall, that time was a very expectant time, when everyone was
anxious for 1.0 to be released. There was little new functionality
introduced, it was mostly cleaning up what was there and working toward
stability. The biggest thing I remember from that time was the
networking war (wars?) but I would rather not get into that in the
timeline :-)
So I am appealing to all of you to fill in the gaping hole in my timeline
that is 1993. What were the significant developments in Linux (both
technical and non-technical) during that period.
Thanks for the memories,
Jeff Newbern
==========================================================================
Jeff Newbern Linux Publicity Project http://babar.mit.edu/LPP/LPP.html
==========================================================================
------------------------------
From: Eugenio Jimenez Yguacel <eugenio@Cascorro.teleco.ulpgc.es>
Date: Sun, 16 Jul 1995 23:28:20 +0000 (GMT)
Subject: Re: IP forwarding broken in 1.3.10
On Sun, 16 Jul 1995, Luca Spada wrote:
>
> Hi...
>
> just installed 1.3.10 and IP forwarding/gatewaying is no longer working
> on my Linux. Any idea or is a bug ?
>
> Bye
>
> Luca Spada (skyluke@sun.skylink.it)
>
>
Hi all,
Just the same problem. I have a PPP link between two Linux boxes; one at
home and another one at University (my ISP :-)). I can connect to the
"PPP server" (University) but nothing else. No ping to other machines, no
ftp... The "PPP server" is running with ProxyARP enabled and it do publishes
the route. Of course, the kernel is compiled with IP forwarding too.
This bug? doesn't happen with 1.3.9, only with 1.3.10.
I'm using pppd-2.1.2d
Ideas, comments, blames ???
Good Linuxing
______________________________________________________________
Eugenio Jimenez Yguacel eugenio@cascorro.teleco.ulpgc.es
E.T.S.I. Telelcomunicacion Tfno: (+34)-28-452863
Campus de Tafira S/N Fax: (+34)-28-451243
Las Palmas 35017, Spain
- --------------------------------------------------------------
------------------------------
From: Scott Johnson <johnsos@ECE.ORST.EDU>
Date: Sun, 16 Jul 1995 15:56:39 -0700
Subject: Re: rmdir hangs on bad ext2 directory (1.2.11)
>On Wed, 12 Jul 1995, Marek Michalkiewicz wrote:
>> Just a moment ago I tried to remove a directory which was a file before
>> the filesystem corruption (not detected by e2fsck) caused by bad RAM.
>>
>> The directory disappeared, but rmdir hung, I can't kill it (even -9 doesn't
>> work, I guess I will have to reboot), ps shows it in the R state using over
>> 90% of CPU time. The following message was found in syslog:
>>
>> EXT2-fs warning (device 22/1): empty_dir: bad directory (dir 46195)
>>
>We've had the exact same thing happen here, running a vanilla 1.3.4
>kernel. What I'd take this to mean is that something between the system
>call and the e2fs code is broken, though I'm not expert on such things.
>I'd also take this to mean it hasn't been fixed yet. :-)
>We were running rmdir on a fairly heavily used drive, mounted as
>/var/spool/news. Very annoying problem. Anyone had this happen with rm, BTW?
>> Just an idea: how about CRC checksums for inodes? This would allow easy
>High overhead?
I've been having a similar problem (rather rarely) on my system as well. I've
got 1.2.10 running, and my entire Linux filesystem is mounted on a single
partition (about 200 Mbytes, I've considered repartitioning to give Linux
more, and OS/2 Warp less space, but thats another story.) The drive is a WD
540 "Caviar" drive, (the device is /dev/hdb5, in case that matters). Every
once in a while, some process will try to access the /var/adm directory, and
for some reason die (enter uninterruptable sleep). When this happens, the
HD makes a strange noise, similar to being powered up for the first time. (My
PC is a desktop, so the HD should not be spinning down for any reason...) It
may be hardware trouble, it may be something Linux is doing, I dunno. At any
rate, ANY process which tries to access this directory (/var/adm) gets put to
sleep. syslogd is usually the first to die, but init soon follows. Any
process which terminates after, instead of dying gracefully, becomes a
zombie. And
shutting down properly with a hung init process is a pain... :) I end up having
to give the computer the One Fingered Salute (shutdown hangs when trying to
kill off these hung processes), and pray when I reboot and run fsck.
As I said, it MIGHT be a HD problem (can anyone reccommend a good utility to
analyze the media of the HD non-destructively? BIOS has a media analysis tool,
but it erases everything). However, if the hardware fails, I don't think the
correct way for Linux to respond is to cause processes to hang. Anyone have
any ideas?
Thanks,
Scott
------------------------------
From: andrew@zycad.com (Andrew Pollard)
Date: Sun, 16 Jul 95 19:31:10 BST
Subject: Modules in 1.3.10 and other things
Hello World,
I have been using/trying to use the 1.3.10 kernel.... here are a number of
comments.....
For information I am running gcc-2.6.2, libc-4.6.27, modules-1.2.8 on a
16M 486DX2/66.
[ I haven't braved ELF yet :-) BTW when is a newer libc-5 coming out? I seem
to remember hearing that there are bugs in the current libc-5.0.9 version ]
Problems when configuring the kernel with module support:
[ I have been getting something similar for ages... I just don't like getting
warnings while compiling things :-) ]
- -------------------------------------------------------------------------------
make[1]: Entering directory `/usr/src/linux-1.3.10/kernel'
gcc -D__KERNEL__ -I/usr/src/linux-1.3.10/include -Wall -Wstrict-prototypes -O2
- -fomit-frame-pointer -pipe -m486 -E -DCONFIG_MODVERSIONS -D__GENKSYMS__ ksyms.c
| /sbin/genksyms -w /usr/src/linux-1.3.10/include/linux/modules
genksyms "ksyms.c": warning: symbol [do_mmap]: unknown 'struct sem_undo'
genksyms "ksyms.c": warning: symbol [do_mmap]: unknown 'struct sem_queue'
genksyms "ksyms.c": warning: symbol [do_mmap]: unknown 'struct minix_super_bloc
k'
genksyms "ksyms.c": warning: symbol [do_mmap]: unknown 'struct ext2_super_block
'
genksyms "ksyms.c": warning: symbol [inet_add_protocol]: unknown 'struct sock'
genksyms "ksyms.c": warning: symbol [inet_add_protocol]: unknown 'struct ip_mc_
list'
genksyms "ksyms.c": warning: symbol [inet_add_protocol]: unknown 'struct udphdr
'
updating /usr/src/linux-1.3.10/include/linux/modversions.h
- -------------------------------------------------------------------------------
Problems with make modules:
[ several compiler warnings, and a total failure with the scsi stuff ]
- -------------------------------------------------------------------------------
make[1]: Entering directory `/usr/src/linux-1.3.10/kernel'
make[1]: Nothing to be done for `modules'.
make[1]: Leaving directory `/usr/src/linux-1.3.10/kernel'
make[1]: Entering directory `/usr/src/linux-1.3.10/drivers'
set -e; for i in block char net scsi ; do make -C $i modules; done
make[2]: Entering directory `/usr/src/linux-1.3.10/drivers/block'
[ all ok ]
make[2]: Leaving directory `/usr/src/linux-1.3.10/drivers/block'
make[2]: Entering directory `/usr/src/linux-1.3.10/drivers/char'
[ all ok ]
make[2]: Leaving directory `/usr/src/linux-1.3.10/drivers/char'
make[2]: Entering directory `/usr/src/linux-1.3.10/drivers/net'
[ most ok ]
gcc -D__KERNEL__ -I/usr/src/linux-1.3.10/include -Wall -Wstrict-prototypes -O2
- -fomit-frame-pointer -pipe -m486 -DMODULE -DCONFIG_MODVERSIONS -c 3c501.c
3c501.c:78: warning: `version' defined but not used
3c501.c:312: warning: `el_open' defined but not used
3c501.c:334: warning: `el_start_xmit' defined but not used
3c501.c:630: warning: `el1_close' defined but not used
3c501.c:650: warning: `el1_get_stats' defined but not used
3c501.c:663: warning: `set_multicast_list' defined but not used
gcc -D__KERNEL__ -I/usr/src/linux-1.3.10/include -Wall -Wstrict-prototypes -O2
- -fomit-frame-pointer -pipe -m486 -DMODULE -DCONFIG_MODVERSIONS -c wavelan.c
wavelan.c: In function `wavelan_dev_show':
wavelan.c:2450: warning: int format, long int arg (arg 2)
gcc -D__KERNEL__ -I/usr/src/linux-1.3.10/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -pipe -m486 -DMODULE -DCONFIG_MODVERSIONS -DDE4X5_DEBUG=1
-DDE4X5_AUTOSENSE=AUTO -c de4x5.c
de4x5.c: In function `de4x5_queue_pkt':
de4x5.c:976: warning: int format, long int arg (arg 4)
make[2]: Leaving directory `/usr/src/linux-1.3.10/drivers/net'
make[2]: Entering directory `/usr/src/linux-1.3.10/drivers/scsi'
make[2]: *** No rule to make target `scsi_syms.ver'. Stop.
make[2]: Leaving directory `/usr/src/linux-1.3.10/drivers/scsi'
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/linux-1.3.10/drivers'
make: *** [modules] Error 2
- -------------------------------------------------------------------------------
Sound driver problems:
- -------------------------------------------------------------------------------
....
The sound driver is now configured.
Usage: hostname [-f] [name]
make[1]: Leaving directory `/usr/src/linux-1.3.10/drivers/sound'
The makefile drivers/sound/Makefile line 52 calls hostname -d to get the
domainname, but Slackware 2.2 doesn't support that option (you need domainname
instead)
- -------------------------------------------------------------------------------
Other problems:
- -------------------------------------------------------------------------------
While trying to compile tcl7.4, the autoconfigure stuff complains about having
a buggy vfork inplementation...
> checking Solaris 2.4 vfork/signal bug... buggy
It seems that the child can override the the SIGCHLD signal handler.
I assume linux *shouldn't* have this bug... but it seems to :-(
[ I guess this may be in libc, not the kernel - I'm using 4.6.27 ]
Here's the bit of the configure script that does the test...
#--------------------------------------------------------------------
# Check to see whether the system provides a vfork kernel call.
# If not, then use fork instead. Also, check for a problem with
# Solaris 2.4 and vforks and signals that can core dumps can occur
# if a vforked child resets a signal handler. If the problem
# exists, then use fork instead of vfork.
#--------------------------------------------------------------------
if test "$tcl_ok" = 1; then
echo $ac_n "checking Solaris 2.4 vfork/signal bug""... $ac_c" 1>&6;
if test "$cross_compiling" = yes; then
{ echo "configure: error: can not run test program while cross compiling" 1>&2; exit 1; }
else
cat > conftest.$ac_ext <<EOF
#line 2064 "configure"
#include "confdefs.h"
#include <stdio.h>
#include <signal.h>
#include <sys/wait.h>
int gotSignal = 0;
sigProc(sig)
int sig;
{
gotSignal = 1;
}
main()
{
int pid, sts;
(void) signal(SIGCHLD, sigProc);
pid = vfork();
if (pid < 0) {
exit(1);
} else if (pid == 0) {
(void) signal(SIGCHLD, SIG_DFL);
_exit(0);
} else {
(void) wait(&sts);
}
exit((gotSignal) ? 0 : 1);
}
EOF
eval $ac_link
if test -s conftest && (./conftest; exit) 2>/dev/null; then
echo "$ac_t""ok" 1>&6
else
echo "$ac_t""buggy" 1>&6
tcl_ok=0
fi
fi
rm -fr conftest*
fi
rm -f core
if test "$tcl_ok" = 0; then
cat >> confdefs.h <<\EOF
#define vfork fork
EOF
fi
- -------------------------------------------------------------------------------
Also, what is the status of the kerneld stuff for 1.3.x? I'd like to try
this lot out again (I tried briefly with 1.2.8 and it sort of worked as far as
I can remember).
Another thing, is there any real need to use the new IDE controller stuff if
all you have is hard disks? I ask because the new stuff needs me to put
hdb=noprobe as a boot option, whereas the old stuff didn't (I read about this
in the readme) - I've got a 1Gb WD31000H disk.
Any comments on this lot?
PS. I haven't received a kernel digest for about 10 days now.. Has something
gone horribly wrong? Someone please mail me if they see this. Anyway I reported
a problem with 1.3.9 about the old IDE hd controller not compiling, and this
was fixed in 1.3.10... was my message seen (or more likely, did someone else
(or others) spot the problem)? Possibly ignore that lot, just spotted that I
got three of them over the weekend....
Andrew
===============================================================================
| Andrew Pollard, Zycad RP Division (InCA) UK | Work: andrew@zycad.com |
| Tel:+44(0)1344 51515 Fax:+44(0)1344 421231 | Home: Andrew@odie.demon.co.uk |
===============================================================================
------------------------------
End of linux-kernel-digest V1 #118
**********************************