On Thu, 2004-09-09 at 06:05 -0700, Steve G wrote: > Sep 9 08:44:53 buildhost fstab-sync[2607]: removed all generated mount points > Sep 9 08:44:53 buildhost fstab-sync[2649]: added mount point /media/idedisk for > /dev/hda5 > Sep 9 08:44:54 buildhost fstab-sync[2655]: added mount point /media/idedisk1 for > /dev/hda1 > Sep 9 08:44:54 buildhost fstab-sync[2686]: added mount point /media/scsidisk for > /dev/sda2 > Sep 9 08:44:54 buildhost fstab-sync[2689]: added mount point /media/scsidisk1 > for /dev/sda1 > Are there valid mountable filesystems on these partitions? > I hand edit my /etc/fstab to only have these disks: /dev/sda3, /dev/sda5. I > really do not want anything else accessible to the system...its a security > violation in my view. I'm not sure I agree: if one cares about security one is using filesystems with uid/gid attributes anyway. That said, however, it might be useful to have a configuration file fstab-sync to explicitly specify don't add this or that drive. And in the longterm finetune the mount point names, e.g. using labels or whatnot. You could also just remove the kudzu,user option from the fstab file for the entries you are concerned about. That way they wont get added the next time you start the haldaemon service and no unprivileged user is able to mount them. > The sad part is that it did not recognize the cdrom which > is /dev/hdc. > This should work. What does 'udevinfo -r -q name -p /block/hdc' say? I've seen on some occasions that udevstart doesn't run; at least the udev database isn't populated with sufficient information to do the udevinfo. Does running 'service haldaemon stop; udevstart; service haldaemon start' solve your problem? Does ude Otherwise you need to file a bug against hal to we can fix it. Thanks, David
