<?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 My Linux Way</title>
	<atom:link href="http://www.mylinuxway.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mylinuxway.com</link>
	<description>Newbie start learning Linux from scratch</description>
	<lastBuildDate>Wed, 03 Mar 2010 18:12:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Top 10 Pretty Linux Desktop by Stephen</title>
		<link>http://www.mylinuxway.com/top-10-pretty-linux-desktop/comment-page-1/#comment-86</link>
		<dc:creator>Stephen</dc:creator>
		<pubDate>Wed, 03 Mar 2010 18:12:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.mylinuxway.com/top-10-pretty-linux-desktop/#comment-86</guid>
		<description>I really like the first one. :]</description>
		<content:encoded><![CDATA[<p>I really like the first one. :]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to kill &quot;nasty&quot; PID process? by A smart way to do process killing &#124; My Linux Way</title>
		<link>http://www.mylinuxway.com/how-to-kill-nasty-pid-process/comment-page-1/#comment-47</link>
		<dc:creator>A smart way to do process killing &#124; My Linux Way</dc:creator>
		<pubDate>Mon, 01 Jun 2009 02:42:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.mylinuxway.com/how-to-kill-nasty-pid-process/#comment-47</guid>
		<description>[...] has been a while I have been using kill command to stop the non responsive running process. But until yesterday then I found out there is a much simple linux command that can do the job of [...]</description>
		<content:encoded><![CDATA[<p>[...] has been a while I have been using kill command to stop the non responsive running process. But until yesterday then I found out there is a much simple linux command that can do the job of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Compiz blacklisted Graphic Cards by Strawberry Utopia &#187; Blog Archive &#187; In which Lucy fixes her Compiz</title>
		<link>http://www.mylinuxway.com/compiz-blacklisted-graphic-cards/comment-page-1/#comment-43</link>
		<dc:creator>Strawberry Utopia &#187; Blog Archive &#187; In which Lucy fixes her Compiz</dc:creator>
		<pubDate>Mon, 20 Apr 2009 13:31:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.mylinuxway.com/compiz-blacklisted-graphic-cards/#comment-43</guid>
		<description>[...] to this guy.  [...]</description>
		<content:encoded><![CDATA[<p>[...] to this guy.  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Linux Folder System by Система каталогов Linux &#124; FlyCat.Info КОТорый летает ,,,^o o^,,,</title>
		<link>http://www.mylinuxway.com/linux-folder-system/comment-page-1/#comment-39</link>
		<dc:creator>Система каталогов Linux &#124; FlyCat.Info КОТорый летает ,,,^o o^,,,</dc:creator>
		<pubDate>Wed, 11 Feb 2009 05:19:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.mylinuxway.com/linux-folder-system/#comment-39</guid>
		<description>[...] Linux Folder System &#124; My Linux Way. [...]</description>
		<content:encoded><![CDATA[<p>[...] Linux Folder System | My Linux Way. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Linux Folder System by file system in linux &#171; Jacobian</title>
		<link>http://www.mylinuxway.com/linux-folder-system/comment-page-1/#comment-31</link>
		<dc:creator>file system in linux &#171; Jacobian</dc:creator>
		<pubDate>Mon, 18 Aug 2008 04:01:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.mylinuxway.com/linux-folder-system/#comment-31</guid>
		<description>[...] clipped from www.mylinuxway.com [...]</description>
		<content:encoded><![CDATA[<p>[...] clipped from <a href="http://www.mylinuxway.com" rel="nofollow">http://www.mylinuxway.com</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How Rename Your Partition Volume Label by devvrath</title>
		<link>http://www.mylinuxway.com/how-rename-your-partition-volume-label/comment-page-1/#comment-14</link>
		<dc:creator>devvrath</dc:creator>
		<pubDate>Thu, 03 Apr 2008 11:21:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.mylinuxway.com/how-rename-your-partition-volume-label/#comment-14</guid>
		<description>&lt;code&gt;UUID=2437-F256 /media/c vfat auto,rw,users,uid=1000,gid=1000,utf8,umask=000,sync 0 0&lt;/code&gt;

this is how my fstab looks like in hardy and it was same in gusty.

in gusty, it used to show partition by its name &quot;c&quot; , &quot;d&quot; etc on my desktop,
but in hardy, it shows the hard disk size as name  , which is annoying
as i have all partition of same size.

thanks</description>
		<content:encoded><![CDATA[<p><code>UUID=2437-F256 /media/c vfat auto,rw,users,uid=1000,gid=1000,utf8,umask=000,sync 0 0</code></p>
<p>this is how my fstab looks like in hardy and it was same in gusty.</p>
<p>in gusty, it used to show partition by its name &#8220;c&#8221; , &#8220;d&#8221; etc on my desktop,<br />
but in hardy, it shows the hard disk size as name  , which is annoying<br />
as i have all partition of same size.</p>
<p>thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Solution for Miro&#8217;s Segmentation fault by libxine1 incompatible causing Miro 1.2 crashed &#124; My Linux Way</title>
		<link>http://www.mylinuxway.com/solution-for-miros-segmentation-fault/comment-page-1/#comment-12</link>
		<dc:creator>libxine1 incompatible causing Miro 1.2 crashed &#124; My Linux Way</dc:creator>
		<pubDate>Wed, 26 Mar 2008 16:07:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.mylinuxway.com/solution-for-miros-segmentation-fault/#comment-12</guid>
		<description>[...] I have solved my problem with Miro, now it comes another new issue. The problem occurred because Ubuntu has updated the libxine to [...]</description>
		<content:encoded><![CDATA[<p>[...] I have solved my problem with Miro, now it comes another new issue. The problem occurred because Ubuntu has updated the libxine to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Frustrating Mounting Problem by gmarian</title>
		<link>http://www.mylinuxway.com/frustrating-mounting-problem/comment-page-1/#comment-10</link>
		<dc:creator>gmarian</dc:creator>
		<pubDate>Sun, 20 Jan 2008 16:50:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.mylinuxway.com/frustrating-mounting-problem/#comment-10</guid>
		<description>The problem has to do with permissions.  The partition is mounted by root, and so root has the read-write permission.

To see what I mean:

&lt;code&gt;ls -l /media&lt;/code&gt;

Solution:

&lt;code&gt;sudo chmod 777 /media/Zzz&lt;/code&gt;

This will change the permissions so that anyone can read or write to it.  Do it after mounting the partition.  (So, if you were re-creating this setup, use this command after the &quot;sudo mount -a&quot; command.)



The rest of this post is mostly for multi-user systems:

Now, you might be thinking that this is dangerous.  Anyone can write to that partition.  Well, yes and no.  

Since you&#039;re using FAT32 for this partition, there isn&#039;t a way to set file permissions.  So, that&#039;s basically the only way to use this type of file system.  If you had multiple users logging into this computer (like if it was a server), everyone would have full access to any file on the FAT32 partition.

If you were using a Linux partition type (like ext3) then, everyone would have access to the partition itself.  They&#039;d be able to create files and directories.  However, since the file system understands Linux file permissions, it isn&#039;t like using the FAT32 file system.  The user who created the file/directory is set as the owner and so has control over the permissions.  This way, any user on the system can use this partition, but they won&#039;t be able to access other user&#039;s stuff on the partition, unless those users change the permissions to allow others access.



There&#039;s nothing wrong with doing what you have done, for the typical desktop installation.  In fact, I&#039;m guessing that you&#039;re dual-booting and using this partition to allow you to transfer files between Linux and Windows.</description>
		<content:encoded><![CDATA[<p>The problem has to do with permissions.  The partition is mounted by root, and so root has the read-write permission.</p>
<p>To see what I mean:</p>
<p><code>ls -l /media</code></p>
<p>Solution:</p>
<p><code>sudo chmod 777 /media/Zzz</code></p>
<p>This will change the permissions so that anyone can read or write to it.  Do it after mounting the partition.  (So, if you were re-creating this setup, use this command after the &#8220;sudo mount -a&#8221; command.)</p>
<p>The rest of this post is mostly for multi-user systems:</p>
<p>Now, you might be thinking that this is dangerous.  Anyone can write to that partition.  Well, yes and no.  </p>
<p>Since you&#8217;re using FAT32 for this partition, there isn&#8217;t a way to set file permissions.  So, that&#8217;s basically the only way to use this type of file system.  If you had multiple users logging into this computer (like if it was a server), everyone would have full access to any file on the FAT32 partition.</p>
<p>If you were using a Linux partition type (like ext3) then, everyone would have access to the partition itself.  They&#8217;d be able to create files and directories.  However, since the file system understands Linux file permissions, it isn&#8217;t like using the FAT32 file system.  The user who created the file/directory is set as the owner and so has control over the permissions.  This way, any user on the system can use this partition, but they won&#8217;t be able to access other user&#8217;s stuff on the partition, unless those users change the permissions to allow others access.</p>
<p>There&#8217;s nothing wrong with doing what you have done, for the typical desktop installation.  In fact, I&#8217;m guessing that you&#8217;re dual-booting and using this partition to allow you to transfer files between Linux and Windows.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How Rename Your Partition Volume Label by Frustrating Mounting Problem &#124; My Linux Way</title>
		<link>http://www.mylinuxway.com/how-rename-your-partition-volume-label/comment-page-1/#comment-8</link>
		<dc:creator>Frustrating Mounting Problem &#124; My Linux Way</dc:creator>
		<pubDate>Sat, 05 Jan 2008 10:35:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.mylinuxway.com/how-rename-your-partition-volume-label/#comment-8</guid>
		<description>[...] time I thought I have managed to settle the drives mounting problem on Ubuntu. But later I realized it was not 100 [...]</description>
		<content:encoded><![CDATA[<p>[...] time I thought I have managed to settle the drives mounting problem on Ubuntu. But later I realized it was not 100 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to upgrade Ubuntu Feisty to Gutsy in 3 Steps? by Bacon</title>
		<link>http://www.mylinuxway.com/how-to-upgrade-ubuntu-feisty-to-gutsy-in-3-steps/comment-page-1/#comment-5</link>
		<dc:creator>Bacon</dc:creator>
		<pubDate>Fri, 19 Oct 2007 16:26:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.mylinuxway.com/how-to-upgrade-ubuntu-feisty-to-gutsy-in-3-steps/#comment-5</guid>
		<description>Nooooo don&#039;t do this, See the page at 
https://help.ubuntu.com/community/GutsyUpgrades</description>
		<content:encoded><![CDATA[<p>Nooooo don&#8217;t do this, See the page at<br />
<a href="https://help.ubuntu.com/community/GutsyUpgrades" rel="nofollow">https://help.ubuntu.com/community/GutsyUpgrades</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
