HDTenEightyP/NetNews huggingface dataset:
From: pca306c@nella3.cc.monash.edu.au (E Elu)
Newsgroups: comp.os.linux
Subject: UUCP
Date: 3 Apr 92 00:46:35 GMT
Organization: Monash University


I am looking for a reliable port of a uucp system to Linux so I can set
up a bbs. I have tried Taylor version 1.3 with no luck, and also a couple of
the minix systems still with no sucess in getting all the modules to port
across. 

Any suggestions or diffs would be greatly appreciated.


Thanky in advance

Ernie Elu
From: knapka@athena.cs.uga.edu (Joseph Knapka)
Newsgroups: comp.os.linux
Subject: Re: virtual consoles/pty's
Date: 17 Apr 92 16:16:24 GMT
Organization: University of Georgia, Athens


>>
>>Nope. ALT-Fn selects virtual console n, which is /dev/tty[n].  
>> 
>
>So that means I have eight virtual consoles available, but I can only
>use four of them with Alt-Fkey sequences... how can I use vc's 5 thru 8?
>
>Thanks^2,
>
>Joseph

Sorry to reply to myself, but a little expirimentation revealed that
the answer is, "You use the getty program to enable logins on the
other vc's, and then use Alt-F[5-8] to get to them..."

Joseph
From: dcuka@cbnewse.cb.att.com (david.a.cuka)
Newsgroups: comp.os.linux
Subject: Linux Printer
Summary: Does it work?
Keywords: linux, printer
Date: 14 Apr 92 14:31:16 GMT
Followup-To: comp.os.linux
Organization: AT&T


I tried last night to get my parallel printer working with linux.  Based
on some previous postings, I tried 

	"mknod /dev/lp0 c 6 0"

followed by a test

	"cat /etc/rc > /dev/lp0"

I got a "ENODEV", so I tried using minor device number 1, which did not
work either.  Is there some addtional setup that I am missing?  I
am running on v0.95a. The printer is a Panasonic KXP-1024 parallel
printer.  Is there a "Guide to installing a printer" yet?

DAC
Obligatory Praise: "Linux is Great!"
Newsgroups: comp.os.linux
From: drew@caesar.cs.colorado.edu (Drew Eckhardt)
Subject: Re: Linux Drivers and Kernel question.
Organization: University of Colorado at Boulder
Date: Tue, 7 Apr 1992 06:02:52 GMT

In article <2208@ariel.its.unimelb.EDU.AU> rab@tauon.ph.unimelb.EDU.AU writes:
>
>What I've been wondering is this: I suspect many of us would love to have X running
>on isolated PCs: is it possible to cut out all the X networking stuff ? Would this
>reduce the size of the server by very much ? Then we could have 2 X binaries to ftp ...
>

Nope.  X clients talk to the server through sockets - it doesn't matter
weather the socket is unix domain or something else, the same code has 
to be there.  

The biggest bloat in 'X' comes from libraries statically linked into 
each X file.

However, we now use shared libraries, which eliminates this problem.


Xref: sparky comp.os.linux:204 alt.os.linux:2302
From: liljeber@klaava.Helsinki.FI (Mika Pekka Liljeberg)
Newsgroups: comp.os.linux,alt.os.linux
Subject: Tcsh 6.01 for Linux
Date: 5 Apr 92 21:45:01 GMT
Distribution: comp,alt
Organization: Department of Computer Science, University of Helsinki, Finland

Hi, everyone!

I just uploaded tcsh 6.01 to funic.funet.fi. It should become
available in a few days.

The package contains a runnable binary, some documentation and
cdiffs against the official tcsh 6.01 release.

I compiled tcsh with GCC 2.0 (haven't had the nerve to try 2.1
yet ;-) ) using static libraries. I haven't tested it very
extensively, but I found no glaring bugs either. If you come
across any, be sure to drop me a note.

Have fun!

		Mika
--
Mika Liljeberg			Email:	liljeber@kruuna.Helsinki.FI
Helsinki University			Mika.Liljeberg@Helsinki.FI
Dept. of Computer Science
-- 
Mika Liljeberg			Email:	liljeber@kruuna.Helsinki.FI
Helsinki University			Mika.Liljeberg@Helsinki.FI
Dept. of Computer Science
From: bvickers@bonnie.ics.uci.edu (Brett J. Vickers)
Subject: Adaptec & Swap space
Newsgroups: comp.os.linux
Organization: Univ. of Calif., Irvine, Info. & Computer Sci. Dept.
Date: 16 Apr 92 04:28:31 GMT

I recently installed Linux 0.95c+, and I have been unable to set up
swap space using either a separate partition or a swap file.  I'm
using an Adaptec SCSI card and SCSI target 1 for my file system
and the swap partition.  mkswap seems to work ok, but when I run swapon,
I get the "Unable to find swap-space signature" error.

Someone else who was using an Adaptec SCSI card posted that they
were having similar problems, and this leads me to wonder if swap
space and the Adaptec driver don't go together very well.

Can anyone confirm my suspicions?

--
bvickers@ics.uci.edu | "Wherever the real power in a Government lies, there
brett@ucippro.bitnet |  is the danger of oppression." - James Madison
From: aclark@netcom.com (Al Clark)
Newsgroups: comp.os.linux
Subject: Re: When will "Linux 1.0" come to the world ?
Keywords: stable
Date: 14 Apr 92 18:07:32 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest)

In article <1992Apr13.215610.22632%dr794348@cs.nthu.edu.tw> dr794348@cs.nthu.edu.tw (mr79) writes:
>Linux 0.95c is still in the period of development.
>Everything is rather unstable.
>when will Linux 1.0 come to the PC 386/486 world ?
>
>			J.H.Lin

The only thing unstable is the configuration management [ :-) ].  Linux
is actually more stable than the early (1.06) Interactive Systems Unix
386/ix that I have.  The only thing I miss is the ability to run DOS
programs.  But I find I would rather have Linux and do some rebooting.
-- 
Al - aclark@netcom.com - My opinions are my own.
      *** Practice random kindness and senseless acts of beauty! ***
From: chojnows@osiris (Brian Chojnowski)
Newsgroups: comp.os.linux
Subject: mtools and messed characters on hard boot   help.
Date: 17 Apr 92 03:53:52 GMT
Article-I.D.: ux1.1992Apr17.035352.8699
Organization: University of Illinois at Urbana


	I have finnaly gotten my hard drive configured to hold both the dos
and Linux OS's invisible to each other. A friend of mine found a neat
utility that let me select f1,f2, etc.. on bootup, which partition to boot
from. I gave up on figuring out how to create a linux only boot partition,
so I wound up making a 3m dos partition, and used bootlin. If anyone knows
how to make Linux boot from the hard drive sans Dos, it would be neat. I
know have 2 problems: 1) I grabbed the binaries for mtools from
tsx-11.mit.edu, and when they are run, I always get the message 'Device not
found -- please specify device' or something like that. What have I not done
to get these to work? and secondly, when booting from floppy, everything
works fine, including the SVGA menu. But from the hard drive, after bootlin
spits out its 3 messages, I get a line of garbage characters. When I press a
key other than enter, it finishes loading in 80x20 mode, hitting return
doesnt give me a menu, I get 80x43 mode. Has anyone else had this problem
after useing bootlin to boot?

	Brian Chojnowski
	-please pardon my grammar, I was in a hurry.
Newsgroups: comp.os.linux
From: britt@leland.Stanford.EDU (Britt Park)
Subject: libtermcap.a bugs?
Summary: Are there known bugs in libtermcap?
Keywords: termcap libtermcap 
Organization: DSG, Stanford University, CA 94305, USA
Date: Tue, 7 Apr 92 22:45:43 GMT


I was trying to compile my much beloved version of uEmacs 3.8, (I've made
several changes to it and am very fond of it.) and found that it compiles
but doesn't work under GCC 1.40.  Does the GCC 1.40 libtermcap have a known
bug in it?  I've traced the problem to that vicinity.  Thanks.

					Britt
					britt@cb-iris.stanford.edu


Newsgroups: comp.os.linux
From: boutell@pecan.udel.edu (Nefaratu the Boutellian)
Subject: Suggestion for Graphics
Organization: University of Delaware, Newark
Date: Fri, 17 Apr 1992 19:36:27 GMT

To those who want a graphics library for Linux, you might profit from
a study of the source code to the new 16/256-color graphics library
for DJGPP, the port of GCC to 386-mode DOS. This new library came
out with version 1.06 and from working with betas I know it to be
quite powerful, but not a humungous remote - display system like X.

-T

-- 
-- Tom Boutell
President, Technology House, U of Delaware. Got a similar resident group at your
school? Please get in touch!
INTERNET:boutell@freezer.cns.udel.edu SNAIL: P.O.Box 295, Newark, DE 19715
From: kraft@gac.edu (Steven Kraft)
Newsgroups: comp.os.linux
Subject: Re: Local Bus support?
Date: 11 Apr 92 22:47:59 GMT
Article-I.D.: gacvx2.1992Apr11.164800.799
Reply-To: kraft@gac.edu

In article <1992Apr11.161526.3872@rs6000.cmp.ilstu.edu>  writes:
! Hello netters.  I was just curious as to whether or not LINUX supports
! 32-bit local bus cards, such as 32-bit video cards and/or disk controllers.
! This is _not_ the same as EISA.  I understand that programs running over
! the bios have no problem, but since LINUX manipulates the hardware directly
! I wasn't sure.
! Jean Liddle
! Computer Science, Illinois State University 
! e-mail:  jliddle@rs6000.cmp.ilstu.edu
!          jliddle@katya.acs.ilstu.edu

I have an Orchid Superboard 486/33 with an Orchid Fahrenheit 1280/D 32 bit  
local bus video card.  Linux 0.12 works fine on it.  I hope to get 0.95c  
installed as soon as I can, and I am sure that will also work.  

However, the fancy S3 accelerator chip functions of the Fahrenheit 1280/D are  
not yet accessible to Linux since no driver has been written yet.  I hope to  
write that driver myself in the future, but I do not have enough info yet about  
that card.  I have ordered an S3 Programming Manual, and I will have it in a  
few days.  I cannot say how long it might take to write the driver though...

For now my video card looks just like any plain VGA card as far as Linux is  
concerned.

However, a local bus disk controller may be a different matter.  Many variables  
are involved, and I have no experience here.

Steven Kraft   KRAFT@GAC.EDU  Micro/Minicomputer Consultant, Comp Sci major
Gustavus Adolphus College
Xref: sparky comp.os.linux:348 alt.os.linux:2427
From: sweh@spuddy.uucp (Stephen Harris)
Newsgroups: comp.os.linux,alt.os.linux
Subject: Problems compiling 0.95c+
Date: 11 Apr 92 18:49:53 GMT
Organization: Spuddy's Public Usenet Domain

Had a few problems compiling the c+ version, patching from 0.95c

These were:
(1) Lack of include/checkpoint.h, needed in char_dev.c
    I just "touch"ed this file, to create it, and the compilation worked.
    What should this include file do????

(2) Boot image finally made recognised my two printer ports then crashed
    in a similar way to other people have described.
    I compiled using 1.40 (newgcc.tar.Z)
    Looking at the stderr from the makefile I found a lot of silly lines
    "unknown option M%I%" or something like that.
    (I already uncommented the GCC_OPT line)
    Using the gccbin.tar.Z version of 1.40 the error became "unknwon
    option -O6
    Removing the "6" and recompiling produced a working bootable kernel.

mknod lp0 c 6 1 / mknod lp1 c 6 2, then my printers both worked.

Hope this helps people with a similar problem.
-- 
                               Stephen Harris
               sweh@spuddy.uucp    ...!uknet!axion!spuddy!sweh

 * Meeeeow ! Call Spud the Cat on > +44 203 638780 < for free Usenet access *
From: 9041592@zeppo.cs.su.OZ.AU (Bernard Joseph Gardner)
Newsgroups: comp.os.linux
Subject: Apology and question
Date: 15 Apr 92 06:54:19 GMT
Reply-To: 9041592@basser.cs.su.OZ.AU (Bernard Gardner)
Followup-To: comp.os.linux
Organization: Basser Dept of Computer Science, University of Sydney, Australia

Well, first, an apology for the multiply included garbage in that previous post,
I really hate the news software here :)

Anyway, my real question is with regard to cut and paste using the mouse. Has
anyone implemented such a beastie? 

If not, I might make it one of my pet projects.

Bernard.
From: gt0449a@prism.gatech.EDU (Rob Coleman)
Newsgroups: comp.os.linux
Subject: Parse error
Date: 13 Apr 92 03:32:52 GMT
Organization: Georgia Institute of Technology

I had the parse error problem for quite a while, but had I been able to
see through my own stupidity, I would have fixed it a lot sooner.  The
problem began with the distribution version of tar (at least the one
that I got on the .95a root disk) being bad.  It would randomly replace
colons (:) with null bytes ($0), and in an executable, this really
mangled the file.  I've known some people to never have a problem with
this version of tar, but obviously a priviledged few run into it :)  I
was instructed to get either the tar in the utils.tar.Z file on tsx-11,
or just build a new tar (from tar-1.10.tar.Z at prep.ai.mit.edu) and use
them rather than the one that came on the root disk.

These solutions didn't seem to work because I kept replacing a the file
named "tar" in /usr/bin with the new version of tar, and the file
actually being called was in /bin.  So, each time I tried a different
version of tar, it was calling the old, corrupt one.  So, ever since
I corrected that little oversight, all has been well.  This same problem
was encountered on a friend's system, so it may very well fix everyone's
problem.  Hope that helps, it did for me!
-- 
        Rob Coleman              ][   Science, like nature, must also be tamed. 
  gt0449a@prism.gatech.edu       ][     With a view towards its presevation..
Georgia Tech, P.O. Box 30449     ][
     Atlanta, GA  30332          ][                  -Rush/Natural Science
From: zlsiial@uts.mcc.ac.uk (A. V. Le Blanc)
Newsgroups: comp.os.linux
Subject: Re: HELP! Problems with rootimage.
Date: 10 Apr 92 10:56:18 GMT
Followup-To: LeBlanc@mcc.ac.uk
Organization: Computing Centre, University of Manchester

In article <1992Apr8.210115.5364@vax.oxford.ac.uk> tony@vax.oxford.ac.uk writes:
>In article <TSILLANP.92Apr7144847@blob.hut.fi>, tsillanp@niksula.hut.fi (Timo Jaakko Sillanp{{) writes:
>> I get rootimage.Z from nic.funet.fi (yes, binary mode is on),
>> uncompress it and write it to a floppy disk (1.44Mb) using
>> rawrite.exe. 
>
>the rootimage is (I think !) for a 1.2Mb floppy.  Try to find a rootimage for a 
>1.44 disk - this could be the problem ...

The root and boot images from nic.funet.fi should work with both
3.5 and 5.25 inch high density floppies without any changes.
Be sure that the floppies are high density, though; both boot and
root floppies must be, even though the boot floppy is small.

     -- Owen
     LeBlanc@mcc.ac.uk
From: sph1@cbnewse.cb.att.com (stephen.p.hill)
Newsgroups: comp.os.linux
Subject: backup problems
Keywords: cpio tar zip etc
Date: 9 Apr 92 10:37:37 GMT
Organization: AT&T


Has anyone had much luck in backing up their systems?  I 
have heard so many things about problems with different 
versions of tar ( and I have no clue which version I 
ended up with - I got at least 3 versions in the files
I ftp'e ) that I didn't want to use it for my backup.

I got cpio, zip and zoo.  I never learned to use zoo, so 
I tried zip first.  It works for text files, but when 
I try to zip /bin, it only does 3 or 4 files before
printing "EINVAL - error making temp file".

cpio seemed to work fine, so I made 6 cpio files that would
each fit (compressed)  onto a 1.4 M floppy and used dd
to write them onto a raw dos-formatted floppy.  I also 
un-cpio'd them into /tmp for a confidence check.

I booted Linux from floppy, re-partitioned my HD (needed 
more DOS space), installed the basic Liunux to HD, and tried 
to restore from my backups.  I read the compressed cpio files
in from the floppies, uncompressed them and attempted to 
un-cpio them.  It would give me the first few files from 
any archive fine, but then it would tell me that it was 
"skipping xxx bytes of garbage" for each file after that.

Well, my heart nearly stopped because I had spent way too 
many hours downloading that stuff at 2400 baud.  I tried 
the cpio again with the exact same results.  I tried it 
again and accidentally left off the "u" flag.  This made 
it skip the files that it had been able to extract before, 
and it was able to extract another 5 or 6 files before it
started "skipping xxx bytes of garbage" again.  Repeating 
this a few times allowed me to recover all the files.  

I then did another "fsck".  The filesystem had been fine 
before I started the restore, but it now gave me several 
pages of errors.  It was very late and I don't quite remember
what they were but it was something about a zone being 
marked in use but wasn't really used.  I ran "fsck -a"
and it fixed the errors.  

Anyone got any ideas what went wrong?  It looks to me 
like there is a bug in the gnu cpio port.  Does anyone
have a magic method for backing up their system?

BTW, I am using linux 0.95a on a AMD 386-40 with SIS chipset
and Diamond SS VGA.  Works great!


Stephen Hill
sph1@cbnewse.att.com
From: gmartin@mcs213f.cs.umr.edu (Greg Martin )
Newsgroups: comp.os.linux
Subject: Help needed with OS topic
Date: 13 Apr 92 02:40:31 GMT
Organization: University of Missouri - Rolla

I seem to remember a discussion going on a while ago
on alt.os.linux pertaing to micro-kernel design versus
monolithic kernel design.  I'm in an OS class this
semester and we have to write a paper, and I'd like
to write it on this subject.  Unfortunately, I'm having
a lot of trouble finding information on the subject.
(after spending 4 hours in the library today, and
coming up with nothing, I'm a bit frustrated.)

Can anybody point me to articles/materials/etc with
information about the advantages/disadvantages in
these designs?

Thanks,
Greg


""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
"  O softly singing lute, / See with my tears thou time do keep.           "
"  Yet softly, gentle strings, / Agree with love that cannot sleep.        "
"  Sorrow hyst whenas it sings. / When tears do fall then sighs arise.     "
"  So grief oft shines in most sad eyes, / Yea love through heart it dies. " 
"         -Francis Pilkington, 1624                                        "
"  Greg Martin  gmartin@cs.umr.edu          What disclaimer???             "
Newsgroups: comp.os.linux
From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
Newsgroups: comp.os.linux,alt.os.linux
Subject: Re: Second 0.95a alpha-patch
Summary: include-file changes
Date: 5 Apr 92 17:44:30 GMT
Organization: University of Helsinki

I forgot to mention some of the changes this alpha-patch brings to the
user: the kernel include-files have been slightly changed in a couple of
cases, which can result in unexpected behaviour...

a.out.h is now the latest GNU a.out.h, and it seems to have slightly
different magic-number handling than the original 386-minix version I
used for older versions.  Without recompiling the kernel with the new
a.out.h, programs linked with the new binutils will not run (unable to
execute binary file errors).  This just means that even if you don't use
the patch in any other capacity, you had better upgrade to the new
a.out.h, or newer programs won't necessarily run.  Right now there are
no such binaries available, but when gcc2 gets more used, they will show
up. 

The other change is that limits.h and sys/dirent.h are now part of the
kernel include-files: they were needed for the readdir() system call. 
Normally this wouldn't change anything, but there is also a slight
change in limits.h - NAME_MAX is now defined to be 255 so that linux
will eventually handle filesystems with longer names than 14 chars. 
This means that the old direntry-routines in the library won't compile
correctly, as they depended on NAME_MAX being the size of a directory
name.  I hope the gcc-2 library won't have this problem, and that we can
move over to the more general readdir-function without undue growing
pains. 

The a.out.h change was made just to minimize the differences between the
linux headers and the library headers - but the second change is pretty
fundamental.  If you are porting software with the old libraries, I'd
suggest keeping to the old limits.h in /usr/include - that way nothing
should break until we get non-minix filesystems.  Adventurous people
might want to test out the new kernel functions that will be supported
even with new filesystems. 

In case anyone is wondering why the NAME_MAX change is needed, it's due
to the fact that the old /library/ readdir only handled a 14-char
library entry.  When the VFS code is enhanced to allow different
filesystems, you no longer can depend on this, and the library routine
wouldn't know what type of directory it's supposed to read - so the code
has to be moved into the kernel which knows about these things.  The new
readdir() will work correctly independently of the underlying filesystem
(so that you can freely mix different filesystems without needing to
bother about it). 

I'm sorry all this is certain to cause it's share of confusion (using
the old library with the new NAME_MAX and vice versa), but there wasn't
any graceful way to handle it all - unless I would have anticipated
these problems from the start, which I didn't...  You can console
yourselves with the thought that linux should be able to handle longer
filenames and >64MB partitions within a couple of releases. 

		Linus
Newsgroups: comp.os.linux
From: cummings@hammer.Prime.COM (Kevin Cummings)
Subject: Re: GCC2.1 (Wonderful !)
Keywords: gcc, 2.1, 1.40
Organization: Prime Computer R&D
Date: Wed, 15 Apr 1992 19:15:09 GMT

OK, coming from one of the companies that pioneered shared libraries
for the mini-computer industry, and therefore having a VERY one-sided
view of them, I need to get a few questions answered about LINUX
shared libraries.  So here goes:

    Are the shared libraries dynamicly linked to at runtime?  or are
    the .a files bound at install time to whatever shared library
    is in /lib/whatever?  If the latter, then this would explain the
    "extra" step necessary to "install" the programs that use them
    and why .a files are necessary.  Does this mean that these 
    programs that use shared libraries must be re-installed every time
    the shared library is updated?  (If so, then: Barf, puke, etc.)

Please excuse if these are newbie style questions, but working for
a proprietary computer manufacturer for 15 years is an easy way to not
become a UNIX expert.

=================================================================
Kevin J. Cummings                       Prime Computer Inc.
20 Briarwood Road                       500 Old Connecticut Path
Framingham, Mass.                       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
=================================================================
From: pthoms@castle.ed.ac.uk (P Thomson)
Newsgroups: comp.os.linux
Subject: swap ?
Keywords: mkswap,swapon,mkfs
Date: 12 Apr 92 10:51:41 GMT
Organization: Edinburgh University

Hi can someone please explain the buisness of swap please, I have
read all the info in FAQ, beginner-guide followed the instruction
but still can't get it to work correctly

What I did was : created a swap device using pfdisk ie /dev/hda3
		 mkfs /dev/hda3
		 mkswap /dev/hda3  5400 (block) about 5Mbytes

and this seems to work ok ie no errors or complaints

next I'm trying to edit using ue a 1Mbyte file (for test purposes)

 5 seconds later the the disk drive ( a 91 Mbytes space) starts
working over time (as expected) but then I get an out of memory 
message and the system seems to hang


	Thanks in advance Peter.
Xref: sparky comp.os.linux:211 alt.os.linux:2308