HDTenEightyP/NetNews huggingface dataset:
From: bergstro@src.honeywell.com (Pete Bergstrom)
Subject: Re: [Q] UseNet on Linux
To: comp.os.linux
Posted-Date: Wed, 23 Dec 92 12: 10:18 CST
Organization: mailEnteringNews at Honeywell SRC
Date: Wed, 23 Dec 1992 18:10:18 GMT
Received-Date: Wed, 23 Dec 92 12: 10:20 CST

vince@halcyon.com (Vince Skahan) wrote:
>robc@Newbridge.COM (Rob Craig) writes:
>>I'm looking for documentation on how to get Linux setup for a UseNet feed.
>>I've installed SLS 0.99 and it seems to have most of the necessary items
>>(eg. elm, trn, uucp) but I need more documentation on how to use some of
>>them.  I've got no problem with reading news and sending mail locally, but
>>I don't have a clue how to setup for a feed.
>>...
>
>...
>
>If you can drop about $25.00, the O'Reilly+Asociates book "managing
>uucp and USENET" is that best one I've found.  You can also read the
>news.admin and news.software hierarchies since you apparently have other
>access to USENET.

I second the ORA book nomination - but be absolutely sure you get the
most recent edition (mine is dated 10/92 and is about 75% thicker than
the editions other people here have). It covers CNews fairly well,
from where I stand.

>[..Peter, if you're reading...is there a way to come up with a set of
>	extremely optional disks for SLS where we could provide this 
>	kind of information ???..]

Yes, please. How about 'd' for documents or 'm' for miscellaneous.

Pete Bergstrom
Newsgroups: comp.os.linux
From: twod@socrates.demon.co.uk (Ian A Parkin)
Subject: Re: Question and Observations 
Distribution: world
Organization: Realizing Relentlessly
X-Mailer: Simple NEWS 1.90 (ka9q DIS 1.19)
Date: Thu, 31 Dec 1992 22:51:05 +0000

Please no flames.

This is purely something that came to mind when reading some of the comments 
in this thread.

I installed 0.98 SLS the other week and am still experiencing 'permission
problems' ( plus some others - X ) but as a relative newcomer to eunuch system 
administration I see these as a blessing in disguise. It gives me the chance to
play with a eunuch system configuration. By doing this you learn certain 
rules / things :

 - Always backup before you make ANY changes;

 - When I said always backup I mean ALWAYS BACKUP;

 - Think about what you are doing, and do you really want to do it. Will
	it achieve what you want ?;

 - What are you going to do if things go horribly wrong ?;

 - The power, and possible misuses of a root login;

 - Learn how to restore, and apply the backups you have made - permissions &
	setuids especially;

 - Exactly what goes into a system administration job.

These are all important points - to my mind at least.

Moral ( Brady Bunch Punchline ) : OK SLS is not yet perfect but it's damn good.
So please do not critise, just use, enjoy, and learn.

Anyway thanks for your time, hope this is not diversifying the thread too much.

Respect to the laudable efforts of **everyone** involved with linux at **all**
levels. 

It's free, it's fun, and lets all have fun with it, but lets be careful out 
there !!

-------------------------------------------------------------------------------
			It's not real you know
-------------------------------------------------------------------------------
Newsgroups: comp.os.linux
From: marcf@nexus.yorku.ca (Marc G Fournier)
Subject: problems with logging in...FIXED : ))
Organization: York University
Date: Thu, 31 Dec 1992 00:12:40 GMT

Hi...

	Thanks to everyone who helps...I got dial in to work :))

	For those that are having similar problems, and still 
haven't found the answer...here is what I have done/replaced
so far on the SLS distribution:

	1 - installed sysinit.tar.Z
	2 - installed getty_ps204.tar.Z
	    w/ /etc/default files
	3 - ran getty (still haven't played with uugetty)

	When you try and log in...login with N81 instead of
E71 (my old system was the other way around *sigh*)

	Next question.  I just 'installed' the patch for
0.99 to bring it to patch level 1.  One thing is new in the
config script...something about 486 optimization.  Default setting
is to do it (-m486)...I just want to confirm...Linux?  Are you
running on a 486 that you have this defaulted to yes?  I'm on a
386, so I presume that settting this to no is appropriate?:)

Thanks load folks...

Marc
Newsgroups: comp.os.linux,comp.windows.x,comp.windows.x.i386unix
From: fmn@nevada.edu (FRANK NEEDHAM)
Subject: X Hangs
Organization: University of Nevada System Computing Services
Date: Tue, 22 Dec 1992 18:09:01 GMT

After X cranks up, the screen hangs with xclock trying to start and no input
is accepted from the mouse.

There have been references to this problem before, I know. I can't recall the
solution to this. Can someone kindly tell me what to look at to solve this?

thanks,
-frank
Newsgroups: comp.os.linux
From: 12100z@d1.dartmouth.edu (Tom Buskey)
Newsgroups: comp.os.linux
Subject: Re: Linux and OS/2
Date: 29 Dec 92 06:45:50 GMT
Organization: Kendo School of Indiscriminate Grappling
Newsreader: MS Windows WinVN

In article <RwciwB1w164w@uuisis.isis.org>, evanc@uuisis.isis.org (Evan Champion) says:
>
>I would like to run Linux and OS/2 together on the same machine.  Is it 
>possible to boot linux in a virtual DOS machine?  If not, could someone 
>direct me to a free unix that I could do that?  What I really want is 
>something that I can boot to do UUCP and maybe a few other things with that 
>there are no good OS/2 version of and porting is somewhat difficult because 
>of the platform-specific nature of the programs.  Any help would be greatly 
>appreciated!
>
>Evan
------------------------------------------------------------
>               UUISIS Electronic Mail Service (Ottawa)  
>                           613-823-6539

I'm running linux & OS/2 on the same machine, but not at the same time.  I really
don't think any unix will run within an OS/2 DOS window/box.  However, if you
just want to give OS/2 some unix flavor, lots of stuff has been ported.
There's BASH, GNU Emacs, KSH, GNU C, g++, most of the other GNU stuff,
BISON, Flex, and SC.  There is also UUPC, a port of UUCP to DOS *and* OS/2
(haven't used it, it's been around awhile).  You could also try running other
UUCP for DOS (like Waffle) within a DOS box.
 
Given all the Unix stuff that's been put on OS/2, I'm not sure porting is all that
difficult.  OS/2 2.x has flat model 32bit memory and long filenames w/ HPFS.  If
you can port the full GNU Emacs, you can probably port most other general stuff.
Newsgroups: comp.os.linux
From: wto@cbnewsg.cb.att.com (William T. O Connell)
Subject: Undefined C library functions
Organization: AT&T
Date: Sat, 26 Dec 1992 21:52:16 GMT

Unable to login, get the following message after entering any login :
	login: root
	Undefined C library functions
		1. ulimit (use getrlimit/setrlimit instead).
		2. light C shared image (use the real one instead).

	login:

I normally use xdm from my rc file, which works fine. I also don't
have problems building any executables (i.e. kernel) But, when I
try to login from a getty in inittab, get the above message refering
to undefined library functions.

Note that I recently updated to libc.so.4.2. But, I don't know
if this library is causing the problem because I inadvertently
deleted some other libaries but restored them from my SLS 99 
distribution. Maybe I have a symbolic missing link? or missing library?

Any ideas on what is causing this during the login process.

- Bill     wto@ihlpx.att.com
Newsgroups: comp.os.linux
From: almesber@nessie.cs.id.ethz.ch (Werner Almesberger)
Subject: BSS initialization (was Re: IMPORTANT [BUG in 0.99] Re: [ANNOUNCE]: linux version 0.99)
Keywords: kernel linux 0.99, bss initialization
Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
Date: Fri, 25 Dec 1992 00:26:26 GMT

In article <20367@ksr.com> zdenek@ksr.com (Zdenek Radouch) writes:
> Also, why does the init code run in 16-bit mode? I'd assume that the first
> five instructions in the boot code would put the processor in some
> reasonable mode.

The reason why so much is done in 16 bit mode is probably because it's
easier to access the BIOS this way and because there are comparably few
occasions where 32 bit arithmetic is necessary.

About zeroing BSS: LILO currently does that (unstripped kernels since 0.3,
traditional kernel images since 0.6 (*)). However, it might be a good idea
to handle it in setup or in the kernel itself, because Shoelace, the
floppy boot sector and probably also BOOTLIN don't initialize BSS.

(*) It may miss a few bytes when using traditional kernels, but this
    shouldn't really be a problem. I might fix this inversion 0.8.

- Werner
-- 
   _________________________________________________________________________
  / Werner Almesberger, ETH Zuerich, CH      almesber@nessie.cs.id.ethz.ch /
 / IFW A44  Tel. +41 1 254 7213                 almesberger@rzvax.ethz.ch /
/_BITNET:_ALMESBER@CZHETH5A__HEPNET/CHADNET:_[20579::]57414::ALMESBERGER_/
From: hedrick@geneva.rutgers.edu (Charles Hedrick)
Newsgroups: comp.os.linux
Subject: Re: Old Libc, can it be tossed?
Date: 4 Jan 93 05:08:56 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

tfoley@camaro.uucp (Tim Foley) writes:

>Can the older libc.so.4.0 & libc.so.4.1 be deleted if you have libc.so.4.2?
>Also, do I have to link libc.so.4.2 to libc.so.4.1 & 4.0 if I do?

The copy of tcsh I have, which seems to be the most recent, explicitly
asks for libc.so.4.1.  If you make it a copy of libc.so.4.2, tcsh
complains that it's incompatible.  Other than tcsh, I think most
programs use the symlink libc.so.4, and so wouldn't care if 4.1 is
gone.
Newsgroups: comp.os.linux
From: tym@dibbler.cs.monash.edu.au (Tim MacKenzie)
Subject: Re: after compiling kernel...then what?
Organization: Computer Science, Monash University, Australia
X-Newsreader: TIN [version 1.1 PL8]
Date: Thu, 31 Dec 1992 07:30:59 GMT

Marc G Fournier (marcf@nexus.yorku.ca) wrote:
>	I just successfully recompiled the kernel in Linux :)

>	Now what do I do with it?  It just leaves it in /usr/src/linux.
>I copied it over /Image...is that right?

Not something I would do... I generally copy it into 
/Image.<something descriptive> (eg Image-991-tcp Image-990-test)
then remove the (hard) link that is /Image and make a new /Image link:
'ln Image.<name> Image'
Then I add a lilo config entry for the new kernel (and remove any that
are for kernels that I've deleted to make room :) and finally run
the lilo install script. (the default linux kernel loaded is always /Image).

This way I can always tell which kernel I am running (it is the one
that has 2 links: /Image and /Image.<descriptive name>) and can get
back to any of my backup kernels if something goes wrong.
[If you're not running LILO (version 0.7 I think) then DO!  I've never had
 any problems with it and it's saved a lot of potential hassles caused by
 dud kernels (my own fault usually:)]

Of course, you should aways have a couple of disks that you can boot off
in case your hard drive goes ga-ga. (H Lu's boot/root disk or a1 and a2
from the SLS distribution).
--
-Tim MacKenzie (tym@dibbler.cs.monash.edu.au)
Newsgroups: comp.os.linux
From: lam836@cs.cuhk.hk (Savio Lam)
Subject: Booting from second hard disk?
Organization: Faculty of Engineering, The Chinese U. of Hong Kong
Date: Wed, 23 Dec 1992 07:31:22 GMT

Sorry if this is an FAQ.

I have two IDE hard disks, Linux is installed on the second one. Besides
Lilo, do I need a boot switcher in order to boot from the hard disk? Is
there any boot switcher that can let me boot from the second hard disk?

Regards,
Savio Lam.

email: lam836@cs.cuhk.hk
From: mycroft@hal.gnu.ai.mit.edu (Charles Hannum)
Newsgroups: comp.os.linux
Subject: Re: [Q] How to change text video mode in SLS startup
Date: 26 Dec 92 12:08:58 GMT
Organization: /etc/organization
NNTP-Posting-Host: hal.gnu.ai.mit.edu


In article <1992Dec25.211549.15414@mnemosyne.cs.du.edu>
amartell@nyx.cs.du.edu (Alex Martelli) writes:
>
> It comes up extended without asking.  rdev -v /vmlinux -3, now rdev
> -v says mode is 65553, and STILL it does not ask - comes up extended
> anyway.

The boot sector in /vmlinux is ignored.  Try `rdev -v /dev/hda -3' (or
`rdev -v /dev/sda -3').

-- 
 \  /   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: wyvern@gnu.ai.mit.edu (The Wyvern)
Subject: libc.a errors with gcc 2.3.3
Keywords: gcc
Organization: Free Software Foundation
Date: Fri, 1 Jan 1993 01:39:16 GMT

I just installed gcc 2.3.3 (The 486 version) and everything seems
fine except for one problem. When I try to compile hello.c
with the -static option, I get these errors:

/usr/lib/libc.a(printf.o): Undefined symbol _stdout referenced from text segment
/usr/lib/libc.a(printf.o): Undefined symbol streambuf::vform(const char *, void *) refer
 *) referenced from text segment
/usr/lib/libc.a(atexit.o): Undefined symbol _malloc referenced from text segment
/usr/lib/libc.a(exit.o): Undefined symbol __cleanup referenced from text segment

This is using the lib486-4.2.TZ from tsx-11.mit.edu:/pub/linux/GCC/486
and 486 compiler. When linking with shared libs, jump or nojump, it works
fine. The problem seems to be only with the static version of 486 libc.
How can I fix this?

-->Configuration
i486-33 system
8mb RAM
200mb IDE HD
Linux 0.99.1, GCC 2.3.3-486
libc.so.4.2 compiled from jump-4.2.TZ sources

Also:
  Is it safe to delete /usr/lib/shlib/jump and nojump?
  I believe these are the gcc 2.2.2d directories for
  the jump libraries and have been replaced with
  lib*.ca and lib*.sa in /usr/lib. Is this correct?


Newsgroups: comp.os.linux
From: engel@sj.ate.slb.com (Mike Engelhardt)
Subject: SPICE for Linux
Organization: Schlumberger ATE, San Jose
Date: Mon, 21 Dec 92 23:23:28 GMT

helz@ecn.purdue.edu asks:

> Has anyone gotten spice for Linux compiled?  [...]

I have compiled and use SPICE3d2 and SPICE3e2 on Linux.  3d2
isn't too hard to compile, though the X11 stuff was a mess.
3e2 is difficult to build.  The reason is that they don't use
a standard makefile scheme.  It is built from shell scripts
which create new files which are concatenated together with
other files into a pipe which is fed to make, which recursively
calls this script to make new files and pipes which are feed
to a another invocation of make.  The scope of variables under
GNUutilites is different than anticipated by the auther(s) of
this build scheme.  It's difficult to debug.  One thing that
can happen is your hard disk gets filled with empty directories.
It was easier to build by hand(even though there are 719 .c
files) than to use the intended build scripts.  However, I did
get the scripts working, because I wanted to be able to easily
hack on SPICE.

Each directory has a file called 'makedefs' instead of 'Makefile'.
I fixed the problem by resetting the offending variables in each
makedefs file.  There are also syntax errors in the distributed
scripts to fix.

Other than that, there's a few hours of fixes to the source code,
most of which are obvious like changing "*<string_pointer> = NULL"
to "*<string_pointer> = '\0'" to suppress the warning.  There
were, however, a few real fixes as I recall.

I don't expect the demand for this is very high, so I wouldn't
pursue uploading my work to an ftp site.  Also, I won't get
involved in copyright or export issues of SPICE.  The latest
version of SPICE is 3f2, but the policy has been to not have it
available via anonymous ftp.  I use a copy of SPICE3e2 I got
from Italy (The Italians do alot of original work done with it,
too.)

But if you need to get SPICE up and running, e-mail me and I'll
try to help get you set up, though.

Mike Engelhardt  engel@sj.ate.slb.com

/*
 *  For those who suffered through this and don't know what
 *  SPICE is:
 *
 *  SPICE is a program used to simulate the behavior of
 *  electric circuits.  It has been an extremely successful
 *  simulator.  The idea is you give it a circuit(as a list of
 *  parts and semiconductor device parameters in text) and tell
 *  it to calculate what it does for the first millisecond of
 *  being turned on.  The best introduction I've seen on the
 *  application of this program is Lawrence Nagal's Ph.D. thesis.
 */
Newsgroups: comp.os.linux
From: sbeeler@acs.ucalgary.ca (Stan W. Beeler)
Subject: Newbie X question
Date: Tue, 22 Dec 92 20:37:39 GMT
Organization: The University of Calgary, Alberta
Keywords: X Trident


  
  
  I have been working away at getting X visable on my system and things
  seem to be progressing well except that whenever I exit from twm the
  system refuses to return to character mode. Hence I am doing a lot of
  blind shutdowns. If I restart X all is well with the world again. 
  I also cannot seem to define my card as "tvga8900" in the Xconfig
  file. If I do so I simply get a blank screen. My documentation for
the card actually says 8900c Is this an important difference? I am
using SLS 98.p5(?) on a 486 dx with 8 meg ram and a large swap
partion. My monitor is a Viewsonic 5(?) 
  I have included at the end of this note a redirected error output from
  a sample session. 
  
  Stan Beeler
  Dept. of English
  University of Calgary
  Canada, The Frozen North
  
  
  
  waiting for X server to shut down xterm:  fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
  XIO:  fatal IO error 32 (Broken pipe) on X server ":0.0"
        after 47 requests (38 known processed) with 0 events remaining.
        The connection was probably broken by a server shutdown or KillClient.
  no SIOCGIFCONF
  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: tvga8900 (mem: 1024k numclocks: 8)
  VGA256:   clocks: 25 28 45 36 57 65 50 40
  VGA256: SpeedUp code selection modified because chipset != et4000
  VGA256: SpeedUp mode selected (Flags=0x30)
  
  
  xinit:  Interrupted system call (errno 4):  Client error.
From: sdw@meaddata.com (Stephen Williams)
Newsgroups: comp.os.linux
Subject: Making a Bootable disk with ram-disk root
Date: 22 Dec 1992 17:31:27 GMT
Organization: Mead Data Central, Dayton OH
NNTP-Posting-Host: bugatti.meaddata.com
X-Newsreader: Tin 1.1 PL5

Is anyone willing to tell me how to make a boot disk with a ramdisk
root?

I think I know how to make a ramdisk, set the size, make it the
root device (all with rdev), etc.

I don't know if there is standard code (to insert into the Kernel's
main?) for loading the contents of the ramdisk from the rest of the
boot disk.

I need to build something like the SLS, only with a custom kernel and
particular files.


Thanks
sdw
--
Stephen D. Williams  Local Internet Gateway Co.; SDW Systems 513 496-5223APager
LIG dev./sales       Internet: sdw@world.std.com CIS 76244.210@compuserve.com
OO R&D Source Dist.  By Horse: 10028 Village Tree Ct., Miamisburg, OH 45342
GNU Support          ICBM: 39 34N 85 15W I love it when a plan comes together
Newsgroups: comp.os.linux
From: dld54032@uxa.cso.uiuc.edu (Dave Dribin)
Subject: X hangs after loading
Organization: University of Illinois at Urbana
Date: Tue, 22 Dec 1992 23:49:05 GMT

Hello,

  I have a problem with X working after getting Xconfig setup.  I think
my Xconfig file is setup right because after typing startx, it eventually
gets to a blue background.  The display looks semi-normal so far.  Then,
I think it tries to put up an xterm or xclock or something, becuase I get
these red bars with white borders around them.  I can only assume that
this is twm's work.  Now it stops as if it were all loaded and ready to
go, but I have no xterm and must exit via alt-ctrl-backspace.

  I had enough of messing around with the color, and just wanted to see
if I could get mono X working, and I got a could not find screen, or no
screen available error, or something like that.  What's up?

Any ideas?  I'm clueless.  Oh, yeah.  The mouse doesn't work either. Thanx
in advance for any help.

Dave

-- 
Dave "Dribs" Dribin         |"Back off man!!!... Don't make me use this...
dribs@uiuc.edu              | One step closer, I'm warning ya... Don't make
"Happy, Happy!! Joy, Joy!!" | me use it!  Now you've done it!  You...
                            | force me to use it!!!"
From: jdg00@ccc.amdahl.com (Josh Grosse)
Newsgroups: comp.os.linux
Subject: X via ka9q/slip
Date: 22 Dec 92 21:42:10 GMT
Reply-To: jdg00@amail.amdahl.com (Josh Grosse)
Organization: Amdahl Corporation, Sunnyvale CA

I've heard via e-mail that it may be possible to use ka9q to drive X
protocol.  Is there anyone out there that has done this and who can
point me in the right direction?

-- 
-----------------------------------------------------------------
Josh Grosse                                jdg00@amail.amdahl.com
Amdahl Corp.                               313-358-4440
Southfield, Michigan
Newsgroups: comp.os.linux
From: mchen@uranus.cs.psu.edu (Michael Chen)
Subject: Slight confusion w/SLS 0.99
Distribution: comp
Date: Tue, 22 Dec 1992 01:34:16 GMT

   Okay, I've installed the minimal system (since I'm downloading at 2400 baud)
and the login tells me Welcome to Lunix 0.98p5.  The kernel DOES say 0.99-47
on boot, however... how do I change this message?
   Also, what is shoelace? It doesn't seem to be in the minimal system, nor is
adduser.

-- Mike
--
_____________________________________________________________________________
| Michael Chen			| From the depths of our most lucid horrors |
|				| spring our fond hopes and pure desires... |
| mchen@cs.psu.edu		| except what comes from HELL! :-) 7/23/92  |
\_______________________________\___________________________________________|
Newsgroups: comp.os.linux
From: wto@cbnewsg.cb.att.com (William T. O Connell)
Subject: Internal compiler error while building kernel
Keywords: gcc
Organization: AT&T
Date: Mon, 28 Dec 1992 01:02:28 GMT


When building the kernel (via 'make all'), I occasionally get the 
following error message and compilation stops:
	gcc: Internal compiler error: program cc1 got fatal signal 4

Then, I re-type 'make all', and the build will continue successfully.
This may happen two or three times during building the entire kernel.
Once built, the kernel works fine.

I've only seen this on large builds (i.e. kernel).
What is causing this compiler error? Any ideas?

I am using .99p1 and recently loaded libc.so.4.2 because of sigaction.
The compiler I am using is 2.2.2d.

- Bill   	wto@ihlpx!att.com



Newsgroups: comp.os.linux