Nemesis update- v24.08 (2024-08-28)

Arch based Porteus community project

Moderator: M. Eerie

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 4114
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Nemesis update- v24.08 (2024-08-28)

Post#1 by ncmprhnsbl » 30 Aug 2024, 08:41

Update time again :)
ISOs available here: ISO Downloads :dl-green:
Modules here: Module Downloads :dl-green:
05-devel here: 05-devel Download :dl-green:
Kernel and crippled sources: Kernel Downloads :dl-green:

Changelog:
  • Packages updated to 2024-08-28 (and mirrorlists set to corresponding package archive by default).
  • Kernel updated to 6.10.6 (thanks Blaze)
  • Fixes for guiexec= cheatcode. Should work from multiple places: cmdline, config/login and config/cheatcodes (thanks Roadie)
  • Fix for volume= cheatcode. Should work with or without %, if i remember correctly
  • Kora icons: tweaked the shutdown/reboot/logout/sleep icons with some color
  • Added a "dummy" package "nemesis-plug" that plugs some dependency holes, by supplying package information to trick various programs (do `pacman -Qi nemesis-plug` for details)
  • Cinnamon: changed to Mint-Y-Grey gtk themes
  • Small adjustment to pman for firefox specific config: added entry in distribution.ini to turn off advertiser info thingy.
Known issues:
  • syslog-ng makes some noise about missing libs to do with optional plugins ..some way of configuring this out rather then adding all that stuff would be good
  • Lxqt panel still clock is somewhat broken
  • The language modules havn't been updated yet, so lxqt and cinnamon will have spotty support until i do so.
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

nanZor
Shogun
Shogun
Posts: 406
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.01 x86-64 LXQT

Nemesis update- v24.08 (2024-08-28)

Post#2 by nanZor » 22 Sep 2024, 13:57

First try at Nemesis and I'm really pleased. Running LXQT, using a module for my changes on a FAT32 usb stick using the default name and path. Noticed something weird though..

If I create text files in qterminal, and save to my module at the end of a session, I seem to lose my previous settings to the font size in LXQT Appearance. Other desktop changes seem to survive a reboot, (like panel-bar size, etc) but the font size in the drop down menu seems to default back to original if I use the terminal to create files in a session.

If I don't do any terminal work, then the font sizes in lxqt appearance seem to be persistent across reboots. But I like the terminal, so can't have that! :)

That was a hair-puller to figure out! Lovin' Nemesis, nice job!
Even read the faq with the onboard mini-browser! Awesome.
That's a UNIX book - cool. -Garth

nanZor
Shogun
Shogun
Posts: 406
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.01 x86-64 LXQT

Nemesis update- v24.08 (2024-08-28)

Post#3 by nanZor » 22 Sep 2024, 16:05

Update - I tried LXDE and I'm running into the same thing. Everything was saving to the module just fine. But right after pmod'ing Firefox, activating, doing a save-session (graphically), and rebooting after a session, I'm losing lxde font size changes in the menus, and also losing text files in the terminal.

PEBKAC - my fault. What was I thinking? Used a savefile.dat for fat32 and all is well. :wall:

Although LXDE does have that volume control slider issue with it only decreasing in the fine-slide with the mouse-wheel. Not a showstopper. Going to hide now. :)
That's a UNIX book - cool. -Garth

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 4114
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Nemesis update- v24.08 (2024-08-28)

Post#4 by ncmprhnsbl » 23 Sep 2024, 13:21

nanZor wrote:
22 Sep 2024, 16:05
PEBKAC - my fault. What was I thinking? Used a savefile.dat for fat32 and all is well
thanks for the feedback :)
save session to module should work for this, regardless of install filesystem. i'll investigate further.
nanZor wrote:
22 Sep 2024, 16:05
volume control slider issue
confirmed(also present in slackware porteus) and i see an open issue on their repo for it with a patch. (and i see few other unmerged pull requests that might be useful patches too)
i'll do some patching on lxpanel for the next release.
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

nanZor
Shogun
Shogun
Posts: 406
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.01 x86-64 LXQT

Nemesis update- v24.08 (2024-08-28)

Post#5 by nanZor » 24 Sep 2024, 01:23

Nice, thank you. This may help so you don't go crazy looking for a phantom problem on my end:

1) Fired up LXQT Nemesis (sweet) for the first time (on fat32) and thought I'll just do changes modules instead of savefiles.
2) Made environmental changes to my liking, and made a changes module before rebooting.
3) Reboot - great persistence works!
4) Make even more changes, and make a changes module of that before rebooting. - great, it works! Looks like it overwrote it, only one changes module.
5) Repeat yet again, but make changes to qterminal font-sizes, touch a few dummy files etc. Make a module for persistence test before rebooting.
6) Reboot to check for persistence. UH OH.
7) Lost my previous font-size changes to the lxqt drop downs. What's this? I lost my font size preference in qterminal, and a few of my text files were gone.
8) Decided to mess with the clock. Well now, when making a changes module before rebooting, it made a NEW changes module with the new date! So now there are two changes modules.

Thing is I KNOW that savefiles work just fine, but I put on my propeller-hat to outsmart the system. I *think* I was simply layering module upon module upon module until it barfed. And no adult-beverages were near me. :)

The REAL problem is I can't keep my hands off Porteus, PorteuX, and Nemesis. You dev's and contributors are awesome, man! (sniff!)
That's a UNIX book - cool. -Garth

vinnie
Samurai
Samurai
Posts: 132
Joined: 13 Jun 2024, 08:25
Distribution: alpine

Nemesis update- v24.08 (2024-08-28)

Post#6 by vinnie » 28 Sep 2024, 07:09

Oh, the new version, I had missed it!
To update it, do I just replace the modules in the distribution or do I have to reinstall Nemesi from scratch and update all the packages I had built with pmod and trizen?

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 4114
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Nemesis update- v24.08 (2024-08-28)

Post#7 by ncmprhnsbl » 28 Sep 2024, 21:49

vinnie wrote:
28 Sep 2024, 07:09
update it, do I just replace the modules in the distribution or do I have to reinstall Nemesis from scratch and update all the packages I had built with pmod and trizen?
just replace the modules in the distribution (and the vmlinuz in /boot/syslinux) should be enough.
the packages you built may need updating (rebuilding) or not, depending whether they have an update or some dependency has become incompatible. ymmv
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

SlikeSayer
Ronin
Ronin
Posts: 2
Joined: 09 May 2024, 12:38
Distribution: Artix

Nemesis update- v24.08 (2024-08-28)

Post#8 by SlikeSayer » 30 Sep 2024, 00:25

Hello!!! 😃
I don't want to bother you.
But, I think you might want to consider making a new KDE Plasma Iso Version.
I promise it will be worth your time and effort because it will be the most used of all! 🤑
If it seems like a lot of work, you might want to stop developing the Cinnamon version and dedicate yourself to the KDE Plasma Edition.
Please, I beg you, just do it 🙏
I assure you that there are many people who want the same thing.
You can be sure that if you make it, you will be making a masterpiece! 🤩
Thank you very much in advance.
You do a very nice job, keep it up! 👍

Translated with DeepL.com (free version) I'm from Venezuela, my pleasure! ✌️🤝

beny
Full of knowledge
Full of knowledge
Posts: 2201
Joined: 02 Jan 2011, 11:33
Location: italy

Nemesis update- v24.08 (2024-08-28)

Post#9 by beny » 30 Sep 2024, 09:50

hi,not nemesis but you have porteux that it have something new: PorteuX 1.6 has been released take a look if it fit your need

SlikeSayer
Ronin
Ronin
Posts: 2
Joined: 09 May 2024, 12:38
Distribution: Artix

Nemesis update- v24.08 (2024-08-28)

Post#10 by SlikeSayer » 30 Sep 2024, 14:20

Yes! Actually, I already knew that distro! But, it's Slackware base.. 😭
I think Arch Linux has more benefits than Slackware! 🤑
That is why I want a Nemesis Linux iso with KDE Plasma!! ✌️🤩

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 4114
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Nemesis update- v24.08 (2024-08-28)

Post#11 by ncmprhnsbl » 30 Sep 2024, 23:01

SlikeSayer wrote:
30 Sep 2024, 00:25
But, I think you might want to consider making a new KDE Plasma Iso Version.
:) ..well, i haven't not considered it.** i won't say never, we'll see.. ;) (** i'm not sure how well double negatives translate)
in the meantime: (not using the lxqt for a base, since it most likely is missing some parts of qt6 that plasma wants (actually not using any 003-* is the best way)

Code: Select all

# pmod plasma
might get something usable.. though i would expect it to be huge.
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

beny
Full of knowledge
Full of knowledge
Posts: 2201
Joined: 02 Jan 2011, 11:33
Location: italy

Nemesis update- v24.08 (2024-08-28)

Post#12 by beny » 01 Oct 2024, 15:50

hi, yes the whole kde-24.08.1-1 xzm load 590mb and you have to add qt6 and plasma,nemesis have the python3.12,no usb key installation, ssd with enclosure is the better for....

vinnie
Samurai
Samurai
Posts: 132
Joined: 13 Jun 2024, 08:25
Distribution: alpine

Nemesis update- v24.08 (2024-08-28)

Post#13 by vinnie » 05 Oct 2024, 11:15

So, I'm trying the new nemesis and it boot without any problems.
However, in the pc where I'm testing it, I needs to have default graphics settings otherwise I can't use it.

This time I opted for the savefile however there are problems:
1) after I create it I get a window confirming the creation of the savefile.dat. Then a dialog box says it will open the config file to check if the line “changes=/mnt/sdb1/porteus/saves/porteussave.dat” is added at the end of the configuration but the file is not opened and the line is not added.

2)Then I go to edit by hand the file “/mnt/sdxy/config/cheatcodes” and add the lines “from=UUID:03fcfe32-857f-4884-b2bd-48a2c1fe7891” (to avoid wrong partition at boot)
and the line “changes=/mnt/sdb1/porteus/saves/porteussave.dat” (exactly as recommended by the previous dialog box).
On reboot, however, it appears that the changes were not restored at reboot.

Now beyond solving this problem, I have more questions.
1) The savefile.dat seems to be fixed size (it even makes me choose the filesystem type), how is savefile.dat supposed to work?
2) Maybe I would prefer the to create a save module.
Is what I am using now with the other pc and it worked, however when I had made another save instead of updating the first one, another one was created. I had tried then to delete the first one and had lost the saves made in the beginning, so I understand that the save is layered and I don't know if I really like it that way.

Could you help me understand the saving better?


[Update 1]
I may have figured out how the creation of save modules works, every time you make a save the changes are saved from the initial state (the startup state I guess) to the current state. *So if you make changes, save a module, make more changes and save another time with the same name, only the new changes are saved and the previous ones are lost....
If it works that way ok, however there would need to be at least a check to avoid overwriting and give the possibility to merge two saves (doing it by hand with xzm2dir seems impossible with the save modules, this error is returned: "FATAL ERROR: write_file: failed to lstat file new/.wh..wh.aufs, because Operation not permitted").

*Not exactly.
It is my understanding that the saved changes are the difference between the current state and the startup state (including any mounted save modules). So if you overwrite a module while you haven't yet done a reboot you don't lose the contents of the overwritten module, but as soon as you do a reboot and load it, if you overwrite it you lose it.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 4114
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Nemesis update- v24.08 (2024-08-28)

Post#14 by ncmprhnsbl » 06 Oct 2024, 04:45

vinnie wrote:
05 Oct 2024, 11:15
2)Then I go to edit by hand the file “/mnt/sdxy/config/cheatcodes” and add the lines “from=UUID:03fcfe32-857f-4884-b2bd-48a2c1fe7891” (to avoid wrong partition at boot)
and the line “changes=/mnt/sdb1/porteus/saves/porteussave.dat” (exactly as recommended by the previous dialog box).
On reboot, however, it appears that the changes were not restored at reboot.
could be a bug :) ..it's possible that this is one cheatcode that won't work via the cheatcodes config :( .. in this case the APPEND line in /boot/syslinux/porteus.cfg is the way to go..
vinnie wrote:
05 Oct 2024, 11:15
1) The savefile.dat seems to be fixed size (it even makes me choose the filesystem type), how is savefile.dat supposed to work?
pretty much requires you to guess how much space you think you'll need, usually overestimating is best.
vinnie wrote:
05 Oct 2024, 11:15
It is my understanding that the saved changes are the difference between the current state and the startup state (including any mounted save modules). So if you overwrite a module while you haven't yet done a reboot you don't lose the contents of the overwritten module, but as soon as you do a reboot and load it, if you overwrite it you lose it.
sounds correct, though not ideal
vinnie wrote:
05 Oct 2024, 11:15
If it works that way ok, however there would need to be at least a check to avoid overwriting and give the possibility to merge two saves (doing it by hand with xzm2dir seems impossible with the save modules, this error is returned: "FATAL ERROR: write_file: failed to lstat file new/.wh..wh.aufs, because Operation not permitted").
certainly, a check for a same named module that would overwritten should probably occur, with at least a warning.
it is possible to xzm2dir a save module with whiteouts in a posix directory outside the live filesystem ie. some mounted volume (which admittedly isn't always available)
but, there's probably no reason for those whiteout files (.wh..wh.*) to be included in the first place, so here's an edited /usr/local/bin/save-session that should exclude those:
which will allow for extraction within the live filesystem.
(also excluded /mnt for the hell of it)
which has me thinking of moving the exclude list to a user configurable one somewhere in the config folder.

EDIT:
just looking at the config folder, i noticed the "backup" file:

Code: Select all

### Service backup file.
### Files listed here will be copied into a module when you run
### the script /usr/local/bin/setup-config-files
### Files must be listed one per line without space before them.
###

/home/guest/.bashrc
/root/.bashrc
/etc/passwd
/etc/group
/etc/shadow
/etc/gshadow
/etc/login.defs

first correction: it should be /usr/local/bin/backup-config-module
this should work in the opposite fashion to save-session, only keeping what is explicitly included, which is handy when you know exactly what you want to keep, not so much if you don't.
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
Ed_P
Contributor
Contributor
Posts: 8600
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Nemesis update- v24.08 (2024-08-28)

Post#15 by Ed_P » 06 Oct 2024, 23:34

ncmprhnsbl wrote:
06 Oct 2024, 04:45
pretty much requires you to guess how much space you think you'll need,
Same logic as determining how big a USB drive to get or how big to make a ext4 partition. Need to know what you're going to use the Porteus system for and where you will save files you download.
ncmprhnsbl wrote:
06 Oct 2024, 04:45
usually overestimating is best.
Absolutely, cause overfilling the file results in rebuilding everything you had saved in it. :crazy: :mega_shok:

When shutting down my system indicates how much space has been used and how much is free and I can decide whether to save the current changes or do it the next time after I have expanded the .dat file. I also run a script to check it's space usage periodically.

spaceck,sh

Code: Select all

#!/bin/sh
# Add to /etc/rc.d/rc.local_shutdown.  And make rc.local_shutdown executable.
#                                      sudo chmod +x /etc/rc.d/rc.local_shutdown
# Bogomips help: https://forum.porteus.org/viewtopic.php?f=140&t=6069&p=47591#p47589
#                https://forum.porteus.org/viewtopic.php?f=140&t=6069&p=47614#p47598

# du -BM -d3 /mnt/live/memory/images/changes 

# Color definitions
txtbld=$(tput bold)               # Bold
txtred=${txtbld}$(tput setaf 1)   # Red
rst=$(tput sgr0)                  # Reset

function redwarning() {
   echo -e $txtred "$1" $rst
}

BOOTDEV=`grep -A1 "Booting" /var/log/porteus-livedbg|tail -n1|sed 's^//^/^g'`
if [ "$BOOTDEV" == "/mnt/isoloop" ]; then
   BOOTDEV=`grep -A1 "ISO=" /var/log/porteus-livedbg`
   BOOTDEV=${BOOTDEV:4:9}
fi
if [ "$BOOTDEV" == "/mnt/nvme" ]; then
   BOOTDEV=`grep -A1 "ISO=" /var/log/porteus-livedbg`
   BOOTDEV=${BOOTDEV:4:14}
fi
VERSION=$(cat /etc/porteus-version)
FOLDER=porteus${VERSION:9:3}
Changes=$BOOTDEV/$FOLDER/changes
if [ ! -d $Changes ]; then 
   Changes="$BOOTDEV/changes"
fi
#set -x;

#SaveDat=porteussave.dat                                            ### Tweak as needed
SaveDat=50save.dat
#SAVEDAT=$(ls -t $Changes/)  # ls -gt $CHANGES
#SaveDat=$(echo $SAVEDAT | awk '{print $2}')  # '{print $1}')
#echo $SaveDat $SAVEDAT
if [ -n "$1" ]; then
   SaveDat=$1
fi
#set -x;

if [ -a /mnt/live/memory/images/changes ]; then
   SDspace=$(df -BM --output=size,used,avail,pcent /mnt/live/memory/images/changes | tail -n1)
   Changes=/mnt/live/memory/images/changes
   SAVEDAT=$(cat /proc/cmdline | awk '{print $7}')
   SaveDat=${SAVEDAT:33}
else
   if [ ! -f $Changes/$SaveDat ]; then
      echo "No $Changes/$SaveDat file."
      read && exit
   fi
   echo toor | sudo -S -u root mloop $Changes/$SaveDat &>/dev/null        
   SDspace=$(df -BM --output=size,used,avail,pcent /mnt/loop | tail -n1)
   Changes=$Changes/$SaveDat
   echo toor | sudo -S -u root uloop &>/dev/null
fi

# echo $SDspace
read size used avail percent <<< $SDspace
if [ ${percent%\%} -ge  85 ]; then
   /usr/share/porteus/gtkdialog.py -p "Warning!  $SaveDat file $percent full" -s "Used: $used - Free: $avail" -d err
   exit
else
#  https://forum.porteus.org/viewtopic.php?p=78822#p78822 - ncmprhnsbl - '/usr/share/porteus/gtkdialog.py -h' to see the usage..  
   /usr/share/porteus/gtkdialog.py -p "$Changes"    -s "$SaveDat file $percent full - Used: $used - Free: $avail" -d info 
   exit
fi

# if no dialog option.
if [ ${percent%\%} -ge  85 ]; then
   echo 
   redwarning "Warning! save.dat file $percent full.  Used: $used  Free: $avail"
   echo 
else
   echo "save.dat file $percent full.  Used: $used  Free: $avail"
fi
sleep 5
exit

Post Reply