9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] /Library/LauchAgents/9pfs.plist
Date: Thu, 21 Dec 2006 08:52:00 -0800	[thread overview]
Message-ID: <3e1162e60612210852l20c4c97at3f5ca078651cfe27@mail.gmail.com> (raw)
In-Reply-To: <3851d0a8471f122e12c32d723a45c464@terzarima.net>

You can enable xinetd in launchd and do it the old way if you choose.
At least that used to be the case.

On 12/20/06, Charles Forsyth <forsyth@terzarima.net> wrote:
> once bsd unix used
>         9fs           stream tcp   nowait root   /bin/9/u9fs u9fs
>
> and xinetd made it a little bit more elaborate,
> but apple decided to combine init, x?inetd and cron
> (because they all start programs!) so in that dialect we must now say
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
> <plist version="1.0">
> <dict>
>         <key>Label</key>
>         <string>com.bell-labs.plan9.u9fs</string>
>         <key>Program</key>
>         <string>/usr/bin/u9fs</string>
>         <key>ProgramArguments</key>
>         <array>
>                 <string>u9fs</string>
>                 <string>-l</string>
>                 <string>/var/log/u9fs.log</string>
>         </array>
>         <key>Sockets</key>
>         <dict>
>                 <key>Listeners</key>
>                 <dict>
>                         <key>SockServiceName</key>
>                         <string>9pfs</string>
>                 </dict>
>         </dict>
>         <key>inetdCompatibility</key>
>         <dict>
>                 <key>Wait</key>
>                 <false/>
>         </dict>
> </dict>
>
> there are probably lots of useful options and better translations
> but at least it got me past that point last week.
>


  parent reply	other threads:[~2006-12-21 16:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-21  7:01 Charles Forsyth
2006-12-21 10:05 ` Gorka guardiola
2006-12-21 14:58   ` ron minnich
2006-12-21 15:06     ` Martin Neubauer
2006-12-30  3:01     ` Martin Atkins
2006-12-30  3:13       ` ron minnich
2006-12-31  7:44         ` Lyndon Nerenberg
2006-12-21 20:03   ` Lyndon Nerenberg
2006-12-21 12:55 ` Brantley Coile
2006-12-21 13:04   ` Anthony Sorace
2006-12-21 12:57 ` Brantley Coile
2006-12-21 15:32   ` Brantley Coile
2006-12-21 14:12 ` Russ Cox
2006-12-21 15:05   ` Anthony Sorace
2006-12-21 15:25     ` Rodrigo Miranda
2006-12-21 15:41       ` Denis Grelich
2006-12-21 16:52 ` David Leimbach [this message]
2006-12-21 17:17   ` C H Forsyth
2006-12-29  5:24 ` kensmith p
2006-12-21 15:11 erik quanstrom
2006-12-21 16:00 ` Dan Cross

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=3e1162e60612210852l20c4c97at3f5ca078651cfe27@mail.gmail.com \
    --to=leimy2k@gmail.com \
    --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).