linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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: 17 May 2000 17:04:56 +0200	[thread overview]
Message-ID: <veu2fxtdyf.fsf@lipta.cendio.se> (raw)
In-Reply-To: Steve Rossi's message of "Wed, 17 May 2000 09:05:29 -0500"


Steve Rossi <srossi@ccrl.mot.com> writes:

> Has anyone successfully compiled e2fsck for 8xx? I was able to compile
> it and run it, but it seg faults with the following output:
>
> sh-2.03# e2fsck /dev/sda2
> e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
> /dev/sda2 contains a file system with errors, check forced.
> Pass 1: Checking inodes, blocks, and sizes
> Segmentation fault

I had no problems with e2fsck on 8xx. I use the Debian Potato
sources for all packages I build for 8xx, and most of them work
just fine out of the box.

//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/

  parent reply	other threads:[~2000-05-17 15:04 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 ` Marcus Sundberg [this message]
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         ` e2fsck? Marcus Sundberg
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=veu2fxtdyf.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 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).