From owner-cvs-all Wed May 26 9:54:44 1999 Delivered-To: cvs-all@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id CE4751563F; Wed, 26 May 1999 09:54:33 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup3-29.iptelecom.net.ua [212.42.69.220]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id TAA28458; Wed, 26 May 1999 19:55:11 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.3) with ESMTP id TAA53368; Wed, 26 May 1999 19:53:12 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <374C26F8.DFF5590E@altavista.net> Date: Wed, 26 May 1999 19:53:12 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: ru,uk,en MIME-Version: 1.0 To: Robert Nordier Cc: Andrey Zakhvatov , bde@zeta.org.au, brian@Awfulhak.org, cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/boot/biosboot table.c References: <199905261625.SAA21419@ceia.nordier.com> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk Robert Nordier wrote: > > > > > Anyone else with reasons to keep the /sys/i386/boot/* (except netboot) > > > > > code around any longer? > > > > _ Have we method to load kernel from DOS partition? > > > > _ I mean ability to have pseudo-diskless workstations with biosboot > > > > and kernel image on local disk for users that must have ability to > > > > work on FreeBSD-based X terminals, for example. > > > > > > Yes, /boot/loader autors claims that loader also can load kernel out of > > > FAT/FAT32 partition, so you can make diskette with /boot/loader and write > > > corresponding loader.rc script to load kernel out of a DOS partition. > > > >   Ok, but it can't helps me to save some diskettes :( > >   And I prefer using DOS utility like biosboot.exe, which can be running > > from user menu. It's strange to use additional diskette (with very short > > life time). > > You're thinking of dosboot (fbsdboot.exe): biosboot is just the > old boot1 and boot2. > > The issue with dosboot is that it hasn't changed in four years, > and it can't be built with the FreeBSD toolchain; so there's no > real real reason for keeping it in the source tree. > > Like other DOS programs useful for FreeBSD (fdimage.exe or fips.exe, > for instance), fbsdboot.exe can always be made available in the > >     pub/FreeBSD/tools > > on ftp.freebsd.org (and mirror sites, CD-ROMs, etc). > > So deleting it from the source tree won't make matters any worse > ... and may even improve them, since it allows some DOS programmer > without commit priviledges to actually maintain it. Unfortunately (as it was pointed in the -current list several days ago) now fbsdboot.exe can't be totally "fixed" due to fact, that FreeBSD VESA and VM86 code relies heavily on BIOS interrupts table but modern versions of DOS (7 and above) trend to overwrite this table so it is impossible to freebsd's loader to restore original BIOS vectors. If you don't mind to use VESA and VM86 you can download modified fbsdboot.exe on  ftp://ftp.genericwindows.com:21/pub/FBSDBOOT.EXE. Also possible solution for you is to get NT boot loader which can load any bootblocks (including DOS and FreeBSD) right out from any file on FAT or NTFS partition (proven - I'm using such scheme, but it may be illegal). Maybe Linux's LILO can help you too, but I just don't know exactly. Finally, you can make a small (100-200KB) FreeBSD partition with /boot/loader and appropriate script and install FreeBSD BootEasy to switch modes between DOS and FBSD. Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message