Re: [gentoo-user] network do not come up after booting, only manual reloading (systemd-networkd)
Hi ... In another. The only difference I see is the systemd-udev-settle.service, do you have it enabled it? What systemd-* services do you have enabled? I have: aztlan ~ # find /etc/systemd/system -name "systemd-*" -type l /etc/systemd/system/network-online.target.wants/systemd-networkd-wait-online.service /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service /etc/systemd/system/multi-user.target.wants/systemd-networkd.service /etc/systemd/system/sockets.target.wants/systemd-networkd.socket Mine is: tamer@tux ~ $ find /etc/systemd/system -name "systemd-*" -type l /etc/systemd/system/sockets.target.wants/systemd-networkd.socket /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service /etc/systemd/system/network-online.target.wants/systemd-networkd-wait-online.service /etc/systemd/system/multi-user.target.wants/systemd-networkd.service I think the problem is somewhere deeper I wish I knew what it might be. best, Tamer Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Debian just voted in systemd for default init system in jessie
On Sun, Feb 16, 2014 at 12:59 PM, Volker Armin Hemmann volkerar...@googlemail.com wrote: [ snip ] or it is an idiotic decision. Because features means complexity. Yeah, like the kernel. Complexity means bugs. Bugs get reported, bugs get fixes. Life goes on. And you don't want complexity in PID1 or init. Let those 'features' be handled by their own specialists. Almost all the features of systemd live outside of PID 1. You know, the unix way. Do one thing, do it well. This is from my desktop machine: /usr/lib/systemd/systemd-reply-password /usr/lib/systemd/ntp-units.d /usr/lib/systemd/systemd-coredump /usr/lib/systemd/systemd-hostnamed /usr/lib/systemd/systemd-binfmt /usr/lib/systemd/systemd-localed /usr/lib/systemd/systemd-machined /usr/lib/systemd/systemd-sleep /usr/lib/systemd/system-generators /usr/lib/systemd/system-generators/systemd-system-update-generator /usr/lib/systemd/system-generators/systemd-gpt-auto-generator /usr/lib/systemd/system-generators/systemd-efi-boot-generator /usr/lib/systemd/system-generators/systemd-fstab-generator /usr/lib/systemd/system-generators/systemd-getty-generator /usr/lib/systemd/system-generators/gentoo-local-generator /usr/lib/systemd/systemd-fsck /usr/lib/systemd/systemd-bootchart /usr/lib/systemd/systemd-shutdown /usr/lib/systemd/systemd-random-seed /usr/lib/systemd/system-sleep /usr/lib/systemd/systemd-remount-fs /usr/lib/systemd/user-generators /usr/lib/systemd/systemd-sysctl /usr/lib/systemd/systemd-timedated /usr/lib/systemd/catalog /usr/lib/systemd/system-shutdown /usr/lib/systemd/systemd-udevd /usr/lib/systemd/systemd-multi-seat-x /usr/lib/systemd/systemd-cgroups-agent /usr/lib/systemd/systemd-user-sessions /usr/lib/systemd/systemd-journal-gatewayd /usr/lib/systemd/systemd-quotacheck /usr/lib/systemd/systemd-shutdownd /usr/lib/systemd/systemd-modules-load /usr/lib/systemd/systemd-backlight /usr/lib/systemd/systemd-ac-power /usr/lib/systemd/systemd-initctl /usr/lib/systemd/systemd-readahead /usr/lib/systemd/systemd-journald /usr/lib/systemd/systemd-activate /usr/lib/systemd/systemd /usr/lib/systemd/systemd-update-utmp /usr/lib/systemd/systemd-vconsole-setup /usr/lib/systemd/systemd-logind All of them are different tools providing one capability to systemd as a whole. So systemd is a collection of tools, where each one does one thing, and it does it well. By your definition, systemd perfectly follows the unix way. Use text to communicate. systemd can comunicate basically everything via text: centurion ~ # systemctl show sshd.service | head Id=sshd.service Names=sshd.service Requires=basic.target Wants=system.slice WantedBy=multi-user.target Conflicts=shutdown.target Before=shutdown.target multi-user.target After=syslog.target network.target auditd.service systemd-journald.socket basic.target system.slice Description=OpenSSH server daemon LoadState=loaded For performance reasons, some things are passed or stored as data. Bu everything works with text also. So, again, it passes your definition. That stuff. That makes things easy. And flexible. And replaceable. Easy to whom? And systemd is more flexible that a lot of init systems, in my opinion including OpenRC. All the configuration and APIs are documented, public and open source. Everything is replaceable if there is someone willing and able to write a replacement. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] Debian just voted in systemd for default init system in jessie
Am 16.02.2014 21:08, schrieb Canek Peláez Valdés: On Sun, Feb 16, 2014 at 12:59 PM, Volker Armin Hemmann volkerar...@googlemail.com wrote: [ snip ] or it is an idiotic decision. Because features means complexity. Yeah, like the kernel. Complexity means bugs. Bugs get reported, bugs get fixes. Life goes on. And you don't want complexity in PID1 or init. Let those 'features' be handled by their own specialists. Almost all the features of systemd live outside of PID 1. You know, the unix way. Do one thing, do it well. This is from my desktop machine: /usr/lib/systemd/systemd-reply-password /usr/lib/systemd/ntp-units.d /usr/lib/systemd/systemd-coredump /usr/lib/systemd/systemd-hostnamed /usr/lib/systemd/systemd-binfmt /usr/lib/systemd/systemd-localed /usr/lib/systemd/systemd-machined /usr/lib/systemd/systemd-sleep /usr/lib/systemd/system-generators /usr/lib/systemd/system-generators/systemd-system-update-generator /usr/lib/systemd/system-generators/systemd-gpt-auto-generator /usr/lib/systemd/system-generators/systemd-efi-boot-generator /usr/lib/systemd/system-generators/systemd-fstab-generator /usr/lib/systemd/system-generators/systemd-getty-generator /usr/lib/systemd/system-generators/gentoo-local-generator /usr/lib/systemd/systemd-fsck /usr/lib/systemd/systemd-bootchart /usr/lib/systemd/systemd-shutdown /usr/lib/systemd/systemd-random-seed /usr/lib/systemd/system-sleep /usr/lib/systemd/systemd-remount-fs /usr/lib/systemd/user-generators /usr/lib/systemd/systemd-sysctl /usr/lib/systemd/systemd-timedated /usr/lib/systemd/catalog /usr/lib/systemd/system-shutdown /usr/lib/systemd/systemd-udevd /usr/lib/systemd/systemd-multi-seat-x /usr/lib/systemd/systemd-cgroups-agent /usr/lib/systemd/systemd-user-sessions /usr/lib/systemd/systemd-journal-gatewayd /usr/lib/systemd/systemd-quotacheck /usr/lib/systemd/systemd-shutdownd /usr/lib/systemd/systemd-modules-load /usr/lib/systemd/systemd-backlight /usr/lib/systemd/systemd-ac-power /usr/lib/systemd/systemd-initctl /usr/lib/systemd/systemd-readahead /usr/lib/systemd/systemd-journald /usr/lib/systemd/systemd-activate /usr/lib/systemd/systemd /usr/lib/systemd/systemd-update-utmp /usr/lib/systemd/systemd-vconsole-setup /usr/lib/systemd/systemd-logind All of them are different tools providing one capability to systemd as a whole. So systemd is a collection of tools, where each one does one thing, and it does it well. By your definition, systemd perfectly follows the unix way. no, it isn't. How are those binaries talk to each other? Besides - why is garbage essential for booting in /usr? Looks broken. Broken by design. The worst form of broken. Use text to communicate. systemd can comunicate basically everything via text: centurion ~ # systemctl show sshd.service | head Id=sshd.service Names=sshd.service Requires=basic.target Wants=system.slice WantedBy=multi-user.target Conflicts=shutdown.target Before=shutdown.target multi-user.target After=syslog.target network.target auditd.service systemd-journald.socket basic.target system.slice Description=OpenSSH server daemon LoadState=loaded For performance reasons, some things are passed or stored as data. Bu everything works with text also. So, again, it passes your definition. oh? I can pipe that output into cat or any any daemon I like? Doesn't look like so. That stuff. That makes things easy. And flexible. And replaceable. Easy to whom? And systemd is more flexible that a lot of init systems, in my opinion including OpenRC. oh really? because everything is done by the magical Pöttering? All the configuration and APIs are documented, public and open source. Everything is replaceable if there is someone willing and able to write a replacement. and that has been debunked by others.
Re: [gentoo-user] Debian just voted in systemd for default init system in jessie
On Sun, Feb 16, 2014 at 2:58 PM, Volker Armin Hemmann volkerar...@googlemail.com wrote: Am 16.02.2014 21:08, schrieb Canek Peláez Valdés: On Sun, Feb 16, 2014 at 12:59 PM, Volker Armin Hemmann volkerar...@googlemail.com wrote: [ snip ] or it is an idiotic decision. Because features means complexity. Yeah, like the kernel. Complexity means bugs. Bugs get reported, bugs get fixes. Life goes on. You didn't answered this, did you? And you don't want complexity in PID1 or init. Let those 'features' be handled by their own specialists. Almost all the features of systemd live outside of PID 1. You know, the unix way. Do one thing, do it well. This is from my desktop machine: /usr/lib/systemd/systemd-reply-password /usr/lib/systemd/ntp-units.d /usr/lib/systemd/systemd-coredump /usr/lib/systemd/systemd-hostnamed /usr/lib/systemd/systemd-binfmt /usr/lib/systemd/systemd-localed /usr/lib/systemd/systemd-machined /usr/lib/systemd/systemd-sleep /usr/lib/systemd/system-generators /usr/lib/systemd/system-generators/systemd-system-update-generator /usr/lib/systemd/system-generators/systemd-gpt-auto-generator /usr/lib/systemd/system-generators/systemd-efi-boot-generator /usr/lib/systemd/system-generators/systemd-fstab-generator /usr/lib/systemd/system-generators/systemd-getty-generator /usr/lib/systemd/system-generators/gentoo-local-generator /usr/lib/systemd/systemd-fsck /usr/lib/systemd/systemd-bootchart /usr/lib/systemd/systemd-shutdown /usr/lib/systemd/systemd-random-seed /usr/lib/systemd/system-sleep /usr/lib/systemd/systemd-remount-fs /usr/lib/systemd/user-generators /usr/lib/systemd/systemd-sysctl /usr/lib/systemd/systemd-timedated /usr/lib/systemd/catalog /usr/lib/systemd/system-shutdown /usr/lib/systemd/systemd-udevd /usr/lib/systemd/systemd-multi-seat-x /usr/lib/systemd/systemd-cgroups-agent /usr/lib/systemd/systemd-user-sessions /usr/lib/systemd/systemd-journal-gatewayd /usr/lib/systemd/systemd-quotacheck /usr/lib/systemd/systemd-shutdownd /usr/lib/systemd/systemd-modules-load /usr/lib/systemd/systemd-backlight /usr/lib/systemd/systemd-ac-power /usr/lib/systemd/systemd-initctl /usr/lib/systemd/systemd-readahead /usr/lib/systemd/systemd-journald /usr/lib/systemd/systemd-activate /usr/lib/systemd/systemd /usr/lib/systemd/systemd-update-utmp /usr/lib/systemd/systemd-vconsole-setup /usr/lib/systemd/systemd-logind All of them are different tools providing one capability to systemd as a whole. So systemd is a collection of tools, where each one does one thing, and it does it well. By your definition, systemd perfectly follows the unix way. no, it isn't. How are those binaries talk to each other? dbus, which is about to be integrated into the kernel with kdbus. Besides - why is garbage essential for booting in /usr? Is not. Most of it is optional, in a server I have there are much less binaries. Looks broken. Broken by design. The worst form of broken. By your opinion, not others. Use text to communicate. systemd can comunicate basically everything via text: centurion ~ # systemctl show sshd.service | head Id=sshd.service Names=sshd.service Requires=basic.target Wants=system.slice WantedBy=multi-user.target Conflicts=shutdown.target Before=shutdown.target multi-user.target After=syslog.target network.target auditd.service systemd-journald.socket basic.target system.slice Description=OpenSSH server daemon LoadState=loaded For performance reasons, some things are passed or stored as data. Bu everything works with text also. So, again, it passes your definition. oh? I can pipe that output into cat or any any daemon I like? Doesn't look like so. But it does, you can cat with journalctl; it's one of its output options: -o, --output= cat generates a very terse output only showing the actual message of each journal entry with no meta data, not even a timestamp. That stuff. That makes things easy. And flexible. And replaceable. Easy to whom? And systemd is more flexible that a lot of init systems, in my opinion including OpenRC. oh really? because everything is done by the magical Pöttering? OK, sorry, I thought you wanted to have a civil, serious, technical conversation. I'm done with you in this thread. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
[gentoo-user] systemd - pulled IN "can not win" :-/
I have in
USE="gnome -qt4 -hal -arts -berkdb X qtk -qt3 -kde dvd alsa cdr cups apache2
ssl foomaticdb ppds mysql -acl \
java tiff png usb scanner gimp gimpprint cgi fam nptl truetype kpathsea type1
opengl tetex spell consolekit dbus policykit -systemd"
But some application managed to pull it IN.
How to fix this blockage?
[blocks B ] sys-apps/gentoo-systemd-integration
("sys-apps/gentoo-systemd-integration" is blocking sys-fs/udev-225-r1)
[blocks B ] sys-fs/udev ("sys-fs/udev" is blocking sys-apps/systemd-226-r2)
[blocks B ] sys-apps/systemd ("sys-apps/systemd" is blocking
sys-fs/udev-225-r1)
[blocks B ] sys-fs/udev ("sys-fs/udev" is blocking
sys-apps/gentoo-systemd-integration-6)
* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.
(sys-apps/systemd-226-r2:0/2::gentoo, ebuild scheduled for merge) pulled in by
>=sys-apps/systemd-207 required by
(sys-apps/gentoo-systemd-integration-6:0/0::gentoo, ebuild scheduled for merge)
sys-apps/systemd:0= required by (sys-apps/dbus-1.10.12:0/0::gentoo, ebuild
scheduled for merge)
(sys-fs/udev-225-r1:0/0::gentoo, installed) pulled in by
>=sys-fs/udev-208-r1 required by (virtual/udev-215:0/0::gentoo, installed)
>=sys-fs/udev-208-r1:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,static-libs?]
(>=sys-fs/udev-208-r1:0/0[abi_x86_32(-),abi_x86_64(-)]) required by
(virtual/libudev-215-r1:0/1::gentoo, installed)
# equery d sys-apps/systemd
* These packages depend on sys-apps/systemd:
app-admin/syslog-ng-3.7.3 (systemd ? sys-apps/systemd)
dev-lang/php-5.6.29 (systemd ? sys-apps/systemd)
gnome-base/gvfs-1.28.3-r1 (systemd ? sys-apps/systemd:0)
media-gfx/sane-backends-1.0.25-r1 (systemd ? sys-apps/systemd:0)
net-fs/samba-4.2.14 (systemd ? sys-apps/systemd:0)
net-libs/libvncserver-0.9.11-r1 (systemd ? sys-apps/systemd)
net-misc/openvpn-2.3.12 (systemd ? sys-apps/systemd)
net-nds/rpcbind-0.2.3-r1 (systemd ? sys-apps/systemd)
net-print/cups-2.1.4 (systemd ? sys-apps/systemd)
net-wireless/bluez-5.43 (systemd ? sys-apps/systemd)
sys-apps/dbus-1.10.12 (systemd ? sys-apps/systemd:0)
sys-apps/util-linux-2.28.2 (systemd ? sys-apps/systemd)
sys-auth/pambase-20150213 (systemd ? >=sys-apps/systemd-204[pam])
sys-auth/polkit-0.113 (systemd ? sys-apps/systemd:0)
sys-fs/udisks-2.1.8 (systemd ? >=sys-apps/systemd-209)
sys-process/procps-3.3.12 (systemd ? >=sys-apps/systemd-209)
virtual/libudev-215-r1 (systemd ?
>=sys-apps/systemd-212-r5:0/2[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?])
virtual/logger-0 (>=sys-apps/systemd-38)
virtual/service-manager-0 (kernel_linux ? sys-apps/systemd)
virtual/udev-215 (systemd ? >=sys-apps/systemd-208:0)
x11-base/xorg-server-1.18.4 (systemd ? sys-apps/systemd)
--
Thelma
Re: [gentoo-user] remove gnome/systemd
On Tue, Sep 12, 2017 at 5:20 PM, Heiko Baums <li...@baums-on-web.de> wrote: > Just to be absolutely sure put this line into > your /etc/portage/make.conf, too: > INSTALL_MASK="/lib/systemd /lib32/systemd /lib64/systemd /usr/lib/systemd > /usr/lib32/systemd /usr/lib64/systemd /etc/systemd" I would advise against this INSTALL_MASK setting. It is quite likely to break things (like sys-fs/udev). Its only value is to give a warm and fuzzy feeling to people who have an irrational hatred of systemd.
[gentoo-user] systemd: "local system does not support BPF/cgroup based firewalling"
I'm getting these at startup: systemd[1]: File /lib/systemd/system/systemd-journald.service:33 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling. systemd[1]: Proceeding WITHOUT firewalling in effect! systemd[1]: File /lib/systemd/system/systemd-udevd.service:32 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling. systemd[1]: Proceeding WITHOUT firewalling in effect! systemd[1]: File /lib/systemd/system/systemd-logind.service:34 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling. systemd[1]: Proceeding WITHOUT firewalling in effect! What do I need to make this work? I found this: https://github.com/systemd/systemd/issues/7188 But CONFIG_BPF_SYSCALL is enabled and I still get that message. This is on kernel 4.9.59 with systemd 235.
Re: [gentoo-user] network do not come up after booting, only manual reloading (systemd-networkd)
On Tue, Sep 7, 2021 at 3:21 PM Tamer Higazi wrote: [...] > Sep 07 22:15:19 tux systemd[1]: Starting Network Configuration... > Sep 07 22:15:19 tux systemd-networkd[958]: lo: Link UP > Sep 07 22:15:19 tux systemd-networkd[958]: lo: Gained carrier > Sep 07 22:15:19 tux systemd-networkd[958]: Enumeration completed > Sep 07 22:15:19 tux systemd[1]: Started Network Configuration. > Sep 07 22:15:20 tux systemd-networkd[958]: eth0: Interface name change > detected, renamed to enp6s0. > Sep 07 22:15:20 tux systemd-networkd[958]: eth1: Interface name change > detected, renamed to enp7s0. > The message "enp6s0: Link UP" never appears? My log is very similar: Aug 31 17:24:12 graphite systemd[1]: Starting Network Configuration... Aug 31 17:24:12 graphite systemd-networkd[453]: lo: Link UP Aug 31 17:24:12 graphite systemd-networkd[453]: lo: Gained carrier Aug 31 17:24:12 graphite systemd-networkd[453]: Enumeration completed Aug 31 17:24:12 graphite systemd[1]: Started Network Configuration. Aug 31 17:24:12 graphite systemd-networkd[453]: eth0: Interface name change detected, renamed to eno1. Aug 31 17:24:14 graphite systemd-networkd[453]: eno1: Link UP Aug 31 17:24:17 graphite systemd-networkd[453]: eno1: Gained carrier Aug 31 17:24:19 graphite systemd-networkd[453]: eno1: Gained IPv6LL The change from eth0 to eno1 happens *after* "Started Network Configuration", like yours, but my connection goes up immediately. Can you please do me a favour and execute on your machine: > systemctl list-dependencies --after systemd-networkd > > my one outputs this: > > tamer@tux ~ $ systemctl list-dependencies --after systemd-networkd > systemd-networkd.service > ● ├─-.mount > ● ├─system.slice > ● ├─systemd-journald.socket > ● ├─systemd-networkd.socket > ● ├─systemd-sysctl.service > ○ ├─systemd-sysusers.service > ○ ├─systemd-udev-settle.service > ● ├─systemd-udevd.service > ○ └─network-pre.target > Mine is: aztlan ~ # systemctl list-dependencies --after systemd-networkd systemd-networkd.service ● ├─-.mount ● ├─system.slice ● ├─systemd-journald.socket ● ├─systemd-networkd.socket ● ├─systemd-sysctl.service ○ ├─systemd-sysusers.service ● ├─systemd-udevd.service ● └─network-pre.target ○ └─iptables-restore.service In one machine, and kodi ~ # systemctl list-dependencies --after systemd-networkd systemd-networkd.service ● ├─-.mount ● ├─system.slice ● ├─systemd-journald.socket ● ├─systemd-networkd.socket ● ├─systemd-sysctl.service ○ ├─systemd-sysusers.service ● ├─systemd-udevd.service ○ └─network-pre.target In another. The only difference I see is the systemd-udev-settle.service, do you have it enabled it? What systemd-* services do you have enabled? I have: aztlan ~ # find /etc/systemd/system -name "systemd-*" -type l /etc/systemd/system/network-online.target.wants/systemd-networkd-wait-online.service /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service /etc/systemd/system/multi-user.target.wants/systemd-networkd.service /etc/systemd/system/sockets.target.wants/systemd-networkd.socket and kodi ~ # find /etc/systemd/system -name "systemd-*" -type l /etc/systemd/system/sockets.target.wants/systemd-networkd.socket /etc/systemd/system/network-online.target.wants/systemd-networkd-wait-online.service /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service /etc/systemd/system/multi-user.target.wants/systemd-resolved.service /etc/systemd/system/multi-user.target.wants/systemd-networkd.service Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: minimal installation CD iso is where?,
Am 06.08.2015 um 18:59 schrieb Jc García: OpenRC is there on the stage3, systemd isn't, if you don't think about systemd you get an OpenRC installation, I think it would confuse more people to talk about choosing init system(especially noobs) right at the beginning of the handbook. To get a really systemd-free system you unfortunately need to do two additional steps: 1. Add USE=-systemd to your /etc/portage/make.conf 2. Add INSTALL_MASK=/lib/systemd /lib32/systemd /lib64/systemd /usr/lib/systemd /usr/lib32/systemd /usr/lib64/systemd /etc/systemd to your /etc/portage/make.conf
[gentoo-user] banshee installation without systemd
Hello, after reading the thread about systemd somebody mentioned sys-fs/eudev. I decided used because I had systemd only to used udev and unmerge systemd. Now I can't use Banshee which I use as my music player because of the next dependency tree: banshee - gnome-base/gnome-settings-daemon - sys-apps/gentoo-systemd-integration - sys-apps/systemd and systemd can't be used because it conflicts with eudev. Is there anyway to avoid emerge systemd in this case? Thank you, Quim
[gentoo-user] preparing for the "systemd rootprefix migration"
I run a stable system using gnome3 and hence systemd, specifically systemd-236-r5. My bootloader is grub2. I do *not* have an EFI platform and do *not* have an initramfs. I do *not* have a separate /usr filesystem. The news item says that, in preparation for the 237 release and the likely removal of the symlinks /usr/lib/systemd/systemd and /usr/lib/systemd/systemd-shutdown we should update our boot config to reference init=/lib/systemd/system 1. Updating the boot config to reference init=/lib/systemd/system seems to mean a 1-line change in /etc/default/grub GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd" --> GRUB_CMDLINE_LINUX="init=/lib/systemd/systemd" followed by the usual grub-mkconfig -o /boot/grub/grub.cfg Is that it? 2. What should I be doing to prepare for the removal of the /usr/lib/systemd/systemd-shutdown symlink? 3. "After upgrading, please run systemctl daemon-reexec". Which upgrade is being referred to? Is it the upgrade to the 237 release, with the likely removal of the two symlinks. Thanks in advance, allan
Re: [gentoo-user] systemd - pulled IN "can not win" :-/
On 02/09/2017 08:30 PM, the...@sys-concept.com wrote:
> I have in
> USE="gnome -qt4 -hal -arts -berkdb X qtk -qt3 -kde dvd alsa cdr cups apache2
> ssl foomaticdb ppds mysql -acl \
> java tiff png usb scanner gimp gimpprint cgi fam nptl truetype kpathsea type1
> opengl tetex spell consolekit dbus policykit -systemd"
>
> But some application managed to pull it IN.
> How to fix this blockage?
>
>
> [blocks B ] sys-apps/gentoo-systemd-integration
> ("sys-apps/gentoo-systemd-integration" is blocking sys-fs/udev-225-r1)
> [blocks B ] sys-fs/udev ("sys-fs/udev" is blocking
> sys-apps/systemd-226-r2)
> [blocks B ] sys-apps/systemd ("sys-apps/systemd" is blocking
> sys-fs/udev-225-r1)
> [blocks B ] sys-fs/udev ("sys-fs/udev" is blocking
> sys-apps/gentoo-systemd-integration-6)
>
> * Error: The above package list contains packages which cannot be
> * installed at the same time on the same system.
>
> (sys-apps/systemd-226-r2:0/2::gentoo, ebuild scheduled for merge) pulled in
> by
> >=sys-apps/systemd-207 required by
> (sys-apps/gentoo-systemd-integration-6:0/0::gentoo, ebuild scheduled for
> merge)
> sys-apps/systemd:0= required by (sys-apps/dbus-1.10.12:0/0::gentoo,
> ebuild scheduled for merge)
>
> (sys-fs/udev-225-r1:0/0::gentoo, installed) pulled in by
> >=sys-fs/udev-208-r1 required by (virtual/udev-215:0/0::gentoo, installed)
>
> >=sys-fs/udev-208-r1:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,static-libs?]
> (>=sys-fs/udev-208-r1:0/0[abi_x86_32(-),abi_x86_64(-)]) required by
> (virtual/libudev-215-r1:0/1::gentoo, installed)
>
> # equery d sys-apps/systemd
>
> * These packages depend on sys-apps/systemd:
> app-admin/syslog-ng-3.7.3 (systemd ? sys-apps/systemd)
> dev-lang/php-5.6.29 (systemd ? sys-apps/systemd)
> gnome-base/gvfs-1.28.3-r1 (systemd ? sys-apps/systemd:0)
> media-gfx/sane-backends-1.0.25-r1 (systemd ? sys-apps/systemd:0)
> net-fs/samba-4.2.14 (systemd ? sys-apps/systemd:0)
> net-libs/libvncserver-0.9.11-r1 (systemd ? sys-apps/systemd)
> net-misc/openvpn-2.3.12 (systemd ? sys-apps/systemd)
> net-nds/rpcbind-0.2.3-r1 (systemd ? sys-apps/systemd)
> net-print/cups-2.1.4 (systemd ? sys-apps/systemd)
> net-wireless/bluez-5.43 (systemd ? sys-apps/systemd)
> sys-apps/dbus-1.10.12 (systemd ? sys-apps/systemd:0)
> sys-apps/util-linux-2.28.2 (systemd ? sys-apps/systemd)
> sys-auth/pambase-20150213 (systemd ? >=sys-apps/systemd-204[pam])
> sys-auth/polkit-0.113 (systemd ? sys-apps/systemd:0)
> sys-fs/udisks-2.1.8 (systemd ? >=sys-apps/systemd-209)
> sys-process/procps-3.3.12 (systemd ? >=sys-apps/systemd-209)
> virtual/libudev-215-r1 (systemd ?
> >=sys-apps/systemd-212-r5:0/2[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?])
> virtual/logger-0 (>=sys-apps/systemd-38)
> virtual/service-manager-0 (kernel_linux ? sys-apps/systemd)
> virtual/udev-215 (systemd ? >=sys-apps/systemd-208:0)
> x11-base/xorg-server-1.18.4 (systemd ? sys-apps/systemd)
I forgo to add:
grep systemd /etc/portage/package.use
# required by virtual/libudev-215-r1[-systemd]
# required by sys-apps/systemd-226-r2::gentoo
>=sys-apps/dbus-1.10.12 systemd
--
Thelma
Re: [gentoo-user] Re: Systemd upower
On Fri, Jun 6, 2014 at 1:46 AM, Mick michaelkintz...@gmail.com wrote: On Friday 06 Jun 2014 00:15:02 Peter Humphrey wrote: I bet you have quite a lot of systemd components lurking in the background though, ready to take over the world the next time you aren't looking :-) Ha! I can already see this one: 338 ?Ss 0:00 /lib/systemd/systemd-udevd --daemon I have set USE=-systemd, but if/when Gentoo migrates to systemd as the default startup I will probably have to remove it and then learn how to use systemd. That would be udev. It has been around long before systemd, and you must have missed the huge flamewar when they renamed it to systemd-udevd. Maybe we'll see java renamed to java-by-oracle-with-ask-toolbar next. :) If you ever migrate to systemd you really just need to set USE=systemd and install systemd. Portage will swap out your udev in the process, though nothing there will really change as systemd and udev install the same udev components. There is a guide for installing systemd that you should follow which gets into all the details. Rich
Re: [gentoo-user] Re: minimal installation CD iso is where?,
Am 08.08.2015 um 19:05 schrieb walt: I just noticed that net-misc/netifrc installs two systemd service files, which puzzled me. Is this in preparation for virtualizing openrc? This is to provide systemd users with the corresponding service files like OpenRC users get the necessary init scripts. Both are installed by netifrc and other packages. That's why I set: INSTALL_MASK=/lib/systemd /lib32/systemd /lib64/systemd /usr/lib/systemd /usr/lib32/systemd /usr/lib64/systemd /etc/systemd I don't use systemd, so I don't need and want those files. That said, I don't mind if systemd users get their service files like OpenRC users get their init scripts, but I don't let portage install the systemd related files on my system. I think this should actually be handled by USE=-systemd, and not by INSTALL_MASK. On the other hand maybe there should be a USE flag openrc which handles the installation of init scripts and OpenRC related stuff for people who want to use systemd instead of OpenRC.
Re: [gentoo-user] network do not come up after booting, only manual reloading (systemd-networkd)
On 9/5/21 12:46 AM, Tamer Higazi wrote: > Hi people, > > After upgrading my gentoo box i see a new behavior, that my machine > after boot doen't configure my network. My network is configured through > systemd-network, > > Only if I manually after login execute: "systemctl restart > systemd-network" it gets configured. > Can somebody tell me why this is the case and how to fix it ? > > systemctl Logs: > > after start: > > ● systemd-networkd.service - Network Configuration > Loaded: loaded (/lib/systemd/system/systemd-networkd.service; > enabled; vendor preset: enabled) > Active: active (running) since Sat 2021-09-04 08:49:48 CEST; 1min > 4s ago > TriggeredBy: ● systemd-networkd.socket > Docs: man:systemd-networkd.service(8) > Main PID: 957 (systemd-network) > Status: "Processing requests..." > Tasks: 1 (limit: 19136) > Memory: 2.3M > CGroup: /system.slice/systemd-networkd.service > └─957 /lib/systemd/systemd-networkd > > Sep 04 08:49:48 tux systemd[1]: Starting Network Configuration... > Sep 04 08:49:48 tux systemd-networkd[957]: lo: Link UP > Sep 04 08:49:48 tux systemd-networkd[957]: lo: Gained carrier > Sep 04 08:49:48 tux systemd-networkd[957]: Enumeration completed > Sep 04 08:49:48 tux systemd[1]: Started Network Configuration. > Sep 04 08:49:49 tux systemd-networkd[957]: eth0: Interface name change > detected, renamed to enp6s0. > Sep 04 08:49:49 tux systemd-networkd[957]: eth1: Interface name change > detected, renamed to enp7s0. > > after manually restart (systemctl restart systemd-networkd): > > > ● systemd-networkd.service - Network Configuration > Loaded: loaded (/lib/systemd/system/systemd-networkd.service; > enabled; vendor preset: enabled) > Active: active (running) since Sat 2021-09-04 08:51:47 CEST; 13s ago > TriggeredBy: ● systemd-networkd.socket > Docs: man:systemd-networkd.service(8) > Main PID: 1167 (systemd-network) > Status: "Processing requests..." > Tasks: 1 (limit: 19136) > Memory: 1.0M > CGroup: /system.slice/systemd-networkd.service > └─1167 /lib/systemd/systemd-networkd > > Sep 04 08:51:47 tux systemd[1]: Starting Network Configuration... > Sep 04 08:51:47 tux systemd-networkd[1167]: enp6s0: Link UP > Sep 04 08:51:47 tux systemd-networkd[1167]: enp6s0: Gained carrier > Sep 04 08:51:47 tux systemd-networkd[1167]: lo: Link UP > Sep 04 08:51:47 tux systemd-networkd[1167]: lo: Gained carrier > Sep 04 08:51:47 tux systemd-networkd[1167]: Enumeration completed > Sep 04 08:51:47 tux systemd[1]: Started Network Configuration. > Sep 04 08:51:48 tux systemd-networkd[1167]: enp6s0: Gained IPv6LL What does your networkd configuration look like? One thing that stands out from your example logs is that the first networkd startup seems to occur _before_ udev assigns predictable network interface names (eth0 -> enp6s0), I'm wondering if that's why it works after you later restart the daemon. I'm not a systemd expert -- perhaps there is a dependency ordering issue here? https://github.com/systemd/systemd/issues/7293
Re: [gentoo-user] OK, so not everything works properly with systemd
On 03/21/2015 02:46 PM, Canek Peláez Valdés wrote: They are; basically everything nowadays is systemd aware. Even OpenRC can now use some of its configurations. Could you run this immediately after booting: systemd-delta I've finally gotten around to doing this: [OVERRIDDEN] /etc/systemd/system/distccd.service → /usr/lib/systemd/system/distccd.service --- /usr/lib/systemd/system/distccd.service 2015-02-20 09:03:58.46960 -0800 +++ /etc/systemd/system/distccd.service 2015-03-12 14:49:15.145608558 -0700 @@ -4,7 +4,7 @@ [Service] User=distcc -ExecStart=/usr/bin/distccd --verbose --no-detach --daemon --port 3632 -N 15 --allow $ALLOWED_SERVERS +ExecStart=/usr/bin/distccd --verbose --no-detach --daemon --port 3632 -N 15 --allow 127.0.0.1 --allow $ALLOWED_SERVERS [Install] WantedBy=multi-user.target [EXTENDED] /etc/systemd/system/distccd.service → /etc/systemd/system/distccd.service.d/00gentoo.conf [EXTENDED] /run/systemd/system/session-1.scope → /run/systemd/system/session-1.scope.d/50-SendSIGHUP.conf [EXTENDED] /run/systemd/system/session-1.scope → /run/systemd/system/session-1.scope.d/50-After-systemd-user-sessions\x2eservice.conf [EXTENDED] /run/systemd/system/session-1.scope → /run/systemd/system/session-1.scope.d/50-After-systemd-logind\x2eservice.conf [EXTENDED] /run/systemd/system/session-1.scope → /run/systemd/system/session-1.scope.d/50-Description.conf [EXTENDED] /run/systemd/system/session-1.scope → /run/systemd/system/session-1.scope.d/50-Slice.conf [EXTENDED] /usr/lib/systemd/system/sntp.service → /etc/systemd/system/sntp.service.d/00gentoo.conf [EXTENDED] /usr/lib/systemd/system/ntpdate.service → /etc/systemd/system/ntpdate.service.d/00gentoo.conf 9 overridden configuration files found. I had to override distccd myself, as it didn't allow specifying multiple hosts. I did discover something else today, the shutdown target doesn't work either. I'm waiting for my array to rebuild. So the reboot and shutdown targets don't work, but the poweroff target seems to. I'm going to double-check that next. I did check my profile: [7] default/linux/amd64/13.0/desktop/kde/systemd * So I am built using a systemd profile. I'm getting a little confused. Dan
Re: [gentoo-user] systemd not starting wpa_supplicant after last update
On Wed, 11 Feb 2015 13:22:13 -0600, Canek Peláez Valdés wrote: I use NetworkManager for wireless connections, and systemd-networkd for static ethernet, so I don't use wpa_supplicant directly. However, I would suggest to simply enable wpa_supplicant@your-wireless-device.service. I have it set up like this % cat /etc/systemd/network/20-wlan0.network [Match] Name=wlan0 [Network] Description=Wireless network DHCP=yes % ls -l /etc/systemd/system/systemd-networkd.service.wants/ systemd-resolved.service - /usr/lib/systemd/system/systemd-resolved.service wpa_supplicant@wlan0.service - /usr/lib64/systemd/system/wpa_supplicant@.service -- Neil Bothwick Puritanism: The haunting fear that someone, somewhere may be happy. pgp8lzqX6zu8n.pgp Description: OpenPGP digital signature
[gentoo-user] Re: Change from udev to eudev?
wabe gmail.com> writes: > waltdnes waltdnes.org wrote: > I'm glad that gentoo users still have an alternative to systemd, and > hope that this will also be the case in future. Non Systemd has a very bright future. In clustering, Systemd is ok, even great for containers. In Hi Performance Computing types of clusters, systemd is loosing the battle. Many in these trenches believe that the cluster engines of HPC cluster architectures will vastly outperform clusters with systemd; thus eventually removing systemd from linux clusters where performance is important. Still, if you manage 1000 linux workstations, then systemd does have it's merits. > But I really don't wanna start another pro/con systemd thread here! ;-) Exactly. I just wanted to encourage the non-systemd folks that their future looks very bright. > Regards > wabe hth, James
Re: [gentoo-user] systemd-240 doesn't load my kernel modules
Hi! On Fri, 11 Jan 2019 13:14:07 +0100 Helmut Jarausch wrote: > Hi, > > I have systemd and openrc installed on my system, but I use openrc for > booting. > Upto systemd-239 this works just fine. > But with systemd-240 my system doesn't load necessary kernel modules > like DRM AMDGPU modules. > This break Xorg : > > (EE) open /dev/dri/card0: No such file or directory > > Has anybody an idea what is different under systemd-240 in comparison > to systemd-239? This is a known bug in udev-240 (and systemd-240): https://github.com/systemd/systemd/issues/11314 It should be fixed in the latest versions in tree. Best regards, Andrew Savchenko pgp9IVGM73nc3.pgp Description: PGP signature
Re: [gentoo-user] Re: Switching default tmpfiles and faster internet coming my way.
On Sun, 06 Dec 2020 10:45:38 +, Michael wrote: > Given M.Orlitzky's comments and discussions with systemd devs he > shared, what's the optimal solution for OpenRC users, who want to avoid > systemd? systemd-tmpfiles != systemd. Despite the claims that systemd is monolithic, it is not. It is an ecosystem comprised of many parts, some of which can be used without any other systemd components, like systemd-tmpfiles and systemd-boot, not to mention udev. Maybe the devs need to rename the systemd-tmpfiles package to satisfy those that break out in a sweat at the mention of the s-word :) -- Neil Bothwick I can't walk on water, but I can stagger on alcohol. pgpdUNg9s1gAH.pgp Description: OpenPGP digital signature
Re: [gentoo-user] [OT] Linus Torvalds on systemd
On 09/17/14 20:36, Volker Armin Hemmann wrote: [snip] It's an interesting read; I highly recommend it. [1] http://www.itwire.com/business-it-news/open-source/65402-torvalds-says-he-has-no-strong-opinions-on-systemd Now you use this to advertise for systemd? Systemd fanbois are becoming more and more desperate. I'll second it. I tried systemd and did not like it at all. -- Joseph
[gentoo-user] Gordian knot systemd / hwids
Hi systemd-249.6-r1 conflicts with sys-apps/hwids[udev] But when I remove the udev use flag, emerge sys-apps/hwids gives The following REQUIRED_USE flag constraints are unsatisfied: systemd? ( udev ) So, I would have to remove sys-apps/systemd-249.6 first. Is it save to emerge -C sys-apps/systemd ? Thanks for a hint, Helmut
[gentoo-user] Re: udev -> eudev
Neil Bothwick digimed.co.uk> writes:
> > emerge -uDtvp world reveals the same trouble::
> >
> > [ebuild R] sys-apps/dbus-1.8.16::gentoo USE="X systemd* -debug
> > -doc (-selinux) -static-libs {-test}" ABI_X86="32 (64) (-x32)" 0 KiB
> It also reveals the cause, not that you have used --tree. You are trying
> to rebuild dbus with the systemd USE flag, no wonder it wants systemd!
Agreed! In fact I have suspicioned either udev or dbus pretty early.
In fact I have -systemd in make.conf for a long time time, but somebody
got around that. I have this setting in package.use::
sys-apps/dbus -systemd
for a while now, but to no avail?
> Next step: grep -r systemd /etc/portage
# grep -r systemd /etc/portage
/etc/portage/package.mask:sys-apps/systemd
/etc/portage/package.mask:sys-apps/gentoo-systemd-integration
/etc/portage/make.conf:threads vaapi glamor python -systemd smp "
/etc/portage/package.use/package.use:sys-apps/dbus -systemd
/etc/portage/package.use/zzz-autounmask:>=sys-fs/udisks-2.1.4 systemd
/etc/portage/package.use/zzz-autounmask:# required by
sys-apps/systemd-226-r2::gentoo
/etc/portage/package.use/zzz-autounmask:# required by
sys-apps/gentoo-systemd-integration-4::gentoo
/etc/portage/package.use/zzz-autounmask:>=sys-apps/dbus-1.8.16 systemd
/etc/portage/package.unmask:# Needs sys-apps/systemd. Masked for non systemd
profiles.
/etc/portage/package.unmask:# required by sys-apps/dbus-1.8.16::gentoo[systemd]
/etc/portage/package.unmask:=sys-apps/systemd-226-r2
/etc/portage/package.unmask:# required by
sys-apps/systemd-226-r2::gentoo[-vanilla]
/etc/portage/package.unmask:# required by sys-fs/udisks-2.1.4::gentoo[systemd]
/etc/portage/package.unmask:=sys-apps/gentoo-systemd-integration-4
/etc/portage/make.conf.archive/make.conf.15mar2015:qt3support threads vaapi
glamor python -systemd smp "
/etc/portage/make.conf.archive/make.conf.3apr2015:qt3support threads vaapi
glamor python -systemd smp "
/etc/portage/make.conf.archive/make.conf.sept17-2015:threads vaapi glamor
python -systemd smp "
/etc/portage/make.conf.archive/make.conf.21jun2015:threads vaapi glamor
python -systemd smp "
/etc/portage/make.conf.archive/make.conf.24feb2015:qt3support threads vaapi
glamor python -systemd "
/etc/portage/make.conf.archive/make.conf.9nov2015:threads vaapi glamor
python -systemd smp "
/etc/portage/make.conf.archive/make.conf.backup.sep1-2015:threads vaapi
glamor python -systemd smp "
/etc/portage/make.conf.archive/make.conf.backup:threads vaapi glamor python
-systemd smp "
/etc/portage/package.USED.archive/package.use.orig:# required by
sys-auth/polkit-0.112[-systemd]
/etc/portage/package.USED.archive/package.use.orig:# required by
virtual/libgudev-215-r1[-systemd]
/etc/portage/package.USED.archive/package.use.orig:# required by
virtual/libudev-215-r1[-systemd]
/etc/portage/package.USED.archive/package.use.dist_:# required by
sys-auth/polkit-0.112[-systemd]
/etc/portage/make.conf.9nov2015:threads vaapi glamor python -systemd smp "
Yep, I'm all ears! Futher guidance ?
James
[gentoo-user] network do not come up after booting, only manual reloading (systemd-networkd)
Hi people, After upgrading my gentoo box i see a new behavior, that my machine after boot doen't configure my network. My network is configured through systemd-network, Only if I manually after login execute: "systemctl restart systemd-network" it gets configured. Can somebody tell me why this is the case and how to fix it ? systemctl Logs: after start: ● systemd-networkd.service - Network Configuration Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2021-09-04 08:49:48 CEST; 1min 4s ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 957 (systemd-network) Status: "Processing requests..." Tasks: 1 (limit: 19136) Memory: 2.3M CGroup: /system.slice/systemd-networkd.service └─957 /lib/systemd/systemd-networkd Sep 04 08:49:48 tux systemd[1]: Starting Network Configuration... Sep 04 08:49:48 tux systemd-networkd[957]: lo: Link UP Sep 04 08:49:48 tux systemd-networkd[957]: lo: Gained carrier Sep 04 08:49:48 tux systemd-networkd[957]: Enumeration completed Sep 04 08:49:48 tux systemd[1]: Started Network Configuration. Sep 04 08:49:49 tux systemd-networkd[957]: eth0: Interface name change detected, renamed to enp6s0. Sep 04 08:49:49 tux systemd-networkd[957]: eth1: Interface name change detected, renamed to enp7s0. after manually restart (systemctl restart systemd-networkd): ● systemd-networkd.service - Network Configuration Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2021-09-04 08:51:47 CEST; 13s ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 1167 (systemd-network) Status: "Processing requests..." Tasks: 1 (limit: 19136) Memory: 1.0M CGroup: /system.slice/systemd-networkd.service └─1167 /lib/systemd/systemd-networkd Sep 04 08:51:47 tux systemd[1]: Starting Network Configuration... Sep 04 08:51:47 tux systemd-networkd[1167]: enp6s0: Link UP Sep 04 08:51:47 tux systemd-networkd[1167]: enp6s0: Gained carrier Sep 04 08:51:47 tux systemd-networkd[1167]: lo: Link UP Sep 04 08:51:47 tux systemd-networkd[1167]: lo: Gained carrier Sep 04 08:51:47 tux systemd-networkd[1167]: Enumeration completed Sep 04 08:51:47 tux systemd[1]: Started Network Configuration. Sep 04 08:51:48 tux systemd-networkd[1167]: enp6s0: Gained IPv6LL
Re: [gentoo-user] systemd and gnome3
(I am assuming that you are using systemd-186 -- all earlier releases I checked have bugs I ran into) If it's right after logging in, then I would suspect some PAM deficiency. I wrote a bit about this on G+ yesterday: For anyone battling the trifecta of PAM, systemd and gnome on Gentoo, take note that once you've gotten rid of consolekit, you need to add the line: -sessionoptionalpam_systemd.so to system-auth, system-login and system-services in /etc/pam.d The first two are documented elsewhere but the last one ensures that gdm-welcome registers with systemd-logind, which fixed reboot from gdm and gnome not working for me. And, you need to get USE=-consolekit and mask consolekit, and you need to get pulseaudio rebuilt after installing systemd and you need to get =polkit-0.107 working. That last bit was a bit hairy for those who lived through it, but now I think it should do to: chown -R polkitd:polkitd /var/lib/polkit-1 Generally, as long as you start services the right way: systemctl start gdm.service (for example) and they start without error, the dependency checking should get all the dependencies started also. FWIW, here's the output of find /etc/systemd/system, but those are all symlinks to /usr/lib/systemd/system /etc/systemd/system/ /etc/systemd/system/bluetooth.target.wants /etc/systemd/system/bluetooth.target.wants/bluetooth.service /etc/systemd/system/default.target /etc/systemd/system/graphical.target.wants /etc/systemd/system/graphical.target.wants/rtkit-daemon.service /etc/systemd/system/graphical.target.wants/gdm.service /etc/systemd/system/multi-user.target.wants /etc/systemd/system/multi-user.target.wants/remote-fs.target /etc/systemd/system/multi-user.target.wants/ntpd.service /etc/systemd/system/multi-user.target.wants/NetworkManager.service /etc/systemd/system/getty.target.wants /etc/systemd/system/getty.target.wants/getty@tty1.service /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service /etc/systemd/system/local-fs.target.wants /etc/systemd/system/sysinit.target.wants /etc/systemd/system/network.target.wants /etc/systemd/system/network.target.wants/NetworkManager-wait-online.service /Peter
Re: [gentoo-user] Re: systemd? [ Was: The End Is Near ... ]
Eliezer Croitoru writes: i want to try this systemd thingy, where do is start at? http://wiki.gentoo.org/wiki/Systemd Wonko
[gentoo-user] Re: gentoo-systemd-only deprecation
On 31/07/13 18:26, Tanstaafl wrote: On 2013-07-31 11:20 AM, Canek Peláez Valdés can...@gmail.com wrote: If you don't use the systemd USE flag (and never install anything that depends on systemd), you will not get systemd installed, but many packages will install systemd unit files in /urs/lib/systemd/system. This unit files are little non-executable files which do nothing in your system, but some people feel really strongly about having anything in their machines with *systemd* in its path. If you want to exorcise those unit files, add /usr/lib/systemd/system to INSTALL_MASK. Ok, thanks Canek... but my last question remains... if this really is going to be the only and one true way to opt out of systemd, shouldn't this be well documented in the man page, as opposed to just generic references to masking 'files'...? Actually, this isn't how you opt out of systemd. You do that by having -systemd in your USE flags. Just because the unit files are present doesn't mean you're now using systemd.
Re: [gentoo-user] Re: Au revoir, gnome-3.8
Am 09.08.2013 07:19, schrieb Samuli Suominen: 2.02.99-r1 has it's own upstream systemd files in ~arch now (they are different from what the systemd-love overlay has, AFAIK) $ qlist lvm2 |grep systemd /usr/lib/systemd/system/dm-event.socket /usr/lib/systemd/system/dm-event.service /usr/lib/systemd/system/lvm2-monitor.service /usr/lib/systemd/system/blk-availability.service /usr/lib/systemd/system/lvm2-lvmetad.socket /usr/lib/systemd/system/lvm2-lvmetad.service /usr/lib/systemd/system-generators/lvm2-activation-generator Back then I had the issue that my LVs weren't correctly activated at boot time. That was not that much of a problem as the stuff necessary for booting wasn't on LVs but anyway. I worked around that with my own service-file ... I should/could try if the new unit-files work better (and check for the diffs). I wonder if I should get rid of the systemd-love overlay? After my initial learning curve I am quite happy with systemd on two of my gentoo systems. More and more packages bring their unit-files and things get better. Stefan
[gentoo-user] systemd and initramfs
Hi, what binaries and libraries have to be put into an initramfs for a system booting with init=/usr/lib/systemd/systemd ? (I am building the initramsfs myself) Thanks for some hints, Helmut
Re: [gentoo-user] udev upgrade 208 212-r1, openrc USE flag changed to disabled?
On Sat, Jun 14, 2014 at 4:39 PM, Alon Bar-Lev alo...@gentoo.org wrote: INSTALL_MASK=/lib/systemd /lib32/systemd /lib64/systemd /usr/lib/systemd /usr/lib32/systemd /usr/lib64/systemd /etc/systemd Warning to the reader: Please do not copy/paste this particular INSTALL_MASK setting. It may work with sys-fs/eudev, but it is quite likely to break your system if you are using sys-fs/udev. As well, the lib32 and lib64 entries should be unnecessary; systemd-related files are only installed in /lib/systemd and /usr/lib/systemd. Any package which installs them in lib32 or lib64 is doing it wrong and should be fixed. Bug reports are welcome. If you just want to exclude unit files, a much safer setting is this: INSTALL_MASK=/lib/systemd/system /usr/lib/systemd/system
Re: [gentoo-user] systemd
Am 17.08.2011 18:00, schrieb Stefan G. Weichinger: sshd.service gets started at boot, network.service not ... I linked multi-user.target to /etc/systemd/system/default.target, didn't help. Do I need that link? Solved, but dunno if done correctly. ln -sf /etc/systemd/system/network.service /etc/systemd/system/multi-user.target.wants ln -sf /lib/systemd/system/multi-user.target /etc/systemd/system/default.target S
Re: [gentoo-user] systemD?
On 08/30/2017 04:39 PM, mad.scientist.at.la...@tutanota.com wrote: > I do not want to start a whole systemd storm, glad i was offline for > that. however, in my case i'd really like to avoid systemd. can i > setup with out systemd, or do i need to remove and patch later. If you follow the handbook and skip the parts that say "if you want to use systemd..." then you'll end up without systemd.
Re: [gentoo-user] systemD?
kool, i can do that. thanks. -- The Power Of the People Is Stronger Than The People In Charge. 30. Aug 2017 14:54 by m...@gentoo.org: > On 08/30/2017 04:39 PM, > mad.scientist.at.la...@tutanota.com> wrote: >> I do not want to start a whole systemd storm, glad i was offline for >> that. however, in my case i'd really like to avoid systemd. can i >> setup with out systemd, or do i need to remove and patch later. > > If you follow the handbook and skip the parts that say "if you want to > use systemd..." then you'll end up without systemd.
Re: [gentoo-user] sys-apps/systemd-239-r2 does not install completely
Am 20.11.18 um 11:19 schrieb Neil Bothwick: > On Tue, 20 Nov 2018 10:49:27 +0100, Stefan G. Weichinger wrote: > >>> What version does "qlist ICv systemd" show? >> >> No version, just a long list of files. > > That should have been "qlist -ICv systemd" thanks -> # qlist -ICv systemd sys-apps/gentoo-systemd-integration-7 sys-apps/systemd-236-r5
[gentoo-user] systemd-240 doesn't load my kernel modules
Hi, I have systemd and openrc installed on my system, but I use openrc for booting. Upto systemd-239 this works just fine. But with systemd-240 my system doesn't load necessary kernel modules like DRM AMDGPU modules. This break Xorg : (EE) open /dev/dri/card0: No such file or directory Has anybody an idea what is different under systemd-240 in comparison to systemd-239? Many thanks for a hint, Helmut
Re: [gentoo-user] systemd - are we forced to switch?
Canek Peláez Valdés can...@gmail.com wrote: On Mon, Jul 22, 2013 at 9:58 PM, cov...@ccs.covici.com wrote: [ snip ] I have several things depending on consolekit: sys-auth/consolekit-0.4.5_p20120320-r2 pulled in by: gnome-base/gnome-control-center-3.8.3 requires sys-auth/consolekit Dependency of gnome-control-center: || ( ( app-admin/openrc-settingsd sys-auth/consolekit ) =sys-apps/systemd-31 ) gnome-base/gnome-session-3.8.2.1-r1 requires sys-auth/consolekit gnome-session: systemd? ( =sys-apps/systemd-183 ) !systemd? ( sys-auth/consolekit ) gnome-base/gnome-shell-3.8.3-r1 requires sys-auth/consolekit gnome-shell: || ( sys-auth/consolekit =sys-apps/systemd-31 ) sys-apps/accountsservice-0.6.30 requires sys-auth/consolekit accountsservice: systemd? ( =sys-apps/systemd-186 ) !systemd? ( sys-auth/consolekit ) sys-auth/pambase-20120417-r2 requires pambase: consolekit? ( =sys-auth/consolekit-0.4.5_p2012[pam] ) systemd? ( =sys-apps/systemd-44-r1[pam] ) =sys-auth/consolekit-0.4.5_p2012[pam] consolekit obviously doesn't depend on itself. sys-auth/polkit-0.111 requires sys-auth/consolekit[policykit] polkit: pam? ( systemd? ( sys-auth/pambase[systemd] ) !systemd? ( sys-auth/pambase[consolekit] ) ) In other words, *ALL* of these packages can use systemd instead of consolekit (and in the case of pambase, both at the same time). And, as Mark already linked[1]: ConsoleKit is currently not actively maintained. The focus has shifted to the built-in seat/user/session management of Software/systemd called systemd-loginctl, I would not really count on these packages supporting CK in the future. So, this implies if I want to keep using gnome then systemd is required, or use another desktop. That is something to think about. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] Re: Systemd upower
On Friday 06 Jun 2014 00:15:02 Peter Humphrey wrote: On Thursday 05 June 2014 13:58:45 Mick wrote: .., I've keyworded sys-power/upower-0.99.0 for now on one machine and it seems to work fine, without imposing systemd at the moment. :-) I bet you have quite a lot of systemd components lurking in the background though, ready to take over the world the next time you aren't looking :-) Ha! I can already see this one: 338 ?Ss 0:00 /lib/systemd/systemd-udevd --daemon I have set USE=-systemd, but if/when Gentoo migrates to systemd as the default startup I will probably have to remove it and then learn how to use systemd. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] udev upgrade 208 212-r1, openrc USE flag changed to disabled?
On 06/14/14 23:39, Alon Bar-Lev wrote: [snip] It means that openrc users should strongly consider migrate to eudev. I use eudev since its beta and never had any issue, nor systemd leaking into my system. And in addition add the following at make.conf, as it seems that we are enforced to have files we never use. INSTALL_MASK=/lib/systemd /lib32/systemd /lib64/systemd /usr/lib/systemd /usr/lib32/systemd /usr/lib64/systemd /etc/systemd How sys-fs/eudev differes from the one we are using sys-fs/udev -- Joseph
Re: [gentoo-user] udev upgrade 208 212-r1, openrc USE flag changed to disabled?
On Sun, Jun 15, 2014 at 5:15 AM, Joseph syscon...@gmail.com wrote: On 06/14/14 23:39, Alon Bar-Lev wrote: [snip] It means that openrc users should strongly consider migrate to eudev. I use eudev since its beta and never had any issue, nor systemd leaking into my system. And in addition add the following at make.conf, as it seems that we are enforced to have files we never use. INSTALL_MASK=/lib/systemd /lib32/systemd /lib64/systemd /usr/lib/systemd /usr/lib32/systemd /usr/lib64/systemd /etc/systemd How sys-fs/eudev differes from the one we are using sys-fs/udev http://article.gmane.org/gmane.linux.gentoo.devel/81901 -- Joseph
[gentoo-user] Re: systemd: "local system does not support BPF/cgroup based firewalling"
There is no such kernel option. On 28/10/17 21:21, Canek Peláez Valdés wrote: Do you have CONFIG_CGROUP_BPF enabled? Regards. On Sat, Oct 28, 2017 at 1:03 PM, Nikos Chantziaras <rea...@gmail.com <mailto:rea...@gmail.com>> wrote: I'm getting these at startup: systemd[1]: File /lib/systemd/system/systemd-journald.service:33 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling. systemd[1]: Proceeding WITHOUT firewalling in effect! systemd[1]: File /lib/systemd/system/systemd-udevd.service:32 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling. systemd[1]: Proceeding WITHOUT firewalling in effect! systemd[1]: File /lib/systemd/system/systemd-logind.service:34 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling. systemd[1]: Proceeding WITHOUT firewalling in effect! What do I need to make this work? I found this: https://github.com/systemd/systemd/issues/7188 <https://github.com/systemd/systemd/issues/7188> But CONFIG_BPF_SYSCALL is enabled and I still get that message. This is on kernel 4.9.59 with systemd 235.
Re: [gentoo-user] network do not come up after booting, only manual reloading (systemd-networkd)
I added the override because of that problem.
I removed the override:
tux /home/tamer # systemctl revert systemd-networkd
Removed /etc/systemd/system/systemd-networkd.service.d/override.conf.
Removed /etc/systemd/system/systemd-networkd.service.d.
tux /home/tamer #
tux /home/tamer # systemctl status systemd-networkd
● systemd-networkd.service - Network Configuration
Loaded: loaded (/lib/systemd/system/systemd-networkd.service;
enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-09-07 22:15:19 CEST; 23s ago
TriggeredBy: ● systemd-networkd.socket
Docs: man:systemd-networkd.service(8)
Main PID: 958 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 19136)
Memory: 2.3M
CGroup: /system.slice/systemd-networkd.service
└─958 /lib/systemd/systemd-networkd
Sep 07 22:15:19 tux systemd[1]: Starting Network Configuration...
Sep 07 22:15:19 tux systemd-networkd[958]: lo: Link UP
Sep 07 22:15:19 tux systemd-networkd[958]: lo: Gained carrier
Sep 07 22:15:19 tux systemd-networkd[958]: Enumeration completed
Sep 07 22:15:19 tux systemd[1]: Started Network Configuration.
Sep 07 22:15:20 tux systemd-networkd[958]: eth0: Interface name change
detected, renamed to enp6s0.
Sep 07 22:15:20 tux systemd-networkd[958]: eth1: Interface name change
detected, renamed to enp7s0.
... and I removed the link.
Can you please do me a favour and execute on your machine:
systemctl list-dependencies --after systemd-networkd
my one outputs this:
tamer@tux ~ $ systemctl list-dependencies --after systemd-networkd
systemd-networkd.service
● ├─-.mount
● ├─system.slice
● ├─systemd-journald.socket
● ├─systemd-networkd.socket
● ├─systemd-sysctl.service
○ ├─systemd-sysusers.service
○ ├─systemd-udev-settle.service
● ├─systemd-udevd.service
○ └─network-pre.target
What about yours ?
best, Tamer
Am 9/7/21 um 10:06 PM schrieb Canek Peláez Valdés:
On Tue, Sep 7, 2021 at 2:35 PM Tamer Higazi <mailto:th9...@googlemail.com>> wrote:
[Unit]
After=systemd-udev-settle.service
I think that's the problem; in my machines, that service is never run.
When did you add the override? What happens if you delete it? (Also
remove the [Link] section in your .network file).
Regards.
--
Dr. Canek Peláez Valdés
Profesor de Carrera Asociado C
Departamento de Matemáticas
Facultad de Ciencias
Universidad Nacional Autónoma de México
[gentoo-user] Pointers on how to speed up the boot process with systemd
Greetings fellow Gentooistas, I am looking for input on how to speed up my boot process with systemd on Gentoo. First of one word to systemd: Gentoo is about choice, and I choose to take a deeper look into systemd out of curiosity, so please respect that and don't turn it into another kind of OpenRC vs. systemd debate. Thanks in advance. Having said that, now to my setup: I am running the vanilla kernel 3.13.6 with only the necessary drivers builtin to the kernel, almost nothing as module. Features I don't need are disabled. Readahead-Services are disabled. Since my root partition is XFS, fsckd is disabled. systemd-analyze says: Startup finished in 584542y 2w 2d 20h 1min 35.953s (loader) + 1.477s (kernel) + 15.966s (userspace) = 17.444s Blame says: 1min 7.815s systemd-tmpfiles-clean.service 4.900s NetworkManager.service 3.214s systemd-logind.service 2.585s lightdm.service 2.373s systemd-vconsole-setup.service 1.506s systemd-update-utmp.service 919ms upower.service 697ms polkit.service 387ms systemd-udev-trigger.service 381ms systemd-sysctl.service 374ms tmp.mount 359ms udisks2.service 334ms kmod-static-nodes.service 333ms user@0.service 332ms systemd-user-sessions.service 299ms systemd-tmpfiles-setup-dev.service 288ms sys-fs-fuse-connections.mount 287ms systemd-remount-fs.service 228ms systemd-tmpfiles-setup.service 178ms systemd-random-seed.service 117ms systemd-fsck-root.service 103ms systemd-journal-flush.service 71ms wpa_supplicant.service 65ms accounts-daemon.service 51ms user@1000.service 35ms systemd-udevd.service 22ms alsa-restore.service Critical Chain says: The time after the unit is active or started is printed after the @ character. The time the unit takes to start is printed after the + character. graphical.target @15.965s └─multi-user.target @15.965s └─NetworkManager.service @11.065s +4.900s └─basic.target @11.065s └─timers.target @11.064s └─systemd-tmpfiles-clean.timer @11.043s └─sysinit.target @4.264s └─systemd-vconsole-setup.service @1.891s +2.373s └─systemd-journald.socket @1.572s └─-.mount @1.571s └─system.slice @1.947s └─-.slice @1.947s Boot disk is a normal HDD SATA. GDM-Replacement is lightdm. So i wonder what could I do to speedup the boot process any further? Thanks in advance.
Re: [gentoo-user] gdm fails to start
On Mon, 2017-05-22 at 16:09 +0200, Hogren wrote: > Hello, > > Very simple question but did you have "pam" in your global USE flag > or > Systemd USE flag ? Yes, I am using the gnome/systemd profile: # euse -I pam global use flags (searching: pam) no matching entries found local use flags (searching: pam) [+ D ] pam (net-dialup/ppp): Enables PAM (Pluggable Authentication Modules) support [+ D ] pam (sys-apps/util-linux): build runuser helper # euse -I systemd global use flags (searching: systemd) No matching entries found local use flags (searching: systemd) ******** [+ D ] systemd (gnome-extra/gnome-system-monitor): Display sys-apps/systemd metadata, e.g. unit names, for running processes [+ D ] systemd (media-sound/pulseaudio): Build with sys-apps/systemd support to replace standalone ConsoleKit. [+ D ] systemd (sys-apps/accountsservice): Use sys-apps/systemd instead of sys-auth/consolekit for session tracking [+ D ] systemd (sys-apps/busybox): Support systemd [+ D ] systemd (sys-apps/dbus): Build with sys-apps/systemd at_console support [+ D ] systemd (sys-auth/pambase): Use pam_systemd module to register user sessions in the systemd control group hierarchy. [+ D ] systemd (sys-auth/polkit): Use sys-apps/systemd instead of sys-auth/consolekit for session tracking [+ D ] systemd (sys-fs/udisks): Support sys-apps/systemd's logind # grep USE= /etc/portage/make.conf USE="-bluetooth -cups -cdr -dvd -dvdr -fortran -games -ipv6 -kde -libav -modemmanager -ppp -qt -qt3 -qt4 -shotwell -wifi" > > If this is on the first, did you compile systemd and may be > dependencies > after add it ? I'm not sure I understood the question: the box was initially LXDE/OpenRC; I installed and booted into systemd and got the system up again; then I installed Gnome and removed LXDE. Out of ideas I also recently did an 'emerge -e world'. > > Did you try that: > > > systemctl reset-failed| > > For a guy on github, that solve (without explanation) the problem: > > > > https://github.com/coreos/bugs/issues/1498| > > > > I just tried it and also the other tip mentioned in the bug (modification in the /etc/pam.d/systemd-user), no change. raffaele
Re: [gentoo-user] Re: Au revoir, gnome-3.8
On 09/08/13 01:59, walt wrote: On 08/07/2013 06:17 PM, Canek Peláez Valdés wrote: And in particular, all the GNOME stack includes their necessary unit files. That's good to know. The only reason I haven't already made the switch to systemd is lvm2 -- I just couldn't puzzle out how to get lvm2 started and get the needed logical volumes active and mounted before fstab is read during bootup. I think arch has unit files for lvm2, but I've been too busy to work on it lately. I'll get there eventually. 2.02.99-r1 has it's own upstream systemd files in ~arch now (they are different from what the systemd-love overlay has, AFAIK) $ qlist lvm2 |grep systemd /usr/lib/systemd/system/dm-event.socket /usr/lib/systemd/system/dm-event.service /usr/lib/systemd/system/lvm2-monitor.service /usr/lib/systemd/system/blk-availability.service /usr/lib/systemd/system/lvm2-lvmetad.socket /usr/lib/systemd/system/lvm2-lvmetad.service /usr/lib/systemd/system-generators/lvm2-activation-generator
[gentoo-user] [~amd64] Hint for bonehead systemd users (like me)
I've been struggling with today's update of systemd on ~arch because the ebuild keeps accusing me of using a compatibility symlink to run systemd during bootup. Yes, guilty as charged, I told grub2 to use /usr/bin/systemd as 'init', when /usr/bin/systemd has been, until now, a symlink to /usr/lib/systemd/systemd. Yes, I pled guilty to this crime and changed my /boot/grub2/grub.cfg to use /usr/lib/systemd/systemd instead of /usr/bin/systemd -- and yet I got the same condemnation every time I tried to emerge -auND world. An additional glass of chardonnay didn't solve this frustration, so I dared to read the systemd ebuild, which confessed that it reads the value of /proc/1/cmdline to find me guilty and ignores my new /boot/grub2/grup.cfg, which would have proved my innocence. IOW, you must reboot after changing your grub.cfg before the ebuild will withdraw it's accusation. HTH someone avoid the same problem. Cheers :)
Re: [gentoo-user] Re: Debian just voted in systemd for default init system in jessie
On Tue, Feb 18 2014, Canek Peláez Valdés wrote: On Tue, Feb 18, 2014 at 2:19 AM, Nicolas Sebrecht nsebre...@piing.fr wrote: The 17/02/14, Canek Peláez Valdés wrote: It depends; right now you can't switch back and forth between OpenRC and systemd without reemerging some stuff. Interesting. Didn't know that. What packages need to be recompiled? Some packages need to be emerged with USE=-systemd when going from systemd to OpenRC, and with USE=systemd the other way around. Different code paths are selected in each case. I think the consolekit USE flag also has to be changed. Systemd: USE=+systemd -consolkit OpenRC: USE=-systemd +consolkit At least that is what I did when I switched OpenRC--Systemd (with Canek's help). Now I have no global USE flags, thanks to the systemd subprofile. newlap-wireless gottlieb # eselect profile show Current /etc/portage/make.profile symlink: default/linux/amd64/13.0/desktop/gnome/systemd newlap-wireless gottlieb # allan
Re: [gentoo-user] Re: Systemd upower
On Friday 06 Jun 2014 12:18:09 Rich Freeman wrote: That would be udev. It has been around long before systemd, and you must have missed the huge flamewar when they renamed it to systemd-udevd. Maybe we'll see java renamed to java-by-oracle-with-ask-toolbar next. :) TBH I wouldn't be surprised. At least java offers a choice of avoiding it. ;-) If you ever migrate to systemd you really just need to set USE=systemd and install systemd. Portage will swap out your udev in the process, though nothing there will really change as systemd and udev install the same udev components. There is a guide for installing systemd that you should follow which gets into all the details. I didn't miss the flamewar. Actually I recall joining in the fun and posting the odd message about systemd. I know that I could use eudev or systemd-udev (or even mdev as kindly shared in this list by Walter). I am mostly happy with openrc and therefore have no reason to move to the systemd monoculture, unless gentoo falls in line with Debian et al. and leaves me no choice. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] Re: --depclean wants to remove udev. What!?
Dale wrote: > > root@fireball / # equery d sys-apps/systemd-utils > * These packages depend on sys-apps/systemd-utils: > sys-apps/systemd-tmpfiles-250 (sys-apps/systemd-utils[tmpfiles]) > sys-fs/udev-250 (sys-apps/systemd-utils[udev,...]) > virtual/libudev-232-r7 (!systemd ? sys-apps/systemd-utils[udev,...]) > virtual/tmpfiles-0-r3 (!prefix-guest ? sys-apps/systemd-utils[tmpfiles]) > virtual/udev-217-r5 (sys-apps/systemd-utils[udev]) Looks completely sane: sys-apps/systemd-tmpfiles-250 and sys-fs/udev-250 are "practically" just virtuals which only pull in sys-apps/systemd-utils with the corresponding USE-flags. And the "true" virtuals for for tmpfiles and udev also depend on that package with the corresponding USE-flags.
Re: [gentoo-user] systemd - are we forced to switch?
On Mon, Jul 22, 2013 at 9:58 PM, cov...@ccs.covici.com wrote: [ snip ] I have several things depending on consolekit: sys-auth/consolekit-0.4.5_p20120320-r2 pulled in by: gnome-base/gnome-control-center-3.8.3 requires sys-auth/consolekit Dependency of gnome-control-center: || ( ( app-admin/openrc-settingsd sys-auth/consolekit ) =sys-apps/systemd-31 ) gnome-base/gnome-session-3.8.2.1-r1 requires sys-auth/consolekit gnome-session: systemd? ( =sys-apps/systemd-183 ) !systemd? ( sys-auth/consolekit ) gnome-base/gnome-shell-3.8.3-r1 requires sys-auth/consolekit gnome-shell: || ( sys-auth/consolekit =sys-apps/systemd-31 ) sys-apps/accountsservice-0.6.30 requires sys-auth/consolekit accountsservice: systemd? ( =sys-apps/systemd-186 ) !systemd? ( sys-auth/consolekit ) sys-auth/pambase-20120417-r2 requires pambase: consolekit? ( =sys-auth/consolekit-0.4.5_p2012[pam] ) systemd? ( =sys-apps/systemd-44-r1[pam] ) =sys-auth/consolekit-0.4.5_p2012[pam] consolekit obviously doesn't depend on itself. sys-auth/polkit-0.111 requires sys-auth/consolekit[policykit] polkit: pam? ( systemd? ( sys-auth/pambase[systemd] ) !systemd? ( sys-auth/pambase[consolekit] ) ) In other words, *ALL* of these packages can use systemd instead of consolekit (and in the case of pambase, both at the same time). And, as Mark already linked[1]: ConsoleKit is currently not actively maintained. The focus has shifted to the built-in seat/user/session management of Software/systemd called systemd-loginctl, I would not really count on these packages supporting CK in the future. Regards. [1] http://www.freedesktop.org/wiki/Software/ConsoleKit/ -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
[gentoo-user] blocking -systemd
I have in make.conf USE: ... -systemd
But gnome-base/gnome-settings-daemon wants to pull in systemd-208
so I need to emerge sys-apps/systemd-208-r2 and I have installed udev which
conflicts with systemd.
Do I need to unmerge udev and emerge systemd. I'm not planning on switching to systemd after recent experience. So I was planning on avoiding it but I don't know
if I can.
emerge -1avq gnome-base/gnome-settings-daemon
* Last emerge --sync was 45d 2h 15m 32s ago.
[ebuild N] sys-apps/systemd-208-r2 USE=filecaps firmware-loader gudev introspection kmod pam policykit tcpd -acl -audit -cryptsetup -doc -gcrypt -http -lzma
-python -qrcode (-selinux) {-test} -vanilla -xattr PYTHON_SINGLE_TARGET=python2_7 PYTHON_TARGETS=python2_7
[ebuild N] sys-apps/gentoo-systemd-integration-2
[uninstall] sys-auth/nss-myhostname-0.3
[blocks b ] =sys-apps/systemd-197 (=sys-apps/systemd-197 is blocking sys-auth/nss-myhostname-0.3)
[blocks b ] sys-auth/nss-myhostname (sys-auth/nss-myhostname is blocking
sys-apps/systemd-208-r2)
[uninstall] app-admin/openrc-settingsd-1.0.1 USE=-systemd
[ebuild R ] gnome-base/gnome-settings-daemon-3.8.6.1 USE=colord cups i18n policykit short-touchpad-timeout udev -debug (-openrc-force) (-packagekit) {-test}
INPUT_DEVICES=-wacom
[blocks B ] sys-fs/udev (sys-fs/udev is blocking sys-apps/systemd-208-r2)
[blocks B ] sys-apps/systemd (sys-apps/systemd is blocking
sys-fs/udev-208, app-admin/openrc-settingsd-1.0.1)
* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.
(sys-apps/systemd-208-r2::gentoo, ebuild scheduled for merge) pulled in by
sys-apps/systemd required by
(gnome-base/gnome-settings-daemon-3.8.6.1::gentoo, ebuild scheduled for merge)
=sys-apps/systemd-208:0/1[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,gudev?,introspection?,kmod?,selinux?,static-libs(-)?]
(=sys-apps/systemd-208:0/1[abi_x86_32(-),gudev,introspection,kmod]) required
by (virtual/udev-208::gentoo, installed)
=sys-apps/systemd-207 required by
(sys-apps/gentoo-systemd-integration-2::gentoo, ebuild scheduled for merge)
(sys-fs/udev-208::gentoo, installed) pulled in by
sys-fs/udev required by @selected
--
Joseph
Re: [gentoo-user] Unlocking Plasma desktop in Gentoo without systemd
On Monday, 11 September 2017 19:18:30 BST Stroller wrote: > > On 11 Sep 2017, at 18:49, Mick <michaelkintz...@gmail.com> wrote: > > > > … > > "The screen locker is broken and unlocking is not possible anymore. > > In order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2), > > log in and execute the command: > > > > loginctl unlock-sessions > > > > ... > > > > If this is a default Gentoo installation with openrc, why does a default > > plasma desktop screenlocker comes up with this nonsense? > > Is it possible some of your KDE components were emerged with USE="systemd"? > > Try something like `emerge -pN world`? > > Stroller. Thanks Stroller, but no, this PC never had any systemd component, on purpose: # emerge -pN world These are the packages that would be merged, in order: Calculating dependencies... done! I had disabled USE flag 'systemd' in make.conf as soon as this flag was established: $ euse -I systemd global use flags (searching: systemd) **** local use flags (searching: systemd) **** [- c] systemd (dev-qt/qtcore): Enable native journald logging support [- c] systemd (media-sound/pulseaudio): Build with sys-apps/systemd support to replace standalone ConsoleKit. [- c] systemd (sys-apps/accountsservice): Use sys-apps/systemd instead of sys-auth/consolekit for session tracking [- c] systemd (sys-apps/busybox): Support systemd [- c] systemd (sys-apps/dbus): Build with sys-apps/systemd at_console support [- c] systemd (sys-auth/pambase): Use pam_systemd module to register user sessions in the systemd control group hierarchy. [- c] systemd (sys-auth/polkit): Use sys-apps/systemd instead of sys-auth/consolekit for session tracking [- c] systemd (sys-fs/udisks): Support sys-apps/systemd's logind The interesting thing is I never enabled screen locking, so plasma ought to be running with default settings. If such a setting causes the session to become inaccessible it should have been disabled by default. There may have been a warning about it in the past, but I can't recall it. The funny thing was the user thought her machine was being hacked! o_O I tried to pacify her by explaining that without systemd stack the attack surface should be smaller. ;-p -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] sys-apps/systemd-239-r2 does not install completely
Am 20.11.18 um 10:19 schrieb Neil Bothwick: > On Mon, 19 Nov 2018 10:14:01 +0100, Stefan G. Weichinger wrote: > >>>> upgrading from sys-apps/systemd-236-r5 to 239-r2 >>>> >>>> the emerge runs through and warns me that it overwrites files >>>> ... so it merges only partially ... >>> >>> What's the exact error message? You may get a suggested >>> solution based on this vague description of the problem but it >>> may not be the right one, or even safe. >>> >>> Normally emerge will put up a warning like this before >>> installing anything. >> >> pasted error msg below >> >> --- >> >> * Package 'sys-apps/systemd-239-r2' merged despite file >> collisions. If * necessary, refer to your elog messages for the >> whole content of the * above message. > > According to this the file collisions were ignore and the updated > package installed, so either something else prevented the > installation from completing or eix is confused. > > What version does "qlist ICv systemd" show? No version, just a long list of files. > How about "ls -ld /var/db/pkg/sys-apps/systemd-*"? # ls -ld /var/db/pkg/sys-apps/systemd-* drwxr-xr-x 2 root root 4096 May 15 2018 /var/db/pkg/sys-apps/systemd-236-r5 but: # systemctl --version systemd 239 and to even make it more interesting: # dmesg -t | grep systemd # last lines ... [Sat Nov 17 10:42:14 2018] systemd[1]: systemd 238 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK -SYSVINIT +UTMP -LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL -XZ +LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 -IDN +PCRE2 default-hierarchy=hybrid) [Sat Nov 17 10:42:14 2018] systemd[1]: Detected architecture x86-64. [Sat Nov 17 10:42:14 2018] systemd[1]: File /lib/systemd/system/systemd-journald.service:35 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling. [Sat Nov 17 10:42:14 2018] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.) [Sat Nov 17 10:51:01 2018] systemd[1]: Reloading. [Sat Nov 17 10:51:01 2018] systemd[1]: /lib/systemd/system/systemd-journald.service:32: Unknown system call group, ignoring: @system-service [Sat Nov 17 10:51:01 2018] systemd[1]: /lib/systemd/system/systemd-udevd.service:28: Unknown lvalue 'PrivateMounts' in section 'Service' [Sat Nov 17 10:51:01 2018] systemd[1]: /lib/systemd/system/systemd-udevd.service:32: Unknown system call group, ignoring: @system-service [Sat Nov 17 10:51:01 2018] systemd[1]: /lib/systemd/system/systemd-timesyncd.service:41: Unknown system call group, ignoring: @system-service [Sat Nov 17 10:51:01 2018] systemd[1]: /lib/systemd/system/systemd-machined.service:26: Unknown system call group, ignoring: @system-service [Sat Nov 17 10:51:01 2018] systemd[1]: /lib/systemd/system/systemd-logind.service:33: Unknown system call group, ignoring: @system-service [Sat Nov 17 10:51:01 2018] systemd[1]: /lib/systemd/system/systemd-resolved.service:41: Unknown system call group, ignoring: @system-service [Sat Nov 17 10:51:01 2018] systemd[1]: /lib/systemd/system/systemd-networkd.service:38: Unknown system call group, ignoring: @system-service [Mon Nov 19 19:26:34 2018] systemd-journald[226]: Failed to set ACL on /var/log/journal/9ce1e483f41dcc57a00e5611521d1771/user-1018.journal, ignoring: Operation not supported
Re: [gentoo-user] gentoo-systemd-only deprecation
On 2013-07-31 8:22 AM, Neil Bothwick n...@digimed.co.uk wrote: On Wed, 31 Jul 2013 07:34:22 -0400, Tanstaafl wrote: Where is this 'INSTALL_MASK' option for opting out of systemd completely documented? man make.conf Thanks but... I didn't see one word mention of systemd. So, how should this be used to 'opt out of systemd completely'?
Re: [gentoo-user] LVM2+mdraid5+LUKS+systemd (was Re: LVM2+mdraid+systemd)
Am 25.09.2013 01:38, schrieb Canek Peláez Valdés: systemd-analyze blame to see what is taking so long. systemd-delta to see what changes from upstream do you have. Thanks ... I cleaned up some cruft already and will test some boot-process soon. Still on the road ...
[gentoo-user] [~amd64] Recent spurious error messages from systemd?
For example, during bootup, systemd said that swap.target failed, but in fact swap was working normally when I logged in, and systemctl status swap.target showed no error messages. systemd also warned that lvm.service failed, but in fact the lvm drive was mounted and working as expected after I logged in. Anyone else seeing strange error messages from systemd during boot?
[gentoo-user] going from systemd to udev
Is it possible to go from systemd to udev? I don't like the way systemd works. I have a problem with mounting USB sick (it mounts as root:root) and I can not even change the permission. I am receiving Hylafax fax transmission reports (email) on all incoming faxes and now these emails are empty. It all start happening after switching to systemd :-( -- Joseph
[gentoo-user] systemd-networkd: simpler config for my network
Aside from all the discussions around systemd, I simply gave the new systemd-networkd a try. It helped me to simplify my config for my main machine where I run KVM for virtualization and need a network bridge: http://www.oops.co.at/en/publications/systemd-networkd-network-configuration-for-a-kvm-server Maybe someone else can make use of that as well. Stefan
Re: [gentoo-user] Can't Get Systemd to Work
Am 16.05.2014 16:00, schrieb Jc García: The same again you are mistyping systemd, is /usr/lib/systemd/systemd read carefully what you copy, and verify always those paths really exist. If you had done this, you would have noticed /usr/lib/system/system doesn't exist at all. ( Ah, I only spotted one missing d ... *oops* )
Re: [gentoo-user] Systemd upower
On 6/3/2014 11:10 AM, Canek Peláez Valdés can...@gmail.com wrote: Maybe. The thing is, this is going to keep happening, as more and more infrastructure migrates towards systemd. Perhaps a news item everytime it happens is unrealistic? Weren't you the one saying that those of us who were voicing concerns that systemd proponents were ultimately wanting to FORCE systemd on everyone were just scare-mongering conspiracy theorists?
Re: [gentoo-user] sys-power/upower with systemd
On 24/06/2014 10:08, Helmut Jarausch wrote: On 06/24/2014 10:01:24 AM, Marc Joliet wrote: Am Mon, 23 Jun 2014 20:39:13 -0400 schrieb gottl...@nyu.edu: I think I had first misinterpreted the news msg, but want to be sure I do understand it correctly now. The message ends with All non-systemd users are recommended to choose between: # emerge --oneshot --noreplace 'sys-power/upower-pm-utils' or # emerge --oneshot --noreplace '=sys-power/upower-0.99.0' However, all systemd users are recommended to stay with sys-power/upower. I first read stay with sys-power/upower to mean systemd users should NOT do any of the two options for non-systemd users and let portage do its thing. However, portage want to replace upower with upower-pm-utils, which I am pretty sure is not intended for systemd users. Is the proper reading of the news message, that the systemd users should use the second option available for non-systemd users? Specifically am I to execute # emerge --oneshot --noreplace '=sys-power/upower-0.99.0' ? Um, personally, I think the message is extremely clear: non-systemd users should choose between the first two options, and systemd users should just stick with plain upower, regardless of version (although there is only one ATM, the older one is masked now). Hi, please tell me - what is a systemd user? A systemd user is someone who has systemd installed and *is using it* How can that be unclear? I have systemd AND openrc installed here and I still don't use systemd as my init system. Am I a systemd user? I ask because I cannot installed some packages, some require upower-0.99.0 others fail with it. Thanks, Helmut -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] [OT] Linus Torvalds on systemd
Am 17.09.2014 20:36, schrieb Volker Armin Hemmann: Now you use this to advertise for systemd? Systemd fanbois are becoming more and more desperate. Gentoo is still all about choice, right? And we still have that choice. If you dislike Systemd, then just don't use it. Period. Contrary to many other distributions, like Debian or Arch Linux, we still have that kind of choice.
Re: [gentoo-user] alternative kernels
On Sunday, October 26, 2014 02:16:24 PM Canek Peláez Valdés wrote: And with systemd, rebooting to a new kernel takes just a few seconds ;) And here I was thinking that the pro-systemd crowd doesn't care about the boot-time of systemd? (See the [OT} Linus Torvalds on systemd thread around 18 - 21 september) Please make up your mind on this. -- Joost
Re: [gentoo-user] Debian forked, because of systemd brouhaha
On 11/30/2014 05:13 AM, Neil Bothwick wrote: systemd isn't monolithic so I can only assume you are referring to the Linux kernel here :) systemd most certainly is monolithic as well as modular. You can't run journald without systemd and you most certainly can't replace journald with a third party binary. Dan
Re: [gentoo-user] Re: minimal installation CD iso is where?,
Am 08.08.2015 um 00:28 schrieb Rich Freeman: Udev installs into such a path, and currently does not depend on systemd (in fact, they block each other). They block each other because udev is part of systemd. So if you install systemd you already have udev and don't need the separate udev package. Regarding the separate udev package, at least regarding eudev I would consider this a bug, because those systemd directories are systemd specific and don't belong to the FHS. If Poettering wants to break Unix, Linux and POSIX standards, it's up to him. Packages that don't belong to Poettering's software are supposed to follow those standards and do it so far. But remember, udev is part of systemd and announced to break on non-systemd systems. So udev is not a valid example here. Obviously you don't use udev, but in general as more stuff ends up in systemd you'll probably find more important stuff with systemd in the filename. Why would it? This again would be a reason for a bug report. Or do you consider every important stuff to be part of systemd? Do you really believe that there will be no other important stuff than systemd resp. that systemd will be the only init system or system managing system? Question again: That sounds exactly like those Poetterix fanboys, particularly when they forced systemd on every user of certain distros whether they wanted it or not. I don't need to be worried, that this will happen with Gentoo either anytime soon? I'd suggest taking the time to understand what it is before you decide that you don't want it (speaking generally, I'm not suggesting that you didn't know what you're doing when you switched to eudev). Heck, even gummiboot is being merged into systemd. Bad example again. Gummiboot was originally developed by Kay Sievers, one of Poettering's fanboys and co-developer of systemd. So a no-go anyway, and no surprise that it got merged into systemd.
Re: [gentoo-user] Re: systemd, libgudev and bug 552036
On Fri, Dec 18, 2015 at 10:51 PM, Jonathan Callen <jcal...@gentoo.org> wrote: > The python USE flag has been removed > from newer stable versions of sys-apps/systemd (in favor of > dev-python/python-systemd), but dev-python/python-systemd is not yet > stable. Thanks for catching that; I will file a stablereq right away.
Re: [gentoo-user] Safe systemd "reload" command
On Sun, Jun 5, 2016 at 9:23 AM, J. <jyo.gar...@gmail.com> wrote: > > SYSTEMD_INIT_PID=`pgrep -o -U 0 systemd` Doesn't systemd call "init" rather "systemd" if you use the "sysv-utils" flag?
Re: [gentoo-user] systemd: "local system does not support BPF/cgroup based firewalling"
Do you have CONFIG_CGROUP_BPF enabled? Regards. On Sat, Oct 28, 2017 at 1:03 PM, Nikos Chantziaras <rea...@gmail.com> wrote: > I'm getting these at startup: > > systemd[1]: File /lib/systemd/system/systemd-journald.service:33 > configures an IP firewall (IPAddressDeny=any), but the local system does > not support BPF/cgroup based firewalling. > systemd[1]: Proceeding WITHOUT firewalling in effect! > systemd[1]: File /lib/systemd/system/systemd-udevd.service:32 configures > an IP firewall (IPAddressDeny=any), but the local system does not support > BPF/cgroup based firewalling. > systemd[1]: Proceeding WITHOUT firewalling in effect! > systemd[1]: File /lib/systemd/system/systemd-logind.service:34 configures > an IP firewall (IPAddressDeny=any), but the local system does not support > BPF/cgroup based firewalling. > systemd[1]: Proceeding WITHOUT firewalling in effect! > > What do I need to make this work? I found this: > > https://github.com/systemd/systemd/issues/7188 > > But CONFIG_BPF_SYSCALL is enabled and I still get that message. > > This is on kernel 4.9.59 with systemd 235. > > > -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] preparing for the "systemd rootprefix migration"
On Wed, Feb 07 2018, Mike Gilbert wrote: > On Wed, Feb 7, 2018 at 3:28 PM, allan gottlieb <gottl...@nyu.edu> wrote: >> I run a stable system using gnome3 and hence systemd, specifically >> systemd-236-r5. My bootloader is grub2. I do *not* have an EFI >> platform and do *not* have an initramfs. >> I do *not* have a separate /usr filesystem. >> >> The news item says that, in preparation for the 237 release and the >> likely removal of the symlinks >>/usr/lib/systemd/systemd and >>/usr/lib/systemd/systemd-shutdown >> we should update our boot config to reference init=/lib/systemd/system >> >> 1. Updating the boot config to reference init=/lib/systemd/system seems >> to mean a 1-line change in /etc/default/grub >> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd" --> >> GRUB_CMDLINE_LINUX="init=/lib/systemd/systemd" >> followed by the usual >>grub-mkconfig -o /boot/grub/grub.cfg >> Is that it? > > Yes. > >> 2. What should I be doing to prepare for the removal of the >> /usr/lib/systemd/systemd-shutdown symlink? > > You don't need to do anything specific here. > >> 3. "After upgrading, please run systemctl daemon-reexec". Which >> upgrade is being referred to? Is it the upgrade to the 237 release, >> with the likely removal of the two symlinks. > > You should run that command after any systemd upgrade, but > specifically after upgrading from a version prior to 234. Thank you. allan gottlieb
Re: [gentoo-user] preparing for the "systemd rootprefix migration"
On Wed, Feb 7, 2018 at 3:28 PM, allan gottlieb <gottl...@nyu.edu> wrote: > I run a stable system using gnome3 and hence systemd, specifically > systemd-236-r5. My bootloader is grub2. I do *not* have an EFI > platform and do *not* have an initramfs. > I do *not* have a separate /usr filesystem. > > The news item says that, in preparation for the 237 release and the > likely removal of the symlinks >/usr/lib/systemd/systemd and >/usr/lib/systemd/systemd-shutdown > we should update our boot config to reference init=/lib/systemd/system > > 1. Updating the boot config to reference init=/lib/systemd/system seems > to mean a 1-line change in /etc/default/grub > GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd" --> > GRUB_CMDLINE_LINUX="init=/lib/systemd/systemd" > followed by the usual >grub-mkconfig -o /boot/grub/grub.cfg > Is that it? Yes. > 2. What should I be doing to prepare for the removal of the > /usr/lib/systemd/systemd-shutdown symlink? You don't need to do anything specific here. > 3. "After upgrading, please run systemctl daemon-reexec". Which > upgrade is being referred to? Is it the upgrade to the 237 release, > with the likely removal of the two symlinks. You should run that command after any systemd upgrade, but specifically after upgrading from a version prior to 234.
[gentoo-user] FYI on kernel 5.2 systemd may fail to bring up the network
Happened on 2/2 systems tested. You can bring the interface up manually if you're at the console. Error looks like systemd-networkd[252]: enp5s0: Could not bring up interface: Invalid argument Looks like its fixed in git https://github.com/systemd/systemd/issues/12784
Re: [gentoo-user] network do not come up after booting, only manual reloading (systemd-networkd)
[Unit] After=systemd-udev-settle.service Am 9/7/21 um 8:45 PM schrieb Canek Peláez Valdés: cat /etc/systemd/system/systemd-networkd.service.d/override.conf
[gentoo-user] Re: systemd-boot on openrc
Peter Humphrey wrote: > On Sunday, 17 April 2022 14:54:50 -00 Rich Freeman wrote: >> >> Can't you just fix your USE flags with systemd-utils? Why revert? > > No, because the flag I'd need is 'boot', and that triggers switching from > elogind to systemd. No, USE=boot for systemd-util does not trigger anything like that.
[gentoo-user] Re: A systemd-only Gentoo system
Canek Peláez Valdés caneko at gmail.com writes: Hi; I've been running systemd in Gentoo since September from 2010, and it works great for me: all my machines run it at this point. Well, I'm curious. How well does systemd work with uClibc based systems? More specifically does systemd work well with embedded linux systems? How does systemd work with a system that uses SElinux? How well does a group of (systemd) systems work with a wide deployment of a distributed file system, such as BTRFS? Just curious if you know about any of these areas related to systemd. James
[gentoo-user] Restart network interface with systemd
Hello all, I installed gnome3 few weeks ago, and had to migrate to systemd. The network init scripts are working fine. But I am not sure how to restart a specific interface. For example in the past I used to do: /etc/init.d/net.eth0 restart The wlan0 starts through wpa_supplicant under openrc. I can not remember doing any modification to adopt to systemd. The wpa_supplicant is not running under systemd, but wlan0 is working: neptune ~ # systemctl status wpa_supplicant wpa_supplicant.service - WPA supplicant Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled) Active: inactive (dead) Jan 23 19:54:20 neptune systemd[1]: Collecting wpa_supplicant.service I think it's because of dhcpcd, but not sure. my question now, is how to stop wlan0 and start eth0 with systemd ?? Thank you.
[gentoo-user] Re: systemd as a Profile - practical or not?
On Tue, 18 Feb 2014 11:24:05 -0500, Tanstaafl tansta...@libertytrek.org wrote: Hi all, Ok, before I go and open up a bug requesting this... I know there have to be a lot of people on this list who can answer this question... Is making the use of systemd or not based on a selected Profile, as opposed to manually trying to do it via USE flags etc, a practical request, or not? How is this different from the status quo? There are several systemd profiles available that make use of the files in /usr/portage/profiles/targets/systemd/ to make the proper package settings for using systemd on gentoo. AFAIU, a user should only need to switch the profile, install and configure systemd itself and configure their bootloader to start using systemd. -- eroen signature.asc Description: PGP signature
Re: [gentoo-user] Re: Debian just voted in systemd for default init system in jessie
On 21.02.2014 08:42, Andrew Savchenko wrote: So all talks about systemd being modular are nothing more than nonsense. Guess what will happen on segfault in libsystemd.so? Segfaults in pid 1 are so nice to bear... And now with 209 there is a new systemd-networkd deamon that is started by default even if not configured or used. http://www.phoronix.com/scan.php?page=news_itempx=MTYxMTI Why has a init system a deamon to configure networks? What comes next? Systemd-Windowsd, a systemd replacement for all other desktop environments? Systemd-Browserd? Systemd-Officed? Greetings Sebastian
Re: [gentoo-user] Pointers on how to speed up the boot process with systemd
Am 09.03.2014 18:39, schrieb Canek Peláez Valdés: Something is wrong here; unless you are booting a 386 machine, there is no way it should take a minute and a half to boot. And even with a 386 I would be suspicious. No, actually it is an Intel i5-4670K with 8 GB of RAM. Something is seriously wrong with systemd-tmpfiles-clean.service; why it takes 1:07 minutes to run? Do you have /tmp as a tmpfs? Yes, at least according to mount, it is. mount | grep tmpfs devtmpfs on /dev type devtmpfs (rw,relatime,size=238864k,nr_inodes=59716,mode=755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755) tmpfs on /tmp type tmpfs (rw) By the way my actual blame does tell: systemd-analyze blame 6.087s NetworkManager.service 5.310s alsa-restore.service 4.226s systemd-logind.service 3.660s lightdm.service 2.581s systemd-vconsole-setup.service 688ms polkit.service 479ms systemd-user-sessions.service 413ms kmod-static-nodes.service 381ms systemd-udev-trigger.service 358ms user@0.service 352ms systemd-tmpfiles-setup-dev.service 274ms tmp.mount 265ms systemd-journal-flush.service 246ms systemd-sysctl.service 235ms systemd-random-seed.service 205ms upower.service 205ms udisks2.service 197ms systemd-udevd.service 195ms systemd-tmpfiles-setup.service 183ms systemd-fsck-root.service 163ms systemd-remount-fs.service 126ms systemd-update-utmp.service 125ms sys-fs-fuse-connections.mount 53ms wpa_supplicant.service 50ms user@1000.service 50ms accounts-daemon.service Actual systemd-analyze: Startup finished in 584542y 2w 2d 20h 1min 42.032s (loader) + 1.540s (kernel) + 11.028s (userspace) = 12.569s Actual critical chain: graphical.target @11.028s └─multi-user.target @11.028s └─NetworkManager.service @4.940s +6.087s └─basic.target @4.939s └─timers.target @4.721s └─systemd-tmpfiles-clean.timer @4.721s └─sysinit.target @4.489s └─systemd-vconsole-setup.service @1.907s +2.581s └─systemd-journald.socket @1.660s └─-.mount @1.660s └─system.slice @2.030s └─-.slice @2.030s Could you run systemd-analyze critical-chain systemd-tmpfiles-clean.service? Sure, here it is: └─systemd-tmpfiles-clean.timer @4.721s └─sysinit.target @4.489s └─systemd-vconsole-setup.service @1.907s +2.581s └─systemd-journald.socket @1.660s └─-.mount @1.660s └─system.slice @2.030s └─-.slice @2.030s In your critical-chain systemd-tmpfiles-clean.service was not included (only systemd-tmpfiles-clean.timer). From blame, I think that's the obvious offender. Again, do you have /tmp as a tmpfs? What do you have in /etc/tmpfiles.d? /etc/tmpfiles.d is empty. Notice that systemd-tmpfiles-clean.service takes almost no time; here it's its critical chain: Yes, I see, so makes me wonder. BTW, my fstab: /dev/sda1 /boot ext2noauto,noatime 0 0 /dev/sda2 / xfs noatime,nodiratime 0 0 Thanks.
Re: [gentoo-user] Re: grub-2 update
On Thu, 16 Jul 2015 19:54:31 -0400, Jonathan Callen wrote: The Gummiboot project is no longer maintained, it has been merged into systemd as systemd-boot (note that using any other part of Systemd should *not* be required to use systemd-boot, but I don't know for sure because I do not have any non-systemd systems). Interesting, I missed that. I've re-emerged systemd with the gnuefi flag and it just worked. I do have a UEFI system without systemd that I could try it on. But it's a headless MythTV backend in the loft, so there will be fun and games if it doesn't boot. -- Neil Bothwick Top Oxymorons Number 11: Terribly pleased pgpiJMGvHsJzD.pgp Description: OpenPGP digital signature
[gentoo-user] Re: udev -> eudev
Mick gmail.com> writes: > James, the guidance has already been given. Can you please grep for systemd > ALL of your /etc/portage? There seems to be a USE flag set somewhere and this > is what is pulling in dbus *with* systemd. YES. I forgot Neil had told me to periodically remove this file:: /etc/portage/package.use/zzz-autounmask and I cleaned out package.unmask from autounmask that inserted systemd flag requirements. emerge -uDvtp @world shows just a few updates needed but nothing pulling in systemd. What I'm missing is why the "-systemd" setting in make.conf did not overrule these missteps? Is there way to set something, anything anywhere what no packages with require systemd can be installed. I never contiously overrode that concern. It is my overwhelming concern. NO systemd. All else is optional. Where's that setting? James
[gentoo-user] Re: systemD?
On 30/08/17 23:39, mad.scientist.at.la...@tutanota.com wrote: I do not want to start a whole systemd storm, glad i was offline for that. however, in my case i'd really like to avoid systemd. can i setup with out systemd, or do i need to remove and patch later. As others mentioned, openrc is the default. If you just do a default install, you won't be using systemd. However, make sure that you don't intend to use something that requires systemd. Like Gnome, for example. You then will need to convert to systemd rather than having started out with it.
Re: [gentoo-user] sys-apps/systemd-239-r2 does not install completely
On Tue, 20 Nov 2018 11:33:03 +0100, Stefan G. Weichinger wrote: > >>> What version does "qlist ICv systemd" show? > >> > >> No version, just a long list of files. > > > > That should have been "qlist -ICv systemd" > > > > thanks -> > > # qlist -ICv systemd > sys-apps/gentoo-systemd-integration-7 > sys-apps/systemd-236-r5 Since no one else has come up with anything less kludgy, and I assume you have already tried reinstalling systemd, I can only think of unmerging and re-emerging it, after making a package with quickpkg. -- Neil Bothwick DOS never says "EXCELLENT command or filename"... pgpKT9DkTg1nW.pgp Description: OpenPGP digital signature
[gentoo-user] systemd 246 gives strange messages
Hi. After the latest update to systemd 246, I get periodic messages like these: systemd[7985]: Not generating service for XDG autostart app-nm\x2dapplet-autostart.service, it is hidden. systemd[7985]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.XSettings-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.Wacom-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-pulseaudio-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.ScreensaverProxy-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.Housekeeping-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.Smartcard-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-orca\x2dautostart-autostart.service, only Type=Application is supported. systemd[7985]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.Sharing-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.UsbProtection-autostart.service, startup phases are not supported. systemd[7985]: gnome-systemd-autostart-condition not found: No such file or directory systemd[7985]: Not generating service for XDG autostart app-xdg\x2duser\x2ddirs-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.Power-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.Color-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.A11ySettings-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.Keyboard-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.MediaKeys-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dssh-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.Datetime-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dsecrets-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-at\x2dspi\x2ddbus\x2dbus-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.Sound-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dpkcs11-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.Rfkill-autostart.service, startup phases are not supported. systemd[7985]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.PrintNotifications-autostart.service, startup phases are not supported. Does this indicate a problem, and if not, how can I stop these messages? Thanks in advance for any suggestions. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una cov...@ccs.covici.com
Re: [gentoo-user] Gordian knot systemd / hwids
On Mon, 29 Nov 2021 at 16:11, Helmut Jarausch wrote: > > Hi > systemd-249.6-r1 conflicts with sys-apps/hwids[udev] > > But when I remove the udev use flag, > emerge sys-apps/hwids gives > >The following REQUIRED_USE flag constraints are unsatisfied: > systemd? ( udev ) > > > So, I would have to remove sys-apps/systemd-249.6 first. > Is it save to > emerge -C sys-apps/systemd > > ? > Thanks for a hint, It seems like systems-249.6-r1 has removed support for hwids. There are references in the ebuild to systemd-hwdb, so I guess they have their own version. You need to remove the systemd USE flag from hwids to solve your knot. Regards, Arve
Re: [gentoo-user] trouble downgrading systemd and virtual/udev
On Wed, Sep 25 2013, Canek Peláez Valdés wrote: On Wed, Sep 25, 2013 at 5:24 PM, gottl...@nyu.edu wrote: I want to downgrade systemd from 207-r2 to 204 (highest stable). I currently have virtual/udev-206-r2 installed, which prevents systemd-204. OK. So I need to downgrade virtual/udev to 200. I thought emerge -1 =virtual/udev-200 =sys-apps/systemd-204 would do it. But this failed (see below) and suggested masking might help. So I added package.mask/systemd, which contains =virtual/udev-201 =sys-apps/systemd-205 and then issued the same emerge as above. But this also failed (see below). What incantation do I need? Don't mask anything, just make sure that systemd (both virtual/ and sys-apps/) is not on package.keywords. This system is ~amd64 (I should have said that earlier). I don't believe there is a virtual/systemd package. Did you mean virtual/udev? If so, I would create /etc/portage/package.accept_keywords/systemd and put in it two lines -~sys-apps/systemd -~virtual/udev Correct? thanks, allan
[gentoo-user] Re: systemd not starting wpa_supplicant after last update
On 02/11/2015 01:05 PM, Neil Bothwick wrote: On Wed, 11 Feb 2015 13:22:13 -0600, Canek Peláez Valdés wrote: I use NetworkManager for wireless connections, and systemd-networkd for static ethernet, so I don't use wpa_supplicant directly. However, I would suggest to simply enable wpa_supplicant@your-wireless-device.service. I have it set up like this % cat /etc/systemd/network/20-wlan0.network [Match] Name=wlan0 [Network] Description=Wireless network DHCP=yes % ls -l /etc/systemd/system/systemd-networkd.service.wants/ systemd-resolved.service - /usr/lib/systemd/system/systemd-resolved.service wpa_supplicant@wlan0.service - /usr/lib64/systemd/system/wpa_supplicant@.service Yes, thank you! Did you use systemctl to make all the symlinks? I just did it all manually and it works, but I'm not sure how I would have done it using systemctl. I just discovered I needed to create a symlink from /run/systemd/resolve/resolv.conf to /etc/resolv.conf. Had to resort to reading a man page :(
Re: [gentoo-user] Re: [ANNOUNCE] I like systemd now :)
On 2012-11-11 13:52, 微蔡 wrote: ok , then why hate systemd ? you seems to hate systemd with no reason. This is my last reply to this thread. I dislike systemd, for the reasons I've already stated. Please re-read my responses if you want to know why I dislike systemd. What I do _hate_ is being forced into using something I don't want so I will look for solutions elsewhere, if need be. Best regards Peter K
[gentoo-user] [systemd] Right way to start an nfs server?
I'm sooo close, but I'm doing something wrong with nfs server, and my nfs clients keep getting rejection messages. I got my systemd scripts here: http://en.gentoo-wiki.com/wiki/Systemd#NFS I know the problem is with the nfs server because the nfs clients work normally if I boot the nfs server using openrc instead of systemd. Anyone have nfs servers working properly with systemd? I'm out of ideas :( Thanks
Re: [gentoo-user] systemd-197-r1 starts gdm-3.6.2
Am 2013-02-09 19:56, schrieb Stefan G. Weichinger: AFAI understand these 2 lines should be enough to let systemd generate its relevant unit-files etc. Right? Additional thoughts: Is pam_mount obsolete with systemd? It is possible to mount my /home via systemd-unit as well ... the difference seems to be that systemd would (try to) mount it at boot-time while with pam_mount it would be mounted at login. Thoughts? Experiences? Stefan
Re: [gentoo-user] gentoo-systemd-only deprecation
On 2013-07-31 11:45 AM, Yohan Pereira yohan.pere...@gmail.com wrote: The one true way is to set -systemd in your useflags. However anything that hard depends on systemd will pull it in like AFAIR gnome. Trying to opt-out of systemd in these cases is not supported and probably not trivial. Ok, I misread some things in those discussions (was reading quickly)... I could have sworn I saw mention a -systemd USE flag was explicitly rejected by the devs... now I see it was only a USE flag for the inclusion of the unit files. Sorry for the noise...
Re: [gentoo-user] systemd as a Profile - practical or not?
Am Dienstag 18 Februar 2014, 11:24:05 schrieb Tanstaafl: Is making the use of systemd or not based on a selected Profile, as opposed to manually trying to do it via USE flags etc, a practical request, or not? Have a look at the files in profiles/targets/systemd/ http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/profiles/targets/systemd/ That's all that is different in the systemd subprofiles. Easy to do manually. -- Andreas K. Huettel Gentoo Linux developer kde, council
Re: [gentoo-user] Debian just voted in systemd for default init system in jessie
On Tue, 18 Feb 2014 11:22:23 -0600 Canek Peláez Valdés wrote: Yet again, I respect ones right to use whatever one wants, but I ask to respect mine as well. That's why I propose a separate systemd profile for those willing to use it. Then write. Just be aware that to write a systemd profile, you need to use systemd. Or to create a non-systemd profile :) Best regards, Andrew Savchenko pgpKEksCQfVOx.pgp Description: PGP signature
Re: [gentoo-user] problems getting systemd to work
Canek Peláez Valdés can...@gmail.com wrote: On Mon, May 12, 2014 at 5:15 AM, cov...@ccs.covici.com wrote: Canek Peláez Valdés can...@gmail.com wrote: On Mon, May 12, 2014 at 2:22 AM, cov...@ccs.covici.com wrote: Hi. I have been trying to get systemd to boot, but I have run into several problems and need some help. I am using everything but /boot as lvm's, with a separate user partition. I had to copy systemd to /sbin because the initrd looks for the realinit too soon, but that is maybe another matter. Moving systemd to /sbin sounds like it's not going to work. Run readelf -d /usr/lib/systemd/systemd; all the NEEDED libraries on /usr/lib should be available to the binary at the time it's being executed. How can I do this, genkernel looks for its init before it mounts /usr and genkernel-next will not mount the separate /usr at all. My latest initrd is from the very latest genkernel. With genkernel, I don't know; I never used it. On the other hand, dracut is designed to work with systemd; if you use the systemd USE flag and the systemd module, it even uses systemd *inside* the initramfs. But how to get a complete history of systemd actions in the order that they are done, I thought the confirm_spawn would do this for me -- at least for my initial debugging. The problem obviously is not in systemd, but in the integration of genkernel+systemd. I repeat, I never used genkernel, so I don't know what you can do. That being said, get a complete history of systemd actions in the order that they are done will not tell you much: systemd uses heavy parallelization, so in some runs the order in which actions are performed will be different from others. The problem is that if systemd is installed into /usr/lib (which is Gentoo's case), then /usr should be mounted before systemd starts. That's responsibility of the initramfs, not of systemd, and the solution lies in the initramfs, not in systemd. My only possible recommendation would be for you to try dracut. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México OK, I will try dracut, but I still want to know what systemd is doing, what processes its spawning, etc. -- how can I find this out -- I thought to use the confirm_spawn, but it times out and keeps going, what can I do instead? Thanks people for all your responses, this is a great list. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
[gentoo-user] Re: systemd-224 Look out for new networking behavior
On Sun, 2 Aug 2015 08:03:11 -0700 walt w41...@gmail.com wrote: I've been running systemd for a long time without needing to enable the dhcpcd service at boot time. Starting with systemd-224 that is no longer true. Oops, journalctl tells me that systemd-networkd is segfaulting repeatedly during boot. I'm reverting back to systemd-222-r1 until this gets sorted out.
[gentoo-user] Re: udev -> eudev
Jc García gmail.com> writes:
> > [blocks B ] sys-fs/eudev ("sys-fs/eudev" is blocking
> > sys-apps/gentoo-systemd-integration-4, sys-apps/systemd-226-r2)
> > [blocks B ] sys-apps/gentoo-systemd-integration
> > ("sys-apps/gentoo-systemd-integration" is blocking sys-fs/udev-225,
> > sys-fs/eudev-3.1.5)
> > [blocks B ] sys-apps/systemd ("sys-apps/systemd" is blocking
> > sys-fs/udev-225, sys-fs/eudev-3.1.5)
> > So just emerge -C sys-apps/systemd sys-apps/gentoo-systemd-integration
> > sys-fs/udev
> You can only have one of sys-apps/systemd, sys-fs/udev or sys-fs/eudev
> installed, portage won't let you install 2(since there's files
> collision), see the contents of virual/udev, so there's no point in
> trying to remove 2 of them from a system, "All softs of things are now
> calling for systemd" isn't really digging into the problem, and being
> honest not that many packages have sys-apps/systemd in any of *DEPEND,
> you should check better why is systemd being pulled( emerge -pvt),
> maybe some use flags misconfiguration.
YES. I agree with you guys. I have -systemd in make.conf for a long time now.
Nothing depends on the sysmtemd flag or software, since forever. OpenRC here.
I synced last night and this blocking occurred, its new and I have not many
any changes on this system except for new packages. I suspect something low
level with udev, but I cannot find what's causing it.
on 'gentoo-dev' I read the thread on " Changing order of default
virtual/udev ". Being in the camp of 100% against systemd, something has
changed and I need help ferreting in out.
equery hasuse systemd
reveals nothing that has the systemd flag set. I should have changed over to
eudev a long time ago. So I need to remove whatever and make the change
now. I run lxde for a desktop, if that matters. Is there syntax to dive
deeper into what's causing this sudden change?
sys-apps/systemd is not even installed, but it shows up as a blocker?
gentoo-systemd-integration is not installed, but it's a blocker.
udev::
[I] virtual/udev
Available versions: 215 ~217 {systemd}
Installed versions: 215(10:34:27 PM 02/15/2015)(-systemd)
So, for me it's time to take the risk and remove udev and install eudev.
I do appreciate guidance and wisdom and especially syntax ideas, but
the decision is already made.
Advice?
James
Re: [gentoo-user] gdm fails to start
Hello, Very simple question but did you have "pam" in your global USE flag or Systemd USE flag ? If this is on the first, did you compile systemd and may be dependencies after add it ? Did you try that: |systemctl reset-failed| |For a guy on github, that solve (without explanation) the problem: | |https://github.com/coreos/bugs/issues/1498| || Hogren On 22/05/2017 14:13, Raffaele Belardi wrote: > On Mon, 2017-05-22 at 13:02 +0300, Alexander Kapshuk wrote: >> On Mon, May 22, 2017 at 1:00 PM, Raffaele Belardi >> <raffaele.bela...@st.com> wrote: >>> On Mon, 2017-05-22 at 12:47 +0300, Alexander Kapshuk wrote: >>>> A Google search found this systemd issue: >>>> https://github.com/systemd/systemd/issues/4342 >>>> Quote: >>>> @poettering I see I left no account modules in the bare-bones PAM >>>> config. Maybe it is pam_acct_mgmt failing then? >>>> >>>> @yuwata what happens if you add account required pam_unix.so ? >>>> >>>> @fsateler Thanks. By adding the line, user sessions successfully >>>> start >>>> without the error messages. Do you think the line should be added >>>> to >>>> the minimal PAM file? >>>> >>>> See if that helps. >>>> >>> Yes, I saw that but the solution is not at all clear to me: which >>> PAM >>> config file are they referring to? >>> >>> raffaele >>> >>> >> Could it be this one, /etc/pam.d/systemd-user? >> > Done then issued 'systemctl daemon-reload' and 'systemctl start gdm', > no change: > > $ cat /etc/pam.d/systemd-user > # This file is part of systemd. > # > # Used by systemd --user instances. > > account include system-auth > # [RB] > account required pam_unix.so > session include system-auth > session optional pam_keyinit.so force revoke > session optional pam_systemd.so > > #journalctl -b > ... > systemd[1]: Created slice User Slice of gdm. > systemd[1]: Starting User Manager for UID 32... > systemd[1]: Started Session c519 of user gdm. > systemd-logind[173]: New session c519 of user gdm. > systemd[15240]: user@32.service: Failed at step PAM spawning > /usr/lib/systemd/systemd: Operation not permitted > systemd[1]: Failed to start User Manager for UID 32. > systemd[1]: user@32.service: Unit entered failed state. > systemd[1]: user@32.service: Failed with result 'protocol'. > gdm-launch-environment][15237]: pam_systemd(gdm-launch- > environment:session): Failed to create session: Start job for unit user > @32.service failed with 'failed' > systemd-logind[173]: Removed session c519. >
[gentoo-user] systemD?
I do not want to start a whole systemd storm, glad i was offline for that. however, in my case i'd really like to avoid systemd. can i setup with out systemd, or do i need to remove and patch later. obviously better to start without it in this case. so are some of the available kernels not systemd, and how much does it change the installation? i did search for it, and found a couple docs at gentoo.org it doesn't look too bad. thanks. -- The Power Of the People Is Stronger Than The People In Charge.
Re: [gentoo-user] systemD?
Am Wed, 30 Aug 2017 23:27:12 +0100 schrieb Mick <michaelkintz...@gmail.com>: > BTW, if you run ps axf and come across '/lib/systemd/systemd-udevd > --daemon' don't panic. RHL advocates of monolithic stack for Linux > haven't taken over your machine, but that's how udev is packaged > these days even if you have not installed or enabled systemd on your > OS. Why not using eudev? Works perfectly. No need for systemd-udev. Heiko
[gentoo-user] Re: Systemd
On 04/11/17 18:15, siefke_lis...@web.de wrote: I have a short question to systemd. I would like to ask your experience in the changeover. Was it easy? Were there problems? Change or reinstall? What mean the profis here? I did both. Changed one system to systemd, re-installed one from scratch with systemd. Both worked. The only problem I have with systemd is that it's unable to reliably restore the ALSA mixer volumes/settings on startup. It fails 50% of the time. Which is very annoying, but not the end of the world.
[gentoo-user] sys-apps/systemd-239-r2 does not install completely
upgrading from sys-apps/systemd-236-r5 to 239-r2 the emerge runs through and warns me that it overwrites files ... so it merges only partially ... after that I see: # systemctl --version systemd 239 (which is OK) # eix -I systemd [U] sys-apps/systemd Available versions: 239-r2(0/2) Installed versions: 236-r5 (which is scary) How to clean that up?
Re: [gentoo-user] network do not come up after booting, only manual reloading (systemd-networkd)
On Sun, Sep 5, 2021 at 1:36 PM Tamer Higazi wrote: [...] > × systemd-networkd-wait-online.service - Wait for Network to be Configured > Loaded: loaded > (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; > vendor preset: disabled) > Active: failed (Result: exit-code) since Sun 2021-09-05 20:22:19 > CEST; 11min ago > Docs: man:systemd-networkd-wait-online.service(8) > Main PID: 984 (code=exited, status=1/FAILURE) > Sep 05 20:20:18 tux systemd[1]: Starting Wait for Network to be > Configured... > Sep 05 20:22:19 tux systemd-networkd-wait-online[984]: Timeout occurred > while waiting for network connectivity. > Sep 05 20:22:19 tux systemd[1]: systemd-networkd-wait-online.service: > Main process exited, code=exited, status=1/FAILURE > Sep 05 20:22:19 tux systemd[1]: systemd-networkd-wait-online.service: > Failed with result 'exit-code'. > Sep 05 20:22:19 tux systemd[1]: Failed to start Wait for Network to be > Configured. > There's your problem: systemd-networkd-wait-online.service is timing out: Sep 05 20:22:19 tux systemd-networkd-wait-online[984]: Timeout occurred while waiting for network connectivity. The systemd-networkd-wait-online service runs relatively early and waits for *ALL* interfaces it is aware of to be fully configured or failed[1], so it probably one of your interfaces is taking too long to be ready. Between timing out and you restarting systemd-networkd.service, the interface reaches the ready state (or fails), and systemd-networkd-wait-online.service doesn't time out anymore. By your logs, you have two ethernet interfaces: enp6s0 and enp7s0, the latter not in use. Do you .network files in /etc/systemd/network/ or /run/systemd/network/? Any changes (uncommented lines) in /etc/systemd/networkd.conf? Regards. [1] https://man7.org/linux/man-pages/man8/systemd-networkd-wait-online.8.html -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
