Bug 180166 - nash "mkrootdev" and "switchroot" only work with a specific pathname
Summary: nash "mkrootdev" and "switchroot" only work with a specific pathname
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Fedora
Classification: Fedora
Component: mkinitrd
Version: 4
Hardware: i586
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Peter Jones
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-06 15:47 UTC by james
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 06:46:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description james 2006-02-06 15:47:12 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

Description of problem:
Despite the descriptions in the nash manpage, the "mkrootdev <path>" and "switchroot <newrootpath>" will now only work with specific path names, rather than any general pathname or newrootpath.  Specifically:

 "mkrootdev /dev/root" will work, but
 "mkrootdev /dev/rootdev" fails, and
 "mkrootdev /rootdev" fails.

Similarly:
 "switchroot --movedev /sysroot" will work, but
 "switchroot --movedev /rootdir" fails - with device mounted, of course.

The commands use to work as described by the manpage.  It would seem that either nash is broken - has hardcoded paths now? - or the manpage needs to be updated.



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

How reproducible:
Always

Steps to Reproduce:
1."mkrootdev /dev/rootdev" or
  "switchroot --movedev /rootdir"
  in initrd init script.
2.
3.
  

Actual Results:  kernel panic on boot - "attempted to kill init", which usually means that the root file system was not mounted.

Expected Results:  normal boot

Additional info:

Comment 1 Peter Jones 2006-02-21 06:46:14 UTC
I'll gladly apply any patches contributed which update the man pages and reflect
current behavior.  For the time being, though, I'm going to close this bug.


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