-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Guys,
A temporary workaround for the problem is to edit /etc/default/rcS file
and set FSCKFIX to yes. At least it wont stop your boot process asking
for manual fsck run.
Hopefully maintainers can put together soon to fix this.
Thanks,
Alan
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
You were right. I compiled and packaged the new upstream 2.16.1, same
issue.
About the questions:
# cat /etc/default/rcS | grep -v "#"
TMPTIME=0
SULOGIN=no
DELAYLOGIN=no
UTC=no
VERBOSE=no
FSCKFIX=no
RAMRUN=no
RAMLOCK=no
# ls /etc/rcS.d/ -l
to
On Wed, Sep 09, 2009 at 09:42:47PM -0700, Alan Baghumian wrote:
> Same issue on squeeze. Guys this becomes more and more of an issue.
> I have the same issue on my both computers and just keep one 24/7 on
> and use hibernate on the laptop! Please fix it.
> Also a new upstream version is available
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: util-linux
Version: 2.16-3
Severity: serious
Same issue on squeeze. Guys this becomes more and more of an issue.
I have the same issue on my both computers and just keep one 24/7 on
and use hibernate on the laptop! Please fix it.
Also a new
Package: util-linux
Version: 2.16-3
Severity: normal
I am having the same problem since the last upgrade (util-linux
2.15.1~rc1-1 to 2.16-3). Below is some of my system information, hope
it is of use.
The error message always says that the last write access had been
e.g. at sth. like 20:30:05 w
5 matches
Mail list logo
