Sun-Spots-Request@RICE.EDU (William LeFebvre) (07/12/88)
SUN-SPOTS DIGEST Monday, 11 July 1988 Volume 6 : Issue 135 Today's Topics: Re: QIC-24 cartridge tape and dump command Gotcha with SunOS 4.0 ftp malloc() - free() problems Help with ZS pseudo-drivers SunOs 4.0 installation question PS to LaserJet and rasterfile to Laserjet Translators Database on optical laser disk? Fonts? BIG FONTS? ONC Solution Guide questionaire Send contributions to: sun-spots@rice.edu Send subscription add/delete requests to: sun-spots-request@rice.edu Bitnet readers can subscribe directly with the CMS command: TELL LISTSERV AT RICE SUBSCRIBE SUNSPOTS My Full Name Recent backissues are available via anonymous FTP from "titan.rice.edu". For volume X, issue Y, "get sun-spots/vXnY". They are also accessible through the archive server: mail the request "send sun-spots vXnY" to "archive-server@rice.edu" or mail the word "help" to the same address for more information. ---------------------------------------------------------------------- Date: Thu, 30 Jun 88 18:06:09 -0400 From: dan@wilma.bbn.com Subject: Re: QIC-24 cartridge tape and dump command In our group we use the following options to dump onto a 450-foot cartridge using the QIC-24 format: dump cbfs 126 /dev/rst8 3820 <filesystems>... plus whatever other options (incremental dump level, etc.) you may want. The reasons for each option are as follows. You must specify "c" (cartridge) so that dump uses the appropriate values for density (1000 bytes/inch -- same for QIC-11 and QIC-24) and inter-record gap. The "b" (blocking) option forces each write to the tape to be very large, making much more efficient use of the tape. The "s" (size) option is needed because the "c" option assumes you're using QIC-11 (rst0), which only puts 4 tracks on the tape, as opposed to the 9 tracks QIC-24 puts on it. The interpretation of the "s" option doesn't understand about multiple serial tracks, so you have to take the length of your tape in feet and multiply it by 9, subtracting some amount for slop. (Even with /dev/rst0, if you are using any size other than 450-foot tapes you should specify the size to dump. Multiply the length of your tape by 4 and subtract some slop. The default "s" value for cartridge tapes is 1700, which is a "slop" of 5.5% of the tape.) If you ever do need to specify the "d" option, note that it is in bytes/inch, not bits/inch (despite the comment in dumpmain.c). With 1/2" reels of tape, each byte is recorded vertically, so it makes no difference, but with cartridges, each byte is recorded serially. QIC-24 (and probably QIC-11) assume that your tape can handle 10,000 flux transitions per inch. All the tapes we have around here are rated to that. You can get a copy of any QIC "standard" from Freeman Associates 311 E. Carillo St. Santa Barbara, Ca 93101 805-963-3853 There is no charge. Despite having a copy of the standard, I am still not sure I understand everything about writing to cartridge tapes. In particular, I don't know how to figure out how big the gap is between each block of data resulting from successive write() calls when you're writing too slowly to stream continuously, as with dump. The drive does sound like it backs up to get near the end of the previous write. However, I can't find anything in the standard implying that each write has to be located no more than a certain distance from the previous one. This means I don't know how to figure out how much slop is really needed in the "s" calculation. (The standard does discuss inter-record gaps, but seems to be talking about the gap between each of the many tiny 512-byte blocks a single write() call is split into.) All I can say is that the number above works. Dan Franklin ------------------------------ Date: Thu, 23 Jun 88 17:52:02 CST From: Simon Hackett <munnari!sirius.ua.oz.au!simon@uunet.uu.net> Subject: Gotcha with SunOS 4.0 ftp Don't know if this has already been mentioned, but here is an important "gotcha" with inward connection to SunOS 4.0 ftp, for sites which use unusual login shells. As of SunOS 4.0, the shell used by the user you want on the SunOS 4.0 machine is validated against the list supplied by "getusershell" (see the manual pages on ftpd and getusershell). Hence, if you want to be able to ftp to usernames running shells other than /bin/sh or /bin/csh (like our site, where everyone except root uses /bin/tcsh), you need to create /etc/shells and put something like the following into it: /bin/sh /bin/csh /bin/tcsh Hope this helps someone out. This stumped us for a while. Reading the manual pages is quite enlightening at times. At other times, of course, it's no use at all... Simon Hackett, Systems Group, University of Adelaide, South Australia VMS: IN%"simon@sirius.ua.oz" ACSNET,CSNET,BITNET: simon@sirius.ua.oz ARPA: simon%sirius.ua.oz@seismo.css.gov USENET: ...!<backbone>!munnari!sirius.ua.oz!simon ------------------------------ Date: 29 Jun 88 15:21:20 GMT From: unido!bilbo.irb!tb@uunet.uu.net (Torsten Beyer) Subject: malloc() - free() problems Hi everybody, I recently ran into a problem with malloc() and free() on our 3/260 running SunOS 3.4.2. Probably I'm doing something wrong. Perhaps anyone could help me. The problem is as follows : I have a little c-program which malloc()s 10 Mb, free()s these 10Mb, malloc()s another 10Mb and then waits for a key to be hit. If I do a ps aux on another terminal at this stage, ps tells me that my program has allocated 20 Mb of virtual storage. When I run the same program on a uVax running Ultrix 2.0 ps tells me I that my program has allocated ~16 Mb of RAM. This too sounds to much for me. But 20Mb on a sun definitely IS to much. To my opinion after the second malloc() there should be 10 Mb allocated. Am I wrong or is my OS wrong ?? Thanx for any hints -Torsten Torsten Beyer e-mail : tb@unido.uucp University of Dortmund ..uunet!unido!tb IRB tb@unido.bitnet P.O.Box 500500 D-4600 Dortmund 50 voice : +49 231 7552422 West-Germany ------------------------------ Date: Wed, 29 Jun 88 17:18:17 EDT From: dae@shire.cs.psu.edu Subject: Help with ZS pseudo-drivers Work-Phone: +1 814 865 9505 Home-Phone: +1 814 862 4811 I have to write a device driver for the Zilog UART on our Sun-4. I don't have the time right now to learn how to write a streams driver (my object is to get this working somewhere--it would be nice to support this code on Suns, but I have other options), so I'm trying to do this as a zs pseudo-driver under 3.2. I've wasn't able to find any documentation on these beasts, so I tried contacting Sun for help. My first request to hotline@sun.com was answered by "Please state your name, address, and serial number." I did so, and heard nothing. A week later, I sent a follow-up message. It's not quite another week and I've heard nothing yet. Anyway, is there anybody out there who can help me? I've got something that looks like it mostly works, but there's an interrupt the Zilog documentation says I should get that I don't seem to be, and I'm not sure where the problem is (Zilog, zs code, or me). Thanks to anyone who can help. --Daemon ------------------------------ Date: Thu, 30 Jun 88 10:21:53 EDT From: Ned Danieley <ndd@sunbar.mc.duke.edu> Subject: SunOs 4.0 installation question As long as we are discussing the installation of 4.0, I was wondering if they've fixed a problem I've had with previous releases? I've never been able to get setup to let me specify an Internet address that was less than 192.*. Since our addresses are 128.109.148.*, that's always been a real pain. Has this been fixed in 4.0? Or am I the only one who's had the problem? Ned Danieley (ndd@sunbar.mc.duke.edu) Basic Arrhythmia Laboratory Box 3140, Duke University Medical Center Durham, NC 27710 (919) 684-6807 or 684-6942 ------------------------------ Date: Thu, 30 Jun 88 07:40:47 ]Io From: Tom Doong <doong@eneevax.umd.edu> Subject: PS to LaserJet and rasterfile to Laserjet Translators Does anyone out there have a working PostScript to HP LaserJet and rasterfile to LaserJet translator for the SUN 3/xxx line of machines? I got the file lj-filters.shar from titan.rice.edu, but it does strange things to my machine, (like continually sending my print file to the printer until I lprm the file from the queue and turn off the printer). You can send replies directly to me: doong@eneevax.umd.edu or doong@reston.unisys.com Thanks in advance for the help. ------------------------------ Date: 30 Jun 88 09:12:51 GMT From: mcvax!pe!fk@uunet.uu.net (Flemming Korslund) Subject: Database on optical laser disk? Does anyone have experience with databases on Optical Laser Disks ('Write Once Read Many' -type) ? Does anyone have experience with choice in hardware (especially the Laser Disk System) or in software? I need up to 6 Gbytes disk space for scanned images. Any suggestions will be appreciated, thanks in advance. Flemming Korslund Purup Electronics a/s Email: fk@pe.dk Soenderskovvej 5 UUCP : ...!mcvax!diku!dkuug!pe!fk 8520 Lystrup Denmark Phone: +45 622 2522 ------------------------------ Date: Wed, 29 Jun 88 09:35:38 -0400 From: mesard@bbn.com Subject: Fonts? BIG FONTS? Phone: 617-873-1878 Does anyone have any vfont format (i.e., SunView-type) fonts that I could get my hands on? Especially large ones. I have the usual array of "screen" [7-14] and "cour" [10-24], and a few others, but we'll be giving a demo to the National Academy of Nearsighted Administrators (N.A.N.A. :-) soon, and it would be awful nice if they could read what's on the screen without having to crawl inside it. wnl, Are there any interesting fonts in the archives? (I didn't see any, but may not have looked in all the right places.) [[ A few applications come with some fonts, but there are no "unbundled" fonts (if I may borrow that term) in the archives. --wnl ]] Any info appreciated. unsigned *Wayne_Mesard(); MESARD@BBN.COM BBN Labs, Cambridge, MA ------------------------------ Date: Wed, 29 Jun 88 19:46:18 PDT From: marsal@sun.com (Jack Marsal) Subject: ONC Solution Guide questionaire As the following cover letter indicates, I am looking for input from the UNIX community regarding implementations of ONC/NFS or applications that use RPC....Also, as they say in the publishing business, "time is of the essence". We need to get the responses by July 29 to go to press on time. Thanks very much!! Jack Marsal Sun Microsystems Software Licensing **************************************************************** June 29, 1988 Dear ONC/NFS Supporter, The ONC/NFS Technology Group of Sun Microsystems is planning to publish an Open Network Computing (ONC) Solution Guide. It will list available implementations of ONC/NFS. The ONC Solution Guide is intended to be useful to companies that have a heterogeneous computing environment. If you have developed an ONC/NFS implementation from the public domain specification, or if you have developed RPC-based applications, we would like to have your input to the ONC Solution Guide. The ONC Solution Guide will be divided into two sections: 1) ONC/NFS implementations, and 2) RPC-based applications. Each ONC/NFS implementation and each application will be described in approximately 1/4 page. We also envision a matrix chart showing which ONC services are available on each operating system. A copy of the ONC Solution Guide will be sent to all contri- butors. We encourage contributors to share the information in the ONC Solution Guide with customers and colleagues. We plan to update the information in the ONC Solution Guide every 6 months. To contribute to the ONC Solution Guide, please fill out the following questionnaire and return it to Sun (see the address below) by July 29, 1988. As we will need your signature on file, we will need a hardcopy. If you have any questions, or if you would like me to send you a hardcopy of the questionaire, you may call me at 415-336-2181 or send email to marsal@sun.com. I look forward to your response! Sincerely, Jack Marsal ONC Solution Guide Coordinator Sun Microsystems, Inc. 2525 Garcia Ave., mail stop 12-33 Mountain View, CA 94043 ******************************************************************** ONC SOLUTION GUIDE QUESTIONNAIRE ******************************************************************** Company name: ___________________________________________________ Street Address: _________________________________________________ Street Address: _________________________________________________ City: __________________________ State: _________ Zip: __________ Telephone: ____________________ email address: __________________ Telex: ________________________ Fax phone number: _______________ Contact information: _________________________________________________________ ONC Solution Guide contact (the person to whom we should address all future ONC Solution Guide mailings) _________________________________________________________ Sales Contact (Contact name from your company to be published in the ONC Solution Guide) _________________________________________________________ Technical Contact (person to whom we should send technical updates and information) Name of ONC/NFS implementation or product which includes it: __________________________________________________________ ONC/NFS features included in product: [ ] Network File System (NFS) [ ] Network Lock Manager [ ] Remote Execution (REX) [ ] Yellow Pages (YP) [ ] RPC [ ] XDR [ ] NETdisk [ ] other ________________________________________________ Implementation Information: [ ] Ported from ONC/NFS source code [ ] BSD [ ] System V [ ] UNFS [ ] Derived from public domain specification Operating system to which your ONC/NFS implementation or application has been ported (please be specific): __________________________________________________________________ Tranport protocol (e.g., TCP/IP, ISO, etc.): __________________________________________________________________ Are ONC/NFS features bundled with the overall operating system? [ ] yes [ ] no Product introduction date: _______________________________________ First customer ship date: ________________________________________ How is your product distributed? [ ]direct [ ]manufacturer's reps [ ]distributors other_____________________________ Pricing information: (indicate currency if not $US:____________) Price for quantity 1 of this product, or if required, price for a minimum-quantity purchase: $________ for qty 1 $________ for min qty ________ Price for volume purchase, site license, or network license, if any of these are available $________ for ___________________________________________ Price for educational or non-profit institutions: $________ for qty 1 $________ for ________________ ___________________________________________________________________ PRODUCT DESCRIPTION ___________________________________________________________________ Please provide a brief written description of the ONC/NFS implementation. We will use this description in the ONC Solution Guide. Responses may be edited so as to maintain a consistent style and format in the Solution Guide. Your description should mention the features and benefits of your ONC/NFS implementation. [[ Insert sufficient number of blank lines here. --wnl ]] ___________________________________________________________________ AUTHORIZATION FOR PUBLICATION ___________________________________________________________________ The information supplied about the above product(s) is correct to the best knowledge of the undersigned company. The undersigned company authorizes Sun Microsystems to publish this information in the ONC Solution Guide. The undersigned company understands that Sun will make every effort to ensure that the data printed is correct. Sun Microsystems is not responsible for any inaccurate information supplied to it. Signature ____________________________ Name__________________________________ Title_________________________________ Company_______________________________ Date__________________________________ ------------------------------ End of SUN-Spots Digest ***********************