<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Yeah I guess if you assume the system
is installed on one partition. EFI would have to be separate
though.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I really just need to know the whole
block device though, not just the boot partition, but the boot
disk, so that is what I plan on tagging.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 1/13/20 9:26 AM, Mantas Mikulėnas
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAPWNY8VEL-hT3-9KLPfndxoPb8VdCZhJPOJZmbNxUxGTzfzpbg@mail.gmail.com">
<div dir="ltr">
<div dir="ltr">On Mon, Jan 13, 2020 at 4:12 PM Boyce, Kevin P.
(AS) <<a href="mailto:kevin.boyce@ngc.com"
moz-do-not-send="true">kevin.boyce@ngc.com</a>> wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote">Thank you Lennart.<br>
<br>
I'm thinking I will create my own sort of "built-in" command
that can <br>
parse /proc/cmdline to look for the root= variable early in
udev rules <br>
so I can create the tag.<br>
</blockquote>
<div><br>
</div>
<div>Well, that's a bit different from what is generally
called the "boot" partition...</div>
</div>
<div><br>
</div>
-- <br>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">Mantas Mikulėnas</div>
</div>
</div>
</blockquote>
<p><br>
</p>
</body>
</html>