Sorry theodore for that i didn't provide the information correctly. I am not
a Linux Expert :-(
On Dec 16, 2007 8:34 PM, Theodore Ts'o <email address hidden> wrote:
> Bulldog, this is due to Ubuntu having buggy init scripts, and not
> setting the time correctly before running e2fsck. For some number of
> strange reasons I haven't been able to get Ubuntu staff to deal with
> this problem correclty, so starting with e2fsprogs 1.40.3, the
> debian/rules files have been set up to work around the problem using an
> /etc/e2fsck.conf script:
>
> [options]
> buggy_init_scripts = 1
>
> --
> fsck on every (re)boot
> https://bugs.launchpad.net/bugs/63175
> You received this bug notification because you are a direct subscriber
> of the bug.
>
Sorry theodore for that i didn't provide the information correctly. I am not
a Linux Expert :-(
On Dec 16, 2007 8:34 PM, Theodore Ts'o <email address hidden> wrote:
> Bulldog, this is due to Ubuntu having buggy init scripts, and not /bugs.launchpad .net/bugs/ 63175
> setting the time correctly before running e2fsck. For some number of
> strange reasons I haven't been able to get Ubuntu staff to deal with
> this problem correclty, so starting with e2fsprogs 1.40.3, the
> debian/rules files have been set up to work around the problem using an
> /etc/e2fsck.conf script:
>
> [options]
> buggy_init_scripts = 1
>
> --
> fsck on every (re)boot
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>