PorteuX 0.5 has been released

[Ed_P]

@Ed_P, could give us more details on what exactly didn't work for you and how to replicate?

I don't rermember the original problems at this point. This config seems to be working:

Code: Select all

~#  uname -a
Linux porteux.example.net 6.2.16-porteux #1 SMP PREEMPT_DYNAMIC Mon Jun 26 23:24:16 NZST 2023 x86_64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz GenuineIntel GNU/Linux

~#  cat /etc/porteux/*
001-core.xzm:20230710
002-xorg.xzm:20230710
002-xtra.xzm:20230710
initrd.zst:20230426

~#  ls -l /mnt/live/memory/images
000-kernel-6.2.16.xzm : Jun 26 11:43
001-core-current-20230710.xzm : Jul 9 23:22
002-xorg-current-20230710.xzm : Jul 9 23:32
002-xtra-current-20230710.xzm : Feb 3 09:59
003-cinnamon-5.8.0-current-20230630.xzm : Jul 1 21:16
firefox-latest-111.0.1-x86_64-1.xzm : Mar 23 01:01

~#  cat /proc/cmdline
quiet BOOT_IMAGE=(loop)/boot/syslinux/vmlinuz from=/ISOs/PorteuX/porteux-v0.5-xfce-4.18-current-x86_64.iso volume=33 reboot=cold extramod=/porteux0.5/Modules kmap=us noload=mate;lxqt;xfce;-test norootcopy

ISO: /ISOs/PorteuX/porteux-v0.5-xfce-4.18-current-x86_64.iso

I would recommend you change your Cinnamon's Task Bar to be at the bottom of the screen. Easier for Windows users and Porteus user to adapt to.

[Jack]

If anyone can get WiFi to work please let me know and how you did it.

[Rava]

Is Porteux running with older Porteus kernels?

For now I do not get it to run with my 5.4.30-porteus - the newest kernel I could compile the needed NV driver nvidia-340.108-k.5.4.30-porteus-v5.0-x86_64_rava.xzm for.

[Ed_P]

Is Porteux running with older Porteus kernels?

21. reverted Nvidia driver to 525.85.05 because newer versions are causing random artifacts
22. reverted kernel to 6.2.16 until we find a solution for the reboot/shutdown issue

Added in 1 hour 57 minutes :

If anyone can get WiFi to work please let me know and how you did it.

Hello Jack

On the Task Bar, on the right hand side, find the icon that says no network connection, click on it, it will show networks in your area, select one, enter it's password. You should be connected.

[Rava]

Is Porteux running with older Porteus kernels?

21. reverted Nvidia driver to 525.85.05 because newer versions are causing random artifacts
22. reverted kernel to 6.2.16 until we find a solution for the reboot/shutdown issue

I am quite sure 525 is not working for me, I need 340.*

[Jack]

Hello Jack

On the Task Bar, on the right hand side, find the icon that says no network connection, click on it, it will show networks in your area, select one, enter it's password. You should be connected.

Hi Ed_P,

Thank you very much now I have 3 to use and they are Porteus, Nemesis and now Porteux. I was about ready to give up.

Now I need to add program that I like to use. One is themes there not many to pick from.

Again Thanks
Jack

[Karmi]

@Ed_P, could give us more details on what exactly didn't work for you and how to replicate?

I would recommend you change your Cinnamon's Task Bar to be at the bottom of the screen. Easier for Windows users and Porteus user to adapt to.

Yeah, took me awhile to figure that one out. Was finally able to drag 'n drop it to the bottom, but can't remember how now. I'll try it again after another update is out...

[Ed_P]

Was finally able to drag 'n drop it to the bottom, but can't remember how now.

Not that hard actually, I've never done it so it was a nice learning experience. Move mouse to the task bar and right click, then click on Move, move pointer to the bottom and click on it.

Added in 2 hours 55 minutes 20 seconds:
Anyone know where Cinnamon stores it's Task Bar setting? Would be good to save it when rebooting. I don't see an updated file in the /mnt/live/memory/changes/home/guest/.cinnamon/configs folder.

[porteux]

@Ed_P, all settings in Cinnamon are stored in ~/.config/dconf/user

[Ed_P]

@Ed_P, all settings in Cinnamon are stored in ~/.config/dconf/user

Thanks porteux.

In Porteus 5.0 a script I made to make a module of this works:

Code: Select all

cp -a -p --parents /home/guest/.config/dconf/*    /tmp/mod/

dir2xzm /tmp/mod /tmp/mycinnamon.xzm

In PorteuX0.5 I get this:

Code: Select all

cp: preserving permissions for ‘/tmp/mod/home/guest/.config/dconf’: No such file or directory

guest@porteux:/mnt/nvme0n1p7/porteux0.5/Guest$ su
Password: 
root@porteux:/mnt/nvme0n1p7/porteux0.5/Guest# ls -on /tmp/mod/home/guest/.config/dconf
total 8
-rw-r--r-- 1 1000 5457 Jul 15 14:38 user
root@porteux:/mnt/nvme0n1p7/porteux0.5/Guest# 

As you can see the user file definitely exists. The script runs as root.

Added in 1 day 55 minutes 28 seconds:
Plus the mod that dir2xzm creates is named mod.xzm not mycinnamon.xzm and booting with it requires me to login, which fails whether I use guest or root.

Added in 1 day 17 hours 37 minutes 30 seconds:
Anyone got a download link for the 05-devel.xzm module? I've just spent 30 mins in Windows clicking on every GitHub link referencing it and still no download.

Added in 9 minutes 35 seconds:
Interesting. With XFCE and Firefox I found it: https://github.com/porteux/porteux/rele ... 230710.xzm

[porteux]

@Ed_P, to download devel you can use the app store.

To make a module using dir2xzm please read the documentation (i.e. help): dir2xzm /mnt/sda2/directory1/ -o=/home/guest/Desktop/module.xzm

[Ed_P]

to download devel you can use the app store.

An interesting option, if I'm in PorteuX. Or are you implying the Porteus 5.0 version works with PorteuX?

To make a module using dir2xzm please read the documentation (i.e. help): dir2xzm /mnt/sda2/directory1/ -o=/home/guest/Desktop/module.xzm

That's very interesting porteux. I've been using the dir2xzm command for years with just:

Code: Select all

dir2xzm  /tmp/mod /tmp/$MOD.xzm   &&   rm -rf /tmp/mod

and it's worked. The Porteus versions have all defaulted to the correct option for the 2nd operand. Apparently the PorteuX version doesn't. I wonder how many other Porteus tools work differently in PorteuX.

BTW The Cinnamon DEs in some other releases I've tried have the taskbar on the bottom, just like the Porteus ones.

[beny]

hi, or can use the sudo mksquashfs name of directory, name of the .xzm like this

Code: Select all

  guest@porteus:~$ sudo mksquashfs /home/guest/libnsl /home/guest/libnsl-2.0.0-x86_64-1.xzm
Password: 
Found a valid exportable SQUASHFS superblock on /home/guest/libnsl-2.0.0-x86_64-1.xzm.
	Compression used xz
	Inodes are compressed
	Data is compressed
	Fragments are compressed
	Xattrs are compressed
	Fragments are present in the filesystem
	Always-use-fragments option is not specified
	Duplicates are removed
	Xattrs are stored
	Filesystem size 26.38 Kbytes (0.03 Mbytes)
	Block size 262144
	Number of fragments 1
	Number of inodes 43
	Number of ids 1

Parallel mksquashfs: Using 6 processors
Scanning existing filesystem...
Read existing filesystem, 42 inodes scanned
Appending to existing 4.0 filesystem on /home/guest/libnsl-2.0.0-x86_64-1.xzm, block size 262144
All -b, -noI, -noD, -noF, -noX, -noId, -no-duplicates, -no-fragments,
-always-use-fragments, -exportable and -comp options ignored

If appending is not wanted, please re-run with -noappend specified!

Recovery file "/root/squashfs_recovery_libnsl-2.0.0-x86_64-1.xzm_6792" written
If Mksquashfs aborts abnormally (i.e. power failure), run
mksquashfs - /home/guest/libnsl-2.0.0-x86_64-1.xzm -recover /root/squashfs_recovery_libnsl-2.0.0-x86_64-1.xzm_6792
to restore filesystem

Source directory entry usr already used! - trying usr_1
Source directory entry lib64 already used! - trying lib64_1
[=================================================================|] 14/14 100%

Exportable Squashfs 4.0 filesystem, xz compressed, data block size 262144
	compressed data, compressed metadata, compressed fragments,
	compressed xattrs, compressed ids
	duplicates are removed
Filesystem size 27.23 Kbytes (0.03 Mbytes)
	13.63% of uncompressed filesystem size (199.79 Kbytes)
Inode table size 618 bytes (0.60 Kbytes)
	27.71% of uncompressed inode table size (2230 bytes)
Directory table size 650 bytes (0.63 Kbytes)
	47.45% of uncompressed directory table size (1370 bytes)
Number of duplicate files found 15
Number of inodes 67
Number of files 30
Number of fragments 2
Number of symbolic links 7
Number of device nodes 0
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 30
Number of ids (unique uids + gids) 3
Number of uids 2
	root (0)
	guest (1000)
Number of gids 2
	root (0)
	users (100)
guest@porteus:~$ 

                                               

[Ed_P]

Thanks beny. So many options to replace Porteus's dir2xzm command. But I like Portues 5.0's version.

Code: Select all

guest@porteus:~$ dir2xzm -h

Convert directory tree into a zstd or xz compressed module
usage: /usr/bin/dir2xzm <-option> source_directory output_file.xzm
 options:  -x : use xz compression. 
 options:  -z : use zstd compression. 
 if no option is given xz is used. 
           -h       : show this usage. 

guest@porteus:~$ 

who's Help display shows how to use the code. Note, no "-o=" code required.

So, how many other Portues 5.0 apps/cmds/aides have gotten changed in PorteuX??

Added in 1 hour 15 minutes 11 seconds:
Apparently the xzm2dir command is different in PorteuX also.

Code: Select all

xzm2dir /mnt/nvme0n1p7/porteux0.5/Modules/003-*   /tmp/mod

Code: Select all

guest@porteux:/mnt/nvme0n1p7/porteux0.5/Guest$ ./mkmod*.sh
Enter root's password
Password: 

Parallel unsquashfs: Using 8 processors
11520 inodes (8355 blocks) to write

[===========================================================|] 19875/19875 100%

created 8238 files
created 708 directories
created 3282 symlinks
created 0 devices
created 0 fifos
created 0 sockets
created 0 hardlinks

ls -on /tmp/mod/home/guest/.config/dconf
ls: cannot access '/tmp/mod/home/guest/.config/dconf': No such file or directory

Yup

Code: Select all

guest@porteux:~$ su
Password: 
root@porteux:/home/guest# xzm2dir -h

Extract xzm modules to directories
usage: /usr/bin/xzm2dir <input> <option> 
 options:  -h : show this help. 
 options:  -o : output directory path
 options:  -q : quiet mode. 

example: /usr/bin/xzm2dir /mnt/sda2/module1.xzm /mnt/sda2/module2.xzm -q
example: /usr/bin/xzm2dir /mnt/sda2/module.xzm -o=/home/guest/Desktop

root@porteux:/home/guest# 

[roadie]

@Ed_P
Most of the scripts dealing with modules in Porteux include the -o= flag, as is easily seen by using the -h flag. I'm confused as to why Porteux would be expected to follow the same format as Porteus. It's to be expected that some things will be different, and they should be.

Personally, I prefer the taskbar of any desktop to be on top, but if it isn't, I just move it. It's easily done with most desktops, even Cinnamon, which I find to be a somewhat not intuitive desktop. This is not a reflection on the Porteux or Porteus devs as they work with what they have.