Howto: Using Network Shares - Revision history

Mcefan at 15:19, 19 October 2012

2012-10-19T15:19:30Z

←Older revision		Revision as of 15:19, 19 October 2012
Line 3:		Line 3:
	\| __TOC__		\| __TOC__
	\|}		\|}
	[[Category: ~~Tutorials]]~~		[[Category:Networking]]
	~~[[Category:Network_Tutorials~~]]
	[[Category: Network Attached Storage]]		[[Category: Network Attached Storage]]

PlatypusPedersen: /* Network Share Using LinuxMCE's Directory Structure */ added "data" folder in the dir tree

2012-08-12T19:33:35Z

Network Share Using LinuxMCE's Directory Structure: added "data" folder in the dir tree

←Older revision		Revision as of 19:33, 12 August 2012
Line 24:		Line 24:
	For a typical Windows share, the storage layout will look like this:		For a typical Windows share, the storage layout will look like this:

	my_share\public\audio		my_share\public\data\audio
	my_share\public\documents		my_share\public\data\documents
	my_share\public\pictures		my_share\public\data\pictures
	my_share\public\videos		my_share\public\data\videos
	my_share\<user_1>\audio		my_share\<user_1>\data\audio
	my_share\<user_1>\documents		my_share\<user_1>\data\documents
	my_share\<user_1>\pictures		my_share\<user_1>\data\pictures
	my_share\<user_1>\videos		my_share\<user_1>\data\videos

	=== Network Share As a Simple Storage Device ===		=== Network Share As a Simple Storage Device ===

PlatypusPedersen: added Category:Network Tutorials

2011-11-27T14:42:06Z

added Category:Network Tutorials

←Older revision		Revision as of 14:42, 27 November 2011
Line 4:		Line 4:
	\|}		\|}
	[[Category: Tutorials]]		[[Category: Tutorials]]
			[[Category:Network_Tutorials]]
	[[Category: Network Attached Storage]]		[[Category: Network Attached Storage]]

Dan249 at 18:21, 4 June 2011

2011-06-04T18:21:45Z

←Older revision		Revision as of 18:21, 4 June 2011
Line 10:		Line 10:
	== Network Share Use ==		== Network Share Use ==

	Network shares are accessed in LinuxMCE using ~~synbolic~~ links created in the media storage directories, either in ''/home/public/data'' in the case of public shares, or in ''/home/<user_name>/data'' if the share has been assigned to a user.		Network shares are accessed in LinuxMCE using symbolic links created in the media storage directories, either in ''/home/public/data'' in the case of public shares, or in ''/home/<user_name>/data'' if the share has been assigned to a user.

	LinuxMCE offers two alternatives for use of network shares:		LinuxMCE offers two alternatives for use of network shares:
Line 60:		Line 60:
	# For each available file share on your new file server, the orbiter will display the share name and ask what you would like to do with it. The list will contain a single option - either ''Windows Share'' or ''NFS Share''. Click this option.		# For each available file share on your new file server, the orbiter will display the share name and ask what you would like to do with it. The list will contain a single option - either ''Windows Share'' or ''NFS Share''. Click this option.
	# The orbiter will ask if the new storage device can be used automatically for storing media. If you select ''Yes'', LinuxMCE will store ripped CDs and DVDs and recorded TV shows on this device.		# The orbiter will ask if the new storage device can be used automatically for storing media. If you select ''Yes'', LinuxMCE will store ripped CDs and DVDs and recorded TV shows on this device.
	# The next orbiter screen will ask ~~allow~~ you to select if you would like to use LinuxMCE's directory structure on the new storage device. You have three options:		# The next orbiter screen will ask you to select if you would like to use LinuxMCE's directory structure on the new storage device. You have three options:
	## Use LinuxMCE's directory structure		## Use LinuxMCE's directory structure
	## Access the device content as-is and make it public		## Access the device content as-is and make it public

Wierdbeard65 at 08:39, 5 May 2010

2010-05-05T08:39:01Z

←Older revision		Revision as of 08:39, 5 May 2010
Line 1:		Line 1:
			{{versioninfo}}
	{\| align="right"		{\| align="right"
	\| __TOC__		\| __TOC__

Ray N: /* Manual Creation of Network Shares */

2009-03-24T22:33:01Z

Manual Creation of Network Shares

←Older revision		Revision as of 22:33, 24 March 2009
Line 102:		Line 102:
	# Click ''Pick device template''.		# Click ''Pick device template''.
	# In the ''Device Template'' menu select the appropriate share type for your file server.		# In the ''Device Template'' menu select the appropriate share type for your file server.
			# Click ''Pick device template'' to select and close the window.
	# In the ''Device data'' area, fill in:		# In the ''Device data'' area, fill in:
	## '''PK_Users''': Leave empty for a public share, or select the desired user [Starting with 0710, select "''Public''", "''Pluto's structure''", or a user name. "''Public''" will mount under data/other.]		## '''PK_Users''': Leave empty for a public share, or select the desired user [Starting with 0710, select "''Public''", "''Pluto's structure''", or a user name. "''Public''" will mount under data/other.]

Royw: /* Manual Creation of Network Shares */

2008-04-24T23:03:28Z

Manual Creation of Network Shares

←Older revision		Revision as of 23:03, 24 April 2008
Line 103:		Line 103:
	# In the ''Device Template'' menu select the appropriate share type for your file server.		# In the ''Device Template'' menu select the appropriate share type for your file server.
	# In the ''Device data'' area, fill in:		# In the ''Device data'' area, fill in:
	## '''PK_Users''': Leave empty for a public share, or select the desired user		## '''PK_Users''': Leave empty for a public share, or select the desired user [Starting with 0710, select "''Public''", "''Pluto's structure''", or a user name. "''Public''" will mount under data/other.]
	## '''Share Name''' (if the share is \\my_server\my_share, enter ''my_share'')		## '''Share Name''' (if the share is \\my_server\my_share, enter ''my_share'')
	## '''Filesystem''': ''cifs'' for Windows shares, ''nfs'' for *nix shares		## '''Filesystem''': ''cifs'' for Windows shares, ''nfs'' for *nix shares

Royw: /* NFS Server Hints */

2008-04-23T08:00:43Z

NFS Server Hints

←Older revision		Revision as of 08:00, 23 April 2008
Line 131:		Line 131:

	Ownership in your share of media files should be: root:public (0:1002) and permissions should be set to 2775 (rwxrwsr-x)		Ownership in your share of media files should be: root:public (0:1002) and permissions should be set to 2775 (rwxrwsr-x)

			You may need to change a groupid if another group is already using 1002. The process will vary depending on your system, but here are the general steps:
			# examine /etc/groups and find an unused group id to move the conflicting group to. This example will use 1234 for the new group id.
			# find all files with that currently have 1002 groupid: find / -group 1002 -print
			#* if it's just a few files then you can change their group id with: chgrp 1234 filename
			#* if it's a lot of files, then you might prefer using the find command: find / -group 1002 -exec chgrp 1234 '{}' \;
			# now double check that you changed all the files with group id 1002: find / -group 1002 -print
			# edit /etc/groups and change the group id for the conflicting group from 1002 to the new group id (1234 in this example)
			# while editing /etc/groups, edit or add the public group with a group id of 1002
			# save /etc/groups
			# if the conflicting group was for a service, then restart the service.
			# if the service was one of the critical service (mine was hald), I'd go ahead and reboot the box.

Royw: /* Advanced Configuration Options */

2008-02-08T08:12:56Z

Advanced Configuration Options

←Older revision		Revision as of 08:12, 8 February 2008
Line 119:		Line 119:
	* '''Directories''': When a share is configured to use LinuxMCE's directory structure, it will by default be used in all media directories: ''audio, documents, pictures'' and ''videos''. You can restrict which media directories will be used by entering their names in this field, separated by commas.		* '''Directories''': When a share is configured to use LinuxMCE's directory structure, it will by default be used in all media directories: ''audio, documents, pictures'' and ''videos''. You can restrict which media directories will be used by entering their names in this field, separated by commas.
	* '''Readonly''': checking this option will make LinuxMCE mount the share as read-only. This will stop LinuxMCE from creating .id3 files for all your videos, and from modifying the MP3 tags of your music files.		* '''Readonly''': checking this option will make LinuxMCE mount the share as read-only. This will stop LinuxMCE from creating .id3 files for all your videos, and from modifying the MP3 tags of your music files.

			== NFS Server Hints ==

			If you are wanting to have a linux system be your server, here are a few hints.

			As of 0710 beta 3, LinuxMCE requires your sever to be very open (insecure). You must allow root access to the share as LinuxMCE writes files as root:public.

			So on the server to share /var/media, assuming your core is at 192.168.80.1, you need to add your share to the /etc/exports like:

			/var/media/ 192.168.80.1(async,no_subtree_check,rw,no_root_squash)

			Ownership in your share of media files should be: root:public (0:1002) and permissions should be set to 2775 (rwxrwsr-x)

Rwilson131 at 04:35, 3 November 2007

2007-11-03T04:35:10Z

←Older revision		Revision as of 04:35, 3 November 2007
Line 1:		Line 1:
			{\| align="right"
			\| __TOC__
			\|}
	[[Category: Tutorials]]		[[Category: Tutorials]]
	[[Category: Network Attached Storage\| ]]		[[Category: Network Attached Storage]]

	The LinuxMCE core is able to auto-detect, configure and use Windows (SMB or CIFS) and *nix (NFS) network shares. This document details the different options for using network shares in LinuxMCE and the actions required to successfully configure them, when the automated discovery processes fail.		The LinuxMCE core is able to auto-detect, configure and use Windows (SMB or CIFS) and *nix (NFS) network shares. This document details the different options for using network shares in LinuxMCE and the actions required to successfully configure them, when the automated discovery processes fail.