Saving a few write cycles to the internal storage in the process. It can also be used to update the "core" component, saving you an USBMS session and a reboot, and quite a bit of time,Īs it will then use a much more efficient compression algorithm than the standard KoboRoot tarball.Īnother major interest in doing it this way is that the compressed data will never make it to disk, Ideally, do that in a tmux session: e.g., to install/update Python 3, runĬ.f., /usr/local/stuff/bin/update-kobostuff.sh for more details (including how to do offline updates). Or by simply keeping the WiFi popup open), then run update-kobostuff To install (or update) Python, make sure WiFi is enabled and will stick around (i.e., either via ForceWifi, Only the "core" stuff is bundled (i.e., everything except Python). Instead of shipping *everything* in the install KoboRoot tarball, NOTE: Since v1.6.N, the way Python is handled has changed a bit. If you have custom stuff in (or symlinked in) /usr/bin, take a closer look at what this package installs to avoid overwriting your own stuff. This touches neither rcS nor inittab, but if you already have an inetd setup in your inittab, you should probably clean that up, or it will clash. If you really need to, I'd recommend disabling inetd, setting up ssh shared key auth, making dropbear actually check passwords,Īnd locking dropbear to shared key auth only:īy removing the -n switch & adding the -s switch to its startup args, see the comments in /usr/local/stuff/bin/stuff-daemons.sh. Since everything is passwordless, running this on a public/open WiFi would be a *terrible* idea. This script is used to launch both inetd & dropbear. (AFAICT, that loop0 udev trick is used in a number of Kobo packages (David Beinder's kobo-nightmode and Andreas Klauer's AutoPatch, for instance), It also installs an udev rule providing a means to run an user-editable script (/usr/local/stuff/bin/stuff.sh) early during boot. If you want an easy way to launch this script (besides in a shell via SSH over WiFi, as it's symlinked as usbnet-toggle), That said, you *can* manually toggle USBNetworking (provided your device isn't truly ancient), if need be:Ĭ.f., /usr/local/stuff/bin/usbnet-toggle.sh for more details (in particular the fact that I'm using legacy Kindle IP settings p). There is *no* automatic USB networking handling here. The keylist is expected in /usr/local/niluje/usbnet/etc/authorized_keys). The dropbear build provides the same convenience features than my Kindle one (namely, persistent shared key auth: It also provides ftpd/telnetd through inetd (following Kevin Short's KoboTelnet package), plus sshd w/ sftp (dropbear). So almost all of this lives in /mnt/onboard/.niluje, so don't be surprised if stuff goes missing after a factory reset. I still follow the Kindle spirit of "don't put anything in the rootfs if you don't have to", Sshfs is also bundled, although Kobo kernels do not ship with FUSE enabled, so making use of it will requireīuilding/installing the proper kernel modules, c.f. ).Īnd yes, just for kicks, there's also KindleTool in there D. Xzdec, zstd-decompress, lz4, ImageMagick, gawk, nano, ZSH, ag, tmux, GDB, gprof, perf, objdump, cURL, evtest, evemu,įBInk, the full OpenSSH suite, jq, bsdtar, lftp, tree, file, dtc,Īnd a CLI Python 2.7 & Python 3.9 build with quite a few third-party modules (HTTPie, requests & co, Pillow, wand. That includes, among other things, stuff like less, htop, strace, ltrace, lsof, fbgrab, sqlite3, elfutils, rsync, This is basically a collection of all the custom binaries I use throughout my Kindle hacks,īut built for the Kobo, put in a single package, and symlinked (when not clashing) in the PATH.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |