<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://wiki.linuxmce.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Alx</id>
	<title>LinuxMCE - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://wiki.linuxmce.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Alx"/>
	<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php/Special:Contributions/Alx"/>
	<updated>2026-05-11T05:33:10Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.44.0</generator>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Create_RAID_in_LMCE&amp;diff=3967</id>
		<title>Create RAID in LMCE</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Create_RAID_in_LMCE&amp;diff=3967"/>
		<updated>2007-06-05T08:31:23Z</updated>

		<summary type="html">&lt;p&gt;Alx: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;p&amp;gt;&amp;lt;h1&amp;gt;Introduction&amp;lt;/h1&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;RAID (&amp;lt;b&amp;gt;R&amp;lt;/b&amp;gt;edundant &amp;lt;b&amp;gt;A&amp;lt;/b&amp;gt;rray of &amp;lt;b&amp;gt;I&amp;lt;/b&amp;gt;ndependent &amp;lt;b&amp;gt;D&amp;lt;/b&amp;gt;rives) refers to a data storage scheme which has as a benefit increase of the data integrity, fault-tolerance, throughput and/or capacity&lt;br /&gt;
There are 3 standard RAID levels which can be used in LMCE, to define RAIDS:&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;RAID 0&amp;lt;/b&amp;gt;: Striped Set (2 disk minimum) without parity: provides improved performance and additional storage but no fault tolerance from disk errors or disk failure. Any disk failure destroys the array, which becomes more likely with more disks in the array&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;RAID 1&amp;lt;/b&amp;gt;: Mirrored Set (2 disks minimum) without parity: provides fault tolerance from disk errors and single disk failure. Increased read performance occurs when using a multi-threaded operating system that supports split seeks, very small performance reduction when writing. A drive has its data duplicated on another different drive. If either drive fails, the other continues to function as a single drive until the failed drive is replaced. Conceptually simple, RAID 1 is popular for those who require fault tolerance and don&#039;t need top-notch read performance.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;RAID 5&amp;lt;/b&amp;gt;: Striped Set (3 disk minimum) with Distributed Parity: Distributed parity requires all but one drive to be present to operate; drive failure requires replacement, but the array is not destroyed by a single drive failure. Upon drive failure, any subsequent reads can be calculated from the distributed parity such that the drive failure is masked from the end user. The array will have data loss in the event of a second drive failure and is vulnerable until the data that was on the failed drive is rebuilt onto a replacement drive&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;h1&amp;gt;Creating RAID&amp;lt;/h1&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Step 1:&amp;lt;/b&amp;gt; Go to LMCE&#039;s admin web page at Advanced-&amp;gt;Configuration-&amp;gt;RAID section. You have to specify the computer that should hold the RAID in the &amp;lt;i&amp;gt;Parent&amp;lt;/i&amp;gt; section. Give a &amp;lt;i&amp;gt;Description&amp;lt;/i&amp;gt; to the Raid you’re creating. Choose the type of RAID, according to what you need to do.&lt;br /&gt;
Check the &amp;lt;i&amp;gt;Use automatically&amp;lt;/i&amp;gt; box, if you want your data to be stored automatically using this RAID. Choose what kind of data structure you want for this RAID. Then click on the &amp;lt;i&amp;gt;Add&amp;lt;/i&amp;gt; button to save your settings.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Step 2:&amp;lt;/b&amp;gt; Choose the disk drives you want to include in the RAID, by selecting the available ones from the drive list. The list contains only the disks that there are not used. Also you have the option to add spare disks.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Step 3:&amp;lt;/b&amp;gt;When you have finished adding your disks, press the ‘Create RAID array’ button, to re-write your data in the desired pattern. You will see your RAID created in the list and you will be able to access the advanced configuration page, to add new drives, or to delete it.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Note: &amp;lt;/b&amp;gt;This is a totally software RAID, you don’t need to activate the RAID in your BIOS.&amp;lt;/p&amp;gt;&lt;/div&gt;</summary>
		<author><name>Alx</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Create_RAID_in_LMCE&amp;diff=3966</id>
		<title>Create RAID in LMCE</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Create_RAID_in_LMCE&amp;diff=3966"/>
		<updated>2007-06-05T08:30:48Z</updated>

		<summary type="html">&lt;p&gt;Alx: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;p&amp;gt;&amp;lt;h1&amp;gt;Introduction&amp;lt;/h1&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;RAID (&amp;lt;b&amp;gt;R&amp;lt;/b&amp;gt;edundant &amp;lt;b&amp;gt;A&amp;lt;/b&amp;gt;rray of &amp;lt;b&amp;gt;I&amp;lt;/b&amp;gt;ndependent &amp;lt;b&amp;gt;D&amp;lt;/b&amp;gt;rives) refers to a data storage scheme which has as a benefit increase of the data integrity, fault-tolerance, throughput and/or capacity&lt;br /&gt;
There are 3 standard RAID levels which can be used in LMCE, to define RAIDS:&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;RAID 0&amp;lt;/b&amp;gt;: Striped Set (2 disk minimum) without parity: provides improved performance and additional storage but no fault tolerance from disk errors or disk failure. Any disk failure destroys the array, which becomes more likely with more disks in the array&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;RAID 1&amp;lt;/b&amp;gt;: Mirrored Set (2 disks minimum) without parity: provides fault tolerance from disk errors and single disk failure. Increased read performance occurs when using a multi-threaded operating system that supports split seeks, very small performance reduction when writing. A drive has its data duplicated on another different drive. If either drive fails, the other continues to function as a single drive until the failed drive is replaced. Conceptually simple, RAID 1 is popular for those who require fault tolerance and don&#039;t need top-notch read performance.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;RAID 5&amp;lt;/b&amp;gt;: Striped Set (3 disk minimum) with Distributed Parity: Distributed parity requires all but one drive to be present to operate; drive failure requires replacement, but the array is not destroyed by a single drive failure. Upon drive failure, any subsequent reads can be calculated from the distributed parity such that the drive failure is masked from the end user. The array will have data loss in the event of a second drive failure and is vulnerable until the data that was on the failed drive is rebuilt onto a replacement drive&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;h1&amp;gt;Creating RAID&amp;lt;/h1&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Step 1:&amp;lt;/b&amp;gt; Go to LMCE&#039;s admin web page at Advanced-&amp;gt;Configuration-&amp;gt;RAID section. You have to specify the computer that should hold the RAID in the &amp;lt;i&amp;gt;Parent&amp;lt;/i&amp;gt; section. Give a &amp;lt;i&amp;gt;Description&amp;lt;/i&amp;gt; to the Raid you’re creating. Choose the type of RAID, according to what you need to do.&lt;br /&gt;
Check the &amp;lt;i&amp;gt;Use automatically&amp;lt;/i&amp;gt; box, if you want your data to be stored automatically using this RAID. Choose what kind of data structure you want for this RAID. Then click on the &amp;lt;i&amp;gt;Add&amp;lt;/i&amp;gt; button to save your settings.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Step 2:&amp;lt;/b&amp;gt; Choose the disk drives you want to include in the RAID, by selecting the available ones from the drive list. The list contains only the disks that there are not used. Also you have the option to add spare disks.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Step 3:&amp;lt;/b&amp;gt;When you have finished adding your disks, press the ‘Create RAID array’ button, to re-write your data in the desired pattern. You will see your RAID created in the list and you will be able to access the advanced configuration page, to add new drives, or to delete it.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Note: &amp;lt;/b&amp;gt;This is a totally software RAID, you don’t need to activate the RAID in your bios.&amp;lt;/p&amp;gt;&lt;/div&gt;</summary>
		<author><name>Alx</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Create_RAID_in_LMCE&amp;diff=3965</id>
		<title>Create RAID in LMCE</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Create_RAID_in_LMCE&amp;diff=3965"/>
		<updated>2007-06-05T08:25:52Z</updated>

		<summary type="html">&lt;p&gt;Alx: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;p&amp;gt;&amp;lt;h1&amp;gt;Introduction&amp;lt;/h1&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;RAID (&amp;lt;b&amp;gt;R&amp;lt;/b&amp;gt;edundant &amp;lt;b&amp;gt;A&amp;lt;/b&amp;gt;rray of &amp;lt;b&amp;gt;I&amp;lt;/b&amp;gt;ndependent &amp;lt;b&amp;gt;D&amp;lt;/b&amp;gt;rives) refers to a data storage scheme which has as a benefit increase of the data integrity, fault-tolerance, throughput and/or capacity&lt;br /&gt;
There are 3 standard RAID levels which can be used in LMCE, to define RAIDS:&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;RAID 0&amp;lt;/b&amp;gt;: Striped Set (2 disk minimum) without parity: provides improved performance and additional storage but no fault tolerance from disk errors or disk failure. Any disk failure destroys the array, which becomes more likely with more disks in the array&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;RAID 1&amp;lt;/b&amp;gt;: Mirrored Set (2 disks minimum) without parity: provides fault tolerance from disk errors and single disk failure. Increased read performance occurs when using a multi-threaded operating system that supports split seeks, very small performance reduction when writing. A drive has its data duplicated on another different drive. If either drive fails, the other continues to function as a single drive until the failed drive is replaced. Conceptually simple, RAID 1 is popular for those who require fault tolerance and don&#039;t need top-notch read performance.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;RAID 5&amp;lt;/b&amp;gt;: Striped Set (3 disk minimum) with Distributed Parity: Distributed parity requires all but one drive to be present to operate; drive failure requires replacement, but the array is not destroyed by a single drive failure. Upon drive failure, any subsequent reads can be calculated from the distributed parity such that the drive failure is masked from the end user. The array will have data loss in the event of a second drive failure and is vulnerable until the data that was on the failed drive is rebuilt onto a replacement drive&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;h1&amp;gt;Creating RAID&amp;lt;/h1&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Step 1:&amp;lt;/b&amp;gt; Go to LMCE&#039;s admin web page at Advanced-&amp;gt;Configuration-&amp;gt;RAID section. You have to specify the computer that should hold the RAID in the &amp;lt;i&amp;gt;Parent&amp;lt;/i&amp;gt; section. Give a &amp;lt;i&amp;gt;Description&amp;lt;/i&amp;gt; to the Raid you’re creating. Choose the type of RAID, according to what you need to do.&lt;br /&gt;
Check the &amp;lt;i&amp;gt;Use automatically&amp;lt;/i&amp;gt; box, if you want your data to be stored automatically using this RAID. Choose what kind of data structure you want for this RAID. Then click on the &amp;lt;i&amp;gt;Add&amp;lt;/i&amp;gt; button to save your settings.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Step 2:&amp;lt;/b&amp;gt;&amp;lt;/p&amp;gt;&lt;/div&gt;</summary>
		<author><name>Alx</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3841</id>
		<title>Building From Source 1.1</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3841"/>
		<updated>2007-04-25T07:16:18Z</updated>

		<summary type="html">&lt;p&gt;Alx: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before You Begin==&lt;br /&gt;
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&#039;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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Build Scripts ==&lt;br /&gt;
The build scripts are in sourceforge svn so to get them you will need subversion installed.&lt;br /&gt;
 sudo apt-get install subversion&lt;br /&gt;
 cd /root&lt;br /&gt;
 svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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&#039;s a short description:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;Install_Build_Needed_Packages&#039;&#039;: 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. This will take about 5 minutes.&lt;br /&gt;
*&#039;&#039;Create Diskless Archive&#039;&#039;: Runs a debootstrap to create a base filesystem for Diskless Media Directors. It&#039;s needed later when it&#039;ll be packed in a deb packages. You also don&#039;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.&lt;br /&gt;
*&#039;&#039;Import_Skins&#039;&#039;: Since linuxmce uses a lot of pngs for the all sort of skins, you won&#039;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.&lt;br /&gt;
*&#039;&#039;Checkout_Svn&#039;&#039;: Will do a svn checkout on sourceforge to get all the needed sources&lt;br /&gt;
*&#039;&#039;Build_Replacements&#039;&#039;: LinuxMCE needs some 3rd party packages that are not part of ubuntu distribution. This function will build / get them for you.&lt;br /&gt;
*&#039;&#039;Build_MakeRelease_Binary&#039;&#039;: 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.&lt;br /&gt;
*&#039;&#039;Import_Build_Database&#039;&#039;: Imports a fresh copy of the pluto databases needed at build time.&lt;br /&gt;
*&#039;&#039;Create_Fake_Windows_Binaries&#039;&#039;: Orbiter and other aplications don&#039;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&#039;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&#039;t fail to run.&lt;br /&gt;
*&#039;&#039;Build_Pluto_Stuff&#039;&#039;: Uses MakeRelase to compile the sources and build packages out of them.&lt;br /&gt;
*&#039;&#039;Create_Local_Repository&#039;&#039;: Optional you can create a local repository so that you can easily test your debs. By default, the local repository will be put in /var/www&lt;br /&gt;
*&#039;&#039;Create_ISO&#039;&#039;: Is an optional step and creates an iso with all the needed packages for a linuxmce instalation. For this, get-packages.sh script is called. By defaul the iso will be located in /var/wwww&lt;br /&gt;
&lt;br /&gt;
== Source Code Location ==&lt;br /&gt;
&lt;br /&gt;
Our source code is located on sourceforge and you can get it by svn from : https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/&lt;br /&gt;
&lt;br /&gt;
The png used for the skins are located here : http://www.linuxmce.com/linuxmce-skins-1.1.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The sql dumps of the databases needed for the build : http://www.linuxmce.com/linuxmce-databases-1.1.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The fake windows binaries needed for the build : http://www.linuxmce.com/linuxmce-fakewindowsbin-1.1.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The arch independent packages needed for the build : http://www.linuxmce.com/linuxmce-independent-pkgs-1.1.tar.bz2&lt;/div&gt;</summary>
		<author><name>Alx</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3840</id>
		<title>Building From Source 1.1</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3840"/>
		<updated>2007-04-24T15:12:36Z</updated>

		<summary type="html">&lt;p&gt;Alx: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before You Begin==&lt;br /&gt;
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&#039;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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Build Scripts ==&lt;br /&gt;
The build scripts are in sourceforge svn so to get them you will need subversion installed.&lt;br /&gt;
 sudo apt-get install subversion&lt;br /&gt;
 cd /root&lt;br /&gt;
 svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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&#039;s a short description:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;Install_Build_Needed_Packages&#039;&#039;: 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. This will take about 5 minutes.&lt;br /&gt;
*&#039;&#039;Create Diskless Archive&#039;&#039;: Runs a debootstrap to create a base filesystem for Diskless Media Directors. It&#039;s needed later when it&#039;ll be packed in a deb packages. You also don&#039;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.&lt;br /&gt;
*&#039;&#039;Import_Skins&#039;&#039;: Since linuxmce uses a lot of pngs for the all sort of skins, you won&#039;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.&lt;br /&gt;
*&#039;&#039;Checkout_Svn&#039;&#039;: Will do a svn checkout on sourceforge to get all the needed sources&lt;br /&gt;
*&#039;&#039;Build_Replacements&#039;&#039;: LinuxMCE needs some 3rd party packages that are not part of ubuntu distribution. This function will build / get them for you.&lt;br /&gt;
*&#039;&#039;Build_MakeRelease_Binary&#039;&#039;: 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.&lt;br /&gt;
*&#039;&#039;Import_Build_Database&#039;&#039;: Imports a fresh copy of the pluto databases needed at build time.&lt;br /&gt;
*&#039;&#039;Create_Fake_Windows_Binaries&#039;&#039;: Orbiter and other aplications don&#039;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&#039;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&#039;t fail to run.&lt;br /&gt;
*&#039;&#039;Build_Pluto_Stuff&#039;&#039;: Uses MakeRelase to compile the sources and build packages out of them.&lt;br /&gt;
*&#039;&#039;Create_Local_Repository&#039;&#039;: Optional you can create a local repository so that you can easily test your debs. By default, the local repository will be put in /var/www&lt;br /&gt;
*&#039;&#039;Create_ISO&#039;&#039;: Is an optional step and creates an iso with all the needed packages for a linuxmce instalation. For this, get-packages.sh script is called.&lt;br /&gt;
&lt;br /&gt;
== Source Code Location ==&lt;br /&gt;
&lt;br /&gt;
Our source code is located on sourceforge and you can get it by svn from : https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/&lt;br /&gt;
&lt;br /&gt;
The png used for the skins are located here : http://www.linuxmce.com/linuxmce-skins-1.1.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The sql dumps of the databases needed for the build : http://www.linuxmce.com/linuxmce-databases-1.1.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The fake windows binaries needed for the build : http://www.linuxmce.com/linuxmce-fakewindowsbin-1.1.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The arch independent packages needed for the build : http://www.linuxmce.com/linuxmce-independent-pkgs-1.1.tar.bz2&lt;/div&gt;</summary>
		<author><name>Alx</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3839</id>
		<title>Building From Source 1.1</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3839"/>
		<updated>2007-04-24T14:34:27Z</updated>

		<summary type="html">&lt;p&gt;Alx: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before You Begin==&lt;br /&gt;
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&#039;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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Build Scripts ==&lt;br /&gt;
The build scripts are in sourceforge svn so to get them you will need subversion installed.&lt;br /&gt;
 sudo apt-get install subversion&lt;br /&gt;
 cd /root&lt;br /&gt;
 svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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&#039;s a short description:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;Install_Build_Needed_Packages&#039;&#039;: 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. This will take about 5 minutes.&lt;br /&gt;
*&#039;&#039;Create Diskless Archive&#039;&#039;: Runs a debootstrap to create a base filesystem for Diskless Media Directors. It&#039;s needed later when it&#039;ll be packed in a deb packages. You also don&#039;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.&lt;br /&gt;
*&#039;&#039;Import_Skins&#039;&#039;: Since linuxmce uses a lot of pngs for the all sort of skins, you won&#039;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.&lt;br /&gt;
*&#039;&#039;Checkout_Svn&#039;&#039;: Will do a svn checkout on sourceforge to get all the needed sources&lt;br /&gt;
*&#039;&#039;Build_Replacements&#039;&#039;: LinuxMCE needs some 3rd party packages that are not part of ubuntu distribution. This function will build / get them for you.&lt;br /&gt;
*&#039;&#039;Build_MakeRelease_Binary&#039;&#039;: 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.&lt;br /&gt;
*&#039;&#039;Import_Build_Database&#039;&#039;: Imports a fresh copy of the pluto databases needed at build time.&lt;br /&gt;
*&#039;&#039;Create_Fake_Windows_Binaries&#039;&#039;: Orbiter and other aplications don&#039;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&#039;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&#039;t fail to run.&lt;br /&gt;
*&#039;&#039;Build_Pluto_Stuff&#039;&#039;: Uses MakeRelase to compile the sources and build packages out of them.&lt;br /&gt;
*&#039;&#039;Create_Local_Repository&#039;&#039;: Optional you can create a local repository so that you can easily test your debs. By default the local repository will be put in /var/www&lt;br /&gt;
*&#039;&#039;Create_ISO&#039;&#039;: Is an optional step and creates an iso with all the needed packages for a linuxmce instalation. For this, get-packages.sh script is called.&lt;br /&gt;
&lt;br /&gt;
== Source Code Location ==&lt;br /&gt;
&lt;br /&gt;
Our source code is located on sourceforge and you can get it by svn from : https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/&lt;br /&gt;
&lt;br /&gt;
The png used for the skins are located here : http://www.linuxmce.com/linuxmce-skins-1.1.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The sql dumps of the databases needed for the build : http://www.linuxmce.com/linuxmce-databases-1.1.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The fake windows binaries needed for the build : http://www.linuxmce.com/linuxmce-fakewindowsbin-1.1.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The arch independent packages needed for the build : http://www.linuxmce.com/linuxmce-independent-pkgs-1.1.tar.bz2&lt;/div&gt;</summary>
		<author><name>Alx</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3838</id>
		<title>Building From Source 1.1</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3838"/>
		<updated>2007-04-24T14:23:41Z</updated>

		<summary type="html">&lt;p&gt;Alx: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before You Begin==&lt;br /&gt;
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&#039;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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Build Scripts ==&lt;br /&gt;
The build scripts are in sourceforge svn so to get them you will need subversion installed.&lt;br /&gt;
 sudo apt-get install subversion&lt;br /&gt;
 cd /root&lt;br /&gt;
 svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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&#039;s a short description:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;Install_Build_Needed_Packages&#039;&#039;: 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. This will take about 5 minutes.&lt;br /&gt;
*&#039;&#039;Create Diskless Archive&#039;&#039;: Runs a debootstrap to create a base filesystem for Diskless Media Directors. It&#039;s needed later when it&#039;ll be packed in a deb packages. You also don&#039;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.&lt;br /&gt;
*&#039;&#039;Import_Skins&#039;&#039;: Since linuxmce uses a lot of pngs for the all sort of skins, you won&#039;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.&lt;br /&gt;
*&#039;&#039;Checkout_Svn&#039;&#039;: Will do a svn checkout on sourceforge to get all the needed sources&lt;br /&gt;
*&#039;&#039;Build_Replacements&#039;&#039;: LinuxMCE needs some 3rd party packages that are not part of ubuntu distribution. This function will build / get them for you.&lt;br /&gt;
*&#039;&#039;Build_MakeRelease_Binary&#039;&#039;: 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.&lt;br /&gt;
*&#039;&#039;Import_Build_Database&#039;&#039;: Imports a fresh copy of the pluto databases needed at build time.&lt;br /&gt;
*&#039;&#039;Create_Fake_Windows_Binaries&#039;&#039;: Orbiter and other aplications don&#039;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&#039;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&#039;t fail to run.&lt;br /&gt;
*&#039;&#039;Build_Pluto_Stuff&#039;&#039;: Uses MakeRelase to compile the sources and build packages out of them.&lt;br /&gt;
*&#039;&#039;Create_Local_Repository&#039;&#039;: Optional you can create a local repository so that you can easily test your debs.&lt;br /&gt;
*&#039;&#039;Create_ISO&#039;&#039;: Is an optional step and creates an iso with all the needed packages for a linuxmce instalation. For this, get-packages.sh script is called.&lt;br /&gt;
&lt;br /&gt;
== Source Code Location ==&lt;br /&gt;
&lt;br /&gt;
Our source code is located on sourceforge and you can get it by svn from : https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/&lt;br /&gt;
&lt;br /&gt;
The png used for the skins are located here : http://www.linuxmce.com/linuxmce-skins-1.1.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The sql dumps of the databases needed for the build : http://www.linuxmce.com/linuxmce-databases-1.1.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The fake windows binaries needed for the build : http://www.linuxmce.com/linuxmce-fakewindowsbin-1.1.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The arch independent packages needed for the build : http://www.linuxmce.com/linuxmce-independent-pkgs-1.1.tar.bz2&lt;/div&gt;</summary>
		<author><name>Alx</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3837</id>
		<title>Building From Source 1.1</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3837"/>
		<updated>2007-04-24T14:20:56Z</updated>

		<summary type="html">&lt;p&gt;Alx: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before You Begin==&lt;br /&gt;
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&#039;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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Build Scripts ==&lt;br /&gt;
The build scripts are in sourceforge svn so to get them you will need subversion installed.&lt;br /&gt;
 sudo apt-get install subversion&lt;br /&gt;
 cd /root&lt;br /&gt;
 svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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&#039;s a short description:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;Install_Build_Needed_Packages&#039;&#039;: 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. This will take about 5 minutes.&lt;br /&gt;
*&#039;&#039;Create Diskless Archive&#039;&#039;: Runs a debootstrap to create a base filesystem for Diskless Media Directors. It&#039;s needed later when it&#039;ll be packed in a deb packages. You also don&#039;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.&lt;br /&gt;
*&#039;&#039;Import_Skins&#039;&#039;: Since linuxmce uses a lot of pngs for the all sort of skins, you won&#039;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.&lt;br /&gt;
*&#039;&#039;Checkout_Svn&#039;&#039;: Will do a svn checkout on sourceforge to get all the needed sources&lt;br /&gt;
*&#039;&#039;Build_Replacements&#039;&#039;: LinuxMCE needs some 3rd party packages that are not part of ubuntu distribution. This function will build / get them for you.&lt;br /&gt;
*&#039;&#039;Build_MakeRelease_Binary&#039;&#039;: 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.&lt;br /&gt;
*&#039;&#039;Import_Build_Database&#039;&#039;: Imports a fresh copy of the pluto databases needed at build time.&lt;br /&gt;
*&#039;&#039;Create_Fake_Windows_Binaries&#039;&#039;: Orbiter and other aplications don&#039;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&#039;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&#039;t fail to run.&lt;br /&gt;
*&#039;&#039;Build_Pluto_Stuff&#039;&#039;: Uses MakeRelase to compile the sources and build packages out of them.&lt;br /&gt;
*&#039;&#039;Create_Local_Repository&#039;&#039;: Optional you can create a local repository so that you can easily test your debs.&lt;br /&gt;
*&#039;&#039;Create_ISO&#039;&#039;: Creates an iso with all the needed packages for a linuxmce instalation. For this, get-packages.sh script is called.&lt;br /&gt;
&lt;br /&gt;
== Source Code Location ==&lt;br /&gt;
&lt;br /&gt;
Our source code is located on sourceforge and you can get it by svn from : https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/&lt;br /&gt;
&lt;br /&gt;
The png used for the skins are located here : http://www.linuxmce.com/linuxmce-skins-1.1.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The sql dumps of the databases needed for the build : http://www.linuxmce.com/linuxmce-databases-1.1.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The fake windows binaries needed for the build : http://www.linuxmce.com/linuxmce-fakewindowsbin-1.1.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The arch independent packages needed for the build : http://www.linuxmce.com/linuxmce-independent-pkgs-1.1.tar.bz2&lt;/div&gt;</summary>
		<author><name>Alx</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3836</id>
		<title>Building From Source 1.1</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3836"/>
		<updated>2007-04-24T13:57:59Z</updated>

		<summary type="html">&lt;p&gt;Alx: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before You Begin==&lt;br /&gt;
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&#039;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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== The Build Scripts ==&lt;br /&gt;
The build scripts are in sourceforge svn so to get them you will need subversion installed.&lt;br /&gt;
 sudo apt-get install subversion&lt;br /&gt;
 cd /root&lt;br /&gt;
 svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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&#039;s a short description:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;Install_Build_Needed_Packages&#039;&#039;: 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. This will take about 5 minutes.&lt;br /&gt;
*&#039;&#039;Create Diskless Archive&#039;&#039;: Runs a debootstrap to create a base filesystem for Diskless Media Directors. It&#039;s needed later when it&#039;ll be packed in a deb packages. You also don&#039;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.&lt;br /&gt;
*&#039;&#039;Import_Skins&#039;&#039;: Since linuxmce uses a lot of pngs for the all sort of skins, you won&#039;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.&lt;br /&gt;
*&#039;&#039;Checkout_Svn&#039;&#039;: Will do a svn checkout on sourceforge to get all the needed sources&lt;br /&gt;
*&#039;&#039;Build_Replacements&#039;&#039;: LinuxMCE needs some 3rd party packages that are not part of ubuntu distribution. This function will build / get them for you.&lt;br /&gt;
*&#039;&#039;Build_MakeRelease_Binary&#039;&#039;: 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.&lt;br /&gt;
*&#039;&#039;Import_Build_Database&#039;&#039;: Imports a fresh copy of the pluto databases needed at build time.&lt;br /&gt;
*&#039;&#039;Create_Fake_Windows_Binaries&#039;&#039;: Orbiter and other aplications don&#039;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&#039;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&#039;t fail to run.&lt;br /&gt;
*&#039;&#039;Build_Pluto_Stuff&#039;&#039;: Uses MakeRelase to compile the sources and build packages out of them.&lt;br /&gt;
*&#039;&#039;Create_Local_Repository&#039;&#039;: Optional you can create a local repository so that you can easily test your debs.&lt;br /&gt;
*&#039;&#039;Create_ISO&#039;&#039;: Creates an iso with all the needed packages for a linuxmce instalation. For this, get-packages.sh script is called.&lt;br /&gt;
&lt;br /&gt;
== Source Code Location ==&lt;br /&gt;
&lt;br /&gt;
Our source code is located on sourceforge and you can get it by svn from : https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/&lt;br /&gt;
&lt;br /&gt;
The png used for the skins are located here : http://www.linuxmce.com/linuxmce-skins-1.0.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The sql dumps of the databases needed for the build : http://www.linuxmce.com/linuxmce-databases-1.0.tar.gz&lt;/div&gt;</summary>
		<author><name>Alx</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3835</id>
		<title>Building From Source 1.1</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3835"/>
		<updated>2007-04-24T08:42:53Z</updated>

		<summary type="html">&lt;p&gt;Alx: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before You Begin==&lt;br /&gt;
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&#039;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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== The Build Scripts ==&lt;br /&gt;
The build scripts are in sourceforge svn so to get them you will need subversion installed.&lt;br /&gt;
 sudo apt-get install subversion&lt;br /&gt;
 cd /root&lt;br /&gt;
 svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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&#039;s a short description:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;Install_Build_Needed_Packages&#039;&#039;: 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. This will take about 5 minutes.&lt;br /&gt;
*&#039;&#039;Create Diskless Archive&#039;&#039;: Runs a debootstrap to create a base filesystem for Diskless Media Directors. It&#039;s needed later when it&#039;ll be packed in a deb packages. You also don&#039;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.&lt;br /&gt;
*&#039;&#039;Import_Skins&#039;&#039;: Since linuxmce uses a lot of pngs for the all sort of skins, you won&#039;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.&lt;br /&gt;
*&#039;&#039;Checkout_Svn&#039;&#039;: Will do a svn checkout on sourceforge to get all the needed sources&lt;br /&gt;
*&#039;&#039;Build_Replacements&#039;&#039;: LinuxMCE needs some 3rd party packages that are not part of ubuntu distribution. This function will build / get them for you.&lt;br /&gt;
*&#039;&#039;Build_MakeRelease_Binary&#039;&#039;: 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.&lt;br /&gt;
*&#039;&#039;Import_Build_Database&#039;&#039;: Imports a fresh copy of the pluto databases needed at build time.&lt;br /&gt;
*&#039;&#039;Create_Fake_Windows_Binaries&#039;&#039;: Orbiter and other aplications don&#039;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&#039;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&#039;t fail to run.&lt;br /&gt;
*&#039;&#039;Build_Pluto_Stuff&#039;&#039;: Uses MakeRelase to compile the sources and build packages out of them&lt;br /&gt;
*&#039;&#039;Create_Local_Repository&#039;&#039;: Optional you can create a local repository so that you can easily test your debs.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Source Code Location ==&lt;br /&gt;
&lt;br /&gt;
Our source code is located on sourceforge and you can get it by svn from : https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/&lt;br /&gt;
&lt;br /&gt;
The png used for the skins are located here : http://www.linuxmce.com/linuxmce-skins-1.0.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The sql dumps of the databases needed for the build : http://www.linuxmce.com/linuxmce-databases-1.0.tar.gz&lt;/div&gt;</summary>
		<author><name>Alx</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3834</id>
		<title>Building From Source 1.1</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3834"/>
		<updated>2007-04-23T16:50:18Z</updated>

		<summary type="html">&lt;p&gt;Alx: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before You Begin==&lt;br /&gt;
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&#039;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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== The Build Scripts ==&lt;br /&gt;
The build scripts are in sourceforge svn so to get them you will need subversion installed.&lt;br /&gt;
 sudo apt-get install subversion&lt;br /&gt;
 sudo mkdir -p /root/Ubuntu_Helpers&lt;br /&gt;
 cd /root/Ubuntu_Helpers&lt;br /&gt;
 svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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&#039;s a short description:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;Install_Build_Needed_Packages&#039;&#039;: 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. This will take about 5 minutes.&lt;br /&gt;
*&#039;&#039;Create Diskless Archive&#039;&#039;: Runs a debootstrap to create a base filesystem for Diskless Media Directors. It&#039;s needed later when it&#039;ll be packed in a deb packages. You also don&#039;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.&lt;br /&gt;
*&#039;&#039;Import_Skins&#039;&#039;: Since linuxmce uses a lot of pngs for the all sort of skins, you won&#039;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.&lt;br /&gt;
*&#039;&#039;Checkout_Svn&#039;&#039;: Will do a svn checkout on sourceforge to get all the needed sources&lt;br /&gt;
*&#039;&#039;Build_Replacements&#039;&#039;: LinuxMCE needs some 3rd party packages that are not part of ubuntu distribution. This function will build / get them for you.&lt;br /&gt;
*&#039;&#039;Build_MakeRelease_Binary&#039;&#039;: 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.&lt;br /&gt;
*&#039;&#039;Import_Build_Database&#039;&#039;: Imports a fresh copy of the pluto databases needed at build time.&lt;br /&gt;
*&#039;&#039;Create_Fake_Windows_Binaries&#039;&#039;: Orbiter and other aplications don&#039;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&#039;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&#039;t fail to run.&lt;br /&gt;
*&#039;&#039;Build_Pluto_Stuff&#039;&#039;: Uses MakeRelase to compile the sources and build packages out of them&lt;br /&gt;
*&#039;&#039;Create_Local_Repository&#039;&#039;: Optional you can create a local repository so that you can easily test your debs.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Source Code Location ==&lt;br /&gt;
&lt;br /&gt;
Our source code is located on sourceforge and you can get it by svn from : https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/&lt;br /&gt;
&lt;br /&gt;
The png used for the skins are located here : http://www.linuxmce.com/linuxmce-skins-1.0.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The sql dumps of the databases needed for the build : http://www.linuxmce.com/linuxmce-databases-1.0.tar.gz&lt;/div&gt;</summary>
		<author><name>Alx</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3833</id>
		<title>Building From Source 1.1</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3833"/>
		<updated>2007-04-23T12:51:54Z</updated>

		<summary type="html">&lt;p&gt;Alx: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before You Begin==&lt;br /&gt;
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&#039;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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== The Build Scripts ==&lt;br /&gt;
The build scripts are in sourceforge svn so to get them you will need subversion installed.&lt;br /&gt;
 sudo apt-get install subversion&lt;br /&gt;
 sudo mkdir -p /root/Ubuntu_Helpers&lt;br /&gt;
 cd /root/Ubuntu_Helpers&lt;br /&gt;
 svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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&#039;s a short description:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;Install_Build_Needed_Packages&#039;&#039;: 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. This will take about 5 minutes.&lt;br /&gt;
*&#039;&#039;Create Diskless Archive&#039;&#039;: Runs a debootstrap to create a base filesystem for Diskless Media Directors. It&#039;s needed later when it&#039;ll be packed in a deb packages. You also don&#039;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.&lt;br /&gt;
*&#039;&#039;Import_Skins&#039;&#039;: Since linuxmce uses a lot of pngs for the all sort of skins, you won&#039;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.&lt;br /&gt;
*&#039;&#039;Checkout_Svn&#039;&#039;: Will do a svn checkout on sourceforge to get all the needed sources&lt;br /&gt;
*&#039;&#039;Build_Replacements&#039;&#039;: LinuxMCE needs some 3rd party some packages that are not part of ubuntu distribution. This function will build / get them for you.&lt;br /&gt;
*&#039;&#039;Build_MakeRelease_Binary&#039;&#039;: 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.&lt;br /&gt;
*&#039;&#039;Import_Build_Database&#039;&#039;: Imports a fresh copy of the pluto databases needed at build time.&lt;br /&gt;
*&#039;&#039;Create_Fake_Windows_Binaries&#039;&#039;: Orbiter and other aplications don&#039;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&#039;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&#039;t fail to run.&lt;br /&gt;
*&#039;&#039;Build_Pluto_Stuff&#039;&#039;: Uses MakeRelase to compile the sources and build packages out of them&lt;br /&gt;
*&#039;&#039;Create_Local_Repository&#039;&#039;: Optional you can create a local repository so that you can easily test your debs.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Source Code Location ==&lt;br /&gt;
&lt;br /&gt;
Our source code is located on sourceforge and you can get it by svn from : https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/&lt;br /&gt;
&lt;br /&gt;
The png used for the skins are located here : http://www.linuxmce.com/linuxmce-skins-1.0.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The sql dumps of the databases needed for the build : http://www.linuxmce.com/linuxmce-databases-1.0.tar.gz&lt;/div&gt;</summary>
		<author><name>Alx</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3832</id>
		<title>Building From Source 1.1</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3832"/>
		<updated>2007-04-23T11:45:37Z</updated>

		<summary type="html">&lt;p&gt;Alx: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before You Begin==&lt;br /&gt;
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&#039;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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== The Build Scripts ==&lt;br /&gt;
The build scripts are in sourceforge svn so to get them you will need subversion installed.&lt;br /&gt;
 sudo apt-get install subversion&lt;br /&gt;
 sudo mkdir -p /root/Ubuntu_Helpers&lt;br /&gt;
 cd /root/Ubuntu_Helpers&lt;br /&gt;
 svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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&#039;s a short description:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;Install_Build_Needed_Packages&#039;&#039;: 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.&lt;br /&gt;
*&#039;&#039;Create Diskless Archive&#039;&#039;: Runs a debootstrap to create a base filesystem for Diskless Media Directors. It&#039;s needed later when it&#039;ll be packed in a deb packages. You also don&#039;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.&lt;br /&gt;
*&#039;&#039;Import_Skins&#039;&#039;: Since linuxmce uses a lot of pngs for the all sort of skins, you won&#039;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.&lt;br /&gt;
*&#039;&#039;Checkout_Svn&#039;&#039;: Will do a svn checkout on sourceforge to get all the needed sources&lt;br /&gt;
*&#039;&#039;Build_Replacements&#039;&#039;: LinuxMCE needs some 3rd party some packages that are not part of ubuntu distribution. This function will build / get them for you.&lt;br /&gt;
*&#039;&#039;Build_MakeRelease_Binary&#039;&#039;: 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.&lt;br /&gt;
*&#039;&#039;Import_Build_Database&#039;&#039;: Imports a fresh copy of the pluto databases needed at build time.&lt;br /&gt;
*&#039;&#039;Create_Fake_Windows_Binaries&#039;&#039;: Orbiter and other aplications don&#039;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&#039;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&#039;t fail to run.&lt;br /&gt;
*&#039;&#039;Build_Pluto_Stuff&#039;&#039;: Uses MakeRelase to compile the sources and build packages out of them&lt;br /&gt;
*&#039;&#039;Create_Local_Repository&#039;&#039;: Optional you can create a local repository so that you can easily test your debs.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Source Code Location ==&lt;br /&gt;
&lt;br /&gt;
Our source code is located on sourceforge and you can get it by svn from : https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/&lt;br /&gt;
&lt;br /&gt;
The png used for the skins are located here : http://www.linuxmce.com/linuxmce-skins-1.0.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The sql dumps of the databases needed for the build : http://www.linuxmce.com/linuxmce-databases-1.0.tar.gz&lt;/div&gt;</summary>
		<author><name>Alx</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3831</id>
		<title>Building From Source 1.1</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Building_From_Source_1.1&amp;diff=3831"/>
		<updated>2007-04-23T11:41:13Z</updated>

		<summary type="html">&lt;p&gt;Alx: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before You Begin==&lt;br /&gt;
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&#039;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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== The Build Scripts ==&lt;br /&gt;
The build scripts are in sourceforge svn so to get them you will need subversion installed.&lt;br /&gt;
 sudo apt-get install subversion&lt;br /&gt;
 svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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&#039;s a short description:&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;Install_Build_Needed_Packages&#039;&#039;: 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.&lt;br /&gt;
*&#039;&#039;Create Diskless Archive&#039;&#039;: Runs a debootstrap to create a base filesystem for Diskless Media Directors. It&#039;s needed later when it&#039;ll be packed in a deb packages. You also don&#039;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.&lt;br /&gt;
*&#039;&#039;Import_Skins&#039;&#039;: Since linuxmce uses a lot of pngs for the all sort of skins, you won&#039;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.&lt;br /&gt;
*&#039;&#039;Checkout_Svn&#039;&#039;: Will do a svn checkout on sourceforge to get all the needed sources&lt;br /&gt;
*&#039;&#039;Build_Replacements&#039;&#039;: LinuxMCE needs some 3rd party some packages that are not part of ubuntu distribution. This function will build / get them for you.&lt;br /&gt;
*&#039;&#039;Build_MakeRelease_Binary&#039;&#039;: 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.&lt;br /&gt;
*&#039;&#039;Import_Build_Database&#039;&#039;: Imports a fresh copy of the pluto databases needed at build time.&lt;br /&gt;
*&#039;&#039;Create_Fake_Windows_Binaries&#039;&#039;: Orbiter and other aplications don&#039;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&#039;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&#039;t fail to run.&lt;br /&gt;
*&#039;&#039;Build_Pluto_Stuff&#039;&#039;: Uses MakeRelase to compile the sources and build packages out of them&lt;br /&gt;
*&#039;&#039;Create_Local_Repository&#039;&#039;: Optional you can create a local repository so that you can easily test your debs.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Source Code Location ==&lt;br /&gt;
&lt;br /&gt;
Our source code is located on sourceforge and you can get it by svn from : https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/&lt;br /&gt;
&lt;br /&gt;
The png used for the skins are located here : http://www.linuxmce.com/linuxmce-skins-1.0.tar.bz2&lt;br /&gt;
&lt;br /&gt;
The sql dumps of the databases needed for the build : http://www.linuxmce.com/linuxmce-databases-1.0.tar.gz&lt;/div&gt;</summary>
		<author><name>Alx</name></author>
	</entry>
</feed>