Bug 8889 - mkbootdisk should run OK without parameters
Summary: mkbootdisk should run OK without parameters
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: mkbootdisk
Version: 6.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Matt Wilson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-01-26 09:14 UTC by Johan Walles
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-01-26 09:14:39 UTC
Embargoed:


Attachments (Terms of Use)

Description Johan Walles 2000-01-26 09:14:39 UTC
Because I yesterday had to -- over the phone -- help a thoroughly computer
impaired friend  making a boot disk for her RH61 system I have this
enhancement suggestion for mkbootdisk:

If it is run without parameters it should assume reasonable defaults, ask
the user if the defaults are OK and then make the boot disk.

Reasonable defaults could be:
device = /dev/fd0
kernel version could be the latest version found in /lib/modules or maybe
somehow located by looking in /proc/version

Otherwise, the tool works nicely.

  cheers //Johan

Comment 1 Erik Troan 2002-06-03 18:39:49 UTC
perhaps, but nobody else has ever asked for this so...

fwiw, mkbootdisk `uname -r` does what you want. You could (easily) argue that
this would be a much more sane default, but right now it mimics mkinitrd and
that default doesn't make sense for mkintird, so I'm going to leave it.


Note You need to log in before you can comment on or make changes to this bug.