First, a few questions.
DO they only have one ISP? (inficad - which just happens to be mine also)
Do you want dial-on-demand? Always-on? random crashes? ;-)
(sorry, that 3rd choice is just hunger speaking ;-)
>
> a "product" when I see one, and this is not one. It
Hmm. Sounds like a RH-7.0 issue - I'm using mandrake
and it was pretty much trivial, as I recall.
> makes me sad, but dialup networking is the main use
> they want to make of this thing, and they don't want to
> hack root each time they dial in.
>
> So I went the KDE route and it connected, but
> hung up immediately. Very Redmondian behavior.
Have you turned 'debug' on so you can see what
is happening in the chat script?
WARNING - Inficad does NOT present a 'normal'
login prompt - there is NO trailing ':' - you
will fail miserably if you look for 'login:'
(and I forget about 'password' or 'password:')
> activate interface". When I tried again, rp3
> reported a segmentation error.
Is anyone else usin gRH7.0? I'm not using rp3 on
my mandrake system, which looks like this:
324 ? S 0:00 /sbin/ppp-watch ifcfg-ppp0 boot
19545 ttyS0 S 0:00 \_ /usr/sbin/pppd -detach lock modem crtscts asyncma
>
> Where are all those wizards Eric Raymond is always
> talking about?
Dunno if I'm a wizard, but I've managed to get connected to just
about all the idiot ISP's I've tried (I cannot remenber
any failures right now, but there may be one ;-)
> Any diagnostic advice will be greatly
> appreciated!
You want to be sure to run pppd and chat with the logging options
turned on so you can see what is going on between you and the ISP.
Output goes into /var/log/messages (usually - you MAY have to hack
your syslog.conf to get it there)
> Some specific info is appended to this
> message, regarding my rp3 attempts. If I can't get it
> done this coming weekend, I will allow this machine to
> be assimilated -- not my machine, not my decision.
Horrors! ;-)
> Thanks,
>
> Vic
>
> -------------------------------
>
> I don't know what version information would be helpful,
I'm a little disturbed by having two ppp interfaces, maybe
its a rp3 thing. Anybody else using rp3 and have a clue?
rusty
From Don Harrop <
don@nis4u.com> Tue Dec 5 19:33:58 2000
From: Don Harrop <
don@nis4u.com> (Don Harrop)
Date: Tue, 5 Dec 2000 12:33:58 -0700 (MST)
Subject: File Splitting
In-Reply-To: <
91304EB25636D411A1D10050BAAAFFC31A54@util1lxi.labxpress.com>
Message-ID: <
Pine.LNX.4.21.0012051220490.1120-100000@tech1.nis4u.com>
Lets say you have a 650meg ISO file you want to split up into 100meg
chunks.. Your file name is "linuxrocks.iso".. do this:
split -b 100000000 linuxrocks.iso linuxiso
This will create files named linuxisoaa, linuxisoab, linuxisoac,
linuxisoad, linuxisoae, linuxisoaf, linuxisoag.. each 95meg except for
the last one which just pickes up the remaining bytes.. Remember that
100,000,000 bytes doesn't quite equal 100meg. To put them back together
use:
cat linuxisoaa >> linuxrocks.iso
cat linuxisoab >> linuxrocks.iso
cat linuxisoac >> linuxrocks.iso
cat linuxisoad >> linuxrocks.iso
cat linuxisoae >> linuxrocks.iso
cat linuxisoaf >> linuxrocks.iso
cat linuxisoag >> linuxrocks.iso
depending on how many files you want to recombine it would be handy to
have a script to take care of that but I still haven't made the time to
write one yet.. It' not like I need to do this everyday.. Or deal with
that many files.. :-)
Don
On Mon, 4 Dec 2000, Justin Wilson wrote:
> Can you help me out?
>
> How are you splitting your files, I am in need of away to take a large plain
> text database report and break it up into small pieces.
>
> -Justin Wilson
> Lab Express Inc.
> justin@labxpress.com
>
From Don Harrop <
don@nis4u.com> Tue Dec 5 19:38:00 2000
From: Don Harrop <
don@nis4u.com> (Don Harrop)
Date: Tue, 5 Dec 2000 12:38:00 -0700 (MST)
Subject: File Splitting
In-Reply-To: <
14893.50.788953.537869@owmyeye.ugive.com>
Message-ID: <
Pine.LNX.4.21.0012051234580.1120-100000@tech1.nis4u.com>
So much for the script then.. :-) just splat it...
cat linuxiso* >> linuxrocks.iso
On Tue, 5 Dec 2000
sinck@ugive.com wrote:
>
>
> No, really, 'cat''s the circa 1988 approved way to do it, skip the
> script. The files are named asciibetically, IIRC, so cat
> doesn't have any issues.
>
(text/plain)