From owner-freebsd-questions  Mon Aug 14 10:36:01 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id KAA04623
          for questions-outgoing; Mon, 14 Aug 1995 10:36:01 -0700
Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id KAA04608
          for <questions@freebsd.org>; Mon, 14 Aug 1995 10:35:57 -0700
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA05934; Mon, 14 Aug 1995 11:37:54 -0600
Date: Mon, 14 Aug 1995 11:37:54 -0600
Message-Id: <199508141737.LAA05934@rocky.sri.MT.net>
To: "Jeff Wilson" <wilson@VNET.IBM.COM>
Cc: questions@freebsd.org
Subject: Re: FreeBSD on Thinkpad 360CE
In-Reply-To: <9508141649.AA24906@belgium.fishkill.ibm.com>
References: <199508141551.JAA05559@rocky.sri.MT.net>
	<9508141649.AA24906@belgium.fishkill.ibm.com>
Reply-To: nate@sneezy.sri.com (Nate Williams)
From: nate@sneezy.sri.com (Nate Williams)
Sender: questions-owner@freebsd.org
Precedence: bulk


> But I already have that kernel on the boot floppy you gave me.  The
> installation program runs fine, but once I boot from the hard disk, it
> doesn't work.  I thought the kernel gets copied from the boot floppy
> to the hard disk.  So, I should have the right kernel, but it still
> doesn't work.

But the kernel copied to the hard-disk is *NOT* the same as the kernel
on the floppy.  The kernel on the floppy using a memory file-system,
while the one copied to the hard-disk is a GENERIC kernel.  If you need,
I can make you a non-MFS kernel available which you'll need to hand-copy
onto your hard-drive.  This might be a bit difficult with the current
tools though, unless you know what you are doing.


> If I go into the config utility (booting with -c) from the hard disk, I have
> no problems in there, but once I go to the login prompt, it doesn't work.  I
> THINK this means that the kernel is fine, but some configuration file that is
> read on startup is changing the keymap.  Unfortunatly, I have no way of
> changing it (except MAYBE by modififing sysinstall, but I'm not sure exactly
> how I would have to do that.)

We could build a modified root.flp, but it would require a complete
re-install.


Nate