Problem mounting NFS/CIFS

[gemini_user]

I've installed the Samba and NFS packages (samba, samba-common, smbfs, cifs-utils, nfs-common), but can't mount either shares.

Samba/CIFS gives me:

Code: [Select]

$ sudo mount -t cifs \\192.168.1.1\share /home/gemini/share
mount error: cifs filesystem not supported by the system

NFS gives me:

Code: [Select]

$ sudo mount -t nfs 192.168.1.1:/share /home/gemini/share
mount.nfs: No such device
Anyone any ideas what I'm doing wrong?  Both Samba and NFS shares have been working from the same server on many other Linux/Windows devices around my house

[mithrandir]

I've installed the Samba and NFS packages (samba, samba-common, smbfs, cifs-utils, nfs-common), but can't mount either shares.

Samba/CIFS gives me:

Code: [Select]

$ sudo mount -t cifs \\192.168.1.1\share /home/gemini/share
mount error: cifs filesystem not supported by the system

NFS gives me:

Code: [Select]

$ sudo mount -t nfs 192.168.1.1:/share /home/gemini/share
mount.nfs: No such device
Anyone any ideas what I'm doing wrong?  Both Samba and NFS shares have been working from the same server on many other Linux/Windows devices around my house

The default kernel is lacking module support. Thus many filesystems (especially nfs and samba) and  USB devices are unsupported. Build your own kernel with the filesystems you need or try my modular kernel from mygnu.de.
Mith

[gemini_user]

The default kernel is lacking module support. Thus many filesystems (especially nfs and samba) and  USB devices are unsupported. Build your own kernel with the filesystems you need or try my modular kernel from mygnu.de.
Mith

Ahhh... that explains it.  Not sure I'm "ready" for playing with kernels yet.  Will these modules be added in a later release?

[morty]

I've installed the Samba and NFS packages (samba, samba-common, smbfs, cifs-utils, nfs-common), but can't mount either shares.

Samba/CIFS gives me:

Code: [Select]

$ sudo mount -t cifs \\192.168.1.1\share /home/gemini/share
mount error: cifs filesystem not supported by the system

NFS gives me:

Code: [Select]

$ sudo mount -t nfs 192.168.1.1:/share /home/gemini/share
mount.nfs: No such device
Anyone any ideas what I'm doing wrong?  Both Samba and NFS shares have been working from the same server on many other Linux/Windows devices around my house

Wtf, not good news for me. One option/workaround could be sshfs, but I still had no time to flash debian to test it...

[Ali Compiler]

I've installed the Samba and NFS packages (samba, samba-common, smbfs, cifs-utils, nfs-common), but can't mount either shares.

Samba/CIFS gives me:

Code: [Select]

$ sudo mount -t cifs \\192.168.1.1\share /home/gemini/share
mount error: cifs filesystem not supported by the system

NFS gives me:

Code: [Select]

$ sudo mount -t nfs 192.168.1.1:/share /home/gemini/share
mount.nfs: No such device
Anyone any ideas what I'm doing wrong?  Both Samba and NFS shares have been working from the same server on many other Linux/Windows devices around my house

I still haven't tried this, but you could try mucommander for browsing and accessing CIFS, I use it heavily on my desktop. I will try it probably tonight and let you know.

[mithrandir]

The default kernel is lacking module support. Thus many filesystems (especially nfs and samba) and  USB devices are unsupported. Build your own kernel with the filesystems you need or try my modular kernel from mygnu.de.
Mith

Ahhh... that explains it.  Not sure I'm "ready" for playing with kernels yet.  Will these modules be added in a later release?

Don't know, unfortunately, but hoping for it. Maybe we should collect requests, what should be changed in kernel configuration, somewhere. I'm quite sure others have additional ideas what should get added.

[loop]

NFS (client) works with the latest kernel and modules from mygnu.de, thanks!

BTW, the kernel can also be installed by booting to TWRP and then doing this from the desktop (be careful to select the correct block device):

Code: [Select]

adb push linux_boot-gemini-3.18.41+_2018_07_12.img /dev/block/mmcblk0p30
adb pull and adb push on block devices (with TWRP) can also be used for creating image backups and restoring them, without having to deal with that flaky flash tool and its scatter file. TWRP even provides a decrypted version of the user data partition in /dev/block/dm-0. The names and sizes of the partitions can be retrieved with

Code: [Select]

adb pull /proc/partitions