public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Javier Sedano <jsedano@dit.upm.es>
To: Linux 8086 <linux-8086@vger.kernel.org>
Subject: Re: Elks Distribution
Date: Wed, 29 May 2002 12:33:21 +0200	[thread overview]
Message-ID: <3CF4AE71.99E6FCB1@dit.upm.es> (raw)
In-Reply-To: 1022653610.3cf474aa11daf@webmail2.zoom.co.uk

neil.holmes@zoom.co.uk wrote:
> 
> 1. To have part of the install set be run on linux to allow
> production of the required kernel.
> 2. To issue a distribution set that caters for every single
> possible root location.
> 

        Another solution: give a disk image boot+root (or maybe 2, if
360k are
used) which boots, fdisks, mkfss and so on. In a different disk (because
I am pretty sure that it won't fit in 720k with all the other stuff),
provide 4 kernels, one for each of the 4 possible installation
(/dev/bda[1..4]). And somewhere in the installation process, copy the
correct kernel to the HD and use bootkit to select it.

        Anywau, you need to do something similar, right? I mean... the
kernel
in the boot floppy must have /dev/fd0 as root device, mustn't it?

> Neither of those are really in the spirit of the goal of the
> project so I have a brick wall looming...... Unless the kernel
> experts can help ?
> 

        That would be the perfect solution, but may be hard to code...




-- 
La indiferencia a las taglines es síntoma de crueldad mental
--------
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

  reply	other threads:[~2002-05-29 10:33 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-28  5:29 Elks Distribution Neil Holmes
2002-05-28  6:27 ` Riley Williams
2002-05-28  7:14   ` Neil Holmes
2002-05-28 11:12     ` Stefan de Konink
2002-05-28  9:53       ` Neil Holmes
2002-05-28 11:39     ` Alan Cox
2002-05-28 10:51       ` Neil Holmes
2002-05-28 12:01         ` Alan Cox
2002-05-28 11:03           ` Neil Holmes
2002-05-28 15:35     ` Javier Sedano
2002-05-29  8:57       ` Pascal Bellard
2002-05-29 10:17         ` Javier Sedano
2002-05-28 23:11     ` Riley Williams
2002-05-28 23:35       ` Dan Olson
2002-05-29  6:26         ` neil.holmes
2002-05-29 10:33           ` Javier Sedano [this message]
2002-05-29 18:31             ` Riley Williams
2002-05-29 23:44           ` Dan Olson
2002-05-30  7:51             ` Stefan de Konink
2002-05-30 13:01               ` Harry Kalogirou
2002-05-30  9:38             ` Javier Sedano
2002-05-29  6:31       ` neil.holmes
  -- strict thread matches above, loose matches on Subject: below --
2002-12-18 20:08 ELKS distribution Gábor Lénárt
     [not found] <Pine.LNX.4.33.0206100912170.8487-100000@zeus.edeclaracion.com>
2002-06-10 15:22 ` ELKS Distribution Daniele D'Elia
2002-06-10 15:35   ` Miguel Bolanos
2002-06-10 14:29 Daniele D'Elia
     [not found] <Pine.LNX.4.21.0205302112040.15697-100000@Consulate.UFP.CX>
2002-06-01  0:25 ` Elks Distribution Blaz Antonic
2002-05-31 16:13 Neil Holmes
2002-05-30 16:47 Neil Holmes
2002-05-30  7:40 neil.holmes
2002-05-28 21:01 Neil Holmes
2002-05-28 22:47 ` Stefan de Konink
2002-05-29  6:40   ` neil.holmes
2002-05-30 11:40     ` Stefan de Konink
2002-05-30 11:03       ` Riley Williams
2002-05-30 19:38         ` Stefan de Konink
2002-05-30 18:47           ` Riley Williams
2002-05-30 19:35             ` neil.holmes
2002-05-31  5:34           ` Neil Holmes
2002-05-30 18:19       ` Blaz Antonic
2002-05-30 11:57         ` Stefan de Konink
2002-05-30 19:18           ` Blaz Antonic
2002-05-28 17:44 Neil Holmes
     [not found] <Pine.LNX.4.21.0205280728170.15697-100000@Consulate.UFP.CX>
2002-05-28 15:13 ` Javier Sedano
2002-05-28  5:30 Neil Holmes
2002-05-28  5:30 Neil Holmes
2002-05-27 13:46 Neil Holmes
2002-05-27 20:34 ` Michael McConnell
2002-05-28  5:33   ` Neil Holmes
2002-05-28  6:46     ` Michael McConnell
2002-05-28  6:57       ` Neil Holmes
2002-05-28  6:59       ` Neil Holmes
2002-05-27 12:22 Re : " Javier Sedano
2002-05-27 18:52 ` Riley Williams
2002-05-27 20:23   ` Stefan de Konink
2002-05-28  6:11     ` Riley Williams
2002-05-25 21:48 Neil Holmes
2002-05-25 23:22 ` Stefan de Konink
2002-05-26 13:30   ` Nicholas Knight
2002-05-25 23:31 ` Stefan de Konink
2002-05-25 22:06   ` Neil Holmes
2002-05-25 23:41     ` Stefan de Konink
2002-05-25 22:15       ` Neil Holmes
2002-05-25 23:47         ` Stefan de Konink
2002-05-25 22:22           ` Neil Holmes
2002-05-25 23:51             ` Stefan de Konink
2002-05-27 16:59   ` Dan Olson
2002-05-26 14:37 ` Blaz Antonic
2002-05-26  6:45   ` Neil Holmes
2002-05-26 15:01     ` Blaz Antonic
2002-05-27 12:30 ` Javier Sedano
     [not found]   ` <3CF33E41.6ED906FB@ascend.com>
2002-05-28 15:46     ` Javier Sedano
2002-05-28 16:30       ` Pascal Bellard
     [not found] <200205242123.WAA08977@eddie.loc>
2002-05-25 20:52 ` Neil Holmes
2002-05-25 22:39   ` Stefan de Konink
2002-05-25 22:55   ` Riley Williams
2002-05-26  6:26     ` Neil Holmes
2002-05-26  8:00       ` Riley Williams
2002-05-26  8:07         ` Neil Holmes
2002-05-26  9:50           ` Riley Williams
2002-05-26 15:27           ` Riley Williams
2002-05-26 12:52   ` pauln
2002-05-24 13:17 Neil Holmes
2002-05-24 14:16 ` Javier Sedano

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=3CF4AE71.99E6FCB1@dit.upm.es \
    --to=jsedano@dit.upm.es \
    --cc=linux-8086@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox