z-vap Posted May 16, 2014 Share #1 Posted May 16, 2014 So i have successfully installed 4458 with GnoBoot. Loving it. I would like to hold off on updating to 4482 w/ nanoboot, for some time. I want to test for a while before I proceeed. But I cannot seem to update to 4458-1 or 4458-2. When I delete the autoupd@te.info file and have it only check for "important updates" it keeps telling me to go directly to 4482. Grr I figured I could manually create my own autoupd@te.info with the pertinent info, but I have no idea what the contents of that file would be; I see tons of posts about running SED against it but nothing that states what is actually in the file, for these updates. Does anyone know what the contents of the file should be, for updating to 4458-1 and 4458-2? Thanks Link to comment Share on other sites More sharing options...
MarsManden Posted May 17, 2014 Share #2 Posted May 17, 2014 Look at this post and the next few after this. viewtopic.php?f=2&t=6&p=17848#p17815 Link to comment Share on other sites More sharing options...
z-vap Posted May 17, 2014 Author Share #3 Posted May 17, 2014 Those posts assume I have an autoupd@te.info file that contains the word flashupdatedeb. I don't. That is why I am asking for the textual contents of those files, for either update 1 or 2 Link to comment Share on other sites More sharing options...
MarsManden Posted May 17, 2014 Share #4 Posted May 17, 2014 Are you sure the file doesn't appear when you have uploaded the update 2 pat-file as described? Link to comment Share on other sites More sharing options...
z-vap Posted May 17, 2014 Author Share #5 Posted May 17, 2014 OK it eventually did show up about 5 minutes later. I guess the system takes the manual update PAT file that is picked, and extracts the data to where the DSM-Security.json tells it to; i found that file is inside the .pat file. So it must create the autoupd file on demand if the system passes mustard after validating everything against the DSM-Security.json file. I extrtacted the pat file, both small and flash deb files, and started to construct my own autoupd file. When I went back to my SSH I saw that I had another autoupd@te.info file sitting there. I was like "Whu...?" when I looked at the contents, it looked exactly like what I was trying to create. LOL So i ran the SED command and now I am updated to 4458-UPDATE 2 ... just needed patience. Link to comment Share on other sites More sharing options...
MarsManden Posted May 17, 2014 Share #6 Posted May 17, 2014 I think the update procedure builds the autoupd@te.info on the fly. An update from Update level 0 is different from an update from Update level 1. Link to comment Share on other sites More sharing options...
Recommended Posts