ingmar-k
commented
11 years ago You're welcome. I'm happy if you found the scripts useful.
I'll update the comments and/or README to make these points more clear. ;-)
- "tester" is just a random name, which in case of the "output_dir_base" is the username on the development host, running Ubuntu or Debian. I had a variable handle that first, but found out that Debian and Ubuntu handle for example "${USERNAME}" differently. You run the script as root, but normally want the output to be placed in a user's home directory (at least that's what I wanted). And that doesn't work that well in BOTH Debian and Ubuntu alike, through env-variables. So, to make it short, you can set ANY path here, but it is recommended to choose one in your development user's home dir.
- qemu-environemt needs a valid nameserver setting to be able to download packages. The setting get's placed in the the target rootfs's 'resolv.conf'. Without this the chances that the script will fail are high. Didn't really test it without this setting. Suppose it won't work, though.
- If you want to continue using the old kernel, then the new one sure is NOT necessary. BUT, then using Emdebian doesn't make sense either, because you won't be able to use compressed rootfs in NAND with the old kernel. At least every time I tried it didn't work. And in that case a normal Debian on USB would make more sense.
First of all, thank you Ingmar for making these scripts available!
I looked into the general settings and was confused about a few things:
Maybe you could update the comments to make these things more clear?