Linux-Development-Sys Digest #974, Volume #6     Mon, 19 Jul 99 08:13:44 EDT

Contents:
  Re: when will Linux support > 2GB file size??? (Leslie Mikesell)
  Re: 32 Char usernames (David Nillesen)
  Re: Help please - want to limit size of user's e-mail on sendmail. (Norman Levin)
  to ignore IO errors ([EMAIL PROTECTED])
  help compiling kernel 2.2.9 please! (root)
  Building a Digital modem box with Linux ? (David Nillesen)
  Re: newbie question (Azhar Abu Talib)
  Re: DMA from/to user space? (Maciej Golebiewski)
  Re: Memory error tool (J.H.M. Dassen (Ray))
  Re: DMA from/to user space? (Maciej Golebiewski)
  Excessive System Mode in SMP Linux (x86) ("Gerlach van Beinum")
  Re: when will Linux support > 2GB file size??? (Peter T. Breuer)
  vm86() syscall ("overflow")
  Re: vm86() syscall (Andreas Jaeger)
  Re: DMA from/to user space? (Robert Kaiser)
  /dev/console handling in 2.2.10 (Neil Faulks)
  Linux/IRDA (Helmut Artmeier)
  Re: vm86() syscall ("overflow")

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

From: [EMAIL PROTECTED] (Leslie Mikesell)
Crossposted-To: comp.os.linux.advocacy
Subject: Re: when will Linux support > 2GB file size???
Date: 18 Jul 1999 15:48:55 -0500

In article <7mo5sf$3678$[EMAIL PROTECTED]>,
bill davidsen <[EMAIL PROTECTED]> wrote:

>| It didn't appear to make a measurable difference when the *BSD's added
>| large file support years on 32 bit machines years ago.  Why do people
>| imagine it would be different with Linux?  
>
>Most of us don't. A few us of CPU added to an i/o measured in ms is
>noise. Unless someone is doing lots of seeks and no i/o, in which case
>they have other problems.
>
>The real issue (as others have noted) is that mmap() won't work in any
>reasonable way, and there isn't an obvious easy solution. The regular
>i/o stuff, open, close, *seek and *tell could probably be faked, and I
>suspect that *stat() stuff could as well, as long as everything was
>recompiled properly.

My memory is hazy here, but I thought that BSDI went through this
transition without having to recompile user code.  I thought the
only real problem was that there was not a portable way to represent
a 64 bit off_t number in ansi C so they had to use a struct. 

>I don't see any easy fix for mmap(), any fix would include 64 bit
>subscripts in many places, and I think that *would* be a performance hit
>of vast impact.

Until (not unless...) you have a box with more than 2 gigs of RAM.
Then the performance hit will be that you can't use all the RAM.

  Les Mikesell
   [EMAIL PROTECTED]

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

From: David Nillesen <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: 32 Char usernames
Date: Mon, 19 Jul 1999 07:53:56 +1000

        Thanks,
        
        We thought of the chown problem. Luckily if you type:

chown Kaptain.Krash:Kaptain.Krash filename

it will work happily. Takes forever to type though.

Mail aliases get a little unmanagable when you have 4500 users and
everyone wants their own psuedonym. Perhaps we should make a web page
that allows users to change there own aliases. hmmmmmm
        
        Thanks for the suggestions, 
        very helpful :)

    David Nillesen

Northnet Internet Services 
+612 67749300


Type Bits/KeyID    Date       User ID
pub  2048/BBCA4E3D 1998/01/03 David A Nillesen <[EMAIL PROTECTED]>

=====BEGIN PGP PUBLIC KEY BLOCK=====
Version: 2.6.3ia

mQENAzSuzZAAAAEIALp91sG9Nq85LKUmvQJlF1imz89BSaoJGb5Dx3pSMhsCztFo
l9iLvGDKQoDXFw7g0FKHme2mBypIeNctBnFCC57xFKDjbJz4KIljN1ngPewgwH2e
PlR0Hm/ocIkuh33HnueJYUC8d8bmAACGAavt40Y+5nVxXcbz+6lGUXEzcdnlKh/E
Oo5MDJnLk1cVl8YgdILKT584oCBWbfBvS9pwNyjwX+HW0cX0f8cOLlGJJNtOtUnm
fff1eV5ZXNXEE7YM2uf3p5u/eCtM0poJA8yY3MwhPiu9a4sjRe7zFpBdTGIBJB+8
iEX7IbQf/NsT8hqkg44IpujnjBGBPqGUAbvKTj0ABRG0J0RhdmlkIEEgTmlsbGVz
ZW4gPGRhdmVAbm9ydGhuZXQuY29tLmF1PokBFQMFEDSuzZA+oZQBu8pOPQEB5j4H
/169BcOssg2lXzTFxmR2ifF1rd0k5PlnCSVEE6+h6EtvZ4uPc+zJTbBLqszV2kfr
WRoiSWTzDVMySMYFmOl+azdkedgqS6GBOl+qBC0w88slFj6kXP1lzLuEDT1Hoxta
NQeleOU0hDibnv0losv4rcis7cThD8YClqkiRStw7IBEgStA3d8o+CMGzdzgvMx4
bqTPDRaTSmGA2Pay5am6/uT1gvEbrjSb8QbDkpKav1cUFYOyIQ6k3XoNZX8eUeqB
kl8c4mg3D0Z9pAY+snv8F76mkpodYO3YBBO/kxa9Zl+YT0LOdsq8FNt5RiFi781L
Oad5uMOPWpTFpD

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

Date: Sun, 18 Jul 1999 11:29:35 -0500
From: Norman Levin <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.setup,comp.os.linux.misc
Subject: Re: Help please - want to limit size of user's e-mail on sendmail.

How about usrquota on the var filesystem?
-- 
Norman Levin
vm/dynAmIX inc.



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

From: [EMAIL PROTECTED]
Subject: to ignore IO errors
Date: 18 Jul 1999 23:44:52 GMT

I'm trying to figure out how to make the kernel ignore IO errors when
reading a CD or SCSI device.  I found what looks like an argument struct
in <linux/cdrom.h> but I don't know which ioctl it should go to or even if
that's the way I should be looking at this problem.

-- 
David Griffith
[EMAIL PROTECTED]

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

From: root <[EMAIL PROTECTED]>
Subject: help compiling kernel 2.2.9 please!
Date: Sun, 18 Jul 1999 20:56:03 -0400

Hi,

I tried to recompile kernel 2.2.9 (from TurboLinux 3.6) with USB audio
drivers as modules, but failed numerous times.  It always has something
to do with /usr/src/linux-2.2.9/kernel/ksyms.c (undeclared variables,
something .... not a function, ...etc).  I tried to compiled it into the
kernel, but no luck.  I know I may not provide enough info to get help,
but did any body get better luck compiling it?  All suggestions welcome.
Thanks.


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

From: David Nillesen <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: Building a Digital modem box with Linux ?
Date: Mon, 19 Jul 1999 10:43:57 +1000

        A company in australia is offering a linux box with a 56K digital modem
service. Thats dial in at 56K , not just dial out at 56K. 
        I have been hunting about to find what cards they would be using. Has
anyone had any experience with making a box like this? 
        DIGI have a seris of cards called "Datafire RAS" that look like it
would do the trick if it had linux support.
        The cards only cost $9999US for a 48 ports which is about what we pay
for a 16 port Ascend upgrade card here in Australia , so the benfits
would be amazing. As well as integrating the proxy etc directly into the
one box.
        Thanks,

    David Nillesen

Northnet Internet Services 
+612 67749300


For info on what this jumble below is look right at the bottom.
Type Bits/KeyID    Date       User ID
pub  2048/BBCA4E3D 1998/01/03 David A Nillesen <[EMAIL PROTECTED]>

=====BEGIN PGP PUBLIC KEY BLOCK=====
Version: 2.6.3ia

mQENAzSuzZAAAAEIALp91sG9Nq85LKUmvQJlF1imz89BSaoJGb5Dx3pSMhsCztFo
l9iLvGDKQoDXFw7g0FKHme2mBypIeNctBnFCC57xFKDjbJz4KIljN1ngPewgwH2e
PlR0Hm/ocIkuh33HnueJYUC8d8bmAACGAavt40Y+5nVxXcbz+6lGUXEzcdnlKh/E
Oo5MDJnLk1cVl8YgdILKT584oCBWbfBvS9pwNyjwX+HW0cX0f8cOLlGJJNtOtUnm
fff1eV5ZXNXEE7YM2uf3p5u/eCtM0poJA8yY3MwhPiu9a4sjRe7zFpBdTGIBJB+8
iEX7IbQf/NsT8hqkg44IpujnjBGBPqGUAbvKTj0ABRG0J0RhdmlkIEEgTmlsbGVz
ZW4gPGRhdmVAbm9ydGhuZXQuY29tLmF1PokBFQMFEDSuzZA+oZQBu8pOPQEB5j4H
/169BcOssg2lXzTFxmR2ifF1rd0k5PlnCSVEE6+h6EtvZ4uPc+zJTbBLqszV2kfr
WRoiSWTzDVMySMYFmOl+azdkedgqS6GBOl+qBC0w88slFj6kXP1lzLuEDT1Hoxta
NQeleOU0hDibnv0losv4rcis7cThD8YClqkiRStw7IBEgStA3d8o+CMGzdzgvMx4
bqTPDRaTSmGA2Pay5am6/uT1gvEbrjSb8QbDkpKav1cUFYOyIQ6k3XoNZX8eUeqB
kl8c4mg3D0Z9pAY

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

From: Azhar Abu Talib <[EMAIL PROTECTED]>
Subject: Re: newbie question
Date: Mon, 19 Jul 1999 10:26:57 +0800

thanks for the help. I just want if all the message never gets print out the
screen and why.

"Moors, ing. E.W.J." wrote:

> Azhar Abu Talib wrote:
> >
> > I am a little bit new with linux . Be patient with me. I have this book
> > By Alessandro Rubini about linux device drivers, and i tried the
> >  examples in the book but even the simplest one doesn't work . I've test
> >
> > the example in two versions of kernel ; one is 2.0.34  , the other one
> > is 2.2.5. The examples given seems do not work on both.
> >  The example is like this:
> >
> > #define MODULE
> > #include <linux/module.h>
> >
> > int init_module(void) { printk(" <1>Heelo World \n"); return; }
> > void cleanup_module { printk("<1>Goodbye Cruel World \n");
> >
> > i compile the file with gcc -c then try to insmod the module but somehow
> >
> > the print
>
> Did you type "dmesg", after the insmod to see if it was printed?
>
> > statement never came out. Can anybody tell me what i am doing wrong .
>
> > Thanks
> >
> > Azhar
>
> eric


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

From: Maciej Golebiewski <[EMAIL PROTECTED]>
Subject: Re: DMA from/to user space?
Date: Mon, 19 Jul 1999 10:04:52 +0200

Robert Kaiser wrote:
> 
> In article <[EMAIL PROTECTED]>,
>         Maciej Golebiewski <[EMAIL PROTECTED]> writes:
> > Robert Kaiser wrote:
> >
> >> IMHO, this kind of functionality should be in the standard kernel.
> >> Anything else (patch or module) is a kludge.
> >
> > I don't know. This (standard part of kernel) is not entirely safe:
> > a rogue application might lock a significant part of physical RAM
> > and bring the system to its knees.
> 
> That's not what I had in mind. I thought of implementing user-space
> DMA functions in the kernel as a standard infrastructure for use
> by device drivers, not as a system call for use by (potentially
> rogue) applications. 

It might work this way. But I was looking at this problem from the
perspective of cluster computing and allowing user apps to directly
access a high speed, and intelligent, network card. This is what
VI Architecture (M-VIA, that I have mentioned here before, is a
free impletation of VIA for Linux) delivers, but it requires that
a user app can lock/unlock a part of its memory, so that the VIA
NIC can do DMA directly into this memory.

Some may argue that you won't lose much if a driver allocates and
locks some memory and the data is copied between this memory and 
user buffers, but this is true only for very short messages, while
for long messages you lose really lot of bandwidth.

> Things are not quite as bad as this sounds though because mlock()
> is a root-only system call and by definition, programs with root
> permissions are to be trusted.

Yes, but this won't work very well on a cluster with many users, many
of whom are not programmers but phycists or scientist of other kind,
and could not be trusted to write programs that can be safely suid'ed.

Maciej

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

From: [EMAIL PROTECTED] (J.H.M. Dassen (Ray))
Crossposted-To: comp.os.linux.development.apps
Subject: Re: Memory error tool
Date: 19 Jul 1999 06:54:33 GMT

Barry Fruitman <[EMAIL PROTECTED]> wrote:
>Can anyone out there recommend a good memory-debugging tool (a la Purify
>or Boundschecker) to find memory errors in my gcc programs?

You can find a list of memory allocation debugging tools at
http://www.cs.colorado.edu/homes/zorn/public_html/MallocDebug.html
Unfortunately, it doesn't list 
Checker or ccmalloc http://iseran.ira.uka.de/~armin/ccmalloc/ .

See also Cesare Pizzi, "Memory Access Error Checkers", Linux Journal #61
(online only article), http://www.linuxjournal.com/issue61/3185.html

Hope this helped,
Ray
-- 
POPULATION EXPLOSION  Unique in human experience, an event which happened 
yesterday but which everyone swears won't happen until tomorrow.  
- The Hipcrime Vocab by Chad C. Mulligan 

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

From: Maciej Golebiewski <[EMAIL PROTECTED]>
Subject: Re: DMA from/to user space?
Date: Mon, 19 Jul 1999 10:16:09 +0200

Robert Kaiser wrote:

> Nevertheless, since so many people seem to be reluctant to patch
> their kernel, I might do just that and offer it as an alternative
> to my patch -- as soon as I can find the time to do it...
> 
> I'm interested in people's feedback on this. Would anyone in this
> group prefer such a module-based solution over a kernel patch ?

Some time ago I was considering applying your patch (I needed that
functionality for a project I'm working on right now) but then
I found M-VIA that has insinde all I need, so I didn't need your
patch any longer.

If there would not be M-VIA available, or I would need this
functionality for another project, I would prefer a module. But if
only a patch would be available, then I would have no problem with
patching my kernel. It would be less comfortable than going with
a module, but in a negligible way :)

Sorry for such a vague statement, my point was that a module would
be a nice thing indeed but is not something crucial :)

Maciej

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

From: "Gerlach van Beinum" <[EMAIL PROTECTED]>
Subject: Excessive System Mode in SMP Linux (x86)
Date: Mon, 19 Jul 1999 09:49:58 +0200

Hello,

 We have a problem on a 2-processor Pentium system. The system has 512 Mb
memory. It is used to make large FEM computations. In general it performs
well. There is one situation where it degrades fast: If we run out test
suite, which consists of about 1500 small jobs, then after say 150 jobs, the
system is mainly running in system mode ( orange in xosview ). This can be
solved by running a small memory allocation (and initializing)job. This
seems to 'flush' memory. But after the next 150 jobs, the same thing
happens. We are Running RedHat 6.0 with kernel 2.5.5. Later kernels behave
the same. What are we missing? I remember something about update or kflushd
processes...

Any help appreciated!

gerlach van beinum  ([EMAIL PROTECTED])



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

From: [EMAIL PROTECTED] (Peter T. Breuer)
Crossposted-To: comp.os.linux.advocacy
Subject: Re: when will Linux support > 2GB file size???
Date: 16 Jul 1999 20:05:26 GMT
Reply-To: [EMAIL PROTECTED]

: to smaller disk, and I would like to tar/gzip the data on the large
: disk into one .tar.gz file into the small disk without having to break
: it into multiple files. (the tar.gz file comes out to about 5 GB in size,
: since the data on the large disk is about 20 GB in size).

Uh folks .. that tar file is useless. (a) it's likely that it contains
a one-bit error somewhere; (b) it's sequential access so you couldn't
access the last element in it in less than 24hrs of computation (I hope
you have a list of the files in it). (c) you surely don't have
partitions of more than about 2-4GB in size anyway? That's just asking
for trouble.

: may be then I wait untill IA-64 is out next year. 

Compute how long it takes to decompress a 5GB file.

I can tell you that a 100MB bzip2 file takes about 1hr to decompress on
a P100.

: Mk.


--
Peter

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

From: "overflow" <[EMAIL PROTECTED]>
Subject: vm86() syscall
Date: Mon, 19 Jul 1999 11:25:33 +0200

I need some kind of documentation about the vm86() syscall. Is is it
supported by glibc? If it's not, how can I call it directly?

Jaime Medrano
[EMAIL PROTECTED]
Eurielec Linux




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

From: Andreas Jaeger <[EMAIL PROTECTED]>
Subject: Re: vm86() syscall
Date: 19 Jul 1999 12:47:07 +0200

>>>>> overflow  writes:

 > I need some kind of documentation about the vm86() syscall. Is is it
 > supported by glibc? If it's not, how can I call it directly?

$ nm /lib/libc-2.1.1.so |grep vm86
000a1940 t __vm86
000a1940 W vm86

$ grep -r vm86 /usr/include/
[...]
/usr/include/sys/vm86.h:extern int vm86 __P ((struct vm86_struct *__info));

Andreas
-- 
 Andreas Jaeger   [EMAIL PROTECTED]    [EMAIL PROTECTED]
  for pgp-key finger [EMAIL PROTECTED]

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

From: [EMAIL PROTECTED] (Robert Kaiser)
Subject: Re: DMA from/to user space?
Date: 19 Jul 1999 09:08:00 GMT

In article <[EMAIL PROTECTED]>,
        Maciej Golebiewski <[EMAIL PROTECTED]> writes:
> Robert Kaiser wrote:
>> 
>> In article <[EMAIL PROTECTED]>,
>>         Maciej Golebiewski <[EMAIL PROTECTED]> writes:
>> > Robert Kaiser wrote:
>> >
>> >> IMHO, this kind of functionality should be in the standard kernel.
>> >> Anything else (patch or module) is a kludge.
>> >
>> > I don't know. This (standard part of kernel) is not entirely safe:
>> > a rogue application might lock a significant part of physical RAM
>> > and bring the system to its knees.
>> 
>> That's not what I had in mind. I thought of implementing user-space
>> DMA functions in the kernel as a standard infrastructure for use
>> by device drivers, not as a system call for use by (potentially
>> rogue) applications. 
> 
> It might work this way. But I was looking at this problem from the
> perspective of cluster computing and allowing user apps to directly
> access a high speed, and intelligent, network card. This is what
> VI Architecture (M-VIA, that I have mentioned here before, is a
> free impletation of VIA for Linux) delivers, but it requires that
> a user app can lock/unlock a part of its memory, so that the VIA
> NIC can do DMA directly into this memory.

In the scenario that I have in mind, the user app would pass the
address and size of the memory to be locked to the VIA NIC (supposing
that it's a device driver) and the driver would do the locking, using
the standard infrastructure in the kernel.

> Some may argue that you won't lose much if a driver allocates and
> locks some memory and the data is copied between this memory and 
> user buffers, but this is true only for very short messages, while
> for long messages you lose really lot of bandwidth.

Well, I certainly wouldn't argue like that: I developed my patch when
I had to deal with a video famegrabber device -- 50MB/sec. Even with
the fastest of CPU's, shuffling that much data around would cause a
significant hog on performance. And the most ridiculous part about this
is that all the CPU does is to move data from one place in memory
to another! Why not DMA directly to where the data should end up?

Cheers

Rob

================================================================
Robert Kaiser                    email: rkaiser AT sysgo DOT de
SYSGO RTS GmbH
Mainz / Germany

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

From: Neil Faulks <[EMAIL PROTECTED]>
Subject: /dev/console handling in 2.2.10
Date: Mon, 19 Jul 1999 10:59:50 GMT

The new console handling in latter kernels seems to be a bit broken.

If a shell is running on /dev/console then /dev/tty does not get
configured properly:

blah: Can't open "/dev/tty"
/dev/tty: Device not configured

Surely /dev/tty should always refer to the controlling terminal, which
in this case is the console.

I note that open 1.4 has trouble with the later kernel (I jumped from
2.0.34 to 2.2.10). I use

open -l /bin/bash
open -l /bin/bash
open -l /bin/bash

To open up three shells on my rescue disk. Now I get two shells running
on /dev/tty2! I wonder if this is related to the console handling.


--
Neil Faulks
[EMAIL PROTECTED]


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

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

From: Helmut Artmeier <[EMAIL PROTECTED]>
Subject: Linux/IRDA
Date: Mon, 19 Jul 1999 13:04:32 +0200

Hi!!!

I have downloaded Dag Brattli's irdatools. I want to use irdadump but
the debug information out of irdadump are very confusing:

09:02:09.620264 xid:cmd 0xffffffff < 0xd152961e S=6 0
09:02:09.690178 xid:cmd 0xffffffff < 0xd152961e S=6 1
09:02:09.750173 xid:cmd 0xffffffff < 0xd152961e S=6 2
09:02:09.820145 xid:cmd 0xffffffff < 0xd152961e S=6 3
09:02:09.880370 xid:cmd 0xffffffff < 0xd152961e S=6 4
09:02:09.880676 xid:rsp 0x00005690 > 0xd152961e S=6 4 LnxMachine
hint=0d00 [ PnP Computer Printer ]
09:02:09.970153 xid:cmd 0xffffffff < 0xd152961e S=6 5
09:02:10.060239 xid:cmd 0xffffffff < 0xd152961e S=6 * Sim1-Client
hint=8404 [ Computer IrCOMM ]
09:02:10.100803 snrm:cmd ca=0xfe pf=1 0x00005690 < 0xd152961e
new-ca=0xe6
09:02:10.101164 ua:rsp ca=0xe6 pf=1 0x00005690 > 0xd152961e
09:02:10.101349 ua:rsp ca=0xe6 pf=1 0x00005690 > 0xd152961e
09:02:10.410419 rr:cmd < ca=0xe6 pf=1 nr=0
09:02:10.410742 rr:rsp > ca=0xe6 pf=1 nr=0
09:02:10.430366 i:cmd  < ca=0xe6 pf=1 nr=0 ns=0 LM slsap=0x03 dlsap=0x00

CONN_CMD
09:02:10.430721 rr:rsp > ca=0xe6 pf=1 nr=1
09:02:10.450332 rr:cmd < ca=0xe6 pf=1 nr=0
09:02:10.450621 rr:rsp > ca=0xe6 pf=1 nr=1
09:02:10.470325 rr:cmd < ca=0xe6 pf=1 nr=0
09:02:10.470615 rr:rsp > ca=0xe6 pf=1 nr=1
09:02:10.490329 rr:cmd < ca=0xe6 pf=1 nr=0
...
09:02:30.870353 i:cmd  < ca=0x4e pf=1 nr=0 ns=0 LM slsap=0x03 dlsap=0x00

CONN_CMD
...
09:02:54.890366 disc:cmd < ca=0xe0 pf=1
09:02:54.890660 ua:rsp ca=0xe0 pf=1 0x00005690 > 0xd152961e
09:02:55.800481 snrm:cmd ca=0xfe pf=1 0x00005690 < 0xd152961e
new-ca=0x8e
09:02:55.800882 ua:rsp ca=0x8e pf=1 0x00005690 > 0xd152961e
09:02:55.801073 ua:rsp ca=0x8e pf=1 0x00005690 > 0xd152961e
09:02:56.110344 rr:cmd < ca=0x8e pf=1 nr=0
09:02:56.110651 rr:rsp > ca=0x8e pf=1 nr=0
09:02:56.130344 i:cmd  < ca=0x8e pf=1 nr=0 ns=0 LM slsap=0x03 dlsap=0x00

CONN_CMD

Maybe you know something about the possible debugging information out of

irdadump...

Helmut Artmeier
[EMAIL PROTECTED]


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

From: "overflow" <[EMAIL PROTECTED]>
Subject: Re: vm86() syscall
Date: Mon, 19 Jul 1999 13:22:35 +0200

Ok, Now I know, how to call it. But I want to know how to use it. How can I
do in vm86, can I call ints, and how can I go back to protected mode?

Thanks

Jaime Medrano
Eurielec Linux


Andreas Jaeger escribi� en mensaje ...
>>>>>> overflow  writes:
>
> > I need some kind of documentation about the vm86() syscall. Is is it
> > supported by glibc? If it's not, how can I call it directly?
>
>$ nm /lib/libc-2.1.1.so |grep vm86
>000a1940 t __vm86
>000a1940 W vm86
>
>$ grep -r vm86 /usr/include/
>[...]
>/usr/include/sys/vm86.h:extern int vm86 __P ((struct vm86_struct *__info));
>
>Andreas
>--
> Andreas Jaeger   [EMAIL PROTECTED]    [EMAIL PROTECTED]
>  for pgp-key finger [EMAIL PROTECTED]



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


** 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: [EMAIL PROTECTED]

You can send mail to the entire list (and comp.os.linux.development.system) via:

    Internet: [EMAIL PROTECTED]

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Development-System Digest
******************************

Reply via email to