Discuss

discuss@lists.centos.org

5 participants
34752 discussions

kqemu centos3
by Dave 17 Nov '05

17 Nov '05

Anyone get kqemu to make in Centos3? I'm getting modules disabled messages, AFAIK module support is enabled, its the stock kernel. make[1]: Leaving directory `/tmp/qemu-0.7.2/mips-softmmu' make -C kqemu make[1]: Entering directory `/tmp/qemu-0.7.2/kqemu' make -C /lib/modules/2.4.21-37.EL/build SUBDIRS=`pwd` modules make[2]: Entering directory `/usr/src/linux-2.4.21-37.EL' The present kernel configuration has modules disabled. Type 'make config' and enable loadable module support. Then build a kernel with module support enabled. make[2]: *** [modules] Error 1 make[2]: Leaving directory `/usr/src/linux-2.4.21-37.EL' make[1]: *** [kqemu.o] Error 2 make[1]: Leaving directory `/tmp/qemu-0.7.2/kqemu' make: *** [all] Error 2

2 2

CESA-2005:810 / CESA-2005:811 -- missing src.rpms?
by Matthew Miller 17 Nov '05

17 Nov '05

Recent updates to gdk-pixbuf and gtk2 have the binary rpms in the updates tree, but not the src.rpms. I know we can just get those from Red Hat, but it's nicer if we've got a coherent, self-contained distribution here.... -- Matthew Miller mattdm(a)mattdm.org <http://mattdm.org/> Boston University Linux ------> <http://linux.bu.edu/>

2 3

RE: [CentOS] SELinux threads, cynicism, one-upmanship, etc.
by Brian T. Brunner 17 Nov '05

17 Nov '05

>All I want is enough power to do my job... and to not be distracted from *my* job to tackle what some stranger in Illinois thinks my job should be! SELinux is my alligator, not my swamp. CentOS4 allowed me to switch the thing off at install. Done. When SELinux is my job, I'll figure it out. Until then, I don't care who I irk, disappoint, or perturb by switching it off. Brian Brunner brian.t.brunner(a)gai-tronics.com (610)796-5838 >>> noyler(a)khimetrics.com 11/16/05 05:05PM >>> > The main reason I think sysadmins in general seem to hate SELinux is the > 'Mandatory' part of 'Mandatory Access Control' : that is, superuser power > is too addictive to get rid of, and SELinux can do away with 'superuser' > powers entirely. I disagree with this. The main reason I dislike SELinux is the way I was introduced to it. I wasted quite a bit of time on an issue before I even knew what SELinux was because it was turned on by default on an FC2 machine. I was asked by another admin to use FC2 on a particular job, and I never saw SELinux. The turning it on by default irked me. Superuser power as a trip is just silly. What's the difference? All I want is enough power to do my job. _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos ******************************************************************* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.hubbell.com - Hubbell Incorporated

1 0

CentOS-announce Digest, Vol 9, Issue 11
by centos-announce-request＠centos.org 17 Nov '05

17 Nov '05

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. CESA-2005:810-01: Important CentOS 2 i386 gdk-pixbuf security update (John Newbigin) ---------------------------------------------------------------------- Message: 1 Date: Thu, 17 Nov 2005 09:24:45 +1100 From: John Newbigin <jnewbigin(a)ict.swin.edu.au> Subject: [CentOS-announce] CESA-2005:810-01: Important CentOS 2 i386 gdk-pixbuf security update To: centos-announce(a)centos.org Message-ID: <437BB1AD.7030501(a)ict.swin.edu.au> Content-Type: text/plain; charset=us-ascii; format=flowed The following errata for CentOS-2 have been built and uploaded to the centos mirror: RHSA-2005:810-01 Important: gdk-pixbuf security update Files available: gdk-pixbuf-0.22.0-12.el2.3.i386.rpm gdk-pixbuf-devel-0.22.0-12.el2.3.i386.rpm gdk-pixbuf-gnome-0.22.0-12.el2.3.i386.rpm More details are available from the RedHat web site at https://rhn.redhat.com/errata/rh21as-errata.html The easy way to make sure you are up to date with all the latest patches is to run: # yum update -- John Newbigin Computer Systems Officer Faculty of Information and Communication Technologies Swinburne University of Technology Melbourne, Australia http://www.ict.swin.edu.au/staff/jnewbigin ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 9, Issue 11 **********************************************

1 0

Turning root partition into a RAID array
by Nigel kendrick 17 Nov '05

17 Nov '05

I have a CentOS 4.2 system that was set up VERY quickly following the demise of its former life as a CentOS 3 server - you don't want the full story, but it had to be done quickly to get a company up and working following a slight disaster involving an electrician, a portable appliance safety tester and a pulled power cable - anyway, here's where I am at... Everything is running fine but I now want to mirror the root partition (/dev/hda3). I have read quite a few set of notes on the theory but since they contain conflicting advice I am hoping someone here can set me straight - here's what IO want to do: hda3 and hde3 become a mirrored pair (/dev/md0) and this is mounted at boot time as / Is it as simple as a quick mdadm command and then an edit of /etc/inittab?? If I try and use mdadm right now I get complaints that /dev/hda3 is busy (fair enough) so I guess I need to be in less than 'full steam ahead' mode to make the change - over to you.... Thanks

7 15

question
by adrian kok 17 Nov '05

17 Nov '05

Hi all I have the following questions 1/ do you know how to interrupt the console to capture the message when the system is in booting 2/ I use "top" to monitor the process to output the file. but the file is empty. Do you know why? Thank you

2 3

Generate 32bit programs on x86_64 architecture?
by Michael Ubell 17 Nov '05

17 Nov '05

I'm trying to run purify on CentOS on an Intel Pentium 4/630 processor. Purify does not like the 64bit code. Is there some way to compile and run programs so that they are only using the 32 bit model? I tried gcc -m32 but then the system libraries come up missing. Purify engine: Error: Couldn't open the file crt1.o Purify engine: Error: Couldn't open the file crti.o Purify engine: Error: Couldn't resolve library directive: -ltcl8.4, (couldn't find library libtcl8.4.so or libtcl8.4.a). Purify engine: Error: Couldn't resolve library directive: -ldl, (couldn't find library libdl.so or libdl.a). Purify engine: Error: Couldn't resolve library directive: -lieee, (couldn't find library libieee.so or libieee.a). Purify engine: Error: Couldn't resolve library directive: -lm, (couldn't find library libm.so or libm.a). Purify engine: Error: Couldn't resolve library directive: -lc, (couldn't find library libc.so or libc.a). Purify engine: Error: Couldn't open the file crtn.o Purify engine: Error: Couldn't resolve library directive: -ldl, (couldn't find library libdl.so or libdl.a).

2 1

Problem with X...help please.
by Sanjay Arora 17 Nov '05

17 Nov '05

List: I am using Centos updated till date. Last night I shut down the system and X was working fine...today morning I start X and it does not work for my normal user. X starts for root & other users. The error output seems totally incomprehensibe and scrolls away from the screen too quickly. The /var/log/Xorg.0.log seems to have only the subsequent success of login of other user or I can't seem to find the correct error in it. Only thing I did yesterday in addition to normal browsing & emailing & yum updation...was to install the Yahoo messenger for RH9...was said to be compatible with ES4 and it did work perfectly fine. How do I startx X for the user it is not starting for? or at least where do I find the errors to report. Only display 0 setup for X. Help a desperate man please !! ;-((( Sanjay. --------------------------------- Yahoo! FareChase - Search multiple travel sites in one click.

3 2

RE: [CentOS] SELinux threads, cynicism, one-upmanship, etc.
by Nathan Oyler 16 Nov '05

16 Nov '05

> Ummm, why were you installing Fedora Core 2 in a _production_ > environment? > > I mean, I'm all for Fedora Core in a production environment, > but _not_ the latest version that changes everything (which > Fedora Core 2 did). Yikes! It was a request I had nothing to do with. I didn't say it was an entirely reasonable argument, but those were my feelings. I wouldn't have installed FC2 if that wasn't what was forced on me. I have my domains, and this wasn't one of them. But yes, you're right.

1 0

RE: [CentOS] SELinux threads, cynicism, one-upmanship, etc.
by Nathan Oyler 16 Nov '05

16 Nov '05

> The main reason I think sysadmins in general seem to hate SELinux is the > 'Mandatory' part of 'Mandatory Access Control' : that is, superuser power > is too addictive to get rid of, and SELinux can do away with 'superuser' > powers entirely. I disagree with this. The main reason I dislike SELinux is the way I was introduced to it. I wasted quite a bit of time on an issue before I even knew what SELinux was because it was turned on by default on an FC2 machine. I was asked by another admin to use FC2 on a particular job, and I never saw SELinux. I turn it on now for all machines, but if you were to have asked me at any point in the week my feelings on SELinux they would have not been pleasant. At the time, I looked and there wasn't any real documentation for what I was trying to do, and why it failed. Now after time has passed, I realize what was going on but when you're in the middle of a job on a time crunch, the last thing you want to do is learn a new security system. I turned the thing off. Got what I needed done, and came back to the issue at a later date. The turning it on by default irked me. Superuser power as a trip is just silly. What's the difference? All I want is enough power to do my job.

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss