From: Patrick Ohly <patrick.ohly@intel.com>
To: OpenEmbedded <openembedded-core@lists.openembedded.org>
Subject: udev + 60-persistent-storage.rules + IDE
Date: Wed, 16 Sep 2015 14:11:41 +0200 [thread overview]
Message-ID: <1442405501.27156.9.camel@intel.com> (raw)
Hello!
I just noticed that udev (no longer) creates /dev/disk/by-uuid links for
my boot partition under qemu when booting a whole-disk image
(hdddirect). The device is then /dev/hda, with /dev/hda2 being the root
partition.
systemd's 60-persistent-storage.rules indeed skips the relevant rules
because "hd" is not listed:
KERNEL!="loop*|mmcblk*[0-9]|msblk*[0-9]|mspblk*[0-9]|nvme*|sd*|sr*|vd*|xvd*|bcache*|cciss*|dasd*|ubd*", GOTO="persistent_storage_end"
Adding "hd*" to that line fixes the problem. I'll send patches to
systemd and for OE-core.
I'm a bit puzzled a) that plain-old IDE block devices have never been
matched by 60-persistent-storage.rules (I checked the history) and b)
that this suddenly broke. I'm fairly sure that I had tested that (but I
cannot 100% guarantee that anymore).
Did indeed something change recently that led to /dev/hda?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next reply other threads:[~2015-09-16 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 12:11 Patrick Ohly [this message]
2015-09-17 6:44 ` udev + 60-persistent-storage.rules + IDE Patrick Ohly
2015-09-17 6:49 ` [PATCH] systemd: apply persistent storage udev rules also for /dev/hd* Patrick Ohly
2015-09-17 12:24 ` udev + 60-persistent-storage.rules + IDE Bruce Ashfield
2015-09-21 14:30 ` [PATCH v2] systemd: apply persistent storage udev rules also for /dev/hd* Patrick Ohly
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=1442405501.27156.9.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox