[Mono-osx] configuring mod_mono for apache

Pierre Mignolet p.mignolet@ulg.ac.be
Tue, 26 Apr 2005 09:14:43 +0200


As I am a stupid beginner in Mac user and always on the mac site. I =
maybe
made a confusion between Panther and Tiger.

So I'm under Mac Os X 10.3 (Panther ?) and the solution of Andy works =
very
well.

Thx to all and sorry for the misunderstood.

P.Mignolet

-----Message d'origine-----
De=A0: Ian Stoba [mailto:ian@babcockbrown.com]=20
Envoy=E9=A0: lundi 25 avril 2005 20:21
=C0=A0: Adhamh Findlay
Cc=A0: mono-osx@lists.ximian.com; Pierre Mignolet
Objet=A0: Re: [Mono-osx] configuring mod_mono for apache

Please excuse my desperate plea:

Some of us are bound to NDAs for Apple's developer programs and do not=20
have seed keys. This means (at least in my case) that I need to close=20
my eyes, stick my fingers in my ears, and shout "I can't hear you!"=20
whenever anyone discusses Tiger. I think I'm also supposed to hop up=20
and down on one foot. You may be too, check the small print on your ADC=20
membership agreement.

Seriously, though, please don't mention any specifics about Tiger until=20
6:00PM on Friday when the NDA restrictions expire. My coworkers want me=20
to take my fingers out of my ears.

And yes, the merits of promotion through obscurity regarding Apple have=20
been debated ad nauseam. My concern is just not inadvertently breaking=20
the agreement I signed with them.


On Apr 25, 2005, at 10:35 AM, Adhamh Findlay wrote:

> Pierre Mignolet wrote:
>
>> Tiger.
>>
>> I have compiled all by default. It seems to be in=20
>> Library/frameworks/mono...
>>
>> I have launched xsp on port 8080 and try to called it, everything was =

>> right.
>>
>> Know I'm just trying to configure apache to call mod_mono.
>>
>> Thx
>>
> What build of Tiger are you running?
>
> Adhamh
> _______________________________________________
> Mono-osx mailing list
> Mono-osx@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-osx




This email message may contain information that is confidential and
proprietary to Babcock & Brown or a third party. If you are not the =
intended
recipient, please contact the sender and destroy the original and any =
copies
of the original message. Babcock & Brown takes measures to protect the
content of its communications. However, Babcock & Brown cannot guarantee
that email messages will not be intercepted by third parties or that =
email
messages will be free of errors or viruses.=20

If you do not wish to receive any further e-mail from Babcock & Brown,
please send an email to opt-out@babcockbrown.com.