Bug 8889

Summary:	mkbootdisk should run OK without parameters
Product:	[Retired] Red Hat Linux	Reporter:	Johan Walles <johan.walles>
Component:	mkbootdisk	Assignee:	Matt Wilson <msw>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1	Keywords:	FutureFeature
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-01-26 09:14:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.