public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Jason Pyeron" <jpyeron@pdinc.us>
To: <cygwin@cygwin.com>
Subject: RE: [cygwin] Re: virtual box shares are visible in the window, but not in an ssh session
Date: Mon, 17 Aug 2020 18:21:44 -0400	[thread overview]
Message-ID: <075a01d674e4$ca777440$5f665cc0$@pdinc.us> (raw)
In-Reply-To: <546179025.20200818001544@yandex.ru>

> From: Andrey Repin
> Sent: Monday, August 17, 2020 5:16 PM
> 
<snip/>
> > E: on /cygdrive/e type vboxsharedfolderfs
> > (binary,posix=0,user,noumount,auto)
> 
> Don't map shares to disk letters.
> It's that simple.
> 
<snip/>
> > This is in the remote ssh:
> > $ df
> > Filesystem     1K-blocks     Used Available Use% Mounted on
> > C:/cygwin64     51856440 45549844   6306596  88% /
> > D:                 48666    48666         0 100% /cygdrive/d
> 
> Indeed, logging in via SSH, you get a separate session, in which your drives
> aren't mapped.
> See above, drop this poor habit of mapping them to letters.
> Use UNC paths directly or symlink them at convenient locations.

In my experience it is not that simple, the UNC will still likely have access issues, hence my request for tests.

We typically use the fstab to mount them in Cygwin, since things like git misbehave with all the slashes. But even then if the user context (due to admin or AD) is wonky - no access.


  reply	other threads:[~2020-08-17 22:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-17 15:36 marty leisner
2020-08-17 16:03 ` Eliot Moss
2020-08-17 16:11   ` marty leisner
2020-08-17 16:32     ` Eliot Moss
2020-08-17 21:15     ` Andrey Repin
2020-08-17 22:21       ` Jason Pyeron [this message]
2020-08-17 16:15   ` [cygwin] " Jason Pyeron
2020-08-17 16:36     ` Eliot Moss

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='075a01d674e4$ca777440$5f665cc0$@pdinc.us' \
    --to=jpyeron@pdinc.us \
    --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).