Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I guess we are both late then with this information since it was posted 40 days after your original post in the Fedora Project: Announcing New Direction.
I don't understand that comment. Red Hat Linux end-of-life dates were announced around October 2002, if memory serves correctly. At the time Red Hat Linux 9 was published, it was clear the errata support period would end one year later in April 2004 [unless Red Hat chose to extend the support].
Quote:
What I was looking for and failed to place in my previous post is what alternative is their for us who would like to continue to use Red Hat 9 or is this basically the end of it?
I don't whether that was supposed to answer my two question. You must be able to view the /etc/sysconfig/rhn/up2date file, because it's your up2date config file. If you're unable to view it as "root", you have a serious problem. You should not get an I/O error.
As another step, try something else. Open an X terminal, such as "xterm" and run "up2date --nox -u" in there. What do you get?
With KDE or GNOME you can run konsole or gnome-terminal instead of xterm. If need be, start it via the ALT+F2 "Run Command" box and not via menus.
cat /etc/sysconfig/rhn/up2date should give you the output of the config file. I don't understand at all where you get an input/output error. That could indicate harddisk corruption.
It's a hardware problem or damaged file-system. "cat" would simply print the file contents, even if the file were empty. It's a plain text config file. See whether you've got kernel errors in /var/log/messages.
I checked the messages file and looked at the last 3, 4 days and there was no error mentioned anywhere.
I looked in the rhn dir and the only up2date file there was a key signature file.
is this where is supposed to be a config file ?
I have also now noticed that the up2date button on my desktop has now gone since i have been trying to update.
The last thing it said was 60 updates, no ignores but when I tried to update, zip happened.
BTW I now have the button back and it shows me the 61 files available but tells me Iu should update up2date first.
I managed to get the new cert down and ran up2date up2date and got this..
[root@LinuxBox root]# wget -q -O - https://rhn.redhat.com/help/new-cert.sh | /bin/bash
The file /usr/share/rhn/RHNS-CA-CERT has already been updated.
No further action is necessary.
[root@LinuxBox root]# up2date up2date
warning: can't access /etc/sysconfig/rhn/up2date
Traceback (most recent call last):
File "/usr/share/rhn/up2date_client/configdlg.py", line 220, in finish
if self.writeValues(button):
File "/usr/share/rhn/up2date_client/configdlg.py", line 204, in writeValues
dlg = gnome.ui.GnomeErrorDialog(_(
AttributeError: 'module' object has no attribute 'GnomeErrorDialog'
There was some sort of I/O error: [Errno 5] Input/output error: '/etc/sysconfig/rhn/up2date'
[root@LinuxBox root]#
Retrieval ..
Only ticked items.. Do not upgrade packs when local config file has been modified
Use GPG to verify pak
Pak storage dir: /var/spool/up2date
Packages Exceptions
kernel*
When I click this I get the same few errro lines that was in my previous post, exactly.
I went to the var/spool dir ans there are two text files there..
Redhat-Linux 8 with a bunch of numbers and the saem with (obsulate) in the name and same numbers.
I also unticked the ''Do not upgrade packs when local config file has been modified', but still got the same message.
BTW.
I am doing this in root using the Root Console Konsole.
Both new update files are in /root
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.