francois wrote: am happy to read your interest for nemesis.
Hallo francois, I am also glad to find out that this project is not as "sick" as it appears to be. There are some points that can be improved but I think this is a successful path of a new porteus branch. As a mutter of fact, I think it is one of the best aufs arch based distribution I have ever tried! (there are only a couple of those). At the end, maybe only this one have chances to survive.
I have used and use from time to time some puppy related distros like fatdog64 and an alternative arch based frugal distro called "alphaos" (maybe partially abandoned?).
[the similar command to "pman" on alphaOS is called "makesb"].
Although those have some interesting tools and work stably, lacked some modification features and documentation I have found in general porteus (like the straight foreword instructions for a kernel recompile). And when I saw this "nemesis" manjaro/openRC version, I was convinced to give it a try. The manjaro/aur package repository is huge, the arch platform is well supported, the Gentoo OpenRC a very respected init system. I find manjaro a good choice because of the straight support on the openRC init system.
I had also discovered the existence of the Russian only but active distro "PuppyRus", I cannot test it thought.
Those frugal distros above (alphaos/PuppyRus), I think they have locked their update managers to an "arch rollback machine", meaning that instead of using the latest updates, they stay linked on a specific date by default. This can change of course if you edit pacman conf and mirrors to the latest repository. Sometimes a good, sometimes a bad choice.
I also guess that nemesis specific custom tools/code are very few, supposedly this will make the maintenance possible, leaving most of the package support to arch/manjaro side.
I wish I knew which are they and where they reside exactly.
Finally, I am sure there are useful, basic tools that can be ported here easily. Maybe similar other distros also could feature code there, almost ready to use. For example I would like to see a create "save-file" and then a check and resize GUI script like the one from fatdog64.
I also do not know, how some manjaro related core tools could behave here, like The Manjaro HardWare Detection (mhwd) command, and the relative packages, kernels and drivers. If not, there has to be some kind of documentation not to update specific packages or use those tools.
Code: Select all
guest ~ $ mhwd
> 0000:01:00.0 (0300:10de:040d) Display controller nVidia Corporation:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-nvidia-340xx 2014.09.29 false PCI
video-nvidia-304xx 2014.09.24 false PCI
video-nouveau 2015.11.08 true PCI
video-nv 2012.09.18 true PCI
video-vesa 2012.09.18 true PCI
Code: Select all
guest ~ $ mhwd-kernel -h
Usage: mhwd-kernel [option]
-h --help Show this help message
-i --install Install a new kernel [kernel(s)] [optional: rmc = remove current kernel]
-l --list List all available kernels
-li --listinstalled List installed kernels
-r --remove Remove a kernel [kernel(s)]
francois wrote:No xorg nemesis.
I was wandering if we could strip nemesis even more to a text mode version without xorg and build from there.
This would be good, as long a xorg/openbox companion xzm package could be there for anyone to use. Many will have hard time to update in console if for example, they have to use wifi. There are huge amount of options there, even for special purposes.