Quote:
Originally Posted by antithesis
As a Kindle DX user outside the US, I'm getting this error as well.
I think that if I took more time, I'd figure out how to SSH into the device, but the fact of the matter is that I don't have much time on my hand, and I find SSH'ing a lot of hassle for a task as simple as changing the date (I don't know what else I'll be using SSH for either).
I've been thinking, maybe we could figure out an easier way to install KUAL for people outside the Whispernet area who don't want to get their hands dirty with SSH. I figured that it complains about the date, because the "last accessed" and "last modified" dates are, according to the device, in the future, because the DX thinks it's 1970. I have no clue why it would be so picky or how that is even relevant for running the file, but it's what the error message suggests.
I tried changing those dates to 1970 using both Linux and Windows utilities, and those utilities work, but when disconnecting and reconnecting the device, you'll see that it just resets the date to what it was before. Likewise, the error reoccurs. It seems that the DX resets those dates as soon as it's unplugged.
Where to go from here: - First of all, figure out whether or not changing those dates will have any impact in the first place. The error message also states something about permissions (which I've set to 777). What does it mean?
- If the device indeed resets the dates on disconnect, perhaps it stores a backup of the metadata somewhere. If only we could find out where, and edit that.
I'll dig into this further, but for now, any help would be appreciated. |
There are two "times" in Linux -
The "system time" - something stored in the software;
The "hardware time" - stored in the hardware;
You have to re-set the date/time in the hardware clock to have any lasting effect. The utility for that is, aptly: hwclock
man hwclock
will give you the details (on a Linux system with manuals or in a web-search engine).
On the DX you have two choices -
Re-set the hardware clock from the 3G access point, or
Re-set the hardware clock yourself.
PS: you don't **have** to "mess with ssh"
The USBnetworking package also installs the telnetd server -
Just telnet in over the USB cable after installing the package, no username/password required.