RE: Elks Distribution

Neil Holmes
2002-05-28T07:14:21Z

Hi Riley,

I am very greatful to you for your support of what I am doing. Basic, though
it is at the moment, I do expect it to go much, much further.

The goal of the Distribution Edition is to create a version of ELKS that is
accessible to the less technically able of us out there. Simply stated - to
be able to boot from a floppy disk, follow a procedure, and finish up with
a PC that boots into ELKS at the end of that process. (From my web page)

I remember that, when I first started out with Elks, I had a lot of trouble
getting going from anything other than the disk images. I had an 80286 PC
that had been sat around gathering dust and I decided that it should be my
ELKS desktop PC.

Even then it took me a long time to get anywhere far with that. Although I
have an IT career, its not as a 'C' Programmer. And my low level knowledge
is sketchy to say the least. I find Tannebaum's tome very interesting but
hard going. I guess that sort of level is not my scene.

But what I do have is a gritty determination. And that is how I got going
with the 80286. I resolved that I would get it self booting and running
ELKS. I achieved that after a lot of experimentation and Newsgroup scouring.

As I said in my email last week. I then got to the point where I wanted to
try and put something back into the project of my own. But what could I do ?
I certainly don't have, and probably never will have, the low level skills
that you guys have. But what I did have was my own experience of getting
started with ELKS.

I realised that many others may be getting turned off to ELKS because they
don't possess the same kind of determination that I do. So that was when I
decided to pull together my experience into what, I hope, will become a
decent Distribution Edition for people like me.

So the roadmap that I have now goes something like this :-

1. Bootable Install Floppy
- Shell Scripting
- Maybe look at some of the mini "curses" code that is lying around to try
and make it
look prettier later
- I would appreciate some feedback on what I can do with the bcc version
of "curses".
I noticed it in the ELKSCMD source.

- I am thinking that for a Distribution I need to be able to, pretty well,
automate everything.
But, of course, with manual options for those who prefer that way. The
key installation issues
that I see my needing to consider are :-
- How do I resolve the kernel configuration for each platform/ disk layout
?
- May be Linux controlled as per your information.
- How do I control partitioning during install ?
- Again your suggestions are likely to help here.
- How do I deal with different types of install images ?
- Your suggestions, again, will be key.
- How do I Resolve the multi-booting issue ?
- This may be a lilo answer ? Not really thought about it yet.

2. SLIP Network Installation
- Automatic installation of a SLIP connection and test during install
- I have not really played with this yet though I do have Harry's notes in
my file.

3. Package Installation
- Look to install package sets as part of the installation process
- Here I will need suggestions and contributions. I can start work on this
now so, if anyone
has anything then please let me know. Please be sure that I am ok with
licensing before
submitting anything. Documentation would be very helpful too ! I will
try them out on my
desktop before I include them.
- SmallC I expect to be one
- Elvis perhaps

So there you have it. Thats what I am up to. The feedback that I get is
vital and I very greatful for all the encouragement that I have had thus
far.

Many Thanks

Neil

-----Original Message-----
From: linux-8086-owner@vger.kernel.org
[mailto:linux-8086-owner@vger.kernel.org]On Behalf Of Riley Williams
Sent: 28 May 2002 07:27
To: Neil Holmes
Cc: Linux 8086
Subject: Re: Elks Distribution

Hi Neil.

> Thanks Riley.
>
> I have a few things to do before I get to disk formats. Thank you for
> your, as ever, very useful information.

No problem. Here's how I would envision your install image working:

1. The user does the current `make comb` or `make full3` or `make
full5` to create the relevant bootable system image, which provides
an outline of the files that should be on the target system. If the
`make comb` route is taken, they also do `make net` to create one
with the SLIP networking tools on it.

2. The user then does a `make imstimg` that creates a second system
image, which produces a 720k image that can be written to either
a 720k floppy, a 1200k 5.25" floppy or a 1440k 3.5" floppy, and
which basically partitions and formats the hard drive, then mounts
the disk produced in step 1 and then copies each file on that to
the same relative location on the hard drive.

3. Also included on the `make instimg` disk and copied to the hard
drive is a script that can copy additional disks over to the hard
drive. This script would be used for the `make net` disk referred
to in (1) above.

How does that compare with your design?

Best wishes from Riley.

> -----Original Message-----
> From: linux-8086-owner@vger.kernel.org
> [mailto:linux-8086-owner@vger.kernel.org]On Behalf Of Riley Williams
> Sent: 27 May 2002 19:53
> To: Javier Sedano
> Cc: Linux 8086
> Subject: Re: Elks Distribution

> Hi Javier.

>>>> I will arrange somewhere to post my distributions for download.
>>>>
>>>> I'll post a message when I have this arranged.

>>> ftp.linux.org.uk will be happy to provide space

>> Wouldn't it be better to upload that files to the official ELKS home
>> page at sourceforge? Riley?

> Ideally, it would be an extension of the elkscmd package that was
> implemented as a `make instimg` command that created the disk images in
> a similar way to how the `make full3` creates a disk image of a 1.44M
> 3.5" ELKS boot floppy. If Neil wishes to do that, I have no problem with
> the idea, and my recommended route would be to create an elkscmd/hdinst
> directory in the existing tree and develop this in there, then go from
> that.
>
> Comments?
>
> Best wishes from Riley.

-
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html