Why Are You NOT Using FreeBSD ?

[Zane C. B-H.]

On Mon, 04 Jun 2012 18:49:45 +0300
Daniel Kalchev <daniel at digsys.bg> wrote:

> 
> 
> On 04.06.12 18:04, xenophon\+freebsd wrote:
> >> -----Original Message-----
> >> From: owner-freebsd-stable at freebsd.org [mailto:owner-freebsd-
> >> stable at freebsd.org] On Behalf Of Daniel Kalchev
> >> Sent: Saturday, June 02, 2012 12:42 AM
> >>
> >> I really see no reason why your 'mail or calendaring server'
> >> should be able to wipe your devices.. This is the sort of bloat
> >> that keeps me away. From Microsoft products.
> > I don't think that's fair to say.  Email/calendaring seems to be
> > the only connection point between a smartphone and an
> > organization for at least the current crop of devices (although
> > I'm sure that at some point soon, you'll be able to include
> > organizational file servers as well).
> 
> Again, what does your e-mail or calendaring service have to do with 
> wiping your device clean?? Wiping the device is task for your
> device management platform, which does not belong to the e-mail or
> calendaring platform. If you connect your desktop to Exchange, is
> it supposed to be wiped too? What if the  Exchange account is just
> one of the many e-mail accounts you use, as typically is the case?

It is part of the protocol, Exchanged ActiveSync, used by Exchange
based mobile devices.

> >> In this regard I rather prefer the way Apple handles things.
> >> Shiny wrapper interface to pretty much generic technology. No
> >> reinvention of the wheel and experiments to see if it can be made
> >> square.
> > You can't damn Microsoft for being too proprietary in one
> > paragraph and then praise Apple for its openness in the next.
> > Does not compute.
> 
> I don't care how proprietary an proprietary thing is. If it is
> correctly implemented, it is ok, if it is not correctly
> implemented, it is not ok. Microsoft's "wipe trough Exchange" is
> weird, to put it mildly. Apple too had a track record of doing many
> proprietary things, but in recent years their offerings are, as I
> mentioned earlier, pretty much generic standard and widespread
> protocols with a lot of sugar coating.

From a enterprise perspective, it makes sense. Lets say a device goes
missing, it allows one to wipe it the next time it calls home.

The usefulness of such a feature is better disconnected from the
debate of proprietary v. non-proprietary though, given the different
nature of both issues.