From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Guillaume Laures <guillaume.laures@noos.fr>
Cc: Tony Mantler <nicoya@apia.dhs.org>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: st corruption
Date: Sun, 25 Mar 2001 21:21:20 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.05.10103252120020.13875-100000@callisto.of.borg> (raw)
In-Reply-To: <200103251635.KAA16519@lists.linuxppc.org>
On 25 Mar 2001, Guillaume Laures wrote:
> > merida:/home/nicoya# md5sum testfile
>
> 13b37214355ea84d906a54bb14c1c0be testfile
>
> > merida:/home/nicoya# tar -c testfile >/dev/st0
> > merida:/home/nicoya# mv testfile testfile.1
> > merida:/home/nicoya# tar -x </dev/st0
> > merida:/home/nicoya# md5sum testfile
>
> 13b37214355ea84d906a54bb14c1c0be testfile
>
> uname -a :
> Linux shiner.gom.net 2.2.18-snd-bkport #26 Wed Feb 28 23:19:57 CET 2001
> ppc unknown
>
> So no prob here either with close hardware.
Thanks! Do you also have a 2.4.x kernel around?
Or perhaps I should try 2.2.18... No idea whether 2.2.18 works on LongTrail,
though. I switched to 2.3.x a long time ago...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-03-25 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 19:41 st corruption Geert Uytterhoeven
2001-03-22 23:14 ` Tony Mantler
2001-03-23 7:20 ` Geert Uytterhoeven
2001-03-23 13:22 ` Tony Mantler
2001-03-25 15:08 ` Guillaume Laures
2001-03-25 19:21 ` Geert Uytterhoeven [this message]
2001-03-25 20:08 ` Guillaume Laures
2001-03-27 18:26 ` Geert Uytterhoeven
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=Pine.LNX.4.05.10103252120020.13875-100000@callisto.of.borg \
--to=geert@linux-m68k.org \
--cc=guillaume.laures@noos.fr \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=nicoya@apia.dhs.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).