HDTenEightyP/NetNews huggingface dataset:
From: "William L. Mullica" <p00192@psilink.com>
Subject: Emacs w/SLS 0.98
Organization: Performance Systems Int'l
Date: Mon, 16 Nov 1992 02:18:23 GMT
X-Mailer: PSILink-DOS (3.3)

I recently upgraded from SLS 0.96 to 0.98. Before, my emacs was setup to 
handle extended keyboard codes. The HOME key would cause the cursor to 
go to the start of a line, the END key to the end of the line, F10 would 
exit emacs just like C-x C-c, etc. Now, none of these keys seem to work 
anymore. I even got a copy of a friend's /.emacs file from 0.96 and put 
it on my 0.98 system: still no support for HOME, END, etc.

What gives? How can I get the extended key codes to be recognized again?
If there are some key definitions that I can add to my .emacs file, 
please let me know what they are and I'll put them in.

Thanks.

Bill Mullica

Newsgroups: comp.os.linux
From: aviz@lanai.cs.ucla.edu (Dr Algirdas Avizienis)
Subject: Problems w/MudOS 0.9(LPmud) and Linux..
Organization: UCLA, Computer Science Department
Date: Mon, 23 Nov 92 01:12:16 GMT

	Hello, I'm having trouble gettin the MudOS 0.9.3 driver to compile
under linux.  I'm using 0.98.5 with the three tcp patches.  The problem
is kinda strange.  It compiles fine now, and it loads what it need to load
into memory, but after that, when it tries to set up the IPC, I get messages
from the kernel along the lines of, "kernel unable to process request" or
somesuch, and I know somehow I should be able to look up what the problem
is in System.map, but I don't know what exactly it is that I am supposed to
do.  Could someone give me some advice?  Thanks a lot.
From: kevin@cyber.net (Kevin R. Sanders)
Newsgroups: comp.os.linux
Subject: Re: Empire Progress?
Keywords: empire, linux
Date: 20 Nov 92 18:52:17 GMT
Organization: The Cyberspace Station

In article <1992Nov19.135357.4405@lynx.dac.northeastern.edu> pclark@lynx.dac.northeastern.edu (Peter Clark) writes:
>Um, wouldn't KSU be a better version to port?
>
Well, I asked the folks at rec.games.empire which was the latest version
of the game, and this (chainsaw 2.1) was the consensus.  Personally I last
played empire when I was in school, back in the dark ages of 1982-83.
I am aware of several new features (distributions of commodities rather
than just routing, different plane types, ucw's, to name a few); these
are all present in the Chainsaw distribution.  All the trade and loan stuff
seems to have been disabled in this distrribution however.

What are your compelling reasons why I should be porting KSU?  I imagine
that once one version is ported, porting the other should be much simpler since
I will have already solved the problems I am likely to encounter.  I am not
against switching to KSU later if that proves to be a better version; I would
like to finish this one first, just to get something out there.

Porting is going OK; currently the "power" command crashes the server, and
there are some parsing problems with some commands, and the "build" command
does not work.  I have been able to explore, grow civs, produce things, and
attack however.  So I'd say it's going faster than planned.
-- 
---------------------
Kevin Sanders, KD6FKJ
kevin@cyber.net
Newsgroups: comp.os.linux
From: cs911169@ariel.yorku.ca (Douglas W. F. Acheson)
Subject: Floppy Drives
Organization: York University, Toronto, Canada
Date: Wed, 18 Nov 1992 03:10:49 GMT

HI,

I have just installed linux on my PC and am having a hard time to do
the following:

mounting the floppy drives (so I can read write to them)
using mtools with the floppy drives

I would appreciate it if someone could get back to me so I could chat
with them about the problem.  E-mail is preferred.  Thanks in advance


     ######################################################################
     # Douglas W. F. Acheson                                              #
     # Internet E-mail cs911169@ariel.yorku.ca                            #
     # President York University Computer Club 92/93                      #
     #--------------------------------------------------------------------#
     #                  Space the final frontier.....                     #
     # These are the voyages of the starship Enterprise.  Its 5 year      #
     # mission to explore strange new worlds to seek out new life and new #
     # civilizations to boldly go where no man has gone before!           #
     #                                    Captain J. T. Kirk              #
     ######################################################################
Newsgroups: comp.os.linux
From: hlu@eecs.wsu.edu (H.J. Lu)
Subject: Re: a shell idea
Organization: School of EECS, Washington State University
Date: Mon, 16 Nov 92 18:53:29 GMT

In article <1e8m7pINN51i@usenet.INS.CWRU.Edu>, mal11@po.CWRU.Edu (Matthew A. Lewis) writes:
|> 
|> 
|> 
|> i was thinking that one could create a "super" shell which understood
|> the syntax of all the major shells: csh, tcsh, ksh, sh, bash, ash, etc.
|> of course, size would be affected, but imagine the power, not to 
|> mention the end of all the bickering.
|> 

zsh is what you are looking for.

H.J.
Newsgroups: comp.os.linux
From: wissner@beech.mcs.gvsu.edu (Jim Wissner)
Subject: something's freaking out olvwm
Organization: Grand Valley State University
Date: Fri, 20 Nov 1992 19:36:29 GMT


Has anybody else had strange problems with olvwm?  For some
reason, when I try to use it, it brings X down, complaining
about some sort of memory problem (can't remember exact words).
Oddly enough, twm works just fine.

I've been using olvwm for a heck of a long time now, and have
never had any problems.  This seems to be happening on pl4 and 5.
I've recompiled; it's not just an old binary.  I'm using HLU's
package on a 486-33, 12mb RAM, tseng, etc etc.  I've had the
same setup for quite a while (I did get a new drive; but have a
hard time picturing /that/ causing this problem).

I follow the group and haven't seen anyone else ask about this,
so I'm assuming that I'm just missing something blatantly obvious.
Any clues would be great; else I'm probably just stumble upon it.

- Jim
Newsgroups: comp.os.linux
From: koch@rtsg.mot.com (Clifton Koch)
Subject: Problems with TCP/IP and .98pl5
Organization: Motorola Inc., Cellular Infrastructure Group
Distribution: usa
Date: Mon, 23 Nov 1992 01:13:49 GMT

  Subject line says it.  I took the plunge and decided to get TCP/IP going,
because I want to try and run a SLIP link in the near future.  After much
hair pulling over configuration it's sort of working, but not very well.

  First, the code compiled fine.  No problems if I run with the code compiled
and nothing configured.  I added the 3 pl5 patchs to a clean copy of the pl5
kernel went from there.

  With a loopback device and local IPaddress configured, I can telnet to them,
but only if I use the IPaddress itself.  The 'connected...' message comes back
immediately, but it takes about 2 minutes for the login prompt to come up, and
then everything seems to work OK.  If I try to start another telnet session
to the same address while the first one is waiting around, the first one ends
with connection closed by other end.

  Using the name (i.e. telnet loopback) just hangs telnet.

  After running rc.net, my system also seems to be in a unstable
state.  When I back out of X with <ctrl><alt><bksp> and then try to reboot with
<ctrl><alt><del>, the system hangs.  I've also had the system come crashing
down and reboot while playing with telnet.  I also can't get a printer daemon
to work at all when inetd is running.

  Anyone have any helpfull hints??  I'm still bashing at it, but I'm not real
familiar with the innerworkings of TCP/IP (yet).

CVK
-- 
-----------------------------------------------------------------------------
    Cliff Koch
    Motorola Cellular Infrastructure Division
    koch@rtsg.mot.com
From: makisara@vtinsx.ins.vtt.fi (Kai Makisara)
Newsgroups: comp.os.linux
Subject: Re: X11: Number of colors significant
Date: 20 Nov 92 18:24:33
Organization: Technical Research Centre, Instrument Lab., Espoo, Finland
NNTP-Posting-Host: vtinsy.ins.vtt.fi
In-reply-to: tex@ipf.bau-verm.uni-karlsruhe.de's message of Fri, 20 Nov 1992 09:12:23 GMT

   Hello,

   I'm running X-Windows on my Linux PC  (0.98 pl4/5) with an ATI
   graphics vantage card and the new Xlinux.8514 driver. Everything
   works fine ...
   BUT: xdpyinfo reports that only 6 bits are significant in color 
	specification. That's sad, because I want to implement and test
	some image processing tools and 256 different colors are absolutely
	necessary for doing this job.

   QUESTION: Did I make some configuration mistakes ?? Is the 6 bit significance
	     a feature (what a pity) --> the hardware of the graphic card can
	     display 256 different colors !!!!
....

   Thanks in advance 
   Stefan
   ---

You can display 256 different colours with Xlinux.8514 and ATI Graphics Vantage.
The fact that only six bits are significant applies to each colour component
(red, green, blue) and this means that you can choose your 256 colours from
64 * 64 * 64 alternatives. The six bit limitation comes from the six bit D/A
converters.

I am using my Linux machine to develop image processing tools, too. They look
the same at home on my Linux screen as here at work on a DECstation.

	Kai

--
DISCLAIMER: The views expressed here are mine and may not always
coincide with the views of my employer.

*  Kai Makisara                *  email Kai.Makisara@vtt.fi    *
From: sad@deakin.OZ.AU (Scott Macdonald)
Newsgroups: comp.os.linux
Subject: NFS server for linux
Date: 17 Nov 1992 09:50:39 GMT
Organization: Deakin University, Victoria, Australia
Distribution: world
NNTP-Posting-Host: tethys.cc.deakin.oz.au

I would like to get in touch with anyone who has been able to get the
nfs server code available in ALPHA/NFS on tsx11 up and running under Linux.

Any assistance is much appreciated.

thanks

Scott Macdonald
Computing Facilities Administration
Deakin University Warrnambool

PS.  Thanks to all those that sent email regarding the problem I was having
with tcpip - it is all fixed now.
From: wirzeniu@klaava.Helsinki.FI (Lars Wirzenius)
Newsgroups: comp.os.linux
Subject: Re: function-->macro bugs.
Date: 21 Nov 92 00:02:41 GMT
Organization: University of Helsinki

jy10033@ehsn11.cen.uiuc.edu (Joshua M Yelon) writes:
>Our "stdlib.h" does something unusual: it defines malloc as a macro.
>According to the standard, though, malloc is a function.  

However, the standard also explicitly allows defining any function as
a macro as well, as long as the macro is well-behaving (evaluates its
arguments exactly once, and so on).  It also specifies that the
functions have to be implemented as a macro as well.  In order to make
certain that you get access to the function, do this:

	#include <stdlib.h>
	#undef malloc

>Indeed, there are many functions that have been converted to macros
>by our header files.

This is often done because of efficiency (e.g. the <ctype.h> macros
will often be significantly faster if they are macros instead of
functions).

>1. This is correct:
>
>extern void *malloc();

If you include the <stdlib.h> header, it is not correct, at least
under ANSI C.

>2. This is correct:
>
>void *(*allocator)() = malloc;

Yup.  The library should have a function called malloc even if it is
implemented as a macro as well.  I think it does (at least my libc.a
contains malloc, and a quick test doesn't complain).

>3. This is correct:
>
>/* My-super-efficient-malloc: */
>static void *malloc(n)
>int n;
>{...

Nope, not if you include <stdlib.h>.  You cannot have declarations /
definitions for malloc that specify both external and internal
linkage.

>In case you think these are far-fetched examples, and you don't think
>they are likely to bite us, I'd like to point out that both emacs 18.59
>and f2c _would_ compile out-of-the-box, but don't because of these errors.

I don't disagree with this at all.  However, at least in this respect,
I think that emacs and f2c are broken, not our malloc.  The best
solution, IMHO would be to fix them.  Not that I particularly oppose
of removing any malloc macros, either.

--
Lars.Wirzenius@helsinki.fi  (finger wirzeniu@klaava.helsinki.fi)
   MS-DOS, you can't live with it, you can live without it.
Newsgroups: comp.os.linux
From: lee@Hawaii.Edu (Greg Lee)
Subject: Re: xview and olwm
Organization: University of Hawaii
X-Newsreader: TIN [version 1.1 PL6]
Date: Fri, 20 Nov 1992 10:02:08 GMT

brad John pitzel (pitzel@ug.cs.dal.ca) wrote:
: I am interested if anyone has decent start-up files for olwm (.xinitrc,
: Xdefaults, root menus, etc). ...  I can't get Xterm windows to appear,etc etc..

The files in /usr/openwin/lib which define the root menu have long
names.  If you unpacked the distribution tar file into a minix
filesystem, the names will have been truncated and olwm can't find them.

If someone gets the DIRMENU and WINMENU functions working for olvwm
v. 3.2, I hope they let us know how.  I've tried, but so far no go.

Newsgroups: comp.os.linux
From: gml@parker.ositech.fi (Mikael Lonnroth)
Subject: Smail and TCP/IP (problems...)
Organization: Ositech Oy
Date: Mon, 16 Nov 1992 12:14:13 GMT

Hi,
    I'm installing the smail-(3.1.28)package and I'm experiencing some
troubles with the TCP/IP-code.

    In the conf/EDITME-file I have DRIVER_CONFIGURATION=arpa-network and 
HAVE=BIND. After some minor changes to the files gethost.c and bindlib.c
all the programs compiled but the linker complains about the following 
symbols:

drivertab.o: Undefined symbol _tpd_smtp referenced from data segment
                              _tpb_smtp
                              _tpd_tcpsmtp
                              _tpb_tcpsmtp

Is this something Linux should have or am I trying to compile it with
a bogus configuration?
--
gml@perko.ositech.fi
Mikael Lonnroth
Espoo, Finland
From: Jim.Corbett@f35.n152.z1.fidonet.org (Jim Corbett)
Newsgroups: comp.os.linux
Subject: Re: SLS "shell-init: Unknown Error"
Date: Wed, 18 Nov 1992 12:25:02 -0800

JG> Another SLS question...  I can't get "sysinstall" to read
JG> my floppy drives.
JG> The floppy 'light' doesn't even come on.  I tried
JG> "sysinstall -special i -drive b:"

I found that problem also, replace  -special with -series and it will
work! 
 
 * Origin: Intermittent Connection  Eugene, OR (1:152/35)

Newsgroups: comp.os.linux
From: "Hood Philip" <hood_philip@po.gis.prc.com>
Subject: SLS infanticide
Reply-To: hood_philip@po.gis.prc.com
Organization: The Internet
Date: Mon, 16 Nov 1992 14:58:42 GMT

I recently downloaded SLS and have experienced some problems installing. 
During the installation process I get a variety of error messages similar to
others recently posted.  Since we have been advised to ignore them I didn't
write them down.  What is harder to ignore is that several disks (including A3)
were barely even read by the install script.

When I finish the install script and attempt to reboot according to the
instructions it goes well for a while, but when child processes are spawned
they all die immediately with code ff00.  This leads to an infinite loop
spawning chilren that die...

Any insight????
From: eric@tantalus.nrl.navy.mil (Eric Youngdale)
Newsgroups: comp.os.linux
Subject: New scsi code.
Date: 18 Nov 92 16:35:32 GMT
Organization: Naval Research Laboratory


	The mail handler at niksula.hut.fi seems to be all foobar, so
it appears as if I cannot post things to the SCSI channel and expect them to
arrive.  Thus I am going to do this the old fashion way...

	I have uploaded a new alpha version of the scsi code to tsx-11.mit.edu.
The source code is on tsx-11.mit.edu in pub/linux/ALPHA/scsi in fscsi-06.tar.Z
I do not have context diffs from fscsi-a05, but if people want them, I can
generate them easily enough (the new future domain code would make the diffs
rather long).  There are a number of minor fixes here and there, which I
described at the end of this message.

	My firm intention is that the new code be in place in the 0.99 kernel,
and according to Linus, we have about 1-2 weeks (I want the code in 1.0, and it
would be foolish to drop in the new code at the last minute).  I STRONGLY
encourage people to try and use the code, even if the performance enhancements
are not in place for your specific scsi adapter.  I do not intend to rush
people working on the low-level code - if you do not have time to complete the
job prior to 0.99, then we will just go with the slower code for the time
being, and drop in the replacements once they are ready - after 1.0 if need be.

-Eric

Here is a short list of some of the changes that have been made since
fscsi-a05:

	* The Makefile/Makefile.in has been cleaned up a little more - it
should automatically regenerate the Makefile when you first drop the code into
place.  A "make clean" resets things so the next make forces a regeneration
of the Makefile the next time around.

	* The future domain code has some scatter-gather enabled, and the
performance has reportedly been improved quite significantly.

	* I added the framework for blacklisting certain devices, and skipping
a lun scan for those devices.

	* Fixed the cdrom code so that it will in principle accept buffer sizes
in any multiple of 512 bytes (in preparation for different size buffers in the
buffer cache).  The scsi disk code should already handle this correctly.

	* Commented out a couple of printks that had been there for debugging.

	* Added a few minor Ultrastor patches from Dave Gentzel (use
request_dma to allocate dma channel).

	* Use the new linux/ioctl.h linux/mtio.h include files.

	* A bunch of other minor corrections here and there.

-- 
Eric Youngdale
From: hlu@yoda.eecs.wsu.edu (H.J. Lu)
Newsgroups: comp.os.linux
Subject: Re: Severe problems with "realloc" (FIX_MALLOC)!
Keywords: linux realloc bug malloc
Date: 19 Nov 92 08:28:21 GMT
Article-I.D.: serval.1992Nov19.082821.13419
Organization: Washington State University

In article <1992Nov19.004235.9239@arbi.Informatik.Uni-Oldenburg.DE> Adrian.Wallaschek@arbi.informatik.uni-oldenburg.de (Adrian Wallaschek) writes:
>
>Hi fellows!
>
>I don't know wether I'm going to warm up forgotten discussions, but hasn't yet
>anybody worked on a program that makes heavy use of realloc ?
>
>I had severe problems getting a regex-package (0.11) to work. I got several
>IOT-Trap-cores till I remebered about the malloc(0) problem with linux.
>There is a work-around for malloc and calloc in stdlib.h BUT none for realloc!
>Somebody forgot something, I suppose! ;-) So to avoid unnecessary cores you
>might want to include few lines to your stdlib.h (to make it easy, lets 
>patch it!). Its nothing serious (just copied 5 lines) but it makes regex work!
>
>I have found that even some library-functions make use of realloc, I think
>this might be the cause of some porting-problems.
>
>If this is a well known problem, please don't flame, I just wanted to help!
>

[....]

As far as I understand, 

realloc (foo, 0);

should free `foo', at least under POSIX. I have put regex 0.11 in the
testing release of libc 4.2. I haven't heard any bug report about
that. If it is true, it is a bug in regex 0.11. You should file
a bug report to the regex maintainer.


H.J.
Newsgroups: comp.os.linux
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.os.linux
Subject: Re: Inode/Zone count errors with ext fs
Keywords: extfs
Date: 17 Nov 92 22:16:00 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

In article <1992Nov14.151002.23536@mintaka.lcs.mit.edu>, wyvern@hal.gnu.ai.mit.edu (The Wyvern) writes:
| 
| 	I recently upgraded to Linux v0.98pl4. Everything seems to work great,
| except for some strange errors I'm receiving from efsck for my ext fs
| partition. After reboot I did an efsck /dev/hda4 and got these errors:
| 	Free inodes count wrong (13193, counted=13194). 
| 	Free zones count wrong (36297, counted=36317). 
| efsck -r doesn't seem to fix the problem - I've tried it several times.
| Is there any way to get rid of these errors short of remaking the whole
| filesystem?

On most version of UNIX and its clones, an fsck on an active f/s is
likely to produce some warnings. The suggested way to do it is to
unmount the f/s before checking. On Linux this means boot from floppy
for the root partition.

I do this for backup of some systems, too. All partitions other than
root are backed up unmounted in single user mode, root is backed up
booted from another partition (need not be floppy). Of course I do
running dumps of stuff, too, but the dumps I really trust are done on an
unmounted f/s.

-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
    Keyboard controller has been disabled, press F1 to continue.
From: pdc@dcs.ed.ac.uk (Paul Crowley)
Newsgroups: comp.os.linux
Subject: Re: Packaging Linux
Date: 21 Nov 92 15:47:26 GMT
Reply-To: pdc@dcs.ed.ac.uk (Paul Crowley)
Organization: Do they make a washing powder called Caliban Automatic?

Quoting drew@kinglear.cs.colorado.edu (Drew Eckhardt) in article <1992Nov20.233536.28788@colorado.edu>:
>
>Joe User won't port code, contribute fixes or source, and will annoy 
>real Linux users with his whining about there not being a "real" editor, 
>about Linux being difficult because it isn't dos, etc.  
>
>So do we care if Joe User uses Linux?

Yes!  Yes, we certainly do care.  The fact is that many people have to
use commercial software for some of the stuff they do.  If Joe User
starts using Linux, software houses might start porting their software
to Linux so Joe buys it.  At about this point, people might start to
think ``Why spend money enslaving myself to Microsoft when I can have
freedom to move platforms and a real operating system for nothing?''

As I see it, we want people to write for X and port to Windows and not
the other way around.  I think free software is very nice, but not
*important*; what's important is free *standards*.  Any commercial
standard that only one vendor implements is very bad news; such a
standard must be fought.

That's why Linux is so important; it gives us leverage in establishing a
competing free standard.
_____                                __  
\\ // Paul Crowley pdc@dcs.ed.ac.uk /o \/
 \X/  "I'm the boy without a sole"  \__/\
Newsgroups: comp.os.linux
From: jnewbern@athena.mit.edu (Jeffrey L Newbern)
Subject: Anyone using an Ultrastor 12F ESDI controller?
Organization: Massachusetts Institute of Technology
Date: Tue, 17 Nov 1992 00:23:14 GMT

Is anyone using an Ultrastor 12F ESDI controller with Linux?
Does it work well?  Is there anything I should know before I purchase one
of these controllers for the 400 MB ESDI drive I fell into?

Any answers will be appreciated,
jeff
jnewbern@athena.mit.edu
From: ae007@yfn.ysu.edu (Daniel Newcombe)
Newsgroups: comp.os.linux
Subject: Xview for linux?
Date: 19 Nov 92 14:02:02 GMT
Organization: Youngstown State University/Youngstown Free-Net


Is Xview out there for Linux?  Simple enuff :)
   -Dan
-- 
    -Dan Newcombe
Internet Address:  STDN@VM.MARIST.EDU
Youngstown Freenet: ae007@yfn.ysu.edu
GOAL: To put the world on 3.5" diskettes...  :)
From: root@umibox.hanse.de
Newsgroups: comp.os.linux
Subject: Re: Q about Seagate SCSI controller ST02
Date: Sat, 21 Nov 1992 18:30:20 GMT
Organization: Linux Box standing around in Hamburg, Germany

drew@juliet.cs.colorado.edu (Drew Eckhardt) writes:

>In article <1992Nov19.161336.15475@eua.ericsson.se> tmpcms@eua.ericsson.se (Carl Michael Skoog) writes:
>>
>>I recently bought a used Seagate ST02 SCSI Host (Bios Revision 3.2).
>>During POST it first prints out something like "Seagate ST02 bios 3.2"
>>, and then the cryptic message "SCSI Adaptor Failure" comes up.
>>
>>Does this indicate a hardware failure, or does it simply indicate that i have

>Yes.    

No!!!!!!!

It really just indicates you should attach disks to a host, otherwise the
host's lines won't be terminated and the initialization (sp) sequence fails
miserably. No need to worry!

I've experienced this myself with my st-02 even before I put in the Prom
turned 180 degrees :-( (still works!)

Ciao,
    Bernd

P.S.: Newspak is wonderful!