Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-08 Thread cpolish
On 2016-11-08 08:27, Dipal Bhatt wrote:
> Thanks really Leon very much w/ a very resourceful info. esp release notes
> helps across minor versions.  So, this is for a friend of mine, and I have
> been told that they will not currently consider updating their userland
> from 6.3 to 6.8 but only selected few packages.  The picture seems to be
> that their company runs a lot of apps on 6.3 userland and might have some
> specific dependencies, etc., but more importantly, this environment has
> been running in customers' environment for quite some time esp 1000s of
> customers, so updating system properly is not easily feasible for this
> scenario.  However, they can hand pick packages seem fit for update that
> can be pushed out using their internal code fixes and updates for end
> users. SO, this seems to be the problem of trying to hand pick certain
> packages to be updated, if feasible w/o much adverse effects.

Hi Dipal,

I compliment you on your unflagging politeness in the
continual attempt to steer you to another, safer course.

I've been faced with a similar situation, a vendor (Sungard)
who would only qualify Red Hat 4 and Sun Server 6, and wouldn't
budge. The setting was a US$100 million annual budget enterprise
with a CTO with very low risk tolerance. Our staff pushed the
"don't upgrade" strategy about as far as anyone could ever
hope to take it. We hand patched our way through "heartbleed",
for example.

In my case, wanting better outcomes, I accelerated the move to
automated deployment (Cobbler + Puppet), and was then able to
provide solid test environments that allowed developers to
quickly re-deploy applications on newer versions of the OS.
Initially the push-back was voiced as the whole idea being too
costly. The new approach actually reduced costs, freed up
developer time, and led to stable systems running in (mostly)
supported configurations. When the vendor demanded a bug be
demo'd on a Red Hat 4 system, we were able to spin one up. But
they almost never asked. Apparently most of their customers had
decided safety and convenience outranks stupidity on the part of
the vendor, and as a practical matter their help desk
strategically failed to notice the "unsupported" OS.

I believe the approach you've been requested to assist with
has an implicit wager that you're almost certain to lose:

   > they can hand pick packages seem fit for update
   > that can be pushed out using their internal code 
   > fixes and updates

Consider, this is what Red Hat pays staff to do. Update some
packages, test if anything breaks, act on reports from the 
field. When one makes a complete upgrade to 6 (current), one
rides on the coattails of all the work of the Red Hat team to
test and stabilize changes. 

On the other hand, if one omits the update to 6 (current), they
have the identical problem but are foresaking the vendor's sunk
costs in testing and debugging. The implicit wager is that the
few hand-picked packages will reduce exposure to changes,
and so reduce labor, and increase your chances for a stable
system. However, consider that glibc went through these changes

 CentOS 6.3 glibc-2.12-1.80 
 CentOS 6.4 glibc-2.12-1.107 
 CentOS 6.5 glibc-2.12-1.132 
 CentOS 6.6 glibc-2.12-1.149 
 CentOS 6.7 glibc-2.12-1.166 
 CentOS 6.8 glibc-2.12-1.192

and that just about everything links against glibc, and you
can see that upgrading piecemeal is a good recipe for running
into subtle problems. And that's _one_ package.

If you have a small set of specific breaking changes, better
to get the devs off their butts and fix things or find work
arounds than to take on the greater risks of piecing together
odds and ends... which never stops.

Apparently you're in for an unending, unprofitable slog through
the worst, most unsatisfying kind of sysadminery. Been there,
done that, moved on!

Best regards,
-- 
Charles Polisher

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-08 Thread Dipal Bhatt
On Tue, Nov 8, 2016 at 12:10 PM, John R Pierce  wrote:

> On 11/8/2016 9:28 AM, Dipal Bhatt wrote:
>
>> Unfortunately, that's the constraint it seems hence, there's inquiry of
>> other options.  But, looks like, any el6 package should work as long as we
>> meet the dependencies?
>>
>
> mixing current 6.8 packages with very old 6.3 packages and libraries is a
> recipe for problems.  these  combinations are simply untested.   If
> you're willing to do such testing, go for it.   be sure to regression test
> all the corner cases of the specific packages. One thing that would
> help significantly would be to uninstall all packages you don't actually
> need for these systems. I always start with 'minimal', and install just
> the packages my application stack needs.  That is a standard policy of
> security benchmarks such as CIS [1].
>
> how could someone deploy 1000s of computer systems in the field without a
> plan for regular security updates?!?that would be somewhat analogous to
> buying a fleet of airplanes without any plan or provisions for scheduled
> maintenance.
>
>
 Yes, will pass on these excellent suggestions to my friend, but agreed
with your analogy as well as concerns around security issues for such a
large deployment, it seems.  Thanks all.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-08 Thread John R Pierce

On 11/8/2016 9:28 AM, Dipal Bhatt wrote:

Unfortunately, that's the constraint it seems hence, there's inquiry of
other options.  But, looks like, any el6 package should work as long as we
meet the dependencies?


mixing current 6.8 packages with very old 6.3 packages and libraries is 
a recipe for problems.  these  combinations are simply untested.   
If you're willing to do such testing, go for it.   be sure to regression 
test all the corner cases of the specific packages. One thing that 
would help significantly would be to uninstall all packages you don't 
actually need for these systems. I always start with 'minimal', and 
install just the packages my application stack needs.  That is a 
standard policy of security benchmarks such as CIS [1].


how could someone deploy 1000s of computer systems in the field without 
a plan for regular security updates?!?that would be somewhat 
analogous to buying a fleet of airplanes without any plan or provisions 
for scheduled maintenance.



[1] 
https://benchmarks.cisecurity.org/downloads/show-single/?file=centos6.201


--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-08 Thread Dipal Bhatt
Unfortunately, that's the constraint it seems hence, there's inquiry of
other options.  But, looks like, any el6 package should work as long as we
meet the dependencies?
Kindly thanks for many help.

On Tue, Nov 8, 2016 at 10:55 AM, John R Pierce  wrote:

> On 11/8/2016 6:27 AM, Dipal Bhatt wrote:
>
>> Thanks really Leon very much w/ a very resourceful info. esp release notes
>> helps across minor versions.  So, this is for a friend of mine, and I have
>> been told that they will not currently consider updating their userland
>> from 6.3 to 6.8 but only selected few packages.  The picture seems to be
>> that their company runs a lot of apps on 6.3 userland and might have some
>> specific dependencies, etc., but more importantly, this environment has
>> been running in customers' environment for quite some time esp 1000s of
>> customers, so updating system properly is not easily feasible for this
>> scenario.  However, they can hand pick packages seem fit for update that
>> can be pushed out using their internal code fixes and updates for end
>> users. SO, this seems to be the problem of trying to hand pick certain
>> packages to be updated, if feasible w/o much adverse effects.
>>
>
> thats a whole lot of words that boil down to  nothing,they won't
> update because they don't want to, and are too lazy ?
>
>
>
> --
> john r pierce, recycling bits in santa cruz
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-08 Thread John R Pierce

On 11/8/2016 6:27 AM, Dipal Bhatt wrote:

Thanks really Leon very much w/ a very resourceful info. esp release notes
helps across minor versions.  So, this is for a friend of mine, and I have
been told that they will not currently consider updating their userland
from 6.3 to 6.8 but only selected few packages.  The picture seems to be
that their company runs a lot of apps on 6.3 userland and might have some
specific dependencies, etc., but more importantly, this environment has
been running in customers' environment for quite some time esp 1000s of
customers, so updating system properly is not easily feasible for this
scenario.  However, they can hand pick packages seem fit for update that
can be pushed out using their internal code fixes and updates for end
users. SO, this seems to be the problem of trying to hand pick certain
packages to be updated, if feasible w/o much adverse effects.


thats a whole lot of words that boil down to  nothing,they won't 
update because they don't want to, and are too lazy ?




--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-08 Thread Always Learning

On Tue, 2016-11-08 at 08:27 -0600, Dipal Bhatt wrote:

> .  So, this is for a friend of mine, and I have
> been told that they will not currently consider updating their userland
> from 6.3 to 6.8 but only selected few packages.  The picture seems to be
> that their company runs a lot of apps on 6.3 userland and might have some
> specific dependencies, etc., but more importantly, this environment has
> been running in customers' environment for quite some time esp 1000s of
> customers, so updating system properly is not easily feasible for this
> scenario.

If everyone is running STANDARD CENTOS there should be *no* problems
updating to the latest C 6.8 version.

(1) Save one complete installation.

(2) Install it on a spare machine.

(3) Change /etc/sysconfig/network-scripts/ifcfg-eth0 if necessary.

(4) Do a: yum update

(5) Test the applications

(6) Wait a few weeks and if still no problems, then upgrade the others.



-- 
Regards,

Paul.
England, EU.  England's place is in the European Union.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-08 Thread Alice Wonder

On 11/08/2016 06:27 AM, Dipal Bhatt wrote:




Show us this "no way to update system properly" to get a clear big picture
that is allowing us to provide you with potentially better solutions.


Thanks really Leon very much w/ a very resourceful info. esp release notes
helps across minor versions.  So, this is for a friend of mine, and I have
been told that they will not currently consider updating their userland
from 6.3 to 6.8 but only selected few packages.  The picture seems to be
that their company runs a lot of apps on 6.3 userland and might have some
specific dependencies, etc., but more importantly, this environment has
been running in customers' environment for quite some time esp 1000s of
customers, so updating system properly is not easily feasible for this
scenario.  However, they can hand pick packages seem fit for update that
can be pushed out using their internal code fixes and updates for end
users. SO, this seems to be the problem of trying to hand pick certain
packages to be updated, if feasible w/o much adverse effects.
___


I think RHEL sells support packages for specific releases. Maybe they 
could pay for a RHEL license for 6.3 and then rebuild the updates for 
the CentOS 6.3 machines not covered in the RHEL support license.


If they have thousands of customers, paying for RHEL license for some of 
them probably is not an un-reasonable thing to do.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-08 Thread Dipal Bhatt
>
>
>
> Show us this "no way to update system properly" to get a clear big picture
> that is allowing us to provide you with potentially better solutions.
>
Thanks really Leon very much w/ a very resourceful info. esp release notes
helps across minor versions.  So, this is for a friend of mine, and I have
been told that they will not currently consider updating their userland
from 6.3 to 6.8 but only selected few packages.  The picture seems to be
that their company runs a lot of apps on 6.3 userland and might have some
specific dependencies, etc., but more importantly, this environment has
been running in customers' environment for quite some time esp 1000s of
customers, so updating system properly is not easily feasible for this
scenario.  However, they can hand pick packages seem fit for update that
can be pushed out using their internal code fixes and updates for end
users. SO, this seems to be the problem of trying to hand pick certain
packages to be updated, if feasible w/o much adverse effects.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-08 Thread Leon Fauster
Am 08.11.2016 um 07:14 schrieb Dipal Bhatt :
> Thanks very much, understood.  so, it seems, upgrading selected packages is
> probably going to be fine except where the compatibility matters where it
> would break all kinds of things.


Let me rephrase it, to be clear. Its NOT fine to update selected packages. 
Especially a mixture of 6.3 and 6.8 packages is completely untested and
therefore considered as unstable. 

Please communicate what is exactly pinning you on 6.3. CentOS is for example 
not Fedora, where updates can break things. Its for the most cases absolutely 
save to continue updating CentOS to the latest and the only supported version 
inside the major release e.g. version 6. 

Upstream's release notes will list changes that are important between the minor 
releases
https://access.redhat.com/documentation/en/red-hat-enterprise-linux/?version=6/ 
 


> Something of such nature of request would
> need to be internally tested by simply updating the selected packages, test
> the applications previously running on 6.3 w/ these few selected 6.8
> packages updates.  It seems, the answer is to try and see whether works or
> breaks.  of course, currently, no way to update system properly to latest,
> hence further inquiries.  Really appreciated some helpful pointers. Thanks
> kindly.



Show us this "no way to update system properly" to get a clear big picture
that is allowing us to provide you with potentially better solutions. 

--
LF
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-07 Thread Always Learning

On Tue, 2016-11-08 at 00:14 -0600, Dipal Bhatt wrote:

> Thanks very much, understood.  so, it seems, upgrading selected packages is
> probably going to be fine except where the compatibility matters where it
> would break all kinds of things.

Please be realistic and professional. You simply can not run a
professional business computer operating system like Centos with some
packages so old they are probably a major security risk and other
packages up-to-date.

What will your customer or user say when they discover their data has
been hacked or corrupted simply because someone did not want to
incorporate the latest safe versions of packages already installed ?

If your car is recalled to fit a better and safer version of an already
installed component, are you really going to refuse ? 

Your stance is very unwise and misinformed.


-- 
Regards,

Paul.
England, EU.  England's place is in the European Union.

P.S. Good Luck Hillary.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-07 Thread Gordon Messmer

On 11/07/2016 08:53 PM, Dipal Bhatt wrote:

Understood, but unfortunately, updating to latest version of CentOs 6 is
not the option in this specific situation



If you require support at a point release, you should consult Red Hat:
https://access.redhat.com/solutions/238533

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-07 Thread Dipal Bhatt
Thanks very much, understood.  so, it seems, upgrading selected packages is
probably going to be fine except where the compatibility matters where it
would break all kinds of things.  Something of such nature of request would
need to be internally tested by simply updating the selected packages, test
the applications previously running on 6.3 w/ these few selected 6.8
packages updates.  It seems, the answer is to try and see whether works or
breaks.  of course, currently, no way to update system properly to latest,
hence further inquiries.  Really appreciated some helpful pointers. Thanks
kindly.

On Tue, Nov 8, 2016 at 12:02 AM, William Warren 
wrote:

> Yes you would break all kinds of things.  In a nutshell folks are saying
> you are free to try but when it blows up...you better have a total backup
> to restore the entire box.  Your first priority should be getting whatever
> is holding you back from proper system updates and security out of the way.
>
> On Nov 8, 2016 00:59, "Dipal Bhatt"  wrote:
>
> > The specs may have certain dependency on subset of 6.3 packages, but not
> > for all other packages/binaries, as I mentioned earlier.  So, to keep
> > things rather intact, we would simply meet requirements by only updating
> > "selected packages only".  And, for now, that should be considered
> > intermittent solution until we can safely land to a proper job as you
> > mentioned.  So, would there be any issue by upgrading "selected only
> > packages" temporarily?  For example, only updating nss-util or openssl to
> > 6.8 version.  Thanks all, appreciated very much.
> >
> > On Mon, Nov 7, 2016 at 11:43 PM, Frank Cox 
> > wrote:
> >
> > > On Mon, 7 Nov 2016 23:33:56 -0600
> > > Dipal Bhatt wrote:
> > >
> > > > But, yes, there's
> > > > no way to update the 6.3 to 6.8 as I repeatedly mentioned which is
> the
> > > only
> > > > requirement/constraint.
> > >
> > > It occurs to me to ask what you consider to be version 6.3.  If you
> > update
> > > any of the rpms to the 6.8 version you are no longer running version
> 6.3.
> > > If the spec requires 6.3 and nothing else, then you will no longer be
> > > compatible with the spec as soon as you install the first 6.8 rpm.
> > >
> > > On the other hand, if you are allowed to install 6.8 rpms, then what's
> > > keeping you back from doing a proper job instead of a halfway and
> > > half-assed one?
> > >
> > > Upgrading "selected packages only" will leave you with something that's
> > > neither fish or fowl, and it won't meet your requirements as stated
> > either.
> > >
> > > --
> > > MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
> > > ___
> > > CentOS mailing list
> > > CentOS@centos.org
> > > https://lists.centos.org/mailman/listinfo/centos
> > >
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > https://lists.centos.org/mailman/listinfo/centos
> >
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-07 Thread John R Pierce

On 11/7/2016 9:43 PM, Frank Cox wrote:

Upgrading "selected packages only" will leave you with something that's neither 
fish or fowl, and it won't meet your requirements as stated either.


more specifically, it will be a completely untested configuration. 
considering that any single package can be updated 100s of times in the 
lifetime of a major release (rhel/centos 6 for example), and there's 
1000s of packages, thats an exponential number of combinations, it would 
be insane for the distribution to test every possible combination of 
packages across multiple incremental updates.



--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-07 Thread William Warren
Yes you would break all kinds of things.  In a nutshell folks are saying
you are free to try but when it blows up...you better have a total backup
to restore the entire box.  Your first priority should be getting whatever
is holding you back from proper system updates and security out of the way.

On Nov 8, 2016 00:59, "Dipal Bhatt"  wrote:

> The specs may have certain dependency on subset of 6.3 packages, but not
> for all other packages/binaries, as I mentioned earlier.  So, to keep
> things rather intact, we would simply meet requirements by only updating
> "selected packages only".  And, for now, that should be considered
> intermittent solution until we can safely land to a proper job as you
> mentioned.  So, would there be any issue by upgrading "selected only
> packages" temporarily?  For example, only updating nss-util or openssl to
> 6.8 version.  Thanks all, appreciated very much.
>
> On Mon, Nov 7, 2016 at 11:43 PM, Frank Cox 
> wrote:
>
> > On Mon, 7 Nov 2016 23:33:56 -0600
> > Dipal Bhatt wrote:
> >
> > > But, yes, there's
> > > no way to update the 6.3 to 6.8 as I repeatedly mentioned which is the
> > only
> > > requirement/constraint.
> >
> > It occurs to me to ask what you consider to be version 6.3.  If you
> update
> > any of the rpms to the 6.8 version you are no longer running version 6.3.
> > If the spec requires 6.3 and nothing else, then you will no longer be
> > compatible with the spec as soon as you install the first 6.8 rpm.
> >
> > On the other hand, if you are allowed to install 6.8 rpms, then what's
> > keeping you back from doing a proper job instead of a halfway and
> > half-assed one?
> >
> > Upgrading "selected packages only" will leave you with something that's
> > neither fish or fowl, and it won't meet your requirements as stated
> either.
> >
> > --
> > MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > https://lists.centos.org/mailman/listinfo/centos
> >
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-07 Thread Dipal Bhatt
The specs may have certain dependency on subset of 6.3 packages, but not
for all other packages/binaries, as I mentioned earlier.  So, to keep
things rather intact, we would simply meet requirements by only updating
"selected packages only".  And, for now, that should be considered
intermittent solution until we can safely land to a proper job as you
mentioned.  So, would there be any issue by upgrading "selected only
packages" temporarily?  For example, only updating nss-util or openssl to
6.8 version.  Thanks all, appreciated very much.

On Mon, Nov 7, 2016 at 11:43 PM, Frank Cox 
wrote:

> On Mon, 7 Nov 2016 23:33:56 -0600
> Dipal Bhatt wrote:
>
> > But, yes, there's
> > no way to update the 6.3 to 6.8 as I repeatedly mentioned which is the
> only
> > requirement/constraint.
>
> It occurs to me to ask what you consider to be version 6.3.  If you update
> any of the rpms to the 6.8 version you are no longer running version 6.3.
> If the spec requires 6.3 and nothing else, then you will no longer be
> compatible with the spec as soon as you install the first 6.8 rpm.
>
> On the other hand, if you are allowed to install 6.8 rpms, then what's
> keeping you back from doing a proper job instead of a halfway and
> half-assed one?
>
> Upgrading "selected packages only" will leave you with something that's
> neither fish or fowl, and it won't meet your requirements as stated either.
>
> --
> MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-07 Thread William Warren
What constraint is requiring you to run a highly vulnerable server?

On Nov 8, 2016 00:34, "Dipal Bhatt"  wrote:

> On Mon, Nov 7, 2016 at 11:12 PM, John R Pierce 
> wrote:
>
> > On 11/7/2016 8:33 PM, Dipal Bhatt wrote:
> >
> >> Unfortunately, there's not possibility in this specific situation to be
> >> able to update from 6.3 -> 6.8.
> >>
> >
> > any such external specifications that insist you run an old obsolete
> > operating system are inherently broken.   I hope this server isn't
> > connected to the internet, and isn't providing any services to untrusted
> > users.
> >
> > any RHEL/CentOS 6 compatible applications you have that work on 6.3 that
> > won't work on 6.8 are broken.
> >
> >  * 6.8's kernel is is still 2.6.32, same as 6.3.
> >  * 6.8's glibc is still 2.12
> >  * 6.8's php is still 5.3
> >  * 6.8's mysql is still 5.1
> >  * 6.8's postgresql is still 8.4
> >  * 6.8's perl is still 5.10
> >  * 6.8's python is still 2.6.6
> >  * etc etc.
> >
> > all of these components have security and bug fixes from later releases
> > backported to them.
>
>
> Excellent, and thanks John to clarify the above compatibility factor.  It
> seems,  any application that strictly depends on the 6.3 packages must not
> be updated to 6.8.  And, outside of that dependency, I gather it should be
> safe to update any hand picked packages to the latest is my understanding
> here. It seems, in general RHEL tries to maintain ABI level compatibility
> but they may not be perfect and they may only test with the packages set
> current at the time.  So, it's worth testing and possibly updating to 6.8
> packages where there's serious security fixes or such.  But, yes, there's
> no way to update the 6.3 to 6.8 as I repeatedly mentioned which is the only
> requirement/constraint.
>
> Thanks again!
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-07 Thread Frank Cox
On Mon, 7 Nov 2016 23:33:56 -0600
Dipal Bhatt wrote:

> But, yes, there's
> no way to update the 6.3 to 6.8 as I repeatedly mentioned which is the only
> requirement/constraint.

It occurs to me to ask what you consider to be version 6.3.  If you update any 
of the rpms to the 6.8 version you are no longer running version 6.3.  If the 
spec requires 6.3 and nothing else, then you will no longer be compatible with 
the spec as soon as you install the first 6.8 rpm.

On the other hand, if you are allowed to install 6.8 rpms, then what's keeping 
you back from doing a proper job instead of a halfway and half-assed one?

Upgrading "selected packages only" will leave you with something that's neither 
fish or fowl, and it won't meet your requirements as stated either.

-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-07 Thread Dipal Bhatt
On Mon, Nov 7, 2016 at 11:12 PM, John R Pierce  wrote:

> On 11/7/2016 8:33 PM, Dipal Bhatt wrote:
>
>> Unfortunately, there's not possibility in this specific situation to be
>> able to update from 6.3 -> 6.8.
>>
>
> any such external specifications that insist you run an old obsolete
> operating system are inherently broken.   I hope this server isn't
> connected to the internet, and isn't providing any services to untrusted
> users.
>
> any RHEL/CentOS 6 compatible applications you have that work on 6.3 that
> won't work on 6.8 are broken.
>
>  * 6.8's kernel is is still 2.6.32, same as 6.3.
>  * 6.8's glibc is still 2.12
>  * 6.8's php is still 5.3
>  * 6.8's mysql is still 5.1
>  * 6.8's postgresql is still 8.4
>  * 6.8's perl is still 5.10
>  * 6.8's python is still 2.6.6
>  * etc etc.
>
> all of these components have security and bug fixes from later releases
> backported to them.


Excellent, and thanks John to clarify the above compatibility factor.  It
seems,  any application that strictly depends on the 6.3 packages must not
be updated to 6.8.  And, outside of that dependency, I gather it should be
safe to update any hand picked packages to the latest is my understanding
here. It seems, in general RHEL tries to maintain ABI level compatibility
but they may not be perfect and they may only test with the packages set
current at the time.  So, it's worth testing and possibly updating to 6.8
packages where there's serious security fixes or such.  But, yes, there's
no way to update the 6.3 to 6.8 as I repeatedly mentioned which is the only
requirement/constraint.

Thanks again!
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-07 Thread John R Pierce

On 11/7/2016 8:33 PM, Dipal Bhatt wrote:

Unfortunately, there's not possibility in this specific situation to be able to 
update from 6.3 -> 6.8.


any such external specifications that insist you run an old obsolete 
operating system are inherently broken.   I hope this server isn't 
connected to the internet, and isn't providing any services to untrusted 
users.


any RHEL/CentOS 6 compatible applications you have that work on 6.3 that 
won't work on 6.8 are broken.


 * 6.8's kernel is is still 2.6.32, same as 6.3.
 * 6.8's glibc is still 2.12
 * 6.8's php is still 5.3
 * 6.8's mysql is still 5.1
 * 6.8's postgresql is still 8.4
 * 6.8's perl is still 5.10
 * 6.8's python is still 2.6.6
 * etc etc.

all of these components have security and bug fixes from later releases 
backported to them.



--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-07 Thread Dipal Bhatt
Thanks Frank and all.
Understood, but unfortunately, updating to latest version of CentOs 6 is
not the option in this specific situation, in stead, we are taking a look
into options of updating only hand picked packages on Centos 6.3 to
latest.  Any other guidance is welcome and appreciated.



On Mon, Nov 7, 2016 at 10:47 PM, Frank Cox 
wrote:

> On Mon, 7 Nov 2016 22:33:22 -0600
> Dipal Bhatt wrote:
>
> > Simply updating these packages on 6.3, would there be any issues w/o
> > updating rest of the packages from 6.3 to 6.8?
>
> I suppose you could try it and see what happens.  That comes with a
> two-part warranty:  If it breaks, you own both pieces.
>
> As you have been told earlier, the only way to update your system properly
> is to run this command:
>
> yum update
>
> After that you will have the latest version of Centos 6 on your system.
>
> Anything other method will leave you with a system that is definitely
> insecure and probably broken.
>
> --
> MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-07 Thread Frank Cox
On Mon, 7 Nov 2016 22:33:22 -0600
Dipal Bhatt wrote:

> Simply updating these packages on 6.3, would there be any issues w/o
> updating rest of the packages from 6.3 to 6.8? 

I suppose you could try it and see what happens.  That comes with a two-part 
warranty:  If it breaks, you own both pieces.

As you have been told earlier, the only way to update your system properly is 
to run this command:

yum update

After that you will have the latest version of Centos 6 on your system.

Anything other method will leave you with a system that is definitely insecure 
and probably broken.

-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-07 Thread Dipal Bhatt
Hi,
Thanks for your responses.
Unfortunately, there's not possibility in this specific situation to be
able to update from 6.3 -> 6.8.  But, it would be nice to be able to update
specific packages to latest that's available in 6.8 repo at

 http://mirror.centos.org/centos/6/os/x86_64/Packages/


For example,

nss-util-3.21.0-2.el6.i686.rpm


2016-05-12 10:48

67K



nss-util-3.21.0-2.el6.x86_64.rpm


2016-05-12 10:47

67K



nss-util-devel-3.21.0-2.el6.i686.rpm


2016-05-12 10:48

69K



nss-util-devel-3.21.0-2.el6.x86_64.rpm


2016-05-12 10:48

69K



Simply updating these packages on 6.3, would there be any issues w/o
updating rest of the packages from 6.3 to 6.8? As I mentioned, 'yum update'
or updating to latest 6.8 packages from 6.3 is not currently plausible or
even feasible for some reason.  Or, please suggest any other options to be
able to update such packages w/o updating rest of the userland on 6.3?

Thank again very much.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-07 Thread John R Pierce

On 11/7/2016 6:03 PM, Dipal Bhatt wrote:

The other option is to use CentOS 6.8 updated package on 6.3, but I am not
sure of any upstream and downstream dependencies in 6.3 without updating
the rest of the userland from 6.3 to 6.8.  Nonetheless, would this option
be feasible?


yum update

will bring the system up to the latest 6 with all updates, currently 
that's 6.8 + assorted updates.


the dot releases of centos, like 6.3, 6.8, are just quarterly(?) rollups 
where they put out a new ISO with all updates to that point.




--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-07 Thread Jonathan Billings
On Nov 7, 2016, at 9:03 PM, Dipal Bhatt  wrote:
> Hi,
> IT seems, centos6.3 does no longer get any updates esp security fixes as
> per readme here:
> http://mirror.centos.org/centos/6.3/readme 
> 

I believe there’s some confusion about how CentOS release versions work.

You should read this FAQ entry:

https://wiki.centos.org/FAQ/General#head-dcca41e9a3d5ac4c6d900a991990fd11930867d6
 


Basically, there is no supported CentOS 6.3 release.  Only a CentOS 6, with 
updates continuously released throughout its lifetime.  Just because you used 
the installation media for CentOS 6.3 doesn’t mean that you will stay with it 
forever.  You should change your repos to use /6/ and update to the latest 
release.  There’s no other supported release of CentOS 6.

Your system is horribly out of date and vulnerable to many MANY security 
vulnerabilities, both remote and local.

Red Hat supported the EUS release of 6.3.z but even that ceased getting updates 
a while ago, I believe.  I’m sure if you pay them enough money, they’d be 
willing to backport updates to 6.3.

--
Jonathan Billings 


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] CentOS 6.3 packages updates options without upgrading.

2016-11-07 Thread Dipal Bhatt
Hi,
IT seems, centos6.3 does no longer get any updates esp security fixes as
per readme here:
http://mirror.centos.org/centos/6.3/readme

Is there updated source RPMs that can be rebuilt and hand patched, for
example, nss-util 3.21.0-2 or openssl 1.0.1e that can be safely used on
CentOS 6.3? Any other options that you can shed some light on, highly
appreciated for above examples.  My apologies if this is not the right
group to post such questions or if any existing literature available for
same, please kindly refer to right place.

The other option is to use CentOS 6.8 updated package on 6.3, but I am not
sure of any upstream and downstream dependencies in 6.3 without updating
the rest of the userland from 6.3 to 6.8.  Nonetheless, would this option
be feasible?

Appreciated very much, Thank you.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] centos 6.3

2014-12-02 Thread John R Pierce

On 12/1/2014 11:29 PM, Hadi Motamedi wrote:

I want to put my stuff on centos 6.3 but some colleagues warned that
it is not wise to use it at now for some bugs reported. Can you please
confirm if this is true and which vulnerability can be risked for ?



As the others said, the OS is CentOS 6...   6.3 was simply a 
snapshot of the updates as of July 2012.  As soon as you update it with 
current fixes ('yum update') you'll be on the current point release, 
which is CentOS 6.6 at the moment.


As has been pointed out several times here, you should NOT assume you 
can just install individual fixes such as the latest openssl for the 
heartbeat fixes, and so forth, as these have only been tested running 
with ALL the latest packages, not every conceivable combination of 
component versions over the past 4 years or so.





--
john r pierce  37N 122W
somewhere on the middle of the left coast

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] centos 6.3

2014-12-02 Thread Hadi Motamedi

 As has been pointed out several times here, you should NOT assume you
 can just install individual fixes such as the latest openssl for the
 heartbeat fixes, and so forth, as these have only been tested running
 with ALL the latest packages, not every conceivable combination of
 component versions over the past 4 years or so.




 --
 john r pierce  37N 122W
 somewhere on the middle of the left coast

 ___

Please let me to post my special thanks to you as your comments solved
my problem. Thank you again for assigning your valuable time and
experience .
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] centos 6.3

2014-12-01 Thread Hadi Motamedi
Dear All
I want to put my stuff on centos 6.3 but some colleagues warned that
it is not wise to use it at now for some bugs reported. Can you please
confirm if this is true and which vulnerability can be risked for ?
Thank you
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] centos 6.3

2014-12-01 Thread Mihamina Rakotomandimby

On 12/02/2014 10:29 AM, Hadi Motamedi wrote:

Dear All
I want to put my stuff on centos 6.3 but some colleagues warned that
it is not wise to use it at now for some bugs reported. Can you please
confirm if this is true and which vulnerability can be risked for ?



It is generally unsafe to run a outdated operating system.
Whatever it is.
What are your constraints not to upgrade to the latests 6.6?

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] centos 6.3

2014-12-01 Thread Fabian Arrotin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/12/14 08:29, Hadi Motamedi wrote:
 Dear All I want to put my stuff on centos 6.3 but some colleagues
 warned that it is not wise to use it at now for some bugs reported.
 Can you please confirm if this is true and which vulnerability can
 be risked for ? Thank you

matrix modeThere is no 6.3/matrix mode ..
One thing you have to realize is that there is only CentOS 6, and
minor releases that combine security/bugfixes at a certain point in
time.
So take whatever CentOS 6.x distro, do a yum update on it and it
will automatically jump to $actual_version (so 6.6+packages updated
post 6.6 release)

Of course, one can argue that he can just stick with a particular
release (by modifying yum or even not running yum update at all) but
then it's another game, as it means no security update[s] at all, with
all the possible consequences ..

- -- 

Fabian Arrotin
The CentOS Project | http://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlR9a4IACgkQnVkHo1a+xU6TgwCcCQ1RDLGS31pmmySDTtaIIH/J
esgAnRPOgfloAuyZfvwGEA2SWylPGk5U
=4DQK
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] centos 6.3

2014-12-01 Thread Digimer

On 02/12/14 02:29 AM, Hadi Motamedi wrote:

Dear All
I want to put my stuff on centos 6.3 but some colleagues warned that
it is not wise to use it at now for some bugs reported. Can you please
confirm if this is true and which vulnerability can be risked for ?
Thank you


The heartbleed and shellshock bugs are worth upgrading for themselves. 
In any case, there really is no reason to stay on 6.3, it's quite old now.


--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without 
access to education?

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] [centos-6.3-desktop] Unable to login

2013-04-24 Thread Mayur Patil
Thanks to especially Mark Sir.

After *yum -y update* system is now enjoying GUI !!

One thing to mention is that my system processing also increases
considerably !!

Thanks again to All !!

-- 
*Cheers,
Mayur*.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] [centos-6.3-desktop] Unable to login

2013-04-23 Thread Mayur Patil
Hello,

  I have done following steps:

   Press Ctrl+Alt+F2

   By root login, I entered following command :

yum groupinstall basic-desktop desktop-platform x11 fonts

   Then I reboot system; only blank screen appears ; not even cursor.

   Then I tried this :

   yum groupinstall -y ' X Windows System'

   yum groupinstall -y ' Desktop '

   Then I open */etc/inittab* via text editor and change following line:

id:3:initdefault:

To:

id:5:initdefault:

Then give command to start the GUI:

$ init 5
but screen stop responding after giving message  Starting jexec
services .

   After that I reboot system, Then I run.

   $ startx

   It has loaded some packages but failed to load and stop there.

   Then I tried this gnome-session, gnome-panel and gnome-applets.

   It has said everything is installed.

   After this, I tried this:

   yum -y groupinstall X Window System Desktop Fonts General Purpose
Desktop

   upto 83 MB installation Then I reboot and entered startx

it has given following error and stopped

   Loading extension GLX
   FATAL: Module fbcon not found.
   [dix] Could not init font path element catalogue:/etc/X11/fontpath.d,
removing from list!
   [dix] Could not init font path element built-ins, removing from list!

   Fatal server error: could not open default font 'fixed'
   (EE) Please consult the CentOS support  at
http://wiki.centos.org/Documentation  for help.
   (EE) Please also check the log file at /var/log/Xorg.0.log for
additional information.
   (EE) Server terminated with error (1). Closing log file.
   [89.274] (EE)
   [89.274] (II) AIGLX: Suspending AIGLX clients for VT switch

   Now as the last measure, I have run the

  yum -y update

   today itself. 243 MB, will get complete tomorrow (as per I hope).

   I have google for this but not find confirm solution.

   Am I missing something; please help ??

  Seeking for guidance,

  Thank you !!!

-- 
*Cheers,
Mayur*.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] [centos-6.3-desktop] Unable to login

2013-04-23 Thread Tilman Schmidt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am 23.04.2013 16:49, schrieb Mayur Patil:
 Hello,
 
 I have done following steps:
[...]
 I have google for this but not find confirm solution.
 
 Am I missing something; please help ??
 
 Seeking for guidance,

It is virtually impossible to deduce from your description what's
wrong with your machine. You should find someone in your vicinity who
knows
Linux and can have a direct look.

HTH
T.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlF2/rAACgkQ780oymN0g8NhzACfahGgKlEH2kjrB20toC+ALm+t
ynEAnioqWOCRTsTX7SZX81ofp1gaahjv
=Wlar
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] [centos-6.3-desktop] Unable to login

2013-04-23 Thread Cliff Pratt
You should not have removed the i686 packages. The packaging system ensures
that there are no conflicts. I suggest that you reinstall them. It may be
that there is no need of them, but second-guessing the packaging system is
never a good idea, unless you know *exactly* what you are doing.

Cheers,

Cliff


On Tue, Apr 23, 2013 at 1:26 AM, Mayur Patil ram.nath241...@gmail.comwrote:

 Hello,

  I have trapped in weird problem. My Setup is CentOS 6.3 Desktop edition
 x86_64 arch.

  My login screen is blinking so frequently that I am unable to see and
 login into it.

  And also I am unable to reinstall the OS because it will take very long
 time re-setup everything as per my configuration as well as Data.

  The problem is as follows:

  I have several months ago libgcc-4.4.6.i686.

  Today for installing rsyslog, I updated the package libgcc-4.4.7.i686 and
 libgcc-4.4.7.x86_64. Then thinking

  about chances of conflict, I removed libgcc-4.4.7.i686  it has also
 removed the

  cups-libs
  gmp
  gnutils
  gtk2
  libstdc++
  libtiff
  peazip

  all are i686 type. Then I installed same packages for 64 bit through yum
 install above packages

  Message also said successfully installed. Then I try to open another
 terminal window but it was suddenly closing

  so I thought restart might solve this problem; so I restart the computer.

  I am getting normal CentOS login backgroud but getting faster blinking
 screen.

  How should I solve this problem (except formatting the CentOS) as CentOS
 is the only OS on that machine.

  1. How to login into CentOS now??

  2. Which package should I need to install and how ??

  Kindly do the needful,

  Thank you !!

 *--
 Cheers,
 Mayur. *
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] [centos-6.3-desktop] Unable to login

2013-04-22 Thread Mayur Patil
Hello,

 I have trapped in weird problem. My Setup is CentOS 6.3 Desktop edition
x86_64 arch.

 My login screen is blinking so frequently that I am unable to see and
login into it.

 And also I am unable to reinstall the OS because it will take very long
time re-setup everything as per my configuration as well as Data.

 The problem is as follows:

 I have several months ago libgcc-4.4.6.i686.

 Today for installing rsyslog, I updated the package libgcc-4.4.7.i686 and
libgcc-4.4.7.x86_64. Then thinking

 about chances of conflict, I removed libgcc-4.4.7.i686  it has also
removed the

 cups-libs
 gmp
 gnutils
 gtk2
 libstdc++
 libtiff
 peazip

 all are i686 type. Then I installed same packages for 64 bit through yum
install above packages

 Message also said successfully installed. Then I try to open another
terminal window but it was suddenly closing

 so I thought restart might solve this problem; so I restart the computer.

 I am getting normal CentOS login backgroud but getting faster blinking
screen.

 How should I solve this problem (except formatting the CentOS) as CentOS
is the only OS on that machine.

 1. How to login into CentOS now??

 2. Which package should I need to install and how ??

 Kindly do the needful,

 Thank you !!

*--
Cheers,
Mayur. *
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] [centos-6.3-desktop] Unable to login

2013-04-22 Thread Mayur Patil
Hello,

One more thing as per I think I have lost only file which responsible for
GUI of the centos.

If anyone has Idea which files I need to get Login and other explorer
screen back in action

that will be a great help to me.

And I also want to ask that is it possible to install that files from
Putty; I have windows on other PC

so that from terminal there I can install on centos machine??

Waiting for your reply,

Thanks !!
-- 
*Cheers,
Mayur*.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] [centos-6.3-desktop] Unable to login

2013-04-22 Thread m . roth
Mayur Patil wrote:
 Hello,

 One more thing as per I think I have lost only file which responsible for
 GUI of the centos.

 If anyone has Idea which files I need to get Login and other explorer
 screen back in action

There is no explorer - that's a Windows thing. You should have command
line login using ctrlaltf2

I skimmed your other email - a) did you install for 64 bit? b) did I see
that you tried picking and choosing from what release? In any case, you
need to do
yum -y update
and update your whole system to current.

If you're still having gui problems, you *might* have a driver issue. What
video do you have?
nsip
 And I also want to ask that is it possible to install that files from
 Putty; I have windows on other PC

There are no putty files to install on Linux. Putty will bring you in as
though you had ssh'd from another *Nix machine.
snip
 mark

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] [centos-6.3-desktop] Unable to login

2013-04-22 Thread Mayur Patil
Hello Sir,


  One more thing as per I think I have lost only file which responsible for
  GUI of the centos.
  If anyone has Idea which files I need to get Login and other explorer
 screen back in action

 There is no explorer - that's a Windows thing. You should have command
 line login using ctrlaltf2


  Problem is Appearance of login window. System boots normally; now I will
try out your said command.

I skimmed your other email - a) did you install for 64 bit?


   Yes.

b) did I see that you tried picking and choosing from what release?


   Release 6.3


 In any case, you  need to do
 yum -y update and update your whole system to current.


   Problem is I have installed Eucalyptus cloud,Snort IDS and now rSyslog ;
so I am in fear that update

   should not break anything wrt this components so that weird things I
will face in future.

   BTW, system is working fine before this incident.


 If you're still having gui problems, you *might* have a driver issue. What
 video do you have?

nsip


  I have not installed any video drivers before this. I tried to install
one but it does not work. So I leave it as

  everything was working fine before breakage of libgcc.686  package
dependencies (as I remember)


  And I also want to ask that is it possible to install that files from
  Putty; I have windows on other PC

There are no putty files to install on Linux. Putty will bring you in as
 though you had ssh'd from another *Nix machine.
 snip


  I am in SSH with this machine from long time. I am asking if I am unable
to get GUI then I should try to install files

  from PUTTY terminal or browse files with WinSCP.

 What is your opinion sir??

 Waiting for guidance,

 Thanks!!


 mark

-- 
*Cheers,
Mayur*.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] [centos-6.3-desktop] Unable to login

2013-04-22 Thread m . roth
Mayur Patil wrote:

  One more thing as per I think I have lost only file which responsible
 for GUI of the centos.
  If anyone has Idea which files I need to get Login and other explorer
 screen back in action

 There is no explorer - that's a Windows thing. You should have command
 line login using ctrlaltf2


   Problem is Appearance of login window. System boots normally; now I will
 try out your said command.

gnome or kde?
snip

 In any case, you  need to do
 yum -y update and update your whole system to current.


  Problem is I have installed Eucalyptus cloud,Snort IDS and now rSyslog;
 so I am in fear that update

It shouldn't. And why did you install rsyslog? That's the default system
log package in 6.x. Did you install that from something else?

You'll probably have to run whatever snort command once you do a yum
update, or I expect you'll get a lot of false warnings.
nsip
 If you're still having gui problems, you *might* have a driver issue.
 What
 video do you have?

 nsip

   I have not installed any video drivers before this. I tried to install
 one but it does not work. So I leave it as

You really, REALLY need to do some reading about *Nix systems. The base
install installs video drivers; if you add a desktop install, it will
install its best guess at drivers - they're already there. Unless you've
got multiple monitors, in which case you may well have trouble, then the
gui should just work.

   everything was working fine before breakage of libgcc.686  package
 dependencies (as I remember)
snip
   I am in SSH with this machine from long time. I am asking if I am unable
 to get GUI then I should try to install files

Wait - how are you trying to log in, from the console, or remotely?
snip
  mark

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] [centos-6.3-desktop] Unable to login

2013-04-22 Thread Mayur Patil
Hello Sir, sorry for late reply.

 One more thing as per I think I have lost only file which responsible

 for GUI of the centos.
   If anyone has Idea which files I need to get Login and other explorer
  screen back in action
 
  There is no explorer - that's a Windows thing. You should have command
  line login using ctrlaltf2
 
 
Problem is Appearance of login window. System boots normally; now I
 will
  try out your said command.

 gnome or kde?
 snip


  Gnome.


   In any case, you  need to do
  yum -y update and update your whole system to current.
 
   Problem is I have installed Eucalyptus cloud,Snort IDS and now rSyslog;
  so I am in fear that update

It shouldn't. And why did you install rsyslog? That's the default system
 log package in 6.x.


   I think sir you are talking abt CentOS 6.4 becoz in centos 6.3 there is
upto 5.8.10.

Did you install that from something else?

I am installing from source version 7.2.6 because of which this all
mess.

You'll probably have to run whatever snort command once you do a yum
 update, or I expect you'll get a lot of false warnings.
 nsip


  I will try for it.


  If you're still having gui problems, you *might* have a driver issue.
  What
  video do you have?
 
  nsip
 
I have not installed any video drivers before this. I tried to install
  one but it does not work. So I leave it as

 You really, REALLY need to do some reading about *Nix systems. The base
 install installs video drivers; if you add a desktop install, it will
 install its best guess at drivers - they're already there. Unless you've
 got multiple monitors, in which case you may well have trouble, then the
 gui should just work.
 
everything was working fine before breakage of libgcc.686  package
  dependencies (as I remember)
 snip
I am in SSH with this machine from long time. I am asking if I am
 unable
  to get GUI then I should try to install files
 Wait - how are you trying to log in, from the console, or remotely?
 snip


  I will first try out your instructions ; if that works. No remote no
console.

  If not, then I will try to login from Putty - windows client. And sir,

  would you please more focus on *nix systems?? any link??

  And could you briefly address me what is actual mess around here??

  Waiting for reply,

  Thanks !!


 mark


*--*
*Cheers,
Mayur*.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] [centos-6.3-desktop] Unable to login

2013-04-22 Thread m . roth
Mayur Patil wrote:
 One more thing as per I think I have lost only file which responsible
 for GUI of the centos.
 You should have command line login using ctrlaltf2
 
Problem is Appearance of login window. System boots normally; now I
  will try out your said command.

 gnome or kde?
 snip

   Gnome.

   In any case, you  need to do yum -y update and update your whole
   system to current.
 
   Problem is I have installed Eucalyptus cloud,Snort IDS and now
 rSyslog; so I am in fear that update

 It shouldn't. And why did you install rsyslog? That's the default system
 log package in 6.x.


I think sir you are talking abt CentOS 6.4 becoz in centos 6.3 there is
 upto 5.8.10.

You. Do. Not. Understand. What. I. Am. Saying. You need to stop and THINK
while you're reading. rsyslog is the default syslog in ALL VERSIONS of
CentOS 6.


  If you're still having gui problems, you *might* have a driver issue.
  What video do you have?
 
  nsip
 
I have not installed any video drivers before this. I tried to
 install
  one but it does not work. So I leave it as

 You really, REALLY need to do some reading about *Nix systems. The base
 install installs video drivers; if you add a desktop install, it will
 install its best guess at drivers - they're already there. Unless you've
 got multiple monitors, in which case you may well have trouble, then the
 gui should just work.
 
everything was working fine before breakage of libgcc.686  package
  dependencies (as I remember)
 snip
I am in SSH with this machine from long time. I am asking if I am
  unable to get GUI then I should try to install files

 Wait - how are you trying to log in, from the console, or remotely?
 snip

   I will first try out your instructions ; if that works. No remote no
 console.

   If not, then I will try to login from Putty - windows client. And sir,

   would you please more focus on *nix systems?? any link??

   And could you briefly address me what is actual mess around here??

I don't think I'll respond again. I feel as though you do *NOT* understand
linux (or any other version of Unix, usually referred to as *Nix). Go read
the FAQ from the centos website. Go read wikipedia.

I'm tired of making suggestions, and you don't have a clue as to what I'm
asking or suggesting.

I'm at work, for which I am a senior person, and get paid for that. I feel
like I'm wasting time trying to help you.

Try googling for answers, before you post, or if you don't understand some
of the suggestions.

  mark

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] [centos-6.3-desktop] Unable to login

2013-04-22 Thread Mayur Patil
Hello Mark Sir,

   Sorry if you feel bad due to my foolishness and inadequate knowledge.

   My actual problem is that my setup is at college and due to internet
connectivity

   problems as well as college hours are over, I am responding from home.

   So as per your instructions I will again go thoroughly through your
replies.

   And I hope that I won't try to disturb you.

   Sorry for my foolishness,

   Thanks for your help !!

  One more thing as per I think I have lost only file which responsible
  for GUI of the centos.
  You should have command line login using ctrlaltf2
  
 Problem is Appearance of login window. System boots normally; now I
   will try out your said command.
 
  gnome or kde?
  snip
 
Gnome.
 
In any case, you  need to do yum -y update and update your whole
system to current.
  
Problem is I have installed Eucalyptus cloud,Snort IDS and now
  rSyslog; so I am in fear that update
 
  It shouldn't. And why did you install rsyslog? That's the default system
  log package in 6.x.
 
 
 I think sir you are talking abt CentOS 6.4 becoz in centos 6.3 there
 is
  upto 5.8.10.

 You. Do. Not. Understand. What. I. Am. Saying. You need to stop and THINK
 while you're reading. rsyslog is the default syslog in ALL VERSIONS of
 CentOS 6.
 


 Yes Sir got it.Now I understand no need to reinstall rsyslog just use
default one.
  How foolish I am !!

   If you're still having gui problems, you *might* have a driver issue.
   What video do you have?
   nsip
 I have not installed any video drivers before this. I tried to
  install
   one but it does not work. So I leave it as



  You really, REALLY need to do some reading about *Nix systems. The base
  install installs video drivers; if you add a desktop install, it will
  install its best guess at drivers - they're already there. Unless you've
  got multiple monitors, in which case you may well have trouble, then the
  gui should just work.
  
 everything was working fine before breakage of libgcc.686  package
   dependencies (as I remember)
  snip
 I am in SSH with this machine from long time. I am asking if I am
   unable to get GUI then I should try to install files

  Wait - how are you trying to log in, from the console, or remotely?
  snip
 
I will first try out your instructions ; if that works. No remote no
  console.
 
If not, then I will try to login from Putty - windows client. And sir,
 
would you please more focus on *nix systems?? any link??
 
And could you briefly address me what is actual mess around here??
 
 I don't think I'll respond again. I feel as though you do *NOT* understand
 linux (or any other version of Unix, usually referred to as *Nix). Go read
 the FAQ from the centos website. Go read wikipedia.

 I'm tired of making suggestions, and you don't have a clue as to what I'm
 asking or suggesting.

 I'm at work, for which I am a senior person, and get paid for that. I feel
 like I'm wasting time trying to help you.

 Try googling for answers, before you post, or if you don't understand some
 of the suggestions.

   mark

-- 
*Cheers,
Mayur*.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] [centos-6.3-desktop] Unable to login

2013-04-22 Thread Mayur Patil
Hello,

  My X windows system is not working

  So, Mark sir has recommended following steps that what I understand:

1 Press ctrl+alt+f2

2. Then run these commands

 yum groupinstall basic-desktop desktop-platform

 install installs video drivers; if you add a desktop install, it will
 install its best guess at drivers - they're already there. Unless
you've
 got multiple monitors, in which case you may well have trouble, then
the
 gui should just work.

 3. After that  I should perform

   yum -y update

4. Then I should run command for snorts.

 If anyone finds any lacunae please guide

Thanks !!

*-- *
*Cheers,
Mayur*.

 You should have command line login using ctrlaltf2

  
 Problem is Appearance of login window. System boots normally; now I
   will try out your said command.
 
  gnome or kde?
  snip
 
Gnome.
 
In any case, you  need to do yum -y update and update your whole
system to current.
  
Problem is I have installed Eucalyptus cloud,Snort IDS and now
  rSyslog; so I am in fear that update
 
  It shouldn't. And why did you install rsyslog? That's the default system
  log package in 6.x.
 
 
 I think sir you are talking abt CentOS 6.4 becoz in centos 6.3 there
 is
  upto 5.8.10.

 You. Do. Not. Understand. What. I. Am. Saying. You need to stop and THINK
 while you're reading. rsyslog is the default syslog in ALL VERSIONS of
 CentOS 6.
 


  Yes Sir got it.Now I understand no need to reinstall rsyslog just use
 default one.
   How foolish I am !!

If you're still having gui problems, you *might* have a driver
 issue.
   What video do you have?
   nsip
 I have not installed any video drivers before this. I tried to
  install
   one but it does not work. So I leave it as



  You really, REALLY need to do some reading about *Nix systems. The base
  install installs video drivers; if you add a desktop install, it will
  install its best guess at drivers - they're already there. Unless
 you've
  got multiple monitors, in which case you may well have trouble, then
 the
  gui should just work.
  
 everything was working fine before breakage of libgcc.686  package
   dependencies (as I remember)
  snip
 I am in SSH with this machine from long time. I am asking if I am
   unable to get GUI then I should try to install files

  Wait - how are you trying to log in, from the console, or remotely?
  snip
 
I will first try out your instructions ; if that works. No remote no
  console.
 
If not, then I will try to login from Putty - windows client. And sir,
 
would you please more focus on *nix systems?? any link??
 
And could you briefly address me what is actual mess around here??
 
 I don't think I'll respond again. I feel as though you do *NOT* understand
 linux (or any other version of Unix, usually referred to as *Nix). Go read
 the FAQ from the centos website. Go read wikipedia.

 I'm tired of making suggestions, and you don't have a clue as to what I'm
 asking or suggesting.

 I'm at work, for which I am a senior person, and get paid for that. I feel
 like I'm wasting time trying to help you.

 Try googling for answers, before you post, or if you don't understand some
 of the suggestions.

   mark


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] CentOS 6.3 gpgv: Libgcrypt warning: missing initialization - please fix the application

2013-04-15 Thread P J
Howdy,

Seemingly randomly every day the following appears in /var/log/messages

gpgv: Libgcrypt warning: missing initialization - please fix the application
gpgv: Libgcrypt warning: missing initialization - please fix the application
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 gpgv: Libgcrypt warning: missing initialization - please fix the application

2013-04-15 Thread P J
Ahh, premature send! My apologies.

Seemingly random times every day the following appears in /var/log/messages

gpgv: Libgcrypt warning: missing initialization - please fix the application
gpgv: Libgcrypt warning: missing initialization - please fix the application
--snip--

Anyone have any insight on what could be causing this and how to fix it?

locate gpgv
/usr/bin/gpgv
/usr/bin/gpgv2

rpm -qf /usr/bin/gpgv
gnupg2-2.0.14-4.el6.x86_64

rpm -qf /usr/bin/gpgv2
gnupg2-2.0.14-4.el6.x86_64

Thanks in advance!




On Mon, Apr 15, 2013 at 11:16 AM, P J pauljfli...@gmail.com wrote:

 Howdy,

 Seemingly randomly every day the following appears in /var/log/messages

 gpgv: Libgcrypt warning: missing initialization - please fix the
 application
 gpgv: Libgcrypt warning: missing initialization - please fix the
 application

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 gpgv: Libgcrypt warning: missing initialization - please fix the application

2013-04-15 Thread P J
If it helps, I figured out the application causing the error message.
It's Ksplice's uptrace-upgrade which runs via cron...

Still not sure what the solution is, or if this error is benign.


On Mon, Apr 15, 2013 at 11:18 AM, P J pauljfli...@gmail.com wrote:

 Ahh, premature send! My apologies.

 Seemingly random times every day the following appears in /var/log/messages

 gpgv: Libgcrypt warning: missing initialization - please fix the
 application
 gpgv: Libgcrypt warning: missing initialization - please fix the
 application
 --snip--

 Anyone have any insight on what could be causing this and how to fix it?

 locate gpgv
 /usr/bin/gpgv
 /usr/bin/gpgv2

 rpm -qf /usr/bin/gpgv
 gnupg2-2.0.14-4.el6.x86_64

 rpm -qf /usr/bin/gpgv2
 gnupg2-2.0.14-4.el6.x86_64

 Thanks in advance!




 On Mon, Apr 15, 2013 at 11:16 AM, P J pauljfli...@gmail.com wrote:

 Howdy,

 Seemingly randomly every day the following appears in /var/log/messages

 gpgv: Libgcrypt warning: missing initialization - please fix the
 application
 gpgv: Libgcrypt warning: missing initialization - please fix the
 application



___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] centos 6.3 ipv6 default gateway

2013-04-13 Thread Michael H. Warfield
On Fri, 2013-04-12 at 11:38 +0800, Jaze Lee wrote:
 2013/4/12 Michael H. Warfield m...@wittsend.com

Big snip...

  You are, none the less, not suppose to use addresses in that block for
  ANYTHING.  The fc00::/7 block is intended for what you want to do.  Even
  if they happen to work, they are not guaranteed to work and may cause
  other problems (like reverse DNS lookup traffic).

Currently, i just use those ipv6 address to set up my testing
 environment. One day
they will be replaced by global ipv6 address. And i do not have any
 global ipv6 address right now,
i have to use some thing like 1:2:3::4. They truely work on ubuntu
 12.04, so i think they should work on
centos.

That last statement is incorrect.  Just because they work on Ubuntu
doesn't guarantee they will work on CentOS, Scientific Linux, Fedora, or
Redhat Enterprise, if they do not adhere to the proper standards.  You
are in an area that should be considered undefined behavior where it
might work or it might not but, if it doesn't, it's your fault not that
of the system.  Although, in this case, this seems to have been more of
a configuration error/confusion issue between how the systems are
configured.

 But now, i realize i am wrong, what about i change the
 1:2:3:4/64 to fc:2:3::4/64 ?
Is that ok?

No.  Strictly speaking, it should be fc00:2:3::4/64.  The prefix for
local unicast is fc00:: or fd00::, not fc::.  It's fc00 not fc.

   Must i change ipv6 address to some thing like 2000::/3, even i just want
  to
   use ipv6 for private?
 
  No, you should change them to FC00:/7 for private use.  That's what that
  block was allocated for.  Use it.  Don't just dream up stuff.
 
  You will need static routes on each of your two routers for your two
  client routes.
 

   I change ipv6 address to this:

 DEVICE=eth2   - in centosv0
 BOOTPROTO=static
 HWADDR=60:A4:4C:23:2F:4F
 NM_CONTROLLED=yes
 ONBOOT=yes
 TYPE=Ethernet
 #UUID=97d250ea-74db-47ae-bd8c-6682f57f9add
 IPV6INIT=yes
 IPV6ADDR=fc00:2:3::5/64
 IPV6_DEFAULTGW=fc00:2:3::4

 DEVICE=eth1 - in centosv0
 BOOTPROTO=static
 HWADDR=60:A4:4C:23:2F:4E
 NM_CONTROLLED=yes
 ONBOOT=yes
 TYPE=Ethernet
 #UUID=f7f020e9-36a4-4f55-9ed2-81acc2dbd92f
 IPV6INIT=yes
 IPV6ADDR=fc00:2:3:5::1/64

 DEVICE=eth1  --- in centosv1
 BOOTPROTO=static
 HWADDR=60:A4:4C:23:2F:6E
 NM_CONTROLLED=yes
 ONBOOT=yes
 TYPE=Ethernet
 #UUID=3597af05-199b-4eef-9a24-610c2872f313
 IPV6INIT=yes
 IPV6ADDR=fc00:2:3:4::1/64

 DEVICE=eth2 --- in centosv1
 BOOTPROTO=static
 HWADDR=60:A4:4C:23:2F:6F
 NM_CONTROLLED=yes
 ONBOOT=yes
 TYPE=Ethernet
 #UUID=0ddcf499-878f-4ac7-9d1a-c27f85d2bccf
 IPV6INIT=yes
 IPV6ADDR=fc00:2:3::4/64
 IPV6_DEFAULTGW=fc00:2:3::5

 and restart the network:
 [root@centosv0 network-scripts]# /etc/init.d/network restart
 Shutting down interface eth1:  [  OK  ]
 Shutting down interface eth2:  [  OK  ]
 Shutting down interface eth3:  [  OK  ]
 Shutting down loopback interface:  [  OK  ]
 Bringing up loopback interface:[  OK  ]
 Bringing up interface eth1:[  OK  ]
 Bringing up interface eth2:[  OK  ]
 Bringing up interface eth3:[  OK  ]

 It work now, thanks a lot, lot, lot

Great!  Good to see you've made progress!

 Now, why ubuntu 12.04 and centos 6.3 are so different?
 Is that because ubunutu 12.04 uses 3.5 kernel, and centos uses 2.6.32 ?

No.  Actually I suspect it's more in the supporting scripts and
infrastructure.  The RedHat base distros (RH, Fedora, CentOS, SL, NST,
etc) and the Debian based distros (Ubuntu, Knoppix, Backtrack, etc) have
based their network support on different paradigms (and is probably the
PRIMARY reason why I dislike Debian, Knoppix and Ubuntu in their network
code).

Historically, the RH based system is (VERY) loosely based on some of the
ideas that evolved out of the ATT SYSV system with separate
configuration files, the classical init scripts are still referred to as
the sysv-init stuff, and what not.  NetworkManager aka NetworkMangler
and systemd are throwing all that for a loop lately with some
improvements and some abject debacles.

OTOH, Debian was more in-line with the BSD (Berkeley Software
Distribution) philosophy and their network interfaces and a common init
configuration file.

The RH derivative scripts for IPv6 support are largely based on the work
of Peter Bieringer in the ipv6init scripts (to which I had some minor
input and contributions).  I honestly don't know what Debian / Ubuntu is
using but there are some very significant deviations in behavior and
filtering in that arena.  It's not at all just a kernel issue.

I've done some internal distributions based on both paradigms (one
based on 

[CentOS] centos 6.3 ipv6 default gateway

2013-04-11 Thread Jaze Lee
hello,
   i met a problem in configuratiion of ipv6 gw in my box
i install centos 6.3 (64 bit) on my boxs, which have four netcard.
i use a straight-through cable to connect centosv0:netcard-2 and
centosv1:netcard2
the topology is this:
client c(windows xp) --centosv0:netcard-3 -- centosv0:netcard-2 ---
centosv1:netcard-2 centosv1:netcard-2  --- client d (backtrack r2
32)
1:2:3:4::2/64  1:2:3:4::1/64   1:2:3::4/64
  1:2:3::5/64 1:2:3:5::1/64
 1:2:3:5::2/64

what i want to do is set default gw on centosv0 to centosv1

i configure /etc/sysconfig/network-scripts/ifconfig-eth2  (centosv0) as this
DEVICE=eth2
BOOTPROTO=static
HWADDR=60:A4:4C:23:2F:6F
NM_CONTROLLED=yes
ONBOOT=yes
TYPE=Ethernet
#UUID=0ddcf499-878f-4ac7-9d1a-c27f85d2bccf
IPV6INIT=yes
IPV6ADDR=1:2:3::4
IPV6_DEFAULTGW=1:2:3::5

and i also configure /etc/sysconfig/network to this:
NETWORKING=yes
HOSTNAME=centosv0
NETWORKING_IPV6=yes
IPV6_AUTOCONF=no

but i met an error:
Bringing up interface eth2:  WARN : [ipv6_add_route] Unknown error

i do not know how why,and can some one gives me some suggestion?
thanks a lot.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] centos 6.3 ipv6 default gateway

2013-04-11 Thread Michael H. Warfield
Hello,

I may be totally off base here but...

On Thu, 2013-04-11 at 18:06 +0800, Jaze Lee wrote:
 hello,
i met a problem in configuratiion of ipv6 gw in my box
 i install centos 6.3 (64 bit) on my boxs, which have four netcard.
 i use a straight-through cable to connect centosv0:netcard-2 and
 centosv1:netcard2
 the topology is this:
 client c(windows xp) --centosv0:netcard-3 -- centosv0:netcard-2 ---
 centosv1:netcard-2 centosv1:netcard-2  --- client d (backtrack r2
 32)
 1:2:3:4::2/64  1:2:3:4::1/64   1:2:3::4/64
   1:2:3::5/64 1:2:3:5::1/64
  1:2:3:5::2/64

Surely, I hope you jest with those numbers.  You are not allowed to pick
numbers out of the air and just use them, even if it's for private use.
There are specific blocks of addresses for specific uses and assigned
scopes and all the private use addresses are in blocks very high up
in the address space beginning with fc or fd.  If those are literally
the addresses you used, they will not work and I would expect them to
give you all sorts of grief at some point or another.

 what i want to do is set default gw on centosv0 to centosv1

I take it centosv0  and centosv1 are configured for ipv6 forwarding?
You didn't provide the information on that.  There are some gotcha's in
there with default routing on a router (basically there is no such
thing) and the router needs to be set up properly for both routing and
its routes.  But I don't think that's your problem you're describing
down below.

 i configure /etc/sysconfig/network-scripts/ifconfig-eth2  (centosv0) as this
 DEVICE=eth2
 BOOTPROTO=static
 HWADDR=60:A4:4C:23:2F:6F
 NM_CONTROLLED=yes
 ONBOOT=yes
 TYPE=Ethernet
 #UUID=0ddcf499-878f-4ac7-9d1a-c27f85d2bccf
 IPV6INIT=yes
 IPV6ADDR=1:2:3::4
 ^^ You didn't specify a netmask here (default /128).

 IPV6_DEFAULTGW=1:2:3::5
  Technically not on your interface's network (/128)

 and i also configure /etc/sysconfig/network to this:
 NETWORKING=yes
 HOSTNAME=centosv0
 NETWORKING_IPV6=yes
 IPV6_AUTOCONF=no

For forwarding...

In that file you're also going to need:

IPV6FORWARDING=yes

You may also need to add lines to /etc/sysctl.conf (I've needed in the
past on Fedora):

net.ipv6.conf.all.forwarding = 1
net.ipv6.conf.default.forwarding = 1

But those aren't your problem with this...

 but i met an error:
 Bringing up interface eth2:  WARN : [ipv6_add_route] Unknown error

I'm not totally sure if this is because you didn't specify a prefix
length on your IPV6ADDR line or the fact that it then conflicted with
your IPV6_DEFAULTGW which would not have been on 1:2:3::4/128 or if it
was because you choose and illegal IPv6 prefix or if it was a
combination of all of them.  The WARN: [ipv6_add_route] Unknown error
makes me suspicious because your default gatway conflicts with your
interface network definition (because you didn't specify the prefix size
and it defaulted to /128) and the kernel has no way to route it out any
interface.  IAC...  You won't be able to use a default route on a router
anyways (more below).

 i do not know how why,and can some one gives me some suggestion?
 thanks a lot.

If those were literally the addresses you used, It may be an address
that's in an illegal scope.  IPv6 does not behave quite like IPv4 does
and you need to know what some of these blocks of addresses do and what
their scope is.

Local IPv6 unicast addresses begin with the prefix fc00::/7 and there
are recommended procedures for assigning subnets out of them and
choosing network prefixes...

http://www.ietf.org/rfc/rfc4193.txt

Those may be routed between your machines but may not be routed on the
global net either as a source or destination address.  Your machines
should also be given link local addresses which are valid only on that
network segment.  They're in the fe80::/64 prefix.

Global addresses are in the 2000::/3 block.  If you are using a Linux
system as an IPv6 router, the kernel is going to disable the default
route (::/0), preventing non-global addresses from routing.  You'll have
to add appropriate routes for all your local (fc00::/7) subnets and
also provide a global unicast default route using 2000::/3 on the
routers.

Don't try to do your setup above with the two routers pointing default
routes at each other.  Point specific static routes for each subnet
behind each respective opposite router.

Wikipedia has a rundown on the various address blocks and formats:

http://en.wikipedia.org/wiki/IPv6_address

Local addresses in particular are described here:

http://en.wikipedia.org/wiki/Unique_local_address

Anything in 1::/16 (if that's what you're doing) is going to be illegal
afaik as it's not in an assigned block and scope.  It should reject it
as being unroutable or having a non-valid scope.

Certain addresses below 2000::/3 are used for compatibility purposes.

::a.b.c.d use to be an IPv4 compatibility address but is largely
deprecated.


Re: [CentOS] centos 6.3 ipv6 default gateway

2013-04-11 Thread Michael H. Warfield
Slight Clarification on v6 addressing...

On Thu, 2013-04-11 at 15:38 -0400, Michael H. Warfield wrote:

 Those may be routed between your machines but may not be routed on the
 global net either as a source or destination address.  Your machines
 should also be given link local addresses which are valid only on that
 network segment.  They're in the fe80::/64 prefix.

That's should as in the kernel should already have assigned your
link-local v6 addresses to your interfaces.  You don't have to provide
them and I didn't mean to imply you needed to add them.

Generally, if I'm using static IPv6 addresses, I take that link local
address and replace the fe80:: with the network prefix I'm assigning
and leave the lower bits the same.  That way it has the same address as
would be assigned by stateless autoconf generated from router
advertisements from a router.

On Linux routers, you would use either zebra from the quagga package or
radvd to provide router advertisements out to your clients and you'll
probably need to add that to get the end clients to self configure
properly.

Regards,
Mike
-- 
Michael H. Warfield (AI4NB) | (770) 985-6132 |  m...@wittsend.com
   /\/\|=mhw=|\/\/  | (678) 463-0932 |  http://www.wittsend.com/mhw/
   NIC whois: MHW9  | An optimist believes we live in the best of all
 PGP Key: 0x674627FF| possible worlds.  A pessimist is sure of it!


signature.asc
Description: This is a digitally signed message part
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] centos 6.3 ipv6 default gateway

2013-04-11 Thread Jaze Lee
2013/4/12 Michael H. Warfield m...@wittsend.com

 Hello,

 I may be totally off base here but...

 On Thu, 2013-04-11 at 18:06 +0800, Jaze Lee wrote:
  hello,
 i met a problem in configuratiion of ipv6 gw in my box
  i install centos 6.3 (64 bit) on my boxs, which have four netcard.
  i use a straight-through cable to connect centosv0:netcard-2 and
  centosv1:netcard2
  the topology is this:
  client c(windows xp) --centosv0:netcard-3 -- centosv0:netcard-2 ---
  centosv1:netcard-2 centosv1:netcard-2  --- client d (backtrack r2
  32)
  1:2:3:4::2/64  1:2:3:4::1/64   1:2:3::4/64
1:2:3::5/64 1:2:3:5::1/64
   1:2:3:5::2/64

 Surely, I hope you jest with those numbers.  You are not allowed to pick
 numbers out of the air and just use them, even if it's for private use.
 There are specific blocks of addresses for specific uses and assigned
 scopes and all the private use addresses are in blocks very high up
 in the address space beginning with fc or fd.  If those are literally
 the addresses you used, they will not work and I would expect them to
 give you all sorts of grief at some point or another.

  what i want to do is set default gw on centosv0 to centosv1

 I take it centosv0  and centosv1 are configured for ipv6 forwarding?
 You didn't provide the information on that.  There are some gotcha's in
 there with default routing on a router (basically there is no such
 thing) and the router needs to be set up properly for both routing and
 its routes.  But I don't think that's your problem you're describing
 down below.

  i configure /etc/sysconfig/network-scripts/ifconfig-eth2  (centosv0) as
 this
  DEVICE=eth2
  BOOTPROTO=static
  HWADDR=60:A4:4C:23:2F:6F
  NM_CONTROLLED=yes
  ONBOOT=yes
  TYPE=Ethernet
  #UUID=0ddcf499-878f-4ac7-9d1a-c27f85d2bccf
  IPV6INIT=yes
  IPV6ADDR=1:2:3::4
  ^^ You didn't specify a netmask here (default /128).

  IPV6_DEFAULTGW=1:2:3::5
   Technically not on your interface's network
 (/128)

  and i also configure /etc/sysconfig/network to this:
  NETWORKING=yes
  HOSTNAME=centosv0
  NETWORKING_IPV6=yes
  IPV6_AUTOCONF=no

 For forwarding...

 In that file you're also going to need:

 IPV6FORWARDING=yes

 You may also need to add lines to /etc/sysctl.conf (I've needed in the
 past on Fedora):

 net.ipv6.conf.all.forwarding = 1
 net.ipv6.conf.default.forwarding = 1

 But those aren't your problem with this...

  but i met an error:
  Bringing up interface eth2:  WARN : [ipv6_add_route] Unknown error

 I'm not totally sure if this is because you didn't specify a prefix
 length on your IPV6ADDR line or the fact that it then conflicted with
 your IPV6_DEFAULTGW which would not have been on 1:2:3::4/128 or if it
 was because you choose and illegal IPv6 prefix or if it was a
 combination of all of them.  The WARN: [ipv6_add_route] Unknown error
 makes me suspicious because your default gatway conflicts with your
 interface network definition (because you didn't specify the prefix size
 and it defaulted to /128) and the kernel has no way to route it out any
 interface.  IAC...  You won't be able to use a default route on a router
 anyways (more below).

  i do not know how why,and can some one gives me some suggestion?
  thanks a lot.

 If those were literally the addresses you used, It may be an address
 that's in an illegal scope.

  i test those ipv6 address on ubuntu 12.04, and it is ok. But now, we
should change system to Centos 6.3.
  And i add all the stuff that i miss. One machine is configured like this:

 [root@centosv0 sysconfig]# cat /etc/sysconfig/network-scripts/ifcfg-eth2
DEVICE=eth2
BOOTPROTO=static
HWADDR=60:A4:4C:23:2F:6F
NM_CONTROLLED=yes
ONBOOT=yes
TYPE=Ethernet
#UUID=0ddcf499-878f-4ac7-9d1a-c27f85d2bccf
IPV6INIT=yes
IPV6ADDR=1:2:3::4/64
IPV6_DEFAULTGW=1:2:3::5/64

and add the below to /etc/sysctl.conf

  net.ipv6.conf.all.forwarding = 1
  net.ipv6.conf.default.forwarding = 1

and through /proc i can see this

  [root@centosv0 sysconfig]# cat /proc/sys/net/ipv6/conf/default/forwarding
  1
   [root@centosv0 sysconfig]# cat /proc/sys/net/ipv6/conf/all/forwarding
   1

and through command ifconfig i can see this

eth1  Link encap:Ethernet  HWaddr 60:A4:4C:23:2F:6E
  inet6 addr: 1:2:3:4::1/64 Scope:Global  ---
subnet
  inet6 addr: fe80::62a4:4cff:fe23:2f6e/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:0 (0.0 b)  TX bytes:2028 (1.9 KiB)
  Interrupt:17 Memory:dc30-dc32

eth2  Link encap:Ethernet  HWaddr 60:A4:4C:23:2F:6F
  inet6 addr: 1:2:3::4/64 Scope:Global
   connected by straight-through cable
  inet6 addr: fe80::62a4:4cff:fe23:2f6f/64 Scope:Link
  UP BROADCAST 

Re: [CentOS] centos 6.3 ipv6 default gateway

2013-04-11 Thread Michael H. Warfield
On Fri, 2013-04-12 at 09:28 +0800, Jaze Lee wrote:
 2013/4/12 Michael H. Warfield m...@wittsend.com
 
  Hello,
 
  I may be totally off base here but...
 
  On Thu, 2013-04-11 at 18:06 +0800, Jaze Lee wrote:
   hello,
  i met a problem in configuratiion of ipv6 gw in my box
   i install centos 6.3 (64 bit) on my boxs, which have four netcard.
   i use a straight-through cable to connect centosv0:netcard-2 and
   centosv1:netcard2
   the topology is this:
   client c(windows xp) --centosv0:netcard-3 -- centosv0:netcard-2 ---
   centosv1:netcard-2 centosv1:netcard-2  --- client d (backtrack r2
   32)
   1:2:3:4::2/64  1:2:3:4::1/64   1:2:3::4/64
 1:2:3::5/64 1:2:3:5::1/64
1:2:3:5::2/64
 
  Surely, I hope you jest with those numbers.  You are not allowed to pick
  numbers out of the air and just use them, even if it's for private use.
  There are specific blocks of addresses for specific uses and assigned
  scopes and all the private use addresses are in blocks very high up
  in the address space beginning with fc or fd.  If those are literally
  the addresses you used, they will not work and I would expect them to
  give you all sorts of grief at some point or another.
 
   what i want to do is set default gw on centosv0 to centosv1
 
  I take it centosv0  and centosv1 are configured for ipv6 forwarding?
  You didn't provide the information on that.  There are some gotcha's in
  there with default routing on a router (basically there is no such
  thing) and the router needs to be set up properly for both routing and
  its routes.  But I don't think that's your problem you're describing
  down below.
 
   i configure /etc/sysconfig/network-scripts/ifconfig-eth2  (centosv0) as
  this
   DEVICE=eth2
   BOOTPROTO=static
   HWADDR=60:A4:4C:23:2F:6F
   NM_CONTROLLED=yes
   ONBOOT=yes
   TYPE=Ethernet
   #UUID=0ddcf499-878f-4ac7-9d1a-c27f85d2bccf
   IPV6INIT=yes
   IPV6ADDR=1:2:3::4
   ^^ You didn't specify a netmask here (default /128).
 
   IPV6_DEFAULTGW=1:2:3::5
    Technically not on your interface's network
  (/128)
 
   and i also configure /etc/sysconfig/network to this:
   NETWORKING=yes
   HOSTNAME=centosv0
   NETWORKING_IPV6=yes
   IPV6_AUTOCONF=no
 
  For forwarding...
 
  In that file you're also going to need:
 
  IPV6FORWARDING=yes
 
  You may also need to add lines to /etc/sysctl.conf (I've needed in the
  past on Fedora):
 
  net.ipv6.conf.all.forwarding = 1
  net.ipv6.conf.default.forwarding = 1
 
  But those aren't your problem with this...
 
   but i met an error:
   Bringing up interface eth2:  WARN : [ipv6_add_route] Unknown error
 
  I'm not totally sure if this is because you didn't specify a prefix
  length on your IPV6ADDR line or the fact that it then conflicted with
  your IPV6_DEFAULTGW which would not have been on 1:2:3::4/128 or if it
  was because you choose and illegal IPv6 prefix or if it was a
  combination of all of them.  The WARN: [ipv6_add_route] Unknown error
  makes me suspicious because your default gatway conflicts with your
  interface network definition (because you didn't specify the prefix size
  and it defaulted to /128) and the kernel has no way to route it out any
  interface.  IAC...  You won't be able to use a default route on a router
  anyways (more below).
 
   i do not know how why,and can some one gives me some suggestion?
   thanks a lot.
 
  If those were literally the addresses you used, It may be an address
  that's in an illegal scope.
 
   i test those ipv6 address on ubuntu 12.04, and it is ok. But now, we
 should change system to Centos 6.3.
   And i add all the stuff that i miss. One machine is configured like this:
 
  [root@centosv0 sysconfig]# cat /etc/sysconfig/network-scripts/ifcfg-eth2
 DEVICE=eth2
 BOOTPROTO=static
 HWADDR=60:A4:4C:23:2F:6F
 NM_CONTROLLED=yes
 ONBOOT=yes
 TYPE=Ethernet
 #UUID=0ddcf499-878f-4ac7-9d1a-c27f85d2bccf
 IPV6INIT=yes
 IPV6ADDR=1:2:3::4/64
 IPV6_DEFAULTGW=1:2:3::5/64
 ^^^  You do NOT need the /64 on this line.

 and add the below to /etc/sysctl.conf

   net.ipv6.conf.all.forwarding = 1
   net.ipv6.conf.default.forwarding = 1

 and through /proc i can see this
 
   [root@centosv0 sysconfig]# cat /proc/sys/net/ipv6/conf/default/forwarding
   1
[root@centosv0 sysconfig]# cat /proc/sys/net/ipv6/conf/all/forwarding
1

 and through command ifconfig i can see this

 eth1  Link encap:Ethernet  HWaddr 60:A4:4C:23:2F:6E
   inet6 addr: 1:2:3:4::1/64 Scope:Global  ---
 subnet
   inet6 addr: fe80::62a4:4cff:fe23:2f6e/64 Scope:Link
   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
   TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:1000
   RX bytes:0 (0.0 b)  TX bytes:2028 (1.9 KiB)
   Interrupt:17 

Re: [CentOS] centos 6.3 ipv6 default gateway

2013-04-11 Thread Jaze Lee
2013/4/12 Michael H. Warfield m...@wittsend.com

 On Fri, 2013-04-12 at 09:28 +0800, Jaze Lee wrote:
  2013/4/12 Michael H. Warfield m...@wittsend.com
 
   Hello,
  
   I may be totally off base here but...
  
   On Thu, 2013-04-11 at 18:06 +0800, Jaze Lee wrote:
hello,
   i met a problem in configuratiion of ipv6 gw in my box
i install centos 6.3 (64 bit) on my boxs, which have four netcard.
i use a straight-through cable to connect centosv0:netcard-2 and
centosv1:netcard2
the topology is this:
client c(windows xp) --centosv0:netcard-3 -- centosv0:netcard-2
 ---
centosv1:netcard-2 centosv1:netcard-2  --- client d
 (backtrack r2
32)
1:2:3:4::2/64  1:2:3:4::1/64
 1:2:3::4/64
  1:2:3::5/64 1:2:3:5::1/64
 1:2:3:5::2/64
  
   Surely, I hope you jest with those numbers.  You are not allowed to
 pick
   numbers out of the air and just use them, even if it's for private use.
   There are specific blocks of addresses for specific uses and assigned
   scopes and all the private use addresses are in blocks very high up
   in the address space beginning with fc or fd.  If those are literally
   the addresses you used, they will not work and I would expect them to
   give you all sorts of grief at some point or another.
  
what i want to do is set default gw on centosv0 to centosv1
  
   I take it centosv0  and centosv1 are configured for ipv6
 forwarding?
   You didn't provide the information on that.  There are some gotcha's in
   there with default routing on a router (basically there is no such
   thing) and the router needs to be set up properly for both routing and
   its routes.  But I don't think that's your problem you're describing
   down below.
  
i configure /etc/sysconfig/network-scripts/ifconfig-eth2  (centosv0)
 as
   this
DEVICE=eth2
BOOTPROTO=static
HWADDR=60:A4:4C:23:2F:6F
NM_CONTROLLED=yes
ONBOOT=yes
TYPE=Ethernet
#UUID=0ddcf499-878f-4ac7-9d1a-c27f85d2bccf
IPV6INIT=yes
IPV6ADDR=1:2:3::4
^^ You didn't specify a netmask here (default /128).
  
IPV6_DEFAULTGW=1:2:3::5
 Technically not on your interface's network
   (/128)
  
and i also configure /etc/sysconfig/network to this:
NETWORKING=yes
HOSTNAME=centosv0
NETWORKING_IPV6=yes
IPV6_AUTOCONF=no
  
   For forwarding...
  
   In that file you're also going to need:
  
   IPV6FORWARDING=yes
  
   You may also need to add lines to /etc/sysctl.conf (I've needed in the
   past on Fedora):
  
   net.ipv6.conf.all.forwarding = 1
   net.ipv6.conf.default.forwarding = 1
  
   But those aren't your problem with this...
  
but i met an error:
Bringing up interface eth2:  WARN : [ipv6_add_route] Unknown
 error
  
   I'm not totally sure if this is because you didn't specify a prefix
   length on your IPV6ADDR line or the fact that it then conflicted with
   your IPV6_DEFAULTGW which would not have been on 1:2:3::4/128 or if it
   was because you choose and illegal IPv6 prefix or if it was a
   combination of all of them.  The WARN: [ipv6_add_route] Unknown error
   makes me suspicious because your default gatway conflicts with your
   interface network definition (because you didn't specify the prefix
 size
   and it defaulted to /128) and the kernel has no way to route it out any
   interface.  IAC...  You won't be able to use a default route on a
 router
   anyways (more below).
  
i do not know how why,and can some one gives me some suggestion?
thanks a lot.
  
   If those were literally the addresses you used, It may be an address
   that's in an illegal scope.
 
i test those ipv6 address on ubuntu 12.04, and it is ok. But now, we
  should change system to Centos 6.3.
And i add all the stuff that i miss. One machine is configured like
 this:
 
   [root@centosv0 sysconfig]# cat
 /etc/sysconfig/network-scripts/ifcfg-eth2
  DEVICE=eth2
  BOOTPROTO=static
  HWADDR=60:A4:4C:23:2F:6F
  NM_CONTROLLED=yes
  ONBOOT=yes
  TYPE=Ethernet
  #UUID=0ddcf499-878f-4ac7-9d1a-c27f85d2bccf
  IPV6INIT=yes
  IPV6ADDR=1:2:3::4/64
  IPV6_DEFAULTGW=1:2:3::5/64
  ^^^  You do NOT need the /64 on this line.

  and add the below to /etc/sysctl.conf

net.ipv6.conf.all.forwarding = 1
net.ipv6.conf.default.forwarding = 1

  and through /proc i can see this
 
[root@centosv0 sysconfig]# cat
 /proc/sys/net/ipv6/conf/default/forwarding
1
 [root@centosv0 sysconfig]# cat /proc/sys/net/ipv6/conf/all/forwarding
 1

  and through command ifconfig i can see this

  eth1  Link encap:Ethernet  HWaddr 60:A4:4C:23:2F:6E
inet6 addr: 1:2:3:4::1/64 Scope:Global
  ---
  subnet
inet6 addr: fe80::62a4:4cff:fe23:2f6e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:22 errors:0 dropped:0 

Re: [CentOS] Centos 6.3 Network bnx2 Problem on HP DL360

2013-03-25 Thread Woehrle Hartmut SBB CFF FFS (Extern)
Hello Svavar

This was the first time that this problem occurred - with 60 Servers and about 
half a year of Centos 6 (5 before).
But because the interfaces have a permanent load - really 24x7 - problems with 
power management would be a disaster.
I will try to switch off.

Thanks
Hartmut

 How often are you getting these crashes ?

I had simular problem on my HP DL380 G7 server.

I disabled Active State PowerManagement on the PCI-E express.

Try it.

Add pcie_aspm=off as optional boot option.


Best regards,

Svavar O
Reykjavik - Iceland



 On 19.3.2013, at 15:32, Woehrle Hartmut SBB CFF FFS (Extern) wrote:

 Hello Mailing List
 
 I got a severe network error message at a HP DL360 Server.
 The kernel log says:
 
 --- /var/log/messages 
 -
 Mar 19 15:45:06 server kernel: do_IRQ: 2.168 No irq handler for vector 
 (irq -1) Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: 
 DEBUG: intr_sem[0] PCI_CMD[00100446] Mar 19 15:45:17 server kernel: 
 bnx2 :02:00.1: eth1: DEBUG: PCI_PM[19002108] 
 PCI_MISC_CFG[9288] Mar 19 15:45:17 server kernel: bnx2 
 :02:00.1: eth1: DEBUG: EMAC_TX_STATUS[0008] 
 EMAC_RX_STATUS[0006] Mar 19 15:45:17 server kernel: bnx2 
 :02:00.1: eth1: DEBUG: RPM_MGMT_PKT_CTRL[4088] Mar 19 15:45:17 
 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
 HC_STATS_INTERRUPT_STATUS[017f0080]
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
 PBA[] Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: 
 --- start MCP states dump --- Mar 19 15:45:17 server kernel: bnx2 
 :02:00.1: eth1: DEBUG: MCP_STATE_P0[0003610e] 
 MCP_STATE_P1[0003610e] Mar 19 15:45:17 server kernel: bnx2 
 :02:00.1: eth1: DEBUG: MCP mode[b880] state[80008000] 
 evt_mask[0500] Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: 
 DEBUG: pc[0800adec] pc[0800aeb0] instr[8fb10014] Mar 19 15:45:17 server 
 kernel: bnx2 :02:00.1: eth1: DEBUG: shmem states:
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
 drv_mb[0103000f] fw_mb[000f] link_status[006f] 
 drv_pulse_mb[432b] Mar 19 15:45:17 server kernel: bnx2 
 :02:00.1: eth1: DEBUG: dev_info_signature[44564903] 
 reset_type[01005254] condition[0003610e] Mar 19 15:45:17 server 
 kernel: bnx2 :02:00.1: eth1: DEBUG: 03cc:   
  0a3c Mar 19 15:45:17 server kernel: bnx2 :02:00.1: 
 eth1: DEBUG: 03dc: 0ffe    Mar 19 
 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 03ec: 
    0002 Mar 19 15:45:17 server kernel: 
 bnx2 :02:00.1: eth1: DEBUG: 0x3fc[] Mar 19 15:45:17 server 
 kernel: bnx2 :02:00.1: eth1: --- end MCP states dump --- Mar 19 
 15:45:17 server kernel: bnx2 :02:00.1: eth1: NIC Copper Link is 
 Down Mar 19 15:45:20 server kernel: bnx2 :02:00.1: eth1: NIC 
 Copper Link is Up, 1000 Mbps full duplex
 --
 -
 
 Does anyone know that problem?
 
 System is Centos 6.3 Kernel
 Linux server 2.6.32-279.5.2.el6.centos.plus.x86_64 #1 SMP Fri Aug 24 
 00:25:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
 
 
 Thanks
 Hartmut
 
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 Network bnx2 Problem on HP DL360

2013-03-25 Thread Svavar Örn Eysteinsson

After you have tried the pcie_aspm boot option, also try :

echo performance  /sys/module/pcie_aspm/parameters/policy
This will disable ASPM on PCIe and operate with maximum performance.

This is what I use today on the DL380 G7.




On 25.3.2013, at 09:06, Woehrle Hartmut SBB CFF FFS (Extern) wrote:

 Hello Svavar
 
 This was the first time that this problem occurred - with 60 Servers and 
 about half a year of Centos 6 (5 before).
 But because the interfaces have a permanent load - really 24x7 - problems 
 with power management would be a disaster.
 I will try to switch off.
 
 Thanks
 Hartmut
 
 How often are you getting these crashes ?
 
 I had simular problem on my HP DL380 G7 server.
 
 I disabled Active State PowerManagement on the PCI-E express.
 
 Try it.
 
 Add pcie_aspm=off as optional boot option.
 
 
 Best regards,
 
 Svavar O
 Reykjavik - Iceland
 
 
 
 On 19.3.2013, at 15:32, Woehrle Hartmut SBB CFF FFS (Extern) wrote:
 
 Hello Mailing List
 
 I got a severe network error message at a HP DL360 Server.
 The kernel log says:
 
 --- /var/log/messages 
 -
 Mar 19 15:45:06 server kernel: do_IRQ: 2.168 No irq handler for vector 
 (irq -1) Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: 
 DEBUG: intr_sem[0] PCI_CMD[00100446] Mar 19 15:45:17 server kernel: 
 bnx2 :02:00.1: eth1: DEBUG: PCI_PM[19002108] 
 PCI_MISC_CFG[9288] Mar 19 15:45:17 server kernel: bnx2 
 :02:00.1: eth1: DEBUG: EMAC_TX_STATUS[0008] 
 EMAC_RX_STATUS[0006] Mar 19 15:45:17 server kernel: bnx2 
 :02:00.1: eth1: DEBUG: RPM_MGMT_PKT_CTRL[4088] Mar 19 15:45:17 
 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
 HC_STATS_INTERRUPT_STATUS[017f0080]
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
 PBA[] Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: 
 --- start MCP states dump --- Mar 19 15:45:17 server kernel: bnx2 
 :02:00.1: eth1: DEBUG: MCP_STATE_P0[0003610e] 
 MCP_STATE_P1[0003610e] Mar 19 15:45:17 server kernel: bnx2 
 :02:00.1: eth1: DEBUG: MCP mode[b880] state[80008000] 
 evt_mask[0500] Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: 
 DEBUG: pc[0800adec] pc[0800aeb0] instr[8fb10014] Mar 19 15:45:17 server 
 kernel: bnx2 :02:00.1: eth1: DEBUG: shmem states:
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
 drv_mb[0103000f] fw_mb[000f] link_status[006f] 
 drv_pulse_mb[432b] Mar 19 15:45:17 server kernel: bnx2 
 :02:00.1: eth1: DEBUG: dev_info_signature[44564903] 
 reset_type[01005254] condition[0003610e] Mar 19 15:45:17 server 
 kernel: bnx2 :02:00.1: eth1: DEBUG: 03cc:   
  0a3c Mar 19 15:45:17 server kernel: bnx2 :02:00.1: 
 eth1: DEBUG: 03dc: 0ffe    Mar 19 
 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 03ec: 
    0002 Mar 19 15:45:17 server kernel: 
 bnx2 :02:00.1: eth1: DEBUG: 0x3fc[] Mar 19 15:45:17 server 
 kernel: bnx2 :02:00.1: eth1: --- end MCP states dump --- Mar 19 
 15:45:17 server kernel: bnx2 :02:00.1: eth1: NIC Copper Link is 
 Down Mar 19 15:45:20 server kernel: bnx2 :02:00.1: eth1: NIC 
 Copper Link is Up, 1000 Mbps full duplex
 --
 -
 
 Does anyone know that problem?
 
 System is Centos 6.3 Kernel
 Linux server 2.6.32-279.5.2.el6.centos.plus.x86_64 #1 SMP Fri Aug 24 
 00:25:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
 
 
 Thanks
 Hartmut
 
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos
 
 
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 Network bnx2 Problem on HP DL360

2013-03-20 Thread Woehrle Hartmut SBB CFF FFS (Extern)

 On Mar 19, 2013, at 9:32 AM, Woehrle Hartmut SBB CFF FFS (Extern) 
 hartmut.woeh...@sbb.ch wrote:

  Hello Mailing List
  
  I got a severe network error message at a HP DL360 Server.
  The kernel log says:

 If that's a DL360 G7 server, make sure you've applied all of the latest 
 firmware patches from HP on it.  The G7 version has been 
 almost notorious for firmware issues with drive controllers, ethernet 
 interfaces, etc.
 
 Nate

Hello Nate

It is a G6 Server and the firmware is more or less the latest version:

# bash CP017428.scexe -c
MAC  PCI-ID  NIC
18A90576C820 14E4-1639-103C-7055 HP NC382i DP Multifunction Gigabit Server 
Adapter 

 (Installed)(Available)  Interface
 Image  Version Image  Version   eth0
--
  BC5.2.3   BC 5.2.3
  iSCSI 4.2.10   iSCSI  7.4.2  
 I don't use iSCSI at this maschine
  NCSI  2.0.6   NCSI   2.0.12


Hartmut
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 Network bnx2 Problem on HP DL360

2013-03-20 Thread Svavar Örn Eysteinsson
How often are you getting these crashes ?

I had simular problem on my HP DL380 G7 server.

I disabled Active State PowerManagement on the PCI-E express.

Try it.

Add pcie_aspm=off as optional boot option.


Best regards,

Svavar O
Reykjavik - Iceland



On 19.3.2013, at 15:32, Woehrle Hartmut SBB CFF FFS (Extern) wrote:

 Hello Mailing List
 
 I got a severe network error message at a HP DL360 Server.
 The kernel log says:
 
 --- /var/log/messages 
 -
 Mar 19 15:45:06 server kernel: do_IRQ: 2.168 No irq handler for vector (irq 
 -1)
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: intr_sem[0] 
 PCI_CMD[00100446]
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
 PCI_PM[19002108] PCI_MISC_CFG[9288]
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
 EMAC_TX_STATUS[0008] EMAC_RX_STATUS[0006]
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
 RPM_MGMT_PKT_CTRL[4088]
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
 HC_STATS_INTERRUPT_STATUS[017f0080]
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: PBA[]
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: --- start MCP states 
 dump ---
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
 MCP_STATE_P0[0003610e] MCP_STATE_P1[0003610e]
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: MCP 
 mode[b880] state[80008000] evt_mask[0500]
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: pc[0800adec] 
 pc[0800aeb0] instr[8fb10014]
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: shmem states:
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
 drv_mb[0103000f] fw_mb[000f] link_status[006f] drv_pulse_mb[432b]
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
 dev_info_signature[44564903] reset_type[01005254] condition[0003610e]
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 03cc: 
    0a3c
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 03dc: 
 0ffe   
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 03ec: 
    0002
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 0x3fc[]
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: --- end MCP states 
 dump ---
 Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: NIC Copper Link is 
 Down
 Mar 19 15:45:20 server kernel: bnx2 :02:00.1: eth1: NIC Copper Link is 
 Up, 1000 Mbps full duplex
 ---
 
 Does anyone know that problem?
 
 System is Centos 6.3 Kernel 
 Linux server 2.6.32-279.5.2.el6.centos.plus.x86_64 #1 SMP Fri Aug 24 00:25:34 
 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
 
 
 Thanks
 Hartmut
 
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] Centos 6.3 Network bnx2 Problem on HP DL360

2013-03-19 Thread Woehrle Hartmut SBB CFF FFS (Extern)
Hello Mailing List

I got a severe network error message at a HP DL360 Server.
The kernel log says:

--- /var/log/messages 
-
Mar 19 15:45:06 server kernel: do_IRQ: 2.168 No irq handler for vector (irq -1)
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: intr_sem[0] 
PCI_CMD[00100446]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: PCI_PM[19002108] 
PCI_MISC_CFG[9288]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
EMAC_TX_STATUS[0008] EMAC_RX_STATUS[0006]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
RPM_MGMT_PKT_CTRL[4088]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
HC_STATS_INTERRUPT_STATUS[017f0080]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: PBA[]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: --- start MCP states 
dump ---
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
MCP_STATE_P0[0003610e] MCP_STATE_P1[0003610e]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: MCP 
mode[b880] state[80008000] evt_mask[0500]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: pc[0800adec] 
pc[0800aeb0] instr[8fb10014]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: shmem states:
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: drv_mb[0103000f] 
fw_mb[000f] link_status[006f] drv_pulse_mb[432b]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
dev_info_signature[44564903] reset_type[01005254] condition[0003610e]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 03cc: 
   0a3c
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 03dc: 
0ffe   
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 03ec: 
   0002
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 0x3fc[]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: --- end MCP states 
dump ---
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: NIC Copper Link is Down
Mar 19 15:45:20 server kernel: bnx2 :02:00.1: eth1: NIC Copper Link is Up, 
1000 Mbps full duplex
---

Does anyone know that problem?

System is Centos 6.3 Kernel 
Linux server 2.6.32-279.5.2.el6.centos.plus.x86_64 #1 SMP Fri Aug 24 00:25:34 
UTC 2012 x86_64 x86_64 x86_64 GNU/Linux


Thanks
Hartmut

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 Network bnx2 Problem on HP DL360

2013-03-19 Thread Nathan Duehr

On Mar 19, 2013, at 9:32 AM, Woehrle Hartmut SBB CFF FFS (Extern) 
hartmut.woeh...@sbb.ch wrote:

 Hello Mailing List
 
 I got a severe network error message at a HP DL360 Server.
 The kernel log says:

If that's a DL360 G7 server, make sure you've applied all of the latest 
firmware patches from HP on it.  The G7 version has been almost notorious for 
firmware issues with drive controllers, ethernet interfaces, etc.

Nate
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 early panic on Xeon E3-1270V2 - CentOS 6.4 too

2013-03-12 Thread Tilman Schmidt
Having read that RHEL/CentOS 6.4 came with new VMware drivers I checked
whether this problem might perchance be fixed. It isn't.

In the meantime I got a report that Windows 8 (64 bit) showed a similar
problem.

So, updated problem matrix (ESXi build omitted as it has no influence):

ProcessorE5620E3-1230  E3-1270V2

Windows XP/2003/2008   ok   ok   ok

Windows 8   ??  Panic

CentOS 5.8 ok   ok   ok
2.6.18-308.13.1.el5

CentOS 6.2 ok   ok   ok(*)
2.6.32-220.7.1.el6.x86_64

CentOS 6.3 ok   ok  Panic
2.6.32-279.2.1.el6.x86_64

CentOS 6.4 ok   ok  Panic
2.6.32-358.0.1.el6.x86_64

(*) keyboard shows panic blink but system works fine otherwise

Reminder of the problem description: trying to boot a VM with
CentOS 6.3 or later on a VMware ESXi 4 host with a Xeon E3-1270V2
processor fails immediately after GRUB, with the VM locking up,
console message:

Sep 11 17:21:31.498: vmx| PANIC: early exception 0d rip
10:81038879 error 0 cr2 0

and ESXi log messages:

Sep 11 17:21:19.628: vcpu-0| RDMSR: unknown MSR[0x1a0] (read as zero):
rip=0x810388db count=1
Sep 11 17:21:19.628: vcpu-0| RDMSR: unknown MSR[0x1a0] (read as zero):
rip=0x810388db count=2
Sep 11 17:21:19.629: vcpu-0| X86Fault_Warning:
vmcore/vmm64/cpu/interp.c:427: cs:eip=0x10:0x81038879 fault=13
Sep 11 17:21:19.632: vcpu-0| Vix: [1125838 vmxCommands.c:9609]:
VMAutomation_HandleCLIHLTEvent. Do nothing.
Sep 11 17:21:19.632: vcpu-0| MsgHint: msg.monitorevent.halt (sent)
Sep 11 17:21:19.632: vcpu-0| The CPU has been disabled by the guest
operating system. Power off or reset the virtual machine.


-- 
Tilman Schmidt
Phoenix Software GmbH
Bonn, Germany



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 - fail2ban not working properly + workaround

2013-03-12 Thread Theo Band
On 10/17/2012 05:51 PM, SilverTip257 wrote:
 I recall others on this list are using fail2ban to block brute force
 login attempts.
 Packages are from the EPEL repo, so I'm just sharing some knowledge here.

 For about two months now I've had a CentOS 6.3 box (web host) in
 production that occasionally is ftp brute forced.
 Oddly enough fail2ban wasn't nabbing the perpetrators.  I found that
 the iptables chain for VSFTP isn't created for one.

 I have finally come to find [0] that indicates there's a problem with
 the inotify backend.
 Setting backend=gamin in /etc/fail2ban/jail.conf gives me the iptables
 chain I expect to find and one blocked host.

 Hope this is helpful to somebody until a new version is commited to EPEL.

 quote
 yarikoptic:
 ok -- that point was not yet good ;) now (0.8.6-95-gc0c1232) that
 branch seems to work just perfect. If I hear no complaints or do not
 see problem with my instance -- I will merge it into master tomorrow,
 thus closing this issue
 /quote

 [0] https://github.com/fail2ban/fail2ban/issues/44


Thanks for the tip (I know it's a very old message).
I have updated recently to 6 and see that fail2band ssh dos no longer
works. Indeed after log rotate fail2ban seems to follow the old log file
instead of the newly created /var/log/secure.
I had backend = auto in /etc/fail2ban/jail.conf and gamin and pyinotify
are both installed. I now changed backend to gamin and give it another
try. The next log rotate is next week
Anyone else using fail2ban with CentOS6 installed from epel?

fail2ban-0.8.8-2.el6.noarch on CentOS6.4

Theo
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 - fail2ban not working properly + workaround

2013-03-12 Thread SilverTip257
On Tue, Mar 12, 2013 at 11:51 AM, Theo Band theo.b...@greenpeak.com wrote:

 On 10/17/2012 05:51 PM, SilverTip257 wrote:
  I recall others on this list are using fail2ban to block brute force
  login attempts.
  Packages are from the EPEL repo, so I'm just sharing some knowledge here.
 
  For about two months now I've had a CentOS 6.3 box (web host) in
  production that occasionally is ftp brute forced.
  Oddly enough fail2ban wasn't nabbing the perpetrators.  I found that
  the iptables chain for VSFTP isn't created for one.
 
  I have finally come to find [0] that indicates there's a problem with
  the inotify backend.
  Setting backend=gamin in /etc/fail2ban/jail.conf gives me the iptables
  chain I expect to find and one blocked host.
 
  Hope this is helpful to somebody until a new version is commited to EPEL.
 
  quote
  yarikoptic:
  ok -- that point was not yet good ;) now (0.8.6-95-gc0c1232) that
  branch seems to work just perfect. If I hear no complaints or do not
  see problem with my instance -- I will merge it into master tomorrow,
  thus closing this issue
  /quote
 
  [0] https://github.com/fail2ban/fail2ban/issues/44
 

 Thanks for the tip (I know it's a very old message).


Happy you found it useful.


 I have updated recently to 6 and see that fail2band ssh dos no longer
 works. Indeed after log rotate fail2ban seems to follow the old log file
 instead of the newly created /var/log/secure.


I've also recently noticed fail2ban choking on name resolution.  By that I
mean f2b determines the name of the connecting host and it complains
indicating the pointer record doesn't match.  Based on the number of login
attempts it doesn't seem to be actually blocking the host either.

I have SSH locked down for my access only, but FTP is wide open for
customer access.  I let fail2ban keep tabs on logins with the
vsftp-iptables jail.


 I had backend = auto in /etc/fail2ban/jail.conf and gamin and pyinotify
 are both installed. I now changed backend to gamin and give it another
 try. The next log rotate is next week
 Anyone else using fail2ban with CentOS6 installed from epel?

 fail2ban-0.8.8-2.el6.noarch on CentOS6.4

 Theo
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos




-- 
---~~.~~---
Mike
//  SilverTip257  //
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 - fail2ban not working properly + workaround

2013-03-12 Thread Timothy Murphy
Theo Band wrote:

 I have updated recently to 6 and see that fail2band ssh dos no longer
 works. Indeed after log rotate fail2ban seems to follow the old log file
 instead of the newly created /var/log/secure.
 I had backend = auto in /etc/fail2ban/jail.conf and gamin and pyinotify
 are both installed. I now changed backend to gamin and give it another
 try. The next log rotate is next week
 Anyone else using fail2ban with CentOS6 installed from epel?

I'm running fail2ban on my server (under CentOS-6.4)
and it seems to be running according to
-
[tim@grover fail2ban]$ sudo service fail2ban status
Fail2ban (pid 31794) is running...
Status
|- Number of jail:  1
`- Jail list:   ssh-iptables
-
I have absolutely no idea how fail2ban works,
and I'm running it with the default /etc/fail2ban/fail2ban.conf ,
which seems to set the logfile to /var/log/fail2ban.log .
Should I actually study how it is meant to be configured?

I just yum-installed it (from Epel, I assume)
and hope it does its job, whatever that is.

Incidentally, I am running shorewall on this server.
Should I tell shorewall something about fail2ban,
or vice versa?


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 - fail2ban not working properly + workaround

2013-03-12 Thread Theo Band
On 03/12/2013 05:35 PM, Timothy Murphy wrote:
 I'm running fail2ban on my server (under CentOS-6.4)
 and it seems to be running according to
 -
 [tim@grover fail2ban]$ sudo service fail2ban status
 Fail2ban (pid 31794) is running...
 Status
 |- Number of jail:  1
 `- Jail list:   ssh-iptables
 -
 I have absolutely no idea how fail2ban works,
 and I'm running it with the default /etc/fail2ban/fail2ban.conf ,
 which seems to set the logfile to /var/log/fail2ban.log .
 Should I actually study how it is meant to be configured?

 I just yum-installed it (from Epel, I assume)
 and hope it does its job, whatever that is.
It sets up iptables rules for every jail that is configured (iptables 
-L). You seem to have only the ssh-iptables configured. Check the date 
of the logfile. I noticed that SYSLOG is now used for logging. It used 
to be /var/log/fail2ban.log in the past. I removed the old log file.
If ssh is the only public service you want to protect against brute 
force, then you don't need to setup anything. But have a look in 
/etc/fail2ban/jail.conf and add at least your email address to get a 
notification when it blocks access. There lots of other jails that can 
be enabled.
Normally I receive several messages a day. So not receiving them means 
that the service is no longer protecting. Simply because it watches a 
renamed no longer updated version of /var/log/secure:

ls -l /var/log/secure*
-rw--- 1 root root 2130892 Mar 12 18:25 /var/log/secure
-rw--- 1 root root 1374710 Feb 17 01:31 /var/log/secure-20130217
-rw--- 1 root root 1482646 Feb 24 03:09 /var/log/secure-20130224
-rw--- 1 root root 1732930 Mar  3 03:13 /var/log/secure-20130303
-rw--- 1 root root  656454 Mar 10 03:12 /var/log/secure-20130310

Once a week fail2ban stops working as a new secure log file is created 
(logrotate) and it seems to watch the only old name. You will not see 
any error message and status show as running.
But I have no proof that it keeps working with the gamin fix.

Theo



___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 - fail2ban not working properly + workaround

2013-03-12 Thread Fabien Archambault
2013/3/12 Theo Band theo.b...@greenpeak.com:
 On 03/12/2013 05:35 PM, Timothy Murphy wrote:
 I'm running fail2ban on my server (under CentOS-6.4)
 and it seems to be running according to
 -
 [tim@grover fail2ban]$ sudo service fail2ban status
 Fail2ban (pid 31794) is running...
 Status
 |- Number of jail:  1
 `- Jail list:   ssh-iptables
 -
 I have absolutely no idea how fail2ban works,
 and I'm running it with the default /etc/fail2ban/fail2ban.conf ,
 which seems to set the logfile to /var/log/fail2ban.log .
 Should I actually study how it is meant to be configured?

 I just yum-installed it (from Epel, I assume)
 and hope it does its job, whatever that is.
 It sets up iptables rules for every jail that is configured (iptables
 -L). You seem to have only the ssh-iptables configured. Check the date
 of the logfile. I noticed that SYSLOG is now used for logging. It used
 to be /var/log/fail2ban.log in the past. I removed the old log file.
 If ssh is the only public service you want to protect against brute
 force, then you don't need to setup anything. But have a look in
 /etc/fail2ban/jail.conf and add at least your email address to get a
 notification when it blocks access. There lots of other jails that can
 be enabled.
 Normally I receive several messages a day. So not receiving them means
 that the service is no longer protecting. Simply because it watches a
 renamed no longer updated version of /var/log/secure:

 ls -l /var/log/secure*
 -rw--- 1 root root 2130892 Mar 12 18:25 /var/log/secure
 -rw--- 1 root root 1374710 Feb 17 01:31 /var/log/secure-20130217
 -rw--- 1 root root 1482646 Feb 24 03:09 /var/log/secure-20130224
 -rw--- 1 root root 1732930 Mar  3 03:13 /var/log/secure-20130303
 -rw--- 1 root root  656454 Mar 10 03:12 /var/log/secure-20130310

 Once a week fail2ban stops working as a new secure log file is created
 (logrotate) and it seems to watch the only old name. You will not see
 any error message and status show as running.
 But I have no proof that it keeps working with the gamin fix.

 Theo


I too have the same problem but couldn't figure where is the issue. It
stops working even if the service says all is right. I have to restart
the service to let it work again...

I will try to find through your idea.

Thanks,
Fabien
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 - fail2ban not working properly + workaround

2013-03-12 Thread David Hrbáč
Dne 12.3.2013 19:03, Fabien Archambault napsal(a):
 I too have the same problem but couldn't figure where is the issue. It
 stops working even if the service says all is right. I have to restart
 the service to let it work again...

 I will try to find through your idea.

 Thanks,
 Fabien


As temporary solution you can always use fail2ban from Repoforge. It's a
little bit older, but works on 6.x.
Regards,
David Hrbac
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 - fail2ban not working properly + workaround

2013-03-12 Thread SilverTip257
On Tue, Mar 12, 2013 at 1:57 PM, Theo Band theo.b...@greenpeak.com wrote:

 On 03/12/2013 05:35 PM, Timothy Murphy wrote:
  I'm running fail2ban on my server (under CentOS-6.4)
  and it seems to be running according to
  -
  [tim@grover fail2ban]$ sudo service fail2ban status
  Fail2ban (pid 31794) is running...
  Status
  |- Number of jail:  1
  `- Jail list:   ssh-iptables
  -
  I have absolutely no idea how fail2ban works,


First off, as a good security practice do not let SSH open to the world
unless you have to (and even then I'd go so far as to say restrict it the
best you can).  Fail2ban can become a band aid for good security practices.


  and I'm running it with the default /etc/fail2ban/fail2ban.conf ,
  which seems to set the logfile to /var/log/fail2ban.log .
  Should I actually study how it is meant to be configured?


I'd suggest at least checking out information on fail2ban's wiki and
perusing the config files (especially jail.conf).


 
  I just yum-installed it (from Epel, I assume)
  and hope it does its job, whatever that is.
 It sets up iptables rules for every jail that is configured (iptables
 -L). You seem to have only the ssh-iptables configured. Check the date
 of the logfile. I noticed that SYSLOG is now used for logging. It used
 to be /var/log/fail2ban.log in the past. I removed the old log file.
 If ssh is the only public service you want to protect against brute
 force, then you don't need to setup anything. But have a look in
 /etc/fail2ban/jail.conf and add at least your email address to get a


You can tweak things quite a bit to make sure logs are going where you want
them to and that fail2ban is watching the right files.


 notification when it blocks access. There lots of other jails that can
 be enabled.
 Normally I receive several messages a day. So not receiving them means
 that the service is no longer protecting. Simply because it watches a
 renamed no longer updated version of /var/log/secure:


I'll add that if someone decides to restart iptables, your fail2ban chains
will be removed.  So you'll need to restart fail2ban and check that the
chains and rules are present again.  Otherwise fail2ban will report, but
won't be able to actually add a firewall rule to block the brute forcing
host.



 ls -l /var/log/secure*
 -rw--- 1 root root 2130892 Mar 12 18:25 /var/log/secure
 -rw--- 1 root root 1374710 Feb 17 01:31 /var/log/secure-20130217
 -rw--- 1 root root 1482646 Feb 24 03:09 /var/log/secure-20130224
 -rw--- 1 root root 1732930 Mar  3 03:13 /var/log/secure-20130303
 -rw--- 1 root root  656454 Mar 10 03:12 /var/log/secure-20130310

 Once a week fail2ban stops working as a new secure log file is created
 (logrotate) and it seems to watch the only old name. You will not see
 any error message and status show as running.
 But I have no proof that it keeps working with the gamin fix.


I've not seen any problems since I switched to the gamin backend some time
ago.  As you do, I generally get at least one daily notification email that
my FTP daemon is being brute forced.  So I'd say it's working fine.



 Theo



 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos




-- 
---~~.~~---
Mike
//  SilverTip257  //
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 - fail2ban not working properly + workaround

2013-03-12 Thread SilverTip257
On Tue, Mar 12, 2013 at 3:45 PM, David Hrbáč david-li...@hrbac.cz wrote:

 Dne 12.3.2013 19:03, Fabien Archambault napsal(a):
  I too have the same problem but couldn't figure where is the issue. It
  stops working even if the service says all is right. I have to restart
  the service to let it work again...
 
  I will try to find through your idea.
 
  Thanks,
  Fabien
 

 As temporary solution you can always use fail2ban from Repoforge. It's a
 little bit older, but works on 6.x.


The newest is slightly older as you noted:
http://pkgs.repoforge.org/fail2ban/

Quite a selection of older versions too...


 Regards,
 David Hrbac
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos




-- 
---~~.~~---
Mike
//  SilverTip257  //
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] Centos 6.3 - unsupported video hardware

2013-03-06 Thread Robert Moskowitz
I pulled one of my old OQO model 2 out of the junk bin and installed 
Centos 6.3 over Centos 5.3.

The internal video does not work in graphics mode (text works fine), 
though a monitor attacked to the VGA port works fine.  Although my 
intension is to use this as a portable test server, it would be nice if 
the video was available.  How might I go about figuring out the Xorg 
magic to get it working?


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 - unsupported video hardware

2013-03-06 Thread Craig White

On Mar 6, 2013, at 12:24 PM, Robert Moskowitz wrote:

 I pulled one of my old OQO model 2 out of the junk bin and installed 
 Centos 6.3 over Centos 5.3.
 
 The internal video does not work in graphics mode (text works fine), 
 though a monitor attacked to the VGA port works fine.  Although my 
 intension is to use this as a portable test server, it would be nice if 
 the video was available.  How might I go about figuring out the Xorg 
 magic to get it working?

I would recommend that you start by disabling the old xorg.conf and see if it 
can dynamically generate a working configuration.

sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf-disabled

and then restart

Craig
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 - unsupported video hardware

2013-03-06 Thread Robert Moskowitz

On 03/06/2013 02:51 PM, Craig White wrote:
 On Mar 6, 2013, at 12:24 PM, Robert Moskowitz wrote:

 I pulled one of my old OQO model 2 out of the junk bin and installed
 Centos 6.3 over Centos 5.3.

 The internal video does not work in graphics mode (text works fine),
 though a monitor attacked to the VGA port works fine.  Although my
 intension is to use this as a portable test server, it would be nice if
 the video was available.  How might I go about figuring out the Xorg
 magic to get it working?
 
 I would recommend that you start by disabling the old xorg.conf and see if it 
 can dynamically generate a working configuration.

 sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf-disabled

 and then restart

There is no xorg.conf.   This is a fresh install of Centos 6.3; I 
removed the old 5.3 partitions and did a total from scratch install.


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 - unsupported video hardware

2013-03-06 Thread Dale Dellutri
On Wed, Mar 6, 2013 at 2:31 PM, Robert Moskowitz r...@htt-consult.com wrote:

 On 03/06/2013 02:51 PM, Craig White wrote:
 On Mar 6, 2013, at 12:24 PM, Robert Moskowitz wrote:

 I pulled one of my old OQO model 2 out of the junk bin and installed
 Centos 6.3 over Centos 5.3.

 The internal video does not work in graphics mode (text works fine),
 though a monitor attacked to the VGA port works fine.  Although my
 intension is to use this as a portable test server, it would be nice if
 the video was available.  How might I go about figuring out the Xorg
 magic to get it working?

When you say internal video does not work, what do you mean?
Is the laptop screen black, garbled, flickering, unresponsive?

If black, did you try startx for the command line?

Are there any errors (EE) or warnings (WW) in /var/log/Xorg.0.log?

Anything in /var/log/messages or dmesg?

What is the output of lspci | grep VGA?

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 - unsupported video hardware

2013-03-06 Thread Robert Moskowitz

On 03/06/2013 03:47 PM, Dale Dellutri wrote:
 On Wed, Mar 6, 2013 at 2:31 PM, Robert Moskowitz r...@htt-consult.com wrote:
 On 03/06/2013 02:51 PM, Craig White wrote:
 On Mar 6, 2013, at 12:24 PM, Robert Moskowitz wrote:

 I pulled one of my old OQO model 2 out of the junk bin and installed
 Centos 6.3 over Centos 5.3.

 The internal video does not work in graphics mode (text works fine),
 though a monitor attacked to the VGA port works fine.  Although my
 intension is to use this as a portable test server, it would be nice if
 the video was available.  How might I go about figuring out the Xorg
 magic to get it working?
 When you say internal video does not work, what do you mean?
 Is the laptop screen black, garbled, flickering, unresponsive?

Scrolling flickering, blue and white image.

 If black, did you try startx for the command line?

Have not switched to init 3 to try.

 Are there any errors (EE) or warnings (WW) in /var/log/Xorg.0.log?

(EE) open /dev/fb0: No such device

(WW) Falling back to old probe method for vesa
(WW) Falling back to old probe method for fbdev
(WW) CHROME(0): Manufacturer plainly copied main PCI IDs to 
subsystem/card IDs.
(WW) CHROME(0): Unable to estimate virtual size
(WW) CHROME(0): [XvMC] XvMC is not supported on this chipset
(WW) Lid Switch: Don't know how to use device

 Anything in /var/log/messages or dmesg?

what would I search for?


 What is the output of lspci | grep VGA?
01:00.0 VGA compatible controller: VIA Technologies, Inc. CX700/VX700 
[S3 UniChrome Pro] (rev 03)

Hope this points somewhere.


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 - unsupported video hardware

2013-03-06 Thread Dale Dellutri
On Wed, Mar 6, 2013 at 3:03 PM, Robert Moskowitz r...@htt-consult.com wrote:

 On 03/06/2013 03:47 PM, Dale Dellutri wrote:

 On Wed, Mar 6, 2013 at 2:31 PM, Robert Moskowitz r...@htt-consult.com
 wrote:

 On 03/06/2013 02:51 PM, Craig White wrote:

 On Mar 6, 2013, at 12:24 PM, Robert Moskowitz wrote:

 I pulled one of my old OQO model 2 out of the junk bin and installed
 Centos 6.3 over Centos 5.3.

 The internal video does not work in graphics mode (text works fine),
 though a monitor attacked to the VGA port works fine.  Although my
 intension is to use this as a portable test server, it would be nice if
 the video was available.  How might I go about figuring out the Xorg
 magic to get it working?

 When you say internal video does not work, what do you mean?
 Is the laptop screen black, garbled, flickering, unresponsive?


 Scrolling flickering, blue and white image.


 If black, did you try startx for the command line?


 Have not switched to init 3 to try.


 Are there any errors (EE) or warnings (WW) in /var/log/Xorg.0.log?


 (EE) open /dev/fb0: No such device

 (WW) Falling back to old probe method for vesa
 (WW) Falling back to old probe method for fbdev
 (WW) CHROME(0): Manufacturer plainly copied main PCI IDs to subsystem/card
 IDs.
 (WW) CHROME(0): Unable to estimate virtual size
 (WW) CHROME(0): [XvMC] XvMC is not supported on this chipset
 (WW) Lid Switch: Don't know how to use device


 Anything in /var/log/messages or dmesg?


 what would I search for?

Error messages pertaining to the video controller.




 What is the output of lspci | grep VGA?

 01:00.0 VGA compatible controller: VIA Technologies, Inc. CX700/VX700 [S3
 UniChrome Pro] (rev 03)

Use the info in this line (VIA CX700 VX700 or UniChrome Pro) to do a
google search.  Add linux to the search terms to see what driver you need.


 Hope this points somewhere.





-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 - unsupported video hardware

2013-03-06 Thread Robert Moskowitz

On 03/06/2013 04:18 PM, Dale Dellutri wrote:
 On Wed, Mar 6, 2013 at 3:03 PM, Robert Moskowitz r...@htt-consult.com wrote:
 On 03/06/2013 03:47 PM, Dale Dellutri wrote:
 On Wed, Mar 6, 2013 at 2:31 PM, Robert Moskowitz r...@htt-consult.com
 wrote:
 On 03/06/2013 02:51 PM, Craig White wrote:
 On Mar 6, 2013, at 12:24 PM, Robert Moskowitz wrote:

 I pulled one of my old OQO model 2 out of the junk bin and installed
 Centos 6.3 over Centos 5.3.

 The internal video does not work in graphics mode (text works fine),
 though a monitor attacked to the VGA port works fine.  Although my
 intension is to use this as a portable test server, it would be nice if
 the video was available.  How might I go about figuring out the Xorg
 magic to get it working?
 When you say internal video does not work, what do you mean?
 Is the laptop screen black, garbled, flickering, unresponsive?

 Scrolling flickering, blue and white image.


 If black, did you try startx for the command line?

 Have not switched to init 3 to try.


 Are there any errors (EE) or warnings (WW) in /var/log/Xorg.0.log?

 (EE) open /dev/fb0: No such device

 (WW) Falling back to old probe method for vesa
 (WW) Falling back to old probe method for fbdev
 (WW) CHROME(0): Manufacturer plainly copied main PCI IDs to subsystem/card
 IDs.
 (WW) CHROME(0): Unable to estimate virtual size
 (WW) CHROME(0): [XvMC] XvMC is not supported on this chipset
 (WW) Lid Switch: Don't know how to use device


 Anything in /var/log/messages or dmesg?

 what would I search for?
 Error messages pertaining to the video controller.


 What is the output of lspci | grep VGA?
 01:00.0 VGA compatible controller: VIA Technologies, Inc. CX700/VX700 [S3
 UniChrome Pro] (rev 03)
 Use the info in this line (VIA CX700 VX700 or UniChrome Pro) to do a
 google search.  Add linux to the search terms to see what driver you need.

I had another oqo2 in the dustbin with C5.3 on it.  I powered it up and 
it came up in init 3 mode.  When I did startx the external monitor came 
up nicely, but the system's screen was white.

Then I remembered (they have been in the dustbin for a few years).

I never got the video working back on C5.3.  In fact I had to play 
around with xorg.conf to get better than 800x640 for the external 
monitor, so C6.3 is an improvement.

So no driver that I can find.  Oh well.  They will just be little 
servers for testing.


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] Centos 6.3 and dovecot with an abrt problem

2013-02-23 Thread Gregory P. Ennis
Everyone,

I have a mail server  running CentOS release 6.3 (Final) with
2.6.32-279.22.1.el6.i686 kernel that is reporting errors to me
pertaining dovecot.  I have appended the error message to this note.
There is only one user that appears to generate this message, and it is
generated to me by way of e-mail without a perceptible problem to the
user which is not me.  

This particular user had an inbox greater than 2 gigs in size, so I
asked him to move or delete unwanted files, which reduced the size of
the inbox to 400 megs.  Unfortunately, the abrt messages have
continued.  

I did a google search on  : usr/libexec/dovecot/imap was killed by
signal 6, but did not find much that I could use to help me debug this.
Can any of you point me in the right direction.
'
Thanks much!!!

Greg


From:   u...@domain.com
To: r...@domain.com
Subject:[abrt] full crash report
Date:   Fri, 22 Feb 2013 17:57:29 -0600


abrt_version:   2.0.8
cmdline:dovecot/imap
environ:'\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab
\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab
\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab
\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab
\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab
\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab
\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab
\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab
\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab
\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab
\xab\xab'
executable: /usr/libexec/dovecot/imap
kernel: 2.6.32-279.22.1.el6.i686
pid:12871
pwd:/home/user
reason: Process /usr/libexec/dovecot/imap was killed by signal 6
(SIGABRT)
time:   Fri 22 Feb 2013 05:56:56 PM CST
uid:507
username:   user

sosreport.tar.xz: Binary file, 2236756 bytes

limits:
:Limit Soft Limit   Hard Limit
Units 
:Max cpu time  unlimitedunlimited
seconds   
:Max file size unlimitedunlimited
bytes 
:Max data size unlimitedunlimited
bytes 
:Max stack size10485760 unlimited
bytes 
:Max core file size0unlimited
bytes 
:Max resident set  unlimitedunlimited
bytes 
:Max processes 1024 19090
processes 
:Max open files1024 4096
files 
:Max locked memory 6553665536
bytes 
:Max address space unlimitedunlimited
bytes 
:Max file locksunlimitedunlimited
locks 
:Max pending signals   1909019090
signals   
:Max msgqueue size 819200   819200
bytes 
:Max nice priority 00
:Max realtime priority 00
:Max realtime timeout  unlimitedunlimited
us

maps:
:001ec000-001f8000 r-xp  08:07
2108047/lib/libnss_files-2.12.so
:001f8000-001f9000 r--p b000 08:07
2108047/lib/libnss_files-2.12.so
:001f9000-001fa000 rw-p c000 08:07
2108047/lib/libnss_files-2.12.so
:00595000-00596000 r-xp  00:00 0  [vdso]
:0069b000-006b9000 r-xp  08:07 2109054/lib/ld-2.12.so
:006b9000-006ba000 r--p 0001d000 08:07 2109054/lib/ld-2.12.so
:006ba000-006bb000 rw-p 0001e000 08:07 2109054/lib/ld-2.12.so
:006bd000-0084d000 r-xp  08:07 2109055/lib/libc-2.12.so
:0084d000-0084f000 r--p 0018f000 08:07 2109055/lib/libc-2.12.so
:0084f000-0085 rw-p 00191000 08:07 2109055/lib/libc-2.12.so
:0085-00853000 rw-p  00:00 0 
:00881000-00884000 r-xp  08:07 2109061/lib/libdl-2.12.so
:00884000-00885000 r--p 2000 08:07 2109061/lib/libdl-2.12.so
:00885000-00886000 rw-p 3000 08:07 2109061/lib/libdl-2.12.so
:00888000-0089f000 r-xp  08:07
2109060/lib/libpthread-2.12.so
:0089f000-008a r--p 00016000 08:07
2109060/lib/libpthread-2.12.so
:008a-008a1000 rw-p 00017000 08:07
2109060/lib/libpthread-2.12.so
:008a1000-008a3000 rw-p  00:00 0 
:008bb000-008c2000 r-xp  08:07 2109063/lib/librt-2.12.so
:008c2000-008c3000 r--p 6000 08:07 2109063/lib/librt-2.12.so
:008c3000-008c4000 rw-p 7000 08:07 2109063/lib/librt-2.12.so
:008c6000-00946000 r-xp  08:07
1071940/usr/lib/dovecot/libdovecot.so.0.0.0
:00946000-00948000 rw-p 0007f000 08:07
1071940/usr/lib/dovecot/libdovecot.so.0.0.0
:00948000-00949000 rw-p  00:00 0 
:0094b000-00a21000 r-xp  08:07
1079292/usr/lib/dovecot/libdovecot-storage.so.0.0.0
:00a21000-00a25000 rw-p 000d6000 08:07

Re: [CentOS] CentOS 6.3: libreport/abrt update problem

2013-02-01 Thread Johnny Hughes
On 02/01/2013 01:33 AM, Akemi Yagi wrote:
 On Thu, Jan 31, 2013 at 10:52 PM, Mogens Kjaer m...@lemo.dk wrote:
 Hello,

 In updates, there are new packages of abrt and libreport.

 But yum update gives me:

 Error: Package: abrt-2.0.8-6.el6.centos.2.x86_64 (updates)
 Requires: libreport = 2.0.9-5.el6_3.2
 Removing: libreport-2.0.9-5.el6.centos.x86_64 (@base)
 libreport = 2.0.9-5.el6.centos
 Updated By: libreport-2.0.9-5.el6.centos.2.x86_64 (updates)
 libreport = 2.0.9-5.el6.centos.2
   You could try using --skip-broken to work around the problem
   You could try running: rpm -Va --nofiles --nodigest

 Is the new libreport incorrectly named

 libreport-2.0.9-5.el6.centos.2.x86_64

 instead of:

 libreport-2.0.9-5.el6.2.x86_64

 or is the dependency of abrt incorrect?

 Mogens

 abrt does requires libreport = 2.0.9-5.el6_3.2.

 Problem seems to be that 2.0.9-5.el6.centos.2 is older than 2.0.9-5.el6_3.2 .


I am working this issue right now, should be fixed in about an hour.



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3: libreport/abrt update problem

2013-02-01 Thread odusseas
Luigi Rosa lists@... writes:

 
 
 Mogens Kjaer said the following on 01/02/2013 07:52:
 
  In updates, there are new packages of abrt and libreport. But yum update
  gives me: Error: Package: abrt-2.0.8-6.el6.centos.2.x86_64 (updates)
 
 Confirmed. Same issue here.
 
 Ciao,
 luigi
 


The same problem also for me!!
any help??
Cheers

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3: libreport/abrt update problem

2013-02-01 Thread Fabien Archambault
2013/2/1 odusseas piskopakis_antr...@hotmail.com:
 Luigi Rosa lists@... writes:



 Mogens Kjaer said the following on 01/02/2013 07:52:

  In updates, there are new packages of abrt and libreport. But yum update
  gives me: Error: Package: abrt-2.0.8-6.el6.centos.2.x86_64 (updates)

 Confirmed. Same issue here.

 Ciao,
 luigi



 The same problem also for me!!
 any help??
 Cheers

 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

You can just skip, temporarily the update of abrt with:
yum update --exclude=abrt\*


This should leave only abrt not updated (not a huge issue) or just
wait a couple of days until it is fixed.

Cheers,
Fabien
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 - which repos to use?

2013-02-01 Thread Timothy Murphy
Les Mikesell wrote:

 Using any single 3rd party repo is likely to work at least until the
 next update because the contents will have been tested against the
 base distro - as long as the packages are intended for use with
 RHEL/Centos.

I have a slightly different question.
I had kbsingh-CentOS-Extras.repo enabled until recently.
Is disabling a repo that has been in use likely to cause any problems?


-- 
Timothy Murphy  
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College Dublin


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 - which repos to use?

2013-02-01 Thread Les Mikesell
On Fri, Feb 1, 2013 at 9:38 AM, Timothy Murphy gayle...@eircom.net wrote:
 Les Mikesell wrote:

 Using any single 3rd party repo is likely to work at least until the
 next update because the contents will have been tested against the
 base distro - as long as the packages are intended for use with
 RHEL/Centos.

 I have a slightly different question.
 I had kbsingh-CentOS-Extras.repo enabled until recently.
 Is disabling a repo that has been in use likely to cause any problems?

Generally not.  It just means that you won't get any updates on
packages that only exist in that repo.  However there is some chance
that a same-named package will appear with a higher version number in
a different, enabled repo - and if it doesn't have the same origin
there is some chance of it being incompatible in some way.   This is
more likely to result in a single broken app than yum conflicts,
though.

-- 
   Les Mikesell
  lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3: libreport/abrt update problem

2013-02-01 Thread Luigi Rosa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Johnny Hughes said the following on 01/02/2013 11:29:

 I am working this issue right now, should be fixed in about an hour.

It is, thanks.




Ciao,
luigi

- -- 
/
+--[Luigi Rosa]--
\

Mathematicians do it in theory.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlEMDG8ACgkQ3kWu7Tfl6ZSoqgCeK2cH4HhnQblsLfSsAMLxy8BM
uuYAoLHRVVAktPZcEr7l2Z/Si13WCcAm
=l4Ru
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3: libreport/abrt update problem

2013-02-01 Thread Johnny Hughes
On 02/01/2013 05:41 AM, Fabien Archambault wrote:
 2013/2/1 odusseas piskopakis_antr...@hotmail.com:
 Luigi Rosa lists@... writes:


 Mogens Kjaer said the following on 01/02/2013 07:52:

 In updates, there are new packages of abrt and libreport. But yum update
 gives me: Error: Package: abrt-2.0.8-6.el6.centos.2.x86_64 (updates)
 Confirmed. Same issue here.

 Ciao,
 luigi


 The same problem also for me!!
 any help??
 Cheers

 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos
 You can just skip, temporarily the update of abrt with:
 yum update --exclude=abrt\*


 This should leave only abrt not updated (not a huge issue) or just
 wait a couple of days until it is fixed.

For the record, the fix is pushed, however some of our external mirrors
only sync a couple of times per day .. so it may take a day for them to
get fixed.

If you absolutely need that package updated, you can point the updates
repo to mirror.centos.org and yum clean all then yum update.



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 - which repos to use?

2013-01-31 Thread Les Mikesell
On Thu, Jan 31, 2013 at 1:03 AM, Bry8 Star bry8s...@yahoo.com wrote:
 When using multiple repo, then how would i know, an
 app/lib from non-CentOS (that is, 3rd party repo) is going
 to conflict or not with CentOS core, base, essential
 app/lib packages ?


I don't think there is any way to know that.   And more to the point,
using any single 3rd party repo is likely to work at least until the
next update because the contents will have been tested against the
base distro - as long as the packages are intended for use with
RHEL/Centos.   The harder problem is that when you use multiple 3rd
party repos you can have packages with the same names and leapfrogging
version numbers but that are built or configured differently.   So you
install from one repo but it appears later with a higher version
number in a different one that you have enabled and is replaced by
something you don't expect.   This may cause dependency issues in the
yum update or sometimes just as bad, update without errors but fail to
work because of build or configuration differences.   I've always
thought it would be helpful if yum notified you whenever it was about
to overwrite an existing package with one from a different repo, but
even that might not be enough.

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] CentOS 6.3: libreport/abrt update problem

2013-01-31 Thread Mogens Kjaer
Hello,

In updates, there are new packages of abrt and libreport.

But yum update gives me:

Error: Package: abrt-2.0.8-6.el6.centos.2.x86_64 (updates)
Requires: libreport = 2.0.9-5.el6_3.2
Removing: libreport-2.0.9-5.el6.centos.x86_64 (@base)
libreport = 2.0.9-5.el6.centos
Updated By: libreport-2.0.9-5.el6.centos.2.x86_64 (updates)
libreport = 2.0.9-5.el6.centos.2
  You could try using --skip-broken to work around the problem
  You could try running: rpm -Va --nofiles --nodigest

Is the new libreport incorrectly named

libreport-2.0.9-5.el6.centos.2.x86_64

instead of:

libreport-2.0.9-5.el6.2.x86_64

or is the dependency of abrt incorrect?

Mogens

-- 
Mogens Kjaer, m...@lemo.dk
http://www.lemo.dk
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3: libreport/abrt update problem

2013-01-31 Thread Akemi Yagi
On Thu, Jan 31, 2013 at 10:52 PM, Mogens Kjaer m...@lemo.dk wrote:
 Hello,

 In updates, there are new packages of abrt and libreport.

 But yum update gives me:

 Error: Package: abrt-2.0.8-6.el6.centos.2.x86_64 (updates)
 Requires: libreport = 2.0.9-5.el6_3.2
 Removing: libreport-2.0.9-5.el6.centos.x86_64 (@base)
 libreport = 2.0.9-5.el6.centos
 Updated By: libreport-2.0.9-5.el6.centos.2.x86_64 (updates)
 libreport = 2.0.9-5.el6.centos.2
   You could try using --skip-broken to work around the problem
   You could try running: rpm -Va --nofiles --nodigest

 Is the new libreport incorrectly named

 libreport-2.0.9-5.el6.centos.2.x86_64

 instead of:

 libreport-2.0.9-5.el6.2.x86_64

 or is the dependency of abrt incorrect?

 Mogens


abrt does requires libreport = 2.0.9-5.el6_3.2.

Problem seems to be that 2.0.9-5.el6.centos.2 is older than 2.0.9-5.el6_3.2 .

Akemi
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3: libreport/abrt update problem

2013-01-31 Thread Luigi Rosa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Mogens Kjaer said the following on 01/02/2013 07:52:

 In updates, there are new packages of abrt and libreport. But yum update
 gives me: Error: Package: abrt-2.0.8-6.el6.centos.2.x86_64 (updates)

Confirmed. Same issue here.



Ciao,
luigi

- -- 
/
+--[Luigi Rosa]--
\

Xerox never comes up with anything original.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlELcBEACgkQ3kWu7Tfl6ZQCaACgyL3cYJfkP3Wi9quz2Os0NkAv
JaMAoLCz/p7NQGYg3rxSniWMKBnTZ370
=DDQs
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 - which repos to use?

2013-01-30 Thread Bry8 Star
* Another way to use multiple repo, other than what i
mentioned in previous email (different repo with different
priority# ), is to:
* Set all repo's base, main/default, stable, extra, etc
sections/channels on priority 10, and set all repo's other
channels/sections like testing, (source, debuginfo, )
etc on priority 15:
repo#1 main-sections priority 10, others  15
repo#2 main-sections priority 10, others  15
repo#3 main-sections priority 10, others  15
repo#4 main-sections priority 10, others  15
* Use only RHEL compatible channels of any repo. (Avoid
fedora, generic, other-non-Rhel-distro, etc, unless you
are getting source/src.rpm/SRPM for rebuilding on CentOS ).
* Since they all has same priority, highest/last version
will get highest preference.
* run : yum groupinfo Base
It will show Mandatory, Default, etc app list for CentOS.
And run this before adding other repo, so that you get a
fresh list related only to CentOS.
* run : yum check-update
or, run : yum list updates
--disableplugin=filter-data,priorities
--disableexcludes=all --enablerepo=\*
(First try without --enablerepo=\* option )
* You will see, (or If you see,) any other 3d party repo
(other than CentOS ) app/libs, is/are trying to replace
base/core components from CentOS Mandatory, Default, etc
category areas, then put those pkgs/apps/libs in
exclude=pkg-name .., inside those 3rd party repo, so
that those pkgs do not replace base/core CentOS components.
* And, if you choose a very specific app/lib from a very
specific repo, for example, postgresql from Postgresql
repo, then see my previous email for exclude list, place
those postgresql related pkgs/items in all repo in their
all sections/channels other than Postgresql repo itself,
including CentOS repo in all sections/channels.
* Do not do actual update, unless you see or you are 100%
sure, shown repo and apps/libs/pkg are coming from the
repo/channel which you want and safe, if you are not sure,
ask for help here but search on google, read more docs,
manuals, and research little bit first.
* If you search with words like these : pkgname error
problem or pkgname error problem centos, then you
should/will see what kind of error or problem may occur
with that pkg. Take steps so that no error occurs.

Please correct my mistake(s) on these simple (above )
suggestions, info.
Thanks,
-- Bright Star.



Received from Bry8 Star, on 2013-01-30 4:08 AM:
 Sorry, mentioned [pgdg92] twice. Pls ignore/delete
 the [pgdg92] that has priority 15.
 
 
 
 Received from Bry8 Star, on 2013-01-28 10:16 AM:
 For PostgreSQL, i've done these (shown below) at
 initial/test stage: (pls DO NOT follow/copy it,
 try to understand pattern and do what fits for
 your case/need).

 From a VE instance inside HN:

 yum has these plugins:
 fastestmirror, filter-data, keys,
 list-data, merge-conf, presto, priorities, security, verify.

 # CentOS-Base.repo
 [CentOS-base]
 #...snip...
 enabled=1
 # i do not want below set from centos repo
 # as these exacts are released by postgre devs
 # but other postgre portions from others i do want
 exclude=postgresql.* postgresql-contrib*
 postgresql-debuginfo* postgresql-devel* postgresql-docs*
 postgresql-jdbc.* postgresql-jdbc-debuginfo* postgresql-libs*
 postgresql-odbc.i686 postgresql-odbc-debuginfo*
 postgresql-plperl* postgresql-plpython* postgresql-pltcl*
 postgresql-server* postgresql-tcl.i686 postgresql-tcl-debuginfo*
 postgresql-test*
 priority=1

 [CentOS-updates]
 #...snip...
 enabled=1
 exclude=postgresql.*
 postgresql-contrib* postgresql-debuginfo* postgresql-devel*
 postgresql-docs* postgresql-jdbc.* postgresql-jdbc-debuginfo*
 postgresql-libs* postgresql-odbc.i686 postgresql-odbc-debuginfo*
 postgresql-plperl* postgresql-plpython* postgresql-pltcl*
 postgresql-server* postgresql-tcl.i686 postgresql-tcl-debuginfo*
 postgresql-test*
 priority=1

 [CentOS-extras]
 #...snip...
 enabled=1
 exclude=postgresql.*
 postgresql-contrib* postgresql-debuginfo* postgresql-devel*
 postgresql-docs* postgresql-jdbc.* postgresql-jdbc-debuginfo*
 postgresql-libs* postgresql-odbc.i686 postgresql-odbc-debuginfo*
 postgresql-plperl* postgresql-plpython* postgresql-pltcl*
 postgresql-server* postgresql-tcl.i686 postgresql-tcl-debuginfo*
 postgresql-test*
 priority=1

 [CentOSplus]
 #...snip...
 enabled=1
 exclude=kernel.*
 kernel-firmware.* kernel-headers.* postgresql.* 
 postgresql-contrib* postgresql-debuginfo* postgresql-devel* 
 postgresql-docs* postgresql-jdbc.* postgresql-jdbc-debuginfo* 
 postgresql-libs* postgresql-odbc.i686 postgresql-odbc-debuginfo* 
 postgresql-plperl* postgresql-plpython* postgresql-pltcl* 
 postgresql-server* postgresql-tcl.i686 postgresql-tcl-debuginfo* 
 postgresql-test*
 priority=1

 # pgdg92-centos.repo
 [pgdg92]
 #...snip...
 enabled=1 
 priority=10

 [pgdg92-source]
 #...snip...
 enabled=1
 priority=10

 #scntflnx.repo
 [SciLnx-6x-os]
 #...snip...
 enabled=1 
 exclude=redhat-rpm-config.* postgresql.* postgresql-devel* 
 postgresql-docs* postgresql-contrib* 

Re: [CentOS] Centos 6.3 - which repos to use?

2013-01-30 Thread Bry8 Star
When using multiple repo, then how would i know, an
app/lib from non-CentOS (that is, 3rd party repo) is going
to conflict or not with CentOS core, base, essential
app/lib packages ?

We need to know CentOS core, base, essential components.

According to this file:

/usr/lib/anaconda/installclasses/rhel.py

That is located inside the mounted image of this below file:
http://mirror.centos.org/centos-6/6/os/x86_64/images/install.img

or
http://mirror.centos.org/centos-6/6/os/x86/images/install.img

* A CentOS Basic Server has : base, console-internet,
core, debugging, directory-client, hardware-monitoring,
java-platform, large-systems, network-file-system-client,
performance, perl-runtime, server-platform.
* Database Server : Basic Server (shown above), and,
mysql-client, mysql, postgresql-client, postgresql,
system-admin-tools.
* Web Server: Basic Server (shown above), and,
mysql-client, php, postgresql-client, turbogears,
web-server, web-servlet.

So below command will show what app/lib/pkg are in Basic
Server, and should not be replaced by a 3rd party repo
packages:

yum groupinfo base core Console internet tools
Directory Client Java Platform Network file system
client Server Platform debugging large-systems
performance perl-runtime hardware-monitoring
--disablerepo=\* --enablerepo=base,extra,update
--disableplugin=filter-data,priorities --disableexcludes=all

in above, it is, one command-line, (text-based
email-system will break it, so remove LF/CR char to get
full command-line )

You must try to avoid replacing those, (centos essential
packages).

Copy the list in a text file, remove lines(LF/CR), make
paragraphs, and print it out or keep the text file easily
accessible location. So you can see it to decide, on 3rd
party repo which package should be placed inside exclude.

If there is/are mistake(s) in above suggestion, please
correct.
Please post better, other way(s) to achieve these.

Thanks,
-- Bright Star.



Received from Bry8 Star, on 2013-01-28 10:16 AM:
 For PostgreSQL, i've done these (shown below) at initial/test stage:
 (pls DO NOT follow/copy it, try to understand pattern and do what
 fits for your case/need).
 
 From a VE instance inside HN:
 
 yum has these plugins: fastestmirror, filter-data, keys, list-data,
 merge-conf, presto, priorities, security, verify.
 
 # CentOS-Base.repo
 [CentOS-base]
 #...snip...
 enabled=1
 # i do not want below set from centos repo
 # as these exacts are released by postgre devs
 # but other postgre portions from others i do want
 exclude=postgresql.* postgresql-contrib* postgresql-debuginfo*
 postgresql-devel* postgresql-docs* postgresql-jdbc.*
 postgresql-jdbc-debuginfo* postgresql-libs* postgresql-odbc.i686
 postgresql-odbc-debuginfo* postgresql-plperl* postgresql-plpython*
 postgresql-pltcl* postgresql-server* postgresql-tcl.i686
 postgresql-tcl-debuginfo* postgresql-test*
 priority=1
 
 [CentOS-updates]
 #...snip...
 enabled=1
 exclude=postgresql.* postgresql-contrib* postgresql-debuginfo*
 postgresql-devel* postgresql-docs* postgresql-jdbc.*
 postgresql-jdbc-debuginfo* postgresql-libs* postgresql-odbc.i686
 postgresql-odbc-debuginfo* postgresql-plperl* postgresql-plpython*
 postgresql-pltcl* postgresql-server* postgresql-tcl.i686
 postgresql-tcl-debuginfo* postgresql-test*
 priority=1
 
 [CentOS-extras]
 #...snip...
 enabled=1
 exclude=postgresql.* postgresql-contrib* postgresql-debuginfo*
 postgresql-devel* postgresql-docs* postgresql-jdbc.*
 postgresql-jdbc-debuginfo* postgresql-libs* postgresql-odbc.i686
 postgresql-odbc-debuginfo* postgresql-plperl* postgresql-plpython*
 postgresql-pltcl* postgresql-server* postgresql-tcl.i686
 postgresql-tcl-debuginfo* postgresql-test*
 priority=1
 
 [CentOSplus]
 #...snip...
 enabled=1
 exclude=kernel.* kernel-firmware.* kernel-headers.* postgresql.*
 postgresql-contrib* postgresql-debuginfo* postgresql-devel*
 postgresql-docs* postgresql-jdbc.* postgresql-jdbc-debuginfo*
 postgresql-libs* postgresql-odbc.i686 postgresql-odbc-debuginfo*
 postgresql-plperl* postgresql-plpython* postgresql-pltcl*
 postgresql-server* postgresql-tcl.i686 postgresql-tcl-debuginfo*
 postgresql-test*
 priority=1
 
 # pgdg92-centos.repo
 [pgdg92]
 #...snip...
 enabled=1
 priority=10
 
 [pgdg92-source]
 #...snip...
 enabled=1
 priority=10
 
 #scntflnx.repo
 [SciLnx-6x-os]
 #...snip...
 enabled=1
 exclude=redhat-rpm-config.* postgresql.* postgresql-devel*
 postgresql-docs* postgresql-contrib* postgresql-jdbc.*
 postgresql-libs* postgresql-odbc* postgresql-plperl*
 postgresql-plpython* postgresql-pltcl* postgresql-server*
 postgresql-test*
 priority=13
 
 [SciLnx-6x-updates-fastbugs]
 #...snip...
 enabled=1
 exclude=postgresql.* postgresql-devel* postgresql-docs*
 postgresql-contrib* postgresql-jdbc.* postgresql-libs*
 postgresql-odbc* postgresql-plperl* postgresql-plpython*
 postgresql-pltcl* postgresql-server* postgresql-test*
 priority=13
 
 [SciLnx-6x-updates-security]
 #...snip...
 enabled=1
 exclude=postgresql.* postgresql-devel* 

Re: [CentOS] Centos 6.3 - which repos to use?

2013-01-30 Thread Ibrahim Yurtseven
On 24.01.2013 23:26, Nux! wrote:
 If you'd like to try, I do maintain a desktop related repository meant
 to not conflict with @Base or EPEL (or Elrepo):
You are backporting pkgs from fedora to el6.
Imho you should supply your manpower to epel, because epel provides 
backported pkgs!

-- 
Ibrahim Arastirmacilar Yurtseven
The web is what you make of it
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] centos 6.3 git core.sharedRepository = group/all not working?

2013-01-29 Thread Min Wang
HI

I have a git bare repo on centos 6.3 ( with selinux off)

the config is:
[core]
 repositoryformatversion = 0
 filemode = true
 bare = true
 sharedRepository = all  ( or true or group)


chmod -R g+rs objects

when  git pushed the changes from remote ssh .

the new file under objects are not writable.
e.g.:

-r--r--r--. 1 myuser mygroup 156 Jan 29 22:22 
objects/fa/905054c795a3b7e5c244bfc6f3a30a0277c6d0

what could be wrong?


thanks.

min



___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 - which repos to use?

2013-01-29 Thread Bry8 Star
Sorry, mentioned [pgdg92] twice. Pls ignore/delete the [pgdg92] that
has priority 15.



Received from Bry8 Star, on 2013-01-28 10:16 AM:
 For PostgreSQL, i've done these (shown below) at initial/test
 stage: (pls DO NOT follow/copy it, try to understand pattern and
 do what fits for your case/need).
 
 From a VE instance inside HN:
 
 yum has these plugins:
 fastestmirror, filter-data, keys,
 list-data, merge-conf, presto, priorities, security, verify.
 
 # CentOS-Base.repo
 [CentOS-base]
 #...snip...
 enabled=1
 # i do not want below set from centos repo
 # as these exacts are released by postgre devs
 # but other postgre portions from others i do want
 exclude=postgresql.* postgresql-contrib*
 postgresql-debuginfo* postgresql-devel* postgresql-docs*
 postgresql-jdbc.* postgresql-jdbc-debuginfo* postgresql-libs*
 postgresql-odbc.i686 postgresql-odbc-debuginfo*
 postgresql-plperl* postgresql-plpython* postgresql-pltcl*
 postgresql-server* postgresql-tcl.i686 postgresql-tcl-debuginfo*
 postgresql-test*
 priority=1
 
 [CentOS-updates]
 #...snip...
 enabled=1
 exclude=postgresql.*
 postgresql-contrib* postgresql-debuginfo* postgresql-devel*
 postgresql-docs* postgresql-jdbc.* postgresql-jdbc-debuginfo*
 postgresql-libs* postgresql-odbc.i686 postgresql-odbc-debuginfo*
 postgresql-plperl* postgresql-plpython* postgresql-pltcl*
 postgresql-server* postgresql-tcl.i686 postgresql-tcl-debuginfo*
 postgresql-test*
 priority=1
 
 [CentOS-extras]
 #...snip...
 enabled=1
 exclude=postgresql.*
 postgresql-contrib* postgresql-debuginfo* postgresql-devel*
 postgresql-docs* postgresql-jdbc.* postgresql-jdbc-debuginfo*
 postgresql-libs* postgresql-odbc.i686 postgresql-odbc-debuginfo*
 postgresql-plperl* postgresql-plpython* postgresql-pltcl*
 postgresql-server* postgresql-tcl.i686 postgresql-tcl-debuginfo*
 postgresql-test*
 priority=1
 
 [CentOSplus]
 #...snip...
 enabled=1
 exclude=kernel.*
 kernel-firmware.* kernel-headers.* postgresql.* 
 postgresql-contrib* postgresql-debuginfo* postgresql-devel* 
 postgresql-docs* postgresql-jdbc.* postgresql-jdbc-debuginfo* 
 postgresql-libs* postgresql-odbc.i686 postgresql-odbc-debuginfo* 
 postgresql-plperl* postgresql-plpython* postgresql-pltcl* 
 postgresql-server* postgresql-tcl.i686 postgresql-tcl-debuginfo* 
 postgresql-test*
 priority=1
 
 # pgdg92-centos.repo
 [pgdg92]
 #...snip...
 enabled=1 
 priority=10
 
 [pgdg92-source]
 #...snip...
 enabled=1
 priority=10
 
 #scntflnx.repo
 [SciLnx-6x-os]
 #...snip...
 enabled=1 
 exclude=redhat-rpm-config.* postgresql.* postgresql-devel* 
 postgresql-docs* postgresql-contrib* postgresql-jdbc.* 
 postgresql-libs* postgresql-odbc* postgresql-plperl* 
 postgresql-plpython* postgresql-pltcl* postgresql-server* 
 postgresql-test*
 priority=13
 
 [SciLnx-6x-updates-fastbugs]
 #...snip...
 enabled=1 
 exclude=postgresql.* postgresql-devel* postgresql-docs* 
 postgresql-contrib* postgresql-jdbc.* postgresql-libs* 
 postgresql-odbc* postgresql-plperl* postgresql-plpython* 
 postgresql-pltcl* postgresql-server* postgresql-test* 
 priority=13
 
 [SciLnx-6x-updates-security]
 #...snip...
 enabled=1 
 exclude=postgresql.* postgresql-devel* postgresql-docs* 
 postgresql-contrib* postgresql-jdbc.* postgresql-libs* 
 postgresql-odbc* postgresql-plperl* postgresql-plpython* 
 postgresql-pltcl* postgresql-server* postgresql-test* 
 priority=13
 
 [SciLnx-6x-debuginfo]
 #...snip...
 enabled=0
 priority=13
 
 [SciLnx-6x-SRPMS]
 #...snip...
 enabled=1
 priority=13
 
 [pgdg92]
 #...snip...
 enabled=1
 priority=15
 
 ... other repo  distro ...
 
 In above way, i get most from PosteGre repo, and other postgre 
 related side packages from other repos. if i were to place 
 exclude=postgre* then all packages would have gotten excluded,
 and then the extra postgre pkg which are not released by postgre,
 would get hidden/excluded as well, though, i could have used this
 approach for to get that:
 
 includepkgs=related-extra-postgre-pkg
 
 to get those. but then i would need specific name, but what if
 new extra pkg that i dont know yet, is included, but since i have
 not specified specifically, those would get hidden/excluded. (my
 repo inquiries have shown, many other repo has at-least 1 to 3 or
 some up to 6 extra postgre related tools which are not released 
 by postgre devs themselves).
 
 Few patterns/logics which i like to follow:
 
 repo#1, rpm priority 1, srpm priority 50
 repo#2, rpm priority 10, srpm priority 40
 repo#3, rpm priority 15, srpm priority 30 
 repo#4, rpm priority 20, srpm priority 20
 ...
 
 Priority numbering pattern/logic:
 Since i'm using centos as my
 base, so various DISTRO  REPO rpm/binary which are closest to
 CentOS  CentOS's source RHEL, those distro  repo will get
 lowest priority# close to centos. i like to think/visualize in
 this way ... a LIST from top to down, now number them from top to
 bottom 1, 2, 3.. CentOS is at position 1, the top-most position. 
 The lowest priority number, is at highest, upper position in the
 

Re: [CentOS] centos 6.3 git core.sharedRepository = group/all not working?

2013-01-29 Thread Phil Dobbin
On 01/30/2013 03:34 AM, Min Wang wrote:

 HI
 
 I have a git bare repo on centos 6.3 ( with selinux off)
 
 the config is:
 [core]
  repositoryformatversion = 0
  filemode = true
  bare = true
  sharedRepository = all  ( or true or group)
 
 
 chmod -R g+rs objects
 
 when  git pushed the changes from remote ssh .
 
 the new file under objects are not writable.
 e.g.:
 
 -r--r--r--. 1 myuser mygroup 156 Jan 29 22:22 
 objects/fa/905054c795a3b7e5c244bfc6f3a30a0277c6d0
 
 what could be wrong?

You've set the group read permissions but you haven't set any write
permissions.

Take a look at:
http://pic.dhe.ibm.com/infocenter/aix/v6r1/index.jsp?topic=%2Fcom.ibm.aix.cmds%2Fdoc%2Faixcmds1%2Fchmod.htm

Cheers,

  Phil...

-- 
currently (ab)using
CentOS 5.8  6.3, Debian Squeeze  Wheezy, Fedora Beefy  Spherical,
Lubuntu 12.10, OS X Snow Leopard  Ubuntu Precise  Quantal
GnuPG Key : http://www.horse-latitudes.co.uk/publickey.asc


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] centos 6.3 git core.sharedRepository = group/all not working?

2013-01-29 Thread Min Wang
Hi

thanks. I had a typo on my previsous emai

it was:  chmod -R g+rws objects

 -r--r--r--. 1 myuser mygroup 156 Jan 29 22:22
 objects/fa/905054c795a3b7e5c244bfc6f3a30a0277c6d0


min


On Tue, Jan 29, 2013 at 11:18 PM, Phil Dobbin bukowskis...@gmail.comwrote:

 On 01/30/2013 03:34 AM, Min Wang wrote:

  HI
 
  I have a git bare repo on centos 6.3 ( with selinux off)
 
  the config is:
  [core]
   repositoryformatversion = 0
   filemode = true
   bare = true
   sharedRepository = all  ( or true or group)
 
 
  chmod -R g+rs objects
 
  when  git pushed the changes from remote ssh .
 
  the new file under objects are not writable.
  e.g.:
 
  -r--r--r--. 1 myuser mygroup 156 Jan 29 22:22
  objects/fa/905054c795a3b7e5c244bfc6f3a30a0277c6d0
 
  what could be wrong?

 You've set the group read permissions but you haven't set any write
 permissions.

 Take a look at:
 
 http://pic.dhe.ibm.com/infocenter/aix/v6r1/index.jsp?topic=%2Fcom.ibm.aix.cmds%2Fdoc%2Faixcmds1%2Fchmod.htm
 

 Cheers,

   Phil...

 --
 currently (ab)using
 CentOS 5.8  6.3, Debian Squeeze  Wheezy, Fedora Beefy  Spherical,
 Lubuntu 12.10, OS X Snow Leopard  Ubuntu Precise  Quantal
 GnuPG Key : http://www.horse-latitudes.co.uk/publickey.asc


 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 - which repos to use?

2013-01-28 Thread Bry8 Star
For PostgreSQL, i've done these (shown below) at initial/test stage:
(pls DO NOT follow/copy it, try to understand pattern and do what
fits for your case/need).

From a VE instance inside HN:

yum has these plugins: fastestmirror, filter-data, keys, list-data,
merge-conf, presto, priorities, security, verify.

# CentOS-Base.repo
[CentOS-base]
#...snip...
enabled=1
# i do not want below set from centos repo
# as these exacts are released by postgre devs
# but other postgre portions from others i do want
exclude=postgresql.* postgresql-contrib* postgresql-debuginfo*
postgresql-devel* postgresql-docs* postgresql-jdbc.*
postgresql-jdbc-debuginfo* postgresql-libs* postgresql-odbc.i686
postgresql-odbc-debuginfo* postgresql-plperl* postgresql-plpython*
postgresql-pltcl* postgresql-server* postgresql-tcl.i686
postgresql-tcl-debuginfo* postgresql-test*
priority=1

[CentOS-updates]
#...snip...
enabled=1
exclude=postgresql.* postgresql-contrib* postgresql-debuginfo*
postgresql-devel* postgresql-docs* postgresql-jdbc.*
postgresql-jdbc-debuginfo* postgresql-libs* postgresql-odbc.i686
postgresql-odbc-debuginfo* postgresql-plperl* postgresql-plpython*
postgresql-pltcl* postgresql-server* postgresql-tcl.i686
postgresql-tcl-debuginfo* postgresql-test*
priority=1

[CentOS-extras]
#...snip...
enabled=1
exclude=postgresql.* postgresql-contrib* postgresql-debuginfo*
postgresql-devel* postgresql-docs* postgresql-jdbc.*
postgresql-jdbc-debuginfo* postgresql-libs* postgresql-odbc.i686
postgresql-odbc-debuginfo* postgresql-plperl* postgresql-plpython*
postgresql-pltcl* postgresql-server* postgresql-tcl.i686
postgresql-tcl-debuginfo* postgresql-test*
priority=1

[CentOSplus]
#...snip...
enabled=1
exclude=kernel.* kernel-firmware.* kernel-headers.* postgresql.*
postgresql-contrib* postgresql-debuginfo* postgresql-devel*
postgresql-docs* postgresql-jdbc.* postgresql-jdbc-debuginfo*
postgresql-libs* postgresql-odbc.i686 postgresql-odbc-debuginfo*
postgresql-plperl* postgresql-plpython* postgresql-pltcl*
postgresql-server* postgresql-tcl.i686 postgresql-tcl-debuginfo*
postgresql-test*
priority=1

# pgdg92-centos.repo
[pgdg92]
#...snip...
enabled=1
priority=10

[pgdg92-source]
#...snip...
enabled=1
priority=10

#scntflnx.repo
[SciLnx-6x-os]
#...snip...
enabled=1
exclude=redhat-rpm-config.* postgresql.* postgresql-devel*
postgresql-docs* postgresql-contrib* postgresql-jdbc.*
postgresql-libs* postgresql-odbc* postgresql-plperl*
postgresql-plpython* postgresql-pltcl* postgresql-server*
postgresql-test*
priority=13

[SciLnx-6x-updates-fastbugs]
#...snip...
enabled=1
exclude=postgresql.* postgresql-devel* postgresql-docs*
postgresql-contrib* postgresql-jdbc.* postgresql-libs*
postgresql-odbc* postgresql-plperl* postgresql-plpython*
postgresql-pltcl* postgresql-server* postgresql-test*
priority=13

[SciLnx-6x-updates-security]
#...snip...
enabled=1
exclude=postgresql.* postgresql-devel* postgresql-docs*
postgresql-contrib* postgresql-jdbc.* postgresql-libs*
postgresql-odbc* postgresql-plperl* postgresql-plpython*
postgresql-pltcl* postgresql-server* postgresql-test*
priority=13

[SciLnx-6x-debuginfo]
#...snip...
enabled=0
priority=13

[SciLnx-6x-SRPMS]
#...snip...
enabled=1
priority=13

[pgdg92]
#...snip...
enabled=1
priority=15

... other repo  distro ...

In above way, i get most from PosteGre repo, and other postgre
related side packages from other repos. if i were to place
exclude=postgre* then all packages would have gotten excluded, and
then the extra postgre pkg which are not released by postgre, would
get hidden/excluded as well, though, i could have used this approach
for to get that:

includepkgs=related-extra-postgre-pkg

to get those. but then i would need specific name, but what if new
extra pkg that i dont know yet, is included, but since i have not
specified specifically, those would get hidden/excluded.
(my repo inquiries have shown, many other repo has at-least 1 to 3
or some up to 6 extra postgre related tools which are not released
by postgre devs themselves).

Few patterns/logics which i like to follow:

repo#1, rpm priority 1, srpm priority 50
repo#2, rpm priority 10, srpm priority 40
repo#3, rpm priority 15, srpm priority 30
repo#4, rpm priority 20, srpm priority 20
...

Priority numbering pattern/logic:
Since i'm using centos as my base,
so various DISTRO  REPO rpm/binary which
are closest to CentOS  CentOS's source RHEL,
those distro  repo will get lowest priority#
close to centos.
i like to think/visualize in this way ...
a LIST from top to down, now number them
from top to bottom 1, 2, 3.. CentOS is at
position 1, the top-most position.
The lowest priority number, is at highest,
upper position in the list, is chosen first
by yum/installer, and has highest priority,
if it(yum) wants to install something.

my knol is this (i could be wrong):
RHEL based source -
|- CentOS base.
|- Scientific Linux.
|- Oracle Linux.
|- ClearOS Linux.

(Fedora stable source - RHEL - RHEL source).

EPEL has extra small tools/apps/libs for

Re: [CentOS] Centos 6.3 - which repos to use?

2013-01-28 Thread Les Mikesell
On Mon, Jan 28, 2013 at 1:40 AM, Bry8 Star bry8s...@yahoo.com wrote:

 If ALL new apps/libs starts to change their API without backward
 compatibility, then, definitely updating/upgrading core/base apps
 would cause domino effect, like you have pointed out. Various apps
 and libs are inter-dependent  inter-connected with each others.

If libs and apps always maintained backwards compatibility, there
wouldn't be much need for 'enterprise' distributions.  They don't.

 But do all ALL apps, or, libs do really change ALL of their API set ?
 My understanding is, some new APIs are added for new features, and
 older same API gets more refined, and/or newer query or response
 parameters are added behind the old existing query/response.

That is very much up to the respective developers.  But eventually
just about everything that isn't a published standard will change.
Even the C language that underlies just about everything on the system
has changed over the years.

 If they(developers) purposefully does not honor backward
 compatibility handling in their app/lib, that is kind of like,
 forcing people to buy new computer/hardware for new Windows8.

It is the nature of youth to believe that everything older than you
are was done wrong, sometimes even just older than the last book you
read. Sometimes even the same developer decides his own earlier work
was done wrong - and in that case he is something of an authority
regardless of the pain it causes the users.   Sometimes they just
can't come up with a way to add needed functionality without changing
behavior - like perl5 starting to interpolate @ in double-quoted
strings.But 'enterprise' linux distributions put a huge effort
into marshaling the wild and crazy changes (like you'd see in
fedora...) into compatible batches at major version releases.

 Why apps/libs are getting bigger in src or in their binary size ?
 with what ! ?

People keep writing more code - and never agree on shared libraries or
languages.  But look at this in terms of the cost of the disk and RAM
to hold them and you'll see that it is really going down so fast that
nobody cares.

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 - which repos to use?

2013-01-28 Thread Nikolaos Milas
On 27/1/2013 5:11 μμ, Johnny Hughes wrote:

 Taking gtk2 as in our example here, if you wanted a new gtk2 in
 CentOS-5.9, then you would have to rebuild the following packages:

A quick (?) question:

What is the best way to view dependencies?

1. We can use yum deplist xxx.rpm to view dependencies of a particular 
installed package, but we would like to limit output to only *already 
installed* packages and not view all suitable ones. Also, we would like 
to view dependencies as a full rpm name and not as they are output by 
default (e.g. not glibc.x86_64 2.12-1.80.el6_3.6 but 
glibc-2.12-1.80.el6_3.6.x86_64)

2. Is there a way to find out the opposite, i.e. which *installed* 
packages are dependent on a particular installed package? In your 
example above (about gtk2), how could we have produced the list of 
dependent-on-it packages which you have kindly provided?

Thanks,
Nick
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 - which repos to use?

2013-01-28 Thread Johnny Hughes
On 01/28/2013 01:26 PM, Nikolaos Milas wrote:
 On 27/1/2013 5:11 μμ, Johnny Hughes wrote:

 Taking gtk2 as in our example here, if you wanted a new gtk2 in
 CentOS-5.9, then you would have to rebuild the following packages:
 A quick (?) question:

 What is the best way to view dependencies?

 1. We can use yum deplist xxx.rpm to view dependencies of a particular 
 installed package, but we would like to limit output to only *already 
 installed* packages and not view all suitable ones. Also, we would like 
 to view dependencies as a full rpm name and not as they are output by 
 default (e.g. not glibc.x86_64 2.12-1.80.el6_3.6 but 
 glibc-2.12-1.80.el6_3.6.x86_64)

 2. Is there a way to find out the opposite, i.e. which *installed* 
 packages are dependent on a particular installed package? In your 
 example above (about gtk2), how could we have produced the list of 
 dependent-on-it packages which you have kindly provided?

With respect to build and SRPMS, I do this:

I go to a place where all the distro's SRPMS (we have that place on
vault), then I do this command:

rpm -qp --requires name.src.rpm

That will tell me everything that is required to build that individual SRPM.

However, you would also need to take every requirement and do the same
thing to it ... in other words, find the requirements of each requirement.

There is no easy way to do this (that I know of) ... if I want to know,
I do the work.

Also, if you want to develop an initial list of SRPMS that are impacted
when changing something, you would do this inside the LATEST SRPMS
(again, using gtk2 as the example):

for srpm in $(ls *.src.rpm); do requires_gtk2=$(rpm -qp --requires $srpm
| grep gtk2-devel); if [ $requires_gtk2 !=  ]; then echo $srpm;
fi; done

(the above is one line if wrapped)

Once you develop the list of SRPMS, you would need to develop  another
list of requirements for each requirement.

There is a yum-utility called yum-builddep that will install all the
dependencies to build a package for you ... you can do that into a
minimal installed VM as well.



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 - which repos to use?

2013-01-28 Thread Bry8 Star
I've tried this command:

yum deplist gnutls --disableplugin=filter-data,priorities
--disableexcludes=all --enablerepo=\*  yum_01.txt

... that yum_01.txt file was around 202KB in my case.

Result is formatted like this:
##...snip...
package: gnutls.i686 2.12.22-1.fc18
dependency: libz.so.1
provider: zlib.i686 1.2.3-27.el6
provider: zlib.i686 1.2.7-9.fc18
provider: zlib.i686 1.2.3-25.el6
provider: zlib.i686 1.2.3-27.el6
provider: zlib.i686 1.2.3-27.el6
provider: zlib.i686 1.2.3-25.el6
provider: zlib.i686 1.2.3-27.el6
provider: zlib.i686 1.2.3-25.el6
provider: zlib.i686 1.2.3-27.el6
dependency: libgcrypt.so.11
provider: libgcrypt.i686 1.5.0-8.fc18
provider: libgcrypt.i686 1.4.5-9.el6_2.2
provider: libgcrypt.i686 1.5.0-6.fc18
provider: libgcrypt11.i686 1.4.0-15.el6
provider: libgcrypt.i686 1.4.5-9.el6
provider: libgcrypt.i686 1.4.5-5.el6
provider: libgcrypt.i686 1.4.5-3.el6
provider: libgcrypt.i686 1.4.5-5.el6
provider: libgcrypt.i686 1.4.5-5.el6_1.2
provider: libgcrypt.i686 1.4.5-9.el6
provider: libgcrypt.i686 1.4.5-9.el6_2.2
provider: libgcrypt.i686 1.4.5-9.el6_2.2
provider: libgcrypt.i686 1.4.5-3.el6
provider: libgcrypt.i686 1.4.5-9.el6_2.2
dependency: libgcrypt = 1.2.2
provider: libgcrypt.i686 1.5.0-8.fc18
provider: libgcrypt.i686 1.4.5-9.el6_2.2
provider: libgcrypt.i686 1.5.0-6.fc18
provider: libgcrypt.i686 1.4.0-15.el6
provider: libgcrypt.i686 1.4.5-9.el6
##...snip...

the problem is ... in the provider lines, yum is not showing repo
name, after showing lib/pkg name  version, on each line !

If repo, pkg/lib, version, arch, etc are shown  known ... Then it
would have been bit easier to build a technique what to keep and
what to update.


-- Bright Star.



Received from Johnny Hughes,, on 2013-01-28 8:17 PM:
 On 01/28/2013 01:26 PM, Nikolaos Milas wrote:
 On 27/1/2013 5:11 μμ, Johnny Hughes wrote:
 
 Taking gtk2 as in our example here, if you wanted a new gtk2
 in CentOS-5.9, then you would have to rebuild the following
 packages:
 A quick (?) question:
 
 What is the best way to view dependencies?
 
 1. We can use yum deplist xxx.rpm to view dependencies of a
 particular installed package, but we would like to limit output
 to only *already installed* packages and not view all suitable
 ones. Also, we would like to view dependencies as a full rpm
 name and not as they are output by default (e.g. not
 glibc.x86_64 2.12-1.80.el6_3.6 but 
 glibc-2.12-1.80.el6_3.6.x86_64)
 
 2. Is there a way to find out the opposite, i.e. which
 *installed* packages are dependent on a particular installed
 package? In your example above (about gtk2), how could we have
 produced the list of dependent-on-it packages which you have
 kindly provided?
 
 With respect to build and SRPMS, I do this:
 
 I go to a place where all the distro's SRPMS (we have that place
 on vault), then I do this command:
 
 rpm -qp --requires name.src.rpm
 
 That will tell me everything that is required to build that
 individual SRPM.
 
 However, you would also need to take every requirement and do the
 same thing to it ... in other words, find the requirements of
 each requirement.
 
 There is no easy way to do this (that I know of) ... if I want to
 know, I do the work.
 
 Also, if you want to develop an initial list of SRPMS that are
 impacted when changing something, you would do this inside the
 LATEST SRPMS (again, using gtk2 as the example):
 
 for srpm in $(ls *.src.rpm); do requires_gtk2=$(rpm -qp
 --requires $srpm | grep gtk2-devel); if [ $requires_gtk2 !=
  ]; then echo $srpm; fi; done
 
 (the above is one line if wrapped)
 
 Once you develop the list of SRPMS, you would need to develop
 another list of requirements for each requirement.
 
 There is a yum-utility called yum-builddep that will install all
 the dependencies to build a package for you ... you can do that
 into a minimal installed VM as well.
 
 
 
 ___
 CentOS mailing
 list CentOS@centos.org 
 http://lists.centos.org/mailman/listinfo/centos
 



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


  1   2   3   >