From owner-freebsd-questions Sat Sep 28 07:17:32 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA15680 for questions-outgoing; Sat, 28 Sep 1996 07:17:32 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA15651 for ; Sat, 28 Sep 1996 07:17:28 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id HAA01942; Sat, 28 Sep 1996 07:18:48 -0700 (PDT) Message-Id: <199609281418.HAA01942@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: wb2oyc@cyberenet.net cc: freebsd-questions@freebsd.org In-reply-to: Your message of "Sat, 28 Sep 1996 14:26:41 BST." From: David Greenman Reply-To: dg@root.com Date: Sat, 28 Sep 1996 07:18:48 -0700 Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >thru sysinstall. The initial install (CD) failed >with the proc filesystem getting filled, and then >the remaining app's selected failed to install. This is a known bug in the installation software. It is failing to properly reap certain children processes and eventually runs out of processes (process table is full). The work around is to not select so many packages. >However, they remain "installed" as far as pkg_add >is concerned, so now that I have a working system I >still can't go back and install them. How do I get >out of this catch-22? rm -rf /var/db/pkg/* Will get rid of everything in the package database. You'll have to selectively go through /var/db/pkg if you want to prune more specifically. The only thing you'll lose by deleting all of them is the ability to uninstall the specific package later. > Plus, can someone explain why >nearly half of the packages in /All are not really >there? Is this a problem for me because my CD is an >ATAPI? Whether I try it thru sysinstall or pkg_add >about half of them fail! Actually it's about 1/3rd of them. The reason for this has to do with the way that the package list was generated (based on the "ports" collection). Not all "ports" were supplied on the CDROM, however, due to export or redistribution restrictions and other problems. > Another annoying problem >for me is how do I get bash as my login shell? I've >put /usr/local/bin/bash as my shell in /etc/passwd, >but it still doesn't come up that way when I login! FreeBSD uses shadow passwords. You must not edit /etc/passwd directly. Use "vipw" to edit the password file. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project