Re: I can mount USB HD, but NOT USB Flash drive
Maybe this helps: http://wiki.centos.org/TipsAndTricks/NTFS I'd assume anything that works on Centos should work the same on SL as they both try to keep very close to RHEL. Tim On 22/03/11 23:25, john h outlan wrote: HiI'm using SL6 on laptop, and running most of my business from it. At first I had a problem mounting a usb external 500 gig NTFS HD. I installed ntfs-config x64 for FC13 and all usb devices started mounting and popped right up when I plug it in. However, now, suddenly, all usb devices have stopped mounting again. I reran ntfs-config x64 again to no avail. I'm trying desperately to remember what I've installed that may have caused problems. Can someone give me a hand with this? Help on this would be appreciated as I need to transfer files in the office. thank you! ~~ John H. Outlan CPA Orlando, FL USA cell (407) 924-2727 tel:%28407%29%20924-2727 fax (321) 422-5717 tel:%28321%29%20422-5717 email j...@outlancpa.com mailto:j...@outlancpa.com url http://www.outlancpa.com forum http://scientificlinux.proboards.com/ http://scientificlinux.proboards.com/index.cgi
Re: yum.conf ownership in SL6
On 11/03/11 10:05, Andreas Petzold wrote:
Hi,
in SL5 I replaced the stock yum repository files and /etc/yum.conf with files
customized for our site (local repo mirrors, special excludes etc.) with an
RPM with the following properties:
Requires: redhat-release = %{version}
Provides: yum-conf
Provides: epel-release-5
Obsoletes: yum-conf
Obsoletes: yum-conf-epel
Obsoletes: epel-release
With this setup we were able to prevent updates from SL from clobbering our
repo setup. This worked fine, since the yum-conf package owns /etc/yum.conf
on
SL5.
On SL6 however, yum.conf is owned by the yum package. It doesn't make sense
for us to rebuild that just to insert our own yum.conf. Of course, we will
have to change a few things to accomodate the new sl-release rpm, but that's
fine.
Any ideas?
Cheers,
Andreas
You're not the only one, I found this extremely irritating as we use
puppet to manage yum config.
Tim
Re: install alien
On 10/11/10 12:20, Frenck Cacia wrote: The program that i want to convert from .deb to .rpm is Bitmeteros and yo u can download it here (64 bit): http://codebox.org.uk/pages/bitmeteros/downloads thanks You're going to have to download the source and build it yourself unfortunately. Googling around there don't seem to be any RPMs for RHEL/Scientific Linux and the one you found is from another distro (Fedora perhaps?) that uses a more recent version of glibc, and therefore won't work in RHEL/SL. Even more unfortunately taking a quick look at the .tar.gz you downloaded it doesn't look like it quite follows the standard configure; make; make install sequence for building software. They have a forum (http://codebox.org.uk/forum/forums/list.page) so you should ask the author there how to build and install it. Tim
Re: Unable to compile vips (for nip2)
On 13/09/10 20:44, Przemysław Pawełczyk wrote: Hi, I tried to compile nip2 and vips (first)- You don't have to compile vips, it's in Dag's repository. To install: yum --enablerepo=dag install vips If you're not using the default yum config and Dag's repo isn't setup head here: http://dag.wieers.com/rpm/FAQ.php#B Tim Edwards
Re: user account
On 29/04/10 07:53, vivek chal wrote: hi all, i have a user account named globus and i want to give it all the administrative privileges What is the command to do it. As root run 'visudo' and add a line like this: globus ALL=(ALL) NOPASSWD: ALL This will give globus the ability to run any command as root by putting sudo before it, without being prompted for his/her own password, eg.: sudo service something restart Tim
Re: xorg-x11-fonts-ISO8859-1-75dpi breaks when using rpm
On 27/04/10 15:08, Faye Gibbins wrote: When doing rpm -ivh url to xorg-x11-fonts-ISO8859-1-75dpi there does't seem to be another uri pointing to another rpm that will satisfy the dependency that i can add to the command line. but then we aren't using yum Faye What's wrong with just 'yum install xorg-x11-fonts-ISO8859-1-75dpi' or if you actually just wanted emacs then 'yum install emacs'? If you try to install RPMs individually you'll get these problems, which is why programs like yum (and the repositories behind them) were invented. Tim
Re: [OT] Re: xorg-x11-fonts-ISO8859-1-75dpi breaks when using rpm
On 27/04/10 16:16, Faye Gibbins wrote: Yes but we use the mdp devolved layer and I've asked if their repos are yum enabled and they say no. So unless my LM say's I can create a yum archive I'm not sure what else I can do. Faye Can you get them to agree to at least temporarily let you use yum against the official Scientificlinux repos on the web? If not you're out of luck unfortunately. We used to have no access to yum repositories from our DMZ machines and it was very painful getting something installed with just rpm. One tip though, assuming you have a machine with a working yum (your desktop maybe?), is to do a 'yum whatprovides mkfontdir', where mkfontdir is what it complains is missing. That way you can see exactly which RPM is needed. Tim
Re: udev rule to name USB disks after their serial number
On 05/03/10 16:06, Mark Stodola wrote:
Tim Edwards wrote:
On 05/03/10 15:36, Mark Stodola wrote:
Tim Edwards wrote:
On 05/03/10 15:16, Mark Stodola wrote:
Tim,
I think you are confusing sysfs with environment variables. the
%E{key}
is used for environment variables. The serial number is a SYSFS
attribute. Try changing %E{serial} to %s{serial} and see if it works.
Cheers,
Mark
That didn't work unfortunately, my rules file now looks like this:
KERNEL==sd*, SUBSYSTEMS==scsi, SYMLINK+=disknumber-%s{serial}
Any other ideas?
Tim
It works here, I just made a /etc/udev/rules.d/10-test.rules file with
your above line.
Next I ran 'udevcontrol reload_rules'. I then connected my Kingston USB
drive and /dev/disknumber-5B7A121E appeared.
Do you have any other custom rules that are mangling this one?
Cheers,
Mark
It might just be a peculiarity of the USB stick I'm using to test it
then since it's creating a device '/dev/disknumber-' looking like it
can't find the serial number.
I'll try with one of the actual USB hard drives they're using when I
can get access to one next week.
Tim
You can verify that using 'systool'. Try the following command:
systool -b usb -p -v
Find your USB drive in the output, and there should be something like this:
Device = 1-2
Device path = /sys/devices/pci:00/:00:1a.7/usb1/1-2
bConfigurationValue = 1
bDeviceClass= 00
bDeviceProtocol = 00
bDeviceSubClass = 00
bMaxPacketSize0 = 64
bMaxPower = 200mA
bNumConfigurations = 1
bNumInterfaces = 1
bcdDevice = 0100
bmAttributes= 80
configuration =
devnum = 3
idProduct = 1d00
idVendor= 13fe
manufacturer= Kingston
maxchild= 0
product = DataTraveler 2.0
serial = 5B7A121E
speed = 480
uevent = store method only
version = 2.00
If no serial exists for the device, the serial = line will be absent.
Cheers,
Mark
The serial line exists for this USB stick, but the udev rule still isn't
picking it up:
Device = 1-3.2
Device path = /sys/devices/pci:00/:00:1a.7/usb1/1-3/1-3.2
authorized = 1
bConfigurationValue = 1
bDeviceClass= 00
bDeviceProtocol = 00
bDeviceSubClass = 00
bMaxPacketSize0 = 64
bMaxPower = 200mA
bNumConfigurations = 1
bNumInterfaces = 1
bcdDevice = 4000
bmAttributes= 80
busnum = 1
configuration =
descriptors =
dev = 189:6
devnum = 7
idProduct = 0098
idVendor= 0411
manufacturer= BUFFALO
maxchild= 0
product = USB Flash Disk
quirks = 0x0
serial = AB197514
speed = 480
uevent = MAJOR=189
Tim
udev rule to name USB disks after their serial number
We have a process here were users must push files onto USB disks. The
user logs in remotely to a machine which may have many USB disks
attached and he/she knows the serial number of the disk to write to.
In trying to do away with some complex, hacky scripts I'm trying to
udev-ise this. Ie. when a USB disk is plugged into the machine a symlink
to it is made that is /dev/disknumber-123456 where '123456' is the
serial number of the disk.
My udev rule is:
KERNEL==sd*, SUBSYSTEMS==scsi, SYMLINK+=disknumber-%E{serial}
It can create devices with symlink '/dev/disknumber-' but the
substitution of the ATRR{serial} bit seems to be impossible to get working.
The man page is usual includes no examples which might actually give me
the context I need to properly understand the 'printf-like substitution'
syntax that the developers are talking about.
Tim Edwards
Re: udev rule to name USB disks after their serial number
On 05/03/10 15:16, Mark Stodola wrote:
Tim,
I think you are confusing sysfs with environment variables. the %E{key}
is used for environment variables. The serial number is a SYSFS
attribute. Try changing %E{serial} to %s{serial} and see if it works.
Cheers,
Mark
That didn't work unfortunately, my rules file now looks like this:
KERNEL==sd*, SUBSYSTEMS==scsi, SYMLINK+=disknumber-%s{serial}
Any other ideas?
Tim
Re: 'supervising' in process list
On 05/03/10 15:20, Arnau Bria wrote: Think you're refering to: http://supervisord.org/ http://linux.die.net/man/3/supervisor HTH, Arnau On Thu, Mar 4, 2010 at 1:54 PM, Tim Edwards tedwa...@eso.org mailto:tedwa...@eso.org wrote: I've asked the syslog-ng mailing list but got no response here. I'm not sure if this is something related to syslog or a general thing but can someone explain to me what the 'supervising syslog-ng' process is doing, and where (what package or sub-system) it comes from? root 18622 1 0 08:53 ?00:00:00 supervising syslog-ng root 18623 18622 0 08:53 ?00:00:00 /opt/syslog-ng/sbin/syslog-ng --no-caps Thanks Tim Edwards Maybe, however I can't see any of the config files or binaries mentioned in the documentation on their website on the system. Ie. a simple 'find / | grep -i supervis' returns nothing. Tim Edwards
Re: udev rule to name USB disks after their serial number
On 05/03/10 15:36, Mark Stodola wrote:
Tim Edwards wrote:
On 05/03/10 15:16, Mark Stodola wrote:
Tim,
I think you are confusing sysfs with environment variables. the %E{key}
is used for environment variables. The serial number is a SYSFS
attribute. Try changing %E{serial} to %s{serial} and see if it works.
Cheers,
Mark
That didn't work unfortunately, my rules file now looks like this:
KERNEL==sd*, SUBSYSTEMS==scsi, SYMLINK+=disknumber-%s{serial}
Any other ideas?
Tim
It works here, I just made a /etc/udev/rules.d/10-test.rules file with
your above line.
Next I ran 'udevcontrol reload_rules'. I then connected my Kingston USB
drive and /dev/disknumber-5B7A121E appeared.
Do you have any other custom rules that are mangling this one?
Cheers,
Mark
It might just be a peculiarity of the USB stick I'm using to test it
then since it's creating a device '/dev/disknumber-' looking like it
can't find the serial number.
I'll try with one of the actual USB hard drives they're using when I
can get access to one next week.
Tim
Re: Qt 4 installation and configuration woes
On 04/03/10 01:30, David McLean wrote: Hi all, Typically, I try to figure these type issues out myself but I'm currently under a time crunch, hence the email blast! Now to the point: Has anyone had any issues with installing Qt4 and getting it working properly? It seems as though the basic Qt4 package does not include the make utility qmake. Therefore I tried uninstalling it and downloading direct from Trolltech and building it from source which still leaves me some issues. I do appear to have qmake but I seem to have some environment variable issues. When I try to compile a project, I get the following error response: [r...@dhcp...]# qmake Could not find mkspecs for your QMAKESPEC(linux-g++) after trying: /usr/local/Trolltech/Qt-4.6.2/mkspecs Error processing project file: /home/dmclean/Desktop/VIIBRE/StageController/controller_v_0-01/controller_v_0-01.pro Looks like I've got something looking in the wrong place but the /usr/local/Trolltech/Qt-4.6.2/mkspecs is the correct path to the mkspecs directory. I do not have a lot of experience with system/environment variables. Has anyone experienced anything similar to this? yum whatprovides */qmake From the output of that you can see it looks like qt4-devel is needed: yum install qt4-devel Tim Edwards
'supervising' in process list
I've asked the syslog-ng mailing list but got no response here. I'm not sure if this is something related to syslog or a general thing but can someone explain to me what the 'supervising syslog-ng' process is doing, and where (what package or sub-system) it comes from? root 18622 1 0 08:53 ?00:00:00 supervising syslog-ng root 18623 18622 0 08:53 ?00:00:00 /opt/syslog-ng/sbin/syslog-ng --no-caps Thanks Tim Edwards
Re: ROADMAP - Scientific Linux 4 roadmap
On 27/01/10 17:23, Troy Dawson wrote: Hello, The Scientific Linux development team has put out a roadmap for the future of Scientific Linux 4. http://www.scientificlinux.org/distributions/roadmap Scientific Linux 4 is going to follow the same type of roadmap that we followed for Scientific Linux 3. SL 4.9 will be a legacy release. It will be supported until the time that RedHat no longer supports RHEL 4, which is February 2012. This release will only get minimal support, security updates only. Red Hat calles this Production 3 Life Cycle Phase which is During Production 3, at a minimum, qualified security errata of important or critical impact and selected mission critical bug fixes may be released independent of minor releases. No new functionality, new hardware enablement or updated installation images are planned for release in Production 3 life cycle phase. There are no minor releases planned during this phase. https://www.redhat.com/security/updates/errata/ SL 4.0-4.8 will be obsoleted. Currently that is set to October 10, 2010. That date is flexible. We want to give users at least 6 months to update to SL 4.9. So if SL 4.9 takes too long to be released, we will move the October date back. Summary: SL 4.0-4.8 : Obsolete in October 2010 SL 4.9 : Minimal support (security only) until February 2012 Thank You Scientific Linux Development Team Just wondering what you mean by SL 4.0-4.8 being 'obsolete'? Is it the same as saying that SL4.0-4.7 are currently 'obsolete'? Tim Edwards
Memory limits for Scientific Linux kernels
We're trying to work out memory limits for 32-bit versions of SL4 and 5. Redhat's page (http://www.redhat.com/rhel/compare/) says that the maximums are 64GB or RHEL4 and 16GB for RHEL5 (I guess because they dropped the HUGEMEM kernel RPM in RHEL5). This page (http://www.scientificlinux.org/documentation/misc/limits) says that it's 64GB in SL4 but gives no information for SL5. So two questions: Does SL4 i386 have a 'HUGEMEM' kernel build or do you just build those features into the normal -smp kernel build in order to support 64GB RAM? What is the memory limit on SL5 i386? Thanks Tim Edwards
Re: Memory limits for Scientific Linux kernels
On 28/01/10 18:00, Stephan Wiesand wrote: On Jan 28, 2010, at 16:24 , Alan Bartlett wrote: Perhaps I may be permitted to mention the CentOS product page -- http://www.centos.org/product.html As the objective of the CentOS Project is to be 100% binary compatible with TUV's product, the information on that page should have some relevance to SL users. :-) But then, it's not completely accurate either ;-) I don't see it mention the largesmp and PAE kernels, for instance. Tim, I think the SL5/32 limit is 4 GB (3 GB usable) with the regular kernel, 16 GB with the PAE one. I guess the PAE kernel doesn't get as much testing in the field as x86_64. Just curious: why would you want to run a 32-bit OS on a machine with that much RAM? Regards, Stephan Unfortunately we have some internally-developed software which relies strictly on a particular 'certified' OS version, architecture, package versions etc. It takes a long time to get that re-certified for a newer platform, especially an architecture change. In the meantime we're seeing free reporting 32GB of RAM in an SL5.3 i386 Xen virtual machine that's running the normal SMP kernel. This is why I was a bit confused as I can see no evidence of a HUGEMEM kernel even existing for RHEL or SL 5.x. Here's the output: [r...@localhost ~]# lsb_release -a LSB Version: :core-3.0-ia32:core-3.0-noarch:graphics-3.0-ia32:graphics-3.0-noarch Distributor ID: ScientificSL Description:Scientific Linux SL release 4.3 (Beryllium) Release:4.3 Codename: Beryllium [r...@localhost ~]# free -m total used free sharedbuffers cached Mem: 32503 1405 31097 0230241 -/+ buffers/cache:933 31570 Swap: 1992 0 1992 [r...@localhost ~]# uname -a Linux localhost 2.6.9-89.0.19.ELsmp #1 SMP Fri Jan 8 04:31:36 CST 2010 i686 athlon i386 GNU/Linux Tim Edwards
Re: error -12194
On 27/01/10 08:27, vivek chal wrote: Hi all ! I am using scientific linux 5.1 on my hp laptop. After every 2 sec there appears an error on my screen as: Error establishing an encrypted connection to mail.google.com http://mail.google.com Error code-12194. so i've to refresh the gmail every time it appears and it takes lot of time. plz inform me if i can get away with it. If I google that error this is the 2nd result I get: http://forums.mozillazine.org/viewtopic.php?f=38t=613506start=0st=0sk=tsd=a Tim Edwards
Re: amanda xfs m4 woes
On 18/01/10 17:58, Jim Green wrote: Hi all I'n trying to get amanda working on x86_64 SL51 - problem one, an old bug in the amanda rpm causing a segfault on a double-freed pointer, fixed by obtaining amanda-*-2.5.0p2-8.el5.x86_64.rpm and manually installing, - problem two, we get backups OK on ext3 filesystems but failures on XFS filesystems, google suggests that if amanda is compiled on a system without xfsdump installed then the amanda will be built without xfs support. I think that this has happened - question : can I find out if it has XFS support? I can't see a way - problem three, OK, I'll rebuild it myself, grab the source rpm, rpm -i it into /usr/src, cd to /usr/src/redhat/SPECS rpmbuild -bb amanda.spec result : configure.in:2588: /usr/bin/m4: builtin `mkstemp' requested by frozen file is not supported, google says due to m4 being too old. m4 --versionGNU M4 1.4.5 this seems to be the newest SL5 m4 available. Any ideas? What baffles me is that, if the newest m4 in SL is unable to build the amanda package, then how come the SL amanda rpms exist! where they compiled on another RH variant in some bizzare cross distro compilation exercise?! Any pointers would be gratefully received Cheers Jim We use Amanda here but not the Redhat/SL RPM, Amanda themselves provide RPMs for RHEL4 5: http://www.zmanda.com/download-amanda.php See if that has the XFS stuff built in. Tim Edwards
Re: Serious New Install problem
On 13/01/10 21:09, Troy Dawson wrote: snip What we are planning to do till we can get this sorted out is to install Open Suse 9.3 as 10.3 screwed up with LVM trash. Larry Linder If you do go down the Opensuse route the current version is 11.2 and it works quite nicely, even presents you the option of partitioned-based disk layout or LVM-based in the installer (you can choose to completely customise it too). 9.3 was end-of-life nearly 2.5 years ago and 10.3 is also discontinued. http://en.opensuse.org/SUSE_Linux_Lifetime Good luck Tim Edwards
Re: Missing libraries while building gftp on a dual core 64 bit system
On 04/01/10 15:02, Larry Linder wrote: Like to use gftp to up load stuff to our web pages. Binary for 32 bit has worked well for a long time on RH sytems. We are building a few new systems that use a dual core athelon and would like to continue to use gftp. Downloaded the *.gz files, unpacked them and tried to build the new 64 bit binary. When I run the configure command it is checking to make sure all of the required lib's are present before it builds a make file. Several lib's are missing, empty, or have been renamed. I installed all the SW development tools and libs when I installed SL 5.4 86-64. Don't have a complete list of missing libs on this machine. Any guesses as to what went wrong. Larry Linder yum install gftp (it's in the base repo in SL5.4 x86_64) Tim
yum in 5.4 not seeing some packages
Hi, I have a local repository setup with 8 packages in it. On our Scientific Linux 5.1,5.2 or 5.3 (or RHEL5 of all versions) it works fine. However on our only SL5.4 x86_64 machine yum seems to only be capable of seeing 5 of the RPMs. Here is me trying to see the packages, note the initial output from yum list all (at the bottom) which shows that it sees all 8 packages: [r...@sl5build ~]# yum clean all Loaded plugins: kernel-module Cleaning up Everything [r...@sl5build ~]# yum list all | grep local MySQL-client-community.x86_64 5.1.40-0.rhel5 local MySQL-server-community.x86_64 5.1.40-0.rhel5 local amanda-backup_server.x86_642.6.1p1-1.rhel5 local pgsphere.x86_641.1.0-1 local [r...@sl5build ~]# yum clean all Loaded plugins: kernel-module Cleaning up Everything [r...@sl5build ~]# yum list all Loaded plugins: kernel-module local| 951 B 00:00 local/primary| 5.9 kB 00:00 local 8/8 Here are the files that are in the repository: ls local-rhel5-x86_64/RPMS/ amanda-backup_client-2.6.1p1-1.rhel5.x86_64.rpm amanda-backup_server-2.6.1p1-1.rhel5.x86_64.rpm MySQL-client-community-5.1.40-0.rhel5.x86_64.rpm MySQL-server-community-5.1.40-0.rhel5.x86_64.rpm nagios-eso-plugins-1.2-14.x86_64.rpm pgsphere-1.1.0-1.x86_64.rpm repodata syslog-ng-3.0.4-1.rhel5.amd64.rpm syslog-ng-client-3.0.4-1.rhel5.amd64.rpm The only difference I can see is that these files are named .amd64.rpm instead of .x86_64.rpm - is this a yum bug that it's refusing to look at these files? THanks Tim Edwards
Re: yum in 5.4 not seeing some packages
Troy Dawson wrote:
Hi Tim,
I would suspect any package that is labeled *amd64.rpm
I know in the past, yum doesn't like it when the rpm file name doesn't
match the data that is inside the rpm. I believe this is a security
option and not a bug. You don't want someone slipping in a package
called foo.rpm, that is really a hacked up bar.rpm.
I would do a rpm query on those packages, and if need be, rename them to
what they properly are.
rpm -qpi syslog-ng-3.0.4-1.rhel5.amd64.rpm
rpm -qp syslog-ng-3.0.4-1.rhel5.amd64.rpm --qf ==%{name}==%{arch}==\n
Troy
Hi,
These packages are from the syslog-ng site. The name seems to match
what's inside the package AFAICT (see below).
It looks like our 32-bit Scientific Linux machines, as well as 32- and
64-bit RHEL machines have no problem with these RPMs. It's only the yum
on 64-bit Scientific Linux that's not showing them.
Is there a way to tell yum that 'amd64' is valid?
rpm -qp local-rhel5-x86_64/RPMS/syslog-ng-3.0.4-1.rhel5.amd64.rpm --qf
==%{name}==%{arch}==\n
warning: local-rhel5-x86_64/RPMS/syslog-ng-3.0.4-1.rhel5.amd64.rpm:
Header V3 DSA signature: NOKEY, key ID 2aa28252
==syslog-ng==amd64==
rpm -qpi local-rhel5-x86_64/RPMS/syslog-ng-3.0.4-1.rhel5.amd64.rpm
warning: local-rhel5-x86_64/RPMS/syslog-ng-3.0.4-1.rhel5.amd64.rpm:
Header V3 DSA signature: NOKEY, key ID 2aa28252
Name: syslog-ngRelocations: (not
relocatable)
Version : 3.0.4 Vendor: BalaBit IT Ltd.
Release : 1.rhel5 Build Date: Wed 05 Aug 2009
08:53:47 PM CEST
Install Date: (not installed) Build Host: hapci.balabit
Group : System Environment/DaemonsSource RPM:
syslog-ng-3.0.4-1.rhel5.src.rpm
Size: 12939983 License: BalaBit
Proprietary License
Signature : DSA/SHA1, Wed 05 Aug 2009 08:53:55 PM CEST, Key ID
3bdaf86d2aa28252
Packager: Tamas Pal fo...@balabit.hu
URL : http://www.balabit.com
Summary : Next generation system logging daemon
Description :
The syslog-ng application is a flexible and highly scalable system
logging tool.
It is often used to manage log messages and implement centralized
logging, where
the aim is to collect the log messages of several devices to a single,
central
log server.
The main features of syslog-ng include:
* Support for the BSD (RFC 3164) and IETF (RFC 5424-5428) syslog
protocol
standards
* Secure log transfer and storage using public-key encryption
* Reliable log transfer using TCP and TLS
* Pattern based message classification
* Direct database access for MSSQL, MySQL, Oracle, PostgreSQL, and
SQLite
* Flow-control
* Message filtering based on the content and properties of messages
* Message rewriting
* IPv4 and IPv6 support
* Ability to handle high message rates
* Support for heterogeneous UNIX environments
For details about syslog-ng, see the syslog-ng homepage at:
http://www.balabit.com/network-security/syslog-ng/
The documentation of syslog-ng at:
http://www.balabit.com/support/documentation/
Questions, feedback, and bug reports are welcome at the syslog-ng
mailing list:
https://lists.balabit.hu/mailman/listinfo/syslog-ng
Re: Switch from centos 4 to SL4?
Troy Dawson wrote: Chris Tooley wrote: Hi All, first of all, thanks for the help. If you just want to switch a running system, I *think* this would be all you need to do. 1 - Point Yum to look at SL yum repositories 1a - rm -f /etc/yum.repos.d/*repo (a bit drastic, but if you want to go slow, just move everything) 1b (SL4) - rpm -Uvh http://ftp.scientificlinux.org/linux/scientific/4x/i386/misc/RPMS/yum-conf-latest.SL.noarch.rpm Done. 2 - Replace the following packages: yum (from centos) - yum (from SL) centos-release - sl-release centos-release-notes - sl-release-notes (SL5 Only) I cannot seem to install yum: I get dependency errors: # rpm -i yum-2.4.3-10.SL.noarch.rpm warning: yum-2.4.3-10.SL.noarch.rpm: V3 DSA signature: NOKEY, key ID 82fd17b2 error: Failed dependencies: python-elementtree is needed by yum-2.4.3-10.SL urlgrabber is needed by yum-2.4.3-10.SL So I attempt to follow the dependency trail, and end up stalled at: # rpm -i yum-2.4.3-10.SL.noarch.rpm python-2.3.4-14.7.el4.i386.rpm python-elementtree-1.2.6-4.i386.rpm urlgrabber-2.9.6-1.noarch.rpm warning: yum-2.4.3-10.SL.noarch.rpm: V3 DSA signature: NOKEY, key ID 82fd17b2 warning: python-elementtree-1.2.6-4.i386.rpm: V3 DSA signature: NOKEY, key ID a7048f8d error: Failed dependencies: libdb-4.2.so is needed by python-2.3.4-14.7.el4 As far as I can tell, libdb-4.2 is provided by the package compat-db in SL5, however, the latest version in SL4 is 4.2... (I am attempting to convert to SL4) Am I missing something here? Previously I had converted this system from EL4 to Centos4 - might this have something to do with it? Thanks again! -Chris Yes. EL4 never had yum, or the libraries for yum. Centos 4 had yum, so I had assumed that you had yum installed already. Right at the moment I don't have time to track down which packages, maybe someone else had the list of packages needed for yum to be installed on a EL4 machine? Troy I've been yum-enabling some of our RHEl4 machines in the past few days with (note this is all on *one line* - mail client will stuff up the line breaks): rpm -Uvh ftp://ftp.scientificlinux.org/linux/scientific/46/x86_64/SL/RPMS/yum-2.4.3-2.SL.noarch.rpm ftp://ftp.scientificlinux.org/linux/scientific/46/x86_64/SL/RPMS/urlgrabber-2.9.6-1.noarch.rpm ftp://ftp.scientificlinux.org/linux/scientific/46/x86_64/SL/RPMS/python-elementtree-1.2.6-4.x86_64.rpm ftp://ftp.scientificlinux.org/linux/scientific/46/x86_64/SL/RPMS/python-sqlite-1.1.6-1.x86_64.rpm ftp://ftp.scientificlinux.org/linux/scientific/46/x86_64/SL/RPMS/sqlite-3.1.2-3.x86_64.rpm ftp://ftp.scientificlinux.org/linux/scientific/46/x86_64/SL/RPMS/yum-conf-4x-1-7.SL.noarch.rpm Replace the 46/x86_64/ part with whatever's suitable. Tim
More than one inode per file?
The root partition on one of our machines filled up today because it ran out of indoes. We've cleared out some files but can't see how it could possibly use so many inodes. Find reports ~50,000 files while df -i claims over 620,000 are used out of 640,000. The fs is ext3. [r...@localhost /]# find / -xdev | wc -l 47636 [r...@localhost /]# df -i FilesystemInodes IUsed IFree IUse% Mounted on /dev/sda2 64 623423 16577 98% / /dev/sda1 30120 35 300851% /boot none 210437 1 2104361% /dev/shm /dev/sda58077312 11 80773011% /diska /dev/mapper/vg0-diskb 210122 95868443 20053871095% /diskc /dev/sdc14294967295 30501632 42644656631% /diskb Anyone know why this inconsistency could be? Tim Edwards
Re: Yum install; subversion on x86_64
Troy Dawson wrote: Hi Chris, This is a feature of yum in RHEL5 and SL5. I just double checked to see if this was fixed with 5.4. Nope. Why does it do that? Because at some point yum and/or RedHat decided that would be the thing to do so developers would quit whining about not having their 32 bit libraries. (Don't roll your eyes too much. There are plenty of developers/users here on the scientific-linux-users list that have complained because their favorite 32 bit library wasn't installed by default on a 64 bit machine) I have checked Fedora 11, and it only installs the arch that you are running, and it is almost the same version of yum that is in RHEL 5.4, so I'm thinking it is a feature put in by RedHat. Could I track down and change yum so that it doesn't do this? Yes. Am I going to do it? No. Why? Because that would change the functionality of yum on SL5. This could unexpected results. The one expected result that I don't want is that when someone does an x86_64 install, they would get different packages after the change than before the change. How to really fix it? First complain upstream to RedHat. I do know that this was brought up to RedHat at the Summit when discussing RHEL 6. If this feature makes it into the main RHEL, it will make it into SL. If it is possible for there to be an easy fix so that we could make a SL_ rpm, that would be good. But I personally will not dig through yum to find that fix, I just have too much other stuff to do. But if someone has an easy fix, I wouldn't mind wrapping it into an SL_ rpm. Thanks Troy I had the exact same problem a few days ago, and used the same workaround as Chris. I understand SL not deviating from upstream but I still don't understand upstream's reasoning. If I install subversion.x86_64 I have a working subversion, including all the libs. If a developer decides he wants the 32-bit libs then I could just do yum install subversion.i386, why does it need to install 32-bit by default? And do you know, will this change be rolled out to other packages so that whenever we install something in future it will install both 32- and 64-bit versions of it? Regards Tim Edwards
Re: Kickstarting SL 4.3 on Sun Fire x4140
Troy Dawson wrote: John Summerfield wrote: The obvious (to me) workaround is to install a new NIC, at least for the install. It might also be worth trying to boot a live CD (is CentOS4 available?) http://ftp.scientificlinux.org/linux/scientific/livecd/ There is both a SL 4.3 and the latest SL 4.7. Both worth a try. SL 4.3 to see if it really isn't supported in SL 4.3, and SL 4.7 to see if it's been fixed. I've just tried the 4.3 LiveCD and the network card works perfectly once booted up. In lspci it shows correctly as an 'Ethernet Controller'. For a test I've also tried kickstarting (using the same kickstart file) except with SL 4.7, and this kickstart works perfectly. So I guess it's a bug in anaconda in 4.3 that's fixed before 4.7. I'll try kickstarting off DVD media or putting in another NIC. Thanks Tim Edwards
Kickstarting SL 4.3 on Sun Fire x4140
We're trying to kickstart SL4.3 on a Sunfire x4140 which appears to have inbuilt-NICs which use an Nvidia chipset. The problem is that although the NIC's ROM manages to boot off the network, once anaconda is started it fails to see any network devices. I can see in the messages that the forcedeth kernel module is loaded. I found a RHEL bug that suggests that the NICs are detected as bridge devices and not plain ethernet NICs: https://bugzilla.redhat.com/show_bug.cgi?id=156688 We need to use SL 4.3 (due to internal application certifications) so can anyone suggest a possible workaround for this? Has anyone installed SL/Centos/RHEL 4.x on this server before? Thanks Tim Edwards
Trying KVM out before RHEL/SL 5.4?
We were hoping to evaluate KVM in the coming weeks. However as RHEL 5.4 is not yet out, and it'll be a few weeks after that the Scientific Linux releases 5.4, does anyone know of any easy way to go about getting KVM working on SL 5.3? Or would it be better to wait for SL5.4 - if so any ideas when that is likely to be out? Thanks Tim Edwards
Re: upgrading strategy for gimp, gtk+, glib etc
Akemi Yagi wrote: I did not quote this CentOS forum thread here because, as I (toracat) stated there, it was a quick and dirty way to compile / install Gimp 2.4. I just wanted to show what system files get overwritten and that is a no-no in an Enterprise class distribution. I think it'd be better to use Ubuntu, Mandriva or OpenSuse if you want recent versions of desktop software like GIMP. The stability of SL/Centos/RHEL is good for servers but has this downside for desktop usage. Tim Edwards
Re: No Outgoing Sound with Skype
suvayu ali wrote: AFAIK skype doesn't use pulseaudio so the lack of pulseaudio should not be a problem. But I maybe wrong. It doesn't support pulseaudio, much to the annoyance of those of us who use more up-to-date distros than RHEL/SL at home.
