Low prio feature request: qubes-dom0-update could check whether /boot is mounted

30 views
Skip to first unread message

David Hobach

unread,
Jul 27, 2014, 2:43:37 PM7/27/14
to qubes...@googlegroups.com
Dear developers,

it might make sense to check before updates to /boot whether it is
actually mounted by checking whether there are any files in /boot.

I just noticed that qubes-dom0-update wrote to /boot without it being
mounted (i.e. it wrote to a previously empty folder on /). I usually
don't mount /boot in fstab, because it tends to make the boot process
faster by a couple of seconds (& grub doesn't really seem to need it as
it is more low-level).

Just a low prio suggestion.

Kind Regards
David

Zrubecz Laszlo

unread,
Jul 27, 2014, 4:21:18 PM7/27/14
to David Hobach, qubes...@googlegroups.com
On 27 July 2014 12:08, David Hobach <tri...@nurfuerspam.de> wrote:

> it might make sense to check before updates to /boot whether it is actually
> mounted by checking whether there are any files in /boot.
>
> I just noticed that qubes-dom0-update wrote to /boot without it being
> mounted (i.e. it wrote to a previously empty folder on /). I usually don't
> mount /boot in fstab,

And how should the update script decide if you deleted/lost/or just
not mounted your boot partition???


If You made such customizations, You should take care of it later as well...


IMHO.

--
Zrubi

Andrew B

unread,
Jul 27, 2014, 4:32:17 PM7/27/14
to qubes...@googlegroups.com
Using AEM (an 'official' feature and not a customization) also leaves you, on ITL's recommendation, with no mounted /boot. An easily bypass-able reminder to mount /boot before continuing when yum is about to touch files in an unmounted /boot would be a helpful reminder. Unfortunately, the qubes-dom0-update script really has no idea what packages are being upgraded (let alone if any of those packages' scripts touch /boot), and maintaining a fork of yum to add this functionality would probably not be worth the effort. If anyone knows of a better solution, though, I'm all for it.

Andrew
0xB364F63E.asc
signature.asc

Marek Marczykowski-Górecki

unread,
Jul 27, 2014, 4:57:18 PM7/27/14
to David Hobach, qubes...@googlegroups.com
Registered here:
https://wiki.qubes-os.org/ticket/885

--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

signature.asc

David Hobach

unread,
Jul 28, 2014, 1:52:43 PM7/28/14
to Andrew B, qubes...@googlegroups.com
That was my thought as well.
One can even try to avoid the reminder, if there's a /boot in fstab with
noauto by trying to mount /boot & checking whether that works.

Otherwise I only see the option to ask the yum developers about
providing a related option.

@Marek: Thanks for tracking this.

cprise

unread,
Jul 28, 2014, 2:16:36 PM7/28/14
to David Hobach, Andrew B, qubes...@googlegroups.com
Yeah, failing to mount AEM stick once before an update meant I had to
manually update some files on the stick. A warning that appears if AEM
is installed would be quite helpful.
Reply all
Reply to author
Forward
0 new messages