Kultex,
But first one question - whats the sense of the noauto fstab entries?
+1 :)
Kultex,
But first one question - whats the sense of the noauto fstab entries?
+1 :)
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?
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.
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?
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!
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".
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.
Yeah, and add your user to the "root" group :D
Seriously, maybe the differences in the logging in?
~/.profile for user and root?
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!).
You must log in to post.