[Fwd: Elks Distribution]

[Fwd: Elks Distribution]

[Javier Sedano]

[-- Attachment #1: Type: text/plain, Size: 177 bytes --]


-- 
Esta linea representa la importancia de una linea inútil.
--------
Javier Sedano Jarillo      http://www.it.uc3m.es/~jsedano
 jsedano@dit.upm.es (*)
 jsedano@ieee.org

[-- Attachment #2: Type: message/rfc822, Size: 5714 bytes --]

From: "Neil Holmes" <neil.holmes@zoom.co.uk>
To: <jsedano@dit.upm.es>
Subject: RE: Elks Distribution
Date: Fri, 24 May 2002 15:37:52 +0100
Message-ID: <DDENIOHFNLNMCGGDFDPCEEMFCDAA.neil.holmes@zoom.co.uk>

Thanks for your reply.

I guess I will hang around for a few days on the fdisk/mkfs/mount issue.
There are plenty of reasons that I should persist with 0.1.0 if I can get
over this bump.

Thanks for your encouragement on the distro I will carry on and am happy to
share my work if anyone is interested. I will aim to produce a disk image
file once I am over the 0.1.0 issue.

As far as the installation to partition issue is concerned - theres not
really a problem here while I am using fdisk in my script. At the moment I
would have to accept a data entry on exit from fdisk to manually state which
partition I am installing to. Eventually, I expect, I will need an interface
into fdisk or something completely new ?

Thanks for the advise on scripting. I can't see an immediate need for
changing this anyway. It would just be an extra challenge for me further
down the line. I'll keep it as it is just now.

Thanks also for the tip on stable and development versions. I guess I am
working towards what I would call my first stable version. That being a
basic hard drive bootable installation. I will also take an input for
partition to install to for now. That should solve your issue. Anything else
you can suggest for my first version would be appreciated but I think this
would be a start.

My working title for my project is now "The Elks Distributions Edition".
Happy for any other suggestions.

btw - How will I go about publishing a disk image (with scripting) on the
web page when I am ready ?

Any way. Once again - many thanks for your encouragement. I will keep with
it and keep the group posted.

Neil

-----Original Message-----
From: jsedano@dit.upm.es [mailto:jsedano@dit.upm.es]
Sent: 24 May 2002 15:16
To: Neil Holmes
Cc: Linux 8086
Subject: Re: Elks Distribution


Neil Holmes wrote:
>
> Are there any fixes around for this that I may be missing ?
>

	There has been a discussion about it in the last days, so I suppose
they are working on it.

>
> I have now moved onto looking for some sort of a challenge for myself that
I
> may be able to contribute to the project. My C skills are not to the
> standard of the majority of the contributors here. Hence I am not so
> comfortable at low levels. I noticed, though, in the documentation that
> Question 1.3 says "Are there any ready-to-run distributions of ELKS". The
> answer says no and goes on to invite interest to build something. Is this
> still the case ? Are there no distributions ?
>

	As far as I know, nobody is working on it, so your work will be
appreciated.

> During the course of my experimenting I have been playing with scripts
that
> install ELKS to the hard drive from a root and boot floppy. I guess this
is
> the start of a distribution ? My current script will only run, so far,
into
> /dev/bda1. It was devised as a way to save me some time really.
>

	On my side, it is a danger, since I have MSDOS-win30 in bda1 and Minix
in bda2, so I need to change to bda3

> I am currently trying to persuade my script to setup the hard drive to
boot.
> I did it manually so I expect I will soon have it working from my install
> routine too. In due course I may well re-write the script in, perhaps C ?

	I wouldn't do so. Scripts are slower, and sometimes larger, but much
easier to modify (just mount the floppy under UNIX/Linux and edit it). I
would advice scripts, if I were asked.

> I
> would also like to make the Install Floppy Disk be for a 0.1.0 system but
> the problems that I outlined at the head of this message prevent that just
> now.
>

	One hint: keep two distribution. A stable, with that you know that
(almost) works. And publish it in the web page. And keep working on
other, published here (and as alpha/beta in the web, if you want), until
it reaches stable state.

> Is what I have been up to of interest. Maybe good for less technical
people
> who want a first look at Elks ?
>

	I think so.

--
El trabajo en equipo es esencial, te permite echarle la culpa a otro.
--------
Javier Sedano Jarillo      http://www.it.uc3m.es/~jsedano
 jsedano@dit.upm.es (*)
 jsedano@ieee.org

Re: [Fwd: Elks Distribution]

[Javier Sedano]

Javier Sedano wrote:
> 
> As far as the installation to partition issue is concerned - theres not
> really a problem here while I am using fdisk in my script. At the moment I
> would have to accept a data entry on exit from fdisk to manually state which
> partition I am installing to. Eventually, I expect, I will need an interface
> into fdisk or something completely new ?
> 

	Have you installed Minix? It drives you to fdisk, and let you work
(with some advices). And then ends, and asks you: "what is the name of
the partition you have just created?", and continues. I think that's a
good idea for a while.

> 
> My working title for my project is now "The Elks Distributions Edition".
> Happy for any other suggestions.
> 

	As far as there are no other distribution in work, that's fine.

> btw - How will I go about publishing a disk image (with scripting) on the
> web page when I am ready ?
> 

	I am not a ELKS delevoper, just an user, but I suppose that, once it
works, some of the web maintainers can upload it to the main ELKS web
page. I suppose you shouldn't worry about that.


-- 
Nadie debería necesitar más de 640 Kbytes de RAM. (Bill Gates.
Presidente de Microsoft 1981)
--------
Javier Sedano Jarillo      http://www.it.uc3m.es/~jsedano
 jsedano@dit.upm.es (*)
 jsedano@ieee.org
-
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