From owner-freebsd-chat@FreeBSD.ORG Mon May 12 15:59:08 2003 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8AE737B401 for ; Mon, 12 May 2003 15:59:08 -0700 (PDT) Received: from digiflux.org (43.Red-80-59-151.pooles.rima-tde.net [80.59.151.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 395ED43FAF for ; Mon, 12 May 2003 15:59:07 -0700 (PDT) (envelope-from olivas@digiflux.org) Received: from sentinel (sentinel [10.0.2.5]) (authenticated bits=0) by digiflux.org (8.12.9/8.12.9) with ESMTP id h4CMx14P086631 for ; Tue, 13 May 2003 00:59:05 +0200 (CEST) (envelope-from olivas@digiflux.org) From: Stacy Olivas To: freebsd-chat@freebsd.org Date: Tue, 13 May 2003 00:59:01 +0200 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305130059.01754.olivas@digiflux.org> Subject: WarBSD 0.1 Released X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.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: Mon, 12 May 2003 22:59:09 -0000 WarBSD 0.1? Yeah, it's a little hack I did of PicoBSD .500 (using the FreeBSD 5.0-RELEASE-p7 source tree). After seeing WarLinux and how it used an embedded version of Linux to get the job done, I started wondering if PicoBSD could be used for the same thing. It can. After a few hours of hacking I got it done. It wasn't until recently that I decided to make it public. So, if you want to see my first attempt at dong something interesting with FreeBSD surf on over to the temporary home of WarBSD at http://digiflux.org/warbsd There you will find some general information and the source tarball that you can download and (if you have the FreeBSD source tree on your system) you can build your own copy. The system boots. I've got it using bsd-airtools for it's wireless sniffer. I'm running into a problem with the wi network driver. The README file tells you about it. I've decided to release this in hopes that someone will find it useful and maybe even point to way to getting it working right. Let me know what you think. Send all comments, suggestion, flames, etc to my address above. Thanks -Stacy