Re: Elks Distribution

Javier Sedano
2002-05-28T15:35:37Z

Neil Holmes wrote:
>
> 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.
>

We are very gratefull to you for what you are doing. That's the way the
free software works.

>
> 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 don't think it to be a must currently.

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

As many Linux distribution currently do, provide the most possible
generic kernel, and instructions to replace with an optimized one.

> - How do I control partitioning during install ?
> - Again your suggestions are likely to help here.

I'd do in the same way Minix does. Just spawn fdisk, and when it ends
ask: "what is the partition you have just created". In this step, I
wouldn't worry about the possibility to split the installation in more
than one partition, since the whole ELKS can be installed in 31MB (and
much less).

> - How do I deal with different types of install images ?
> - Your suggestions, again, will be key.

I don't know what it means... different kernel images?

> - How do I Resolve the multi-booting issue ?
> - This may be a lilo answer ? Not really thought about it yet.
>

Pascal says his utility can do it.

>
> 3. Package Installation
> - Look to install package sets as part of the installation process

It has been in my todo.gz for many month, but I can not find the time
to do it. I think that, for the moment, a simple packaging system,
without dependencies, is enough. I was wondering to do it using just
"tar" to package a CONTENTS directory, with the files to install, and a
INFO directory with pre-install, post-install, pre-remove, post-remove
scripts. A bit (well... a lot) of shell scripting can be used to do all
the actual work, keeping track of the files installed under
/var/epkg/state (for example) to be able to remove them when "epkg -r
<package>" is used.

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

If the packaging scheme is provided and it is simple, I think it would
be very easy to provide each program as a different package.

--
Has tenido suerte!! Te acaba de salir un tagline que no es penoso!!!
--------
Javier Sedano Jarillo http://www.it.uc3m.es/~jsedano
jsedano@dit.upm.es (*)
jsedano@ieee.org