Given the mounts did work if I used the -v option from the command line,
I experimented with adding the options shown in the verbose output to
the fstab options.
If I add the proto=udp option "an incorrect mount option" error message
goes away and the mount succeeds as before.
n2:/db /db nfs auto
Public bug reported:
Binary package hint: upstart
using 10.04 A3 I am unable to enable capture of boot messages.
/etc/default/boot contains BOOTLOGD_ENABLE=Yes
/sbin/bootlogd in installed
After some bug reports / Googling led me to believe that some of this
functionality is being subsumed into
Public bug reported:
Binary package hint: mount
with /etc/fstab containing;
n2:/db /db nfs auto,nfsvers=3 0 0
OR containing
n2:/db /db nfs auto 0 0
# mount /db
fails with message "mount.nfs: an incorrect mount option was specified"
# mount n2:/db /db
also fails with the same message
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/40832449/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/40832450/AplayDevices.txt
** Attachment added: "ArecordDevices.txt"
http://launchpadlibrarian.net/40832451/ArecordDevices.t
Public bug reported:
df -v does not list bind mounts that are listed in /proc/mounts
df -v does list bind mounts in Ubuntu 8.04
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/
I am seeing this problem in recently installed Feisty (final) amd64.
NFS mounts made during boot do not appear in "mount" or "df" commands
but the mounts have occurred and show up in /proc/mounts.
NFS mounts made from command-line after boot do appear in "mount" and
"df" command.
--
NFS mounts
I recently installed Feisty Herd 5. When Konqueror crashed and asked if
it should report the error it came back that the error was already
reported. I am assuming it correctly diagnosed the error.
The error occurs in Konquer, Firefox, and Seamonkey when trying to access many
different sites. In
