On Friday 29 June 2007 09:15, Ricardo Sánchez wrote: > Randall R Schulz wrote: > ... > > > I don't know the answer to that, but the man page for "mount" > > mentions that /etc/mtab can either be a plain file that records the > > result of issuing the mount command or it can be a symbolic link to > > /proc/mounts. > > by creating a symbolic link to /proc/mounts all file systems are > displayed by df and other applications: > > ... > > However a reboot overwrites the symlink and the info is lost again. > > > Perhaps for some reason (the ordering of your /etc/init.d run-level > > scripts, perhaps?) your mounts all happen while the root file > > system is read-only and hence not recorded in /etc/mtab. > > I am not sure this is the problem. It has been happening for some > time and (at least to my knowledge) I haven't changed any of these > scripts. However, is there a possibility to fix this ordering, in > case it was modified or altered?
If the symlink alternative works for you, you could add a simple start-up script that replaces the file with the symlink late in the start-up sequence. However, given the fact that /etc/mtab (the file) is built from scratch upon each reboot and the fact that it's reconstituted even when the symlink is there, the implication is fairly firm that something in your boot sequence is the cause of the problem. You could search all your /etc/init.d scripts (or at least the active ones—those with symlinks to them in one of the run-level-specific directories) for uses of mount, umount or direct reference to the /etc/mtab file itself. It might give you clue as to what's going wrong. > Best regards Randall Schulz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
