| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
This bug was accidentially introduced in commit ec9bd07c which removed
unionfs-fuse support.
|
|
|
|
alternatives.
|
|
|
|
|
|
* unionfs-fuse itself has been always very buggy for us.
* unionfs-fuse code in live-boot as been experimental at best.
* the FUSE implementation is horribly slow due to the nature of
FUSE (~10min to boot a live system with unionfs-fuse compared
to <<1min with aufs).
* and last but not least, there's overlay in kernel mainline now.
|
|
compatibility (Closes: #773881).
When overlayfs got merged into kernel mainline it was
renamed to overlay. We don't provide backwards compatibility
since overlayfs support was experimental and only with
non-debian default kernels available.
|
|
When no device for an overlay can be found, /tmp/custom_mounts.list
won't be created and will produce warnings while booting:
sort: /tmp/custom_mounts.list: No such file or directory
rm: can't remove '/tmp/custom_mounts.list': No such file or directory
Properly handle this case by calling rm with the -f option and calling
sort only when the file exists.
|
|
uncompressed filesystems, thanks to John Bazik <jsb@cs.brown.edu> (Closes: #728250).
|
|
|
