From: Sean (sean at domain binky.net)
Date: Fri 24 Sep 1999 - 02:32:07 IST
Mark Page wrote:
>
> Unfortunately I got no responses to my fetchmail/sendmail query - never
> the less I decided that perhaps the problems were being caused by using
> SuSE with so many apps. probably conflicting with one another. In the
> event I decided to re-install RedHat 5.2, hoping that I now had a little
> more knowledge in setting up a dial up account.
> Typing 'minicom' at the command line all I get is response 'device
> /dev/modem locked'. Which script do I alter to overcome? I know the
> modem works because it worked under SuSE.
get RH6.0 it gets over a lot. Modem configuration is easy with
netcfg,
even with 5.2 AFAIR. Get the updates as well, they (as usually)
improve
on a hell of a lot of things.
> I suppose the moral in this is that SuSE is dead easy for novices, and
> chock full of apps. ( maybe a bad thing), like myself but I don't
I've really got to try slackware again sometime. My first dist is
was,
and is still running on my first machine (umsdos too if you'd believe
that).
Ahh the days of a diskds, to the x disks...
floppy's you understand, not anything like the 'modern rubbish' like
CDROMS or zip disks.
> actually like the look and feel of it and suppose that there is no
> better feeling than having control over your machine rather than
> vice-versa.
> Would someone please give me a dig out here.
>
To your last request, fetchmail/sendmail. Whats sendmail doing ?
Usually (on my home machine anyways), sendmail tries (and fails)
to send mail (insert irony here) to sean at domain greebo.gofree.indigo.ie and
of course
fails miserably. Anybody spotting what Greebo relates to wins a
reply.
I solved this by using procmail (or deliver) to get the mail to the
local
user. (I've read the bat book and don't want to again, at least till
the
next edition comes out, any time now according to o'reilly).
Procmail will set the mail in /var/spool/mail/<username> or as
according
to ones filters. This has worked for me, though not really fully
tested.
usually unanswered requests to this list seem to be answered in three
ways:
1) A flurry of answers, usually going on to something entirely
different
(eg. see the current discussion on 'real drivers' in the linux
kernel list)
2) Not answered at all, since we (those in the know 8), know the
magic tricks
and are held to the magicians Oat of never reveling a secret.
(bull)
3) We're too lazy, then some one answers out of the blue.
personally, I'd go for 3 if more than two days unanswered.
Sean.
.
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:04:36 GMT