From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] non-standard CD sizes
Date: Tue, 27 Mar 2001 12:49:40 -0500 [thread overview]
Message-ID: <20010327174944.B0EEA199ED@mail.cse.psu.edu> (raw)
i've got a bunch of non-standard sized CDs
(mini-CDs at ~51MB/6min, a few 800MB/80min).
they're all blanks. i've also got a IDE NEC
CD writer. the non-standard sizes don't show
up as anything in cdfs (the small ones show
up in /dev/sdD0, the big ones don't). is
this a known limitation of cdfs/#S, or a
problem with my hardware (never tried it on
any other OS)?
trying it elsewhere is obviously a good idea.
i have an unopened spindle of 800MB blanks back
at school that i'll try next week.
i don't think it's a known problem.
try doing "scuzz /dev/sdD0" and type
"rdiscinfo" (at the invisible prompt).
next reply other threads:[~2001-03-27 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-27 17:49 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-25 14:28 anothy
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=20010327174944.B0EEA199ED@mail.cse.psu.edu \
--to=rsc@plan9.bell-labs.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).