Porteus

Would this be more arch compliant and better than openrc? Saw that Void Linux using it.

https://wiki.archlinux.org/index.php/Runit

quotaholic wrote:Would this be more arch compliant and better than openrc? Saw that Void Linux using it.

have had a Void install for nearly a year, runit is quite nice ... simple to use from a user pov
ive seen a bit activity around porting void runit to arch..
openrc is better supported (in arch and manjaro) with third party repo at the mo....

but hang on.... hasnt Sensei already managed this?

I built manjaro with openrc yesterday. It boots fine. I had a problem with updating any packages via pacman due to mismatched keys though.

So these are good and bad news.

Is there any Change log peculiar to the 3.4 version or are they elsewhere?

For example, what is 002.gui.xzm and 002.xtra.xzm?

Thanks.

002-gui is the required module to get a working gui. 002-xtra are extra apps included that are not essential. Without 002-xtra you will still get a working gui but without sound or aything else extra. As usual you can see the contents of each module in /mnt/live/memory/images/var/lib/pacman/local

Salutations...

Would this be more arch compliant and better than openrc? Saw that Void Linux using it.

Distributed??? Runit sounds like a winner... Let's throw OpenRC under the bus (@ least until it also has distributed capability... ).
I built a 1u rack2tower dual node cluster to use as a DAW to run Rezound and LMMS. Runit would make "it run" like a champion.
Runit
Jungle computing

Parallel service startup (optional, in development)

OpenRC parallelization??? Runit is DOING what OpenRC is still working on.
OpenRC

Best Regards...

@brokenman:
The kde-plasma edition is really good looking with the porteus logo for the kde panel and the feather as wallpaper.

Is there any change log for nemesis 3.5? What is expected from the testers?

Thanks francois. I really like the kde desktop too. It is a little heavier than kde4 but I feel it is nicer to work with. Since kde5 is still in beta you can start another thread for kde5 bugs from which I can send upstream bugs to the bugtracker and fix porteus specific bugs (or preferences) here. Thanks for testing.

An example of an upstream bug would be the baloo crash which is fairly consistent.