I haven't seen an NFS root, in this website http://ccc.ntu.edu.tw/index.php/en/news/40 I noticed some Linux images for the Galileo board, perhaps you can verify if one of them works for your project or you can try to customize your own image. Here some documents you can use to create your image.
Intel® BSP build guide
Also I saw this post https://communities.intel.com/thread/45350 some mentioned a NFS root image, not sure if you could check if he have some additional information about it.
Any idea of how implement CIFS support, I have it in the Arduino YUN and makes life easier moving files from one place to other.
Thanks in advance.
Ok, I see you have a dedicated thread for this, so let's better continue here than in the NTP package one.
So is it server or client you're interested in?
A CIFS/samba client, so I can move files on the network instead of using the SD card.
1 of 1 people found this helpful
try "mount.cifs" or "mount -t cifs" commands, looking at the BSP sources it seems like it may be included right away. If it's indeed there, you just need to specify proper command line parameters, if not, then it would require additional compilation.
Not too much luck yet, I tried on BusyBox v1.20.2 the command below and see the answer, I wonder now the syntax for the CIFS/Samba of mount command.
Thanks for your help.
PS: BTW the REPO site seems to be not working, just FYI.
root@Galileo1:~# mount -h
mount: invalid option -- h
BusyBox v1.20.2 (2013-10-01 00:17:01 IST) multi-call binary.
Usage: mount [OPTIONS] [-o OPTS] DEVICE NODE
root@Galileo1:~# mount -t cifs //192.168.1.11/Documents nas -o username=guest -vvv
mount: mount('//192.168.1.11/Documents','nas','cifs',0x00008000,'username=guest'):-1: No such device
mount: mounting //192.168.1.11/Documents on nas failed: No such device
The immediate reason is that the mountpoint you're trying to mount to ("nas") doesn't exist. Create it first (e.g. "mkdir /nas") and try again using "/nas" as the mountpoint.
The repo is fine, just checked. What's the exact error you get?
I am afraid that is other problem ... see the sequence of commands below ...
Thanks for your help and interest.
root@Galileo1:~# ls -l
drwxr-sr-x 2 root root 1024 Feb 21 10:27 nas
-rwxr-xr-x 1 root root 686 Feb 18 14:59 pyMailCheck.py
root@Galileo1:~# mount -t cifs //192.168.1.11/Documents /home/root/nas -o username=guest -vvv
mount: mount('//192.168.1.11/Documents','/home/root/nas','cifs',0x00008000,'username=guest'):-1: No such device
mount: mounting //192.168.1.11/Documents on /home/root/nas failed: No such device
root@Galileo1:~# mkdir /nas
root@Galileo1:~# mount -t cifs //192.168.1.11/Documents /nas -o username=guest -vvv
mount: mount('//192.168.1.11/Documents','/nas','cifs',0x00008000,'username=guest'):-1: No such device
mount: mounting //192.168.1.11/Documents on /nas failed: No such device
Okay, indeed, that's something else then. The next thing to check is whether the cifs kernel module is actually available on Galileo out of the box ... [checks kernel config in Galileo BSP] ... Okay, it's not enabled there, so you'd need to rebuild the kernel to get that. Or compile the samba package (provided it will compile without major hassle - I see it's in the meta-oe layer, but it's not built by default) and then use the smbclient utility (it doesn't require cifs support in kernel).
I don't have time available to do that for you, sorry. Though I can provide you with some initial instructions and help along the road, if you're willing to give it a try by yourself.
Alex - was there any additional progress on this one?
I'm now at the point where I want to mount a remote directory to facilitate code development
Nope, there wasn't. As you can see I've offered AlphaCHarly my help with going further with that, but I'm not ready (or personally interested, as of today too) to implement that by myself, so as long as no interested was expressed - that's not moved on.
I, too, am in desperate need of a CIFS implementation. I'm making a robot that takes a screenshot from a Windows PC (shared out via CIFS) and controls stepper motors to interact with it. I have tried FIVE configurations for my current project (requiring CIFS and OpenCV) and each have flaws:
- Raspberry Pi: Far too slow on OpenCV, not as good at robot control as Arduino.
- Beaglebone Black: Same disadvantages as Raspberry Pi.
- Arduino YUN: No OpenCV build available for it yet. Probably too slow in OpenCV.
- Intel Galileo: No CIFS support available. May be too slow in OpenCV but without CIFS I can't even test the files I am scanning.
- Some other Arduino and an Intel NUC i3: Fast and good robot control, but clunky, large, and very limited in how I can communicate between the two. Serial only.
I think I'll end up with the Intel NUC i3 do both the CIFS and OpenCV part, then send robot control commands to the Galileo via curl. That means the robot will have THREE computers: The i3 running Linux/OpenCV/file management, the Galileo running the robot, and the original computer providing the screenshots. An ugly solution, to be sure.
I've got the cifs kernel module working, tell me if you want to get the compiled kernel and/or instructions on how to get it built. As I've mentioned in your other thread, you just need to change the target name a bit to have your own build done, so you're very close to getting there on your own
I think I'll publish it right away in the devtools image: Collaborating to develop a "devtools" version of Linux which is Arduino IDE compatable
I've just published an update there, but CIFS can be a cool addition so I'll update it one more time
I'll also publish a recipe in my repo at GitHub (https://github.com/alext-mkrs/meta-alext-galileo) shortly.
If you want the "inside track" of the robot project before I finish and find a publisher for it, reach out to me via Email. I am "thoughtfix" everywhere online, including Gmail, Instructables, Thingiverse, and elsewhere. Let me know when cifs is added to the repo and I'll clone and compile it.