amrecover
Hi, I'm having some amrecover grief. When I run it, it returns: root@gene amanda]# amrecover -C CORBETT -s gene -t gene -d /dev/nst0 AMRECOVER Version 2.4.1p1. Contacting server on gene ... amrecover: Unexpected server end of file If I leave out various bits of information (tape host, index server etc) it returns the same message. amrecover.debug looks like: [root@gene amanda]# cat amrecover.debug amrecover: debug 1 pid 8510 ruid 0 euid 0 start time Tue May 8 15:51:41 2001 [root@gene amanda]# If I browse the directories where the index is it all looks alright - I can see the config/index/hostname/devicename directories... what is amrecover looking for? The hostname matches in all cases... Thanks, Chris Herrmann Far Edge Technology p. 02 99553640 f. 02 99547994 m. 0403 393309 http://www.faredge.com.au
data encription
Title: data encription Hello All, First posting to the mailing list :-) Quick question: Does AMANDA support media encryption? Does the SECURITY-API cover this - or is it only limited to network security? Where do I go for more info or is some code hacking required? Thanks! Luke McKee [EMAIL PROTECTED] Network Administrator & Systems Support Webpay, Secure Digital Commerce Webtel Pty Ltd Ph: +61 2 9921 1234 Fax: +61 2 9923 1700
Re: Please, help me! I don`t know what to do?
ok. Thanks. Leandro Melo de Sales. CEFET/AL - Centro Federal de Educação Tecnológica de Alagoas GTI - Gerência de Tecnologia da Informação - Original Message - From: "John R. Jackson" <[EMAIL PROTECTED]> To: "Leandro Sales" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, May 07, 2001 6:30 PM Subject: Re: Please, help me! I don`t know what to do? > >amanda dgram udp tcp wait amanda /usr/lib/amanda/amandad amandad > > Why did you list both udp and tcp? It should just say udp: > > amanda dgram udp wait amanda /usr/lib/amanda/amandad amandad > > >Leandro. > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
host mozart.cefet-al.br: port 1038 not secure
Hi... I evoluted about the configuration of AMANDA, but now, the following message was shown: $ amcheck completo Amanda Tape Server Host Check - ... ... ... Amanda Backup Client Hosts Check ERROR: mozart: [host mozart.mydomain.com: port 1038 not secure] Client check: 1 host checked in 0.021 seconds, 1 problem found. (brought to you by Amanda 2.4.1p1) where mydomain is the domain of my network, I prefer not to especify it! What I need to do to fix it? thanks.. Leandro. Leandro Melo de Sales. CEFET/AL - Centro Federal de Educação Tecnológica de Alagoas GTI - Gerência de Tecnologia da Informação
Re: another problem from upgrading server to 2.4.2p2
>Isn't "/usr/bin/mail" usally lowercase? It depends on the OS. I have both (on Solaris). The lower case version does not support the -s (Subject) option. The capitalized one (a.k.a. mailx), does. But that has nothing to do with why the input file was missing. >Joi Ellis John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amanda trying to access slots beyond amanda.conf settings...
On Mon, 7 May 2001, John R. Jackson wrote: > >I am using the 'stctl' package to interface between the various Amanda > >applications and the autochanger robotics. > > Huh? What is tpchanger set to in amanda.conf? What are the in changer > configuration files? Ok, 'tpchanger' is set to 'stc-changer', which is a small script that's part of Eric Berggren's 'stctl' Solaris Tape-Changer Control package available from "http://www.cs.pdx.edu/~eric/stctl";. It doesn't used a changer config file as such. I've put the 'stc-changer' script in the appropriate place for tape changer scripts and edited the small configuration section at the top of the script to suit my setup. > >dumpcycle 4 weeks ... > >runspercycle 20 ... > >tapecycle 10 tapes ... > > This is a very bad combination. How do you expect to fit 20 runs on > 10 tapes? 8-) Good point. I guess it makes more sense to set 'tapecycle' and 'runspercycle' both to 10. I was just picking some numbers which seemed ok at the time. > >As you can see, 'tapecycle' it set to 10. ... > > Which is irrelevant to the changer. It does not care about tapecycle. > More interesting would be runtapes, but I doubt even that matters. I've got that set to 1 (so it only uses one tape per 'amdump' run). Regards, Craig. -- Craig Dewick. Send email to "[EMAIL PROTECTED]" Point your web client at "www.sunshack.org" or "www.sunshack.net" to access my archive of Sun technical information and links to other places. For info about Sun Ripened Kernels, go to "www.sunrk.com.au" or "www.sun-surplus.com"
Re: another problem from upgrading server to 2.4.2p2
On Mon, 7 May 2001, John R. Jackson wrote: >Date: Mon, 07 May 2001 17:28:33 -0500 >From: John R. Jackson <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: Paolo Supino <[EMAIL PROTECTED]> >Cc: [EMAIL PROTECTED] >Subject: Re: another problem from upgrading server to 2.4.2p2 > >> Yesterday, the daily amcheck run gave me the following error: >>sh: /tmp/amanda/amcheck.main.16130: No such file or directory >>amcheck: mail command failed: /usr/bin/Mail -s " AMANDA PROBLEM: FIX > Isn't "/usr/bin/mail" usally lowercase? -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: amanda trying to access slots beyond amanda.conf settings...
>I am using the 'stctl' package to interface between the various Amanda >applications and the autochanger robotics. Huh? What is tpchanger set to in amanda.conf? What are the in changer configuration files? >dumpcycle 4 weeks ... >runspercycle 20 ... >tapecycle 10 tapes ... This is a very bad combination. How do you expect to fit 20 runs on 10 tapes? >As you can see, 'tapecycle' it set to 10. ... Which is irrelevant to the changer. It does not care about tapecycle. More interesting would be runtapes, but I doubt even that matters. >Craig. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: another problem from upgrading server to 2.4.2p2
> Yesterday, the daily amcheck run gave me the following error: >sh: /tmp/amanda/amcheck.main.16130: No such file or directory >amcheck: mail command failed: /usr/bin/Mail -s " AMANDA PROBLEM: FIX >BEFORE >RUN, IF POSSIBLE" amanda < /tmp/amanda/amcheck.main.16130 > >Why is it looking for this specific file? Amcheck writes the E-mail report to this temp file and then runs a mail program to send it. I don't know why they file does not exist. Some possibilities are: * The permissions or ownership of /tmp/amanda are wrong. You just remove the whole directory and let Amanda re-create it. * You have some kind of cleanup process running that removes files in /tmp. > Paolo John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Large partition not backing up
>... the backup of my file server parition >is failing with a rather uninformative error message: > >ironwood /mnt/files lev 0 FAILED [dump to tape failed] There should have been other messages besides this one, perhaps at the top of the report or in the NOTES section. >... I exclude a number of directories because >they are backed up with my Macintosh backup program and sendsize >calculates a size of 15Gb to be backed up. The file server partition also >holds the amanda holding disk directory. ... If you're trying to back up the file system that has the holding disk area, you should use "holdingdisk no" in the dumptype to force it to go direct to tape. You can either create a new dumptype with this option but inheriting everything else from the "normal" one, or you can add it to the disklist directly (see the "DISKLIST FILE" section of the amanda.conf man page for the details). >At one point, there seemed to be an option to have a negative chunksize, >whereby amanda would write directly to tape if a chunk was larger than >that chunksize. ... Yeah, I miss that, too. Not sure why someone removed it. >Kevin John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: missing files
>In a test, i removed the --listed-incremental /usr/amanda_0.new >option, and tar archived all my files, just how i like it. Why does >Amanda put that option there? ... Ummm, because that's required to do incremental backups. :-) >And is it feasible/desirable to make it go >away for at least level 0 backups? Only if you don't want to do incrementals (in other words, no). For full dumps, as I recall, Amanda creates an empty file and gives that to gtar with --listed-incremental. You might try something like this: cp /dev/null /tmp/my-li-file gtar ... --listed-incremental /tmp/my-li-file ... and see what you get. >Another question: Why doesn't that /usr/...amanda_0.new file exist? I >have only a >/usr/local/var/amanda/gnutar-lists/dellmachine_home_amanda_0 file, with >contents 989184075 >773 374412 ./.xauth). It probably did exist at the time Amanda ran. The ".new" in the name is a clue that Amanda is using that name and if everything goes right, it is renamed to the "real" name (without the ".new"). Based on what you've posted above, you were trying to back up something called /home/amanda, right? Is that an actual home directory? It looks like it is based on the listed incremental file which only lists one item, .xauth, and that's the kind of thing I'd expect to see inside a home directory. >george John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: tape size
>I presume "Tape Size" means amount of tape used, rather than size of >the whole tape. ... Correct. >I am having 5 out of 23 partitions fail to get to tape and 4 of those 5 >complain about lack of tape (log.20010505.0): > >FAIL taper zhongsgi /home/data 0 [out of tape] >FAIL dumper zhongsgi /home/data 0 ["data write: Broken pipe"] There should be more messages than just these. For instance, at the very top: *** A TAPE ERROR OCCURRED: [[writing file: short write]]. Or in the NOTES: section: taper: tape 041475/lookout kb 38869024 fm 1 writing file: short write (these are just examples from my own system). >It seems like I should be getting nowhere near the end of the tape >with any of these partitions. Amanda is an amazingly simple program in many ways. Writing to tape is one of them. It writes until the OS returns an error code. So you need to find the message Amanda reported about why it stopped writing to tape, then figure out why the OS told it that. The tapetype is irrelevant. That only gives Amanda a hint about how much tape it will have to work with so it can do the planning steps. It is not used at all once the actual writing starts. Assuming you don't have some switches on the drive in the wrong position (e.g. if it supports multiple densities), or you're not doing something like writing compressed data to the drive with hardware compression also turned on, then I'd guess it could be something like the drive needs to be cleaned, or the tapes need to be retensioned (if that applies to your hardware), or the drive is kicking in auto-cleaning in the middle of a session, or there may be some kind of SCSI problem that's reporting an error under some circumstances, which could be bad termination, too much termination, not enough termination, bad cable, bad connector seating, bad controller, etc. >-ken rich John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Help with configuring Amanda
>I'm new to Amanda ... Welcome! >... and would like any help with the initial setup such as the >config files, etc. Please provide any info you have on the matter. Thanks Have you read docs/INSTALL that comes with Amanda? How about the FAQ at www.amanda.org? And there's also an online chapter about Amanda from a book about backups: www.backupcentral.com/amanda.html Aside from that, you should probably post specific questions. They are a whole lot easier to answer than requests for general help. >--Anthony. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Please, help me! I don`t know what to do?
>amanda dgram udp tcp wait amanda /usr/lib/amanda/amandad amandad Why did you list both udp and tcp? It should just say udp: amanda dgram udp wait amanda /usr/lib/amanda/amandad amandad >Leandro. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Please, help me! I don`t know what to do?
I tried to see all the possibilities that could be happen. I checked my /etc/services and all these line are present in the file, but when I saw my log file message, I found the following messages: May 7 14:04:16 mozart inetd[28990]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[28991]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[28992]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[28993]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[28994]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29004]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29003]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29002]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29001]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29000]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[28999]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[28998]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[28997]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[28996]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[28995]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29005]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29006]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29007]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29008]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29016]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29015]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29014]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29013]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29012]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29011]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29010]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29009]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29017]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29018]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29019]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29020]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29024]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[28651]: amanda/udp server failing (looping), service terminated May 7 14:04:16 mozart inetd[29023]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29022]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29021]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29025]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29026]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29027]: getpwnam: wait: No such user May 7 14:04:16 mozart inetd[29028]: getpwnam: wait: No such user I don't know what is happen, but I think that there is something wrong in my /etc/inetd.conf. If someone can help me, I thank! the part that define the amanda configuration in the file inetd.conf is: #Amanda Configuration amanda dgram udp tcp wait amanda /usr/lib/amanda/amandad amandad amandaidx stream tcp nowait amanda /usr/lib/amanda/amindexd amindexd amidxtape stream tcp nowait amanda /usr/lib/amanda/amidxtaped amidxtaped Are there something wrong? Leandro. - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, May 07, 2001 4:48 AM Subject: RE: Please, help me! I don`t know what to do? > Hi Leandro, > > did you described your services in /etc/services? > > ... > # services for amanda backup software > # > amanda 10080/udp > amandaidx 10082/tcp > amidxtape 10083/tcp > ... > > bye mike >
Help with configuring Amanda
Title: Help with configuring Amanda I'm new to Amanda and would like any help with the initial setup such as the config files, etc. Please provide any info you have on the matter. Thanks --Anthony.
Re: Amrecover failure.
> [root@ /root]# amrecover -C Normal > AMRECOVER Version 2.4.2p1. Contacting server on ... > 220 AMANDA index server (2.4.2p1) ready. > 500 Access not allowed: [access as amanda not allowed from root@] > amandahostsauth failed > [root@ /root]# In my ".amandahosts" file, I added the following line to make it possible for the "root" user to run "amrecover", thus connecting to the tape/index server : from_machine1.allow.com root from_machine2.allow.com root ... These lines come after the authorization line for the amanda user itself, "bin", in my case. e.g: from_machine1.allow.com bin ... I guess that it doesn't raise any security matter, provided that the machine names are written as full qualified domain name, and that amandahosts authentication is used , and last, that amanda inetd services are tcp-wrapped. Pierre.
Amrecover failure.
Hello, I was wondering if anyone had ran into any troubles with amrecover before. I can backup files fine but when I try to run amrecover, then it says that amanda access is not allowed. It seems like if amanda wasn't allowed then I wouldn't be able to backup the files on the server. [root@ /root]# amrecover -C Normal AMRECOVER Version 2.4.2p1. Contacting server on ... 220 AMANDA index server (2.4.2p1) ready. 500 Access not allowed: [access as amanda not allowed from root@] amandahostsauth failed [root@ /root]# Amanda server= Redhat6.2 with version 2.4.2p1. (I have it running through xinetd and when I check the logs, it connects just fine.) Clients are the server itself and another Redhat6.2 box. I get the same message when I try to run amrecover and the server on the client. Any help would be greatly appreciated. Frank J Miles System Administrator Physics and Astronomy Dept. Western KY University [EMAIL PROTECTED] 270-745-8836
Re: holding space estimates
FYI, I have run into this problem as well. In my case it was when my "holding disk" was actually just a subdirectory. It just so happened to be on the same partition as /tmp. So even though nothing else of significance was running, Amanda was getting into a fight with herself. "John R. Jackson" wrote: > > >Ideally amanda should look every time a chunk is written to disk how much > >space ios free ... > > That's probably a good idea. I've added it to the TODO list. > > >Gerhard den Hollander > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- Tom Schutter (mailto:[EMAIL PROTECTED]) Platte River Associates, Inc. (http://www.platte.com)
tape size
In "AMANDA Backup AMANDA MAIL REPORT FOR May 5":
Tape Size (meg) 5378.5 5378.50.0
Tape Used (%) 22.9 22.90.0
I presume "Tape Size" means amount of tape used, rather than size of
the whole tape. In amanda.conf I have:
define tapetype AIT1-25 {
comment "AIT-1 cartridge 25/50 GB"
length 23500 mbytes # lowest number seen so far, rounded down
filemark 500 kbytes
speed 3000 mbytes
}
I am having 5 out of 23 partitions fail to get to tape and 4 of those 5
complain about lack of tape (log.20010505.0):
FAIL taper zhongsgi /home/data 0 [out of tape]
FAIL dumper zhongsgi /home/data 0 ["data write: Broken pipe"]
It seems like I should be getting nowhere near the end of the tape
with any of these partitions.
--
-ken rich // [EMAIL PROTECTED]
Re: missing files
"John R. Jackson" wrote: > > >Is the actual (eg, tar) command used by amdump recorded? Where? > > /tmp/amanda/sendsize*debug and /tmp/amanda/sendbackup*debug on the client. > > > george Thanks. I didn't know that because the sendsize*debug files i looked inside didn't have the tar options because amdump wasn't getting that far. So here's the tar command amanda used: sendsize: argument list: /bin/gtar --create --file /dev/null --directory /home/amanda --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/dellmachine_home_amanda_0.new --sparse --ignore-failed-read --totals . In a test, i removed the --listed-incremental /usr/amanda_0.new option, and tar archived all my files, just how i like it. Why does Amanda put that option there? And is it feasible/desirable to make it go away for at least level 0 backups? Another question: Why doesn't that /usr/...amanda_0.new file exist? I have only a /usr/local/var/amanda/gnutar-lists/dellmachine_home_amanda_0 file, with contents 989184075 773 374412 ./.xauth). thank u, george
Large partition not backing up
Hi, Using amanda-2.4.2p2 (but this was happening with earlier versions as well) on a Red Hat Linux 6.2 server, the backup of my file server parition is failing with a rather uninformative error message: ironwood /mnt/files lev 0 FAILED [dump to tape failed] I don't see anything in the logs that indicate why its failed, although I will offer my suspicions. The partition being backed up is a 38Gb partition and has 30Gb in use. I exclude a number of directories because they are backed up with my Macintosh backup program and sendsize calculates a size of 15Gb to be backed up. The file server partition also holds the amanda holding disk directory. What I am theorizing is that there is not enough space on the dump disk to dump the entire parition at once and hence it fails. In my amanda.conf I have: comment "main holding disk" directory "/mnt/files/amanda/dumps" use -200 Mb chunksize 1Gb At one point, there seemed to be an option to have a negative chunksize, whereby amanda would write directly to tape if a chunk was larger than that chunksize. That would have solved my problem but that solution is gone now. Was something else implimented for situations like this? Thanks, Kevin -- Kevin M. Myer Systems Administrator Lancaster-Lebanon Intermediate Unit 13 (717)-560-6140
another problem from upgrading server to 2.4.2p2
Hi Yesterday, the daily amcheck run gave me the following error: sh: /tmp/amanda/amcheck.main.16130: No such file or directory amcheck: mail command failed: /usr/bin/Mail -s " AMANDA PROBLEM: FIX BEFORE RUN, IF POSSIBLE" amanda < /tmp/amanda/amcheck.main.16130 Why is it looking for this specific file? Paolo
RE: Please, help me! I don`t know what to do?
Hi Leandro, did you described your services in /etc/services? ... # services for amanda backup software # amanda 10080/udp amandaidx 10082/tcp amidxtape 10083/tcp ... bye mike
amanda trying to access slots beyond amanda.conf settings...
Hi, I've just come across a strange problem. I'm using an ADIC 1200D DAT autochanger, and I have data tapes in the first 10 slots of the 12-slot magazine, with the 11th empty (because I don't have any more data tapes!), and the 12th slot contains a cleaning tape. I am using the 'stctl' package to interface between the various Amanda applications and the autochanger robotics. The problem is that even though I have amanda.conf set up so that it thinks there are only 10 tapes being used, it's still trying to access slots beyond the 10th when running the 'amcheck' scans... This is the section of amanda.conf which is relevant: org "ORBnet"# your organization name for reports mailto "craig netstat@jedi" # space separated list of operators at your site dumpuser "amanda" # the user to run dumps under inparallel 4# maximum dumpers that will run in parallel (max 63) # this maximum can be increased at compile-time, # modifying MAX_DUMPERS in server-src/driverio.h netusage 600 Kbps # maximum net bandwidth for Amanda, in KB per sec dumpcycle 4 weeks # the number of days in the normal dump cycle runspercycle 20 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 10 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that # need amflush and so we do not overwrite the full # backups performed at the beginning of the previous # cycle As you can see, 'tapecycle' it set to 10. So I'm wondering if this is highlighting an oversight with the code which talks to the autochanger device in that it's seeing that there are more slots than tapes, and ignoring the setting of 'tapecycle'. 'amcheck' is coming back with this error message: Amanda Tape Server Host Check - Holding disk /amanda/tmp: 1878008 KB disk space available, using 1615864 KB amcheck-server: slot -1: Can't determine current tape; drive empty ? amcheck-server: slot -1: No subsequent volume available amcheck-server: slot -1: No subsequent volume available amcheck-server: slot -1: No subsequent volume available amcheck-server: slot -1: No subsequent volume available amcheck-server: slot -1: No subsequent volume available amcheck-server: slot -1: No subsequent volume available amcheck-server: slot -1: No subsequent volume available amcheck-server: slot -1: No subsequent volume available amcheck-server: slot -1: No subsequent volume available amcheck-server: slot -1: No subsequent volume available amcheck-server: slot -1: No subsequent volume available ERROR: new tape not found in rack (expecting a new tape) NOTE: skipping tape-writable test Server check took 2755.973 seconds I'm currently using v2.4.2p1 of Amanda, btw. This machine is a Sun Sparc 20 running Solaris 8, using the 'stctl' package to handle low-level autochanger communication. Is there anything I should check? Is this a known problem that's fixed in 2.4.2p2 or a later (as yet unofficially released) beta version of the package? Regards, Craig. -- Craig Dewick. Send email to "[EMAIL PROTECTED]" Point your web client at "www.sunshack.org" or "www.sunshack.net" to access my archive of Sun technical information and links to other places. For info about Sun Ripened Kernels, go to "www.sunrk.com.au" or "www.sun-surplus.com"
