From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 05:49:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9883D16A40F for ; Fri, 15 Sep 2006 05:49:36 +0000 (UTC) (envelope-from verbo.solo@sbcglobal.net) Received: from smtp101.plus.mail.re2.yahoo.com (smtp101.plus.mail.re2.yahoo.com [206.190.53.26]) by mx1.FreeBSD.org (Postfix) with SMTP id 136B743D46 for ; Fri, 15 Sep 2006 05:49:35 +0000 (GMT) (envelope-from verbo.solo@sbcglobal.net) Received: (qmail 65971 invoked from network); 15 Sep 2006 05:49:35 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Received:Subject:From:To:Content-Type:Date:Message-Id:Mime-Version:X-Mailer:Content-Transfer-Encoding; b=hPyAgU4TihTX9UgZ0IZFMnjEUZ89/EX6icNolXTElydy66Zi8udKhPpvk5qBkwkk0oKXGWzNjEN82ZJZTYSBX2ueFEGyWAA+fF8HMSVAwEACjJiU480YRPlFNpO+OTwuOPD5QBRMtZJWkEPENCeHJ4dEZUvBKib3BXc9F+Fqv1Q= ; Received: from unknown (HELO elbereth.gateway.2wire.net) (verbo.solo@sbcglobal.net@69.151.15.132 with plain) by smtp101.plus.mail.re2.yahoo.com with SMTP; 15 Sep 2006 05:49:35 -0000 From: "Charles P. Schaum" To: "freebsd-stable@freebsd.org" Content-Type: text/plain Date: Fri, 15 Sep 2006 00:49:33 -0500 Message-Id: <1158299373.1608.72.camel@elbereth.gateway.2wire.net> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: PC-BSD and DesktopBSD compared to FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Sep 2006 05:49:36 -0000 A note on PC-BSD and DesktopBSD as compared to my -STABLE experiences: -STABLE works best. First, PC-BSD will panic under more conditions than -RELEASE, -STABLE or DesktopBSD. I did some monkeying around and found that to be true, especially with older boxes. Second, DesktopBSD works better than PC-BSD, and noticeably so. But it's based on 5 and I want 6. So that kinda throws a spanner in the works. Both desktop installers, however, do not easily support an install over multiple disks or a lot of customization. FreeBSD does. That's the same reason why I like the Debian installer and the old Ubuntu installer over many of the others. (Although the Ubuntu installer, old and new, has geometry issues.) Fedora's default is to use an LVM setup that will be a pain in the tush if you install anything else over it unless you use a third-party util to hose all the LVM info. Merely creating a new FS, i.e., installing FBSD in the slice where Fedora was, won't cut it; you will get weirdness in the boot loader. When I want desktop, I don't want dumb. I want defaults for those that want them and then I want to depart from that when needed. The desktop attempts based on FreeBSD do not easily handle this. I see that as basically a show-stopper. The elegant thing about FreeBSD is the way in which one can vary things to meet individual needs. This is no "canonical distro" template mentality. The real trick is to make a desktop work with such variation. One thing I see, for example, is an opportunity to have a decision like "here is some default art, themes, whatever" in a port/package for those that want a "my machine looks like FreeBSD" feel. One might suggest that all ports that would normally be associated with menus and MIME types in XFCE, KDE and Gnome, etc. would arrange to install these in the expected places. Presently, some do; some don't. One need not integrate a lot into the OS. Indeed, scripts for removable media events and the like can safely remain in ports. But it strikes me that Linux and Windows, as well as MacOS, all have a certain "look and feel" per distro and that a move to say "for those that want a default option of >>look and feel<< and don't want to continually edit menus (for which KDE is easiest) then we have a plan for you." This would not add too much burden to the port maintainers and it would just make the learning curve a little easier for noobs, until they do a BOFH-recommended action after failing to RTFM. Even running the autoconfig for X, if X is installed, and allowing a GUI login manager selection menu in the installer couldn't hurt. After all, if one bundles things like Gnome and KDE on distribution media, why not go the distance and give the option to do all the preliminary integration in the installer, if so selected? For example, I have no problem installing NetBSD, knowing that I first go to the utility menu and set up the NIC, then install, then say yes, I want those NIC settings to save some work, then do the reboots and set things up. Then I tweak more files and add software with pkgsrc. But that's extra work that FreeBSD already integrates to some extent into one installer session. Why not continue along that path? What about a menu that allows an expert mode for certain stages as well as just a default decision like "I want FreeBSD with KDE/Gnome." For example, if pdftk or ImageMagick blow up /var/tmp when batch converting or if OpenOffice takes about 9G to compile, then one could consider a resource needs database correlating to packages desired at install time. Given, that puts stress on the size of the image. It could also be a DVD-only option. One could select the ports that one would eventually like (perhaps like synaptic) and the needs could be anticipated for install-time FS-tuning. A subsequent option might allow installation via pkg_add or simply set up a script and notify root to run it in the background to fetch and install the desired packages at a later time. Such an approach would take the selection of distributions and packages to perhaps another level. Yes, it violates the "small is better" dictum but it also recognizes that the folks at the middle of the bell curve are great in number and short on technical mastery. The decision comes when the target market is determined. It would also give a certain "slick" factor. That might not always be good, but remembering old Amiga demos, I can hardly deny that eye candy and ease of use does attract. Part of the desktop thing for me is that I am partially blind and I find that Gnome is very friendly to my vision, or lack thereof. It causes much less eye strain than other desktops. So I like working from that environment for accessibility issues. I like the idea of a challenge and solving a problem. I like FreeBSD. I don't get off on messing with pixmaps, menus, MIME types and other mickey-mouse stuff. Requiring a certain standard of desktop integration by port maintainers, giving the option of a default look and feel and otherwise keeping things robust and packing more configuration steps into the installer would suit me fine. Charles