From: John Bak <bakj@gdinet.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] double gateway - new thread
Date: Fri, 31 Jan 2003 00:46:45 +0000 [thread overview]
Message-ID: <marc-lartc-104397410826394@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104397124523448@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 356 bytes --]
At 05:58 PM 1/30/2003, Paul Evans wrote:
<< Snip >>
>
>I am doing it from the *outside* via ssh, which makes it a little more
>difficult, since when I mess up I lose access until I can get someone to
>restart the network without my changes...
Might I suggest mgetty and a POTS line so you can "phone home" and
undo the damage yourself. ;-)
John
<*>
next prev parent reply other threads:[~2003-01-31 0:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 23:58 [LARTC] double gateway - new thread Paul Evans
2003-01-31 0:33 ` William L. Thomson Jr.
2003-01-31 0:46 ` John Bak [this message]
2003-01-31 4:39 ` William L. Thomson Jr.
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=marc-lartc-104397410826394@msgid-missing \
--to=bakj@gdinet.com \
--cc=lartc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.