public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: dahms@ifk20.mach.uni-karlsruhe.de
To: jqb@netcom.com
Cc: gnu-win32@cygnus.com, dahms@ifk20.mach.uni-karlsruhe.de
Subject: Re: Buglist
Date: Mon, 07 Apr 1997 18:53:00 -0000	[thread overview]
Message-ID: <009B274E.91EFDCE0.13508@ifk20.mach.uni-karlsruhe.de> (raw)

Hi Jim, you wrote:

: Under win32, paths consisting of only dots, with the exception of .
: and .., are illegal.  This is along with a number of other
: illegal characters and combinations, including such winners as
: mkdir -p "abcde/xyz/con/ffo/bar" hanging as it tries to do I/O to the
: "con" device; lots of fun when you untar a 500Meg tar tape from
: some other system that was designed on less ad hoc principles.

Yeah, a collegue of mine tried to get com961231.tgz via FTP, after a while
I figured out that specifying a harmless local filename works (I guess there's
no box with >100000 serial ports on the market 8-).

Did you finally got cygwin tar to work? Another collegue gave my an NT tar
binary but which handles only a blocksize of 512, not the standard 10kB,
while the manual of our fine new DDS3 says it works best with 32kB...
And is there any decent "mt" for NT, preferably with sources to spy at?


Bye, Heribert (dahms@ifk20.mach.uni-karlsruhe.de)
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

             reply	other threads:[~1997-04-07 18:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-04-07 18:53 dahms [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-04-07 12:09 Buglist Stephan Mueller
1997-04-04 16:05 Buglist Scott Mintz
1997-04-04 14:27 Buglist dahms
1997-04-04 19:15 ` Buglist Jim Balter
1997-04-03 17:13 Buglist Tim Iverson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=009B274E.91EFDCE0.13508@ifk20.mach.uni-karlsruhe.de \
    --to=dahms@ifk20.mach.uni-karlsruhe.de \
    --cc=gnu-win32@cygnus.com \
    --cc=jqb@netcom.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).