From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: fdutils.
Date: 14 Nov 2001 17:15:07 -0800 [thread overview]
Message-ID: <9sv4ur$buj$1@cesium.transmeta.com> (raw)
In-Reply-To: <20011114123033.N991@zip.com.au> <Pine.LNX.4.21.0111150027200.3058-100000@Consulate.UFP.CX>
Followup to: <Pine.LNX.4.21.0111150027200.3058-100000@Consulate.UFP.CX>
By author: Riley Williams <rhw@MemAlpha.cx>
In newsgroup: linux.dev.kernel
>
> As I see it, there are the following options available:
>
> 1. Insist that those using the rescue CD have two CD drives.
>
> In my book, that's a non-starter, so 'nuff said).
>
> 2. Prohibit access to the CD drive for anything other than the
> rescue CD.
>
> 3. Copy the contents of the CD into a ramdisk, then run from
> the ramdisk.
>
> If the user has enough RAM, maybe, but if not...
>
> 4. Provide a "Virtual CD Drive" on single CD drive systems
> (similar to the way drive B: on MS-DOS 2.00 and later is a
> virtual floppy drive on single floppy systems).
>
> I'm not sure how this would work in practice, but it could
> be done, I'm sure.
>
All of this is why different rescue-CD distributions take different
approaches... as well as those that use other means such as floppy- or
network-booting.
One size doesn't necessarily fit all, and that's just fine.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2001-11-15 1:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 9:11 fdutils Rajiv Malik
2001-11-13 16:44 ` fdutils Keith Owens
2001-11-15 22:51 ` fdutils Kai Henningsen
2001-11-13 18:28 ` fdutils H. Peter Anvin
2001-11-13 19:42 ` fdutils Maciej W. Rozycki
2001-11-13 19:57 ` fdutils H. Peter Anvin
2001-11-13 20:12 ` fdutils Maciej W. Rozycki
2001-11-13 20:42 ` fdutils H. Peter Anvin
2001-11-13 20:52 ` fdutils Maciej W. Rozycki
2001-11-13 21:02 ` fdutils H. Peter Anvin
2001-11-13 21:45 ` fdutils Richard B. Johnson
2001-11-14 0:22 ` fdutils Pascal Schmidt
2001-11-14 0:23 ` fdutils H. Peter Anvin
2001-11-14 0:37 ` fdutils Pascal Schmidt
2001-11-14 0:50 ` fdutils Riley Williams
2001-11-14 1:30 ` fdutils CaT
2001-11-14 1:35 ` fdutils H. Peter Anvin
2001-11-15 0:40 ` fdutils Riley Williams
2001-11-15 0:51 ` fdutils CaT
2001-11-15 1:09 ` fdutils Riley Williams
2001-11-15 6:23 ` fdutils CaT
2001-11-15 1:15 ` H. Peter Anvin [this message]
2001-11-14 2:20 ` fdutils Mr. James W. Laferriere
2001-11-14 2:18 ` fdutils. (Was Re: [Q] pivot_root and initrd) Mr. James W. Laferriere
2001-11-14 12:18 ` fdutils Maciej W. Rozycki
2001-11-13 22:03 ` fdutils Gerhard Mack
2001-11-14 12:20 ` fdutils Maciej W. Rozycki
2001-11-14 15:25 ` fdutils Gerhard Mack
2001-11-14 13:08 ` fdutils Horst von Brand
2001-11-14 14:01 ` fdutils Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2001-11-16 10:26 fdutils Rajiv Malik
2001-11-13 7:35 fdutils Rajiv Malik
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='9sv4ur$buj$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@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