Subject: Linux-Development Digest #954
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, 27 Jul 94 22:13:15 EDT

Linux-Development Digest #954, Volume #1         Wed, 27 Jul 94 22:13:15 EDT

Contents:
  Re: Fix for problems with sound when system is idle. (Oliver Daudey)
  IPX (David G. Boney)
  Re: ASUS486SP3G Linux users? (Archie Cobbs)
  Re: file source? (Jim Balter)
  Genoa 8300 Hornet (NCR 77C32BLT) and Linux? (Pete Kruckenberg)
  Re: using RS232 from program ? (Adam DePrince)
  Re: Mounting sector-translated 540MB disks (Mark Lord)
  Re: threads in kernel (Larry McVoy)
  Welcome to the comp.os.linux.* hierarchy! (Matt Welsh)
  Re: IDE patch won't work w/new kernels? (David Boyd)
  Re: CD-ROM tray control (Ken Pizzini)

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

From: traveler@backdoor.hacktic.nl (Oliver Daudey)
Subject: Re: Fix for problems with sound when system is idle.
Date: 25 Jul 1994 16:28:24 -0000

In a previous article, Rob Janssen (rob@pe1chl.ampr.org) wrote:

[original article sacrificed to the Gods of Bandwidth]

: I would suggest making sure that nothing else is using irq 7...
: Normally this IRQ is used for the printer port.  Maybe your printer port
: permanently drives this line, and therefore the IRQ from the soundblaster
: does not get through reliably?
: That would at least explain why it does not wakeup the CPU from the halted
: state...

That's the weird thing about it...  I tried all possible IRQ's with no
success...  My printerport is configured for IRQ5, btw, so that couldn't
be the problem...  According to procinfo, the SB-IRQ's are comming in just
fine...

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

       Greets...

           Oliver......
--
   /----------------------------------------------------------------------\
   | traveler@backdoor.hacktic.nl  |  For my public PGP2.3-key, finger    |
   |                               |  traveler@hacktic.nl or send empty   |
   | Linux...  The full 32-bit,    |  mail to pubkey@backdoor.hacktic.nl  |
   | free Unix for 386 and higher. |  Support electronic privacy before   |
   |                               |  it's too late!  Use PGP!            |
   |      --- This message printed with 100% recycled electrons ---       |
   \----------------------------------------------------------------------/

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

From: dboney@cs.ttu.edu (David G. Boney)
Subject: IPX
Reply-To: dboney@cs.ttu.edu
Date: Mon, 25 Jul 94 06:12:14 GMT

Hi, 
        Where can I find info on how to use the ipx stuff in the kernel?


-- 
Sincerely,

David G. Boney                          AF&AM

American Heart Association Medical Student Research Fellow
Texas Tech School of Medicine

dboney@cs.ttu.edu       Texas Tech University
Ph. 806-742-1191        Department of Computer Science
Fax 806-742-3519        Lubbock, Tx. 79409     USA

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

From: archie@qin.CS.Berkeley.EDU (Archie Cobbs)
Subject: Re: ASUS486SP3G Linux users?
Date: 27 Jul 94 20:01:12 GMT

broadley@neurocog.lrdc.pitt.edu (Bill Broadley) writes:

>I'd like to talk to any ASUS PCI/I-486SP3G linux users, especially if
>they use the on board scsi.

There is a mailing list for ASUS boards like the SP3, SP3G, pentium, etc.
Mail to listserv@cornell.edu with a line like this in the message body:

        subscribe ASUS-L lastname firstname

Disclaimer: I THINK this is the correct procedure (this is from memory)!
Mail sent to "asus-l@cornell.edu" goes to the whole list.

-Archie


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

From: jqb@netcom.com (Jim Balter)
Subject: Re: file source?
Date: Wed, 27 Jul 1994 15:54:05 GMT

In article <MIKE.94Jul27121539@moocow.math.nat.tu-bs.de>,
Mike Dowling <on.dowling@zib-berlin.de> wrote:
>I've had mysterious problems when using the "file" command on certain files.
>It sometimes just dies with a segmentation fault.  I would very much like to
>re-compile it using the -g option and run it through gdb, but I have been
>completely unsuccessful in my attempts at locating the source code.
>
>Can anyone tell me where I can get it?

archie sez the latest version is in tesla.ee.cornell.edu:/pub/file-3.14.tar.gz
-- 
<J Q B>

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

From: kruckenb@sal.cs.utah.edu (Pete Kruckenberg)
Crossposted-To: comp.os.linux.misc,comp.os.linux.help,comp.os.linux.admin
Subject: Genoa 8300 Hornet (NCR 77C32BLT) and Linux?
Date: 27 Jul 1994 20:34:10 GMT

I'm trying to find out if the new Genoa VLB 8300 Hornet, using the NCR
chipset (the numbers on the chip are 77C32BLT, 609-0391602, X1204148,
9413N) is in any way usable with Linux and X-windows. I need to know
ASAP (by 7/29 at latest) so I can decide if I should buy it or not. Is
anyone working on something to get it to work, or is there any way to
use previous drivers, etc, to make it work? Is it simply a matter of
clock settings that I can get out of the manual, or is a special
version of X-windows necessary?

Responses by email would be greatly appreciated, so I can get them
sooner. I will summarize to the group.

Thanks.
Pete.
kruckenb@sal.cs.utah.edu
pete@dswi.com

--
  ------------------------------------------------------------------------
  Pete Kruckenberg                       School: kruckenb@sal.cs.utah.edu
  University of Utah                       Work: pete@dswi.com
  Computer Engineering    For even more addresses, "finger pete@dswi.com"

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

Crossposted-To: comp.os.linux.help,comp.os.linux.misc
From: axd0822@hertz.njit.edu (Adam DePrince)
Subject: Re: using RS232 from program ?
Date: Mon, 25 Jul 1994 06:42:02 GMT

In article <1994Jul24.113618.204@tora.robin.de>,
Steffen W. Schilke <sws@tora.RoBIN.de> wrote:
>Hi,
>
>I plan to write a framegrabber software to control and access a 
>framegrabber which is connected via a RS232 to my LinuX box. I
>would like to know how to set the speed of a serial port (is
>up to 115200 bps possible ?) and all the other tiny things I 
^^^^^^^^^^^^^^^^^^^^^

type "man setserial"

This will show you how to do things like set your speed to 115,200.

You had better have a 16550 or you are going to drop characters, and I 
suspect that your frame grabber doesn't have a very robust transmission
-- 
===============================================================
Tic.                            |       Adam DePrince
                                |       axd0822@hertz.njit.edu

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

From: mlord@bnr.ca (Mark Lord)
Subject: Re: Mounting sector-translated 540MB disks
Date: 27 Jul 1994 16:30:54 GMT

In article <315sj2$oge@constellation.ecn.uoknor.edu> parprods@ecn.uoknor.edu writes:
>   I'm using Ontrack-software with my Western Digital 540MB hard disk--
>and as it uses sector translation, I can't mount it under linux--or I don't
>think I can--what I'm asking is -Is there a way I can mount it?--I formatted
>it down originally so that linux would recognize it--but PC Tools made a 
>big fuss about it--and I think that's why my dos partition crashed last week--
>when I restored I install ontrack--thanks for any help, 

There is a kernel patch coming out shortly to provide support for
translation of drive geometries.  Let me know if it works or not in
your case.
-- 
mlord@bnr.ca    Mark Lord       BNR Ottawa,Canada       613-763-7482

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

From: lm@stanford.edu (Larry McVoy)
Subject: Re: threads in kernel
Date: 27 Jul 1994 21:58:07 GMT

Peter Mutsaers (plm@sci.kun.nl) wrote:
: In <313igq$i33@Times.Stanford.EDU> lm@stanford.edu (Larry McVoy) writes:
: 
: >Could you please explain what you mean by threads?  Are talking about
: >Sun like threads, where there are two sorts of processes, processes
: >that map 1:1 with an address space and processes (threads) that map
: >many:1 with an address space?  I personally think this is the wrong
: >approach.
: 
: >SGI has a model which is like the clone() stuff discussed here recently.
: >A "thread" is simply a new process that happens to share (part of) the 
: >parent's address space.  That is easy to implement, easy to scale, and
: >simple.
: 
: There are two problem2 with these SGI 'threads' however:
: a) not POSIX compliant.

Couldn't you build posix threads on top?

: b) very slow context switches! Even a little bit slower than between normal
:    processes. Not strange, because these 'threads' (sproc's in SGI-speak)
:    are full-blown processes that have a process table entry. They are
:    *not* multiple (light-weight) threads within one process.

This is a red herring.  Light weight threads in a single process are 
going to be fast but useless.  Useful threads context switch slowly.
Explanation: light weight user level threads don't have a kernel context,
i.e., if any thread blocks in a read() then they all block.  Useless.
Fast, but useless.  Any sort of thread that has a kernel context is 
basically a full blown process.  Sun's LWPs context switch just as
slowly as SGIs process threads.  More slowly, I believe.

You are a victim of hype, I am afraid.  Het spijt mij erg.

: plm@sci.kun.nl                  |  "...En?..., doet ie het al?"

--
--
Larry McVoy                     lm@cygnus.com                   (415) 821-5758

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

Crossposted-To: comp.os.linux.announce,comp.os.linux.help,comp.os.linux.admin,comp.os.linux.misc
From: mdw@sunsite.unc.edu (Matt Welsh)
Subject: Welcome to the comp.os.linux.* hierarchy!
Date: Wed, 27 Jul 1994 19:45:36 GMT

                 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@tc.cornell.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.

--
M. Welsh, mdw@sunsite.unc.edu

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

From: dwb@ITD.Sterling.COM (David Boyd)
Subject: Re: IDE patch won't work w/new kernels?
Date: 26 Jul 1994 18:04:01 GMT

In article <30sfrg$lmu@vixen.cso.uiuc.edu>,
Christian Holtje <choltje@ux1.cso.uiuc.edu> wrote:
>tjko@tarzan.math.jyu.fi (Timo Kokkonen) writes:
>
>
>>IDE Performance Patch v2.0 [by Mark Lord] doesn't work with new 
>>WD540 drives??? Or is it just my kernel 1.1.30 that causes the problem?
>
<Stuff Deleted>h
>
>This happens with my first HD (hda, which is mainly my dos parition and the
>swap space), but not my second partition (which is all linux).
>The HD are both WesternDigital HD's (340megs) Caviars...the second is
>newer by about a year and a half.
>
>       I can get HD info (like above) if it'll help anyone.
>BTW: You do know that kernel 1.1.32 has these patches in it already, though
>the little hdparm program isn't in there...I had to go hunt it out.
>(Also, don't use 1.1.32...it has a nasty typo in it...patch up to 1.1.33)
>
>
>>P.S. these IDE patches used to work in my machine with Seagate ST3390A 
>>drive (kernel v1.1.0) with no problems...
>
        These patches also used to work for me as well.  I thought it
might be another problem with my new Promise controller, but it looks like
something changed as I am having the exact same problems.  Will try an
older kernel tonight to verify. 

P.S. Glad to see that the IDE patches made it into the main kernal tree.

P.S.2 - Anyone gotten a Promise 4030VL controller to work with more
than 2 drives?  

-- 
David W. Boyd                UUCP:     uunet!sparky!dwb
Sterling Software ITD        INTERNET: Dave_Boyd@Sterling.COM
1404 Ft. Crook Rd. South     Phone:    (402) 291-8300 
Bellevue, NE. 68005-2969     FAX:      (402) 291-4362
I survived - Seoul Sea of Fire Tour 94

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

From: ken@chinook.halcyon.com (Ken Pizzini)
Subject: Re: CD-ROM tray control
Date: 25 Jul 1994 06:59:10 GMT

In article <4IXQB3YD@gwdu03.gwdg.de>,
>I could implement a separate CDROMCLOSEDOOR, but that probably would not
>help you. One can only take actions upon an "opened" device, and you will
>not get access to the device without a disk in it.

How about if it was opend O_NDELAY?

                --Ken Pizzini

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


** 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
******************************
