HDTenEightyP/NetNews huggingface dataset:
From: rbraun@spdcc.com (Rich Braun)
Newsgroups: comp.os.linux
Subject: Re: HELP --- LILO won't let me select other OS
Date: 20 Dec 92 19:13:28 GMT
Organization: Jupiter Technology Inc., Waltham MA

harry@atlas.socsci.umn.edu (Kuo-Chen Chang) writes:
>Hi, netters!
>
>I just updated to LILO 7.0.  The new version won't give me any chance to
>select other OS.  (CUrrently I have LINUX, DOS and OS2.)  I followed
>all instructions.  I'll be very appreciated for any resolution,
>suggestion.

Works for me, though I confess it took a lot of code-reading to figure
out how the heck to pick the O/S at boot time.  (Please, whomever
updates the README file, mention the Shift/Ctrl/Alt key business.  And
even better would be a standard option in the code to display a
multiple-select menu at boot time, rather than requiring the user to
know some obscure keystroke in advance.  I'm posting rather than emailing
in hopes of benefiting others struggling with LILO.)

Did you use the "-d" (delay) option to delay boot?  If you don't, it won't
give you much (any?) chance to press Shift at boot time.  I set the delay
to 2 seconds (-d20), with msdos as the first O/S in the list so it's the
default.

-rich
From: Jim.Corbett@f35.n152.z1.fidonet.org (Jim Corbett)
Newsgroups: comp.os.linux
Subject: [comp.os.linux.announce] Welcome to comp.os.linux.announce!
Date: Tue, 15 Dec 1992 14:33:00 -0800

 > From: mdw@db.TC.Cornell.EDU (Matt Welsh)

 > Plans are in the works for having this group archived
 > at one or more of
 > the Linux FTP sites; more on that later. I also plan
 > to start a mailing
 > list channel for those without USENET access (when the
 > linux-activists list is going again).

That would be welcomed by some of the users of my DOS BBS.
It would allow them to d/l a file one a week and stay current on
announcements.

Please let us know when you start this added feature!

Thanks for taking the time to moderate.

 * Origin: Intermittent Connection, Eugene OR 503-344-9838 (1:152/35)

Newsgroups: comp.os.linux
From: pmacdona@sanjuan (Peter MacDonald)
Subject: Re: problems with mount
Keywords: mount
Organization: University of Victoria, Victoria B.C. CANADA
Date: Tue, 15 Dec 92 02:27:31 GMT

In article <9234923.25842@mulga.cs.mu.OZ.AU> caw@cs.mu.OZ.AU (Chris Wright) writes:
>Thanks for all the work that has gone into this...
>I've got the minimal SLS installation (a1-4), and all seems find,
>whoops, fine, except for two things:
>mounting a floppy and adding a new user. 
>I've read both the linux and SLS faq's so I hope that this isn't a
>waste ot bandwidth.
>
>whether I use menu, or mount, to mount a floppy, I get
>"/dev/fd? mounted, or ?? busy". This is as root.
>
>and using menus adduser, or just using adduser from the 
>console fails, as it can't find the command.
>

adduser is dead

use useradd

>Thanks again for the patience...we non gurus appreciate it.
>(Oh, and I've checked in the unix.faq about the mount thing :0)
>
>cheers
>
>chris
From: jwiegand@moe.eng.temple.edu (James Wiegand)
Newsgroups: comp.os.linux
Subject: Re: Suggestion Spliting Group
Date: 14 Dec 92 16:24:13 GMT
Organization: Temple University EE Dept.

In article <1992Dec12.205425.15557@exucom.com> cyberman@exucom.com (Stephen R. Phillips) writes:
>
>Stephen R. Phillips (cyberman@exucom.com) wrote:
>: 
>: In hopes that this will prevent the 99-300 message per day from
>: SWAMPING most poeple.  I suggest this group be split.
>
>PLEASE do not reply or follow up to this message any longer I am canceling it.
>I guess I missed the CFV and voting on this topic.  I will no longer
>read this group since:
>1:	The traffic is rediculous
>2:	No comment.
>
>No flames are needed I apologize for posting this. 
>
>This means the subject is closed I will NO longer reply to mail for
>this either.  So if you get bounced it's because I bounced it and the
>subject matter is closed as far as I'm concerned.
>
>Cyberman

Nice guy, huh? That's it, start a flame war and run for cover.

jim
Newsgroups: comp.os.linux
From: daum@ee.ualberta.ca (Tanya Louise Daum)
Subject: Cache
Organization: University Of Alberta, Edmonton Canada
Date: Fri, 18 Dec 1992 05:00:31 GMT

I am running Linux 0.98.5 on a 486DX/50 with 8 megs of ram and 16 megs of
swap. I have a hardware cache installed (256k) but Linux keeps reserving
huge huge ammounts of space for cache.

When I look at the output from "free" I usually get values ranging from 2
megs to 6 megs reserved for cache!  Even when I've run out of RAM and Linux
starts to use swap the system still commonly uses 2 megs or 3 megs for
cache.  Is there any way to get it to use less or (maybe) none?  I mean,
this really ticks me off to have the system swapping to death while I sit
there with 3 megs basically unused.

-- 
"And men are men who till the land, and women are women who weave, fifty men
 own the lemon grove, and no man is a slave." -- Herbert Read

Comrade @ LambdaMOO (telnet lambda.parc.xerox.com 8888) daum@bode.ualberta.ca
Newsgroups: comp.os.linux
From: buckel@winx06.informatik.uni-wuerzburg.de (bernhard buckel)
Subject: Installing X on a non-Multisync
Organization: University of Wuerzburg, Germany
X-Newsreader: TIN [version 1.1 PL6]
Date: Tue, 15 Dec 1992 14:44:16 GMT


After several nights i finally decided to ask the netpeople for help. My 
configuration is a 486DX,105MB HD,8MB RAM, paradise card(512k) and -
a regular fixed-frequency-monitor, capable of 640x480, 800x600 and in
interlaced mode 1024x768. Trying to start X in any mode worked, but the 
feedback was rather poor... my screen went completely out of sync. After
gambling with clock.exe, timings.exe and the res script from the X386 kit
i am wondering whwther any helping soul out there is willing to mail me his/
her Xconfig for a non-multisync-monitor. The first mails reaching me will be
awarded by several cans of virtual beer!

Thanx in progress,
				Bernhard

P.s.:
Monitor specs are
640 x 480 at 60 Hz, horiz. freq. 31.5kHz
800 x 600 at 56 Hz, horiz. freq. 35.2kHz
1024x 768 at 87?Hz, horiz. freq. 35.5kHz

Please help, i`m just a poor compsci student and cant afford a multisync! 
Newsgroups: comp.os.linux
From: evansmp@uhura.aston.ac.uk (Mark Evans)
Subject: Re: tcp/ip support and the Makefile of 0.99
Organization: Aston University
X-Newsreader: TIN [version 1.1 PL241235]
Date: Tue, 15 Dec 1992 13:25:59 GMT

Ammo Goettsch (ammo@cc.gatech.edu) wrote:
: I disabled TCP/IP throught the "make config" option of the kernel Makefile
: for version 0.99. In .../net/Makefile, it still wants to link in 
: tcp/tcpip.o, which of course had not been compiled, since the make file
: in .../net/tcp never gets executed ifndef CONFIG_TCPIP. 
: 
: Is the link line in the make file wrong or should it have been compiled?
: 
: Also, what will happen if I compile TCP/IP but have no network card?

it will produce an error on bootup about being unable to find the hardware,
tcp functions will still work through the loopback device

--
-------------------------------------------------------------------------
Mark Evans                                   |evansmp@uhura.aston.ac.uk
+(44) 21 429 9199  (Home)                    |evansmp@cs.aston.ac.uk
+(44) 21 359 6531 x4039 (Office)             |
Newsgroups: comp.os.linux
From: torvalds@klaava.Helsinki.FI (Linus Torvalds)
Subject: Re: BUG REPORT (strace -p 1 messes up process tree) under 0.98.6
Organization: University of Helsinki
Date: Thu, 17 Dec 1992 12:17:35 GMT

In article <jpo.724582915@hrz.tu-chemnitz.de> jpo@my.informatik.tu-chemnitz.de (Joerg Pommnitz) writes:
>I have mentioned this bug to Linus when 0.98.6 was out. It's still
>in 0.99, just tried it yesterday. Hope someone who is familiar with
>the kernel can fix this.

Yes, sorry about forgetting about this bug.  The fix is very simple:
disallow tracing of init, even by root.  Init is special in other ways
anyway (you cannot kill init with any outside signal including SIGKILL
etc), as it has to run so that zombies can be given to somebody. The fix
is easy:

in linux/kernel/ptrace.c, function sys_ptrace(), add these two lines to
just after checking against PTRACE_TRACEME:

----- pseudo-patch -----
  		/* set the ptrace bit in the proccess flags. */
  		return 0;
  	}
+ 	if (pid == 1)
+ 		return -EPERM;
  	if (!(child = get_task(pid)))
  		return -ESRCH;
  	if (request == PTRACE_ATTACH) {
----- pseudo-patch -----

That may not have been what people wanted, but it's consistent with how
the rest of the kernel handles the init task.  So no, you won't be able
to trace init, but on the other hand you won't be able to mess with the
internal kernel process pointers either.. 

		Linus
Newsgroups: comp.os.linux
From: johnsonm@lars.acc-admin.stolaf.edu (Michael K. Johnson)
Subject: YAPPS
Organization: St. Olaf College; Northfield, MN  USA
Date: Fri, 18 Dec 1992 06:38:31 GMT


yes, it is "yet another /proc ps".

I took the classic /dev/kmem ps, the perl /proc ps, and the simple c
/proc ps posted recently, and made one c /proc ps.

The interface and output is that of the /dev/kmem ps, and the guts are
those of the simple c /proc ps (but majorly revised).  Unfortunately,
/proc is not quite up to fulfilling the role of /dev/kmem, but if I
start hacking on the kernel tomorrow, it may come closer ;-)

Right now there are a /lot/ of zeros as placeholders for unimplemented
stuff... ;-)  Try "ps -m", for instance...

I'd like to wait to release it until I know what Linus wants to do (or
wants me to do) further with /proc, and I have modified to to work
with that, but if anyone wants to play with it, mail me...

A /dev/kmem proc does have real advantages: for instance, a /dev/proc
filesystem can't really do the WCHAN field unless some real changes
are made to the kernel...  I just like a ps that doesn't require a
namelist file, and that doesn't have to be suid or sgid, and is thus
not a security risk, and doesn't have to be recompiled and updated all
the time.

michaelkjohnson
Newsgroups: comp.os.linux
Subject: Linux 0.99 broke /dev/lp0
From: cvadr021@vmsb.is.csupomona.edu
Date: 15 Dec 92 11:27:23 PST
Organization: California State Polytechnic University, Pomona
Nntp-Posting-User: cvadr021


	When I try: cat foo.bar > /dev/lp0 under my newly compiled kernel (0.99
without SCSI, with tcp, minix fs only) i get nothing but lp0 timeout on all of
the virtual terminals until the job is killed.

	It still works when I boot on linux0.98pl1, but not on the new kernel. 
Is this a bug, or is there something that I need to to to the /dev/* files when
I recompile?
 
---
						David Dhuyvetter
  						email: cvadr021@csupomona.edu
From: sjm86289@cs.tut.fi (Sami J. M{kinen)
Newsgroups: comp.os.linux
Subject: Re: rayshade for Linux
Date: 18 Dec 1992 15:38:14 GMT
Organization: Tampere University of Technology
Distribution: world
NNTP-Posting-Host: kaarne.cs.tut.fi


In article <1992Dec18.145522.25056@athena.mit.edu> AN72958%LTUVAX.BITNET@mitvma.mit.edu writes:
>I was wondering if anybody has had experience using the linux port
>of rayshade?

	I just compiled it myself.  Is there a ready-compiled binary
	available?

>My only real question is:
>what is the command line to view a *.ray file?
>do you have to configure your video card to use with rayshade?

	Argh.  Rayshade normally produces its output in RLE format.
	You better have Utah Raster Toolkit installed.  RLE pictures
	are 24-bit color images, and you can view them with xv or
	getx11.  The latter comes with Utah Raster Toolkit.  Needless
	to say, you need X11 installed and running to view the images.
	The .ray files are rayshade "code" that is needed in
	generating the image.  It typically takes several thousand CPU
	seconds to create one, and you better have 387 or 486.
	Xv does not support animation like getx11 does.

>when i type in (ie)   rayshade coin.ray    I get !#$!^%!%!%!^ characters
>and then a "(10434) lines processed" type output...  is this correct?

	Yes.  Rayshade dumps the RLE image into standard output. The
	diagnostic messages go into stderr, so you could say something
	like

		rayshade coin.ray > coin.rle

	or use the command line switch -O like this:

		rayshade -v -O coin.rle coin.ray |& tee coin.log

	-v means verbose output.

	Was this of any help?  IMO, this doesn't belong to c.o.l really.


-- 
// sjm
If a train station is where the train stops,
what's a workstation?
Newsgroups: comp.os.linux
From: irc@socs.uts.edu.au (Paul Hatchman)
Subject: Re: PATCH: (0.98.6) allow root to link/unlink directories
Keywords: kernel,patch,0.98.6,fs,link,unlink,root,directory,namei,standard,fix
Organization: Computing Sciences, Uni of Technology, Sydney.
Date: 16 Dec 92 08:02:46 GMT

torvalds@klaava.Helsinki.FI (Linus Torvalds) writes:

>In article <1992Dec14.213538.15934@tc.cornell.edu> Frank T Lofaro <fl0p+@andrew.cmu.edu> writes:
>>	I noticed that rm -d and ln -d don't work under linux (I tested under
>>0.98.6), even for root (they say Operation not permitted, unlink/link
>>gives EPERM as a return value). [ deleted ]

>Is there anybody out there that actually needs this? I'm just warning
>you that this patch won't get into the standard kernel unless somebody
>can come up with a truly good reason for it (I doubt there is any). 

I know RCS (some versions of it at least) uses this feature.

It recreates the source directory structure under your home directory
by hard linking directories.

Still it is nothing that cant be done with a symlink.

----
Paul Hatchman
pdhatchm@socs.uts.edu.au 
Newsgroups: comp.os.linux
From: jlnance@eos.ncsu.edu (JAMES LEWIS NANCE)
Subject: Re: Announce Floppy file system for normal users
Organization: North Carolina State University, Project Eos
Date: Sat, 19 Dec 1992 03:48:55 GMT

I posted the source code for a program to format/mount/unmount a floppy for
a normal user earlier today.  After I posted it, I realized that it has a
serious security problem.  It lets you choose the formatter you want to use,
ie mkfs, or mkefs, or what ever you want.  So you could choose bash or tcsh
and have a root shell running.  Not a good thing.  I will change it so that
it will only use mkfs or mkefs.  I also received some mail suggesting ways
to make it more secure.  I will incorporate these changes into it this
weekend, and put it on an ftp server if anyone is interested in it.


Jim Nance
Newsgroups: comp.os.linux
From: erc@unislc.uucp (Ed Carp)
Subject: Re: 0.99 Succes!
X-Newsreader: TIN [version 1.1 PL6]
Organization: Unisys Corporation SLC
Date: Fri, 18 Dec 1992 00:32:28 GMT

Vincent D. Skahan (vds7789@aw2.fsl.ca.boeing.com) wrote:

: >The moral of the story is, wait a week before deciding to upgrade
: >when a new version comes out.
: 
: ==> the moral also is that it you bust your butt and get a solution
: 	with as much pain as you probably went through, there are
: 	also probably dozens of us (me included) who don't want to
: 	feel the same pain and who would be greatly appreciative if
: 	you post what you did, so we know too.

Well, I also got bit by the kernel crash bug in 0.99, so I got the posting
by Linus and made the (very small) patch.  Now, everything works great -
hey, even my internal modem works now!  I read (and followed) the README,
as well as both ANNOUNCE postings by Linus, and had no problems.  I can't
quite understand why everyone is having so many problems, especially with
the kernel crash bug.  Did Linus' first post announcing 0.99 get out, and
his patch post not?  Or are there a lot of people out there just not paying
a lot of attention, preferring to post instead of READING the docs?
-- 
Ed Carp			erc@apple.com, erc@saturn.upl.com	801/538-0177

Who and what would you be if you went beyond your deepest fears?
Xref: sparky comp.os.linux:20385 comp.unix.bsd:10198
From: mharm@pollux.usc.edu (Michael Harm)
Newsgroups: comp.os.linux,comp.unix.bsd
Subject: Pros/cons of linux/386bsd?
Date: 14 Dec 1992 11:50:18 -0800
Organization: University of Southern California, Los Angeles, CA
Distribution: world
NNTP-Posting-Host: pollux.usc.edu

Hi folks.
We are trying to decide whether to go with linux or 386bsd for
our 486 machines.  Particular constraints are:

We don't have a lot of disk space.
We need X11.
We don't have a lot of memory per machine.
We don't have cd roms

Any information on the relative strengths/weaknesses of these
two systems would be a big help.  Please email info to harm@morue.usc.edu

Thanks much!

Mike Harm
harm@morue.usc.edu
Univ. of Southern California
---------------------------------------------------------------
"I agree that 'two times two makes four' is an excellent thing;
but if we are dispensing praise, then 'two times two makes five'
is sometimes a most charming little thing as well."
                 -Fyodor Dostoevsky,   "Notes From Underground"
Newsgroups: comp.os.linux
From: Jeff-Randall@uiuc.edu (Jeff Randall)
Subject: Re: Modem control (was Re: uucico not hanging up the telephone line)
X-Aka: Upholder
Reply-To: Jeff-Randall@uiuc.edu (Jeff Randall)
Organization: The University of Illinois at Urbana-Champaign (UIUC)
Date: Sun, 20 Dec 1992 06:10:41 GMT

bhenning@wimsey.bc.ca (Bill Henning) writes:
>I have a problem with logging in to my system... getty seems to set
>a case-mapping mode, showing all output in capitals, and not accepting
>logins... does not even print /etc/issue before each login: prompt.

>I am running a fairly vanilla Linux 0.98pl1 (SLS) with a USR v32bis
>modem. After getty times out, it prints /etc/issue, lower case output
>is available, and I can log in.

My guess is that you have getty setup improperly for you modem, what I would
guess is happening is that your modem is sending an "OK" through the line
and getty is saying "cool, someone trying to login... but the first character
is capital, I guess they don't have Lowercase capability" (this is the standard
assumption for all UN*X systems, if the first car is capital, all capitals
are printed and the capitals input are mapped to lowercase)

The solution to this would be to reconfigure getty/uugetty to ignore the
first "OK" sent from the modem and/or configure the modem to not echo 
-- 
Jeff-Randall@uiuc.edu (ASCII mail)           THIS IS _NOT_ CCSO'S OPINION!!!
jar42733@sumter.cso.uiuc.edu (NeXT mail)      If It were, It would've had a
wi.6580@n7kbt.rain.com (anon)                  more important name on it. =)
Newsgroups: comp.os.linux,comp.windows.x,comp.unix.sysv386
From: fmn@nevada.edu (FRANK NEEDHAM)
Subject: X on Enhanced VGA! (almost)
Organization: University of Nevada System Computing Services
Date: Sat, 12 Dec 1992 20:04:23 GMT

ok,

With a lot of help, X is almost working on this card, YES! Thanks Scott.

I have done the following, made sure the dir /tmp/.X11-unix exists, checked the
paths in etc/profile (they seem ok),cp'd xserverrc and xinit to the dir / and
used chown on them. 
I then cp'd system.twmrc to /, renamed it to .twmrc. Does this file also need 
to have the chown run on it?
When X is fired up, a grey screen with a cross-hatch pattern happens and it
stays. The <ctrl><alt><bkspc> sequence still doesn't kill the server.
Can anyone share some ideas on what I might try from here?

thanks,
-frank
From: probreak@wyatt.ksu.ksu.edu (James Michael Chacon)
Newsgroups: comp.os.linux
Subject: Re: gcc -g
Date: 19 Dec 1992 01:52:13 -0600
Organization: Kansas State University
NNTP-Posting-Host: wyatt.ksu.ksu.edu

dsc3pzp@nmrdc1.nmrdc.nnmc.navy.mil (Philip Perucci) writes:

>In article <1992Dec17.232305.24764@watson.ibm.com> rajat@watson.ibm.com (Rajat Datta) writes:
>>I'm running with the basedisk, libdisk, rootdisk, etc. that H.J. Lu
>>distributes with the GCC package.  Where can I find a working libg.a?
>>Meanwhile, any files I compile with gcc -g fails with segmentation
>>error; something to do with i/o, I believe, but haven't looked into it
>>any deeper.  Of course, this means gdb is pretty useless too.
>>
>>Any ideas?  Thanks,
>>-- 
>>rajat (rajat@watson.ibm.com)

>Could the response be posted on c.o.l?  I have the same problem.


>-- 
>===========================================================================
>  phil perucci      | "Any opinions expressed are solely my own views and 
>  ssb1pzp@digex.com |  do not reflect the position of any organization"
>===========================================================================

You can just link libc.a to libg.a and compile with -g just fine. All the 
libg.a stuff had in it before was all the functions compiled with -g.
This meant you could debug library functions if they broke.

James
Newsgroups: comp.os.linux
From: mdw@db.TC.Cornell.EDU (Matt Welsh)
Subject: Re: Suggestion Spliting Group
Organization: The Linux Inquisition, Propaganda Division
Date: Sat, 12 Dec 1992 19:21:35 GMT

In article <1992Dec12.044702.4234@exucom.com> cyberman@exucom.com (Stephen R. Phillips) writes:
>
>In hopes that this will prevent the 99-300 message per day from
>SWAMPING most poeple.  I suggest this group be split.

Sorry. You're too late. We already went through the grueling RFD and
CFV process; all groups failed the vote except for comp.os.linux.announce,
which now exists. 

USENET policy says that we can't bring up the proposal for another 6 months.
I'm surprised there are still people on this group who DIDN'T notice the
previous RFD/CFV, unless you just joined the group. :)

mdw

-- 
Matt Welsh     mdw@tc.cornell.edu     Cornell Theory Center
  "Go on, emote! I was raised on thought balloons!"
Newsgroups: comp.os.linux
From: cloos@theory.TC.Cornell.EDU (James H. Cloos Jr.)
Subject: Gateway 2000 Nomad 425SXL + Linux
Organization: Cornell Information Technologies, Ithaca, NY 14853
Distribution: comp
Date: Fri, 18 Dec 1992 03:16:59 GMT

Well, I placed an order this morning for a Gateway 2000 Nomad
notebook, with a 486SX/25.  Wanting 8Mo as I do, I had my choice of
letting them install the second 4Mo, which entailed a 3 to 4 week
wait, or having their upgrade kit (complete with anti-static gloves,
surface covers, etc.) sent after the notebook and installing it
myself.  This option means only a 7 to 10 day wait.  I'm sure you can
guess which choice I made.  ;-)

Once it arrives, I'll be crunching down the dos fs to one small
partition and making room for Linux.  Any suggestions on splitting,
say, 90Mo between root, swap, and home partitions?  (Or perhaps root,
swap, usr and home.)  I will install X once I get the 2nd 4Mo.

I guess I'll be able to run X in a 800x600 virtual, 640x480 real
screen size.  Will it support 6-bit greyscale, matching the LCD
display?  Also, although I won't have a monitor right away, the Nomad
can support 1Kx786 simultaneously with the LCD display.  Does anyone
know if Xfree86 will support that resolution on *this* machine?  (Ie.,
does anyone have either a Nomad or a TI TravelMate 4000 w/ Xfree up &
running?)

It comes with a PS/2 mouse port (or mouse/keyboard port?).  Any
suggestions for good 3-button devices for this?

Thanks for the info.  

-JimC
-- 
James H. Cloos, Jr.		include <std/disclaimers.h>
Cloos@Theory.TC.Cornell.EDU     include <std/qotd>
Cloos@Batcomputer.UUCP 		Phone:  +1 716 866-5249
Cloos@CrnlThry.BITNET 		Snail:  POBox 1111, Amherst, NY 14226-1111