Archaic wrote:
In an attempt to get this info both archived, and presented to the larger community, I am writing up a synopsis of ideas that have been floating around on IRC as to how to handle the chroot/reboot phase of the cross-lfs book. I will list them and give a brief pro/con for each as I understand it.1) Tar up the temptools and *somehow* move them to the target. |-> This one has many drawbacks as it requires that the host already has an OS and that host has the ability to create partitions, etc. in preparation for the tarball. If the system is remote, then it will require uploading a sizable tarball to the host, assuming the host knows what to do with it. Even in the day of high-speed personal internet, upload speed sucks. :)
This one, IMHO is the worst possible option to support in the book. The others of course, too, have drawbacks, but this one is by far the worst. I would rather see the book *only* have a chroot path than have a tar/copy files for your new system.
In fact, the more I think about it, I think this is the way we should go. Where the book currently splits, there should be an explanation of the different courses a reader could take with links that point to hints on various methods of getting the new tools onto the target machine and in an environment where they can then finish the book. Each hint should leave the user ready to pick up just where the user enters into chroot, and allow them to successfully finish the build.
After spending some time on the "reboot" section, I think it's a mistake to include any of that extra stuff in the book. Esp. when it still seems that more will be taking the chroot path anyway.
-- JH -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
