[CentOS-announce] CESA-2012:0715 Critical CentOS 5 thunderbird Update
CentOS Errata and Security Advisory 2012:0715 Critical
Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0715.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
6bf79e5cac8fc2edf5ddd0ea3eb9b8f59856ccef9d2e3f9532717420a4bea844
thunderbird-10.0.5-2.el5.centos.i386.rpm
x86_64:
31f5fbeaba9516065a1e96069b9db0c033c35ffebca84b40e91d5ed14905ea28
thunderbird-10.0.5-2.el5.centos.x86_64.rpm
Source:
492c542a791f9c5cae5af3026594e5e6a94d11010d5a34ca8a63867b6185a6d8
thunderbird-10.0.5-2.el5.centos.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:0715 Critical CentOS 6 thunderbird Update
CentOS Errata and Security Advisory 2012:0715 Critical
Upstream details at : http://rhn.redhat.com/errata/RHSA-2012-0715.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
a6c2d89df73766c12a2f49fc744382ad6abfd251ad6f9de10b5ec551fe1977ce
thunderbird-10.0.5-2.el6.centos.i686.rpm
x86_64:
4f3b26e0947e4611551bbb19491f6263b7493a9fbcdd347333a5552514c25fef
thunderbird-10.0.5-2.el6.centos.x86_64.rpm
Source:
159c10043424925479cc0bc79ec1139f6da9f1270bc86388bdf1cf3ae628c187
thunderbird-10.0.5-2.el6.centos.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:0717 Important CentOS 5 bind97 Update
CentOS Errata and Security Advisory 2012:0717 Important
Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0717.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
2b9b6c83fc41075777d1571201e7a1c88eb44a3a137b19b10d5891c731e18d3d
bind97-9.7.0-10.P2.el5_8.1.i386.rpm
9cd7c8ef84dd48ecbfa497c7cc9a5b18852f4c06d246bf5937db6bd53271db4d
bind97-chroot-9.7.0-10.P2.el5_8.1.i386.rpm
c231140964ec0ab35407d6eeb2887c2b0096460bec68d2ce15772acdc7d66932
bind97-devel-9.7.0-10.P2.el5_8.1.i386.rpm
a7447f529de7315ead9a05983d355be900d83870f143fbdcb712ec0a0e30813e
bind97-libs-9.7.0-10.P2.el5_8.1.i386.rpm
f2a40630eda6b048fdad3cc3a4358456eb37ab613ece602014b04c0a891c8ac8
bind97-utils-9.7.0-10.P2.el5_8.1.i386.rpm
x86_64:
1d1a3f2e1006da35bcce3a8ddfe2b2e0ef4358b935602610091859d4623a8450
bind97-9.7.0-10.P2.el5_8.1.x86_64.rpm
6438ee28377db46dd744c013d909aacee1a7bd58677aa88d430ec42371505ff2
bind97-chroot-9.7.0-10.P2.el5_8.1.x86_64.rpm
c231140964ec0ab35407d6eeb2887c2b0096460bec68d2ce15772acdc7d66932
bind97-devel-9.7.0-10.P2.el5_8.1.i386.rpm
bcab3bed2e2be8cf33554db1d8d6a7090af0bb6e6092f56e6bfb758ff17451ef
bind97-devel-9.7.0-10.P2.el5_8.1.x86_64.rpm
a7447f529de7315ead9a05983d355be900d83870f143fbdcb712ec0a0e30813e
bind97-libs-9.7.0-10.P2.el5_8.1.i386.rpm
2cf8f66d57a2bafd3ce19445e915347a3b5965c0141e676ec99eca4c2c3007fe
bind97-libs-9.7.0-10.P2.el5_8.1.x86_64.rpm
521102f0597bfc5cf47b2d0ece9ce5478ad387f773392cbc3a7870840df65624
bind97-utils-9.7.0-10.P2.el5_8.1.x86_64.rpm
Source:
ac9d2233f649da230376ddb9a0cd226f35dbfa2f9a411c7d000c7dbbe859dfca
bind97-9.7.0-10.P2.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:0716 Important CentOS 5 bind Update
CentOS Errata and Security Advisory 2012:0716 Important
Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0716.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
e77741388e628e6f5d5ef07c11e999b58d51f3554594d2551da58a57d5d189e8
bind-9.3.6-20.P1.el5_8.1.i386.rpm
9544267342a5aabb7714607bc7979e55bcb61cc561f4136b725b5c56adcb2614
bind-chroot-9.3.6-20.P1.el5_8.1.i386.rpm
72c8171cab0a3d0c18d1981eb8403469a9ef45265321bfc1d662098fcb65
bind-devel-9.3.6-20.P1.el5_8.1.i386.rpm
0fa7194e0eee3fe17a0bd9d5d9e4beb16a9bbb1b244454773729a90810cb381d
bind-libbind-devel-9.3.6-20.P1.el5_8.1.i386.rpm
5e33cf76249fdef29735f2f37890136c9d9cb525d28230e73a0f6f4b21cce958
bind-libs-9.3.6-20.P1.el5_8.1.i386.rpm
6b8ee07523c01ee8fc9813390fe118982ef4c89de94c50e192995404b1de9081
bind-sdb-9.3.6-20.P1.el5_8.1.i386.rpm
7875d70c531bb1c28b5a374a0b3609a9fa38043c919206cd2fe6343bfadf61be
bind-utils-9.3.6-20.P1.el5_8.1.i386.rpm
1e9ff807dea89f7718a655df290e5f3e25b2fd40e351593ff5a46c4ac6bea870
caching-nameserver-9.3.6-20.P1.el5_8.1.i386.rpm
x86_64:
8280005de8fd86901d2e779f3991c80854a26e69359f35f94eb55dc84fee39b2
bind-9.3.6-20.P1.el5_8.1.x86_64.rpm
9509c40f89c9f4e08df2ce205eb433078f880b21167da36770cabbb941f54724
bind-chroot-9.3.6-20.P1.el5_8.1.x86_64.rpm
72c8171cab0a3d0c18d1981eb8403469a9ef45265321bfc1d662098fcb65
bind-devel-9.3.6-20.P1.el5_8.1.i386.rpm
ce6fe0b2bcd7332a66ed2a84ce810562eaa454a0cd4d6fcaf6492aab992d3244
bind-devel-9.3.6-20.P1.el5_8.1.x86_64.rpm
0fa7194e0eee3fe17a0bd9d5d9e4beb16a9bbb1b244454773729a90810cb381d
bind-libbind-devel-9.3.6-20.P1.el5_8.1.i386.rpm
4cd6e54330bcafef627f62ea30efbca7e10cf668e096b4f4c62f242cb1abf18c
bind-libbind-devel-9.3.6-20.P1.el5_8.1.x86_64.rpm
5e33cf76249fdef29735f2f37890136c9d9cb525d28230e73a0f6f4b21cce958
bind-libs-9.3.6-20.P1.el5_8.1.i386.rpm
4a5ac3dae1ac63722f2a65686be8ac966a30de69ef74d76c2696297b95b040ac
bind-libs-9.3.6-20.P1.el5_8.1.x86_64.rpm
a07f61dc78e390c8cc709c1ac56cdd797657ffc9916d3e98d3b287c53b55fc6f
bind-sdb-9.3.6-20.P1.el5_8.1.x86_64.rpm
8b22daca4e19d687432094fe9caf81b8d8203b362289f81cb8c59d3b49a0c8f2
bind-utils-9.3.6-20.P1.el5_8.1.x86_64.rpm
965cdee27c7a5b4aa3623ebef96dfb09db035b8e99063ff2c38ebabb69f4901d
caching-nameserver-9.3.6-20.P1.el5_8.1.x86_64.rpm
Source:
02788f487ba600dbb39ac972a6383ebf4136678ff8896fc77b46e01af7aeac69
bind-9.3.6-20.P1.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:0716 Important CentOS 6 bind Update
CentOS Errata and Security Advisory 2012:0716 Important
Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0716.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
081b3e564fa77e8042355bf02848a1384b8321391e19d11d1348a8c3b220a72d
bind-9.7.3-8.P3.el6_2.3.i686.rpm
bac48abad13d32c664a68e8730558e65a2ed280d732fc6db37109efa502a7a0f
bind-chroot-9.7.3-8.P3.el6_2.3.i686.rpm
2d2debcbb81feac2ca95aed1dd8d0d138ac1ec65cc752b4a3c020f17e6601938
bind-devel-9.7.3-8.P3.el6_2.3.i686.rpm
b450fbefc48d5c6fe9e624fb54f5df46b03e02a9eb69da2cc019e6d00e160600
bind-libs-9.7.3-8.P3.el6_2.3.i686.rpm
48917fd1680a3ce07a2e5760f1d2eee9335301c1c86884b5a65dccc052bf53c8
bind-sdb-9.7.3-8.P3.el6_2.3.i686.rpm
342be62081582d5538ef6c7f74d5a7239be2eb293e6780e79872be28cdd1ce05
bind-utils-9.7.3-8.P3.el6_2.3.i686.rpm
x86_64:
7e36254c2830868c4555ad564a25b562f48548ecf9b952beefa4354bb05c02f3
bind-9.7.3-8.P3.el6_2.3.x86_64.rpm
c6a565e300c2359090febca013f6240435d28976acf8e33685f7a15cca255100
bind-chroot-9.7.3-8.P3.el6_2.3.x86_64.rpm
2d2debcbb81feac2ca95aed1dd8d0d138ac1ec65cc752b4a3c020f17e6601938
bind-devel-9.7.3-8.P3.el6_2.3.i686.rpm
1cb45a52030eff6da500e0716c0d0e1860b40b2d5a8b1f5fc5f252ed92bbf101
bind-devel-9.7.3-8.P3.el6_2.3.x86_64.rpm
b450fbefc48d5c6fe9e624fb54f5df46b03e02a9eb69da2cc019e6d00e160600
bind-libs-9.7.3-8.P3.el6_2.3.i686.rpm
1d394744ea456c996cbbb4e8edf5742b67bccc36e376d2ae10df2277412f0faa
bind-libs-9.7.3-8.P3.el6_2.3.x86_64.rpm
4513cb91c85a818b1a1719ef4141559102a1eeea29c8294c615ef3196cded645
bind-sdb-9.7.3-8.P3.el6_2.3.x86_64.rpm
3d4739b13cf9b6993e52ffed100be8086571940369f3203ca2c88cd52caf2c2f
bind-utils-9.7.3-8.P3.el6_2.3.x86_64.rpm
Source:
387212f6401f4d14939be846fdae6d898cc80f65a74044ebf893265a08228b31
bind-9.7.3-8.P3.el6_2.3.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] noexec tmp directory
Hi, On Thursday, June 7, 2012 at 2:09 PM, Bob Hoffman wrote: Hello, I am fixing up a system for someone and they did not make a separate partition for /tmp...but I want to make it noexec, nosuid. I came across a site that said I could skip all the mount/unmount and new partition stuff (which would probably include downsizing a lvm to make room for it)... by adding this in fstab /tmp /tmp bind nosuid,noexec,bind 0 0 and then reboot... There is no /tmp in their fstab at the moment and I am afraid to test this Is this a correct workaround to mount that folder as noexec? OR was this site wrong? That should work. But maybe it’s better to create a test machine/VM and try it there. Or, don’t edit your fstab (yet). Just do it live and see if it worked: # mount --bind /tmp /tmp # mount -o remount,nosuid,noexec /tmp That way, you know it’ll be back to the old settings when you reboot. HTH, -- - Edo - mailto:ml2ed...@gmail.com “May a stranger, and not your own mouth, praise you; may a foreigner, and not your own lips, do so.”—Pro. 27:2 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] mdadm: failed to write superblock to
Hello, i have a little problem. Our server has an broken RAID. # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sda1[2](F) sdb1[1] 2096064 blocks [2/1] [_U] md2 : active raid1 sda3[2](F) sdb3[1] 1462516672 blocks [2/1] [_U] md1 : active raid1 sda2[0] sdb2[1] 524224 blocks [2/2] [UU] unused devices: none I have remove the partition: # mdadm --remove /dev/md0 /dev/sda1 mdadm: hot removed /dev/sda1 from /dev/md0 # mdadm --remove /dev/md2 /dev/sda3 mdadm: hot removed /dev/sda3 from /dev/md2 Now i want to add the old partition (to sync the raid), unfortunately, comes an error message: # mdadm --add /dev/md0 /dev/sda1 mdadm: failed to write superblock to /dev/sda1 What is wrong here? Here some more details: # mdadm --detail /dev/md0 /dev/md0: Version : 0.90 Creation Time : Fri Sep 2 12:38:17 2011 Raid Level : raid1 Array Size : 2096064 (2047.28 MiB 2146.37 MB) Used Dev Size : 2096064 (2047.28 MiB 2146.37 MB) Raid Devices : 2 Total Devices : 1 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Thu Jun 7 08:57:12 2012 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 UUID : 9beaf2eb:4b5c7416:776c2c25:004bd7b2 Events : 0.147 Number Major Minor RaidDevice State 0 000 removed 1 8 171 active sync /dev/sdb1 Thanks Sebastian ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Installing QEMU without KVM
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm developing some kernel module, so i need a stand alone qemu to test my kernel. But yum install qemu fails. After yum search qemu , i get this : gpxe-roms-qemu.noarch : Network boot loader roms supported by QEMU, .rom format qemu-img.x86_64 : QEMU command line tool for manipulating disk images libvirt-lock-sanlock.x86_64 : Sanlock lock manager plugin for QEMU driver qemu-kvm.x86_64 : Userspace component of KVM qemu-kvm-tools.x86_64 : KVM debugging and diagnostics tools sheepdog.x86_64 : The Sheepdog Distributed Storage System for KVM/QEMU vios-proxy.x86_64 : Network proxy between a QEMU host and QEMU guests using : virtioserial channels vios-proxy-guest.x86_64 : Network proxy using virtioserial for QEMU guest vios-proxy-host.x86_64 : Network proxy using virtioserial for QEMU host But i do not need KVM or anything. I just need a stand alone qemu. I then enabled optional repos like EPEL, RPMFUSION, RPMFORGE etc. Although i've seen a qemu in rpmforge, still yum install qemu does not work. I can build qemu from source, but i like installing packages from repositories. Thanks in advance. Cheers. - -- - -aft -BEGIN PGP SIGNATURE- Version: OpenPGP.js v0.1 Comment: http://openpgpjs.org wsBcBAEBAgAQBQJP0IQrCRCJVJ6A/SK8awAAUN8H/jb2hXDAfMQilyZ5ZP1R d5Cyl0710LHTnGJhZ2+2KZEDrnhx1c07L1atQc663rOILBZge6cpfQJkQkT3 LTKOudzrCA/04FyvBPqApO3p39CLEHjYlJ14TU9sAHODlDvENx1S/kWBBxPk r3mKJ7ODwiXoAE9nu1FvwOtYw5PUoreRaDlfpl8nFD9mEO8hFeoZ3JOw5Wy4 /n3FDc+5lIZfHlQ5hHxOwbr82olMMO7jFwrDP0o7YQFFYWpfH3WdPmd6mNWy MU6YInMSWYZ3FQlCAGcb7XV0EhUrdbns3PsG21pMBXNYjefzAB5zLt3Brm4o OjQj6m0NSTM09T53wcDvAb0= =K27A -END PGP SIGNATURE- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] mdadm: failed to write superblock to
Am 07.06.2012 09:48, schrieb sebastian: # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sda1[2](F) sdb1[1] 2096064 blocks [2/1] [_U] md2 : active raid1 sda3[2](F) sdb3[1] 1462516672 blocks [2/1] [_U] md1 : active raid1 sda2[0] sdb2[1] 524224 blocks [2/2] [UU] unused devices: none I have remove the partition: # mdadm --remove /dev/md0 /dev/sda1 mdadm: hot removed /dev/sda1 from /dev/md0 # mdadm --remove /dev/md2 /dev/sda3 mdadm: hot removed /dev/sda3 from /dev/md2 Now i want to add the old partition (to sync the raid), unfortunately, comes an error message: # mdadm --add /dev/md0 /dev/sda1 mdadm: failed to write superblock to /dev/sda1 What is wrong here? Looks like a hardware defect to me. That's probably also the reason why the RAID went degraded in the first place. Better replace that disk while the other one still holds the line. HTH T. -- Tilman Schmidt Phoenix Software GmbH Bonn, Germany ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Installing QEMU without KVM
From: Aft nix aft...@gmail.com I'm developing some kernel module, so i need a stand alone qemu to test my kernel. Although i've seen a qemu in rpmforge, still yum install qemu does not work. What do you mean by does not work? Dependencies problems? Dependencies Resolved Package Arch Version Repository Size Installing: qemu x86_64 2:0.15.0-1.el6.rfx rpmforge-extras 25 M Installing for dependencies: audiofile x86_64 1:0.2.6-11.1.el6 base 95 k bluez-libs x86_64 4.66-1.el6 base 75 k celt051 x86_64 0.5.1.3-0.el6 base 50 k esound-libs x86_64 1:0.2.41-3.1.el6 base 74 k qemu-img x86_64 2:0.12.1.2-2.209.el6_2.5 updates 338 k spice-server x86_64 0.8.2-5.el6 base 251 k Transaction Summary Install 7 Package(s) JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] mdadm: failed to write superblock to
Am 07.06.2012 13:48, schrieb Tilman Schmidt: Am 07.06.2012 09:48, schrieb sebastian: # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sda1[2](F) sdb1[1] 2096064 blocks [2/1] [_U] md2 : active raid1 sda3[2](F) sdb3[1] 1462516672 blocks [2/1] [_U] md1 : active raid1 sda2[0] sdb2[1] 524224 blocks [2/2] [UU] unused devices:none I have remove the partition: # mdadm --remove /dev/md0 /dev/sda1 mdadm: hot removed /dev/sda1 from /dev/md0 # mdadm --remove /dev/md2 /dev/sda3 mdadm: hot removed /dev/sda3 from /dev/md2 Now i want to add the old partition (to sync the raid), unfortunately, comes an error message: # mdadm --add /dev/md0 /dev/sda1 mdadm: failed to write superblock to /dev/sda1 What is wrong here? Looks like a hardware defect to me. That's probably also the reason why the RAID went degraded in the first place. Better replace that disk while the other one still holds the line. HTH T. yes, of course, the hardware is defective. I was confused because I've only works something like this more often, and otherwise a resync works. I was this morning certainly did not fit ;) thanks ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Installing QEMU without KVM
On Thu, Jun 7, 2012 at 5:53 PM, John Doe jd...@yahoo.com wrote: From: Aft nix aft...@gmail.com I'm developing some kernel module, so i need a stand alone qemu to test my kernel. Although i've seen a qemu in rpmforge, still yum install qemu does not work. What do you mean by does not work? Dependencies problems? Dependencies Resolved Package Arch Version Repository Size Installing: qemu x86_64 2:0.15.0-1.el6.rfx rpmforge-extras 25 M Installing for dependencies: audiofile x86_64 1:0.2.6-11.1.el6 base 95 k bluez-libs x86_64 4.66-1.el6 base 75 k celt051 x86_64 0.5.1.3-0.el6 base 50 k esound-libs x86_64 1:0.2.41-3.1.el6 base 74 k qemu-img x86_64 2:0.12.1.2-2.209.el6_2.5 updates 338 k spice-server x86_64 0.8.2-5.el6 base 251 k Transaction Summary No, package qemu availabe. yum install qemu Loaded plugins: fastestmirror, refresh-packagekit, security Loading mirror speeds from cached hostfile * base: mirrors.sin3.sg.voxel.net * epel: ftp.riken.jp * extras: mirrors.sin3.sg.voxel.net * rpmforge: mirror.oscc.org.my * rpmfusion-free-updates: ftp.upjs.sk * rpmfusion-free-updates-testing: ftp.upjs.sk * updates: mirrors.sin3.sg.voxel.net Setting up Install Process No package qemu available. Error: Nothing to do You can see rpmforge is infact enabled. Cheers. Install 7 Package(s) JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos -- -aft ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Installing QEMU without KVM
From: Aft nix aft...@gmail.com On Thu, Jun 7, 2012 at 5:53 PM, John Doe jd...@yahoo.com wrote: From: Aft nix aft...@gmail.com I'm developing some kernel module, so i need a stand alone qemu to test my kernel. Although i've seen a qemu in rpmforge, still yum install qemu does not work. What do you mean by does not work? Dependencies problems? No, package qemu availabe. yum install qemu Loaded plugins: fastestmirror, refresh-packagekit, security Loading mirror speeds from cached hostfile * base: mirrors.sin3.sg.voxel.net * epel: ftp.riken.jp * extras: mirrors.sin3.sg.voxel.net * rpmforge: mirror.oscc.org.my * rpmfusion-free-updates: ftp.upjs.sk * rpmfusion-free-updates-testing: ftp.upjs.sk * updates: mirrors.sin3.sg.voxel.net Setting up Install Process No package qemu available. Error: Nothing to do You can see rpmforge is infact enabled. But not rpmforge-extras... JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Installing QEMU without KVM[SOLVED]
On Thu, Jun 7, 2012 at 6:43 PM, John Doe jd...@yahoo.com wrote: From: Aft nix aft...@gmail.com On Thu, Jun 7, 2012 at 5:53 PM, John Doe jd...@yahoo.com wrote: From: Aft nix aft...@gmail.com I'm developing some kernel module, so i need a stand alone qemu to test my kernel. Although i've seen a qemu in rpmforge, still yum install qemu does not work. What do you mean by does not work? Dependencies problems? No, package qemu availabe. yum install qemu Loaded plugins: fastestmirror, refresh-packagekit, security Loading mirror speeds from cached hostfile * base: mirrors.sin3.sg.voxel.net * epel: ftp.riken.jp * extras: mirrors.sin3.sg.voxel.net * rpmforge: mirror.oscc.org.my * rpmfusion-free-updates: ftp.upjs.sk * rpmfusion-free-updates-testing: ftp.upjs.sk * updates: mirrors.sin3.sg.voxel.net Setting up Install Process No package qemu available. Error: Nothing to do You can see rpmforge is infact enabled. But not rpmforge-extras... Hi JD, Thanks for pointing this. everything seems ok now. I'm marking this thread as SOLVED. Cheers. JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos -- -aft ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Worrying after IPv6 day...
Hi, after IPv6 day, I was wondering if our server were really secure... And, I know we should switch on IPv6 everywhere but... it will take some time. Usually, we disable(d) IPv6; so we are not running ip6tables. Can I start ip6tables in all cases (even if only IPv4) just to be on the safe side? On CentOS 6 servers, I use the --noipv6 in the kickstart files and I removed NetworkManager; but ifconfig still shows IPv6 adresses. And I wonder from where it gets them... based on the MAC? I guess they are not routable, so I should not get any traffic... right? Thx, JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Worrying after IPv6 day...
On 07/06/2012 16:36, John Doe wrote: Hi, after IPv6 day, I was wondering if our server were really secure... And, I know we should switch on IPv6 everywhere but... it will take some time. Usually, we disable(d) IPv6; so we are not running ip6tables. Can I start ip6tables in all cases (even if only IPv4) just to be on the safe side? On CentOS 6 servers, I use the --noipv6 in the kickstart files and I removed NetworkManager; but ifconfig still shows IPv6 adresses. And I wonder from where it gets them... based on the MAC? I guess they are not routable, so I should not get any traffic... right? Thx, JD Your best bet with regard to protecting yourself from passing IPv6 tunnelled traffic is to make sure you're blocking protocol 41. This will prevent rogue IPv6 tunnels forming across your IPv4 network. You don't need ip6tables to do this. If your other managed endpoints are not running IPv6 and you're blocking protocol 41 (note this is not port 41, but _protocol_ 41) then you should mitigate most of the IPv6 issues. I would normally assume that your demarc points have a default policy to drop unknown / unspecified traffic. -- Regards, Giles Coochey, CCNA, CCNAS NetSecSpec Ltd +44 (0) 7983 877438 http://www.coochey.net http://www.netsecspec.co.uk gi...@coochey.net ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS-announce Digest, Vol 88, Issue 4
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. CESA-2012:0715 Critical CentOS 5 thunderbird Update
(Johnny Hughes)
2. CESA-2012:0715 Critical CentOS 6 thunderbird Update
(Johnny Hughes)
--
Message: 1
Date: Thu, 7 Jun 2012 09:01:37 +
From: Johnny Hughes joh...@centos.org
Subject: [CentOS-announce] CESA-2012:0715 Critical CentOS 5
thunderbird Update
To: centos-annou...@centos.org
Message-ID: 20120607090137.ga23...@chakra.karan.org
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2012:0715 Critical
Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0715.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
6bf79e5cac8fc2edf5ddd0ea3eb9b8f59856ccef9d2e3f9532717420a4bea844
thunderbird-10.0.5-2.el5.centos.i386.rpm
x86_64:
31f5fbeaba9516065a1e96069b9db0c033c35ffebca84b40e91d5ed14905ea28
thunderbird-10.0.5-2.el5.centos.x86_64.rpm
Source:
492c542a791f9c5cae5af3026594e5e6a94d11010d5a34ca8a63867b6185a6d8
thunderbird-10.0.5-2.el5.centos.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
--
Message: 2
Date: Thu, 7 Jun 2012 12:44:35 +
From: Johnny Hughes joh...@centos.org
Subject: [CentOS-announce] CESA-2012:0715 Critical CentOS 6
thunderbird Update
To: centos-annou...@centos.org
Message-ID: 20120607124435.ga1...@chakra.karan.org
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2012:0715 Critical
Upstream details at : http://rhn.redhat.com/errata/RHSA-2012-0715.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
a6c2d89df73766c12a2f49fc744382ad6abfd251ad6f9de10b5ec551fe1977ce
thunderbird-10.0.5-2.el6.centos.i686.rpm
x86_64:
4f3b26e0947e4611551bbb19491f6263b7493a9fbcdd347333a5552514c25fef
thunderbird-10.0.5-2.el6.centos.x86_64.rpm
Source:
159c10043424925479cc0bc79ec1139f6da9f1270bc86388bdf1cf3ae628c187
thunderbird-10.0.5-2.el6.centos.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 88, Issue 4
**
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 75% - 80% Rebuild Complete
On 6/5/2012 7:21 PM, Eugene Poole wrote: OK, I'm about 90% sure that I've corrected the boot loader situation with RAID-1 and the second hard drive. I haven't tested the correction, but here's what I did: Examined the grub.conf file and noticed that hd0 uses (hd0,1), so what followed was grub grub device (hd1) /dev/sdc grub root (hd1,1) grub setup (hd1) after receiving the successful message grub quit I didn't rebuild the boot loader on /dev/sda because it is working (if it ain't broke don't fix it). My situation is that I'm using 4 - 1 TB hard drives and I used the following pattern: /dev/sda | /dev/sdc = First Raid -1 volume /dev/sdb | /dev/sdd = Second Raid-1 volume There is no complete solution to this problem. The question is this: When one of the drives dies, how will the system see the remaining drive? Will it still see it as sdb, or will it now see that drive as sda? These situations need different grub configs. I generally configure both drives as if they were hd0/sda. That way, if sda crashes, I can remove the disk and boot the second drive normally. -- Bowie ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Postfix not reading main.cf
Neil wrote: Hello: I just did a fresh install of CentOS 6.2 on a virtual server. I am trying to configure Postfix but it does not seem to be reading configuration directives from /etc/postfix/main.cf Here is what I did to test it: vi /etc/postfix/main.cf and set this directive: myorigin = hello.world.com postfix reload postconf -d | grep myorigin I get this output: append_at_myorigin = yes myorigin = $myhostname Any ideas why it is not picking up the configuration? Thanks, Neil What you should do is run postconf without paramaters to a file and inspect that. In my case e.g. myorigin is set to $mydomain, but mydomain is set to the correct value. Good lcuk Adrian -- Adri P. van Bloois Antonlaan 104 email: adr...@pa0rda.nl 3701 VG Zeist voice: +31-(0)-30-6912741 The Netherlands fax:NONE 52 05'15.77N 5 4'44.56E QTH-locater JO 22 OC The whole point of cooking is to get as much flavour out of the ingredients as possible. -- Delia Smith -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Postfix not reading main.cf
Adrian: That is a great suggestion. Thanks for the tip! Neil -- Neil Aggarwal, (972)834-1565, http://UnmeteredVPS.net/centos Virtual private server with CentOS 6 preinstalled Unmetered bandwidth = no overage charges -Original Message- What you should do is run postconf without paramaters to a file and inspect that. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] (?) Dual-monitor wallpapers on CEntOS 6
I've recently set up two workstations running CentOS 6, one with an nVidia card and the elrepo drivers and one with an ATI Radeon card with the elrepo fglrx drivers. Both work well, but one aspect of the systems works different from CEntOS 5 on those systems: I cannot get a wallpaper image to span the two monitors. I have tried both with and without xinerama and there is no difference in this regard. The specified wallpaper is displayed on both monitors. Has anybody else run across this or a solution? I freely admit, this is a trivial issue. It's strictly an aesthetic matter and I'm curious as to why it doesn't work the same. Just wonderin' -- Jay Leafey - jay.lea...@mindless.com Memphis, TN ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] (?) Dual-monitor wallpapers on CEntOS 6
Jay Leafey wrote: I've recently set up two workstations running CentOS 6, one with an nVidia card and the elrepo drivers and one with an ATI Radeon card with the elrepo fglrx drivers. Both work well, but one aspect of the systems works different from CEntOS 5 on those systems: I cannot get a wallpaper image to span the two monitors. I have tried both with and without xinerama and there is no difference in this regard. The specified wallpaper is displayed on both monitors. Has anybody else run across this or a solution? I freely admit, this is a trivial issue. It's strictly an aesthetic matter and I'm curious as to why it doesn't work the same. Just wonderin' For the nVidia one, are you using the nVidia X server setting applet? mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] (?) Dual-monitor wallpapers on CEntOS 6
On 06/07/2012 04:08 PM, m.r...@5-cent.us wrote: For the nVidia one, are you using the nVidia X server setting applet? mark Yes, I am. I used the nvidia-xconfig program to set the initial display configuration. I believe I used the options --twinview --dynamic-twinview when I ran it. Here's the relevant sections from /etc/X11/xorg.conf: Section Device Identifier Device0 Driver nvidia VendorName NVIDIA Corporation BoardName GeForce 8400 GS EndSection Section Screen Identifier Screen0 Device Device0 MonitorMonitor0 DefaultDepth24 Option TwinView 1 Option TwinViewXineramaInfoOrder DFP-0 Option metamodes DFP: nvidia-auto-select +0+0, CRT: nvidia-auto-select +1920+0 SubSection Display Depth 24 EndSubSection EndSection As you can see, I've got one monitor on the DVI connection and one on the VGA. Both monitors are the same resolution, 1920x1080. Oddly, it only shows one Monitor section in the file, the one for the DVI connection. I believe this is an artefact of the dynamic-twinview option, the second monitor appears to be detected on-the-fly. Any thoughts? -- Jay Leafey - jay.lea...@mindless.com Memphis, TN ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 75% - 80% Rebuild Complete
on 6/7/2012 9:40 AM Bowie Bailey spake the following: On 6/5/2012 7:21 PM, Eugene Poole wrote: OK, I'm about 90% sure that I've corrected the boot loader situation with RAID-1 and the second hard drive. I haven't tested the correction, but here's what I did: Examined the grub.conf file and noticed that hd0 uses (hd0,1), so what followed was grub grub device (hd1) /dev/sdc grub root (hd1,1) grub setup (hd1) after receiving the successful message grub quit I didn't rebuild the boot loader on /dev/sda because it is working (if it ain't broke don't fix it). My situation is that I'm using 4 - 1 TB hard drives and I used the following pattern: /dev/sda | /dev/sdc = First Raid -1 volume /dev/sdb | /dev/sdd = Second Raid-1 volume There is no complete solution to this problem. The question is this: When one of the drives dies, how will the system see the remaining drive? Will it still see it as sdb, or will it now see that drive as sda? These situations need different grub configs. I generally configure both drives as if they were hd0/sda. That way, if sda crashes, I can remove the disk and boot the second drive normally. In older versions sdb would become sda, but I don't have enough time on the 6 series to know for sure... Maybe I will fire up a virtual machine with a couple emulated sata drives and see ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 75% - 80% Rebuild Complete
On Thu, Jun 7, 2012 at 4:48 PM, Scott Silva ssi...@sgvwater.com wrote: In older versions sdb would become sda, but I don't have enough time on the 6 series to know for sure... Maybe I will fire up a virtual machine with a couple emulated sata drives and see Sda/sdb are the kernel's conventions. What matters is what bios sees. And that may be different depending not only on the hardware but also the failure mode - sometimes a drive will fail but not really disappear from detection and it is hard to emulate that. Also, back in ATA days it was pretty common for a failed drive to lock both channels on the controller. As long as you have physical access to the box you can fix it fairly quickly by booting a rescue iso and re-installing grub, even if you have to try a couple of times to get it right. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] some security measures I would like to share
I apologize for the html, but it is a copy from a web post I did. I wanted to share this with list members and hope it helps others. I tried not to be redundant and add things I have not seen posted before. Always interested in constructive thoughts, better ideas, etc. ** *Security thoughts for server admins/webmasters* I would like to add some security measures I like to use. These are not listed on security sites and I feel it is time someone posted this stuff. This concerns programs/items used by webmasters/server admins on a very irregular basis. (not very often). This list assumes you have an IPMI card with its own eth port or an onboard IPMI interface, both having video access. Or accessing the shell of a virtual host to access virtual servers located on it. (if no IPMI) Quote: *PHPMYADMIN* - This is a wonderful tool for use by web programmers. Most security with this program lists just two protections. a)Use htaccess to password protect, force SSL b)Alias the folder from /phpmyadmin to something like /examp This is where security measures, aside from keeping updated, seem to end. This is bad. There is more you can do to protect that access to your database. PhpMyAdmin is a program you will use at times, but 99% of the time you will never touch it at all. So why would you leave it open to hackers all the time? Simply disable the 'alias' in httpd to prevent it from being accessed. For example in CentOS 6 the file /etc/httpd/conf.d/phpmyadmin.conf contains this directory information. (or something like it.) I have added 'Deny from ALL and commented out 'Allow from ALL' and restarted httpd. (the allowoverride is allowing htaccess protection for the folder). You could comment out everything except the allowoverride and deny from all... Quote: Directory /usr/share/phpMyAdmin/ *Order Deny,Allow* Deny from All Allow from 127.0.0.1 Allow from ::1 *#Allow from All* allowoverride All /Directory Once httpd is restarted no one can access the phpmyadmin folder if it is not in the html folder. (in centos 6 the program is usually located in /usr/share/phpmyadmin). This prevents the hacking of your phpmyadmin program. If you think about it, outside of a small fix or initial programming you will almost never use the program. So why do you leave it open to everyone 24 hours a day? Quote: *IPMI* IPMI is great but if you are a webmaster you are probably leaving this open to the internet. If you are local to the datacenter, or the datacenter is really cool, you can remove the eth cable from the ipmi port. And ask them to plug it in when there is an issue. This only works if you have a separate ipmi card with its own eth port. (and helps if you tag the cable and port for the center) I think most of us seldom, if ever, use our IPMI during the course of a year once the system is set up. This prevents root access, IPMI card getting hacked, and still allows emergency access with a quick visit or a phone call *IPMI, Virtual Host, Virtual Machines* Quote: *Your Virtual Host server* I seldom ever need to go into my virtual host. It is set up correctly and I get my logwatches every day. I have no ports open up on it. If I never use it, why would I leave a shell port open 24 hours a day? If I have an IPMI card I can log in and open that port. Then I can do what I need to do. Safest, if IPMI is available (with video) is to comment out/disable the ssh port. On a virtual host you most likely use a physical bridge. This means nothing is touching the host. Great Security tip. Quote: *Virtual Machines- DNS* Are your DNS servers virtual machines on a server (or on a dedicated with an IPMI card in it)? I bet you never access shell except to make that very rare dns change. And if you use rndc you never use shell. If you have IPMI with video disable ssh port. Enable it via IPMI on those very rare instances you need to access it. Logwatch can still send out. Only port 53 should be open 24 hours a day (and if rndc that port too...and 5353 if you are doing that.) There is no reason to leave this system open to the net at all. Enable shell when you need it and then disable when done. You do not need to open port 25 (or any port) to send emails out of the system. So why do you leave port 22 (or other shell port) on 24 hours a day if you never ever use it? Quote: *MYSQL servers* Again, if on a virtual host or even its own dedicated disable port 22 (ssh port) and only enable via IPMI on those rare times you need to use it. Quote: *Your website/webserver* The same issue remains. Outside of the times you are using shell OR FTP...these ports should be disabled. Enable using IPMI. This simple act prevents a lot of hack attempts, log filling, and gives massive peace of mind. Yes, you use shell and ftpbut not that much. Think about it. You might use ftp and shell a lot, but you are leaving those ports open
[CentOS] SCO OpenServer under KVM?
Does anybody here have experience running SCO OpenServer 5.0.6a or earlier under KVM? Bill -- INTERNET: b...@celestial.com Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way Voice: (206) 236-1676 Mercer Island, WA 98040-0820 Fax:(206) 232-9186 Skype: jwccsllc (206) 855-5792 Under democracy one party always devotes its chief energies to trying to prove that the other party is unfit to rule and both commonly succeed, and are right. -- H.L. Mencken ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] some security measures I would like to share
On 6/7/2012 7:42 PM, Bob Hoffman wrote: *On a final note* If you are building a web application you should use a mysql user that is only allowed to update and select... With proper programming you can set up items to be deleted via a cron job using a mysql user that has a bit more access. This prevents a hacker from actually deleting or altering any dataand easily rolled back. This is how I program and I think it should be standard. As far as I know not one single program does this...and that is a shame. Sorry, I meant select and insert only. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Bug 820677 - (CVE-2012-2337) CVE-2012-2337 sudo: Multiple netmask values used in Host / Host_List configuration cause any host to be allowed access
Hi all, I just want to confirm, there is no patch release yet for this sudo, is it? https://bugzilla.redhat.com/show_bug.cgi?id=820677 Thank you. -- Fajar. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] (?) Dual-monitor wallpapers on CEntOS 6
A bit more Googling found the answer: it is a regression caused by a fix in Gnome to fix a reported problem where some individuals found it too difficult to create dual-monitor wallpapers. Apparently there are some patches available to the control-center package that will add a spanning option to the desktop background control, but Red Hat NAKed the change for 6.1. Apparently this is available in Fedora 12, but the option is missing in RHEL 6. See https://bugzilla.redhat.com/show_bug.cgi?id=616701 for the response. I may try to rebuild the control-center RPM with the patches when I get some time. I'll post here if I make any progress. -- Jay Leafey - jay.lea...@mindless.com Memphis, TN ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 75% - 80% Rebuild Complete
On 06/07/2012 03:48 PM, Les Mikesell wrote: On Thu, Jun 7, 2012 at 4:48 PM, Scott Silva ssi...@sgvwater.com wrote: In older versions sdb would become sda, but I don't have enough time on the 6 series to know for sure... Maybe I will fire up a virtual machine with a couple emulated sata drives and see Sda/sdb are the kernel's conventions. What matters is what bios sees. And that may be different depending not only on the hardware but also the failure mode - sometimes a drive will fail but not really disappear from detection and it is hard to emulate that. Also, back in ATA days it was pretty common for a failed drive to lock both channels on the controller. As long as you have physical access to the box you can fix it fairly quickly by booting a rescue iso and re-installing grub, even if you have to try a couple of times to get it right. And if the server is colocated, but you have remote console access, you can leave a recovery CD in the drive, but set the boot order to boot the hard drive and then remotely change the boot order if you have problems. Nataraj ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
