[thomas@localhost ~]$ rc-statusRunlevel: default dbus [ started ] consolekit [ started ] netmount [ stopped ] xdm [ started ] alsasound [ started ] acpid [ started ] local [ started ]Dynamic Runlevel: hotpluggedDynamic Runlevel: needed xdm-setup [ started ]Dynamic Runlevel: manualI (still) have to be root to get the network started so I made a script and autostarted it in xfce.

I converted my system to openrc earlier, and on one partition x started but network manager was giving me grief... the other partition x wouldn't start. I'm not sure what happend, but i'm gonna do a fresh install tomorrow and try again, hopefully give you guys some logs to look at if it doesn't work properly

For network manager maybe you need networkmanager-openrc if the networkmanager in the repos does not work out..

And I simply forgot to mention the instructions for installing from Artoo's repos..

Step 1) I clone the repository to my hard drive for easy access. I have a git directory in which I keep these git repos. The steps:

cd git-reposgit clone https://github.com/udeved/pkgbuilds.gitNow the repos have been cloned, I can get around to building packages. To update these repos, one has to do git pull to pull in the latest changes.

Step 2) Changing to required directory and making packages.Viking60 wanted scripts for salt, and Rudylorren wanted them for mpd, both of which can be found in the openrc-misc folder. So we change to it. Then we run makepkg -cs to build the packages.

cd pkgbuilds/openrc/openrc-miscmakepkg -csWith this step the packages should be created. To install all of them, one can do makepkg -i, and to install specific packages, one can do sudo pacman -U <package-path>

Plymouth is not supported by openrc, the best you can do is to disable 'splash' kernel boot parameter in your bootloader config.There is an experimental/unstable openrc-plugin for plymouth in gentoo portage tree, but I did not port it.

I feel I answered this already, did I? The split thread confused me here. :)

$ cpupower frequency-info analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 1.20 GHz - 2.60 GHz available frequency steps: 2.60 GHz, 2.00 GHz, 1.60 GHz, 1.20 GHz available cpufreq governors: ondemand, performance current policy: frequency should be within 1.20 GHz and 2.60 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 2.60 GHz. boost state support: Supported: no Active: no

Status: Configure and Testing

2) replacement for gvfs-mtp .. works as root

3) installed plymouth-git, bypasses plymouth splash screen; also need to configure lxdm and xfce4 to have boot and reboot GUI features currently hammering the command-line to reboot su <password> reboot

analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 1.20 GHz - 2.60 GHz available frequency steps: 2.60 GHz, 2.00 GHz, 1.60 GHz, 1.20 GHz available cpufreq governors: ondemand, performance current policy: frequency should be within 1.20 GHz and 2.60 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 2.60 GHz. boost state support: Supported: no Active: no

$ cpupower frequency-info analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 1.20 GHz - 2.60 GHz available frequency steps: 2.60 GHz, 2.00 GHz, 1.60 GHz, 1.20 GHz available cpufreq governors: ondemand, performance current policy: frequency should be within 1.20 GHz and 2.60 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 2.60 GHz. boost state support: Supported: no Active: no

Status: Configure and Testing

2) replacement for gvfs-mtp .. works as root

3) installed plymouth-git, bypasses plymouth splash screen; also need to configure lxdm and xfce4 to have boot and reboot GUI features currently hammering the command-line to reboot su <password> reboot

For these, you could install consolekit, lxdm-consolekit (https://aur.archlinux.org/packages/lxdm-consolekit/), and xfce4-session-consolekit (https://aur.archlinux.org/packages/xfce4-session-consolekit/).

Sorry, dont know much about cpupower.I had tried it once, and it had failed to start on my PC..All I can tell you is that there is a cpupower-openrc package, dont know whether you are using it ot not..

You can readup on the first one here (https://forum.manjaro.org/index.php?topic=14395.msg129107#msg129107).As usual report all issues (https://github.com/udeved/pkgbuilds/issues) you might have with this!

I think that it is so cool that excalibur has put all of this effort into creating a QT only Manjaro spin. In combination with the work that artoo, aaditya & Phil are doing in their efforts to create a systemd & gtk free Manjaro spin, Manjaro is looking like it is going to come up with an Arch based systemd & gtk free release that will end up attracting people from the allover the GNU/Linux distro world. :D

Well done to all concerned in this, it really is a milestone in the GNU/Linux world that I see all of your combined efforts creating. :D :D :D

On another positive note: moved to "eudev-openrc"My System uses 1% less memory, and World of Warcraft video improved by 7 - 10 fps.

Issue:How to get Thunar to auto-mount and show secondary HDD (/sdb1/Thing2).

aatoo openrc

I think I had to rebuild gvfs to get it to display my mounted partitions..I havent checked, but I think doing yaourt -S gvfs-nosystemd might work..Another way is building from artoo's packages (https://github.com/udeved/pkgbuilds/tree/master/desktop-eudev/gvfs-eudev).. (makepkg -cs, followed by sudo pacman -U <path-of-package-you-want-to-install>)(You may also need to reboot after installing built packages)

It is surprising that Systemd is heavily criticized and a potentially growing hairball that makes it an "accident waiting to happen", now will be used by every distro with 1,5 exceptions:Gentoo and Manjaro (the 0.5 part).

Ubuntu and Debian are caving in too (why?).

Does that make us Don Quijote and are we not fighting Windmills? Is not this "standardization" of Linux what everybody has been waitng for?(http://www.donquijote.cc/sitebuildercontent/sitebuilderpictures/DQWindmill.gif)In any case I have a lot of sympathy for Don Quijote and Sancho Panza and personally I have never lost a fight with a Windmill yet :)

Yes that makes sense. And we do like choices and flexibility. I have noticed that the chief penguin has swung his hammer too:http://www.phoronix.com/scan.php?page=news_item&px=MTY1MzAOnce this hits stable I am will put openRC on an old low spec box here that runs Manjaro openbox now - I am convinced it will be snappier with OpenRC

Testing it in a VM is probably not going to let me know if it's worth it or not. ;) In case things break is it easy enough to remove? Setting the init back to systemd is obviously the start of it, but will everything else uninstall without leaving cruft?

Written by Michael Larabel in systemd"Steven Rostedt ended up sending to the Linux kernel mailing list a patch that would hide the debug string from appearing in the kernel command-line as to hide it from systemd and reserve it just for kernel use. Steven wrote, "we OWN the kernel command line, and as such, we can keep the users from seeing stuff on it if we so choose. "What else will be hid from the "users"?

Is Manjaro thinking about dropping systemd and replacing it with openrc in the future?If so I will have to start looking for another distribution again. When Arch moved to systemd from openrc is when I actually starting to consider using it, I had no desire to even try it before that, I have no intention on using something that moves backwards.

Testing it in a VM is probably not going to let me know if it's worth it or not. ;) In case things break is it easy enough to remove? Setting the init back to systemd is obviously the start of it, but will everything else uninstall without leaving cruft?

Yes, I think so :)Though I have tried it in various VMs too to see how things work..

sudo pacman -R systemd-sysvcomaptsudo pacman -S sysvinitsudo pacman -S openrc-basesudo pacman -S displaymanager-openrcsudo pacman -S alsa-utils-openrcAt this point you have not removed apart from systemd-sysvcompat, which are just a bunch of symlinks..However if you also want to install networkmanager-openrc, that would require consolekit, which replaces the polkit in the repos with its own.

To go back to systemd, use the init=/usr/lib/systemd/systemd method, or just install systemd-sysvcompat..The wiki lists some of this: https://wiki.manjaro.org/index.php?title=Openrc

Is Manjaro thinking about dropping systemd and replacing it with openrc in the future?If so I will have to start looking for another distribution again. When Arch moved to systemd from openrc is when I actually starting to consider using it, I had no desire to even try it before that, I have no intention on using something that moves backwards.

The reason I do openrc for arch based systems, I have a problem with a functionalitiy absorbing ever growing very complex "init", which develops steadily kernel like features.

The day, systemd tries to replace the linux kernel will be the official death of linux. Atm linux is dying a slow death, caused by an all out attack on the very principle of open source, gnu linux.

You get with systemd a lindows, components which used to be modular and could be replaced, are all absorbed into systemd source. At some point, nobody will understand systemd source any more, because it also pulls in a huge amount of forced dependencies. So the systemd source is only a fraction of the real code base it uses.

Take logind, no bad idea to replace consolekit, but since systemd version 206, logind requires a running systemd voodoo.

Oh good, I was not looking forward to having to find another distribution that works for me again. I guess I could always just move to the Netrunner Standard version, but I like the Rolling Version so much more, not to mention that I never cared for anything Ubuntu or Debian based, LOL

However if you also want to install networkmanager-openrc, that would require consolekit, which replaces the polkit in the repos with its own.

Looks like networkmanager-openrc needs dbus-openrc... this is getting a little more complicated. :D

I haven't had this much fun for a while. :D

Edit:And without network access I have to use USB. And with a recent update when inserting a USB flash drive nothing happens (it does not show up at all, not in a file manager, not in lsusb, not in dmesg). :D

Edit 2:OK, so I plugged in an ethernet cable and started dhcpcd, that gave me network access again. Phew!

Edit 3:I think I have NetworkManager running. ZFS does not start correctly on boot, though, and there doesn't seem to be an init script for tor...

Edit 4:OK, so it looks promising but it's not quite there for me yet. Some things definitely load quicker (e.g. Chrome).

Just to check I could, I went back to systemd. Not very complicated to reverse, but I did have to allow removal of a load of extra packages and reinstall them (e.g. ufw, gufw, networkmanager, network-manager-applet).

Just to check I could, I went back to systemd. Not very complicated to reverse, but I did have to allow removal of a load of extra packages and reinstall them (e.g. ufw, gufw, networkmanager, network-manager-applet).

For the less advanced users who are not going to learn much by looking at code, can you please elaborate on this? I keep seeing such vagaries as your comment here and yet no one seems to say anything more detailed. What is it that is nefarious in systemd and who exactly is behind it?

@pokerface, this is a technical thread on discussing how to use OpenRC, not about discussing systemd vs OpenRC.

If you want, you can open a new thread about it in the Discussion section, and I will move your post(s) there.

However I think you are just trolling as you make statements like:

Fine i am sorry, i thought its good place (there is also topic "development talk" soo). I just read this: http://boycottsystemd.org. But can you explain me what are advantages of OpenRC for me, normal user? And no, this is not "troll" question, i am very serious.

I personally switched to OpenRC (from a user's point of view), becuase systemd was increasingly adding more and more services to autostart (an example being the mandb.service (https://forum.manjaro.org/index.php?topic=13943.0)), which I didnt know how to disable, and it using binary logs instead of text logs (so I cant view it from another system), and not being able to understand its messages (a couple of times some services failed, and it adviced me to use systemctl and journalctl to find out the issue, but I could not find any useful information from them).

Another is the huge size of the logs (https://forum.manjaro.org/index.php?topic=7087.0) it creates, most of which were worthless to me, and had to be manually removed.

There are many other reasons (both practical and philosophical in nature), which are highlighted in http://boycottsystemd.org/ and the articles that it mentions.

5) For networking, dhcpcd is enabled by default; however if it does not work for you try the networkmanager-openrc package.(If the networkmanager-openrc from the AB repos doesnt work for you and conlicts with existing packages, try out networkmanager-openrc from the AUR.)After that, I restart my laptop and all fine..when I try shut down or restart my laptop again, I got only welcome screen to logon..and when I put this :

Quote

systemctl list-unitsFailed to get D-Bus connection: Unknown error -1

How I know that I install fine this and all working ? thanks..I really don't know about this openrc but i'll try learn :)

P.S when I go to Update manager , I got message that Authentication failed :-\

I only have problems with this :when I try shut down or restart my laptop , I got only welcome screen to logon..and when I put this : systemctl list-unitsgot : Failed to get D-Bus connection: Unknown error -1andwhen I go to Update manager , I got message that Authentication failed :-\

I only have problems with this :when I try shut down or restart my laptop , I got only welcome screen to logon..and when I put this : systemctl list-unitsgot : Failed to get D-Bus connection: Unknown error -1andwhen I go to Update manager , I got message that Authentication failed :-\

systemctl is systemd specific, it doesn't exist on openrc install with eudev.

You need to install this package:https://aur.archlinux.org/packages/xfce4-session-consolekit/

Besides the package Artoo mentioned, I think you would also require consolekit-openrc, and a display manager that supports consolekit, for example, lxdm-consolekit (https://aur.archlinux.org/packages/lxdm-consolekit/)

Some wiki info:https://wiki.manjaro.org/index.php?title=Openrc#Consolekithttps://wiki.manjaro.org/index.php?title=OpenRC,_an_alternative_to_systemd#Using_Consolekithttps://wiki.manjaro.org/index.php?title=OpenRC,_an_alternative_to_systemd#Display_Manager

sudo pacman -S consolekit-openrcAfter that, on rebooting, and logging in, if the commandck-list-sessionsreturns output, I guess a ck-session was started..Besides if you are using Xfce, I guess xfce4-session-consolekit is also needed, and can be installed with:

Maybe you could follow schpankme's lead (and edit /etc/conf.d/xdm) to install and configure lxdm-consolekit.Some info in the wiki also (https://wiki.manjaro.org/index.php?title=Openrc#Display_Manager).

I just wanted to say a quick thanks, for all the obvious hard work to ALL those (a special thanks to R2 - and you know who I mean), for keeping a free init's, a free choice, be it OpenRC, andor rc/bsd-inits,..., without systemd, within Arch Linux. And also Manjaro, for the new home, that you gave an (Arch)Manjaro/OpenRC, a fruittfull chance to exist.seriously though, Carry On, my wayward sons !-you got my vote.;)

Gentoo and Funtoo both recommend "readahead" for performance improvement. Is the third party attachment something that keeps us from having this readahead or supporting?

No, but I don't want it in my pkgbuild.If you want to submit the build to AUR and maintain it, say so, you can have it. :)Its just not good if eg readahead-openrc is in manjaro repo, but the readahead depend is only on AUR.

You may ask for inclusion of readahead for community, but I definitely don't want to maintain it. I am busy with the ones I have. ;)

That is a problem with packages in the "manjaro repo with depend's on AUR".My thoughts were that someone was already maintaining "readahead", and that we had access to it.

I've been an IT Infrastructures manager for 25+ years, this actual development piece is new to me. Is there any documentation that could teach/show me the basics of, How To: "build and submit the build to AUR"? :-X

That is a problem with packages in the "manjaro repo with depend's on AUR".My thoughts were that someone was already maintaining "readahead", and that we had access to it.

I've been an IT Infrastructures manager for 25+ years, this actual development piece is new to me. Is there any documentation that could teach/show me the basics of, How To: "build and submit the build to AUR"? :-X

The wiki has this documented :)https://wiki.manjaro.org/index.php?title=Openrc#Installation

Dont you also get all the other packages as documented by the wiki?

I read and followed the wiki but I didn't get any other packages that the ones I listed with the first command. I can see that the wiki lists some things like alsa and the sudo pacman -S openrc-desktop wants to install some stuff but this isn't replacing what I have already (I don't have a display manager and it is not asking me to install mpd). I apologise if I am missing something that I should have noticed with this but I can see any way to replace what needs to be replaced other than blindly installing things and hoping everything is covered.

I read and followed the wiki but I didn't get any other packages that the ones I listed with the first command. I can see that the wiki lists some things like alsa and the sudo pacman -S openrc-desktop wants to install some stuff but this isn't replacing what I have already (I don't have a display manager and it is not asking me to install mpd). I apologise if I am missing something that I should have noticed with this but I can see any way to replace what needs to be replaced other than blindly installing things and hoping everything is covered.

Ok, as (all) the packages are not being automatically installed, you could install them manually (will report this issue to artoo):

sudo pacman -S openrc-core cronie-openrc cryptsetup-openrc dbus-openrc device-mapper-openrc dhcpcd-openrc glibc-openrc inetutils-openrc lvm2-openrc mdadm-openrcOpenRC is just an init system, and you are not removing systemd, so no packages are being replaced yet :)Even if you install eudev (for replacing systemd), Artoo has made the packages in such a way that minimal packages need to be replaced :)

If you follow the wiki step by step, and see the output of each step, maybe you can understand the steps better ;)

If you follow the wiki step by step, and see the output of each step, maybe you can understand the steps better ;)

I did read through the wiki but the first step was different quite a lot from what the wiki was saying should happen so I didn't want to go too far without some clarification.

I have booted in to it now and everything seems to be working except for rtorrent and rutorrent. I did install lighttpd-openrc but I think I just need to start the right things with openrc rather than systemctl, I'll have a look in to it tomorrow.

Many thanks for the help, for the packages work and for posting here in the first place, I'm very grateful to be made aware of the dire need to be at least wary of systemd.

I did read through the wiki but the first step was different quite a lot from what the wiki was saying should happen so I didn't want to go too far without some clarification.

I have booted in to it now and everything seems to be working except for rtorrent and rutorrent. I did install lighttpd-openrc but I think I just need to start the right things with openrc rather than systemctl, I'll have a look in to it tomorrow.

Many thanks for the help, for the packages work and for posting here in the first place, I'm very grateful to be made aware of the dire need to be at least wary of systemd.

Thanks for your input too :)My role here is mainly of a tester and documentation writer, its artoo who provides the packages :)

For starting or enabling services, you can find the documentation also ;)https://wiki.manjaro.org/index.php?title=Openrc#Configuration

However, after doing all that, I remembered from the forum,it was mentioned to change to unstable repo, which I did not do,and still on stable. Seems to have had a serious effect, since I'm not able to connect to ethernet.

It boots into OpenRC just fine; however,not being able to get to internet prevents continuing.

My question is, how to get internet connection working again? without having to reinstall, if at all possible? Not a big deal, just would rather not. :)

sudo rc-update add alsasound defaultTry resinatalling package in the terminal. So you will see a list of thing that looks something like kinda like this "==> Run 'rc-update add dhcpcd default' "And you don't need to be in unstable to used openrc. Since the new update. Openrc can be used in stable. https://forum.manjaro.org/index.php?topic=15003.0

The Wikia does need to be update a little bit. Thing like displaymanager can run as they are or the must be consolekit version only.

sudo pacman -S openrc-core cronie-openrc cryptsetup-openrc dbus-openrc device-mapper-openrc dhcpcd-openrc glibc-openrc inetutils-openrc lvm2-openrc mdadm-openrcAdded this note in the wiki as well. After this step you can follow the wiki for installing the additional packages; note that plymouth can fail untill you also setup a graphical display manager.

Thx for reporting. Bitleebee-openrc package will have a syslog depend.

You need to install a syslogger.eg syslog-ng-openrc or rsyslog-openrc or metalog-openrc.

bitlbee service should autostart syslog

Thanks, that fixed it. I think I just have two other issue I'm trying to fix (or three but I haven't tried the things in the wiki for the reboot/hibernate/suspend things yet).

mpd starts ok but it is not seeing any of my library or configs.

Also, how can I create a service to start with arguments? I want to set 'tmux new -s rtorrent -d rtorrent' to start but I can't see a way to do this. I could add it to my .Xinitrc but I've always used systemctl for this.

Thanks, that fixed it. I think I just have two other issue I'm trying to fix (or three but I haven't tried the things in the wiki for the reboot/hibernate/suspend things yet).

mpd starts ok but it is not seeing any of my library or configs.

Also, how can I create a service to start with arguments? I want to set 'tmux new -s rtorrent -d rtorrent' to start but I can't see a way to do this. I could add it to my .Xinitrc but I've always used systemctl for this.

Hi spectromas, I searched for it and found a link:http://www.calculate-linux.org/main/en/rc-service

Also, how can I create a service to start with arguments? I want to set 'tmux new -s rtorrent -d rtorrent' to start but I can't see a way to do this. I could add it to my .Xinitrc but I've always used systemctl for this.

Could I get some help with logging out, shutdown and suspend/hibernate? I see in the wiki it says I need to have consolekit to shutdown as a non-root user but it must not be set up or working properly for me because I still need to be root to do this.

I usually use oblogout inside Awesome to logout/suspend/reboot/shutdown but suspend and hibernate are not working at all and shutdown require root (and does nothing from oblogout, I have to do it from a terminal).

I usually use oblogout inside Awesome to logout/suspend/reboot/shutdown but suspend and hibernate are not working at all and shutdown require root (and does nothing from oblogout, I have to do it from a terminal).

You can try to install upower-pm-utils and see if that helps.

I will check lighttpd, but my guess is, it crashes due to some misconfiguration.

Edit: to explain quickly

upower had its pm-utils suppoort removed upstream, so this version depends on running systemd for suspend/hiberante.

I think there is no way around to install upower-pm-utils, ie you need eudev.

Could I get some help with logging out, shutdown and suspend/hibernate? I see in the wiki it says I need to have consolekit to shutdown as a non-root user but it must not be set up or working properly for me because I still need to be root to do this.

Could I get some help with logging out, shutdown and suspend/hibernate? I see in the wiki it says I need to have consolekit to shutdown as a non-root user but it must not be set up or working properly for me because I still need to be root to do this.

I usually use oblogout inside Awesome to logout/suspend/reboot/shutdown but suspend and hibernate are not working at all and shutdown require root (and does nothing from oblogout, I have to do it from a terminal).

Added a oblogout-consolekit (https://aur.archlinux.org/packages/oblogout-consolekit/) package in the AUR.

I've noticed that there's no reason to have both "lxpolkit" and "polkit-consolekit" installed. On my minimal Xfce/i3 build, "polkit-consolekit" works great.

Hi schpankme,

As far as I understand, polkit-consolekit is a system level component (like polkit which it replaced), while lxpolkit is a user level component.

Hence lxpolkit is added to my startup programs in Xfce or {Open,Flux}box.What it does is that when I try to mount my unmounted partitions it asks me for a password; without it I simply get "Authentication failed".

1. Any idea where i can read description of services (taken from rc-services --list)?2. Can i check somehow if i got some leftovers from systemd and related packages/functionality?3. Is it safe to do sudo pacman -Rns lib32-systemd? Says "lib32-mesa: requires lib32-systemd".this grows up to

1. Any idea where i can read description of services (taken from rc-services --list)?2. Can i check somehow if i got some leftovers from systemd and related packages/functionality?3. Is it safe to do sudo pacman -Rns lib32-systemd? Says "lib32-mesa: requires lib32-systemd".this grows up to

1. I dont know if it can be done directly, but you could try the command pacman -Qs openrc to get details about installed openrc packages.

2. You could try pacman -Qs systemd to see if you have any systemd related package. Note that nowadays systemd is quite integrated with a lot of stuff, and the current combo of eudev-systemdcompat and eudev tries to reduce the conflicts to a minimum.

3. I think that lib32-systemd and other 32 bit libraries are part of multilib, ie to run 32 bit apps on 64 bit, so if you removed them, you could probably not run graphical 32 bit apps, like games or wine (for windows apps). If you dont do gaming or run wine you could probably remove them.

With the Manjaro switch to Xorg-1.16 (https://forum.manjaro.org/index.php?topic=16650.0), I guess we will need to deal with Arch making X rootless with systemd (https://www.archlinux.org/news/xorg-server-116-is-now-available/).

Quote from: Arch Linux

X is now rootless with the help of systemd-logind, this also means that it must be launched from the same virtual terminal as was used to log in, redirecting stderr also breaks rootless login. The old root execution behavior can be restored through the Xorg.wrap config file (man xorg.wrap). Please note that launching X through a login-manager (gdm, kdm, ...) doesn't yet provide rootless access.

The workaround (https://bbs.archlinux.org/viewtopic.php?pid=1441150#p1441150) that can be used is:

Quote from: Lone_Wolf

The recent upgrade to Xorg 1.16.0 will break X for those of us using openrc with OSS videodrivers.

The reason for this is the new Xorg.wrap command, it checks if the videodriver supports KMS.If it does, then Xorg.wrap tries to start X without root rights using logind .

As logind only functions if the system is booted with systemd as PID 1, Xorg.wrap can't start X without root rights and fails.

The solution is to CREATE an /etc/X11/Xwrapper.config file with contents like this :

With Artoo's help in updating devtools (https://github.com/udeved/devtools) and build scripts (https://github.com/udeved/pkgbuilds), I managed to enhance my pacman repo (https://forum.manjaro.org/index.php?topic=14619.msg152613#msg152613) with all the the latest packages from github (https://github.com/udeved/pkgbuilds) :)

To get the packages available in this repo, add the following to /etc/pacman.conf (at the end)

[openrc-eudev]SigLevel = Optional TrustAllServer = http://downloads.sourceforge.net/project/mefiles/Manjaro/$repo/$archAs it is a signed package repo, maybe you will need to add my signature to pacman's conf with

sudo pacman -S openrc-eudev/eudev openrc-eudev/eudev-systemdcompatNote that there could be bugs involved with running the latest packages, so for maximum stability, only the packages from the Manjaro repos can be used.To downgrade to the packages from the Manjaro repos, use:

I'm still scratching my head on this one; both eudev-openrc and eudev-systemdcompat were updated, but running the command again downgraded them; then eudev was updated; now we have updated eudev-openrc and eudev-systemdcompat.

I'm still scratching my head on this one; both eudev-openrc and eudev-systemdcompat were updated, but running the command again downgraded them; then eudev was updated; now we have updated eudev-openrc and eudev-systemdcompat.

:o

Haha, it was just a shot in the dark ;)Software can be confusing sometimes..

If people find adding the repo path to package confusing, you can also rank the repos in pacman.conf differently.

Since systemd is in base group, and core repo & the community repo on top, it pacman will prefer core repo for udev provider.If you put say aaditya's repo on top, before core & community repo, additya's packages will be preferred without the repo path.

So eudev-1.10 will overlay eudev-1.9 from community repo as well as systemd from core repo.

keyboardctl is being shown as crashed as it exits after executing; its startup script has been changed accordingly to fix this issue.For getting the new version, you could add the repo (https://forum.manjaro.org/index.php?topic=14080.msg157380#msg157380) I mentioned earlier in this thread (page 11), and run:

sudo pacman -S openrc-eudev/keyboardctl-openrcAnother alternative is to build a package yourself using artoo's git repo (https://github.com/udeved/pkgbuilds/tree/master/keyboardctl-openrc).Yet another option is to simply disable keyboardctl if you dont use it ;) (for example, you use standard en-US keyboard layout)

For networkmanager also, you could try adding the repo I mentioned and update it, ie:

sudo rc-service networkmanager stop # stop nm servicesudo rc-update del networkmanager # remove nm service from startupBut if you need wifi, then you could try switching to wicd and see if it works for you (this is what I did when networkmanager was not working for me):

I successfully swapped to OpenRC and Eudev 2, 3 months ago on my Arch. I'm mentioning it here because I got the idea from and followed the instructions in this thread (and the Arch wiki). So I thought I'd thank you all for the vital instructions and add a success to the log :). Networking using dhcpcd-openrc was easy to set up, so far the installation hasn't had any problems with any system upgrades and nothing to complain about at all. I hope this is not considered spam even though it's not 100% Manjaro related :-\.

I successfully swapped to OpenRC and Eudev 2, 3 months ago on my Arch. I'm mentioning it here because I got the idea from and followed the instructions in this thread (and the Arch wiki). So I thought I'd thank you all for the vital instructions and add a success to the log :). Networking using dhcpcd-openrc was easy to set up, so far the installation hasn't had any problems with any system upgrades and nothing to complain about at all. I hope this is not considered spam even though it's not 100% Manjaro related :-\.

System is really booting OpenRC:(http://i.imgur.com/sbWnthps.jpg) (http://i.imgur.com/sbWnthps)

Thanks for the report :)I also have a similar setup, except for using wicd and not using lvm.

I noticed that you have some older versions of packages, you could add my repo mentioned in this post (https://forum.manjaro.org/index.php?topic=14080.msg157380#msg157380) to keep upto date if you prefer :)

On a side note: I noticed earlier today that power buttons weren't working in the LightDM greeter that I have installed. I hadn't noticed earlier because I usually shutdown manually via the terminal. After some poking around I discovered that I needed to have consolekit-openrc installed. I was unable to install with Yaourt because its dependency, consolekit was failing to install. So I tried to build and install consolekit-openrc without Yaourt, but that failed too. I had a look at the consolekit-openrc build log and it said that -ludev couldn't be found. "pacman -Qs udev" did report libeudev as installed.

After some internet digging I found a forum post that explained to me. For some reason the file /usr/lib/libudev.so didn't exist, but the other eudev lib files did. According to the post it's a terrible, terrible idea to fix it by symlinking the libudev.so, so I did it anyway :D. Consolekit and consolekit-openrc are now installed and power buttons in the greeter work. Perhaps until the next time I update..

Anyway, the point is: I don't know whether this eudev issue is specific to Arch, or whether Manjaro is affected by it as well, or whether I messed something up when I installed eudev in the first place.

Came back to OpenRC after a while. Still sticking on ZFS. I created an /etc/init.d/zfs based on this one for Gentoo: https://raw.githubusercontent.com/zfsonlinux/zfs/master/etc/init.d/zfs.gentoo.in (just changing @sbindir@ to /usr/bin). I added it with 'rc-update add zfs default' but it doesn't show in rc-status and doesn't start on boot (and so ZFS pools don't mount); running it manually with 'rc-service zfs start' gets it working though... :S

Came back to OpenRC after a while. Still sticking on ZFS. I created an /etc/init.d/zfs based on this one for Gentoo: https://raw.githubusercontent.com/zfsonlinux/zfs/master/etc/init.d/zfs.gentoo.in (just changing @sbindir@ to /usr/bin). I added it with 'rc-update add zfs default' but it doesn't show in rc-status and doesn't start on boot (and so ZFS pools don't mount); running it manually with 'rc-service zfs start' gets it working though... :S

On a side note: I noticed earlier today that power buttons weren't working in the LightDM greeter that I have installed. I hadn't noticed earlier because I usually shutdown manually via the terminal. After some poking around I discovered that I needed to have consolekit-openrc installed. I was unable to install with Yaourt because its dependency, consolekit was failing to install. So I tried to build and install consolekit-openrc without Yaourt, but that failed too. I had a look at the consolekit-openrc build log and it said that -ludev couldn't be found. "pacman -Qs udev" did report libeudev as installed.

After some internet digging I found a forum post that explained to me. For some reason the file /usr/lib/libudev.so didn't exist, but the other eudev lib files did. According to the post it's a terrible, terrible idea to fix it by symlinking the libudev.so, so I did it anyway :D. Consolekit and consolekit-openrc are now installed and power buttons in the greeter work. Perhaps until the next time I update..

Anyway, the point is: I don't know whether this eudev issue is specific to Arch, or whether Manjaro is affected by it as well, or whether I messed something up when I installed eudev in the first place.

Yeah, I think maybe it got messed up somewhere, as there were probably many changes to packages since when they were conceived. I would suggest updating to the pacman repo linked earlier :)

modules="vboxdrv"modules="vboxnetadp"modules="vboxnetflt"modules="vboxpci"modules="snd-pcm-oss"modules="snd-mixer-oss"modules="fuse"The only one that loads is "fuse". I can load the others manually without a hitch.

Second, still getting the following errors at boot even though they are commented out:

* setting up tmpfiles.d entries ...tmpfiles: ignoring invalid entry on line 12 of `/usr/lib/tmpfiles.d//etc.conf'tmpfiles: ignoring invalid entry on line 14 of `/usr/lib/tmpfiles.d//etc.conf'tmpfiles: ignoring invalid entry on line 15 of `/usr/lib/tmpfiles.d//etc.conf'tmpfiles: ignoring invalid entry on line 33 of `/usr/lib/tmpfiles.d//legacy.conf'tmpfiles: ignoring invalid entry on line 34 of `/usr/lib/tmpfiles.d//legacy.conf'tmpfiles: ignoring invalid entry on line 35 of `/usr/lib/tmpfiles.d//legacy.conf'tmpfiles: ignoring invalid entry on line 11 of `/usr/lib/tmpfiles.d//systemd-nologin.conf'tmpfiles: ignoring invalid entry on line 18 of `/usr/lib/tmpfiles.d//x11.conf' [ !! ]Isn't really a big deal. More of an anoyance than anything else. Would prefer not to have them listed at boot time or in the logs.

Not sure where to go from here considering I am very new to Openrc.

Other than these 2 issues everything seems to be running just fine.

Also, right now systemd is still installed but was thinking about going with eudev. Using Xfce and will not touch Gnome or Kde. Could someone be kind enough to tell me what drawbacks I might have to face?

Thanks for all the work you guys put into this. Just can't stand the logic behind systemd.

modules="vboxdrv"modules="vboxnetadp"modules="vboxnetflt"modules="vboxpci"modules="snd-pcm-oss"modules="snd-mixer-oss"modules="fuse"The only one that loads is "fuse". I can load the others manually without a hitch.

Second, still getting the following errors at boot even though they are commented out:

* setting up tmpfiles.d entries ...tmpfiles: ignoring invalid entry on line 12 of `/usr/lib/tmpfiles.d//etc.conf'tmpfiles: ignoring invalid entry on line 14 of `/usr/lib/tmpfiles.d//etc.conf'tmpfiles: ignoring invalid entry on line 15 of `/usr/lib/tmpfiles.d//etc.conf'tmpfiles: ignoring invalid entry on line 33 of `/usr/lib/tmpfiles.d//legacy.conf'tmpfiles: ignoring invalid entry on line 34 of `/usr/lib/tmpfiles.d//legacy.conf'tmpfiles: ignoring invalid entry on line 35 of `/usr/lib/tmpfiles.d//legacy.conf'tmpfiles: ignoring invalid entry on line 11 of `/usr/lib/tmpfiles.d//systemd-nologin.conf'tmpfiles: ignoring invalid entry on line 18 of `/usr/lib/tmpfiles.d//x11.conf' [ !! ]Isn't really a big deal. More of an anoyance than anything else. Would prefer not to have them listed at boot time or in the logs.

Not sure where to go from here considering I am very new to Openrc.

Other than these 2 issues everything seems to be running just fine.

Also, right now systemd is still installed but was thinking about going with eudev. Using Xfce and will not touch Gnome or Kde. Could someone be kind enough to tell me what drawbacks I might have to face?

Thanks for all the work you guys put into this. Just can't stand the logic behind systemd.

Also, right now systemd is still installed but was thinking about going with eudev. Using Xfce and will not touch Gnome or Kde. Could someone be kind enough to tell me what drawbacks I might have to face?

None, and it will probably stay this way once a standalone logind project takes shape.Only gnome will not be usable currently, since gnome hard depends on systemd's logind.Its impossible to extarct logind from systemd source and make it run without systemd, so we temporarily go with old consolekit, the precursor of logind.

Edit: you also can't use gnome with openrc & systemd, gnome requires a running systemd.

This thing has been so stable and fast that I got bored.I left systemd but tried to break it with installing eudev. Replaced systemd and rebooted. And...everything works!

I run Openbox and Pekwm on it.

The first boot after removing systemd was very slow though. On the second boot it was fast again (but I could not notice any boot speed improvement in comparison to systemd - it seemed just as blistering fast).

The one thing that does not work is logout in Oblogout - restart and shutdown works fine. So I thought I should install upower-pm-utils to get the hibernating etc going.And got an internal conflict with upower (and would I like to remove it). I thought upower-pm-utils was an alternative dependency of upower?

Edit:I replaced upower and did not notice much difference so I installed upower again and removed the pm-utils.Everything works just fine except the logout in Oblogout....And that is not surprising since /etc/oblogout.conf has

I replaced upower and did not notice much difference so I installed upower again and removed the pm-utils.Everything works just fine except the logout in Oblogout....And that is not surprising since /etc/oblogout.conf has

openbox --exit which does not work all that well in Pekwm ^-^ Works well in Openbox though :)

A quick explanation for upower-pm-utils.

upower had upstream pm-utils support removed with 0.99, and it relies on systemd to suspend and hibernate afaik.You should check this, you may encounter problems with upower and eudev and not properly working power-management.

Thanks !I take it that those problems will not occur in upower-pm-utils then?As I said; I did not notice much difference so it is just a question of which one to choose.(upower-pm-utils if I understand you correctly - since systemd is gone).

I have now installed OpenRC and eudev on real hardware rather than in a virtual machine, and predictably ran into a small problem. I have an Optimus (Intel+Nvidia) laptop which is hardwired to go through the Intel HD4k. Bumblebee worked fine under systemd as expected, but I was unable to find a version of it that would work with OpenRC, apart from one mention of bumblebee-openrc on Google where the link 404'd. Any ideas?

I have now installed OpenRC and eudev on real hardware rather than in a virtual machine, and predictably ran into a small problem. I have an Optimus (Intel+Nvidia) laptop which is hardwired to go through the Intel HD4k. Bumblebee worked fine under systemd as expected, but I was unable to find a version of it that would work with OpenRC, apart from one mention of bumblebee-openrc on Google where the link 404'd. Any ideas?

I can provide bumblebee script, its just nobody has asked for it yet. :)

If there's just me looking for it, I'd say don't use your time for it :P. This is nothing more than an off-the-cuff experiment for me, and I'd hate to use up someone's time when they could be concentrating on more important things.. :)

If there's just me looking for it, I'd say don't use your time for it :P. This is nothing more than an off-the-cuff experiment for me, and I'd hate to use up someone's time when they could be concentrating on more important things.. :)

Oh, no problem, the builds already exist, I just haven't put them in repo.

Currently I don't have systemd installed at all, both the vm and hardware are on OpenRC+eudev. I did check that 'optirun glxgears' did work on the hardware one before replacing systemd, that should be proof enough that Bumblebee really was working. I suppose I could reinstall systemd to find check for the pid file :-\

Do you have bublebee running on systemd?If yes, does it produce a pid file in /run or /run/bumblebee?

I re-installed from scratch to get a clean systemd system. 'optirun glxgears -info' showed that the GL_RENDERER was Nvidia. There was no /run/bumblebee, no pid file in /run. The only bumblebee related thing in /run was bumblebee.socket.

Quote

bumblebee not bublebeed, reminds me to fix this.

Services added successfully. nvidia-smi is still descibed as nvidia-smid in the 'run =>' install output.

I re-installed from scratch to get a clean systemd system. 'optirun glxgears -info' showed that the GL_RENDERER was Nvidia. There was no /run/bumblebee, no pid file in /run. The only bumblebee related thing in /run was bumblebee.socket.Services added successfully. nvidia-smi is still descibed as nvidia-smid in the 'run =>' install output.

I must confess I'm confused. VirtualGL getting stuck prevents all services after it from being started at all, even ftpd which has nothing to do with graphics. It would make sense to me that no changes to the way bumblebee is compiled can fix it since bumblebee is never reached in the first place.

Anyway. I downloaded the files from https://projects.archlinux.org/svntogit/community.git/tree/trunk?h=packages/bumblebee, installed the necessary dependencies, edited the PKGBUILD to use the pid. Compiled, reinstalled bumblebee without first removing it and then rebooted. No change, no services after and including VirtualGL are started.

One thing I noticed is that while starting bumblebeed from a root account works, using sudo from a non-root account does not. The process launches, but I don't have the privileges to use it. The non-root account is in the bumblebee group.

Since bumblebee appears to work when not launched during init, it makes me feel as if the problem is VirtualGL, not bumblebee.

Edit: However, then I thought to myself: if bumblebee requires VirtualGL, how can it work if VGL never started? The answer is that it did start, but never "returned" to resume the rest of the init process.

Found a Logitech Receiver (/dev/hidraw0), but did not have permission to open it.

If you've just installed Solaar, try removing the receiver and plugging it back in.Which I did do and got the same message again. Any thoughts? My keyboard and mouse are working, it's just that Solaar cannot manage the Unifying Receiver now.

Found a Logitech Receiver (/dev/hidraw0), but did not have permission to open it.

If you've just installed Solaar, try removing the receiver and plugging it back in.Which I did do and got the same message again. Any thoughts? My keyboard and mouse are working, it's just that Solaar cannot manage the Unifying Receiver now.

The aur build wants user in uaccess group.If that not works, you can also try to cretae a plugdev group.This is just from looking at source of solaar.

Found a Logitech Receiver (/dev/hidraw0), but did not have permission to open it.

If you've just installed Solaar, try removing the receiver and plugging it back in.Which I did do and got the same message again. Any thoughts? My keyboard and mouse are working, it's just that Solaar cannot manage the Unifying Receiver now.

Hi,

Did you follow the steps here..https://pwr.github.io/Solaar/installation.html

Did you follow the steps here..https://pwr.github.io/Solaar/installation.html

No, I hadn't because when I installed Solaar everything worked without a problem. But since you posted this link, I have done everything the instructions say to do manually. Nothing changed except the udev rules file was 42-* and I renamed it to 99-* which hasn't helped. I wasn't part of the plugdev group before yesterday but I added myself via KUser and am not sure what else to try as it is still acting the same. I even changed the GROUP="my_username" as the instructions suggested...

No, I hadn't because when I installed Solaar everything worked without a problem. But since you posted this link, I have done everything the instructions say to do manually. Nothing changed except the udev rules file was 42-* and I renamed it to 99-* which hasn't helped. I wasn't part of the plugdev group before yesterday but I added myself via KUser and am not sure what else to try as it is still acting the same. I even changed the GROUP="my_username" as the instructions suggested...

Hi,

First of all, GROUP="my_username" means GROUP="urbanomad64"

Let me list some points-

Quote

You should have a reasonably new kernel (3.2+), with the logitech-djreceiver driver enabled and loaded

To check if this module is loaded, type lsmod | grep logitech-djreceiverIf there is no output, you could try to load this module with sudo modprobe logitech-djreceiverAfter that try unplugging and plugging your device.

To check if this module is loaded, type lsmod | grep logitech-djreceiverIf there is no output, you could try to load this module with sudo modprobe logitech-djreceiverAfter that try unplugging and plugging your device.

Thank you for your reply again... so, it seems as per this http://www.gossamer-threads.com/lists/linux/kernel/1992882 (http://www.gossamer-threads.com/lists/linux/kernel/1992882) that the module name has changed to hid-logitech-dj in Kernel 3.17 and I have just started in Kernel 3.16 and it is also called the same... could this have something to do with my problem?

Thank you for your reply again... so, it seems as per this http://www.gossamer-threads.com/lists/linux/kernel/1992882 (http://www.gossamer-threads.com/lists/linux/kernel/1992882) that the module name has changed to hid-logitech-dj in Kernel 3.17 and I have just started in Kernel 3.16 and it is also called the same... could this have something to do with my problem?

modinfo -n hid-logitech-djmodinfo -n logitech-djreceiverPoint is, the driver/module should be loaded for it to work correctly.systemd takes modules to load at startup from /etc/modules-load.d/<module-name>, while OpenRC accepts a list of modules specified in /etc/conf.d/modules

modinfo -n hid-logitech-djmodinfo -n logitech-djreceiverPoint is, the driver/module should be loaded for it to work correctly.systemd takes modules to load at startup from /etc/modules-load.d/<module-name>, while OpenRC accepts a list of modules specified in /etc/conf.d/modules

We must have crossed posts as I just updated my previous post with the output of dmesg but these are the ouputs you've requested.

I'm sorry to interupt. I am so happy to find this manjaro iso with openbox and openrc. This has all but saved Linux for me and I am an old time user not at affraid of get into the guts of things. But before I write my own scripts, I would like to ask if these is a stock script for cups and sshd and to run them in openrc

There is no setup and administration tool kit with Manjaro that I can see.

I also have a comment about the wifi and NetoworkManager discussions I see sprinkled in this thread... look guys, You really really don't need it and its wifi control is buggy and unreliable compared to wicd. I was SO glad to have found it with the fustrating failures of nm-applet oye.

I'm sorry to interupt. I am so happy to find this manjaro iso with openbox and openrc. This has all but saved Linux for me and I am an old time user not at affraid of get into the guts of things. But before I write my own scripts, I would like to ask if these is a stock script for cups and sshd and to run them in openrc

There is no setup and administration tool kit with Manjaro that I can see.

I also have a comment about the wifi and NetoworkManager discussions I see sprinkled in this thread... look guys, You really really don't need it and its wifi control is buggy and unreliable compared to wicd. I was SO glad to have found it with the fustrating failures of nm-applet oye.

Ruben

Hi Ruben,

No problem ;)For cups there is cups-openrc package, and for ssh there is openssh-openrc :)

How to start and enable these services (after installing packages given above), is present in the wiki (https://wiki.manjaro.org/index.php?title=Openrc#Configuration) (the services are cupsd and sshd, I will try to add this info in the wiki also).

For cups, you could try the web interface (available as "manage printing") option in the System category in the Xfce menu, else the address for it (available after starting the cups service ofc) is http://localhost:631/

Thank you. I started them from the /etc/init.d/ directory and now I'm wondering how I confiure them to start on reboot (this is my laptop).I use wmaker generally, usually. I pulled the main packages from pacman but the other little bits of it, they are in the AUR and they don't come up with pacman -S . In fact wmakerconf won't even compile with makepkg ... weird. BTW I got here after 15 years on suse and opensue. I tried a dozen or so distros on this new laptop and none of them worked at all. Netrunner worked pretty good but systemd was was killing me and actually it eventually refused to boot. They are arch based and they pointed me here to this openrc distro. So far, so good but I lost all my oracle school work :(

Thank you. I started them from the /etc/init.d/ directory and now I'm wondering how I confiure them to start on reboot (this is my laptop).I use wmaker generally, usually. I pulled the main packages from pacman but the other little bits of it, they are in the AUR and they don't come up with pacman -S . In fact wmakerconf won't even compile with makepkg ... weird. BTW I got here after 15 years on suse and opensue. I tried a dozen or so distros on this new laptop and none of them worked at all. Netrunner worked pretty good but systemd was was killing me and actually it eventually refused to boot. They are arch based and they pointed me here to this openrc distro. So far, so good but I lost all my oracle school work :(

sudo rc-update add cupsdThe systemd directory could be present as its present in the manjaroiso (https://wiki.manjaro.org/index.php?title=ManjaroISO) configs (I dont try to change too much stuff to remain compatible with the official editions).

I would not be accepting any donations for my work, as I do it out of a hobby (and a lot of the work is done by artoo) :)

sudo nano /etc/hostname Delete "manjaro" (Hint: it the default hostname).Then add whatever you want. Ctrl+X to Save.3) Or you burn your disk to fast as you install the iso image. Which can lead to weird problem to the install or after. Always set it to the slowest speed that you can!

It doesn't listen to that file anyway. No matter what is in there it still thinks its hostname is manjaro

I installed openbox openrc rc1 version and it works flawlessly, no overheating problems i had with systemd version :D, except after switching to networkmanager (need for mobile broadband) i cant add modemmanger to startup, mobile broadband works when I start it manually.

I installed openbox openrc rc1 version and it works flawlessly, no overheating problems i had with systemd version :D, except after switching to networkmanager (need for mobile broadband) i cant add modemmanger to autostart, mobile broadband works when I start it manually.

Seems sourceforge is down again at the moment so was unable to load networkmanger-openrc. I will get some secret project up and running in the near future. How on earth you got eudev working with Arch is amazing.

The reason I think the OpenRC edition is not in the community editions is that first of all the users could get confused by having two versions of Xfce/Openbox ISOs, and secondly OpenRC is a niche product ;)

In Manjaro systemd releases I like how shutdown command is configured so that it works without sudo. How to configure it similarly in openrc edition?

shutdown is simply symlinked to systemctl, its not configured it any way.Method1You can configure sudo to run certain commands without entering password:https://wiki.archlinux.org/index.php/Allow_users_to_shutdown#Users_without_sudo_privilegesWith OpenRC (non-systemd) that would translate to:

user hostname =NOPASSWD: /usr/bin/poweroff,/usr/bin/rebootwhere user and hostname have to be substituted.

After that you can add aliases to the shell (bash) so that sudo is appended automatically:https://wiki.archlinux.org/index.php/Allow_users_to_shutdown#Creating_aliasesWith OpenRC (non-systemd) that would translate to:

But it *is* configured somehow, because in Manjaro with systemd it works for all users without any aliases having been set in .bashrc.

1. Install Manjaro with systemd2. Open up .bashrc - no aliases that you speak of3. type shutdown -h now - works4. type reboot - works

In my Xfce installation (systemd), I set the alias "off" for shutdown -h now over a year ago.

Since shutdown and poweroff are symlinked to systemctl, when you call shutdown -h now, what gets called is (systemctl) shutdown -h now, and as systemctl does not require root rights to shut the system off (as it communicates with systemd which runs with root rights), so off it goes...

that the openrc versions are currently niche products is maybe based on the situation, that such a great running editions aren't presented in an more attractive way.

Greetings

B-Lux

Hmm, I kind of agree with you there.

The reason I am keeping it low profile is because of the situation we are in regarding systemd; as systemd gains more ground and if it makes it to the kernel, there will obviously be a divide b/w those who want systemd and those who dont, and as Manjaro follows Arch which supports only systemd, the foundation is weak..

Hence I dont want to publicize it too much only to throw in the trowel six months later saying "oh, we cant support it anymore".

Disclaimer: This is just my opinion though and not necessarily the team's.

Since shutdown and poweroff are symlinked to systemctl, when you call shutdown -h now, what gets called is (systemctl) shutdown -h now, and as systemctl does not require root rights to shut the system off (as it communicates with systemd which runs with root rights), so off it goes...

I see, so it works only because it's linked to systemd. And therefore more tweaks are needed to achieve the same in openrc.

I see, so it works only because it's linked to systemd. And therefore more tweaks are needed to achieve the same in openrc.

We depend currently on arch packages, and if arch decide to go eg kdbus as some point, it may be that we get in a situation where more manpower is needed to port some solution to manjaro and to replace heavily systemd depend arch packages.I personally would love to eliminate some stuff in arch packages to suit alternatives much better.

We depend currently on arch packages, and if arch decide to go eg kdbus as some point, it may be that we get in a situation where more manpower is needed to port some solution to manjaro and to replace heavily systemd depend arch packages.I personally would love to eliminate some stuff in arch packages to suit alternatives much better.

I am bit more optimistic than aaditya though. :)

I would like to help, and i have a friend, David Sugar who has been a big GNU systems progrmmer for a long time, he want to help as well.

Hi guys, have been playing with OpenRC since yesterday, as aaditya knows :) Hi aaditya, I just thought I'd get in here and thank artoo too, thanks artoo ;) The both of you have came up with something rather nice here.

I have been trying all day to break it and it just won't break hahaha. Just kidding, this OpenRC release is, in my opinion, the way XFCE, Openbox and whatever else will work on it, was made to run on Linux, it is blindingly fast and as far as I can tell up to now very very stable, hell, I even considered switching to unstable just to see if I could break it there >:D

@aaditya, I think I will end up using this as my main flavour of The Mighty Manjaro. ;)

Thanks schpankme, it really is and all, I'm really enjoying the lightening speed in comparison to the "other" init system, don't want to say it and be told I'm flaming lol Just kidding, I don't know enough to flame about it anyhow, just know this is super quick compared and that's from what I see with regards to system performance.

Stability, so far so good, I haven't broken it yet, ask me again in a few weeks lol

I am running OpenRC on an old Viglen computer I use for "messing" about, just installed it tonight :) I did have LXqt on it (thanks Esclapion :)) ) and it ran but it was really unbearably slow. So far this old machine is now usable although it is still slow but not no were near as bad, this release has a lot of potential to suit many different scenarios and even breath life back in to an old dead horse ;)

Here is a pastebin (http://pastebin.com/ynfmp2qr) with the specs of this old box.

Thanks for that schpankme, that saved around 28mb so far ;D makes a difference on this machine, poor thing is old like myself :o

I wouldn't mind trying to save more and I will likely only use Openbox as the DE but I don't want to rape and pillage the fine piece of work that artoo and aaditya has put together, thank you guys. I haven't actually tried XFCE on it yet, will go and do that now ;)

Thanks again schpankme, you're a real gentleman, I hope the offer is an open one ;)

EDIT: I logged in to XFCE to try it and granted, it did just a little more wheezing but it's not to bad still. I am gonna put this OpenRC on my main box also, sure it'll give me something else to learn about :P

Hi guys, I have a little question, I have been hunting for info on mounting my disk on boot using OpenRC and have not found anything, all I keep coming up with is the systemd way. Here's my question, can anyone help please? :-[

Hi Ponder, thanks for your answer, so if I am reading you right all I need to do is add the UUID and other info to fstab? Is that right?

Cheers,darso.

That should do it. Of course it has to be the right information for your system, which is going to be different than my example. You don't have to use UUIDs, but they supposedly are the superior way to identify the individual drive(s) and partitions.

Hi again mate, I set up my fstab with the info needed, I have two partitions I want to load, /data Label:Data and 1tb Label:1TB. I entered the UUID's in to my fstab and on booting the computer it's telling me there are no mount points for these drives, now I am totally lost and I can no longer see the drives in my file manager (Thunar), I know restoring the fstab file to original will bring them back okay although I would still like them to automount. I don't mean to be a pain in the neck but could you even point me in the right direction to create fore mentioned mount points, pleeeeeeeeeeease ;D

Me too hahaha this OpenRC release is nice though, it means a new learning process for me but the benefits are well worth it. I had udes used Manjarobox before and loved the OpenBox WM although found that a learning process on it's own. I also love XFCE and used that for quite a while. I tried installing OpenBox on my XFCE setup but I could never just get OB to work/look/feel the way these guys can, they really are excellence personified at what they are doing.

So OpenRC has so far given me exactly what I wanted and much more than what I need and we all have the "Dynamic Duo" as my good friend Ticnt calls them artoo and aaditya to thank for this and of course the brilliant devs behind all the packages and software that makes it possible.

A big heart felt thank you guys, and to you to Ponder, for your help tonight.

The site is under constant scrutiny and improvement; I'd love to incorporate any comments, experiences and suggestions. Ideally, it could include more init systems - no, scratch that: it will include more init systems once we achieve a resonably reliable desktop configuration guide, which has become the most difficult part, thanks to you-know-what's intrusiveness.

Truly, if an init system stays within the scope of its purpose and doesn't mess with other components' business, switching to/from it cannot and should not affect desktop functionality.

I did have a look in to it and tried from a live USB to install using Btrfs but was unable to do so. I am not sure if this was down to my lack of knowledge or that it simply is not supported, yet, I hope! So just thought I would ask above question here to be sure.

I did have a look in to it and tried from a live USB to install using Btrfs but was unable to do so. I am not sure if this was down to my lack of knowledge or that it simply is not supported, yet, I hope! So just thought I would ask above question here to be sure.

Thanks in advance for any info.

Cheers,darso.

Hi darso,

As far as I know, the cli installer offers an option for formatting a partition as Btrfs while installing; I have not tried it though and hence dont know if it works.

I don't think this does work with OpenRC, at least the set-up I need. I get as far as "Disk Preparation" and the installer starts asking for swap, root and home drives.

I am atm trying to put together a small tutorial on using grub-btrfs to create an environment that makes snapshots of the system really simple, as soon as I have that finished I will get back in to this and see if I can configure it with the fore mentioned config, just to see what happens ;)

i'll explain again ... if openrc use grub then it work. If openrc does not use grub, simply use a two partition set-up / boot btrfs and / btrfsThen no need for grub since all admin is done from level 0

i'll explain again ... if openrc use grub then it work. If openrc does not use grub, simply use a two partition set-up / boot btrfs and / btrfsThen no need for grub since all admin is done from level 0

Have fun

Hi Loup,

EDIT: Yes OpenRC uses grub.

I didn't realize this could be done with /boot /. Can I also have /home and do I need swap? I have 8gb ram.

Cheers,darso.

P.S. I have been searching all over the net for specific btrfs+OpenRC info :o

I understand that you went thru alot of reading these recent days . ;D

Btrfs does not support swap so far. At 8 g. of ram ... have you ever seen swap used on your system ?

You will not find info on btrfs and openrc, since it as nothing to do with btrfs. Btrfs is an fs ( file system ) openrc is an init program like systemd

Hope this is a better explanation :-[

Hi Loup,

Yes, I have, lots & lots :o ;D

No, I have never seen it being used at all, thanks - "swapoff" = 8gb extra disk space ;D

I know btrfs is a filesystem and OpenRC is init, I should maybe have worded that better, what I meant was I had been looking for info on weather someone had used the two together already, sorry for the bad explanation on that one :-[

Yes it does explain it better mate, I needed to sleep last night and just kinda flaked out. I'm not sure if I dreamt it or not but I sort of seen your answer, it came to me on the back of a white leprechaun??? :o ::) ;D >:D The wee bugger didn't bring any gold though! ;D

The swap area is used for hibernation. I'm not sure what happens if you have no swap but try to hibernate.

I know you can have a swap file instead of a dedicated partition and hibernate to that, though. Never tried it myself.

The swap file works like the normal "swap" there are no downsides, so when our friend here finds out what hibernation is :) and needs a swapfile; he can simply make one.(It is that thing where you computer goes to "sleep" and starts within seconds after you turn it on again - some people are impressed with that fast "boot" - particularly Gnome devs who even left out the poweroff button and had hibernation as default)

You can also make a swap file if you find out that you have to little swap the file will then add to the swap you had.(Not instead of dedicated partition but in addition to...)

So when the time comes: here is HowTo (http://bjoernvold.com/forum/viewtopic.php?f=25&t=1763#p16976)

(It is that thing where you computer goes to "sleep" and starts within seconds after you turn it on again - some people are impressed with that fast "boot" - particularly Gnome devs who even left out the poweroff button and had hibernation as default)

Damn, I thought they were pledged to Red Hat. Silly me. They seem to be Redmond bound. ;D

(It is that thing where you computer goes to "sleep" and starts within seconds after you turn it on again - some people are impressed with that fast "boot" - particularly Gnome devs who even left out the poweroff button and had hibernation as default)

So when the time comes: here is HowTo (http://bjoernvold.com/forum/viewtopic.php?f=25&t=1763#p16976)

Computer goes to sleep! I pay for the buggers electricity, it isn't allowed to sleep, even IF I do >:D

Thanks for this though guys, it's a better idea to create a file I feel anyhow. I think it would give more control i.e. where the file resides, it can be put on the largest partition and if you want to "swapoff" you can just delete the file and voila! instant free space ;)

I am doing nothing for a few days except for enjoying my computer. I spent a few days (thanks Loup) figuring out Btrfs and now I am just enjoying playing with a new Gnome install, it wouldn't work after updates but I got it sorted and I have been wanting to have a look for a while, now I am! ;D

Next step is to try and set-up OpenRC with Btrfs but I'm leaving that for a few days :o

Just wanted to post and say that the detailed instructions for moving from Systemd to OpenRC were flawless. Took me about 30mins, and that is including the 'missed' graphical login procedure.System 'feels' more responsive and on bootup, uses about 75-100mb less memory.Great work on the Wiki page.Straightforward and easy to follow.

Just wanted to post and say that the detailed instructions for moving from Systemd to OpenRC were flawless. Took me about 30mins, and that is including the 'missed' graphical login procedure.System 'feels' more responsive and on bootup, uses about 75-100mb less memory.Great work on the Wiki page.Straightforward and easy to follow.

That tells you that a version of udev is running, but not if it is eudev. The only way I know is to look at the packages. Eudev will conflict with the systemd version. Both versions can't be installed at the same time. If eudev is installed, it will be the version running.

We could think about providing openrc with runit instead of sysvinit.>=0.16 support process supervision, the question is, do we need such gimmick?

I been testing out a distro that used pure runit. The boot time on runit is insane fast. On my new ssd. less then half sec boot. vs manjaro openrc 8.13 in 3 sec boot. boot time are base from grub to log in screen. or tty for me.

I been testing out a distro that used pure runit. The boot time on runit is insane fast. On my new ssd. less then half sec boot. vs manjaro openrc 8.13 in 3 sec boot. boot time are base from grub to log in screen. or tty for me.

I know runit is fst if you use it, but runit with openrc would only serve as sysinit replacement, and openrc could be configured to use runit's process supervision. But I think, it not really a pressing feature we need.

I know runit is fst if you use it, but runit with openrc would only serve as sysinit replacement, and openrc could be configured to use runit's process supervision. But I think, it not really a pressing feature we need.

Hi

That is why I asked what differece it would make. Boottime seriously means nothing to me since I run this on my workstations and my small servers. Is there any other advantage?

@artoo: I had already looked at that page & bookmarked it. I find it a bit hard to understand with all of the extra Gentoo stuff. [edit:] There wasn't really that much extra Gentoo stuff... ;) /

It has been years since I last setup NFS & from memory (which isn't my strong point) it was fairly easy/simple to get going (harder to fine tune).

So it looks like I'll have to use the Arch & the Gentoo wiki's to find my way through this. The Arch one is much simpler, though systemd specific, which is of course why I'm posting the question here to begin with...

The /etc/init.d/nfsclient script is missing from the machine which I followed the wiki instructions to convert from systemd to OpenRC/eudev yesterday.

As is /etc/init.d/nfs (& I haven't checked to see what others that don't belong to NFS may be missing?).

I'll copy them over from my full OpenRC/eudev install & see how I go from there...

I think it would be good if these files were included in the OpenRC base package. I also understand how easy it would be to miss them. ;)

[edit:] I'll post a list of the files that are in the /etc/init.d directory of the full OpenRC install that I did a few days ago, that are not on my machine that I converted according to the Manjaro wiki page yesterday. In case it is of any use to anyone (I chose not to install cups on the machine I converted yesterday):

I think I've got the Server sorted out & now I've started on the Client, where I've struck a problem in the Gentoo wiki:

The /etc/init.d/nfsclient script is missing from the machine which I followed the wiki instructions to convert from systemd to OpenRC/eudev yesterday.

As is /etc/init.d/nfs (& I haven't checked to see what others that don't belong to NFS may be missing?).

I'll copy them over from my full OpenRC/eudev install & see how I go from there...

I think it would be good if these files were included in the OpenRC base package. I also understand how easy it would be to miss them. ;)

[edit:] I'll post a list of the files that are in the /etc/init.d directory of the full OpenRC install that I did a few days ago, that are not on my machine that I converted according to the Manjaro wiki page yesterday. In case it is of any use to anyone (I chose not to install cups on the machine I converted yesterday):

sudo: /etc/init.d/autofs: command not foundI had a bit of a ferret around inside of /etc but I can't find the file? Had a look in the pacman.log & it just says "transaction completed" there are no error messages.

sudo: /etc/init.d/autofs: command not foundI had a bit of a ferret around inside of /etc but I can't find the file? Had a look in the pacman.log & it just says "transaction completed" there are no error messages.

This is a more a DE question. But also a theroy. Are gtk3 DE starting to become more of a issue to used due to GNOME lack of consolekit support? If this is true. I wonder if the same issue will be in qt5. Or all this depend on the developer?

My mind went out to wonderland to much. Maybe being a little to concern to early.

Yes, right, its basically up to the developers.I try to answer regarding gnome.The bottleneck is systemd's logind.As of now, the is no true equivalent to logind as alternative, but consolekit2 is heading towards implementing kind of logind replacement. Historically, consolekit was the precursor of logind, but logind is for various reasons difficult to replicate.Consolekit2 is a forked and further developed version of unmaintained consolekit.So the short answer is, gnome devs decided to remove consolekit support couple of months ago.Their code doesn't support it any longer afaik. If someone was keen on patching in ck2 support, feel free to do.

I just installed this last night and I am at a loss of words. It was super fast, worked right out of the box. I started converting all my gentoo boxes over to this distro. Again I really appreciate your hard work on the switch from systemd to openrc and giving me a choice of init systems once more.

Not sure what I can do to help but let me know if there is anything I can do.

# if openrc should make use of /etc/modules-load.d# systemd places stuff thereuse_modules_load_d=false

This means, openrc will read conf files in /etc/modules-load.d and will write /etc/conf.d/modules at every boot. if set true. So it basically loads modules automatically, that are provided by kernel extra packagesIt is deactivated by default, but it should work well except for hybrid cards eventually.Enthusiasts can test by setting the switch to true, but please report back any errors.

# if openrc should make use of /etc/modules-load.d# systemd places stuff thereuse_modules_load_d=false

This means, openrc will read conf files in /etc/modules-load.d and will write /etc/conf.d/modules at every boot. if set true. So it basically loads modules automatically, that are provided by kernel extra packagesIt is deactivated by default, but it should work well except for hybrid cards eventually.Enthusiasts can test by setting the switch to true, but please report back any errors.

This is not working for my b43 module I need to load. I have blacklisted wl module and "unblacklisted" b43 in /etc/modprobe.d/linux41-broadcom-wl.conf. In /etc/modules-load.d/modules.conf I put b43. And my /etc/conf.d/modules contains a single line: use_modules_load_d=true. The /etc/conf.d/modules file is being generated at each boot, copying the old file to /etc/conf.d/modules.lastboot.

I can load the b43 with modprobe b43 and wifi works fine.

I am using Manjaro OpenRC xfce (The one just created by aaditya) and my updates are all current.

Hi Artoo, I'm using the KDE Openrc version from some days and I'm more than happy, also if I have to tune some aspects. Anyway, some considerations.First: I did an error voting and I'm using eudev, not udev, a click error; sorry O:-)

Second: I got some little problems, almost all solved and they are:1) I'm not able to startup pulseaudio as standard service (I read and tried all the options in the thread about it, but nothing), anyway, I was able to start it with the "Startup and Program" service in System Settings, so no problem, but strange2) Wine emulation is slower and more CPU crunching than with the standard systemd Manjaro KDE version (I'm till using it as my production OS), and I'm not able to understand why: all look like identical3) After the installation (KDE minimal the last version) the menu icon wasn't visible, and 2 reboot was needed4) Plasma 5 seems to be slower to open and close the windows, but I must profile the time better, this is simply an impression5) The upgrades are aligned with the standard Manjaro upgrade or there is a delay?

Just to inform you, but nothing so terrible and my BEST compliments for the great work!

I'm using a luks crypted disk with btrfs and no problems. In the next days I'll install also all the other programs that usually use and I'll do some deeper tests, but all seems to work fine.

If needed, I may manage some tests, I can install and I'll installa testing environment.

Good works also if its not yet ready for a "standard user", IMHO. I'll try also the xfce version, just cause I'm curious, but I like too much the Plasma environment ;)

@dxrobertson, I did modprobe b43 right after installing and had no problems.

I think the recent kernels addressed some issue with the b43 module :). My MacBook 7,1 broadcom 4322 chip suddenly started working out-of-the-box again. Earlier it needed pulling the sta driver from AUR on Arch Linux or installing the module from the main repos here in Manjaro.

On my side I would like to applaud the openRC endeavor for Manjaro. The Gentoo-converted packages work flawlessly and together with the Manjaro/Arch base are how an openRC distro should work, I think - simple dependency resolution with sane syntax and output (hail pacman!) + PKGBUILDs. The only minor problem I had was the openGL provider setter through mhwd (Gentoo uses eselect for that, so there is not much difference, though eselect is somewhat 'canon') and dhcpcd not being enabled through rc-update on startup after install (no internet connection, therefore).

The relative slowness may be a result of systemd libs still present on the system.Most arch packages are compiled with some systemd feature enabled.

Relatively to my gentoo on the same machine, yes, it tends to be a wee bit slower, however, my gentoo packages are also cpu optimized etc..., as opposed to generic arch/manjaro settings.

A long term goal would be to eliminate libsystemd, and to have a systemdless package base, which could also serve to reorganize swapping udev components. Its atm all pretty much libsystemd depend, instead of eg libudev, but this can only be addressed when there is some new needed infrastructure available.It is nearly impossible to maintain currently a full package set by just one dev.

The relative slowness may be a result of systemd libs still present on the system.Most arch packages are compiled with some systemd feature enabled.

Relatively to my gentoo on the same machine, yes, it tends to be a wee bit slower, however, my gentoo packages are also cpu optimized etc..., as opposed to generic arch/manjaro settings.

A long term goal would be to eliminate libsystemd, and to have a systemdless package base, which could also serve to reorganize swapping udev components. Its atm all pretty much libsystemd depend, instead of eg libudev, but this can only be addressed when there is some new needed infrastructure available.It is nearly impossible to maintain currently a full package set by just one dev.