Mounting devices

/etc/fstab

• in Linux/Unix system the most important file containing informations about partitions, hard disks and all drives is /etc/fstab

• some options:
  • relatime
  • errors=remount-ro
  • auto
  • defaults
  • ro
  • rw
  • users
  • gid=
  • uid=

mount

• the command called without parameters will show the current mounted partitions:

mount 

• to do a mount action, specify:

  mount -t "filesystem type" device destination-directory

• to mount an ext2 partition (run as root), tiao

mount  -t ext2 /dev/sdb5 /mnt/disk2

• to mount an ntfs partition (run as root), tiao

automount

• most of linux-es is using hal as mount system, with dbus managing the lower system level of devices.

• installing automont function for KDE

emerge kioslaves dbus hal
rc-update add hald default
rc-update add dbus default
/etc/init.d/hald start
/etc/init.d/dbus start

issues

automount

• I did this to solve a broken library dependency (I wasn't aware of revdep-rebuild)

 ln -s /usr/lib/libdbus-1.so.3 /usr/lib/libdbus-1.so.2

per un problema di versioni di dbus/KDE

• Problema HAL:

con la versione >= 0.5.9 spesso il processo hald entra in un loop infinito:

/etc/init.d/hald stop
hald --daemon=no --verbose=yes
device_info.c:983: Unhandled rule (0)!
device_info.c:983: Unhandled rule (0)! 
device_info.c:983: Unhandled rule (0)!
device_info.c:983: Unhandled rule (0)! 
device_info.c:983: Unhandled rule (0)!
device_info.c:983: Unhandled rule (0)! 
[...]

Il problema è un file che crea libgphoto2 per interagire con hal:

/usr/share/hal/fdi/information/10freedesktop/10-camera-libgphoto2.fdi

commentando l'interno di questo file si risolve il problema. Secondo me funziona anche aggiungendo la use flag:

media-libs/libgphoto2 -hal

in

/etc/portage/package.use