linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James <james@piku.org.uk>
To: linux-admin <linux-admin@vger.kernel.org>
Subject: Re: what tech?
Date: Mon, 29 Apr 2002 18:03:44 +0100	[thread overview]
Message-ID: <20020429170344.GR23141@piku.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.10.10204290541510.16720-100000@yossarian.aniota.net>

On Mon, Apr 29, 2002 at 06:09:00AM -0700, terry white wrote:
| on "4-28-2002" "urgrue" writ:
| 
| : along normal copper wires
|   
|     a better bet would be coax ethernet.  if i recall correctly, longer
| runs possible using it.  i just checked, and 200M the limit.  this also
| reduces the wirecount to one.

Coax would probably also be dirt cheap since coax-based networking is
old tech now :) (although its used a lot in CCTV systems) Just mind its
minimum bending radius when bending it round things, a broken piece of
coax is a nightmare.

|     further, i seem to recall a system that superimposed the data on
| the power distribution system, and another that used existant phone
| lines.

The power one would only work if everything was on the same phase and
didn't go through any UPSs or filters.

Never heard of the phone one (well, it's called 'dsl'...) but I've
heard of the opposite - running a phone line and network down one piece
of cat5.

| from the sounds of it, neither of these applicable.  however, wireless
| might be a way to go.  that, of course introduces security issues ...

It also has problems going through solid objects like concrete floors
and walls.

-- 
I will not carve gods  
 
6AD6 865A BF6E 76BB 1FC2 | www.piku.org.uk/public-key.asc
E4C4 DEEA 7D08 D511 E149 | www.piku.org.uk wnzrf@cvxh.bet.hx (rot13'd)

  reply	other threads:[~2002-04-29 17:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-27 22:46 what tech? urgrue
2002-04-28  7:59 ` James
2002-04-29 13:09 ` terry white
2002-04-29 17:03   ` James [this message]
2002-04-29 20:02     ` Kyle

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=20020429170344.GR23141@piku.org.uk \
    --to=james@piku.org.uk \
    --cc=linux-admin@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 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).