Red Hat Bugzilla – Bug 9973
Wrong date in .conf file
Last modified: 2008-05-01 11:37:54 EDT
Linuxconf reports when exiting that /etc/sysconfig/mouse and other files
from /etc directory have a date in the future. This bug started since
1st january of y2k. I tested on two totally different computers (P75,K6-2
450) and with redhat 6.0 and now with official redhat 6.1. Linuxconf told
about the first time linux is installed.
Please verify that this is still a problem with the latest version of linuxconf
from Raw Hide (ftp://ftp.redhat.com/pub/rawhide/i386/RedHat/RPMS/). I've not
experienced this problem, so I suspect the cause is elsewhere. What is the
timestamp on the file?
I just installed my system and had the exact same problem, other files it says
are inetd, mouse and two others, I restart the system and the changes I have
made dont appear to have worked..
I configured (in linux conf) Lilo to boot windows before linux and it always
boots linux, the lilo.conf says that default is windows, but when I tried to
run lilo -u to uninstall it (and boot from disk) it says about the date
incorrect on boot.b and that I should use lilo -U (if I know what I am doing)
so I try and it doesnt remove lilo and still boots linux before dos (although
the conf file says windows, not dos) I have noticed a boot.800 file, which I
guess is the windows image. now the boot.b file is an older date and the
boot.800 is the current date.
in linuxconf, I set the time and everytime I go back the time zone has changed
back to ,no time zone, so I set it Australia/Adelaide and next time I go back
its incorrect, and it always gives me the message when I activate the changes;
the file /etc/inetd as a date in the future, which says that your clock may be
set incorrectly or has been in the past. (and about three other files
I have also had this on a totally different computer, in both kde or text mode.
Closing because we don't ship linuxconf anymore
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.