Day Brown wrote:

>  Bob George wrote:
>
> > Here we go again: What is it you want to do?
>
>
>  Try to stay flexible. try to retain as much functionality of the
>  hardware I already have.

Well, for your dial-up, email-only alternative network scheme, your 486
running even an older Linux system, updated as necessary, would work
fine. If you're just talking to a partial mesh of compatriots
(conspirators?), then you could easily set up uucp to dial one, some or
all of the "Intermesh" on a schedule according to rates and preferences,
or simply whenever there's something outbound (trusting them to call YOU
for any inbound.) You don't need to reinvent anything, and any mix of
old and new Internet-standards based apps will work for reading and
composing messages and "news." One or more of the 'mesh crowd with good
Internet connectivity could offer up gateway services between your
multitude and the rest of the Internet world, even doing spam filtering
and the like. This all exists and works just dandy, but of course you
need to find other like-minded folk to make it actually happen.

For dial-up access to an existing provider that insists on advanced
authentication options, just update any workable Linux distribution on
that same 486 with reasonably current ppp software and you're in
business. No changes to hardware required here either.

For your wild-eyed, damn the FCC wireless scheme, as you repeatedly
state, if you can find other individuals with an equal disregard for the
law and legitimate bandwidth users, by all means, do it. Just don't
expect applause from the masses, and heed the cautions of the
isp-wireless list: rocks ain't trees, and if you're in the hills, best
account for those too.

For any genuine interest in using LEGITIMATE wireless, uucp etc. was
long ago adapted by the ham crowd. How your low bandwidth usage varies
from theirs, I've yet to understand but they've been doing exactly what
you insist on doing illegally quite legally and successfully since the
mid-1980's (Karn's KA9Q was a part of this.) I well recall guys in
Germany doing data at 1,200 bps "for free" back when long distance calls
were prohibitive and general Internet connectivity only a dream. Again,
old news. It's been done. I certainly haven't kept up, but a quick
google shows that these guys have never ceased being active, and could
probably easily build the alternative network you so desire (and already
have.)

>  try to see which way the system is evolving, and what backup system
>  might be useful if it chokes on it's own bloatware.


Don't update to a newer distribution when you run into a stumbling block
then. Figure out what's not working, and make the adjustments. If you're
really the rugged survivalist you pose as, you would consider your
ability to actually maintain the system in the absence of an annual
distribution update as important as the hardware and operating system. A
box you can't fix yourself is useless if there's nobody around to snivel
to for help.

>  The Internet was setup by government to facilitate the functionality
>  of organizations.

Wrong. It was designed to provide a network to operate in the event of
total meltdown of centralized control. I would think that would be
appealing to you.

>  Be interesting to see what users would setup to maximize the
>  functionality for users... of the stuff we already have, and the most
>  cost effective way of coping with the evolution of components and
>  systems. Big Blue, Big Bill, and the other powers that be have
>  created enemies, as evidenced by sabotage software. Be nice to have
>  something setup, out of the way, that we users can still use while
>  the struggle goes on around us.

Been done. All of it. Back in the 1980s. On pre-486 systems. At 1,200bps
and slower. Wireless. No need for the bloat of 16MB RAM and a 486 and
any stinkin' TV frequencies. No need for connections to any central
network, unless you want it.

I suspect you prefer to rant against government and what you don't
understand rather than work to actually build any sort of alternate network.

- Bob

Reply via email to