Subject: Linux-Development Digest #388
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, 19 Jan 94 07:13:05 EST

Linux-Development Digest #388, Volume #1         Wed, 19 Jan 94 07:13:05 EST

Contents:
  Welcome to the comp.os.linux.* hierarchy! (Matt Welsh)
  Re: DOSEMU Problem (Tim Shnaider)
  Re: What's the current WINE status? (Eildert Groeneveld)
  Re: Math functions don't seem to work (Fritz Ganter)
  Re: PCI SCSI Support ? (Drew Eckhardt)
  Re: Is there an _official_ directory structure for linux? (Jeffrey Wescott)
  Re: Are we going to have DBX on linux? (Jeffrey Wescott)
  Re: What's the current WINE status? (R. Schalk)
  Re: What's the current WINE status? (R. Schalk)
  Re: DOSEMU Problem (Cindy Mann)
  Re: Is there an _official_ directory structure for linux? (Daniel Quinlan)
  Re: Still: Undefined symbol ___setfpucw (Harri Pasanen)
  Re: Status of NIS (cale hollingsworth)

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

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: 19 Jan 1994 07:53:19 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 
        reknowned 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
        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.


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

Subject: Re: DOSEMU Problem
From: tims@kcbbs.gen.nz (Tim Shnaider)
Date: 18 Jan 94 09:39:40 GMT

Chris Royle (car1002@cus.cam.ac.uk) wrote:
: When I type

: dos -A > /dev/null

: with dosemu 0.49

: The screen flickers violently, displays my video BIOS startup message, and
: hangs. It also flashes the floppy drive with boot disc in it once.

: I can switch consoles and kill the dosemu, but otherwise, it seems a bit
: crashed to me...

I had the same problem. Ok, what sort of video card do you have?
One way of fixing this is to use the GETROM program to dump your video
bios to a file and edit the config file in the /etc/dosemu directory
There will be a few video lines. 
Here is my video line
>video { vga console graphics chipset trident memsize 1024 vbios_file
/etc/dosemu/vbios }

where vbios is the file generated by going 
getrom > vbios

The rest should be as easy as following the instructions in the readme's.
Make sure you have a DOS boot disk in your drive A as the emulater still
needs the DOS startup files to work.
Hopefully you can get it working.

(Post all follow ups in this group )


--
Tim Shnaider   -    tims@kcbbs.gen.nz

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

From: groeneveld@tzv.fal.d400.de (Eildert Groeneveld)
Subject: Re: What's the current WINE status?
Date: Wed, 19 Jan 1994 08:23:02 GMT

For once, what *is* the current status of wine. At least somewhere in this
thread we should have a hint.
-- 
Eildert Groeneveld
Institute of Animal Husbandry and Animal Behaviour
Federal Agricultural Research Center
31535 Neustadt 
Germany
e-mail: eg@tzv.fal.d400.de

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

From: ganter@fvkmapc02.tu-graz.ac.at (Fritz Ganter)
Subject: Re: Math functions don't seem to work
Date: 18 Jan 1994 16:09:05 GMT

Andrezej Borowiec (anton@MCS.COM) wrote:
: /usr/tmp/cca010491.o: Undefined symbol _sin referenced from text segment
: /usr/tmp/cca010491.o: Undefined symbol _cos referenced from text segment
: make: *** [testmath] Error 1
: This happens every time I try to compile .
: I have stock SLS distribution with pl12 and gcc2.4.5
: Any ideas?
: Andrzej

You have to add -lm to the linkoptions.
It includes the math-libraries.

--

Fritz Ganter                    Graz University of Technology, Austria
Email:  ganter@fvkmapc02.tu-graz.ac.at, ganter@fvkmads02.tu-graz.ac.at
HAM-Radio:                OE6FAD@OE6XYG.AUT.EU, OE6FAD@OE6FAD.AMPR.ORG 
Phone:                +43 316 873-7222 (Office), +43 316 663243 (home)
   **********      Linux... try it, use it, love it.      ************

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

From: drew@kinglear.cs.colorado.edu (Drew Eckhardt)
Subject: Re: PCI SCSI Support ?
Date: Wed, 19 Jan 1994 06:02:35 GMT

In article <CJp4DC.CG0@rniil.rni.sub.org>,
Norbert J. Girardi <girardi@rniil.rni.sub.org> wrote:
>Drew Eckhardt (drew@kinglear.cs.colorado.edu) wrote:
>: In article <2gtqir$5tg@news.cs.tu-berlin.de>,
>: Wolfgang Jung <wong@cs.tu-berlin.de> wrote:
>: >
>: >Two things to ask:
>: >
>: >a)  Are there special patches involved running linux on a
>: >    PCI Board ?
>: No.
>: >b)  Is there a SCSI-Driver for that SCSI Chip, which sits on
>: >    those PCI Boards ?      
>: It's under development.
>
>: I'm writing a driver for the chip and article concerning it "PCI unter
>: Linux" for IX Multiuser Multitasking magazine.
>
>Any publication date yet? 

A German Linux user mailed me saying that he'd read that IX 
was working on a NCR53c810 driver and that the planned release
date was May.  

If that's accurate, presumably the planned "official" release date 
and article publication coincide, although as I stated in my previous
post, alpha code should be available a long time before then - 

    "shortly after my sample hardware shows up"

since the code's fleshed out, and hopefully it will work the first 
time I run it on real hardware :-)

(They attempted to deliver my PCI board today, I had a cashiers check
waiting and left explicit instructions with my roomates to give it to
the UPS deliveryman, some one was home all day, and the UPS driver left
a note on my door saying they'd try again tommorrow.  SIGH)

>Or, do we have to ask Juegen Steeger
>( editor in chief of iX) ??

If you want an official answer, that couldn't hurt.

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

From: wescott@spectrum.cs.bucknell.edu (Jeffrey Wescott)
Subject: Re: Is there an _official_ directory structure for linux?
Date: 19 Jan 1994 06:26:11 GMT
Reply-To: wescott@spectrum.cs.bucknell.edu

First of all, this message should NOT have been posted in
comp.os.linux.development.  c.o.l.d is intended to be used for kernel
deveopment discussion.  Your question does not have anything to do
with the kernel.  Read the Linux META-FAQ for details, available by
anonymous ftp on sunsite or any of the other Linux sites.

To answer your question, however, there *IS* a file-system standard
being worked on currently.  As far as I have heard, it is VERY
in-depth and quite understandable and well-written.  I am not sure
when it is going to be released, but it is worth the wait (from what I
hear).  There used to be a FSSTND Linux-Activists channel, but I am
not sure if still exists or not.  Anyone?  Your best bet would be to
wait for the file-system standard document and use it as your guide.
Maybe someone from the channel will read your post or mine and will
respond.  ;-)  I agree, though.  Most current Linux distributions do
have quite a sloppy or incomplete file system.  *sigh*

--
Jeffrey Wescott                 <wescott@spectrum.cs.bucknell.edu>

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

From: wescott@spectrum.cs.bucknell.edu (Jeffrey Wescott)
Subject: Re: Are we going to have DBX on linux?
Date: 19 Jan 1994 06:32:46 GMT
Reply-To: wescott@spectrum.cs.bucknell.edu

First of all, this question should NOT have been posted in
comp.os.linux.development, which is ONLY intended for kernel
discussion.  Please read the META-FAQ for further details.  You can
obtain the META-FAQ by anonymous ftp to sunsite.unc.edu or any of the
other common Linux ftp-sites.  If you can't get a copy, e-mail me and
I will send you one.

To answer your question, gdb can "trace" as you said, but it is not
called tracing.  Are you using Emacs?  Emacs is the best environment
to run gdb in, so that is what you should do first.  Once in Emacs,
split the Emacs window in two.  In one window, load gdb.  In the
other, load your source file.  Put the cursor into the source-file
window and set a breakpoint where you would like to begin the trace
(read the info-page for gdb if you don't know how to set a breakpoint,
but CTRL-X, <SPC> should work).  Then put the cursor into the gdb
window and run the program.  It will break at the breakpoint and put a
little arrow in the left-hand column of the source window where it has
"broken".  Type 'step', or 's' and the arrow will move, line by line,
in the source window.  This should do what you need.

Hope this helps.
--
Jeffrey Wescott                 <wescott@spectrum.cs.bucknell.edu>

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

Date: Wed, 12 Jan 1994 14:25:56 +0100
From: U001295@HNYKUN11.URC.KUN.NL (R. Schalk)
Subject: Re: What's the current WINE status?

In article <1994Jan11.230057.8628@taylor.wyvern.com>
mark@taylor.wyvern.com (Mark A. Davis) writes:

<a lot of blabber about dates deleted>
>>In Europe, people tend to write dates in Day/Month/Year format instead
>>of our Month/Day/Year format.  It makes more sense to me, actually,
>>since it goes from least-significant to most-significant in order.
>
>It does make a lot more sence, especially for sorting....  but hey, that's
                                               ^^^^^^^
Not really YYMMDD is easiest for sorting and comparing, most systems use this
internal format. e.g. 940112 < 941201 is TRUE this way. When you have to map
it to the real world, you have to map it to your local settings.

>the standard here and would be pretty hard to fight :)   What can we do?
>USA is still not even metric yet....  hmm 2 and 13/16ths less 1 and 5/8ths
>inches plus four and 1/8th feet divided by 14/25ths yards......   eeeeek

Looks like a nightmare to me. 15 years ago I was in Canada, and were
transfering from miles to kilometers, so a lot of signs had both speeds.
Is Canada now completely metriciced? (Is that a correct word ???)

Grtx Ronald

********************************************************************
* ing. Ronald Schalk, afdeling CS, sectie COOS                     *
* Universitair Centrum Informatievoorziening (UCI)                 *
* University of Nijmegen (KUN)    snailmail: Geert Grooteplein 41  *
* e-mail : R.Schalk@uci.kun.nl               6525 GA Nijmegen      *
* tel: +31 80 617997 fax: +31 80 617979      The Netherlands       *
********************************************************************

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

Date: Thu, 13 Jan 1994 10:00:38 +0100
From: U001295@HNYKUN11.URC.KUN.NL (R. Schalk)
Subject: Re: What's the current WINE status?

In article <14165@dirac.physics.purdue.edu>
bcr@bohr.physics.purdue.edu (Bill C. Riemers) writes:

>Other notes:
>  English pronounce "Z" as "Zedd", while Americans pronounce "Z" as "Zee".
>  People from former Soviet states that speak English, often have a very
>  difficult time understanding the American accent even if thier English
>  is very good!  (In this cas an English to English translator can greatly
>  facilitate communication, until the other party has practiced American
>  English or you have practiced a Brittish pronounciations(sp)/accent.)
>  For some reason Western European's don't seem to have this problem even
>  if they have never studied American English.

In case of Dutch people: a lot of movies on tv are american movies. Overhere
we don't like resynchronised movies, so we hear a lot of American language.
I suppose that's the reason we don't have that kind of problem, although
we learn at school the perfect "how do you do" :-) I guess that in the former
USSR there weren't that many American movies.
>
>                                   Bill
>
Ronald


********************************************************************
* ing. Ronald Schalk, afdeling CS, sectie COOS                     *
* Universitair Centrum Informatievoorziening (UCI)                 *
* University of Nijmegen (KUN)    snailmail: Geert Grooteplein 41  *
* e-mail : R.Schalk@uci.kun.nl               6525 GA Nijmegen      *
* tel: +31 80 617997 fax: +31 80 617979      The Netherlands       *
********************************************************************

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

From: cam@adied.oz.au (Cindy Mann)
Subject: Re: DOSEMU Problem
Date: Wed, 19 Jan 1994 05:57:32 GMT

Chris Royle <car1002@cus.cam.ac.uk> writes:

>When I type

>dos -A > /dev/null

>with dosemu 0.49

>The screen flickers violently, displays my video BIOS startup message, and
>hangs. It also flashes the floppy drive with boot disc in it once.

>I can switch consoles and kill the dosemu, but otherwise, it seems a bit
>crashed to me...

>Chris.

Yes, I get exactly the same problem.
I've read the documentation but still can't see what is wrong.

Anybody care to give us a solution?

c.


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

From: quinlan@spectrum.cs.bucknell.edu (Daniel Quinlan)
Subject: Re: Is there an _official_ directory structure for linux?
Date: 19 Jan 1994 07:43:51 GMT
Reply-To: quinlan@spectrum.cs.bucknell.edu

J. Mark Noworolski <jmn@crown.EECS.Berkeley.EDU> writes:

> I recently installed slackware on my box and am somewhat
> disappointed with how messy the directory structure is. I seem to be
> finding files all over the place in weird places. In many cases the
> applications themselves dont know where their include files are
> (eg. Latex has no clue without TEXINPUTS being set, emacs can't find
> auc-tex file, xmahjongg is in some weird place, /usr/local/games has
> only some games, /usr/X11/bin has x games - this is probably ok).

I can't really comment on Slackware's directory structure since I have
not seen it in action.  However, knowing the version of Slackware that
you are using would be useful since Slackware began undergoing
extensive directory structure changes (towards that standard you
mention) in the last version(s).  In any such massive change it is
possible that some problems may result.

> Where _should_ all these files be?
>
> I recall reading somewhere that there is some sort of recommended
> standard floating around somewhere.

Yes, there is.

Way back in August, there was a discussion on the "NORMAL" channel of
the Linux-activists mailing list that ended up in the creation of a
channel, "FSSTND", devoted to discussion of the subject.  Eventually,
a draft describing our recommendations was compiled/written (by yours
truly) which is still being worked on, although it is relatively
stable.  Plans are to make the draft public RSN (real soon now).
Incidentally, we moved to a different mailing list because the old one
was slow and unpredictable.

> thanks,
> mark
> PS. I want to know this because I am about to try porting latex to linux
> (the one distributed with slackware is apparently broken since it doesn't
> include slitex and also needs a setenv TEXINPUTS command to work).

I encourage any developer who is interested in knowing more about the
filesystem structure standard (by no means is it official) that we are
working on to contact me.  I ask anyone else to wait since we are
going to release our work soon -- there are probably going to be some
more changes before we release it.  Thanks.

// Dan

--
Daniel Quinlan  <quinlan@spectrum.cs.bucknell.edu>

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

From: pa@tekla.fi (Harri Pasanen)
Subject: Re: Still: Undefined symbol ___setfpucw
Date: 19 Jan 1994 08:04:48 GMT

   From: yavuz@bnr.ca (Yavuz Onder)

   I have followed the recent thread, but the suggestions did not help...

   I am running linux 99p13 gcc-2.4.5 libc-4.4.4 and ldso-1.3.

   I tried the following:

   - do not use "-g" option: it works, but is not acceptable, as I 
     need debugging info in the executable
   - world read permission on /usr/lib/crt0.o: i have it already
   - link with -lieee: i did, it removed ___fpu_control error, 
     but not ___setfpucw error

You probably have an old version of libg.a.  Unless you really need to
debug libc.a, you can do:

ln -sf /usr/lib/libc.a /usr/lib/libg.a

This will quite likely take care of your problem.  

   I also have a general question on this subject: since this type of
   problem can always come up if one does not know his/her libraries'
   contents inside-out, there must be a way to search the libraries in
   common places like /usr/lib /usr/X11/lib etc. Is there a tool like
   this? If yes what it is? If no, what would be involved in building
   one?

You can do: "nm /usr/lib/libg.a | grep fpu"
See man nm.

   Please post the answers... I do not have e-mail.


You're welcome,

Harri

--
======================================================
Harri Pasanen           pa@tekla.fi
phone                   home: 802 5350  work: 887 9436


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

From: CALE_HOLLINGSWORTH@billteds.com (cale hollingsworth)
Subject: Re: Status of NIS
Date: Mon, 17 Jan 1994 23:56:51 GMT

->
-> In article <CJ9Ktp.Fx4@lysator.liu.se> pen@lysator.liu.se (Peter Erik
-> writes:
-> >trockij@pt.Cyanamid.COM (Jim Trocki) writes:
-> >
-> >>  I read in the "Linux Network Administrators Guide" that someone w
-> >>working on NIS code.  Can anyone tell me the status of this project
-> >>Might we see it soon?
-> >
-> >Actually there are two different NIS "projects". One is included
-> >in the standard libc but only implements YP (NIS version 2). It
-> >requires that you find working ypbind and portmap daemons from
-> >somewhere that I don't know.
-> >
-> Does anybody know of the whereabouts of the `other' project?
-> And does it have a working YP/NIS?
-> And I guess I'll need to know where to find ypbind and portmap too!
->
-> Ross

test

===========================================================================
Bill and Ted's Excellent BBS - Russiaville, Indiana    Internet/USENET/Fido
(317) 883-4510 v32bis                                               4 Nodes
10 CD-ROM's On-line                       Over 2 Gigabytes Hard Drive Space
===========================================================================


============================================================

============================================










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


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