Re: verifying a (src) rpm
Ron Rechenmacher wrote: Hi, I want to install kernel-2.6.18-128.1.10.el5.src.rpm which I can get via: wget ftp://linux.fnal.gov/linux/scientific/53/SRPMS/vendor/\ kernel-2.6.18-128.1.10.el5.src.rpm But before I do an rpm --install, I would like to verify the integrity of the rpm. How do I do this? I've found the following web site: http://rhn.redhat.com/errata/RHSA-2009-0473.html which shows: SRPMS: kernel-2.6.18-128.1.10.el5.src.rpm 5784eab8bcaf859f66d0fc09d37870f8 and I assume there is some way to see the associated number on my system if the .src.rpm is valid. The md5sum command produces: # md5sum kernel-2.6.18-128.1.10.el5.src.rpm e505dd681cf83a06410e86f6301feed8 kernel-2.6.18-128.1.10.el5.src.rpm The right number of digits, but the wrong ones. I've noticed the rpmsign command, but it produces: # rpmsign -K kernel-2.6.18-128.1.10.el5.src.rpm kernel-2.6.18-128.1.10.el5.src.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#82fd17b2) But, maybe I don't know how to use it (it's the first time I have). Any help is appreciated. BTW, I've also downloaded the same kernel-2.6.18-128.1.10.el5.src.rpm file from other sites and I get consistent, but different md5sums. Thanks, Ron Hi Ron, The md5sum that you get from our src.rpm directories ftp://linux.fnal.gov/linux/scientific/53/SRPMS/vendor/ is going to be different than if you download it directly from redhat, or someplace that just mirrors them directly ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/os/SRPMS/ The reason for this is that we sign both our compiled rpm's and our sourc rpm's. RedHat doesn't sign their src.rpm's that they put in their public area's. I believe (but haven't verified) that they do sign the rpm's that they put in their rhn area's though. As for verifing rpm's, I usually use the -K option ... which I believe works on src.rpm, but I currently cannot verify that rpm -K package Troy -- __ Troy Dawson daw...@fnal.gov (630)840-6468 Fermilab ComputingDivision/LCSI/CSI DSS Group __
Re: Network driver
Akemi Yagi wrote: On Tue, May 26, 2009 at 9:53 AM, Alan Bartlett ajb.st...@googlemail.com wrote: Thanks Alan. I followed the steps that you given previously to the thread. Now am able to access network. http://www.centos.org/modules/newbb/viewtopic.php?topic_id=19920forum=41 - Not able to access my notwork - Network device not recognized Browse the ElRepo site and download the kmod-atl1 rpm that matches your kernel's type and arch. Then copy the file over to your box and issue: rpm -ivh kmod-atl1 That is excellent news. You have tracked down a recent CentOS forum thread that covers your issue exactly! :-D Now all you need is for someone else to help you get your wireless connection to work. (I'm sorry, I won't be able to help with that -- I have no experience with wireless networking.) Alan. The 3945 wireless device is fully supported in SL 5.3 (iwl3945 driver). There is a CentOS wiki article that may help you: http://wiki.centos.org/HowTos/Laptops/Wireless#head-0cf42e721d60c0cbd8dfe145a4899390b41a5c4c Please note that, unlike CentOS, SL provides the firmware for this device. Unless you must stay with the older kernel, I suggest you update to the current kernel. If you cannot install the 5.3 kernel, then your option is to use the ipw3945 driver (now deprecated) which is also explained in that wiki article. Akemi I'd like to second Akemi's words. If it's possible, do a fresh reinstall of SL 5.3. The intel wireless should just work if you do. Well, you'll need to turn NetworkManager on usually /sbin/chkconfig --level 2345 NetworkManager on /etc/init.d/NetworkManager start We had a user that had the same chipset as you, and for SL 5.1 and 5.2 it never worked very well. Even when he did a yum update to SL 5.3, because enough of the old driver and setups were still on his system. He did a fresh install of SL 5.3, and his wireless worked great. Troy -- __ Troy Dawson daw...@fnal.gov (630)840-6468 Fermilab ComputingDivision/LCSI/CSI DSS Group __
SLC4 - udev
Hello to everyone,
I have a Scientific Linux CERN 4 installation and I need to control an
usb device with it.
My device is an Opal Kelly FPGA with an usb interface.
I need to access it from some c++ code.
In the FPGA user manual they say:
__
The Linux installation requires the addition of one file to the directory:
60-opalkelly.rules - /etc/udev/rules.d/
This file includes a generic udev rule to set the permissions on all
attached Opal Kelly USB devices to allow user access. Once this file is
in place, you will need to reload the rules by either rebooting or using
the following command:
/sbin/udevcontrol reload_rules
__
I successfully copied the file into rules.d/ but I still have some problem.
I don't have the /sbin/udevcontrol application:
all the application with udev in their name are:
udevinfo
udevtest
start_udev
udev
udevd
udevstart
udevstart.static
udev.static
udev_colume_id
the file 60-opalkelly.rules is pasted at the and of this mail.
How do I make the system load this rule manually?
If I reboot while the device is connected everything works fine,
except that I can only access the FPGA with root priviledges. Any way
to allow users to use it?
Thank you in advance,
Nicola Maggi
# udev rules file for all Opal Kelly VID matches.
# This file allows udev to change the mode to 666 (all read/write)
# for any Opal Kelly VID.
#
# For FedoraCore 5 and similar:
SUBSYSTEM==usb_device, SYSFS{idVendor}==151f, MODE=0666
# For FedoraCore 7 and similar:
SUBSYSTEM==usb, ATTRS{idVendor}==151f, MODE=0666
Re: print jobs not send to disabled queues on cups server
hi, we use 2 cups servers with SL53 and cups-1.3.7 (default rpm) an our clients use SL53 too with the same cups-1.3.7 release. the server name is primas1 the config on all clients config is: running a local cupsd and device for printerX: http://primas1:631/printers/printerX?waitjob=no the server config for the same printer is: device for printerX: socket://printerX (there runs a cupsd too) if the queue on server is disabled (cupsdisable printerX) then it's impossible to send jobs to this server and the first lp command on client disables the printer queue on client too - also if spooling on server is enabled. as long we used cups up to version 1.2.4-11.18.el5 the error doesn't appear. the bug is seemed to fixed in version 1.3.10. best regards thomas On Wed, 27 May 2009, Troy Dawson wrote: Thomas Koppe wrote: Hi there, we send all print-jobs to cups (IPP) servers (scientific linux 5.3, cups-1.3.7). If one queue on server is disabled for printing but enabled for spooling then the following happens: if the first job from client will be send to server the local queue will also be disabled and the job remain in the local cups queue. Jobs would only be sent if the server queue is enabled. The local queue is then explicit to enable by root. Is this a known bug ? What can I do in Scientific Linux ? Best regards Thomas Hi Thomas, I just want you to know that both of your posts to this list arrived. I was a bit surprised that nobody responded the first time. I am not a cups expert, but we'll see what we can find. What does your configuration of the printer look like when it is disabled but enabled for spooling? Can you send that part of the configuration file? Or is this all being handled via some interface like cups web interface. Also, what OS is the client running? That might have something to do with it as well. Troy
Re: print jobs not send to disabled queues on cups server
On Wed, 27 May 2009, Thomas Koppe wrote: hi, we use 2 cups servers with SL53 and cups-1.3.7 (default rpm) an our clients use SL53 too with the same cups-1.3.7 release. the server name is primas1 the config on all clients config is: running a local cupsd and device for printerX: http://primas1:631/printers/printerX?waitjob=no the server config for the same printer is: device for printerX: socket://printerX (there runs a cupsd too) if the queue on server is disabled (cupsdisable printerX) then it's impossible to send jobs to this server and the first lp command on client disables the printer queue on client too - also if spooling on server is enabled. as long we used cups up to version 1.2.4-11.18.el5 the error doesn't appear. the bug is seemed to fixed in version 1.3.10. I've occasionally seen this when printing from MacOSX boxes to our SL cups servers but had assumed it was a Mac bug 'cos we hadn't seen it on the SL machines (though we rarely disable printing for a queue without also disabling spooling anyway)... A quick search shows http://cups.org/articles.php?L575 - the announcement of 1.3.9 includes a fix listed as: The IPP backend incorrectly stopped the local queue if the remote server reported the paused state. which is the closest I can find. Sadly that doesn't list an obvious STR so obtaining a patch which could be easily applied to earlier versions might not be trivial, and pursuading TUV to update to 1.3.9 or 1.3.10 may take a lot of doing - they only just updated to 1.3.7 from 1.2.x :-) I see that Apple recently updated the cups in OSX 10.5 to 1.3.10 so for a while at least they are actually up to date! I'm seriously thinking of updating my cups servers to 1.3.10 mostly to get the new pdftops (back-ported from cups-1.4 where pdftops is just a wrapper around one of a variety of pdf handlers...) -- Jon best regards thomas On Wed, 27 May 2009, Troy Dawson wrote: Thomas Koppe wrote: Hi there, we send all print-jobs to cups (IPP) servers (scientific linux 5.3, cups-1.3.7). If one queue on server is disabled for printing but enabled for spooling then the following happens: if the first job from client will be send to server the local queue will also be disabled and the job remain in the local cups queue. Jobs would only be sent if the server queue is enabled. The local queue is then explicit to enable by root. Is this a known bug ? What can I do in Scientific Linux ? Best regards Thomas Hi Thomas, I just want you to know that both of your posts to this list arrived. I was a bit surprised that nobody responded the first time. I am not a cups expert, but we'll see what we can find. What does your configuration of the printer look like when it is disabled but enabled for spooling? Can you send that part of the configuration file? Or is this all being handled via some interface like cups web interface. Also, what OS is the client running? That might have something to do with it as well. Troy -- /\ | Computers are different from telephones. Computers do not ring. | | -- A. Tanenbaum, Computer Networks, p. 32 | -| | Jon Peatfield, _Computer_ Officer, DAMTP, University of Cambridge | | Mail: jp...@damtp.cam.ac.uk Web: http://www.damtp.cam.ac.uk/ | \/
Hello!!
This is my first post to the list. So far, I love SL. I think it's a great distribution,even though I am only using it in a home setting right now. I have one issue,though,and I am wondering if anyone else has had a similar problem. After the liveCD 5.3 install, sound works for the default root and sluser accounts, but not for accounts created post install. When trying to access the volume control in my personal account, it tells me Gstreamer is not installed,or no sound devices were detected. I can configure and test the soundcard as root, from my personal account, and the soundcard auto detect works and the test sounds play. Anyone know what this might be. I am no stranger to Linux,so don't be afraid to throw technical answers my way. Thanks, and other than this tiny issue,I am loving the SL experience. Brice -- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com
Re: question about packaging guidelines
On Sun, May 24, 2009 at 3:18 AM, John Summerfield deb...@herakles.homelinux.org wrote: Why do you think you should install to /opt2? I can't for the moment think why I would, but if I did I most likely create an rpm that contains that directory structure, and list it as a prereq for everything else I was going to build install there. However, this isn't a very standard way of doing things. snip Thanks to everyone for the comments. Shortly before John's above email arrived, I came to his same conclusion. Our site has accumulated lots of non-standard practices over the years such as storing applications in atypical places. My post mentioned /opt2 just to make my situation comprehensible -- the actual setup is far more convoluted. I decided to finally do things the right way after reading the Filesystem Hierarchy Standard: http://www.pathname.com/fhs/ Now I'll just just /opt. If I had stuck with /opt2, I would have created an addons RPM which owned that directory and made other local customizations. Matt
Strategies for setting up scientific packages?
This isn't specifically a Scientific Linux question, but I suspect many of the list's readers are in the same boat as me. We have about 30 scientific packages, of which about 20 are command-line only and about 10 are GUI applications. Rather than have massive, slow, and unmaintainable .cshrc/.bashrc files, people use an application called prepare to set up each app as necessary. prepare originally came from Johan Postma at EMBL Heidelberg and unfortunately its website seems to have disappeared. It's a clever csh script which detects the architecture in use and then sources an appropriate csh file to set up environment variables and aliases. Originally it worked with IRIX and OSF/1, and when Linux came on the scene I made the necessary modifications. The idea is that prepare ccp4 will set up the CCP4 package for whatever type of computer a user is currently using: SGI, Tru64 Alpha, Linux Alpha, Linux x86, or Linux AMD64. Simply typing prepare gives a list of applications currently configured for the computer in use. This has worked well, but I haven't revisited this issue in 15 years and am wondering how the rest of the scientific world solves this problem. All comments welcomed. Matt UCSF
Re: question about packaging guidelines
Matt Harrington wrote: http://www.pathname.com/fhs/ I thought about pointing you in that direction. Now I'll just just /opt. If I had stuck with /opt2, I would have created an addons RPM which owned that directory and made other local customizations. Matt You may wish to add a file or two to /etc/profile.d/ to initialise PATH and (maybe) other environment variables. I suggest doing it in the rpm itself. -- Cheers John -- spambait 1...@coco.merseine.nu z1...@coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-)
Skype video problem
Hello, I have just formatted my hard drive and installed SL5.3 from scratch. Everything (even the wireless!) more or less works now except that there is a minor issue with Skype. I followed the advice in one of the previous emails on this subject and installed Skype using yum localinstall skype-2.0.0.72-centos.i586.rpm after downloading the RPM from the Skype website. The audio works, but the camera does not. When I try to test it, it gives me the following: Skype V4L2: Could not find a suitable capture format Skype V4L2: Could not find a suitable capture format Starting the process... Skype Xv: Xv ports available: 32 Skype XShm: XShm support enabled Skype Xv: Using Xv port 224 Skype Xv: No suitable overlay format found The webcam is a Chicony Electronics USB camera. It looks like there exists a driver for it, (it is labeled USB 2.0 Camera /dev/video0 in Skype), but I don't know how to get Skype to work with it. Does anyone know how to fix this? Thanks. -- Aram
