Page 2 of 3
Nemesis 2022 rebooted!
Posted: 03 Nov 2022, 16:53
by M. Eerie
I have noticed that new (polkit) policy rules are present in this new release. I.e.: root user is replaced by normal (wheel) user as I experienced some time ago while developing update-base script.
I use the line below to revert:
Code: Select all
# sed -i 's/wheel/0/' /usr/share/polkit-1/rules.d/50-default.rules
On the other hand, having migrated to gtk3 and including several packages in the
shared module, my MATE module has become much thinner.
Nemesis 2022 rebooted!
Posted: 04 Nov 2022, 01:49
by ncmprhnsbl
M. Eerie wrote: ↑03 Nov 2022, 16:53
I have noticed that new (polkit) policy rules are present in this new release. I.e.: root user is replaced by normal (wheel) user as I experienced some time ago while developing update-base script.
hmm, this is from upstream .. remind me what's the upshot of this? (wheel is a group btw)
we have /etc/polkit-1/rules.d/49-rootpw_global.rules :
Code: Select all
/* Always authenticate Admins by prompting for the root
* password, similar to the rootpw option in sudo
*/
polkit.addAdminRule(function(action, subject) {
return ["unix-user:root"];
});
Nemesis 2022 rebooted!
Posted: 04 Nov 2022, 09:21
by M. Eerie
ncmprhnsbl wrote: ↑04 Nov 2022, 01:49
we have /etc/polkit-1/rules.d/49-rootpw_global.rules :
I don't know exactly when, but I remember checking that file when it failed every time I tried to automatically update packages.
It's funny that it showed up now in your release when it's been almost 2 years since I had those problems and the solution finally came when I made that modification to the file
/usr/share/polkit-1/rules.d/50-default.rules (I was looking only at /etc folder)
Try to do some regular admin tasks and you'll see.
Nemesis 2022 rebooted!
Posted: 04 Nov 2022, 13:08
by ncmprhnsbl
M. Eerie wrote: ↑04 Nov 2022, 09:21
Try to do some regular admin tasks and you'll see.
might need to be more specific ... any "regular admin task" i do works fine for me as far as i can see...
Nemesis 2022 rebooted!
Posted: 05 Nov 2022, 19:50
by M. Eerie
It occurs when I tried to activate a module (whichever it was).
I tried to reproduce the error and upload a gif, but now it doesn't happen and I don't know why.
My apologies.
Nemesis 2022 rebooted!
Posted: 16 Nov 2022, 05:15
by gnintilgyes
It looks like I would have to fix another USB stick like my copy of Porteus.
I tried to install Nemesis on ordinary 32GB drive formatted with FAT but stubborn "Porteus Installation" sh-script failed. I went into GNOME Disk Utility to set the partition to ESP. Then I try to boot it, it shows the Nemesis menu, counts down from ten to one and then resets and starts over. It seems it cannot find a file which is why it does it.
Tried again, reformatting the USB drive, putting the Nemesis files into it like instructed, then going into my copy of Porteus and choosing the "Porteus Installer". Because it was taking a really long time making it look like it was slow-formatting the new drive I aborted. Maybe I should have allowed it to finish, but why?
I had chosen Cinnamon D.E. for Nemesis. I haven't tried it yet but not very eager to have a 28GB "ext4" partition for the sake of a distro I planned to use less than my original Slackware-based Porteus MATE.
A lot of documentation still says "Porteus", and even the "main" directory is called that way but that's less important, so long as it works.
Nemesis 2022 rebooted!
Posted: 16 Nov 2022, 07:39
by spa_time
A link with install instructions and porteus kit running also appimages and windows programs
https://www.youtube.com/watch?v=5hNBOCEoCwA
for up-grade just change modules
Nemesis 2022 rebooted!
Posted: 16 Nov 2022, 09:58
by bour59
@gnintilgyes
in porteus config modify
KERNEL with KERNEL /boot/syslinux/vmlinuz
and INITRD with INITRD /boot/syslinux/initrd.xz
Nemesis 2022 rebooted!
Posted: 16 Nov 2022, 10:40
by beny
hi gnintilgyes if you have an old porteus version you can pick the linux script installer from there but you have to know if you have a guest system like windows you have to use the window installer,but the better way for linux you have to mount the usb device into a directory and run the script into this directory like this example mount /dev/sdx1 /mnt/your directory cd into the directory and run the script if you have a strange target change the script to an old one.
Nemesis 2022 rebooted!
Posted: 16 Nov 2022, 19:34
by gnintilgyes
bour59 wrote: ↑16 Nov 2022, 09:58
@gnintilgyes
in porteus config modify
KERNEL with KERNEL /boot/syslinux/vmlinuz
and INITRD with INITRD /boot/syslinux/initrd.xz
Hi bour59 thank you in advance!
Nemesis 2022 rebooted!
Posted: 16 Nov 2022, 21:40
by gnintilgyes
I'm sorry for not trying harder to search for answers on this forum or elsewhere.
The "/etc/porteus.d" is completely empty, is there supposed to be files in there?
Unless this is resolved I cannot download apps or other packages to convert to XZM. Probably could use "pacman". Ran "setup-pman" twice, each time it couldn't sense that I wasn't in "always fresh" mode. I ran "setup-config-pman" which did nothing, made sure "/config" from ISO was in the same partition as "/porteus", largely left the "/config/modules" file untouched. "pman" keeps complaining about something in "/etc/porteus.d".
Went to check my Porteus MATE (Slackware) installation and there is no such folder, but what's going on? There is a "/etc/porteus" folder but I don't think it's what a package manager would look for.
What I'm doing: I'm running on a 10-year-old HP laptop with "Sandy Bridge" CPU. I'm trying to install Nemesis Cinnamon on an external 32GB USB stick which has a 512MB ESP and a c.28GB "ext4" partition where "/porteus" and "/config" reside. I'm not using a savefile and don't want to do it that way.
Nemesis 2022 rebooted!
Posted: 16 Nov 2022, 21:59
by beny
your note have uefi on? if you have a esp partition you need to boot in efi mode and you try to boot porteus or nemesys
Nemesis 2022 rebooted!
Posted: 16 Nov 2022, 22:11
by gnintilgyes
Hi beny. I could boot from the USB drive that has to be plugged and could go into Cinnamon desktop. But I'm trying to install some apps through "pman" and I cannot. I prefer not to do it with "pacman" because I have another Arch-based distro that I'm trying to give up for this one.
Nemesis 2022 rebooted!
Posted: 16 Nov 2022, 22:21
by beny
hi you have the devel package installed i think is better that you have, and setup-pman you have to be root all the option of a package manager you need to be root, try to start pman with sudo pman -Syu that start the update of the artix repo do not install the packages that are listed say no, and try to download packages
with sudo pman -S
devel package with go and yay,you can use all the aur repository without limit.
Nemesis 2022 rebooted!
Posted: 17 Nov 2022, 06:44
by ncmprhnsbl
gnintilgyes wrote: ↑16 Nov 2022, 21:40
The "/etc/porteus.d" is completely empty, is there supposed to be files in there?
yes there should.. /config being the folder/files that populates /etc/porteus.d ...
"512MB ESP" is fat32? if you you have no intention of using "changes" there's no need for a second ext4 partition ....
i'd have to look into it, but maybe /config needs to be in same partition as /boot and /EFI ....
EDIT: yes, looking at initrd, this seems to be the case, the config files a sourced from $BOOTDEV which is the partition where /boot & /EFI are.... . so.. that's where /config should be too.