From owner-freebsd-questions@FreeBSD.ORG Fri Mar 25 14:21:39 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B105416A4CE for ; Fri, 25 Mar 2005 14:21:39 +0000 (GMT) Received: from clunix.cl.msu.edu (clunix.cl.msu.edu [35.9.2.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16ED143D31 for ; Fri, 25 Mar 2005 14:21:39 +0000 (GMT) (envelope-from jerrymc@clunix.cl.msu.edu) Received: (from jerrymc@localhost) by clunix.cl.msu.edu (8.11.7p1+Sun/8.11.7) id j2PELIE01076; Fri, 25 Mar 2005 09:21:18 -0500 (EST) From: Jerry McAllister Message-Id: <200503251421.j2PELIE01076@clunix.cl.msu.edu> To: kline@tao.thought.org (Gary Kline) Date: Fri, 25 Mar 2005 09:21:18 -0500 (EST) In-Reply-To: <20050325054452.GA27349@thought.org> from "Gary Kline" at Mar 24, 2005 09:44:52 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: FreeBSD Mailing List Subject: Re: update on the dual-boot and newfs hassles X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 14:21:39 -0000 > > People, > > I'm almost done with the installation on my test platform. > The reason newfs was erroring was a WRITE err; I finally > booted single-user and fsck's /usr, then tried the > CD sysinstall for the Nth time N >=1, <= 70 :-| > Everything worked; from there is was a matter of getting > files in /etc set. > > For sure, the past few days have been a learning experience. > Understanding how to partition the 4 slices is a major win. > > I have one question. Now when I boot I see > > F1: ??? > F2 FreeBSD > > Can anybody tell me what to add to /boot (??) so the loader > prints "DOS" instead of "???" If the sysinstall scripts > recognize NTFS, what's wrong with the loader? If you are using the standard FreeBSD MBR, nothing, unless you want to hack the code yourself. It is written to fit in a minimum of space and no one has taken the time to figure out how to cram recognition of NTFS and a label string in to the block. Some other third party MBRs use up more space - which almost all of the time nowdays you can get away with - and identify more things and even allow you to configure how you want them to be described in your menu. But, I believe they are still considered not 100% compatible, or more likely, backward compatible. So, the standard FreeBSD MBR is designed to work with even old clunkers. Now, if you are feeling bored and need something to do, you might extend the standard MBR and then ammend sysinstall to offer that additional alternative and submit those changes. Some people would probably love you for it - and you would learn more than you ever wanted to know about boot code and sector 0 formats, etc. ////jerry > > thanks for the help, > > gary > > -- > Gary Kline kline@thought.org www.thought.org Public service Unix > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >