HDTenEightyP/NetNews huggingface dataset:
From: pete@medea.rice.edu (Louis Wu)
Subject: Re: Distributed Shared Memory
Organization: Whatsamatta U
Date: Fri, 22 Jan 1993 19:04:21 GMT


mcdowell@exlogcorp.exlog.com (Steve McDowell) says:
>    I'm looking for pointers to work that's been done in the
>    area of transparent distributed shared memory for UNIX
>    systems. I am only aware of the "mether" system. Is there
>    anything else? 


On UNIX, there has been very little. Several people have used Mach's
external memory manager to implement DSM, but the performance of these
systems has not been spectacular.  Sorry, don't have these references handy.

Currently, Brian Bershad's (bershad@cs.cmu.edu) group at CMU is working on
a system called Midway that runs uses entry consistency.

@TECHREPORT{bershadzekauskas91,
	AUTHOR = {B.N. Bershad and M.J. Zekauskas},
	TITLE = {Midway: Shared Memory Parallel Programming with Entry 
			Consistency for Distributed Memory Multiprocessors},
	INSTITUTION = {Carnegie-Mellon University},
	YEAR = {1991},
	NUMBER = {CMU-CS-91-170},
	MONTH = sep}


I am currently building a DSM system at Rice that runs on top of SunOS and
Ultrix and implements various forms of eager and lazy release consistency.

@CONFERENCE{kelehercox92,
	AUTHOR = {P. Keleher and A. L. Cox and W. Zwaenepoel},
	TITLE = {Lazy Consistency for Software Distributed Shared Memory},
	BOOKTITLE = SIGARCH92,
	YEAR = 1992,
	PAGES = {13-21},
	MONTH = may}


@CONFERENCE{dwarkadaskeleher93,
	AUTHOR = {S. Dwarkadas and P. Keleher and A.L. Cox and W. Zwaenepoel},
	TITLE = {An Evaluation of Software Distributed Shared Memory for Next-Generation Processors and Networks},
	BOOKTITLE = SIGARCH93,
	MONTH = jun,
	YEAR = 1993,
	NOTE = {To appear}}

All of these articles talk about memory consistencies that will be used in
DSM systems rather than the systems themselves, but implementation and
performance papers on both the above systems will probably be submitted to
conferences in a few months.


Pete Keleher


--
=============================================================================
Pete Keleher   "Relax! Don't worry! Have a homebrew!"        pete@cs.rice.edu
=============================================================================

Newsgroups: comp.unix.wizards
From: aldavi01@starbase.spd.louisville.edu (Arlie Davis)
Subject: Re: How to avoid calling time(2)
Date: Thu, 28 Jan 1993 15:41:39 GMT
Reply-To: Arlie Davis <aldavi01@starbase.spd.louisville.edu>
Organization: University of Louisville

gcody@gandalf.ca (Gord Cody) writes:

> How about this. Each process attaches to a small shared memory
> segment when they start. 1 process has an alarm go off every
> second, it does the time() call and updates the shared memory.
> Whenever any other process requires the time, it simply uses the
> shared memory value. No setuid required, or running as root, or
> touching of /unix or /de/kmem required. Have a nice day :)

You're kidding, right?

-- 
lrwx------   1 aldavi01 emacsstu       9 Jun  6 12:43 .signature -> /dev/null
Xref: sparky comp.unix.wizards:5588 comp.unix.bsd:11658
From: markb@spock.dis.cccd.edu (Mark Bixby)
Newsgroups: comp.unix.wizards,comp.unix.bsd
Subject: Re: Palladium does exist!
Date: 21 Jan 1993 08:40:15 -0800
Organization: Coast Community College District, Costa Mesa, CA
Reply-To: markb@cccd.edu
NNTP-Posting-Host: spock.dis.cccd.edu

In article <1jmb02INNh7n@sol.tis.com> mjr@tis.com (Marcus J Ranum) writes:
>	It doesn't seem to actually exist. I.e.: Who is selling it
>right now?

Palladium does exist, and HP has been selling it as HP Openspool for at least
the past year.  When ordering our first Unix system, we took a look at the
lp spooler and thought "What a joke!".  Forms control?  Ha.  Paper jam 
recovery?  Ha.

Palladium/Openspool gives us these features and more.  It offers centralized
control of all network spooling.  Extensive opportunities for user
customization exist.  Plus you even get lp command-set emulation.  Or you can
use the native command-line set, or a Motif GUI.  The GUI is especially nice
for spooler administration/configuration tasks.

We're glad we went with it.  Lp would have been rather unsuitable for a 
high-volume production environment.
-- 
Mark Bixby                         Internet: markb@cccd.edu
Coast Community College District   1370 Adams Avenue
District Information Services      Costa Mesa, CA, USA  92626
Technical Support                  (714) 432-5064
"You can tune a file system, but you can't tune a fish." - tunefs(1M)
Newsgroups: comp.unix.wizards
From: gcody@gandalf.ca (Gord Cody)
Subject: Re: How to avoid calling time(2)
Organization: Gandalf Data Ltd.
Date: Thu, 28 Jan 1993 13:26:32 GMT

In <1993Jan27.195309.15120@cpio1.fr.mugnet.org> bernard@cpio1.fr.mugnet.org (Bernard Fouche) writes:

>Hi wizards!

>I run many applications that need to call very often the time(2)
>system call. I do not see how I could design my programs to do without
>having to get the result of time(2) very ofen.

>But I wonder if there is a way (on a 486 running Dell Unix 2.0 at
>least) to get time information without having to do a system call each
>time.

Every time you do a system call you are giving UNIX a chance
to swap your process.

>For instance, does someone know if I can get a pointer toward the
>value of time that is stored somewhere in the system ? Of course this
>should work with processes having no suid bit set nor running as root
>and files like /unix or /dev/kmem must stay to be not readable by
>anyone :-)

How about this. Each process attaches to a small shared memory
segment when they start. 1 process has an alarm go off every
second, it does the time() call and updates the shared memory.
Whenever any other process requires the time, it simply uses the
shared memory value. No setuid required, or running as root, or
touching of /unix or /de/kmem required. Have a nice day :)

Gord Cody - all opinions are MINE,MINE,MINE #$@%^#!##:^)  gcody@gandalf.ca
Gandalf Mobile Systems Inc. - the company has its own     613-723-6500 x 8817
2 Gurdwara Rd. Nepean Ont. Can.  - #define  th_th_th_thats_all_folks  }
Newsgroups: comp.unix.wizards
Subject: named pipe
From: marcello@deis20.cineca.it (Marcello Dalpasso)
Date: 22 Jan 93 18:53:26 +0100
Distribution: world
Organization: Dept. of Electronics, Computer Science & Systems, Univ. of Bologna, Italy

Is there any wizard on the net being so kind to summarize to me the usage of
named pipes?!

In particular, I would make something like this:

cp file named-pipe

and get "file" passed to lpr, i.e. named-pipe == | lpr

Thanks in advance for any help, preferably via e-mail

-- 
	Marcello Dalpasso (e-mail: marcello@deis20.cineca.it)
	D.E.I.S. - Department of Electronics, Computer Science and Systems
	Viale Risorgimento 2, I-40136 Bologna, Italy			
	Phone: +39-51-644-3015 (fax: +39-51-644-3073)
From: limes@straylight.eng.sun.com (Greg Limes)
Newsgroups: comp.unix.wizards
Subject: Re: asynchronous I/O to disk??
Date: 27 Jan 93 14:22:40
Organization: Sun Microsystems Computer Corporation (Mountain View, California,
	USA)
NNTP-Posting-Host: straylight
In-reply-to: jason@george.lbl.gov.itg's message of 27 Jan 93 19:30:31 GMT

In article <1k6nsnINNeq3@overload.lbl.gov> jason@george.lbl.gov.itg (Jason Lee (SFSU student)) writes:
|   I'm on a sun sparc (4.1.2) and I have three disks 
|   attached to it.  Now I want to read off the disks
|   simultaneously from the same process.

Check out "aioread" and friends. Section 3 of the manual.
--
   Greg Limes						[limes@eng.sun.com]
Not speaking for Sun Microsystems Computer Corp., Mountain View, California
From: nguyend@paul.rutgers.edu (Duc Nguyen)
Newsgroups: comp.unix.wizards
Subject: Increase file descriptor size
Keywords: file descriptor
Date: 27 Jan 93 19:45:43 GMT
Organization: Rutgers Univ., New Brunswick, N.J.


Hi,
I've been trying to increase the number of open file descriptors
per process and failing miserably. The call setrlimit() suppose
to set the soft and hard limit. The default is 64 for the soft
and 256 for the hard (I'm running SunOS 4.1.3). I could increase
the soft limit but I could not increase the hard limit beyond
256 (even when I'm the superuser). I tried looking under the
kernel and could only find the resource for the soft limit:
RLIMIT_NOFILE = 6. Can any of you wizards out there please
help me ? Sorry for any inconvenience. Thanks.
Please respond to
dnguyen@ida.org
From: robert@kommu.UUCP (3730)
Newsgroups: comp.unix.wizards
Subject: Heavy system load SINIX5.24NSC
Date: 21 Jan 93 10:15:00 GMT
Organization: SNC
X-Newsreader: Tin 1.1 PL5

I am running a configuration with 4 MX-SINIX5.24/NSC.
On one machine a dabtabase is runnging (ORACLE). 
The userinterface are SQLFORMS30-Masks which access via
SQLNET to the database.
On my backend - machine I am running out of memory therefore
the machine starts paging/swapping a lot.
Yesterday I had the problem that the machine had a 
system load of 90% ( 8 CPU ). 
After analyzing the system with TRACEX(a kernel trace-utility)
I found out that all the ORACLE-Backend processes approx. 80
made many of the following system-calls.
The interval for the listed number is 159 sec.

   sigvec   approx. 5000-6000
   sigsetmask  approx. 1600-1800
   sigblock  approx. 700
   sigpause   approx. 600

As I have no idea in understainding this values in terms of figuring out
if these are vlues that showing a synchronizationb problem ( TCP/IP,
acessing ALM-shared memory ...)  I would need the
help of a wizard.
THANKS
Xref: sparky comp.unix.wizards:5586 comp.unix.bsd:11649
From: mjr@tis.com (Marcus J Ranum)
Newsgroups: comp.unix.wizards,comp.unix.bsd
Subject: Re: IMPORTANT: POSIX threatens our use of lp/lpr and friends
Date: 21 Jan 1993 14:12:18 GMT
Organization: Trusted Information Systems, Inc.
NNTP-Posting-Host: sol.tis.com

[note newsgroups line re-edit]

>Can somebody please explain why palladium is a bad system?

	It doesn't seem to actually exist. I.e.: Who is selling it
right now? And you did notice the magic word "sell" in the previous
sentence? That means that either you'll pay for it even if you do
not want it, or you'll have it "unbundled" and you'll pay for some
of it even if you do not want it, and the old BSD stuff will still
be with your system, but the vendors will sneer at problem complaints
and bugfixes for it.
	Just say "no" to standardizing on vaporware. If it's real
good, once it's been out for a few years, everyone will want and
demand it and then it'll be worth standardizing on.

mjr.
-- 
                                                 "guns don't die. people do."
Organization: Pittsburgh Supercomputing Center, Carnegie Mellon, Pittsburgh, PA
Newsgroups: comp.unix.wizards
Date: Tue, 26 Jan 1993 15:05:43 -0500 
From: "Douglas A. Balog" <db6p+@andrew.cmu.edu>
Subject: Accessing the text segment of a process.

Hi,
 I want to have a subroutine that looks at the text segment of a process and
builds a table of what variables and functions are there. So that later on in
the program I can call a function or reference a variable by its name. Kind of
like asking a debugger to run a function.

I know of a way to compile the program, run a perl script which calls nm and
then recompile the program. But every time I recompile, I have to do it twice.

I also know of a way to popen(nm argv[0]) and find the info that way.

I really want to look at the text segment and figure this out.

Is this possible ?

Thanks for any info,
Doug
Newsgroups: comp.unix.wizards,comp.os.misc
From: rminnich@super.org (Ronald G Minnich)
Subject: Re: Distributed Shared Memory
Organization: Supercomputing Research Center (Bowie, MD)
Date: Sat, 23 Jan 1993 00:02:22 GMT

mcdowell@exlogcorp.exlog.com (Steve McDowell) says:
>    I'm looking for pointers to work that's been done in the
>    area of transparent distributed shared memory for UNIX
>    systems. I am only aware of the "mether" system. Is there
>    anything else? 

Well, last year we took the Mether model and used it 
as a guide to change the way 
NFS deals with mapped files. We call the result MNFS (for Mether-NFS). 
It works like NFS 
in most ways (save the way in which memory-mapped files work, for 
which a couple of things such as global ordering of writes apply)
and runs as NFS V3. There is a paper in HPDC-1 which makes an oblique 
reference to it. On Suns it runs as a loadable module, so you don't 
have to rebuild your kernel. 
We have an automounter that mounts MNFS, not NFS, when needed.

We're working out distribution details with Sun now. 

It's pretty fast ... we also made some changes to NFS where it would 
buy performance. We have a paper in the works, so I can't really give 
out much written material on it yet.

But we have run shared-memory programs from Crays on both Mether and 
MNFS on a cluster of SPARCStations we have here.
It works. 

Mether source is still available for the asking, as well.
It has been distributed to a fair number of places at this point.
But development here halted about ten months ago. MNFS is a nicer path.

Next step after MNFS, of course, is a hardware cut. That's in the works.
ron
-- 
Heard on WHFS: "... show brought to you by DC          | rminnich@super.org
Inaugural Balls. How can a city which has so           | (301)-805-7451 or 7312
few balls before an election have so many after?"      |
Xref: sparky comp.unix.wizards:5660 comp.os.misc:1059
From: i3558@newsie.dc.dk (Soren Michael Roug)
Newsgroups: comp.unix.wizards,comp.os.misc
Subject: Re: Distributed Shared Memory
Date: 26 Jan 93 17:42:27 GMT
Organization: Datacentralen A/S

mcdowell@exlogcorp.exlog.com (Steve McDowell) writes:

>I'm looking for pointers to work that's been done in the
>area of transparent distributed shared memory for UNIX
>systems. I am only aware of the "mether" system. Is there
>anything else? 

For what it is worth, one shouldn't forget Don Libes sharedmem package.
It exists in ftp.uu.net:/usenet/comp.sources.unix/volume14/sharedmem
and here is the README: ( Okay, it's a bit dated ;-)

The NBS Common Memory System (CMS)
Sept 25, 1987

This system emulates a shared memory system for 4.2BSD.  A common
memory server handles requests to access shared variables.  Because
communication uses TCP/IP, processes may be distributed across
machines.

The system is all user level code and requires no kernel
modifications.  This implementation provides interfaces for C and
Franz Lisp.  It is known to work on Sun UNIX releases from 1.0 to
3.4.

The system is documented by the files in the doc directory.
doc/usenix contains a paper that was presented at the Summer 1985
Usenix Conference.  The system has changed somewhat since then.

Installation instructions

This package depends upon a tiny communications library called
streamlib which must be installed first.

	cd stream
	cat README

and follow the directions in there.

Once you have installed streamlib, change to the common memory
source directory and run make.

	cd ../src
	make install

If you would like to try out some of the examples, type:

	make examples

The examples are numbered as sets.  I.e. client1 runs with server1.
The most interesting is server1y, server1z, client1a and client1b.
Run these in 4 different windows.  They are documented by their
source and serve as coding examples.

Don Libes
National Bureau of Standards
Metrology Building, Room A-127
Gaithersburg, MD  20899
(301) 975-3535

libes@cme-durer.arpa
uunet!cme-durer!libes


-- 
Venlig hilsen Soren Roug, <smr@dc.dk>                     DataCentralen
Telefon: 43 71 81 22 Lokal 3820, Telefax 43 71 33 12      Oldenburg Alle 1
						          2630 Taastrup
I havent't lost my mind -- I'm sure it is backed up somewhere.
Newsgroups: comp.unix.wizards
From: wv@dasc.nl (Wouter Visscher)
Subject: Detection broken tcp connection
Summary: Detection broken tcp connection in an application
Keywords: tcp connection broken
Organization: Data Sciences B.V.
Date: Wed, 27 Jan 1993 14:14:59 GMT

Dear wizards,

I have te following situation:
A tcp connect, with keep_alive option and non blocking mode.

If the ethernet fails ( pull out a drop cable for instance) I want
my application to detect a broken connection.

Want can I expect in my application:
A - from a select
B - from a send
C - form a recv
D - signals
E - Any other means to determine the broken connection

Also a indication of the times involved on sunos 4.1 .

The manuals are not to clear on this subject, testing showed  the above calls
i.e. select, send, recv did not return error codes indicating a problem.
Mind you if an error code is only return once I might have missed it during
this test


#include <stddisclaimer.h>       This might not be the view of my employer.
Newsgroups: comp.unix.wizards,comp.unix.bsd,alt.suit.att-bsdi
From: lancelot@spock.uucp (Thor Lancelot Simon)
Subject: Re: BSDI/USL Lawsuit -- More Bad News for Human Beings...
Organization: Choate Rosemary Hall
Date: Tue, 26 Jan 1993 21:57:08 GMT

In article <18102@umd5.umd.edu> mark@roissy.umd.edu (Mark Sienkiewicz) writes:
>>] I think it would be a great idea if USL people showed up.
>>] This way, we could tell them, in person, what we think.
>>] That's what USENIX is all about!
>>
>>Look, I'm not fond of what USL is doing *as* *a* *corporate* *body*, but
>>I like a lot of the things the folks in the trenches have done.  Do you
>>seriously want to be abused because of the corporate policies of *your*
>>employer?
>
>It _is_ an opportunity to talk to USL people.  It should _not_ be looked
>at as an occasion to yell and scream at them.
>
>If 50 people a day come to their booth and say "The USL suit against BSDI
>is making you look _really_ _bad_", that will get noticed.  If you staff
>a booth at a trade show, its your _job_ to tell your employer when people
>are saying stuff like that.
>
>But resist the urge to say "You're all a bunch of assholes!!!"  The people
>you talk to didn't cause this and don't deserve to take the heat for it.
>
>Be nice and you might get your point across.  Be nasty and you just turn 
>them against you.

It is a shame nobody thought to organize pickets.  That might be the right
blend of nice and nasty for the occasion.
-- 
*******************************************************************************
*Thor Simon             * Okay, just a little pin-prick...There'll be no more-*
*tls@panix.COM          * Aieeeeaaaugh!-but you may feel a little _sick_.     *
*tls@spock.UUCP         *   ---Pink Floyd                                     *
*******************************************************************************

Xref: sparky comp.unix.wizards:5614 comp.org.eff.talk:9126 comp.org.usenix:1370 comp.unix.bsd:11721 alt.suit.att-bsdi:831
From: jbotz@mtholyoke.edu (Jurgen Botz)
Newsgroups: comp.unix.wizards,comp.org.eff.talk,comp.org.usenix,comp.unix.bsd,alt.suit.att-bsdi
Subject: Re: BSDI/USL Lawsuit -- More Bad News for Human Beings...
Date: 22 Jan 1993 19:03:23 -0500
Organization: Mount Holyoke College
Distribution: inet
NNTP-Posting-Host: slab.mtholyoke.edu

In article <C12urA.7Dw@wimsey.bc.ca> sl@wimsey.bc.ca (Stuart Lynne) writes:
>Given the importance of presenting a positive image at a large trade
>show and the $$$ spent to achieve it, you can bet that two things would
>happen. First you *would* get noticed. And second you would probably be
>escorted off the premises.

Excuse me?  Get escorted of USENIX premises for telling a USL employee
what I thought USL could do with their lawsuit?  What the hell?  Nobody
is likely to beat anybody else up over this, you know, and this /is/ a
free country, and AT&T (or Novell) is /not/ big brother.
-- 
Jurgen Botz, jbotz@mtholyoke.edu
Northampton, MA, USA
Newsgroups: comp.unix.wizards
From: sbo@bcars656.bnr.ca (Stephane Boucher)
Subject: Problem implementing an NFS server... 
Organization: /u/sbo/.organization
Date: Thu, 28 Jan 1993 18:12:08 GMT
Comments: Hyperbole mail buttons accepted, v3.06.


Hi,

I know people asking questions here should be able to write Unix from
scratch, but I'll ask you a question anyway :-) (I think it requires
some wizardry knowledge)

I'm writting an nfs front end to a database, but first I am testing
the basic functions by just mirroring a regular ufs through my own
nfsd.

Sytem used:
	Sparcstation with SunOS4.1.1

The server:
	It listens to port 2048, and it does not register itself to 
	the portmapper;
	It is based on NFS Protocol version 2

Client Side:
	I have written a mount command that does a mount system call.
	This allows me to use a port that is different from the standard
	nfs port, and thus have my own server cohexist with standard NFS.

1. Now, after mounting the filesystem, I do an ls -R and I get
everything listed. I can see the server processing nfs_getattr,
nfs_readdir and nfs_lookup calls and everything runs as expected.

2. If I issue the ls command a second time, the only call that the
server will have to serve is a single call to nfs_getattr.

3. If I do a touch on the mountpoint, then I essentially am back to 1
when I do an ls command, otherwise I'm stuck in the situation 2.

This is if my nfs_getattr gives the time(atime,mtime,ctime) that the
physical file has.

However, things work as expected when I cheat and use the current time
(as returned by time(3)) for the value of mtime, except for the fact
that mtime is not what it should be.

Why is this?

Any help will be  greatly appreciated.

Thanks in advance.

BTW, if you don't think it is an interesting question, then maybe you
should just answer to me by e-mail.
--
  ,
Stephane Boucher | Bell-Northern Research
sbo@bnr.ca       
Newsgroups: comp.unix.wizards,comp.unix.bsd,alt.suit.att-bsdi
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: BSDI/USL Lawsuit -- More Bad News for Human Beings...
Organization: Netcom Online Communications Services (408-241-9760 login: guest)
Date: Sat, 23 Jan 1993 05:20:46 GMT

Perhaps we could state our arguments to our Congressman or Senators,
for instance, think about all the *free* R/D development which is
going on at least on 386BSD and Linux. I just hate to see USL
step to close to stiffle our work in the 386bsd or Linux arena.


-- 
This message brought to you by the letters X and S and the number 3
Amancio Hasty           |  
Home: (415) 495-3046    |  ftp-site depository of all my work:
e-mail hasty@netcom.com	|  sunvis.rtpnc.epa.gov:/pub/386bsd/incoming
Xref: sparky comp.unix.wizards:5655 alt.suit.att-bsdi:846
From: pcg@aber.ac.uk (Piercarlo Grandi)
Newsgroups: comp.unix.wizards,alt.suit.att-bsdi
Subject: Re: ENOUGH! Re: BSDI/USL Lawsuit -- More Bad News for Human Beings...
Date: 27 Jan 93 20:33:13 GMT
	<MIKE.93Jan22144301@cuba.vlsivie.tuwien.ac.at>
	<1993Jan23.212839.7548@prl.dec.com>
Organization: University College of Wales, Aberystwyth


In article <MIKE.93Jan22144301@cuba.vlsivie.tuwien.ac.at>,
mike@vlsivie.tuwien.ac.at (Michael Gschwind) writes:

	[ ... A list of BSD contributions ... ]

On 23 Jan 93 21:28:39 GMT, boyd@prl.dec.com (Boyd Roberts) said:

	[ ... a list of equivalent BTL modules ... ]

Summarizing:

	BSD				BTL

	paging				paging
	FFS				BITFS
	jobcontrol			xt
	csh				rc
	sockets				streams
	vi				sam
	curses				[unnecessary: blit]
	termcap				[unnecessary: blit]
	sendmail			upas
	dbx				pi

There are two interesting aspects to all this:

* The BSD material has been almost completely copied into the USL product,
  and (perhaps regrettably) virtually none of the BTL stuff has.

* The BSD technology on average was developed a few years before the
  equivalent BTL.
Newsgroups: comp.unix.wizards