From owner-freebsd-current Mon Feb 21 7:46: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from distortion.dk (distortion.dk [195.249.147.156]) by hub.freebsd.org (Postfix) with ESMTP id 055E637BA8C for ; Mon, 21 Feb 2000 07:46:02 -0800 (PST) (envelope-from morten@seeberg.dk) Received: from sos (fwuser@fw.merkantildata.dk [194.239.79.3]) by distortion.dk (8.9.3/8.9.1) with SMTP id QAA32145 for ; Mon, 21 Feb 2000 16:55:35 +0100 (CET) (envelope-from morten@seeberg.dk) Message-ID: <00e201bf7c82$fc123e70$16280c0a@sos> From: "Morten Seeberg" To: Subject: Things to consider in CURRENT Date: Mon, 21 Feb 2000 16:47:40 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just installed: FreeBSD fw.home 4.0-20000208-CURRENT and have a few comments: It seems that BASH in 4.x needs Combat 3.x, but why cant BASH work this out for it self? One day when installing BSD without X (which automatically installs Combat 3.x) I couldnt start it without. Shouldnt config pick up errors when making a new kernel? If I fx forget to remove an SCSI controller, but removes all SCSI peripheral lines, then the make fails, which is naturally, but shouldnt config catch that error? The same thing happens if you mark out device miibus, and compiles one of the cards that need it into the kernel. These things might be logically to some, but new users just might fall into this trap. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /\/\orten $eeberg, Systems Consultant @ Merkantildata - Enterprise Solutions #echo 'System Administrators suck :)' > /dev/console To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message