Re: 8086/88 80286 ||| 80386 80486 Pentium ...

2000-02-28 Thread Bruce Irving

I have a 386 AND a 486 that I am unable to bring up on Linux because the
current version requires more than 8 MB ram.  The setup that I want requires
the greater security that Linux brings over bloat 95-2k.  Currently, I am
waiting with baited -- er, held -- breath for ELKS to have networking
capability.

Bruce

-Original Message-
From: Christoph Plattner [EMAIL PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Wednesday, February 23, 2000 4:01 PM
Subject: 8086/88 80286 ||| 80386 80486 Pentium ...


Hi all elks hackers.

I am one of you hackers, and I also develop on elks (look at
netboot in elks, etc)

But we should never forget the aim of elks !

I am really a linux fan and also hack on linux and so there is a
simple rule for me:

 All computers should run Linux, except for them, which
 are not able to ( 386).

 And when I cannot use Linux, then the next best:

 E L K S !

But I cannot imagine to use elks on a 386 or greater board.
On =386 boards I would collect tools for a mini Linux running on
4MB and so on, but in this case Linux not Elks.

Nethertheless, I like Elks, really. And I also will go on
elks hacking..

greetings
 Christoph P.




Re: Call for a README

2000-01-24 Thread Bruce Irving

Thanks for getting this started.  I've had images.zip for quite a while,
now, and didn't know what to do with the unzipped files.  It is also nice to
know that the Comb has nothing to do with my hair! :)

I knew just enough Linux (from my unsuccessful installs) that Phill's
version increased my knowledge.  And Matt had an excellent DOS instruction
set, too.

Bruce

-Original Message-
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Saturday, January 22, 2000 10:11 AM
Subject: RE: Call for a README


Here's a README  I've attached the text file too in case you mail program
mangles it.  What do you think?


(1) Introduction
(2) Trying out ELKS using the disk images
(3) Compiling your own kernel



(1) Introduction

Hello and welcome to the exciting world of Linux-8086, ELKS, or the
Embeddable Linux Kernel Subset!  This is a project which will eventually
produce a linux like OS for the 8086(186,286) as well as for the psion
series of processors.  But as you have this file you probably already know
that so let's get down to buisness.



(2) Trying out Elks using the images

So you want to give ELKS a try but you don't want all the fuss and bother
of
compiling the kernel and the tools yourself.  No problem.  All you need to
do is grab the images.zip file from the download section of
http://www.elks.ecs.soton.ac.uk/cgi-bin/ELKS and save it to its own
directory.  We'll assume ./ELKS/ is the directory.  Then do the following

  cd ./ELKS
  unzip images.zip
  ls

Now you should have three files boot, root, and comb.  The file called
"boot" contains the kernel and is used with "root", which contains the
actual applications, for systems with low capacity diskette drives.  The
file "comb" is a combination of the two disk images and can be used on
systems with diskette drives with a capacity of 720 kilobytes and higher.
We'll make all three just to show how it's done.  We'll assume that all
files are being written to "/dev/fd0" but you may have to figure out which
is the approproate drive on your system.   You should still be in the
./ELKS/ directory.  Put a diskette labeld boot in the drive and do the
following and remember all data on the diskettes will be lost.

  dd if=./boot of=/dev/fd0
   /* Change diskettes. Use one labled root*/
  dd if=./root of=/dev/fd0
   /* Change Diskettes. Use one labled comb */
  dd if=./comb of=/dev/fd0

That's it you should now have three diskettes that you can use to boot
your ELKS system.  If you using the boot and root disks you'll have to use
boot first and insert root when asked.  If you can use the comb disk then
you'll only have to use that disk.




(3) Compiling your own kernel

Compiling your own kernel is a bit more involved but we'll get through it.
First your going to need a few files from the download section of
http://www.elks.ecs.soton.ac.uk/cgi-bin/ELKS

  elks-x.x.xx.tar.gz
  images.zip
  elkscmd-.tar.gz
  Dev86bin-x.xx.x.tar.gz

Ok so you've got the files personnally I like to keep them in /ELKS/ so
that's what I'll assume your doing.  So cd to /ELKS and let's get started
The first thing we need to do is install the Developement tools.

  cp Dev86bin-x.x.xx.tar.gz /
  cd /
  tar xvzf Dev86bin-x.x.xx.tar.gz
  rm Dev86bin-x.x.xx.tar.gz

And you should have the 8086 developement tools installed.  Next we need to
cd back to /ELKS/ and untar the elks kernel sources. So
  cd /ELKS
  tar xvzf elks-x.x.xx.tar.gz
  cd ./elks

Now that we're in the source directory we can start setting up the kernel
the firt thing that needs to be done is

   make config

You'll be asked a few questions about how you want the kernel set up, for
now we'll accept the defaults and just keep hitting enter until we get
to the end then

  make

You'll see a lot of warnings go by for a few minutes, and then we'll assume
a perfect compile.  So we'll now have an diskette image file with our new
kernel on it.  We'll assume we built for the 8086.  The image is a little
buried so we'll have to dig into the source tree to find it

  cd /ELKS/elks/arch/i86/
  ls

If the compile was successful you'll have an "Image" file here and you'll
have to get it onto a diskette I'll assume "/dev/fd0"

  dd if=./Image of=/dev/fd0

This will be your boot disk,  but you'll need a root disk too so

  cd /ELKS/
  unzip images,zip
  dd if=./root of=/dev/fd0

After that you should be able to use the boot and root disks and watch ELKS
work its linux like magic on your machine.  Have fun!


Re: I want to unsubscribe

1999-11-27 Thread Bruce Irving





-Original Message-From: Noah Roberts 
(jik-) [EMAIL PROTECTED]To: Mailing 
List [EMAIL PROTECTED]Date: 
Friday, November 26, 1999 3:53 PMSubject: I want to 
unsubscribe
But I don't know how. Please let me know the 
procedure.
Welcome to the linux-8086 
mailing list!

Please save this message for future 
reference. Thank you.

If you ever want to remove yourself 
from this mailing list,you can send mail to [EMAIL PROTECTED] with 
the followingcommand in the body of your email message:

 unsubscribe 
linux-8086 your email 
address




Re: Questions

1999-11-25 Thread Bruce Irving


-Original Message-
From: Alistair Riddoch [EMAIL PROTECTED]
To: Giles Russell [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Tuesday, November 23, 1999 7:35 AM
Subject: Re: Questions


Giles Russell writes:

 Can someone please tell me what these mean for the help :)

 ROM_SETUP_CODE

Code segment location for the setup code when programmed into a ROM. This
is usually the base segment address of the ROM.

 ROM_KERNEL_CODE

Code segment location for the kernel code when programmed into a ROM. This
is usually the base segment address of the ROM + 0x60.

 ROM_SETUP_DATA

Segment location in RAM where the setup code keeps the values it is going
to pass to the kernel.

 ROM_KERNEL_IRQDATA

Segment location of an absolute area of RAM where the kernel stores certain
variables that it must be able to access when it does not know where its
data segment is.

 ROM_KERNEL_DATA

Segment location of the kernels data segment, used only when the kernel
image is in ROM.

 ROM_CHECKSUM_SIZE --  Is this size or an offset value 

Size of the ROM image to be prepared. This value is stored in the ROM
header, and the whole ROM must checksum to zero.

 ROM_USE_ORG_INTMASK

Force the irq system to read in the original interrupt mask before it
starts
sorting out interrupts. By default the kernel disables all interrupts. This
should only be used by kernel hackers.

 ROM_CONFIG_8253


Appears to be unused.

Al

IMHO, and if my rusty RAM serves, an 8253 was the normal serial chip on the
old CP/M and early DOS machines.

Bruce