lkml.org 
[lkml]   [1999]   [Aug]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Kernels > 1M
Date
[ Cc:s trimmed ]

Dr. Michael Weller wrote:
> But making a lilo based boot disk is a bit of hassle

Agreed.

> It would be good if there were something like:
>
> mklilobootdisk <floppy device> <bootimage>.

The main issue here is probably where you draw the line between
full functionality and ease of use. Writing the script should be
trivial nowadays (size-detecting mkfs and such really help).

> I think it would be simple to write as a script based on the current lilo.
> If lilo would be extended to accept explicit record numbers of
> the images in its config file,

LILO has this: image = /dev/foo range = 1-200

But I'm phasing it out, because it's not nearly as useful as one may
think. (See also lilo/INCOMPAT, search for "range").

> one could even make this work w/o a filesystem on the disk.

No, LILO still needs to write its map file.

> And you'd need something like rdev. [ etc. ]

See, you really want a file system ;-)

> Its up to you if you want to leave this poor guy stand
> in the rain then or continue to support this old feature.

I don't have a problem with bootsect.S. It has its limitations, which
will eventually force it into obsoleteness, but until then, I don't
see why it should be removed.

- Werner

--
_________________________________________________________________________
/ Werner Almesberger, ICA, EPFL, CH werner.almesberger@ica.epfl.ch /
/_IN_R_131__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:53    [W:1.181 / U:0.076 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site