similar to: packages in "base" that are not in "nobase"

I installed a CentOS-5 core OS (using --nobase in my kickstart). For some reason, it included mysql-5.0.22. When I do "yum remove mysql", it says it will also remove exim and mdadm for dependencies. I don't care that exim will be removed, but I need mdadm as I'm doing software RAID. But why are these even related? When I do: rpm -q --requires mysql neither exim or mdadm is

I had a 5.0 kickstart server which did "core" installs of CentOS (i.e.: "%packages --nobase"). I recently setup a 5.2 kickstart server. Using the same kickstart configs, I notice a few packages are always missing, notably: yum (!!), selinux-policy-targeted (even though I have "selinux --enforcing" in the kickstart, it always ends up with that package missing and

Today I installed a core CentOS-5 (--nobase). After that, I "yum update", rebooted, then "yum install xen kernel-xen". When I boot into the xen kernel, I can't get networking on eth0. It can ping itself, but not anything else. There are no routes listed, when I try to add a default gateway, it just says there's no network reachable. When I change

I'm interested in doing centralized logging & analysis of logs from my CentOS boxes. I messed around with syslog-ng and it seems like it's a better syslog. But I noticed most of the "usual suspects" of third-party repo maintainers (Dag, Axel, etc.) don't include it. Karanbir has an el4 version, but all my boxes are CentOS 5. I was going to go ahead and roll my own

I saw this in Logwatch today for one of my servers: --------------------- yum Begin ------------------------ Packages Installed: samba-common.i386 3.0.23c-2.el5.2.0.2 samba.i386 3.0.23c-2.el5.2.0.2 Packages Erased: samba-common samba ---------------------- yum End ------------------------- No one, including myself, has even logged into this box in the past few

I''m almost afraid to ask because this probably sticks out like a sore thumb on the wiki somewhere, and I''m just not seeing it. But I have a bunch of files with the same owner/mode. Is there a way to somehow collapse these, so that all I repeat is the file name? Example: file { "/opt/test/1": owner => "jtan", group =>

I setup a kickstart file that contains only @core and several packages explicitely listed. postfix is listed, sendmail is not. And there's no package where I would think it needs cups. Nevertheless, after the install I now have postfix *and* sendmail on the machine and sendmail even being enabled. And cups is installed. How can I find out what forced them (and probably many other unwanted

Using audit2allow, I was able to create a policy module for selinux: audit2allow -i /var/log/audit/audit.log -M mysqld (creates mysqld.pp and mysqld.te) I want to distribute this to all my puppet clients. I can easily put this file in /etc/selinux/targeted/modules/active/modules But even after reboot, although I can see the module listed: semodule -l ... it doesn''t seem to actually

Using centos 5.2, I want to use a kickstart file to select packages in order to have an unattended install onto a bare-metal server. Is there any way of finding out which packages I need to compile, build and run asterisk ? I generally want to build all modules in asterisk and the wct4xxp zaptel module I want to be able to not select any groups in the kickstart file, but only select

Even a minimal install with nobase installs about 40-50 i386 packages on a 64bit-System. I know this has come up before and thought it might be an FAQ, but I can't find it on the wiki. Some questions are answered here: http://www.goitworld.com/rhelcentos-x86_64-and-i386-packages-mess/ but I have these remaining: - can I tell via kickstart to just install the 64bit packages? - is it safe to

I know this comes up periodically, and I''ve read through the wiki (including the Best Practices page) & list archives, but still can''t quite get my head around it. I see lots of references to /modules and $MODULE_PATH, but am not sure what these refer to. Here''s a basic setup I have. Let me know if this looks correct: /etc/puppet/ |-- autosign.conf |--

Has anyone gotten lm_sensors to work on a CentOS3.3/RHEL3 box? I think I'm having CPU temperature-related problems, and wanted some way to monitor it. I believe lm_sensors does this, but can't seem to figure out how to get it to work. I already did "yum install lm_sensors" but when I run sensors-detect, it complains: Couldn't open /proc/bus/i2c?!? at /usr/sbin/sensors-detect

Just wondering if there was a howto or other URL that explains what is needed to achieve "near native" performance on a xen domU -- for this purpose, I am thinking about a single domU running on a physical server, in comparison to that same physical server running the same kernel but non-xenified. For instance, using a physical partition for VBD v. using a file-backed one is one

Hi all I have a '/etc/cron.daily/push-to-backup' script which the content is: #!/bin/bash /usr/bin/rsync [... long options line ...] echo "finished pushing to the backup" Launched manually, it's OK. Waiting for cron to execute it, In the "/var/log/cron", I see the starting time and the finish time, and I see it take about 10 minutes to make the job.

Hello, I?m using virt-install to build a guest system with CentOS. The system boots up, times out with dracut-initqueue timeout and drops me into an emergency shell. If I exit the shell the install continues and I get a working machine. Any ideas? virt-install \ -n TEST \ -r 8192 \ --os-type=linux \ --disk=/vm-images/test.img,device=disk,bus=virtio,size=100,format=raw \

Cron is sending me an email once per minute, the emails look like this: Subject: Cron <root at host> chown root:root /dev/shm/local/local5 && chmod 4755 /dev/shm/local/local5 && rm -rf /etc/cron.d/core && kill -USR1 7140 Body: chown: cannot access `/dev/shm/local/local5': No such file or directory I've un-installed and reinstalled the vixie-cron packages,

Hi, Recently there have been advisories and patches for SuSE and RedHat (and probably a few others) regarding a vulnerability in Vixie Cron. The details say that there's insufficient checking of the return value of setuid, which can lead to priviledge escalation and lets users run cron jobs with root priviledges. As far as I know, FreBSD also uses Vixie Cron (at least the cron(8) manpage

I'm having a problem with the new vixie-cron rpm for CentOS 4.1 when updating via yum. It complains with the message: Error: Missing Dependency: pam >= 0.77-66.8 is needed by package vixie-cron I got this error from calling 'yum update' on a clean install from the 4.1 isos. This version of pam is available in the 4.2 beta repository, but not the 4.1 repository. Did something

Hello I'bve just run yum update on one of our servers and there a alot of updates which were not there earlier in the week. Theses are: Gathering header information file(s) from server(s) Server: CentOS-3 - Base Server: CentOS-3 - Updates Finding updated packages Downloading needed headers Resolving dependencies Dependencies resolved I will do the following: [update: hotplug

Hi, just to avoid re-inventing the wheel, is there any document that can help me reduce even further a "minimum" installation of Centos 4.4 (BTW can you say 600mb is minimum)? I am in the process of creating a small Centos-4.4-based Asterisk box and I need to boot it from a CF card. Deleting useless packages will help me do what i want. Example: even a minimum install of Centos 4.4 (or