Michael Biebl:
2013/7/12 <[email protected]>:
Reindl Harald:
Your use of sshfs# as a FUSE type is wrong -- you must use fuse.sshfs
as
the fstype instead.
this simply wrong, this line below in /etc/fstab works day
and night from FC9 to Fedora 18 as well as curlftpsfs
mounts in /etc/fstab are starting with curlftpfs#
and *both* have "fuse" and nothing else as fstype
sshfs#reindl@webserver:/ /mnt/webserver fuse
noauto,user,rw,noexec,nosuid,nodev,uid=harry
the server is a simple openssh on F17 with native sftp-chroot
Reindl, thank goodness you're listening. Have you by chance, tried this
with auto, to see whether it automounts on wake from suspend?
systemd doesn't unmount the fs on suspend, why should it mount it on resume?
Maybe you are mixing up what "auto" means.
Why is everyone so uptight here?
No, I am not mixing up what "auto" means. Auto is supposed to mean that
it --mounts automatically--, period, like the word says. But it does
not, as you can see.
If "auto" does not make it mount automatically on wake for some reason,
THEN WHAT WILL? That is the real question here. Why won't it mount on
WAKE? The point is -not- to argue what "auto" means. The question is
about how to make the drive mount on wake. Do we prefer to nit-pick, or
to advance the cause? The goal is to make this drive mount on wake, a
very common function.
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
