Tomasz Grzelak pisze:


2009/10/16 Mader, Alexander <auma...@gmx.net <mailto:auma...@gmx.net>>

    Tomasz Grzelak schrieb:
    > what is the status of the case - am I the only one experiencing the
    > problem still?
    > Is there anyone affected by this even with the new version of
    util-linux
    > 2.16.1-4?
    As mentioned in an earlier e-mail everything works fine since I edited
    the hwclock-udev-rule as decribed in another e-mail in this bug
    report.

Hello,

I am sorry, but I'm still affected by this problem. I have added the lines to the file, so now it contains:

m...@daemon:~$ cat /lib/udev/rules.d/85-hwclock.rules
# Reset the System Clock to UTC if the hardware clock from which it was
# copied by the kernel was in localtime.

KERNEL=="rtc0", RUN+="/lib/udev/hwclock-set $root/$name"
KERNEL=="rtc0", RUN+="/bin/touch /dev/rtc0-appeared"
KERNEL=="rtc0", RUN+="logger.agent"


but it does not change anything for me.
Immediatelly after I had removed

[options]
       buggy_init_scripts = 1


from e2fsck.conf file, and rebooted the machine, I got the error about "last superblock write time in future" (exactly the same as on the screenshots I attached previously).


In my opinion the problem has not been solved.

How about others?

B. Regards,
Tomasz Grzelak

P.S.
Before having made the test I updated all packages, so my system was fresh.




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to