Ann, Curious about the boot over nfs part. Why not install all the development tools with apt-get?
Yes -- I have indeed used apt-get to install build-essential and the other tools on the Plug itself.
1) Because I can modify all the Plug's files from both the x86 development server (which has sophisticated editors, scripting languages, etc.), and from the stripped-down Sheeva. Sometimes it's helpful to modify the filesystem when the Sheeva is powered off.
2) When connected with cat6 cable straight to the desktop x86 NFS server (and maybe its RAID?), it's probably the Sheeva's highest-performing storage solution.
3) The Plug can use all the storage space available to the more powerful development system.
ShPlug is definitely fast enough for development.
I agree -- the Sheeva is fast enough to do its own builds (especially for the things OTHER than the kernel!
), so that's my intention too.
I would be interested in a full tools howto -- where to get the complete environment, ...
Me too, and have put up a thread requesting same. But in place of that, all we can do is share setups. I've only had my Plug a week, so my set up is rapidly evolving. But currently, it's like this:
I have a linux x86, full desktop / development system, which holds various kernels and root filesystems for the Sheeva. These are ultimately organized under one (grand-)parent directory, and exported over both NFS and TFTP. So switching between kernels or filesystems means changing only one u-boot parameter.
For the record, this development system is actually a VirtualBox virtual machine, hosted on my MacBook Pro, and it has two (virtual) network cards: one is connected (via NAT) to the MacBook's AirPort, for internet connectivity; the other is bridged to the laptop's gigabit ethernet card, which is cabled directly to the Sheeva.
The gigabit interface on the Mac, the gigabit interface on the VirtualBox, and the gigabit interface on the Plug are all configured on the the 172.16.*.* subnet, and the linux system forwards packets from one interface to the other, so that the Plug can use the VBox's 172.16 address as a gateway.
End result: I can carry all gear with me in my bag, then carry out the following steps when I'm ready to play:
1) Wake laptop from sleep and restore VirtualBox from its latest snapshot (30-45 seconds)
2) Cable Sheeva to laptop and boot. (another 30 seconds or so to SSH prompt)
Any internet access the laptop has is shared among all systems, and there's no need to use the serial cable.*
*except to switch boot settings, which is one more reason why we need this thread resolved!
But I keep thinking it should be possible to write this env utility in a script language, either bash or something like php... That is my current interest.