Subject: Linux-Development Digest #890
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, 5 Jul 94 20:13:06 EDT

Linux-Development Digest #890, Volume #1          Tue, 5 Jul 94 20:13:06 EDT

Contents:
  Re: TCP/IP networking for DOSEMU (Byron A Jeff)
  Re: dosemu and lost selection (Byron A Jeff)
  Re: e@mail of LinuX CDROM publisher wanted (Jon Saken)
  Re: Intel EtherExpress ethernet drivers in alpha ? (John Lellis)
  Re: Linux seems to perform terribly for large directories (Mark Lord)
  Re: Multicasting. (Alan Cox)
  HD floppy with 1600 kB, why not? (Bram Bouwens)
  ypserv has memory- lack (Joachim Landwehr)
  Re: CD Recorder Driver? ("Robert J Brashear")
  Re: tcsh bug: more information (Kjetil Torgrim Homme)
  Floppy drive errors with 1.1.23 (Bogdan Urma)
  Re: Floppy drive errors with 1.1.23 (Bogdan Urma)
  is sendmsg() system call supported yet under Linux? (Gautam Thaker)
  Re: 1.1.23 floppy driver broken on my notebook (Bogdan Urma)
  Re: HD floppy with 1600 kB, why not? (Uwe Bonnes)
  Re: Intel EtherExpress ethernet drivers in alpha ? (Austin Donnelly)

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

From: byron@gemini.cc.gatech.edu (Byron A Jeff)
Subject: Re: TCP/IP networking for DOSEMU
Date: 5 Jul 1994 13:10:40 GMT

In article <CsGJoG.2yD@pe1chl.ampr.org>, Rob Janssen <pe1chl@rabo.nl> wrote:
-In <1994Jul4.142703.11656@uk.ac.swan.pyr> iiitac@uk.ac.swan.pyr (Alan Cox) writes:
-
->In article <2v6gbk$p7q@solaria.cc.gatech.edu> byron@gemini.cc.gatech.edu (Byron A Jeff) writes:
->>Well consider this: If Linux and DOSEMU share the same Enet card for TCPIP
->>then essentially you're putting a network in a single box. Mui confusing
->>if you have the same IP for both.
-
->Much better would be to find the dos interrupt interface to one of the DOS
->tcp/ip packages, and make that work in DOSEMU as calls to the 'real' kernel
->TCP/IP linux side.

Still doesn't solve the routing problem. See below.

-
-I have digged up the "PC/TCP" kernel interface, but it seems like too much
-work to be worth the trouble for me.
-I will probably do some more work on the packet driver interface in DOSEMU
-so that you can at least access all the cards and loopback.  Of course you
-need different IP addresses for all the dosemu's.

Your solution sounds like multiple NIC's which solves part of the problem.
If you have a single DOSEMU session and 2 NIC's then running a packet
driver directly on the second NIC should work. 

But what I don't understand is how the single enet card is going to recognize
all of those DOSEMU IP's without some kind of routing involved?

It seems that DOSEMU already has a driver interface that connects to the
Linux Enet driver. All I was saying is by Virtualizing that interface
and having routing to that interface that both DOSEMU and Linux would be
happy with minimal impact.

Maybe someone can give a high level overview of how the current single NIC
DOSEMU interface works right now? So then I won't sound like I'm talking
out of my ear ;-)

My synopsis: Netware and TCP/IP can share a single NIC because they are 2 
different protocols. However Linux TCP/IP and DOSEMU TCP/IP on the same NIC
cannot use the same IP because it's impossible to tell to where packets to
that IP must go (since they are now both using exactly the same protocol). So 
to solve the problem:

- create virtual NICs and a virtual network for the DOSEMU sessions.
- have the Linux TCP/IP route code route packets from the real
  net into the virtual net. 
- The virtual NICs for DOSEMU would consist of a loopback interface for the 
  lower half and a packet driver interface for the upper half. 
- So to both the real net and the Linux box, the DOSEMU side would
  look like a separate network and each DOSEMU session would look like a new
  machine on the DOSEMU network.
- The DOSEMU packet driver will have a packet driver interface on the top end
  for DOS TCP/IP/applications to connect to.
- The bottom end of the packet driver will connect to the DOSEMU virutal NIC.
  
This way only one packet driver for DOSEMU need be written: the driver for
the virtual NIC. Linux takes care of the real NIC and routing to the virtual
NICs.

Question: routing works properly now right? What kernel/net package are
required for correct routing?

Tell me what you think.

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: byron@gemini.cc.gatech.edu (Byron A Jeff)
Subject: Re: dosemu and lost selection
Date: 5 Jul 1994 13:17:22 GMT

In article <CsGJv2.32n@pe1chl.ampr.org>, Rob Janssen <pe1chl@rabo.nl> wrote:
-In <1994Jul5.023606.2714@hal.depaul.edu> dmahle@falcon.depaul.edu (Dennis Mahle) writes:
-
->My Problem: When I boot linux, selection (vt cut/paste) works fine 
->until I run dosemu.  After a normal dosemu exit, via emuexit, I get
->no response from the mouse on a vt.  (Mouse works fine in X, though).
-
->If anyone has a workaround please share...
-
-Disable all serial/mouse support in dosemu and try again.
-Once you find what causes it, try to re-enable what you really need.

I've been thinking about a bizarre solution: Give DOSEMU it's own mouse.
Mice are cheap enough ($12US) that buying another one and attaching it to
a extra serial port may be a good idea. That way DOSEMU (which unfortunatly
doesn't play nice) can have mouse support while keeping selection and X
Windows (which do play nice together) happy.

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: saken@stsci.edu (Jon Saken)
Crossposted-To: comp.os.linux.misc,comp.os.linux.admin,de.comp.os.linux,comp.os.linux.help
Subject: Re: e@mail of LinuX CDROM publisher wanted
Date: 5 Jul 1994 12:59:30 GMT



   Here are a few I got when I posted a similiar question:

InfoMagic: orders@Infomagic.com

ReadMe and Index files for the current CD's may be found at:
        ftp.uu.net:/vendor/InfoMagic


Just Computers!: 
Internet Order E-Mail:  sales@justcomp.com
   Information E-Mail:  info@justcomp.com
                        Include word "help" on a single line in message

Universal CD-ROM (tm)
        1645 S. Bascom Ave., #7
        Campbell, CA 95008
        Phone/Fax: 
        (408)369-9818
        Email: alte@rahul.net



jon

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

From: lellis@dmccorp.com (John Lellis)
Subject: Re: Intel EtherExpress ethernet drivers in alpha ?
Date: 5 Jul 1994 14:27:03 GMT

Austin Donnelly (and1000@cus.cam.ac.uk) wrote:
: Can anyone point me in the direction of some kernel patches for Intel
: EtherExpress cards ?   I would quite like to test any alpha/beta code
: people have lying around... :)

EtherExpress support has been included in the kernels for quite some time
now.  Uncomment the line in config.in referencing the EtherExpress cards,
do a make config to select it and remake your kernel.  Works great here!

--

John Lellis (lellis@dmccorp.com)

--
... Our continuing mission: To seek out knowledge of C, to explore
strange UNIX commands, and to boldly code where no one has man page 4.




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

From: mlord@bnr.ca (Mark Lord)
Subject: Re: Linux seems to perform terribly for large directories
Date: 5 Jul 1994 14:29:22 GMT

In article <Cs76BL.2F2@research.canon.oz.au> luke@research.canon.oz.au writes:
>I have strong suspicion that Linux has a problem with large
>directories.  An early pointer to this, was that doing an `ls'
>on a directory with (say) 5000 files, took several minutes

Try using the '-f' option.  The large delay is probably due to the ls 
command trying to sort everything into alphabetical order before dumping it.

The linux ext2 filesystem seems more than adequately fast for directory
lookups.  My 'symlinks' utility seems pretty quick at traversing entire
filesystems on harddisk (ext2) or even on CD (iso9660), and does not 
suffer any long delays on directories of any size.  So whatever slowdown
you have observed is likely due to the 'ls' program, rather than linux.
-- 
mlord@bnr.ca    Mark Lord       BNR Ottawa,Canada       613-763-7482

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

From: iiitac@uk.ac.swan.pyr (Alan Cox)
Subject: Re: Multicasting.
Date: Tue, 5 Jul 1994 14:17:48 GMT

In article <2vbg70$aqk@louie.udel.edu> chavey@bambam.cis.udel.edu (Laurent Chavey) writes:
>What protocol standard are you planning to use for multicasting.
>Is any "video conferencing" support in the work ?
>
IP multicasting is the only real standard. The video conferencing tools use
an experimental stream protocol called RTP, normally run over UDP. Once
you have kernel multicasting the rest works, although you would need to add
videoblaster drivers and camera drivers and stuff for the full works.

Alan



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

From: d70@nikhef.nl (Bram Bouwens)
Subject: HD floppy with 1600 kB, why not?
Date: 5 Jul 94 15:52:06 GMT
Reply-To: d70@nikhefh.nikhef.nl (Bram Bouwens)

In the old days, when CP/M was kind of standard, most computers
could handle 800kB on a floppy. Then came DOS, and decided that
that was too much: 40 tracks was enough, and 9 sectors per track too.

But now we have a nice OS and nice hardware which can handle disk
formats up to 1600 kB (within specs), and we only put 1440 kB on
them. Why is that? Of course, to do so you should use 10 1024 byte
sectors per track instead of 18 x 512. Indeed, DOS will not be able
to read these; but who cares?
Actually, even those old CP/M machines could mix 128, 256, 512 and
1024 byte sector floppies (at least if you had a Heathkit :-).

So: anyone thought about this yet? Are there any problems that I
overlook here?

Bram
====================================================================
  Bram Bouwens <Bram.Bouwens@nikhef.nl>
  NIKHEF-H, National Institute for Nuclear and High-Energy Physics
====================================================================

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

From: joelan@intrepid.physik.Uni-Osnabrueck.DE (Joachim Landwehr)
Subject: ypserv has memory- lack
Date: 5 Jul 1994 08:29:36 GMT


Hi,

the NIS- Server crashed one machine several times. This is what ps -aux 
deliverd:

USER       PID %CPU %MEM SIZE  RSS TTY STAT START   TIME COMMAND
root         1  0.0  0.3   48   52 con S    10:39   0:15 init auto
root      3626  0.0  0.1   37   20 p 1 S    16:17   0:00 /sbin/agetty 38400 tt
root      3449  0.0  3.0  352  468 p 2 S    15:36   0:00 -bash
root        51  1.0 79.3 27580 12148 con S    10:40  14:43 ypserv
                         ^^^^^ ^^^^^

root        17  1.1  0.1    5   24 con S    10:40  15:51 /sbin/update
root        32  1.1  1.0   57  156 con S    10:40  16:28 /usr/sbin/syslogd
root        34  0.2  0.5   36   88 con S    10:40   3:59 /usr/sbin/klogd
root      5363  0.0  1.4   68  220 p 2 R    10:13   0:00 ps -axu
root        38  0.6  0.3   68   60 con S    10:40   9:20 /usr/sbin/inetd
root        40  0.0  0.0   68    0 con SW   10:40   0:00 (lpd)
root        48  0.0  0.0  104    0 con SW   10:40   0:00 (rpc.mountd)
root        46  0.0  0.0   60    0 con SW   10:40   0:00 (rpc.ugidd)
root      1906  0.0  0.0   37    0 p 3 SW   13:01   0:00 (agetty)
root      1728  0.0  0.0   37    0 p 4 SW   12:58   0:00 (agetty)
root        69  0.0  0.0   37    0 p 5 SW   10:40   0:00 (agetty)
root        70  0.0  0.0   37    0 p 6 SW   10:40   0:00 (agetty)
root      1620  0.0  0.0   12    0 con SW   12:56   0:00 (bdflush)

Does anyone know some fixes?

Greetings,
                Joachim

System: Kernel 1.1.16; ypserv-0.5;slackware 1.1.2 & 1.2.0 (net)
-- 
-- 

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

From: "Robert J Brashear" <brashear@MR.Net>
Subject: Re: CD Recorder Driver?
Date: Tue, 5 Jul 94 10:59:07 CST
Reply-To: <brashear@MR.NET>

On 1 Jul 1994 15:57:40 GMT, 
Randy Chapman  <chapmra@u.washington.edu> wrote:

>In article <STEFAN.94Jul1095743@pippi.tu-bs.de>,
>Stefan Markgraf <stefan@pippi.tu-bs.de> wrote:
>>>I have heard a rumour that there is a Phillips CD-R (recordable CD) driver
>>>for Linux.  Does anyone know anything about this driver?  Anyone actually
>>>been able to use the CD-R with linux?
>>Do you really believe you can convert a CD-ROM into a writable CD?
>>I think there was a warning that this driver is a virus 
>>which destroys the harddisk.
>
>Actually, that was a DOS based program for Chinon drives that offered to 
>convert a normal CD-ROM drive into a CD-R drive.
>
>Randy
>
>
I have seen that "DOS based program" described as either a Trojan or just 
a collection of files. It was called CD-IT!. We use the real program to 
make one-offs. You cannot make a reader into a burner (well, if you up the 
power to the laser, rearrange the optics,...I guess you could).

======================================================================
Robert J Brashear                            brashear@oneoff.com
Technical Services Manager                   76450.3557@compuserve.com
The One-Off CD Shop Minneapolis              74660.2625@compuserve.com
                                             612-374-4643 (voice)
                                             612-374-3901 (fax)

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

From: kjetilho@ifi.uio.no (Kjetil Torgrim Homme)
Subject: Re: tcsh bug: more information
Date: 5 Jul 1994 16:43:33 GMT

+--- Roth Mark Daniel:
| On the flip side, it's trivial to do string pattern matching under
| csh, whereas sh uses test for all it's expression evaluation, and is
| a bit limited.
| 

Nonsense. "test" isn't even a builtin in the original V7 shell, but
"case" is. Besides, "expr" is just as good a tool for expression
matching. If sh doesn't have good enough data manipulation for your
task, write (perhaps just parts of it) in awk or Perl.

(Okay, Bourne shell lacks modifiers amd arrays, but you can do a lot
of cool tricks with IFS and set :-)


Kjetil T.

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

From: bogdan@crl.com (Bogdan Urma)
Subject: Floppy drive errors with 1.1.23
Date: 28 Jun 1994 00:53:41 -0700

    After playing around with 1.1.23, I looked through my /usr/adm/messages
file and found A LOT of kernel errors involving /dev/fd0. It seems that
whenever I mount a floppy, the kernel reports some errors which appear
to be harmless but baffling! Here are some examples:

  kernel:  floppy: weird interrupt ignored (0)
  kernel:  Reset-floppy called
  kernel:  floppy: FIFO enabled

   The above happens when I mount an msdos disk (mount -t msdos /dev/fd0 
/mnt)

   When I tried to 'cat zImage>/dev/fd0'
                   'rdev......etc'

    I got many I/O errors in /usr/adm/messages. 

     The disks are fine and things are getting copied onto the disks OK, 
despite all these warnings, so I am really confused! 

Any ideas?

Thanks,
Bogdan Urma
bogdan@crl.com


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

From: bogdan@crl.com (Bogdan Urma)
Subject: Re: Floppy drive errors with 1.1.23
Date: 28 Jun 1994 01:13:21 -0700

Bogdan Urma (bogdan@crl.com) wrote:
:     After playing around with 1.1.23, I looked through my /usr/adm/messages
: file and found A LOT of kernel errors involving /dev/fd0. It seems that
: whenever I mount a floppy, the kernel reports some errors which appear
: to be harmless but baffling! Here are some examples:

:   kernel:  floppy: weird interrupt ignored (0)
:   kernel:  Reset-floppy called
:   kernel:  floppy: FIFO enabled

:    The above happens when I mount an msdos disk (mount -t msdos /dev/fd0 
: /mnt)

:    When I tried to 'cat zImage>/dev/fd0'
:                    'rdev......etc'

:     I got many I/O errors in /usr/adm/messages. 

:      The disks are fine and things are getting copied onto the disks OK, 
: despite all these warnings, so I am really confused! 

  WHOOPS!!!!! The disks are physically fine, but the stuff is NOT getting
copied on them ok. There are A LOT of I/O errors reported in /adm/messages,
and the drive light won't turn off! What is going on??

Bogdan
bogdan@crl.com


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

From: gthaker@polyphony.sw.stratus.com (Gautam Thaker)
Subject: is sendmsg() system call supported yet under Linux?
Date: 05 Jul 1994 18:17:29 GMT


I believe that sendmsg() system call is not support at least 
upto kernel version 1.1.13. 

Does anyone know when this might be supported?

Thanks.

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

From: bogdan@crl.com (Bogdan Urma)
Subject: Re: 1.1.23 floppy driver broken on my notebook
Date: 28 Jun 1994 13:08:30 -0700

Klaus Schneider (uk0q@rzstud1.rz.uni-karlsruhe.de) wrote:
: Andrew Gallatin (gallatin@duke.edu) wrote:
: : I just built & installed 1.1.23 and noticed that the floppy driver is
: : broken.

: Although I have different symptoms than Andrew mentioned, it seems the
: floppy driver is broken in 1.1.23 for me, too.

: I tried to build a new boot disk and after the floppy started working
: I got messages like

:       floppy I/O error
:       dev 0200, sector 470
:       Reset-floppy called

: for every other sector.  I have tried this about 10 times, half of it
: with older kernel versions I still have "in stock" and I was able to
: built the bootdisk every time with older kernels and _never_ with
: 1.1.23 (all with the same disk).

      WHEW!! I thought it was just me who was having these floppy drive
errors! Maybe 1.1.24 will fix this!

Bogdan,
bogdan@crl.com
  



: Klaus
: -------------------------------------------------------------------------------
: Klaus Schneider                         Email: root@ks1i486.dialup.xlink.net
: Student of Informatics                         uk0q@rzstud1.rz.uni-karlsruhe.de
: University of Karlsruhe, Germany               klsc@delphi.com
: -------------------------------------------------------------------------------


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

From: bon@lte.e-technik.uni-erlangen.de (Uwe Bonnes)
Subject: Re: HD floppy with 1600 kB, why not?
Date: Tue, 5 Jul 1994 18:43:54 GMT

In article <2886@nikhefh.nikhef.nl> d70@nikhefh.nikhef.nl (Bram Bouwens) writes:
>In the old days, when CP/M was kind of standard, most computers
>could handle 800kB on a floppy. Then came DOS, and decided that
>that was too much: 40 tracks was enough, and 9 sectors per track too.
>
>But now we have a nice OS and nice hardware which can handle disk
>formats up to 1600 kB (within specs), and we only put 1440 kB on
>them. Why is that? Of course, to do so you should use 10 1024 byte
>sectors per track instead of 18 x 512. Indeed, DOS will not be able
>to read these; but who cares?
>Actually, even those old CP/M machines could mix 128, 256, 512 and
>1024 byte sector floppies (at least if you had a Heathkit :-).
>
>So: anyone thought about this yet? Are there any problems that I
>overlook here?
>


The fdpatches supplied such sizes for the 0.999.15 kernel. If you apply the
patches by hand , the work to at least up to 1.1.22
---
Uwe Bonnes  bon@lte.e-technik.uni-erlangen.de

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

From: and1000@cus.cam.ac.uk (Austin Donnelly)
Subject: Re: Intel EtherExpress ethernet drivers in alpha ?
Date: 5 Jul 1994 19:05:04 GMT

In article <2vbqjn$44p@uuneo.neosoft.com>,
John Lellis <lellis@dmccorp.com> wrote:
>Austin Donnelly (and1000@cus.cam.ac.uk) made a fool of himself in public thus:
>: Can anyone point me in the direction of some kernel patches for Intel
>: EtherExpress cards ?   I would quite like to test any alpha/beta code
>: people have lying around... :)
>
>EtherExpress support has been included in the kernels for quite some time
>now.  Uncomment the line in config.in referencing the EtherExpress cards,
>do a make config to select it and remake your kernel.  Works great here!

Thanks to all who emailed me.  I should have RTFSourceCode.

For your information, the EtherExpress driver was first uncomented
officially in 1.1.22.  You just need to say 'y' to the alpha net
drivers prompt.

Ta much :)

Austin

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


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