You are not logged in.
Pages: 1
How do I load the kernel module fuse with systemd?
I tryied modprobe fuse but no joy. So I'm guessing there is something else.
Looking for ideas in the forums gives me all kind of solutions that not not apply to my problem.
I have and Arch 64 bits system (just built it) do I need something "special" to make it work? In my old 32 bit system it use to work just fine.
Thanks.
R.
Last edited by ralvez (2013-02-14 01:50:26)
Offline
You shouldn't have to load it. It should do it for you. Have you updated and not rebooted after a kernel update?
Offline
Offline
@WonderWoofy,
Nope. As I say in the post this is a brand new install, so everything is "the latest"; nevertheless, the module is not loaded.
@jasonwryan,
I did read that manual you kindly pointed me to, but (I mentioned it in my post, I think ...) when I do modprobe fuse if I query
systemd to see if the module is loaded with :systemctl --all |grep fuse I get no response, I expect something like:
sys-module-fuse.device loaded active plugged /sys/module/fuse
Now. If I create an /etc/rc.conf file and add a DAEMONS line with "sshfs" it works. But the way I read the instructions in Arch, this is
deprecated and we should be able to do it just with systemd ... or am I missing (missreading) something?
Thanks both for posting.
R.
Offline
Have you installed a package that includes the module?
I'm sorry, but I am having difficulty understanding what the problem is.
Offline
The problem is that I installed a brand new Arch 64 bit system and according to current literature in the Arch site I understand that I do not need to have an /etc/rc.conf file to load the kernel modules like fuse.
But if I do not do that it does not work.
If I try to load the module by using modprobe fuse, it will not load it and after hours browsing arround and reading notes int the site and in Google I cannot find any way to tell systemd to start the module for me... unless, of course I use /etc/rc.conf with I understand I should not use. Or am I wrong?
If I should **not** be using /etc/rc.conf is there a documentation you can point me to that I can follow to load the module with systemd **only** and get things to work?
Hope this is a better explanation.
Thanks.
R.
Offline
1. install fuse
2. modprobe fuse
3. create conf file under /etc/modules-load.d/ with the single word "fuse" in it and it will load at boot
That is all there is to it. There is no /etc/rc.conf anymore.
Offline
Guys... I know that I am no expert but... all I did was installed:
sshfs
package on the client and rebooted and right after that I have run on the ssh client (where the drive is being mounted using sshfs):
su
mkdir /media/1862_GB_X-Ternal
chown login:login /media/1862_GB_X-Ternal
and then as user I ran:
sshfs -p 22 login@hostname:/mount/point/ /media/1862_GB_X-Ternal/
and since I have ssh authentication with a auth keys - drive was mounted.
Later I have created a .sh script that runs the command for me at boot time automagically and it works...
Added:
/media/1862_GB_X-Ternal/
to the dolphin places menu and it's there... after each boot.
Same command in my LXDE machine - pcmanfm sees the drive as a local drive - never even had to add it in the "Places" pane...
I know I am probably not doing it right but... it works.
I wrote this while still using PCLinuxOS. I know - You will probably laugh and say it's lame but what the heck...
Regards.
Andrzej
Last edited by AndrzejL (2013-02-14 01:04:32)
The worst thing about censorship is ██████ ██ ████ ████████████ and ██████ ███████ ███ ███████████.
Offline
1. install fuse
2. modprobe fuse
3. create conf file under /etc/modules-load.d/ with the single word "fuse" in it and it will load at bootThat is all there is to it. There is no /etc/rc.conf anymore.
I had read somewhere (may be Google or some Arch doc.) about your point 3.
At the time I created a fuse.conf but no joy... now, based on your instuction I just created the file /etc/modules-load.d/conf with the word "fuse" and that **did** work.
Fantastic!! [ happy camper here ].
From what I've read I think I can also add other modules there, one per line, to load other things I may need. Am I correct?
Thanks Very much!!
@AndrzejL,
That was precisely what **did not** work for me.
That's why I went out of my way to make it work the "correct" way. I had it working via /etc/rc.conf but I knew it was not the way to do it based on what I had read.
Offline
What does lsmod | grep fuse give?
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
From what I've read I think I can also add other modules there, one per line, to load other things I may need. Am I correct?
If you add other files to that directory, the only stipulation is they have to end in .conf. So you might want to rename your file to sshfs.conf so you can easily add others (if needed).
Please don't forget to mark your thread as solved.
Offline
@jasonwryan,
Interesting ... for what you say it should have worked the fist time when I named it /etc/modules-load.d/fuse.conf but it dit not. That's what started this "quest".
I'll play with it a bit more then, as I would rather have a more meaningfull name than "conf".
Thanks your help and to all who posted.
R.
Offline
I don't think you can have just "conf", it needs to be *.conf. So something like modules.conf would work nicely... nice and generic.
Offline
Well ... it did work just with conf.
I've renamed it again to fuse.conf to have a more meaingful way to describe what that file is doing there. It continued to work so I'm happy either way.
Thanks for your help WonderWoofy.
R.
Offline
This is kind of an old post, but for others who read it looking for help: the instructions at https://wiki.archlinux.org/index.php/Sshfs are kind of misleading. I had to first mount the remote filesystem before "systemctl list-units -all | grep fuse" gave the expected output. For those familiar with how systemd works, that may be obvious, but many of us are still pretty new to it.
So the modified instructions are:
1. Install sshfs (will install fuse as dependency)
2. Load module: sudo modprobe fuse
3. Mount remote directory: sshfs sshserver:/home/user ~/REMOTE
4. Verify with systemctl list-units -all | grep fuse
Of course, step 4 isn't really necessary, if step 3 works.
Last edited by ke7mbz (2013-11-29 14:19:45)
Offline
Yes, I just confirmed that the module gets loaded automatically when running sshfs. Thanks for pointing that out. I've added a couple notes to the wiki page, but someone with better understanding of how it works should probably clean it up.
So then:
1. install sshfs
2. reboot if you've updated the kernel since the last reboot.
3. run the sshfs command to mount the remote directory.
Last edited by ke7mbz (2013-11-29 14:38:19)
Offline
Pages: 1