Subject: Linux-Development Digest #957
From: Digestifier <Linux-Development-Request@senator-bedfellow.MIT.EDU>
To: Linux-Development@senator-bedfellow.MIT.EDU
Reply-To: Linux-Development@senator-bedfellow.MIT.EDU
Date:     Thu, 28 Jul 94 16:13:12 EDT

Linux-Development Digest #957, Volume #1         Thu, 28 Jul 94 16:13:12 EDT

Contents:
  Re: Panasonic CD-ROM broke under >1.1.31 (NJ. Bruton)
  Re: threads in kernel (Rob Janssen)
  Re: Networking very slow (Rob Janssen)
  Re: Dosemu won't work with >1.1.29 <1.1.35 and (Lutz Molgedey)
  Re: 1.1.36 make problem: 'NULL' undeclared (Matthias Urlichs)
  Re: New kernel message at boot time? (Matthias Urlichs)
  Re: 1.1.35 make problem: exhausted memory (Peter Schmitt)
  Re: Ooops! SCSI CD-Rom broken in 1.1.33 (Stephane Boyer)
  Re: threads in kernel (Peter Mutsaers)
  Re: threads in kernel (Patrick Schaaf)
  insmod and iBCS (darryl@burke.north.net)
  Re: 1.1.36 make problem: 'NULL' undeclared (BARRY TITMARSH)
  Re: 1.1.36 make problem: 'NULL' undeclared (Sean McCarthy)
  Re: 1.1.36 make problem: 'NULL' undeclared (Sean McCarthy)
  question about game port (Michael Cain)
  Re: Interest in a new (up to date) LaTeX dist.? (Michael Griffith)
  Re: Panasonic CD-ROM broke under >1.1.31 (Eberhard Moenkeberg)
  Thanks, all! (Randy Chapman)
  Re: Voice Mail cards. (Russell Nelson)
  Re: FYI -- context switching times (Larry McVoy)
  Re: New kernel message at boot time? (Michael Haardt)
  Cannot Compile New Kernel (Aston Martin)

----------------------------------------------------------------------------

From: ccnjb@sun.cse.bris.ac.uk (NJ. Bruton)
Subject: Re: Panasonic CD-ROM broke under >1.1.31
Date: Tue, 26 Jul 1994 08:56:35 GMT

Tim (tims@kcbbs.gen.nz) wrote:
: lcvanveen@et.tudelft.nl wrote:
: : When mounting my CD-ROM (panasonic cr-562b) under 1.1.35 I got
: : this nice error:
: : mount: block device /dev/sbpcd is not permitted on its filesystem
: : It wasn't in at 1.1.30 so it came later (I presume at 1.1.32).
: : Does anybody have a fix here.

As of 1.1.3? something you have to mount the cd read-only
Nick

------------------------------

From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: threads in kernel
Reply-To: pe1chl@rabo.nl
Date: Thu, 28 Jul 1994 06:10:31 GMT

In <316l9f$rpt@Times.Stanford.EDU> lm@stanford.edu (Larry McVoy) writes:

>  Light weight threads in a single process are 
>going to be fast but useless.  Useful threads context switch slowly.
>Explanation: light weight user level threads don't have a kernel context,
>i.e., if any thread blocks in a read() then they all block.  Useless.
>Fast, but useless.

I disagree with that.  It depends on your requirements.
I have been able to use a (very simple) lightweight threads package quite
successfully in many instances where a non-preemptive multithreading model
made a program much simpeler to design and implement, and where the blocking
in system calls was no problem at all.

Please note that lightweight threads have advantages, and that these may
well outweigh the above disadvantage when using them on existing systems.

Rob
-- 
=========================================================================
| Rob Janssen                | AMPRnet:   rob@pe1chl.ampr.org           |
| e-mail: pe1chl@rabo.nl     | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU     |
=========================================================================

------------------------------

Crossposted-To: comp.os.linux.help,comp.os.linux.misc,comp.os.linux.help
From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: Networking very slow
Reply-To: pe1chl@rabo.nl
Date: Thu, 28 Jul 1994 06:13:01 GMT

In <316osa$fsb@hermes.unt.edu> john@gab.unt.edu writes:

>Hi, I've got a bit of a problem--my networking is extremely slow--telnet to machine
>can take up to 2 min to actually connect.  It doesn't look as if the local net
>is overflowing with packets everywhere.  The 3c509 network card I am using is
>supposed to be a very quick card.

You probably have a problem with the configuration of your name
services.  Decide if you want to run a nameserver, find out where the
nameserver (if any) resides on your network, and then check the content
of "/etc/host.conf" and "/etc/resolv.conf".

Rob
-- 
=========================================================================
| Rob Janssen                | AMPRnet:   rob@pe1chl.ampr.org           |
| e-mail: pe1chl@rabo.nl     | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU     |
=========================================================================

------------------------------

From: molgedey@theo-physik.uni-kiel.de (Lutz Molgedey)
Subject: Re: Dosemu won't work with >1.1.29 <1.1.35 and
Date: 27 Jul 1994 08:39:56 GMT
Reply-To: molgedey@theo-physik.uni-kiel.de

In article 4029@tudedv.et.tudelft.nl, lcvanveen@et.tudelft.nl writes:
> Last week I rebuild Linux to version 1.33 and noticed dosemu0.52 
> wouldn't work anymore. The screen went black and the only thing 
> I could do was shutdown with crtl-alt-del. This morning I went 
> over to Linux 1.1.35 and recompiled dosemu again. I still won't 
> work. I does in an xterm, but goes black in a VC. I then set 
> commented aout the S3-support and the direct access to the 
> videoport and got a segmentation fault that brought Linux to a 
> complete standstill. The only thing I could do was reset my poor 
> machine.
> Does anybody know what's changed within Linux VC support that 
> Thanks a lot in advance.
> Martijn

Starting with kernel 1.1.31 Linus has changed the mmap() stuff. Hence use
1.1.30- or wait for the new dosemu 0.53 :-).

Lutz.
---
Lutz Molgedey                    |molgedey@theo-physik.uni-kiel.de
Institut f|r Theoretische Physik |http://www.theo-physik.uni-kiel.de/~molgedey 
Olshausenstr. 40                 |Tel. (+49/431)8804071
D-24118 Kiel                     |Fax. (+49/431)8804094



------------------------------

From: urlichs@smurf.noris.de (Matthias Urlichs)
Subject: Re: 1.1.36 make problem: 'NULL' undeclared
Date: 28 Jul 1994 14:08:30 +0200

In comp.os.linux.development, article <31633d$hie@news.doit.wisc.edu>,
  mja@venus.telecom.wisc.edu (Michael Adas) writes:
> 
> I fixed this by putting this at the top of timer.h:
> 
> #ifndef NULL
> #define NULL ((void *) 0)
> #endif
> 
Why don't you just include the file where NULL _is_ defined, i.e.
linux/types.h?

-- 
Electricians do it with spark.
-- 
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

Click <A HREF="http://smurf.noris.de/~urlichs/finger">here</A>.

------------------------------

From: urlichs@smurf.noris.de (Matthias Urlichs)
Subject: Re: New kernel message at boot time?
Date: 28 Jul 1994 14:14:51 +0200

In comp.os.linux.development, article <DHOLLAND.94Jul27104017@scws34.harvard.edu>,
  dholland@scws34.harvard.edu (David Holland) writes:
> 
> (After all, I would have expected to find the .34 "new" swap behavior
> all along, too.)
> 
The new swap behavior means that swapped-in pages stay allocated in swap
space after they're brought back in. In fact, I had to increase swap on one
machine after switching to 1.1.36. There's also more memory overhead in the
kernel 'cause since the page is in memory you can't use the page table
entry to remember where it is in swap space.

All taken together, the new scheme is a win for everybody, even if you do
need a bit more swap space and even if you do have a bit less memory to
work with. (But that happens with nearly every kernel release...)

-- 
The Third Law of Photography:
       If you did manage to get any good shots, they will be ruined
       when someone inadvertently opens the darkroom door and all of
       the dark leaks out.
-- 
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

Click <A HREF="http://smurf.noris.de/~urlichs/finger">here</A>.

------------------------------

From: pete@geminga.dartmouth.edu (Peter Schmitt)
Crossposted-To: comp.os.linux.admin
Subject: Re: 1.1.35 make problem: exhausted memory
Date: 28 Jul 1994 11:25:57 GMT

danw@connected.com (Dan Wilder) writes:

>pcsigler@whale.st.usm.edu (Peter C. Sigler) writes:

>>Peter Schmitt (pete@geminga.dartmouth.edu) wrote:
>>: My 386 has 5M ram and 5M swap.  I am currently running 1.1.34 and got
>>: the following when trying to make 1.1.35:

>>I think this is a problem with the memory handling in 34.
>>I tried to compile 35, as well, under 34 and got the same
>>thing. My system is a 386/40 w/5Meg ram and 10meg swap.

>That isn't a lot of room.  Try running 'top' to see what the situation
>is.  I suspect with 5 meg RAM and 10 meg swap, you are nearing swap
>full compiling the kernel even with earlier kernels.  'Course it
>could be the memory handling.

I solved this from a tip from a previous posting to my problem.  I
went back and rebooted a 1.0.9 kernel and then was able to make 1.1.35
and 1.1.36 successfully.

-pete
--
peter.schmitt@dartmouth.edu             Computing Services
UNIX Systems Specialist                 Dartmouth College
Phn: 603-646-2085                       6028 Kiewit Computation Center
postmaster@dartmouth.edu                Hanover, NH  03755

------------------------------

From: s_boyer@smegheads.montreal.qc.ca (Stephane Boyer)
Subject: Re: Ooops! SCSI CD-Rom broken in 1.1.33
Date: Thu, 28 Jul 1994 03:44:52 GMT

Rob Janssen (rob@pe1chl.ampr.org) wrote:
: In <1994Jul26.021022.964@encomix.exnet.com> rampa@encomix.exnet.com (Ramon Martinez) writes:


: >:>Error:
: >:>root:/home/cjs# mount /dev/cdrom /system_cd/ -t iso9660
: >:>mount: block device /dev/cdrom is not permitted on its filesystem
: >:>root:/home/cjs#


: >  Not only on SCSI. i have the same here with a Double Speed Panasonic. 
: >(SBPCD).

: >  It works fine in 1.1.31 but fails in 1.1.32 to 1.1.35

: > -Ramon-

: How about first reading some of the other postings on this subject??

This is the last time i write this, people 

a cdrom is a READ ONLY device so mounting READ/WRITE should give you an
error message!

now when moounting a cdrom you have to use: 

        mount -t iso9660 -o ro /dev/cdrom /cdrom
                         ^^^^^

defines device as READ ONLY!

Steph!
-- 
 \    s_boyer@smegheads.montreal.qc.ca    /  Data: (514)457-0093  /
  >-------------------------------------<  Login: guest          <
 /        S  M  E  G  H  E  A  D  S      \    Passwd: <none>      \
|    The Red Dwarf Appreciation Society   |------------------------|

------------------------------

From: plm@sci.kun.nl (Peter Mutsaers)
Subject: Re: threads in kernel
Date: Wed, 27 Jul 1994 08:24:46 GMT

In <313igq$i33@Times.Stanford.EDU> lm@stanford.edu (Larry McVoy) writes:

>Could you please explain what you mean by threads?  Are talking about
>Sun like threads, where there are two sorts of processes, processes
>that map 1:1 with an address space and processes (threads) that map
>many:1 with an address space?  I personally think this is the wrong
>approach.

>SGI has a model which is like the clone() stuff discussed here recently.
>A "thread" is simply a new process that happens to share (part of) the 
>parent's address space.  That is easy to implement, easy to scale, and
>simple.

There are two problem2 with these SGI 'threads' however:
a) not POSIX compliant.
b) very slow context switches! Even a little bit slower than between normal
   processes. Not strange, because these 'threads' (sproc's in SGI-speak)
   are full-blown processes that have a process table entry. They are
   *not* multiple (light-weight) threads within one process.
--
Peter Mutsaers                  |
plm@sci.kun.nl                  |  "...En?..., doet ie het al?"

------------------------------

From: bof@wg.saar.de (Patrick Schaaf)
Subject: Re: threads in kernel
Date: Thu, 28 Jul 1994 14:54:05 GMT

lm@stanford.edu (Larry McVoy) writes:

>The idea behind a clone() or tfork() system call is that the only thing
>that you get is a new stack (it would be nice, I think, if the new stack
>was at the same virtual address as the old stack; it saves you having to
>rethread it).

On the other hand, this means that you can no longer share the page
directory. One of the potential speed advantages of clone()ed vs. fork()ed
context switch is that you don't have to change the address space at all.
I have no hard data on this, but I think not flushing the TLB will be
a good thing for tightly coupled clones. Larry, you don't happen to
have a benchmark for this handy, do you?

>       open()/close() - does it affect the other process (yes)

Not with clone(), currently. SHAREFD is not yet implemented.

>If anyone is seriously working on this, please contact me and I will help.

To the person(s) that said they are working on this: Can you post some
kind of design document about what you are attempting to do? Do you
build on the clone() paradigm, or are you inventing your own?
Wouldn't it be nice if we had a nice technical discussion on c.o.l.d
for a change? :)

Patrick

------------------------------

From: darryl@burke.north.net
Subject: insmod and iBCS
Date: Sun, 24 Jul 1994 23:33:40 GMT


I'm trying to install ibcs and I'm getting the following errors while trying to use "insmod"

_input undefined
_printk undefined
_do_execve undefined
..
..
..
..
..
..
___get_free_pages undefined


Are there some options i'm missing when i'm compiling the kernel (v1.1.23)


Darryl Burke
darryl@burke.north.net


------------------------------

Date: Thu, 28 Jul 1994 16:21:37 EST
From: BARRY TITMARSH <BTITMARS@ESOC.BITNET>
Subject: Re: 1.1.36 make problem: 'NULL' undeclared

Interesting thread.. Ill have to print it all out.
Ok I did: patch -p0 etc  patch36
make dep && make  and i did not see this error at all?
i have 1.1.36 up running now for 23hrs no problems.
must admit i did not do make clean first..
its was lunchtime and i wanted a quick compile.. hi.
Barry.

------------------------------

From: wx8l@vtc.tacom.army.mil (Sean McCarthy)
Subject: Re: 1.1.36 make problem: 'NULL' undeclared
Date: 28 Jul 1994 11:48:20 -0400

BTITMARS@ESOC.BITNET (BARRY TITMARSH) writes:
: Interesting thread.. Ill have to print it all out.
: Ok I did: patch -p0 etc  patch36
: make dep && make  and i did not see this error at all?
: i have 1.1.36 up running now for 23hrs no problems.
: must admit i did not do make clean first..
: its was lunchtime and i wanted a quick compile.. hi.
: Barry.

You, apparently, do not run a PS/2 mouse.
Sean


------------------------------

From: wx8l@vtc.tacom.army.mil (Sean McCarthy)
Subject: Re: 1.1.36 make problem: 'NULL' undeclared
Date: 28 Jul 1994 11:01:13 -0400

I usually dont get involved in this, but per Linus:

move the line  "#include <linux/timer.h>"

down a few lines, so its the last "#include"

in psaux.c, like this:

#include <linux/sched.h>
#include <linux/kernel.h>
#include <linux/fcntl.h>
#include <linux/errno.h>

#include <asm/io.h>
#include <asm/segment.h>
#include <asm/system.h>

#include <linux/config.h>
#include <linux/timer.h>


Simple and it works.

Sean



------------------------------

From: mcain@advtech.uswest.com (Michael Cain)
Subject: question about game port
Date: 28 Jul 1994 15:56:50 GMT


This may be a dumb question, but a quick look through various FAQs and
HOW-TOs didn't get me an answer:  does there exist linux support for a
joystick attached to the game port?  There seems to be a device major
number reserved for the purpose, but I haven't come across any code or
pointers to code that actually implement the device...

Thanks in advance
Mike Cain
U S WEST Advanced Technologies
Boulder, CO, USA
mcain@advtech.uswest.com

------------------------------

From: grif@tempest.ucr.edu (Michael Griffith)
Subject: Re: Interest in a new (up to date) LaTeX dist.?
Date: 28 Jul 1994 16:39:16 GMT

In article <318m8o$nf6@vixen.cso.uiuc.edu>,
Byron Faber <btf57346@uxa.cso.uiuc.edu> wrote:
>I am curious whether there is enough interest in a new up to date LaTeX 
>distribution?
>
>If enough people want one, I can put together a LaTeX distribution based
>on the June release standard of LaTeX 2e.

You might want to also include web2c 6.1 (w/TeX 3.1415), xdvik-1.8,
and dvipsk 5.55a.  It is nice to have the newest of everything.
-- 
Michael A. Griffith (grif@cs.ucr.edu)
Department of Computer Science
University of California, Riverside


------------------------------

Date: Thu, 28 Jul 1994 03:16:43 +0200
From: Eberhard_Moenkeberg@p27.rollo.central.de (Eberhard Moenkeberg)
Subject: Re: Panasonic CD-ROM broke under >1.1.31


Hello lcvanveen and all others,

on 25.07.94 lcvanveen wrote to All in USENET.COMP.OS.LINUX.DEVELOPMENT:

l> When mounting my CD-ROM (panasonic cr-562b) under 1.1.35 I got
l> this nice error:
l> mount: block device /dev/sbpcd is not permitted on its filesystem

All CDROM devices have to get mounted explicitely "read-only" now.

Someone saw a bug within one driver, and so all drivers got changed.

Let's hope that NFS mounts will not be the next (but, if someone
is willing to restrict NFS mounts, too: -ENXIO would look nice,
and probably really noone would understand the message. :-)

Greetings ... Eberhard


------------------------------

From: chapman@u.washington.edu (Randy Chapman)
Subject: Thanks, all!
Date: 28 Jul 1994 04:23:29 GMT

(seeing as I don't know where else this ought to go ... :)

THANKS ALL FOR SUCH A GREAT SYSTEM!

As a side note, 1.1.36 seems to be a GREAT improvement speedwise for me.  It 
seems to boot significantly faster than 1.1.27 and 1.1.18 ever did.  X programs
(like xterm) also seem to pop up and resesitate (sp!) faster than before (I
have 6mb of ram on a 486dlc/20 w/ a sun3/60 as a display, for the record.  My
HD is an slower elderly IDE w/o multimode support).

Good work all!

Randy Chapman
LLR Obed BBS SysOp (206)485-8854


------------------------------

From: nelson@crynwr.crynwr.com (Russell Nelson)
Crossposted-To: comp.dcom.modems,comp.os.linux.help
Subject: Re: Voice Mail cards.
Date: 26 Jul 1994 15:00:30 GMT

In article <MATT.94Jul25100233@eve.albany.edu> matt@csc.albany.edu (Matt Womer) writes:

   In article <3104sq$m2@brachio.zrz.TU-Berlin.DE> jorgagif@w250zrz (Joerg Mertin) writes:

   > By the Way, I also have an Phone-Answering System Working with a
   > U-1496 E Zyxel and vgetty that mails me the incoming call to the Phone
   > Administrator. So, why buy such special things ???

   My original question was not clear enough, I wish to buy a voice mail card
   that answers the phone and can store and retrieve messages stored on the
   computer.

Buy a ZyXEL modem, and run mgetty+sendfax.  It does voice handling.

--
-russ <nelson@crynwr.com>    http://www.crynwr.com/crynwr/nelson.html
Crynwr Software   | Crynwr Software sells packet driver support | ask4 PGP key
11 Grant St.      | +1 315 268 1925 (9201 FAX)  | What is thee doing about it?
Potsdam, NY 13676 | LPF member - ask me about the harm software patents do.

------------------------------

From: lm@stanford.edu (Larry McVoy)
Subject: Re: FYI -- context switching times
Date: 28 Jul 1994 18:13:55 GMT

Oh, shit.  Sorry folks, but I suspect that there are two benchmarks
being mixed here.  I wrote one, posted it a while ago, and then
realized that a substantial amount of the reported time was not the
context switch.  I fixed that and the numbers get a bit smaller.
I have a whole suite of such benchmarks and I promise I will post 
them all by Friday.  Or redirect /usr/spool/news/alt/flame into my
mailbox :-)

Gustaf Neumann (neumann@watson.ibm.com) wrote:
: In article <313n9m$hoh@jac.zko.dec.com> from [26 Jul 1994 19:13:58 GMT]
:  feingold@avette.zko.dec.com (Elan Feingold)  wrote:
: 
:  |> Got this off of a *.os.* group:
:  |> 
:  |> Date: Wed, 9 Feb 94 14:56:13 PST
:  |> From: Larry.McVoy@eng.sun.com (Larry McVoy)
:  |> To: dck@cse.nd.edu
:  |> 
:  |> 68     99 Mhz HP-735 HP-UX 9.01
:  |> 80     33 MHz 486DX QNX 4.2
:  |> 87    160 Mhz DEC 4000/610 DEC OSF/1 v1.3
:  |> 98     40 MHz R3000 DEC 5000/240 Ultrix 4.2
:  |> 98     66 MHz 486DX2 Linux 0.99.10        ***** Cool! *****
:  |> 102     62 MHz IBM-RS6000/580 AIX 3.2
:  |> 106     66 Mhz snake HP-UX 9.x
:  |> 128     40 Mhz SS10 SunOS 4.1.3
:  |> 154     25 MHz R3000 DEC 5000/200
:  |> 158     50 MHz R4000 SGI
:  |> 188     48 Mhz + 1Me$ SS10 SunOS 5.2
:  |> 198     33 MHz Sparc 4/470 SunOS 4.1.1
:  |> 210     33 Mhz 486 386BSD 0.1
:  |> 212     50 Mhz RIOS AIX 3.2
:  |> 225     40Mhz SS10 SunOS 5.2
:  |> 230     40Mhz SS2 SunOS 4.1.2
:  |> 281     20 MHz R3000 DEC 5000/120
:  |> 345     33 MHz R3000/3010 SGI Irix 4.0.5
:  |> 380     33 MHz 486 NetBSD
:  |> 454     40Mhz SS2 SunOS 5.2
:  |> 628     50Mhz Sparc classic SunOS 5.2
:  |> 
:  |> %Title Context switch times in microseconds (raw numbers)
:  |> 
:  |> I wonder how we do with the later kernels...
:  
:  well, on my 90MHz Pentium, single user mode, Larry's context switch
:  timing program gives the following numbers (microseconds/switch)
:  in five consecutive runs
:  
:  Linux 1.1.27     41; 38; 38; 38; 41
:  Linux 1.1.35     40; 42; 41; 42; 42
:  
:  It looks, like recent Linux versions on a Pentium 90MHz have the lead
:  amont the machines listed above
: 
: -gustaf
: PS: i used the context switch program of Larry McVoy <lm@slovax.Eng.Sun.COM>
: posted in comp.arch,comp.benchmarks on 18 Jun 1993 22:30:21 GMT 
: with message id <m24gftINN3no@appserv.Eng.Sun.COM>
: 
: --
: Gustaf Neumann                     neumann@watson.ibm.com
: Postdoctoral/Visiting Scientist    Tel: (914) 784 7086
: IBM T.J.Watson Research Center, P.O.Box 704
: Yorktown Heights, New York 10598
: 

--
--
Larry McVoy                     lm@cs.stanford.edu               (415) 821-5758

------------------------------

From: Michael Haardt <(michael)u31b3hs@pool.informatik.rwth-aachen.de>
Subject: Re: New kernel message at boot time?
Date: Mon, 25 Jul 94 23:07:23 MET

torvalds@cc.Helsinki.FI (Linus Torvalds) writes:
> Idea and original code by Dmitry Gorodchanin, btw, with some rather
> heavy hacking by me.  People with 4MB machines might like to test out
> 1.1.34: it should be reasonably stable and I'd really like to have some
> comments (timings if possible) by a few testers who have less memory
> than most of the normal kernel testers..  (people who test out the
> latest kernel tend to have at least 8MB in their machines). 

I just got 1.1.35, and I would love to test it because I have a spare 
machine for that now, but first of all it needs to be booted with root 
fs on floppy to install it.  My problem:

VFS: Insert root floppy and press ENTER
floppy I/O error
dev 0200, sector 0
VFS: Disk change detected on device 2/0
floppy I/O error
...

I tried other floppies and all of them work fine on other machines.  I
tried 1.1.33 before, with the same result, even with FDC_FIFO_UNTESTED
and FDC_FIFO_BUG undefined.  Changing the initialisation of fdc_version
does not change anything either.

I put some debugging output after each result() call, and all that is
ever printed are the register contents from the result() in
floppy_init() (0x80 0x0 0x0 0x0) and in check_readonly() (0x20 0x0 0x0
0x0 the first time and 0x30 0x0 0x0 0x0 later).  I changed ST3
back to st[3] for that, but leaving it as it is does not change the 
output of st[0..2].

There is nothing special to say about the floppy controller, it is a
common MFM HD/FD combi controller.  It never gave trouble before, and
it worked fine with version 1.0 last time I tested.  I boot from that
floppy, so it does work.

Michael
--
Twiggs and root are a wonderful tree (tm) Twiggs & root 1992 :-)

------------------------------

From: wnchan@encserver (Aston Martin)
Subject: Cannot Compile New Kernel
Date: Wed, 27 Jul 1994 17:49:56 GMT

Hi all,

        I have just download the Linux kernel 1.1.33 source code and the
patch34, 35 and 36 . When I started to compile the kernel 1.1.33, I found 
that there was errors in the linking stage. I think that my linker 
(/usr/bin/ld) is too old and cannot accept the option -qmagic. 

        Where I can get the updated version of ld which can accept the 
-qmagic option?


Thanks in advance

Aston Martin.



------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: Linux-Development-Request@NEWS-DIGESTS.MIT.EDU

You can send mail to the entire list (and comp.os.linux.development) via:

    Internet: Linux-Development@NEWS-DIGESTS.MIT.EDU

Linux may be obtained via one of these FTP sites:
    nic.funet.fi				pub/OS/Linux
    tsx-11.mit.edu				pub/linux
    sunsite.unc.edu				pub/Linux

End of Linux-Development Digest
******************************
