Mike Frysinger wrote:
> On Thursday 26 April 2007, Jason wrote:
>> This sounds like the solution to my problem, although I'm a bit hesitant
>> to muddy my ${SYSROOT}...
>
> i dont understand what you mean by "muddy" ... it's managed by portage, so
> you
> could just as easily do:
> ROOT=/usr/$CTARGET emerge -C zlib ...
yeah, I think the big fat red warning in the guide led me to assume that
I should only let crossdev populate $SYSROOT... I'm over it now. :-)
>
>> Is this what most people do (libs/headers to SYSROOT)?
>
> it's what i do ;)
Good to know I'm on the right track...
So, small update. I added the serial port to the nslu, and cut the
resistor (change processor speed from 133MHz to 266MHz).
I just uploaded my first kernel (2.6.20-gentoo-r6) and ramdisk via tftp
using this guide[1]. A few false starts with the kernel (serial port
shouldn't be a module, need ramdisk, etc), and it's looking good. It
halts now with two errors, one seems to be a size mismatch between the
kernel's config and the physical size of the ramdisk fs. The other is
asking for a pointer to init... neat.
After doing this:
# xmerge --root /rootfs uclibc busybox baselayout-lite dropbear
# cd /rootfs
# du --max-depth=1
12 ./lost+found
1 ./tmp
292 ./var
4394 ./lib
3406 ./usr
57 ./sbin
21 ./etc
825 ./bin
1 ./home
1 ./root
1 ./mnt
1 ./proc
2 ./dev
9015 ./
Not bad. I haven't even cleaned it out yet (I have a whole bunch of
unneeded modules in /lib)
Jason.
[1] - http://www.nslu2-linux.org/wiki/HowTo/TestAnImageInRamUsingRedBoot
--
[EMAIL PROTECTED] mailing list