Re: [CentOS] ekiga
Hadi, Forget it. I suspect you would have to upgrade a whole load of libraries and if it were you doing it, you will break your system beyond recognition. Christopher On Monday, September 19, 2011 12:48 PM, hadi motamedi wrote: > Dear All > I have installed Asterisk on my centos 5.0 and I have two other centos > 6.0 and centos 5.6 with ekiga sip client. The centos 6.0 can make > successful sip calls but centos 5.6 cannot. Among the Asterisk logs, I > found that the centos 6.0 has ekiga 3.2.6 but centos 5.6 has ekiga > 2.0.2 . How can I install/upgrade my older ekiga? > Thank you > ___ > 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] ekiga
On 9/19/11, Christopher Chan wrote: > Hadi, > > Forget it. I suspect you would have to upgrade a whole load of libraries > and if it were you doing it, you will break your system beyond recognition. > > Christopher > > On Monday, September 19, 2011 12:48 PM, hadi motamedi wrote: >> Dear All >> I have installed Asterisk on my centos 5.0 and I have two other centos >> 6.0 and centos 5.6 with ekiga sip client. The centos 6.0 can make >> successful sip calls but centos 5.6 cannot. Among the Asterisk logs, I >> found that the centos 6.0 has ekiga 3.2.6 but centos 5.6 has ekiga >> 2.0.2 . How can I install/upgrade my older ekiga? >> Thank you >> ___ >> 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 > Thank you very much for your help. You mean it is better to just rely on centos 6.0 and have all clients running it as well? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Safely Remove Disk on LVM
On Fri, Sep 16, 2011 at 5:57 PM, Theo Band wrote: > On 09/16/2011 05:03 AM, Muhammad Panji wrote: > > Dear All, > > I plan to replace an error disk that is part of an LV. from LVM how-to > > it could be done with using pvmove to move all PE from old disk to new > > disk.But the howto also said that pvmove is slow. Anyone has > > experience using pvmove on 2TB disk? > > > > Is it possible to make all PE on the old disk empty so I don't have to > > do pvmove (assuming that I can make a free space >= 2TB). Thank you in > > advance > > Regards > Yes it is slow, but it works. You can condider to remove some (unused) > LVM that have extends on the physical disk. That speeds it up, as the > extends are marked free again. How many disks do you now have in your > volume group? If only one, then simply try to copy the entire disk to > another one (dd/ddrescue/clonezilla). If the disk has bad sectors, then > the pvmove will most likely fail anyhow. > Hi Theo, thank you for the reply. I have four disk in one LV. so yesterday I already done pvmove the 2TB disk and it took time about 20 hours. I think the disk is just start to fail and most part of the disk is still good, that's why the pvmove process didn't take time that long. Regards, -- - Muhammad Panji http://www.panji.web.id http://www.kurungsiku.com http://sumodirjo.wordpress.com http://www.kurungsiku.web.id http://www.linuxbox.web.id ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 6.1 Update request
On Sun, 18 Sep 2011, Timo Neuvonen wrote: > I simply installed CentOS 6.0, downloaded kernel from SL6.1 repo, and > installed it. Basically this is what was needed to make Intel graphics work, > I think there were 1-2 other rpms I needed to upgrade too to fix > dependencies, but this was easy to notice during the kernel install. > > This way the system automatically will roll back to pure CentOS when newer > CentOS 6.1 rpms will be available. If you don't mind passing on some details for me, as I've got a related problem. Which intel chipset have you got? Does OpenGL work, and if so, what's you glxinfo output? Thanks, jh ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ekiga
On Monday, September 19, 2011 03:30 PM, hadi motamedi wrote: > On 9/19/11, Christopher Chan wrote: >> Hadi, >> >> Forget it. I suspect you would have to upgrade a whole load of libraries >> and if it were you doing it, you will break your system beyond recognition. >> > Thank you very much for your help. You mean it is better to just rely > on centos 6.0 and have all clients running it as well? If you want them all running the same version, then yes, just go centos 6 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 6.1 Update request
Hello all I had the same problems with centos 6.0 and a SandyBridge laptop (Dell Latitude E5420 i5 2410M) On 09/19/2011 12:24 PM, John Hodrien wrote: > On Sun, 18 Sep 2011, Timo Neuvonen wrote: > >> I simply installed CentOS 6.0, downloaded kernel from SL6.1 repo, and >> installed it. Basically this is what was needed to make Intel graphics work, >> I think there were 1-2 other rpms I needed to upgrade too to fix >> dependencies, but this was easy to notice during the kernel install. > If you don't mind passing on some details for me, as I've got a related > problem. you have to install the following from SL 6.1: - latest kernel (kernel-2.6.32-131.12.1.el6) - kernel-firmware-2.6.32-131.12.1.el6 - latest xorg-x11-drv-intel (xorg-x11-drv-intel-2.14.0-1) with dependencies (xorg-x11-drivers) - latest mesa packages: mesa-dri-drivers, mesa-libGL, mesa-libGLU (version 7.10-1 at the moment) - latest libdrm (libdrm-2.4.23-1) > Which intel chipset have you got? Does OpenGL work, and if so, what's you > glxinfo output? openGL and DRI now work. (for my laptop also screen brightness and suspend to RAM work ok) Lec lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Sandy Bridge DRAM Controller [8086:0104] (rev 09) 00:02.0 VGA compatible controller [0300]: Intel Corporation Sandy Bridge Integrated Graphics Controller [8086:0116] (rev 09) 00:16.0 Communication controller [0780]: Intel Corporation Cougar Point HECI Controller #1 [8086:1c3a] (rev 04) 00:1a.0 USB Controller [0c03]: Intel Corporation Cougar Point USB Enhanced Host Controller #2 [8086:1c2d] (rev 04) 00:1b.0 Audio device [0403]: Intel Corporation Cougar Point High Definition Audio Controller [8086:1c20] (rev 04) 00:1c.0 PCI bridge [0604]: Intel Corporation Cougar Point PCI Express Root Port 1 [8086:1c10] (rev b4) 00:1c.1 PCI bridge [0604]: Intel Corporation Cougar Point PCI Express Root Port 2 [8086:1c12] (rev b4) 00:1c.5 PCI bridge [0604]: Intel Corporation Cougar Point PCI Express Root Port 6 [8086:1c1a] (rev b4) 00:1c.6 PCI bridge [0604]: Intel Corporation Cougar Point PCI Express Root Port 7 [8086:1c1c] (rev b4) 00:1d.0 USB Controller [0c03]: Intel Corporation Cougar Point USB Enhanced Host Controller #1 [8086:1c26] (rev 04) 00:1f.0 ISA bridge [0601]: Intel Corporation Cougar Point LPC Controller [8086:1c49] (rev 04) 00:1f.2 SATA controller [0106]: Intel Corporation Cougar Point 6 port SATA AHCI Controller [8086:1c03] (rev 04) 00:1f.3 SMBus [0c05]: Intel Corporation Cougar Point SMBus Controller [8086:1c22] (rev 04) 02:00.0 Network controller [0280]: Intel Corporation 6000 Series Gen2 [8086:0082] (rev 34) 03:00.0 SD Host controller [0805]: O2 Micro, Inc. Device [1217:8321] (rev 05) 03:00.1 Mass storage controller [0180]: O2 Micro, Inc. Device [1217:8331] (rev 05) 04:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5761 Gigabit Ethernet PCIe [14e4:1681] (rev 10) glxinfo name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap, GLX_INTEL_swap_event GLX version: 1.4 GLX extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile GEM 20100330 DEVELOPMENT OpenGL version string: 2.1 Mesa 7.10 OpenGL shading language version string: 1.20 OpenGL extensions: GL_ARB_copy_buffer, GL_ARB_depth_clamp, GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_draw_elements_base_vertex, GL_ARB_explicit_attrib_location, GL_ARB_fragment_coord_conventions, GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader, GL_ARB_framebuffer_object, GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, GL_ARB_map_buffer_range, GL_ARB_mult
Re: [CentOS] ekiga
On 9/19/11, Christopher Chan wrote: > On Monday, September 19, 2011 03:30 PM, hadi motamedi wrote: >> On 9/19/11, Christopher Chan wrote: >>> Hadi, >>> >>> Forget it. I suspect you would have to upgrade a whole load of libraries >>> and if it were you doing it, you will break your system beyond >>> recognition. >>> >> Thank you very much for your help. You mean it is better to just rely >> on centos 6.0 and have all clients running it as well? > > If you want them all running the same version, then yes, just go centos 6 > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > Thank you very much for your help. Excuse me, do we have other sip clients rather than ekiga that I can give them a try? The ekiga 2.0.2 is too old to work with my new Asterisk version on my centos 5.0 . I will upgrade my other clients to centos 6.0 (as you told me) but for unknown reasons this version of Asterisk does not work on my centos 6.0 but just my centos 5.0 so I need to keep my Asterisk server still running centos 5.0 but I will upgrade all of my other clients to centos 6.0 to make use of this new version of ekiga 3.2.6 . Thank you again ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] mount exFAT filesystem on centos
Hi, Is there some simple tool to mount exFAT filesystem on CentOS (2.6.18)? Regards. __ Notre adresse de messagerie évolue pour plus de simplicité vers : prenom@ifpen.fr. La racine @ifpenergiesnouvelles.fr reste néanmoins active. Our e-mail address is changing to firstname.surn...@ifpen.fr. Nevertheless, messages sent to the domain @ifpenergiesnouvelles.fr will still be delivered. Ce message (et toutes ses pièces jointes éventuelles) est confidentiel et établi à l'intention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. IFP Energies nouvelles décline toute responsabilité au titre de ce message. This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. IFP Energies nouvelles should not be liable for this message. Visitez notre site Web / Visit our web site : www.ifpenergiesnouvelles.fr / www.ifpenergiesnouvelles.com __ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 6.1 Update request
On Mon, 19 Sep 2011, Alexandru Chiscan wrote: > I had the same problems with centos 6.0 and a SandyBridge laptop (Dell > Latitude E5420 i5 2410M) > openGL and DRI now work. (for my laptop also screen brightness and > suspend to RAM work ok) Thanks a lot for this info, it's much appreciated. When I get a chance (when there's not someone logged in) I'll update mesa to match the versions you suggested, and hopefully that'll sort it out. jh ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] mount exFAT filesystem on centos
From: MOKRANI Rachid > Is there some simple tool to mount exFAT filesystem on CentOS (2.6.18)? Google says: http://en.wikipedia.org/wiki/ExFAT#Support_on_Other_Platforms JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] run without sendmail
I'm running centos on a "limited" environment. Is it ok to turn off sendmail and run without it. Are there issues with doing that or is all Ok. Thanks, Jerry ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] run without sendmail
The machine will run fine. The question is do you need it to send you email for alerting reasons? On Mon, 19 Sep 2011, Jerry Geis wrote: > I'm running centos on a "limited" environment. Is it ok to turn off > sendmail > and run without it. > -- Jim Wildman, CISSP, RHCE j...@rossberry.com http://www.rossberry.net "Society in every state is a blessing, but Government, even in its best state, is a necessary evil; in its worst state, an intolerable one." Thomas Paine ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] run without sendmail
> The machine will run fine. The question is do you need it to send you > email for alerting reasons? > > On Mon, 19 Sep 2011, Jerry Geis wrote: > > >/ I'm running centos on a "limited" environment. Is it ok to turn off > />/ sendmail > />/ and run without it. > / Jim Thanks - I thought it would be ok - but just wanted to check. No - there are no alerts from this particular device that I need/want. jerry ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS and Scientific Linux Cern installations with FAI
I'm very happy to announce, that FAI (Fully automatic Installation) now can install and configure CentOS and Scientific Linux Cern (SLC). You can use a Debian FAI server for installing CentOS version 5 and 6 or SLC 5 and 6. As an example I've also built a FAI multi-distribution CD which installs those three different Linux distributions with different configurations. Get this ISO image from http://fai-project.org/fai-cd/ This installation is very quick. I've done a CentOS 6.0 installation (with graphical desktop) in 199 seconds (in a kvm instance on a quad-core 3.2GHz, hard disk in RAM) and it only needs 490 seconds on the real hardware when installing from CD. A short description how to install CentOS or SLC via network from your FAI server is described in this mail: https://lists.uni-koeln.de/pipermail/linux-fai/2011-September/009243.html Feedback is always welcome. Please send your feedback to the linux-fai mailing list https://lists.uni-koeln.de/mailman/listinfo/linux-fai/ Best regards, Thomas, in behalf of the FAI team About FAI: FAI is a non-interactive system to install, customize and manage Linux systems and software configurations on computers as well as virtual machines and chroot environments, from small networks to large infrastructures and clusters. Compared to kickstart, FAI is more flexible and includes a powerfull class mechanism to build a configuration from multiple building blocks. It also includes the features of cobbler. The project was started in 1999 for the Debian distribution. Later Ubuntu support was added and some time ago we start adding RPM support. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] mount exFAT filesystem on centos
Hi, I found. Install this rpm and it's working on CentOS 5. http://exfat.googlecode.com/files/fuse-exfat-0.9.5-1.fc14.i686.rpm Regards. __ Notre adresse de messagerie évolue pour plus de simplicité vers : prenom@ifpen.fr. La racine @ifpenergiesnouvelles.fr reste néanmoins active. Our e-mail address is changing to firstname.surn...@ifpen.fr. Nevertheless, messages sent to the domain @ifpenergiesnouvelles.fr will still be delivered. Ce message (et toutes ses pièces jointes éventuelles) est confidentiel et établi à l'intention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. IFP Energies nouvelles décline toute responsabilité au titre de ce message. This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. IFP Energies nouvelles should not be liable for this message. Visitez notre site Web / Visit our web site : www.ifpenergiesnouvelles.fr / www.ifpenergiesnouvelles.com __ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] questions about upgrading
I'm pretty new to the task of upgrading CentOS or RedHat o.s.'s. I'm more familiar with upgrading Debian based o.s.'s. Here are my questions: 1) will yum ever upgrade the major version? I understand that there is no upgrade path from v5.x to v6.x, but is that always the case? e.g. was there an upgrade path from v4.x -> v5.x? If yum is capable of doing so, what are the command-line arguments necessary? 2) can I upgrade a minor version to any other greater minor number, or only to the greatest? E.g. if i have a v5.4 box, can i upgrade to v5.5 or v5.6, or only to v5.7 (currently the latest)? 3) if an upgrade delivers a new kernel, am I obligated to run it (i.e. will the old kernel remain installed, or will the upgrade remove the old kernel)? If not, does the upgrade automatically update grub such that the new kernel becomes the default? Will the upgraded box function properly without running the new kernel? 4) aside from when an upgrade includes a new kernel, how can I tell when a reboot is necessary? I gather that a new glibc may require services to be restarted, but is a reboot strictly necessary? 5) is there a way to apply only the updates that were made for the given minor version you're currently at? E.g. if I'm at v5.5, how can I only apply updates that were made prior to v5.6's availability? Thanks, Jon ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] eth enumeration order
I have installed Centos 6 on a server with two NICs. It so happens that
the NIC with the lower ARP adr is assigned 'eth1' and the NIC with the
higher ARP 'eth0'. (Not sure if this a bug but it is at least inconvenient)
I have modified the udev rules in
/etc/udev/rules.d/70-persistent-net.rules
by swapping eth0 with eth1 in the NIC's rules.
However: the file gets changed on reboot. A third rule is automaticaly
added for some reason, for one of the NICs which already has a rule. See
below.
The system ends up with no network interface set up at all, because the
init-script gets confused.
So
How do you specifiy the order in which NICs are enumerated?
or at least how to tell centos to stop messing with the
70-persistent-net.rules?
Regards
.Volker
Contents of /etc/udev/rules.d/70-persistent-net.rules (arps anonymized):
(These are the two rules modified by me, assigning eth0/eth1 in
ascending arp order)
# PCI device 0x8086:0x10d3 (e1000e) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="xx:xx:xx:xx:8f:ea", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth0"
# PCI device 0x8086:0x1502 (e1000e) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="xx:xx:xx:xx:8f:eb", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth1"
(This is the rule which gets automaticaly added on reboot)
# PCI device 0x8086:0x1502 (e1000e) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="xx:xx:xx:xx:8f:eb", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth0"
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] questions about upgrading
Jon Detert wrote: > I'm pretty new to the task of upgrading CentOS or RedHat o.s.'s. I'm more > familiar with upgrading Debian based o.s.'s. Here are my questions: > > 1) will yum ever upgrade the major version? I understand that there is no > upgrade path from v5.x to v6.x, but is that always the case? e.g. was > there an upgrade path from v4.x -> v5.x? If yum is capable of doing so, > what are the command-line arguments necessary? Never has been a full release upgrade path - that's a bad idea, too much cruft. > > 2) can I upgrade a minor version to any other greater minor number, or > only to the greatest? E.g. if i have a v5.4 box, can i upgrade to v5.5 or > v5.6, or only to v5.7 (currently the latest)? Yum update *will* do that without a problem. > > 3) if an upgrade delivers a new kernel, am I obligated to run it (i.e. > will the old kernel remain installed, or will the upgrade remove the old > kernel)? If not, does the upgrade automatically update grub such that the > new kernel becomes the default? Will the upgraded box function properly > without running the new kernel? No, you're not. It will update /etc/grub.conf (a link to /boot/grub/grub.conf), and the next time you reboot, it will default to the new kernel. It does remove the oldest kernel, but leave (I believe) at least three (current, and the last two). > > 4) aside from when an upgrade includes a new kernel, how can I tell when a > reboot is necessary? I gather that a new glibc may require services to be > restarted, but is a reboot strictly necessary? New kernel. > > 5) is there a way to apply only the updates that were made for the given > minor version you're currently at? E.g. if I'm at v5.5, how can I only > apply updates that were made prior to v5.6's availability? Tune /etc/yum.repos.d to point to explicity subreleases is, I think, the answer. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] questions about upgrading
> 2) can I upgrade a minor version to any other greater minor number, or only > to the greatest? E.g. if i have a v5.4 box, can i upgrade to v5.5 or v5.6, > or only to v5.7 (currently the latest)? Yes if you configure the repositories in /etc/yum.repos.d accordingly (i.e. use the vault). > 3) if an upgrade delivers a new kernel, am I obligated to run it (i.e. will > the old kernel remain installed, or will the upgrade remove the old kernel)? > If not, does the upgrade automatically update grub such that the new kernel > becomes the default? Will the upgraded box function properly without running > the new kernel? Kernels are installed side by side. For the second question, see /etc/sysconfig/kernel. In theory you should be able to mix and match any components from the same CentOS major release without problems, unless any of the release notes say otherwise. Whether it's a good idea is a different matter. > 4) aside from when an upgrade includes a new kernel, how can I tell when a > reboot is necessary? I gather that a new glibc may require services to be > restarted, but is a reboot strictly necessary? New glibc requires a reboot. Upgrading other system libraries does too, but I can't give a definite answer on the how to tell. ldd /sbin/init indicates the libselinux and libsepol packages are other candidates, but that's just one example. > 5) is there a way to apply only the updates that were made for the given > minor version you're currently at? E.g. if I'm at v5.5, how can I only apply > updates that were made prior to v5.6's availability? See the answer to 2). Other people will give you some flak for these questions as it's generally recommended to run the latest version. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Can't boot Centos6 ext4 partition from GAG bootloader
On Sun, 18 Sep 2011 18:22:34 +0100, I wrote: > there any way tp persuade Centos-6 to use an ext3 root partition? Seems not, so - sadly - have crossed Centos off my list. -- /\/\aurice ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Can't boot Centos6 ext4 partition from GAG bootloader
Maurice Batey wrote: > On Sun, 18 Sep 2011 18:22:34 +0100, I wrote: > >> there any way tp persuade Centos-6 to use an ext3 root partition? > > Seems not, so - sadly - have crossed Centos off my list. Sorry, I seem to have missed the start of this thread, and certainly don't understand it. Certainly, all the systems I've upgraded to CentOS 6, including the one I'm writing this on, are all booting off ext3 /boot partitions. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Can't boot Centos6 ext4 partition from GAG bootloader
>> there any way tp persuade Centos-6 to use an ext3 root partition? > > Seems not, so - sadly - have crossed Centos off my list. Did the installer try to install /boot in the same partition as / ? CentOS6/SL6 does support ext4 as a root device (My webserver is currently doing so) but I still keep /boot as ext3. -- Drew "Nothing in life is to be feared. It is only to be understood." --Marie Curie ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Can't boot Centos6 ext4 partition from GAG bootloader
On Mon, 19 Sep 2011 11:08:20 -0700, Drew wrote: > Did the installer try to install /boot in the same partition as / ? That's what it did. > I still keep /boot as ext3. OIC. So it needs an extra (ext3) /boot partition, as well as /. Now, if the installer had offered that, things might have been different! -- /\/\aurice ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Can't boot Centos6 ext4 partition from GAG bootloader
On 9/19/2011 2:18 PM, Maurice Batey wrote: > On Mon, 19 Sep 2011 11:08:20 -0700, Drew wrote: > >> Did the installer try to install /boot in the same partition as / ? >That's what it did. > >> I still keep /boot as ext3. > OIC. So it needs an extra (ext3) /boot partition, as well as /. > Now, if the installer had offered that, things might have been different! > It is there. I don't recall exactly how I got to it... I think I selected 'Customize' at the point where you can choose your packages and then I selected that I wanted to set the partitions myself. I got the same partition interface I've always gotten with CentOS installs... but it wasn't as obvious during the install process. It seems like some of these buttons might be sort of greyed out, but in fact they are live buttons. Sorry I don't remember the exact process. It's been a couple of weeks since doing the last install. John Hinton ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] mdadm and drive identification?
I have a server that has 16 drives in it. They are connected to a 3ware 9650SE-16ML SATA RAID card. I have the card set to export all the drives as JBOD because I prefer Linux to do the reporting of drive and RAID health . I'm using mdadm to create a RAID6 with a hot spare. Doing this I can take the disks and put them on a completely different SATA controller/computer and still have the RAID intact. My problem is that I have no "for sure" way of matching a drive assigned to one of the /dev/sd[a-z]. Normally I could use a number of methods to match up what /dev/sd[a-z] is to a drives serial number. smartctl, hdparm, udevinfo, /dev/disk/by-uuid, or /dev/disk/by-id. However, the 3ware card obfuscates the drives from the OS and those methods don't work. The only way I know how to get a drives serial number is via the smartctl command like "smartctl -d 3ware,[0-15] -i /dev/twa0", but that does not tell me which sd[a-z] the drive is assigned to. Here is what I have tried. Creating a single large partition with fdisk on each drive as linux autoraid to get a uuid. for some reason the OS assigns the same uuid and only one uuid to the last drive I partition from the 3ware card. Basically all drives on the 3ware card have the same uuid.. Using the /dev/disk/by-id/. For some reason the 3ware card does not always assign the same id to a drive after a reboot. Is there another easy way I can positively ID a drive by serial number and the /dev/sd[a-z] that mdadm sees? Thanks. David. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Can't boot Centos6 ext4 partition from GAG bootloader
On Mon, 19 Sep 2011 14:31:41 -0400, John Hinton wrote: > I > selected 'Customize' at the point where you can choose your packages and > then I selected that I wanted to set the partitions myself. That's what I did. > I got the > same partition interface I've always gotten with CentOS installs... but > it wasn't as obvious during the install process. It seems like some of > these buttons might be sort of greyed out, but in fact they are live > buttons. I might just have another try, just out of curiousity! Perhaps I missed what I was not then looking for. -- /\/\aurice ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] run without sendmail
Jerry Geis wrote: > I'm running centos on a "limited" environment. Is it ok to turn off > sendmail > and run without it. > Are there issues with doing that or is all Ok. Mail delivery can still work with sendmail turned off. The daemon is just there to receive mail. This guy explains it better than I can: http://www.deer-run.com/~hal/sysadmin/sendmail.html There's no reason to turn the MTA on unless you're running a mail server. Non-mail servers should just have a cron job flushing the submission queue just in case, but the MTA itself doesn't need to run. -- Spiro Harvey Knossos Networks Ltd (04) 460-2531 : (021) 295-1923 www.knossos.net.nz signature.asc Description: PGP signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] eth enumeration order
On Monday 19 September 2011 11:04, the following was written: > So > How do you specifiy the order in which NICs are enumerated? > or at least how to tell centos to stop messing with the > 70-persistent-net.rules? Add the hardware addresses to their ifcfg-eth# files. HWADDR=xx:xx:xx:xx:xx:xx -- Regards Robert Linux The adventure of a lifetime. Linux User #296285 Get Counted http://linuxcounter.net/ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] This doesn't make sense
On Sep 17, 2011, at 7:49 PM, Craig White wrote: > At some point, security updates for 6.1 will be released and then it > becomes a matter of deciding to install it based on the evidence that > security updates have been non-existent all this time. I'm sorry I don't follow you here? I'm fairly certain that 6.1 will include both 6.1 security/bug updates AND security/bug updates that have been released up to the beginning of the 6.1 release cycle, minus several that where released during the C6.1 release cycle. Security updates and bug fixes are intermingled without being able to distinguish one from the other outside of the RPM history. It's not the security updates that prevent me from moving to 6.0 right now, but those pesky .0 blues. -Ross ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] This doesn't make sense
On Mon, 2011-09-19 at 18:41 -0400, Ross Walker wrote: > On Sep 17, 2011, at 7:49 PM, Craig White wrote: > > > At some point, security updates for 6.1 will be released and then it > > becomes a matter of deciding to install it based on the evidence that > > security updates have been non-existent all this time. > > I'm sorry I don't follow you here? > > I'm fairly certain that 6.1 will include both 6.1 security/bug updates AND > security/bug updates that have been released up to the beginning of the 6.1 > release cycle, minus several that where released during the C6.1 release > cycle. Security updates and bug fixes are intermingled without being able to > distinguish one from the other outside of the RPM history. > > It's not the security updates that prevent me from moving to 6.0 right now, > but those pesky .0 blues. those pesky .0 blues as you call them were clearly there - see other threads about video issues, etc. I guess the point I was trying to make without being excessively blunt is that the track record of timely releases for CentOS 6.x (any release) and the track record of timely security updates (none) should really cause any one to pause before installing any version of CentOS 6 - even if 6.1 and all of the current security updates were released tomorrow. Craig ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] LVM lvresize/lvextend requires some space in /etc to grow a logical volume?
Side note: In CentOS-6, I noticed a new option in lvresize / lvextend: -r, --resizefs Resize underlying filesystem together with the logical volume using fsadm(8). Nice. Two steps (lvresize and resize2fs) can now be combined into one! Works great. But that has nothing to do with my question, just thought I'd share the discovery. == Anyway, here's the real issue with LVM, at least in CentOS-6: [root@jttest ~]# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/vg_main-lv_root 1548144 1548144 0 100% / [root@jttest ~]# lvextend -L 2G /dev/vg_main/lv_root /etc/lvm/archive/.lvm_jttest.pp.local_5523_51321310: write error failed: No space left on device Volume group "vg_main" metadata archive failed. /etc/lvm/cache/.cache.tmp: write error failed: No space left on device So I can't extend a logical volume if there's no space in /etc? Granted, I only need to delete like 2k worth of files in the same logical volume as /etc to make the above work, but I don't recall lvresize or lvextend requiring space in /etc to do a resize. Has this always been the case? I don't have any 5.x servers handy to test this with. Can anyone verify? If this is new, this seems less-than-ideal. /etc itself rarely fills up, so, in theory, I could make it its own LV, but that's even less ideal. For now, I'll stick to deleting just enough to do the extend/resize. johnny ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ekiga
On Monday, September 19, 2011 06:30 PM, hadi motamedi wrote: > Thank you very much for your help. Excuse me, do we have other sip > clients rather than ekiga that I can give them a try? The ekiga 2.0.2 > is too old to work with my new Asterisk version on my centos 5.0 . I > will upgrade my other clients to centos 6.0 (as you told me) but for > unknown reasons this version of Asterisk does not work on my centos > 6.0 but just my centos 5.0 so I need to keep my Asterisk server still > running centos 5.0 but I will upgrade all of my other clients to > centos 6.0 to make use of this new version of ekiga 3.2.6 . How about searching for sip clients? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] reading vdump files?
I have a lot of data in some vdump files backed up from a Tru64 system that I now need to recover to a Centos server. We no longer have any servers running Tru64, is there any way to extract/convert them on a "standard" linux system? Ideally converting in bulk to a tar would do. Any ideas? Russell Smithies === Attention: The information contained in this message and/or attachments from AgResearch Limited is intended only for the persons or entities to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipients is prohibited by AgResearch Limited. If you have received this message in error, please notify the sender immediately. === ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] LVM lvresize/lvextend requires some space in /etc to grow a logical volume?
Am Montag, den 19.09.2011, 19:15 -0400 schrieb Johnny Tan:
> Anyway, here's the real issue with LVM, at least in CentOS-6:
>
You would deal with the same issues in older lvm versions.
> [root@jttest ~]# df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/mapper/vg_main-lv_root
>1548144 1548144 0 100% /
>
Do i read that correctly and 1548144 1K Blocks are about 1,5G of Root
File System? Please tell me you have a seperated /var for log files.
If not, for production use, install a tool which gives you a warning
when reaching the 5% Level.
> [root@jttest ~]# lvextend -L 2G /dev/vg_main/lv_root
> /etc/lvm/archive/.lvm_jttest.pp.local_5523_51321310: write error
> failed: No space left on device
> Volume group "vg_main" metadata archive failed.
> /etc/lvm/cache/.cache.tmp: write error failed: No space left on device
>
> So I can't extend a logical volume if there's no space in /etc?
lvm tries to be helpfull if you ran into a power failure and can then
recover due his tmp files in /etc.
> Granted, I only need to delete like 2k worth of files in the same
> logical volume as /etc to make the above work, but I don't recall
> lvresize or lvextend requiring space in /etc to do a resize. Has this
> always been the case? I don't have any 5.x servers handy to test this
> with. Can anyone verify?
>
You will have the same problem, i think this procedure is the same in
all lvm2 versions, which seems a long time now.
> If this is new, this seems less-than-ideal. /etc itself rarely fills
> up, so, in theory, I could make it its own LV, but that's even less
> ideal. For now, I'll stick to deleting just enough to do the
> extend/resize.
>
This is why the older unix guys always seperate stuff from / which could
fill up the root file system. ;)
--
Stefan Held VI has only 2 Modes:
obi unixkiste orgThe first one is for beeping all the time,
FreeNode: foo_barthe second destroys the text.
---
perl -e'map{print pack c,($|++?1:13)+ord,select$,,$,,$,,$|}split//,ESEL.$/'
---
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] LVM lvresize/lvextend requires some space in /etc to grow a logical volume?
On Mon, Sep 19, 2011 at 9:38 PM, Stefan Held wrote: > Am Montag, den 19.09.2011, 19:15 -0400 schrieb Johnny Tan: >> Anyway, here's the real issue with LVM, at least in CentOS-6: >> > You would deal with the same issues in older lvm versions. Thanks Stefan. I guess I just never noticed previously. >> [root@jttest ~]# df >> Filesystem 1K-blocks Used Available Use% Mounted on >> /dev/mapper/vg_main-lv_root >> 1548144 1548144 0 100% / >> > > Do i read that correctly and 1548144 1K Blocks are about 1,5G of Root > File System? Please tell me you have a seperated /var for log files. As evidenced by the hostname, this is a test VM solely for demonstration of this problem :-). johnny ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] LVM lvresize/lvextend requires some space in /etc to grow a logical volume?
On Mon, Sep 19, 2011 at 07:15:09PM -0400, Johnny Tan wrote: > Anyway, here's the real issue with LVM, at least in CentOS-6: > > [root@jttest ~]# df > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/mapper/vg_main-lv_root >1548144 1548144 0 100% / > > [root@jttest ~]# lvextend -L 2G /dev/vg_main/lv_root > /etc/lvm/archive/.lvm_jttest.pp.local_5523_51321310: write error > failed: No space left on device > Volume group "vg_main" metadata archive failed. > /etc/lvm/cache/.cache.tmp: write error failed: No space left on device Many LVM modifications make a backup of the lvm metadata, which typically resides in /etc/lvm. You might try the -A n switch to disable the automatic backups (after strongly heeding the advice in man lvm; but as you said, on a test system, it's fine to play with). On a production system, if your / fills to 0 available blocks you've probably got bigger problems. :) So I imagine it's probably not a problem the LVM developers are too worried about (i.e., they may feel that the -A switch is sufficient to handle it). --keith -- kkel...@wombat.san-francisco.ca.us pgpo3U4s4emIb.pgp Description: PGP signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] LVM lvresize/lvextend requires some space in /etc to grow a logical volume?
On Mon, Sep 19, 2011 at 10:19 PM, Keith Keller wrote: > On Mon, Sep 19, 2011 at 07:15:09PM -0400, Johnny Tan wrote: >> Anyway, here's the real issue with LVM, at least in CentOS-6: >> >> [root@jttest ~]# df >> Filesystem 1K-blocks Used Available Use% Mounted on >> /dev/mapper/vg_main-lv_root >> 1548144 1548144 0 100% / >> >> [root@jttest ~]# lvextend -L 2G /dev/vg_main/lv_root >> /etc/lvm/archive/.lvm_jttest.pp.local_5523_51321310: write error >> failed: No space left on device >> Volume group "vg_main" metadata archive failed. >> /etc/lvm/cache/.cache.tmp: write error failed: No space left on device > > Many LVM modifications make a backup of the lvm metadata, which > typically resides in /etc/lvm. You might try the -A n switch to > disable the automatic backups (after strongly heeding the advice > in man lvm; but as you said, on a test system, it's fine to play > with). That did the trick: [root@jttest~]# lvresize -L 2G /dev/vg_main/lv_root /etc/lvm/archive/.lvm_jttest.pp.local_1416_1029753972: write error failed: No space left on device Volume group "vg_main" metadata archive failed. /etc/lvm/cache/.cache.tmp: write error failed: No space left on device [root@jttest~]# lvresize -A n -L 2G /dev/vg_main/lv_root Extending logical volume lv_root to 2.00 GiB WARNING: This metadata update is NOT backed up Logical volume lv_root successfully resized /etc/lvm/cache/.cache.tmp: write error failed: No space left on device (And the subsequent resize worked too.) Thank you for pointing out the -A flag (missed the fine print of common options being in man lvm). As you noted, I would probably never run into this situation in a non-testing environment and, if I did, would have much bigger problems. This probably explains why I never saw it previously. Good to know. johnny ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ekiga
On 9/20/11, Christopher Chan wrote: > On Monday, September 19, 2011 06:30 PM, hadi motamedi wrote: > >> Thank you very much for your help. Excuse me, do we have other sip >> clients rather than ekiga that I can give them a try? The ekiga 2.0.2 >> is too old to work with my new Asterisk version on my centos 5.0 . I >> will upgrade my other clients to centos 6.0 (as you told me) but for >> unknown reasons this version of Asterisk does not work on my centos >> 6.0 but just my centos 5.0 so I need to keep my Asterisk server still >> running centos 5.0 but I will upgrade all of my other clients to >> centos 6.0 to make use of this new version of ekiga 3.2.6 . > > How about searching for sip clients? > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > Thank you very much for your help. At now, I can do my job. Thank you again ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Submitting patches from upstream fixes/bugs
On Wed, Sep 14, 2011 at 3:10 PM, Karanbir Singh wrote: > On 09/14/2011 01:59 PM, Trey Dockendorf wrote: > > Based on the bug report for the snapshot-create issue, it seems it's in > > libvirt 0.9.0 and that it's something that may be solved completely in > > Fedora 16. Is there a good way to find if a specific patch/fix has been > > applied upstream by Red Hat? > > grab the sources, look at the code. I hepe to have an easier way than > that soon, stay tuned :) > > > What goes into the maintenance of a patch? I'd be happy to do so, but I > > only know enough C to be able to work in patches / changes and track > > down compile errors, but not enough to have been the original person > > that finds these solutions. > > essentially, when you request a package be locally ( ie, in CentOS ) > patched, we would need to copy that rpm over from the base distro into > the CentOS Plus repo. Apply the patch, test it, release it. But that > process needs to be re-done everytime there is an update to the rpm, as > long as upstream does not fix the issue, change the expected behaviour > to what you are proposing or remove / change functionality in a way that > its no longer possible to support the patches. But while the patch is in > circulation, it would mean that everytime there is an update from > upstream, you would need to make sure the patch still applies, or adapt > it to apply cleanly. > > does this clear up the requirements a bit ? > > - KB > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > That does, thanks. If you want to give me more details off-list I'd like to work on getting these patches into CentOS Plus. Also where could I begin looking to see if upstream RHEL has applied these to their releases? Thanks - Trey ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
