Discuss

discuss@lists.centos.org

34758 discussions

rpmbuild date shift
by David Hrbáč 19 May '09

19 May '09

Hi, I'd like to ask if anyone's experiencing date shift with rpmbuild/mock on C5. I see +1 day date shift within changelog. Checked with mock-0.9.14-3.el5.hrb and mock-0.6.13-1.el5_2.3. Regards, David Hrbáč Source rpm: [mockbuild@builder2 ~]$ rpm -qp --changelog repoview-0.6.4-1.el4.hrb.src.rpm | less * Wed May 13 2009 David Hrbáč <david(a)hrbac.cz> - 0.6.3-1 - new upstream version - added requirements * Wed May 13 2009 David Hrbáč <david(a)hrbac.cz> - 0.6.3-1 - new upstream version Source rpm after rebuild: [mockbuild@builder2 ~]$ rpm -qp --changelog /var/lib/mock/epel-5-i386/result/repoview-0.6.4-1.el5.src.rpm | less * Thu May 14 2009 David Hrbáč <david(a)hrbac.cz> - 0.6.3-1 - new upstream version - added requirements * Thu May 14 2009 David Hrbáč <david(a)hrbac.cz> - 0.6.3-1 - new upstream version

3 5

Re: [CentOS] Solved: Dual-booting CentOS and WinXP
by William L. Maltby 19 May '09

19 May '09

On Tue, 2009-05-19 at 08:52 +0200, Sorin Srbu wrote: > >-----Original Message----- > >From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On > Behalf > >Of William L. Maltby > <snip> > >I think for maximum performance, if you have a secondary channel, put > >the linux disk on that channel, rather than primary channel. > > The flat cables won't reach. 8-} <*chuckle*> I can't tell you how many times I've found myself in that situation... *after* I installed the drive and *then* tried to attach the cables. This was back when a whole bunch of screws were involved. When the cables were only 40 conductor I bought a whole roll and a bunch of connectors and made my own as needed. Now that stuff is 80 wires, I don't do that. Since I use full towers, this was a problem. I searched on-line and found some quality extended ones, but they were fairly expensive. For your use, they may not be worth it. Or budgets may intrude, etc. Anyway, glad your setup is working now. > <snip sig stuff> -- Bill

2 1

Re: [CentOS] Solved: Dual-booting CentOS and WinXP
by William L. Maltby 19 May '09

19 May '09

On Mon, 2009-05-18 at 15:00 +0200, Sorin Srbu wrote: > <snip> > * Install a new hd and jumper it as primary master. Linux hd should > consequently be set as primary slave. Install WinXP. I've ghosted the I think for maximum performance, if you have a secondary channel, put the linux disk on that channel, rather than primary channel. > <snip> -- Bill

2 1

Re: [CentOS] Solved: Dual-booting CentOS and WinXP
by Les Mikesell 19 May '09

19 May '09

Sorin Srbu wrote: >> -----Original Message----- >> From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On > Behalf >> Of Sorin Srbu >> Sent: Friday, May 15, 2009 8:48 AM >> To: 'CentOS mailing list' >> Subject: Re: [CentOS] Dual-booting CentOS and WinXP >> >> Thanks for the confirmation all. I'll try switching the master/slave >> settings. >> >> Luckily I'm still at the testing phase, to see how things'll go smoothest, >> before I go live so to speak. > > First test machine finished after some serious tinkering, will probably need > to do another test install according to the documentation I made during the > testing. The machine now boots both CentOS and WinXP and all seems fine. > > Below are the steps I took: > > * Disconnect linux hd. > > * Install a new hd and jumper it as primary master. Linux hd should > consequently be set as primary slave. Install WinXP. I've ghosted the > Workgroup install with g4u, so next deployment should be fairly quick. Also > wrote zeroes to all empty areas on the Windows hd to save space at ghosting. > > * Connect linux hd. > > * Boot from cd1 with appropriate CentOS release and run "linux rescue". > > * At prompt, run "grub-install --recheck /dev/hda". > > * At prompt run "grub". > > * Enter root (hd1,0). This'll install grub to second hd on MBR, the one with > CentOS on it, if my information is correct. > > * Enter "setup (hd1). > > * Enter "quit" and reboot. > > * Boot CentOS and check /etc/grub.conf. > > * Boot Windows and check whatever needs to be checked. > > * Done. > > > The nice thing here is that I can use the same IP for both installs. Being > continually low on available IP's for this department, this is super! > > Thanks all for hints and help! Note that it is also possible to set up VMware and perhaps virtualbox to be able to boot the alternate OS as a virtual machine so you can run both at once if you like. If you don't have the enterprise-licensed version of windows you might need to run it as the host, though. Otherwise it will want to be re-licensed every time you switch between virtual and physical boots and it sees different hardware. With Vmware you have to install the (free) server version to do the setup, although you can later remove it and use the player version at runtime if you prefer. -- Les Mikesell lesmikesell(a)gmail.com

2 1

unable to read partition table in log
by P.A 18 May '09

18 May '09

Hi recently I noticed in the messages log, the following error May 18 15:59:52 mail kernel: sdb: assuming drive cache: write through May 18 15:59:52 mail kernel: sdb : READ CAPACITY failed. May 18 15:59:52 mail kernel: sdb : status=0, message=00, host=1, driver=00 May 18 15:59:52 mail kernel: sdb : sense not available. May 18 15:59:52 mail kernel: sdb: assuming Write Enabled May 18 15:59:52 mail kernel: sdb: assuming drive cache: write through May 18 15:59:52 mail kernel: sdb:<3>Buffer I/O error on device sdb, logical block 0 May 18 15:59:52 mail kernel: Buffer I/O error on device sdb, logical block 0 May 18 15:59:52 mail last message repeated 5 times May 18 15:59:52 mail kernel: unable to read partition table I'm not sure what sdb is since its not listed on my partition table [root@mail srvadmin]# fdisk -l Disk /dev/sda: 109.1 GB, 109196476416 bytes 255 heads, 63 sectors/track, 13275 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 13 104391 83 Linux /dev/sda2 14 13275 106527015 8e Linux LVM [root@mail srvadmin]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol00 99G 42G 52G 45% / /dev/sda1 99M 44M 51M 47% /boot none 3.9G 0 3.9G 0% /dev/shm [root@mail srvadmin]# I looked at the hardware itself and all disk in this raid system are fine, my question is, is this something I need to worry about and what is causing this issue. Although everything looking fine, my messages log is full of sdb complaints.

5 4

Re: [CentOS] Solved: Dual-booting CentOS and WinXP
by Sorin Srbu 18 May '09

18 May '09

>-----Original Message----- >From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf >Of Sorin Srbu >Sent: Friday, May 15, 2009 8:48 AM >To: 'CentOS mailing list' >Subject: Re: [CentOS] Dual-booting CentOS and WinXP > >Thanks for the confirmation all. I'll try switching the master/slave >settings. > >Luckily I'm still at the testing phase, to see how things'll go smoothest, >before I go live so to speak. First test machine finished after some serious tinkering, will probably need to do another test install according to the documentation I made during the testing. The machine now boots both CentOS and WinXP and all seems fine. Below are the steps I took: * Disconnect linux hd. * Install a new hd and jumper it as primary master. Linux hd should consequently be set as primary slave. Install WinXP. I've ghosted the Workgroup install with g4u, so next deployment should be fairly quick. Also wrote zeroes to all empty areas on the Windows hd to save space at ghosting. * Connect linux hd. * Boot from cd1 with appropriate CentOS release and run "linux rescue". * At prompt, run "grub-install --recheck /dev/hda". * At prompt run "grub". * Enter root (hd1,0). This'll install grub to second hd on MBR, the one with CentOS on it, if my information is correct. * Enter "setup (hd1). * Enter "quit" and reboot. * Boot CentOS and check /etc/grub.conf. * Boot Windows and check whatever needs to be checked. * Done. The nice thing here is that I can use the same IP for both installs. Being continually low on available IP's for this department, this is super! Thanks all for hints and help! -- /Sorin

1 0

URL of website doesn't point anymore to CentOS/Drupal installation
by M. Fioretti 18 May '09

18 May '09

sorry for the vague subject, but I couldn't find a better one. I have the website http://digifreedom.net running on a Centos 4 VPS with Apache and Drupal 6.10 . This is a multisite Drupal setup: only one installation, with subdirectories in sites/, and a separate mysql database for each website. For several reasons, I had setup DNS, drupal and everything to work without the www prefix on domain names. In other words, http://digifreedom.net is OK, www.digifreedom.net was never used. Everything worked perfectly for months, if not years. Five minutes ago, somebody wrote to me that a digifreedom.net URL I suggested him to read "doesn't work". I checked, and what happens now is that, if I type http://digifreedom.net/node/82 the browser is immediately redirected to www.digifreedom.net/node/82, which (of course) returns an error message: "Firefox can't find the server at www.digifreedom.net" That error message is OK, because I had NOT set up DNS and apache to answer to that address. What I don't get is why http://digifreedom.net now becomes www.digifreedom.net. I haven't changed anything myself in DNS, drupal or apache config for many weeks, so why all of a sudden something started to behave differently? The weirdest thing is that this "forced redirection" from example.com to www.example.com happens with some, but not all of the other domains configured in the same way and running on the same server off the same Apache/Drupal installation! How can I find, at least, which piece of the puzzle is responsible for this problem? I am aware that probably this isn't even a centos issue, I just need a pointer in the right direction. TIA, Marco -- Your own civil rights and the quality of your life heavily depend on how software is used *around* you: http://digifreedom.net/node/84

4 6

CentOS 5.3: duplicate glib2-2.12.3-2.fc6 packages
by William R. Lorenz 18 May '09

18 May '09

Hi All, I have a freshly installed CentOS 5.3, x86_64 system -- just the Base package selection (via custom packages selection), and nothing else. Immediately after install (no updates), here's what's in the RPM db: [root@dev ~]# rpm -qa | grep -i glib2 glib2-2.12.3-2.fc6 glib2-2.12.3-2.fc6 [root@dev ~]# I have two questions about this: (1) Should this package be listed in the RPM database twice? (2) Should it be listed there with the fc6 extension? Any insights would be appreciated. Thanks, -- William R. Lorenz

3 3

When will we be moving to lighttpd 1.5?
by James Matthews 18 May '09

18 May '09

I know I can compile it however I prefer to use the package manager and having an updated version. -- http://www.goldwatches.com

4 3

Kickstart hang trying to install CentOS 5.3
by Alfred von Campe 17 May '09

17 May '09

I've been using kickstart successfully with a local mirror going back to CentOS 4.X. I'm trying to install CentOS 5.3 via kickstart on a new system (which happens to be different than most other systems I've installed on), and the install process always hangs shortly after the partitions are created. If I go to the alternate console #3, the last two lines are always this (except that the time stamp changes every time I try it of course): 10:06:18 DEBUG: Member xorg-x11-drv-i128-1.2.0-4 - u 10:06:18 DEBUG: Adding Package xorg-x11-drv-i128-1.2.0-4.i386 in mode u This is preceded by hundreds of similar lines for other packages, but it always hangs at xorg-x11-drv-i128-1.2.0-4. I am currently out of other systems to test/install this on. Instead of the usual ThinkCentre mini tower, this system is a ThinkCentre pizza box. I've installed CentOS on this type of hardware before without problems, but it hangs on the only two systems I currently have. It's possible that there is something wrong with my local mirror, but I rsync it every night and this problem has been going on for a few days. I will try to install this on a mini tower to rule out any hardware compatibility issues, but in the mean time, I'm looking for suggestions on how to debug this. I've booted into Linux rescue mode after power cycling the system after it hung to look at whatever did get installed, but there are no useful log files. Alfred

3 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