M.Canales.es wrote:
El Viernes, 12 de Mayo de 2006 23:17, George Boudreau escribió:
<snip>
If these 4 tests are true then the makefile tests will succeed.
If they fail should jhalfs do the creation automatically or force the
user to do the work?
IMHO, to force the user to fix it.
As a side note, Archiac made me the next suggestions:
- At the end of the build we should to remove the user, group, and homedir, if
they was created by the Makefile, and be sure that all files under $BUILDDIR
are owned by root:root. Also, review if we can unmount the virtual
filesystems at the end of the build. The host should finish in the same exact
state it was in before the build, if posdsible.
Housekeeping is the correct path to take. The ugly bits come from
tracking user/group creation (who did it) and the virtual fs. LFS does a
mount --bind to /dev (to side step starting udev) and mounts some
directories. Whereas HLFS and CLFS do the standard directory creation
and pseudo mount.
With both styles you have to manually create unique makefile entries
and unwind the mount order.
Tracking of user/group creation can be done via semaphore file..
- Evaluate the posibility of using sudo to run jhalfs and the Makefile. That
could to allow to format and mount the partiition and create the system as a
normal user.
I am not sure about this. You must be 'root' to run jhalfs so running
jhalfs via sudo from your user account achieves?? (OK.. you should not
be in root unless you are doing admin/maintenance but..) I am trying a
'sudo' build at the moment to see what nasties pop up..
--
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
