|
Post by rustleg on Feb 2, 2012 14:18:13 GMT -5
I tried to back up settings but they were not there on the next boot. I understood from the initial announcement that they would automatically be read in at the next boot but it seems this did not happen. For example The settings for Firefox and Chromium were not retained.
The backup is in a file KNOS_PREFS64.tar.gz in the root of my partition "TestKNOS-SSD" which is a FAT32 partition on my SSD. It has a lot of dot folders in it which seems to mean it recorded ok but whatever is supposed to reinstate these didn't work.
(Kevin - you already have a diags of mine but I'd have to give you another one if you need it as when I tried this the first time the KNOS_PREFS64.tar.gz had zero length - presumably due to me hitting the reset button to restart which then didn't flush the buffers!)
|
|
|
Post by Kevin McAleavey on Feb 3, 2012 2:13:56 GMT -5
I tried to back up settings but they were not there on the next boot. I understood from the initial announcement that they would automatically be read in at the next boot but it seems this did not happen. For example The settings for Firefox and Chromium were not retained. The backup is in a file KNOS_PREFS64.tar.gz in the root of my partition "TestKNOS-SSD" which is a FAT32 partition on my SSD. It has a lot of dot folders in it which seems to mean it recorded ok but whatever is supposed to reinstate these didn't work. (Kevin - you already have a diags of mine but I'd have to give you another one if you need it as when I tried this the first time the KNOS_PREFS64.tar.gz had zero length - presumably due to me hitting the reset button to restart which then didn't flush the buffers!) My fault there for not being specific enough when there's a bunch of drives available as in your case there. We limit the number of places we look for it at bootup time because having to attempt to mount every possible location and then search for the presence or absence of the backup file would seriously slow down bootup time, especially on a DVD boot. So currently, what KNOS will look for is one of only three possible locations at thjs time. So the backup would have to be on one of these three possible locations: 1. A separate USB "data stick" as is commonly used with KNOS when booted from DVD 2. The KNOS personal storage space on a USB bootable stick of 8GB or larger 3. The KNOS personal storage space on a KNOS-formatted hard disk There is also a priority order to it, in order to allow a choice of which backup actually gets loaded. KNOS looks first to the hard disk (3) and then to the Boot USB stick (2) next on the basis of you wouldn't have booted from the stick if you had a hard disk with KNOS on it already, so it will load that one if the hard disk exists and finally, if you plug in a "data" stick with either of the previous conditions, then you really want to read what's on that data stick instead of what was on the booted drive. Seemed logical to me at the time ... Those were the only three locations we anticipated, and they're hard-coded to avoid having to mount, test and unmount any possible locations. An error if they're not there speedily sends our checker on to the next location if it isn't there or boot continues. The existing disk structures that appear in KNOS' desktop do not exist during the boot cycle, all part of our security design to keep the kernel; and boot space thoroughly isolated from the KNOS desktop and its jailed "userland" ... sorry about that ... I wasn't expecting it to get tossed where you put the backup. Will see about planning for that on the next build so long as it doesn't affect bootup time or security OR I'll explain that better at release time.
|
|
|
Post by rustleg on Feb 3, 2012 6:40:07 GMT -5
Your methodology looks sound to me so only an explanation needed as far as I am concerned.
|
|
|
Post by Kevin McAleavey on Feb 4, 2012 2:14:07 GMT -5
Your methodology looks sound to me so only an explanation needed as far as I am concerned. If your "personal space" turns out to be where I said it should be in the other thread, save that backup to that location and bliss should ensue at no extra charge.
|
|