linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Iain Sandoe" <iain@sandoe.co.uk>
To: linuxppc-dev@lists.linuxppc.org
Subject: Upgraded utils...
Date: Fri, 14 Jul 2000 18:30:10 +0100	[thread overview]
Message-ID: <200007141730.SAA17219@hyperion.valhalla.net> (raw)


Hi,
Since I'm working on 2.4.0-testx I upgraded modutils, e2fsprogs and
util-linux as suggested... (looking at the changes list).

Now I have the following behaviour:

on boot

"cannot access hardware clock by any known method"

on damaged boot partition --- 2.4.0-test4 crashes one in three times on
reboot :-(

generally heart-stopping behaviour from fsck saying that is cannot find
things and then dropping me into manual fsck...

Is there something else I need to upgrade? or remove?

Iain.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-07-14 17:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-14 17:30 Iain Sandoe [this message]
2000-07-14 18:54 ` Upgraded utils Martin Costabel
2000-07-14 19:06   ` Franz Sirl
2000-07-14 19:16     ` Martin Costabel
2000-07-15 15:20     ` Martin Costabel
2000-07-16 11:45       ` RTC on 2.4.0-test4 (Was Re: Upgraded utils...) Martin Costabel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200007141730.SAA17219@hyperion.valhalla.net \
    --to=iain@sandoe.co.uk \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).