At Fri, 26 Jun 2015 11:58:07 -0400 CentOS mailing list <centos@xxxxxxxxxx> wrote:
>
> On Thu, Jun 25, 2015 at 01:27:47PM -0600, Chris Murphy wrote:
> > It's bad design. First, it's a nested mount: file system A on /, and
> > file system B on /boot, and file system C on /boot/efi. Therefore the
> > mount process must make sure they're mounted in that order, or there's
> > failure.
>
> I've never once had a problem with nested mounts. Is this a problem
> people have? First I've heard of it.
'mount -av' has *long* supported nested mounts. Nested mounts are a 'trick'
from the days of UNIX from way back when. Mount knows all about going through
/etc/fatab and coming up with a sane and correct order for mounting file
systems.
>
> > Second, there is no good reason for the EFI System partition
> > to ever be mounted; and multiple reasons to not ever mount it (Windows
> > and OS X never mount the EFI System partition but somehow all the
> > Linux distros are obsessed with mounting things that don't need
> > mounting). Eventually systemd will become smarter and handle on-demand
> > dynamic mount and umount, including the ESP so this will get better
> > but even better would be not ever mounting it in the first place.
>
> It would be nice if that were the case, however, in an automated
> dual-boot system with EFI, we have to manage rEFInd *somewhere*, and
> it is easier for us to manage it under configuration management in
> Linux than in Windows. Our managed dual-boot workstations need to be
> able to reboot into the other OS during the evening for updates.
>
--
Robert Heller -- 978-544-6933
Deepwoods Software -- Custom Software Services
http://www.deepsoft.com/ -- Linux Administration Services
heller@xxxxxxxxxxxx -- Webhosting Services
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
