Tiny CentOS 5.5 32 bit (i386) - Revision history

Kamran: /* Summary */

Kamran — Wed, 05 Jan 2011 06:43:29 GMT

Summary

← Older revision		Revision as of 06:43, 5 January 2011
Line 18:		Line 18:

	==Summary==		==Summary==
-	~~(Finalized on 18 Dec 2010)~~	+	As I mentioned earlier. The idea is to have an absolute minimum number of packages. The driving force behind this thought was a need to have such a small CD, which would be easier to download and distribute, with a capability to be topped up with additional packages from the internet, when necessary. And effective enough to get the job done. Since I have included yum in it, I (and you) can add any other RPM based package to it, without a problem. In coming days however, I will release a (so called) hypervisor version, InshaAllah (God Willing). Update: HypervisorEdition is released. [[CentOS 5.5 x86 64 Hypervisor Edition (Minimal)]]
-	As I mentioned earlier. The idea is to have an absolute minimum number of packages. The driving force behind this thought was a need to have such a small CD, which would be easier to download and distribute, with a capability to be topped up with additional packages from the internet, when necessary. And effective enough to get the job done. Since I have included yum in it, I (and you) can add any other RPM based package to it, without a problem. In coming days however, I will release a (so called) hypervisor version, InshaAllah (God Willing). HypervisorEdition released ~~here~~.	+

	CENTOS/RHEL already has a @core group (option), which can be used in the kickstart based installation. Even that takes up considerable space and installs CUPS, SENDMAIL and a lot of other un-necessary packages.		CENTOS/RHEL already has a @core group (option), which can be used in the kickstart based installation. Even that takes up considerable space and installs CUPS, SENDMAIL and a lot of other un-necessary packages.

-	Since I wanted to create a very small list of RPMS. I came up with a plan. I started with kernel, and kept trying to install the related RPMS in a temporary directory using RPM. I continued including missing files (RPMS), which were being reported by RPM as required dependencies. When all dependencies got resolved, I believed I had the desired minimal file list.	+	Since I wanted to create a very small list of RPMS. I came up with a plan. I started with kernel, and kept trying to install the related RPMS in a temporary directory using RPM. I continued including missing files (RPMS), which were being reported by RPM as required dependencies. When all dependencies got resolved, I believed I had the desired minimal file list. Update: Can be done with more ease, using yumdownloader.

	When I completed the basic minimal list, I added ssh-server, wget and yum to it. I further added the following: grub (boot loader), openssh-clients (for ssh, scp, sftp, etc), and vim-minimal (editor).		When I completed the basic minimal list, I added ssh-server, wget and yum to it. I further added the following: grub (boot loader), openssh-clients (for ssh, scp, sftp, etc), and vim-minimal (editor).
-
-	~~That would essentially make it a working server installation/distribution. Anything else can be added through "yum". The packages size is 131 RPM files (CENTOS), and 149 MB in total.~~

	Note that I (generated and) tested this on a KVM based VM.		Note that I (generated and) tested this on a KVM based VM.

Kamran: /* Summary */

Kamran — Wed, 05 Jan 2011 06:39:59 GMT

Summary

← Older revision		Revision as of 06:39, 5 January 2011
Line 19:		Line 19:
	==Summary==		==Summary==
	(Finalized on 18 Dec 2010)		(Finalized on 18 Dec 2010)
-	As I mentioned earlier. The idea is to have an absolute minimum number of packages. The driving force behind this thought ~~is the latest RedHat Virtualization solution, RHEV, or, RedHat Enterprise Virtualization. RHEV is~~ a ~~slim/cut down version of RHEL 6, working as~~ a ~~KVM Hypervisor~~, with a ~~very small install foot-print. I noticed that it is a similar concept as Citrix XEN Server. So, I wanted~~ to ~~see, if I can~~ be ~~successful in creating a similar product~~, ~~based on CentOS 5~~.~~5. Notice that~~ the ~~procedure explained below DOES NOT contain libvirt, as yet. This is only because I was first interested in creating a distribution as small as possible~~. Since I have included yum in it, I (and you) can add any other RPM based package to it, without a problem. In coming days however, I will release a (so called) hypervisor version, InshaAllah (God Willing).	+	As I mentioned earlier. The idea is to have an absolute minimum number of packages. The driving force behind this thought was a need to have such a small CD, which would be easier to download and distribute, with a capability to be topped up with additional packages from the internet, when necessary. And effective enough to get the job done. Since I have included yum in it, I (and you) can add any other RPM based package to it, without a problem. In coming days however, I will release a (so called) hypervisor version, InshaAllah (God Willing). HypervisorEdition released here.

	CENTOS/RHEL already has a @core group (option), which can be used in the kickstart based installation. Even that takes up considerable space and installs CUPS, SENDMAIL and a lot of other un-necessary packages.		CENTOS/RHEL already has a @core group (option), which can be used in the kickstart based installation. Even that takes up considerable space and installs CUPS, SENDMAIL and a lot of other un-necessary packages.

Kamran: /* Infrastructure */

Kamran — Tue, 04 Jan 2011 07:56:52 GMT

Infrastructure

← Older revision		Revision as of 07:56, 4 January 2011
Line 59:		Line 59:
	<pre>		<pre>
	[root@fedora14 cdimages]# cat /etc/exports		[root@fedora14 cdimages]# cat /etc/exports
-	/data/cdimages 192.168.122.0/255.255.255.0(rw,no_root_squash).	+	/data/cdimages 192.168.122.0/255.255.255.0(rw,no_root_squash)
	[root@fedora14 cdimages]#		[root@fedora14 cdimages]#

Line 76:		Line 76:
	</pre>		</pre>
	The BuildHost has only 512 MB Virtual Memory, and 2GB Virtual Disk. We basically do not need much disk space on the build host. The BuildHost (VM) has the IP: 192.168.122.94, on its eth0 interface.		The BuildHost has only 512 MB Virtual Memory, and 2GB Virtual Disk. We basically do not need much disk space on the build host. The BuildHost (VM) has the IP: 192.168.122.94, on its eth0 interface.
-

	==Steps==		==Steps==

Kamran: /* Test the stuff you just build (the bootable ISO image) */

Kamran — Tue, 21 Dec 2010 05:39:17 GMT

Test the stuff you just build (the bootable ISO image)

← Older revision		Revision as of 05:39, 21 December 2010
Line 680:		Line 680:

	[[File:Screenshot-centos-55-32-tiny-cd_Virtual_Machine-small.png]]		[[File:Screenshot-centos-55-32-tiny-cd_Virtual_Machine-small.png]]
		+

	Note: Just press ENTER/OK on this (package selection) screen.		Note: Just press ENTER/OK on this (package selection) screen.
	[[File:Screenshot-centos-55-32-tiny-cd Virtual Machine-2-small.png]]		[[File:Screenshot-centos-55-32-tiny-cd Virtual Machine-2-small.png]]
		+

	[[File:Screenshot-centos-55-32-tiny-cd Virtual Machine-3-small.png]]		[[File:Screenshot-centos-55-32-tiny-cd Virtual Machine-3-small.png]]

Kamran: /* Why a small/server CD in the first place? */

Kamran — Mon, 20 Dec 2010 12:17:37 GMT

Why a small/server CD in the first place?

← Older revision		Revision as of 12:17, 20 December 2010
Line 3:		Line 3:
	==Why a small/server CD in the first place?==		==Why a small/server CD in the first place?==
	Well, the key benefits are:		Well, the key benefits are:
-	* centos.org does not provide a server CD for centos 5.5. That is a good enough reason to create one ourselves.	+	* centos.org does not provide a server CD for centos 5.5. That is a good enough reason to create one ourselves, in the first place.
	* Small ISO size, makes it easier and ideal to download, even in bandwidth/volume limited environments.		* Small ISO size, makes it easier and ideal to download, even in bandwidth/volume limited environments.
	* Less packages means, less vulnerabilities (if you decide to use it in production).		* Less packages means, less vulnerabilities (if you decide to use it in production).

Kamran: /* Why a small/server CD in the first place? */

Kamran — Mon, 20 Dec 2010 12:17:16 GMT

Why a small/server CD in the first place?

← Older revision		Revision as of 12:17, 20 December 2010
Line 3:		Line 3:
	==Why a small/server CD in the first place?==		==Why a small/server CD in the first place?==
	Well, the key benefits are:		Well, the key benefits are:
		+	* centos.org does not provide a server CD for centos 5.5. That is a good enough reason to create one ourselves.
	* Small ISO size, makes it easier and ideal to download, even in bandwidth/volume limited environments.		* Small ISO size, makes it easier and ideal to download, even in bandwidth/volume limited environments.
	* Less packages means, less vulnerabilities (if you decide to use it in production).		* Less packages means, less vulnerabilities (if you decide to use it in production).

Kamran at 11:22, 19 December 2010

Kamran — Sun, 19 Dec 2010 11:22:05 GMT

← Older revision		Revision as of 11:22, 19 December 2010
Line 18:		Line 18:
	==Summary==		==Summary==
	(Finalized on 18 Dec 2010)		(Finalized on 18 Dec 2010)
-	~~Based on my previous (unfinished) article on creating a Tiny CentOS distribution, I have created this article. This one is finished (almost).~~
-
	As I mentioned earlier. The idea is to have an absolute minimum number of packages. The driving force behind this thought is the latest RedHat Virtualization solution, RHEV, or, RedHat Enterprise Virtualization. RHEV is a slim/cut down version of RHEL 6, working as a KVM Hypervisor, with a very small install foot-print. I noticed that it is a similar concept as Citrix XEN Server. So, I wanted to see, if I can be successful in creating a similar product, based on CentOS 5.5. Notice that the procedure explained below DOES NOT contain libvirt, as yet. This is only because I was first interested in creating a distribution as small as possible. Since I have included yum in it, I (and you) can add any other RPM based package to it, without a problem. In coming days however, I will release a (so called) hypervisor version, InshaAllah (God Willing).		As I mentioned earlier. The idea is to have an absolute minimum number of packages. The driving force behind this thought is the latest RedHat Virtualization solution, RHEV, or, RedHat Enterprise Virtualization. RHEV is a slim/cut down version of RHEL 6, working as a KVM Hypervisor, with a very small install foot-print. I noticed that it is a similar concept as Citrix XEN Server. So, I wanted to see, if I can be successful in creating a similar product, based on CentOS 5.5. Notice that the procedure explained below DOES NOT contain libvirt, as yet. This is only because I was first interested in creating a distribution as small as possible. Since I have included yum in it, I (and you) can add any other RPM based package to it, without a problem. In coming days however, I will release a (so called) hypervisor version, InshaAllah (God Willing).

Kamran at 05:06, 19 December 2010

Kamran — Sun, 19 Dec 2010 05:06:37 GMT

← Older revision		Revision as of 05:06, 19 December 2010
Line 1:		Line 1:
	<b>CentOS-5.5-i386 minimalistic Server CD</b>		<b>CentOS-5.5-i386 minimalistic Server CD</b>
-	~~==Summary==~~
-	~~(Finalized on 18 Dec 2010)~~
-	~~Based on my previous (unfinished) article on creating a Tiny CentOS distribution, I have created this article. This one is finished (almost).~~
-
-	As I mentioned earlier. The idea is to have an absolute minimum number of packages. The driving force behind this thought is the latest RedHat Virtualization solution, RHEV, or, RedHat Enterprise Virtualization. RHEV is a slim/cut down version of RHEL 6, working as a KVM Hypervisor, with a very small install foot-print. I noticed that it is a similar concept as Citrix XEN Server. So, I wanted to see, if I can be successful in creating a similar product, based on CentOS 5.5. Notice that the procedure explained below DOES NOT contain libvirt, as yet. This is only because I was first interested in creating a distribution as small as possible. Since I have included yum in it, I (and you) can add any other RPM based package to it, without a problem. In coming days however, I will release a (so called) hypervisor version, InshaAllah (God Willing).
-
-	CENTOS/RHEL already has a @core group (option), which can be used in the kickstart based installation. Even that takes up considerable space and installs CUPS, SENDMAIL and a lot of other un-necessary packages.
-
-	Since I wanted to create a very small list of RPMS. I came up with a plan. I started with kernel, and kept trying to install the related RPMS in a temporary directory using RPM. I continued including missing files (RPMS), which were being reported by RPM as required dependencies. When all dependencies got resolved, I believed I had the desired minimal file list.
-
-	~~When I completed the basic minimal list, I added ssh-server, wget and yum to it. I further added the following: grub (boot loader), openssh-clients (for ssh, scp, sftp, etc), and vim-minimal (editor).~~
-
-	~~That would essentially make it a working server installation/distribution. Anything else can be added through "yum". The packages size is 131 RPM files (CENTOS), and 149 MB in total.~~
-
-	~~Note that I (generated and) tested this on a KVM based VM.~~

	==Why a small/server CD in the first place?==		==Why a small/server CD in the first place?==
Line 30:		Line 15:

	[v/p = Virtual or Physical]		[v/p = Virtual or Physical]
		+
		+	==Summary==
		+	(Finalized on 18 Dec 2010)
		+	Based on my previous (unfinished) article on creating a Tiny CentOS distribution, I have created this article. This one is finished (almost).
		+
		+	As I mentioned earlier. The idea is to have an absolute minimum number of packages. The driving force behind this thought is the latest RedHat Virtualization solution, RHEV, or, RedHat Enterprise Virtualization. RHEV is a slim/cut down version of RHEL 6, working as a KVM Hypervisor, with a very small install foot-print. I noticed that it is a similar concept as Citrix XEN Server. So, I wanted to see, if I can be successful in creating a similar product, based on CentOS 5.5. Notice that the procedure explained below DOES NOT contain libvirt, as yet. This is only because I was first interested in creating a distribution as small as possible. Since I have included yum in it, I (and you) can add any other RPM based package to it, without a problem. In coming days however, I will release a (so called) hypervisor version, InshaAllah (God Willing).
		+
		+	CENTOS/RHEL already has a @core group (option), which can be used in the kickstart based installation. Even that takes up considerable space and installs CUPS, SENDMAIL and a lot of other un-necessary packages.
		+
		+	Since I wanted to create a very small list of RPMS. I came up with a plan. I started with kernel, and kept trying to install the related RPMS in a temporary directory using RPM. I continued including missing files (RPMS), which were being reported by RPM as required dependencies. When all dependencies got resolved, I believed I had the desired minimal file list.
		+
		+	When I completed the basic minimal list, I added ssh-server, wget and yum to it. I further added the following: grub (boot loader), openssh-clients (for ssh, scp, sftp, etc), and vim-minimal (editor).
		+
		+	That would essentially make it a working server installation/distribution. Anything else can be added through "yum". The packages size is 131 RPM files (CENTOS), and 149 MB in total.
		+
		+	Note that I (generated and) tested this on a KVM based VM.

	==Infrastructure==		==Infrastructure==

Kamran at 11:59, 18 December 2010

Kamran — Sat, 18 Dec 2010 11:59:13 GMT

← Older revision		Revision as of 11:59, 18 December 2010
Line 1:		Line 1:
		+	<b>CentOS-5.5-i386 minimalistic Server CD</b>
	==Summary==		==Summary==
	(Finalized on 18 Dec 2010)		(Finalized on 18 Dec 2010)

Kamran: /* Why a small/server CD in the first place? */

Kamran — Sat, 18 Dec 2010 11:58:15 GMT

Why a small/server CD in the first place?

← Older revision		Revision as of 11:58, 18 December 2010
Line 28:		Line 28:
	* Provides HTTPD, out of the box, so if (for some reason) you can't connect your (v/p) box to the internet, you can still extract some productivity out of your (v/p) machine.		* Provides HTTPD, out of the box, so if (for some reason) you can't connect your (v/p) box to the internet, you can still extract some productivity out of your (v/p) machine.

-	[v/p = ~~Virual~~ or Physical]	+	[v/p = Virtual or Physical]

	==Infrastructure==		==Infrastructure==