Re: [gentoo-user] systemd unit executing but not persistent later in boot

[Daniel Frey]

On 4/6/24 18:38, Andrew Udvare wrote:

On Sat, 6 Apr 2024 at 21:32, Daniel Frey  wrote:

What's even stranger is if I manually start it and restart lircd it works!


Have you tried adding Before=lircd.service in the [Unit] section?



OK, I have finally sorted out the IR keymap/lircd/irexec/LCDd problems.

It turns out the systemd units as shipped just simply do not work, at 
least for my hardware.


The custom unit I made to apply a new keytable and protocol change was 
working fine. After a lot of reading about systemd units and also poring 
through logs, I discovered udev was triggering something related to the 
LCD/IR module - my custom unit was running before this happened but the 
udev trigger reset it to defaults (for whatever reason.)


In order to fix that, I had to change my unit to this:

[Unit]
Description=Add custom keymap to iMon remote
Requires=systemd-udevd.service systemd-udev-settle.service 
systemd-udev-trigger.service
After=systemd-udevd.service systemd-udev-settle.service 
systemd-udev-trigger.service

Before=lircd.service inputlircd.service irexec.service

[Service]
RemainAfterExit=true
ExecStart=/usr/bin/ir-keytable -c -p rc-6 -w /etc/rc_keymaps/imon_mce.toml

[Install]
WantedBy=multi-user.target
RequiredBy=lircd.service irexec.service


This made the keymap change work reliably.

After this lircd was working normally.

I use lircd so I can use irexec to listen for the power button and just 
shut the computer off. Kodi is too finicky and just wouldn't turn off or 
it would just logout, even with the polkit policy in the wiki applied.


Now, starting irexec didn't work the the shipped systemd unit either, it 
would just exit and not stay running. I fixed that with this custom unit:


[Unit]
Documentation=man:irexec(1)
Documentation=http://lirc.org/html/configure.html
Documentation=http://lirc.org/html/configure.html#lircrc_format
Description=Handle events from IR remotes decoded by lircd(8)
After=lircd.service
Requires=lircd.service

[Service]
; user=lirc
; group=lirc

; Hardening opts, see systemd.exec(5).  Doesn't add much unless
; not running as root. If these are applicable or not depends on
; what commands irexec.lircrc invokes.
;
; NoNewPrivileges=true
; MemoryDenyWriteExecute=true
; PrivateTmp=true
; ProtectHome=true
; ProtectSystem=full


Type=forking
ExecStart=/usr/bin/irexec --daemon /etc/lirc/irexec.lircrc

[Install]
WantedBy=multi-user.target


So irexec would start and actually stay running. I did also tell it to 
start after lircd (although I'm not 100% sure this matters - it may not.)


Of course the LCD unit wouldn't start and stay running either, again the 
systemd unit shipped didn't work so I customized it:


[Unit]
Description=LCDProc (LCDd)
After=network-online.target lircd.service
Requires=lircd.service

[Service]
ExecStart=/usr/sbin/LCDd -c /etc/LCDd.conf
Type=forking

[Install]
WantedBy=multi-user.target

After all this, then Kodi wouldn't start up. I figured out quickly this 
was caused by lightdm starting before the network was ready, fixed with 
this custom unit:


[Unit]
Description=Light Display Manager
Documentation=man:lightdm(1)
After=systemd-user-sessions.service
After=network-online.target
Wants=network-online.target

[Service]
ExecStart=/usr/sbin/lightdm
Restart=always
IgnoreSIGPIPE=no
BusName=org.freedesktop.DisplayManager

[Install]
Alias=display-manager.service


Hopefully this may be helpful to others with HTPCs switching to systemd 
from openrc. In openrc nearly all of this customization isn't needed - I 
only modified /etc/init.d/lircd in openrc in order to load the keymap 
before lircd started.


Dan

Re: [gentoo-user] systemd unit executing but not persistent later in boot

[Daniel Frey]

On 4/6/24 18:38, Andrew Udvare wrote:

On Sat, 6 Apr 2024 at 21:32, Daniel Frey  wrote:

What's even stranger is if I manually start it and restart lircd it works!


Have you tried adding Before=lircd.service in the [Unit] section?



I did, it made no difference.

From what I can tell it is running before lircd.

I have disabled lircd. Ran daemon-reload and rebooted.

For some reason, systemctl is saying it has run and exited successfully 
according to the timestamps:


# systemctl status ir-key-map
○ ir-key-map.service - Add custom keymap to iMon remote
 Loaded: loaded (/etc/systemd/system/ir-key-map.service; enabled; 
preset: disabled)
 Active: inactive (dead) since Sun 2024-04-07 08:56:18 PDT; 1min 
36s ago

   Duration: 48ms
Process: 295 ExecStart=/usr/bin/ir-keytable -c -p rc-6 -w 
/etc/rc_keymaps/imon_mce.toml (code=exited, status=0/SUCCESS)

   Main PID: 295 (code=exited, status=0/SUCCESS)
CPU: 19ms

Apr 07 08:56:18 htpclivingrm systemd[1]: Started Add custom keymap to 
iMon remote.

Apr 07 08:56:18 htpclivingrm ir-keytable[295]: Read imon_mce table
Apr 07 08:56:18 htpclivingrm ir-keytable[295]: Old keytable cleared
Apr 07 08:56:18 htpclivingrm ir-keytable[295]: Wrote 76 keycode(s) to driver
Apr 07 08:56:18 htpclivingrm ir-keytable[295]: Protocols changed to rc-6
Apr 07 08:56:18 htpclivingrm systemd[1]: ir-key-map.service: Deactivated 
successfully.



But, it doesn't actually change the protocol. It says it has 
"ir-keytable[295]: Protocols changed to rc-6" but when you check 
manually as root it really hasn't:


# ir-keytable
Found /sys/class/rc/rc0/ with:
Name: iMON Remote (15c2:0038)
Driver: imon
Default keymap: rc-imon-pad
Input device: /dev/input/event8
LIRC device: /dev/lirc0
Supported kernel protocols: rc-6 imon
Enabled kernel protocols: imon
bus: 3, vendor/product: 15c2:0038, version: 0x0001
Repeat delay = 500 ms, repeat period = 125 ms

...and I have no idea why. Until this works, lircd will not work.

If you run it manually, it will update it. It shows in the log and more 
importantly, if you check with ir-keytable you can see it was successful.


It's bizarre.

I even tried adding User= and Group= in the [Service] context and it 
made no difference.


Dan

Re: [gentoo-user] systemd unit executing but not persistent later in boot

[Andrew Udvare]

On Sat, 6 Apr 2024 at 21:32, Daniel Frey  wrote:
> What's even stranger is if I manually start it and restart lircd it works!

Have you tried adding Before=lircd.service in the [Unit] section?

Re: [gentoo-user] Systemd query ...

[Rich Freeman]

On Wed, May 17, 2023 at 6:18 AM Jacques Montier  wrote:
>
> Well, well, Rich, you are completely right, you've found the key ! 
> I have that line in make.conf
> INSTALL_MASK="/lib/systemd/system /usr/lib/systemd/system"
> I now see where it comes from.
> On the same machine, I have another OpenRC Gentoo with systemd masqued.
> I just copîed the make.conf without uncommenting that line... How silly i am 
> !!!
> So I delete that bl...y line !
>

So, I realize this will be controversial, but this is why I don't make
super-minimalistic builds.  If I were trying to make a Gentoo build to
run on a C64 or something and every last inode counted, then sure.
However, things like text files simply don't do anything if nothing
reads them.  These days I also tend to be generous with building
kernel modules - it slows down kernel builds, but it has no impact on
running kernels if they aren't actually loaded.  I also use -mtune
these days and not -march.  Sure, you lose a little performance, but
if I lose a motherboard then I can just build a new PC, stick my hard
drive in it, and it will just work.

Now, if you're building disposable workers in some cluster that
processes lots of jobs, then sure that extra few percent performance
might be worth it, but then the individual hosts are all disposable
anyway.  Otherwise, I've found it is much better to optimize things
for MY time than CPU time.

-- 
Rich

Re: [gentoo-user] Systemd query ...

[Jacques Montier]

Le mer. 17 mai 2023 à 11:30, Rich Freeman  a écrit :

> On Wed, May 17, 2023 at 4:43 AM Jacques Montier 
> wrote:
> >
> > As I didn't mask anything, I don't understand why this file was not
> installed as it was declared in the apache ebuild...
>
> You don't have anything set in INSTALL_MASK?  Check "emerge --info
> www-servers/apache"
>
> You might want to check the build log for anything.  I don't think
> there is anything conditional about systemd_newunit, and it is
> supposed to generate a fatal error if it fails.
>
> --
> Rich
>
>
Well, well, Rich, you are completely right, you've found the key ! 
I have that line in make.conf
INSTALL_MASK="/lib/systemd/system /usr/lib/systemd/system"
I now see where it comes from.
On the same machine, I have another OpenRC Gentoo with systemd masqued.
I just copîed the make.conf without uncommenting that line... How silly i
am !!!
So I delete that bl...y line !

Thanks a lot,

Cheers

--
Jacques

Re: [gentoo-user] Systemd query ...

[Rich Freeman]

On Wed, May 17, 2023 at 4:43 AM Jacques Montier  wrote:
>
> As I didn't mask anything, I don't understand why this file was not installed 
> as it was declared in the apache ebuild...

You don't have anything set in INSTALL_MASK?  Check "emerge --info
www-servers/apache"

You might want to check the build log for anything.  I don't think
there is anything conditional about systemd_newunit, and it is
supposed to generate a fatal error if it fails.

-- 
Rich

Re: [gentoo-user] Systemd query ...

[Jacques Montier]

Hi all,

Thanks to Neil and Rich.

I Effectively found the file
www-servers/apache/files/apache2.4-hardened.service.
I renamed it as apache2.service in /lib/systemd/system.
Now it works !!! 

BUT,

As I didn't mask anything, I don't understand why this file was not
installed as it was declared in the apache ebuild...

 # Note: wait for mod_systemd to be included in some forthcoming release,
# Then apache2.4.service can be used and systemd support controlled
# through --enable-systemd
systemd_newunit "${FILESDIR}/apache2.4-hardened.service"
"apache2.service"
dotmpfiles "${FILESDIR}/apache.conf"
#insinto /etc/apache2/modules.d
#doins "${FILESDIR}/00_systemd.conf"

My use flags and modules :

Installed versions:  2.4.55-r1(2)(11:11:07 12/05/2023)(gdbm ssl suexec-caps
systemd -debug -doc -ldap -selinux -split-usr -static -suexec
-suexec-syslog -threads APACHE2_MODULES="actions alias auth_basic
authn_anon authn_core authn_dbm authn_file authz_core authz_dbm
authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid
dav dav_fs dav_lock deflate dir env expires ext_filter file_cache filter
headers http2 include info log_config logio mime mime_magic negotiation
rewrite setenvif socache_shmcb speling status unique_id unixd userdir
usertrack vhost_alias -access_compat -asis -auth_digest -auth_form
-authn_dbd -authn_socache -authz_dbd -brotli -cache_disk -cache_socache
-cern_meta -charset_lite -dbd -dumpio -ident -imagemap -lbmethod_bybusyness
-lbmethod_byrequests -lbmethod_bytraffic -lbmethod_heartbeat -log_forensic
-lua -macro -md -proxy -proxy_ajp -proxy_balancer -proxy_connect
-proxy_fcgi -proxy_ftp -proxy_hcheck -proxy_html -proxy_http -proxy_http2
-proxy_scgi -proxy_uwsgi -proxy_wstunnel -ratelimit -remoteip -reqtimeout
-session -session_cookie -session_crypto -session_dbd -slotmem_shm
-socache_memcache -substitute -version -watchdog -xml2enc"
APACHE2_MPMS="-event -prefork -worker" LUA_SINGLE_TARGET="lua5-1 -lua5-3
-lua5-4")


However, it works fine and thanks again to all of you !

Cheers,

--
Jacques




Le mar. 16 mai 2023 à 21:43, Rich Freeman  a écrit :

> On Tue, May 16, 2023 at 3:32 PM Jacques Montier 
> wrote:
> >
> > After install, apache2.service not found...
>
> Have you done something to mask service file installs/etc?
>
> The unit file is in the gentoo repo:
> www-servers/apache/files/apache2.4-hardened.service
>
> --
> Rich
>
>

Re: [gentoo-user] Systemd query ...

[David M. Fellows]

>Le lun. 15 mai 2023 à 11:58, Wols Lists  a écrit :
>
>> Nothing to do with but sparked by the Apache problem ...
>>
>> One of the emails mentioned that the "ExecStop" section didn't appear to
>> be working ... That's caused me considerable grief in a systemd config
>> file I've written ...
>>
>> Basically, somebody else added an ExecStop section - and all hell broke
>> loose. It seemed to be firing on boot :-( And the service in question -
>> ScarletDME - seemed to be killing processes at random, like DoveCot ...
>>
>> Okay, accidentally killing processes it shouldn't is probably down the
>> fork/exec code in ScarletDME, I haven't dug into it to know, but systemd
>> should not be triggering the stop in the first place. Has anybody else
>> encountered anything like this?
>>
>> Sorry I'm not likely to respond quickly to say "solved", as I need to
>> get "in the mood" to get back to debugging, but if anybody has any hints
>> and tips, they'd be appreciated, and it might shed some light on that
>> Apache problem :-)
>>
>> Cheers,
>> Wol
>>
>>
>Hi Wol,
>
>It was very difficult to get Apache working with systemd Gentoo.
>No apache2.service found with apache installation.
>so i looked at the Linux Mint OS to copy the apache2.service.
>These commands
>
>ExecStart=/usr/sbin/apachectl start
>ExecStop=/usr/sbin/apachectl graceful-stop
>ExecReload=/usr/sbin/apachectl graceful
>
>did not work at all...
>BUT,
>By manually launching /usr/bin/apache2ctl, it  worked.
>

On my gentoo system apache is installed in
/usr/sbin as apache2 and apache2ctl
 ^
It also installs /lib/systemd/system/apache2.service which references the
above files in a "gentoo-ish" way.

The Linux Mint service file you list above refers to apache without the "2".

Perhaps this shedd some light on your problem.

DaveF

>So i wrote a little simple bash script /usr/bin/op_apache
>
>#!/bin/bash
>
>case ${1} in
>"start")
>apache2ctl
>;;
>"stop")
>killall apache2
>;;
>"restart")
>killall apache2
>sleep 1
>apache2ctl
>;;
>esac
>
>And in apache2.service, i put :
>
>ExecStart=/usr/bin/op_apache start
>ExecStop=/usr/bin/op_apache stop
>ExecReload=/usr/sbin/op_apache restart
>
>Now it works fine, but what a headache !
>
>Cheers,
>
>--
>Jacques
>

Re: [gentoo-user] Systemd query ...

[Rich Freeman]

On Tue, May 16, 2023 at 3:32 PM Jacques Montier  wrote:
>
> After install, apache2.service not found...

Have you done something to mask service file installs/etc?

The unit file is in the gentoo repo:
www-servers/apache/files/apache2.4-hardened.service

-- 
Rich

Re: [gentoo-user] Systemd query ...

[Jacques Montier]

Le mar. 16 mai 2023, 20:58, Neil Bothwick  a écrit :

> On Tue, 16 May 2023 20:03:36 +0200, Jacques Montier wrote:
>
> > It was very difficult to get Apache working with systemd Gentoo.
> > No apache2.service found with apache installation.
>
> Really?
>
> % qfile apache2.service
> www-servers/apache: /lib/systemd/system/apache2.service
>
> Yes.
>
After install, apache2.service not found...

>
>
> > so i looked at the Linux Mint OS to copy the apache2.service.
> > These commands
> >
> > ExecStart=/usr/sbin/apachectl start
> > ExecStop=/usr/sbin/apachectl graceful-stop
> > ExecReload=/usr/sbin/apachectl graceful
> >
> > did not work at all...
>
> % systemctl cat apache2.service
> # /lib/systemd/system/apache2.service
> [Unit]
> Description=The Apache HTTP Server
> After=network.target remote-fs.target nss-lookup.target
>
> [Service]
> EnvironmentFile=/etc/conf.d/apache2
> ExecStart=/usr/sbin/apache2 $APACHE2_OPTS -DFOREGROUND
> ExecReload=/usr/sbin/apache2 $APACHE2_OPTS -k graceful
> ExecStop=/usr/sbin/apache2 $APACHE2_OPTS -k graceful-stop
> # We want systemd to give httpd some time to finish gracefully, but still
> want # it to kill httpd after TimeoutStopSec if something went wrong
> during the # graceful stop. Normally, Systemd sends SIGTERM signal right
> after the # ExecStop, which would kill httpd. We are sending useless
> SIGCONT here to give # httpd time to finish.
> KillSignal=SIGCONT
> PrivateTmp=true
> #Hardening
> CapabilityBoundingSet=CAP_CHOWN CAP_SETGID CAP_SETUID CAP_DAC_OVERRIDE
> CAP_KILL CAP_NET_BIND_SERVICE CAP_IPC_LOCK
> SecureBits=noroot-locked
> ProtectSystem=full
> PrivateDevices=true
> MemoryDenyWriteExecute=true
>
> [Install]
> WantedBy=multi-user.target
>
>
> --
> Neil Bothwick
>
> K: (n., adj.) a binary thousand, which isn't a decimal thousand or even
> really a binary thousand (which is eight), but is the binary number
> closest to a decimal thousand. This has proven so completely confusing
> that it has become a standard.
>


Thanks Neil, i'll have a try.

--
Jacques

>

Re: [gentoo-user] Systemd query ...

[Neil Bothwick]

On Tue, 16 May 2023 20:03:36 +0200, Jacques Montier wrote:

> It was very difficult to get Apache working with systemd Gentoo.
> No apache2.service found with apache installation.

Really?

% qfile apache2.service
www-servers/apache: /lib/systemd/system/apache2.service

> so i looked at the Linux Mint OS to copy the apache2.service.
> These commands
> 
> ExecStart=/usr/sbin/apachectl start
> ExecStop=/usr/sbin/apachectl graceful-stop
> ExecReload=/usr/sbin/apachectl graceful
> 
> did not work at all...

% systemctl cat apache2.service 
# /lib/systemd/system/apache2.service
[Unit]
Description=The Apache HTTP Server
After=network.target remote-fs.target nss-lookup.target

[Service]
EnvironmentFile=/etc/conf.d/apache2
ExecStart=/usr/sbin/apache2 $APACHE2_OPTS -DFOREGROUND
ExecReload=/usr/sbin/apache2 $APACHE2_OPTS -k graceful
ExecStop=/usr/sbin/apache2 $APACHE2_OPTS -k graceful-stop
# We want systemd to give httpd some time to finish gracefully, but still
want # it to kill httpd after TimeoutStopSec if something went wrong
during the # graceful stop. Normally, Systemd sends SIGTERM signal right
after the # ExecStop, which would kill httpd. We are sending useless
SIGCONT here to give # httpd time to finish.
KillSignal=SIGCONT
PrivateTmp=true
#Hardening
CapabilityBoundingSet=CAP_CHOWN CAP_SETGID CAP_SETUID CAP_DAC_OVERRIDE CAP_KILL 
CAP_NET_BIND_SERVICE CAP_IPC_LOCK
SecureBits=noroot-locked
ProtectSystem=full
PrivateDevices=true
MemoryDenyWriteExecute=true

[Install]
WantedBy=multi-user.target


-- 
Neil Bothwick

K: (n., adj.) a binary thousand, which isn't a decimal thousand or even
really a binary thousand (which is eight), but is the binary number
closest to a decimal thousand. This has proven so completely confusing
that it has become a standard.


pgpuqHNUVm4hR.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] Systemd query ...

[Jacques Montier]

Le lun. 15 mai 2023 à 11:58, Wols Lists  a écrit :

> Nothing to do with but sparked by the Apache problem ...
>
> One of the emails mentioned that the "ExecStop" section didn't appear to
> be working ... That's caused me considerable grief in a systemd config
> file I've written ...
>
> Basically, somebody else added an ExecStop section - and all hell broke
> loose. It seemed to be firing on boot :-( And the service in question -
> ScarletDME - seemed to be killing processes at random, like DoveCot ...
>
> Okay, accidentally killing processes it shouldn't is probably down the
> fork/exec code in ScarletDME, I haven't dug into it to know, but systemd
> should not be triggering the stop in the first place. Has anybody else
> encountered anything like this?
>
> Sorry I'm not likely to respond quickly to say "solved", as I need to
> get "in the mood" to get back to debugging, but if anybody has any hints
> and tips, they'd be appreciated, and it might shed some light on that
> Apache problem :-)
>
> Cheers,
> Wol
>
>
Hi Wol,

It was very difficult to get Apache working with systemd Gentoo.
No apache2.service found with apache installation.
so i looked at the Linux Mint OS to copy the apache2.service.
These commands

ExecStart=/usr/sbin/apachectl start
ExecStop=/usr/sbin/apachectl graceful-stop
ExecReload=/usr/sbin/apachectl graceful

did not work at all...
BUT,
By manually launching /usr/bin/apache2ctl, it  worked.

So i wrote a little simple bash script /usr/bin/op_apache

#!/bin/bash

case ${1} in
"start")
apache2ctl
;;
"stop")
killall apache2
;;
"restart")
killall apache2
sleep 1
apache2ctl
;;
esac

And in apache2.service, i put :

ExecStart=/usr/bin/op_apache start
ExecStop=/usr/bin/op_apache stop
ExecReload=/usr/sbin/op_apache restart

Now it works fine, but what a headache !

Cheers,

--
Jacques

Re: [gentoo-user] systemd-journald: user-1000.journal ... Not a XENIX named type file

[Matt Connell]

On Sun, 2023-02-26 at 10:31 +0800, johnstrass wrote:
> Monotonic clock jumped backwards relative last journal entry

Is your system clock accurate?  Is it in sync the the hardware clock,
if the machine has one?

Re: [gentoo-user] systemd-boot on an openrc system

[Peter Humphrey]

On Wednesday, 28 September 2022 12:05:19 BST Nils Freydank wrote:
> Hi Peter,
> 
> long story short: AFAICT it's a deprecated or moved configuration entry
> inside the file /etc/machine-info and should be safe to just delete, maybe
> even with the whole file machine-info itself.
> 
> On my machine with openrc and systemd-boot I don't even have
> /etc/machine-info at all and things work fine together. To me it looks as
> the variable was just thrown out of the machine-info file and in case you
> would need it you should put it into /etc/kernel/install.conf.
> 
> I don't know which software uses the string. If you compile your kernel
> manually or using the gentoo-kernel packages it seems to be not necessary.
> 
> (But as always when taking advice from strangers on the internet: First make
> a backup, have a live medium for recovery at hand and test it yourself.)

Thanks Nils.

Looking more carefully, I see only one machine has an /etc/machine-info. I've 
moved it and I no longer get the warning. Simple as that, eh?

-- 
Regards,
Peter.

Re: [gentoo-user] systemd-boot on an openrc system

[Nils Freydank]

Hi Peter,

long story short: AFAICT it's a deprecated or moved configuration entry inside
the file /etc/machine-info and should be safe to just delete, maybe even with
the whole file machine-info itself.

On my machine with openrc and systemd-boot I don't even have /etc/machine-info
at all and things work fine together. To me it looks as the variable was just
thrown out of the machine-info file and in case you would need it you should
put it into /etc/kernel/install.conf.

I don't know which software uses the string. If you compile your kernel
manually or using the gentoo-kernel packages it seems to be not necessary.

(But as always when taking advice from strangers on the internet: First make a
backup, have a live medium for recovery at hand and test it yourself.)

Kind regards,
Nils


signature.asc
Description: PGP signature

Re: [gentoo-user] systemd-boot on openrc

[Peter Humphrey]

On Sunday, 17 April 2022 14:54:50 -00 Rich Freeman wrote:
> On Sun, Apr 17, 2022 at 9:03 AM Peter Humphrey  
wrote:
> > On Sunday, 17 April 2022 12:13:06 -00 Neil Bothwick wrote:
> > 
> > --->8
> > 
> > > It looks like this is cause my using mixed keywords, amd64 for udev and
> > > ~amd64 for systemd-boot/utils. Does keywording udev-250 resolve the
> > > blocks?
> > 
> > Yes, after keywording several others, thus:
> > 
> > ~sys-apps/systemd-tmpfiles-249.9
> > ~sys-apps/systemd-utils-250.4
> > ~sys-fs/udev-250
> > ~virtual/tmpfiles-0-r2
> > 
> > But then, after rebooting because of the udev update, systemd-boot-250-r1
> > has come in. I can't revert those keywords though, because then I'd have
> > to ditch elogind in favour of systemd. I really do not want to do that.
> 
> 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.

> If I need to bump a package up to ~arch temporarily usually I just do
> it with an atom like " that, so that I keep getting ~arch updates within the major version,
> but the next major bump happens when it hits stable.  Obviously you
> need to understand the versioning/stabilization policies for the
> packages involved if you do that, and it is situational, but you
> really shouldn't be mixing keywords anyway unless you're comfortable
> with that.

No, I know it's a bad idea to mix keywords, but how else do I get systemd-boot 
on a stable system?

-- 
Regards,
Peter.

Re: [gentoo-user] systemd-boot on openrc

[Rich Freeman]

On Sun, Apr 17, 2022 at 9:03 AM Peter Humphrey  wrote:
>
> On Sunday, 17 April 2022 12:13:06 -00 Neil Bothwick wrote:
>
> --->8
> > It looks like this is cause my using mixed keywords, amd64 for udev and
> > ~amd64 for systemd-boot/utils. Does keywording udev-250 resolve the
> > blocks?
>
> Yes, after keywording several others, thus:
>
> ~sys-apps/systemd-tmpfiles-249.9
> ~sys-apps/systemd-utils-250.4
> ~sys-fs/udev-250
> ~virtual/tmpfiles-0-r2
>
> But then, after rebooting because of the udev update, systemd-boot-250-r1 has
> come in. I can't revert those keywords though, because then I'd have to ditch
> elogind in favour of systemd. I really do not want to do that.

Can't you just fix your USE flags with systemd-utils?  Why revert?

If I need to bump a package up to ~arch temporarily usually I just do
it with an atom like "

Re: [gentoo-user] systemd-boot on openrc

[Peter Humphrey]

On Sunday, 17 April 2022 12:13:06 -00 Neil Bothwick wrote:

--->8
> It looks like this is cause my using mixed keywords, amd64 for udev and
> ~amd64 for systemd-boot/utils. Does keywording udev-250 resolve the
> blocks?

Yes, after keywording several others, thus:

~sys-apps/systemd-tmpfiles-249.9
~sys-apps/systemd-utils-250.4
~sys-fs/udev-250 
~virtual/tmpfiles-0-r2 

But then, after rebooting because of the udev update, systemd-boot-250-r1 has 
come in. I can't revert those keywords though, because then I'd have to ditch 
elogind in favour of systemd. I really do not want to do that.

So I have a running system now - thanks. If this gets more complicated in 
future, I can always try blocking =>sys-boot/systemd-boot-250.

> > On another system, ~amd64 openrc, I was
> > told to set USE=boot on systemd-utils, so I did that and now when I
> > boot I have no mouse or keyboard.
> > 
> > Is this the end of the road for systemd-boot on openrc?
> 
> I think that USE flag just causes the systemd-boot part of systemd-utils
> to be built. systemd-boot itself is just a virtual now. It doesn't sound
> like that would cause this problem, did you emerge anything X related at
> the same time?

Nope, nothing else. And I forgot to say that smartd failed to start on that 
machine too, with nothing in dmesg or /var/log/messages. (I'm working on that 
machine via ssh.)

-- 
Regards,
Peter.

Re: [gentoo-user] systemd-boot on openrc

[Neil Bothwick]

On Sun, 17 Apr 2022 11:41:23 +, Peter Humphrey wrote:

> I've been using bootctl from sys-boot/systemd-boot for several years,
> with some success, but I'm stuck after today's --sync.
> 
> First I was told I had to keyword sys-apps/systemd-utils, so I did
> that, but now I get this, which I can't decode:
> 
> Calculating dependencies  ... . . done!
> [ebuild  N~] sys-apps/systemd-utils-250.4::gentoo  USE="boot
> (split-usr) sysusers tmpfiles udev (-selinux) -test" ABI_X86="(64) -32
> (-x32)" 10,872 KiB [ebuild U ~] sys-boot/systemd-boot-250::gentoo
> [249.9::gentoo] 0 KiB [blocks b  ]  (" sys-apps/systemd-utils-250.4) [blocks B  ]
>  soft blocking sys-apps/systemd-utils-250.4) [blocks B  ]
>  apps/systemd-utils-250.4)
> 
> Total: 2 packages (1 upgrade, 1 new), Size of downloads: 10,872 KiB
> Conflict: 3 blocks (2 unsatisfied)
> 
>  * Error: The above package list contains packages which cannot be
>  * installed at the same time on the same system.
> 
>   (sys-apps/systemd-tmpfiles-249.9-2:0/0::gentoo, installed) pulled in
> by sys-apps/systemd-tmpfiles required by
> (virtual/tmpfiles-0-r1-1:0/0::gentoo, installed) USE="" ABI_X86="(64)"
> 
>   (sys-apps/systemd-utils-250.4:0/0::gentoo, ebuild scheduled for
> merge) pulled in by
> sys-apps/systemd-utils[udev] required by (sys-boot/systemd-
> boot-250:0/0::gentoo, ebuild scheduled for merge) USE="" ABI_X86="(64)"
> 
>   (sys-fs/udev-249.6-r2-3:0/0::gentoo, installed) pulled in by
> >=sys-fs/  
> udev-232:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?]
>  
> (>=sys-fs/udev-232:0/0[abi_x86_64(-)]) required by
> (virtual/libudev-232- r5-2:0/1::gentoo, installed) USE="-systemd"
> ABI_X86="(64) -32 (-x32)"
> >=sys-fs/udev-217 required by (virtual/udev-217-r3-1:0/0::gentoo,   
> installed) USE="" ABI_X86="(64)"
> 
> This is an amd64 openrc system.

It looks like this is cause my using mixed keywords, amd64 for udev and
~amd64 for systemd-boot/utils. Does keywording udev-250 resolve the
blocks?

> On another system, ~amd64 openrc, I was
> told to set USE=boot on systemd-utils, so I did that and now when I
> boot I have no mouse or keyboard.
> 
> Is this the end of the road for systemd-boot on openrc?

I think that USE flag just causes the systemd-boot part of systemd-utils
to be built. systemd-boot itself is just a virtual now. It doesn't sound
like that would cause this problem, did you emerge anything X related at
the same time?


-- 
Neil Bothwick

without C people would code in Basi, Pasal and Obol


pgpalhNg49Ji2.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] systemd DNS does not resolve 'local' addresses

[Rich Freeman]

On Sun, Apr 3, 2022 at 4:25 AM Alexander Puchmayr
 wrote:
>
> wasn't systemd per se, it was an update of /etc/nsswitch.conf. The old version
> had
>
> Hosts:  mymachines files myhostname dns
>
> while the new version contains
>
> Hosts:  mymachines resolve [!UNAVAIL=return] files myhostname dns
>
> The extra "resolve [!UNAVAIL=return]" makes the difference. It loads the
> glibc's plugin nss-resolve [1], which then calls systemd-resolved [2], which
> interprets '.local' as mDNS address. The mDNS is not activated on purpose, it
> seems to be some default setting of the router which does not appear in the
> configuration pages (or I didn't find it).

So, the nsswitch file does direct glibc to use the systemd resolve
library, but it is resolved that is using mDNS.  Did you check your
resolved.conf?  Does it have MulticastDNS=no set?  If it isn't
explicitly set you'd probably need to check the build-time options for
what the defaults are these days.

I don't see how your router would impact this.  You don't even need
DHCP/DNS at all to use mDNS, as long as the hosts implement mDNS and
link-local autoconfig.  (Those are addresses in the range
169.254.0.0/16 and fe80::/10.  Many OSes support this at this point by
default.)

In any case, disabling resolved would certainly solve the issue, but
if you want to still use it you can fine-tune the mDNS settings on it.

-- 
Rich

Re: [gentoo-user] systemd DNS does not resolve 'local' addresses

[Alexander Puchmayr]

Thanks for the hint with mDNS, I wasn't aware of that. I'm using the '.local' 
domain for all my machines for more than 15 years now, longer than mDNS 
exists, but finally, after some research I found the problem, and actually it 
wasn't systemd per se, it was an update of /etc/nsswitch.conf. The old version 
had 

Hosts:  mymachines files myhostname dns

while the new version contains

Hosts:  mymachines resolve [!UNAVAIL=return] files myhostname dns

The extra "resolve [!UNAVAIL=return]" makes the difference. It loads the 
glibc's plugin nss-resolve [1], which then calls systemd-resolved [2], which 
interprets '.local' as mDNS address. The mDNS is not activated on purpose, it 
seems to be some default setting of the router which does not appear in the 
configuration pages (or I didn't find it).

Anyway, there are some ways to solve this:
1) create an entry in /etc/hosts on every machine. Contradicts the idea of 
DNS, but works
2) keep the old setting in nsswich.conf (without "resolve ...")
3) change my "own" TLD from .local to something else, like .home, as suggested 
in [3]

I think as long term strategy option 3 would be the best.

Regards
Alex

[1] https://www.freedesktop.org/software/systemd/man/nss-resolve.html
[2] https://www.freedesktop.org/software/systemd/man/systemd-resolved.html#
[3] https://www.rfc-editor.org/rfc/rfc6762#appendix-G



Am Samstag, 2. April 2022, 23:48:06 CEST schrieb Rich Freeman:
> On Sat, Apr 2, 2022 at 5:22 PM Alexander Puchmayr
> 
>  wrote:
> > ## portage.local maps to 192.168.1.6
> > ## DNS-Server provided via DHCP is 192.168.1.1 (openwrt-router)
> > 
> > buildhost-desktop ~ # ping portage.local
> > ping: portage.local: Temporary failure in name resolution
> > 
> >Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
> 
> So, I haven't really used resolved much, but I see you have mDNS
> enabled.  Does the portage.local host broadcast itself using mDNS?  If
> it is running Gentoo then the answer is no unless you have it running
> avahi, which is usually not installed by default.  Many
> desktop-oriented linux distros provide avahi by default.
> 
> A resolver that supports mDNS will not use DNS to resolve the .local
> TLD, in accordance with RFC 6762.
> 
> If you intend to use .local for DNS and not mDNS then you probably do
> not want mDNS enabled.  You can either disable it for resolved
> globally by setting MulticastDNS=no in the [Resolve] section of
> /etc/systemd/resolved.conf, or by disabling it for a specific network
> in your network manager (the setting has the same name for
> systemd-networkd).
> 
> This is one of those reasons why it is best to not use the .local TLD
> for DNS on your home network.  You can disable it on systemd-resolved,
> but some IoT device in your home might have it permanently enabled.
> It allows a form of name resolution to work without any DNS server as
> devices discover and broadcast on their own.

Re: [gentoo-user] systemd DNS does not resolve 'local' addresses

[Rich Freeman]

On Sat, Apr 2, 2022 at 5:22 PM Alexander Puchmayr
 wrote:
>
> ## portage.local maps to 192.168.1.6
> ## DNS-Server provided via DHCP is 192.168.1.1 (openwrt-router)
>
> buildhost-desktop ~ # ping portage.local
> ping: portage.local: Temporary failure in name resolution
>
>Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported

So, I haven't really used resolved much, but I see you have mDNS
enabled.  Does the portage.local host broadcast itself using mDNS?  If
it is running Gentoo then the answer is no unless you have it running
avahi, which is usually not installed by default.  Many
desktop-oriented linux distros provide avahi by default.

A resolver that supports mDNS will not use DNS to resolve the .local
TLD, in accordance with RFC 6762.

If you intend to use .local for DNS and not mDNS then you probably do
not want mDNS enabled.  You can either disable it for resolved
globally by setting MulticastDNS=no in the [Resolve] section of
/etc/systemd/resolved.conf, or by disabling it for a specific network
in your network manager (the setting has the same name for
systemd-networkd).

This is one of those reasons why it is best to not use the .local TLD
for DNS on your home network.  You can disable it on systemd-resolved,
but some IoT device in your home might have it permanently enabled.
It allows a form of name resolution to work without any DNS server as
devices discover and broadcast on their own.

-- 
Rich

Re: [gentoo-user] systemd boot timer

[Rich Freeman]

On Fri, Oct 1, 2021 at 4:36 PM antlists  wrote:
>
> I now want to run lvm snapshot on the first boot of the weekend. Writing
> a unit to do the snapshot seems pretty easy, but obviously I don't want
> it firing every boot, if I stick the date in the volume name I don't
> want it colliding with an earlier run the same day, etc etc.

I'm not sure a timer is a great way to do this.  Offhand I'm not sure
how the persistence on those works exactly - maybe you could get it to
fire off when you want it to.  However, there is another issue you're
missing.

I assume you want to wait for the snapshot to complete before you
mount local filesystems.  Normally you'd just do this with a
dependency - the local filesystems get an After dependency on your
snapshot, so they don't get mounted until the snapshot is complete.
The problem is that the service that does the snapshot won't be
enabled - so the dependency will not constrain mounting the
filesystems.  An After dependency on its own doesn't cause the thing
it depends on to run - it just says that IF it is going to run it has
to run first.  The service that does the snapshot is going to be
started by the timer, not a target, and so at the moment the
dependencies are analyzed it won't be taken into account.  That
creates a race condition, since timers do not launch their services in
any sort of synchronization with the system startup.

Now, you could set a dependency on the snapshot such that it doesn't
let filesystems be mounted while it runs, but then when it gets run it
will force all your filesystems to unmount (which is basically going
to do a clean near-shutdown of your entire system to whatever degree
it has started up), then do the snapshot, then remount everything and
restart it all.  That isn't what you want either.

I think the cleanest approach is just make the snapshot a regular
service and enable it and set up the dependencies so that it has to
complete before local filesystems are mounted.  Then all you need to
do is put logic in that service that turns it into a no-op if there is
a recent enough snapshot already.

Timers are really useful for stuff that is asynchronous, whether
time-based or not.  They're not really good for anything synchronous
with the boot process, unless there is some magic to this that I'm
unaware of.

-- 
Rich

Re: [gentoo-user] systemd boot timer

[Canek Peláez Valdés]

On Fri, Oct 1, 2021 at 5:24 PM antlists  wrote:
[...]

> Ouch. Dunno if that would work. Bear in mind I'm running this BEFORE
> fstab, so / is read-only ...
>

You can store the timestamp in /run and then have another unit that updates
the timestamp in /var after remounting root (/) read/write. Again, you have
all the flexibility of scripts+systemd units.

I will have to see if the timer can set up the oneshot service, and if
> it really is one shot per activation ...
>

It's one shot per activation, but the activation is set either by timer, or
by unit dependency (After= and/or Before=), AFAIU. I don't think the
granularity you want is there: the timer will elapse once a week, whether
you are booting or running the system (if using timers); or it will run at
boot, whether a week has passed or not (if using a normal service). I don't
think you can mix and match; the precise state you want is beyond what
systemd offers (I think).

I think the simpler answer is to write a script and handle the state
yourself; but knock yourself up. It's possible I'm wrong and you can do
that with only systemd units/timers.

Regards.
[1] https://man7.org/linux/man-pages/man5/systemd.timer.5.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

Re: [gentoo-user] systemd boot timer

[antlists]

On 01/10/2021 22:54, Canek Peláez Valdés wrote:
On Fri, Oct 1, 2021 at 3:37 PM antlists > wrote:






I think it would be much simpler to have a Type=oneshot service at boot, 
and the Exec= line to call a script. You can store the timestamp of the 
last time it was called someplace in the filesystem (say, 
/var/lib/my-script or something), and if the timestamp doesn't exists or 
is older than one week, the scripts executes lvm snapshot and updates 
the timestamp; otherwise it ends without doing anything.


Ouch. Dunno if that would work. Bear in mind I'm running this BEFORE 
fstab, so / is read-only ...


The timer units are very similar to cron, and I believe what you want 
cannot be done with cron either; you need special logic and state ("I'm 
booting AND haven't run this in at least a week"), so a script is 
necessary (I think). Luckly, systemd allows you to smartly manage your 
scripts and impose dependencies on them (you need /var in my example, 
and you can set it to run before starting X).


I will have to see if the timer can set up the oneshot service, and if 
it really is one shot per activation ...


Cheers,
Wol

Re: [gentoo-user] systemd boot timer

[Canek Peláez Valdés]

On Fri, Oct 1, 2021 at 3:37 PM antlists  wrote:

> I'm trying to get a systemd unit to fire on boot once a week. Reading up
> on timer units, I can't work out how to get it to work.
>
> This is tied up with my earlier systemd mount post - I've now got that
> sorted - I've got dm-integrity to fire before fstab.
>
> I now want to run lvm snapshot on the first boot of the weekend. Writing
> a unit to do the snapshot seems pretty easy, but obviously I don't want
> it firing every boot, if I stick the date in the volume name I don't
> want it colliding with an earlier run the same day, etc etc.
>
> The question really is - if I have a weekly timer fire and activate the
> unit, is the activation going to survive the reboot to run on the next
> boot?
>
> The problem I'm having is that all the stuff I've seen about timers says
> you have two lines - activate on Saturdays, and activate on boot. Snag
> is, they seem to be independent such that EITHER condition will activate
> the service. As I say, I want BOTH. I don't want the service running
> while the system is up and running.
>

I'm not sure timer units have enough flexibility to do what you want.

I think it would be much simpler to have a Type=oneshot service at boot,
and the Exec= line to call a script. You can store the timestamp of the
last time it was called someplace in the filesystem (say,
/var/lib/my-script or something), and if the timestamp doesn't exists or is
older than one week, the scripts executes lvm snapshot and updates the
timestamp; otherwise it ends without doing anything.

The timer units are very similar to cron, and I believe what you want
cannot be done with cron either; you need special logic and state ("I'm
booting AND haven't run this in at least a week"), so a script is necessary
(I think). Luckly, systemd allows you to smartly manage your scripts and
impose dependencies on them (you need /var in my example, and you can set
it to run before starting X).

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] systemd mount - what on earth is it doing ...

[antlists]

On 25/09/2021 21:30, Canek Peláez Valdés wrote:
On Sat, Sep 25, 2021 at 1:48 PM antlists > wrote:

[...]

Bear in mind, integritysetup is not in my initrd, so ...


I think you would need to put it in your initrd.

If I've got my root on it (which is the plan, but that means learning 
how to cut my own stuff into the initrd ...)



It looks to me like grub switches to the real root partition read-only
before firing stuff off, so if I tell my integritysetup.service to run
before local-fs.target, does that mean everything should be working
before systemd runs fstab?

Bear in mind dm-integrity is on my raw partitions, and I'm running lvm
and md-raid, I'm guessing they're part of local-fs-pre.target? So I
really need to run dm-integrity before that? Or preferably add
dm-integrity TO that - how do I do that?

The problem is this isn't all that discoverable - even digging around
/etc/systemd, it's hard to find clues ...


As Rich already mentioned it, noauto != remove mount point from fstab. 
That's the first thing.


Well, it's working, which is the important thing. I just want to 
understand WHY it's working - especially since when it was working the 
other way it broke Wayland ... which was why it was weird ...


Then you need to specify that home.mount should run *after* md/LVM, 
which in turn runs after your integrity setup service. The problem is: 
you have root (/) on md/LVM too; I know they are different 
RAIDs/volumes, but there is one *service* for RAID and LVM, at least 
out-of-the-box, in systemd. You could try to split different instances 
using templates (the units with @ in their names), but the simplest 
solution is to put your integrity logic in the initrd (with the added 
benefit that you can mount it in emergencies if something goes wrong 
with root).


At the moment, with root on lvm but not anything else, gentoo takes care 
of all that for me. I'm not ready for the next learning curve of doing 
all that myself in the initrd ...


If you have the integrity logic in early boot, then your integrity setup 
service should have:


Before=mdmonitor.service lvm2-lvmetad.service

And I think that should be enough? The home.mount unit depends on the 
underlying device being available, and that will happen only after md 
and LVM have done it's thing.


I'll try that. lvm should act on the root (sda3) device directly, but 
integrity needs to run before md will join sda4 and sdc4, and then lvm 
will run on the raid to make home available for fstab.


I'll play with that and get rid of the home.mount, and hope that all 
that doesn't break Wayland. What I don't understand was that when 
home.mount was enabled, it worked but broke Wayland, now I've disabled 
it it still appears to be working, but Wayland is working too! That's 
what I'd like to understand.


Although if fixing it how you suggest fixes everything, then I'll have 
an understandable, working system, and I'll be happy.


Cheers,
Wol

Re: [gentoo-user] systemd mount - what on earth is it doing ...

[Rich Freeman]

On Sat, Sep 25, 2021 at 4:30 PM Canek Peláez Valdés  wrote:
>
>  the simplest solution is to put your integrity logic in the initrd (with the 
> added benefit that you can mount it in emergencies if something goes wrong 
> with root).
>

If you want to try this, consider this article I wrote ages ago.  I no
longer use this but it is a quick recipe for how to create your own
dracut module:
https://rich0gentoo.wordpress.com/2012/01/21/a-quick-dracut-module/

It is really easy to tweak dracut, and it has a lot of automagic
functionality which means you mostly only need to worry about whatever
is particular with your setup.  You can also have your module grab any
config files and binaries/libraries needed off of your filesystem so
that they are available when it runs.

-- 
Rich

Re: [gentoo-user] systemd mount - what on earth is it doing ...

[Canek Peláez Valdés]

On Sat, Sep 25, 2021 at 1:48 PM antlists  wrote:
[...]

> Bear in mind, integritysetup is not in my initrd, so ...
>

I think you would need to put it in your initrd.


> It looks to me like grub switches to the real root partition read-only
> before firing stuff off, so if I tell my integritysetup.service to run
> before local-fs.target, does that mean everything should be working
> before systemd runs fstab?
>
> Bear in mind dm-integrity is on my raw partitions, and I'm running lvm
> and md-raid, I'm guessing they're part of local-fs-pre.target? So I
> really need to run dm-integrity before that? Or preferably add
> dm-integrity TO that - how do I do that?
>
> The problem is this isn't all that discoverable - even digging around
> /etc/systemd, it's hard to find clues ...
>

As Rich already mentioned it, noauto != remove mount point from fstab.
That's the first thing.

Then you need to specify that home.mount should run *after* md/LVM, which
in turn runs after your integrity setup service. The problem is: you have
root (/) on md/LVM too; I know they are different RAIDs/volumes, but there
is one *service* for RAID and LVM, at least out-of-the-box, in systemd. You
could try to split different instances using templates (the units with @ in
their names), but the simplest solution is to put your integrity logic in
the initrd (with the added benefit that you can mount it in emergencies if
something goes wrong with root).

If you have the integrity logic in early boot, then your integrity setup
service should have:

Before=mdmonitor.service lvm2-lvmetad.service

And I think that should be enough? The home.mount unit depends on the
underlying device being available, and that will happen only after md and
LVM have done it's thing.

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] systemd mount - what on earth is it doing ...

[antlists]

On 24/09/2021 21:30, Canek Peláez Valdés wrote:
On Fri, Sep 24, 2021 at 2:25 PM antlists > wrote:


This is weird ...

My /home directory is set up somewhat strangely, as in I've got two raw
partitions, I've put dm-integrity on them, raided them together, then
put lvm on top of that.


Which got me into a bind with fstab. I've created a systemd service,
which fires up dm-integrity on those two partitions. But I get the
impression it doesn't run until fstab completes. Catch-22 - fstab tries
to mount /home, but it can't until dm-integrity has made the volume
appear!


Have you tried using Before=local-fs.target in the service? Or even 
Before=local-fs-pre.target?


Bear in mind, integritysetup is not in my initrd, so ...

It looks to me like grub switches to the real root partition read-only 
before firing stuff off, so if I tell my integritysetup.service to run 
before local-fs.target, does that mean everything should be working 
before systemd runs fstab?


Bear in mind dm-integrity is on my raw partitions, and I'm running lvm 
and md-raid, I'm guessing they're part of local-fs-pre.target? So I 
really need to run dm-integrity before that? Or preferably add 
dm-integrity TO that - how do I do that?


The problem is this isn't all that discoverable - even digging around 
/etc/systemd, it's hard to find clues ...


Cheers,
Wol

Re: [gentoo-user] systemd mount - what on earth is it doing ...

[Rich Freeman]

On Sat, Sep 25, 2021 at 6:49 AM antlists  wrote:
>
> On 24/09/2021 21:30, Canek Peláez Valdés wrote:
>
> There's a lot of info about how to write a service file, but if you need
> to run before or after system service files, it's nowhere near so easy
> to find out Before=WHAT or After=WHAT :-)

So, I have a similar challenge because I use lizardfs and it can take
a while to initialize, and it isn't something systemd understands out
of the box.  (Plus it depends on a container running on the same host,
and those tend to run late, and other containers depend on the mount.)

I solved my issues with drop-ins and dependencies.

I did not create a mount unit for the mount.  I'm using fstab and its
generator to manage that.  However, I did use a drop-in so that the
automatically-created unit obtains the additional dependencies and
loads in the right order.  This requires using the right unit name as
created by the generator.

I set up dependencies for the mount unit so that it would run after
things that it needed.  I also set dependencies on services that use
the mount, so that they load later.  This wasn't something like home,
so I didn't apply those dependencies to a target.  However, if you
want to tie this into a standard target I suggest checking man
systemd.special or ask around.

> >
> > So I created a systemd mount unit for /home, which only runs after
> > dm-integrity. Great - I enabled it and it appeared to work!
> >
> >
> > You removed the /home entry from fstab, right?
> >
> mad it noauto, yes ...

That won't prevent the system from creating a unit for it - it just
won't be a dependency of local-fs.target.

I would suggest using only ONE of the following two approaches:1.
Entry in fstab plus a drop-in to modify its behavior with the same
name.
2. Custom mount unit with no entry in fstab at all (commented out is
fine, noauto is not).

It is possible you have more than one unit for the same mountpoint.
I'm not sure how exactly that behaves.  I'd just run "systemctl | grep
mount" and see what comes up - see if you have two apparent entries
for home.  If so one is probably from fstab and the other is probably
from your custom unit.  Unless they have the exact same name your unit
won't override the system one, and I'm actually not quite sure how
generators interact with unit overrides.  They seem to work fine with
drop-ins which is why I used this approach.

> > That should be home.mount. What does systemctl status home.mount says?
> >
> anthony@thewolery ~ $ systemctl status home.mount
> ● home.mount - Mount Home
>   Loaded: loaded (/etc/systemd/system/home.mount; disabled; vendor
> preset: disabled)
>
> > So what on earth is going on, and more importantly, what am I
> > misunderstanding or doing wrong. I would very much like to know why
> > it's
> > working, when I think it shouldn't be!
> >
> So fstab says noauto, home.mount is disabled, and /home is mounted on
> boot...
>

Using noauto only prevents it from being a dep for local-fs.target.
It doesn't prevent it from being mounted for some other reason.

I'd look at:
systemctl list-dependencies --reverse home.mount

Another command you might find useful is systemd-analyze dot.  The
direct output is actually readable, though intended to be converted
into a chart with graphviz using the hinted command it outputs.

If anything explicitly wants home.mount then it is going to get
mounted even if set to noauto.

Systemd is one of those things that is really capable, but you have to
grok a lot of concepts to make it dance for you, otherwise you'll feel
like you're the one being made to dance.  The internet is full of
one-liners now that it is so popular, but these often obfuscate how it
actually works.  It operates using a series of basic rules and once
you get how they're being strung together to make things work then it
is a lot easier to make it do what you expect.  Lennart's original
blog posts about systemd are very useful for this - maybe there are
some other good resources out there these days.

-- 
Rich

Re: [gentoo-user] systemd mount - what on earth is it doing ...

[antlists]

On 24/09/2021 21:30, Canek Peláez Valdés wrote:
On Fri, Sep 24, 2021 at 2:25 PM antlists > wrote:


This is weird ...

My /home directory is set up somewhat strangely, as in I've got two raw
partitions, I've put dm-integrity on them, raided them together, then
put lvm on top of that.


Which got me into a bind with fstab. I've created a systemd service,
which fires up dm-integrity on those two partitions. But I get the
impression it doesn't run until fstab completes. Catch-22 - fstab tries
to mount /home, but it can't until dm-integrity has made the volume
appear!


Have you tried using Before=local-fs.target in the service? Or even 
Before=local-fs-pre.target?


You mean in my integritysetup.service file? No, because in scrabbling 
around to try and find out what magic incantation was required, I didn't 
find it.


There's a lot of info about how to write a service file, but if you need 
to run before or after system service files, it's nowhere near so easy 
to find out Before=WHAT or After=WHAT :-)


So I created a systemd mount unit for /home, which only runs after
dm-integrity. Great - I enabled it and it appeared to work!


You removed the /home entry from fstab, right?


mad it noauto, yes ...


Only problem, startplasma-wayland now dumped me at a blank screen.

Now for the weirdo. I disabled it, thinking I would have to log in as
root, mount /home, and go from there. Except that, when I logged in,
/home was mounted and startplasma-wayland worked!


That sounds like /home was still on fstab...


#LABEL=boot /boot   ext4noauto,noatime  1 2
/dev/disk/by-uuid/F436-354A /boot   vfatnoauto,noatime  1 2
#UUID=58e72203-57d1-4497-81ad-97655bd56494  /   ext4
noatime 0 1
#LABEL=swap noneswapsw  0 0
#/dev/cdrom /mnt/cdrom  autonoauto,ro   0 0
/dev/vg-root/lv-gentoo  /   ext4rw  0   0
/dev/vg-home/lv-data/home   ext4noauto,rw   0   0
/dev/disk/by-uuid/e2b75f09-8cb4-4e20-9cfd-21c0aadfa540  noneswap 
sw,pri=10   0
/dev/disk/by-uuid/e03459f5-1f57-485b-92e4-b09cf50534c1	none	swap 
sw,pri=1	0	0


systemctl tells me mount.home is disabled, but also tells me that it
ran
and mounted the drive.


That should be home.mount. What does systemctl status home.mount says?


anthony@thewolery ~ $ systemctl status home.mount
● home.mount - Mount Home
 Loaded: loaded (/etc/systemd/system/home.mount; disabled; vendor 
preset: disabled)
 Active: active (mounted) since Fri 2021-09-24 20:13:49 BST; 2min 
51s ago

  Where: /home
   What: /dev/mapper/vg--home-lv--data
CPU: 13ms
 CGroup: /system.slice/home.mount

Sep 24 20:13:48 thewolery systemd[1]: Mounting Mount Home...
Sep 24 20:13:49 thewolery systemd[1]: Mounted Mount Home.
anthony@thewolery ~ $ cd Scans/HP-M477/


So what on earth is going on, and more importantly, what am I
misunderstanding or doing wrong. I would very much like to know why
it's
working, when I think it shouldn't be!

So fstab says noauto, home.mount is disabled, and /home is mounted on 
boot...


Cheers,
Wol

Re: [gentoo-user] systemd mount - what on earth is it doing ...

[Canek Peláez Valdés]

On Fri, Sep 24, 2021 at 2:25 PM antlists  wrote:

> This is weird ...
>
> My /home directory is set up somewhat strangely, as in I've got two raw
> partitions, I've put dm-integrity on them, raided them together, then
> put lvm on top of that.
>

> Which got me into a bind with fstab. I've created a systemd service,
> which fires up dm-integrity on those two partitions. But I get the
> impression it doesn't run until fstab completes. Catch-22 - fstab tries
> to mount /home, but it can't until dm-integrity has made the volume appear!
>

Have you tried using Before=local-fs.target in the service? Or even
Before=local-fs-pre.target?

So I created a systemd mount unit for /home, which only runs after
> dm-integrity. Great - I enabled it and it appeared to work!
>

You removed the /home entry from fstab, right?


> Only problem, startplasma-wayland now dumped me at a blank screen.
>
> Now for the weirdo. I disabled it, thinking I would have to log in as
> root, mount /home, and go from there. Except that, when I logged in,
> /home was mounted and startplasma-wayland worked!
>

That sounds like /home was still on fstab...


> systemctl tells me mount.home is disabled, but also tells me that it ran
> and mounted the drive.
>

That should be home.mount. What does systemctl status home.mount says?


> So what on earth is going on, and more importantly, what am I
> misunderstanding or doing wrong. I would very much like to know why it's
> working, when I think it shouldn't be!
>

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] systemd install attempt busybox and pam are fighting

[Neil Bothwick]

On Fri, 13 Nov 2020 18:59:24 -0500, Jude DaShiell wrote:

> Thanks for the decode, I hope I'll get better at understanding this kind
> of error output in future.

You will, it takes a while to learn to speak portagese :)
 
> On Fri, 13 Nov 2020, Neil Bothwick wrote:
> 
> > Date: Fri, 13 Nov 2020 18:28:32
> > From: Neil Bothwick 
> > Reply-To: gentoo-user@lists.gentoo.org
> > To: gentoo-user@lists.gentoo.org
> > Subject: Re: [gentoo-user] systemd install attempt busybox and pam are
> > fighting
> >
> > On Fri, 13 Nov 2020 17:40:43 -0500, Jude DaShiell wrote:
> >  
> > > !!! The ebuild selected to satisfy "sys-apps/busybox" has unmet
> > > requirements.
> > > - sys-apps/busybox-1.32.0-r1::gentoo USE="ipv6 pam static systemd
> > > -debug -livecd -make-symlinks -math -mdev -savedconfig (-selinux)
> > > -sep-usr -syslog" ABI_X86="(64)"
> > >
> > >   The following REQUIRED_USE flag constraints are unsatisfied:
> > > pam? ( !static )  
> >
> > It means that if you have the pam USE flag set, the static flag must
> > be unset. You can have one or the other, or neither, but not both.
> >
> >
> >  
> 




-- 
Neil Bothwick

If a deaf person swears, does his mother wash his hands with soap?


pgpH8CqFMwgiV.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] systemd install attempt busybox and pam are fighting

[Jude DaShiell]

Thanks,

Now I got me a slot conflict.  That's the first time I ever ran into one
of those but I suppose they're a gentoo feature.

On Fri, 13 Nov 2020, Neil Bothwick wrote:

> Date: Fri, 13 Nov 2020 18:28:32
> From: Neil Bothwick 
> Reply-To: gentoo-user@lists.gentoo.org
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] systemd install attempt busybox and pam are
> fighting
>
> On Fri, 13 Nov 2020 17:40:43 -0500, Jude DaShiell wrote:
>
> > !!! The ebuild selected to satisfy "sys-apps/busybox" has unmet
> > requirements.
> > - sys-apps/busybox-1.32.0-r1::gentoo USE="ipv6 pam static systemd
> > -debug -livecd -make-symlinks -math -mdev -savedconfig (-selinux)
> > -sep-usr -syslog" ABI_X86="(64)"
> >
> >   The following REQUIRED_USE flag constraints are unsatisfied:
> > pam? ( !static )
>
> It means that if you have the pam USE flag set, the static flag must be
> unset. You can have one or the other, or neither, but not both.
>
>
>

-- 
United States has 633 Billionaires with only 10 doing any annual
significant giving.

Re: [gentoo-user] systemd install attempt busybox and pam are fighting

[Jude DaShiell]

I think I like neither, makes use flags a little shorter.

I know what I've done in make.conf it's the rest of the system I need to
research.

On Fri, 13 Nov 2020, Neil Bothwick wrote:

> Date: Fri, 13 Nov 2020 18:28:32
> From: Neil Bothwick 
> Reply-To: gentoo-user@lists.gentoo.org
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] systemd install attempt busybox and pam are
> fighting
>
> On Fri, 13 Nov 2020 17:40:43 -0500, Jude DaShiell wrote:
>
> > !!! The ebuild selected to satisfy "sys-apps/busybox" has unmet
> > requirements.
> > - sys-apps/busybox-1.32.0-r1::gentoo USE="ipv6 pam static systemd
> > -debug -livecd -make-symlinks -math -mdev -savedconfig (-selinux)
> > -sep-usr -syslog" ABI_X86="(64)"
> >
> >   The following REQUIRED_USE flag constraints are unsatisfied:
> > pam? ( !static )
>
> It means that if you have the pam USE flag set, the static flag must be
> unset. You can have one or the other, or neither, but not both.
>
>
>

-- 
United States has 633 Billionaires with only 10 doing any annual
significant giving.

Re: [gentoo-user] systemd install attempt busybox and pam are fighting

[Manuel McLure]

On Fri, Nov 13, 2020 at 3:59 PM Jude DaShiell  wrote:

> Thanks for the decode, I hope I'll get better at understanding this kind
> of error output in future.
>
> On Fri, 13 Nov 2020, Neil Bothwick wrote:
>
> > Date: Fri, 13 Nov 2020 18:28:32
> > From: Neil Bothwick 
> > Reply-To: gentoo-user@lists.gentoo.org
> > To: gentoo-user@lists.gentoo.org
> > Subject: Re: [gentoo-user] systemd install attempt busybox and pam are
> > fighting
> >
> > On Fri, 13 Nov 2020 17:40:43 -0500, Jude DaShiell wrote:
> >
> > > !!! The ebuild selected to satisfy "sys-apps/busybox" has unmet
> > > requirements.
> > > - sys-apps/busybox-1.32.0-r1::gentoo USE="ipv6 pam static systemd
> > > -debug -livecd -make-symlinks -math -mdev -savedconfig (-selinux)
> > > -sep-usr -syslog" ABI_X86="(64)"
> > >
> > >   The following REQUIRED_USE flag constraints are unsatisfied:
> > > pam? ( !static )
> >
> > It means that if you have the pam USE flag set, the static flag must be
> > unset. You can have one or the other, or neither, but not both.
>
>
As a related comment, I highly recommend having a statically linked busybox
installed on your system. It can save your bacon if something breaks.
Several years ago there was a problem where "expr" was missing a dependency
on gmp. gmp got upgraded without rebuilding "expr", and that resulted in
"expr" not working. I tried to reinstall "expr"  but emerge required "expr"
to work so I was in a bind. Luckily I had a statically linked busybox on
the system - I just hard-linked busybox to "/usr//bin/expr" and that was
sufficient to get emerge to rebuild the proper "expr".

This was a case where even booting with a live CD would have been tricky,
because as soon as I'd done a chroot I would have ended up with the same
broken "expr". Having a static busybox saved me a lot of hassle.
-- 
Manuel A. McLure WW1FA  <http://www.mclure.org>
...for in Ulthar, according to an ancient and significant law,
no man may kill a cat.   -- H.P. Lovecraft

Re: [gentoo-user] systemd install attempt busybox and pam are fighting

[Jude DaShiell]

Thanks for the decode, I hope I'll get better at understanding this kind
of error output in future.

On Fri, 13 Nov 2020, Neil Bothwick wrote:

> Date: Fri, 13 Nov 2020 18:28:32
> From: Neil Bothwick 
> Reply-To: gentoo-user@lists.gentoo.org
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] systemd install attempt busybox and pam are
> fighting
>
> On Fri, 13 Nov 2020 17:40:43 -0500, Jude DaShiell wrote:
>
> > !!! The ebuild selected to satisfy "sys-apps/busybox" has unmet
> > requirements.
> > - sys-apps/busybox-1.32.0-r1::gentoo USE="ipv6 pam static systemd
> > -debug -livecd -make-symlinks -math -mdev -savedconfig (-selinux)
> > -sep-usr -syslog" ABI_X86="(64)"
> >
> >   The following REQUIRED_USE flag constraints are unsatisfied:
> > pam? ( !static )
>
> It means that if you have the pam USE flag set, the static flag must be
> unset. You can have one or the other, or neither, but not both.
>
>
>

-- 
United States has 633 Billionaires with only 10 doing any annual
significant giving.

Re: [gentoo-user] systemd install attempt busybox and pam are fighting

[Neil Bothwick]

On Fri, 13 Nov 2020 17:40:43 -0500, Jude DaShiell wrote:

> !!! The ebuild selected to satisfy "sys-apps/busybox" has unmet
> requirements.
> - sys-apps/busybox-1.32.0-r1::gentoo USE="ipv6 pam static systemd
> -debug -livecd -make-symlinks -math -mdev -savedconfig (-selinux)
> -sep-usr -syslog" ABI_X86="(64)"
> 
>   The following REQUIRED_USE flag constraints are unsatisfied:
> pam? ( !static )

It means that if you have the pam USE flag set, the static flag must be
unset. You can have one or the other, or neither, but not both.


-- 
Neil Bothwick

Honk if you love peace and quiet.


pgpiOtq88Z7CJ.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] systemd 246 gives strange messages

[John Covici]

On Wed, 12 Aug 2020 10:55:14 -0400,
Rich Freeman wrote:
> 
> On Wed, Aug 12, 2020 at 9:32 AM John Covici  wrote:
> >
> > Does this indicate a problem, and if not, how can I stop these
> > messages?
> >
> 
> I'm guessing it is just log spam, but I don't use Gnome so I can't
> really be sure.  You might do well to ask on a Gnome mailing list, or
> maybe ping one of the gnome maintainers on Gentoo.
> 
> It looks like Gnome is integrating with systemd via xdg and a new
> systemd generator to have systemd automatically launch some services
> based on events.  If I had to take a wild guess some of these services
> are managed by systemd, and others are not, and systemd is being noisy
> about the ones that aren't.
> 
> But it is also possible something is broken.  I bet a Gnome maintainer
> would know what is going on offhand.  They may not monitor this list
> but if you pinged one on IRC/email and asked them to look they
> probably would.  The Gentoo maintainer is probably your best first
> bet, but we probably run relatively close to upstream since that's how
> Gentoo does stuff, so upstream might also help you.  I know on the
> systemd front we try to stay close to upstream (much closer to
> something like Arch than something like Ubuntu).

OK, I will check, thanks a lot.

-- 
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] systemd 246 gives strange messages

[Rich Freeman]

On Wed, Aug 12, 2020 at 9:32 AM John Covici  wrote:
>
> Does this indicate a problem, and if not, how can I stop these
> messages?
>

I'm guessing it is just log spam, but I don't use Gnome so I can't
really be sure.  You might do well to ask on a Gnome mailing list, or
maybe ping one of the gnome maintainers on Gentoo.

It looks like Gnome is integrating with systemd via xdg and a new
systemd generator to have systemd automatically launch some services
based on events.  If I had to take a wild guess some of these services
are managed by systemd, and others are not, and systemd is being noisy
about the ones that aren't.

But it is also possible something is broken.  I bet a Gnome maintainer
would know what is going on offhand.  They may not monitor this list
but if you pinged one on IRC/email and asked them to look they
probably would.  The Gentoo maintainer is probably your best first
bet, but we probably run relatively close to upstream since that's how
Gentoo does stuff, so upstream might also help you.  I know on the
systemd front we try to stay close to upstream (much closer to
something like Arch than something like Ubuntu).

-- 
Rich

Re: [gentoo-user] systemd crashes when I try to mount a USB drive

[Mike Gilbert]

On Thu, Aug 1, 2019 at 9:59 AM Helmut Jarausch  wrote:
>
> Hi,
> since the upgrade from systemd-242-r6 to systemd-243_rc1 I cannot mount
> my (external) USB drive any more.
> I get
> kernel: sd 10:0:0:0: [sde] Assuming drive cache: write through
> kernel:  sde: sde1 sde2 sde3 sde4 sde5 sde6 sde7
> kernel: systemd-udevd[480887]:
> Assertion 'key' failed at src/libsystemd/sd-device/device-private.c:34,
> function device_add_property(). Aborting.
>
> The strange thing is, I don't use systemd on start-up (I'm using
> openrc) but I have systemd installed here.
> This configuration has been working for a very long time.
>
> Many thanks for a hint,
> Helmut

A failed assertion almost always means there is a programming error in
the software. Please report the issue to the systemd developers.

https://github.com/systemd/systemd/issues

Re: [gentoo-user] systemd crashes when I try to mount a USB drive

[Mick]

On Thursday, 1 August 2019 20:29:08 BST Jack wrote:
> On 2019.08.01 09:59, Helmut Jarausch wrote:
> > Hi,
> > since the upgrade from systemd-242-r6 to systemd-243_rc1 I cannot
> > mount my (external) USB drive any more.
> > I get
> > kernel: sd 10:0:0:0: [sde] Assuming drive cache: write through
> > kernel:  sde: sde1 sde2 sde3 sde4 sde5 sde6 sde7
> > kernel: systemd-udevd[480887]:
> > Assertion 'key' failed at
> > src/libsystemd/sd-device/device-private.c:34,
> > function device_add_property(). Aborting.
> > 
> > The strange thing is, I don't use systemd on start-up (I'm using
> > openrc) but I have systemd installed here.
> > This configuration has been working for a very long time.
> > 
> > Many thanks for a hint,
> > Helmut
> 
> Helmut,
> 
> You say you don't use systemd on start-up, but is any of it running
> when you get this error?  If you aren't using it at start-up, I wonder
> what the implcations are of having it installed - where might it have
> insinuated itself, so it gets called instead of something else you
> might have expected.
> 
> Next time you get the error, can you do "ps auxf" to see if you can
> tell what processes called systemd-udevd?
> 
> Jack

Could it be the systemd upgrade you refer to interfered with any udev rules 
you had set up to deal with your external drive, or in any case changes in 
udev rules are no longer agreeable with your external device?

-- 
Regards,

Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] systemd crashes when I try to mount a USB drive

[Jack]

On 2019.08.01 09:59, Helmut Jarausch wrote:

Hi,
since the upgrade from systemd-242-r6 to systemd-243_rc1 I cannot  
mount my (external) USB drive any more.

I get
kernel: sd 10:0:0:0: [sde] Assuming drive cache: write through
kernel:  sde: sde1 sde2 sde3 sde4 sde5 sde6 sde7
kernel: systemd-udevd[480887]:
Assertion 'key' failed at  
src/libsystemd/sd-device/device-private.c:34,

function device_add_property(). Aborting.

The strange thing is, I don't use systemd on start-up (I'm using  
openrc) but I have systemd installed here.

This configuration has been working for a very long time.

Many thanks for a hint,
Helmut

Helmut,

You say you don't use systemd on start-up, but is any of it running  
when you get this error?  If you aren't using it at start-up, I wonder  
what the implcations are of having it installed - where might it have  
insinuated itself, so it gets called instead of something else you  
might have expected.


Next time you get the error, can you do "ps auxf" to see if you can  
tell what processes called systemd-udevd?


Jack

Re: [gentoo-user] Systemd-boot not compiling

[Peter Humphrey]

On Tuesday, 9 April 2019 17:36:04 BST Mike Gilbert wrote:

> The above log snippet is fairly useless. In the future, please make
> sure to include the relevant log snippet, or attach/pastebin the
> entire build log if in doubt.

I had all the logs etc ready to send; I wanted first to see if it was a common 
problem or just mine.

> The most important part of the log on bug 682908 was this:
> 
> Call stack:
>  ebuild.sh, line 124:  Called src_compile
>environment, line 2145:  Called die
>  The specific snippet of code:
>   patchelf --remove-rpath bootctl || die
> 
> That tells me that the patchelf call in src_compile was failing and
> gives a much better starting point than some cryptic "stat" error.

Indeed, but I didn't get that in my log. I'd have come to the same conclusion 
if I had.

-- 
Regards,
Peter.

Re: [gentoo-user] Systemd-boot not compiling

[Mike Gilbert]

On Mon, Apr 8, 2019 at 9:14 AM Peter Humphrey  wrote:
>
> Hello list,
>
> Is anyone else having trouble emerging systemd-boot-241? This machine has a
> small rescue system as an alternative boot, and I get a mysterious error when
> I emerge the package. The end of the log shows this:
>
> [248/248] x86_64-pc-linux-gnu-gcc  -o bootctl 'bootctl@exe/
> src_boot_bootctl.c.o' -Wl,--no-undefined -Wl,--as-needed -Wl,-z,relro -Wl,-
> z,now -Wl,--gc-sections -O2 -march=haswell -pipe -Wl,-O1 -Wl,--as-needed -
> Wl,--start-group src/shared/libsystemd-shared-241.a src/libsystemd/
> libsystemd_static.a src/basic/libbasic.a /usr/lib64/libblkid.so -lrt /usr/
> lib64/libcap.so /usr/lib64/libmount.so -lrt -lm -Wl,--end-group -pthread '-
> Wl,-rpath,$ORIGIN/src/shared:$ORIGIN/src/libsystemd:$ORIGIN/src/basic' -Wl,-
> rpath-link,/var/tmp/portage/sys-boot/systemd-boot-241/work/systemd-boot-241-
> build/src/shared:/var/tmp/portage/sys-boot/systemd-boot-241/work/systemd-
> boot-241-build/src/libsystemd:/var/tmp/portage/sys-boot/systemd-boot-241/work/
> systemd-boot-241-build/src/basic
> stat: No such file or directory
>  * ERROR: sys-boot/systemd-boot-241::gentoo failed (compile phase):
>  *   (no error message)
>
> But it compiles just fine on the main system.
>
> Perhaps something is missing from the rescue system and hasn't been caught by
> the ebuild, but I can't think of what. If 'stat' had said what file or
> directory wasn't present, I'd be able to dig a bit deeper to find the problem.
>
> I see the same behaviour on another machine. Both are 64-bit, but only this
> one is ~amd64; the other one has a KEYWORD to enable systemd-boot.

The above log snippet is fairly useless. In the future, please make
sure to include the relevant log snippet, or attach/pastebin the
entire build log if in doubt.

The most important part of the log on bug 682908 was this:

Call stack:
 ebuild.sh, line 124:  Called src_compile
   environment, line 2145:  Called die
 The specific snippet of code:
  patchelf --remove-rpath bootctl || die

That tells me that the patchelf call in src_compile was failing and
gives a much better starting point than some cryptic "stat" error.

Re: [gentoo-user] Systemd-boot not compiling

[Peter Humphrey]

On Tuesday, 9 April 2019 14:34:19 BST J. Roeleveld wrote:
> On Tuesday, April 9, 2019 11:11:42 AM CEST Peter Humphrey wrote:
> > On Tuesday, 9 April 2019 06:56:02 BST J. Roeleveld wrote:
> > > if you search for "stat" in the build-log and/or makefile(s), does it
> > > show
> > > which file(s) it is checking?
> > 
> > Looking into the work directory I find this little surprise:
> > 
> > # ls -l
> > /var/tmp/portage/sys-boot/systemd-boot-241/work/systemd-boot-241-build
> > [...]
> > lrwxrwxrwx  1 portage portage   22 Apr  9 09:26 libnss_myhostname.so ->
> > libnss_myhostname.so.2 lrwxrwxrwx  1 portage portage   22 Apr  9 09:26
> > libnss_mymachines.so -> libnss_mymachines.so.2 lrwxrwxrwx  1 portage
> > portage   19 Apr  9 09:26 libnss_resolve.so -> libnss_resolve.so.2
> > lrwxrwxrwx  1 portage portage   19 Apr  9 09:26 libnss_systemd.so ->
> > libnss_systemd.so.2 lrwxrwxrwx  1 portage portage   15 Apr  9 09:26
> > libsystemd.so -> libsystemd.so.0 lrwxrwxrwx  1 portage portage   20 Apr  9
> > 09:26 libsystemd.so.0 -> libsystemd.so.0.25.0 [...]
> > 
> > Konsole shows all these in red, indicating nonexistence of the links'
> > targets, and indeed they don't exist, either there or anywhere else in the
> > system. On the other hand, after ebuild ... compile on the main system,
> > which succeeds, I get the same nonexistent links. So that can't be the
> > problem.
> > 
> > "find . -name Makefile -exec grep '-lw' 'stat' {} +" returns a blank.
> > 
> > I'm close to getting out of my depth here.
> > 
> > (This is an openrc box.)
> 
> I just tested the compile on my system and I get the exact same error.
> This is on my primary desktop, so would expect most build-dependencies to be
> present.
> 
> I also noticed the following bug on b.g.o.:
> https://bugs.gentoo.org/682908

Ah. That must have been posted after I looked.

> For your current issue, you could try version 239, which does compile on my
> system. I am not going to test installing it as that risks not being able to
> boot my desktop.

Yes, 239 is fine here too. I'll leave the boxes that can compile 241 alone for 
the time being.

Thanks for your help.

-- 
Regards,
Peter.

Re: [gentoo-user] Systemd-boot not compiling

[J. Roeleveld]

On Tuesday, April 9, 2019 11:11:42 AM CEST Peter Humphrey wrote:
> On Tuesday, 9 April 2019 06:56:02 BST J. Roeleveld wrote:
> > if you search for "stat" in the build-log and/or makefile(s), does it show
> > which file(s) it is checking?
> 
> Looking into the work directory I find this little surprise:
> 
> # ls -l
> /var/tmp/portage/sys-boot/systemd-boot-241/work/systemd-boot-241-build
> [...]
> lrwxrwxrwx  1 portage portage   22 Apr  9 09:26 libnss_myhostname.so ->
> libnss_myhostname.so.2 lrwxrwxrwx  1 portage portage   22 Apr  9 09:26
> libnss_mymachines.so -> libnss_mymachines.so.2 lrwxrwxrwx  1 portage
> portage   19 Apr  9 09:26 libnss_resolve.so -> libnss_resolve.so.2
> lrwxrwxrwx  1 portage portage   19 Apr  9 09:26 libnss_systemd.so ->
> libnss_systemd.so.2 lrwxrwxrwx  1 portage portage   15 Apr  9 09:26
> libsystemd.so -> libsystemd.so.0 lrwxrwxrwx  1 portage portage   20 Apr  9
> 09:26 libsystemd.so.0 -> libsystemd.so.0.25.0 [...]
> 
> Konsole shows all these in red, indicating nonexistence of the links'
> targets, and indeed they don't exist, either there or anywhere else in the
> system. On the other hand, after ebuild ... compile on the main system,
> which succeeds, I get the same nonexistent links. So that can't be the
> problem.
> 
> "find . -name Makefile -exec grep '-lw' 'stat' {} +" returns a blank.
> 
> I'm close to getting out of my depth here.
> 
> (This is an openrc box.)

I just tested the compile on my system and I get the exact same error.
This is on my primary desktop, so would expect most build-dependencies to be 
present.

I also noticed the following bug on b.g.o.:
https://bugs.gentoo.org/682908

For your current issue, you could try version 239, which does compile on my 
system. I am not going to test installing it as that risks not being able to 
boot my desktop.

--
Joost

Re: [gentoo-user] Systemd-boot not compiling

[Peter Humphrey]

On Tuesday, 9 April 2019 06:56:02 BST J. Roeleveld wrote:

> if you search for "stat" in the build-log and/or makefile(s), does it show
> which file(s) it is checking?

Looking into the work directory I find this little surprise:

# ls -l /var/tmp/portage/sys-boot/systemd-boot-241/work/systemd-boot-241-build
[...]
lrwxrwxrwx  1 portage portage   22 Apr  9 09:26 libnss_myhostname.so -> 
libnss_myhostname.so.2
lrwxrwxrwx  1 portage portage   22 Apr  9 09:26 libnss_mymachines.so -> 
libnss_mymachines.so.2
lrwxrwxrwx  1 portage portage   19 Apr  9 09:26 libnss_resolve.so -> 
libnss_resolve.so.2
lrwxrwxrwx  1 portage portage   19 Apr  9 09:26 libnss_systemd.so -> 
libnss_systemd.so.2
lrwxrwxrwx  1 portage portage   15 Apr  9 09:26 libsystemd.so -> libsystemd.so.0
lrwxrwxrwx  1 portage portage   20 Apr  9 09:26 libsystemd.so.0 -> 
libsystemd.so.0.25.0
[...]

Konsole shows all these in red, indicating nonexistence of the links' targets,
and indeed they don't exist, either there or anywhere else in the system. On
the other hand, after ebuild ... compile on the main system, which succeeds, I
get the same nonexistent links. So that can't be the problem.

"find . -name Makefile -exec grep '-lw' 'stat' {} +" returns a blank.

I'm close to getting out of my depth here.

(This is an openrc box.)

-- 
Regards,
Peter.

Re: [gentoo-user] Systemd-boot not compiling

[Peter Humphrey]

On Tuesday, 9 April 2019 06:56:02 BST J. Roeleveld wrote:

> if you search for "stat" in the build-log and/or makefile(s), does it show
> which file(s) it is checking?

The log has four occurrences of "stat". The first is during the initial 
checks: Program stat found: YES (/usr/bin/stat)

Line 148 appears to be x86_64-pc-linux-gnu-gcc compiling ../systemd-241/src/
basic/stat-util.c

Line 167 shows x86_64-pc-linux-gnu-ar csrD src/basic/libbasic.a with a list of 
about 80 .o files.

Then the last line, 248, is followed immediately by the error message "stat: 
No such file or directory".

I don't have the source files at the moment; I'll look into those when I can.

-- 
Regards,
Peter.

Re: [gentoo-user] Systemd-boot not compiling

[J. Roeleveld]

On Monday, April 8, 2019 4:44:58 PM CEST Peter Humphrey wrote:
> On Monday, 8 April 2019 15:29:47 BST J. Roeleveld wrote:
> > On April 8, 2019 1:14:38 PM UTC, Peter Humphrey 
> 
> wrote:
> > >Hello list,
> > >
> > >Is anyone else having trouble emerging systemd-boot-241? This machine
> > >has a small rescue system as an alternative boot, and I get a mysterious
> > >error when I emerge the package. The end of the log shows this:
> > >
> > >[248/248] x86_64-pc-linux-gnu-gcc  -o bootctl 'bootctl@exe/
> > >src_boot_bootctl.c.o' -Wl,--no-undefined -Wl,--as-needed -Wl,-z,relro
> > >-Wl,- z,now -Wl,--gc-sections -O2 -march=haswell -pipe -Wl,-O1
> > >-Wl,--as-needed -Wl,--start-group src/shared/libsystemd-shared-241.a src/
> > >libsystemd/libsystemd_static.a src/basic/libbasic.a
> > >/usr/lib64/libblkid.so
> > >-lrt/usr/lib64/libcap.so /usr/lib64/libmount.so -lrt -lm -Wl,--end-group
> > >-pthread
> > >'-Wl,-rpath,$ORIGIN/src/shared:$ORIGIN/src/libsystemd:$ORIGIN/src/
> > >basic'-Wl,-rpath-link,/var/tmp/portage/sys-boot/systemd-boot-241/work/
> > >systemd-boot-241- build/src/shared:/var/tmp/portage/sys-boot/systemd
> > >-boot-241/work/systemd-boot-241-build/src/libsystemd:/var/tmp/portage/sys
> > >-
> > >boot/systemd-boot-241/work/ systemd-boot-241-build/src/basic
> > >stat: No such file or directory
> > >
> > > * ERROR: sys-boot/systemd-boot-241::gentoo failed (compile phase):
> > > *   (no error message)
> > >
> > >But it compiles just fine on the main system.
> > >
> > >Perhaps something is missing from the rescue system and hasn't been
> > >caught by the ebuild, but I can't think of what. If 'stat' had said what
> > >file or directory wasn't present, I'd be able to dig a bit deeper to find
> > >the problem.
> > >
> > >I see the same behaviour on another machine. Both are 64-bit, but only
> > >this one is ~amd64; the other one has a KEYWORD to enable systemd-boot.
> > 
> > Have you tried compiling with "MAKEOPTS="-j 1"? (Eg, no parallel build?
> 
> I knew I'd missed something out - yes, that's the first thing I tried.

if you search for "stat" in the build-log and/or makefile(s), does it show 
which file(s) it is checking?

--
Joost

Re: [gentoo-user] Systemd-boot not compiling

[Peter Humphrey]

On Monday, 8 April 2019 15:29:47 BST J. Roeleveld wrote:
> On April 8, 2019 1:14:38 PM UTC, Peter Humphrey  
wrote:
> >Hello list,
> >
> >Is anyone else having trouble emerging systemd-boot-241? This machine
> >has a small rescue system as an alternative boot, and I get a mysterious
> >error when I emerge the package. The end of the log shows this:
> >
> >[248/248] x86_64-pc-linux-gnu-gcc  -o bootctl 'bootctl@exe/
> >src_boot_bootctl.c.o' -Wl,--no-undefined -Wl,--as-needed -Wl,-z,relro
> >-Wl,- z,now -Wl,--gc-sections -O2 -march=haswell -pipe -Wl,-O1
> >-Wl,--as-needed -Wl,--start-group src/shared/libsystemd-shared-241.a src/
> >libsystemd/libsystemd_static.a src/basic/libbasic.a /usr/lib64/libblkid.so
> >-lrt/usr/lib64/libcap.so /usr/lib64/libmount.so -lrt -lm -Wl,--end-group
> >-pthread '-Wl,-rpath,$ORIGIN/src/shared:$ORIGIN/src/libsystemd:$ORIGIN/src/
> >basic'-Wl,-rpath-link,/var/tmp/portage/sys-boot/systemd-boot-241/work/
> >systemd-boot-241- build/src/shared:/var/tmp/portage/sys-boot/systemd
> >-boot-241/work/systemd-boot-241-build/src/libsystemd:/var/tmp/portage/sys-
> >boot/systemd-boot-241/work/ systemd-boot-241-build/src/basic
> >stat: No such file or directory
> >
> > * ERROR: sys-boot/systemd-boot-241::gentoo failed (compile phase):
> > *   (no error message)
> >
> >But it compiles just fine on the main system.
> >
> >Perhaps something is missing from the rescue system and hasn't been
> >caught by the ebuild, but I can't think of what. If 'stat' had said what
> >file or directory wasn't present, I'd be able to dig a bit deeper to find
> >the problem.
> >
> >I see the same behaviour on another machine. Both are 64-bit, but only
> >this one is ~amd64; the other one has a KEYWORD to enable systemd-boot.
> 
> Have you tried compiling with "MAKEOPTS="-j 1"? (Eg, no parallel build?

I knew I'd missed something out - yes, that's the first thing I tried.

-- 
Regards,
Peter.

Re: [gentoo-user] Systemd-boot not compiling

[J. Roeleveld]

On April 8, 2019 1:14:38 PM UTC, Peter Humphrey  wrote:
>Hello list,
>
>Is anyone else having trouble emerging systemd-boot-241? This machine
>has a 
>small rescue system as an alternative boot, and I get a mysterious
>error when 
>I emerge the package. The end of the log shows this:
>
>[248/248] x86_64-pc-linux-gnu-gcc  -o bootctl 'bootctl@exe/
>src_boot_bootctl.c.o' -Wl,--no-undefined -Wl,--as-needed -Wl,-z,relro
>-Wl,-
>z,now -Wl,--gc-sections -O2 -march=haswell -pipe -Wl,-O1
>-Wl,--as-needed -
>Wl,--start-group src/shared/libsystemd-shared-241.a src/libsystemd/
>libsystemd_static.a src/basic/libbasic.a /usr/lib64/libblkid.so -lrt
>/usr/
>lib64/libcap.so /usr/lib64/libmount.so -lrt -lm -Wl,--end-group
>-pthread '-
>Wl,-rpath,$ORIGIN/src/shared:$ORIGIN/src/libsystemd:$ORIGIN/src/basic'
>-Wl,-
>rpath-link,/var/tmp/portage/sys-boot/systemd-boot-241/work/systemd-boot-241-
>build/src/shared:/var/tmp/portage/sys-boot/systemd-boot-241/work/systemd-
>boot-241-build/src/libsystemd:/var/tmp/portage/sys-boot/systemd-boot-241/work/
>systemd-boot-241-build/src/basic
>stat: No such file or directory
> * ERROR: sys-boot/systemd-boot-241::gentoo failed (compile phase):
> *   (no error message)
>
>But it compiles just fine on the main system.
>
>Perhaps something is missing from the rescue system and hasn't been
>caught by 
>the ebuild, but I can't think of what. If 'stat' had said what file or 
>directory wasn't present, I'd be able to dig a bit deeper to find the
>problem.
>
>I see the same behaviour on another machine. Both are 64-bit, but only
>this 
>one is ~amd64; the other one has a KEYWORD to enable systemd-boot.

Have you tried compiling with "MAKEOPTS="-j 1"? (Eg, no parallel build?
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] systemd-240 doesn't load my kernel modules

[Andrew Savchenko]

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] systemd/dracut: Correctly boot using flash drive with LUKS key?

[Andrew Udvare]

On 16/11/2018 14:43, Rich Freeman wrote:
> On Fri, Nov 16, 2018 at 12:15 PM Andrew Udvare  wrote:
>>
>> I am not sure if there is a way to move the systemd-cryptsetup@home.service 
>> up the dependency tree once it's working, which would then remove the 
>> mnt-chuan.mount dependency.
>>
> 
> Ok, I did a bit more reading.  You're using the cryptsetup generator
> most likely.  It sets up units to be oneshot+remainafterexit, which
> means they're "active" whenever the LUKS device is mounted (without
> any processes - but they show as active so that you can stop them and
> unmount the device).  It sets the RequiresMountsFor parameter for the
> device the key file is contained on, which makes that mount service a
> Required dependency.  That means that it can't be unmounted while the
> cryptsetup device is in use, and in theory attempting to unmount the
> key file should make systemd attempt to unmount the cryptsetup device
> (though busy filesystems could interfere with that).

So it is a bit strange that /mnt/chuan was considered a dependency just
because of mention in /etc/crypttab. However I found out that the reason
has something to do with the /mnt/chuan entry in /etc/fstab in my real
root, and this is not a necessary line (it is the only entry in the
initrd fstab). I removed the line and now the dependency is still show
with list-dependencies, but it is white instead of red. My system is
still shown as running rather than degraded.

Removing the line from /etc/fstab only partially solves the problem, as
it's not explained what happens with the USB drive once the root is
switched because after that it's not shown to be mounted. I am pretty
sure it's not safely unmounted before the switch, which leaves it in a
strange state requiring fsck. Don't know the best way around this other
than wait till systemd supports the keyscript option in /etc/crypttab.

-- 
Andrew



signature.asc
Description: OpenPGP digital signature

Re: [gentoo-user] systemd/dracut: Correctly boot using flash drive with LUKS key?

[Rich Freeman]

On Fri, Nov 16, 2018 at 12:15 PM Andrew Udvare  wrote:
>
> I am not sure if there is a way to move the systemd-cryptsetup@home.service 
> up the dependency tree once it's working, which would then remove the 
> mnt-chuan.mount dependency.
>

Ok, I did a bit more reading.  You're using the cryptsetup generator
most likely.  It sets up units to be oneshot+remainafterexit, which
means they're "active" whenever the LUKS device is mounted (without
any processes - but they show as active so that you can stop them and
unmount the device).  It sets the RequiresMountsFor parameter for the
device the key file is contained on, which makes that mount service a
Required dependency.  That means that it can't be unmounted while the
cryptsetup device is in use, and in theory attempting to unmount the
key file should make systemd attempt to unmount the cryptsetup device
(though busy filesystems could interfere with that).

I'm not sure if there is a cleaner solution for this without adding
some kind of new dependency type to systemd.  You really do want that
mountpoint to be considered "Required" when the service starts as that
file is essential, but you don't need it to stick around after the
unit starts.  Of course, you don't want it to automatically stop right
away either (that would create a race condition between unmounting the
key and reading it).

This is built-in systemd behavior.  I wouldn't be surprised if the
folks on the #systemd IRC channel would be interested in talking about
this use case and ways to improve it.  The fact that they anticipate
the key being on a removable mount makes me think it is something they
want to support, but it would clearly be more secure to not leave that
file mounted all the time.

I'd encourage you to ask about it on IRC.  If that isn't something you
want to do I might inquire about it myself, but I don't want to steal
your thunder.

--
Rich

Re: [gentoo-user] systemd/dracut: Correctly boot using flash drive with LUKS key?

[Andrew Udvare]

> On 2018-11-16, at 08:16, Rich Freeman  wrote:
> 
> On Fri, Nov 16, 2018 at 12:11 AM Andrew Udvare  wrote:
>> 
>> - use key to decrypt root partition (systemd job in the first systemd
>> launched within initramfs)
>> ...
>> Nov 16 00:01:52 limelight systemd[1]: Dependency failed for /mnt/chuan.
>> Nov 16 00:01:52 limelight systemd[1]: mnt-chuan.mount: Job
>> mnt-chuan.mount/start failed with result 'dependency'.
> 
> So, I haven't messed around that much with systemd and removable
> media, but a few things I'd start by looking at:
> 
> systemctl show mnt-chuan.mount
> systemctl list-dependencies --reverse --all mnt-chuan.mount

So this output seems to make sense, and running systemctl stop on the mount 
gave me similar messages about dependencies. I"m not sure there is a way around 
this, as the dependency tree always relies on that mount before 
systemd-cryptsetup@root can work. If unmounted it will be flagged as in invalid 
state.

I am not sure if there is a way to move the systemd-cryptsetup@home.service up 
the dependency tree once it's working, which would then remove the 
mnt-chuan.mount dependency.

Tree from the device:

dev-disk-by\x2...device
● └─mnt-chuan.mount
│ └─...
●   ├─systemd-cryptsetup@home.service
●   │ ├─dev-disk-by\x2duuid-device
│ │   └─...
●   │ ├─dev-mapper-home.device
●   │ └─cryptsetup.target
●   │   └─sysinit.target

systemd-cryptsetup@home.service is red.

-- 
Andrew Udvare

Re: [gentoo-user] systemd/dracut: Correctly boot using flash drive with LUKS key?

[Rich Freeman]

On Fri, Nov 16, 2018 at 12:11 AM Andrew Udvare  wrote:
>
> - use key to decrypt root partition (systemd job in the first systemd
> launched within initramfs)
> ...
> Nov 16 00:01:52 limelight systemd[1]: Dependency failed for /mnt/chuan.
> Nov 16 00:01:52 limelight systemd[1]: mnt-chuan.mount: Job
> mnt-chuan.mount/start failed with result 'dependency'.

So, I haven't messed around that much with systemd and removable
media, but a few things I'd start by looking at:

systemctl show mnt-chuan.mount
systemctl list-dependencies --reverse --all mnt-chuan.mount

I'd have to read up the manpages on how automounting works and what
the appropriate flags are in fstab to trigger that.  Obviously that is
someplace else to check.

Clearly you have things set up so that the usb drive is mounted before
your script goes and reads the key off of it.  If you're doing that in
a service and have a dependency on the usb drive (or system somehow
figured out that there should be a dependency on it), and that service
is left in a running state after the decryption is done, that could be
causing issues as systemd thinks that drive is still needed and is
desperately trying to get it back.

With systemd mountpoints are units, and can be started/stopped like
any service and can be dependencies of services.  This is usually a
good thing, but services tend to be persistent and removable drives
tend not to be, so you probably need to use some care when mixing the
two.  Note that due to generators system will create mount units
automatically from fstab and other sources.  Usually traditional
commands like mount/umount and so on just do the right thing, but if
you've inadvertently enabled some kind of automounting logic or
systemd believes there is a dependency with another unit then you
might be fighting the system.

Here is another route you could take.  When you want to remove that
usb drive, instead of just pulling it out or manually unmounting it,
try running:
systemctl stop mnt-chuan.mount
That is asking systemd to nicely unmount it.  If systemd doesn't want
to unmount it then it will nicely tell you take a hike, but perhaps
the error output will give you some clues as to why.

-- 
Rich

Re: [gentoo-user] "systemd sysv-utils blocker resolution"

[allan gottlieb]

On Sat, Feb 10 2018, Rich Freeman wrote:

> On Sat, Feb 10, 2018 at 10:02 PM, allan gottlieb  wrote:
>> On Sat, Feb 10 2018, Rich Freeman wrote:
>>
>>>
>>> Interesting.  Does /sbin/reboot exist?
>>
>> gottlieb@E6430 ~ $ ls -l /sbin/reboot
>> lrwxrwxrwx 1 root root 16 Jan 28 13:08 /sbin/reboot -> ../bin/systemctl
>>
>>> What does "qfile /sbin/reboot" return?
>>
>> gottlieb@E6430 ~ $ qfile /sbin/reboot
>> sys-apps/systemd (/sbin/reboot)
>
> Ok, your systemd is built with USE=sysv-utils.
>
>>> Ultimately it comes down to whether you care about the compatibility
>>> symlinks.  It probably isn't a bad idea to have them though.  Maybe
>>> some day you'll install a UPS and its shutdown scripts will just call
>>> shutdown/poweroff/etc and not work.  Software that shuts down using
>>> either systemctl or dbus would be fine.
>>
>> Since you lean toward having the symlinks, why is the new default for
>> the use flag on?  Upstream?
>
> When the flag is on the symlinks are created.  They're only missing
> (from systemd) when the flag is off.
>
>> Also why do I have the symlinks with the 236-r5 system, contracting the
>> news item.  (This is true for both machines.)
>
> You have them because the default is USE=sysv-utils, which installs
> the symlinks.
>
> The real question is why euse didn't show you has having the flag
> enabled.  That I'm not sure about.  It shows it as enabled on my
> system.  I'd have to dig into where it is getting its data and how
> this might get out of sync.
>
> To avoid a second email - a lack of depcleaning might explain why
> software like openrc/netifrc is still installed.  I don't believe it
> has anything to do with the output of euse.

Thank you (and dale) again.
allan

Re: [gentoo-user] "systemd sysv-utils blocker resolution"

[Rich Freeman]

On Sat, Feb 10, 2018 at 10:02 PM, allan gottlieb  wrote:
> On Sat, Feb 10 2018, Rich Freeman wrote:
>
>>
>> Interesting.  Does /sbin/reboot exist?
>
> gottlieb@E6430 ~ $ ls -l /sbin/reboot
> lrwxrwxrwx 1 root root 16 Jan 28 13:08 /sbin/reboot -> ../bin/systemctl
>
>> What does "qfile /sbin/reboot" return?
>
> gottlieb@E6430 ~ $ qfile /sbin/reboot
> sys-apps/systemd (/sbin/reboot)

Ok, your systemd is built with USE=sysv-utils.

>> Ultimately it comes down to whether you care about the compatibility
>> symlinks.  It probably isn't a bad idea to have them though.  Maybe
>> some day you'll install a UPS and its shutdown scripts will just call
>> shutdown/poweroff/etc and not work.  Software that shuts down using
>> either systemctl or dbus would be fine.
>
> Since you lean toward having the symlinks, why is the new default for
> the use flag on?  Upstream?

When the flag is on the symlinks are created.  They're only missing
(from systemd) when the flag is off.

> Also why do I have the symlinks with the 236-r5 system, contracting the
> news item.  (This is true for both machines.)

You have them because the default is USE=sysv-utils, which installs
the symlinks.

The real question is why euse didn't show you has having the flag
enabled.  That I'm not sure about.  It shows it as enabled on my
system.  I'd have to dig into where it is getting its data and how
this might get out of sync.

To avoid a second email - a lack of depcleaning might explain why
software like openrc/netifrc is still installed.  I don't believe it
has anything to do with the output of euse.

-- 
Rich

Re: [gentoo-user] "systemd sysv-utils blocker resolution"

[Dale]

allan gottlieb wrote:
> I have a question on this news item.
>
> I use systemd (gnome3) on a gentoo stable system.
> eix reports that sys-apps/systemd-236-r5 is installed
>
> But
>euse -I sysv-utils
> reports
>no matching entries found
>
> Is something wrong?
>
> I do *not* have
>   sys-apps/sysvinit, sys-apps/openrc, or net-misc/netifrc
> in my world file.
>
> However, the last two are installed.
>
> thanks,
> allan
>
>


I would use 'equery d openrc netifrc'to see what if anything depends on
them.  If you get packages listed, then you know why they are there, and
maybe why as well.  If it lists nothing, then --depclean should clean it
up when you get a chance to run it. 

Just my thinking.

Dale

:-)  :-) 

Re: [gentoo-user] "systemd sysv-utils blocker resolution"

[allan gottlieb]

On Sat, Feb 10 2018, Rich Freeman wrote:

> On Sat, Feb 10, 2018 at 7:16 PM, allan gottlieb  wrote:
>> I have a question on this news item.
>>
>> I use systemd (gnome3) on a gentoo stable system.
>> eix reports that sys-apps/systemd-236-r5 is installed
>>
>> But
>>euse -I sysv-utils
>> reports
>>no matching entries found
>>
>> Is something wrong?
>>
>> I do *not* have
>>   sys-apps/sysvinit, sys-apps/openrc, or net-misc/netifrc
>> in my world file.
>>
>> However, the last two are installed.
>>
>
> Interesting.  Does /sbin/reboot exist?

gottlieb@E6430 ~ $ ls -l /sbin/reboot
lrwxrwxrwx 1 root root 16 Jan 28 13:08 /sbin/reboot -> ../bin/systemctl

> What does "qfile /sbin/reboot" return?

gottlieb@E6430 ~ $ qfile /sbin/reboot
sys-apps/systemd (/sbin/reboot)

> The only thing that is changing is a default - that flag was defaulted
> off before, and is defaulted on now.  So, an emerge --changed-use -u
> world should reinstall systemd with this flag enabled, assuming you
> didn't manually disable it.

I have not dis- or en- abled the flag

> In any case, you can probably actually survive without poweroff,
> reboot, etc, assuming you shutdown using systemctl.  Obviously some
> legacy scripts/programs/etc that are supposed to shut down your system
> might balk at the missing symlinks.  All the use flag does is install
> compatibility symlinks to systemctl for these sysvinit programs and
> their manpages.

My poweroff sequence is to use the gnome icon to logoff
and then the gnome icon to poweroff

> Unless you have some package installed that explicitly depends on
> sysvinit or openrc you should be fine.  Do you actually get any
> blockers/etc?

No blockers.  I have two similar machines.  Only problems are a
long-standing difficulty with one machine compiling chromium and a known
bug in compiling webkit-gtk-2.4.11-r200 on either machine.

> Ultimately it comes down to whether you care about the compatibility
> symlinks.  It probably isn't a bad idea to have them though.  Maybe
> some day you'll install a UPS and its shutdown scripts will just call
> shutdown/poweroff/etc and not work.  Software that shuts down using
> either systemctl or dbus would be fine.

Since you lean toward having the symlinks, why is the new default for
the use flag on?  Upstream?

Also why do I have the symlinks with the 236-r5 system, contracting the
news item.  (This is true for both machines.)

Thanks again for all your help,
allan

Re: [gentoo-user] "systemd sysv-utils blocker resolution"

[Rich Freeman]

On Sat, Feb 10, 2018 at 7:16 PM, allan gottlieb  wrote:
> I have a question on this news item.
>
> I use systemd (gnome3) on a gentoo stable system.
> eix reports that sys-apps/systemd-236-r5 is installed
>
> But
>euse -I sysv-utils
> reports
>no matching entries found
>
> Is something wrong?
>
> I do *not* have
>   sys-apps/sysvinit, sys-apps/openrc, or net-misc/netifrc
> in my world file.
>
> However, the last two are installed.
>

Interesting.  Does /sbin/reboot exist?  What does "qfile /sbin/reboot" return?

The only thing that is changing is a default - that flag was defaulted
off before, and is defaulted on now.  So, an emerge --changed-use -u
world should reinstall systemd with this flag enabled, assuming you
didn't manually disable it.

In any case, you can probably actually survive without poweroff,
reboot, etc, assuming you shutdown using systemctl.  Obviously some
legacy scripts/programs/etc that are supposed to shut down your system
might balk at the missing symlinks.  All the use flag does is install
compatibility symlinks to systemctl for these sysvinit programs and
their manpages.

Unless you have some package installed that explicitly depends on
sysvinit or openrc you should be fine.  Do you actually get any
blockers/etc?

Ultimately it comes down to whether you care about the compatibility
symlinks.  It probably isn't a bad idea to have them though.  Maybe
some day you'll install a UPS and its shutdown scripts will just call
shutdown/poweroff/etc and not work.  Software that shuts down using
either systemctl or dbus would be fine.

-- 
Rich

Re: [gentoo-user] Systemd

[siefke_lis...@web.de]

On Sat, 04 Nov 2017 16:58:16 +
Neil Bothwick  wrote:

> It's pretty straightforward, just follow the wiki. The profile takes care of 
> setting the appropriate USE flags. One thing to watch out for is that systemd 
> will not pick up your openrc startup services so save the output from 
> rc-update - s then enable the services after changeover . 

That sounds good then I will do it. Thank you. 

Silvio

Re: [gentoo-user] Systemd

[Neil Bothwick]

It's pretty straightforward, just follow the wiki. The profile takes care of 
setting the appropriate USE flags. One thing to watch out for is that systemd 
will not pick up your openrc startup services so save the output from rc-update 
- s then enable the services after changeover . 

On 4 November 2017 16:15:39 GMT, "siefke_lis...@web.de"  
wrote:
>Hello, 
>
>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?
>
>Thank you for help and have nice weekend.
>
>Silvio 

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] systemd: "local system does not support BPF/cgroup based firewalling"

[Canek Peláez Valdés]

Do you have CONFIG_CGROUP_BPF enabled?

Regards.

On Sat, Oct 28, 2017 at 1:03 PM, Nikos Chantziaras  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] systemD?

[Rich Freeman]

On Wed, Aug 30, 2017 at 7:28 PM, Heiko Baums  wrote:
> Am Wed, 30 Aug 2017 23:27:12 +0100
> schrieb Mick :
>
>> 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.
>

Other than one default setting and the filenames there really is
little difference either way.  If eudev has drifted further than that
I'm curious to hear.

-- 
Rich

Re: [gentoo-user] systemD?

[Daniel Campbell]

On 08/30/2017 01: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. 
> 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.

We have a wiki page for it [1] that I'm awaiting review on for my edited
version[2], which briefly goes over the steps needed to setup Gentoo
without systemd.

In short:

eselect profile list
(choose one that doesn't have 'systemd' in its name)
eselect profile set [profile-number]

make.conf:
USE="$USE -systemd"

(sidenote: is logind a USE flag yet?)

package.mask:
sys-apps/systemd
sys-fs/udev

Remerging virtual/udev after configuring the above will pull in
sys-fs/eudev, which is a drop-in replacement for systemd-udev. Be sure
to merge your preferred init, and systemd will be removed on the next
depclean (if present and not in a set somewhere like @world).

[1]: https://wiki.gentoo.org/wiki/Gentoo_Without_systemd
[2]: https://wiki.gentoo.org/wiki/User:Zlg/Drafts/Gentoo_without_systemd

-- 
Daniel Campbell - Gentoo Developer, Trustee, Treasurer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C  1DE4 6F7A 9091 1EA0 55D6



signature.asc
Description: OpenPGP digital signature

Re: [gentoo-user] systemD?

[Heiko Baums]

Am Wed, 30 Aug 2017 23:27:12 +0100
schrieb Mick :

> 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

Re: [gentoo-user] systemD?

[Mick]

On Wednesday, 30 August 2017 22:18:40 BST Rich Freeman wrote:
> On Wed, Aug 30, 2017 at 4:39 PM,   
wrote:
> > are some of the available kernels not systemd,
> 
> Michael's answer was correct, but I just wanted to note that the
> kernel and systemd are really two different things.  You don't really
> need to do anything special with the kernel to not use systemd.
> 
> If you do use systemd (or openrc) you do need to make sure the kernel
> has the required options enabled.  The gentoo-sources package has menu
> items that automatically select these, both for openrc and systemd.
> There really isn't anything special here - lots of software requires
> certain kernel features to work.  There is generally no harm in
> turning on options you don't need.
> 
> You generally won't end up with systemd on Gentoo unless you go
> looking for it.  If something does pull it in there is usually a way
> to avoid it, and somebody around here would be able to help you with
> that until you accept your fate and line up for assimilation...

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.

PS. If you are still uncertain, this trick (I believe it must have been fixed 
in recent versions of systemd) may crash your systemd running PC  :-p

 https://www.agwa.name/blog/post/how_to_crash_systemd_in_one_tweet

-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] systemD?

[Rich Freeman]

On Wed, Aug 30, 2017 at 4:39 PM,   wrote:
> are some of the available kernels not systemd,

Michael's answer was correct, but I just wanted to note that the
kernel and systemd are really two different things.  You don't really
need to do anything special with the kernel to not use systemd.

If you do use systemd (or openrc) you do need to make sure the kernel
has the required options enabled.  The gentoo-sources package has menu
items that automatically select these, both for openrc and systemd.
There really isn't anything special here - lots of software requires
certain kernel features to work.  There is generally no harm in
turning on options you don't need.

You generally won't end up with systemd on Gentoo unless you go
looking for it.  If something does pull it in there is usually a way
to avoid it, and somebody around here would be able to help you with
that until you accept your fate and line up for assimilation...

-- 
Rich

Re: [gentoo-user] systemD?

[Dale]

mad.scientist.at.la...@tutanota.com wrote:
> 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.
>


You may want to add "-systemd" to the USE line in make.conf as early as
possible.  That way you can build packages without it from the start. 

Hope that helps.

Dale

:-)  :-) 

Re: [gentoo-user] systemD?

[mad.scientist.at.large]

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] systemD?

[Michael Orlitzky]

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 questions: hdparm unit file, OpenRC packages

[Rich Freeman]

On Mon, Apr 10, 2017 at 3:27 AM, Raffaele Belardi
 wrote:
> After 10+ years of LXDE/OpenRC I decided to give Gnome/systemd a try.
>
> 1. With OpenRC I used hdparm to put an external USB disk to sleep:
>
> $ cat /etc/conf.d/hdparm
> sdb_args="-S24"
>
> Looks like systemd does not provide a unit file for hdparm yet, right? If so
> I suppose I'll have to write my own.
> In general I suppose the same holds for everything that was under
> /etc/local.d/

As Kai pointed out there are units/generators to run the stuff under
local.d.  You could certainly create a unit for hdparm but a local.d
script is probably fine for something done once like this, especially
if there is no need to maintain any kind of state and undo it later.

>
> 2. Which OpenRC-related packages can I unmerge?
> - sys-apps/sysvinit
> - sys-apps/openrc

This stuff ends up being pulled in by the system set, but you can
eliminate it if you create a symlink from /lib/gentoo/functions.sh to
/etc/init.d/functions.sh.  Don't ask me why stuff STILL sources the
old location, other than it being so trivial that nobody cares that
much.  I've put openrc in package.provided just to avoid the needless
upgrades.  You can ditch sysvinit if you set USE=sysv-utils on systemd
(so that you still get stuff like reboot/halt/poweroff, though I'm not
sure how essential those actually are these days).

> - app-admin/sysklogd

Never used it, so obviously you can live without that.

> - cron/anacron after transition to systemd timers

You might want to also look at sys-process/systemd-cron as a bridge.
It basically generates timer units from your crontab and also runs the
stuff in /etc/cron.*.d/.  But, timer scripts also work just fine and I
do that for stuff that I want a bit more control over.

> - sys-apps/debianutils provides savelog functionality also provided by
> systemd but also installkernel so I shall not remove it

I use logrotate personally, and I still need it for stuff that doesn't
use syslog.

> - others?

That depends how far down the rabbit hole you want to go.  Systemd has
semi-replacements for stuff like ntpd, dns, etc.  They're not intended
as full replacements.  If you're serving time/dns/etc then you
probably won't want it.  If you just want something to manage it
locally on the host then these are fairly viable replacements.  There
is also networkd, which I use on systems that don't have wifi.

Systemd basically tries to provide all the essential services from a
client-only perspective.

-- 
Rich

Re: [gentoo-user] systemd - pulled IN "can not win" :-/

[massi ppp]

disable systemd via package mask;

https://github.com/dantrell/gentoo-project-gnome-without-systemd/blob/master/HACKING.md#differences-between-gnome-profiles


user flag settings

On Feb 10, 2017 6:02 AM, "Alan McKinnon"  wrote:

> On 10/02/2017 06:15, the...@sys-concept.com wrote:
> > On 02/09/2017 08:37 PM, the...@sys-concept.com wrote:
> >> 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?
> >>>
> > [snip]
> >
> > Solved. libreoffice-bin was pulling "systemd".  I was trying to save
> > time on emerge.
> >
> > --
> > Thelma
> >
>
>
> Every time you fins yourself asking these questions:
>
> > But some application managed to pull it IN.
> > How to fix this blockage?
>
> ALWAYS run emerge with -t option and the output will give the answer you
> seek.
>
> Most replies on this list will ask you do it, so just get in the habit
> of doing it yourself
>
>
> --
> Alan McKinnon
> alan.mckin...@gmail.com
>
>
>

Re: [gentoo-user] systemd - pulled IN "can not win" :-/

[Alan McKinnon]

On 10/02/2017 06:15, the...@sys-concept.com wrote:
> On 02/09/2017 08:37 PM, the...@sys-concept.com wrote:
>> 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?
>>>
> [snip]
> 
> Solved. libreoffice-bin was pulling "systemd".  I was trying to save
> time on emerge.
> 
> --
> Thelma
> 


Every time you fins yourself asking these questions:

> But some application managed to pull it IN.
> How to fix this blockage?

ALWAYS run emerge with -t option and the output will give the answer you
seek.

Most replies on this list will ask you do it, so just get in the habit
of doing it yourself


-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] systemd - pulled IN "can not win" :-/

[thelma]

On 02/09/2017 08:37 PM, the...@sys-concept.com wrote:
> 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?
>>
[snip]

Solved. libreoffice-bin was pulling "systemd".  I was trying to save
time on emerge.

--
Thelma

Re: [gentoo-user] systemd - pulled IN "can not win" :-/

[thelma]

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] Systemd good or bad?

[Dale]

Alan McKinnon wrote:
> On 08/01/2017 19:03, Dominus Mundi wrote:
>> I read in the history feeds that the universal init system (formerly
>> known as systemd) was controversial when introduced. I would like the
>> opinions of people from your time.
>> -- 
>> Securely sent with Tutanota. Claim your encrypted mailbox today!
>> https://tutanota.com
>
> No, no, no, please.
>
> Please please please for the love of all that is green and small furry
> animals, please do not ask that question.
>
> IT HAS BEEN FLAMEWARED TO DEATH. MANY TIMES. THE LAST TIME WAS ABOUT 2
> WEEKS AGO.
>
> Search the online archives and set aside about a week to read them, and
> another month to form an opinion.
>
> Short answer to the question you asked:
> It's still controversial. Some like it, some don't. There are two camps.
> There is no consensus.
>
> Just thought of something: are you trolling?
>

Based on other thread, I think it is high trolling.  :/

Dale

:-)  :-) 

Re: [gentoo-user] Systemd good or bad?

[Philip Webb]

170108 wabe wrote:
> Dominus Mundi  wrote:
>> I read in the history feeds that the universal init system (formerly
>> known as systemd) was controversial when introduced. I would like the
>> opinions of people from your time. -- Securely sent with Tutanota.
>> Claim your encrypted mailbox today! https://tutanota.com
> It seems that you are not only come from a future time but also from
> a parallel universe with a completely different timeline. ;-)

He's been to see the new movie 'Arrival' (grin).

-- 
,,
SUPPORT ___//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT`-O--O---'   purslowatchassdotutorontodotca

Re: [gentoo-user] Systemd good or bad?

[Jorge Almeida]

On Sun, Jan 8, 2017 at 8:14 PM, Gevisz  wrote:
> On Sun, 8 Jan 2017 11:47:24 -0600 Dale  wrote:
>
>> wabe wrote:
>> > Dominus Mundi  wrote:

>
> May be, it is in somebody business plan to start such threads just
> after the New Year so that to remind us about this topic and make
> PR action?
>
I have a feeling this thread was started by the author Himself. (Hint,
to the less attentive readers: "Dominus Mundi" means "Lord of the
World") ~_^

Jorge Almeida

Re: [gentoo-user] Systemd good or bad?

[Gevisz]

On Sun, 8 Jan 2017 11:47:24 -0600 Dale  wrote:

> wabe wrote:
> > Dominus Mundi  wrote:
> >  
> >> I read in the history feeds that the universal init system (formerly
> >> known as systemd) was controversial when introduced. I would like the
> >> opinions of people from your time. -- Securely sent with Tutanota.
> >> Claim your encrypted mailbox today! https://tutanota.com  
> > It seems that you are not only come from a future time but also from
> > a parallel universe with a completely different timeline. ;-)
> > --
> > Regards
> > wabe
> >  
> I wonder how long his subscription here will last?  ROFL  Now or in the
> future.  lol 
> 
> Dale
> 
I have noted that a thread about systemd regularly re-appears in
this mailing list just after the New Year.

May be, it is in somebody business plan to start such threads just
after the New Year so that to remind us about this topic and make
PR action?

Re: [gentoo-user] Systemd good or bad?

[Alan McKinnon]

On 08/01/2017 19:03, Dominus Mundi wrote:
> 
> I read in the history feeds that the universal init system (formerly
> known as systemd) was controversial when introduced. I would like the
> opinions of people from your time.
> -- 
> Securely sent with Tutanota. Claim your encrypted mailbox today!
> https://tutanota.com


No, no, no, please.

Please please please for the love of all that is green and small furry
animals, please do not ask that question.

IT HAS BEEN FLAMEWARED TO DEATH. MANY TIMES. THE LAST TIME WAS ABOUT 2
WEEKS AGO.

Search the online archives and set aside about a week to read them, and
another month to form an opinion.

Short answer to the question you asked:
It's still controversial. Some like it, some don't. There are two camps.
There is no consensus.

Just thought of something: are you trolling?

-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] Systemd good or bad?

[Dale]

wabe wrote:
> Dominus Mundi  wrote:
>
>> I read in the history feeds that the universal init system (formerly
>> known as systemd) was controversial when introduced. I would like the
>> opinions of people from your time. -- Securely sent with Tutanota.
>> Claim your encrypted mailbox today! https://tutanota.com
> It seems that you are not only come from a future time but also from
> a parallel universe with a completely different timeline. ;-)
>
> --
> Regards
> wabe
>
>

I wonder how long his subscription here will last?  ROFL  Now or in the
future.  lol 

Dale

:-)  :-) 

Re: [gentoo-user] Systemd good or bad?

[wabe]

Dominus Mundi  wrote:

> I read in the history feeds that the universal init system (formerly
> known as systemd) was controversial when introduced. I would like the
> opinions of people from your time. -- Securely sent with Tutanota.
> Claim your encrypted mailbox today! https://tutanota.com

It seems that you are not only come from a future time but also from
a parallel universe with a completely different timeline. ;-)

--
Regards
wabe

Re: [gentoo-user] Systemd to manage (DNS) security?

[Tom H]

On Mon, Jun 6, 2016 at 8:19 PM, Rich Freeman  wrote:
> On Mon, Jun 6, 2016 at 12:29 PM, James  wrote:
>>
>> https://lists.dns-oarc.net/pipermail/dns-operations/2016-June/014964.html
>
> That's pretty old news. In any case, you certainly don't need to use
> systemd as your DNS resolver if you don't want to.
>
> Systemd also doesn't touch /etc/resolv.conf contrary to what that
> email states. It only touches /run/systemd/resolve/resolv.conf which
> does absolutely nothing on its own unless you choose to symlink
> /etc/resolv.conf to it. The obvious options using systemd and
> resolv.conf are:
>
> 1. Don't use it at all - just put whatever you want in
> /etc/resolv.conf and it works like you'd expect it to.
>
> 2. Have systemd-networkd populate /run/systemd/resolve/resolv.conf
> with whatever DNS servers were discovered using DHCP and then symlink
> that to /etc/resolv.conf so that your system uses it. This is
> basically the behavior you typically expect from the likes of dhcpcd
> and such but instead of tampering with a file in /etc it just messes
> with a transient file in /run.

It's resolved that populates "/run/systemd/resolve/resolv.conf".

In the past, if you used "DNS=..." in a .network unit, networkd would
populate "/etc/resolv.conf".

>From an old man page of systemd.network:

DNS=
   A DNS server address, which must be in the format described in
   inet_pton(3). This option may be specified more than once.

>From a new man page of systemd.network:

DNS=
   A DNS server address, which must be in the format described in
   inet_pton(3). This option may be specified more than once. This
   setting is read by systemd-resolved.service(8).


> 3. Run systemd-resolved as a caching forwarding-only DNS server and
> have that end up in /run/systemd/resolve/resolv.conf.

IIUC, resolved'll be a dns server if you have nss-resolve installed
(which, looking at the systemd ebuild, seems to be included by default
because there isn't a use flag for it and there's no script removing
it) and if you change "hosts: files dns" to "hosts: files resolve" in
"/etc/nsswitch.conf". Otherwise, resolved is basically an openresolv
replacement.

Re: [gentoo-user] Systemd to manage (DNS) security?

[Rich Freeman]

On Mon, Jun 6, 2016 at 12:29 PM, James  wrote:
>
> This is about the most scary idea I have every heard of in unix/linux,
> in long time.
>
> I guess all of those conspiracy theories were correct::
> prepare to be assimilateD!
>
>
> https://lists.dns-oarc.net/pipermail/dns-operations/2016-June/014964.html
>

That's pretty old news.  In any case, you certainly don't need to use
systemd as your DNS resolver if you don't want to.

Systemd also doesn't touch /etc/resolv.conf contrary to what that
email states.  It only touches /run/systemd/resolve/resolv.conf which
does absolutely nothing on its own unless you choose to symlink
/etc/resolv.conf to it.  The obvious options using systemd and
resolv.conf are:
1.  Don't use it at all - just put whatever you want in
/etc/resolv.conf and it works like you'd expect it to.
2.  Have systemd-networkd populate /run/systemd/resolve/resolv.conf
with whatever DNS servers were discovered using DHCP and then symlink
that to /etc/resolv.conf so that your system uses it.  This is
basically the behavior you typically expect from the likes of dhcpcd
and such but instead of tampering with a file in /etc it just messes
with a transient file in /run.
3.  Run systemd-resolved as a caching forwarding-only DNS server and
have that end up in /run/systemd/resolve/resolv.conf.  I haven't
really taken a serious look at the security implications of this.  It
is intended as a lightweight forwarding-only DNS server, and if it has
any security flaws I'm sure they'll accept them as bugs.  It is meant
as a single-host solution - not as something you'd point your entire
network at.  It certainly isn't BIND.

As with most systemd integrated solutions they tend to start out
simple and evolve.

The last time I checked systemd does not block you from installing the
DNS server of your choosing, just as it doesn't block installing
syslog, or cron, or a network manager, or even another service
manager.  You could use it as an oversized sysvinit if you wanted to
(not that you would).  How distros choose to use it is another matter.

-- 
Rich

Re: [gentoo-user] Systemd to manage (DNS) security?

[Andrew Savchenko]

Hi,

On Mon, 6 Jun 2016 16:29:13 + (UTC) James wrote:
> This is about the most scary idea I have every heard of in unix/linux,
> in long time.
> 
> I guess all of those conspiracy theories were correct:: 
> prepare to be assimilateD!
> 
> 
> https://lists.dns-oarc.net/pipermail/dns-operations/2016-June/014964.html

I'm glad that both openrc and eudev exist, so that I can safely
burn that horrible abomination with fire and purge it from all my
systems, which is done long time ago and I'm happy.

My gratitude for openrc and eudev devs for their hard work.

It should be noted, that there are other non-systemd solutions like
runit, mdev and so on. I wish them good luck too (and looks like I
even use mdev on one server :)).

Best regards,
Andrew Savchenko


pgplkFLji8ExF.pgp
Description: PGP signature

Re: [gentoo-user] systemd, libgudev and bug 552036

[Adam Carter]

Still blocked - anything else i should try?

tnx.


# emerge -a1 =sys-apps/systemd-226-r2 dev-libs/libgudev virtual/libgudev

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N ] dev-libs/libgudev-230  USE="introspection -debug
(-static-libs)" ABI_X86="(64) -32 (-x32)"
[ebuild U  ] virtual/libgudev-230 [215-r3]
[ebuild U  ] sys-apps/systemd-226-r2 [218-r5] USE="kdbus* -gnuefi%
-importd% -nat%"
[blocks B  ] sys-apps/systemd[gudev(-)] ("sys-apps/systemd[gudev(-)]"
is blocking dev-libs/libgudev-230)

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

sys-apps/systemd:0

  (sys-apps/systemd-226-r2:0/2::gentoo, ebuild scheduled for merge) pulled
in by
=sys-apps/systemd-226-r2 (Argument)

  (sys-apps/systemd-218-r5:0/2::gentoo, installed) pulled in by

sys-apps/systemd[python(-),python_targets_python2_7(-)?,python_single_target_python2_7(+)?,python_targets_python3_3(-)?,python_single_target_python3_3(+)?,python_targets_python3_4(-)?,python_single_target_python3_4(+)?]
required by (net-analyzer/fail2ban-0.9.2:0/0::gentoo, installed)




It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously.  If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.


 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (dev-libs/libgudev-230:0/0::gentoo, ebuild scheduled for merge) pulled in
by

dev-libs/libgudev: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(-)?,introspection?,static-libs?]
(dev-libs/libgudev:0/0[abi_x86_64(-),introspection]) required by
(virtual/libgudev-230:0/0::gentoo, ebuild scheduled for merge)
dev-libs/libgudev


On Fri, Dec 18, 2015 at 2:35 PM, Mike Gilbert  wrote:

> On Dec 17, 2015 9:37 PM, "Adam Carter"  wrote:
> >
> > The gudev USE flag is deprecated from systemd, and the functionality is
> now provided by libgudev (see bug 552036). However, i get the following
> block;
> >
> > # emerge -a1 =sys-apps/systemd-226-r2 dev-libs/libgudev
> >
> > These are the packages that would be merged, in order:
> >
> > Calculating dependencies... done!
> > [ebuild  N ] dev-libs/libgudev-230  USE="introspection -debug
> (-static-libs)" ABI_X86="(64) -32 (-x32)"
> > [ebuild U  ] sys-apps/systemd-226-r2 [218-r5] USE="kdbus* -gnuefi%
> -importd% -nat%"
> > [blocks B  ] sys-apps/systemd[gudev(-)]
> ("sys-apps/systemd[gudev(-)]" is blocking dev-libs/libgudev-230)
> >
> > So i plan to emerge libgudev with nodeps (to avoid the blocker), then
> upgrade systemd which will of course build without the gudev flag and I
> think I should be ok. Do I understand correctly?
>
> Add virtual/libgudev to your emerge line and it should auto-resolve the
> blocker.
>

Re: [gentoo-user] systemd, libgudev and bug 552036

[Neil Bothwick]

On Fri, 18 Dec 2015 21:00:02 +1100, Adam Carter wrote:

> Still blocked - anything else i should try?
> 
> tnx.
> 
> 
> # emerge -a1 =sys-apps/systemd-226-r2 dev-libs/libgudev virtual/libgudev

Why are you including libgudev in the merge list? If it's a dependency
of systemd, let portage take care of it.
 
> These are the packages that would be merged, in order:
> 
> Calculating dependencies... done!
> [ebuild  N ] dev-libs/libgudev-230  USE="introspection -debug
> (-static-libs)" ABI_X86="(64) -32 (-x32)"
> [ebuild U  ] virtual/libgudev-230 [215-r3]
> [ebuild U  ] sys-apps/systemd-226-r2 [218-r5] USE="kdbus* -gnuefi%
> -importd% -nat%"
> [blocks B  ] sys-apps/systemd[gudev(-)]
> ("sys-apps/systemd[gudev(-)]" is blocking dev-libs/libgudev-230)

Try "emerge -1avt systemd" for more information about what portage really
wants.


-- 
Neil Bothwick

Top Oxymorons Number 26: Software documentation


pgpSQWiHZmwEY.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] systemd, libgudev and bug 552036

[Mike Gilbert]

On Fri, Dec 18, 2015 at 5:00 AM, Adam Carter  wrote:
> Still blocked - anything else i should try?

Perhaps your ABI_X86 flags are mismatched.

You keep truncating/editing the emerge output, so we have to make
guesses. Stop doing that please.

Re: [gentoo-user] systemd, libgudev and bug 552036

[Adam Carter]

>
> On Fri, Dec 18, 2015 at 5:00 AM, Adam Carter 
> wrote:
> > Still blocked - anything else i should try?
>
> Perhaps your ABI_X86 flags are mismatched.
>
> You keep truncating/editing the emerge output, so we have to make
> guesses. Stop doing that please.
>
> Sorry - here's the full output;

# emerge -a1 =sys-apps/systemd-226-r2 dev-libs/libgudev virtual/libgudev

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N ] dev-libs/libgudev-230  USE="introspection -debug
(-static-libs)" ABI_X86="(64) -32 (-x32)"
[ebuild U  ] virtual/libgudev-230 [215-r3]
[ebuild U  ] sys-apps/systemd-226-r2 [218-r5] USE="kdbus* -gnuefi%
-importd% -nat%"
[blocks B  ] sys-apps/systemd[gudev(-)] ("sys-apps/systemd[gudev(-)]"
is blocking dev-libs/libgudev-230)

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

sys-apps/systemd:0

  (sys-apps/systemd-226-r2:0/2::gentoo, ebuild scheduled for merge) pulled
in by
=sys-apps/systemd-226-r2 (Argument)

  (sys-apps/systemd-218-r5:0/2::gentoo, installed) pulled in by

sys-apps/systemd[python(-),python_targets_python2_7(-)?,python_single_target_python2_7(+)?,python_targets_python3_3(-)?,python_single_target_python3_3(+)?,python_targets_python3_4(-)?,python_single_target_python3_4(+)?]
required by (net-analyzer/fail2ban-0.9.2:0/0::gentoo, installed)




It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously.  If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.


 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (dev-libs/libgudev-230:0/0::gentoo, ebuild scheduled for merge) pulled in
by

dev-libs/libgudev: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(-)?,introspection?,static-libs?]
(dev-libs/libgudev:0/0[abi_x86_64(-),introspection]) required by
(virtual/libgudev-230:0/0::gentoo, ebuild scheduled for merge)
dev-libs/libgudev

Re: [gentoo-user] systemd, libgudev and bug 552036

[Adam Carter]

 emerge -1avt systemd

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!
[ebuild   R] sys-apps/systemd-218-r5:0/2::gentoo  USE="acl gudev
introspection kmod lz4 pam policykit python seccomp ssl (-apparmor) -audit
-cryptsetup -curl -doc -elfutils -gcrypt -http -idn -kdbus -lzma -qrcode
(-selinux) -sysv-utils -terminal {-test} -vanilla -xkb" ABI_X86="(64) -32
(-x32)" PYTHON_SINGLE_TARGET="python2_7 -python3_3 -python3_4"
PYTHON_TARGETS="python2_7 python3_4 -python3_3" 0 KiB

Total: 1 package (1 reinstall), Size of downloads: 0 KiB

WARNING: One or more updates/rebuilds have been skipped due to a dependency
conflict:

sys-apps/systemd:0

  (sys-apps/systemd-226-r2:0/2::gentoo, ebuild scheduled for merge)
conflicts with
>=sys-apps/systemd-212-r5:0/2[abi_x86_64(-),gudev(-),introspection(-)]
required by (virtual/libgudev-215-r3:0/0::gentoo, installed)


sys-apps/systemd[python(-),python_targets_python2_7(-),python_single_target_python2_7(+),python_targets_python3_4(-)]
required by (net-analyzer/fail2ban-0.9.2:0/0::gentoo, installed)




Would you like to merge these packages? [Yes/No]

Re: [gentoo-user] systemd, libgudev and bug 552036

[Mike Gilbert]

On Dec 17, 2015 9:37 PM, "Adam Carter"  wrote:
>
> The gudev USE flag is deprecated from systemd, and the functionality is
now provided by libgudev (see bug 552036). However, i get the following
block;
>
> # emerge -a1 =sys-apps/systemd-226-r2 dev-libs/libgudev
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild  N ] dev-libs/libgudev-230  USE="introspection -debug
(-static-libs)" ABI_X86="(64) -32 (-x32)"
> [ebuild U  ] sys-apps/systemd-226-r2 [218-r5] USE="kdbus* -gnuefi%
-importd% -nat%"
> [blocks B  ] sys-apps/systemd[gudev(-)] ("sys-apps/systemd[gudev(-)]"
is blocking dev-libs/libgudev-230)
>
> So i plan to emerge libgudev with nodeps (to avoid the blocker), then
upgrade systemd which will of course build without the gudev flag and I
think I should be ok. Do I understand correctly?

Add virtual/libgudev to your emerge line and it should auto-resolve the
blocker.

Re: [gentoo-user] systemd-logind problem

[Alec Ten Harmsel]

On 2015-11-24 13:17, cov...@ccs.covici.com wrote:

I am running systemd-226-r1


There's your problem ;)

I'm really kidding.


and am having some strange problems with
systemd-logind.  It gets into some state where it can take 20 seconds to
login to the box via ssh, if I restart systemd-logind or rather stop and
start -- restart has no effect -- then it works for some unknownperiod,
but then it dies again.  Any way to fix more permanently -- I saw some
discussion a while back, but I never saw a resolution.

Thanks in advance for any ideas.



I did not know sshd used systemd-logind; have run any of these commands?:

journalctl -u systemd-logind
systemctl status systemd-logind

I am not terribly familiar with systemd, but that's the first place I 
would start. You could also try changing the LogLevel parameter in 
'/etc/systemd/system.conf'.


Alec

Re: [gentoo-user] systemd-logind problem

[covici]

Alec Ten Harmsel  wrote:

> 
> On 2015-11-24 13:17, cov...@ccs.covici.com wrote:
> > I am running systemd-226-r1
> 
> There's your problem ;)
> 
> I'm really kidding.
> 
> > and am having some strange problems with
> > systemd-logind.  It gets into some state where it can take 20 seconds to
> > login to the box via ssh, if I restart systemd-logind or rather stop and
> > start -- restart has no effect -- then it works for some unknownperiod,
> > but then it dies again.  Any way to fix more permanently -- I saw some
> > discussion a while back, but I never saw a resolution.
> >
> > Thanks in advance for any ideas.
> >
> 
> I did not know sshd used systemd-logind; have run any of these commands?:
> 
> journalctl -u systemd-logind
> systemctl status systemd-logind
> 
> I am not terribly familiar with systemd, but that's the first place I
> would start. You could also try changing the LogLevel parameter in
> '/etc/systemd/system.conf'.


I did run systemctl status systemd-logind and it was starting over and
over again and it did not work, so I stopped and restarrted manually and
its now working for a while.

-- 
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] systemd & libgudev block

[Neil Bothwick]

On Fri, 23 Oct 2015 20:00:51 -0200 (BRST), ferreir...@usp.br wrote:

> mephisto / # emerge -vpuDN world | grep blocks 
> [blocks b ] sys-apps/systemd[gudev(-)] ("sys-apps/systemd[gudev(-)]" is
> blocking dev-libs/libgudev-230) [blocks b ] dev-libs/libgudev
> ("dev-libs/libgudev" is blocking sys-apps/systemd-219_p112) 

These are blocks with a small b, portage will take care of them for you.
You only need to intervene when they are marked with a capital B.

-- 
Neil Bothwick

Why is the word abbreviation so long?


pgpRwsCzoWptq.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] systemd very slow to compile?

[Neil Bothwick]

On Sun, 13 Sep 2015 13:16:29 +0200, Marc Joliet wrote:

> On Friday 11 September 2015 15:08:54 walt wrote:
> >My very old and slow ~amd64 machine took 3 hours and 45-minutes to
> >compile systemd-226 today.  
> 
> Just out of curiosity: exactly how old?  My dual-core amd64 system is
> almost 9 years old now, and systemd compiles in about 6 minutes:
> 
> # genlop -t systemd
>  * sys-apps/systemd
>  Mon Sep  7 23:57:50 2015 >>> sys-apps/systemd-218-r3
>merge time: 12 minutes and 30 seconds.
> 
> (My system might have been pretty busy on that last one, and the second
> one must have been a binpkg merge.)

> Perhaps it is a problem only in the build system of newer systemd
> versions?

It appears to have only occurred with systemd-226, which is why you are
not seeing it. I won't post my emerge times because portage was
building Chromium at the same time, but even so they were hours in 
excess of previous builds.


-- 
Neil Bothwick

"There's more to life than sex, beer and computers.
Not a lot more admittedly..."


pgp7KqN1aXes9.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] systemd very slow to compile?

[Peter Humphrey]

On Sunday 13 September 2015 13:16:29 Marc Joliet wrote:

> I couldn't get KMail -- which I am still getting used to -- to stop it's
> automatic line wrapping just for those lines, if it even supports that

You can switch it on or off, but it applies to the whole message. What I do if 
I want a line not wrapped is to go through the rest of the message and insert 
a line break in place of each line-end space, then switch wrapping off. 
Laborious if it's a long message, but it does at least work.

Welcome to the Brave New World of a mostly good MUA. :)

-- 
Rgds
Peter