From: Jan Nieuwenhuizen <janneke@gnu.org>
To: linuxppc-dev@lists.linuxppc.org
Cc: dgatwood@deepspace.mklinux.org, dorland@lords.com,
hollis+@andrew.cmu.edu
Subject: Re: Floppy problems
Date: Sat, 20 Nov 1999 14:27:22 +0100 [thread overview]
Message-ID: <199911201327.OAA17266@appel.flower> (raw)
On Sat, 20 Nov 1999 David A. Gatwood writes:
> It is very weird. Again, other G3 users, does your floppy drive work?
No, mine doesn't work either. I've reported and asked several times here,
but never got replies (other than: use gdb.. duh)
See, eg,
* To: linuxppc-dev@lists.linuxppc.org
* Subject: /dev/fd0 close () hangs -- how to debug?
* From: Jan Nieuwenhuizen <janneke@gnu.org>
* Date: Tue, 16 Nov 1999 12:14:57 +0100
_________________________________________________________________
Hi,
I've never gotten my floppy drive to work under Linuxppc, it works fine
under MacOS. When accessing the floppy, it sounds ok, but the close ()
system call doesn't return. After this, the fd0 device can't be accessed
again because it's busy. The process can't be killed.
[...]
Greetings,
Jan.
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien/ | http://www.lilypond.org/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-11-20 13:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-20 13:27 Jan Nieuwenhuizen [this message]
1999-11-20 18:52 ` Floppy problems David A. Gatwood
1999-11-20 21:40 ` Jan Nieuwenhuizen
1999-11-20 21:52 ` David A. Gatwood
1999-11-20 23:22 ` Jan Nieuwenhuizen
1999-11-20 23:37 ` David A. Gatwood
1999-11-24 16:20 ` Giuliano Pochini
1999-11-24 19:41 ` Jeff Hubbach
-- strict thread matches above, loose matches on Subject: below --
1999-11-20 1:58 Eric Dorland
1999-11-20 3:20 ` Hollis R Blanchard
1999-11-20 3:45 ` David A. Gatwood
1999-11-20 5:53 ` Eric Dorland
1999-11-20 6:17 ` David A. Gatwood
1999-11-20 6:18 ` Eric Dorland
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=199911201327.OAA17266@appel.flower \
--to=janneke@gnu.org \
--cc=dgatwood@deepspace.mklinux.org \
--cc=dorland@lords.com \
--cc=hollis+@andrew.cmu.edu \
--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).