From owner-freebsd-hackers  Tue Mar 21 05:20:28 1995
Return-Path: hackers-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA19860 for hackers-outgoing; Tue, 21 Mar 1995 05:20:28 -0800
Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA19850 for <hackers@freebsd.org>; Tue, 21 Mar 1995 05:20:08 -0800
Received: from caramba.cs.tu-berlin.de (caramba.cs.tu-berlin.de [130.149.18.7]) by mail.cs.tu-berlin.de (8.6.10/8.6.10) with ESMTP id OAA25741 for <hackers@freebsd.org>; Tue, 21 Mar 1995 14:19:18 +0100
From: Wolfram Schneider <wosch@cs.tu-berlin.de>
Received: (wosch@localhost) by caramba.cs.tu-berlin.de (8.6.10/8.6.9) id OAA19769; Tue, 21 Mar 1995 14:19:01 +0100
Date: Tue, 21 Mar 1995 14:19:01 +0100
Message-Id: <199503211319.OAA19769@caramba.cs.tu-berlin.de>
To: hackers@FreeBSD.org
Subject: biosboot code size
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: hackers-owner@FreeBSD.org
Precedence: bulk


I changed the biosboot sources to emulate simple ls and more/cat
(read help files, list /dev etc.) at boot prompt. It works fine for
FreeBSD-2.0.

Unfortunately, in FreeBSD-current grow the code and boot hangs. 
I delete the usage printf to reduce the code. Is there any other way
to avoid this strange size limit?

Wolfram