Path: number1.nntp.dca.giganews.com!local01.nntp.dca.giganews.com!nntp.adelphia.com!news.adelphia.com.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 26 Oct 2005 21:08:18 -0500
Newsgroups: fidonet.linux
From: MARTIN_ATKINS@f140.n123.z1
Date: Sat, 22 Oct 2005 15:34:00 -0400
Subject: software for linspire
Message-ID: 
Organization: Try Our Web Based QWK: DOCSPLACE.ORG
 456
 205/1
 267/200
Lines: 23
NNTP-Posting-Host: 24.48.121.215
 properly
Xref: number1.nntp.dca.giganews.com fidonet.linux:28

-=> MARK LEWIS wrote to MARTIN ATKINS <=-

 WC> Heh. Both my Practical Peripherals and USR modems setup here and
 WC> connected no problem. The P.P. is only a 28,800 but the USR 56k
 WC> routinely connects at 49,333

 MA> Same here. I have used many Linux distros and none have not been
 MA> able to handle any of my Hayes modems connected to the serial port.
 MA> Some have wrongly linked /dev/modem to ttyS0 when the modem has
 MA> been on /dev/ttyS1 but that is easily fixed. I've never understood
 MA> why you need a symlink to point to the serial port anyway. ;)

 ML> so you can configure your programs and such to point to the one, never
 ML> changing symlink but you can change where the symlink points to if/when
 ML> you need to... this way, you're just changing one thing to point to the
 ML> new location rather than having to change all those program's
 ML> configs...

I know many uses for symlinks but i can't understand why you would
need /dev/modem to point to /dev/ttySx.

:-}