Re: qemu support for OpenBSD as a guest on sparc, mips, mipsel, arm, ppc, amd64
On Fri, Jan 05, 2007 at 03:08:47AM +0530, Siju George wrote: > Hi, Hi! > will the SGI port run under mips/mipsel? 'mipsel' not, since the SGI port uses big endian mips. On some parts it has code for little endian too, but not everywhere. If you mean by 'mipsel' the gnu toolchain target then it is even harder, since it is 32bit. SGI is mips64. There are a lot of different mips designs. Don't get confused ;) The different desings support different subsets of commands... Besides that, you will need macebus/crimebus on the qemu to use the SGI port. Sorry, Rainer
Re: OpenBSD as a PDC on a windows network
Hi Stuart, On Wed, Nov 01, 2006 at 04:59:21PM -0500, stuartv wrote: > > This project is all part of my devious plan to gradually > convert to an all (or at least mostly) OpenBSD environment > here at work (psst... don't tell my boss). If this pans out, > I think replacing our SQL server with MySQL on an OpenBSD box > will be the next big conquest. :) I would not do that if i were you. It does not matter if you use MySQL or PostgreSQL or any other. Changeing the backend for MSAccess is a pain in the a**, especially if you have frontends written in VisualBasic (dudes checking for -1 instead of false...). You will become at least problems with compatibility of the data types. /dev/rainer
Re: OpenBSD as a PDC on a windows network
> >You will become at least problems > I want to become a vegetable. > (SCNR.) > ;-P Aaargh, what a shame! ;(
Re: OpenBSD as a PDC on a windows network
On Thu, Nov 02, 2006 at 09:24:49AM -0700, Jeff Ross wrote: > Rainer Giedat wrote: > >Hi Stuart, > > > >On Wed, Nov 01, 2006 at 04:59:21PM -0500, stuartv wrote: > >>This project is all part of my devious plan to gradually > >>convert to an all (or at least mostly) OpenBSD environment > >>here at work (psst... don't tell my boss). If this pans out, > >>I think replacing our SQL server with MySQL on an OpenBSD box > >>will be the next big conquest. :) > >I would not do that if i were you. It does not matter if you > >use MySQL or PostgreSQL or any other. Changeing the backend > >for MSAccess is a pain in the a**, especially if you have > >frontends written in VisualBasic (dudes checking for -1 instead > >of false...). You will become at least problems > >with compatibility of the data types. > > > >/dev/rainer > > > > But that is exactly what we _did_ do at work. We moved from MS Access > to PostgreSQL seamlessly by using psqlodbc. That let us put our data in > a real database, eliminated all of the data corruption problems we were > having with Access, and let our users continue to use the forms and > whatnot that they were used to while we coded up a web front end (using > php, to throw a comment out there to another thread running on misc@). If you had data corruption, you had a reason to change it. Stuart seemed like he wants to do it only to get rid of the windows boxes. > The boolean problem mentioned above is a checkbox in the ODBC driver > configs--not a very big PITA compared to supporting Access! I know. It was only the first example which came to my mind.. I had to change a lot of code to get it running. I also had stability problems with psqlodbc. When did you do that? Maybe psqlodbc is better now... > Jeff Rainer
Re: MIPS based routerboard machines
Hi, > Hi, > > I would support (money|board) a BCM95352E[1] based solution like > the Linksys WRT54GL[2]. The HW is pretty cheap ca. 60 Euros. I am working on support for BCM947xx[1] at the moment. I have a WRTG54 v2.0, which is ok for now, but documentation would help very much. ;) There is nearly no documentation for the Broadcom specific stuff. [2] is a good start, but most of this informations can also be found at the gpl'ed sources of Linksys firmware and the openwrt project. So, if you want to help: Ask Braodcom for documentation! And again and again and again ;) Bye bye, Rainer [1] http://www.broadcom.com/products/Wireless-LAN/802.11-Wireless-LAN-Solutions/BCM94712 [2] http://bcm-v4.sipsolutions.net/
