Bug 144269 - Add --bind and --move support to the nash builtin mount command
Summary: Add --bind and --move support to the nash builtin mount command
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: mkinitrd
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Peter Jones
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-01-05 13:51 UTC by Kasper Dupont
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-03 22:35:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Add --bind and --move support to nash builtin mount command (1.06 KB, patch)
2005-01-05 13:52 UTC, Kasper Dupont
no flags Details | Diff

Description Kasper Dupont 2005-01-05 13:51:21 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Gecko/20040922

Description of problem:
If you want to use a subdirectory of a filesystem as your root, a
bindmount is needed before pivot_root. It is quite simple to add
--bind and --move support to nash.

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

How reproducible:
Always

Steps to Reproduce:
1. nash --force
2. mount --bind -t none /mnt /mnt


Actual Results:  (forcing normal run)
Red Hat nash version 3.5.22 starting
mount --bind -t none /mnt /mnt
mount: error 19 mounting none


Expected Results:  nash sets up a bindmount:

(forcing normal run)
Red Hat nash version 3.5.22 starting
mount --bind -t none /mnt /mnt


Additional info:

I'll attach a patch in a moment. After that I'll try to enhance the
mkinitrd script to make use of this new feature.

Comment 1 Kasper Dupont 2005-01-05 13:52:37 UTC
Created attachment 109366 [details]
Add --bind and --move support to nash builtin mount command

Comment 2 Matthew Miller 2005-04-26 16:26:17 UTC
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.


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