From owner-freebsd-chat@FreeBSD.ORG Sun Nov 2 05:04:19 2014 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 76EE8DA7 for ; Sun, 2 Nov 2014 05:04:19 +0000 (UTC) Received: from mario.brtsvcs.net (mario.brtsvcs.net [IPv6:2607:fc50:0:a400::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4E21A6E0 for ; Sun, 2 Nov 2014 05:04:19 +0000 (UTC) Received: from chombo.houseloki.net (unknown [IPv6:2601:7:400:640:21c:c0ff:fe7f:96ee]) by mario.brtsvcs.net (Postfix) with ESMTPSA id C1BC32C160E for ; Sat, 1 Nov 2014 22:04:16 -0700 (PDT) Received: from [IPv6:2601:7:2580:674:baca:3aff:fe83:bd29] (unknown [IPv6:2601:7:2580:674:baca:3aff:fe83:bd29]) by chombo.houseloki.net (Postfix) with ESMTPSA id 38A27A19 for ; Sat, 1 Nov 2014 22:04:15 -0700 (PDT) Message-ID: <5455BB53.3000607@bluerosetech.com> Date: Sat, 01 Nov 2014 22:04:19 -0700 From: Darren Pilgrim User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-chat@freebsd.org Subject: Re: FreeBSD turns 21 today! References: In-Reply-To: X-Forwarded-Message-Id: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.18-1 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: Sun, 02 Nov 2014 05:04:19 -0000 From: > FreeBSD turns 21 today! FreeBSD 1.0, the first official > production-ready release of FreeBSD was announced 21 years ago today, > on November 2nd, 1993. See the original announcement here[1]. > > 1: http://www.freebsd.org/releases/1.0/announce.html So how does one go about getting an OS cannot-find-my-ssh-keys drunk?