Date: Sat,  2 Jan 93 04:30:11 PST
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V93 #2
To: tcp-group-digest


TCP-Group Digest            Sat,  2 Jan 93       Volume 93 : Issue    2

Today's Topics:
                            Computer Life
            Mail delayed on sr.hp.com (queue id: AA01895)
            Mail delayed on sr.hp.com (queue id: AA02554)
            Mail delayed on sr.hp.com (queue id: AA02769)
    Please add Bruce@Pixar.com (Bruce Perens, KD6OTD) to tcp-group
                      ramdrive and forward quiet

Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.

Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: Fri, 1 Jan 93 9:39:27 MST
From: Larsen Karl VAL-C 678-3145 <klarsen@curie.UCSD.EDU>
Subject: Computer Life
To: tcp-group@ucsd.edu

 Doug really said it all but as a Fido Net BBS I have some data
that is based on years of use. Computers are damaged by heat and voltage
spikes. This is due to the nature of semiconductors. And hard drives are
mechanical monsters and can fail for many reasons. 
 I recall my first North Star 10 Mbyte hard drive. It was shipped
in a wooden crate with an internal wooden crate suspended inside with
springs....I called and asked why the fancy shipping container...they
said all "overseas shipping goes that way". I pointed out that New
Mexico is in the usa still. After about 2 weeks I dropped the hard drive
from a bench-top to a cement floor. It didn't bounce. But it still works
fine. Now they ship 350 mbyte hard drives in some plastic foam and say
to control accelerations kOto below 40g's...
 I am using a 386-25 with 4 meg ram and a 350 mbyte hard drive
and it has been on for 4 years solid, save for power failures and the
occasional crash due to my stupidity. When I am home and the lightning
gets close I unplug the computers and ground the antenna's. When I am
away I don't. It has yet to have any breakdowns. 

 In my opinion it is best to cycle a new computer on and off lots
for the first month or so. After that leave it on and enjoy it. I turn
off the monitors when not in use. The Fido Net has nf*odes with xt
computers that are 6 years old and still working like new.

Happy New Year to All

------------------------------

Date: Fri, 1 Jan 93 23:36:05 -0800
From: Postmaster <postmaster@sr.hp.com>
Subject: Mail delayed on sr.hp.com (queue id: AA01895)
To: Advanced Amateur Radio Networking Group <tcp-group@UCSD.EDU>

After 3 days and 12 hours, your message to:

  tcp-group-digest@UCSD.EDU

has not yet been fully delivered for the following reason:

  Deferred: No route to host

Delivery is still pending for the following address(es):

  glenne@srlr12

Your message was received Tuesday, 29 December 1992 10:57:36 PST
by sr.hp.com.  sr.hp.com will continue to attempt to deliver
your message for an additional 11 days and 11 hours.  If it has not
been delivered by the end of that time it will be returned to you.

No further action is required by you.

Your message began as follows:
--------------------

To: tcp-group-digest@UCSD.EDU
From: Advanced Amateur Radio Networking Group <tcp-group@UCSD.EDU>
Subject: TCP-Group Digest V92 #351
Message-Id: <9212291230.AA18640@ucsd.edu>


TCP-Group Digest            Tue, 29 Dec 92       Volume 92 : Issue  351

Today's Topics:
                           FTP performance

------------------------------

Date: Fri, 1 Jan 93 23:44:32 -0800
From: Postmaster <postmaster@sr.hp.com>
Subject: Mail delayed on sr.hp.com (queue id: AA02554)
To: Advanced Amateur Radio Networking Group <tcp-group@UCSD.EDU>

After 3 days and 12 hours, your message to:

  tcp-group-digest@UCSD.EDU

has not yet been fully delivered for the following reason:

  Deferred: No route to host

Delivery is still pending for the following address(es):

  glenne@srlr12

Your message was received Tuesday, 29 December 1992 11:14:01 PST
by sr.hp.com.  sr.hp.com will continue to attempt to deliver
your message for an additional 11 days and 11 hours.  If it has not
been delivered by the end of that time it will be returned to you.

No further action is required by you.

Your message began as follows:
--------------------

To: tcp-group-digest@UCSD.EDU
From: Advanced Amateur Radio Networking Group <tcp-group@UCSD.EDU>
Subject: TCP-Group Digest V92 #350
Message-Id: <9212281230.AA25532@ucsd.edu>


TCP-Group Digest            Mon, 28 Dec 92       Volume 92 : Issue  350

Today's Topics:
                      MX in Domain.txt (2 msgs)

------------------------------

Date: Fri, 1 Jan 93 23:50:35 -0800
From: Postmaster <postmaster@sr.hp.com>
Subject: Mail delayed on sr.hp.com (queue id: AA02769)
To: Advanced Amateur Radio Networking Group <tcp-group@UCSD.EDU>

After 3 days and 12 hours, your message to:

  tcp-group-digest@UCSD.EDU

has not yet been fully delivered for the following reason:

  Deferred: No route to host

Delivery is still pending for the following address(es):

  glenne@srlr12

Your message was received Tuesday, 29 December 1992 11:23:48 PST
by sr.hp.com.  sr.hp.com will continue to attempt to deliver
your message for an additional 11 days and 11 hours.  If it has not
been delivered by the end of that time it will be returned to you.

No further action is required by you.

Your message began as follows:
--------------------

To: tcp-group-digest@UCSD.EDU
From: Advanced Amateur Radio Networking Group <tcp-group@UCSD.EDU>
Subject: TCP-Group Digest V92 #349
Message-Id: <9212271230.AA23305@ucsd.edu>


TCP-Group Digest            Sun, 27 Dec 92       Volume 92 : Issue  349

Today's Topics:
                           MX in Domain.txt

------------------------------

Date: Fri, 1 Jan 1993 21:11:49 -0800 (PST)
From: Bruce Perens <bruce@pixar.com>
Subject: Please add Bruce@Pixar.com (Bruce Perens, KD6OTD) to tcp-group
To: tcp-group@ucsd.edu

Hello,

Please add me to the tcp-group mailing list. I am:

 Bruce@Pixar.com (Bruce Perens, KD6OTD)

     Thanks!

------------------------------

Date: Sat, 2 Jan 93 01:45:34 EST
From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Subject: ramdrive and forward quiet
To: nos-bbs@hydra.carleton.ca

Jeff

 I would save everything to RAM drive that would not cause a problem in
the event of loss.

On the other hand...

 Having a large ramdrive temp directory and using a disk cache (smartdrv etc.)
really diminish the need to save any files to a ramdrive. Files that are
only read - like help files would be a good choice. Give at least 256K
to a ramdrive for /tmp - I use 512K - and everthing else 3-4 megs or more
if you have it to a disk cache. On a 386xs-25 with an st251-1 28ms drive
I have absolutely no complaints about latency in the mail. Some of the
new IDE drives (12-16ms) with built-in cache would run rings around that.
What happens when you run large disk caches with delayed write is that
the application returns long before the disk is done. It can sit there and
churn while you are doing other things. Where this really is seen is in
ftp transfers over ethernet. I can transfer a 1 megabyte file between my
system and the receiving system never even accesses the drive until after
the transfer is reported complete. It then writes the data. Since the
transfer is not interrupted by disk writes the transfer rate is very good.
Approaching 100,000 chrs/sec. A lot can be done to optimize systems. 

Doug

 

------------------------------

End of TCP-Group Digest V93 #2
******************************
******************************