From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11811] lsblk (util-linux) should depend on libudev if available
Date: Sun, 05 May 2019 02:21:52 +0000 [thread overview]
Message-ID: <bug-11811-163-YZLC9XwE91@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11811-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11811
--- Comment #8 from Pete Morici <pmorici@dev295.com> ---
I've attached my config it is a modified version of the included pc/efi def
config.
Looking at your output though I think you have reproduced the problem. The
serial column for your sda device is blank. You can also get the serial by
running the utility "/lib/udev/ata_id /dev/sda" If that returns something
where lsblk returns a blank then that is the problem. I've not tested this
with MMC or SD devices so it might be limited to SATA and USB drives.
Another way to see the difference is to do a full build followed by a "make
util-linux-dirclean" and then "make" again that will cause lsblk to link
against libudev and report the serial number correctly.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-05-05 2:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 3:02 [Buildroot] [Bug 11811] New: lsblk (util-linux) should depend on libudev if available bugzilla at busybox.net
2019-04-30 7:00 ` [Buildroot] [Bug 11811] " bugzilla at busybox.net
2019-04-30 12:34 ` bugzilla at busybox.net
2019-04-30 12:56 ` bugzilla at busybox.net
2019-05-03 12:10 ` bugzilla at busybox.net
2019-05-03 12:19 ` bugzilla at busybox.net
2019-05-05 0:15 ` bugzilla at busybox.net
2019-05-05 2:15 ` bugzilla at busybox.net
2019-05-05 2:17 ` bugzilla at busybox.net
2019-05-05 2:21 ` bugzilla at busybox.net [this message]
2019-05-07 16:57 ` bugzilla at busybox.net
2019-05-09 17:19 ` bugzilla at busybox.net
2020-05-29 21:04 ` bugzilla at busybox.net
2020-11-04 21:57 ` bugzilla at busybox.net
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-11811-163-YZLC9XwE91@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox