HDTenEightyP/NetNews huggingface dataset:
From: lye@fraser.sfu.ca (William Michael Lye)
Subject: Re: Non-destructive repartitioning (was Re: What is linux?)
Organization: Simon Fraser University, Burnaby, B.C., Canada
Date: Thu, 9 Apr 1992 15:29:33 GMT

anthony@cae.wisc.edu (Anthony Frey) writes:

>In article <1992Apr4.192714.12174@rice.edu> adam@owlnet.rice.edu (Adam Justin Thornton) writes:
>>Using pfdisk, it's actually not that bad.  Use a disk optimizer to put all your
>>stuff on the front of the disk.  Use pfdisk to create your partitions, making 
>>sure that the DOS partition is bigger than all the stuff you now have in it.
>>If it's your boot partition, use Norton or something to edit the boot record so
>>that the whole filesystem believes it's the right size.
>>
>>Then boot from linux and mkfs on your new partition(s).  No problem.
>>
>>Adam
>>

>Hi everyone,

>I think this non-destructive partitioning is the route I want to take. I've
>done most things up to the point of running pfdisk and I feel fairly confident
>of what I'm doing but there's one thing that's hanging me up. I guess this is
>kind of a DOS question but there's probably more repartitioning going on here
>than the average DOS newsgroup.

>I'm running DOS 5.0 and Norton for DOS 5.0 and the Norton optimizer reports the
>very last few clusters of the hard disk as being unmovable and owned by a file
>called 'image.idx'. I believe this has something to do with an extra copy of
>the DOS 5.0 boot image. The question is, does DOS absolutely need this file in
>that particular location, or might it possibly create a new image in the last
>few clusters of a new partion? If not, can this file be moved and how?

>I've got an extra 40meg free on my hard drive that's got Linux written all
>over it. Thanks! 
>-- 
>-----------------------------------------------------------------------------
>Anthony Frey
>anthony@cae.wisc.edu                          "Building stereotypes
>                                               for the 90's"

You can just delete this file.  It would be out of date once you do your
partition editing anyways.  Use "attrib -hr image.idx" to make the file
writable and visible, and then delete it.  Check your autoexec.bat file and
comment out the line that creates this file (probably mirror) until you've
finished re-arranging your disk.  Once you've done your magic, and made sure
that everything is working ok (use NU to write garbage to the last logical 
sector of the new, smaller partition, and then use absolute sector read to
find it and check your math is correct) you can remove the comment.  One
thing in the original message you should know about.  If you've got multiple
DOS partitions, only one of which is bootable, you should know that all
partitions have boot code in them even if it is code that says "Non-system
disk" or something similar.  You'd have to massage the sector count in all
partitions' boot records.

Good luck!



-- 
Bill Lye, lye@sfu.ca
SFU claims these views....NOT!
Newsgroups: alt.os.linux
From: tree@midget.towson.edu (Denise Tree)
Subject: GCC2.1
Reply-To: tree@midget.towson.edu (Denise Tree)
Organization: The Internet
Date: Mon, 13 Apr 1992 12:20:35 GMT

I know this has been asked before, but I have been unable to find a definative
reply...............

??????????? When I try and compile a trivial program with gcc2.1 I get <stuff>
"parse error before (".
I installed according to the FAQ on a new system that I had never used 1.4 on
before. That is I:
                   1. untarred 2.1 misc (z switch does not work on my tar)
                   2. did same for 2.1lib
                   3. ditto for binutils
                   4. ran inst2.x and received success confirmation.
Are there any more doodads to do before GCC2.1 will fly? 
I have seen posted that tar not working correctly for some... is the fact that
the "z" switch does not work an indication of this? and if so which dist.
copy of tar is KNOWN to be OK?

...............................HELP!........................................
Denise Tree
Towson State Univ.
"lone Linuxoid in a sea of Windows "users""
Newsgroups: alt.os.linux
From: drew@caesar.cs.colorado.edu (Drew Eckhardt)
Subject: Re: IBM PS/2 Model 70
Organization: University of Colorado at Boulder
Date: Mon, 13 Apr 1992 13:09:40 GMT

In article <VFq3iB4w164w@pdnfido.fidonet.org> erik@pdnfido.fidonet.org (erik vanriper) writes:
>Hello all!  
>
>        I have a "half a computer" at work that I have tried to boot up with 
>Linux (0.95c) on a floppy, but to no avail.  I get the initial "loading", 
>get to the screen asking me what video mode I want, (does not matter what I 
>enter at this point), and everything dies.  
>
>        If anyone has any suggestions, I would appreciate it.
>

As far as I can tell, the only differences between Microchannel and 
ISA as far as systems software is concerned are the way interrupts are 
handled, and IRQ lines assigned to serial ports.

ISA uses edge triggered interrupts, with IRQ lines tristated.  This 
is somewhat braindead, as multiple devices cannot share the same IRQ line.
If drivers are enabled on more than one, and one goes high, the other
remains low.... they short each other out.  

MCA did interrupts right, and does level-active interrupts, with 
IRQ lines open collector.  Multiple devices can pull an IRQ low,
and IRQ lines can be shared.

Serial ports  :

Everything after COM2: shares the same IRQ line, even or odd.


These changes should be quite trivial - you will need to change the 
8259 PIC programming to be level triggered, rather than edge triggered.

If someone has a way to tell the difference between a MC PS/2 and an
ISA system, this could even be incorporated into the standard 
release with only a few lines of code.
From: ching@brahms.amd.com (Mike Ching)
Newsgroups: alt.os.linux
Subject: Re: Partitioning Warning!
Date: 13 Apr 92 21:46:52 GMT
Organization: Advanced Micro Devices; Sunnyvale, CA

In article <1992Apr12.151734.4845@donau.et.tudelft.nl> wolff@neuron.et.tudelft.nl (Rogier Wolff) writes:
>visnucc@ubvmsd.cc.buffalo.edu (Niagara U. Courtesy Account) writes:
>
>
>
>YEP happened to me too! DR DOS 6.0 recognizes MINIX and Linux partitions
>as if they are DOS 2.0 partitions, and will friendly as ever write format
>recover files to them, thereby destroying them.
>
>This is clearly DR DOS's fault. I won't use it anymore. (too bad for the
>extra 30M i'd get on my 30M partition, haven't bought/found Stacker yet...)
>
>
>						Roger
>-- 
>If the opposite of "pro" is "con", what is the opposite of "progress"? 
>	(stolen from  kadokev@iitvax ==? technews@iitmax.iit.edu)
>EMail:  wolff@duteca.et.tudelft.nl   ** Tel  +31-15-783644 or +31-15-142371


Seems like DRDOS thinks partition types are 7 bits since it called my
Minix partition (0x81) a DOS 2.0 partition (0x01). I'm going to use a
partition type < 0x80 for Linux to keep DRDOS happy.

Mike Ching
From: sh2v+@andrew.cmu.edu (Stephen Hathorne)
Newsgroups: alt.os.linux
Subject: Re: what does linux rhyme with?
Date: 14 Apr 92 13:12:57 GMT
	<1992Apr14.092142.26968@klaava.Helsinki.FI>
Organization: University Libraries - Library Automatio, Carnegie Mellon, Pittsburgh, PA


Yes Linus- This should be in the FAQ us silly americans think that people
might even be vain enough to include their own name in a product!

Sorry about that!


Stephen Hathorne
******************************************************
Computing Systems Administrator
Department of Statistics
Carnegie Mellon 
sh2v@andrew.cmu.edu                                  

/* comments are all mine */
******************************************************
Newsgroups: alt.os.linux
From: Epstein@DOCKMASTER.NCSC.MIL
Subject: Re: Binaries considered harmful
Reply-To: Epstein@DOCKMASTER.NCSC.MIL
Organization: The Internet
Date: Tue, 7 Apr 1992 22:09:53 GMT

Even source files can be harmful.  Since make requires being su on some
people's systems (-:  and lots of superusers use vi vice emacs when
logged in as root need to watch out for things like hlu's latest GCC ---
there is a .exrc in 2.1ps.tar.Z This caused grief when I did my first
download via kermit under Linux as I lose/garbage 1 out of the last 9
bytes of a binary file [FEATURE of the download process thru a 36 bit
machine] The uncompress and tar left a bad .exrc file in the ps
directory There should be no reason to be including .exrc files in the
GCC
                    John
Newsgroups: alt.os.linux
From: johnsonm@stolaf.edu (Michael K. Johnson)
Subject: kermit5A.tar.Z
Reply-To: johnsonm@stolaf.edu (Michael K. Johnson)
Organization: The Internet
Date: Sat, 11 Apr 1992 02:32:03 GMT

kermit5A.tar.Z at tsx-11.mit.edu was accidentally compiled using
shared libs, which has caused some trouble for some people :-)

A working (I beleive) version is now in
/pub/linux/binaries/usr.bin/kermit5A.tar.Z

michaelkjohnson
johnsonm@stolaf.edu
Newsgroups: alt.os.linux
From: johnsonm@stolaf.edu (Michael K. Johnson)
Subject: new stuff at tsx-11
Reply-To: johnsonm@stolaf.edu (Michael K. Johnson)
Organization: The Internet
Date: Fri, 10 Apr 1992 17:18:47 GMT

tsx-11.mit.edu:
/pub/linux/binaries/usr.bin/uucp-1.03-bin.tar.Z
			    xcomm.tar.Z (sz/rz comm package)
/pub/linux/sources/usr.bin/uucp-1.03-src.tar.Z

michaelkjohnson
johnsonm@stolaf.edu
Xref: sparky alt.os.linux:2467 comp.os.linux:387
From: bolsen@mcs213h.cs.umr.edu (Brian Olsen)
Newsgroups: alt.os.linux,comp.os.linux
Subject: Just plain questions
Keywords: gcc temp files and where to find TeX & groff guides
Date: 13 Apr 92 15:34:06 GMT
Followup-To: alt.os.linux
Organization: University of Missouri - Rolla


Hello!
Last night I decided to try some stuff out on Linux, so I started 
up three compile jobs at once with gcc2.1.  About 15 minutes into the
jobs, I started getting errors regarding the cpp temp files.
When I ran the jobs separately the programs went without minimal error.
Is this a problem with the kernel or with gcc keeping track off temp files?

Another question: 
Where is the best site to pick up a TeX and/or groff user's guide?

Brian
bolsen@cs.umr.edu
From: scfisher@oasys.dt.navy.mil (Fisher)
Newsgroups: alt.os.linux
Subject: Re: what does linux rhyme with?
Date: 14 Apr 92 16:04:38 GMT
Organization: Disorganization
X-Organization: (formerly David Taylor Research Center)

In article <1992Apr14.092142.26968@klaava.Helsinki.FI> torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds) writes:
|>In article <1992Apr13.183516.19064@ra.msstate.edu> dam1@ra.msstate.edu (Daniel A. Martin) writes:
|>>In article <7823@cayman.COM> pgf@cayman.COM (Paul Fox) writes:
|>>>
|>>>	Big question:
|>>>	
|>>>	Does "linux" sound like "linus" (i.e.  like "line" followed by "ux"
|>>>	which rhymes with "us"), or does "linux" sound almost just like
|>>>	"minix", which I assume people say the way they start "minimal"?
|>>
|>>Yeah!  I have been wondering about this too...
|>>I've been pronouncing in line-ux since that is how I would pronounce
|>>Linus...although pronouncing it like minix seems to make a lot of
|>>sense too...hmmmmm...I guess we need Linus to settle this :)
|>
|>Oh God. This comes up again :)
|>
|>No, linux doesn't sound like Linus - it's a short [i] sound, like in
|>mInIx or mInImal or prInt or ...  The reason isn't that I wanted it to
|>sound like minix, it's just the natural way to pronounce it (imho) in
|>Swedish.  Pronouncing it like "line"+"ux" is totally foreign to Swedish:
|>in that case I'd have written it "lainux".  So there.  Maybe this should
|>be in the FAQ :)
|>
|>		Linus

Gee, I thought it was for  Lion - ux, the Lion of Unix! :-)

-steve
Newsgroups: alt.os.linux,comp.os.linux
From: drew@romeo.cs.colorado.edu (Drew Eckhardt)
Subject: Re: Custom setups: RFD
Organization: University of Colorado at Boulder
Distribution: alt, comp
Date: Sat, 11 Apr 1992 08:02:47 GMT

In article <20053@castle.ed.ac.uk> eonu24@castle.ed.ac.uk (I Reid) writes:
>This article is posted as a "Request for Discussion" (RFD) although I
>realise at the outset that I may be alone in my viewpoint :-(. If I am
>then please feel free to send me a nice mailer telling me to shut up and
>stop wasting bandwidth. 
>
>The main bit
>------------
>
>Some facts:
>
>3. Different people want greatly differing things from Linux but above
>   all the consensus is that the kernel should be small and fast.
>
>
>So, putting these things together we come up against a problem....
>what should be "standard" in the Linux kernel and what should be
>optional. Take, for example, two different setups run on two different
>machines by two different people.
>

Everything should be standard, and on boot up should autodetect, and install
if the hardware needed to support it is there.  Yes, this is larger than 
a bare kernel, but one distribution will work for everybody until they
recompile or relink it with the options they want.


>2. A well documented configuration file to allow EASY changing of
>   setups and trouble free building of custom kernels. This should be
>   very wide ranging and should cover all possibilities.

Maybe a script file, like Larry Wall's Perl configuration script would 
be easier to use and more flexible, as it could configure Makefiles,
C source and header files transparantly to the end user.

>Some of this may be in 0.95c (haven't had a chance to look yet... I
>know the national keyboard selection is now done more sensibly) but I
>think anyone writing kernel level code should be aware that however
>wonderfull their code, there are those who need it and those who
>don't. Should needs change it should be easy to adjust things (by easy I
>mean a 1 (or so) line change in a master config file).
>
>Iain

You might take a look at what I did with the configuration files in 
the SCSI driver package - they consolodate all of the configuration
information in one config file, with a CONFIG_DISTRIBUTION that turns
on everything, and defaults that work for most systems.  

>patches for and installing ps. This was written for 0.95a not 0.95c
>                                                        ^         ^
>                                                        |         |
>                                     Please note________|_________|
>
>(which I haven't had a chance to look at yet) so buyer beware.
>

Just get .95c+, as it has the PS and lp patches already applied,
and they work beautifully.

Note that to correctly compile ps.c, you should make sure that 
the files in /usr/include/linux match those in /usr/src/linux/include/linux, 
and you should remove the -I flag from the Makefile.



Newsgroups: alt.os.linux
From: dam1@ra.msstate.edu (Daniel A. Martin)
Subject: Re: what does linux rhyme with?
Organization: Mississippi State University
Date: Mon, 13 Apr 1992 18:35:16 GMT

In article <7823@cayman.COM> pgf@cayman.COM (Paul Fox) writes:
>
>	Big question:
>	
>	Does "linux" sound like "linus" (i.e.  like "line" followed by "ux"
>	which rhymes with "us"), or does "linux" sound almost just like
>	"minix", which I assume people say the way they start "minimal"?
>
>	Enquiring minds want to know.   I certainly hope it's like "minix" --
>	it's much easier to say.
>
>	paul fox, pgf
>
>	no email please -- swamp the net.  :-)
>-- 
>		paul fox, pgf@cayman.com, (617)494-1999
>		Cayman Systems, 26 Landsdowne St., Cambridge, MA 02139

Yeah!  I have been wondering about this too...
I've been pronouncing in line-ux since that is how I would pronounce
Linus...although pronouncing it like minix seems to make a lot of
sense too...hmmmmm...I guess we need Linus to settle this :)
-- 
Danny Martin : dam1@Ra.MsState.Edu
Newsgroups: alt.os.linux,comp.os.linux
From: harlick@lindy.Stanford.EDU (Will Clark)
Subject: Re: IMPORTANT: gcc 2.1, libc.a 2.1a and Linux
Organization: Stanford University
Date: Tue, 7 Apr 1992 17:56:40 GMT

In article <1992Apr6.211500.7340@serval.net.wsu.edu> hlu@luke.eecs.wsu.edu (Hongjiu Lu -- Graduate Student) writes:
>Hi,
>
>I heard there were some problems with binaries linked with my new ld.
>That is caused by the new a.out.h introduced with Linus's second patch.
>The new a.out.h is compatible with the old one, But not vice versa.
>
>My new ld (binutils.tar.Z) uses the new a.out.h. The binaries
>linked by it can only run under the kernel with Linus's second patch,
>which has to be built by the old ld.
>
>Any programs using the old a.out.h, e.g., gdb, will not recognize the
>binaries linked by the new ld. You can either use the old ld or use
>the new version compiled with the new a.out.h.
>
>From Linus's second patch, we are moving to VFS. As a result, there
>will be some changes in libc.a. That means next release of gcc 2.x and
>libs will not run under the kernel below Linus's second patch to 0.95a.
>I strongly recommend you move to 0.95a with Linus's second patch if you
>haven't done so.
>
>H.J.


A plea from the C-impaired:  (Am I the only one using Linux?)

Someone please put a 0.95c boot image somewhere for FTP.

I am trying to learn enough about C to feel at least a little
comfortable with kernel patching.  I'd like to use gcc 2.1, but to do
that I have to patch the kernel ...

Will Clark (Baseball season is here!)
will.an@site007.saic.com
------------------------
SAIC does not share my opinions.
harlick@lindy is a friend's account, but you can send me email here, too.
From: tkendel@ernohb.UUCP (T. Kendelbacher OT133)
Newsgroups: alt.os.linux
Subject: What is LINUX?
Keywords: LINUX
Date: 11 Apr 92 09:53:41 GMT
Organization: Erno Raumfahrttechnik GmbH, Bremen, Germany

Can anybody please tell me what LINUX is?
Thank you for mailing or posting a short answer.

Thomas Kendelbacher  |  eMail : tkendel@ernohb.uucp
Robbenplate 13       |  voice : +49 539 5492
D-2800 Bremen 66     |     or : +49 57 04 37
Germany
Newsgroups: alt.os.linux
From: cummings@hammer.Prime.COM (Kevin Cummings)
Subject: Re: Binaries considered harmful
Organization: Prime Computer R&D
Date: Tue, 7 Apr 1992 20:58:44 GMT

In article <1992Apr7.201618.29108@muddcs.claremont.edu>, jwinstea@jarthur.claremont.edu (Jim Winstead Jr.) writes:
> I have the (as I know it) most current source for all of this, and
> I'll be uploading them as a package today (hopefully) to tsx-11, etc,
> and they should be available soon.  Look for system-0.95a.tar.Z.
> 
> Included:
> 	chsh	-	new to this release (change shell for a user)
> 	doshell	-	start a process on another tty
> 	fdisk-x	-	fdisk that understands extended partitions
> 	fdisk	-	the old fdisk
> 	hostname-	set your computer's name!
> 	mkfs	-	make a filesystem
> 	mknod	-	make a device
> 	mkswap	-	make a swap device/file
> 	mount	-	mount a filesystem
> 	passwd	-	change a user's password
> 	pwd	-	print working directory (from BSD)
> 	rootdev	-	display/change root device (rdev.c)
> 	setterm	-	set terminal characteristics
> 	swapon	-	use a swap file/partition
> 	sync	-	sync the filesystem (monster source! :)
> 	umount	-	unmount a filesystem
> 	update	-	background update thing - syncs filesystem
> 
> Like I said, keep an eye out for 'em - they are mostly the versions
> from the 0.95a root disk, with some cleanup of the code, the addition
> of a couple of minor utilities, and some other minor changes.

Not all of these executables are on the 0.95a root disk.  fdisk-x,
hostname, and passwd.  Who is packaging these executables for us?

(I downloaded hostname from tsx-11, and got passwd from my 0.95
root disk.  Where can I find fdisk-x?????)

=================================================================
Kevin J. Cummings                       Prime Computer Inc.
20 Briarwood Road                       500 Old Connecticut Path
Framingham, Mass.                       Framingham, Mass.

InterNet:  cummings@primerd.Prime.COM
UUCP:      uunet!primerd.Prime.COM!cummings

Std. Disclaimer: "Mr. McKittrick, after careful consideration,
		  I've come to the conclusion that your new
		  defense system SUCKS..."   --  War Games
=================================================================
Newsgroups: alt.os.linux
From: johnsonm@stolaf.edu (Michael K. Johnson)
Subject: Texinfo
Reply-To: johnsonm@stolaf.edu (Michael K. Johnson)
Organization: The Internet
Date: Tue, 14 Apr 1992 22:08:48 GMT

From: jknapka@aisun1.ai.uga.edu (Joseph Knapka [MSAI])

   Thanks for the tex-info^2. Two more questions:

   1) Can texinfo documents (if that's the word) be created using LaTeX, of
   is raw TeX necessary? 2) I assume Texinfo has been ported to Linux; where
   is it?

Neither is needed -- All texinfo is done with fairly simply
@-commands, with the exception of a
/input texinfo.tex
at the beginning of the texinfo file to bootstrap tex to understand
the @-commands.  It is _much_ _much_ easier, in my opinion, to use
texinfo than TeX/LaTeX, and I have use LaTeX to create answer keys
math classes, etc.  It was hellish -- Not that TeX was bad, but that
there is just so much to learn, and I can't afford either Knuth's or
Lamport's books right now.  Texinfo has a free manual (written in
texinfo, of course :-) and is quite easy to use, especially if you are
used to @commands and/or "intentional formatting."

It _is_ possible to include raw TeX code if you _really_ want to, but
there doesn't generally seem to be a lot of call for that, as in I
have not seen a reason to do it yet.

The manual and all necessary things, including an info browser
(program to display info files, the on-line versions of texinfo files)
written in c, are available from ftp.gnu.ai.mit.edu in /pub/gnu.  Look
under texinfo*.

If you want to print off the documentation, I can give a few hints --
The first of which is that it is about 150 pages, as I recall.  It is
also possible to order it from the FSF for $10-15, I think.

michaelkjohnson
johnsonm@stolaf.edu
From: jon@robots.oxford.ac.uk (Jon Tombs)
Newsgroups: alt.os.linux
Subject: Re: mount:unable to open lock-file
Date: 16 Apr 92 21:18:21 GMT
Organization: Robotics Research Group, Engineering Science Dept, Oxford, UK.

In article <1992Apr16.142538@hammer.Prime.COM> cummings@hammer.Prime.COM (Kevin Cummings) writes:
>In article <1992Apr16.120449.17752@athena.mit.edu>, szb50@juts.ccc.amdahl.com (Sid Boyce) writes:
>> 
>>    Does anyone know how I can recover the "LOCK-FILE".
>This is becoming a FAQ.  look for /etc/mtab~  if it exists, delete it.
>

I put a 
rm -f /etc/mtab~ 
in my /etc/rc a long time ago, maybe this should be but on the rootimage
as standard?

I've already seen it in one FAQ if it isn't in the official one it should
be!
--
 Jon                    <jon@robots.ox.ac.uk>
                        "I got in today just as the sun was crashing"
                                                
                                                


                                            

                        
Xref: sparky alt.os.linux:2417 comp.os.linux:328