HDTenEightyP/NetNews huggingface dataset:
From: drew@juliet.cs.colorado.edu (Drew Eckhardt)
Subject: Re: Slow SCSI performance
Organization: University of Colorado at Boulder
Date: Mon, 31 Aug 1992 19:47:13 GMT

In article <1992Aug31.162211.8065@zip.eecs.umich.edu> yhe@quip.eecs.umich.edu (Youda He) writes:
>I had this problem from 0.97pl1, and now pl2, when SCSI is accessed, the
>system seems stop to respond to other vc, and SCSI itself is SLOW. sometimes
>the hard drive LED light but nothing happened, when this happened, I usually
>can issue some command on other vc and the "deadlock" on SCSI seemed resolved.
>the system is:

1.  SCSI transfer rates should be slow, 50-100k/sec on systems with unbuffered
	disks, (~300k/sec on buffered drives) or disks that require mode page 
	twiddling to enable the buffers.   

	This will be fixed in R2 of the SCSI drivers - basically, a design
	flaw results in the routines reading 1 block per revolution - 
	on a 3600 RPM drive, this comes to ~60k/sec.  

2.  Accessing SCSI disks on one tty / pty /ttys / etc should not 
	affect performance of a non-I/O bound process on another 
	tty.  It doesn't on my system.  

	A lot depends on the specific low level driver.


>33 MHZ 486 with AHA1542B Maxter 8760S, the files systems are sda3 32MB swap 
>(I don't know I need it since I have 16MB memary), sda4 64MB minix, sda5 100MB
>on logical device, sda5 200MB also a logical device. sda[56] are extended files
>systems. I guess the problems may be that I use extended file systems on 
>extended partition on a SCSI drive? can I repartition the system that not use
>the extended partition solve the problem? The other partitions are used for
>OS/2, so the system must coexist with OS/2.
>

Extended / "Normal" partitions don't make a difference as far as the driver
is concerned.  As far as the driver is concerned, the only difference 
between extended and normal partitions is during initialization - 
when you actually access them, they're just a starting sector
and a limit to the device driver.

The only problem you might see comes from the Linux block device code - 
requests are sorted by major, minor, and block number.  With different
partitions, requests may be "out of order" with respect to the disk 
blocks - which will degrade performance as the thing has to seek.



-- 
Microsoft is responsible for propogating the evils it calls DOS and Windows, 
IBM for AIX (appropriately called Aches by those having to administer it), but 
marketing's sins don't come close to those of legal departments.
Boycott AT&T for their absurd anti-BSDI lawsuit.
From: zlsiial@uts.mcc.ac.uk (A. V. Le Blanc)
Newsgroups: comp.os.linux
Subject: Problems with 0.97p2
Date: 25 Aug 92 06:33:40 GMT
Reply-To: LeBlanc@mcc.ac.uk (A. V. Le Blanc)
Organization: Computing Centre, University of Manchester

In addition to the problem described in an earlier post about
LILO, I've found a number of odd bugs when running under 0.97p2.
I've not run across the problems with mount/umount, but I'm
using my own version of those.  I have had difficulty with make.

The following simple Makefile can be used as an example:

     CC=cc

Under 0.97p1 it produces an error message 'No targets specified...',
but under 0.97p2 it dumps core.

A few other oddities have surfaced.  I expect this is due to the
rewrite of low-level functions in the kernel.  Nie od razu Krakow
zbudowali, since it seems to be the fashion to include a propos
snippets in odd tongues.

     -- Owen
     LeBlanc@mcc.ac.uk
From: sp@questor.wimsey.bc.ca (Steve Pershing)
Newsgroups: comp.os.linux
Subject: Termcap Entry for WYSE 30
Date: Wed, 26 Aug 92 20:31:20 PDT
Organization: Questor|Free Usenet News|Vancouver, BC: +1 604 681 0670

I'm looking for a TermCap entry for a Wyse 30 terminal which I might
use with linux.

If anyone has one, please let me know, or send a copy.  Thanks!

---
        Steve Pershing, System Administrator, The QUESTOR Project
  FREE access to Environ, Sci, Med, & AIDS news, and more.  [also UUCP]
        on a ZyXEL-1496S v.42bis, v.32bis, v.33, up to 16,800bps.
  .-------------------------------------------------------------------.
  |  POST: 1027 Davie St., Box 486, Vancouver, B.C., Canada  V6E 4L2  |
  |  Fones: (+1 604)  Data: 681-0670  FAX: 682-6160  Voice: 682-6659  |
From: c-amb@math.utah.edu (Mark B. Alston)
Newsgroups: comp.os.linux
Subject: Re: lilo problems
Date: 4 Sep 92 17:14:34 GMT
Article-I.D.: solitude.C-AMB.92Sep4101434
Organization: Department of Mathematics, University of Utah

In article <1992Sep4.094349.17604@inmos.co.uk> bob@cheetah.inmos.co.uk (Bob Green) writes:
   Hope this hasn't been asked before. I've looked in the README supplied
   with lilo.4 and also in the extra README supplied by mcc. I'm trying
   to make a bootable floppy before I wreck my hard disk ;-) However I
   invoke lilo I get the following message:

   Hole found in map file (zero sector)

   What does this mean ? Am I doing something stupid ?

No, you are doing everything as expected.   It's just that you need this patch for lilo to work correctly with 0.97p2.

------------------        cut here   ---------------------------------------

*** geometry.orig       Mon Aug 24 21:53:28 1992
--- geometry.c  Mon Aug 24 21:53:31 1992
***************
*** 165,170 ****
--- 165,171 ----
            die("Incompatible block size: %d\n",st.st_blksize);
        geo->spb = st.st_blksize/SECTOR_SIZE;
      }
+     geo->spb = 2;
      return geo->fd;
  }
  

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

After applying this patch, to the lilo source, everything will work
fine.  One thing to remember.  You are supposed to reinstall lilo
everytime you compile a new image.  The install shell script works
great for this,


Have fun!
--
--------------------------------------------------------
  Mark Alston        
  c-amb@math.utah.edu
       
"Never knew a decent man who liked mathematics."
			- Bonnie Abbzug-Sarvis
			  Hayduke Lives!
---------------------------------------------------------
From: Emmett.Sauer@f215.n3802.z1.fidonet.org (Emmett Sauer)
Newsgroups: comp.os.linux
Subject: HELP: SLS distribution install fails with bad magic number.
Date: Sun, 30 Aug 1992 15:02:01 -0800

DS> I am installing linux on my machine for the first time and am
DS> Using the SLS
DS> distribution. I am getting a bad magic number problem on the
DS> 1st install
DS> disk.
First of all... the first two disks are Rawritten to Dos formatted
disks.

The first disk will call and mount the second disk....

The remaining disks are all dos disks with the files dos copied to them,
be sure and include the DISK# file on each diskette.
DS> Where can I get more info on the SLS distribution? I know next
DS> to nothing about
DS> linux and its installation and am not sure how to go about
You should gotten a README file with the SLS diskettes or files if
downloaded.

This README will guide through the installation.

DS> my Boot manager and DOS partition. Doinstall tells me to do a
DS> mkfs first. Which
DS> wants me to do a fdisk first.
DS>
Well the mkfs and fdisk it refers you to are on the Linux disks 1 or
2...
they should be self explanitory.
DS>

If you need more help you can contact my BBS (512)578-2720 and I will be
glad to help you.... I went through this myself.. I know how you
feel...

FREQ 'LINUX' to get a current Linux files list.

Emmett Sauer                        |  ADVANCED BBS   |
emmett@tenet.edu                    | (512) 578-2720  |
                                    | FIDO 1:3802/215 |
                                    |  Linux Files    |
                                    |  FTPing Daily   |


 * Origin: Advanced BBS - Line 1 (512)578-2720 (1:3802/215)
From: ace3@quads.uchicago.edu (Tony 'LLama' Acero)
Subject: X386 for 8514A - Misc Notes and Problems
Followup-To: comp.os.linux
Reply-To: ace3@midway.uchicago.edu
Organization: University of Chicago Computing Organizations
Date: Fri, 4 Sep 1992 04:17:37 GMT

First, many thanks to Kevin Martin for all his work on the 8514 port of
X386 to Linux!!  Things seem to be working almost flawlessly!  Implicit, of
course, are thanks to Linus and the legions of hackers that have made every
thing possible.

Ok.  Through a bit of good fortune, an ATI 8514 Ultra has come into my
possession.  The Ultra is a subset of the more recoginized (to me at least)
ATI Graphics Ultra.  It lacks standard VGA (it must be piggy-backed off an
existing VGA adapter using the (ahem) 'feature connector'), bus mouse and
port.

While I was trying to setup the card, I ran into an UNDOCUMENTED FEATURE: 
the card's ports are at addresses in the neighborhood of 0x2e0.  This is
where COM4 tends to live.  If you have COM4 you may need to disable it to
get the card to work.  This potential conflict is not documented in the
manual, although tech support seems to be well acquainted with it :-).  So
for a good while last night it seemed my bit of good fortune was actually
the reverse, but fortunately this was not the case.

So I grabbed the X386 1.1 distribution from
tsx-11.mit.edu:pub/linux/packages/X11/ and overlayed Kevin's 8514 driver,
and followed the relatively straight-forward installation instructions.

Foolishly thinking that was all there was to it I  typed 'startx'.  Of
course it locked up...

After looking more carefully at the installation instructions, I
'chown root.root /dev/ptyp*';  I had grabbed the MCC-interim release in
which a lot of binaries and devices tend to by owned by 'bin'.

At this point 'startx' brings up X with clock and shell.  If I try to exit
from the window manager (after closing all the windows) the machine locks
up tight (ie the NumLock light doesn't even toggle). If I capture std error
from startx (ie 'startx 2> xerror') xerror contains "xinit: connection to X
server lost"

Could anyone

1) Tell me how to avoid the lock-ups when exiting

2) Tell me if selection is compatible with X386 (I'll be able to answer
that one myself pretty soon)

3) Point me to a slightly more detailed guide to setting up X386


Many, many thanks,

tony acero
Newsgroups: comp.os.linux
From: jbrogers@phoenix.Princeton.EDU (John B.  Jr. Rogerson)
Subject: keymapping under vi
Originator: news@nimaster
Organization: Princeton University
Date: Wed, 2 Sep 1992 14:25:32 GMT

Using mks vi under DOS I can map the umlaut equivalents of a,A,o,O,u,U
to F1 through F6.  Does anyone know whether or not this is possible for
any of the vi variants (vile,elvis) under Linux?  This is not of
universal importance, but I do some corresponding in German and it would
a help to me if I did not need to exit Linux and boot DOS just for this
facility.   Thanks for any help.
                   jbrogers@phoenix.princeton.edu
Newsgroups: comp.os.linux
Subject: Re: Clue?
From: system@kryton.UUCP (Scott Beckstead)
Date: Thu, 03 Sep 92 15:51:50 PDT
Organization: Paradox Alley F&SF BBS 805-492-8789

David Reeve Sward <dsa3+@andrew.cmu.edu> writes:

> Psst!  Buddy, can you spare a clue?
> 
> A couple Linux-newbie(tm) questions:
> 
> 1) Is there any Token Ring support?  I've got a 16Mb card here and it
> would sweet to ftp right to Linux instead of to DOS -> rawrite -> Linux
> -> tar.
> 
> 2) Just how do you move stuff from DOS to Linux via rawrite -> tar?  I
> grabbed tcsh.tar.Z from tsx, uncompressed it in DOS, rawrote it to a
> floppy, fired up Linux (thanks BootLinux & Boot.Sys!) and ran
> 
> tar -tvf /dev/fd0H1440
>      ^^^
Never used tar before either I see, Try tar vxf /dev/fd0h1440
 
> It spat out the verbose file listing as (I assumed) it put the files on
> the HD. But!  There were no additional files on the HD.  df reported no
> used/free changes.  What am I doing wrong here?
It did exactly what you told it to. 

> 3) Is there a Common Lisp implementation for Linux?
   Don't know sorry.

> 4) mtools.  Where can I find docs for mtools?  (DOS is on C, Linux is on
> D with 3 partitions - 18M /, 63M /usr & 10M swap).
> 
> 5) Anything else a Linux-newbie(tm) should know that's not in the FAQ/whatnot
> 
> Thanks!
> 


System Administrator Paradox Alley  F&SF BBS and Usenet News/Mail 
805-492-8789  Thousand Oaks, Ca. The Place For Science Fiction and Fantasy
"Spin My Nipple Nuts and Send Me to Alaska!" Kryten, Red Dwarf

Newsgroups: comp.os.linux
From: djr48312@uxa.cso.uiuc.edu (X X)
Subject: SCSI controller choices, help.
Organization: University of Illinois at Urbana
Date: Thu, 3 Sep 1992 06:28:43 GMT

Ok.  Ive asked before about what SCSI controllers linux supports.  Im down
to the final decision.  It can be any of the following controllers:

	Adaptec AHA-1542B SCSI
	ADAPTEC AHA-1542BK SCSI BUS MASTER HOST ADAPTER KIT
	FUTURE DOMAIN 1670 16 BIT SCSI ADAPTER
	FUTURE DOMAIN 1680 DNK SCSI KIT
	FUTURE DOMAIN 1680 SCSI HD/FD HOST ADAPTER

Does anyone use any of these controllers?  How is performance?  Which one
for the BEST linux (and OS/2) compatibility?
From: hammond@kwhpc.caseng.com (Kevin W. Hammond)
Newsgroups: comp.os.linux
Subject: Re: your mail
Date: 31 Aug 92 01:40:12 GMT
Reply-To: hammond@kwhpc.caseng.com
Organization: The Internet

| 
| There is a problem with symbolic links in 0.97 patch level 2.  i.e
| they're not followed if you are not the owner ( of the link ) or a
| member of the owner's group. I'm using the minix file system.
| 
| I discovered this because I have shell scripts that look like this ..
|  
| #!/bin/sh
| shell commands...
| 
| /bin/sh is a symbolic link to /bin/bash. ( owner bin:bin ). If I try to
| execute the shell script as a normal user, it fails with "operation not
| permitted". The permissions on bash are rwxr-xr-x
| 

I am running 0.97pl2 and do not see the same problem.  I have /bin/bash
owned by bin:bin with perms of 755.  I then have /bin/sh as a symbolic
link to /bin/bash (however I cannot get the link to be owned by bin:bin.
It always seems to be owned by root:root  Anyone know why?)  Who own's
the /bin/sh link on your system?

I tested it with a shell script as you indicated above and it works fine.
I know this doesn't really help your problem, but it might go a little to
indicate that it may not be 0.97pl2 that is the cause of the problem.

I also have all sorts of other symbolic links to files throughout my system
(such as awk to gawk, etc.) and all works well!


-kwh-
-- 
Kevin W. Hammond
hammond@kwhpc.caseng.com

  CASE Engineering * 575 W. Madison #1601 * Chicago, IL 60661 * (312)902-2161
From: jhelberg@nl.oracle.com (Joost Helberg)
Newsgroups: comp.os.linux
Subject: Re: problems with 0.97pl2 and tcpip
Date: 26 Aug 92 16:13:32 GMT
Organization: Oracle Europe
X-Newsreader: Tin 1.1 PL3

X-Disclaimer: This message was written by an unauthenticated user
              at Oracle Corporation.  The opinions expressed are those
              of the user and not necessarily those of Oracle.

hlu@fili.eecs.wsu.edu (H.J. Lu) writes:
: In article <2746@nlsun1.oracle.nl>, jhelberg@nl.oracle.com (Joost Helberg) writes:
: |> 
: |> I have 0.97pl2 up and running and tried to add tcpip0.8 into it.
: |> 
: |> the patch worked allright, compiled good too but:
: |>   when loading the image i get unresolveds:
: |>   	_outb_p
: |> 	_inb_p
: |> 	_outb
: |> severals hundreds! from net/net.o. 
: |> 
: |> As the only code from net using outb/inb etc. is we.c It must come from there.
: |> 
: |> we.c includes asm/io.h, so I don't know why this goes wrong?
: |> 
: |> 
: |> 
: 
: Just my wild guess. Did you use -O?
: 
: H.J.

Right you are!
I changed the first 5 lines of the Makefile for tcpip into comment.
After that it worked.

the lines as they are in tcpip 0.8: 
  AS    =as
  AR    =ar
  LD    =ld
  CC    = gcc -I../../include

Yakee! See why it works now?

--  
   Joost Helberg                                Rijnzathe 6
   jhelberg@oracle.nl                           NL-3454 PV De Meern
   jhelberg@nl.oracle.com                       The Netherlands

   Oracle Europe BV                             Product Line Development	
   Phone: +31 3406 94211                        Fax:   +31 3406 65609
Newsgroups: comp.os.linux
From: klode@syslab.csd.uwo.ca (Claude Morin)
Subject: Re: Shoelace won't boot linux partition
Organization: Department of Computer Science, University of Western Ontario, London
Date: Wed, 26 Aug 1992 18:51:35 GMT
Summary: possible cause & fix

Sounds like your root linux partition does not start on a cylinder boundary.
You should try other things before assuming this is the problem, since fixing
it requires messing with the partition table.  If you try to fix your
partitions, don't forget to do a backup first :-)

Note that DOS does not care where its partition starts.
---
Claude Morin
(that's "klode", NOT "clod"...French :-)
London, Ontario, Canada
Newsgroups: comp.os.linux
From: jwinstea@fenris.claremont.edu (Jim Winstead Jr.)
Subject: Re: new X11 editor: aXe
Organization: Harvey Mudd College, WIBSTR
Date: Tue, 25 Aug 1992 17:37:36 GMT

In article <1992Aug25.144151.2046@athena.mit.edu> chchen@stat.fsu.edu writes:
>In my department our SA installed a new X11 editor called aXe which
>looks quite nice. I got the tar.Z file here but unfortunately I am
>just a newbie in GCC or compiler to port it (I will try anyway :) )
>Anyone already ported it to Linux?

I compiled this a while ago, and it goes pretty easily once you supply
a scandir() function, which you can snarf from the BSD sources.

The problem is that it coredumps in a rather unfortunate location
(when trying to shutdown all the buffers), so unless you like
sprinkling core files around your filesystem, it's a pain to use
(although it does still work - it saves the file then coredumps :).

I tracked the problem to a point (with the help of Jim Wight, the
author), but we weren't able to come up with anything, and suspect it
might be a problem with the X libraries for Linux.  I've been waiting
for the next release of the X stuff before trying again.

-- 
                                    +      Jim Winstead Jr. (CSci '95)
                                    |      Harvey Mudd College, WIBSTR
                                    |   jwinstea@jarthur.Claremont.EDU
                                    + or jwinstea@fenris.Claremont.EDU
From: gt6698a@prism.gatech.EDU (Andrew Hobson)
Newsgroups: comp.os.linux
Subject: More info and corrections Re: Microsoft Bus mice
Date: 27 Aug 92 22:52:39 GMT
Organization: Georgia Institute of Technology

Hello!

Hopefully you have seen my first post about my problems using X with
a microsoft mouse.  In my first article, I said that if I ran a program
that did an ioperm on the four ports used by the mouse, then after that
I could get my mouse to work in X.  Well that is half true.  If I run
a program that does an ioperm on all the ports and I interrupt it 
(with a ctrl-C) then I get the described behavior.  If I allow the program
to exit normally, then the mouse does not work at all.

In my first article I also said that the mouse would work until the xterm
came up.  That is not so.  I can move the mouse around until ??? 
Until something happens.  If I remove the xterm and xclock from my
xinitrc, the mouse still stops working at some unspecified time.

If I just run xinit with no window manager the behavior is exactly
the same.

Thanks for any help you can give me.

Andrew Hobson

-- 
Andrew Hobson                         Internet: gt6698a@prism.gatech.edu
"He who joyfully marches to music in rank and file has already
earned my contempt.  He has been given a large brain by mistake,
since for him the spinal cord would fully suffice."   -- Albert Einstein
Newsgroups: comp.os.linux
From: upsyf108@unibi.uni-bielefeld.de (Wolfgang Thiel)
Subject: Re: Microsoft bus mouse support
Date: Thu, 27 Aug 92 07:06:42 GMT
Organization: Universitaet Bielefeld


The bus mouse driver and the ethernet use the same device number (I think
it's Major 10, Minor 0). So one of them has to be changed. 
                     Wolfgang Thiel
Newsgroups: comp.os.linux
From: hammond@kwhpc.caseng.com (Kevin W. Hammond)
Subject: Using tools/build
Reply-To: hammond@kwhpc.caseng.com (Kevin W. Hammond)
Organization: The Internet
Date: Fri, 28 Aug 1992 23:53:04 GMT

I finally (!!!!!!!!!!!) got 0.97pl1 to build!!!  (Those of you who mailed
me that you have had similar problems, the answer is on the way....)

However, when tools/build is run to build Image, the following message
is always displayed:

	"/dev/hda2: Function not implemented"

If I leave off the root device, I will get a proper Image file that mounts
the floppy as root, but I need to have the hard drive used as root.

I'm building the kernel under 0.96a.  What am I missing here??

-kwh-
-- 
Kevin W. Hammond
hammond@kwhpc.caseng.com

                 Looking for a real operating system?  Try Linux.

  CASE Engineering * 575 W. Madison #1601 * Chicago, IL 60661 * (312)902-2161
From: sander@kozmix.hacktic.nl (Sander van Malssen)
Newsgroups: comp.os.linux
Subject: uemacs
Date: Thu, 27 Aug 92 14:12:13 MET
Organization: Kozmic Egg Productions

Hi!

Has anyone ported MicroEMACS 3.11 to Linux yet?




Bye!
Sander

		       = Linux or bust! =
Sander van Malssen | sander@kozmix.hacktic.nl | Fido 2:285/101.6
From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
Newsgroups: comp.os.linux
Subject: Re: VM86
Date: 29 Aug 92 09:12:00 GMT
Organization: University of Helsinki

In article <1992Aug29.065940.1256@athena.mit.edu> hammond@kwhpc.caseng.com (Kevin W. Hammond) writes:
>I see with patch 2 there is a vm86.h file and I recall seeing some mention
>of Linux supporting a virtual 8086 mode.  Is this true and, if so, how does
>one use the virtual 8086 driver?

Yes, 0.97.pl2 has support for a vm86 mode: note that this is /not/ the
same as a DOS emulator, but it can be used for that.  The interface
looks like this:

	void vm86(struct vm86_struct * info);

where vm86_struct is defined in linux/vm86.h, and currently looks like
this:

	struct vm86_struct {
		struct vm86_regs regs;
		unsigned long flag;
	}

The flag value is not currently used, and I assume some additional
fields will be added eventually (a page dirty map for efficient screen
updating etc), but the above is enough for a simple DOS emulator.

The vm86() system call is pretty simple: it loads the registers with the
values in the 'regs' structure, and starts executing in vm86 mode.  It
will return to protected mode when a signal happens: when this happens
the vm86 state is saved in the info structure and the signal handler is
executed in normal 32-bit mode.  The signal handlers can then use the
vm86_struct information to see what is going on, and correcting any
errors etc. 

A simple DOS emulator would look like this (pseudo-code):

global struct vm86_struct info;

main()
{
	set up the DOS memory image at 0 - 1MB
	set up SIGSEGV and SIGILL etc signal handlers
	set up the initial regs etc in 'info'
	while (1)
		vm86(&info);
}

SIGILL_handler()
{
	read 'info' to see why we got a SIGILL - if we can
	emulate it, update 'info' and return, else exit
}

SIGSEGV_handler()
{
	see SIGILL
}

SIGALRM_handler()
{
	check the screen memory in the vm86 box, and update the real
	screen every now and then. Do any other regular house-keeping
	fn's.
}

Note that all this happens in user mode - the kernel doesn't really do
anything special about vm86 mode. And as the emulator and vm86 code is
in the same process, is should be possible to make it all relatively
efficient.

		Linus
Newsgroups: comp.os.linux
From: paula@Informatik.TU-Muenchen.DE (Andreas Paul)
Subject: Swap-Partiton-Size ?
Originator: paula@hpzenger1.informatik.tu-muenchen.de
Organization: Technische Universitaet Muenchen, Germany
Date: Wed, 2 Sep 1992 12:45:28 GMT


Hi all ...

I have Linux installed on a approx 30 MB partiton ... with X installed
and some applications (gnuplot,minicom ... ).

This leaves me with about 10 MB free ... 
(not too much when trying to compile some more interesting X-stuff ... :)

I also do have a 10 MB swap partiton ... but running out of HD space I think
about repartitoning ... 

Any suggestions on a sensible root-partiton / swap-partiton ratio ?

Andreas Paul