<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://wiki.linuxmce.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Vestminster</id>
	<title>LinuxMCE - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://wiki.linuxmce.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Vestminster"/>
	<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php/Special:Contributions/Vestminster"/>
	<updated>2026-05-11T05:22:25Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.44.0</generator>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=VDR_Setup-Wizard&amp;diff=26025</id>
		<title>VDR Setup-Wizard</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=VDR_Setup-Wizard&amp;diff=26025"/>
		<updated>2010-10-28T16:04:40Z</updated>

		<summary type="html">&lt;p&gt;Vestminster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page highlights what should be done in the setup wizard.&lt;br /&gt;
&lt;br /&gt;
== Choose transmission type ==&lt;br /&gt;
VDR supports&lt;br /&gt;
* DVB-S(2) &lt;br /&gt;
* DVB-T(2)&lt;br /&gt;
* DVB-C&lt;br /&gt;
&lt;br /&gt;
VDR supports a mix of different cards, i.e. you can plug a DVB-S and a DVB-T card into your system.&lt;br /&gt;
&lt;br /&gt;
== Choose Provider ==&lt;br /&gt;
There are three options. &lt;br /&gt;
&lt;br /&gt;
# We can either scan for the channels using the selection of the user based on the list of base data in dvb-utils (/usr/share/doc/dvb-utils/examples/scan/). &lt;br /&gt;
# We can try to find existing channels.conf on the net. &lt;br /&gt;
# We can scan using w_scan, a utility which scans without initial start data.&lt;br /&gt;
&lt;br /&gt;
The advantage of using w_scan is, that we only need the country (for DVB-C and DVB-T), or the satellite position (for DVB-S). The disadvantage is, a scan with w_scan can easily take 30-45minutes.&lt;br /&gt;
&lt;br /&gt;
=== Using the scan base data ===&lt;br /&gt;
scanning using the scan base data is done by using the scan utility, which is part of the dvb-utils&lt;br /&gt;
 scan -e 7 /usr/share/doc/dvb-utils/examples/scan/dvb-s/Astra-19.2E &lt;br /&gt;
for the Astra satellite on 19.2degree east.&lt;br /&gt;
=== Using existing channels.conf on the net ===&lt;br /&gt;
==== DVB-S(2) Provider ====&lt;br /&gt;
In theory we should use [http://www.lyngsat.com Lyngsat page] and show the list of satellites from that page, based on the location of the core. &lt;br /&gt;
* [http://www.lyngsat.com/freetv/Europe.html Europe]&lt;br /&gt;
* [http://www.lyngsat.com/freetv/Africa.html Africa]&lt;br /&gt;
etc.&lt;br /&gt;
&lt;br /&gt;
==== DVB-C and DVB-T Provider ====&lt;br /&gt;
The channels.conf for the cable companies and the terrestrial broadcast companies is kinda hard to come by. There are examples available on the [http://vdr-wiki.de/wiki/index.php/DVB-T_channels.conf vdr-wiki]&lt;br /&gt;
&lt;br /&gt;
=== Scanning using w_scan ===&lt;br /&gt;
An example on how to scan for the channels.conf is described in the [http://vdr-wiki.de/wiki/index.php/W_scan#DVB-S.2FS2_Suche_.28Hotbird_an_DiSeqC_Switch_Port_3.2C_vdr_1.7.x.2C_ab_20090502.29 VDR wiki] and on the [http://edafe.org/vdr/w_scan/ homepage] of w_scan.&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
[http://mackeeper.zeobit.com/mac-data-recovery data recovery for mac]&lt;/div&gt;</summary>
		<author><name>Vestminster</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=How_to_upgrade_linuxmce&amp;diff=26024</id>
		<title>How to upgrade linuxmce</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=How_to_upgrade_linuxmce&amp;diff=26024"/>
		<updated>2010-10-28T16:03:55Z</updated>

		<summary type="html">&lt;p&gt;Vestminster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;LinuxMCE updates are not relased on any schedule but usually every week or two there are some updated packages.  Usually if your system is working well there is no need to do an upgrade.  But there may be bugfixes or new features which affect your system (or your enjoyment of it) that you wish to take advantage of.&lt;br /&gt;
&lt;br /&gt;
When you do a package upgrade you should do it on the core first and then on each or your media directors.  If you do not upgrade each of your MDs some functionality can break.  (MythTV is an example.)&lt;br /&gt;
&lt;br /&gt;
So..  In most situations you want to do the following:&lt;br /&gt;
&lt;br /&gt;
On your core:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;apt-get update&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;apt-get upgrade&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then on each MD (after you&#039;ve completed the core upgrade)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;apt-get update&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;apt-get upgrade&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Sometimes performing an &#039;apt-get dist-upgrade&#039; is required to install new packages (like new kernels when they are available) but this is rare and you will know when it may affect you because &#039;apt-get upgrade&#039; will tell you that &#039;The following packages have been held back&#039;... or something similar.  This is telling you that there are packages that will not be changed with &#039;apt-get upgrade&#039; and that performing an &#039;apt-get dist-upgrade&#039; would likely install the new packages.  This can sometimes cause problems so be careful if you do.  Backups can be very handy.&lt;br /&gt;
&lt;br /&gt;
(Source: http://forum.linuxmce.org/index.php?topic=9524.0)&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
[http://mackeeper.zeobit.com/how-to-make-your-mac-faster speed up mac os x]&lt;/div&gt;</summary>
		<author><name>Vestminster</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=SMB_/_Samba_NAS_Configurations&amp;diff=26022</id>
		<title>SMB / Samba NAS Configurations</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=SMB_/_Samba_NAS_Configurations&amp;diff=26022"/>
		<updated>2010-10-28T16:00:29Z</updated>

		<summary type="html">&lt;p&gt;Vestminster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Tutorials]]&lt;br /&gt;
&lt;br /&gt;
[[How to setup Samba with two workgroups?]]&lt;br /&gt;
[[How to setup Samba to follow symbolic links?]]&lt;br /&gt;
&lt;br /&gt;
Problem: we have shares for each users. if I want to access it from Windows, I have to enter password. if I don&#039;t this on first access, windows won&#039;t ask my anymore to enter password and just denies access. How can I force windows, to reenter password for share ???&lt;br /&gt;
&lt;br /&gt;
If your samba password doesn&#039;t work then run this on core to update your samba password:&lt;br /&gt;
 sudo smbpasswd pluto_USER&lt;br /&gt;
where USER is your username. For instance to change john&#039;s password run sudo smbpasswd pluto_john&lt;br /&gt;
&lt;br /&gt;
== Adding fileserver on the external network ==&lt;br /&gt;
The external network does not get scanned for Samba servers. You can easily add a new server by going into the web admin&lt;br /&gt;
* Click Show Device Tree&lt;br /&gt;
* Click CORE&lt;br /&gt;
* On the right hand side, click Create Child Device&lt;br /&gt;
* Click Pick Device Template&lt;br /&gt;
* In the popup select Manufacturer-&amp;gt;Generic and Device Category-&amp;gt;File Server from the drop down menus; you can also enter device template ID 1837 in the &amp;quot;Do you know the ID of the device template?&amp;quot; field&lt;br /&gt;
* Now, it is important to fill out just the IP field (otherwise the DHCP configuration gets screwed)&lt;br /&gt;
* The username and password are only needed if the file server requires them.&lt;br /&gt;
* There is currently a bug in the webadmin which causes this file server to not be scanned for shares.&lt;br /&gt;
=== Scanning For Shares ===&lt;br /&gt;
The good thing about LinuxMCE is, that LinuxMCE routinely scans the internal network for servers, and if found, scans those servers for shares to be mounted and spidered for media. To initiate the scan for shares manually (because of a manually added server) do the following&lt;br /&gt;
* Open a terminal&lt;br /&gt;
* Execute&lt;br /&gt;
 /usr/pluto/bin/Configure_1837.sh -d &amp;lt;device-id&amp;gt; -i &#039;&amp;lt;ip-address&amp;gt;&#039; -m &#039;&amp;lt;mac-address&amp;gt;&#039;&lt;br /&gt;
&lt;br /&gt;
This will execute the scan for new shares. The shares will be presented to you on any orbiter.&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
[http://mackeeper.zeobit.com/mac-security mac security]&lt;/div&gt;</summary>
		<author><name>Vestminster</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Motorola_DCT6200&amp;diff=26021</id>
		<title>Motorola DCT6200</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Motorola_DCT6200&amp;diff=26021"/>
		<updated>2010-10-28T15:19:54Z</updated>

		<summary type="html">&lt;p&gt;Vestminster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Hardware]]&lt;br /&gt;
[[Category: Video]]&lt;br /&gt;
{{stub}}&lt;br /&gt;
Aparently it works: http://forum.linuxmce.org/index.php?topic=2922.0&lt;br /&gt;
&lt;br /&gt;
If connecting via firewire, you should be able to configure this device via mythtv-setup. Myth supports firewire recording and channel changing directly via firewire. Content varies by provider and many providers (Charter) have encrypted content over firewire, which LMCE and Myth cannot record.&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
[http://mackeeper.zeobit.com/uninstaller-for-mac uninstaller mac]&lt;/div&gt;</summary>
		<author><name>Vestminster</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Netboot&amp;diff=24848</id>
		<title>Netboot</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Netboot&amp;diff=24848"/>
		<updated>2010-08-09T14:30:17Z</updated>

		<summary type="html">&lt;p&gt;Vestminster: /* Troubleshooting */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{versioninfo}}&lt;br /&gt;
{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
[[Category:Tutorials]]&lt;br /&gt;
[[Category:Networking]]&lt;br /&gt;
A netboot is the process of [http://en.wikipedia.org/wiki/Network_booting booting an operating system over a network]. The operating system image is stored on a central server&#039;s hard drive (in this case the [[Core]]), and loaded into the RAM of the PC which is requesting the netboot.&lt;br /&gt;
&lt;br /&gt;
In many ways, it is similar to booting from a LiveCD or floppy, but the storage media is on the network.&lt;br /&gt;
&lt;br /&gt;
==Hardware enabled netboot==&lt;br /&gt;
Many newer PCs have [http://en.wikipedia.org/wiki/Preboot_Execution_Environment PXE] built into the BIOS and are able to netboot. Older PCs from the 1990s may not have this capability.&lt;br /&gt;
&lt;br /&gt;
Many current Ethernet NIC cards have a hardware chip ([http://en.wikipedia.org/wiki/Preboot_Execution_Environment PXE]-ROM) that allows booting over a network. This option is selected from the BIOS configuration on the PC.&lt;br /&gt;
&lt;br /&gt;
Netbooting is more difficult [[Wireless_Networking#Netbooting_Wirelessly|wirelessly]] if the wireless card does not have an embedded PXE-ROM chip. Check the manufacturer&#039;s specifications. Some users have used [[Wireless_Networking#Netbooting_Wirelessly|wireless bridges]] to enable wireless netboots.&lt;br /&gt;
&lt;br /&gt;
If the PC has both an active wireless and a wired Ethernet card, or multiple active wired NIC cards, it can be tricky to set which card to use for PXE netboot.&lt;br /&gt;
&lt;br /&gt;
In general, direct netbooting from the BIOS is more successful over a single wired connection.&lt;br /&gt;
&lt;br /&gt;
==Software enabled netboot==&lt;br /&gt;
Alternatively, a netboot can be specified using a boot loader on the local PC&#039;s hard drive, such as GRUB. See [[GRUB_PXE_network_boot|this discussion]].&lt;br /&gt;
&lt;br /&gt;
This can be configured to use different Ethernet cards and allows for greater flexibility, but there is a certain amount of configuration and Linux knowledge required.&lt;br /&gt;
&lt;br /&gt;
==Netbooting in LinuxMCE==&lt;br /&gt;
LinuxMCE can automatically configure itself to allow the [[Media Directors]] to do a &amp;quot;[http://en.wikipedia.org/wiki/Network_booting Network Boot]&amp;quot;. In the past, network booting has been used mostly by Apple computers, and Windows generally hasn&#039;t supported it. Nevertheless, nearly all modern computer are capable of doing a network boot, offering some significant advantages.&lt;br /&gt;
&lt;br /&gt;
When a computer does a network boot it means that it does not use its internal hard drive at all. Instead it boots up off the Core. This allows you to leave your current computer system on your local hard drive untouched by LinuxMCE, and you just hit a button on the remote to indicate if you want to use your computer like a normal PC (normal boot) or as a media director appliance (network boot). When it boots up as a Media Director, you don&#039;t have any computing issues to worry about. It functions just like an appliance -- no start menu, no software to install, nothing to configure, no viruses to worry about. This solves one of people&#039;s biggest complaints with media PC&#039;s (like Windows XP Media Centers) -- when they just want to watch TV, listen to music, or play a DVD they don&#039;t want to mess with a computer. They just want an appliance. With network boot you get the best of both worlds--it&#039;s a computer when you want to do computing, and an appliance the rest of the time.&lt;br /&gt;
&lt;br /&gt;
Best of all there&#039;s no software you need to install to make it work. When you first turn your computer on, just press the key to enter the BIOS or setup program. There is normally an option to enable network boot, sometimes called &amp;quot;PXE&amp;quot;. (This is an embedded Linux netboot protocol.) There will also be an option for boot order. Put the network boot option before the hard drive boot option -- that way the Core can tell the computer whether it should do a network boot or boot like normal.&lt;br /&gt;
&lt;br /&gt;
If you can&#039;t figure out how to set this in your computer, you should contact the manufacturer&#039;s tech support. You can also try LinuxMCE&#039;s support and forums.&lt;br /&gt;
&lt;br /&gt;
Normally, once you enable network boot in your BIOS, every time you turn on your computer it will show you this MAC Address for a few seconds.&amp;amp;nbsp; There is also an Advanced / IPs and Mac&#039;s page in the LinuxMCE Admin site that will show all the Mac Addresses in use in your home.&lt;br /&gt;
&lt;br /&gt;
DHCP must be enabled on the Core to use netboot. You can do this by checking the box in the installation wizard, or after the fact from the LinuxMCE Admin web site.&lt;br /&gt;
&lt;br /&gt;
===Disadvantages of netbooting===&lt;br /&gt;
Netbooting can be slower than booting from the hard drive -- depending on network speeds, it can be much slower.&lt;br /&gt;
&lt;br /&gt;
In addition, if there is limited memory on the client, swap time is potentially slower over the network. The hard drive used by the peripheral PC remains on the central Core, so in effect, the effective &amp;quot;bus speed&amp;quot; becomes the data transmission speed of your network.&lt;br /&gt;
&lt;br /&gt;
Lastly, unique hardware drivers and configurations for the client may not be recognized by a netboot, potentially causing a [http://en.wikipedia.org/wiki/Kernel_Panic kernel panic] (i.e. the hardware can&#039;t be recognized well enough to netboot the OS).&lt;br /&gt;
&lt;br /&gt;
===See also===&lt;br /&gt;
See also: [[Automatic diskless boot of media directors]]&lt;br /&gt;
&lt;br /&gt;
===Troubleshooting===&lt;br /&gt;
*[[MDs Do Not Network %28PXE%29 Boot]]&lt;br /&gt;
*[http://mackeeper.zeobit.com/secure-delete-mac secure erase mac]&lt;br /&gt;
*[[Automatic_diskless_boot_of_media_directors#Troubleshooting|Troublshooting an automatic diskless boot]]&lt;/div&gt;</summary>
		<author><name>Vestminster</name></author>
	</entry>
</feed>