Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:225 comp.os.linux:35811 Newsgroups: comp.os.386bsd.misc,comp.os.linux Path: sserve!newshost.anu.edu.au!munnari.oz.au!hp9000.csc.cuhk.hk!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!menudo.uh.edu!uuneo!sugar!peter From: peter@NeoSoft.com (Peter da Silva) Subject: Re: Linux/386bsd on a diskless workstation Organization: NeoSoft Communications Services -- (713) 684-5900 Date: Sat, 24 Apr 1993 12:11:08 GMT Message-ID: <C5zLuL.KBC@sugar.neosoft.com> References: <C5sACr.Jp2@sleeper.apana.org.au> <1993Apr22.214040.27674@fcom.cc.utah.edu> Lines: 16 In article <1993Apr22.214040.27674@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes: > location that doesn't interfere with the operation of the download. This > is the first good argument I have heard for a DOS boot-loader for 386BSD > or Linux... No, it's not. It's not a new argument: it's the same argument that the folks who want a DOS bootloader have been using all along. You sometimes need to do stuff in DOS to deal with proprietary hardware or systems before you get into a real O/S. Whether that's loading over a network or setting up some weird video card, it's the same basic problem: you can't leverage off DOS drivers any other way. -- Peter da Silva. <peter@sugar.neosoft.com>. `-_-' Har du kramat din varg idag? 'U` My Apple-II has more RAM than my Mac!