All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15847] Systemd: Incorrect Permission on /usr/lib/systemd
Date: Fri, 10 Nov 2023 19:52:29 +0000	[thread overview]
Message-ID: <bug-15847-163-Q6FBqneYJo@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15847-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=15847

--- Comment #1 from Arnout Vandecappelle <arnout@mind.be> ---
I've taken qemu_x86_64_defconfig with BR2_INIT_SYSTEMD and _NETWORKD, and I
don't see the same issue:

# ls -ald /usr/lib/systemd/
drwxr-xr-x   13 root     root          2048 Nov 10 19:43 /usr/lib/systemd/
# ls -al /usr/lib/systemd/systemd-networkd
-rwxr-xr-x    1 root     root       1579456 Nov 10 19:43
/usr/lib/systemd/systemd-networkd
# ps -ef | grep network
   84 systemd- /usr/lib/systemd/systemd-networkd
  119 root     grep network
# systemctl status systemd-networkd
● systemd-networkd.service - Network Configuration
     Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled;
preset: enabled)
     Active: active (running) since Fri 2023-11-10 19:48:48 UTC; 2min 8s ago
TriggeredBy: ● systemd-networkd.socket
       Docs: man:systemd-networkd.service(8)
             man:org.freedesktop.network1(5)
   Main PID: 84 (systemd-network)
     Status: "Processing requests..."
   FD Store: 0 (limit: 512)
        CPU: 220ms
     CGroup: /system.slice/systemd-networkd.service
             └─84 /usr/lib/systemd/systemd-networkd

Nov 10 19:48:47 buildroot systemd[1]: Starting Network Configuration...
Nov 10 19:48:47 buildroot systemd-networkd[84]: lo: Link UP
Nov 10 19:48:47 buildroot systemd-networkd[84]: lo: Gained carrier
Nov 10 19:48:48 buildroot systemd-networkd[84]: Enumeration completed
Nov 10 19:48:48 buildroot systemd[1]: Started Network Configuration.
Nov 10 19:48:49 buildroot systemd-networkd[84]: eth0: Interface name change
detected, renamed to enp0s3.

(I didn't bother changing the kernel config and I didn't add anything in
/etc/systemd/network, so the network isn't actually coming up, but
systemd-networkd is running.)

It seems that something went wrong in your build and /usr/lib/systemd was
created with the wrong permissions?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-11-10 19:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09 11:07 [Buildroot] [Bug 15847] New: Systemd: Incorrect Permission on /usr/lib/systemd bugzilla
2023-11-10 19:52 ` bugzilla [this message]
2023-11-22  8:58 ` [Buildroot] [Bug 15847] " bugzilla
2024-06-15 15:13 ` bugzilla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-15847-163-Q6FBqneYJo@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.