From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: DVD-cd usage
Date: Fri, 22 Jul 2005 17:50:05 +0000 (UTC) [thread overview]
Message-ID: <loom.20050722T194450-362@post.gmane.org> (raw)
In-Reply-To: 001201c58e1b$066a2d10$5f01010a@jnetlab.lcl
Dave Nebinger <dnebinger <at> joat.com> writes:
> > cdrecord -dao dev=ATAPI:0,0,0 -eject speed=2 -pad -data -v README
> Success, at least for what you were asking it to do, and that is to write a
> file named README onto a disk. Never mind that the disk doesn't have a
> filesystem and the README file is just a file and not a filesystem, just
> write it to the disk.
> Which it looks like it did just that.
> You've now got yourself a perfectly usable dring coaster to place beside
> your monitor as that's all it's really good for at this point.
> Sarcasm aside, you really should have built an iso-based filesystem with
> README on it, then burn the resulting file to the disk. The man page for
> cdrecord has the details from building mkisofs followed by cdrecord.
Well, sarcasm is fine (I deserve it). However, you have helped me uncover
a simple but profound problem. The system where I'm working on the cd-rw,
does not have a man page for cdrecord. It has the exact same USE flags
as that another system (including 'doc') has that does have the man page for
cdrecord. I thought that if the USE flag 'doc' was in /etc/make.conf, then
all man pages get installed????
So, pretty lame, but that's why I missed the cdrecord man page. I did not
think there was one...
Any ideas how to get ALL of the man pages possible to all of the installed
software on a gentoo system?
James
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-22 17:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 17:11 [gentoo-user] DVD-cd usage James
2005-07-18 17:25 ` Daniel da Veiga
2005-07-18 18:57 ` [gentoo-user] " James
2005-07-18 19:37 ` Daniel da Veiga
2005-07-18 20:36 ` James
2005-07-18 21:09 ` Daniel da Veiga
2005-07-18 21:22 ` James
2005-07-18 21:22 ` Nick Rout
2005-07-18 22:01 ` James
2005-07-18 22:28 ` Nick Rout
2005-07-18 23:03 ` James
2005-07-18 23:32 ` Nick Rout
2005-07-18 23:54 ` James
2005-07-19 0:02 ` Nick Rout
2005-07-19 0:47 ` James
2005-07-19 1:25 ` Holly Bostick
2005-07-19 19:51 ` James
2005-07-19 20:44 ` Holly Bostick
2005-07-20 5:38 ` Rumen Yotov
2005-07-20 18:40 ` James
2005-07-21 4:25 ` Zac Medico
2005-07-21 16:38 ` James
2005-07-21 12:26 ` James Hiscock
2005-07-21 16:42 ` James
2005-07-21 17:40 ` Rumen Yotov
2005-07-19 0:07 ` James
2005-07-21 17:23 ` James
2005-07-21 17:38 ` Dave Nebinger
2005-07-22 17:50 ` James [this message]
2005-07-22 18:20 ` Dave Nebinger
2005-07-23 0:32 ` Bob Sanders
2005-07-21 17:58 ` Holly Bostick
2005-07-22 18:13 ` James
2005-07-23 6:13 ` Walter Dnes
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=loom.20050722T194450-362@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.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