From: Marcus Sundberg <marcus@cendio.se>
To: Steve Rossi <srossi@ccrl.mot.com>
Cc: Embedded Linux PPC List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: e2fsck?
Date: 18 May 2000 10:21:01 +0200 [thread overview]
Message-ID: <ve66scmfpu.fsf@lipta.cendio.se> (raw)
In-Reply-To: Steve Rossi's message of "Wed, 17 May 2000 10:57:03 -0500"
Steve Rossi <srossi@ccrl.mot.com> writes:
> Well, that seems to be my problem too. I grabed the
> e2fs-progs-1.18 from the debian potato distribution,
> along with the debian patch.
> I'm compiling with gcc-2.95.2 (from the monta vista dev
> kit) on linuxppc on a G4 (yellowdog champion server 1.2
> distribtion). Still I get the same effect. Marcus what is
> different in your configuration?
Well, I cross-compile from an x86 machine using Debian's gcc 2.95.2,
and my kernel is different from yours. Does your kernel contain
the MMU fixes? Otherwise things will go haywire as soon as all your
RAM is used up by e2fsck.
//Marcus
--
-------------------------------+-----------------------------------
Marcus Sundberg | Phone: +46 707 452062
Embedded Systems Consultant | Email: marcus@cendio.se
Cendio Systems AB | http://www.cendio.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-18 8:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-17 14:05 e2fsck? Steve Rossi
2000-05-17 14:32 ` e2fsck? Daris Nevil
2000-05-17 14:58 ` e2fsck? Steve Rossi
2000-05-17 15:04 ` e2fsck? Marcus Sundberg
2000-05-17 15:18 ` e2fsck? Daris Nevil
2000-05-17 15:35 ` e2fsck? Marcus Sundberg
2000-05-17 15:57 ` e2fsck? Steve Rossi
2000-05-18 8:21 ` Marcus Sundberg [this message]
2000-05-18 16:15 ` e2fsck? Daris Nevil
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=ve66scmfpu.fsf@lipta.cendio.se \
--to=marcus@cendio.se \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=srossi@ccrl.mot.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.