From owner-freebsd-current@freebsd.org Mon Aug 24 19:49:39 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7F3BB3CB0F8 for ; Mon, 24 Aug 2020 19:49:39 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Bb2l568cmz49G8 for ; Mon, 24 Aug 2020 19:49:37 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x733.google.com with SMTP id g26so8709208qka.3 for ; Mon, 24 Aug 2020 12:49:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=OdJRsEZUuj0vf/iJPsQ7KwKZgJ6J2xxrfYiSmXKyG14=; b=Spu1C5EAxg/g952wD/b3KPipvSAZnY48sYVCE8/ztGoZeBqv3JpTF4IrSDqdJwYr4H JMeEw1CMgx+d5qPA7P/sHW1E8oXcfAlplKCDMGGyr4rQc99mXlvutqWVOPsqq68tY7Pv VjzwVh3KR4yaaSKynAcNCTNpMdhLu5YJvliO3NdxGpwHDL1gGOV6zwIBZROZOciAqOg+ 4779MNZUQ13/NDAcVsjru2A9qbVk0E5OlxGYTzNSDy9HWxDPNawfk78ePa5WosH+DDMz GJOAkeQXlfZ2Dxsm3Rwyde5l597SzZugOjyh/bngY37K6OiC2lqpLdCmCrPx7203xG8K KXQQ== X-Gm-Message-State: AOAM5306x6GcqIF+eWulhk6bD40QTSipQcch7hRM/EURfjWOe7zsQAwl 00rhT/8LlGXr7k4MLhOk0gFnNgjz0sZ3O67jxDGXoAShsgqm5g== X-Google-Smtp-Source: ABdhPJx99lccAToM7flNbnYi6270t3X8nVeICsStg40AQoHp5Rbg6zroastAh1ZrMr7ayAGTS61K5nZQQAeGG+Jj4tA= X-Received: by 2002:ae9:e315:: with SMTP id v21mr6597108qkf.215.1598298576456; Mon, 24 Aug 2020 12:49:36 -0700 (PDT) MIME-Version: 1.0 From: Warner Losh Date: Mon, 24 Aug 2020 13:49:25 -0600 Message-ID: Subject: HEADS UP: coming changes to a devd event To: FreeBSD Current , FreeBSD-STABLE Mailing List X-Rspamd-Queue-Id: 4Bb2l568cmz49G8 X-Spamd-Bar: / X-Spamd-Result: default: False [-0.29 / 15.00]; ARC_NA(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-0.59)[-0.594]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.30)[0.305]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::733:from]; R_SPF_NA(0.00)[no SPF record]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 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: Mon, 24 Aug 2020 19:49:39 -0000 Greetings I just pushed https://svnweb.freebsd.org/changeset/base/364725 into -current. In documenting all the messages that devd can receive from the kernel, I noticed an inconsistency I'd like to correct. We currently have both system=kernel and system=kern generated by the kernel. This makes no sense, imho. I've decided to transition the 'kern' one to 'kernel' because (a) I think it's less used and (b) I like it less than 'kernel' for this. The one message is generated by newus on resume. It's redundant since we also generate one for ACPI. We don't really document either (until recently), but use the ACPI one in the default devd.conf script. I'm not changing that at all since it doesn't need adjustment. This is a heads up that the other one is changing from system=kern to system=kernel to be more consistent with the other messages generated by the kernel. I've updated the documentation and added an UPDATING entry. For a while, we'll generate both system=kern and system=kernel events for this. Sometime after 13 is branched, I'll remove the system=kern one. If all goes well, I'll MFC the change to generate both to stable/12 in a few days, along with the improved docs to devd.conf (which I may do prior to that), but won't MFC the removal. I don't think this will cause anybody any grief, and the lead times on making changes will be at least 6 months for people following -current, and likely on the scale of years for people following stable branches. Sadly, it's not simple to add a deprecation notice for current users. Just thought I'd give a heads up in case this will cause people grief. Warner