From owner-freebsd-questions Thu Aug 24 10:54:38 2000 Delivered-To: freebsd-questions@freebsd.org Received: from rknebel.uplink.net (rknebel.uplink.net [209.173.88.243]) by hub.freebsd.org (Postfix) with ESMTP id 4CA4237B422 for ; Thu, 24 Aug 2000 10:54:35 -0700 (PDT) Received: from [192.168.1.2] (mac.uplink.net [192.168.1.2]) by rknebel.uplink.net (8.9.3/8.9.3) with ESMTP id NAA04036; Thu, 24 Aug 2000 13:57:29 -0400 (EDT) (envelope-from rknebel@uplink.net) Mime-Version: 1.0 X-Sender: rknebel@rknebel.uplink.net Message-Id: In-Reply-To: <39A55BC6.E418A174@mitre.org> References: <39A55BC6.E418A174@mitre.org> Date: Thu, 24 Aug 2000 13:47:10 -0400 To: "Andresen,Jason R." From: Rick Knebel Subject: Re: windowmanagers Cc: questions@freebsd.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Rick Knebel wrote: >> >> Hi, >> >> I intially installed windowmaker as my default windowmanager on install. >> I was haveing problems with users getting there backround and >>themes working. >> It worked fine in root but not for users. >> >> I used sysinstall to installl kde which again works great for root >> but I had to edit the .xinitrc files manually in the users >> directories and then kde di not come up. >> i keep getting these error messages that say /dev/null permission denied. > >This last line throws up big red flags for me. Check the permissions on >/dev/null, they should be evil (666): >crw-rw-rw- 1 root wheel 2, 2 Aug 24 02:08 null > >-- > _ _ _ ___ ____ ___ ______________________________________ > / \/ \ | ||_ _|| _ \|___| | Jason Andresen -- jandrese@mitre.org > / /\/\ \ | | | | | |/ /|_|_ | Views expressed may not reflect those >/_/ \_\|_| |_| |_|\_\|___| | of the Mitre Corporation. Thanks, I changed the permissions on this dev and now my windowmakers and netscape works. Rick -- Rick Knebel rknebel@uplink.net http://rknebel.uplink.net/~rknebel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message