Nemesis update april-06-2017 discussion

Arch based Porteus community project
User avatar
istinnjazz
Samurai
Samurai
Posts: 115
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Nemesis update april-06-2017 discussion

Post#16 by istinnjazz » 14 Apr 2017, 22:15

beny wrote:hi istinnjazz but nemesis work for you the first edition? if yes you can upgrade only the x package with the last xorg and the last mesa and repack .
thanks!!, I have just did this ...before reading your message... nice1 :)

it is very clever to have a separated and independent xorg module... this could be very beneficial for old gpu compatibility and of course to keep hard to recompile driver/kernel compilations.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 1440
Joined: 20 Mar 2012, 03:42
Distribution: 4.0-64bit all-DE+more
Location: australia
Contact:

Re: Nemesis update april-06-2017 discussion

Post#17 by ncmprhnsbl » 14 Apr 2017, 22:36

@istinnjazz .. my comment was directed at you (i didnt notice francois' comment for some reason)
i see you have found a solution :good:
this topic: viewtopic.php?f=138&t=6484 outlines a method/commands that can be used to upgrade other modules you may have..
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
istinnjazz
Samurai
Samurai
Posts: 115
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Nemesis update april-06-2017 discussion

Post#18 by istinnjazz » 14 Apr 2017, 22:56

nice...

I will have to study a bit because I tend to forget some parts i have left behind...

so lets say I have an almost updated file system through my savefile... and then I will try to update a base module like yours or the lxde one by the new method...
Is there a possibility that might be a conflict? what is the aufs layer priority in that case? savefile or the core module (or a simple module)?

is this order right? savefile ->user-module->base-core-module ?

what about a clean function for the savefile that can remove some old outdated duplicated files that are older than core? (of course there might be constant garbage files @ savefile, but I guess without any harm, until a package or system update function will replace them or delete them in the future again and again.

So if savefile has previous versions of the updated core files will the system know and refine this?

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 1440
Joined: 20 Mar 2012, 03:42
Distribution: 4.0-64bit all-DE+more
Location: australia
Contact:

Re: Nemesis update april-06-2017 discussion

Post#19 by ncmprhnsbl » 15 Apr 2017, 09:21

istinnjazz wrote:what is the aufs layer priority in that case?
order is: base modules first , user modules, then changes
each layering on top of the last, potentially overwriting an underlying file..
so, yes changes takes priority..
istinnjazz wrote:Is there a possibility that might be a conflict?
yes, this could present a problem..
running #pacman -Syu will complain of duplicated database entries if package(s) are in more than one place(modules or changes)
if it also wants to upgrade that package it/they can probly be removed from the changes folder using :
#pacman -R --root=/path/to/changes <package(s)> (i think thats the right command)
as opposed to just pacman -R <package> which will put whiteouts in the changes folder(which effectively removes the package completely from the live system)
istinnjazz wrote:what about a clean function for the savefile that can remove some old outdated duplicated files that are older than core?
sounds nice :) but beyond my feeble scripting abilities... :cry:
istinnjazz wrote:So if savefile has previous versions of the updated core files will the system know and refine this?
the system knows nothing.. :unknown:
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
istinnjazz
Samurai
Samurai
Posts: 115
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Nemesis update april-06-2017 discussion

Post#20 by istinnjazz » 15 Apr 2017, 09:41

ncmprhnsbl wrote:
istinnjazz wrote:what is the aufs layer priority in that case?
order is: base modules first , user modules, then changes

...
...
thanks for the explanation

User avatar
istinnjazz
Samurai
Samurai
Posts: 115
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Nemesis update april-06-2017 discussion

Post#21 by istinnjazz » 15 Apr 2017, 10:29

the duplicated files, pacman shows the related packages, so I have a very first clue of the conflicting entries

Code: Select all

guest ~ $ su
Password: 
root /home/guest # pacman -S pacman
error: duplicated database entry 'alsa-utils-openrc'
error: duplicated database entry 'libpulse'
error: duplicated database entry 'acpid'
error: duplicated database entry 'acpid-openrc'
error: duplicated database entry 'archlinux-keyring'
error: duplicated database entry 'ca-certificates'
error: duplicated database entry 'cgmanager-openrc'
error: duplicated database entry 'consolekit'
error: duplicated database entry 'consolekit-openrc'
error: duplicated database entry 'cronie'
error: duplicated database entry 'cronie-openrc'
error: duplicated database entry 'dbus-glib'
error: duplicated database entry 'dbus-openrc'
error: duplicated database entry 'device-mapper'
error: duplicated database entry 'device-mapper-openrc'
error: duplicated database entry 'dhcpcd'
error: duplicated database entry 'dhcpcd-openrc'
error: duplicated database entry 'downgrade'
error: duplicated database entry 'eudev'
error: duplicated database entry 'gcc-libs'
error: duplicated database entry 'glib-networking'
error: duplicated database entry 'glib2'
error: duplicated database entry 'glibc'
error: duplicated database entry 'glibc-openrc'
error: duplicated database entry 'gpm'
error: duplicated database entry 'gpm-openrc'
error: duplicated database entry 'haveged-openrc'
error: duplicated database entry 'inetutils-openrc'
error: duplicated database entry 'iptables-openrc'
error: duplicated database entry 'json-c'
error: duplicated database entry 'libmnl'
error: duplicated database entry 'libnftnl'
error: duplicated database entry 'libnm-glib'
error: duplicated database entry 'libsecret'
error: duplicated database entry 'lzo'
error: duplicated database entry 'mdadm'
error: duplicated database entry 'mdadm-openrc'
error: duplicated database entry 'networkmanager-consolekit'
error: duplicated database entry 'networkmanager-openrc'
error: duplicated database entry 'ntp'
error: duplicated database entry 'ntp-openrc'
error: duplicated database entry 'openrc'
error: duplicated database entry 'openssh'
error: duplicated database entry 'openssh-openrc'
error: duplicated database entry 'openvpn'
error: duplicated database entry 'openvpn-openrc'
error: duplicated database entry 'pacman'
error: duplicated database entry 'perl'
error: duplicated database entry 'syslog-ng'
error: duplicated database entry 'syslog-ng-openrc'
error: duplicated database entry 'udev-openrc'
:: Some packages should be upgraded first...
resolving dependencies...
looking for conflicting packages...

Packages (1) archlinux-keyring-20170320-1

Total Download Size:   0.62 MiB
Total Installed Size:  0.86 MiB
Net Upgrade Size:      0.08 MiB

:: Proceed with installation? [Y/n] 

User avatar
istinnjazz
Samurai
Samurai
Posts: 115
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Nemesis update april-06-2017 discussion

Post#22 by istinnjazz » 15 Apr 2017, 17:13

for those who might use nvidia linux driver and 304.xx or 340.xx branch, support for xorg 1.19 included in this update. Not tested but should work if compiled with the kernel in use.
http://www.nvidia.com/object/unix.html

Version: 340.102
Release Date: 2017.2.14
Operating System: Linux 64-bit
Language: English (US)
File Size: 66.72 MB

Version: 304.135
Release Date: 2017.2.14
Operating System: Linux 64-bit
Language: English (US)
File Size: 66.53 MB

Added support for X.Org xserver ABI 23 (xorg-server 1.19)
Fixed a bug that allowed nvidia-installer to attempt loading kernel modules that were built against non-running kernels.

User avatar
francois
Contributor
Contributor
Posts: 5369
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

Re: Nemesis update april-06-2017 discussion

Post#23 by francois » 15 Apr 2017, 19:05

Hello istinjazz. Welcome back!

A separate thread, maybe a howto for nvidia drivers under nemesis would be a great contribution. :wink:

And as you have a special type of computer, a thread on your hardware and nemesis would be a treat. :twisted:

Are you working on fat32 or linux filesystem?
Prendre son temps, profiter de celui qui passe.

User avatar
istinnjazz
Samurai
Samurai
Posts: 115
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Nemesis update april-06-2017 discussion

Post#24 by istinnjazz » 15 Apr 2017, 21:23

francois wrote: A separate thread, maybe a howto for nvidia drivers under nemesis would be a great contribution. :wink:

And as you have a special type of computer, a thread on your hardware and nemesis would be a treat. :twisted:
francois wrote:Are you working on fat32 or linux filesystem?
Yap, I see your point francois, if I will have a reason to do this again I will log the steps for a howto, it is a combination of the main porteus website kernel-compile how-to and blaze's nvidia topic (Russian).. but I cannot tell if or when this will happen.
Some additional info...
For my notebook I also have used a custom dsdt table, loaded via the compiled kernel with special config parameters and additional initrd modification to include the dsdt override. This was a tricky one , there is a strange and sometimes dangerous fan speed acpi bug @ this notebook not resolved at any of the kernels later of 3.12

Finally, I also had tested btrfs file system with success as an alternative to ext4 for the changes file, slower but I guess safer. Also with customized kernel configuration @ compile stage.

For a bit of experimentation I had used a sort of "modified" version of the kernel called "xanmod", you can search for it if you want and download the sources, it includes already the aufs patch if I remember correctly. https://xanmod.org/

System: SD card @ fat32

User avatar
francois
Contributor
Contributor
Posts: 5369
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

Re: Nemesis update april-06-2017 discussion

Post#25 by francois » 15 Apr 2017, 23:16

With a small fat32 first partition, you could install nemesis on a second partition which could be linux. This way the changes file is no more a container, thus size limited to the second partition. A first partition in fat32 is necessary if you use to boot windows once and a while. It is more natural to have a linux OS on a linux filesystem. But I imagine that you knew that already. :wink:
Prendre son temps, profiter de celui qui passe.

User avatar
istinnjazz
Samurai
Samurai
Posts: 115
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Nemesis update april-06-2017 discussion

Post#26 by istinnjazz » 16 Apr 2017, 10:50

francois wrote:With a small fat32 first partition, you could install nemesis on a second partition which could be linux. This way the changes file is no more a container, thus size limited to the second partition. A first partition in fat32 is necessary if you use to boot windows once and a while. It is more natural to have a linux OS on a linux filesystem. But I imagine that you knew that already. :wink:
Yap, I know, I just like the container for various reasons but I had used native also, there has been a discussion about it some time ago considering flash memory life span and Linux file systems if you remember (file system corruption, ext4 journaling on/off, btrfs etc).
I agree with you about the native fs superiority, Fat32 has limits, e.g max container file size on fat32. I was wondering what other file systems the system could support for the sd formatting (ntfs, ext4) to hold a container more than 4GB. Is this possible?

User avatar
Ed_P
Contributor
Contributor
Posts: 3952
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Re: Nemesis update april-06-2017 discussion

Post#27 by Ed_P » 16 Apr 2017, 18:04

istinnjazz wrote:Fat32 has limits, e.g max container file size on fat32. I was wondering what other file systems the system could support for the sd formatting (ntfs, ext4) to hold a container more than 4GB. Is this possible?
I'm pretty sure NTFS is supported and possibly exFAT. But not everything has to be stored in a "container", large downloads for example can be stored directly on the drive. My save.dat file for years use to be 320 MB, then 512 MB and now it is 1 GB due to Wine's requirements. Basically my save.dat is for system settings and configurations and caches, and my bash scripts. Even my modules are stored directly on the drive.
Ed

User avatar
istinnjazz
Samurai
Samurai
Posts: 115
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Nemesis update april-06-2017 discussion

Post#28 by istinnjazz » 22 Apr 2017, 18:47

Ed_P wrote:
istinnjazz wrote:Fat32 has limits, e.g max container file size on fat32. I was wondering what other file systems the system could support for the sd formatting (ntfs, ext4) to hold a container more than 4GB. Is this possible?
I'm pretty sure NTFS is supported and possibly exFAT. But not everything has to be stored in a "container", large downloads for example can be stored directly on the drive. My save.dat file for years use to be 320 MB, then 512 MB and now it is 1 GB due to Wine's requirements. Basically my save.dat is for system settings and configurations and caches, and my bash scripts. Even my modules are stored directly on the drive.
@ ed_p, thanks for the info. I will test ntfs probably and report back. I suppose it will have some benefits over fat32 at least for possible inconsistencies or corruption. I do not know.
I have used savefile a lot for some packages because I was a bit lazy to create some xzm packages or big xzm changes versions, but I use a ext4 hdd partition for pacman full package cache (a grow up fast directory).

So if I want to create a xzm from an already installed package, I think I will have to uninstall it and then reinstall with pman, or create a full changes file xzm snapshot and free up the changes file.
But then, if I will need to clean things up later, it might be difficult because of the lack of clean up functions. But if someone is careful could do it with minimal garbage files around.

@fransois, I have tried to recompile a recent kernel (4.9 LTS) but it gives me acpi errors and breaks the custom dsdt table I use @ initrd level, for the time being I have not have time to research this, so I will keep the old one for some months and see. I will let you know if I will do a full kernel-nvidia compile with logged instructions.

User avatar
istinnjazz
Samurai
Samurai
Posts: 115
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Nemesis update april-06-2017 discussion

Post#29 by istinnjazz » 22 Apr 2017, 20:21

I would like to note that I have just seen significant changes to the latest update of openrc manjaro packages, there will be conflicts updating to the latest base, messages like this may come out:

Code: Select all

:: Starting full system upgrade...
:: Replace cgmanager-openrc with community/elogind-openrc? [Y/n] y
:: Replace consolekit with community/elogind? [Y/n] y
:: Replace consolekit-openrc with community/elogind-openrc? [Y/n] y
:: Replace libdbus with core/dbus? [Y/n] y
:: Replace pacman-mirrorlist with core/pacman-mirrors? [Y/n] y
:: Replace pm-utils with community/elogind? [Y/n] y
:: Replace polkit-consolekit with community/polkit-elogind? [Y/n] y
:: Replace udev-openrc with community/eudev-openrc? [Y/n] y
and after this there might be many conflicting packages and forced removals maybe needed depending on installation, preventing the update and/or break the system apart. So.. backup.
I did not update, but some help might be this post: https://forum.manjaro.org/t/solved-just ... cies/21818

User avatar
francois
Contributor
Contributor
Posts: 5369
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

Re: Nemesis update april-06-2017 discussion

Post#30 by francois » 23 Apr 2017, 02:05

1) I have tried to recompile a recent kernel (4.9 LTS) but it gives me acpi errors

According to falcony:
https://forum.porteus.org/viewtopic.php ... 9&start=75
Might be related to linux kernel, if it is 4.9.1:
https://bugs.archlinux.org/task/52271

At the end user reports that in 4.9.6 it is fixed.

For slackware kernel 4.9.1 here is a solution. I don't know if you can adapt to your systemd installation:
viewtopic.php?f=53&t=6688


2) Thanks for the backup advice.
We will see how ncmprhnsbl, our expert in residence in terms of arch linux will modify its updated modules. :wink:
Prendre son temps, profiter de celui qui passe.

Post Reply