Hrmm... We'll probably need to end up doing a check on
$NEWROOT/etc/redhat-release to check the version, and do custom
handling on the 7.x series.
Thanks,
-J
On Wed, Aug 3, 2016 at 6:26 PM, Danny Thompson <
surf...@gmail.com> wrote:
> Hi Jason,
>
> Here is what I found with 95-umount:
>
> In CentOS 7, /etc/mtab is a symlink to /proc/self/mounts which is read only,
> so the first line that tries to clear it doesn't. I removed the mtab link in
> my VNFS knowing that 95-umount will recreate it.
>
> At the bottom of the file there are 3 chroot mount commands. IIRC the bottom
> two were throwing code 32 (busy or already mounted). As a quick hack I put
> return 0 at the end of 95-umount and the system booted, with SELinux enabled
> :)
>
> I'll patch my RPM's to include this for the short-term. How would you
> approach error handling for 95-umount?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Warewulf" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
warewulf+u...@lbl.gov.
> To post to this group, send email to
ware...@lbl.gov.
> To view this discussion on the web visit
>
https://groups.google.com/a/lbl.gov/d/msgid/warewulf/6f96caae-5339-489a-9d69-356396109e18%40lbl.gov.
>
> For more options, visit
https://groups.google.com/a/lbl.gov/d/optout.