public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: what path to use that is not DOS??
Date: Wed, 08 Oct 2014 20:11:00 -0000	[thread overview]
Message-ID: <54359A6C.4030204@redhat.com> (raw)
In-Reply-To: <543596B3.1020705@tlinx.org>

[-- Attachment #1: Type: text/plain, Size: 914 bytes --]

On 10/08/2014 01:55 PM, Linda Walsh wrote:
> I get this message the 1st time logging in via 'rlogin':
> 
>  MS-DOS style path detected:
> /Windows/System32/cygwin/usr/spool/mail/Bliss/law
>  Preferred POSIX equivalent is:
> /Windows/System32/cygwin/usr/spool/mail/Bliss/law

Could any prefix of that path be a symlink with questionable contents?
For example, if /Windows is a symlink to 'c:/' instead of '/cygdrive/c',
that might explain the cryptic error message being reported on the
pre-symlink expansion name although the name being warned about is
post-symlink expansion.  At any rate, you are right that it is an
awkward message, so it would be nice to get to a root cause of what you
did that provoked it to make the message nicer, as well as letting you
fix your root cause.



-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]

  reply	other threads:[~2014-10-08 20:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08 19:56 Linda Walsh
2014-10-08 20:11 ` Eric Blake [this message]
2014-10-11 21:38   ` Linda Walsh
2014-10-13 16:26     ` Eric Blake
2014-10-08 20:15 ` Eric Blake
2014-10-08 22:08   ` login -p disabling leads to Windows failures -- as it expects its ENV to remain instact for new processes Linda Walsh

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=54359A6C.4030204@redhat.com \
    --to=eblake@redhat.com \
    --cc=cygwin@cygwin.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).