9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Greg Hudson <ghudson@MIT.EDU>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] SO for plan9?
Date: Thu, 22 Jun 2000 09:19:20 -0400	[thread overview]
Message-ID: <200006221319.JAA25125@small-gods.mit.edu> (raw)
In-Reply-To: Your message of "Thu, 22 Jun 2000 08:49:11 EDT." <001001bfdc48$43bed880$9e096887@union1.nj.home.com>

> there is an article on what they call "DLL hell".  It debunks most
> of the supposed advantages of dlls and talks about all the problems
> they have caused.

By coincidence, I've read this article.  The primary problems
discussed in the article stem from the fact that Windows applications
often ship with replacement DLLs for system libraries.  This concept
is totally foreign to most Unix developers (even commercial Unix
developers, in my experience).

I have to wonder how much of the anti-shared-library sentiment on this
list comes from Windows experience.  Unix-based systems have been
using shared libraries with reasonable success for ages.  I'm sure
that it's more elegant if you can just use IPC or write small code,
but Plan 9 accomplished that goal at the expense of backward
compatibility with its predecessor, something a successful operating
system can probably never do.

(Incidentally, the person who thought you could trivially get a root
shell on Solaris using LD_LIBRARY_PATH should do his homework better.
The run-time loader unsets the LD_* variables for setuid programs on
all Unix systems supporting shared libraries; it's just too obvious of
a security hole to have been left open.)


  reply	other threads:[~2000-06-22 13:19 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-20  8:47 Oleg Krivosheev
     [not found] ` <kriol@wally.fnal.gov>
2000-06-20 16:12   ` Tom Duff
2000-06-21  8:41     ` Oleg Krivosheev
2000-06-21  9:03     ` Alexander Viro
2000-06-22  8:45     ` Douglas A. Gwyn
2000-06-22 12:49       ` Howard Trickey
2000-06-22 13:19         ` Greg Hudson [this message]
2000-06-22 21:47           ` Steve Kilbane
2000-06-26  9:00             ` Douglas A. Gwyn
2000-06-23  8:57           ` Douglas A. Gwyn
2000-06-23 13:05           ` Kasper Peeters
     [not found]             ` <K.Peeters@damtp.cam.ac.uk>
2000-06-23 16:01               ` Tom Duff
2000-06-24 10:10             ` Steve Kilbane
2000-06-20 10:13 rob pike
2000-06-21 15:16 dhog
2000-06-21 17:56 ` Randolph Fritz
2000-06-22  8:40 ` Oleg Krivosheev
2000-06-22 13:08 Anthony Sorace
2000-06-25 11:56 forsyth
2000-06-26  9:03 ` Michael Dingler
2000-06-26 10:23   ` Nigel Roles
2000-06-26 14:22     ` Steve Kotsopoulos
2000-06-26 14:44       ` Nigel Roles
2000-06-27  8:31       ` Michael Dingler
2000-06-28  8:27         ` Steve Simon
2000-06-28  9:40           ` Nigel Roles
     [not found]             ` <ngr@9fs.org>
2000-06-28 16:50               ` Tom Duff
2000-06-29 12:59                 ` Douglas Fraser
2000-06-29  8:31           ` Douglas A. Gwyn
2000-06-26 13:53 ` James A. Robinson
2000-06-26 14:09 rob pike
2000-06-26 14:31 ` Skip Tavakkolian
2000-06-28  8:28   ` Chris Locke
2000-06-28 14:50     ` Srinivasa, Balaji
2000-06-28 10:40 john
2000-06-28 19:35 forsyth
2000-07-07  2:15 rob pike

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200006221319.JAA25125@small-gods.mit.edu \
    --to=ghudson@mit.edu \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).