Subject: Linux-Development Digest #946
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:     Mon, 25 Jul 94 09:13:14 EDT

Linux-Development Digest #946, Volume #1         Mon, 25 Jul 94 09:13:14 EDT

Contents:
  Dosemu won't work with >1.1.29 <1.1.35 and recompile won't help (lcvanveen@et.tudelft.nl)
  Re: TCP/IP networking for DOSEMU - Why it should be there. (Martin Rex)
  Re: gcc and Linux (compiling)... (the MOST SIGNIFICANT bit)
  Re: procps-0.95 broken -- problem is in linux/sched.h (Jim Balter)
  Re: procps-0.95 broken -- problem is in linux/sched.h (Nick Kralevich)
  Voice Mail cards. (Matt Womer)
  Re: Voice Mail cards. (Joerg Mertin)
  Re: using RS232 from program ? (Rob Janssen)
  PCI video card not working with ALL graphics (John Edward Bauer)
  Where's the source? (Karl Hakimian - staff)
  Re: Linux Performance Enhance ? (Brandon S. Allbery)
  Ooops! SCSI CD-Rom broken in 1.1.33 (Christopher Shaulis)
  Re: Energy Star Screen Saver for X? Monitor Shutdown codes? (Kim-Minh Kaplan)
  Re: ARP broken ?! (Hans-Christoph Rohland)
  Re: patch 31 breaks kmem ps *sob* (Caleb Epstein)
  Re: GOTO haters ..Re: Linux Performance En (Chris Bitmead)
  Re: Media Vision: Pro Video Board (Christopher M. May)
  Re: Xfree86: increase pallate? (Christopher M. May)

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

From: lcvanveen@et.tudelft.nl
Subject: Dosemu won't work with >1.1.29 <1.1.35 and recompile won't help
Date: 25 Jul 94 11:02:59 +0200

Last week I rebuild Linux to version 1.33 and noticed dosemu0.52 
wouldn't work anymore. The screen went black and the only thing 
I could do was shutdown with crtl-alt-del. This morning I went 
over to Linux 1.1.35 and recompiled dosemu again. I still won't 
work. I does in an xterm, but goes black in a VC. I then set 
commented aout the S3-support and the direct access to the 
videoport and got a segmentation fault that brought Linux to a 
complete standstill. The only thing I could do was reset my poor 
machine.
Does anybody know what's changed within Linux VC support that 
Thanks a lot in advance.
Martijn

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

From: mrex@indigo0.urz.uni-heidelberg.de (Martin Rex)
Subject: Re: TCP/IP networking for DOSEMU - Why it should be there.
Date: Tue, 12 Jul 1994 17:54:03 GMT
Reply-To: mrex@rz.fht-mannheim.de

Rob Janssen (rob@pe1chl.ampr.org) wrote:
> I would certainly want to add the necessary support (if needed or necessary)
> to the packet driver, but I lack the info about what to do.

Hmmm,  I don't know what you're discussing all the time;
I have booted DOSemu with 1.1.18 and NCSA-Telnet works fine
within the emulator together with Novell Netware.

Do you say that this is not officially supported and it even isn't
supposed to work?

.. just wondering,

-Martin


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

From: xmsb@borland.com (the MOST SIGNIFICANT bit)
Subject: Re: gcc and Linux (compiling)...
Date: Fri, 22 Jul 1994 02:12:31 GMT

In article <BCR.94Jul21174705@k9.via.term.none>,
Bill C. Riemers <bcr@physics.purdue.edu> wrote:
>In article <30l3tu$hih@luxor.mch.sni.de> Reinhard.Schiedermeier@deejai.mch.sni.de (Reinhard Schiedermeier) writes:
>
>Hmmm, I thought
>#include <stdlib.h>
>
>is always required.  If not, it is still good programming style to
>include it.
>
    actually, only if you want to use something that's declared
    in stdlib.h.  in my opinion good programming practice includes
    only incluuding headers if you are going to use something
    from it.

>> :   main()
>> : ^^^^^^^^^ Sorry, sorry, sorry...I typed the post by had and read off a 
>I don't know if it is required, but all unix programs I've ever
>written or edited use:
>
>  void main(int argc, char *argv[])
>
    hrm.  How unfortunate.  the first one is a correct way to define
    main (defining it to take an unspecified number of arguments
    and returning an int **), while the second is not (main() always
    returns an int).  Note that "void main()" is a ridiculous
    but common compiler extension.

suggested reading:  the FAQ from comp.lang.c --- many good pointers
for using C.  One of those files that I always try to keep handy.

--
Maurice S. Barnum               ==    I speak for me, not my employer.
xmsb@genghis.borland.com        ||    "There is no confusion like the
mosigbit@deeptht.armory.com     ||    confusion of a simple mind."
mbarnum@nyx.cs.du.edu           ==       -- F. Scott Fitzgerald

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

From: jqb@netcom.com (Jim Balter)
Subject: Re: procps-0.95 broken -- problem is in linux/sched.h
Date: Mon, 25 Jul 1994 10:03:10 GMT

In article <jqbCtHFss.K4K@netcom.com>, Jim Balter <jqb@netcom.com> wrote:
>I don't understand the difficulty.  The compiler told you, quite explicitly,
>that testfile.c includes sched.h which includes fs.h which includes net.h,
>and that net.h has an error on line 104 at the token "select"table".
>select_table is obviously a typedef, and so it has to be defined before being
>used.  Grepping the headers show that it is in linux/wait.h, so that needs to
>be included somewhere.  Why would that take 4 hours?  Exactly what the best
>fix is depends upon the Linux philosophy on nested header files.  My method
>is to include a header file in any header file that requires it; this costs
>nothing since, if headers are protected from multiple inclusion, gcc is clever
>(tricky?) enough not to even open the header file more than once.

As someone else pointed out, you need to defined __KERNEL__.  linux/wait.h
is already included by linux/net.h .

This suggests that the application of #ifdef __KERNEL__ has been inconsistent.
Either all uses of select_table should also be within __KERNEL__, or the
typedef should not be within __KERNEL__.


-- 
<J Q B>

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

From: nickkral@po.EECS.Berkeley.EDU (Nick Kralevich)
Subject: Re: procps-0.95 broken -- problem is in linux/sched.h
Date: 25 Jul 1994 10:18:19 GMT

In article <jqbCtHFss.K4K@netcom.com>, Jim Balter <jqb@netcom.com> wrote:
>>However, when I tried to compile it, I came up with these error 
>>messages:
>>
>>In file included from /usr/include/linux/fs.h:15,
>>                 from /usr/include/linux/sched.h:86,
>>                 from testfile.c:1:
>>/usr/include/linux/net.h:104: parse error before `select_table'
>
>I don't understand the difficulty.  The compiler told you, quite explicitly,
>that testfile.c includes sched.h which includes fs.h which includes net.h,
>and that net.h has an error on line 104 at the token "select"table".
>select_table is obviously a typedef, and so it has to be defined before being
>used.  

If you reread the error statement, it says that there was a parse error 
BEFORE select_table.  In fact, you wil notice that line 22 of net.h 
has the include file for linux/wait.h, so your solution is obviously
incorrect.

>Grepping the headers show that it is in linux/wait.h, so that needs to
>be included somewhere.  Why would that take 4 hours?  

It took 4 hours because linux/wait.h WAS included in net.h, without
me having to add it!  The problem is BEFORE select_table.

The other suggestion about using -D__KERNEL__ during complies,
however, did work.  But I thought that it should be reserved
for when one is compiling the kernel.  Or perhaps it just
means that it should be included when compiling code that 
involves source code from the kernel.

Take care,
-- Nick Kralevich
   nickkral@cory.eecs.berkeley.edu

-- 
Nick Kralevich                        nickkral@cory.eecs.berkeley.edu
"A man sits with a pretty girl for an hour and it seems shorter than 
a minute.  But tell that same man to sit on a hot stove for a minute, 
it is longer than any hour.  That's relativity."  -- Einstein

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

From: matt@csc.albany.edu (Matt Womer)
Subject: Voice Mail cards.
Date: 25 Jul 1994 05:30:22 GMT

I'm looking into buying a voice mail card... I'd like to use it under
Linux, I know it comes with Windows software (it's the Boca Multisomething
or other insert buzzword here, type of thing).  Now, what is required to
make such a beast work udner linux?  Is there a standard for voice mail
cards?  Does anyone have experience with ANY type of voice mail card
that they'd like to share?  

Should I start reading the kernel hackers guide now?


-Matt
--
matt@csc.albany.edu

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

From: jorgagif@w250zrz (Joerg Mertin)
Subject: Re: Voice Mail cards.
Date: 25 Jul 1994 10:41:30 GMT

Matt Womer (matt@csc.albany.edu) wrote:
: I'm looking into buying a voice mail card... I'd like to use it under
: Linux, I know it comes with Windows software (it's the Boca Multisomething
: or other insert buzzword here, type of thing).  Now, what is required to
: make such a beast work udner linux?  Is there a standard for voice mail
: cards?  Does anyone have experience with ANY type of voice mail card
: that they'd like to share?  

: Should I start reading the kernel hackers guide now?

Well, under Linux you don't need a Voice-Mail-Card. I have an Old
Galaxy-NX Card (Soundblaster Compatible) and installed on my system
the metamail Package. Since the I'm using Voice mail for some Close
Sites from home.
By the Way, I also have an Phone-Answering System Working with a
U-1496 E Zyxel and vgetty that mails me the incoming call to the Phone
Administrator. So, why buy such special things ???


: -Matt
: --
: matt@csc.albany.edu


Solong & Happy Hacking...
--
*************************************************
*       It s not a trick :-) !! It s Linux      *
*             Smurphy, Email under:             *
*        jorgagif@w203zrz.tu-berlin.de          *
*   How long Will we survive our technologie ?  *
*       I don't know, But the next World,       *
*          We shall build it better !!!         *
*************************************************

/----------------------------------------------\
|HomeBox                                       |
|       smurphy@stardust.fan.bln.sub.org       |
|                                              |
\----------------------------------------------/


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

Crossposted-To: comp.os.linux.help,comp.os.linux.misc
From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: using RS232 from program ?
Reply-To: pe1chl@rabo.nl
Date: Mon, 25 Jul 1994 08:23:19 GMT

In <1994Jul24.113618.204@tora.RoBIN.de> sws@tora.RoBIN.de (Steffen W. Schilke) writes:

>Hi,

>I plan to write a framegrabber software to control and access a 
>framegrabber which is connected via a RS232 to my LinuX box. I
>would like to know how to set the speed of a serial port (is
>up to 115200 bps possible ?) and all the other tiny things I 
>need to know ;-)

>I think to access the serial port I can use C's fopen and the
>fgetc/fputc, or ?

>ThanX a lot            steffen

You can use something like this:  (cut from a program, not necessarily
compilable by itself)

#include <termio.h>
#ifdef __linux__
#include <linux/serial.h>
#endif

struct termios Termio;          /* termios used for the tty */
#ifdef __linux__
struct serial_struct Serial;    /* high-speed and other serial details */
#endif

int openline()

{
        int fd;
        int flags;


        if ((fd = open(DevName,O_RDWR | O_NDELAY)) < 0) {
            logmesg("cannot open line");
            return FAIL;
        }

        settermio();

        /* clear O_NDELAY flag now, we need it for blocking reads
         */
        flags = fcntl(STDIN, F_GETFL, 0);
        fcntl(STDIN, F_SETFL, flags & ~O_NDELAY);

        return fd;
}

void
settermio()
{
        int speed;
#ifdef __linux__
        int divisor;
#endif

        ioctl(STDIN, TCGETS, &Termio);
#ifdef __linux__
        if (ioctl(STDIN, TIOCGSERIAL, &Serial) < 0)
            Serial.type = 0;
        else
            Serial.flags &= ~ASYNC_SPD_MASK;
#endif

        switch (speed = atoi(Speed))
        {
        case 9600:
                Cbaud = B9600;
                break;
        case 19200:
                Cbaud = B19200;
                break;
        case 38400:
                Cbaud = B38400;
                break;
#if defined(__linux__) && defined(USE_SPD_HI)
        case 57600:
                if (Serial.type != 0) {
                    Serial.flags |= ASYNC_SPD_HI;
                    Cbaud = B38400;
                    break;
                }
        case 115200:
                if (Serial.type != 0) {
                    Serial.flags |= ASYNC_SPD_VHI;
                    Cbaud = B38400;
                    break;
                }
#endif
        default:
#ifdef __linux__
                if (Serial.type != 0) {
                    divisor = Serial.baud_base / speed;
                    if ((divisor * speed) == Serial.baud_base) {
                        Serial.flags |= ASYNC_SPD_CUST;
                        Serial.custom_divisor = divisor;
                        Cbaud = B38400;
                        break;
                    }
                }
#endif
                sprintf(MsgBuf, "Invalid speed (%d)",speed);
                logmesg(MsgBuf);
                Cbaud = B9600;
                break;
        }

#ifdef __linux__
        if (Serial.type != 0)
            ioctl(STDIN,TIOCSSERIAL,&Serial);
#endif

        /* initial settings - reasonable to talk to the MODEM
         */
        Termio.c_iflag = BRKINT | INPCK;
        Termio.c_oflag = 0;
        Termio.c_cflag = Cbaud | CS8 | CREAD | HUPCL | CLOCAL | CRTSCTS;
        Termio.c_lflag = 0;

        /* set c_cc[] chars to reasonable values
         */
        Termio.c_cc[VINTR] = CINTR;
        Termio.c_cc[VQUIT] = CQUIT;
        Termio.c_cc[VERASE] = CERASE;
        Termio.c_cc[VKILL] = CKILL;
        Termio.c_cc[VEOF] = CEOF;
        Termio.c_cc[VSTART] = CSTART;
        Termio.c_cc[VSTOP] = CSTOP;
        Termio.c_cc[VSUSP] = CSUSP;
        Termio.c_cc[VREPRINT] = CRPRNT;
        Termio.c_cc[VWERASE] = CWERASE;
        Termio.c_cc[VLNEXT] = CLNEXT;

        Termio.c_cc[VTIME] = 0;         /* block read for 1 char */
        Termio.c_cc[VMIN] = 1;

        ioctl(STDIN, TCSETSF, &Termio);
}
-- 
=========================================================================
| Rob Janssen                | AMPRnet:   rob@pe1chl.ampr.org           |
| e-mail: pe1chl@rabo.nl     | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU     |
=========================================================================

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

From: jbauer@badlands.NoDak.edu (John Edward Bauer)
Subject: PCI video card not working with ALL graphics
Date: Mon, 25 Jul 1994 11:55:29 GMT

I have the Paradise WD90C33 PCI chipset and am having major problems with it.
I cannot run ANY graphical programs. The result is my system locking hard.
I personaly believe that it's not getting the correct address from the BIOS
or something like that... looking in the Linux src  /usr/src/linux/boot
and the file setup.S   There is a section for Paradise cards. Very small
at that. Is there a way I could find out the correct address for this board
so that it will work. I have little/no knowledge of assembly language. (yet)
heh,   Can someone help me in hacking this so it will work?  Thanks
everyone for your time. Please respond e-mail, I would really appreciate it.

I still have hope (well after 5 months very little) that this card will
work. If anything the hardware address of this board would be good too. :)
I'm not picky at this point.


John Edward Bauer <jbauer@badlands.nodak.edu>

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

From: hakimian@haney.eecs.wsu.edu (Karl Hakimian - staff)
Subject: Where's the source?
Date: Fri, 22 Jul 1994 02:53:20 GMT

I hope this is the right place to ask. If not, please politely point me in the
right direction.

One of the main reason I decided to put a Linux on my system (actually I
bought my system to run Linux) instead of purchasing a commercial unix (price
was only part of it) is because when I run into the inevitable bugs, I would
have the source to go and fix the bugs (and add any feature I might want while
I am at it).

As I expected, when I started running Linux I found several bugs (mostly
minor) that I have wanted to fix. The problem has been locating the source!

I put the slackware distribution on and it only comes with a few items of
source. The rest is supposed to be on the ftp sites. Well, I guess the problem
is knowing where on which.

Specifically, I am looking for the source to:

df
color_xterm
who

I have downloaded util-linux which had several things I was looking for but I
am still not able to find everything.

Is there a site where I can get the source to the slackware distribution? Am I
just blind and it has been sitting out there in plain sight begging to be
ftp'ed and I have not seen it?

Any help would be appreciated. Thanks.
--

Karl Hakimian
hakimian@eecs.wsu.edu

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

Crossposted-To: comp.lang.c
From: bsa@kf8nh.wariat.org (Brandon S. Allbery)
Subject: Re: Linux Performance Enhance ?
Date: Fri, 22 Jul 1994 02:07:56 GMT

In article <774702537snz@genesis.demon.co.uk>, fred@genesis.demon.co.uk says:
+---------------
| I agree that C is one of the languages where it can be implemented but it
| isn't the only one (clearly it can be implemented in machine code so
| it isn't inherently a C language issue).
+------------->8

Unfair:  *every* language ultimately results in machine code (even an
interpreter executes machine code to implement the functions requested by the
interpreted program).  Assembler or machine code aren't valid comparisons.

Now, if you can show us Duff's Device in Ada/CoBOL/Pascal/Modula-3/etc.,
you have an argument.

++Brandon
-- 
Brandon S. Allbery         kf8nh@44.70.4.88               bsa@kf8nh.wariat.org
Friends don't let friends load Windows NT (tnx Sun)    A Linux iBCS2 developer

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

From: cjs@netcom.com (Christopher Shaulis)
Subject: Ooops! SCSI CD-Rom broken in 1.1.33
Date: Fri, 22 Jul 1994 02:25:15 GMT

Kernel Version: 1.1.33
'puter: 486XDX/33, 8M ram
SCSI Host: Adaptec 1542C
CD-ROM:
   Vendor: TEAC      Model: CD-ROM CD-50      Rev: 1.06
   Type:   CD-ROM                             ANSI SCSI revision: 02
   Detected scsi CD-ROM sr0 at scsi0, id 2, lun 0
   scsi : detected 1 SCSI disk 1 CD-ROM drive total.

Error:
root:/home/cjs# mount /dev/cdrom /system_cd/ -t iso9660
mount: block device /dev/cdrom is not permitted on its filesystem
root:/home/cjs#

/dev/cdrom:
brwxr--r--   1 admin    admin     11,   0 Oct 27  1992 /dev/cdrom

  ___     _  ___   ____  _  _ ___ _____  ___  ___  __  __     ___  ___  __  __ 
 / __|_  | |/ __| / __ \| \| | __|_   _|/ __|/ _ \|  \/  |   / __|/ _ \|  \/  |
| (__| |_| |\__ \/ / _` | .` | _|  | | | (__| (_) | |\/| | _| (__| (_) | |\/| |
 \___|\___/ |___/\ \__,_|_|\_|___| |_|  \___|\___/|_|  |_|(_)\___|\___/|_|  |_|
==================\____/=======================================================


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

From: kaplan@jussieu.fr (Kim-Minh Kaplan)
Crossposted-To: comp.os.linux.help
Subject: Re: Energy Star Screen Saver for X? Monitor Shutdown codes?
Date: 24 Jul 1994 12:47:45 GMT
Reply-To: kkaplan@cdfhp3.in2p3/fr

Mark Lord (mlord@bnr.ca) wrote:
: In article <2vsalk$qec@bmerha64.bnr.ca> mlord@bnr.ca writes:
: ..
: >I'll have a look in my monitor's specs tonight to see if the details
: >are listed there.

: Okay, here's the scoop.  My Mitsubishi DiamondScan 17FS claims to 
: support the VESA, EPA, and NUTEK power management requirements:

: 1. Stand-by mode:  when the Hsync is off, the monitor is switched to a
: stand-by mode, the screen is off, and when Hsync is restored the monitor
: resumes "immediately".

: 2. Suspend mode:  when the Vsync is off, the monitor is switched to a
: suspend mode, the screen is off, and when Vsync is restored the monitor
: resumes "immediately".

: 3. Complete-off mode:  when the Hsync *and* Vsync are both off, the monitor
: is switched to a complete-off mode, the screen is off, and when the two
: syncs are restored the monitor resumes within 15 seconds.

: So as long as a screen blanker does it's job by turning off the sync
: signal(s), the energy saving circuit will kick in. 

: Looking at function "blank_screen()" in linux/drivers/char/console.c,
: it appears that linux by default does not do this, but rather simply
: fills the display with spaces (0x0020) and turns off the cursor.

: It also looks pretty trivial to add a line or two to turn off the sync(s).
: -- 
: mlord@bnr.ca  Mark Lord       BNR Ottawa,Canada       613-763-7482

  I just wanted to do the same.  So I took the code that did this on
the virtual terminals, and adapted it to XFree86-2.1.1 (on the SVGA
server).  It seems to work for me.  The diffs are short, so I can post
here if anyone is interested.  The original patch was from Christoph
Rimek, chrimek@toppoint.de.  I don't know why, but turning off both
HSYNC and VSYNC doesn't goes into `complete-off' mode

---
Kaplan Kim-Minh, <kkaplan@cdfhp3.in2p3.fr>

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

From: hrohlan@gwdg.de (Hans-Christoph Rohland)
Subject: Re: ARP broken ?!
Date: Mon, 25 Jul 1994 12:20:13 GMT

David Marples (dmarples@voyager.comms.eee.strath.ac.uk) wrote:

: Thank god someone else has this problem - I thought it was just me!
: The prob. does not exist on the 1.0.* kernels, but certainly does to
: date on all 1.1.* kernels from 1.1.22 upwards (I didn't test before
: that, compilation takes a while, you know).  So, since I want to use
: bootp, I'm stuck with 1.0.9 for now!  I didn't go backwards through
: the 1.1's to find out when it did occour though, 'cos I was bored by
: then.

I am using bootpd with kernel 1.1.3 (the last with old networking code)
without probs.
Christoph

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

From: cae@aww.ny.jpmorgan.com (Caleb Epstein)
Subject: Re: patch 31 breaks kmem ps *sob*
Date: 21 Jul 1994 20:17:19 GMT

Simon Ferrett (c9108932@sage.newcastle.edu.au) wrote:

| >patch 31 contains some stuff in it which seems enough to 
| >break kmem ps again (recompiling them doesnt help either)

| >I get negative RSS's and %MEMS way bigger than 100% ...

| something I forgot to mention is that the kmem utilities 
| report correct results until things start getting swapped
| out.. then the bizzare numbers pop up...

        This is also true of the proc-based ps-utils.  I noticed the
same exact behavior last night when running 1.1.31.  I think,
therefore, that this is not related to the kmem stuff but is a bug in
the kernel proper.

--
[ cae@jpmorgan.com ][ Caleb Epstein ][ JP Morgan & Co. Incorporated ]

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

From: chrisb@tansu.com.au (Chris Bitmead)
Subject: Re: GOTO haters ..Re: Linux Performance En
Date: 22 Jul 1994 01:57:32 GMT
Reply-To: chrisb@tansu.com.au

In article 94Jul21100358@k9.via.term.none,  bcr@k9.via.term.none (Bill C. Riemers) writes:
> In article <cairnss.774748222@ucsu.Colorado.EDU> cairnss@ucsu.Colorado.EDU (cairnss) writes:
>    What have they been telling you kids in school?
>    There seems to be a group of upstarts who want to defeat the GOTO.
>          "NO Top-Down with GOTO."
>    What about the simple relationship between GOTO and your machine's
>    assembly language?
> 
>    Maybe it's the FORTRAN in me but I prefer 
>          start:
>          if (cond)
>             {
>               stat;
>               goto start;
>             }
>    to the "top-down" invention 
>          while (cond) {
>            stat;
>          }
> IF I was a compiler I would have much less difficulty
> generating efficient code from the first example.

From the compiler's point of view both of these are exactly the same thing and equally easy or hard to optimise. From a programers point of view, though, once you put in one label with a goto, it's too tempting to put another label in somewhere and another goto. Soon your code has degenerated to spagetti. 

I have no objection to a goto here and there if it's *really* needed, but I think you should dump your fortranish habits.

> 
>> Not that I hate goto's, but in general I would consider both of these
>> examples bad programming?  Why?  Because a goto loop, or a while()
>> loop should only be used when you are willing to face the possability
>> of an infinite loop.  (Very rarely the case.)  Otherwise you should
>> use a for() loop (or the equivlent of it) so you have a counter to 
>> insure even if something in your code is broken, eventually the
>> program will exit the loop.

I don't buy this argument at all. Here's a piece of code from a version of the unix "cat" program. How is using a for loop going to be better than while?

while (0 < (size = read(in, buf, sizeof(buf))))
        if (write(STDOUT_FILENO, buf, size) != size)
                {
                fprintf(stderr, "Write Error\n");
                rtn = 1;
                }

I hardly consider code like the above "rare".



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

From: cmay@titan.ucs.umass.edu (Christopher M. May)
Subject: Re: Media Vision: Pro Video Board
Date: 22 Jul 1994 03:20:20 GMT

Christian Holtje (choltje@ux1.cso.uiuc.edu) wrote:
: I just bought a Media Vision: Pro Video Board, and wondering if anyone
: has any clues what would be necessary to take advantage of this board
: in linux.  If anyone can point me in the right direction, I would be willing
: to write a driver and such for this, but I have NO clue as to how to code
: for X windows (which would be the place to write the app, no?).  I've
: only written diddly-sh*t CS project programs, and would be interested in
: writing something interesting.

:       -Doc

: -- 
:     ---     ---     ---   -      -  -  -   ---  -----  docwhat@uiuc.edu
:    +   -  +    -  +      +      +  -  +  -   +   -    CS major at Illinois
:   *   +  *    +  *      *  +   *  +*+*  +*+*+   *    --- finger me at ---
:  ****     ***     ***   **  **   *  *  *   *   *    choltje@ux1.cso.uiuc.edu

Well, I'm no expert at drivers, but I know 2 things... Media vision is 
in trouble, last I heard, had some "executive" restructuring, (loss of 
some boards of directors.. as a result of ..... (hearsay) them counting
stockpiles of merchandise which was returned as defective as inventory.
I also believe the mediavision boards don't use any "standard" chipset
such as the ET4000, S3, Cirrus, Trident, Mach, come to mind.

Generally, the reason that a given chipset is supported, is that Linux,
developers and (in my opinion more importantly) the XFree86 team 
are given the programming information for free.

Media Vision probably sells a developer's kit... 

But who want's to buy it when a friendly company will help you
write the driver just to sell boards.

--

-Chris May, Computer Science, University of MA, Amherst
-       Technical Assistant, P.C. Maintenance Lab


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

From: cmay@titan.ucs.umass.edu (Christopher M. May)
Subject: Re: Xfree86: increase pallate?
Date: 22 Jul 1994 03:22:06 GMT

Chris Csanady (ccsanady@iastate.edu) wrote:
: I know that implementing true 24-bit graphics in Xfree would be quite
: a task, but how about just increasing the size of the colormap for
: now?  Maybe from 256 to 4096 or something.  Is this possible?

: -chris(ccsanady@iastate.edu)
: -- 

I heard that millions of colors would arrive with XFree 3.1

--

-Chris May, Computer Science, University of MA, Amherst
-       Technical Assistant, P.C. Maintenance Lab


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


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