You are not logged in.
Another thing: I get
kernel.kptr_restrict invalid argument
in the boot when I boot with grsec kernel. Is this any OpenRC specific or not?
Thanks,
Hmm, no idea...
I thought you are following gentoo repo. One question: what's the state of openrc in Manjaro Linux? I don't want to start a battle Manjaro/Arch, but is the systemd the default boot system in Manjaro too?
Yup, systemd is the default, OpenRC is available as an alternative.
Edit-
"boot option" written above is slightly misleading, its not like Ubuntu where you have an option to choose your init at boot, "init system" is probably the more correct term.
Last edited by aaditya (2015-05-17 14:10:05)
Offline
The last version (0.16.4-2) of openrc-core causes that mouse does not run in X. Can you review it. The previous version (0.16.4-1) is OK.
Owning one OpenRC (artoo way) and other three systemd machines
Offline
Can anyone check it?
Thanks,
The last version (0.16.4-2) of openrc-core causes that mouse does not run in X. Can you review it. The previous version (0.16.4-1) is OK.
Owning one OpenRC (artoo way) and other three systemd machines
Offline
@xanb
Gentoo's splitting udev script into udev+udev-trigger+udev-settle. This process lasted for two or three days, and bugs have been resolved today. Arch's package may be a bit behind, so if the new version installs udev-trigger you should be careful with the upgrade.
P.S. Aren't scripts install with a different package (eudev-arch-scripts or somesuch)?
Offline
@xanb
Gentoo's splitting udev script into udev+udev-trigger+udev-settle. This process lasted for two or three days, and bugs have been resolved today. Arch's package may be a bit behind, so if the new version installs udev-trigger you should be careful with the upgrade.
P.S. Aren't scripts install with a different package (eudev-arch-scripts or somesuch)?
So do I have to wait until then? My level is begginer already ;-) Thanks for answering.
Last edited by xanb (2015-06-16 07:16:01)
Owning one OpenRC (artoo way) and other three systemd machines
Offline
That and the manjaro pkgbuilds (surprise!) now install to /usr/lib/manjaro.
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Offline
Guys do not upgrade if you need a fully functional system right now. On Gentoo I got the working wersion of the scripts yesterday, but since Arch is not as close to upstream as Gentoo is (unless you're using git version) it may be a while for it to come to Arch.
By all means try the new version, but do not be surprised if it does not boot or some of things is missing.
P.S. Just remembered what was the cause of no mouse in xorg. udev-trigger was starting too early, before udev finished. Delaying that script's start in any way by a few seconds would help.
Offline
Delaying that script's start in any way by a few seconds would help.
Haha. And so we return to slackware style init systems. Sleep, sleep everywhere.
Last edited by Earnestly (2015-06-16 17:17:50)
Offline
You could also move the script from sysinit to boot runlevel. I've not tried it as the defaults work perfectly on my pc, or you could change the scripts so they would have some sort of sync logic, than make a pull request.
The first "solution" I've found was a user using interactive boot to delay the script. The user manually started one script after another accouting for the needed delay.
Offline
Perhaps Aaditya could tell us what amount of time we have to wait ;-)
Owning one OpenRC (artoo way) and other three systemd machines
Offline
Perhaps Aaditya could tell us what amount of time we have to wait ;-)
me and nous are co-maintainers.
I will try to do it today. Source is available here.
Offline
Thanks for the update but I get the same results with openrc-core 0.16.4-3 (with the removal of eudev-openrc)
Owning one OpenRC (artoo way) and other three systemd machines
Offline
Aaditya, Nous : some comments about the openrc-core pkgbuild
if [ -f /etc/os-release ]; then
. /etc/os-release
_base_args+=(BRANDING="$NAME")
else
_base_args+=(BRANDING='Unknown Linux')
fi
If etc/os-release doesn't exist, you should check for /usr/lib/os-release instead (check filesystem manpage) .
_rc_args+=(LIBEXECDIR=/usr/lib/rc)
_f_args+=(ROOTLIBEXECDIR=/usr/lib/manjaro)
_net_args+=(LIBEXECDIR=/usr/lib/${_net})
Why 3 different libexec directories instead of just 1 ?
In the package() function i notice several uses of sed. Maybe they can be replaced by patching source files in prepare ?
Last edited by Lone_Wolf (2015-06-18 08:05:36)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Thanks for the update but I get the same results with openrc-core 0.16.4-3 (with the removal of eudev-openrc)
Dunno about that, you could downgrade to the version which works or you or check the logs and do some investigation.
Aaditya, Nous : some comments about the openrc-core pkgbuild
if [ -f /etc/os-release ]; then . /etc/os-release _base_args+=(BRANDING="$NAME") else _base_args+=(BRANDING='Unknown Linux') fi
If etc/os-release doesn't exist, you should check for /usr/lib/os-release instead (check filesystem manpage) .
_rc_args+=(LIBEXECDIR=/usr/lib/rc) _f_args+=(ROOTLIBEXECDIR=/usr/lib/manjaro) _net_args+=(LIBEXECDIR=/usr/lib/${_net})
Why 3 different libexec directories instead of just 1 ?
In the package() function i notice several uses of sed. Maybe they can be replaced by patching source files in prepare ?
Hi Lone_Wolf,
Artoo is the maintainer of most of the pkgbuilds, we just maintain the repo.
I agree with your first point, dunno about the second, and for the third I think sed is simpler, because patches would probably need to be updated every time a script is changed, and for a large number for files it could be difficult to maintain as well.
Last edited by aaditya (2015-06-18 16:04:31)
Offline
xanb wrote:Thanks for the update but I get the same results with openrc-core 0.16.4-3 (with the removal of eudev-openrc)
Dunno about that, you could downgrade to the version which works or you or check the logs and do some investigation.
Version of openrc-core 0.16.4-1 works perfectly, but openrc-core 0.16.4-3 causes the problem.
Owning one OpenRC (artoo way) and other three systemd machines
Offline
WIth completely new OpenRC installation, I get a problem when I run
pacman -S eudev-openrc eudev-systemdcompat
openrc-core is in conflict with these packages?
On the other hand, I get an error on the boot:
* Setting up tmpfiles.d entries...
tmpfiles: ignoring invalid entry on line 11 of '/usr/lib/tmpfiles.d//tmp.conf'
tmpfiles: ignoring invalid entry on line 12 of '/usr/lib/tmpfiles.d//tmp.conf'
tmpfiles: ignoring invalid entry on line 21 of '/usr/lib/tmpfiles.d/var.conf'
The lines in tmp.conf are:
v /tmp 1777 root root 10d
v /var/tmp 1777 root root 30d
and
v /var/lib/machines 0700 - - -
Thanks,
Owning one OpenRC (artoo way) and other three systemd machines
Offline
WIth completely new OpenRC installation, I get a problem when I run
pacman -S eudev-openrc eudev-systemdcompat
openrc-core is in conflict with these packages?
On the other hand, I get an error on the boot:
* Setting up tmpfiles.d entries... tmpfiles: ignoring invalid entry on line 11 of '/usr/lib/tmpfiles.d//tmp.conf' tmpfiles: ignoring invalid entry on line 12 of '/usr/lib/tmpfiles.d//tmp.conf' tmpfiles: ignoring invalid entry on line 21 of '/usr/lib/tmpfiles.d/var.conf'
The lines in tmp.conf are:
v /tmp 1777 root root 10d v /var/tmp 1777 root root 30d
and
v /var/lib/machines 0700 - - -
Thanks,
eudev-openrc is deprecated with openrc-core>=0.16.4-2 and can be skipped, so only eudev and eudev-systemdcompat could be installed.
For the tmpfiles error https://github.com/OpenRC/openrc/issues/59
Offline
Thanks a lot. I used this guide (https://abchk1234.wordpress.com/2014/06 … aro-linux/)
Owning one OpenRC (artoo way) and other three systemd machines
Offline
By the way, there is a new version: 0.17
Owning one OpenRC (artoo way) and other three systemd machines
Offline
Is there any service available to run logrotate every day? If not, what's the best way to put in cron?
Owning one OpenRC (artoo way) and other three systemd machines
Offline
Which is the key for pacman does not get error? That is, how can comment the line
#SigLevel = PackageOptional
in [openrc-eudev]?
Owning one OpenRC (artoo way) and other three systemd machines
Offline
Is there any service available to run logrotate every day? If not, what's the best way to put in cron?
You could install cronie-openrc and enable the respective service, and add a logrotate cron job to /etc/cron.daily
https://github.com/notfoss/archlinux-cronjobs
Which is the key for pacman does not get error? That is, how can comment the line
#SigLevel = PackageOptional
in [openrc-eudev]?
SigLevel = PackageOptional is what I am using.
Offline
xanb wrote:Is there any service available to run logrotate every day? If not, what's the best way to put in cron?
You could install cronie-openrc and enable the respective service, and add a logrotate cron job to /etc/cron.daily
https://github.com/notfoss/archlinux-cronjobsxanb wrote:Which is the key for pacman does not get error? That is, how can comment the line
#SigLevel = PackageOptional
in [openrc-eudev]?
SigLevel = PackageOptional is what I am using.
Great: your logrotate cron job is awesome. Thanks for sharing it with us.
On the other hand, tell me "paranoid" ;-) but I want to sign my packages. What is the keys used in [openrc-eudev] packages?
Owning one OpenRC (artoo way) and other three systemd machines
Offline
Can you include pkgstats cron job:
# cat pkgstats
#!/bin/sh
# nicenesses range from -20 (most favorable scheduling) to 19 (least favorable)
NICE=19
# 0 for none, 1 for real time, 2 for best-effort, 3 for idle
IONICE_CLASS=2
# 0-7 (for IONICE_CLASS 1 and 2 only), 0=highest, 7=lowest
IONICE_PRIORITY=7
CMD_PKGSTATS="/usr/bin/pkgstats -q"
if [ -x /usr/bin/nice ]; then
CMD_PKGSTATS="/usr/bin/nice -n ${NICE:-19} ${CMD_PKGSTATS}"
fi
if [ -x /usr/bin/ionice ]; then
IONICE_CMD="/usr/bin/ionice -c ${IONICE_CLASS:-2}"
if [ $IONICE_CLASS -ne 3 ]; then
IONICE_CMD="${IONICE_CMD} -n ${IONICE_PRIORITY:-7}"
fi
CMD_PKGSTATS="${IONICE_CMD} ${CMD_PKGSTATS}"
fi
${CMD_PKGSTATS}
exit 0
I copied from you and from systemd profile. Is there any way to run it with user nobody (systemd does)?
Thanks,
Owning one OpenRC (artoo way) and other three systemd machines
Offline
Great: your logrotate cron job is awesome. Thanks for sharing it with us.
On the other hand, tell me "paranoid" ;-) but I want to sign my packages. What is the keys used in [openrc-eudev] packages?
Cron job repo is by x33a.
Package signing was removed, because of two reasons: 1. there are two maintainers now, 2. signed package seem to cause more errors than unsigned ones.
If you are concerned about security you could build it yourself, source is available as I have mentioned before.
Offline