HDTenEightyP/NetNews huggingface dataset:
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.os.linux
Subject: Re: shared libs - can everyone be happy with this?
Date: 18 Aug 92 12:59:01 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

In article <NOP.92Aug17135014@theory.Mankato.MSUS.EDU>, nop@theory.Mankato.MSUS.EDU (Jay A. Carlson) writes:

| I think that William and I were thinking in a more theoretical slant.
| Yes, the kernel would give each process its own copy if this was done
| without guile.  

  Exactly so. We need to write the page in such a way that the kernel
doesn't notice. Hum, I've used kernels that did that, but it wasn't a
feature.

| A brute force technique would be to include a kernel function that
| would do the necessary patch and then restore the previous
| dirty-status of the page.

  Or, as you implied earlier, not effect the status at all. Since these
are shared code segs, they better be clean.

| Note that with processes sharing the same text, there is even less
| overhead, since the patch only happens once per call point per shared
| image instead of once per call point per process.

  I had completely missed this. The overhead of a single fixup is shared
between all processes running the image. That is a feature of a runtime
loader, as well.

| I'm not sure that all this trouble is worth it.  Does anyone have any
| hard data on the performance loss of jump tables?

  That's very hard to get, since the overhead is dependent to some
degree on program behavior and system load. If the jump table stays in
memory due to usage, the overhead is small. If the call to the jump
table results in a page fault, the realtime goes up, and the system
overhead may or may not be reported back to the process. Up to a certain
point load help keep the JT in memory, after which it starts to force
other stuff out, and the memory used by the jump table(s) starts to
hurt. This seems likely only in a machine with minimal memory for its
load.

-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
    I admit that when I was in school I wrote COBOL. But I didn't compile.
From: d88-jwn@drax.nada.kth.se (Johan W}hlin)
Subject: Re: (emulating the) Motif Window Manager on Linux??
Organization: Royal Institute of Technology, Stockholm, Sweden
Date: Fri, 21 Aug 1992 15:13:40 GMT

In article <1992Aug21.131543.5296@osf.org> ede@kadabra.osf.org (Ted Ede) writes:

> ...

>If you want the real motif mwm and libraries, you'll have to convince
>a binary vendor to port it to linux.  I have some friends that work
>for such a vendor.  Do anyone think it would be worthwhile to port
>motif to Linux.  Considering the OSF would get the first $40 of the
>sale, how much would you be willing to pay for a copy?

> ...

I'd be most interested in having the Motif libs and wm for Linux. I would be
willing to pay for it as well. I do not know how much I'd be willing to pay.
/Johan

>
>   Ted Ede -- ted@world.std.com -- on contract at the Open Software Foundation
>      -- All views expressed are mine unless explicitly stated otherwise --
>	           -- This line intentionally left blank  --
>
From: rburns@key.COM (Randy Burns)
Newsgroups: comp.os.linux
Subject: Would Anyone Working on a Linux CD-ROM please contact me
Date: 19 Aug 92 01:20:10 GMT
Organization: Amdahl Corporation, Advanced Systems, Fremont CA

Thanks.
Newsgroups: comp.os.linux
From: jrs@world.std.com (Rick Sladkey)
Subject: schedules (was: X11 w/ Trident binaries request)
Organization: The Internet
            <1992Aug12.140705.10993@sisd.kodak.com>
Date: Thu, 13 Aug 1992 02:35:01 GMT

>>>>> On Wed, 12 Aug 92 14:07:05 GMT, obz@sisd.kodak.com (Orest
>>>>> Zborowski COMP) said:

zorst> i apologive profusely for the delay. apparently the net
zorst> connection between our building and our main feed (internet
zorst> side) blew up many internet sites along the eastern seaboard
zorst> and the powers-that-be are working trying to get the problem
zorst> resolved. i thought it would be a couple of days, or a week...
zorst> like every other time estimate in life, you need to multiply by
zorst> 3 :-)

A rule that I picked up from somewhere is quite useful in such situations.

	"Bump up to the next unit of measurement and muliply by two."

So when you hear a schedule like:		Expect:

	1 hour					2 days

	2 days					4 weeks

	1 month					2 years

Sad, but often true.
--
Rick Sladkey
jrs@world.std.com
From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
Newsgroups: comp.os.linux
Subject: Re: The Third Degree
Date: 14 Aug 92 20:54:08 GMT
Organization: University of Helsinki

In article <7gh1Hm#z&8@atlantis.psu.edu> bairstow@copland.psu.edu (Steven Bairstow) writes:
>In article <1992Aug13.124939.16680@kth.se> d88-jwn@blofeld.nada.kth.se (Johan W}hlin) writes:
>>bairstow@copland.psu.edu (Steven Bairstow) writes:
>>: ...
>>: 	- Has anyone noticed free inodes being left around? I think 
>>: 	  halt/shutdown is doing it. (This is what I was trying to figure 
>>: 	  out when it crashed.)
>>Yes I've been having this problem at least with reboot
>>
>
>Okay, so does anyone know where the code is for these programs so I can take 
>a look at them, or who the author is?

I doubt it's either reboot or shutdown that results in the fsck errors:
what you are probably seeing is a normal result of the filesystem setup
under unix.  I assume the problem is that fsck reports "inode XXX marked
in use: no file uses it" and "block XXXX marked in use: no file uses
it". 

This can happen if you install a new version of a running program (like
'init') and reboot.  The old 'init' is removed from the directory tree,
but as it's still in use, neither the inode nor the blocks are actually
reclaimed until the program is exited.  And in many cases (like /bin/sh
or init or update), the program is never exited until the reboot has
happened.  "fsck -a" should clear up the problem - or you should be more
careful when rebooting with "deleted" programs still running. 

		Linus
Newsgroups: comp.os.linux
From: rafal@utstat.uucp (Rafal Kustra (summer student))
Subject: reggae.oit.unc.edu:can't download MGR stuff
Organization: University of Toronto, Dept. of Statistics
Date: Tue, 18 Aug 1992 22:31:44 GMT

As per subject line, will powers-that-be at reggae change
the permisions in Linux/MGR (and perhaps others)
directory?

			Thanx, Rafal

-- 
/|| Numbers exist only in our minds. There is no physical entity that
 ||_is_ number 1. If there were, 1 would be in a place of honor in 
 || some great museum of science, and past it would file a steady
==== stream of mathematicians gazing at 1 in wonder and awe.
Newsgroups: comp.os.linux
From: tep@engr.uark.edu (Tim Peoples)
Subject: Re: Stabilizing Linux
Reply-To: tep@engr.uark.edu
Organization: University of Arkansas
Organiztion: University of Arkansas, Dept. of Computer Systems Engineering
Date: Wed, 12 Aug 1992 12:47:49 GMT

dje@sspiff.ampr.ab.ca (Doug Evans) writes:

>davidsen@ariel.crd.GE.COM (william E Davidsen) writes:
>>  Let me say a word about documentation. I ahve written a number of
>>things which have gone out through source groups, all the way back to
>>mod.sources. During that time I wrote a user's guide to zoo, the
>>archiver. The guide is about 35 pages long, and took almost as long to
>>write a a major program. I have had a total of two people drop me a line
>>to tell me they liked it, and few if any archive sites carry the manual
>>even though they have the software.
>>
>>  Given that documentation is less fun to write than software, brings no
>>recognition whatsoever, and takes longer page for page than code, you
>>need to find someone who really wants to write documentation, or it's
>>not going to happen. If there's someone who is a good writer and a
>>complete loss as a programmer, and who wants to really contribute to the
>>effort, that's the person who should do it. And all the postings in the
>>world about what we need won't help unless you can find someone to do
>>it.
>
>Why not try to use documentation that already exists (where possible, of
>course)? Why keep reinventing the wheel just for the sake of reinventing the
>wheel???
>
>For example, I can buy a whole suite of manuals on SVR4/386 from Prentice Hall
>for about $300. Yes yes, that's pretty steep, but what are the realistic
>alternatives?
>
>Suppose Linux was heading to where SVR4/386 already is: most of our manuals
>would already be written for us. And we would rarely have to cope with Linux
>quirks when porting the various applications. And we would have a roadmap of
>where we were going.
>
>I know we don't want to do this, but as a hacker, I often (though not always)
>like hacking on new things, not redoing existing things just so I can say
>"I did it my way".
>-- 
>Doug Evans               | "You're just supposed to sit here?"
>dje@sspiff.ampr.ab.ca    |               - Worf in a mud bath.

Plagiarism.

-- 

+--------------------------------------+-------------------------------------+
| Tim Peoples                          | The time has come the hacker said   |
| tep@engr.uark.edu                    | to talk of many things,             |
| Dept. of Computer Systems Engineering| of simms and sockets and semaphores |
| University of Arkansas, Fayetteville | of processes and pings....          |
+--------------------------------------+-------------------------------------+
|    I need no disclaimer; nobody listens to what I have to say anyway!!     |
+----------------------------------------------------------------------------+
From: kenney@milton.u.washington.edu (Michael Kenney)
Newsgroups: comp.os.linux
Subject: Re: README: gcc 2.2.2d is out
Date: 17 Aug 92 04:21:53 GMT
Organization: University of Washington, Seattle

In article <1992Aug16.085002.26503@serval.net.wsu.edu> hlu@phys1.physics.wsu.edu (Hongjiu Lu) writes:
>
>This release only runs under Linux 0.96c or above.
>This release only runs under Linux 0.96c or above.
>This release only runs under Linux 0.96c or above.
>This release only runs under Linux 0.96c or above.
>This release only runs under Linux 0.96c or above.
>
>This release only works with Linux 0.97 patch 1 or above.
>This release only works with Linux 0.97 patch 1 or above.
>This release only works with Linux 0.97 patch 1 or above.
>This release only works with Linux 0.97 patch 1 or above.
>This release only works with Linux 0.97 patch 1 or above.
>This release only works with Linux 0.97 patch 1 or above.
>This release only works with Linux 0.97 patch 1 or above.
>
[ useful gcc info deleted]



Huh????  Will it work with 0.96c or not?

-----
Mike Kenney
UW Applied Physics Lab
mikek@apl.washington.edu
Newsgroups: comp.os.linux
From: drew@kinglear.cs.colorado.edu (Drew Eckhardt)
Subject: Re: Stabilizing Linux
Organization: University of Colorado at Boulder
Date: Wed, 12 Aug 1992 17:30:12 GMT

In article <1992Aug11.203828.11554@crd.ge.com> davidsen@crd.ge.com (bill davidsen) writes:
>
>  Just one last thought. Linux has really taken to doing the hard stuff
>first, like virtual memory. Work is going on right now to look at
>improving the shared libraries, when most other systems don't even
>/have/ shared libraries.
>

Most AT&T variants do.  No BSD flavor I know of has shared libraries.

>  It would be really great to have loadable device drivers. More to the
>point, it would allow people to add devices without generating a new
>kernel, something I believe most users would like to see. Nice a it is
>to have source, I lose an evening of use of my system every time I
>recompile the kernel.
>

Loadable device drivers are bad because you need to relocate them 
at load time.  Loadable device drivers may be impractical - for 
instance, if your disk driver is on the root disk which you can't
read, you are SOL.  I don't like loadable device drivers - you
don't really gain anything significant that you don't get with a 
good config utility.

It takes me ~45 seconds to add a new SCSI driver into my development 
kernel.  I have automatically generated make files and something 
like the BSD ioconf.c, table.c.  When I change the configuration 
file, table.c gets recompiled, and nothing but the new files that
were'nt built before.
 
Linux needs this - users can then recompile just the new parts that
weren't in their kernel before.

>  This also allows people to install to unsupported devices, by loading

People can install new devices by recompiling the kernel.  If we 
get a decent config program, people can install new devices by relinking
the thing.

>the driver from a floppy at boot from floppy time. It has been done by a
>commercial vendor, I see no reason why it couldn't be in Linux.

Assuming you run in kernel space :

1.  You will have to allocate more kernel memory.  This is a sloppy operation,
	because currently everything assumes that kernel memory is 
	identity mapped.  You may have to swap things arround for 
	other processes just to get a large enough chunk of contigous
	physical memory in the right place.  Messy.

2.  You need to relocate the drivers at run time if you run them in kernel
	space, writing something like LD to load them.

Assuming you run in user space :

1.  You will be VERY, VERY, slow.  Anything that accesses the device 
	will incur extra context switches.
 
2.  You will need to do nasty things to access kmem.

Get a decent config program, it will accomplish the same thing 
(except you have to reboot to use the new device driver),
without all of the negative side effects.
-- 
Microsoft is responsible for propogating the evils it calls DOS and Windows, 
IBM for AIX (appropriately called Aches by those having to administer it), but neither is as bad as AT&T.  Boycott AT&T, and let them know how you feel.
From: wirzeniu@klaava.Helsinki.FI (Lars Wirzenius)
Newsgroups: comp.os.linux
Subject: Re: Repartitioning and using DOS again
Date: 18 Aug 92 08:47:39 GMT
Organization: University of Helsinki

cljackso@uokmax.ecn.uoknor.edu (Chris Jackson) writes:
>	I'm having a problem with partitioning for Linux.  First, after I
>delete my existing partitn and create three new ones (DOS, Linux, and 
>Linux swap),  I loose all my programs which isn't that bad.  Then when I
>try installing DOS, and even though the DOS partition is flaged as boot, 
>DOS (I'm using 5.0) can't figure out which partition to install on (C: ).
>I like Linux but I need DOS till I get it running.

How did you create the partitions?  You probably need to create the DOS
partition using DOS' fdisk.

--
Lars.Wirzenius@helsinki.fi
From: int177c@aurora.cc.monash.edu.au (Jae Won)
Newsgroups: comp.os.linux
Subject: xsetroot
Date: 19 Aug 92 09:22:41 GMT
Organization: Monash University

Hi,

	I am just wondering if there is a port of xsetroot to X386 yet. If there is
where can I find it? I couldn't find it with the X386 distribution(version 1.0)


Jae

int177c@aurora.cc.monash.edu.au

.sig: I can't be bothered...really..:)
From: harrism@garage.ecn.purdue.edu (Matthew M Harris)
Newsgroups: comp.os.linux
Subject: Linux-Activists mailing list is going nuts.
Date: 12 Aug 92 04:21:55 GMT
Distribution: global
Organization: Purdue University Engineering Computer Network

I didn't know who to mail this to, but there have been linux-activists
archives within the linux-activists mailings. I.e #606 would be in #608.
My mailbox is being overloaded with unnecessary mail.
From: zhao@unixg.ubc.ca (Jiansheng Zhao)
Newsgroups: comp.os.linux
Subject: ps-0.97 patch 1? where?
Date: 18 Aug 92 20:05:08 GMT
Organization: University of British Columbia, Vancouver, B.C., Canada

There was a dicussion recenly about defuncted ps under 0.97. Has new ps-0.97
with patch 1 (binary and source) been uploaded to any linux site?
Thanks.
-- 
Jiansheng Zhao
Dept. Chem. Eng, Univ. of B. C., Canada. V6T 1Z4
zhao@unixg.ubc.ca
Newsgroups: comp.os.linux
From: erc@unislc.uucp (Ed Carp)
Subject: Re: header woes with 2.2.2d
X-Newsreader: Tin 1.1 PL5
Organization: Unisys Corporation SLC
Date: Thu, 20 Aug 1992 20:14:14 GMT

Theodore Ts'o (tytso@ATHENA.MIT.EDU) wrote:

: only get releases once every six months to every few years.  If you took
: 0.96c, and didn't upgrade to 0.97, or 0.97pl1, you'd have a perfectly
: stable system.  I suggest that those people who are complaining take
: either the MCC release, or the SLS release --- AND THEN NOT UPGRADE.

There are certain advantages to upgrading.  For instance, I had to upgrade to
0.97 to get my serial stuff to work.  I have 8250's on my serial cards, and
0.96c just wasn't cutting it.  I upgraded to 0.97 (compiled with gcc-2.2.2,
BTW) and everything works fine.  I haven't upgraded to 2.2.2d yet - I'm
waiting for it to become more stable.  Probably by the time 0.98 comes out :)
-- 
Ed Carp, N7EKG     erc@apple.com                801/538-0177
"This is the final task I will ever give you, and it  goes  on  forever.   Act
happy, feel happy, be happy, without a reason in the world. Then you can love,
and do what you will."           -- Dan Millman, "Way Of The Peaceful Warrior"
From: pdp@ariel.its.unimelb.EDU.AU (Paul Douglas Page)
Newsgroups: comp.os.linux
Subject: zsh
Date: 23 Aug 92 09:13:45 GMT
Organization: University of Melbourne

After using zsh for a couple of months I have grown to like it.
Could someone direct me to a site that has the zsh source and Linux diffs ?

I would also be interested in knowing what the differences are between zsh
and ksh ? I have not seen ksh yet though I beleive there is a port for Linux
under way if not already available. 

What is the recomended shell to use with Linux? I know ash is shipped often with Linux root disks but I think it's a bit simple as shells go.

thanks in advance.
Newsgroups: comp.os.linux
From: sheldon@iastate.edu (Steve Sheldon)
Subject: Re: Installing Linux w/o destroying existing partitions
Organization: Iowa State University, Ames IA
Distribution: na
Date: Fri, 14 Aug 1992 21:14:39 GMT

In <1992Aug14.193838.16110@nas.nasa.gov> chiu@wk211.nas.nasa.gov (Ing-Tsau Chiu) writes:

>Wonder if there's any way to install Linux w/o destroying existing
>partitions.  (Sorry if this is an faq.)
>--
>--
>Ing-Tsau Chiu                       chiu@nas.nasa.gov

 Sure on floppy disks, silly! :-)

 There is some explanation of this in 'install.notes' written by
I Reid.  Actually it's an appendix towards the end written by
Drew Eckhardt.

 I personally wouldn't recommend it, even though I think I understand
what he's doing.

 Basically it seems to me that it's much more work than it is worth.
I did a complete backup of my harddisk of about 60 Megs of data to
floppy disks(720K no less! as I have hundreds of these), using
CP Backup 6.0.  It takes about 1/2 hour to backup, another 1/2 to
reinstall.
 If you've got more than 100 Megs, definately buy a cheap tape
backup for around $200.

 Basically, it just doesn't seem worth the possible frustration, and
you're going to have to backup the partition anyway.

 Any comments?

-- 
Steve Sheldon         sheldon@iastate.edu
Iowa Cooperative Soil Survey Resource Unit
2142 Agronomy, Iowa State University  (515) 294-5429
From: minyard@bnr.ca (Corey Minyard)
Newsgroups: comp.os.linux
Subject: Re: UUCICO doesn't fail properly
Keywords: uucp, uucico, taylor
Date: 21 Aug 92 03:54:39 GMT
Organization: Bell-Northern Research, Richardson, Tx.

I had the same problem with uucico, it did not time out on failure to
get in to the remote end.  It turns out the signal handler did not
set up interrupts to stop the read.  The fix is in the file sys1.c,
you should find the line:

        s.sa_flags = 0;

and change it to:

    #ifdef SA_INTERRUPT
        s.sa_flags = SA_INTERRUPT;
    #else
        s.sa_flags = 0;
    #endif

BTW, thanks to the people who provide all the nifty tools for linux.
I think linux is better than the commercial stuff we have at work.

Corey
-- 
----------------------------------------------------------------------

Corey Minyard
Newsgroups: comp.os.linux
From: drew@kinglear.cs.colorado.edu (Drew Eckhardt)
Subject: Re: DOS2Linux: Newbie to Newbie
Organization: University of Colorado at Boulder
Date: Wed, 12 Aug 1992 17:48:28 GMT

In article <1992Aug11.085511.3148@nntp.hut.fi> sakaria@vipunen.hut.fi (Sakari Aaltonen) writes:
>
>If your background is non-Unix like mine, you might find the following
>hints useful:
>
>1. You have compiled your first hello.c for Linux. You type
>  hello
>and nothing happens. Gotcha! Unlike MSDOS, say, Linux does NOT automatically
>search your current directory. You should type
>  ./hello


This isn't Linux, it's your PATH environment variable.  '.' must be 
explicitly stated in PATH.

To add . to your path, edit your .profile (Bourne shells), or .cshrc (C shells),
and add . to the PATH= (Bourne shell), or path=() (C shell) statement.  To 
add . to your path immediately under Bourne shell,

PATH=${PATH}:.

'C' shell : 

setenv PATH $PATH:.

Note that having . in your path is a security hole - if you are in 
/tmp or any other world writeable directory, or some users directory,
they can have mispellings of normal commands there to catch you.
If you screw up, they can have something SUID to you, and have 
access to all your files.  

Also, if . is first, things in the current directory will be 
executed first - so typing a normal ls in the wrong place can give some
one access to all your files.


-- 
Microsoft is responsible for propogating the evils it calls DOS and Windows, 
IBM for AIX (appropriately called Aches by those having to administer it), but neither is as bad as AT&T.  Boycott AT&T, and let them know how you feel. 

Newsgroups: comp.os.linux
From: rafal@utstat.uucp (Rafal Kustra (summer student))
Subject: Re: Need Help: Mtools
Organization: University of Toronto, Dept. of Statistics
Date: Sat, 22 Aug 1992 16:39:01 GMT

In article <1992Aug20.203910.7846@mcs.kent.edu> jhuang@Chaos.mcs.kent.edu (Jing Huang) writes:
>	Hello netters. I just realized that my "mtools" are behaving funny.
>
>	Specifically, when I used "mdir b:" the first time, it gave me the
>correct diretory list of the diskette. But then after I changed to another
>diskette, "mdir b:" gave me the old (the first) diretory list. In other words,
>"mdir b:" seemed to have a memory of only the first invocation. To get a file
>list of another diskette, I have to reboot Linux. That is crazy. "mdir c:"
>seems ok though.
>
>	What should I do to correct this behavior?
>
>--
>Jing Huang  |  jhuang@Chaos.mcs.kent.edu
>Department of Physics
>Kent State University
>Kent, OH 44242
>

Change floppy drive, perhaps. I remember having same
problem when building the system with NEC 1.44 FD.
It was in dos, that I discovered it and it was the drive.
Anyway, my mtools works fine.

				Rafal

-- 
/|| Numbers exist only in our minds. There is no physical entity that
 ||_is_ number 1. If there were, 1 would be in a place of honor in 
 || some great museum of science, and past it would file a steady
==== stream of mathematicians gazing at 1 in wonder and awe.