Subject: Linux-Development Digest #802
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:     Tue, 7 Jun 94 11:13:10 EDT

Linux-Development Digest #802, Volume #1          Tue, 7 Jun 94 11:13:10 EDT

Contents:
  Re: developing X apps in Linux (Frank Hofmann)
  Re: Appletalk support? (Martin Sckopke)
  Re: assembly language & Linux... rep insw, esp. (Florian Schmidt)
  Cannot use debuginfo with GCC en XView 3.0 (ramon.via@sni.de)
  Re: Frustrated with new kernels (Mike Dowling)
  Re: Serial drivers in 1.1.16 (autoconfig for IRQ's) (Jason Sokolosky)
  Re: SOLVED: /dev/audio busy (Rob Janssen)
  Re: Problems compiling 1.1.18 (Rob Janssen)
  Re: IPX is there, what next ? (Rob Janssen)
  Re: ncurses 1.8.1 (Mauricio Plaza Villegas)
  Re: Let's rename v1.0.9! [Was: Frustrated with new kernels] (Kevin Lentin)
  [Q]:  Linux as an aquisition platform/device driver  (Schultz, Russell)
  Device or resource busy error (Richard Whittaker)
  Re: NCurses 1.8.5 (Brandon S. Allbery)
  Re: ncurses 1.8.1 (Stuart Herbert)
  Re: problem programming Tcl/Tk + C application (Erik Troan)
  Re: Linux game development (Was Re: Why [DOS, W (Michael D. Zoran)

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

From: cip574@wpax01.physik.uni-wuerzburg.de (Frank Hofmann)
Subject: Re: developing X apps in Linux
Date: 7 Jun 1994 09:27:47 GMT

Paul Kolonay (paulk@cs.pitt.edu) wrote:
: What do I need in general to develop X apps under Linux... hardware
: requirements, software packages, etc... and specifically, what do I
: need to use PHIGS stuff...
              ^^^^^
Don't use it. it's slower than slow...
Ask the same question again in comp.windows.x.i386-unix and you will get
answers.

Frank

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

From: ecco@ipx2.rz.uni-mannheim.de (Martin Sckopke)
Subject: Re: Appletalk support?
Date: 7 Jun 1994 09:54:50 GMT

James Hammett (jamesh@apple.com) wrote:
: In article <Cpx0Do.K2v@stortek.com> Jeff Andre, andre@hoth.stortek.com
: writes:
: > One of the real questions is how much of an interest is there in such
: > a capability.  Beyond sharing printers, AppleTalk isn't a steller
: performer.
: > 
: > I believe there is a way to attach Ethernet to old Macs; I believe there
: > are SCSI devices.  If you're interested, I'll find the product.  I think
: > we may have one or two here at work.
: > 
: > The other solution would be to get an IP <-> AppleTalk gateway.
: > 
BTW did anybody successfully compile the CAP (California appletalk package) 
under Linux ? It allows to offer Appleshare disks to Macs and to share
printers with unix-boxes.
    Martin

--
* ----------------------------------------------------------------------- *
* Martin Sckopke (ecco@ixp2.rz.uni-mannheim.de)                           *
* ----------------------------------------------------------------------- *

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

From: F.SCHMIDT@BIONIC.zer.de (Florian Schmidt)
Subject: Re: assembly language & Linux... rep insw, esp.
Date: Fri, 03 Jun 1994 23:00:00 +0000

reply on user dyoung@superdec.uni.uiuc.edu


>       I'm trying to port some assembly language written for DOS
> assemblers to Linux to operate a video digitizer at high speed.
>
>       I'm having a little luck in spite of having absolutely NO
> documentation for the Linux assembler "as".
>
>       First question: what's the syntax for "rep insw" for the
> Linux assembler? It's something like rep insw %ax,%es:(%edi),
> right? What is it exactly? rep insw %dx,%es:(%edi) doesnt' work....
>
>       Where do I find documentation for the Linux assembler that covers
> all of that and more?
>
> Dave

here the same prob!




--
florian schmidt - der kaempfer gegen die rechtschreibung und fuer ungehemmte kommunikation
lessingstr. 36  33604 bielefeld
GMU -d+ -p+ c++ l u--- e* m--- s++/+ !n f? g+ w+ t+ r y?
## CrossPoint v3.0 ##

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

From: ramon.via@sni.de
Crossposted-To: gnu.gcc
Subject: Cannot use debuginfo with GCC en XView 3.0
Date: 7 Jun 94 07:04:21 GMT

Hi there,

I've tried to compile Workman under my Linux box, but I failed to
get it linked with debugging information in it. It complains about
missing libraries. I remember something that it uses different
libraries, but I can't find that information anymore (sorry, if it's
a FAQ). I do have 'libxview.sa', but I think I need 'libxview.a'. Is
that true? And if so, how can I obtain it. I'm running with the
Slackware v1.2.0 distribution...


--

Keep on hacking,                        \\\//
                                        (o o)
Ramon de Klein                  +----ooO-(_)-Ooo----+
Th. de Keyserstraat 298         |  _                |
7545 AJ  Enschede               | |_)        |/     |
The Netherlands                 | | \amon de |\lein |
                                |                   |
Email: ramon.via@sni.de         +-------------------+

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

From: mike@MooCow.math.nat.tu-bs.de (Mike Dowling)
Subject: Re: Frustrated with new kernels
Reply-To: on.dowling@zib-berlin.de
Date: Tue, 7 Jun 1994 11:16:55 GMT

>>> On 03 Jun 1994 22:08:46 GMT, ron@draconia.hacktic.nl (Ron Smits) said:

Ron> Sorry, but I would like to disagree, I'm now running 1.1.16 with a fully
Ron> functional network, 4.5.21 libraries and gcc 2.5.8, I havent encountered
Ron> any problems whatsoever.

Yes, indeed!  I've been following this discussion and find myself puzzled as to
difficulties some people seem to be having.  I'm using 1.1.18 and find it as
stable as a rock, as too all the previous kernels from 0.99.14 onwards.

As many have mentioned, the place to ask for help is comp.os.linux.help, but
let me add my voice of incompetence.

I have, on occasions, had severe problems.  Emacs fault segmenting, gcc giving
up the ghost claiming that it was killed or that it had an illegal instruction,
etc. etc.  Invariably the problem was not software but hardware.  I've had
ethernet cards that were hardware incompatible with the VGA cards that caused
Linux issue so many error messages that the system was impossible to use.  One
I set my DRAMS to "faster" when it should have been "slower", and that caused
these mysterious messages from gcc and so on.  Currently, there is a 386
upstairs that won't boot.   It is an identical copy of what I'm using to write
this, so it must be system dependent.  When it issued an error message from the
BIOS to the effect that its cache was faulty, it was clear that Linux is not to
blame.

My advice is that, if you are having perennial Linux problems, then look to
your hardware first.  I've even had problems that only occurred with Linux and
not with DOS, in the bad old days when I still did not trust Linux enough to
flush DOS.  Things have changed now!

                Mike Dowling
--
Dr. Michael L. Dowling                    (__)       on.dowling@zib-berlin.de
Abteilung fuer Mathematische Optimierung  (oo)
Institut fuer Angewandte Mathematik        \/-------\
TU Braunschweig                             ||     | \
Pockelsstr. 14                              ||---W||  *
38106 Braunschweig, Germany                 ^^    ^^    Ph.: +49 (531) 391-7553


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

From: sokolosk@socket.cuug.ab.ca (Jason Sokolosky)
Subject: Re: Serial drivers in 1.1.16 (autoconfig for IRQ's)
Date: Sat, 4 Jun 1994 06:21:53 GMT

Davor Jadrijevic (davj@ds5000.irb.hr) wrote:
: I also feel that CONFIG_AUTO_IRQ was better. I obtained setserial,
: and tried it after CONFIG_AUTO_IRQ. I had problems with uugetty.

: Without setserial, I was able to overtake the line at /dev/cua1 
: although uugetty was sleeping at /dev/ttyS1 After setserial that's 
: no longer possible. Device /dev/cua1 is reported busy. -- setserial
: seems overcome - any help how to get normal behaviour back?

: Also, why is setserial so slow when autodetecting devices??? 

: Best regards, Davor.
: --
: <davj@ds5000.irb.hr>


I agree.  I liked the automatic kernel configuration.  I'm having some
problems with uugetty that I never had before.  It seems to answer the
phone once, but it can never initialize the line again after that, so
it never answers after that.  

Does anyone know what could be the problem???

Jason Sokolosky
sokolosk@socket.cuug.ab.ca

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

Crossposted-To: comp.os.linux.admin,comp.os.linux.help
From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: SOLVED: /dev/audio busy
Reply-To: pe1chl@rabo.nl
Date: Tue, 7 Jun 1994 07:42:15 GMT

In <2t08ro$i9m@csnews.cs.Colorado.EDU> drew@kinglear.cs.colorado.edu (Drew Eckhardt) writes:

> D8 and D9 are used for DACK0 and DRQ0.
> 
> >I think it is more like this: DMA #0 is sometimes used to indicate 'DMA
> >not used'.  E.g. for VLB or EISA busmastering cards.   If that is the
> >case, your patch is not the appropriate way to get it working.
> 
> Since the hardware in question is an ISA board, this patch is 
> correct.

Ah, interesting...  Thanks.  I am out of 8-bit DMA channels, and that means
I can have another one by adding a piece of cardedge to an 8-bit card.
I had studied the 8-bit connector layout and found only DMA1-3.

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

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

From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: Problems compiling 1.1.18
Reply-To: pe1chl@rabo.nl
Date: Tue, 7 Jun 1994 07:43:05 GMT

In <SCHULTE.94Jun6235036@sun3.thp.uni-koeln.de> schulte@thp.uni-koeln.de (Martin Schulte) writes:

>I got linux-1.1.13 from ftp.cs.helsinki.fi and patched it up to
>1.1.18.

>I configured it without net(see below for my .config) and got the
>following problem when linking:

>net/net.o: Undefined symbol _dev_init referenced from text segment
>net/net.o: Undefined symbol _net_bh referenced from text segment

>I use gcc2.5.7.

>Any help appreciated, Martin

For now, it is easiest to configure with networking enabled.  This
will undoubtedly be fixed in a later patch.

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

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

From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: IPX is there, what next ?
Reply-To: pe1chl@rabo.nl
Date: Tue, 7 Jun 1994 07:44:35 GMT

In <1994Jun7.013906.811@offline.be> marc@offline.be (Marc Duponcheel) writes:

>Hello Linux developers,

>I noticed the precence of IPX code when compiling
>linux. Does this mean that a Linux PC will be able
>(or already is able) to be inegrated in a Netware
>network ? If yes, is it possible to run IPX and TCP/IP
>together on one card  ? thanks for replies !

Yes, but only from dosemu.  There is no support of the protocols
above IPX in the kernel.  dosemu can run the Novell products.

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

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

From: mok@roxanne.nuclecu.unam.mx (Mauricio Plaza Villegas)
Subject: Re: ncurses 1.8.1
Date: 07 Jun 1994 00:06:04 GMT


 Why don't you try ncurses 1.8.5?

ciao.
-mok
" A rock that doesn't love it's a rolling stone "
--


ciao.
-mok

" A rock that doesn't love it's a rolling stone "

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

From: kevinl@bruce.cs.monash.edu.au (Kevin Lentin)
Subject: Re: Let's rename v1.0.9! [Was: Frustrated with new kernels]
Date: 7 Jun 1994 01:56:32 GMT

Kevin Brown (kevin@frobozz.sccsi.com) wrote:
> Look, guys, this isn't a hard problem or anything.

> Where does one get v1.1 patches?  On

>       ftp.funet.fi:pub/OS/Linux/PEOPLE/Linus/v1.1

> right?

> So instead, move v1.1 to:

>       ftp.funet.fi:pub/OS/Linux/PEOPLE/Linus/ALPHA/v1.1

> and keep 1.0 in:

>       ftp.funet.fi:pub/OS/Linux/PEOPLE/Linus/v1.0.

> And make the same changes on all sites that hold patches.  The same thing
> goes for the networking code.

That would work for people getting the patches but there is still the
problem that people who don't know better see messages in the col.* groups
asking questions about and commenting about 1.1.* kernels. Their immediate
reaction is to post saying 'Where can I get these 1.1 kernels?', 'Should I
ugrade?', 'What is the latest version?', etc. 

Maybe a different numbering scheme is needed. How about we turn 1.1.* into
0.999.0.* :-) [ie 0.99 because it is alpha and 0.* because it is also
development on top of the 1.0 kernel].

> People who retrieve the v1.1 patches will then *immediately* know that it's
> an ALPHA-stage kernel, without looking at any documentation.  No need to
> protect the sources in a private directory, no need to change the version
> numbers.

I don't believe in changing the version numbers. Unfortunately, although
your solution will certainly help in a few situations, I don't think it
solves the general problem. The solution to the general problem is to
include the details in the daily posting and educate the people out there.


-- 
[==================================================================]
[ Kevin Lentin                   |___/~\__/~\___/~~~~\__/~\__/~\_| ]
[ kevinl@bruce.cs.monash.edu.au  |___/~\/~\_____/~\______/~\/~\__| ]
[ Macintrash: 'Just say NO!'     |___/~\__/~\___/~~~~\____/~~\___| ]
[==================================================================]

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

From: schultz_russell@semail.jsc.nasa.gov (Schultz, Russell)
Subject: [Q]:  Linux as an aquisition platform/device driver 
Date: 6 Jun 1994 19:14:47 GMT

We're currently in the process of making some decisions about choosing
a UNIX flavor for an aquisition platform that may eventually find
itself on the MIR spacestation.

What, if any, device drivers are written for a/d acquisition cards, and
what/how easy is it write custom drivers for Linux?

Source code, faqs, personal experience, whatever would be greatly
appreciated.

P.S.  it would be extra spiffy if Linux ran on a IBM thinkpad 750, does
it?

Russ
--
I'm not allowed to get anybody in trouble except myself.

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

Crossposted-To: comp.os.linux.admin
From: rwhittak@orion.docwhitehorse.doc.ca (Richard Whittaker)
Subject: Device or resource busy error
Date: Tue, 7 Jun 94 04:33:21 GMT

After much helpful E-Mail suggestions, I've finally suceeded in getting the
version 1.1.18 kernel to compile (yay!), HOWEVER, I've run into a problem
with my serial ports.. I now get the error "device or resource busy" when I
try to access any of the ports on my DigiBoard, and this error was not
occuring with my version 1.0 kernel (which I'm using as a backup right
now)... I heard once a while back that the serial driver was made "less
agressive" in it's assertion of interrupt lines, and that may be causing
some of my grief, however, the serial drive looks to be substantially
changed to the point where I can't plug in my more "agressive" serial driver
from way back to .99pl12 (this is how I got 1.0 to work :-)).. Does anyone
have a bloodhound of a serial driver that I can use in the place of the one
included with 1.1.18?.. If not, are there any suggestions as to how I can
"toughen up" the 1.1.18 serial driver?..

Any help is much appreciated..

E-Mail is the preferred method of response.. :-)

Thanks in advance..

                                        Cheers,
                                        Rich W.
--
Richard Whittaker: Snailmail: 1102 Pine St, Whitehorse YT Y1A 4E8
  Internet E-Mail: rwhittak@orion.docwhitehorse.doc.ca 
Geographic Coords: 60 Deg., 45', 53" N., 135 Deg., 7', 17" W. 
    Amateur Radio: VY1RW, VY1RW@VY1DX, VY1RW@VY1BBS, 145.010 MHz         

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

From: bsa@kf8nh.wariat.org (Brandon S. Allbery)
Subject: Re: NCurses 1.8.5
Date: Tue, 7 Jun 1994 00:01:19 GMT

In article <2t02g7$opo@netaxs.com>, sto2@netaxs.com (Brian Stoler) says:
+---------------
| Well, I did the same as you, installed 1.8.5 over Slackware's default 
| 1.8.1, and yes, all ncurses apps' color broke. But after I recompiled 
| dialog, it worked fine. Try recompiling again .. and look at the Makefile?
+------------->8

ncurses 1.8.5's terminfo entries are incompatible with 1.8.1's... but are now
compatible with everyone else's, so you can now use binary terminfo entries
from other machines (and iBCS2 curses apps will work with the Linux terminfo
database if you're using the iBCS emulator).  You need to recompile existing
apps and to re-tic any terminfo entries you added that didn't come with
ncurses 1.8.5.

++Brandon
-- 
Brandon S. Allbery         kf8nh@kf8nh.ampr.org          bsa@kf8nh.wariat.org
The FUDs at Microsoft are shouting "Kill The Wabi!"

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

From: ac3slh@sunc.sheffield.ac.uk (Stuart Herbert)
Subject: Re: ncurses 1.8.1
Date: 6 Jun 1994 19:29:29 GMT

Zenon Fortuna (zenon@resonex.com) wrote:
: In article <2shm4q$fh0@news.cs.tu-berlin.de>,
: centauri <centauri@cs.tu-berlin.de> wrote:
: >Hi,
: >
: >I'm having some problems with ncurses.

: You should not waste time wrestling with ncurses 1.8.1.
: Get ncurses 1.8.5 from netcom.com:/pub/zmbenhal/ncurses/1.8.5.tgz

:       Zenon

Hrm, unfortunately, this is appears broken as well ... at least with ncurses
1.8.1 I don't have apps hanging for no apparent reason!

Stuart
--
Stuart Herbert -- S.Herbert@shef.ac.uk

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

From: ewt@merengue.unc.edu (Erik Troan)
Subject: Re: problem programming Tcl/Tk + C application
Date: 7 Jun 1994 00:59:24 GMT

In article <2svqn0$kln@taiwan.informatik.uni-rostock.de>,
Henning Zingler <hzingler@informatik.uni-rostock.de> wrote:
>I get the following errors from my compiler:
>gcc dbprog.c -I/usr/include/tcl -ltcl -ltk -o dbprog
>/usr/lib/libtcl.sa(__T00002.o): Undefined symbol "__NEEDS_SHRLIB_libm_4" referenced
>/usr/lib/libtcl.sa(__T00009.o): Undefined symbol "__NEEDS_SHRLIB_libm_4" referenced
>/usr/X386/lib/libtk.sa(__T00131.o): Undefined symbol "__NEEDS_SHRLIB_libX11_3" referenced
>/usr/X386/lib/libtk.sa(__T00131.o): Undefined symbol "__NEEDS_SHRLIB_libm_4" referenced

To get rid of the __NEEDS_SHRLIB_libm_4, try linking in the libm shared library.
Likewise, to get rid of the libX11 message, link in libX11. Your final
command line should look like this:

gcc dbprog.c -I/usr/include/tcl -ltcl -ltk -lm -lX11 -o dbprog

Erik

-- 
===========================================================================
"I'm not like that -- except when I am"   ewt@sunsite.unc.edu  = Erik Troan
                                          sasewt@unx.sas.com
    - Nora from "Pump up the Volume"

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

From: mdz@po.CWRU.Edu (Michael D. Zoran)
Subject: Re: Linux game development (Was Re: Why [DOS, W
Date: 7 Jun 1994 05:47:39 GMT
Reply-To: mdz@po.CWRU.Edu (Michael D. Zoran)


    I think a unix like system or a time sharing system is simply a bad
enviroments for games.  Simply put, most of the good games are written in
assembly, take over the entire machine, and usually completely bypass the
OS and access the hardware directly to give optimal performence.  This in
away is why DOS is so great for games.  The os loads the program and
doesn't do much else. Isn't this why its called a "Disk Operating system." 
I think a unix system with its layered hardware abstraction just gets 
in the way of these types of games.
    If you want to play games, reboot into dos.

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


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