On Thu, Jul 05, 2012 at 03:01:22PM +0430, Yasser Zamani wrote: > > > > > Hi there, After doing LFS, I have four questions which may every body ask him > or herself at finish of LFS:
Sensible questions, but in future *please* break up your lines. A line length of 70 or less is preferred, but the real problem I have replying to you is that you've put several questions in one very very long line. This time I've broken it up so that I can reply at the correct places (I must be exceptionally relaxed and chilled out, normally I wouldn't bother ;) Paragraphs would make this easier. Thanks. > How to save a checkpoint to 1) recover and then redo in case of feauture > mistkes Back up the whole system - 'tar' (run by root) normally works adequately. Do this from a different system, either from the original host system, or from a Live CD. To roll back, you would need to *remove* the system containing the failed attempt (e.g. using mke2fs) and then extract all the files from the backup. I don't think I've had to do this sort of rollback in BLFS more than once (several years ago, I was trying to use /opt/xorg and /opt/gnome instead of /usr, but eventually gave up - possibly I rolled back, or perhaps I just scrapped that build). Almost all mistakes in BLFS can be worked around, typically by building an optional dependency that was not installed, and/or rebuilding a package (or rebuilding it with extra configure options), and then perhaps rebuilding some other packages which use it. If you intend to continue to use LFS systems, and you are not experienced in what you wish to use on the desktop, I suggest that you regard your first build as experimental - use it to try out different packages, decide if they are useful to you, and then use this system to build the next one. Scripts are useful! >or 2) deploying LFS to architectural same other machines?I myself tared all >files which are in LFS partition using tar. Does untaring them on an >architectural same another machine and then changing configuration files work? Yes. Normally I build new systems on the machine they are going to run on, but when I get a new machine I will transfer a pre-built system. Obviously, you need to have an existing system, or LiveCD, which is able to extract the tarball and then chroot to it to fix up the configuration and change the kernel .config to match the hardware, and build and install the new kernel. >Do we have to continue package's installation by 1) rebooting to the created >LFS system or we can 2) continue to BLFS in chrooted environment on host >system? What's better and what are similarities and differences?' Provided you have added everything *you* need (in my own case this includes nfs-utils because my /sources, my backups and my notes, are on nfs mounts), rebooting is fine. The upside is that you can confirm the system is working. The downside is that reading the BLFS book and searching for solutions to problems are harder when you only have a tty. Recently, I've several times built most of a complete desktop in chroot - partly to sort out changes in my scripts and any changes required by changes to package versions (e.g. automake-1.12 and perl-5.16). Of course, if there are run-time problems (e.g. recent cairo causing poor rendering with certain versions of the xorg server and the xorg video drivers) these only become apparent after you have booted this new software. You can, of course, periodically boot the host system to use things that you have not yet built on your new system. >9.3. Rebooting the System' section have been cited that we can continue to >BLFS more easier by installing Lynx and GPM then using Virtual Terminals; I've >done installations but I don't know how to setup Virtual Terminals? This means using several ttys, e.g. building in tty1, book open in tty2, etc. >LFS system does not have 'wget' utility. Is there any alternative for >downloading BLF'S packages? if not so, how we should download BLF'S packa > ges in LFS booted system? Thanks in advance! > That is probably one of the packages you should download before booting the new system :) I remember that someone posted an alternative using bash, but that was probably between 8 and 12 years ago. I guess it's in the archives. Lynx can usually download the packages. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
