From owner-freebsd-advocacy Sun Oct 13 10: 4: 5 2002 Delivered-To: freebsd-advocacy@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9996D37B401 for ; Sun, 13 Oct 2002 10:04:03 -0700 (PDT) Received: from pepcross.com (pc-80-192-15-110-az.blueyonder.co.uk [80.192.15.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AE1743E88 for ; Sun, 13 Oct 2002 10:04:02 -0700 (PDT) (envelope-from steve@pepcross.com) Received: (from steve@localhost) by pepcross.com (8.11.6/8.11.6) id g9DH3gW00383 for freebsd-advocacy@freebsd.org; Sun, 13 Oct 2002 18:03:42 +0100 (BST) (envelope-from steve) Date: Sun, 13 Oct 2002 18:03:42 +0100 From: Stephen Roome To: freebsd-advocacy@freebsd.org Subject: What happened to FreeBSD ?? Message-ID: <20021013180342.C185@dylan.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG So far this year working with FreeBSD I've : 1) sent in a new port, ports/42234. 2) sent some bug reports to the maintainer of fetch and FTP that they bomb out on servers not supporting MDTM. 3) Asked for help with bktr 4) sent in a bug report about ports breaking (35218) A few years ago things would have happened to these, so far, well someone closed ports/35218 with just a straight it's a duplicate which is fair enough and des has said that he'll integrate the rather simple fix for MDTM support into (lib)fetch, but it's not happened yet. No one has mentioned anything about the new port and no-one has a response for help with some mods to the bktr driver. Which reminds me could someone now close gnu/29331 as this has been fixed. (I sent this one in over a year ago.) This all seems to be a bit like bin/22124. Back in 1996 I started work on some pci mods. I worked a bit with the guys doing the pci code then and I set some stuff up to have a pci device database (much as it works now) and get pciconf and bootup to be more informative about device found on the bus. The idea of a database of pci devices was at the time decided to be wrong, so later I submitted code for pciconf to just at least display the type of devices attached. But now it's the right to do it apparently and Mike Smith added stuff to current. In a message off list to me around the time he did mention that if he'd seen the code I'd done he'd probably just have committed that instead. So it took over three years for code very similar to the stuff I originally proposed to make into FreeBSD, and even then it took a bloody long route and wasted more than just my time in the process. So.. What the hell is wrong with FreeBSD, pr's don't ever seem to get looked at, or just closed with often impolite responses, and people like me, the sort of people who are FreeBSD advocates, developers and regular users, but not committers get more and more pissed off with the general attitude of adding what appears to be cruft and ignoring valid comments and code from a seasoned bunch of users. I've installed almost every FreeBSD version since 2.0.5 and use it daily but I'm starting to think that Linux might be a better bet while we have this complacency and general godhood type arrogance coming across. I'm not the only person to think this way either, most of my friends who are regular FreeBSD users are considering switching away while they are ignored and feel FreeBSD is just steadily flushing itself down the toilet. Besides, don't give me that shit about all being part-timers. Me too, and the work people like I do doesn't even get looked at because we're all too busy stabbing each other in the back and ignoring the complaints from the user base. Good luck, looks like you'll be needing it, Steve, pissed off with an increasingly crappy crufty OS. [I'm not subscribed to the list.] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message