Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Redhat-list digest, Vol 1 #3954 - 15 msgs

0 views
Skip to first unread message

redhat-li...@redhat.com

unread,
Mar 7, 2002, 6:25:00 PM3/7/02
to
Send Redhat-list mailing list submissions to
redha...@redhat.com

To subscribe or unsubscribe via the World Wide Web, visit
https://listman.redhat.com/mailman/listinfo/redhat-list
or, via email, send a message with subject or body 'help' to
redhat-li...@redhat.com

You can reach the person managing the list at
redhat-l...@redhat.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Redhat-list digest..."


Today's Topics:

1. Re: confuse with errata to rpm nicely (Ed Wilts)
2. CDRom drive (Michael...@CottonStates.com)
3. RE: CDRom drive (Paul Hamm)
4. Re: How to format man pages for A4 paper printing? (Cameron Simpson)
5. Re: SED Question (Cameron Simpson)
6. Re: Redhat Transition issue (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=)
7. Re: Redhat Transition issue (Ed Wilts)
8. Re: Redhat Transition issue (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=)
9. sockets - accept() (Bruce Tong)
10. multiple nics and ports (dbrett)
11. Re: How to format man pages for A4 paper printing? (Vidiot)
12. Re: sockets - accept() (Statux)
13. Re: CDRom drive (Trevor Hamm)
14. [OT]Basic to Matlab (=?iso-8859-1?Q?Julian_Ni=F1o?=)
15. Re: remote logins for admin (Rodolfo J. Paiz)

--__--__--

Message: 1
Date: Thu, 7 Mar 2002 13:23:28 -0600
From: Ed Wilts <ewi...@ewilts.org>
To: redha...@redhat.com
Subject: Re: confuse with errata to rpm nicely
Reply-To: redha...@redhat.com

On Thu, Mar 07, 2002 at 06:12:40PM +0100, Ismael Touama wrote:
> I am really disturbing with my linux learning, I read all the day severals
> doc to understand in order to do the things kind properly.
> According to the vulnerability in Netfilter, I say to me cool my first
> update
> (or upgrade - don't know-) with rpm command line. But I read in /errata
> (CAN-2002-0060)
> that I needed to be up to date with these rpm to apply this one. What the
> hell !!

> PS:this what disturbed me
> "...Before applying this update, make sure all previously released errata
> relevant to your system have been applied..."

All the Red Hat errata say that. Sometimes they mean it and sometimes they
don't. What you have to realize is that almost all of errata fix security or
major bugs, so you really should apply them and keep yourself up to date.
Rarely do errata offer new features or upgrades to specific packages - that's
why, for example, Red Hat patched php3 for Red Hat Linux 6.2 rather than go
straight to php4. You get much better compatibility this way.

So, the bottom line is that you try to patch just netfilter and see if you get
any dependency failures, and if not, you're done. If you do get a dependency
failure, then apply the dependencies as Red Hat suggested. You should,
however, at your earliest convenience, apply all the errata. This is no
different than any other major computer OS vendor.

What Red Hat really needs to produce is 7.2-1 which has all the errata in it
up to a certain date and let people download the iso and do upgrades that way.
Especially for new installations in areas with poor network connectivity, this
would save many hours or even days of work. You know, almost like service
pak 1...

--
Ed Wilts, Mounds View, MN, USA
mailto:ewi...@ewilts.org


--__--__--

Message: 2
From: Michael...@CottonStates.com
To: redha...@redhat.com
Subject: CDRom drive
Date: Thu, 7 Mar 2002 15:26:34 -0500
Reply-To: redha...@redhat.com

What is a good CDRom that will work with Linux and won't giv eme any driver
issues.


--__--__--

Message: 3
From: Paul Hamm <paul...@OpenRatings.com>
To: "'redha...@redhat.com'" <redha...@redhat.com>
Subject: RE: CDRom drive
Date: Thu, 7 Mar 2002 15:35:03 -0500
Reply-To: redha...@redhat.com

I know of no currently avaialable internal cdrom drives that will give you a
problem with linux, IDE or SCSI.

-----Original Message-----
From: Michael...@CottonStates.com
[mailto:Michael...@CottonStates.com]
Sent: Thursday, March 07, 2002 3:27 PM
To: redha...@redhat.com
Subject: CDRom drive


What is a good CDRom that will work with Linux and won't giv eme any driver
issues.

_______________________________________________
Redhat-list mailing list
Redha...@redhat.com
https://listman.redhat.com/mailman/listinfo/redhat-list


--__--__--

Message: 4
Date: Fri, 8 Mar 2002 07:49:08 +1100
From: Cameron Simpson <c...@zip.com.au>
To: redha...@redhat.com
Subject: Re: How to format man pages for A4 paper printing?
Reply-To: redha...@redhat.com

On 06:30 07 Mar 2002, José Romildo Malaquias <rom...@uber.com.br> wrote:
| On Tue, Mar 05, 2002 at 11:41:46AM +0100, Rick van der Linde wrote:
| > >I want to print some manuals, but the default formatting I am getting
| > >is for letter paper and I am using A4 paper. I am doing:
| > > $ man -t fvwm2 | lpr
| > >to print the fvwm2 manual, for example. What should I do to get
| > >A4 paper formatting?
| >
| > I can't tell you exactly what to do. But I know you'll need
| > to change an/some entries in your /etc/printcap file.
| >
| > Probably you'll be able to change settings in printconf
| > too. It will allow you to choose the default paper size.
|
| My printer is already configured for A4 paper printing.
|
| The problem is the generation of the PostScript file in A4
| by groff, which is called by man as a consequence of the -t
| option.
|
| Making some research, I have found the
| /usr/share/doc/groff-1.17.2/README.A4 file with instructions
| on how to achieve that.

We do this a different way: we use nroff for the formatting
(implicitly by using the output of the "man" command) and feed it
to a2ps, using its A4 options.
--
Cameron Simpson, DoD#743 c...@zip.com.au http://www.zip.com.au/~cs/

penetration resistance is always a bonus. - Jody Levine


--__--__--

Message: 5
Date: Fri, 8 Mar 2002 07:54:07 +1100
From: Cameron Simpson <c...@zip.com.au>
To: redha...@redhat.com
Subject: Re: SED Question
Reply-To: redha...@redhat.com

On 00:41 07 Mar 2002, Vidiot <br...@mrvideo.vidiot.com> wrote:
| >This is actually false. For the envelope ("From ") it's true, but for
| >the mail headers (the envelope's not part of the headers) the header name
| >is case insensitive. Have a look at RFC2822 - an enlightening document.
| >Cameron Simpson, DoD#743 c...@zip.com.au http://www.zip.com.au/~cs/
|
| I've never seen "From:" be anything but as I typed it. Interesting.

No good mail client will damage what you type, and so if you type
"From:" that's how it will stay. But it _is_ legal to supply "froM:"
or any other wierd case combination.
--
Cameron Simpson, DoD#743 c...@zip.com.au http://www.zip.com.au/~cs/

This should be good fun. It's been a while since the group has had such a
ripe opportunity to gut, gill, and fillet some poor bastard. Ah well. Off to
get the popcorn...
- bo...@vice.ICO.TEK.COM (Robert Beauchaine)


--__--__--

Message: 6
To: redha...@redhat.com
Subject: Re: Redhat Transition issue
Organization: Red Hat, Inc.
From: t...@redhat.com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=)
Date: 07 Mar 2002 15:53:05 -0500
Reply-To: redha...@redhat.com

Ed Wilts <ewi...@ewilts.org> writes:

> On Mon, Mar 04, 2002 at 01:27:21PM +0530, Ashwin Khandare wrote:
> > a)There has been change in directory structure to some extent
> > b)Path of various configuration files have been changed
> > c)New libraries have been introduced
>
> That's an unfortunate side-effect of major releases and an every-changing
> platform base. You'll also see similar problems transitioning from one
> distribution to another.
>
> To make matters worse, if you install a Red Hat package and then decide you
> want to install the original developer's version instead, you may find that
> files have moved around since Red Hat wants to follow their own
> standards.

Hardly. Many packages are not FHS-compliant, however, and we fix them.

> Since 8.0 is not even beta yet, you probably won't get an official statement.
> However, since most of the Linux distributors are slowly migrating to the
> Linux Standard Base, and Red Hat is currently not compliant, I would expect
> more stuff to move around again.

It's very close to comformant, like pretty much everyone else.

--
Trond Eivind Glomsrød
Red Hat, Inc.


--__--__--

Message: 7
Date: Thu, 7 Mar 2002 15:24:10 -0600
From: Ed Wilts <ewi...@ewilts.org>
To: redha...@redhat.com
Subject: Re: Redhat Transition issue
Reply-To: redha...@redhat.com

On Thu, Mar 07, 2002 at 03:53:05PM -0500, Trond Eivind Glomsrød wrote:
> Ed Wilts <ewi...@ewilts.org> writes:
>
> > On Mon, Mar 04, 2002 at 01:27:21PM +0530, Ashwin Khandare wrote:
> > > a)There has been change in directory structure to some extent
> > > b)Path of various configuration files have been changed
> > > c)New libraries have been introduced
> >
> > That's an unfortunate side-effect of major releases and an every-changing
> > platform base. You'll also see similar problems transitioning from one
> > distribution to another.
> >
> > To make matters worse, if you install a Red Hat package and then decide you
> > want to install the original developer's version instead, you may find that
> > files have moved around since Red Hat wants to follow their own
> > standards.
>
> Hardly. Many packages are not FHS-compliant, however, and we fix them.

I'm not saying that what you do is bad. Some of the raw sources that you must
deal with (at least some of what I've seen) don't conform to any normal Linux
standards - some are simply for another Unix base or based on what the original
author thinks is right. You have the right (and I say the obligation) to
deliver a distribution that makes sense, and you've done so.

> > Since 8.0 is not even beta yet, you probably won't get an official statement.
> > However, since most of the Linux distributors are slowly migrating to the
> > Linux Standard Base, and Red Hat is currently not compliant, I would expect
> > more stuff to move around again.
>
> It's very close to comformant, like pretty much everyone else.

So, to get back to the original poster's question, can we/he expect things to
move around, or is it too early in the development cycle to make general
commments like this? Have directory structures stabilized now? How much
upward compatibility can developers expect going forward?

Cheers,
.../Ed
--
Ed Wilts, Mounds View, MN, USA
mailto:ewi...@ewilts.org


--__--__--

Message: 8
To: redha...@redhat.com
Subject: Re: Redhat Transition issue
Organization: Red Hat, Inc.
From: t...@redhat.com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=)
Date: 07 Mar 2002 16:33:18 -0500
Reply-To: redha...@redhat.com

Ed Wilts <ewi...@ewilts.org> writes:

> On Thu, Mar 07, 2002 at 03:53:05PM -0500, Trond Eivind Glomsrød wrote:
> > Ed Wilts <ewi...@ewilts.org> writes:
> >
> > > On Mon, Mar 04, 2002 at 01:27:21PM +0530, Ashwin Khandare wrote:
> > > > a)There has been change in directory structure to some extent
> > > > b)Path of various configuration files have been changed
> > > > c)New libraries have been introduced
> > >
> > > That's an unfortunate side-effect of major releases and an every-changing
> > > platform base. You'll also see similar problems transitioning from one
> > > distribution to another.
> > >
> > > To make matters worse, if you install a Red Hat package and then decide you
> > > want to install the original developer's version instead, you may find that
> > > files have moved around since Red Hat wants to follow their own
> > > standards.
> >
> > Hardly. Many packages are not FHS-compliant, however, and we fix them.
>
> I'm not saying that what you do is bad. Some of the raw sources that you must
> deal with (at least some of what I've seen) don't conform to any normal Linux
> standards - some are simply for another Unix base or based on what the original
> author thinks is right. You have the right (and I say the obligation) to
> deliver a distribution that makes sense, and you've done so.
>
> > > Since 8.0 is not even beta yet, you probably won't get an official statement.
> > > However, since most of the Linux distributors are slowly migrating to the
> > > Linux Standard Base, and Red Hat is currently not compliant, I would expect
> > > more stuff to move around again.
> >
> > It's very close to comformant, like pretty much everyone else.
>
> So, to get back to the original poster's question, can we/he expect things to
> move around, or is it too early in the development cycle to make general
> commments like this?

As far as LSB goes, things won't change much from what they are
now. He's depending on things outside the scope of LSB, like perl, PHP
etc. These change, and paticulary binary modules for these
seldom/never stay compatible on multiple major versions.

--
Trond Eivind Glomsrød
Red Hat, Inc.


--__--__--

Message: 9
Date: Thu, 7 Mar 2002 16:36:44 -0500 (EST)
From: Bruce Tong <zzt...@pugsly.ev.net>
To: <redha...@redhat.com>
Subject: sockets - accept()
Reply-To: redha...@redhat.com

I'm bringing a home-grown in-house server application up to newer versions
of RedHat (7.1 and 7.2). When a client attempts to connect, the server's
accept() call fails and the error is EINVAL ("Invalid Argument").

The socket code has not changed since inception, right around RedHat 4.2.
If I build and test on RedHat 7.0 and before, it works. If I build and
test on 7.1 or later it fails.

I'm tempted to think there's some configuration issue, though I've
exhausted all of the things I've thought of. Does anyone have any ideas
why this might be failing?

--

Bruce Tong | Got me an office; I'm there late at night.
Sr. Software Engineer | Just send me e-mail, maybe I'll write.
Electronic Vision / FITNE |
zzt...@pugsly.ev.net | -- Joe Walsh for the 21st Century

--__--__--

Message: 10
Date: Thu, 7 Mar 2002 12:01:23 -0500 (EST)
From: dbrett <dbr...@tcn.net>
To: redha...@redhat.com
Subject: multiple nics and ports
Reply-To: redha...@redhat.com

Is it possible to have one computer with two network cards and have one
application use the first nic and all other applications use the second
nic?

david

--__--__--

Message: 11
From: Vidiot <br...@mrvideo.vidiot.com>
Subject: Re: How to format man pages for A4 paper printing?
To: redha...@redhat.com
Date: Thu, 7 Mar 2002 15:00:42 -0600 (CST)
Reply-To: redha...@redhat.com

>We do this a different way: we use nroff for the formatting
>(implicitly by using the output of the "man" command) and feed it
>to a2ps, using its A4 options.
>Cameron Simpson, DoD#743 c...@zip.com.au http://www.zip.com.au/~cs/

Read up on groff. You can give it a paper option.

MB
--
e-mail: vid...@vidiot.com It is God's job to forgive bin Laden.
It is our job to set up the meeting.
U.S. Marine Corp.
Visit - URL: http://www.vidiot.com/ (Your link to Star Trek and UPN)


--__--__--

Message: 12
Date: Thu, 7 Mar 2002 17:43:25 -0500 (EST)
From: Statux <sta...@bigfoot.com>
To: redha...@redhat.com
Subject: Re: sockets - accept()
Reply-To: redha...@redhat.com

Posting a snippet of code might help, although a Networking-in-C list
might be more suitable :)

On Thu, 7 Mar 2002, Bruce Tong wrote:

> I'm bringing a home-grown in-house server application up to newer versions
> of RedHat (7.1 and 7.2). When a client attempts to connect, the server's
> accept() call fails and the error is EINVAL ("Invalid Argument").
>
> The socket code has not changed since inception, right around RedHat 4.2.
> If I build and test on RedHat 7.0 and before, it works. If I build and
> test on 7.1 or later it fails.
>
> I'm tempted to think there's some configuration issue, though I've
> exhausted all of the things I've thought of. Does anyone have any ideas
> why this might be failing?
>
>

--
-Statux


--__--__--

Message: 13
Subject: Re: CDRom drive
From: Trevor Hamm <tre...@sask.trlabs.ca>
To: redha...@redhat.com
Date: 07 Mar 2002 16:49:19 -0600
Reply-To: redha...@redhat.com

On Thu, 2002-03-07 at 14:26, Michael...@CottonStates.com wrote:
> What is a good CDRom that will work with Linux and won't giv eme any driver
> issues.
>

AFAIK, all IDE and SCSI CDROMs work with Linux. There's even support for
some of the older non-IDE, non-SCSI CDROMs that used to interface with
the sound card, though I don't think you'll have to worry about those
too much. IDE CD-R(W)s are a little more tricky, in that you need to use
the IDE SCSI emulator to get them fully operational. You may want to
check out the CDROM-HOWTO:
http://www.linuxdoc.org/HOWTO/CDROM-HOWTO/index.html

--
Trevor Hamm

--__--__--

Message: 14
From: =?iso-8859-1?Q?Julian_Ni=F1o?= <ani...@cantv.net>
To: <redha...@redhat.com>
Subject: [OT]Basic to Matlab
Date: Thu, 7 Mar 2002 19:28:52 -0600
Reply-To: redha...@redhat.com

This is a multi-part message in MIME format.

------=_NextPart_000_0016_01C1C60E.50B0F260
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello:

I need information about some "compiler " from Basic to Matlab files.

thanks.

------=_NextPart_000_0016_01C1C60E.50B0F260
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4134.100" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>Hello:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I need information about some "compiler =
" from=20
Basic to Matlab files.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>thanks.</FONT></DIV></BODY></HTML>

------=_NextPart_000_0016_01C1C60E.50B0F260--


--__--__--

Message: 15
Date: Thu, 07 Mar 2002 17:21:54 -0600
To: redha...@redhat.com
From: "Rodolfo J. Paiz" <rp...@indahaus.com>
Subject: Re: remote logins for admin
Reply-To: redha...@redhat.com

At 3/7/2002 12:45 AM -0600, you wrote:
>What would be a good way to login to my RH7.2 box from a remote location
>to do things like adding email users, etc? Seems to me there are more
>secure way than telnet, that are more favored these days, am I right?

Use ssh. Get the latest RPM's from the updates FTP site (2.9.2p1 IIRC) and
install the openssh, openssh-clients, and openssh-server RPM's.

Alternately, as you said, use Webmin. Make sure you enable SSL. Note that
Webmin has an ssh module as well, so installing both is a good idea anyway.
That way you can get to your box through ssh from anywhere with a browser. :)

>I'm running NAT on a Cisco 678, so if there's a port to open up, pls tell
>me tell me that too.

Port 22 for ssh, 10000 (ten thousand) for Webmin.


--
Rodolfo J. Paiz
rp...@indahaus.com

--__--__--

_______________________________________________
Redhat-list mailing list
Redha...@redhat.com
https://listman.redhat.com/mailman/listinfo/redhat-list


End of Redhat-list Digest

0 new messages