http://wiki.linuxmce.org/api.php?action=feedcontributions&user=Razvang&feedformat=atomLinuxMCE - User contributions [en]2024-03-29T10:43:21ZUser contributionsMediaWiki 1.24.1http://wiki.linuxmce.org/index.php?title=Porting_0710_0804&diff=12182Porting 0710 08042008-05-22T12:11:40Z<p>Razvang: </p>
<hr />
<div>Problems and Steps for 0804<br />
<br />
1. Build dependencies are not installed. The list with packages needed for building linuxmce needs to be updated from one release to another so you can have the dependencies installed on the build machine. There is no automatic tool for doing this and is a time consuming task when package names change and split as you need to wait for the build to fail to intstall other packages.<br />
<br />
2. New release in linuxmce database. For every release/distro you need to add a bunch entries in the linuxmce database. First you need to update the 'Distro' table then all the Packages related tables. Linuxmce uses the database at build time when creating deb packages for depencies and later at install time to install those dependecies, add repositories and so on. Since on every release some packages tend to change names or split/merge into others, updating the packages tables is time consuming and as you need to do some install / fix cycles before figure them out.<br />
<br />
3. Download packages that will go on CD1/CD2 . Same problem: packages rename, split/merge will result in dificulties of updating the list of packages that will be needed on CD1/CD2. A depency wallker that walks the dependicies from the Packages table will not do the trick as the database is bloated with packages that will never install on a real system and will cause the size of downloaded packages to increase too much. CD1/CD2 contains the packages needed to satisfy install time depencies of LinuxMCE.<br />
<br />
4. The scripts which creates the deboostrap diskless image needed to be updated and switch from 'gutsy' to 'hardy'. I've not changed it so that will work on any ubunutu release from now on without any modification.<br />
<br />
5. There is no centralized way to fetch the skins / pluto sample media files. I created a internal rsync public repository to fix this but this copying needs to be done by hand for now. Usually you find out about this problem when some pacakges fail to create => more time lost.<br />
<br />
6. Updating the replacements dependencies: There are some deb-scr packages in trunk/ubuntu. The debs created from this ones are not found in ubuntu but are needed by linuxmce. Since the package rename split/merge affects them too, they need to be updated. <br />
<br />
7. Related to 6, Lib simple phone that we used with 0710 no longer compiles on 0804 as it uses some old headers. So the makefile for Pluto Simple Phone needs to change to use the new version that is available in ubuntu. It's depencies need to be updated in the database so it will not try to install the unbuild package. Also the simple phone code needs to be updated to compile and run with the new lib.<br />
<br />
8. Need to find a new version of vmware that runs file in 0804 and install a kubuntu on it so we can use it as a start point for a dvd creating machine. This steps are detailed in [[Building_LinuxMCE]]<br />
<br />
9. A kubuntu 0804 bootable cd needs to be striped down so it can be used as a starting point for the dvd. This steps are detailed in [[Building_LinuxMCE]]<br />
<br />
10. sqlCVS seams to stop working correctly on creating a sqlcvsdump file => the database packages fails to install. A script that copies the sqlcvsdumps from older 0710 build machines (if you're lucky to have one). This lead to a lot of problems with the first build as it contained a older sqldump which didn't had the changes of the Packages / Distro tables.<br />
<br />
11. Diskless image failes to create because of some missing packages. This missing packages have no source in our svn and are imported from other developers / companies: slimserver, vdr, zwave, myth...<br />
<br />
12. Try to make a list of package from #11 and find out if we have debs for 0804. Some of them aren't so easy to find.<br />
<br />
13. Manually update the database of the build system to fix some dependencies. Our previous sqlcvs local server that we used to do this changes just failed. Until somebody 'A..' comes with some info on how to do a sqlcvs sync I can't touch the database in the main repository (pluto-mythtv). Need to be redone when i can do a sqlsync.<br />
<br />
14. Found out that asterisk-pluto was hardcoded on a specific version of zaptel kernel modules that are not longer available in 0804. Fixed by updating it's dependencies.<br />
<br />
15. Intial linux image the md's boot in order to annouce theirselves needs to be update to match 0804's kernel version.<br />
<br />
16. Mplayer svn26234 fails to compile on 0804 : ''can't find a register in class 'GENERAL_REGS' while reloading 'asm' ''. The solution was to add ''-fomit-frame-pointer'' to the CFLAGS in the Makefile that was compiling that file.<br />
<br />
17. Nvidia drivers needed by linuxmce are now found in ubuntu but in nvidia-glx-new instead on nvidia. Needed to update the depenencies and script that where looking for nividia-glx to point to the new packages. Also needed to create a diversion to lrm-video so that it can load the nvidia module even if nvidia is not listed in xorg.conf so avwizard can run.<br />
<br />
18. The scripts that create the diskless image where hardcoded to the kernel version that 0710 had. Changed all hardcodings to a generic 'uname -r'</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Porting_0710_0804&diff=12180Porting 0710 08042008-05-22T09:39:32Z<p>Razvang: </p>
<hr />
<div>Problems and Steps for 0804<br />
<br />
1. Build dependencies are not installed. The list with packages need for building linuxmce needs to be updated from one release to another so you can have the dependencies installed on the build machine. There is no automaticall tool for doing this and is a time consuming task when package name changes and split as you need to wait for the build to fain to intstall other packages.<br />
<br />
2. New release in linuxmce database. For every release/distro you need to add a bunch entries in the linuxmce database. First you need to update the 'Distro' table then all the Packages related tables. Linuxmce uses the database at build time when creating deb packages for depencies and later at install time to install those dependecies, add repositories and so on. Since on every release some packages tend to change names or split/merge into others, updating the packages tables is time consuming and as you need to do some install / fix cycles before figure them out.<br />
<br />
3. Download packages that will go on CD1/CD2 . Same problem: packages rename, split/merge will result in dificulties of updating the list of packages that will be needed on CD1/CD2. A depency wallker that walks the dependicies from the Packages table will not do the trick as the database is bloated with packages that will never install on a real system and will cause the size of downloaded packages to increase too much. CD1/CD2 contains the packages needed to satisfy install time depencies of LinuxMCE.<br />
<br />
4. The scripts which creates the deboostrap diskless image needed to be updated and switch from 'gutsy' to 'hurdy'. I've not changed is so that will work on any ubunutu realase from now on without any modification.<br />
<br />
5. There is no centralized way to fetch the skins / pluto sample media files. I created a internal rsync public repository to fix this but this copying needs to be done by hand for now. Usually you find out about this problem when some pacakges fail to create => more time lost.<br />
<br />
6. Updating the replacements dependencies: There are some deb-scr packages in trunk/ubuntu. The debs created from this ones are not found in ubuntu but are needed by linuxmce. Since the package rename split/merge affects them too, they need to be updated. <br />
<br />
7. Related to 6, Lib simple phone that we used with 0710 no longer compiles on 0804 as it uses some old headers. So the makefile for Pluto Simple Phone need to changes to use the new version that is available in ubuntu. It's depencies needs to be update in the database so it will not try to install the unbuild package. Also the simple phone code needs to be updates to compile and run with the new lib.<br />
<br />
8. Need to find a new version of vmware that runs file in 0804 and install a kubuntu on it so we can use it as a start point for a dvd creating machine. This steps are detailed in [[Building_LinuxMCE]]<br />
<br />
9. A kubuntu 0804 bootable cd needs to be striped down so it can be used as a starting point for the dvd. This steps are detailed in [[Building_LinuxMCE]]<br />
<br />
10. sqlCVS seams to stop working correctly on creating a sqlcvsdump file => the database packages fails to install. A script that copies the sqlcvsdumps from older 0710 build machines (if you're lucky to have one). This lead to a lot of problems with the first build as it contained a older sqldump which didn't had the changes of the Packages / Distro tables.<br />
<br />
11. Diskless image failes to crete because of some missing packages. This missing packages have no source in our svn and are imported from other developers / companies: slimserver, vdr, zwave, myth...<br />
<br />
12. Try to make a list of package from #11 and find out if we have debs for 0804. Some of them aren't so easy to find.<br />
<br />
13. Manually update the database of the build system to fix some dependencies. Our previous sqlcvs local server that we used to do this changes just failed. Until somebody 'A..' comes with some info on how to do a sqlcvs sync I can't touch the database in the main repository (pluto-mythtv). Need to be redone when i can do a sqlsync.<br />
<br />
14. Found out that asterisk-pluto was hardcoded on a specific version of zaptel kernel modules that are not loger available in 0804. Fixed by updating it's depenncies.<br />
<br />
15. Intial linux image the md's boot in order to annouce theirselfs needs to be update to macth 0804's kernel version.<br />
<br />
16. Mplayer svn26234 fails to compile on 0804 : ''can't find a register in class 'GENERAL_REGS' while reloading 'asm' ''. The solution was to add ''-fomit-frame-pointer'' to the CFLAGS in the Makefile that was compiling that file.<br />
<br />
17. Nvidia drivers needed by linuxmce are now found in ubuntu but in nvidia-glx-new instead on nvidia. Needed to update the depenencies and script that where looking for nividia-glx to point to the new packages. Also needed to create a diversion to lrm-video so that it can load the nvidia module even if nvidia is not listed in xorg.conf so avwizard can run.</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Porting_0710_0804&diff=12179Porting 0710 08042008-05-22T08:48:41Z<p>Razvang: </p>
<hr />
<div>Problems and Steps for 0804<br />
<br />
1. Build dependencies are not installed. The list with packages need for building linuxmce needs to be updated from one release to another so you can have the dependencies installed on the build machine. There is no automaticall tool for doing this and is a time consuming task when package name changes and split as you need to wait for the build to fain to intstall other packages.<br />
<br />
2. New release in linuxmce database. For every release/distro you need to add a bunch entries in the linuxmce database. First you need to update the 'Distro' table then all the Packages related tables. Linuxmce uses the database at build time when creating deb packages for depencies and later at install time to install those dependecies, add repositories and so on. Since on every release some packages tend to change names or split/merge into others, updating the packages tables is time consuming and as you need to do some install / fix cycles before figure them out.<br />
<br />
3. Download packages that will go on CD1/CD2 . Same problem: packages rename, split/merge will result in dificulties of updating the list of packages that will be needed on CD1/CD2. A depency wallker that walks the dependicies from the Packages table will not do the trick as the database is bloated with packages that will never install on a real system and will cause the size of downloaded packages to increase too much. CD1/CD2 contains the packages needed to satisfy install time depencies of LinuxMCE.<br />
<br />
4. The scripts which creates the deboostrap diskless image needed to be updated and switch from 'gutsy' to 'hurdy'. I've not changed is so that will work on any ubunutu realase from now on without any modification.<br />
<br />
5. There is no centralized way to fetch the skins / pluto sample media files. I created a internal rsync public repository to fix this but this copying needs to be done by hand for now. Usually you find out about this problem when some pacakges fail to create => more time lost.<br />
<br />
6. Updating the replacements dependencies: There are some deb-scr packages in trunk/ubuntu. The debs created from this ones are not found in ubuntu but are needed by linuxmce. Since the package rename split/merge affects them too, they need to be updated. <br />
<br />
7. Related to 6, Lib simple phone that we used with 0710 no longer compiles on 0804 as it uses some old headers. So the makefile for Pluto Simple Phone need to changes to use the new version that is available in ubuntu. It's depencies needs to be update in the database so it will not try to install the unbuild package. Also the simple phone code needs to be updates to compile and run with the new lib.<br />
<br />
8. Need to find a new version of vmware that runs file in 0804 and install a kubuntu on it so we can use it as a start point for a dvd creating machine. This steps are detailed in [[Building_LinuxMCE]]<br />
<br />
9. A kubuntu 0804 bootable cd needs to be striped down so it can be used as a starting point for the dvd. This steps are detailed in [[Building_LinuxMCE]]<br />
<br />
10. sqlCVS seams to stop working correctly on creating a sqlcvsdump file => the database packages fails to install. A script that copies the sqlcvsdumps from older 0710 build machines (if you're lucky to have one). This lead to a lot of problems with the first build as it contained a older sqldump which didn't had the changes of the Packages / Distro tables.<br />
<br />
11. Diskless image failes to crete because of some missing packages. This missing packages have no source in our svn and are imported from other developers / companies: slimserver, vdr, zwave, myth...<br />
<br />
12. Try to make a list of package from #11 and find out if we have debs for 0804. Some of them aren't so easy to find.<br />
<br />
13. Manually update the database of the build system to fix some dependencies. Our previous sqlcvs local server that we used to do this changes just failed. Until somebody 'A..' comes with some info on how to do a sqlcvs sync I can't touch the database in the main repository (pluto-mythtv). Need to be redone when i can do a sqlsync.<br />
<br />
14. Found out that asterisk-pluto was hardcoded on a specific version of zaptel kernel modules that are not loger available in 0804. Fixed by updating it's depenncies.<br />
<br />
15. Intial linux image the md's boot in order to annouce theirselfs needs to be update to macth 0804's kernel version.<br />
<br />
16. Mplayer svn26234 fails to compile on 0804 : ''can't find a register in class 'GENERAL_REGS' while reloading 'asm' ''</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Porting_0710_0804&diff=11601Porting 0710 08042008-05-19T16:05:07Z<p>Razvang: New page: Problems and Steps for 0804 1. Build dependencies are not installed. The list with packages need for building linuxmce needs to be updated from one release to another so you can have the ...</p>
<hr />
<div>Problems and Steps for 0804<br />
<br />
1. Build dependencies are not installed. The list with packages need for building linuxmce needs to be updated from one release to another so you can have the dependencies installed on the build machine. There is no automaticall tool for doing this and is a time consuming task when package name changes and split as you need to wait for the build to fain to intstall other packages.<br />
<br />
2. New release in linuxmce database. For every release/distro you need to add a bunch entries in the linuxmce database. First you need to update the 'Distro' table then all the Packages related tables. Linuxmce uses the database at build time when creating deb packages for depencies and later at install time to install those dependecies, add repositories and so on. Since on every release some packages tend to change names or split/merge into others, updating the packages tables is time consuming and as you need to do some install / fix cycles before figure them out.<br />
<br />
3. Download packages that will go on CD1/CD2 . Same problem: packages rename, split/merge will result in dificulties of updating the list of packages that will be needed on CD1/CD2. A depency wallker that walks the dependicies from the Packages table will not do the trick as the database is bloated with packages that will never install on a real system and will cause the size of downloaded packages to increase too much. CD1/CD2 contains the packages needed to satisfy install time depencies of LinuxMCE.<br />
<br />
4. The scripts which creates the deboostrap diskless image needed to be updated and switch from 'gutsy' to 'hurdy'. I've not changed is so that will work on any ubunutu realase from now on without any modification.<br />
<br />
5. There is no centralized way to fetch the skins / pluto sample media files. I created a internal rsync public repository to fix this but this copying needs to be done by hand for now. Usually you find out about this problem when some pacakges fail to create => more time lost.<br />
<br />
6. Updating the replacements dependencies: There are some deb-scr packages in trunk/ubuntu. The debs created from this ones are not found in ubuntu but are needed by linuxmce. Since the package rename split/merge affects them too, they need to be updated. <br />
<br />
7. Related to 6, Lib simple phone that we used with 0710 no longer compiles on 0804 as it uses some old headers. So the makefile for Pluto Simple Phone need to changes to use the new version that is available in ubuntu. It's depencies needs to be update in the database so it will not try to install the unbuild package. Also the simple phone code needs to be updates to compile and run with the new lib.<br />
<br />
8. Need to find a new version of vmware that runs file in 0804 and install a kubuntu on it so we can use it as a start point for a dvd creating machine. This steps are detailed in [[Building_LinuxMCE]]<br />
<br />
9. A kubuntu 0804 bootable cd needs to be striped down so it can be used as a starting point for the dvd. This steps are detailed in [[Building_LinuxMCE]]<br />
<br />
10. sqlCVS seams to stop working correctly on creating a sqlcvsdump file => the database packages fails to install. A script that copies the sqlcvsdumps from older 0710 build machines (if you're lucky to have one). This lead to a lot of problems with the first build as it contained a older sqldump which didn't had the changes of the Packages / Distro tables.<br />
<br />
11. Diskless image failes to crete because of some missing packages. This missing packages have no source in our svn and are imported from other developers / companies: slimserver, vdr, zwave, myth...<br />
<br />
12. Try to make a list of package from #11 and find out if we have debs for 0804. Some of them aren't so easy to find.<br />
<br />
13. Manually update the database of the build system to fix some dependencies. Our previous sqlcvs local server that we used to do this changes just failed. Until somebody 'A..' comes with some info on how to do a sqlcvs sync I can't touch the database in the main repository (pluto-mythtv). Need to be redone when i can do a sqlsync.<br />
<br />
14. Found out that asterisk-pluto was hardcoded on a specific version of zaptel kernel modules that are not loger available in 0804. Fixed by updating it's depenncies.<br />
<br />
15. Intial linux image the md's boot in order to annouce theirselfs needs to be update to macth 0804's kernel version.</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Building_LinuxMCE_0804&diff=10972Building LinuxMCE 08042008-05-13T12:26:02Z<p>Razvang: /* First Time Build */</p>
<hr />
<div>With this tutorial I'll try to summarize the step involved in building the LinuxMCE CDs and DVDs together with some changes that I've done when switching from Kubuntu 0704 to Kubuntu 0710.<br />
<br />
== Requirements ==<br />
''Requirements'':<br />
* Powerful enough system to do the compilation and building of packages as is a cpu intensive task and it can take quite a long time.<br />
* Lot of disk space, at least 40G hard drive.<br />
* A working internet connection as the build and preparation process will need to access get some files from the public domain.<br />
<br />
''First Steps'':<br />
* Install Kubuntu 0804. I use the desktop installation CD and i would recommend to do the same as this steps will consider this kind of installation performed. Of course an Ubuntu Server or Alternate CD will work too but you may need to install some build dependencies / runtime libraries that I have by default installed on Kubuntu 0804.<br />
* Install some subversion so you can checkout a copy of the build script from LinuxMCE's svn.<br />
apt-get install subversion<br />
<br />
== Build Scripts ==<br />
The next step after having 0804 installed is to get a copy of the build script:<br />
sudo su<br />
cd $HOME<br />
svn co http://svn.linuxmce.com/pluto/trunk/src/Ubuntu_Helpers_NoHardcode/<br />
mv Ubuntu_Helpers_NoHardcode/ /usr/local/lmce-build<br />
<br />
I will try to explain them quickly so you'll know what each of them does.<br />
;build.sh<br />
:This is the main script and calls all the other script of the build process to perform simple task.<br />
<br />
;loop-build.sh<br />
:This is a script used on our build machines and it does the next steps in a infinite loop: <br />
:#Calls ''build.sh'' script to performa a build. <br />
:#Stores the build output in a ftp viewable directory.<br />
:#Sends mail to developers on fail and on success.<br />
<br />
=== Scripts used for preaparing the build system ===<br />
;prepare-scripts/install-build-pkgs.sh<br />
:This script will download and install all the build dependencies needed to create the linuxmce packages.<br />
<br />
;prepare-scripts/cd1-prepare.sh<br />
:Download the ubuntu packages that will be copied on LinuxMCE CD1<br />
<br />
;prepare-scripts/cd2-packages.sh<br />
:Download the ubuntu packages that will be copied on LinuxMCE CD2<br />
<br />
;prepare-scripts/create-diskless-debootstrap.sh<br />
:Creates a debootsrap image used later as a base for creating the diskless image.<br />
<br />
;prepare-script/import-external-files.sh<br />
:Downloads the linuxmce media file : skins, demo videos ..<br />
<br />
;prepare-script/preseed-build-pkgs.sh:<br />
:It was used to preseed some src packages like lirc-module so that they will build in a non interactive mode by the build process. It is not used for 0804.<br />
<br />
=== Scripts used for building CDs === <br />
;build-scripts/checkout-svn.sh<br />
:Gets a updated copy of the source tree from svn and stores it in ''/var/lmce-build/svn/''<br />
<br />
;build-script/import-win32bins.sh<br />
:Copies the latest windows binaries from the linuxmce ftp <br />
<br />
;buils-script/build-replacements.sh<br />
:Creates a set of non-linuxmce-specific deb packages which don't usually come with Ubuntu but are needed by our applications. It may also build some packages that are already in Ubuntu but are patched and needs to be repacked. The sources for this debs are located in trunk/ubuntu directory of the svn this means /var/lmce-build/svn/trunk/ubuntu on your local machine (after the svn checkout). Moust of this sources are in a deb-src format. The created debs will be stored in ''/var/lmce-build/replacements/'' directory.<br />
<br />
;build-script/build-makerelease.sh<br />
:Build a c++ linuxmce application and it's dependencies from the linuxmce svn. This application, called ''MakeRelease'' it's used to build and pack all the linuxmce packages. The output files will be stored in ''/var/lmce-build/MakeRelease/'' when the script finishes.<br />
<br />
;build-script/import-database.sh<br />
:This script takes the latest version of the LinuxMCE MySQL databases from the LinuxMCE server. The information from this databases is used by MakeRelease to build and compile the software. The databases will also be used to create some sqldumps that will be packaged on the LinuxMCE CDs and DVSs that are created.<br />
<br />
;build-scripts/build-maindebs.sh<br />
:Runs MakeRelease and based on the information from the database compiles and packs the linuxmce packages using the sources stored in ''/var/lmce-build/svn''. The created debs will be stored in ''/var/lmce-build/out/tmp'' directory.<br />
<br />
;build-scripts/get-closed-source-debs.sh<br />
:Download the latest pluto debs which are build on a remote server. This debs are compiled from source which are object of some Pluto NDAs and cannot be made public (ex: pluto-zwave).<br />
<br />
;build-script/create-repo.sh<br />
:After all the needed packages are created / downloaded, this script copies them from their output directories and stores them in ''/var/www/'' directory. It also creates a Packages.gz file so you can use that directory as a repository which you can add in sources.list.<br />
<br />
;build-script/cd1-build.sh<br />
:Creates LinuxMCE CD1. This cd will contain moust of the linuxmce specific debs but also some Ubuntu debs which are needed for by LinuxMCE application and are not installed by default in Kubuntu. The linuxmce debs are copied from ''/var/www' and the extra ubuntu debs are fetched from ''/var/lmce-build/cd1-packages/'' directory.<br />
<br />
;build-scripts/cd2-build.sh<br />
:Creates LinuxMCE CD2. This cd contains only few linuxmce debs and a lot of ubuntu debs which are not installed by default on a Kubuntu system but are needed douring the install process. The Ubuntu debs are copied from ''/var/lmce-build/cd2-packages/'' folder.<br />
<br />
=== Scripts used for building DVDs ===<br />
;vmware-install/install_in_vmware.sh<br />
:This script uses the LinuxMCE CD1&2 to automatically install LinuxMCE on a clean Kubuntu system. All the installation takes place in vmware virtual machine and at the end of the installation the script will create a tar.gz image of the vmware disk directory structure. This tar.gz image will be used for creating the dvd image.<br />
<br />
;build-dvd/build-cd.sh<br />
:This script takes the tar.gz image created by the install_in_vmware.sh script and generates the bootable dvd image. For generating the bootable dvd image this script also needs<br />
:*The content of a striped squashfs image found on the Kubuntu CD : ''/var/lmce-build/lite-installer/ubuntu-squashfs-base.tgz''<br />
:*The content of a Kubuntu CD without the squashfs file: ''/var/lmce-build/lite-installer/ubutu-livecd.tgz''<br />
<br />
== First Time Build ==<br />
At this point you should already have the Kubuntu system installed and some basic knowledge of what each build script is doing. I recommend running the each script by hand for the first time and not use the ''build.sh'' or ''prepare.sh'' scripts. It will be a lot easer to debug problems this way.<br />
<br />
===Preparation for the build===<br />
This set of scripts should be run only once to prepare a Kubuntu system to act as a build server. The order is not so important for them but I recomend to stick with it. You'll need to run all the script as ''root'' as they will need write access in several directories.<br />
<br />
* The next script will create the /etc/lmce-build configuration directory and copy all the default configuration files there. The default files are stored in the ''conf-files'' folder and spited other folders depending on release and architecture. I recommend you check the ''install.sh'' script to see how it does this before running it.<br />
./install.sh<br />
* Install the build dependencies. Takes aprox. 30min depending on you internet connection speed. The packages that get installed are listed in ''/etc/lmce-build/build-packages'':<br />
./prepare-scripts/install-build-pkgs.sh<br />
* Download Ubuntu packages needed by CD1&2. The downloded packages are liste in files ''/etc/lmce-build/cd1-packages'' and ''/etc/lmce-build/cd2-packages''<br />
./prepare-scripts/cd1-prepare.sh<br />
./prepare-scripts/cd2-prepare.sh<br />
* Download Ubuntu packages found on a default Kubuntu CD. This ones are used when installing the system in vmware:<br />
mkdir -p /var/lmce-build/kubuntu-cd<br />
pushd /var/lmce-build/kubuntu-cd<br />
aptitude download `cat /etc/lmce-build/cdK-packages`<br />
popd<br />
* Run the other prepare scripts :<br />
./prepare-scripts/create-diskless-debootstrap.sh<br />
./prepare-scripts/import-external-files.sh<br />
./prepare-scripts/preseed-build-pkgs.sh<br />
<br />
===Preparing for DVD Creation===<br />
If you want only to be able to create linuxmce packages and create the standard CDs you can skip this steps. This steps are only needed for creating the DVD and involve some advanced skills as you must manually do most of the things here.<br />
<br />
* Create the ''/var/lmce-build/lite-installer/ubuntu-livecd.tgz'' and ''/var/lmce-build/lite-installer/ubuntu-squashfs-base.tgz'' archives that are used as a base of the LinuxMCE DVD:<br />
**'''ubuntu-livecd.tgz''': This is the simple one. It contains the all files from the kubnuntu dvd except for the squashfs image file. The steps to create this file are:<br />
**#Mount the kubuntu cd<br />
**#Copy the contents of the cd in a directory<br />
**#Remove the squashfs image from the directory (casper/filesystem.squashfs)<br />
**#Create a the tar.gz<br />
**'''filesystem.squashfs''': You'll need to use the ''casper/filesystem.squashfs'' which you eliminate in creation of the previous tar.gz:<br />
**#Mount the squashfs image in a directory<br />
**#Copy the entire chroot content into another directory so you can modify it<br />
**#Chroot in the new directory and uinstall all the x11/kde related packages<br />
**#Exit the chroot and targz what is left of the unpacked squashfs image<br />
* Create the vmware virtual machine and install vmware player:<br />
**The build scripts expect a vmware virtual machine that can be started with vmware player. It's important for the disk image of the vmware machine to be in a 'flat' format, meaning that will not be splited in 2G files and all the disk space is allocated from the start, i use 15G virtual disks. Second, make sure that the network is set on nat. It's important the the virtual machine to be named 'Kubuntu'.<br />
**Install a Kubuntu CD on the virtual machine.<br />
**Copy the ssh public key (''/etc/lmce-build/builder.key.pub'') in the virtual machine and make sure that you can ssh using the private key from you system (''/etc/lmce-build/builder.key'') into root on you vmware machine.<br />
**Add an entry in /etc/hosts with hostname 'vmware' and ip of your vmware machine<br />
**Leave virtual machine powered up and shutdown vmware. This way the next time you start the virtual machine you will be able to login quickly with ssh on it.<br />
**Copy all the files of the virtual machine in ''/var/Kubuntu''</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Building_LinuxMCE_0804&diff=10971Building LinuxMCE 08042008-05-13T12:25:18Z<p>Razvang: /* Runing the prepare script */</p>
<hr />
<div>With this tutorial I'll try to summarize the step involved in building the LinuxMCE CDs and DVDs together with some changes that I've done when switching from Kubuntu 0704 to Kubuntu 0710.<br />
<br />
== Requirements ==<br />
''Requirements'':<br />
* Powerful enough system to do the compilation and building of packages as is a cpu intensive task and it can take quite a long time.<br />
* Lot of disk space, at least 40G hard drive.<br />
* A working internet connection as the build and preparation process will need to access get some files from the public domain.<br />
<br />
''First Steps'':<br />
* Install Kubuntu 0804. I use the desktop installation CD and i would recommend to do the same as this steps will consider this kind of installation performed. Of course an Ubuntu Server or Alternate CD will work too but you may need to install some build dependencies / runtime libraries that I have by default installed on Kubuntu 0804.<br />
* Install some subversion so you can checkout a copy of the build script from LinuxMCE's svn.<br />
apt-get install subversion<br />
<br />
== Build Scripts ==<br />
The next step after having 0804 installed is to get a copy of the build script:<br />
sudo su<br />
cd $HOME<br />
svn co http://svn.linuxmce.com/pluto/trunk/src/Ubuntu_Helpers_NoHardcode/<br />
mv Ubuntu_Helpers_NoHardcode/ /usr/local/lmce-build<br />
<br />
I will try to explain them quickly so you'll know what each of them does.<br />
;build.sh<br />
:This is the main script and calls all the other script of the build process to perform simple task.<br />
<br />
;loop-build.sh<br />
:This is a script used on our build machines and it does the next steps in a infinite loop: <br />
:#Calls ''build.sh'' script to performa a build. <br />
:#Stores the build output in a ftp viewable directory.<br />
:#Sends mail to developers on fail and on success.<br />
<br />
=== Scripts used for preaparing the build system ===<br />
;prepare-scripts/install-build-pkgs.sh<br />
:This script will download and install all the build dependencies needed to create the linuxmce packages.<br />
<br />
;prepare-scripts/cd1-prepare.sh<br />
:Download the ubuntu packages that will be copied on LinuxMCE CD1<br />
<br />
;prepare-scripts/cd2-packages.sh<br />
:Download the ubuntu packages that will be copied on LinuxMCE CD2<br />
<br />
;prepare-scripts/create-diskless-debootstrap.sh<br />
:Creates a debootsrap image used later as a base for creating the diskless image.<br />
<br />
;prepare-script/import-external-files.sh<br />
:Downloads the linuxmce media file : skins, demo videos ..<br />
<br />
;prepare-script/preseed-build-pkgs.sh:<br />
:It was used to preseed some src packages like lirc-module so that they will build in a non interactive mode by the build process. It is not used for 0804.<br />
<br />
=== Scripts used for building CDs === <br />
;build-scripts/checkout-svn.sh<br />
:Gets a updated copy of the source tree from svn and stores it in ''/var/lmce-build/svn/''<br />
<br />
;build-script/import-win32bins.sh<br />
:Copies the latest windows binaries from the linuxmce ftp <br />
<br />
;buils-script/build-replacements.sh<br />
:Creates a set of non-linuxmce-specific deb packages which don't usually come with Ubuntu but are needed by our applications. It may also build some packages that are already in Ubuntu but are patched and needs to be repacked. The sources for this debs are located in trunk/ubuntu directory of the svn this means /var/lmce-build/svn/trunk/ubuntu on your local machine (after the svn checkout). Moust of this sources are in a deb-src format. The created debs will be stored in ''/var/lmce-build/replacements/'' directory.<br />
<br />
;build-script/build-makerelease.sh<br />
:Build a c++ linuxmce application and it's dependencies from the linuxmce svn. This application, called ''MakeRelease'' it's used to build and pack all the linuxmce packages. The output files will be stored in ''/var/lmce-build/MakeRelease/'' when the script finishes.<br />
<br />
;build-script/import-database.sh<br />
:This script takes the latest version of the LinuxMCE MySQL databases from the LinuxMCE server. The information from this databases is used by MakeRelease to build and compile the software. The databases will also be used to create some sqldumps that will be packaged on the LinuxMCE CDs and DVSs that are created.<br />
<br />
;build-scripts/build-maindebs.sh<br />
:Runs MakeRelease and based on the information from the database compiles and packs the linuxmce packages using the sources stored in ''/var/lmce-build/svn''. The created debs will be stored in ''/var/lmce-build/out/tmp'' directory.<br />
<br />
;build-scripts/get-closed-source-debs.sh<br />
:Download the latest pluto debs which are build on a remote server. This debs are compiled from source which are object of some Pluto NDAs and cannot be made public (ex: pluto-zwave).<br />
<br />
;build-script/create-repo.sh<br />
:After all the needed packages are created / downloaded, this script copies them from their output directories and stores them in ''/var/www/'' directory. It also creates a Packages.gz file so you can use that directory as a repository which you can add in sources.list.<br />
<br />
;build-script/cd1-build.sh<br />
:Creates LinuxMCE CD1. This cd will contain moust of the linuxmce specific debs but also some Ubuntu debs which are needed for by LinuxMCE application and are not installed by default in Kubuntu. The linuxmce debs are copied from ''/var/www' and the extra ubuntu debs are fetched from ''/var/lmce-build/cd1-packages/'' directory.<br />
<br />
;build-scripts/cd2-build.sh<br />
:Creates LinuxMCE CD2. This cd contains only few linuxmce debs and a lot of ubuntu debs which are not installed by default on a Kubuntu system but are needed douring the install process. The Ubuntu debs are copied from ''/var/lmce-build/cd2-packages/'' folder.<br />
<br />
=== Scripts used for building DVDs ===<br />
;vmware-install/install_in_vmware.sh<br />
:This script uses the LinuxMCE CD1&2 to automatically install LinuxMCE on a clean Kubuntu system. All the installation takes place in vmware virtual machine and at the end of the installation the script will create a tar.gz image of the vmware disk directory structure. This tar.gz image will be used for creating the dvd image.<br />
<br />
;build-dvd/build-cd.sh<br />
:This script takes the tar.gz image created by the install_in_vmware.sh script and generates the bootable dvd image. For generating the bootable dvd image this script also needs<br />
:*The content of a striped squashfs image found on the Kubuntu CD : ''/var/lmce-build/lite-installer/ubuntu-squashfs-base.tgz''<br />
:*The content of a Kubuntu CD without the squashfs file: ''/var/lmce-build/lite-installer/ubutu-livecd.tgz''<br />
<br />
== First Time Build ==<br />
At this point you should already have the Kubuntu system installed and some basic knowledge of what each build script is doing. I recommend running the each script by hand for the first time and not use the ''build.sh'' or ''prepare.sh'' scripts. It will be a lot easer to debug problems this way.<br />
<br />
===Runing the prepare scripts===<br />
This set of scripts should be run only once to prepare a Kubuntu system to act as a build server. The order is not so important for them but I recomend to stick with it. You'll need to run all the script as ''root'' as they will need write access in several directories.<br />
<br />
* The next script will create the /etc/lmce-build configuration directory and copy all the default configuration files there. The default files are stored in the ''conf-files'' folder and spited other folders depending on release and architecture. I recommend you check the ''install.sh'' script to see how it does this before running it.<br />
./install.sh<br />
* Install the build dependencies. Takes aprox. 30min depending on you internet connection speed. The packages that get installed are listed in ''/etc/lmce-build/build-packages'':<br />
./prepare-scripts/install-build-pkgs.sh<br />
* Download Ubuntu packages needed by CD1&2. The downloded packages are liste in files ''/etc/lmce-build/cd1-packages'' and ''/etc/lmce-build/cd2-packages''<br />
./prepare-scripts/cd1-prepare.sh<br />
./prepare-scripts/cd2-prepare.sh<br />
* Download Ubuntu packages found on a default Kubuntu CD. This ones are used when installing the system in vmware:<br />
mkdir -p /var/lmce-build/kubuntu-cd<br />
pushd /var/lmce-build/kubuntu-cd<br />
aptitude download `cat /etc/lmce-build/cdK-packages`<br />
popd<br />
* Run the other prepare scripts :<br />
./prepare-scripts/create-diskless-debootstrap.sh<br />
./prepare-scripts/import-external-files.sh<br />
./prepare-scripts/preseed-build-pkgs.sh<br />
<br />
===Preparing for DVD Creation===<br />
If you want only to be able to create linuxmce packages and create the standard CDs you can skip this steps. This steps are only needed for creating the DVD and involve some advanced skills as you must manually do most of the things here.<br />
<br />
* Create the ''/var/lmce-build/lite-installer/ubuntu-livecd.tgz'' and ''/var/lmce-build/lite-installer/ubuntu-squashfs-base.tgz'' archives that are used as a base of the LinuxMCE DVD:<br />
**'''ubuntu-livecd.tgz''': This is the simple one. It contains the all files from the kubnuntu dvd except for the squashfs image file. The steps to create this file are:<br />
**#Mount the kubuntu cd<br />
**#Copy the contents of the cd in a directory<br />
**#Remove the squashfs image from the directory (casper/filesystem.squashfs)<br />
**#Create a the tar.gz<br />
**'''filesystem.squashfs''': You'll need to use the ''casper/filesystem.squashfs'' which you eliminate in creation of the previous tar.gz:<br />
**#Mount the squashfs image in a directory<br />
**#Copy the entire chroot content into another directory so you can modify it<br />
**#Chroot in the new directory and uinstall all the x11/kde related packages<br />
**#Exit the chroot and targz what is left of the unpacked squashfs image<br />
* Create the vmware virtual machine and install vmware player:<br />
**The build scripts expect a vmware virtual machine that can be started with vmware player. It's important for the disk image of the vmware machine to be in a 'flat' format, meaning that will not be splited in 2G files and all the disk space is allocated from the start, i use 15G virtual disks. Second, make sure that the network is set on nat. It's important the the virtual machine to be named 'Kubuntu'.<br />
**Install a Kubuntu CD on the virtual machine.<br />
**Copy the ssh public key (''/etc/lmce-build/builder.key.pub'') in the virtual machine and make sure that you can ssh using the private key from you system (''/etc/lmce-build/builder.key'') into root on you vmware machine.<br />
**Add an entry in /etc/hosts with hostname 'vmware' and ip of your vmware machine<br />
**Leave virtual machine powered up and shutdown vmware. This way the next time you start the virtual machine you will be able to login quickly with ssh on it.<br />
**Copy all the files of the virtual machine in ''/var/Kubuntu''</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Building_LinuxMCE_0804&diff=10970Building LinuxMCE 08042008-05-13T12:24:55Z<p>Razvang: /* Preparing for DVD Creation */</p>
<hr />
<div>With this tutorial I'll try to summarize the step involved in building the LinuxMCE CDs and DVDs together with some changes that I've done when switching from Kubuntu 0704 to Kubuntu 0710.<br />
<br />
== Requirements ==<br />
''Requirements'':<br />
* Powerful enough system to do the compilation and building of packages as is a cpu intensive task and it can take quite a long time.<br />
* Lot of disk space, at least 40G hard drive.<br />
* A working internet connection as the build and preparation process will need to access get some files from the public domain.<br />
<br />
''First Steps'':<br />
* Install Kubuntu 0804. I use the desktop installation CD and i would recommend to do the same as this steps will consider this kind of installation performed. Of course an Ubuntu Server or Alternate CD will work too but you may need to install some build dependencies / runtime libraries that I have by default installed on Kubuntu 0804.<br />
* Install some subversion so you can checkout a copy of the build script from LinuxMCE's svn.<br />
apt-get install subversion<br />
<br />
== Build Scripts ==<br />
The next step after having 0804 installed is to get a copy of the build script:<br />
sudo su<br />
cd $HOME<br />
svn co http://svn.linuxmce.com/pluto/trunk/src/Ubuntu_Helpers_NoHardcode/<br />
mv Ubuntu_Helpers_NoHardcode/ /usr/local/lmce-build<br />
<br />
I will try to explain them quickly so you'll know what each of them does.<br />
;build.sh<br />
:This is the main script and calls all the other script of the build process to perform simple task.<br />
<br />
;loop-build.sh<br />
:This is a script used on our build machines and it does the next steps in a infinite loop: <br />
:#Calls ''build.sh'' script to performa a build. <br />
:#Stores the build output in a ftp viewable directory.<br />
:#Sends mail to developers on fail and on success.<br />
<br />
=== Scripts used for preaparing the build system ===<br />
;prepare-scripts/install-build-pkgs.sh<br />
:This script will download and install all the build dependencies needed to create the linuxmce packages.<br />
<br />
;prepare-scripts/cd1-prepare.sh<br />
:Download the ubuntu packages that will be copied on LinuxMCE CD1<br />
<br />
;prepare-scripts/cd2-packages.sh<br />
:Download the ubuntu packages that will be copied on LinuxMCE CD2<br />
<br />
;prepare-scripts/create-diskless-debootstrap.sh<br />
:Creates a debootsrap image used later as a base for creating the diskless image.<br />
<br />
;prepare-script/import-external-files.sh<br />
:Downloads the linuxmce media file : skins, demo videos ..<br />
<br />
;prepare-script/preseed-build-pkgs.sh:<br />
:It was used to preseed some src packages like lirc-module so that they will build in a non interactive mode by the build process. It is not used for 0804.<br />
<br />
=== Scripts used for building CDs === <br />
;build-scripts/checkout-svn.sh<br />
:Gets a updated copy of the source tree from svn and stores it in ''/var/lmce-build/svn/''<br />
<br />
;build-script/import-win32bins.sh<br />
:Copies the latest windows binaries from the linuxmce ftp <br />
<br />
;buils-script/build-replacements.sh<br />
:Creates a set of non-linuxmce-specific deb packages which don't usually come with Ubuntu but are needed by our applications. It may also build some packages that are already in Ubuntu but are patched and needs to be repacked. The sources for this debs are located in trunk/ubuntu directory of the svn this means /var/lmce-build/svn/trunk/ubuntu on your local machine (after the svn checkout). Moust of this sources are in a deb-src format. The created debs will be stored in ''/var/lmce-build/replacements/'' directory.<br />
<br />
;build-script/build-makerelease.sh<br />
:Build a c++ linuxmce application and it's dependencies from the linuxmce svn. This application, called ''MakeRelease'' it's used to build and pack all the linuxmce packages. The output files will be stored in ''/var/lmce-build/MakeRelease/'' when the script finishes.<br />
<br />
;build-script/import-database.sh<br />
:This script takes the latest version of the LinuxMCE MySQL databases from the LinuxMCE server. The information from this databases is used by MakeRelease to build and compile the software. The databases will also be used to create some sqldumps that will be packaged on the LinuxMCE CDs and DVSs that are created.<br />
<br />
;build-scripts/build-maindebs.sh<br />
:Runs MakeRelease and based on the information from the database compiles and packs the linuxmce packages using the sources stored in ''/var/lmce-build/svn''. The created debs will be stored in ''/var/lmce-build/out/tmp'' directory.<br />
<br />
;build-scripts/get-closed-source-debs.sh<br />
:Download the latest pluto debs which are build on a remote server. This debs are compiled from source which are object of some Pluto NDAs and cannot be made public (ex: pluto-zwave).<br />
<br />
;build-script/create-repo.sh<br />
:After all the needed packages are created / downloaded, this script copies them from their output directories and stores them in ''/var/www/'' directory. It also creates a Packages.gz file so you can use that directory as a repository which you can add in sources.list.<br />
<br />
;build-script/cd1-build.sh<br />
:Creates LinuxMCE CD1. This cd will contain moust of the linuxmce specific debs but also some Ubuntu debs which are needed for by LinuxMCE application and are not installed by default in Kubuntu. The linuxmce debs are copied from ''/var/www' and the extra ubuntu debs are fetched from ''/var/lmce-build/cd1-packages/'' directory.<br />
<br />
;build-scripts/cd2-build.sh<br />
:Creates LinuxMCE CD2. This cd contains only few linuxmce debs and a lot of ubuntu debs which are not installed by default on a Kubuntu system but are needed douring the install process. The Ubuntu debs are copied from ''/var/lmce-build/cd2-packages/'' folder.<br />
<br />
=== Scripts used for building DVDs ===<br />
;vmware-install/install_in_vmware.sh<br />
:This script uses the LinuxMCE CD1&2 to automatically install LinuxMCE on a clean Kubuntu system. All the installation takes place in vmware virtual machine and at the end of the installation the script will create a tar.gz image of the vmware disk directory structure. This tar.gz image will be used for creating the dvd image.<br />
<br />
;build-dvd/build-cd.sh<br />
:This script takes the tar.gz image created by the install_in_vmware.sh script and generates the bootable dvd image. For generating the bootable dvd image this script also needs<br />
:*The content of a striped squashfs image found on the Kubuntu CD : ''/var/lmce-build/lite-installer/ubuntu-squashfs-base.tgz''<br />
:*The content of a Kubuntu CD without the squashfs file: ''/var/lmce-build/lite-installer/ubutu-livecd.tgz''<br />
<br />
== First Time Build ==<br />
At this point you should already have the Kubuntu system installed and some basic knowledge of what each build script is doing. I recommend running the each script by hand for the first time and not use the ''build.sh'' or ''prepare.sh'' scripts. It will be a lot easer to debug problems this way.<br />
<br />
===Runing the prepare script===<br />
This set of scripts should be run only once to prepare a Kubuntu system to act as a build server. The order is not so important for them but I recomend to stick with it. You'll need to run all the script as ''root'' as they will need write access in several directories.<br />
<br />
* The next script will create the /etc/lmce-build configuration directory and copy all the default configuration files there. The default files are stored in the ''conf-files'' folder and spited other folders depending on release and architecture. I recommend you check the ''install.sh'' script to see how it does this before running it.<br />
./install.sh<br />
* Install the build dependencies. Takes aprox. 30min depending on you internet connection speed. The packages that get installed are listed in ''/etc/lmce-build/build-packages'':<br />
./prepare-scripts/install-build-pkgs.sh<br />
* Download Ubuntu packages needed by CD1&2. The downloded packages are liste in files ''/etc/lmce-build/cd1-packages'' and ''/etc/lmce-build/cd2-packages''<br />
./prepare-scripts/cd1-prepare.sh<br />
./prepare-scripts/cd2-prepare.sh<br />
* Download Ubuntu packages found on a default Kubuntu CD. This ones are used when installing the system in vmware:<br />
mkdir -p /var/lmce-build/kubuntu-cd<br />
pushd /var/lmce-build/kubuntu-cd<br />
aptitude download `cat /etc/lmce-build/cdK-packages`<br />
popd<br />
* Run the other prepare scripts :<br />
./prepare-scripts/create-diskless-debootstrap.sh<br />
./prepare-scripts/import-external-files.sh<br />
./prepare-scripts/preseed-build-pkgs.sh<br />
<br />
===Preparing for DVD Creation===<br />
If you want only to be able to create linuxmce packages and create the standard CDs you can skip this steps. This steps are only needed for creating the DVD and involve some advanced skills as you must manually do most of the things here.<br />
<br />
* Create the ''/var/lmce-build/lite-installer/ubuntu-livecd.tgz'' and ''/var/lmce-build/lite-installer/ubuntu-squashfs-base.tgz'' archives that are used as a base of the LinuxMCE DVD:<br />
**'''ubuntu-livecd.tgz''': This is the simple one. It contains the all files from the kubnuntu dvd except for the squashfs image file. The steps to create this file are:<br />
**#Mount the kubuntu cd<br />
**#Copy the contents of the cd in a directory<br />
**#Remove the squashfs image from the directory (casper/filesystem.squashfs)<br />
**#Create a the tar.gz<br />
**'''filesystem.squashfs''': You'll need to use the ''casper/filesystem.squashfs'' which you eliminate in creation of the previous tar.gz:<br />
**#Mount the squashfs image in a directory<br />
**#Copy the entire chroot content into another directory so you can modify it<br />
**#Chroot in the new directory and uinstall all the x11/kde related packages<br />
**#Exit the chroot and targz what is left of the unpacked squashfs image<br />
* Create the vmware virtual machine and install vmware player:<br />
**The build scripts expect a vmware virtual machine that can be started with vmware player. It's important for the disk image of the vmware machine to be in a 'flat' format, meaning that will not be splited in 2G files and all the disk space is allocated from the start, i use 15G virtual disks. Second, make sure that the network is set on nat. It's important the the virtual machine to be named 'Kubuntu'.<br />
**Install a Kubuntu CD on the virtual machine.<br />
**Copy the ssh public key (''/etc/lmce-build/builder.key.pub'') in the virtual machine and make sure that you can ssh using the private key from you system (''/etc/lmce-build/builder.key'') into root on you vmware machine.<br />
**Add an entry in /etc/hosts with hostname 'vmware' and ip of your vmware machine<br />
**Leave virtual machine powered up and shutdown vmware. This way the next time you start the virtual machine you will be able to login quickly with ssh on it.<br />
**Copy all the files of the virtual machine in ''/var/Kubuntu''</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Building_LinuxMCE_0804&diff=10969Building LinuxMCE 08042008-05-13T12:15:15Z<p>Razvang: /* Preparing for DVD Creation */</p>
<hr />
<div>With this tutorial I'll try to summarize the step involved in building the LinuxMCE CDs and DVDs together with some changes that I've done when switching from Kubuntu 0704 to Kubuntu 0710.<br />
<br />
== Requirements ==<br />
''Requirements'':<br />
* Powerful enough system to do the compilation and building of packages as is a cpu intensive task and it can take quite a long time.<br />
* Lot of disk space, at least 40G hard drive.<br />
* A working internet connection as the build and preparation process will need to access get some files from the public domain.<br />
<br />
''First Steps'':<br />
* Install Kubuntu 0804. I use the desktop installation CD and i would recommend to do the same as this steps will consider this kind of installation performed. Of course an Ubuntu Server or Alternate CD will work too but you may need to install some build dependencies / runtime libraries that I have by default installed on Kubuntu 0804.<br />
* Install some subversion so you can checkout a copy of the build script from LinuxMCE's svn.<br />
apt-get install subversion<br />
<br />
== Build Scripts ==<br />
The next step after having 0804 installed is to get a copy of the build script:<br />
sudo su<br />
cd $HOME<br />
svn co http://svn.linuxmce.com/pluto/trunk/src/Ubuntu_Helpers_NoHardcode/<br />
mv Ubuntu_Helpers_NoHardcode/ /usr/local/lmce-build<br />
<br />
I will try to explain them quickly so you'll know what each of them does.<br />
;build.sh<br />
:This is the main script and calls all the other script of the build process to perform simple task.<br />
<br />
;loop-build.sh<br />
:This is a script used on our build machines and it does the next steps in a infinite loop: <br />
:#Calls ''build.sh'' script to performa a build. <br />
:#Stores the build output in a ftp viewable directory.<br />
:#Sends mail to developers on fail and on success.<br />
<br />
=== Scripts used for preaparing the build system ===<br />
;prepare-scripts/install-build-pkgs.sh<br />
:This script will download and install all the build dependencies needed to create the linuxmce packages.<br />
<br />
;prepare-scripts/cd1-prepare.sh<br />
:Download the ubuntu packages that will be copied on LinuxMCE CD1<br />
<br />
;prepare-scripts/cd2-packages.sh<br />
:Download the ubuntu packages that will be copied on LinuxMCE CD2<br />
<br />
;prepare-scripts/create-diskless-debootstrap.sh<br />
:Creates a debootsrap image used later as a base for creating the diskless image.<br />
<br />
;prepare-script/import-external-files.sh<br />
:Downloads the linuxmce media file : skins, demo videos ..<br />
<br />
;prepare-script/preseed-build-pkgs.sh:<br />
:It was used to preseed some src packages like lirc-module so that they will build in a non interactive mode by the build process. It is not used for 0804.<br />
<br />
=== Scripts used for building CDs === <br />
;build-scripts/checkout-svn.sh<br />
:Gets a updated copy of the source tree from svn and stores it in ''/var/lmce-build/svn/''<br />
<br />
;build-script/import-win32bins.sh<br />
:Copies the latest windows binaries from the linuxmce ftp <br />
<br />
;buils-script/build-replacements.sh<br />
:Creates a set of non-linuxmce-specific deb packages which don't usually come with Ubuntu but are needed by our applications. It may also build some packages that are already in Ubuntu but are patched and needs to be repacked. The sources for this debs are located in trunk/ubuntu directory of the svn this means /var/lmce-build/svn/trunk/ubuntu on your local machine (after the svn checkout). Moust of this sources are in a deb-src format. The created debs will be stored in ''/var/lmce-build/replacements/'' directory.<br />
<br />
;build-script/build-makerelease.sh<br />
:Build a c++ linuxmce application and it's dependencies from the linuxmce svn. This application, called ''MakeRelease'' it's used to build and pack all the linuxmce packages. The output files will be stored in ''/var/lmce-build/MakeRelease/'' when the script finishes.<br />
<br />
;build-script/import-database.sh<br />
:This script takes the latest version of the LinuxMCE MySQL databases from the LinuxMCE server. The information from this databases is used by MakeRelease to build and compile the software. The databases will also be used to create some sqldumps that will be packaged on the LinuxMCE CDs and DVSs that are created.<br />
<br />
;build-scripts/build-maindebs.sh<br />
:Runs MakeRelease and based on the information from the database compiles and packs the linuxmce packages using the sources stored in ''/var/lmce-build/svn''. The created debs will be stored in ''/var/lmce-build/out/tmp'' directory.<br />
<br />
;build-scripts/get-closed-source-debs.sh<br />
:Download the latest pluto debs which are build on a remote server. This debs are compiled from source which are object of some Pluto NDAs and cannot be made public (ex: pluto-zwave).<br />
<br />
;build-script/create-repo.sh<br />
:After all the needed packages are created / downloaded, this script copies them from their output directories and stores them in ''/var/www/'' directory. It also creates a Packages.gz file so you can use that directory as a repository which you can add in sources.list.<br />
<br />
;build-script/cd1-build.sh<br />
:Creates LinuxMCE CD1. This cd will contain moust of the linuxmce specific debs but also some Ubuntu debs which are needed for by LinuxMCE application and are not installed by default in Kubuntu. The linuxmce debs are copied from ''/var/www' and the extra ubuntu debs are fetched from ''/var/lmce-build/cd1-packages/'' directory.<br />
<br />
;build-scripts/cd2-build.sh<br />
:Creates LinuxMCE CD2. This cd contains only few linuxmce debs and a lot of ubuntu debs which are not installed by default on a Kubuntu system but are needed douring the install process. The Ubuntu debs are copied from ''/var/lmce-build/cd2-packages/'' folder.<br />
<br />
=== Scripts used for building DVDs ===<br />
;vmware-install/install_in_vmware.sh<br />
:This script uses the LinuxMCE CD1&2 to automatically install LinuxMCE on a clean Kubuntu system. All the installation takes place in vmware virtual machine and at the end of the installation the script will create a tar.gz image of the vmware disk directory structure. This tar.gz image will be used for creating the dvd image.<br />
<br />
;build-dvd/build-cd.sh<br />
:This script takes the tar.gz image created by the install_in_vmware.sh script and generates the bootable dvd image. For generating the bootable dvd image this script also needs<br />
:*The content of a striped squashfs image found on the Kubuntu CD : ''/var/lmce-build/lite-installer/ubuntu-squashfs-base.tgz''<br />
:*The content of a Kubuntu CD without the squashfs file: ''/var/lmce-build/lite-installer/ubutu-livecd.tgz''<br />
<br />
== First Time Build ==<br />
At this point you should already have the Kubuntu system installed and some basic knowledge of what each build script is doing. I recommend running the each script by hand for the first time and not use the ''build.sh'' or ''prepare.sh'' scripts. It will be a lot easer to debug problems this way.<br />
<br />
===Runing the prepare script===<br />
This set of scripts should be run only once to prepare a Kubuntu system to act as a build server. The order is not so important for them but I recomend to stick with it. You'll need to run all the script as ''root'' as they will need write access in several directories.<br />
<br />
* The next script will create the /etc/lmce-build configuration directory and copy all the default configuration files there. The default files are stored in the ''conf-files'' folder and spited other folders depending on release and architecture. I recommend you check the ''install.sh'' script to see how it does this before running it.<br />
./install.sh<br />
* Install the build dependencies. Takes aprox. 30min depending on you internet connection speed. The packages that get installed are listed in ''/etc/lmce-build/build-packages'':<br />
./prepare-scripts/install-build-pkgs.sh<br />
* Download Ubuntu packages needed by CD1&2. The downloded packages are liste in files ''/etc/lmce-build/cd1-packages'' and ''/etc/lmce-build/cd2-packages''<br />
./prepare-scripts/cd1-prepare.sh<br />
./prepare-scripts/cd2-prepare.sh<br />
* Download Ubuntu packages found on a default Kubuntu CD. This ones are used when installing the system in vmware:<br />
mkdir -p /var/lmce-build/kubuntu-cd<br />
pushd /var/lmce-build/kubuntu-cd<br />
aptitude download `cat /etc/lmce-build/cdK-packages`<br />
popd<br />
* Run the other prepare scripts :<br />
./prepare-scripts/create-diskless-debootstrap.sh<br />
./prepare-scripts/import-external-files.sh<br />
./prepare-scripts/preseed-build-pkgs.sh<br />
<br />
===Preparing for DVD Creation===<br />
If you want only to be able to create linuxmce packages and create the standard CDs you can skip this steps. This steps are only needed for creating the DVD and involve some advanced skills as you must manually do most of the things here.<br />
<br />
* Create the ''/var/lmce-build/lite-installer/ubuntu-livecd.tgz'' and ''/var/lmce-build/lite-installer/ubuntu-squashfs-base.tgz'' archives that are used as a base of the LinuxMCE DVD:<br />
**'''ubuntu-livecd.tgz''': This is the simple one. It contains the all files from the kubnuntu dvd except for the squashfs image file. The steps to create this file are:<br />
**#Mount the kubuntu cd<br />
**#Copy the contents of the cd in a directory<br />
**#Remove the squashfs image from the directory (casper/filesystem.squashfs)<br />
**#Create a the tar.gz<br />
**'''filesystem.squashfs''': You'll need to use the ''casper/filesystem.squashfs'' which you eliminate in creation of the previous tar.gz:<br />
**#Mount the squashfs image in a directory<br />
**#Copy the entire chroot content into another directory so you can modify it<br />
**#Chroot in the new directory and uinstall all the x11/kde related packages<br />
**#Exit the chroot and targz what is left of the unpacked squashfs image</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Building_LinuxMCE_0804&diff=10968Building LinuxMCE 08042008-05-13T11:12:57Z<p>Razvang: /* First Time Build */</p>
<hr />
<div>With this tutorial I'll try to summarize the step involved in building the LinuxMCE CDs and DVDs together with some changes that I've done when switching from Kubuntu 0704 to Kubuntu 0710.<br />
<br />
== Requirements ==<br />
''Requirements'':<br />
* Powerful enough system to do the compilation and building of packages as is a cpu intensive task and it can take quite a long time.<br />
* Lot of disk space, at least 40G hard drive.<br />
* A working internet connection as the build and preparation process will need to access get some files from the public domain.<br />
<br />
''First Steps'':<br />
* Install Kubuntu 0804. I use the desktop installation CD and i would recommend to do the same as this steps will consider this kind of installation performed. Of course an Ubuntu Server or Alternate CD will work too but you may need to install some build dependencies / runtime libraries that I have by default installed on Kubuntu 0804.<br />
* Install some subversion so you can checkout a copy of the build script from LinuxMCE's svn.<br />
apt-get install subversion<br />
<br />
== Build Scripts ==<br />
The next step after having 0804 installed is to get a copy of the build script:<br />
sudo su<br />
cd $HOME<br />
svn co http://svn.linuxmce.com/pluto/trunk/src/Ubuntu_Helpers_NoHardcode/<br />
mv Ubuntu_Helpers_NoHardcode/ /usr/local/lmce-build<br />
<br />
I will try to explain them quickly so you'll know what each of them does.<br />
;build.sh<br />
:This is the main script and calls all the other script of the build process to perform simple task.<br />
<br />
;loop-build.sh<br />
:This is a script used on our build machines and it does the next steps in a infinite loop: <br />
:#Calls ''build.sh'' script to performa a build. <br />
:#Stores the build output in a ftp viewable directory.<br />
:#Sends mail to developers on fail and on success.<br />
<br />
=== Scripts used for preaparing the build system ===<br />
;prepare-scripts/install-build-pkgs.sh<br />
:This script will download and install all the build dependencies needed to create the linuxmce packages.<br />
<br />
;prepare-scripts/cd1-prepare.sh<br />
:Download the ubuntu packages that will be copied on LinuxMCE CD1<br />
<br />
;prepare-scripts/cd2-packages.sh<br />
:Download the ubuntu packages that will be copied on LinuxMCE CD2<br />
<br />
;prepare-scripts/create-diskless-debootstrap.sh<br />
:Creates a debootsrap image used later as a base for creating the diskless image.<br />
<br />
;prepare-script/import-external-files.sh<br />
:Downloads the linuxmce media file : skins, demo videos ..<br />
<br />
;prepare-script/preseed-build-pkgs.sh:<br />
:It was used to preseed some src packages like lirc-module so that they will build in a non interactive mode by the build process. It is not used for 0804.<br />
<br />
=== Scripts used for building CDs === <br />
;build-scripts/checkout-svn.sh<br />
:Gets a updated copy of the source tree from svn and stores it in ''/var/lmce-build/svn/''<br />
<br />
;build-script/import-win32bins.sh<br />
:Copies the latest windows binaries from the linuxmce ftp <br />
<br />
;buils-script/build-replacements.sh<br />
:Creates a set of non-linuxmce-specific deb packages which don't usually come with Ubuntu but are needed by our applications. It may also build some packages that are already in Ubuntu but are patched and needs to be repacked. The sources for this debs are located in trunk/ubuntu directory of the svn this means /var/lmce-build/svn/trunk/ubuntu on your local machine (after the svn checkout). Moust of this sources are in a deb-src format. The created debs will be stored in ''/var/lmce-build/replacements/'' directory.<br />
<br />
;build-script/build-makerelease.sh<br />
:Build a c++ linuxmce application and it's dependencies from the linuxmce svn. This application, called ''MakeRelease'' it's used to build and pack all the linuxmce packages. The output files will be stored in ''/var/lmce-build/MakeRelease/'' when the script finishes.<br />
<br />
;build-script/import-database.sh<br />
:This script takes the latest version of the LinuxMCE MySQL databases from the LinuxMCE server. The information from this databases is used by MakeRelease to build and compile the software. The databases will also be used to create some sqldumps that will be packaged on the LinuxMCE CDs and DVSs that are created.<br />
<br />
;build-scripts/build-maindebs.sh<br />
:Runs MakeRelease and based on the information from the database compiles and packs the linuxmce packages using the sources stored in ''/var/lmce-build/svn''. The created debs will be stored in ''/var/lmce-build/out/tmp'' directory.<br />
<br />
;build-scripts/get-closed-source-debs.sh<br />
:Download the latest pluto debs which are build on a remote server. This debs are compiled from source which are object of some Pluto NDAs and cannot be made public (ex: pluto-zwave).<br />
<br />
;build-script/create-repo.sh<br />
:After all the needed packages are created / downloaded, this script copies them from their output directories and stores them in ''/var/www/'' directory. It also creates a Packages.gz file so you can use that directory as a repository which you can add in sources.list.<br />
<br />
;build-script/cd1-build.sh<br />
:Creates LinuxMCE CD1. This cd will contain moust of the linuxmce specific debs but also some Ubuntu debs which are needed for by LinuxMCE application and are not installed by default in Kubuntu. The linuxmce debs are copied from ''/var/www' and the extra ubuntu debs are fetched from ''/var/lmce-build/cd1-packages/'' directory.<br />
<br />
;build-scripts/cd2-build.sh<br />
:Creates LinuxMCE CD2. This cd contains only few linuxmce debs and a lot of ubuntu debs which are not installed by default on a Kubuntu system but are needed douring the install process. The Ubuntu debs are copied from ''/var/lmce-build/cd2-packages/'' folder.<br />
<br />
=== Scripts used for building DVDs ===<br />
;vmware-install/install_in_vmware.sh<br />
:This script uses the LinuxMCE CD1&2 to automatically install LinuxMCE on a clean Kubuntu system. All the installation takes place in vmware virtual machine and at the end of the installation the script will create a tar.gz image of the vmware disk directory structure. This tar.gz image will be used for creating the dvd image.<br />
<br />
;build-dvd/build-cd.sh<br />
:This script takes the tar.gz image created by the install_in_vmware.sh script and generates the bootable dvd image. For generating the bootable dvd image this script also needs<br />
:*The content of a striped squashfs image found on the Kubuntu CD : ''/var/lmce-build/lite-installer/ubuntu-squashfs-base.tgz''<br />
:*The content of a Kubuntu CD without the squashfs file: ''/var/lmce-build/lite-installer/ubutu-livecd.tgz''<br />
<br />
== First Time Build ==<br />
At this point you should already have the Kubuntu system installed and some basic knowledge of what each build script is doing. I recommend running the each script by hand for the first time and not use the ''build.sh'' or ''prepare.sh'' scripts. It will be a lot easer to debug problems this way.<br />
<br />
===Runing the prepare script===<br />
This set of scripts should be run only once to prepare a Kubuntu system to act as a build server. The order is not so important for them but I recomend to stick with it. You'll need to run all the script as ''root'' as they will need write access in several directories.<br />
<br />
* The next script will create the /etc/lmce-build configuration directory and copy all the default configuration files there. The default files are stored in the ''conf-files'' folder and spited other folders depending on release and architecture. I recommend you check the ''install.sh'' script to see how it does this before running it.<br />
./install.sh<br />
* Install the build dependencies. Takes aprox. 30min depending on you internet connection speed. The packages that get installed are listed in ''/etc/lmce-build/build-packages'':<br />
./prepare-scripts/install-build-pkgs.sh<br />
* Download Ubuntu packages needed by CD1&2. The downloded packages are liste in files ''/etc/lmce-build/cd1-packages'' and ''/etc/lmce-build/cd2-packages''<br />
./prepare-scripts/cd1-prepare.sh<br />
./prepare-scripts/cd2-prepare.sh<br />
* Download Ubuntu packages found on a default Kubuntu CD. This ones are used when installing the system in vmware:<br />
mkdir -p /var/lmce-build/kubuntu-cd<br />
pushd /var/lmce-build/kubuntu-cd<br />
aptitude download `cat /etc/lmce-build/cdK-packages`<br />
popd<br />
* Run the other prepare scripts :<br />
./prepare-scripts/create-diskless-debootstrap.sh<br />
./prepare-scripts/import-external-files.sh<br />
./prepare-scripts/preseed-build-pkgs.sh<br />
<br />
===Preparing for DVD Creation===<br />
If you want only to be able to create linuxmce packages and create the standard CDs you can skip this steps. This steps are only needed for creating the DVD and involve some advanced skills as you must manually do most of the things here.<br />
<br />
* Create the ''/var/lmce-build/lite-installer/ubuntu-livecd.tgz'' and ''/var/lmce-build/lite-installer/ubuntu-squashfs-base.tgz'' archives that are used as a base of the LinuxMCE DVD:<br />
**'''ubuntu-livecd.tgz''': This is the simple one. It contains the Un</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Building_LinuxMCE_0804&diff=10967Building LinuxMCE 08042008-05-13T11:08:04Z<p>Razvang: /* First Build */</p>
<hr />
<div>With this tutorial I'll try to summarize the step involved in building the LinuxMCE CDs and DVDs together with some changes that I've done when switching from Kubuntu 0704 to Kubuntu 0710.<br />
<br />
== Requirements ==<br />
''Requirements'':<br />
* Powerful enough system to do the compilation and building of packages as is a cpu intensive task and it can take quite a long time.<br />
* Lot of disk space, at least 40G hard drive.<br />
* A working internet connection as the build and preparation process will need to access get some files from the public domain.<br />
<br />
''First Steps'':<br />
* Install Kubuntu 0804. I use the desktop installation CD and i would recommend to do the same as this steps will consider this kind of installation performed. Of course an Ubuntu Server or Alternate CD will work too but you may need to install some build dependencies / runtime libraries that I have by default installed on Kubuntu 0804.<br />
* Install some subversion so you can checkout a copy of the build script from LinuxMCE's svn.<br />
apt-get install subversion<br />
<br />
== Build Scripts ==<br />
The next step after having 0804 installed is to get a copy of the build script:<br />
sudo su<br />
cd $HOME<br />
svn co http://svn.linuxmce.com/pluto/trunk/src/Ubuntu_Helpers_NoHardcode/<br />
mv Ubuntu_Helpers_NoHardcode/ /usr/local/lmce-build<br />
<br />
I will try to explain them quickly so you'll know what each of them does.<br />
;build.sh<br />
:This is the main script and calls all the other script of the build process to perform simple task.<br />
<br />
;loop-build.sh<br />
:This is a script used on our build machines and it does the next steps in a infinite loop: <br />
:#Calls ''build.sh'' script to performa a build. <br />
:#Stores the build output in a ftp viewable directory.<br />
:#Sends mail to developers on fail and on success.<br />
<br />
=== Scripts used for preaparing the build system ===<br />
;prepare-scripts/install-build-pkgs.sh<br />
:This script will download and install all the build dependencies needed to create the linuxmce packages.<br />
<br />
;prepare-scripts/cd1-prepare.sh<br />
:Download the ubuntu packages that will be copied on LinuxMCE CD1<br />
<br />
;prepare-scripts/cd2-packages.sh<br />
:Download the ubuntu packages that will be copied on LinuxMCE CD2<br />
<br />
;prepare-scripts/create-diskless-debootstrap.sh<br />
:Creates a debootsrap image used later as a base for creating the diskless image.<br />
<br />
;prepare-script/import-external-files.sh<br />
:Downloads the linuxmce media file : skins, demo videos ..<br />
<br />
;prepare-script/preseed-build-pkgs.sh:<br />
:It was used to preseed some src packages like lirc-module so that they will build in a non interactive mode by the build process. It is not used for 0804.<br />
<br />
=== Scripts used for building CDs === <br />
;build-scripts/checkout-svn.sh<br />
:Gets a updated copy of the source tree from svn and stores it in ''/var/lmce-build/svn/''<br />
<br />
;build-script/import-win32bins.sh<br />
:Copies the latest windows binaries from the linuxmce ftp <br />
<br />
;buils-script/build-replacements.sh<br />
:Creates a set of non-linuxmce-specific deb packages which don't usually come with Ubuntu but are needed by our applications. It may also build some packages that are already in Ubuntu but are patched and needs to be repacked. The sources for this debs are located in trunk/ubuntu directory of the svn this means /var/lmce-build/svn/trunk/ubuntu on your local machine (after the svn checkout). Moust of this sources are in a deb-src format. The created debs will be stored in ''/var/lmce-build/replacements/'' directory.<br />
<br />
;build-script/build-makerelease.sh<br />
:Build a c++ linuxmce application and it's dependencies from the linuxmce svn. This application, called ''MakeRelease'' it's used to build and pack all the linuxmce packages. The output files will be stored in ''/var/lmce-build/MakeRelease/'' when the script finishes.<br />
<br />
;build-script/import-database.sh<br />
:This script takes the latest version of the LinuxMCE MySQL databases from the LinuxMCE server. The information from this databases is used by MakeRelease to build and compile the software. The databases will also be used to create some sqldumps that will be packaged on the LinuxMCE CDs and DVSs that are created.<br />
<br />
;build-scripts/build-maindebs.sh<br />
:Runs MakeRelease and based on the information from the database compiles and packs the linuxmce packages using the sources stored in ''/var/lmce-build/svn''. The created debs will be stored in ''/var/lmce-build/out/tmp'' directory.<br />
<br />
;build-scripts/get-closed-source-debs.sh<br />
:Download the latest pluto debs which are build on a remote server. This debs are compiled from source which are object of some Pluto NDAs and cannot be made public (ex: pluto-zwave).<br />
<br />
;build-script/create-repo.sh<br />
:After all the needed packages are created / downloaded, this script copies them from their output directories and stores them in ''/var/www/'' directory. It also creates a Packages.gz file so you can use that directory as a repository which you can add in sources.list.<br />
<br />
;build-script/cd1-build.sh<br />
:Creates LinuxMCE CD1. This cd will contain moust of the linuxmce specific debs but also some Ubuntu debs which are needed for by LinuxMCE application and are not installed by default in Kubuntu. The linuxmce debs are copied from ''/var/www' and the extra ubuntu debs are fetched from ''/var/lmce-build/cd1-packages/'' directory.<br />
<br />
;build-scripts/cd2-build.sh<br />
:Creates LinuxMCE CD2. This cd contains only few linuxmce debs and a lot of ubuntu debs which are not installed by default on a Kubuntu system but are needed douring the install process. The Ubuntu debs are copied from ''/var/lmce-build/cd2-packages/'' folder.<br />
<br />
=== Scripts used for building DVDs ===<br />
;vmware-install/install_in_vmware.sh<br />
:This script uses the LinuxMCE CD1&2 to automatically install LinuxMCE on a clean Kubuntu system. All the installation takes place in vmware virtual machine and at the end of the installation the script will create a tar.gz image of the vmware disk directory structure. This tar.gz image will be used for creating the dvd image.<br />
<br />
;build-dvd/build-cd.sh<br />
:This script takes the tar.gz image created by the install_in_vmware.sh script and generates the bootable dvd image. For generating the bootable dvd image this script also needs<br />
:*The content of a striped squashfs image found on the Kubuntu CD : ''/var/lmce-build/lite-installer/ubuntu-squashfs-base.tgz''<br />
:*The content of a Kubuntu CD without the squashfs file: ''/var/lmce-build/lite-installer/ubutu-livecd.tgz''<br />
<br />
== First Time Build ==<br />
At this point you should already have the Kubuntu system installed and some basic knowledge of what each build script is doing. I recommend running the each script by hand for the first time and not use the ''build.sh'' or ''prepare.sh'' scripts. It will be a lot easer to debug problems this way.<br />
<br />
===Runing the prepare script===<br />
This set of scripts should be run only once to prepare a Kubuntu system to act as a build server. The order is not so important for them but I recomend to stick with it. You'll need to run all the script as ''root'' as they will need write access in several directories.<br />
<br />
* The next script will create the /etc/lmce-build configuration directory and copy all the default configuration files there. The default files are stored in the ''conf-files'' folder and spited other folders depending on release and architecture. I recommend you check the ''install.sh'' script to see how it does this before running it.<br />
./install.sh<br />
* Install the build dependencies. Takes aprox. 30min depending on you internet connection speed. The packages that get installed are listed in ''/etc/lmce-build/build-packages'':<br />
./prepare-scripts/install-build-pkgs.sh<br />
* Download Ubuntu packages needed by CD1&2. The downloded packages are liste in files ''/etc/lmce-build/cd1-packages'' and ''/etc/lmce-build/cd2-packages''<br />
./prepare-scripts/cd1-prepare.sh<br />
./prepare-scripts/cd2-prepare.sh<br />
* Download Ubuntu packages found on a default Kubuntu CD. This ones are used when installing the system in vmware:<br />
mkdir -p /var/lmce-build/kubuntu-cd<br />
pushd /var/lmce-build/kubuntu-cd<br />
aptitude download `cat /etc/lmce-build/cdK-packages`<br />
popd<br />
* Run the other prepare scripts :<br />
./prepare-scripts/create-diskless-debootstrap.sh<br />
./prepare-scripts/import-external-files.sh<br />
./prepare-scripts/preseed-build-pkgs.sh</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Building_LinuxMCE_0804&diff=10966Building LinuxMCE 08042008-05-13T10:48:46Z<p>Razvang: /* Scripts used for building DVDs */</p>
<hr />
<div>With this tutorial I'll try to summarize the step involved in building the LinuxMCE CDs and DVDs together with some changes that I've done when switching from Kubuntu 0704 to Kubuntu 0710.<br />
<br />
== Requirements ==<br />
''Requirements'':<br />
* Powerful enough system to do the compilation and building of packages as is a cpu intensive task and it can take quite a long time.<br />
* Lot of disk space, at least 40G hard drive.<br />
* A working internet connection as the build and preparation process will need to access get some files from the public domain.<br />
<br />
''First Steps'':<br />
* Install Kubuntu 0804. I use the desktop installation CD and i would recommend to do the same as this steps will consider this kind of installation performed. Of course an Ubuntu Server or Alternate CD will work too but you may need to install some build dependencies / runtime libraries that I have by default installed on Kubuntu 0804.<br />
* Install some subversion so you can checkout a copy of the build script from LinuxMCE's svn.<br />
apt-get install subversion<br />
<br />
== Build Scripts ==<br />
The next step after having 0804 installed is to get a copy of the build script:<br />
sudo su<br />
cd $HOME<br />
svn co http://svn.linuxmce.com/pluto/trunk/src/Ubuntu_Helpers_NoHardcode/<br />
mv Ubuntu_Helpers_NoHardcode/ /usr/local/lmce-build<br />
<br />
I will try to explain them quickly so you'll know what each of them does.<br />
;build.sh<br />
:This is the main script and calls all the other script of the build process to perform simple task.<br />
<br />
;loop-build.sh<br />
:This is a script used on our build machines and it does the next steps in a infinite loop: <br />
:#Calls ''build.sh'' script to performa a build. <br />
:#Stores the build output in a ftp viewable directory.<br />
:#Sends mail to developers on fail and on success.<br />
<br />
=== Scripts used for preaparing the build system ===<br />
;prepare-scripts/install-build-pkgs.sh<br />
:This script will download and install all the build dependencies needed to create the linuxmce packages.<br />
<br />
;prepare-scripts/cd1-prepare.sh<br />
:Download the ubuntu packages that will be copied on LinuxMCE CD1<br />
<br />
;prepare-scripts/cd2-packages.sh<br />
:Download the ubuntu packages that will be copied on LinuxMCE CD2<br />
<br />
;prepare-scripts/create-diskless-debootstrap.sh<br />
:Creates a debootsrap image used later as a base for creating the diskless image.<br />
<br />
;prepare-script/import-external-files.sh<br />
:Downloads the linuxmce media file : skins, demo videos ..<br />
<br />
;prepare-script/preseed-build-pkgs.sh:<br />
:It was used to preseed some src packages like lirc-module so that they will build in a non interactive mode by the build process. It is not used for 0804.<br />
<br />
=== Scripts used for building CDs === <br />
;build-scripts/checkout-svn.sh<br />
:Gets a updated copy of the source tree from svn and stores it in ''/var/lmce-build/svn/''<br />
<br />
;build-script/import-win32bins.sh<br />
:Copies the latest windows binaries from the linuxmce ftp <br />
<br />
;buils-script/build-replacements.sh<br />
:Creates a set of non-linuxmce-specific deb packages which don't usually come with Ubuntu but are needed by our applications. It may also build some packages that are already in Ubuntu but are patched and needs to be repacked. The sources for this debs are located in trunk/ubuntu directory of the svn this means /var/lmce-build/svn/trunk/ubuntu on your local machine (after the svn checkout). Moust of this sources are in a deb-src format. The created debs will be stored in ''/var/lmce-build/replacements/'' directory.<br />
<br />
;build-script/build-makerelease.sh<br />
:Build a c++ linuxmce application and it's dependencies from the linuxmce svn. This application, called ''MakeRelease'' it's used to build and pack all the linuxmce packages. The output files will be stored in ''/var/lmce-build/MakeRelease/'' when the script finishes.<br />
<br />
;build-script/import-database.sh<br />
:This script takes the latest version of the LinuxMCE MySQL databases from the LinuxMCE server. The information from this databases is used by MakeRelease to build and compile the software. The databases will also be used to create some sqldumps that will be packaged on the LinuxMCE CDs and DVSs that are created.<br />
<br />
;build-scripts/build-maindebs.sh<br />
:Runs MakeRelease and based on the information from the database compiles and packs the linuxmce packages using the sources stored in ''/var/lmce-build/svn''. The created debs will be stored in ''/var/lmce-build/out/tmp'' directory.<br />
<br />
;build-scripts/get-closed-source-debs.sh<br />
:Download the latest pluto debs which are build on a remote server. This debs are compiled from source which are object of some Pluto NDAs and cannot be made public (ex: pluto-zwave).<br />
<br />
;build-script/create-repo.sh<br />
:After all the needed packages are created / downloaded, this script copies them from their output directories and stores them in ''/var/www/'' directory. It also creates a Packages.gz file so you can use that directory as a repository which you can add in sources.list.<br />
<br />
;build-script/cd1-build.sh<br />
:Creates LinuxMCE CD1. This cd will contain moust of the linuxmce specific debs but also some Ubuntu debs which are needed for by LinuxMCE application and are not installed by default in Kubuntu. The linuxmce debs are copied from ''/var/www' and the extra ubuntu debs are fetched from ''/var/lmce-build/cd1-packages/'' directory.<br />
<br />
;build-scripts/cd2-build.sh<br />
:Creates LinuxMCE CD2. This cd contains only few linuxmce debs and a lot of ubuntu debs which are not installed by default on a Kubuntu system but are needed douring the install process. The Ubuntu debs are copied from ''/var/lmce-build/cd2-packages/'' folder.<br />
<br />
=== Scripts used for building DVDs ===<br />
;vmware-install/install_in_vmware.sh<br />
:This script uses the LinuxMCE CD1&2 to automatically install LinuxMCE on a clean Kubuntu system. All the installation takes place in vmware virtual machine and at the end of the installation the script will create a tar.gz image of the vmware disk directory structure. This tar.gz image will be used for creating the dvd image.<br />
<br />
;build-dvd/build-cd.sh<br />
:This script takes the tar.gz image created by the install_in_vmware.sh script and generates the bootable dvd image. For generating the bootable dvd image this script also needs<br />
:*The content of a striped squashfs image found on the Kubuntu CD : ''/var/lmce-build/lite-installer/ubuntu-squashfs-base.tgz''<br />
:*The content of a Kubuntu CD without the squashfs file: ''/var/lmce-build/lite-installer/ubutu-livecd.tgz''<br />
<br />
== First Build ==</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Building_LinuxMCE_0804&diff=10965Building LinuxMCE 08042008-05-13T10:48:13Z<p>Razvang: /* Build Scripts */</p>
<hr />
<div>With this tutorial I'll try to summarize the step involved in building the LinuxMCE CDs and DVDs together with some changes that I've done when switching from Kubuntu 0704 to Kubuntu 0710.<br />
<br />
== Requirements ==<br />
''Requirements'':<br />
* Powerful enough system to do the compilation and building of packages as is a cpu intensive task and it can take quite a long time.<br />
* Lot of disk space, at least 40G hard drive.<br />
* A working internet connection as the build and preparation process will need to access get some files from the public domain.<br />
<br />
''First Steps'':<br />
* Install Kubuntu 0804. I use the desktop installation CD and i would recommend to do the same as this steps will consider this kind of installation performed. Of course an Ubuntu Server or Alternate CD will work too but you may need to install some build dependencies / runtime libraries that I have by default installed on Kubuntu 0804.<br />
* Install some subversion so you can checkout a copy of the build script from LinuxMCE's svn.<br />
apt-get install subversion<br />
<br />
== Build Scripts ==<br />
The next step after having 0804 installed is to get a copy of the build script:<br />
sudo su<br />
cd $HOME<br />
svn co http://svn.linuxmce.com/pluto/trunk/src/Ubuntu_Helpers_NoHardcode/<br />
mv Ubuntu_Helpers_NoHardcode/ /usr/local/lmce-build<br />
<br />
I will try to explain them quickly so you'll know what each of them does.<br />
;build.sh<br />
:This is the main script and calls all the other script of the build process to perform simple task.<br />
<br />
;loop-build.sh<br />
:This is a script used on our build machines and it does the next steps in a infinite loop: <br />
:#Calls ''build.sh'' script to performa a build. <br />
:#Stores the build output in a ftp viewable directory.<br />
:#Sends mail to developers on fail and on success.<br />
<br />
=== Scripts used for preaparing the build system ===<br />
;prepare-scripts/install-build-pkgs.sh<br />
:This script will download and install all the build dependencies needed to create the linuxmce packages.<br />
<br />
;prepare-scripts/cd1-prepare.sh<br />
:Download the ubuntu packages that will be copied on LinuxMCE CD1<br />
<br />
;prepare-scripts/cd2-packages.sh<br />
:Download the ubuntu packages that will be copied on LinuxMCE CD2<br />
<br />
;prepare-scripts/create-diskless-debootstrap.sh<br />
:Creates a debootsrap image used later as a base for creating the diskless image.<br />
<br />
;prepare-script/import-external-files.sh<br />
:Downloads the linuxmce media file : skins, demo videos ..<br />
<br />
;prepare-script/preseed-build-pkgs.sh:<br />
:It was used to preseed some src packages like lirc-module so that they will build in a non interactive mode by the build process. It is not used for 0804.<br />
<br />
=== Scripts used for building CDs === <br />
;build-scripts/checkout-svn.sh<br />
:Gets a updated copy of the source tree from svn and stores it in ''/var/lmce-build/svn/''<br />
<br />
;build-script/import-win32bins.sh<br />
:Copies the latest windows binaries from the linuxmce ftp <br />
<br />
;buils-script/build-replacements.sh<br />
:Creates a set of non-linuxmce-specific deb packages which don't usually come with Ubuntu but are needed by our applications. It may also build some packages that are already in Ubuntu but are patched and needs to be repacked. The sources for this debs are located in trunk/ubuntu directory of the svn this means /var/lmce-build/svn/trunk/ubuntu on your local machine (after the svn checkout). Moust of this sources are in a deb-src format. The created debs will be stored in ''/var/lmce-build/replacements/'' directory.<br />
<br />
;build-script/build-makerelease.sh<br />
:Build a c++ linuxmce application and it's dependencies from the linuxmce svn. This application, called ''MakeRelease'' it's used to build and pack all the linuxmce packages. The output files will be stored in ''/var/lmce-build/MakeRelease/'' when the script finishes.<br />
<br />
;build-script/import-database.sh<br />
:This script takes the latest version of the LinuxMCE MySQL databases from the LinuxMCE server. The information from this databases is used by MakeRelease to build and compile the software. The databases will also be used to create some sqldumps that will be packaged on the LinuxMCE CDs and DVSs that are created.<br />
<br />
;build-scripts/build-maindebs.sh<br />
:Runs MakeRelease and based on the information from the database compiles and packs the linuxmce packages using the sources stored in ''/var/lmce-build/svn''. The created debs will be stored in ''/var/lmce-build/out/tmp'' directory.<br />
<br />
;build-scripts/get-closed-source-debs.sh<br />
:Download the latest pluto debs which are build on a remote server. This debs are compiled from source which are object of some Pluto NDAs and cannot be made public (ex: pluto-zwave).<br />
<br />
;build-script/create-repo.sh<br />
:After all the needed packages are created / downloaded, this script copies them from their output directories and stores them in ''/var/www/'' directory. It also creates a Packages.gz file so you can use that directory as a repository which you can add in sources.list.<br />
<br />
;build-script/cd1-build.sh<br />
:Creates LinuxMCE CD1. This cd will contain moust of the linuxmce specific debs but also some Ubuntu debs which are needed for by LinuxMCE application and are not installed by default in Kubuntu. The linuxmce debs are copied from ''/var/www' and the extra ubuntu debs are fetched from ''/var/lmce-build/cd1-packages/'' directory.<br />
<br />
;build-scripts/cd2-build.sh<br />
:Creates LinuxMCE CD2. This cd contains only few linuxmce debs and a lot of ubuntu debs which are not installed by default on a Kubuntu system but are needed douring the install process. The Ubuntu debs are copied from ''/var/lmce-build/cd2-packages/'' folder.<br />
<br />
=== Scripts used for building DVDs ===<br />
;vmware-install/install_in_vmware.sh<br />
:This script uses the LinuxMCE CD1&2 to automatically install LinuxMCE on a clean Kubuntu system. All the installation takes place in vmware virtual machine and at the end of the installation the script will create a tar.gz image of the vmware disk directory structure. This tar.gz image will be used for creating the dvd image.<br />
<br />
;build-dvd/build-cd.sh<br />
:This script takes the tar.gz image created by the install_in_vmware.sh script and generates the bootable dvd image. For generating the bootable dvd image this script also needs<br />
:*The content of a striped squashfs image found on the Kubuntu CD : ''/var/lmce-build/lite-installer/ubuntu-squashfs-base.tgz''<br />
:*The content of a Kubuntu CD without the squashfs file: ''/var/lmce-build/lite-installer/ubutu-livecd.tgz''</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Building_LinuxMCE_0804&diff=10964Building LinuxMCE 08042008-05-13T10:46:07Z<p>Razvang: /* Build Scripts */</p>
<hr />
<div>With this tutorial I'll try to summarize the step involved in building the LinuxMCE CDs and DVDs together with some changes that I've done when switching from Kubuntu 0704 to Kubuntu 0710.<br />
<br />
== Requirements ==<br />
''Requirements'':<br />
* Powerful enough system to do the compilation and building of packages as is a cpu intensive task and it can take quite a long time.<br />
* Lot of disk space, at least 40G hard drive.<br />
* A working internet connection as the build and preparation process will need to access get some files from the public domain.<br />
<br />
''First Steps'':<br />
* Install Kubuntu 0804. I use the desktop installation CD and i would recommend to do the same as this steps will consider this kind of installation performed. Of course an Ubuntu Server or Alternate CD will work too but you may need to install some build dependencies / runtime libraries that I have by default installed on Kubuntu 0804.<br />
* Install some subversion so you can checkout a copy of the build script from LinuxMCE's svn.<br />
apt-get install subversion<br />
<br />
== Build Scripts ==<br />
The next step after having 0804 installed is to get a copy of the build script:<br />
sudo su<br />
cd $HOME<br />
svn co http://svn.linuxmce.com/pluto/trunk/src/Ubuntu_Helpers_NoHardcode/<br />
mv Ubuntu_Helpers_NoHardcode/ /usr/local/lmce-build<br />
<br />
I will try to explain them quickly so you'll know what each of them does.<br />
;build.sh<br />
:This is the main script and calls all the other script of the build process to perform simple task.<br />
<br />
;loop-build.sh<br />
:This is a script used on our build machines and it does the next steps in a infinite loop: <br />
:#Calls ''build.sh'' script to performa a build. <br />
:#Stores the build output in a ftp viewable directory.<br />
:#Sends mail to developers on fail and on success.<br />
<br />
=== Scripts used for preaparing the build system ===<br />
;prepare-scripts/install-build-pkgs.sh<br />
:This script will download and install all the build dependencies needed to create the linuxmce packages.<br />
<br />
;prepare-scripts/cd1-prepare.sh<br />
:Download the ubuntu packages that will be copied on LinuxMCE CD1<br />
<br />
;prepare-scripts/cd2-packages.sh<br />
:Download the ubuntu packages that will be copied on LinuxMCE CD2<br />
<br />
;prepare-scripts/create-diskless-debootstrap.sh<br />
:Creates a debootsrap image used later as a base for creating the diskless image.<br />
<br />
;prepare-script/import-external-files.sh<br />
:Downloads the linuxmce media file : skins, demo videos ..<br />
<br />
;prepare-script/preseed-build-pkgs.sh:<br />
:It was used to preseed some src packages like lirc-module so that they will build in a non interactive mode by the build process. It is not used for 0804.<br />
<br />
<br />
=== Scripts used for building CDs === <br />
;build-scripts/checkout-svn.sh<br />
:Gets a updated copy of the source tree from svn and stores it in ''/var/lmce-build/svn/''<br />
<br />
;build-script/import-win32bins.sh<br />
:Copies the latest windows binaries from the linuxmce ftp <br />
<br />
;buils-script/build-replacements.sh<br />
:Creates a set of non-linuxmce-specific deb packages which don't usually come with Ubuntu but are needed by our applications. It may also build some packages that are already in Ubuntu but are patched and needs to be repacked. The sources for this debs are located in trunk/ubuntu directory of the svn this means /var/lmce-build/svn/trunk/ubuntu on your local machine (after the svn checkout). Moust of this sources are in a deb-src format. The created debs will be stored in ''/var/lmce-build/replacements/'' directory.<br />
<br />
;build-script/build-makerelease.sh<br />
:Build a c++ linuxmce application and it's dependencies from the linuxmce svn. This application, called ''MakeRelease'' it's used to build and pack all the linuxmce packages. The output files will be stored in ''/var/lmce-build/MakeRelease/'' when the script finishes.<br />
<br />
;build-script/import-database.sh<br />
:This script takes the latest version of the LinuxMCE MySQL databases from the LinuxMCE server. The information from this databases is used by MakeRelease to build and compile the software. The databases will also be used to create some sqldumps that will be packaged on the LinuxMCE CDs and DVSs that are created.<br />
<br />
;build-scripts/build-maindebs.sh<br />
:Runs MakeRelease and based on the information from the database compiles and packs the linuxmce packages using the sources stored in ''/var/lmce-build/svn''. The created debs will be stored in ''/var/lmce-build/out/tmp'' directory.<br />
<br />
;build-scripts/get-closed-source-debs.sh<br />
:Download the latest pluto debs which are build on a remote server. This debs are compiled from source which are object of some Pluto NDAs and cannot be made public (ex: pluto-zwave).<br />
<br />
;build-script/create-repo.sh<br />
:After all the needed packages are created / downloaded, this script copies them from their output directories and stores them in ''/var/www/'' directory. It also creates a Packages.gz file so you can use that directory as a repository which you can add in sources.list.<br />
<br />
;build-script/cd1-build.sh<br />
:Creates LinuxMCE CD1. This cd will contain moust of the linuxmce specific debs but also some Ubuntu debs which are needed for by LinuxMCE application and are not installed by default in Kubuntu. The linuxmce debs are copied from ''/var/www' and the extra ubuntu debs are fetched from ''/var/lmce-build/cd1-packages/'' directory.<br />
<br />
;build-scripts/cd2-build.sh<br />
:Creates LinuxMCE CD2. This cd contains only few linuxmce debs and a lot of ubuntu debs which are not installed by default on a Kubuntu system but are needed douring the install process. The Ubuntu debs are copied from ''/var/lmce-build/cd2-packages/'' folder.<br />
<br />
<br />
=== Scripts used for building DVDs ===<br />
;vmware-install/install_in_vmware.sh<br />
:This script uses the LinuxMCE CD1&2 to automatically install LinuxMCE on a clean Kubuntu system. All the installation takes place in vmware virtual machine and at the end of the installation the script will create a tar.gz image of the vmware disk directory structure. This tar.gz image will be used for creating the dvd image.<br />
<br />
;build-dvd/build-cd.sh<br />
:This script takes the tar.gz image created by the install_in_vmware.sh script and generates the bootable dvd image. For generating the bootable dvd image this script also needs<br />
:*The content of a striped squashfs image found on the Kubuntu CD : ''/var/lmce-build/lite-installer/ubuntu-squashfs-base.tgz''<br />
:*The content of a Kubuntu CD without the squashfs file: ''/var/lmce-build/lite-installer/ubutu-livecd.tgz''</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Building_LinuxMCE_0804&diff=10963Building LinuxMCE 08042008-05-13T10:34:36Z<p>Razvang: </p>
<hr />
<div>With this tutorial I'll try to summarize the step involved in building the LinuxMCE CDs and DVDs together with some changes that I've done when switching from Kubuntu 0704 to Kubuntu 0710.<br />
<br />
== Requirements ==<br />
''Requirements'':<br />
* Powerful enough system to do the compilation and building of packages as is a cpu intensive task and it can take quite a long time.<br />
* Lot of disk space, at least 40G hard drive.<br />
* A working internet connection as the build and preparation process will need to access get some files from the public domain.<br />
<br />
''First Steps'':<br />
* Install Kubuntu 0804. I use the desktop installation CD and i would recommend to do the same as this steps will consider this kind of installation performed. Of course an Ubuntu Server or Alternate CD will work too but you may need to install some build dependencies / runtime libraries that I have by default installed on Kubuntu 0804.<br />
* Install some subversion so you can checkout a copy of the build script from LinuxMCE's svn.<br />
apt-get install subversion<br />
<br />
== Build Scripts ==<br />
The next step after having 0804 installed is to get a copy of the build script:<br />
sudo su<br />
cd $HOME<br />
svn co http://svn.linuxmce.com/pluto/trunk/src/Ubuntu_Helpers_NoHardcode/<br />
mv Ubuntu_Helpers_NoHardcode/ /usr/local/lmce-build<br />
<br />
I will try to explain them quickly so you'll know what each of them does.<br />
;build.sh<br />
:This is the main script and calls all the other script of the build process to perform simple task.<br />
<br />
;loop-build.sh<br />
:This is a script used on our build machines and it does the next steps in a infinite loop: <br />
:#Calls ''build.sh'' script to performa a build. <br />
:#Stores the build output in a ftp viewable directory.<br />
:#Sends mail to developers on fail and on success.<br />
<br />
=== Scripts used for building CDs === <br />
;build-scripts/checkout-svn.sh<br />
:Gets a updated copy of the source tree from svn and stores it in ''/var/lmce-build/svn/''<br />
<br />
;build-script/import-win32bins.sh<br />
:Copies the latest windows binaries from the linuxmce ftp <br />
<br />
;buils-script/build-replacements.sh<br />
:Creates a set of non-linuxmce-specific deb packages which don't usually come with Ubuntu but are needed by our applications. It may also build some packages that are already in Ubuntu but are patched and needs to be repacked. The sources for this debs are located in trunk/ubuntu directory of the svn this means /var/lmce-build/svn/trunk/ubuntu on your local machine (after the svn checkout). Moust of this sources are in a deb-src format. The created debs will be stored in ''/var/lmce-build/replacements/'' directory.<br />
<br />
;build-script/build-makerelease.sh<br />
:Build a c++ linuxmce application and it's dependencies from the linuxmce svn. This application, called ''MakeRelease'' it's used to build and pack all the linuxmce packages. The output files will be stored in ''/var/lmce-build/MakeRelease/'' when the script finishes.<br />
<br />
;build-script/import-database.sh<br />
:This script takes the latest version of the LinuxMCE MySQL databases from the LinuxMCE server. The information from this databases is used by MakeRelease to build and compile the software. The databases will also be used to create some sqldumps that will be packaged on the LinuxMCE CDs and DVSs that are created.<br />
<br />
;build-scripts/build-maindebs.sh<br />
:Runs MakeRelease and based on the information from the database compiles and packs the linuxmce packages using the sources stored in ''/var/lmce-build/svn''. The created debs will be stored in ''/var/lmce-build/out/tmp'' directory.<br />
<br />
;build-scripts/get-closed-source-debs.sh<br />
:Download the latest pluto debs which are build on a remote server. This debs are compiled from source which are object of some Pluto NDAs and cannot be made public (ex: pluto-zwave).<br />
<br />
;build-script/create-repo.sh<br />
:After all the needed packages are created / downloaded, this script copies them from their output directories and stores them in ''/var/www/'' directory. It also creates a Packages.gz file so you can use that directory as a repository which you can add in sources.list.<br />
<br />
;build-script/cd1-build.sh<br />
:Creates LinuxMCE CD1. This cd will contain moust of the linuxmce specific debs but also some Ubuntu debs which are needed for by LinuxMCE application and are not installed by default in Kubuntu. The linuxmce debs are copied from ''/var/www' and the extra ubuntu debs are fetched from ''/var/lmce-build/cd1-packages/'' directory.<br />
<br />
;build-scripts/cd2-build.sh<br />
:Creates LinuxMCE CD2. This cd contains only few linuxmce debs and a lot of ubuntu debs which are not installed by default on a Kubuntu system but are needed douring the install process. The Ubuntu debs are copied from ''/var/lmce-build/cd2-packages/'' folder.<br />
<br />
<br />
=== Scripts used for building DVDs ===<br />
;vmware-install/install_in_vmware.sh<br />
:This script uses the LinuxMCE CD1&2 to automatically install LinuxMCE on a clean Kubuntu system. All the installation takes place in vmware virtual machine and at the end of the installation the script will create a tar.gz image of the vmware disk directory structure. This tar.gz image will be used for creating the dvd image.<br />
<br />
;build-dvd/build-cd.sh<br />
:This script takes the tar.gz image created by the install_in_vmware.sh script and generates the bootable dvd image. For generating the bootable dvd image this script also needs<br />
:*The content of a striped squashfs image found on the Kubuntu CD : ''/var/lmce-build/lite-installer/ubuntu-squashfs-base.tgz''<br />
:*The content of a Kubuntu CD without the squashfs file: ''/var/lmce-build/lite-installer/ubutu-livecd.tgz''</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Building_LinuxMCE_0804&diff=10962Building LinuxMCE 08042008-05-13T10:03:30Z<p>Razvang: /* Build Scripts */</p>
<hr />
<div>With this tutorial I'll try to summarize the step involved in building the LinuxMCE CDs and DVDs together with some changes that I've done when switching from Kubuntu 0704 to Kubuntu 0710.<br />
<br />
== Requirements ==<br />
''Requirements'':<br />
* Powerful enough system to do the compilation and building of packages as is a cpu intensive task and it can take quite a long time.<br />
* Lot of disk space, at least 40G hard drive.<br />
* A working internet connection as the build and preparation process will need to access get some files from the public domain.<br />
<br />
''First Steps'':<br />
* Install Kubuntu 0804. I use the desktop installation CD and i would recommend to do the same as this steps will consider this kind of installation performed. Of course an Ubuntu Server or Alternate CD will work too but you may need to install some build dependencies / runtime libraries that I have by default installed on Kubuntu 0804.<br />
* Install some subversion so you can checkout a copy of the build script from LinuxMCE's svn.<br />
apt-get install subversion<br />
<br />
== Build Scripts ==<br />
The next step after having 0804 installed is to get a copy of the build script:<br />
sudo su<br />
cd $HOME<br />
svn co http://svn.linuxmce.com/pluto/trunk/src/Ubuntu_Helpers_NoHardcode/<br />
mv Ubuntu_Helpers_NoHardcode/ /usr/local/lmce-build<br />
<br />
I will try to explain them quickly so you'll know what each of them does.<br />
;build.sh<br />
:This is the main script and calls all the other script of the build process to perform simple task.<br />
<br />
;loop-build.sh<br />
:This is a script used on our build machines and it does the next steps in a infinite loop: <br />
:#Calls ''build.sh'' script to performa a build. <br />
:#Stores the build output in a ftp viewable directory.<br />
:#Sends mail to developers on fail and on success.<br />
<br />
=== Scripts used for building CDs === <br />
;build-scripts/checkout-svn.sh<br />
:Gets a updated copy of the source tree from svn and stores it in ''/var/lmce-build/svn/''<br />
<br />
;build-script/import-win32bins.sh<br />
:Copies the latest windows binaries from the linuxmce ftp <br />
<br />
;buils-script/build-replacements.sh<br />
:Creates a set of non-linuxmce-specific deb packages which don't usually come with Ubuntu but are needed by our applications. It may also build some packages that are already in Ubuntu but are patched and needs to be repacked. The sources for this debs are located in trunk/ubuntu directory of the svn this means /var/lmce-build/svn/trunk/ubuntu on your local machine (after the svn checkout). Moust of this sources are in a deb-src format. The created debs will be stored in ''/var/lmce-build/replacements/'' directory.<br />
<br />
;build-script/build-makerelease.sh<br />
:Build a c++ linuxmce application and it's dependencies from the linuxmce svn. This application, called ''MakeRelease'' it's used to build and pack all the linuxmce packages. The output files will be stored in ''/var/lmce-build/MakeRelease/'' when the script finishes.<br />
<br />
;build-script/import-database.sh<br />
:This script takes the latest version of the LinuxMCE MySQL databases from the LinuxMCE server. The information from this databases is used by MakeRelease to build and compile the software. The databases will also be used to create some sqldumps that will be packaged on the LinuxMCE CDs and DVSs that are created.<br />
<br />
;build-scripts/build-maindebs.sh<br />
:Runs MakeRelease and based on the information from the database compiles and packs the linuxmce packages using the sources stored in ''/var/lmce-build/svn''. The created debs will be stored in ''/var/lmce-build/out/tmp'' directory.<br />
<br />
;build-scripts/get-closed-source-debs.sh<br />
:Download the latest pluto debs which are build on a remote server. This debs are compiled from source which are object of some Pluto NDAs and cannot be made public (ex: pluto-zwave).<br />
<br />
;build-script/create-repo.sh<br />
:After all the needed packages are created / downloaded, this script copies them from their output directories and stores them in ''/var/www/'' directory. It also creates a Packages.gz file so you can use that directory as a repository which you can add in sources.list.<br />
<br />
;build-script/cd1-build.sh<br />
:Creates LinuxMCE CD1. This cd will contain moust of the linuxmce specific debs but also some Ubuntu debs which are needed for by LinuxMCE application and are not installed by default in Kubuntu. The linuxmce debs are copied from ''/var/www' and the extra ubuntu debs are fetched from ''/var/lmce-build/cd1-packages/'' directory.<br />
<br />
;build-scripts/cd2-build.sh<br />
:Creates LinuxMCE CD2. This cd contains only few linuxmce debs and a lot of ubuntu debs which are not installed by default on a Kubuntu system but are needed douring the install process. The Ubuntu debs are copied from ''/var/lmce-build/cd2-packages/'' folder.<br />
<br />
<br />
=== Scripts used for building DVDs ===<br />
;vmware-install/install_in_vmware.sh<br />
:This script uses the LinuxMCE CD1&2 to automatically install LinuxMCE on a clean Kubuntu system. All the installation takes place in vmware virtual machine and at the end of the installation the script will create a tar.gz image of the vmware disk directory structure. This tar.gz image will be used for creating the dvd image.<br />
<br />
;build-dvd/build-cd.sh<br />
:This script takes the tar.gz image created by the install_in_vmware.sh script and generates the bootable dvd image. For generating the bootable dvd image this script also needs<br />
:*</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Building_LinuxMCE_0804&diff=10961Building LinuxMCE 08042008-05-13T09:37:49Z<p>Razvang: /* Build Scripts */</p>
<hr />
<div>With this tutorial I'll try to summarize the step involved in building the LinuxMCE CDs and DVDs together with some changes that I've done when switching from Kubuntu 0704 to Kubuntu 0710.<br />
<br />
== Requirements ==<br />
''Requirements'':<br />
* Powerful enough system to do the compilation and building of packages as is a cpu intensive task and it can take quite a long time.<br />
* Lot of disk space, at least 40G hard drive.<br />
* A working internet connection as the build and preparation process will need to access get some files from the public domain.<br />
<br />
''First Steps'':<br />
* Install Kubuntu 0804. I use the desktop installation CD and i would recommend to do the same as this steps will consider this kind of installation performed. Of course an Ubuntu Server or Alternate CD will work too but you may need to install some build dependencies / runtime libraries that I have by default installed on Kubuntu 0804.<br />
* Install some subversion so you can checkout a copy of the build script from LinuxMCE's svn.<br />
apt-get install subversion<br />
<br />
== Build Scripts ==<br />
The next step after having 0804 installed is to get a copy of the build script:<br />
sudo su<br />
cd $HOME<br />
svn co http://svn.linuxmce.com/pluto/trunk/src/Ubuntu_Helpers_NoHardcode/<br />
mv Ubuntu_Helpers_NoHardcode/ /usr/local/lmce-build<br />
<br />
I will try to explain them quickly so you'll know what each of them does.<br />
;build.sh<br />
:This is the main script and calls all the other script of the build process to perform simple task.<br />
<br />
;loop-build.sh<br />
:This is a script used on our build machines and it does the next steps in a infinite loop: <br />
:#Calls ''build.sh'' script to performa a build. <br />
:#Stores the build output in a ftp viewable directory.<br />
:#Sends mail to developers on fail and on success.<br />
<br />
;build-scripts/checkout-svn.sh<br />
:Gets a updated copy of the source tree from svn and stores it in ''/var/lmce-build/svn/''<br />
<br />
;build-script/import-win32bins.sh<br />
:Copies the latest windows binaries from the linuxmce ftp <br />
<br />
;buils-script/build-replacements.sh<br />
:Creates a set of non-linuxmce-specific deb packages which don't usually come with Ubuntu but are needed by our applications. It may also build some packages that are already in Ubuntu but are patched and needs to be repacked. The sources for this debs are located in trunk/ubuntu directory of the svn this means /var/lmce-build/svn/trunk/ubuntu on your local machine (after the svn checkout). Moust of this sources are in a deb-src format.<br />
<br />
;build-script/build-makerelease.sh<br />
:Build a c++ linuxmce application and it's dependencies from the linuxmce svn. This application, called ''MakeRelease'' it's used to build and pack all the linuxmce packages. The output files will be stored in ''/var/lmce-build/MakeRelease/'' when the script finishes.<br />
<br />
;build-script/import-database.sh<br />
:This script takes the latest version of the LinuxMCE MySQL databases from the LinuxMCE server. The information from this databases is used by MakeRelease to build and compile the software. The databases will also be used to create some sqldumps that will be packaged on the LinuxMCE CDs and DVSs that are created.<br />
<br />
;build-scripts/build-maindebs.sh</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Building_LinuxMCE_0804&diff=10960Building LinuxMCE 08042008-05-13T09:25:24Z<p>Razvang: /* Build Scripts */</p>
<hr />
<div>With this tutorial I'll try to summarize the step involved in building the LinuxMCE CDs and DVDs together with some changes that I've done when switching from Kubuntu 0704 to Kubuntu 0710.<br />
<br />
== Requirements ==<br />
''Requirements'':<br />
* Powerful enough system to do the compilation and building of packages as is a cpu intensive task and it can take quite a long time.<br />
* Lot of disk space, at least 40G hard drive.<br />
* A working internet connection as the build and preparation process will need to access get some files from the public domain.<br />
<br />
''First Steps'':<br />
* Install Kubuntu 0804. I use the desktop installation CD and i would recommend to do the same as this steps will consider this kind of installation performed. Of course an Ubuntu Server or Alternate CD will work too but you may need to install some build dependencies / runtime libraries that I have by default installed on Kubuntu 0804.<br />
* Install some subversion so you can checkout a copy of the build script from LinuxMCE's svn.<br />
apt-get install subversion<br />
<br />
== Build Scripts ==<br />
The next step after having 0804 installed is to get a copy of the build script:<br />
sudo su<br />
cd $HOME<br />
svn co http://svn.linuxmce.com/pluto/trunk/src/Ubuntu_Helpers_NoHardcode/<br />
mv Ubuntu_Helpers_NoHardcode/ /usr/local/lmce-build<br />
<br />
I will try to explain them quickly so you'll know what each of them does.<br />
;build.sh<br />
:This is the main script and calls all the other script of the build process to perform simple task.<br />
<br />
;loop-build.sh<br />
:This is a script used on our build machines and it does the next steps in a infinite loop: <br />
:#Calls ''build.sh'' script to performa a build. <br />
:#Stores the build output in a ftp viewable directory.<br />
:#Sends mail to developers on fail and on success.<br />
<br />
;build-scripts/checkout-svn.sh<br />
:Gets a updated copy of the source tree from svn and stores it in ''/var/lmce-build/svn/''<br />
<br />
;build-script/import-win32bins.sh<br />
:Copies the latest windows binaries from the linuxmce ftp <br />
<br />
;buils-script/build-replacements.sh<br />
:Creates a set of non-linuxmce-specific deb packages which don't usually come with Ubuntu but are needed by our applications. It may also build some packages that are already in Ubuntu but are patched and needs to be repacked. The sources for this debs are located in trunk/ubuntu directory of the svn this means /var/lmce-build/svn/trunk/ubuntu on your local machine (after the svn checkout). Moust of this sources are in a deb-src format.</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Building_LinuxMCE_0804&diff=10959Building LinuxMCE 08042008-05-13T09:05:31Z<p>Razvang: /* Requirements & Preparation */</p>
<hr />
<div>With this tutorial I'll try to summarize the step involved in building the LinuxMCE CDs and DVDs together with some changes that I've done when switching from Kubuntu 0704 to Kubuntu 0710.<br />
<br />
== Requirements ==<br />
''Requirements'':<br />
* Powerful enough system to do the compilation and building of packages as is a cpu intensive task and it can take quite a long time.<br />
* Lot of disk space, at least 40G hard drive.<br />
* A working internet connection as the build and preparation process will need to access get some files from the public domain.<br />
<br />
''First Steps'':<br />
* Install Kubuntu 0804. I use the desktop installation CD and i would recommend to do the same as this steps will consider this kind of installation performed. Of course an Ubuntu Server or Alternate CD will work too but you may need to install some build dependencies / runtime libraries that I have by default installed on Kubuntu 0804.<br />
* Install some subversion so you can checkout a copy of the build script from LinuxMCE's svn.<br />
apt-get install subversion<br />
<br />
== Build Scripts ==</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Building_LinuxMCE_0804&diff=10958Building LinuxMCE 08042008-05-13T09:04:23Z<p>Razvang: New page: With this tutorial I'll try to summarize the step involved in building the LinuxMCE CDs and DVDs together with some changes that I've done when switching from Kubuntu 0704 to Kubuntu 0710....</p>
<hr />
<div>With this tutorial I'll try to summarize the step involved in building the LinuxMCE CDs and DVDs together with some changes that I've done when switching from Kubuntu 0704 to Kubuntu 0710.<br />
<br />
== Requirements & Preparation ==<br />
''Requirements'':<br />
* Powerful enough system to do the compilation and building of packages as is a cpu intensive task and it can take quite a long time.<br />
* Lot of disk space, at least 40G hard drive.<br />
* A working internet connection as the build and preparation process will need to access get some files from the public domain.<br />
<br />
''Preparation'':<br />
* Install Kubuntu 0804. I use the desktop installation CD and i would recommend to do the same as this steps will consider this kind of installation performed. Of course an Ubuntu Server or Alternate CD will work too but you may need to install some build dependencies / runtime libraries that I have by default installed on Kubuntu 0804.<br />
* Install some subversion so you can checkout a copy of the build script from LinuxMCE's svn.<br />
apt-get install subversion<br />
<br />
== Build Scripts ==</div>Razvanghttp://wiki.linuxmce.org/index.php?title=GPT&diff=9819GPT2008-03-31T07:18:38Z<p>Razvang: /* Resize Existing Partitions */</p>
<hr />
<div>If you want to create partitions larger than 2TB you'll have to use GTP partitioning system instead of classical MBR. Note that you BIOS knows only MBR partitioning schema and will not likely boot from a GTP partition. You cannot mix GTP and MBR partitions on a single drive so drives larger than 2TB will need to be completely GTP and will be non-bootable; you will need a separate hard drive that contains the system.<br />
<br />
== Creating Partitions ==<br />
You'll need to use parted to create the partitions since fdisk only know to work with MBR. The next command will open a parted shell, you'll need to replace /dev/sda with the drive that you want to partition.<br />
parted /dev/sda<br />
<br />
The next commands should be typed int the parted shell.<br />
<br />
WARNING: By running this commands you will delete you partition schema and won't be able to access the information that was stored on the disk (if any).<br />
(parted) mklabel gpt <-- This one creates a empty partition table on the disk<br />
<br />
(parted) print <-- List some information about the current partition table, size of the disc<br />
<br />
(parted) mkpart primary 0 3000GB <--- Creates a partition starting from the beginning trough the 3000GB location<br />
(parted) mkpart primary 3000GB 5000GB <--- Creates another partition starting from the 3000GB locations to the 5000GB location<br />
<br />
(parted) quit <-- Exit the parted shell<br />
<br />
After doing the previous command, you should have created two partitions, a 3TB and a 2TB one. In order for udev to create /dev/sda1 and /dev/sda2 devices associated with the partitions, you need to run the next command or reboot your computer:<br />
partprobe /dev/sda<br />
<br />
== Formating the Partitions ==<br />
<br />
Except of partition creation you won't see any difference between GPT and MBR in linux. So for formatting you can do it the same way as you would format any other discs. For example:<br />
<br />
mkfs.ext3 /dev/sda1<br />
<br />
<br />
== Resize Partition Table ==<br />
If you partitioned a raid array with GPT and you later increased the size by adding more disks you must run parted again on that drive and tell it to use all available space. A simple 'print' command in parted will use the warning message to which you you need to answe 'F'.<br />
<br />
# parted /dev/sda<br />
<br />
(parted) print<br />
Warning: Not all of the space available to /dev/sda appears to be used, you can fix the GPT to use all <br />
of the space (an extra 1953103872 blocks) or continue with the current setting? <br />
Fix/Ignore? F<br />
<br />
<br />
== Resize Existing Partitions ==<br />
<br />
'''Warning:''' <span style="color: #700">Parted has some known bugs in both Ubuntu 0710 and LinuxMCE that will prevent resizing of a ext3 partition. Until this bugs get fixed the next instruction are here just for information purpose.</span><br />
<br />
Parted can also resize an existing partition to fill some unused space that you added. Before trying doing the partition resize check first that you partition is umounted and that it the filesystem on it is fine. Parted will complain about mounted partitions or inconsistent filesystem anyway.<br />
<br />
For example, let's take a 5000GB drive that has a 4000GB ext3 partition on it.<br />
(parted) print <br />
Model: AMCC 9650SE-16M DISK (scsi)<br />
Disk /dev/sda: 5000GB<br />
Sector size (logical/physical): 512B/512B<br />
Partition Table: gpt<br />
<br />
Number Start End Size File system Name Flags<br />
1 17.4kB 4000GB 4000GB ext3 primary<br />
<br />
To resize that partition, you need to use the ''resize'' parted command which has the fallowing syntax :<br />
resize <partition_no> <new_start> <new_end><br />
<br />
To transform the partition from our example from 4000GB to 5000GB :<br />
(parted) resize 1 0GB 5000GB</div>Razvanghttp://wiki.linuxmce.org/index.php?title=GPT&diff=9818GPT2008-03-31T07:18:07Z<p>Razvang: /* Resize Partition Table */</p>
<hr />
<div>If you want to create partitions larger than 2TB you'll have to use GTP partitioning system instead of classical MBR. Note that you BIOS knows only MBR partitioning schema and will not likely boot from a GTP partition. You cannot mix GTP and MBR partitions on a single drive so drives larger than 2TB will need to be completely GTP and will be non-bootable; you will need a separate hard drive that contains the system.<br />
<br />
== Creating Partitions ==<br />
You'll need to use parted to create the partitions since fdisk only know to work with MBR. The next command will open a parted shell, you'll need to replace /dev/sda with the drive that you want to partition.<br />
parted /dev/sda<br />
<br />
The next commands should be typed int the parted shell.<br />
<br />
WARNING: By running this commands you will delete you partition schema and won't be able to access the information that was stored on the disk (if any).<br />
(parted) mklabel gpt <-- This one creates a empty partition table on the disk<br />
<br />
(parted) print <-- List some information about the current partition table, size of the disc<br />
<br />
(parted) mkpart primary 0 3000GB <--- Creates a partition starting from the beginning trough the 3000GB location<br />
(parted) mkpart primary 3000GB 5000GB <--- Creates another partition starting from the 3000GB locations to the 5000GB location<br />
<br />
(parted) quit <-- Exit the parted shell<br />
<br />
After doing the previous command, you should have created two partitions, a 3TB and a 2TB one. In order for udev to create /dev/sda1 and /dev/sda2 devices associated with the partitions, you need to run the next command or reboot your computer:<br />
partprobe /dev/sda<br />
<br />
== Formating the Partitions ==<br />
<br />
Except of partition creation you won't see any difference between GPT and MBR in linux. So for formatting you can do it the same way as you would format any other discs. For example:<br />
<br />
mkfs.ext3 /dev/sda1<br />
<br />
<br />
== Resize Partition Table ==<br />
If you partitioned a raid array with GPT and you later increased the size by adding more disks you must run parted again on that drive and tell it to use all available space. A simple 'print' command in parted will use the warning message to which you you need to answe 'F'.<br />
<br />
# parted /dev/sda<br />
<br />
(parted) print<br />
Warning: Not all of the space available to /dev/sda appears to be used, you can fix the GPT to use all <br />
of the space (an extra 1953103872 blocks) or continue with the current setting? <br />
Fix/Ignore? F<br />
<br />
<br />
== Resize Existing Partitions ==<br />
<br />
'''Warning:''' <span style="color: #700">Parted has some known bugs in both Ubuntu 0710 and LinuxMCE that will prevent resizing of a ext3 partition. Utils this bugs get fixed the next instruction are here just for information purpose.</span><br />
<br />
Parted can also resize an existing partition to fill some unused space that you added. Before trying doing the partition resize check first that you partition is umounted and that it the filesystem on it is fine. Parted will complain about mounted partitions or inconsistent filesystem anyway.<br />
<br />
For example, let's take a 5000GB drive that has a 4000GB ext3 partition on it.<br />
(parted) print <br />
Model: AMCC 9650SE-16M DISK (scsi)<br />
Disk /dev/sda: 5000GB<br />
Sector size (logical/physical): 512B/512B<br />
Partition Table: gpt<br />
<br />
Number Start End Size File system Name Flags<br />
1 17.4kB 4000GB 4000GB ext3 primary<br />
<br />
To resize that partition, you need to use the ''resize'' parted command which has the fallowing syntax :<br />
resize <partition_no> <new_start> <new_end><br />
<br />
To transform the partition from our example from 4000GB to 5000GB :<br />
(parted) resize 1 0GB 5000GB</div>Razvanghttp://wiki.linuxmce.org/index.php?title=GPT&diff=9632GPT2008-03-11T13:52:10Z<p>Razvang: /* Formating the Partitions */</p>
<hr />
<div>If you want to create partitions larger than 2TB you'll have to use GTP partitioning system instead of classical MBR. Note that you BIOS knows only MBR partitioning schema and will not likely boot from a GTP partition. You cannot mix GTP and MBR partitions on a single drive so drives larger than 2TB will need to be completely GTP and will be non-bootable; you will need a separate hard drive that contains the system.<br />
<br />
== Creating Partitions ==<br />
You'll need to use parted to create the partitions since fdisk only know to work with MBR. The next command will open a parted shell, you'll need to replace /dev/sda with the drive that you want to partition.<br />
parted /dev/sda<br />
<br />
The next commands should be typed int the parted shell.<br />
<br />
WARNING: By running this commands you will delete you partition schema and won't be able to access the information that was stored on the disk (if any).<br />
(parted) mklabel gpt <-- This one creates a empty partition table on the disk<br />
<br />
(parted) print <-- List some information about the current partition table, size of the disc<br />
<br />
(parted) mkpart primary 0 3000GB <--- Creates a partition starting from the beginning trough the 3000GB location<br />
(parted) mkpart primary 3000GB 5000GB <--- Creates another partition starting from the 3000GB locations to the 5000GB location<br />
<br />
(parted) quit <-- Exit the parted shell<br />
<br />
After doing the previous command, you should have created two partitions, a 3TB and a 2TB one. In order for udev to create /dev/sda1 and /dev/sda2 devices associated with the partitions, you need to run the next command or reboot your computer:<br />
partprobe /dev/sda<br />
<br />
== Formating the Partitions ==<br />
<br />
Except of partition creation you won't see any difference between GPT and MBR in linux. So for formatting you can do it the same way as you would format any other discs. For example:<br />
<br />
mkfs.ext3 /dev/sda1<br />
<br />
<br />
== Resize Partition Table ==<br />
If you partitioned a raid array with GPT and you later increased the size by adding more disks you must run parted again on that drive and tell it to use all available space. A simple 'print' command in parted will use the warning message to which you you need to answe 'F'.<br />
<br />
# parted /dev/sda<br />
<br />
(parted) print<br />
Warning: Not all of the space available to /dev/sda appears to be used, you can fix the GPT to use all <br />
of the space (an extra 1953103872 blocks) or continue with the current setting? <br />
Fix/Ignore? F<br />
<br />
Parted can also resize an existing partition to fill some unused space that you added. Before trying doing the partition resize check first that you partition is umounted and that it the filesystem on it is fine. Parted will complain about mounted partitions or inconsistent filesystem anyway.<br />
<br />
For example, let's take a 5000GB drive that has a 4000GB ext3 partition on it.<br />
(parted) print <br />
Model: AMCC 9650SE-16M DISK (scsi)<br />
Disk /dev/sda: 5000GB<br />
Sector size (logical/physical): 512B/512B<br />
Partition Table: gpt<br />
<br />
Number Start End Size File system Name Flags<br />
1 17.4kB 4000GB 4000GB ext3 primary<br />
<br />
To resize that partition, you need to use the ''resize'' parted command which has the fallowing syntax :<br />
resize <partition_no> <new_start> <new_end><br />
<br />
To transform the partition from our example from 4000GB to 5000GB :<br />
(parted) resize 1 0GB 5000GB</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Mirrors_0710_beta_4&diff=9429Mirrors 0710 beta 42008-03-03T13:33:12Z<p>Razvang: /* LinuxMCE 0710 Beta 4 */</p>
<hr />
<div>== LinuxMCE 0710 Beta 4 ==<br />
<br />
'''Before installing, check out the [[KnownIssues_0710_Beta4]].'''<br />
<br />
To get the latest sources, use [[http://svn.linuxmce.com/pluto/trunk svn]].<br />
<br />
This wiki page is editable so users can add additional mirrors. <br />
<br />
LinuxMCE 0710 Beta 4 was released on March 3rd, 2008.<br />
<br />
'''''Warning: The DVD installation will wipe the whole disk of the machine, all previous data will be permanently lost!'''''<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" style="border-collapse:collapse; border-color:#8eabd0; background:#e7edf5"<br />
|- style="background: lightsteelblue"<br />
|-<br />
!Official Torrents:<br />
|<br />
*http://thepiratebay.org/tor/4059806 - LinuxMCE Install CDs for AMD64 - 0710 Beta 4<br />
*http://thepiratebay.org/tor/4059808 - LinuxMCE Install CDs for I386 - 0710 Beta 4<br />
*http://thepiratebay.org/tor/4059811 - LinuxMCE Install DVD for AMD64 - 0710 Beta 4<br />
*http://thepiratebay.org/tor/4059813 - LinuxMCE Install DVD for I386 - 0710 Beta 4<br />
*http://thepiratebay.org/tor/4059815 - LinuxMCE Install/Upgrade DVD for I386 - 0710 Beta 4<br />
Please help us seed! Leave your torrent open for as long as possible after your download finishes.<br />
|-<br />
|}<br />
<br />
<br />
caa718e4bddcf7230f3c7f4bc31453ab LinuxMCE-CD1-0710Beta4-amd64.iso<br />
193b2147d52e64ae77b3385bef7da187 LinuxMCE-CD2-0710Beta4-amd64.iso<br />
6ba755634fbf6403d5d599b12e240fa2 LinuxMCE-DVD-0710Beta4-amd64.iso<br />
7679241208c974b4ae14f5069583873a LinuxMCE-DVD-DL-0710Beta4-amd64.iso<br />
234ab22fb2d1924d0a880ff422f158d8 LinuxMCE-CD1-0710Beta4-i386.iso<br />
2041c2e6b3ce165b378f8d34d67cca8e LinuxMCE-CD2-0710Beta4-i386.iso<br />
705b7543af00472cb389f255acfb525e LinuxMCE-DVD-0710Beta4-i386.iso</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Version_0710_Beta4&diff=9426Version 0710 Beta42008-03-03T12:50:26Z<p>Razvang: /* March 3rd, 2008 Version 0710 beta 4 is released */</p>
<hr />
<div>==March 3rd, 2008 Version 0710 beta 4 is released==<br />
<br />
Before installing, check out the [[KnownIssues_0710_Beta4|Known issues 0710 beta 4]]. <br />
<br />
<br />
'''[http://linuxmce.com/feedback.php Feedback] please report the results of your installation and be sure to describe any problems you have, and if possible, include contact information.'''<br />
<br />
<br />
LinuxMCE is integrated into the KDE desktop and runs on Kubuntu Gutsy 7.10. Click [[ChangeLog_0710_Beta4|here]] for change log.<br />
<br />
<br />
To download:<br />
*Choose one of the torrents or mirrors here: [[Mirrors_0710_beta_4|Mirrors 0710 beta 4]]<br />
<br />
How to install : <br />
<br />
1. If you have a Kubuntu 0710 installed and you want to keep your applications settings, use CD's installation. Same steps as for 0704 (go [[Installation_Guide|here]]).<br />
<br />
2. If you want to do a quick install, use the DVD's. It will install both Kubuntul 0710 and LinuxMCE 0710. More [[DVD_Installation|here]].<br />
<br />
'''''Warning: The DVD quick installation will wipe the whole disk of the machine, all previous data will be permanently lost!'''''<br />
<br />
3. If you have LMCE 0704, you might want to try one of the following upgrade methods ( more [[Upgrade_to_0710|here]] ):<br />
<br />
- Installation using the upgrade DVD, with keep settings option (also works if you want to switch to amd64 version).<br />
<br />
- Download the upgrade helper application from [ftp://upgrade.linuxmce.com/Upgrade/gutsy-upgrade-scripts_0.1.0-2_i386.deb gutsy-upgrade-scripts_0.1.0-2_i386.deb] and choose to install from web or from DVD, if you have the double layer dvd.<br />
<br />
<br />
See also:<br />
<br />
[[FOSS_0710|FOSS 0710]] for the FOSS and development community explains what happened with the open source development after 1.1, and the current plans to develop a FOSS community<br />
<br />
<br />
[[Category:Versions]]</div>Razvanghttp://wiki.linuxmce.org/index.php?title=GPT&diff=9290GPT2008-02-29T15:44:51Z<p>Razvang: /* Formating the partitions */</p>
<hr />
<div>If you want to create partitions larger than 2TB you'll have to use GTP partitioning system instead of classical MBR. Note that you BIOS knows only MBR partitioning schema and will not likely boot from a GTP partition.<br />
<br />
== Creating Partitions ==<br />
You'll need to use parted to create the partitions since fdisk only know to work with MBR. The next command will open a parted shell, you'll need to replace /dev/sda with the drive that you want to partition.<br />
parted /dev/sda<br />
<br />
The next commands should be typed int the parted shell.<br />
<br />
WARNING: By running this commands you will delete you partition schema and won't be able to access the information that was stored on the disk (if any).<br />
(parted) mklabel gpt <-- This one creates a empty partition table on the disk<br />
<br />
(parted) print <-- List some information about the current partition table, size of the disc<br />
<br />
(parted) mkpart primary 0 3000GB <--- Creates a partition starting from the beginning trough the 3000GB location<br />
(parted) mkpart primary 3000GB 5000GB <--- Creates another partition starting from the 3000GB locations to the 5000GB location<br />
<br />
(parted) quit <-- Exit the parted shell<br />
<br />
After doing the previous command, you should have created two partitions, a 3TB and a 2TB one. In order for udev to create /dev/sda1 and /dev/sda2 devices associated with the partitions, you need to run the next command or reboot your computer:<br />
partprobe /dev/sda<br />
<br />
== Formating the Partitions ==<br />
<br />
Except of partition creation you won't see any difference between GPT and MBR in linux. So for formatting you can do it the same way as you would format any other discs. For example:<br />
<br />
mkfs.ext3 /dev/sda1</div>Razvanghttp://wiki.linuxmce.org/index.php?title=GPT&diff=9289GPT2008-02-29T15:43:31Z<p>Razvang: New page: If you want to create partitions larger than 2TB you'll have to use GTP partitioning system instead of classical MBR. Note that you BIOS knows only MBR partitioning schema and will not lik...</p>
<hr />
<div>If you want to create partitions larger than 2TB you'll have to use GTP partitioning system instead of classical MBR. Note that you BIOS knows only MBR partitioning schema and will not likely boot from a GTP partition.<br />
<br />
== Creating Partitions ==<br />
You'll need to use parted to create the partitions since fdisk only know to work with MBR. The next command will open a parted shell, you'll need to replace /dev/sda with the drive that you want to partition.<br />
parted /dev/sda<br />
<br />
The next commands should be typed int the parted shell.<br />
<br />
WARNING: By running this commands you will delete you partition schema and won't be able to access the information that was stored on the disk (if any).<br />
(parted) mklabel gpt <-- This one creates a empty partition table on the disk<br />
<br />
(parted) print <-- List some information about the current partition table, size of the disc<br />
<br />
(parted) mkpart primary 0 3000GB <--- Creates a partition starting from the beginning trough the 3000GB location<br />
(parted) mkpart primary 3000GB 5000GB <--- Creates another partition starting from the 3000GB locations to the 5000GB location<br />
<br />
(parted) quit <-- Exit the parted shell<br />
<br />
After doing the previous command, you should have created two partitions, a 3TB and a 2TB one. In order for udev to create /dev/sda1 and /dev/sda2 devices associated with the partitions, you need to run the next command or reboot your computer:<br />
partprobe /dev/sda<br />
<br />
== Formating the partitions ==<br />
<br />
Except of partition creation you won't see any difference between GPT and MBR in linux. So for formatting you can do it the same way as you would format any other discs. For example:<br />
<br />
mkfs.ext3 /dev/sda1</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Torrents_0710_beta_3&diff=8460Torrents 0710 beta 32008-01-16T16:32:13Z<p>Razvang: </p>
<hr />
<div>http://thepiratebay.org/tor/3980064 - LinuxMCE Install CDs for AMD64 - 0710 Beta 3<br />
<br />
http://thepiratebay.org/tor/3980066 - LinuxMCE Install CDs for I386 - 0710 Beta 3<br />
<br />
http://thepiratebay.org/tor/3980070 - LinuxMCE Install DVD for AMD64 - 0710 Beta 3<br />
<br />
http://thepiratebay.org/tor/3980072 - LinuxMCE Install DVD for I386 - 0710 Beta 3<br />
<br />
http://thepiratebay.org/tor/3980074 - LinuxMCE Install/Upgrade DVD for I386 - 0710 Beta 3</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Version_0710_beta3&diff=8428Version 0710 beta32008-01-16T13:33:11Z<p>Razvang: /* January 16, 2008 Version 0710 beta 3 is released */</p>
<hr />
<div>==January 16, 2008 Version 0710 beta 3 is released==<br />
<br />
Before installing, check out the [[KnownIssues_0710|Known issues 0710 beta 3]]. <br />
<br />
LinuxMCE is integrated into the KDE desktop and runs on Kubuntu Gutsy 7.10. Major changes:<br />
<br />
* Added support for amd64 <br />
<br />
* Added support for mixed amd64/i386 md’s <br />
<br />
* Added support for 1080p resolution. It work great with the masking UI, but it’s slow with alpha blended UI. <br />
<br />
* Upgraded xine to latest version <br />
<br />
* Latest mythtv packages and fixes for lmce mythtv stuff <br />
<br />
* Integrated VDR to LMCE and added support for few dvb-s cards <br />
<br />
* Telecom refactoring, most of the issues fixed (you can now easily create a conference, leave a conference, merge two conferences, use an assisted transfer, etc). Upgraded to asterisk 1.4.10 <br />
<br />
* Added latest nVidia drivers (169.07 Dec 20th) <br />
<br />
<br />
More here [[ChangeLog_0710|Changelog 0710]]<br />
<br />
<br />
To download, use the following torrents: <br />
[[Torrents_0710_beta_3|Torrents 0710 beta 3]]<br />
<br />
How to install : <br />
<br />
1. If you have a Kubuntu 0710 installed and you want to keep your applications settings, use CD's installation. Same steps as for 0740 (go [[Installation_Guide|here]]).<br />
<br />
2. If you want to do a quick install, use the DVD's. It will install both Kubuntul 0710 and LinuxMCE 0710. More [[DVD_Installation|here]].<br />
<br />
3. If you have LMCE 0704, you might want to try one of the following upgrade methods ( more [[Upgrade_to_0710|here]] ):<br />
<br />
- Installation using the DVD, with keep settings option (also works if you want to switch to amd64 version).<br />
<br />
- Download the upgrade helper application from [ftp://upgrade.linuxmce.com/Upgrade/gutsy-upgrade-scripts_0.1.0-1_i386.deb gutsy-upgrade-scripts_0.1.0-1_i386.deb] and choose to install from web or from DVD, if you have the double layer dvd.<br />
<br />
<br />
See also:<br />
<br />
[[FOSS_0710|FOSS 0710]] for the FOSS and development community explains what happened with the open source development after 1.1, and the current plans to develop a FOSS community<br />
<br />
[http://linuxmce.com/feedback.php Feedback] please report the results of your installation and be sure to describe any problems you have, and if possible, include contact information.<br />
<br />
[[Category:Versions]]</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Version_0710_beta3&diff=8403Version 0710 beta32008-01-15T14:16:24Z<p>Razvang: /* January 16, 2008 Version 0710 beta is released */</p>
<hr />
<div>==January 16, 2008 Version 0710 beta is released==<br />
<br />
Before installing, check out the [[KnownIssues_0710|Known issues 0710 beta]]. <br />
<br />
LinuxMCE is integrated into the KDE desktop and runs on Kubuntu Gutsy 7.10. Major changes:<br />
<br />
* Added support for amd64 <br />
<br />
* Added support for mixed amd64/i386 md’s <br />
<br />
* Added support for 1080p resolution. It work great with the masking UI, but it’s slow with alpha blended UI. <br />
<br />
* Upgraded xine to latest version <br />
<br />
* Latest mythtv packages and fixes for lmce mythtv stuff <br />
<br />
* Integrated VDR to LMCE and added support for few dvb-s cards <br />
<br />
* Telecom refactoring, most of the issues fixed (you can now easily create a conference, leave a conference, merge two conferences, use an assisted transfer, etc). Upgraded to asterisk 1.4.10 <br />
<br />
* Added latest nVidia drivers (169.07 Dec 20th) <br />
<br />
<br />
More here [[ChangeLog_0710|Changelog 0710]]<br />
<br />
<br />
To download, use the following torrents: [[Torrents_0710_beta|Torrents 0710 beta]]<br />
<br />
<br />
How to install : <br />
<br />
1. If you have a Kubuntu 0710 installed and you want to keep your applications settings, use CD's installation.<br />
<br />
2. If you want to do a quick install, use the DVD's. It will install both Kubuntul 0710 and LinuxMCE 0710<br />
<br />
3. If you have LMCE 0704, you might want to try one of the following upgrade methods:<br />
<br />
- Installation using the DVD, with keep settings option (also works if you want to switch to amd64 version).<br />
<br />
- Download the upgrade helper application from [ftp://upgrade.linuxmce.com/Upgrades/gutsy-upgrade-scripts_0.1.0-1_i386.deb gutsy-upgrade-scripts_0.1.0-1_i386.deb] and choose to install from web or from DVD, if you have the double layer dvd.<br />
<br />
<br />
See also:<br />
<br />
[[Download_Instructions_0710|Download instructions]]<br />
<br />
[[Installation_Guide]]<br />
<br />
[[FOSS_0710|FOSS 0710]] for the FOSS and development community explains what happened with the open source development after 1.1, and the current plans to develop a FOSS community<br />
<br />
[http://linuxmce.com/feedback.php Feedback] please report the results of your installation and be sure to describe any problems you have, and if possible, include contact information.<br />
<br />
[[Category:Versions]]</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Update_System&diff=4192Update System2007-07-18T09:39:37Z<p>Razvang: /* How to Test */</p>
<hr />
<div>==Short Description of the Update System==<br />
<br />
*The update system is looking every 24 hours (via a cron job) on http://updates.linuxmce.com for a file named updates.xml<br />
*If it finds that the updates.xml file was updated it downloads it and displays a message in all orbiters to inform the user that new updates are available<br />
*If the user choses to use/apply the updates, all the available updates will be applied at computer's next boot<br />
<br />
<br />
==Background Information on Updates==<br />
<br />
The updates.xml file contains descriptions of all the updates available since that version of the product was released till present.<br />
<br />
An updates contains at least one of the below:<br />
*a link to a '.deb' file which is can be installed on the system (using dpkg -i)<br />
*a link to a 'archive' file which can be unpacked on a system in a directory described in the update<br />
<br />
An update can also contain :<br />
*An option to reboot the computer before or after the update is applied [BUGGY ?]<br />
*An option to reload the router before or after the update is applied [NOT IMPLEMENTED]<br />
*An option to run an executable file after a file (deb / archive) is applied (installed / unpacked)<br />
<br />
An update must be addressed to at lease one of the fallowing 'products':<br />
*LMCE_CORE_1_1 - LinuxMCE 1.1 Kubuntu core or hybrid<br />
*LMCE_MD_1_1 - LinuxMCE 1.1 Kubuntu diskless or disked md<br />
*FIIRE_STATION_1_1 - LinuxMCE 1.1 Debian via disked md<br />
<br />
Every update has his own number associated with it (Unique ID)<br />
<br />
<br />
==Things To Care When Applying Updates==<br />
Since updating the MD's before the Core is updated might cause problems: some updates that can be applied to MD's may be delayed (based on the information from xml) by the update system until the Core itself was updated to a certain version.<br />
<br />
The user can not select what updates to use, he can only chose not to update at that time. For example if the user says no to update 'A' and after some time some a new update 'B' is available, he can update to 'B' but this means updating to 'A' then updating to 'B'.<br />
<br />
When updates are available and he is asked about them, the user has three options:<br />
*'Yes' - Start applying the updates at the next reboot<br />
*'No' - Don't apply updates (will be asked again only when new updates will be available)<br />
*'Later' - Will be asked again in 24 hours but the updates will not be applied when rebooting the computer<br />
<br />
If the used exits the screen without selecting any of the options displayed (by pressing the top-right X, orbiter closes because of a router reload , etc) the updates will be applied or not at reboot depending on the choose that he made last time he saw that screen. If is the first time the screen was shown, it will be considered as he pressed 'Later'. The screen will be displayed again in 24 hours regardless the implied answer.<br />
<br />
<br />
==How to Test==<br />
Right not 'update.linuxmce.com' points to 10.0.0.83. In /var/www/Updates on 83 you have 4 xml files. This files contain the description of up to 4 different updates:<br />
*updates-1.xml: Update 1<br />
*updates-2.xml: Update 1 and 2<br />
*updates-3.xml: Update 1 and 2 and 3<br />
*updates-4.xml: Update 1 and 2 and 3 and 4<br />
<br />
By copying them in /var/www with the name 'updates.xml' (on 83) you'll make the update system think that some updates are available.<br />
<br />
Since waiting up to 24 hours for the update mechanist to acknowledge the changes of the update system is impossible when testing, you can force that by running '/usr/pluto/bin/LMCEUpdate_DownloadXml.sh'<br />
<br />
Here is a description of every update:<br />
<br />
UPDATE 1:<br />
What computers can update: LMCE_CORE_1_1<br />
When they can update: No restrictions for this update<br />
What it does: Unpacks vim sources in /var/vim71 then reboots.<br />
How to see if it worked: A directory "/var/vim71" should be created on computer of type LMCE_CORE_1_1<br />
<br />
UPDATE 2:<br />
What computers can update: LMCE_MD_1_1, FIIRE_STATION_1_1<br />
When they can update: Both can update only after LMCE_CORE_1_1 had already got UPDATE 1<br />
What it does: Unpacks vino sources in /var/vino<br />
How to see if it worked: A directory "/var/vino" should be created<br />
<br />
UPDATE 3:<br />
What computers can update: LMCE_CORE_1_1, LMCE_MD_1_1<br />
When they can update: LMCE_MD_1_1 can update only after LMCE_CORE_1_1 had already got UPDATE 3<br />
What it does: It installs a package named 'x11vnc' then reboots<br />
How to see if it worked: dpkg -l x11vnc | grep "^ii"<br />
<br />
UPDATE 4:<br />
What computer cat update: FIIRE_STATION_1_1<br />
When they can update: Only after LMCE_CORE_1_1 had got UPDATE 3<br />
What it does: It installs a applications called 'mytop'<br />
Ho to see if it worked: dpkg -l mytop | grep "^ii"</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Update_System&diff=4191Update System2007-07-17T15:39:32Z<p>Razvang: </p>
<hr />
<div>==Short Description of the Update System==<br />
<br />
*The update system is looking every 24 hours (via a cron job) on http://updates.linuxmce.com for a file named updates.xml<br />
*If it finds that the updates.xml file was updated it downloads it and displays a message in all orbiters to inform the user that new updates are available<br />
*If the user choses to use/apply the updates, all the available updates will be applied at computer's next boot<br />
<br />
<br />
==Background Information on Updates==<br />
<br />
The updates.xml file contains descriptions of all the updates available since that version of the product was released till present.<br />
<br />
An updates contains at least one of the below:<br />
*a link to a '.deb' file which is can be installed on the system (using dpkg -i)<br />
*a link to a 'archive' file which can be unpacked on a system in a directory described in the update<br />
<br />
An update can also contain :<br />
*An option to reboot the computer before or after the update is applied [BUGGY ?]<br />
*An option to reload the router before or after the update is applied [NOT IMPLEMENTED]<br />
*An option to run an executable file after a file (deb / archive) is applied (installed / unpacked)<br />
<br />
An update must be addressed to at lease one of the fallowing 'products':<br />
*LMCE_CORE_1_1 - LinuxMCE 1.1 Kubuntu core or hybrid<br />
*LMCE_MD_1_1 - LinuxMCE 1.1 Kubuntu diskless or disked md<br />
*FIIRE_STATION_1_1 - LinuxMCE 1.1 Debian via disked md<br />
<br />
Every update has his own number associated with it (Unique ID)<br />
<br />
<br />
==Things To Care When Applying Updates==<br />
Since updating the MD's before the Core is updated might cause problems: some updates that can be applied to MD's may be delayed (based on the information from xml) by the update system until the Core itself was updated to a certain version.<br />
<br />
The user can not select what updates to use, he can only chose not to update at that time. For example if the user says no to update 'A' and after some time some a new update 'B' is available, he can update to 'B' but this means updating to 'A' then updating to 'B'.<br />
<br />
When updates are available and he is asked about them, the user has three options:<br />
*'Yes' - Start applying the updates at the next reboot<br />
*'No' - Don't apply updates (will be asked again only when new updates will be available)<br />
*'Later' - Will be asked again in 24 hours but the updates will not be applied when rebooting the computer<br />
<br />
If the used exits the screen without selecting any of the options displayed (by pressing the top-right X, orbiter closes because of a router reload , etc) the updates will be applied or not at reboot depending on the choose that he made last time he saw that screen. If is the first time the screen was shown, it will be considered as he pressed 'Later'. The screen will be displayed again in 24 hours regardless the implied answer.<br />
<br />
<br />
==How to Test==<br />
TODO 1: talk to admins to make updates.linuxmce.com point to 10.0.0.83 so you can test<br />
<br />
TODO 2: get a system with via going so admins can write down update #4<br />
<br />
In /var/www/Updates you have 4 xml files. This files contain the description of up to 4 different updates:<br />
*updates-1.xml: Update 1<br />
*updates-2.xml: Update 1 and 2<br />
*updates-3.xml: Update 1 and 2 and 3<br />
*updates-4.xml: Update 1 and 2 and 3 and 4<br />
<br />
By copying them in /var/www with the name 'updates.xml' (on 83) you'll make the update system think that some updates are available. Since waiting up to 24 hours for the update mechanist to acknowledge the changes of the update system is impossible when testing, you can force that by running '/usr/pluto/bin/LMCEUpdate_DownloadXml.sh'<br />
<br />
Here is a description of every update:<br />
<br />
UPDATE 1:<br />
What computers can update: LMCE_CORE_1_1<br />
What it does: Unpacks vim sources in /var/vim71 then reboots.<br />
How to see if it worked: A directory "/var/vim71" should be created<br />
<br />
UPDATE 2:<br />
What computers can update: LMCE_MD_1_1, FIIRE_STATION_1_1<br />
When they can update: Both can update only after LMCE_CORE_1_1 had already got UPDATE 1<br />
What it does: Unpacks vino sources in /var/vino<br />
How to see if it worked: A directory "/var/vino" should be created<br />
<br />
UPDATE 3:<br />
What computers can update: LMCE_CORE_1_1,LMCE_MD_1_1<br />
When they can update: LMCE_MD_1_1 can update only after LMCE_CORE_1_1 had already got UPDATE 3<br />
What it does: It installs a package named 'x11vnc' then reboots<br />
How to see if it worked: dpkg -l x11vnc | grep "^ii"<br />
<br />
UPDATE 4: (see TODO2)<br />
What computer cat update: FIIRE_STATION_1_1<br />
.........................</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Update_System&diff=4190Update System2007-07-17T15:35:38Z<p>Razvang: </p>
<hr />
<div>Short Description of the Update System:<br />
-----------------------------------------------------------<br />
- The update system is looking every 24 hours (via a cron job) on http://updates.linuxmce.com for a file named updates.xml<br />
- If it finds that the updates.xml file was updated it downloads it and displays a message in all orbiters to inform the user that new updates are available<br />
- If the user choses to use/apply the updates, all the available updates will be applied at computer's next boot<br />
<br />
<br />
Background information on Updates :<br />
-----------------------------------------------------<br />
The updates.xml file contains descriptions of all the updates available since that version of the product was released till present.<br />
<br />
An updates contains at least one of the below:<br />
- a link to a '.deb' file which is can be installed on the system (using dpkg -i)<br />
- a link to a 'archive' file which can be unpacked on a system in a directory described in the update<br />
<br />
An update can also contain :<br />
- An option to reboot the computer before or after the update is applied [BUGGY ?]<br />
- An option to reload the router before or after the update is applied [NOT IMPLEMENTED]<br />
- An option to run an executable file after a file (deb / archive) is applied (installed / unpacked)<br />
<br />
An update must be addressed to at lease one of the fallowing 'products':<br />
- LMCE_CORE_1_1 - LinuxMCE 1.1 Kubuntu core or hybrid<br />
- LMCE_MD_1_1 - LinuxMCE 1.1 Kubuntu diskless or disked md<br />
- FIIRE_STATION_1_1 - LinuxMCE 1.1 Debian via disked md<br />
<br />
Every update has his own number associated with it (Unique ID)<br />
<br />
<br />
Things to care when applying Updates :<br />
---------------------------------------------------------<br />
Since updating the MD's before the Core is updated might cause problems: some updates that can be applied to MD's may be delayed (based on the information from xml) by the update system until the Core itself was updated to a certain version.<br />
<br />
The user can not select what updates to use, he can only chose not to update at that time. For example if the user says no to update 'A' and after some time some a new update 'B' is available, he can update to 'B' but this means updating to 'A' then updating to 'B'.<br />
<br />
When updates are available and he is asked about them, the user has three options:<br />
'Yes' - Start applying the updates at the next reboot<br />
'No' - Don't apply updates (will be asked again only when new updates will be available)<br />
'Later' - Will be asked again in 24 hours but the updates will not be applied when rebooting the computer<br />
<br />
If the used exits the screen without selecting any of the options displayed (by pressing the top-right X, orbiter closes because of a router reload , etc) the updates will be applied or not at reboot depending on the choose that he made last time he saw that screen. If is the first time the screen was shown, it will be considered as he pressed 'Later'. The screen will be displayed again in 24 hours regardless the implied answer.<br />
<br />
<br />
How to Test :<br />
-------------------<br />
TODO 1: talk to admins to make updates.linuxmce.com point to 10.0.0.83 so you can test<br />
TODO 2: get a system with via going so admins can write down update #4<br />
<br />
In /var/www/Updates you have 4 xml files. This files contain the description of up to 4 different updates:<br />
updates-1.xml: Update 1<br />
updates-2.xml: Update 1 and 2<br />
updates-3.xml: Update 1 and 2 and 3<br />
updates-4.xml: Update 1 and 2 and 3 and 4<br />
<br />
By copying them in /var/www with the name 'updates.xml' (on 83) you'll make the update system think that some updates are available. Since waiting up to 24 hours for the update mechanist to acknowledge the changes of the update system is impossible when testing, you can force that by running '/usr/pluto/bin/LMCEUpdate_DownloadXml.sh'<br />
<br />
Here is a description of every update:<br />
UPDATE 1:<br />
What computers can update: LMCE_CORE_1_1<br />
What it does: Unpacks vim sources in /var/vim71 then reboots.<br />
How to see if it worked: A directory "/var/vim71" should be created<br />
<br />
UPDATE 2:<br />
What computers can update: LMCE_MD_1_1, FIIRE_STATION_1_1<br />
When they can update: Both can update only after LMCE_CORE_1_1 had already got UPDATE 1<br />
What it does: Unpacks vino sources in /var/vino<br />
How to see if it worked: A directory "/var/vino" should be created<br />
<br />
UPDATE 3:<br />
What computers can update: LMCE_CORE_1_1,LMCE_MD_1_1<br />
When they can update: LMCE_MD_1_1 can update only after LMCE_CORE_1_1 had already got UPDATE 3<br />
What it does: It installs a package named 'x11vnc' then reboots<br />
How to see if it worked: dpkg -l x11vnc | grep "^ii"<br />
<br />
UPDATE 4: (see TODO2)<br />
What computer cat update: FIIRE_STATION_1_1<br />
.........................</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Download_Instructions&diff=3776Download Instructions2007-03-29T21:31:13Z<p>Razvang: /* Getting the source code */</p>
<hr />
<div>== Important ==<br />
<br />
Read the [[Known_Issues|Known Issues]] page first. There are some warnings to Ubuntu users who have already modified their Ubuntu installation or customized their .conf files that LinuxMCE will override their changes.<br />
<br />
== Getting help ==<br />
<br />
In addition to the usual community options like forums, for the moment a few volunteers have agreed to provide [[Tech_Support|live tech support via Yahoo/Skype]] to identify common installation problems so they can be fixed in the next release.<br />
<br />
== Reading before installing LinuxMCE ==<br />
<br />
Before installing LinuxMCE, I suggest reading [[What_To_Expect|What to expect]] which says exactly what sequences and equipment was used to setup my whole home media + automation system as shown in the demo video, and warns what are the pitfalls you may run into.<br />
<br />
Also read:<br />
<br />
The [[Installation_Guide|Detailed step-by-step instructions for installing LinuxMCE]] which has step-by-step instructions on installing Ubuntu and LinuxMCE.<br />
Then the short [[Architecture_Intro|Architecture Intro]] which explains what pc's you'll need to install software on and how they all work together.<br />
Then there's a [[QuickStart_Guide|Quick Start Guide]] which explains how to set the video and audio settings using the AV Wizard, and to add devices to LinuxMCE with the Setup Wizard.<br />
The [[Usage_Intro|Usage Intro]] is a quick primer on how to use LinuxMCE once it's installed.<br />
<br />
LinuxMCE is a huge program with lots of features that you won't even notice right away, and the wiki already has a ton of pages which I imported from existing sources when I launched LinuxMCE, such as the original [[User's_Manual|User's Manual]] and [[Programmer's_Guide|Programmer's Guide]]. I found most of these docs weren't well organized and some of the data isn't up to date. But it's a wiki and all pages are open for editing, so hopefully this will improve.<br />
<br />
== Getting the CD's ==<br />
<br />
As explained in the [[Installation_Guide|Installation Guide]] You need 2 cd's to install LinuxMCE, which you can get here:<br />
<br />
1) Ubuntu 6.10 live cd. For now Linux MCE can only be installed on top of the Ubuntu 6.10 distribution of Linux, which is available [http://www.ubuntu.com/products/GetUbuntu/download?action=show&redirect=download here].<br />
<br />
2) The LinuxMCE install cd, which is available on these [[Mirrors]].<br />
<br />
== The LinuxMCE installer ==<br />
<br />
Once you have already burned the LinuxMCE install cd, and finished installing Ubuntu 6.10, here is the installer application you run from within Ubuntu to install LinuxMCE:<br />
<br />
[http://linuxmce.com/download.php http://linuxmce.com/images/download_button.gif]<br />
<br />
== Getting the source code ==<br />
Instructions on getting the source code and compiling it are located on [[Building From Source]] page.</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Building_From_Source&diff=3775Building From Source2007-03-29T21:28:48Z<p>Razvang: /* The Build Scripts */</p>
<hr />
<div>== Before You Begin==<br />
The build script is tested and designed to run on Ubuntu 6.10 x86 but it can be changed to work on various platforms or at least to give others a starting point on how to do it. It'll be harder to port it to non deb based distributions since the software depends on many debian specific stuff but this i hope to be change over time.<br />
<br />
Also since this script was written with a single goal in mind, to get everything done, i might left by mistake some lines of code that may not run on your computers (hardcoded paths and stuff like this) but i relay on you to at lease try to fix them before asking for help but if the problem is not so obvious i would gladly give you advices.<br />
<br />
== The Build Scripts ==<br />
The build scripts are in sourceforge svn so to get them you will need subversion installed.<br />
sudo apt-get install subversion<br />
svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers<br />
<br />
Before running the build script, i insist that you take a look over it so that you know what is doing and not run it blindly. <br />
<br />
The main script that you need to run would be BuildUbuntu.sh. This script should checkout the svn for you, compile the source, build the packages, build an iso and everything else so you can end up with a usable linuxmce build. In this script you can find some functions that are called one by one to perform several operations, here's a short description:<br />
<br />
*''Install_Build_Needed_Packages'': This will install all the deb packages that you will need to build the sourcecode. Probably you will only need to run it once and comment it after the first run on BuildPackages.sh.<br />
*''Create Diskless Archive'': Runs a debootstrap to create a base filesystem for Diskless Media Directors. It's needed later when it'll be packed in a deb packages. You also don't need to run this every time but is safer to leave it uncommented so that the diskless archive will have the latest ubuntu updates.<br />
*''Import_Skins'': Since linuxmce uses a lot of pngs for the all sort of skins, you won't find them in the svn. This function will download a tar.bz2 archive with all the skins and unpack it so that the package builder will now where to take it from.<br />
*''Checkout_Svn'': Will do a svn checkout on sourceforge to get all the needed sources<br />
*''Build_Replacements'': LinuxMCE needs some 3rd party some packages that are not part of ubuntu distribution. This function will build / get them for you.<br />
*''Build_MakeRelease_Binary'': This function compiles the building tools that will do the compilation / package creation of all the other packages by using information stored in the pluto_main_build database.<br />
*''Import_Build_Database'': Imports a fresh copy of the pluto databases needed at build time.<br />
*''Create_Fake_Windows_Binaries'': Orbiter and other aplications don't only run on Linux. Usually the pluto guys compile their applications on windows and put the binaries on the linux build machine so that package creating application will know where to get them. Since we can't compile windows binaries on linux i made this function that creates some fake binary files with a touch so that the package builder won't fail to run.<br />
*''Build_Pluto_Stuff'': Uses MakeRelase to compile the sources and build packages out of them<br />
*''Create_Local_Repository'': Optional you can create a local repository so that you can easily test your debs.<br />
<br />
There is also the get-packages.sh script that is called by BuildUbuntu.sh and has the goal to create and iso with all the needed packages for a linuxmce installation.<br />
<br />
== Source Code Location ==<br />
<br />
Our source code is located on sourceforge and you can get it by svn from : https://linuxmce.svn.sourceforge.net/nroot/linuxmce/<br />
<br />
The png used for the skins are located here : http://www.linuxmce.com/linuxmce-skins-1.0.tar.bz2<br />
<br />
The sql dumps of the databases needed for the build : http://www.linuxmce.com/linuxmce-databases-1.0.tar.gz</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Building_From_Source&diff=3774Building From Source2007-03-29T21:19:01Z<p>Razvang: /* The Build Scripts */</p>
<hr />
<div>== Before You Begin==<br />
The build script is tested and designed to run on Ubuntu 6.10 x86 but it can be changed to work on various platforms or at least to give others a starting point on how to do it. It'll be harder to port it to non deb based distributions since the software depends on many debian specific stuff but this i hope to be change over time.<br />
<br />
Also since this script was written with a single goal in mind, to get everything done, i might left by mistake some lines of code that may not run on your computers (hardcoded paths and stuff like this) but i relay on you to at lease try to fix them before asking for help but if the problem is not so obvious i would gladly give you advices.<br />
<br />
== The Build Scripts ==<br />
The build scripts are in sourceforge svn so to get them you will need subversion installed.<br />
sudo apt-get install subversion<br />
svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers<br />
<br />
Before running the build script, i insist that you take a look over it so that you know what is doing and not run it blindly. <br />
<br />
The main script that you need to run would be BuildUbuntu.sh. This script should checkout the svn for you, compile the source, build the packages, build an iso and everything else so you can end up with a usable linuxmce build. In this script you can find some functions that are called one by one to perform several operations, here's a short description:<br />
<br />
*''Install_Build_Needed_Packages'': This will install all the deb packages that you will need to build the sourcecode. Probably you will only need to run it once and comment it after the first run on BuildPackages.sh.<br />
*''Create Diskless Archive'': Runs a debootstrap to create a base filesystem for Diskless Media Directors. It's needed later when it'll be packed in a deb packages. You also don't need to run this every time but is safer to leave it uncommented so that the diskless archive will have the latest ubuntu updates.<br />
*''Import_Skins'': Since linuxmce uses a lot of pngs for the all sort of skins, you won't find them in the svn. This function will download a tar.bz2 archive with all the skins and unpack it so that the package builder will now where to take it from.<br />
*''Checkout_Svn'': Will do a svn checkout on sourceforge to get all the needed sources<br />
*''Build_Replacements'': LinuxMCE needs some 3rd party some packages that are not part of ubuntu distribution. This function will build / get them for you.<br />
*''Build_MakeRelease_Binary'': This function compiles the building tools that will do the compilation / package creation of all the other packages by using information stored in the pluto_main_build database.<br />
*''Import_Build_Database'': Imports a fresh copy of the pluto databases needed at build time.<br />
*''Create_Fake_Windows_Binaries'': Orbiter and other aplications don't only run on Linux. Usually the pluto guys compile their applications on windows and put the binaries on the linux build machine so that package creating application will know where to get them. Since we can't compile windows binaries on linux i made this function that creates some fake binary files with a touch so that the package builder won't fail to run.<br />
*''Build_Pluto_Stuff'': Uses MakeRelase to compile the sources and build packages out of them<br />
*''Create_Local_Repository'': Optional you can create a local repository so that you can easily test your debs.<br />
<br />
There is also the get-packages.sh script that is called by BuildUbuntu.sh and has the goal to create and iso with all the needed packages for a linuxmce installation.</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Building_From_Source&diff=3773Building From Source2007-03-29T21:17:23Z<p>Razvang: /* The Build Scripts */</p>
<hr />
<div>== Before You Begin==<br />
The build script is tested and designed to run on Ubuntu 6.10 x86 but it can be changed to work on various platforms or at least to give others a starting point on how to do it. It'll be harder to port it to non deb based distributions since the software depends on many debian specific stuff but this i hope to be change over time.<br />
<br />
Also since this script was written with a single goal in mind, to get everything done, i might left by mistake some lines of code that may not run on your computers (hardcoded paths and stuff like this) but i relay on you to at lease try to fix them before asking for help but if the problem is not so obvious i would gladly give you advices.<br />
<br />
== The Build Scripts ==<br />
The build scripts are in sourceforge svn so to get them you will need subversion installed.<br />
sudo apt-get install subversion<br />
svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers<br />
<br />
Before running the build script, i insist that you take a look over it so that you know what is doing and not run it blindly. <br />
<br />
The main script that you need to run would be BuildUbuntu.sh. This script should checkout the svn for you, compile the source, build the packages, build an iso and everything else so you can end up with a usable linuxmce build. In this script you can find some functions that are called one by one to perform several operations, here's a short description:<br />
<br />
*''Install_Build_Needed_Packages'': This will install all the deb packages that you will need to build the sourcecode. Probably you will only need to run it once and comment it after the first run on BuildPackages.sh.<br />
*''Create Diskless Archive'': Runs a debootstrap to create a base filesystem for Diskless Media Directors. It's needed later when it'll be packed in a deb packages. You also don't need to run this every time but is safer to leave it uncommented so that the diskless archive will have the latest ubuntu updates.<br />
*''Import_Skins'': Since linuxmce uses a lot of pngs for the all sort of skins, you won't find them in the svn. This function will download a tar.bz2 archive with all the skins and unpack it so that the package builder will now where to take it from.<br />
*''Checkout_Svn'': Will do a svn checkout on sourceforge to get all the needed sources<br />
*''Build_Replacements'': LinuxMCE needs some 3rd party some packages that are not part of ubuntu distribution. This function will build / get them for you.<br />
*''Build_MakeRelease_Binary'': This function compiles the building tools that will do the compilation / package creation of all the other packages by using information stored in the pluto_main_build database.<br />
*''Import_Build_Database'': Imports a fresh copy of the pluto databases needed at build time.<br />
*''Create_Fake_Windows_Binaries'': Orbiter and other aplications don't only run on Linux. Usually the pluto guys compile their applications on windows and put the binaries on the linux build machine so that package creating application will know where to get them. Since we can't compile windows binaries on linux i made this function that creates some fake binary files with a touch so that the package builder won't fail to run.<br />
*''Build_Pluto_Stuff'': Uses MakeRelase to compile the sources and build packages out of them<br />
*''Create_Local_Repository'': Optional you can create a local repository so that you can easily test your debs.</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Building_From_Source&diff=3772Building From Source2007-03-29T20:34:40Z<p>Razvang: </p>
<hr />
<div>== Before You Begin==<br />
The build script is tested and designed to run on Ubuntu 6.10 x86 but it can be changed to work on various platforms or at least to give others a starting point on how to do it. It'll be harder to port it to non deb based distributions since the software depends on many debian specific stuff but this i hope to be change over time.<br />
<br />
Also since this script was written with a single goal in mind, to get everything done, i might left by mistake some lines of code that may not run on your computers (hardcoded paths and stuff like this) but i relay on you to at lease try to fix them before asking for help but if the problem is not so obvious i would gladly give you advices.<br />
<br />
== The Build Scripts ==<br />
The build scripts are in sourceforge svn so to get them you will need subversion installed.<br />
<br />
<br />
sudo apt-get install subversion<br />
svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers<br />
<br />
Before running the build script, i insist that you take a look over it so that you know what is doing and not run it blindly. <br />
<br />
The main script that you need to run would be BuildUbuntu.sh. This script should checkout the svn for you, compile the source, build the packages, build an iso and everything else so you can end up with a usable linuxmce build. In this script you can find some functions that are called one by one to perform several operations, here's a short description:<br />
<br />
*''Install_Build_Needed_Packages'': This will install all the deb packages that you will need to build the sourcecode. Probably you will only need to run it once and comment it after the first run on BuildPackages.sh.<br />
*''Create Diskless Archive'': Runs a debootstrap to create a base filesystem for Diskless Media Directors. It's needed later when it'll be packed in a deb packages. You also don't need to run this every time but is safer to leave it uncommented so that the diskless archive will have the latest ubuntu updates.<br />
*''</div>Razvanghttp://wiki.linuxmce.org/index.php?title=QuickStart_Guide&diff=3050QuickStart Guide2007-03-14T01:11:53Z<p>Razvang: </p>
<hr />
<div>If you haven't already installed LinuxMCE, start with the [[Installation_Guide|Detailed step-by-step instructions for installing LinuxMCE]].<br />
<br />
'''IMPORTANT:''' If you intend to watch commercial DVD's in Linux MCE, pay attention to step 1 in those installation instructions.<br />
<br />
This Quick Start Guide assumes you already completed the installation. If, during the installation of LinuxMCE you did not specify that LinuxMCE should be started by default, you can start it now from the Ubuntu system menu > Application > Sound & Video > Start 'Linux MCE Center'<br />
<br />
The first time you do a start-up it will take somewhere between 5 and 10 minutes so it can verify everything in your installation; after that it takes about 30-60 seconds. In this time some software/services will started (like: mysql server, etc.), you just have to wait, no other interaction is needed. The first time you start LinuxMCE it will run the AVWizard automatically. This is where you pick the video and audio settings LinuxMCE will use. Note this has no effect on Ubuntu's desktop.<br />
<br />
The AVWizard will guide you though audio/video settings for your hardware. You will be presented with 3 choices for the user interface. UI1, UI2 with masking, and UI2 with alpha blending. UI2 with alpha blending is generally considered the best, but it requires your video card support X's composite extensions. At this time, only nVidia 6xxx or greater can do this. This is the recommended platform for LinuxMCE. UI2 with masking has the same 3D OpenGL effects, but is less demanding on the hardware, and will run on most video cards that have decent OpenGL and XDamage support. UI1 is the simplest because it has no 3d effects, and never puts any graphics on top of the video. UI1 should run on nearly all Linux-compatible video cards. See [[Screenshots]] to see the difference between the 3 UI options.<br />
<br />
'''IMPORTANT:''' Regarding Step 4 in the AV Wizard, if your TV doesn't overscan, meaning crop off the edges, you will see all 4 yellow arrows completely on step 4. If your TV does overscan, be sure to hit the - key to reduce the image until all 4 arrows are fully visible. Use the arrow keys to shift the image. The goal is that all 4 arrows are centered and as close to the edges of your screen as possible, but without being cropped off. This is where LinuxMCE will display the user interface. Your movies and media themselves are always full-screen and are not effected by this.<br />
<br />
These are the steps in AV Wizard:<br />
<table><br />
<tr><br />
<td>[[Image:AVWizardStep1.jpg|200px]]</td><br />
<td>[[Image:AVWizardStep11.jpg|200px]]</td><br />
<td>[[Image:AVWizardStep2.jpg|200px]]</td><br />
<td>[[Image:AVWizardStep21.jpg|200px]]</td><br />
</tr><br />
<tr><br />
<td>[[Image:AVWizardStep3.jpg|200px]]</td><br />
<td>[[Image:AVWizardStep4.jpg|200px]]</td><br />
<td>[[Image:AVWizardStep5.jpg|200px]]</td><br />
<td>[[Image:AVWizardStep6.jpg|200px]]</td><br />
</tr><br />
<tr><br />
<td>[[Image:AVWizardStep7.jpg|200px]]</td><br />
<td>[[Image:AVWizardStep8.jpg|200px]]</td><br />
<td>[[Image:AVWizardStep9.jpg|200px]]</td><br />
</tr><br />
</table><br />
<br />
The final step asks for a confirmation of these steps, if you press 'I Agree' the installation continues and you'll get the Media Center started.<br />
<br />
'''IMPORTANT:''' At this time you don't have any rooms or users (ie family members) added to LinuxMCE. Because LinuxMCE is a whole house solution and manages all your family member's content, before you can use LinuxMCE you must, at a minimum, provide a list of the Rooms and Users in your home, and specify which Room this system is in. If you want to dive right in, you can skip the other setup steps for now, but you cannot use LinuxMCE at all until you specify the Rooms and Users.<br />
<br />
To do this, you can login to the web admin panel from your LinuxMCE system, or any other PC in the house, as explained on the LinuxMCE startup screen. A walk-through of the web admin is available, but if you want to just get going asap, choose Wizard > Basic Info > Rooms and also Wizard > Basic Info > Users to specify the Rooms and Users, and Wizard > Devices > Media Directors to specify which room this system is in.<br />
<br />
If you prefer not to use the web admin site, there is also an interactive setup wizard built-into the GUI. It doesn't let you do a lot of customizing, but, it's a very fast and easy way to get up and running in about 5 minutes using all the default options for all the features of LinuxMCE. To start the setup wizard, choose Misc > Advanced Options from the GUI and then 'Setup wizard'.<br />
<br />
Note that in the future there will be video files in the setup wizard. For now the video files are not complete, so you won't see or hear the video clips. If some of the screens are a bit vague because of this, we recommend you stick to the web admin site for now.<br />
<br />
Here are some screen shots from the setup wizard:<br />
<br />
<table><br />
<tr><br />
<td>[[Image:VideoWizard.jpg|200px]]</td><br />
<td>[[Image:Which Wizard.jpg|250px]]</td><br />
<td>[[Image:UsersWizard.jpg|250px]]</td><br />
<td>[[Image:RoomsWizard.jpg|250px]]</td><br />
</tr><br />
<tr><br />
<td>[[Image:CountryWizard.jpg|200px]]</td><br />
<td>[[Image:This Room.jpg|200px]]</td><br />
<td>[[Image:TV Manufacturer.jpg|200px]]</td><br />
<td>[[Image:AV Devices.jpg|200px]]</td><br />
</tr><br />
</table><br />
<br />
After Video Wizard is ended and the house is entirely setup, press 'start using the system'. This action will also regenerate the interface with the new changes you've made.</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Installation_Guide&diff=3049Installation Guide2007-03-14T00:42:11Z<p>Razvang: </p>
<hr />
<div>Steps for installing Linux MCE on an Ubuntu 6.10 system (only Ubuntu 6.10 is support for now):<br />
<br />
'''1.''' Take an Ubuntu install already configured with Internet connection (Configure your network card and DNS). If you don't have an Ubuntu system already installed please follow these generic steps:<br />
<br />
*Take an [http://www.ubuntu.com/products/GetUbuntu/download?action=show&redirect=download Ubuntu Live Cd] and boot from it.<br />
*Choose 'Start or install Ubuntu'<br />
*When Ubuntu's desktop appears, double-click on 'Install'<br />
*A short wizard will start and guide you; Select the language and press 'forward'<br />
*Choose you timezone and press 'forward'<br />
*Select the keyboard layout<br />
*Choose desktop name, an user name and a password<br />
*Select the partitioning options for your disk: erase the entire disk or just manually edit the options.<br />
*Ready to install.<br />
*Reboot the system and remove the Live CD<br />
*(Optional) Ubuntu and Linux MCE won't install by default software needed to play DVD or some other restricted media formats that might be illegal in some countries. You can follow the [[Restricted Software Installation Guide]] if the restrictions don't apply to your country.<br />
*(Optional) Before installing LinuxMCE is recommended to apply all the Ubuntu updates that are available. If you don't do this, the Linux MCE installer will do this for you at the end of the installation.<br/><br />
<br />
<br />
<br />
'''2.''' Go to [http://www.linuxmce.com www.linuxmce.com] and select 'Download Instructions' and 'Installer for Ubuntu 6.10' to download the Linux MCE Installer on your machine. Or just use this direct link [http://www.linuxmce.com/download.php click here]<br />
<br />
[[Image:DownloadInstaller.jpg|400px]]<br />
<br />
<br />
'''3.''' Save the mce-installer on your Ubuntu desktop. A pop-up message will appear and there you must check "Save to Disk" and then click "ok"<br />
<br />
[[Image:SaveInstaller.jpg|400px]]<br />
<br />
<br />
'''4.''' Then double-click on your "Install Linux MCE" icon from Ubuntu`s desktop to start the installation process. A window will appear asking to choose if you want a dedicated core or a hybrid ([http://linuxmce.com/wiki/index.php/Getting_Started#A_Dedicated_Core click here]to find out the difference between a core and a hybrid), after that you must click on "Forward" button. <br />
<br />
[[Image:CoreOrHybrid.jpg|400px]]<br />
<br />
<br />
'''5.''' The next screen will ask you want to keep your current network configuration or if you want to set your network options manually; then press "Forward".<br />
<br />
[[Image:ConfirNetworkSettings.jpg|400px]]<br />
<br />
<br />
'''6.''' In the next step you must select the method you want to choose to install Linux MCE and you have 3 options: <br />
*Download the needed packages from the internet. Just downloads the packages from linuxmce.com website.<br />
*Download and use an ISO file from one of LinuxMCE mirrors. Instead of downloading the packages one by one just, it downloads an archive which contains all packages. <br />
*Use the Linux MCE CDROM that I already have in my drive. This assumes you have already [[Installation_Guide|downloaded LinuxMCE as an ISO image]] and burned it to a cd. This is the recommended method so that if you install Linux MCE again, the installer won't need to download everything again.<br />
<br />
After you have chosen your option press 'Forward'.<br />
<br />
[[Image:InstallOptions.jpg|400px]]<br />
<br />
<br />
'''7.''' In the next step you have 2 options :<br />
*First it asks you if you want to Run a DHCP Server or not. LinuxMCE must be the DHCP server for your home in order to provide plug-and-play detection of network devices like IP Cameras and VOIP phones, and to provide network boot images to any other pc's in the home you want to use as media stations.<br />
*The other option asks if you want to keep the default Internal Network address or if you want to change it.<br />
<br />
After that you must press 'Forward'.<br />
<br />
[[Image:DhcpSettings.jpg|400px]]<br />
<br />
<br />
'''8.''' In the next window you can see how the Linux MCE system is installing<br />
<br />
[[Image:StartInstall.jpg|400px]]<br />
<br />
<br />
'''9.''' In the final step you will see a message saying "Installation was finished , please reboot"<br />
<br />
[[Image:FinalStep.jpg|400px]]<br />
<br />
After reboot you have the Linux MCE software installed.<br />
<br />
Next follow the [http://linuxmce.com/wiki/index.php?title=QuickStart_Guide Quick Start Guide] to tell LinuxMCE about how you want to use it.</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Getting_Started&diff=3048Getting Started2007-03-14T00:40:31Z<p>Razvang: /* A Dedicated Hybrid */</p>
<hr />
<div><table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>==Equipment: Picking The Right Components==<br />
<br />
[http://plutohome.com/index.php?section=pluto_system_overview Equipment overview]<br />
<br />
===The Core===<br />
<br />
Most important, is the "core". This is the main Pluto server that runs all the applications. The commercial version uses a high-end server with RAID-5 storage. You'll probably get by with a good Pentium 4, least 80 GB of storage, two network cards (Gigabit ideally).<br />
<br />
It would be best to use a dedicated core, which means you'll end up putting this computer somewhere out of the way and not connecting a monitor to it. If you are using only one computer for your system, then you've chosen the "hybrid" system, which means that your core will also be your media player. You'll definitely need a monitor or TV for this system!<br />
<br />
===Media Directors===<br />
<br />
Note that each media director will need a Bluetooth dongle if you want to use a Bluetooth mobile phone as the remote in that area. To control your a/v equipment using infrared, you will need an interface module (global cache gc100). This interface module also gives you extra serial ports. So, in this example, the TV is controlled by infrared, and the receiver by RS232.<br />
<br />
[[Sound Cards]]<br />
<br />
[[Network_Boot_for_Media_Directors]]<br />
<br />
===Orbiters===<br />
<br />
===Network Attached Storage===<br />
<br />
An alternative to having a lot of memory in the core is to have a small hard drive for the core and store all your files on a [[Network Attached Storage|network attached storage]] (or NAS) server. The [http://www.buffalotech.com/products/product-detail.php?productid=97 Buffalo TeraStation] is 1.0 TeraByte RAID-5 and under $1K(US). Having a NAS will allow you to not lose your precious media files. You'll likely want the larger storage for your collection of music and videos. Keep in mind that your Pluto system can also record TV shows (using MythTV) and video from your security cameras (using Motion).<br />
<br />
===Additional Devices===<br />
<br />
[[Recommended_Accessories]]<br />
<br />
Optionally, you may want the aformentioned home automation devices for controlling your lights. Also, optionally, you may want security cameras, plasma screen TV, a streaming media music player such as the [http://www.slimdevices.com Squeezebox], an alarm system with a serial interface, etc. Some of these devices need ''another'' device called a [http://www.globalcache.com/products/gc-index.html gc100]. This allows devices that communicate using a serial port (good alarm panels) or infrared (like your TV) to connect to the network and talk with your Pluto core.<br />
<br />
===Location Considerations===<br />
<br />
This section has been moved to [[Choosing_Locations]].<br />
<br />
===Wiring Considerations===<br />
<br />
[[Wiring Considerations]]<br />
<br />
There are 2 basic configurations, which we officially test and support. Both require that the Core be [[Do I want a dedicated Core?|dedicated]], meaning that you use the [[Kick-Start CD]] and let Pluto "take over" the computer. If you're a Linux user, you can still use the dedicated Core as a Debian Linux PC. Otherwise, once Pluto is installed, just treat it like an appliance--plug it in, turn it on, and leave it alone. The great news is that don't need to install any software on the media PC's that will be used as media directors.<br />
You can leave whatever operating system is on there, such as Windows, untouched-they will do a [[Network Boot for Media Directors]] when you want to use them as a Media Director.<br />
<br />
The only special requirement is that the Pluto Core needs to be your DHCP server so that it can offer the plug-and-play and network boot services. You cannot have 2 DHCP servers on the same network (not easily at least). In our Core, we provide [[Why dual network cards?|dual network cards]] one for the "external" network, where your internet is connected, and one for the "internal" network within the house, and into which all your devices are connected. This makes Pluto act as a firewall, and allows it to co-exist with another DHCP server. If you have a DSL or cable modem that needs to be the DHCP server it won't be a problem--just plug it into the "external" port. Pluto's DHCP server only operates on the "internal" one. However, if you have only 1 network card in the Core, you will need to be able to give it a static IP and disable the DHCP server in your DSL/Cable modem. Otherwise you will have to disable Pluto's DHCP server and lose a lot of functionality.<br />
<br />
==Setting Up The Hardware==<br />
<br />
There are many ways to install Pluto, and lots of options for equipment. However, the key components in a Pluto system are the Core (the PC acting as the master server), Media Directors (media PC's connected to your TV's), and Orbiters (remote controls-web pads, pda's, mobile phones, etc.).<br />
<br />
===A Dealer Core===<br />
<br />
<p>If you buy from a Pro dealer, they will come to your home, analyze your situation, and make the decision with you. They will offer a complete, custom-installed solution.</p><br />
<p>If you buy from regular dealer, the first thing you will need to get is 1 Core. This is the brains behind the whole system, and it must run 24/7 since it will be providing all the services in your home, like the security system, media server, phones, etc. Also, all the media in the home (movies, music, etc.) will be stored on the Core. Most dealers sell Cores that are commercial servers with massive storage and full redundancy so they will run non-stop without incident. Since these Cores are often bulky, they are normally tucked away in a wiring closet or equipment rack. However, you can also hook the Core up to your TV and use it as your first media director--we call this a hybrid. Prices for Cores vary from under $1,000 for a basic Pentium PC, up to $7,000+ for a dual Xeon model with 4TB of storage. See our ***Core comparisson*** guide for help deciding.</p><br />
<p>Then for each TV area where you want media you will need a media director. It's easy to add or remove media directors at any time. See our ***media director comparisson guide***.</p><br />
<p>For Orbiters you can either buy touch-screen tablets from a Pluto dealer ***comparisson guide***. Be sure to get a Bluetooth-enabled Symbian http://www.series60.com phone from your local mobile phone carrier--they make great remote controls.</p><br />
<p>Also view our http://plutohome.com/index.php?section=compatibility to see what 3rd party devices will work with Pluto, like lighting control systems, cameras, alarm panels, etc.</p><br />
<br />
<br />
=== I will use my own PC's ===<br />
<br />
<p><b>First a warning</b> Pluto is Linux-based, but don't worry. If you don't know Linux you'll never have to see a Linux prompt, the kick-start will do everything and the only interaction you need with Pluto is through a web interface, <b>*IF*</b> (here's the warning) your hardware is supported. Sometimes drivers are not available for Linux as soon as they are for Windows. Particularly, if you bought some new, exotic hardware there may not be drivers. If the kick-start CD (which is based on Debian's) is not able to recognize all your hardware and find the drivers, then things can get complicated. If you're looking to get some new hardware to run Pluto you may want to check sites like http://www.linuxcompatible.org to be sure it's supported under Linux before you buy. Or maybe post a "will this work?" message in our forum. If you already have the hardware it can't hurt to try. We've seen that about 80% of PC's are fully supported by the kick-start cd and will not require any intervention.</p><br />
<br />
<p>You will need one PC to run the <b>Core</b> software. Although you could install the Core ontop of your existing Windows/Linux o/s, or build from source, it will be tricky and you will miss out on a lot of features. You really needs to use our own distribution because, in addition to our own software, Pluto also includes lots of other open source projects, like Asterisk, Firefox, Xine, VideoLan, etc. We built "wrappers" for all of them which is how we get them all to work together seamlessly. For example, if you start watching a movie in 1 room, Pluto will use Xine on that local media director. Use the orbiter to move that movie to 2 rooms, and Pluto seamlessly detects the network capabilities (multi-cast switch, etc.), moves the video source to the Core using VideoLan, broadcasts to both rooms, uses VLC to do the rendering and changes the UI on the remote controls. If you use the vanilla packages from, say Fedora, none of that will work. Plus, a lot of Pluto's more advanced, kernel-level modules, like plug-and-play, bandwidth shaping to ensure your phone calls are clear, network boot, and so on may not work on other Linux distributions and definately cannot be done under Windows. So, we highly recommend you dedicate 1 PC and install Pluto's own distribution with our kick-start CD--it's fast and requires no technical skills. You can still use this as your normal, Linux PC--our distro is based on Debian Sarge and we take nothing out. You can add whatever software/desktop environment you want, and this PC can also be your first media director.</p><br />
<br />
<p>Note this PC should always be left on since it becomes the 'brains' for the whole house and all the other pieces won't function unless they can find the <b>Core</b>. In our commercial product, the Core is a fail-safe, redundant server.</p><br />
<br />
<p>There is only <b>one special requirement</b>. The Core needs to be your DHCP server so that it can offer the plug-and-play and network boot services. You cannot have 2 DHCP servers on the same network (not easily at least). If you have another DHCP server (like a cable/dsl modem), we recommend your Core have dual network cards: one for the "external" network, where your internet is connected, and one for the "internal" network within the house, and into which all your devices are connected. This makes Pluto act as a firewall, and allows it to co-exist with another DHCP server. If you have a DSL or cable modem that needs to be the DHCP server it won't be a problem--just plug it into the "external" port. Pluto's DHCP server only operates on the "internal" one. However, if you have only 1 network card in the Core, you will need to be able to give it a static IP and disable the DHCP server in your DSL/Cable modem. Otherwise you will have to disable Pluto's DHCP server and lose a lot of functionality.</p><br />
<br />
<p>You can also put other cards in the Core, such as analog phone line interfaces from www.digium.com for the phone system or analog video capture cards for surveillance cameras. You can put the PVR/satellite capture cards in the individual media PC's, or you can put several in the Core, which will share the video throughout the house.</p><br />
<br />
<p>Wherever you have a TV/Stereo you can use a PC or thin-client as the Media Director--it doesn't need to be on all the time and there's no software to install since they will network boot off the Core. Just be sure it supports has a good sound card, a Linux-compatible video card, supports PXE network boot (nearly all recent motherboards do), and optionally a PVR card. To use the Bluetooth mobile phones as remote controls, add a USB Bluetooth Dongle for each media director (around $25). All the media directors will report the signal strengths of all the mobile phones--this is how the Core figures out what room you're in. Since all resources in the whole house are shared, you will be able to control any device in any room from anywhere--as long as you're within Bluetooth range of any media director (about 10m or 30feet), you will have control over everything in the house. You can also use low-cost network audio players, like the Squeeze Box, wherever you want to add music.</p><br />
<br />
<p>To control the system, you can use the PC's mouse and keyboard, or an infrared remote, or run the Orbiter software on your mobile phones, webpads and PDA's.</p><br />
<br />
<p>Also view our http://plutohome.com/index.php?section=compatibility to see what 3rd party devices will work with Pluto, like lighting control systems, cameras, alarm panels, etc.</p><br />
<br />
===A Dedicated Core===<br />
<br />
<p>The Core is the central point of the Linux MCE system and runs applications and daemons needed for the other devices to exchange messages. A dedicated core will run only the backed applications and will not provide any fronted except the web interface, this means you won't act as a media center. You'll need to use Media Directors to be able to play movies, listen to music and watch TV. This kind of setup is recommended when you have lot of extra devices, this way the backend applications will have full access to Core's resources.</p><br><br />
<br />
[[Image:Diagram1.jpg|200px]]<br />
<br />
===A Dedicated Hybrid===<br />
<br />
A "hybrid" just means the computer that is running is the "Core" software is also running the "Media Director" software-you use the Core as a Media Director. The only reason we don't recommend this in our high-end installations is because a computer suitables for a Core is usually a pretty massive box with major hard drive capacity and rather noisy, so it's shoved away in the wiring closet, rather than sitting next to a TV like a Media Director would. However, you can use a regular PC as the Core + Media Director (Hybrid) also. Just remember that it will need to always be on since the Core software is what controls everything in the house.<br />
<br />
[[Image:Diagram2.jpg|200px]]<br />
<br />
Be sure you complete the installation of your Core/Hybrid before trying to boot the media directors.<br />
<br />
==Installation==<br />
<br />
===Pre-installation Setup===<br />
<br />
'''Note:''' During the installation, you may have some difficulties that can be avoided by following the advise below:<br />
<br />
# Make sure you have an Internet connection prior to starting! After Pluto installs from the disk, it will need to access the Internet and download the latest patches. (More often than not, you want this!)<br />
# Confused about which ethernet adapter should be your "main" when that option is given to you during the install? Just click on one. You have a 50/50 chance of getting it right. You can easily change it later in the pluto-admin pages by selecting "Advanced -> Network -> Network Settings" from the drop-down and clicking "Swap Interfaces".<br />
# Use the core's DHCP server to give machines on your network a dynamic IP address. Turn off the DHCP server on any other devices you may have on your network! This is very important! You probably already have your home router giving out addresses. Check the configuration and turn that feature off. Pluto uses the DHCP requests from machines that come online to figure out what they are and what to do with them.<br />
# A map of your home. This is actually a very important step because Pluto seems to need the map to properly finish the installation of some devices. It is easy to create a map using any drawing software or just draw one by hand and scan it. You don't need anything fancy, just some squares representing your different rooms. If the file is too big, Pluto will scale it to fit. You can always upload a new map later on when you feel like being more creative. You can also make multiple maps, say, one for each floor or section of your house. This will all make more sense later when you get into configuring the devices.<br />
<br />
===Download===<br />
Download the Kickstart CD and Extra CD [http://plutohome.com/index.php?section=get_pluto here].<br />
<br />
===Software Installation===<br />
The Kickstart CD is based upon and incorporates Debian Sarge. If you want to know more about installing Debian, click [http://www.debian.org/releases/stable/i386/index.html.en here].<br />
<br />
During the installation, you will be asked what you want to install, a Pluto Home Core, a Pluto Home Hybrid, which is a Core and a Media Director or other. <br />
<br />
You will also be asked if you have a broadband internet connection, and if you have the Pluto Extras CD. I have been unsuccessful in installing a Pluto Home Core without the Extras CDs. It looks like there is an error in the bootscript generation scripts that makes the system hang. <br />
<br />
When you first insert the Extras CD and instruct the system to use it, you will receive sparse information about what is happening. You'll see PLEASE WAIT and you will see CD and hard disk activity. On slower systems, whatever is being done will take several minutes. Be patient, the system will eventually return. If you want to see what's going on, you can switch to another console and look at the logfiles. <br />
<br />
Once the system returns, you'll see a whole lot of activity. Be patient.<br />
<br />
===Finalize The Install===<br />
<br />
<p>After you have set everything up, you should do a full reboot of the "Pluto universe", meaning rebooting the Core/Hybrid plus any media directors.<br />
You can do this by choosing "Restart" from the Pluto Admin site wizard (the last option), or from any orbiter or media director by clicking the Pluto logo on the main menu and choosing "Reboot Core".</p><br />
<p>If your media directors support both software power off and wake on lan, the core will turn them off before it reboots itself, and will turn them back on when it has finished booting up. If not, you may need to reboot the media directors manually by cycling power on them. Note that you should not turn the media directors on until the Core/Hybrid has finished booting up.</p><br />
<br />
==Configuration==<br />
<br />
===Tell Pluto About Your Home===<br />
<br />
[[Tell Pluto about your home]] shows you how to use our Pluto Admin wizard. In about 2 hours you can have everything setup--the whole-house media server, full control all your lights, climate, and tv/hi-fi gear, the phone system, follow-me, everything. It's quick, painless, and non-technical.<br />
<br />
===Adding Other Devices===<br />
<br />
If you chose a "Core", not being used as a Media Director, then it will boot up and you will see a simple menu like this:<br><br />
[[Image:Console.jpg|200px]]<br />
<em>Pluto Core; After boot-up menu</em><br><br><br />
<p>You don't need to do anything. Your Core is up and running. Just make note of the IP address - you will need it to configure the system. </p><br />
<p>If you chose a "Hybrid", that is you are using your Core as a Media Director, it will boot up to the same welcome menu as any media director. Note that the welcome menu will appear on the first boot. After that, it will boot to the normal main menu, however, you can click the Pluto logo in the lower left corner of the main menu to see the advanced options, including all the buttons on the welcome menu.</p><br><br />
[[Image:Welcome.jpg|200px]]<br />
<br />
<p>You need a web browser to configure your Pluto system using the built-in [[Pluto Admin Website]]<br />
Since the Hybrid + Media Directors have one built in, you can just click the "Pluto Admin" website to bring it up directly on the Hybrid. Or, from any web browser in your home, go to the URL: http://myip/pluto_admin where myip is the IP address of the<br />
Core/Hybrid. <br />
Login then click [[Wizard Pages|Wizard]]. You will see the following screen.</p><br />
[[Image:Wizard.jpg|200px]]<br />
<br />
<p>Follow each of the links in the left panel to choose your basic settings, add the devices, scenarios, and event handlers. <br />
Here's an example for setting up an ultra low-cost smart home setup based on X10. The equipment we mention will cost under $1,000, although the procedure is exactly the same with a $100,000 high-end based on Lutron, Vantage, EIB, etc. So, please read the example regardless of your system type, so you understand the techniques.</p><br />
<p><b>EXAMPLE: Adding other devices</b></p><p>Example:<br />
You have 2 gc100's which give you Infrared control of you're a/v equipment, extra serial ports to plug other stuff into, ttl inputs and relays. You have some tv's and stereo's to control, and also a CM11A module to control X10 devices, plus some X10 lights and thermostats.<br />
You will plug the CM11A into one of the rs232 serial ports on the gc100. You also have an alarm panel with a serial interface, some squeeze box audio players, and some network cameras.</p><br />
<br />
<p>After specifying [[Basic Info]] on the first couple wizard pages, like family members and rooms, you get to [[Interfaces]].<br />
Here you add all the devices that are used to interface with, or control other devices. So, the gc100 is an interface device, but the tv's and stereo's it controls are on the a/v page. The CM11A, Vantage, Lutron, etc. are also interfaces, the lights, blinds, drapes, etc. they control are on the [[Lights|lighting page]]. The alarm panel is an interface, the motion, glassbreak, smoke alarms, etc., are on the [[Security]].<br />
Some home automation devices do not require an interface, some do. An IP-based camera does not require an interface device-add it directly to [[Surveillance Cameras]].<br />
Analog cameras do need some sort of interface device, like a camera capture board, which you must first add to the interfaces page. Add the interface devices first on the interface page, and then the devices they control on the respective page. If you want to add EIB lights (on the lights page), you won't be allowed to do that until you first add the EIB interface on the interfaces page, because an EIB light cannot be used with an interface. If you add interfaces for both an EIB Lighting system, and an X10 lighting system, then on the lighting page you will be able to add both types of lights, and the 'Controlled Via' field will show you what interface is being used.</p><br />
<p>Back to our example: Plug one of your gc100's into the network, and click the 'add gc100' button on the interface page. gc100's are treated special because they are IP-based, but their network configuration is a bit different and does not allow them to be plug-and-play. Once you got the message that it was found and configured, click on the Interfaces page again--now you'll see it there. Maybe give it a descriptive name so you can remember which is which. Now plug in the 2nd gc100, and repeat.<br />
Next choose 'Add Devices' and add the CM11A. Like all RS232 devices, it is not plug and play, you must add it manually. Repeat for the alarm panel. In both cases, the Controlled Via devices is the Core, since that's where the software drivers will be run. But, when you go to choose the port, it only shows the Core's internal serial ports, and you want to plug it into one of the ports on the gc100. So, click 'Wizard', 'Restart' and 'quick reload router'. That causes the DCE Router to reload the list of devices in the house so it sees the new gc100's you added, and adds the ports. Refresh the Interfaces page, and now you can choose the gc100 ports for the CM11A and alarm panel.</p><p>Next, add your tv's and stereo's on the [[AV Devices]] and indicate how they are connected (which AV inputs). If your model is not in the database you will need to add it. If the I/R codes for your device aren't listed or don't work, you will click the A/V properties button and either [[Learning/typing my own code|learn them]] using the gc100's learner (plug it into serial port 1 and click 'learn'), or [[Learning/typing my own code|copy+paste the I/R codes in pronto format]] from a source like www.remotecentral.com. Your devices and I/R codes will automatically be sent to Pluto and added to the master database for other users unless you uncheck the box. In the 'controlled via' chose whichever one of the gc100's has the infrared emitter attached for that device. Turn your Squeeze Boxes on, set the network to DHCP, and plug them in. Pluto will automatically recognize them and configure them. You will see a confirmation message and be asked to pick the room they're in. Refresh the A/V page to see the Squeeze Boxes and indicate how you connect them to your stereo system.</p><br />
<br />
<p>On the [[Media Directors]] and [[Orbiters]] page, be sure your settings are correct. Then on the [[Lights]] and [[Climate]] pages, add all your X10 lights/thermostats. The 'Controlled Via' is the cm11A device. On the security page, add all your motion detectors, smoke alarms, etc. The 'Controlled Via' is the alarm panel. <br />
On the [[Floorplans]], drag and drop your devices on the maps you upload. You'll need to do a 'regen orbiter' followed by a 'quick reload router' before you can use the floorplans.</p><br />
<br />
<p>Now let's test the devices. Do another 'quick reload router' so DCERouter sees these new devices. Go back to a device, like a light, click 'ADV' to go to the advanced page, or go there manually by choosing [[Devices]] from the menu. Click 'Send command to device', and choose a command. If it doesn't respond, go to 'Advanced', 'Logs' and check the logs for the interface, the CM11A in this case.</p><br />
<br />
===Scenarios, Events & Security===<br />
<br />
<p>In the [[Scenarios]] page, add the scenarios, or buttons, you want for each room. Like a Lighting scenario in the Bedroom called 'Go to sleep' which dims the lights, or a security scenario in the living to view a camera. When you do a 'quick reload router', DCERouter will automatically add Media Scenarios for each room for whatever media devices are in there. But your new scenarios are not visible on the Orbiter until you regenerate--see the note below in 'Using Pluto with an Orbiter'. Next add [[Events]], in other words, when something happens (a motion detector is tripped, the sun sets, etc.) you want Pluto to do this (turn on a light). Also set security options, like how you want to be notified when something happens in the house. Each page has context sensitive help to explain everything. They will take effect next time you reboot or 'quick reload router'.</p><br />
<br />
===Configuring Myth TV===<br />
<br />
This section has been moved to [[Setting up MythTV]].<br />
<br />
===Upload Your Media===<br />
<br />
<p>There will also be Microsoft Windows compatible network shares on the Core or Hybrid (uses Samba) . There is a "public" share for putting all files that the whole family can share--movies, music, etc. And there is a private share for each family member. To access these network shares in Windows, choose Start, Run, and type \\ plus the IP address of the Core or hybrid. <br />
<br />
For example: \\192.168.80.1 Note that if you add new family members, their network share will not be available until after you reboot the Core/Hybrid. Once you copy your media into the appropriate folder, you can go into the Pluto Admin site, choose "Files &amp; Media" and "Media Files Sync" to be sure your media is in the database, add attributes (artist, actor, etc.), and choose cover art.</p><br />
<br />
==Using Pluto==<br />
<br />
This secion has been moved to [[Using Pluto]]. In 10 minutes you'll be up to speed and using all of Pluto's features.<br />
<br />
<p><b>Using Pluto with an Orbiter</b></p><br />
<p>Orbiter is just our way of saying remote control. All the Media Directors run an on-screen Orbiter, like the one below. Choose options on the on-screen orbiter with a keyboard/mouse attached to the media director, or with an infrared remote control. The Orbiter software runs on Linux, Windows and Windows CE, and can also be run on webpads and PDA's.<br />
Either way, it works exactly the same.</p><p>Below is the main menu. In the lower right are the [[Who Am I, Where Am I|'who' and 'where']] buttons. This indicates what room you are in, or want to control, and which family member is using the Orbiter. <br />
<br />
Touch either button if this isn't correct. Even if you are using an on-screen orbiter on the media director in the Living Room, for example, you can still change the location to the Bedroom. That means you would be using the Media Director in the Living Room as a remote control for the devices in the bedroom. Normally you don't change the location for an on-screen orbiter, since that device stays in a fixed place, but you do when you have a wireless web pad or pda you carry around.</p><br />
<br />
<p>The icons on the left all lead to a [[maps]], or floorplan, of your house showing your lighting, media, climate, telecom and security devices. Next to each of the floorplan icons are the scenarios for that category and the given room. In the scenarios section of the Pluto Admin web site you create the scenarios for each room. You can have a lighting scenario called 'entertaining guests' that sets some lights, plays some background music, unlocks the door, and so on.<br />
<br><br />
[[Image:Main-menu.jpg|200px]]<br />
<br />
[[Image:Litscen.jpg|200px]]<br><br />
<br />
<p><b>NOTE:</b><br />
Many orbiters have relatively slow processors (like PDA's and phones) and may be running on slow wi-fi connections. So, the orbiters do not retrieve the large, full-size graphics, scaling them, drawing the text, and rendering everything on the fly. <br />
<br />
Rather all the graphics on your Orbiter are pre-scaled and pre-rendered by OrbiterGen. This means that if you add new scenarios or devices, or change floorplans or skins, you won't see them immediately on the Orbiter. You must go to the 'Advanced<br />
Options' page by clicking the Pluto logo on the main menu, and choose 'Regenerate this Orbiter'. You'll be asked to wait about 60 seconds or so while the renderer creates new graphics, and then the Orbiter willreload.</p><br />
<br />
<p><b>Using your system with a Mobile Orbiter</b></p><br />
<p>Unless you turned off the "Auto Detect new Bluetooth Phones" option for the Media Director, compatible Bluetooth Mobile phones will automatically be detected when they are within range of any Media Director if they have Bluetooth turned on. A message will appear on all the Orbiters asking if it's a phone, and if so, to whom it belongs. Be sure you add your family members to the Pluto Admin web site before doing this. Also, you may need to turn on the TV to see the message on the on-screen orbiter.</p><br />
<br />
<p>If you choose to install the software, the phone will beep. Just hit 'yes' to accept the software, and accept the default prompts.</p><p>The mobile orbiter works pretty much like a regular orbiter. The difference is that you don't usually need to worry about the "who" and "where" button. The "who" is determined when you chose to install the software. That family member is assumed to always be the user. And the "where" is automatic-whenever you come within range of a media director it will automatically switch to the correct location. You can press the button under the location if you want to control a location other than the one you are in.</p><br />
<br />
<p>Since the display is smaller, rather than showing all the scenarios on the main menu, you must first choose the category, like lighting, and then choose the scenario from the sub menu that appears. You can also hold the category to toggle 'follow-me' mode, indicated with a red F. So, if you hold down the 2 button, a red F appears for media. Now as you move around the house your media will follow you. All 5 categories have follow-me. <a<br />
href="http://plutohome.com/index.php?section=how_pluto_works">Screen shots of the Mobile Orbiter</a> / [[User's manual]]</p><br />
<br />
==Troubleshooting==<br />
<br />
[[Testing_and_troubleshooting_devices]]<br />
<br />
<p>[[Development status for all modules|What works and what doesn't?]]</p><br />
<br />
<p>If you don't know Linux at all, you can go into the Pluto Admin website and choose [[Outside Access]], and check the box to get outside assistance from Pluto. You will pick a password you will give one of our tech support staff. When you do, your system will make a secure, encrypted connection back to our support staff giving us temporary access to your system. The connection is closed as soon as you uncheck the box. Without checking that box, nobody at Pluto will have any access to your system.</p><br />
<br />
<p>This troubleshooting guide assumes some basic knowledge of Linux. In Pluto, everything is a device. In the Pluto Admin web site, you can choose [[Devices]], to see a list of all the devices in your installation. We recommend you don't make changes here - you can break things! The top level device is usually a computer, either the core or a hybrid or an orbiter. All the logs for the devices on that computer are stored in /var/log/pluto. You can ssh in to the core using the root password you chose, and from there, you can ssh to all the media directors-shared keys were automatically setup.</p><br />
<p>All current activity is logged in the file that ends in ".newlog". After a device crashes, its logs are moved into<br />
the ".log" directory. At bootup, all logs are archived into /var/log/pluto/archives.</p><br />
<br />
<p>All DCE devices are running in separate screen sessions. Type "screen -ls" to see all active screen sessions,<br />
and "screen -r PID" where PID is the id you saw in the -ls list to attach to the screen session. There is not much for you to do or see though since all the output on stderr and stdout is going into the logs. DCERouter is running the same way on your core or hybrid.</p><br />
<br />
<p>At bootup, all the scripts listed in the Pluto Admin website under [[Boot Sequence]] are run. If any programs crash, a core dump file is put in /usr/pluto/coredump. At each reboot, any core dumps are archived with the log files in /var/log/pluto/archives. A database dump/configuration snapshot are also put in each archive. Archives are deleted after 5 days.</p><br />
<br />
<p>If you're a programmer, you can also check out our [[Programmer's Guide]]. If you want to learn about writing DCE Devices, see the [[DCE]].<br />
</p><br />
<br />
<br />
''Note:''<br />
<p>We had to leave some basic features out of the free version due to licensing issues. See [http://www.yttron.as.ro http://www.yttron.as.ro] for a list. If you purchase a pre-built Pluto system, some or all of these technologies may be licensed and the license fee built into the purchase price. Before contacting Pluto support to ask why something doesn't work, please refer to that site so you know what features were left out intentionally. Note that Pluto does not encourage, endorse or support users adding 3rd party modules, nor did Pluto develop those modules. If you choose to add 3rd party modules we suggest you first confirm they are legal in your area.</p></div>Razvanghttp://wiki.linuxmce.org/index.php?title=Getting_Started&diff=3047Getting Started2007-03-14T00:38:41Z<p>Razvang: /* A Dedicated Core */</p>
<hr />
<div><table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>==Equipment: Picking The Right Components==<br />
<br />
[http://plutohome.com/index.php?section=pluto_system_overview Equipment overview]<br />
<br />
===The Core===<br />
<br />
Most important, is the "core". This is the main Pluto server that runs all the applications. The commercial version uses a high-end server with RAID-5 storage. You'll probably get by with a good Pentium 4, least 80 GB of storage, two network cards (Gigabit ideally).<br />
<br />
It would be best to use a dedicated core, which means you'll end up putting this computer somewhere out of the way and not connecting a monitor to it. If you are using only one computer for your system, then you've chosen the "hybrid" system, which means that your core will also be your media player. You'll definitely need a monitor or TV for this system!<br />
<br />
===Media Directors===<br />
<br />
Note that each media director will need a Bluetooth dongle if you want to use a Bluetooth mobile phone as the remote in that area. To control your a/v equipment using infrared, you will need an interface module (global cache gc100). This interface module also gives you extra serial ports. So, in this example, the TV is controlled by infrared, and the receiver by RS232.<br />
<br />
[[Sound Cards]]<br />
<br />
[[Network_Boot_for_Media_Directors]]<br />
<br />
===Orbiters===<br />
<br />
===Network Attached Storage===<br />
<br />
An alternative to having a lot of memory in the core is to have a small hard drive for the core and store all your files on a [[Network Attached Storage|network attached storage]] (or NAS) server. The [http://www.buffalotech.com/products/product-detail.php?productid=97 Buffalo TeraStation] is 1.0 TeraByte RAID-5 and under $1K(US). Having a NAS will allow you to not lose your precious media files. You'll likely want the larger storage for your collection of music and videos. Keep in mind that your Pluto system can also record TV shows (using MythTV) and video from your security cameras (using Motion).<br />
<br />
===Additional Devices===<br />
<br />
[[Recommended_Accessories]]<br />
<br />
Optionally, you may want the aformentioned home automation devices for controlling your lights. Also, optionally, you may want security cameras, plasma screen TV, a streaming media music player such as the [http://www.slimdevices.com Squeezebox], an alarm system with a serial interface, etc. Some of these devices need ''another'' device called a [http://www.globalcache.com/products/gc-index.html gc100]. This allows devices that communicate using a serial port (good alarm panels) or infrared (like your TV) to connect to the network and talk with your Pluto core.<br />
<br />
===Location Considerations===<br />
<br />
This section has been moved to [[Choosing_Locations]].<br />
<br />
===Wiring Considerations===<br />
<br />
[[Wiring Considerations]]<br />
<br />
There are 2 basic configurations, which we officially test and support. Both require that the Core be [[Do I want a dedicated Core?|dedicated]], meaning that you use the [[Kick-Start CD]] and let Pluto "take over" the computer. If you're a Linux user, you can still use the dedicated Core as a Debian Linux PC. Otherwise, once Pluto is installed, just treat it like an appliance--plug it in, turn it on, and leave it alone. The great news is that don't need to install any software on the media PC's that will be used as media directors.<br />
You can leave whatever operating system is on there, such as Windows, untouched-they will do a [[Network Boot for Media Directors]] when you want to use them as a Media Director.<br />
<br />
The only special requirement is that the Pluto Core needs to be your DHCP server so that it can offer the plug-and-play and network boot services. You cannot have 2 DHCP servers on the same network (not easily at least). In our Core, we provide [[Why dual network cards?|dual network cards]] one for the "external" network, where your internet is connected, and one for the "internal" network within the house, and into which all your devices are connected. This makes Pluto act as a firewall, and allows it to co-exist with another DHCP server. If you have a DSL or cable modem that needs to be the DHCP server it won't be a problem--just plug it into the "external" port. Pluto's DHCP server only operates on the "internal" one. However, if you have only 1 network card in the Core, you will need to be able to give it a static IP and disable the DHCP server in your DSL/Cable modem. Otherwise you will have to disable Pluto's DHCP server and lose a lot of functionality.<br />
<br />
==Setting Up The Hardware==<br />
<br />
There are many ways to install Pluto, and lots of options for equipment. However, the key components in a Pluto system are the Core (the PC acting as the master server), Media Directors (media PC's connected to your TV's), and Orbiters (remote controls-web pads, pda's, mobile phones, etc.).<br />
<br />
===A Dealer Core===<br />
<br />
<p>If you buy from a Pro dealer, they will come to your home, analyze your situation, and make the decision with you. They will offer a complete, custom-installed solution.</p><br />
<p>If you buy from regular dealer, the first thing you will need to get is 1 Core. This is the brains behind the whole system, and it must run 24/7 since it will be providing all the services in your home, like the security system, media server, phones, etc. Also, all the media in the home (movies, music, etc.) will be stored on the Core. Most dealers sell Cores that are commercial servers with massive storage and full redundancy so they will run non-stop without incident. Since these Cores are often bulky, they are normally tucked away in a wiring closet or equipment rack. However, you can also hook the Core up to your TV and use it as your first media director--we call this a hybrid. Prices for Cores vary from under $1,000 for a basic Pentium PC, up to $7,000+ for a dual Xeon model with 4TB of storage. See our ***Core comparisson*** guide for help deciding.</p><br />
<p>Then for each TV area where you want media you will need a media director. It's easy to add or remove media directors at any time. See our ***media director comparisson guide***.</p><br />
<p>For Orbiters you can either buy touch-screen tablets from a Pluto dealer ***comparisson guide***. Be sure to get a Bluetooth-enabled Symbian http://www.series60.com phone from your local mobile phone carrier--they make great remote controls.</p><br />
<p>Also view our http://plutohome.com/index.php?section=compatibility to see what 3rd party devices will work with Pluto, like lighting control systems, cameras, alarm panels, etc.</p><br />
<br />
<br />
=== I will use my own PC's ===<br />
<br />
<p><b>First a warning</b> Pluto is Linux-based, but don't worry. If you don't know Linux you'll never have to see a Linux prompt, the kick-start will do everything and the only interaction you need with Pluto is through a web interface, <b>*IF*</b> (here's the warning) your hardware is supported. Sometimes drivers are not available for Linux as soon as they are for Windows. Particularly, if you bought some new, exotic hardware there may not be drivers. If the kick-start CD (which is based on Debian's) is not able to recognize all your hardware and find the drivers, then things can get complicated. If you're looking to get some new hardware to run Pluto you may want to check sites like http://www.linuxcompatible.org to be sure it's supported under Linux before you buy. Or maybe post a "will this work?" message in our forum. If you already have the hardware it can't hurt to try. We've seen that about 80% of PC's are fully supported by the kick-start cd and will not require any intervention.</p><br />
<br />
<p>You will need one PC to run the <b>Core</b> software. Although you could install the Core ontop of your existing Windows/Linux o/s, or build from source, it will be tricky and you will miss out on a lot of features. You really needs to use our own distribution because, in addition to our own software, Pluto also includes lots of other open source projects, like Asterisk, Firefox, Xine, VideoLan, etc. We built "wrappers" for all of them which is how we get them all to work together seamlessly. For example, if you start watching a movie in 1 room, Pluto will use Xine on that local media director. Use the orbiter to move that movie to 2 rooms, and Pluto seamlessly detects the network capabilities (multi-cast switch, etc.), moves the video source to the Core using VideoLan, broadcasts to both rooms, uses VLC to do the rendering and changes the UI on the remote controls. If you use the vanilla packages from, say Fedora, none of that will work. Plus, a lot of Pluto's more advanced, kernel-level modules, like plug-and-play, bandwidth shaping to ensure your phone calls are clear, network boot, and so on may not work on other Linux distributions and definately cannot be done under Windows. So, we highly recommend you dedicate 1 PC and install Pluto's own distribution with our kick-start CD--it's fast and requires no technical skills. You can still use this as your normal, Linux PC--our distro is based on Debian Sarge and we take nothing out. You can add whatever software/desktop environment you want, and this PC can also be your first media director.</p><br />
<br />
<p>Note this PC should always be left on since it becomes the 'brains' for the whole house and all the other pieces won't function unless they can find the <b>Core</b>. In our commercial product, the Core is a fail-safe, redundant server.</p><br />
<br />
<p>There is only <b>one special requirement</b>. The Core needs to be your DHCP server so that it can offer the plug-and-play and network boot services. You cannot have 2 DHCP servers on the same network (not easily at least). If you have another DHCP server (like a cable/dsl modem), we recommend your Core have dual network cards: one for the "external" network, where your internet is connected, and one for the "internal" network within the house, and into which all your devices are connected. This makes Pluto act as a firewall, and allows it to co-exist with another DHCP server. If you have a DSL or cable modem that needs to be the DHCP server it won't be a problem--just plug it into the "external" port. Pluto's DHCP server only operates on the "internal" one. However, if you have only 1 network card in the Core, you will need to be able to give it a static IP and disable the DHCP server in your DSL/Cable modem. Otherwise you will have to disable Pluto's DHCP server and lose a lot of functionality.</p><br />
<br />
<p>You can also put other cards in the Core, such as analog phone line interfaces from www.digium.com for the phone system or analog video capture cards for surveillance cameras. You can put the PVR/satellite capture cards in the individual media PC's, or you can put several in the Core, which will share the video throughout the house.</p><br />
<br />
<p>Wherever you have a TV/Stereo you can use a PC or thin-client as the Media Director--it doesn't need to be on all the time and there's no software to install since they will network boot off the Core. Just be sure it supports has a good sound card, a Linux-compatible video card, supports PXE network boot (nearly all recent motherboards do), and optionally a PVR card. To use the Bluetooth mobile phones as remote controls, add a USB Bluetooth Dongle for each media director (around $25). All the media directors will report the signal strengths of all the mobile phones--this is how the Core figures out what room you're in. Since all resources in the whole house are shared, you will be able to control any device in any room from anywhere--as long as you're within Bluetooth range of any media director (about 10m or 30feet), you will have control over everything in the house. You can also use low-cost network audio players, like the Squeeze Box, wherever you want to add music.</p><br />
<br />
<p>To control the system, you can use the PC's mouse and keyboard, or an infrared remote, or run the Orbiter software on your mobile phones, webpads and PDA's.</p><br />
<br />
<p>Also view our http://plutohome.com/index.php?section=compatibility to see what 3rd party devices will work with Pluto, like lighting control systems, cameras, alarm panels, etc.</p><br />
<br />
===A Dedicated Core===<br />
<br />
<p>The Core is the central point of the Linux MCE system and runs applications and daemons needed for the other devices to exchange messages. A dedicated core will run only the backed applications and will not provide any fronted except the web interface, this means you won't act as a media center. You'll need to use Media Directors to be able to play movies, listen to music and watch TV. This kind of setup is recommended when you have lot of extra devices, this way the backend applications will have full access to Core's resources.</p><br><br />
<br />
[[Image:Diagram1.jpg|200px]]<br />
<br />
===A Dedicated Hybrid===<br />
<br />
A "hybrid" just means the computer that is running is the "Core" software is also running the "Media Director" software-you use the Core as a Media Director. The only reason we don't do this in our high-end installations is because the Core is usually a pretty massive box with major hard drive capacity and rather noisy, so it's shoved away in the wiring closet, rather than sitting next to a TV like a Media Director would. However, you can use a regular PC as the Core + Media Director (Hybrid) also. Just remember that it will need to always be on since the Core software is what controls everything in the house.<br />
<br />
[[Image:Diagram2.jpg|200px]]<br />
<br />
Be sure you complete the installation of your Core/Hybrid before trying to boot the media directors.<br />
<br />
==Installation==<br />
<br />
===Pre-installation Setup===<br />
<br />
'''Note:''' During the installation, you may have some difficulties that can be avoided by following the advise below:<br />
<br />
# Make sure you have an Internet connection prior to starting! After Pluto installs from the disk, it will need to access the Internet and download the latest patches. (More often than not, you want this!)<br />
# Confused about which ethernet adapter should be your "main" when that option is given to you during the install? Just click on one. You have a 50/50 chance of getting it right. You can easily change it later in the pluto-admin pages by selecting "Advanced -> Network -> Network Settings" from the drop-down and clicking "Swap Interfaces".<br />
# Use the core's DHCP server to give machines on your network a dynamic IP address. Turn off the DHCP server on any other devices you may have on your network! This is very important! You probably already have your home router giving out addresses. Check the configuration and turn that feature off. Pluto uses the DHCP requests from machines that come online to figure out what they are and what to do with them.<br />
# A map of your home. This is actually a very important step because Pluto seems to need the map to properly finish the installation of some devices. It is easy to create a map using any drawing software or just draw one by hand and scan it. You don't need anything fancy, just some squares representing your different rooms. If the file is too big, Pluto will scale it to fit. You can always upload a new map later on when you feel like being more creative. You can also make multiple maps, say, one for each floor or section of your house. This will all make more sense later when you get into configuring the devices.<br />
<br />
===Download===<br />
Download the Kickstart CD and Extra CD [http://plutohome.com/index.php?section=get_pluto here].<br />
<br />
===Software Installation===<br />
The Kickstart CD is based upon and incorporates Debian Sarge. If you want to know more about installing Debian, click [http://www.debian.org/releases/stable/i386/index.html.en here].<br />
<br />
During the installation, you will be asked what you want to install, a Pluto Home Core, a Pluto Home Hybrid, which is a Core and a Media Director or other. <br />
<br />
You will also be asked if you have a broadband internet connection, and if you have the Pluto Extras CD. I have been unsuccessful in installing a Pluto Home Core without the Extras CDs. It looks like there is an error in the bootscript generation scripts that makes the system hang. <br />
<br />
When you first insert the Extras CD and instruct the system to use it, you will receive sparse information about what is happening. You'll see PLEASE WAIT and you will see CD and hard disk activity. On slower systems, whatever is being done will take several minutes. Be patient, the system will eventually return. If you want to see what's going on, you can switch to another console and look at the logfiles. <br />
<br />
Once the system returns, you'll see a whole lot of activity. Be patient.<br />
<br />
===Finalize The Install===<br />
<br />
<p>After you have set everything up, you should do a full reboot of the "Pluto universe", meaning rebooting the Core/Hybrid plus any media directors.<br />
You can do this by choosing "Restart" from the Pluto Admin site wizard (the last option), or from any orbiter or media director by clicking the Pluto logo on the main menu and choosing "Reboot Core".</p><br />
<p>If your media directors support both software power off and wake on lan, the core will turn them off before it reboots itself, and will turn them back on when it has finished booting up. If not, you may need to reboot the media directors manually by cycling power on them. Note that you should not turn the media directors on until the Core/Hybrid has finished booting up.</p><br />
<br />
==Configuration==<br />
<br />
===Tell Pluto About Your Home===<br />
<br />
[[Tell Pluto about your home]] shows you how to use our Pluto Admin wizard. In about 2 hours you can have everything setup--the whole-house media server, full control all your lights, climate, and tv/hi-fi gear, the phone system, follow-me, everything. It's quick, painless, and non-technical.<br />
<br />
===Adding Other Devices===<br />
<br />
If you chose a "Core", not being used as a Media Director, then it will boot up and you will see a simple menu like this:<br><br />
[[Image:Console.jpg|200px]]<br />
<em>Pluto Core; After boot-up menu</em><br><br><br />
<p>You don't need to do anything. Your Core is up and running. Just make note of the IP address - you will need it to configure the system. </p><br />
<p>If you chose a "Hybrid", that is you are using your Core as a Media Director, it will boot up to the same welcome menu as any media director. Note that the welcome menu will appear on the first boot. After that, it will boot to the normal main menu, however, you can click the Pluto logo in the lower left corner of the main menu to see the advanced options, including all the buttons on the welcome menu.</p><br><br />
[[Image:Welcome.jpg|200px]]<br />
<br />
<p>You need a web browser to configure your Pluto system using the built-in [[Pluto Admin Website]]<br />
Since the Hybrid + Media Directors have one built in, you can just click the "Pluto Admin" website to bring it up directly on the Hybrid. Or, from any web browser in your home, go to the URL: http://myip/pluto_admin where myip is the IP address of the<br />
Core/Hybrid. <br />
Login then click [[Wizard Pages|Wizard]]. You will see the following screen.</p><br />
[[Image:Wizard.jpg|200px]]<br />
<br />
<p>Follow each of the links in the left panel to choose your basic settings, add the devices, scenarios, and event handlers. <br />
Here's an example for setting up an ultra low-cost smart home setup based on X10. The equipment we mention will cost under $1,000, although the procedure is exactly the same with a $100,000 high-end based on Lutron, Vantage, EIB, etc. So, please read the example regardless of your system type, so you understand the techniques.</p><br />
<p><b>EXAMPLE: Adding other devices</b></p><p>Example:<br />
You have 2 gc100's which give you Infrared control of you're a/v equipment, extra serial ports to plug other stuff into, ttl inputs and relays. You have some tv's and stereo's to control, and also a CM11A module to control X10 devices, plus some X10 lights and thermostats.<br />
You will plug the CM11A into one of the rs232 serial ports on the gc100. You also have an alarm panel with a serial interface, some squeeze box audio players, and some network cameras.</p><br />
<br />
<p>After specifying [[Basic Info]] on the first couple wizard pages, like family members and rooms, you get to [[Interfaces]].<br />
Here you add all the devices that are used to interface with, or control other devices. So, the gc100 is an interface device, but the tv's and stereo's it controls are on the a/v page. The CM11A, Vantage, Lutron, etc. are also interfaces, the lights, blinds, drapes, etc. they control are on the [[Lights|lighting page]]. The alarm panel is an interface, the motion, glassbreak, smoke alarms, etc., are on the [[Security]].<br />
Some home automation devices do not require an interface, some do. An IP-based camera does not require an interface device-add it directly to [[Surveillance Cameras]].<br />
Analog cameras do need some sort of interface device, like a camera capture board, which you must first add to the interfaces page. Add the interface devices first on the interface page, and then the devices they control on the respective page. If you want to add EIB lights (on the lights page), you won't be allowed to do that until you first add the EIB interface on the interfaces page, because an EIB light cannot be used with an interface. If you add interfaces for both an EIB Lighting system, and an X10 lighting system, then on the lighting page you will be able to add both types of lights, and the 'Controlled Via' field will show you what interface is being used.</p><br />
<p>Back to our example: Plug one of your gc100's into the network, and click the 'add gc100' button on the interface page. gc100's are treated special because they are IP-based, but their network configuration is a bit different and does not allow them to be plug-and-play. Once you got the message that it was found and configured, click on the Interfaces page again--now you'll see it there. Maybe give it a descriptive name so you can remember which is which. Now plug in the 2nd gc100, and repeat.<br />
Next choose 'Add Devices' and add the CM11A. Like all RS232 devices, it is not plug and play, you must add it manually. Repeat for the alarm panel. In both cases, the Controlled Via devices is the Core, since that's where the software drivers will be run. But, when you go to choose the port, it only shows the Core's internal serial ports, and you want to plug it into one of the ports on the gc100. So, click 'Wizard', 'Restart' and 'quick reload router'. That causes the DCE Router to reload the list of devices in the house so it sees the new gc100's you added, and adds the ports. Refresh the Interfaces page, and now you can choose the gc100 ports for the CM11A and alarm panel.</p><p>Next, add your tv's and stereo's on the [[AV Devices]] and indicate how they are connected (which AV inputs). If your model is not in the database you will need to add it. If the I/R codes for your device aren't listed or don't work, you will click the A/V properties button and either [[Learning/typing my own code|learn them]] using the gc100's learner (plug it into serial port 1 and click 'learn'), or [[Learning/typing my own code|copy+paste the I/R codes in pronto format]] from a source like www.remotecentral.com. Your devices and I/R codes will automatically be sent to Pluto and added to the master database for other users unless you uncheck the box. In the 'controlled via' chose whichever one of the gc100's has the infrared emitter attached for that device. Turn your Squeeze Boxes on, set the network to DHCP, and plug them in. Pluto will automatically recognize them and configure them. You will see a confirmation message and be asked to pick the room they're in. Refresh the A/V page to see the Squeeze Boxes and indicate how you connect them to your stereo system.</p><br />
<br />
<p>On the [[Media Directors]] and [[Orbiters]] page, be sure your settings are correct. Then on the [[Lights]] and [[Climate]] pages, add all your X10 lights/thermostats. The 'Controlled Via' is the cm11A device. On the security page, add all your motion detectors, smoke alarms, etc. The 'Controlled Via' is the alarm panel. <br />
On the [[Floorplans]], drag and drop your devices on the maps you upload. You'll need to do a 'regen orbiter' followed by a 'quick reload router' before you can use the floorplans.</p><br />
<br />
<p>Now let's test the devices. Do another 'quick reload router' so DCERouter sees these new devices. Go back to a device, like a light, click 'ADV' to go to the advanced page, or go there manually by choosing [[Devices]] from the menu. Click 'Send command to device', and choose a command. If it doesn't respond, go to 'Advanced', 'Logs' and check the logs for the interface, the CM11A in this case.</p><br />
<br />
===Scenarios, Events & Security===<br />
<br />
<p>In the [[Scenarios]] page, add the scenarios, or buttons, you want for each room. Like a Lighting scenario in the Bedroom called 'Go to sleep' which dims the lights, or a security scenario in the living to view a camera. When you do a 'quick reload router', DCERouter will automatically add Media Scenarios for each room for whatever media devices are in there. But your new scenarios are not visible on the Orbiter until you regenerate--see the note below in 'Using Pluto with an Orbiter'. Next add [[Events]], in other words, when something happens (a motion detector is tripped, the sun sets, etc.) you want Pluto to do this (turn on a light). Also set security options, like how you want to be notified when something happens in the house. Each page has context sensitive help to explain everything. They will take effect next time you reboot or 'quick reload router'.</p><br />
<br />
===Configuring Myth TV===<br />
<br />
This section has been moved to [[Setting up MythTV]].<br />
<br />
===Upload Your Media===<br />
<br />
<p>There will also be Microsoft Windows compatible network shares on the Core or Hybrid (uses Samba) . There is a "public" share for putting all files that the whole family can share--movies, music, etc. And there is a private share for each family member. To access these network shares in Windows, choose Start, Run, and type \\ plus the IP address of the Core or hybrid. <br />
<br />
For example: \\192.168.80.1 Note that if you add new family members, their network share will not be available until after you reboot the Core/Hybrid. Once you copy your media into the appropriate folder, you can go into the Pluto Admin site, choose "Files &amp; Media" and "Media Files Sync" to be sure your media is in the database, add attributes (artist, actor, etc.), and choose cover art.</p><br />
<br />
==Using Pluto==<br />
<br />
This secion has been moved to [[Using Pluto]]. In 10 minutes you'll be up to speed and using all of Pluto's features.<br />
<br />
<p><b>Using Pluto with an Orbiter</b></p><br />
<p>Orbiter is just our way of saying remote control. All the Media Directors run an on-screen Orbiter, like the one below. Choose options on the on-screen orbiter with a keyboard/mouse attached to the media director, or with an infrared remote control. The Orbiter software runs on Linux, Windows and Windows CE, and can also be run on webpads and PDA's.<br />
Either way, it works exactly the same.</p><p>Below is the main menu. In the lower right are the [[Who Am I, Where Am I|'who' and 'where']] buttons. This indicates what room you are in, or want to control, and which family member is using the Orbiter. <br />
<br />
Touch either button if this isn't correct. Even if you are using an on-screen orbiter on the media director in the Living Room, for example, you can still change the location to the Bedroom. That means you would be using the Media Director in the Living Room as a remote control for the devices in the bedroom. Normally you don't change the location for an on-screen orbiter, since that device stays in a fixed place, but you do when you have a wireless web pad or pda you carry around.</p><br />
<br />
<p>The icons on the left all lead to a [[maps]], or floorplan, of your house showing your lighting, media, climate, telecom and security devices. Next to each of the floorplan icons are the scenarios for that category and the given room. In the scenarios section of the Pluto Admin web site you create the scenarios for each room. You can have a lighting scenario called 'entertaining guests' that sets some lights, plays some background music, unlocks the door, and so on.<br />
<br><br />
[[Image:Main-menu.jpg|200px]]<br />
<br />
[[Image:Litscen.jpg|200px]]<br><br />
<br />
<p><b>NOTE:</b><br />
Many orbiters have relatively slow processors (like PDA's and phones) and may be running on slow wi-fi connections. So, the orbiters do not retrieve the large, full-size graphics, scaling them, drawing the text, and rendering everything on the fly. <br />
<br />
Rather all the graphics on your Orbiter are pre-scaled and pre-rendered by OrbiterGen. This means that if you add new scenarios or devices, or change floorplans or skins, you won't see them immediately on the Orbiter. You must go to the 'Advanced<br />
Options' page by clicking the Pluto logo on the main menu, and choose 'Regenerate this Orbiter'. You'll be asked to wait about 60 seconds or so while the renderer creates new graphics, and then the Orbiter willreload.</p><br />
<br />
<p><b>Using your system with a Mobile Orbiter</b></p><br />
<p>Unless you turned off the "Auto Detect new Bluetooth Phones" option for the Media Director, compatible Bluetooth Mobile phones will automatically be detected when they are within range of any Media Director if they have Bluetooth turned on. A message will appear on all the Orbiters asking if it's a phone, and if so, to whom it belongs. Be sure you add your family members to the Pluto Admin web site before doing this. Also, you may need to turn on the TV to see the message on the on-screen orbiter.</p><br />
<br />
<p>If you choose to install the software, the phone will beep. Just hit 'yes' to accept the software, and accept the default prompts.</p><p>The mobile orbiter works pretty much like a regular orbiter. The difference is that you don't usually need to worry about the "who" and "where" button. The "who" is determined when you chose to install the software. That family member is assumed to always be the user. And the "where" is automatic-whenever you come within range of a media director it will automatically switch to the correct location. You can press the button under the location if you want to control a location other than the one you are in.</p><br />
<br />
<p>Since the display is smaller, rather than showing all the scenarios on the main menu, you must first choose the category, like lighting, and then choose the scenario from the sub menu that appears. You can also hold the category to toggle 'follow-me' mode, indicated with a red F. So, if you hold down the 2 button, a red F appears for media. Now as you move around the house your media will follow you. All 5 categories have follow-me. <a<br />
href="http://plutohome.com/index.php?section=how_pluto_works">Screen shots of the Mobile Orbiter</a> / [[User's manual]]</p><br />
<br />
==Troubleshooting==<br />
<br />
[[Testing_and_troubleshooting_devices]]<br />
<br />
<p>[[Development status for all modules|What works and what doesn't?]]</p><br />
<br />
<p>If you don't know Linux at all, you can go into the Pluto Admin website and choose [[Outside Access]], and check the box to get outside assistance from Pluto. You will pick a password you will give one of our tech support staff. When you do, your system will make a secure, encrypted connection back to our support staff giving us temporary access to your system. The connection is closed as soon as you uncheck the box. Without checking that box, nobody at Pluto will have any access to your system.</p><br />
<br />
<p>This troubleshooting guide assumes some basic knowledge of Linux. In Pluto, everything is a device. In the Pluto Admin web site, you can choose [[Devices]], to see a list of all the devices in your installation. We recommend you don't make changes here - you can break things! The top level device is usually a computer, either the core or a hybrid or an orbiter. All the logs for the devices on that computer are stored in /var/log/pluto. You can ssh in to the core using the root password you chose, and from there, you can ssh to all the media directors-shared keys were automatically setup.</p><br />
<p>All current activity is logged in the file that ends in ".newlog". After a device crashes, its logs are moved into<br />
the ".log" directory. At bootup, all logs are archived into /var/log/pluto/archives.</p><br />
<br />
<p>All DCE devices are running in separate screen sessions. Type "screen -ls" to see all active screen sessions,<br />
and "screen -r PID" where PID is the id you saw in the -ls list to attach to the screen session. There is not much for you to do or see though since all the output on stderr and stdout is going into the logs. DCERouter is running the same way on your core or hybrid.</p><br />
<br />
<p>At bootup, all the scripts listed in the Pluto Admin website under [[Boot Sequence]] are run. If any programs crash, a core dump file is put in /usr/pluto/coredump. At each reboot, any core dumps are archived with the log files in /var/log/pluto/archives. A database dump/configuration snapshot are also put in each archive. Archives are deleted after 5 days.</p><br />
<br />
<p>If you're a programmer, you can also check out our [[Programmer's Guide]]. If you want to learn about writing DCE Devices, see the [[DCE]].<br />
</p><br />
<br />
<br />
''Note:''<br />
<p>We had to leave some basic features out of the free version due to licensing issues. See [http://www.yttron.as.ro http://www.yttron.as.ro] for a list. If you purchase a pre-built Pluto system, some or all of these technologies may be licensed and the license fee built into the purchase price. Before contacting Pluto support to ask why something doesn't work, please refer to that site so you know what features were left out intentionally. Note that Pluto does not encourage, endorse or support users adding 3rd party modules, nor did Pluto develop those modules. If you choose to add 3rd party modules we suggest you first confirm they are legal in your area.</p></div>Razvanghttp://wiki.linuxmce.org/index.php?title=Installing_codecs_and_decryption&diff=3046Installing codecs and decryption2007-03-14T00:18:03Z<p>Razvang: </p>
<hr />
<div>==Playing DVDs==<br />
Most commercial DVDs are encrypted with CSS (the Content Scrambling System), which attempts to restrict the software that can play a DVD. <br />
By installing the ''libdvdcss2'' package you can play encrypted DVDs. To get it installed you need to fallow this steps:<br />
*Open a terminal. Select Applications->Accesories->Terminal if you are in a Gnome session or ALT+F1 (ALT+F11 to go back) if you are using the LinuxMCE interface.<br />
*Type this set of commands:<br />
sudo apt-get install -y libdvdread3<br />
sudo /usr/share/doc/libdvdread3/install-css.sh<br />
*Insert a Video DVD in the LinuxMCE drive to test it ;)<br />
<br />
==Playing WMV, WMA, and RealPlayer formats==<br />
Support for WMV, RealMedia and other formats has been bundled into the w32codecs package. This package is not available from the Ubuntu repositories or supported by Ubuntu, due to licensing and legal restrictions. You can download the package from debian-multimedia.org:<br />
<br />
wget -c http://www.debian-multimedia.org/pool/main/w/w32codecs/w32codecs_20061022-0.0_i386.deb<br />
sudo dpkg -i w32codecs_20061022-0.0_i386.deb<br />
*Note: The w32codecs package from the Debian repositories have been tested and work with Ubuntu systems however not all Debian packages will work correctly with Ubuntu, so for your safety do not add Debian repositories to your /etc/apt/sources.list<br />
*WMV files encoded with DRM (Digital Rights Management) cannot be played with this package.<br />
*If you are experiencing choppy audio when playing WMV files, try [[http://ubuntuforums.org/showpost.php?p=136306&postcount=2 the fix described here]].<br />
*If you still cannot play WMV files after installing w32codecs, try [[http://ubuntuforums.org/showthread.php?p=1649012 the method suggested here]].</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Installing_codecs_and_decryption&diff=3044Installing codecs and decryption2007-03-14T00:07:17Z<p>Razvang: </p>
<hr />
<div>==Playing DVDs==<br />
Most commercial DVDs are encrypted with CSS (the Content Scrambling System), which attempts to restrict the software that can play a DVD. <br />
By installing the ''libdvdcss2'' package you can play encrypted DVDs. To get it installed you need to fallow this steps:<br />
*Open a terminal. Select Applications->Accesories->Terminal if you are in a Gnome session or ALT+F1 (ALT+F11 to go back) if you are using the LinuxMCE interface.<br />
*Type this set of commands:<br />
sudo apt-get install -y libdvdread3<br />
sudo /usr/share/doc/libdvdread3/install-css.sh<br />
*Insert a Video DVD in the LinuxMCE drive to test it ;)<br />
<br />
==</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Installation_Guide&diff=3041Installation Guide2007-03-13T23:55:26Z<p>Razvang: </p>
<hr />
<div>Steps for installing Linux MCE on an Ubuntu 6.10 system (only Ubuntu 6.10 is support for now):<br />
<br />
'''1.''' Take an Ubuntu install already configured with Internet connection (Configure your network card and DNS). If you don't have an Ubuntu system already installed please follow these generic steps:<br />
<br />
*Take an [http://www.ubuntu.com/products/GetUbuntu/download?action=show&redirect=download Ubuntu Live Cd] and boot from it.<br />
*Choose 'Start or install Ubuntu'<br />
*When Ubuntu's desktop appears, double-click on 'Install'<br />
*A short wizard will start and guide you; Select the language and press 'forward'<br />
*Choose you timezone and press 'forward'<br />
*Select the keyboard layout<br />
*Choose desktop name, an user name and a password<br />
*Select the partitioning options for your disk: erase the entire disk or just manually edit the options.<br />
*Ready to install.<br />
*Reboot the system and remove the Live CD<br />
*(Optional) Ubuntu and Linux MCE won't install by default software needed to play DVD or some other restricted media formats that might be illegal in some countries. You can follow the [[Restricted Software Installation Guide]] if the restrictions don't apply to your country.<br />
*(Optional) Before installing LinuxMCE is recommended to apply all the Ubuntu updates that are available. If you don't do this, the Linux MCE installer will do this for you at the end of the installation.<br/><br />
<br />
<br />
<br />
'''2.''' Go to [http://www.linuxmce.com www.linuxmce.com] and select 'Download Instructions' and 'Installer for Ubuntu 6.10' to download the Linux MCE Installer on your machine. Or just use this direct link [http://www.linuxmce.com/download.php click here]<br />
<br />
[[Image:DownloadInstaller.jpg|400px]]<br />
<br />
<br />
'''3.''' Save the mce-installer on your Ubuntu desktop. A pop-up message will appear and there you must check "Save to Disk" and then click "ok"<br />
<br />
[[Image:SaveInstaller.jpg|400px]]<br />
<br />
<br />
'''4.''' Then double-click on your "Install Linux MCE" icon from Ubuntu`s desktop to start the installation process. A window will appear asking to choose if you want a dedicated core or a hybrid ([http://linuxmce.com/wiki/index.php/Getting_Started#A_Dedicated_Core click here]to find out the difference between a core and a hybrid), after that you must click on "Forward" button. <br />
<br />
[[Image:CoreOrHybrid.jpg|400px]]<br />
<br />
<br />
'''5.''' The next screen will ask you want to keep your current network configuration or if you want to set your network options manually; then press "Forward".<br />
<br />
[[Image:ConfirNetworkSettings.jpg|400px]]<br />
<br />
<br />
'''6.''' In the next step you must select the method you want to choose to install Linux MCE and you have 3 options: <br />
- Download the needed packages from the internet. Just downloads the packages from linuxmce.com website.<br />
- Download and use an ISO file from one of LinuxMCE mirrors. Instead of downloading the packages one by one just, it downloads an archive which contains all packages. <br />
- Use the Linux MCE CDROM that I already have in my drive. This assumes you have already [[Installation_Guide|downloaded LinuxMCE as an ISO image]] and burned it to a cd. This is the recommended method so that if you install Linux MCE again, the installer won't need to download everything again.<br />
<br />
After you have chosen your option press 'Forward'.<br />
<br />
[[Image:InstallOptions.jpg|400px]]<br />
<br />
<br />
'''7.''' In the next step you have 2 options :<br />
*First it asks you if you want to Run a DHCP Server or not. LinuxMCE must be the DHCP server for your home in order to provide plug-and-play detection of network devices like IP Cameras and VOIP phones, and to provide network boot images to any other pc's in the home you want to use as media stations.<br />
*The other option asks if you want to keep the default Internal Network address or if you want to change it.<br />
<br />
After that you must press 'Forward'.<br />
<br />
[[Image:DhcpSettings.jpg|400px]]<br />
<br />
<br />
'''8.''' In the next window you can see how the Linux MCE system is installing<br />
<br />
[[Image:StartInstall.jpg|400px]]<br />
<br />
<br />
'''9.''' In the final step you will see a message saying "Installation was finished , please reboot"<br />
<br />
[[Image:FinalStep.jpg|400px]]<br />
<br />
After reboot you have the Linux MCE software installed.<br />
<br />
Next follow the [http://linuxmce.com/wiki/index.php?title=QuickStart_Guide Quick Start Guide] to tell LinuxMCE about how you want to use it.</div>Razvanghttp://wiki.linuxmce.org/index.php?title=QuickStart_Guide&diff=2977QuickStart Guide2007-03-13T03:26:45Z<p>Razvang: </p>
<hr />
<div> <br />
Steps for installing Linux MCE on an Ubuntu system:<br />
<br />
'''1.''' Take an Ubuntu install already configured with Internet connection (Configure your network card and DNS). If you don't have an Ubuntu system already installed please follow this generic steps:<br />
<br />
- Take an Ubuntu Live Cd and boot from it.<br />
- Choose 'Start or install Ubuntu'<br />
- Wait the cd to boot; from Desktop double-click on 'Install'<br />
- A short wizard will start and guide you; Select the language and press 'forward'<br />
- Choose you timezone and press 'forward'<br />
- Select the keyboard layout<br />
- Choose desktop name, an user name and a password<br />
- Select the partitioning options for your disk: erase the entire disk or just manually edit the options.<br />
- Ready to install.<br />
- Reboot the system and remove the Live CD<br />
<br />
<br />
'''2.''' Go to [http://www.linuxmce.com www.linuxmce.com] and press 'Download' to download the Linux MCE Installer on your machine. Or just use this direct link [http://www.linuxmce.com/download.php click here]<br />
<br />
[[Image:DownloadInstaller.jpg|400px]]<br />
<br />
<br />
'''3.''' Save the mce-installer on your Ubuntu desktop. A pop-up message will appear and there you must check "Save to Disk" and then click "ok"<br />
<br />
[[Image:SaveInstaller.jpg|400px]]<br />
<br />
<br />
'''4.''' Then double-click on your "Install Linux MCE" icon from ubuntu`s desktop to start the installation process. A window will appear asking to choose if you want a dedicated core or a hybrid ([http://linuxmce.com/wiki/index.php/Getting_Started#A_Dedicated_Core click here]to find out the difference between a core and a hybrid), after that you must click on "Forward" button. <br />
<br />
[[Image:CoreOrHybrid.jpg|400px]]<br />
<br />
<br />
'''5.''' The next screen will ask you want to keep your current network configuration or if you want to set your network options manually; then press "Forward".<br />
<br />
[[Image:ConfirNetworkSettings.jpg|400px]]<br />
<br />
<br />
'''6.''' In the next step you must select the method you want to choose to install Linux MCE and you have 3 options: <br />
- Download the needed packages from the internet. Just downloads the packages from linuxmce.com website.<br />
- Download and use an ISO file from one of LinuxMCE mirrors. Instead of downloading the packages one by one just downloads an archive which contains all packages. <br />
- Use the Linux MCE CDROM that I allready have in my drive. Download first the ISO file on your hard drive, burn it on a disc and insert the disc in drive.<br />
<br />
After you have chosen your option press 'Forward'.<br />
<br />
[[Image:InstallOptions.jpg|400px]]<br />
<br />
<br />
'''7.''' In the next step you have 2 options :<br />
- First asks you if you want to Run a DHCP Server or not. A dhcp server is needed for the internal network and allows you to add devices like: media directors, network players, external hard drives, etc.<br />
- The other option asks if you want to keep the default Internal Network address or if you want to change it.<br />
<br />
After that you must press 'Forward'.<br />
<br />
[[Image:DhcpSettings.jpg|400px]]<br />
<br />
<br />
'''8.''' In the next window you can see how the Linux MCE system is installing<br />
<br />
[[Image:StartInstall.jpg|400px]]<br />
<br />
<br />
'''9.''' In the final step you will see a message saying "Installation was finished , please reboot"<br />
<br />
[[Image:FinalStep.jpg|400px]]<br />
<br />
<br />
Now, you have the Linux MCE software installed. Start Linux MCE Center which starts another piece called AVWizard.<br />
These are the steps:<br />
<table><br />
<tr><br />
<td>[[Image:AVWizardStep1.jpg|200px]]</td><br />
<td>[[Image:AVWizardStep11.jpg|200px]]</td><br />
<td>[[Image:AVWizardStep2.jpg|200px]]</td><br />
<td>[[Image:AVWizardStep21.jpg|200px]]</td><br />
</tr><br />
<tr><br />
<td>[[Image:AVWizardStep3.jpg|200px]]</td><br />
<td>[[Image:AVWizardStep4.jpg|200px]]</td><br />
<td>[[Image:AVWizardStep5.jpg|200px]]</td><br />
<td>[[Image:AVWizardStep6.jpg|200px]]</td><br />
</tr><br />
<tr><br />
<td>[[Image:AVWizardStep7.jpg|200px]]</td><br />
<td>[[Image:AVWizardStep8.jpg|200px]]</td><br />
<td>[[Image:AVWizardStep9.jpg|200px]]</td><br />
</tr><br />
</table><br />
<br />
The final step asks for a confirmation of these steps, if you press 'I Agree' the installation continues and you'll get the Media Center started.<br />
<br />
At this time you don't have any rooms or users added in data base. Using the UI go to Advanced Options screen and choose 'Setup wizard' which will guide you through whole house and media setup.</div>Razvanghttp://wiki.linuxmce.org/index.php?title=Screenshots&diff=2976Screenshots2007-03-13T03:26:23Z<p>Razvang: </p>
<hr />
<div>'''Screenshots: Using the Linux MCE'''<br />
<br />
<br />
''Main menu''<br />
<br />
<table><br />
<tr><br />
<td>UI1 or Basic UI</td><br />
<td>UI2 with medium settings</td><br />
<td>UI2 with alpha blending / transparency</td><br />
</tr><br />
<tr><br />
<td>[[Image:MainMenuUI1.jpg|300px]]</td><br />
<td>[[Image:MainMenu2.jpg|300px]]</td><br />
<td>[[Image:MainMenu2.jpg|300px]]</td><br />
</tr><br />
</table><br />
<br />
<br />
''File Browser''<br />
<br />
<table><br />
<tr><br />
<td>UI1 or Basic UI</td><br />
<td>UI2 with medium settings</td><br />
<td>UI2 with alpha blending / transparency</td><br />
</tr><br />
<tr><br />
<td>[[Image:FileBrowserUI1.jpg|300px]]</td><br />
<td>[[Image:MainMenu2.jpg|300px]]</td><br />
<td>[[Image:MainMenu2.jpg|300px]]</td><br />
</table><br />
<br />
<br />
''DVD Remote''<br />
<br />
<table><br />
<tr><br />
<td>UI1 or Basic UI</td><br />
<td>UI2 with medium settings</td><br />
<td>UI2 with alpha blending / transparency</td><br />
</tr><br />
<tr><br />
<td>[[Image:DVDRemoteUI1.jpg|300px]]</td><br />
<td>[[Image:MainMenu2.jpg|300px]]</td><br />
<td>[[Image:MainMenu2.jpg|300px]]</td><br />
</table><br />
<br />
<br />
''Dial number''<br />
<br />
<table><br />
<tr><br />
<td>UI1 or Basic UI</td><br />
<td>UI2 with medium settings</td><br />
<td>UI2 with alpha blending / transparency</td><br />
</tr><br />
<tr><br />
<td>[[Image:DialNumberUI1.jpg|300px]]</td><br />
<td>[[Image:MainMenu2.jpg|300px]]</td><br />
<td>[[Image:MainMenu2.jpg|300px]]</td><br />
</table><br />
<br />
<br />
''Security panel''<br />
<br />
<table><br />
<tr><br />
<td>UI1 or Basic UI</td><br />
<td>UI2 with medium settings</td><br />
<td>UI2 with alpha blending / transparency</td><br />
</tr><br />
<tr><br />
<td>[[Image:SecurityPanelUI1.jpg|300px]]</td><br />
<td>[[Image:MainMenu2.jpg|300px]]</td><br />
<td>[[Image:MainMenu2.jpg|300px]]</td><br />
</table></div>Razvanghttp://wiki.linuxmce.org/index.php?title=Contacts&diff=2975Contacts2007-03-13T02:35:51Z<p>Razvang: </p>
<hr />
<div>LinuxMCE is a hot new open source project. It's stable, practical and usable, and really cool. Just check out the [[Video_Screenshots|Demo Videos and Screen Shots]] to see for yourself. I'm looking for developers and maintainers to '''[[Contribute|join the team]]'''. New LinuxMCE team members, please add your name, contact info, and a brief bio or description of what you're working on. Thanks!<br />
<br />
----<br />
'''Paul Webber''' -- contact: webpaul1 -at- gmail (.com)<br><br />
Responsibilities: Installer, Ubuntu packaging, build system, linuxmce.com site<br><br />
I launched LinuxMCE on March 07. [[History|History of LinuxMCE]]<br />
----</div>Razvang