SliTaz Forum
You are not logged in.
Now the answers to your requests. I trim outputs to relevant parts.
[c]~> df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 9614116 6270108 2855636 69% /
/dev/root 9614116 6270108 2855636 69% /
tmpfs 377972 264 377708 1% /run
tmpfs 377972 264 377708 1% /var/run
devtmpfs 377752 0 377752 0% /dev
tmpfs 377972 0 377972 0% /dev/shm
tmpfs 377972 4 377968 1% /var/lock
/dev/sda3 87891612 41172836 46718776 47% /data
/dev/sda7 15798620 7692700 8105920 49% /home
/dev/sda8 21726224 5383524 16342700 25% /archive
~> cat /etc/fstab
/dev/sda1 /win/C ntfs-3g defaults,noauto,user,permissions,fmask=177,dmask=077 0 2
/dev/sda2 /win/D ntfs-3g defaults,noauto,user,uid=1000,gid=1000,permissions,fmask=177,dmask=077 0 2
/dev/sda3 /data ntfs-3g defaults,auto,user,uid=1000,gid=1000,permissions,fmask=177,dmask=077 0 2
/dev/sda5 none swap defaults 0 0
/dev/sda7 /home ext4 defaults 0 2
/dev/sda8 /archive ext4 defaults 0 2
# clé EMTEC
/dev/disk/by-label/NTFS_part /media/NTFS_part ntfs-3g defaults,async,noauto,user,noatime,uid=1000,gid=1000,permissions,fmask=177,dmask=077 0 2
# clé Transcend
/dev/disk/by-id/usb-JetFlash_Transcend_8GB_4SQJ51NT-0:0-part2 /media/Linux_partition squashfs noauto,user 0 2
/dev/disk/by-label/LucasLevrel /media/LucasLevrel vfat defaults,async,noatime,noauto,user,fmask=133,dmask=022 0 2
~> ls -l /media /win
/media:
drwxr-xr-x 2 root root 4096 mai 13 2014 Linux_partition
drwxr-xr-x 2 root root 4096 mai 13 2014 LucasLevrel
drwxrwxrwx 2 root root 4096 mai 13 2014 NTFS_part
/win:
drwxrwxrwx 2 root root 4096 déc. 27 2012 C
drwxrwxrwx 2 root root 4096 déc. 27 2012 D
~> sudo fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 1147 9213246 7 HPFS/NTFS
/dev/sda2 1148 2431 10313730 7 HPFS/NTFS
/dev/sda3 2432 13373 87891615 7 HPFS/NTFS
/dev/sda4 13374 19458 48872281+ 5 Extended
/dev/sda5 13374 13495 979933+ 82 Linux swap
/dev/sda6 * 13496 14711 9767488+ 83 Linux
/dev/sda7 14712 16710 16051589+ 83 Linux
/dev/sda8 16710 19458 22073144 83 Linux
Disk /dev/sdb: 8004 MB, 8004829184 bytes
102 heads, 38 sectors/track, 4033 cylinders
Units = cylinders of 3876 * 512 = 1984512 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 4034 7817197 7 HPFS/NTFS
Disk /dev/sdc: 8031 MB, 8031043584 bytes
99 heads, 18 sectors/track, 8802 cylinders
Units = cylinders of 1782 * 512 = 912384 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 4384 3906135 b Win95 FAT32
/dev/sdc2 4385 8803 3936672 88 Unknown[/c]
Offline
evrything looks good
what I ment with check with spacefm - what partions do you see with spacefm just after boot and uninstall udevil before, if you installed udevil
mybe in spacefm the partitions window is not open - just click the little computer left in the second row
just to check - is it a general problem or a problem with pcmanfm
pleas attach the spacefm screenshot
[attachment=36043,1851]
Offline
Hi,
Udevil had been installed as a dependence of spacefm. I removed it now as per your instructions.
After adding uid= and gid= to fstab, I could mount & use the Win partitions at will. My NTFS USB key mounts as expected, now that udisksctl is used by spacefm.
However I can't make it show unplugged, fstab-listed devices, even using the Show|Volumes dialog. (I guess it doesn't parse fstab itself, it relies on udev and udisks to list and mount devices.)
[attachment=36061,1852]
Offline
IMHO, it is very important that pcmanfm will *not* create automatic mounts, when run as Live RAM.
But on left, click on disk to mount, *and* icon to unmount.
That is critical for who does forensics, scripts with hardcoded disk label names, and so on... 
so I think, that it is mainly a problem of pcmanfm
so that means, that I have to make some fstab isos and test it on my laptop - thats the only one, where I have ntfs files.
But first one question - whats the sense of the noauto fstab entries?
pcmanfm sees my ntfs partitions and mounts them all the time on the same place - for me noauto does not have any more sense - it comes from times, when there was no udisk and no hal and you had to mount evrything by hand....
Offline
Kultex,
But first one question - whats the sense of the noauto fstab entries?
+1 
Offline
Why noauto? Let's say that I want to be more foolproof: not mounted==not at risk! Also mounting at boot may take time if the "max fs mount count before check" is reached (inducing fsck during boot).
(Just to be sure: noauto in fstab means not mounted at boot if present; it does not mean no automount of removable devices.)
But the problem is more general, and not limited to NTFS: now that I updated pcmanfm, udisks2, and gvfs, NTFS partitions can be mounted by user. But I don't see any fstab entry anymore, whatever the filesystem (so kultex, you don't have to test specifically with NTFS partitions).
Why on earth does root get the behaviour I want, and tux doesn't?
Offline
Few citations:
http://sourceforge.net/p/pcmanfm/bugs/326/
Bug #326 does not show mounted drives listed in fstab
Whether a volume should be shown or not is controlled by udisks.
If you really need it to be in the side pane, add it to bookmarks.
PCMan
http://wiki.lxde.org/en/PCManFM#Known_GTK_issues
Non-mountable entries in /etc/fstab may cause 100% CPU load on mount attempt. The bug is reported to GNOME. Workaround: disable option 'Mount mountable volumes automatically on program startup' in Preferences or (better) remove those devices from /etc/fstab.
And my IMHO.
[*]PCManFM not auto-mounts internal HDD partitions.
[*]PCManFM not shows any partitions listed in the /etc/fstab.
All that my IMHO and only on my SliTaz. So, I can't suggest you to remove (comment) your lines in the /etc/fstab. But you can try on your own.
PCManFM uses external (for it) systems to list/mount/unmount partitions — GVFS, Udisks. And that systems is too complicated as for me. SliTaz-4.0 was used old good HAL And SliTaz-next-to-4.0 (some of Cooking) was broken for a long time because of difficulty of GVFS/Udisks settings. Then SliTaz maintainers fixed it in one good day. And what? Is it broken again?
Offline
Hi Aleksej,
Thanks for the links: I followed some more links therein and found this: https://git.gnome.org/browse/gvfs/tree/monitor/udisks2/what-is-shown.txt which gives explanations and a solution.
Explanation: internal devices will be shown only if their path is in /media, $HOME, or /run/media/$USER.
Solution: one can add option x-gvfs-show to device options in fstab to force it to be shown, and x-gvfs-name=(something) to set its displayed name.
It works for internal devices. According to the cited doc my USB devices should be displayed (their mountpoints are in /media), but they are not even if I add the x-gvfs-show option in fstab. But they do show up once plugged in, so everything is fine.
The mystery about the root-launched pcmanfm behaving differently remains, but as you say this is complicated to debug!
Thanks to everybody for your help.
P.S. : the comment by "PCMan" in the sourceforge bug is silly: one cannot mount and unmount devices with bookmarks!
Offline
Oh, thank you very much for that link! It's very useful knowledge. And my congrats.
As for fixing udisks. Maybe try to check your user groups belongs to.
Read /etc/passwd, add using addgroup. Or do it using TazPanel.
Seems like user should belong to group "disk" (or "disks", can't recall that), "plugdev" and/or something else.
PS. PCMan's comment have sense in the ordinary case. I mean not to write "noauto" to the fstab. So, I can mount my /dev/sda5 as /mnt/sda5 using fstab. And then add bookmark to /mnt/sda5. Of course, here's another case with "noauto".
Offline
Yes, I was so desperate that I had tried to add tux to *every* group (even root, wheel, etc.) then reboot, but no effect. Too bad.
Offline
Yeah, and add your user to the "root" group 
Seriously, maybe the differences in the logging in?
~/.profile for user and root?
Offline
Good idea, but I found nothing. Root has no .profile, ~tux/.profile and /etc/profile only change some environment variables, so I changed tux's variable so as to get the same as root, but no effect.
I noticed that pcmanfm launched by root ignores the x-gvfs-name settings! It also has a small icon in the toolbar with tooltip "You are in super-user mode". So maybe pcmanfm devs made a branch in their code to treat root specially (and maybe they changed the behaviour for normal users but forgot to update the root branch!).
Offline
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.57 MiB (Peak: 1.77 MiB) ]