Re: How can I install Skype on SL 5.0 ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 skype-2.0.0.72-centos.i586 works fine on sl5.2 Pedro Ferreira wrote: Hello all, I dont't know how to install skype on my SL5. I don't even know which distribution I should download, since there are no Red Hat versions. Which dependencies will I need to install? Thanks, Pedro Ferreira. Veja quais são os assuntos do momento no Yahoo! + Buscados: Top 10 http://br.rd.yahoo.com/mail/taglines/mail/*http://br.maisbuscados.yahoo.com/ - Celebridades http://br.rd.yahoo.com/mail/taglines/mail/*http://br.maisbuscados.yahoo.com/celebridades/ - Música http://br.rd.yahoo.com/mail/taglines/mail/*http://br.maisbuscados.yahoo.com/m%C3%BAsica/ - Esportes http://br.rd.yahoo.com/mail/taglines/mail/*http://br.maisbuscados.yahoo.com/esportes/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFJt78dOMIGC6x7/XQRAtCFAKCC2INEfmFLahTY5MOvmuUG46n8tQCgvRFH t1VlFgUIUNQCXz/FEZh08lw= =0IMR -END PGP SIGNATURE- begin:vcard fn:Robert Blair n:Blair;Robert org:Argonne National Lab;HEP adr:;;9700 S. Cass Ave.;Argonne;IL;60439;USA email;internet:r...@anl.gov tel;work:630-252-7545 tel;fax:630-252-5782 x-mozilla-html:FALSE url:http://www.hep.anl.gov/reb version:2.1 end:vcard smime.p7s Description: S/MIME Cryptographic Signature
Re: How can I install Skype on SL 5.0 ?
Pedro, For me I used the 'static' version, follow the instructions included with the tar file. Unfortunately, the audio mixer in SL doesn't allow for Skype calls so I just use it to send IMs. (If anyone has had success configuring skype for calls, then please let me know how you did it!) Craig On Wed, 2009-03-11 at 06:30 -0700, Pedro Ferreira wrote: Hello all, I dont't know how to install skype on my SL5. I don't even know which distribution I should download, since there are no Red Hat versions. Which dependencies will I need to install? Thanks, Pedro Ferreira. __ Veja quais são os assuntos do momento no Yahoo! + Buscados: Top 10 - Celebridades - Música - Esportes
Re: How can I install Skype on SL 5.0 ?
Craig Moore wrote: Pedro, For me I used the 'static' version, follow the instructions included with the tar file. Unfortunately, the audio mixer in SL doesn't allow for Skype calls so I just use it to send IMs. (If anyone has had success configuring skype for calls, then please let me know how you did it!) skype-2.0.0.72-centos.i586.rpm works for me with video and audio under SL52. Urs
Re: How can I install Skype on SL 5.0 ?
Try the CentOS package. It will let you know of dependencies when you try to install. Cheers, Mark Pedro Ferreira wrote: Hello all, I dont't know how to install skype on my SL5. I don't even know which distribution I should download, since there are no Red Hat versions. Which dependencies will I need to install? Thanks, Pedro Ferreira. Veja quais são os assuntos do momento no Yahoo! + Buscados: Top 10 http://br.rd.yahoo.com/mail/taglines/mail/*http://br.maisbuscados.yahoo.com/ - Celebridades http://br.rd.yahoo.com/mail/taglines/mail/*http://br.maisbuscados.yahoo.com/celebridades/ - Música http://br.rd.yahoo.com/mail/taglines/mail/*http://br.maisbuscados.yahoo.com/m%C3%BAsica/ - Esportes http://br.rd.yahoo.com/mail/taglines/mail/*http://br.maisbuscados.yahoo.com/esportes/ -- Mr. Mark V. Stodola Digital Systems Engineer National Electrostatics Corp. P.O. Box 620310 Middleton, WI 53562-0310 USA Phone: (608) 831-7600 Fax: (608) 831-9591
Re: determining the appropriate sata driver
Mark Stodola wrote: I believe most of anaconda's magic comes from probing the PCI and USB bus for vendor and device IDs. If you dig into a driver (for example, e1000e), you will find a pcitable listing all of the IDs the driver supports. If you look in /lib/modules/kernel/ you will find a modules.pcimap and modules.usbmap among other bus types. Hope that helps. Cheers, Mark Ken Teh wrote: How does a system determine the appropriate sata driver? Specifically, how does anaconda figure out to write alias scsi_hostadapter ata_piix in my modprobe.conf and to bind it into my initrd image? I took apart boot.iso but didnt find anything readable that indicated how this was determined. Thanks! Ken Hi Ken, On SL 5, alot of that data comes from hwdata, which is in the /usr/share/hwdata directory. The main ones people and programs look at is pci.ids and usb.ids But there are other files in there. Troy -- __ Troy Dawson daw...@fnal.gov (630)840-6468 Fermilab ComputingDivision/LCSI/CSI LMSS Group __
Re: determining the appropriate sata driver
Hi Troy, I'm looking for something more basic. I'm trying to craft an init script for an initrd image to load appropriate drivers. Nothing fancy. Just the basics. Like what sort of hard drives are on the system. SATA or IDE? The SATA issue confuses me since there is a plethora of SATA drivers. Does the init script have to try each one to see if it finds a match or is there something in /proc or /sys that provides some identification? The only tool I have in my initrd image is busybox and it doesnt have an lspci equivalent. The /proc system contains a subdirectory that lists all devices on PCI but as bus.device files. I tried cat'ing the files but they are not ascii. I'm guessing it's possible to walk these files to extract the information I need. I can dig deeper but to save time, I'd ask if someone already knows the answer. Ken Troy Dawson wrote: Mark Stodola wrote: I believe most of anaconda's magic comes from probing the PCI and USB bus for vendor and device IDs. If you dig into a driver (for example, e1000e), you will find a pcitable listing all of the IDs the driver supports. If you look in /lib/modules/kernel/ you will find a modules.pcimap and modules.usbmap among other bus types. Hope that helps. Cheers, Mark Ken Teh wrote: How does a system determine the appropriate sata driver? Specifically, how does anaconda figure out to write alias scsi_hostadapter ata_piix in my modprobe.conf and to bind it into my initrd image? I took apart boot.iso but didnt find anything readable that indicated how this was determined. Thanks! Ken Hi Ken, On SL 5, alot of that data comes from hwdata, which is in the /usr/share/hwdata directory. The main ones people and programs look at is pci.ids and usb.ids But there are other files in there. Troy
Re: How can I install Skype on SL 5.0 ?
On Wed, Mar 11, 2009 at 6:46 AM, Urs Beyerle urs.beye...@env.ethz.ch wrote: Craig Moore wrote: Pedro, For me I used the 'static' version, follow the instructions included with the tar file. Unfortunately, the audio mixer in SL doesn't allow for Skype calls so I just use it to send IMs. (If anyone has had success configuring skype for calls, then please let me know how you did it!) skype-2.0.0.72-centos.i586.rpm works for me with video and audio under SL52. And this CentOS Wiki might be helpful, too: http://wiki.centos.org/HowTos/Skype Akemi
Re: determining the appropriate sata driver
Ken, /proc/pci contains much of the info provided by lspci. For an initrd script, you might want to consider looking at the linux-live scripts used to build many of the livecds you find online (include the SL flavor made by Urs). I believe if you look at Urs's livecd-trunk, you will find linux-live.sl/initrd/liblinuxlive. This file has procedures for probing all common modules for a certain type of support (e.g. modprobe_usb_sata_modules). Brute force seems the standard way to go. I've made livecds in several ways, and have not run into a situation where I had to manually identify and probe modules for a specific IDE or SATA controller. Are you doing something drastically different from the norm? Cheers, Mark Ken Teh wrote: Hi Troy, I'm looking for something more basic. I'm trying to craft an init script for an initrd image to load appropriate drivers. Nothing fancy. Just the basics. Like what sort of hard drives are on the system. SATA or IDE? The SATA issue confuses me since there is a plethora of SATA drivers. Does the init script have to try each one to see if it finds a match or is there something in /proc or /sys that provides some identification? The only tool I have in my initrd image is busybox and it doesnt have an lspci equivalent. The /proc system contains a subdirectory that lists all devices on PCI but as bus.device files. I tried cat'ing the files but they are not ascii. I'm guessing it's possible to walk these files to extract the information I need. I can dig deeper but to save time, I'd ask if someone already knows the answer. Ken Troy Dawson wrote: Mark Stodola wrote: I believe most of anaconda's magic comes from probing the PCI and USB bus for vendor and device IDs. If you dig into a driver (for example, e1000e), you will find a pcitable listing all of the IDs the driver supports. If you look in /lib/modules/kernel/ you will find a modules.pcimap and modules.usbmap among other bus types. Hope that helps. Cheers, Mark Ken Teh wrote: How does a system determine the appropriate sata driver? Specifically, how does anaconda figure out to write alias scsi_hostadapter ata_piix in my modprobe.conf and to bind it into my initrd image? I took apart boot.iso but didnt find anything readable that indicated how this was determined. Thanks! Ken Hi Ken, On SL 5, alot of that data comes from hwdata, which is in the /usr/share/hwdata directory. The main ones people and programs look at is pci.ids and usb.ids But there are other files in there. Troy -- Mr. Mark V. Stodola Digital Systems Engineer National Electrostatics Corp. P.O. Box 620310 Middleton, WI 53562-0310 USA Phone: (608) 831-7600 Fax: (608) 831-9591
Re: determining the appropriate sata driver
On 10/03/2009, Ken Teh t...@anl.gov wrote: How does a system determine the appropriate sata driver? Specifically, how does anaconda figure out to write alias scsi_hostadapter ata_piix in my modprobe.conf and to bind it into my initrd image? I took apart boot.iso but didnt find anything readable that indicated how this was determined. Ken, I wonder if the helper script, get-driver.sh, referenced on p61 of Linux Kernel in a Nutshell by Greg Kroah-Hartman and available to download from the publisher's web-site [1] will be any use to you? Regards, Alan. [1] http://examples.oreilly.com/9780596100797/examples.tar.gz
Re: How can I install Skype on SL 5.0 ? DONE
Thank you all ! Now I just have to configure my microfone. --- Em qua, 11/3/09, Urs Beyerle urs.beye...@env.ethz.ch escreveu: De: Urs Beyerle urs.beye...@env.ethz.ch Assunto: Re: How can I install Skype on SL 5.0 ? Para: Robert E. Blair r...@anl.gov Cc: pedrojun...@yahoo.com.br, scientific-linux-us...@fnal.gov Data: Quarta-feira, 11 de Março de 2009, 10:40 Robert E. Blair wrote: skype-2.0.0.72-centos.i586 works fine on sl5.2 Download from http://www.skype.com/download/skype/linux/choose/ and install it as root with yum localinstall skype-2.0.0.72-centos.i586.rpm Not fully true, but almost ... CentOS 5 = SL 5 = RHEL 5 Urs Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com
Re: determining the appropriate sata driver
Hi Ken, In the LiveCD initrd I probe for modules needed to access CD/DVD ROMS (IDE, SATA), USB disks/sticks and network cards (in case of a diskless client). https://svn.iac.ethz.ch/pub/livecd/trunk/linux-live.sl/initrd/linuxrc https://svn.iac.ethz.ch/pub/livecd/trunk/linux-live.sl/initrd/liblinuxlive The SATA part is very simple, I just load libata, ata_piix, ahci, sata_nv, sata_svw, sg, ... This seems to be good enough for most DVD/CD ROMS connected over SATA. Of course I would be interested in a more intelligent way to load the sata modules. Concerning the detection of the network card. I did it on older LiveCDs with a statically compiled lspci (running under busybox) and some grep commands looking in the file pcitable for the correct module. The static lspci is still available in https://svn.iac.ethz.ch/pub/livecd/trunk/linux-live.sl/initrd/static-binaries/ However, pcitable was always out of date and the modules could support more cards than listed in pcitable. Therefore I decided to do it with brute force. Now, I load a network module, check if I see an active link. If not, I unload the module again and load the next network module ... and so on. This is fast and works nicely. Cheers, Urs Mark Stodola wrote: Ken, /proc/pci contains much of the info provided by lspci. For an initrd script, you might want to consider looking at the linux-live scripts used to build many of the livecds you find online (include the SL flavor made by Urs). I believe if you look at Urs's livecd-trunk, you will find linux-live.sl/initrd/liblinuxlive. This file has procedures for probing all common modules for a certain type of support (e.g. modprobe_usb_sata_modules). Brute force seems the standard way to go. I've made livecds in several ways, and have not run into a situation where I had to manually identify and probe modules for a specific IDE or SATA controller. Are you doing something drastically different from the norm? Cheers, Mark Ken Teh wrote: Hi Troy, I'm looking for something more basic. I'm trying to craft an init script for an initrd image to load appropriate drivers. Nothing fancy. Just the basics. Like what sort of hard drives are on the system. SATA or IDE? The SATA issue confuses me since there is a plethora of SATA drivers. Does the init script have to try each one to see if it finds a match or is there something in /proc or /sys that provides some identification? The only tool I have in my initrd image is busybox and it doesnt have an lspci equivalent. The /proc system contains a subdirectory that lists all devices on PCI but as bus.device files. I tried cat'ing the files but they are not ascii. I'm guessing it's possible to walk these files to extract the information I need. I can dig deeper but to save time, I'd ask if someone already knows the answer. Ken Troy Dawson wrote: Mark Stodola wrote: I believe most of anaconda's magic comes from probing the PCI and USB bus for vendor and device IDs. If you dig into a driver (for example, e1000e), you will find a pcitable listing all of the IDs the driver supports. If you look in /lib/modules/kernel/ you will find a modules.pcimap and modules.usbmap among other bus types. Hope that helps. Cheers, Mark Ken Teh wrote: How does a system determine the appropriate sata driver? Specifically, how does anaconda figure out to write alias scsi_hostadapter ata_piix in my modprobe.conf and to bind it into my initrd image? I took apart boot.iso but didnt find anything readable that indicated how this was determined. Thanks! Ken Hi Ken, On SL 5, alot of that data comes from hwdata, which is in the /usr/share/hwdata directory. The main ones people and programs look at is pci.ids and usb.ids But there are other files in there. Troy
Re: my ongoing battle with large filesystems
Jon Peatfield said... [snip] |Re-configuring your RAID controllers to export as 2TB slices isn't fun, |but it should be possible without a re-install (if a bit fiddly). Thanks for all of this. I'll look again, but I didn't notice anything obvious in the Adaptec screens at boot that would do this. Any key phrases to look for? Thanks, Miles
Re: my ongoing battle with large filesystems
On Wed, 11 Mar 2009, Miles O'Neal wrote: Jon Peatfield said... [snip] |Re-configuring your RAID controllers to export as 2TB slices isn't fun, |but it should be possible without a re-install (if a bit fiddly). Thanks for all of this. I'll look again, but I didn't notice anything obvious in the Adaptec screens at boot that would do this. Any key phrases to look for? With luck it is somewhere in the 'container' documentation/descriptions. I don't have a lot of experience with recent Adaptec raid controllers, on one box with ~3TB of disk on an adaptec 216010SA it had to be configured as 2 RAID-5 sets each over parts of the same disks which sounds horrid I know... ie in aaccli (yes this is old!) we see: CLI open aac0 Executing: open aac0 AAC0 disk list Executing: disk list C:ID:L Device Type BlocksBytes/Block UsageShared Rate -- -- - --- -- 0:00:0 Disk488397168 512 Initialized NO 264 0:01:0 Disk488397168 512 Initialized NO 264 0:02:0 Disk488397168 512 Initialized NO 264 0:03:0 Disk488397168 512 Initialized NO 264 0:04:0 Disk488397168 512 Initialized NO 264 0:05:0 Disk488397168 512 Initialized NO 264 0:06:0 Disk488397168 512 Initialized NO 264 0:07:0 Disk488397168 512 Initialized NO 264 1:00:0 Disk488397168 512 Initialized NO 264 1:01:0 Disk488397168 512 Initialized NO 264 1:02:0 Disk488397168 512 Initialized NO 264 1:03:0 Disk488397168 512 Initialized NO 264 1:04:0 Disk488397168 512 Initialized NO 264 1:05:0 Disk488397168 512 Initialized NO 264 1:07:0 Disk488397168 512 Initialized NO 264 AAC0 disk show part Executing: disk show partition Scsi Partition Container MultiLevel C:ID:L Offset:Size Num Type Num Type R/W -- - --- -- --- -- --- 0:00:0 64.0KB: 116GB 0 RAID-5 0 None RW 0:00:0 116GB: 116GB 1 RAID-5 0 None RW 0:01:0 64.0KB: 116GB 0 RAID-5 0 None RW 0:01:0 116GB: 116GB 1 RAID-5 0 None RW 0:03:0 64.0KB: 116GB 0 RAID-5 0 None RW 0:03:0 116GB: 116GB 1 RAID-5 0 None RW 0:04:0 64.0KB: 116GB 0 RAID-5 0 None RW 0:04:0 116GB: 116GB 1 RAID-5 0 None RW 0:05:0 64.0KB: 116GB 0 RAID-5 0 None RW 0:05:0 116GB: 116GB 1 RAID-5 0 None RW 0:06:0 64.0KB: 116GB 0 RAID-5 0 None RW 0:06:0 116GB: 116GB 1 RAID-5 0 None RW 0:07:0 64.0KB: 116GB 0 RAID-5 0 None RW 0:07:0 116GB: 116GB 1 RAID-5 0 None RW 1:00:0 64.0KB: 116GB 0 RAID-5 0 None RW 1:00:0 116GB: 116GB 1 RAID-5 0 None RW 1:01:0 64.0KB: 116GB 0 RAID-5 0 None RW 1:01:0 116GB: 116GB 1 RAID-5 0 None RW 1:02:0 64.0KB: 116GB 0 RAID-5 0 None RW 1:02:0 116GB: 116GB 1 RAID-5 0 None RW 1:03:0 64.0KB: 116GB 0 RAID-5 0 None RW 1:03:0 116GB: 116GB 1 RAID-5 0 None RW 1:04:0 64.0KB: 116GB 0 RAID-5 0 None RW 1:04:0 116GB: 116GB 1 RAID-5 0 None RW 1:05:0 64.0KB: 116GB 0 RAID-5 0 None RW 1:05:0 116GB: 116GB 1 RAID-5 0 None RW 1:07:0 64.0KB: 116GB 1 RAID-5 0 None RW 1:07:0 116GB: 116GB 0 RAID-5 0 None RW AAC0 contain list Executing: container list Num Total Oth Stripe Scsi Partition Label Type Size Ctr Size Usage C:ID:L Offset:Size - -- -- --- -- --- -- - 0RAID-5 1.47TB 64KB Open0:00:0 64.0KB: 116GB /dev/sda SubData 0:01:0 64.0KB: 116GB 0:04:0 64.0KB: 116GB 0:03:0 64.0KB: 116GB 1:07:0 116GB: 116GB 0:05:0 64.0KB: 116GB 0:06:0 64.0KB: 116GB 0:07:0 64.0KB: 116GB 1:00:0 64.0KB: 116GB 1:01:0 64.0KB: 116GB 1:02:0 64.0KB: 116GB 1:03:0 64.0KB: 116GB 1:04:0 64.0KB: 116GB 1:05:0 64.0KB: 116GB 1RAID-5 1.47TB 64KB Open0:00:0 116GB: 116GB /dev/sdb SubData2 0:01:0 116GB: 116GB 0:04:0 116GB: 116GB 0:03:0 116GB: 116GB 1:07:0 64.0KB: 116GB 0:05:0 116GB: 116GB
