From: "doc" <talmidim@wrightplaceinc.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Linux and data storage?
Date: Sun, 26 Sep 2004 19:42:27 -0600 [thread overview]
Message-ID: <007c01c4a433$42c4af10$6400a8c0@DESKWRIGHT> (raw)
In-Reply-To: <Pine.BSF.4.61.0409262010360.21468@server2.shellworld.net>
Looking for tips on how to install rpm programs.
Doc Wright
http://wrightplaceinc.net
If we can't look at ourselves, and ask, why?
then where does the learning start?
----- Original Message -----
From: "Karen Lewellen" <klewellen@shellworld.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, September 26, 2004 6:23 PM
Subject: Linux and data storage?
Hi all,
This is an odd one, so I hope I ask it in such a way to make sense.
I do not have a Linux machine. I have been trying to get this, and
thought I had one in the he works but it seems that party either made up the
machines they were offering, or for some other reason is not coming
through.
In any case, I do use a Linux shell service extensively. I fear almost
too extensively, as you will understand in a moment.
The OS on the system i use mostly is dos, and I use nettamer to telnet to
my Linux shell.
In the workspace of my shell service i have a great deal of irreplaceable
files and programs. I eave them up here, for ease, but I just was
reminded that this may be a venerable state of affairs.
Fortunately when the server went down nothing was lost or so it seems, but
I have a serious factor to consider.
My question has two parts.
first, is there a way to move large amounts of data stored in the
workspace of a Linux shell service to another location in tact, with
relative ease, and without taking all of the data on the entire system?
second, if my machine was also a Linux one, would this kind of storage be
easy to do?
As I said before I do not have such a machine, but this has shaken me up
enough that if a full Linux or Linux/dos or Linux/windows machine would
give me some firm safe backup, I will have to start advertising for
someone to build this for me and encurl the expense.
I have too busy a professional life to do this myself, and would rather
pay someone with the skills than lose valuable time trying to re-invent the
wheel.
Thanks,
Karen
_______________________________________________
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
` doc [this message]
` 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='007c01c4a433$42c4af10$6400a8c0@DESKWRIGHT' \
--to=talmidim@wrightplaceinc.net \
--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).