From:     Digestifier <Linux-Development-Request@senator-bedfellow.mit.edu>
To:       Linux-Development@senator-bedfellow.mit.edu
Reply-To: Linux-Development@senator-bedfellow.mit.edu
Date:     Wed, 11 May 94 21:13:07 EDT
Subject:  Linux-Development Digest #712

Linux-Development Digest #712, Volume #1         Wed, 11 May 94 21:13:07 EDT

Contents:
  Where's Linus? (khockenb@vaxc.stevens-tech.edu)
  Re: Linux CD-ROMs? (Rob Ransbottom)
  Re: New kernel introduces gawk bug? (Rick)
  Re: SLIP bitch (Jim Wygralak)
  Network File Server and 8 Workstations? Hardware Neede? (Brian Fritz/ ADVISOR Russell (MAE))
  CD-ROM's do all read and write now? (Brian Fritz/ ADVISOR Russell (MAE))
  Re: 1.0.9 kernel bug (with fix): don't signal zombie processes (Rob Janssen)
  Re: SLIP bitch (Denis Solaro)
  Welcome to the comp.os.linux.* hierarchy! (Matt Welsh)

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

From: khockenb@vaxc.stevens-tech.edu
Subject: Where's Linus?
Date: Wed, 11 May 1994 16:25:22 GMT

In article <1994May10.175557.1668@pe1chl.ampr.org>, rob@pe1chl.ampr.org (Rob Janssen) writes:
> however now that Linus is on a world tour, you may have better luck
> mailing it to him and/or to the "Linux activists" mailing list.

Would someone be willing to post Linus's itinerary on his world tour?  
I'm sure that many people would like to by him a non-virtual beer. :-)

-Kurt  "Looking for a _Linus Torvalds Tour Dates_ T-shirt"

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

From: rob@phavl.uucp (Rob Ransbottom)
Subject: Re: Linux CD-ROMs?
Date: Mon, 9 May 1994 17:17:27 GMT

In article <1994May8.171522.15836@cc.ntnu.edu.tw> s21008@cc.ntnu.edu.tw (DL83-08) writes:
>David - Foulds (foulds@shell.portal.com) wrote:

>: I just got the InfoMagic 2 CD set for $20, and it's hard to imagine
>: how much better a deal could be available.

>The deal sounds unbelievably good, I admit, but do I really need ALL
>versions? Is it possible to run stuff off of the CD (I have only 200MB HD,
>and I already need alot of it)? There are one or two systems that will run
>nearly or entirely off of the CD, one being EXPENSIVE, the other reasonable.

You can not run off of the InfoMagic CD.

If your access to ftp archives costs anything or is inconvenient, 
having the entire linux archives of tsx-11 & sunsite at hand is 
great.

If the melder of your distribution mangles a package somehow you 
can grab it from elsewhere on the CD.

Running off of a CD doesn't sound like much fun.  Slow. A good 
way to get a taste of linux for the unix newbie, though.  

rob


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

From: pclink@qus102.qld.tne.oz.au (Rick)
Subject: Re: New kernel introduces gawk bug?
Date: Tue, 10 May 1994 00:11:20 GMT

fish@ecst.csuchico.edu (Kevin Haddock) writes:

>I have some programs I wrote in gawk that run fine on everything I have
>tried except for slackware 1.2.0.  I have used SLS and debian.  I even
>downloaded a SLS gawk binary and I still got the same error.

>Here is how it is reproduced:

>> find / -print | awk ' { "echo " $1 | getline fubar; print fubar }'
>> 
>> I get about 90 lines of output then it says:
>> 
>> /usr/X11/lib/fonts/misc/xhextris.pcf.Z
>> /usr/X11/lib/fonts/misc/xmahjongg.pcf.Z
>> /usr/X11/lib/fonts/misc/vga.pcf.Z
>> charB08.pcf.Z
>> awk: cmd. line:1: (FILENAME=- FNR=91) fatal: cannot fork for "echo
>       /usr/X11/lib/fonts/75dpi/courB08.pcf.Z" (Try again)
>>Broken pipe

It's a problem with your awk program, and only indirectly related to the
kernel.  Every time you use "|" in an awk program, you use up a file
descriptor.  Your program doesn't free descriptors, so eventually you
hit the system limit and your program fails.  Try the following instead:

find / -print | awk ' { "echo " $1 | getline fubar; print fubar ; close "echo " $1}'

I'm assuming that your example is a cut down version of the original,
because I can't see what you're trying to do here (that couldn't be
done in a much simpler fashion).

Rick.

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

From: darus@MCS.COM (Jim Wygralak)
Subject: Re: SLIP bitch
Date: 10 May 1994 16:42:03 -0500

In article <1994May9.124820.2626@uk.ac.swan.pyr>,
Alan Cox <iiitac@uk.ac.swan.pyr> wrote:
>In article <2qhcdi$m8a@Mercury.mcs.com> darus@MCS.COM (Jim Wygralak) writes:
>>As I was getting the configuration info from him, I asked for the IP address
>>of the host side of the link and he wanted to know why I needed to know.
>>I explained that I was running linux, and that the slip software needed to
>>know. His response was that slip shouldnt need to know the IP of the other
>>end, and that I should register a bitch with the developers.
>
>Tell him the developers think he should explain what he's talking about
>better. I think what your pet gorilla is trying to tell you is that
>they are using bootp or rarp so you get your address via that system
>(effecitvely you broadcast 'help who am I' packets and it tells you.

I guess I need to clarify things a bit. I made the original post in haste.
First of all I should apologize for calling this a bitch, when it is
really just a point for discussion.

For everyone telling me to RTFM about dynamic addressing, I already have,
and I understand it. Dynamic addressing is not my problem.
*MY* IP address is static.

The part that is dynamic is the IP address of the HOST, depending which
dialin line I call on. (He has about 100 dial in lines connected to the
internet with a T1. He is not an amateur.)

His assertation is that MY end of the SLIP link shouldnt need to know
what the IP address of the OTHER end is.
I have some software that runs under DOS (ka9q networking package)
that works just that way. It couldnt care less what the IP address of the
system at the other end of the phone line is.

Dip on my linux system, on the other hand wont let me complete the setup
of the slip connection until I tell it the IP address of the host system.

Who's right here? How should this REALLY work?
-- 
==============================================================================
Jim Wygralak                         |
darus@mcs.com                        | PGP public key available via finger
DoD #0651  '74 Honda CL360 "George"  |

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

Crossposted-To: comp.os.os2.programmer.misc,comp.os.minix,comp.os.mach,comp.periphs,comp.unix.bsd,comp.unix.pc-clone.32bit,comp.os.386bsd.development,comp.sys.ibm.pc.hardware.misc
From: rme81977@zach.fit.edu (Brian Fritz/ ADVISOR Russell (MAE))
Subject: Network File Server and 8 Workstations? Hardware Neede?
Date: Tue, 10 May 1994 01:12:06 GMT

Our company is looking to build a 8 to 10 person network, which is to
include a server and 8/10 workstations.  Does anyone have any suggestions
for hardware and software?
Thanks in advance
-Brian


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

Crossposted-To: comp.os.os2.programmer.misc,comp.os.minix,comp.os.mach,comp.periphs,comp.unix.bsd,comp.unix.pc-clone.32bit,comp.os.386bsd.development,comp.sys.ibm.pc.hardware.misc
From: rme81977@zach.fit.edu (Brian Fritz/ ADVISOR Russell (MAE))
Subject: CD-ROM's do all read and write now?
Date: Tue, 10 May 1994 01:14:15 GMT

Can someone tell me if all CD drives read and write now?  Which ones
are the "top of the line"?
Thanks
-BRian


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

From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: 1.0.9 kernel bug (with fix): don't signal zombie processes
Date: Tue, 10 May 1994 17:55:57 GMT
Reply-To: pe1chl@rabo.nl

In <2qmogo$n1o@pad-thai.aktis.com> jik@cam.ov.com (Jonathan I. Kamens) writes:

>(I have just recently jumped into the linux fray, and more recently than that
>started debugging kernel problems, so I don't know what the protocol is for
>reporting bugs and fixes for the kernel.  If there is somewhere in particular
>to which I should be mailing bug reports and fixes in addition to posting them
>here, or if there is some specific format I should use for my bug reports and
>patches, please let me know.)

Posting it here will usually get it to the proper people's attention,
however now that Linus is on a world tour, you may have better luck
mailing it to him and/or to the "Linux activists" mailing list.
Read the FAQ to find out how to do that.
(KERNEL channel in this case)

Rob
-- 
=========================================================================
| Rob Janssen                | AMPRnet:   rob@pe1chl.ampr.org           |
| e-mail: pe1chl@rabo.nl     | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU     |
=========================================================================

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

From: drzob@vectrex.login.qc.ca (Denis Solaro)
Subject: Re: SLIP bitch
Date: Mon, 9 May 1994 20:18:30 GMT

Jim Wygralak (darus@MCS.COM) wrote:
: This is a bitch directed to linux software developers on behalf of the
: sysadmin at the site where I just got a dialup slip account.

: As I was getting the configuration info from him, I asked for the IP address
: of the host side of the link and he wanted to know why I needed to know.
: I explained that I was running linux, and that the slip software needed to
: know. His response was that slip shouldnt need to know the IP of the other
: end, and that I should register a bitch with the developers.

Unless I read all TCP/IP docs upside-down, how do you go without IP addresses?
(even unregistered...)

But let see, a bad syadmin who doesn't want to leave his Xtank session to
fiddle in configs...mmmm?!

Well, then go the un-official and kludgy way of TERM.  It doesn't belong to
the comp.os.linux.development as it is a pretty common tool, yet the
esoteric uses one can make out of it could (TCP/IP uucp, telnet tricks...).  
Be nice to sum it up in comp.os.linux.misc. At least until Slap comes out.
--
                                     Denis Solaro -- drzob@vectrex.login.qc.ca

"Winners don't use DOS.", William Csh Session, FBI. 

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

From: mdw@sunsite.unc.edu (Matt Welsh)
Crossposted-To: comp.os.linux.announce,comp.os.linux.help,comp.os.linux.admin,comp.os.linux.misc,comp.os.linux,news.answers,comp.answers
Subject: Welcome to the comp.os.linux.* hierarchy!
Date: 12 May 1994 00:29:20 GMT

Archive-name: linux/announce/intro
Last-modified: 18 January 94

[]
                 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 
        renowned UNIX wizard from Helsinki, Finland.

        For the past two years or so, the newsgroup comp.os.linux 
        grew to 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 on 4 August 1993.
        The results were 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 was deleted 
        on 11 November 1993. The new newsgroups were created 
        on 11 August 1993. This posting describes these newsgroups, 
        including comp.os.linux.announce, which remains entact.

        There should be no more traffic to the now-defunct group
        comp.os.linux; please use one of the new groups instead.


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.

          Also of interest are the Linux HOWTO documents, found on 
          sunsite.unc.edu in pub/Linux/docs/HOWTO. They describe many
          features of the Linux system.

        * 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
he 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-Development-Request@NEWS-DIGESTS.MIT.EDU

You can send mail to the entire list (and comp.os.linux.development) via:

    Internet: Linux-Development@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-Development Digest
******************************
