Tag Info

New answers tagged

1

Why are you installing one item at a time via a script? No need to do this when you can just place all items in one line like this: yum -y install libstdc++.i686 ibibcm.x86_64 librdmacm.x86_64 ibsim.x86_64 ibutils.x86_64 libcxgb3.x86_64 libibmad.x86_64 libipathverbs.x86_64 Now that said, I don’t believe all of the yum -y install directives are running ...


0

Your first question regards disk errors. It can be caused by a list of different things. I would start with fsck and other file system tools, and then move on to commercial disk recovery tools afterwards (e.g. SpinRite). Your second question is frequently asked.


2

The Apache API changed from 2.2 to 2.4, unixd_config was renamed ap_unixd_config (see Api changes from 2.2 to 2.4). You need a php module version that is compatible with Apache 2.4 or stay with Apache 2.2.


0

I am not sure about exactly what you mean by physical ports. dmidecode can list connectors, # dmidecode --type 8 # dmidecode 2.12 SMBIOS 2.5 present. Handle 0x0004, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: Internal Connector Type: None External Reference Designator: EXTERNAL MONITOR PORT External ...


-1

This worked for me. yum --nogpgcheck install git -y


0

From CProgramming Borad The win32 API supports both the one-to-one and many-to-many models (in the thread library and fiber library respectively). Windows 7, like all of the NT family, supports the win32 API. Windows 7 supports kernel threads. So it must be a one to one model or many to many model. But it is in fact a hybrid that supports ...


0

I have never seen the rocommunity option. By the looks of the config you pasted, you have edited the default snmpd.conf, so, changing public to iglass should suffice. On the other hand I'd advise to use v3 instead of v2c, that's full of vulnerabilities. Also, with v3 the config files get edited automatically. Example: net-snmp-config --create-snmpv3-user ...


0

It happens because %post section is chrooted to /mnt/sysimage (where the system you are installing is). To get access to /tmp created in your %pre, you need to use "--nochroot " option in the %post section. This may lead to create 2 distinct post sections (one with "--nochroot " the other without), or you'll need to prefix any path with /mnt/sysimage. ...



Top 50 recent answers are included