From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] drawterm dies when my mac book sleeps by 9p design?
Date: Sun, 6 Mar 2011 20:44:35 -0800 [thread overview]
Message-ID: <20110307044435.691F9B827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Sun, 06 Mar 2011 20:25:10 PST." <AANLkTinA-dmsSkzzBKY7jULXyetagdmabAXfdB8nU-bB@mail.gmail.com>
On Sun, 06 Mar 2011 20:25:10 PST ron minnich <rminnich@gmail.com> wrote:
> I used to work with David Mills, back long ago. He was one of the
> original Internet Buzzards, a really great guy. One of the many things
> he invented was NTP.
I wonder if he still owns a class B block of IP addresses :-)
[A friend did his PhD with him so we heard stories.]
> He would get pretty exercised about keep-alives. Felt that it was not
> the business of TCP to make these kinds of decisions. I can't remember
> if he actually called them an abomination, but at the same time, one
> was left with the feeling that he might have.
Agreed 100%. TCP is supposed to be resilient and not throw a
fit every time a link goes down.
> I never fully appreciated his argument until John DeGood described ham
> radio internet tcp sessions (this is also long ago) that would halt
> for days, then come back to life. That's pretty neat, and it can be
> hard if you are depending on keepalives. Just about any value you pick
> will be wrong.
A TCP connection is defined as <src-ip-addr, src-port,
dst-ip-addr, dst-port>. As long as these are in use, and a
path exists *when* a packet is to be sent, it is no one
else's business to consider it dead!
> So, yeah, they're out there and I guess nowadays everyone does them.
> Whether they are a good idea is somebody else's guess, I suppose. I
> note that today I slept my mac several times during this workshop and
> my ssh session was always there when I opened the lid again. That's
> nice.
I routinely leave ssh, xterm etc. alive for weeks on end and
my macbookpro puts itself to sleep a few times a day! Even
when I used to take my laptop to work, no connexion broke as
long as avoided accidentally typing in the window (which would
generate traffic).
next prev parent reply other threads:[~2011-03-07 4:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 0:35 Fernan Bolando
2011-03-07 2:34 ` erik quanstrom
2011-03-07 3:31 ` Bakul Shah
2011-03-07 3:34 ` erik quanstrom
2011-03-07 4:15 ` Bakul Shah
2011-03-07 4:17 ` erik quanstrom
2011-03-07 4:25 ` ron minnich
2011-03-07 4:44 ` Bakul Shah [this message]
2011-03-07 4:51 ` erik quanstrom
2011-03-07 5:38 ` Bakul Shah
2011-03-07 4:49 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-03-07 5:00 ` erik quanstrom
2011-03-07 8:54 ` Anthony Sorace
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=20110307044435.691F9B827@mail.bitblocks.com \
--to=bakul@bitblocks.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).