RE: confuse with errata to rpm nicely

2002-03-09 Thread Keith Morse

On Fri, 8 Mar 2002, Paul Hamm wrote:

[snippage occurred here]
> 
> Oh and I am no expert on how to make a custom distro the first time I looked
> into it was in Late January.  If you can mount an iso, rm, mv, edit 1 file
> "comps" and run the command "># genhdlist --withnumbers /location/of/disc1
> /location/of/disc2" you can make a custom distro that works great.  You will
> need to use 700mb discs though as the patches boost the size of the iso
> files.  If you don't want to burn the additional cds just copy the contents
> of the RPMS directory from disc2 to disc1.  Share that directory.  Then you
> can use the  boot floppy or original 7.2 boot CD and do a network install
> from http, nfs, or ftp.


My take on this was to read the RedHat-CDROM-Howto and implement the 
"patched" not on a cd, but rather on an internal anonymous ftp server.  
The process is automated using the perl "mirror" script, along with 
modified scripts from the Howto referenced above.  It dispenses with the 3 
day old obsoleted cd collection, and each install is assured to be current 
at the time of install.



___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



RE: confuse with errata to rpm nicely

2002-03-08 Thread Paul Hamm

2512588Kb(Pensacola 4 disks) x3,4,6,12 times a year still seems like that
little bitty 46900Kb is a bargan to me.  About all you really save is that
468000Kb gets a bit smaller.

Oh and I am no expert on how to make a custom distro the first time I looked
into it was in Late January.  If you can mount an iso, rm, mv, edit 1 file
"comps" and run the command "># genhdlist --withnumbers /location/of/disc1
/location/of/disc2" you can make a custom distro that works great.  You will
need to use 700mb discs though as the patches boost the size of the iso
files.  If you don't want to burn the additional cds just copy the contents
of the RPMS directory from disc2 to disc1.  Share that directory.  Then you
can use the  boot floppy or original 7.2 boot CD and do a network install
from http, nfs, or ftp.

-Original Message-
From: Ed Wilts [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 08, 2002 1:24 PM
To: [EMAIL PROTECTED]
Subject: Re: confuse with errata to rpm nicely


On Fri, Mar 08, 2002 at 12:53:28PM -0500, Paul Hamm wrote:
>  Like I said grab the iso files grab all the patches and roll your
> own. 

That's fine for those of us with lots of bandwidth and expert knowledge.
For
those that have poor or expensive bandwidth, they're paying a very hefty
premium.  Some parts of the world pay by the amount of traffic and even some
US ISPs are looking at or already are capping the traffic downloads.

I'm happy with my own bandwidth and the price I pay - I'm fighting this
issue
for the little guys!

For the record, the current size of the 7.2 errata in the i386 directory is
469,012,837 bytes.  At 5kBps (for a 56kbps modem), this would amount to 26 
HOURS of transfer time.

-- 
Ed Wilts, Mounds View, MN, USA
mailto:[EMAIL PROTECTED]



___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



Re: confuse with errata to rpm nicely

2002-03-08 Thread Ed Wilts

On Fri, Mar 08, 2002 at 12:53:28PM -0500, Paul Hamm wrote:
>  Like I said grab the iso files grab all the patches and roll your
> own. 

That's fine for those of us with lots of bandwidth and expert knowledge.  For
those that have poor or expensive bandwidth, they're paying a very hefty
premium.  Some parts of the world pay by the amount of traffic and even some
US ISPs are looking at or already are capping the traffic downloads.

I'm happy with my own bandwidth and the price I pay - I'm fighting this issue
for the little guys!

For the record, the current size of the 7.2 errata in the i386 directory is
469,012,837 bytes.  At 5kBps (for a 56kbps modem), this would amount to 26 
HOURS of transfer time.

-- 
Ed Wilts, Mounds View, MN, USA
mailto:[EMAIL PROTECTED]



___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



RE: confuse with errata to rpm nicely

2002-03-08 Thread Paul Hamm

Ed you would have even more of those iso downloads not less.  How many time
should they update the iso every year? 3,4,6,12 how many people that already
have 7.2 or going to grab 7.2- how many would download every
single one?  Whenever RH releases a new batch of isos all the mirrors and
rhn tank for a week or 2.  Thats what you could expect what 12 times a year
maybe?  Like I said grab the iso files grab all the patches and roll your
own.  I did and have a nice batch of bootable cds patched to 2002-02-14.  I
even called it rh7.2.1 ;-)  Was a pain as I did the whole thing manually but
a few perl scripts and it could be automated except the disc swap.

-Original Message-
From: Ed Wilts [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 08, 2002 12:32 PM
To: [EMAIL PROTECTED]
Subject: Re: confuse with errata to rpm nicely


On Fri, Mar 08, 2002 at 10:08:58AM -0500, Paul Hamm wrote:
> Err Ed how is downloading 4 iso images on a regular basis for people with
> slow connections going to help them out?  rsync running on cron will
> download all the updates available in the middle of the night that you
have
> not already got.  And replacing the old packages with the new ones in an
iso
> image is not that difficult after that first batch of patches.

What I suggested is for Red Hat to release (say) 7.2-1.  This will have 7.2
plus the current errata and make that available in a single iso set.  Then
people who want to install tomorrow would download the 7.2-1 isos instead of
7.2 isos and hundreds of megs of errata.  My suggestion would not help
people
that are already running 7.2.  My suggestion would *NOT* replace errata but
simply provide a more convenient mechanism for new installers.

7.2-1 would report itself to the system as 7.2 and would look identical to a
7.2 system that had been upgraded using current errata.  The only reason
they'd
number them 7.2-1 would be to differentiate how current the errata are.  
Perhaps they'd just call the iso 7.2-2002.03 or something weird like that.

I strongly suspect that if you ask Red Hat or any of their mirrors how often
the 7.2 isos are being downloaded that you'll find that they're regularly
accessed.  My suggestion would reduce download time for the clients and
reduce
the load on the servers, especially Red Hat's rhn servers.

-- 
Ed Wilts, Mounds View, MN, USA
mailto:[EMAIL PROTECTED]



___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



Re: confuse with errata to rpm nicely

2002-03-08 Thread Ed Wilts

On Fri, Mar 08, 2002 at 10:08:58AM -0500, Paul Hamm wrote:
> Err Ed how is downloading 4 iso images on a regular basis for people with
> slow connections going to help them out?  rsync running on cron will
> download all the updates available in the middle of the night that you have
> not already got.  And replacing the old packages with the new ones in an iso
> image is not that difficult after that first batch of patches.

What I suggested is for Red Hat to release (say) 7.2-1.  This will have 7.2
plus the current errata and make that available in a single iso set.  Then
people who want to install tomorrow would download the 7.2-1 isos instead of
7.2 isos and hundreds of megs of errata.  My suggestion would not help people
that are already running 7.2.  My suggestion would *NOT* replace errata but
simply provide a more convenient mechanism for new installers.

7.2-1 would report itself to the system as 7.2 and would look identical to a
7.2 system that had been upgraded using current errata.  The only reason they'd
number them 7.2-1 would be to differentiate how current the errata are.  
Perhaps they'd just call the iso 7.2-2002.03 or something weird like that.

I strongly suspect that if you ask Red Hat or any of their mirrors how often
the 7.2 isos are being downloaded that you'll find that they're regularly
accessed.  My suggestion would reduce download time for the clients and reduce
the load on the servers, especially Red Hat's rhn servers.

-- 
Ed Wilts, Mounds View, MN, USA
mailto:[EMAIL PROTECTED]



___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



Re: confuse with errata to rpm nicely

2002-03-08 Thread Ed Wilts

On Fri, Mar 08, 2002 at 11:24:56AM +0100, Ismael Touama wrote:
> But rhn isn't not free ?

It is for a single system!  For home users, it's perfect.  For corporate users,
you should expect to pay for this type of support.

-- 
Ed Wilts, Mounds View, MN, USA
mailto:[EMAIL PROTECTED]



___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



RE: confuse with errata to rpm nicely

2002-03-08 Thread Ismael Touama

OK thank you,

I'm kind of disturbing cause it lacks me a lot of linux concept or
calling terms, by the way, I have to install this new kernell realease
cause i'm having IRC installed and just to be up to date, isn't it.
I intend to do so to cultivate myself to linux word (kind of old papy
grummbling
always the same !!?).
For the moment I try to ... transfer my rpm downloaded from my MS PC via a
CD-RW !!
Hard! but it's fun... not yet really easy with the fs.
I'll automatise that with pretty good bash treatment or cron later when more
comfurtable.

Really thanks,
ism

-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]De la part de Paul Hamm
Envoyé : vendredi 8 mars 2002 16:09
À : '[EMAIL PROTECTED]'
Objet : RE: confuse with errata to rpm nicely


Err Ed how is downloading 4 iso images on a regular basis for people with
slow connections going to help them out?  rsync running on cron will
download all the updates available in the middle of the night that you have
not already got.  And replacing the old packages with the new ones in an iso
image is not that difficult after that first batch of patches.

Ism
As Ed stated most of the Redhat patches are to close security holes and fix
known bugs.  The only ones you really need to install are the ones that can
be abused for security but if you are not using say wu-ftp then you really
don't need to patch it as no matter how many holes it has you can not be
effected by them if you are not using the offending package.  If you plan on
installing lots of linux machines or maybe just install the same machine
several times I would recommend that you creating a custom distibution which
contains all the errata to date.  It makes the install much faster.  Check
through the forums for custom distro and genhdlist if you are interested.

-Original Message-
From: Ed Wilts [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 07, 2002 2:23 PM
To: [EMAIL PROTECTED]
Subject: Re: confuse with errata to rpm nicely


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:[EMAIL PROTECTED]



___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



RE: confuse with errata to rpm nicely

2002-03-08 Thread Paul Hamm

Err Ed how is downloading 4 iso images on a regular basis for people with
slow connections going to help them out?  rsync running on cron will
download all the updates available in the middle of the night that you have
not already got.  And replacing the old packages with the new ones in an iso
image is not that difficult after that first batch of patches.

Ism
As Ed stated most of the Redhat patches are to close security holes and fix
known bugs.  The only ones you really need to install are the ones that can
be abused for security but if you are not using say wu-ftp then you really
don't need to patch it as no matter how many holes it has you can not be
effected by them if you are not using the offending package.  If you plan on
installing lots of linux machines or maybe just install the same machine
several times I would recommend that you creating a custom distibution which
contains all the errata to date.  It makes the install much faster.  Check
through the forums for custom distro and genhdlist if you are interested.

-Original Message-
From: Ed Wilts [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 07, 2002 2:23 PM
To: [EMAIL PROTECTED]
Subject: Re: confuse with errata to rpm nicely


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:[EMAIL PROTECTED]



___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



RE: confuse with errata to rpm nicely

2002-03-08 Thread Ismael Touama

Yes of course it's a kind of way...
But rhn isn't not free ?
Furthermore, I'm learning so I want to know what's goin'on on my system.
And, can be shoking, but, my server is not yet on my LAN...
I really thank you but I prefer explications rather thatn just a magic
command
that shouldn't give me the opportunity to understand how linux is running.

Thanks,
ism
"What's goin'on; what's goin'on, what's goin'on inside my head!" -HüSKER DÜ

-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]De la part de Eric Wood
Envoyé : jeudi 7 mars 2002 19:24
À : [EMAIL PROTECTED]
Objet : Re: confuse with errata to rpm nicely


After registering with redhat network (rhn_register), I'll I do is

# update -u

It downloads and install errate rpms automatically.  Easy as pie.

-eric wood

- Original Message -
From: "Ismael Touama" <[EMAIL PROTECTED]>
> Is someone can take a bit of his/her time to introduce me in a good way
> (what do you think of !?) ?
> I'm kind of disturbed, and near the loss of control.
> Thanks for the help, even a little one would be consider as a great one !




___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



RE: confuse with errata to rpm nicely

2002-03-08 Thread Ismael Touama

Hi Ed,

thanks for details.
Ok so i'll have hours downloading and then installing this errata fixes.
You should propose your idea, it's sure for guys who got poor connection
and they've just install their new system, it must be a real bad first
contact
to linux.
So download time operation.
Thanks again.

-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]De la part de Ed Wilts
Envoye : jeudi 7 mars 2002 20:23
A : [EMAIL PROTECTED]
Objet : Re: confuse with errata to rpm nicely


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:[EMAIL PROTECTED]



___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



Re: confuse with errata to rpm nicely

2002-03-07 Thread Ed Wilts

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:[EMAIL PROTECTED]



___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



Re: confuse with errata to rpm nicely

2002-03-07 Thread Eric Wood

After registering with redhat network (rhn_register), I'll I do is 

# update -u

It downloads and install errate rpms automatically.  Easy as pie.

-eric wood

- Original Message - 
From: "Ismael Touama" <[EMAIL PROTECTED]>
> Is someone can take a bit of his/her time to introduce me in a good way
> (what do you think of !?) ?
> I'm kind of disturbed, and near the loss of control.
> Thanks for the help, even a little one would be consider as a great one !




___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



confuse with errata to rpm nicely

2002-03-07 Thread Ismael Touama

Hi,

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 !!
Nearly 60 rpm !!! to download and install !!
No no, there is a thing, no there are lot of things that I don't
understand...
Is someone can take a bit of his/her time to introduce me in a good way
(what do you think of !?) ?
I'm kind of disturbed, and near the loss of control.
Thanks for the help, even a little one would be consider as a great one !

ism

PS:this what disturbed me
"...Before applying this update, make sure all previously released errata
relevant to your system have been applied..."
@ http://www.redhat.com/support/errata/RHSA-2002-028.html

I'm on a DELL PowerEdge 2500 in RAID1.



___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list