On Thu, Mar 6, 2014 at 1:22 PM, Antti Kantee <[email protected]> wrote: > Hi, > > I got tired of typing "./rumpremote foo args" and built some wrappers so > that you can now just run "foo args". This is done via a shell env that > you first source to enter "rumpremote mode". For example: > > pooka@watou:~/src/rumprun/rr$ . rumpremote.bash > rumpremote (NULL)$ export RUMP_SERVER=unix:///tmp/tst > rumpremote (unix:///tmp/tst)$ sysctl kern.hostname > kern.hostname = rump-23969.watou > rumpremote (unix:///tmp/tst)$ ifconfig -a > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33648 > inet 127.0.0.1 netmask 0xff000000 > rumpremote (unix:///tmp/tst)$ export RUMP_SERVER=unix:///tmp/tst2 > rumpremote (unix:///tmp/tst2)$ !sysctl > sysctl kern.hostname > kern.hostname = rump-29095.watou > rumpremote (unix:///tmp/tst2)$ unload_rumpremote > pooka@watou:~/src/rumprun/rr$ > > It's called .bash because apparently bash is the only bourne-type shell > which evaluates PS1 on the fly. I think having $RUMP_SERVER in the > prompt is useful. > > Now, questions: > should this be the default mode of operation? In other words, should we > use this for the automated tests and docs?
Sounds tidier. i don't think I would be inclined to use it for the tests, but probably would for the docs. Test machines might not have bash installed, and then the tests document what is going on, while the docs are more readable. > What should the relationship of rumprun and rumpremote be? It seems to > be like they're completely different animals. Should there be two > separate builds? For one, rumpremote doesn't require building the > kernel components. Also, the above type wrapper for rumprun is only > available e.g. via the Lua console, and cannot be implemented using a shell. If you can make a simpler build that is quicker and only builds rumpremote then we could make that the default and use for all the tests. I have some use cases for rumprun, but can always fork it... > I pushed my hacks onto the "shellenv" branch of rumprun on github. > > - antti > > ------------------------------------------------------------------------------ > Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. > With Perforce, you get hassle-free workflows. Merge that actually works. > Faster operations. Version large binaries. Built-in WAN optimization and the > freedom to use Git, Perforce or both. Make the move to Perforce. > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk > _______________________________________________ > rumpkernel-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/rumpkernel-users ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
