| 1 |
Marcel Romijn wrote: |
| 2 |
|
| 3 |
> I used genkernel, with the --minkernpackage and --modulespackage |
| 4 |
> options, to create a kernel.tar.bz2 and modules.tar.bz2. This has |
| 5 |
> support for ALSA and my sound interface. With gnap_remaster I created a |
| 6 |
> new core. |
| 7 |
> |
| 8 |
> However, since I did not have my setup ready for CF, I tested it by |
| 9 |
> using gnap_overlay to create an ISO. Booting from the ISO resulted in |
| 10 |
> the following: |
| 11 |
> |
| 12 |
>>>Mounting squashfs filesystem |
| 13 |
> mount: Mounting /newroot/mnt/cdrom/livecd.squash on /newroot/mnt/livecd |
| 14 |
> failed: No such device |
| 15 |
|
| 16 |
Maybe your kernel lacks squashfs support ? |
| 17 |
|
| 18 |
> How can I emerge alsa-utils in such a way that I know which files it |
| 19 |
> pulled down? |
| 20 |
> If I just do an 'emerge alsa-utils', the files will end up in my |
| 21 |
> development environment. Is there a way to isolate where the emerged |
| 22 |
> files end up? Is it a chroot trick? |
| 23 |
|
| 24 |
The "ebuild" command is your friend. For example : |
| 25 |
|
| 26 |
ebuild /usr/portage/app-whatever/whatever-2.0.ebuild install |
| 27 |
|
| 28 |
will unpack, compile, and prepare installation for whatever-2.0. The |
| 29 |
image containing all the files will be located in : |
| 30 |
|
| 31 |
/var/tmp/portage/whatever-2.0/install |
| 32 |
|
| 33 |
-- |
| 34 |
Koon |
| 35 |
-- |
| 36 |
gentoo-embedded@g.o mailing list |
Archives