Even a working driver without any management utilities is not what I would want to run on a production server. I need to be able to find out what is wrong with the RAID setup, if anything, state of all the disks, etc... which I cannot do without rebooting. And I fail to see how letting a community write their own management utility buy just releasing some documentation could hurt in any way. Please, someone answer me, how is not releasing JUST DOCUMENATION, to let a community support themselves, AND BUY YOU'RE HARDWARE, worth losing all this business.
Jason On Sat, 19 Mar 2005 13:29:36 -0700, Scott Long <[EMAIL PROTECTED]> wrote: > It's not a binary driver, it's a 2-clause BSD licensed driver that > contains full source. You said that the OpenBSD driver is unstable, > so I offered to help. That has nothing to do with binary apps. > Deleting it from the OpenBSD tree is always an option, of course. > > Scott > > Jason Crawford wrote: > > The OpenBSD community doesn't want help for closed utilities and > > drivers. All we want is documentation. No source, no > > binary-only-cannot-distrubute drivers and utilities, just enough > > documenatation for which to write their drivers, and support > > oursevles. No one has been able to answer us on how releasing just > > documentation would lose them so much business that it's worth losing > > all this business. > > > > Jason > > > > On Sat, 19 Mar 2005 13:21:19 -0700, Scott Long <[EMAIL PROTECTED]> wrote: > > > >>Jason Crawford wrote: > >> > >>>The problem is that the AAC driver doesn't work. My 3.6-stable dell > >>>poweredge server with that raid controller crashes at least once a > >>>week because of the raid controller driver. There is nothing wrong > >>>with fighting for something that you want, and neither you nor Doug > >>>have been that helpful. All Doug did was give Theo the run-around by > >>>saying, don't worry, we'll be coming out with all new stuff! Which he > >>>neglected to mention that they wouldn't be opening documentation for > >>>either, at least enough to write a stable driver and management > >>>utility. Adaptec would not be losing any money for just releasing > >>>enough docs to let someone else write their own driver and management > >>>utility TO USE ADAPTEC'S HARDWARE. They'd be generating more business. > >>>This attitude so far has been quite productive, the OpenBSD community > >>>has gotten many wireless firmware's and drivers completely open, not > >>>to mention Theo getting the FSF award. I'd say that is pretty damn > >>>productive. > >>> > >>>Jason > >>> > >> > >>If the OpenBSD driver is buggy, then ask for help. I don't normally > >>monitor the OpenBSD mailing lists and I don't run it at home, so I have > >>no idea what the state of it is. I do, however, answer email from > >>developers from other projects who contact me. The hardware is tricky > >>to get right and there are bugs in different cards and different > >>firmware versions that often need to be worked around. It's all > >>documented in my driver, and I'm happy to share my knowledge. > >> > >>Scott > >> > >> > >>>On Sat, 19 Mar 2005 13:08:06 -0700, Scott Long <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>>>Adam wrote: > >>>> > >>>> > >>>>>On Sat, 19 Mar 2005 12:34:09 -0700, Scott Long <[EMAIL PROTECTED]> wrote: > >>>>> > >>>>> > >>>>> > >>>>>>I would have been happy to > >>>>>>help. Heck, I might have even ported the management app (AACCLI, not > >>>>>>a GUI, btw) for you like I did for FreeBSD. Barring that, I would have > >>>>>>been happy to show you how to do the linux compat shims for the driver > >>>>>>so that you could use the Linux AACCLI on OpenBSD. But no, you never > >>>>>>contacted me. > >>>>> > >>>>> > >>>>>Does everyone who's worked at adaptec have such big problems with reading > >>>>>comprehension? Nobody wants a maybe working, cludgy, binary only tool. > >>>>>How would giving the developers something they don't want be considered > >>>>>"helping"? > >>>>> > >>>>>Adam > >>>> > >>>>I can't see how the All Or Nothing attitude here is productive. Good, > >>>>you guys want to produce fully open and unencumbered stuff. That's > >>>>wonderful. But why is it so important to go around screaming and > >>>>yelling about it and alientating those who do try to help? Let me > >>>>tell you, Doug is about the most positive and supportive guy you'll > >>>>ever have at Adaptec, pissing him off really won't produce results. > >>>>Why is it so important to drag your users into your political fights > >>>>by depriving them of stuff that works now but isn't exactly everything > >>>>that you want? I'd love to have fully open stuff from all the RAID > >>>>companies too, but I also want the users of FreeBSD to be able to use > >>>>the resources that are out there to their full advantage and not be > >>>>pinned down by my political beliefs on the subject. > >>>> > >>>>Scott > >>>> > >>>> > >> > >> > > _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
