|
I tried two different ways of accessing a Linux chroot. The chroot itself is stated by Linux deploy which works as expected.
Initially, I tried my usual setup with the xsdl xserver app. It loads up OK with since patience, but really seems to draw a lot of CPU power (don't quite remember, but I think I had 30-40%load when idle). So that is possible in principle (and would be more flexible for seeing keymaps with setxkbmap and so forth), but doesn't seem lots of fun on a single core CPU.
My alternative is to use the vnc server method in Linux deploy and acres that with the bvnc app. That seemed to be the least resource hogging one among the ones I've tried, I think you get below 10%CPU load when idle (maybe even below 5?)and some reasonably low memory load.
Gedit is rather usable that easy, I think - it's still a tad slow, but more comfortable than with xsdl (where it's also possible but with the high cpu usage battery life should take a plunge). Is poetically use it more often if 1) it was still a bit faster, 2) I'd get around the keyboard mapping issue and 3) I had a larger screen than the 6.8 of the T68+. Given the relatively show scroll speed (partly due to the eink, partly due to simple cpu limitations), it's harder to get an overview of a larger piece of text on such a small screen, since you'll try to not scroll around too much.
Hope this helps.
|