<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.11" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: How to Develop Virtual Appliances Using Ubuntu JeOS</title>
	<link>http://www.linux-mag.com/id/4829/</link>
	<description>Open Source, Open Standards</description>
	<pubDate>Mon, 07 Jul 2008 04:07:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: Manish Kochar</title>
		<link>http://www.linux-mag.com/id/4829/#comment-1134</link>
		<pubDate>Wed, 04 Jun 2008 07:59:12 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4829/#comment-1134</guid>
					<description>I attempted to automate the trick described at
http://h0bbel.p0ggel.org/shrinking-vmdk-files

I wrote this script "packit.sh", into one of my jeos based appliances.
It could automatically remove the fragmented pockets, from all the partitions.

When I need to ship and share my appliance, with anybody, I run this script, then I run the VMware utility to defragment, and then tar/gzip the directory that needs to be shipped.

Works pretty well for me so I thought I might share.
Could somebody share a trick, that allows me to call this script automatically, whenever I shutdown my appliance.

### Bash script - packit.sh starts below this line ###
#!/bin/bash


SHRINK_IT ()
        {
                echo "creating $1, and filling up that partition until there\'s no more space"
                cat /dev/zero &#62; $1
                sync
                echo "deleting $1, so that we have no pockets left in that partition"
                rm -f $1
        }

ZEROFILL_ALL_DISKS
        {
        ## Description: 
        # This will "fillup" each partition with a file called zero.fill. 
        # And then delete that file, to remove fragmented pockets.

                DISKS=`df -h`
                D=`echo "${DISKS}" &#124; wc -l`
                C=`expr $D - 1`

                ITEMS=`echo "${DISKS}" &#124; tail -n $C &#124; awk '{print $6}'`
                for S in ${ITEMS}
                do
                        SHRINK_IT `readlink -f ${S}/zero.fill`
                done
        return;
        }

MAIN ()
        {
                # The list of Functions that must be called
                ZEROFILL_ALL_DISKS
        }

MAIN

### Bash script ends above this line ###

I guess we could similarly automate the other tasks, by adding more functions in the packit.sh script and then including them in the MAIN ()

Shipping and sharing jeos based appliance should also be always accompanied with a note for users to modify vmx file for new eth0 and also change in /etc/udev/rules.d/70-persistent-net.rules

When I get some more time, I think I will add-in functions for security too like removing SSH keys, etc., besides something to fix the changed mac-address.</description>
		<content:encoded><![CDATA[<p>I attempted to automate the trick described at<br />
<a href="http://h0bbel.p0ggel.org/shrinking-vmdk-files" rel="nofollow">http://h0bbel.p0ggel.org/shrinking-vmdk-files</a></p>
<p>I wrote this script &#8220;packit.sh&#8221;, into one of my jeos based appliances.<br />
It could automatically remove the fragmented pockets, from all the partitions.</p>
<p>When I need to ship and share my appliance, with anybody, I run this script, then I run the VMware utility to defragment, and then tar/gzip the directory that needs to be shipped.</p>
<p>Works pretty well for me so I thought I might share.<br />
Could somebody share a trick, that allows me to call this script automatically, whenever I shutdown my appliance.</p>
<p>### Bash script - packit.sh starts below this line ###<br />
#!/bin/bash</p>
<p>SHRINK_IT ()<br />
        {<br />
                echo &#8220;creating $1, and filling up that partition until there\&#8217;s no more space&#8221;<br />
                cat /dev/zero &gt; $1<br />
                sync<br />
                echo &#8220;deleting $1, so that we have no pockets left in that partition&#8221;<br />
                rm -f $1<br />
        }</p>
<p>ZEROFILL_ALL_DISKS<br />
        {<br />
        ## Description:<br />
        # This will &#8220;fillup&#8221; each partition with a file called zero.fill.<br />
        # And then delete that file, to remove fragmented pockets.</p>
<p>                DISKS=`df -h`<br />
                D=`echo &#8220;${DISKS}&#8221; | wc -l`<br />
                C=`expr $D - 1`</p>
<p>                ITEMS=`echo &#8220;${DISKS}&#8221; | tail -n $C | awk &#8216;{print $6}&#8217;`<br />
                for S in ${ITEMS}<br />
                do<br />
                        SHRINK_IT `readlink -f ${S}/zero.fill`<br />
                done<br />
        return;<br />
        }</p>
<p>MAIN ()<br />
        {<br />
                # The list of Functions that must be called<br />
                ZEROFILL_ALL_DISKS<br />
        }</p>
<p>MAIN</p>
<p>### Bash script ends above this line ###</p>
<p>I guess we could similarly automate the other tasks, by adding more functions in the packit.sh script and then including them in the MAIN ()</p>
<p>Shipping and sharing jeos based appliance should also be always accompanied with a note for users to modify vmx file for new eth0 and also change in /etc/udev/rules.d/70-persistent-net.rules</p>
<p>When I get some more time, I think I will add-in functions for security too like removing SSH keys, etc., besides something to fix the changed mac-address.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: murraymints</title>
		<link>http://www.linux-mag.com/id/4829/#comment-876</link>
		<pubDate>Tue, 04 Mar 2008 23:00:59 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4829/#comment-876</guid>
					<description>'sudo tasksel install lamp-server' workerd for me, when I tried 'sudo apt-get install lamp-server' I just got package not found errors</description>
		<content:encoded><![CDATA[<p>&#8217;sudo tasksel install lamp-server&#8217; workerd for me, when I tried &#8217;sudo apt-get install lamp-server&#8217; I just got package not found errors
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: nijaba</title>
		<link>http://www.linux-mag.com/id/4829/#comment-872</link>
		<pubDate>Fri, 29 Feb 2008 23:17:27 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4829/#comment-872</guid>
					<description>@v.dibenedetto:
Looks like the editor thought that '^' was a typo.  The command line should have read :
$ sudo apt-get install lamp-server^

Sorry about this.</description>
		<content:encoded><![CDATA[<p>@v.dibenedetto:<br />
Looks like the editor thought that &#8216;^&#8217; was a typo.  The command line should have read :<br />
$ sudo apt-get install lamp-server^</p>
<p>Sorry about this.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: v.dibenedetto</title>
		<link>http://www.linux-mag.com/id/4829/#comment-869</link>
		<pubDate>Thu, 28 Feb 2008 11:56:41 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4829/#comment-869</guid>
					<description>sudo apt-get install lamp-server doesn't work for me. Does it needs special repository to work?</description>
		<content:encoded><![CDATA[<p>sudo apt-get install lamp-server doesn&#8217;t work for me. Does it needs special repository to work?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: nijaba</title>
		<link>http://www.linux-mag.com/id/4829/#comment-864</link>
		<pubDate>Sat, 23 Feb 2008 14:27:58 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4829/#comment-864</guid>
					<description>Thanks for your very usefull comments.  As we are working on v8.04 of JeOS, we are currently rewriting this article and will publish it soon after release in the Ubuntu Wiki.  We'll make sure to address your  remarks and you'll have the opportunity to do some fixing yourself if you feel like it.

Regarding the issues you may have with Ubuntu JeOS, it would be very usefull if you could report them in our bugtracking tool at https://bugs.launchpad.net/ubuntu-jeos/ as Karsten did lately with bug #192771, reporting the WMWare tool installation problems (which brought me here, by the way, as I am not reading my own article every day ;).

Again, thanks for you remarks,

Nick</description>
		<content:encoded><![CDATA[<p>Thanks for your very usefull comments.  As we are working on v8.04 of JeOS, we are currently rewriting this article and will publish it soon after release in the Ubuntu Wiki.  We&#8217;ll make sure to address your  remarks and you&#8217;ll have the opportunity to do some fixing yourself if you feel like it.</p>
<p>Regarding the issues you may have with Ubuntu JeOS, it would be very usefull if you could report them in our bugtracking tool at <a href="https://bugs.launchpad.net/ubuntu-jeos/" rel="nofollow">https://bugs.launchpad.net/ubuntu-jeos/</a> as Karsten did lately with bug #192771, reporting the WMWare tool installation problems (which brought me here, by the way, as I am not reading my own article every day ;).</p>
<p>Again, thanks for you remarks,</p>
<p>Nick
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: dankegel</title>
		<link>http://www.linux-mag.com/id/4829/#comment-859</link>
		<pubDate>Thu, 21 Feb 2008 20:15:03 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4829/#comment-859</guid>
					<description>Yeah, it took me a while to figure out how to
shrink my .vmdk's.  I describe the steps at
http://kegel.com/linux/jeos-vmware-player-howto.html
but in short, it's
1. delete unneeded files (and I show which ones)
2. copy to a fresh filesystem (a bit more effective
than the zero copy trick you link to)
3. compress with 7zip (yeah, I know, it's a wierd tool, but it compresses .vmdk's much better than
anything else I've tried).
My vanilla jeos gutsy image is down to 80MB now!</description>
		<content:encoded><![CDATA[<p>Yeah, it took me a while to figure out how to<br />
shrink my .vmdk&#8217;s.  I describe the steps at<br />
<a href="http://kegel.com/linux/jeos-vmware-player-howto.html" rel="nofollow">http://kegel.com/linux/jeos-vmware-player-howto.html</a><br />
but in short, it&#8217;s<br />
1. delete unneeded files (and I show which ones)<br />
2. copy to a fresh filesystem (a bit more effective<br />
than the zero copy trick you link to)<br />
3. compress with 7zip (yeah, I know, it&#8217;s a wierd tool, but it compresses .vmdk&#8217;s much better than<br />
anything else I&#8217;ve tried).<br />
My vanilla jeos gutsy image is down to 80MB now!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Manish Kochar</title>
		<link>http://www.linux-mag.com/id/4829/#comment-801</link>
		<pubDate>Wed, 06 Feb 2008 06:59:27 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4829/#comment-801</guid>
					<description>Somebody recently egged me to lookup "jeos", as I am  looking to build a VM appliance. Like most others, I eventually landed on this page. My advice for anybody who's making a maiden experiment with building VM appliance, THIS is the place guys. Nick &#38; Soren have written a great "step-by-step howto" here. 

Jeos, by itself is very well built, and lives upto it's claimed strengths, so if you can accept its admitted lacunae, it definitely is the best platform to build your VM appliance. Jeos is also a great place to begin with, if you are looking to experiment with truly debian lineage of linux.

I have personally checked out the stuff built by others. Most of the Linux OS distributed as a VM appliance, are vulgarly "obese" compared to Jeos. Most irritatingly, you have to install atleast one email server and client (sic) to properly install the base OS! But, Jeos has been built rather intelligently, and the usually required packages have been carefully built to use as few dependencies as possible. This is because, most of the other distros have merely rehashed their existing distros into a VM image, to simply show-case the included goodies. Jeos on the other hand has been carefully built, keeping the VM appliance developers in mind.
So all my votes go to Jeos, alongwith a lot of thanks to the Jeos team.

A few things that Nick &#38; Soren missed out on -

1. Novice developers, who may be migrating from other distros may have been more comfortable with a few links that helped them understand apt-get / aptitude.

2. VM appliance first timers could be a little shocked to note that their eforts of appliance building could result in really huge vmdk files. A few tricks like the one documented here http://h0bbel.p0ggel.org/shrinking-vmdk-files
should help. And the users should take heart, from the fact that, even if post-optimisation, if the vmdk files look rather too huge to upload / download, tar / gzip-ing  them will make them comfortably small tar.gz packages. I do wish Nick &#38; Soren do a follow up on this article to include tips and tricks for such things too.

So all of you fellow developers, if you wanted to build your VM appliance, read the above article a couple of times, and calmly go step-by-step.</description>
		<content:encoded><![CDATA[<p>Somebody recently egged me to lookup &#8220;jeos&#8221;, as I am  looking to build a VM appliance. Like most others, I eventually landed on this page. My advice for anybody who&#8217;s making a maiden experiment with building VM appliance, THIS is the place guys. Nick &amp; Soren have written a great &#8220;step-by-step howto&#8221; here. </p>
<p>Jeos, by itself is very well built, and lives upto it&#8217;s claimed strengths, so if you can accept its admitted lacunae, it definitely is the best platform to build your VM appliance. Jeos is also a great place to begin with, if you are looking to experiment with truly debian lineage of linux.</p>
<p>I have personally checked out the stuff built by others. Most of the Linux OS distributed as a VM appliance, are vulgarly &#8220;obese&#8221; compared to Jeos. Most irritatingly, you have to install atleast one email server and client (sic) to properly install the base OS! But, Jeos has been built rather intelligently, and the usually required packages have been carefully built to use as few dependencies as possible. This is because, most of the other distros have merely rehashed their existing distros into a VM image, to simply show-case the included goodies. Jeos on the other hand has been carefully built, keeping the VM appliance developers in mind.<br />
So all my votes go to Jeos, alongwith a lot of thanks to the Jeos team.</p>
<p>A few things that Nick &amp; Soren missed out on -</p>
<p>1. Novice developers, who may be migrating from other distros may have been more comfortable with a few links that helped them understand apt-get / aptitude.</p>
<p>2. VM appliance first timers could be a little shocked to note that their eforts of appliance building could result in really huge vmdk files. A few tricks like the one documented here <a href="http://h0bbel.p0ggel.org/shrinking-vmdk-files" rel="nofollow">http://h0bbel.p0ggel.org/shrinking-vmdk-files</a><br />
should help. And the users should take heart, from the fact that, even if post-optimisation, if the vmdk files look rather too huge to upload / download, tar / gzip-ing  them will make them comfortably small tar.gz packages. I do wish Nick &amp; Soren do a follow up on this article to include tips and tricks for such things too.</p>
<p>So all of you fellow developers, if you wanted to build your VM appliance, read the above article a couple of times, and calmly go step-by-step.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: arosiqueh</title>
		<link>http://www.linux-mag.com/id/4829/#comment-798</link>
		<pubDate>Fri, 01 Feb 2008 17:24:02 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4829/#comment-798</guid>
					<description>I've got the very same error trying to install vmware-tools in Ubuntu JeOS.

The host is VMware workstation 6.0 runing in Linux.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve got the very same error trying to install vmware-tools in Ubuntu JeOS.</p>
<p>The host is VMware workstation 6.0 runing in Linux.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: vmboi</title>
		<link>http://www.linux-mag.com/id/4829/#comment-796</link>
		<pubDate>Tue, 29 Jan 2008 08:46:01 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4829/#comment-796</guid>
					<description>followed your guide, up until the point where VMware-tools are to be installed, and I get the following error:
The following VMware kernel modules have been found on your system that were
not installed by the VMware Installer.  Please remove them then run this
installer again.

vmxnet
vmblock
vmmemctl
vmhgfs

Execution aborted.

The Host is VMware Workstation 6.0 running in Windows</description>
		<content:encoded><![CDATA[<p>followed your guide, up until the point where VMware-tools are to be installed, and I get the following error:<br />
The following VMware kernel modules have been found on your system that were<br />
not installed by the VMware Installer.  Please remove them then run this<br />
installer again.</p>
<p>vmxnet<br />
vmblock<br />
vmmemctl<br />
vmhgfs</p>
<p>Execution aborted.</p>
<p>The Host is VMware Workstation 6.0 running in Windows
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Corne Beerse</title>
		<link>http://www.linux-mag.com/id/4829/#comment-795</link>
		<pubDate>Mon, 28 Jan 2008 10:35:24 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4829/#comment-795</guid>
					<description>It is clearly stated that a jeos-guest needs ide-disks and cannot coop with scsi disks. That indicates for me it does not work on VMWare ESX, since guests on ESX only get scsi-disks and no ide-disks...

Can we expect that the next ubuntu release has an option on the server-installation to get a jeos system?</description>
		<content:encoded><![CDATA[<p>It is clearly stated that a jeos-guest needs ide-disks and cannot coop with scsi disks. That indicates for me it does not work on VMWare ESX, since guests on ESX only get scsi-disks and no ide-disks&#8230;</p>
<p>Can we expect that the next ubuntu release has an option on the server-installation to get a jeos system?
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
