Discuss

discuss@lists.centos.org

5 participants
34752 discussions

Delay during boot up
by Dave Gutteridge 10 Sep '05

10 Sep '05

CentOS has recently started booting slower than it did before. Just when X starts up and the screen is dark blue and the only thing is the hour glass in the middle of screen turning round and round. It stays like that for quite a while, and then later it will resume the normal boot process. This long pause did not exist before. This seems to have started happening after I installed a FAT32 drive. So my guess is that for whatever reason, it takes CentOS a while to mount that drive. Actually, I'm a little concerned that maybe CentOS is doing something to the drive, some kind of directory reordering or something, because whenever I look at the drive from Windows and use Diskeeper (defragmenting software), it seems to have excessive fragmentation. But I don't know for sure that linux is doing anything to the drive, and I don't even know for sure that it's because of the drive that the boot process now has this added delay. So my first question, I suppose, is - What do I do to diagnose what is causing the delay in my boot process? Dave

3 3

SCSI controller setup
by James B. Byrne 09 Sep '05

09 Sep '05

I have an IDE based PC running Linux/CentOS4 to which I wish to attach a scsi dlt. The host controller is an Adaptec AHA3940 something that lspci reports as: SCSI storage controller: Initio Corporation 360P (rev 02). I would like to have the system load the driver for this adapter at boot but I have two problems: 1. I am not sure which driver to use; and 2. I do not know how to force Linux to load a driver module. My research to date indicates that the driver module for this device likely is one of: /lib/modules/2.6.9-11.EL/kernel/drivers/scsi/aic7xxx/aic7xxx.ko /lib/modules/2.6.9-11.EL/kernel/drivers/scsi/aic7xxx/aic79xx.ko /lib/modules/2.6.9-11.EL/kernel/drivers/scsi/initio.ko My reading of man modprobe.conf and modprobe lead me to conclude that the following needs to be added to /etc/modprobe.conf install <name of one of the above drives> alias scsi_host_adapter <name used for install> Can somebody confirm whether I am on the right track or not and provide some advice has to how to proceed? Which is the preferred driver for this card? Do I have to make additional entries for the tape drive itself an HP surestore dlt vs80? How do I create the necessary /dev/st# and /dev/mt# entries? Is there a Linux utility program like kudzu that can probe the hardware and automate any of this? I am a digest subscriber so replies that only go to the list will reach me in about 24 hours. Regards, Jim -- *** e-mail is not a secure channel *** mailto:byrnejb.<token>@harte-lyne.ca James B. Byrne Harte & Lyne Limited vox: +1 905 561 1241 9 Brockley Drive fax: +1 905 561 0757 Hamilton, Ontario <token> = hal Canada L8E 3C3

3 7

[OT] 3Ware 9.2.1.1 firmware for 9000 series released ...
by Bryan J. Smith 09 Sep '05

09 Sep '05

Claims to have fixed the write performance issues with multiple volumes. Haven't tried it personally (I do not have a 9500S card, and I have only installed one once for a client). NOTE: This (9.2.1.1) is an actual, formal, supported release -- not an unsupported engineering release. -- Bryan J. Smith | Sent from Yahoo Mail mailto:b.j.smith@ieee.org | (please excuse any http://thebs413.blogspot.com/ | missing headers)

4 14

Error when starting apache
by William J.A. Brillinger 09 Sep '05

09 Sep '05

Hi, On my NU-BQ+CentOS (cobalt replacement) server today, I noticed I get an error when re-starting apache. The box has 2 sites on it, both of them are vsites on the same IP as is assigned to the server. The error is (ip masked on purpose): /etc/init.d/httpd restart Stopping httpd: [ OK ] Starting httpd: [Thu Sep 08 17:03:48 2005] [warn] NameVirtualHost **.**.***.**:80 has no VirtualHosts [ OK ] Is this normal for this server? - Bill --------------------------------- William J.A. Brillinger Precision Design Co. E-Mail: mailto:billy@pdcweb.net Web site: http://www.pdcweb.net

4 5

What's going on with my Linux Swap?
by Dave Gutteridge 09 Sep '05

09 Sep '05

I've tried to create a Linux swap file, but when I run fdisk, it looks like this: Device Boot Start End Blocks Id System /dev/hdb1 * 1 3644 29270398+ 83 Linux /dev/hdb2 3645 3737 747022+ f W95 Ext'd (LBA) /dev/hdb5 3645 3737 746991 82 Linux swap Why is this W95 partition existing in the same place as my Linux swap? I would have thought they'd be incompatible. Can my Linux OS use this Linux swap? Does this need cleaning up, and if so how? Dave

4 7

Red Hat Hardware Catalog
by Petr Klíma 09 Sep '05

09 Sep '05

Hello Did anybody get any result for search in "Red Hat Hardware Catalog" http://bugzilla.redhat.com/hwcert/list.cgi?product=Red%20Hat%20Hardware%20C… On question for "3Com" I get only answer "15 certifications found" but no list of HW. Petr Klíma e-mail: petr.klima(a)madeta-group.cz MADETA Group a.s. phone: +420 389 136 209 Rudolfovská 246/83 web: http://www.madeta-group.cz 370 50 České Budějovice Czech Republic -- Petr Klíma e-mail: qaxi(a)seznam.cz

4 3

Installing on Abit BE7-RAID
by Todd Cary 09 Sep '05

09 Sep '05

I have RH 8 running on a Abit BE7-RAID motherboard. My task is installing Centos 4.1 with limited knowledge on installing with hardware RAID. The arrays are still in place for the two pairs of drives. HighPoint only shows drivers up through RH 9. Is there anyone who can take me through the steps? Remove the existing arrays? Will the drivers work with Centos 4.1? Since I used Windows to download the HighPoint tar file for RH 9, I am not what I should do with it. Todd -- Ariste Software 200 D Street Ext Petaluma, CA 94952 (707) 773-4523

3 5

[OT] Concept: RepoDELTA (simple createrepo hack)
by Bryan J. Smith 09 Sep '05

09 Sep '05

I'm not on the YUM lists, so I'll post this here in the hope it will make someone happy. I'll forward the concept to Seth for consideration (if he doesn't see it here). This is a simple "createrepo" hack that would require corresponding support in the "yum" binary as well. I'm not sure this would work, but it's just an idea I figure I might as well through out. PROBLEM Users want to be able to access the "state" of a YUM repository at any arbitrary point in time or by a known tag. REQUIREMENTS In order for this to work, there are 3 requirements: 1. Appending-only Repository No package deletions, packages are only added to the YUM repository, never removed (at least not without careful considerations -- i.e., not recommended). 2. Multiple Repodata Instances/Tracking For those who actually know how YUM works at the HTTP-accessed repository, it is the "repodata" directory that holds all meta-data/package list information. In order for any resolution to occur on any arbitrary date/tag, there must be a way to control/delta/host multiple Repodata Instances and track. 3. Resolution There must be a new set of mechanisms for resolving what Repodata Instance to use, given an option in the YUM client. Either a radical change must occur in the way YUM operates (i.e., repositories are accessed via HTTP), or the client must take on this additional burden. SOLUTION 1. Doesn't change regardless of solution -- unless, of course, the server wants the additional overhead of binary deltas between RPMs. No thanks, we'll just keep all RPM package releases. 2/3. An evolutionary approach is used, no fancy version control system, just a flat directory system all still accessed via HTTP. This is how it works. New Subdirectory: ./repodelta A. Tree organization Repodelta is a tree of subdirectories whose names are the string of absolute POSIX seconds assuming UTC -- i.e., the same output as "date -u +%s", e.g., ./repodelta/1126278362 B. Tree index Since HTTP does not lend itself to file management (at least not without something like WebDAV on both the server and client), there will be an index file of the tree. This should be a simple file, something like "./repodelta/releases.txt" or similar. It should be a flat text file, just the `date -u +%s" format on each line, although an MD5 or other checksum could be attached to the end or a separate file for verification of its integrity. C. New createrepo option: --delta The createrepo should have a new option called "--delta". Instead of generating new meta-data files in the "./repodata" subdirectory, it creates a new "./repodelta/`date -u +%s`" subdirectory with new meta-data files, then symlinks ./repodata/ to it. It also re-reads the "./repodelta/" directory, looks for subdirectories ( [ -d ] "test" in most scripting languages) with valid meta-data indicies (this would be more subjective/involved), and regenerates the "./repodelta/releases.txt" file with an date index to those releases. Again, we do this since standard HTTP does not define file operations such as reading a directory list. D. Tags: Symlinks Creating tags is as simple as symlinking a new directory against one of the `date -u +%s` format directories. The createrepo "--delta" option will look for symlinks in the under "./repodelta", and add the tag in the "./repodelta/releases.txt" after the de-referenced directory name (whitespace delimited). E.g., given the directory listing: ./repodelta/1126278362 ./repodelta/4.1 -> 1126278362 ./repodelta/current -> 1126278362 The line in ./repodelta/releases.txt would be: 1126278362 4.1 current It probably wouldn't hurt for a reserved "HEAD" tag to be automagically generated whenever createrepo --delta is run for the new directory. E. YUM client options New YUM clients would have to be written with new options and resolution logic -- date and tag options. Resolution is straight-forward for tags, although a decision whether to default to HEAD or give an error if a tag doesn't exist would have to be considered. Date resolution is almost as straight-forward -- given a date/time (in a variety of formats -- absolute seconds, traditional format, reverse offset from current, etc...), the YUM client will look for the closest date that is "no later" than the one given. Kinda like the Price-is-Right, the closest without going over (the given date/time). F. Backward compatibility, both client and server Because the ./repodata/ is just a symlink, legacy YUM clients work without modification. And in the case where someone runs a non-repodelta verison of createrepo, only the last repo is overwritten. NOTE: An option to avoid this might be to have ./repodata not be a symlink to a subdirectory in ./repodelta/, but a copy of of the appropriate subdirectory. Another option would be to leave the symlink, but it always points to a reserved ./repodelta/HEAD/ directory that is not a symlink. That way you always know the ./repodelta/`date -u +%s` is always true to that date, and the only consideration is if ./repodelta/HEAD/ is not the same as the latest ./repodelta/`date -u +%s`. In fact, that might be most ideal, HEAD is _never_ a tag/symlink, but its own, real subdirectory. EXAMPLE: An example directory structure might be: ./repodata ./repodelta/1125372135 ./repodelta/1126278362 ./repodelta/4.0 -> 1125372135 ./repodelta/os -> 1125372135 ./repodelta/4.1 -> 1126278362 ./repodelta/HEAD Where ./repodelta/releases.txt contains: HEAD 1126278362 4.1 1125372135 4.0 os HEAD may or may not be the same as 1126278362. Again, refereincing "F" above, this is to prevent 1126278362 from being changed in case someone runs "createrepo" without the "--delta" option. But if someone did when 1126278362 was created, it will copy its contents into HEAD. And if no one has run createrepo since, the contents will match. Again, this "hack" is probably very easy to implement on the server side. In fact, it could be run daily or on another, regular period. If new files have been added (Q: by date? or my comparing to the previous meta-data?), it will revision a new ./repodelta/`date -u +%s` subdirectory and the other operations. If not, there is no sense in creating a second, exact copy from the previous run. -- Bryan J. Smith | Sent from Yahoo Mail mailto:b.j.smith@ieee.org | (please excuse any http://thebs413.blogspot.com/ | missing headers)

1 0

CentOS-announce Digest, Vol 7, Issue 6
by centos-announce-request＠centos.org 09 Sep '05

09 Sep '05

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-2005:761 Moderate CentOS 4 ia64 pcre - security update (Pasi Pirhonen) 2. CESA-2005:761 Moderate CentOS 3 ia64 pcre - security update (Pasi Pirhonen) 3. CESA-2005:761 Moderate CentOS 3 s390(x) pcre - security update (Pasi Pirhonen) 4. CESA-2005:761 Moderate CentOS 4 s390(x) pcre - security update (Pasi Pirhonen) 5. CESA-2005:761 Moderate CentOS 4 x86_64 pcre - security update (Johnny Hughes) 6. CESA-2005:761 Moderate CentOS 4 i386 pcre - security update (Johnny Hughes) 7. CESA-2005:358 Moderate CentOS 4 ia64 exim - security update (Pasi Pirhonen) 8. CESA-2005:358 Moderate CentOS 4 s390(x) exim - security update (Pasi Pirhonen) 9. CESA-2005:358 Moderate CentOS 4 i386 exim - security update (Johnny Hughes) 10. CESA-2005:358 Moderate CentOS 4 x86_64 exim - security update (Johnny Hughes) 11. CESA-2005:761 Moderate CentOS 3 i386 pcre - security update (Tru Huynh) 12. CESA-2005:761 Moderate CentOS 3 x86_64 pcre - security update (Tru Huynh) 13. CESA-2005:761-02: Moderate CentOS 2 i386 pcre security update (John Newbigin) ---------------------------------------------------------------------- Message: 1 Date: Thu, 8 Sep 2005 21:08:23 +0300 From: Pasi Pirhonen <upi(a)papat.org> Subject: [CentOS-announce] CESA-2005:761 Moderate CentOS 4 ia64 pcre - security update To: centos-announce(a)centos.org Message-ID: <20050908180823.GG15823(a)core.upi.iki.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2005:761 https://rhn.redhat.com/errata/RHSA-2005-761.html The following updated files have been uploaded and are currently syncing to the mirrors: files: updates/ia64/RPMS/pcre-4.5-3.2.RHEL4.ia64.rpm updates/ia64/RPMS/pcre-devel-4.5-3.2.RHEL4.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://iki.fi/upi/

1 0

RE: [CentOS] Installing on Abit BE7-RAID
by Drew Weaver 09 Sep '05

09 Sep '05

Good luck getting a hw raid vendor (other than 3ware) to help you :-) -----Original Message----- From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of Ignacio Vazquez-Abrams Sent: Thursday, September 08, 2005 10:46 PM To: CentOS mailing list Subject: Re: [CentOS] Installing on Abit BE7-RAID On Thu, 2005-09-08 at 19:26 -0700, Todd Cary wrote: > I have RH 8 running on a Abit BE7-RAID motherboard. My task is > installing Centos 4.1 with limited knowledge on installing with hardware > RAID. The arrays are still in place for the two pairs of drives. > > HighPoint only shows drivers up through RH 9. > Will the drivers work with Centos 4.1? Absolutely not. The kernel versions are far too different. Contact HighPoint for updated drivers. -- Ignacio Vazquez-Abrams <ivazquez(a)ivazquez.net> http://centos.ivazquez.net/ gpg --keyserver hkp://subkeys.pgp.net --recv-key 38028b72

3 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss