Triode wrote: > Seems to me that copying Voxtexbox layout only works for people who are > familar with it and needs explaining to everyone else... So I am > thinking of going with /storage and /mnt/disk[1-6] with /storage > exported rw via samba. This is how CSOS was - does this work for > everyone? (or does no one care?)
You could do that, but I have two points: 1. The user, who for example, attaches a USB HDD to their Wandboard and wants to drag & drop files on to it via their network would have to know to use /storage and not /mnt/disk[1-6] 2. What happens if a user wishes to attach more than one USB HDD to their Wandboard? I have separate questions re: /mnt/disk[1-6] which relates to how people may have organised large audio file collections in order to make best use of LMS and for their own ease of maintenance. Let's say someone has organised their audio data on NAS something like this: /media/music/classical /media/music/jazz /media/music/blues /media/music/pop /media/music/ . etc. How do they mount this on their Wandboard? If they have more than six categories, they would have to mount top-level /media/music on one of the /mnt/diskX. So if they wanted to do maintenance on one part of their audio collection, they would have to umount the entire collection. Also, as a result of the /mnt/disk[1-6] scheme, the mount names and what you see as LMS folders are rather anonymous. For example, a network share like /media/music/classical turns into /mnt/disk1. Triode asked if there should be separate mount points for local and remote mounts, while the user shouldn't care, I think this does have several advantages from a design/usability viewpoint. For example, if there was a single mount in the system of remote mounts, called say /mnt/NAS or /mnt/NetShares, then the user just adds as many remote shares as they want (nfs or cifs) under this single point and a share like /media/music/classical would map to /mnt/NAS/classical, and /media/music/jazz would map to /mnt/NAS/jazz etc. You would then see meaningful folder names in LMS. Local external drives/partitions could be mounted under a single point in the same way, say under /mnt/local/, or even under /media. How to deal with attached USB memory sticks is an open question. This leaves the question of running a SAMBA server. I believe we only need to share locally attached storage. As soa-aur on Arch has no normal user, just root and system user jivelite, you could expose everything under /mnt/local/ with a samba config that has security = user and guest account = root. This would make all local data available as a public share fully rw. That may not be restrictive enough for some users. It should also be possible enabel/disable any SAMBA server via the soa-webUI. I think the current/proposed scheme ( /mnt/disk[1-6] + /storage ) has a number of limitations, and if the project wishes to progress from the developer stage and has any ambitions to be usable on a variety devices, and not just the Wandboard, then I think it's worth the effort of getting the soa-web storage functions into better shape. ------------------------------------------------------------------------ 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
