HDTenEightyP/NetNews huggingface dataset:
From: danubius@halcyon.com (Joseph R. Pannon)
Subject: Corrupt 'tar' man page
Organization: Northwest Nexus Inc. (206) 455-3505
Date: Sun, 10 Jan 1993 03:49:26 GMT

I have already alluded to this problem in a message dealing with Seyon,
hoping to kill two birds with one stone.  Well, that didn't work, so let
me target a single bird this time. ;-)

I am running the SLS 0.99 linux installation successfully, but I noticed
that the tar man page is corrupted. There may be some others, but I
don't remember which ones.  Anyway, when I run the 'man tar' command, I
get a text which starts out like this:

\input texinfo @c -*-texinfo-*-

@setfilename tar.info
@settitle The @code{tar} Manual: DRAFT
@ifinfo
This file documents the tape archive of the GNU system.

Copyright (C) 1988 Free Software Foundation, Inc.

Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
preserved on all copies.

@ignore
Permission is granted to process this file through TeX and print the
results, provided the printed document carries copying permission
notice identical to this one except for the removal of this paragraph
(this paragraph not being relevant to the printed manual).

@end ignore
Permission is granted to copy and distribute modified versions of
this manual under the conditions for verbatim copying, provided that
.... etc., etc.


Can other SLS 0.99 installers verify if they have the same problem, or I
am the only one?  Can anybody recognize what format this text file is in
and how it might have gotten produced -- and possibly how I could fix
this?  This text is, BTW, the content of the /usr/man/cat1/tar.1 file
and there is no corresponding /usr/man/man1/tar.1 file.

Thanks, 
Joe Pannon
Newsgroups: comp.os.linux
From: esaffle@gmuvax2.gmu.edu (Ed Saffle)
Subject: gcc executables size of net02 stuff
Organization: George Mason University, Fairfax, Virginia, USA
Date: Tue, 12 Jan 1993 19:25:53 GMT

Hi folks,  I have just recently decided to go around grabbing source to
stuff I use in case something breaks or something happens to my filesystem,
etc.  The first thing I checked out was the net02 stuff.  I have the binaries
installed, but nslookup puts its help file in an odd place (to me, anyway) and
I wanted to re-compile it with a new location in mind.  However, everything I
compile is pretty big.  How did they get the net-bin binaries that small
compared to my compiled net-src version?
  Also, where can I pick up the docs for the latest gcc?  Ascii is tolerated,
but tex/ps would be VERY nice... :)

Ed
From: randy@kcin.alphacdc.com (Randy S. Welch)
Newsgroups: comp.os.linux
Subject: Re: Need help buying a SCSI host adapter
Date: 9 Jan 93 07:57:40 GMT
Organization: Randy's own unix box..

In article <1993Jan7.215033.11186@ncar.ucar.edu> kuehn@citadel.scd.ucar.edu (Jeff Kuehn) writes:

   the Adaptec 1742 or the UltraStor 24F (EISA bus masters) look good.
   are either of these supported by the current set of drivers?
   will they be supported in the future?
   how do they perform?
   what would you recommend instead?

Well a few comments based on my initial install of SLS on a Dell 466DE.
It has the adaptec 1742 card in it.   The adaptec card must be in enhanced
mode in order for linux to come up.   But it seems to work reasonably
well, only some real simple tests shows that it runs quite nicely.

I had tried booting linux on a Gateway 2000 486/33 EISA tower
configuration with an Ultrastor 24F and linux failed to see it at all, and
SCO 3.2.4 had the worst time with it, enough for us to send the Utrastor
back to Gateway for the adaptec.  Now one thing that  I noticed when
installing SLS, was that the Adaptec card needed to be out of enhaced
mode, otherwise the kernal used on the a1 disk would not see the
controller.

Now if anybody could tell me if the HP EtherTwist ( 32?) ( it's and EISA
ethernet card ) is supported under Linux, I would be most apprecative.
And if so do I have to upgrade the kernal? ( is the SLS on tsx-11 0.99
based or 0.98, it seems to have a split personality... )

Plus could anybody comment on the Extended file system provided with SLS,
is it stable enough for several devlopers to work on?

And one last note:

Thanks to all of you who have made Linux in all it's forms possible.  When
I buy a PC it will be to run Linux on.  Plus Linux is able to do something
that SCO can't, and that's running on a fast 486 ( 33Mhz+ ) , give
yourselves  a pat on the back and a virtual beer or two :-)

-randy
--

-- 
Randy Welch   also known as..       (home) randy@kcin.alphacdc.com
Boulder, CO                           or   randy%kcin@csn.org
"MS-DOS is to computing as the      (uucp) {csn,scicom}!kcin!randy
 black plague was to Europe" - NH   (at&t) (303) 442-6717
Newsgroups: comp.os.linux
From: fingon@pcuf.fi (Markus Stenberg)
Subject: Re: Problem Installing Linux
Organization: The PC-users of Finland
Date: Wed, 6 Jan 1993 14:59:39 GMT

Yes, read FAQ.
 
fdisk /dev/sda - ?
<Fdisks scsi-drive 1>
From: bryanw@rahul.net (Bryan Woodworth)
Newsgroups: comp.os.linux
Subject: Re: What video card is good for Linux, OS2 and MS-Windows?
Date: 7 Jan 93 21:12:54 GMT
Organization: a2i network

In <ow9ywB1w165w@pwong.tdkcs.waterloo.on.ca> pwong@pwong.tdkcs.waterloo.on.ca (P.Wong) writes:

>I have purchased SpeedStar 24x couple months ago and it is a good card
>for MS-Windows. However, I could not get the card to work in resolution
>higher than 640x480 on Linux and OS2. I was going to wait for the drivers,
>but I figure by the time the drivers become available, my 486/50MHz would
>have been obsolete. Right now I am looking for a video card which is
>supported by Linux, OS2 and MS-Windows. Would anyone please tell me what
>video cards are good to be considered? The price range is < $400.

Your system sounds perfect for a ATI Graphics Ultra Plus.  The Pro is a few
hundred more, and you don't really get your money's worth.  But the Plus is
a value.

In Windows, there are drivers for up to 16bit color to 1024x768.  24bit
drivers are being worked on, but don't count on much, 24bit color will be
SLOW.  the GUP is an accelerated card, and works quite fast even in 16bit
color.  In fact there is virtually no decrease in speed when you switch
from 256 colors to 16bit color, since the card is accelerated up to 16bit.

I don't know about OS/2; I don't think there are many good drivers.  ATI is
not really supporting OS/2 until they see how much of a presence in the
marketplace it has.  This is my personal opinion. But then, I don't give a
fiddle about OS/2, so it wasn't something which influenced my decision.

As for Linux, I am able to run in 800x600x256 colors, and it is very peppy
on screen draws and so forth. The only problem is, my computer is an
underpowered 386/25 and you need a 486 probably to get fast graphics
viewing (for gifs, etc.).

so, for Linux and Win, I recommend the ATI Graphics Ultra Plus.  It is
around $319 from USA-Flex, but they are on backorder now.  Best of luck, it
is a very good and popular card and most places are out of stock now.  Just
use the time waiting to see if you can find a better card ;-)

-- 
Bryan Woodworth <bryanw@rahul.net>
Newsgroups: comp.os.linux
From: andrewc@aurora.cc.monash.edu.au (Andrew J. Cosgriff !)
Subject: Re: Getting talk, telnet, ftp to work
Organization: Monash University, Melb., Australia.
Date: Tue, 5 Jan 1993 08:25:00 GMT

djr48312@uxa.cso.uiuc.edu (Dennis Robinson) writes:

>I've grabbed sls .99-1.  I also grabbed talk, and talkd.  I have no directoin
>in which to go now in getting talk, telnet and ftp to work...  Even in
>loopback mode.  The faq is simply not detailed enough in these areas, it
>assumes you have a network card.  ANy help is GREATLY appreciated.


I didn't have any problems with the FAQ, and I don't have a network card !

Besides that, you didn't actually say what was going wrong - how are we meant
to help if you don't tell us what's wrong ?

The SLS tcpip does work, by the way, so something's been stuffed up somewhere
 - have a bit of a play with it first, *then* come back and say *exactly* what
happened and then you might get some help.


Happy hunting !

Cos !
-- 
-------------------------------------------------------------------------------
 * Andrew J. Cosgriff ! *                   #include <std_witty_quote.h>
#define HERE cc.monash.edu.au               #include <std_disclaimer.h>
Hassle me at :      andrewc@aurora.HERE ; andrewc@lindblat.HERE ; cos@yoyo.HERE
From: hlu@luke.eecs.wsu.edu (H.J. Lu)
Newsgroups: comp.os.linux
Subject: Re: correction to release.libc-4.2 notes
Date: 5 Jan 93 08:27:03 GMT
Article-I.D.: serval.1993Jan5.082703.16846
Organization: Washington State University!

In article <1993Jan5.025748.10858@afterlife.ncsc.mil> jepstei@afterlife.ncsc.mil (John Epstein) writes:
>If you already have a version of libc.so.4.2 the instructions cause
>libc.so.4 to disappear --- I actually recovered without using bootdisk.
>by mcopy to floppy and mcopy to /lib since my mcopy didn't use libc.so.4
>
>BTW: It might be nice if ln was -static so ln -sf always available!!!
>
>The problem with the instructions is:
>
>cp libc.so.4.2 libc.so.4.2.old --> libc.so.4.2.ol for 14 char minix file system
>the next line is
>ln -sf libc.so.4.2.old libc.so.4 --> generates a 15 char symbolic link
>
>I thought this would work as identical for first 14 char
>
>My system died on the mv libc.so.4.2 foo
>
>I am running linux-0.99 pl 1 prior to begin of libc-4.2 and gcc-2.3.3
>
>John

This is the real fix for jump-4.2.TZ.

H.J.
-----
*** /tmp/Makefile	Tue Jan  5 00:20:57 1993
--- shlib/jump/Makefile	Tue Jan  5 00:24:13 1993
***************
*** 396,402 ****
  	done
  	# The following is necessary because the "text file" may be active.
  	-if [ -f $(IMAGEDIR)/$(CSHLIB) ]; then \
! 	  mv $(IMAGEDIR)/$(CSHLIB) $(IMAGEDIR)/$(CSHLIB).old; \
  	fi
  	cp $(CSHLIB) $(IMAGEDIR)
  
--- 396,406 ----
  	done
  	# The following is necessary because the "text file" may be active.
  	-if [ -f $(IMAGEDIR)/$(CSHLIB) ]; then \
! 	  cp $(IMAGEDIR)/$(CSHLIB) $(IMAGEDIR)/libc.so.old; \
! 	  if [ -f $(IMAGEDIR)/$(CLOADSHLIB) ]; then \
! 	    ln -fs $(IMAGEDIR)/libc.so.old $(IMAGEDIR)/$(CLOADSHLIB); \
! 	  fi
! 	  rm -f $(IMAGEDIR)/$(CSHLIB); \
  	fi
  	cp $(CSHLIB) $(IMAGEDIR)
  
Newsgroups: comp.os.linux
From: gdm@shrdlu.kwnet.on.ca (Giles D Malet)
Subject: Re: UUGETTY & Lock files...
Organization: 3.141592653589793238462643383279502884197169399
Date: Thu, 7 Jan 1993 16:45:53 GMT

In article <C0EFGJ.706@jti.com> richb@jti.com (Richard Braun) writes:
>
>My version of kermit uses binary PIDs so I had to change
>and recompile uugetty to do likewise.

A word of warning - the binary version of kermit doing the rounds is
`wrong' in using binary PID's. I say `wrong' because all software has
to agree on a format, and since the dark ages kermit has used straight
ascii. uucp, uugetty, and various other programs all use ascii as well.

You should be fixing kermit, and now your uugetty, else the following can
happen : uucp starts using the line and writes an ascii lock.  You fire
up kermit, it reads the lock as binary, gets a PID about 15digits long,
can't find that process, assumes it is dead, removes the lock and also
tries to grab the line.... Next cron fires off a uucico which reads the
binary file as ascii, ..... and grabs the line. Next uugetty wakes up,
looks around... and grabs the line.
I'll stop now - I'm breaking out in a cold sweat.

Also, ascii lock numbers are easliy readable by scripts and humans.

This is going to cause problems and more volume in the newsgroup if that
kermit is not fixed !

-- 
Giles D Malet                                             gdm@shrdlu.kwnet.on.ca
Waterloo, Ont, Canada       +1 519 725 5726       gdmalet@descartes.uwaterloo.ca
Newsgroups: comp.os.linux
From: fingon@pcuf.fi (Markus Stenberg)
Subject: Re: Linux v. Coherent: Comments
Organization: The PC-users of Finland
Date: Wed, 6 Jan 1993 14:55:50 GMT

Remember - these are only my opinions regarding Linux & Coherent.
 
At first I tried Coherent. It looked nice, installed easily, but
had some problems w/ my SCSI-drive. But then I tried to compile some
of UNIX sources I've got. NO SUCCESS! I succeeded in compiling only
really bare-bones software.
 
Linux: Installation was bit harder, but no problems overall. Only
annoying thing was that I had to boot from disk - haven't yet
tried LILO. Compiling of sources was more successfull, and so far
over 50% of non-Linux sources have worked with only little modifications,
and some just out-of-the-tar.Z. 
 
Of course Linux has it's problems too, but I recommend it. Free,
and new versions arrive quite often.
From: probreak@matt.ksu.ksu.edu (James Michael Chacon)
Newsgroups: comp.os.linux
Subject: Re: SLS's tcpip - doesn't work for me !
Date: 8 Jan 1993 16:23:49 -0600
Organization: Kansas State University
NNTP-Posting-Host: matt.ksu.ksu.edu

pfr@psun2.hmi.de (Fritsch_Wolfgang) writes:

>In view of all the apparent frustration by the maintainers of faq's and
>doc's I feel bad about it, but still I cannot get tcpip to run.

>Someone hinted to me that 'define' the host name means a command
>'hostname <hostname>'. I did that and indeed, now the install.net
>script inserts my hostname where it used to have 'softland' before.
>But alas, next time I boot there is again 'softland' for hostname!
>So. how can I make my hostname permanent, please? I may have more problems
>but there is no hope before I can clear this one.

>Besides, I refuse, to this point, to 'compile' anything because I don't want
>to get into trouble with gcc. Personally I will never make use of gcc for
>my work. So I changed the settings of my WD8013 card to the default values,
>assuming that this is a valid approach. (the description which comes with
>the SLS package mentions changing parameters in linux/net/Makefile but truely
>I cannot find this path/file anywhere on my disk).

>Wolfgang Fritsch
>pfr@psun2.hmi.de

Try looking through all the other boot files and see if softland gets set 
there. Also, change your /usr/etc/inet/hosts table to reflect your new
name as well.

I don't see how you can expect to have a unix style system running and never
have to compile anything. The file you mentioned not being able to find is
in the kernel source. In order to make those changes you will have to recompile.
I really don't see the problem with using the compiler. How would you
"get into trouble with gcc"? This compiler has been stable and running fine
for close to a year now.

James
Newsgroups: comp.os.linux
From: janl@ifi.uio.no (Jan Nicolai Langfeldt)
Subject: Re: Gcc 2.3.3, gcc 2.2.2d and -V
Organization: Folkeaksjonen for gjeninsettelse av Revolvermagasinet
Date: Thu, 7 Jan 1993 11:42:35 GMT
Originator: janl@maud.ifi.uio.no


In article <1993Jan6.232818.1544@ifi.unizh.ch>, amir@avalon.physik.unizh.ch (Guindehi Amir) writes:
> gcc: installation problem, cannot exec cpp: No such file or directory
> 
> Thats curious ! Both cpp correctly reside in /usr/lib/gcc-lib/i386-linux/2.2.2d
> and /usr/lib/gcc-lib/i486-linux/2.3.3 and have the correct flags. I have
blah,blah,blah

Read ****ing news man! (yes, when running a un*x box your're supposed
to be super human and remember everything you read :) I posted the
answer a few days ago, do like this:

  cd /usr/lib/gcc-lib/i486-linux
  ln -s ../i386-linux/* .

Nicolai
-- 
Nicolai Langfeldt, "Bugs made while you wait"
Internet: janl@ifi.uio.no
Newsgroups: comp.os.linux
From: kfisher3@mach1.wlu.ca (kevin fisher U)
Subject: Re: SLS update: gcc 2.3.3, libc4.2, etc
X-Newsreader: TIN [version 1.1 PL6]
Organization: Wilfrid Laurier University
Date: Tue, 12 Jan 1993 12:25:04 GMT


Um, what do you mean when you say that upgrading current systems is a
problem??  Will I have to wipe everything and start over, or what?

just curious,

-- 
--------------------------------------------------------------------------------
Kevin Fisher  ><> 	|  "Thank you.  You can't believe everything you
kfisher3@mach1.wlu.ca   |  see and hear, can you?" - Hendrix, 'EXP'
________________________________________________________________________________
From: root@magoo
Newsgroups: comp.os.linux
Subject: mail over smtp
Date: 8 Jan 1993 14:59:23 -0600
Organization: UTexas Mail-to-News Gateway
NNTP-Posting-Host: cs.utexas.edu

Hi all,
 Well somehow I managed to get the dern thing working. Mostly it was in the
sendmail.cf file, which I hacked and hacked. Its hard when you're not sure
of what you are doing. It all started working when I shipped over the
sendmail.cf file from our next machine. Now if I could only get incoming
mail to work. sigh...

-- 

Patrick L. McGillan
Computer Systems Specialist
University Of Wisconsin     Ph:  (715) 394-8191
Superior, Wisconsin         pmcgilla@magoo.uwsuper.edu

Linux is the only way to go!!!

Newsgroups: comp.os.linux
From: evansmp@uhura.aston.ac.uk (Mark Evans)
Subject: Re: Anyone working on diskquotas and acl's?
Organization: Aston University
X-Newsreader: TIN [version 1.1 PL241235]
Date: Tue, 12 Jan 1993 21:10:30 GMT

khockenbury@vaxc.stevens-tech.edu wrote:
:     I was wondering if anyone was working on diskquotas and acl's
: (access control lists) for Linux.  I know there were old (.96?)
: diskquota patches, but is anyone working on it currently?  ACLs are
: used for finer file control than the standard unix "ugo" stuff, and
: both are features of many "modern" unix os's (AIX, HP-UX). 

Also is any support needed when a file system is mounted from an
NFS server where quota's are enabled?

--
-------------------------------------------------------------------------
Mark Evans                                   |evansmp@uhura.aston.ac.uk
+(44) 21 429 9199  (Home)                    |evansmp@cs.aston.ac.uk
+(44) 21 359 6531 x4039 (Office)             |
From: rcopg@minyos.xx.rmit.OZ.AU (Paul Gortmaker)
Newsgroups: comp.os.linux
Subject: Re: /usr/include/linux/<missing.h>
Date: 12 Jan 93 03:18:55 GMT
Organization: RMIT Computer Centre
NNTP-Posting-Host: minyos.xx.rmit.oz.au

jliddle@rs6000.cmp.ilstu.edu (Jean Liddle) writes:

>In article <1993Jan9.110222.4284@exucom.com> kjv@exucom.com (Karl J. Vesterling) writes:
>>
>>	Where do I get the files that are in, "/usr/include/linux/*"
>>They weren't in any of the SLS disks, or the GCC distribution on
>>TSX-11...
>>
>>	Things don't like to compile without them.
>>

>Get the sources to the latest kernel 0.99.2.  Place them in 
>/usr/src/linux, and make the following 2 links:

>ln -s /usr/src/linux/include/linux /usr/include/linux
>ln -s /usr/src/linux/include/asm /usr/include/asm

	I had trouble with the symlinks ending up in the wrong place when
using the above (even with the -f switch) when I tried to upgrade from
98p5 to 99p2. ln did not like the fact that the target already existed.
Here's what I did to get around it

mv /usr/include/linux /usr/include/Linux
mv /usr/include/asm /usr/include/Asm
( save these for future reference ??? - suppose could rm -rf /usr/include/linux
and rm -rf /usr/include/asm)
...and then make the symlinks.

Make sure you do BOTH, the ./linux and the ./asm -- if you don't do the ./asm
the kernel will still compile with the unpatched asm code, and will lock up 
during boot up.

Then all you have to do is get ps and top to work.  ;-)


							Paul.
Newsgroups: comp.os.linux
From: ado@ibg1.ibg.sub.org (Christoph Adomeit)
Subject: SLS, why don't you use gzip for compression ?
Organization: ibg
Date: Tue, 12 Jan 1993 18:55:46 GMT

Hi SLS-Makers,

why don't you use gzip for compression of your Disks ?
As long as gzip is on the distribution I don't see any compatibility-
problems.
I benchmarked gzip a little and found out that eg : gcc-2.3.3-source
has an original size of    : 19901952 bytes
compressed with "compress" :  7350491 bytes
compressed with "freeze"   :  5761878 bytes
compressed with "gzip"     :  5076738 bytes

This is about 30 % saving versus "compress".
(Might be fewer with binaries)
Imagine how many Gigabytes of SLS are blown through the net every day,
how many disks are written every day and how many Millions of Dollars
have to be paid for this.

It would really be a great saving.
Bye 
	Christoph
-- 
Origin: It's not a bug, it's a feature !
Newsgroups: comp.os.linux
From: wto@cbnewsg.cb.att.com (William T. O Connell)
Subject: Re: problem with Seyon
Organization: PC peripheral operational services group
Date: Tue, 12 Jan 1993 01:04:23 GMT

In article <C0opyt.5p0@dei.unipd.it> beppe@sabrina.dei.unipd.it (Giuseppe Zanetti) writes:
>Hi linuxers,
>
>I have Seyon 1.6 (binaries for linux found in the official seyon site at mit),
>it works well, but i have a problem with overlapping buttons (toggles) in
>the set windows (and in another window that i do not remeber).
>
>can anyone help me

Ensure that the application defaults file 'Seyon' was copied
to /usr/X386/lib/X11/app-defaults. The latest version of seyon
puts it in the right place. The previous version, when installing
Seyon, put it in /usr/lib/shlib/jump/app-defaults -or- something
like that.

Muhammad keep up the outstanding work on seyon!

- Bill
From: Craig.McCracken@f19.n375.z1.fidonet.org (Craig McCracken)
Newsgroups: comp.os.linux
Subject: efsck: bad magic number in super-block, boot manager's fault?
Date: Mon, 04 Jan 1993 19:57:00 -0800

 > but I wonder if anyone has had problems with Boot
 > Manager and how they
 > get it to work, there must be some reasons why people
 > call it the Boot
 > Mangler.  ;-)  I'd appreciate any help.

I'm pretty sure if you run the fdisk that came with OS/2 it will tell
you that BootManager should be the first partition on your drive. Makes
sence to me as the boot sector is track 0 . I have Os/2 and Linux setup
here with boot manager and it does recognize Linux if BootManager is set
up as the very first partition.

What I did was install OS/2 first with BM and followed the instructions
in the OS/2 manual for setting up multiple OS's on the box. Then I
installed the 0.98pl5 SLS version. The Linux fdisk faithfully reported
the correct partitions so all that was left was to mkfs and swap disks !
:) It did take me three time though to get my brain working properly and
get Linux on-line.

Hope this helps some !

Craig

 * Origin: The Com Port RA/FD/TS (205-260-9904) (1:375/19)
From: stern@amath.washington.edu (L.G. "Ted" Stern)
Newsgroups: comp.os.linux
Subject: Re: SLS, etc
Date: 10 Jan 93 18:58:55 GMT
Article-I.D.: shelley.1iprlfINNkef
Distribution: world
Organization: University of Washington, Applied Mathematics, Seattle
NNTP-Posting-Host: glacier.amath.washington.edu

In article <wHX5wB1w165w@mintir.new-orleans.la.us>, 
           craig@mintir.new-orleans.la.us (Craig Johnston) writes:

|> Peter, thanks for all the work on SLS...I flamed a bit earlier about
|> things not working, so now I would like to be a bit more constructive...
...

|>         What would be the possibility of 2 distributions, one on which 
|> everything def. works, and one "latest 'n greatest" one?  Is there 
|> perhaps something like this on some FTP site other than tsx-11? 

I heartily second this motion!  Especially once Linux 1.00 comes out!  I am
willing to wait up to a month or two for a *really* stable 1.00 SLS :-).

....

|>  
|> Craig Johnston

I also second the thanks to Linus, Larz, Peter, and the hundreds of other
diligent workers on this project!

-- 
 ==========================================================================
  L.G. 'Ted' Stern    ---       Mostly a Grad Student Peon . . .
  stern@amath.washington.edu
  lstern@orville.nas.nasa.gov
From: nation@dopey.sanders.lockheed.com (Robert Nation)
Newsgroups: comp.os.linux
Subject: HJLu boot/rootdisk has 1.9Mbytes on floppy, how?
Date: 7 Jan 93 14:16:27 GMT
Distribution: comp.os.linux
Organization: Lockheed Sanders, Inc.

I was studying the HJ Lu boot/rootdisk and the SLS a1 disk with
an eye to making a goot boot/root floppy that runs entirely in
a ramdisk and could be used to repair/restore HD problems. I noticed
that, after putting far fewer files on my floppies than H.J. Lu or
SLS a1, I ran out of space, but then du -s * on H.J. Lu's 98.5 boot
root disk showed that it had almost 1.9Mbytes of data, while
df showed that it was a 1.44 Mbyte filesystem. How is this
accomplished?

Is there some space-saving procedure for minix-formatted floppies?

Rob Nation
nation@rocket.sanders.lockheed.com
Newsgroups: comp.os.linux