public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Dr Bean <drbean@freeshell.org>
To: Dr Bean via Cygwin <cygwin@cygwin.com>
Subject: Re: Persistent and same Cygwin session for Windows login and ssh login?
Date: Sat, 19 Aug 2023 09:25:35 +0000	[thread overview]
Message-ID: <lgfe72bv4i7vfkywrb6cx77yiwcz3q6q4akhahpitap56fsdsn@foot3vmdie2s> (raw)
In-Reply-To: <l4z5bl3jzl2iekxcwydwz5jbideoiy2gp7zcfivfqum3gu4zij@xurgkvj6wfem>

On Thu, 17 Aug 2023, Dr Bean via Cygwin wrote:

> On Thu, 17 Aug 2023, Cedric Blancher via Cygwin wrote:
> 
> > Good evening!
> > 
> > How can I get a Cygwin session for one Windows login, and get the same
> > Cygwin session when I log into the same Windows machine via ssh?
> 
> 
> Following 
> https://learn.microsoft.com/ja-jp/windows-server/administration/openssh/openssh_server_configuration
> 
> and substituting cygwin bash's
> path for powershell's, I get
> a cygwin bash shell.
> 
> But $HOME is Window's and .bashrc
> is not executed.
> 
> Let me see if I can set HOME.

I appear to have answered a
question which wasn't asked,
how to get Microsoft's
implementation of sshd working.

i have run up against the problem 
of the OP, trying and failing
to reattach a detached screen
session over ssh.

Solving my own problem of wrong
HOME and no execution of bashrc,
a Windows batch file that sets HOME
and invokes bash with
interactive, login and rcfile
options did the trick.

But is there an official way
to run cygwin with MS's sshd?

> > Cedric Blancher <cedric.blancher@gmail.com>
> > [https://plus.google.com/u/0/+CedricBlancher/]
> > Institute Pasteur
> > 
> > -- 
> > Problem reports:      https://cygwin.com/problems.html
> > FAQ:                  https://cygwin.com/faq/
> > Documentation:        https://cygwin.com/docs.html
> > Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
> -- 
> Greg Matheson          Theory and practice. In theory, they are the same thing.
> http://drbean.sdf.org  In practice, they are different.
> drbean@freeshell.org   --https://quoteinvestigator.com/2018/04/14/theory/

  reply	other threads:[~2023-08-19  9:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17 17:30 Cedric Blancher
2023-08-17 21:38 ` Dr Bean
2023-08-19  9:25   ` Dr Bean [this message]
2023-08-18  8:47 ` Corinna Vinschen
2023-08-18 10:23   ` Thomas Wolff
2023-08-18 11:50     ` Corinna Vinschen

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=lgfe72bv4i7vfkywrb6cx77yiwcz3q6q4akhahpitap56fsdsn@foot3vmdie2s \
    --to=drbean@freeshell.org \
    --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).