Subject: Linux-Development Digest #872
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:     Thu, 30 Jun 94 00:13:04 EDT

Linux-Development Digest #872, Volume #1         Thu, 30 Jun 94 00:13:04 EDT

Contents:
  Driver for Sony CDU33A ??? (Erik Konijnenburg)
  Serial Driver/Callback Problems (John Lellis)
  Re: tcsh bug: more information (Matthias Urlichs)
  motif what is it? (Michael Harris)
  Re: Module-izing the floppy driver? (Heiko Schlittermann)
  Berkeley Socket Bug (John F. Davis)
  Re: linux-1.1.20 breaks dosemu0.52 (Andre Schroeter)
  Re: Wine-940620 (Dave Gardner)
  Re: motif what is it? (Chris Flatters)
  Re: Kenrel hacking tips (Erick Herring)
  Re: Disk-compression for Linux (Peter Holzer)
  Re: Wine mailing list (Robert Adams)
  Re: computer science (Steven Buytaert)
  Silicon Valley, CA-- Linux, ISDN, PPP consultant needed at Yggdrasil (Adam J. Richter)

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

From: kony@dutnsi2.tudelft.nl (Erik Konijnenburg)
Subject: Driver for Sony CDU33A ???
Date: Wed, 29 Jun 1994 07:14:40 GMT

I want to buy a Sony CDU33A CD ROM player. Can I use the CDU31A driver
for this player ?

Erik Konijnenburg
Faculty of Applied Physics
Delft University of Technology
The Netherlands

kony@si.tn.tudelft.nl


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

From: lellis@dmccorp.com (John Lellis)
Crossposted-To: comp.os.linux.admin
Subject: Serial Driver/Callback Problems
Date: 29 Jun 1994 14:46:36 GMT

I've e-mailed this question to Karel Kubat, author of callback-1.21, Kris
Gleason, author of getty_ps-2.0.7e, and Ted Ts'o, author of the serial port
drivers, but I am open to suggestions from anyone with a bright idea as to
how to solve this problem:

The callback-1.21/getty_ps-2.0.7e combination works great under kernel 1.0.9
(I now have four lines coming into a kind of "modem server" here at work).
I've been trying out the 1.1.x kernels as they are issued and would like to
migrate to one of them (faster SCSI access, networking improvements, etc.)
except that when I test them, the callback setup always malfunctions.

The scenario goes something like this:

        1.      If I dial in "direct" (bypassing callback) and terminate my session by
                hanging up the phone, all is well.  The modem reinitializes properly
                and recycles to await the next incoming call.

        2.      If I attempt to use callback, it will often work properly, but it will
                occasionally get "stuck" in state = 1 (attempting to call back) and
                never complete the call.  In fact, I need to kill -9 or cbstat -reset
                to get the modem back into service.

        3.      However I connect ("direct" or callback), if I terminate my session
                "gracefully" (i.e., type "exit" at the bash prompt), the modem will
                often get "stuck" in state = 0 (waiting for incoming calls) but does
                not answer the phone.  Again, a kill -9 or cbstat -reset is needed to
                restore the modem to normal service.  It is as though the modem failed
                to init properly, though there is nothing in the getty log to indicate
                that it failed.  If I terminate by hanging up the phone, the modem
                will recycle properly and answer the next call as it should.

Needless to say, this behaviour has kept me from migrating from kernel 1.0.9 to
anything newer.  I note that the version number of the serial drivers changed
from 3.99 to 4.0 between kernels 1.0.x and 1.1.x, so I suspect that is at least
part of the problem.

Can you think of any reason why it should behave this way?  Do you agree that
it is a serial driver problem?  Who should I contact about this?  Who maintains
the serial drivers?

Thanks for any help you can offer me.

--

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: urlichs@smurf.noris.de (Matthias Urlichs)
Subject: Re: tcsh bug: more information
Date: 29 Jun 1994 19:57:13 +0200

In comp.os.linux.development, article <2unqdj$cf9@harbinger.cc.monash.edu.au>,
  shcun1@aurora.cc.monash.edu.au (Stuart Cunningham) writes:
>   I've now realised that there is an important difference between csh
> and tcsh from the point of view of someone who writes alot of scripts.

This comment may not be helpful, but a lot of people (myself included)
think that if you want to write scripts, you should use sh.

Seriously.

-- 
The more noise a motor or a man makes the less power is available.
                                                 -- W. R. McGeary
-- 
Matthias Urlichs        \ XLink-POP N|rnberg  | EMail: urlichs@smurf.noris.de
Schleiermacherstra_e 12  \  Unix+Linux+Mac    | Phone: ...please use email.
90491 N|rnberg (Germany)  \   Consulting+Networking+Programming+etc'ing     42

Click <A HREF="http://smurf.noris.de/~urlichs/finger">here</A>.

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

From: harrism@holmes.ece.orst.edu (Michael Harris)
Subject: motif what is it?
Date: 29 Jun 1994 15:08:35 GMT

I hope you aren't easily upset by "newbee" questions. I have
recently dived into the world of motif programing at work,
and i have a question. What exactly IS motif? I understand that it 
is above all a standard for user interfaces. My question is this:
How can I develop portable applications under X? Can I compile a
motif program to be independent (i.e. work on any X system with
or without motif). I have found the "/Xm/Xm.h" and other header
files. Are these all that are required to compile a motif program?
Is there some kind of run time module that must be present?  

I must write applications to run under X on Suns, HP Appalos, and
my i486 Linux box. Any suggestions for widget sets, GUI builders
i can use for any of these systems (hopefully all of them?) I have
heard about "athena" widgets, which are supposed to be included
with all versions of X, but i can't find them on either my 
TransAmeritech/Slackware or Yggrasil Linux machines. Are they
hiding?

That brings me to my last question. Is there an equivelent to a
dos "PATH" statement in Linux? I get a lot of "no such file or
directory"s for programs that i *know* are there. If i can track
it down in the path structure (no easy task!) it runs fine.

Any help is very appreciated. You can reach me at:

rsmith@gsfc.nasa.gov
harrism@ece.orst.edu

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

From: heiko@lotte.sax.de (Heiko Schlittermann)
Subject: Re: Module-izing the floppy driver?
Date: Tue, 28 Jun 1994 06:25:43 GMT

In article <2ufeob$age@trane.uninett.no>,
Harald T. Alvestrand <hta@uninett.no> wrote:
>Has anyone made the floppy driver into a loadable module?
>I've got a floppy that is a bit weird (connected via a PCMCIA card,
>so it might go away and come back while Linux is running), and would
>like to mess around with the floppy driver a bit.
>
>Loadable modules seem to make for easier debugging than recompiling
>the whole kernel and rebooting. (It took 12 kernel recompiles to find
>out that the PCMCIA card that I was trying would *not* work.....)
>
>Next question: If not, why not? :-) (that is, could anyone call
>it out as easy/difficult/impossible?)

I turned the unifix mitsumi cd-rom driver into a loadable module -
minor problems only:

        o unresolved references (I use an old kernel and an old insmod)
          - manually patching kernel/ksyms.S solved this

        o free_region() (as opposite to snarf_region()) was needed.
          - adding free_region() to kernel/ioport.c solved this
            (by copying snarf_region() to free_region() and turning
            a 0 into 1 (or vice versa, I forgot)

-- heiko

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

From: davis@clark.net (John F. Davis)
Subject: Berkeley Socket Bug
Date: 29 Jun 1994 18:05:43 GMT

Hello.  I wrote some code for a class that uses a full-duplex socket.
When I run the code on a RS6000 or a Sun, it works as planned.  However,
when i run on Linux, it fails.  It fails because I have a socket open with
more than one file descriptor.  i.e., I have a socket with two different
processes hanging onto each end of the socket.  The parent processes
read from the socket, and the child processes write to the socket.

This is supposed to be an application that exchanges files.  i.e., the 
server sends the client a file at the same time the client sends the 
server file.  It's also supposed to demonstrate the full duplex nature 
of sockets.

        A picture is worth a thousand words.
                

                 Parent       / // Really bad picture
                +-----+      /_//  of one end of a socket.
                |     |<----(_)/
                |     |      A    
                +-----+      |
                             |
                Child        |
                +-----+      |
                |     |------+
                |     |
                +-----+

Anyway, what happens is:  On the other unix platforms, after I have
finished sending data to the socket, I do a shutdown(sockfd,1).  (In the
child processes - of course.  They are the ones reading the file and
sending it to the socket.) This is supposed to shutdown the socket in one
direction only.  Thus, allowing the parent processes to get an EOF and return
from it's read of the socket.  After the shutdown is issued, the child 
processes issues a close.  To finally remove all evidence of the socket, 
the parent issues a close, when it gets its EOF.

Well, this works fine on the other platforms, but it chokes on my linux
box.  In Linux, when the shutdown is issued, it closes the socket for both
the child and the parent.  This sucks, buecause it doesn't give the 
parent enough time to finish reading his data from the socket.  Thus, 
if you are exchanging two different files of different sizes, the larger file
is not transferred in its entirety.  (The larger file destination copy will
be the same size as the smaller file.)

Now then, my question is: is this a bug, or a feature of my kernel?  I'm 
running the Yggdrasill F93 distribution, which is version 0.99.l7.  (I 
think.  Someone else said I needed to know the version inorder to answer
my dosemu question.)  Someone told me that I could hack up my kernel, in 
order to get it to work.  I think I'll try that out as a last resort.  If
it's just a kernel version problem, I'll just get a new cd.

Thanks in advance.

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

From: aschr@freddy.rz.FHT-Mannheim.DE (Andre Schroeter)
Subject: Re: linux-1.1.20 breaks dosemu0.52
Date: Tue, 28 Jun 94 08:04:52 CET

Mike Heidt (heidt@mikey.jsc.nasa.gov) wrote:
: I also had problems with dosemu0.52 and linux 1.0.20. Dosemu would report no
: problems, then blank the screen and hang. I was using an ATI ultra 
: mach 8 card. I replaced the mach 8 with an et4000 card and everything
: works fine, so I conclude that the problem is in the video drvers. The
: mach 8 was hanging during execution of the onboard bios. Turning graphics
: off worked mostly, but no cursor. I would like to go back to the mach 8
: if the problem ever gets fixed because it is faster in X windows. BTW, the
: mach 8 worked fine in dosemu0.49.

:       Mike Heidt
:       heidt@aio.jsc.nasa.gov
i'm using a ati graphics ultra mach 8 and an et4000. the mach8 for x and the
et4000 for console and dos. maybe you can switch off the vga part of you'r
ati and use both cards in parallel ??
  andre

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

From: dgardner@netcom.com (Dave Gardner)
Subject: Re: Wine-940620
Date: Wed, 29 Jun 1994 19:14:34 GMT

Joel M. Hoffman (joel@wam.umd.edu) wrote:
: Did I miss something?  Is there a public release of WINE?

Wine is still alpha code, not meant for public consumption.  However,
anyone who is interested can try it out if they want.  It's available at
tsx-11.mit.edu in the directory /pub/linux/ALPHA/Wine/development. 


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

From: cflatter@laphroaig.nrao.edu (Chris Flatters)
Subject: Re: motif what is it?
Date: 29 Jun 1994 17:56:44 GMT

>>>>> "Michael" == Michael Harris <harrism@holmes.ece.orst.edu> writes:

    Michael> I hope you aren't easily upset by "newbee" questions. I
    Michael> have recently dived into the world of motif programing at
    Michael> work, and i have a question. What exactly IS motif? I
    Michael> understand that it is above all a standard for user
    Michael> interfaces. My question is this: How can I develop
    Michael> portable applications under X? Can I compile a motif
    Michael> program to be independent (i.e. work on any X system with
    Michael> or without motif). I have found the "/Xm/Xm.h" and other
    Michael> header files. Are these all that are required to compile
    Michael> a motif program?  Is there some kind of run time module
    Michael> that must be present?

Motif can actually mean one of a number of things.  The first of these
is a GUI standard that specifies the appearance and behaviour of user-
interface components.  Motif is also used to refer to the OSF/Motif
widget set and associated convenience functions that implements these
components in an X Window System environment.  It is also sometimes
used to refer only to the Motif window manager (some people think that
Motif is the window manager only;  such people are generally regarded
as losers in the X Window System community --- with some justification).
There are other toolkits that claim to provide user-interface components
with the appearance and some of the behaviour required by the Motif
UI standard.

An OSF/Motif development environment comprises the header files,
the OSF/Motif libraries (libMrm, libUil and libXm), the UIL compiler.
It should also include on-line documentation, the Motif window manager
(mwm) and some example programs.  A few vendors miss out the UIL
support (avoid them --- UIL is a useful learning tool even if you
don't use it for a final product;  much of its bad reputation stems
from the fact that older versions plain didn't work and is undeserved
by version 1.2.x).

Generally speaking, if you got OSF/Motif as a (binary) developers kit
you can distribute an application that may be run on a machine with
or without binaries by ensuring that the Motif libraries are statically
linked.  If you built Motif from source then things are a little more
complicated.  In either case check what your Motif vendor said you can
and can not do.

    Michael> I must write applications to run under X on Suns, HP
    Michael> Appalos, and my i486 Linux box. Any suggestions for
    Michael> widget sets, GUI builders i can use for any of these
    Michael> systems (hopefully all of them?) I have heard about
    Michael> "athena" widgets, which are supposed to be included with
    Michael> all versions of X, but i can't find them on either my
    Michael> TransAmeritech/Slackware or Yggrasil Linux machines. Are
    Michael> they hiding?

If you use Motif and X11R5 you can compile your applications on any
of these machines providing that you follow reasonable portability
guidelines for your own code [Voice of experience: In decreasing
order of preference use ANSI C library interfaces, POSIX.1 interfaces,
XPG/3 interfaces and --- only as a last resort --- machine specific
interfaces.  Dealing with Linux means that you need to start dividing
code into system-specific trees between the POSIX.1 level and the XPG/3
level --- Linux does not conform to XPG/3.  Compile code in strict ANSI
mode and use feature test macros to make POSIX and XPG/3 features
visible in the modules where they are needed;  this way the compiler
will issue error messages if you attempt to use a non-portable interface
--- some ANSI C compilers will also issue warnings about some constructs
in the Motif headers if run in a more relaxed mode.   Finally life is
easier if you don't have to deal with versions of SunOS earlier than
5.x: earlier versions do not conform to XPG/3 and do not fully conform
to the ANSI C standard for a hosted environment --- even with gcc -ansi
or acc.

The Athena widgets are an example widget set included with the sample
X11 implementation from the X Consortium (previously from MIT).  They
can be (and have been) used to write applications but they are primarily
intended as example widgets and provide a much more limited set of
features than the OSF/Motif widgets.  The Athena widgets are not a
required part of X11 and may not be supplied by all vendors (although
most vendors do include them so that freeware programs that use them
may be compiled).  Some vendors that ship the Athena widgets may make
them an optional part of their installation.

    Michael> That brings me to my last question. Is there an
    Michael> equivelent to a dos "PATH" statement in Linux? I get a
    Michael> lot of "no such file or directory"s for programs that i
    Michael> *know* are there. If i can track it down in the path
    Michael> structure (no easy task!) it runs fine.

It's called PATH (surprise!) and is usually set in your .profile
(.login for csh users who also have other ways of setting it.

-- 
==============================================================================
Chris Flatters                                          cflatter@nrao.edu
==============================================================================
Well, our problem stems from the fact that we, basically, allow every planet
and moon-base this side of Alpha Centauri to make their own version of Spam.
                                                        "Mystery Meat"
                                                        Man... or Astroman?

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

From: herring@iesd.auc.dk (Erick Herring)
Subject: Re: Kenrel hacking tips
Date: 29 Jun 1994 15:20:33 GMT

Drew is: Drew Moseley <dmoseley@brtph8df.bnr.ca>

--> 1) A book on the workings of the x386 processor. I mean, not
--> only explaining opcodes but also protected mode memory
--> segments, GDT, LDT, Task switching structure
--> 
--> Steven Buytaert

Drew> Any personal recommendations for a book of this sort?

I can recommend:


Crawford, John H.
  Programming the 80386 / John H. Crawford, Patrick P. Gelsinger.  San
Francisco : SYBEX, c1987.  xx, 774 p. : ill. ; 23 cm.
 
LC CALL NUMBER: QA76.8.I2684 C72 1987
 
SUBJECTS:
  Intel 80386 (Microprocessor)--Programming.
 
ADDED ENTRIES:
  Gelsinger, Patrick P.
 
DEWEY DEC:  005.265 dc19
 
NOTES:
  Includes index.
 
ISBN:  0895883813 (pbk.) : $24.95
LCCN:  87-61199



Happy hacking!

Erick

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

From: hp@vmars.tuwien.ac.at (Peter Holzer)
Subject: Re: Disk-compression for Linux
Date: 23 Jun 1994 16:21:44 GMT

teffta@cs690-3.erie.ge.com (Andrew R. Tefft) writes:

>This topic gets beaten to death but there is one approach I like.
[...]
>the idea was a nightly cron job compressed a configurable set
>of files. The first time one of those was accessed, it was transparently
>uncompressed and put back *in place* and left uncompressed till
>the nightly compression run. 

I used soemthing like this under DOS some time. Apart from the
reliability aspects of that particular implementation there is a
fundamental problem: You can cause the disk to fill up just by reading
files. Every now and then I do something like `find ~ -print | xargs
exec grep' and if this requires another 50MB which aren't there I'm out
of luck (and all other people on the same machine, too). The file system
would have to start compressing files again if space is getting tight.
Or it might keep both the compressed and uncompressed versions of a file
which was not modified. This way it doesn't have to compress a file if
it isn't needed any more, but can simply delete it.

        hp
-- 
   _  | hp@vmars.tuwien.ac.at | Peter Holzer | TU Vienna | CS/Real-Time Systems
|_|_) |------------------------------------------------------------------------
| |   | It's not what we don't know that gets us into trouble, it's
__/   | what we know that ain't so. -- Will Rogers

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

From: robert@oblique.ksmith.com (Robert Adams)
Subject: Re: Wine mailing list
Date: Tue, 28 Jun 1994 05:00:45 GMT

Robert Adams (robert@oblique.ksmith.com) wrote:

:       Where is the current version of wine comilable for linux located?
: also i have heard of a wind mailing list..  could anyone tell me the address.
: Thanks..   I few people i know are very interested in this..


        Thank you to the _many_ people who replied to my message..  
It helped alot..
<I didnt really type the above.. I didnt type that badly.. no it couldnt
have been me.. must have been someone else....  ;^) >


Robert.
-- 
Robert Adams.                                   still wanting a good .signature
                                                    adamsr@hamlet.uncg.edu
It's just me!!!!!                                  robert@oblique.ksmith.com


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

From: buytaert@imec.be (Steven Buytaert)
Subject: Re: computer science
Date: Tue, 28 Jun 1994 08:46:18 GMT

Grant Edwards (grante@reddwarf.rosemount.com) wrote:
: Albert D. Cahalan (adc@bach.coe.neu.edu) wrote:
: : I would like to know what some of the Linux developers think of their
: : jobs.  I am considering switching my major from electrical engineering
: : to computer science.  What would be important to learn?  What might I
: : end up doing?

[ good advice about staying in the engineers league ]
: I was an EE, but took language theory, OS courses, compiler 
: construction, data structures, and so on.  Other than that my 
: emphasis was in microprocessors and digital electronics.  
[ ... ]

  Same for me here. Except, the OS and CS stuff, I have learned
  through 'auto didaction', another word for SM :-) I graduaded
  in digital electronics like Grant, but am now busy 90% doing
  analog microelectronics.

[ ... ]
: It may not be fair but CS grads are second class
: citizens at most of the companies that I'm familiar with.  Some or the
: CS grads are much sharper than some of the engineering grads, but "if
: you don't have an engineering degree, you ain't an engineer" is a
: pretty common attitude.

  Maybe that is the situation in the States, it sure isn't this
  way in Belgium. I know people, that have are CS that earn a lot
  more pay then I do; but then again, when you're an engineer 
  in a research environment, you probably earn more by selling
  ice cones in Alaska :-) You do something because you *like* to
  do it. You won't get rich, but you'll sure get older. Hey, take
  that from a guy that's only 29...

: Keep in mind that my experience is with companies that manufacturing
: hardware (ranging from missile launchers, to cellular phones, to golf
: carts, to process control equipment).  The software is mostly
: embedded, real-time stuff.  If you go to places that write database
: applications, I'm sure it's a different story.

  Aha, the database apps. I have (together with 4 other partners), a
  company selling what we call 'solutions to a problem'. I.e. we don't
  sell hardware platform X with software Y. No, we solve a problem for
  the client. This involves most of the times writing custom software
  between databases and CAD systems. Now, this market, especialy in
  Belgium, is a snake pit. Its reputation is completely f*cked up by 
  'malafide' amateurs and even large (multinational) companies. We have
  our own system of engineering SW that works 100% all the time, so we
  have happy customers.

  Why all this salespitch ? These four partners of mine are all
  micro electronics engineers. So, moral of the story:

  1) take the degree you like working for first
  2) keep in mind that an engineering degree is a good
     starting point for a lot of careers. BTW, as Grant said,
     an engineering degree in X doesn't mean you'll be working
     your whole life on topic X.

  Hope this helps a bit in making your decision,

  Stef

--
Steven Buytaert 

WORK buytaert@imec.be
HOME buytaert@innet.be

        'Imagination is more important than knowledge.'
                        (A. Einstein)

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

From: adam@yggdrasil.com (Adam J. Richter)
Crossposted-To: misc.jobs.offered
Subject: Silicon Valley, CA-- Linux, ISDN, PPP consultant needed at Yggdrasil
Date: 29 Jun 1994 15:03:19 GMT


        Yggdrasil Computing, maker of the first and best selling free
operating system CDROM's, has an opportunity for a consultant to write
a Linux PPP driver for an inexpensive ISDN board.

        Required:
                1. You must know PPP (point-to-point protocol) inside
                   and out. 

        Desired:
                1. Linux experience, especially kernel programming,
                   especially networking.  We have kernel hackers
                   here who will can with this project, but it will be
                   much better if you can implement most of your work
                   without help.
                2. ISDN experience.  We are told that nobody here will
                   need to know much about ISDN.
                3. You live in the Bay Area and can work in our offices.

        If you are interestested, you must respond *very* quickly.
We will probably make a decision on this project tomorrow (June 30) or
Friday.  Please call or send email now now.  You can send a resume and
other job information a day or two later, but we need to know who is
available right now.

        Contact:        Adam Richter
                        Yggdrasil Computing, Inc.
                        (408) 261-6630
                        adam@yggdrasil.com
-- 
Adam J. Richter                     -      --------------   "Free software for
adam@yggdrasil.com                    \  /                   the rest of us."
4880 Stevens Creek Blvd., Suite 205    || g g d r a s i l    408-261-6630
San Jose, CA 95129-1034                ||  Computing Inc.    fax 408-261-6631

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


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