Quote:
Originally Posted by tshering
Did you double-check that the edited version is in /bin and did not end up in a different location because of a typo?
|
Yes, in fact the one I uploaded to MR was actually loaded from /bin/busybox after I telneted into the device after reboot because the original edit on my PC was lost. Whatever I've done wrong, or however busybox it doing what it does -- it's not at all obvious. Though I'm willing to check *any* angle.
I can log in now, here's a capture of a telnet session:
Code:
bash-4.2$ !tel
telnet AndrewsKoboHD 2323
Trying 192.168.3.128...
Connected to AndrewsKoboHD.
Escape character is '^]'.
^]
telnet> mode char
~ # stty sane
~ # cd / ; find . -iname busybox
./bin/busybox
~ # md5sum /bin/busybox
0b17487b53dd95a306d834bb8a7ebd79 /bin/busybox
~ #
~ #
And, if I transfer the file to my PC using my mime transfer shell script -- my main machine's checksum agrees.
Note, my kobo's wireless has opened telnet port 2323, and when the wireless connects it exports a host name I defined in /etc/init.d/rcS -- so my host PC which is running DNSmasq finds my AuraHD by the name (AndrewsKoboHD); I can't get a wrong ip address that way. The same device I do the telnet tests on has to be the one that I receive the file from. There wasn't a GloHD when I made the name up -- so AndrewsKoboHD is actually my AuraHD.
Quote:
bash-4.2$ export REMOTE="AndrewsKoboHD 2323"
bash-4.2$ mmget.rc /bin/busybox
remote 0b17487b53dd95a306d834bb8a7ebd79 /bin/busybox
local 0b17487b53dd95a306d834bb8a7ebd79 busybox
bash-4.2$
|
So, there is no other file on the drive named busybox, unless find is malfunctioning. (I have no reason to believe it is broken.)
Of course, there is another copy on the factory restore partition (mmcblk0p2) -- but I don't know how that one could possibly be running as that partition is not mounted; and it's not possible to umount a partition if a binary is being run from it as far as I know.
Quote:
~ # mount
rootfs on / type rootfs (rw)
/dev/root on / type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
none on /proc type proc (rw,relatime)
none on /tmp type tmpfs (rw,relatime,size=16384k)
none on /dev type tmpfs (rw,relatime)
none on /var/lib type tmpfs (rw,relatime,size=16k)
none on /var/log type tmpfs (rw,relatime,size=16k)
none on /var/run type tmpfs (rw,relatime,size=128k)
none on /sys type sysfs (rw,relatime)
/dev/mmcblk0p3 on /mnt/onboard type vfat (rw,noatime,nodiratime,fmask=0022,dmask=0022,codep age=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/mmcblk1p1 on /mnt/sd type vfat (rw,noatime,nodiratime,fmask=0022,dmask=0022,codep age=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/mmcblk1p3 on /mnt/user type ext2 (ro,noatime,nodiratime,barrier=1,data=writeback)
/dev/mmcblk1p2 on /mnt/home type vfat (rw,noatime,nodiratime,uid=500,fmask=0022,dmask=00 22,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
|
Though, now that I'm looking -- it doesn't actually say what device partition is mounted as root.
When I check the Kobo's /proc/mounts, it says that "/dev/root / ext4 ..." is the mounted partition.
But there is no /dev/root found in the udev device directory.
But if I do "mkdir /test ; mount /dev/mmcblk0p1 /test" (The expected root partition)
It says: mount: mounting /dev/mmcblk0p1 on /test failed: Device or resource busy
and it does allow me to "mount /dev/mmcblk0p2 /test" (The expected system restore/reset partition)
So -- root pretty much has to be a mounted version of mmcblk0p1 ...
Question: Can anyone verify that the md5sum I get for the unedited busybox ( ffa324c328fdc4c168433337d4c58c7f ) is the same as is on their device? ESP: for anyone with an AuraHD or a GLO ? According to Talusan, busybox is in the upper git repository directory is up to date -- and since there is only ONE version of it in over a years time; I would expect more device's updates to share a busybox with the same md5sum. eg: I would like to know if that is correct or not.
I'm not sure when talusan says things, that he means by his words the same thing I think he means by his words. It's not that I'm accusing him of anything -- just that I'm new at this. For example, he talked about 100MB being a github limit for binaries, as a justification for why he had to break out busybox in to the upper github directory -- but if you check, he added an KoboGloHD directory (A very large new directory) to the lower directory which supposedly already too big... SO maybe he meant something different than I what I thought he meant.... what does binaries have to do with busybox sourcecode, anyway?
eg: -- I have no idea if I understand talusan correctly when I point to the upper Github directory as being the busybox repository for all devices, but I'd like to find out.