Subject: Linux-Development Digest #303
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:     Fri, 10 Dec 93 06:13:04 EST

Linux-Development Digest #303, Volume #1         Fri, 10 Dec 93 06:13:04 EST

Contents:
  compiling Motif on Linux (David Barr)
  Re: lib with fn _MAX? (Kai Petzke)
  Re: (none) (Mike Horwath)
  Ethernet Bugs... (Darren Reed)
  Re: patches for term for alpha/osf1.3 (Ken Burrell)
  Warning: ftape-0.9.7 may crash your system! (Kai Harrekilde-Petersen)
  Re: Merry $*!@ing Christmas! (Garrett Wollman)
  Compiling LAPACK with f2c and Linux (Dave Weber)
  Re: Xconfig (David E. Wexelblat)
  where should I tell ups to turn off power? (Kevin Smolkowski)
  searching for mailing-list redirect to local newsgroup via procmail (Carsten Paeth)
  Re: (none) (Rene COUGNENC)
  Other site to get libc-4.4.4.zip? (Kao Chen-Yi)
  Re: Neuronal networks (Christian Pablo Tagtachian)

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

From: davidb@stein3.u.washington.edu (David Barr)
Crossposted-To: comp.windows.x.motif
Subject: compiling Motif on Linux
Date: 8 Dec 1993 18:10:57 GMT

I'm trying to get Motif 1.2.3 to compile on Linux, but I'm having a
few problems.  Anyway, I've set up a small ftp archive to put the
patches I have to make to get it to compile.  I've also included a
copy of the output of my most recent compilation.  Some of the stuff
compiled without error, like libXm.a, libMrm.a and mwm, but nothing is
running very well yet.  You can get my patches and compile script from
ftp.u.washington.edu:/public/davidb/motif-linux.

David

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

From: wpp@marie.physik.tu-berlin.de (Kai Petzke)
Subject: Re: lib with fn _MAX?
Date: 9 Dec 1993 22:06:04 GMT

In <JROZES.93Dec9111015@allegro.cs.tufts.edu> jrozes@allegro.cs.tufts.edu (J Rozes) writes:

>In compiling the rmail package included with sendmail 8.6.4, ld spit out
>an error about function _MAX (and a few other functions) being defined
>but unreferenced. Adding -lbsd took care of the few others, but I can't
>find the library that has this function. Can anyone enlighten me?

Most likely, you are missing a header file.  MAX(a, b) is typically
defined as a macro.

If you can't find a header, which defines MAX, you might try:

        #define MAX(a,b)        ((a) < (b) ? (b) : (a))

or, (better, because it acceses a and b only once, but only
working if the type of argument is right):

        #define MAX(a,b)        ({ int _a = (a), _b = (b); \
                                _a < _b ? _b : _a; })

The gcc info files contain even some more examples on defining
a MAX() macro, which is independant of the type of a and b, or
doesn't fail, if given _a and _b as parameters.

Include these #define's into a header file included by all
those c modules, which use the MAX macro.
--
Kai
wpp@marie.physik.tu-berlin.de
Advertisement by Microsoft in a well-known German magazine:
        If you don't like our programmes, then make your own ones.
However, they expect you to use Microsoft products for this -:)

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

From: root@jacobs.mn.org (Mike Horwath)
Subject: Re: (none)
Date: 9 Dec 1993 19:07:01 GMT

and there are more odd things.

Bad page ... [address] [address]

happens pretty frequently after the error mentioned in previous post, then
within about 20 min of this error, it will eventually do a double kernel
panic :)  Oh the joy of being on the front line.

Wish I could give ya more information...

--
Mike Horwath    IRC: Drechsau   BBS: Drechsau   LIFE: lover
root@jacobs.mn.org  drechsau@jacobs.mn.org
Jacob's Ladder  612-588-0201  UUCP, UseNet, Linux files, BBS

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

From: avalon@cairo.anu.edu.au (Darren Reed)
Subject: Ethernet Bugs...
Date: 9 Dec 93 22:56:14 GMT

I'd forward these to the right list (wherever that is)...

anyway, when using 0.99pl14, etherlink III ethernet driver, 486dx33:

1) it prints up "missed interrupt" messages every now and then
   (strangely, only just before a connection is opened for TCP, usu.);

2) it was having problem with rlogin, so I did "^C" - kernel ran out of
   network buffers, REAL fast.  Had another machine pinging linux at this
   time and ping times went up too.

3) to do a test, someone logged in sevral times using telnet.  Then, in
   each session, cd'd to / and did an ls -lR.  The result was less than
   pleasant since I got the boot screen info fill syslogd files (kept
   getting sent from somewhere - who knows where!).  Restarting syslogd
   seemed like the thing to do, except that after restarting it, the messages
   continued.

Dec  3 17:23:00 whaite vmunix: 6>eth0: transmit timed out, tx_status 00 status 2
000.
Dec  3 17:23:00 whaite vmunix: 6>eth0: transmit timed out, tx_status 00 status 2
000.
Dec  3 17:23:01 whaite vmunix: exists (0), using polling driver
Dec  3 17:23:01 whaite vmunix: exists (0), using polling driver
Dec  3 17:23:01 whaite vmunix: Probing 82C710 mouse port device.
Dec  3 17:23:01 whaite vmunix: Calibrating delay loop.. ok - 16.61 BogoMips (tm)
Dec  3 17:23:01 whaite vmunix: Memory: 5476k/8192k available (496k kernel code,
384k reserved, 1836k data)
Dec  3 17:23:01 whaite vmunix: This processor honours the WP bit even when in su
pervisor mode. Good.
Dec  3 17:23:01 whaite vmunix: Floppy drive(s): fd0 is 1.44M, fd1 is 1.2M
Dec  3 17:23:01 whaite vmunix: Swansea University Computer Society Net2Debugged
[1.24]
Dec  3 17:23:01 whaite vmunix: IP Protocols: ICMP, UDP, TCP
Dec  3 17:23:01 whaite vmunix: eth0: 3c509 at 0x300      tag 1, AUI port, addres
s  00 60 8c c0 6a ed, IRQ 10.
Dec  3 17:23:01 whaite vmunix: 3c509.c:pl13t 11/24/93 becker@super.org
Dec  3 17:23:01 whaite vmunix: Checking 386/387 coupling... Ok, fpu using except
ion 16 error reporting.
Dec  3 17:23:01 whaite vmunix: Linux version 0.99.14 (root@whaite.anu.edu.au) #1
 Wed Dec 1 17:46:11 GMT 1993: 17:46:11
Dec  3 17:23:01 whaite vmunix: Partition check:
Dec  3 17:23:01 whaite vmunix:   hda: hda1 hda2 hda3
Dec  3 17:23:01 whaite vmunix: EXT2-fs warning: mounting unchecked file system,
running e2fsck is recommended
Dec  3 17:23:01 whaite vmunix: VFS: Mounted root (ext2 filesystem).
Dec  3 17:23:01 whaite vmunix: Adding Swap: 10344k swap-space
Dec  3 17:23:01 whaite vmunix: eth0: Missed interrupt, status then 2011 now 2011
  Tx 00 Rx 386e.
Dec  3 17:23:01 whaite vmunix: eth0: transmit timed out, tx_status 00 status 200
0.
Dec  3 17:23:01 whaite vmunix: exists (0), using polling driver

This is from (3) but has the messages from (1) too.
(2) didn't get logged, but were something about sk_buff being full and
no more network buffers left.

Oh, if it matters, I'm using pl13 with pl14 kernel and a few other odd
bits and pieces which were customised (nothing in the kernel).


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

From: ktb@uai.com (Ken Burrell)
Subject: Re: patches for term for alpha/osf1.3
Date: Thu, 9 Dec 1993 23:12:28 GMT


Hey, leave this guy alone.  Don't you know that you need to run term
on two machines to get X-windows working?  If you are like me, you run
Linux at home and dial into a work machine (like the Alpha). What's
the point of running Linux at home with term, if you can't get term
running on the other machine(an Alpha).  Let this guy speak!


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

From: kaihp@id.dth.dk (Kai Harrekilde-Petersen)
Subject: Warning: ftape-0.9.7 may crash your system!
Date: Thu, 9 Dec 1993 20:18:04 GMT


It is possible that ftape-0.9.7 may crash your system (and zapping your super-
block on the way down). To avoid this, ensure that the definition of BUFFERS
in the Makefile is set to 2 (it is set to 3 in the distributed Makefile).

This caused Bas' system to crash some months ago. We have, however, not seen
this since, but we want to PLAY IT SAFE!

On behalf of Bas,

Kai Harrekilde-Petersen,
khp@imladris.mic.dth.dk (prefered), or
kaihp@id.dth.dk

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

Crossposted-To: gnu.misc.discuss,comp.sources.d
From: wollman@aix2.emba.uvm.edu (Garrett Wollman)
Subject: Re: Merry $*!@ing Christmas!
Date: Thu, 9 Dec 1993 23:43:18 GMT

In article <KAIHP.93Dec9131724@idsun3.id.dth.dk>,
Kai Harrekilde-Petersen <kaihp@id.dth.dk> wrote:

>THIS CHANNEL IS MEANT FOR ***** D E V E L O P M E N T ******

Hmmm...  ``Channel''.  How quaint.

Oh, I see, you're complaining that the article to which you were
following up was a heated discussion being conducted in a
non-discussion group.  This doesn't make sense, since flamage is just
about the entire contents of gnu.misc.discuss, which is why it was
created in the first place (to keep said flamage out of the technical
groups).

Oh, you mean I have to read the Newsgroups: header, too?  Spoil-sport.

-GAWollman

-- 
Garrett A. Wollman   | Shashish is simple, it's discreet, it's brief. ... 
wollman@emba.uvm.edu | Shashish is the bonding of hearts in spite of distance.
uvm-gen!wollman      | It is a bond more powerful than absence.  We like people
UVM disagrees.       | who like Shashish.  - Claude McKenzie + Florent Vollant

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

From: weber@young.ece.cmu.edu (Dave Weber)
Subject: Compiling LAPACK with f2c and Linux
Date: 10 Dec 1993 04:04:47 GMT


              Getting LAPACK to work with f2c using Linux
              ===========================================


This is what I did to get the lapack distribution "lapack.tar.z" from
netlib.att.com:netlib/lapack/lapack.tar.z running on my Linux box. It
should work for any site without a FORTRAN compiler but no promises.
comments would be most welcome, especially in the places where I have
had to modify code or a test has failed. If there is sufficient interest,
I will upload the libraries to a suitable site.

Send comments to me (Dave Weber) at weber@young.ece.cmu.edu.  Please
take a look at the file INSTALL/install.ps in the lapack distribution
(careful, it is 150 pages long) for more information.


The bottom line:
================

The good news: LAPACK compiles and looks like it works. The single precision
               tests as well as the LAPACK++ tests work.

The bad news: Most of the LAPACK tests (single excluded) fail to 
              compile (f2c just dies with a segmentation error) 

              This is not too hard to do but I am sure I have
              overlooked something :-).


A few notes about what I have done might clear up some mysteries.

1) I have used f2c to compile K&R c (no -A switch) because f2c does its
   nut (segmentation fault) when compiling one of the BLAS test programs 
   with this option on.
2) I have used the optimizer only where it was used by the developers.
   I don't know why they switched it of on one or two files but they went
   to some trouble to do it. I acted dumb and followd the leaders.
3) I used Linux at patch level 13s and gcc v2.4.5 with libc4.4.2. I could 
   not coax a version number out of f2c so you guess.
4) I did not run the timings because I used the BLAS in the distribution
   which are apparently not well optimized so benchmarks will be a bit
   iffy. 
5) I had to kludge an "ETIME" function for the LINPACK testing routines.
   It is just a dummy and always returns 1. Maybe some kind soul can write
   an ETIME for linux as I do not feel like doing this right now. 
6) Most of the tests failed to compile. f2c just dies with a segmentation
   error so the problems lie here. This may be the version I have as Steve
   Sullivan (sullivan@mathcom.com) does not report these problems when
   he went through this effort.

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

BLAS
====

Change BLAS/SRC/makefile as follows:

160c160,163
<       $(FORTRAN) $(OPTS) -c $*.f
---
> #     $(FORTRAN) $(OPTS) -c $*.f
>       f2c $<
>       gcc -c -O6 $*.c
>       rm $*.c

f2c chokes on BLAS/SRC/zrotg.f for reasons beyond my humble (FORTRAN
hating) FORTRAN capabilities so I just looked at crotg.f and made the
following hack. There are no level 1 BLAS tests in the lapack
distribution so who knows? You have been warned :-)

zrotg.f
13,14c13,16
<          norm = scale*dsqrt((cdabs(ca/dcmplx(scale,0.0d0)))**2 +
<      *                      (cdabs(cb/dcmplx(scale,0.0d0)))**2)
---
> c         norm = scale*dsqrt((cdabs(ca/dcmplx(scale,0.0d0)))**2 +
> c     *                      (cdabs(cb/dcmplx(scale,0.0d0)))**2)
>          norm = scale*dsqrt((cdabs(ca))**2/scale**2 +
>      *                      (cdabs(cb))**2/scale**2)


then just do a make in the BLAS/SRC directory. If you are only going
to use single, double complex or complex16, do a "make single complex"
or whatever.

BLAS testing:
============
Change the TESTING/makeblat2 as follows:

3c3
< LOADER   = f77
---
> LOADER   = gcc
5c5
< BLAS     = ../../blas.a 
---
> BLAS     = ../../blas.a -lf2c -lm 
83c83,88
<       $(FORTRAN) $(OPTS) -c $*.f
---
> #     $(FORTRAN) $(OPTS) -c $*.f
>       f2c $<
>       gcc -c -O6 $*.c
>       rm $*.c
> 
> 

Do the following changes for TESTING/makeblat3:

3c3
< LOADER   = f77
---
> LOADER   = gcc
5c5
< BLAS     = ../../blas.a 
---
> BLAS     = ../../blas.a -lf2c -lm 
83c83,86
<       $(FORTRAN) $(OPTS) -c $*.f
---
> #     $(FORTRAN) $(OPTS) -c $*.f
>       f2c $<
>       gcc -c -O6 $*.c
>       rm $*.c

Do the following makes from the BLAS/TESTING directory:

make -f makeblat2
make -f makeblat2

This compiles without error or warning 

All the BLAS tests run fine except xblat2z. The xblat2z test chokes
with a SEGMENTATION error that I have not tracked down. Any takers or
suggestions would be welcome.



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

Ok, so you got this far. You can now try to compile LAPACK.

Go to the SRC/ directory and change makefile as follows:


270c270,274
<       $(FORTRAN) $(NOOPT) -c $<
---
> #     $(FORTRAN) $(NOOPT) -c $<
>       f2c $<
>       gcc -c  $*.c
>       rm $*.c
> 
272c276,279
<       $(FORTRAN) $(NOOPT) -c $<
---
> #     $(FORTRAN) $(NOOPT) -c $<
>       f2c $<
>       gcc -c $*.c
>       rm $*.c
275c282,286
<       $(FORTRAN) $(OPTS) -c $<
---
> #     $(FORTRAN) $(OPTS) -c $<
>       f2c $<
>       gcc -c -O6 $*.c
>       rm $*.c
> 

I don't know why the powers that be decided to compile slamch.f and
dlamch.f with the optimizer switched off but I did what they did and
asked no questions.

The lapack libraries should compile without error. You can stop here
if you do not want to do any testing.

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

Testing LAPACK.

I only managed to get the single precision linear test routine to
compile and run. It passed all its tests. the double precision ran
fine for a while and then died with a segmentation error. The remaining
tests failed to compile (f2c spews chunks again!). I gave up and dit not
try the egen analysis tests. Maybe I will try again if I can get f2c
updated.


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

LAPACK++

I have successfully compiled all of the library. There seems to be
a problem with the diagonal matrix class tests and gcc 2.4.5 suffers an 
internal compiler error on the linear analysis test routines for symmetrical
matrices. I will try this again when I finally get a big enough hard drive 
to compile gcc 2.5.?.

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









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

From: dwex@aib.com (David E. Wexelblat)
Subject: Re: Xconfig
Date: Fri, 10 Dec 1993 04:00:14 GMT

In article <2e1mk4$31s@pianosa.to.sem.it> paolo@to.sem.it (Paolo Zeppegno) writes:
>There was one intelligent proposal some time ago, about writing a dos program
>that using the bios would print the right clock values. I don't know what
>happened about it. I seem to rememember that David Wexelblatt objected
>that it wouldn't be legal??? to use such a program to help in setting up
>the right clock entries.
>       paolo zeppegno
>
>P.S. read my lips, no changes to XFree86 required, here.
>-- 
>Dr. Paolo Zeppegno                             email:  paolo@to.sem.it
>Systems and Management S.p.A.                          zeppegno@relay.iunet.it
>Via Alfieri 19                                 phone:  +39-11-561-2323
>10121 Torino ITALY                             fax:    +39-11-557-6304

David Wexelblat (one 't', please - two 't's is someone else) certainly
has NOT objected to writing a program that reads the mode settings after
a BIOS mode has been entered.  This is what I have been ADVOCATING for
quite a while.  I finally have the facilities to write such a program;
now, I lack the time.  So I can't do it.

What I object to is people DISASSEMBLING the BIOS to figure out how it
does its job.  I find reverse-engineering ethically questionable at
best.  Its legality it many jurisdictions is questionable as well.

I see a whole world of difference between forward engineering
(e.g. looking at values in registers and deriving information from
them) and reverse engineering (e.g. disassembling the BIOS so you can
figure out how someone else did the job).  Others do not agree with
me; ethics are always a touchy subject, and more so in freeware than
in commercial software.

--
David Wexelblat <dwex@aib.com>  (703) 430-9247  Fax: (703) 450-4560
AIB Software, Inc., 46030 Manekin Plaza, Suite 160, Dulles, VA  20166
  Formerly Virtual Technologies, Inc.

Mail regarding XFree86 should be sent to <xfree86@physics.su.oz.au>

"...Laughing as they danced, highest colours touching others.
   Did her eyes at the turn of the century tell me plainly
     How we'll meet, how we'll love?  Oh, let life so transform me."
        -- Yes, "Turn of the Century"

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

From: kevins@aragorn.ori.org (Kevin Smolkowski)
Subject: where should I tell ups to turn off power?
Date: 10 Dec 1993 06:06:44 GMT


Maybe this is one of those questions that really has no "right"
answer.  I have a older ups (not a new intelligent one) that
drives a RS-232 line high when the power goes off.  I wrote
my own little program (based on powerd but I use different 
control lines) that shut down the system all right using
shutdown when I lose power.

Now I want to shut off my ups after my system is safely shutdown
by driving another line high, easy to do, but where should I do it. 

I was thinking of two places.  

In its own program called by /etc/brc.  But then halt will never
finish as the power will be shut off before /etc/brc returns.  
I guess this would be ok.

Or should I change halt so that it sends the signal?  This
seems kinda ugly.

-Kevins


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

From: paeth@cs.tu-berlin.de (Carsten Paeth)
Subject: searching for mailing-list redirect to local newsgroup via procmail
Date: 10 Dec 1993 07:20:11 GMT

Sorry, perhaps this is the wrong newsgroup, but do YOU know all ?

I'm running linux at my home machine.

I have written a ppp-driver for connection to my friends site
(in the same room)

but that's not the problem (everything working fine).

I get an mail+news connection via in-berlin.de in the next time.

I'm reading KERNEL, NET and PPP channel of the linux comunity.

I installed for mail+news processing
inn-1.4
mailx-5.3b
mm-2.6 (MIME)
elm-2.4pl22
procmail-2.90
taylor-uucp-1.04
smail-3.1.28
btoa,xv,pbmplus,uu-utils

to get my news+mail system running.
everything working fine, but ...

I want to redirect my mailing-list response to
a local newsgroup, and handle it like a newsgroup.

I the mom.. I can't reply easily to mailing-list
cause of inews add a new header.

my ..procmailrc is:
====================================================
:0
* ^From: owner-linux-activists@joker.cs.hut.fi
* ^X-Mn-Key: NET
|formail +1 -fr -s inews -h -n calle.linux.net-channel

:0
* ^From: owner-linux-activists@joker.cs.hut.fi
* ^X-Mn-Key: KERNEL
|formail +1 -fr -s inews -h -n calle.linux.kernel-channel

:0
* ^X-Mn-Key: PPP
|formail +1 -fr -s inews -h -n calle.linux.ppp-channel
========================================================

perhaps you can't help me, but you have any pointers or other hints

Please relpy by email (newsgroups are overcrowded and I don't have time
to read them all)
to paeth@cs.tu-berlin.de !

In Future you can reach me at calle@calle-in.berlin.de

Thanks for not skipping this news.

calle.





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

From: rene@renux.frmug.fr.net (Rene COUGNENC)
Subject: Re: (none)
Date: 10 Dec 1993 00:30:58 GMT

Ce brave Theodore Ts'o ecrit:

> well, I've finally taken the time to package them all out and release a
> new patch set.  I'd appreciate it if people could try them out.  They
> can be found on tsx-11.mit.edu, in /pub/linux/ALPHA/serial.  

> Please try these changes out, especially if you support dialup via
> modems.  There are a bunch of tricky race conditions with the hangup
> code, which I *think* that I've resolved.  I want to make sure that
> they work, though, before submitting them to Linux for inclusion in

Well, I tried them, they seem to solve some problems, but now I am currently
recompiling my kernel whithout them, just to avoid what happens now...
Read on and I hope this will help !


The dialup  line is  device 4/65
The dialout line is  device 5/65
The UART is a 16450, the computer a 386/25 8mb ram 8mb swap.

Most of the traffic is sending megabytes of Linux to the users, and
receiving them via uucp, or getting news.

First, all seemed to be OK. The first user of this new kernel logged in,
and the console scrolled whith a lot of "tty65: input overrun" messages.

After that, cron started an uucp call to get news... And a few minutes
later:
        Dec  9 20:21:56 renux vmunix: tty65: input overrun
        Dec  9 20:21:57 renux last message repeated 169 times
        Dec  9 20:21:57 renux vmunix: tty65
        Dec  9 20:21:57 renux vmunix: : input overrun
        Dec  9 20:21:57 renux vmunix: : input overrun
        Dec  9 20:21:57 renux vmunix: tty65: input overrun
        Dec  9 20:22:01 renux last message repeated 351 times

Then the machine crashed.

I MAY have a flow-control problem, but I don't think so; everything has been
plugged for about two years and use to work well, and CRTSCTS is ok whith
Linux...

Anyway, I commented out the printk("input overrun") in tty_io.c, to avoid
losing CPU time printing so many lines.

Everything works, except the following problems (which do NOT happen all
the time):

A user connects, the modem rise the CD line, and immediately:

Oops: 0000
EIP: 0010:00165f58
EFLAGS: 00010046
eax: 00000000      ebx: 00192b0c    ecx: 00000001  edx: 000002fe
esi: 005c1000      edi: 000000b0    ebp: 005c14ec
ds: 0018     es: 0018   fs: 002b   gs:002b
Pid: 1, process nr: 1

83 78 08 00 7d 3d f6 46 0c 02

   This gives in my kernel some place around the rs_interrupt() routine:

00165aec t serial.o
00165b0c t _rs_start
00165b2c t _rs_probe
00165b4c t _rs_interrupt
001660a8 t _do_softint
001661a8 t _rs_timer



Next time, the machine was freshly rebooted, and I switched the modem ON:



Unable to handle kernal paging request at address c0000009

Oops: 0000

EIP: 0010:00165f0e
EFLAGS: 00010002
eax: 00000000      ebx: 00192b0c    ecx: 00000004  edx: 000002fe
esi: 00000000      edi: 0000000f    ebp: 0008e4ec 
ds: 0018     es: 0018   fs: 002b   gs:002b
Pid: 0, process nr: 0

f6 40 09 08 75 3f 89 fA 84 d2

task[0] (swapper) killed. unable to recover.
Kernel panic, etc...

00165b4c t _rs_interrupt
001660a8 t _do_softint



It seems that there are more problems after a dialout occured: For now,
5 users logged in and downloaded whith zmodem since the last reboot,
apparently whithout problems. 

The kernel is compiled whith GCC 2.5.6, version compiled by myself.
The previous kernel, without patches, is also compiled whith gcc 2.5.6 and
never crash. (except sometimes in SLIP, but this is another story :-) )


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

There is another problem, since about linux pl12, that these patches seems
to cure, or at least to minimize:

I have modified my getty that way:

        if ((mytest=open(tty, O_RDWR, 0)) != 0)
        {
           char buf[BUFSIZ];
                sprintf(buf,"GETTY, open returns %d and errno is %d",mytest,errno);
                error("/dev/%s: %s", tty, buf);
                /*****
                error("/dev/%s: cannot open as standard input: %m", tty);
                *****/
        }

( Don't tell me to use SuperBogoGettyTurbo, this is for another thread :-) )

        I repeat for the one I see pressing the (F)ollup-up key:

( Don't tell me to use SuperBogoGettyTurbo, this is for another thread :-) )

When waiting for a connection, the open() blocks, this is the correct
behaviour, and life is beautiful.

When someone connects, the device unlocks the open call, this is the correct
behaviour too... But look what getty get at this time:

Dec  2 20:45:18 renux /etc/getty[3278]: /dev/ttys1: GETTY, open returns -1 and errno is 513

Yes, errno = 513. I like what the include file says :-))

        /* Should never be seen by user programs */
        #define ERESTARTNOINTR  513


The vanilla getty ( agetty from alt.sources, the one grabbed by Peter-poe@daimi
when Linux  had no login program... ) tries to display sys_errlist[513] and
fatally makes a core dump in /dev.


This problem happens every time after a dialout call on the corresponding
callout device. With the new patches, it seems to  happen less frequently.
(When the computer does not hang :-) )


Well, I hope all that will help !

--
 linux linux linux linux -[ cougnenc@renux.frmug.fr.net ]- linux linux linux 

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

From: cykao@math.nthu.edu.tw (Kao Chen-Yi)
Subject: Other site to get libc-4.4.4.zip?
Date: Fri, 10 Dec 1993 08:54:03 GMT


I need to upgrade library with libc-4.4.4.zip. It is very hard for me to
connect with sunsite.unc.ed. So does anyone knows the nearer site support
libc-4.4.4.zip. Also, inc-4.4.4.zip and image-4.4.4.zip are needed. Could
somebody give me a list that I can get these files.

Second, is pl14 support D-Link DE2** series ethernet card? I got the error messages as
follow:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
SIOCSIFADDR: Invalid argument
SIOCGIFFLAGS: Invalid argument
SIOCSIFFLAGS: Invalid argument
SIOCSIFNETMASK: Invalid argument
Usage: ifconfig [-av] interface [address | up | down |
       metric NN | mtu NN | arp | -arp | trailers |
       -trailers | broadcast aa.bb.cc.dd |
       dstaddr aa.bb.cc.dd | netmask aa.bb.cc.dd |
       pointopoint aa.bb.cc.dd ... ]
SIOCADDRT: Network is unreachable
SIOCADDRT: Network is unreachable
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
        Here is my rc.inet1
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
#! /bin/sh
#
# rc.inet1      This shell script boots up the base INET system.
#
# Version:      @(#)/etc/rc.d/rc.inet1  1.01    05/27/93
#
# Author:       Fred N. van Kempen, <waltje@uwalt.nl.mugnet.org>
#

  HOSTNAME=`/bin/hostname`

  # Attach the loopback device.
  /etc/ifconfig lo 127.0.0.1

  # Set up the Ethernet connection(s).
  IPADDR="140.114.32.238"
  NETMASK="255.255.255.0"
  NETWORK="140.114.32.0"
  BROCAST="140.114.32.355"
  GATEWAY="140.114.32.254"
  /etc/ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
  #/etc/ifconfig eth0  netmask 255.255.254.0 broadcast 140.114.32.255

  # Set up the primary (static) routes.
  #/etc/route add microwalt
  /etc/route add 127.0.0.1
  /etc/route add ${NETWORK}
  /etc/route add default gw ${GATEWAY} metric 1

  # All done.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

        Hope someone could solve my problem.

Johnathan Kao
1993-12-10
cykao@math.nthu.edu.tw

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

From: floyd@arthax.satlink.net (Christian Pablo Tagtachian)
Subject: Re: Neuronal networks
Date: Thu, 9 Dec 1993 22:12:34 GMT

Christian Wehrfritz (sz0166@cd4680fs.rrze.uni-erlangen.de) wrote:
: bcr@bohr.physics.purdue.edu (Bill C. Riemers) writes:

: The best Network Simulator is SNNS, you can get it at
: ftp.informatik.uni-stuttgart.de in pub/SNNS/.
: There's a graphical user interface for X and many learning functions.
: But maybe this belongs to comp.ai.neural-nets...
: Christian

May be it does... but since I can only get to a few newsgroups and I want to 
run it on a Linux system...., this was my only choice. 
I am in Argentina, many things are not in my grasp.
However I thank you very much all the replies.
Does anyone know how to get there through mail? 
Thanks 
Christian

<floyd@arthax.satlink.net> Buenos Aires, Argentina.

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


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