Discuss

discuss@lists.centos.org

34753 discussions

Re: [CentOS] tinydns/djbdns opinion poll
by James B. Byrne 13 Feb '09

13 Feb '09

Message-ID: <4991E3B7.6090503(a)andrei.myip.org> On: Tue, 10 Feb 2009 12:29:43 -0800, Florin Andrei <florin(a)andrei.myip.org> wrote: >Jake wrote: >> >> We're about to start moving our public DNS to in-house managed >> servers. My first thought was "Linux + BIND" and we're done. >> Someone in another business unit's IT dept. has suggested >> tinydns be used. > > But things have changed. Nowadays Bind is solid enough. If > you're still worried about security issues (you shouldn't, > but I'm assuming the paranoid scenario) then CentOS has a > good SELinux policy around it, so just install the latest > CentOS, keep SELinux enabled, do a "yum update" every once > in a while, and be at peace. By the way, this is also the > most sweat-free solution from a sysadmining perspective. With one very large caveat. Be aware that updating bind via yum can result in your existing bind configuration files being renamed to something.rmpsave and your name server left in a dysfunctional state. I suggest that you consider excluding bind from normal updates and only update it when you are ready and able to check for possible configuration issues. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

8 17

Problem with PXEBOOT of diskless client -- fails to mount RAMDISK
by Robert Heller 13 Feb '09

13 Feb '09

I am having a problem with setting up diskless clients under CentOS 5.2. I have everything working under CentOS 4.7. This is an adaptation of the (somewhat old) Diskless Linux with PXE HOWTO by Gerd v. Egidy, originally at the URL http://www.intra2net.com/opensource/diskless-howto/, which is now defunt (there is a mirror of it at http://blog.chinaunix.net/u/2389/showart_82438.html) What I am doing is using a RAMDISK to mount a NFS exported (read-only) root file system and copying part of it to a RAMDISK root file system, all of this after configuring the clients ethernet (via DHCP) and loading the NFS modules. The RAMDISK uses a statically built BusyBox for all of its functions, including ash. I am using the stock syslinux, dhcpd, tftp-server, and kernel RPMS. My /tftpboot directory contains: sauron.deepsoft.com% dir -l /CentOS52/tftpboot/ total 10012 -rw-r--r-- 1 root root 8388608 Feb 12 14:26 pxeboot-2.6.18-92.el5.img -rw-r--r-- 1 root root 13148 Feb 11 16:27 pxelinux.0 drwxr-xr-x 2 root root 4096 Feb 12 14:37 pxelinux.cfg/ -rw-r--r-- 1 root root 1806388 Feb 11 16:26 vmlinuz-2.6.18-92.el5 sauron.deepsoft.com% dir -lhR /CentOS52/tftpboot/ /CentOS52/tftpboot/: total 9.8M -rw-r--r-- 1 root root 8.0M Feb 12 14:26 pxeboot-2.6.18-92.el5.img -rw-r--r-- 1 root root 13K Feb 11 16:27 pxelinux.0 drwxr-xr-x 2 root root 4.0K Feb 12 14:37 pxelinux.cfg/ -rw-r--r-- 1 root root 1.8M Feb 11 16:26 vmlinuz-2.6.18-92.el5 /CentOS52/tftpboot/pxelinux.cfg: total 16K -rw-r--r-- 1 root root 101 Feb 12 14:37 default -rw-r--r-- 1 root root 134 Feb 12 14:09 default~ and /CentOS52/tftpboot/pxelinux.cfg/default contains: sauron.deepsoft.com% cat /CentOS52/tftpboot/pxelinux.cfg/default LABEL linux KERNEL vmlinuz-2.6.18-92.el5 APPEND ramdisk_size=8192 initrd=pxeboot-2.6.18-92.el5.img vmlinuz-2.6.18-92.el5 is the stock kernel, copied from /boot pxeboot-2.6.18-92.el5.img is a 8meg EXT2 filesystem image (under CentOS 4.7 the image is compressed, under CentOS 5.2, I have it uncompressed -- I seem to get 'further' that way). The last thing the kernel writes out is: RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 8192KiB [1 disk] into ram disk... done. EXT2 fs: blocksize too small for device. grow_buffers: requested out-of-range block 18446744071562067968 for device ram0 isofs_fill_super: bread failed, dev=ram0, iso_blknum=17, block=-2147483648 No filesystem could mount root, tried: ext2 iso9660 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,3) Under CentOS 4.7 (*stock* kernel version 2.6.9-67.0.22.EL), the ramdisk is uncompress, mounted, and the linuxrc script runs. Once the root file system is NFS mounted and setup, the normal boot process continues to completion. *Something* seems to be different with CentOS 5.2, and things don't seem to work and I cannot figure it out. I've looked through all of the kernel documents, but I am not finding any clues. -- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller(a)deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/

3 2

ext4 in 5.3
by Jerry Geis 12 Feb '09

12 Feb '09

Hi guys - I'm really looking forward to 5.3 for the potential of ext4. I am moving/copying image files lately 8G file and it is slow. I am hoping that ext4 really speeds that up. My question is: will we be able to boot ext4 file systems? Will the boot partition still be ext3 and then have to mount the ext4 filesystem? I did not see mention of it in the release notes. Thanks, Jerry

15 18

Re: [CentOS] tinydns/djbdns opinion poll
by James B. Byrne 12 Feb '09

12 Feb '09

Message-ID: <VA.000036bd.05799d0c(a)news.conactive.com> On: Thu, 12 Feb 2009 10:31:23 +0100, Kai Schaetzl <maillists(a)conactive.com> wrote: > > Ian Forde wrote on Wed, 11 Feb 2009 20:01:21 -0800: > >> locate rpmsave >> locate rpmnew > > rpmsave is left from *un*installations, rpmnew is the *new* file, > there is no file overwritten. rpm usually doesn't overwrite files > if they got changed. And I haven't seen any overwrites with all > the bind updates in the past months. So, I cannot back James' > claim. > > Kai I cannot answer whether this situation is still the case, and I know that it was not always the case, but on the last but one update to bind my configuration files were all renamed to .rpmsave and there were no .rpmnew files created, only the default config files left in place of the old ones. I also believe, be cannot be sure, that this particular revision was a "minor" (9.X.y) as opposed to "tiny" (9.x.Y) update. I also believe that the same thing happened on the last update as well but, as I now do bind updates far more circumspectly, I may simply be confusing the present remedy with the original problem. In any case, the problem was not expected and it caused considerable grief until the problem was identified and the cause determined. It is just something that anyone hosting their own DNS should consider. The consequences of a dysfunction name server can be quite severe and can initially evidence itself in places that one would not immediately associate with DNS issues. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

3 2

Missing EL4 glibc update
by CentOS User 12 Feb '09

12 Feb '09

Seeing upstream has an update for glibc http://rhn.redhat.com/errata/RHBA-2009-0052.html I rebuilt the glibc-2.3.4-2.41.el4_7.1.src.rpm and it produced the following rpms :- glibc-2.3.4-2.41.el4_7.1.i386.rpm glibc-common-2.3.4-2.41.el4_7.1.i386.rpm glibc-debuginfo-2.3.4-2.41.el4_7.1.i386.rpm glibc-debuginfo-common-2.3.4-2.41.el4_7.1.i386.rpm glibc-devel-2.3.4-2.41.el4_7.1.i386.rpm glibc-headers-2.3.4-2.41.el4_7.1.i386.rpm glibc-profile-2.3.4-2.41.el4_7.1.i386.rpm glibc-utils-2.3.4-2.41.el4_7.1.i386.rpm nptl-devel-2.3.4-2.41.el4_7.1.i386.rpm nscd-2.3.4-2.41.el4_7.1.i386.rpm Is it okay to install all of them or should i skip the debuginfo rpms? Is an official CentOS update going to be made of the glibc from Red Hat?

4 4

Question on canada
by Jerry Geis 12 Feb '09

12 Feb '09

I have a possible customer in canada. Can I export a machine pre-loaded with centos to canada? Jerry

4 3

Logrotate base
by Fajar Priyanto 12 Feb '09

12 Feb '09

Hi guys, Logrotate is checked every day by cron.daily, right? I notice in logrotate.conf by default it's weekly. If I change it into monthly (now, on 12 of Feb), when will it do the monthly rotation? a. On 12 of March or b. On 1st of March? Thanks for any insight.

4 6

Re: [CentOS] Missing EL4 glibc update
by CentOS User 12 Feb '09

12 Feb '09

> Kai wrote > This question is rethorical, right? What is "rethorical" my learned friend? Do you have anything to contribute to the original topic other than showing that you may need an English dictionary?

1 0

CentOS-announce Digest, Vol 48, Issue 6
by centos-announce-request＠centos.org 12 Feb '09

12 Feb '09

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-2009:0261 Moderate CentOS 3 i386 vnc - security update (Tru Huynh) 2. CESA-2009:0261 Moderate CentOS 3 x86_64 vnc - security update (Tru Huynh) 3. CESA-2009:0012 Moderate CentOS 4 i386 netpbm - security update (Tru Huynh) 4. CESA-2009:0012 Moderate CentOS 4 x86_64 netpbm - security update (Tru Huynh) 5. CESA-2009:0261 Moderate CentOS 4 i386 vnc - security update (Tru Huynh) 6. CESA-2009:0261 Moderate CentOS 4 x86_64 vnc - security update (Tru Huynh) 7. CESA-2009:0261 Moderate CentOS 3 ia64 vnc - security update (Pasi Pirhonen) 8. CESA-2009:0261 Moderate CentOS 4 ia64 vnc - security update (Pasi Pirhonen) 9. CESA-2009:0012 Moderate CentOS 4 ia64 netpbm - security update (Pasi Pirhonen) 10. CESA-2009:0261 Moderate CentOS 3 s390(x) vnc - security update (Pasi Pirhonen) ---------------------------------------------------------------------- Message: 1 Date: Wed, 11 Feb 2009 19:55:04 +0100 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2009:0261 Moderate CentOS 3 i386 vnc - security update To: centos-announce(a)centos.org Message-ID: <20090211185504.GA1608(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2009:0261 vnc security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2009-0261.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/vnc-4.0-0.beta4.1.8.i386.rpm updates/i386/RPMS/vnc-server-4.0-0.beta4.1.8.i386.rpm source: updates/SRPMS/vnc-4.0-0.beta4.1.8.src.rpm You may update your CentOS-3 i386 installations by running the command: yum update vnc\* Tru -- Tru Huynh (mirrors, CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

mirroring centos servers
by fabian dacunha 12 Feb '09

12 Feb '09

Dear All, I have 2 server with almost identical configuration nd would like to mirror them bascillay i would like to use it as a firewall. i was thinking of linux HA but could not really find clear examples if it could achive my purpose apprecite if someone can help me of any site with examples on how to mirror 2 centos servers so i one fails the other works perfect thanks and really apprecite regards fabian -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

4 5

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