Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 58945 - qmkbootdisk
Product: Red Hat Linux
Classification: Retired
Component: kdeadmin (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2002-01-28 09:22 EST by Giuseppe Raimondi
Modified: 2007-04-18 12:39 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-09-25 15:29:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Giuseppe Raimondi 2002-01-28 09:22:00 EST
Description of Problem:
if you start qmkbootdisk as normal user you may think it actually created a bootdisk

Version-Release number of selected component (if applicable):

How Reproducible:

Steps to Reproduce:
1. launch qmkbootdisk as user
2. select device and kernel
3. click ok

Actual Results:
you don't get any boot disk and no error messages or warnings at all

Expected Results:
either a request for root password (like many other tools) or a message saying
the bootdisk couldn't be created

Additional Information:
if you start qmkbootdisk in a shell you actually get a "Cannot find root
partition in /etc/fstab" message. What if you start it from Gnome/KDE panel?
there's no warning there... just an 100% ok which makes you think the floppy is
Comment 1 Gerald Teschl 2002-03-06 11:38:52 EST
I guess this is due to the use of labels rather than devices in fstab.
Probably it should be linked against console-helper.
Comment 2 Giuseppe Raimondi 2002-03-07 04:26:00 EST
I'm not sure about it, since if you run it in a root shell it does exactly what
you expect.
Comment 3 Ngo Than 2002-10-06 08:17:50 EDT
it needs console-helper.It's fixed in rawhide.

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