> On Wed, Apr 3, 2013 at 1:30 PM, John Ford <[email protected]> wrote: >> Hi all. We are going to attempt to update the standard romfs file >> system >> to support some additional stuff, like ssh and ???. Can someone give me >> a >> hint where to start? > > Well, the current romfs is mainly busybox (unmodified) and the katcp > tools (tcpborphserver3) > and then some libraries and extra utilities. > > There are several ways of adding more things: > > - build them yourself... probably the most space efficient way of > going about it. > You probably want to look at dropbear rather than the conventional > opensshd > > - Just copy sshd and its needed libraries from the NFS filesystem (a > debian image). > Typically one ends up using ldd to figure out what libraries are > needed and then strace > to find the other missing pieces. > > - Look at some other small distribution as a starting point ... > openwrt comes to mind >
I guess I was hoping to start with the "standard" romfs build tree and add to that. >> Or is there a better way? > > For quick sharing of files or misc development, just mount an nfs > server export on the roach, say in /mnt > That should be more convenient than scp, though not encrypted. Often > -o nolock can be useful. This sounds like a good way to go. > > Our plan is to treat a roach as an appliance (eg printer) where one > uses katcp (instead of say ippl) > to operate the system remotely. I suspect we'll gradually add features > to optimise some of that, eg > eliminate certain polling operations. I think this is fine to a certain extent, but I think there is a network latency issue with it being remote that will sometimes force us to run programs directly on the PPC that will interact with the FPGA programs. Maybe not... Thanks for the info. John > > regards > > marc >
