Quote:
Originally Posted by newman
donB006: I suggest you read the original guide, if you haven't done so already, I know it's quite verbose but it contains valuable information, e.g. regarding your former problem with .dat files.
re syslog-ng.conf: Feel free to extract the file from your Kindle and bspatch it on your PC with a the binary patch from the OTA update. Then verify the MD5s (the original, the patched and the expected-new). See how the script does it, it's fairly simple shell string match. (I somehow guess that you still don't have the proper/expected/vanilla syslog-ng.conf file.)
|
Thank you for the information. I went back and tried carefully to follow your excellent guide. In my case to simply edit the Amazon 3.3 update for my 3.1 installation would not work. I was able to extract the files and make an update following your directions for the 3.4 update.
I have discovered the file I thought had the desired md5sum was actually the file to result after the patch. The CURRENT means the old file, the EXPECTED is the md5 required of the patched file and the PATCH is the md5 of the patched file. I was trying to make the CURRENT = EXPECTED and I should have tried to make the PATCH(ed) = EXPECTED.
Because I already have the file expected after the patching no changes were needed and I commented out the section trying to update the syslog-ng.conf. I then found I must have also edited the tinyrot.conf file so I also commented that out. The update then almost finished before finding a mismatch with the md5 for the libdtp_module.so.0.1 after patching. So I have my own problems here now although your updating technique works for me almost to completion.
Quote:
|
Originally Posted by knc1
Note:
You can find bsdiff and bspatch both in source and in binary if you search the web a bit.
It is a utility that hasn't changed for years (decades?).
|
I found the bspatch for my debian in the bsdiff package. I was able to get the same result on my desktop as inside the DXG. I had the expected result and the Amazon binary patch for a file I did not have. I tried to patch a few different versions of the syslog-ng.conf and compare the result with the expected result without a match. I found the 'patch -R' not the 'bspatch -R' option so I finally edited the shell script to leave the syslog-ng.conf file I now have because that is what Amazon wanted in the end anyway.
I now see I need to decide how much of the K3G updates I want to allow for my DXG. Yifan Lu originally decided for the 2.5.8 upgrade to 3.1 installation and now I have a mixture of old DXG versions and K3G versions. I am going to follow this thread and study the guide in the original post to see if I can learn enough to do the upgrade properly. I feel I don't understand enough now to know whether I should upgrade certain packages or not to go from 3.1 to 3.3. I have seen some more threads addressing these matters like the 3.2.1 update so maybe I can look there too.
I recently upgraded my K3G from 3.1 to 3.4.2 so my occasional use of the 3G for checking email when away from the internet is already possible even without the DXG. I really like to read with my DXG now so I am not too unhappy without the TLS for my DXG. I enjoy learning and want my DXG to work as good as possible so I will follow this thread.