<?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"
	>
<channel>
	<title>Comments on: Locked out of My Home Directory</title>
	<atom:link href="http://www.elharo.com/blog/mac/2006/04/15/locked-out-of-my-home-directory/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.elharo.com/blog/mac/2006/04/15/locked-out-of-my-home-directory/</link>
	<description>Ranting and Raving</description>
	<pubDate>Tue, 02 Dec 2008 13:15:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Elliotte Rusty Harold</title>
		<link>http://www.elharo.com/blog/mac/2006/04/15/locked-out-of-my-home-directory/#comment-1202</link>
		<dc:creator>Elliotte Rusty Harold</dc:creator>
		<pubDate>Thu, 20 Apr 2006 13:46:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.elharo.com/blog/mac/2006/04/15/locked-out-of-my-home-directory/#comment-1202</guid>
		<description>The problem was indeed that the &lt;code&gt;uchg&lt;/code&gt; flag was set. Lord only knows how that happened. The Finder's Get Info window was not able to unlock it though. I had to use &lt;samp&gt;$ chflags -noucgh elharo&lt;/samp&gt; which did unlock it. Thanks for the tip!</description>
		<content:encoded><![CDATA[<p>The problem was indeed that the <code>uchg</code> flag was set. Lord only knows how that happened. The Finder&#8217;s Get Info window was not able to unlock it though. I had to use <samp>$ chflags -noucgh elharo</samp> which did unlock it. Thanks for the tip!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Thompson</title>
		<link>http://www.elharo.com/blog/mac/2006/04/15/locked-out-of-my-home-directory/#comment-1182</link>
		<dc:creator>Andrew Thompson</dc:creator>
		<pubDate>Mon, 17 Apr 2006 18:58:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.elharo.com/blog/mac/2006/04/15/locked-out-of-my-home-directory/#comment-1182</guid>
		<description>Or could you somehow have acquired an ACL on the folder?
Are they enabled on this volume?</description>
		<content:encoded><![CDATA[<p>Or could you somehow have acquired an ACL on the folder?<br />
Are they enabled on this volume?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg</title>
		<link>http://www.elharo.com/blog/mac/2006/04/15/locked-out-of-my-home-directory/#comment-1171</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Sun, 16 Apr 2006 16:52:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.elharo.com/blog/mac/2006/04/15/locked-out-of-my-home-directory/#comment-1171</guid>
		<description>One of the flags described for chflags(1) may be set, on the directory itself or a file.

The flags are normally hidden in an ls -l listing.  To reveal them, use ls -lo.

If a flag is set, and its name starts with 'u', it's easy to solve: use the chflags command to remove the flag.  If the flag is 'uchg', then you can turn it off in Finder's Get Info window: it's the "Locked" checkbox.

If a flag is set, and its name starts with 's', like 'schg' or 'sappnd', it's a lot harder to fix.  You'll have to reboot in single-user mode, remount file-systems as read/write, then navigate to the offender and apply 'chflags' to the file or dir.

By coincidence, I was mucking around with these flags yesterday, to see their effect, and your symptoms sound just like what I was observing.</description>
		<content:encoded><![CDATA[<p>One of the flags described for chflags(1) may be set, on the directory itself or a file.</p>
<p>The flags are normally hidden in an ls -l listing.  To reveal them, use ls -lo.</p>
<p>If a flag is set, and its name starts with &#8216;u&#8217;, it&#8217;s easy to solve: use the chflags command to remove the flag.  If the flag is &#8216;uchg&#8217;, then you can turn it off in Finder&#8217;s Get Info window: it&#8217;s the &#8220;Locked&#8221; checkbox.</p>
<p>If a flag is set, and its name starts with &#8217;s&#8217;, like &#8217;schg&#8217; or &#8217;sappnd&#8217;, it&#8217;s a lot harder to fix.  You&#8217;ll have to reboot in single-user mode, remount file-systems as read/write, then navigate to the offender and apply &#8216;chflags&#8217; to the file or dir.</p>
<p>By coincidence, I was mucking around with these flags yesterday, to see their effect, and your symptoms sound just like what I was observing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
