From: Alexey Gladkov <legion@kernel.org>
To: make-initrd@lists.altlinux.org
Subject: Re: [make-initrd] Ошибка от udev при загрузке
Date: Mon, 9 Nov 2026 18:17:47 +0100
Message-ID: <avIAO0ESI4XfD-D1@example.org> (raw)
In-Reply-To: <1d835080-9188-4036-9841-843b64476e6e@altlinux.org>
On Mon, Nov 09, 2026 at 07:49:42PM +0300, Anton Midyukov wrote:
> При загрузке с новым udev 262 возникает ошибка на экране (чем портит всю эстетику тихой загрузки):
>
> Failed to connect to udev via varlink: No such file or directory
>
> Её можно скрыть, например, таким патчем:
>
> diff --git a/external/libshell/upstream b/external/libshell/upstream
> index 07dd60f9..30c7619d 160000
> --- a/external/libshell/upstream
> +++ b/external/libshell/upstream
> @@ -1 +1 @@
> -Subproject commit 07dd60f948b53b2e18b3293e1674aeed62b0c3ab
> +Subproject commit 30c7619df52ece02df0a7d34ea2cb51333da9ad7
> diff --git a/features/runtime/data/etc/rc.d/init.d/udev b/features/runtime/data/etc/rc.d/init.>
> index 67427de1..4e55b7d3 100755
> --- a/features/runtime/data/etc/rc.d/init.d/udev
> +++ b/features/runtime/data/etc/rc.d/init.d/udev
> @@ -47,7 +47,7 @@ start() {
> udevadm control --log-priority=info 2>/dev/null
> [ -z "${DEBUG-}" ] || udevadm control --log-priority=debug 2>/dev/null
>
> - udevadm control --property=STARTUP=1
> + udevadm control --property=STARTUP=1 2>&1
> udevadm control --reload >/dev/null 2>&1 ||:
>
> udevadm trigger --type=subsystems --action=add >/dev/null 2>&1
>
> Но может есть идея получше?
Практически все udevadm выполняются с `>/dev/null 2>&1`. Можно всех
завернуть таким же образом. Или же перенаправить в
/var/log/udevadm_init.log на случай проблем. Но кажется ничего полезного в
этом логе не будет.
--
Rgrds, legion
next prev parent reply other threads:[~2026-11-09 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 16:49 Anton Midyukov
2026-11-09 17:17 ` Alexey Gladkov [this message]
2026-11-09 17:24 ` Anton Midyukov
2026-11-10 9:30 ` Alexey Gladkov
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=avIAO0ESI4XfD-D1@example.org \
--to=legion@kernel.org \
--cc=make-initrd@lists.altlinux.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
Make-initrd development discussion
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/make-initrd/0 make-initrd/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 make-initrd make-initrd/ http://lore.altlinux.org/make-initrd \
make-initrd@lists.altlinux.org make-initrd@lists.altlinux.ru make-initrd@lists.altlinux.com
public-inbox-index make-initrd
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.make-initrd
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git