Architecture Intro - Revision history

Chris Caven: /* LinuxMCE and DHCP */

2010-02-08T15:58:13Z

LinuxMCE and DHCP

←Older revision		Revision as of 15:58, 8 February 2010
Line 27:		Line 27:
	If you choose the nested "network within a network" configuration, the LinuxMCE Core will act as the DHCP router for the "internal" automation/multimedia network only. Your existing router would still handle DHCP functions for the "external" home LAN.		If you choose the nested "network within a network" configuration, the LinuxMCE Core will act as the DHCP router for the "internal" automation/multimedia network only. Your existing router would still handle DHCP functions for the "external" home LAN.

	The easiest way to do this is to have 2 network cards (NICs) in the PC that will be the LinuxMCE Core. One NIC would connect to the external network (the home router, or perhaps directly to a cable or DSL modem) and gets an IP address from the DHCP of your home router or ISP provider. The other NIC would connect to your "internal" LinuxMCE automation/multimedia LAN (through a switch or a router with the DHCP disabled). All your other ~~PC's~~ and devices ''within'' your LinuxMCE automation/multimedia LAN connect to the switch (or the DHCP-disabled router) and therefore use the Core as the DHCP server.		The easiest way to do this is to have 2 network cards (NICs) in the PC that will be the LinuxMCE Core. One NIC would connect to the external network (the home router, or perhaps directly to a cable or DSL modem) and gets an IP address from the DHCP of your home router or ISP provider. The other NIC would connect to your "internal" LinuxMCE automation/multimedia LAN (through a switch or a router with the DHCP disabled). All your other PCs and devices ''within'' your LinuxMCE automation/multimedia LAN connect to the switch (or the DHCP-disabled router) and therefore use the Core as the DHCP server.

	This is the default configuration that the LinuxMCE installer expects by default. This is the configuration recommended if you aren't experienced with networking.		This is the default configuration that the LinuxMCE installer expects by default. This is the configuration recommended if you aren't experienced with networking.
Line 33:		Line 33:
	In some situations it is possible for the Core to get by with a single network card (NIC), but it is not recommended. For example, if your home has a static, unchanging IP address assigned by your cable or DSL provider, and every device in your home LAN will also be part of your home automation/multimedia LAN, then you will only need one network card. The Core will be the DHCP server for your entire LAN.		In some situations it is possible for the Core to get by with a single network card (NIC), but it is not recommended. For example, if your home has a static, unchanging IP address assigned by your cable or DSL provider, and every device in your home LAN will also be part of your home automation/multimedia LAN, then you will only need one network card. The Core will be the DHCP server for your entire LAN.

	In the rare instance when you will have a single PC acting as a hybrid Core/Media Director and do not plan to have any additional devices (i.e. you don't have a home LAN at all), then the Core does not need to be configured to provide DHCP. In this scenario, one PC would act as an standalone Home Theater PC. None of the network capabilites of LinuxMCE would be available.		In the rare instance when you will have a single PC acting as a hybrid Core/Media Director and do not plan to have any additional devices (i.e. you don't have a home LAN at all), then the Core does not need to be configured to provide DHCP. In this scenario, one PC would act as a standalone Home Theater PC. None of the network capabilites of LinuxMCE would be available.

	The [[Usage Intro]] explains the concepts about how to use LinuxMCE.		The [[Usage Intro]] explains the concepts about how to use LinuxMCE.

	[[Category:Documentation\| ]]		[[Category:Documentation\| ]]

Chris Caven: /* Orbiters */

2010-02-08T15:52:06Z

Orbiters

←Older revision		Revision as of 15:52, 8 February 2010
Line 16:		Line 16:

	==Orbiters==		==Orbiters==
	'''[[Orbiters]]''' are the control interfaces, or remote controls, for the system. Each Media Director has an on-screen Orbiter user interface. In addition, multiple devices, such as a Nokia Internet Tablet ~~(n810)~~, web enabled equipment, or mobile phones can be used as Orbiters. The Orbiter User Interface (stored on and accessed from the Core) can also be accessed from any web browser.		'''[[Orbiters]]''' are the control interfaces, or remote controls, for the system. Each Media Director has an on-screen Orbiter user interface. In addition, multiple devices, such as a Nokia Internet Tablet N810, web-enabled equipment, or mobile phones can be used as Orbiters. The Orbiter User Interface (stored on and accessed from the Core) can also be accessed from any web browser.

	==LinuxMCE and DHCP==		==LinuxMCE and DHCP==

Chris Caven: /* Media Directors */

2010-02-08T15:49:44Z

Media Directors

←Older revision		Revision as of 15:49, 8 February 2010
Line 5:		Line 5:

	==Media Directors==		==Media Directors==
	A '''[[Media Directors \| Media Director]]''' (aka a Media Station) is connected to your TV. It is a PC running LinuxMCE, but you do not need to install any software on a Media Director as long as you enable the Media Director to ''[[netboot]]'' LinuxMCE from the Core server. (Network booting is a capability that almost all PCs have. Through the BIOS setup on any PC, netboot can be enabled as the first bootup device. When this setting is chosen and the PC is rebooted, the PC will search the network for a boot image and boots that image as its OS (rather than the OS on the hard drive).) In a LinuxMCE network, the Core provides the boot image over the network. The local PC that functions as a Media Director is essentially a thin client to the Core. (You can leave Windows, Fedora, or any other operating system you want on your PC's hard drive. When you want to use that PC as a LinuxMCE Media Director, enable netboot in the BIOS. When you want to use the OS that is stored on that PC's hard drive, reset the BIOS so that the hard drive is again the first boot device. (You can't do both at the same time.)) When LinuxMCE netboots, the software will not interfere with the software or operating system on the hard drive; it's like having 2 systems in one. You only have to install LinuxMCE software on one PC, the Core, and you can then have thin client Media Stations on PCs throughout the house. The whole process is fully automated and plug and play (whether or not you understand the concept of a netboot). The only technical thing you need to do is turn on netboot in the BIOS of a PC you want to use as a Media Director. Your PC manufacturer instructions should tell you how to change the BIOS settings.		A '''[[Media Directors \| Media Director]]''' (aka a Media Station) is connected to your TV. It is a PC running LinuxMCE, but you do not need to install any software on a Media Director, as long as you enable the Media Director to ''[[netboot]]'' LinuxMCE from the Core server.

	It is possible for the PC that functions as the LinuxMCE Core to also function as a Media Director. This is known as a [[hybrid]], and it can be used as a standalone Home Theater solution. Later, you can add other Media Directors (using the netboot method described above). A hybrid, like a standalone Core, will provide netboot images across a network. The UI (user interface) on all Media Directors looks exactly the same as the UI on the hybrid Core/Media Director. The hybrid should not be shut down, either, since it is acting as a Core. If you do, all the other Media Directors will stop working.		Network booting is a capability that almost all PCs have. Through the BIOS setup on any PC, netboot can be enabled as the first bootup device. When this setting is chosen and the PC is rebooted, the PC will search the network for a boot image and boots that image as its OS (rather than the OS on the hard drive). In a LinuxMCE network, the Core provides the boot image over the network.

			The local PC that functions as a Media Director is essentially a thin client to the Core. You can leave Windows, Fedora, or any other operating system you want on your PC's hard drive. When you want to use that PC as a LinuxMCE Media Director, enable netboot in the BIOS. When you want to use the OS that is stored on that PC's hard drive, reset the BIOS so that the hard drive is again the first boot device. (You can't do both at the same time.)

			When LinuxMCE netboots, the software will not interfere with the software or operating system on the hard drive; it's like having 2 systems in one. You only have to install LinuxMCE software on one PC -- the Core -- and you can then have thin client Media Stations on PCs throughout the house. The whole process is fully automated and plug and play (whether or not you understand the concept of a netboot). The only technical thing you need to do is turn on netboot in the BIOS of a PC you want to use as a Media Director. Your PC manufacturer instructions should tell you how to change the BIOS settings.

			It is possible for the PC that functions as the LinuxMCE Core to also function as a Media Director. This is known as a [[hybrid]], and it can be used as a standalone Home Theater solution. Later, you can add other Media Directors (using the netboot method described above). A hybrid, like a standalone Core, will provide netboot images across a network. The UI (user interface) on all Media Directors looks exactly the same as the UI on the hybrid Core/Media Director. The hybrid should not be shut down, either, since it is acting as a Core. If you do, all the other Media Directors will stop working.

	==Orbiters==		==Orbiters==

Chris Caven: /* The Core */

2010-02-08T15:35:31Z

The Core

←Older revision		Revision as of 15:35, 8 February 2010
Line 2:		Line 2:

	==The Core==		==The Core==
	The '''[[Core]]''' has no user interface other than an [[LinuxMCE Admin Website\|administration page]] (unless it is a [[hybrid]]). It provides processing services throughout the home, however. It acts as the central database that catalogues your media. It routes home automation messages and commands, and provides net boot images for the [[Media Directors~~\|Media Stations~~]]. It can even act as your phone system. You only have one Core in the house because it is the central point through which all devices connect. Your Core is generally left on all the time. If it is turned off, LinuxMCE functionality everywhere else in the home stops working.		The '''[[Core]]''' has no user interface other than an [[LinuxMCE Admin Website\|administration page]] (unless it is a [[hybrid]]). It provides processing services throughout the home, however. It acts as the central database that catalogues your media. It routes home automation messages and commands, and provides net boot images for the [[Media Directors]]. It can even act as your phone system. You only have one Core in the house because it is the central point through which all devices connect. Your Core is generally left on all the time. If it is turned off, LinuxMCE functionality everywhere else in the home stops working.

	==Media Directors==		==Media Directors==

Ray N at 22:43, 12 August 2009

2009-08-12T22:43:14Z

←Older revision		Revision as of 22:43, 12 August 2009
Line 31:		Line 31:
	The [[Usage Intro]] explains the concepts about how to use LinuxMCE.		The [[Usage Intro]] explains the concepts about how to use LinuxMCE.

	[[Category:~~Hardware~~\| ]]		[[Category:Documentation\| ]]

Perspectoff: /* Orbiters */

2008-07-02T06:36:04Z

Orbiters

←Older revision		Revision as of 06:36, 2 July 2008
Line 10:		Line 10:

	==Orbiters==		==Orbiters==
	'''[[Orbiters]]''' are the control interfaces, or remote controls, for the system. Each Media Director has an on-screen Orbiter user interface. In addition, multiple devices, such as a Nokia Internet Tablet (n810), web enabled equipment, or mobile phones, can be used as Orbiters. The Orbiter User Interface (stored on and accessed from the Core) can also be accessed ~~through~~ any web browser.		'''[[Orbiters]]''' are the control interfaces, or remote controls, for the system. Each Media Director has an on-screen Orbiter user interface. In addition, multiple devices, such as a Nokia Internet Tablet (n810), web enabled equipment, or mobile phones can be used as Orbiters. The Orbiter User Interface (stored on and accessed from the Core) can also be accessed from any web browser.

	==LinuxMCE and DHCP==		==LinuxMCE and DHCP==

Perspectoff at 06:35, 2 July 2008

2008-07-02T06:35:24Z

←Older revision		Revision as of 06:35, 2 July 2008
Line 8:		Line 8:

	It is possible for the PC that functions as the LinuxMCE Core to also function as a Media Director. This is known as a [[hybrid]], and it can be used as a standalone Home Theater solution. Later, you can add other Media Directors (using the netboot method described above). A hybrid, like a standalone Core, will provide netboot images across a network. The UI (user interface) on all Media Directors looks exactly the same as the UI on the hybrid Core/Media Director. The hybrid should not be shut down, either, since it is acting as a Core. If you do, all the other Media Directors will stop working.		It is possible for the PC that functions as the LinuxMCE Core to also function as a Media Director. This is known as a [[hybrid]], and it can be used as a standalone Home Theater solution. Later, you can add other Media Directors (using the netboot method described above). A hybrid, like a standalone Core, will provide netboot images across a network. The UI (user interface) on all Media Directors looks exactly the same as the UI on the hybrid Core/Media Director. The hybrid should not be shut down, either, since it is acting as a Core. If you do, all the other Media Directors will stop working.

			==Orbiters==
			'''[[Orbiters]]''' are the control interfaces, or remote controls, for the system. Each Media Director has an on-screen Orbiter user interface. In addition, multiple devices, such as a Nokia Internet Tablet (n810), web enabled equipment, or mobile phones, can be used as Orbiters. The Orbiter User Interface (stored on and accessed from the Core) can also be accessed through any web browser.

	==LinuxMCE and DHCP==		==LinuxMCE and DHCP==

Perspectoff: Undo revision 14599 by Posde (Talk)

2008-07-02T06:30:56Z

Undo revision 14599 by Posde (Talk)

←Older revision		Revision as of 06:30, 2 July 2008
Line 1:		Line 1:
	LinuxMCE is divided in ~~three~~ parts: the '''Core''' (aka the backend~~),the '''Orbiter''' (aka the frontend~~) and the '''Media Director''' (aka the ~~media interface~~).		LinuxMCE is divided in two parts: the '''Core''' (aka the backend) and the '''Media Director''' (aka the frontend).

	==The Core==		==The Core==
	The '''[[Core]]''' has no user interface other than an [[LinuxMCE Admin Website\|administration page]] (unless it is a [[hybrid]]). It provides processing services throughout the home, however. It acts as the central database that catalogues your media. It routes home automation messages and commands, and provides net boot images for the [[Media Directors\|Media Stations]]. It can even act as your phone system. You only have one Core in the house because it is the central point through which all devices connect. Your Core is generally left on all the time. If it is turned off, LinuxMCE functionality everywhere else in the home stops working.		The '''[[Core]]''' has no user interface other than an [[LinuxMCE Admin Website\|administration page]] (unless it is a [[hybrid]]). It provides processing services throughout the home, however. It acts as the central database that catalogues your media. It routes home automation messages and commands, and provides net boot images for the [[Media Directors\|Media Stations]]. It can even act as your phone system. You only have one Core in the house because it is the central point through which all devices connect. Your Core is generally left on all the time. If it is turned off, LinuxMCE functionality everywhere else in the home stops working.

	~~==Orbiters==~~
	The '''[[Orbiters]]''' are the control interfaces into the system. Orbiters can be the screen of the Media Director, a Nokia Internet Tablets (n810), a web based interface, allowing control using any kind of web enabled equipment, or mobile phones.

	==Media Directors==		==Media Directors==

Marie.o: Added note about orbiters, as LinuxMCE really is three parts and not just two.

2008-06-30T21:04:10Z

Added note about orbiters, as LinuxMCE really is three parts and not just two.

←Older revision		Revision as of 21:04, 30 June 2008
Line 1:		Line 1:
	LinuxMCE is divided in ~~two~~ parts: the '''Core''' (aka the backend) and the '''Media Director''' (aka the ~~frontend~~).		LinuxMCE is divided in three parts: the '''Core''' (aka the backend),the '''Orbiter''' (aka the frontend) and the '''Media Director''' (aka the media interface).

	==The Core==		==The Core==
	The '''[[Core]]''' has no user interface other than an [[LinuxMCE Admin Website\|administration page]] (unless it is a [[hybrid]]). It provides processing services throughout the home, however. It acts as the central database that catalogues your media. It routes home automation messages and commands, and provides net boot images for the [[Media Directors\|Media Stations]]. It can even act as your phone system. You only have one Core in the house because it is the central point through which all devices connect. Your Core is generally left on all the time. If it is turned off, LinuxMCE functionality everywhere else in the home stops working.		The '''[[Core]]''' has no user interface other than an [[LinuxMCE Admin Website\|administration page]] (unless it is a [[hybrid]]). It provides processing services throughout the home, however. It acts as the central database that catalogues your media. It routes home automation messages and commands, and provides net boot images for the [[Media Directors\|Media Stations]]. It can even act as your phone system. You only have one Core in the house because it is the central point through which all devices connect. Your Core is generally left on all the time. If it is turned off, LinuxMCE functionality everywhere else in the home stops working.

			==Orbiters==
			The '''[[Orbiters]]''' are the control interfaces into the system. Orbiters can be the screen of the Media Director, a Nokia Internet Tablets (n810), a web based interface, allowing control using any kind of web enabled equipment, or mobile phones.

	==Media Directors==		==Media Directors==

Perspectoff: /* Media Directors */

2008-06-30T20:14:43Z

Media Directors

←Older revision		Revision as of 20:14, 30 June 2008
Line 5:		Line 5:

	==Media Directors==		==Media Directors==
	A '''[[Media Directors \| Media Director]]''' (aka a Media Station) is connected to your TV. It is a PC running LinuxMCE, but you do not need to install any software on a Media Director as long as you enable the Media Director to ''[[~~Automatic diskless boot of media directors \|~~ netboot]]'' LinuxMCE from the Core server. (Network booting is a capability that almost all PCs have. Through the BIOS setup on any PC, netboot can be enabled as the first bootup device. When this setting is chosen and the PC is rebooted, the PC will search the network for a boot image and boots that image as its OS (rather than the OS on the hard drive).) In a LinuxMCE network, the Core provides the boot image over the network. The local PC that functions as a Media Director is essentially a thin client to the Core. (You can leave Windows, Fedora, or any other operating system you want on your PC's hard drive. When you want to use that PC as a LinuxMCE Media Director, enable netboot in the BIOS. When you want to use the OS that is stored on that PC's hard drive, reset the BIOS so that the hard drive is again the first boot device. (You can't do both at the same time.)) When LinuxMCE netboots, the software will not interfere with the software or operating system on the hard drive; it's like having 2 systems in one. You only have to install LinuxMCE software on one PC, the Core, and you can then have thin client Media Stations on PCs throughout the house. The whole process is fully automated and plug and play (whether or not you understand the concept of a netboot). The only technical thing you need to do is turn on netboot in the BIOS of a PC you want to use as a Media Director. Your PC manufacturer instructions should tell you how to change the BIOS settings.		A '''[[Media Directors \| Media Director]]''' (aka a Media Station) is connected to your TV. It is a PC running LinuxMCE, but you do not need to install any software on a Media Director as long as you enable the Media Director to ''[[netboot]]'' LinuxMCE from the Core server. (Network booting is a capability that almost all PCs have. Through the BIOS setup on any PC, netboot can be enabled as the first bootup device. When this setting is chosen and the PC is rebooted, the PC will search the network for a boot image and boots that image as its OS (rather than the OS on the hard drive).) In a LinuxMCE network, the Core provides the boot image over the network. The local PC that functions as a Media Director is essentially a thin client to the Core. (You can leave Windows, Fedora, or any other operating system you want on your PC's hard drive. When you want to use that PC as a LinuxMCE Media Director, enable netboot in the BIOS. When you want to use the OS that is stored on that PC's hard drive, reset the BIOS so that the hard drive is again the first boot device. (You can't do both at the same time.)) When LinuxMCE netboots, the software will not interfere with the software or operating system on the hard drive; it's like having 2 systems in one. You only have to install LinuxMCE software on one PC, the Core, and you can then have thin client Media Stations on PCs throughout the house. The whole process is fully automated and plug and play (whether or not you understand the concept of a netboot). The only technical thing you need to do is turn on netboot in the BIOS of a PC you want to use as a Media Director. Your PC manufacturer instructions should tell you how to change the BIOS settings.

	It is possible for the PC that functions as the LinuxMCE Core to also function as a Media Director. This is known as a [[hybrid]], and it can be used as a standalone Home Theater solution. Later, you can add other Media Directors (using the netboot method described above). A hybrid, like a standalone Core, will provide netboot images across a network. The UI (user interface) on all Media Directors looks exactly the same as the UI on the hybrid Core/Media Director. The hybrid should not be shut down, either, since it is acting as a Core. If you do, all the other Media Directors will stop working.		It is possible for the PC that functions as the LinuxMCE Core to also function as a Media Director. This is known as a [[hybrid]], and it can be used as a standalone Home Theater solution. Later, you can add other Media Directors (using the netboot method described above). A hybrid, like a standalone Core, will provide netboot images across a network. The UI (user interface) on all Media Directors looks exactly the same as the UI on the hybrid Core/Media Director. The hybrid should not be shut down, either, since it is acting as a Core. If you do, all the other Media Directors will stop working.