From owner-freebsd-stable@FreeBSD.ORG Tue Jun 5 04:31:20 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC2BD106564A for ; Tue, 5 Jun 2012 04:31:20 +0000 (UTC) (envelope-from v.velox@vvelox.net) Received: from vulpes.vvelox.net (vulpes.vvelox.net [99.69.115.42]) by mx1.freebsd.org (Postfix) with ESMTP id 296978FC0C for ; Tue, 5 Jun 2012 04:31:19 +0000 (UTC) Received: from vixen42.vulpes.vvelox.net (vixen42.vulpes.vvelox.net [192.168.15.2]) (Authenticated sender: kitsune) by vulpes.vvelox.net (Postfix) with ESMTPA id 51A4F3F62E for ; Mon, 4 Jun 2012 23:32:36 -0500 (CDT) Date: Mon, 4 Jun 2012 23:33:08 -0500 From: "Zane C. B-H." To: freebsd-stable@freebsd.org Message-ID: <20120604233308.25183995@vixen42.vulpes.vvelox.net> In-Reply-To: <4FCCD919.2080502@digsys.bg> References: <20120601121555.GF5335@home.opsec.eu> <4FC8B67D.5090208@digsys.bg> <31DFBF41-37EC-43CF-A555-2D4E46F1F6E2@ee.ryerson.ca> <4FCCD919.2080502@digsys.bg> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Subject: Re: Why Are You NOT Using FreeBSD ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2012 04:31:20 -0000 On Mon, 04 Jun 2012 18:49:45 +0300 Daniel Kalchev wrote: >=20 >=20 > On 04.06.12 18:04, xenophon\+freebsd wrote: > >> -----Original Message----- > >> From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd- > >> stable@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). >=20 > Again, what does your e-mail or calendaring service have to do with=20 > 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. >=20 > 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. =46rom 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.