From: Javier Sedano <jsedano@dit.upm.es>
To: elks <linux-8086@vger.kernel.org>
Cc: Neil Holmes <neil.holmes@zoom.co.uk>
Subject: Re: [Fwd: Elks Distribution]
Date: Fri, 24 May 2002 18:49:50 +0200 [thread overview]
Message-ID: <3CEE6F2E.3D111F74@dit.upm.es> (raw)
In-Reply-To: 3CEE5392.751D7124@dit.upm.es
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
prev parent reply other threads:[~2002-05-24 16:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 14:52 [Fwd: Elks Distribution] Javier Sedano
2002-05-24 16:49 ` Javier Sedano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CEE6F2E.3D111F74@dit.upm.es \
--to=jsedano@dit.upm.es \
--cc=linux-8086@vger.kernel.org \
--cc=neil.holmes@zoom.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.