bug #1410480, overlayfs v1: renaming existing file uses chardev whiteout (should be symlink)
seems to have nothing at all to do with ubiquity install failures which is this bug here.
I've verified tahr 14.04 booted /etc/default/keyboard has file permissions
-rw-r--r--
while later 15.10 has file permissions
c---------
no wonder ubiquity can't even access it.
which is nonsense. What's that got to do with bug #1410480 about chardev whiteout?
bug #1410480, overlayfs v1: renaming existing file uses chardev whiteout (should be symlink)
seems to have nothing at all to do with ubiquity install failures which is this bug here.
I've verified tahr 14.04 booted /etc/default/ keyboard has file permissions
-rw-r--r--
while later 15.10 has file permissions
c---------
no wonder ubiquity can't even access it.
which is nonsense. What's that got to do with bug #1410480 about chardev whiteout?