<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for What&#039;s Going On?</title>
	<atom:link href="http://wolf911.us/wgo/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://wolf911.us/wgo</link>
	<description>Knowledge is Power</description>
	<lastBuildDate>Sun, 13 May 2012 00:12:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>Comment on Sabayon &#8211; Virtualbox Installation Woos by eric</title>
		<link>http://wolf911.us/wgo/?p=699&#038;cpage=1#comment-23232</link>
		<dc:creator>eric</dc:creator>
		<pubDate>Sun, 13 May 2012 00:12:39 +0000</pubDate>
		<guid isPermaLink="false">http://wolf911.us/wgo/?p=699#comment-23232</guid>
		<description>All the mirrors for sabayon display no data available or check sum wrong for app-emulation/virtualbox-modules-4.1.12#3.3.0-sabayon. 

I had to download VirtualBox-4.1.14-77440-Linux_amd64.run from Oracle and install but it failed to build modules!

This is a lot of work which has been doomed from the start, why it not simply archived in entropy through sulfur.</description>
		<content:encoded><![CDATA[<p>All the mirrors for sabayon display no data available or check sum wrong for app-emulation/virtualbox-modules-4.1.12#3.3.0-sabayon. </p>
<p>I had to download VirtualBox-4.1.14-77440-Linux_amd64.run from Oracle and install but it failed to build modules!</p>
<p>This is a lot of work which has been doomed from the start, why it not simply archived in entropy through sulfur.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sabayon &#8211; Virtualbox Installation Woos by ReemZ</title>
		<link>http://wolf911.us/wgo/?p=699&#038;cpage=1#comment-22989</link>
		<dc:creator>ReemZ</dc:creator>
		<pubDate>Tue, 08 May 2012 02:01:10 +0000</pubDate>
		<guid isPermaLink="false">http://wolf911.us/wgo/?p=699#comment-22989</guid>
		<description>Spettro: no.
If you read more carefully, you&#039;ll see the article is about installing VB in Sabayon, not the other way around. In other words: Sabayon is the host.</description>
		<content:encoded><![CDATA[<p>Spettro: no.<br />
If you read more carefully, you&#8217;ll see the article is about installing VB in Sabayon, not the other way around. In other words: Sabayon is the host.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Argh at Udisks! Howto Gain Sanity Back by wolfden</title>
		<link>http://wolf911.us/wgo/?p=706&#038;cpage=1#comment-22631</link>
		<dc:creator>wolfden</dc:creator>
		<pubDate>Sun, 29 Apr 2012 21:41:50 +0000</pubDate>
		<guid isPermaLink="false">http://wolf911.us/wgo/?p=706#comment-22631</guid>
		<description>my bad, had a typo in there, all fixed</description>
		<content:encoded><![CDATA[<p>my bad, had a typo in there, all fixed</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sabayon &#8211; Virtualbox Installation Woos by Spettro</title>
		<link>http://wolf911.us/wgo/?p=699&#038;cpage=1#comment-22391</link>
		<dc:creator>Spettro</dc:creator>
		<pubDate>Mon, 23 Apr 2012 06:49:14 +0000</pubDate>
		<guid isPermaLink="false">http://wolf911.us/wgo/?p=699#comment-22391</guid>
		<description>I just installed Sabayon 8 in virtualbox 4.1.12 with 4.1.12 extension. 
Sabayon has got the kernel 3.2, and Virtualboxguestaddition version 4.1.10.
I cannot see the shared folders of the host Mac OS.
Do I have to follow your instructions to see the host shared folders?

Thank you in advance</description>
		<content:encoded><![CDATA[<p>I just installed Sabayon 8 in virtualbox 4.1.12 with 4.1.12 extension.<br />
Sabayon has got the kernel 3.2, and Virtualboxguestaddition version 4.1.10.<br />
I cannot see the shared folders of the host Mac OS.<br />
Do I have to follow your instructions to see the host shared folders?</p>
<p>Thank you in advance</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sabayon &#8211; Virtualbox Installation Woos by wolfden</title>
		<link>http://wolf911.us/wgo/?p=699&#038;cpage=1#comment-22329</link>
		<dc:creator>wolfden</dc:creator>
		<pubDate>Sat, 21 Apr 2012 15:47:13 +0000</pubDate>
		<guid isPermaLink="false">http://wolf911.us/wgo/?p=699#comment-22329</guid>
		<description>I don&#039;t know what has changed or how it was for sure before as I&#039;m not a big VB user myself.  This is first I have seen users mention it.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know what has changed or how it was for sure before as I&#8217;m not a big VB user myself.  This is first I have seen users mention it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sabayon &#8211; Virtualbox Installation Woos by patrick</title>
		<link>http://wolf911.us/wgo/?p=699&#038;cpage=1#comment-22324</link>
		<dc:creator>patrick</dc:creator>
		<pubDate>Sat, 21 Apr 2012 13:58:27 +0000</pubDate>
		<guid isPermaLink="false">http://wolf911.us/wgo/?p=699#comment-22324</guid>
		<description>Wlofden,  i know. That&#039;s why i wrote the first comment on your article., to warn others.

But i don&#039;t get it.  What has changed?
Afaik, the procedure on the wiki was always right.
In the past, installing VBox never pulled a new kernel, even when there was one available.    (please correct me if i&#039;m wrong)
And now VBox suddenly pulls a new kernel.</description>
		<content:encoded><![CDATA[<p>Wlofden,  i know. That&#8217;s why i wrote the first comment on your article., to warn others.</p>
<p>But i don&#8217;t get it.  What has changed?<br />
Afaik, the procedure on the wiki was always right.<br />
In the past, installing VBox never pulled a new kernel, even when there was one available.    (please correct me if i&#8217;m wrong)<br />
And now VBox suddenly pulls a new kernel.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sabayon &#8211; Virtualbox Installation Woos by stupot</title>
		<link>http://wolf911.us/wgo/?p=699&#038;cpage=1#comment-22288</link>
		<dc:creator>stupot</dc:creator>
		<pubDate>Fri, 20 Apr 2012 19:28:15 +0000</pubDate>
		<guid isPermaLink="false">http://wolf911.us/wgo/?p=699#comment-22288</guid>
		<description>Interesting.  I was thinking that even if VB had been on the iso, that an upgrade would still want to pull in a later kernel.  I definitely slightly misunderstood the complicatedness of the issue.</description>
		<content:encoded><![CDATA[<p>Interesting.  I was thinking that even if VB had been on the iso, that an upgrade would still want to pull in a later kernel.  I definitely slightly misunderstood the complicatedness of the issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sabayon &#8211; Virtualbox Installation Woos by wolfden</title>
		<link>http://wolf911.us/wgo/?p=699&#038;cpage=1#comment-22284</link>
		<dc:creator>wolfden</dc:creator>
		<pubDate>Fri, 20 Apr 2012 17:19:36 +0000</pubDate>
		<guid isPermaLink="false">http://wolf911.us/wgo/?p=699#comment-22284</guid>
		<description>Desired?  No, but entropy doesn&#039;t have the ability to check and see what the kernel version environment is and than apply the same version of modules.  If VB and modules were added to the initial ISOs than one wouldn&#039;t have this problem.  If you start to think about it, any initial module not installed before a new kernel is going to do this.  We would have to kick out a new release for every kernel change to avoid it.  VB just happens to be very popular so I foresee that one causing the most issues.

Fabio is aware of it and at this time unsure of how to avoid this.  I have stressed over and over in the past to our users that blindly updating your system is dangerous, one should always be aware of the changes that the package manager is going to perform.  People will throw back at me, well I shouldn&#039;t have to know or understand all that, and all I can think is well, good luck than.  It&#039;s no different than going to the doctor or mechanic, I want to know everything before I give the ok.

Anyway, kernels are always a sticky situation for people.

Patrick, I would do a equo upgrade and make sure I was current with the repo before doing a kernel switch.  I would feel much safer doing that, the lesser the changes with a kernel upgrade the better.</description>
		<content:encoded><![CDATA[<p>Desired?  No, but entropy doesn&#8217;t have the ability to check and see what the kernel version environment is and than apply the same version of modules.  If VB and modules were added to the initial ISOs than one wouldn&#8217;t have this problem.  If you start to think about it, any initial module not installed before a new kernel is going to do this.  We would have to kick out a new release for every kernel change to avoid it.  VB just happens to be very popular so I foresee that one causing the most issues.</p>
<p>Fabio is aware of it and at this time unsure of how to avoid this.  I have stressed over and over in the past to our users that blindly updating your system is dangerous, one should always be aware of the changes that the package manager is going to perform.  People will throw back at me, well I shouldn&#8217;t have to know or understand all that, and all I can think is well, good luck than.  It&#8217;s no different than going to the doctor or mechanic, I want to know everything before I give the ok.</p>
<p>Anyway, kernels are always a sticky situation for people.</p>
<p>Patrick, I would do a equo upgrade and make sure I was current with the repo before doing a kernel switch.  I would feel much safer doing that, the lesser the changes with a kernel upgrade the better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sabayon &#8211; Virtualbox Installation Woos by stupot</title>
		<link>http://wolf911.us/wgo/?p=699&#038;cpage=1#comment-22270</link>
		<dc:creator>stupot</dc:creator>
		<pubDate>Fri, 20 Apr 2012 14:34:54 +0000</pubDate>
		<guid isPermaLink="false">http://wolf911.us/wgo/?p=699#comment-22270</guid>
		<description>Is that really the desired behavior? I know equo upgrades shouldn&#039;t pull in kernels, but wouldn&#039;t having an older version of VirtualBox and doing and equo upgrade pull in this kernel?

Truthfully, I think the kernel-switcher functionality should be built into equo.  If equo is attempting to install a new kernel, it should prompt the user if they would like to switch to using that kernel and install all the lovely drivers and whatnot.

Another option would be to not switch grub to automatically boot a new kernel installed via equo and leave that up to the kernel-switcher.  Actually, I almost kind of like this option better.  But I don&#039;t know how feasible it is.</description>
		<content:encoded><![CDATA[<p>Is that really the desired behavior? I know equo upgrades shouldn&#8217;t pull in kernels, but wouldn&#8217;t having an older version of VirtualBox and doing and equo upgrade pull in this kernel?</p>
<p>Truthfully, I think the kernel-switcher functionality should be built into equo.  If equo is attempting to install a new kernel, it should prompt the user if they would like to switch to using that kernel and install all the lovely drivers and whatnot.</p>
<p>Another option would be to not switch grub to automatically boot a new kernel installed via equo and leave that up to the kernel-switcher.  Actually, I almost kind of like this option better.  But I don&#8217;t know how feasible it is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sabayon &#8211; Virtualbox Installation Woos by patrick</title>
		<link>http://wolf911.us/wgo/?p=699&#038;cpage=1#comment-22265</link>
		<dc:creator>patrick</dc:creator>
		<pubDate>Fri, 20 Apr 2012 13:24:44 +0000</pubDate>
		<guid isPermaLink="false">http://wolf911.us/wgo/?p=699#comment-22265</guid>
		<description>Don&#039;t know if it matters,
but (advanced)users with a Fresh installed KDE system, using the Official Sabayon 8 release of KDE (NOT the Daily iso) AND want the new kernel, need to first upgrade the system.
Because it&#039;s still shipped with KDE-4.7.4 , and is on sabayon-weekly repository, Kernel 3.3 is not yet in weekly repo.  
But if one decides to switch to the sabayonlinux.org repository, 
and doing a kernel-switch BEFORE upgrading the system, 
kernel-switcher  also  pulls the packages for KDE-4.8.2</description>
		<content:encoded><![CDATA[<p>Don&#8217;t know if it matters,<br />
but (advanced)users with a Fresh installed KDE system, using the Official Sabayon 8 release of KDE (NOT the Daily iso) AND want the new kernel, need to first upgrade the system.<br />
Because it&#8217;s still shipped with KDE-4.7.4 , and is on sabayon-weekly repository, Kernel 3.3 is not yet in weekly repo.<br />
But if one decides to switch to the sabayonlinux.org repository,<br />
and doing a kernel-switch BEFORE upgrading the system,<br />
kernel-switcher  also  pulls the packages for KDE-4.8.2</p>
]]></content:encoded>
	</item>
</channel>
</rss>

