From: "Igor Gueths" <igueths@yahoo.com>
To: <speakup@braille.uwo.ca>
Subject: Re: file re-naming?
Date: Thu, 28 Feb 2002 14:50:13 -0500 [thread overview]
Message-ID: <006b01c1c091$23ab3be0$01213e18@mycomputer> (raw)
In-Reply-To: <5.1.0.14.0.20020228121248.00aab3c8@janus.northatlantic.nf.ca>
Hi Ed. Does nearo actually rename linux-style filenames? Thanks for the info!
----- Original Message -----
From: Ed Barnes <ed.barnes@janus.northatlantic.nf.ca>
To: <speakup@braille.uwo.ca>
Sent: Thursday, February 28, 2002 7:14 AM
Subject: Re: file re-naming?
> Hi there, I think Nero Burning ROM conforms to the ISO 9660
> standard however I may stand corrected.
> I hope this is helpful.
> Good luck!
> Ed Barnes
>
> At 10:39 AM 28/02/2002, you wrote:
>
> > Hi You can try going into the cd project propertys and changeing the file
> >system type to the ISO standard instead of the juliet file system type.
> > Pete
> >
> >----- Original Message -----
> >From: "Igor Gueths" <igueths@yahoo.com>
> >To: <speakup@braille.uwo.ca>
> >Sent: Tuesday, February 26, 2002 9:00 PM
> >Subject: file re-naming?
> >
> >
> >Hi. I have a winblows box over here from which I am trying to copy my linux
> >kernel tar archive, and speakup. I plan to untar everything on the linux
> >box, and then try to compile speakup, my linksys net driver, among other
> >things into my 2.4.17 kernel. However, Roxio easy cd creator on the box over
> >here tries to re-name speakup-1.00.tar.gz, to speakup_1.0_tar.gz. It also
> >re-names linux-2.4.17.tar.gz, to a similar name. I believe that it is doing
> >this because it conforms to the Umsdos standard of file naming? Someone
> >please correct me if I am wrong. Does anyone know a way in which I can get
> >around this by possibly using other burning software? Because I know that
> >iso9660 let's you have multiple extensions, as is often the case with linux
> >i.e., readme.debian.gz.sign. I have considered translation tables, but in
> >talking to one of my linux friends about it, we found it a little short of
> >impractical. If anyone wants to mail me privately on their suggestions,
> >please send the message to igueths@yahoo.com. Or, you can respond on-list.
> >Either way is fine with me. Thanks in advance for your help!
> >
> >Igor
> >
> >
> >_________________________________________________________
> >Do You Yahoo!?
> >Get your free @yahoo.com address at http://mail.yahoo.com
> >
> >
> >_______________________________________________
> >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
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths
` Gregory Nowak
` Richard Villa
` Igor Gueths
` Buddy Brannan
` Igor Gueths
` Alex Snow
` Igor Gueths
` Gregory Nowak
` Alex Snow
` Richard Villa
` Igor Gueths
` Richard Villa
` Igor Gueths
` Gregory Nowak
` Richard Villa
` Pete
` Ed Barnes
` Maurice A. Mines
` Igor Gueths [this message]
` Ed Barnes
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='006b01c1c091$23ab3be0$01213e18@mycomputer' \
--to=igueths@yahoo.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).