*BSD News Article 29709


Return to BSD News archive

Xref: sserve comp.os.386bsd.misc:2370 comp.os.linux.misc:13345
Newsgroups: comp.os.386bsd.misc,comp.os.linux.misc
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!MathWorks.Com!europa.eng.gtefsd.com!emory!swrinde!elroy.jpl.nasa.gov!decwrl!netcomsv!netcom.com!hasty
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: Impressions: FreeBSD vs Linux
Message-ID: <hastyCouGst.KwG@netcom.com>
Organization: Netcom Online Communications Services (408-241-9760 login: guest)
References: <2p72cm$278@eve.adam.com.au> <2p6jqn$9b2@acme.gatech.edu> <2pfjmi$3j9@u.cc.utah.edu>
Date: Tue, 26 Apr 1994 02:12:29 GMT
Lines: 18

In article <2pfjmi$3j9@u.cc.utah.edu> terry@cs.weber.edu (Terry Lambert) writes:
>In article <2p6jqn$9b2@acme.gatech.edu> gt8134b@prism.gatech.edu (Robert Sanders) writes:
>]steve@adam.com.au (Stephen White) writes:
>]
>
>Actually, a better plan is a protected mode vm86() call so anything
>anyone wants to write in kernel space could make a BIOS call if it
>needed one.

Care to elaborate on this one so we may implement it :)

	Tnks,
	Amancio
-- 
FREE unix, gcc, tcp/ip, X, open-look, netaudio,  tcl/tk, MIME, midi,sound
at  freebsd.cdrom.com:/pub/FreeBSD
Amancio Hasty,  Consultant |
Home: (415) 495-3046       |  
e-mail hasty@netcom.com	   |  ftp-site depository of all my work:    
ahasty@cisco.com           |  sunvis.rtpnc.epa.gov:/pub/386bsd/X