9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Fwd: ubiquitous environment?
Date: Sun,  4 Mar 2018 01:02:12 +0100	[thread overview]
Message-ID: <CAFSF3XPMie-J9GO4eUMZ1mNFQ-6ZiwXo8WE78oh=mnh+CWzZgg@mail.gmail.com> (raw)
In-Reply-To: <34985C61-FB8C-4EF9-BB1B-06D2D4CC7E39@quintile.net>

it just keeps on breaking. it does reconnect after you press cancel or
ok (i don't remember), but it always keeps a while and when you have
files open or transfers happening you have to start again when
everything below breaks.

On 3/4/18, Steve Simon <steve@quintile.net> wrote:
> i see.
>
> i would have thought/hoped that windows would remake the cifs session when
> windows comes out if standby, using cached credentials, so  other than being
> a bit slow to start,  cifs to the plan9 server should come back.
>
> i guess i am missing something.
>
> -Steve
>
>
> On 3 Mar 2018, at 23:32, hiro <23hiro@gmail.com> wrote:
>
>>> also, i would have thought you could build a windows drawterm which also
>>> included the code from exportfs so you could use 9fs and aan to get at
>>> the
>>> files on your windows box.
>>
>> we don't use exportfs for this any more, but yes, i already use the
>> equivalent feature for this direction.
>> i want to also be able to use the windows file explorer to access the
>> 9front server through drawterm somehow (opposite direction), because
>> then the cifs mount doesn't get killed by window's inability to keep
>> the network connections running. 127.0.0.1 (drawterm) should always
>> stay up, and drawterm would take care of the rest :)
>
>
>



  reply	other threads:[~2018-03-04  0:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOEdRO14fa3VT_dWatAo66aB3YD530Q3uK=KC2DjJ2T5wjQ1wQ@mail.gmail.com>
2018-03-03 16:22 ` Rudolf Sykora
2018-03-03 17:41   ` hiro
2018-03-03 19:13     ` Steve Simon
2018-03-03 19:18       ` Francisco J Ballesteros
2018-03-03 19:23         ` Steve Simon
2018-03-03 19:27           ` Francisco J Ballesteros
2018-03-03 20:17       ` Kurt H Maier
2018-03-03 23:32       ` hiro
2018-03-03 23:46         ` Steve Simon
2018-03-04  0:02           ` hiro [this message]
2018-03-04  0:03             ` hiro
2018-03-03 23:24   ` Skip Tavakkolian
2018-03-03 23:40     ` hiro
2018-03-03 23:43     ` hiro
2018-03-04  0:10       ` Skip Tavakkolian
2018-03-03 23:56   ` cigar562hfsp952fans
2018-03-04  7:17     ` Francisco J Ballesteros
2018-03-04  8:23       ` Ethan Grammatikidis
2018-03-04  8:57   ` Ethan Grammatikidis
2018-03-08 12:38     ` Rudolf Sykora
2018-03-08 19:19       ` FJ Ballesteros
2018-03-09  0:45         ` Aram Hăvărneanu
2018-03-09  5:50           ` Sean Callanan
2018-03-09  6:23           ` Francisco J Ballesteros
2018-03-08 23:29       ` 岡本健二

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='CAFSF3XPMie-J9GO4eUMZ1mNFQ-6ZiwXo8WE78oh=mnh+CWzZgg@mail.gmail.com' \
    --to=23hiro@gmail.com \
    --cc=9fans@9fans.net \
    /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 NNTP newsgroup(s).