HDTenEightyP/NetNews huggingface dataset:
From: messina@netcom.com (Tony Porczyk)
Subject: Re: LINUX, Unix, and opportunity for change
Organization: Messina Software
Date: Sun, 27 Dec 1992 23:24:50 GMT

goer@ellis.uchicago.edu (Richard L. Goerwitz) writes:

>mleech@bnr.ca (Marcus Leech) writes:
>>
>>Were it not for the fact that I have a job where everything I create is
>>  owned by my employer, I'd be as busy as Linus; contributing, rather
>>  than just pontificating.  [Though it's certainly not unheard-of around
>>  here to be able to release freeware, just rather rare].

>Did you actually sign a contract that gives them rights to code you cut
>at home during off hours?  If so, I'm quite amazed.  Perhaps I'm just
>naive, but this sounds like a form of slavery.  I hope they pay you a
>king's ransom.

That is actually a common practice in many companies.  Of course, you may
argue that court might not uphold such broad definition.  Nevertheless,
I have seen it in contracts (and have singed at least one).

t.
Newsgroups: comp.os.linux
From: ckurs-2@wilbur.uni-mainz.de (Teilnehmer am C-Kurs WS 1992_93)
Subject: Re: [BUG REPORT]
Keywords: 0.99pl1 kernel keyboard linus
Organization: Johannes Gutenberg Universitaet Mainz
Date: Tue, 29 Dec 1992 14:38:48 GMT

Yes it is DEAD !!! (*SNIFF*)
I digged for some old utilites concerning whether your kbd is really mf2 and
so on ...
So what i'm going to do is:

1. Check my keyboard real hard !!!

2. If my keyboard is ok, then i'll rewrite the keyboard driver from scratch!

Hope this will end misery for me ...

Dominik

+-----------------------------------------------------------------------------+
| eMail to:      kubla@MZDMZA.ZDV.UNI-MAINZ.DE                                |
| sMail to:      Dominik Kubla, Steinsberg 34, 5428 Nastaetten, GERMANY       |
+-----------------------------------------------------------------------------+
|                                                                             |
|                     I don't  *like*  LINUX, I  *LOVE*  it ...               |
|                                                                             |
+-----------------------------------------------------------------------------+
Newsgroups: comp.os.linux
From: jasona@softwords.bc.ca (Jason Anderson)
Subject: Re: A discipline for packages
Followup-To: jasona@softwords.bc.ca
Organization: Softwords
Date: Thu, 31 Dec 92 21:32:44 GMT


This would be good thing, I agree.

Myself, I find myself following the Linux versions, upgrading
along with SLS each time, having to make sure I don't
lose packages that I have installed in addition to SLS.

Typically I don't like to place anything that is not in the
standard SLS release in the root directories (/usr, /lib etc), but
rather create symlinks to another "more static" spot on my 
system.

This allows me to upgrade without fear of losing something I have
ported/ftp'd etc. when I upgrade each time.

Generally this is a hassle because most packages "assume" where
they will be placed.  Some are friendly and create symlinks for
you ;-)


Jason
From: dsc3pzp@nmrdc1.nmrdc.nnmc.navy.mil (Philip Perucci)
Newsgroups: comp.os.linux
Subject: Re: Question and Observations
Date: 29 Dec 92 20:28:27 GMT
Organization: Naval Medical Research & Development Command

In article <1992Dec29.165604.17462@athena.mit.edu> whit@Tymnet.COM (Kendall Whitlatch) writes:
>pmacdona@sanjuan (Peter MacDonald) writes:
>|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
>
>Peter takes a pretty good beating here on C.O.L. every time any minor
>flaw in the package is found.  I think he needs a little applause for
>even attempting the task in the first place.
>
>Thanks again.
>

Amen!

-- 
===========================================================================
  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: david@prism.demon.co.uk (David Metcalfe)
Subject: Re: ANSWER: lpr on SLS
Reply-To: david@prism.demon.co.uk
Distribution: world
X-Mailer: cppnews $Revision: 1.20 $
Organization: ** none **
Date: Mon, 21 Dec 1992 20:38:24 +0000

In article <1gnei8INNqfi@rifraf.atl.ge.com> wmitchell@atl.ge.com writes:
> As suggested by someone in a recent post, to help reduce the traffic
> on this newsgroup, here is a summary of the responses to my query about
> getting lpr to work.
> 
> For me (I'm running SLS 0.98pl1) the following 5 steps do it:
> 
> 1) obtain lpr.tar.Z from sunsite.unc.edu:/pub/Linux/system/Daemons/lpr.tar.Z
> 
> 2) logged in as root and in the directory /, type
> tar -xZf lpr.tar.Z
> 
> 3) edit /etc/rc to add the line "/usr/etc/lpd" at the end
> 
> 4) chmod og+w /usr/spool/lp1 (I don't know if this is necessary,
> but it can't hurt)
> 
> 5) edit /etc/printcap to change line 1 from
> lp|panasonic:lp=/dev/lp1:sd=/usr/spool/lp/panasonic:lf=/usr/bin/mail:mc#1:\
> to
> lp:lp=/dev/lp1:sd=/usr/spool/lp1:mc#1:\
>
< rest deleted >

Well I tried the above and I still can't get lpd to remain resident.
However, whenever I run lpd it does print anything that happens to be
in the print queue and then promptly kills itself again.

Any ideas anyone.  This is with 0.99 BTW.

David

-----------------------------------------------------
David Metcalfe          david@prism.demon.co.uk
London, England         dmetcalf@cix.compulink.co.uk
     
                       
            
Newsgroups: comp.os.linux
From: rwebb@nyx.cs.du.edu (Russell Webb)
Subject: New Linux User: SLS 0.99 SCSI timeouts on mkfs
Organization: Nyx, Public Access Unix @ U. of Denver Math/CS dept.
Date: Thu, 24 Dec 92 07:42:57 GMT

I'm a rather new Linux user myself, but I'm posting this for a local
BBS user who I urged to try Linux.  I suppose he's using SLS v0.99
with the line patch (?) because he grabbed SLS from tsx-11 around 3 days 
ago.  He's getting SCSI timeouts when he gets the point of trying to
mkfs during the SLS installation procedure.  I don't know what to tell
him since I'm using an IDE drive and SLS 0.98pl4.

I emphasize in what now seems to be classic comp.os.linux fashion:
Please respond to steven.osman@factory.com.
Please respond to steven.osman@factory.com.
Please respond to steven.osman@factory.com.

-Russell
rwebb@nyx.cs.du.edu
---

I have a Vega 3-486DSX motherboard in 386-40 configuration, with 8 megs
of RAM, and 64 K cache.
I have a Future Domain TMC-1680 SCSI controller (with only two floppy
drives installed) set up with BIOS at c8000, I/O address 140 and IRQ 14.
I have two CDC 94171-9 drives installed revision 885.  (Actually,
are Seagate's now)... and a Wangtek tape drive.

First drive is sd0 at scsi1, lun 0, id 0
second is sd1 at scsi1, lun 0, id 1, and
tape drive is st0 at scsi1, lun 0, id 4.

I've tried the system on a minimal configuration with only my
motherboard, drive controller, and a Diamond Stealth VRAM installed.
fdisk works properly, creates partitions ok on /dev/sda.  My Linux
partition is currently /dev/sda1, and on bootup, the system reads the
partitions ok.
When I try to use mkfs, it SEEMS to work, returns me to the prompt, and
shortly (1 second or so) later, I get the message "SCSI host 1 timed
out - aborting command".

A second or two later, it fills with error messages like this (five
lines each) :

        SCSI host 1 timed out - aborting command
        SCSI disk error : host 1 id 0 lun 0 return code = f030000
        scsidisk I/O error
        dev 0801, sector 332
        SCSI host 1 timed out - aborting command

The sector number varies, but is always even (i.e., 332, 334, then 336,
etc...) I'm not sure which number it starts at, because it scrolls
fast.

I'd appreciate it if you could get me some help... I can't wait to get
this up and running!

Thanks in advance.

Steven
steven.osman@factory.com
From: tfoley@camaro (Tim Foley)
Newsgroups: comp.os.linux
Subject: List of Broken Binaries for 0.99 [v1.1]
Date: 21 Dec 92 17:54:30 GMT
Organization: camaro


 
Below is an un-official list of programs which break under 0.99 (or 0.98.6)
and the method to get them running again.  I felt there was a great need
for such a thing.

Any Changes/Suggestions/Fixes, tfoley@camaro.uucp or whome!camaro!tfoley@uucp


     NOTE: ENSURE YOU GET THE NEW LIBC 4.2 FILE FROM YOUR LOCAL SITE

Revision	1.1
Date		12/21/92 5:43pm

-Added minicom correction/makefile had different install dir/my fault ;)
-Added sed problems
-Updated rz/sz / tested...works


NAME	STATUS	FIXED	METHOD OF REPAIR 
---------------------------------------------------------------------------  
ps	Broke	Yes	-recompiled the ps-0.97.6.tar source
			-ps -U after installing the new ps in /usr/bin
elm	Ok?	Yes	-Appears to work ok
trn	Ok?	Yes	-Appears to work ok (needs new sed for inews to post)
emacs	Ok?	Yes	-Appears to work ok
uucp	Broke	Yes	-recompiled the Taylor 1.03 with the -fwritable-strings in
		 	the makefile in addition to all other cflags and
		 	added the new libc.so.4.2 (MUST HAVE!)
minicom	Broke	Yes	-Apply mini98.5.tar patch
			-Check Config.h install dir though, it changed
rz/sz	Ok?	Yes	-Appears to work ok (tested from minicom)
sed	Broke?	Yes	-Did not behave reliably, version GNU 1.09
			-Get GNU 1.13, added -dHAVE_BCOPY and removed def in
			sed.c for sys_errlist as its in errno.h
			-now works properly, fixes INEWS problem
cnews	Broke	Yes	-Inews shell script keeps dumping in dead.article
			-Due to SED not fully working
mail	Broke	Yes	-Recompiled the mailpak-1.3 mail, with -fwritable-strings in
		 	the makefile, remember to re-link rmail as well
getty	Broke	Yes	-Recompiled the 2.04 (Not 2.03) sources
			-No longer likes terminals?  Had to use uugetty for
			my vt220
uugetty Broke	Yes	-Recompiled the 2.04 (Not 2.03) sources
man	Stat()	Yes	-Recompiled 1.1 sources


 The new lib, libc.so.4.2 seems to solve many a problem actually.



-- 
  --------------------------------------------------------------------------
               The HeartBeat of America...Yesterdays Camaro Z28 
                             tfoley@camaro.uucp   
     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: vince@victrola.sea.wa.us (Vince Skahan)
Subject: Re: help: SLS FDISK with two hard disks
Keywords: SLS, FDISK
Organization: Vince and Suzie's Underpowered PC
Date: Thu, 31 Dec 1992 14:01:13 GMT

shong@magnus.acs.ohio-state.edu (Sang-ki Hong) writes:
>I have two hard disks (340Mb each).  The first disk (C:) is partitioned as
>primary DOS for all 340Mb.  The second drive (D:) has 340Mb DOS extended
>patition.

>I'd like to use the first drive only for DOS, and the second only for linux.
>The FDISK in SLS doesn't seem to provide a way to do this kind of setup. If 


when you boot, you'll see which disk(s) linux sees as part of the boot process.
you'll see /dev/hda* for the first disk and /dev/hdb* for the second.

then when you run fdisk in SLS, you have to say 'fdisk /dev/hdb1' to get the
second disk.

IMPORTANT: you have to be sure that you get the right disk or you'll nuke the 
DOS one by mistake.  When you run fdisk, pay attention to the 'type' of each
disk so that you get the extended one (d:) and not the primary one (c:).

-- 
     ---------- Vince Skahan --------- vince@victrola.sea.wa.us ----------
	Heineken uncertainty principle: you can never be sure how many
		beers you had last night.
From: denouden@cs.utwente.nl (Jan den Ouden)
Newsgroups: comp.os.linux
Subject: named files
Keywords: named nameserver
Date: 26 Dec 92 23:51:05 GMT
Organization: University of Twente, Dept. of Computer Science

I've spent Christmas trying to install the TCP/IP package for
my ethernet network (Artisoft AE2 cards, btw). Ftp and telnet
work without problems, but I can't get a nameserver up.

Could somebody tell me the contents of the files needed for
the named daemon for a 2-node isolated network? The tcpip
README and FAQ files and hostcvt man pages are unclear at
points.

I haven't been able to get NFS working, but I suppose (??)
that the nfsd daemon relies on a working nameserver, so I'll
first try to fix the named problems.
 
Newsgroups: comp.os.linux
From: enewton@uucp (Eric C. Newton)
Subject: compiling trashes a partition
Reply-To: uunet.uu.net!srg!enewton
Organization: The World
Distribution: comp
Date: 30 Dec 92 08:34:25


Here's a story:

  I tried to compile xfishtank.  I worked on the #ifdefs and built an
  executable.  It failed to work.  No biggie, do a stack trace on the
  core file, edit the sources and recompile.

Here's the problem:

  I do this work on partition 1 (type minux).  This trashes partition
  2 (type minux).  TRASHED beyond repair. fsck tells me the magic
  numbers are incorrect.  I have not changed anything on the second
  partition since the last boot.

I have repeated the problem.  Anybody have any ideas?  I have verified
that the partitions do not overlap (if that's even possible).  The
filesystem was not full, and I don't think that any directory
contained more than 128 files.

This is with linux-0.99.1, -msdos -scsi +selection-patches.  I use the
extended filesystem on a second drive.

Backups are a wonderful thing to have.

-Eric
Remember to mail to: 	uunet.uu.net!srg!enewton    "The more you complain,
<or>			enewton@oswego.oswego.edu    the longer God lets you
<or>			enewton@access.digex.com     live."



--
Remember to mail to: 	uunet.uu.net!srg!enewton    "The more you complain,
<or>			enewton@oswego.oswego.edu    the longer God lets you
<or>			enewton@access.digex.com     live."
Newsgroups: comp.os.linux
From: qualtrak@netcom.com (Qual Trak)
Subject: Re: X and Orchid Fahrenheit 1280
Organization: QualTrak Corporation
Date: Fri, 1 Jan 1993 04:08:16 GMT

In article <9301010226.AA05468@hrt216.brooks.af.mil> Sten M. Drescher <smd@hrt216.brooks.af.mil> writes:
...
> Jonathan> if you want to avoid going trans-atlantic (and live on my
> Jonathan> side. :) ) we mirror robots on a daily basis. check on
> Jonathan> sunsite.unc.edu in /pub/X11/X-servers.
>
>	Sorry.  I was just on sunsite, and no such directory existed.
>Now, /pub/linux/X11/X-servers, yes.  It wouldn't even be worth
>mentioning, except that there IS a /pub/X11 directory.
>		Sten
Try
 pub/Linux/X11/X-servers/s3
-----                                                              -----
John Birchfield - QualTrak Corp (408) 730-2674 Home (408) 736-3852
jb@QualTrak.COM
-----                                                              -----
Newsgroups: comp.os.linux
From: dhliu@solar.csie.ntu.edu.tw (Der-Hua Liu)
Subject: Linux on Local Bus IDE (with Cache)
Organization: NTUTaiwan
X-Newsreader: TIN [version 1.1 PL8]
Date: Wed, 23 Dec 1992 03:07:17 GMT


   Local bus IDE with 2MB RAM Cache,    (GA-??? board, from Taiwan)
   Local bus 486/50 mother board        (also GA-???, SiS chipset)

Have anyone install Linux 0.99 on such IDE card ?

Thanks.

D.H. Liu

dhliu@solar.csie.ntu.edu.tw
Newsgroups: comp.os.linux
From: a080700@hp9000.csc.cuhk.hk (Stephen Wong S M)
Subject: Re: 0.99.2 compile prob #2
Keywords: 0.99.2 compile problem
Organization: The Chinese University of Hong Kong
Date: Sat, 2 Jan 1993 18:13:31 GMT

In article <C08L0n.3oE@nmrdc1.nmrdc.nnmc.navy.mil> dsc3pzp@nmrdc1.nmrdc.nnmc.navy.mil (Philip Perucci) writes:
>In article <1993Jan2.135609.25278@hp9000.csc.cuhk.hk> a080700@hp9000.csc.cuhk.hk (Stephen Wong S M) writes:
>>Copy linux/include/asm/* to /usr/include/asm and linux/include/linux/* to
>>/usr/include/linux.
>
>I believe:
>
>  ln -s /usr/src/linux/include/linux /usr/include/linux
>  ln -s /usr/src/linux/include/asm   /usr/include/asm
>
>is the preferred method.
 
Okay, no matter soft link or actual copy, the .99p2 cannot be compiled.
I've grep all files from the patch kit and patched files, I CANNOT find
definition for KEYBOARD_BH, and that's why the make process cannot be
completed.

*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*
v Stephen Wong Siu-ming       v internet: stephenwong@cuhk.hk        v
^ Computer Services Center    ^ bitnet  : a080700@cucsc.bitnet       ^
* Chinese University of       * phone   : (852) 609-8904             *
v Hong Kong                   v fax     : (852) 603-5001             v
*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*
Newsgroups: comp.os.linux
From: spierce@wam.umd.edu (Stephen Pierce)
Subject: Linux Questions
Keywords: linux dosemu mud NFS 
Organization: University of Maryland, College Park
Date: Tue, 22 Dec 1992 18:07:44 GMT

  I've just completed installation of SLS linux .98p5. I just have a
few questions:

  1) I logged in over the network, and accedently killed the machine. It
didn't reset, so I had to walk over to the machine and hit reset. Is there
a way to setup the machine so it reboots (and syncs) if there's a major
system-wide problem?

  2) When I log in at the console, and then telnet into the machine, it
works great. Now if i telnet in from the modem annex system, i have to
use ctrl-j instead of return. Why is this? Can i fix it? BTW: This is only
for the login and password, all other prompts use return correctly. Also,
the FTP client and su use this ctrl-J..

  3) When I try to use login it tells me i have to be in the bottom most
sh shell. But i am!?

  4) I noticed that the filenames are restricted in length. Anyway to change
this?
  
  5) Is the NFS system stable enough to run constantly? I want to setup
the PC as a file server with NFS mounts on other (MS-DOS) PC's.

   These are just the few nit-picking problems that I've found. Linux
works great on my system. Now maybe I'll get some Real Work done on it..

Steve
From: kf8nh@kf8nh.wariat.org (Brandon S. Allbery)
Newsgroups: comp.os.linux
Subject: WEIRD ATI video problem with X386
Date: Sun, 03 Jan 93 00:12:26 EST
Distribution: world
Organization: Brandon S. Allbery's Personal System

This one isn't the usual problem, if I've been reading the posts I've seen
so far correctly.  This is an ATI Graphics Vantage.

X386mono works.  (Well, it would work if I ever get the kernel to recognize
my bus mouse.  See my earlier posts.)  The color server I configured to come
up in 640x480 mode just to test it out, using the example ATI Xconfig from
ftp.cs.unc.edu.  It does have a small sync problem for some reason, but I
can fiddle with that later; there's something more serious wrong.

The problem is that only about 1/4 of the screen is correct.  If you divide
the display up into a bunch of small blocks (roughly character-sized, were
it a text mode screen) the top-left quarter of the block is correct; the
top-right quarter is solid white and the bottom half is black.  Worse, when
I exit X (ctrl-alt-backspace) the screen switches back to text mode but only
the top half of each character displays and spaces come out as at signs,
with similar mutilations to other characters.  If I didn't know better, I'd
say something was imposing a bitmask on displayed characters once I enter X,
and doesn't stop after it exits.  Using vgalib to reset the screen to text
mode manually doesn't fix the problem.  I tried it both with and without
cacheing enabled on my motherboard.

The "proper" fix is to install the X8514 server :-) but downloading Xfree86
1.1 will take me a while (I have to (ab)use my Internet privileges on Delphi
and then download it over their X.25 link... call it 470 cps using zmodem.)

HELP!  I'm confused (as usual...)

++Brandon

He's BAAAACK! Brandon S. Allbery     NOTE NEW ADDRESS!!! kf8nh@kf8nh.wariat.org

Newsgroups: comp.os.linux
From: amir@avalon.physik.unizh.ch (Guindehi Amir)
Subject: HELP : bad magic number in super-block
Organization: University of Zurich, Department of Computer Science
X-Newsreader: Tin 1.1 PL4
Date: Wed, 30 Dec 1992 20:49:11 GMT

HI everybody !

I'm standing under shock. I use my Linux since 4 weeks now, have upgraded
on Kernel .99p1 from SLS .98p5 and all worked fine.

Then, I had the idea to try : shutdown -r now.

After that, my machine booted and suddenly a saw this :

..
Partition table ok.
MINIX-fs: magic match failed         <-- NEW, I don't know why ! Didn't 
EXT-fs: magic match failed           <-- touch /etc/fstab or something.
[MS-DOS ... ]			     <----- comes from my mounted DOS-Part.
[me=.... ]
Unsuported FS parameters             <-- It seems that he does'nt re- 
Kernel panic: Unable to mount root       kognize the root - fs !

Found answers :
---------------

Booting with my rawrited bootdisks from the installation I saw that I
can mount my /usr partition but not my root-partition !

Making an fsck /dev/sda8 (where my / resides) prints this :

fsck : bad magic number in super-block

Questions :
-----------

- How can I fix this ?? I don;t want to reinstall Linux because of the
  /home etc. directorys on the root-partition and second I don't know
  how to install only / and not /usr.

- What have I done wrong ?? I don't know. I logget out of Xwindows. Changed
  to VT-1 where I was logged on as root, and typed : shutdown -r now.


Please help me ! I feel so bad without Linux.

Thanks,
Amir Guindehi

EMail : amir@avalon.physik.unizh.ch
        aguindeh@iiic.ethz.ch



Newsgroups: comp.os.linux
From: marcf@nexus.yorku.ca (Marc G Fournier)
Subject: Re: A discipline for packages
Organization: York University
Date: Wed, 30 Dec 1992 05:12:26 GMT

nelson@crynwr.com (Russell Nelson) writes:

>You know something I've always hated about Unix (and people are
>starting to hate about Windows)?

>When you install a package, it inserts itself inextricably into
>various places in your system.

>What I would rather see is a subdirectory per package.  For example,
>/package/sendmail (and the corresponding subdirectories lib, src, cf,
>man.1, man.5, man.8, bin, etc).

	So?  Install DOS

>This seems a lot cleaner than every program in the world inserting
>itself into /etc, /usr/lib/, /usr/bin, /usr/man,
>/usr/local/lib/package, etc.  Of course, you'd still need to have
>these things inserted into the standard places, so that it still
>looked like a Unix machine.  But this could be done through the use
>of symbolic links and a program that automatically created them.  It
>would walk through /package/*/bin for things to put into /usr/bin,
>/package/*/man* for things to put into /usr/man/man*, /package/*/etc
>for things to put into /etc.

	Geez...that would make one messy file system...everything
symlinked to everything else.

>Then, when you wanted to remove a package, you'd just rm -r
>/package/name, then re-run the symlinks builder.

	Most Unix Operating Systems I've used have both an install
and an uninstall command that does the same as rm -r would do
to a /package/name directory

>Of course, chasing down all these symlinks is going to make your
>system less efficient.  But that's solvable by creating cache files,
>and gradually improving programs so that they look in the cache files
>instead of at the symlinks.  Of course, the cache files get
>automatically built also.

	I think this guy is warped by DOS :(  

>And, of course, the symlinks builder could also be told to look in
>places other than /package.

>Why don't I just go off and do this myself?  Well, because the chief
>benefit comes from easy package installation/removal.  These benefits
>don't come unless people *do* it.

	I don't see a benefit to this at all.  On top of the inefficiency
of it all...you would be wasting a hell of a lot of i-nodes doing this
as well (among probably a hundred other things)

Marc