Subject: Linux-Activists Digest #54
From: Digestifier <Linux-Activists-Request@BLOOM-PICAYUNE.MIT.EDU>
To: Linux-Activists@BLOOM-PICAYUNE.MIT.EDU
Reply-To: Linux-Activists@BLOOM-PICAYUNE.MIT.EDU
Date:     Sat, 11 Apr 92 07:15:12 EDT

Linux-Activists Digest #54, Volume #2            Sat, 11 Apr 92 07:15:12 EDT

Contents:
  Re: Meta-Question (Theodore Y. Ts'o)
  Custom setups: RFD (Michael K. Johnson)
  How to FORMAT a floppy in Linux? (M. Saggaf)
  Re: Custom setups: RFD (Drew Eckhardt)
  Re: Custom setups: RFD (Drew Eckhardt)
  Re: Problems with serial port drivers?? (Mika Pekka Liljeberg)
  Re: Problems with serial port drivers?? (Mika Pekka Liljeberg)
  What is LINUX? (T. Kendelbacher OT133)
  smail 3.1.25 (david nugent)
  Re: kernel building problems (Linus Benedict Torvalds)
  Re: kernel building problems (Mika Pekka Liljeberg)

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

From: tytso@athena.mit.edu (Theodore Y. Ts'o)
Subject: Re: Meta-Question
Date: Sat, 11 Apr 1992 03:39:48 GMT

In article <1992Apr10.173427.15796@cs.cornell.edu> murthy@cs.cornell.edu (Chet Murthy) writes:
>  What relation does Linux have to the GNU  Hurd Project?
>  Essentially, what I'm trying to figure out, is why all
>  this work on Linux is being done in what seems complete
>  disconnection from GNU, when the aims of this group,
>  and GNU in general, are almost identical.

Well, Linux is being distributed under the GNU GPL, and most of its
utilities are the GNU utilities, including the GNU C compiler and the
GNU shell bash.  Other than that, not much.

One big difference between Linux and GNU Hurd is that Linux works now.
In fact, Linux was the first working free Unix to be generally
available.  Hurd can (sort of) boot and be useful, but it's not very
stable at all.  While Linux is hardly commercial production quality,
it's stable enough for a large number of people to do development, which
is simply not true of the other free Unix systems out there.

The big difference between Hurd and Linux is that Hurd is Big.  (At the
very least, it has been Architected Big.)  If you wish, think of Hurd as
GNU Emacs, and think of Linux as /bin/ed or vi.  Seen in this light, it
is hardly surprising that Linux has reached stability first, despite the
fact that the people at GNU have been working on Hurd for longer than
Linus has been working on Linux.

While Hurd will eventually have many more features than Linux, it is not
clear how much disk space or memory will be required to run it.  And for
most people, those extra features may or may not be useful.  Time will
tell.

As for the BSD 386, from what I can tell from other people's reports (I
have not tried running BSD 386 yet myself), Linux is slightly more
stable, but only slightly.  BSD 386 has the advantage that (except for
the 386/AT&T-free modules which were newly written), the majority of it
is vintage code, which should be pretty robust.  It's disadvantages are:
it's big; it doesn't have shared libraries; it wants to take over your
entire hard disk (Linux and DOS can co-exist on the same hard disk; BSD
can not); it doesn't have SCSI drivers (yet).  It's one big, big, big
advantage is: It has networking in the kernel already.  For people with
Ethernet cards, things like FTP at close to 100Kbytes/second and NFS are
very big draws.

I think Linux has a place, but I think the one thing it needs fast is
networking code in the kernel.  (That, and X11 :-) This features will
eventually come, but hopefully it will be sooner rather than later.  Is
anyone working on networking in the kernel right now?  I know there were
a few people interested in it, but I don't know if any of them are still
working on it.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Theodore Ts'o                           bloom-beacon!mit-athena!tytso
308 High St., Medford, MA 02155         tytso@athena.mit.edu
   Everybody's playing the game, but nobody's rules are the same!

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

From: johnsonm@stolaf.edu (Michael K. Johnson)
Subject: Custom setups: RFD
Reply-To: johnsonm@stolaf.edu (Michael K. Johnson)
Date: Sat, 11 Apr 1992 04:48:09 GMT

   May I suggest that instead of describing in long and careful detail how
   to fix the failed patch hunks in swap.c, you simply provide a new patch
   file which doesn't fail?  I suspect it would take up less room than your
   description, and would be simpler for most people to do.

I think that providing a description _is_ worthwhile, not because it
fixes this problem, but because it demonstrates the process of
patching, and especially the process of patching by hand, to people
who are not used to patching.  I know that the first time I ever
patched something, I was flying by night.  I was lucky enough to do
things right, but not everyone is.  So anyone who follows these
instructions can provide diffs, and those who want to understand
patching can follow the instructions to learn the process.

Note that the manual project influences my thinking this way :-)

   As to your point about a configuration process, I agree with you.  Linux

Ross Biro has made available a configuration system.  Unfortunately, I
have not had time to look at it, as all my hacking time (non-existent
these past two weeks :-( ) is being spent on scsi for the DTC.

   is rapidly approaching the point where it could really use a
   /usr/etc/config program ala BSD to build its Makefile.  Although I
   haven't had the time in a while to do any kernel hacking in a while
   (unfortunately, sigh....) I will note that the config program is freely
   available in /packages/bsd-sources/usr.sbin/config on ftp.uu.net.
   Perhaps someone would be willing to take a whack at adapting it for
   Linux?  If not, when I manage to find some time I'll look into it.

                                                           - Ted

michaelkjohnson
johnsonm@stolaf.edu

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

From: alsaggaf@ERL.MIT.EDU (M. Saggaf)
Subject: How to FORMAT a floppy in Linux?
Date: Sat, 11 Apr 1992 06:01:11 GMT

This is just that. I'd like to know how to format a floppy under Linux.

-- M. Saggaf (alsaggaf@erl.mit.edu)


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

Crossposted-To: alt.os.linux
From: drew@romeo.cs.colorado.edu (Drew Eckhardt)
Subject: Re: Custom setups: RFD
Date: Sat, 11 Apr 1992 08:02:47 GMT

In article <20053@castle.ed.ac.uk> eonu24@castle.ed.ac.uk (I Reid) writes:
>This article is posted as a "Request for Discussion" (RFD) although I
>realise at the outset that I may be alone in my viewpoint :-(. If I am
>then please feel free to send me a nice mailer telling me to shut up and
>stop wasting bandwidth. 
>
>The main bit
>------------
>
>Some facts:
>
>3. Different people want greatly differing things from Linux but above
>   all the consensus is that the kernel should be small and fast.
>
>
>So, putting these things together we come up against a problem....
>what should be "standard" in the Linux kernel and what should be
>optional. Take, for example, two different setups run on two different
>machines by two different people.
>

Everything should be standard, and on boot up should autodetect, and install
if the hardware needed to support it is there.  Yes, this is larger than 
a bare kernel, but one distribution will work for everybody until they
recompile or relink it with the options they want.


>2. A well documented configuration file to allow EASY changing of
>   setups and trouble free building of custom kernels. This should be
>   very wide ranging and should cover all possibilities.

Maybe a script file, like Larry Wall's Perl configuration script would 
be easier to use and more flexible, as it could configure Makefiles,
C source and header files transparantly to the end user.

>Some of this may be in 0.95c (haven't had a chance to look yet... I
>know the national keyboard selection is now done more sensibly) but I
>think anyone writing kernel level code should be aware that however
>wonderfull their code, there are those who need it and those who
>don't. Should needs change it should be easy to adjust things (by easy I
>mean a 1 (or so) line change in a master config file).
>
>Iain

You might take a look at what I did with the configuration files in 
the SCSI driver package - they consolodate all of the configuration
information in one config file, with a CONFIG_DISTRIBUTION that turns
on everything, and defaults that work for most systems.  

>patches for and installing ps. This was written for 0.95a not 0.95c
>                                                        ^         ^
>                                                        |         |
>                                     Please note________|_________|
>
>(which I haven't had a chance to look at yet) so buyer beware.
>

Just get .95c+, as it has the PS and lp patches already applied,
and they work beautifully.

Note that to correctly compile ps.c, you should make sure that 
the files in /usr/include/linux match those in /usr/src/linux/include/linux, 
and you should remove the -I flag from the Makefile.




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

Crossposted-To: alt.os.linux
From: drew@romeo.cs.colorado.edu (Drew Eckhardt)
Subject: Re: Custom setups: RFD
Date: Sat, 11 Apr 1992 08:02:47 GMT

In article <20053@castle.ed.ac.uk> eonu24@castle.ed.ac.uk (I Reid) writes:
>This article is posted as a "Request for Discussion" (RFD) although I
>realise at the outset that I may be alone in my viewpoint :-(. If I am
>then please feel free to send me a nice mailer telling me to shut up and
>stop wasting bandwidth. 
>
>The main bit
>------------
>
>Some facts:
>
>3. Different people want greatly differing things from Linux but above
>   all the consensus is that the kernel should be small and fast.
>
>
>So, putting these things together we come up against a problem....
>what should be "standard" in the Linux kernel and what should be
>optional. Take, for example, two different setups run on two different
>machines by two different people.
>

Everything should be standard, and on boot up should autodetect, and install
if the hardware needed to support it is there.  Yes, this is larger than 
a bare kernel, but one distribution will work for everybody until they
recompile or relink it with the options they want.


>2. A well documented configuration file to allow EASY changing of
>   setups and trouble free building of custom kernels. This should be
>   very wide ranging and should cover all possibilities.

Maybe a script file, like Larry Wall's Perl configuration script would 
be easier to use and more flexible, as it could configure Makefiles,
C source and header files transparantly to the end user.

>Some of this may be in 0.95c (haven't had a chance to look yet... I
>know the national keyboard selection is now done more sensibly) but I
>think anyone writing kernel level code should be aware that however
>wonderfull their code, there are those who need it and those who
>don't. Should needs change it should be easy to adjust things (by easy I
>mean a 1 (or so) line change in a master config file).
>
>Iain

You might take a look at what I did with the configuration files in 
the SCSI driver package - they consolodate all of the configuration
information in one config file, with a CONFIG_DISTRIBUTION that turns
on everything, and defaults that work for most systems.  

>patches for and installing ps. This was written for 0.95a not 0.95c
>                                                        ^         ^
>                                                        |         |
>                                     Please note________|_________|
>
>(which I haven't had a chance to look at yet) so buyer beware.
>

Just get .95c+, as it has the PS and lp patches already applied,
and they work beautifully.

Note that to correctly compile ps.c, you should make sure that 
the files in /usr/include/linux match those in /usr/src/linux/include/linux, 
and you should remove the -I flag from the Makefile.




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

From: liljeber@kruuna.Helsinki.FI (Mika Pekka Liljeberg)
Crossposted-To: alt.os.linux
Subject: Re: Problems with serial port drivers??
Date: 11 Apr 92 10:40:27 GMT

In article <65178@apple.Apple.COM> erc@Apple.COM (Ed Carp) wrote:
> Has anyone seen any problems with the serial port drivers under
> linux?  I'm running 0.95a and am having a hard time making uucp fly
> at 9600 baud and above, either straight through or with a modem.
> This same machine and comm board runs XENIX HDB UUCP flawlessly,
> and there have not been any reported complaints about taylor-uucp
> dropping packets, etc.
> 
> This might not show up under light loads -- just under a heavy
> load, like uucp at 19200.

Yeah, I have experienced problems at high speeds, too. There is packet
loss when transferring files with kermit, and the modem has an irritating
habit of suddenly dropping off-line, if simultaneous heavy disk activity
occurs. The surest way to effect this is to compile something on another
console (thank God I don't need swap in order to use the compiler!).
I even have a 16550AN UART chip, and it doesn't help at all (does anyone
know, if the serial driver supports 16550 fifos?).

My guess is that something in the kernel disables interrupts for too
long, perhaps its the hard disk driver, perhaps the problem occurs when
forking a new process, I don't know. It's annoying all the same.

As an aside, I've been hearing that it isn't possible to use serial ports
using the same IRQ line simultaneously. Isn't it possible to poll all the
UARTS on the IRQ line in the interrupt handler? Ie. you'd need a slightly
smarter interrupt handler. One routine would handle com1 and com3 and
another one would handle com2 and com4. I've never written an actual serial
driver, so I'm not very sure about this, but I think it ought to be possible.

        Mika
--
Mika Liljeberg                  Email:  liljeber@kruuna.Helsinki.FI
Helsinki University                     Mika.Liljeberg@Helsinki.FI
Dept. of Computer Science

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

From: liljeber@kruuna.Helsinki.FI (Mika Pekka Liljeberg)
Crossposted-To: alt.os.linux
Subject: Re: Problems with serial port drivers??
Date: 11 Apr 92 10:40:27 GMT

In article <65178@apple.Apple.COM> erc@Apple.COM (Ed Carp) wrote:
> Has anyone seen any problems with the serial port drivers under
> linux?  I'm running 0.95a and am having a hard time making uucp fly
> at 9600 baud and above, either straight through or with a modem.
> This same machine and comm board runs XENIX HDB UUCP flawlessly,
> and there have not been any reported complaints about taylor-uucp
> dropping packets, etc.
> 
> This might not show up under light loads -- just under a heavy
> load, like uucp at 19200.

Yeah, I have experienced problems at high speeds, too. There is packet
loss when transferring files with kermit, and the modem has an irritating
habit of suddenly dropping off-line, if simultaneous heavy disk activity
occurs. The surest way to effect this is to compile something on another
console (thank God I don't need swap in order to use the compiler!).
I even have a 16550AN UART chip, and it doesn't help at all (does anyone
know, if the serial driver supports 16550 fifos?).

My guess is that something in the kernel disables interrupts for too
long, perhaps its the hard disk driver, perhaps the problem occurs when
forking a new process, I don't know. It's annoying all the same.

As an aside, I've been hearing that it isn't possible to use serial ports
using the same IRQ line simultaneously. Isn't it possible to poll all the
UARTS on the IRQ line in the interrupt handler? Ie. you'd need a slightly
smarter interrupt handler. One routine would handle com1 and com3 and
another one would handle com2 and com4. I've never written an actual serial
driver, so I'm not very sure about this, but I think it ought to be possible.

        Mika
--
Mika Liljeberg                  Email:  liljeber@kruuna.Helsinki.FI
Helsinki University                     Mika.Liljeberg@Helsinki.FI
Dept. of Computer Science

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

From: tkendel@ernohb.UUCP (T. Kendelbacher OT133)
Subject: What is LINUX?
Date: 11 Apr 92 09:53:41 GMT

Can anybody please tell me what LINUX is?
Thank you for mailing or posting a short answer.

Thomas Kendelbacher  |  eMail : tkendel@ernohb.uucp
Robbenplate 13       |  voice : +49 539 5492
D-2800 Bremen 66     |     or : +49 57 04 37
Germany

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

From: david@csource.oz.au (david nugent)
Subject: smail 3.1.25
Date: Sat, 11 Apr 92 17:12:28 +1000
Reply-To: david@csource.oz.au

Has anyone got a working smail 3.1.25 for Linux yet? I managed to
get one compiled with a new machine description file and editing
the EDITME file to suit, and it seems to work - mostly. It
consistently traps _after_ delivering mail to local mailboxes,
otherwise it seems quite function.

I haven't been able to track it down further yet due to gdb not
functioning with the new gcc 2.1 beta + kernel + a.out.h, but I
thought I'd post this just in case the problem is known and
someone's already been though this before. If not, then I'll wait
for an updated gdb.

Regards,

  david

..............................................................................
david nugent          Public Access Usenet        "Only Nixon can go to China"
david@csource.oz.au     +61-3-792-3507                - ancient Vulcan proverb
3:632/400@fidonet, 58:4100/1@intlnet, 199:4242/5@rainbownet, 33:300/6@admin
PO Box 260, Endeavour Hills, Victoria, Australia, 3802.

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

From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
Subject: Re: kernel building problems
Date: 11 Apr 92 09:57:24 GMT

In article <1992Apr10.162906.21379@ods.com> david@ods.com (David Engel) writes:
>
>Aside to Linus:  Would you mind describing how you have your system set
>up?  It might help aleviate problems like this if we knew which compiler
>and system libraries you are using.

I'm still using 2.0 (and an older version at that) as I've been too busy
to upgrade.  I doubt the HJ-patch is really needed - I read through it,
and I'd guess 0.95c+ should compile pretty cleanly without it.  Anybody
tried it? HJ's patch also assumes you have a 387, and you'll have to
edit the makefile if you don't. 

I'll have to upgrade my compiler (probably this weekend), and the next
real version should have no problems with 2.1.  I'm in fact still using
my original 1.40 for everything but the kernel - I've left the actual
beta-testing of the new compilers and libraries to everyone else, and
I'll step in now that they seem stable.  Lazyness or prudency, you
decide :)

                Linus

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

From: liljeber@kruuna.Helsinki.FI (Mika Pekka Liljeberg)
Subject: Re: kernel building problems
Date: 11 Apr 92 11:14:00 GMT

In article <1992Apr11.095724.8928@klaava.Helsinki.FI> torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds) wrote:
> In article <1992Apr10.162906.21379@ods.com> david@ods.com (David Engel) writes:
>>
>>Aside to Linus:  Would you mind describing how you have your system set
>>up?  It might help aleviate problems like this if we knew which compiler
>>and system libraries you are using.
> 
> I'm still using 2.0 (and an older version at that) as I've been too busy
> to upgrade.  I doubt the HJ-patch is really needed - I read through it,
> and I'd guess 0.95c+ should compile pretty cleanly without it.  Anybody
> tried it? HJ's patch also assumes you have a 387, and you'll have to
> edit the makefile if you don't. 

I compiled .95c first without and the with the HJ patch. There were no
problems either way. Then I moved the kernel includes under /usr/include/linux
with HJ's conv script. I hope this will become "official" practise, since
it makes everything ever so much simpler. How about it, Linus? :)

> I'll have to upgrade my compiler (probably this weekend), and the next
> real version should have no problems with 2.1.  I'm in fact still using
> my original 1.40 for everything but the kernel - I've left the actual
> beta-testing of the new compilers and libraries to everyone else, and
> I'll step in now that they seem stable.  Lazyness or prudency, you
> decide :)

In my case a bit of both. ;)

        Mika
--
Mika Liljeberg                  Email:  liljeber@kruuna.Helsinki.FI
Helsinki University                     Mika.Liljeberg@Helsinki.FI
Dept. of Computer Science

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


** 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-Activists-Request@NEWS-DIGESTS.MIT.EDU

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

    Internet: Linux-Activists@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
    tupac-amaru.informatik.rwth-aachen.de	pub/msdos/replace

The current version of Linux is 0.95a released on March 17, 1992

End of Linux-Activists Digest
******************************
