@fandog:
https://ubuntuforums.org/archive/index. ... 45536.html
This would be too dangerous to be automated. The risk of things going wrong and make the situation worse is just too high. If you do this thing, you'd better be aware of the risk involved.
@stemsee:
I also discovered that the init scripts and boot process has changed significantly (system-init) > (busybox-init (binary)).
Not really. That way of booting has always been the case since Fatdog 600.
. . making it difficult to boot the main.sfs with any other initrd/init script.
Of course. You can't just replace Fatdog's initrd with any random init/initrd script and expect things to work. They both work together. If you want to replace it, the replacement init/initrd need to be compatible. It's not too difficult. In fact, with some loss of functionality, the basesfs can be booted with no initrd at all. See
here.
Also there are significant changes in the use of permissions or ACLs on root directories, it seems.
Main permission change is on /root, as noted in the release notes. Anything else (ACL, etc) are probably just showing because in 720 the utilities are built with support for ACL and extended attributes; but they aren't being used.
Previous 710 would break with the latest upgrades using gslapt.
Unfortunately yes, because we can't afford the effort to maintain two separate repositories for 710 and 720. Anyway, we always state that we can only support the latest version of Fatdog. As soon as a new release is announced, support for the previous versions cease (it's up to the community to maintain those older versions, if they wish).
720 is working great now, and I wonder if all the technical changes are listed somewhere?
Release Notes.
@dr. Dan:
How small can a Fatdog64 installation partition be and still function? Either with save folder there or elsewhere?
What is ideal as a minimum?
Kirk alreay answered that. But I will elaborate a little bit.
"Installation partition" is a very vague word in Fatdog.
If you use the default install, you need a minimum space of vmlinuz + initrd (plus any savefile/savefolder you need), as Kirk said.
But with Fatdog you've got options to suit your needs.
You can have vmlinuz in one partition, and initrd in another.
You can extract basesfs (fd64.sfs) from initrd and put it elsewhere, while the "shrunk" initrd + vmlinuz is in one partition.
You can extract basesfs, kernel-modules.sfs, and put these in separate or same partition; and have "nano-ed" initrd + vmlinuz in one partition.
None of the "advanced" installation is automated/scripted/GUI-ed, you need to do it yourself, depending on what you're doing.
Of course, to all the above, you need to add the size of the bootloader if you don't have one already. It's about 3MB for grub4dos, and 10MB for UEFI.
@vanchutr: Thanks for testing.
For the record, "pdrv=f737daea-5272-4175-9c6e-3ebbd50065e0 psubdir=fatdog720 pmedia=atahd pfix=fsck" are all not supported by Fatdog, so you're running it as if you don't pass in any extra parameter at all.
The first 3 parameters are replaced by "savefile" and "basesfs" parameter; and the last one is replaced by "dofsck".
@snayak: There is already setuptools and pip in the repo. It's a bit old, version 12, but do you need the latest version?
If you really need to use the latest version, look at our build recipes below to see how we built the earlier versions:
http://distro.ibiblio.org/fatdog/source ... h-1.tar.gz
and
http://distro.ibiblio.org/fatdog/source ... h-1.tar.gz
As for multiarch_wrapper, it's meant so that some programs who aren't multi-lib aware, can run in a multi-lib environment. In other words, it allows 32-bit python and 64-bit python to co-exist, for example. You can read the details here:
http://www.clfs.org/view/CLFS-3.0.0-SYS ... apper.html.
EDIT: I saw step's reply when I was typing this. Thanks step
![Smile :)](./images/smilies/icon_smile.gif)