The title line says it all.
I am experimenting with ecryptfs. And it seems to not work properly unless I first use "modprobe ecryptfs" as root.
Printable View
The title line says it all.
I am experimenting with ecryptfs. And it seems to not work properly unless I first use "modprobe ecryptfs" as root.
Would it be a problem to add it initrd? Just a thought.Quote:
Originally Posted by nrickert
I guess that could be done. It doesn't need to be that early. Adding to the "after.local" initscript would be plenty early enough. I think that still runs with systemd.Quote:
Originally Posted by please_try_again
I'm just wondering if there is an official place to list modules that should always be loaded.
Let me give a little more detail. I used "ecryptfs-setup-private" to set things up. That just gave a message that modprobe is needed. Well, no big deal, since you only run the setup once.
Now, after boot and login, I run ecryptfs-mount-private to make the private files available. And that sort-of works. If I first run the modprobe it works well. But without the prior modprobe, it still mounts - presumably it is loading the module itself. But the mounted Private file system has only encrypted filenames, which makes it pretty hard to use. I'll probably report this as a bug after a bit more experimenting. Forcing the module to load before running ecryptfs-mount-private works just fine.
It should be MODULES_LOADED_ON_BOOT in /etc/sysconfig/kernel. You can add modules to this list from YaST sysconfig Editor too... and/or the files in /etc/modprob.d. Did you try to load it in /etc/modprobe.d/99-local.conf?Quote:
Originally Posted by nrickert
Thanks. That's the kind of information I was looking for.
I think it's fixed in the recent systemd update, but in case not, you can list the modules, one per line, in /etc/modules-load.d/something.conf