keniv wrote: ↑Tue Sep 08, 2020 6:14 pm Hi Fred,
Well I've tried the other Dogs so I thought I'd try this one. However, my record on getting them to work with a save folder rather than save file is abysmal. I only managed to do this once and that was with a lot of help. In keeping with this record I've failed again. Here is the setup I'm using. I have a 40GB 2.5 inch ide HDD which came from an old laptop. It's plugged into an adapter which allows it to be used as a USB drive. It has two partitions. sda1, formatted ntsf at just over 9 GB and sda2, formatted ext3 at about 28GB. I have both buster dog and racy551 on sda1. I did not manage to create a save folder for buster dog, though I did try, so sda2 has nothing on it. Buster dog has a save file on sda1. I did a manual frugal install of fossa dog on sda1. I'm using grub4dos to boot both buster dog and racy so it was relatively easy to boot fossa dog. All I did after booting was to set up the wifi then I shutdown. As part of the shutdown process I was give the option of creating a save file or a save folder. I chose save folder. This is where things start to become confusing. I was asked to choose a folder in which the save folder called "changes" would be placed. I migrated to sda2 and chose "create folder". I named my folder f-dog-sf. I was told that this folder could not be used as it was not on a linux partition even although sda2 is a linux partition. I repeated this but this time did not choose a folder. This time the "changes" folder was accepted and written to sda2 and was used to save the changes. Now we come to the next problem that of the "cheat code" I looked at "Examples-boot-codes.txt". Below is the one I considered most relevant to me.
"Recommended to put the casper folder in a folder with unique name, e.g. Fossa_Dog, then use this:"
I found this a little confusing as the changes folder appears to be called casper when the routine to set up a changes folder only allows the name "changes" as well as the fact that the folder containing vmlinuz, initrd1.xz and the .sfs file is also called casper. Below is the boot code I've used.Code: Select all
title FossaDog in folder Fossa_Dog, save on exit (sda1) root (hd0,0) kernel /Fossa_Dog/casper/vmlinuz noauto from=/Fossa_Dog changes=EXIT:/Fossa_Dog/casper/ initrd /Fossa_Dog/casper/initrd1.xz
I have also tried many variations of this including =EXIT:/mnt/sda2/changes and =EXIT:/changes and others I can't remember. Some times when it fails the report seems to suggest that sda2 cannot be found. I'm now wondering if I am not alone in having problems in finding a "cheat code" that will let me boot using my save folder.Code: Select all
title FossaDog (sda1/7920fossadog) root (hd0,0) kernel /7920fossadog/casper/vmlinuz noauto from=/7920fossadog changes=EXIT:/sda2/changes initrd /7920fossadog/casper/initrd1.xz
Can you suggest how I can get fossa dog to use the save folder that was created using the fossa dog shutdown routine or if not is there a way to make a save folder that can be got to work.
Regards,
Ken.
EDITED to clarify a few things I got sort of wrong or confusing.
I think you have a few slight misconceptions that once cleared up will make this a whole lot easier for you.
The folder that you specify with the changes bootcode, is where the changes folder is. So, if you set it to changes=/sda2/ then it will look for the changes folder /sda2/changes/ and when you choose a location to save changes to when shutting down the first time, select sda2, and it will make the changes folder there. Done.
BUT, /sda2/ is not a location. You could use /dev/sda2/ which should work.
BUT, depending on which drives get detected first, how many drives are connected, etc, what sda is may change. A better way is to label the partition with a name you know is unique, and use changes=LABEL:whateveryourlabelis/ or if you want, use the block ID like changes=UUID:whateveryourblockidis/ which you can get by running blkid in a terminal.
BUT, you want to put it in it's own Fossa_Dog folder. There are a few good reasons for this, as in you can have several DebDog/Puppy installations each in their own folder, and should you ever run into major problems, booting from a USB key won't try to automatically use the files on the hard drive.
So, assuming you go the label route(though you can use UUID the same way,) you will want to copy your casper directory to /mnt/sda2/ do something like:
Code: Select all
title FossaDog in folder Fossa_Dog, save on exit (sda1)
root (hd0,0)
kernel /Fossa_Dog/casper/vmlinuz noauto from=/Fossa_Dog changes=EXIT:LABEL:whateveryourlabelforsda2is/
initrd /Fossa_Dog/casper/initrd1.xzIn other news, two more very minor things I found, searchmonkey's desktop file is pointing to the wrong icon, and move-in-crypt points to an entirely non-existent icon.
Other than that, UEFI method installs as expected on my HP Envy 13 without any problem, posting from it now.
