From owner-freebsd-questions Fri May 5 16:47:15 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA16948 for questions-outgoing; Fri, 5 May 1995 16:47:15 -0700 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA16942 for ; Fri, 5 May 1995 16:47:10 -0700 Received: (from nate@localhost) by trout.sri.MT.net (8.6.11/8.6.11) id RAA20230; Fri, 5 May 1995 17:51:11 -0600 Date: Fri, 5 May 1995 17:51:11 -0600 From: Nate Williams Message-Id: <199505052351.RAA20230@trout.sri.MT.net> In-Reply-To: kelly@fsl.noaa.gov (Sean Kelly) "Re: turning off ctrlaltdel" (May 5, 7:42pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: kelly@fsl.noaa.gov (Sean Kelly) Subject: Re: turning off ctrlaltdel Cc: markh@stack.urc.tue.nl, questions@FreeBSD.org Sender: questions-owner@FreeBSD.org Precedence: bulk > Easiest, but not necessarily the cleanest. I might want to install > FreeBSD systems in a public user area (yes, this debate again) and > allow users to modify the keymap to their liking, via ~/.login, for > instance. I'd want to disable assigning `boot' to any of the > keys, though. > > Nate> or else modify the kernel to ignore that keystroke. > > Not the keystroke, just the action that goes with it. Of course, > modifying the kernel to do this still doesn't ring true. Kernel > config sounds nicer, though. They are *way* too many configuration options as it is. If you *really* want to make sure nothing happens, modify init to ignore the signal and no matter what it will get ignored. If you want to make it clean AND configurable, make init read a file to determine if it's supposed to ignore the signal. Nate