Bug 19156

Summary: Enable the doFS.sh to run in arbitrary locations
Product: Base System Reporter: patrick <patrick>
Component: kernAssignee: jkh
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.0-STABLE   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.diff none

Description patrick 2000-06-09 23:10:00 UTC 
The doFS.sh script in /usr/src/release/scripts can only work in a chrooted
environment because it references /dev directly to access the vnode device
being built.

This makes it difficult to use the script outside the scope of a make
from the /usr/src/release directory (which runs it in a chroot'd dir).

Also the mount point has to be specified as an absolute path.

Fix: The following patch transform the path for the mount point to a absolute path
and gets the location of the device directory to use from the command line
(following the mount path argument). The device path is also canonicalized to
an absolute path.

If needed the script will also create the devices and mount directories. If the
directories were created by doFS.sh, they will be removed after the script is
done.

The /usr/src/release/Makefile is updated to provide the location of the devices
directory to the doFS.sh script.


How-To-Repeat: 
n/a
Comment 1 Sheldon Hearn freebsd_committer freebsd_triage 2000-08-07 14:45:23 UTC 
Responsible Changed
From-To: freebsd-bugs->jkh

Over to the chief release engineer.
Comment 2 jkh freebsd_committer freebsd_triage 2002-08-12 21:41:25 UTC 
State Changed
From-To: open->closed

Given the rather limited scope of doFS.sh, this limitation is sort 
of a feature of the design of the overall release process and won't 
be changed until/unless the entire "build in chroot" approach changes.