Re: Elks Distribution

Riley Williams
2002-05-28T06:27:23Z

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.