M.Canales.es wrote:
El Sábado, 13 de Mayo de 2006 02:08, George Boudreau escribió:
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.
For a LFS build I borrowed some code from 'clean_chapter6' to do the
housekeeping. It worked last evening but I am doing a full build this
morning.
Housekeeping for HLFS/CLFS builds is a problem, they run udevstart
at the end of the final stage. This causes the system udevd to be
replaced ( ? true/false ) and $MOUNT_PT/dev becomes owned by the new
udevd and unmountable (? true/false) On my own system I just kill udevd
and let it restart itself when the next event occurs. NOT the nicest
thing to do to an innocent program but I have no other idea.
Tracking of user/group creation can be done via semaphore file..
Forgot, we already track user creation with the file 'user-lfs-exist'.
I left on your hands to decide how all that could be best fixed ;-)
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..
That is basically for those folks that don't like scripts running as root.
Actually the partition formatting and mounting steps can be done also if we
forced jhalfs to be run as root when that feature is on.
--
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
