From owner-freebsd-current Mon Sep 16 18:22:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 075A937B400 for ; Mon, 16 Sep 2002 18:22:19 -0700 (PDT) Received: from hun.org (hun.org [216.190.27.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FDE343E65 for ; Mon, 16 Sep 2002 18:22:18 -0700 (PDT) (envelope-from attila@hun.org) Received: by hun.org (Postfix, from userid 1001) id 154A53463E; Tue, 17 Sep 2002 01:22:18 +0000 (GMT) Date: Tue, 17 Sep 2002 01:22:17 +0000 (GMT) Message-Id: <20020917012217.ijdM73487@hun.org> From: attila! X-Mailer: AttilaMail with XEmacs & Postfix on FreeBSD 5.0-CURRENT X-Ballistic: N 37.218497 W 113.614979 X-No-Archive: yes In-Reply-To: <6C3D95B5-C8AC-11D6-AF56-0003937E39E0@mac.com> References: <20020914173520.G91535-100000@mail.allcaps.org> To: CURRENT Cc: Matthew Jacob , leimy2k@mac.com Subject: Re: FreeBSD 5.0 as a desktop 'failure' report Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; name="" Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG OK, I know this dates me, but I started with 'twm' as a window manager in 1983 when X was on V10 --on a prototype DEC GTX box with a 20" 24bit color monitor. Didn't have a lot of graphics other than what I wrote using Athena widgets. First, I still use 'twm' with a dual line 16 wide icon bar using 40 pixels across the bottom of the screen. I don't need pictures, the words are just fine and I don't have icons all over the screen. A picture is not worth a thousand words. Second, I have been continuously tracking -CURRENT since before it cut to 3.0-CURRENT --on my desktop. Sure, there have been a couple anxious moments, but I only needed the fixit disk once in all those years. My server also runs -CURRENT. Third, I run at least two full X sessions depending on how many projects I'm playing with at a time and swap whenever on a 1600 x 1280 screen. Lots of Xemacs, Netscape and some GIMP and SOffice --the only thing which crashes is Netscape and that's almost invariably due to crap code from WinSleaze ASP generators. Use the KISS principle; if you need it to look like Windows, run Windows and put up with their viri and crashes. Anything Microsoft has been banned here since before there even was a Microsoft product. Hard-nosed? Not really, just committed. My five kids learned on BSD. Even government "retrainables" can be converted if KISS is followed (been there, done that). -- I don't need your attitude. I have one of my own. ---------- Original Message ---------- Sent: Sun, 15 Sep 2002 08:09:52 -0500 by leimy2k@mac.com + On Saturday, September 14, 2002, at 07:40 PM, Andrew P. Lentvorski + wrote: + + > On Sat, 14 Sep 2002, Matthew Jacob wrote: + > + >> But we need a window manager- let's build gnome2! That worked- but, + >> haha, gnome2 refused to run because it failed to be able to do NFS + >> locking on my NFS mounted (on a Solaris 8 server) home directory. Oh, + >> well that's really not going to cut it now, is it.... Oh, well, let's + >> live with plain sawfish until we sort this one out... + > + > Please report this to the Gnome folks. Given the state of NFS + > filelocking + > on *any* open source system (they are all broken in various ways-this + > includes Linux and *BSD), requiring fully working NFS file locking on a + > widespread windowing system is not a good idea. + > + + Yes, the only successful NFS file locking I have ever seen on linux is + on NFS v3 + and it must be mounted with the "noac" [no attribute caching] option. + + I am sure that option degrades performance pretty badly. + + Give it a shot... see if it works + + + > In addition, I would bet that they'll probably point you to some + > command-line flag which disables that file locking. + > + > -a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message