Hello,
Could somebody please compile BusyBox 17.2 with all the features/utilities turned ON, especially CIFS and NFS (for mount utility)? I know it's not a stable release yet, but instead of compiling a stable one, why not the latest...
The ultimate purpose for me is a future use of "mount", when all necessary modules are published by Dev team.
The next of course would be to compile CIFS and NFS (along with dependencies such as RPC etc.) modules.
Since we don't have a working CIFS modules yet, I was fooling around with NFS and I was able to use older BusyBox builds, where NFS was ON.
I also got very close to mounting a remote NFS share - I used NetRipper's regular kernel, but loaded (modprobe) NFS module (with dependency modules) from NetRipper's USBHOST kernel, making sure that kernel build IDs are the same, otherwise modules would not load...
So everything seemed to be OK, modules loaded, busybox with NFS enabled mount ready, myself excited about what I might have achieved, up until I stumbled on "mounting failed: Not a directory" error... Initially mount command was failing with "mounting failed: Input/output error", then I switched to "TCP" with "nolock" mode, that's when "Not a directory" error surfaced...
I guess there is still some incompatibility with the kernel... just time wasted
Anyway, just created this thread for BusyBox 17.2.
I can attach all other older BusyBox versions that I was able to dig up online, they have different sets of features/utilities and I tested them all. Just let me know if anybody interested.
CJ
Please help..
Please give me a instructions about openvpn..
And is there a available tun.ko for my phone?
Heres my info..
Version: 2.3.6
Kernel: 2.6.35.7
Build: GINGERBREAD.WC13
I try using tun.ko installer but when i open the app,it said, TUN MODULE IS PRELOADED, PATH FOR TUN.KO IS NOT FOUND and when i push install it says TUN MODULE IS INCOMPATIBLE..
Please help...
Sent from my SHW-M110S using XDA
Maybe the kernel has include tun.ko module.
You can enter the command line mode on the phone.(Bette Terminal Emulator)
Run modprobe or lsmod command to check tun status.
If Tun Installer can't find the correct and compatible tun.ko, you must compile it by youself.
To compile tun.ko, you must download the Phone's resource code. Establish a Linux system.
Phone is rooted?
Hoping for CIFS modules compiled for 4.2...
I have these: cifs module for 3.1.10-g52027f9
from:
http://forum.xda-developers.com/showthread.php?t=1781411
but after flashing the 4.2 zip, Mount Manager won't load them. MM is getting root permissions.
Thanks!
Same thing happening to me. No idea how to write modules. Need someone smarter than me to do this.
Me too
Same thing here! Because of that, "Mount Manager" stopped working. Is there any alternative to that? I use "mount manager" to watch some movies located on my network NAS
Hi folks
My issue that I cannot seem to resolve is one of CIFS share mounting. I have trawled the XDA forums, google, and many many other android sites with no luck.
Current state
Nexus 4
CyanogenMod 10.1 RC4 (but have been running nightlies and RCs almost since release)
Latest version of CifsManager
Folders created:
/mnt/cifs/*
Where * is various folder names matched to my CIFS shares being served from an OpenMediaVault storage PC.
My understanding is that CM10.1 has CIFS support built into the kernel, as there are no cifs modules in the usual places one would expect to find them.
No matter what I try in CifsManager, the mount fails with:
Code:
Mounting the share has failed with an error. mount: Invalid argument
I thought this may be an issue with CifsManager, so I hopped into the shell to see what I could find. I am no *nix guru, but am comfortable (mostly) in the commandline.
I fired up ADB, connected the device and entered an ADB shell with root access via su.
I issued a BUNCH of different mount commands, with no luck, some of which were:
Code:
mount -t cifs //192.168.1.3/share1 /mnt/cifs/share1
mount -o username=<username> -t cifs //192.168.1.3/share1 /mnt/cifs/share1
mount -o username=<username>,password=<password> -t cifs //192.168.1.3/share1 /mnt/cifs/share1
I tried variations of these with the options after the type and vice versa, and with one/both of those after the device/mount point pieces.
All consistently gave the same error as CifsManager:
Code:
mount: Invalid argument
I even tried using
Code:
-t smbfs
and get the following error:
Code:
mount: No such device
The only additional note I could find that I thought worth mentioning is this entry in dmesg:
Code:
<3>[14314.292444] CIFS VFS: Connecting to DFS root not implemented yet
At this point I am officially out of ideas and operating beyond my capabilities so if you have any suggestions or advice, please let me know what additional information I can provide here.
I should note that I have two Xoom's and an SGS2 all of which mount these shares fine. The Xooms are running EOS4 and the SGS2 was also running CM10.x - interestingly both of these ROMS had cifs modules rather than having them built into the kernel.
Thanks in advance.
/system/xbin/mount (soft-linked to busybox) rather than /system/bin/mount (linked to toolbox) works for me. I'm not sure that it's entirely safe to point the link in "bin" to busybox (which is necessary if you're using CifsManager as it has no option to set a path to "mount"), but everything seems to be alright, except that the busybox'es "mount" refuses to remount root read-write sometimes, and you need to specify a different dir for CifsManager (e.g. /data/cifs instead of /mnt/cifs).
[SOLVED]
OK,
so with a bit of luck, I seem to have got to the bottom of this.
Within CifsManager, the following configuration for a share works:
Share Path
<IP address>/<share>
Mount Point
/mnt/cifs/<share>
Username
<username>
Password
Leave blank - if this is populated, it causes the "Invalid argument" error when mounting the CIFS share.
Options
Code:
unc=\\\\<IP address>\\<share>,pass=<password>
Now that I have it working, I remember reading on a post long time ago, that if the CIFS module is built into the kernel it required the unc= option to work.
Would it be worth getting in touch with the CifsManager devs and logging this as a bug do you think?
[keywords]
How to mount a cifs share on Google Nexus 4 with CifsManager and CyanogenMod 10
Does it still works? I am using CM 10.1 nightly based on Android 4.2.2 and I am unable to make it work.
Do you use a kernel other than CM default?
Why do i want to mount cifs? Any specific reason?
Sent from my Nexus 4
kewlfais said:
Why do i want to mount cifs? Any specific reason?
Sent from my Nexus 4
Click to expand...
Click to collapse
I want to conect to my samba share over wifi. I'd prefer to mount them because, If I can mount them, I am free to use all programs/file explorers etc. to browse files/watch movies etc.
Well basically nexus talks only on mtp protocol.
U have options of connecting ur device via ssh by installing ssh server on phone but for me it wss slow so i dropped that.
Even there is a app name software data cable which connects via ftp.
Sent from my Nexus 4
---------- Post added at 02:08 AM ---------- Previous post was at 02:07 AM ----------
Or use airdroid that is also good app
Sent from my Nexus 4
gergefil said:
Does it still works? I am using CM 10.1 nightly based on Android 4.2.2 and I am unable to make it work.
Do you use a kernel other than CM default?
Click to expand...
Click to collapse
Hi
yes this still works. Please note my original post got screwed up by the forums - it removed some of the \'s. I have fixed this now in the original post, but by explanation there should be double the number of normal \'s in the UNC path (as escape characters I guess) so \ \ \ \ unc \ \ path
I do not use any custom kernel, just what is in the standard nightly CM builds (I also update to most nightlies..)
I hope this is clear
Swaziboy said:
Hi
yes this still works. Please note my original post got screwed up by the forums - it removed some of the \'s. I have fixed this now in the original post, but by explanation there should be double the number of normal \'s in the UNC path (as escape characters I guess) so \ \ \ \ unc \ \ path
I do not use any custom kernel, just what is in the standard nightly CM builds (I also update to most nightlies..)
I hope this is clear
Click to expand...
Click to collapse
I am now able to make it work. Thanks.
Hey Swaziboy,
I have one more question:
Did you try to mount cifs share anywhere other than /mnt/cifs/SHARE
I want all applications to see my share, so I try to mount them into /mnt/sdcard/SHARE When I mount it to /mnt/cifs/ everything is perfect. However when I try to mount it into /mnt/sdcard/SHARE, cifs manager says it is mounted, however I can't see it on mount list and, it is not mounted at all.
Do you have any idea/suggestions?
Hello,
I'm looking for these modules nfs, and cifs.
I'm in stock 4.4.2 (KOT49H) factory rooted. I want to mount my nas synology in /sdcard/synology
As i see, i'm unable to find any answer about cifs and nfs module for Nexus 4. Some of you have create a custom kernel that include these modules.
I'm familiar with "everytime flash", everytime flashin recovery to the last TWRP or CWM, baseband, etc.....
So How i can't find these module in any rom or kernel that i've tested? what is so hard? no one think about this?
My question is : Is that possible to "put" these module and use them in 4.4.2?
Forum search just lead me to one post about it,
http://forum.xda-developers.com/showthread.php?t=2021437
Just one kernel, only one and it's for 4.2.2. Sadly i try it and nothing change : insmod cifs.ko / nfs.ko --> can't open......
Help, i just want to mount my nas, (sure i already setup my Nas to have a nfs directory for my nexus)
even my try with mount manager failed.
Need help
Also looking for a CIFS (or NFS) module on a 4.2.2 rom.
I believe that ak kernel in original development has it
Sent from my Nexus 4 using XDA Premium 4 mobile app