From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 19 07:07:46 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0EF28106566B for ; Thu, 19 Jan 2012 07:07:45 +0000 (UTC) (envelope-from vermaden@interia.pl) Received: from smtpo.poczta.interia.pl (smtpo.poczta.interia.pl [217.74.65.207]) by mx1.freebsd.org (Postfix) with ESMTP id 40FA98FC13 for ; Thu, 19 Jan 2012 07:07:44 +0000 (UTC) Date: Thu, 19 Jan 2012 08:07:43 +0100 From: vermaden To: freebsd-hackers@freebsd.org X-Mailer: interia.pl/pf09 In-Reply-To: References: X-Originating-IP: 194.0.181.128 Message-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interia.pl; s=biztos; t=1326956863; bh=p0rIxLqLvri3lxF6iiX+2I7z9B9TwJ4r6jMVKlJ0Y/0=; h=Date:From:Subject:To:X-Mailer:In-Reply-To:References: X-Originating-IP:Message-Id:MIME-Version:Content-Type: Content-Transfer-Encoding; b=BZ38XTzDCX6/WP4HW49/oqYkl4av4R0TJIZFa7RMaCua3aWpMMnkQvOdv3bt3IXH2 +uXGyQaXkydEJYq5/86yQjcppK1HSHjVY+b+eXD6VquKCjDK1p+poygqagQ/JooToi DW7fohhotgB5yKrNfV24klH11VBjI9Lmr3gaeOds= Subject: FreeBSD has serious problems with focus, longevity, and lifecycle X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jan 2012 07:07:46 -0000 (This is my earlier 'rant' about current situation, it was not 'approved' to the freebsd-hackers ML because I was not subscribed to it (my bad), possible little too much personal and emotional, but who we are without emotions, machines.) This well known 'open secret' FreeBSD problem also hit me many times, but as experience tells me, all of us would chick-chat here a lot what can be done to make things better and in the end ... nothing will happen. Many of You say 'step-up' and help/do something, I am actually or tried to do that in the past. I submit PRs and try to help test them as some developer/commiter will pick up the PR, submit a patch to test, but it was MANY times that the response from developer/commiter was way too long that I even DID NOT HAVE THE HARDWARE anymore ... Long time ago I had a lot of fun with emulation/virtualization using QEMU on FreeBSD, so I decided to write a FreeBSD Handbook section that would cover what I already known and it will help a LOT of people that would also want to use it the same or similar way. Here is one of the messages that I sent by then to the mailing lists: http://lists.freebsd.org/pipermail/freebsd-doc/2007-May/012507.html ... and NOTHING HAPPENED, no one told me what to do next, should I sent a SGML version or anything ... or just GTFO. Maybe that is the reason why my HOWTO 'QEMU on FreeBSD' was so popular before VirtualBox 'happened' on FreeBSD. And these Handbook pages are still available on my site to this very day: http://strony.toya.net.pl/~vermaden/FreeBSD-Handbook-Virtualization.htm I have an issue with my Lenovo X300 laptop that the 'output jack' for headphone did not worked as advertised, I submitted a PR, some the developer/commiter helped me to make it work by adding some 'hacks' to /boot/loader.conf (and it worked), but IT WAS NOE FIXED, these changes was never added to any branch, not even CURRENT, whats the point of fixing something if it is not even commited to at least CURRENT so it will not hit anyone anymore? Lets talk about Ports maintainers for a while, ftp/vsftpd maintainer for example, one of the options of this port is to provide a RC script so one will be able to start this FTP server with /usr/local/etc/rc.d script, but ... ITS NOT ENABLED BY DEFAULT, wtf people? Now every person that wants to use vsftpd NORMALLY will have to compile it instead of adding a package, so whats the need for building all the packages if You provide such useless defaults? Another example, net/samba*, its WELL KNOWN that samba sucks on FreeBSD with current selected defaults for this port, the current defaults are to DISABLE AIO support, but You only get good performance with samba on FreeBSD when the AIO is enabled, so another bunch of useless prebuilt packages, You need to compile anyway. Its options for FreeBSD, not every other OS on the world, so why not enable it? FreeBSD Ports are not PKGSRC where many systems are supported, if some option is 'good for default' why keep it disabled? What I have done about these 'Ports issues'? I contacted these ports maintainers and said that both RC script and AIO support for samba should be enabled by default by linking to several threads at FreeBSD Forums that the problem is known and exists ... and I did not get ANY RESPONSE till this very day, not even a GTFO (which would probably be better then nothing). I got these maintainers email addresses from http://freshports.org page, are they up-to-date there? Maybe that is the problem and that my mails jest went to /dev/null ... Just checking for sure. Its not that people does not try to help, a lot tried (and I am still trying), but its VERY unpleasant to have awareness, that You dedicated your time, tried to help as much as possible, made some steps to achieve that ... and no one even cares about that. At least some should say 'You are doing it wrong' try this and that, understand that, that is the way it works etc. Just my $0.02 on that well known FreeBSD problem and 'crisis'. With kind regards, vermaden