HDTenEightyP/NetNews huggingface dataset:
From: jwinstea@fenris.claremont.edu (Jim Winstead Jr.)
Subject: Re: Official version?
Organization: Harvey Mudd College, WIBSTR
Date: Thu, 1 Oct 1992 07:19:57 GMT

In article <1992Sep30.144248.11602@cc.tut.fi> jk87377@cc.tut.fi (Juhana Kouhia) writes:
>
>In article <1992Sep29.183716.15204@muddcs.claremont.edu>
>jwinstea@fenris.claremont.edu (Jim Winstead Jr.) writes:
>>
>>There might be an official 'Linux 1.0' with all sorts of goodies and a
>>sane distribution, and there might not.  People are trying to organize
>>things, but it is a giant undertaking.
>
>Flame war on /usr/local is not organizing.

I never said it was.  Please do not try and put words in my mouth.

>So, is the official directory structure decided yet?

No.

>Can we have the results of standardizing group (which now is
>non-active)?

Sure, browse through pub/Linux/linux-standards on sunsite.unc.edu to
follow the discussions on the Standards and see how things were left.
Michael Johnson has posted his directory.7, which describes the
directory standard.  For a look at the 'device standard', my
/dev/MAKEDEV is consistent with the MCC release and the 'official'
root/boot disk combination, so it could be considered a de facto
standard.

>What they made?
>Did they just waste time?

For the most part, not much got accomplished.  The final decisions
still eventually lay with the people who put together the
distributions.
-- 
                                    +      Jim Winstead Jr. (CSci '95)
                                    |      Harvey Mudd College, WIBSTR
                                    |   jwinstea@jarthur.Claremont.EDU
                                    + or jwinstea@fenris.Claremont.EDU
From: mirons@ccs.northeastern.edu (Michael A. Irons)
Newsgroups: comp.os.linux
Subject: Re: Linux 0.97 PL 6 detecting bogus bus mice
Summary: There's still problems
Date: 30 Sep 92 21:38:49 GMT
Organization: Northeastern University, CCS Dept.


	I applied this patch to 0.97.6 and it went in fine. My system does
now detect my PS/2 mouse, and the tst/mouse/mouse program that came w/ X11
doest something with it (the prog can't speak PS/2, but it does get input)
HOWEVER, after that my keyboard dies and IHAVE to power cycle the machine.
As such I put in a jmp no_psmouse at the start of the code in setup.S to
deactivate my mouse. It seems that there is a bug somewhere else.

	I have:
	Packard Bell 486-33
	Packard Bell PS/2 mouse

   I spent about a week verifying with them that the mouse conforms to the IBM
PS/2 mouse spec. They said 'it even uses the same controller as the keyboard,
just like the IBM's do.' so that may be the problem in itself.

					Mike Irons;

	PS - Thanks for the patch. Atleast that part works now :}


-- 

                                  Mike Irons;
                       mirons@Dworkin.CCS.Northeastern.EDU	(School)
                 mirons%minix1.uucp@MecEng.COE.Northeastern.EDU	(Home)
From: hellers@cs.wisc.edu (Joe Hellerstein)
Newsgroups: comp.os.linux
Subject: combo MS/Mouse-Systems mouse
Date: 30 Sep 92 17:09:08 GMT
Distribution: comp
Organization: Univ. of Wisconsin @ Madison, CS Dept.

I recently got a 486 box from HD systems, and it came with a no-name
serial mouse (well, it says "HD" on it, but I don't know who makes
it).  Under DOS, the mouse is configurable to work either as a
Microsoft mouse or a Mouse Systems mouse -- by default, it's a
Microsoft, but if you hold a button down during power-up, it acts
likes a Mouse Systems mouse.

I'd like to use it as a Mouse Systems mouse under linux, because (at
least under DOS) in Mouse Systems mode all three of its buttons work,
while in Microsoft mode the middle button is useless.  However under
linux/X11 it always appears to be a Microsoft mouse, even when I hold
a button down during bootup.  Any suggestions?  I'm running linux
.97pl1, with the older version of X11 (is it v1.1?  I don't have my
machine here...)

Joe Hellerstein
From: troyer@saifr00.cfsat.honeywell.com (Dean Troyer)
Subject: Re: PS/2 pointing device initialization patch
Organization: Honeywell Air Transport Systems Division
Date: Tue, 6 Oct 92 15:29:53 GMT

In article <1992Oct6.011653.19143@wam.umd.edu> joel@wam.umd.edu (Joel M. Hoffman) writes:
>I think we might have a copyright problem if we start using code
>obtained from disassembling a BIOS.  I know that the original BIOS
>clones were made by two groups of people, one that saw what the code
>did, and the other that did the re-coding, specificially to avoid
>copyright infringement.  (Yes, it sounds like a foolish way for adults
>to spend their time, but that's not the issue....)

I may just be picking nits here, but the patch included NO code obtained
from the BIOS disassembly.  It did include a replication of the data
written to the mouse ports.

>I don't want to start a lengthy discussion of this here.  I would
>suggest that someone in charge decide:  Do we use code obtained from
>disassembling other code?
>
>-Joel

I believe a recent court decision has cleared this issue somewhat, but
until I have some authoritative references, I'll not say more about that.
Any one else know?

dt

-- 
Dean Troyer                               troyer@saifr00.cfsat.Honeywell.COM
Honeywell Commercial Flight Systems       72240.3152@compuserve.com
Phoenix AZ
(602) 436-3613
Newsgroups: comp.os.linux
From: drew@kinglear.cs.colorado.edu (Drew Eckhardt)
Subject: Re: SCSI Controller Recommendations?
Keywords: SCSI, tape.
Organization: University of Colorado at Boulder
Date: Tue, 6 Oct 1992 02:32:23 GMT

In article <1992Oct5.212555.7897@afterlife.ncsc.mil> swaliff@afterlife.ncsc.mil (Steve Aliff) writes:
>
>I'm purchasing a Wangtek 5150ES tape drive in hopes of making it
>work with Linux (It's the one from comp.unix.bsd/
>misc.forsale.computers if anyone really cares). I don't have a SCSI
>controller yet and am looking for recommendations.  I know this
>drive will work with the Adaptec 1542B under 386BSD. So if need be,
>that looks like a good combination to try to make fly under Linux.
>However, I'd really like something cheaper for the moment. I don't
>suppose by some miracle the ST-01 works with tapes?  (the cheapest
>SCSI controller card I know of)
>

The way the Linux SCSI drivers are set up, any highlevel driver 
should work with any low level driver.  So, the CD and disk drivers
work with the Seagate, Adaptec, Ultrastor, etc.

Tapes aren't supported yet for anything, but when they are, the situation   
should be the same.

Note that the assembly code that does the actual data transfer in the 
Seagate driver maxes out at ~500k/sec - so you will have problems streaming
a SCSI tape from a SCSI disk on the same bus.

-- 
Microsoft is responsible for propogating the evils it calls DOS and Windows, 
IBM for AIX (appropriately called Aches by those having to administer it), but 
marketing's sins don't come close to those of legal departments.
Boycott AT&T for their absurd anti-BSDI lawsuit.
Newsgroups: comp.os.linux
From: heim@peanuts.informatik.uni-tuebingen.de (Gerald Heim)
Subject: Re: Okay, another CLISP problem (fatal!)
Organization: organisiert? ich? ach was!
Date: 30 Sep 92 16:12:48


Hi

I have exactly the same problem. I linked my version of CLISP with gcc222d
and jumptables 4.1 using the old setjmp.s source posted here recently.
Maybe that's it. If I have time I will try to link it with gcc222 and see
what happens...

gjh

[dunno exactly, but I think I was using load-file instead of load when I got
 this error]
From: rcskb@minyos.xx.rmit.oz.au (Kendall Bennett)
Newsgroups: comp.os.linux
Subject: Re: Gnu hardware
Date: 28 Sep 92 04:56:10 GMT
Organization: RMIT Computer Centre
NNTP-Posting-Host: minyos.xx.rmit.oz.au

dmiller@beta.tricity.wsu.edu (David L. Miller) writes:

>I have been seeing some interesting ideas floating about on this thread.

>I may have time to do some design work on this hardware after the first of 
>the year.  What I would like to see before I start though is some coordination
>and detailed specifications.  If there seems to be a consensus by the time
>I get started, I will probably design to it.

Ok, now we are getting down to the nuts and bolts of the issue. We have
decided that this might be a _good idea_, so the next step is to work out
how to do it. I have some background in hardware, but only enough to 
possibly understand the design :-) My area is software, especially graphics
programming (I have done a lot of low level programming for the PC
graphics adapters), so I am very interested in the software specification
for this device.

Some people have been saying that it will cost too much to produce, and
you may as well go and buy a card for US$200 instead. Well personally
I believe that this is possible. If we have enough people interested in
the project, we could scrape together enough money to design and build
a prototype (probably the most expensive part of the process). Once this
is done it could be bulk produced and would be a lot cheaper.

The thing is, if _we_ the users do this, we will be building the card
at cost price - there will be no middle man between the manufacturer and
the user. Alternatively it could be made available in kit form, but if
the device is going to be good enough, a kit will probably be too hard
to assembler (ever tried soldering surface mount resistors and caps?).

We ned to fighure out how all of this will be coordinated? Maybe a mailing
list should be set up for the purpose? In order to solicit more interest,
maybe a proposal should be cross-posted to a number of other groups on the
net?

Anyway, this sound like great idea to me, so count me in...

+------------------------------------------+-------------------------------+
| Kendall Bennett                          | Internet:                     |
| RMIT Advanced Computer Graphics Centre   | kjb@citri.edu.au              |
| CITRI Building, 723 Swanston Street      | rcskb@minyos.xx.rmit.oz.au    |
| Carlton Victoria 3053 AUSTRALIA.         |                               | 
+------------------------------------------+-------------------------------+
| CoSysop (Bossman), PC Connection Australia:               +61 3 688 0909 |
+--------------------------------------------------------------------------+
From: ton@blade.stack.urc.tue.nl (Ton van Rosmalen)
Newsgroups: comp.os.linux
Subject: Re: Summary of: What tape drives work with Linux
Date: 28 Sep 92 12:29:59 GMT
Organization: MCGV Stack, Eindhoven University of Technology, the Netherlands.
X-Newsreader: TIN [version 1.1 PL6]

Petri Juhani Riipinen (riipinen@dxcern.cern.ch) wrote:
: Summary of answers to question: What Tape Drives work with Linux?
: 
:  - There is a working QIC-02 device driver for Linux
:    - It supports (at least) Everex/Wangtek cards
: 
:  - There are additional patches for the QIC-02 driver
:    - They make the driver support Archive SC402/499R
: 
:  - The driver can be found from: tsx-11.mit.edu:/pub/linux/alpha/qic-02
: 
:  - There are some bugs in the driver, but you can make backups with it.
: 
:  [stuff deleted concerning scsi/floppydisk tape-streamers]

I would like to know how to get a hold of the patches for the archive
controller. I have been working in them myself but I'm not satisfied
with it just yet. So I'd like to have look at the patches of someone
else.

The author has a *few* remarks about a kernel usleep(). I think there is
such a function in the kernel now. And is work being done to solve the
timing problems which it still has ? If not I hereby volunteer to do
this.

I hope to hear something about this Archive SC499 patch soon. Thanx
in advance.

		Ton.
From: hedrick@geneva.rutgers.edu (Charles Hedrick)
Newsgroups: comp.os.linux
Subject: Re: date, clocks, and FAQs
Date: 2 Oct 92 21:32:58 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

apm233m@vaxc.cc.monash.edu.au writes:

>I have deduced that the Linux (and all other unixes?) clock keeps time
>as GMT (UTC?). ms-dos keeps local time. To preserve some compatibility
>it seems to me that during the post boot-up processing phase under
>Linux the CMOS clock should be read and the value of the TZ variable
>added to it to produce the GMT time for the Linux clock. Is there a
>standard or prefered way of doing this?

I believe you want the stuff in binaries/usr.bin/timebin.tar.Z or
sources/usr.bin/timesrc.tar.Z on tsx-11.mit.edu.  This gives you a
program "clock" that will let you set the Linux clock from the CMOS
clock or the CMOS clock from the Linux clock, and will let you specify
whether you keep your CMOS clock in GMT or local time.  There's a file
time.doc with the binaries that explains how to use it, as well as the
files in /usr/lib/zoneinfo, which define the time zones.  timebin
supplies a version of date that knows how to handle time zones.  But
that's now built into libc, so I recommend that you use the current
version of date from the root disk.

Because different people want different setups, this is more complex
than it might be.  You're right that the assumption is that Unix uses
GMT.  DOS uses local time.  Because I use mostly Linux, I keep my CMOS
clock in GMT.  I use the MKS toolkit under DOS, which expects (or at
least allows) the clock to be in GMT, and does zone translation.
People who use DOS a lot, and want DOS time to work as expected, will
probably want to keep their CMOS clock in local time.  The
disadvantage of this is that you have to remember to change the CMOS
clock for daylight time.  If you keep it in GMT, that is handled
automatically.  The program "clock" supports all possible combinations
of GMT and local time.

Note that "clock" does user-mode I/O to read and write the CMOS clock.
If more than one thing is going on at the same time using CMOS,
there's a possible race condition.  This should not be a problem when
clock is used in /etc/rc, and in fact I don't expect it ever to cause
trouble in practice.

Note that ka9q has an "rdate" command that will let you set your Unix
clock from the network (though you have be running as root for that to
work).  Once the kernel TCP gets up, presumably rdate and/or ntp can
be ported.
Newsgroups: comp.os.linux
From: bjl@loki.research.ptt.nl (Ben Lippolt)
Subject: Re: How small a root partition can I get away with?
Keywords: small HD
Reply-To: B.J.Lippolt@research.ptt.nl
Organization: PTT Research
Date: Mon, 5 Oct 1992 07:13:49 GMT

msb@cats.ucsc.edu (Maurice Stanley Barnum) writes:

>Would a 4 meg root partition be enough?  Offhand, I can't think of
>too much that goes on the partition, though I don't know how big
>/dev and /bin get.  

I use 4 meg and that's plenty. I even keep 2-4 kernels around. The trick
is to put only enough stuff on it to be able to mount your /usr partition.
I believe that without my kernels my root-partition is about 1-1.5 meg.

But in your case you might consider making one 60 meg partition and put
everything (/ /usr swap) on that partition. That way you make the most
efficient use of your system. 60 meg should be enough for a decent Linux
system. My /usr (including all the basic stuff, X11, TeX, etc) is about
45 meg.


Ben Lippolt.
Newsgroups: comp.os.linux
From: tree@midget.towson.edu (Denise Tree)
Subject: Re: Pascal compiler needed
Reply-To: tree@midget.towson.edu (Denise Tree)
Organization: The Internet
Date: Thu, 1 Oct 1992 03:21:31 GMT


alovellkerberos.demon.co.uk (Anthony Lovell) writes:

|Another solution would be to use p2c to convert the pascal
|interpreter source.

  Much thanks for the many responses this time!

  Well, I got p2c and it compiles, as is so often the case with
  gcc 2.2.2, out of the box.

  P2c works great and is really fun to use with the pascal.el mode
  of gnu emacs. I'll try and get it to run p2c with the compile
  command. And when I get time I will try to compile the pascal
  interpreter. 

  P2c is really nice too, for people like myself who are working at
  learning C but who are forced to take pascal courses to satisfy
  GUR requirements; using Linux and associated fun tools on my
  pretty-much-rockin'-home-*nix-system takes much of the futility
  out of pascal-grubbing-for-grades-wastage.

|Denise why the change of major, got sick of Bio:)

  How sweet... you remembered '\003' '\003' :-)
  I've found I prefer virtual bugs to microscopic ones and I rather
  enjoy the hackish folk. GPA preservation too... I was being a bio
  major in my spare time!
_____________________________________________________________________
_______________ Denise Tree
____________________________tree@midget.towson.edu
_________________________________________.... . . .   .   .    .     .
                                                                     .
                                                                     .
                                                                     *
From: sachse@owlnet.rice.edu (Eric Christopher Sachs)
Newsgroups: comp.os.linux
Subject: XFree386 with Trident
Keywords: XFree386, Trident
Date: 5 Oct 92 17:17:49 GMT
Article-I.D.: rice.Bvns1q.EEz
Organization: Rice University


  Has anyone gotten the new version of X386 on tsx-11.mit.edu
to work on a Trident card yet.  I had the old VGA version of
X386 working with my Trident card but the new SVGA version
that just came out does not appear to work.
  The results of running startx are listed below.  Unfortunately
the error message that is returned is not correct because
the permission settings for the new X386 are the same as the
old X386 monochronme that will still work if I change the X
link.
  I would guess that my Xconfig file is just not giving the
X386 program enough information to work with my trident card.
Unfortunately the X386 man page and vga.dbase file which came
with the new version do not have any information about how to
set the new version up to work with a Trident chip.  These two
files appear to be the same ones as were in the last release.
If anyone knows where I can find new versions of these files
or has suggestions as to how to get XFree386 to work on a Trident
under Linux then please let me know.



Results of running startx using new full version of X386:
---------------------------------------------------------
X386 Version 1.2 / X Windows System [linux v1.1]
(protocol Version 11, revision 0, vendor release 5000)

Failed to read VGA Bios.  (X386 must be installed as suid root.)
Failed to read VGA Bios.  (X386 must be installed as suid root.)

Fatal server error:
no screens found

giving up.
xinit:  Interrupted system call (errno 4):  unable to connect to X server
xinit:  No such process (errno 3):  Server error.
---------------------------------------------------------

Results of running ls -l on /usr/bin/X11/X*:
---------------------------------------------------------
lrwxrwxrwx   1 root     daemon          4 Oct  5  1992 /usr/bin/X11/X -> X386*
-rws--s--x   1 root     daemon     687077 Jul  1  1992 /usr/bin/X11/X386*
-rws--s--x   1 root     daemon     545796 Oct  4  1992 /usr/bin/X11/XMON*
---------------------------------------------------------


The XMON program is the VGA version of X386 and if I change the X link to
point to it instead the program works fine and X starts up in VGA mode.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
           Eric Sachs
     Graduating Class of 93
       Comp Sci/Mana Stud

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Newsgroups: comp.os.linux
From: hlu@eecs.wsu.edu (H.J. Lu)
Subject: new README for HLU bootable root disk.
Organization: School of EECS, Washington State University
Date: Tue, 29 Sep 92 22:53:32 GMT

The main change is

(cd /; /mnt/bin/tar cf - ./bin ./dev ./etc ./lib ./usr ./tmp ./vmlinux) | (cd /mnt; /mnt/bin/tar xvvf -)

That is in one line.

BTW, I will update the kernel to 0.98 once I get it compiled.

H.J.
---------------
These are bootable root disks for Linux. Kernel is 0.97 patch level 6
with Ted's one line fix for serial.c. There are some basic binaries on
root disks, all of which are linked with jump table 4.1. They are on
tsx-11.mit.edu under pub/linux/GCC/rootdisk.


This is a partial list of what are on root disks.

1. bash 1.12
2. gnu tar 1.10 (tar.Z)
3. compress 4.2.3
4. elvis 1.6
5. doshell, chmod, chown, cp, ls, mv, rm, and ln.
6. mount, umount, swapon
7. more
8. ps and free
9. mkfs, mkswap, fsck and fdisk

There are two versions of root disks, one, 3rootdisk.Z, for 1.44MB drive,
the other, 5rootdisk.Z, for 1.2MB drive. Please do

1. uncompress [3|5]rootdisk.Z.
2. rawrite or dd it to a floppy disk.
3. boot that floppy disk.

If you want to use it to install Linux on your HD, you are on your own.
Everything is there. But you have to know how to use them.

Since there is no enough room on a 5.25" floppy, I left out init, getty
and login stuffs. After booting Linux off a 5.25" floppy, do

su
doshell /dev/tty2 bash&

You will get another virtual console on /dev/tty2.

Suppose you want to install Linux on partition, /dev/hdxx, whose size
is yyyy K bytes, you can use fdisk to find it out, you do

mkfs /dev/hdxx yyyyy
mount /dev/hdxx /mnt
cd /mnt
mkdir bin
cp /bin/tar.Z /mnt/bin
chmod 755 /mnt/bin
uncompress /mnt/bin/tar
(cd /; /mnt/bin/tar cf - ./bin ./dev ./etc ./lib ./usr ./tmp ./vmlinux) | (cd /mnt; /mnt/bin/tar xvvf -)

You have to do these:

cd /lib
cp libc.so.4.1 /mnt/lib
cp libm.so.4.0 /mnt/lib

This will save some disk spaces since cp can make holes and tar can't.
You now should edit /mnt/etc/fstab to make sure /dev/hdxx will be
mounted as root. There are some examples in /mnt/etc/fstab. After that,
do

cd /mnt/etc/lilo
rm map boot.????
./lilo -r /mnt -b /dev/hdxx -i boot.b -v -v -v /vmlinux


Now, you can boot Linux from your HD. To install the other stuffs
should be very trivial now since you have tar and compress on your HD,
and you can boot Linux off your HD. I suggest you get my bonuses come
with jump table 4.1.

I will try to update my root disk regularly with Linus' new kernel.

This root disk works on my machine with 100MB IDE drive. I don't know
anything about your machine or SCSI. Wish you good luck.

Correct me if I am wrong. Tell me about your story.


Thanks.

H.J.
hlu@eecs.wsu.edu
09/25/09
Newsgroups: comp.os.linux,comp.unix.bsd
From: russed@nuge103.its.rpi.edu (Daniel Russell)
Subject: Re: Suggestions for the free Unix projects
Date: Wed, 7 Oct 1992 01:05:55 GMT

rmk@rmkhome.UUCP (Rick Kelly) writes:
[ really long quote deleted ]

>At one time, it was rumored that BSDI was going to provide a binary only
>release of BSD386 for $295.  Have they ever said anything about this?

	Why is this on c.o.l?  Why not c.u.bsd (or something, I'm not
familiar with the hierarchy over there)?  Please keep c.o.l limited to
discussions that (even remotely) relate to Linux.
	thanks, and happy Linuxing!
 dan
=====
Dan Russell		russed@rpi.edu

>-- 

>Rick Kelly	rmk@rmkhome.UUCP	unixland!rmkhome!rmk	rmk@frog.UUCP
Newsgroups: comp.os.linux
From: djr48312@uxa.cso.uiuc.edu (X X)
Subject: Re: Who will handle publicity for Linux 1.0?
Organization: University of Illinois at Urbana
Distribution: usa
Date: Tue, 29 Sep 1992 04:48:12 GMT
Keywords: Advertising

I think linus should get a little compensation for the hard work he has
put into this wonderful product.  Maybe make it so if you register it for
say x dollars you get these additional features.  
Newsgroups: comp.os.linux
From: oyang@cs.monash.edu.au (Kai Shing O'Yang)
Subject: 0.97pl6 + X11v2.0 problems?
Organization: Computer Science, Monash University, Australia
Date: Sat, 3 Oct 1992 00:57:43 GMT

I'm currently running 0.97 pl6 with the old x1.1. I've got the v2.0
stuff and when i tried to startx, it failed because can't listen
to some sockets. I know this is because I haven't got the tcpip code 
in the kernel. However, the tcpip.0.8 stuff works for pl2 only, is there
anyway to bypass the socket checking? or do i need to upgrade to 0.98
in order to get x2.0 running?

Thanks for your help
Kai
--
- Kai S O'Yang, Dept of Comp Sci, Monash Uni, Clayton VIC 3168, Australia  
- AARNET: oyang@bruce.cs.monash.edu.au         - Voice : +(61) 3 565 5778
					       - FAX :   +(61) 3 565 5146
'If one believes everything from the book, rather have no book.'