2021 Updated Nemesis Base Modules

Arch based Porteus community project

Moderator: M. Eerie

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

2020 Updated Nemesis Base Modules

Post#151 by ncmprhnsbl » 01 Jun 2020, 08:52

M. Eerie wrote:
28 May 2020, 20:12
Does pman works for you? I'm having troubles pinging to the router resulting in:
seems to be ok here..
M. Eerie wrote:
28 May 2020, 20:12
Also, does pkg2xzm manage new *.zst packages?
yeah, no.. because arch's build of file doesn't handle -z(uncompress) option with zstd archives, which is kind of stupid since they've adopted zstd for their packaging(ironically slackware's file has no such problem) .. so, for the moment, a workaround would be to disable the checking section: ie. comment lines 19~

Code: Select all

[ ! -e $pkg ] && { echo "`gettext "File does not exist."`"; exit 1; }
ftype=`file -bz $1`
[[ ! `grep -o "POSIX tar" <<<$ftype` ]] || [[ ! `grep -o "XZ compressed" <<<$ftype` ]] && bad=0

[ "$bad" ] && { echo "`gettext "This does not appear to be an arch package."`"; exit; }
or maybe something like:

Code: Select all

ftype=`file -b $1`
[[ ! `grep -o "XZ compressed" <<<$ftype` ]] && [[ ! `grep -o "Zstandard compressed data" <<<$ftype` ]] && bad=0
not great but unless your using a * in a dir of random pkgs and other archives, shouldn't be a problem..
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

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

2020 Updated Nemesis Base Modules

Post#152 by ncmprhnsbl » 16 Sep 2020, 06:20

2020-09-16
base modules updated with latest package versions.
notes:
core:
js60 > js68
replaced libutil-linux with util-linux-libs
replaced opensysusers with esysusers
replaced opentmpfiles with etmpfiles
pkg2xzm should work for zst pkgs( just commented the file type check, as per above^)

gui:
xorg-fonts-alias replaced with xorg-fonts-alias-misc

added to xtra:
rav1e, l-smash (new ffmpeg deps)
pulseaudio, alsa-plugins, alsa-topology-conf, alsa-ucm-conf, rtkit, pulseaudio-alsa (was having trouble with audio, basicly threw a bunch of stuff at it)
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

raja
Shogun
Shogun
Posts: 434
Joined: 02 May 2017, 09:51
Distribution: v3.2.2-32 and Porteus-Artix-64
Location: Chennai,India

2020 Updated Nemesis Base Modules

Post#153 by raja » 25 Sep 2020, 17:25

After recent update...

following errors noticed during boot.. in rc.log

Code: Select all

 * Setting up tmpfiles.d entries ...
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /var during canonicalization of /var.
Detected unsafe path transition /  /var during canonicalization of /var/lib.
Detected unsafe path transition /  /run during canonicalization of /run.
Detected unsafe path transition /  /run during canonicalization of /run/lock.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /run during canonicalization of /run.
Detected unsafe path transition /  /run during canonicalization of /run.
Detected unsafe path transition /  /run during canonicalization of /run.
Detected unsafe path transition /  /var during canonicalization of /var.
Detected unsafe path transition /  /run during canonicalization of /run.
Detected unsafe path transition /  /run during canonicalization of /run/sudo.
Detected unsafe path transition /  /var during canonicalization of /var.
Detected unsafe path transition /  /var during canonicalization of /var.
Detected unsafe path transition /  /var during canonicalization of /var.
Detected unsafe path transition /  /var during canonicalization of /var.
Detected unsafe path transition /  /tmp during canonicalization of /tmp.
Detected unsafe path transition /  /tmp during canonicalization of /tmp.
Detected unsafe path transition /  /tmp during canonicalization of /tmp.
Detected unsafe path transition /  /tmp during canonicalization of /tmp.
Detected unsafe path transition /  /tmp during canonicalization of /tmp.
 [ !! ]
 * ERROR: opentmpfiles-setup failed to start
boot-network-setup Line 73: Started dhcpcd on all interfaces

ERROR in boot-network-setup on line 74:
Could not start dhcpcd

Code: Select all

Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /var during canonicalization of /var.
Detected unsafe path transition /  /var during canonicalization of /var/lib.
Detected unsafe path transition /  /run during canonicalization of /run.
Detected unsafe path transition /  /run during canonicalization of /run/lock.
Detected unsafe path transition /  /etc during canonicalization of /etc.
Detected unsafe path transition /  /run during canonicalization of /run.
Detected unsafe path transition /  /run during canonicalization of /run.
Detected unsafe path transition /  /run during canonicalization of /run.
Detected unsafe path transition /  /var during canonicalization of /var.
Detected unsafe path transition /  /run during canonicalization of /run.
Detected unsafe path transition /  /run during canonicalization of /run/sudo.
Detected unsafe path transition /  /var during canonicalization of /var.
Detected unsafe path transition /  /var during canonicalization of /var.
Detected unsafe path transition /  /var during canonicalization of /var.
Detected unsafe path transition /  /var during canonicalization of /var.
Detected unsafe path transition /  /tmp during canonicalization of /tmp.
Detected unsafe path transition /  /tmp during canonicalization of /tmp.
Detected unsafe path transition /  /tmp during canonicalization of /tmp.
Detected unsafe path transition /  /tmp during canonicalization of /tmp.
Detected unsafe path transition /  /tmp during canonicalization of /tmp.
 [ !! ]
 * ERROR: opentmpfiles-setup failed to start
 * Starting local ...
 [ ok ]

rc default logging stopped at Fri Sep 25 00:34:17 2020
However, system boots to desltop.
Linux Kernel-4.4.272 -32 bit; Linux Kernel-5.4.185 - 64 bit

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

2020 Updated Nemesis Base Modules

Post#154 by ncmprhnsbl » 27 Sep 2020, 04:28

raja wrote:
25 Sep 2020, 17:25
following errors noticed during boot.. in rc.log
thanks for reporting :)
i think this might be because of the root (/) filesystem somehow picking up a sticky(t) tag in it's permissions( check: stat / )
havn't tracked down how this happened, but have reuploaded 001, 002s, and 05-devel with permissions fixed(755), and the rc.log on my test run looked ok.. also seemed to fix broken /bin /sbin /lib /lib64 links that i had noticed..
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

raja
Shogun
Shogun
Posts: 434
Joined: 02 May 2017, 09:51
Distribution: v3.2.2-32 and Porteus-Artix-64
Location: Chennai,India

2020 Updated Nemesis Base Modules

Post#155 by raja » 30 Sep 2020, 10:39

As you said strict implementation of permissions, was the cause. I continued to get those errors with modified 001 & 002.

I keep porteus folder, as r-w-x for guest, for my convenience. So I added , 'norootcopy' to boot parameter and all those error messages in rc.log vanished.

Thanks.

I went through ' Gentoo' forum, regarding conversion of Systemd* to Openrc init. Purpose is to modify Neko's Aporteus to Openrc. I collected a list of files that may be required from Nemisis OS and try with a boot parameter, init=/usr/bin/openrc-init.

Request: As an expert, thorough with internals of this init, can you please make a xzm module with all needed files.
Not so urgent. An experiment!

* Systemd has problem in unmounting all drives in use and modules in tmpfs in memory cleanly, leaving dirty message, during shutdown.
Linux Kernel-4.4.272 -32 bit; Linux Kernel-5.4.185 - 64 bit

User avatar
Blaze
DEV Team
DEV Team
Posts: 3869
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

2020 Updated Nemesis Base Modules

Post#156 by Blaze » 04 Oct 2020, 09:01

ncmprhnsbl, with a new Nemesis base - I can't boot it.
MyXorg log https://pastebin.com/e7tBNPgc
Linux 6.6.11-porteus #1 SMP PREEMPT_DYNAMIC Sun Jan 14 12:07:37 MSK 2024 x86_64 Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

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

2020 Updated Nemesis Base Modules

Post#157 by ncmprhnsbl » 04 Oct 2020, 12:38

Blaze wrote:
04 Oct 2020, 09:01
with a new Nemesis base - I can't boot it.
looks like we're missing vulkan-icd-loader : a mesa dep..
you can try:
1. boot to text
2. do: pacman -Sy vulkan-icd-loader
3. and then startx
raja wrote:
30 Sep 2020, 10:39
Request: As an expert, thorough with internals of this init, can you please make a xzm module with all needed files.
Not so urgent. An experiment!
:) expert? me? i'll see what i can do ... i suspect there may differences in the initrd.xz too.. eg. i think aporteus is mounting it's modules in /run/ somewhere...
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
Blaze
DEV Team
DEV Team
Posts: 3869
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

2020 Updated Nemesis Base Modules

Post#158 by Blaze » 04 Oct 2020, 13:08

ncmprhnsbl, well, but setup-pman and pacman does not work for me :D
Linux 6.6.11-porteus #1 SMP PREEMPT_DYNAMIC Sun Jan 14 12:07:37 MSK 2024 x86_64 Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

Kulle
Warlord
Warlord
Posts: 594
Joined: 28 Jan 2017, 10:39
Distribution: v4.0 64bit Xfce
Location: Berlin

2020 Updated Nemesis Base Modules

Post#159 by Kulle » 08 Oct 2020, 11:10

nemesis WiFi problem !

I've downloaded from mediafire
nemesis-xfce-20.02.04-x86_64.iso
I've tried it.
startup is very fast.

But there is a WIFI problem:
WiFi has been detected and the wireless network connection is active after entering the password.
But then:
When using the browser: Error message "This site can’t be reached https://google.com/ is unreachable"
What can that be??

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

2020 Updated Nemesis Base Modules

Post#160 by ncmprhnsbl » 11 Oct 2020, 06:40

updated base modules 2020-10-11
core:
now js78
added libxcrypt (needed for perl)
pkgs updated
gui:
added vulkan-icd-loader (missing mesa dep)
pkgs updated
xtra:
pkgs updated
devel:
pkgs updated
xfce:
added:
libappindicator-gtk3
libdbusmenu-glib
libdbusmenu-gtk3
libindicator-gtk3
:needed for nm-applet
Kulle wrote:
08 Oct 2020, 11:10
nemesis-xfce-20.02.04-x86_64.iso
can only suggest: install it and update the base modules
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

Kulle
Warlord
Warlord
Posts: 594
Joined: 28 Jan 2017, 10:39
Distribution: v4.0 64bit Xfce
Location: Berlin

2020 Updated Nemesis Base Modules

Post#161 by Kulle » 11 Oct 2020, 08:19

Hi ncmprhnsbl,

I have now everything updated (Date: 20201011)
Also kernel (000-kernel-5.4.16.xzm ) und vmlinuz
But the error remained!

By the way:
Exactly the same error also with a new German Porteus (based now on Porteus 5.0rc1), see here #239 :
Porteus linux on the net or on the waves of the web
#239
This is very strange!
With all other Porteus versions that I have tried on my notebook so far, this strange error has never occurred.

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

2020 Updated Nemesis Base Modules

Post#162 by beny » 11 Oct 2020, 11:55

hi kulle you connect to wifi with what: wicd or other one, you are sure that the radio is on,and if you don't use wicd maybe is useful to install iw to set up your wifi device.

User avatar
Blaze
DEV Team
DEV Team
Posts: 3869
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

2020 Updated Nemesis Base Modules

Post#163 by Blaze » 11 Oct 2020, 12:04

Download ISO nemesis-xfce-20.10.11-k5.4.50-x86_64.iso (Arch Linux version of Porteus)
http://www.mediafire.com/file/z7aa9e5fj ... 4.iso/file
Image
Linux 6.6.11-porteus #1 SMP PREEMPT_DYNAMIC Sun Jan 14 12:07:37 MSK 2024 x86_64 Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

User avatar
M. Eerie
Moderator
Moderator
Posts: 620
Joined: 31 Aug 2017, 21:18
Distribution: Nemesis Xfce/MATE x64

2020 Updated Nemesis Base Modules

Post#164 by M. Eerie » 12 Oct 2020, 09:06

Hi guys.

@Blaze @beny @ncmprhnsbl and @anyone interested:

I've been using this script to update nemesis base modules, but it's not working 100%.

Until now, this method works pretty well while updating xtra, gui and xfce base modules.

However, core one is another matter. Maybe because it has some key files that need to survive the --overwrite pacman switch. Perhaps --force instead would do the trick, or maybe using pacman -U instead of pacman -S, but I'm stuck and need some help.

Can anyone give a hand?

Thanks so much.

Cheers!

Script follows:

Code: Select all

#!/bin/bash
# Update NEMESIS base modules ( $PORTDIR/base )
# <https://forum.porteus.org> 

HERE="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
warn() { echo; echo "$(tput setaf 1) $1 $(tput sgr0)"; echo; }
confirm() { echo; tput setaf 6; read -n1 -rsp "$1"; tput sgr0; echo -e "\n"; [[ $REPLY = [Yy] ]]; }

[ ! $(grep -o 'base' /proc/cmdline) ] && echo "Please init Nemesis with **Always Fresh** boot paramaters" && exit 0;
[ ! $EUID != 0 ] || sudo $(basename $0)

the_end() {
	if [ $? == 0 ]; then
		dir2xzm /tmp/LOCALES /tmp/LOCALES.xzm
		mv /tmp/'*.xzm' $HERE
		cd /tmp; rm -r LOCALES $outMOD >/dev/null 2>&1
		echo -ne "  All Done! \n Your files are here: $HERE"
	else 
		warn " Aborted. Exit code: $?"
	fi
	unset patches HERE outMOD
	eval "exit $?"
}
trap the_end SIGHUP SIGINT SIGTERM

fixPERMS() {
	chmod -f 750 $1/root #$1/etc/sudoers.d/ $1/etc/openvpn/client/ $1/etc/openvpn/server/
	chmod -f 755 $1/etc $1/etc/local.d $1/usr $1/usr/local $1/usr/local/bin
	find $1/usr/share/icons -type d -exec chmod 755 {} + >/dev/null 2>&1
	find $1/usr/share/icons -type f -exec chmod 644 {} + >/dev/null 2>&1
}

prepareSYS() {
fixPERMS ""

[ $(pacman -Qu | wc -l) == 0 ] || {
	setup-pman # WORKAROUND In case setup-pman fails --> "Please ensure you have a connection and try again. Exit code: 1"
	if [ $? == 1 ]; then
		pacman-db-upgrade && pacman -Sy
		haveged; sleep 3; pacman-key --init; pacman-key --populate archlinux artix; pkill haveged; update-ca-trust;
	fi
	pacman -Syyu --overwrite '*'
	touch /tmp/dbDONE ### avoid iterations
	}
	echo "  System updated!"; echo
}

updateBASE() {
	[ -f /tmp/dbDONE ] || prepareSYS
	[ ! -d /tmp/LOCALES ] && mkdir -p /tmp/LOCALES
	PS3=$'\n'$'\e[00;36mPlease, select base module to update or exit (1-5): \e[0m'
	select outMOD in core gui xtra xfce exit
	do
		patches=""
		case $outMOD in
			core) patches="{archlinux,artix}-{keyring,mirrorlist}";;
			 gui) patches="";;  #TODO Could be used to interact with the user adding new deps
			xtra) patches="";;
			xfce) patches="";;
			exit*) the_end;;
		esac
	outMOD="$(basename $(ls -1 $PORTDIR/base | grep -i $outMOD) | cut -d- -f-2)"
	break
	done

cd /tmp
	unsquashfs -f -d $outMOD $PORTDIR/base/$outMOD*
	fixPERMS "$outMOD"

### PATCH CORE MODULE. TRICKY ONE AND NOT 100% WORKING AS post transactions hooks (eudev, openrc...) need to run in real root environment, (mountpoints, etc.)
	if [ $outMOD == "001-core" ]; then
		pacman -Rddr $outMOD {archlinux,artix}-{keyring,mirrorlist}
		rm -r $outMOD/etc/pacman.d/gnupg
		pacman-key --gpgdir $outMOD/etc/pacman.d/gnupg --init
		pacman-key --gpgdir $outMOD/etc/pacman.d/gnupg --populate archlinux artix
	fi

	cp -au --parents /var/lib/pacman/{sync/,local/ALPM_DB_VERSION} $outMOD
	pacman -Qqnr $outMOD | pacman --root $outMOD -Sdd - --overwrite '*'
	# UNDO previous patch / apply new deps
	[ -z "$patches" ] || eval "pacman -Sddr $outMOD $patches"

cd $outMOD
	find usr/share/locale \( -name 'e[ns]_[EU]S' -o -name 'e[ns]' -o -iname 'locale.alias' \) -exec cp -au --parents {} /tmp/LOCALES \;
	rm -r usr/share/{doc,gir-1.0,gtk-doc,info,licenses,locale,man} usr/include usr/lib/{pkgconfig,systemd} tmp boot >/dev/null 2>&1
	rm -r var/lib/pacman/{sync/,local/ALPM_DB_VERSION} >/dev/null 2>&1
	rm etc/ld.so.cache etc/sudo_logsrvd.conf etc/shadow.pacnew etc/sudo.conf

cd /tmp
	mv $outMOD/var/log/pacman.log $HERE/$outMOD-pacman.log >/dev/null 2>&1
	chown -R 0.0 $outMOD; [ -d $outMOD/home ] && chown -R 1000.1000 $outMOD/home >/dev/null 2>&1
	dir2xzm $outMOD "$outMOD"-$(date '+%Y%m%d').xzm
	rm -r $outMOD/
}

while confirm "Shall we update [Yy/*]? "; do updateBASE; done

the_end
Last edited by M. Eerie on 12 Oct 2020, 09:14, edited 1 time in total.
> Does not compute_ 🖖

https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584

User avatar
M. Eerie
Moderator
Moderator
Posts: 620
Joined: 31 Aug 2017, 21:18
Distribution: Nemesis Xfce/MATE x64

2020 Updated Nemesis Base Modules

Post#165 by M. Eerie » 12 Oct 2020, 09:11

Blaze wrote:
04 Oct 2020, 13:08
ncmprhnsbl, well, but setup-pman and pacman does not work for me
Hi Blaze.

Same was reported in this topic sometime ago: here

In fact, my script above uses a workaround to solve this issue.

Cheers!
> Does not compute_ 🖖

https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584

Post Reply