From: Ken H. <ke...@ha...> - 2005-08-01 17:55:14
|
Tony Houghton wrote: > In <42E...@ha...>, Ken Hayber wrote: > > >>Tony Houghton wrote: >> >>>There seem to be two problems with mount points. The first is when >>>you've got a symlink to a mount point eg /cdrom which is created >>>automatically on the panel when installing ROX for the first time; >>>/cdrom used to be the actual mount point in Debian, but nowadays it's a >>>symlink to /media/cdrom0 or similar. ROX doesn't recognise it as being a >>>mount point. >> >>This works OK for me. Do you see the mount point in /etc/fstab? By >>default in some systems hotplug runs fstab-sync to update fstab when >>mountpoints change. > > > fstab only contains the actual mount point, /media/cdrom0, not the > symlink to it at /cdrom. Ah, didn't notice that these were symlinks you were talking about. In my case there is just /media/cdrecorder and no symlinks. > >>>The second problem is that when I mount a CD from the command line ROX >>>doesn't detect that and automatically turn the blob green on the >>>corresponding icon(s). It's very good at spotting when files and >>>directories have been updated, so shouldn't it be able to detect mounts >>>and unmounts too? >> >>When you mount manually there is no fstab entry. I think ROX is only >>looking at fstab - I don't think it is looking at /proc/mounts. Maybe >>it should? > > > I'm not sure whether you mean mtab here. /etc/fstab is a static file so > there's no way of telling from that whether something is mounted. No, I meant that it uses fstab to tell what MIGHT be mounted. I haven't looked at how it tells whether it actually is mounted or not. Re-reading your original message - if it shows the mountpoint indicator (un-green) then it does at least know that this is a mountpoint so I'm probably wrong here. > I looked at ROX's code for checking whether a directory is mounted a while > back, because I ripped it off for something else: it checks whether the > directory is on a different device from its parent (or has the same > inode - I'm not really sure why). I think the problem is that it just > isn't receiving/responding to whatever signal it might get to indicate > that the mount points have changed. It could probably use the same > method it uses to detect when the contents of a directory have changed. > In that case wouldn't a manual refresh be enough to get the green light? |