Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Anybody had experience enough with shfs and/or sshfs to compare/contrast the two? I'm having difficulty with shfs and a 2.6.20 linux kernel, but sshfs doesn't deal with file permissions quite as seamlessly.
Just looking for opinions and likes/dislikes for the two.
Does this solve the problem/feature that all users accessing a mounted share have mount-owner privileges on that share? In other words, if root mounts a volume with the allow_other option set, then any action that user bob takes on that mounted share will be with the privileges that root has. In other words, bob can now delete files on the mounted share that he normally would not be allowed to, just because the share was mounted by root originally.
Does this solve the problem/feature that all users accessing a mounted share have mount-owner privileges on that share? In other words, if root mounts a volume with the allow_other option set, then any action that user bob takes on that mounted share will be with the privileges that root has. In other words, bob can now delete files on the mounted share that he normally would not be allowed to, just because the share was mounted by root originally.
Well, looks like the option default_permissions takes care of the above issue and causes the kernel to check permissions like what would occur on a local volume.
That's what happens when you sit down and actually read the documentation. :-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.