Thanks Johnny for taking the time, it looks like the issue is much more convoluted than I initially assumed.
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
----- Original Message -----
> From: "Johnny Hughes" <johnny(a)centos.org>
> To: centos-devel(a)centos.org
> Sent: Wednesday, 1 October, 2014 10:00:04
> Subject: Re: [CentOS-devel] yum-plugin-security and shellshock
> On 09/30/2014 11:10 AM, Kevin Stange wrote:
>> On 09/30/2014 10:03 AM, Nux! wrote:
>>> What needs to happen for that?
>>
>> We had a short discussion about it here:
>>
>> http://lists.centos.org/pipermail/centos-devel/2014-September/011893.html
>>
>> The issue is that something during the issuance of new updates has to
>> build a persistent list of CExAs and then regenerate the updateinfo.xml
>> while building the repo update.
>>
>> Right now CentOS pushes the update notices directly to the mailing list
>> and doesn't store that data anywhere to generate the XML file. The only
>> way I know to build historical updateinfo.xml would be to scrape the
>> mailing list for all previous data. Needed are release ID, package
>> (name, version, release, arch), SHA sum, release type (bug, enhancement,
>> new package, security), severity (if security), reference URL, summary,
>> additional description (if any).
>>
>> SL publishes updateinfo.xml so if someone has insight into how they
>> manage it, perhaps we could make use of the process to shoehorn into
>> CentOS. See:
>>
>> http://ftp.scientificlinux.org/linux/fermi/scientific/6x/x86_64/updates/sec…
>>
>
> I think that is only one issue.
>
> The other issue (as I understand it), is that we would need an all
> encompassing metadata across all versions to make this work as well.
>
> Meaning that (lets take CentOS-6 as an example) ... we would need a tree
> of all RPMs (6.0, 6.1, 6.2, 6.3, 6.4, 6.5 .. plus all the updates
> directories) on all the mirrors to make that work.
>
> I suppose we could do it if all the metadata was in one place (at a
> level up) and the directories could be separate.
>
> But either way, it would add significantly to the size required to
> mirror CentOS and require a redesign of how we do trees completely (we
> currently only push the latest tree for each live major version).
>
> (For example, we would likely have to separate ISOs out of main trees as
> there is no way we could mirror all the ISO's as well as all the binary
> RPMs for 11 CentOS 5 versions, 5 CentOS 6 versions, etc. to every
> mirror, that is several TB of info if we include ISOs)
>
> =====================================================================
>
> So, all of this would be required and the end result would be that you
> would then be able to install security updates only.
>
> The only problem with that is ... in a staged build system, security
> updates only is not supported. It is not really supported in RHEL
> either. Why do I say that? Look at any RHEL RHSA update .. I'll take
> one of the shellshock updates:
>
> https://rhn.redhat.com/errata/RHSA-2014-1306.html
>
> If you look at the Solution section you will see this quote:
>
> "Before applying this update, make sure all previously released errata
> relevant to your system have been applied."
>
> It does not say all "previously release Security Errata" has been
> applied ... it does not say all "BugFix and Security Errata" has been
> applied .. it says "all previously released Errata" has been applied.
>
> Why is that?
>
> Well, because things are built on top of the last update (the build root
> used is 'staged'). The build root grows as you add packages to the
> distribution. Package A is built, it goes into the build root and then
> Package B gets built the next day against that Package A. If you run
> that Package B against an older version of Package A than the one it was
> built against, then it may not work the same way as it was intended to work.
>
> So, the only 'supported' and 'tested' configuration is all the latest
> packages installed.
>
> That is why Red Hat specifically has EUS/AUS repositories where they
> SPECIFICALLY built the same bash (in our example) against the extended
> 6.4 EUS tree. They have a different shell shock patched build of bash
> there:
>
> https://rhn.redhat.com/errata/RHSA-2014-1311.html
>
> The bash for RHEL-6.4 AUS is (after being built against the 6.4 AUS
> tree) different that the one for RHEL-6.5 .. why is that? Because it is
> the same source code, but it is built against a different subset of
> packages. (The AUS is basically all of 6.4 as it was when 6.5 was
> released, and all the new 6.5 security updates, built in order and in a
> staged manner against that 6.4 tree ... so it is '6.4 plus 6.5 security
> updates'.) Do you think Red Hat would maintain a separate AUS/EUS 6.4
> tree and build all the new security updates from 6.5 again against that
> 6.4 EUS/AUS tree if the users could just not update to 6.5 and just use
> yum-security to use the 6.5 updates? Of course not, they would just use
> the 6.5 security packages for 6.4. They don't use the 6.5 security
> updates directly against 6.4, because it might not work. Instead, they
> maintain a separate 6.4 tree.
>
> If you take the 6.5 bash update and install it in 6.4, will it work?
> Likely. Will it absolutely fix the security issue? Maybe not .. it is
> certainly not 'supported' by Red Hat that way.
>
> ======================================================================
>
> So, only installing Security updates and not all updates is not a very
> good idea (certainly on on different minor versions), because you are
> not operating in a tested manner and the update could very well not even
> mitigate the security issue UNLESS you install all updates (security and
> otherwise) that happen before it anyway.
>
> Therefore why would we want to take great pains to totally redesign our
> mirror infrastructure (the size increase rendering some number of our
> current donated mirrors as too small to now be used). Take great pains
> to maintain a separate database of Security info to generate the xml
> file. Then that will make the end release that it is now very easy for
> users to think they are safe (because they do all security updates after
> all) ... but they are not safe because they are running 6.5 security
> updates against 6.4? Or help them run only critical security updates
> and the combination introduces new issues unique to that combination?
>
> They only way to have another secure combination is to build and test
> the security updates in that combination. If you want 6.3 with only the
> 6.4 and 6.5 Moderate Security updates (or above) added to that, you
> would need to build the 6.4 and 6.5 security updates (in order) against
> that 6.3 tree ... staging it as you go so that the next update gets
> built against the update before it. You would also then need to TEST
> that this combination actually fixes the security issues. Then you
> could be reasonably sure that the solution was safe.
>
> But if you just installed the CentOS 6.4 and 6.5 moderate updates (or
> higher) on CentOS 6.3 (the same packages you rebuilt in the preceding
> paragraph) .. even if they installed, it would be significantly
> different than the solution where you built them yourself.
>
>
>
>
> _______________________________________________
> CentOS-devel mailing list
> CentOS-devel(a)centos.org
> http://lists.centos.org/mailman/listinfo/centos-devel
On Tue, Jul 01, 2008 at 03:04:41PM +0930, Tom Lanyon wrote:
> On 01/07/2008, at 2:19 PM, Amos Shapira wrote:
>
>> 2008/6/30 Bazy <bazy(a)goofy.celuloza.ro>:
>>> Hello,
>>>
>>> Is anyone using Spacewalk (http://www.redhat.com/spacewalk/) on
>>> CentOS 5 or 4? What kind of hardware are you useing it on?
>>
>> Do I read it right that it requires Oracle 9??
>> (http://tinyurl.com/6rff8l) or am I missing something?
>
> 9 or 10, I believe.
10.2.0.x seems to be what you need.
The yum install spacewalk output freaks me out ;)
Btw, might as well pop a question here, should I remove specspo to resolve
this conflict?
--> Processing Conflict: rhns-xp conflicts specspo
--> Processing Conflict: rhns-app conflicts specspo
[root@mikaelf-centos1 rpm]# yum install spacewalk
Loading "fastestmirror" plugin
Loading "priorities" plugin
Loading mirror speeds from cached hostfile
* itsforge: repo.its.uu.se
* spacewalk: spacewalk.redhat.com
* base: ftp.crc.dk
* updates: ftp.crc.dk
* addons: ftp.crc.dk
* local:
* extras: ftp.crc.dk
66 packages excluded due to repository priority protections
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
--> Running transaction check
---> Package spacewalk.noarch 0:0.1-7 set to be updated
--> Processing Dependency: rhns-applet for package: spacewalk
--> Processing Dependency: taskomatic-sat for package: spacewalk
--> Processing Dependency: rhns-xml-export-libs for package: spacewalk
--> Processing Dependency: rhn-java-sat for package: spacewalk
--> Processing Dependency: rhn-pxt for package: spacewalk
--> Processing Dependency: rhn-base for package: spacewalk
--> Processing Dependency: rhnpush for package: spacewalk
--> Processing Dependency: rhn-html for package: spacewalk
--> Processing Dependency: rhns for package: spacewalk
--> Processing Dependency: rhns-config-files for package: spacewalk
--> Processing Dependency: rhns-xp for package: spacewalk
--> Processing Dependency: rhns-satellite-tools for package: spacewalk
--> Processing Dependency: rhn-dobby for package: spacewalk
--> Processing Dependency: rhns-config-files-tool for package: spacewalk
--> Processing Dependency: rhn-grail for package: spacewalk
--> Processing Dependency: rhn-cypress for package: spacewalk
--> Processing Dependency: rhn-sniglets for package: spacewalk
--> Processing Dependency: rhns-package-push-server for package: spacewalk
--> Processing Dependency: rhns-xmlrpc for package: spacewalk
--> Processing Dependency: rhn-satellite-schema for package: spacewalk
--> Processing Dependency: rhn-moon for package: spacewalk
--> Processing Dependency: rhns-certs-tools for package: spacewalk
--> Processing Dependency: rhns-config-files-common for package: spacewalk
--> Processing Dependency: spacewalk-setup for package: spacewalk
--> Processing Dependency: rhns-server for package: spacewalk
--> Processing Dependency: rhns-app for package: spacewalk
--> Processing Dependency: rhn-satellite-config for package: spacewalk
--> Processing Dependency: rhns-sql for package: spacewalk
--> Running transaction check
---> Package rhn-cypress.noarch 0:0.1-3.el5 set to be updated
---> Package rhns-certs-tools.noarch 0:5.2.0-2.el5 set to be updated
---> Package rhns-sql.noarch 0:0.1-4.el5 set to be updated
--> Processing Dependency: python(:DBAPI:oracle) for package: rhns-sql
---> Package rhns-server.noarch 0:0.1-4.el5 set to be updated
--> Processing Dependency: python-sgmlop for package: rhns-server
--> Processing Dependency: PyXML for package: rhns-server
---> Package rhns-xp.noarch 0:0.1-4.el5 set to be updated
---> Package rhn-satellite-config.noarch 0:5.2.0-1.el5 set to be updated
--> Processing Dependency: perl(Satcon) for package: rhn-satellite-config
--> Processing Dependency: perl(Apache::DBI) for package: rhn-satellite-config
---> Package rhnpush.noarch 0:5.2.0-5 set to be updated
---> Package rhns-config-files.noarch 0:0.1-4.el5 set to be updated
---> Package rhns-xmlrpc.noarch 0:0.1-4.el5 set to be updated
---> Package rhn-base.noarch 0:0.1-3.el5 set to be updated
--> Processing Dependency: perl(XML::LibXML) for package: rhn-base
--> Processing Dependency: perl(DBD::Oracle) for package: rhn-base
--> Processing Dependency: perl-Frontier-RPC for package: rhn-base
--> Processing Dependency: perl(Unix::Syslog) for package: rhn-base
--> Processing Dependency: perl(Schedule::Cron::Events) for package: rhn-base
--> Processing Dependency: perl-DateTime-TimeZone for package: rhn-base
--> Processing Dependency: perl-IPC-ShareLite for package: rhn-base
--> Processing Dependency: perl(Frontier::RPC2) for package: rhn-base
--> Processing Dependency: perl(RPM2) for package: rhn-base
--> Processing Dependency: perl(Date::Parse) for package: rhn-base
--> Processing Dependency: perl-Crypt-SSLeay for package: rhn-base
--> Processing Dependency: perl-Params-Validate for package: rhn-base
--> Processing Dependency: perl-Class-Factory-Util for package: rhn-base
--> Processing Dependency: perl-XML-LibXML-Common for package: rhn-base
--> Processing Dependency: perl(DateTime) for package: rhn-base
--> Processing Dependency: perl-DateManip for package: rhn-base
--> Processing Dependency: perl-Data-Buffer for package: rhn-base
--> Processing Dependency: perl(Frontier::Client) for package: rhn-base
--> Processing Dependency: perl(Text::Diff) for package: rhn-base
--> Processing Dependency: perl-Convert-ASN1 for package: rhn-base
--> Processing Dependency: perl(Mail::RFC822::Address) for package: rhn-base
--> Processing Dependency: perl-Math-FFT for package: rhn-base
--> Processing Dependency: perl-Archive-Tar for package: rhn-base
--> Processing Dependency: perl(Authen::PAM) for package: rhn-base
--> Processing Dependency: perl(XML::LibXML) >= 1.53 for package: rhn-base
--> Processing Dependency: perl-Crypt-DSA for package: rhn-base
--> Processing Dependency: perl-Set-Crontab for package: rhn-base
--> Processing Dependency: perl-Schedule-Cron-Events for package: rhn-base
--> Processing Dependency: perl-Crypt-DES_EDE3 for package: rhn-base
--> Processing Dependency: perl-Convert-ASCII-Armour for package: rhn-base
--> Processing Dependency: perl(Crypt::OpenPGP) for package: rhn-base
--> Processing Dependency: perl-XML-LibXML for package: rhn-base
--> Processing Dependency: perl-Authen-PAM for package: rhn-base
--> Processing Dependency: perl-Devel-Symdump for package: rhn-base
--> Processing Dependency: perl-Unix-Syslog for package: rhn-base
--> Processing Dependency: perl(Archive::Tar) for package: rhn-base
--> Processing Dependency: perl-Proc-Daemon for package: rhn-base
--> Processing Dependency: perl-Crypt-Blowfish for package: rhn-base
--> Processing Dependency: perl-Crypt-Primes for package: rhn-base
--> Processing Dependency: perl-DateTime for package: rhn-base
--> Processing Dependency: perl-Class-Singleton for package: rhn-base
--> Processing Dependency: perl-Digest-MD2 for package: rhn-base
--> Processing Dependency: perl(NOCpulse::Config) for package: rhn-base
--> Processing Dependency: perl-XML-Writer for package: rhn-base
--> Processing Dependency: perl-Text-Diff for package: rhn-base
--> Processing Dependency: perl-Mail-RFC822-Address for package: rhn-base
--> Processing Dependency: perl-DBD-Oracle for package: rhn-base
--> Processing Dependency: perl-Crypt-OpenPGP for package: rhn-base
--> Processing Dependency: perl-Crypt-RSA for package: rhn-base
--> Processing Dependency: perl-Crypt-Rijndael for package: rhn-base
--> Processing Dependency: perl-Crypt-RIPEMD160 for package: rhn-base
--> Processing Dependency: perl-RPM2 for package: rhn-base
--> Processing Dependency: perl-TimeDate for package: rhn-base
--> Processing Dependency: perl(Term::ReadKey) for package: rhn-base
--> Processing Dependency: perl-Crypt-CAST5_PP for package: rhn-base
--> Processing Dependency: perl-Crypt-Random for package: rhn-base
--> Processing Dependency: perl-XML-SAX for package: rhn-base
--> Processing Dependency: perl-Algorithm-Diff for package: rhn-base
--> Processing Dependency: perl-Business-CreditCard for package: rhn-base
--> Processing Dependency: perl-Convert-PEM for package: rhn-base
--> Processing Dependency: perl-XML-LibXML >= 1.53 for package: rhn-base
--> Processing Dependency: perl-Math-Pari for package: rhn-base
--> Processing Dependency: perl-Date-Calc for package: rhn-base
--> Processing Dependency: perl-DateTime-Locale for package: rhn-base
--> Processing Dependency: perl(Params::Validate) for package: rhn-base
--> Processing Dependency: perl-Bit-Vector for package: rhn-base
--> Processing Dependency: perl(Proc::Daemon) for package: rhn-base
--> Processing Dependency: perl-Class-Loader for package: rhn-base
---> Package rhns-xml-export-libs.noarch 0:0.1-4.el5 set to be updated
---> Package rhns-applet.noarch 0:0.1-4.el5 set to be updated
---> Package rhn-java-sat.noarch 0:0.1-3.el5 set to be updated
--> Processing Dependency: hibernate3 >= 3.2.4 for package: rhn-java-sat
--> Processing Dependency: rhn-oracle-jdbc-tomcat5 for package: rhn-java-sat
--> Processing Dependency: bcel for package: rhn-java-sat
--> Processing Dependency: jpam for package: rhn-java-sat
--> Processing Dependency: sitemesh for package: rhn-java-sat
--> Processing Dependency: jfreechart for package: rhn-java-sat
--> Processing Dependency: bouncycastle-jdk1.5 for package: rhn-java-sat
--> Processing Dependency: jakarta-commons-lang for package: rhn-java-sat
--> Processing Dependency: xalan-j2 >= 2.6.0 for package: rhn-java-sat
--> Processing Dependency: java >= 1.5.0 for package: rhn-java-sat
--> Processing Dependency: rhn-java-config-sat for package: rhn-java-sat
--> Processing Dependency: log4j for package: rhn-java-sat
--> Processing Dependency: jpackage-utils >= 1.5 for package: rhn-java-sat
--> Processing Dependency: java-devel >= 1.5.0 for package: rhn-java-sat
--> Processing Dependency: jakarta-taglibs-standard for package: rhn-java-sat
--> Processing Dependency: jcommon for package: rhn-java-sat
--> Processing Dependency: bouncycastle for package: rhn-java-sat
--> Processing Dependency: quartz for package: rhn-java-sat
--> Processing Dependency: jakarta-commons-logging for package: rhn-java-sat
--> Processing Dependency: redstone-xmlrpc for package: rhn-java-sat
--> Processing Dependency: jasper5 for package: rhn-java-sat
--> Processing Dependency: rhn-oracle-jdbc >= 1.0-10 for package: rhn-java-sat
--> Processing Dependency: oscache for package: rhn-java-sat
--> Processing Dependency: rhn-java-lib-sat for package: rhn-java-sat
--> Processing Dependency: tomcat5 for package: rhn-java-sat
--> Processing Dependency: concurrent for package: rhn-java-sat
--> Processing Dependency: struts >= 1.2.9 for package: rhn-java-sat
--> Processing Dependency: jakarta-commons-codec for package: rhn-java-sat
--> Processing Dependency: servletapi5 for package: rhn-java-sat
--> Processing Dependency: c3p0 for package: rhn-java-sat
--> Processing Dependency: jakarta-commons-configuration for package: rhn-java-sat
--> Processing Dependency: xerces-j2 for package: rhn-java-sat
---> Package rhns-satellite-tools.noarch 0:0.1-4.el5 set to be updated
--> Processing Dependency: rhn-satellite-admin >= 3.6.0-198 for package: rhns-satellite-tools
--> Processing Dependency: python-gzipstream for package: rhns-satellite-tools
---> Package rhn-moon.noarch 0:0.1-3.el5 set to be updated
--> Processing Dependency: perl(GD) for package: rhn-moon
---> Package rhns-config-files-tool.noarch 0:0.1-4.el5 set to be updated
---> Package rhns-package-push-server.noarch 0:0.1-4.el5 set to be updated
---> Package rhn-grail.noarch 0:0.1-3.el5 set to be updated
---> Package rhn-dobby.noarch 0:0.1-3.el5 set to be updated
--> Processing Dependency: perl(Filesys::Df) for package: rhn-dobby
---> Package rhn-satellite-schema.noarch 0:5.1.0-27 set to be updated
---> Package rhns.noarch 0:0.1-4.el5 set to be updated
--> Processing Dependency: rhnlib >= 1.8 for package: rhns
---> Package rhns-app.noarch 0:0.1-4.el5 set to be updated
---> Package rhn-html.noarch 0:0.1-3.el5 set to be updated
---> Package taskomatic-sat.noarch 0:0.1-3.el5 set to be updated
--> Processing Dependency: jakarta-commons-cli for package: taskomatic-sat
--> Processing Dependency: java >= 1.5.0 for package: taskomatic-sat
--> Processing Dependency: java-devel >= 1.5.0 for package: taskomatic-sat
--> Processing Dependency: cglib for package: taskomatic-sat
--> Processing Dependency: tanukiwrapper for package: taskomatic-sat
---> Package spacewalk-setup.noarch 0:0.01-3 set to be updated
---> Package rhn-sniglets.noarch 0:0.1-3.el5 set to be updated
--> Processing Dependency: perl-XML-Parser for package: rhn-sniglets
--> Processing Dependency: perl-Cache-Cache for package: rhn-sniglets
--> Processing Dependency: perl(XML::RSS) for package: rhn-sniglets
--> Processing Dependency: perl-XML-RSS for package: rhn-sniglets
--> Processing Dependency: perl(MIME::Lite) for package: rhn-sniglets
--> Processing Dependency: perl-MIME-Lite for package: rhn-sniglets
--> Processing Dependency: perl(Cache::FileCache) for package: rhn-sniglets
---> Package rhns-config-files-common.noarch 0:0.1-4.el5 set to be updated
---> Package rhn-pxt.noarch 0:0.1-3.el5 set to be updated
--> Processing Dependency: perl(Apache2::Cookie) for package: rhn-pxt
--> Processing Dependency: perl(Apache2::Request) for package: rhn-pxt
--> Processing Dependency: perl-libapreq2 for package: rhn-pxt
--> Processing Dependency: perl-SOAP-Lite for package: rhn-pxt
--> Processing Dependency: perl(SOAP::Lite) for package: rhn-pxt
--> Running transaction check
---> Package perl-Crypt-Rijndael.i386 0:1.05-2.el5 set to be updated
---> Package tanukiwrapper.i386 0:3.2.1-2jpp.ep1.1.el5 set to be updated
--> Processing Dependency: xml-commons-apis for package: tanukiwrapper
---> Package perl-Text-Diff.noarch 0:0.35-11.el5 set to be updated
---> Package perl-DateTime-TimeZone.noarch 0:0.59-5.el5 set to be updated
---> Package perl-XML-SAX.noarch 0:0.14-5 set to be updated
--> Processing Dependency: perl(XML::NamespaceSupport) for package: perl-XML-SAX
---> Package perl-Algorithm-Diff.noarch 0:1.1901-11.el5 set to be updated
---> Package cx_Oracle.i386 0:4.2.1-4.el5 set to be updated
--> Processing Dependency: libclntsh.so.10.1 for package: cx_Oracle
---> Package perl-Crypt-SSLeay.i386 0:0.51-11.el5 set to be updated
---> Package perl-Convert-ASN1.noarch 0:0.20-1.1 set to be updated
---> Package np-config.noarch 0:2.110.3-6.el5 set to be updated
--> Processing Dependency: NPusers for package: np-config
--> Processing Dependency: perl(IO::AtomicFile) for package: np-config
---> Package log4j.i386 0:1.2.13-3jpp.2 set to be updated
--> Processing Dependency: java-gcj-compat for package: log4j
---> Package bcel.i386 0:5.1-8jpp.1 set to be updated
--> Processing Dependency: regexp for package: bcel
---> Package bouncycastle.noarch 0:1.37-1jpp.1.el5 set to be updated
---> Package hibernate3.noarch 0:3.2.4-1.SP1_CP01.0jpp.ep1.1.el5.1 set to be updated
--> Processing Dependency: asm for package: hibernate3
--> Processing Dependency: antlr >= 2.7.6 for package: hibernate3
--> Processing Dependency: dom4j >= 1.6.1 for package: hibernate3
--> Processing Dependency: jakarta-commons-collections >= 2.1.1 for package: hibernate3
--> Processing Dependency: jta for package: hibernate3
---> Package perl-Math-FFT.i386 0:0.26-12.el5 set to be updated
---> Package jakarta-commons-configuration.noarch 0:1.2-1jpp_1rh set to be updated
--> Processing Dependency: servletapi4 for package: jakarta-commons-configuration
--> Processing Dependency: jakarta-commons-digester for package: jakarta-commons-configuration
--> Processing Dependency: jakarta-commons-dbcp for package: jakarta-commons-configuration
--> Processing Dependency: jakarta-commons-beanutils >= 1.7.0 for package: jakarta-commons-configuration
--> Processing Dependency: jakarta-commons-pool for package: jakarta-commons-configuration
---> Package perl-Set-Crontab.noarch 0:1.00-12.el5 set to be updated
---> Package perl-Crypt-Primes.noarch 0:0.49-11.el5 set to be updated
---> Package perl-Authen-PAM.i386 0:0.14-14.el5 set to be updated
---> Package tomcat5-servlet-2.4-api.i386 0:5.5.23-0jpp.7.el5 set to be updated
---> Package perl-Math-Pari.i386 0:2.010603-7.el5 set to be updated
---> Package perl-Class-Loader.noarch 0:2.02-11.el5 set to be updated
---> Package perl-XML-RSS.noarch 0:1.05-6.el5 set to be updated
---> Package perl-Crypt-RIPEMD160.i386 0:0.04-13.el5 set to be updated
---> Package perl-libapreq2.i386 0:2.09-6.el5 set to be updated
--> Processing Dependency: libapreq2.so.3 for package: perl-libapreq2
---> Package perl-SOAP-Lite.noarch 0:0.60a-11.el5 set to be updated
---> Package oscache.noarch 0:2.2-2jpp.ep1.1.el5 set to be updated
---> Package perl-GD2.i386 0:2.17-10.el5 set to be updated
---> Package perl-DateTime-Locale.noarch 0:0.09-6.el5 set to be updated
---> Package perl-RPM2.i386 0:0.68-34.el5 set to be updated
---> Package perl-Satcon.noarch 0:1.3-9.el5 set to be updated
--> Processing Dependency: perl(RPM::Specfile) for package: perl-Satcon
---> Package jpam.i386 0:0.4-16.el5 set to be updated
---> Package rhn-java-sat.noarch 0:0.1-3.el5 set to be updated
--> Processing Dependency: java >= 1.5.0 for package: rhn-java-sat
--> Processing Dependency: java-devel >= 1.5.0 for package: rhn-java-sat
---> Package perl-Crypt-OpenPGP.noarch 0:1.03-14.el5 set to be updated
---> Package jfreechart.noarch 0:0.9.21-2jpp.ep1.1.el5.2 set to be updated
---> Package perl-XML-LibXML-Common.i386 0:0.13-8.2.2 set to be updated
---> Package PyXML.i386 0:0.8.4-4 set to be updated
---> Package cglib.noarch 0:2.1.3-2jpp.ep1.3.el5.1 set to be updated
---> Package perl-Data-Buffer.noarch 0:0.04-8.el5 set to be updated
---> Package perl-Convert-PEM.noarch 0:0.06-7.el5 set to be updated
---> Package perl-MIME-Lite.noarch 0:3.01-6.el5 set to be updated
---> Package jakarta-commons-logging.i386 0:1.0.4-6jpp.1 set to be updated
---> Package rhn-satellite-admin.noarch 0:5.2.0-3.el5 set to be updated
---> Package xalan-j2.i386 0:2.7.0-6jpp.1 set to be updated
---> Package perl-Filesys-Statvfs-Df.i386 0:0.72-9.el5 set to be updated
---> Package perl-XML-LibXML.i386 0:1.58-5 set to be updated
---> Package rhnlib.noarch 0:2.2.5-1 set to be updated
--> Processing Dependency: pyOpenSSL for package: rhnlib
---> Package sitemesh.noarch 0:2.1-1jpp_1rh set to be updated
--> Processing Dependency: jsp >= 1.2 for package: sitemesh
--> Processing Dependency: velocity-tools for package: sitemesh
--> Processing Dependency: freemarker for package: sitemesh
--> Processing Dependency: velocity for package: sitemesh
---> Package redstone-xmlrpc.noarch 0:1.1_20071120-6.el5 set to be updated
---> Package perl-Digest-MD2.i386 0:2.03-10.el5 set to be updated
---> Package perl-Crypt-Blowfish.i386 0:2.09-4.8.el5 set to be updated
---> Package jakarta-commons-cli.noarch 0:1.0-6jpp.ep1.1.el5.1 set to be updated
---> Package perl-DBD-Oracle.i386 0:1.19-8.el5 set to be updated
--> Processing Dependency: oracle-instantclient-basic for package: perl-DBD-Oracle
---> Package c3p0.noarch 0:0.9.0-2jpp.ep1.1.el5 set to be updated
---> Package perl-Date-Calc.i386 0:5.4-1.2.2.1 set to be updated
--> Processing Dependency: perl(Carp::Clan) for package: perl-Date-Calc
---> Package perl-Class-Factory-Util.noarch 0:1.6-6.el5 set to be updated
---> Package jakarta-commons-lang.i386 0:2.1-5jpp.1 set to be updated
---> Package python-sgmlop.i386 0:1.1.1-20040207.15.el5 set to be updated
---> Package perl-IPC-ShareLite.i386 0:0.13-1.el5 set to be updated
---> Package perl-TimeDate.noarch 1:1.16-5.el5 set to be updated
---> Package perl-Devel-Symdump.noarch 0:2.03-21.el5 set to be updated
---> Package perl-XML-Writer.noarch 0:0.4-12.el5 set to be updated
---> Package perl-Crypt-DSA.noarch 0:0.12-10.el5 set to be updated
---> Package jakarta-commons-codec.i386 0:1.3-7jpp.2 set to be updated
---> Package bouncycastle-jdk1.5.noarch 0:1.37-1jpp.1.el5 set to be updated
--> Processing Dependency: jaf for package: bouncycastle-jdk1.5
--> Processing Dependency: java >= 1.5.0 for package: bouncycastle-jdk1.5
--> Processing Dependency: javamail for package: bouncycastle-jdk1.5
---> Package perl-Apache-DBI.noarch 0:0.94-12.el5 set to be updated
---> Package perl-Crypt-CAST5_PP.noarch 0:1.02-6.el5 set to be updated
---> Package quartz.noarch 0:1.5.2-1jpp.ep1.5.el5 set to be updated
---> Package python-gzipstream.noarch 0:1.4.0-15.el5 set to be updated
---> Package taskomatic-sat.noarch 0:0.1-3.el5 set to be updated
--> Processing Dependency: java >= 1.5.0 for package: taskomatic-sat
--> Processing Dependency: java-devel >= 1.5.0 for package: taskomatic-sat
---> Package perl-Business-CreditCard.noarch 0:0.28-6.el5 set to be updated
---> Package perl-XML-Parser.i386 0:2.34-6.1.2.2.1 set to be updated
---> Package concurrent.noarch 0:1.3.4-6jpp.ep1.2.el5.1 set to be updated
---> Package tomcat5.i386 0:5.5.23-0jpp.7.el5 set to be updated
--> Processing Dependency: jakarta-commons-daemon >= 1.0.1 for package: tomcat5
--> Processing Dependency: tomcat5-common-lib = 5.5.23-0jpp.7.el5 for package: tomcat5
--> Processing Dependency: tomcat5-server-lib = 5.5.23-0jpp.7.el5 for package: tomcat5
--> Processing Dependency: tomcat5-server-lib = 5.5.23-0jpp.7.el5 for package: tomcat5
--> Processing Dependency: tomcat5-common-lib = 5.5.23-0jpp.7.el5 for package: tomcat5
--> Processing Dependency: jakarta-commons-launcher >= 0.9 for package: tomcat5
--> Processing Dependency: jndi-ldap for package: tomcat5
---> Package perl-Cache-Cache.noarch 0:1.03-7.el5 set to be updated
---> Package perl-Proc-Daemon.noarch 0:0.03-6.el5 set to be updated
---> Package rhn-java-config-sat.noarch 0:0.1-3.el5 set to be updated
---> Package tomcat5-jasper.i386 0:5.5.23-0jpp.7.el5 set to be updated
---> Package perl-Frontier-RPC.noarch 0:0.07-7.el5 set to be updated
---> Package perl-Convert-ASCII-Armour.noarch 0:1.4-11.el5 set to be updated
---> Package perl-TermReadKey.i386 0:2.30-11.el5 set to be updated
---> Package perl-Archive-Tar.noarch 0:1.30-1.fc6 set to be updated
--> Processing Dependency: perl(IO::Zlib) for package: perl-Archive-Tar
---> Package perl-DateTime.i386 0:0.27-10.el5 set to be updated
---> Package perl-Schedule-Cron-Events.noarch 0:1.8-11.el5 set to be updated
---> Package struts.i386 0:1.2.9-4jpp.5 set to be updated
--> Processing Dependency: jakarta-commons-validator for package: struts
--> Processing Dependency: jakarta-commons-fileupload for package: struts
--> Processing Dependency: oro for package: struts
---> Package perl-Unix-Syslog.i386 0:0.100-10.el5 set to be updated
---> Package rhn-java-lib-sat.noarch 0:0.1-3.el5 set to be updated
---> Package jcommon.noarch 0:0.9.7-1jpp.ep1.1.el5 set to be updated
---> Package xerces-j2.i386 0:2.7.1-7jpp.2 set to be updated
--> Processing Dependency: xml-commons-resolver >= 1.1 for package: xerces-j2
---> Package perl-Crypt-RSA.noarch 0:1.50-7.el5 set to be updated
--> Processing Dependency: perl(Tie::EncryptedHash) for package: perl-Crypt-RSA
--> Processing Dependency: perl(Crypt::CBC) for package: perl-Crypt-RSA
--> Processing Dependency: perl(Sort::Versions) for package: perl-Crypt-RSA
---> Package perl-Crypt-Random.noarch 0:1.11-11.el5 set to be updated
---> Package rhn-oracle-jdbc-tomcat5.noarch 0:1.0-14.fc9 set to be updated
---> Package perl-Mail-RFC822-Address.noarch 0:0.3-10.el5 set to be updated
---> Package jakarta-taglibs-standard.i386 0:1.1.1-7jpp.1 set to be updated
---> Package perl-Class-Singleton.noarch 0:1.03-6.el5 set to be updated
---> Package perl-Params-Validate.i386 0:0.74-10.el5 set to be updated
---> Package jpackage-utils.noarch 0:1.7.3-1jpp.2.el5 set to be updated
---> Package rhn-oracle-jdbc.noarch 0:1.0-14.fc9 set to be updated
---> Package perl-DateManip.noarch 0:5.44-1.2.1 set to be updated
---> Package perl-Bit-Vector.i386 0:6.4-2.2.2.1 set to be updated
---> Package perl-Crypt-DES_EDE3.noarch 0:0.01-6.el5 set to be updated
--> Running transaction check
---> Package jakarta-commons-launcher.i386 0:0.9-6jpp.1 set to be updated
---> Package oracle-instantclient-basic.i386 0:10.2.0.4-1 set to be updated
---> Package tomcat5-server-lib.i386 0:5.5.23-0jpp.7.el5 set to be updated
--> Processing Dependency: mx4j >= 3.0.1 for package: tomcat5-server-lib
--> Processing Dependency: jakarta-commons-el >= 1.0 for package: tomcat5-server-lib
--> Processing Dependency: jakarta-commons-modeler >= 1.1-8jpp.1.0.1 for package: tomcat5-server-lib
--> Processing Dependency: mx4j >= 3.0.1 for package: tomcat5-server-lib
--> Processing Dependency: jakarta-commons-modeler >= 1.1-8jpp.1.0.1 for package: tomcat5-server-lib
--> Processing Dependency: jakarta-commons-el >= 1.0 for package: tomcat5-server-lib
---> Package tomcat5-jsp-2.0-api.i386 0:5.5.23-0jpp.7.el5 set to be updated
---> Package perl-IO-Zlib.noarch 0:1.04-4.2.1 set to be updated
---> Package perl-RPM-Specfile.noarch 0:1.17-6.el5 set to be updated
---> Package tomcat5-common-lib.i386 0:5.5.23-0jpp.7.el5 set to be updated
--> Processing Dependency: ant >= 1.6 for package: tomcat5-common-lib
--> Processing Dependency: eclipse-ecj >= 3.1.1 for package: tomcat5-common-lib
--> Processing Dependency: eclipse-ecj >= 3.1.1 for package: tomcat5-common-lib
--> Processing Dependency: ant >= 1.6 for package: tomcat5-common-lib
---> Package velocity-tools.noarch 0:1.2-1jpp_1rh set to be updated
--> Processing Dependency: jaxen >= 1.1 for package: velocity-tools
--> Processing Dependency: velocity-dvsl for package: velocity-tools
---> Package xml-commons-apis.i386 0:1.3.02-0.b2.7jpp.10 set to be updated
--> Processing Dependency: xml-commons = 1.3.02-0.b2.7jpp.10 for package: xml-commons-apis
---> Package jakarta-commons-validator.i386 0:1.1.4-5jpp.1 set to be updated
---> Package asm.noarch 0:1.5.3-1jpp.ep1.1.el5.2 set to be updated
---> Package classpathx-jaf.i386 0:1.0-9jpp.1 set to be updated
---> Package pyOpenSSL.i386 0:0.6-1.p24.7.2.2 set to be updated
---> Package jakarta-commons-beanutils.i386 0:1.7.0-5jpp.1 set to be updated
---> Package NPusers.noarch 0:1.17.11-6.el5 set to be updated
---> Package dom4j.noarch 0:1.6.1-2jpp.ep1.5.el5.2 set to be updated
--> Processing Dependency: xpp3 for package: dom4j
--> Processing Dependency: bea-stax-api for package: dom4j
--> Processing Dependency: xpp2 for package: dom4j
--> Processing Dependency: bea-stax for package: dom4j
--> Processing Dependency: ws-jaxme for package: dom4j
--> Processing Dependency: relaxngDatatype for package: dom4j
--> Processing Dependency: msv-xsdlib for package: dom4j
--> Processing Dependency: msv-msv for package: dom4j
---> Package xml-commons-resolver.i386 0:1.1-1jpp.12 set to be updated
---> Package rhn-java-sat.noarch 0:0.1-3.el5 set to be updated
--> Processing Dependency: java >= 1.5.0 for package: rhn-java-sat
--> Processing Dependency: java-devel >= 1.5.0 for package: rhn-java-sat
---> Package velocity.i386 0:1.4-6jpp.1 set to be updated
--> Processing Dependency: werken.xpath for package: velocity
--> Processing Dependency: avalon-logkit for package: velocity
--> Processing Dependency: jdom >= 1.0-1 for package: velocity
---> Package perl-IO-stringy.noarch 0:2.109-11.el5 set to be updated
---> Package jakarta-commons-daemon.i386 1:1.0.1-6jpp.1 set to be updated
---> Package jakarta-oro.i386 0:2.0.8-3jpp.1 set to be updated
---> Package perl-Sort-Versions.noarch 0:1.4-11.el5 set to be updated
---> Package perl-Carp-Clan.noarch 0:5.3-1.2.1 set to be updated
---> Package servletapi4.noarch 0:4.0.4-3jpp_5rh set to be updated
---> Package libapreq2.i386 0:2.09-6.el5 set to be updated
---> Package geronimo-specs-compat.i386 0:1.0-0.M2.2jpp.12.el5.centos set to be updated
--> Processing Dependency: geronimo-specs = 1.0-0.M2.2jpp.12.el5.centos for package: geronimo-specs-compat
---> Package jakarta-commons-pool.i386 0:1.3-5jpp.1 set to be updated
---> Package perl-Crypt-CBC.noarch 0:2.12-6.el5 set to be updated
---> Package jakarta-commons-digester.i386 0:1.7-5jpp.1 set to be updated
---> Package bouncycastle-jdk1.5.noarch 0:1.37-1jpp.1.el5 set to be updated
--> Processing Dependency: java >= 1.5.0 for package: bouncycastle-jdk1.5
---> Package taskomatic-sat.noarch 0:0.1-3.el5 set to be updated
--> Processing Dependency: java >= 1.5.0 for package: taskomatic-sat
--> Processing Dependency: java-devel >= 1.5.0 for package: taskomatic-sat
---> Package jakarta-commons-fileupload.i386 1:1.0-6jpp.1 set to be updated
---> Package perl-XML-NamespaceSupport.noarch 0:1.09-1.2.1 set to be updated
---> Package jakarta-commons-collections.i386 0:3.2-2jpp.3 set to be updated
---> Package ldapjdk.i386 0:4.18-2jpp.3.el5 set to be updated
---> Package regexp.i386 0:1.4-2jpp.2 set to be updated
---> Package antlr.i386 0:2.7.6-4jpp.2 set to be updated
---> Package jakarta-commons-dbcp.i386 0:1.2.1-7jpp.1 set to be updated
---> Package oracle-lib-compat.i386 0:10.2-3.fc9 set to be updated
---> Package freemarker.noarch 0:2.3.6-2jpp_1rh set to be updated
--> Processing Dependency: avalon-framework for package: freemarker
--> Processing Dependency: jython for package: freemarker
---> Package perl-Tie-EncryptedHash.noarch 0:1.21-4.4.el5 set to be updated
---> Package java-1.4.2-gcj-compat.i386 0:1.4.2.0-40jpp.115 set to be updated
--> Processing Dependency: gjdoc for package: java-1.4.2-gcj-compat
---> Package classpathx-mail.i386 0:1.1.1-4jpp.2 set to be updated
--> Running transaction check
---> Package mx4j.i386 1:3.0.1-6jpp.4 set to be updated
--> Processing Dependency: axis >= 1.1 for package: mx4j
---> Package gjdoc.i386 0:0.7.7-12.el5 set to be updated
---> Package jakarta-commons-el.i386 0:1.0-7jpp.1 set to be updated
---> Package jython.noarch 0:2.2-0.a0.2jpp_1rh set to be updated
---> Package ant.i386 0:1.6.5-2jpp.2 set to be updated
--> Processing Dependency: java-devel for package: ant
---> Package jakarta-commons-modeler.i386 0:1.1-8jpp.3.el5 set to be updated
---> Package geronimo-specs.i386 0:1.0-0.M2.2jpp.12.el5.centos set to be updated
---> Package relaxngDatatype.noarch 0:1.0-2jpp.ep1.2.el5.2 set to be updated
---> Package rhn-java-sat.noarch 0:0.1-3.el5 set to be updated
--> Processing Dependency: java >= 1.5.0 for package: rhn-java-sat
--> Processing Dependency: java-devel >= 1.5.0 for package: rhn-java-sat
---> Package xpp2.noarch 0:2.1.10-4jpp.ep1.2.el5.1 set to be updated
---> Package avalon-logkit.i386 0:1.2-4jpp.3 set to be updated
---> Package eclipse-ecj.i386 1:3.2.1-19.el5.centos set to be updated
---> Package xpp3.noarch 0:1.1.3.4.O-2jpp.ep1.1.el5.1 set to be updated
---> Package xml-commons.i386 0:1.3.02-0.b2.7jpp.10 set to be updated
---> Package werken-xpath.i386 0:0.9.4-0.beta.12jpp.1 set to be updated
---> Package velocity-dvsl.noarch 0:0.45-5jpp_1rh set to be updated
---> Package ws-jaxme.noarch 0:0.5.1-2jpp.ep1.1.el5.1 set to be updated
---> Package bouncycastle-jdk1.5.noarch 0:1.37-1jpp.1.el5 set to be updated
--> Processing Dependency: java >= 1.5.0 for package: bouncycastle-jdk1.5
---> Package msv.noarch 0:1.2-0.20050722.5jpp.ep1.1.el5.2 set to be updated
--> Processing Dependency: isorelax for package: msv
---> Package taskomatic-sat.noarch 0:0.1-3.el5 set to be updated
--> Processing Dependency: java >= 1.5.0 for package: taskomatic-sat
--> Processing Dependency: java-devel >= 1.5.0 for package: taskomatic-sat
---> Package bea-stax.noarch 0:1.2.0-0.rc1.2jpp.ep1.1.el5 set to be updated
---> Package jdom.i386 0:1.0-4jpp.1 set to be updated
---> Package jaxen.noarch 0:1.1-1jpp.ep1.4.el5.2 set to be updated
--> Processing Dependency: xom for package: jaxen
---> Package avalon-framework.i386 0:4.1.4-2jpp.13 set to be updated
---> Package bea-stax-api.noarch 0:1.2.0-0.rc1.2jpp.ep1.1.el5 set to be updated
---> Package msv-xsdlib.noarch 0:1.2-0.20050722.5jpp.ep1.1.el5.2 set to be updated
--> Running transaction check
---> Package xom.noarch 0:1.0-2jpp.ep1.3.el5.1 set to be updated
--> Processing Dependency: icu4j for package: xom
---> Package rhn-java-sat.noarch 0:0.1-3.el5 set to be updated
--> Processing Dependency: java >= 1.5.0 for package: rhn-java-sat
--> Processing Dependency: java-devel >= 1.5.0 for package: rhn-java-sat
---> Package isorelax.noarch 0:0.1-0.20041111.2jpp.ep1.2.el5.4 set to be updated
---> Package axis.i386 0:1.2.1-2jpp.6 set to be updated
--> Processing Dependency: jakarta-commons-discovery for package: axis
--> Processing Dependency: jakarta-commons-httpclient for package: axis
--> Processing Dependency: wsdl4j for package: axis
---> Package bouncycastle-jdk1.5.noarch 0:1.37-1jpp.1.el5 set to be updated
--> Processing Dependency: java >= 1.5.0 for package: bouncycastle-jdk1.5
---> Package taskomatic-sat.noarch 0:0.1-3.el5 set to be updated
--> Processing Dependency: java >= 1.5.0 for package: taskomatic-sat
--> Processing Dependency: java-devel >= 1.5.0 for package: taskomatic-sat
---> Package java-1.4.2-gcj-compat-devel.i386 0:1.4.2.0-40jpp.115 set to be updated
--> Processing Dependency: libgcj-devel >= 4.0.0-0.42 for package: java-1.4.2-gcj-compat-devel
--> Processing Dependency: /usr/lib/gcc/i386-redhat-linux/4.1.1/libgcj.spec for package: java-1.4.2-gcj-compat-devel
--> Processing Dependency: gcc-java >= 4.0.0-0.42 for package: java-1.4.2-gcj-compat-devel
--> Processing Dependency: libgcj-devel >= 4.0.0-0.42 for package: java-1.4.2-gcj-compat-devel
--> Processing Dependency: /usr/lib/gcc/i386-redhat-linux/4.1.1/libgcj.spec for package: java-1.4.2-gcj-compat-devel
--> Processing Dependency: gcc-java >= 4.0.0-0.42 for package: java-1.4.2-gcj-compat-devel
--> Running transaction check
---> Package jakarta-commons-discovery.i386 1:0.3-4jpp.1 set to be updated
---> Package rhn-java-sat.noarch 0:0.1-3.el5 set to be updated
--> Processing Dependency: java >= 1.5.0 for package: rhn-java-sat
--> Processing Dependency: java-devel >= 1.5.0 for package: rhn-java-sat
---> Package jakarta-commons-httpclient.i386 1:3.0-7jpp.1 set to be updated
---> Package gcc-java.i386 0:4.1.2-42.el5 set to be updated
---> Package bouncycastle-jdk1.5.noarch 0:1.37-1jpp.1.el5 set to be updated
--> Processing Dependency: java >= 1.5.0 for package: bouncycastle-jdk1.5
---> Package taskomatic-sat.noarch 0:0.1-3.el5 set to be updated
--> Processing Dependency: java >= 1.5.0 for package: taskomatic-sat
--> Processing Dependency: java-devel >= 1.5.0 for package: taskomatic-sat
---> Package libgcj-devel.i386 0:4.1.2-42.el5 set to be updated
---> Package icu4j.noarch 0:3.4.5-2jpp.ep1.2.el5 set to be updated
---> Package wsdl4j.i386 0:1.5.2-4jpp.1 set to be updated
--> Processing Conflict: rhns-xp conflicts specspo
--> Processing Conflict: rhns-app conflicts specspo
--> Finished Dependency Resolution
Error: rhns-app conflicts with specspo
Error: rhns-xp conflicts with specspo
Error: Missing Dependency: java-devel >= 1.5.0 is needed by package taskomatic-sat
Error: Missing Dependency: java >= 1.5.0 is needed by package bouncycastle-jdk1.5
Error: Missing Dependency: java-devel >= 1.5.0 is needed by package rhn-java-sat
Error: Missing Dependency: java >= 1.5.0 is needed by package rhn-java-sat
Error: Missing Dependency: java >= 1.5.0 is needed by package taskomatic-sat
--
Mike
2009/5/12 Juan Pablo Botero <juanpabloboterolopez(a)gmail.com>
> Ya revisaste la configuración del SELinux?.
>
> Para descartar, desactivalo, si deshabilitando tienes la solución, activalo
> y lo configuras de nuevo:
>
> # setup
> -> Firewall Configuration
> -> Customize (Personalizar), allí miras los dispositivos permitidos.
>
> Nos cuentas como te va.
>
> 2009/5/12 Walter Cervini <wcervini(a)gmail.com>
>
> Por lo general los servidores traen dos NIC, por l de la redundancia, en
>> ese configuras las interfaces en modo bonding.
>> Walter Cervini
>> movil: 0424-1543350
>> Pin: 20911CF3
>> Sent from Caracas, Venezuela
>>
>> 2009/5/13 Victor Padro <vpadro(a)gmail.com>
>>
>>
>>>
>>> 2009/5/12 Javier Aquino H. <JAquino(a)lexuseditores.com>
>>>
>>>> Hola Lista,
>>>>
>>>> Les comento un poco que hice y que problema tengo:
>>>>
>>>> Instalé CentOS 5.3 en un servidor HP con 6 GB de Ram, 450 GB de Disco y
>>>> 3 Tarjetas de Red ( eth0, eth1 y eth2 ), la idea es virtualizar este
>>>> servidor para soportar diversos servicios de mi empresa ( Base de datos,
>>>> Página Web, Correo, File Server, etc ). Durante la instalación todo bien.
>>>>
>>>> Las 3 tarjetas de red pertenecen al mismo segmento de red (
>>>> 192.168.1.0/24 ) de la siguiente manera:
>>>>
>>>> Eth0: 192.168.1.100
>>>> Eth1: 192.168.1.101
>>>> Eth2: 192.168.1.102
>>>>
>>>> Lóxicamente el default Gateway es el 192.168.1.1
>>>>
>>>> Actualmente solo el eth0 tiene cable de red, pero cuando inicio el
>>>> servidor este aparece aislado de la red por consiguiente no puede salir a
>>>> Internet, hacer ping a otras pc o hacer un ping de otra pc al servidor lo
>>>> cual me pareció muy raro y revisando di con el problema. Al hacer “route –n”
>>>> me dice que el defaul Gateway es el 192.168.1.1 pero el dispositivo que usa
>>>> es el eth1 y no en eth0 como debería ser muy a pesar que ese valor configuré
>>>> para la tarjeta eth0.
>>>>
>>>> Un dato curioso es que cuando hago un “service network restart” el def.
>>>> Gateway ya apunta al eth0 como debe ser y todo se normaliza. Otro dato
>>>> curioso es que cuando el servidor inicia, por un momento (muy breve) durante
>>>> el levantamiento de los servicios si le puedo hacer un ping al servidor pero
>>>> una vez que termina de cargar ya no hay forma.
>>>>
>>>> Alguien sabe que podría estar pasando ???? es como si algún script al
>>>> final de la carga de los servicios le dijera a mi Server que use el eth1
>>>> para el default Gateway ☹.
>>>>
>>>> Sorry por lo extenso del correo, quedo a la espera de vuestros
>>>> comentarios los cuales agradezco desde ya.
>>>>
>>>> Saludos,
>>>>
>>>> Javier.
>>>>
>>>>
>>>>
>>>> __________ Información de ESET NOD32 Antivirus, versión de la base de
>>>> firmas de virus 4068 (20090512) __________
>>>>
>>>> ESET NOD32 Antivirus ha comprobado este mensaje.
>>>>
>>>> http://www.eset.com
>>>>
>>>>
>>>>
>>>> --
>>>> Este mensaje ha sido analizado por MailScanner
>>>> en busca de virus y otros contenidos peligrosos,
>>>> y se considera que está limpio.
>>>> For all your IT requirements visit: http://www.transtec.co.uk
>>>>
>>>>
>>>> _______________________________________________
>>>> CentOS-es mailing list
>>>> CentOS-es(a)centos.org
>>>> http://lists.centos.org/mailman/listinfo/centos-es
>>>>
>>>>
>>> Ya probaste conectar las demas NICs a la red para ver que hace?
>>> que te hace el comando:
>>>
>>> ethtool eth0
>>> ethtool eth1
>>> ethtool eth2
>>>
>>> si no tienes el ethtool instalalo con:
>>>
>>> yum install ethtool
>>>
>>>
>>>
>>> saludos.
>>>
>>>
>>>
>>> --
>>> "It is human nature to think wisely and act in an absurd fashion."
>>>
>>> "Todo el desorden del mundo proviene de las profesiones mal o
>>> mediocremente servidas"
>>>
>>> _______________________________________________
>>> CentOS-es mailing list
>>> CentOS-es(a)centos.org
>>> http://lists.centos.org/mailman/listinfo/centos-es
>>>
>>>
>>
>> _______________________________________________
>> CentOS-es mailing list
>> CentOS-es(a)centos.org
>> http://lists.centos.org/mailman/listinfo/centos-es
>>
>>
>
>
> --
> Juan Pablo Botero
> Administrador de Sistemas informáticos
> http://jpill.wordpress.com
> eSSuX: http://slcolombia.org/eSSuX
> Linux Registered user #435293
>
> _______________________________________________
> CentOS-es mailing list
> CentOS-es(a)centos.org
> http://lists.centos.org/mailman/listinfo/centos-es
>
>
Con ethtool puedes ver si en verdad esta conectada la(s) NIC(s), que
velocidad usa(n) la(s) interface(s) eth0, eth1, eth2, entre otras cosas.
Yo uso bonding(load balancing) con cuatro NICs en dos diferentes subredes,
nada mas que no uso Xen si no con OpenVZ y no estan dificil hacerlo
funcionar, de este sitio me guie para hacer que funcionaran a la perfeccion:
http://www.howtoforge.com/network_card_bonding_centos
Podrias tambien checar el SElinux como sugirieron anteriormente.
--
"It is human nature to think wisely and act in an absurd fashion."
"Todo el desorden del mundo proviene de las profesiones mal o mediocremente
servidas"
okkkk
On Thu, Jan 30, 2014 at 9:10 PM, Jeffrey Hass <xaccusa(a)gmail.com> wrote:
> ... release notes and manuals, too --
> always good to hear what the 'prominent Linux vendor in 'North America'
> is thinking --
>
> ah, the pleasure of knowledge.. I'm surprised at the questions here ..
> most can be
> solved with that Google search. don't have to be technical now.. in
> fact, most technical
> people aren't. sad. get those damn iPod plugs out of your ears, jr.!
>
> /jh
>
>
>
> On 1/30/2014 7:38 AM, yoursurrogategod(a)gmail.com wrote:
> > Google is your friend (not that you really need in this instance).
> >
> > Sent from my iPhone
> >
> >> On Jan 30, 2014, at 10:32, dip patel <dip.patel6555(a)gmail.com> wrote:
> >>
> >> or i m also want to run cent os with my window 8 socan u please
> provide a
> >> direct download link for centos 6.5 or ftp link for download it?
> >>
> >>
> >>> On Thu, Jan 30, 2014 at 9:00 PM, dip patel <dip.patel6555(a)gmail.com>
> wrote:
> >>>
> >>> it can not b possible cause i m working in ISRO - PRL and it had a 348
> >>> node cluster and that all system is already running on Cent os so it
> is not
> >>> possible to change whole system due to this single problem my head
> doesnt
> >>> allow to me for this
> >>>
> >>>
> >>> On Thu, Jan 30, 2014 at 8:56 PM, Andreas Reschke <
> >>> Andreas.Reschke(a)mahle.com> wrote:
> >>>
> >>>> centos-bounces(a)centos.org schrieb am 30.01.2014 16:20:47:
> >>>>
> >>>>> Von: dip patel <dip.patel6555(a)gmail.com>
> >>>>> An: CentOS mailing list <centos(a)centos.org>
> >>>>> Datum: 30.01.2014 16:21
> >>>>> Betreff: Re: [CentOS] netcdf
> >>>>> Gesendet von: centos-bounces(a)centos.org
> >>>>>
> >>>>> i had used all the resources as below
> >>>>> and when i had all the untar in a directories and then ./configure
> the
> >>>>> netcdf file so it fives x lib developer is missing and some x11
> library
> >>>> is
> >>>>> also missing etc so please help me...
> >>>>>
> >>>>>
> >>>>> netcdf-4.3.1.tar.gz
> >>>>>
> >>>>> hdf5-1.9.148.tar.gz
> >>>>>
> >>>>> ncview-2.1.2.tar.gz
> >>>>>
> >>>>>
> >>>>> On Thu, Jan 30, 2014 at 8:38 PM, Alexander Dalloz
> >>>> <ad+lists(a)uni-x.org>wrote:
> >>>>>> Am 30.01.2014 16:03, schrieb Alexander Dalloz:
> >>>>>>> Am 30.01.2014 15:45, schrieb dip patel:
> >>>>>>>> i m working in PHYSICAL RESEARCH LABORATORY as a engineer trainee
> >>>> and
> >>>>>> want
> >>>>>>>> to install netcdf file and ncview but it gives some OS error
> >>>>>> Sorry, I did sent my previous message too early.
> >>>>>>
> >>>>>> Your problem description lacks a lot of detail.
> >>>>>>
> >>>>>> Where do you take netcdf from? The EPEL repository provides it. If
> you
> >>>>>> use that package and binaries fail, you should contact the EPEL
> >>>> packager
> >>>>>> and provide a bug report.
> >>>>>>
> >>>>>> "some OS error" is very unspecific.
> >>>>>>
> >>>>>> Start by asking yourself: "What kind of information would I need if
> >>>>>> someone else has this problem and searches for support?" Then
> provide
> >>>>>> this information actively.
> >>>>>>
> >>>>>> Kind regards
> >>>>>>
> >>>>>> Alexander
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> CentOS mailing list
> >>>>>> CentOS(a)centos.org
> >>>>>> http://lists.centos.org/mailman/listinfo/centos
> >>>>>
> >>>>>
> >>>>> --
> >>>>>
> >>>>>
> >>>>> Thanks and Regards,
> >>>>> Dip Patel
> >>>>> +919925598555
> >>>>> _______________________________________________
> >>>>> CentOS mailing list
> >>>>> CentOS(a)centos.org
> >>>>> http://lists.centos.org/mailman/listinfo/centos
> >>>> Why do you don't use "yum search netcdf" btw "yum install netcdf" ?
> >>>>
> >>>>
> >>>> Mit freundlichen Grüßen / Kind regards
> >>>>
> >>>> Andreas Reschke
> >>>> _______________________________________________
> >>>> CentOS mailing list
> >>>> CentOS(a)centos.org
> >>>> http://lists.centos.org/mailman/listinfo/centos
> >>>
> >>>
> >>> --
> >>>
> >>>
> >>> Thanks and Regards,
> >>> Dip Patel
> >>> +919925598555
> >>
> >>
> >> --
> >>
> >>
> >> Thanks and Regards,
> >> Dip Patel
> >> +919925598555
> >> _______________________________________________
> >> CentOS mailing list
> >> CentOS(a)centos.org
> >> http://lists.centos.org/mailman/listinfo/centos
> > _______________________________________________
> > CentOS mailing list
> > CentOS(a)centos.org
> > http://lists.centos.org/mailman/listinfo/centos
>
> _______________________________________________
> CentOS mailing list
> CentOS(a)centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
--
Thanks and Regards,
Dip Patel
+919925598555
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/23/2011 07:51 AM, David McGuffey wrote:
>
> On Fri, 2011-04-22 at 06:50 -0400, David McGuffey wrote:
>> On Fri, 2011-04-22 at 06:18 -0400, Daniel J Walsh wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> On 04/21/2011 09:47 PM, David McGuffey wrote:
>>>>
>>>> On Thu, 2011-04-21 at 21:09 -0400, David McGuffey wrote:
>>>>> On Thu, 2011-04-21 at 18:01 +0200, Kenni Lund wrote:
>>>>>> 2011/4/21 Johnny Hughes <johnny(a)centos.org>:
>>>>>>> On 04/21/2011 06:11 AM, David McGuffey wrote:
>>>>>>>> redlibvirtError: internal error Process exited while reading console log
>>>>>>>> output: qemu: could not open disk image /dev/hda
>>>>>>>
>>>>>
>>>>> Problem may be an SELinux problem. Here is the alert. Notice the
>>>>> reference to '/dev/hda' (which is the virtual machine boot disk), and
>>>>> the SELinux context 'virt_content_t'
>>>>>
>>>>> Summary:
>>>>>
>>>>> SELinux is preventing pam_console_app (pam_console_t) "getattr"
>>>>> to /dev/hda
>>>>> (virt_content_t).
>>>>>
>> ...
>>>>> Detailed Description:
>>>>>
>>>>> SELinux denied access requested by pam_console_app. It is not expected
>>>>> that this
>>>>> access is required by pam_console_app and this access may signal an
>>>>> intrusion
>>>>> attempt. It is also possible that the specific version or configuration
>>>>> of the
>>>>> application is causing it to require additional access.
>>>>>
>> ...
>>>>
>>>> Yep...each time I try to start the VM, sealert increments this error by
>>>> one.
>>>>
>>>> I created /.autorelable and rebooted. SELinux relabeled everything, but
>>>> the sealert still fires when I try to start the VM.
>>>>
>>>> I did a qemu-img <path_to_vm>/vm.img and the format is declared 'raw'
>>>> Therefore I should not be editing the vm.xml file and changing 'raw' to
>>>> 'qcow2'
>>>>
>>>> Problem is definately with the SELlnux labels in the 5.6 upgrade.
>>>>
>>>> Dave M
>>>>
>>>>
>> ...
>>> This is an SELinux issue. It really has no effect on the virtual
>>> machine. The problem is the label is not something pam_console policy
>>> expected to have on a blk device.
>>
>> Yes, I was lured by the coincidence of the sealert and my effort to
>> start the VM. The fact that the blk device in question happens to
>> register as /dev/hda and the VM also uses an internal "virtual" device
>> called /dev/hda can lead one astray.
>>
>> I'm still left without an answer as to why virsh won't create or
>> define-->start a VM after the upgrade.
>>
>> [root@desk dev]# cd /etc/libvirt/qemu
>>
>> [root@desk qemu]# virsh create Win7-base.xml
>> error: Failed to create domain from Win7-base.xml
>> error: internal error Process exited while reading console log output:
>> qemu: could not open disk image /dev/hda
>>
>> using qemu-img against the image file reports 'raw' not 'qcow2' So...I
>> should not have to edit the .xml file...it is already correct.
>>
>> [root@desk images]# qemu-img info Win7-base.img
>> image: Win7-base.img
>> file format: raw
>> virtual size: 29G (31457280000 bytes)
>> disk size: 29G
>>
>> This is not good. I've been developing a prototype which uses several
>> VMs under qemu-kvm. I'm now starting to question whether CentOS is the
>> right tool to be using for prototyping capability that may eventually
>> roll onto regular RHEL.
>>
> Did some more poking around and this is an SELinux problem. SELinux is
> denying access to /dev/hda. /dev/hda turns out to be the CDROM/DVD R/W
> device on the EIDE port of the motherboard. Lots of alias devices are
> linked to it.
>
> When I try to start a VM that has a cdrom defined, selinux stops the
> access and virsh (and Virtual Machine Manager) will report an error
> accessing /dev/hda (the cdrom). Here is the cdrom portion of the xml
>
> <disk type='block' device='cdrom'>
> <driver name='qemu' type='raw'/>
> <source dev='/dev/hda'/>
> <target dev='hdc' bus='ide'/>
> <readonly/>
> <address type='drive' controller='0' bus='1' unit='0'/>
> </disk>
>
> As soon as I detached the cdrom device from the VM, the VM starts and
> runs A-OK.
>
> Here is a listing of all the hda devices (blk and links) in /dev
>
> [root@desk ~]# cd /dev/
> [root@desk dev]# ls -Z |grep hda
> lrwxrwxrwx root root system_u:object_r:device_t cdrom-hda
> lrwxrwxrwx root root system_u:object_r:device_t cdrw-hda
> lrwxrwxrwx root root system_u:object_r:device_t cdwriter-hda
> lrwxrwxrwx root root system_u:object_r:device_t dvd-hda
> lrwxrwxrwx root root system_u:object_r:device_t dvdrw-hda
> lrwxrwxrwx root root system_u:object_r:device_t dvdwriter-hda
> brw------- dave disk system_u:object_r:virt_content_t hda
>
> Notice the selinux context includes 'virt_content_t' I'm not sure this
> is right or wrong.
>
> What is strange is the owner:group of hda is my normal (unprivileged)
> user login 'dave' I would have thought it would be root:kvm (where dave
> is a member of kvm).
>
> Methinks either the owner:group or the selinux context of hda is wrong,
> or the linked devices may also need to have the 'virt_content_t'
> context.
>
> I just downloaded a fresh 5.6 iso and will build it on a spare machine.
> Goal is to see what kind of devices are created and what kind of
> owner:group permissions are given and what kind of selinux context is
> given to /dev/hda. They may be different from an upgrade.
>
> All this came up with the upgrade from 5.5 to 5.6, so it is both a
> CentOS 5.6 problem and an selinux problem. Should I leave this here or
> summarize what I found over on the fedora selinux forum?
>
> Dave M
>
>
> _______________________________________________
> CentOS mailing list
> CentOS(a)centos.org
> http://lists.centos.org/mailman/listinfo/centos
Try restorecon -RF on the device.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAk21b/gACgkQrlYvE4MpobNbNQCeMME1CsmexXYEtnv+dY7Vdwoz
7iEAoMpw7H0l488ihvpblNbXMPmZn+xW
=Ojrb
-----END PGP SIGNATURE-----
I had my eye on the Tyan dual-Opteron mobos for awhile. I tried to find
a posting *anywhere* sharing experiences with these boards under Linux.
No such luck. So placing myself under the heading "Where Angles Fear to
Tread," I went ahead and built a system anyway. Here's what I've learned.
The specs:
Tyan Thunder K8SE S2892, BIOS 1.01
2x Opteron 270, 2Ghz Dual-Core, retail package with fan
2GB RAM (4x SuperTalent 512MB P/N D32RB12P3)
3Ware 9500S-4LP 4 port SATA controller
4x 200GB Segate ST3200826AS 7200.8 SATA (attached to 3Ware controller)
1x 80GB Wester Digital WD800JD-00LSA0 SATA (attached to onboard controller)
Antec Truepower 2.0 550W PSU
Chenming 901A-0-0 RTL Case
Supermicro 5-drive SATA HD Cage
CentOS 4.1 x86_64
I thought I bought a plenty large case. Turns out the CPU heat sink at
the front of the motherboard sticks up far enough to interfere with the
drive bays at the bottom of the case. I had carefully mounted the CPUs,
heat sinks and memory before mounting the motherboard. When I tried to
insert the motherboard, the front heat sink hit the shelf that supports
one of the two internal hard drive cages that come with the Chenming
case. I had to peel off the heat sink to get the board in then reinstall
it -- something I didn't want to do. If the case was 9" wide instead of
8", this probably wouldn't be an issue.
The heat sink sticks up far enough to keep me from reinstalling the
internal hard drive cages. Not a problem since I'm using the Supermicro
SATA cage, but it bugs me to lose expansion possibilities. Can anyone
recommend a "low-rise" Opteron heat sink?
I hadn't yet purchased an optical drive and so was planning on
booting the install program from a USB key. However I could not get the
BIOS to recognize the key. I put 'removable drives' at the top of the
boot preferences but it refused to recognize the key. I ended up doing a
PXE boot install instead.
The install hung once forcing me to restart. But after that the install
process was the fastest I've ever seen, taking about seven minutes to
copy everything.
Booting the first time, I was happy to see that everything was
recognized by the system, all three network ports, the Nvidia SATA
controller and even the 3Ware controller.
However, the boot messages showed:
warning: many lost ticks.
Your time source seems to be instable or some driver is hogging
interrupts
and several repeating messages:
powernow-k8: error - out of sync...
Also, /proc/cpuinfo showed each cpu as running at about 1004Mhz with
about 900 bogomips. Not what I expected.
I decided to press ahead and added a couple of drives the the 3Ware,
created a unit, formatted it and began benchmarking the array. The
"powernow" messages continued to occur and then the 3Ware driver started
issuing error messages. Eventually the system crashed and stopped
responding.
Googling on the powernow error message let me know that the kernel
wizards had started to fix some powernow bugs starting with about kernel
2.6.10. Of course the stock CentOS 4.1 kernel is 2.6.9-11.
So I downloaded, compiled and installed kernel 2.6.12.3. On rebooting,
the error messages went away and the 3Ware worked without complaint. Now
/proc/cpuinfo showed each cpu running at 2009.267 Mhz with 4014.08
bogomips. Ah, much better! In addition, the system came up in with NUMA
enabled. Looks like the Red Hat kernel had it turned off by default.
I benchmarked disk array performance using Bonnie++ version 1.03a. I ran
six benchmarks using 50GB of data, three using 16k blocks and three
using 64k blocks. During the raid 0 testing I had two instances of
Setiathome running. During the raid 5 testing I had three instances of
Setiathome running. Here are the results:
Raid 0, 64k Stripes:
bonnie++ 1.03a ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
Tyan 50G:16k 49317 99 138307 62 +++++ +++ 46765 80 183180 22 88.9 0
Tyan 50G:16k 48911 98 148421 67 77099 21 46018 79 182136 21 89.8 0
Tyan 50G:16k 49188 98 143615 65 77381 21 46158 78 181181 21 90.5 0
Tyan 50G:64k 49372 99 146417 67 77185 21 45828 78 179758 21 76.7 0
Tyan 50G:64k 48585 98 145376 66 76580 21 45609 78 171888 21 76.3 0
Tyan 50G:64k 46093 92 134903 58 67851 18 45200 77 172103 21 75.6 0
------Sequential Create------ --------Random Create--------
-Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files:max:min /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
Tyan 16 2524 97 +++++ +++ +++++ +++ 2542 97 +++++ +++ 8670 99
Tyan 16 2385 98 +++++ +++ +++++ +++ 2579 97 +++++ +++ 8408 98
Tyan 16 2627 97 +++++ +++ +++++ +++ 2437 92 +++++ +++ 8671 100
Tyan 16 1582 98 +++++ +++ +++++ +++ 1647 98 +++++ +++ 8488 100
Tyan 16 1399 85 +++++ +++ +++++ +++ 1632 98 +++++ +++ 8476 99
Tyan 16 1654 95 +++++ +++ +++++ +++ 1636 98 +++++ +++ 8405 99
Writes at about 140MB/Sec, reads at about 180MB/Sec. Very nice.
Raid 5, 64k Stripes:
bonnie++ 1.03a ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
Tyan 50G:16k 33394 68 35889 16 26513 7 44096 75 157248 19 84.1 0
Tyan 50G:16k 32601 67 36058 16 26623 7 43964 75 156970 19 83.3 0
Tyan 50G:16k 37892 77 35702 16 26960 7 44390 75 157084 19 83.5 0
Tyan 50G:64k 36168 74 35560 17 27003 8 43463 75 155179 20 69.1 0
Tyan 50G:64k 32713 68 36187 16 26580 7 43922 76 156752 20 69.2 0
------Sequential Create------ --------Random Create--------
-Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files:max:min /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
Tyan 16 1561 98 +++++ +++ +++++ +++ 1694 97 +++++ +++ 8428 97
Tyan 16 1672 98 +++++ +++ +++++ +++ 1712 97 +++++ +++ 8751 99
Tyan 16 1542 98 +++++ +++ +++++ +++ 1355 81 +++++ +++ 8986 100
Tyan 16 2534 96 +++++ +++ +++++ +++ 2408 96 +++++ +++ 7945 98
Tyan 16 2382 97 +++++ +++ +++++ +++ 2380 97 +++++ +++ 7989 99
Whoa! Writes drop to about 35MB/Sec under raid 5, about 25% of the raid 0
performance. In fact, it was taking so long that I aborted the last test. Just to be
sure that setiathome wasn't interfering, I killed seti and reran a smaller test.
Writes increased to about 50MB/Sec without seti running. I was expecting some hit for
raid 5 but not this much. Guess I'll stick with the hot rsync backups to other hosts
scheme that I'm using now.
As a final test, I restarted the 50GB benchmark under raid5 and popped out one of the
drives. There was a pause while I guess the 3Ware controller decided that the drive
actually went off-line. The writing then continued to the remaining three disks.
Checking the controller showed that both the drive and the unit were 'DEGRADED.'
After popping the disk back in, I had to remove and re-add the drive to the array
configuration then start the rebuild process. At this point the drive showed
'DEGRADED' and the unit showed 'REBUILDING.' The 3Ware drive logged appropriate
messages when the disk was removed and replaced. I didn't bother finishing the
rebuild, but it looked like it would take a couple of hours to finish if I let the
benchmark continue to run.
The 3Ware controller is pretty cool. As I said, the driver (3w-9xxx) is
included in the 2.6 kernel. 3Ware provides a simple CLI utility for
management. They also have a GUI tool but I didn't bother running it.
You can create, remove and verify 'units' on a running system. The
associated /dev entries are dynamically added and removed as you make
changes. Very nice.
In summary, the Tyan S2892 plus the 3Ware controller runs well under CentOS 4.1
although you will have to update to a more current kernel than the one provided by
Red Hat. Watch your clearance at the front of the motherboard when selecting a case.
Comments and corrections are encouraged.
Kirk Bocek
Ryan+list
The link lights are up on the card from very early in the boot process. I
am pretty sure the card is working except it is just unavailable if I try
and start eth1. The system-config-network gui for wireless doesn't
actually let you select the channel to use either. I am actually on
channel 13 which should work OK. As I say, all things currently point to
the /en/ locale not being installed. Can this be retrofitted? I can't
find the files in the CentOS4 packages anywhere.
TIA
John
John Logsdon "Try to make things as simple
Quantex Research Ltd, Manchester UK as possible but not simpler"
j.logsdon(a)quantex-research.com a.einstein(a)relativity.org
+44(0)161 445 4951/G:+44(0)7717758675 www.quantex-research.com
On Tue, 24 May 2005, Ryan wrote:
> is the link/power light on your pcmcia card on when you plug it in, or
> is it stay off?
>
> John Logsdon wrote:
> > Ryan and list
> >
> > pcmcia set 0,1,6 off and 2,3,4,5 on.
> >
> > If I try to restart pcmcia, it obviously complains that pcmcia_core is
> > used by i82365,pcnet_cs,ds as I have another network card plugged in at
> > the moment so I can use the machine (the Tosh Portege 3490CT's other
> > network interface requires plugging the big dongle thing in so I use a
> > card).
> >
> > And while using the standard CentOS update solved the gpg problem,
> >
> > yum upgrade kde (for example) gave an error:
> >
> > Traceback (most recent call last):
> > File "/usr/bin/yum", line 7, in ?
> > yummain.main(sys.argv[1:])
> > File "/usr/share/yum-cli/yummain.py", line 34, in main
> > locale.setlocale(locale.LC_ALL, '')
> > File "/usr/lib/python2.3/locale.py", line 381, in setlocale
> > return _setlocale(category, locale)
> > locale.Error: unsupported locale setting
> >
> > which may be entirely unconnected but is an error in the same area as the
> > strace indicated for the wireless card. I can post the strace if needed
> > but it is quite long.
> >
> > TIA
> >
> > John
> >
> > John Logsdon "Try to make things as simple
> > Quantex Research Ltd, Manchester UK as possible but not simpler"
> > j.logsdon(a)quantex-research.com a.einstein(a)relativity.org
> > +44(0)161 445 4951/G:+44(0)7717758675 www.quantex-research.com
> >
> >
> > On Mon, 23 May 2005, Ryan wrote:
> >
> >
> >>Does chkconfig have pcmcia in it? If so, what is it set to?
> >>
> >>John Logsdon wrote:
> >>
> >>>That seems a bit better so I can add the 128 bit WEP code. But for some
> >>>reason I still can't activate it. I get:
> >>>
> >>>SIOCSIFFLAGS: Resource temporarily unavailable
> >>>
> >>>which does not point too far.
> >>>
> >>>I have checked that the atmel_cs module is installed (the card is a Belkin
> >>>F5D6020 rev 2).
> >>>
> >>>I have tried an strace and it seems to be looking for a file libc.mo in
> >>>/usr/share/locale/[en.UTF-8|en.utf8|en]/LC_MESSAGES but there is one in
> >>>/usr/share/local/en_GB/LC_MESSAGES and pretty nearly every other locale
> >>>which are all in glibc-common.
> >>>
> >>>I guess this is because I switched from en_US to en_GB when I installed -
> >>>ie I unchecked US English. I don't seem to recall having this problem
> >>>with other machines although this is the first one that I have tried
> >>>to use wireless with...
> >>>
> >>>I tried changing LANG to be en and I get the same result although the
> >>>strace now fails rather earlier.
> >>>
> >>>So it seems at least that I should reinstall en=en_US but I am not
> >>>convinced that this will solve the problem. And where is it anyway? I
> >>>can't see it in any of the CentOS4 rpms - I have been through all 1404 of
> >>>them. It seems to be installed from somewhere when you set up CentOS4.
> >>>Surely I don't have to reinstall?
> >>>
> >>>Clues?
> >>>
> >>>TIA
> >>>
> >>>John
> >>>John Logsdon "Try to make things as simple
> >>>Quantex Research Ltd, Manchester UK as possible but not simpler"
> >>>j.logsdon(a)quantex-research.com a.einstein(a)relativity.org
> >>>+44(0)161 445 4951/G:+44(0)7717758675 www.quantex-research.com
> >>>
> >>>
> >>>On Mon, 23 May 2005, ryan wrote:
> >>>
> >>>
> >>>
> >>>>system-config-network from the commandline brings up a GUI that you can
> >>>>enter in the WEP key for. You do not need to upgrade to KDE 3.4 for this.
> >>>>
> >>>>
> >>>>
> >>>>>What do people recommend?
> >>>>
> >>>>My recommendation is to use a different included GUI tool than kwifi
> >>>>(system-config-network). Instructions are here:
> >>>>http://www.centos.org/docs/4/html/rhel-sag-en-4/s1-network-config-wireless.…
> >>>>
> >>>>You can also edit /etc/sysconfig/network-scripts/ifcfg-eth0 (or whatever
> >>>>your LAN card is) directly, but if you have never done this before, I'd say
> >>>>use the GUI.
> >>>>
> >>>>
> >>>>----- Original Message -----
> >>>>From: "John Logsdon" <j.logsdon(a)quantex-research.com>
> >>>>To: "CentOS mailing list" <centos(a)centos.org>
> >>>>Sent: Monday, May 23, 2005 4:25 AM
> >>>>Subject: Re: [CentOS] CentOS4, KDE3.3 and 128 WEP
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>Folks
> >>>>>
> >>>>>My concern is not so much just how good or bad WEP is - and I agree that
> >>>>>it is much better to use ssh or a vpn tunnel. Until 802.11i is fully
> >>>>>implemented, standard wireless is always going to be very easy to hack by
> >>>>>a sniffing geekster.
> >>>>>
> >>>>>The problem is that there are quite a lot other machines on the network
> >>>>>that have been configured with WEP128. I don't use DHCP and I have MAC
> >>>>>filtering enabled so that is some protection. Unconfiguring all those
> >>>>>machines will be a pain and as some of them are WinDroze XPoor, almost
> >>>>>certainly to fall over.
> >>>>>
> >>>>>OK - maybe the solution is to upgrade to KDE3.4. There are comments about
> >>>>>128 WEP in the 3.4 kdenetwork package. And is KDE3.4 already stable
> >>>>>enough to be included? What do people recommend? Has anyone upgraded to
> >>>>>3.4?
> >>>>>
> >>>>>Another issue is where is the gpg public key repository for CentOS4?
> >>>>>
> >>>>>So my problem remains. At the moment I am using a regular wired
> >>>>>connection but that means that the garden is out of bounds and it is nice
> >>>>>and sunny today here in Manchester ... :-)
> >>>>>
> >>>>>Best wishes
> >>>>>
> >>>>>John
> >>>>>
> >>>>>John Logsdon "Try to make things as simple
> >>>>>Quantex Research Ltd, Manchester UK as possible but not simpler"
> >>>>>j.logsdon(a)quantex-research.com a.einstein(a)relativity.org
> >>>>>+44(0)161 445 4951/G:+44(0)7717758675 www.quantex-research.com
> >>>>>
> >>>>>
> >>>>>On Sun, 22 May 2005, Ryan wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>>I disagree with this assessment.
> >>>>>>
> >>>>>>WPA-PSK is not much more secure than 128-bit WEP, since its passphrases
> >>>>>>vulnerable to common dictionary attacks. Worse, linux has poor WPA
> >>>>>>support - not every wifi card supported by linux has WPA support.
> >>>>>>
> >>>>>>Also, many non-computer devices (wireless webcams, etc) only have WEP as
> >>>>>>an option.
> >>>>>>
> >>>>>>Use system-config-network , not kwifi, and you should be able to use WEP
> >>>>>>with no problem. Also, consider turning OFF DHCP, turning the AP off
> >>>>>>when you aren't using it, and enabling MAC filtering.
> >>>>>>
> >>>>>>If you are really concerned about security, consider using an SSH or VPN
> >>>>>>tunnel to encrypt data between laptops and a wired router/server.
> >>>>>>
> >>>>>>For some information on WPA-PSK weaknesses:
> >>>>>>http://wifinetnews.com/archives/002452.html
> >>>>>>
> >>>>>>
> >>>>>>system-config-network requires you enter in "0x" bbefore the key.
> >>>>>>
> >>>>>>
> >>>>>>Maciej Zenczykowski wrote:
> >>>>>>
> >>>>>>
> >>>>>>>You can skip wep128 or wep64 or any other wep for that matter,
> >>>>>>>currently a standard notebook with a supported wireless card running
> >>>>
> >>>>linux
> >>>>
> >>>>
> >>>>>>>can passively break through wep64/wep128 encryption within 10-30
> >>>>>>>minutes, switching to active mode can break through the encryption
> >>>>>>>within 3-5 minutes. Simply put, encryption of the WEP kind is no
> >>>>
> >>>>longer
> >>>>
> >>>>
> >>>>>>>worth the bother.
> >>>>>>>
> >>>>>>>Just look around on google, he's a quote I found:
> >>>>>>>
> >>>>>>>Department: Here's a demo of the FBI, using commonly available and
> >>>>
> >>>>openly
> >>>>
> >>>>
> >>>>>>>documented hardware & software to crack WEP 128-bit security in three
> >>>>>>>minutes.
> >>>>>>>
> >>>>>>>http://www.tomsnetworking.com/Sections-article111-page1.php
> >>>>>>>
> >>>>>>>The needed utilites can be freely downloaded of the internet.
> >>>>>>>
> >>>>>>>Cheers,
> >>>>>>>MaZe.
> >>>>>>>
> >>>>>>>On Sun, 22 May 2005, John Logsdon wrote:
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>>CentOS4 standard installation.
> >>>>>>>>
> >>>>>>>>I see that KwifiManager doesn't support 128 bit WEP which I need for
> >>>>>>>>other
> >>>>>>>>machines on the network, which is a bit of a blow - and rather
> >>>>
> >>>>surprising
> >>>>
> >>>>
> >>>>>>>>really as security should be quite a consideration on an enterprise
> >>>>
> >>>>level
> >>>>
> >>>>
> >>>>>>>>system (NB RH!).
> >>>>>>>>
> >>>>>>>>Is there a workaround? An alternative way of configuring my Belkin
> >>>>>>>>F5D6020 ver 2 card? eg a cvs download that I can get and copy via a
> >>>>>>>>stick? Or how to do it manually? I have tried regressing kdenetwork
> >>>>
> >>>>but
> >>>>
> >>>>
> >>>>>>>>that doesn't include kwifimanager at all.
> >>>>>>>>
> >>>>>>>>Ideas?
> >>>>>>>>
> >>>>>>>>TIA
> >>>>>>>>
> >>>>>>>>John
> >>>>>>>>
> >>>>>>>>John Logsdon "Try to make things as
> >>>>
> >>>>simple
> >>>>
> >>>>
> >>>>>>>>Quantex Research Ltd, Manchester UK as possible but not
> >>>>
> >>>>simpler"
> >>>>
> >>>>
> >>>>>>>>j.logsdon(a)quantex-research.com a.einstein(a)relativity.org
> >>>>>>>>+44(0)161 445 4951/G:+44(0)7717758675 www.quantex-research.com
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>_______________________________________________
> >>>>>>>>CentOS mailing list
> >>>>>>>>CentOS(a)centos.org
> >>>>>>>>http://lists.centos.org/mailman/listinfo/centos
> >>>>>>>>
> >>>>>>>
> >>>>>>>_______________________________________________
> >>>>>>>CentOS mailing list
> >>>>>>>CentOS(a)centos.org
> >>>>>>>http://lists.centos.org/mailman/listinfo/centos
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>_______________________________________________
> >>>>>>CentOS mailing list
> >>>>>>CentOS(a)centos.org
> >>>>>>http://lists.centos.org/mailman/listinfo/centos
> >>>>>>
> >>>>>
> >>>>>_______________________________________________
> >>>>>CentOS mailing list
> >>>>>CentOS(a)centos.org
> >>>>>http://lists.centos.org/mailman/listinfo/centos
> >>>>>
> >>>>
> >>>>_______________________________________________
> >>>>CentOS mailing list
> >>>>CentOS(a)centos.org
> >>>>http://lists.centos.org/mailman/listinfo/centos
> >>>>
> >>>
> >>>
> >>>
> >>>_______________________________________________
> >>>CentOS mailing list
> >>>CentOS(a)centos.org
> >>>http://lists.centos.org/mailman/listinfo/centos
> >>>
> >>>
> >>
> >>_______________________________________________
> >>CentOS mailing list
> >>CentOS(a)centos.org
> >>http://lists.centos.org/mailman/listinfo/centos
> >>
> >
> >
> > _______________________________________________
> > CentOS mailing list
> > CentOS(a)centos.org
> > http://lists.centos.org/mailman/listinfo/centos
> >
> >
>
> _______________________________________________
> CentOS mailing list
> CentOS(a)centos.org
> http://lists.centos.org/mailman/listinfo/centos
>