I tried to leave the "l_mid_dbg_p_1.1.007.tgz" on
targets/targ/fs/root and I was hoping this will automatically get into
rootfs, but that didn't happen.
----------------------------------------------------------------------------
I think it is the right way to include more stuff into rootfs. We ever 
installed test suite and more packages into rootfs this way. It should be 
workable. Please double check.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of lifu
Sent: 2008年9月17日 5:48
To: [email protected]
Subject: [Moblin Dev] rootfs on menlow-lpia-moblin2

I recently used image-creator to create a usb live image for platform
menlow-lpia-moblin2. I could boot it up wo/ problem. I'm trying to set up
SEP (or vtune) on it, but I can't figure out how. Vtune's README says untar
the vtune file and run install, but how? I tried three options, none of them
solvd my problem yet. I am not sure if these are the right way to go.

First, I tried to leave the "l_mid_dbg_p_1.1.007.tgz" on
targets/targ/fs/root and I was hoping this will automatically get into
rootfs, but that didn't happen. I thought that mksquashfs will compress
everything under target's file system except those in exclude. However, if I
do mksquashfs manually, it seems to work fine. Other than those in exclude
file, what other files are not compressed into rootfs image. How does
image-creator control it?

Second, the platform doesn't seem to auto-configure NIC. Even the NIC could
be manually ifconfig'ed up,  there is no ftp, scp, rcp, etc to transfer
files. If such tools exist, I could copy SEP or whatever files from remote
site. Is it supposed to be this way? Or did I miss something?

Third, I tried to duplicate image-creator's "create-install-usb" option, but
didn't have any luck. I know it's probably not worth to going this
direction.


In short, when I need to add any applications, tools or source into the
rootfs, what's the right way to do so?

Thanks,
Lifu
_______________________________________________
dev mailing list
[email protected]
https://www.moblin.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
[email protected]
https://www.moblin.org/mailman/listinfo/dev

Reply via email to