Discuss

discuss@lists.centos.org

34753 discussions

SELinux Strict Mode
by Leonardo Vilela Pinheiro 03 Sep '06

03 Sep '06

According to http://www.redhat.com/magazine/006apr05/features/selinux/ there is a package named selinux-policy-strict, which contains a series of rules for correctly handling many situations (software) when using strict policy. Does CentOS have this package available ? If not, can someone make it available through Centosplus or Addon, for example ? This package is not part of the upstream main release, but according to the link above it is made available on their website for subscribers who want it. Anyway, I have just tried Fedora 4 package selinux-policy-strict-1.27.1-2.27.noarch.rpm. It might work, as it's just a package containing rules, but it's list of dependencies is incompatible, so I'd better leave it alone: rpm -Uvh selinux-policy-strict-1.27.1-2.27.noarch.rpm warning: selinux-policy-strict-1.27.1-2.27.noarch.rpm: V3 DSA signature: NOKEY, key ID 4f2a6fd2 error: Failed dependencies: kernel >= 2.6.11-1.1219 is needed by selinux-policy-strict-1.27.1-2.27.noarch libselinux >= 1.23.5-1 is needed by selinux-policy-strict-1.27.1-2.27.noarch policycoreutils >= 1.22-2 is needed by selinux-policy-strict-1.27.1-2.27.noarch Thanks -- Vilela

2 3

pppoe problems
by kai 03 Sep '06

03 Sep '06

I'm having problem connecting to my isp with my sangoma s518. Everything seems to run smooth and wanrouter are training to connect....but forever.. Now, to test the connection i mounted up my standard nic and my old dsl router, to establish a standard basic pppoe connection..... and I can't with centos. I follow this standard setup: http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/sysadmin-guide/… tested on two different centos installations, but no. I spent 4 hours I think and needed two minits on my debian installation. Both rp-pppoe and ppp are installed, please someone tell me what am I missing before I totally loose it :-) ? kai # tail -20 /var/log/messages Aug 29 21:40:35 localhost pppd[21465]: pppd 2.4.2 started by root, uid 0 Aug 29 21:40:35 localhost pppd[21465]: Using interface ppp0 Aug 29 21:40:35 localhost pppd[21465]: Connect: ppp0 <--> /dev/pts/4 Aug 29 21:41:06 localhost pppd[21465]: LCP: timeout sending Config-Requests Aug 29 21:41:06 localhost pppd[21465]: Connection terminated. Aug 29 21:41:10 localhost pppoe[21466]: Timeout waiting for PADO packets Aug 29 21:41:10 localhost pppd[21465]: Exit. Aug 29 21:41:10 localhost adsl-connect: ADSL connection lost; attempting re-connection. Aug 29 21:41:15 localhost pppd[21553]: pppd 2.4.2 started by root, uid 0 Aug 29 21:41:15 localhost pppd[21553]: Using interface ppp0 Aug 29 21:41:15 localhost pppd[21553]: Connect: ppp0 <--> /dev/pts/4 Aug 29 21:41:46 localhost pppd[21553]: LCP: timeout sending Config-Requests Aug 29 21:41:46 localhost pppd[21553]: Connection terminated.

6 6

Release 4.4 and MPC51 ethernet controller
by Jerry Geis 03 Sep '06

03 Sep '06

When using 4.4 to install on gigabyte GA-M51GM-S2 motherboard basically an Nforce 410/430 chipset then network is not initially detect to perform a network install. It let me attempt to manually select a driver but I do not see the driver in the list. After installing the network works and the forcedeth driver is loaded. Is there a way to get this driver detected or manually loaded? THanks, jerry

5 4

ipw2200 Stats MT in /proc/net/wireless
by Ben Mohilef 03 Sep '06

03 Sep '06

In 5100 and 1100 series Inspirons Intel 2915abg cards work MUCH cooler than the original Broadcoms, don't choke up in hot weather like the original Dell cards and don't require ndiswrapper. (All of 2 Notebooks were tested outdoors at 98 deg F ambient. Dropouts occured in both Centos 4.4 & XP on these dual boot notebooks with the Dell Mini-PCI's, none with 2915's). The only problem is that there are no wireless stats showing up in /proc/net/wireless (running wpa2, although that shouldn't make a difference). The /proc/net/wireless file claims that the Extensions are at Version 18 which should include the ipw_get_wireless_stats() call. Dmesg tells me nothing of interest about this (admittedly noncritical) issue. What am I missing here? Is the appropriate version of ipw-firmware needed other other than 2.4 or 3.0 ? [REPOST -- Original Post Never Appeared ]

1 0

Beranger: Updating to CentOS 4.4: Possible Issues and Small Hints
by Larry Vaden 03 Sep '06

03 Sep '06

<http://beranger.org/index.php?categ=17&offset=0>, but nothing specific about the named/bind showstopper. rgds/ldv

2 2

Sendmail restriction
by Ugo Bellavance 03 Sep '06

03 Sep '06

Hi, I'm looking for a way, in sendmail, to set access rule, saying: Accept messages for domain.com only from this IP address. I did some research yesterday, but could only find a way to restrict by IP for all domains managed by sendmail. Any ideas? Regards, Ugo

7 12

CentOS needs some love at DistroRankings.com
by Akemi Yagi 03 Sep '06

03 Sep '06

Johnny Hughes wrote: > / Guys, />/ />/ CentOS is not doing very well at this ranking site: />/ />/ http://www.distrorankings.com/ />/ />/ We need some good foo there, so if you like CentOS, go there and rank />/ us ... />/ />/ {If you don't like CentOS then you are getting sleepy .... sleepy ..... />/ You will not remember anything you read in this message} />/ />/ Thanks, />/ Johnny Hughes />/ />/ ------------------------------------------------------------------------ />/ />/ _______________________________________________ />/ CentOS mailing list />/ CentOS at centos.org <http://lists.centos.org/mailman/listinfo/centos> />/ http://lists.centos.org/mailman/listinfo/centos // / I am new to CentOS. Have been running it on a test machine for about 3 weeks now. And I already like it, so poured lot of love on the ranking site. Look, Ma, CentOS is on top of the world. Honestly, I had never heard of the name CentOS until March this year when I also learned about the little city Tuttle.... The fact that the person behind the project is so patient made me feel this is the distro to use. Having used RedHat/Fedora for many years, I found myself quite comfortable on the first day I installed CentOS. Glad I found you, CentOS. Akemi

5 4

Kernel-2.6.9-42.0.2EL fails to boot after upgrade to CentOS 4.4
by Johnny Hughes 02 Sep '06

02 Sep '06

---On Sat, 2006-09-02 at 07:42 -0500, Gerald Waugh wrote: We have a problem with upgrade to 4.4 When we run 'yum update' everything appears to be OK But, if we reboot the server with the new kernel, we get "kernel panic" when the new kernel attempts to load. The CentOS splash screen shows briefly, but not long enough to select the old kernel Gerald (let's try it like this ... johnny :)

9 18

Cron Problem
by Matthew T. O'Connor 02 Sep '06

02 Sep '06

Cron is sending me an email once per minute, the emails look like this: Subject: Cron <root@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, I have verified that they are not corrupted by using rpm --verify vixie-cron, I have checked all the crontabs on the system there aren't any running every minute. I don't understand why this is happening, anyone have any insight? Thanks, Matt

4 5

CentOS 4.4 LILO Raid (also e2fsprogs in general)
by Benjamin Karhan 02 Sep '06

02 Sep '06

i noticed that the 4.4 upgrade broke LILO on Raid... it gave errors on partitions not on the primary disk along the lines of "/dev/dis: no such device"... even explicitly installing the boot sector on each device in the array, while it allowed the system to boot, gave errors at boot time and did not display the CentOS boot screen anymore... i solved the problem by creating a package for the most recent version of LILO and installing that... with a few minor changes to "lilo.conf" everything was kosker for LILO install and boot... i even made a nice new 640x480x256 CentOS boot screen for it... there is one caveat to using the new LILO... the new version (or at least one above 22.x) must be booted once (text-mode) before LILO can correctly probe the video BIOS... so, the boot screen needs to be installed after an initial priming boot... afterwards, i did some thorough testing before deploying on any production servers... and noticed only one problem... the new version of LILO broke the "grubby" probe... primarily because "/boot/boot.b" is no longer needed... but also because the comparisons between "boot.b" and the actual boot sector aren't accurate anymore either... since i'd noticed that "grubby"'s probe for GRUB itself has been broken for a while... i decided a quick patch-job for the "mkinitrd" package was in order... my new package correctly identifies whether either LILO or GRUB has been installed at all, but lacks the careful byte comparisons that were the core of the breakage of the original "grubby"... it's possibly problematic... but i doubt it... and it solves more problems than it creates... anyways... that solved my 4.4 upgrade breakage... and... since i was writing to the list... i figured i should mention a rather serious, but extremely unlikely to happen, bug i noticed in "e2fsprogs" (specifically "e2fsck")... with the version on CentOS... "e2fsck" will cause some big problems and potential data loss on directories containing more than 1.2 million inodes... the first 1.2 million inodes will be ok... the next 1.2 million (max) will be saved to /lost+found as unidentified files... before it too fills up... and then everything else will just "vanish"... this problem is due to some incorrect math in the handling of the maximum inode size... and has already been fixed in e2fsprogs 1.38... so, my solution was to take the 1.38 Fedora Core sources and build a package for CentOS... if anyone is particularly interested... i have the SRPMS for my lilo, mkinitrd, and e2fsprogs packages... also, i have the pretty new CentOS boot screen (and a few others i made) and some working lilo configurations for switching over to them... all of which i could probably post somewhere public... but if they are really useful, i'd rather ship them along to someone more closely involved in maintaining CentOS... so as to "contribute" as best i could to everyone's future well-being as well... B. Karhan simon(a)pop.psu.edu PRI/SSRI Unix Administrator

1 0

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