From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: re: linking to dev cooridinates
Date: Tue, 7 May 2002 21:05:19 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0205072105001.1985-100000@igueths> (raw)
In-Reply-To: <E175FSA-0005X5-00@speech.braille.uwo.ca>
Hi Greg. I kind of figured this could be done via hardlinks. Gotta look at
the man page for ln to find the answer to that one I guess.
Gates go to hell, your OS is waiting for you there!
On Tue, 7 May 2002, Gregory Nowak wrote:
> I don't think either of those options are possible. Of course I could be wrong.
> Greg
>
>
>
> > ----- Original Message -----
>
> >From: "Igor Gueths" <igueths@attbi.com
>
> >To: <speakup@braille.uwo.ca
>
> >Date: Tue, 7 May 2002 19:34:24 -0400
>
> >Subject: linking to dev cooridinates
>
> >Hi all. Don't know if anyone has tried this with Cdrw drives, but here goes. I have not tested /dev/sr0 yet to see if I can mount the device using this file, but could I possibly create a link called cdr thatwill interface to 0,0,0? These are the coordinates that cdrecord uses to access my burner. I was thinking this just because then I could make sure that the device is going to work. Also, then put an entry in fstab, make it rw, then I can just mv stuff from the disk to Cd without using cdrecord? Is this actually possible? Thanks!
>
>
> >_______________________________________________
>
> >Speakup mailing list
>
> >Speakup@braille.uwo.ca
>
> >http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Gregory Nowak
` Igor Gueths [this message]
` Steve Holmes
-- strict thread matches above, loose matches on Subject: below --
Igor Gueths
` Cecil H. Whitley
` Igor Gueths
` Cecil H. Whitley
` Igor Gueths
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.44.0205072105001.1985-100000@igueths \
--to=igueths@attbi.com \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).