From owner-freebsd-chat@FreeBSD.ORG Fri Jul 15 06:21:14 2011 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B899106564A for ; Fri, 15 Jul 2011 06:21:14 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id D83C78FC1B for ; Fri, 15 Jul 2011 06:21:13 +0000 (UTC) Received: by gxk28 with SMTP id 28so510862gxk.13 for ; Thu, 14 Jul 2011 23:21:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=O3eiSDtG1lK+vLq3sTechJtT+EzOotzzyqRZXsbUh4U=; b=q9TbQLQSQA8LK9jue8kUumTkbmFUMltia/NI6E1XbspNWDSo7TQEKr6xoDv/NAbdII +o/l5h5wAneO4kpFDxFjDzdbj9tks+IUJnw68vgdXsSu+y/ykUGlxQx+SYd5Q1vb7J7r zSap5fXpUkBTWvKZSlHFDWFolVgNA37zPf8OM= MIME-Version: 1.0 Received: by 10.236.136.67 with SMTP id v43mr439795yhi.440.1310709461260; Thu, 14 Jul 2011 22:57:41 -0700 (PDT) Received: by 10.236.110.40 with HTTP; Thu, 14 Jul 2011 22:57:41 -0700 (PDT) Date: Fri, 15 Jul 2011 01:57:41 -0400 Message-ID: From: Aryeh Friedman To: FreeBSD chat Content-Type: text/plain; charset=ISO-8859-1 Subject: freebsd on rackspace X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2011 06:21:14 -0000 I just talked to rackspace tech support on an other issue and they said they plan to offer FreeBSD as a option after the upgrade from Zend Classic to Zend Enterprise (ETA not known).... but they did say we as a client are free to overwrite any slice on the virtual disk and then use the console to configure GRUB to boot that kernel... any ideas on how to proceed from this general advice to an actual implementation? ..... they also said if we did get it to work before the Zend upgrade was complete they would use our solution as the standard one