From owner-freebsd-hackers Sat Nov 2 23:35:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA03577 for hackers-outgoing; Sat, 2 Nov 1996 23:35:09 -0800 (PST) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA03556 for ; Sat, 2 Nov 1996 23:34:51 -0800 (PST) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA14187; Sat, 2 Nov 1996 23:34:08 -0800 Date: Sat, 2 Nov 1996 23:34:08 -0800 (PST) From: "Brian N. Handy" To: Joerg Wunsch Cc: FreeBSD hackers Subject: Re: 2.2-961006-SNAP keyboard lockup In-Reply-To: <199611030035.BAA01301@uriah.heep.sax.de> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >echo "set ipending=2" | gdb -k -w /kernel /dev/mem >/dev/null 2>&1 >> >> I just tried this. This is in a script, suid root, which is then called >> from within my .fvwmrc. > >But you know that shell scripts won't work setuid? Arrghh...and you know, I remember from the *previous* life of this thread someone quickly mentioned this...I must be popping up in .procmailrc files everywhere > /dev/null... :-) >(Perl scripts will, but only by requesting #!/usr/bin/suidperl.) Mebbe I'll give this a shot. Based on the harrassment I've gotten for an suid script, and *no* reponse on the problem itself...do I safely assume this is probably still a problem? Happy trails Brian