From nobody Tue Dec 14 17:27:01 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id DFA9118EE18E; Tue, 14 Dec 2021 17:27:03 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JD50R5Pmjz3rsC; Tue, 14 Dec 2021 17:27:03 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from [10.0.1.4] (ralph.baldwin.cx [66.234.199.215]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: jhb) by smtp.freebsd.org (Postfix) with ESMTPSA id 09D07499B; Tue, 14 Dec 2021 17:27:02 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Message-ID: Date: Tue, 14 Dec 2021 09:27:01 -0800 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:91.0) Gecko/20100101 Thunderbird/91.4.0 Subject: Re: smr inp breaks some jail use cases and panics with i915kms don't switch to the console anymore Content-Language: en-US To: Alexey Dokuchaev , Emmanuel Vadot Cc: Gleb Smirnoff , "freebsd-current@freebsd.org" , x11@freebsd.org References: <1db0942e-0e66-4337-ce2f-4e1005107435@FreeBSD.org> <20211213183222.f945b2e730f7c22dbe74681c@bidouilliste.com> <20211214091427.c531cf51b0284d8a1165b9bb@bidouilliste.com> From: John Baldwin In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1639502823; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Wa7BL5h5lY9r6VZ6qe0hRxPt8usUQvW5HgxQ2QMkEFM=; b=bcBqYZetbdLiFunkSJ4KVz8mUpzSod2QWcZSJ3ZpYk/4TQ+uZ0f1ny7uDbfRo32qffLR8Q T5kzLWifwj9BxFAEUco5Ar91qewt7t9ebQRThi4Paucoj5b7ts25YKiEmRuxPnquD1fQ9B POQrQH4xangO0+Ow+VbJ/1skivBoo+rnDWpuX95QpGEdVu1yhloP5rCfxPXbqiRtQTW5KS LbekqERYqLZ/D1WDhG7jb4uKiEogmSLloSn4sKmqgzJYbBkfy2aG5KRtkd5aSKePpUqjM0 j61OLMEdJCX+RxOWpaq+/PNrYSIA2qPHLN+S7GjJ8TKX3kVrA1M2IigVVFwRzw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1639502823; a=rsa-sha256; cv=none; b=R19Gsyc83Zc7pYTZh/fL2KkxeEwrMrMVI98biCrjTBDXGmHUspzxbIGbbUaCFRHjlhK3cB nCr19+qoXAwXM1tNTrifqw4vohmASkSmLXg8f/2+H4dp/b8XN/cJ6tr5lw/OymfZCUsZ25 JXguqUMD1JYiZHeqLkoLp8B6BQtaYW4mADFGZxTHX44AJVAFFYgf1GTNhWB0FKsU0jPf8A Soxdh8r8d+cd/hM9PbWToUAA7DAFvWlk+KygdKa33Hm3JlmVNJk2t/GRp1wABtL7ksBLVm dOeSBKxyErPlVRzJkkGJ0zgjV74J6V2ndGMMP4x7axCRU6rUzWYVj5dcT6dr0Q== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On 12/14/21 2:14 AM, Alexey Dokuchaev wrote: > How do you mean? Most FreeBSD people, not some random Twitter crowd, want > the bell to be on by default, but it's still off. I don't know that that's true, and I myself am not sure that I want it back on by default. Previously my laptop had a rather annoying beep whose volume I couldn't control that I actually prefer to have off normally. On further reflection, the beep I was looking for for bad input may actually be an xscreensaver thing for an invalid character to unlock the screen vs a sysbeep anyway. -- John Baldwin