> From: Michael Schwendt

> Please do not quote e-mail addresses. They make it into the archives
> where -- even after a long time -- address collectors can still
> harvest them for bulk e-mail address listings.

Sorry, I try to be careful about distributing e-mail addresses, that one
didn't get my attention.  However, your e-mail is still included in the
archives, whether it is quoted or not... That's why I use a different
address for high-volume lists like this one.


> Which is correct, because only a very few i686 packages exist.
> glibc-common doesn't contain any files where i686-specific
> optimization would make sense.

So I should install as much i686 packages as possible and use i386
packages when there isn't an i686 package available?
I was under the impression that mixing i686 and i686 wasn't a good idea.

> That doesn't show the architecture. Query with:

indeed that's much better, thanks!
[M8ram@localhost M8ram]$ rpm -qa --qf "%{name}-%{version}-%{release} is
for %{arch}\n" | grep kernel
kernel-utils-2.4-7.4 is for i386
kernel-2.4.18-3 is for i686
kernel-source-2.4.18-19.7.x is for i386
kernel-doc-2.4.18-19.7.x is for i386
kernel-2.4.18-19.7.x is for i386
[M8ram@localhost M8ram]$ rpm -qa --qf "%{name}-%{version}-%{release} is
for %{arch}\n" | grep glibc 
glibc-2.2.5-42 is for i386
glibc-debug-2.2.5-42 is for i386
compat-glibc-6.2-2.1.3.2 is for i386
glibc-utils-2.2.5-42 is for i386
glibc-profile-2.2.5-42 is for i386
glibc-kernheaders-2.4-7.16 is for i386
glibc-debug-static-2.2.5-42 is for i386
glibc-devel-2.2.5-42 is for i386
glibc-common-2.2.5-42 is for i386

I do have the following i686 packages:
glibc-2.2.5-42.i686.rpm
glibc-debug-2.2.5-42.i686.rpm
kernel-2.4.18-19.7.x.i686.rpm
kernel-debug-2.4.18-19.7.x.i686.rpm

Should I upgrade? can I even do this without problems? I mean won't rpm
complain that kernel-2.4.18-19.7.x is already installed? or does it
check the architecture as well?

Or is it best to leave this as they are, because everything seems to be
fine now...

> Do you have the network time protocol daemon enabled? See checkbox
> in dateconfig as well as "chkconfig --list ntpd". If you want it and
> need it, you may need to check its config file.

I thought I only needed to enable this if I wanted my machine to look up
the current time through the net, it was disabled because I don't need
this, but I started it before running dateconfig which seemed to have
helped.  I disabled the option in dateconfig because I wasn't able to
edit the time while it was enabled.

Now the daemon isn't running anymore:
[M8ram@localhost M8ram]$ su -   
Password: 
[root@localhost root]# chkconfig --list ntpd
ntpd            0:off   1:off   2:off   3:off   4:off   5:off   6:off

But the time and timezone seem to be correct, so I guess that's solved.

Thanks again for your help!
-- 
 #  Mertens Bram "M8ram"  <[EMAIL PROTECTED]>  Linux User #249103  #
 # Red Hat Linux release 7.3 (Valhalla) kernel 2.4.18-19.7.x i686 128MB RAM #
 #  2:32pm up 21:09, 1 user, load average: 0.15, 0.20, 0.16 #



-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to