Discuss

discuss@lists.centos.org

34758 discussions

DVD install via NFS asks for CD #1 ISO
by Marco Fais 16 Apr '07

16 Apr '07

Hi all, I'm installing Centos 5.0 (fresh install) x86_64 via NFS. I've downloaded just the DVD iso via bittorrent, but when it starts the graphical installation phase an error message appears telling me that anaconda can't find the CD iso in the remote server. Seems that's looking for Centos-5.0-x86_64-bin-1of7.iso, I'm downloading it right now to go ahead but... I think I'm doing something wrong or there is some problems in the NFS DVD install... Anyway, thanks for the great work folks! Let me know if you need more informations, bye!

3 3

Problem installing CentOS 5.0
by Varian 16 Apr '07

16 Apr '07

I decided to replace Suse 10.1 with Centos 5.0 on my file server. Im getting stuck right after I select the keyboard layout. I get the following message on the console: /dev/sdb: "sil" and "pdc" formats discovered ( using pdc)! and it just hangs there. I think sil and pdc are referring to the onboard raid chips that the drive was attached to. This drive was used in a machine with a Silicon Image raid chip and a Promise raid chipset in the past, now its attached to onboard nvidia based controller but not in raid mode. I tried to low level format the drive and it sill did not work. Any ideas, I don't have this problem with Suse or Freebsd.

1 1

Hot swapping drives
by Ashley M. Kirchner 16 Apr '07

16 Apr '07

If I have a board that supports hot swapping SATA drives, what do I need to have in terms of installed utilities for it to work with CentOS 4? (There's all kinds of information from the board's manual for things like Windows flavors, but nothing on unix, as to always...) -- W | It's not a bug - it's an undocumented feature. +-------------------------------------------------------------------- Ashley M. Kirchner <mailto:ashley@pcraft.com> . 303.442.6410 x130 IT Director / SysAdmin / Websmith . 800.441.3873 x130 Photo Craft Imaging . 3550 Arapahoe Ave. #6 http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A.

3 6

Beta upgrade (could not find a decent answer yet)
by Evans Mitchell 16 Apr '07

16 Apr '07

Greetings All from Florida. As of tonight, Sunday April 14th, 07, I finished loading the dvd iso of 5 beta (or 4.92 as it is shown to be) and went archive diving to see what was up with the updater not finding the 4.92 files on the mirrors.. I only saw a few notes about removing a dev file and something else, then a comment about removing an image file, then a comment about not doing it in X as there is a bug....... Has anyone find a simple way to force yum to update without looking at the current version?? or at least telling the system to go get centos 5 even thou it is 4.92?? Any ideas would be great, as I am trying to take a crack at upgrading my Knopixx FADCA box to CentOS and seeing what all I can make out of the thing.... ALSO how do I go about enabling ax25 kernel support with the CentOS 5 releases??? Full of questions and what not... nah, just wanting to make use of this stuff before I upgrade my IRLP nodes to CentOS 4 that was just released to us recently from irlp.net 73 Evans Mitchell kd4efm / afa2th FL / WQFK-894 GMRS Lakeland, FL. USA

3 2

Looking for a better way to build
by Mark Hull-Richter 16 Apr '07

16 Apr '07

I have been following the wiki on how to build a custom kernel, and it works great. Except, I am doing ongoing work with the internals of the kernel, and it is really awkward to set up a change and then build it using the standard methodology (edit the file to change, diff it against the original to make a patch file, rebuild the whole thing). Isn't there a way (and what is it) to play around with the kernel source files until they are in the shape I want them to be in, and THEN go through the whole build process again. Thanks. Mark Hull-Richter, Linux Kernel Engineer DATAllegro (www.datallegro.com) 85 Enterprise, Second Floor, Aliso Viejo, CA 92656 949-680-3082 - Office 949-330-7691 - fax

3 6

Scripts to generate exact copy of CentOS-5.0-i386-bin-DVD.iso from CD images
by Wojtek.Pilorz 16 Apr '07

16 Apr '07

I am enclosing scripts and config files to generate exact copy of CentOS 5.0 i386 installation DVD image, that is CentOS-5.0-i386-bin-DVD.iso if you have CD images for i386. If there is interest I can post the same for x86_64. Please follow README files for instructions. All the scripts are GPL. SHA1 for attached files: 439f7b0bd50722388a2836eedafeb1c227f97385 *00_README.txt 520e805b4c9386d1e08b3741337ee83afe60547d *DVDgen_bin_i386.tar.bz2 Best regards, Wojtek Pilorz

3 4

Many Fedora 6 packages in CentOS 5
by Frank Büttner 16 Apr '07

16 Apr '07

Why are there so many Fedora 6 packages in CentOS 5? Are there something wrong with the build system?

9 15

Migration from FC3 to Centos4.4 gives problems with Samba
by Theo Band 15 Apr '07

15 Apr '07

Hi I have updated one of my servers from Fedora Core 3 to Centos. All services run fine except Samba. The Centos installation is fresh and I setup Samba in a similar way as I did before with Fedora. I copied the samba password file from the Fedora installation and also all user+machine accounts to the /etc/passwd|shadow etc. Problem I now have is that clients cannot find their server profiles when they try to logon (bath owner rights, or profile is unavailable). After some trial I found out that I can solve this issue by removing the XP client computer form the domain and then adding the client computer again. So it looks to me that the client machine is not seen properly by Samba. Is there a way to copy information from the old installation to the new Centos installation so that I don't have to re-join every individual computer to the domain again? Or is there a way I can do this with Samba? Thanks for any help or suggestions. Theo

2 2

Multipath-root (mpath) problems with CentOS 5
by Pasi Kärkkäinen 15 Apr '07

15 Apr '07

Hi list! I have a server with dual port Qlogic iSCSI HBA. I set up the same LUN for both ports, and boot the CentOS installer with "linux mpath". Installer detects multipathing fine, and creates mpath0 device for root disk. Installation goes fine, and the system boots up and works fine after the install from the multipath root device. After install the setup is like this: LUN 0 on port 1: /dev/sda LUN 0 on port 2: /dev/sdb and those form mpath0 device, which works OK. But then comes the problem.. when I add another LUN for both ports, the setup is like this: LUN 0 on port 1: /dev/sda LUN 1 in port 1: /dev/sdb LUN 0 on port 2: /dev/sdc LUN 1 on port 2: /dev/sdd And now after rebooting the system, root device multipath (mpath0) doesn't work anymore.. initrd seems to use/mount /dev/sda* partitions instead of mpath0 device. In fact the whole mpath0 is not started up. The weird thing is that the other LUN is now using multipathing instead.. using mpath1 device. How can I fix that? I'd like to use multipathing for both LUNs, also for root device. If I regenerate initrd with verbose flag, it just sets up the mpath1, not mpath0. I guess that's because mpath0 is not running when regenerating initrd. I have edited /etc/multipath.conf and disabled the "blacklist" line, and added multipath-entries for both LUNs. So those should be fine.. Any ideas? Thanks! -- Pasi

2 3

RE: [CentOS] Difference between vi an vim on Centos5?
by Johnny Hughes 15 Apr '07

15 Apr '07

On Sun, 2007-04-15 at 06:09 -0400, Michael Velez wrote: > > > > -----Original Message----- > > From: centos-bounces(a)centos.org > > [mailto:centos-bounces@centos.org] On Behalf Of Sebastian Marten > > Sent: Sunday, April 15, 2007 5:30 AM > > To: CentOS mailing list > > Subject: [CentOS] Difference between vi an vim on Centos5? > > > > Hello, > > i have a little problem on OS5. > > On CentOS4 vi an vim are the same programs. > > On 5 vi have no syntax highlighting while vim have it. > > > > Whats wrong? > > > > Greetings, > > Sebastian > > In CentOS 4, by default vi is aliased to vim. The unaliased vi does not > have syntax highlighting. > > Could it be that vi is not aliased to vim by default in CentOS 5? Run the > 'alias' command to see a list of aliases. If you want to alias vi to vim, > just run: > alias vi=vim > > Michael I believe that root is the only user where this happens ...

3 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