Portál AbcLinuxu, 12. května 2025 13:20
/dev/sda6 / ext3 relatime 1 1 /dev/sdb /media/USB vfat ro,users,auto 0 0 none /media/cdrom supermount fs=udf:iso9660,dev=/dev/cdrom,--,iocharset=utf8,nosuid,ro,umask=0022,users,nodev,exec 0 0 /dev/hda2 /media/hd ext3 defaults 1 2 /dev/hda5 /media/hd2 ntfs umask=0,user,dev,suid,exec 0 0 /dev/sda1 /mnt/windows ntfs umask=0022,nls=utf8,ro 0 0 none /proc proc defaults 0 0 /dev/sda5 swap swap defaults 0 0Adresář /media/USB jsem vytvořil a supermount jsem použil až dodatečně. Prosím o radu, co je špatně, případně alespoň o výpis defaultního nastavení. Díky.
I found what seems to be the problem, thanks to bug #131107. gparted creates the file: /usr/share/hal/fdi/policy/gparted-disable-automount.fdi which stops any drives from automounting. I removed the file and restarted hal with "sudo /etc/init.d/hal restart" but this didn't have any effect; but after I rebooted completely, my drives now automount. Normally gparted deletes the file when it exits. I assume that (a) because gparted crashed, it didn't delete the file; (b) originally when I was rebooting, the file was flagged each time for deletion upon exit, so it didn't persist, and after reboot the drives mounted; but at some point the file became persistent and this broke automounting. Although gparted needs to stop drives from automounting (eg see bug #37768 and its duplicates), it's a bit dangerous to allow a file that disables all automounting to persist through reboots. To the end user, it just looks like automounting is broken.
Tiskni
Sdílej:
ISSN 1214-1267, (c) 1999-2007 Stickfish s.r.o.