nfs-boot with unionfs doesn't work

[Bernhard Seibold]

Binary package hint: casper

When using unionfs=unionfs and nfsboot, the "ro" option for the unionfs mountpoint is replaced by "nfsro".

This option has been removed more than two years ago. Instead, the default "ro" should be used.

--- casper 2009-10-08 15:51:19.000000000 +0000
+++ casper.fixed 2009-10-26 01:09:26.000000000 +0000
@@ -375,9 +375,7 @@
     # Let's just mount the read-only file systems first
     rofsstring=""
     rofslist=""
- if [ "${NETBOOT}" = "nfs" ] ; then
- roopt="nfsro" # work around a bug in nfs-unionfs locking
- elif [ "${UNIONFS}" = "aufs" ]; then
+ if [ "${UNIONFS}" = "aufs" ]; then
         roopt="rr"
     elif [ "${UNIONFS}" = "unionfs-fuse" ]; then
         roopt="RO"

[Bernhard Seibold (blubb8128)]

Hello? Anyone still alive?

Could anyone please apply the provided fix? Oh right, I didn't use apport. My bad.

[Colin Watson (cjwatson)]

Using apport has nothing to do with it (I for one don't filter on that). Assigning to ubuntu-bugs didn't particularly help though ...

I've applied your patch for the next upload. Thanks!

[Launchpad Janitor (janitor)]

This bug was fixed in the package casper - 1.226

---------------
casper (1.226) lucid; urgency=low

  [ Colin Watson ]
  * Stop using removed nfsro option for NFS/unionfs (thanks, Bernhard
    Seibold; LP: #460781).

  [ Jonathan Riddell ]
  * Remove scripts/casper-bottom/48enable_kubuntu_netbook and ubiquity-
    hooks/48enable_kubuntu_netbook now enabled in kubuntu-netbook-
    default-settings
 -- Jonathan Riddell <email address hidden> Wed, 10 Mar 2010 22:23:04 +0000