> ln -s nonexistent foo
> There could be some kind of -f, --follow option so that mkdir will
> create the directory pointed to. You'd probably use it together with
> -p. Then 'mkdir -fp' would be a way to try everything sensible to make
> sure the destination exists and can be used as a directory
[EMAIL PROTECTED] (Eric Blake) writes:
> After further thought and discussion on the cygwin list, I'm convinced
> that dd should default to binary mode (on non-ttys) on systems that
> have a distinct text mode.
That sounds reasonable, but I'm beginning to worry that the code is
becoming more ad-h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paul Eggert on 5/13/2005 4:55 PM:
> 2005-05-13 Paul Eggert <[EMAIL PROTECTED]>
>
> * m4/prereqs.m4 (gl_PREREQ): Require gl_UNLINKDIR.
> * src/remove.c: Include unlinkdir.h.
> (UNLINK_CAN_UNLINK_DIRS): Remove.
> (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paul Eggert on 5/16/2005 6:14 PM:
> This isn't just dd; it's cat, md5sum, split, etc. And I don't really
> understand how it works, or why some programs use binary modes and not
> others. For example, POSIX says that the input to "head"
I installed the following obvious fixes to unlinkdir.c that I
discovered when converting GNU tar to use this new file.
--- unlinkdir.c 14 May 2005 08:01:17 - 1.1
+++ unlinkdir.c 15 May 2005 05:57:31 - 1.2
@@ -59,11 +59,11 @@ cannot_unlink_dir (void)
}
# else
/* In
Eric Blake <[EMAIL PROTECTED]> writes:
> This change broke cygwin. Cygwin does not have struct dirent.d_type, so
> DT_IS_DIR is defined as do_not_use_this_macro. I think protecting this if
> statement with HAVE_STRUCT_DIRENT_D_TYPE, and letting cygwin fall through
> to the unlink, will fix the p
I'd like to suggest a possible new feature for mkdir and see what people
think of it.
% ln -s nonexistent foo
% mkdir foo
mkdir: cannot create directory `foo': File exists
There could be some kind of -f, --follow option so that mkdir will
create the directory pointed to. You'd probably use it to
