HDTenEightyP/NetNews huggingface dataset:
From: erc@unislc.uucp (Ed Carp)
Subject: Re: linux-logo, gif version uploaded to tsx-11
X-Newsreader: Tin 1.1 PL5
Organization: Unisys Corporation SLC
Date: Thu, 13 Aug 1992 23:10:55 GMT

Yuan-Yin Wu (yuanyin@utdallas.edu) wrote:

: Since some one here said he wants a gif version of the linux logo,
: I've put one in gif87 format in the incoming directory at 
: tsx-11.mit.edu. Or if you have gs, just run gs to get a gif output.

Since we can't read the incoming directory, it would be nice if someone
would mention the name of the file... :(
-- 
Ed Carp, N7EKG     erc@apple.com                801/538-0177
"This is the final task I will ever give you, and it  goes  on  forever.   Act
happy, feel happy, be happy, without a reason in the world. Then you can love,
and do what you will."           -- Dan Millman, "Way Of The Peaceful Warrior"
Newsgroups: comp.os.linux
From: peterw@archsci.arch.su.oz.au (Peter Williams )
Subject: another proposed LINUX logo
Organization: Design Computing Unit, The University of Sydney
Date: Wed, 19 Aug 1992 08:15:09 GMT

I have posted a proposed Linux logo in pub/linux/ll.ps on
archsci.arch.su.oz.au (129.78.66.1). It is a hand coded postscript image and
is only about 6kbytes. It depicts a seabird (freedom) forming the L of linux.
I have tested it under pageview, ghostview and an apple laserprinter.

Under ghostview the inux of linux does not show properly due to problems with
scaling the Helvetica font but you can still get the idea.

This is only a proposal (for the moment) and I will clean it up later.
I am also open to suggestions for enhancements to the proposal.

-- 
Peter Williams                |e-mail: peterw@archsci.arch.su.oz.au
Key Centre for Design Quality |phone: +61-2-692 2053 or +61-2-660 6156
University of Sydney          |+++++++++++++++++++++++++++++++++++++++
From: hedrick@aramis.rutgers.edu (Charles Hedrick)
Newsgroups: comp.os.linux
Subject: KA9Q now works with WD80x3 Ethernet controllers
Date: 15 Aug 92 09:30:57 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

I'm still not sure whether the kernel TCP/IP is at a point that it no
longer makes sense to do work on KA9Q.  But I spent this evening
making KA9Q work properly with Ethernet.  (I did this because we've
now got a machine on our Ethernet, and it's a lot faster to get
software onto it this way.)  On cs.rutgers.edu, you'll find
/pub/linux/ka9qsrc.6.tar.Z and ka9qbin.6.tar.Z.  (Yes, I've checked
the protections.)  The binary has a binary of KA9Q and source for the
kernel changes, together with instructions on how to install the
device driver in the kernel and how to set up KA9Q.

The device driver is a modified version of we.c which has been on
tsx-11 since May (in wd8003.tar.Z).  I had to change it for several
reasons:
  - the new IRQ code
  - a bug in definition of memory size that caused lots of
	checksum errors
  - a bug in the receive interrupt handling that caused very
	poor performance.  (This fix was taken from a newer
	copy of we.c that appears to be intended for use with
	the Alpha kernel TCP/IP.  I couldn't just use the new
	we.c as is, because the structure of Ethernet drivers
	has changed somewhat.)

This code will win no prizes for performance, but I can tranfer 2 MB
files in one or two minutes.  This is still a great improvement over
serial lines or floppies.  Furthermore, while doing that file
transfer, I can be using telnet with no visible interference.

The device driver will support WD8003, WD8013, and SMC Elite
controllers.  KA9Q itself doesn't care what kind of controller you are
using.  But you need a device driver in the kernel for the specific
controller type.
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.os.linux
Subject: Re: Stabilizing Linux
Date: 13 Aug 92 20:22:14 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

In article <1992Aug13.150646.22412@athena.mit.edu>, komarimf@craft.camp.clarkson.edu (Mark Komarinski) writes:

| Having a committee would at least *try* to keep both sides happy.
| Or, if we Russ Nelson's idea about a 'paid programmer' to make an official
| release/etc, this committee could help him (or her...) get what both groups 
| eventually want:  a stable, working system.

  I would consider a committee a success if they could keep track of
who's working on what, how it's coming, and post the status weekly.

  I have little enough time to do anything with Linux, and limit myself
to porting apps or writing small apps, because of it. While I've been
lucky that the 3-4 apps I ported were not duplicates, I would really
like see a list of "what's being worked on" and "what's been
requested." It would allow me, and other busy people, to pick something
we know about, offer a little help to someone who's a bit bogged down,
etc.

  I think this is something that some who can't write code could do, but
someone has to grab the bull by the horns and do it. And don't look at
me, I can and do write code, and I'm porting some of my usenet sources
and new toys to Linux. I may even break down and fix the flaming shared
memory so I can get some things working, but that's another story.

  Here's the info I have to contribute, will someone who is using Linux
and wants to contribute please pick up the ball?

prog		use			status

bpe		binary file edit	done, on tsx-11 and banjo
zoo		archiver		done, on tsx-11
diskgeom	list HD geom in DOS	done, sent to TAMU
zip		archiver		1.8g done, wait official rls date
time		/bin/time		done, uploaded to tsx-11
bundle		multivolume tool	wait shared mem fix
bplus		B+tree library		wait new shared lib format
qictoo		QIC-02 tape driver	abandoned, dup effort

-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
    I admit that when I was in school I wrote COBOL. But I didn't compile.
From: james@netcom.com (James L. Paul)
Newsgroups: comp.os.linux
Subject: ps-0.97 error creating psdatabase
Date: 15 Aug 92 20:10:36 GMT
Organization: Netcom

I compiled 0.97 patch1 ok today, by playing with the include directory
problem and removing the SCSI code. (Yes, I had to do both. have no idea
why. I gather I'm not completely alone though.)

I tried to compile ps-0.97, but the include files problem just got too
convoluted to deal with. So, I just copied the binaries into /usr/bin.
w, uptime, and free work ok. ps doesn't. I have /usr/src/linux/tools/system
there, and even built it an extra time, but I get this error: 

ps -U /usr/src/linux/tools/system /dev/hdb3
symbol '_main_memory_start' not found
trying to read invalid address

I have /dev/swap symlinked to /dev/hdb3 (my swap partition) and
have tried using that, and also just a ps -U, but get the same error.

Where is the problem, and how to fix?

-- 
James L. Paul

Internet:    netcom!james@apple.com | AppleLink: D1231 | CompuServe: 72767,3436
UUCP:   {apple,amdahl}!netcom!james | GEnie:    J.PAUL | Voice:    607 776-3070
Packet: N6SIW@WB2PSI.#WNY.NY.USA.NA | Delphi:   JLPaul | Home Fax: 607 776-3070
America Online:   JLPaul or Memorex | BIX:      JLPaul | Prodigy:       PWTB41A
From: tytso@ATHENA.MIT.EDU (Theodore Ts'o)
Newsgroups: comp.os.linux
Subject: Re: EISA bus machines
Date: 23 Aug 92 05:47:41 GMT
Reply-To: tytso@ATHENA.MIT.EDU (Theodore Ts'o)
Organization: The Internet


   From: cc_s525@kingston.ac.uk (Francis Bell)
   Date: 22 Aug 92 14:10:56 GMT

	  The FAQ says that Linux won't run on EISA machines. Can anyone
   explain why, and suggest how difficult it would be to remedy ?

That's not strictly true; if your EISA machine has a ISA floppy
controller and a ISA graphics card plugged into, then Linux should be
able to run on it without any problems.  In fact, I think I remember
someone reporting success with this configuration.

The problem is that if you're doing this,  there's really no point in
your having  shelled out extra $$$ for the EISA bus, since you wouldn't
be able to use it.  

What's needed to rememdy this is that someone would need to write (or
"borrow" from somewhere) device drivers that recognized EISA interface
cards, particularily the hard disk and video interfaces.

The same situation is true for the MCA bus, although that will be much
harder, since MCA isn't even backwards compatible with ISA.  At least
with EISA, someone could borrow a ISA hard disk controller while he/she
was debugging the EISA controller; thus development would be much easier
under EISA than it would be under MCA.  That's not to say that it
wouldn't be possible to include MCA support as well; it would just be
much more complicated.  So I wouldn't hold your breath for MCA support,
but EISA support is within the realm of possibility, assuming someone
blessed with such a machine is willing to look at writing Linux drivers
for these new controllers.

								- Ted
From: laakkone@klaava.Helsinki.FI (Tero Laakkonen)
Newsgroups: comp.os.linux
Subject: tlA: reggae's Incoming dir must be chmod ugo+x...
Date: 14 Aug 92 10:25:32 GMT
Organization: University of Helsinki

... so that people can cd into it.

-tero.
Newsgroups: comp.os.linux
From: hlu@phys1.physics.wsu.edu (Hongjiu Lu)
Subject: Re: GCC questions
Organization: Washington State University
Date: Tue, 18 Aug 92 18:53:26 GMT

In article <1992Aug18.162006.13422@athena.mit.edu>, chchen@stat.fsu.edu (Ching-Hsiang Chen) writes:
|> I've upgraded to GCC 2.2.2d yesterday. By reading FAQ for GCC and FAQ for
|> Linux, I still have some questions:
|> 
|> 1. The FAQ says I should get rid of gcc older than 2.2.2. But how about
|>    2.2.2 itself? With 2.2.2 and 2.2.2d together, I don't have much more
|>    hard disk space left. Should I used the method suggested in Linux FAQ,
|>    which means I need to use some device to detect the depending version
|>    of all the binaries compiled by GCC and then recompile the older ones?
|> 

You only need gcc 2.2.2 for X386 v1.1 which will be replaced by a new one
soon. Please read release.2.2.2d and make your own decision.

|> 2. Having only 2 introductory C books on hand and a simple GCC man page,
|>    Should I keep all the stuffs in the following 3 directories if I don't
|>    write C programs myself and just use GCC to compile new utilities and
|>    use them?
|> 
|>        /lib/*.*
|>        /usr/lib/...../i386-linux/2.2.2d/*.*
|>        /usr/lib/...../i386-linux/2.2.2d/shared/*.*
|> 
|> 

You need them. 

|> Steve Chen                   chchen@stat.fsu.edu
|>        

-- 
H.J.
Gcc/libc maintainer for Linux.
Newsgroups: comp.os.linux
From: kennu@mits.mdata.fi (Kenneth Falck)
Subject: Re: GCC questions
Organization: Microdata Oy, Helsinki, Finland
Date: Wed, 19 Aug 1992 19:47:38 GMT

In article <1992Aug18.185326.23062@serval.net.wsu.edu> hlu@phys1.physics.wsu.edu (Hongjiu Lu) writes:
>|>        /lib/*.*
>|>        /usr/lib/...../i386-linux/2.2.2d/*.*
>|>        /usr/lib/...../i386-linux/2.2.2d/shared/*.*
>|> 
>|> 
>
>You need them. 

By the way, may I ask where that unbeliavably long and cryptic
path to the library files has come from? :-) No offence to whoever
is "responsible", but somehow I think it might be a little bit
less complex...

I suppose it has something to do with having a lot of GCC
libraries for different compilers on different machines on 
the same filesystem.

I must admit though, that I haven't even checked whether
you can change the default path very easily, probably so...

>-- 
>H.J.
>Gcc/libc maintainer for Linux.

-- 
kennu@mits.mdata.fi
From: boyer@sumax.seattleu.edu (Chuck Boyer)
Newsgroups: comp.os.linux
Subject: need: submissions, file descrptions for 00-index.txt tsx-11.mit
Date: 22 Aug 92 05:08:06 GMT
Organization: Seattle University, Seattle WA


Subject: Linux Project Registry
boyer@sumax.seattleu.edu
 
Linux ftp site file listing index.txt
began August 21 1992
 
A '00-index.txt' ascii text file listing of files in ea. dir. with
40 character 'one-line' description of the file. Like we are used to
at Simtel and wuarchive.wustl.edu ftp sites. So that 'newbies' can
comprehend from this listing what they may want/need and thus stay
away from what they don't want/need. I need help, what you know what
is please email me. The site listing will be of 'te
sx-11.mit.edu'.
 
(help needed with more obscure files already there, as well as
anything beyond 'beginner' status, as that is what I am, so basically
I need help on all stuff now, to get this listing started. I am
basically volunteering to coordinate a text file for each dir
to submit to the site coordinator to place in each head of each
dir. C'mon you guys, help with this one please.)
 
chuck
Newsgroups: comp.os.linux
From: d88-jwn@nada.kth.se (Johan W}hlin)
Subject: Does anyone have a _working_ /usr/include they could mail me
Originator: d88-jwn@dront.nada.kth.se
Keywords: gcc, include
Reply-To: d88-jwn@nada.kth.se (Johan W}hlin)
Organization: Royal Institute of Technology, Stockholm, Sweden
Date: Wed, 12 Aug 1992 19:11:43 GMT


Tnx 8) /Johan
From: cgwillme@cybaswan.UUCP (r b willmersdorf)
Newsgroups: comp.os.linux
Subject: lilo works fine! (At least for me :)
Date: 13 Aug 92 17:58:09 GMT
Reply-To: cgwillme@pyr.swan.ac.uk (r b willmersdorf)

Hi,

I finally found the courage to try to use lilo. I was tired of booting
from floopy, and as shoelace is being obsoleted anyway, I took the plunge,
even knowing that it still in alpha.

I found the documentation pretty daunting, but that's because it can do
a _lot_ of stuff in _many_ different ways. In the end I istalled it as
the boot record of my linux partition, left the dos master boot record
in place, and set the linux partition as the active one. Now when the
computer boots, it loads lilo, and it defaults to booting linux, or I
can press a key and boot dos. (At least that is my understanding of the
boot procedure :) With the vga mode pre-selected, booting is instant!! 
(err..., very quick, more like it). BTW, everything worked first time
through.

I just wanted to report a success history, so the people that are 
having problems with shoelace may try something else. Obviously, even
the AUTHOR warns that it's still alpha, so if it zaps your hard disk,
though luck. BTW2, if you're going to try this, back up _all_ boot sectors
to a _floppy_, according to the docs. 

Nice work to the guy is Switzerland that's writing this.

Bye,

-- 
--

Ramiro || cgwillme@pyr.swan.ac.uk
Newsgroups: comp.os.linux
From: vince@halcyon.com (Vince Skahan)
Subject: reorganize linux ftp sites ???
Organization: Northwest Nexus Inc. (206) 455-3505
Date: Thu, 20 Aug 1992 19:33:03 GMT

Might it be time to consider reorganizing the directory structure
of the Linux ftp sites?  So many people are working on so much
and being so successful that it's virtually impossible to figure
out where to get what. Is it reasonable to expect people to read
an upload announcement of 'freds utilities assortment' and understand
that it's the exact thing they need ?

I was thinking that maybe there needs to be an organization more
along product lines so it's obvious where to grab stuff.  The
current usr.bin doesn't do much for me.  If you don't know where
it should go, you can't figure out where to grab it.

There are basic things in any working system and other things that
some users don't feel are as essential. I come up with this:

	- kernel (sources/patches/docs too...)
	- basic utilities (/bin)
	- added utilities (/usr/bin)
	- X11 and stuff
	- communications packages (terminal emulation, not uucp)
	- uucp and e-mail packages 
	- usenet software
	- compilers
	- text processing
	- editors
	- maybe a whole branch for gnu ?
	- incoming stuff...
	- compilations of various kits (mcc, mj, [r|b]ootimage)

It might be worth considering moving goodies around to make the
directory structure a little clearer. Each file in the archives is
there to do something, indicating what it does by its place in the
tree on the archive sites might be somewhat self-documenting...

Also, each tree should have something like:
	- binaries
	- sources
	- patches from the 'normal' sources
	- info files (readme's, etc.)

So, you want to grab a copy of smail3.1 ?, cd to /pub/linux/mail
and grab bin/smail3.1pl25 for binaries, src/smail3.1pl25 for
preconfigured-for-linux sources, etc.


thoughts ?

-- 
          Vince Skahan				vince@halcyon.com (here)
    vince@atc.boeing.com (work)		    vince@victrola.sea.wa.us (home)

Newsgroups: comp.os.linux
From: pete@cbnewsl.cb.att.com (peter.j.fillingham)
Subject: 0.97 WORKS with SCSI ! [attn NEWBIES]
Organization: AT&T Bell Laboratories
Date: Fri, 14 Aug 1992 16:42:55 GMT
Keywords: linux, scsi


Hooray ! Despite the many postings re glitches, features, bugs, etc.,
both 0.97 boot-image and root-image work;
In addition to boot screen announcements of hd0 etc etc the following
graced my screen 
	sd0 @ scsi0 ID0 lun0
	sd1 @ scsi0 ID4 lun0
	sd0 p.1 start    32 size 51168 end 51199
	    p.2 start 51200 size 40960 end 92159
	sd1 p.1 start    32 size 20448 end 20479
	    p.2 start 20480 size 20480 end 4085?
and so with fear and trembling i interpreted sd1 p.1 as sdb1 & used
mkfs -c /dev/sdb1 10000
when asked for /usr in the [excellent] install script.
SO, the guts went on hda1 and the /usr stuff on /dev/sdb1 [AKA /usr].
While this may be OBVIOUS to the cognescenti, perhaps my experience
will be helpful to the less fortunate...
BTW, i KNEW that my first SCSi drive was employed elsewhere as
was the second half of sd1;  apparently the size reported is in
blocks of 512 bytes, wheres linux uses 1024 byte/block...
KUDOS to the SCSI freaks at woz etc.
...and KEEP THE ASPIDISTRA FLYING

Peter Fillingham [keeper of the DDEBs]      <<fillingham@att.com>>
Newsgroups: comp.os.mach
From: bgbg@cbnewsd.cb.att.com (brian.g.beuning)
Subject: multi processor 386 and mach
Organization: AT&T
Date: Thu, 13 Aug 1992 23:12:30 GMT
Keywords: multi processor 386 mach

Like many people, I have been considering getting
a 386 box just to be able to use mach (and UNIX and DOS).
So I keep checking the prices on the latest fast 486
machines.

But wait a minute, isn't the point of mach supposed
to be that it is meant for a multiple processor
machine?  So instead of getting a fast 486, shouldn't
I get a cheap 386 that has more than one CPU in it
and get more than the performance of a fast 486?

So my questions are:
1. Does Mach support more than one processor on a 386?

2. Are there any cheap (or reasonable) machines for
	sale that can be configured with more than
	one CPU?

	Thanks for an info,
	Brian Beuning
Newsgroups: comp.os.mach
From: mcrosbie@unix1.tcd.ie (Mark J. Crosbie)
Subject: Re: multi processor 386 and mach
Organization: Computer Science, Trinity College Dublin
Date: Mon, 17 Aug 1992 16:14:03 GMT

In <1992Aug13.231230.15155@cbnewsd.cb.att.com> bgbg@cbnewsd.cb.att.com (brian.g.beuning) writes:

>Like many people, I have been considering getting
>a 386 box just to be able to use mach (and UNIX and DOS).
>So I keep checking the prices on the latest fast 486
>machines.

>But wait a minute, isn't the point of mach supposed
>to be that it is meant for a multiple processor
>machine?  So instead of getting a fast 486, shouldn't
>I get a cheap 386 that has more than one CPU in it
>and get more than the performance of a fast 486?

>So my questions are:
>1. Does Mach support more than one processor on a 386?

>2. Are there any cheap (or reasonable) machines for
>	sale that can be configured with more than
>	one CPU?

>	Thanks for an info,
>	Brian Beuning

Hi Brian,

Mach does indeed support more than one processor in a system,
it was one of the design goals of Mach that it could run in parallel
systems with multi-processors. The kernel contains a lot of locking
structures for ensuring that the data structures in the kernel are
updated cleanly etc.

However, to actually run Mach on a multi-processor system, you have to
buy a multi-processor machine which Mach supports.
I'm working on a Mitac 4280G/MP which implements the Corollary Bus 
architecture in it's own wonderful way. The Corollary Bus is a
proprietary multi-processor bus which allows multiple processors to run
and ensures cache-coherency between them all.
Mach recognises this by havign the pre-processor symbol CBUS defined
in the kernel code.

It also recognises Sequent Symmetry, Intel Hypercube, Compaq Systempro,
 Vax, mips and plain uni-processor 386 machines.

Simply put, to buy a machine with more than 1 386 would be very
expensive as you would be paying for the multi-processor bus which would
have to be quite complex if caches were used on each board.
It would also have to be recognised by Mach, as each bus implementation
is different. If Mach didn't support it, you could forget it!

In my humble opinion, it's a lot simpler to buy a FAST (50Mhz) 486 
machine with a fast
SCSI disk and lots of memory to run Mach (>8 MB) than it is to buy
a multi-processor system.

Hope this helps,

Mark Crosbie		mcrosbie@ashe.cs.tcd.ie
Computer Architecture Group
Trinity College, Dublin
Dublin 2
Ireland.

Newsgroups: comp.os.mach
From: cfleck@src.honeywell.com (Chuck Fleckentein)
Subject: Re: ATTN DECstation/SGI Mach users
Organization: Honeywell Systems & Research Center
Date: Wed, 19 Aug 1992 19:13:46 GMT

In article <SALEHI.92Aug11121408@gaia.cs.umass.edu> salehi@gaia.cs.umass.edu (James Salehi) writes:
>As part of a long-term research project in network protocols, 
>we are planning to use Mach as our OS.  We would like to establish 
>contact with groups or individuals who are using Mach on the DECstation 
>and/or SGI platforms, to share ideas and solutions to problems which 
>arise in the build, port, and development process. 

   I have the Mach 3.0 microkernel running on our DEC 5000...
   Please keep me informed of your progress...

>
>We have also put together documentation on the DECstation build, to help 
>others who are interested. 

   Please send me a copy.... I'll compare with my notes..

>
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
>	a soft link to /dev/rz0g/MACH_PAGING_FILE (where /usr is mounted on 
>	/dev/rz0g.)  The paging file on the rz0g partition is found, but
>	"ls /usr" gives an empty directory listing.  So I can't access
>	/usr/mach3 and all the code that's there. 

        
        I installed the 3.0 micro kernel on a Decstation that has
        Dec Ultrix on it... The non-root partitions could not be
        mounted because the major number for device special files
        were 21 (what Ultrix expects).  ... 

        Mach 3.0 wants a major number = 8    :-).....

        Once I created device special files with major 8, I was
        able to mount the /usr and other partitions....

>
>	during the boot.  We are ignoring the SUPERROOT (/../../) and 
>	LOCALROOT constructs under the assumption that they only apply 
>	to CMU's configuration.  Is that correct? 


	True... I believe the Superroot is only available via the
	Andrew file system....



|\/\/\/|
|      |
|      |        ________________
| (.)(.)       /                \
C      _)      | Think parallel | 
 | ,___|    ___|     Man!       |
 |   /         \________________/
 /---\
/     \

Chuck Fleckenstein
cfleck@src.honeywell.com   
Honeywell inc
Date: 13 Aug 92 02:45:49 GMT
From: lychan@socs.uts.edu.au (91031322 l y chan)
Newsgroups: comp.os.mach
Subject: Mach 3.0 on 386/486

I'm looking for a version of Mach 3.0 that will run on Intel 386/486.
I would also like to know the hardware requirements for that.    

And I'm also interested to know those who have successfully installed it
on 386/486 machines and are still using it.

Thanks!
Newsgroups: comp.os.mach