HDTenEightyP/NetNews huggingface dataset:
From: thoth@uiuc.edu (Ben Cox)
Subject: Re: Mail hint
Originator: btc30679@uxa.cso.uiuc.edu
Reply-To: thoth@uiuc.edu (Ben Cox)
Organization: University of Illinois at Urbana
Date: Tue, 21 Jul 1992 23:41:45 GMT

rmk@rmkhome.UUCP (Rick Kelly) writes:

>>|> SVR4, and (2) to more accurately calculate throughput figures.  There are
>>|> still problems with uucp, though.  I'm seeing uucico hang on a modem port without
>>|> timing out - I wonder if it's related to H. J.'s recent patches affecting
>>|> restartable system calls?
>>
>>I didn't change any sys calls. All is done inside the kernel.

>Interestingly enough, I have Taylor UUCP up and running on Coherent 4.0
>Beta.  I have seen the same uucico hang on a modem port problem, but it
>only seems to happen every couple of weeks.  I haven't come up with a
>reliable method of reproducing it yet.  It would seem that DTR isn't
>changing state when the modem hangs up.

This used to happen to me too (hanging with out timing out), until I
upgraded to Linux 0.96c-pl2.

Now the only problem I have is xcomm (easily solved: use kermit
instead :^>).  (Oh, and occasionally I get a busy signal.  Is there a
patch for that? :^>)

Seriously, though, If you haven't upgraded to 0.96c-pl2, you should
try it.

--
Ben Cox
thoth@uiuc.edu
From: card@masi.ibp.fr (Remy CARD)
Newsgroups: comp.os.linux
Subject: Re: Problems with extfs
Keywords: problems, extfs
Date: 30 Jul 92 16:56:53 GMT
Organization: Laboratoire MASI - Universite Pierre et Marie Curie - Paris - France

In article <Bs5tqK.BMr@ux1.cso.uiuc.edu> Upholder@uiuc.edu (THE Upholder of Truth) writes:
>I decided to start from scratch on my new 486/50 and use the extended
>filesystem instead of the Minix filesystem...
>
>so after makeing sure I had backed up everything, I repartitioned
>the harddrive and executed the mkefs binaries that I pulled from
>the france FTP site.  My partitions are as such:
>
>	/dev/hda1 70M dos
>	/dev/hda2 8M /  (was originally going to be swap until I remembered
>			 that linux needed a minix root filesystem)
>	/dev/hda3 20M /home (using the extfs)
>	/dev/hda4 60M /usr (using the extfs)
>
>no problems making or mounting the filesystems... rebuild the system from
>the backups.. modify the fstab as needed... no problems at all.
>
>However, many of the binaries don't seem to want to work with the new 
>filesystems.
>
>for example, issuing a 'compress vixie-cron.tar' results in an error message
>that a .Z could not be appended because the filename was already 14 characters.
>
>also, while in /usr/tmp, a emacs README (when README exists) results in emacs
>not finding the file and starting with a new file (apparently because emacs
>cannot find the file).  However, emacs /usr/tmp/README works just fine. 
>
>Third, tcsh cannot complete the names of directories or files in an extended
>partition (ie, cd /us[TAB]/tm[TAB]/RE[TAB] to get /usr/tmp/README does not
>work.  It will find /usr (because it's in the minix I-node list?) but not
>the tmp or thr README).
>
>My question is, do I just need to recompile the binaries or is the problem
>more severe than that?

	To use the ext fs (and any fs different from the Minix fs) in Linux, you
have to recompile every program using the readdir() system call (e.g. tar, shells,
file utils, ...) with gcc 2.2.2 (actually at least gcc 2.11c but it is better to
use the last release).

>
>-- 
>The Upholder of Truth		  	    I am not only ready to
>Upholder@uiuc.edu (BSD/ASCII mail)          retract this, but also
>jar42733@sumter.cso.uiuc.edu (NeXT mail)    deny I said anything.  =)
>wi.4173@wizvax.methuen.ma.us (anon. mail)   This is *NOT* CCSO's opinion.


	Remy Card
	card@masi.ibp.fr
From: Michael_Kraehe@hb.maus.de (Michael Kraehe)
Newsgroups: comp.os.linux
Subject: Re: C_A_D=0
Date: Wed, 29 Jul 92 11:56:00 GMT
Organization: MausNet
X-Gateway: MausGate/News 1.11

 > I have mucked about with the kernel lately (0.96cpl2). When I set the
 > C_A_D varaible to 0 (to avoid reboot on pressing C-A-D) (and compile,
 > reboot :-). After login in and executing sync I press C-A-D and the
 > system locks, completely... Anyone with similar experiences?

I think this is a bug in some rom's of taiwan-mainboards, the same thing
is since I canged my board to a 486/33. And I've seen it on some Minix/AT's

By Michael.
From: rohrer@fncrd6.fnal.gov (Keith Rohrer)
Newsgroups: comp.os.linux
Subject: Re: Extended File System
Summary: we know what we need, now WHERE is it?
Keywords: extended file system efs where location
Date: 23 Jul 92 04:54:26 GMT
Followup-To: comp.os.linux
Organization: Fermilab

In article <711857605.F00039@remote.halcyon.com> Rob.Levin@f217.n3802.z1.fidonet.org (Rob Levin) writes:
[deleted...]
>support for the extended FS.  You just need to locate the special mkfs
>program and I think a special mount.  

Okay, so we just need a new mkfs and a new mount.  From WHERE can we get
them?  Anybody?

And while we're at it, does anybody know if the efs is slower/faster than
the Minix fs, and/or slower/faster than OS/2's HPFS or somebody's (BSD's?) 
FFS?

>Rob L.
> * Origin: Via the Annex in Victoria, TX (1:3802/217)

	Keith
(rohrer@fncrd0.fnal.gov)
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.os.linux
Subject: Re: Device names (was Re: ttys2 not responding)
Date: 22 Jul 92 14:37:05 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

In article <711742044.F00069@remote.halcyon.com>, Rob.Levin@f217.n3802.z1.fidonet.org (Rob Levin) writes:

|> Could you be more specific on the BSD convention for hard disk naming? 
|> And for partitions, if such a thing exists in the vanilla BSD
|> environment?

  Let me try to explain several ways in which disks are named, all of
which seem to me to be better than the way it's currently done in linux.

  Many BSD systems call their drives hd#P (where # is the drive # and P
is the partition). Many have conventions that partition c is the whole
disk. SCO uses the drive number and partition number (rather than
letter), reserving the letters for a=all and d=dos (as I recall).

  Some systems include the controller number on the id, like V.4, where
a device might be c0d0s3 (controller 0, device 0, slice 3).

  What I think might improve the information content of names is to
include the controller and device number as digits, then the partitions
as lower case characters, reserving the character A of the whole (ALL)
disk. This would give hd00a, hd00b, etc, hd00A the whole disk, hd01a the
2nd disk, etc. hd10a would be the 2nd controller, drive 0. I think
that's important in the near term, because there are a lot of smaller
drives becoming available and people need a 2nd controller to run more
than 2 drives.

  Since I'm probably going to get flamed for this anyway, I think the
SCO floppy naming conventions are useful, if somewhat verbose. They're
easy to remember because they contain tpi, spt, etc. fd096ds15 is device
0, 96 tpi (HD), double sided, 15 spt. The raw (character) device has an
'r' added to the front of the device name.

  While that's not optimal for linux (no one runs linux on single sided
disks, do they?), I think the names in use now may have less than optimal
information, and could be improved. I leave it to someone else to pick
names which reflext the mimits of the existing device drivers.
-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
	It never ceases to amaze me that otherwise rational people, able to
	understand calculus, compound interest, and the income tax form, can
	continue to believe that poker is a game of chance.
Newsgroups: comp.os.linux
From: Ching-Hsiang Chen <chchen@stat.fsu.edu>
Subject: Re: olvwm
Reply-To: chchen@stat.fsu.edu
Organization: The Internet
Date: Tue, 28 Jul 1992 22:59:05 GMT

|From: tdunbar@vttcf.cc.vt.edu (Thomas Dunbar)
|Subject: Re: olvwm
|Organization: Virginia Tech, Blacksburg, VA
|
|
|the olvwm binary that's been posted at banjo.concert.net for a good
|while is the window manager i regularly use (with linux 0.96c-p2).
| why all these msgs for a binary that's already there?
|  thomas

|From: tdunbar@vttcf.cc.vt.edu (Thomas Dunbar)
|Subject: Re: Compiling OLVWM: the steps
|
|the olvwm binary that's been posted at banjo (and tsx-11) for weeks
|works FINE! i assume the recent todo in c.o.l. is just due to 
|not making the needed changes in xinitrc (twm -> olvwm) and
|in Xconfig (olvwm needs the 75dpi fonts, ie lucida)

Well, not that simple. It just didn't work. I change xinitrc and Xconfig
but no luck. So I compiled it myself. Mine works. I even tried to run these two
versions alternatively. Only mine works. I guess people who can not get the
binary from banjo/tsx11 work should try to compile themselves. Besides,
recompile it is not that difficult.

My Linux is 0.96c-p2 with DOSFS-alfa-6.                  

Steve Chen
From: vargish@sura.net (Nick Vargish)
Newsgroups: comp.os.linux
Subject: Help with 0.96c pl 2 Compile Please
Summary: duplicate IRQ symbols?!
Date: 27 Jul 92 22:22:22 GMT
Organization: SURAnet, College Park, MD, USA, NA, Earth, Milky Way

It's me again... I'd like to thank everyone who helped with my previous
slew of questions (you know who you are!). I have a couple more, of course,
mostly relating to rebuilding kernels.

1. pl2 won't compile "out-of-the-box" (the box being the file on banjo in
   ../Incoming). I keep getting linker errors to the effect that symbols
   "_IRQn_interrupt" (where n=3,4,5,9) in "irq.o" and "sys_call.o" are
   multiply defined. This keeps make from building kernel.o and we go
   downhill from there.

   I looked at the code, and the macro that defines the symbols looks like
   the last one in /usr/src/linux/include/asm/irq.h. But "irq.c" seems to
   be the only program that uses "irq.h" and certainly doesn't explicitly
   call BUILD_IRQ (I _think_ that's the name of the macro) more than once.
   Commenting out the lines where IRQn_interrupt are built in irq.c kills
   the compile as well (surprise! :^)

   The pl-2 didn't come with any documentation that I could see. Did I
   miss it?

2. Currently I have a file called "vmlinux.96c+" in my root directory.
   /etc/config points to this... is this the kernel? How is it related
   to /usr/src/linux/Image. And if I built a new Image yesterday (before
   unpacking pl-2) should I "cp /usr/src/linux/Image /vmlinux.96c+"?

   Will getting the right kernel image loaded (please help me do this!)
   fix the $%@! problems with the ps96b package? Remember, I can't build
   the kernal now without fixing problem (1), but I did successfully do
   so yesterday. I may not be loading the kernel I made yesterday, though.

Good News Dept: I'm getting 4 more Megs of RAM tomorrow (brining me to
8 total), and by Sunday I should have an almost-new 120Meg HD installed,
solely for Linux!

Nick "the dilemma: Linux or sleep"

-- 
|  Nick Vargish       | "I'm just another wide area network packet-herder..." |
|  SURAnet Operations +-------------------------------------------------------+
|  vargish@sura.net   | "SURAnet  and I do  not have a  relationship based on |
|  h: 301 474-1863    | mutually-shared ideologies.  Don't assume otherwise." |
Newsgroups: comp.os.linux
From: chad@src.umd.edu (R Michael McMahon)
Subject: Protoize uploaded to tsx-11.
Organization: Systems Research Center, Maryversity of Uniland, College Park
Date: Sat, 25 Jul 1992 16:47:05 GMT

I've uploaded in binary and source the protoize/unprotoize utility which
comes as part of GNU's gcc-2.2.2 distribution from athena (but not with
hj's port). For those who don't know, this program takes K&R code and 
creates protoyped/declared ANSI C source, which I find much more readable
and less error-prone due to ANSI type checking. 

Only programmers who've *never* made an argument-passing error may 
flame me for that last statement.

R Michael McMahon		chad@src.umd.edu
Newsgroups: comp.os.linux
From: kk@cs.tu-berlin.de (Kolja Kaehler)
Subject: xfig compiled ?
Organization: Techn. University of Berlin, Germany
Date: Fri, 31 Jul 1992 13:46:52 GMT

Did anybody manage to get xfig up and running ? Compilation worked fine
(well, mostly... I'd really like to know the difference between free() and
cfree()!). But when run, drawing doesn't work correctly:
Whenever I draw a figure, the first point is set somewhere *very* far
off the right border of the window, which results in horizontal lines from
the 2nd point to the right. This is true for all figures which are built
from lines, circles seem to work.
Usually, the program crashes with a SEGV after some more helpless attempts
to bring a mere box onto the screen... (BTW, the resulting xfig.SAVE contains
correct coordinates for the figures)

Any suggestions ?

	Kolja
-- 
------------------------------------------------------------------------------
Kolja Kaehler                                            <kk@cs.tu-berlin.de>
From: thoth@uiuc.edu (Ben Cox)
Subject: Re: vt100 lines character set
Originator: btc30679@uxa.cso.uiuc.edu
Reply-To: thoth@uiuc.edu (Ben Cox)
Organization: University of Illinois at Urbana
Date: Fri, 24 Jul 1992 21:33:26 GMT

hyvatti@klaava.Helsinki.FI (Jaakko Hyvatti) writes:

>  So, in shell type

>bash$ echo <ctrl-V><ctrl-O>

>  or just press <ctrl-V><ctrl-O><enter> to output a ^O character.

...but this could run you into trouble if you have a command named ^O.

:-) :-)

--
Ben Cox
thoth@uiuc.edu
Newsgroups: comp.os.linux
From: bjl@sif.pttrnl.nl (Ben Lippolt)
Subject: Re: say goodbye to shoelace
Reply-To: B.J.Lippolt@research.ptt.nl
Organization: PTT Research
Date: Wed, 22 Jul 1992 07:53:48 GMT

thoth@uiuc.edu (Ben Cox) writes:

>pmacdona@sol.UVic.CA (Peter MacDonald) writes:

>>With the addition of the DOS FS, the kernel has grown to over 
>>256K, which, if my memory serves me correctly,  was the max 

>If you don't compile in the SCSI drivers, it still slides in at >just<
>under 256k.

I don't use SCSI, but use the selection patch and a few other minor patches
and it is 260K. But I still use shoelace to boot. So what this about not
being able to use shoelace with kernels > 256K?


PS. I don't use shoelace as my primary boot program. For that I use pfdisk.

Ben Lippolt.
From: rcs82150@zach.fit.edu (Brian Gann /ADVISOR Clay)
Newsgroups: comp.os.linux
Subject: GWM - Motif Ported to Linux
Summary: X Window Manager (Generic)
Keywords: mwm Motif
Date: 30 Jul 92 10:14:42 GMT
Organization: Florida Institute of Technology, Melbourne USA

Just wanted to comment that I was able to compile the
gwm (Generic Window Manager) for Linux.  This diffs are minor.
I was then able to get the Motif Emulation up - NICE!!

The only problem you will have is in malloc.c and the much discussed
problem with bison/flex.. These don't work properly when 
building WOOL (Windows Object Oriented Language).  lex and yacc
work without a glitch.

BTW: I used lex & yacc on a NightHawk SYSV, as I haven't located
source code for the REAL versions.  I can upload the diffs
and the lex/yacc'ed files if requested.

Brian K. Gann
rcs82150@zach.fit.edu

gwm is available at export.lcs.mit.edu in /contrib/gwm*

olvwm is nice, but mwm is certainly preferred!
From: tdunbar@vttcf.cc.vt.edu (Thomas Dunbar)
Newsgroups: comp.os.linux
Subject: Metafont graphic window geometry
Date: 30 Jul 92 03:40:30 GMT
Organization: Virginia Tech, Blacksburg, VA


If one is using MetaFont to draw pictures, etc., one runs it in proof mode
and a graphic window is created. the default is much too big. to change it,
in your .Xdefaults file, add:
    mf*Width:800
    mf*Height: 600
for example.
  this assumes mf is using the Xt version interface (as the version at 
archsci does). see x11-xt.c in the mfwindow subdir of the web2c.tar for
the code that controls this.
   thomas
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.os.linux
Subject: Re: find 3.7 and fileutils 3.3 uploaded
Date: 29 Jul 92 19:35:43 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

In article <dirkst.712335866@messua>, dirkst@messua.informatik.rwth-aachen.de (Dirk Steinberg) writes:

| I think it is a bad practice to upload static binaries. They are totally
| useless for anyone who does not want to waste massive amounts of disk space.
| I have both Linux 0.96cpl2 and 386BSD 0.1 installed on my 486 and I prefer
| to use LINUX because it is more efficient and faster and it has shared
| libraries (and because gdb-4.6 and X386-1.2E work). The shared libraries
| are the single most biggest plus in favor of Linux, especially when it comes
| to X.
| 
| We should always use the latest official gcc release shared images for
| uploading binaries. Starting from next release, these will be based on
| jump-tables anyway. If you really want, you can include /lib/libc.2.2.2

  But uploading binaries based on shared libraries makes them break as
soon as you upgrade your gcc. Your thought about .a files was better,
because gcc is relatively small, and you can trim the compiler and still
use the linker if you're all that tight for disk.

  The statement about "we should always use..." doesn't make sense
unless people are uploading stuff as a paying job. I would encourage
people to upload .a files if possible, or static linked files as an
alternative. I have a nice collection of files I've downloaded and which
don't work because I have gcc 2.2.2. Let's not add to the problem.

  BTW: how much os a hit does the library take on using the jump table?
Between the extra level of indirect, dumping the cache and pipeline
twice as often, and paging on small systems, this looks like a potential
5% increase in clock time. Do you have numbers? I see people taking the
compile time to use -O2 and a bunch of hand selected -f options to make
things faster, so performance hits of a percent or more are probably
going to be noticed.

  Note, I'm looking for clarification rather than saying "this is bad."
My guess of what it adds to small systems calls could be way off, etc.
I'm well aware of the benefits of jump tables, just concerned about
possible performance costs. Maybe the only hit is the extra pieline
dump, I suspect the table would be memory, if not in cache, all the
time.
-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
	It never ceases to amaze me that otherwise rational people, able to
	understand calculus, compound interest, and the income tax form, can
	continue to believe that poker is a game of chance.
Newsgroups: comp.os.linux
From: jrs@world.std.com (Rick Sladkey)
Subject: Re: New Emacs binary?
Organization: The World
	<1992Jul25.155555.8777@cs.brown.edu>
Date: Mon, 27 Jul 1992 02:04:33 GMT

>>>>> On Sat, 25 Jul 1992 15:55:55 GMT, wcn@cs.brown.edu (Wen-Chun Ni) said:

wcn> I successfully compiled Emacs 15.18 using gcc 2.2.2 after changing
wcn> some parameters. The major problems I've encountered  and can't
wcn> be solved up to now are:
wcn> 1. The suspended Emacs cannot recover the the terminal characterisics
wcn> after being resumed.

Use #define HAVE_TCATTR

wcn> 2. The M-x shell command doesn't work quite correctly no matter how
wcn> I change the method of interprocess communications.

Use #define HAVE_SETSID

wcn> The first problem also haunts the elvis binary I got from banjo so I
wcn> guess that there may be  bugs in the library. 

The problem is unrelated.  Stock elvis does not support suspending.

wcn> I also hack a little on emacs/lisp/term/at386.el to obtain a set of
wcn> elisp files suitable for Linux's virtual consoles. I myself don't
wcn> know whether there are people working on the version, but the source
wcn> I got from tsx-11 isn't a ported source because there remain alot
wcn> of works to be done when I was porting emacs.

The source on tsx-11 is the same as the that on prep.  My most recent
linux-specific patches are in

tsx-11.mit.edu:/pub/linux/sources/usr.bin.X11/x11emacs.patches

I will be releasing a new version that supports shared libraries shortly.
--
Rick Sladkey
jrs@world.std.com
From: james@netcom.com (James L. Paul)
Newsgroups: comp.os.linux
Subject: IRQs and 0.96c PL2. I'm still confused!
Date: 24 Jul 92 18:00:10 GMT
Organization: Netcom

I just got everything upgraded to 0.96c PL2. SLICK! Except...

I'm trying to use all 4 of my serial ports. I have 2 cards, each
with 2 ports. One card uses 2 16550 UARTs. I've tried various IRQ
setups, but haven't gotten things to work yet.

Right now I have:

COM1   IRQ 4
COM2   IRQ 3
COM3   IRQ 5
COM4   IRQ 2

When booting, Linux says that COM3 and COM4 have the same IRQs as
COM1 and COM2, respectively. Like this:

COM1   IRQ 4
COM2   IRQ 3
COM3   IRQ 4
COM4   IRQ 3

Linux does this no matter how I have the IRQs set up. Why, and how
do I fix it?

BTW, the first 2 ports work properly, but the last 2 don't, obviously.
I can send data out the port, but nothing can get in. I assume this IRQ
problem is at the heart of the matter.

Sorry if this is a FAQ, but I haven't seen it!

-- 
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: Jim.Corbett@f35.n152.z1.fidonet.org (Jim Corbett)
Newsgroups: comp.os.linux
Subject: Thanks
Date: Tue, 21 Jul 1992 05:20:01 -0800

Thanks for the netmail msg with the help installing GCC2.2.2
It made my weekend.  I can now help others that have had the same
problems 
cutting thru the confussion. 
 
 * Origin: Intermittent Connection  Eugene, OR (1:152/35)

Newsgroups: comp.os.linux
From: mj@dfv.rwth-aachen.de (Martin Junius)
Subject: Re: tlQ: where is arch for linux?
Organization: Communication Networks
Date: Thu, 23 Jul 1992 12:10:18 GMT

laakkone@klaava.Helsinki.FI (Tero Laakkonen) writes:

>hi, i'm trying to build a C++ class lib called La++. the source code
>comes with a Makefile that uses /bin/arch to display the architecture 
>of the machine.
>can somebody tell me where to find the sources for arch?

I'm using a very small script for this purpose:

/usr/bin/arch:

    #!/bin/sh
    echo "i386"

Martin
-- 
 _____ _____
|     |___  |   Martin Junius           FIDO:      2:242/6.1
| | | |   | |   Communication Networks  Internet:  mj@dfv.rwth-aachen.de
|_|_|_|@work|   Aachen U of Technology  Phone:     ++49-241-8790220 (voice)
From: as@prg.ox.ac.uk (Andrew Stevens)
Newsgroups: comp.os.linux
Subject: shutdown not doing so (solved)
Date: 29 Jul 92 07:25:13 GMT
Organization: Oxford University Computing Laboratory, UK

If, like me, you've been irritated by shutdown occasionally hanging
you may be interested to know the cause.   Basically, when shutdown
runs it uses /etc/utmp to figure out which tty's to send shutdown
messages to.   If /etc/utmp is messed up containing entries for
pty's with nothing attached (i.e. messily killed of xterm's and the
like) shutdown tries to write to these and hangs.   Various
work-around's are (1) always kill things off by hand before exiting X-windows,
(2) hack shutdown to ignore pty's (3) Zap the /etc/utmp file by hand
if shutdown hangs.

I haven't (quite) got the energy to figure out the ioctl's needed to
properly cure this problem.

Andrew
        Andrew Stevens                  
      Programmming Research Group       JANET: Andrew.Stevens@uk.ac.oxford.prg
     11 Keble Road, Oxford, England     UUCP:  ...!uunet!mcvax!ukc!ox-prg!as
     OX1 3QD   +44 0865 272563
Newsgroups: comp.os.linux
From: otto@nevada.edu (Frederick J. Haab)
Subject: Transfering files from floppy
Originator: otto@helios.nevada.edu
Organization: University of Nevada System Computing Services
Date: Fri, 24 Jul 1992 22:29:16 GMT


Ok, it's me again, that new user.  I found all the sites
that carry linux stuff, thanks to all who replied.  I can
use linux's kermit to download the smaller things.  At
school, I can use a sparc station to copy the bigger things
to a floppy disk.

How do I transfer this to my hard disk at home?
Should I:
	Use dd, then tar xzf, like the installation disks?
	Copy to disk in msdos format, then how do I read them?

Please keep in mind that I haven't tried anything yet, so if
this sounds like a stupid question, please don't grumble...no
matter how much of a guru you may be now, you were a beginner
at some point 8^).

-Fred again
Newsgroups: comp.os.linux