Hello,
I'm still having the same issue.
I made an update, and rebooted the machine which casued the error
appeared again.
I have a dual boot machine, but I have not run vista today yet.
And there's a 'screenshot' what happend after the restart right after
having updated all the packages:
Hello,
like I was afraid, having used older versions of e2fslibs and progs did
not change the situation, today (Sat 10.10.2009) I got the error again.
Next I updated all packages, and while rebooting I got the same error
again :(
Please have a look at the picture I took with my camera:
Let's try some simple and stupid debugging. Somebody who can reliably
reproduce the problem please add something like this to the *end* of
/lib/udev/rules.d/85-hwclock.rules :
KERNEL==rtc0, RUN+=/bin/touch /dev/rtc0-appeared
KERNEL==rtc0, RUN+=logger.agent
Hello,
I did try it and it was
[Marco d'Itri]
Petter determined that this works. I think that the real problem is
that the RUN rules in 85-hwclock.rules are only executed if
ENV{BADYEAR} exists.
Could be.
Importing /etc/default/rcS as if were a list of variables looks like
a bad idea to me anyway, so please replace the
On Mon, Oct 05, 2009 at 08:04:23AM +0200, Mader, Alexander (N-MSR) wrote:
Something additional: I am running a Debian kernel not a self built one,
and /lib/udev/rules.d/85-hwclock.rules was not there in the first place
so I had to create it.
That file is delivered by util-linux what
LaMont Jones schrieb:
On Mon, Oct 05, 2009 at 08:04:23AM +0200, Mader, Alexander (N-MSR) wrote:
Something additional: I am running a Debian kernel not a self built one,
and /lib/udev/rules.d/85-hwclock.rules was not there in the first place
so I had to create it.
That file is delivered by
Hi!
The two lines in /lib/udev/rules.d/85-hwclock.rules didn't change a thing for
me. Btw, I'm using the 2.6.30er kernel from here:
http://kernel-archive.buildserver.net/debian-kernel sid main
Since the last Debian update, however, the fsck problem doesn't
seem to appear anymore.
My guess is
Hello,
this is my first post here, and I'd like to report the bug is also affecting
me.
I have been using Debian unstable (AMD64) for about two years (with regular
updates every several days), and the issue started to occur around the
beginning of August (never had this problem before).
My first
On Sep 25, Marco d'Itri m...@linux.it wrote:
KERNEL==rtc0, RUN+=logger.agent
Petter determined that this works. I think that the real problem is
that the RUN rules in 85-hwclock.rules are only executed if
ENV{BADYEAR} exists.
Importing /etc/default/rcS as if were a list of variables looks like a
[LaMont Jones]
I completely agree on the severity, and would love to hear from the
people who convinced me this would work. again.
I guess that was me and Scott. :)
The idea was to allow the init.d scripts detect when udev would take
care of setting the system clock from the hardware clock
On Sep 25, Petter Reinholdtsen p...@hungry.com wrote:
I was told that udev would run the udev rule to set the system clock
if it was enabled, and thus believed it would be sufficient to look
for the existence of /dev/.udev to decode when to disable the init.d
scripts. Obviously this
Processing commands for cont...@bugs.debian.org:
severity 543375 serious
Bug #543375 [util-linux] initscripts: last superblock write time in future
occurring sometimes
Severity set to 'serious' from 'important'
thanks
Stopping processing here.
Please contact me if you need assistance.
On Thu, Sep 24, 2009 at 02:54:31PM +0200, Norbert Preining wrote:
No response from the maintainers, no action, raising the priority.
that is happening again and again, although it never happened in all
the many years I am using Debian before. Now it
is getting a pain, esp when you are
13 matches
Mail list logo
