Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!uwm.edu!cs.utexas.edu!asuvax!ncar!csn!yuma!barnesdo From: barnesdo@CS.ColoState.EDU (douglas barnes) Subject: Some questions about 386BSD Sender: news@yuma.ACNS.ColoState.EDU (News Account) Message-ID: <Oct16.224608.51840@yuma.ACNS.ColoState.EDU> Date: Fri, 16 Oct 1992 22:46:08 GMT Nntp-Posting-Host: beethoven.cs.colostate.edu Organization: Colorado State University, Computer Science Department Lines: 35 I have been following the discussions on this newsgroup very closely but I remain somewhat confused on a couple of topics because conflicting posts were made and no clear victor emerged (or I missed the article where one was declared). Here goes: 1) Various posts have been made to the effect that using more than 16MB to run 386BSD is a *bad thing*. I also remember similar problems with earlier versions of Interactive. In both cases the difficulty was attributed to the limited address space for devices (say SCSI controllers) to DMA into. Is this a real problem for 386BSD? Is anyone successfully running with >16MB of memory? 2) Several approaches have been outlined for causing DOS and 386BSD to coexist. Some apparently do not work for IDE drives. Could someone mail me or repost the canonical method for installing multiple OSs on a *SCSI* drive? Also, I appreciate the ongoing efforts to discern exactly what the deal is with IDE, as the next available platform available to me has IDE drives. 3) That handy little program "os-bs" does not permit booting from other hard drives. Is there a fundamental reason for this, or could such a utility theoretically boot from another drive? Is there a utility that does this? Thank you for whatever help you can provide on the topic. doug -- ----------- ----------- douglas barnes Calgon can't take me away... barnesdo@CS.ColoState.EDU From the things I did today -L7