Discuss

discuss@lists.centos.org

34753 discussions

/var goes read-only
by Joshua Gimer 05 Dec '06

05 Dec '06

This is an issue that I have been having with one of our production servers for a couple of months, just out of no where /var goes to read only. There aren't any errors that show up in /var/log/messages nor dmesg, I checked to make sure that the drives on error option is set to continue and there isn't anything as far as I can tell wrong with the disks. Also there is plenty of disk space. Here is the output of tune2fs -l /dev/sda3: Filesystem volume name: /var1 Last mounted on: <not available> Filesystem UUID: 6bb81ddf-b0f8-4c47-ae9f-b39f504c114e Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 1281696 Block count: 2560359 Reserved block count: 128017 Free blocks: 1946888 Free inodes: 1279680 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 625 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 16224 Inode blocks per group: 507 Filesystem created: Wed Jun 29 10:43:21 2005 Last mount time: Fri Dec 1 10:30:30 2006 Last write time: Fri Dec 1 10:30:30 2006 Mount count: 21 Maximum mount count: -1 Last checked: Wed Jun 29 10:43:21 2005 Check interval: 0 (<none>) Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 128 Journal inode: 8 Default directory hash: tea Directory Hash Seed: 6f24f054-98af-4bd8-9af2-d40254126ac7 Journal backup: inode blocks Here is what is in /etc/fstab: # This file is edited by fstab-sync - see 'man fstab-sync' for details LABEL=/1 / ext3 defaults 1 1 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 LABEL=/qt1 /opt ext3 defaults 1 2 none /sys sysfs defaults 0 0 LABEL=/var1 /var ext3 defaults 1 2 LABEL=SWAP-sda5 swap swap defaults 0 0 /dev/hda /media/cdrom auto pamconsole,exec,noauto,managed 0 0 /dev/fd0 /media/floppy auto pamconsole,exec,noauto,managed 0 0 Here is the output of df -h: Filesystem Size Used Avail Use% Mounted on /dev/sda2 22G 2.0G 19G 10% / none 4.0G 0 4.0G 0% /dev/shm /dev/sdb1 269G 48G 208G 19% /opt /dev/sda3 9.7G 2.3G 7.0G 25% /var Kernel version: 2.6.9-42.0.3.ELsmp Any help would be greatly appreciated!! -- Thx Joshua Gimer

7 10

The amazing smartctl -a /dev/hda
by Paul 05 Dec '06

05 Dec '06

I finally fixed my drive error problem. This has been going on quite a while. I've posted before with no success on getting this fixed. I was getting these errors. Dec 4 04:03:10 bikesn4x4s kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Dec 4 04:03:10 bikesn4x4s kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } And now for the amazing smartctl -a command. The output actually had a link that advised and directed me to a link to upgrade my firmware, which looks to have fixed it. Simply amazing. smartctl -a /dev/hda: smartctl version 5.33 [i686-redhat-linux-gnu] Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: IBM-DTLA-307020 Serial Number: YH0YHL24292 Firmware Version: TX3OA50C User Capacity: 20,576,747,520 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 5 ATA Standard is: ATA/ATAPI-5 T13 1321D revision 1 Local Time is: Mon Dec 4 06:45:29 2006 EST ==> WARNING: IBM Deskstar 40GV and 75GXP drives may need upgraded SMART firmware. Please see http://www.geocities.com/dtla_update/ and http://www-3.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-42215 or http://www-1.ibm.com/support/docview.wss?uid=psg1MIGR-42215 SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (1496) seconds. Offline data collection capabilities: (0x1b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. No Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. No General Purpose Logging support. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 14) minutes. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 060 Pre-fail Always - 0 2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0 3 Spin_Up_Time 0x0007 115 115 024 Pre-fail Always - 188 (Average 194) 4 Start_Stop_Count 0x0012 099 099 000 Old_age Always - 4026 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 9 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 100 100 020 Pre-fail Offline - 0 9 Power_On_Hours 0x0012 097 097 000 Old_age Always - 21888 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 2693 192 Power-Off_Retract_Count 0x0032 097 097 050 Old_age Always - 4026 193 Load_Cycle_Count 0x0012 097 097 050 Old_age Always - 4026 194 Temperature_Celsius 0x0002 183 183 000 Old_age Always - 30 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 10 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 367 SMART Error Log Version: 1 ATA Error Count: 431 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 431 occurred at disk power-on lifetime: 21885 hours (911 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 ac 28 f9 e1 Error: ICRC, ABRT at LBA = 0x01f928ac = 33106092 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 a5 28 f9 e1 00 9d+18:33:42.900 READ DMA c8 00 68 3d 28 f9 e1 00 9d+18:33:42.900 READ DMA c8 00 10 3d 1a f9 e1 00 9d+18:33:42.900 READ DMA c8 00 68 d5 19 f9 e1 00 9d+18:33:42.900 READ DMA c8 00 08 0d 12 f9 e1 00 9d+18:33:42.900 READ DMA Error 430 occurred at disk power-on lifetime: 21885 hours (911 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 dc 29 f9 e1 Error: ICRC, ABRT at LBA = 0x01f929dc = 33106396 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 d5 29 f9 e1 00 9d+18:33:41.900 READ DMA c8 00 68 6d 29 f9 e1 00 9d+18:33:41.900 READ DMA c8 00 60 ad 0d f9 e1 00 9d+18:33:41.900 READ DMA c8 00 08 fd 5a fb e1 00 9d+18:33:41.900 READ DMA c8 00 68 95 5a fb e1 00 9d+18:33:41.900 READ DMA Error 429 occurred at disk power-on lifetime: 21885 hours (911 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 1c 27 9c e1 Error: ICRC, ABRT at LBA = 0x019c271c = 27010844 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 18 05 27 9c e1 00 9d+18:33:40.900 READ DMA c8 00 08 9d a2 9e e1 00 9d+18:33:40.900 READ DMA c8 00 20 b5 a2 9e e1 00 9d+18:33:40.900 READ DMA c8 00 18 35 42 9c e1 00 9d+18:33:40.900 READ DMA c8 00 18 b5 1e a2 e1 00 9d+18:33:40.900 READ DMA Error 428 occurred at disk power-on lifetime: 21885 hours (911 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 dc b2 a5 e1 Error: ICRC, ABRT at LBA = 0x01a5b2dc = 27636444 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 30 ad b2 a5 e1 00 9d+18:33:40.400 READ DMA c8 00 28 f5 d4 a2 e1 00 9d+18:33:40.400 READ DMA c8 00 18 1d d5 a2 e1 00 9d+18:33:40.400 READ DMA c8 00 10 3d dc a2 e1 00 9d+18:33:40.400 READ DMA c8 00 28 25 db a2 e1 00 9d+18:33:40.400 READ DMA Error 427 occurred at disk power-on lifetime: 21885 hours (911 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 0c 41 b0 e1 Error: ICRC, ABRT at LBA = 0x01b0410c = 28328204 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 20 ed 40 b0 e1 00 9d+18:33:37.900 READ DMA c8 00 50 d5 29 b0 e1 00 9d+18:33:37.900 READ DMA c8 00 30 75 42 b0 e1 00 9d+18:33:37.900 READ DMA c8 00 28 25 4a b0 e1 00 9d+18:33:37.900 READ DMA c8 00 18 45 d5 ab e1 00 9d+18:33:37.800 READ DMA SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 17736 - # 2 Short offline Completed without error 00% 15777 - # 3 Short offline Completed without error 00% 15776 - Device does not support Selective Self Tests/Logging And now after upgrading the firmware: smartctl version 5.33 [i686-redhat-linux-gnu] Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: IBM-DTLA-307020 Serial Number: YH0YHL24292 Firmware Version: TX3OA5AA User Capacity: 20,576,747,520 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 5 ATA Standard is: ATA/ATAPI-5 T13 1321D revision 1 Local Time is: Mon Dec 4 18:56:58 2006 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (1496) seconds. Offline data collection capabilities: (0x1b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. No Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. No General Purpose Logging support. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 14) minutes. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 060 Pre-fail Always - 0 2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0 3 Spin_Up_Time 0x0007 100 100 024 Pre-fail Always - 0 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 1 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 9 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 100 100 020 Pre-fail Offline - 0 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 0 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1 192 Power-Off_Retract_Count 0x0032 100 100 050 Old_age Always - 1 193 Load_Cycle_Count 0x0012 100 100 050 Old_age Always - 1 194 Temperature_Celsius 0x0002 177 177 000 Old_age Always - 31 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 10 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] Device does not support Selective Self Tests/Logging

1 0

I've been hacked -- what should I do next?
by Alfred von Campe 04 Dec '06

04 Dec '06

My home system has been hacked. It's running CentOS 4.4, and I recently added an account to play around with Samba shares to back up PCs here at home. I had set a weak password for that account and forgot to disable it after my testing. I could hear the disk being accessed constantly, so I knew something was up. I disabled the port forwarding to my CentOS box on my Linksys router (only ports 22 and 80 were being forwarded). After some poking around, I found the following files in the directory "/var/tmp/ /.. ": -rw-rw-r-- 1 backup backup 9468 Dec 1 00:20 azi2.seen -rw-rw-r-- 1 backup backup 9513 Dec 1 00:20 azi3.seen -rw-rw-r-- 1 backup backup 9513 Dec 1 00:20 azi4.seen -rwxr-xr-x 1 backup backup 504464 Feb 10 2005 -bash -rwx--x--x 1 backup backup 22936 Feb 10 2005 kswap.help -rw-r--r-- 1 backup backup 1085 Dec 1 00:00 kswap.levels -rw------- 1 backup backup 5 Nov 29 17:28 kswap.pid -rw-r--r-- 1 backup backup 1480 Dec 1 00:00 kswap.session -rw-r--r-- 1 backup backup 4731 Dec 25 2005 kswap.set -rw-r--r-- 1 backup backup 165073 Dec 1 00:26 LinkEvents -rw-r--r-- 1 backup backup 258 Dec 1 00:00 mech2.users -rw-r--r-- 1 backup backup 258 Dec 1 00:00 mech3.users -rw-r--r-- 1 backup backup 258 Dec 1 00:00 mech4.users -rw-r--r-- 1 backup backup 258 Jun 28 1999 mech.users -rwxr-xr-x 1 backup backup 174396 May 17 2004 pico Anyone recognize this root kit (if that is what it is)? I've disabled the backup account, and re-enabled port forwarding on my router (so I can access the system from home). Other than deleting these files, is there anything else I should worry about? I'd rather not re-install the OS... Alfred

22 33

In need of assistance... (part 2)
by Administrator 04 Dec '06

04 Dec '06

Hello, i wrote in a week ago and was overwhelmed by the response, but maybe i need to be more specific. We need to get a rock solid backup system in place, basically a self-running system that would be set up once and then periodically checked on. We have 2 Windows machines (NT4, 2003 Server) and 3 Linux Machines (Centos 4.4, Centos 4.3 and Red Hat 3). Two machines are hosted locally (Centos 4.4 & NT4). We have a Dell Server that just needs new hard drives and that could be setup to be a backup server, but we want to be sure that we have off-site backups of the local machines (so we could ship the machine to a hosting facility once it is set up). We would like to have the ability to have a rolling archive of about 30 days. Since we are a publishing company, our archives are important but not critical to our daily operations and they don't change. The current projects are changed daily and need to be archived daily. We are open to the options that were suggested a week ago, but we are thinking that we need someone to implement it. This is very important and not something that should be left to someone who is 'learning as he goes'. We need a clear and solid plan along with someone who could execute it. Please let me know of any people who are in/around San Diego, California and could help us- or someone who could accomplish the task flawlessly with a remote connection. Many thanks, Noah -- Noah Spahn Tech Manager/Systems Administrator Wells Publishing Inc (619)584-1100 ext.122

3 2

another iscsi question
by James Fidell 04 Dec '06

04 Dec '06

I have an iscsi array that I'd like to mount and share using NFS and I need it to happen without user intervention on a reboot. In the default configuration this doesn't seem to work very well because the iscsi intiator isn't started until after the network is up (obviously) and by that time all local filesystems are mounted. I can't mount the partitions in rc.local because NFS has already started. Does a tidy way to handle this already exist, or do I need to do something like hack /etc/init.d/iscsi to mount and unmount iscsi partitions as necessary? James

4 5

kde cant mount cdroms on users with nfs home
by Jean Figarella 04 Dec '06

04 Dec '06

I can't mount the cdrom when the user account has an nfs home directory. It works fine on the gnome side with the same user. It also works fine if I create a brand new local account, with no nfs mounted home directory. This error is affecting all users on all computers; not just one account. The one thing in common is that they all are using nfs mounted home directories and that CentOS is the distro. Older systems that are still using fc3 dont have this issue. Any ideas? Suggestions?

4 4

YUM conflict with RHEL 4_X86_64
by johnny 04 Dec '06

04 Dec '06

Hi, everyone, I have one conflict problem when I try to install Centos YUM on RHEL 4_X 86_64. Uname -a shows: Linux PT3 2.6.9-42.0.0.0.1.ELsmp #1 SMP Sun Oct 15 15:13:57 PDT 2006 x86_64 x86_64 x86_64 GNU/Linux Yum -version shows: Repository update is listed more than once in the configuration Repository base is listed more than once in the configuration Repository contrib is listed more than once in the configuration Repository addons is listed more than once in the configuration Repository extras is listed more than once in the configuration 2.4.3 And upon running yum -y update, it only can updates some of the packages, for other packages it shows conflict with /usr/lib/python2.3/site-packages/elementtree/. The error messages are: Transaction Check Error: file /usr/lib/python2.3/site-packages/elementtree/ElementInclude.pyc from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/ElementInclude.pyo from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/ElementPath.pyc from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/ElementPath.pyo from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/ElementTree.pyc from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/ElementTree.pyo from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/HTMLTreeBuilder.pyc from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/HTMLTreeBuilder.pyo from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/SgmlopXMLTreeBuilder.pyc from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/SgmlopXMLTreeBuilder.pyo from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/SimpleXMLTreeBuilder.pyc from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/SimpleXMLTreeBuilder.pyo from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/SimpleXMLWriter.pyc from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/SimpleXMLWriter.pyo from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/TidyHTMLTreeBuilder.pyc from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/TidyHTMLTreeBuilder.pyo from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/TidyTools.pyc from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/TidyTools.pyo from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/XMLTreeBuilder.pyc from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/XMLTreeBuilder.pyo from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/__init__.pyc from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 file /usr/lib/python2.3/site-packages/elementtree/__init__.pyo from install of python-elementtree-1.2.6-4.2.1 conflicts with file from package python-elementtree-1.2.6-4.2.1 What I have done is just to install the Yum for the RHEL 4_X 86_64. with the following commends: mkdir /usr/local/src/yum cd /usr/local/src/yum wget http://centos.cs.ucr.edu/centos/4/apt/i386/RPMS.os/python-elementtree-1.2.6- 4.2.1.i386.rpm wget http://centos.cs.ucr.edu/centos/4/apt/i386/RPMS.os/python-urlgrabber-2.9.8-2 .noarch.rpm wget http://centos.cs.ucr.edu/centos/4/apt/i386/RPMS.os/python-sqlite-1.1.7-1.2.i 386.rpm wget http://centos.cs.ucr.edu/centos/4/apt/i386/RPMS.os/yum-2.4.3-1.c4.noarch.rpm wget http://centos.cs.ucr.edu/centos/4/apt/i386/RPMS.os/sqlite-3.3.3-1.2.i386.rpm wget http://centos.mirror.vpslink.com/centos-4/4.4/os/i386/CentOS/RPMS/libxml2-py thon-2.6.16-6.i386.rpm wget http://centos.mirror.vpslink.com/centos-4/4.4/os/i386/CentOS/RPMS/rpm-python -4.3.3-18_nonptl.i386.rpm wget <http://mirror.freepbx.org/centos-yumconf-4-4.5.noarch.rpm> http://mirror.freepbx.org/centos-yumconf-4-4.5.noarch.rpm rpm -ivh --nodeps --force *rpm Any one knows any thing wrong with it? I am new to linux and thanks in advance for any help. Best Regards Johnny Xing Haipeng ------------------------------------------------- Mobile: 65-97418592 Banshing Industrial Co, (Pte) Ltd. 13 Serangoon North Ave 5, 554787 -------------------------------------------------

3 2

Re: [CentOS] Installing CentOS over LAN
by Al Sparks 04 Dec '06

04 Dec '06

Thanks. It looks like I've got something to work with. Another question. I'm also looking at virtual servers. What's the most popular free software for that? === Al ----- Original Message ---- From: Les Mikesell <lesmikesell(a)gmail.com> To: CentOS mailing list <centos(a)centos.org> Sent: Saturday, December 2, 2006 8:08:22 PM Subject: Re: [CentOS] Installing CentOS over LAN On Sat, 2006-12-02 at 21:02, Al Sparks wrote: > I want to set up a server that will do network installs of CentOS, > perhaps through NFS. > > Ideally, I'd put a CentOS in the CD of the target computer, I boot > it off of that CD, and then the rest is done over my network and > with the server. > > Has anyone done that and published it? Where can I find docs? If you download the iso images to an NFS exported directory you can burn only the first CD and boot it with 'linux askmethod' at the boot prompt, then select NFS as the install method and fill in the server and path info. Once it starts the install it will take care of all the loopback mounts for you so you don't have to wait around and swap CDs. You can automate even more with a kickstart file, but answering those first few questions doesn't take that long. -- Les Mikesell lesmikesell(a)gmail.com _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

9 8

AMD 64 single core and vmware
by rado 04 Dec '06

04 Dec '06

...months ago, I started using vmware w/this same setup and, I think it was Aleksandar Milivojevic and directed me to a link to a white paper or whatever w/the tweaks to get me running right. I have issues of typematic and time sync. I believe that the tweaks actually took away the power saving features of the cpu and set the processor at one steady speed. I thought I saved that page somewhere but w/all the confusion and have really been away from this for the most part for months now, I cannot find that page and I have been googling forever on my own to try to find it w/no luck. If anyone could direct me back to it it would be appreciated thx John Rose

1 0

YUM conflict with RHEL 4_X86_64
by johnny 04 Dec '06

04 Dec '06

5 4

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