Jeremy Huntwork wrote:
>
>Therefore, the question comes up, how do we get the cross-compiled
>tools over to the target machine and set up the user to finish the
>remaining book? To date, I think the suggested method has been to tar
>up the tools and kernel, and copy them over, *somehow*.
Heh
>I think it was proposed to have various hints written that could
>link to the book showing possible ways of accomplishing this.
Personally, I attach a new disk into the build machine, partition it up
and mount it under ${LFS}, do the build, then transfer the whole disk
to the target machine. Bootloader can be a little fun though depending
on which one is required...
Tar up and untar is not really a sustainable option.
How do you untar a tarball onto the target if it has no OS?
How do you get it on a filesystem if target doesn't have ext2/3/etc
support and doesn't provide a filesystem you are capable of booting
linux from? (genext2fs)
Other options if cross-compiling on same-host with different OS
is to setup a slice/partition to build into, then layout an ext2
filesystem (if supported on that host, if not use genext2fs)
Alternatively Jim is looking at network booting the whole shebang...
Many ways to skin that cat...
>This just feels wrong to me on several levels:
<SNIP>
>
>3) We're giving them an option in the book but not really seeing it
>through. We say, in effect, "you need to get to this point to finish
>the book, but to do that, you have to get there yourself - see you
>there!"
>
>To have their system usable and able to build the remaining LFS -
>they'll need to not just switch over to that machine, but actually
>boot it with a Linux kernel
Yep
> which also implies a bootloader and perhaps
>some simplistic bootscripts.
Current LFS bootscripts do the job fine ;-) (with a small edit)
They are what I currently use...
>If we're asking that much of them at that point
>already, why not just finish the job? With a couple more simple
>packages and a few instructions on how to bring it all together, we
>could give to them a complete solution in the form of a minimal
>bootable cd.
True, current cross-lfs scripts provide all that is required for a
bootable disk image (and most of what is required for network booting),
shouldn't be too much of a stretch to make it a bootable CD...
I'd also recommend also adding unionfs support if we go the cd route,
boot the cd, union the cd filesystem and the final target-host
filesystem, build away...
>By far, the majority of machines out there can boot from a cd,
>and the methods to produce one are already documented - we just
>have to bring them in.
>
>Anyway, I realize there are likely to be different opinions on this
>one, but I wanted to put this forward for comments. Personally, it
>would make me feel much more comfortable with where we're leading
>the reader.
Still early days yet ;-)
Best Regards
[R]
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
