Nemesis update- v24.06 (2024-06-17)

[ncmprhnsbl]

It seems to me that for porteus they are in the /opt/porteus-scripts/ directory, whereas in nemesis they are in /usr/local/bin

and some are in /usr/local/sbin .. shared between 001-core and 002-gui mostly

Ah I noticed that the interface to mount the modules is missing, is that intentional?

it's there in the right click menu (in xfce)(not the 'open with' part) down a little bit..
but yes, nemesis doesn't have all the porteus utilities, some being irrelevant, others handled by third party eg. inxi for system info..

Is anyone else getting a grey logout box.....commands work, but no colorful icons, just grey. I'm getting it in Xfce and Always Fresh. I've had no luck tracking down a file that shows any mention of the icon names for the logout box. I'm sure that no non-stock files are getting into the system at boot.
It happens only with guest user, root is fine.

, this actually a bug for the root user, in that the icon theme is not set (or incorrectly) and what you're seeing is probly a fall back to the hicolor theme for that logout box. (as you may have noticed the poor icon coverage elsewhere)
ie. the grey icons are the correct ones for the kora theme.

When booting the Cinnamon iso I see these 2 msgs:

presumably at this stage this would part of the openrc processes, and might be present in the /var/log/rc.log ..which might help the give some context..

re: sourceforge.. it has always been a bit hit and miss with download speeds .. i mainly picked it because it has it's own network of world wide mirrors..

[roadie]

, this actually a bug for the root user, in that the icon theme is not set (or incorrectly) and what you're seeing is probly a fall back to the hicolor theme for that logout box. (as you may have noticed the poor icon coverage elsewhere)
ie. the grey icons are the correct ones for the kora theme.

I'm amazed that someone would create a theme that makes the system look broken, it's a trigger every time I see it. I installed the adwaita-xfce theme, now I'm happy and un-triggered. I'm not saying it's great, there's not a lot of decent icons in the package, but it beats a grey logout box.

[vinnie]

You're right. It is located in /usr/bin @ 002-gui-YYYYMMDD.xzm module.

Okay, wouldn't there be an inclusive list of these tools somewhere? I was hoping they would all be in one .xzm so I could look at them all nice and separate already

You'll need both mate & matezcustoms modules for this to work.

I'm a little bit loyal to xfce, and it's a long history, to be brief, I think it's a "standard" type dm that hasn't undergone twists over the years but has remained consistent while still remaining supported and in constant development.
When I started I think there was gnome 2 and kde 6 (i don't remember the version). Kde was windows like, gnome was clean and simple the way I liked it, but afterward they started messing up. Xfce stayed as gnome not forcing me to follow that fork or the other, but staying true to the initial idea. I think as of today the eligible choices for me are experimental dm or xfce.

s anyone else getting a grey logout box.....commands work, but no colorful icons

The different thing for me from porteus is that I only have "suspend" but no longer have "hiberndate" and "hybrid sleep."
I think it's just an interface thing though because in power-managment the entries are still there (but I haven't tried to use them).

it's there in the right click menu (in xfce)(not the 'open with' part) down a little bit..
but yes, nemesis doesn't have all the porteus utilities, some being irrelevant, others handled by third party eg. inxi for system info..

Ah, I get it, you're referring to thunar's context menu.
Yes I wasn't referring to that, I was referring to the interface with the whole list of mounted modules and those that can be mounted, it's convenient because at a glance you can see what's mounted. I don't remember the name of the executable because I'm on nemesis now.



News: Today I had a strange problem.
When I turned on the pc today nemesis wouldn't start anymore.
To restore it eventually I reinstalled it from scratch with the usual procedure (the rock solid one ), since I'm in the experimental stage it's not a problem now, although I'm afraid to reboot now .
However, there is to say that yesterday I brutally shut down the pc by giving a poweroff from another shell, maybe somehow I messed up.
In no particular order I'd like to report that I can't find the command to do repository search, pmod -s I think interferes with preset parameters of the script, and pacman -s doesn't work, no matter pmod --help says that the parameter exists (referring to pacman!).

[ncmprhnsbl]

Ah, I get it, you're referring to thunar's context menu.
Yes I wasn't referring to that, I was referring to the interface with the whole list of mounted modules and those that can be mounted, it's convenient because at a glance you can see what's mounted. I don't remember the name of the executable because I'm on nemesis now.

ah ok, lsmodules is pygobject based, and i've been avoiding that for now (staying with older gtkdialog interfaces)
what nemesis does have is some shell functions, one of which: mods which lists active modules (it's basically 'ls /mnt/live/memory/images')
to see all the functions type: wtf (what's the functions) in the terminal. (and alias to see all the aliases)

In no particular order I'd like to report that I can't find the command to do repository search, pmod -s I think interferes with preset parameters of the script, and pacman -s doesn't work, no matter pmod --help says that the parameter exists (referring to pacman!).

pmod is just an alias for 'pman -Sw' (a hack to prevent installing in the live system when making a module)
to search use: pman -Ss or pacman -Ss or -Si for more detailed info..
for a guide to pacman: https://wiki.archlinux.org/title/Pacman
there's also fzf searching:

Code: Select all

pacman -Slq | fzf --multi --preview '\''pacman -Si {1}'\'' | xargs -ro pacman -Si

[vinnie]

what nemesis does have is some shell functions, one of which: mods which lists active modules (it's basically 'ls /mnt/live/memory/images')
to see all the functions type: wtf (what's the functions) in the terminal. (and alias to see all the aliases)

what's the function eh
nevertheless it's very useful, is there something like that that makes a list of all the nemesis own tools?
In this list I found "fuzzyactivate" which is almost the same thing, it has a list of modules although it doesn't give info on whether they are active, which is solved by "mods", and it just doesn't let you unmount the modules as well.

pmod is just an alias ... there's also fzf searching:

Okay, the search works fantastically, fzf I didn't know about it although it's very interesting.
The command you mentioned seems to work only if I put a ' at the end even though it gives me an error "unexpected end of file"

Code: Select all

pacman -Slq | fzf --multi --preview 'pacman -Si {1}' | xargs -ro pacman -Si

in that way it works, I vote to add this command to the psearch alias!

[beny]

hi just for the record: https://wiki.archlinux.org/title/Pacman/Rosetta

[vinnie]

I think the "unmount-module" command have a problem, maybe it points to the wrong path.
If I mount a module and then try to unmount it I get a window saying "is not mounted at /mnt/loop" and the program still remains accessible and it is still listed by the mods command.

edit 1:
I did a check on the fly, at line 24:

Code: Select all

chk=`cut -d" " -f2 /proc/mounts | grep -w /mnt/loop`

maybe the path to grep is '/mnt/live'

But even making that change, on line 29 the

Code: Select all

umount /mnt/loop

command doesn't specify the package name, so I can't imagine how it figures out what to unmount.

But, if I try to unmount manually:

Code: Select all

[porteus /]# umount /mnt/live/memory/images/firefox-127.0-1-x86_64.pkg.xzm/
umount: /mnt/live/memory/images/firefox-127.0-1-x86_64.pkg.xzm/: target is busy.

edit 2:
But the command

Code: Select all

modules-activation deactivate firefox-127.0-1-x86_64.pkg.xzm

is fully functional
Perhaps then this would be the command to invoke on the context menu of thunar to unmount a module?

[ncmprhnsbl]

I think the "unmount-module" command have a problem, maybe it points to the wrong path.

i'm detecting some confusion about these commands, ie. mount-(in the context of modules and other archives) and activate/deactivate

the 'mount module'(backend: mloop) and 'unmount-module'(backend: uloop) loop mount/unmount a module(or other archive) in /mnt/loop read only, purely for the purposes of inspection(or copying).
it is not layered onto the aufs filesystem.

while 'activate' does involved loop mounting, there's other processes involved in inserting/layering it onto the live aufs filesystem and i think it's best to not think about the 'mount' aspect of activation at all.
thus you cannot just umount an activated module (any more than you could just mount a module for it to be active)
as for thunar's context menu, rightclicked on a module> open > activate or deactivate ..that's it.

But the command

simply 'deactivate <module.xzm>'

[vinnie]

ok, I apologize for my mistake, I didn't realize that you also put the functionality to inspect the module just by mounting it and I was confusing/not distinguishing with module activation.

[vinnie]

hi just for the record: https://wiki.archlinux.org/title/Pacman/Rosetta

And thanks for this citation

[roadie]

It seems guiexec is not working as it's supposed to. If using something like "guiexec=palemoon~http://porteus.org/forum;mousepad~/etc/issue", it won't work. I get a 404 page with the address bar showing the guiexec command. If I drop the "~", and use spaces, it works.

EDIT: It works as intended if the command is in the config/login file, though I get a boot error about mousepad, goes too fast to get it all, but it does open. On the cmdline, the "~" doesn't work.

[ncmprhnsbl]

It seems guiexec is not working as it's supposed to.

yep, thanks ..not processing colons, i think. a single tild separated command is ok, just not multiple. in your example palemoon will fail to find "guiexec=palemoon~http://porteus.org/forum;mousepad"
looks like in /usr/share/porteus-functions line: 477

Code: Select all

cheatval=`grep -Eo " $1=[^ ]+" /proc/cmdline | cut -d= -f2`

needs the tr bit:

Code: Select all

cheatval=`grep -Eo " $1=[^ ]+" /proc/cmdline | cut -d= -f2 | tr ";" " "`

although the whole function looks a bit dodgy:

Code: Select all

get_cheatcode_value(){
unset cheatval
local cfg=/etc/porteus.d/$2
cheatval=`grep -Eo " $1=[^ ]+" /proc/cmdline | cut -d= -f2 | tr ";" " "`

if [ -z "$cheatval" ]; then
	if [ -f $cfg ]; then
		echo
		cheatval=`awk -F= '/^'$1'/{print$NF}' $cfg`
	fi
fi
}

it looks like if you use the command line, then whatever's in config/cheatcodes is ignored.. (for that cheat at least)
hmm, and /usr/local/bin/gui-autostart doesn't parse /etc/porteus.d/login but /etc/porteus.d/cheatcodes..

[roadie]

hmm, and /usr/local/bin/gui-autostart doesn't parse /etc/porteus.d/login but /etc/porteus.d/cheatcodes..

I noticed that and wondered if it should parse the login file too. Anyway, I rebuilt the 001-core.xzm with the edited /usr/share/porteus/porteus-functions file in and no difference. I did the core so as to boot Always Fresh. Even a simple "guiexec=mousepad~/etc/issue" doesn't run. No different with saved changes.

But here it gets weird. I have another Nemesis install that I'm customizing. It works with the full "mousepad~/etc/issue;palemoon~http://porteus.org/forum" plus another file I run to kill the ever present empty /.cache folder......it's a constant battle with that folder. Anyway, I can run it with saved changes and it works and that's without the edited /usr/share/porteus/porteus-functions.

Something I've noticed is that you can't have a guiexec command that includes thunar, ristretto, or engrampa. They all throw errors at boot, thunar is "can't initialize Xconf".....engrampa is "CRITICAL: and something to do with dbus, it goes way too fast to catch. Running dmesg shows for engrampa:

Code: Select all

    5.292540] elogind[1976]: Failed to connect to system bus: No such file or directory
[    5.292550] elogind[1976]: Failed to fully start up daemon: No such file or directory

It almost seems like things are happening too early in the boot. I get errors like "ristretto: file not found", but the files are in place. It doesn't stop Xorg from running, everything like wifi works as normal. I can't see any files I've changed in the custom install that would have a bearing on it, but obviously, there must be something.

[ncmprhnsbl]

But here it gets weird.

double hmmm. my test with the edit worked as expected with a command line: guiexec=xgamma~-gamma~1.475;mousepad~/etc/issue
/usr/local/bin/gui-autostart is started by the gui-autostart.desktop in /etc/xdg/autostart which starts at xorg startup.
i'll keep poking at it..

[roadie]

But here it gets weird.

double hmmm. my test with the edit worked as expected with a command line: guiexec=xgamma~-gamma~1.475;mousepad~/etc/issue
/usr/local/bin/gui-autostart is started by the gui-autostart.desktop in /etc/xdg/autostart which starts at xorg startup.
i'll keep poking at it..

Still no go here, I restored the original 001-core and built a module containing only the changed /usr/share/porteus/porteus-functions:
I used your guiexec=xgamma~-gamma~1.475;mousepad~/etc/issue.......nothing happens on hitting the desktop. I'm booting with base_only norootcopy and no changes folder or anything else.

Code: Select all

[me@nemesis]~$ ls -la /mnt/sda4/nemesis-24.01/porteus/base
total 310568
drwxr-xr-x 2 root root      4096 2024-07-07 07:30 .
drwxr-xr-x 7 root root      4096 2024-07-07 07:25 ..
-rw-r--r-- 1 root root   4456448 2024-07-05 11:08 000-kernel-6.9.8-nemesis.xzm
-rw-r--r-- 1 root root 128757760 2024-06-18 07:57 001-core-20240617.xzm
-rw-r--r-- 1 root root  88727552 2024-06-18 07:57 002-gui-20240617.xzm
-rw-r--r-- 1 root root  73637888 2024-06-18 07:57 002-xtra-20240617.xzm
-rw-r--r-- 1 root root  12869632 2024-06-18 07:57 003-shared-20240617.xzm
-rw-r--r-- 1 root root   9551872 2024-06-19 03:32 003-xfce-20240617.xzm
-rw-r--r-- 1 root root      8192 2024-07-07 07:29 06-ch-port-func.xzm

With the customized Nemesis, the guiexec command runs without a hitch.....that xgamma thing is hard on these old eyes. It also runs without the changed porteus-functions file. I'm seeing "file not found" errors with my mousepad/palemoon/kill.cache guiexec.....yet they all execute fine. I'm going through the changes between the two versions, but not finding the difference.

I did get a clue today though, so the search goes on.