From owner-freebsd-stable Thu Feb 22 14:53:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail4.webintl.com (nat.webintl.com [209.248.144.106]) by hub.freebsd.org (Postfix) with ESMTP id 03F1037B503 for ; Thu, 22 Feb 2001 14:53:48 -0800 (PST) (envelope-from aeverett@webintl.com) Received: from [209.248.144.126] by mail4.webintl.com with ESMTP (Eudora Internet Mail Server 1.2); Thu, 22 Feb 2001 16:53:46 -0600 X-Sender: waee@mail2.webintl.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 22 Feb 2001 16:54:25 -0600 To: freebsd-stable@freebsd.org From: "Albert Everett, Web International Inc." Subject: schg'd file that won't let go... Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm tracking 4.2-stable on a Dell 450MHz PC. I've never been able to get X to start up on this machine, getting a KDENABIO error (or something close to it - I'm typing from memory). Anyway, I tried to make/install XFree86-4 from ports last night. Now X still doesn't work and also my installworlds have started breaking. make installworld (in single user mode) breaks when trying to install a new version of /usr/lib/libscrypt.so.2 from /usr/src. I've tried deleting, moving etc but can't. This file will not even yield to chflags. Everything I try gets "operation not permitted." Same logged in as root or in single-user. Right now the only option I see to get things back on track with this server is to start over from the 4.2 cd and forget about X. Actually, while I'm irritated about it, I might as well point out that on every machine I've installed FreeBSD on, I've never had an easy time getting X to work. But I really like cvsup and the ports, so I continue with it. Any advice out there? Albert ---------------------------------------------------------------------- Albert Everett - aeverett@webinternational.net Web International, Inc. - 501/372-0393 - FAX 501/372-1599 www.webinternational.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message