Discuss

discuss@lists.centos.org

34758 discussions

Permissions of mercurial-hgk?
by Dave Johansen 17 Jun '13

17 Jun '13

I just installed mercurial-hgk on CentOS 6.4 x86 and the permissions were set so that it couldn't be run by a non-root user. The two files that had incorrect permissions were: /usr/libexec/mercurial/ /usr/libexec/mercurial/hgk Is that an issue with CentOS? Or is it an issue that I should open a bugzilla against RHEL for? Thanks, Dave

1 0

ipv6 only kickstart installs
by Markus Falb 16 Jun '13

16 Jun '13

Hi, I have a kvm host and I try to install a centos 6 guest with a static ip address. When I do a manual install I eventually get to the network configuration and if I enter IP, gateway and DNS Server I can ping6 the guest from the host and I can ping6 the guest from outside. I do not want to do manual installation, so I have to specify a url to a kickstart file, but to download it the network must be configured. I try some kernel options noipv4 ipv6=... gateway=... dns=... ks=http… This gets me so far that I can ping6 the guest from the host, but I can not reach it from outside. When I ping from outside I see the guest sending neighbor solicitation requests for the IP I ping from, but this IP is in another network. I think the guest does not get a gateway configured. At least the ipv6 option is working, because I can ping the guest from the host. How do I achieve such a ipv6 only with static network configuration kickstart install? How to specify ipv6 gateway (and possibly dns) -- Markus

2 1

404 Error
by Mark LaPierre 16 Jun '13

16 Jun '13

Hey Y'all, I got this error from yum http://vault.centos.org/6.4/os/i386/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found" Has the path to the repo changed? -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

2 2

Setting up paths etc. for Qt 4 development
by Toralf Lund 14 Jun '13

14 Jun '13

Hi, I was just wondering, is there a "correct" or "preferred" way of setting up the path and other environment variables for Qt 4 development/build using qmake and all - on a CentOS 6 system? I mean, this does not work out-of-the box, at least if you have build files that assume "qmake" may be executed just like that - as there is no Qt 4 qmake on the path, although "qmake-qt4" is available. Also, if qt3-devel is installed, and the default path setup is used, "qmake" will point to the Qt 3 version, as the package includes a profile.d file that modify the path in such a way. Which also sets up other Qt related variables, I believe. There is no such file in qt4-devel, however. I know ways to set up everything so that this works as expected, of course, but it would be interesting to know how the packagers intended it to be done. Are you expected to edit login files by hand? That's sort of surprising in this day and age... Or is the thinking that the suffixed ("-qt4") version of commands will always be used? Or that everyone will be using plain make with pkg-config? Or is there some other mechanism that should to be used to select the right Qt version? - Toralf This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

2 1

CentOS-announce Digest, Vol 100, Issue 6
by centos-announce-request＠centos.org 14 Jun '13

14 Jun '13

Send CentOS-announce mailing list submissions to centos-announce(a)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-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)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-2013:0945 CentOS 6 ipa Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 13 Jun 2013 14:43:53 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2013:0945 CentOS 6 ipa Update To: centos-announce(a)centos.org Message-ID: <20130613144353.GA28907(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2013:0945 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0945.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 83a7529265080304a85b1b5f09e9593dd06c8b3ebcded082a3200e667598b6c7 ipa-admintools-3.0.0-26.el6_4.4.i686.rpm 655df337252e1a49d65875c1ab0ead80af1a8ca951d36f52a2b670f34e118ed0 ipa-client-3.0.0-26.el6_4.4.i686.rpm 790f7ea4b67366153d7b8a36e7efb96f82a4885592b31cf53734edeec05d2316 ipa-python-3.0.0-26.el6_4.4.i686.rpm 888b9bc850f53c99be9b0987d67348155bc53655060ca4f6923b6c01b1b8ba9e ipa-server-3.0.0-26.el6_4.4.i686.rpm da8c9f3a4c0279cc1d067d0c0ce84abe0989bd667ec3f52170a254080cad1dcf ipa-server-selinux-3.0.0-26.el6_4.4.i686.rpm 76f01ae1c99fc8fca9d85ba796a155af72edc606a4e062996fd55e6d0f220dd3 ipa-server-trust-ad-3.0.0-26.el6_4.4.i686.rpm x86_64: a8210e3234805c2de834cd564e41a32faa8d3b6b112f75f055b259d6106e4c20 ipa-admintools-3.0.0-26.el6_4.4.x86_64.rpm a8bbe9ee1ccb57f4bc2ebf5a00815a5059dd5e5b9c81f4a1454702483161c6c6 ipa-client-3.0.0-26.el6_4.4.x86_64.rpm 2cc104b2060fbab414926b0ec665ee5be11020b11158ff03adf2dade79ced150 ipa-python-3.0.0-26.el6_4.4.x86_64.rpm 3e8194e6a1b55b3db0bfbdb5d7919a044aaac691d01bca301767d3d58797b3f7 ipa-server-3.0.0-26.el6_4.4.x86_64.rpm f7753514b369618b1eac6b697b34b843d67128bc710181bf7afbfaa19e914000 ipa-server-selinux-3.0.0-26.el6_4.4.x86_64.rpm 9c8aa87425a0060adf21a559103d8ff8bd06a3f3303265079fbaaedcb21a8891 ipa-server-trust-ad-3.0.0-26.el6_4.4.x86_64.rpm Source: e43d62daa35d7f3651aa641a3c28765b782ce15b28912ddf48941588bc493b7b ipa-3.0.0-26.el6_4.4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 100, Issue 6 ***********************************************

1 0

KDE 4.10 repos?
by Bruce Ferrell 13 Jun '13

13 Jun '13

I'm looking for a repository that will allow me to install KDE 4.10. Are there any? I seem to be asking google the wrong questions

2 1

adaptec RAID
by m.roth＠5-cent.us 13 Jun '13

13 Jun '13

We've got this PC PitStop RAID box (they're so proud of it, there's no logo), and what lspci tells me is an Adaptec AAC-RAID (ref 09) controller. I see there's no F/OSS controllers for it, but when I go to Adaptec's site, the search denies all knowledge of such a controller. I'd like to get the correct one, and I really want an x86_64 version; googling found me a 386 rpm. Anyone know how to identify what *Adaptec* calls this thing, so I can find the info I need on their site? mark

3 9

Repair grub GPT/UEFI?
by Les Mikesell 13 Jun '13

13 Jun '13

What does it take to make a disk bootable on a system with UEFI and a GPT on the boot disk? I used a default disk layout in the initial install on a 600Gb drive (on a box that also contained a larger raid). and it used a GPT. ReaR won't work to back up/restore this system, complaining about the UEFI. I cloned the drive to a different server with clonezilla-live which completed without errors but it won't boot. I booted an install disk in rescue mode, did a chroot to /mnt/sysimage and everything looked OK. A 'grub-install /dev/sda' did not give any errors and I can now get it to boot to the grub> prompt. What's the right way to fix the grub install here? -- Les Mikesell lesmikesell(a)gmail.com

4 8

*BAD*gran_size
by m.roth＠5-cent.us 13 Jun '13

13 Jun '13

CentOS 6.4, current, Dell PE R720. Had an issue today with a bus error, and googling only found two year old references to problems with non-Dell drives (we just added two WD Reds, and mdadm raided them). So, looking through dmesg and /var/log/messages, I ran into a *lot* of G gran_size: 128K chunk_size: 256K num_reg: 10 lose cover RAM: 0G gran_size: 128K chunk_size: 512K num_reg: 10 lose cover RAM: 0G gran_size: 128K chunk_size: 1M num_reg: 10 lose cover RAM: 0G gran_size: 128K chunk_size: 2M num_reg: 10 lose cover RAM: 0G gran_size: 128K chunk_size: 4M num_reg: 10 lose cover RAM: 0G gran_size: 128K chunk_size: 8M num_reg: 10 lose cover RAM: 0G gran_size: 128K chunk_size: 16M num_reg: 10 lose cover RAM: 0G gran_size: 128K chunk_size: 32M num_reg: 10 lose cover RAM: 0G gran_size: 128K chunk_size: 64M num_reg: 10 lose cover RAM: 0G gran_size: 128K chunk_size: 128M num_reg: 10 lose cover RAM: 0G gran_size: 128K chunk_size: 256M num_reg: 10 lose cover RAM: 0G gran_size: 128K chunk_size: 512M num_reg: 10 lose cover RAM: 0G gran_size: 128K chunk_size: 1G num_reg: 10 lose cover RAM: 0G *BAD*gran_size: 128K chunk_size: 2G num_reg: 10 lose cover RAM: -1G Googling finds various threads, and a bug or two, and one person has an answer of setting this in the kernel line in grub. HOWEVER, the one person who gave that thread's O/P what to put never responded to *how* he chose those parms. Anyone here have any idea how to chose them? mark

1 0

Link for Logical Volume has incorrect SE Linux context
by Clint Dilks 13 Jun '13

13 Jun '13

Hi A few days ago we rebooted a server and found that one of the Logical Volumes would not mount at boot, but mounted cleanly manually. So I traced the problem to SE Linux. Specifically the context for /dev/mapper/VolGroup01-lv_ staff is wrong. s -lsahZ /dev/mapper/VolGroup01-* lrwxrwxrwx. root root system_u:object_r:quota_db_t:s0 /dev/mapper/VolGroup01-lv_staff -> ../dm-25 lrwxrwxrwx. root root system_u:object_r:device_t:s0 /dev/mapper/VolGroup01-lv_student -> ../dm-24 I have tried to correct this with the Logical Volume active and mounted using chcon -v --reference /dev/mapper/VolGroup01-lv_student /dev/mapper/VolGroup01-lv_staff and while this command completes the context is not changed. Can someone confirm or deny that making the Logical Volume inactive and then repeating the chcon should change the link to the correct context? Thanks for any insight you can offer.

3 3

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss