What libraries does the 32-bit compatibility sfs contain?

[socr8es]

Hi,
I have been using Fossapup for some time now. And, I love it. I was thinking of moving to Jammy since Woof-CE does support it. But, I need the 32-bit compatibility sfs for Jammy. I believe fossa's sfs might work out, but, I was just wondering if there's a list of libraries that need to be included in the 32-bit sfs for it to work properly. A preliminary look into the file for fossa says that it has libc6 files. I'd love to know if there's an official list or something of the files that the 32-bit compatibility sfs contains.

[mikeslr]

I don't know of any 'official list'. Hoping to find one in the /root/packages or /var/packages I mounted 32bit_compatibility_fossa64,sfs. But it doesn't have either folder. Worst case scenario, do the same and make a note of all files in /lib and /usr/lib.

You might be able to get by using fossapup's. That's what Duprate did when with Voidpup and I can confirm that it worked in early Voidpups but not later ones. See the post here, viewtopic.php?p=60293&sid=e14ef09510118 ... 5f1#p60293 and the several posts immediately before it. But take particular note of the possible need to move libraries out of /lib. IIRC, 'user-merge' was implemented in Ubuntu Jammy: applications by users can not use top-level folders. But also note, if you have to move libraries, /root/my-applications/lib --unique to puppys-- can also be used.

The reason why 32-bit compatibility SFS may not have to be 'distro-specific' is that it provides almost an entire operating system, running independently, only called from and later using the web-applications of the 64-bit system.

Still, VanillaDpup may be a better candidate for your project than Jammypup. Ubuntu jammy had entirely dropped 32-bit while debian has not and dimkr has published both 64-bit and 32-bit VanillaDpups. If you have to use 32-bit libraries newer than fossa's, you'll have to use debian's.

But why this project? What 32-bit applications do you want/need to run?

There's an alternative you might consider: run a 32-bit operating system in a Chroot. Sorry, I have to go out so can't point to the specific post where discussed dissembling a Chroot published by MikeWalsh then using the base/core sfs of any puppy, remastered to include wine, as the cont folder in a Chroot.sfs. You may be able to locate it using https://rockedge.org/psearch/ and some combination of the search terms mikeslr, chroot, wine.

[socr8es]

You just covered all my doubts, even the ones I didn't know I had in that single reply, my man! Thanks a lot for that. I will go through them one by one.

I am looking for 32-bit support to run some old games using Wine and Steam.

[mikeslr]

Glad I could help. Needless to say, "I'm back". Here's the post about creating a Chroot I mentioned. viewtopic.php?p=33971#p33971.

Short version: (1) Select a 32-bit Puppy --your choice-- boot into it and install any applications you want. I don't know steam. But to run games you would install one of version2013's pets, https://www.forum.puppylinux.com/viewtopic.php?t=103 and every game you will want to run*.
(2) Remaster that Puppy. I recommend one of the Remaster tools in nicOS-Utility-Suite. https://www.forum.puppylinux.com/viewto ... 983#p12983. I think you can use the 'Alternate' rather than the 'Classic'. It's faster and requires no user input.
(3) After remastering Right-Click/mount the puppy_VERSION_NUMBER.sfs --e.g. xenialpup7.5.sfs and copy all its files into a top level directory named cont. The post explains what goes into the /usr folder. Then package it as an SFS.

* IIRC, staam is used with on-line games. You'll need to include a web-browser in the ChrootOS as Chrooted applications can't access application in the 'MainOS'.

I'm not all that familiar with recent 32-bit Puppys. Xenialpup 32 bit was a solid OS. But using newer web-browsers under it may be a problem. VanillaDpup 32 bit may be a good choice as, IIRC, debian is still offering current 32-bit web-browsers. If it doesn't matter, you could use a seamonkey. Unpacking the tar.gz from mozilla produces a portable. All it needs is a menu entry. How to is explained in the Chroot post. I think there are recent 32-bit versions of Slimjet and vivaldi. It might be possible to use any 32-bit Windows Web-browser. They will run. But I'm not sure how to designate them as the browser to be used by Chrooted programs.

After thought: Maybe the easiest way to get from where you are to where you want to be is the proton Appimage, https://github.com/ferion11/Proton_Appimage or ProtonUp-QT, https://davidotek.github.io/protonup-qt/. Don't know anything about them, and particularly not which Puppys they will work with OOTB.

[socr8es]

Thank you again! This was extremely helpful. Your post yesterday really got me interested in Vanilla DPup. I am gonna try that too.

[dimkr]

If you want the 32-bit compatibility SFS because you want Steam or Wine, in Vanilla Dpup you can just dpkg --add-architecture i386 && apt update, then apt install steam or apt install wine wine32. If you want, you can do this after booting pfix=ram, create a SFS from /usr/lib, then boot without pfix=ram and load this SFS.

[mikeslr]

Thanks, dimkr. I'll have to return to exploring VanillaDpups so that their characteristics are in recent memory. One of which, I recall, is being much closer to how debian, itself, functions than other Puppys. But if memory serves (always a big if) nicOS-Utility-Suite did function under the VanillaDup 9 series: having booted pfix=ram and installed the libraries Save2SFS could quickly create an adrv.sfs or ydrv.sfs of the changes. I haven't explored the VanillaDpup 10 series at all.

If not, /var/packages will provide an catalog of what's been installed. Indeed, again if I recall correctly, /var may hold duplicates of the files which have been installed until you reboot [or until deleted if you didn't boot pfix=ram).

PaDS is an application which can decompress any number debs (and other formatted packages) and combine their contents re-assembled into their proper locations creating an SFS. The duplicates in /var could be used as sources. But, again if memory serves, PaDS didn't function under VanillaDpup. [I find the logic of PaDS script hard to follow. So have marked modification as 'above my pay grade'. Be interested to know if my memory is wrong.

But if Save2SFS is usable, having created an adrv or ydrv, it's a simple matter to rename it if you don't want to to auto-load at bootup.