Le 27/02/2013 14:31, Pierre Labastie a écrit :
Here is a patch for the common/makefile-functions part (change
Forgot the patch :-[
Index: jhalfs-trunk/common/makefile-functions =================================================================== --- jhalfs-trunk.orig/common/makefile-functions 2012-03-15 16:43:49.232770964 +0100 +++ jhalfs-trunk/common/makefile-functions 2013-02-27 14:19:29.902052962 +0100 @@ -182,7 +182,7 @@ echo $(BOLD) The report file $(BLUE)$(1)$(BOLD) has been created ; \ echo ; \ echo $(WHITE)Please send the $(BOLD)$(MOUNT_PT)/jhalfs/$(1)$(WHITE) ; \ - echo file to $(BOLD)[email protected]$(WHITE) ; \ + echo file to $(BOLD)[email protected]$(WHITE) ; \ echo ; \ echo That will help us to keep more accurate SBU and ; \ echo disk usage values into the book. Thanks. ; \ @@ -198,32 +198,36 @@ @echo -------------------------------------------------------------------------------- @echo @echo To be able to boot your new system you need to follow - @echo the next steps:$(WHITE) + @echo the following steps:$(WHITE) + @echo + @echo $(tab_)- Mount the virtual files as in -Preparing the Virtual + @echo $(tab_)Kernel File Systems-: first mount /dev and then the + @echo $(tab_)virtual files. + @echo + @echo $(tab_)- Enter the chroot environment using the command found in the + @echo $(tab_)section -Cleaning Up-, except if building CLFS with METHOD=boot. + @echo + @echo $(tab_)- Set a password for the root user. It may be a good idea + @echo $(tab_)to create at least one unprivileged user and to set his(her) + @echo $(tab_)password. + @echo + @echo $(tab_)- Edit or create /etc/fstab, /etc/hosts, /etc/resolv.conf, + @echo $(tab_)/etc/sysconfig/clock, /etc/sysconfig/console, + @echo $(tab_)/etc/sysconfig/network, /etc/sysconfig/ifconfig.eth0 and + @echo $(tab_)any other configuration file you might need. + @echo $(tab_)Review also the file /etc/sysconfig/rc.site, and edit it + @echo $(tab_)as needed. + @echo + @echo $(tab_)- Set up the boot loader, except if building CLFS with + @echo $(tab_)METHOD=boot. There are roughly two ways to do so: + @echo $(tab_)(a) Use the host bootloader: it is better then to exit + @echo $(tab_)the chroot environment. + @echo $(tab_)(b) Use the LFS just built boot loader, following -Using GRUB + @echo $(tab_)to Set Up the Boot Process-. + @echo $(tab_) + @echo $(tab_)- Exit the chroot environment and umount the virtual files, + @echo $(tab_)following -Rebooting the System-. @echo - @echo $(tab_)- Enter to the chroot using the command found - @echo $(tab_)in the section -Entering the Chroot Environment- - @echo $(tab_)except if building CLFS with METHOD=boot. - @echo - @echo $(tab_)- Set a password for the root user. - @echo - @echo $(tab_)- Edit or create /etc/fstab, /etc/hosts, /etc/sysconfig/clock, - @echo $(tab_)/etc/sysconfig/console, /etc/sysconfig/network, - @echo $(tab_)/etc/sysconfig//network-devices/ifconfig.eth0/ipv4 and - @echo $(tab_)any other configuration file required to suit your needs. - @echo - @echo $(tab_)- Exit from the chroot. - @echo - @echo $(tab_)- Set-up the boot loader, except if building CLFS with METHOD=boot. - @echo $(tab_)You can set-up the host bootloader or the new boot-loader - @echo $(tab_)installed on the new system. - @echo $(tab_)If the last, you must to mount the virtual filesystems, re-enter - @echo $(tab_)the chroot and be sure that /dev is populated with the - @echo $(tab_)required devices before configure the boot-loader. When ready, - @echo $(tab_)exit from the chroot and umount the filesystems - @echo - @echo If you are an experienced LFS user, several of those steps can be - @echo skipped or done in a different way. But then, that is something - @echo that you already know and there is no need to discuss it here. @echo $(BOLD) @echo -------------------------------------------------------------------------------- @echo $(tab_)$(tab_)$(GREEN)Have a nice day $(ORANGE):-\)$(BOLD)
-- http://linuxfromscratch.org/mailman/listinfo/alfs-discuss FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
