From: firewind <firewind AT metroid DOT dyn DOT ml DOT org>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Int-Hooking, DOS vs LINUX
Date: 1 Oct 1997 05:31:27 GMT
Organization: Netcom
Lines: 16
Message-ID: <60sn7f$7fo@dfw-ixnews6.ix.netcom.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> <EHCs14 DOT EDL AT nonexistent DOT com>
NNTP-Posting-Host: elp-tx2-10.ix.netcom.com
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Followups-To: comp.os.linux.misc
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

[Followups set to comp.os.linux.misc]

Arthur Bredrick <sammy AT blast DOT net> wrote:
> 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?

In a word? Yes. There is absolutely no advantage to be gained by hooking it
yourself, and indeed, much to be lost. Other programs on the console wouldn't
get input, and keys special to Linux (ALT+Fxx, Shift+ScrLock, Ctrl+Scrlock,
Alt+SysRq, etc) wouldn't get recognized.

-- 
[- 				 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-."          -]