Newsgroup: it.comp.os.linux.iniziare
Titolo: problema fstab con ntfs-3g

se faccio il mount a mano con ntfs3g   tutto ok, ma come implementarlo 
in automatico in fstab? ho provato con le seguenti righe aggiunte in fstab:
/dev/hdc1		/mnt/hdc1		ntfs-3g  	0 0
/dev/hdc2		/mnt/hdc2		ntfs-3g 	0 0
purtroppo in partenza non le monta (riporto dmesg|grep 'hd')...
che cavolo fare?
da notare è che se dopo l'avvio faccio mount -a monta che è uno 
splendore....
     ide0: BM-DMA at 0x1860-0x1867, BIOS settings: hda:DMA, hdb:pio
     ide1: BM-DMA at 0x1868-0x186f, BIOS settings: hdc:DMA, hdd:DMA
hda: WDC WD400BB-23DEA0, ATA DISK drive
hdc: Maxtor 6Y080L0, ATA DISK drive
hdd: LITE-ON DVDRW LDW-411S, ATAPI CD/DVD-ROM drive
hda: max request size: 128KiB
hda: 78165360 sectors (40020 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
hda: cache flushes not supported
  hda: hda1 hda2 hda3
hdc: max request size: 128KiB
hdc: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=65535/16/63, 
UDMA(100)
hdc: cache flushes supported
  hdc: hdc1 hdc2
EXT3-fs: hda2: orphan cleanup on readonly fs
EXT3-fs: hda2: 4 orphan inodes deleted
SELinux: initialized (dev hda2, type ext3), uses xattr
hdd: ATAPI 40X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
EXT3 FS on hda2, internal journal
audit(1175111515.323:4): avc:  denied  { getattr } for  pid=1553 
comm="mount.ntfs-3g" name="modprobe" dev=hda2 ino=1375141 
scontext=system_u:system_r:mount_t:s0 
tcontext=system_u:object_r:insmod_exec_t:s0 tclass=file
audit(1175111515.323:5): avc:  denied  { execute } for  pid=1554 
comm="mount.ntfs-3g" name="bash" dev=hda2 ino=1931460 
scontext=system_u:system_r:mount_t:s0 
tcontext=system_u:object_r:shell_exec_t:s0 tclass=file
SELinux: initialized (dev hdc1, type fuseblk), not configured for labeling
audit(1175111516.602:6): avc:  denied  { mount } for  pid=1555 
comm="fusermount" name="/" dev=hdc1 ino=1 
scontext=system_u:system_r:mount_t:s0 
tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem
SELinux: initialized (dev hdc2, type fuseblk), not configured for labeling
audit(1175111516.693:7): avc:  denied  { mount } for  pid=1567 
comm="fusermount" name="/" dev=hdc2 ino=1 
scontext=system_u:system_r:mount_t:s0 
tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem
Adding 425712k swap on /dev/hda3.  Priority:-1 extents:1 across:425712k
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
SELinux: initialized (dev hdc1, type fuseblk), not configured for labeling
audit(1175111536.976:8): avc:  denied  { mount } for  pid=2315 
comm="fusermount" name="/" dev=hdc1 ino=1 
scontext=system_u:system_r:mount_t:s0 
tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem
SELinux: initialized (dev hdc2, type fuseblk), not configured for labeling
audit(1175111537.049:9): avc:  denied  { mount } for  pid=2319 
comm="fusermount" name="/" dev=hdc2 ino=1 
scontext=system_u:system_r:mount_t:s0 
tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem
SELinux: initialized (dev hdc1, type fuseblk), not configured for labeling
SELinux: initialized (dev hdc2, type fuseblk), not configured for labeling

 cavolo fare?
Deh, se non gli dici cosa farne dei due dischi!! ^__^ ;-)
-- 
Signature automatica inserita a mano.
In God we trust, all others we monitor 
(National Security Agency)

 Deh, se non gli dici cosa farne dei due dischi!! ^__^ ;-)
Grazie per l'info, ma il problem non era quello da te segnalato (fstab 
puo' andare anche così..)
L'ho risolto implemnetando le policy di selinux (non ci capisco un tubo, 
ma seguendo questo post (la terza risposta) 
http://www.fedoraitalia.org/modules/newbb/viewtopic.php?topic_id=11749
ci sono riuscito:
ciao e grazie comunque
claudio

 L'ho risolto implemnetando le policy di selinux
SELinux un'implementazione della sicurezza fortemente voluta dalla
NSA (Vedi la mia firma)
