From owner-freebsd-current@FreeBSD.ORG Wed Feb 4 21:57:11 2015 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BC0C6F7C for ; Wed, 4 Feb 2015 21:57:11 +0000 (UTC) Received: from mail-wi0-f176.google.com (mail-wi0-f176.google.com [209.85.212.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 560D4C70 for ; Wed, 4 Feb 2015 21:57:10 +0000 (UTC) Received: by mail-wi0-f176.google.com with SMTP id bs8so35073160wib.3 for ; Wed, 04 Feb 2015 13:57:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:subject:from:to:date:organization :content-type:mime-version:content-transfer-encoding; bh=mVUDFkg4viyDo0WS0m25KgDCXzBBBFo3QVZUrrZmbcA=; b=HMvZULxaUVkn9Z9yDUm+ms2zoBQmmTgSjfmgKaYLNPuDdpKcf9uzU34O5cwQcB+bYU Li0gyu2S01uzv6usV26rFSInwUWJPpfRN/HhIl6kAi0AWt7DjzQXTj+Jfr7yKaiuBOpX /P+Z4bhbuZC17WMSmulr3RR4mJgPhayLG+YVAjpiIBeiK6ELps5NOYKSPTzyGPPf0mw7 BysSn5uq6ZnwRIU0yCpddPS0y/W/1+d5hLYHENKBQVNHOKERZTzqqAvFIqSj9OaeP1tL 4/eMCZPZ65HIS9RMYE0gkpQRKefJ7PluZD2V+QlaPi8iKq9UnKAgqs9uHAP4r2ItB8pA LPLA== X-Gm-Message-State: ALoCoQmTpLMx1KoyhaIhxQD4wdhMkBbWnxDWB3VqnYYKw8V6Q9CYurXRK+J4bt5gWNHj+XZJz2fD X-Received: by 10.195.13.168 with SMTP id ez8mr1173995wjd.30.1423087029147; Wed, 04 Feb 2015 13:57:09 -0800 (PST) Received: from xenon (105.42.broadband6.iol.cz. [88.101.42.105]) by mx.google.com with ESMTPSA id dz10sm4991206wib.17.2015.02.04.13.57.07 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Feb 2015 13:57:08 -0800 (PST) Message-ID: <1423087017.854.20.camel@stonehenge.sk> Subject: vt(4) sysctl inconsistency question From: Michal Varga To: current@freebsd.org Date: Wed, 04 Feb 2015 22:56:57 +0100 Organization: Stonehenge Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.10 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Feb 2015 21:57:11 -0000 I have a quick question regarding the vt driver which hopefully someone involved in its design could answer for me. Roughly 4 months ago, vt gained the ability to listen to a set of keyboard combinations controlling power/debug situations and the ability to control (or more precisely, turn off) their behavior via sysctls: http://svnweb.freebsd.org/base/head/sys/dev/vt/vt_core.c?r1=271380&r2=271381& Interestingly, two cases in particular (excluding SPSC which isn't implemented yet) were left out of this configuration, namely the standby and suspend modes (STBY, SUSP), making use of those keys completely non-optional. If anyone could tell me, what was the reason for not including sysctls for those two modes? m. -- Michal Varga, Stonehenge