2016-02-18, 23:19
Hi Milhouse
Thanks for quick reply. Let me apologize for the Linux-n00b exercise in advance...
mkdir = successful, but I'm stuck on the mount command (...let me count the hours )
The operation fails with either this:
or - in desperation - this:
In the second case (ie: using explicit IP address) the device is recognized alright, but I can't tell what "Invalid arguement" is actually complaining about.
I'm curious why it's necessary to use the UNAME and PWORD options... IF permissions on the FreeNAS box are open (yeah, I know... next project). Kodi has full control of "media", and so presumably the scripts running on the Kodi box will have the same authority. Is that view too simple ?
Thanks.
Thanks for quick reply. Let me apologize for the Linux-n00b exercise in advance...
mkdir = successful, but I'm stuck on the mount command (...let me count the hours )
The operation fails with either this:
Code:
OpenELEC:~ # mount -t cifs -o username=*****,password=*****,sec=ntlm //FREENAS/media /storage/media
mount: bad address 'FREENAS'
mount: mounting //FREENAS/media on /storage/media failed
or - in desperation - this:
Code:
OpenELEC:~ # mount -t cifs //192.168.1.175/media/ -o username=*****,password=*****,sec=ntlm /storage/media
mount: mounting //192.168.1.175/media/ on /storage/media failed: Invalid argument
In the second case (ie: using explicit IP address) the device is recognized alright, but I can't tell what "Invalid arguement" is actually complaining about.
I'm curious why it's necessary to use the UNAME and PWORD options... IF permissions on the FreeNAS box are open (yeah, I know... next project). Kodi has full control of "media", and so presumably the scripts running on the Kodi box will have the same authority. Is that view too simple ?
Thanks.