From: "nick G" <Nick6489@andrelouis.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Linux and data storage?
Date: Mon, 27 Sep 2004 20:19:50 -0400 [thread overview]
Message-ID: <000001c4a591$a25f1dc0$cc00a8c0@nickysp4> (raw)
In-Reply-To: <Pine.BSF.4.61.0409271814370.11413@server2.shellworld.net>
It is really hard to corrupt a zip file. There are no risks involved. And
If you create a zip, you don't have to delete what is in your home directory
anyway...Or so I believe. Your welcome to correct me, go on, do it!
Thanks,
Nick
----- Original Message -----
From: "Karen Lewellen" <klewellen@shellworld.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, September 27, 2004 6:18 PM
Subject: Re: Linux and data storage?
> *we* agreed on no such thing.
> I have no intention of risking a zip of any of these files, nor do i want
> to have to create alist.
> I want a direct uninterrupted transfer of the entire contents of my home
> directory here minus the shellworld programs themselves to a directory so
> created on the ftp area of my site to so store them as a backup.
> no one said anything about ziping anything.
> Tar was s mentioned before you came in this morning yes.
>
>
> On Mon, 27 Sep 2004, Janina Sajka wrote:
>
>> I don't know how sftp would be better?
>>
>> 1.) You can specify a file mask to transfer multiple files with scp.
>>
>> 2.) You can specify multiple source files with scp, and do so in one
>> command where sftp would require you to do one at a time if you didn't
>> use a file mask.
>>
>> And, didn't we agree that the better strategy would be to tar and either
>> bun or gun zip the archive first?
>>
>> Luke Davis writes:
>>> On Mon, 27 Sep 2004, Luke Yelavich wrote:
>>>
>>>> The tools I am thinking of, are the SSH suite of tools, particularly
>>>> one
>>>> command being scp. This command allows you to copy data securely over a
>>>> network connection, by means of encryption.
>>>
>>> sftp, might be a better option, for several files.
>>>
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@braille.uwo.ca
>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>> --
>>
>> Janina Sajka, Chair
>> Accessibility Workgroup
>> Free Standards Group (FSG)
>>
>> janina@freestandards.org Phone: +1 202.494.7040
>>
>>
>> _______________________________________________
>> 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: 176+ messages / expand[flat|nested] mbox.gz Atom feed top
Using Grub with Speech Sean M McMahon
` Steve Holmes
` Janina Sajka
` Steve Holmes
` Janina Sajka
` Janina Sajka
` Linux and data storage? Karen Lewellen
` hank
` Karen Lewellen
` Chuck Hallenbeck
` Sina Bahram
` Karen Lewellen
` Sina Bahram
` Karen Lewellen
` Hart Larry
` Terry D. Cudney
` Karen Lewellen
` Terry D. Cudney
` Hart Larry
` games doc
` games Jayson Smith
` games Gregory Nowak
` Linux and data storage? Ann Parsons
[not found] ` <Pine.BSF.4.61.0409271506320.884@server2.shellworld.net>
` Linux system...dressed downfrom yesterday Karen Lewellen
` Janina Sajka
` Karen Lewellen
` Janina Sajka
` Karen Lewellen
` Janina Sajka
` Ann Parsons
` Karen Lewellen
` Gregory Nowak
` Janina Sajka
` Kenny Hitt
` Karen Lewellen
` Correction about Pine and debian; was " Cheryl Homiak
` Linux and data storage? Janina Sajka
` Sina Bahram
` Karen Lewellen
` Janina Sajka
` Sina Bahram
` doc
` Janina Sajka
` Luke Davis
` Janina Sajka
` Luke Davis
` Janina Sajka
` Luke Davis
` Janina Sajka
` Janina Sajka
` Luke Davis
` Karen Lewellen
` Luke Davis
` Karen Lewellen
` Luke Davis
` Karen Lewellen
` Luke Davis
` Karen Lewellen
` Luke Davis
` Luke Davis
` Janina Sajka
` Luke Davis
` Janina Sajka
` Karen Lewellen
` Luke Davis
` Janina Sajka
` Karen Lewellen
` Janina Sajka
` Karen Lewellen
` Sina Bahram
` Karen Lewellen
` nick G
` Sina Bahram
` Janina Sajka
` Sina Bahram
` Janina Sajka
` Sina Bahram
` Janina Sajka
` Karen Lewellen
` Janina Sajka
` Karen Lewellen
` Janina Sajka
` Sina Bahram
` Janina Sajka
` Sina Bahram
` Janina Sajka
` Sina Bahram
` Janina Sajka
` Luke Davis
` Janina Sajka
` Luke Davis
` Janina Sajka
` Luke Davis
` Karen Lewellen
` Janina Sajka
` Karen Lewellen
` Janina Sajka
` Karen Lewellen
` Janina Sajka
` Karen Lewellen
` Luke Davis
` Karen Lewellen
` Luke Yelavich
` Karen Lewellen
` Luke Davis
` Janina Sajka
` Luke Davis
` Janina Sajka
` Luke Davis
` Karen Lewellen
` Luke Davis
` Karen Lewellen
` Luke Davis
` Karen Lewellen
` Chuck Hallenbeck
` Karen Lewellen
` Luke Davis
` nick G [this message]
` doc
` Luke Davis
` Janina Sajka
` Janina Sajka
` Luke Davis
` Janina Sajka
` Karen Lewellen
` Luke Davis
` Karen Lewellen
` Janina Sajka
` Luke Davis
` Karen Lewellen
Sean M McMahon
` Karen Lewellen
` Janina Sajka
` Karen Lewellen
` Janina Sajka
Sean M McMahon
` Thomas Stivers
` Luke Davis
` Janina Sajka
` Luke Davis
Sean M McMahon
Sean M McMahon
` Karen Lewellen
` Luke Davis
` Gregory Nowak
` Luke Davis
` Hart Larry
` Karen Lewellen
` Steve Holmes
` Chuck Hallenbeck
` Karen Lewellen
` Janina Sajka
` Adam Myrow
` Chuck Hallenbeck
` Karen Lewellen
` Luke Davis
` Karen Lewellen
` Luke Davis
` Karen Lewellen
` Karen Lewellen
` Luke Davis
` Karen Lewellen
` Karen Lewellen
` Janina Sajka
` Gregory Nowak
` nick G
Sean M McMahon
` Karen Lewellen
` Gregory Nowak
Sean M McMahon
` Gregory Nowak
Sean M McMahon
` Gregory Nowak
Sean M McMahon
` Gregory Nowak
Sean M McMahon
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='000001c4a591$a25f1dc0$cc00a8c0@nickysp4' \
--to=nick6489@andrelouis.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).