Once again thx for the details. I tried now to setup and apply the changes but more questions appear. I hope you don’t mind especially since I might lack some basics.
I followed the instruction, downloaded the scripts, launch ./build_image.sh and this starts automatically a download for Ubuntu quantal (12.10). Since I am not very familiar with the syntax for command-line arguments I have no idea, what arguments should I apply to get a build for raring (13.04). Neither --distro raring nor --release raring work. Changing config.in to only get raring didn’t help either.
Hm’, I’m not really sure if I made myself clear - I guess not. I want to have something like
ln -s /usr/share/zoneinfo/Europe/Paris /etc/localtime
resp.
"cat > grepall
#!/bin/sh
find . -type f -exec grep -q $1 {} ; -print
" ########### which I can as well store in a prepared file and then only
“cp grepall /usr/local/bin/”
(Or static eth0 config).
The reason why I mention it is due to the pointers I assume regular boot-up-scripts should run regularly. But I’m not interested in that cause to my understanding the changes are already save permanently. So, they need to copied/applied just once.
Thx. Is it also possible to assign root as well a default password? On the above link or somewhere else?
Thx. I guess my workaround will be the default user with some default pwd.
Looks great. Thx. Especially this give freedom to add own packages.
- install resp. compile automatically the latest kernel
easy enough…
Hm’, I assume that the build should take automatically the latest build. Right?
When I review the output I get e.g.
chroot_KERNEL_HTTP_DIR=“https://rcn-ee.net/deb/quantal-armhf/v3.11.0-rc6-armv7-x10/ https://rcn-ee.net/deb/quantal-armhf/v3.7.10-x13/ https://rcn-ee.net/deb/quantal-armhf/v3.8.13-bone26/”
which gives me headache cause its bone26 instead of bone28.
And my second question for this: If I have made the script the way I like
it, i.e. run perfectly on the SD card - how to flash the content to the
eMMC?
(this was designed for images created with “omap-image-builder”
https://github.com/RobertCNelson/tools/blob/master/scripts/beaglebone-black-copy-microSD-to-eMMC.sh
I didn’t test it due to my above obstacles, but I’m curious if there is the practical restriction of the SD-card. Namely e.g. 15GB SD card wouldn’t fit into 2GB eMMC - which is clear. When I boot up I see 13GB space are left, 1.2 GB used. Am I able to flash that amount or is there the logical limit restriction for 2GB? PLUS when I configure swap-file of eg. 500 MB do they remain on the SD-card or will they be flashed as well?
Response rep. help would be highly appreciated.
leo