Subject: Linux-Development Digest #416
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:     Fri, 28 Jan 94 12:13:11 EST

Linux-Development Digest #416, Volume #1         Fri, 28 Jan 94 12:13:11 EST

Contents:
  Re: Second and 3-rd VLB Video cards for Non-Workspace use? ("Alexander During")
  Re: Help on interpreting GNU license and restriction (Remco Treffkorn)
  Re: Winders NT on MC68K?  (was Re: Which is better? 680x0 or 80x86?) (David Barr)
  Re: UMSDOS Patch to Use \linux? (Tommy Thorn)
  Re: Version control systems... (Jim Anderson)
  Re: configuration during boot-up ??? (Donald Jeff Dionne)
  Re: Broadcast Bug? (Remco Treffkorn)
  Ftape-0.9.9d woes.  Help! (Kevin Hanson)
  Re: Syquest 88 meg - parameters?? (Drew Eckhardt)
  Re: DOSEMU Problem (Kumar K.E.V.)
  Re: pl14s runs my hard drive a lot (Kumar K.E.V.)
  Gcc bug - I need some help!! (Allan Clearwaters)
  RFS supported in Linux (Robert L Sanson)

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

From: 63912i@cfi.waseda.ac.jp ("Alexander During")
Crossposted-To: comp.sys.next.hardware,comp.sys.ibm.pc.hardware.video
Subject: Re: Second and 3-rd VLB Video cards for Non-Workspace use?
Date: 28 Jan 1994 04:31:38 GMT

In article <2i7c23$pk4@agate.berkeley.edu> izumi@pinoko.berkeley.edu writes:
>
>However, I do NOT want these additional video boards to become part
>of Workspace served by the WindowServer (or X server).  I would
>like to access them outside of the WindowServer/DPS as custom
>devices.  There will not be any GUI stuff on them, i.e., no
>windows there.
>
>Do any of video cards allow multiple instances on a single machine,
>i.e., I/O addresses, BIOS and VRAM ranges configurable to
>non-overlapping areas?
>

Well, I once worked at a software company that had exactly the same problem.
They used up to three cards in one computer and wrote their own GUI, being
able to work as if they had one big screen thrice as wide.

Here comes their trick: They used PS/2s and a card named CAD-Genius by a
very small German company that went bankrupt at least once in two years.
According to what I heard from them, this was the only card that supported
multiple instances in one system and that only on PS/2. The output was done
via port I/O, which didn't really matter as it was pretty intelligent. I
had to program it the other day and it was fine.

But the outcome of it is that you can't have it under Linux, because this
does not run on MCA.

Well, as I quoted their trick, they are called STS then. Just advertisement.

Gambatte kudasai

Alex


--
As MS-DOS is very abstruse, \\it's also quite tricky to use. \\So many give in
and try typing 'win'. \\But that means completely to lose.
Alexander D\"uring, Physics Department, Waseda University, Tokyo, Japan.
Statistical Physics, Linux, Shakespeare. --- This space for rent ---

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

Crossposted-To: gnu.g++,gnu.g++.help,gnu.gcc,gnu.misc.discuss,comp.os.linux,comp.os.linux.help,comp.os.linux.misc
From: root@hip-hop.sbay.org (Remco Treffkorn)
Subject: Re: Help on interpreting GNU license and restriction
Date: Tue, 25 Jan 1994 03:44:25 GMT
Reply-To: remco@hip-hop.sbay.org

Sven Heinicke (sven@bradbury.nrl.navy.mil) wrote:
: In article <2i0gob$qtv@brachio.zrz.TU-Berlin.DE> wpp@marie (Kai Petzke) writes:

:    mng@eos.ncsu.edu (MUI-KIM NG) writes:
:    >   Here is my problem: I need money for school. So, I am planning to sell 
:    >my applications to a potential customer.  These applications would use gnu
:    >database and would be compiled gnu g++ and gnu gcc.  Is it still legal to
:    >sell my applications?

: descriptions of GPL and GLPL removed . . .

: perhaps we need a file called COPYING.english and COPYING.leaglieze to
: be put someplace.  :-)


:                       Sven

I agree! I have followed previous flare-ups of that subject and sometimes
got the impression that I finally got it, but then the next time around
I find out that I did not :-(

My reaction: I do pretty much what I feel is ok. If I will subsequently
get sued, I will worry about it then. Since I do not make millions using
gnu stuff, I gather I am safe.

I have been told, that the GPL is for me, it protects my rights. Great,
but after having followed the discussion about it for some time, I am
just confused and feel threatend. I certainly do not make enuff money
using gnu code to warrant the expense to pay a lawyer for a professional
opinion.

It is not that I don't care, it is just more than a normal guy can handle.
The GPL ranges right up there with the tax forms. You can tell that a lot
of man power went into their creation and subsequent refinement. Certainly
a nice piece of work, but beyond my compehension.

Too bad to see so many wrong interpretations flooding the net.
How do I know that they are wrong? Well, if you get 5 diffrent ones and
only one (at most) can be right, that at least 80% are wrong.

From my perspective, the GPL is like any other religion. You try to make the
best of it and if you are wrong you go to hell :-)
Both have their 'high priests', lawyers in this case, who make a good living
out of it.

Remco

-- 

Remco Treffkorn, DC2XT
remco@hip-hop.sbay.org   <<-- REAL reply address !!
(408) 685-1201

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

From: barr@pop.psu.edu (David Barr)
Subject: Re: Winders NT on MC68K?  (was Re: Which is better? 680x0 or 80x86?)
Date: 27 Jan 1994 17:20:40 -0500

In article <2i8tcf$q13@sol.ctr.columbia.edu>,
Jerry Shekhel <jerry@msi.com> wrote:
>Alan Cox (iiitac@swan.pyr) wrote:
>: >MS may simply be avoiding binary file incompatibilities and
>: >byte swapping issues.
>:
>: Snigger.. Unix fixed this 15 years ago too. I would think its a bit more
>: serious than a few byte swapping issues somehow. 
>
>Stop it!  Unix didn't fix squat.  Try writing some integers out to a binary
>file on one machine and then reading them back in on another machine of
>different endian-ness.

Try again.

Look up "byteorder" in your UNIX man pages.  (htonl, htons, ntohl, ntohs).
Also look at RPC, which extends tranparency to other types.

Endianness in a non-issue in UNIX.

--Dave
-- 
"Liberty means responsibility.  That is why most men dread it."
- George Bernard Shaw

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

From: tthorn@hof (Tommy Thorn)
Subject: Re: UMSDOS Patch to Use \linux?
Date: 27 Jan 1994 16:14:46 GMT

Jacques Gelinas (jack@solucorp.qc.ca) wrote:
....

: ............ I suggest you wait for Umsdos 0.2.
: It should be released pretty soon. To give you a preview, here
: is what it does.

: -Autosense \linux\etc\rc or \linux\etc\init. If any of these files
: is there, it switch in pseudo-root mode. .....................

Good idea, but systems adhering to the new Linux Filesystem Standard,
FSSTND, won't be detected, as rc is in /etc/rc.d/rc and init is in
/sbin/init. The easy fix is to look for /sbin/init as well as /etc/init.

: Another feature of Umsdos 0.2, is the flexible mode. Currently, umsdos
: rely on a file --linux-.--- for directory listing. If --linux-.--- is
: either empty or missing, umsdos tells you the directory is empty.
: Using umssync you can creat --linux-.--- on the fly in any directory.
: This could be annoying in many DOS directory. A new semantic has been
: introduced. A missing --linux-.--- means the directory is a DOS directory
: with all its limitations. This means that right after installing
: umsdos 0.2, all you DOS file will be visible in /DOS/...

Very good.
--
Tommy.Thorn@daimi.aau.dk                   Staff-programmer
Aarhus University, Ny Munkegade 116        Phone: +45 89423223
DK-8000 Aarhus C, Denmark.                 Fax:   +45 86135725 
PGP Public Key fingerprint:                E7B1175FC30D9E96B67AF61D89A70A1F 

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

From: anderj@mun18.fi.gs.com (Jim Anderson)
Subject: Re: Version control systems...
Date: Wed, 26 Jan 1994 23:47:19 GMT

>>>>> "Eric" == Eric Jeschke <jeschke@cs.indiana.edu> writes:
In article <1994Jan25.135424.21486@news.cs.indiana.edu> "Eric Jeschke" <jeschke@cs.indiana.edu> writes:


Eric> rsmits@xs4all.hacktic.nl (Ron Smits) writes: : Check out RCS
Eric> version 5.6a is distributed under the GNU licensing and is :imho
Eric> a very robust and easy package to use. Furthermore Emacs
Eric> completly :supports it

Eric> I use RCS, but wasn't aware of the emacs support.  In what way
Eric> does it support RCS?

Check out the "File Handling" chapter in the _emacs19_ manual or read
thru the doc in the distribution.
--
---
Jim Anderson
anderj@fi.gs.com
(212) 902-2406
---

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

From: jeff@ee.ryerson.ca (Donald Jeff Dionne)
Subject: Re: configuration during boot-up ???
Date: 27 Jan 1994 23:59:23 GMT

Enrico Scotoni (scoti@p46.keru.chg.imp.com) wrote:
: Hi all,

: maybe this is a dumb (ignorant) question but:

: I have experience with several other operating systems (VMS, PRIMOS, even MS-
: DOS) and they have some kind of configuration file that is read during boot-up
: in order to configure the kernel. When I first came in touch with a unix system
: I realized that instead of reading such a configuration file you have to
: actually build new kernels for different configurations. To be true when seeing
: this the first time I really was SHOCKED. Since then I now got used to it, but
: the question remains: Why must this be that way ? unix/linux is known to be an
: "elegant OS" (whatever this means), but I think reading a configuration file
: during startup is much more elegant than always building new kernels for
: different configurations. Wouldn't it be nice to have something like /etc/
: config:

: nvc 24          # number of virtual consoles
: nprc 1024       # number of process
: memlimit yes    # limit memory to 16MB

: etc. etc. I think the only thing that really has to be configured with kernel
: configuration is the support of the FS and HD-Support (SCSI etc), so that the
: kernel is at least able to READ this /etc/config or one could enable ALL of
: this support but this would result in a big kernel.

: Am I talking crap ???

Support for loadable modules is the answer to your question, and it well
on the way to useable for all device drivers, etc.  I have seen that
some are concerened about the possible security hole this creates on 
networked machines, though.
: Enrico.

: ---

73! de Jeff / VE3DJF

Internet Jeff@ee.Ryerson.Ca
AMPRnet  VE3DJF@bbs.VE3RPI.ampr.org
AX25bbs  VE3DJF@VE3RPI.#SCON.ON.CAN.NOAM

Linus is a code poet, Bill Gates is a bean counter...

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

Crossposted-To: comp.os.linux.help
From: root@hip-hop.sbay.org (Remco Treffkorn)
Subject: Re: Broadcast Bug?
Date: Tue, 25 Jan 1994 03:26:57 GMT
Reply-To: remco@hip-hop.sbay.org

Derek Hackbardt (hackbard@egr.msu.edu) wrote:
: I am not sure if this is a kernel bug or not..

: It seems that when my default route is set to our gateway, broadcast 
: packets carry the wrong netmask.  This problem occurs when using yp
: under Slackware 1.1.1 and 0.99.14s kernel.  Although when I set the
: default route to the nisserver everything appears to work properly..

: The netmask should be: 255.255.255.0
: Broadcast: 150.220.40.255

: The outgoing broadcast packets go to 150.220.255.255.

: Any ideas?  I can provide more details to who ever would like..

: Thanks..

: -derek A. hackbardt
: hackbard@mced.kodak.com

If I am not mistaken, this is a class B network address. You are subnetting
it. A Class B network has 16 network bits, thus the trailing 255.255 .
If you want something else, just specify the broadcast and subnetmask
explicitly on the ifconfig command line. Use :
 'broadcast 150.220.40.255 netmask 255.255.255.0'

Maybe the library (or ifconfig) could be a bit smarter about it, but
no big deal.

Remco
-- 

Remco Treffkorn, DC2XT
remco@hip-hop.sbay.org   <<-- REAL reply address !!
(408) 685-1201

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

From: kevinh@metronet.com (Kevin Hanson)
Subject: Ftape-0.9.9d woes.  Help!
Date: Fri, 28 Jan 1994 06:57:52 GMT

I am having problems getting ftape-0.9.9d to work at all writing
to a tape.  I am on pl14t and have followed all installation 
instructions and have read all FAQs and HOW-TOs.  Here is a
summary:

  1.  All compilations and module loading were successful
  2.  Compilations were done with gcc2.4.5 and lib4.4.1
  3.  Tape drive is a new CMS Jumbo 250
  4.  Tape is formatted in DOS with CMS tape utility

Once I have installed the ftape module I tried a rewind and
a retension.  These both work fine.  I then tried a simple
tar of one file (tar cvf /dev/ftape file).  Immediately I
get the following output:

(setup_new_segment) - segment: 0
(fdc_isr) - 1am/crc error, let ecc handle it.
(fdc_isr) - too many errors, retry.
(ftape_smart_stop) - tape stopped at undetermined location.

the tape then slowly goes to the end of the tape and rewinds.
Then:

(ftape_read_id) - fdc_interrupt_wait failed.
(fdc_command) - fdc not ready.
(fdc_seek) - failed, status = -16.
(fdc_seek) - destination was: 9, resetting FDC....
(ftape_command) - fdc_seek failed.
(ftape_report_operation) - ftape command failed.
(ftape_start_tape) - ftape_report_drive_status  failed with code -5.
(read_segment) - error: segment 0 unreachable.
(setup_new_segment) - segment: 1
(ftape_smart_stop) - tape stopped passing segment: 5.
(setup_new_segment) - segment: 1
(setup_new_segment) - segment: 2
(ftape_smart_stop) - tape stopped passing segment: 3.
(read_header_segment) - segments-per-track:  150
(read_header_segment) - tracks-per-cartrige:  28
(read_header_segment) - max-floppy-side:       6
(read_header_segment) - max-floppy-track:    149
(read_header_segment) - max-floppy-sector:   128
(read_header_segment) - first data segment: 2
(read_header_segment) - `last' segment is 4199, 29Kb
(read_header_segment) - 121699 Kb usable on this tape.
(ftape_write) - failed: not busy, failure or wrong unit.

tar then terminates with an I/O error.  I've checked out the drive
under DOS and all works fine.  If anyone has experienced similar
problems and can shed some light on what I may be doing wrong, I
would really appreciate it.  Thanks in advance for the help.

kevin
==================
kevinh@feenix.metronet.com
Dallas, Texas


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

From: drew@kinglear.cs.colorado.edu (Drew Eckhardt)
Subject: Re: Syquest 88 meg - parameters??
Date: Fri, 28 Jan 1994 08:29:15 GMT

In article <2i9rsh$lec@great-miami.iac.net>,
George Gerald Gibeau <ggibeau@iac.net> wrote:
>Greetings,
>
>I have been playing with Linux, and have a question.  I currently
>have it working with a Seagate IDE drive, I also have a SCSI
>controller that I use to share an 88 meg Syquest as well as a
>Hitachi CD-ROM with my Amiga.  So far I have been unable to
>get the Syquest to be recognized properly, there is no problem
>with the CD-ROM.
>
>Has anyone out there utilized a Syquest drive with Linux??

Yes.  

If you'd like better pointers as to what you might be able to 
do to fix the problem, I suggest capturing the messages printed
at bootup and posting them.  

From the SCSI-HOWTO (It assumes that Linux isn't up yet, modify the
procedure where appropriate)

Format a floppy diskette under DOS.  Note that if you have a distribution
which mounts the root diskette off of floppy rather than RAM drive, you'll
have to format a diskette readable in the drive not being used to mount
root.

Boot Linux, and login as root

        mkdir /tmp/dos

Insert the diskette in a drive not being used to mount root, and
mount it.  Ie

        mount -t msdos /dev/fd0 /tmp/dos

        or 

        mount -t msdos /dev/fd1 /tmp/dos

Insure that the /proc filesystem is mounted.

        grep proc /etc/mtab

If the /proc filesystem is not mounted, mount it 

        mkdir /proc
        chmod 755 /proc
        mount -t proc /proc /proc

Copy the kernel revision and messages into a log file

        cat /proc/version > /tmp/dos/log
        cat /proc/kmsg >> /tmp/dos/log

Type CNTRL-C after a second or two.

Unmount the DOS floppy

        umount /tmp/dos

And shutdown Linux

        shutdown

Reboot into DOS, and using your favorite communications software include
the log file in your trouble mail.

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

Subject: Re: DOSEMU Problem
From: kkev@sieglinde.umkc.edu (Kumar K.E.V.)
Date: 28 Jan 1994 04:52:11 GMT

Cindy Mann (cam@adied.oz.au) wrote:
: Chris Royle <car1002@cus.cam.ac.uk> writes:

: >When I type

: >dos -A > /dev/null

: >with dosemu 0.49

: >The screen flickers violently, displays my video BIOS startup message, and
: >hangs. It also flashes the floppy drive with boot disc in it once.

: >I can switch consoles and kill the dosemu, but otherwise, it seems a bit
: >crashed to me...

: >Chris.

: Yes, I get exactly the same problem.
: I've read the documentation but still can't see what is wrong.

: Anybody care to give us a solution?

: c.
Well, I KINDA had the same problem.  Except, the problem really was that
I did not follow the proper steps to setup DOSEMU.

You might try getting dosemu0.49pl3.tgz from sunsite.unc.edu:/pub/Linux/
ALPHA/dosemu.  It has a "QuickStart" text file, which shows cleanly the
steps to be taken.  I think this "QuickStart" file is sorely missing dosemu0.49.
The documentation is rather vague otherwise.

BTW, why don't you send the "debug" to a file instead of /dev/null.

like: dos -A > dbg or something like that.  That way you can post the message 
if you have any problems. 
DOS

Well, hope this helps.
Kumar. 

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

Subject: Re: pl14s runs my hard drive a lot
From: kkev@sieglinde.umkc.edu (Kumar K.E.V.)
Date: 28 Jan 1994 04:55:32 GMT

Rob Janssen (rob@pe1chl.ampr.org) wrote:
: In <jcgreen.759357050@boris.tele.iastate.edu> jcgreen@iastate.edu (Jon Green) writes:

: >I've recently installed pl14s, and noticed that my hard drive seems to
: >come on every two minutes or so and run for about 10 seconds or more. I 
: >assume it is syncing, but it never ran the drive that long before.  Is 
: >this something new?

: Don't notice that here...  Of course it is accessed sometimes, but not
: for 10 seconds...

Well.... This has nothing to do with the original post, but I always
wanted to know the answer to this.

I have a SEAGATE and it is very annonyingly loud.  When I leave my computer
on overnight, it makes a lot of noise when it accesses the HDD. 

Is there a way to "park" the HDD and put Linux in a sleep mode or something
like that?  So that it does not have to write to the hard drive everytime.

Thankx.
Kumar.
PS: Please don't reply to my e-mail address. It'll bounce. Just post it
    I'll read it like everyone else.
:)

: Rob
: -- 
: -------------------------------------------------------------------------
: | Rob Janssen                | AMPRnet:   rob@pe1chl.ampr.org           |
: | e-mail: pe1chl@rabo.nl     | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU     |
: -------------------------------------------------------------------------

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

From: allan@mct.uucp (Allan Clearwaters)
Subject: Gcc bug - I need some help!!
Date: 27 Jan 94 18:49:53 GMT

Hi Folks,

This post is a copy of a message I sent on the gnu channels yesterday - 
since this appears to be an i386/486 problem, I thought I might as well
send to the linux community as well.  In essence, the attached programs
work when compiled on a Sparc but not on a linux/80x86 system.  If anyone
has any ideas, they would be greatly appreciated.

Thanx,
Al

=========================================================================
Included with this meassage is a source file that provokes a segmentation
violation under linux when compiled with gcc Objective C v2.5.8/7.  The 
example works on a Sparc system.

The error is somewhere in the area of __builtin_apply() - the violation
occurs on the return for the routine tt().

Since I am in the process of porting Objective C code from the Sun to
the Linux platforms, this is a real problem for me.  It is the case
the the Objective C runtime makes use for the call constructors (in
particular sendmsg()) and so this error is most worrying.  I have
also experienced other violations - my suspicion is that they are all
releated to the same problem.

Is there anyone who may have some insight into this problem??  I'm not
really familiar enough with the compiler to dig into it without diverting
a considerable amount of effort.

Note that if the call constructors are replaced by:

        return( tt( (arglist_t)NULL) )

the example works on linux.

Many Thanks,
Al

<< CUT LINE >>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
/*

Allan Clearwaters, MCT. Ltd., Malvern, England

This is a small test file that provokes a segmentation violation.  The
problem appears to be related to  the builtin_apply() on an i386 machine.
It is the case that this code runs correctly on a Sun SparcStation 2
when compiled with gcc-2.5.7.

Output from gcc -v

=====================================
> gcc -v
Reading specs from /usr/local/lib/gcc-lib/i486-xen-linux/2.5.8/specs
gcc version 2.5.8
=====================================
This behavior also applies to gcc-2.5.7 on linux

The compilation command line is:

=====================================
>gcc -O -g -v testb.m -o testb -lobjc
Reading specs from /usr/local/lib/gcc-lib/i486-xen-linux/2.5.8/specs
gcc version 2.5.8
 /usr/local/lib/gcc-lib/i486-xen-linux/2.5.8/cpp -lang-objc -v -undef -D__OBJC__ -D__GNUC__=2 -D__GNUC_MINOR__=5 -Dunix -Di386 -Dlinux -D__unix__ -D__i386__ -D__linux__ -D__unix -D__i386 -D__linux -Asystem(unix) -Asystem(posix) -Acpu(i386) -Amachine(i386) -D__OPTIMIZE__ -g -D__i486__ testb.m /tmp/cca10087.i
GNU CPP version 2.5.8 (80386, BSD syntax)
#include "..." search starts here:
#include <...> search starts here:
 /usr/local/include
 /usr/local/i486-xen-linux/include
 /usr/local/lib/gcc-lib/i486-xen-linux/2.5.8/include
 /usr/include
End of search list.
 /usr/local/lib/gcc-lib/i486-xen-linux/2.5.8/cc1obj /tmp/cca10087.i -quiet -dumpbase testb.m -g -O -version -lang-objc -o /tmp/cca10087.s
GNU Obj-C version 2.5.8 (80386, BSD syntax) compiled by GNU C version 2.5.8.
 as -o /tmp/cca100871.o /tmp/cca10087.s
 ld -dll-verbose -m486 -o testb /usr/lib/crt0.o -static -L/usr/local/lib/gcc-lib/i486-xen-linux/2.5.8 -L/usr/local/lib /tmp/cca100871.o -lobjc -lgcc -lg -lgcc
Fixup count 0
Removed 0 symbols from symtab
Fixup table address: 149a0
======================================

Output from gdb:

=====================================
Current directory is /local/src/libcoll-931026/tests/
GDB is free software and you are welcome to distribute copies of it
 under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.8, Copyright 1993 Free Software Foundation, Inc...
(gdb) b tt
Breakpoint 1 at 0x67: file testb.m, line 12.
(gdb) run
Starting program: /local/src/libcoll-931026/tests/testb 

Breakpoint 1, tt (f=0x1dfd0) at testb.m:12
(gdb) cont
Continuing.

in tt

Program received signal 11, Segmentation fault
0xc0 in _i_MyTest__test_ (self=0x2a, _cmd=0x10000, aFunc=0x64) at testb.m:32
(gdb) 
========================================

*/

#include <objc/objc.h>
#include <objc/objc-api.h>
#include <objc/Object.h>
#include <stdio.h>

static unsigned tt( arglist_t f )
{
  printf( "\nin tt\n");
  fflush( stdout );
  return(42);
}

@interface MyTest: Object
{
}

- (unsigned) test: ( unsigned (*)(arglist_t))aFunc;
@end

@implementation MyTest
- (unsigned) test: ( unsigned (*)(arglist_t))aFunc
{
  int size;
  void *ptr1;

  size = method_get_sizeof_arguments(
            class_get_instance_method(self->isa, _cmd));
  ptr1 = (void *)__builtin_apply((apply_t)aFunc,
                                 __builtin_apply_args(),size );
  __builtin_return( ptr1 );
}
@end

main()
{
  id a = [MyTest new];
  int i;

  i = [a test: tt ];
  exit(0);
}
<< CUT LINE >>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++

This is a c program that displays the same behavior

<< CUT LINE >>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
/*
Allan Clearwaters, MCT. Ltd., Malvern, England

This is a small test file that provokes a segmentation violation.  The
problem appears to be related to  the builtin_apply().

Output from gcc -v

=====================================
> gcc -v
Reading specs from /usr/local/lib/gcc-lib/i486-xen-linux/2.5.8/specs
gcc version 2.5.8
=====================================
This behavior also applies to gcc-2.5.7 on linux

The compilation command line is:

=====================================
>gcc -O -g -v testb.m -o testb -lobjc
Reading specs from /usr/local/lib/gcc-lib/i486-xen-linux/2.5.8/specs
gcc version 2.5.8
 /usr/local/lib/gcc-lib/i486-xen-linux/2.5.8/cpp -lang-objc -v -undef -D__OBJC__ -D__GNUC__=2 -D__GNUC_MINOR__=5 -Dunix -Di386 -Dlinux -D__unix__ -D__i386__ -D__linux__ -D__unix -D__i386 -D__linux -Asystem(unix) -Asystem(posix) -Acpu(i386) -Amachine(i386) -D__OPTIMIZE__ -g -D__i486__ testb.m /tmp/cca10087.i
GNU CPP version 2.5.8 (80386, BSD syntax)
#include "..." search starts here:
#include <...> search starts here:
 /usr/local/include
 /usr/local/i486-xen-linux/include
 /usr/local/lib/gcc-lib/i486-xen-linux/2.5.8/include
 /usr/include
End of search list.
 /usr/local/lib/gcc-lib/i486-xen-linux/2.5.8/cc1obj /tmp/cca10087.i -quiet -dumpbase testb.m -g -O -version -lang-objc -o /tmp/cca10087.s
GNU Obj-C version 2.5.8 (80386, BSD syntax) compiled by GNU C version 2.5.8.
 as -o /tmp/cca100871.o /tmp/cca10087.s
 ld -dll-verbose -m486 -o testb /usr/lib/crt0.o -static -L/usr/local/lib/gcc-lib/i486-xen-linux/2.5.8 -L/usr/local/lib /tmp/cca100871.o -lobjc -lgcc -lg -lgcc
Fixup count 0
Removed 0 symbols from symtab
Fixup table address: 149a0
======================================

Output from gdb:

=====================================
Current directory is /local/src/libcoll-931026/tests/
GDB is free software and you are welcome to distribute copies of it
 under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.8, Copyright 1993 Free Software Foundation, Inc...
(gdb) b tt
Breakpoint 1 at 0x67: file testb.m, line 12.
(gdb) run
Starting program: /local/src/libcoll-931026/tests/testb 

Breakpoint 1, tt (f=0x1dfd0) at testb.m:12
(gdb) cont
Continuing.

in tt

Program received signal 11, Segmentation fault
0xc0 in _i_MyTest__test_ (self=0x2a, _cmd=0x10000, aFunc=0x64) at testb.m:32
(gdb) 
========================================

It is the case that this code runs correctly on a Sun SparcStation 2
when compiled with gcc-2.5.7.

*/

#include <stdio.h>

static unsigned tt( void aFunc( void), int k)
{
  printf( "\nin tt\n");
  fflush( stdout );
  return 47; 
}

unsigned test( void aFunc( void* t,int x ),int k  )
{
  int size;
  void *ptr1;

  return (  (int)__builtin_apply( aFunc,
                                 __builtin_apply_args(),8  ));
}

main()
{
  int i;

  i = test( (void*)tt,44 );
  printf( "i= %d\n",i );
  exit(0);
}




















--

=======================================================================
= Allan Clearwaters             Phone:  44+(684)569292                =
= MCT Ltd.                      Fax:    44+(684)561153                =
= 62 Albert Rd. North           Email:  allan%mct.uucp@britain.eu.net =
= Malvern, Worcs.                       (allan@mct.uucp)              =
= England  WR14 2TL                     The first address guarantees  =
=                                         delivery                    =
=======================================================================

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

From: R.L.Sanson@massey.ac.nz (Robert L Sanson)
Subject: RFS supported in Linux
Date: Fri, 28 Jan 1994 09:07:28

Dear Linuxers,

Just wanted to know if RFS is supported in Linux. I have need of running a 
program on a remote Sun, which supports a digitizer. I need to have the 
digitizer connected to my Linux box. I have talked with a person who has 
implemented this in a Sun only environment using RFS (remote file sharing).
Will this be possible under Linux?

Regards,

Robert Sanson
R.L.Sanson@massey.ac.nz


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


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