From: "Igor Gueths" <igueths@yahoo.com>
To: <speakup@braille.uwo.ca>
Subject: file re-naming?
Date: Tue, 26 Feb 2002 21:00:19 -0500 [thread overview]
Message-ID: <000701c1bf32$82b737c0$02b05b18@mycomputer> (raw)
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
next reply other threads:[~ UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths [this message]
` 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
` 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='000701c1bf32$82b737c0$02b05b18@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).