HDTenEightyP/NetNews huggingface dataset:
From: sens@FASECON.ECON.NYU.EDU (Sunando Sen)
Newsgroups: comp.os.linux
Subject: Re: fstat dead under 0.99.1
Date: 24 Dec 92 02:35:04 GMT
Organization: New York University

In article <1992Dec23.002229.21267@uc.msc.edu> mfrankow@hamline.edu
(Mike Frankowski) writes:

>The Wyvern (wyvern@gnu.ai.mit.edu) wrote:
>: The fstat/fuser programs from the ps package seem to be broken under
>: 0.99.1 - an fstat gives this:
>: USER     COMMAND    PID    FD  DEV   INUM   SZ|DV MODE       NAME
>: 
>: and that's it. All the other programs in the package seem to work
>: without any problems. At first I thought that ps and family
>: might just need to be recompiled, as is the case so often, but
>: recompilation didn't seem to produce any results.
>: Anyone else having this problem?
>
>Same problem here, all other things work (maybe not fuser, but then again
>I have never had a need for it).
>
>Mike

Actually I can't even get ps & top to work under 0.99.1.  My ps/top etc. are 
for hlu's bootable rootdisk (0.98.5).  ps -U /usr/src/linux/tools/system (
this is where the sources are) produces absolutely no result.  Please 
advice, otherwise I will have to go back to 0.98.5.  I can't use the new 
kernel without at least a working ps (I can live without top).  Thanks in 
advance.

Regards,

Sunando Sen
sens@fasecon.econ.nyu.edu
Newsgroups: comp.os.linux
From: danubius@halcyon.com (Joseph R. Pannon)
Subject: Re: Makeing new kernel
Organization: The 23:00 News and Mail Service
Date: Fri, 25 Dec 1992 20:19:31 GMT

In article <78809@hydra.gatech.EDU> ccasted@prism.gatech.EDU (Edward Deering Boykin) writes:

>I am getting ready to 'make' linux 99.1 kernel. Do I unpack linux-0.99.1.tar.Z
>in root or /usr/linux ? After I successfully compile (:)) what then
>does the makefile automatically update whatever has to be done or do I need
>to move some file around ? If so which files are they and where do they go.
>Do I need to create a new boot floppy or does it not matter? If I
>do need to create one how do I go about doing it?

Good questions!  As a matter of fact, you just took them out of my
mouth.  Let's hope the responses will also be public.

One additional thing I would add to your question is that I would also
like to know the exact uncompress and tar parameters to be used for
installing the new kernel source.  For instance, is the h switch to be
used to force tar to follow the symbolic links as if they were normal
files and directories?

>I do not have linux source allready on my filesystem.

But what about those, who already got the kernel 0.99 source on their
system via the SLS packages?
>
>Also I would like to update my gcc-libs to 2.3.2 fron 2.2.2d. How do I go 
>about doing this. Should I just create a new directory in the same place
>as 2.2.2d ? 

Another question stolen from me! ;-)

>Help would be appreciated very much. Thanks folks

Same here!
>
Joe Pannon
danubius@halcyon.com
Newsgroups: comp.os.linux
From: axi0349@ultb.isc.rit.edu (A.X. Ivasyuk)
Subject: [X11]  Problems running X programs with kernel 0.99pl0 and pl1
Originator: axi0349@ultb
Reply-To: axi0349@ultb.rit.edu ()
Organization: Rochester Institute of Technology
Date: Thu, 24 Dec 1992 23:59:25 GMT

After I upgraded my kernel to 0.99pl0, any new X program that I compile
under that kernel bombs with some sort of strange error.  For example:
  Seyon 1.5: attempt to manage child when parent not Composite
  xxgdb 1.06: Couldn't find per display information.

Any binaries that I already have (like my old copy of xxgdb) run just fine.
It's just the new stuff that I compile under the new kernel that dies.  This
also happens under the .99pl1 kernel.  I haven't changed my X setup since
I got Xfree86 1.1 (Xlinux 2.1) when that came out a while ago.  I'm using
gcc 2.2.2d7, and I just got libc.so.4.2 installed, although the same thing
was happening with libc.so.4.1.  Any ideas?  Should I try reinstalling X?

-Anatoly
-- 
  Anatoly Ivasyuk @ Computer Science House @ Rochester Institute of Technology
   anatoly@nick.csh.rit.edu || axi0349@ultb.rit.edu || axi0349@ritvax.rit.edu

                  You say you haven't heard of CSH?  You will...
Newsgroups: comp.os.linux
From: healyzh@iat.holonet.net (Zane H. Healy)
Subject: Does Linux 0.99 break bash 1.12.3?
Organization: HoloNet National Internet Access BBS: 510-704-1058/modem
Date: Wed, 23 Dec 1992 10:42:11 GMT

I just upgraded my system to 0.99 and I am now gettin some very strange
reaction's when I try to run shell scripts.  It seem's that 0.99 broke bash.
Has anyone had simular problem's?

BTW I upgraded from 0.98pl1 to 0.99

     Zane in DC
\
-- 
Zane H. Healy        |  Once I had a little game
healyzh@holonet.net  |  I liked to crawl, back into my brain
  on Internet        |  I think you know, the game I mean
                     |  I mean the game, called 'go insane'
Newsgroups: comp.os.linux,comp.unix.questions
From: tglovie@sail.uwaterloo.ca ()
Subject: Postscript to Ascii
Summary: Is there such a thing? 
Originator: tglovie@sail.uwaterloo.ca
Organization: University of Waterloo
Date: Tue, 22 Dec 1992 19:53:05 GMT

Hello,

I was wondering if there is such a beast as a postscript to ascii
converter?  I have heard rumours that the Next has something of the sort,
but I was wondering if there was a generic public domain (or copyleft or
shareware even) program to do this (It'd be even better if it was already
ported to Linux!)  Could anyone let me know if I can get such a thing
(or even to tell me that I'm crazy to even consider it) and where to
get it? (FTP preferably)
\
Thanks,
Jerry
From: Dave-Nuttall@cup.portal.com (David Dave Nuttall)
Newsgroups: comp.os.linux
Subject: LILO 7 and LINUX 0.99.1
Date: Thu, 24 Dec 92 05:35:54 PST
Organization: The Portal System (TM)

I've compiled and am successfully using LINUX 0.99.1.
I've compiled and wish to be equally so with LILO 7.

I can make a LILO 7 floppy which boots fine, but attempts to
make the hard drive bootable are failures.  Would appreciate
insights other than RTFM/FAQs. 

My /etc/lilo/config is:
install = /etc/lilo/boot.b
image = /Image
  label = lin-hd
  root  = /dev/hda1

If I run:
$ROOT/etc/lilo/lilo - C /etc/lilo/config $*

no errors are reported.
Then I sync and reboot.
The system reports NO OS.

My disktab is:
0x301	0x80	38	16	683	0	# /dev/sda

The drive is a Maxtor 210MB IDE....683, 38, 16 are reported by the BIOS.

Comments, suggestions, PLEASE!
Thanks.
dave@csoftec.csf.com
Newsgroups: comp.os.linux
From: torvalds@klaava.Helsinki.FI (Linus Torvalds)
Subject: Re: compiling the kernel...cool : )
Organization: University of Helsinki
Date: Wed, 30 Dec 1992 12:28:24 GMT

In article <marcf.725692606@yorku.ca> marcf@nexus.yorku.ca (Marc G Fournier) writes:
>
>	First of all, I would like to congratulate he would
>wrote the config script for compiling the kernel...it is excellent.

Heh.  It's a fast hack, but it seems people like it a lot more than
editing Makefiles..  Strange.

>	What is:
>		kernel math emulation (co-processor emulation?)

Yes, it's the co-processor emulation code.  If you have a co-processor,
you can answer 'n' (or just press enter: the default is set up according
to my system, which has a copro).  Without a coprocessor, you should
answer 'y' to this question. 

>		kernel profiling support?

Answering 'y' to this adds some small code to do limited kernel
profiling: to actually get the information you'll have to use a special
program that reads kmem to find out the results.  This is not something
people generally need to do: it's meant only for kernel hackers who want
to see where the kernel spends most of its time. 

>		/proc filesystem support?

If you answer 'y' (or blank) to this, the proc-fs filesystem code is
linked in. Do a

	mkdir /proc
	mount -t proc /proc /proc

to find out more about it: it essentially gives some general linux
process information (so that you can write 'ps' as a shell script or
whatever instead of messing around with kmem). 

		Linus
Newsgroups: comp.os.linux
From: torvalds@klaava.Helsinki.FI (Linus Torvalds)
Subject: Re: Suggest inclusion of the QIC-02 driver
Organization: University of Helsinki
Date: Tue, 22 Dec 1992 00:38:32 GMT

>> >I second inclusion of the QIC-02 driver!
>> I third inclusion of QIC-02 driver (for Archive/Wangtek).
>I vote for inclusion of the QIC-02 driver (for Archive/Wangtek).

Guidelines to get something included into the standard kernel follows. 
They are just general suggestions, and have nothing to do with the QIC
driver, other than explain why it won't help however many people posts
to the newsgroup about it.. 

Q: I want something included into the kernel. How do I do it?

A: Write nice code.  Make sure it's a feature I people (me) actually
   wants, and tell me about it by mail.

   I need the *author* to tell me about it - I'll largely ignore any
   requests from anybody else.  The reasons are:

    - that tells me clearly that the person who wrote the code really
      wants it as a part of the standards kernel.  Under some
      circumstances, somebody may want to write code that he/she isn't
      quite willing to make part of the "real" linux distribution for
      one reason or another, even if he/she makes it available for
      beta-testing.

    - The author usually knows the limitations of his code best, and may
      not feel it's really ready for general consumption.

    - I can get the newest version, as well as start up communication
      with the author if there are questions or comments.

   Also note that it may not be enough just to drop me a short note
   about it: I get quite enough mail as it is, so if it for some reason
   or another doesn't catch my eye, I'll probably just ignore it.  Don't
   count on me remembering about things: if things haven't happened in a
   week, mail me again.

   Finally, the timing is pretty bad right now: I wouldn't count on any
   new features (especially features that I cannot test) before there is
   a 1.0 release that works. 

So don't panic, I'm sure the QIC driver will make it into the kernel
eventually.

		Linus
Newsgroups: comp.os.linux
From: jlaiho@ichaos.nullnet.fi (Juha Laiho)
Subject: Re: [Q] Serial ports?
Organization: NullNet r.y.
Date: Wed, 23 Dec 1992 05:28:01 GMT
Keywords: serial ports

In article <1992Dec22.010535.23815@alw.nih.gov> arm@helix.nih.gov (Andrew Mitz) writes:
>In article <1992Dec20.190600.21543@spdcc.com> rbraun@spdcc.com (Rich Braun) writes:
>>AST is indeed a manufacturer.  Last I checked, though, multi-port
>>serial boards on the ISA bus were horrendously overpriced (like
>>US$1000 for an 8-port board from DigiBoard, as compared to $30 for a
>>2-port board).  Is there *any* manufacturer of densely-populated
>>serial boards in the sub-$25/port range?  One which would suit the
>>needs of Linux users?
>>
I suppose you're comparing apples and oranges when you compare some DigiBoard
product with normal ports. I think most DigiBoards that are advertized are
intelligent ones, i.e. have an onboard 80186 or something like that, some RAM,
some ROM etc. I think USD 1000 is quite a normal price for such a card.
DigiBoard also has non-intelligent multiport cards, but I've asked around and
found out that they require Non-disclosure agreement before releasing any
real information.

I'm in the process to write a fax to Boca Research in order to ask about their
8-port non-intelligent board, that is built around two 16c554 chips.
(16c554 is a chip carrying 4 16550 compatibles. If I just knew whether it is
the A version or not.. I'll ask.)
Anyway, I'm not a kernel hacker, but if I get some useful programming
information from Boca, I hope I get someone to look at it, and write
a driver.
(the price of the board is a bit over USD 200 from a local retailer)

>Some of the mouse port boards, e.g. Mouse Systems, are fancy
>serial ports with extra options for selecting addresses and
>interrupts.  They run about $35/port, if I remember
>correctly.  Unfortunately, they cost 1 slot/port.
I have a nameless clone IDE/Multi-I/O-card on which the COM ports can be
set to IRQs 3,4,5 and 9.

..Wolf
From: probreak@matt.ksu.ksu.edu (James Michael Chacon)
Newsgroups: comp.os.linux
Subject: Re: Kermit lock files wrong for uugetty
Date: 23 Dec 1992 11:45:12 -0600
Organization: Kansas State University
NNTP-Posting-Host: matt.ksu.ksu.edu

bribbeck@exucom.com (Bob Ribbeck) writes:


>  Kermit puts its lockfile in the tmp directory. uugetty puts it's
>lock in usr/spoll/uucp where it belongs.  Can anyone fix this??

You will have to recompile kermit, or hope someone else will. Last time
I compiled it, that was a compile time option. The source should be available
on tsx-11.mit.edu.

James
Newsgroups: comp.os.linux
From: junio@twinsun.com (Jun Hamano)
Subject: Re: Question and Observations
Organization: Twin Sun, Inc. (El Segundo CA)
Date: Tue, 29 Dec 1992 18:26:53 GMT

In article <1992Dec29.165604.17462@athena.mit.edu>
whit@Tymnet.COM (Kendall Whitlatch) writes:

   I just wanted to extend to Peter my thanks for compiling the SLS package.
   If it wasn't for him I think the spread of Linux would have been VERY
   limited.  I personally am not interested in combing through all the FTP
   sites trying to find code that I can run on (much less port to) Linux.

   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.

I regret that I sounded as if I were saying minor flaws in SLS
releases were causing harm to the users.  That was not what I
meant to say; I apologize.  As everybody says, SLS releases have
brought a tremendous benefit to linux community with its ease to
installing a usable system in more-or-less `out of the box'
manner.  What I wanted to say was, when we encounter flaws in a
SLS release, we should not just complain, but we should help
improving it, since it has so much influence on how most users
organize and manage the system on their boxes.

Peter, thanks again.
--
      |
   __-+-__      Jun Hamano
_-+ (|o|) +-_   junio@twinsun.com
  !   .   !
Newsgroups: comp.os.linux
From: danubius@halcyon.com (Joseph R. Pannon)
Subject: Re: efsck: bad magic number in super-block, boot manager's fault?
Organization: The 23:00 News and Mail Service
Date: Sun, 3 Jan 1993 20:31:41 GMT

In article <1i75ovINNmbm@matt.ksu.ksu.edu> nan@matt.ksu.ksu.edu (Nan Zou) writes:

>I created the extended partition (and the logical partitions inside it)
>using the fdisk from SLS, all is going well until I decided to add the
>Linux root partition to OS/2 Boot Manager's menu, BIG MISTAKE, OS/2 Boot

Your BIG MISTAKE was to use the linux fdisk for partitioning your hard
disk, instead of OS/2's own partitioning routine.  I don't know how many
times this has been pointed out here already (and even in the various
README and FAQ files, I believe) that if you use OS/2 with Linux, then
use OS/2 to partition your HD and use the linux fdisk only to set the
System Id (81 or 82) for linux partitions!  So you might want to try to
do it that way next time.

Good luck!
Joe Pannon
From: dharry@cyclone.rice.edu (Dennis Harry)
Newsgroups: comp.os.linux
Subject: Re: something screwy with mail...
Date: 29 Dec 92 17:09:07 GMT
Organization: Rice University

In article <marcf.725421090@yorku.ca>, marcf@nexus.yorku.ca (Marc G Fournier) writes:
|> 
|> 	We are fooling around with things right now, and have just
|> noticed a weird problem...when you send email to a user, the
|> ownership is incorrect, so that the receiver can not even read his 
|> email :(
|> 
|> 	I just sent user from my account to another, and I am now
|> the owner of his mail folder.  
|> 

I'm having the same problem, also after "fooling around".  Specifically,
I moved several binaries between /bin and /etc/bin (after copying both
directories to a safe place in case I broke something).  Mail broke,
so I restored the saved directories.  Mail's still broke as Marc described.

Sigh.  Did someone say something about not fixing what ain't broke?

-- dlh
From: ail8070@tamuts.tamu.edu (Andy I. Liaw)
Newsgroups: comp.os.linux
Subject: second batch of problems: tcsh, adduser, hostname, lilo...
Date: 30 Dec 1992 01:56:02 GMT
Organization: ~/lib/organization
NNTP-Posting-Host: tamuts.tamu.edu

Hi all!

I've got most of my earlier problems solved thanks to those who
helped.  Here are my second batch:

1. I downloaded tcsh6.02, unpacked it, and ran the install script.
   But tcsh always gives me 'Segmentation faults (core dumped)'.
   
2. How do I add a user which does not have superuser previleges?
   What's the group number?

3. If I changed the hostname to something other than softland,
   it'll remain changed.  But After reboot the hostname is back to
   softland.  What's causing this?

4. I still can't get lilo 0.7 to work.  I got linux on my boot
   manager menu (that's right, I'm using os/2).  After selecting
   linux, I get to where it says 'partition table ok' and it stops
   right there.  Why?

I'm still in SLS 0.98pl5.  My system: /dev/hdb1 as /, /dev/hdb3
as /usr.

If possible, please reply by e-mail.  I'll post a summary when/if
I get most of these resolved.  Thanks in advanced.

Andy Liaw
aliaw@stat.tamu.edu

Newsgroups: comp.os.linux
From: fjh@munta.cs.mu.OZ.AU (Fergus James HENDERSON)
Subject: Re: IMPORTANT [BUG in 0.99] Re: [ANNOUNCE]: linux version 0.99
Organization: Computer Science, University of Melbourne, Australia
Date: Tue, 29 Dec 1992 20:21:30 GMT

sdw@meaddata.com (Stephen Williams) writes:

>Lars Wirzenius (wirzeniu@klaava.Helsinki.FI) wrote:
>: >Just curious - I haven't got the .99 sources yet, but why is an explicit
>: >initialiser needed here. A static pointer ought to be initialised to
>: >NULL in the executable already? 
>NOT!

You are incorrect here. Ansi C guarantees that static variables are
initialized.

>: 
>: In normal C programs, yes, but the kernel is a bit special.  Like, for
>NOT!

You are incorrect here also.

>: instance, who is going to do the initialization?  Normally it is the
>: kernel (which zeroes out all memory before it is given to a user
>: process), the linker (which loads the pre-initialized variables from a
>: file, i.e. those variables which are given an explicit initializer),
>: and possbily the C startup code.  Trouble is, none of these are active
>: when the kernel is booting...
>
>Statics are either explicitly initialized or they are not.
>If they are not, their contents are UNDEFINED until set.
>This is per ANSI C.

Wrong.

>There is NO requirement of the compiler or system to zero
>un-initialized statics (or auto's).

Wrong.

>The fact that some systems waste time doing so is no reason rely on it
>as a feature.  This was already debated and tossed out as something to
>rely on.

For all multi-user operating systems (like Linux ;-), the operating
system must in general initialize the memory for security reasons.
Thus it is not time wasted.

(Otherwise you could go snooping about in the unitialized memory, looking
for confidential data stored there by the previous inhabitant. See
the recent article in comp.risks about the Risk of leaving confidential
data in memory on DOS machines.)

[lots of extremely non-portable suggestions deleted]
>
>And, yes, it would be nice if the nulling were garunteed.  The problem
>I think is the overhead incurred for a program that has a huge bss and
>doesn't need it initialized.  A better solution would be (if it
>weren't for the headache..) to have bss and bsz segments.

As noted above, the initialization *is* guaranteed, and it is *not*
unnecessary overhead.

-- 
Fergus Henderson             fjh@munta.cs.mu.OZ.AU      
This .signature virus is a self-referential statement that is true - but 
you will only be able to consistently believe it if you copy it to your own
.signature file!
Newsgroups: comp.os.linux
From: danubius@halcyon.com (Joseph R. Pannon)
Subject: Re: Ctrl-Alt-Del
Organization: The 23:00 News and Mail Service
Date: Tue, 29 Dec 1992 18:52:17 GMT

Thanks for everybody who pointed out the BIOS shodowing adowing problem.  After 
disabling it, the reboot works as advertised.  Now I just hope that the 
disabled shadowing won't affect adversely my DOS and OS2/2 speeds.
 
Thanks again,
Joe Pannon
From: Jim.Corbett@f35.n152.z1.fidonet.org (Jim Corbett)
Newsgroups: comp.os.linux
Subject: Question and Observations
Date: Wed, 30 Dec 1992 14:18:00 -0800

 > I am doing the best I can with SLS.  I can't help the fact
 > that minor errors on my part result in extra postings on
 > the internet.  A hazard of the trade.  What you don't see
 > are the countless hours I spent collecting and configuring
 > the tcpip system, shadow passwords, the install scripts, etc.
 > Please be patient and you will be rewarded.

You seem to be catching some flak now and then Peter.
Let me turn the tide a bit and say THANKS for your efforts.

May I suggest that you not try to keep up with all the
latest releases of everything, and just release SLS sets that you are
very happy with.

Or release a SOLID SLS and a BEAT-BETA SLS set, so those that have to
have the latest and greatest will be able to help you debug and those
that are wanting something more solid can have that as well.

Your install scripts and now Linus's "make config" have been GREAT
additions to those of us that are trying to help others set up LINUX
systems.

I started messing with LINUX to learn UNIX (tm) and to have a true
multitasking system at home.  This last year has really educated me.

Thanks to getting the FIDO LINUX ECHO from GregN at 343/34 (yes it is a
lot of stuff to read) I have learned LOTS about Linux, and have been
able to assist others setting it up.

My thanks to you and all the others that have made MAJOR and MINOR
contributions to the LINUX project.  And especilly to SANTA LINUS!

 > But if you need a finished product now, try SCO or DELL.

Well said!  (add SUN SOLARIS to the list...)

I have a feeling that there will be many impovements in the comming
year, a more stable kernel and recompiles of many of the utils and
support programs.  I truly look forward to the year 2000 and what LINUX
will be then!  (think of all the NEW CPU's it will have been compiled to
work on by then)


Have a great 1993!

And again, thanks for your efforts.

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

Newsgroups: comp.os.linux
From: root@bigcomm.gun.de (Christoph Adomeit)
Subject: Missing Curses definitions (A_BOLD ...) in SLS ?
Organization: Private
Date: Sun, 3 Jan 1993 18:47:10 GMT

Hi, 
I'am trying to port some Software to Linux, but I'am missing the
Curses definitions for A_BOLD,A_UNDERLINE ... in curses.h.
"man curses" says they should exist.
Any idea how I can work around that ?
I'm using .98 SLS with .99.1 Kernel Image.

Another Question: WHat curses implementation is in SLS ? Are the
sources available ? Is it 8-bit clean ? Does it support colors ?

Happy new year to everyone
Bye
  Christoph
Newsgroups: comp.os.linux
From: lam836@cs.cuhk.hk (Savio Lam)
Subject: Can't allocate color?!
Organization: Faculty of Engineering, The Chinese U. of Hong Kong
Date: Sun, 27 Dec 1992 15:38:18 GMT

I use xloadimage to load a 256 color image onto the background. But each
time after doing this, I get the message "Can't allocate color" when
running other applcations (e.g. xmahjongg, Seyon). Moreover, if I add
"xloadimage -onroot image.gif" into my .twmrc before "exec twm", I get
only black and white windows. It appears that xloadimage is holding the
colors, disallowing others to use them. Can anyone please help?
 

Regards,
Savio Lam.

email: lam836@cs.cuhk.hk
Newsgroups: comp.os.linux
From: marcf@nexus.yorku.ca (Marc G Fournier)
Subject: URGENT: inability to login using dialin line...
Organization: York University
Date: Wed, 30 Dec 1992 03:00:37 GMT

Hi...

	finally got the modem to answer the phone (hurray!!)
and then I hit a problem with logging in on that dialin line
(*sigh*)

	Someone suggested I needed the login program from the
poeigl.tar.Z distribution, so I tried it...guess what...doesn't
work.  I'm presuming that that logi doesn't use shadow passwd's,
whereas my system does...and I can't seem to find any flags in
the include files that allow me to turn on shadow passwds :(

	Anyone have another idea as to how I can do this?  It
does answer, it does prompt for login: and for passwd: but that
is as far as it gets :(

Thanks...

Marc