Re: How to make a remastering tool use space on another partition?
Good thing you mentioned that. Can we update the kernel ourselves? How?
Discussion, talk and tips
https://forum.puppylinux.com/
Good thing you mentioned that. Can we update the kernel ourselves? How?
I've been thinking:
1. I'm used to having a complete copy of my / structure.
2. Updating that copy is very fast because I use rsync. It just updates whatever has changed.
3. It seems to me that quick-remaster copies everything from the current installation.
4. What if it could use a previous remaster as reference to just "update" it, rsync style? Maybe it would be faster.
Luluc wrote: Thu Nov 21, 2024 8:09 pmI've been thinking:
1. I'm used to having a complete copy of my / structure.
2. Updating that copy is very fast because I use rsync. It just updates whatever has changed.
3. It seems to me that quick-remaster copies everything from the current installation.
4. What if it could use a previous remaster as reference to just "update" it, rsync style? Maybe it would be faster.
3) No, it doesnt copy. it mounts , as you may notice that it starts almost immediately with creating the .squashfs.
4) So , not faster.
If it creates a completely new 01-filesystem.squashfs, it has to copy.
Can't it open/mount an existing 01-filesystem.squashfs file then update it with the changes? It's obvious that it doesn't currently do that.
Luluc wrote: Thu Nov 21, 2024 9:49 pmIf it creates a completely new 01-filesystem.squashfs, it has to copy.
Depends how you call it. Creating 01-filesystem.squashfs from a mountpoint, I wouldn't call it copying.
Can't it open/mount an existing 01-filesystem.squashfs file then update it with the changes? It's obvious that it doesn't currently do that.
AFAIK you need to unsquash it first , make changes and then squash again.