From: Digestifier To: Linux-Admin@senator-bedfellow.mit.edu Reply-To: Linux-Admin@senator-bedfellow.mit.edu Date: Thu, 18 Nov 93 11:23:59 EST Subject: Linux-Admin Digest #173 Linux-Admin Digest #173, Volume #1 Thu, 18 Nov 93 11:23:59 EST Contents: Re: Debugger wants libc source?! (J. M. O'Donnell) TLI (Transport Layer Interface) for Linux (EXT Andreas Gerlich) Re: Slackware 1.1.0 fixed my lpr/lpd problems (Carlos Y. Villalpando) Re: Berkeley Fast Filesystem (Stephen Williams) Can't run VI and other programs!!! Re: Default shell on login [ANSWER] (Clifton Koch) Re: Berkeley Fast Filesystem (Stephen Williams) Re: Major/Minor numbers for Ethernet (Alan Cox) Should at(1) bump days? (Thomas Koenig) Re: SCSI timeouts: worse on a different machine (robert.k.nichols) Re: Tape drives that connect to floppy controller (Stephen Williams) Re: Default shell on login [ANSWER] (Ed Weiss) Linux and Yellow Pages (Edwin Ramirez) Welcome to the comp.os.linux.* hierarchy! (Matt Welsh) ---------------------------------------------------------------------------- Crossposted-To: comp.os.linux.development From: odonnell@mpx0.lampf.lanl.gov (J. M. O'Donnell) Subject: Re: Debugger wants libc source?! Date: Wed, 17 Nov 1993 16:46:00 GMT In article , thompson@indigo.cuug.ab.ca (Bruce Thompson 295-5967(w) or 229-3370(h)) writes... >In article <2be9at$p5m@fbi-news.informatik.uni-dortmund.de> muenx@heike.informatik.uni-dortmund.de (Holger Muenx) writes: > > Guten Tag! > > Unfortunately, while debugging various pieces of code, I really that my > debuggers -- gdb and ups -- demand the sources of libc when libc calls, > like printf or whatever, are reached. > > I can pass it by using "next" instead of "step"ping into the call. However, > it's not very comfortable. Moreover, I always get a disturbing little "beep" > for each call with a missing source. > > My libs are from image-4.4.1.tar.gz (or so) from the GCC directory on sunsite. > > So: what I am doing wrong? > > Thank you in advance! Any information will be appreciated! > > Holger Muenx (muenx@heike.informatik.uni-dortmund.de) > >What are you doing wrong? Nothing. The behavior you're describing is >correct, assuming that the libraries you are referring to were >compiled with debugging enabled. The debugger is assuming that since >you stepped into the library routines, you want to debug them. That >is, after all, what the step command is for. The debugger `should' >step completely over any routine that is not compiled for debugging >unless you specify to step to the next machine instruction. > >If you have the sources for libc, I'd recommend that you recompile >them without debugging, not to mention turning optimization on. If you >don't have the sources, I'd suggest looking into finding a libc that >is nott compiled with debugging on. > >In the mean time, here are a couple of things you can do once you've >stepped into a routine you don't have source for: > 1) Try the `continue -return' command (I think that's it). > Check the gdb manual for more info, but I believe there's > an option to continue that means continue until this > routine is exited. > > 2) Move up one stack frame and set a one time breakpoint on > the next line after the call you're currently in. > >Hope this helps some. I'd check my own system, but I don't yet have >it. > > Cheers, > Bruce. >-- >Bruce Thompson, |I do not speak for CUUG, ACTC Technologies, >Software Development Engineer,|Renegade Legion nor NAPRA, just myself. >ACTC Technologies Inc. |"So this is it, we're going to die!" >Renegade Legion, NAPRA #473 | -- Dent Arthur Dent >-- >Bruce Thompson, |I do not speak for CUUG, ACTC Technologies, >Software Development Engineer,|Renegade Legion nor NAPRA, just myself. >ACTC Technologies Inc. |"So this is it, we're going to die!" >Renegade Legion, NAPRA #473 | -- Dent Arthur Dent The libc-4.4.4 documentation says that if gcc is invoked with -g then it will link to a set of libraries with debugging on. I only installed 4.4.4 yesterday so I haven't played with this yet, but two posibilities come to mind: (1) do the compile only with -g, then invoke gcc again to link, (this does not need the -g flag so the normal libraries will be used). (2) specify the non-debugging libraries explicityl on the gcc command line. John. ------------------------------ From: gerlich@felix.rz.fh-ulm.de (EXT Andreas Gerlich) Subject: TLI (Transport Layer Interface) for Linux Date: 17 Nov 1993 23:14:27 GMT Reply-To: gerlich@felix.rz.fh-ulm.de Hello Linux-Users, I am looking for TLI (Transport Layer Interface) library for Linux. Do you have any kind idea where it can be found? Andreas -- Andreas Gerlich, FH-Ulm, Germany, email: gerlich@fh-ulm.de ------------------------------ From: unbelver@brain.jpl.nasa.gov (Carlos Y. Villalpando) Subject: Re: Slackware 1.1.0 fixed my lpr/lpd problems Date: 17 Nov 1993 18:38:25 GMT In article <2cdkop$4hf@knobel.knirsch.de>, andreas@knobel.knirsch.de (Andreas Klemm) writes: > byron@cc.gatech.edu (Byron A Jeff) writes: > > [...] About "no problems with Slackware lpr/lpd" vs. SLS one > > >I've have to agree except for one small point. I'm using a remote printer > >that's hung off a Sparc 2. It prints fine, no complaints from the daemon. > >The only problem is that lpq reports that the link is down always. > > Same for me with a sparcprinter on a SS10 with SunOS 4.1.3 && Slack 1.1.0. Not here. We've got a laser printer on a Sparc 2 and an HP plotter on a Sparc 1+. `lpq` reports the correct status on both. -- ======================================================================== Carlos Y. Villalpando | Don't even think I speak for the Gov't unbelver@brain.jpl.nasa.gov | I also didn't screw up the Mars Observer unbelver@ccwf.cc.utexas.edu | (There was that button I sat on......) ======================================================================== ------------------------------ From: sdw@meaddata.com (Stephen Williams) Subject: Re: Berkeley Fast Filesystem Date: 17 Nov 1993 18:42:49 GMT Piercarlo Grandi (pcg@aber.ac.uk) wrote: : >>> On 10 Nov 93 21:13:18 GMT, imcclogh@cs.ucsd.edu (Ian McCloghrie) said: : Ian> Now, it would be nice to have an _actual_ BSD FFS for linux, so : Ian> that one could communicate between the BSD du jour and linux, using : Ian> something other than DOS :) : Tar floppies/tapes? That's how one communicates between any two Unix : machines as a rule. Using filesystem structured floppies/removable : cartridges seems rather pointless... I disagree now that mkisofs -R is available... I've always used msdos to archive, but filename limitations make you put things in zoo or other archives. With Rock Ridge, all that goes away... My sun doesn't appear to understand Rock Ridge however... (SunOS 4.1.1) sdw -- Stephen D. Williams Local Internet Gateway Co.; SDW Systems 513 496-5223APager LIG dev./sales Internet: sdw@lig.net CIS 76244.210@compuserve.com OO R&D Source Dist. By Horse: 2464 Rosina Dr., Miamisburg, OH 45342-6430 GNU Support ICBM: 39 34N 85 15W I love it when a plan comes together ------------------------------ From: ez025807@othello.ucdavis.edu ( ) Subject: Can't run VI and other programs!!! Date: Wed, 17 Nov 1993 20:58:12 GMT I have trouble running VI, CU, and other programs on my computer. I have been running Linux on my computer for several months with no problem. Therefore, this is not due to incorrect installation. When I want to run programs such as CU or VI I get an error message saying: "No space left on device" In VI it would prompt: garbage() failed to read oldhdr?? [More...] "test" [READONLY] 1 line, 1 char [More...] Trouble writing to tmp file In CU it would prompt: cu: write (/usr/spool/uucp/Tmp00000000f3) cu: No space left on device cu: work: All matching ports in use Disconnected ('work' is the systems I am trying to call) Does anyone recognize this problem????? ------------------------------ From: koch@rtsg.mot.com (Clifton Koch) Subject: Re: Default shell on login [ANSWER] Date: 17 Nov 93 16:23:52 GMT Thanks to all who responded. The problem boiled down to bash not reading the .bashrc on login. I had assumed that sh was being run (which I know is also bash, but it behaves differently when run that way) from some sort of default. Bad assumption. The answer is that on a login shell, bash reads .bash_profile, and not .bashrc. On anything else it appears that it runs .bashrc and not .bash_profile. I don't feel too bad on not figuring this out, because I can't find this documented *anywhere* (except maybe the source :). Cliff -- ============================================================================= Cliff Koch Motorola Cellular Infrastructure Division koch@rtsg.mot.com ------------------------------ From: sdw@meaddata.com (Stephen Williams) Crossposted-To: comp.os.linux.development Subject: Re: Berkeley Fast Filesystem Date: 17 Nov 1993 18:58:49 GMT I'm afraid that I haven't closely examined the details of ext2 or the others, but I want to point out, while the topic is hot: Interactive Unix boosted performance of the SysV 1K filesystem 30% by just keeping the free block list in core as a bitmap. They flushed or invalidated it on the disk on unmount/crash. This had the effect of keeping a sorted freelist that was easy to allocate the largest contiguous set of blocks. Worked great, except that the first version took a while on large disks to mount/unmount, unless the disk was mostly full... Note that they still kept the safe inode freelist structure technically, just handled it differently internally. You could optimize memory by not having it on readonly mounts and only keeping a limited number of references (say the next N MB's worth of free blocks) in core and scanning the free list if you used those up. sdw -- Stephen D. Williams Local Internet Gateway Co.; SDW Systems 513 496-5223APager LIG dev./sales Internet: sdw@lig.net CIS 76244.210@compuserve.com OO R&D Source Dist. By Horse: 2464 Rosina Dr., Miamisburg, OH 45342-6430 GNU Support ICBM: 39 34N 85 15W I love it when a plan comes together ------------------------------ From: iiitac@swan.pyr (Alan Cox) Subject: Re: Major/Minor numbers for Ethernet Date: Wed, 17 Nov 1993 18:23:26 GMT In article mmatveev@boi.hp.com (Maxim Matveev) writes: >Hi, > >Can anyone say me the correct major/minor pairs for LANCE and DE-600 >pocket Ethernet adapter. I run SLS 1.03 with 0.99pl13. ANd only >devices for WD and 3Com cards are in /dev/. I read NET-2-HOWTO - no >information. This comes up again and again. You don't need no /dev entries or anything of the sort unless you are playing with Fred Van Kempens NET2E code. Neither 2D (in Slackware/SLS/...) nor NET2Debugged (in pl13f-r [ALPHA pl14]) need the dev entries. Alan ------------------------------ From: ig25@fg70.rz.uni-karlsruhe.de (Thomas Koenig) Crossposted-To: comp.os.linux.misc Subject: Should at(1) bump days? Date: 17 Nov 1993 23:44:04 GMT Hello, fellow Linuxers; I've put a bug/feature in my current at(1) implementation which, although sometimes useful, may also cause surprises. To quote the manpage: At allows some moderately complex TIME specifications. It accepts times of the form HHMM or HH:MM to run a job at a specific time of day. (If that time is already past, the next day is assumed.) So, when I run a command via $ at -f myscript 12:00 myscript will get executed at 12:00 the next day, if it is 13:00 (for example). Do people actually find this useful, or should it be removed in the next release (which is due within a few days, anyway)? Does anybody depend on it? Input appreciated, either via discussion or E-Mail. -- Thomas Koenig, ig25@rz.uni-karlsruhe.de, ig25@dkauni2.bitnet The joy of engineering is to find a straight line on a double logarithmic diagram. ------------------------------ From: rnichols@cbnewsg.cb.att.com (robert.k.nichols) Subject: Re: SCSI timeouts: worse on a different machine Date: 18 Nov 93 02:29:34 GMT In article dan@dyndata.com writes: >I posted before about seeing "SCSI timeout - command aborted" errors >when running my tape drive and hard disk at the same time when running >multiuser. The post generated a lot of "I'm seeing that too" >responses but not anything pointing to a solution. I just resigned >myself to having to shut the machine down to do backups and restores. > >Until I installed Linux on a second machine. > >The second machine is a 486DX33 instead of a 486DX50, and the SCSI >timeout error will appear sometimes even if the tape drive is not >running. :-( Both machines have 1542B controllers. The 33 has Linux >99.13, and the 50 has Linux 99.12. The only time I see this is when the tape drive is performing a lengthy operation that does not involve an ongoing data transfer. Rewind is the big culprit, but the first read operation on a newly loaded tape also takes a while. I haven't yet examined the SCSI operation with a logic analyzer, but judging by the blinkenlights, it would appear that the drive is not disconnecting, but hangs onto the bus during the entire operation. Perhaps the firmware on the host adapter is not giving the target the disconnect privilege. I'll have to check into it. (Gimme a chance! I haven't even got this thing booting reliably yet.) -- Bob Nichols AT&T Bell Laboratories rnichols@ihlpm.ih.att.com ------------------------------ From: sdw@meaddata.com (Stephen Williams) Subject: Re: Tape drives that connect to floppy controller Date: 17 Nov 1993 20:36:56 GMT Don & (bashford@griffy.scripps.edu) wrote: : I would like to get a tape drive for my linux system and I do not have : a SCSI card now. It looks like a SCSI card + SCSI tape drive combination : will cost over $700, but for less than $200 there are tape drives that : connect directly to the floppy controller. Can I use these floppy-connecting : tape drives with linux? : The brands I have seen are: : Colorado Jumbo 250 : Conner Tape Stor : 250MB Internal System QIC-80 With ftape (0.9.6???), I've been trying to get the Conner to work. It can go to the end and rewind, but other operations seem to cause errors: the kernel complains about a bad address and dumps the driver state or something. You have to install modules, which comes with it. : Both of them claim to support "UNIX/XENIX" with "optional software." : I have looked at the old FAQ and at the hardware and SCSI HOWTOs but : I find no mention of tape drives of this kind. I'd appreciate advice : on using them with linux sdw -- Stephen D. Williams Local Internet Gateway Co.; SDW Systems 513 496-5223APager LIG dev./sales Internet: sdw@lig.net CIS 76244.210@compuserve.com OO R&D Source Dist. By Horse: 2464 Rosina Dr., Miamisburg, OH 45342-6430 GNU Support ICBM: 39 34N 85 15W I love it when a plan comes together ------------------------------ From: spock@oca.com (Ed Weiss) Subject: Re: Default shell on login [ANSWER] Date: Wed, 17 Nov 1993 20:37:30 GMT In article , Clifton Koch wrote: > The problem boiled down to bash not reading the .bashrc on login. I had >assumed that sh was being run (which I know is also bash, but it >behaves differently when run that way) from some sort of default. Bad >assumption. The answer is that on a login shell, bash reads .bash_profile, >and not .bashrc. On anything else it appears that it runs .bashrc and not >.bash_profile. > > I don't feel too bad on not figuring this out, because I can't find this >documented *anywhere* (except maybe the source :). Have you tried 'man bash'? However, I do agree that the first snippet should also be mentioned in the invocation section. > Bash also interprets a number of multi-character options. > These options must appear on the command line before the > single-character options to be recognized. > > -norc Do not load the personal initialization file > ~/.bashrc if the shell is interactive. This is > the default if the shell name is sh. > INVOCATION > A login shell is one whose first character of argument zero > is a - , or one started with the -login flag. > > An interactive shell is one whose standard input and output > are both connected to terminals (as determined by > isatty(3)), or one started with the -i flag. PS1 is set and > $- includes i if bash is interactive, allowing a way to test > this state from a shell script or a startup file. > > Login shells: > On login: > if /etc/profile exists, source it. > > if ~/.bash_profile exists, source it, > else if ~/.bash_login exists, source it, > else if ~/.profile exists, source it. > > On logout: > if ~/.bash_logout exists, source it. > > Non-login interactive shells: > On startup: > if ~/.bashrc exists, source it. > > Non-interactive shells: > On startup: > if the environment variable ENV is non-null, expand > it and source the file it names. -- Ed Weiss "I thought it was generally accepted, sir, that spock@swissbank.com Vulcans are an advanced and most honorable race." "They are, they are. And damn annoying at times." ------------------------------ From: ramirez@mchip00.med.nyu.edu (Edwin Ramirez) Subject: Linux and Yellow Pages Date: 17 Nov 93 21:40:34 GMT Hello all, I would like to run yellow pages on my linux machine, has this been ported to linux yet? Where can I find it (bind, yp,...) Thanks Edwin Ramirez ------------------------------ From: mdw@sunsite.unc.edu (Matt Welsh) Crossposted-To: comp.os.linux.announce,comp.os.linux.help,comp.os.linux.development,comp.os.linux.misc,comp.os.linux,news.answers,comp.answers Subject: Welcome to the comp.os.linux.* hierarchy! Date: 18 Nov 1993 03:18:10 GMT Archive-name: linux/announce/intro Last-modified: 8 August 93 Welcome to the comp.os.linux.* hierarchy! Background ========================================================================= This posting is an introduction to the comp.os.linux.* hierarchy of USENET newsgroups. Linux is a free implementation of UNIX for 80386/80486 machines covered by the GNU GPL. Most of the development of the Linux kernel has been done by Linus Torvalds, an internationally reknowned UNIX wizard from Helsinki, Finland. For the past two years or so, the newsgroup comp.os.linux has grown be one of the most popular groups on USENET. Late in 1992, a CFV for splitting comp.os.linux was posted; the only group which passed was comp.os.linux.announce, a moderated newsgroup for Linux announcements and patches. Six months later, during the summer of 1993, another CFV for splitting comp.os.linux was posted. The voting period for the comp.os.linux reorganization results ended at 23:59:59 UTC on 4 August 1993 (4:59PM US Pacific Time, 7:59PM US Eastern Time.) The results are as follows: comp.os.linux reorganization results - 1842 votes Yes No : 2/3? >100? : Pass? : Group ---- ---- : ---- ----- : ----- : ------------------------------- 1692 135 : Yes Yes : Yes : comp.os.linux.admin 1741 90 : Yes Yes : Yes : comp.os.linux.development 1647 177 : Yes Yes : Yes : comp.os.linux.help 1660 155 : Yes Yes : Yes : comp.os.linux.misc Because of this split, the newsgroup comp.os.linux will be deleted on 11 November 1993. The new newsgroups will be created on 11 August 1993. This posting describes these newsgroups, including comp.os.linux.announce, which will remain entact. General Policy ========================================================================= The general policy for the Linux newsgroups is simple. Who sets the policy? We all do. All of us on USENET are interested in communicating openly about a number of topics. That's why we have USENET. If you want the Linux newsgroups to work for you, a few suggestions: * Read the Linux FAQ and follow the newsgroups for some time before posting questions. This is very important. comp.os.linux suffered from HUGE amounts of noise and traffic because much of the growing readership never bothered to READ the newsgroup; they only posted questions. The same thing will happen with the new newsgroups unless you read the FAQ (found on sunsite.unc.edu in the file pub/Linux/docs/FAQ) and read the newsgroup for some time before posting questions. Chances are, your question has already been recently answered, and a simple browsing of the newsgroup will answer it. We suggest using a threaded newsreader such as "trn" which will allow you to browse and mark articles by subject, so you don't have to read each and every article in each newsgroup. * Crossposting between the Linux newsgroups is STRONGLY discouraged. If you do crosspost questions between Linux newsgroups, expect to be flamed to oblivion. The reason we have a newsgroup split is to categorize discussions into separate newsgroups. Crossposting negates this effect. If your posting cannot fit into ONE of the newsgroups c.o.l.admin, c.o.l.help, or c.o.l.development, then you should post it to c.o.l.misc. The one exception is for announcements. Occasionally, an important announcement (such as this one) will be crossposted between c.o.l.announce and one or more of the other c.o.l.* groups. These announcements must be approved by the .announce moderator; see below. * Reply to questions via e-mail if at all possible. While discussion in the newsgroups is encouraged, if someone is asking a simple question to which the answer is well-known, there is no reason to post the reply. Don't assume that the person posting the question actually reads the newsgroup or will even note your followup if they do. Reply via e-mail unless the reply is of general interest. * Don't flame newbies. Over the course of the past few months, the Linux community has developed an oversensitive ego and a reputation for being unfriendly towards newcomers, mostly because of unwarranted flaming by a handful of righteous individuals. If someone posts, saying, "Hi! I'm new to this group! What is Linux?" (which will inevitably happen as the new newsgroups are propagated), DO NOT FLAME THEM. When someone sees a new newsgroup pop up within "rn", they are justifiably curious about the new group and probably don't know that well over 80,000 people who know EVERYTHING about Linux read the group. Right? Instead of being rude, you can send a polite note to the poster, saying, "Hello, Linux is a free implementation of UNIX for the 386 and 486. You can get the FAQ from sunsite.unc.edu in /pub/Linux/docs. Let me know if I can be of help!". That's all. Not difficult, eh? You can even save your stock reply in a file and simply send form-letters to newbies if you wish. But there is very little point in flaming or ever being rude. It goes against everything that Linux can and should be. Just remember that nobody knows everything---not even Linus--- and that you were a newbie once, too. :) comp.os.linux.announce ========================================================================= Comp.os.linux.announce is a moderated newsgroup for Linux announcements and source patches. The purpose of this group was to get all of the ``important'' Linux information out of the regular newsgroup and into a place where all Linux users could see the important announcements without having to wade through a jungle of other postings. So far, this group has been very successful. The moderators for this group are myself (Matt Welsh, mdw@sunsite.unc.edu) and Lars Wirzenius (wirzeniu@cc.helsinki.fi). We will be sharing the moderator duty, and backing each other up to make sure that postings to this group will be approved as soon as possible after they're submitted. Submissions to this group should be mailed to the address: linux-announce@tc.cornell.edu If you have any problems or questions about c.o.l.announce, please send mail to the moderators at linux-announce-request@tc.cornell.edu Or simply mail us directly. This is not a request address for mailing list subscription; see below. A separate posting details the guidelines for submitting to this group. I plan to approve just about anything that's posted to this group, except for questions or discussions about Linux. So, please, post away. :) There are also archives of comp.os.linux.announce available at a number of Linux FTP sites: check sunsite.unc.edu:/pub/Linux/docs/linux-announce.archive There is a mailing list mirror of the comp.os.linux.announce newsgroup; to join, send mail to linux-activists-request@niksula.hut.fi With the line X-Mn-Admin: join ANNOUNCE at the top of the body (not in the subject). Approved postings to c.o.l.announce will automatically be mailed to this mailing list channel. comp.os.linux.admin ========================================================================= This newsgroup was created simply to thwart the unique newsgroup acronym "c.o.l.a", previously used by c.o.l.announce. However, this newsgroup is also used for discussions and questions about running Linux systems, either in a single-user or multi-user environment. Clearly, there is no large distinction between c.o.l.admin and c.o.l.help. However, .admin should be mostly used for discussions about RUNNING Linux, not USING or PROGRAMMING it. Unfortunately, especially with Linux, the line between system administrator and system user is very fuzzy. In short, we anticipate c.o.l.admin to be mostly about questions with installing, setting up, and configuring Linux systems, as well as other discussions relating to system administration. comp.os.linux.development ========================================================================= c.o.l.development, or "c.o.l.d" for short, is a newsgroup for questions and discussions about Linux kernel and systems-level development. Please note that this is a newsgroup about development OF Linux, not development FOR Linux. In other words, c.o.l.d isn't for questions about programming or porting software to Linux. Instead, this is a newsgroup for discussions about developing the Linux kernel itself, including writing device drivers, adding new features, and so on. In addition, discussions about development of shared libraries, and other essential systems-level projects, are welcome here. Hopefully, this newsgroup will embody some of the content and scope of the linux-activists mailing list channels such as GCC, KERNEL, SCSI, and NET. comp.os.linux.help ========================================================================= Comp.os.linux.help is perhaps the most general of Linux newsgroups. It is for any general user, programming, or setup questions and discussion about Linux. If your question is about Linux development, post to c.o.l.development. If it is about system administration, post to c.o.l.admin. However, if your question is of a more general nature, such as "How do I set up Linux for use with an NE2000 card?", c.o.l.help is your place. Remember that you should not crosspost between .help and other Linux newsgroups. This means that if you are asking for help in .development, that's fine, but .help is for those questions which don't fit into .admin and .development. comp.os.linux.misc ========================================================================= This group is the canonical ``catch-all'' for discussions and questions which don't fit into the other Linux newsgroups. While c.o.l.help is generally for questions, c.o.l.misc is for discussions of a general nature about Linux, such as setting up a file hierarchy standard, questions about Linus' personal life and virtual beer, and the inevitable flame war. Again, it should be noted that crossposting between c.o.l.misc and other Linux newsgroups is strongly discouraged. If your posting or question does not fit into ONLY ONE of the other Linux newsgroups, post it to .misc. Comments ========================================================================= If you have questions or comments about this document, please direct them to mdw@sunsite.unc.edu. Flames to /dev/null; cheques and money orders to Linus Torvalds. Thanks. ------------------------------ ** FOR YOUR REFERENCE ** The service address, to which questions about the list itself and requests to be added to or deleted from it should be directed, is: Internet: Linux-Admin-Request@NEWS-DIGESTS.MIT.EDU You can send mail to the entire list (and comp.os.linux.admin) via: Internet: Linux-Admin@NEWS-DIGESTS.MIT.EDU Linux may be obtained via one of these FTP sites: nic.funet.fi pub/OS/Linux tsx-11.mit.edu pub/linux sunsite.unc.edu pub/Linux End of Linux-Admin Digest ******************************