Subject: Linux-Misc Digest #591
From: Digestifier <Linux-Misc-Request@senator-bedfellow.MIT.EDU>
To: Linux-Misc@senator-bedfellow.MIT.EDU
Reply-To: Linux-Misc@senator-bedfellow.MIT.EDU
Date:     Mon, 24 Jan 94 07:13:22 EST

Linux-Misc Digest #591, Volume #1                Mon, 24 Jan 94 07:13:22 EST

Contents:
  Re: CAS for Linux (was Re: Mathematica for Linux) (Alexander Schliep)
  Re: Linux as X-Terminal? No! (Amancio Hasty Jr)
  Re: PPP slower than SLIP! (Michael Horwath)
  Re: Advice on multi-serial cards wanted... (Michael Horwath)
  Re: Bogomips Information Sheet (Frank Lofaro)
  NEC CDR-25 (Ernie Elu)
  Where is a 680*0 kernel ? (Bo-Erik Sandholm)
  *** PLEASE READ THIS BEFORE POSTING *** (misc-2.07) (Ian Jackson)
  MSDOS Better than Linux (Julian D Glover)
  Re: Fortran compilers for linux? (Bill C. Riemers)
  Re: How much disk for Slackware 1.1.1 (Jay Maynard)
  Re: Global Alert For All: Jesus is Coming Soon (J.J. Paijmans)

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

Crossposted-To: sci.math.symbolic
From: schliep@chopin.udel.edu (Alexander Schliep)
Subject: Re: CAS for Linux (was Re: Mathematica for Linux)
Date: Wed, 19 Jan 1994 17:46:37 GMT


Well maybe the producer of CAS system are more interested how many people
willing to spend big bucks for their programs are using Linux.

My (admittely uneducated) guess would be that not too many Universities
or companies use Linux ... and I dont think that anybody wants to do a port
to a new OS just to sell a couple of hundreds student versions.
(I am refering to the OS and platform used for general computing above and not
somebodys personal machine).

You could have more luck porting shareware/free stuff to Linux. There was an
article in the AMS Notices last year with math software and there is also
a list which is posted here from time to time (or can ge ftp'd from
berkeley.math or so -- I am getting old, I forgot the exact address).

Good luck,
Alexander


Alexander Schliep               501 Ewing Hall          phone: (302) 831-6920
Department of Mathematics       Newark, DE 19716        fax: (302) 831-4511
University of Delaware                                  
schliep@math.udel.edu           schliep@strauss.udel.edu

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

Crossposted-To: comp.windows.x.i386unix
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: Linux as X-Terminal? No!
Date: Mon, 24 Jan 1994 05:54:04 GMT

>
>Not to my knowledge- but rest assured that Xterminal speeds will most likely
>increase also (its not an industry in a vacuum).  Personally, I think that
>100k xstones is about all that is needed in most circomstances- it is very
>much more comfortable than the < 10k xstone performance of typical ET4000
>cards (a factor of 10) ; but I'm not sure that a factor of ten more
>(1,000,000) would be that much more noticable (perhaps a human perception
>thing).
Would not be surprised to see a special ASIC to handle the X protocols
to generate 1,000,000k xstones (Please don't ask me about this because this
all I know)

As far as I am concerned the et4000 is obsolete;nevertheless, I understand
your point. The current 2D technology in the leading graphic card's
technology such as the Viper, Matrox MGA, #9 S3 928 based cards are
perhaps more than adequate performance wise. However, once we
entered animation, 3D graphics, Video, or Virtual Reality I don't see a 
place for X terminals.


My current pet projects are sound and a Virtual Reality system and
I will deliver :-)

        Enjoy,
        Amancio



-- 
FREE unix, gcc, tcp/ip, X, open-look, interviews, tcl/tk, MIME, midi, sound
at  freebsd.cdrom.com:/pub/FreeBSD
Amancio Hasty,  Consultant |
Home: (415) 495-3046       |  
e-mail hasty@netcom.com    |  ftp-site depository of all my work:    
ahasty@cisco.com           |  sunvis.rtpnc.epa.gov:/pub/386bsd/X

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

From: drechsau@winternet.mpls.mn.us (Michael Horwath)
Crossposted-To: comp.os.linux.help
Subject: Re: PPP slower than SLIP!
Date: 24 Jan 1994 06:08:19 GMT

Rene COUGNENC (rene@renux.frmug.fr.net) wrote:
: Ce brave Michael Horwath ecrit:

: > Rene COUGNENC (rene@renux.frmug.fr.net) wrote:
: > : PING ftp.ibp.fr (132.227.60.2): 56 data bytes
: > : 64 bytes from 132.227.60.2: icmp_seq=7 ttl=179 time=158 ms

: > I wish I could get ping times like that on my system (and a friend is
: > thinking the same thing right here over my shoulder). 

: One thing to have in mind whith modern modem links such as v32bis or more,
: is that the connection speed may often not be really 14400, but a
: slower fallback speed, depending on the phone line quality, the modem
: quality, and many other things.

[some deleted about modem speeds]

:  linux linux linux linux -[ cougnenc@renux.frmug.fr.net ]- linux linux linux 

We are just talking ping here.  Response times and ftp times are doing just
fine, it is just the ping that seems very very very slow and we are wondering
why that is, and if it is related to the MTU (MRU) size, then we can play
some with our termserver and see if changing the MRU (for PPP) from 1500
to 512 makes a difference.  It should, but I don't want to slow the FTPs
down, at the expense of faster ping/response time.

--
Mike Horwath   IRC: Drechsau  LIFE: Lover   drechsau@winternet.mpls.mn.us
Winternet:  info@winternet.mpls.mn.us       root@jacobs.mn.org <- Linux!
Twin Cities area Internet Access:  612-941-9177 for more info

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

From: drechsau@winternet.mpls.mn.us (Michael Horwath)
Subject: Re: Advice on multi-serial cards wanted...
Date: 24 Jan 1994 06:17:21 GMT

Mark and Mark (Bentley knows me :):

If you are going to go above about 8 ports, try out a termserver.  I just
got one for StarNet (the winternet.... address uses one) is just great.

Remove the IRQ load off of your machine, with that many lines, I would
rather have interrupts created for the ether than for upteen serial ports.

Yes, I know, the interrupts are fast and services regulary, but with the
ANNEX Micro XL I have, I can have it send packets based on how many 
characters received or a timeout, which ever comes first, and can run
all 16 ports at 57600 without adding the load of 16 serial ports on the
machine itself.

--
Mike Horwath   IRC: Drechsau  LIFE: Lover   drechsau@winternet.mpls.mn.us
Winternet:  info@winternet.mpls.mn.us       root@jacobs.mn.org <- Linux!
Twin Cities area Internet Access:  612-941-9177 for more info

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

From: ftlofaro@unlv.edu (Frank Lofaro)
Subject: Re: Bogomips Information Sheet
Date: Mon, 24 Jan 94 07:44:24 GMT

In article <759356356.29635@minster.york.ac.uk> al-b@minster.york.ac.uk writes:
>In article <2ht7fi$908@raffles.technet.sg>,
>Mathias Koerber <mathias@solomon.technet.sg> wrote:
>>In (<2hhgeq$3s1@klaava.Helsinki.FI>) Wim van Dorst (baron@clifton.hobby.nl) wrote:
>>| [ Moderator's note: This is LaTeX code, for those who don't recognize it at
>>|   sight.  --liw ]
>>
>>| 486DX2/66 ICL ErgoPRO     & 33.55 & mathias@solomon.technet.sg (Mathias Koerber) \\
>>This was under SLS 1.03, the same machine (no changes) prints 33.22 under 
>>Slackware 1.1.0. Any idea why this difference?
>
>My 486DX2/66 with 0.99.13 kernel alternately prints 33.22 and 33.55!
>The choice seems to be random, though it does seem to prefer the
>33.55 (hooray).
>
>Andrew.
>

Hmm, my 486DX33 alternates between 16.61 and 16.77 (exactly half)!

It unfortunately goes for the 16.61 most of the time.

My kernel hacking (totally unrelated) has an effect, it seems to make it 
prefer 16.61 more :( It might have to do with alignment of the Bogo-code :)

Before I upgraded from 4 to 8 MB, I always only got 16.61, btw.
(this included upping the cache from 128 -> 256 K)



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

From: ernie@werple.apana.org.au (Ernie Elu)
Subject: NEC CDR-25
Date: 24 Jan 1994 21:00:06 +1100

Does any one know if an NEC CDR-25 which is their low speed external SCSI 
CD ROM drive will work with Linux ? I have the opportunity to pick one up
cheap, but there is no point if it doesn't work with Linux.

- Ernie.




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

From: bosse@ericsson.se (Bo-Erik Sandholm)
Subject: Where is a 680*0 kernel ?
Date: 24 Jan 1994 08:36:43 GMT
Reply-To: bosse@ericsson.se

I have a friend who is interested in porting Linux to a 680*0 platform.
I have a memory of somebody already having done some work in this
direction, can any body give me a pointer.

---
Bo-Erik Sandholm   bosse@snoddas.ericsson.se
Working for Ericsson Telecom Stockholm, Sweden


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

From: ijackson@nyx.cs.du.edu (Ian Jackson)
Subject: *** PLEASE READ THIS BEFORE POSTING *** (misc-2.07)
Date: Mon, 24 Jan 1994 11:03:01 GMT

Please do not post questions to comp.os.linux.misc - read on for details of
which groups you should read and post to.

Please do not crosspost anything between different groups of the comp.os.linux
hierarchy.  See Matt Welsh's introduction to the hierarchy, posted weekly.

If you have a question about Linux you should get and read the Linux Frequently
Asked Questions with Answers list from sunsite.unc.edu, in /pub/Linux/docs, or
from another Linux FTP site.  It is also posted periodically to c.o.l.announce.

In particular, read the question `You still haven't answered my question!'
The FAQ will refer you to the Linux HOWTOs (more detailed descriptions of
particular topics) found in the HOWTO directory in the same place.

Then you should consider posting to comp.os.linux.help - not
comp.os.linux.misc.

Note that X Windows related questions should go to comp.windows.x.i386unix, and
that non-Linux-specific Unix questions should go to comp.unix.questions.
Please read the FAQs for these groups before posting - look on rtfm.mit.edu in
/pub/usenet/news.answers/Intel-Unix-X-faq and .../unix-faq.

Only if you have a posting that is not more appropriate for one of the other
Linux groups - ie it is not a question, not about the future development of
Linux, not an announcement or bug report and not about system administration -
should you post to comp.os.linux.misc.


Comments on this posting are welcomed - please email me !
--
Ian Jackson  <ijackson@nyx.cs.du.edu>  (urgent email: iwj10@phx.cam.ac.uk)
2 Lexington Close, Cambridge, CB4 3LS, England;  phone: +44 223 64238

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

From: univ0020@black.ox.ac.uk (Julian D Glover)
Subject: MSDOS Better than Linux
Date: Mon, 24 Jan 1994 11:24:19 GMT

In terms of real world work you lusers should realise that MS-DOS and
MS-Windows is far better than some half assed Unix toy, get a life and
pay for your software like everyone else you spongers.




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

From: bcr@bohr.physics.purdue.edu (Bill C. Riemers)
Subject: Re: Fortran compilers for linux?
Date: 24 Jan 94 05:20:33 GMT

In article <tgmCK1xJv.LHv@netcom.com> tgm@netcom.com (Thomas G. McWilliams) writes:
>Tim Bandy (timn8r@eelpout.micro.umn.edu) wrote:
> > I have searched high and low, yet found no trace of a fortran
> > compiler for linux.  If any of you out there in the great 
> > unknown know of where I can find one, that would be
> > simply Maaaahhhvelous.  
> > email to timn8r@mermaid.micro.umn.edu

>There is a Fortran compiler under development by the FSF. It is
>due to be released a year or two after GNU Hurd. :-)

Whoever told you this was full of hot air.  Here is the official status
report of g77:


GNU Fortran alpha testers acct (fortran)
Home: /home/gd2/fortran
Shell: /usr/local/gnubin/bash
Mail forwarded to burley.
GNU Fortran alpha testers acct (fortran) is not presently logged in.
Last seen at mole.gnu.ai.mit.edu on Tue Dec  7 10:30:36 1993


Plan:
CONTENTS OF THIS FILE: (last updated 93/12/06)

-  GNU FORTRAN AVAILABILITY (93/05/19)
-  ALPHA TEST STATUS (93/12/06)
-  WHAT IS GNU FORTRAN? (93/04/08)
-  WHAT WILL GNU FORTRAN SUPPORT? (93/05/19)
-  HOW TO GET F2C (93/05/19)
-  IMPORTANT EMAIL ADDRESSES (93/05/19)
-  HOW TO GET THIS FILE (93/09/29)


GNU FORTRAN AVAILABILITY (last updated 93/05/19)
========================

GNU Fortran (g77) is in private alpha test (as of September 26, 1992).
The Free Software Foundation (FSF) has no idea when g77 will be
fully released to the public.  Until then we advise people to use
f2c (a FORTRAN-to-C translator) and gcc (the GNU C compiler).  As
g77 is largely based on these two tools (the f2c libraries and the
gcc back end), your use of them will help speed the release of g77.

Both f2c and gcc are available from the FSF.  Ask gnu@prep.ai.mit.edu or

    Free Software Foundation
    675 Massachusetts Avenue
    Cambridge, MA  02139
    +1-617-876-3296

for details on ordering them.


ALPHA TEST STATUS (last updated 93/12/06)
=================

I am now working on g77-0.4, which consists of removing lots of
code that is present to make early debugging and testing of g77
fairly easy (including some internal consistency checks).  This
should make g77 smaller and faster, and somewhat easier to maintain
now that preliminary testing is basically done.  I'm hoping to
release g77-0.4 by 93/12/20, but that's just a guess.


The latest private alpha-test release of g77 is:

    g77-0.3.12     (93/11/16 11:00) -- the front end
    ss-931113      (93/11/16 11:00) -- the back end

Changes in g77-0.3.12:
    Cleanup patch for patching up to ss-931113

Changes in g77-0.3.11:
    CHARVAR(:I) now works, just as CHARVAR(1:I) did

    "g77 -o foo foo.f" now works in cases where it didn't before

Changes in g77-0.3.10:
    Enable DIMAG intrinsic when double-complex intrinsics enabled

Changes in g77-0.3.9:
    Fix silly bug causing g77 to reject passing arrays as actual arguments

Changes in g77-0.3.8:
    g77 no longer rejects intrinsics as disabled
    COMPLEX FUNCTIONs no longer crash g77
    LOC(), %LOC(), %VAL(), %REF(), and %DESCR() now supported

Changes in g77-0.3.7:
    DCMPLX(ONEARG) no longer crashes (two args was fine)
    .EQ. and .NE. on COMPLEX*16 operands no longer crashes
    Assigned GOTO with no label list can no longer crash

Changes in g77-0.3.6:
    Fix g77 front end to use back end facility in a manner required by
        the back end but not clearly documented by it; this fixes
        bugs in SIGN, ISIGN, DSIGN, ISHFT, ISHFTC, and MVBITS intrinsics

Changes in g77-0.3.5:
    Disabled intrinsics now produce diagnostics when passed by name as
        actual arguments to procedures
    Passing intrinsics by name as actual arguments to procedures no longer
        has the potential to crash g77

Changes in g77-0.3.4:
    Disabled intrinsics now produce proper diagnostics when referenced

Changes in g77-0.3.3:
    g77 should now build for host/target combinations where the compiler
        emulates floating-point arithmetic (instead of using the host's
        float/double data types) to compile for the target
    Some minor improvements to ease building g77 on sun-sparc-sunos4.1*
        targets
    Stand-alone front end now builds cleanly
    More intrinsics involving DOUBLE COMPLEX now accepted as long as
        -fdcp-intrinsics-enable specified, even if f90, f2c, or vxt
        intrinsics aren't enabled

Changes in g77-0.3.2:
    Compiler crashes with "no type for size" fixed (was just some
        debugging code that should have been removed, but the whole
        area has been improved with this patch)

Changes in g77-0.3.1:
    NAMELIST involving variables/arrays not given initial values via DATA
        or equivalent no longer crashes
    New g77 optimization for certain cases of COMPLEX function invocations
        no longer crashes complex division
    CHARACTER*(*) arguments in ENTRY following executable statements
        no longer crashes
    FILE= in OPEN may be omitted when STATUS='OLD' or 'NEW' specified
        now, though -pedantic produces a diagnostic
    DO loops (implied and regular) with REAL or DOUBLE PRECISION
        iterators no longer crash
    Compiled name of blank common changed for better f2c
        compatibility; other stuff like this done as well


    Lots of changes to improve source code maintainability
    Intrinsic subroutines now supported (MVBITS is the only one so far)
    NAMELIST implemented
    Better code generation (primarily for invoking COMPLEX-returning
        intrinsic or user functions)
    Subroutine with no alternate returns no longer bothers to return
        integer 0 (slight optimization)
    CHAR() now works
    Implicit conversion of/to DOUBLE COMPLEX now works
    REAL() on DOUBLE COMPLEX now works
    C1.NE.C2 now works for REAL(C1).NE.REAL(C2).AND.IMAG(C1).EQ.IMAG(C2)
    Crashes with -O fixed
    Longstanding back-end problems (crashes) with COMPLEX fixed
    LEN(A//B) now works

Bugs pending or being worked on:
    Back-end crash on some machine(s)
    Front-end crash following g77 diagnostics on at least some machines
        -- fixed
    Need to improve -g so it at least doesn't crash or produce invalid
        intermediate assembler file


WHAT IS GNU FORTRAN? (last updated 93/04/08)
====================

GNU Fortran is the Fortran development system for Project GNU.  GNU
means "GNU's Not UNIX(tm)" and is the primary project currently being worked
on by the Free Software Foundation (FSF), a non-profit organization
committed to the creation of a large body of useful, free, source-code-
available software.  GNU is intended as a replacement, wholesale and/or
in pieces, of a complete UNIX system.  (UNIX is a trademark of AT&T.)

GNU Fortran, also called g77, consists of a compiler, run-time libraries,
debugger support, and documentation.  g77 supports ANSI FORTRAN 77
conformance, plus popular extensions to Fortran including some ANSI/ISO
Fortran 90 features.

The g77 compiler is a combination of a "front end" that translates
Fortran source programs and a "back end" that uses the results of the
translation to make an object or executable file that performs the
actions specified by the source programs when run.  The back end is
the same back end used by GNU C, C++, and Objective-C, which have their
own front ends to translate their respective languages.  Other front ends
for Pascal and ADA are in progress.

The run-time libraries for g77 are currently whatever is compatible with
the libraries used by the f2c program, a public-domain Fortran-to-C
converter from AT&T Bell Laboratories and Bellcore.  f2c comes with its
own libraries (written in C) for systems that don't already have compatible
libraries. By using the same libraries, procedures compiled by g77 and f2c
can be freely mixed to create an executable program.  However, g77 is unable
to offer some popular extensions that aren't supported by f2c-compatible
libraries, and the interface to the libraries isn't necessarily a
high-performance design.  Thus, use of the f2c library interface might
be a short-term thing.  (SEE BELOW for "HOW TO GET F2C".)

Debugger support for g77 consists of compiler code to output the appropriate
debugging information when -g is specified at compile time plus code in
the GNU Debugger, GDB, to support evaluation of Fortran expressions.

The private alpha test is called "private" because the source code making
accepted by the author of GNU Fortran should have a copy of g77 currently.
It is called "alpha" because it is the first phase of testing (alpha is the
first letter of the Greek alphabet).  There are around 30 or so alpha
testers in locations all over the U.S.A., including testers in Norway,
Brazil, the U.K., Canada, France, Denmark, and, yes, even New Jersey!
As alpha test winds down (as necessary features are added and the bug-rate
gets lower), plans will be made to go to beta test (the second phase of
testing), which will be a public release.

The primary focus of the alpha test is to test the g77 front end, since that
has most of the new code.  The secondary focus of the alpha test is to test
the integration between the front end and the back end.  Currently, this is
where most of the bugs seem to be.  The tertiary focus is the quality of
code generated by the GNU back end.

There are no schedules regarding future events such as when beta test will
happen, when documentation will be written, and so on.  The GNU Fortran
effort so far is entirely voluntary, and delays might happen due to the
need to earn income, so the best way to assure rapid delivery of a high-
quality free Fortran system is to offer donations or other forms of funding
to the author and/or the FSF.


WHAT WILL GNU FORTRAN SUPPORT? (93/05/19)
==============================

The quickest answer to this question is "GNU Fortran does or will soon
support any reasonably portable feature already supported by f2c used
in conjunction with gcc and the f2clib (libI77 and libF77) libraries".

Some f2c command-line options aren't supported, and might not be for
a while, including the run-time array-bounds-checking option, just
because there seem to be more important things to do first.

GNU Fortran already supports many features f2c doesn't, such as the
MIL-STD 1753 intrinsics, some Fortran-90 features like SELECT CASE
(not for CHARACTER types yet, however), no limit on the number of
continuation lines for a single statement, and so on.  As development
progresses, more information will be available.


HOW TO GET F2C (last updated 93/05/19)
==============

While waiting for GNU Fortran to become available, you might want to
use a free program called f2c, a Fortran-to-C converter whose output,
compiled by a quality C compiler (such as GNU C) and linked with the
f2c (or compatible) libraries (called F77 and L77, though they can be
stuck together, and often are, in a library called f2c), produces
an executable for the input Fortran program.  It works quite well,
supports ANSI FORTRAN 77 plus some popular extensions, and bug fixes
are made to it quite rapidly in response to bug reports.

f2c is available on tape from the FSF.  Get ordering info from
gnu@prep.ai.mit.edu.  The latest version also is available via anonymous
ftp to various GNU sites including prep.ai.mit.edu.

I obtain the very latest version via ftp to research.att.com, login
as "netlib", giving your email address as the password.  (Netlib is widely
used in the numerical computing community; for general information on
netlib, send the e-mail message "send index" to netlib@research.att.com,
netlib@ornl.gov, or netlib@nac.no.)

Then, I do "type binary", "cd f2c", and obtain the following files,
depending on what I need:

readme.Z -- a file describing what f2c is and what to do
libf77.Z -- the (compressed shar archive) sources to the F77 (non-I/O)
            run-time library
libi77.Z -- the (compressed shar archive) sources to the I77 (I/O)
            run-time library
src/*.Z  -- the (compressed) sources, mostly in C, to the f2c converter
            itself
fixes.Z  -- a list of recent fixes and version/checksum stamps for sources
f2c.h.Z  -- the header file needed when compiling f2c output (the C code)

Configuring and installing f2c for various machines doesn't appear to
be too difficult.  There are MS-DOS executables (one using extended/
expanded memory, one not) in the msdos subdirectory; these seem to
be rebuilt fairly often from a recent f2c release.


IMPORTANT EMAIL ADDRESSES (last updated 93/05/19)
=========================

fortran@gnu.ai.mit.edu
    Send email here to contact the author and/or current maintainer of GNU
    Fortran at the FSF, if you don't already know who that is.

info-gnu-fortran@prep.ai.mit.edu
    The GNU Fortran Mailing List (moderated).  Status info is occasionally
    posted to this list regarding the alpha test, plans or questions about
    g77 and Fortran in general, and so on.

info-gnu-fortran-request@prep.ai.mit.edu
    Send email to this address to get added to the above mailing list.

gnu@prep.ai.mit.edu
    Send email to this address to get information on the FSF and Project GNU.

lpf@uunet.uu.net
    Send email to this address to get information on the League for
    Programming Freedom (LPF), a political organization that is trying to
    make sure that projects like GNU Fortran aren't shut down now or in the
    future because of increasing legal barriers to the free flow of
    information (the essential component of all software) in the U.S.A. and
    elsewhere.


HOW TO GET THIS FILE (last updated 93/09/29)
====================

How to get information on GNU Fortran (the .plan file for user
fortran at Project GNU):

If you can do finger -l, try:

    finger -l fortran@gate.gnu.ai.mit.edu

If that produces output of around 250 lines, then it probably works.

Otherwise, if you can do ftp, try:

    ftp gate.gnu.ai.mit.edu
    Username: ftp

    get g77.plan

The ftp copy of the file is updated every 3 hours from the live copy.

NOTE: Try gate-1.gnu.ai.mit.edu, gate-2.gnu.ai.mit.edu, or
      gate-3.gnu.ai.mit.edu if you are having problems with
      gate.gnu.ai.mit.edu.

Otherwise, you could try sending email to user fortran@gnu.ai.mit.edu
asking to be sent the latest copy of the file, but _please_ make this
your last option, because it requires human intervention!



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

From: jmaynard@nyx10.cs.du.edu (Jay Maynard)
Subject: Re: How much disk for Slackware 1.1.1
Date: Mon, 24 Jan 94 11:42:39 GMT

In article <2hugmk$hf0@spitfire.navo.navy.mil>,
Rick Slater <slater@nrlssc.navy.mil> wrote:
>A minimal installation would probably consist of only the three A disks
>and the four AP disks.  That would occupy fewer than 20 megabytes of
>disk.  If you left the AP disks out, you would need around 10 megs of
>space, but you couldn't do much with what you had. -- Rick

Actually, you can do better than that, if you're careful about what you 
install. I installed pieces of the A, AP, N, and Y packages on my system, and 
have quite a usable system in 15 meg (+about 9 meg of swap partition). The key 
is leaving off some notorious disk hogs...like, for example, Ghostscript.

>P.S.  I'm *very* *very* pleased with the Slackware installation,
>as compared to an SLS installation that I did more than a year ago.
>The Slackware material has all run correctly right "out of the box"
>with only a few tiny glitches.  It's a very professionally organized
>installation system, and is a real asset to the Linux community.

I'm pleased with Slackware 1.1.1 also. After I fixed one install script bug, 
it went in smoothly, even in 2 meg of RAM. No problems in running at all. Now, 
to add more hard disk...
--
Jay Maynard, EMT-P, K5ZC, PP-ASEL | Never ascribe to malice that which can
jmaynard@oac.hsc.uth.tmc.edu      | adequately be explained by stupidity.
        "A good flame is fuel to warm the soul." -- Karl Denninger

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

From: paai@kub.nl (J.J. Paijmans)
Subject: Re: Global Alert For All: Jesus is Coming Soon
Date: Mon, 24 Jan 94 11:15:13 GMT

In article <1994Jan22.215949.4291@persys.sta.sub.org> jayes@persys.sta.sub.org (Juergen Schreier) writes:
...
>them).
>Yes I do think everybody should have the right to express his views but I want to have the
>right not to listen to (here: not to read) it if I don't want to !!!
>
>Cheers
>     Juergen

Check your keyboard. Even on german keyboards you can occasionally find
a 'n' or a 'k'. OK, Satan and Jezus are no subjects for comp.os groups,
but the infinitesimal extra tear and wear on Internet, in my view,
are worth the occasional laugh. And if you don't want extra traffic,
then DON'T REACT.
:-)
Paai.




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


** 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-Misc-Request@NEWS-DIGESTS.MIT.EDU

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

    Internet: Linux-Misc@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-Misc Digest
******************************
