Bug 2770 - initrd options with mkinitrd and mkbootdisk
initrd options with mkinitrd and mkbootdisk
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: mkinitrd (Show other bugs)
6.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-05-12 14:14 EDT by Cristian Gafton
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-07-29 15:32:49 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Cristian Gafton 1999-05-12 14:14:27 EDT
I needed to build an initrd image and a complementary boot
disk with
support for my scsi card and for raid0. In the process I
noticed that
mkinitrd and mkbootdisk work slightly differently and don't
agree
completely with their respective man pages.


Man page for mkinitrd

mkinitrd [-fv] [--with=module] [--preload=module]
         [--omit-scsi-modules] [--version] image
         kernel-version

when executing program however it seems to prefer "--with
module" (in my
case --with raid0)


while man page for mkbootdisk says

mkbootdisk [--version] [--noprompt] [--verbose]
           [--mkinitrdargs <args>] [--device <devicefile>]
            <kernel>

When executing mkbootdisk I found that I needed to specify
the initrd
options as "--mkinitrdargs --with=module" (here I used
--mkinitrdargs
--with=raid0)
Comment 1 Michael K. Johnson 1999-07-29 15:32:59 EDT
mkinitrd accepts both --with=foo and --with foo; it always has
(according to my reading of our version control logs) and
I just tested to make sure that it works.

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