Subject: Linux-Development Digest #850
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, 22 Jun 94 16:13:08 EDT

Linux-Development Digest #850, Volume #1         Wed, 22 Jun 94 16:13:08 EDT

Contents:
  Re: Deadlock with unix domain sockets (Alan Cox)
  Re: Support for modem based on IBM's MWAVE chip??? (Erik Troan)
  Major device number clash (iCS) (Romano Giannetti)
  Re: [Q]: Signal handling in Unix. (Hamish Macdonald)
  linux-1.1.20 breaks dosemu0.52 (RAINER SCHIELE INFORMATIK)
  Re: linux-1.1.20 breaks dosemu0.52 (Hui-Hui Hu)
  Re: 1.1.20 - Mosaic 2.4 broken? (Bill Heiser)
  Re: Solaris x86 disk = 82 = Linux swap (Manfred Brandl)
  Re: Disk-compression for Linux (David Kastrup)
  Bug in ISO9660 file system! (Joseph Toman)
  Re: Linux ext2fs vs. ufs vs. presto was Re: Fast File System? (Callum Gibson)
  Re: PLIP problems... (Johannes Stille)
  Re: Disk-compression for Linux (Brandon S. Allbery)
  Re: 1.1.20 - Mosaic 2.4 broken? (James Smith)
  Re: Compiling the kernel faster (Dennis Henriksen)
  Re: dosemu-0.52 + CIM (Eckard Kopatzki)
  [Q] What about Amanda? (Gioacchino La_vecchia)
  Runtime compilation and execution (Steven Hugg)
  talk, more, etc. (matthew c. mead)

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

From: iiitac@uk.ac.swan.pyr (Alan Cox)
Subject: Re: Deadlock with unix domain sockets
Date: Tue, 21 Jun 1994 11:56:10 GMT

In article <1994Jun21.055913.27709@unlv.edu> ftlofaro@unlv.edu (Frank Lofaro) writes:
>Linux makes the connect to the server socket block until there is an accept
>performed on the server socket. But that will not occur until the connect 
>goes through, since the process is blocked waiting in connect().

Yeah as I keep pointing out unix domain sockets are only partially implemented
and it doesn't make sense to complete them until the other restructuring is
done. If that one worries you just fix linux/net/unix/sock.c to handle the
O_NDELAY flag properly.

Alan




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

From: ewt@sunSITE.unc.edu (Erik Troan)
Subject: Re: Support for modem based on IBM's MWAVE chip???
Date: 21 Jun 1994 13:49:16 GMT

In article <1994Jun20.164135.5355@kocrsv01.delcoelect.com>,
Michael W. Small <mwsmall@kocrsv01.delcoelect.com> wrote:
> In article <1994Jun14.191735.24719@kocrsv01.delcoelect.com>, mwsmall@kocrsv01.delcoelect.com (Michael W. Small) writes:
> 
> Could anybody tell me if there is work being done to support modems
> based on DSP chips, such as the MWAVE chip from IBM?  I purchased one
> of the first 'ACE' modems from Best Data Products Corp..  This Voice-
> mail/modem/fax modem board is based on the MWAVE chip.  The card works
> great in a windows environment, no drivers exist yet for solely DOS
> usage, and I'm pretty sure that support under linux does not exist
> either.

No drivers exist for linux, and they're not likely to. You should have better
luck with DOS though, I'm actually surprised they're not available yet.

The MWave architecture used on that board is very complicated, and involves 
a real time OS that was split into two pieces, one runs on the board itself 
and the other piece runs on the main box and privides services to the
various device drivers (FAX, TAM, etc). To support Linux, well over 150,000
lines of code would have to be ported from Windows to Linux. It would be
almost impossible to rewrite this code as it uses many undocumented
interfaces and chipsets.

Fyi, I worked on the MWave project for about 6 months last year on the 
FAX/TAM development team. One of the reasons I left was I didn't like
working on a product that I'd never use on my own computer :-)

If you have any other questions, feel free to contact me via email.

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: romano@pimac2.iet.unipi.it (Romano Giannetti)
Subject: Major device number clash (iCS)
Date: 21 Jun 1994 13:14:24 GMT

It have to happen one day...
Only to point out to all around here that iBCS2 and the PC sound
driver (for reference: pcsndrv-0.6 ibcs-940526) use the same major
device number (30). I hit it when trying the wp demo. The solution is
simple, change the MAJOR in the iBCS2 in the Makefile to, say, 31, and
all is ok.

Bye,
        Romano

PS To the iBCS2 team: ****GREAT****

--
*******************************************************************************
Romano Giannetti        * DII-EIT, University of Pisa(E stands for Electronics)
romano@iet.unipi.it     * Dpto Electr. y Electronica, Facultad de Fisica
                        * Universidad Complutense de Madrid
*******************************************************************************

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

From: Hamish.Macdonald@bnr.ca (Hamish Macdonald)
Subject: Re: [Q]: Signal handling in Unix.
Date: 21 Jun 1994 13:12:36 GMT

>>>>> On 21 Jun 1994 07:09:49 EST,
>>>>> In message <2u6lad$2n4@senator-bedfellow.MIT.EDU>,
>>>>> svalente@ATHENA.MIT.EDU (Salvatore Valente) wrote:

Salvatore> Currently, Linux uses the SysV defintion of signal() by
Salvatore> default.  There is some minor flamage going on about
Salvatore> whether it should use the BSD definition by default.
Salvatore> (Personally, I think it should.)  For now, you can get the
Salvatore> BSD definition on Linux by compiling with
Salvatore> -D__USE_BSD_SIGNAL.

Hopefully people aren't using "signal()" in programs intended for
Linux.  Hopefully they're using the POSIX "sigaction()" routine, which
is available in most modern Unices.

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

From: 81264@novell1.rz.fht-mannheim.de (RAINER SCHIELE INFORMATIK)
Subject: linux-1.1.20 breaks dosemu0.52
Date: Tue, 21 Jun 1994 05:58:57 GMT

Hello

Yesterday i compiled dossemu0.52. When i start it, i can not enter more then
one keystroke. My display locks then up. Using rawkey off, give me the 
chance to switch to another vt and kill the process. The Problem is mentioned
in the HOWTO(keybint on), but this must be another mistake. When using 
linux-1.1.19 dosemu0.52 runs.

Rainer

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

From: hdesiato@cs.umd.edu (Hui-Hui Hu)
Subject: Re: linux-1.1.20 breaks dosemu0.52
Date: 21 Jun 1994 09:18:15 -0400

Dosemu runs fine in my 1.1.20 (thanks DOSEMU developers -- it is fast!
heh, Norton sysinfo's CPU speed changes from 5,718 to 90 to 30 ;P)

-Hui-Hui Hu
hdesiato@cs.umd.edu

In article <81264.73.772178337@novell1.rz.fht-mannheim.de>,
RAINER SCHIELE INFORMATIK <81264@novell1.rz.fht-mannheim.de> wrote:
>Hello
>
>Yesterday i compiled dossemu0.52. When i start it, i can not enter more then
>one keystroke. My display locks then up. Using rawkey off, give me the 
>chance to switch to another vt and kill the process. The Problem is mentioned
>in the HOWTO(keybint on), but this must be another mistake. When using 
>linux-1.1.19 dosemu0.52 runs.
>
>Rainer



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

From: bill@bhhome.ci.net (Bill Heiser)
Subject: Re: 1.1.20 - Mosaic 2.4 broken?
Date: 22 Jun 1994 02:23:19 GMT

ralphs@locus.halcyon.com (Ralph Sims) writes:

>What is your MTU setting?  You might try running 966, if you've been
>using a much lower setting.  Or, beef up your lower setting in increments
>of 40 MTU's until the problem goes away (if, in fact, it DOES go away).
>I'd suggest data fragmentation due to blocksizes incompatible with
>Mosaic.  Since Mosaic is the only constant in your equation... ????

I saw the same problem with 1.1.20 and my MTU is 1006.  This is on a SLIP
link using a 28.8 modem.



-- 
Bill Heiser:    bill@bhhome.ci.net

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

From: mbrandl@myhost.subdomain.domain (Manfred Brandl)
Subject: Re: Solaris x86 disk = 82 = Linux swap
Date: 21 Jun 1994 09:10:40 GMT

Brandon S. Allbery (bsa@kf8nh.wariat.org) wrote:
: In article <TLP00.94Jun20140423@mtlyell.spg.amdahl.com>, tlp00@mtlyell.spg.amdahl.com (Tibor Polgar) says:
: +---------------
: | This may be known, but in case it isn't.  Linux has defined filesystem type 82 as 
: | linux swap.  This same filesystem type is used by Solaris to define UFS.  Now since 
: +------------->8

: It doesn't matter, since *ixes don't use the partition type set in fdisk.  As
: long as you stay away from DOS / Netware / OS/2 / NT partition types (those
: operating systems *do* use the partition type) it doesn't matter what you use.
: In particular, Linux is *not* going to suddenly start swapping in your Solaris
: file system on its own just because its partition type is "Linux swap"; nor
: will it stop you from doing a "mkswap"/"swapon" on a type 83 (Linux e2fs)
: partition.
But some software may suggest you to use the partition as swap space
(slackware will certainly do so !)
: ++Brandon
: -- 
: Brandon S. Allbery       kf8nh@kf8nh.ampr.org          bsa@kf8nh.wariat.org
: Friends don't let friends load Windows NT.            Linux iBCS2 emulation

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

From: dak@hathi.informatik.rwth-aachen.de (David Kastrup)
Subject: Re: Disk-compression for Linux
Date: 21 Jun 1994 07:57:51 GMT

dupke@koma.han.de (Kai Dupke) writes:

>albayrak@cc.helsinki.fi wrote:

>:      I would like to discuss about on-fly disk compression. My
>:      opinion is that implementing DoubleSpace(R) and Stacker(R)
>:      -type compressing file-system is one of the most important
>:      future enhancements needed for Linux.

>:      
>:      3. Would it be better to implement whole new file-system
>:         rather than compress data through some existing
>:         file-system (like ext2) by using a large file as an compressed
>:         'disk' (that's how Stacker and DoubleSpace does it).
I hope not. One bad sector would ruin the rest of your disk.
Better compress scraps.

>:      4. Is there any compression-algorithms (sources?) suitable to
>:         task?

>Hi Ali,

>i think that there is the 'double'-patch which include a disk compression
>like You want. For this You should give it a chance or a mail to the
>author.

I liked the idea of the compression libraries: when opening a non-present
file for reading, for which a equally-named file with appended .gz
existed, the library opened that instead (uncompressing of course).
No file positioning, of course.

This still around somewhere?
-- 
 David Kastrup        dak@pool.informatik.rwth-aachen.de          
 Tel: +49-241-72419 Fax: +49-241-79502
 Goethestr. 20, D-52064 Aachen

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

From: toman@darkwing.uoregon.edu (Joseph Toman)
Subject: Bug in ISO9660 file system!
Date: 15 Jun 94 16:42:10 GMT

Hi,

I found a reproducible bug under Linux 1.1.19.  When trying to read a
damaged file from a CD-ROM (Texel) the system prints out two messages
(wrote them down but lost the note) and then hangs.  There is *no*
register dump and I can still switch to other VCs, but after typing the
username at the login prompt there is no further response.  Ctrl+Alt+Del
is not recognized any longer and then after a few minutes I always have
to reset my system (Adaptec 1542C, 20Mb RAM).
If someone would be willing to look into this bug, I'd gladly be of
assistence.


Johannes (toman@darkwing.uoregon.edu)

-- 
===========================================================================
A *very* dumb signature!!!!!

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

Crossposted-To: comp.sys.sun.admin
From: callum@frost.bain.oz.au (Callum Gibson)
Subject: Re: Linux ext2fs vs. ufs vs. presto was Re: Fast File System?
Date: Tue, 21 Jun 1994 04:21:21 GMT

Nigel Gamble (nigel@gate.net) wrote:
> If you are concerned about power failure, the way to survive with
> no corruption and no performance hit is to use a UPS.  Why would you
> want to put any performance hit in the filesystem when there is a
> better way to address the power fail problem?

Then you could do as our sys admin did and trip over the power cord between
the ups and the computer. (sorry Glenn). :-)

regards,
    Callum
-- 
Callum Gibson                                             callum@bain.oz.au
Fixed Income Division, DB Bain & Co.                          61 2 258 1620

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

Crossposted-To: comp.os.linux.admin
From: johannes@titan.westfalen.de (Johannes Stille)
Subject: Re: PLIP problems...
Date: Tue, 21 Jun 1994 23:11:36 GMT

In article <2u3v66$21c@owl.nstn.ns.ca> gpurdy@fox.nstn.ns.ca (Mark Metson) writes:
>Richard Whittaker (rwhittak@orion.docwhitehorse.doc.ca) wrote:
[...]
>: plip1     Link encap 10Mbps Ethernet  HWaddr FD:FD:8E:5C:AE:64
[...]
>
>Ethernet? 10Mbps? I thought PLIP was Parallel Link Internet Protocol using
[...]

This just means that PLIP uses the *packet format* of standard Ethernet
(standard - as opposed to Experimental Ethernet which used, as far as I
remember, 3 Mbit/s). It doesn't say anything about the speed of the
physical connection.

        Johannes

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

From: bsa@kf8nh.wariat.org (Brandon S. Allbery)
Subject: Re: Disk-compression for Linux
Date: Wed, 22 Jun 1994 11:26:02 GMT

In article <2u8kt2$hth@cyberspace.com>, jjulian@cyberspace.com (Joe Julian) says:
+---------------
| The biggest thing that causes unreliablity in MS-DOG compressed "filesystems"
| is the "random non-integrated power intrrupter" or "user" for short.  If they'd
| keep their mits off that switch until they've sat at the prompt and waited for 
| smartdrive, or whatever buffer utility they're using to purge, there wouldn't
+------------->8

        C> COPY CON SYNC.BAT
        SMARTDRV/C
        ^Z

++Brandon
-- 
Brandon S. Allbery         kf8nh@kf8nh.ampr.org          bsa@kf8nh.wariat.org
Friends don't let friends load Windows NT.              Linux iBCS2 emulation

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

From: smith@meishan.animal.uiuc.edu (James Smith)
Subject: Re: 1.1.20 - Mosaic 2.4 broken?
Date: 21 Jun 1994 14:23:41 GMT

bart@scotch.NoSubdomain.NoDomain (Michael Bartmann) writes:

>In article <1994Jun20.063018.737@kshome.ruhr.de>, karsten@kshome.ruhr.de (Karsten Steffens) writes:
>|> Ralph Sims (ralphs@locus.halcyon.com) wrote:
>|> : whywhyZ (yyz@video.ne) wrote:
>|> 
>|> : What is your MTU setting?  You might try running 966, if you've been
>|> : using a much lower setting.  Or, beef up your lower setting in increments
>|> : of 40 MTU's until the problem goes away (if, in fact, it DOES go away).
>|> : I'd suggest data fragmentation due to blocksizes incompatible with
>|> : Mosaic.  Since Mosaic is the only constant in your equation... ????
>|> 
>|> 296. Increasing to 966 did not help, either. So there must be another
>|> problem. I even tried MTU 1500... no use. And Mosaic 2.4 is working with
>|> 1.1.19, only 1.1.20 makes the problems.
>|> 
>|> Karsten
>|>

>I am using Linux-TCP/IP since 0.98 and my WD-kompatible SMC-Elite
>never had problems with Mosaic.
>But now: the same problem as Ralph Sims reported, I cannot access
>URLs OUTSIDE of our domain using 1.1.20.
>All other TCP/IP stuff works well though.
>Maybe some timeout values have changed ?

>Clueless,   Michael
> 
>-- 
>Michael Bartmann                | internet: bartmann@rog.rwth-aachen.de
>Rogowski Institut RWTH-Aachen   | tel:      0241/80-7584
>52062 Aachen, Schinkelstr. 2    | fax:      0241/80-7605

Also telnet in from some sites not work in 1.1.20
1.1.19 work fine.


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

From: duke@diku.dk (Dennis Henriksen)
Subject: Re: Compiling the kernel faster
Date: Wed, 22 Jun 1994 13:40:18 GMT

agulbra@nvg.unit.no (Arnt Gulbrandsen) writes:

>make -j isn't so good, but what I use, "make -j 5 -k -l 4.0" seems
>about right if there's enough RAM to avoid swapping, and enough
>files to compile in the same directory to keep the CPU utilisation
>at 100%.  (I usually use a 16MB RAM 486 with no other users, and
>without any X server).

>If you don't supply an argument to -j, it will start all the
>compiles in each directory at the same time, no good idea.

>The important thing is to avoid make clean, of course.

>--Arnt

I have a configuration similar to that and usually when I boot my
system I have the following line in my rc.local 

  nice -n 8 procinfo -df > /dev/tty8 &

That way I can actually monitor the system's resource usage. I have found
that make -s actaully speeds things up a bit on it's own. ( It produces only
"relevant" info to the tty). But I too use
-j -l . With different values depending up on my intension with the system
whilst waiting for a new kernel to be ready.

Dennis Henriksen
duke@diku.dk

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

From: root@stevie.isar.muc.de (Eckard Kopatzki)
Subject: Re: dosemu-0.52 + CIM
Date: 22 Jun 1994 12:55:48 GMT

In article <2u80m7$1tf@stevie.kopp.muc.de>, root@stevie.isar.muc.de (Eckard Kopatzki) writes:
> Hi all,
> 
> has anybody managed to get the CompuServe Information Manager (CIM) up and
> running under dosemu-0.52? (I know this question concerns 'enemy's territory'
> but I really need CIS for professional purposes (in fact, it was the reason I
> started with thinking about dosemu ...)) I'm kicked off at the point where CIM 
> tries to connect in most cases (sometimes even if it tries to build up it's
> screens).
 
I have to correct this statement posted yesterday. It should read:
"I'm kicked off at the point where CIM tries to display something after having
connected." (The connection itself seems to work, at least the LEDs on my show
heavy traffic. BTW, Telix works without flaws under dosemu.)

-- 
Eckard Kopatzki           Internet eko@isar.muc.de
Therese-Giehse-Allee 53     CompuServe 100024,2175
D-81739 Muenchen, Germany     Voice +49-89-6378103

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

From: gio@cli.di.unipi.it (Gioacchino La_vecchia)
Crossposted-To: comp.os.linux.admin
Subject: [Q] What about Amanda?
Date: 22 Jun 1994 01:56:48 GMT

Anybody working with amanda on linux systems?

(amanda is the popular multi-backup client/server program)

                                        gio

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

From: hugg@xi.cs.fsu.edu (Steven Hugg)
Subject: Runtime compilation and execution
Date: 21 Jun 1994 23:09:07 GMT


I am trying to port an application from DPMI to Linux, and have hit the
rocks in one respect . . . My program relies on a compiler to generate
machine code in real time and execute it, giving it full access to the
data segment. It needs to recompile and execute a few times per second.

Under DPMI I did this with a few selector aliases and by changing the
rights of the selectors. How is this normally done in Linux? I have looked
at the kernel-hackers-guide, HOWTOs and FAQs, and even the man pages
disappoint me. I looked at shared memory, but from what I gather,
shared-memory segments do not currently allow execution priviliges. Is this
true?

I would appreciate any help -- the quicker I get through this, the quicker
my cool program can be released :)

--
Steven E. Hugg
hugg@cs.fsu.edu

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

From: mmead@csugrad.cs.vt.edu (matthew c. mead)
Subject: talk, more, etc.
Date: 22 Jun 1994 09:35:51 -0400



        I think around 1.1.18 or so, talk, more, and other programs that use
the same screen movement routines have broken.  They worked fine in earlier
kernel releases, but don't work any longer.  I was hoping that future kernel
releases would fix it.  I've also tried recompiling under these newer kernels
with no success.  Any ideas as to why this behavior is occuring?  Thanks!



-matt


-- 
-- Matthew C. Mead --       | To learn recursivity you must know recursivity.
mmead@csugrad.cs.vt.edu     | To learn recursivity you ... oh wait that's
ztalk voicemail accepted at |-------------------------------------\ iteration
-thumbtack.bevc.blacksburg.va.us - | http://thumbtack.../~mmead   |----------

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


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