From: "Bruce Ellis" <brucee@chunder.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] trace.c
Date: Wed, 28 Jan 2004 21:46:41 +1100 [thread overview]
Message-ID: <009201c3e58c$0e6b21b0$8201a8c0@cc77109e> (raw)
In-Reply-To: <b09f0f2486775560c2ec37ad9213e0bb@centurytel.net>
sorry, it's hard to get a dinosaur to write a cd,
give it all the cpu ... still no good. there are
many > 1G P3s at the local hock shop for
a few hunge..
> was trying to write a deterministic cat for copying CD audio files to
> /dev/audio on a slow machine (K6-166Mhz). Regular cat results in a
next prev parent reply other threads:[~2004-01-28 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 19:48 mirtchov
2004-01-27 19:58 ` Peter Bosch
2004-01-28 8:13 ` Skip Tavakkolian
2004-01-28 10:46 ` Bruce Ellis [this message]
2004-01-28 13:06 ` boyd, rounin
2004-01-28 13:00 ` Sape Mullender
2004-01-28 15:52 ` Rob Pike
2004-01-28 16:21 ` Sape Mullender
2004-01-29 1:48 ` Geoff Collyer
2004-01-29 1:56 ` Peter Bosch
2004-01-29 2:34 ` Geoff Collyer
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='009201c3e58c$0e6b21b0$8201a8c0@cc77109e' \
--to=brucee@chunder.com \
--cc=9fans@cse.psu.edu \
/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).