[100142] in RedHat Linux List
Re: I'm dissapointed in 5.2
daemon@ATHENA.MIT.EDU (Matthew Saltzman)
Wed Nov 18 16:57:57 1998
From: Matthew Saltzman <mjs@math.clemson.edu>
Date: Wed, 18 Nov 1998 16:55:11 -0500 (EST)
To: redhat-list@redhat.com
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com
Doug Roberts <roberts@tsasa.lanl.gov> wrote:
>After 5 days of encountering bugs in 5.2, I convinced that this
>distribution was released way prematurely. Here's a short list of
>RedHat things that don't work as they should:
>[1 & 2 addressed elsewhere]
>
>3. Linuxconf. The network -> PPP -> Communication portion does not
> work. According to the documentation you can test the set-up by
> clicking on the "connect" button to see if the modem dials. It's
> broken, nothing happens.
Don't know about this problem. I assume you did manage to get it working.
> Linuxconf. Activating the ppp0 interface via the network portion of
> Linuxconf changes the mode of whatever cua /dev/modem is linked to
> to root only read/write permissions, even if you have specfied via
> linuxconf that any user is allowed to (de)activate the ppp0
> interface.
Why is this a problem? The way RedHat allows ordinary users to bring
network interfaces up and down is by a wrapper program that sets the
uid. My /dev/cua* and /dev/ttyS* devices are only writable by root,
but the RedHat interface management scripts "ifup ppp0" and "ifdown
ppp0" work just fine for my ordinary userid.
You do need to get into the "RedHat spirit" of network management. If
you manage the interfaces entirely via Linuxconf or the control panel
or the scripts in /etc/sysconfig, then everything ought to work as
advertised. If you do *all* your network management by hand, things
will behave as you are used to. If you try to mix RedHat management
with the regular PPP stuff, you are likely to have problems.
>4. PPP. After configuring pppd with proper settings for netmask, mru,
> crtscts, defaultroute, modem, and detach, the ppp0 interface was
> extremely slow to to numerous dropped RX packets. This could be due
> to the pcmcia problems described above.
If you are sure that this is only a 5.2 custom kernel problem, and
since we know that RedHat is aware of this issue, I don't know what
else to suggest but wait and see if it is fixed when the pcmcia issue
is fixed. For the record, my desktop (running stock 5.1 with all
updates) has not exhibited any problem.
Matthew Saltzman
Clemson University Math Sciences
mjs@clemson.edu
http://www.math.clemson.edu/~mjs
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com http://archive.redhat.com
To unsubscribe: mail redhat-list-request@redhat.com with
"unsubscribe" as the Subject.
