9 replies to this topic

[hemispherical1]

Recently I realized I wasn't the only one that wished the DM800 would save shell command history across logins. I tried updating the busybox config (openembedded/recipes/busybox/busybox-1.18.5/openpli/defconfig), updating the options:

CONFIG_FEATURE_EDITING_HISTORY=100
CONFIG_FEATURE_EDITING_SAVEHISTORY=y

The resulting busybox binary seems to work fine & it didn't grow in size at all. Unless someone thinks it's too much wear & tear writing the history to flash (only reason not to add it I could think of), could this be added to the images?


Thanks,
--
hemi

Ps. I just noticed OE E1 image has it included already...

Edited by hemispherical1, 31 October 2011 - 06:45.

[pieterg]

I removed it, because that messes with the history if you have more than one shell at the same time (as is usually the case here).
This option saves the history before you logoff, and the other shell re-reads the history, as a result you have no usable history in either shell.

With the option disabled, at least you have a working history in every shell, though the history is not saved.

[hemispherical1]

I guess that is that. If anyone wants to add the feature to their image, they can build an image with the edits noted above & force busybox to be rebuilt, or I'll add the dm800 binary I built with Oct.30 source code.

A note of caution, I had no trouble overwriting the existing busybox binary. I ftp'd it to /bin/busybox~ then in telnet cp /bin/busybox~ /bin/busybox & rebooted, it worked fine for me. Then I gave a copy to someone else and they managed to hose their box, requiring a reflash. I don't know what went wrong, but you've been warned. It would be a good idea to make a backup just in case...


--
hemi

Ps. The binary was built for the dm800, I don't know if it has all the required calls compiled in for other mips e2 boxes.

Pps. Added the ipk.

Attached Files

•  busybox.zip   385.96KB   6 downloads
•  busybox_1.18.5-r42.8_mipsel.ipk   389.97KB   1 downloads

Edited by hemispherical1, 31 October 2011 - 19:45.

[bigroma]

You can just install package after removing files in /var/lib/opkg. I think this way better then manual replacement file.

[hemispherical1]

Yes, it probably is, I'm just a manual sort of guy...


I added the ipk to first post.

--
hemi

[pieterg]

What would be even better is that somebody would fix the feature;
-read history at login
-write history at logoff

[pieterg]

Just gave it a quick test, and actually, it's a lot more usable compared to when I last used, and disabled it in frustration.
history is not saved untill you logoff, and read only on login.
So they have fixed a few things in the meantime.

I'll add the history settings.

[hemispherical1]

Thank you!

--
hemi

[jimux]

There is no problem with having more than one busybox installed and provided you want to use it just for remote users then a readymade binary from busybox.net will suffice. Just put the second copy elsewhere on the path. I use /usr/local/bin as it is the first searched by a remote session but not by enigma. Initially set up some new user IDs with the adduser command and point to new shell. For example, create users admin and ashman as below....
/usr/local/bin/busybox adduser -h/home/admin -s/usr/local/bin/sh admin
/usr/local/bin/busybox adduser -h/home/ashman -s/usr/local/bin/ash ashman

[jimux]

Forgot to add..... Once remote users run latest busybox then they have full hush features, and individual IDs maintain history across their own sequential sessions. Try the smaller ash shell for remote users.