Re: SEUL: SEUL duplicating efforts?

[jfm2@club-internet.fr]

> X-Authentication-Warning: belegost.mit.edu: majordomo set sender to owner-seul-project@seul.org using -f
> X-Priority: 3 (Normal)
> Content-Type: text/plain; charset=iso-8859-1
> X-URL: http://thunder.prohosting.com/~oehansen/
> Date: Tue, 17 Feb 1998 00:59:46 +0100 (CET)
> Reply-To: oe.hansen@isholf.is
> Organization: Private Home
> From: "Orn E. Hansen" <oe.hansen@oehansen.pp.se>
> Cc: seul-project@seul.org, seul-dev-ui@seul.org,
>         "Orn E. Hansen" <oe.hansen@isholf.is>
> Sender: owner-seul-project@seul.org
> To-Get-Off-This-List: mail majordomo@seul.org, body unsubscribe seul-project
> X-UIDL: 3dc8758948af460cc04dca385543ba79
> 
> 
> Þann 16-Feb-98 skrifar George Bonser:
> > 
> > So a /dev/BIOS "device driver" is needed? 
> > 
>   That's not a bad idea, except it would also be a possible security flaw
> though?  I mean, the code incide the BIOS doesn't obey Unix rules, so I
> wouldn't be surprised if the kernel forbids it?  You know if anyone has
> codes such access to BIOS information?
> 

Read /proc/kcore.  About executing Dos calls see the VM86 mode in the
386 family.  And about hacking the kernel just go to Linux-kernel and
see Linus reaction.  :-)

-- 
			Jean Francois Martinez

"For drinking muddy water if that is the water of truth,
            for that the camel is needed"