HDTenEightyP/NetNews huggingface dataset:
From: koverber@cs.ulowell.edu (Kurt Overberg)
Subject: Re: X Question
Originator: koverber@bigmax.ulowell.edu
Organization: University of Massachusetts at Lowell Computer Science
Date: Mon, 21 Dec 1992 15:45:59 GMT


Normally, there is a startup file that gets executed when
you run startx.  I believe the name of the file is
'.startxrc' or something like that.  Your problem might be
that when X starts up, all it does is start up the Xserver, 
it dosen't start up any clients, such as xterm.

This is a sample .startxrc

#
# Clients started by default by startx
# The last client should NOT be started in the background.
#
xterm -sb  &
exec uwm 


					peace out.


					   kurt
-- 
Kurt Overberg            | Opinions expressed here are MINE!           
U of Mass, Lowell        | "Poke a double-decker on a Llama taboot,       
koverber@cs.ulowell.edu  |  Llama taboot, taboot!"      -Phish
From: rick@ee.uwm.edu (Rick Miller, Linux Device Registrar)
Newsgroups: comp.os.linux
Subject: Re: Kernel build benchmark
Date: 22 Dec 1992 18:43:02 GMT
Organization: Just me.
NNTP-Posting-Host: 129.89.2.33

[...]
>I think differences in processor speed become relevant only if you have 
>sufficient memory. I mean, for a 2M machine you'll see few difference from 
>a 486 and 386sx, but for a 8M machine... (I'm guessing it, I have tried 
>Linux only on my own box).
>
>                Romano.

This seems to be true... Here's what I've seen:

	386SX/20 (no 387) w/ 2Mb RAM	16 hours
	386DX/25 (no 387) w/ 4Mb RAM	45 minutes
	486DX/33 w/ 8Mb RAM		12 minutes

In each case there is only 5Mb of swap (I really haven't needed more).
The hard drives on all three machines have similar access times.

The main influence on performance seems to be the amount of RAM.
This makes sense, since access time is a *LOT* shorter for RAM than disk.

So... what's the going rate for RAM?  I'm game to upgrade my home box
to as much as I can afford! (...which isn't really saying a lot.)
My motherboard's RAM slots are half taken with the 4Mb it already has...
does this mean I can't put more than 8Mb on it?  How would I go about
putting more than 8Mb of RAM on such a box?

Rick Miller   <rick@ee.uwm.edu> | <rick@discus.mil.wi.us>   Ricxjo Muelisto
Occupation:  Husband, Father, WEPCo. WAN Mgr., Discus Sys0p, and  Linux fan
From: jwiegand@moe.eng.temple.edu (James Wiegand)
Newsgroups: comp.os.linux
Subject: Re: cp foo.graphics /dev/lp1 is slooooooooow. ANSWER!
Date: 25 Dec 92 06:36:29 GMT
Organization: Temple University EE Dept.

In article <1992Dec23.150230.22344@news.stolaf.edu> johnsonm@lars.acc-admin.stolaf.edu (Michael K. Johnson) writes:
>
>In article <1h9s83INNlng@nz12.rz.uni-karlsruhe.de> bernd@iamk4526.mathematik.uni-karlsruhe.de (Bernd Wiebelt) writes:
>
>
>   This has been asked before, but not yet answered.
>
>BZZZZZZZZZZZZT!  Wrong.  I have posted twice about this already.
>
>   Somewhere between linux98.1 and linux99 there was
>   a change in the blk-drv code which affects output
>   speed on printers. Does anyone know a cure for
>   this dilemma which doesn't involve putting the 
>   old blk-drv code from linux98.1 back into 99?
>   (In fact, I remeber there was a posting about
>   a programm solving this problem (lptune???) but
>   the same posting said that this programm was not
>   yet completed).
>
>That wasn't exactly what it said.
>
>ANYONE WITH PRINTER PROBLEMS *PLEASE* MAIL ME
>ANYONE WITH PRINTER PROBLEMS *PLEASE* MAIL ME
>ANYONE WITH PRINTER PROBLEMS *PLEASE* MAIL ME
>
>Please tell me what printer you have, and give me a description of
>your computer, and I will do my best to help you.
>
>   This gets me to another question: Why the hell was
>   there a change in the !working! lpr-code in a
>   version so close to linux 1.0. Shouldn`t we have been
>   waiting till 1.0 was out and then think about redesigning
>   lpr-code?
>
>NOT!  Working?  Well, that depends on your definition of working.
>Yes, it got stuff to the printer, but for many people, it was 5 times
>as slow as printing under dos, and really sucked up system time.  Now,
>my redesigned driver is much faster and more efficient for most
>people.  Unfortunately, it appears to break on deskjet 500's, and
>perhaps other printers, though I have only heard about deskjets...
>
>As far as waiting, I re-wrote that code quite a while ago.  If you
>haven't bothered to ask about it before now, and just now complain
>about the speed, right before 1.0 comes out, you /DON'T/ have my
>sympathy.  I'll still try to fix it, but I won't feel sorry for you.
>
>michaelkjohnson

Actually, the answer is quite simple and no secret.
Increase the value of LP_INIT_CHAR until you are happy.
I have:

#define LP_INIT_CHAR 250000

in include/linux/lp.h and get the same throughput as before. Otherwise,
I was getting one line of graphics every 20 minutes. Pretty sh*tty!

jim
When in doubt, there is always the source code!
From: tfoley@camaro.uucp (Tim Foley)
Newsgroups: comp.os.linux
Subject: Restricted Shell Needed
Date: 29 Dec 92 00:17:59 GMT
Organization: camaro


Anyone have a working Restricted Shell available?  Or is there one floating 
around somewhere?
 
					
-- 
  --------------------------------------------------------------------------
               The HeartBeat of America...Yesterdays Camaro Z28 
                             tfoley@camaro.uucp   
     Call the Camaro Linux Pub-access site: 1-416-238-6550 USRobotics HST
    Note: Please, no ftpmail or mailing lists or the host gets annoyed :)
  --------------------------------------------------------------------------
Newsgroups: comp.os.linux
From: mauney@adm.csc.ncsu.edu (Jon Mauney)
Subject: Re: Question and Observations
Organization: North Carolina State University
Date: Tue, 29 Dec 1992 18:50:50 GMT

whit@Tymnet.COM (Kendall Whitlatch) writes:
>Peter takes a pretty good beating here on C.O.L. every time any minor
>flaw in the package is found.  I think he needs a little applause for
>even attempting the task in the first place.

>Thanks again.

Hear, hear!
I like to think of myself as a Unix guru, but
I probably wouldn't have gotten around to installing Linux
if it hadn't been for SLS.  (Gurus can be lazy, too.)
-- 
Jon Mauney, Mauney Computer Consulting
mauney@csc.ncsu.edu   (919) 828-8053

"She wrote a long letter, on a short piece of paper."
Newsgroups: comp.os.linux
From: "2-JAN-1993 15:39:39.59" <nmp08@rz.uni-kiel.dbp.de>
Subject: Where are gethostbyname() & getservbyname()?
Reply-To: nmp08@rz.uni-kiel.dbp.de
Organization: The Internet
Date: Sat, 2 Jan 1993 14:41:36 GMT

I have a problem with the new gcc-2.3.3 stuff: several packages won't compile
anymore (e.g. plp) because of two missing functions: 'gethostbyname()' and 
'getservbyname()'. ld claims about not finding these symbols.
Where are these functions gone?

Any hints would be appreciated.
Please reply to: nmp08@rz.uni-kiel.dbp.de
From: nieuwhzn@fys.ruu.nl (Gerrit J. Nieuwenhuizen)
Newsgroups: comp.os.linux
Subject: SLS, Laptops, X and Xega
Date: 29 Dec 92 08:56:57 GMT
Organization: Physics Department, University of Utrecht, The Netherlands

Can some kind soul point out how to get Xfree86 working properly on
a laptop.
The Xega thing seems to have some problems with setting the proper 
font path, the Xmono server (finally, after some fiddling with the
Xconfig file) gave a root window and twm, but clicking the mouse 
did not do a thing.


			Gerrit J. van Nieuwenhuizen
			Sub Atomic Physics department
			University of Utrecht
			nieuwhzn@ruunfs.fys.ruu.nl
Newsgroups: comp.os.linux
From: jlaiho@ichaos.nullnet.fi (Juha Laiho)
Subject: Linux 0.99/Taylor UUCP 1.04gamma
Organization: NullNet r.y.
Date: Fri, 25 Dec 1992 20:52:11 GMT

I'm currently testing Taylor UUCP 1.04gamma with my Linux 0.99 (based on
HJLu's 0.98pl5(?) disk set).

On the other end of the wire is my Xenix box with Taylor UUCP 1.03.

So far things have gone pretty neatly, no major hacking has been needed.

..Wolf
Newsgroups: comp.os.linux
From: tytso@ATHENA.MIT.EDU (Theodore Ts'o)
Subject: New version of the serial driver to try out.
Reply-To: tytso@ATHENA.MIT.EDU (Theodore Ts'o)
Organization: The Internet
Date: Sat, 2 Jan 1993 08:02:47 GMT

I've been working on a partial rewrite of the serial driver, in an
attempt to speed it up and fix some of the other problems people have
been complaining about.  This version should be a lot more reliable,
especially on systems with unusual serial boards or other unusual
hardware.

If you're not afraid to recompile kernels and play with test versions of
device drivers, I'd really appreciate if you give my new driver a try.
It can be found on tsx-11:/pub/linux/ALPHA/serial/serpatches.

Please let me if it gives you any problems; and if it works, I'd also
like to know about it, so I know how many people have tried it.  Thanks!

						- Ted
From: Bryant.Graham@f3.n292.z1.fidonet.org (Bryant Graham)
Newsgroups: comp.os.linux
Subject: Trident Card Woes
Date: Fri, 25 Dec 1992 14:20:50 -0800

Edward,
  I join the choir in pleading for help with a TVGA card.


I have:

       386sx 20
       SyncMaster 3 monitor
       2 IDE Seagate 100 meg H.D.
       Digicom Scout plus 14.4
       3.5 & 5.25 F.D.
       4 meg RAM <4 more on order>

       install older SLS 0.96 <full package> 
       on a 32 meg partion on /dev/hd0/

 * Origin: Disclaimer: Hell, I'm out on this limb by myself (1:292/3)

Newsgroups: comp.os.linux
From: becker@super.org (Donald J. Becker)
Subject: Re: The 3c503-ALPHA-DRIVER (WAS: [NET]: Problems with 0.99) 
Organization: IDA Supercomputing Research Center
Date: Wed, 23 Dec 1992 18:58:08 GMT

In article <725050966snx@crynwr.com> nelson@crynwr.com (Russell Nelson) writes:
>In article <EWERLID.92Dec19032033@ida.docs.uu.se> ewerlid@ida.docs.uu.se writes:
>
>   The probe that detects the 3c503 card fails to properly check
>   the shared memory.  This means that shared memory is
>   detected and given an address even though it is disabled by the
>   onboard shared memory jumper.  There are MSDOS 3c503 drivers that can
>   use a 3c503 card with the shared memory disabled.
>
>Yeah, but it's real fussy to get right.  You have to bunch your I/O's
>in blocks of 16, then wait for the board to get ready for more.  It's
>really icky.  Much better just to set the board to shared memory mode.
>
>-russ <nelson@crynwr.com> What canst *thou* say?
>Crynwr Software           Crynwr Software sells packet driver support.
>11 Grant St.              315-268-1925 Voice  |  LPF member - ask me about
>Potsdam, NY 13676         315-268-9201 FAX    |  the harm software patents do.

Good News:
The bug of not detecting the no-shared-memory mode of the 3c503 is
gone with the latest ethercard driver version.  There is code that is
supposed to handle the non-shared-memory case.

Bad News:
I haven't gotten the non-shared-memory code to work yet (one reason that it's
still "alpha").  It's a low priority since I always run my card with shared
memory.


-- 
Donald Becker				       becker@super.org
Supercomputing Research Center
17100 Science Drive, Bowie MD 21114		   301-805-7482
From: 93jay@williams.edu (Jonathan Young)
Newsgroups: comp.os.linux
Subject: Son of SLS questions (tm)
Date: 27 Dec 1992 22:44:47 GMT
Organization: Williams College, Williamstown, MA
Distribution: world
NNTP-Posting-Host: hancock.cc.williams.edu

I have been spending much of the holidays tweaking SlS .99 on my
machine. Having solved a few of the basic problems (default install
has wrong passwd permissions etc.. ) I'm getting into more fun stuff.

1) My password seems to expire daily, no matter what usermod -e
setting I use. This does not happen with root.

2) I dug up an old printer to use and I can't find lpr or anything
else which would address it. There is a macro called print which calls
several programs not part of the SLS distribution (someone really
should fix that sort of thing)

3) I tried to install the fortune.tar from tsx-11 but the binaries all
seem to break with the message "uses old stat() call recompile your
binary" but can't gcc strfile.c for example - I don't think there are
makeifles for the respective utilities. Also where are the offensive
fortunes? (Hey it's *my* system :) The symbolic link for fortunes-o
goes to nowhere.

4) lots of little things like that, I think the FTP version of SLS
could use a bit of tweaking before it can be called 1.0 even if the
kernel moves to 1.0 soon. i.e. minicom still refuses to run claiming
that there is no global config file and there are no instructions on
how to create one. I created the respective directories but even when
I run it as root I get the message.. cannot create lockfile and it
quits.


5) is there a way to display dvi files on hercules graphics? I see
xdvi but no other dvi viewers.


			Till next time.
				Jonathan Young
From: kf8nh@kf8nh.wariat.org (Brandon S. Allbery)
Newsgroups: comp.os.linux
Subject: Re: Linux questions
Date: Tue, 29 Dec 92 17:59:54 EST
Distribution: world
Organization: Brandon S. Allbery's Personal System

jem@sunSITE.unc.edu (Jonathan Magid) writes:
> In article <9212278041@monty.apana.org.au> daryl@monty.apana.org.au (Daryl Te
> >1) Can Linux utilize an ordinary MDA (or Hercules) adaptor? Seems everyone
> >   is running SVGA adaptors (with dot clocking problems :-).
> 
> Hercules text mode is supported; I don't know about MDA.  The dot clocking

MDA and Hercules text use the same video addresses, etc.  Of course, Herc
graphics won't go anywhere on an MDA.  :-)

++Brandon

Brandon S. Allbery		NOTE NEW ADDRESS!!! --> kf8nh@kf8nh.wariat.org
From: jlaiho@ichaos.nullnet.fi (Juha Laiho)
Newsgroups: comp.os.linux
Subject: Re: Help Needed for Linux.
Date: 21 Dec 92 21:04:55 GMT
Organization: NullNet r.y.

In article <1992Dec21.063353.6903@sfu.ca> wonge@fraser.sfu.ca (Edmund Wong) writes:
>   8) I can't seem to get the X11 to work.  When I do a 'startx' 
>      command, the following screen appears:-
>
>      Creating TCP socket: Invalid argument
>      XFree86 Version 1.0Ya / X Window System
>      (protocol Version 11, revision 0, vendor release 5000)
>      Configured drivers:
>          VGA256 (256 colour SVGA);
>              et4000, et3000, pvga1, gvga, ati, tvga8900
!      VGA256: et4000 (mem: 0k numclocks: 16)
!      VGA256:   clocks: 25 28 36 27 30 33 20 24 50 57 72 45 60 65 40 47
!      VGA256: Too little memory for virtual resolution
>
>    I have a Trident 8900 card(?), with 512k,  a CTX SVGA monitor
>    for a 486/33 clone with 8megs of ram.
>
Seems like you have some errors in your XConfig..
First, your XConfig explicitly states that you have et4000 chipset, and you
explicitly state that you have tvga8900.

Second, I think that you may have "Virtual 1024 1024" in your XConfig.
This is size of the virtual screen, and this virtual screen should be small
enough to fit in your VGA RAM. As this is a 256-colour mode, every pixel needs
8 bits, thus 1024x1024 pixels need 1MByte. Reducing the virtyal resolution, or
commenting out the whole line could make the situation a lot better.
(Hey, someone, put this virtual resolution thing to X FAQ, if one exists..)

I also think that XFree 1.0 had some strange bug that appeared with tvga/512k,
but is fixed with XFree 1.1, and does not affect tvga cards w 1M memory
installed.

..Wolf
Newsgroups: comp.os.linux
From: "William L. Mullica" <p00192@psilink.com>
Subject: Null Modem "Dial-in" to Linux
Organization: Performance Systems Int'l
Date: Wed, 30 Dec 1992 02:32:02 GMT
X-Mailer: PSILink-DOS (3.3)

I've run into a perplexing problem when dialing into Linux via a null 
modem cable. I have no problems logging into Linux using the virtual 
terminals (tty1, tty2, etc.). However, when I use ttys0 (which is 
connected via a null modem cable to an SCO Xenix machine) to "dial in", 
characters are 'lost' (one or two at a time) in the transmission. For 
example, if 'la -laF' is input, the resulting directory display will 
have several lines misaligned due to missing characters. Different 
characters will be missing each time this is done...there does not seem 
to be a pattern in which characters are missing.

I've had this occur using both the standard SLS getty and getty_ps203 on 
the Linux machine and have used both cu and minicom to log in from the 
Xenix machine. I suspected the gettydefs parms might be at fault but 
cannot find any configuration which alleviates this problem.

Can anyone venture a guess as to what might be going on here? Any ideas 
will be appreciated. Thanks.

Bill, N6CKM







Newsgroups: comp.os.linux
From: mrhoten@cs.stanford.edu (Matt Rhoten)
Subject: Re: [Q] Linux fdisk DOS compatible?
Originator: mrhoten@Xenon.Stanford.EDU
Organization: CS Department, Stanford University, California, USA
Date: 26 Dec 92 22:22:13 GMT

okir@monad.swb.de (Olaf Kirch) writes:

> Since DOS fdisk refused to make more than one primary partition, I
> used Linux fdisk. However, I left one partition for later use with
> DOS. But now, DOS won't recognize my disk at all!

I ran into this as well. DOS breaks if you have more than one primary
partition. Since you don't need any of your linux partitions to be
primary partitions, you could simply remove the "bootable" or primary
bit from them with linux fdisk, leaving only your DOS partition marked
primary.

Your mileage might vary depending on the software with which you boot
linux. bootlin.com doesn't seem to need the primary bit set on anything.

 -matt
-- 
Matthew Rhoten | mrhoten@cs.stanford.edu | m_rhoten@leland.stanford.edu
"When Adam and Eve first saw each other, that's when the blues started."
 -John Lee Hooker
Newsgroups: comp.os.linux
From: mnl@dtro.e-technik.th-darmstadt.de (Michael N. Lipp)
Subject: umount and /proc
Date: Thu, 31 Dec 1992 21:06:21 GMT
Organization: TH-Darmstadt

I mount the /proc file system during boot with an fstab entry

  /dev/kmem /proc proc

When I halt the system (or when I try to unmount /proc by hand),
I get

  umount: /dev/kmem: not mounted

bug or feature?

Michael
--
-----------------,------------------------------,------------------------------
Michael N. Lipp  !  Institut fuer Datentechnik  !  Phone: 49-6151-163776
                 !  Merckstr. 25     ,----------'  Fax:   49-6151-164976
                 !  D-6100 Darmstadt ! E-Mail:
                 !  (Germany)        !     mnl@dtro.e-technik.th-darmstadt.de
-----------------'-------------------'-----------------------------------------
Newsgroups: comp.os.linux
From: cloos@theory.TC.Cornell.EDU (James H. Cloos Jr.)
Subject: Re: Installing SLS on my Gateway Nomad
Organization: Cornell Information Technologies, Ithaca, NY 14853
Distribution: comp
Date: Thu, 31 Dec 1992 06:11:51 GMT

I re-installed my sls disks, after dl'ing the c series, too.  I did a
385 cyl root partition (65450 Ko) as a minix fs, and a 200 cyl (34000
Ko) /home partition as an extfs.  As I still do not have my ram
upgrade, I set up a 8500 Ko swap partition and the rest of the disk
(100 cyl = 17000 Ko) will be for my dos needs--would that they were
not in fact *needs*.

Anyway, it all seems to be running OK, though I am stuck in 80x25 text
mode.  Looking thru the kernal src (99.1, from sunsite's incomming
dir) I didn't find what I need to change to get 80x50 text mode.  I
also cannot get /proc to show up.  Do I need an entry in /etc/fstab
or something???

I just have to make sure that I have the latest versions of the extfs
utilities, dl term-0.7 to let me do background dl's, and get the t and
x series installed, not to mention all those recently announced fsf
packages, etc.  Thanks in advance to whomever did them--I'm quite
short for disk space here until I get the desktop system to backup the
Nomad.

Again:  Vielen Kudos to Linus, Softlanding, and every other contributor!
Man is it great to be the sysadmin for a change!

P.S.	Almost forgot:  HOW do I add users such that the shadow files get
	updated.  Using the routines in the SLS distrib, even passwd(1),
	I only see changes to /etc/passwd & /etc/groups.  Because I used
	passwd(1) to set my root passwd, I get "no shadow entry for root's
	password" (or some such) errors whenever I log in....

-JimC
-- 
James H. Cloos, Jr.	include <std/qotd>
Cloos@TC.Cornell.EDU	include <std/disclaimers.h>
Cloos@Batcomputer.UUCP 	Snail:  POBox 1111, Amherst, NY 14226-1111
Cloos@CrnlThry.BITNET 	Phone:  +1 716 673-1250 (voice only, for now)
From: nhc@cbnewsj.cb.att.com (n.h.chandler)
Newsgroups: comp.os.linux
Subject: Re: More problems with telnetd/ftpd
Keywords: tcpip, telnet, ftp
Date: 30 Dec 92 22:55:58 GMT
Organization: AT&T

In article <1992Dec30.040050.14120@mintaka.lcs.mit.edu>, wyvern@gnu.ai.mit.edu (The Wyvern) writes:
> Well, I was optimistic after I downloaded the new net-src package
> from sunsite, since telnetd would allow me to log into my own
> machine via loopback again. But I've recently been having some
> serious problems with it, along with ftpd.
> 
> When I'm using term (v0.9.9) with the tredir utility to redirect
> ports to my own system (i.e. tredir 6111 23 so people can log
> in via telnet) it'll work once, and then all subsequent attempts to 
> telnet to that port will result in a connection that just hangs, with
> no login prompt, or anything. Interestingly enough, I can still

I experience the same behaviour with telnet.  After one connection
all subsequent attempts to connection just hang.

> telnet from my own machine to my own machine, but not for long -
> after a few more times, it fails even to do that, just locking up.
> I suspect this may have something to do with /bin/login, as I'm
> using the login from the shadow-password package, and it never did
> work well with telnetd (why?). Needless to say this problem
> pretty much trashes any hopes of using telnet(d) with term over
> the internet.

I'm not using the shadow-password package and my system fails the
same way.

> Ftpd has a similar problem with working once (sometimes not at all)
> and then locking up on all subsequent attempts to connect.
> Part of this is probably due to my using shadow passwords which ftpd
> doesn't seem to support.
> 

Same here, and I'm not using shadow passwords.

> 
> My system configuration:
> 486, Phoenix BIOS
> 200mb IDE drive
> No ethernet board
> X8514 with TCP/IP
> Linux Kernel version 0.99.1
> 
> 

My system configuration:
486/33, AMI BIOS
8 mb ram
2 - 200mb IDE drives
16 mb swap
WD8013EBT (16k ram)
Xfree86 with Local Bus ET 4000
TCP/IP, Linux 0.99.1 

-- 
-----------------------------------------------------------------
Neville H. Chandler           ||       AT&T Bell Laboratories
nhc@mtdcr.att.com             ||       Middletown, NJ 07748
-----------------------------------------------------------------
From: mycroft@hal.gnu.ai.mit.edu (Charles Hannum)
Newsgroups: comp.os.linux
Subject: .99.1 keyboard lossage
Date: 24 Dec 92 13:31:15 GMT
Article-I.D.: life.1hce33INNj04
Organization: /etc/organization
NNTP-Posting-Host: hal.gnu.ai.mit.edu


In article <1992Dec23.102704.5911@klaava.Helsinki.FI>
torvalds@klaava.Helsinki.FI (Linus Torvalds) writes:
>
> PS.  0.99.1 can mess up your keyboard leds at bootup: [...]

This happens to me.

Not only that, but it doesn't actually wait for me to press a key at
either the VGA mode or root disk prompts.  This is very annoying when
booting from floppy.  (I added a second drive to my machine to
circumvent it.)

-- 
 \  /   Charles Hannum, mycroft@ai.mit.edu
 /\ \   PGP public key available on request.  MIME, AMS, NextMail accepted.
Scheme  White heterosexual atheist male (WHAM) pride!
Newsgroups: comp.os.linux
From: agc@weasel.demon.co.uk (Alan Charlton)