From owner-freebsd-questions Mon Sep 6 11: 1:44 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mail.networkone.net (mail.networkone.net [209.144.112.75]) by hub.freebsd.org (Postfix) with SMTP id C127B15093 for ; Mon, 6 Sep 1999 11:01:42 -0700 (PDT) (envelope-from reader@newsguy.com) Received: (qmail 2324 invoked from network); 6 Sep 1999 18:00:15 -0000 Received: from pm3-6-4.la.networkone.net (HELO satellite.local.lan) (reader@209.144.125.68) by mail.networkone.net with SMTP; 6 Sep 1999 18:00:15 -0000 Received: (from reader@localhost) by satellite.local.lan (8.9.3/8.9.1) id LAA03186; Mon, 6 Sep 1999 11:00:10 -0700 To: freebsd-questions@freebsd.org Subject: Example desktop / permission denied From: Harry Putnam Date: 06 Sep 1999 11:00:10 -0700 Message-ID: Lines: 24 User-Agent: Gnus/5.070096 (Pterodactyl Gnus v0.96) Emacs/20.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After installing 3.2 distribution, following along in the manual to intall the example desktop as described in chapter 17. On install CD in boot/scripts there are two scripts that are supposed to install the example desktop in what ever user root tells them. Not happening for me... The scripts go thru the necessary software reporting that all is alread installed. Then comes a part where root is prompted for a user name. Given $USER then it breaks down with this message: "su: /cdrom/book/scripts/install-rcfiles: Permission denied. The script scans the passwords file for $USER name and $DIR. No problems are reported so apparently the $USER and $DIR checkout ok. Finally figured out that the scripts forget to change the files permissions so that the su 'ed user can access them. Getting past that only to find that the files needed are not where the script expects them. /usr/share/skel/exapmles/cfbsd/scripts/.xinitrc (etc) Can anyone tell what is the problem here? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message