(OLD) (ARCHIVED) Puppy Linux Discussion Forum

[gyro]

[gyro]

I have updated the first post to include current usage information.
gyro

[peebee]

[gyro]

[peebee]

Hi @gyro

Have you had any thoughts on how an experimental woof-ce build might be done to include overlayfs?

Presumably the overlay-mods.sfs would be converted to a .pet and included in the DISTRO_PKG_SPECS ??

and then overlay-setup-frugal would need to be run via
EXTRA_COMMANDS
in
_00build.conf ??

?? or not??

Cheers
peebee

[gyro]

@peebee,

All my current methods for producing an "overlay_init" Puppy work outside woof-ce.
"overlay-setup_frugal" converts a normal frugal install to an "overlay_init" frugal install.
"overlay-make-iso" converts a normal iso to an "overlay_init" iso. Unfortunatley this requires the "overlay" module to be loaded, as it merges directories by creating an "overlayfs" stack.

One method of integrating "overlay_init" into woof-ce is to actually include it all into a normal Puppy, with the alternative init being activated by a boot parameter at run time.
I'm not convinced that "bloating" a normal Puppy with all the extra files from "overlay_init" is the best way to proceed.

"overlay_init" consists of an alternative initird.gz (smaller), a number of files that replace existing files in Puppy, and quite a few new files with no equivalent in normal Puppy.

My original idea was that woof-ce would be capable of producing an alternative "initrd.gz" just as it can produce different Puppies.
So, similar to a woof-ce user choosing to build a "upupbb" or "slacko" Puppy, they would be able to choose to build an "aufs" or an "overlay" initrd.gz.

gyro

[gyro]

I have uploaded a delta for upupbb-18.05+8.iso http://www.fishprogs.software/puppy/initrd/upupbb-18.05+8.iso___upupbb_overlay0.9d-18.05+8.iso.delta.

This is just a maintenance release for a newer upupbb, and to fix a couple of minor bugs.

gyro

[watchdog]

[gyro]

[rockedge]

I have set up a Puppy Linux Bionic18.05+8 using the OverlayFs and the instructions from this thread.

[Wyk72]

After a whole afternoon studying this (and other) threads on the subject, I managed to assemble (i.e. hack) a working upupbb 18.05+8 on an USB stick formatted with BTRFS.

- I used the info provided in this thread to install upupBB 18.05+8 with overlayFS on a (ext4 formatted) USB stick.

- I compiled the latest stable kernel (4.17.10) with the stemsee script (nubuild.sh) provided in this thread:

http://www.murga-linux.com/puppy/viewtopic.php?t=96723

- I used the change-kernel script provided here by gyro, to install the 4.17.10 vmlinuz/ zdrv sfs (modules)

- I formatted a new USB stick with BTRFS using gparted. Set the "boot" flag.

- booted from another system, copied the whole content of the previous USB stick to the BTRFS formatted one

- Downloaded extlinux from PPM, installed it onto the BTRFS formatted USB stick (mbr too)

- Edited the extlinux.conf with proper UUID values, i.e.:

Default puppy
display boot.msg
prompt 1
timeout 50

F1 boot.msg
F2 help.msg
F3 help2.msg

label puppy
kernel vmlinuz
append initrd=initrd.gz uuid=799f112b-800a-4291-b03f-74e999ab75eb pupsfs=799f112b-800a-4291-b03f-74e999ab75eb

- modified the upupbbBOOTspecs file in the root (/) directory of the BTRFS stick with the correct UUID

And that was it

I am testing it now, it looks fine for the most part. I am looking for a way to enable ZSTD file compression, it must be the initial "Mount" command in the init script by gyro.

[rockedge]

[gyro]

@rockedge,
Thanks for testing, good to see it works for you.

I'm just about to upgrade my overlay_init upupbb to upupbb-18.05+10.
I usually do this by simply replacing adrv, fdrv, puppy and ydrv sfs files with those from peebee's new iso.
(Replacing the zdrv just results in "rc.update" doing a whole lot of unnecessary stuff.)

Later: Upgrade to upupbb-18.05+10 worked fine.

gyro

[gyro]

[gyro]

I like to place unique labels on my partitions, so my grub4dos entry for overlay_init upupbb is: