Porteus-v5.0 is released!

[peebee]

Porteus-v5.0 is released!
Post#1 by ncmprhnsbl » 03 Jul 2022, 22:05

Team Porteus is finally able to announce the immediate availability of Porteus-v5.0 final in EIGHT desktop flavours.
You can download the releases at any of our mirrors: http://porteus.org/porteus-mirrors.html in the following folders:

x86_64/Porteus-v5.0
i586/Porteus-v5.0

Main changes include:
Kernel 5.18.8
Core is based on Slackware 15.0
8 desktop options to choose from! (7 for i586)

[wiak]

Nice to hear of new release.

At least maybe beat them to the boot from nvme issue fix/solution

Porteus changes extract:

The syslinux bootloader creator(Porteus-installer-for-Linux.com) should now handle NMVe installations
BusyBox in initrd updated to 1.35

KLV-Airedale thread re: WeeDog initrd:

08 April 2022
SUCCESS.

Posting from weedogit Zorin frugal install (put onto my HP nvme drive partition) now.

As well as modprobing nvme in the WDL initrd/init the main problem was indeed (per my immediately above post) the busybox uclibc static version being used. I changed to this one:

https://www.busybox.net/downloads/binar ... sl/busybox (busybox 1.35)

and boots fine to the nvme drive now.

If Puppy has similar issues (or any Dog) then I expect that busybox needs changed (or compiled) similarly.
I'll modify WDL initrd soonish such that KLV-Airedale will boot from nvme with appropriate nvme-enabled kernel (and weedogit distros with appropriate nvme modprobes).

[fredx181]

.... If Puppy has similar issues (or any Dog) then I expect that busybox needs changed (or compiled) similarly. ...

Strangely, with the busybox v1.31 included in the initrd1.xz from DebianDog (EDIT: since Bullseye) (porteus-boot mod for many years already) booting from nvme drive partition works fine.

[esos]

FYI
changes-ro parameter is very nice feature to stop any unnecessary changes.
This is useful when you have your system set up exactly how you like it and do not want to save any other changes you might make during a live
session.

[wiak]

.... If Puppy has similar issues (or any Dog) then I expect that busybox needs changed (or compiled) similarly. ...

Strangely, with the busybox v1.31 included in the initrd1.xz from DebianDog (porteus-boot mod for many years already) booting from nvme drive partition works fine.

That surprises me. Definitely needed 1.35 in klv, and made sense. Wonder why the difference. Life full of mysteries at Puppy linux forum!

[fredx181]

.... If Puppy has similar issues (or any Dog) then I expect that busybox needs changed (or compiled) similarly. ...

Strangely, with the busybox v1.31 included in the initrd1.xz from DebianDog (porteus-boot mod for many years already) booting from nvme drive partition works fine.

That surprises me. Definitely needed 1.35 in klv, and made sense. Wonder why the difference. Life full of mysteries at Puppy linux forum!

For clarity: Same for me on KLV, earlier version than 1.35 didn't work on nvme drive. Apparently some change in 1.35 that works for KLV but somehow not required for Debiandog(Bullseye)., it has special busybox build, v1.31 taken from porteus.

[ozsouth]

@wiak @peebee - thanks for link to busybox 1.35, wiak. I previously tried to compile v1.35 from source in ScPup64-20.06, with several field-length errors. Not sure how critical those are. I used bbconfig to provide compiling config.
Tried the busybox binary provided in 2nd post & found these functions missing:
bbconfig ; guess_fstype ; minips ; vercmp . These are symlinks to busybox in /bin in ScPup64_20.06. Not sure if vital. The 1.35 busybox version may have other features which should be symlinks in /bin, but I haven't checked/am not sure how to. Advice most welcome.

[wiak]

Tried the busybox binary provided in 2nd post & found these functions missing:
bbconfig ; guess_fstype ; minips ; vercmp . These are symlinks to busybox in /bin in ScPup64_20.06. Not sure if vital. The 1.35 busybox version may have other features which should be symlinks in /bin, but I haven't checked/am not sure how to. Advice most welcome.

Not sure what your are meaning oz - I expect you mean you want to know what symlinks are necessary for that Pup you use - I wouldn't know.

When my script builds first stage of KLV-Airedale for rockedge, I have a bit of code making symlinks for the particular busybox used:

Code: Select all

	# Make the command applet symlinks for busybox
	for i in `bin/busybox --list-full`; do ln -s /bin/busybox ${i}; done

There are other more basic ways of doing similar that I've used before, but can't remember now.

[ozsouth]

@wiak - thanks for that script. That sets up what v1.35 DOES have, & for the missing functions, I made a script (ps-FULL -u) as minips & grabbed the guess_fstype & vercmp binaries from Slacko64-6.9.9.9 - 5 years old but they work.

[williams2]

To create symlinks to /bin/busybox in /tmp/bb/

Code: Select all

mkdir /tmp/bb
busybox --install -s /tmp/bb/

If a file is already there, for example, the full version of wget,
a symlink is not created that would over write the full version.

[wiak]

To create symlinks to /bin/busybox in /tmp/bb/

Code: Select all

mkdir /tmp/bb
busybox --install -s /tmp/bb/

If a file is already there, for example, the full version of wget,
a symlink is not created that would over write the full version.

Ah yes, that's the other mechanism I tried at one time too; can't remember why I didn't stick with it