alanr@tekigm2.MEN.TEK.COM (Alan N Rovner) (07/25/90)
I am trying to upload an application to c.b.i.p but I don't think it's getting there and could use a little help. I zoo'ed my application together on my PC, and kermit'ed it to the Unix machine at work. There I ran uuencode on the zoo file which generated about a 133k uuencoded ASCII file. From there I email'ed the ASCII file to ibmbin@crdgw1.crd.ge.com as supplied by Bill Davidsen. I haven't seen anything show up on c.b.i.p. after about 3 weeks which brings up another question. What is the typical lag time from when an application is posted to c.b.i.p until it shows up on the net? I realize that Bill does this as a "hobby" and it may take awhile. (None of these comments are intended to be a flame at Bill). Is the 133k file too large to email? If so, what utility do I use to split it? Or can I just edit it myself into two smaller files? For that matter I'm not sure that plain uuencode is the right utility to use in the first place. My site (which run BSD 4.3) also has uusend in addition to other uu-type utilities. Any help from experienced c.b.i.p'ers would really be appreciated. Thanks in advance, Al Rovner Tektronix Inc. Vancouver, Wash.
davidsen@sixhub.UUCP (Wm E. Davidsen Jr) (07/25/90)
In article <9601@tekigm2.MEN.TEK.COM> alanr@tekigm2.MEN.TEK.COM (Alan N Rovner) writes: | I haven't seen anything show up on c.b.i.p. after about 3 weeks which brings | up another question. What is the typical lag time from when an application is | posted to c.b.i.p until it shows up on the net? I realize that Bill does this | as a "hobby" and it may take awhile. (None of these comments are intended to be | a flame at Bill). It takes about 3 hours a day to do everything including the virus checks. You may have noticed that we are getting 200-500k a day out now, due to increased room in my spool directory. A submission goes through three queues. The long one is the one from the time when I get it on the ibmbin machine until I'm ready to do something with it. At that point you should get a note saying it arrived and that it's not decoded yet. Depending on the format I'll be able to decode it in anywhere from five minutes to three weeks (the last for self extracting archives). After I decode it, check for viruses, and test it, I either queue it to got to sixhub, or I send it to a reviewer. I'm doing almost all my own reviews now, to catch up on the backlog from my time out. Typical time unless I send it to someone else is two days. Then it goes to sixhub, where it is put in line to be sent out by "at" some morning when my phone rates are low. That runs about a week. There you have it, the path of a submission from my mailbox to yours. I hope to get the time down to about a week total, but the submission rate is high, and some things have time value and have to go quickly. Others, like some games from Timo Salmi, are waiting for either another week of games or filler. -- bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen) sysop *IX BBS and Public Access UNIX moderator of comp.binaries.ibm.pc and 80386 mailing list "Stupidity, like virtue, is its own reward" -me
bobmon@iuvax.cs.indiana.edu (RAMontante) (07/26/90)
Common experience seems to indicate that email files should not exceed 64K or so in size --- maybe 50K if you're real conservative. Since the whole point of uuencode is to generate a pure ASCII file, you can split it up with anything that works on ASCII files --- split, vi, sed, less .... (I use either split or vi, myself.)