Subject: Linux-Activists Digest #61
From: Digestifier <[email-masked]>
To: [email-masked]
Date: Mon, 13 Apr 92 23:45:10 EDT

Linux-Activists Digest #61, Volume #2            Mon, 13 Apr 92 23:45:10 EDT

Contents:
  Re: New project:  S3 Acc. video support for Linux. (Kevin Cummings)
  Re: New project:  S3 Acc. video support for Linux. (Kevin Cummings)
  Re: Problems with serial port drivers?? (Drew Eckhardt)
  all kinds of questions (Greenup)
  all kinds of questions (Greenup)
  Re: Needed: a guide to setting up swap space. (Kevin Cummings)
  .95c+ and GCC2.1 kernel compiles, MAN? (Bowen Goletz)
  Arrow keys and emacs (Demian A. Johnston)
  Arrow keys and emacs (Demian A. Johnston)
  Re: all kinds of questions (Bowen Goletz)
  Re: all kinds of questions (Bowen Goletz)
  Re: Questions from a beginner... (Kevin Cummings)
  Re: all kinds of questions (David Engel)
  System Architecture (Philippe Backouche)
  Patching Bootimage disks (Rainer Kirsch)
  When will "Linux 1.0" come to the world ? (mr79)

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

From: [email-masked] (Kevin Cummings)
Crossposted-To: alt.os.linux
Subject: Re: New project:  S3 Acc. video support for Linux.
Date: 13 Apr 92 18:11:02 GMT

In article <[email-masked]>, [email-masked] (Steven Kraft) writes:
> To all who are interested in (or curious about) direct (local) bus video and S3  
> accelerated video cards being used with Linux:  
> 
>       I have to decided to start discussion and development of S3 accelerated  
> video support in Linux.  

Being the owner of a brand spanking new Diamond Stealth VRAM S3 based video
card with 1MB of memory and the Hi-Color DAC, I share your interest in the S3
based video support category.

>       This morning I received S3 Incorporated's manual on the "86C911 GUI  
> Accelerator."  I ordered it from Orchid Technology for $25.  If you want one  
> for yourself, just call Orchid's Tech Support and they will sell it to you.   
> (Numbers are below.)  The manual looks good, but I have only had a few minutes  
> to glance through it.  It states that:  "the S3 86C911 is a high-performance  
> GUI accelerator specifically designed to accelerate applications running under  
> Windows, Presentation Manager, and X."  I will try to contact S3 Inc. to see  
> what they might have already on the X driver.

Great news!  Maybe I should order up a copy, since Diamond doesn't provide
access to ALL the S3 supported modes in it's video BIOS.  On the other hand,
Diamond does provide a VESA BIOS, but it doesn't support all the S3 modes either.

>       Now some info on the Fahrenheit 1280's modes.  The 1280 * [960|1024]  
> modes are interlaced.  The refresh rate can be set to 43 or 48 Hz.  The 640 *  
> 480 and 800 * 600 modes can be set to 60 or 72 Hz, and 1024 * 768 can be set to  
> 60 or 70 Hz.

So far, all this is pretty S3 standard, the Diamond supports these refresh rates
as well.

>               The primary way of setting refresh rates is through switches which  
> are easily accessible through a slot in the card's back panel.  A small  
> screwdriver is all it takes, no need to open the computer.

The Stealth only has 4 swithches on the back of its card.  Two of them help
select refresh rates.  I guess I'm lucky.  Two of these four states support the
NEC 3 and NEC 4/5 series monitors (I have a NEC 3D).

>                                                             The other way is a  
> resident driver for DOS (size of about 4k in memory I think) called FSCAN.  It  
> prompts you through setting the horizontal and vertical position adjustments  
> (to center the image at each resolution) and the refresh rates.

Diamond supplies an SMODE program to fine tune your video configuration, and select
other monitors or special frequencies/syncs/etc.

> Since the DOS utilities won't work  
> in Linux, refresh rates will need to be set using the switches.  

Yes, agreed, however, if we can figure out what the BIOSes are doing when they set
modes, maybe we can duplicate some of that in protected mode code so we don't need
the BIOSes (they're hard to access once LINUX gets running!).

>       The various S3-based cards are basically the same except for setting  
> the modes or whatever.  (I could be wrong here.)  I think that they are very  
> much the same, and that if any changes are needed, #define's will do the trick.   
> I think that local bus video cards look just like a card on an ISA bus as far  
> as software drivers are concerned.  They have a memory address just like any  
> other video card.  The difference is that the data is sent to the card at 32  
> bits.  (Correct me if I am wrong.)

Uh, BIOS interfaces are probably card specific, though VESA support can help here.
As far as card interfaces, 8, 16, and 32 bits are all possible.  My card is a 16 bit
card with jumpers on board to restrict access to 8 bits if necessary (not recommended
in an AT+ class machine!).

>       Soon I will start a channel on the linux-activists list for this  
> discussion.  If you have anything to contribute, please do, either through  
> email to me, the soon-to-be-created list channel, or comp.os.linux.

Great!  Please include me in your discussions!

Use either E-Mail address below if you start up a mailing list.   Thanx!

=================================================================
Kevin J. Cummings                       Prime Computer Inc.
20 Briarwood Road                       500 Old Connecticut Path
Framingham, Mass.                       Framingham, Mass.

Work:  [email-masked]
Home:  [email-masked]

Std. Disclaimer: "Mr. McKittrick, after careful consideration,
                  I've come to the conclusion that your new
                  defense system SUCKS..."   --  War Games
=================================================================

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

From: [email-masked] (Kevin Cummings)
Crossposted-To: alt.os.linux
Subject: Re: New project:  S3 Acc. video support for Linux.
Date: 13 Apr 92 18:11:02 GMT

In article <[email-masked]>, [email-masked] (Steven Kraft) writes:
> To all who are interested in (or curious about) direct (local) bus video and S3  
> accelerated video cards being used with Linux:  
> 
>       I have to decided to start discussion and development of S3 accelerated  
> video support in Linux.  

Being the owner of a brand spanking new Diamond Stealth VRAM S3 based video
card with 1MB of memory and the Hi-Color DAC, I share your interest in the S3
based video support category.

>       This morning I received S3 Incorporated's manual on the "86C911 GUI  
> Accelerator."  I ordered it from Orchid Technology for $25.  If you want one  
> for yourself, just call Orchid's Tech Support and they will sell it to you.   
> (Numbers are below.)  The manual looks good, but I have only had a few minutes  
> to glance through it.  It states that:  "the S3 86C911 is a high-performance  
> GUI accelerator specifically designed to accelerate applications running under  
> Windows, Presentation Manager, and X."  I will try to contact S3 Inc. to see  
> what they might have already on the X driver.

Great news!  Maybe I should order up a copy, since Diamond doesn't provide
access to ALL the S3 supported modes in it's video BIOS.  On the other hand,
Diamond does provide a VESA BIOS, but it doesn't support all the S3 modes either.

>       Now some info on the Fahrenheit 1280's modes.  The 1280 * [960|1024]  
> modes are interlaced.  The refresh rate can be set to 43 or 48 Hz.  The 640 *  
> 480 and 800 * 600 modes can be set to 60 or 72 Hz, and 1024 * 768 can be set to  
> 60 or 70 Hz.

So far, all this is pretty S3 standard, the Diamond supports these refresh rates
as well.

>               The primary way of setting refresh rates is through switches which  
> are easily accessible through a slot in the card's back panel.  A small  
> screwdriver is all it takes, no need to open the computer.

The Stealth only has 4 swithches on the back of its card.  Two of them help
select refresh rates.  I guess I'm lucky.  Two of these four states support the
NEC 3 and NEC 4/5 series monitors (I have a NEC 3D).

>                                                             The other way is a  
> resident driver for DOS (size of about 4k in memory I think) called FSCAN.  It  
> prompts you through setting the horizontal and vertical position adjustments  
> (to center the image at each resolution) and the refresh rates.

Diamond supplies an SMODE program to fine tune your video configuration, and select
other monitors or special frequencies/syncs/etc.

> Since the DOS utilities won't work  
> in Linux, refresh rates will need to be set using the switches.  

Yes, agreed, however, if we can figure out what the BIOSes are doing when they set
modes, maybe we can duplicate some of that in protected mode code so we don't need
the BIOSes (they're hard to access once LINUX gets running!).

>       The various S3-based cards are basically the same except for setting  
> the modes or whatever.  (I could be wrong here.)  I think that they are very  
> much the same, and that if any changes are needed, #define's will do the trick.   
> I think that local bus video cards look just like a card on an ISA bus as far  
> as software drivers are concerned.  They have a memory address just like any  
> other video card.  The difference is that the data is sent to the card at 32  
> bits.  (Correct me if I am wrong.)

Uh, BIOS interfaces are probably card specific, though VESA support can help here.
As far as card interfaces, 8, 16, and 32 bits are all possible.  My card is a 16 bit
card with jumpers on board to restrict access to 8 bits if necessary (not recommended
in an AT+ class machine!).

>       Soon I will start a channel on the linux-activists list for this  
> discussion.  If you have anything to contribute, please do, either through  
> email to me, the soon-to-be-created list channel, or comp.os.linux.

Great!  Please include me in your discussions!

Use either E-Mail address below if you start up a mailing list.   Thanx!

=================================================================
Kevin J. Cummings                       Prime Computer Inc.
20 Briarwood Road                       500 Old Connecticut Path
Framingham, Mass.                       Framingham, Mass.

Work:  [email-masked]
Home:  [email-masked]

Std. Disclaimer: "Mr. McKittrick, after careful consideration,
                  I've come to the conclusion that your new
                  defense system SUCKS..."   --  War Games
=================================================================

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

From: [email-masked] (Drew Eckhardt)
Subject: Re: Problems with serial port drivers??
Date: 13 Apr 92 18:46:43 GMT

In article <[email-masked]> [email-masked] (Jim Nelson) writes:
>In article <[email-masked]> [email-masked] (Jim Burns) writes:
>>in article <[email-masked]>, [email-masked] (Mika Pekka Liljeberg) says:
>>> 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
>>
>>You're not *supposed* to be able to do this. The ISA interrupts are level
>>triggered, which I believe means that after the ICU latches the first
>>interrupt, a 2nd one won't still be active after the first one is serviced.
>>You might try polling all devices on any interrupt, not just poll for the
>>*first* device that needs service. Don't know how successful that would be.
>>The MCA interrupts are level triggered, so this is not supposed to be a
>>problem there.
>

100% false with ISA.  ISA interrupts are edge triggered.  It has nothing
to do with the ICU not letting you have multiple interrupts.  The ISA 
IRQ lines are tristated, and if more than one is enabled at a time,
they short each other out.  Not as bad as it sounds, but it doesn't 
work.  

You are correct about MCA though - it uses level active IRQ lines,
and they are open collector. 

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

From: [email-masked] (Greenup)
Crossposted-To: alt.os.linux
Subject: all kinds of questions
Date: 13 Apr 92 19:15:37 GMT

Hello netters!
   I just booted up for the first time two days ago, and now I'm a happy
Linux user.  Well, almost.  I do have a few questions...

1. is "agetty" different than "getty", if so,
      where do I find it, 
      what's the difference?
2. why doesn't "tar +help | more" work?
3. does "sync" do a diskpark, or do I have to round up a routine for that?
4. I've heard that there's some binary incompatibility coming up.
      does the new work with the old or does the old work with the new,
      when (+/- a week) is this expected to take effect?
      is this tied in with the new compiler, or a new kernal goodie?
5. has anyone done any work on something similar to messydos's "snipper"
      (a cut & paste print screen) or "buffit" (a scrollback buffer)
6. will the ABC release make it out before I leave school for the year?
      (twice, one extra to make sure it doesn't have big bugs :-) )
      (leave school ~= May 14)

MANY THANKS--
john Greenup
[email-masked]

-- 
          john Greenup                       | snail mail: 
Internet: [email-masked]            |   414 Langford Hall  
Bitnet  : not yet                            |   Bozeman, MT 59771 

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

From: [email-masked] (Greenup)
Crossposted-To: alt.os.linux
Subject: all kinds of questions
Date: 13 Apr 92 19:15:37 GMT

Hello netters!
   I just booted up for the first time two days ago, and now I'm a happy
Linux user.  Well, almost.  I do have a few questions...

1. is "agetty" different than "getty", if so,
      where do I find it, 
      what's the difference?
2. why doesn't "tar +help | more" work?
3. does "sync" do a diskpark, or do I have to round up a routine for that?
4. I've heard that there's some binary incompatibility coming up.
      does the new work with the old or does the old work with the new,
      when (+/- a week) is this expected to take effect?
      is this tied in with the new compiler, or a new kernal goodie?
5. has anyone done any work on something similar to messydos's "snipper"
      (a cut & paste print screen) or "buffit" (a scrollback buffer)
6. will the ABC release make it out before I leave school for the year?
      (twice, one extra to make sure it doesn't have big bugs :-) )
      (leave school ~= May 14)

MANY THANKS--
john Greenup
[email-masked]

-- 
          john Greenup                       | snail mail: 
Internet: [email-masked]            |   414 Langford Hall  
Bitnet  : not yet                            |   Bozeman, MT 59771 

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

From: [email-masked] (Kevin Cummings)
Subject: Re: Needed: a guide to setting up swap space.
Date: Mon, 13 Apr 1992 18:52:15 GMT

In article <[email-masked]>, [email-masked] (Clifford A Adams) writes:
>       I recently installed Linux on my HD (/dev/hda1 mostly
> following I Reid's instructions), and things seem to be running OK.  I
> have 4 meg of ram (2.7meg reported free after buffers, etc), which is
> enough for most activities.  However, I'd like to add a few meg of
> swap space (especially since I like to use the full GNU Emacs while
> simultaneously compiling with GCC. :-)  I have about 200k of various
> FAQs and guides, but none of them explicitly say much about how to set
> up swap space.  I don't think I've been successful so far in figuring
> it out...

It was pretty easy for me.  First off there are two ways to set up
swap space.  You can create a swap file in your file system and page to it, or
you can set aside a disk partition, and page to that.  I choose the latter.

Step 1) Using pfdisk, I made the disk partition.  It was a little difficult
        finding the right fdisk to figure out the exact device name to use,
        but a little common sense came through in the end.  For me /dev/hda1
        is my primary DOS partition, and /dev/hda2 is my extended DOS partition.
        Using pfdisk, I set up partitions 3 and 4 and labeled them as
        type Linux/Minix file-system, and Linux-swap partitions.  The latter
        wasn't really necessary, I could have labeled it as anything.
        So, I have LINUX root on /dev/hda3, and LINUX swap on /dev/hda4.
        (If you already have LINUX on your hard drive, you only have to setup
        your swap partition.  I just happened to do both at the same time.)

Step 2) I ran "mkswap -c /dev/hda4 xxxx" where xxxx is the amount of space
        reported by fdisk as being available on the device.  The -c
        tells mkswap to check the media for bad spots (unrecoverable errors).
        You don't want to page onto one of those!

Step 3) After the partition is ready for swapping, I turned it on via
        "swapon /dev/hda4" to see if there would be any problems and ran that
        way for a while.

Step 4) To make the swap area appear permanently in my system, I modifed /etc/rc
        to do the swapon for me during system boot.

The prcedure for a file system swap file is similar to the above, except that the
swap device being used by the mkswap and swapon commands is a file instead of
a device.  Create a file big enough to hold the amount of swap space you want,
and use that pathname in place of /dev/hdax in the above sequence.

>       Here are my problems (using 0.95c+ boot floppy and a mostly
> 0.95a root on /dev/hda1):
> 
>       * "mkswap" was on my 0.95a rootdisk.  There seems to be a
> newer version (later file date) at tsx-11 under the binaries tree
> (the later one is bigger).  What are the differences, and which should
> I use?  For the rest of my experiments 

I don't know, I used the one on my root disk without problems.

>       * Looking at "mkswap" I noticed a "-c" option--what does it
> do?  Early on I thought that "-c" meant "create", and that otherwise
> mkswap would set up and use the swapfile.  At the moment it seems like
> you use swapon to set up a swap file--at the first reading it seemed
> like swapon was only for swap partitions...

Like I said above, the -c causes a media check for bad spots.

mkswap configures the disk for swapping.  (Like mkfs configures a disk
to be used as a file system.)  swappon is the command which actually
tells the OS to use the new swap space.

>       * I made a file "/dev/swapfile" using emacs to create a file
> of 1K spaces, then using cat to make 4K/16K/64K/256K/1meg files, and finally
> the 6 meg /dev/swapfile.  I didn't know if it would need a little more
> space for tables or whatever so I added another 256K as extra.
>               * Is there a better way to create the swapfile?

Under SUNOS, they have a mkfile command.  I haven't seen one for LINUX yet.

>               * Do I need to have more space than the #blocks I tell mkswap?

Nope, but if you have more space than you've configured with mkswap, it'll never
get used.

>       * I noticed that the mkswap blocks are 1K--this should
> probably be noted since its different than the filesystem blocks...

So swapping swaps 1K bytes at a time.  That is a memory page size.

>       * Is there any way to tell how much swap space you are using or
> have left?

Under SUNOS I do a "pstst -T".  I haven't seen a LINUX command yet to tell me
how much is actually in use.  And seeing as gcc-1.4 didn't know when my disk
was full (other that getting unexpected EOF error messages during compiliation),
I wouldn't be surprised if LINUX doesn't detect "out of swap space" cleanly either.
For now, I hope that 4MB of memory and 9MB of swap space is enough to not run out of
until we get something that tells us swap usage.

> ...What I'd really like to see is a guide something like Reid's guide
> to installation for setting up swap space--one that would cover both
> swapfiles and swap partitions.  (Perhaps it could be added as an
> appendix to the guide?).  Just a list of the commands and what they do
> would be nice however...
> 
>       Finally, my first impression of Linux is: "zippy".  Its been a
> long time since I've had the kind of quick response Linux gives, even
> when I worked on "unloaded" machines (where I'm the only user, the load
> avg is 0.00, etc...).  Even when running GNU emacs the response is
> excellent (on my 40mhz 386 w/64K cache).  It may seem like a
> small difference between the seeming immediate Linux response and the
> more typical 2/3-1 second reaction time, but it feels nice...  (Its also
> nice not to wait for overloaded NFS fileservers, and being able to
> mess with the kernal is a plus. :-)

Yeah, ain't it great?

=================================================================
Kevin J. Cummings                       Prime Computer Inc.
20 Briarwood Road                       500 Old Connecticut Path
Framingham, Mass.                       Framingham, Mass.

Work:  [email-masked]
Home:  [email-masked]

Std. Disclaimer: "Mr. McKittrick, after careful consideration,
                  I've come to the conclusion that your new
                  defense system SUCKS..."   --  War Games
=================================================================

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

From: [email-masked] (Bowen Goletz)
Subject: .95c+ and GCC2.1 kernel compiles, MAN?
Date: 13 Apr 92 19:31:41 GMT

I don't seem to be able to compile the .95c+ kernel using GCC 2.1.  Make
complained about not finding gpp, so I read through the GCC docs and
set up various links to appease make.  However, after a slew of errors,
I am still not able to compile.  Is anyone working on a current "how
to" with the new releases?  Are there problems that .95c+ and the
kernel patch available with GCC don't address?  Also  -- is the manual
binary available anywhere?  I have the manual tree and most of the
documentation in the right place, but nothing to make it go.

        -bg
mak

-- 
________________________________________________________________________________
Bowen Goletz
Purdue University                  Midi 'n Music
[email-masked]         [email-masked]

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

From: [email-masked] (Demian A. Johnston)
Crossposted-To: alt.os.linux
Subject: Arrow keys and emacs
Date: 13 Apr 92 19:00:10 GMT

I saw it posted here not too long ago a few lines to add to one's .emacs
file to let you use the arrow keys with emacs ???  Could someone repost
that?

                                                  Demian 
                                              --->  [email-masked]
                                              --->  [email-masked]
                                              --->  [email-masked]

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

From: [email-masked] (Demian A. Johnston)
Crossposted-To: alt.os.linux
Subject: Arrow keys and emacs
Date: 13 Apr 92 19:00:10 GMT

I saw it posted here not too long ago a few lines to add to one's .emacs
file to let you use the arrow keys with emacs ???  Could someone repost
that?

                                                  Demian 
                                              --->  [email-masked]
                                              --->  [email-masked]
                                              --->  [email-masked]

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

From: [email-masked] (Bowen Goletz)
Crossposted-To: alt.os.linux
Subject: Re: all kinds of questions
Date: 13 Apr 92 19:44:02 GMT

In article <[email-masked]> [email-masked] (Greenup) writes:
>
>Hello netters!
>   I just booted up for the first time two days ago, and now I'm a happy
>Linux user.  Well, almost.  I do have a few questions...
>
>1. is "agetty" different than "getty", if so,

        No significant difference, if any, just renamed.  getty is the 
more recent of the two.

>2. why doesn't "tar +help | more" work?

        The help output is through stderr insted of stdio (why?)  If you
want to pipe stderr, use the amperstand (&).  For example: tar &> tar.help.
Then more the tar.help file.  For some reason, stderr pipes aren't supported
with bash.  You should be able to do a &| to pipe the output directly to
more in the first place.

>3. does "sync" do a diskpark, or do I have to round up a routine for that?

        Sync flushes the disk cache.  Very important!  Most modern drives
auto-park on powerdown.  

        [abc release and binary incompatibility deleted]

        -bg

-- 
________________________________________________________________________________
Bowen Goletz
Purdue University                  Midi 'n Music
[email-masked]         [email-masked]

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

From: [email-masked] (Bowen Goletz)
Crossposted-To: alt.os.linux
Subject: Re: all kinds of questions
Date: 13 Apr 92 19:44:02 GMT

In article <[email-masked]> [email-masked] (Greenup) writes:
>
>Hello netters!
>   I just booted up for the first time two days ago, and now I'm a happy
>Linux user.  Well, almost.  I do have a few questions...
>
>1. is "agetty" different than "getty", if so,

        No significant difference, if any, just renamed.  getty is the 
more recent of the two.

>2. why doesn't "tar +help | more" work?

        The help output is through stderr insted of stdio (why?)  If you
want to pipe stderr, use the amperstand (&).  For example: tar &> tar.help.
Then more the tar.help file.  For some reason, stderr pipes aren't supported
with bash.  You should be able to do a &| to pipe the output directly to
more in the first place.

>3. does "sync" do a diskpark, or do I have to round up a routine for that?

        Sync flushes the disk cache.  Very important!  Most modern drives
auto-park on powerdown.  

        [abc release and binary incompatibility deleted]

        -bg

-- 
________________________________________________________________________________
Bowen Goletz
Purdue University                  Midi 'n Music
[email-masked]         [email-masked]

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

From: [email-masked] (Kevin Cummings)
Subject: Re: Questions from a beginner...
Date: 13 Apr 92 19:34:51 GMT

In article <[email-masked]>, [email-masked] (Bowen Goletz) writes:
> In article <[email-masked]> [email-masked] (Chris P. Sullivan) writes:
> >RESET-FLOPPY CALLED errors.  HOW WOULD WE MAKE LINUX UNDERSTAND THAT WE HAVE
> >AND A: DRIVE THAT IS 1.44MB?
> 
> Re-run the mkdev script as described above.  PS0 is the desired device name
> for a 1.44MB floppy (unit 0).

Better yet, go find 0.95c or 0.95c+.  This was supposed to fixed
the uncommon reset floppy problem that only a few people had.

=================================================================
Kevin J. Cummings                       Prime Computer Inc.
20 Briarwood Road                       500 Old Connecticut Path
Framingham, Mass.                       Framingham, Mass.

Work:  [email-masked]
Home:  [email-masked]

Std. Disclaimer: "Mr. McKittrick, after careful consideration,
                  I've come to the conclusion that your new
                  defense system SUCKS..."   --  War Games
=================================================================

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

From: [email-masked] (David Engel)
Subject: Re: all kinds of questions
Date: 13 Apr 92 20:51:38 GMT

[email-masked] (Bowen Goletz) writes:
: Then more the tar.help file.  For some reason, stderr pipes aren't supported
: with bash.  You should be able to do a &| to pipe the output directly to
: more in the first place.

Actually, standard error pipes are supported by bash.  You just have to use
the traditional /bin/sh syntax like this:

        command1 2>&1 | command2

David
-- 
David Engel                        Optical Data Systems, Inc.
[email-masked]                      1101 E. Arapaho Road
(214) 234-6400                     Richardson, TX  75081

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

From: [email-masked] (Philippe Backouche)
Subject: System Architecture
Date: 13 Apr 92 20:13:46 GMT
Reply-To: [email-masked] (Philippe Backouche)

   Could anyone explain me the difference of architecture between Linux, Mach and
   Minix ? What makes Linux be so fast ? 

   Thanks for your answers....
                     
                               Philippe.

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

From: [email-masked] (Rainer Kirsch)
Subject: Patching Bootimage disks
Date: Mon, 13 Apr 1992 21:06:43 GMT

I got pmk32.zip from wuarchive.wustl.edu in order to patch my boot-disk to 
tell about an alternative root device. (Wanting to change bytes no. 508 and 
509).
But: It did not work. I checked the behaviour of pmk with the new formatted 
disk - all ok. It seems, that the data of the boot information is too 
different from that of an ordinary MS/DOS disk. So a "General disk error" is 
reported.
Can anyone tell me an alternative mechanism for patching boot-disks?

Many thanks in advance!
Rainer Kirsch
Technical University of Vienna - Austria - Europe
[email-masked]

          +----------------------------+
          |      iaee_cad/kirsch       |
          | [email-masked] |
+----------------------------+---------------------+
| fax:   int +(043 1) nat +(0222) 505 26 66        |
| phone: int +(043 1) nat +(0222) 588 01 / 3848    |
+--------------------------------------------------+
| postal:                                          |
| TU-Vienna                                        |
| Inst. E359 / CAD                                 |
| Gusshaustr. 25-29                                |
| A-1040 Vienna                                    |
| Austria / Europe                                 |
+--------------------------------------------------+

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

From: [email-masked] (mr79)
Subject: When will "Linux 1.0" come to the world ?
Date: 13 Apr 92 21:56:10 GMT

Linux 0.95c is still in the period of development.
Everything is rather unstable.
when will Linux 1.0 come to the PC 386/486 world ?

                        J.H.Lin

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

** 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: [email-masked]

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

    Internet: [email-masked]

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
******************************