From: Kanoalani Withington <kanoa@cfht.hawaii.edu>
To: Luca Berra <bluca@comedia.it>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID backup - mtx w/ tcl
Date: Wed, 09 Oct 2002 11:54:51 -1000 [thread overview]
Message-ID: <3DA4A5AB.60205@cfht.hawaii.edu> (raw)
In-Reply-To: 20021005123036.GB28819@percy.comedia.it
Ah, pardon me.
This may be off subject for this list. I'm only replying here because
I've lost track of everyone on this thread but I think they were all
here originally.
Unfortunately I don't have them nicely packaged so they can be used
generically. I would be willing to do that if there was a need for it
but I think there are plenty of good GPL archive/backup software
packages. The only useful thing I think I have is a command line library
interface which manages, names, tracks, loads and unloads tapes from a
tape or CD/DVD library using a low level driver like mtx. It has a
simple text interface and supports device locking and time stamps on
library operations. It's what I use in all my archive/backup scripts to
interface with media libraries.
Unfortunately it also uses an SQL database but I could make a standalone
version if it would be useful to people.
I put what I have on my anonymous ftp server:
ftp.cfht.hawaii.edu:/pub/daprog/kanoa/libh.tgz
I doubt it is useful to anyone in the state it is in though it might
have some ideas that are useful and it could adapted to another
installation.
Aloha,
-Kanoa
Luca Berra wrote:
> On Fri, Oct 04, 2002 at 12:22:03PM -1000, Kanoalani Withington wrote:
>
>> Hi Alvin,
>>
>> Funny, when I searched for it on the web I didn't find anything. The
>> original was written by Leonard Zubkoff and subsequently modified by
>> Eric Lee Green. I never got it to work for me until around version
>> 1.2.15. I emailed Eric to see what's up with it but in the meantime I
>> put my latest copy of it on my anonymous ftp server:
>>
>> ftp.cfht.hawaii.edu:/pub/daprog/kanoa/mtx-1.2.16rel.tar.gz
>>
> mtx is hosted on sourceforge http://sourceforge.net/projects/mtx
> but i believe Alvin was referring to your tcl scripts
>
> L.
>
next prev parent reply other threads:[~2002-10-09 21:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 11:20 RAID backup jbradford
2002-10-03 11:26 ` Roy Sigurd Karlsbakk
2002-10-03 11:36 ` jbradford
2002-10-03 20:00 ` Kanoalani Withington
2002-10-03 23:59 ` Effrem Norwood
2002-10-04 8:00 ` Lars Marowsky-Bree
2002-10-04 10:25 ` Illtud Daniel
2002-10-04 11:12 ` jbradford
2002-10-04 11:20 ` Alvin Oga
2002-10-04 12:52 ` Alan Cox
2002-10-04 12:52 ` Mr. James W. Laferriere
2002-10-04 13:24 ` Dr. David Alan Gilbert
2002-10-04 14:07 ` Russell King
2002-10-04 17:15 ` Dr. David Alan Gilbert
2002-10-04 21:45 ` Alvin Oga
2002-10-04 14:32 ` Luca Berra
2002-10-04 15:13 ` Richard B. Johnson
2002-10-04 15:31 ` Herman Oosthuysen
2002-10-04 16:11 ` Russell King
2002-10-04 18:51 ` Herman Oosthuysen
2002-10-04 21:37 ` RAID backup - media Alvin Oga
2002-10-04 18:58 ` RAID backup Kanoalani Withington
2002-10-04 21:51 ` RAID backup - mtx w/ tcl Alvin Oga
2002-10-04 21:59 ` Effrem Norwood
2002-10-04 22:22 ` Kanoalani Withington
2002-10-05 12:30 ` Luca Berra
2002-10-09 21:54 ` Kanoalani Withington [this message]
2002-10-10 1:39 ` Alvin Oga
2002-10-03 11:27 ` RAID backup Roy Sigurd Karlsbakk
2002-10-03 13:40 ` Adam Luter
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=3DA4A5AB.60205@cfht.hawaii.edu \
--to=kanoa@cfht.hawaii.edu \
--cc=bluca@comedia.it \
--cc=linux-raid@vger.kernel.org \
/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).