HDTenEightyP/NetNews huggingface dataset:
From: jimc@hal.gnu.ai.mit.edu (James Carpenter)
Newsgroups: comp.os.linux
Subject: Re: Seagte ST-01 with Quantum Prodrive ELS
Date: 29 Dec 1992 06:48:43 GMT
Organization: Massachusetts Institute of Technology
NNTP-Posting-Host: hal.gnu.ai.mit.edu

I have things working a little bit better now. And I have linux working with
it also!

But the keyboard still hangs (see below).

I have that AUTO_IRQ thing enabled and at boot the first line on the screen
says something about a "wild interrupt" (I think thats it) for IRQ 1
(keyboard). What does this mean and could it be related to my problems?

I know this isn't really Linux now so I guess I should move it over to
comp.sys.ibm.pc.hardware (including this note). Is there any place else I
should look for help?


I have solved half of my ST-01 problems. I have the hard drive working
PERFECTLY now but the keyboard still hangs. The drive can be working, turned
off, or unpluged, and sooner or later the keyboard will hang. I've done all
the things with the jumpers (changing IRQ, base address, & 0W/S) but nothing.
There is nothing special about my machine (that I know of, poor docs.) and
there is NO cache. And I know its not a problem with the operating system.

I just noticed something... The keyboard doesn't hang totally SOMETIMES. It
looks like sometimes the keys just get all messed up, BAD. For example "v"
SOMETIMES transmits TWO carriage returns. "d" is a backspace. And most other
letters transmit stuff above 128 (It likes the line stuff i.e. 179). And one
of the keys will turn the Scrool Lock light on. Next time it hangs the keys
can transmit something totally different.

I know this isn't my keyboard. I tried a different type keyboard.

PLEASE tell me that someone else out there has had the same problem. I don't 
want to be the only guy thats gone through this :-)

P.S. I fixed the drive problem by pulling a jumper on the motherboard that
controlled something called "pipeline". Could someone tell me what this is
so I can figure what isn't going to work now without it.

-- 

	Jim Carpenter
	CARPENTER@Eisner.DECUS.Org
	jimc@gnu.ai.mit.edu
Newsgroups: comp.os.linux
From: bkuhn@cs.loyola.edu (Bradley " b " Kuhn)
Subject: SLS problem, possible bug in 0.98 and newer kernels
Organization: Loyola College in Maryland
Distribution: comp
Date: 27 Dec 92 18:02:39

I recently posted that SLS installed fine but that it died at 

hda :

when I logged in off my new boot disk for the first time.

Actually, I found (after trying the bootimage of every kernel I could find)
that the problem occurs in all the kernels after and including 0.98.  They
doesn't have the prompt

Enter <RETURN> to see SVGA modes or <SPACE> to continue:

I usually hit <SPACE> in kernel 0.97 and the 0.98pl15 on SLS disk a1.
(this is why they work.)  On kernel tsx-11.mit.edu: 
pub/linux/images/bootimage.0.98 and the kernel that is written as the boot disk
for the SLS distribution, the prompt is skipped.  I immediatly get the

COLUMNSxROWS:

00:  ??x??
01:  ??x??
02:  ??x??
03:  ??x??
Enter the the number the corresponds to blah blah:

However, the user is not allowed to answer this prompt either (it is only
shown).  I do not have SVGA, so the screen freezes when I reach the end of
the screen (i.e. there is no scrolling).  What does the screen default to
in kernels 0.98 and after?  I want to use simple VGA mode, not SVGA.  How
can I do this with the kernel that is written to the bootdisk on SLS?
Someone *PLEASE* help!  I would really like to get SLS running before the
next semester starts.  Any linux gurus have any suggestions??????

(Sorry for the inaccuracy of the menus above, but I was doing it from 
memory...it should be easy to see which ones I am refering to....)

Please HELP,
            brad

      
--

 -- Bradley M. Kuhn    Computer Systems Development, Inc.

     INTERNET: bkuhn@cs.loyola.edu, bkuhn@loyola.edu, kuhn@cpwsca.psc.edu,
               rhlab!bkuhn@uunet.uu.net (take your pick :-)
     BITNET:   bkuhn@loyvax.BITNET
     UUCP:     ...uunet!rhlab!bkuhn
     SNAIL:    100 W. Cold Spring Lane, Box: 141, Baltimore, MD   21210
     VOICE:    (410) 617-(4343 || 4497), (x4343 || x4497 on Loyola Campus)

Newsgroups: comp.os.linux
From: marcf@nexus.yorku.ca (Marc G Fournier)
Subject: Re: Cron for Linux?
Organization: York University, CS Dept. Toronto
Date: Sun, 27 Dec 1992 19:18:51 GMT

In article <1hkr9qINNo3v@matt.ksu.ksu.edu> probreak@matt.ksu.ksu.edu (James Michael Chacon) writes:
>qumqats@citrus.SAC.CA.US ( Joel M. Baldwin ) writes:
>
>>marc@r-node.gts.org (Marc Fournier - Admin) writes:
>>: In article <1992Dec21.050300.17459@netcom.com> zmbenhal@netcom.com (Zeyd M. Ben-Halim) writes:
>>: >In article <BzL4M1.Cp8@cs.dal.ca> dinn@ug.cs.dal.ca (Michael 'Moose' Dinn) writes:
>>: >>
>>: 	It is also included in the new .99 release in /usr/bin.
>>: But...it doesn't get started as part of the installation stuff..you
>>: have to add it to /etc/rc
>
>>??????  /usr/bin?????   whats it doing in there?  shouldn't it be in /etc?
>
>>Joel M. Baldwin
>
>Then move it to where you think it belongs. The SLS stuff just installs
>where they thought things should go, it's not exactly set in stone.
>
	I have not looked at the source, but is there nothing in the
source that needs to be changed before mv'ing it?  I wouldn't see any
reason for there to be, but just in case...?

Marc
Newsgroups: comp.os.linux
From: wto@cbnewsg.cb.att.com (William T. O Connell)
Subject: [Q] Seyon
Organization: AT&T
Date: Sun, 27 Dec 1992 03:46:36 GMT

I have a couple of questions with seyon. First, Seyon.c refers
to a file 'seyon.emu'. this file does not exit (seyon.cmd is built
but none with an .emu file extension).

Where do I get this file??

Second question, is that seyon needs certain libraries 
(i.e. libX11.so.2.1 and XawVen.so.2.1; I am using SLS which
has libX11.so.2.0 and XawVen.so.2.0), I looked on various
ftp sites but, can't seem to locate them, does anyone
know were they are?

- Bill        wto@ihlpx.att.com

) 
Newsgroups: comp.os.linux
From: wto@cbnewsg.cb.att.com (William T. O Connell)
Subject: Re: pwd command missing in L
Organization: PC peripheral operational services group
Date: Sat, 2 Jan 1993 23:19:47 GMT

In article <726010584.AA29502@remote.halcyon.com> Randy.Edwards@f60.n128.z1.fidonet.org (Randy Edwards) writes:
>To: wonge@fraser.sfu.ca (Edmund Wong) 
> On 12-29-92 Edmund Wong wrote to All... 
> 
> EW>    HELP!.. I've been searching my system for the 'pwd' command,
>[...] 
> EW>    Everytime I log on as a non-root user, I get the following:- 
> EW>     Welcome to Linux SLS .... 
> EW>     ....etc 
> EW>      Your password will expire in 0 days. 
> EW>      No mail. 
> EW>      shell-init: Permission denied 
> EW>      pwd: Permission denied 
> EW>      : Permission denied 
> EW>      # 
> 
>   pwd is the command for Print Working Directory.  I think what you 
>want (but what do I know, I'm a unix-newbie :-) is "passwd". 
> 
>   Also, FWIW, you might want to look around for a file called 
>"perms.sh" which is a shell script which purports to fix the permission
>
>problems in the SLS release. 
>. 
>Randy 

I believe your actual problem is that somewhere in the directory
path to your login directory, you permissions on one or more of your
directorys is wrong. try logging in as root, and check them.

- Bill O'Connell     wto@ihlpx.att.com
From: rick@ee.uwm.edu (Rick Miller, Linux Device Registrar)
Newsgroups: comp.os.linux
Subject: Re: modem call-in/callout script
Date: 28 Dec 1992 13:39:43 GMT
Organization: Just me.
NNTP-Posting-Host: 129.89.2.33
Summary: I've never had trouble with uugetty...

bribbeck@exucom.com (Bob Ribbeck) writes:
>
>  Since the Linux wizards can't seem to creat a uugetty that will work 
>for callin and call out use this script.  It will check if uugety has a
>lock, then kill the old uugetty & init, call kermit (or your favorite)
>and when finished reinstall uugetty and reinit back to call in mode.
>All it needs is a inittab.old in /etc which is just a copy of inittab
>without the uugetty of your ttys?.  You may need to change the ttys0 in
>the script to your ttys#.

Man, this is *STRANGE*!  It *sounds* like you're still using the old getty!
I definitely would *NOT* recommend that anyone use your shell script.
It even has a *typo* in it!!  (check the first instance of "ten"...)
                                                             ^("then")

I've never had any problems using uugetty...  It works great on /dev/ttys0
with a Hayes Optima 24 (2400 baud V.42bis).  I can call into my linux-box
from anywhere else, and I can kermit out of it just as easily.  It's supposed
to be using the same lock files as the UUCP suite, so I doubt I'd have any
trouble using uucico either.

Rick Miller   <rick@ee.uwm.edu> | <rick@discus.mil.wi.us>   Ricxjo Muelisto
Occupation:  Husband, Father, WEPCo. WAN Mgr., Discus Sys0p, and  Linux fan
Newsgroups: comp.os.linux
From: pmacdona@sanjuan (Peter MacDonald)
Subject: Re: Question and Observations
Organization: University of Victoria, Victoria B.C. CANADA
Date: Tue, 29 Dec 92 00:37:10 GMT

>About your `gripes' section; I too have the same feeling about
>SLS distribution, but this is certainly _not_ the problem with
>linux itself.  We should send bug-reports and suggestions to
>people (person?) at SoftLanding so that the next release will
>have more reasonable configuration.  From what I've seen in
>c.o.l, about 30% of newbee questions and gripes wouldn't have
>been posted in the first place if SLS release did things right
>(e.g.  "/etc/passwd not being readable by everybody" comes to
>mind).  It is a trivial, but a tad tedious task to fix all the
>ownership and permission bits and such, but SLS release has so
>much influence to those naive linux users with little or no unix
>experience, we should urge and help SLS to provide more
>reasonable and easy to manage system configuration.  I think it
>would benefit us, too; we wouldn't have to be bothered by trivial
>questions every time somebody finds out his users get error
>message from `who' command, for example.

Welcome to beta software land.  Let me set the record straight
about the /etc/passwd problem: SLS has just gone to shadow
password support.   This is absolutely necessary to provide
real security for those that need it, given the advent of
the networking stuff.  Of course there were bugs in the
otherwise excellant package, which sopped up 50 hours of
my time debugging.

I made a mistake when I put together the shadow.taz package:
I should not have included /etc/passwd in it.

Anyways, these kind of traumatic changes are occasionally
necessary, particularly as we are nearing 1.0, after which
such major changes may not be viewed so charitably.

I am doing the best I can with SLS.  I can't help the fact
that minor errors on my part result in extra postings on
the internet.  A hazard of the trade.  What you don't see
are the countless hours I spent collecting and configuring
the tcpip system, shadow passwords, the install scripts, etc.
Please be patient and you will be rewarded.  But if you need
a finished product now, try SCO or DELL.

Peter
From: zdenek@ksr.com (Zdenek Radouch)
Newsgroups: comp.os.linux
Subject: Re: IMPORTANT [BUG in 0.99] Re: [ANNOUNCE]: linux version 0.99
Date: 29 Dec 92 15:33:58 EST
Organization: Kendall Square Research Corp.

Stephen Williams writes:

>Statics are either explicitly initialized or they are not.
>If they are not, their contents are UNDEFINED until set.
>This is per ANSI C.
>There is NO requirement of the compiler or system to zero
>un-initialized statics (or auto's).


I'll quote for you:

"A static object not explicitly initialized is initialized as if it 
(or its members) were assigned the constant 0. The initial value of
an automatic object not explicitly initialized is undefined."


>The fact that some systems waste time doing so is no reason rely on it
>as a feature.  This was already debated and tossed out as something to
>rely on.

Where ???

>If you wanted to clear the bss segment, as an explicit optimization
>over having nulls in your executable, link a dummy module first (ok,
>after crt0.o) and last that each have a dummy bss variable.

So that you get screwed up only in your crt0!
To quote again: "The initialization is done once only, conceptually before
the program starts executing..."
All systems I have used would do this in the loader.

>And, yes, it would be nice if the nulling were garunteed.

It is guaranteed!

>The problem
>I think is the overhead incurred for a program that has a huge bss and
>doesn't need it initialized.  A better solution would be (if it
>weren't for the headache..) to have bss and bsz segments.

That's bullshit, in the 10+ years I have been developing unix I've
never encountered environment that would omit the BSS initialization,
even as an optimization, because of the trouble this would be causing.

-Z

P.S.
You could argue that initializing explicitly might be a good PRACTICE,
but it certainly is not (and never was) required by the language definitions.
Newsgroups: comp.os.linux
From: pmacdona@sanjuan (Peter MacDonald)
Subject: where is "deliver"
Organization: University of Victoria, Victoria, BC, CANADA
Date: Fri, 1 Jan 93 21:42:15 GMT

There was talk of a program called deliver a while ago.  I have
searched for hours, but can't find it or reference to it.

Peter
From: adelt@imada.ou.dk (Adel Shavandi)
Newsgroups: comp.os.linux
Subject: Interviews 3.1 for linux ?
Summary: Interviews 3.1 for linux ?
Keywords: Interviews 3.1 for linux ?
Date: 30 Dec 92 14:40:31 GMT
Organization: Dept. of Math. & Computer Science, Odense University, Denmark




I downloaded the version 3.1 of the interviews from stanford. When trying
to compile it for linux, I got some problems. It claims about some undefined
strings when running /lib/cpp. 

Now I would like to ask the people who ported the 3.01 version to linux,
whether they did any special tricks to overcome this problem (If they had 
it at all!) What I did was to make a new iv-*.cf file in the directory for
linux and do exactly as they had suggested in the README file.

Another question is whether anybody has ported ibuild to linux? and where 
are header files of interviews 3.01?






				Thanks,

					Ade'l
From: dsc3pzp@nmrdc1.nmrdc.nnmc.navy.mil (Philip Perucci)
Newsgroups: comp.os.linux
Subject: And then came?
Date: 29 Dec 92 12:40:36 GMT
Organization: Naval Medical Research & Development Command

*------------------------------
In the beginning...
  there was Linus, and He was Good.

The rootdisk/bootdisk combination was created, and IT was Good.
Then came Peter and the shared libraries.
Then came SLS.
Then came H.J. Lu and GCC.

These, too, were Good.
------------------------------*

...something like that!

Anyway, there seems to be a substantial amount of time dedicated 
to Linux on the Internet by Linus, Peter, and H.J. Lu, as well as
COUNTLESS others.  Question, though.  Is there any way to tell at
this point which Linux distributions will survive into the future?

We have:  1) bootdisk/rootdisk
          2) GCC
          3) SLS
          4) MCC

Which distributions are for developers only?  Which are for test?
Which will die because their author gets a/another job?
Which will survive a few years, and be supported by their author
or protege(s)!?

I personally could survive for a couple years with the GCC        
distribution plus a few packages I already have.  But any feedback
on this would be MOST enlightening!

-- 
===========================================================================
  phil perucci      | "Any opinions expressed are solely my own views and 
  ssb1pzp@digex.com |  do not reflect the position of any organization"
===========================================================================
Newsgroups: comp.os.linux,comp.unix.questions
From: bvaughan@sheps.Princeton.EDU (Barbara Vaughan)
Subject: Re: Postscript to Ascii
Originator: news@nimaster
Organization: Princeton University
Date: Wed, 23 Dec 1992 06:51:16 GMT

In article <BzoF8I.2CE@watserv1.uwaterloo.ca> tglovie@sail.uwaterloo.ca () writes:
>Hello,
>
>I was wondering if there is such a beast as a postscript to ascii
>converter?  

There's something called ps2txt.  The results are pretty ugly, but look
better after piping through fmt.  Sorry, I don't know where to get it.

Barbara Vaughan

Newsgroups: comp.os.linux
From: djr48312@uxa.cso.uiuc.edu (Dennis Robinson)
Subject: Is there a SCSI FAQ for the new SCSI drivers
Organization: University of Illinois at Urbana
Date: Tue, 22 Dec 1992 05:52:20 GMT

I've tried to install the new scsi drivers 2 times to no avail.
Is there a FAQ for this?
From: andrewc@aurora.cc.monash.edu.au (Andrew J. Cosgriff !)
Newsgroups: comp.os.linux
Subject: Re: shell in emacs problem
Date: 21 Dec 92 08:35:22 GMT
Organization: Monash University, Melb., Australia.

jaffer@zurich.ai.mit.edu (Aubrey Jaffer) writes:

>Linux V0.98  from tsx-11 Dec 8
>emacs18.59   from tsx-11 Dec 8
>When I run a shell (/bin/sh) in a window in emacs (not Xemacs) as root
>or su everything works fine.  When I try it logged in as someone else,
>after every shell command it prints:

>/bin/sh: [328: 2] tcgetattr: Invalid argument

>(The 328 number changes with every invocation).  Additionally,
>isatty() called from a program I run in the shell returns 0.

>I assume that changing the permission on some file will fix this; what
>file???? (i have tried several).

Well, it wouldn't hurt to try a 
chmod -R 755 /usr/local/emacs

And see if it helps...

(I think emacs uses 'env' for shells, by the way - maybe that's it...)


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
From: probreak@matt.ksu.ksu.edu (James Michael Chacon)
Newsgroups: comp.os.linux
Subject: Re: That annoying msg at shutdown!
Date: 26 Dec 1992 03:19:30 -0600
Organization: Kansas State University
NNTP-Posting-Host: matt.ksu.ksu.edu

danubius@halcyon.com (Joseph R. Pannon) writes:

>Could somebody explain why I am getting this as the last message in a
>shutdown sequence?

>"Cannot exec /etc/umount, trying umount."

>Thanks,
>Joe Pannon

Probably because umount is in /bin not /etc. I just moved mine to /etc when
it belongs and no problems.

James
From: dsc3pzp@nmrdc1.nmrdc.nnmc.navy.mil (Philip Perucci)
Newsgroups: comp.os.linux
Subject: Re: My own bootdisk?
Date: 29 Dec 92 01:56:18 GMT
Organization: Naval Medical Research & Development Command

In article <Bzztur.HJ8@nmrdc1.nmrdc.nnmc.navy.mil> dsc3pzp@nmrdc1.nmrdc.nnmc.navy.mil (Philip Perucci) writes:
>I tried with LILO 0.7 as specified in README for GCC rootdisk, it dies
>with "init: exec rc failed".  Yes I have /etc/rc on floppy.  777 type,
>even (chmod 777 /mnt/etc/rc).  Two things look funny:
>
>  1) With other bootdisks I have seen (GCC & SLS), I don't see LILO message.

OOPS! Brain damage here!  GCC rootdisk (bootable) DOES use LILO!
My mistake.  But still - When I boot from floppy w/0.99pl1 & LILO 0.7
WHY do I get prompted for root disk in /dev/fd0???



-- 
===========================================================================
  phil perucci      | "Any opinions expressed are solely my own views and 
  ssb1pzp@digex.com |  do not reflect the position of any organization"
===========================================================================
Newsgroups: comp.os.linux
From: loser@clueless.newbie.tyro.org ()
Subject: Re: compiling xview prog
Organization: Workstations at Maryland, University of Maryland, College Park
X-Newsreader: TIN [version 1.1 PL6]
Date: Tue, 22 Dec 1992 14:10:49 GMT

You need to also link the RPC libraries.  If you don't have them, you can
get them from tsx-11.mit.edu.  I believe they are located in the NFS
directory.  That should do it.

Jaime

Newsgroups: comp.os.linux
From: marcf@nexus.yorku.ca (Marc G Fournier)
Subject: Re: known problem with email...buy why?
Organization: York University
Date: Thu, 31 Dec 1992 21:56:11 GMT

pmacdona@sanjuan (Peter MacDonald) writes:

>Here is a shot in the dark:  doesn't a process have to be running as 
>root to use "chown"?  Elm is sgid mail.

	I just tested your shot in the dark, except that it isn't elm
that creates the mailbox, it is smail...so I chown'd smail so that
it had the suid set...still owned by the user who sent it :(

	I just tried suid'ing elm also...that still doesn't allow you
to read the folder.  

	This is most curious :(  as was stated, the 'mail' command reads it
without a problem (even though the user doesn't own themailbox), but
elm doesn't...with same permissions.

	Question: Does anyone have this running successfully?  Straight
off the SLS distribution, without recompilng anything?

Marc
Newsgroups: comp.os.linux
From: ramesh@utdallas.edu (R. Ramesh)
Subject: Re: BSD lpr/lpd and serial lw - help help help
Organization: Univ. of Texas at Dallas
Date: Mon, 28 Dec 1992 22:36:19 GMT

In article <1992Dec28.182111.1772@sol.UVic.CA> pmacdona@sanjuan (Peter MacDonald) writes:
>In article <1992Dec28.170337.7582@dartvax.dartmouth.edu> jgrape@coos.dartmouth.edu (Johan A. Grape) writes:
>>Well, this thread seemed to die....  I still can't get the
>>daemon to print anything.
>>
>
>The next release of SLS will have lpr setup.  But the released
>lpr doesn't work with the libc.4.2 (because of the stupid
>net code being moved).   So if you are using it the daemon 
>won't run.
>

Really? I did not know that. May be about 20 messages could have been avoided
had this been made public earlier. Or, was it made public and I missed?
Any way thanks Peter. I will try with bash and libc.so.4.1.

Ramesh


Newsgroups: comp.os.linux
From: sno@ais.org (Stephen Opal)
Subject: Can't get my scsi acknowledged.
Organization: UMCC
Date: Thu, 24 Dec 1992 14:27:36 GMT

I'm hobbling through preliminary set up stages but am stuck on not
being able to install on my scsi HD device.

I have the a? distribution available to me, but not enough "space" to
make patches or sysinstall -install, because I'm stuck in the floppy
environment.

My preliminary attempts to first set a /dev link to my device has met
with failure.  I have an Adaptech 1742a (SCSI device 7) connected to a CDC 
Wren IV 350 (SCSI device 0).  Dos acknowledges the drive and I have Dos 
booting from it.  Nothing important will be lost from the Dos partition 
if I screw up.

However,
# mkdir /scsi
# mount /dev/sda /scsi
mount: permission denied

# mount /dev/sda7 /scsi
mount: permission denied


-- 
Stephen N. Opal     sno@umcc.ais.org