PorteuX 1.5 has been released

Post#1 by **porteux** » 28 Jul 2024, 16:04

1. Fixed `chkufsd` wrong path (it's accessible via `fsck` cheatcode or `check-filesystem` script)
2. Fixed an issue where some vulkan applications could fail (e.g. geekbeck6 --compute Vulkan)
3. Fixed an issue where `changes-ro` cheatcode was not working properly (thanks to Otto for reporting)
4. Fixed a rare issue where super fast boot could lead to a blank screen
5. Fixed `.m4a` file extension not opening in `audacious` in Cinnamon
6. Fixed missing icon in logout screen in `openbox`
7. Fixed missing `XPDF` icon in LXQt
8. Added `nghttp3` in current (new NetworkManager dependency)
9. Added fast whiteout copy when using saved session (missing from last release)
10. Improved LXQt stripping
11. Updated kernel to 6.10.2 (~150 MB of RAM lighter \o/)
12. Updated Nvidia driver to 555.58.02
13. Updated Cinnamon to 6.2.7 (current)
14. Updated GNOME to 46.3.1 (current)
15. Updated many packages in both stable and current according to Slackware updates

Downloads available at: https://github.com/porteux/porteux/releases/latest

Post#2 by **Ed_P** » 28 Jul 2024, 18:39

Cinnamon current boots and can access the web.

Post#3 by **cmbarreto** » 29 Jul 2024, 02:10

I'm sorry if this isn't the right place to ask. But I was testing Porteux 1.5 and it seems strange to me that every so often, a few minutes, it asks the router for a new dhcp lease. And obtaining it as a user does not cause me problems.

Post#4 by **beny** » 29 Jul 2024, 18:07

hi porteux, well good job as usual,i have done a try and plasma6 work like a charm on porteus 1.5 without a lot of changes to the core,well we have to wait the load of the changes but very good system ps:current

Post#5 by **porteux** » 29 Jul 2024, 21:20

@cmbarreto, are you using stable or current? Can you replicate this in Always Fresh?

@beny, yes, I made a KDE 6.1 testing module a few weeks ago and it works OK, but it's not Slackware official, so I going to wait for them -- btw, why is it taking so long?

Post#6 by **Otto** » 30 Jul 2024, 01:48

Thanks Porteux,
No more issue with `changes-ro` cheatcode.
FF latest version download over app store was ok, but
"Error creating module" for brave browser.

Post#7 by **porteux** » 30 Jul 2024, 10:28

@Otto, it seems they forgot to add the RPM in their release. Even using the official RPM link doesn't work for the latest release: https://brave-browser-rpm-release.s3.br ... x86_64.rpm, although this one works: https://brave-browser-rpm-release.s3.br ... x86_64.rpm

I'm afraid there isn't much we can do unless wait for them to fix that

Post#8 by **vinnie** » 30 Jul 2024, 15:32

I was curious to try it but it seems that the installer for linux does not support partitions formatted in ext4:

Code: Select all

[porteus boot]# ./porteux-installer-for-linux.run 
Creating directory /tmp/porteux-installer
Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing PorteuX Installer  100%  
egrep: warning: egrep is obsolescent; using grep -E
Partition filesystem not supported

Post#9 by **beny** » 30 Jul 2024, 16:04

hi, no problem with ext4 installer on my side,on sandisk key,you can mount the device on a linux directory cd on boot directory and start the installer from here,take a look at device name when the script start: sh Porteus-installer-for-Linux.com

Post#10 by **vinnie** » 30 Jul 2024, 16:22

I honestly believe that's exactly the procedure I did, to which you can see the error in my previous message.
In fact I then repeated the procedure on the same disk (an external sd) but formatted in fat32 and now I am writing to you from porteux.

Post#11 by **porteux** » 30 Jul 2024, 16:28

@vinnie, here's the output I have when trying to install PorteuX in a ext4 partition (no FAT32):

Code: Select all

# ./porteux-installer-for-linux.run 
Creating directory /tmp/porteux-installer
Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing PorteuX Installer  100%  

PorteuX is going to be installed in /dev/sda1

Press Enter to continue

Flushing filesystem buffers...
Installing extlinux bootloader...
Updating initrd with Porteux partition unique ID...
11332 blocks
11333 blocks
Setting permissions...

Installation finished successfully

You may reboot your system now and start using PorteuX.
Don't forget to set your BIOS to boot from this storage media.

I don't see any 'egrep' warning, and the partition is definitely supported.

Anyway, I'm glad you found a way

Post#12 by **vinnie** » 30 Jul 2024, 16:54

I think the egrep error depends on the system from which you are installing porteux (so in my case it must have been a nemesis warning).
However I seem to remember that when I ran the same command on the fat32 partitioned disk the egrep error didn't reappear, so I'm not so sure what I'm saying.

Otherwise, porteux is very, very fast.
30 seconds to boot from the syslinux menu, 45 if all in ram.
And all are very responsive.
The only thing slackware repos are not very well stocked, for example I couldn't find firejail (if I remember correctly though I had had the same problem in porteus and had used salix repos).

I use firejail to sandbox start some appimages, and it's convenient because then the configurations also stay saved in the same directory as the program, so I can use the same programs on all distros (interchangeable porteus-nemesis-porteux).

Post#13 by **porteux** » 30 Jul 2024, 17:09

@vinnie, 30 seconds to boot is too slow. Is it installed in an old USB2 stick? I can boot in less than 10 seconds on a Sandisk Ultra Luxe USB stick. Also, I recommend either installing it in a proper SSD/nvme partition or at least switching to 'changes=EXIT:' so it will only write into the storage unit during reboot/shutdown, speeding up the system A LOT. I'm actually thinking about setting this as the default option for the next release.

Indeed I couldn't find firejail in Slackware repo, but it's available for you to build using SlackBuild: https://slackbuilds.org/repository/15.0 ... /firejail/

Post#14 by **beny** » 30 Jul 2024, 17:33

hi porteux i have rebuild the kernel stock on porteux1.5 because i don't like the old gcc builder so i have rebuild the kernel with your config,the enigma why the vmlinux is smallest if i have the same configure of yours 8.5 against 9.8,btw is just for fun i have added only the whole cgroup command....

Post#15 by **porteux** » 30 Jul 2024, 17:42

@beny, how exactly are you building the kernel? Any script/tool? PorteuX compiles the kernel using aggressive GCC flags to optimize performance, and because of that vmlinuz binary is a bit larger.