HDTenEightyP/NetNews huggingface dataset:
From: minyard@crchh7b9 (Corey Minyard)
Subject: Re: PC port I/O for Linux MS-DOS emulator (long)
Organization: Bell-Northern Research, Richardson, Tx
X-Newsreader: TIN [version 1.1 PL8]
Date: Fri, 11 Dec 1992 20:50:58 GMT

Howlin' Bob (gt8134b@prism.gatech.EDU) wrote:
: dear Those in the Know,

: A plea for help:

:    I am currently modifying Linux's (pre-alpha) MS-DOS emulator to 
: support simulated port I/O; that is, if a program does an in
: from I/O address 0x2f8, I'll hand it the next available character
: on com2.  The author of the dos emulator provided much of the
: framework I need for this, which isn't that much anyway.  Because it
: runs in the 386's vm86 mode with no I/O permissions, all port I/O is
: trapped and passed to emulator functions inb() and outb().  

:    I have implemented a 3-minute subset of com port 2 (i.e. the UART
: at 0x2f8) that at least fools Telix into thinking that there
: is a UART there.  Telix hangs after out'ing something to
: port 0x21, which I believe is the interrupt controller.  This, along
: with the fact that Telix accesses the UART's interrupt enable and
: interrupt id registers, has led me to believe that Telix is waiting
: for a serial interrupt.

You are running into a problem I have been thinking about and will
have to solve soon.  I need to modify the DOS emulator so I can use an
"in circuit emulator (ICE)" under DOS.  This will require port access
(not too difficult with inb and outb) and the ability to receive
interrupts (much more difficult). This means that when the board sends
an interrupt, it somehow filters up through the OS and gets to the
task, probably as a signal.  I don't know if SIGIO will do this for
serial ports, but I will have to do custom work to implement a signal
to handle this.

Any kernel gurus that want to comment on this problem?

Also, I have writing my own MS-DOS emulator for the DOS emulator.  No
need to have a real version of MS-DOS, and you can directly run DOS
programs without having to start up DOS first. It seems to run most
programs ok (My C compiler works great) but programs that come with
DOS 5 behave very badly; some of them call functions that are not even
documented in the DOS 5 Undocumented DOS!  MS-DOS is a wierd beast, a
whole collection of kludges that somehow work.

Corey
minyard@bnr.ca
Newsgroups: comp.os.linux
From: becker@super.org (Donald J. Becker)
Subject: Re: Optimal Partition Sizes
Organization: IDA Supercomputing Research Center
Date: Mon, 14 Dec 1992 19:54:40 GMT


I first installed a Unix system about a decade ago (BSD on a VAX 750)
and little has changed since then -- you always choose badly the first
time you partition your disk.  Luckily back then we had RA81 disk
drives and could revisit our decision at the biweekly disk crash:^|

While installing SunOS recently I saw a disk partitioning aid that I
really found useful.  There was a table of disk drive sizes and suggested
partitioning that was understood by the disk partitioning program: you
could select one of the pre-defined partitionings for the partiticular
disk size you had.

Sun's implementation had some flaws (like, their install only works
with a layout very close to the "suggested" layout) and history has
forced them to support some arcane cruft (like, the 'c' disk partition
is really the whole disk -- which often lead to "gee we're not using
the biggest partition, I'll make it swap") but with the added tables
it's better than the way linux currently does 'fdisk'-related
configuration.

I've been rambling a little bit so I'll conclude: the linux community
should be able to come up with something better than printing out the
FAQ and typing in values verbatim.


-- 
Donald Becker				       becker@super.org
Supercomputing Research Center
17100 Science Drive, Bowie MD 21114		   301-805-7482
Newsgroups: comp.os.linux
From: fjh@munta.cs.mu.OZ.AU (Fergus James HENDERSON)
Subject: Re: ANNOUNCE: Sound for Linux 0.99 (Sound driver v 0.4)
Keywords: SOUND
Organization: Computer Science, University of Melbourne, Australia
Date: Tue, 15 Dec 1992 09:27:57 GMT

arumble@extro.ucc.su.OZ.AU (Anthony Rumble) writes:

>kenc@sol.acs.unt.edu (Ken Corey - Operator) writes:
>
>>(Also, there's a sneaky little voice in the back of my head 
>>thinking..."Wow..rogue would be *cool* with a few sound effects...")
>
>Very easy to do.. Just make the source code fork() and 
>cat the sample to /dev/dsp..

What about just
	system("cat sample > /dev/dsp &");

-- 
Fergus Henderson             fjh@munta.cs.mu.OZ.AU      
This .signature virus is a self-referential statement that is true - but 
you will only be able to consistently believe it if you copy it to your own
.signature file!
From: wjin@cs.uh.edu (W. Woody Jin)
Newsgroups: comp.os.linux
Subject: Re: Can X run with only 4 megs RAM?
Date: 14 Dec 1992 05:03:16 GMT
Organization: University of Houston
NNTP-Posting-Host: rodin.cs.uh.edu

In article <9dj2#wl@rpi.edu> jfritz@ptolemy2.rdrc.rpi.edu (Joe Fritz) writes:
>In article <andrewc.724292380@aurora.cc.monash.edu.au> andrewc@aurora.cc.monash.edu.au (Andrew J. Cosgriff !) writes:
>>jblaine@garnet.acns.fsu.edu (Jeff Blaine) writes:
>>
>>>I have a 386-25 with 4 megs and a 9 meg swap partition.  It seems very
>>>odd the responses that this question has been getting.  People with nearly
>>>the same configuration are having totally different circumstances come about
>>>from running X.  
>>
>>>One person said they could run 2 xterms, xconq, xman etc and the initial 
>>>person said they had 2 to 3 minutes lags between mouse movements.
>>>I can open one xterm.  If I open anything else at all, X starts swapping
>>>massively to disk.  I mean, unbearable lag if I open anything other than
>>>an xterm.  X seems to swap for a few minutes (lots of disk action) if
>>>anything more than that one xterm is opened.  Does anyone know what the
>>>deal is with all of these different reports?
>>
>>Is this the new X or the old one ?
>>I remember back when I had 4 megs (on a 386dx25) and just got linux going
>>with 0.97pl2 MCC dist. + X (ie X 1.0) and, yep, just having XClock, XBiff
>>going beside an Xterm made it unusable...
>>
>i am unable to get X to work with only 4M.  The server works fine .98,
>but it crashes the system On 0.98.4 or later.  Maybe this is the same
>problem that has beem complained about.  It looks like the kernel is
>killing jobs, but i cannot tell since X is usually what ends up
>killed.

First, monitor the swap space usage.

I have been using (Xwindow + Xview3) with 0.98.2, 98.3, 98.4, 98.5
and now 98.6, without any problem  with only 4M bytes without math processor.
I use X stuff from SLS distribution.
When I start X, I open 3 xterms, oclock, xeyes with olwm.
I found that Linux uses about 2M for swap in this case.
Xdvi, ghostview/script work just fine.
Only problem is that compiling is so slow and you need some patience when 
moving to other window (5 sec or slightly more). 
In this case, I found that Linux uses 8M for swap (twice more than my memory).


-- 
____   ____  ____ ____________________________________ (___) _________________
|  |   |  |  |  |  W. Woody Jin (wjin@cs.uh.edu)       (o o)      Moo.... 
|  |   |  |__|  |  PhD Student. Research Asst.  o=======\ /  I'm  a Cow Lover.
|  |   |        |  Dept. of Computer Science   / |     ||O   My wife  was born
\  |---|  |--|  |  University of Houston      `  ||'---||    in Cow year. Mooo
 \____/|__|  |__| _______________________________^^    ^^_____________________


Newsgroups: comp.os.linux,comp.windows.x.i386unix
From: pmacdona@sanjuan (Peter MacDonald)
Subject: status of QIC-80 driver on tsx-11.
Organization: University of Victoria, Victoria, BC, CANADA
Date: Sun, 13 Dec 92 05:54:10 GMT

Does anyone know anything about the status of the QIC-80 driver on
tsx-11.mit.edu?  I am one of the many with an IDE based computer,
and I would like to find a way of adding a backup.  The Colorado
types seem plentiful (but we have one at work, and it doesn't work
under either DELL or ISC unix, at least not in multiuser mode).

The QIC code on tsx doesn't seem to have anything to do with Linux,
so I take it someone just plunked it in there for future reference?
Am I wrong?  Is someone looking at this?  I heard mumblings months
ago about timing problems being insurmountable on a multitasking
machine.  Is this correct?

By the same token, finding a CDROM that works with an IDE based PC
would be great (could a CDROM be another read-only IDE drive, 
theoretically?).  Having to plunk in a SCSI board seems futile,
and adds to the cost and complexity of setting it up.  I am 
unenlightened in this area.  Anyone who would care to talk about
it to me, please drop me a line.  My main rational is establishing
how feasible or when a CDROM of SLS would be practical/affordable
for most of us.  I certainly am not willing to retool my entire 
system just to have it, but I would consider spending $300-$400.
Also, SCSI seems to be a bit problematic.

Also, is an EXT FS feasible for a CDROM?  Or are we doomed to using
the ISO formats?

Peter
pmacdona@sanjuan.uvic.ca

Newsgroups: comp.os.linux
From: hartnegg@sun1.ruf.uni-freiburg.de (Klaus Hartnegg)
Subject: Re: HELP!!!! SCSI problem!
Organization: Rechenzentrum der Universitaet Freiburg, Deutschland
Date: Sun, 13 Dec 92 20:02:21 GMT

adams@pdv2.fmr.maschinenbau.th-darmstadt.de (Adams) writes:

>In article <1gd9h7INNard@usenet.INS.CWRU.Edu> kbj@po.CWRU.Edu (Kevin B. Jacobs) writes:

>>   Thanks for all the help people have given me through e-mail, but it 
>>   still hasn't fixed the problem.  I tried telling fdisk my drive settings
>>   were 64 heads, 32 sectors/track and XXX cylinders.  It didn't work.
>>   I still get a partition table looking something like this when I do a 
>>   "p" from the extended fdisk menu.  (its not the exact thing, but its the
>>   general numbers)

>You may NOT use any translated values, but MUST use the actual drive
>geometry (that means: the actual number of heads/sides, the actual
>number of sectors you will use per sector, the ACTUAL number of cylinders).

Won't this crash if other operating systems also create partitions
on the same drive? I think DOS will write the logical drive geometry,
not the actual one. I have here a disk with a bot more than 1000 real
cylinders that gets mapped to 200 by an adaptec.
Can I use Cylinders 1-500 for linux and 100-200 for DOS at the
same time????? I think not.

-- 
------------------------------------------------------------------------------
Klaus Hartnegg, Kleist-Str. 7, D-7835 Teningen, Germany | This text reflects  
Internet : hartnegg@sun1.ruf.uni-freiburg.de            | MY opinion, not that
Bitnet : hakl@dfrruf1 or hartnegg@cernvm                | of my employer !     
Newsgroups: comp.os.linux
From: timp@extro.ucc.su.OZ.AU (Tim Posney)
Subject: SoundBlaster CD-ROM
Organization: Sydney University Computing Service, Sydney, NSW, Australia
Date: Fri, 18 Dec 1992 03:11:07 GMT

Is anyone writing a driver for this ?

If not does anyone have the technical specs on the interface and I'll
attempt to write one.
regards tim
Newsgroups: comp.os.linux
From: vds7789@aw2.fsl.ca.boeing.com (Vincent D. Skahan)
Subject: Re: Prob: ELM from SLS.98p[56] = no password entry ?
Keywords: ELM PASSWORD PASSWD
Organization: none
Date: Tue, 15 Dec 1992 14:36:30 GMT

acornwal@fox.nstn.ns.ca (James MacLean) writes:

>ELM was working fine for me with 98p5 + Image from 98.6 but now that I have
>added some more of the additional 98.6 benefits (shadow passwords,etc...),
>ELM states that there is no password entry for every user except ROOT. What
>gives?

elm likes users to have passwords...give them one.
-- 
   ---------   Vince Skahan   ----- vds7789@aw101.iasl.ca.boeing.com ------- 
	The weather ??? It's Seattle.  It's winter.  It's raining.
From: ansgarr@rama.informatik.rwth-aachen.de (Ansgar Radermacher)
Newsgroups: comp.os.linux
Subject: SCSI Controller
Date: 12 Dec 92 12:59:24 GMT
Organization: Rechnerbetrieb Informatik - RWTH Aachen
NNTP-Posting-Host: rama.informatik.rwth-aachen.de
Keywords: scsi, adaptec


	Hello

I have a SCSI harddisk Quantum PD 210s and I want to buy a controller
for using it with the PC. I am thinking about the Adaptec 1542, but if there
is a cheaper solution (it shouldn't be a slower solution) that can be used
with Linux I would like to hear about it.
I also considered the Adaptec 1522, but I am not sure if it is supported
yet.
I heard that the Seagate ST01/ST02 might not work with my drive. Is this
true ?

Thanks
	Ansgar


PS: I have a 486 DX 33 with a microtel board

-- 
ansgarr@Pool.Informatik.RWTH-Aachen.DE                    Ansgar Radermacher
Tel. +49 241 34852		            Schuetzenstr. 22, DW-5100 Aachen
Newsgroups: comp.os.linux
From: tannerrj@cnsvax (ROOT OF INSIGHT-- A 486 RUNNING LINUX V0.99)
Subject: Fujistu
Organization: University of Wisconsin Eau Claire - Power Users
Date: Sun, 20 Dec 1992 11:28:00 GMT
News-Software: VAX/VMS VNEWS 1.41    
X-Posted-From: cnsvax.uwec.edu
NNTP-Posting-Host: sol.ctr.columbia.edu

I am looking for the stats (heads, sectors and cylinders) for
the Fujistu SCSI drive model number m2624F-512. Thanks
Newsgroups: comp.os.linux
From: tfoley@camaro (Tim Foley)
Subject: Upgrade to PL6 process?
Organization: camaro
Date: Sun, 13 Dec 1992 18:43:41 GMT
Summary: What has to be done...


  Someone mentioned that UUCP will break with PL6 and than PS broke with 
PL4....whats the story?
 
  I'm still running PL1, and would like to get tcp working, so I'm ready to 
take the PL6 plunge...but what things need patching?
 
			1) I have the minicom PL6 Patch
			2) Does uucp need a patch?
			3) Does ps need a patch?
			4) Does anything else need....
 
Please reply in the group as quite a few others have been asking the same 
question. 
 
			


-- 
--------------------------------------------------------------------------
  The HeartBeat of America...Yesterdays Camaro Z28
  Call the Camaro Linux Pub-access site: 1-416-238-6550 USRobotics HST
  Note: Please, no ftpmail or mailing lists or the host gets annoyed :)
Newsgroups: comp.os.linux
From: cdapor@iiic.ethz.ch (Carlo Dapor)
Subject: Buying a SVGA Card...which one should i get?
Originator: cdapor@c11
Keywords: svga, graphics
Organization: Dept. Informatik, Swiss Federal Institute of Technology (ETH)
Date: Tue, 15 Dec 1992 09:01:37 GMT

Hello people,

I'm looking forward to get a new (and considerably faster) SVGA card for my comp, since the Trident 8900C is veeeeeeeery slow (especially when using X...).
So, what I am trying to get is a fast moderate priced card (means no 1000$ TIGA...). The performance of that actix was quite impressive....or an ATI Graphics ultra pro? What should I buy? The Xserver should support it (now or in near future). I am using MSDOS on the same HD (shameshame :)). Here comes my config (maybe that has an influence to the choice of he card *shrug*):

Intel 486/33
16MB RAM
240MB HD

If somebody could help me here, I would be thankful.

ILG
From: h235_003@ccvax.ucd.ie (ARE WE HAVING FUN YET)
Newsgroups: comp.os.linux
Subject: Can't make 0.98pl6 !
Date: 12 Dec 92 19:17:34 GMT
Organization: University College Dublin


I'm having trouble making the 0.98pl6 kernel - everything goes fine until
it gets to linking things, then I get a load of Undefined symbols - mostly
_put_fs_long, _put_fs_byte, and things like _set_bit and _clear_bit.

How do I get this to compile  ??? (I have the SLS 0.98 distribution with 
the 2.2.2d gcc libs)


Ronan Mullally
(H235_003@ccvax.ucd.ie, year3-23@midir.ucd.ie)


Newsgroups: comp.os.linux
From: jem@snakemail.hut.fi (Johan Myreen)
Subject: Re: Dell PS/2 type mouse in X
Organization: Helsinki University of Technology, Finland
Date: 11 Dec 92 20:13:11 GMT

In article <1992Dec9.231707.24498@wam.umd.edu> hunley@wam.umd.edu (Joshua Hunley) writes:

>   I am having trouble getting my ps/2 style microsoft mouse to
>work in X. I set the mouse to "Microsoft" "/dev/dmouseps2" in Xconfig
>and can get the mouse to move some. It will only move acress the top of
>the screen sporaticaly.
>   Any ideas on how to fox this problem? The mouse works fine under
>ms-windows and with the mouse test program in the SLS X distribution.

The PS/2 mouse does not use the same protocol as the Microsoft serial
mouse. The X server does not yet support the PS/2 mouse protocol, so
you'll need to use the mconv mouse protocol converter available on
nic.funet.fi in pub/OS/Linux/tools/mconv.c. Instructions for use are
included in the file.

--
Johan Myreen
jem@cs.hut.fi
Newsgroups: comp.os.linux
From: johnsonm@lars.acc-admin.stolaf.edu (Michael K. Johnson)
Subject: Can't boot .99, where's the bug?
Organization: St. Olaf College; Northfield, MN  USA
Date: Tue, 15 Dec 1992 04:35:45 GMT


I have been struggling with this, and I am finally bringing it out and
asking the newsgroup.

I have linux .99, lilo .7, and poeigl 1.7, all compiled and installed,
on a plain jane IDE drive (no SCSI, so no disktab)

With this setup, I can boot .98.6 just fine, and that is what I am
using now.  However, both with .99, and with .99+little patch that
Linus posted, I cannot get it to boot.

I have correctly specified the root device, both in the kernel
Makefile, and in the LILO config file.

Everything goes dandy until the Linux banner is printed, then the line
init/main.c:execve("/etc/init",argv_init,envp_init); is executed, and
*nothing* else happens.  No disk access, no "Unable to handle kernel
paging request", no nothing.  I know that the root device is set
correctly, because if I boot
LILO boot: vmlinux.new root=302
(where 302 is bogus (my swap partition)) linux complains that it can't
mount the root partition.  No such message is printed in the other
case, and linux does find /etc/init.  (I tried changing the kernel to
look for /etc/foo, and it fell through, so I know that it is exec'ing
/etc/init.)  So init doesn't like something, as far as I can tell.
But remember, it works with .98.6.

I tried removing the call to parse_command in init/main.c, thinking
that init might be choking on options passed to it without my
knowlege, and I had no success with that, either.

Adding a printf() (yes, it /is/ supposed to be printf in this part of
the kernel, no mistaken flames here, please -- read the source
yourself) after the call to execve() mentioned earlier confirms that
it is at exactly that point that my computer is hanging.

I have re-build poeigl and reinstalled it.  No luck.  I tried an older
version of poeigl.  No luck.  (I went back to 1.7, don't worry) I have
reinstalled my LILO, including making a new map file.  No luck.  I
added Linus's patch.  No joy at all.  Please, someone, help.  I am
stymied.  I'd rather not stay with .98.6 all my life, as wonderful as
it is.

michaelkjohnson
Organization: Ryerson Polytechnical Institute
Distribution: na
Date: Friday, 18 Dec 1992 17:29:44 EST
From: <ACPS7221@RyeVm.Ryerson.Ca>
Newsgroups: comp.os.linux
Subject: Re: dbx debugger out there?
 <1992Dec18.144035.10768@monu6.cc.monash.edu.au>

  I have xxgdb compiled with 0.99 and gcc 2.3.2 if anyone is interested.
  xxgdb is a X11 interface for gdb.
                                   Michael.
Newsgroups: comp.os.linux
From: jem@sunSITE.unc.edu (Jonathan Magid)
Subject: Re: ps that uses /proc
Organization: University of North Carolina, Chapel Hill
Date: Mon, 14 Dec 1992 08:39:29 GMT

In article <1992Dec14.032831.9921@u.washington.edu> barr@stein.u.washington.edu (David Barr) writes:
>Has anyone written a version of ps that uses the proc file system?  I
>couldn't get my old version of ps to work with linux 0.99, so I wrote
>my own ps program.  It uses the proc file system, so it should work
>with any version of the kernel which includes this file system.  There
>are a few major disadvantages of my program.  Because I wrote it in a
>hurry, the output is kind of non-standard and there are only 3 options
>(a, u and x).  I may fix it later if there is any interest.  There
>were a few fields that I couldn't figure out how to get out of the
>proc system.  These fields include MEM%, CPU%, MEM% and TIME.  I also
>don't do nearly as much error checking as I should.  All that aside,
>it does just about everything I need it to.  So here is the code
>(comments are welcome):


Good idea... someone else (poe@daimi.aau.dk (Peter Orbaek)) did do this though 
in perl (good thing too. it allowed me to save my system without having to 
reboot and corrupt my file system, but thats story for another day.  thanks
Peter!).  His version is Posix compliant and works quite well. :)

But being in perl, it's probably a bit slower than yours.

jem.
-- 
Jonathan Magid     jem@sunSITE.unc.edu       sunSITE Administrator
Virtual pizza Delivery (tm)::faxed in 30 cycles or less or you get it
----------------------------------------FREE!!!-----------------------
Newsgroups: comp.os.linux
From: andrewc@aurora.cc.monash.edu.au (Andrew J. Cosgriff !)
Subject: Re: DikuMud/pennMUSH ??? with .98.pl5
Organization: Monash University, Melb., Australia.
Date: Sun, 13 Dec 1992 23:16:36 GMT

bmyers@shyguy.lonestar.org (bob myers) writes:

>I've pull both DikuMUD and also pennMUSH down, due to having an interest
>in MUDs now.  Unfortunately, I can't get either to work properly:

>1) DikuMUD will start up, however -- as soon as i telnet back into the
>   system (i'm using a Tandy 4800HD laptop), I get a message about connecting
>   into the game.  I try to type something into the dikuserver program, but
>   as soon as i hit any key...the connection is closed.

>   I look in the virtual console that shows the server running and see
>   that gethostbyaddr is having a problem, that a EOF was read on the
>   socket, and one other warning came up (which i can't remember now).

>2) pennMUSH will start up, but will kick me out also (along the same lines
>   as what happens with Diku?), when I try to telnet into the system port.

Erm i get the same problems just telnetting to the loopback port normally...
But for my MUD (I'm using LambdaMOO), i'm using mud.el (an emacs script) to
connect and it works fine !!! (No, telnet doesn't work either...)

(I haven't got TinyTalk to compile yet - a bit too BSDish for Linux to
compile it straight, it seems, although I remember someone saying they did
get it going...)

You can get mud.el at parcftp.xerox.com, in the pub/MOO/clients dir.
(if you can't, ask me and i'll send it or put it on sunsite...)

Enjoy !

Cos !
-- 
-------------------------------------------------------------------------------
 * Andrew J. Cosgriff ! *                   #include <std_witty_quote.h>
#define HERE cc.monash.edu.au               #include <std_disclaimer.h>
Hassle me at :      andrewc@aurora.HERE ; andrewc@lindblat.HERE ; cos@yoyo.HERE