From owner-freebsd-hackers Tue Sep 22 01:07:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14325 for freebsd-hackers-outgoing; Tue, 22 Sep 1998 01:07:01 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA14308 for ; Tue, 22 Sep 1998 01:06:55 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id DAA04160; Tue, 22 Sep 1998 03:06:21 -0500 (CDT) Message-ID: <19980922030621.43827@futuresouth.com> Date: Tue, 22 Sep 1998 03:06:21 -0500 From: "Matthew D. Fuller" To: "Brian W. Buchanan" Cc: hackers@FreeBSD.ORG Subject: Re: vty lock References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from Brian W. Buchanan on Mon, Sep 21, 1998 at 08:47:58PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Sep 21, 1998 at 08:47:58PM -0700, Brian W. Buchanan woke me up to tell me: > I want to write a vty locking program similar in function to Linux's > vlock. Anyone have (partial?) code implementing something like this, or > have any pointers as to what I'd need to modify in the kernel to > facilitate this? You mean, like lock(1)? *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message