View Single Post
Old 05-01-2020, 08:06 PM   #86
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
Okay, packages updated .

As promised, less is now available! (I also updated the git package posted earlier to avoid duplicates).

A possibly to-be-reverted change: I mangled dropbear to force logins to ZSH instead of the awful ash version shipped on Kobo.
It might be a problem because it lives in onboard...
In which case, I have another option waiting in the wing, which is to use the ash from my own busybox build that's installed in the rootfs.

(That whole thing was sparked from an annoying issue I have where scp processes spawned by sh -c via dropbear were sometimes deadlocking for no apparent reason... I smelled stdio buffering issues, so I figured I'd try something else).

Speaking of said busybox build, it's now full-featured, standalone, with all the bells and whistles. While in ZSH, it is put in front of the PATH, so most tools will now behave slightly less terribly. If you actually run that ash version (i.e., exec ash), you won't even need it in the PATH, bb is setup in the fancy nofork & prefer applets mode.
As a reminder, that ash build is the only way to have functional unicode input, because everything is terrible.

Warning: if you test shell scripts interactively, that means I strongly urge you to do so from the crap stock shell directly (/bin/sh), with a clean env. Just in case old busybox & friends choke on some stuff that's handled just fine by new busybox & friends, which is quite likely.

Last edited by NiLuJe; 05-01-2020 at 08:12 PM.
NiLuJe is offline   Reply With Quote