[CentOS-announce] CEBA-2012:1195 CentOS 6 openssl Update

2012-08-23 Thread Johnny Hughes

CentOS Errata and Bugfix Advisory 2012:1195 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-1195.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 


i386:
229ff98b63378930d1ec4e79a099c53909ebb4771f62a79fa3b40a7edab2fecc  
openssl-1.0.0-25.el6_3.1.i686.rpm
71f11efd8e96e954fb0a554e7cc53116d0d4fb3d4ef4e12f7b23d82b4bb2f0b9  
openssl-devel-1.0.0-25.el6_3.1.i686.rpm
87021f4863342784b7459ff4cabd35022bb69ae7dcdab98662936196f4cdcbe8  
openssl-perl-1.0.0-25.el6_3.1.i686.rpm
4d531fcc376715669de0bbcd3e97e517dcef601eb90166de24a2f92ce1c72185  
openssl-static-1.0.0-25.el6_3.1.i686.rpm

x86_64:
229ff98b63378930d1ec4e79a099c53909ebb4771f62a79fa3b40a7edab2fecc  
openssl-1.0.0-25.el6_3.1.i686.rpm
055021efa830257f9d46fdd387b2f2d56abe282d0dacb781d15f76e1fa810068  
openssl-1.0.0-25.el6_3.1.x86_64.rpm
71f11efd8e96e954fb0a554e7cc53116d0d4fb3d4ef4e12f7b23d82b4bb2f0b9  
openssl-devel-1.0.0-25.el6_3.1.i686.rpm
91c2b1eca5834e186cc54e26837d6b8d82f58450ff54c0ccdd6fab5d6e951bd2  
openssl-devel-1.0.0-25.el6_3.1.x86_64.rpm
38b718ba3682b23efe60106ea7fa97e00f953392fb1e3710a36cc090860cb642  
openssl-perl-1.0.0-25.el6_3.1.x86_64.rpm
6cbd2f853026d43e72180341949251ec86f33b033b5c1b9339aeca6949956fc5  
openssl-static-1.0.0-25.el6_3.1.x86_64.rpm

Source:
f0aca17475b5abcb589b5388f59e1ea200c4808c441e86d0a7e2714164517d1b  
openssl-1.0.0-25.el6_3.1.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net

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


[CentOS-announce] CESA-2012:1201 Moderate CentOS 5 tetex Update

2012-08-23 Thread Johnny Hughes

CentOS Errata and Security Advisory 2012:1201 Moderate

Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-1201.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
0564129724071c9d3c33c19bd8a994b80453747f89547d5edf4f8cbb1167fed1  
tetex-3.0-33.15.el5_8.1.i386.rpm
3bf40a29d1c92a76c772ba1c7f83a0af36bdf42cb79a09ad08e7898c712b9014  
tetex-afm-3.0-33.15.el5_8.1.i386.rpm
41808c10844fdbcce8241f93383b8552a4d3516a666fe0923236f739cd6cbcae  
tetex-doc-3.0-33.15.el5_8.1.i386.rpm
1abb7885788c2adbe46117f1e86eaa56075d3a6afae374caa6082a35dae0b5f5  
tetex-dvips-3.0-33.15.el5_8.1.i386.rpm
6d315be666aa954528c32efde8451074edb0c186705a8d58b5e603ce05e05927  
tetex-fonts-3.0-33.15.el5_8.1.i386.rpm
267a3d7b9a965a8b2b4a737738b5a23fdcd80e825dda6ed7168883a390a55212  
tetex-latex-3.0-33.15.el5_8.1.i386.rpm
42ef5e9bde52926e568996bdcce951b49dbf840fe038fc10adb2bf76a0c3e496  
tetex-xdvi-3.0-33.15.el5_8.1.i386.rpm

x86_64:
18de8aa0d8089108d0b6b00a7a6dca23c6ef5e18d578056bf8b19c04116efc21  
tetex-3.0-33.15.el5_8.1.x86_64.rpm
1fb19d69a5d32d86e76cd6ac66d928580c07c8408f648fa33a7d02f3775a5768  
tetex-afm-3.0-33.15.el5_8.1.x86_64.rpm
feed0b7c8b60dd1fecd98f2cf975ba0e9ca19b69e1977aabed3dd9f23c3b3600  
tetex-doc-3.0-33.15.el5_8.1.x86_64.rpm
7f6a0f68b17996f0c907a797db5de29308ed116adf941d26c94db4edc256c5fe  
tetex-dvips-3.0-33.15.el5_8.1.x86_64.rpm
8883e029a1cf9df243ba670ae23f4f1c4ba9ad6d17af1b0d854afb59e9a3a353  
tetex-fonts-3.0-33.15.el5_8.1.x86_64.rpm
b4859d48001cebbfaca912f857815620ee6790ea72fbcf0dcc89bd2e956573af  
tetex-latex-3.0-33.15.el5_8.1.x86_64.rpm
c3153d4a7d531ceac4460f1c46b37639ec47888e461d6ab77db1803be9d94d88  
tetex-xdvi-3.0-33.15.el5_8.1.x86_64.rpm

Source:
d8ed0829ae85d447dc246fd8b41c7c99e25ba6aa7d4ad30c192c185af4ec9663  
tetex-3.0-33.15.el5_8.1.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net

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


[CentOS-announce] CESA-2012:1202 Moderate CentOS 6 libvirt Update

2012-08-23 Thread Johnny Hughes

CentOS Errata and Security Advisory 2012:1202 Moderate

Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-1202.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 


i386:
c86207d53a90797f2659ae93fc74e390ea91865e82b79f19306bbc82296bfbaa  
libvirt-0.9.10-21.el6_3.4.i686.rpm
19707fde2b0258bb63c28306e9b031c5d3be7732b745d63044719f6c77939543  
libvirt-client-0.9.10-21.el6_3.4.i686.rpm
bdfa3bdd638087f209c892fad41dca818a18678a69ed37124941821d1426ef87  
libvirt-devel-0.9.10-21.el6_3.4.i686.rpm
e89174fafbf143612e3b3859d1da36cb858b2655a5dbdb8b95a3d795f746d876  
libvirt-python-0.9.10-21.el6_3.4.i686.rpm

x86_64:
32187f8cfdac84b250ac662683cb11c6a46e9d9231f5d86dfb036ac0bfac2c03  
libvirt-0.9.10-21.el6_3.4.x86_64.rpm
19707fde2b0258bb63c28306e9b031c5d3be7732b745d63044719f6c77939543  
libvirt-client-0.9.10-21.el6_3.4.i686.rpm
d5e2d059a1c4c64b35966b6b689101fa7bed6f8c1382c5df85e082e7220ae959  
libvirt-client-0.9.10-21.el6_3.4.x86_64.rpm
bdfa3bdd638087f209c892fad41dca818a18678a69ed37124941821d1426ef87  
libvirt-devel-0.9.10-21.el6_3.4.i686.rpm
235fe5df23fc24177a86a353ea483f5bcb7cc8640013d87fdf5fcb8a8370f919  
libvirt-devel-0.9.10-21.el6_3.4.x86_64.rpm
73881454d29cfa8277f976888109c26790c78b6f11179040d2054884570cd3f0  
libvirt-lock-sanlock-0.9.10-21.el6_3.4.x86_64.rpm
9c7a65cee4e4a968f316f775ab3c6ad6a5805afa2dedb5eda76cde99cc6ec2ca  
libvirt-python-0.9.10-21.el6_3.4.x86_64.rpm

Source:
e441840625ccef1722752cd3cea17fb049276328875688ac2ac96c2cb44342a2  
libvirt-0.9.10-21.el6_3.4.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net

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


[CentOS-announce] CEBA-2012:1199 CentOS 6 kernel Update

2012-08-23 Thread Johnny Hughes

CentOS Errata and Bugfix Advisory 2012:1199 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-1199.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 


i386:
971ca5387d219d9167c20bce91c25a964edfc52eb45bd988181a28b54f944ddf  
kernel-2.6.32-279.5.2.el6.i686.rpm
71e25ae35b2973fd7a863acc2ff54a69a3eed68848876753db3f60e60428d2e8  
kernel-debug-2.6.32-279.5.2.el6.i686.rpm
7820e1f8c71af460fc1dc050b803954a8b1d966f164b9b50e89fb41025fdc109  
kernel-debug-devel-2.6.32-279.5.2.el6.i686.rpm
06a76df20532bf79a323df53f27c37ad9946ae8651c040833cfb215503342100  
kernel-devel-2.6.32-279.5.2.el6.i686.rpm
b96f379a46859f068185f7e8703e3c1ffbf34a4659fa64f3a95aa6045169ebb6  
kernel-doc-2.6.32-279.5.2.el6.noarch.rpm
538e4dd08461ec62ae6bf1b9da35d32812993748081d9be5ff58f3d2604375b3  
kernel-firmware-2.6.32-279.5.2.el6.noarch.rpm
2934af12898ba1ae339ee050b2eb1fbd97a6ad893d6302a87d8b0053fa33caed  
kernel-headers-2.6.32-279.5.2.el6.i686.rpm
09e4cbd8164eb10963681e85bdb4506f379b59f0d447043c2524ad6747ce00a0  
perf-2.6.32-279.5.2.el6.i686.rpm
7e844898857c93cbafcbde56092543fb42c8f58ff574a936ba17e87c5378ebfa  
python-perf-2.6.32-279.5.2.el6.i686.rpm

x86_64:
8fc09d646ba61ead80cd16cd946d0a40b5baa479157654cb2014ca8a185ca555  
kernel-2.6.32-279.5.2.el6.x86_64.rpm
f72225479b194cd6c1d590b66320e9603735fede0328b8d8ff2148efd3e476ad  
kernel-debug-2.6.32-279.5.2.el6.x86_64.rpm
66066fe52e2cb46378817161fa719c2f40406a047f53bb8ea4165a93a18b42ec  
kernel-debug-devel-2.6.32-279.5.2.el6.x86_64.rpm
66ea3790f30294f11ec53fc369ee2891d21afb01fbf92732f3fed906f2f673d3  
kernel-devel-2.6.32-279.5.2.el6.x86_64.rpm
aec47899356c269bede34a05673c111bd4bebee83de83e2bc3de7e4d08cf32e9  
kernel-doc-2.6.32-279.5.2.el6.noarch.rpm
46a6ec8357341787d87b9b90be9ae3a0436c375e9a1f42b3a5768d72a1d9d6c6  
kernel-firmware-2.6.32-279.5.2.el6.noarch.rpm
119a768658c21bea1cd98b1bdb873b06b043f7f95b6e01a1fd27719711ef10e2  
kernel-headers-2.6.32-279.5.2.el6.x86_64.rpm
f2133df7ccf1ecf1e020e87bb1cfa673de62e91052966e7f609fc9c57cb79dba  
perf-2.6.32-279.5.2.el6.x86_64.rpm
5e0c3b046eddab01f2341697afc6bb5c08930aea6b0f5059e05eb6ae2bb041ef  
python-perf-2.6.32-279.5.2.el6.x86_64.rpm

Source:
d8da378ee1e720c307ee99fd1fa17eb6548b77914031ee0407d8659d84f0b54e  
kernel-2.6.32-279.5.2.el6.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net

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


Re: [CentOS] secure boot.

2012-08-23 Thread James Hogarth
On 23 August 2012 05:51, Jimmy Bradley bmobil...@ocellaris.net wrote:
 I've been reading up some about the new secure boot that's
 coming out on new machines when MS releases Win 8. Has a workaround been
 developed yet for those of us who don't want to run windows? Typically,
 I mostly build my own desktops, and I install cent os right from the
 start, but sometimes I do buy a desktop, and naturally it comes with
 windows on it, so I have to do a wipe and load, to get rid of windows.


On X86 you will be able to disable the secure boot so you can then
install what you want - not such a big deal

It's ARM (which is not currently supported of course) which is the
questionable one...
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] secure boot.

2012-08-23 Thread John Doe
From: Jimmy Bradley bmobil...@ocellaris.net
            I've been reading up some about the new secure boot that's
coming out on new machines when MS releases Win 8. Has a workaround been
developed yet for those of us who don't want to run windows? Typically,
I mostly build my own desktops, and I install cent os right from the
start, but sometimes I do buy a desktop, and naturally it comes with
windows on it, so I have to do a wipe and load, to get rid of windows.

First, the manufacturer can/should decide to let the user enable/disable secure 
boot in the bios...

As for linux, from memory, different distributions chose different paths...
I think RedHat will apparently buy a key from verisign and Canonical has 
decided to use their own key.
I think they need to use non GPL boot loaders (to protect the key I guess), so 
no grub2...


JD

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


[CentOS] Loading drivers during linux rescue

2012-08-23 Thread Jobst Schmalenbach

Hi

I got a new Adaptec 6405 card with a set of new harddrives.
Problem that I assumed that the card had kernel drivers, which it has but only 
from 2.6.39 onwards.

I installed the kmod-aacraid drivers, they see the card and drives, fine.

However, I need to get a linux rescue to work, thus I need to load the 
drivers during the boot of the resuce disk.
How do I do this?

thanks
Jobst



-- 
C is a write-only language.

  | |0| |   Jobst Schmalenbach, jo...@barrett.com.au, General Manager
  | | |0|   Barrett Consulting Group P/L  The Meditation Room P/L
  |0|0|0|   +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] Order of sata/sas raid cards

2012-08-23 Thread Jobst Schmalenbach
Hi.

I bought a new Adaptec 6405 card including new (much larger) SAS drives 
(arrays).

I need to copy content of the current SATA (old adaptec 2405) drives to the new 
SAS drives.

When I put the new controller into the machine, the card is seen and I can see 
that the kernel loads the new drives and the old drives. The problem is that 
the new drives are loaded as SDA and SDB, which then stops the kernel loading, 
becasue it cannot find root and get kernel panic.

Is there a way to tell the kernel in which order to load the drives and assign 
the drive order in a way that the new drives are assigned SDC and SDD and the 
old drives get SDA and SDB?

thanks
Jobst


-- 
Why are a wise man and a wise guy opposites?

  | |0| |   Jobst Schmalenbach, jo...@barrett.com.au, General Manager
  | | |0|   Barrett Consulting Group P/L  The Meditation Room P/L
  |0|0|0|   +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Loading drivers during linux rescue

2012-08-23 Thread John Doe
From: Jobst Schmalenbach jo...@barrett.com.au

 I got a new Adaptec 6405 card with a set of new harddrives.
 Problem that I assumed that the card had kernel drivers, which it has but 
 only 
 from 2.6.39 onwards.
 
 I installed the kmod-aacraid drivers, they see the card and drives, fine.
 
 However, I need to get a linux rescue to work, thus I need to load 
 the drivers during the boot of the resuce disk.
 How do I do this?

Tried adaptec's driver disk?
http://www.adaptec.com/en-us/speed/raid/aac/linux/aacraid_linux_driverdisks_v1_1_7-29100_tgz.htm

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


Re: [CentOS] Order of sata/sas raid cards

2012-08-23 Thread Adrian Sevcenco
On 08/23/12 12:13, Jobst Schmalenbach wrote:
 Is there a way to tell the kernel in which order to load the drives
 and assign the drive order in a way that the new drives are assigned
 SDC and SDD and the old drives get SDA and SDB?
use UUID= in fstab (lsblk -o NAME,KNAME,UUID) and you will get rid of
all this headaches (if you have software raid the assembling is done
internally based on UUID so you don't have to worry about mdraid)

HTH,
Adrian

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


Re: [CentOS] secure boot.

2012-08-23 Thread Dennis Jacobfeuerborn
On 08/23/2012 10:39 AM, John Doe wrote:
 From: Jimmy Bradley bmobil...@ocellaris.net
 I've been reading up some about the new secure boot that's
 coming out on new machines when MS releases Win 8. Has a workaround been
 developed yet for those of us who don't want to run windows? Typically,
 I mostly build my own desktops, and I install cent os right from the
 start, but sometimes I do buy a desktop, and naturally it comes with
 windows on it, so I have to do a wipe and load, to get rid of windows.
 
 First, the manufacturer can/should decide to let the user enable/disable 
 secure boot in the bios...

Actually at least for X86 hardware the Microsoft certification guidelines
*mandate* that the secure boot can be disabled.

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


Re: [CentOS] Order of sata/sas raid cards

2012-08-23 Thread Jobst Schmalenbach
Hi Adrian

yes this will do.
Because I do not know (yet) the UUID of the new partitions (drives), 
if I specify the UUID for the known drives for the partitions
the kernel will assign the new drives to higher sdx?
Is this correct?

thanks
Jobst



On Thu, Aug 23, 2012 at 12:49:38PM +0300, Adrian Sevcenco 
(adrian.sevce...@cern.ch) wrote:
 On 08/23/12 12:13, Jobst Schmalenbach wrote:
  Is there a way to tell the kernel in which order to load the drives
  and assign the drive order in a way that the new drives are assigned
  SDC and SDD and the old drives get SDA and SDB?
 use UUID= in fstab (lsblk -o NAME,KNAME,UUID) and you will get rid of
 all this headaches (if you have software raid the assembling is done
 internally based on UUID so you don't have to worry about mdraid)
 
 HTH,
 Adrian
 


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


-- 
f u cn rd ths, u cn gt a gd jb n cmptr prgmmng. [Anon]

  | |0| |   Jobst Schmalenbach, jo...@barrett.com.au, General Manager
  | | |0|   Barrett Consulting Group P/L  The Meditation Room P/L
  |0|0|0|   +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Loading drivers during linux rescue

2012-08-23 Thread Jobst Schmalenbach
Sorry, maybe I did not give enough information.
I have the drivers from adaptecs site (plus the kmod stuff).

At least once I need to boot the rescue disk to select the
bootpartition and install grub on the new drives, I need to insmod
the drivers, but I do not know where and how to do that during
the boot process of the rescue disk (there is no menu for that).

I have never had to do this before ... in all the years of using Linux ;-)


Jobst




On Thu, Aug 23, 2012 at 02:31:55AM -0700, John Doe (jd...@yahoo.com) wrote:
 From: Jobst Schmalenbach jo...@barrett.com.au
 
  I got a new Adaptec 6405 card with a set of new harddrives.
  Problem that I assumed that the card had kernel drivers, which it has but 
  only 
  from 2.6.39 onwards.
  
  I installed the kmod-aacraid drivers, they see the card and drives, fine.
  
  However, I need to get a linux rescue to work, thus I need to load 
  the drivers during the boot of the resuce disk.
  How do I do this?
 
 Tried adaptec's driver disk?
 http://www.adaptec.com/en-us/speed/raid/aac/linux/aacraid_linux_driverdisks_v1_1_7-29100_tgz.htm
 
 JD
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

-- 
while ( !sorted ) { do_nothing ( ) ; }

  | |0| |   Jobst Schmalenbach, jo...@barrett.com.au, General Manager
  | | |0|   Barrett Consulting Group P/L  The Meditation Room P/L
  |0|0|0|   +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Order of sata/sas raid cards

2012-08-23 Thread Markus Falb
On 23.8.2012 14:01, Jobst Schmalenbach wrote:
 Hi Adrian
 
 yes this will do.
 Because I do not know (yet) the UUID of the new partitions (drives), 
 if I specify the UUID for the known drives for the partitions
 the kernel will assign the new drives to higher sdx?
 Is this correct?

After reboot sdx could be sdy, as you noticed.
The solution: you dont access a drive via /dev/sdx
You access per UUID and the kernel maps it to the appropiate sdXY which
could be sdy after reboot.

I am not sure about initial ramdisks etc. maybe there is hardcoded stuff
to sdx in there. Maybe it has to be rebuilt? Maybe you has to rebuild
initrd as well as updating fstab?
-- 
Kind Regards, Markus Falb



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


Re: [CentOS] Loading drivers during linux rescue

2012-08-23 Thread Stu Watts
Hi Jobst,

I believe you'll need to build a new initrd image and include the driver
modules.  Try http://wiki.centos.org/TipsAndTricks/CreateNewInitrd for a
start.  There are other guides out there too.

Good luck!

Stu

On 23 August 2012 13:08, Jobst Schmalenbach jo...@barrett.com.au wrote:

 Sorry, maybe I did not give enough information.
 I have the drivers from adaptecs site (plus the kmod stuff).

 At least once I need to boot the rescue disk to select the
 bootpartition and install grub on the new drives, I need to insmod
 the drivers, but I do not know where and how to do that during
 the boot process of the rescue disk (there is no menu for that).

 I have never had to do this before ... in all the years of using Linux ;-)


 Jobst




 On Thu, Aug 23, 2012 at 02:31:55AM -0700, John Doe (jd...@yahoo.com)
 wrote:
  From: Jobst Schmalenbach jo...@barrett.com.au
 
   I got a new Adaptec 6405 card with a set of new harddrives.
   Problem that I assumed that the card had kernel drivers, which it has
 but only
   from 2.6.39 onwards.
  
   I installed the kmod-aacraid drivers, they see the card and drives,
 fine.
  
   However, I need to get a linux rescue to work, thus I need to load
   the drivers during the boot of the resuce disk.
   How do I do this?
 
  Tried adaptec's driver disk?
 
 http://www.adaptec.com/en-us/speed/raid/aac/linux/aacraid_linux_driverdisks_v1_1_7-29100_tgz.htm
 
  JD
  ___
  CentOS mailing list
  CentOS@centos.org
  http://lists.centos.org/mailman/listinfo/centos

 --
 while ( !sorted ) { do_nothing ( ) ; }

   | |0| |   Jobst Schmalenbach, jo...@barrett.com.au, General Manager
   | | |0|   Barrett Consulting Group P/L  The Meditation Room P/L
   |0|0|0|   +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos




-- 
Stu

Did I do that deja-vu joke?
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Loading drivers during linux rescue

2012-08-23 Thread John Doe
From: Jobst Schmalenbach jo...@barrett.com.au

 At least once I need to boot the rescue disk to select the
 bootpartition and install grub on the new drives, I need to insmod
 the drivers, but I do not know where and how to do that during
 the boot process of the rescue disk (there is no menu for that).

Look at the dd option in the documentation:
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/ap-rescuemode.html#s1-rescuemode-boot

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


Re: [CentOS] Order of sata/sas raid cards

2012-08-23 Thread m . roth
Markus Falb wrote:
 On 23.8.2012 14:01, Jobst Schmalenbach wrote:
 Hi Adrian

 yes this will do.
 Because I do not know (yet) the UUID of the new partitions (drives),
 if I specify the UUID for the known drives for the partitions
 the kernel will assign the new drives to higher sdx?
 Is this correct?

 After reboot sdx could be sdy, as you noticed.
 The solution: you dont access a drive via /dev/sdx
 You access per UUID and the kernel maps it to the appropiate sdXY which
 could be sdy after reboot.

You can also label it. I loathe UUIDs - there is *no* way you're going to
remember one when you need it. Labels are so much clearer.

 I am not sure about initial ramdisks etc. maybe there is hardcoded stuff
 to sdx in there. Maybe it has to be rebuilt? Maybe you has to rebuild
 initrd as well as updating fstab?

I've actually never seen a system *not* know what the first drive was,
hardware-wise. And grub will point to root hd(0,x), normally, not UUID or
anything else. You *can* (and I do, all the time) use LABEL= on the kernel
line.

  mark

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


Re: [CentOS] Order of sata/sas raid cards

2012-08-23 Thread Adrian Sevcenco
On 08/23/12 15:01, Jobst Schmalenbach wrote:
 Hi Adrian
Hi!

 yes this will do.
 Because I do not know (yet) the UUID of the new partitions (drives), 
 if I specify the UUID for the known drives for the partitions
 the kernel will assign the new drives to higher sdx?
AFAIK the sdX names are given by the bios so this is why when new
hardware is addend and/or something is change hardware-wise the sdX
nomenclature is changed.
If you decide to use UUID nomenclature you should use it for ALL
disks/partitions .. for centos that menas the beside fstab to modify
grub to have something like root=UUID= in kernel command line from grub.
IMHO the easiest way to change all to UUID is to boot a live-cd find out
all UUIDs and modify the fstab and grub accordingly.
I dont know about root(hd0,0) .. i have the grub and / installed on an
disk which by system is recognized as /dev/sdc and in grub.conf i have
hd(2,msdos1)

HTH,
Adrian


 Is this correct?
 
 thanks
 Jobst
 
 
 
 On Thu, Aug 23, 2012 at 12:49:38PM +0300, Adrian Sevcenco 
 (adrian.sevce...@cern.ch) wrote:
 On 08/23/12 12:13, Jobst Schmalenbach wrote:
 Is there a way to tell the kernel in which order to load the drives
 and assign the drive order in a way that the new drives are assigned
 SDC and SDD and the old drives get SDA and SDB?
 use UUID= in fstab (lsblk -o NAME,KNAME,UUID) and you will get rid of
 all this headaches (if you have software raid the assembling is done
 internally based on UUID so you don't have to worry about mdraid)

 HTH,
 Adrian

 
 
 ___
 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] Order of sata/sas raid cards

2012-08-23 Thread m . roth
Adrian Sevcenco wrote:
 On 08/23/12 15:01, Jobst Schmalenbach wrote:
snip
 I dont know about root(hd0,0) .. i have the grub and / installed on an
 disk which by system is recognized as /dev/sdc and in grub.conf i have
 hd(2,msdos1)
snip
I've never seen anything like msdos1 - I assume it's a label, but have
seen nothing suggesting I could do that. At any rate, that's h/d 3, or
presented as the third drive to the BIOS?

 mark


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


Re: [CentOS] Order of sata/sas raid cards

2012-08-23 Thread m . roth
Adrian Sevcenco wrote:
 On 08/23/12 15:01, Jobst Schmalenbach wrote:
snip
 I dont know about root(hd0,0) .. i have the grub and / installed on an
 disk which by system is recognized as /dev/sdc and in grub.conf i have
 hd(2,msdos1)

Ok... to follow myself up, I started looking. There is zero indication in
any manpage about the syntax you use. After doing some googling, I finally
found
http://www.gnu.org/software/grub/manual/grub.html#Device-syntax, and
geez, the Gnu documentation is *dreadful* - why isn't there a syntax
description for the root line of a grub entry? Then I found the above,
which is *not* with the root directive, and they give examples including
msdos1, msdos5, but with no explanation of what those names are - labels?
the first and fifth partitions that are msdos format?

As I said in my previous post, I've never seen anything like that - it's
always
root (hdx,y).

 mark


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


Re: [CentOS] Order of sata/sas raid cards

2012-08-23 Thread Adrian Sevcenco
On 08/23/12 17:41, m.r...@5-cent.us wrote:
 Adrian Sevcenco wrote:
 On 08/23/12 15:01, Jobst Schmalenbach wrote:
 snip
 I dont know about root(hd0,0) .. i have the grub and / installed on an
 disk which by system is recognized as /dev/sdc and in grub.conf i have
 hd(2,msdos1)

 Ok... to follow myself up, I started looking. There is zero indication in
 any manpage about the syntax you use. After doing some googling, I finally
 found
 http://www.gnu.org/software/grub/manual/grub.html#Device-syntax, and
 geez, the Gnu documentation is *dreadful* - why isn't there a syntax
 description for the root line of a grub entry? Then I found the above,
 which is *not* with the root directive, and they give examples including
 msdos1, msdos5, but with no explanation of what those names are - labels?
 the first and fifth partitions that are msdos format?
 
 As I said in my previous post, I've never seen anything like that - it's
 always
 root (hdx,y).
err, sorry that was my mistake ... i copy pasted from wrong terminal
(from my desktop fedora 16 grub 2 instead from the centos server where i
look initially)

so, to wrap things up: on my centos 5 storage i have root (hd0,0)
that stayed the same no matter how many block devices i added or removed
from my hardware card... but in fstab i use only UUIDs

HTH,
Adrian


 
  mark
 
 
 ___
 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] Order of sata/sas raid cards

2012-08-23 Thread m . roth
Adrian Sevcenco wrote:
 On 08/23/12 17:41, m.r...@5-cent.us wrote:
 Adrian Sevcenco wrote:
 On 08/23/12 15:01, Jobst Schmalenbach wrote:
 snip
 I dont know about root(hd0,0) .. i have the grub and / installed on an
 disk which by system is recognized as /dev/sdc and in grub.conf i have
 hd(2,msdos1)

 Ok... to follow myself up, I started looking. There is zero indication
 in any manpage about the syntax you use. After doing some googling, I
 finally found
 http://www.gnu.org/software/grub/manual/grub.html#Device-syntax, and
 geez, the Gnu documentation is *dreadful* - why isn't there a syntax
 description for the root line of a grub entry? Then I found the above,
 which is *not* with the root directive, and they give examples including
 msdos1, msdos5, but with no explanation of what those names are -
 labels? the first and fifth partitions that are msdos format?

 As I said in my previous post, I've never seen anything like that - it's
 always
 root (hdx,y).
 err, sorry that was my mistake ... i copy pasted from wrong terminal
 (from my desktop fedora 16 grub 2 instead from the centos server where i
 look initially)

Oh, no problem. I can't see how you could *possibly* have copied from the
wrong term (says the guy with seven open for use, sudo -s on three, and
one for later use for streaming media)

 so, to wrap things up: on my centos 5 storage i have root (hd0,0)
 that stayed the same no matter how many block devices i added or removed
 from my hardware card... but in fstab i use only UUIDs

Yup, what we've got. As I said, though, I hate UUIDs - for any non-RAIDed
drives, we *always* label them, indicative of where they mount. That way,
we all know what's expected, where a UUID tells you nothing of what it is.

  mark

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


[CentOS] CentOS-announce Digest, Vol 90, Issue 14

2012-08-23 Thread centos-announce-request
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than Re: Contents of CentOS-announce digest...


Today's Topics:

   1. CEBA-2012:1195  CentOS 6 openssl Update (Johnny Hughes)


--

Message: 1
Date: Thu, 23 Aug 2012 13:34:15 +
From: Johnny Hughes joh...@centos.org
Subject: [CentOS-announce] CEBA-2012:1195  CentOS 6 openssl Update
To: centos-annou...@centos.org
Message-ID: 20120823133415.ga12...@chakra.karan.org
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Bugfix Advisory 2012:1195 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-1195.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 


i386:
229ff98b63378930d1ec4e79a099c53909ebb4771f62a79fa3b40a7edab2fecc  
openssl-1.0.0-25.el6_3.1.i686.rpm
71f11efd8e96e954fb0a554e7cc53116d0d4fb3d4ef4e12f7b23d82b4bb2f0b9  
openssl-devel-1.0.0-25.el6_3.1.i686.rpm
87021f4863342784b7459ff4cabd35022bb69ae7dcdab98662936196f4cdcbe8  
openssl-perl-1.0.0-25.el6_3.1.i686.rpm
4d531fcc376715669de0bbcd3e97e517dcef601eb90166de24a2f92ce1c72185  
openssl-static-1.0.0-25.el6_3.1.i686.rpm

x86_64:
229ff98b63378930d1ec4e79a099c53909ebb4771f62a79fa3b40a7edab2fecc  
openssl-1.0.0-25.el6_3.1.i686.rpm
055021efa830257f9d46fdd387b2f2d56abe282d0dacb781d15f76e1fa810068  
openssl-1.0.0-25.el6_3.1.x86_64.rpm
71f11efd8e96e954fb0a554e7cc53116d0d4fb3d4ef4e12f7b23d82b4bb2f0b9  
openssl-devel-1.0.0-25.el6_3.1.i686.rpm
91c2b1eca5834e186cc54e26837d6b8d82f58450ff54c0ccdd6fab5d6e951bd2  
openssl-devel-1.0.0-25.el6_3.1.x86_64.rpm
38b718ba3682b23efe60106ea7fa97e00f953392fb1e3710a36cc090860cb642  
openssl-perl-1.0.0-25.el6_3.1.x86_64.rpm
6cbd2f853026d43e72180341949251ec86f33b033b5c1b9339aeca6949956fc5  
openssl-static-1.0.0-25.el6_3.1.x86_64.rpm

Source:
f0aca17475b5abcb589b5388f59e1ea200c4808c441e86d0a7e2714164517d1b  
openssl-1.0.0-25.el6_3.1.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net



--

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


End of CentOS-announce Digest, Vol 90, Issue 14
***
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] tigervnc-server-module crashes after EL 6.3 update

2012-08-23 Thread Cal Webster
On Fri, 2012-08-17 at 19:46 -0500, Johnny Hughes wrote:
 On 08/17/2012 01:40 PM, Cal Webster wrote:
  On Thu, 2012-08-16 at 17:01 -0500, Johnny Hughes wrote:
  On 08/16/2012 11:43 AM, Cal Webster wrote:
  On Wed, 2012-08-15 at 13:56 -0500, Johnny Hughes wrote:
  On 08/15/2012 09:47 AM, Cal Webster wrote:
  On Tue, 2012-08-14 at 20:55 -0500, Johnny Hughes wrote:
  On 08/14/2012 05:23 PM, Cal Webster wrote:
  We began experiencing failed vnc connections to the console display on
  servers that have been updated to EL 6.3. No such failures have 
  occurred
  on similar connections to EL 6.2 servers.
 
  On the client machine a normal vncviewer display appears with the
  expected graphical login until the mouse pointer is moved within the
  boundaries of the vncviewer window. At this point the window closes 
  and
  an error message appears in both a pop-up window and in the terminal
  window in which the session was initiated stating read: Connection
  reset by peer (104).
 
  On the server end, a core dump is generated and a abrt bug report is
  created.
 
  /var/log/messages
  --
  Aug 14 11:00:30 jato2 abrt[11411]: File '/usr/bin/Xorg' seems to be
  deleted
  Aug 14 11:00:30 jato2 abrt[11411]: Saved core dump of pid 7892
  (/usr/bin/Xorg) to /var/spool/abrt/ccpp-2012-08-14-11:00:30-7892
  (42041344 bytes)
  Aug 14 11:00:30 jato2 abrtd: Directory 'ccpp-2012-08-14-11:00:30-7892'
  creation detected
  --
 
  This bug has been reported in the CentOS bug tracker here:
 
  0005824: tigervnc-server-module keep crashing
  http://bugs.centos.org/view.php?id=5824
 
  However, this appears to be a bug upstream. The source RPM provided 
  with
  CentOS is identical to that of upstream with no modifications. Also,
  there is an upstream bug reported that appears to have the same
  symptoms. I have added a comment to the upstream bug report (listed
  below) if anyone wishes to see the details.
 
  tigervnc-server-module crashes with dual screen setup
  https://bugzilla.redhat.com/show_bug.cgi?id=820443
 
 
 
  We have verified that rebuilding the unmodified source RPM for 
  tigervnc
  produces a tigervnc-server-module RPM that does not suffer from this
  bug.
 
  Removing the original tigervnc-server-module package and replacing it
  with the rebuilt one fixes the problem.
 
  I've duplicated the problem on 2 EL 6.3 x86_64 single-head display
  machines and have verified the fix.
 
  Tomorrow, I'll duplicate the problem on a dual-head x86_64 machine 
  that
  currently still works after updating to EL 6.2 then confirm the the 
  fix.
 
  Did you rebuild the SRPM using mock or directly on a physical machine
  with rpmbuild?
  No mock, just a simple rpmbuild -ba SPEC/tigervnc.spec
  OK, if you find that this solves your problems for sure, I will build
  the SRPM outside of mock and see if it is different.
  I've confirmed the same faulty behavior for the update to 6.3 on our
  dual-head systems.
 
  Also confirmed is that replacing the 6.3 base tigervnc-server-module rpm
  with the rebuilt one does fix the problem on the dual-head systems.
 
  One disturbing difference between single and dual headed systems is that
  on the dual-head systems Xorg generates a core dump and completely
  freezes up when the mouse movement is detected. Single-head systems just
  fail to connect. This complication could be somehow caused by our
  proprietary ATI FirePro 2270 drivers, though. Once the rebuilt module
  is installed the systems run fine.
 
  I've also updated the upstream bug report.
  can you see if either or both of these work for you:
 
  http://people.centos.org/hughesjr/tigervnc/
 
  One set was built inside of mock, the other outside of mock in a virtual
  machine with only the build requirements of the SRPM installed.
  Both builds work without problems on single and dual-head systems here.
  As with all the other tests, I only replaced the tigervnc-server-module
  package on each host.
 
  I've also confirmed that i686 platforms suffer from the same bug. These
  too, however, are easily remedied by replacing the base
  tigervnc-server-module RPM with a locally re-build one.
 
 Would you also test that these work:
 
 http://people.centos.org/hughesjr/tigervnc/
 
 (same link, newer files :D)
 
 NOTE:  It is CentOS policy that we do not correct upstream bugs in our
 distributions directly ... therefore these will not be released into the
 main distro until upstream releases an update.  I know that is a PITA
 for people, however, it is our policy and we can't break it.

Sorry Johnny. I've been deep in some internal issues past few days -
Migration planning for Win7, building out new CentOS 6 servers, and
such. 

I'll be happy to test these.

./Cal

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


Re: [CentOS] tigervnc-server-module crashes after EL 6.3 update

2012-08-23 Thread Cal Webster
On Fri, 2012-08-17 at 19:46 -0500, Johnny Hughes wrote:
 On 08/17/2012 01:40 PM, Cal Webster wrote:
  On Thu, 2012-08-16 at 17:01 -0500, Johnny Hughes wrote:
  On 08/16/2012 11:43 AM, Cal Webster wrote:
  On Wed, 2012-08-15 at 13:56 -0500, Johnny Hughes wrote:
  On 08/15/2012 09:47 AM, Cal Webster wrote:
  On Tue, 2012-08-14 at 20:55 -0500, Johnny Hughes wrote:
  On 08/14/2012 05:23 PM, Cal Webster wrote:
  We began experiencing failed vnc connections to the console display on
  servers that have been updated to EL 6.3. No such failures have 
  occurred
  on similar connections to EL 6.2 servers.
 
  On the client machine a normal vncviewer display appears with the
  expected graphical login until the mouse pointer is moved within the
  boundaries of the vncviewer window. At this point the window closes 
  and
  an error message appears in both a pop-up window and in the terminal
  window in which the session was initiated stating read: Connection
  reset by peer (104).
 
  On the server end, a core dump is generated and a abrt bug report is
  created.
 
  /var/log/messages
  --
  Aug 14 11:00:30 jato2 abrt[11411]: File '/usr/bin/Xorg' seems to be
  deleted
  Aug 14 11:00:30 jato2 abrt[11411]: Saved core dump of pid 7892
  (/usr/bin/Xorg) to /var/spool/abrt/ccpp-2012-08-14-11:00:30-7892
  (42041344 bytes)
  Aug 14 11:00:30 jato2 abrtd: Directory 'ccpp-2012-08-14-11:00:30-7892'
  creation detected
  --
 
  This bug has been reported in the CentOS bug tracker here:
 
  0005824: tigervnc-server-module keep crashing
  http://bugs.centos.org/view.php?id=5824
 
  However, this appears to be a bug upstream. The source RPM provided 
  with
  CentOS is identical to that of upstream with no modifications. Also,
  there is an upstream bug reported that appears to have the same
  symptoms. I have added a comment to the upstream bug report (listed
  below) if anyone wishes to see the details.
 
  tigervnc-server-module crashes with dual screen setup
  https://bugzilla.redhat.com/show_bug.cgi?id=820443
 
 
 
  We have verified that rebuilding the unmodified source RPM for 
  tigervnc
  produces a tigervnc-server-module RPM that does not suffer from this
  bug.
 
  Removing the original tigervnc-server-module package and replacing it
  with the rebuilt one fixes the problem.
 
  I've duplicated the problem on 2 EL 6.3 x86_64 single-head display
  machines and have verified the fix.
 
  Tomorrow, I'll duplicate the problem on a dual-head x86_64 machine 
  that
  currently still works after updating to EL 6.2 then confirm the the 
  fix.
 
  Did you rebuild the SRPM using mock or directly on a physical machine
  with rpmbuild?
  No mock, just a simple rpmbuild -ba SPEC/tigervnc.spec
  OK, if you find that this solves your problems for sure, I will build
  the SRPM outside of mock and see if it is different.
  I've confirmed the same faulty behavior for the update to 6.3 on our
  dual-head systems.
 
  Also confirmed is that replacing the 6.3 base tigervnc-server-module rpm
  with the rebuilt one does fix the problem on the dual-head systems.
 
  One disturbing difference between single and dual headed systems is that
  on the dual-head systems Xorg generates a core dump and completely
  freezes up when the mouse movement is detected. Single-head systems just
  fail to connect. This complication could be somehow caused by our
  proprietary ATI FirePro 2270 drivers, though. Once the rebuilt module
  is installed the systems run fine.
 
  I've also updated the upstream bug report.
  can you see if either or both of these work for you:
 
  http://people.centos.org/hughesjr/tigervnc/
 
  One set was built inside of mock, the other outside of mock in a virtual
  machine with only the build requirements of the SRPM installed.
  Both builds work without problems on single and dual-head systems here.
  As with all the other tests, I only replaced the tigervnc-server-module
  package on each host.
 
  I've also confirmed that i686 platforms suffer from the same bug. These
  too, however, are easily remedied by replacing the base
  tigervnc-server-module RPM with a locally re-build one.
 
 Would you also test that these work:
 
 http://people.centos.org/hughesjr/tigervnc/
 
 (same link, newer files :D)
 
 NOTE:  It is CentOS policy that we do not correct upstream bugs in our
 distributions directly ... therefore these will not be released into the
 main distro until upstream releases an update.  I know that is a PITA
 for people, however, it is our policy and we can't break it.

I haven't heard anyone on this list verify that the problem does, in
fact, exist on RHEL 6. It would be nice to confirm this is an upstream
bug versus a packaging issue with CentOS. If there are members here with
mixed upstream and CentOS environments, such confirmation would be
welcome. We just allowed the last of our entitlements to expire so I
can't do it here.

./Cal


Re: [CentOS] Centos machine sometimes unreachable

2012-08-23 Thread Richard Reina
2012/8/22 Les Mikesell lesmikes...@gmail.com

 On Wed, Aug 22, 2012 at 8:01 AM, Richard Reina gatorre...@gmail.com
 wrote:
  I have a simple perl script that every few hours pings the handful of
  machines on my LAN. Lately I've sometimes been getting
 
  ping of 192.168.0.1 succeeded
  ping of 192.168.0.7 succeeded
  ping of 192.168.0.5 FAILED
  ping of 192.168.0.6 succeeded
  ping of 192.168.0.9 succeeded
 
This machine in question has been running Centos faithfully for about
 six
  years and no recent changes to it have been made. When I try and ping the
  machine manually it works.   /var/og/messages does not seem irregular.
 Does
  anyone know know what might be the problem or what else I might check?
 

 What does ethtool say about your duplex setting


Here is the output from ethtool

 Settings for eth0:
 Supported ports: [ TP MII ]
 Supported link modes:   10baseT/Half 10baseT/Full
 100baseT/Half 100baseT/Full
 Supports auto-negotiation: Yes
 Advertised link modes:  10baseT/Half 10baseT/Full
 100baseT/Half 100baseT/Full
 Advertised auto-negotiation: Yes
 Speed: 100Mb/s
 Duplex: Full
 Port: MII
 PHYAD: 1
 Transceiver: internal
 Auto-negotiation: on
 Supports Wake-on: g
 Wake-on: g
 Current message level: 0x0007 (7)
 Link detected: yes

THe switch is a linksys etherfast 3124 that has worked perfectly for 10
years. I don't know anything about it's settings. This is a LAN with about
a dozen machines.

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


[CentOS] Gambas Compile on Any Version of Centos

2012-08-23 Thread Casey Kemp
I've unsuccessfully been attempting to get Gambas to compile on Centos 5.8. 
I've seen comment that it also doesn't compile on Centos 6.2. Has anyone gotten 
a successful compile of Gambas on any version of Centos. I'd greatly appreciate 
hearing from you.


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


[CentOS] System will not boot - faulty fstab?

2012-08-23 Thread James B. Byrne
I believe that I made a boo boo recently when recovering some unused
disk space.  Without going into painfully embarrassing detail I need
to delete an entry in fstab for a now non-existent logical volume.

The system reports that the there is a bad superblock for said logical
volume.  Mainly I expect because there isn't one anymore. How do I
edit fstab so as to remove the mount request?  For some reason the
system will not boot from the cdrom and the I for interactive option
is just blown by when the HDD boot starts.


-- 
***  E-Mail is NOT a SECURE channel  ***
James B. Byrnemailto:byrn...@harte-lyne.ca
Harte  Lyne Limited  http://www.harte-lyne.ca
9 Brockley Drive  vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada  L8E 3C3

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


Re: [CentOS] System will not boot - faulty fstab?

2012-08-23 Thread Ross Cavanagh
On Fri, Aug 24, 2012 at 7:17 AM, James B. Byrne byrn...@harte-lyne.cawrote:

 I believe that I made a boo boo recently when recovering some unused
 disk space.  Without going into painfully embarrassing detail I need
 to delete an entry in fstab for a now non-existent logical volume.

 The system reports that the there is a bad superblock for said logical
 volume.  Mainly I expect because there isn't one anymore. How do I
 edit fstab so as to remove the mount request?  For some reason the
 system will not boot from the cdrom and the I for interactive option
 is just blown by when the HDD boot starts.


Can you have some other rescue device besides the CD then, can you boot to
USB and create a rescue disk image onto USB and then go and edit it?
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] System will not boot - faulty fstab?

2012-08-23 Thread Ross Cavanagh
On Fri, Aug 24, 2012 at 7:39 AM, Ross Cavanagh ross@gmail.com wrote:

  On Fri, Aug 24, 2012 at 7:17 AM, James B. Byrne byrn...@harte-lyne.cawrote:

 I believe that I made a boo boo recently when recovering some unused
 disk space.  Without going into painfully embarrassing detail I need
 to delete an entry in fstab for a now non-existent logical volume.

 The system reports that the there is a bad superblock for said logical
 volume.  Mainly I expect because there isn't one anymore. How do I
 edit fstab so as to remove the mount request?  For some reason the
 system will not boot from the cdrom and the I for interactive option
 is just blown by when the HDD boot starts.


 Can you have some other rescue device besides the CD then, can you boot to
 USB and create a rescue disk image onto USB and then go and edit it?


Or pull the disk out if you have to and mount it on another system?
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] secure boot.

2012-08-23 Thread Mark LaPierre
On 08/23/2012 06:56 AM, Dennis Jacobfeuerborn wrote:
 On 08/23/2012 10:39 AM, John Doe wrote:
 From: Jimmy Bradleybmobil...@ocellaris.net
  I've been reading up some about the new secure boot that's
 coming out on new machines when MS releases Win 8. Has a workaround been
 developed yet for those of us who don't want to run windows? Typically,
 I mostly build my own desktops, and I install cent os right from the
 start, but sometimes I do buy a desktop, and naturally it comes with
 windows on it, so I have to do a wipe and load, to get rid of windows.

 First, the manufacturer can/should decide to let the user enable/disable 
 secure boot in the bios...

 Actually at least for X86 hardware the Microsoft certification guidelines
 *mandate* that the secure boot can be disabled.

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


So I gather that MS plans to abandon the X86 platform and move over to 
supporting ARM.  They think, Let Linux have the X86.  It will die after 
we abandon it leaving them with nothing to run on.  The evil empire lives.

-- 
 _
°v°
   /(_)\
^ ^  Mark LaPierre
Registerd Linux user No #267004
www.counter.li.org

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


Re: [CentOS] System will not boot - faulty fstab?

2012-08-23 Thread James B. Byrne

On Thu, August 23, 2012 18:17, James B. Byrne wrote:
 I believe that I made a boo boo recently when recovering some unused
 disk space.  Without going into painfully embarrassing detail I need
 to delete an entry in fstab for a now non-existent logical volume.

 The system reports that the there is a bad superblock for said logical
 volume.  Mainly I expect because there isn't one anymore. How do I
 edit fstab so as to remove the mount request?  For some reason the
 system will not boot from the cdrom and the I for interactive option
 is just blown by when the HDD boot starts.

I discovered the problem with the cd-rom.  It is just that, a cd-rom,
and I was trying to boot from a dvd rescue disk. I have corrected that
problem, edited fstab, and rebooted the system, apparently with
success, so far.


-- 
***  E-Mail is NOT a SECURE channel  ***
James B. Byrnemailto:byrn...@harte-lyne.ca
Harte  Lyne Limited  http://www.harte-lyne.ca
9 Brockley Drive  vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada  L8E 3C3

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


Re: [CentOS] Order of sata/sas raid cards

2012-08-23 Thread Jobst Schmalenbach


I agree with the UUID stuff, I do not like them for the exact same reason.
I do not understand why RedHat cannot include the partition into the UUID,
e.g.

  dev-sda1-c05e-449a-837b-b2579b949d55

As for the first drive, when the kernel boots I think it assigns the
drives in order of the controller on the system bus/slots. As the new controller
sits lower in the slot system (i.e. closer to the CPUs) it is recognised first 
as
I can see it appearing first in the order being initialized by the kernel.
I cant move it below the old card as there is no slot that has the correct 
PCI-x8.

I will try the LABEL way of doing 

I remember that was the same problem a few years back when one had multiple
network interfaces  until the MAC addresses where introduced into the ifcfg 
files.

Jobst



On Thu, Aug 23, 2012 at 09:40:24AM -0400, m.r...@5-cent.us (m.r...@5-cent.us) 
wrote:
 Markus Falb wrote:
  On 23.8.2012 14:01, Jobst Schmalenbach wrote:
  Hi Adrian
 
  yes this will do.
  Because I do not know (yet) the UUID of the new partitions (drives),
  if I specify the UUID for the known drives for the partitions
  the kernel will assign the new drives to higher sdx?
  Is this correct?
 
  After reboot sdx could be sdy, as you noticed.
  The solution: you dont access a drive via /dev/sdx
  You access per UUID and the kernel maps it to the appropiate sdXY which
  could be sdy after reboot.
 
 You can also label it. I loathe UUIDs - there is *no* way you're going to
 remember one when you need it. Labels are so much clearer.
 
  I am not sure about initial ramdisks etc. maybe there is hardcoded stuff
  to sdx in there. Maybe it has to be rebuilt? Maybe you has to rebuild
  initrd as well as updating fstab?
 
 I've actually never seen a system *not* know what the first drive was,
 hardware-wise. And grub will point to root hd(0,x), normally, not UUID or
 anything else. You *can* (and I do, all the time) use LABEL= on the kernel
 line.
 
   mark
 
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

-- 
When the Pope visits a country he really likes, does he french kiss the 
ground?

  | |0| |   Jobst Schmalenbach, jo...@barrett.com.au, General Manager
  | | |0|   Barrett Consulting Group P/L  The Meditation Room P/L
  |0|0|0|   +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Order of sata/sas raid cards

2012-08-23 Thread John R Pierce
On 08/23/12 4:15 PM, Jobst Schmalenbach wrote:
 I will try the LABEL way of doing 

the problem with labels, there's no guarantee they will be unique.  the 
default labels that the centos installer uses are the same on every 
system, so if you plug a drive into another computer, the odds are 
pretty high there will be a collision.

-- 
john r pierceN 37, W 122
santa cruz ca mid-left coast

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