Date: Sun, 20 Feb 2000 12:24:28 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT bigfoot DOT com>, djgpp-workers AT delorie DOT com
Subject: Re: fileutils mkdir gotcha
In-Reply-To: <Pine.SUN.3.91.1000220115846.25009t@is>
Message-ID: <Pine.SUN.3.91.1000220122139.25009x-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 20 Feb 2000, I wrote:

> On Sat, 19 Feb 2000, Mark E. wrote:
> 
> > I would suggest modifying 'mkdir.c' check the result of _put_path for 
> > '/dev' and '/dev/env' and set errno to EEXIST (and return -1) for these 
> > two cases.
> 
> I think /dev should be left alone.
> 
> > This would in turn require a small change to _put_path2 to  
> > prevent '/dev/env' from turning into 'env' like it currently does.
> 
> Please send in a patch for preventing /dev/env from being created.

On second thought, if we prevent /dev/env from being created, no matter 
where, some program might go ahead and stat it, in which case it will get 
errors.  Perhaps we should leave things as they are, after all...  Or, 
better yet, make sure /dev/env without anything else gets treated as a 
normal file/directory, i.e. in this case, /dev/env will actually be 
created.