Thanks for trying this, mateorod. I'll try to figure out what's going on with the hello package. The hello executable is actually just a shell script -- just have a look inside /system/bin/hello (cat /system/bin/hello). I wasn't intending to make anything special with it... just an example of how an Opkg package might be constructed. I appreciate the time you've put into this!
Oh, and if you're using the GUI: it automatically remounts /system for you, and it should raise a root request when that happens. it should also request root when it actually installs something (including itself, during the bootstrap phase). And, after it's done what it wanted to do, it makes /system read-only again (but only if it had to remount rw in the first place).
Updates from my end:
nb: runit is currently not able to start itself; but you could start it using `nohup runsvdir-start &`. this should also bring up dropbear, if you have that installed too. runit might also consume more electricity by monitoring processes; but that's going to happen anyway with dropbear running... I'll have to test battery usage.
I have a couple of screenshots demonstrating runit, dropbear, dtach, and weechat. I have dropbear running on my [CM9] nookcolor, monitored by runit. I have weechat running on the nookcolor, under dtach. On my netbook, I am ssh'd into the nookcolor and sharing the weechat screen. The reason that the netbook view is slightly funky is that I'm letting the nookcolor control the terminal size/shape; I could just as easily make it netbook-friendly (but then it would look strange on the nookcolor).
Oh, and if you're using the GUI: it automatically remounts /system for you, and it should raise a root request when that happens. it should also request root when it actually installs something (including itself, during the bootstrap phase). And, after it's done what it wanted to do, it makes /system read-only again (but only if it had to remount rw in the first place).
Updates from my end:
- python now works with hashlib
- made lots of development packages, which is good for building stuff directly on the device (but i haven't actually tested them yet)
- packaged runit, a service watchdog that keeps your stuff running
- packaged dropbear, a small ssh client and server (with support for runit)
- packaged dtach, which provides the gnu screen functionality for sharing shells
- packaged weechat, an irc client
nb: runit is currently not able to start itself; but you could start it using `nohup runsvdir-start &`. this should also bring up dropbear, if you have that installed too. runit might also consume more electricity by monitoring processes; but that's going to happen anyway with dropbear running... I'll have to test battery usage.
I have a couple of screenshots demonstrating runit, dropbear, dtach, and weechat. I have dropbear running on my [CM9] nookcolor, monitored by runit. I have weechat running on the nookcolor, under dtach. On my netbook, I am ssh'd into the nookcolor and sharing the weechat screen. The reason that the netbook view is slightly funky is that I'm letting the nookcolor control the terminal size/shape; I could just as easily make it netbook-friendly (but then it would look strange on the nookcolor).
Last edited: