From: Marina Brown <marina@surferz.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] asn.1 alternatives
Date: Sat, 11 Feb 2006 12:52:11 -0500 [thread overview]
Message-ID: <43EE244B.6070301@surferz.net> (raw)
In-Reply-To: <8218ff6a1a57a150abfee58726f26a5a@proxima.alt.za>
lucio@proxima.alt.za wrote:
>>also, in my experience, managers (pointy-head or not) are rarely overly
>>caught up by the technical details. they just want such-and-such a problem to go away.
>>they usually don't really care how you do it, especially if it works well
>>and they never ever have to cut short a trip to the golf course because of it.
>>
>>
>
>I don't share your luck and I think few do, although this forum may be
>more fortunate in that respect. I am heading to Cape Town tomorrow
>morning to install MS Exchange in what will probably still be a NetBSD
>shop for a year or so. Me, when I have no idea what Exchange actually
>look like!
>
>This is what comes of bucking the trend successfully. IT management
>there believe it will cost them less to entrust the installation to me
>than to bring in an MCSE (by whatever the current label may be) that
>will install herself permanently behind the Exchange keyboard at a
>formidable monthly salary. What will in fact happen, sadly, is that
>I'll be blamed for all the things that will go wrong with MS Exchange,
>irrespective of the real responsibility, more things will go wrong
>than usual because I'll insist in front-ending Exchange with the
>existing Sendmail installation, modified in haste to deliver to
>Exchange instead of the local mailboxes. All sorts of extremely fancy
>features of Exchange will be used and the reliability of the existing
>system will soon will be forgotten.
>
>
>
Reminds me of last weekend - i got a paniced call from one of the sales
execs - one with a clue - to get him OFF the exchange server because of
the problems. Now he is happy to have his mail forwarded to a linux
virtserver
where he uses procmail and pine. I am ever so greatfull i am not responsible
for the exchange. I warned them against it and they went with a hosted
solution
which gives people 150MB of mailbox space.... About the volume i dispose of
after a long weekend.
Good Luck...
-- Marina Brown
next prev parent reply other threads:[~2006-02-11 17:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 0:10 [9fans] More 'Sam I am' quanstro
2006-02-11 3:01 ` jmk
2006-02-11 14:29 ` [9fans] asn.1 alternatives Charles Forsyth
2006-02-11 14:54 ` Sape Mullender
2006-02-11 16:13 ` lucio
2006-02-11 16:57 ` Skip Tavakkolian
2006-02-11 16:05 ` lucio
2006-02-11 17:52 ` Marina Brown [this message]
2006-02-11 16:28 ` Dan Cross
2006-02-11 16:53 ` Charles Forsyth
2006-02-11 22:47 ` Brantley Coile
2006-02-20 0:04 ` Harri Haataja
2006-02-11 6:04 ` ASN.1 (Was: [9fans] More 'Sam I am') lucio
2006-02-11 6:54 ` geoff
2006-02-11 8:06 ` lucio
2006-02-11 8:44 ` geoff
2006-02-11 12:10 ` lucio
2006-02-11 8:55 ` Steve Simon
2006-02-11 9:16 ` Bruce Ellis
2006-02-11 7:04 ` Skip Tavakkolian
2006-02-11 7:09 ` geoff
2006-02-11 7:53 ` lucio
2006-02-11 7:53 ` Skip Tavakkolian
2006-02-11 16:37 [9fans] asn.1 alternatives quanstro
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=43EE244B.6070301@surferz.net \
--to=marina@surferz.net \
--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).