From owner-freebsd-questions Sun Sep 3 11:37:23 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id LAA25621 for questions-outgoing; Sun, 3 Sep 1995 11:37:23 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.FreeBSD.org (8.6.11/8.6.6) with SMTP id LAA25615 for ; Sun, 3 Sep 1995 11:37:21 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA16298; Sun, 3 Sep 1995 14:36:43 -0400 Date: Sun, 3 Sep 1995 14:36:43 -0400 From: "Garrett A. Wollman" Message-Id: <9509031836.AA16298@halloran-eldar.lcs.mit.edu> To: scott@statsci.com Cc: questions@freebsd.org Subject: Re: problems with initial FreeBSD (2.0.5 CD) installation attempts In-Reply-To: References: Sender: questions-owner@freebsd.org Precedence: bulk < said: > 2) Upon booting, I get this message right after the Boot: prompt and > "text=0x..." message: > BIOS basemem (637K) != RTC basemem (640K) This means that your BIOS reserves some of the high memory for its own use. FreeBSD tells you this because on some machines, one of the two values really is significantly wrong. It probably doesn't matter a whole lot. > 5) Is there a way to make a simple boot floppy from the sysinstall process? > There were a couple of times when I really wanted to boot (to an MFS root?) > to do some simple repairs on the disk. So, how DOES one go about doing > that? Or do I have to do a Minimal install from sysinstall, then switch > over to the holographic shell in VT4 to do anything? I think I've seen that > suggested as the "fixit floppy" alternative (I think I've probably missed > some messages on that subject recently). The Makefile that generates the install floppy is also capable of generating a fixit floppy. This really ought to be distributed if it isn't already. (Check the `floppies' directory of wherever you got your FreeBSD install floppy from.) > 6) I notice that when booting with something like 'fbsdboot -D ...\kernel', > the path to the kernel file makes it into the boot process > somewhere wollman@khavrinen(26)$ sysctl -n kern.bootfile /kernel > I was wondering if I could (or should) do something > similar for putting a symlink like this: > /kernel -> /c/freebsd/kernels/mykernel.001 No. The boot loader cannot handle symbolic links or multiple directories. However, you can easily change the name that the kernel thinks it was loaded under; read sysctl(8) for the full syntax. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant