Discuss January 2006

discuss@lists.centos.org

240 participants
336 discussions

Centos Folding@Home team!
by Sharon Kimble 28 Jan '06

28 Jan '06

Centos now has its own Folding@Home team! If you would like to learn more about what we do, please follow this <a href="http://folding.stanford.edu/">link</a> to the Folding@Home homepage. New to distributed computing?, its not a problem. Here is the simplest description: Many computers working on separate pieces of the same puzzle are faster than a few computers working on many pieces of the puzzle. By "distributing" the work load to as many computers as possible, results are faster and accumulate faster. This provides more information to the people who can use it, thus letting them actually work with the results instead of working to get results. Hopefully the above summary doesn't leave you lost and confused. If you are still with us then great, but if you're feeling lost? You can search <a href="http://www.google.com/search?hl=en&ie=UTF-8&q=distributed+computing&btnG=Go…">google</a> for distributed computing for more in depth information. Now on to Centos folders and Folding@Home. We are a team of members with various computer setups and knowledge. Our primary operating system of choice is Centos and our favourite distributed computing program is Folding@Home. You can see our team stats by clicking <a href="http://vspx27.stanford.edu/cgi-bin/main.py?qtype=teampage&teamnum=48721">here</a>, this should be updated regularly. Would you like to join the team? Well, if so it is as simple as visiting the <a href="http://folding.stanford.edu/download.html"Folding@Home</a> website and downloading the version you prefer. Once you've got it please read this <a href="http://www.fedoraforum.org/forum/showthread.php?t=18393&page=1&pp=15">FAQ</a> written by Jtang613. Please note, our team number is 48721. There now, its just as easy as that and now you are a part of the team. Welcome to the Fold! :) Further information about various installers and monitors can be found <a href="http://forum.folding-community.org/viewtopic.php?t=11700">here</a>. My personal preference is to use <a href="http://www.vendomar.ee/~ivo/">finstall</a> to install and a superkaramba theme to help monitor the work unit. Sharon. -- 13:21:27 up 3 days, 2:12, 1 user, load average: 2.07, 2.06, 1.93 A taste of linux http://www.sharons.org.uk/taste/index.html efever http://www.efever.blogspot.com/ Centos 4.2, KDE 3.5.0-1.7, OpenOffice 2.0.1 Registered Linux user 334501

1 0

Has anyone had success getting on-board sound to work on a Tyan S2895?
by David J. Mellor 28 Jan '06

28 Jan '06

My setup is as follows: Motherboard: Tyan S2895 CPU: Two Opteron 275s Memory: 4 GB Disk: Three 250 GB SATA drives attached to a 3Ware 9500S-4LP RAID card Video: Nvidia GeForce 7800 The only hardware that I have added to the motherboard is the 3Ware card and the Nvidia card. The disks are configured as a RAID 5 array, and the machine boots from this array. I installed CentOS 4.2 x86 on this system without any problems during the installation. The on-board sound card was recognised and the correct driver (snd_intel8x0) installed to handle it. However, on rebooting into the SMP kernel after the install, the installation proved to be completely unstable. The kernel would panic sometimes during startup and sometimes during shutdown. The uniprocessor kernel seemed to be stable, but I noticed the following error messages appearing on the console during startup (the same error messages also appeared when booting into the SMP kernel): 3w-9xxx: scsi0: ERROR: (0x03:0x0104): SGL entry has illegal length:address=0x37077000, length=0xFF, cmd=X. Suspecting that there might be a driver incompatibility with my particular hardware configuration, I downloaded one of the Fedora 4 kernel sources from the 2.6.12 series, and compiled my own SMP kernel. This solved the stability issue, and I have been using this intensively for four months without experiencing any system crashes. Unfortunately, I have been unable to get the on-board sound to work. If I use XMMS to play an MP3 file (I have the XMMS MP3 plugin from the Dag Wieers repository installed), then on hitting the play button nothing happens. It is not that XMMS thinks that it is processing the file but no sound is being produced, rather the playback counter stays at "00:00". If I visit a web page containing a Flash animation with sound, Firefox locks up and has to be killed. I have compiled other Fedora kernels from source (2.6.14) and the same behaviour is observed. I also cannot get sound to work with the 2.6.9 uniprocessor kernel supplied with CentOS 4.2. I know that the hardware on the motherboard is not faulty, because the machine is set up to dual-boot into CentOS or Windows XP. On Windows, there is no problem with the sound, and interestingly once I have booted into Windows if I then reboot into Linux then the sound will work under Linux (although sound mixing is still a problem - one application outputting sound will cause a second application trying to output sound to stall until the first is finished). Has anyone on this list experienced the same problems, and if so found a way to overcome them? Failing that, does anyone have any suggestions for any tweaks I can make to my system to make the sound work without having to boot into Windows first? Thanks, David Mellor.

2 1

gfs performance
by Jure Pečar 28 Jan '06

28 Jan '06

Hi all, Since I've got no reply on redhat cluster list, I'm trying here ... I'm testing a rhcs4 cluster with gfs. I noticed some poor performance while tarring data from a gfs volume to a local disk from both nodes at the same time, so I deceided to have a closer look. Here are the bonnie++ results: http://jure.pecar.org/gfs/ I don't know what to think of these ... but I doubt it's normal for performance to go down by an order of magnitude when both nodes are doing some i/o to the shared file system ... I'd like to see some numbers from other gfs systems to see if this is normal and if it is not, how to figure out what's wrong and how to fix it. Thanks, -- Jure Pečar http://jure.pecar.org/

2 3

can't install cyrus-sasl-devel using yum
by spart cus 28 Jan '06

28 Jan '06

hi guys, im having some erro when installing cysrus-sasl-devel #yum install cyrus-sasl-devel error --------------------------------- What are the most popular cars? Find out at Yahoo! Autos

2 1

php-ldap can't log on with browser
by Kai Sandsengen 28 Jan '06

28 Jan '06

It has been some posting about this issue, but I cant find a solution I can't log on to my ldap server port 389 with my browser. service seems to be running. I am not running selinux, port 389 are open on both client and server. Message from browser: Access to this port is disabled for security reasons. Added command (hint from earlier posting) and got this list # netstat -aptn | grep :389 tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:33057 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:32833 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:33058 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:33053 127.0.0.1:389 ESTABLISHED 2576/httpd tcp 0 0 127.0.0.1:33055 127.0.0.1:389 ESTABLISHED 2574/httpd tcp 0 0 127.0.0.1:33054 127.0.0.1:389 ESTABLISHED 2575/httpd tcp 0 0 127.0.0.1:33057 127.0.0.1:389 ESTABLISHED 2572/httpd tcp 0 0 127.0.0.1:33058 127.0.0.1:389 ESTABLISHED 2569/httpd tcp 0 0 127.0.0.1:33069 127.0.0.1:389 ESTABLISHED 2573/httpd tcp 0 0 127.0.0.1:33068 127.0.0.1:389 ESTABLISHED 2570/httpd tcp 0 0 127.0.0.1:33067 127.0.0.1:389 ESTABLISHED 2571/httpd tcp 0 0 127.0.0.1:33084 127.0.0.1:389 ESTABLISHED 3235/-bash tcp 0 0 127.0.0.1:389 127.0.0.1:33093 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:33093 127.0.0.1:389 ESTABLISHED 3269/-bash tcp 0 0 127.0.0.1:389 127.0.0.1:32837 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:32815 127.0.0.1:389 ESTABLISHED 2443/cupsd tcp 0 0 127.0.0.1:32837 127.0.0.1:389 ESTABLISHED 2494/xinetd tcp 0 0 127.0.0.1:32833 127.0.0.1:389 ESTABLISHED 2479/sshd tcp 0 0 127.0.0.1:32851 127.0.0.1:389 ESTABLISHED 2563/xfs tcp 0 0 127.0.0.1:32861 127.0.0.1:389 ESTABLISHED 2625/dbus-daemon-1 tcp 0 0 127.0.0.1:32856 127.0.0.1:389 ESTABLISHED 2615/atd tcp 0 0 127.0.0.1:32905 127.0.0.1:389 ESTABLISHED 2664/sh tcp 0 0 127.0.0.1:389 127.0.0.1:32905 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:33067 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:43309 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43308 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43311 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43310 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43305 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43304 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43307 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43306 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43301 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43303 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43302 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43298 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43325 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43324 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43327 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43326 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43321 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43320 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43323 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43322 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43317 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43316 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43319 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43318 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43313 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43312 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43315 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43314 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:389 127.0.0.1:33069 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:43373 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43372 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43375 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43374 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43369 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43368 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43371 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43370 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43365 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43364 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43367 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43366 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43361 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43360 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43363 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43362 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43389 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43388 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43391 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43390 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43385 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43384 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43387 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43386 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43381 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43380 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43383 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43382 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43377 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43376 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43379 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43378 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43341 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43340 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43343 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43342 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43337 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43336 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43339 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43338 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43333 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43332 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43335 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43334 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43329 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43328 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43331 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43330 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43357 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43356 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43359 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43358 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43353 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43352 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43355 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43354 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43349 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43348 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43351 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43350 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43345 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43344 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43347 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43346 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43437 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43436 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43439 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43438 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43433 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43432 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43435 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43434 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43429 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43428 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43431 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43430 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43425 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43424 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43427 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43426 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43453 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43452 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43455 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43454 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43449 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43448 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43451 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43450 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43445 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43444 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43447 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43446 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43441 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43440 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43443 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43442 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43405 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43404 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43407 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43406 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43401 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43400 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43403 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43402 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43397 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43396 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43399 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43398 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43393 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43392 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43395 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43394 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43421 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43420 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43423 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43422 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43417 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43416 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43419 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43418 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43413 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43412 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43415 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43414 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43409 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43408 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43411 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43410 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43457 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43456 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43459 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43458 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:389 127.0.0.1:33068 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:32815 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:32851 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:32856 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:33053 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:32861 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:33084 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:33055 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:33054 ESTABLISHED 2407/slapd tcp 0 0 :::389 :::* LISTEN 2407/slapd

2 4

sata_nv, CentOS 4 update 2 and hang during post-install
by Zube 28 Jan '06

28 Jan '06

Good day. Thanks in advance for any help. I have a Tyan S2895 (Thunder K8WE) with 2 275 Opterons and the latest (1.02) bios. It appears to have an nVidia nForce SATA chipset which connects to a 250gb WD Caviar SATA drive. Using the CentOS 4 update 2 x86_64 DVD, the install is peachy until half-way through the "performing post install configuration" bit. Then it hangs forever. I have tried: disabling RAID in the bios mem=256M on the command line a text install -- the hang was at the 50% marker a memory check -- all clean according to memtest86+ 1.65 CentOS 4 update 1 on cd smaller root partition without any change in behavior. I then installed an old Adaptec 29160N and an old SCSI disk and turned off the SATA bits in the BIOS. CentOS installs just fine. Has anyone else seen this issue? If it's a problem only with the nVidia SATA drivers, anyone have a recommendation for a SATA card that could be used instead of the onboard stuff? RAID is not necessary. Thanks again. Cheers, Zube

1 1

Volume of patches for CentOS vs Fedora
by Steve Bergman 27 Jan '06

27 Jan '06

I'm trying to come to a decision between CentOS 4.2 and Fedora Core 4 for use on a server. One of the things the server will be serving is X desktops so there are some advantages to Fedora. However, one thing I can't help but notice is that the patch volume for FC4 from Oct 11 2005 thru the present compared to CentOS 4.2 for the same period is about 5 times greater. In fact, since June, there are 899 RPMs in the FC4 updates directory for FC4 which seems absolutely insane. CentOS is a smaller distro, but not that much smaller. Also, I understand that CentOS's parent distro (from a prominent North American Linux Distributor) is supposed to be better tested before release than Fedora. But still, there must be some other factor to explain the disparity. Like CentOS only releasing a patch for security problems and not bug fixes or something like that. Could someone enlighten me? Thanks, Steve Bergman

6 11

HP storageworks DAT72 USB external tape drive and centos 4.2
by Kim Gabrielsen 27 Jan '06

27 Jan '06

hi, i've bought at HP storageworks DAT72 USB external tape drive and i'm trying to make it work under centos 4.2 first the hard facts: os - centos 4.2 kernel 2.4.9-22.0.2.EL MB - MSI 8kn diamong 4gb ram the problem is that i don't see the drive. i'd expected that a device called st0 would appear but it's not the case. watching the messages file when unplugging the device and the replugging it is: Jan 27 13:47:36 miraculix kernel: usb 1-8: new high speed USB device using address 6 Jan 27 13:47:41 miraculix kernel: usb 1-8: control timeout on ep0in Jan 27 13:47:42 miraculix kernel: usb 1-8: device not accepting address 6, error -71 Jan 27 13:47:42 miraculix kernel: usb 1-8: new high speed USB device using address 7 Jan 27 13:47:47 miraculix kernel: usb 1-8: control timeout on ep0in Jan 27 13:47:48 miraculix kernel: usb 1-8: device not accepting address 7, error -71 Jan 27 13:48:16 miraculix kernel: usb 1-7: new high speed USB device using address 8 Jan 27 13:48:21 miraculix kernel: usb 1-7: control timeout on ep0in Jan 27 13:48:22 miraculix kernel: usb 1-7: device not accepting address 8, error -71 Jan 27 13:48:22 miraculix kernel: usb 1-7: new high speed USB device using address 9 Jan 27 13:48:27 miraculix kernel: usb 1-7: control timeout on ep0in Jan 27 13:48:28 miraculix kernel: usb 1-7: device not accepting address 9, error -71 Jan 27 13:49:01 miraculix kernel: usb 1-1: new high speed USB device using address 10 Jan 27 13:49:07 miraculix kernel: usb 1-1: control timeout on ep0in Jan 27 13:49:07 miraculix kernel: usb 1-1: device not accepting address 10, error -71 Jan 27 13:49:07 miraculix kernel: usb 1-1: new high speed USB device using address 11 Jan 27 13:49:12 miraculix kernel: usb 1-1: control timeout on ep0in Jan 27 13:49:13 miraculix kernel: usb 1-1: device not accepting address 11, error -71 but i don't know what it means. the documentation on the drives says the the two drivers usb_storage and st should be loaded and the drive should work out of the box. but it doesn't. i'm loading both drivers after startup using this command: modprobe usb_storage and modbrobe st what am i missing????? any help appreciated. br kim gabrielsen

1 0

Using Centos
by Alex Chen 27 Jan '06

27 Jan '06

We need to resell systems that run commercial software on Linux. We were using Red Hat ES 3 originally. But we later realize that we cannot redistribute RHES without paying them huge subscription fee because of the trademark. I came across CentOS from WBEL mailing list. This looks like a godsend to me. I have some questions regarding CentOS. I would appreciate it if someone can provide me the answers: 1. Can I use your package to install a machine for resell? Is there fee involved? Do you have any EULA that I can get? 2. I believe it is RHES based, what is the version matrix corresponding to Red Hat ES? 3. Does it have extra stuff other than vanilla RHES added? 4. If I decide to do the rebuild myself to remove the RH trademark stuff, what packages should I modify? Any help will be greatly appreciated. Alex

3 2

Re: su, context(selinux?) 2nd prompt
by Kanwar Ranbir Sandhu 27 Jan '06

27 Jan '06

On Wed, 2006-25-01 at 12:06 -0500, Daniel J Walsh wrote: > >> Remove multiple from the pam file. > >> > > > > editing /etc/pam.d/su, changing > > session required /lib/security/$ISA/pam_selinux.so open multiple > > to > > session required /lib/security/$ISA/pam_selinux.so open > > > > Did the trick, thanks Dan! > > > > # rpm -q -f /etc/pam.d/su > > coreutils-5.2.1-31.2 > > > > > You can actually remove the pam_selinux.so lines from the su file > altogether. We have done this for FC5 and it works > fine. In strict or MLS Policy you will be required to run newrole but > in targeted everything should just work. I'm seeing the same behaviour with telnetd. I had to install it for a client that runs a text based app which Windows users telnet into (it's only open to the local network, and the app loads immediately after login). When a user logs in via telnet, the same question appears. I told my client to just accept the default answer, which is "no". Ideally, I'd like to remove the option all together. I assume it's possible to turn it off like it was for "su", but I'm not sure which file to edit. /etc/pam.d/login looks like the closest one, specifically this line: # pam_selinux.so open should be the last session rule session required pam_selinux.so multiple open I'm not sure though. Any tips? Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.14-1.1656_FC4 i686 GNU/Linux 16:34:54 up 9:34, 5 users, load average: 0.06, 0.35, 0.43

1 0

← Newer
1
...
4
5
6
7
8
9
10
...
34
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss January 2006