From: Idris S Hamid <ishamid@lamar.colostate.edu>
Subject: Re: Permission denied
Date: Wed, 19 Nov 2003 14:37:47 -0700 [thread overview]
Message-ID: <3FBBE2AB.43C0CC37@lamar.colostate.edu> (raw)
In-Reply-To: <87n0as8dgm.fsf@uga.edu>
Thnx Ed and Giuseppe 4 your help & direction.
Question: When backing up to cd is there any way to maintain write-permission upon
retransfer to hard disk? I use Nero for back-up. This is getting off-topic I
know...
Best & thnx
Idris
Ed L Cashin wrote:
> Giuseppe Bilotta <gip.bilotta@iol.it> writes:
>
> > Thursday, November 13, 2003 Idris S Hamid wrote:
> I backed up some stuff on a cd; when I transferred the files to my other
> >> computer all the file properties read "read-only", so whenever eomega tried
> >> to modify a temporary file (fls, log, etc) it was denied permission.
next prev parent reply other threads:[~2003-11-19 21:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 19:30 Idris S Hamid
2003-11-13 21:37 ` Giuseppe Bilotta
2003-11-13 22:20 ` Idris S Hamid
2003-11-13 22:58 ` Re[2]: " Giuseppe Bilotta
2003-11-19 17:39 ` Ed L Cashin
2003-11-19 21:37 ` Idris S Hamid [this message]
2003-11-20 8:59 ` Re[2]: " Giuseppe Bilotta
2003-11-20 11:49 George N. White III
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=3FBBE2AB.43C0CC37@lamar.colostate.edu \
--to=ishamid@lamar.colostate.edu \
--cc=ntg-context@ntg.nl \
/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).