cvs.gedasymbols.org/archives/browse.cgi   search  
Mail Archives: djgpp/1997/10/01/13:01:45

Newsgroups: comp.os.msdos.djgpp
From: "Arthur Bredrick" <sammy AT blast DOT net>
Subject: Re: Int-Hooking, DOS vs LINUX
Lines: 26
Message-ID: <EHCs14.EDL@nonexistent.com>
References: <199709282203 DOT PAA14896 AT adit DOT ap DOT net> <EHCAw1 DOT EKv AT nonexistent DOT com> <60sbl0$foq AT dfw-ixnews8 DOT ix DOT netcom DOT com>
Date: Wed, 1 Oct 1997 03:23:20 GMT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

I don't know much about Unix, but I suppose then that the kernel does a
better job of hooking the keyboard interrupt in the first place, so it is
unnecessary to write your own handler?

Art

firewind wrote in article <60sbl0$foq AT dfw-ixnews8 DOT ix DOT netcom DOT com>...

>Arthur Bredrick <sammy AT blast DOT net> wrote:
>>  Why would it be good to forbid hooking interrupts when it is obviously
>> useful in many situations?
>
>Well, system security and stability! Personally, I'm rather thankful any
ol'
>user program can't hook my keyboard interrupt...
>
>In Linux there is simply no need to hook any interrupts from userspace. The
>kernel takes care of this all for you.
>
>--
>[- firewind                             -]
>[-   email: firewind AT metroid DOT dyn DOT ml DOT org (home), firewind AT aurdev DOT com
work)  -]
>[-     "You're just jealous because the voices talk to -me-."          -]


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019