From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <787c14d20612282124v3a815905y1f29ea9b1fd0b4eb@mail.gmail.com>
Date: Fri, 29 Dec 2006 10:54:25 +0530
From: "kensmith p" <kensmithp@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] /Library/LauchAgents/9pfs.plist
In-Reply-To: <3851d0a8471f122e12c32d723a45c464@terzarima.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <3851d0a8471f122e12c32d723a45c464@terzarima.net>
Topicbox-Message-UUID: fb8ba72e-ead1-11e9-9d60-3106f5b1d025

Hi Charles, I am new to limbo programming. Can you please give some
small sample program for exception handling to understand the concept.

Expecting reply,

Ken

On 12/21/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.
>