Subject: Linux-Misc Digest #800
From: Digestifier <[email-masked]>
To: [email-masked]
Date: Thu, 22 Sep 94 11:13:20 EDT

Linux-Misc Digest #800, Volume #2                Thu, 22 Sep 94 11:13:20 EDT

Contents:
  Re: DoubleSpace Filesystem (Alan Cox)
  Re: Does Linux detect parity NMI? (Alan Cox)
  Re: Trouble with fdisk 1.5 on big disk (Stinger)
  Re: More Memory = Slow Linux?? (Beeblebrox)
  Re: ** autoconf.h? ** (Rob Janssen)
  Re: More Memory = Slow Linux?? (Sverker Wiberg)
  Don't use Linux or it's to academic! (Svein Erik Brostigen)
  Re: Linux is a GNU system and the DWARF support (Alan Cox)
  Sound, but no music in DOOM (HongGuang Bi)
  inn 1.4 missing file nntp_access (Andre Addicks)
  cron - crond - crontab(s) (Darin Parsons)
  Re: 80-bit floats with f2c and linux (Dan Pop)
  Re: 486 Math Not Detected on 486SLC (Rob Fugina)
  Re: Linux in OpenSystems Today (Michael Rogero Brown (Sys Admin))
  Smalltalk under Linux ([email-masked])
  Re: DoubleSpace Filesystem (Trink Andreas)

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

From: [email-masked] (Alan Cox)
Subject: Re: DoubleSpace Filesystem
Date: Thu, 22 Sep 1994 10:40:35 GMT

In article <[email-masked]> [email-masked] (Harry C Pulley) writes:
>Matthew S. Richmond (mattr@h4snap) wrote:
>: Thomas Scheuermann ([email-masked]) wrote:
>: : Title        = Linux Filesystem for DoubleSpace (readonly)
>: : Version      = 1.0
>: : Desc1        = With this kernel module Linux is able to read
>: : Desc2        = a DoubleSpace compressed Filesystem.
>
>: Are there any plans to make this work with Drive Spaced drives since
>: Doublespace is no longer used since Stacker won the lawsuit against
>: Micro$oft?  Thanks
>
>And what about Stacker itself?  If Microsoft got into hot water then I guess
>someone should talk to Stac Electronics before they distribute anything.

The author is in Germany. They don't have software patents in germany like
most of the world. Someone might cop it for using it in the USA however.

Alan

-- 
  ..-----------,,----------------------------,,----------------------------,,
 // Alan Cox  //  [email-masked]   //  GW4PTS@GB7SWN.#45.GBR.EU  //
 ``----------'`----------------------------'`----------------------------''

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

From: [email-masked] (Alan Cox)
Subject: Re: Does Linux detect parity NMI?
Date: Thu, 22 Sep 1994 10:55:48 GMT

In article <[email-masked]> [email-masked] (Alex Ramos) writes:
>Does Linux detect and handle a memory parity error NMI?
>Given empirical evidence that I have, I think the answer
>is "NO, Linux just ignores them", but I would like to know 
>for sure.
>
Assuming you actually get one it logs the NMI with a warning you may have
bad ram. Most problems with modern ram are not caught by parity errors
however.

Alan
-- 
  ..-----------,,----------------------------,,----------------------------,,
 // Alan Cox  //  [email-masked]   //  GW4PTS@GB7SWN.#45.GBR.EU  //
 ``----------'`----------------------------'`----------------------------''

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

From: [email-masked] (Stinger)
Crossposted-To: comp.os.linux.help
Subject: Re: Trouble with fdisk 1.5 on big disk
Date: 22 Sep 1994 11:53:56 +0200
Reply-To: [email-masked]

In article <[email-masked]>,
[email-masked] (Goncal Badenes) wrote:

> worked without problems. Could the problem be related to the fact that
> the disk has more than 1024 cylinders?

I don't think that's the problem, cause it works on my drive which has 19xx
cylinders. Linux gives me a warning about the high cylinder number tho.

The disk I'm using is a 2GB HP connected to a Buslogic 747.

-- 
->Stinger<-

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

From: [email-masked] (Beeblebrox)
Subject: Re: More Memory = Slow Linux??
Date: Thu, 22 Sep 1994 11:40:21 GMT

[email-masked] (Brad Matthew Garcia) writes:

>I keep seeing posts made by people who have added memory
>to their computers and subsequently experienced a drop in
>performance under Linux.

>I want to know if anyone knows *why* this happens. 

It's due to caching problems.  This is bound to happen to some extent or
other as the ratio of cache to main memory falls but if it is significant, it
is usually caused by a duff motherboard.  Make sure you have a 256K of cache
and you should be fine.  I've got 20M and I've no problems.
---
   [email-masked]              [email-masked]
             "I follow your steps in snow, the traces disappear.
     We know what we've lost when it's gone, I'm wishing you were here."

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

From: [email-masked] (Rob Janssen)
Subject: Re: ** autoconf.h? **
Reply-To: [email-masked]
Date: Thu, 22 Sep 1994 07:38:33 GMT

In <[email-masked]> [email-masked] (Christopher Michael Joslyn) writes:

>In article <[email-masked]>,
>Michael_Nelson <[email-masked]> wrote:
>>Recently, when attempting to build some applications (one was yamm), I've
>>encountered a problem where the application will #include 
>>
>>      "/usr/src/linux/include/config.h"
>>
>>config.h isn't a problem, because it's there, and it gets #included without
>>problem.  But config.h has a line in it that #includes "<linux/autoconf.h>",
>>and there is no autoconf.h anywhere on my system.
>>
>>So far I've been able to get around the problem by commenting the #include
>>of that file out of config.h, and the applications seem to build without
>>problem... but it makes me uncomfortable when I have to hack system files
>>like this... 
>>
>>Is this #include of autoconf.h an error in config.h, or should I really have
>>an autoconf.h?

>/usr/src/linux/include/linux/autoconf.h is created after you do a make
>config in the /usr/src/linux directory.  The kernel uses it, as well as
>some other applications, to know how the kernel is configured.  There are
>two ways it can be removed, one is to explicitly remove it and the other
>is to do a make mrproper in the /usr/src/linux directory [can we get this
>changed anyone?].  You will need to do a make config again to recreated it.

OTOH, it is not a good idea to include /usr/src/linux/include/config.h
in an application program...
Apparently the application depends on configuration details of the kernel,
but those can change without the application knowing about it!

Rob
-- 
=========================================================================
| Rob Janssen                | AMPRnet:   [email-masked]           |
| e-mail: [email-masked]     | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU     |
=========================================================================

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

From: [email-masked] (Sverker Wiberg)
Subject: Re: More Memory = Slow Linux??
Date: 22 Sep 1994 11:50:11 GMT

[email-masked] (Brad Matthew Garcia) writes:
> I keep seeing posts made by people who have added memory
> to their computers and subsequently experienced a drop in
> performance under Linux.
> 
> I want to know if anyone knows *why* this happens.

The FAQ says:

   Question 6.9. When I add more memory it slows to a crawl.

   This is quite a common symptom of a failure to cache the additional
   memory. The exact problem depends on your motherboard.

   Sometimes you have to enable caching of certain regions in your BIOS
   setup. Look in the CMOS setup and see if there is an option to cache
   the new memory area which is currently switched off.  This is
   apparently most common on a 486.

   Sometimes the RAMs have to be in certain sockets to be cached.

   Sometimes you have to set jumpers to enable the caching.

   Some motherboards don't cache all the RAM if you have more RAM per
   amount of cache than they expect. Usually a full 256K cache will solve
   this problem.

   If in doubt, check your motherboard manual. If you still can't fix it
   because the documentation is inadequate you might like to post a
   message giving *all* the details - make, model number, date code,
   etc. so that other Linux users can avoid it.

--
Sverker Wiberg  <[email-masked]>
        There is more than one way to skin a cat:
           Way #257: Bombard with relativistic (0.9 c) steel pellets.
        GCS -d+ c+(++) l++ u e+(*) m++(*) s !n h f+ g+ w t+ r !y

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

From: [email-masked] (Svein Erik Brostigen)
Subject: Don't use Linux or it's to academic!
Date: 22 Sep 1994 09:09:44 +0200
Reply-To: [email-masked]

<Flam-bait follows!>
First, please excuse my language - English is my second language,
Norwegian is my first.

Now, I would never (or at least not for some years) recommend Linux to
my customers as an alternative to MS-DOS or OS/2, especially not when
we are talking about networks and day-to-day use of business programs.

1. There is no support for the more sofisticated disk handlings like
   RAID 5 or STRIPING.

2. There are no programs available that does Word-processing, spreadsheets,
   databases, presentation graphics and so on, as we have under MS-DOS
   and Windows.

3. There is currently no easy way to interconnect to LAN Server or Netware
   natively, i.e.  from Linux.

4. There is no support for MCA-based machines.

5. There is no support for Token-Ring (some ALPHA code is floating around
   on the Net, but....)

6. Nationalized version of the few programs existing are not available.

7. Nationalized versions of Linux is not available.

8. Support for modern graphics accelerators like Mach64, Stealth64 etc, 
   is not scheduled until maybe next year.

9. Printed manuals and easy 'Get started' manuals does not exist.

10. Support for Mulit-media is shaky.

11. Support for ISDN is not generally available.

12. There is no disk-compression.

I do have more points, but I think this is enough. 
Personally, I think Linux is great and I'm runnig it on one of my disks,
but I also run MS-DOS and WfW 3.11 and OS/2 WARP2 BETA, OS/2 2.11, all
except WARP2 in native language.

When I'm recommending some system to my customers it should be something 
that has a proven record of durability, Netware and Lan Server both have 
that when it comes to NOS'es. MS-DOS and OS/2 have it when it comes to
PC OS'es.

My customers are like all other customers, they will use wordprocessors,
spreadsheets and so on. They are now used to be able to see the same thing
on the screen as they will get on the paper. They need to import data
from a wide range of other products, read MAC disks etc.

In a network environment, things like RAID 5 and STRIPING both adds to
security and speed. 

When it comes to TokenRing and MCA based machines, well IBM is the
biggest player in the computer world no matter what you people of the
.edu thinks!

What amazes me, is that there are so few from the commercial world in
this fora, only from the academic world. Maybe I should take that as
a sign telling me that this is of purely academic interest at the
moment.

Now gentlemen, it's up to YOU!

---
Svein Erik Brostigen, Tech. manager
Rønning Netverk Systemer AS          Pho. +47 22 37 04 00
P.O. Box 6730, Rodeløkka             Fax. +47 22 37 03 70
N-0503 Oslo                          Cel. +47 92 03 00 74
Norway

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

Crossposted-To: gnu.misc.discuss
From: [email-masked] (Alan Cox)
Subject: Re: Linux is a GNU system and the DWARF support
Date: Thu, 22 Sep 1994 11:50:15 GMT

In article <house.780027739@helios> [email-masked] (ron house) writes:
>What they are saying is up to them, not you. That's why there are licences -
>to clarify what they are saying. But what I ask authors to do is ask
>themselves whether they really _want_ to say what the GNU licences say,
>given their basis in a very strange concept of (lack of) property rights.

The GNU license and the FSF are two totally unrelated things. I think bits of
the FSF politics is a bit but the GPL achieves exactly what I want - and
doesn't in anyway do away with property rights.

Alan

-- 
  ..-----------,,----------------------------,,----------------------------,,
 // Alan Cox  //  [email-masked]   //  GW4PTS@GB7SWN.#45.GBR.EU  //
 ``----------'`----------------------------'`----------------------------''

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

From: [email-masked] (HongGuang Bi)
Subject: Sound, but no music in DOOM
Date: Sun, 18 Sep 1994 19:19:44 GMT

Hi,

why is there stereo sound but no music from my SB16
(kernel 1.1.45) when play linuxxdoom+sndserver+doom1.wad ?
I read two posts about the same problem before, haven't
find reply here nor in FAQ.Linux.Doom.

Thanx.

HongGuang ([email-masked])

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

From: [email-masked] (Andre Addicks)
Crossposted-To: comp.os.linux.help
Subject: inn 1.4 missing file nntp_access
Date: 22 Sep 1994 09:30:41 GMT

Hello,

I recently installed inn.1.4. on my Linux system as it was distributed
with the Slackware 2.0 version. First of all it seems to work fine. But
sometimes, when I want to read news with winvn or telnet on port 119,
I'm getting the message: "innd server can't talk to you"
When I'm looking in the syslog file, I see the following message:
"nntp[]: access: fopen /usr/lib/news/nntp/nntp_access : No such file or 
directory.
This is correct I don't have this file, in fact I never had it.
The workaround is, that I have to shutdown and restart inn.

I tried to post this question on news.software.nntp, but I did not get
any satisfactory answers.

Can somebody tell me what is wrong ..

Thanks in advance,

greetings
Andre Addicks.
==============================================================================
Andre Addicks                  | Telephone : +31 70 3437944
PTT Telecom B.V.               | Telefax   : +31 70 3436268
I&AT                           | E-mail    : [email-masked]
P.O. Box 423                   | DISCLAIMER: This Statement is not an official
NL-2260 AK Leidschendam        | statement from, nor does it  represent an
The Netherlands                | official position of, PTT Telecom B.V.
==============================================================================

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

From: [email-masked] (Darin Parsons)
Subject: cron - crond - crontab(s)
Date: 22 Sep 1994 13:05:23 GMT
Reply-To: [email-masked] (Darin Parsons)

Anyone have any info on crontabs and their use and/or cron/crond and its use?
Linux documentation/faq(s) are too vague as to use. Email appreciated. Thanks

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

Crossposted-To: comp.lang.fortran
From: [email-masked] (Dan Pop)
Subject: Re: 80-bit floats with f2c and linux
Date: Wed, 21 Sep 1994 21:35:03 GMT

In <[email-masked]> [email-masked] (David E. Fox) writes:

>Doesn't the coprocessor do all arithmetic internally in 80 bits already? 
>If so, the question then becomes whether or not it is prudent to keep
>around the extra bits from the 80 bit internal operation when stored in
>variables.
>
>I think you can use 80-bit values (tenbytes) directly but you need to drop
>to some inline asm to accomplish it, since the language doesn't support it
>directly.

This is not a problem, because the language which is converted to 
machine code is C and not Fortran. And gcc supports the 80 bit format,
via the standard C type 'long double'.

Other posters have pointed out the real problem: such an implementation
is non-standard and the compiler itself would need changes, to be aware
of the fact that the size of a DOUBLE PRECISION variable is not twice
the size of a REAL variable, as required by the language definition.

Dan
--
Dan Pop 
CERN, CN Division
Email: [email-masked]
Mail:  CERN - PPE, Bat. 31 R-004, CH-1211 Geneve 23, Switzerland

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

Crossposted-To: comp.os.linux.help
From: rfugina@mcdgs01 (Rob Fugina)
Subject: Re: 486 Math Not Detected on 486SLC
Date: Wed, 21 Sep 1994 23:21:25 GMT
Reply-To: [email-masked]

In article <[email-masked]>, Karl Buck <[email-masked]> wrote:
>System:
>
>ThinkPad 340
>486SLC 25/50
>kernel v1.1.51
>Slackware 2.0.0
>
>Symptoms:
>When installing a fresh 1.1.51 kernel (gcc 2.5.8), and booting things
>go ok until it gets to the math coprocessor test where it says
>something to the effect:
>
>Math coprocessor or emulator not found
>Giving up
>
>Anyone know how to fix this or why it is happening? --Karl

I know exactly why it's happening.  The 486SLC doesn't have a math coprocessor.
If the salesman said it did, then you got ripped off.

Rob

-- 
Rob Fugina, Systems Analyst ** I think, therefore I am not politically correct.
  [email-masked], [email-masked], [email-masked], [email-masked]
     GE/CS d-(---) p c++++ l++ u++ e- m+ s+/- n--- h-- f? !g w+ t+ r y?
                    http://mcmcweb.cr.usgs.gov/~rfugina/

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

From: [email-masked] (Michael Rogero Brown (Sys Admin))
Subject: Re: Linux in OpenSystems Today
Date: Tue, 20 Sep 1994 20:56:21 GMT

Robert Mudge ([email-masked]) wrote:

: I saw an editorial about Linux in Open Systems Today
: Magazine.  Says as stable as Sun 4.1.3!  Great job
: Linus T and crew.

I don't know if it was the same thing, but in the latest Open Systems Today
(#158), their "Systems Administation" column by Bruce Hunter focused on
Linux.

One nice point he made is comparing the slowness of major developers in gettting
out OSs verses Linux's development.

--
==========All Opinions Expressed are MINE, not IBM's==============
Michael Rogero Brown       (*IX System Administrator)  
IBM (uK Development)         TEL/TIE   (407) 443-6400   
Boca Raton, FL               Internet:  [email-masked]

If you think I speak for IBM, then I've got some swamp land^H^H^H^H^H^H^H^H^H^H
real estate to sell you.

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

Subject: Smalltalk under Linux
From: [email-masked]
Date: 22 Sep 94 12:14:05 WET+0100

Hi guys !

        The following information will help all those who want to use Smalltalk
under Linux. 
        Steve Byrne was kind enough to send me the following diffs (which he 
in turn got from Mark Bush) to make smalltalk 1.1.1 run on Linux :
have fun.

                                                Sami Ahmad
                                                ITT WD, Nederland.
                                                [email-masked]
===============================================================================

diff -w -r -c --new-file smalltalk-1.1.1.old/config/m-linux.h smalltalk-1.1.1/config/m-linux.h
*** smalltalk-1.1.1.old/config/m-linux.h
--- smalltalk-1.1.1/config/m-linux.h    Mon Feb 15 21:22:30 1993
***************
*** 0 ****
--- 1,36 ----
+ /*
+  * Copyright (C) 1990, 1991 Free Software Foundation, Inc.
+  * Written by Steve Byrne.
+  *
+  * This file is part of GNU Smalltalk.
+  *
+  * GNU Smalltalk is free software; you can redistribute it and/or modify it
+  * under the terms of the GNU General Public License as published by the Free
+  * Software Foundation; either version 1, or (at your option) any later 
+  * version.  GNU Smalltalk is distributed in the hope that it will be useful, 
+  * but WITHOUT ANY WARRANTY; without even the implied warranty of 
+  * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General 
+  * Public License for more details.
+  * 
+  * You should have received a copy of the GNU General Public License along with
+  * GNU Smalltalk; see the file COPYING.  If not, write to the Free Software
+  * Foundation, 675 Mass Ave, Cambridge, MA 02139, USA.  
+  */
+ 
+ /* Linux on i386 or i486 */
+ 
+ /* Define this if the machine in question has a alloca.h that should be
+  * included to get a properly functioning alloca.
+  */
+ #define HAS_ALLOCA_H
+ 
+ /* Define this to use 14 character file names */
+ #define SHORTNAMES
+ 
+ #ifndef FOR_MAKE
+ /* This is the return type of routines that are declarable as signal handlers.
+  * may be void for some implementations
+  */
+ typedef void  signalType;
+ 
+ #endif
diff -w -r -c --new-file smalltalk-1.1.1.old/mstinterp.c smalltalk-1.1.1/mstinterp.c
*** smalltalk-1.1.1.old/mstinterp.c     Fri Sep 13 04:02:36 1991
--- smalltalk-1.1.1/mstinterp.c Mon Feb 15 21:10:12 1993
***************
*** 3618,3624 ****
--- 3618,3626 ----
   */
  void initSignals()
  {
+ #ifndef _POSIX_SOURCE
    signal(SIGBUS, interruptHandler);
+ #endif
    signal(SIGSEGV, interruptHandler);
  
    signal(SIGINT, stopExecuting);
***************
*** 3676,3684 ****
--- 3678,3688 ----
  int   sig;
  {
    switch (sig) {
+ #ifndef _POSIX_SOURCE
    case SIGBUS:
      errorf("Bus Error");
      break;
+ #endif
  
    case SIGSEGV:
      errorf("Segmentation violation");
diff -w -r -c --new-file smalltalk-1.1.1.old/mstmain.c smalltalk-1.1.1/mstmain.c
*** smalltalk-1.1.1.old/mstmain.c       Sat Sep 14 07:15:30 1991
--- smalltalk-1.1.1/mstmain.c   Mon Feb 15 22:51:40 1993
***************
*** 86,92 ****
  #include <sys/types.h>
  #include <sys/stat.h>
  #include <sys/file.h>
! #if defined(USG)
  #include <unistd.h>
  #endif
  
--- 86,92 ----
  #include <sys/types.h>
  #include <sys/stat.h>
  #include <sys/file.h>
! #if defined(USG) || defined(_POSIX_SOURCE)
  #include <unistd.h>
  #endif
  
***************
*** 222,232 ****
    "Boolean.st",
    "False.st",
    "True.st",
! #if !defined(USG) && !defined(atarist)
!   "ProcessorScheduler.st",
! #else
!   "ProcSched.st",
! #endif
    "Delay.st",
    "SharedQueue.st",
    "Behavior.st",
--- 222,228 ----
    "Boolean.st",
    "False.st",
    "True.st",
!   MAP_FILE("ProcessorScheduler.st",  "ProcSched.st"),
    "Delay.st",
    "SharedQueue.st",
    "Behavior.st",
diff -w -r -c --new-file smalltalk-1.1.1.old/mstoop.c smalltalk-1.1.1/mstoop.c
*** smalltalk-1.1.1.old/mstoop.c        Fri Sep 13 04:02:39 1991
--- smalltalk-1.1.1/mstoop.c    Mon Feb 15 23:14:27 1993
***************
*** 77,83 ****
  #define       K               1024
  
  #ifndef atarist
! #define MEM_SPACE_SIZE                (4 * K * K) 
  #else
  #define MEM_SPACE_SIZE                (1152 * K) 
  #endif
--- 77,83 ----
  #define       K               1024
  
  #ifndef atarist
! #define MEM_SPACE_SIZE                (2 * K * K) 
  #else
  #define MEM_SPACE_SIZE                (1152 * K) 
  #endif
diff -w -r -c --new-file smalltalk-1.1.1.old/mstpaths.h smalltalk-1.1.1/mstpaths.h
*** smalltalk-1.1.1.old/mstpaths.h
--- smalltalk-1.1.1/mstpaths.h  Mon Feb 15 20:58:53 1993
***************
*** 0 ****
--- 1,63 ----
+ /***********************************************************************
+  *
+  *    Definitions for various path related things.  These are compiled into
+  *    the GNU Smalltalk interpreter and are used for finding various files
+  *    (the image file, the kernel .st files, etc.).
+  *
+  ***********************************************************************/
+ 
+ 
+ /***********************************************************************
+  *
+  * Copyright (C) 1990, 1991 Free Software Foundation, Inc.
+  * Written by Steve Byrne.
+  *
+  * This file is part of GNU Smalltalk.
+  *
+  * GNU Smalltalk is free software; you can redistribute it and/or modify it
+  * under the terms of the GNU General Public License as published by the Free
+  * Software Foundation; either version 1, or (at your option) any later 
+  * version.
+  * 
+  * GNU Smalltalk is distributed in the hope that it will be useful, but WITHOUT
+  * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or 
+  * FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for
+  * more details.
+  * 
+  * You should have received a copy of the GNU General Public License along with
+  * GNU Smalltalk; see the file COPYING.  If not, write to the Free Software
+  * Foundation, 675 Mass Ave, Cambridge, MA 02139, USA.  
+  *
+  ***********************************************************************/
+ 
+ 
+ 
+ /*
+  *    Change Log
+  * ============================================================================
+  * Author      Date       Change 
+  * sbyrne    15 Oct 89          Created.
+  *
+  */
+ 
+ 
+ /***********************************************************************
+  *
+  *    You'll need to change these definitions if you do not install GNU
+  *    Smalltalk in the standard place (which, as defined here, is
+  *    /usr/local/smalltalk).  You should save this file as mstpaths.h and
+  *    leave mstpaths.h-dist in its original form.
+  *
+  ***********************************************************************/
+ 
+ 
+ #ifndef __MSTPATHS__
+ #define __MSTPATHS__
+ 
+ /* This defines where the kernel smalltalk (.st) files can be found */
+ #define KERNEL_PATH "/usr/local/mst111"
+ 
+ /* This defines where to search for the saved binary image */
+ #define IMAGE_PATH "/usr/local/mst111"
+ 
+ #endif /* __MSTPATHS__ */
diff -w -r -c --new-file smalltalk-1.1.1.old/stix/socket.c smalltalk-1.1.1/stix/socket.c
*** smalltalk-1.1.1.old/stix/socket.c   Thu May 24 23:31:02 1990
--- smalltalk-1.1.1/stix/socket.c       Mon Feb 15 21:04:39 1993
***************
*** 252,258 ****
  int   fd, timeout;
  {
    struct timeval time, *timePtr;
! #ifdef SUNOS4
    fd_set      fds;
  
    FD_ZERO(&fds);
--- 252,258 ----
  int   fd, timeout;
  {
    struct timeval time, *timePtr;
! #if defined(SUNOS4) || defined(linux)
    fd_set      fds;
  
    FD_ZERO(&fds);
diff -w -r -c --new-file smalltalk-1.1.1.old/ymakefile smalltalk-1.1.1/ymakefile
*** smalltalk-1.1.1.old/ymakefile       Fri Sep 13 04:02:45 1991
--- smalltalk-1.1.1/ymakefile   Mon Feb 15 21:01:26 1993
***************
*** 121,130 ****
  /* Compilation flags definitions */
  CFLAGS_NORMAL   = -g EXTRA_CC_FLAGS 
  CFLAGS_PROFILE  = -g -pg -DUSE_MONCONTROL EXTRA_CC_FLAGS 
! CFLAGS_OPTIMIZE = -O -DOPTIMIZE EXTRA_CC_FLAGS 
  
  /* Actual compilation flags and compiler definition */
! CFLAGS = $(CFLAGS_NORMAL) $(READLINEDEF)

  
--- 121,130 ----
  /* Compilation flags definitions */
  CFLAGS_NORMAL   = -g EXTRA_CC_FLAGS 
  CFLAGS_PROFILE  = -g -pg -DUSE_MONCONTROL EXTRA_CC_FLAGS 
! CFLAGS_OPTIMIZE = -O2 -DOPTIMIZE EXTRA_CC_FLAGS 
  
  /* Actual compilation flags and compiler definition */
! CFLAGS = $(CFLAGS_OPTIMIZE) $(READLINEDEF)

  
***************
*** 197,204 ****
        @echo "the diffs file that you've created.  End with Ctrl-D."
        @cat > mst.diffs.note
        @echo "-----------------------------------" >> mst.diffs.note
!       @### If there's a more portable/better way to do this, please
!       @### don't hesitate to fix this and send the new version back -- SBB
        @cat mst.diffs.note mst.diffs | mail $(MAINTAINER)
  
  diffs:
--- 197,204 ----
        @echo "the diffs file that you've created.  End with Ctrl-D."
        @cat > mst.diffs.note
        @echo "-----------------------------------" >> mst.diffs.note
!       @### If there is a more portable/better way to do this, please
!       @### do not hesitate to fix this and send the new version back -- SBB
        @cat mst.diffs.note mst.diffs | mail $(MAINTAINER)
  
  diffs:

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

From: [email-masked] (Trink Andreas)
Subject: Re: DoubleSpace Filesystem
Date: 22 Sep 1994 12:02:22 GMT

Matthew S. Richmond (mattr@h4snap) wrote:
: Thomas Scheuermann ([email-masked]) wrote:
: : Title        = Linux Filesystem for DoubleSpace (readonly)
: : Version      = 1.0
: : Desc1        = With this kernel module Linux is able to read
: : Desc2        = a DoubleSpace compressed Filesystem.

: Are there any plans to make this work with Drive Spaced drives since
: Doublespace is no longer used since Stacker won the lawsuit against
: Micro$oft?  Thanks

: --Matt Richmond
: --
: [email-masked]             |  The opinions expressed herein are my 
:                                       |  own and do not necessarily reflect 
: That which does not kill us, makes us |  those of E-Systems, Melpar.
: strong.                               |
:           --Freidrich Nietzsche       |
     ^
     |
A leg-amputation does not kill me, also it makes me strong!

======================================================================
 Trink Andreas                     |  Tel: 0316-873-7456
                                   |  Fax: 0316-463697
 Institut fuer Nachrichtentechnik  |  EMail: [email-masked] 
 und Wellenausbreitung, TU Graz    |         [email-masked] 
 Inffeldgasse 12                   |
 A-8010 Graz                       |
======================================================================
                            Sapere aude!
======================================================================

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

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

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

    Internet: [email-masked]

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