9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Brandon Black photon@nol.net
Subject: The future of Plan9?
Date: Mon,  5 May 1997 09:02:21 -0500	[thread overview]
Message-ID: <19970505140221.0kihhSVqTRF4gB_wFBLfbJuurBE-S46PYEC0WQAxGbU@z> (raw)



I can confirm that this is the correct approach for chroot-ing a network
service under Solaris.  See Sun's paper on setting up anonymous FTP under
Solaris (or was it a paper by a third party?  Its a paper by someone.. :)

They explicitly state that for anonymous ftp to work if it chroot()'s to
ftp's home directory, you must have certain files from the root filesystem
copied into the chroot() environment, including many, but not all, of what
you list below.  What you have down there, also, will only support UDP,
which I assume is fine for u9fs... you have to get /dev/tcp and the
related streams devices, etc.. to support tcp (which anon ftp needed).

Brandon


On Sun, 4 May 1997, Markus Friedl wrote:

> > file system directly" approach? And I haven't made u9fs work with chroot()
> > on the Solaris machine. To boot over the net I belive I need the chroot().
> 
> in order to make u9fs+chroot work under Solaris, I had to copy some
> files to the chroot-tree: (i did a strace and filtered the 'open' system
> calls, I'm not sure if you need all files)
> 
> 	/dev/zero
> 	/dev/ticotsord
> 	/dev/udp
> 	/etc/passwd
> 	/etc/nsswitch.conf
> 	/etc/netconfig
> 	/usr/lib/nss_compat.so.1
> 	/usr/lib/nss_nis.so.1
> 	/usr/lib/libnsl.so.1
> 	/usr/lib/libintl.so.1
> 	/usr/lib/libmp.so.1
> 	/usr/lib/libw.so.1
> 	/usr/lib/libsocket.so.1
> 	/usr/lib/straddr.so
> 
> you need chroot unless you want to mix the plan9 & the solaris
> file tree.
> 
> -markus
> 


/*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
 * Brandon Lee Black     * SysAdmin/Developer      *
 * F+E Applications Dept * WorldCom, Inc.          *
 *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
 *                Office * 281.362.6466            *
 *            Voice Mail * 800.362.1141 x6466      *
 *       Electronic Mail * photon@nol.net          *
 *                       * photon@gnu.ai.mit.edu   *
 *                       * vis_blb@unx1.shsu.edu   *
 *                       * brandon.black@wcom.com  *
 *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
 *          Numeric Page * 800.940.9797 x7012263   *
 * Alpha Page (Operator) * 800.940.9595 x7012263   *
 *   Alpha Page (E-mail) * 7012263@mobilecomm.net  *
 *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*/






             reply	other threads:[~1997-05-05 14:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-05-05 14:02 Brandon [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-05-08  4:39 Adam
1997-05-06  0:45 Eric
1997-05-04  9:04 Markus
1997-05-02 22:04 Bengt
1997-05-02 12:26 Digby
1997-05-02  0:59 Digby
1997-05-01 19:14 Greg
1997-05-01 18:28 Eric
1997-05-01 16:04 Berry
1997-05-01 15:25 Tom
1997-05-01 12:46 bwong
1997-05-01  7:45 Steve_Kilbane
1997-05-01  3:54 Digby
1997-04-30 23:48 Scott
1997-04-30 21:11 rsc
1997-04-30 20:09 Lucio
1997-04-30 17:06 Digby
1997-04-30  7:38 Borja
1997-04-30  6:01 Brandon
1997-04-29 23:28 Alex
1997-04-29 23:06 Digby

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=19970505140221.0kihhSVqTRF4gB_wFBLfbJuurBE-S46PYEC0WQAxGbU@z \
    --to=9fans@9fans.net \
    /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).