From: Dan Malek <dan@netx4.com>
To: Steve Rossi <srossi@ccrl.mot.com>
Cc: Embedded Linux PPC List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: more on e2fsck
Date: Wed, 17 May 2000 18:06:48 -0400 [thread overview]
Message-ID: <392317F8.F32062C6@embeddededge.com> (raw)
In-Reply-To: 3922CB9E.873738B6@ccrl.mot.com
Steve Rossi wrote:
> when I run mke2fs /dev/sda2 it creates a file system just fine.
Oh, I'll just make a wild guess here.....SCSI disks on 8xx.....:-).
How many pieces of untested hardware (and software) are in this path?
Have you written a simple program to make sure you can read/write
sectors on the disk without errors? I, like the others, have e2fsck
working on PCMCIA "disk" devices. The sources compile just fine. I
suppose someone could compile and test something for you to verify it
works. I don't have anything handy at the moment, but I will add it
to my list.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-17 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-17 16:41 more on e2fsck Steve Rossi
2000-05-17 16:49 ` Pavel Roskin
2000-05-17 22:06 ` Dan Malek [this message]
[not found] <200005171655.SAA21603@denx.local.net>
2000-05-17 20:30 ` Steve Rossi
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=392317F8.F32062C6@embeddededge.com \
--to=dan@netx4.com \
--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).