CentOS Errata and Security Advisory 2014:X001 (Xen4CentOS)
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
-
X86_64
-
CentOS Errata and Security Advisory 2014:X002 (Xen4CentOS)
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
-
X86_64
-
CentOS Errata and Security Advisory 2014:X003 (Xen4CentOS)
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
-
X86_64
-
Hi,
After upgrading to kernel 2.6.32-431.1.2.el6.x86_64 the messages below
keep appearing in /var/log/messages.
--
ata16.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata16.00: irq_stat 0x4001
scsi 16:0:0:0:
On 1/24/2014 12:54 AM, Steve Brooks wrote:
[root@mach~]# sginfo /dev/scanner
INQUIRY response (cmd: 0x12)
Device Type3
Vendor:Marvell
Product: 91xx Config
Revision level:1.01
fwiw, scsi
On Fri, 24 Jan 2014, John R Pierce wrote:
On 1/24/2014 12:54 AM, Steve Brooks wrote:
[root@mach~]# sginfo /dev/scanner
INQUIRY response (cmd: 0x12)
Device Type3
Vendor:Marvell
Product: 91xx Config
On 1/23/2014 6:41 PM, Peter wrote:
On 01/24/2014 03:47 AM, Michael Hennebry wrote:
On Thu, 23 Jan 2014, Peter wrote:
it has four molex four pin connectors any one of which should be
suitable for your CD drive, and one floppy connector which should work
for your floppy drive just fine.
I
I wasn't paying much attention, but I remember a day or two ago, someone
was complaining about python updates. From the RH alerts...
snip
This update fixes the following bug:
* Previously, the dependencies between the Python subpackages were set
erroneously and caused problems with the inclusion
I installed Centos 6.x 64 bit with the minimal ISO and used two disks
in RAID 1 array.
Filesystem Size Used Avail Use% Mounted on
/dev/md2 97G 918M 91G 1% /
tmpfs16G 0 16G 0% /dev/shm
/dev/md1485M 54M 407M 12% /boot
/dev/md33.4T 198M
In article caaom8fxumosagbde+pzryraruhcswojwjqf-3mc0tsn4odr...@mail.gmail.com,
Matt matt.mailingli...@gmail.com wrote:
I installed Centos 6.x 64 bit with the minimal ISO and used two disks
in RAID 1 array.
Filesystem Size Used Avail Use% Mounted on
/dev/md2 97G 918M 91G 1%
On Fri, Jan 24, 2014 at 11:58 AM, Matt matt.mailingli...@gmail.com wrote:
I installed Centos 6.x 64 bit with the minimal ISO and used two disks
in RAID 1 array.
Filesystem Size Used Avail Use% Mounted on
/dev/md2 97G 918M 91G 1% /
tmpfs16G 0 16G 0%
I installed Centos 6.x 64 bit with the minimal ISO and used two disks
in RAID 1 array.
Filesystem Size Used Avail Use% Mounted on
/dev/md2 97G 918M 91G 1% /
tmpfs16G 0 16G 0% /dev/shm
/dev/md1485M 54M 407M 12% /boot
/dev/md33.4T
On Fri, Jan 24, 2014 at 11:25 AM, Matt matt.mailingli...@gmail.com wrote:
I am guessing this is saying its present on both? I did nothing to
copy it there so it must have done it during the centos 6.x install
process.
I think the 6.x installers try to do it for you on both drives - but
On 1/24/2014 10:11 AM, Les Mikesell wrote:
On Fri, Jan 24, 2014 at 11:25 AM, Mattmatt.mailingli...@gmail.com wrote:
I am guessing this is saying its present on both? I did nothing to
copy it there so it must have done it during the centos 6.x install
process.
I think the 6.x installers
On 01/24/2014 07:32 PM, John R Pierce wrote:
On 1/24/2014 10:11 AM, Les Mikesell wrote:
On Fri, Jan 24, 2014 at 11:25 AM, Mattmatt.mailingli...@gmail.com wrote:
I am guessing this is saying its present on both? I did nothing to
copy it there so it must have done it during the centos 6.x
On Fri, Jan 24, 2014 at 1:30 PM, Ljubomir Ljubojevic cen...@plnet.rs wrote:
and, even if you have the boot loader on both drives, there's no
guarantee your BIOS will boot from the 2nd one.Disks can partially
fail in nasty ways that might allow the already-running system to stay
up on the
On 01/24/2014 09:25 AM, Matt wrote:
# file -s /dev/sda
/dev/sda: x86 boot sector; GRand Unified Bootloader, stage1 version
0x3, boot drive 0x80, 1st sector stage2 0x849fc, GRUB version 0.94;
partition 1: ID=0xee, starthead 0, startsector 1, 4294967295 sectors,
extended partition table
On 01/24/2014 09:33 PM, Les Mikesell wrote:
On Fri, Jan 24, 2014 at 1:30 PM, Ljubomir Ljubojevic cen...@plnet.rs wrote:
and, even if you have the boot loader on both drives, there's no
guarantee your BIOS will boot from the 2nd one.Disks can partially
fail in nasty ways that might allow
Is it possible to install CentOS on a USB Flash Drive. Have boot
sector, / and /boot on USB drive then put /home, etc on a software
raid array of the physical drives.
Thought there used to be motherboards with SDHC slots that you could
use to boot off.
On Fri, Jan 24, 2014 at 4:17 PM, Ljubomir Ljubojevic cen...@plnet.rs wrote:
Doesn't grub need to know the bios disk id for subsequent stages of
the boot and where to find the root filesystem? I think it matters
whether or not bios remaps your 2nd drive to the first id.
GRUB boots first
On 01/25/2014 12:20 AM, Les Mikesell wrote:
On Fri, Jan 24, 2014 at 4:17 PM, Ljubomir Ljubojevic cen...@plnet.rs wrote:
Doesn't grub need to know the bios disk id for subsequent stages of
the boot and where to find the root filesystem? I think it matters
whether or not bios remaps your 2nd
Hi Mark,
I am having an issue where eth1 is throwing some messages and stops
responding. Restarting networking doesn't work and also just bringing
down
eth1 with 'ifdown' doesn't fix it. I have never seen anything like these
messages:
eth1: no IPv6 routers present
r8169
On 1/25/14, Matt matt.mailingli...@gmail.com wrote:
Is it possible to install CentOS on a USB Flash Drive. Have boot
sector, / and /boot on USB drive then put /home, etc on a software
raid array of the physical drives.
Thought there used to be motherboards with SDHC slots that you could
use
23 matches
Mail list logo
