Core - Revision history

Mcefan: /* Centralized configuration and administration */

2016-02-24T04:17:29Z

Centralized configuration and administration

←Older revision		Revision as of 04:17, 24 February 2016
Line 40:		Line 40:
	In a LinuxMCE system, all the settings are stored in the Core Server. Each system component's location, functions, and options are stored on the Core. Every device's configuration, and, all network settings are also stored on the Core.		In a LinuxMCE system, all the settings are stored in the Core Server. Each system component's location, functions, and options are stored on the Core. Every device's configuration, and, all network settings are also stored on the Core.

	::For example, the [[AV devices]] are connected to the Media Director(s)~~, nevertheless~~, [[AV devices]] connected anywhere within the system, even those connected to another (such as a [[Media Director]] PC) in another part of the house are all managed by the Core. In the [[LinuxMCE Admin Website\|LinuxMCE Admin]] panel, A/V devices settings are specified separately from the settings of the Media Directors to which they are connected. This is done because the Core keeps track of the controls and settings for each individual device in the system.		::For example, even though the [[AV devices]] are connected to the Media Director(s), [[AV devices]] connected anywhere within the system, even those connected to another (such as a [[Media Director]] PC) in another part of the house are all managed by the Core. In the [[LinuxMCE Admin Website\|LinuxMCE Admin]] panel, A/V devices settings are specified separately from the settings of the Media Directors to which they are connected. This is done because the Core keeps track of the controls and settings for each individual device in the system.


Line 50:		Line 50:
	All the devices part of the LinuxMCE network are listed and configured on the Core. The Core Server provides a standardized administration website accessible via web browser from any Media Director or other device connected to the LinuxMCE network. The [[LinuxMCE Admin Website]] is the interface used to configure the LinuxMCE system.		All the devices part of the LinuxMCE network are listed and configured on the Core. The Core Server provides a standardized administration website accessible via web browser from any Media Director or other device connected to the LinuxMCE network. The [[LinuxMCE Admin Website]] is the interface used to configure the LinuxMCE system.

	Since the entire system can be administered from any Media Director, ~~and~~ you can run the Core Server without a monitor, keyboard, mouse or any other input or output device if you choose to do so. It is a true server. In this configuration, the server is said to be running "headless".		Since the entire system can be administered from any Media Director, you can run the Core Server without a monitor, keyboard, mouse or any other input or output device if you choose to do so. It is a true server. In this configuration, the server is said to be running "headless".

	{{p}}		{{p}}

Mcefan: /* Configurations repository */

2016-02-24T03:48:14Z

Configurations repository

←Older revision		Revision as of 03:48, 24 February 2016
Line 40:		Line 40:
	In a LinuxMCE system, all the settings are stored in the Core Server. Each system component's location, functions, and options are stored on the Core. Every device's configuration, and, all network settings are also stored on the Core.		In a LinuxMCE system, all the settings are stored in the Core Server. Each system component's location, functions, and options are stored on the Core. Every device's configuration, and, all network settings are also stored on the Core.

	::For example, the [[AV devices]] are connected to the Media Director(s), nevertheless, [[AV devices]] connected anywhere within the system, even those connected to another (such as a [[Media Director]] PC) in another part of the house are all managed by the Core. In the [[LinuxMCE Admin Website\|LinuxMCE Admin]] panel, A/V devices settings are specified separately from the settings of the Media Directors to which they are connected. This is done because the Core ~~individually~~ keeps track of the controls and settings ~~of every~~ device on the system.		::For example, the [[AV devices]] are connected to the Media Director(s), nevertheless, [[AV devices]] connected anywhere within the system, even those connected to another (such as a [[Media Director]] PC) in another part of the house are all managed by the Core. In the [[LinuxMCE Admin Website\|LinuxMCE Admin]] panel, A/V devices settings are specified separately from the settings of the Media Directors to which they are connected. This is done because the Core keeps track of the controls and settings for each individual device in the system.

Mcefan: /* Communications hub */

2016-02-24T02:46:11Z

Communications hub

←Older revision		Revision as of 02:46, 24 February 2016
Line 30:		Line 30:

	The LinuxMCE Core is also at the center of communications on the network. New users commonly misunderstand this role and attempt to install LinuxMCE as "just another component" of their existing network. However, the LinuxMCE Core does not only route home automation messages and commands between components, but also distributes IP addresses, delivers boot images, and serves as the gateway to the Internet for the system components. The LinuxMCE Core functions as the network's router. <br>		The LinuxMCE Core is also at the center of communications on the network. New users commonly misunderstand this role and attempt to install LinuxMCE as "just another component" of their existing network. However, the LinuxMCE Core does not only route home automation messages and commands between components, but also distributes IP addresses, delivers boot images, and serves as the gateway to the Internet for the system components. The LinuxMCE Core functions as the network's router. <br>
	To install LinuxMCE on an existing network, it has to be ~~added as node on~~ the existing network, but the LinuxMCE system components have to be added to the LinuxMCE Core's internal network, essentially creating two distinct networks. It then becomes your responsibility to join the two networks as necessary if you would like to interact with the LinuxMCE system components from the external network. In general, LinuxMCE Core is used as the router and gateway of the network to which the access points are connected, and the pre-existing router/gateway is placed outside the network (essentially used as a bridge to the Internet).<br>		Though it is possible to install LinuxMCE on an existing network, the Core has to be the gateway for the {{l}} system. It can join the existing network as a node, but the LinuxMCE system components have to be added to the LinuxMCE Core's internal network, essentially creating two distinct networks. It then becomes your responsibility to join the two networks as necessary if you would like to interact with the LinuxMCE system components from the external network. In general, LinuxMCE Core is used as the router and gateway of the network to which the access points are connected, and the pre-existing router/gateway is placed outside the network (essentially used as a bridge to the Internet).<br>
	To learn more about LinuxMCE networking role, network cabling and configuration, see [[Why dual network cards?]].		To learn more about LinuxMCE networking role, network cabling and configuration, see [[Why dual network cards?]].

Mcefan: /* Core PC hardware selection guide */

2014-12-17T03:56:55Z

Core PC hardware selection guide

←Older revision		Revision as of 03:56, 17 December 2014
Line 76:		Line 76:
	== Core PC hardware selection guide ==		== Core PC hardware selection guide ==
	To learn about the PC components necessary in a Core, read the [[Core - Hardware selection primer]]		To learn about the PC components necessary in a Core, read the [[Core - Hardware selection primer]]

			{{p}}

			==Links==
			* [[User Manual#Composition of a LinuxMCE system\|Learn about the other LinuxMCE system components]]

	{{p}}		{{p}}

Mcefan: /* The LinuxMCE Core server */

2014-12-16T18:17:45Z

The LinuxMCE Core server

←Older revision		Revision as of 18:17, 16 December 2014
Line 13:		Line 13:
	* a multiprotocol router		* a multiprotocol router
	::- a communications hub for all connected devices: it routes home automation messages and commands.		::- a communications hub for all connected devices: it routes home automation messages and commands.
	::- the networking [[Why dual network cards? \|router of the multimedia network]]		::- the networking [[Why dual network cards? \|router of the home automation/multimedia network]]
	::- a PBX for all connected IP telephony devices and media directors		::- a PBX for all connected IP telephony devices and media directors

Mcefan: /* Centralized administration */

2014-12-16T18:10:38Z

Centralized administration

←Older revision		Revision as of 18:10, 16 December 2014
Line 50:		Line 50:
	All the devices part of the LinuxMCE network are listed and configured on the Core. The Core Server provides a standardized administration website accessible via web browser from any Media Director or other device connected to the LinuxMCE network. The [[LinuxMCE Admin Website]] is the interface used to configure the LinuxMCE system.		All the devices part of the LinuxMCE network are listed and configured on the Core. The Core Server provides a standardized administration website accessible via web browser from any Media Director or other device connected to the LinuxMCE network. The [[LinuxMCE Admin Website]] is the interface used to configure the LinuxMCE system.

	Since the entire system can be administered from any Media Director, and you can run the Core Server without a monitor, keyboard, mouse or any other input or output device if you choose to do so. It is a true server. In this configuration, the server is said to be running "~~'''[[~~headless~~]]'''~~".		Since the entire system can be administered from any Media Director, and you can run the Core Server without a monitor, keyboard, mouse or any other input or output device if you choose to do so. It is a true server. In this configuration, the server is said to be running "headless".

	{{p}}		{{p}}

Mcefan: /* Configurations repository */

2014-12-16T18:03:54Z

Configurations repository

←Older revision		Revision as of 18:03, 16 December 2014
Line 43:		Line 43:


	This centralization of settings enables plug-and-play operation throughout the LinuxMCE system. All devices connected anywhere within the system are automatically configurable once discovered by the LinuxMCE Core.		This centralization of settings enables [[#Plug 'n' Play Capabilities\|plug-and-play operation]] throughout the LinuxMCE system. All devices connected anywhere within the system are automatically configurable once discovered by the LinuxMCE Core.

	{{p}}		{{p}}

Mcefan: /* Centralized administration */

2014-12-16T17:57:11Z

Centralized administration

←Older revision		Revision as of 17:57, 16 December 2014
Line 48:		Line 48:

	==== Centralized administration ====		==== Centralized administration ====
	All the devices part of the LinuxMCE network are listed and configured on the Core. The Core Server provides a standardized ~~[[LinuxMCE Admin Website\|Administration Website]]~~ accessible via web browser from any Media Director or other device connected to the LinuxMCE network. The [[LinuxMCE Admin Website]] is the interface used to configure the LinuxMCE system.		All the devices part of the LinuxMCE network are listed and configured on the Core. The Core Server provides a standardized administration website accessible via web browser from any Media Director or other device connected to the LinuxMCE network. The [[LinuxMCE Admin Website]] is the interface used to configure the LinuxMCE system.

	Since the entire system can be administered from any Media Director, and you can run the Core Server without a monitor, keyboard, mouse or any other input or output device if you choose to do so. It is a true server. In this configuration, the server is said to be running "'''[[headless]]'''".		Since the entire system can be administered from any Media Director, and you can run the Core Server without a monitor, keyboard, mouse or any other input or output device if you choose to do so. It is a true server. In this configuration, the server is said to be running "'''[[headless]]'''".

Mcefan: /* Central repository: centralized configuration and administration */

2014-12-16T17:56:18Z

Central repository: centralized configuration and administration

←Older revision		Revision as of 17:56, 16 December 2014
Line 35:		Line 35:
	{{p}}		{{p}}

	== ~~Central repository: centralized~~ configuration and administration ==		== Centralized configuration and administration ==

	==== Configurations repository====		==== Configurations repository ====
	In a LinuxMCE system, all the settings are stored in the Core Server. Each system component's location, functions, and options are stored on the Core. Every device's configuration, and, all network settings are also stored on the Core.		In a LinuxMCE system, all the settings are stored in the Core Server. Each system component's location, functions, and options are stored on the Core. Every device's configuration, and, all network settings are also stored on the Core.

Line 47:		Line 47:
	{{p}}		{{p}}

	==== ~~Administration~~ ====		==== Centralized administration ====
	The Core Server provides a standardized [[LinuxMCE Admin Website]] accessible via web browser from any Media Director or other device connected to the LinuxMCE network. ~~Since all devices part of~~ the LinuxMCE ~~network are listed and configured on the Core,~~ the entire system can be administered from any Media Director, and you can run the Core Server without a monitor, keyboard, mouse or any other input or output device if you choose to do so. It is a true server. In this configuration, the server is said to be running "'''[[headless]]'''".		All the devices part of the LinuxMCE network are listed and configured on the Core. The Core Server provides a standardized [[LinuxMCE Admin Website\|Administration Website]] accessible via web browser from any Media Director or other device connected to the LinuxMCE network. The [[LinuxMCE Admin Website]] is the interface used to configure the LinuxMCE system.

			Since the entire system can be administered from any Media Director, and you can run the Core Server without a monitor, keyboard, mouse or any other input or output device if you choose to do so. It is a true server. In this configuration, the server is said to be running "'''[[headless]]'''".

	{{p}}		{{p}}

Mcefan: /* Administration */

2014-12-16T17:47:04Z

Administration

←Older revision		Revision as of 17:47, 16 December 2014
Line 48:		Line 48:

	==== Administration ====		==== Administration ====
	The Core Server provides a standardized [[LinuxMCE Admin Website]] accessible via web browser from any Media Director. Since all devices part of the LinuxMCE network are listed and configured on the Core, the entire system can be administered from any Media Director, and you can run the Core Server without a monitor, keyboard, mouse or any other input or output device if you choose to do so. It is a true server. In this configuration, the server is said to be running "'''[[headless]]'''".		The Core Server provides a standardized [[LinuxMCE Admin Website]] accessible via web browser from any Media Director or other device connected to the LinuxMCE network. Since all devices part of the LinuxMCE network are listed and configured on the Core, the entire system can be administered from any Media Director, and you can run the Core Server without a monitor, keyboard, mouse or any other input or output device if you choose to do so. It is a true server. In this configuration, the server is said to be running "'''[[headless]]'''".

	{{p}}		{{p}}