[Bug 476208] Re: casper booting from nfsroot doesn't respect nfs filesystem options correctly

[Brian Murray]

** Tags added: patch

** Changed in: casper (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to casper in Ubuntu.
https://bugs.launchpad.net/bugs/476208

Title:
  casper booting from nfsroot doesn't respect nfs filesystem options
  correctly

Status in “casper” package in Ubuntu:
  New

Bug description:
  Binary package hint: casper

  the use of nfsroot filesystem options when booting casper is not possibly. nfs filesystem options are usually needed as for example the choice of transport layer (UDP or TCP), transport unit size, etc. cannot be supplied by DHCP. 
  first of all it is very confusing that the regular ubuntu initrd nfsroot option works differently when using casper:
  casper doesn't accept filesystem options to be appended like nfsroot=[server:]/path[,options] but rather seems to provide an aditional boot option nfsopts. unfortunately this option is not treated correctly in scripts/casper in do_nfsmount() as no additional "-o" is given in the nfsmount call an the use of quoting in kernel boot options is terribly ugly.
  probably the same applies when using CIFS, but i didn't have the chance to verify that.
  a patch against the current development tree to fix the problem is attached.
  the patch simply prefixes the ${NFSROOT} variable, if set, with the string "-o ". in this way using the nfsopts boot option is possible.
  in general it is probably better to harmonize the syntax of nfsroot such that the nfsroot string is parsed the same way the nfs script normal initramfs does...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/476208/+subscriptions