HDTenEightyP/NetNews huggingface dataset:
From: monkey@z.eecs.umich.edu (Xinbing Liu)
Subject: Question about getting files from ftp sites
Organization: University of Michigan EECS Dept., Ann Arbor, MI
Date: Thu, 30 Jul 1992 22:42:26 GMT

Now I am beginning to download some packages from various ftp sites, a new
problem arises: Most files are named xxx.x.tar.Z, when I do (in binary mode) 
"(m)get xxx.x.tar.Z", ftp won't send the file(s) to my PC (DOS) because
the DOS file has to be named xxxxxxxx.yyy, no more than one period.  I have
to do "get xxx.x.tar.Z  xxx.z".  But this is tedious, and once I mcopy 
xxx.z to linux side, I have to do "mv xxx.z xxx.tar.Z", quite annoying.
Any suggestions on how to avoid it?
From: cummings@hammer.Prime.COM (Kevin Cummings)
Newsgroups: comp.os.linux
Subject: Re: New Install - Comments and Questions
Date: 27 Jul 92 20:09:09 GMT
Organization: Prime Computer R&D

In article <sheldon.712259366@pv141b.vincent.iastate.edu>, sheldon@iastate.edu (Steve Sheldon) writes:
>  1. Upon booting Linux it asks for SVGA modes.  I get 6 or 7 options.
> Well I can get the 80 column modes to work, but not the 132 column.
> When I select a 132 column mode, the screen stays the same (i.e. 80x25),
> but internally it things it's right.  So if I selected something like
> 132x50, it thinks there is 50 lines, but I only see the top 25.
> I'm using a Trident 8900 video card, with 256K of memory onboard, with
> an Everex monochrome VGA monitor.  I get 132 column modes just fine using
> DOS.  Has anyone else had this problem?

In order to answer this question, I need to know what version of LINUX you
are running?  When LINUX boots, do you see a line indicating VESA support
in your video card?  Followed by your video mode choices?  If so, then 
when you select a mode, LINUX make a VESA BIOS extension call to set your
video mode.  If it fails, then there is a problem with your video card.

My card gives me 4 choices.  The first two are hard coded (80x25, and 80x50)
and appear in EVERYONE's VESA list.  80x25 is the standard MODE-3, while
80x50 is the same mode with an 8x8 font loaded instead of the default 8x16
(or 8x14) font.  The rest of the modes in the list come from the VESA modes
list returned by the Get VESA information call.  On my card they are 132x25
and 132x43.  These modes both work for me.

IF you are running version 0.96c at patch level 1 or greater and 
IF YOU DO NOT HAVE A VESA BIOS, or
IF you are running any version before 0.96c-pl1, then you get a list of
"standard" modes put up specific to your video card,
which for a Trident card would be:  07, 50, 51, 52, 57, 58, 59, and 5A
which are 80x30, 80x43, 80x60, 132x25, 132x30, 132x43, and 132x60.  These
are stadard Trident Video modes, and are set by an INT 10 video bios call
to the Set Video Mode function using the mode number from the list.  

Unless I have screwed up the old functionality badly with the VESA support,
which you can check by building a LINUX kernel with an old boot/setup.S
file, then your mode set call is failing and you possibly have a faulty
video board.  I'll double check the compatibility code when I get home
tonight, but I would have thought that there would have been more complaints
by now if I broke the old stuff.

Please let me know if I can be of any more help.

=================================================================
Kevin J. Cummings                       PrimeService
20 Briarwood Road                       A Computervision Company
Framingham, Mass.                       500 Old Connecticut Path
					Framingham, Mass.
Work:  cummings@primerd.Prime.COM
Home:  cummings@kjc386.framingham.ma.us

Std. Disclaimer: "Mr. McKittrick, after careful consideration,
		  I've come to the conclusion that your new
		  defense system SUCKS..."   --  War Games
=================================================================
Newsgroups: comp.os.linux
From: besp@ellis.uchicago.edu (anna  besprozannaya)
Subject: Support for multiple video cards (was Last Message to All)
Reply-To: besp@midway.uchicago.edu
Organization: University of Chicago Computing Organizations
Date: Thu, 23 Jul 1992 01:57:06 GMT

In article <1992Jul18.183600.22257@athena.mit.edu> jnewbern@athena.mit.edu (Jeffrey L Newbern) writes:
>
>The reason that it is not trivial to add support for new video cards is
>that the cards are not hardware compatible.  Typically, each manufacturer
>designs the card a little different, and often those differences are
>sufficient to make the hardaware incompatible.  Normally, these
>differences don't show up, because the video BIOS corrects for the
>inconsistencies.  For example, two VGA cards may use different chips, but

A while ago I was doing system administration on SCO system ;-{ and was
surprised by their innovative approach to handling different video cards.
The way I understood it, their video driver uses a runtime configuration
file, which tells it how to put a particular video card into video modes
the card is capable of runig. It looked somewhat like:

1024x768x8:
{ outport(0x123, 0x56); outport(0x789, 0xab); ...  }

This file also described "capabilities" of the mode, much as /etc/termcap
does. I know very little about video cards / drivers.
Does it make sense and is it a good idea ? And does SCO _new__X11R4_ server
really runs that way ?
Newsgroups: comp.os.linux
From: J.Jagger@sheffield-city-poly.ac.uk
Subject: Re: Linux and DRDOS 6.0 and Superstor
Reply-To: J.Jagger@sheffield-city-poly.ac.uk
Organization: The Internet
Date: Wed, 29 Jul 1992 09:28:07 GMT

[Question from Ghazali Shafie]

NO you can't use Superstor on a Linux partition. Neither can Linux
read a DOS drive that has been compressed by Superstor.

The MCC-interim release mentions an important point about using DRDOS.
The partition table id-number for Linux is 0x81 (or 0x82 for
swap). However DRDOS sees this as 0x01 (perhaps it only looks at the
lower 4 bits). Now, 0x01 is a DOS number. The upshot of all this is
that you need to change this id-number if you've want Linux and
DRDOS to exists peacefully. MCC recommends changing the linux id-
number in the partition table to 0x41 and 0x42, which I use and
that works fine.

Lastly if you need to copy files ftp'd to a DOS machine onto Linux,
you will need a DOS drive that is not compressed by Superstor. If you
run MS-Windows then you should have such a drive for your
permanant swap file (since you must be on a 386+).

JJ
:: Jon Jagger  asjrbj@oak.scp.ac.uk
:: Sheffield City Polytechnic, Pond Sreet, SHEFFIELD S1 1WB
:: Tel 0742 533802/432889 (work/home) Fax 0743 533840
:: Newspaper ad: Men wanted for expanding contracting company!
Newsgroups: comp.os.linux
From: joef@extro.ucc.su.OZ.AU ()
Subject: olvwm
Summary: Can someone put it SOMEWHERE
Organization: Sydney University Computing Service, Sydney, NSW, Australia
Date: Mon, 27 Jul 1992 23:30:05 GMT


  If I ask really nicely, could SOMEONE please upload the olvwm binary to somewhere? I was talking to someone
a few weeks back who promised to ftp it to here, but he's forgotten [I assume]  
 
  Would someone be nice enough to fulfill this task?
 
   [BTW - extro.ucc.su.oz.au has a large ~ftp/tmp directory - hint hint :-)]

    Oh, if extro.ucc.su.oz.au doens't work, try extro.cs.su.oz.au - for some reason unbeknownst to the proles
they have decided to change it.  a gethostbyaddr() returns cs.  Wierd.

          Thanks

            Joe

---
joef@extro.ucc.su.oz.au
Newsgroups: comp.os.linux
From: peterw@archsci.arch.su.oz.au (Peter Williams )
Subject: re: olvwm
Organization: Design Computing Unit, The University of Sydney
Date: Tue, 28 Jul 1992 23:33:35 GMT

In article <1992Jul28.013323.4760@uvm.edu>, lhanson@moose.uvm.edu (lhanson) writes:
|> 	I would like to add my voice to the plea for olvwm binaries.
|> Would someone please upload binaries that run under 0.96c?  I have
|> tried to compile the current sources from banjo.concert.net and have
|> not been successful (fatal errors in olwm.c).  The Makefile also
|> requires flex; where are the current sources for flex?
|> 
|> Lee
|> 

I put it in olvwm.bin.T.Z in pub/linux/X11 on archsci.arch.su.oz.au (129.78.66.1)
this morning. Includes man and info files.

-- 
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: Rob.Levin@f217.n3802.z1.fidonet.org (Rob Levin)
Newsgroups: comp.os.linux
Subject: Minor problems with Linux
Date: Fri, 24 Jul 1992 22:48:34 -0800

 wED> | /etc/passwd to "bash" instead of "sh".  On MCC, I'm not sure.

 wED>   What am I missing? The shell with both the mj and drs
(sc.tamu.edu)
 wED> versions seem to like .profile just fine.

It varies from version to version.  Perhaps the folks who compile it
change the defaults....

Rob L.


 * Origin: Via the Annex in Victoria, TX (1:3802/217)
From: kk@cs.tu-berlin.de (Kolja Kaehler)
Newsgroups: comp.os.linux
Subject: Re: RFD: comp.unix.* reorganization
Date: 22 Jul 92 22:52:25 GMT
Organization: Techn. University of Berlin, Germany

bjl@sif.pttrnl.nl (Ben Lippolt) writes:
> unixsys@ssg.com (Rick Emerson) writes:
> 
[stuff deleted]
> 
> To me it really doesn't matter. I would just say: go with the majority.
> If the minix and coherent and other groups want to move, just follow them.

I agree. BTW: if people considered linux to be 'mainly unix', as c.u.l
suggests, couldn't this possibly reduce the number of postings with questions
about general unix behaviour (like the famous 'rm ./-I'-thread)  in c.o.l ? 

	Kolja
-- 
------------------------------------------------------------------------------
Kolja Kaehler                                            <kk@cs.tu-berlin.de>
Newsgroups: comp.os.linux
From: joef@extro.ucc.su.OZ.AU ()
Subject: Re: Problems with X as non-root
Keywords: X tty
Organization: Sydney University Computing Service, Sydney, NSW, Australia
Date: Thu, 23 Jul 1992 05:41:26 GMT

davidsen@ariel.crd.GE.COM (william E Davidsen) writes:
>In article <1992Jul21.234613.4757@cs.tulane.edu>, butler@cs.tulane.edu (Larry Butler) writes:
>| problem. When I run X as a non-root user I get the message:
>| 
>|   Can't open '/dev/tty0'
>| 
>| As far as I know, I followed all the instructions that said make sure you
>| do <this> if you want to be able to run X as a regular user. Any help
>| would be greatly appreciated.
>  I didn't even see the instructions, and I get a slightly different
>message, but I have the same problem. Since I have more pressing
>problems I didn't worry about it, but it's a really odd choice of

   As a stab in the dark, try this [as root]
# chmod 4755 /usr/bin/X11/xterm
#   

   That will setuid to root xterm.  
   Unfortunatly, it DOES leave some security holes open, and if you ever
intend to have more than yourself use the machine, and you are worried about
someone getting root privs who isn't meant to, just run it as root, and
leave it un-suid.

            Joe

---
joef@extro.ucc.su.oz.au
From: djansa@mersem.cs.wisc.edu (Dean Jansa)
Newsgroups: comp.os.linux
Subject: Spreadsheet for Linux
Date: 30 Jul 92 14:28:58 GMT
Organization: University of Wisconsin, Madison -- Computer Sciences Dept.

Just in case anyone is interested:

	I am currently porting sc (spreadsheet calculator) to linux.
	It's up and running on my system, but I want to test it fully
	and get the arrow keys to work (the great curses problem).

	Also, I want to clean up the code and Makefile( gee, what a
	mess!! Enough #ifdefs to kill a horse! ).  I will make a Linux
	makefile and take all the #ifdefs out of the code to make it
	`simple'  to debug and maintain. I'll keep the "#ifdef'ed" code around
	in case anyone wants to port it to some other platform. 

	If there is no interest, stop me now :) !

C ya...
	Dean Jansa
	University of Wisconsin - Madison
	Computer Systems Lab
Newsgroups: comp.os.linux
From: drew@hamlet.cs.colorado.edu (Drew Eckhardt)
Subject: Re: Tape support (Adaptec 1542B)
Organization: University of Colorado at Boulder
Date: Sat, 25 Jul 1992 03:29:46 GMT

In article <1992Jul24.101600.812@rz.uni-karlsruhe.de> erb@insu1.etec.uni-karlsruhe.de (Olaf Erb) writes:
>Hi there,
>I hope this isn't a FAQ  - is there tape support for Adaptec 
>and a Wangtek 150MB tape drive? I don't want to copy 100++
>disks...

Not yet.
From: Rob.Levin@f217.n3802.z1.fidonet.org (Rob Levin)
Newsgroups: comp.os.linux
Subject: Is tar still broken on 0.96c (how do I install anything?)
Date: Fri, 24 Jul 1992 08:26:58 -0800

 JSF> the appropriate README files, I find that I need to use rawrite to
write
 JSF> a file to a floppy and then use tar to get it back 
 JSF> off. But wait, according
 JSF> to the README, tar on 0.95c is broken and you need to get the one
off of
 JSF> tsx-11. It still seems to be broken on 096c so I did 
 JSF> that, but now how do I 
 JSF> get it on to my system?

The 'tar' on 0.96c is a different matter.  It is actually a linked
version of 'pax'.  It's not broken, but it does not do
compression-related stuff, since those functions do not appear to be
part of the posix-standard 'pax' implements.

GNU tar *does* perform those functions.  Versions 1.10 and later are not
broken in any sense; they work fine.

Rob L.


 * Origin: Via the Annex in Victoria, TX (1:3802/217)
From: drmo@gnv.ifas.ufl.edu
Newsgroups: comp.os.linux
Subject: Future Domain SCSI Support
Date: 27 Jul 92 21:48:18 GMT

Has anyone had any success in installing Linux on a SCSI drive with a
Future Domain 880 controller card.  The SCSI faq says that it is similar
to one of the drivers already supported, and that it should be possible.

Thanks 

Drew Moseley
Newsgroups: comp.os.linux
From: fortony@sonne.cso.uiuc.edu
Subject: performance under linux
Originator: fortony@murphy
Organization: University of Illinois at Urbana
Date: Thu, 23 Jul 1992 05:54:06 GMT
Keywords: subjective use of objective criteria


I was bored and running out of things to download, so I downloaded
the source to dhrystone 1.1 and ran it under Linux and a sun3/60.
The sun3/60 was a standard sun3/60, and my machine is a 386/25 clone
with 4M memory and 8M swap.

Now, clearly, this is not any kind of scientific endeavor, but I
will note that both machines were equally loaded in terms of percent
of overall memory, and both machines had enough memory to run the
dhrystone suite without swapping or getting otherwise nervous.

                    The sun 3:                        my toy:
straight up         15772                             4468
with registers      18450                             5170
optimized straight  25641                             7824
opt with registers  25641                             7824

The larger number, the better.  

Now, this study has nothing to do with anything, but by interesting
comparison, my desktop 386 is grossly outpowering a vax-784 running
4.3 BSD/Mach and putting up a valiant struggle against a Vax 8600,
easily besting it in the register competition but not doing so well
regularly.

This says nothing at all, really, I must hasten to re-mention, but it
does indicate that Linux is a real contender in terms of speed with
some of the big boys, given rough approximations at equal hardware.

It also indicates that times are a-changin'.  I'm writing this from
my Linux box in an xterm.  On that Vax 8600 which squeaks by my $1,300
computer, you had to use multiple hard terminals.
-- 
a b c d e f g h i j k l m n o p q r s t u v w x y z
Felix Sebastian Ortony	fortony@murphy.gis.uiuc.edu
Newsgroups: comp.os.linux
From: wcn@cs.brown.edu (Wen-Chun Ni)
Subject: Re: Problem with elvis binaries from tsx-11
Keywords: elvis binary
Organization: Brown University Department of Computer Science
Distribution: usa
Date: Mon, 27 Jul 1992 04:33:51 GMT

In article <farrow.712194800@fido.Colorado.EDU> farrow@fido.Colorado.EDU writes:
>Has anyone else had problems with the elvis binaries from tsx-11?
>
>When I try to run elvis I get a general protection fault and whole stream
>of other error messages. I'd insert them here, but I don't have anything 
>on my Linux system working since I don't have an editor and I can't cut and
>paste to DOS. :)
>
>I've tried deleting the binaries and downloading them again, but with the same
>results.
>
>Linux version is 0.96c.
>
>ps. yes, I've given up for now and am downloading emacs
>
>Scott
>

I tried to tp the elvis file from banjo and the file turned out to
be corrupted. Finally, I just get the source from the GNU site
(prep.*.mit.edu) and compiled it myself. After setting it to be
SYSV and just changed *very* little, my new elvis is running.

So don't give up, if you really like vi.



Wen-Chun Ni

P.S> I also compiled xfig without any problems. The resulting program
     is really great, though it reminds me of the fact that

	"I only have a 386 ;-("
From: cummings@hammer.Prime.COM (Kevin Cummings)
Newsgroups: comp.os.linux
Subject: Re: Newbie Linuxer & misc. Qs (LONG!)
Date: 31 Jul 92 15:32:45 GMT
Organization: Prime Computer R&D

In article <1992Jul31.091432.11879@constellation.ecn.uoknor.edu>, callison@uokmax.ecn.uoknor.edu (James P. Callison) writes:
> In article <5446@mccuts.uts.mcc.ac.uk> LeBlanc@mcc.ac.uk (A. V. Le Blanc) writes:
> >In article <1992Jul26.220519.18078@sura.net> vargish@sura.net (Nick Vargish) writes:
> >>4. Mtools sometimes can't initialize my floppies, and sometimes can't
> >>   even see them (depending on what random numbers I'm using in
> >>   /etc/mtools).
> >
> >You should have
> >     A /dev/fd0 12 0 0 0
> >     B /dev/fd1 12 0 0 0
> >for the floppy entries in /etc/mtools.
> 
> Hmmm. I just left it as
> 	A /dev/PS0
> and did
> 	ln /dev/fd0 /dev/PS0
> and it works just fine for me.

/dev/PS0 is supposed to be a 1.4 MB 3.5" disk driver.
/dev/fd0 is supposed to be an auto-detecting disk size and format disk driver.

So what you have done is make a link from a specific device name to the general
driver.  (Not as bad as the other way around I have to admit).  

This may be a quickfix, or a workaround until you understand what should have
been done, but PLEASE don't go around giving this to other people.  The
confusion level about floppy disk drives is high enough without complicating
it with mis-information.   Thanx.

=================================================================
Kevin J. Cummings                       PrimeService
20 Briarwood Road                       A Computervision Company
Framingham, Mass.                       500 Old Connecticut Path
					Framingham, Mass.
Work:  cummings@primerd.Prime.COM
Home:  cummings@kjc386.framingham.ma.us

Std. Disclaimer: "Mr. McKittrick, after careful consideration,
		  I've come to the conclusion that your new
		  defense system SUCKS..."   --  War Games
=================================================================
Newsgroups: comp.os.linux
From: jgifford@attmail.com
Subject: splitting of c.o.l, new suggestion.
Reply-To: jgifford@attmail.com
Organization: The Internet
Date: Thu, 23 Jul 1992 05:21:53 GMT

I am against the split, but it would seem to be a good idea to have 
comp.os.linux.install for people haveing problems installing anything like gcc, 
X, Linux...

What would be much better though, would be a MAILING LIST, something like
linux-install@site.dom

Newsgroups: comp.os.linux
From: negaard@aero.org (Eric Negaard)
Subject: QIC-02 tape driver?
Organization: The Aerospace Corporation, El Segundo, CA
Date: Mon, 27 Jul 1992 20:30:06 GMT

I thought I remembered seeing a message from someone who is working
on a QIC-02 driver, but I can't find it now.  Is anyone working
on this beast?  Do you need beta-testers? :-)  Or, more seriously,
do you need help?

			Eric Negaard
Newsgroups: comp.os.linux
From: zmbenhal@netcom.com (Zeyd M. Ben-Halim)
Subject: Re: only 4 pty's
Date: Fri, 31 Jul 92 05:07:05 GMT
Organization: Netcom - Online Communication Services (408 241-9760 guest)

In article <1992Jul31.042326.22392@cs.tulane.edu> butler@cs.tulane.edu (Larry Butler) writes:
>When linux boots up it says 4 pty's. How  do I get more than 4 pty's?
>
>Thanks,
>Larry (butler@cs.tulane.edu)

You change NR_PTYS in /usr/src/linux/include/linux/tty.h to the number you want
Then create the extra /dev entries to match that number, and voila!

Zeyd

Newsgroups: comp.os.linux
From: drew@hamlet.cs.colorado.edu (Drew Eckhardt)
Subject: Re: New questions (was: Help a linux newcomer please)
Organization: University of Colorado at Boulder
Date: Thu, 30 Jul 1992 23:14:00 GMT

In article <1992Jul30.213310.28841@zip.eecs.umich.edu> monkey@z.eecs.umich.edu (Xinbing Liu) writes:
>Thanks to all who sent me email about my questions. Most are very helpful. A
>few said all the answers were in FAQ.  I disagree.  I did read thru FAQ.  But
>nowhere in FAQ mentions where to get the command 'ln' which is needed for the
>mtools to work.  And I did not find in FAQ how to setup new accounts.
>Anyway, now I've got mtools to work, and I can avoid the long and tedious
>process of rawriting to floppies.  Now I have new questions:
>
>1. How do I set new path?  In unix I do "set path = ($path /mypath)", but
>this does not seem to work here.
>
>2. How do I change the prompt?  Again in unix it's "set prompt="myprompt" ",
>and this does not work either.

Answer : This is unix, or as close as we'll get without a USL lawsuit =8^)

You're just used to c-shell and its derivatives, 
rather than Bourne shell (/bin/sh) and its kin.  Either get a csh for
Linux (ie, tcsh) and do what you always do, or use the Bourne shell syntax,
which is to say variable=value, and then export the result for environment
variables (as oposed to shell variables).

Ie : 

PATH=${PATH}:/foo 
export PATH

would add /foo to the default path.

Under Bourne shells, the prompts are set with 
PS1 and PS2.

PS1 sets the "top level" promt, ie what you see at the command line, ie
PS1=foo:

Will give me a prompt like 

foo:

PS2 sets what you see if you've done something to get yourself a second
level prompt, ie not closing some sort of quote or control structure,
or by using \ line continuation.

So, if PS1 = "foo: ", and PS2="bar: ", I could have a session that looks like
this : 
 
foo: I=10  
foo: while [ $I -gt 0 ]; do
bar: echo $I 
bar: I=`
bar: expr $I - 1
bar: `
bar: done
10
9
8
...
foo:

Whizzy Bourne-like  shells like gnu BASH (Bourne Again SHell), zsh, etc
have special escapes that can be embedded in the path that expand to 
the current path, execute some command, etc.  Read the manual 
for your Bourne shell.