Discuss

discuss@lists.centos.org

34753 discussions

need texlive & lyx-1.55 for Centos 5.2
by Paul Johnson 16 Jul '08

16 Jul '08

Today I installed the newest Centos I could find and encountered the old software problem. I couldn't find any third party repositories that have TexLive to replace tetex. Ii tried the Fedora version, but it calls for a different libpoppler. LyX in Centos is aged as well. As far as I can tell, rpmfusion will provide these things, but its confiig page still says 'not ready.' I followed quite a few blind alleys trying to work this one out. Got advice? I'm looking for an RPM based distro that is conservative on the kernel updates, but not so slow on apps. I don't want Fedora b/c the lifespan is too short. PJ ps. already tried EPEL and rpmforge. No Centos packages show up in rpmfind.net -- Paul E. Johnson Professor, Political Science 1541 Lilac Lane, Room 504 University of Kansas

2 1

settings up cheap a NAS / SAN server, is it possible?
by Rudi Ahlers 16 Jul '08

16 Jul '08

Hi all I want to look at setting up a simple / cheap SAN / NAS server using normal PIV motherboard, 2GB (or even more) RAM, Core 2 Duo CPU (probably a Intel 6700 / 6750 / 6800) & some SATA HDD's (4 or 6x 320GB - 750GB). My budget is limited, so I can't afford a pre-built NAS device. Can this be done with CentOS? I've been looking FreeNAS (which is built on FreeBSD), and it look like a great project, but since the hardware support in FreeBSD is limit, I'd rather use Linux for it. Has anyone done this? If so, please share a bit in your experiences :) -- Kind Regards Rudi Ahlers CEO, SoftDux Web: http://www.SoftDux.com Check out my technical blog, http://blog.softdux.com for Linux or other technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting stuff

19 69

Help with iptables rule for blocking UDP port 53
by Sean Carolan 16 Jul '08

16 Jul '08

I would like to block all DNS queries that come from one particular ip address. I used TCPdump to verify that the queries were in fact, coming from this IP: [scarolan@server:~]$ sudo tcpdump -n udp port 53 and src 10.100.1.1 tcpdump: listening on eth0 11:12:17.162100 10.100.1.1.19233 > 10.100.1.61.domain: 14270+ A? server.domain.com. (32) (DF) Could someone help with the proper syntax for an IPtables rule to block port 53 udp traffic from this IP? I tried this rule but it doesn't work: -A RH-Firewall-1-INPUT -s 10.100.1.1 -m udp -p udp --dport 53 -j REJECT

5 12

Stopping a server not controled by service
by Robert Moskowitz 16 Jul '08

16 Jul '08

Miredo is run as a server from the command line: /usr/sbin/miredo The man page says the signal SIGTERM stops the server. How do I send SIGTERM to the server? Or SIGHUP, as I want to make a change to the config file. And once I get this as I want it, how do I run it at system boot?

7 15

RADVD and default IPv6 gateway
by Robert Moskowitz 16 Jul '08

16 Jul '08

the man page for RADVD says: radvd is the router advertisement daemon for IPv6. It listens to router solicitations and sends router advertisements as described in "Neighbor Discovery for IP Version 6 (IPv6)" (RFC 2461). With these advertise- ments hosts can automatically configure their addresses and some other parameters. They also can choose a default router based on these adver- tisements. But there is nothing I see in man radvd.conf that answers how hosts choose a default router, nor can I find anything else about this. Anyone know the answer or where to get the information???

2 3

Documentation file for ifcfg options
by Robert Moskowitz 15 Jul '08

15 Jul '08

Sometime in the past two weeks, Some kind person pointed me to a GREAT document file that explained all those commands you find in the ifcfg-* files and the network file (and others, I believe). It was a great help to me, and now I need it again, and I did not write down the file location, nor can I find that original note. My bad, I am busy documenting everything I can now. But I really need that info. Can someone point me to file again?

3 3

can I host a Ubuntu / Gentoo repository on a CentOS server?
by Rudi Ahlers 15 Jul '08

15 Jul '08

Hi all I was wondering if someone could answer this one for me. How do I host a different Linux OS repository(s) on my CentOS server? -- Kind Regards Rudi Ahlers CEO, SoftDux Web: http://www.SoftDux.com Check out my technical blog, http://blog.softdux.com for Linux or other technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting stuff

9 13

Test - you don't need to read it
by Sergio Belkin 15 Jul '08

15 Jul '08

-- -- Open Kairos http://www.openkairos.com Watch More TV http://sebelk.blogspot.com Sergio Belkin -

1 0

Bug-buddy and bug reports for GNOME 2.16...
by MHR 15 Jul '08

15 Jul '08

There seems to be some hostility to the idea of this being a GNOME or Evolution problem: Bug 542280 – Refuses to report bugs because gnome 2.16.x is too old View Bug Activity Product: bug-buddy Component: general Version: 2.16.x Status: RESOLVED Resolution: WONTFIX Opened by Mark Hull-Richter (reporter, points: 3) 2008-07-09 23:40 UTC [reply] On CentOS 5.2 (and 5.1 and 5.0, and Red Hat Enterprise Linux of the same versions, which happen to be the most current ones available), the bug buddy "tool" consistently refuses to report any bugs because it claims that the version of Gnome is too old. This is unacceptable - Gnome 2.16.x is the /standard/ release with RHEL and CentOS distributions of Linux/Gnome. There are too many issues that can (and do) come up for the tool simply to refuse to report a bug for this reason. Comment #1 from Cosimo Cecchi (points: 22) 2008-07-14 20:29 UTC [reply] This is intentional and isn't a bug-buddy issue. Bugzilla only accepts crashers from the two most recent stable releases (e.g. now that 2.22 is the current stable, it rejects everything <= 2.19.99). This is because we can't support every stable branch, as the codebases evolve and backporting fixes would be nearly impossible. If you need a specific fix, please backport it yourself in your distribution (like RHEL does I think) or just use newer releases. I'm closing this as WONTFIX, please file a bug under bugzilla.gnome.org component if you need more explanations, thanks. Comment #2 from Andre Klapper (points: 28) 2008-07-14 20:46 UTC [reply] It's not our problem that CentOS and RHEL ship ancient software. Ask them to patch bug-buddy to report against their distribution bug tracker instead of GNOME Bugzilla. We are definitely not interested in bugs that probably have been fixed for ages and 95% of those ancient reports are dups anyway. If you volunteer to triage all that useless incoming stuff, okay. We definitely don't want to, we got better stuff to spend our time on than 2.16 that in fact nobody works on, except for two LTS distros. LTS? Long Term Support? So much for that effort. Any chance of CentOS (or RHEL) patching bug-buddy as suggested in #2, above? Just curious.... Thanks, all. mhr

4 7

r8169-driver CentOS5.2
by Simen Timian Thoresen 15 Jul '08

15 Jul '08

Hi all, Another FYI-mail (and just to verify that I'm not going insane here); I recently purchased an ASUS M3A78-EMH HDMI -board with a tri-core Phenom. This is a small uATX-board with all the garnish integrated motherboards are supposed to come with, and fairly well supported in CentOS 5 and other modern distros. When I installed it (~2 months ago) the NIC was not supported; Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) ...but Realtek provided a 2.6-kernel compatible r8168-driver; r8168-8.006.00 When the CentOS 5.2 updates were published, I saw to my happiness that the kernel-supplied r8169-driver now handled the NIC, and I had no reason to rebuild the r8168-driver to support the new kernel. Last time I rebooted, was July 2nd, to the 2.6.19-92.1.6.el5 kernel. Since then, the kernel supplied r8169-driver worked like a charm. The machine is a home file-server, serving files over NFS and SMB, and runs my torrent downloads. It also pulls CentOS updates. I would have noticed if it did not work. Today, I got around to replacing a failed disk, and after rebooting I had no network connectivity. The NIC displayed 'weird' symptoms; 10Mbps link as shown by ethtool, 100Mbps link as shown by the link-indicator on the switch, ifconfig showed no TX-packets, some RX-packets, /billions/ of dropped packets - increasing by millions every second. The kernel log showed multiple 'Link down' entries. After digging around a little, swapping switch-ports, yattayatta, I unloaded the r8169-module (rmmod) and built and loaded the Realtek-supplied r8168-module. Link up, packtes going in and out, no dropped packets, GigE link, etc etc. At this point I have no idea what actually happened. I'm thinking some weird state on the PHY of the NIC (I've seen this on the Nvidia NICs) that was not flushed due to a too short power-loss, or possibly that the r8168-driver sets some PHY-state that was not lost at the kernel-update that brought me the 'working' r8169-driver, or something similar. I'm taking suggestions, tho. Anyone else with this same board, CentOS 5.2 (x86_64) and using the r8169-driver? -S -- Simen Thoresen, Dolphin ICS Systems Administration and Wulfkit Support

2 2

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