Hola Arthur Marsh! El 05/12/2011 a las 12:48 escribiste: > Is there a standard set of error values that mount.$fstype is > supposed to return to mount? The original problem was the boot > process failing if a vfat filesystem was listed in /etc/fstab but > the device did not exist (e.g. a removable drive not plugged in).
The normal 0 on success and a != 0 on failure is good enough for the mount command. I'm not sure I follow the use case. I added a line to my fstab to mount my pendrive as: /dev/sdb1 /mnt vfat defaults 0 0 I removed my pendrive and rebooted my computer. It booted normally, the system tried to mount the pendrive, failed, and continued the with rest of the filesystems. Is this the use case you were mentioning? > I found some workaround or the problem was fixed, but maybe some > pointers to documenting the error codes that mount expects from > mount.$fstype could be helpful. The "appropriate" value should be the ones listed in the mount man page. Should we close this bug? Thanks for reporting, -- "It is not the task of the University to offer what society asks for, but to give what society needs." -- Edsger W. Dijkstra Saludos /\/\ /\ >< `/
signature.asc
Description: Digital signature
