On Friday, January 19, 2007 @ 5:45 AM, Joe Morris wrote: >Greg Wallace wrote: >> Switching to UTC caused that date message to go away!
>So you must have the setting that said your bios clock was set to utc, >yet before it was actually set to localtime. They only need to agree. I'm still confused about this. My BIOS doesn't have the ability to use UTC vs Local. Plus, I haven't changed my clock configuration since 8.1 and have never had this problem before, so I guess it's something new with 10.2. Anyway, it's working now so I guess that's all that matters. >> Now, the only thing >> that comes out is - >> >> Waiting for device /dev/hda2 to appear: OK >> fsck 1.39 (29-May-2006) >> [/bin/fsck/ext3 (1) -- /] fsck.ext3 -a -CO /dev/hda2 >> / (/dev/hda2) clean, 34... files, 89... blocks >> fsck succeeded. Mounting root device read write Mounting root /dev/hda2 >> >> So if that date problem is cleared up, why do I still get an fsck every time >> I boot? >It is an automatic check to make sure no filesystem needs more extensive >checking. Ok. I always thought that the only time an fsck was invoked was when the number of mounts you had done equaled the setting for that. In the past when an fsck occurred it was always accompanied by a message saying something like "number of mounts since last check exceeded. fsck forced", or something to that effect. Otherwise, I don't ever seeing the words fsck in the log at all. Now it's in the log every time I boot. Maybe it was there before and I just didn't notice it. >> Here is a list of all of the rpmnews on my system. >> >> /etc/cups/printers.conf.rpmnew >> /etc/init.d/smbfs.rpmnew >> /etc/inittab.rpmnew >> /etc/krb5.conf.rpmnew >> /etc/ldap.conf.rpmnew >> /etc/localtime.rpmnew >> /etc/magic.rpmnew >> /etc/networks.rpmnew >> /etc/nsswitch.conf.rpmnew >> /etc/opt/kde3/share/config/k3b/k3bsetup.rpmnew >> /etc/opt/kde3/share/config/khelpcenterrc.rpmnew >> /etc/opt/kde3/share/config/kioslaverc.rpmnew >> /etc/postfix/main.cf.rpmnew >> /etc/samba/lmhosts.rpmnew >> /etc/samba/smb.conf.rpmnew >> /etc/samba/smb.conf.rpmnew~ >> /etc/samba/smbfstab.rpmnew >> /etc/samba/smbpasswd.rpmnew >> /etc/sane.d/dll.conf.rpmnew >> /etc/security/pam_unix2.conf.rpmnew >> /etc/sudoers.rpmnew >> /etc/syslog-ng/syslog-ng.conf.rpmnew >> /etc/X11/qtrc.rpmnew >> /etc/xinetd.d/swat.rpmnew >> /opt/kde3/share/config/kdm/kdmrc.rpmnew >> /etc/udev/rules.d/30-net_persistent_names.rules.rpmnew >> /usr/sbin/useradd.local.rpmnew >> >You should really go through every one of those files and either replace >the orig with the newer one, or at least deal with all those config >files. I see /etc/localtime is one of those files. That was probably >your time problem's root. If you are going to update your install, you >need to finish it by checking and resolving these config files. Yeah. I just recently (a few weeks ago) became aware of what it meant to have RPMNEW files. Should I go through them one by one and see if the date of the RPMNEW is later than the date of the RPM (else, the RPMNEW was created in an earlier install and the RPM would actually be the latest version, right?). For those where the RPMNEW is the latest, is it pretty safe to just swap them in for the regular rpm file? I guess I'd want to do them a few at a time so that if I foul up my system I'll know which one to swap back. >-- >Joe Morris >Registered Linux user 231871 running openSUSE 10.2 x86_64 Greg Wallace -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
