9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ronald G Minnich <rminnich@lanl.gov>
To: <9fans@cse.psu.edu>
Subject: [9fans] My "plan9" stuff for Linux (last reference, I promise)
Date: Thu,  6 Dec 2001 09:12:24 -0700	[thread overview]
Message-ID: <Pine.LNX.4.33.0112060840350.17486-100000@snaresland.acl.lanl.gov> (raw)
In-Reply-To: <20011206072931.90885199E8@mail.cse.psu.edu>

v9fs.sourceforge.net, source and docs. Now builds on redhat and the demo
works (i.e. you can run /bin/cat and it will read the file from the "9p"
server). More details on the web page. VFS work for 2.4 in progress (you
can't do exec unless you have a VFS). There was major dry rot from 2.5
years of storage and the upgrade from redhat 5 to redhat 7 is still not
quite done.

mail list:  majordomo@lanl.gov, subscribe v9fs

Amusement time, I learned just how much shared libraries suck. So nice
that Plan 9 did not fall down that rathole. Masataka Ohta, where are you
now? You were right all along.

Here's a simple example: /bin/cat

/bin/cat /etc/hosts: opens 18 files (if no error); 323 symbol fixups.

many of the symbol fixups are for identical function (e.g. open, open64,
__open, __libc_open, etc). Some fraction of gcc lib is 64-bit-ized, some
is not.

There are > 5 different symbol versions supported: 2.0, 2.1, 2.1.3, 2.2,
2.2.something. This is in one library.

So the version number 2.2.2 on the file for libc-2.2.2.so is not really at
all useful, except maybe as a ceiling on version number.

Library-specific optimization: there is now a /lib/i686, and a /lib/i386.
Libraries are compiled different ways, and then you link to the right one
for your cpu. It's getting to the point where you no longer can make the
case that shared libraries save lots of space (unless you have a badly
designed windowing system or something).

Yikes, my brain hurts.

ron




  parent reply	other threads:[~2001-12-06 16:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-06  7:29 [9fans] python Russ Cox
2001-12-06  7:17 ` Lucio De Re
2001-12-06 16:12 ` Ronald G Minnich [this message]
2001-12-06 16:53   ` [9fans] My "plan9" stuff for Linux (last reference, I promise) Boyd Roberts
2001-12-06 16:57   ` Matt

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=Pine.LNX.4.33.0112060840350.17486-100000@snaresland.acl.lanl.gov \
    --to=rminnich@lanl.gov \
    --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).