HDTenEightyP/NetNews huggingface dataset:
From: gt0178a@prism.gatech.EDU (Jim Burns)
Newsgroups: comp.os.linux
Subject: Re: Problems with serial port drivers??
Date: 12 Apr 92 20:35:10 GMT
Organization: Georgia Institute of Technology

in article <LILJEBER.92Apr11124027@kruuna.Helsinki.FI>, liljeber@kruuna.Helsinki.FI (Mika Pekka Liljeberg) says:

Sorry - we don't get alt.os.unix here, so I couldn't crosspost.

> using the same IRQ line simultaneously. Isn't it possible to poll all the
> UARTS on the IRQ line in the interrupt handler? Ie. you'd need a slightly

You're not *supposed* to be able to do this. The ISA interrupts are level
triggered, which I believe means that after the ICU latches the first
interrupt, a 2nd one won't still be active after the first one is serviced.
You might try polling all devices on any interrupt, not just poll for the
*first* device that needs service. Don't know how successful that would be.
The MCA interrupts are level triggered, so this is not supposed to be a
problem there.
-- 
BURNS,JIM (returned student)
Georgia Institute of Technology, 30178 Georgia Tech Station,
Atlanta Georgia, 30332            | Internet: gt0178a@prism.gatech.edu
uucp:	  ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!gt0178a
From: michael@gandalf.informatik.rwth-aachen.de (Michael Haardt)
Newsgroups: comp.os.linux
Subject: line printer deamon for Linux, any suggestions?
Date: 5 Apr 92 18:12:59 GMT
Reply-To: u31b3hs@messua.informatik.rwth-aachen.de (Michael Haardt)
Organization: Gandalf - a 386-20 machine

I applied the 0.95a patches to the 0.95a kernel, corrected the out_b
instruction with exchanged parameters and changed the test to != 255.
I have one printer connected to lp0 and everything works ok.

Now I need a line printer deamon.  I wrote a small deamon with lpd, lpr,
lprm and lpq a few months ago for MINIX.  It is a simple deamon, only made
for one queue.  I am not familiar with real UNIX printer deamons, I know
how to use lpr, lpq and lprm, that's all.

My deamon will be started by lpr and then runs until the queue is empty.
When there is nothing to print, no deamon runs and no resources are
wasted.  It supports multiple kinds of paper, because I sometimes change
between single sheets and endless paper.  It has no priority classes, no
net interface, no printcap, no multiple queues with job scheduling or
things like that.

-  Would you prefer a standard system V deamon?
-  Do you think a Linux specific deamon with special support for typical
   PC problems (multiple kinds of paper etc.) may be better?
-  I don't know how printcap works, I only know it is a termcap like
   database for printer capabilities.  Do you think it is useful, do you
   use it and can you give me more informations about it?
-  I thought about running the spool files through compress, the printer
   is so slow, that uncompressing should not need much CPU power.  Any
   comments?
-  My lpr does not know any filter options.  Do you consider them to be
   useful?  Any suggestions, standards on how to implement them?
-  My lpr does not change the incoming data in any way, no \n to \r\n
   expansion, no tab expansion, no line break after a fixed number of
   characters etc. Ok?

I set the \n -> \r\n menu entry on my printer, so I can print usual text
files without converting them.

I am waiting for your suggestions, what would you appreciate to see in a
line printer deamon package?

Michael
From: ajayshah@alhena.usc.edu (Ajay Shah)
Newsgroups: comp.os.linux
Subject: Re: User's Guide project
Date: 11 Apr 1992 14:09:32 -0700
Organization: University of Southern California, Los Angeles, CA
NNTP-Posting-Host: alhena.usc.edu

knapka@athena.cs.uga.edu (Joseph Knapka) writes:

>There's an embryonic project underway to collect/write a reasonably
>coherent User's Guide to Linux. I include here an excerpt of recent
>discussion from the man-page mailing list, and invite comments on the
>plan outlined. We're especially looking for comments / criticism /
>volunteerism on the following points:
>1) Do you think there is a need for such a document?

Yes, I think such a document would be rather valuable.

Linux is great.. what more could a hacker ask for?
But we could make the results of the same work accessible to
a much larger class of users if we add "a little" effort
on documentation and easy-to-use installation/administration.

        -ans.
-- 

Ajay Shah, (213)749-8133, ajayshah@usc.edu
Xref: sparky comp.os.linux:221 comp.sys.ibm.pc.hardware:13344
From: berger@atropa (Mike Berger)
Newsgroups: comp.os.linux,comp.sys.ibm.pc.hardware
Subject: Re: Help: Straighten Me Out on SCSI Controller Cards (Host Adapter?)
Date: 7 Apr 92 16:06:52 GMT
Article-I.D.: ux1.1992Apr7.160652.14458
Organization: University of Illinois at Urbana

sonny@charybdis.harris-atd.com (Bob Davis) writes:
>	I am *so* confused about SCSI -- all aspects of it. And I can't
>seem to locate answers. First, what do I get for the $250 for an Adaptec 1542
>SCSI controller that I don't get with the $150 controllers , or with the $35
>Seagate ST02?
*----
The extra money buys substantially higher performance.  The Seagate is
the bottom-of-the-line.  It uses the CPU heavily, and doesn't support
non-Seagate drives too extensively.  I don't know what kind of software
is available for tape or CD-ROM drivers.

The Adaptec 1542B is on the opposite end of the spectrum.  It's a
bus-master disk controller, and has very high performance if your
motherboard can handle it.  Software support is excellent.

At the higher end are EISA type controllers, and below the 1542B
are non bus-master controllers that are a lot smarter and faster
than the ST-01/02.

--
	Mike Berger
	Department of Statistics, University of Illinois
	AT&TNET     217-244-6067
	Internet    berger@atropa.stat.uiuc.edu
From: kxb@matt.ksu.ksu.edu (Karl R. Buck)
Newsgroups: comp.os.linux
Subject: Where are expr and mkdir binaries?
Date: 9 Apr 1992 20:02:13 -0500
Organization: Kansas State University
NNTP-Posting-Host: matt.ksu.ksu.edu

Subject says it all. Please email and I'll followup. Thanks.
-- 
Karl Buck, kxb@matt.ksu.edu 	:)
Newsgroups: comp.os.linux
From: jwinstea@jarthur.claremont.edu (Jim Winstead Jr.)
Subject: Re: 0.95c+ bootimage on tsx-11, will there be a rootimage?
Organization: Harvey Mudd College, WIBSTR
Date: Sun, 12 Apr 1992 02:13:49 GMT

In article <nolan.703010240@helios> nolan@helios.unl.edu writes:
>I see that a bootimage for 0.95c+ has arrived on tsx-11, will there be a
>corresponding rootimage file?  (Linus's message said he would post a new
>kernel, but didn't the patches since 0.95a also involve stuff in rootimage?)

There won't be a corresponding root image release.  None of the
patches since 0.95a affected the root disk except for a new fdisk,
which is available in source form on tsx-11 as system-0.95a.tar.Z.

So, you're okay using the 0.95a root image, unless you plan on mucking
around with extended partitons.  (Even then, the 0.95c+ kernel does a
fdisk-like listing upon booting, so you could get by with that.)

The next release of Linux, 0.96, will have a new rootimage, and we'll
be changing the numbering scheme a bit.  More on all this later....

-- 
Jim Winstead Jr. (CSci '95)    | "Catch a fish!"
Harvey Mudd College            |  -Geddy Lee,
jwinstea@jarthur.Claremont.EDU |   San Diego Sports Arena
Disclaimer: Mine, not theirs!  |   January 20, 1992
From: cheetah@sage.cc.purdue.edu (Bowen (Laughing Cheetah))
Newsgroups: comp.os.linux
Subject: Re: HELP! Problems with rootimage.
Date: 9 Apr 92 20:49:12 GMT
Article-I.D.: mentor.44663
Distribution: comp
Organization: Purdue University Computing Center

In article <1992Apr8.210115.5364@vax.oxford.ac.uk> tony@vax.oxford.ac.uk writes:
>In article <TSILLANP.92Apr7144847@blob.hut.fi>, tsillanp@niksula.hut.fi (Timo Jaakko Sillanp{{) writes:
>> ...
>
>> Am I doing something totally wrong? 
>> I get rootimage.Z from nic.funet.fi (yes, binary mode is on),
>> uncompress it and write it to a floppy disk (1.44Mb) using
>> rawrite.exe. 
>
>the rootimage is (I think !) for a 1.2Mb floppy.  Try to find a rootimage for a 
>1.44 disk - this could be the problem ...

The images I have seem to work without any difficulties for either 1.2MB or
1.44MB disks.  Since (to my understanding) they are raw images, it dosen't
really matter how big the disk is, just as long as the entire thing fits.

	-bg
-- 
________________________________________________________________________________
Bowen Goletz
Purdue University                  Midi 'n Music
cheetah@sage.cc.purdue.edu         Bowen.Goletz@f120.n201.z1.Fidonet.Org
From: knapka@athena.cs.uga.edu (Joseph Knapka)
Newsgroups: comp.os.linux
Subject: <assert.h> in gcc2.1
Date: 8 Apr 92 13:39:22 GMT
Organization: University of Georgia, Athens

Has anyone had trouble using assert under gcc-2.1? The problem I'm
having (and it only takes a trivial bit of code to demonstrate) is
that while #define-ing NDEBUG turns off assertions as advertised, it
seems that subsequently #undef-ig NDEBUG and re-#include-ing
<assert.h> *fails* to turn them back on.  Am I hallucinating, or is
there really a problem?

Thanks for any assistance,

Joseph
Newsgroups: comp.os.linux
From: cummings@hammer.Prime.COM (Kevin Cummings)
Subject: Re: Modems and com port access
Organization: Prime Computer R&D
Date: Mon, 13 Apr 1992 18:38:42 GMT

In article <1992Apr10.233541.472@magnus.acs.ohio-state.edu>, bjones@magnus.acs.ohio-state.edu (William A Jones) writes:
> Now that I have a copy of UUCP for linux, I decided that it was time to
> see if my modem worked properly.  So, I scanned all of the digest entries
> that had anything to do with the modem and decided that, under version
> 0.95c+, COM2 was assigned to /dev/ttys2.
> 
> Following the FAQ, I put the following line in /etc/inittab
> 
> ttys2:console:/bin/getty -m 1200 ttys2
> 
> and rebooted.  So far, so good.
> 
> Now, kermit, uucico, pcomm, and everything else will not recognize that
> a modem exists.  What have I done wrong?

While getty is running, it "owns" the serial port device (/dev/ttys2).
Kermit, uucp, pcomm, etc can't open it to use it.  In order to fix this
problem, you need to get something like the acu.pkg that was posted
recently.  On my Sun system (at work), the getty is intelligent enough to
release the serial line when some other process wants to use it for outgoing
(instead of waiting for incoming).  The current getty in LINUX is not so
smart.  The acu.pkg indictased that it might be better at this (tho I haven't
tried it yet!)

> If someone who has a working kermit, uucp, etc., would send detailed(!!)
> instructions on how to get set up I would be very grateful.

Gladly, after I download uucp and get it working B^).

=================================================================
Kevin J. Cummings                       Prime Computer Inc.
20 Briarwood Road                       500 Old Connecticut Path
Framingham, Mass.                       Framingham, Mass.

Work:  cummings@primerd.Prime.COM
Home:  cummings@kjc386.framingham.ma.us

Std. Disclaimer: "Mr. McKittrick, after careful consideration,
		  I've come to the conclusion that your new
		  defense system SUCKS..."   --  War Games
=================================================================
From: choma@staff.dccs.upenn.edu (Peter Choma)
Newsgroups: comp.os.linux
Subject: Re: Loadable Device drivers.
Keywords: devices, drivers, linux, project
Date: 16 Apr 92 03:31:48 GMT
Organization: University of Pennsylvania

In article <1992Apr15.125511.28578@donau.et.tudelft.nl> wolff@dutecaj.et.tudelft.nl (Rogier Wolff) writes:
>
>Hi everyone,
>
>I will be doing a project involving the implementation of 
>"loadable device drivers" in linux. This will facilitate developing
>new device drivers: you should be able to:
> ...
>					Roger

Beta? copies of Solaris 2.0 should be released sometime in June'92. 
Solaris 2.0 will use a new design for device drivers which differs from 
SunOS 4.1 It might be useful to use Solaris 2.0 as a model since Solaris 2.0 
will support device drivers which can be load/unloaded on the fly without 
rebooting the operating system.

The ability to load/unload device drivers while the system is running is
a very useful feature as it makes it much easier to test new device drivers
and it makes it much easier to have systems auto-configure themselves.

Newsgroups: comp.os.linux
From: cm445a17@socrates.umd.edu (cm445a17)
Subject: Sockets, Tubes--> IPC status for Linux????
Organization: University of Maryland University College
Date: Thu, 16 Apr 1992 05:40:46 GMT

What is the current status of the IPC library for Linux?  I have been
playing around with the socket libray emulation a little and I was
wondering if people are still working on it.  Also, I've seen in the ftp
sites the tubes library.  What is it exactly?  Does it work with the
latest version of Linux (0.95c+)?  Thanks,

Jaime Jofre
From: rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson)
Newsgroups: comp.os.linux
Subject: Re: tar files on floppy.
Date: 15 Apr 92 13:16:48 GMT
Article-I.D.: nmrdc1.1992Apr15.131648.17230
Organization: Naval Medical Research & Development Command

In article <1992Apr14.221309.19168@ods.com> david@ods.com (David Engel) writes:
>rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson) writes:
>: I am just about finished with linking everything in 2.1shared-A.tar.Z with
>: shared libs and symlinking into /usr/bin.  A word of caution, DON'T use
>: shared libs or symlinks on anything in /bin or /etc if / and /usr are on
>: different partitions.  They won't work until /usr is mounted.  Keep a good
>: bootimage floppy and root floppy handy just in case.
>
>If you copy the shared lib to /lib instead of symlinking it (done by the 
>install script) you can use shared binaries in /bin and /etc.  You can also 
>safely remove /usr/shared the next time you upgrade libraries.  It's still 
>a good idea to have "emergency" boot and root floppies handy however.
>
Good news.  I had thought about this and will very likely do it.  With only
a 4 Meg root partition, I ran out of space attempting to install the shadow
passwd utilities.  Converting all binaries in the root partition to shared
libs will save lots of space.  Now I just need to go back and grab the src
for the shadow stuff to compile and link it for shared libs.  I assume I
should also cp the shared binaries into /usr/bin rather than using symlinks
to /usr/shared/bin.

Mike

-- 
LCDR Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil
nmrdc1.nmrdc.nnmc.navy.mil      | UUCP:   ...uunet!mimsy!nmrdc1!rdc30
AT&T 3B2/600G Sys V R 3.2.3     | BITNET:   dobson@usuhsb or nrd0mxd@vmnmdsc
WIN/TCP for 3B2  R3.2           | MCI-Mail: 377-2719 or 0003772719@mcimail.com
Newsgroups: comp.os.linux
From: bbrown@b11.ingr.com (Bailey Brown)
Subject: ksh in linux?
Keywords: linux ksh
Organization: Intergraph Corp. Huntsville, AL
Date: Mon, 6 Apr 1992 19:30:31 GMT

Does linux have ksh (Korn Shell)?  And if so, does it's ksh implementation
have the command line editing (vi mode)?

------------
Bailey Brown                               "Above all else, confusion reigns."
Intergraph Corporation                                  
bbrown@casca.b11.ingr.com                              Procol Harum
Newsgroups: comp.os.linux
From: drew@kinglear.cs.colorado.edu (Drew Eckhardt)
Subject: Re: AS86
Organization: University of Colorado at Boulder
Date: Fri, 17 Apr 1992 05:54:51 GMT

In article <54893@hydra.gatech.EDU> gt0449a@prism.gatech.EDU (Rob Coleman) writes:
>I'm curious just what is necessary in an assembly source file to create
>an executable with either as/ld or as86/ld86.  Maybe a better question
>is which is the preferred assembler (if there is one), and what is the
>basic format of the file, and method to assemble and link it?  Ultimately,

as86 and ld86 are used for two files in the kernel source tree, 
boot/setup.S, boot/bootsect.S.  They create 80x86 REAL mode code.

You MUST use gas (as) and gld (ld) for 386 code.  gas uses that AT&T 
syntax, which differs radically from intel syntax.  

Texinfo gas documentation is available from prep.ai.mit.edu under 
the usual /pub/gnu directory, so I won't cover the Intel / AT&T syntax
differences other than saying you need the documentation.

Also, remember that as is designed to read compiler output, not human
generated code, and if you want ANY macro capabilities, use the 
C preprocessor.  Also, when given a .S file, gcc 2.x will run 
cpp on it before passing it to as, and running gcc on a .s file 
will 'do the right thing'

>I will probably just be hacking the assembly portion of the kernel which
>doesn't require that I know this, but I'd also like to be able to create
>standalone programs.
>Thanks..
>

For very small things, that have minimal use of the library functions 
(or only syscalls), you can just make an assembler program, which is 
entered at address zero, and has a call to __exit, assemble it,
and link it to libc.a.  For more substantial things, 
write a 'C' driver, or _main function in assembler 

ie 
.globl main
_main:

and link as a normal 'C' program.  

Interfacing to 'C' is done in the usual way, with parameters pushed 
in reverse order, on a 32 bit wide stack, 32 bit return address, caller
removing parameters.  Naming convention is standard 'C', with all 
global symbols prefixed with an _.  

Xref: sparky comp.os.linux:361 alt.os.linux:2440
From: cummings@hammer.Prime.COM (Kevin Cummings)
Subject: Re: bash ?   And Root disk software.
Organization: Prime Computer R&D
Date: Tue, 7 Apr 1992 20:07:22 GMT

In article <1992Apr7.112626.422@spacm1.spac.spc.com>, audit036@spacm1.spac.spc.com (David.L.) writes:
> Where do I get am image or sources for bash ? do I need to get the earlier root
> image ? (.12 , .11 ) ? I'm using 0.95a.

My hard disk with 0.95 installed over 0.12 crashed.  After getting a new
drive, I found myself having to install from scratch.  So I went and
got the latest root disk 0.95a.  When I found that BASH was not on
it, I mounted the 0.95 root disk and copied both BASH (/bin/sh) and the
PASSWD executable from it to my new system disk (/usr/local/bin/bash,
and /bin/passwd).

In a related issue, When I formatted my new 200MB IDE drive under DOS,
I created one DOS primary (bootable) partition, and put the rest
of my DOS logical drives in the DOS extended partition.  This leaves
me two primary partitions for LINUX, which I configured using the
pfdisk on the 0.95a root disk.  However, the infamous extended partition
bug kept both the 0.95 and 0.95a fdisk from correctly reading my
partition table on /dev/hda.  This resulted in my inability to
know for sure which logical linux devices I needed to run mkfs and
mkswap on!  I had to get the fdisk from the 0.12 root disk, and
create a /dev/hd0 link to /dev/hda in order to find out which
was /dev/hd3 (/dev/hda3) and which was /dev/hd4 (/dev/hda4).

patches to the kernal are NO GOOD if you cannot be sure which
devices to make in order to put your system on hard disk!

Based on this, someone had better put together a BOOTIMAGE and
a ROOTIMAGE for 0.95c if we want users to be able to install
LINUX in systems that do not already have LINUX partitions!
You just can't expect non-hacker users to have to have 3 rootdisks
around to get all the necessary software in one place (never mind
the changing of the device names too.  Sigh).

When I get done re-creating my system, I'll be happy to post a list
of the software I had to download, in addition to what was on the
0.95a root disk, and install in order to make my system useable
to me.

=================================================================
Kevin J. Cummings                       Prime Computer Inc.
20 Briarwood Road                       500 Old Connecticut Path
Framingham, Mass.                       Framingham, Mass.

InterNet:  cummings@primerd.Prime.COM
UUCP:      uunet!primerd.Prime.COM!cummings

Std. Disclaimer: "Mr. McKittrick, after careful consideration,
		  I've come to the conclusion that your new
		  defense system SUCKS..."   --  War Games
=================================================================
Xref: sparky comp.os.linux:424 alt.os.linux:2492
From: dingbat@diku.dk (Niels Skov Olsen)
Newsgroups: comp.os.linux,alt.os.linux
Subject: Re: Keyboard dies when I hit Caps-Lock (+SCSI)
Date: 13 Apr 92 22:49:13 GMT
Organization: Department of Computer Science, U of Copenhagen

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

[My keyboard locks up when Caps-Lock is hit both in scsi-version
at sc.tamu.edu (DK and US keyb.) and in the scsi0.95c+ version at
headrest.woz.coloradu.edu.]

[scsi devices now use major 8]

>The keyboard : 

>Does the keyboard lock up, period, do numlock, CAD still work,
>or not?

Ok I checked it more thoroughly.

Following keys gives TOTAL lock up but with Linux stil running:
	Pause
	Scroll Lock (gives a task-info)
	Caps Lock
	Num Lock


When these keys are hit all following keys will make a beep instead
of normal function except Return/Enter which will restore the normal
state:
	PgUp
	PgDn
	Home
	End
	Ins
	Del

The scsi0.95c+ version from headrest is only tested with the supplied
keyboard driver since I cannot yet compile it.

Niels
From: gt0449a@prism.gatech.EDU (Rob Coleman)
Newsgroups: comp.os.linux
Subject: AS86
Date: 17 Apr 92 04:02:34 GMT
Organization: Georgia Institute of Technology

I'm curious just what is necessary in an assembly source file to create
an executable with either as/ld or as86/ld86.  Maybe a better question
is which is the preferred assembler (if there is one), and what is the
basic format of the file, and method to assemble and link it?  Ultimately,
I will probably just be hacking the assembly portion of the kernel which
doesn't require that I know this, but I'd also like to be able to create
standalone programs.
Thanks..

-- 
        Rob Coleman              ][   Science, like nature, must also be tamed. 
  gt0449a@prism.gatech.edu       ][     With a view towards its presevation..
Georgia Tech, P.O. Box 30449     ][
     Atlanta, GA  30332          ][                  -Rush/Natural Science
Newsgroups: comp.os.linux,alt.os.linux
From: jwinstea@jarthur.claremont.edu (Jim Winstead Jr.)
Subject: Re: all kinds of questions
Organization: Harvey Mudd College, Claremont, CA 91711
Date: Tue, 14 Apr 1992 01:35:38 GMT

In article <1992Apr13.223428.29499@colorado.edu> drew@ophelia.cs.colorado.edu (Drew Eckhardt) writes:
>In article <1992Apr13.191537.8035@coe.montana.edu> icsu8268@cs.montana.edu (Greenup) writes:
>>
>>Hello netters!
>>   I just booted up for the first time two days ago, and now I'm a happy
>>Linux user.  Well, almost.  I do have a few questions...
>>
>>1. is "agetty" different than "getty", if so,
>
>No real obvious differences.

To clear up any questions:  The 'getty' on the 0.95a root disk is the
*exact* same program as 'agetty' on the 0.95 root disk.  I renamed it
for the 0.95a release to be consistent with other Unix implementations.
-- 
Jim Winstead Jr. (CSci '95)    | "Catch a fish!"
Harvey Mudd College            |  -Geddy Lee,
jwinstea@jarthur.Claremont.EDU |   San Diego Sports Arena
Disclaimer: Mine, not theirs!  |   January 20, 1992
From: hns@regent.e-technik.tu-muenchen.dbp.de (Henning Spruth)
Newsgroups: comp.os.linux
Subject: German 84-key keyboard support
Date: 6 Apr 92 11:44:32 GMT

When I first installed linux on my system, I had to patch the
(german) keyboard driver, because several important keys
(<, >, ~ and some others) were missing. In addition, the
cursor keys were only accessible by pressing them together with
a shift key (84-key keyboards do not have separate cursor
keys). I'd like to know if other users with 84-key keyboards
have similar problems or if there is a bug in the german key
tables.

Henning
--
------------------------------------------------------------------------
Henning Spruth		 	  spruth@regent.e-technik.tu-muenchen.de
Institute of Electronic Design Automation
Technical University of Munich, Germany
Newsgroups: comp.os.linux,alt.os.linux