Subject: Linux-Development Digest #904
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:     Sun, 10 Jul 94 17:13:05 EDT

Linux-Development Digest #904, Volume #1         Sun, 10 Jul 94 17:13:05 EDT

Contents:
  utmp / wtmp handling (David Dyer-Bennet)
  Re: TCP/IP networking for DOSEMU (Byron A Jeff)
  Re: TCP/IP networking for DOSEMU (Mark Evans)
  Re: TCP/IP networking for DOSEMU (Mark Evans)
  Re: 1.1.26 breaks dialout serial device (Rene COUGNENC)
  Swapping problems with VL-300 (aha152x driver) VLB SCSI controller (was: Re: Dedicated SCSI swap drive?) (Craig Sanders)
  Re: Linux seems to perform terribly for large directories (Dan Pop)
  Re: Xconfig builder (Paul Sitz)
  Truedox mousc/trackball drivr? (Bill Broadley)
  Xfree86 2.2.1 -- No XIM ? (Jinwoo Shin)
  Problem with swap - UMSDOS/Net conflict? (Chris Adams)
  ?: free MOTIF clone ? (Steffen W. Schilke)
  Re: How to know the patch level (Ronald Kuehn)
  Re: List of programs which need shadow changes (David Holland)

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

From: ddb@terrabit.mn.org (David Dyer-Bennet)
Subject: utmp / wtmp handling
Date: Sat, 9 Jul 1994 06:08:29 GMT

utmp.h refers to a number of functions, none of which seem to exist --
at least I can't find them by grepping my kernel source tree or
looking in the map produced by my last kernel build.  There also
aren't man pages for them.  Do these functions exist in Linux?  Where
can I find some information about them?

Related to this -- I know utmp and wtmp aren't really unique to Linux,
but they aren't described in my Posix book, either.  Can somebody
point me to Linux-specific doc on them, or at least tell me which Unix
variant they came from so I can go look them up there?

-- 
David Dyer-Bennet, proprietor, The Terraboard    4242 Minnehaha Ave. S.
ddb@network.com, ddb@terrabit.mn.org              Minneapolis, MN 55406
Don't waste your time arguing about allocating          +1-612-721-8800
blame; there'll be enough to go around.             Fax +1-612-724-3314

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

From: byron@cc.gatech.edu (Byron A Jeff)
Subject: Re: TCP/IP networking for DOSEMU
Date: 8 Jul 1994 21:52:32 -0400

In article <CsMy92.Ln@aston.ac.uk>,
Mark Evans <evansmp@mb52112.aston.ac.uk> wrote:
:Rob Janssen (rob@pe1chl.ampr.org) wrote:
:
:: The trouble is that Linux networking will be making responses to some of
:: the packets that are really destined for the dosemu box, because the TCP/IP
:: protocol specifications tell it to.  This is mostly solved by running a
:: different IP address in the dosemu box than the Linux networking uses, but
:: subtle problems remain.  (e.g. forwarding has to be turned off in both
:: the Linux networking and the software running in the dosemu box)
:
:Allocating a virtual host for a dosemu session is rather trickier for IP
:than for IPX. The problem is to do with the addressing differences between
:the two protocols. (Remember that you can have an *arbitary* number of
:dosemu sessions running.) For IPX you can have your machine regarded as
:a network (it's IP address is a possible choice for the IPX network number),
:then you use the pid as being the node number. For IP how do you do this?

This is why I originally proposed setting up all the DOSEMU sessions in
a virtual network and having Linux route packets between the outside world
and the virtual DOSEMU network interfaces.

All the elements to do this are available:

- Linux can already route between networks.
- The loopback driver already has conecptualized the virtual network interface.
- DOSEMU already has a packet driver interface.

THe only drawback that has been pointed out is that we'll actually be emulating
the TCP/IP protocol stack (Like WATTCP or Trumpet) when in fact Linux already
has a far superior TCP/IP stack. But that's the price you pay to emulate DOS
software.

Comments?

BAJ
-- 
Another random extraction from the mental bit stream of...
Byron A. Jeff - PhD student operating in parallel - And Using Linux!
Georgia Tech, Atlanta GA 30332   Internet: byron@cc.gatech.edu

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

From: evansmp@mb52112.aston.ac.uk (Mark Evans)
Subject: Re: TCP/IP networking for DOSEMU
Date: Fri, 8 Jul 1994 18:57:48 GMT

Richard M. Warner (rick@sjsumcs.sjsu.edu) wrote:

: Unfortunately, it is also false (in part).  Because Netware can run
: over IP (Netware/IP) and in that configuration you can still run
: Netware and 'regular' TCP/IP on a single NIC; with this 
: configuration I could, in a multitasking environment (e.g., DV/X),
: run Netware applications and TCP/IP applications (Telnet, FTP,
: Mosaic, Gopher, etc.) all using IP and all running concurrently.
: So much for the different protocol theory.

: The correct answer is that the higher level manager (ODI in Netware's
: case, NDIS for others) has the ability to manage multiple sessions/
: protocols/framings on a single card.  I am not sure about the internals of 
: NDIS, but the ODI drivers make the single board look like multiple 
: virtual boards. The functionality missing in Linux is this higher level 
: network manager - someone creates one for Linux and then the NIC will be 
: able to handle multiple concurrent network sessions over one, or many, 
: protocol stacks.

I think you are forgetting that IP will quite happily multiplex protocols.

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

From: evansmp@mb52112.aston.ac.uk (Mark Evans)
Subject: Re: TCP/IP networking for DOSEMU
Date: Fri, 8 Jul 1994 19:03:01 GMT

Rob Janssen (rob@pe1chl.ampr.org) wrote:

: The trouble is that Linux networking will be making responses to some of
: the packets that are really destined for the dosemu box, because the TCP/IP
: protocol specifications tell it to.  This is mostly solved by running a
: different IP address in the dosemu box than the Linux networking uses, but
: subtle problems remain.  (e.g. forwarding has to be turned off in both
: the Linux networking and the software running in the dosemu box)

Allocating a virtual host for a dosemu session is rather trickier for IP
than for IPX. The problem is to do with the addressing differences between
the two protocols. (Remember that you can have an *arbitary* number of
dosemu sessions running.) For IPX you can have your machine regarded as
a network (it's IP address is a possible choice for the IPX network number),
then you use the pid as being the node number. For IP how do you do this?

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

From: rene@renux.frmug.fr.net (Rene COUGNENC)
Subject: Re: 1.1.26 breaks dialout serial device
Date: 9 Jul 1994 23:54:45 GMT
Reply-To: cougnenc@blaise.ibp.fr (Rene COUGNENC)

Ce brave Rene COUGNENC ecrit:


> Serial devices seems broken in 1.1.26; 
(and in 1.1.27)

The problem seems to be in the last patch against tty_io.c in patch26:

@@ -836,19 +840,19 @@
                        (*driver->other->refcount)++;
                        if (o_tty->ldisc.open) {
                                retval = (o_tty->ldisc.open)(o_tty);
-                               if (retval < 0)
+                               if (retval < 0) {
+

(etc...)

If I remove it, everything is fine. (I tried each patch against this
file separately).
--
 linux linux linux linux -[ cougnenc@renux.frmug.fr.net ]- linux linux linux 

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

From: cas@muffin.apana.org.au (Craig Sanders)
Subject: Swapping problems with VL-300 (aha152x driver) VLB SCSI controller (was: Re: Dedicated SCSI swap drive?)
Date: Sun, 10 Jul 1994 05:01:51 GMT

Adrian_Savage.sbd-e@rx.xerox.com (Adrian Savage) writes:

>Naresh Sharma (nash@dutllu4.gmd.de) wrote:
>>> Hans-Christoph Rohland (hrohlan@gwdg.de) wrote:

>>> : I am using a 16MB swap on a Quantum 240 connected via Adaptec 1542 since
>>> : January and never had any problems with Kernels 0.99.15, 1.0.0 and 1.1.3...
>>> : Actually I never heard about such probs before. I would like to know if
>>> : there are more people experiencing failures of swap with scsi.

>>> The bug is not seen in the 1542 code, and 1542 does not exercise it.
>>> Adapter cards of other makes e.g. future domain (used to ?) exercise this
>>> bug.

> I'm using a fdomain 1680 and am unable to use a SCSI partition as
> swap - as soon as swapping starts, the system locks up within about 2
> minutes.  This is with kernel versions 1.0.6, 1.1.13 and 1.1.24.

> My solution was to get a cheap IDE drive and use that as a swap
> device, which is a shame as my SCSI drive is 4 times faster both for
> access time and data transfer :-(

I have a similar problem with swapping on SCSI disk.


Here's what I've got:

486-SX-33, 8MB Ram, Ocean "DCA cache" motherboard, 3 local bus slots.

VL-300 (aha-1522 clone) local bus SCSI card.

Everything except for the SCSI port is disabled, including the SCSI
BIOS.  Port 0x140, IRQ 11, SCSI ID 7.  This card is in the first VLB
Master slot.  I've also tried it in an ISA bus slot with the same
results.


aha152x: processing commandline: ok
detection complete
aha152x: vital data: PORTBASE=0x140, IRQ=11, SCSI ID=7, reconnect=disabled, parity=enabled
scsi0 : Adaptec 152x SCSI driver; $Revision: 1.0 $
scsi : 1 hosts.
  Vendor: MAXTOR    Model: XT-4380S          Rev: B3D1
  Type:   Direct-Access                      ANSI SCSI revision: 01 CCS
Detected scsi disk sda at scsi0, id 0, lun 0
  Vendor: MATSHITA  Model: CD-ROM CR-5XX     Rev: 1.0c
  Type:   CD-ROM                             ANSI SCSI revision: 01 CCS
Detected scsi CD-ROM sr0 at scsi0, id 2, lun 0
  Vendor: ARCHIVE   Model: VIPER 150  20000  Rev: -000
  Type:   Sequential-Access                  ANSI SCSI revision: 01
Detected scsi tape st0 at scsi0, id 6, lun 0
scsi : detected 1 SCSI disk 1 tape 1 CD-ROM drive total.
Scd sectorsize = 2048 bytes


The MATSHITA CD-ROM is a Panasonic 501B single speed drive.  I also have
some problems with this - listing the contents of many .tar.gz files on
my Feb Infomagic Linux CD (especially tar files over 300K) often dies
halfway through - tar reports that the archive is corrupted or that it
has ended unexpectedly.  If i copy the file to, say, /tmp first and
then examine it it still occurs.  This implies that either a) the files
are corrupted in the first place (i don't think so because it is not
100% consistent as to which files have the errors) or b) there is a
serious cd-rom read problem with either my 501B CD drive, or the vl-300
controller card, or the aha152x driver.


WD-1007 ESDI controller
        Priam 638 ESDI disk
        1.2MB floppy is also being run off this card

   The ESDI disk just crapped out so I'll be getting rid of this soon,
   and enabling the BIOS and the floppy port on the VL-300.  At the
   moment I can still boot off the ESDI disk [if i jiggle it around a
   bit when it gets a read error, it eventually manages to read the
   data], but it is basically unusable for anything but simply booting.

I use the following line in my lilo configuration:

        append = "aha152x=320,11,7,0"


Here's the symptoms:

        Swapping on the SCSI disk actually works perfectly well UNLESS I am
        reading or writing from the Viper tape drive.  When the kernel tries
        to swap stuff back from disk into RAM, it can't do it (presumably
        because the tape operation "locks" the SCSI bus), panics, and dies.

        Until my ESDI drive died the other day, I just used the Maxtor SCSI
        disk for storage/programs, and the ESDI for booting and for swap.  I
        can't do this any more, so now I have to swap to /dev/sda5.  I've
        modified my tape-backup scripts so that they do a 'swapoff -a'
        before any tape operation, and a 'swapon -a' as soon as it has
        finished.


So, my question is:

        Is this a generic scsi under linux problem, or is it a problem
        with the adaptec 152x driver, or a problem with the VL-300
        controller card?



BTW, does anyone have any good info on whether I'm better off using a
partition on my medium-speed Maxtor XT4380 disk, or a partition on a
really slow (28ms) Seagate 125-N SCSI disk I was just given?  I suspect
that performance would be roughly equivalent - I'm trying to decide
whether to use the Seagate for swap space or as a dumping ground for
stuff I've ftp-ed off the net...




-- 
cas@muffin.apana.org.au

        "I am not now, nor have I ever been an American"
                                            --  kfelsche@metz.une.edu.au

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

From: danpop@cernapo.cern.ch (Dan Pop)
Subject: Re: Linux seems to perform terribly for large directories
Date: Sun, 10 Jul 1994 12:07:29 GMT

In <CsnzxL.DEn@pe1chl.ampr.org> rob@pe1chl.ampr.org (Rob Janssen) writes:

>In <1994Jul5.090612.139@dutch.eng.ox.ac.uk> tpfpdt@eng.ox.ac.uk writes:
>
>>Good point.  Yes, ls is much faster than ls -F.  Does this mean that file
>>type data is not cached along with the filename?  Maybe it should be, I find
>>the -F flag really useful.
>
>File type data is not *stored* along with the filename.

And there are very good reasons for this. Think about hard links.
Directory entries are directory entries and inodes are inodes.

Before suggesting "improvements", it's better to understand why things
are the way they are.

Dan
--
Dan Pop 
CERN, CN Division
Email: danpop@cernapo.cern.ch
Mail:  CERN - PPE, Bat. 31 R-004, CH-1211 Geneve 23, Switzerland

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

From: psitz@empros.com (Paul Sitz)
Subject: Re: Xconfig builder
Date: Sun, 10 Jul 1994 16:18:50 GMT

Elaine Walton (ewalton@magnus.acs.ohio-state.edu) wrote:
: I recently completed updating my ModesDB timings generator.  Now it makes
: an Xconfig.  I have tested it on 256-color SVGA; it needs testing on 16-
: and 2-color VGAs.  It does not work yet on excelerators (like S3, etc.).
: I would like to have a few more volunteers who would like to test this
: tool.
: Please email me if interested.
: -Sean Walton

I would be willing to give it a try on an Orchid Fahrenheit 1280+

--
Paul Sitz                                                          
Empros                             Facility Code:  PLY067
2300 Berkshire Lane North          email:          psitz@empros.com
Plymouth, MN  55441-3694           screammail:     (612) 553-4516


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

From: broadley@neurocog.lrdc.pitt.edu (Bill Broadley)
Subject: Truedox mousc/trackball drivr?
Date: 10 Jul 1994 19:29:23 GMT

I bought a nice trackball for $15 or so.  TrueDox trackball with 3 buttons.

It works as an MS compatible mouse but of course I only get to use
two buttons.

I'd be happy to write a driver for it, but the middle button produces
no output.  I.e. if I do a od -x < /dev/mouse.

Any ideas?

I probably have to send the mouse something to put it into another mode?

Any ideas?

Any help appreciated?  Anyone else with similiar experiences?

--
Bill                    Broadley@neurocog.lrdc.pitt.edu 
Linux is great.         Bike to live, live to bike.                      PGP-ok

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

From: jwshin@nitride.EECS.Berkeley.EDU (Jinwoo Shin)
Crossposted-To: comp.os.linux.misc,comp.os.linux.help
Subject: Xfree86 2.2.1 -- No XIM ?
Date: 10 Jul 94 17:31:35 GMT

Why is input method extentions being left out in XFree86 ??? Is there some
internal difficulties that prevents it from being included? I'm in the process
of developing some foreign language editor (Korean and Japanese) and input
method would help me out a lot. Does XFree86 3.0beta include this? If so,
can I grab a copy of it, for I'm in very urgent need of one.

-- 
Jinwoo Shin                             jwshin@eecs.berkeley.edu
System Administrator                    
Berkeley Sensor and Actuator Center

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

From: racerx@vespucci.iquest.com (Chris Adams)
Crossposted-To: comp.os.linux.help
Subject: Problem with swap - UMSDOS/Net conflict?
Date: 10 Jul 1994 13:12:06 -0500

I have a problem that I think is some kind of conflict between UMSDOS
and the Networking parts of the kernel.  It appears to be some kind of
problem with having swapspace on a UMSDOS drive.  I first had problems
when I installed Slackware 2.0 with UMSDOS on my drive.  When I tried to
recompile my kernel, I kept getting errors from the compiler while
trying to read header files.  I could get the problem to go away by
doing a swapoff and swapon, but it would eventually happen again.  When
I compiled a kernel on another machine without the Networking stuff, it
worked fine.  But as soon as I compiled in the Networking stuff, it
happened again.  By the way, the kernel installed originally with
Slackware was 1.0.9, and the kernel I compiled was 1.1.26.  Both had the
same problems.
-- 
Chris Adams
racerx@iquest.com
United States Space Academy Simulations Director and Trainer
"With friends like these, who needs halucinations?" - Buddy, 'Night Court'

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

Crossposted-To: comp.os.linux.misc,comp.os.linux.help
From: sws@tora.RoBIN.de (Steffen W. Schilke)
Subject: ?: free MOTIF clone ?
Date: Sun, 10 Jul 1994 09:28:26 GMT

Hi,

I onces heard something about a free (share/PD/free-ware) MOTIF or a
project which is working on something like that.

Is there something like that (or at least planned) ?


ThanX   steffen


--
[Standard Disclaimer] in addition I would like to speak with my lawyer ....
S. Schilke; PoBox 1213; 61102 Bad Vilbel; Germany  a.k.a  sws@tora.RoBIN.de
                  Sokonoke Sokonoke tora-sama ga touru
$@%9%F%U%'%s(J  $@CN2H!Z%7%k%1![(J  $@$=$3$N$1$=$3$N$18WMM$,DL$k(J
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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

From: Ronald Kuehn <Kuehn@rz.tu-clausthal.de>
Subject: Re: How to know the patch level
Date: Sun, 10 Jul 1994 19:13:28 GMT

Yavuz Onder (yavuz@bnr.ca) wrote:
> I want to know what patch level of 1.0 I am running. I tried "uname"
> it only tels me it is "1.0".

> Is there a place in source distribution, in header files or
> wherever else, I can extract this info?

Hi,
if uname -a tells you it is 1.0 then _it_is_ version 1.0.
( an other way to find it out: cat /proc/version )

Ciao,
 Ronald
--
Ronald Kuehn                                  e-mail: Kuehn@rz.tu-clausthal.de
>>>  To obtain PGP public key use 'finger inrk@asterix.rz.tu-clausthal.de' <<<

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

Subject: Re: List of programs which need shadow changes
From: dholland@husc7.harvard.edu (David Holland)
Date: 10 Jul 94 13:38:15


rob@pe1chl.ampr.org's message of Sat, 9 Jul 1994 08:44:22 GMT said:

 > >Why not come up with a standardized library interface, fix these
 > >programs once and for all, and use replacement dynamic libraries to
 > >get shadow passwords, Kerberos, s/key, and/or whatever other schemes
 > >come down the pipe?
 > 
 > Hmmm...  that was tried some time ago.  It was promised it would
 > not break anything, but there were severe performance problems and
 > it also caused other nasty problems.  (e.g. it left a file open
 > which could cause problems in programs that expected to be able to
 > open new stdin/stdout/stderr files)

That's because it wasn't done right. You can't try to cram it into
getpwent() and its related functions. You need a separate set of
functions for retrieving the password(s). Whatever it is has to be
sufficiently general to allow for multiple challenge/response pairs...
or conceivably none, in some cases.

Then, that list of programs would have to be converted to use the
library, but only once; that's much better than having to rework all
of them every time somebody dreams up a new authentication scheme.

If none of the commercial unix vendors have come up with an interface
of this sort, I propose we design our own and get it adopted.

--
   - David A. Holland          | "The right to be heard does not automatically
     dholland@husc.harvard.edu |  include the right to be taken seriously."

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


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