There was a fair bit of discussion on the orig CSOS project thread about
whether there should be a SAMBA server on the Wandboard, and how it
should be configured for the envisaged use cases: e.g.:

http://forums.slimdevices.com/showthread.php?99395-Community-Squeeze-OS-F19-Release-1/page125

http://forums.slimdevices.com/showthread.php?99395-Community-Squeeze-OS-F19-Release-1/page126

The idea of using the “VortexBox file share layout” was in favour for
quite a while, 

http://info.vortexbox.org/tiki-index.php?page=VortexBox+file+share+layout

but I don't know if that was the last word on the subject, or if it's
still relevant. 

I think you only need to share storage local to the Wandboard via SAMBA
to cater for  files on USB HDD, USB mem sticks, and possibly HDD
attached via SATA header.  

But will you cater for both the case where the local storage is already
formatted and loaded with audio files, and the case where the attached
local storage is blank and unformatted and the “VortexBox file share
layout” template, or something like it, can be generated on such media?

It would be  plus if the soa-aur project could be used on other devices
where additional SATA drives are easily attached.  I would also think it
would be best if any mount scheme adhered to the Linux Filesystem
Hierarchy where possible, which, for example,  begs the question as to
where a USB memory stick should be mounted and if/how to share it via
SAMBA. 

Do you need separate mount points for local and network mounts?  End
users don't care, they just want the simplest unambiguous way to store
and access their audio data: local or remote.   They see the webUI, and
don't care about the back end complexities.


------------------------------------------------------------------------
Krisbee's Profile: http://forums.slimdevices.com/member.php?userid=59080
View this thread: http://forums.slimdevices.com/showthread.php?t=101624

_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix

Reply via email to