Nemesis update- v25.01 (2025-01-02)

[vinnie]

You need quite a bit of storage space but once you have it setup if you need one app you can just do it that way.

I understand, I've used docker a couple of times so basically you keep a container with archlinux (or whatever) installed and when you need a program you install it on that.
I think it can be useful and certainly podman seems to be nicer than docker since it doesn't require a daemon or root access.
I'll keep it in mind if I need to do anything in particular, thanks for the detailed guide.

[dreadbird]

Yeah I noticed shadow is installed already but I got a weird message said failed to create usernamespace /usr/bin/newuid failed to get filecaps

I then made a module of shadow it cleared it up.

Podman is super super finicky. If you get an error go to storage.conf and switch to vfs.
podman system reset
switch it back to overlay
podman system reset

that cleared it up. I think what its doing is trying to parse multiple iterations of previous config files. Then gets lost and gives bogus errors. So once you have it setup it works fine

[dreadbird]

I found something quite useful. By default syslog-ng package is installed but its setup to not log anything. The reason is because some oversight from the arch repo package which in turn went down to artix. Replacing the syslog-ng.conf with commented out lines. Just they never uncommented it. You can use metalog package

pman -Sw metalog
enter

pman -Sw metalog-openrc
enter

you have to disable syslog-ng as its doesnt make sense to have two processes listening for the same stuff
in a terminal type
rc-service syslogd-ng stop

ps aux | grep syslogd
killall syslogd or kill syslogd

cd /usr/bin/
Or it should be in path

start it with
metalog &

two processes are spawned Kernel and master. All events will be output to that terminal.

metalog logs in folders in /var/log/ example /var/log/everything will have all that is output on the terminal

This is useful for debugging if an application wont start or if you are trying to track down what package is possibly missing

[ncmprhnsbl]

You can use metalog package

thanks will ditch syslog-ng with the next update.

[ncmprhnsbl]

However, I am testing with Nemesis instead of Porteu{s,x}. Although it works relatively well, I don't know exactly where to place the "config" folder. If I put it in the first partition, the cheatcodes seem to be ignored. If I put them in the second partition, I still get multiple errors related to etmpfiles (among others) if I remember correctly.

<something from another topic .. i'll be working on a the next release shortly, so hopefully there's something that can be fixed
so.. the correct place is in the same partition as the porteus folder, or at least that's where i have it..
i'll have to investigate if i can duplicate the errors ... where exactly are you seeing them?

[M. Eerie]

where exactly are you seeing them?

Likely a permissions issue, but I don't know where it comes from. I've reviewed every single module loaded and have no clue.

BOOTING with PORTDIR in EXT4 fs:
================================
root:# cd /
user:/# ls -al
total 0
drwxr-xr-x 57 guest guest 280 Mar 28 10:57 ./
drwxr-xr-x 57 guest guest 280 Mar 28 10:57 ../
drwxr-xr-x 18 root root 4840 Mar 28 11:41 dev/
drwxr-xr-x 104 root root 340 Mar 28 10:57 etc/
drwxr-xr-x 10 root root 60 Mar 28 10:57 home/
lrwxrwxrwx 1 root root 7 Nov 21 21:50 lib -> usr/lib/
drwxr-xr-x 12 root root 240 Mar 28 11:41 mnt/
drwx------ 13 root root 140 Mar 28 11:14 root/
drwxr-xr-x 16 root root 680 Mar 28 11:14 run/
lrwxrwxrwx 1 root root 7 Nov 21 21:50 sbin -> usr/bin/
drwxrwxrwt 4 root root 180 Mar 28 11:40 tmp/
drwxr-xr-x 47 root root 100 Mar 28 10:57 usr/
drwxr-xr-x 21 root root 120 Mar 28 10:57 var/

NO .cache, bin, lib64, proc, sys, opt, srv, sys ...

BOOTING with PORTDIR in FAT32 fs:
=================================
root:# cd /
user:/# ls -al
total 0
drwxrwxrwx 53 root root 300 Mar 28 11:47 ./
drwxrwxrwx 53 root root 300 Mar 28 11:47 ../
drwx------ 2 polkitd polkitd 40 Mar 28 11:47 .cache/
lrwxrwxrwx 1 root root 7 Nov 21 21:50 bin -> usr/bin/
drwxr-xr-x 18 root root 4540 Mar 28 11:52 dev/
drwxr-xr-x 107 root root 440 Mar 28 11:52 etc/
drwxr-xr-x 8 root root 60 Mar 28 11:47 home/
lrwxrwxrwx 1 root root 7 Nov 21 21:50 lib -> usr/lib/
lrwxrwxrwx 1 root root 7 Nov 21 21:50 lib64 -> usr/lib/
drwxr-xr-x 9 root root 180 Mar 28 11:52 mnt/
drwxr-xr-x 2 root root 3 Nov 21 21:50 opt/
dr-xr-xr-x 373 root root 0 Mar 28 11:47 proc/
drwx------ 11 root root 120 Mar 28 11:52 root/
drwxr-xr-x 21 root root 780 Mar 28 11:47 run/
lrwxrwxrwx 1 root root 7 Nov 21 21:50 sbin -> usr/bin/
drwxr-xr-x 4 root root 38 Jan 3 15:20 srv/
dr-xr-xr-x 12 root root 0 Mar 28 11:47 sys/
drwxrwxrwt 6 root root 220 Mar 28 11:52 tmp/
drwxr-xr-x 45 root root 120 Mar 28 11:47 usr/
drwxr-xr-x 21 root root 120 Mar 28 11:52 var/

Code: Select all

rc boot logging started at Fri Mar 28 10:57:48 2025

 * Loading module crypto_user ...
insmod /lib/modules/6.13.6-porteus/kernel/crypto/crypto_user.ko 
 [ ok ]
 * Loading module sg ...
insmod /lib/modules/6.13.6-porteus/kernel/drivers/scsi/sg.ko 
 [ ok ]
 * Setting system clock using the hardware clock [UTC] ...
 [ ok ]
 * Mounting misc binary format filesystem ...
 [ ok ]
 * Loading custom binary format handlers ...
 [ ok ]
 * Checking local filesystems  ...
 [ ok ]
 * Remounting filesystems ...
mount: /mnt/nvme0n1p4: mount failed: Invalid argument.
mount: /mnt/nvme0n1p3: mount failed: Invalid argument.
 [ ok ]
 * Updating /etc/mtab ...
 * Creating mtab symbolic link
 [ ok ]
 * Activating swap devices ...
 [ ok ]
 * Mounting local filesystems ...
 [ ok ]
 * Configuring kernel parameters ...
 [ ok ]
 * Creating user login records ...
 [ ok ]
 * Wiping /tmp directory ...
 [ ok ]
 * Starting dbus ...
 [ ok ]
 * Starting elogind ...
 [ ok ]
 * Setting up sysusers.d entries ...
 [ ok ]
 * Setting up tmpfiles.d entries ...
Detected unsafe path transition / (owned by guest)  /var (owned by root) during canonicalization of var.
Detected unsafe path transition / (owned by guest)  /var (owned by root) during canonicalization of var/lib.

.
.
.
[color=#0000FF](Lots of similar messages)[/color]

Thanks!

[M. Eerie]

UPDATE:

I have narrowed down the issue by starting the system with BASEONLY (no additional features). The error messages remain the same.

[ncmprhnsbl]

Likely a permissions issue, but I don't know where it comes from. I've reviewed every single module loaded and have no clue.

can't say that i've ever seen that here .. all my booting is done UFI these days with initrd and vmlinuz in fat32 and PORTDIR(porteus,config) in EXT4 ...
it's beyond me how the (frugal) install partition filesystem type could have any effect on the live system .. maybe if rootcopy had the wrong ownership, but that seems like a stretch.
so..is this with stock nemesis modules? or ones you've updated? does copy2ram have any effect?

[M. Eerie]

maybe if rootcopy had the wrong ownership

That was it! I had never worried about it since I had always used a single FAT/NTFS partition.

Thanks!