From owner-freebsd-current@freebsd.org Mon May 27 14:05:07 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2820C15975A8 for ; Mon, 27 May 2019 14:05:07 +0000 (UTC) (envelope-from voidanix@420blaze.it) Received: from cock.li (mx1.cock.li [185.10.68.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B8F176E518 for ; Mon, 27 May 2019 14:05:05 +0000 (UTC) (envelope-from voidanix@420blaze.it) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on cock.li X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=BAYES_20,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,NO_RECEIVED,NO_RELAYS shortcircuit=_SCTYPE_ autolearn=disabled version=3.4.2 MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=420blaze.it; s=mail; t=1558965321; bh=5PMNdjjtSquhyMLhDVT88a8IBTFAHdzN0uznVR/WvVs=; h=Date:From:To:Subject:From; b=Lw33e+LV8wbo4aLnQKtvh9Jv0LxY9QF3rTOAdXgyRKtqEsQnJlyawpR2ayz5tFZxZ RRvAKLGt65SLq2IOy3q8IrKlK/LM7GyR0nFhTbf3fxUgED722ouH1gkMDpXenWZ5YG o1iFT+pg1/hq8EZbsDtYRL2ub9wlJMFrUB1cdH4S8+uYdanGCiD5MErt39F2Vt6OBH +0LQx3qxKmyJvwft2Hm07/unZGQeI+zDp7lUSQJg9T59eUYxEXl5w+3TMYZJuRuKSv C+/FSYlUDyuYhyTK1b624tVBKwPwKddJV2NXgCGPaiPHpprySl0ZeYI3jwHrpTsE3s DxieKRTYKhuJw== Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 27 May 2019 15:55:21 +0200 From: voidanix@420blaze.it To: freebsd-current@freebsd.org Subject: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option Message-ID: X-Sender: voidanix@420blaze.it User-Agent: Roundcube Webmail/1.3.6 X-Rspamd-Queue-Id: B8F176E518 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=420blaze.it header.s=mail header.b=Lw33e+LV; spf=pass (mx1.freebsd.org: domain of voidanix@420blaze.it designates 185.10.68.5 as permitted sender) smtp.mailfrom=voidanix@420blaze.it X-Spamd-Result: default: False [-4.10 / 15.00]; R_SPF_ALLOW(-0.20)[+mx]; TO_DN_NONE(0.00)[]; MX_GOOD(-0.01)[cached: mx1.cock.li]; DKIM_TRACE(0.00)[420blaze.it:+]; NEURAL_HAM_SHORT(-0.87)[-0.868,0]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-0.72)[asn: 200651(-3.52), country: SC(-0.09)]; ASN(0.00)[asn:200651, ipnet:185.10.68.0/24, country:SC]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[420blaze.it:s=mail]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[420blaze.it]; RCPT_COUNT_ONE(0.00)[1]; FROM_NO_DN(0.00)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 27 May 2019 14:05:07 -0000 Hello, I wanted to discuss about bug 231768 a bit: it is about keeping COMPAT_FREEBSD4/5/6/7/9 on by default in the kernel configs. The patch attached for the bug is for disabling these options by default, following a few reasons which I'm going to list here: - Keeping support for deprecated libraries isn't exactly the best we could do to avoid security issues (if there are any) as I'm sure nobody wants to spend that much time maintaining such stuff (it's enough to think about misc/compat4x in the ports tree: that version of FreeBSD was released on March 2000 and keeping 19 years old libraries around isn't ideal) - Devs should get track of time and realize that developing software using unsupported libraries is NOT something that you should do - Only a tiny fraction of the ports need COMPAT_FREEBSD9 or older: if the software won't compile without the legacy components (and has a replacement of some kind), considering removal wouldn't be a bad idea - This is on by default: most users don't care or don't use binaries that old I don't see any practical reason to keep these options on by default, but I do appreciate any sort of input regarding this issue. - voidanix From owner-freebsd-current@freebsd.org Mon May 27 14:46:13 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 119291598999; Mon, 27 May 2019 14:46:13 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id 2BDBD6FEBC; Mon, 27 May 2019 14:46:10 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Mon, 27 May 2019 16:46:03 +0200 Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 127.0.0.10 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=127.0.0.10; helo=connect.ultra-secure.de; envelope-from= Received: from connect.ultra-secure.de (webmail [127.0.0.10]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id FE9800B2-D7D5-4E05-BC6B-629B6799BC0F.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=AES256-SHA verify=NO); Mon, 27 May 2019 16:46:00 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 27 May 2019 16:46:00 +0200 From: rainer@ultra-secure.de To: voidanix@420blaze.it Cc: freebsd-current@freebsd.org, owner-freebsd-current@freebsd.org Subject: Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option In-Reply-To: References: Message-ID: X-Sender: rainer@ultra-secure.de User-Agent: Roundcube Webmail/1.2.0 X-Haraka-GeoIP: --, , NaNkm X-Haraka-GeoIP-Received: X-Haraka-p0f: os="undefined undefined" link_type="undefined" distance=undefined total_conn=undefined shared_ip=Y X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED, BAYES_00, SPF_NONE, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 941, bad: 0, connections: 947, history: 941, pass:all_good, relaying X-Rspamd-Queue-Id: 2BDBD6FEBC X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [0.56 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.69)[-0.690,0]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_SPAM_SHORT(0.26)[0.258,0]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[ultra-secure.de]; AUTH_NA(1.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[connect.ultra-secure.de]; NEURAL_SPAM_LONG(0.15)[0.152,0]; FROM_NO_DN(0.00)[]; R_SPF_NA(0.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:88.198.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.15)[ipnet: 88.198.0.0/16(1.00), asn: 24940(-1.75), country: DE(-0.00)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 27 May 2019 14:46:13 -0000 Am 2019-05-27 15:55, schrieb voidanix@420blaze.it: > Hello, > I wanted to discuss about bug 231768 a bit: it is about keeping > COMPAT_FREEBSD4/5/6/7/9 on by default in the kernel configs. > > The patch attached for the bug is for disabling these options by > default, following a few reasons which I'm going to list here: > - Keeping support for deprecated libraries isn't exactly the best > we could do to avoid security issues (if there are any) as I'm sure > nobody wants to spend that much time maintaining such stuff (it's > enough to think about misc/compat4x in the ports tree: that version of > FreeBSD was released on March 2000 and keeping 19 years old libraries > around isn't ideal) > - Devs should get track of time and realize that developing > software using unsupported libraries is NOT something that you should > do > - Only a tiny fraction of the ports need COMPAT_FREEBSD9 or older: > if the software won't compile without the legacy components (and has a > replacement of some kind), considering removal wouldn't be a bad idea > - This is on by default: most users don't care or don't use > binaries that old > > I don't see any practical reason to keep these options on by default, > but I do appreciate any sort of input regarding this issue. I have a 32bit FreeBSD 6 binary that I'll need for a bit until the department who is technically responsible for the service gets around redoing that service. From owner-freebsd-current@freebsd.org Mon May 27 15:06:05 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 836B2159F282; Mon, 27 May 2019 15:06:05 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it1-f176.google.com (mail-it1-f176.google.com [209.85.166.176]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 744D270943; Mon, 27 May 2019 15:06:03 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it1-f176.google.com with SMTP id m140so24474636itg.2; Mon, 27 May 2019 08:06:03 -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:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=qV6ALZXQdgK0W7+14VxMovFhMAcg0sXhhVKCF7mZ0+s=; b=K+FYaXJbLbniTgskV6gW54dQURsZGHk+hiX/2HG4uvBUOs5EkmkDBGDLJSIf3ypemV ZY2KA8EhTgWGjDC7L9zBAdzdUe/IwiHlmWd3BQZK5ZPylYEH9lOfZMvALKw6fQs7qZnv 3D6Xh3ZCw+6bJUn0vNpwxAdklukC0TqaG6btNbUbI2YVWupd+Pf067PqEeK+ma3umtpr EHZVSqVk/1gCdne1PQIAOtPMy3FGabc+dz+Toxg4XFS7yPwOiqMhmtlOD3zqTBjufNeP vMPfEAnBpNExZeD3BcOW+cqPl+GaDyPI0RGC8YB1KKD1bxWQD7g99199HfaqdDH/DUpo f+IA== X-Gm-Message-State: APjAAAXXI5T4+UIP5Exy8ys76VE8kXyyTUrSudtGq+/GgzpzJ8Z9/LmX sNSM+LY6MeKEWVMHIPiGRGMbADV+ X-Google-Smtp-Source: APXvYqyr+H12cOkTYf+OFFC39lPM0e9j+7jDfOI2v5dBP6im9U4GVaQL7wWe1bmIjHx22Dxm1QA5Dg== X-Received: by 2002:a24:7949:: with SMTP id z70mr31275480itc.36.1558969557093; Mon, 27 May 2019 08:05:57 -0700 (PDT) Received: from mail-it1-f177.google.com (mail-it1-f177.google.com. [209.85.166.177]) by smtp.gmail.com with ESMTPSA id c185sm5002101itc.17.2019.05.27.08.05.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 May 2019 08:05:56 -0700 (PDT) Received: by mail-it1-f177.google.com with SMTP id a186so17415188itg.0; Mon, 27 May 2019 08:05:56 -0700 (PDT) X-Received: by 2002:a02:ce52:: with SMTP id y18mr1484954jar.78.1558969556274; Mon, 27 May 2019 08:05:56 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Reply-To: cem@freebsd.org From: Conrad Meyer Date: Mon, 27 May 2019 08:05:45 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option To: Rainer Duffner Cc: voidanix@420blaze.it, freebsd-current , owner-freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 744D270943 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of csecem@gmail.com designates 209.85.166.176 as permitted sender) smtp.mailfrom=csecem@gmail.com X-Spamd-Result: default: False [-5.28 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[cem@freebsd.org]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; MX_GOOD(-0.01)[alt3.gmail-smtp-in.l.google.com,alt4.gmail-smtp-in.l.google.com,gmail-smtp-in.l.google.com,alt2.gmail-smtp-in.l.google.com,alt1.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.96)[-0.959,0]; FORGED_SENDER(0.30)[cem@freebsd.org,csecem@gmail.com]; IP_SCORE(-2.31)[ip: (-5.83), ipnet: 209.85.128.0/17(-3.40), asn: 15169(-2.29), country: US(-0.06)]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; TAGGED_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_NEQ_ENVFROM(0.00)[cem@freebsd.org,csecem@gmail.com]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[176.166.85.209.list.dnswl.org : 127.0.5.0]; RCVD_TLS_LAST(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 27 May 2019 15:06:05 -0000 Hi Rainier, On Mon, May 27, 2019 at 7:47 AM wrote: > I have a 32bit FreeBSD 6 binary that I'll need for a bit until the > department who is technically responsible for the service gets around > redoing that service. Even if this proposal is approved, it would only affect 13+. You could still run your FreeBSD 6 binary in a 32-bit 12 VM in a 13+ Bhyve. But do consider lighting a fire under whatever department thinks it's ok to deploy like that :-). Take care, Conrad From owner-freebsd-current@freebsd.org Mon May 27 15:13:49 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 33055159F7FB for ; Mon, 27 May 2019 15:13:49 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 74FE970EE5 for ; Mon, 27 May 2019 15:13:48 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id x4RFDdZo014495 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 27 May 2019 18:13:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua x4RFDdZo014495 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id x4RFDcg5014494; Mon, 27 May 2019 18:13:38 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 27 May 2019 18:13:38 +0300 From: Konstantin Belousov To: voidanix@420blaze.it Cc: freebsd-current@freebsd.org Subject: Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option Message-ID: <20190527151338.GB2748@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.4 (2019-03-13) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 27 May 2019 15:13:49 -0000 On Mon, May 27, 2019 at 03:55:21PM +0200, voidanix@420blaze.it wrote: > Hello, > I wanted to discuss about bug 231768 a bit: it is about keeping > COMPAT_FREEBSD4/5/6/7/9 on by default in the kernel configs. What problem are you trying to solve ? > > The patch attached for the bug is for disabling these options by > default, following a few reasons which I'm going to list here: > - Keeping support for deprecated libraries isn't exactly the best we > could do to avoid security issues (if there are any) as I'm sure nobody > wants to spend that much time maintaining such stuff (it's enough to > think about misc/compat4x in the ports tree: that version of FreeBSD was > released on March 2000 and keeping 19 years old libraries around isn't > ideal) > - Devs should get track of time and realize that developing software > using unsupported libraries is NOT something that you should do This is nonsense. These options are not for developing new software. > - Only a tiny fraction of the ports need COMPAT_FREEBSD9 or older: > if the software won't compile without the legacy components (and has a > replacement of some kind), considering removal wouldn't be a bad idea And that options are usually not about ports. > - This is on by default: most users don't care or don't use binaries > that old This is I am really interesting about. How do you know ? The method you came to this conclusion should allow us to solve many other old issues, I hope. > > I don't see any practical reason to keep these options on by default, > but I do appreciate any sort of input regarding this issue. From owner-freebsd-current@freebsd.org Mon May 27 15:13:58 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BFDD9159F813; Mon, 27 May 2019 15:13:57 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id 4AEBE70EF8; Mon, 27 May 2019 15:13:57 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:3210:b3ff:fe77:ca3f] (unknown [IPv6:2001:470:1f11:617:3210:b3ff:fe77:ca3f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 61C5611BE; Mon, 27 May 2019 15:13:50 +0000 (UTC) To: FreeBSD Current , "freebsd-hackers@freebsd.org" From: Eric McCorkle Subject: FreeBSD and Coreboot Openpgp: preference=signencrypt Autocrypt: addr=eric@metricspace.net; prefer-encrypt=mutual; keydata= mDMEXMXabRYJKwYBBAHaRw8BAQdAJ2yzSUUR7u7H/bLAFOzhPII7vvJ45zQeB60TxyCoio20 JEVyaWMgTWNDb3JrbGUgPGVyaWNAbWV0cmljc3BhY2UubmV0PoiWBBMWCAA+FiEEG/v8wt9b D9+AxsV/6Y4m2LfgVbIFAlzF2m0CGwMFCQHhM4AFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA CgkQ6Y4m2LfgVbJ9mwD/YpSeQ5F9gpvKFS5Bs5w1Bw7zTOfO7zJQrh9NzDbWtd0BAOSGr/i5 zJer2pAjwambsyU0bhgHNy9IDQ7AGnidIyMHuDgEXMXabRIKKwYBBAGXVQEFAQEHQEBwYuBK iJPJEDtS6hbLgcDSUSbfUNA2rGp3TJ1G+7EqAwEIB4h+BBgWCAAmFiEEG/v8wt9bD9+AxsV/ 6Y4m2LfgVbIFAlzF2m0CGwwFCQHhM4AACgkQ6Y4m2LfgVbJ2kwEAlJj1z3zRJm3mmi6N81by nuwAxk3qcKa67WX2/F3C4soA/iwVuPMnx5RWaoX3i2eKXVNzNwzvTFfeGKxfQBOzMocM Message-ID: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> Date: Mon, 27 May 2019 11:13:46 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3TIj6TfZlOozBpG1IFXlam5oyFEhyFrxE" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 27 May 2019 15:13:58 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3TIj6TfZlOozBpG1IFXlam5oyFEhyFrxE Content-Type: multipart/mixed; boundary="6htyX95lFWE5crKa5A6cQDnuT8DXDN3WK"; protected-headers="v1" From: Eric McCorkle To: FreeBSD Current , "freebsd-hackers@freebsd.org" Message-ID: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> Subject: FreeBSD and Coreboot --6htyX95lFWE5crKa5A6cQDnuT8DXDN3WK Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Hello everyone, I'm through enough of my job change that I can start working on FreeBSD again. One thing I've had on my list to examine is using FreeBSD with coreboot, so I wanted to put out a call for anyone who has done work on this, or knows anything about it. Here is what I know: * Coreboot _can_ boot kernels directly, but this requires two things: 1) you must flash your BIOS every time you update a kernel, 2) the kernel must be able to work without the usual device initialization that the BIOS does. * Coreboot has two significant payload options beyond a kernel: Seabios and GRUB (supposedly Tianocore EFI is an option, but it apparently doesn't really work). * Scrounging the coreboot wiki seems to produce some conflicting information. One page claims that the FreeBSD kernel can boot directly as a coreboot payload; another claims GRUB or Seabios to be the only options. * The PC Engines boards evidently use coreboot, and I've heard multiple reports of them running FreeBSD systems without a problem. I don't know whether they use GRUB or Seabios. (Aside: I'm thinking about ordering some of these boards for my own use, so I'm generally interested in how well they function with FreeBSD) My plan is roughly this: * Refurbish the GRUB port, get it working again in QEMU (possibly on one of my machines), also possibly push a patch to GRUB to use the keybufs mechanism to pass in GELI keys. * Get coreboot with GRUB/Seabios booting FreeBSD in QEMU * Possibly create a coreboot port (uncertain how this would work, since Coreboot has its own extensive config menu) * Hold my breath and test it out on real hardware (I have a Librem 13 r1 for this purpose) * Possibly try getting the FreeBSD kernel to work as a coreboot payload. Here's what I don't know/what would be useful knowledge for me: * Anyone else who's been experimenting/working on coreboot support, and what they found * Any working examples of using Coreboot with FreeBSD * Down the road, anything about adapting the FreeBSD kernel to work with a new boot platform (ie. low level details about how to set it up in memory on a bare-metal system and start execution) --6htyX95lFWE5crKa5A6cQDnuT8DXDN3WK-- --3TIj6TfZlOozBpG1IFXlam5oyFEhyFrxE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQQb+/zC31sP34DGxX/pjibYt+BVsgUCXOv+rQAKCRDpjibYt+BV skEKAQCUHfKPzTGFHmB6FQqdpmeMwEwelIuKtVa8/evNB0m6tAD/aj1/ZhwbUo6Y BlaR2LtGUbXwigNgDqr0KoufJQkkWQg= =A08d -----END PGP SIGNATURE----- --3TIj6TfZlOozBpG1IFXlam5oyFEhyFrxE-- From owner-freebsd-current@freebsd.org Mon May 27 15:18:58 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5A3B4159FC5D for ; Mon, 27 May 2019 15:18:58 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-vs1-xe41.google.com (mail-vs1-xe41.google.com [IPv6:2607:f8b0:4864:20::e41]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 ECFE671299 for ; Mon, 27 May 2019 15:18:57 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-vs1-xe41.google.com with SMTP id x8so10753968vsx.13 for ; Mon, 27 May 2019 08:18:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=vKK7tgehwjOFBLNF6c1a2oDiro+bV+eGUcpTyZwq+Fo=; b=R1ZREN6hmNhXc1/xZ7QeBAIdQcXN8PJkDzfcQ6+i0C5hdbPaYSRXjC74aRQzi46tao O293P13DnmcPhLeXuLyYMI0jBUhz8kNN58T7cHkCPZVegGpkllxYLMO3BFtcG919NY1+ YoixhZUn8HCnTHYKAme6Gz+symmNnTCoI2eyplPM4lfE1TOkAzkeHBARueNCfUP/KzRA L+wmqH2TO4RyFS6HAnYdMDiDGKeP82Xi4tKs/PCQmNF0jSeBdIa/2aTqkFJTu6r7Ly8I /DuqxyaWtGU/k7fXkkoHoiqy7QFlSBdk2BrxRNDC8/N8uXDVNl4KE3ufhFuS/yuZJKXF UJMg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=vKK7tgehwjOFBLNF6c1a2oDiro+bV+eGUcpTyZwq+Fo=; b=brKlBOJFOSORQBaZe1Ol968R4WCUTl60J29NN8kS0NVr3BpN9yapISN0FcKIgDrzYY QciAufHM+Zm7Hn3KWkpF1ivetrZp7E7oL1ustzAZDqaG19ZtUhpIO+lnjNa5pEyzBgQR lp0bw9vFJIxQ6SLqil28WBMVdxqx89H5GR5Lv2qDtezI2rGMPakXi3uf1UCNeAk/RZ7n oci/FbQHWHiV/6eIygrjQOLb5ZYmtTa/8k/DukaR1ucrb1VOhySW18DEEghX+kwv6V+f Kg6hvU4MeyZDuc6BU+oB04wbqOvYBlJ0lrTngjG+nZS5CRWyOjvrT6rmYFALk94D+Eph Xcsw== X-Gm-Message-State: APjAAAVIZ8tmKCnwNoh/8vW2Hs4RzQnogeYPG3G/RjD63BLGzxBkCsLp LDScLTg4gO6a7uiIXTCdnNIiyA== X-Google-Smtp-Source: APXvYqww/cdCpJHZoYqrsviq/z1CpsXYLdR6qLFQQI4pwqTfnc1uh/OgtUPMVXiiEiCvD30ioPHrvA== X-Received: by 2002:a67:db88:: with SMTP id f8mr35791378vsk.14.1558970337256; Mon, 27 May 2019 08:18:57 -0700 (PDT) Received: from mutt-hbsd ([151.196.118.239]) by smtp.gmail.com with ESMTPSA id n23sm9775238vsj.27.2019.05.27.08.18.56 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Mon, 27 May 2019 08:18:56 -0700 (PDT) Date: Mon, 27 May 2019 11:18:55 -0400 From: Shawn Webb To: Eric McCorkle Cc: FreeBSD Current , "freebsd-hackers@freebsd.org" Subject: Re: FreeBSD and Coreboot Message-ID: <20190527151855.iqbkedo7r6n5hgab@mutt-hbsd> References: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="jo3orqfnivhqnbvw" Content-Disposition: inline In-Reply-To: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> X-Operating-System: FreeBSD mutt-hbsd 13.0-CURRENT-HBSD FreeBSD 13.0-CURRENT-HBSD HARDENEDBSD-13-CURRENT amd64 X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0xFF2E67A277F8E1FA User-Agent: NeoMutt/20180716 X-Rspamd-Queue-Id: ECFE671299 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.994,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 27 May 2019 15:18:58 -0000 --jo3orqfnivhqnbvw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hey Eric, My response is inline. On Mon, May 27, 2019 at 11:13:46AM -0400, Eric McCorkle wrote: > Hello everyone, >=20 > I'm through enough of my job change that I can start working on FreeBSD > again. One thing I've had on my list to examine is using FreeBSD with > coreboot, so I wanted to put out a call for anyone who has done work on > this, or knows anything about it. >=20 > Here is what I know: >=20 > * Coreboot _can_ boot kernels directly, but this requires two things: 1) > you must flash your BIOS every time you update a kernel, 2) the kernel > must be able to work without the usual device initialization that the > BIOS does. >=20 > * Coreboot has two significant payload options beyond a kernel: Seabios > and GRUB (supposedly Tianocore EFI is an option, but it apparently > doesn't really work). >=20 > * Scrounging the coreboot wiki seems to produce some conflicting > information. One page claims that the FreeBSD kernel can boot directly > as a coreboot payload; another claims GRUB or Seabios to be the only > options. >=20 > * The PC Engines boards evidently use coreboot, and I've heard multiple > reports of them running FreeBSD systems without a problem. I don't know > whether they use GRUB or Seabios. (Aside: I'm thinking about ordering > some of these boards for my own use, so I'm generally interested in how > well they function with FreeBSD) I own several PC Engines APU boards. They definitely use Coreboot as maintained by these peeps: https://twitter.com/3mdeb_com The Coreboot for the APU boards uses Seabios. >=20 >=20 > My plan is roughly this: >=20 > * Refurbish the GRUB port, get it working again in QEMU (possibly on one > of my machines), also possibly push a patch to GRUB to use the keybufs > mechanism to pass in GELI keys. >=20 > * Get coreboot with GRUB/Seabios booting FreeBSD in QEMU >=20 > * Possibly create a coreboot port (uncertain how this would work, since > Coreboot has its own extensive config menu) >=20 > * Hold my breath and test it out on real hardware (I have a Librem 13 r1 > for this purpose) >=20 > * Possibly try getting the FreeBSD kernel to work as a coreboot payload. >=20 >=20 > Here's what I don't know/what would be useful knowledge for me: >=20 > * Anyone else who's been experimenting/working on coreboot support, and > what they found >=20 > * Any working examples of using Coreboot with FreeBSD >=20 > * Down the road, anything about adapting the FreeBSD kernel to work with > a new boot platform (ie. low level details about how to set it up in > memory on a bare-metal system and start execution) >=20 Reach out to 3mdeb (feel free to CC me, if you'd like). See what they'd like help with. There's certainly a lot more work that could be done. Thanks, --=20 Shawn Webb Cofounder / Security Engineer HardenedBSD Tor-ified Signal: +1 443-546-8752 Tor+XMPP+OTR: lattera@is.a.hacker.sx GPG Key ID: 0xFF2E67A277F8E1FA GPG Key Fingerprint: D206 BB45 15E0 9C49 0CF9 3633 C85B 0AF8 AB23 0FB2 --jo3orqfnivhqnbvw Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEA6TL67gupaZ9nzhT/y5nonf44foFAlzr/9oACgkQ/y5nonf4 4fpd6A/+Lwya5qx8dlQbXbI+4qqcT44EzRPe9llW0kmJIaktgi5cJoQcUHBpmdOQ 5ToHGHBQavTnhlj3DueIFfxiV2jru45VDPJMWcf3TYGrmair/E43a85pN2gAoCRy hjH+8QVTi6NdSu6hynXCkMwBioJb/21X8NwtYuHtdZ3KD64L7P6+k9V5BvO5ZKWS 4HrCAtep26Bi+JBfvG3v5VDFHokxmhB1VvxbH0+6EIpwOtOu13GLOPAW+sxINuHY xJZEuMVY8x9aFjAjVcFVGXMuauGW5IJ0EdDtciCTIVumksWuwYExAARMe1YgdQC/ NIMVO6hFplYFS6798pqCHx9bkeVsHoJquMAF51LKTEN+K7YgKV9OdyAc2fy4XIrz UxctKrA0ggE4wgHUtqaS+oTRqRtrZJ3XfPSyyzat7DOB6ymICnb0CQSuK0MQAY/m imA6oUHZL9OMSnNtVuB/+/u3FSEbDAPt1hfSmVRJc4H3NLS9Asfcur2nhGl38hIt dCaNlTXt3kt9kMJaD0RAbL7dpvSUY5XtuWEKyVmsvnt4LZ/9UXapHG/xYyH2b8uI GPjz+uKxQvs03N22k9H69j2o3YMOCe5f0NNc+tuoaWUmg2HmW/Vapg+q/RSHcHTe VrzlGVWNdYpTedxvewcv9dVGGOmaXl/Tr7ap07MrD5FuLy4nghM= =UF4R -----END PGP SIGNATURE----- --jo3orqfnivhqnbvw-- From owner-freebsd-current@freebsd.org Mon May 27 15:22:42 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C602315A311E for ; Mon, 27 May 2019 15:22:42 +0000 (UTC) (envelope-from karl@denninger.net) Received: from colo1.denninger.net (colo1.denninger.net [104.236.120.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6B26A718B4 for ; Mon, 27 May 2019 15:22:42 +0000 (UTC) (envelope-from karl@denninger.net) Received: from denninger.net (ip68-1-57-197.pn.at.cox.net [68.1.57.197]) by colo1.denninger.net (Postfix) with ESMTP id 3714B21109C for ; Mon, 27 May 2019 11:22:06 -0400 (EDT) Received: from [192.168.10.28] (D18.Denninger.Net [192.168.10.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by denninger.net (Postfix) with ESMTPSA id CAF9AEA32B for ; Mon, 27 May 2019 10:22:04 -0500 (CDT) Subject: Re: FreeBSD and Coreboot To: freebsd-current@freebsd.org References: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> From: Karl Denninger Openpgp: preference=signencrypt Autocrypt: addr=karl@denninger.net; prefer-encrypt=mutual; keydata= mQINBFIX1zsBEADRcJfsQUl9oFeoMfLPJ1kql+3sIaYx0MfJAUhV9LnbWxr0fsWCskM1O4cV tHm5dqPkuPM4Ztc0jLotD1i9ubWvCHOlkLGxFOL+pFbjA+XZ7VKsC/xWmhMwJ3cM8HavK2OV SzEWQ/AEYtMi04IzGSwsxh/5/5R0mPHrsIomV5SbuiI0vjLuDj7fo6146AABI1ULzge4hBYW i/SHrqUrLORmUNBs6bxek79/B0Dzk5cIktD3LOfbT9EAa5J/osVkstMBhToJgQttaMIGv8SG CzpR/HwEokE+7DP+k2mLHnLj6H3kfugOF9pJH8Za4yFmw//s9cPXV8WwtZ2SKfVzn1unpKqf wmJ1PwJoom/d4fGvQDkgkGKRa6RGC6tPmXnqnx+YX4iCOdFfbP8L9rmk2sewDDVzHDU3I3ZZ 8hFIjMYM/QXXYszRatK0LCV0QPZuF7LCf4uQVKw1/oyJInsnH7+6a3c0h21x+CmSja9QJ+y0 yzgEN/nM89d6YTakfR+1xkYgodVmMy/bS8kmXbUUZG/CyeqCqc95RUySjKT2ECrf9GhhoQkl +D8n2MsrAUSMGB4GQSN+TIq9OBTpNuvATGSRuF9wnQcs1iSry+JNCpfRTyWp83uCNApe6oHU EET4Et6KDO3AvjvBMAX0TInTRGW2SQlJMuFKpc7Dg7tHK8zzqQARAQABtCNLYXJsIERlbm5p bmdlciA8a2FybEBkZW5uaW5nZXIubmV0PokCPAQTAQIAJgUCUhfXOwIbIwUJCWYBgAYLCQgH AwIEFQIIAwQWAgMBAh4BAheAAAoJEG6/sivc5s0PLxQP/i6x/QFx9G4Cw7C+LthhLXIm7NSH AtNbz2UjySEx2qkoQQjtsK6mcpEEaky4ky6t8gz0/SifIfJmSmyAx0UhUQ0WBv1vAXwtNrQQ jJd9Bj6l4c2083WaXyHPjt2u2Na6YFowyb4SaQb83hu/Zs25vkPQYJVVE0JX409MFVPUa6E3 zFbd1OTr3T4yNUy4gNeQZfzDqDS8slbIks2sXeoJrZ6qqXVI0ionoivOlaN4T6Q0UYyXtigj dQvvhMt0aNowKFjRqrmSDRpdz+o6yg7Mp7qEZ1V6EZk8KqQTH6htpCTQ8i79ttK4LG6bstSF Re6Fwq52nbrcANrcdmtZXqjo+SGbUqJ8b1ggrxAsJ5MEhRh2peKrCgI/TjQo+ZxfnqEoR4AI 46Cyiz+/lcVvlvmf2iPifS3EEdaH3Itfwt7MxFm6mQORYs6skHDw3tOYB2/AdCW6eRVYs2hB RMAG4uwApZfZDKgRoE95PJmQjeTBiGmRPcsQZtNESe7I7EjHtCDLwtJqvD4HkDDQwpzreT6W XkyIJ7ns7zDfA1E+AQhFR6rsTFGgQZRZKsVeov3SbhYKkCnVDCvb/PKQCAGkSZM9SvYG5Yax 8CMry3AefKktf9fqBFg8pWqtVxDwJr56dhi0GHXRu3jVI995rMGo1fLUG5fSxiZ8L5sAtokh 9WFmQpyl Message-ID: <0dfb1917-b983-7633-be19-b2141b2c1dfc@denninger.net> Date: Mon, 27 May 2019 10:22:04 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms050901010901020002040008" X-Rspamd-Queue-Id: 6B26A718B4 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.992,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 27 May 2019 15:22:43 -0000 This is a cryptographically signed message in MIME format. --------------ms050901010901020002040008 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 5/27/2019 10:13, Eric McCorkle wrote: > Hello everyone, > > I'm through enough of my job change that I can start working on FreeBSD= > again. One thing I've had on my list to examine is using FreeBSD with > coreboot, so I wanted to put out a call for anyone who has done work on= > this, or knows anything about it. > > Here is what I know: > > * Coreboot _can_ boot kernels directly, but this requires two things: 1= ) > you must flash your BIOS every time you update a kernel, 2) the kernel > must be able to work without the usual device initialization that the > BIOS does. > > * Coreboot has two significant payload options beyond a kernel: Seabios= > and GRUB (supposedly Tianocore EFI is an option, but it apparently > doesn't really work). > > * Scrounging the coreboot wiki seems to produce some conflicting > information. One page claims that the FreeBSD kernel can boot directly= > as a coreboot payload; another claims GRUB or Seabios to be the only > options. > > * The PC Engines boards evidently use coreboot, and I've heard multiple= > reports of them running FreeBSD systems without a problem. I don't kno= w > whether they use GRUB or Seabios. (Aside: I'm thinking about ordering > some of these boards for my own use, so I'm generally interested in how= > well they function with FreeBSD) > PCEngines machines run just fine with FreeBSD; I use and support a bunch of them around here for various purposes, mostly as edge firewall and gateway devices. --=20 Karl Denninger karl@denninger.net /The Market Ticker/ /[S/MIME encrypted email preferred]/ --------------ms050901010901020002040008 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC DdgwggagMIIEiKADAgECAhMA5EiKghDOXrvfxYxjITXYDdhIMA0GCSqGSIb3DQEBCwUAMIGL MQswCQYDVQQGEwJVUzEQMA4GA1UECAwHRmxvcmlkYTESMBAGA1UEBwwJTmljZXZpbGxlMRkw FwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRhIFN5c3RlbXMgQ0ExITAf BgNVBAMMGEN1ZGEgU3lzdGVtcyBMTEMgMjAxNyBDQTAeFw0xNzA4MTcxNjQyMTdaFw0yNzA4 MTUxNjQyMTdaMHsxCzAJBgNVBAYTAlVTMRAwDgYDVQQIDAdGbG9yaWRhMRkwFwYDVQQKDBBD dWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRhIFN5c3RlbXMgQ0ExJTAjBgNVBAMMHEN1 ZGEgU3lzdGVtcyBMTEMgMjAxNyBJbnQgQ0EwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIK AoICAQC1aJotNUI+W4jP7xQDO8L/b4XiF4Rss9O0B+3vMH7Njk85fZ052QhZpMVlpaaO+sCI KqG3oNEbuOHzJB/NDJFnqh7ijBwhdWutdsq23Ux6TvxgakyMPpT6TRNEJzcBVQA0kpby1DVD 0EKSK/FrWWBiFmSxg7qUfmIq/mMzgE6epHktyRM3OGq3dbRdOUgfumWrqHXOrdJz06xE9NzY vc9toqZnd79FUtE/nSZVm1VS3Grq7RKV65onvX3QOW4W1ldEHwggaZxgWGNiR/D4eosAGFxn uYeWlKEC70c99Mp1giWux+7ur6hc2E+AaTGh+fGeijO5q40OGd+dNMgK8Es0nDRw81lRcl24 SWUEky9y8DArgIFlRd6d3ZYwgc1DMTWkTavx3ZpASp5TWih6yI8ACwboTvlUYeooMsPtNa9E 6UQ1nt7VEi5syjxnDltbEFoLYcXBcqhRhFETJe9CdenItAHAtOya3w5+fmC2j/xJz29og1KH YqWHlo3Kswi9G77an+zh6nWkMuHs+03DU8DaOEWzZEav3lVD4u76bKRDTbhh0bMAk4eXriGL h4MUoX3Imfcr6JoyheVrAdHDL/BixbMH1UUspeRuqQMQ5b2T6pabXP0oOB4FqldWiDgJBGRd zWLgCYG8wPGJGYgHibl5rFiI5Ix3FQncipc6SdUzOQIDAQABo4IBCjCCAQYwHQYDVR0OBBYE FF3AXsKnjdPND5+bxVECGKtc047PMIHABgNVHSMEgbgwgbWAFBu1oRhUMNEzjODolDka5k4Q EDBioYGRpIGOMIGLMQswCQYDVQQGEwJVUzEQMA4GA1UECAwHRmxvcmlkYTESMBAGA1UEBwwJ TmljZXZpbGxlMRkwFwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRhIFN5 c3RlbXMgQ0ExITAfBgNVBAMMGEN1ZGEgU3lzdGVtcyBMTEMgMjAxNyBDQYIJAKxAy1WBo2kY MBIGA1UdEwEB/wQIMAYBAf8CAQAwDgYDVR0PAQH/BAQDAgGGMA0GCSqGSIb3DQEBCwUAA4IC AQCB5686UCBVIT52jO3sz9pKuhxuC2npi8ZvoBwt/IH9piPA15/CGF1XeXUdu2qmhOjHkVLN gO7XB1G8CuluxofOIUce0aZGyB+vZ1ylHXlMeB0R82f5dz3/T7RQso55Y2Vog2Zb7PYTC5B9 oNy3ylsnNLzanYlcW3AAfzZcbxYuAdnuq0Im3EpGm8DoItUcf1pDezugKm/yKtNtY6sDyENj tExZ377cYA3IdIwqn1Mh4OAT/Rmh8au2rZAo0+bMYBy9C11Ex0hQ8zWcvPZBDn4v4RtO8g+K uQZQcJnO09LJNtw94W3d2mj4a7XrsKMnZKvm6W9BJIQ4Nmht4wXAtPQ1xA+QpxPTmsGAU0Cv HmqVC7XC3qxFhaOrD2dsvOAK6Sn3MEpH/YrfYCX7a7cz5zW3DsJQ6o3pYfnnQz+hnwLlz4MK 17NIA0WOdAF9IbtQqarf44+PEyUbKtz1r0KGeGLs+VGdd2FLA0e7yuzxJDYcaBTVwqaHhU2/ Fna/jGU7BhrKHtJbb/XlLeFJ24yvuiYKpYWQSSyZu1R/gvZjHeGb344jGBsZdCDrdxtQQcVA 6OxsMAPSUPMrlg9LWELEEYnVulQJerWxpUecGH92O06wwmPgykkz//UmmgjVSh7ErNvL0lUY UMfunYVO/O5hwhW+P4gviCXzBFeTtDZH259O7TCCBzAwggUYoAMCAQICEwCg0WvVwekjGFiO 62SckFwepz0wDQYJKoZIhvcNAQELBQAwezELMAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3Jp ZGExGTAXBgNVBAoMEEN1ZGEgU3lzdGVtcyBMTEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBD QTElMCMGA1UEAwwcQ3VkYSBTeXN0ZW1zIExMQyAyMDE3IEludCBDQTAeFw0xNzA4MTcyMTIx MjBaFw0yMjA4MTYyMTIxMjBaMFcxCzAJBgNVBAYTAlVTMRAwDgYDVQQIDAdGbG9yaWRhMRkw FwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRswGQYDVQQDDBJrYXJsQGRlbm5pbmdlci5uZXQw ggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQC+HVSyxVtJhy3Ohs+PAGRuO//Dha9A 16l5FPATr6wude9zjX5f2lrkRyU8vhCXTZW7WbvWZKpcZ8r0dtZmiK9uF58Ec6hhvfkxJzbg 96WHBw5Fumd5ahZzuCJDtCAWW8R7/KN+zwzQf1+B3MVLmbaXAFBuKzySKhKMcHbK3/wjUYTg y+3UK6v2SBrowvkUBC+jxNg3Wy12GsTXcUS/8FYIXgVVPgfZZrbJJb5HWOQpvvhILpPCD3xs YJFNKEPltXKWHT7Qtc2HNqikgNwj8oqOb+PeZGMiWapsatKm8mxuOOGOEBhAoTVTwUHlMNTg 6QUCJtuWFCK38qOCyk9Haj+86lUU8RG6FkRXWgMbNQm1mWREQhw3axgGLSntjjnznJr5vsvX SYR6c+XKLd5KQZcS6LL8FHYNjqVKHBYM+hDnrTZMqa20JLAF1YagutDiMRURU23iWS7bA9tM cXcqkclTSDtFtxahRifXRI7Epq2GSKuEXe/1Tfb5CE8QsbCpGsfSwv2tZ/SpqVG08MdRiXxN 5tmZiQWo15IyWoeKOXl/hKxA9KPuDHngXX022b1ly+5ZOZbxBAZZMod4y4b4FiRUhRI97r9l CxsP/EPHuuTIZ82BYhrhbtab8HuRo2ofne2TfAWY2BlA7ExM8XShMd9bRPZrNTokPQPUCWCg CdIATQIDAQABo4IBzzCCAcswPAYIKwYBBQUHAQEEMDAuMCwGCCsGAQUFBzABhiBodHRwOi8v b2NzcC5jdWRhc3lzdGVtcy5uZXQ6ODg4ODAJBgNVHRMEAjAAMBEGCWCGSAGG+EIBAQQEAwIF oDAOBgNVHQ8BAf8EBAMCBeAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMDMGCWCG SAGG+EIBDQQmFiRPcGVuU1NMIEdlbmVyYXRlZCBDbGllbnQgQ2VydGlmaWNhdGUwHQYDVR0O BBYEFLElmNWeVgsBPe7O8NiBzjvjYnpRMIHKBgNVHSMEgcIwgb+AFF3AXsKnjdPND5+bxVEC GKtc047PoYGRpIGOMIGLMQswCQYDVQQGEwJVUzEQMA4GA1UECAwHRmxvcmlkYTESMBAGA1UE BwwJTmljZXZpbGxlMRkwFwYDVQQKDBBDdWRhIFN5c3RlbXMgTExDMRgwFgYDVQQLDA9DdWRh IFN5c3RlbXMgQ0ExITAfBgNVBAMMGEN1ZGEgU3lzdGVtcyBMTEMgMjAxNyBDQYITAORIioIQ zl6738WMYyE12A3YSDAdBgNVHREEFjAUgRJrYXJsQGRlbm5pbmdlci5uZXQwDQYJKoZIhvcN AQELBQADggIBAJXboPFBMLMtaiUt4KEtJCXlHO/3ZzIUIw/eobWFMdhe7M4+0u3te0sr77QR dcPKR0UeHffvpth2Mb3h28WfN0FmJmLwJk+pOx4u6uO3O0E1jNXoKh8fVcL4KU79oEQyYkbu 2HwbXBU9HbldPOOZDnPLi0whi/sbFHdyd4/w/NmnPgzAsQNZ2BYT9uBNr+jZw4SsluQzXG1X lFL/qCBoi1N2mqKPIepfGYF6drbr1RnXEJJsuD+NILLooTNf7PMgHPZ4VSWQXLNeFfygoOOK FiO0qfxPKpDMA+FHa8yNjAJZAgdJX5Mm1kbqipvb+r/H1UAmrzGMbhmf1gConsT5f8KU4n3Q IM2sOpTQe7BoVKlQM/fpQi6aBzu67M1iF1WtODpa5QUPvj1etaK+R3eYBzi4DIbCIWst8MdA 1+fEeKJFvMEZQONpkCwrJ+tJEuGQmjoQZgK1HeloepF0WDcviiho5FlgtAij+iBPtwMuuLiL shAXA5afMX1hYM4l11JXntle12EQFP1r6wOUkpOdxceCcMVDEJBBCHW2ZmdEaXgAm1VU+fnQ qS/wNw/S0X3RJT1qjr5uVlp2Y0auG/eG0jy6TT0KzTJeR9tLSDXprYkN2l/Qf7/nT6Q03qyE QnnKiBXWAZXveafyU/zYa7t3PTWFQGgWoC4w6XqgPo4KV44OMYIFBzCCBQMCAQEwgZIwezEL MAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3JpZGExGTAXBgNVBAoMEEN1ZGEgU3lzdGVtcyBM TEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBDQTElMCMGA1UEAwwcQ3VkYSBTeXN0ZW1zIExM QyAyMDE3IEludCBDQQITAKDRa9XB6SMYWI7rZJyQXB6nPTANBglghkgBZQMEAgMFAKCCAkUw GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTkwNTI3MTUyMjA0 WjBPBgkqhkiG9w0BCQQxQgRAoi5NCwmQZBeerf1t0qzwYlT78W003eeT/ulni0QOvAO6z35x Ujol/Jut7SijMZkLlSamVQege7Sj6PaZfFIQkDBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFl AwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3 DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGjBgkrBgEEAYI3EAQxgZUwgZIwezEL MAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3JpZGExGTAXBgNVBAoMEEN1ZGEgU3lzdGVtcyBM TEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBDQTElMCMGA1UEAwwcQ3VkYSBTeXN0ZW1zIExM QyAyMDE3IEludCBDQQITAKDRa9XB6SMYWI7rZJyQXB6nPTCBpQYLKoZIhvcNAQkQAgsxgZWg gZIwezELMAkGA1UEBhMCVVMxEDAOBgNVBAgMB0Zsb3JpZGExGTAXBgNVBAoMEEN1ZGEgU3lz dGVtcyBMTEMxGDAWBgNVBAsMD0N1ZGEgU3lzdGVtcyBDQTElMCMGA1UEAwwcQ3VkYSBTeXN0 ZW1zIExMQyAyMDE3IEludCBDQQITAKDRa9XB6SMYWI7rZJyQXB6nPTANBgkqhkiG9w0BAQEF AASCAgCO5GM4IplveNJbf20W/wKttWsx5g3QJWldtT7s6YYU/7bGkP1IuLKwdcBUsQ6r4YX4 oOXNoCRl55TRF3wuGsOtuEZrqup46N1OXEOH0lB2mGh+NJNxf9DraEox2ht1X1mhucGbHfPU nPVtqeENXsn5fobIG32WwrytUq3xxDDZJk55AuVtxSArD+sz2oAMBPI3MOmS5jZk+osRYA6O SgU56TZdJMBQfkSl3YycmJJihLVTjH1pdhMrIGHRrxd27CoHqMFxPDG44Yo23MyjZ4k1bxTs 2+KoNnSD/GpmKiRbnB65fSLqACXY0VNWEBDp3ptH7pIYOS1b1NLJ9EVco23XaRNHhULgF88O 5EdvO1NmbcwOErZcI2KuTg2bCK1cFoNNAWLsCHQ739o8IL/IpBUifCd7zHC3QkIg3tECl7kN mvPQs/ksqCYVRtXaUjqGRTG+x4vAAz350osy7SuM2IwS2ptz1k+U7OWX/95ajQNv6zoSBOVT BZAnXI813p4eyEpZD069V42yY6ndNmNhuFGNth7NsWnGINf13dEev8pRFzu2/+WN2m02AtTS 5pVe9KjDtu/zdmp1V0TSIHnZeas8KNdciR29++Dy2+m0lU4kTkYLuUMz6akVHMA+JrNyU0Wc G8qNMim7VhRNAqP9i5QuAzAlmesjE1FdGPQNqIb7lAAAAAAAAA== --------------ms050901010901020002040008-- From owner-freebsd-current@freebsd.org Mon May 27 15:28:02 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1696B15A3423; Mon, 27 May 2019 15:28:02 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id CEEBF71AFC; Mon, 27 May 2019 15:28:00 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Mon, 27 May 2019 17:27:59 +0200 Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 127.0.0.10 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=127.0.0.10; helo=connect.ultra-secure.de; envelope-from= Received: from connect.ultra-secure.de (webmail [127.0.0.10]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id 27D6BEFC-CEC2-4411-9BBF-A0CBCB7E4741.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=AES256-SHA verify=NO); Mon, 27 May 2019 17:27:55 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 27 May 2019 17:27:54 +0200 From: rainer@ultra-secure.de To: cem@freebsd.org Cc: voidanix@420blaze.it, freebsd-current , owner-freebsd-current@freebsd.org Subject: Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option In-Reply-To: References: Message-ID: <2d16a2a9ac5c090f196674d40d0cb398@ultra-secure.de> X-Sender: rainer@ultra-secure.de User-Agent: Roundcube Webmail/1.2.0 X-Haraka-GeoIP: --, , NaNkm X-Haraka-GeoIP-Received: X-Haraka-p0f: os="undefined undefined" link_type="undefined" distance=undefined total_conn=undefined shared_ip=Y X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED, BAYES_00, SPF_NONE, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 942, bad: 0, connections: 948, history: 942, pass:all_good, relaying X-Rspamd-Queue-Id: CEEBF71AFC X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [1.21 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.67)[-0.668,0]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.72)[0.724,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[ultra-secure.de]; AUTH_NA(1.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: connect.ultra-secure.de]; NEURAL_SPAM_LONG(0.31)[0.312,0]; FROM_NO_DN(0.00)[]; R_SPF_NA(0.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:88.198.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.15)[ipnet: 88.198.0.0/16(0.99), asn: 24940(-1.75), country: DE(-0.00)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 27 May 2019 15:28:02 -0000 Am 2019-05-27 17:05, schrieb Conrad Meyer: > Hi Rainier, > > On Mon, May 27, 2019 at 7:47 AM wrote: >> I have a 32bit FreeBSD 6 binary that I'll need for a bit until the >> department who is technically responsible for the service gets around >> redoing that service. > > Even if this proposal is approved, it would only affect 13+. You > could still run your FreeBSD 6 binary in a 32-bit 12 VM in a 13+ > Bhyve. But do consider lighting a fire under whatever department > thinks it's ok to deploy like that :-). > > Take care, > Conrad I thought so, too. I don't really want to run the abandonware of a RADIUS-server any longer than necessary (as absurd as that sounds). It's also running a recursive nameserver (previously also authoritative) that is still hard-coded in CPE and computers behind firewalls. I first wanted to virtualize it (it's not a big problem) - but this way the problem is just dragged out: "But it still works, does it and we have no time". Everybody now knows that the clock is ticking, literally. Oh, I also remember George Neville-Neil talking about a - what - FreeBSD 4 binary that a certain search-engine had lost the sources for and was running on FreeBSD 7 with compat4. (We also have a client who literally begged us to leave a decade-old Solaris box running through 2019 and half of 2020 so they could continue to do their bookkeeping on a home-grown java-app that I suspect they, too have lost the sources to...). It's running jdk15 and getting that thing to run under anything semi-decent doesn't seem to have worked-out too well. So, people pray for the best and don't prepare for the worst. Other stuff I can think of: - very old Netbackup-Clients (like 5-series), though I doubt they still work on recent releases, because 7.71 (last official version and intended for FreeBSD 11) stopped working on FreeBSD12, sadly) - certain pre-compiled VMWare Tools Modules? Pre open-source-tools (I can never make up my mind if it's VMWare-open-Tools or Open-VMWare-Tools or something different) What ever people do with COMPAT4-9 - it's bordering the pathological. From owner-freebsd-current@freebsd.org Mon May 27 16:25:14 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB2EA15A4B2F; Mon, 27 May 2019 16:25:14 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 56E9A73882; Mon, 27 May 2019 16:25:14 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by home.opsec.eu with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hVIR1-000Feb-KY; Mon, 27 May 2019 18:25:15 +0200 Date: Mon, 27 May 2019 18:25:15 +0200 From: Kurt Jaeger To: Eric McCorkle Cc: FreeBSD Current , "freebsd-hackers@freebsd.org" Subject: Re: FreeBSD and Coreboot Message-ID: <20190527162515.GH72200@home.opsec.eu> References: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 27 May 2019 16:25:15 -0000 Hi! > * The PC Engines boards evidently use coreboot, and I've heard multiple > reports of them running FreeBSD systems without a problem. I have approx. 130 of the PC Engines APUs in varius versions up until the most recent, running with FreeBSD just fine. No special setup, just the generic coreboot firmware. Well, they had some issues with 12.0-REL booting from USB sticks Booting 11.2 sticks, installing and upgrading works fine. Did not test more recent firmware. This worked to reflash the BIOS to their most recent versions: Source of the BIOS: https://pcengines.github.io/ I used flashrom -w apu4_v4.9.0.5.rom --programmer internal to upgrade: Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) mapped at physical address 0x00000000ff800000. /usr/local/bin/flashrom was installed by package flashrom-1.0_1 -- pi@opsec.eu +49 171 3101372 One year to go ! From owner-freebsd-current@freebsd.org Mon May 27 17:19:48 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E063115A61A8; Mon, 27 May 2019 17:19:48 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from smh-06.1blu.de (smh-06.1blu.de [178.254.0.206]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7EFDC75C58; Mon, 27 May 2019 17:19:48 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [172.16.29.5] (helo=sh4-5.1blu.de) by smh-06.1blu.de with esmtp (Exim 4.86_2) (envelope-from ) id 1hVJHd-0000wn-VN; Mon, 27 May 2019 19:19:38 +0200 Received: from ftp51246-2575596 by sh4-5.1blu.de with local (Exim 4.86_2) (envelope-from ) id 1hVJHd-0007UO-R4; Mon, 27 May 2019 19:19:37 +0200 Date: Mon, 27 May 2019 19:19:37 +0200 From: Matthias Apitz To: Eric McCorkle Cc: FreeBSD Current , "freebsd-hackers@freebsd.org" Subject: Re: FreeBSD and Coreboot Message-ID: <20190527171937.GA27133@sh4-5.1blu.de> Reply-To: Matthias Apitz Mail-Followup-To: Eric McCorkle , FreeBSD Current , "freebsd-hackers@freebsd.org" References: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> X-Operating-System: FreeBSD 12.0-CURRENT r314251 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.5.24 (2015-08-30) X-Rspamd-Queue-Id: 7EFDC75C58 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.991,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 27 May 2019 17:19:49 -0000 El día Monday, May 27, 2019 a las 11:13:46AM -0400, Eric McCorkle escribió: > Hello everyone, > > I'm through enough of my job change that I can start working on FreeBSD > again. One thing I've had on my list to examine is using FreeBSD with > coreboot, so I wanted to put out a call for anyone who has done work on > this, or knows anything about it. Hello Eric, I don't know if this is something which has to do with your project. Since 2015 I use an Acer C720 Chromebook with FreeBSD (CURRENT) this has AFAIK coreboot with SeaBIOS and works just fine. Just to let you know. matthias -- Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub May, 9: Спаси́бо освободители! Thank you very much, Russian liberators! From owner-freebsd-current@freebsd.org Mon May 27 18:58:32 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CC2A415A821B; Mon, 27 May 2019 18:58:31 +0000 (UTC) (envelope-from lwhsu.freebsd@gmail.com) Received: from mail-yw1-f65.google.com (mail-yw1-f65.google.com [209.85.161.65]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 673D980D94; Mon, 27 May 2019 18:58:30 +0000 (UTC) (envelope-from lwhsu.freebsd@gmail.com) Received: by mail-yw1-f65.google.com with SMTP id b74so6968268ywe.5; Mon, 27 May 2019 11:58:30 -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:cc; bh=44Z4oQ47vxtC57tP9spS1c0ysU8Kk4UIoKMSG816sLY=; b=scR/ZXGwG/2IAyG/tKvBvWe3ChCiLEMDK7sbp6twfZGE5dqgWu+uBurcNLlN1mSnDc XmbglghVdsJDk7G4xoTFFU/bXLuOnABmzhhD2FoHC+2V9YJv/z1s8eU5K+k+RWpu/S7J U+5eXeM74cnc6rclbVwZ7G1pyh2JScCXanXe+68q4TO09bFG07vpjeDy++AIJR7m6vyQ MKh3M2nxcqX/93UgvH5eLFuRa+FRsVgxA1KDjd3bV51f0vqJUp6TMt0X2bg3ivN71t0B yjUFf4zhcF9tfEWJKZisCaMlDNx6HxIVB1UG6EkNQ3k5SsnFCCBB1e6GUjTNN9RedlES IOhg== X-Gm-Message-State: APjAAAVzW4wMQHMgZfsA11A7B0+4qfPZhfrLNZo1PGu5LlJj9w1Jq/X3 wysrmTuMRiCOJKoNN7PblC42fUdbHyaqpsJ8ZBaS1oeUCt0= X-Google-Smtp-Source: APXvYqzBYvF6cYTU9aOfKBcq0VktNFD5KFzBNdF3DQKb9SidmdqW8jhy5+7BqhKcFBqps7DtPq9/EACwn+UJgONCUHQ= X-Received: by 2002:a81:160c:: with SMTP id 12mr5829523yww.360.1558983504187; Mon, 27 May 2019 11:58:24 -0700 (PDT) MIME-Version: 1.0 From: Li-Wen Hsu Date: Mon, 27 May 2019 14:58:13 -0400 Message-ID: Subject: FreeBSD CI Weekly Report 2019-05-26 To: freebsd-testing@freebsd.org Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 673D980D94 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of lwhsufreebsd@gmail.com designates 209.85.161.65 as permitted sender) smtp.mailfrom=lwhsufreebsd@gmail.com X-Spamd-Result: default: False [-3.99 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_NEQ_ENVFROM(0.00)[lwhsu@freebsd.org,lwhsufreebsd@gmail.com]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_TLS_LAST(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.68)[-0.684,0]; RCVD_IN_DNSWL_NONE(0.00)[65.161.85.209.list.dnswl.org : 127.0.5.0]; IP_SCORE(-1.30)[ip: (-0.74), ipnet: 209.85.128.0/17(-3.39), asn: 15169(-2.29), country: US(-0.06)]; FORGED_SENDER(0.30)[lwhsu@freebsd.org,lwhsufreebsd@gmail.com]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; TAGGED_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 27 May 2019 18:58:32 -0000 (Please send the followup discussions to freebsd-testing@ list.) FreeBSD CI Weekly Report 2019-05-26 =================================== Here is a summary of the FreeBSD Continuous Integration results for the period from 2019-05-20 to 2019-05-26. During this period, we have: * 2273 builds (97% passed, 3% failed) were executed on aarch64, amd64, armv6, armv7, i386, mips, mips64, powerpc, powerpc64, powerpcspe, riscv64, sparc64 architectures for head, stable/12, stable/11 branches. * test runs (% passed, % unstable, % exception) were executed on amd64, i386, riscv64 architectures for head, stable/12, stable/11 branches. * 21 doc builds (100% passed) (The statistics from experimental jobs are omitted) If any of the issues found by CI are in your area of interest or expertise please investigate the PRs listed below. The latest web version of this report is available at https://hackmd.io/s/HyiX1HETN and archive is available at http://hackfoldr.org/freebsd-ci-report/, any help is welcome. ## Failing Tests * https://ci.freebsd.org/job/FreeBSD-head-amd64-test/ * sys.geom.class.eli.init_test.init * sys.geom.class.eli.init_test.init_a * sys.geom.class.eli.init_test.init_alias * sys.geom.class.eli.integrity_test.copy * sys.geom.class.eli.integrity_test.data * sys.geom.class.eli.integrity_test.hmac Those geli(8) test cases are failing because some algorithms are deprecated in r348206 and the return value and output are changed. The fix to the test cases are under development. * sys.netinet.socket_afinet.socket_afinet_bind_zero Affected by mac_portacl(4), which is loaded by MAC tests. Need to specify AF_INET to workaround and fix is being discussed. * https://ci.freebsd.org/job/FreeBSD-head-i386-test/ * i386 test is current suffering from loading ipsec(4) kernel module, which is needed after https://svnweb.freebsd.org/changeset/base/347410 , causes kernel panic. For more information, see: * https://bugs.freebsd.org/238012 * https://bugs.freebsd.org/230857 * https://reviews.freebsd.org/D17512 * Same as amd64: * sys.geom.class.eli.init_test.init * sys.geom.class.eli.init_test.init_a * sys.geom.class.eli.init_test.init_alias * sys.geom.class.eli.integrity_test.copy * sys.geom.class.eli.integrity_test.data * sys.geom.class.eli.integrity_test.hmac * sys.netinet.socket_afinet.socket_afinet_bind_zero * Others: * sys.netpfil.pf.forward.v6 * sys.netpfil.pf.forward.v4 * sys.netpfil.pf.set_tos.v4 * sys.opencrypto.runtests.main * https://ci.freebsd.org/job/FreeBSD-stable-12-i386-test/ * sys.netpfil.pf.forward.v6 * sys.netpfil.pf.forward.v4 * sys.netpfil.pf.set_tos.v4 * lib.libc.regex.exhaust_test.regcomp_too_big * lib.libregex.exhaust_test.regcomp_too_big * sys.opencrypto.runtests.main Failed with: ``` File "/usr/tests/sys/opencrypto/cryptodev.py", line 179, in __init__ ioctl(_cryptodev, CIOCGSESSION2, s, 1) IOError: [Errno 22] Invalid argument ``` * https://ci.freebsd.org/job/FreeBSD-stable-11-i386-test/ * local.kyua.* (31 cases) * local.lutok.* (3 cases) ## Failing and Flaky Tests (from experimental jobs) * https://ci.freebsd.org/job/FreeBSD-head-amd64-dtrace_test/ * There are ~980 test cases failure with message: `dtrace: failed to compile script err.D_AGG_SCALAR.maxnoarg.d: [D_UNKNOWN] "/usr/lib/dtrace/mbuf.d", line 114: failed to copy type of 'm_data': Type information is in parent and unavailable` * Flakey test case: common.misc.t_dtrace_contrib.tst_dynopt_d https://bugs.freebsd.org/237641 * https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/ * This job is currently suffering from timeout because of https://bugs.freebsd.org/237652 * There are ~60 failing cases, including flakey ones, see https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/lastCompletedBuild/testReport/ for more details ## Disabled Tests * lib.libc.sys.mmap_test.mmap_truncate_signal https://bugs.freebsd.org/211924 * sys.fs.tmpfs.mount_test.large https://bugs.freebsd.org/212862 * sys.fs.tmpfs.link_test.kqueue https://bugs.freebsd.org/213662 * sys.kqueue.libkqueue.kqueue_test.main https://bugs.freebsd.org/233586 * usr.bin.procstat.procstat_test.command_loogle.com/ine_arguments https://bugs.freebsd.org/233587 * usr.bin.procstat.procstat_test.environment https://bugs.freebsd.org/233588 ## Open Issues * https://bugs.freebsd.org/237077 possible race in build: /usr/src/sys/amd64/linux/linux_support.s:38:2: error: expected relocatable expression * https://bugs.freebsd.org/237403 Tests in sys/opencrypto should be converted to Python3 * https://bugs.freebsd.org/237641 Flakey test case: common.misc.t_dtrace_contrib.tst_dynopt_d * https://bugs.freebsd.org/237652 tests.hotspare.hotspare_test.hotspare_snapshot_001_pos timeout since somewhere in (r346814, r 346845] * https://bugs.freebsd.org/237655 Non-deterministic panic when running pf tests in interface ioctl code (NULL passed to strncmp) * https://bugs.freebsd.org/237656 "Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of memory." seen when running sys/netipsec tests * https://bugs.freebsd.org/237657 sys.kern.pdeathsig.signal_delivered_ptrace timing out periodically on i386 ### Cause build fails * [233735: Possible build race: genoffset.o /usr/src/sys/sys/types.h: error: machine/endian.h: No such file or directory](https://bugs.freebsd.org/233735) * [233769: Possible build race: ld: error: unable to find library -lgcc_s](https://bugs.freebsd.org/233769) ## Other News * bz@ committed https://svnweb.freebsd.org/changeset/base/348063 in Waterloo Hackathoon 2019, it contains basic socket tests and can be used as an example for writing tests. * https://issues.tmatesoft.com/issue/SVNKIT-740 The patch is asked to be updated and help wanted. * https://bugs.freebsd.org/235356 Help on how to reproduce and analyze is wanted. * "FreeBSD CI Tasks and Ideas", discussed in the [DevSummit201905](https://wiki.freebsd.org/DevSummit/201905/): https://hackmd.io/bWCGgdDFTTK_FG0X7J1Vmg From owner-freebsd-current@freebsd.org Mon May 27 22:01:25 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ECFC915AC577; Mon, 27 May 2019 22:01:24 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-ot1-f44.google.com (mail-ot1-f44.google.com [209.85.210.44]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 89DE5886B5; Mon, 27 May 2019 22:01:24 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by mail-ot1-f44.google.com with SMTP id t24so15910049otl.12; Mon, 27 May 2019 15:01:24 -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:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qXMSqqMbSE2mwi/e2dY2kunlogGixg4YbG4sZipczio=; b=BAkvVmhi5ZKCN+Ace3vL/JCIiS/iwSXmMBNIBDkoruWrGc5vUF6ON7PdvpV1NsrNOw 9ZrgMDpsDvG2R2q/RAsnQJqZEqJxPFxjWOJeUkQm3QN3k+p8ueQylh/Lqn7MOFVlsPam EW+rLis5eJM5Os2hFm7iOcWIRXezazKhukWCFLI8RrAjcZs+cXWO1D1MHxnEIYr3OEeL q6zl74gmXIomufEB0fDZBYSR3ilejX3mzBfLI9v9fRaF3N0lVD/FSY6Z2QfP/WJeek79 9LkW4eVJDxi6yXe5gPupD3RbbXLa9m9vlMrA8AOAuM+lTley57elejLC39PPIdmyGBZC kHig== X-Gm-Message-State: APjAAAXHVA6MYrm3OAIrDGZfCTUgteK7bcyhxqq+UVH5ysU5Hx+FJE1s K9hdtg7seh6XQyQ+4PqkPNstxPwlp94TChWZgkI= X-Google-Smtp-Source: APXvYqwg/8pzPsFcTF1ZTXhOGkhcNtJdaGFLRymLlUYYqigcdVw1lMgQW+QQjYB4KKxv+TpKHgmpKN21Cr+eie9ItS4= X-Received: by 2002:a9d:7d9a:: with SMTP id j26mr14776408otn.102.1558994034336; Mon, 27 May 2019 14:53:54 -0700 (PDT) MIME-Version: 1.0 References: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> In-Reply-To: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> From: Edward Napierala Date: Mon, 27 May 2019 22:53:42 +0100 Message-ID: Subject: Re: FreeBSD and Coreboot To: Eric McCorkle Cc: FreeBSD Current , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 89DE5886B5 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.96 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.96)[-0.963,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 27 May 2019 22:01:25 -0000 On Mon, 27 May 2019 at 16:14, Eric McCorkle wrote: [..] > My plan is roughly this: > > * Refurbish the GRUB port, get it working again in QEMU (possibly on one > of my machines), also possibly push a patch to GRUB to use the keybufs > mechanism to pass in GELI keys. > > * Get coreboot with GRUB/Seabios booting FreeBSD in QEMU > > * Possibly create a coreboot port (uncertain how this would work, since > Coreboot has its own extensive config menu) > > * Hold my breath and test it out on real hardware (I have a Librem 13 r1 > for this purpose) > > * Possibly try getting the FreeBSD kernel to work as a coreboot payload. Out of curiosity - why the kernel and not loader(8)? From owner-freebsd-current@freebsd.org Mon May 27 22:50:51 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 592E015AD6B6; Mon, 27 May 2019 22:50:51 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (static-108-31-38-18.washdc.fios.verizon.net [108.31.38.18]) by mx1.freebsd.org (Postfix) with ESMTP id 6EE468A437; Mon, 27 May 2019 22:50:50 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:3210:b3ff:fe77:ca3f] (unknown [IPv6:2001:470:1f11:617:3210:b3ff:fe77:ca3f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 2BB70128F; Mon, 27 May 2019 22:50:49 +0000 (UTC) To: Edward Napierala Cc: FreeBSD Current , "freebsd-hackers@freebsd.org" References: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> From: Eric McCorkle Openpgp: preference=signencrypt Autocrypt: addr=eric@metricspace.net; prefer-encrypt=mutual; keydata= mDMEXMXabRYJKwYBBAHaRw8BAQdAJ2yzSUUR7u7H/bLAFOzhPII7vvJ45zQeB60TxyCoio20 JEVyaWMgTWNDb3JrbGUgPGVyaWNAbWV0cmljc3BhY2UubmV0PoiWBBMWCAA+FiEEG/v8wt9b D9+AxsV/6Y4m2LfgVbIFAlzF2m0CGwMFCQHhM4AFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA CgkQ6Y4m2LfgVbJ9mwD/YpSeQ5F9gpvKFS5Bs5w1Bw7zTOfO7zJQrh9NzDbWtd0BAOSGr/i5 zJer2pAjwambsyU0bhgHNy9IDQ7AGnidIyMHuDgEXMXabRIKKwYBBAGXVQEFAQEHQEBwYuBK iJPJEDtS6hbLgcDSUSbfUNA2rGp3TJ1G+7EqAwEIB4h+BBgWCAAmFiEEG/v8wt9bD9+AxsV/ 6Y4m2LfgVbIFAlzF2m0CGwwFCQHhM4AACgkQ6Y4m2LfgVbJ2kwEAlJj1z3zRJm3mmi6N81by nuwAxk3qcKa67WX2/F3C4soA/iwVuPMnx5RWaoX3i2eKXVNzNwzvTFfeGKxfQBOzMocM Subject: Re: FreeBSD and Coreboot Message-ID: <1452db0c-1210-3230-c044-bc682e7e1745@metricspace.net> Date: Mon, 27 May 2019 18:50:45 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="9ECAOtpg9rw2jdh2m5vI63HP0iDzOZsig" X-Rspamd-Queue-Id: 6EE468A437 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-1.79 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_ATTACHMENT(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; DMARC_NA(0.00)[metricspace.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_SHORT(0.94)[0.940,0]; NEURAL_HAM_LONG(-0.87)[-0.874,0]; IP_SCORE(0.25)[asn: 701(1.29), country: US(-0.06)]; MX_GOOD(-0.01)[mail.metricspace.net]; NEURAL_HAM_MEDIUM(-0.99)[-0.992,0]; R_SPF_NA(0.00)[]; SIGNED_PGP(-2.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+]; ASN(0.00)[asn:701, ipnet:108.31.0.0/16, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 27 May 2019 22:50:51 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --9ECAOtpg9rw2jdh2m5vI63HP0iDzOZsig Content-Type: multipart/mixed; boundary="V8N54xAkborfrU9cp4VGzVm42fljY09MH"; protected-headers="v1" From: Eric McCorkle To: Edward Napierala Cc: FreeBSD Current , "freebsd-hackers@freebsd.org" Message-ID: <1452db0c-1210-3230-c044-bc682e7e1745@metricspace.net> Subject: Re: FreeBSD and Coreboot References: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> In-Reply-To: --V8N54xAkborfrU9cp4VGzVm42fljY09MH Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 5/27/19 5:53 PM, Edward Napierala wrote: > On Mon, 27 May 2019 at 16:14, Eric McCorkle wrot= e: >=20 > [..] >=20 >> My plan is roughly this: >> >> * Refurbish the GRUB port, get it working again in QEMU (possibly on o= ne >> of my machines), also possibly push a patch to GRUB to use the keybufs= >> mechanism to pass in GELI keys. >> >> * Get coreboot with GRUB/Seabios booting FreeBSD in QEMU >> >> * Possibly create a coreboot port (uncertain how this would work, sinc= e >> Coreboot has its own extensive config menu) >> >> * Hold my breath and test it out on real hardware (I have a Librem 13 = r1 >> for this purpose) >> >> * Possibly try getting the FreeBSD kernel to work as a coreboot payloa= d. >=20 > Out of curiosity - why the kernel and not loader(8)? >=20 If I understand coreboot correctly, loader would have to directly manipulate devices _without a BIOS_. That is, it would have to have an entire device detection/interface layer, which I don't believe is the case today. At least in the EFI case, loader is talking through the system's EFI implementation, which takes care of all that for you. BIOS works in a similar way. My sense is getting loader to the point where it could be a coreboot (without Seabios/GRUB/Tianocore) would be quite an undertaking= =2E --V8N54xAkborfrU9cp4VGzVm42fljY09MH-- --9ECAOtpg9rw2jdh2m5vI63HP0iDzOZsig Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQQb+/zC31sP34DGxX/pjibYt+BVsgUCXOxpxQAKCRDpjibYt+BV smxvAQC8YAcRUOedMVulJbiCdYNJzUWUBzCU6CBBxPYrn1R7VAEAgGBE64FIU0Wk WDMkEUWLlnfktDk+bFSVQWk1KtFVqQQ= =jtPc -----END PGP SIGNATURE----- --9ECAOtpg9rw2jdh2m5vI63HP0iDzOZsig-- From owner-freebsd-current@freebsd.org Tue May 28 00:47:53 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2642515AFAA4; Tue, 28 May 2019 00:47:53 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 379ED8DC67; Tue, 28 May 2019 00:47:52 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pf1-x431.google.com with SMTP id z26so10356705pfg.6; Mon, 27 May 2019 17:47:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=otT5l7yuRRQYzGTaFGNIbNrmu8j+WBc4QgLMyet8B10=; b=i1Brewa1tvkRq5pJewG4qEuz/Sr9iABrSzv4CdXe3hWR14BaZuLpVGrlpOqouQ7NRO Re/zxw82tTFuh72wY132bYYrgVLIikoUv4z10sZPwQbscvRse0fyrqwlt3KOcxnlKsIc AvsBaG3Av44zbj9FU7Y6MGhpbpPICb4ErNQhADsPPgShmu68iLpqeHsDyo76MIRAq2+n 0an713BBKo0Q4ZaEUL0j7nppDbxUShgjYPQm5hN08OEAKRzUmIHdPPw7A29vbnyIEQuk q24OpMH+fWjyqopjT+zZdpyy82sL090/cj+EmehyEaWS5n9eBOPB8jsVeFyBZDl6ORRg 59lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=otT5l7yuRRQYzGTaFGNIbNrmu8j+WBc4QgLMyet8B10=; b=G9/STIcDg4L9Sl13DR6YU1ZSxcCv9L4uXjy173MXlTVZ20xmCt2Nuw66qXTtTm4L4p nh5J/meOWUWO73+AirF0bw4fuh0l30IU11Jk/rLl/bCAXJrZ8GvsjUg2XQiiECYa8ead 7r6dgK72boFgtWbgb0Auz+FtAaV8yWKiuNUbkCsbWs6QQ8mhLHuqk0DO2vdv7kLtT8HP t+ywXcwu17w8NAULc1T5yoHCWoozSV/F5t4qsVdmSISbHhJImD1J3z/uvEVhTJPXv+8j ESQs48a4RiIuWnWeSu0ftx1IZIQ+oju4ksIohe9W11YiD+Tf1F6/KTniaYpyD7FFKwQA BtLg== X-Gm-Message-State: APjAAAXU3/LUYa5wodGfCde6oKc0vmXz4rRfKNRjhBVgjwAMYFHBAxLW Drhavw7xfZVi2De8YEwG1nd+BQnT X-Google-Smtp-Source: APXvYqzQ2dwGxINVuTu+aa4FsXNosjkjAiEhnGI1ZxLbZXKRAsd3nKNByjlw9XzJHCzwD28OMZ+IOw== X-Received: by 2002:a17:90a:9a87:: with SMTP id e7mr1914992pjp.90.1559004470704; Mon, 27 May 2019 17:47:50 -0700 (PDT) Received: from ?IPv6:2607:fb90:a694:54a3:cd89:b3e5:6af5:362b? ([2607:fb90:a694:54a3:cd89:b3e5:6af5:362b]) by smtp.gmail.com with ESMTPSA id r185sm14903764pfc.167.2019.05.27.17.47.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 May 2019 17:47:49 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option From: Enji Cooper X-Mailer: iPhone Mail (16F156) In-Reply-To: <2d16a2a9ac5c090f196674d40d0cb398@ultra-secure.de> Date: Mon, 27 May 2019 17:47:47 -0700 Cc: cem@freebsd.org, voidanix@420blaze.it, freebsd-current , owner-freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <3E7C1D63-996E-4AA0-A0A4-455B996BB9D6@gmail.com> References: <2d16a2a9ac5c090f196674d40d0cb398@ultra-secure.de> To: rainer@ultra-secure.de X-Rspamd-Queue-Id: 379ED8DC67 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=i1Brewa1; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of yaneurabeya@gmail.com designates 2607:f8b0:4864:20::431 as permitted sender) smtp.mailfrom=yaneurabeya@gmail.com X-Spamd-Result: default: False [-6.42 / 15.00]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MV_CASE(0.50)[]; RCPT_COUNT_FIVE(0.00)[5]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.94)[-0.935,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-2.97)[ip: (-9.22), ipnet: 2607:f8b0::/32(-3.29), asn: 15169(-2.28), country: US(-0.06)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[1.3.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Tue, 28 May 2019 00:47:53 -0000 > On May 27, 2019, at 08:27, rainer@ultra-secure.de wrote: >=20 > Am 2019-05-27 17:05, schrieb Conrad Meyer: >> Hi Rainier, >> On Mon, May 27, 2019 at 7:47 AM wrote: >>> I have a 32bit FreeBSD 6 binary that I'll need for a bit until the >>> department who is technically responsible for the service gets around >>> redoing that service. >> Even if this proposal is approved, it would only affect 13+. You >> could still run your FreeBSD 6 binary in a 32-bit 12 VM in a 13+ >> Bhyve. But do consider lighting a fire under whatever department >> thinks it's ok to deploy like that :-). >> Take care, >> Conrad >=20 >=20 > I thought so, too. >=20 > I don't really want to run the abandonware of a RADIUS-server any longer t= han necessary (as absurd as that sounds). >=20 > It's also running a recursive nameserver (previously also authoritative) t= hat is still hard-coded in CPE and computers behind firewalls. >=20 > I first wanted to virtualize it (it's not a big problem) - but this way th= e problem is just dragged out: "But it still works, does it and we have no t= ime". >=20 > Everybody now knows that the clock is ticking, literally. >=20 > Oh, I also remember George Neville-Neil talking about a - what - FreeBSD 4= binary that a certain search-engine had lost the sources for and was runnin= g on FreeBSD 7 with compat4. > (We also have a client who literally begged us to leave a decade-old Solar= is box running through 2019 and half of 2020 so they could continue to do th= eir bookkeeping on a home-grown java-app that I suspect they, too have lost t= he sources to...). It's running jdk15 and getting that thing to run under an= ything semi-decent doesn't seem to have worked-out too well. > So, people pray for the best and don't prepare for the worst. >=20 >=20 > Other stuff I can think of: > - very old Netbackup-Clients (like 5-series), though I doubt they still wo= rk on recent releases, because 7.71 (last official version and intended for = FreeBSD 11) stopped working on FreeBSD12, sadly) > - certain pre-compiled VMWare Tools Modules? Pre open-source-tools (I can n= ever make up my mind if it's VMWare-open-Tools or Open-VMWare-Tools or somet= hing different) >=20 >=20 > What ever people do with COMPAT4-9 - it's bordering the pathological. I=E2=80=99ll counter the OP=E2=80=99s suggestion a bit: It would be nice if the compat options were modularized and printed out an E= OS warning when loaded, so the user was aware that the modules are not suppo= rted by FreeBSD, in terms of security and whatnot. Thanks! -Enji= From owner-freebsd-current@freebsd.org Tue May 28 00:53:53 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C595215AFF9F; Tue, 28 May 2019 00:53:53 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id 133E88E24D; Tue, 28 May 2019 00:53:53 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:3210:b3ff:fe77:ca3f] (unknown [IPv6:2001:470:1f11:617:3210:b3ff:fe77:ca3f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 7A60012C0; Tue, 28 May 2019 00:53:52 +0000 (UTC) Subject: Re: FreeBSD and Coreboot To: freebsd-hackers@freebsd.org, freebsd-current References: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> From: Eric McCorkle Openpgp: preference=signencrypt Autocrypt: addr=eric@metricspace.net; prefer-encrypt=mutual; keydata= mDMEXMXabRYJKwYBBAHaRw8BAQdAJ2yzSUUR7u7H/bLAFOzhPII7vvJ45zQeB60TxyCoio20 JEVyaWMgTWNDb3JrbGUgPGVyaWNAbWV0cmljc3BhY2UubmV0PoiWBBMWCAA+FiEEG/v8wt9b D9+AxsV/6Y4m2LfgVbIFAlzF2m0CGwMFCQHhM4AFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA CgkQ6Y4m2LfgVbJ9mwD/YpSeQ5F9gpvKFS5Bs5w1Bw7zTOfO7zJQrh9NzDbWtd0BAOSGr/i5 zJer2pAjwambsyU0bhgHNy9IDQ7AGnidIyMHuDgEXMXabRIKKwYBBAGXVQEFAQEHQEBwYuBK iJPJEDtS6hbLgcDSUSbfUNA2rGp3TJ1G+7EqAwEIB4h+BBgWCAAmFiEEG/v8wt9bD9+AxsV/ 6Y4m2LfgVbIFAlzF2m0CGwwFCQHhM4AACgkQ6Y4m2LfgVbJ2kwEAlJj1z3zRJm3mmi6N81by nuwAxk3qcKa67WX2/F3C4soA/iwVuPMnx5RWaoX3i2eKXVNzNwzvTFfeGKxfQBOzMocM Message-ID: <0c236dad-391f-5bb8-11d3-92ab532323ee@metricspace.net> Date: Mon, 27 May 2019 20:53:44 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="zaA7IYSmNSVX1QCopAjLEvf3SHPyp39uU" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Tue, 28 May 2019 00:53:53 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --zaA7IYSmNSVX1QCopAjLEvf3SHPyp39uU Content-Type: multipart/mixed; boundary="7pfumWsctv7bbhOyH8GEFEgikWGFTrvQH"; protected-headers="v1" From: Eric McCorkle To: freebsd-hackers@freebsd.org, freebsd-current Message-ID: <0c236dad-391f-5bb8-11d3-92ab532323ee@metricspace.net> Subject: Re: FreeBSD and Coreboot References: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> In-Reply-To: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> --7pfumWsctv7bbhOyH8GEFEgikWGFTrvQH Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 5/27/19 11:13 AM, Eric McCorkle wrote: > My plan is roughly this: >=20 > * Refurbish the GRUB port, get it working again in QEMU (possibly on on= e > of my machines), also possibly push a patch to GRUB to use the keybufs > mechanism to pass in GELI keys. I managed to get the grub2 port compiling against 2.02 (latest release) in an afternoon's worth of work. Note: the --force-label flag on grub-install isn't presently implemented; I'll need to dig deeper into the code to get that working. I haven't tried to see if it works yet. You can follow my work on the grub2 branch of my freebsd-ports fork: https://github.com/emc2/freebsd-ports/tree/grub2 Also, I am potentially willing to take over maintenance of the port, assuming the volume of work isn't too high. --7pfumWsctv7bbhOyH8GEFEgikWGFTrvQH-- --zaA7IYSmNSVX1QCopAjLEvf3SHPyp39uU Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQQb+/zC31sP34DGxX/pjibYt+BVsgUCXOyGmAAKCRDpjibYt+BV slglAP90iSkN0gWDBEL7X9OvZSMK0YIJVLJ1KQRtlqJ+YVLaDQEAyCbyASc1KfiY Ik+B1/Poti0L5GzvE8GQ0kAAKKw9RQY= =iHgG -----END PGP SIGNATURE----- --zaA7IYSmNSVX1QCopAjLEvf3SHPyp39uU-- From owner-freebsd-current@freebsd.org Tue May 28 01:16:41 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C84315B0B49; Tue, 28 May 2019 01:16:41 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CF9938EEDC; Tue, 28 May 2019 01:16:40 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from comporellon.tachypleus.net (cpe-45-49-150-87.socal.res.rr.com [45.49.150.87]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id x4S15lUU009826 (version=TLSv1.2 cipher=AES128-SHA bits=128 verify=NOT); Mon, 27 May 2019 18:05:47 -0700 Subject: Re: FreeBSD and Coreboot To: Eric McCorkle , Edward Napierala Cc: "freebsd-hackers@freebsd.org" , FreeBSD Current References: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> <1452db0c-1210-3230-c044-bc682e7e1745@metricspace.net> From: Nathan Whitehorn Openpgp: preference=signencrypt Autocrypt: addr=nwhitehorn@freebsd.org; keydata= mQINBFuARN8BEADLKYsG3l1aq/M21R59I/5EsEfvtvd15ZJ9lDHcWPuxzIfGnu2LMpe5PrFP e/Y4bcsPrlB4S3I3ooIUDvoEEsDeqgqlZod3QevOK/RjLqiqx1i/4mKnobJ++3ppyVVIccgN sUrj786OYCFCI/W+uWw7cbKewNeaL//Z/TDKlHLkssiy6qmZbNQ0ZjcMLJKUesk4eVg2TtTD HNe42ZuxbUC9iLYieO4c7kQB4qiFhagDRiObXrLzvm2MQYeAaNVRqID+mfI75TWrQ+t98iVu mHvFu461eeteq59jg6H/IL07ACxL+HzEVM+D6tPtPrz7ppr3wiZL5Cu17yu0nAx0nhJTV8ZB qza1rOVun0x65S14L41XD2HkmBDxTaRlTg8ypnkLFo8kh+MEq4k67apL/DUGcaUjKy2TVUC7 3igLO/DwQHrkWx2RrOmS3xS0TgGXVmB47nq2Zveo3fcjporQK63n2sbLkS70cfAJAJ9KHEIx u9am44iW5Ku3+mVLgQYybtcUxlk/Jw/BA5V6KUcDQMd5kTm0MyagziqMaT+57ceYxwRBK4HC DCLRpSOHV81/YzyL5vnwfHsxADm3091rd0uwr8uRCQn7wLvlcFyp/JKSFkVnE1oo7UE4QQJZ GbSJyvj7GdXu0LdghALcMj/thdb+js4D3UuCaAMecgVSscxEIQARAQABtClOYXRoYW4gV2hp dGVob3JuIDxud2hpdGVob3JuQGZyZWVic2Qub3JnPokCTgQTAQgAOBYhBD1kIPqoIUk+gL8N YTi2TZRmhOh3BQJbgFJIAhsDBQsJCAcCBhUKCQgLAgQWAgMBAh4BAheAAAoJEDi2TZRmhOh3 M6YP/RHkgLWCPGGBSKZ3an3GhRMO2B5qd+g5QGUt4gvvdMMgUqwvmUva4obvgS5qXbYOmFGM cP5myo1mcJ45Q06Qdy8pnFEBBm4dKlNZT8LHAz/lr0/I8FINJcIdwmyxHJzELW7nlBy+ZO0z rCJ4CK//MMCAlomj6s9ydaGF0Dnbj9LmE+CS/ZZaYqil5KgsXO2rbN1wa0QOpZjAc8I1NyDN 10nWTZSLeFcbfTWItc8bxVC8NOerG25OVMxjyvqp15ZSExL5NfxIMsrTAjk5AsLr0bCW3tGA A0eM2cwLBhAfdh3fdj+/8tzakafFwR8XrA6YWrvgFmIjCgXfbVGp058595SDHGM1BeCJ94Bm TJMbCTsGPTUbRsWXJ4ytjziqMPPYkXif+NdWNLX3/TTu4oGPGsPQjbTA2xTfLLjNFKLv0ieT XTMg3vMhiOsZnfKt65fwoJWh+mfBe9S4ImNiI2C6H/gr9rpjZZQ3f85+AUAQrVjZJwaOctTC wOr8o8odS5WrpwZVEQhJj8TdOiHKPsAS8+zsjdGucfkXBHnSctMS1uv9QMTTrMvWhuihzYlw 2pC3LHEvxUpv1lk+jH42uRqbMF0FfSPkundHalWXY/HZKWdukc5lhIcGYR9bcm+Eq5/P0Qyv 3q8Q6hIjx6pN4828q8aA0lDnQ1LOtGZjToGZUrcmuQINBFuARRkBEAC9SmeRBQpprN52L+js v29No0eITfSrXTbNhqLB4ikDcnGFDih9yunAQyKk+y++unxYute4NH70qnKpvHOzHENKrSNg uDgs0ga7/4iQMs2rWqTgSQ97JfmW6ilqJXbtKyKvLvK2Jt1lJo7I2uB3Sg3pupHc0WMElIyg EHm/goNnZA401BPGmkgwl9vD4UHxn4+om3CrqpcNWFIrJ/bHKjtg/CcINz3DA7KuyKTlg+jO IgH1Xf5cmCW8e4LeQoMqkXu5y9E+4/M+o6YKiLLplSk5pc0pep/+9S+5fVW2YTDjNXVIY1KK E5IqWZ5HsjxcsfEVEVgm/auR7iVreIi2dkJVrKczMMV0KBOqqwg3eXwfaUZo1NWL6FaHruYK tHkSblUWKSR2sLfDUnrFTj8/fRTHba6fDUhoxHPVnptEjCsSvUxCEVWZN9V64XjlFCO3cF72 e75ikbGp2R1PRPWgDFmmX0pHTGPKUImqKuF4krGrY64pf8iRUTyQvbNF49i6e4ycGwlAHhSq FBZkVBwvUZeDp9DFfL2Rht/QtjYH0yfcT5zRL0aI3oX6I7luCYvm4K4HG461BvTkvxZ2xmo3 dACzmwEyAClpseEaMOsbgwosnTFhehd4Qz1Kl4Yiry8/yqISEodt6vRjs5jAsT2okDBCc6qx +dww3ymXNvEGrf+AvQARAQABiQRsBBgBCAAgFiEEPWQg+qghST6Avw1hOLZNlGaE6HcFAluA RRkCGwICQAkQOLZNlGaE6HfBdCAEGQEIAB0WIQTTpX+yMt35tfRft49NUswkCJ+wagUCW4BF GQAKCRBNUswkCJ+waqoWEACAWq6YgCh4H+JPNxM33ENOmKZ+WmIfr7jgoy1UAhUz0OshLPHM dy4oyaPefNaio5jcp8rvuT7qxA19s1VOyA6NIvCBnMzs+x9bTkQdZ31mcBcESNltKShYO3mq JE8Iz665xUlY2U45x8oGO+pYvWXvZv1C4pXtqczzQQldRuYJ+zfHyGmJoDP6exj0ALVfApH1 RKrCHt51ZottN0gcy4fkmBF+D13hUWAEtq0TBXw+2m6Qwq5xQmWkItzw4x9CF+wE78hNodY5 TXoifJvMB78O/ltPUqUiiPn6FAmi7ErDA3Ue+b4dSBWCx/i+jhh08blrbTQeMr6yswQJzx3M m6BDvYsKZKC9WNI9YKJxopd/udikmcPSoBTyWgMhjm0FPMb3c9Ay9nlbV04LlaqT7DsG8WbL X6O8CZUEpsB8r2kptm4wjjkIywT5eyXbcoNMV449KRzobWDCLOzA50cqTCPwa+YaHUamcoXs 7f3g0AllZVg3J48tq3orQrbmd80/n6AK158fURHR4pPf1m7Z8LGvmfN5vSpw81IgJ0KQEg7P mBsrOZKXGRNvtiHipWvdC9+ex1OSHRNtKTL7bbBYV01atsw74pspBLwXbH/lWnUtFucwav41 wbtHYdfbhxpXZRL0YLcrJq6+oatJlUxzAjO3wz/EuU/5OAwMGJVptO80308ID/4jEYmXl0Ux PEXv2/FjHser/OdhzQNhLft9bBlMiSGwui5Rv0tWPZ7dB7gxsuJIBzvb/FoJXbFysmm+o4Bt go0xQqXqFBX4pD9KYKTDo9q4Bh+0k+NGKvBMJI9pwFu+Ix+u1dbrFnpi/q2nFRfYEKeZiKOD HOxMMcSeYEFaHqiiy5A7QDuW7i7e4uGY0Ls7vnxrNQTWpEIe9E6kIjIHtNWAOIypL8+tiuxr CckPYFEDEmJmp1XIIoFXOIgGceky7huMvtyWHAuE1RjrZpN34nuntpoPlYv0PpPNAIg20HBA eX+reoTCRquUz5F2yZuZRL4o2/sSbDwu4m1As4G0QNaWB7j3grTn6AEVhMbjLgA+QkPpvpN8 s3iEVlEyzuypuGhRR9sMMB/8itWKtCV4/TGoAGJkoK+LsVllfIuu2m9ekV9HAOg3583ame9L NQD0nD35egjdIv7PhbZDYVgPq1NS27b8wz8RqvYWlw+1kUSD62byWu/oFLLifHfUh66ImLCk kbJJBZ5XgGKb/mVpBRiyw7zJUJZgIyTB1NcCWr09n7X+44KuocAYM/hE7NKv8To/5PFmsWFu Y8m1Qh/j7U8/gOdAT7+Q4tLczRRU/ngcW8b/1ajWMY6UuZhrp/WfLoKHS79VYK39OClHRLSU hr911kye7XJLUdGr4S2k+enQb7kCDQRbgEVBARAA4soW2Dq6zQAsDsu2+PEiyQiCoUmMfDaR r9S10njfY/2S+YGrvPi/T6b+CTEI44bTIOLYK/8AsmhuzJvnq1tToxTRJGNOKjflLaOK3fr0 HUEMLZMs0XffuxSq5THSXjCQRcQF5+8tFii4XwFFuSCO96DuwDg2OyJ25DH3a88mcGhofY5b GoNuvlfqQXlzH2M+spQnhmof+toT9JIOG2jDhoo7SdZu15UZyTXlbVf9LwrOI9cprPEJDyqm tBFMB6Gx0b9tJtYP3mGndMCURuXg3hSqpLufiMJm6cJ6KLZMNkdW/H+WkUBPZ7PHrjqnY9SY fmGmJUyBtjm4dzJqHA1/54047uCi2c1iiJ6gvDh9R5Ng6r6zcg2KwIHiKi9Bxk4JhLObBGiV BGCBfS0FJ6dHo+CnfxiNUiRa8weHFtWJ8C6yO9Vub8ZB4DYxoK2SiDncjJ+juuL0N42lW5Fz /jsHEeLwm13LIaAs7XcCNzBzpXsot4ObD9JckAyyy5ZCVfOzw6Cyk2+3KYGHmurhOXEBjrkv di//KHSLMTO04k7c5v3LeAuuntN4MjQQ71LIa4VduBZj81eUPBYdaC4yA7sNYz8rF5oxjId+ d98h5Dq6EzbXLjYjs1XXWZbDJy/9cmQgPd93sZYF5xqR1idgj/sVgwMeaxRA+ZIyRuoKphxl 7jsAEQEAAYkCNgQYAQgAIBYhBD1kIPqoIUk+gL8NYTi2TZRmhOh3BQJbgEVBAhsMAAoJEDi2 TZRmhOh3ZFsQAJtDZvAnf75u+pyUStt6R/sFdiNrfv8fEYTrurf3F/byF6fy9Ya1fCrhtaZl PkfxsGpeKADhtRTic3hffEQN9PKqRAy4NOefBPtjrUHhASqGLhqrhp1/8o/SXVQKDgInQpL3 fUdqf5VuK5Rxtp27VlffsR/qD+Eb6a3n0V5cMxTSt6uzYGmvzMHzLCiMCxUL3aS84cuwJC10 Kw/ML5HoHVtjr9F72yUzU0F37aTgFRWFi7wVvwivfs6Y3RoZDNi5FzN+uZH85Xn/X6Dld5hI Vur/RDcqQVYsd+KZ9/yVv0ZFat285SljIaW6/j1v8bmj2VLE/BfIF9qhWL9YMN8n9cnD0f3R crrxNjE98RCR64sQTOD4HPdl527KjZnHhLlqkuoBu/RHN25eAgZhlU+7xHjJrydBYd5Smi3X uW3xIvvIWQwloBeTbtCpQBrGOqcYEufvRgxZcUbJJ++OBpHUW279L8dIqofubxoVhl+2qztm iNc12oYdkpGsjHqFFRi5lAzy7EcPB4XiMX5AjBghSa2vLmHyK2JKO30oeOmQfdbPmjWaTpxs U037CCkemUOX+JkxmMWyRMAl8SxgdVJKbbXNxi++iCtupi9yIxO3Lrn7QDwbP20xtw3H149o agz72N4V6GvNON1qJOIL66ZJ39jb0MJbg4EyvVV+59VUpt8B Message-ID: <3aa00c6b-2502-ffad-c915-a833292882bd@freebsd.org> Date: Mon, 27 May 2019 18:05:45 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: <1452db0c-1210-3230-c044-bc682e7e1745@metricspace.net> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="LyIxkKby04YEpGsH5AeydSISyWGbOKjgf" X-Sonic-CAuth: UmFuZG9tSVbWyOWmqredkSUqPpij1VbraeWHougpD8h9Z6qsrQNCJ+9AdyDr/Yz5MzLx47cuU1rvT4D0x5U6GCMM4KZnYztkPRUm2Z3mOm4= X-Sonic-ID: C;+u7oueSA6RG6gccSXokrVQ== M;4EsouuSA6RG6gccSXokrVQ== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd X-Rspamd-Queue-Id: CF9938EEDC X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.981,0]; ASN(0.00)[asn:7065, ipnet:64.142.96.0/19, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Tue, 28 May 2019 01:16:41 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --LyIxkKby04YEpGsH5AeydSISyWGbOKjgf Content-Type: multipart/mixed; boundary="q6PuLJAQ2dVeKq7lQ0j4emexr8iAFIqQL"; protected-headers="v1" From: Nathan Whitehorn To: Eric McCorkle , Edward Napierala Cc: "freebsd-hackers@freebsd.org" , FreeBSD Current Message-ID: <3aa00c6b-2502-ffad-c915-a833292882bd@freebsd.org> Subject: Re: FreeBSD and Coreboot References: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> <1452db0c-1210-3230-c044-bc682e7e1745@metricspace.net> In-Reply-To: <1452db0c-1210-3230-c044-bc682e7e1745@metricspace.net> --q6PuLJAQ2dVeKq7lQ0j4emexr8iAFIqQL Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US On 2019-05-27 15:50, Eric McCorkle wrote: > On 5/27/19 5:53 PM, Edward Napierala wrote: >> On Mon, 27 May 2019 at 16:14, Eric McCorkle wro= te: >> >> [..] >> >>> My plan is roughly this: >>> >>> * Refurbish the GRUB port, get it working again in QEMU (possibly on = one >>> of my machines), also possibly push a patch to GRUB to use the keybuf= s >>> mechanism to pass in GELI keys. >>> >>> * Get coreboot with GRUB/Seabios booting FreeBSD in QEMU >>> >>> * Possibly create a coreboot port (uncertain how this would work, sin= ce >>> Coreboot has its own extensive config menu) >>> >>> * Hold my breath and test it out on real hardware (I have a Librem 13= r1 >>> for this purpose) >>> >>> * Possibly try getting the FreeBSD kernel to work as a coreboot paylo= ad. >> Out of curiosity - why the kernel and not loader(8)? >> > If I understand coreboot correctly, loader would have to directly > manipulate devices _without a BIOS_. That is, it would have to have an= > entire device detection/interface layer, which I don't believe is the > case today. > > At least in the EFI case, loader is talking through the system's EFI > implementation, which takes care of all that for you. BIOS works in a > similar way. My sense is getting loader to the point where it could be= > a coreboot (without Seabios/GRUB/Tianocore) would be quite an undertaki= ng. > On IBM PowerNV systems, which also don't provide interfaces to a second-stage loader, we just abandoned loader(8). It's way too much work.= -Nathan --q6PuLJAQ2dVeKq7lQ0j4emexr8iAFIqQL-- --LyIxkKby04YEpGsH5AeydSISyWGbOKjgf Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE06V/sjLd+bX0X7ePTVLMJAifsGoFAlzsiWoACgkQTVLMJAif sGrKyxAAnhNhQhSx91G/JcTnIdvrvcQLJCOhlX6TZhQdWOXNeB0/Eb7CjeEWns3a Cxoi4abJmHYV82oerBSnszEuj5rZFo0H8wy0PCaPYsg4UhBUI0GtrfGCxSzewbfq NAgPnYA9hENLk0YX1QjI3gASSKv10+Ab6MiLIvrwwIgaB1iAEPy3GjI+OlvhqBak 3VeQyyM8PpQOhMirhND21oGiAV5uknLJdtNQCXqlFAGZa9l1KDeviKlNm7Hnur9N Xa5xzNF8fHtPs8kmWdd2gof8hthdFESHV3E6+3l2RHeVTrJBtv8NfnwmM/xwdjbA xQDS3Qs7kvjY034KvALgIDamhNScN6Lg+51rpAyfkgwXmPpgWLk2S/Wl41rKDuNH V6AYd2ceNe7fdKwz6cMgraQOsqMAG3jO4r9Cy9bPrIGX28oPet2jee0NsJv+f5qV HP+Qc4GZNCMM7cQbLaX5qeNVtAri0Tc02jz7m3wfqejzJDCx2XAbfQYWpYU2t3qk YH0o7RgrVtxUi0tMawe1BSlCcvBYqRUEqB7wLxWRAYUDCI4HUs1DJhaRjNMfBj5C MlwhU3cNxhS+/tzl16kRPePCNJnvP7nZzz6y7ceiPBfBeAbc0pdX4SqNoD/Dm1Gv vy3A2rOUa2oT5OZjlYgR2p3cWa5FLo6/x40WnvWFz4XpyMRjp5c= =O/BF -----END PGP SIGNATURE----- --LyIxkKby04YEpGsH5AeydSISyWGbOKjgf-- From owner-freebsd-current@freebsd.org Tue May 28 02:14:43 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 371B115B256E for ; Tue, 28 May 2019 02:14:43 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x741.google.com (mail-qk1-x741.google.com [IPv6:2607:f8b0:4864:20::741]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 4BF0890D4E for ; Tue, 28 May 2019 02:14:42 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x741.google.com with SMTP id t64so20035375qkh.1 for ; Mon, 27 May 2019 19:14:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=N2rtnLbCwk7TtmdmCjx8VrdshvnAH4bHJEsr2f55FwA=; b=SqI5uRV4z8ocZGZ6ceiS7XRI6CYQir19gDC4Vq+/eZj9pcIA8EDFiS2H91VZuamDQw zyIYubokPVcwrFJl5e0FFIDUbLgvaE3EVWxQTQ55gPSuJttUHePtPu5g/sFAZe2mAvJa QGZoI5jfL6cCLU3R9+0rWU04wP8TieB7BVlcN5lU4b7yF4G9AfyV/c22BujQMltzKBIB scM0YdNbkRNezO5pE8pK5lkl5Ij842D7ttlFwIUxGA2O9XIUMxjBYOQtP0V3hbV9UN/w 3bOsdgTRYck/0wWLO/bFlrthhhvtat1V0sS74hpBmievIrSHgcnNkzVQtbm2CpnWqMOY OdtQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=N2rtnLbCwk7TtmdmCjx8VrdshvnAH4bHJEsr2f55FwA=; b=XHvdhbOWxiAuoqWofSTOcnDnQ8L9q90OSvqUilhkJ/6YQDhHh9bX4GFFPU53nrVB8L nM2lzMWLTYIeKGuOJY0GMCIhFXCnuUWBMjMj7fBRBUwqpdrVXRgdWhPlXBJXXee0rD7y fnyiA1boXwk5By163FDhhtw+W/eI0lbAhfgZXFe+fpFrjh2KyODJRfmz65eEiF7Bu6Mz U7AffTbCL/IDR5L/VDm7ihAd+vJzspT0Tmc4r6wLOqWAOCYiqpmnSH6h4wdfF+ofXS0w UGqF3at21sxsnb9wei2e2ejpNlNuW4Eco/x1Lewchffh347RKy3quHMQGqHxOKrmMjG4 4TAw== X-Gm-Message-State: APjAAAX49TR9lxvdiLyv2P8/oj1lpdsqVXwarWYnurVkQlSZlKjhErV2 /bPt1DvS4pXmcZAikfA6/YnVTdHq4gV1kUNO8szTBg== X-Google-Smtp-Source: APXvYqwAxlyEvgG/U4YCp2h6XVM4s/8L3g36g1HgFjfxSP8N0ahyLjZGmFbkdqOPBxucqrkfg0+lUiywYqn8f/O/CPQ= X-Received: by 2002:a05:620a:1384:: with SMTP id k4mr37539684qki.69.1559009681728; Mon, 27 May 2019 19:14:41 -0700 (PDT) MIME-Version: 1.0 References: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> <1452db0c-1210-3230-c044-bc682e7e1745@metricspace.net> <3aa00c6b-2502-ffad-c915-a833292882bd@freebsd.org> In-Reply-To: <3aa00c6b-2502-ffad-c915-a833292882bd@freebsd.org> From: Warner Losh Date: Mon, 27 May 2019 20:14:29 -0600 Message-ID: Subject: Re: FreeBSD and Coreboot To: Nathan Whitehorn Cc: Eric McCorkle , =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= , "freebsd-hackers@freebsd.org" , FreeBSD Current X-Rspamd-Queue-Id: 4BF0890D4E X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=SqI5uRV4 X-Spamd-Result: default: False [-3.55 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; RCPT_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; MX_GOOD(-0.01)[cached: ALT1.aspmx.l.google.com]; RCVD_IN_DNSWL_NONE(0.00)[1.4.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.80)[-0.803,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; IP_SCORE(-0.74)[ip: (1.95), ipnet: 2607:f8b0::/32(-3.29), asn: 15169(-2.28), country: US(-0.06)]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Tue, 28 May 2019 02:14:43 -0000 On Mon, May 27, 2019, 7:18 PM Nathan Whitehorn wrote: > > > On 2019-05-27 15:50, Eric McCorkle wrote: > > On 5/27/19 5:53 PM, Edward Napierala wrote: > >> On Mon, 27 May 2019 at 16:14, Eric McCorkle > wrote: > >> > >> [..] > >> > >>> My plan is roughly this: > >>> > >>> * Refurbish the GRUB port, get it working again in QEMU (possibly on > one > >>> of my machines), also possibly push a patch to GRUB to use the keybufs > >>> mechanism to pass in GELI keys. > >>> > >>> * Get coreboot with GRUB/Seabios booting FreeBSD in QEMU > >>> > >>> * Possibly create a coreboot port (uncertain how this would work, since > >>> Coreboot has its own extensive config menu) > >>> > >>> * Hold my breath and test it out on real hardware (I have a Librem 13 > r1 > >>> for this purpose) > >>> > >>> * Possibly try getting the FreeBSD kernel to work as a coreboot > payload. > >> Out of curiosity - why the kernel and not loader(8)? > >> > > If I understand coreboot correctly, loader would have to directly > > manipulate devices _without a BIOS_. That is, it would have to have an > > entire device detection/interface layer, which I don't believe is the > > case today. > > > > At least in the EFI case, loader is talking through the system's EFI > > implementation, which takes care of all that for you. BIOS works in a > > similar way. My sense is getting loader to the point where it could be > > a coreboot (without Seabios/GRUB/Tianocore) would be quite an > undertaking. > > > > On IBM PowerNV systems, which also don't provide interfaces to a > second-stage loader, we just abandoned loader(8). It's way too much work. > How do you use tunables and loadable modules? Warner > From owner-freebsd-current@freebsd.org Tue May 28 02:20:45 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9430D15B2A2D for ; Tue, 28 May 2019 02:20:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 BD4E391155 for ; Tue, 28 May 2019 02:20:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x735.google.com with SMTP id m14so1217208qka.10 for ; Mon, 27 May 2019 19:20:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ockj9Byf3T5gvRtemQ0G6GpfpIz3wwZ0L8nyTtxTOr4=; b=eiI/xkJnRlmg/ZLKcfVhWm66+FPb7RVmycS2uLHlImzRJAYvNl10FhE+pqPwKJwWlR CEBo1yyRGRbYf2dkeMo6+ZBGMzj9XR7T6gQvxgiYKwCeoyolktxrGTBsmTNOC+YUWOS+ yO9hdCJg43dGX83ifZ7VztqZJy1vDz28nxkoK3BMURgW0xWYf0fFh0lXVOYgcYBk9Ni3 UpetS83lBnp4m8f//+4JkKW0sT3k+IAhf8RNnbP6CeZ6PGcZrXAyRwF+SSVRXx0Yty5G 7+CfaZpzo4T/RXwKwC1puUnLTKLDcCl2WfIBAVbAUeY982tr9yOhCTFJn5JUMk70h3Ra OEXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ockj9Byf3T5gvRtemQ0G6GpfpIz3wwZ0L8nyTtxTOr4=; b=StO6NTIHKaiWRIfoepNPhTRO1eNtnppfVw+JrCIA0t9jzID7zEypVxVktd5xVuMe49 VonNSQjbzjHdui3wn+ABnGLVj1fLge71LGpJ1b7cs1XOAOCp4mqT8DXlTpJfnoFz2LsS B3s3MIY4y0BicfRXFLocfmbWJ+HkE7nieKVDC1LTwcF0s33vBHbtKwDdxgyIwlt0sGcp GRQeflAmiEyuJ4sb0JhxVBeTqjv0ePHCzO+pSq/3vvxQMkxpP3BK2EZYQufVn4QRbRgx 08yRnmRHC+WfBWxv8xDp1SfcbL1wkXGRsLUa6Yn4/nzvxAeFXwj4cWT3ibcR8W3alTPn LABw== X-Gm-Message-State: APjAAAUQsxfh2/Bz9xJBd6n4igyc/aLhTd4vPMKNVi1GJBDsVsb4Zhaw jX6rhN+evTV04z6yX15+nqIcciB0sY9xQiQ01hBnBQ== X-Google-Smtp-Source: APXvYqyAKJ1wWuk/89dqvgNoY1pXzELDRuWUBZtaMBXwenwFKUFPL7a4T0/o1oZQ5U7G4Bx2F/B6rHDKJolteqg1WVU= X-Received: by 2002:a37:4b48:: with SMTP id y69mr85889385qka.77.1559010043828; Mon, 27 May 2019 19:20:43 -0700 (PDT) MIME-Version: 1.0 References: <2d16a2a9ac5c090f196674d40d0cb398@ultra-secure.de> <3E7C1D63-996E-4AA0-A0A4-455B996BB9D6@gmail.com> In-Reply-To: <3E7C1D63-996E-4AA0-A0A4-455B996BB9D6@gmail.com> From: Warner Losh Date: Mon, 27 May 2019 20:20:32 -0600 Message-ID: Subject: Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option To: Garrett Cooper Cc: Rainer Duffner , "Conrad E. Meyer" , voidanix@420blaze.it, freebsd-current , owner-freebsd-current@freebsd.org X-Rspamd-Queue-Id: BD4E391155 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=eiI/xkJn X-Spamd-Result: default: False [-6.01 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; RCPT_COUNT_FIVE(0.00)[6]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; MX_GOOD(-0.01)[cached: ALT1.aspmx.l.google.com]; RCVD_IN_DNSWL_NONE(0.00)[5.3.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.99)[-0.992,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; FREEMAIL_TO(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; IP_SCORE(-3.01)[ip: (-9.43), ipnet: 2607:f8b0::/32(-3.29), asn: 15169(-2.28), country: US(-0.06)]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Tue, 28 May 2019 02:20:45 -0000 On Mon, May 27, 2019, 6:49 PM Enji Cooper wrote: > > > On May 27, 2019, at 08:27, rainer@ultra-secure.de wrote: > > > > Am 2019-05-27 17:05, schrieb Conrad Meyer: > >> Hi Rainier, > >> On Mon, May 27, 2019 at 7:47 AM wrote: > >>> I have a 32bit FreeBSD 6 binary that I'll need for a bit until the > >>> department who is technically responsible for the service gets around > >>> redoing that service. > >> Even if this proposal is approved, it would only affect 13+. You > >> could still run your FreeBSD 6 binary in a 32-bit 12 VM in a 13+ > >> Bhyve. But do consider lighting a fire under whatever department > >> thinks it's ok to deploy like that :-). > >> Take care, > >> Conrad > > > > > > I thought so, too. > > > > I don't really want to run the abandonware of a RADIUS-server any longe= r > than necessary (as absurd as that sounds). > > > > It's also running a recursive nameserver (previously also authoritative= ) > that is still hard-coded in CPE and computers behind firewalls. > > > > I first wanted to virtualize it (it's not a big problem) - but this way > the problem is just dragged out: "But it still works, does it and we have > no time". > > > > Everybody now knows that the clock is ticking, literally. > > > > Oh, I also remember George Neville-Neil talking about a - what - FreeBS= D > 4 binary that a certain search-engine had lost the sources for and was > running on FreeBSD 7 with compat4. > > (We also have a client who literally begged us to leave a decade-old > Solaris box running through 2019 and half of 2020 so they could continue = to > do their bookkeeping on a home-grown java-app that I suspect they, too ha= ve > lost the sources to...). It's running jdk15 and getting that thing to run > under anything semi-decent doesn't seem to have worked-out too well. > > So, people pray for the best and don't prepare for the worst. > > > > > > Other stuff I can think of: > > - very old Netbackup-Clients (like 5-series), though I doubt they still > work on recent releases, because 7.71 (last official version and intended > for FreeBSD 11) stopped working on FreeBSD12, sadly) > > - certain pre-compiled VMWare Tools Modules? Pre open-source-tools (I > can never make up my mind if it's VMWare-open-Tools or Open-VMWare-Tools = or > something different) > > > > > > What ever people do with COMPAT4-9 - it's bordering the pathological. > > I=E2=80=99ll counter the OP=E2=80=99s suggestion a bit: > > It would be nice if the compat options were modularized and printed out a= n > EOS warning when loaded, so the user was aware that the modules are not > supported by FreeBSD, in terms of security and whatnot. > How is that relevant? They just control system calls, not any userland libraries that might or might not have a security exposure. Plus, if not done right you either startle the horses for no reason, or you run the risk of a console DoS if you print something on each system call... Warner Thanks! > -Enji > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > From owner-freebsd-current@freebsd.org Tue May 28 02:23:33 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 367EA15B2DED; Tue, 28 May 2019 02:23:33 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 1FD6E915A2; Tue, 28 May 2019 02:23:32 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pl1-x62f.google.com with SMTP id d21so7663505plr.3; Mon, 27 May 2019 19:23:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Jis/B3N++PaOTLp+4uxDKh2K+yQsv30taFw1RdcAZ9I=; b=tq3WeHnLCw6X+BkPFtOnGpmSjw3U6FMbz+Wz9bJ8zVSM96EUPLcyeQ7O9UiZjlU+ZW FNEVilL7PHrycH6SqR1vLo1soL/5qgF0vN8hndLFQlsJ3MNyQKUerPjtbiBU8FJryoi5 ZnV3maVDQ65u/RKHI3DYMPkiPj7pINfNvO/MhOeQZtKzBD3Xol5dQoLKdz0GPnNmTI2G vx2pyYFWc44E1lRJgpqwLOLv89xMabmj1c2JDnqJKxgmQddPHzaGDwGcAT/fX3INxVfj B5RkBFU6ZUWZ1HPQgHRa+hOkQMyZgB68jAYEJnkGEfOkm+rauy50DgSbydr2kyycpCBk bcyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Jis/B3N++PaOTLp+4uxDKh2K+yQsv30taFw1RdcAZ9I=; b=e5Iul6jfVG6xyaJNNrTHJBVqFwVW3+uDY5Vpy2BaSYngegZeiVWpstRNu8FvuObbgN YZZ67qSUVPTr5WzoO71xc383Q/P+MYVmkkRmmxqR8O0HOPloSvSdGlQY9ujFprCy/XNI QLHoTBSOI1CrDcbPiTBDfYo9VrVp7DK0M01DaOXIgxxMvvPSrxTb4jj1qXkCHjgyTL60 +TZNJ3kId9enLwiQdOFFLIg0TIw3iOmgPHZwTEfUL+tT4dS3C/L//dSHpmJDz7hgvAJg N9IuKHhm0J3+FwLj2fJTOfV+J7pegGAvO0YIFx2CrhNxgn2Tp+N0H+teLW9/nfuc16/G xbxA== X-Gm-Message-State: APjAAAWEG5aoaFnxjVxfWQo10z4hs6d6r9wccefMH+cal5mYOO3R+NSm FW3XgSe9cAyZw0Q6xygUQ4c= X-Google-Smtp-Source: APXvYqznwYQ2i7YMKmFTG9Ab/6VNEeOamrZArPEGgXOL/NwYtQ59HwPJEWVhNhttM57k4cH2Fv3RQA== X-Received: by 2002:a17:902:1029:: with SMTP id b38mr90519099pla.72.1559010210646; Mon, 27 May 2019 19:23:30 -0700 (PDT) Received: from [192.168.20.7] (c-73-19-52-228.hsd1.wa.comcast.net. [73.19.52.228]) by smtp.gmail.com with ESMTPSA id n37sm772239pjb.0.2019.05.27.19.23.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 May 2019 19:23:29 -0700 (PDT) From: Enji Cooper Message-Id: <24F2196F-A5A9-4BBA-B4D4-D6721B42A7C8@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option Date: Mon, 27 May 2019 19:23:28 -0700 In-Reply-To: Cc: Rainer Duffner , "Conrad E. Meyer" , voidanix@420blaze.it, freebsd-current , owner-freebsd-current@freebsd.org To: Warner Losh References: <2d16a2a9ac5c090f196674d40d0cb398@ultra-secure.de> <3E7C1D63-996E-4AA0-A0A4-455B996BB9D6@gmail.com> X-Mailer: Apple Mail (2.3445.104.11) X-Rspamd-Queue-Id: 1FD6E915A2 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=tq3WeHnL; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of yaneurabeya@gmail.com designates 2607:f8b0:4864:20::62f as permitted sender) smtp.mailfrom=yaneurabeya@gmail.com X-Spamd-Result: default: False [-6.43 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MV_CASE(0.50)[]; RCPT_COUNT_FIVE(0.00)[6]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.92)[-0.922,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE(-2.99)[ip: (-9.34), ipnet: 2607:f8b0::/32(-3.29), asn: 15169(-2.28), country: US(-0.06)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[f.2.6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Tue, 28 May 2019 02:23:33 -0000 > On May 27, 2019, at 7:20 PM, Warner Losh wrote: >=20 > On Mon, May 27, 2019, 6:49 PM Enji Cooper > wrote: >=20 > > On May 27, 2019, at 08:27, rainer@ultra-secure.de = wrote: > >=20 > > Am 2019-05-27 17:05, schrieb Conrad Meyer: > >> Hi Rainier, > >> On Mon, May 27, 2019 at 7:47 AM > wrote: > >>> I have a 32bit FreeBSD 6 binary that I'll need for a bit until the > >>> department who is technically responsible for the service gets = around > >>> redoing that service. > >> Even if this proposal is approved, it would only affect 13+. You > >> could still run your FreeBSD 6 binary in a 32-bit 12 VM in a 13+ > >> Bhyve. But do consider lighting a fire under whatever department > >> thinks it's ok to deploy like that :-). > >> Take care, > >> Conrad > >=20 > >=20 > > I thought so, too. > >=20 > > I don't really want to run the abandonware of a RADIUS-server any = longer than necessary (as absurd as that sounds). > >=20 > > It's also running a recursive nameserver (previously also = authoritative) that is still hard-coded in CPE and computers behind = firewalls. > >=20 > > I first wanted to virtualize it (it's not a big problem) - but this = way the problem is just dragged out: "But it still works, does it and we = have no time". > >=20 > > Everybody now knows that the clock is ticking, literally. > >=20 > > Oh, I also remember George Neville-Neil talking about a - what - = FreeBSD 4 binary that a certain search-engine had lost the sources for = and was running on FreeBSD 7 with compat4. > > (We also have a client who literally begged us to leave a decade-old = Solaris box running through 2019 and half of 2020 so they could continue = to do their bookkeeping on a home-grown java-app that I suspect they, = too have lost the sources to...). It's running jdk15 and getting that = thing to run under anything semi-decent doesn't seem to have worked-out = too well. > > So, people pray for the best and don't prepare for the worst. > >=20 > >=20 > > Other stuff I can think of: > > - very old Netbackup-Clients (like 5-series), though I doubt they = still work on recent releases, because 7.71 (last official version and = intended for FreeBSD 11) stopped working on FreeBSD12, sadly) > > - certain pre-compiled VMWare Tools Modules? Pre open-source-tools = (I can never make up my mind if it's VMWare-open-Tools or = Open-VMWare-Tools or something different) > >=20 > >=20 > > What ever people do with COMPAT4-9 - it's bordering the = pathological. >=20 > I=E2=80=99ll counter the OP=E2=80=99s suggestion a bit: >=20 > It would be nice if the compat options were modularized and printed = out an EOS warning when loaded, so the user was aware that the modules = are not supported by FreeBSD, in terms of security and whatnot. >=20 > How is that relevant? They just control system calls, not any userland = libraries that might or might not have a security exposure. Plus, if not = done right you either startle the horses for no reason, or you run the = risk of a console DoS if you print something on each system call=E2=80=A6 My point was to suggest basically controlling the syscall table (like = linux does for instance). If a compat module was loaded, it would print = out the warning. Not on each syscall entry. That would be insanity as = far as performance degradation would be concerned :/. -Enji From owner-freebsd-current@freebsd.org Tue May 28 02:29:46 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8724D15B32C3 for ; Tue, 28 May 2019 02:29:46 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 B166291962 for ; Tue, 28 May 2019 02:29:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x72f.google.com with SMTP id c70so6133663qkg.7 for ; Mon, 27 May 2019 19:29:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BYZKr72PfZwQqXqVxK7CZR8fEdmlyHYUJaF0Zaeanik=; b=ep3oz+B1MoDY+emoi1nFQQVsN/zAiMvJOqB6IUDckUR32D/CL2lEvnLmYsX1EqRPh2 JhgfzQqie/Uq/CmCisseupLjdqoTUgFSE2FHVvE9aex8wJyce+nNMZk7fzAcln6y1SXp JUlByhrKKED7xJSMhandtUoHblcZWdkvRStBa26QvNHgiEmr5gpCxMYm2GFtlSjylh4k a0L4IYWc5FQxMh2kD5PM4tvt7k/Ycd/uXFC2AFZuJOnwQbgacSGPw/E5hFnddZa2v6B2 M2y1w0KxhI7w/I3n2z73Mlr2CuNwvmuohF+gcvH5o0vN7DAeKxEzA4r9ZwJ2gz48mImu Y4qQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BYZKr72PfZwQqXqVxK7CZR8fEdmlyHYUJaF0Zaeanik=; b=MREsOy6no7plBmFyfanLQKLvIvuAh3rhynop4gRkWaJJh2Rvsc4sBIMetFj7f0lWPG 1oLj1tCyHWLJ0+4HGxZzJlhtTGk+jOYysZy3nyl9DRT5bDs59EtxyzbfB9PuxEUJuFYm Xxu6+40bk2TgyGusOrawJvLVguSL5hB5ZSI1815mdTuFOiW5UEHMv5lF86h1aCf14YHR qtkq0Rkpwi8slvZlsoNEf0/c8QBAbamWr8s7sVUSt/xD+2g9WExubB1g/AK1CfmaDWXZ Sh3DUTXugskzA4CtCLUz7PsXk/21jMFvnRlrXA0bOG5cUkwhzGk4vM51g5MQ/GMvdk2j 2gug== X-Gm-Message-State: APjAAAUSJT2h6b2IE1U7MT9A/jjD+cbihqC+WYuy9e3Q3Xy/BoPMX/rl sq+5xSjaALcU768NGPC/ZokRRyb3VbtuKfO7qUJSPM9G X-Google-Smtp-Source: APXvYqx8tdb5qyoqePqwtKPYkaZcR90AiIz1No6BcGscoOiqvZZoMzYQuDUBfEBTH8yes9v/jSanu6RgBF5BhpcMjD0= X-Received: by 2002:a37:484e:: with SMTP id v75mr9894873qka.331.1559010584927; Mon, 27 May 2019 19:29:44 -0700 (PDT) MIME-Version: 1.0 References: <2d16a2a9ac5c090f196674d40d0cb398@ultra-secure.de> <3E7C1D63-996E-4AA0-A0A4-455B996BB9D6@gmail.com> <24F2196F-A5A9-4BBA-B4D4-D6721B42A7C8@gmail.com> In-Reply-To: <24F2196F-A5A9-4BBA-B4D4-D6721B42A7C8@gmail.com> From: Warner Losh Date: Mon, 27 May 2019 20:29:33 -0600 Message-ID: Subject: Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option To: Garrett Cooper Cc: Rainer Duffner , "Conrad E. Meyer" , voidanix@420blaze.it, freebsd-current , owner-freebsd-current@freebsd.org X-Rspamd-Queue-Id: B166291962 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=ep3oz+B1 X-Spamd-Result: default: False [-5.96 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; RCPT_COUNT_FIVE(0.00)[6]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; MX_GOOD(-0.01)[cached: ALT1.aspmx.l.google.com]; RCVD_IN_DNSWL_NONE(0.00)[f.2.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.92)[-0.924,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; FREEMAIL_TO(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; IP_SCORE(-3.03)[ip: (-9.50), ipnet: 2607:f8b0::/32(-3.29), asn: 15169(-2.28), country: US(-0.06)]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Tue, 28 May 2019 02:29:46 -0000 On Mon, May 27, 2019, 8:23 PM Enji Cooper wrote: > > On May 27, 2019, at 7:20 PM, Warner Losh wrote: > > On Mon, May 27, 2019, 6:49 PM Enji Cooper wrote: > >> >> > On May 27, 2019, at 08:27, rainer@ultra-secure.de wrote: >> > >> > Am 2019-05-27 17:05, schrieb Conrad Meyer: >> >> Hi Rainier, >> >> On Mon, May 27, 2019 at 7:47 AM wrote: >> >>> I have a 32bit FreeBSD 6 binary that I'll need for a bit until the >> >>> department who is technically responsible for the service gets aroun= d >> >>> redoing that service. >> >> Even if this proposal is approved, it would only affect 13+. You >> >> could still run your FreeBSD 6 binary in a 32-bit 12 VM in a 13+ >> >> Bhyve. But do consider lighting a fire under whatever department >> >> thinks it's ok to deploy like that :-). >> >> Take care, >> >> Conrad >> > >> > >> > I thought so, too. >> > >> > I don't really want to run the abandonware of a RADIUS-server any >> longer than necessary (as absurd as that sounds). >> > >> > It's also running a recursive nameserver (previously also >> authoritative) that is still hard-coded in CPE and computers behind >> firewalls. >> > >> > I first wanted to virtualize it (it's not a big problem) - but this wa= y >> the problem is just dragged out: "But it still works, does it and we hav= e >> no time". >> > >> > Everybody now knows that the clock is ticking, literally. >> > >> > Oh, I also remember George Neville-Neil talking about a - what - >> FreeBSD 4 binary that a certain search-engine had lost the sources for a= nd >> was running on FreeBSD 7 with compat4. >> > (We also have a client who literally begged us to leave a decade-old >> Solaris box running through 2019 and half of 2020 so they could continue= to >> do their bookkeeping on a home-grown java-app that I suspect they, too h= ave >> lost the sources to...). It's running jdk15 and getting that thing to ru= n >> under anything semi-decent doesn't seem to have worked-out too well. >> > So, people pray for the best and don't prepare for the worst. >> > >> > >> > Other stuff I can think of: >> > - very old Netbackup-Clients (like 5-series), though I doubt they stil= l >> work on recent releases, because 7.71 (last official version and intende= d >> for FreeBSD 11) stopped working on FreeBSD12, sadly) >> > - certain pre-compiled VMWare Tools Modules? Pre open-source-tools (I >> can never make up my mind if it's VMWare-open-Tools or Open-VMWare-Tools= or >> something different) >> > >> > >> > What ever people do with COMPAT4-9 - it's bordering the pathological. >> >> I=E2=80=99ll counter the OP=E2=80=99s suggestion a bit: >> >> It would be nice if the compat options were modularized and printed out >> an EOS warning when loaded, so the user was aware that the modules are n= ot >> supported by FreeBSD, in terms of security and whatnot. >> > > How is that relevant? They just control system calls, not any userland > libraries that might or might not have a security exposure. Plus, if not > done right you either startle the horses for no reason, or you run the ri= sk > of a console DoS if you print something on each system call=E2=80=A6 > > > My point was to suggest basically controlling the syscall table (like > linux does for instance). If a compat module was loaded, it would print o= ut > the warning. Not on each syscall entry. That would be insanity as far as > performance degradation would be concerned :/. > Except it would take a lot of work to make the compat options a module. Also, we need them for the upgrade path... I'm still not convinced a warning would be more beneficial than the concern it would generates... Warner From owner-freebsd-current@freebsd.org Tue May 28 04:44:09 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8014815B5C2C; Tue, 28 May 2019 04:44:09 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9950395622; Tue, 28 May 2019 04:44:08 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from comporellon.tachypleus.net (cpe-45-49-150-87.socal.res.rr.com [45.49.150.87]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id x4S4i4ve009608 (version=TLSv1.2 cipher=AES128-SHA bits=128 verify=NOT); Mon, 27 May 2019 21:44:04 -0700 Subject: Re: FreeBSD and Coreboot To: Warner Losh Cc: Eric McCorkle , "freebsd-hackers@freebsd.org" , FreeBSD Current , =?UTF-8?Q?Edward_Tomasz_Napiera=c5=82a?= References: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> <1452db0c-1210-3230-c044-bc682e7e1745@metricspace.net> <3aa00c6b-2502-ffad-c915-a833292882bd@freebsd.org> From: Nathan Whitehorn Openpgp: preference=signencrypt Autocrypt: addr=nwhitehorn@freebsd.org; keydata= mQINBFuARN8BEADLKYsG3l1aq/M21R59I/5EsEfvtvd15ZJ9lDHcWPuxzIfGnu2LMpe5PrFP e/Y4bcsPrlB4S3I3ooIUDvoEEsDeqgqlZod3QevOK/RjLqiqx1i/4mKnobJ++3ppyVVIccgN sUrj786OYCFCI/W+uWw7cbKewNeaL//Z/TDKlHLkssiy6qmZbNQ0ZjcMLJKUesk4eVg2TtTD HNe42ZuxbUC9iLYieO4c7kQB4qiFhagDRiObXrLzvm2MQYeAaNVRqID+mfI75TWrQ+t98iVu mHvFu461eeteq59jg6H/IL07ACxL+HzEVM+D6tPtPrz7ppr3wiZL5Cu17yu0nAx0nhJTV8ZB qza1rOVun0x65S14L41XD2HkmBDxTaRlTg8ypnkLFo8kh+MEq4k67apL/DUGcaUjKy2TVUC7 3igLO/DwQHrkWx2RrOmS3xS0TgGXVmB47nq2Zveo3fcjporQK63n2sbLkS70cfAJAJ9KHEIx u9am44iW5Ku3+mVLgQYybtcUxlk/Jw/BA5V6KUcDQMd5kTm0MyagziqMaT+57ceYxwRBK4HC DCLRpSOHV81/YzyL5vnwfHsxADm3091rd0uwr8uRCQn7wLvlcFyp/JKSFkVnE1oo7UE4QQJZ GbSJyvj7GdXu0LdghALcMj/thdb+js4D3UuCaAMecgVSscxEIQARAQABtClOYXRoYW4gV2hp dGVob3JuIDxud2hpdGVob3JuQGZyZWVic2Qub3JnPokCTgQTAQgAOBYhBD1kIPqoIUk+gL8N YTi2TZRmhOh3BQJbgFJIAhsDBQsJCAcCBhUKCQgLAgQWAgMBAh4BAheAAAoJEDi2TZRmhOh3 M6YP/RHkgLWCPGGBSKZ3an3GhRMO2B5qd+g5QGUt4gvvdMMgUqwvmUva4obvgS5qXbYOmFGM cP5myo1mcJ45Q06Qdy8pnFEBBm4dKlNZT8LHAz/lr0/I8FINJcIdwmyxHJzELW7nlBy+ZO0z rCJ4CK//MMCAlomj6s9ydaGF0Dnbj9LmE+CS/ZZaYqil5KgsXO2rbN1wa0QOpZjAc8I1NyDN 10nWTZSLeFcbfTWItc8bxVC8NOerG25OVMxjyvqp15ZSExL5NfxIMsrTAjk5AsLr0bCW3tGA A0eM2cwLBhAfdh3fdj+/8tzakafFwR8XrA6YWrvgFmIjCgXfbVGp058595SDHGM1BeCJ94Bm TJMbCTsGPTUbRsWXJ4ytjziqMPPYkXif+NdWNLX3/TTu4oGPGsPQjbTA2xTfLLjNFKLv0ieT XTMg3vMhiOsZnfKt65fwoJWh+mfBe9S4ImNiI2C6H/gr9rpjZZQ3f85+AUAQrVjZJwaOctTC wOr8o8odS5WrpwZVEQhJj8TdOiHKPsAS8+zsjdGucfkXBHnSctMS1uv9QMTTrMvWhuihzYlw 2pC3LHEvxUpv1lk+jH42uRqbMF0FfSPkundHalWXY/HZKWdukc5lhIcGYR9bcm+Eq5/P0Qyv 3q8Q6hIjx6pN4828q8aA0lDnQ1LOtGZjToGZUrcmuQINBFuARRkBEAC9SmeRBQpprN52L+js v29No0eITfSrXTbNhqLB4ikDcnGFDih9yunAQyKk+y++unxYute4NH70qnKpvHOzHENKrSNg uDgs0ga7/4iQMs2rWqTgSQ97JfmW6ilqJXbtKyKvLvK2Jt1lJo7I2uB3Sg3pupHc0WMElIyg EHm/goNnZA401BPGmkgwl9vD4UHxn4+om3CrqpcNWFIrJ/bHKjtg/CcINz3DA7KuyKTlg+jO IgH1Xf5cmCW8e4LeQoMqkXu5y9E+4/M+o6YKiLLplSk5pc0pep/+9S+5fVW2YTDjNXVIY1KK E5IqWZ5HsjxcsfEVEVgm/auR7iVreIi2dkJVrKczMMV0KBOqqwg3eXwfaUZo1NWL6FaHruYK tHkSblUWKSR2sLfDUnrFTj8/fRTHba6fDUhoxHPVnptEjCsSvUxCEVWZN9V64XjlFCO3cF72 e75ikbGp2R1PRPWgDFmmX0pHTGPKUImqKuF4krGrY64pf8iRUTyQvbNF49i6e4ycGwlAHhSq FBZkVBwvUZeDp9DFfL2Rht/QtjYH0yfcT5zRL0aI3oX6I7luCYvm4K4HG461BvTkvxZ2xmo3 dACzmwEyAClpseEaMOsbgwosnTFhehd4Qz1Kl4Yiry8/yqISEodt6vRjs5jAsT2okDBCc6qx +dww3ymXNvEGrf+AvQARAQABiQRsBBgBCAAgFiEEPWQg+qghST6Avw1hOLZNlGaE6HcFAluA RRkCGwICQAkQOLZNlGaE6HfBdCAEGQEIAB0WIQTTpX+yMt35tfRft49NUswkCJ+wagUCW4BF GQAKCRBNUswkCJ+waqoWEACAWq6YgCh4H+JPNxM33ENOmKZ+WmIfr7jgoy1UAhUz0OshLPHM dy4oyaPefNaio5jcp8rvuT7qxA19s1VOyA6NIvCBnMzs+x9bTkQdZ31mcBcESNltKShYO3mq JE8Iz665xUlY2U45x8oGO+pYvWXvZv1C4pXtqczzQQldRuYJ+zfHyGmJoDP6exj0ALVfApH1 RKrCHt51ZottN0gcy4fkmBF+D13hUWAEtq0TBXw+2m6Qwq5xQmWkItzw4x9CF+wE78hNodY5 TXoifJvMB78O/ltPUqUiiPn6FAmi7ErDA3Ue+b4dSBWCx/i+jhh08blrbTQeMr6yswQJzx3M m6BDvYsKZKC9WNI9YKJxopd/udikmcPSoBTyWgMhjm0FPMb3c9Ay9nlbV04LlaqT7DsG8WbL X6O8CZUEpsB8r2kptm4wjjkIywT5eyXbcoNMV449KRzobWDCLOzA50cqTCPwa+YaHUamcoXs 7f3g0AllZVg3J48tq3orQrbmd80/n6AK158fURHR4pPf1m7Z8LGvmfN5vSpw81IgJ0KQEg7P mBsrOZKXGRNvtiHipWvdC9+ex1OSHRNtKTL7bbBYV01atsw74pspBLwXbH/lWnUtFucwav41 wbtHYdfbhxpXZRL0YLcrJq6+oatJlUxzAjO3wz/EuU/5OAwMGJVptO80308ID/4jEYmXl0Ux PEXv2/FjHser/OdhzQNhLft9bBlMiSGwui5Rv0tWPZ7dB7gxsuJIBzvb/FoJXbFysmm+o4Bt go0xQqXqFBX4pD9KYKTDo9q4Bh+0k+NGKvBMJI9pwFu+Ix+u1dbrFnpi/q2nFRfYEKeZiKOD HOxMMcSeYEFaHqiiy5A7QDuW7i7e4uGY0Ls7vnxrNQTWpEIe9E6kIjIHtNWAOIypL8+tiuxr CckPYFEDEmJmp1XIIoFXOIgGceky7huMvtyWHAuE1RjrZpN34nuntpoPlYv0PpPNAIg20HBA eX+reoTCRquUz5F2yZuZRL4o2/sSbDwu4m1As4G0QNaWB7j3grTn6AEVhMbjLgA+QkPpvpN8 s3iEVlEyzuypuGhRR9sMMB/8itWKtCV4/TGoAGJkoK+LsVllfIuu2m9ekV9HAOg3583ame9L NQD0nD35egjdIv7PhbZDYVgPq1NS27b8wz8RqvYWlw+1kUSD62byWu/oFLLifHfUh66ImLCk kbJJBZ5XgGKb/mVpBRiyw7zJUJZgIyTB1NcCWr09n7X+44KuocAYM/hE7NKv8To/5PFmsWFu Y8m1Qh/j7U8/gOdAT7+Q4tLczRRU/ngcW8b/1ajWMY6UuZhrp/WfLoKHS79VYK39OClHRLSU hr911kye7XJLUdGr4S2k+enQb7kCDQRbgEVBARAA4soW2Dq6zQAsDsu2+PEiyQiCoUmMfDaR r9S10njfY/2S+YGrvPi/T6b+CTEI44bTIOLYK/8AsmhuzJvnq1tToxTRJGNOKjflLaOK3fr0 HUEMLZMs0XffuxSq5THSXjCQRcQF5+8tFii4XwFFuSCO96DuwDg2OyJ25DH3a88mcGhofY5b GoNuvlfqQXlzH2M+spQnhmof+toT9JIOG2jDhoo7SdZu15UZyTXlbVf9LwrOI9cprPEJDyqm tBFMB6Gx0b9tJtYP3mGndMCURuXg3hSqpLufiMJm6cJ6KLZMNkdW/H+WkUBPZ7PHrjqnY9SY fmGmJUyBtjm4dzJqHA1/54047uCi2c1iiJ6gvDh9R5Ng6r6zcg2KwIHiKi9Bxk4JhLObBGiV BGCBfS0FJ6dHo+CnfxiNUiRa8weHFtWJ8C6yO9Vub8ZB4DYxoK2SiDncjJ+juuL0N42lW5Fz /jsHEeLwm13LIaAs7XcCNzBzpXsot4ObD9JckAyyy5ZCVfOzw6Cyk2+3KYGHmurhOXEBjrkv di//KHSLMTO04k7c5v3LeAuuntN4MjQQ71LIa4VduBZj81eUPBYdaC4yA7sNYz8rF5oxjId+ d98h5Dq6EzbXLjYjs1XXWZbDJy/9cmQgPd93sZYF5xqR1idgj/sVgwMeaxRA+ZIyRuoKphxl 7jsAEQEAAYkCNgQYAQgAIBYhBD1kIPqoIUk+gL8NYTi2TZRmhOh3BQJbgEVBAhsMAAoJEDi2 TZRmhOh3ZFsQAJtDZvAnf75u+pyUStt6R/sFdiNrfv8fEYTrurf3F/byF6fy9Ya1fCrhtaZl PkfxsGpeKADhtRTic3hffEQN9PKqRAy4NOefBPtjrUHhASqGLhqrhp1/8o/SXVQKDgInQpL3 fUdqf5VuK5Rxtp27VlffsR/qD+Eb6a3n0V5cMxTSt6uzYGmvzMHzLCiMCxUL3aS84cuwJC10 Kw/ML5HoHVtjr9F72yUzU0F37aTgFRWFi7wVvwivfs6Y3RoZDNi5FzN+uZH85Xn/X6Dld5hI Vur/RDcqQVYsd+KZ9/yVv0ZFat285SljIaW6/j1v8bmj2VLE/BfIF9qhWL9YMN8n9cnD0f3R crrxNjE98RCR64sQTOD4HPdl527KjZnHhLlqkuoBu/RHN25eAgZhlU+7xHjJrydBYd5Smi3X uW3xIvvIWQwloBeTbtCpQBrGOqcYEufvRgxZcUbJJ++OBpHUW279L8dIqofubxoVhl+2qztm iNc12oYdkpGsjHqFFRi5lAzy7EcPB4XiMX5AjBghSa2vLmHyK2JKO30oeOmQfdbPmjWaTpxs U037CCkemUOX+JkxmMWyRMAl8SxgdVJKbbXNxi++iCtupi9yIxO3Lrn7QDwbP20xtw3H149o agz72N4V6GvNON1qJOIL66ZJ39jb0MJbg4EyvVV+59VUpt8B Message-ID: <79c249c0-e6b0-a584-ad23-c9a4f57ff3c1@freebsd.org> Date: Mon, 27 May 2019 21:44:03 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Sonic-CAuth: UmFuZG9tSVYrlsBa+UkOuWqmMbK/TSh8BJnjxuZwdiuMPjZQNMzdvfNHyBrjL+3xnQE/FCJLTcP6nIHpLVCAA9okt8M9G/bkQ8573ve5cPw= X-Sonic-ID: C;TL12OAOB6RGdcj30OgXfLQ== M;0B7IOAOB6RGdcj30OgXfLQ== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd X-Rspamd-Queue-Id: 9950395622 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.93 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.94)[-0.935,0]; ASN(0.00)[asn:7065, ipnet:64.142.96.0/19, country:US] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Tue, 28 May 2019 04:44:09 -0000 On 2019-05-27 19:14, Warner Losh wrote: > On Mon, May 27, 2019, 7:18 PM Nathan Whitehorn > wrote: > >> >> On 2019-05-27 15:50, Eric McCorkle wrote: >>> On 5/27/19 5:53 PM, Edward Napierala wrote: >>>> On Mon, 27 May 2019 at 16:14, Eric McCorkle >> wrote: >>>> [..] >>>> >>>>> My plan is roughly this: >>>>> >>>>> * Refurbish the GRUB port, get it working again in QEMU (possibly on >> one >>>>> of my machines), also possibly push a patch to GRUB to use the keybufs >>>>> mechanism to pass in GELI keys. >>>>> >>>>> * Get coreboot with GRUB/Seabios booting FreeBSD in QEMU >>>>> >>>>> * Possibly create a coreboot port (uncertain how this would work, since >>>>> Coreboot has its own extensive config menu) >>>>> >>>>> * Hold my breath and test it out on real hardware (I have a Librem 13 >> r1 >>>>> for this purpose) >>>>> >>>>> * Possibly try getting the FreeBSD kernel to work as a coreboot >> payload. >>>> Out of curiosity - why the kernel and not loader(8)? >>>> >>> If I understand coreboot correctly, loader would have to directly >>> manipulate devices _without a BIOS_. That is, it would have to have an >>> entire device detection/interface layer, which I don't believe is the >>> case today. >>> >>> At least in the EFI case, loader is talking through the system's EFI >>> implementation, which takes care of all that for you. BIOS works in a >>> similar way. My sense is getting loader to the point where it could be >>> a coreboot (without Seabios/GRUB/Tianocore) would be quite an >> undertaking. >> On IBM PowerNV systems, which also don't provide interfaces to a >> second-stage loader, we just abandoned loader(8). It's way too much work. >> > How do you use tunables and loadable modules? > > Warner > The firmware on PowerNV has a way to write tunables to the device-tree, which we rehydrate into something that looks like it came from loader. We don't usefully support loadable modules at the moment. The firmware can optionally load exactly one file from the boot filesystem and pass it to the kernel (for Linux, the initrd). There are a couple of ways to imagine exploiting this for kernel modules, but all of them are kind of crummy. -Nathan From owner-freebsd-current@freebsd.org Tue May 28 04:46:27 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25D5E15B5DCC for ; Tue, 28 May 2019 04:46:27 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x744.google.com (mail-qk1-x744.google.com [IPv6:2607:f8b0:4864:20::744]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 588579581D for ; Tue, 28 May 2019 04:46:26 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x744.google.com with SMTP id j1so20532757qkk.12 for ; Mon, 27 May 2019 21:46:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LYTziAV32kqbAD06fdIn2YevrGVoLtxN68LH5exHUCQ=; b=tyVZ3eFHM5Vls1QAIMqD2BdbHoW6w0nom18sLynoHunuj4BWJ+qhiUhBf7ZUsPrjCa wslD47sVjadlN9CJdRQ7hln0BeK4FpEarxzSl/9ZgD80ujSBJNB09DOQjEZzkkfIqZbp VMbF4Z6TZRzwDVaGBVwqhkQajYB2rAW6KlXgL9hd00z4rOiF4cug4uVwItSFKqZxvsMg BlmCxQ0aZCcdjcmn75Hu0oIuFsq7Bl9edm5eqKHYj8/8LaI3c5MYMo138sXc5Njzp0qS vaU+n1s6V9PYmCwGE1pLPgHZsbmIh+q+STVILmQ/PvDnvqO2zvogezL6XMOUCIh3LDVd tkiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LYTziAV32kqbAD06fdIn2YevrGVoLtxN68LH5exHUCQ=; b=KljRr7s2eBWNc3Q7smeW2VCUiuYF8fjU/Sreg77ImTmREn4c2v3FO6S1dLucz2xryX okHhTcNNU/HWlnIWexpiuVso4u5F4ulxpEHW6NsWgCZ4Uy4KZPV+550iczlnJQ+EHxHx q01SNz2ZbAUF/ZsyVyH4Hsj9tF9wBQgT5LFPEmIHLp5ScZ/RWgXXgloxkglFWIN/mzQ3 cgnQqCHu7YT5mOAC8xOeHQ7S5NYwm6CCu0dk/Cf2YWeQ7fhXZ1xxm62vDJkibmSXITus MPh4Kx1V54UwUxDsZmKB7BE+0GkFC8m1yMWr6mA9cOhw+Q5pRWn3wl3/HnbFhlfCtEKT sFjQ== X-Gm-Message-State: APjAAAU+SrU5P21RBePAGm3JP2fBIhNifJr68JevdGb1Gc1xQn4jdZi0 fG8VOinxt6co5pUxH1iFStAmTiJeVPCDO2q7m7he4Q== X-Google-Smtp-Source: APXvYqzf0il/NzHYHZFC6Shon9+uBIWylF3xebTDL0ITjGG6W0Xb9J2NvLxq1929KbODY7xSdyk7CEts6DxUI0aSYyw= X-Received: by 2002:a37:4b48:: with SMTP id y69mr86077271qka.77.1559018785613; Mon, 27 May 2019 21:46:25 -0700 (PDT) MIME-Version: 1.0 References: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> <1452db0c-1210-3230-c044-bc682e7e1745@metricspace.net> <3aa00c6b-2502-ffad-c915-a833292882bd@freebsd.org> <79c249c0-e6b0-a584-ad23-c9a4f57ff3c1@freebsd.org> In-Reply-To: <79c249c0-e6b0-a584-ad23-c9a4f57ff3c1@freebsd.org> From: Warner Losh Date: Mon, 27 May 2019 22:46:13 -0600 Message-ID: Subject: Re: FreeBSD and Coreboot To: Nathan Whitehorn Cc: Eric McCorkle , FreeBSD Hackers , FreeBSD Current , =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= X-Rspamd-Queue-Id: 588579581D X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=tyVZ3eFH X-Spamd-Result: default: False [-3.35 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; RCPT_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; MX_GOOD(-0.01)[cached: ALT1.aspmx.l.google.com]; RCVD_IN_DNSWL_NONE(0.00)[4.4.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.56)[-0.563,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; IP_SCORE(-0.78)[ip: (1.73), ipnet: 2607:f8b0::/32(-3.29), asn: 15169(-2.28), country: US(-0.06)]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Tue, 28 May 2019 04:46:27 -0000 On Mon, May 27, 2019, 10:44 PM Nathan Whitehorn wrote: > > > On 2019-05-27 19:14, Warner Losh wrote: > > On Mon, May 27, 2019, 7:18 PM Nathan Whitehorn > > wrote: > > > >> > >> On 2019-05-27 15:50, Eric McCorkle wrote: > >>> On 5/27/19 5:53 PM, Edward Napierala wrote: > >>>> On Mon, 27 May 2019 at 16:14, Eric McCorkle > >> wrote: > >>>> [..] > >>>> > >>>>> My plan is roughly this: > >>>>> > >>>>> * Refurbish the GRUB port, get it working again in QEMU (possibly on > >> one > >>>>> of my machines), also possibly push a patch to GRUB to use the > keybufs > >>>>> mechanism to pass in GELI keys. > >>>>> > >>>>> * Get coreboot with GRUB/Seabios booting FreeBSD in QEMU > >>>>> > >>>>> * Possibly create a coreboot port (uncertain how this would work, > since > >>>>> Coreboot has its own extensive config menu) > >>>>> > >>>>> * Hold my breath and test it out on real hardware (I have a Librem 13 > >> r1 > >>>>> for this purpose) > >>>>> > >>>>> * Possibly try getting the FreeBSD kernel to work as a coreboot > >> payload. > >>>> Out of curiosity - why the kernel and not loader(8)? > >>>> > >>> If I understand coreboot correctly, loader would have to directly > >>> manipulate devices _without a BIOS_. That is, it would have to have an > >>> entire device detection/interface layer, which I don't believe is the > >>> case today. > >>> > >>> At least in the EFI case, loader is talking through the system's EFI > >>> implementation, which takes care of all that for you. BIOS works in a > >>> similar way. My sense is getting loader to the point where it could be > >>> a coreboot (without Seabios/GRUB/Tianocore) would be quite an > >> undertaking. > >> On IBM PowerNV systems, which also don't provide interfaces to a > >> second-stage loader, we just abandoned loader(8). It's way too much > work. > >> > > How do you use tunables and loadable modules? > > > > Warner > > > > The firmware on PowerNV has a way to write tunables to the device-tree, > which we rehydrate into something that looks like it came from loader. > > We don't usefully support loadable modules at the moment. The firmware > can optionally load exactly one file from the boot filesystem and pass > it to the kernel (for Linux, the initrd). There are a couple of ways to > imagine exploiting this for kernel modules, but all of them are kind of > crummy. > Now that the loader supports a ram disk, we are almost to something useful... but yea, almost and crummy often go hand in hand. Warner > From owner-freebsd-current@freebsd.org Tue May 28 08:22:10 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC5CA15BA817 for ; Tue, 28 May 2019 08:22:10 +0000 (UTC) (envelope-from pkubaj@anongoth.pl) Received: from mail.anongoth.pl (mail.anongoth.pl [46.248.190.61]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "anongoth.pl", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 40B0F6D7D2 for ; Tue, 28 May 2019 08:22:08 +0000 (UTC) (envelope-from pkubaj@anongoth.pl) Received: from anongoth.pl (unknown [10.8.0.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: pkubaj@anongoth.pl) by mail.anongoth.pl (Postfix) with ESMTPSA id 1461A27A43 for ; Tue, 28 May 2019 10:21:54 +0200 (CEST) Date: Tue, 28 May 2019 10:21:53 +0200 From: Piotr Kubaj To: freebsd-current@freebsd.org Subject: Re: FreeBSD and Coreboot Message-ID: <20190528082153.GA80209@ThinkPad-X200.g.anongoth.pl> Mail-Followup-To: freebsd-current@freebsd.org References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="kjBJdXS7LUedAkI3" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.4 (2019-03-13) X-Rspamd-Queue-Id: 40B0F6D7D2 X-Spamd-Bar: --------- X-Spamd-Result: default: False [-9.74 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[anongoth.pl:s=ANONGOTH]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:46.248.190.61]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; DKIM_TRACE(0.00)[anongoth.pl:+]; MX_GOOD(-0.01)[mail.anongoth.pl]; DMARC_POLICY_ALLOW(-0.50)[anongoth.pl,reject]; NEURAL_HAM_SHORT(-0.97)[-0.967,0]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; IP_SCORE(-3.67)[ip: (-9.90), ipnet: 46.248.160.0/19(-4.91), asn: 47544(-3.58), country: PL(0.06)]; ASN(0.00)[asn:47544, ipnet:46.248.160.0/19, country:PL]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-Mailman-Approved-At: Tue, 28 May 2019 10:39:02 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Tue, 28 May 2019 08:22:11 -0000 --kjBJdXS7LUedAkI3 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline I have been running coreboot on many boards with FreeBSD for a few years now. I've been getting mixed results. E.g. on ASUS F2A85-M there's no fan control in coreboot so the OS must do it itself and FreeBSD doesn't support it. After running it for some time, my CPU eventually burned... Thinkpads seem to basically work fine, since ACPI takes care of fans. ASUS KGPE-D16 are great boards and can run completely blobless, but to run them with FreeBSD, I had to upgrade cooling (it overheated). And the only way to control fans on those boards with FreeBSD and coreboot is via BMC (there's OpenBMC port that runs great). If KGPE-D16 is too expensive, you could get ASUS KCMA-D8 which are cheaper and basically a low-end KGPE-D16. Asrock E350M1 also works pretty well, but it's a really old board with embedded CPU from AMD. There are also (mentioned before) APU from PCEngines, but beware, only APU1 can run blobless. APU2 and newer need proprietary AGESA (APU1 runs with open-source AGESA) and PSP (ME equivalent). Finally, FreeBSD runs on Raptor Talos and Blackbird boards. They don't run coreboot but OpenPOWER firmware, which is also 100% FOSS. If you can afford them, it's the best way to run FOSS firmware. I run both coreboot boards (with FreeBSD and other systems) and Talos II, so feel free to reach to me via email if you have further questions. --kjBJdXS7LUedAkI3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAABCgB9FiEEycyIeNkkgohzsoorelmbhSCDnJ0FAlzs76FfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM5 Q0M4ODc4RDkyNDgyODg3M0IyOEEyQjdBNTk5Qjg1MjA4MzlDOUQACgkQelmbhSCD nJ1PTRAAn+xnXXV6hcIXl6H3VTcHCqpihCWQRq3NWvXbY57bHINvDnYpl4ZPMtOv YAVj1U5Vw0GjDaMQhgF2B8Gtkv06u4bkIi4jbQmpOcFfwX1tnKYthYZtlhlYA6/0 29B1ot6FwUa4LaftVU0IY4UorUmVCm2Sn/1SRVRIPaeP7P+Xe+uPG+zi3BhPPPlX TaMSmuKVbRfCRTWibX6bKKc/LfMKwyTOHvbgHW9hiQG1QKGHCCTddH2jaKq9T3p/ WRHJCHgb24ReDHKT51qTOkKVNxrq06fSjHxXk4fJSKptuGnyXaHqhblf6IxUCEXy FMkxWgdpeg7NXAG/sR4X50ksVWHoMq16ZaF3zqZ7zz4wNMXDCdTXWisMQjPC5+rH QnLclkLHoOw1ohEF0L65AT4P13tVfM7WWUntgc9ubto15Jf4/4CHlPaWLcJHH3Ox R5Q9D4Qmq0QjRo7JUbsGegxObrWjULL4qZRO1q5QXpVj+4TnsW1A8zle/rY9QpO6 kfSk9TTNL9uSYTu4ZNk6BXhdcWHtXb+FMUXvP7TKzZ3aWAFvJ5Xt7zq/2o0HtYuJ 5vHoZoTlWozU5u5MOyss2Y5JxNQIOBrO/GxR8/A81memHenSbae1qhLYf6824gtl 1trYEwMbc0gKAEpkkyzI6jaO954+qsH89XFdf4BpWim3a4Zcc1w= =1UKQ -----END PGP SIGNATURE----- --kjBJdXS7LUedAkI3-- From owner-freebsd-current@freebsd.org Tue May 28 11:17:29 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 948DC15BE997; Tue, 28 May 2019 11:17:29 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id B3B897480B; Tue, 28 May 2019 11:17:28 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:3210:b3ff:fe77:ca3f] (unknown [IPv6:2001:470:1f11:617:3210:b3ff:fe77:ca3f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 4B4F313AC; Tue, 28 May 2019 11:17:28 +0000 (UTC) To: Warner Losh , Nathan Whitehorn Cc: FreeBSD Hackers , FreeBSD Current , =?UTF-8?Q?Edward_Tomasz_Napiera=c5=82a?= References: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> <1452db0c-1210-3230-c044-bc682e7e1745@metricspace.net> <3aa00c6b-2502-ffad-c915-a833292882bd@freebsd.org> <79c249c0-e6b0-a584-ad23-c9a4f57ff3c1@freebsd.org> From: Eric McCorkle Openpgp: preference=signencrypt Autocrypt: addr=eric@metricspace.net; prefer-encrypt=mutual; keydata= mDMEXMXabRYJKwYBBAHaRw8BAQdAJ2yzSUUR7u7H/bLAFOzhPII7vvJ45zQeB60TxyCoio20 JEVyaWMgTWNDb3JrbGUgPGVyaWNAbWV0cmljc3BhY2UubmV0PoiWBBMWCAA+FiEEG/v8wt9b D9+AxsV/6Y4m2LfgVbIFAlzF2m0CGwMFCQHhM4AFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA CgkQ6Y4m2LfgVbJ9mwD/YpSeQ5F9gpvKFS5Bs5w1Bw7zTOfO7zJQrh9NzDbWtd0BAOSGr/i5 zJer2pAjwambsyU0bhgHNy9IDQ7AGnidIyMHuDgEXMXabRIKKwYBBAGXVQEFAQEHQEBwYuBK iJPJEDtS6hbLgcDSUSbfUNA2rGp3TJ1G+7EqAwEIB4h+BBgWCAAmFiEEG/v8wt9bD9+AxsV/ 6Y4m2LfgVbIFAlzF2m0CGwwFCQHhM4AACgkQ6Y4m2LfgVbJ2kwEAlJj1z3zRJm3mmi6N81by nuwAxk3qcKa67WX2/F3C4soA/iwVuPMnx5RWaoX3i2eKXVNzNwzvTFfeGKxfQBOzMocM Subject: Re: FreeBSD and Coreboot Message-ID: Date: Tue, 28 May 2019 07:17:28 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Tue, 28 May 2019 11:17:29 -0000 On 5/28/19 12:46 AM, Warner Losh wrote: > > > On Mon, May 27, 2019, 10:44 PM Nathan Whitehorn > wrote: > > > > On 2019-05-27 19:14, Warner Losh wrote: > > On Mon, May 27, 2019, 7:18 PM Nathan Whitehorn > > > > wrote: > > > >> > >> On 2019-05-27 15:50, Eric McCorkle wrote: > >>> On 5/27/19 5:53 PM, Edward Napierala wrote: > >>>> On Mon, 27 May 2019 at 16:14, Eric McCorkle > > > >> wrote: > >>>> [..] > >>>> > >>>>> My plan is roughly this: > >>>>> > >>>>> * Refurbish the GRUB port, get it working again in QEMU > (possibly on > >> one > >>>>> of my machines), also possibly push a patch to GRUB to use the > keybufs > >>>>> mechanism to pass in GELI keys. > >>>>> > >>>>> * Get coreboot with GRUB/Seabios booting FreeBSD in QEMU > >>>>> > >>>>> * Possibly create a coreboot port (uncertain how this would > work, since > >>>>> Coreboot has its own extensive config menu) > >>>>> > >>>>> * Hold my breath and test it out on real hardware (I have a > Librem 13 > >> r1 > >>>>> for this purpose) > >>>>> > >>>>> * Possibly try getting the FreeBSD kernel to work as a coreboot > >> payload. > >>>> Out of curiosity - why the kernel and not loader(8)? > >>>> > >>> If I understand coreboot correctly, loader would have to directly > >>> manipulate devices _without a BIOS_.  That is, it would have to > have an > >>> entire device detection/interface layer, which I don't believe > is the > >>> case today. > >>> > >>> At least in the EFI case, loader is talking through the system's EFI > >>> implementation, which takes care of all that for you.  BIOS > works in a > >>> similar way.  My sense is getting loader to the point where it > could be > >>> a coreboot (without Seabios/GRUB/Tianocore) would be quite an > >> undertaking. > >> On IBM PowerNV systems, which also don't provide interfaces to a > >> second-stage loader, we just abandoned loader(8). It's way too > much work. > >> > > How do you use tunables and loadable modules? > > > > Warner > > > > The firmware on PowerNV has a way to write tunables to the device-tree, > which we rehydrate into something that looks like it came from loader. > > We don't usefully support loadable modules at the moment. The firmware > can optionally load exactly one file from the boot filesystem and pass > it to the kernel (for Linux, the initrd). There are a couple of ways to > imagine exploiting this for kernel modules, but all of them are kind of > crummy. > > > Now that the loader supports a ram disk, we are almost to something > useful... but yea, almost and crummy often go hand in hand. This is looking out ahead of my current roadmap, but if you were to do a kernel as the coreboot payload, there'd need to be some kind of trick to support ZFS-only systems. ZFS requires modules, which are typically pre-loaded (and linked) by loader (or GRUB). Coreboot has no disk or filesystem or even device access facilities, however. It's just "pull an image out of flash, do the bare essential hardware initialization to get to a C runtime environment, then jump into the image". One way around it might be to concatenate the modules and a kernel together with a kind of mezzanine level that does all the module linking, then jumps into the kernel. I suppose you could also build that functionality into the kernel itself, or perhaps even coreboot. I suspect there might be some license issues that kept us from being able to build these modules into the kernel in the first place, though, and that might affect the choice as well. From owner-freebsd-current@freebsd.org Tue May 28 14:22:13 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AED44159E260; Tue, 28 May 2019 14:22:13 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2154F83557; Tue, 28 May 2019 14:22:12 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x4SEM2wH015969; Tue, 28 May 2019 07:22:02 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x4SEM2fR015968; Tue, 28 May 2019 07:22:02 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201905281422.x4SEM2fR015968@gndrsh.dnsmgr.net> Subject: Re: FreeBSD and Coreboot In-Reply-To: To: Eric McCorkle Date: Tue, 28 May 2019 07:22:02 -0700 (PDT) CC: Warner Losh , Nathan Whitehorn , FreeBSD Hackers , FreeBSD Current , =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 2154F83557 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.92 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.92)[-0.923,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Tue, 28 May 2019 14:22:13 -0000 > On 5/28/19 12:46 AM, Warner Losh wrote: > > > > > > On Mon, May 27, 2019, 10:44 PM Nathan Whitehorn > > wrote: > > > > > > > > On 2019-05-27 19:14, Warner Losh wrote: > > > On Mon, May 27, 2019, 7:18 PM Nathan Whitehorn > > > > > > wrote: > > > > > >> > > >> On 2019-05-27 15:50, Eric McCorkle wrote: > > >>> On 5/27/19 5:53 PM, Edward Napierala wrote: > > >>>> On Mon, 27 May 2019 at 16:14, Eric McCorkle > > > > > >> wrote: > > >>>> [..] > > >>>> > > >>>>> My plan is roughly this: > > >>>>> > > >>>>> * Refurbish the GRUB port, get it working again in QEMU > > (possibly on > > >> one > > >>>>> of my machines), also possibly push a patch to GRUB to use the > > keybufs > > >>>>> mechanism to pass in GELI keys. > > >>>>> > > >>>>> * Get coreboot with GRUB/Seabios booting FreeBSD in QEMU > > >>>>> > > >>>>> * Possibly create a coreboot port (uncertain how this would > > work, since > > >>>>> Coreboot has its own extensive config menu) > > >>>>> > > >>>>> * Hold my breath and test it out on real hardware (I have a > > Librem 13 > > >> r1 > > >>>>> for this purpose) > > >>>>> > > >>>>> * Possibly try getting the FreeBSD kernel to work as a coreboot > > >> payload. > > >>>> Out of curiosity - why the kernel and not loader(8)? > > >>>> > > >>> If I understand coreboot correctly, loader would have to directly > > >>> manipulate devices _without a BIOS_.? That is, it would have to > > have an > > >>> entire device detection/interface layer, which I don't believe > > is the > > >>> case today. > > >>> > > >>> At least in the EFI case, loader is talking through the system's EFI > > >>> implementation, which takes care of all that for you.? BIOS > > works in a > > >>> similar way.? My sense is getting loader to the point where it > > could be > > >>> a coreboot (without Seabios/GRUB/Tianocore) would be quite an > > >> undertaking. > > >> On IBM PowerNV systems, which also don't provide interfaces to a > > >> second-stage loader, we just abandoned loader(8). It's way too > > much work. > > >> > > > How do you use tunables and loadable modules? > > > > > > Warner > > > > > > > The firmware on PowerNV has a way to write tunables to the device-tree, > > which we rehydrate into something that looks like it came from loader. > > > > We don't usefully support loadable modules at the moment. The firmware > > can optionally load exactly one file from the boot filesystem and pass > > it to the kernel (for Linux, the initrd). There are a couple of ways to > > imagine exploiting this for kernel modules, but all of them are kind of > > crummy. > > > > > > Now that the loader supports a ram disk, we are almost to something > > useful... but yea, almost and crummy often go hand in hand. > > This is looking out ahead of my current roadmap, but if you were to do a > kernel as the coreboot payload, there'd need to be some kind of trick to > support ZFS-only systems. > > ZFS requires modules, which are typically pre-loaded (and linked) by > loader (or GRUB). Coreboot has no disk or filesystem or even device > access facilities, however. It's just "pull an image out of flash, do > the bare essential hardware initialization to get to a C runtime > environment, then jump into the image". ZFS does not "require" modules, you can statically compile both opensolaris and zfs into your kernel. > > One way around it might be to concatenate the modules and a kernel > together with a kind of mezzanine level that does all the module > linking, then jumps into the kernel. I suppose you could also build > that functionality into the kernel itself, or perhaps even coreboot. It is called a statically linked kernel, no modules at all. > I suspect there might be some license issues that kept us from being > able to build these modules into the kernel in the first place, though, > and that might affect the choice as well. I do not know of a license issue for US, linux has one due to incompatibility of a GPL kernel with a CDDL ZFS module, thankfully we do not have that issue. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Tue May 28 15:41:28 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 81ABC15A3876; Tue, 28 May 2019 15:41:28 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-ot1-f44.google.com (mail-ot1-f44.google.com [209.85.210.44]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 2428185C89; Tue, 28 May 2019 15:41:28 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by mail-ot1-f44.google.com with SMTP id g18so18155991otj.11; Tue, 28 May 2019 08:41:28 -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:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7mFP629XXHkvIS9PRfhZv6JcHIF8FHaKF/7IJ1tg37g=; b=b6Q3I1qtmGy6PfPg8jM5XdU345bW5MtZQ34ixNBMWL5yG+CHpuISC6q3BQu75s2PL7 QT0n72kKV93Kc583fMRB1xhDx1yD4NOGjQ5/ySDhJSSFC9gQby6c/ZwcI/axF2ZwyKdc 1cKTNs4wHO6CedtIVvNhLXpCtOajevPk64lqUxkFa7YFxYfbTQoSNtxkqc8/d5T+7r7V 5vaBfyqqlrwYy4S3gh2cGWeMZmFftmuJ43AZH2+4L7OYZIQA4sb/5t5CPXmhHBjXXjRf jBQ9NREdtwIXkiLOAbEtiCmbbNCoRq191ZxyDLblA5din4OBnj37OAy7uzceFrumv4Zk dEUg== X-Gm-Message-State: APjAAAUidJxsiHRhil6Gaa2oYRbSKy+juOfTFVaN3qY8tKahQap3KAht S1PqCziTeSw9SFrJ4crxMgrrlwLg/teAIZ5qtyU= X-Google-Smtp-Source: APXvYqxdKlgQDAZd0rVz1kTCKAKz67KchoSC71iAsPkm5jnJvEjgH/isLw5WMmMNY34d+EOxbXv+L6gEn7PFmzsPuX0= X-Received: by 2002:a9d:469b:: with SMTP id z27mr3200209ote.11.1559058086922; Tue, 28 May 2019 08:41:26 -0700 (PDT) MIME-Version: 1.0 References: <4a6b0f1e-64ec-6b83-b43b-f9791ec8428f@metricspace.net> <1452db0c-1210-3230-c044-bc682e7e1745@metricspace.net> <3aa00c6b-2502-ffad-c915-a833292882bd@freebsd.org> <79c249c0-e6b0-a584-ad23-c9a4f57ff3c1@freebsd.org> In-Reply-To: From: Edward Napierala Date: Tue, 28 May 2019 16:41:15 +0100 Message-ID: Subject: Re: FreeBSD and Coreboot To: Eric McCorkle Cc: Warner Losh , Nathan Whitehorn , FreeBSD Hackers , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 2428185C89 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.90 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.90)[-0.903,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Tue, 28 May 2019 15:41:28 -0000 On Tue, 28 May 2019 at 12:17, Eric McCorkle wrote: [..] > > Now that the loader supports a ram disk, we are almost to something > > useful... but yea, almost and crummy often go hand in hand. > > This is looking out ahead of my current roadmap, but if you were to do a > kernel as the coreboot payload, there'd need to be some kind of trick to > support ZFS-only systems. > > ZFS requires modules, which are typically pre-loaded (and linked) by > loader (or GRUB). Coreboot has no disk or filesystem or even device > access facilities, however. It's just "pull an image out of flash, do > the bare essential hardware initialization to get to a C runtime > environment, then jump into the image". A ramdisk could help with that - boot with UFS-formatted ramdisk image as rootfs, have init(8) execute a script that loads zfs.ko and whatever other kernel module that's neccessary, and reroot into ZFS. From owner-freebsd-current@freebsd.org Tue May 28 22:01:10 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 174A515ADB25 for ; Tue, 28 May 2019 22:01:10 +0000 (UTC) (envelope-from delphij@gmail.com) Received: from mail-io1-xd41.google.com (mail-io1-xd41.google.com [IPv6:2607:f8b0:4864:20::d41]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 0CDF76D42E for ; Tue, 28 May 2019 22:01:09 +0000 (UTC) (envelope-from delphij@gmail.com) Received: by mail-io1-xd41.google.com with SMTP id f22so25829iol.11 for ; Tue, 28 May 2019 15:01:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ffAIOE7PQi3vQQnsptErGq6e3d2sr/g8zvtFuS+L8aM=; b=jqG0cGTUE3O9y6HZ1adqbtM2Zg0i3mAKG1/D4WWP5KYBvGRxA9B9Qjtw52oJbAf7u5 0Ib4gSxHDvI9zDh5o1LS4rVDiILkZuUrLnoDl/S/Zi2MtDXahaD5anN29ePEgKttURVo 5XI0iCVp/cgH8NY0GaVCMUVtbAQf5+lVr4i3Ka8lxMHje7idAqUObx/3lUnl3PeH+BtJ mQpQLgHHXsJyKfuZnX+kBuLIRX9WFVOts9VEYsNYYr0wGVe8yc30LoANtOWwvNwttVfu e0b/P++fR+hj0m9AZSGMvsTIT/7Zt95meF3RviAhHFdShfWznRF+jKC6xfbfXBCqOpjk p6TA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ffAIOE7PQi3vQQnsptErGq6e3d2sr/g8zvtFuS+L8aM=; b=HlGl+kVestFKF4inOg+1mtff3JdDmQ2thNKvR2rnYU59azC40vEiIL5UtXse9sItzu idNijpV8pCUjMT12590MghtGTt8lx7roJfdznWlZLhFi14VOoZgjomgZyIAcLXiYOuGq vsLGd70mHeUZWW9aqRNHNzlXhaQ5Vje4ADSDgetNZc/+CqnL/i5NkDFl9a6wuI8Lw3ih HaXe5dZN75jbYeMelhf9FrB8eXJgartprmmmkUzWp4ZyHOc8WoMwHIdlGIM3ziU0j34U SKriehYGIqzoPmqZHM1JVqujGzwdtsx/LRUdoX5vcqvOCJlFJKOia8NzRQa3zk54atM/ ngxg== X-Gm-Message-State: APjAAAW4uF+86hJDyts0rCdLwiMO9RazUgOafQEd2p5KbSdYlFPl3pLR 67m6zygWnnTOp3Aq02YohkV+9rT+SpnEoDfWnsSuLA== X-Google-Smtp-Source: APXvYqzwt16YXYtFLy0WIvlrNxo80PsTpYuTOXaomIBC6up2aVhPbs76hiXbjQmQEuuxkIDOoAEWJDo5srxA0o1Yqxo= X-Received: by 2002:a5d:9352:: with SMTP id i18mr16310762ioo.177.1559080867805; Tue, 28 May 2019 15:01:07 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Xin LI Date: Tue, 28 May 2019 15:00:54 -0700 Message-ID: Subject: Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option To: voidanix@420blaze.it Cc: FreeBSD Current X-Rspamd-Queue-Id: 0CDF76D42E X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=jqG0cGTU; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of delphij@gmail.com designates 2607:f8b0:4864:20::d41 as permitted sender) smtp.mailfrom=delphij@gmail.com X-Spamd-Result: default: False [-4.26 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.38)[-0.380,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[1.4.d.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-0.87)[ip: (1.29), ipnet: 2607:f8b0::/32(-3.30), asn: 15169(-2.29), country: US(-0.06)]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Tue, 28 May 2019 22:01:10 -0000 On Mon, May 27, 2019 at 7:08 AM wrote: > Hello, > I wanted to discuss about bug 231768 a bit: it is about keeping > COMPAT_FREEBSD4/5/6/7/9 on by default in the kernel configs. > > The patch attached for the bug is for disabling these options by > default, following a few reasons which I'm going to list here: > - Keeping support for deprecated libraries isn't exactly the best we > could do to avoid security issues (if there are any) as I'm sure nobody > wants to spend that much time maintaining such stuff (it's enough to > think about misc/compat4x in the ports tree: that version of FreeBSD was > released on March 2000 and keeping 19 years old libraries around isn't > ideal) > To accomplish this goal, a prerequisite would be to remove libc.a (possibly also libthr.a as well as anything that makes a direct system call). I'd rather see that happen first. > - Devs should get track of time and realize that developing software > using unsupported libraries is NOT something that you should do > - Only a tiny fraction of the ports need COMPAT_FREEBSD9 or older: > if the software won't compile without the legacy components (and has a > replacement of some kind), considering removal wouldn't be a bad idea > - This is on by default: most users don't care or don't use binaries > that old > > I don't see any practical reason to keep these options on by default, > but I do appreciate any sort of input regarding this issue. > Because users would find a way (e.g. by not upgrading) which further undermines their security? I know quite some Windows users would disable Windows Update for the exact same reason, if you break backward compatibility, your credibility is broken and it is much harder to regain the trust. Cheers, From owner-freebsd-current@freebsd.org Wed May 29 10:26:54 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5B20315BE677 for ; Wed, 29 May 2019 10:26:54 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lj1-f176.google.com (mail-lj1-f176.google.com [209.85.208.176]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 4F5458C811 for ; Wed, 29 May 2019 10:26:53 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lj1-f176.google.com with SMTP id o13so1895772lji.5 for ; Wed, 29 May 2019 03:26:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:cc:references:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=dXiag5VTzLEoyo4G4HDyUmgT9zRfpxlce4GD5iWOb8Y=; b=ciJaml7OGagRtuDCMTnKsld27sCNSBhDiPO56V93IuAqlNAhIrpBlGgkIUcFFOjLjz K4eRijv1uXPGiuA8L+VIJ4xD0TRZ1HIP1QZOGKSZHegGVQIrElmbjB9zc/BlwlSXOuRy shO1P5Y3OsZt1sq41A/X5uKEevVpP/hOwQfG2o+QN/b7Ek+tiVfg7BONETgApphOV6eK B3dGHdxD/QCqenZ2HGSV54O8fs+3uT6rhBIgyKTsmSPvV4Aljm36WtqMs2UiSl5x/hPN HrSel+2UtsWgTKUG3QSDa/6qsXrXGLYblnyaW+B/HtAk6CT49o7+7hRXRWFqchCYQsO1 U/EQ== X-Gm-Message-State: APjAAAUytAYEJcWiwBMGQ11hQXwtqEtzdBG+DnpzR+wb0HzfWWc9UH+z hFsuDIt9jOempoxk8LS7Wqy9DMC7 X-Google-Smtp-Source: APXvYqy7HivANeKCKONlA0IzCjuzezIDpMDowWDdQSUF/65QVe64FIMZSdsYc4TRWNLoZSQcwdNVvQ== X-Received: by 2002:a2e:88ce:: with SMTP id a14mr25405052ljk.122.1559125606124; Wed, 29 May 2019 03:26:46 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id u7sm3444485ljj.51.2019.05.29.03.26.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 May 2019 03:26:44 -0700 (PDT) Subject: Re: impossible to installkernel without a compiler? From: Andriy Gapon To: FreeBSD Current Cc: Warner Losh References: <5f15aa33-cd2f-da5a-9f9b-412f81467736@FreeBSD.org> <9d4c67c9-09ed-4dd4-bb0c-94df3c9ebcb2@FreeBSD.org> Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: Date: Wed, 29 May 2019 13:26:43 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <9d4c67c9-09ed-4dd4-bb0c-94df3c9ebcb2@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4F5458C811 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of agapon@gmail.com designates 209.85.208.176 as permitted sender) smtp.mailfrom=agapon@gmail.com X-Spamd-Result: default: False [-3.19 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.95)[-0.952,0]; FORGED_SENDER(0.30)[avg@FreeBSD.org,agapon@gmail.com]; IP_SCORE(-1.23)[ip: (-0.43), ipnet: 209.85.128.0/17(-3.37), asn: 15169(-2.29), country: US(-0.06)]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[avg@FreeBSD.org,agapon@gmail.com]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; SUBJECT_ENDS_QUESTION(1.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[FreeBSD.org]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[176.208.85.209.list.dnswl.org : 127.0.5.0]; RCVD_TLS_LAST(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[176.208.85.209.rep.mailspike.net : 127.0.0.17] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 29 May 2019 10:26:54 -0000 Just want to note that the problem extends to doing such things as "make aliases" in /etc/mail on a system installed without a compiler. I guess it would be nice if COMPILER_TYPE was enforced only when a compiler is actually needed. make can be used for more things than building C code. -- Andriy Gapon From owner-freebsd-current@freebsd.org Wed May 29 20:14:31 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CB34615AC187 for ; Wed, 29 May 2019 20:14:31 +0000 (UTC) (envelope-from unidef_rogue@live.com) Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-oln040092005036.outbound.protection.outlook.com [40.92.5.36]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 972D484E74 for ; Wed, 29 May 2019 20:14:29 +0000 (UTC) (envelope-from unidef_rogue@live.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=live.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/D2+NWo13KoYxHjQBZfa8X6+87OTdQeBl+p0CpF6IpM=; b=YFKKOyfqsjJ+IBGABaNzWhCXsctvxFoCy0RgmPZHz2BcvWy82q6H2yOpIlE0WrC1VYrQ7PPnWfUIWxqkfl+RMSjLt7t8Xtw6P7D/Zw+empYnmv0Ox1Zy2M5+L/Nc4mKegXxGJCiWRqJ7OnqUhriZUfc3DkuMU8g2IOF00C3uRbB1W9Zo2wC+VMTf6gxPT1NlDzLCzFsF/fHytuywcoou5fDAovIw7hMy8LI074TcNcuYMA00NA4Qe+hQzayIms9BKEeykzkEmgMzmbE9YL7oaMfIpGvnl197DO2+pHSCUx8DAB1nGPgkackqPhjdWFoRCVNmztUrdb0q2XcswyJ6Ug== Received: from BL2NAM02FT063.eop-nam02.prod.protection.outlook.com (10.152.76.59) by BL2NAM02HT135.eop-nam02.prod.protection.outlook.com (10.152.77.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1922.16; Wed, 29 May 2019 20:14:27 +0000 Received: from BYAPR02MB5704.namprd02.prod.outlook.com (10.152.76.51) by BL2NAM02FT063.mail.protection.outlook.com (10.152.77.121) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1922.16 via Frontend Transport; Wed, 29 May 2019 20:14:27 +0000 Received: from BYAPR02MB5704.namprd02.prod.outlook.com ([fe80::fcff:ed52:e519:9bf7]) by BYAPR02MB5704.namprd02.prod.outlook.com ([fe80::fcff:ed52:e519:9bf7%4]) with mapi id 15.20.1922.021; Wed, 29 May 2019 20:14:27 +0000 From: abhja kaanlani To: "freebsd-current@freebsd.org" Subject: Built in database for tcsh (dbcsh?) Thread-Topic: Built in database for tcsh (dbcsh?) Thread-Index: AQHVFlsdFnQBrpy4c0CDa2eDZtZBTQ== Date: Wed, 29 May 2019 20:14:26 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-incomingtopheadermarker: OriginalChecksum:5B0D46D69686F7C7958F57A9C46FF388AB1BD3592EF22CA34C6E6DA3D5031640; UpperCasedChecksum:C132EC7D4495C29064740778549B899923C466D7D8CB5C9A33B160A870F35CA9; SizeAsReceived:6701; Count:41 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [BPtBWOg0xh90Jk3p58jNgm3uHsKsilhmA1x3EJDBMKcQmBeg/aKWJ6Lo6pfKADFf] x-ms-publictraffictype: Email x-incomingheadercount: 41 x-eopattributedmessage: 0 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(5050001)(7020095)(20181119110)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031322404)(2017031323274)(2017031324274)(1601125500)(1603101475)(1701031045); SRVR:BL2NAM02HT135; x-ms-traffictypediagnostic: BL2NAM02HT135: x-ms-exchange-purlcount: 1 x-microsoft-antispam-message-info: autQZoMSMGTrOj74T2KG66pkpriqtNQBDdPJdLhxarYBGP2i86P8dYEAX0bhPAm2TfkVCYbiRToYcTbKP6ZgPaxxfQ2mdUDlLz2UUFqu8ngWgqXaOw0spMcMPz0NzlIc0VwZ9hnHPZlIZUJamnE7J7eplqQHJSKfPMv+39lBWgJukBHlShpErkjvPV2/xmO2 Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: live.com X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-Network-Message-Id: 20b0fb9b-f339-4dcc-2055-08d6e4724003 X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-originalarrivaltime: 29 May 2019 20:14:26.9825 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL2NAM02HT135 X-Rspamd-Queue-Id: 972D484E74 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=live.com header.s=selector1 header.b=YFKKOyfq; dmarc=pass (policy=none) header.from=live.com; spf=pass (mx1.freebsd.org: domain of unidef_rogue@live.com designates 40.92.5.36 as permitted sender) smtp.mailfrom=unidef_rogue@live.com X-Spamd-Result: default: False [-4.93 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[live.com:s=selector1]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:40.92.0.0/14]; FREEMAIL_FROM(0.00)[live.com]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[4]; IP_SCORE(-1.00)[ipnet: 40.64.0.0/10(-2.77), asn: 8075(-2.18), country: US(-0.06)]; DKIM_TRACE(0.00)[live.com:+]; DMARC_POLICY_ALLOW(-0.50)[live.com,none]; RCVD_IN_DNSWL_NONE(0.00)[36.5.92.40.list.dnswl.org : 127.0.3.0]; MX_GOOD(-0.01)[live-com.olc.protection.outlook.com,live-com.olc.protection.outlook.com]; TO_DN_EQ_ADDR_ALL(0.00)[]; NEURAL_HAM_SHORT(-0.92)[-0.918,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[live.com]; ASN(0.00)[asn:8075, ipnet:40.64.0.0/10, country:US]; RCVD_TLS_LAST(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[]; DWL_DNSWL_NONE(0.00)[live.com.dwl.dnswl.org : 127.0.3.0] X-Mailman-Approved-At: Wed, 29 May 2019 20:51:38 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 29 May 2019 20:14:32 -0000 Something that would creating a nice messaging system like in c++ or maybe = objc that would be transparent to hardware to end user I have some sample code of a mdmdbt on https://unidef.net Sent from my iPhone= From owner-freebsd-current@freebsd.org Wed May 29 22:35:29 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A0FA115AF6E1 for ; Wed, 29 May 2019 22:35:29 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 E2C9D8ABA8 for ; Wed, 29 May 2019 22:35:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x72e.google.com with SMTP id g18so2625916qkl.3 for ; Wed, 29 May 2019 15:35:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xghfP4Ig8OD8d0rPTWiudiWUtcZ0QwJFGmNH5A9zf/I=; b=XDsnOR9WQudF/bjX8k4t9Bod6np9Ug6zEsSWmn0uPvPVtug/5563GwfzvWN0WfxIqO zOTQhAKHszhxtiYbcH30uQoW5UvnyieWnolW1scIhJScAlnG/fHZuQQP7ciyit4alj7e FTdvC05mEQqLU9relIb5IREPsj10X80VGJ06cWm4W6csgkABgeKsB3f+lDSrdiXnKROZ IrDe+XBAcqIuODAi7A/geIyshs9g0iJ8tnK+G+njdnZ9NyVtrHlkrZnQtpf04CGzIxnI wkXkr4h6dVabBnQ4DWhNWwhVQkANHie2KzMOfkBslnlyEWQkibWnbMY69c4euMiDOsEA gejA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xghfP4Ig8OD8d0rPTWiudiWUtcZ0QwJFGmNH5A9zf/I=; b=K3b6yLE68HvcE0fN7CAUQ+p9uhTLLeEOgETFWd1N1PAJNVFeZgOLAgNVLGLI/n9pYj szE0Pm6PRbGuGVg3SL2KNHpet93kTvkoYTYRZTjbq8T9A4sHMWaQqteAigmEDmQNJ3uB C3nwt04UjcTgbS1JLjopOZ2ZCKgR6L665gKJqoQdw/J5Mw9qixjsEajJ327gIAZPHQoq 9Qfmkn2obmgWO//EaUpL640C5lIuQxeXoN8Ic+pr3S93x1uXrhIIDcbXP5pI/m6Mnl7O pCppj3G5Y+iJnJkkmd1UAfLp/+wr37MP44sbOadK8W9BQg/V4lhEQ5AVgthTClS5kOKC uRwA== X-Gm-Message-State: APjAAAVxWKorD9Vk6BwEBKvmr5YAySsnx6l141A/AvI2gZl+EDyU5H7c 8WU7uYLueSXt594kBQyWCrmDrBEztIyOqXMbDEBIiA== X-Google-Smtp-Source: APXvYqyIt4Nq/dX9cmQPcrteTEDnwpCvlwwhXX7IqyFNl1q296Jwkphdnp+gN16nHGCs+38gbC0CHoUrShaOskY0hg4= X-Received: by 2002:a37:4b48:: with SMTP id y69mr248296qka.77.1559169328238; Wed, 29 May 2019 15:35:28 -0700 (PDT) MIME-Version: 1.0 References: <5f15aa33-cd2f-da5a-9f9b-412f81467736@FreeBSD.org> <9d4c67c9-09ed-4dd4-bb0c-94df3c9ebcb2@FreeBSD.org> In-Reply-To: From: Warner Losh Date: Wed, 29 May 2019 16:35:17 -0600 Message-ID: Subject: Re: impossible to installkernel without a compiler? To: Andriy Gapon Cc: FreeBSD Current X-Rspamd-Queue-Id: E2C9D8ABA8 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=XDsnOR9W X-Spamd-Result: default: False [-4.95 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_SHORT(-0.92)[-0.919,0]; IP_SCORE(-3.02)[ip: (-9.42), ipnet: 2607:f8b0::/32(-3.32), asn: 15169(-2.30), country: US(-0.06)]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; 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)[e.2.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; MX_GOOD(-0.01)[cached: ALT1.aspmx.l.google.com]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+,1:+]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 29 May 2019 22:35:29 -0000 There's already a list of targets to except... It's hard to have an opt-in list, however :( Warner On Wed, May 29, 2019 at 4:26 AM Andriy Gapon wrote: > > Just want to note that the problem extends to doing such things as "make > aliases" in /etc/mail on a system installed without a compiler. > > I guess it would be nice if COMPILER_TYPE was enforced only when a > compiler is > actually needed. make can be used for more things than building C code. > > > -- > Andriy Gapon > From owner-freebsd-current@freebsd.org Wed May 29 20:59:11 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3FA3F15AD7FD for ; Wed, 29 May 2019 20:59:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B5A7D87570 for ; Wed, 29 May 2019 20:59:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 7979C15AD7FA; Wed, 29 May 2019 20:59:10 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 67EAC15AD7F9 for ; Wed, 29 May 2019 20:59:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 068488756C for ; Wed, 29 May 2019 20:59:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 391E21C022 for ; Wed, 29 May 2019 20:59:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x4TKx9u3029689 for ; Wed, 29 May 2019 20:59:09 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4TKx9h6029688 for current@FreeBSD.org; Wed, 29 May 2019 20:59:09 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 197921] [patch] [sched] Allow non-migratable threads to bind to their current CPU. Date: Wed, 29 May 2019 20:59:08 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: needs-qa, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emaste@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Wed, 29 May 2019 22:56:42 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 29 May 2019 20:59:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D197921 Ed Maste changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emaste@freebsd.org --- Comment #1 from Ed Maste --- + } + else {=20=20 should be: } else { but, what about just moving the KASSERT after the `if (PCPU_GET(cpuid) =3D= =3D cpu)` test? --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-current@freebsd.org Thu May 30 01:42:26 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B9F515B3A7F for ; Thu, 30 May 2019 01:42:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 30DAD6A024 for ; Thu, 30 May 2019 01:42:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id E57EF15B3A7C; Thu, 30 May 2019 01:42:25 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2EAD15B3A79 for ; Thu, 30 May 2019 01:42:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6AFAF6A01F for ; Thu, 30 May 2019 01:42:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id B23C41E98A for ; Thu, 30 May 2019 01:42:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x4U1gOuC077111 for ; Thu, 30 May 2019 01:42:24 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4U1gO7K077110 for current@FreeBSD.org; Thu, 30 May 2019 01:42:24 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 197921] scheduler: Allow non-migratable threads to bind to their current CPU Date: Thu, 30 May 2019 01:42:24 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: needs-patch, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? mfc-stable12? X-Bugzilla-Changed-Fields: keywords short_desc bug_status flagtypes.name Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 30 May 2019 03:27:32 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Thu, 30 May 2019 01:42:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D197921 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|patch |needs-patch Summary|[patch] [sched] Allow |scheduler: Allow |non-migratable threads to |non-migratable threads to |bind to their current CPU. |bind to their current CPU Status|New |Open Flags| |mfc-stable11?, | |mfc-stable12? --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-current@freebsd.org Thu May 30 11:47:26 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD49415BF3D1 for ; Thu, 30 May 2019 11:47:26 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:300:2185:123::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1CF9384CF9 for ; Thu, 30 May 2019 11:47:25 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [104.207.135.49]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id x4UBlOEo088262 for ; Thu, 30 May 2019 12:47:24 +0100 (BST) (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id x4UBlOOp088261 for freebsd-current@freebsd.org; Thu, 30 May 2019 12:47:24 +0100 (BST) (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <201905301147.x4UBlOOp088261@donotpassgo.dyslexicfish.net> Date: Thu, 30 May 2019 12:47:24 +0100 Organization: Dyslexic Fish To: freebsd-current@freebsd.org Subject: FreeBSD contrib/one-true-awk now it's own fork? User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [104.207.135.49]); Thu, 30 May 2019 12:47:24 +0100 (BST) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Thu, 30 May 2019 11:47:26 -0000 contrib/one-true-awk hasn't been synced with the official src maintained by Brian Kernighan for a number of years, though in that time a number of FreeBSD changes have been made, independently of the official branch. Is this the official policy now? There are some useful bugfixes and changes out there! - https://github.com/onetrueawk/awk cheers From owner-freebsd-current@freebsd.org Thu May 30 13:20:20 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0E7315C24CF for ; Thu, 30 May 2019 13:20:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 B4E9789371 for ; Thu, 30 May 2019 13:20:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x730.google.com with SMTP id g18so3817519qkl.3 for ; Thu, 30 May 2019 06:20:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0dFUjRPhDcnC40MJoQZ9NleuQiESMwhndE7b0I+dkuE=; b=lvNdWEneSrgJu/yusGVkwjNOIGW3oFwVY3LgZv4bSPsDW6mhKU8nPy/pJdsN11NFB5 psnPNIl/MwsCdiryuTuGw5ZQ2Pwk5K/V1PvUx787tb81flcdCzKQ/g02FarSjwBb3I86 dey3CkOOoow5yhP5DPzar20UH/jEByFZ3jlXqzgZhQvXaNV/mrcVzXiDyEZMLsldBO9K b7lnAIrVgqPDQ/O6Hy1uyxPsz5hm32jUf+oh1tbuqu52jGdaK7f6T796cMcCYbtILD02 /+LZ3xEzl+4zdvB372nSUvjuHb65ijhQbSL0o9x4iTP3w3y69Ap9pabYmw5ZgSTgJdNt BzFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0dFUjRPhDcnC40MJoQZ9NleuQiESMwhndE7b0I+dkuE=; b=uEUfduxobMvE4xvaK0MrGQj+ATegBrqjx6RZbuMcuCpA3L25t0+tyC1DTlRS68hnGO ycvAiaWGDaDFND9t4mrgZfph+cR2tSwNXJPyS30t0yxv3vtMO3AZAYYgEj50deHb5N1V pcoDTVWzliKD/NV5OUo+x2gXkcvmQAy9bT9ZKrNPOYtxWhzznLkDwVJ6VW+bOOoF1pyN X8dsldc/X3OYK+C6/CldIp3f2rHSGXnKuQCg3RyRF300PY7l9tHY6XC9sR8//QA+O8m7 wrK07CKzbLMRaimS3+lAG89nMrqMhr948YKtQB3gLEZchEscXuY9APzuZelP5TdyNkwR WfyQ== X-Gm-Message-State: APjAAAU9ujnI6QCUTGvCHaINFIz5A3Uigo0X1LN+mPoXyDPbvixzF0Es FX6MXFIYz5zCJ7Utq8+3Dlx+AX4jfsaXfsRudilbEPUp X-Google-Smtp-Source: APXvYqz15QPjB9288aXU5/rZJE8065PPK2vZg7mITuKSyqnnl0y7YxkH5k+8nPJXEElPxEcn5dThs6+kZZ6RKokMgaI= X-Received: by 2002:a05:620a:1384:: with SMTP id k4mr3139700qki.69.1559222418934; Thu, 30 May 2019 06:20:18 -0700 (PDT) MIME-Version: 1.0 References: <201905301147.x4UBlOOp088261@donotpassgo.dyslexicfish.net> In-Reply-To: <201905301147.x4UBlOOp088261@donotpassgo.dyslexicfish.net> From: Warner Losh Date: Thu, 30 May 2019 07:20:06 -0600 Message-ID: Subject: Re: FreeBSD contrib/one-true-awk now it's own fork? To: Jamie Landeg-Jones Cc: FreeBSD Current X-Rspamd-Queue-Id: B4E9789371 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.985,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Thu, 30 May 2019 13:20:20 -0000 On Thu, May 30, 2019, 5:48 AM Jamie Landeg-Jones wrote: > contrib/one-true-awk hasn't been synced with the official src maintained > by Brian Kernighan for a number of years, though in that time a number > of FreeBSD changes have been made, independently of the official branch. > > Is this the official policy now? There are some useful bugfixes and changes > out there! - https://github.com/onetrueawk/awk I updated things a while ago, but hit some snags getting them in. At the time, upstream was dormant. I'll take another run at it. Warner > cheers > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Thu May 30 15:31:48 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A59A515C5797 for ; Thu, 30 May 2019 15:31:48 +0000 (UTC) (envelope-from johalun@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1237190D21 for ; Thu, 30 May 2019 15:31:48 +0000 (UTC) (envelope-from johalun@FreeBSD.org) Received: from [10.46.14.95] (wsip-72-212-151-146.ph.ph.cox.net [72.212.151.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: johalun) by smtp.freebsd.org (Postfix) with ESMTPSA id A4BBB95C0 for ; Thu, 30 May 2019 15:31:47 +0000 (UTC) (envelope-from johalun@FreeBSD.org) To: FreeBSD Current From: Johannes Lundberg Subject: Inconsistent behavior with wpa / devd / network interfaces Message-ID: Date: Thu, 30 May 2019 08:31:45 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 1237190D21 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.96 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.96)[-0.960,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Thu, 30 May 2019 15:31:48 -0000 Hi I have a bridge and an ethernet/wifi lagg failover like this: # First define all cloned interfaces cloned_interfaces="bridge0 lagg0" # bhyve bridge ifconfig_bridge0="inet 192.168.8.1/24 addm lagg0 up" # Ethernet/WiFi failvoer ifconfig_em0="up" wlans_iwm0="wlan0" ifconfig_wlan0="WPA up" create_args_wlan0="wlanaddr xx:xx:xx:xx:xx:xx" ifconfig_lagg0="laggproto failover laggport em0 laggport wlan0 DHCP up" When I move between home and work networks and plug in the network cable it sometimes reconfigure and sometimes (mostly) not. Looking at devd output from a failed occasion and I can see that it calls dhclient on em0 and not lagg0. But it since it works sometimes I don't know if this is correct or not (I would expect lagg0 and not em0 but manually running this command with either em0 or lagg0 doesn't do anything)... devd log: Executing 'service dhclient quietstart $'em0'' In addition to this, I often have to run ifconfig wlan0 scan (or service netif restart) or to have the it reconnect to a different wifi. It doesn't seem to be doing any periodical scanning and reconnecting at all (but maybe that's a different issue). For sometime now I usually have to run service netif restart to get network working after switching location, followed by adding all my VM tap interfaces to the bridge manually, and restarting bhyve guests because they lose connectivity.. It's getting a bit tiring and I would like to find a solution. Do I have something weird in my setup causing this? I don't recall ever having this issue when not using failover lagg. Running recent 13-CURRENT. Thanks! /Johannes From owner-freebsd-current@freebsd.org Thu May 30 16:37:53 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0DF8E15C6E33 for ; Thu, 30 May 2019 16:37:53 +0000 (UTC) (envelope-from gcr+freebsd-current@tharned.org) Received: from roadkill.tharned.org (tunnel294749-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:107f::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "tharned.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A9AE93531; Thu, 30 May 2019 16:37:52 +0000 (UTC) (envelope-from gcr+freebsd-current@tharned.org) Received: from flake.tharned.org ([IPv6:2001:470:1f11:107f:fc23:b4f4:b79d:a329]) (authenticated bits=0) by roadkill.tharned.org (8.15.2/8.15.2) with ESMTPSA id x4UGboMl091297 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 30 May 2019 11:37:51 -0500 (CDT) (envelope-from gcr+freebsd-current@tharned.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tharned.org; s=2017; t=1559234271; bh=e6XlN0raQes/7Z3tKXtfESz1zw3jSyh7fDp1scOTzvs=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=HDX6DHP5Bjli551uB+H3Kb6KJth2RT5OReNXfQg2x/cTpaN4h3Jz7oj0JOF51rW6w rwd4ry7ecZ4tj486NwnWr+SZafIYxIfKqUE8/qYeAwPcjhC7XHIJOsM87qLK7tVmbp Kig2lF6rFH1q8tD87tpnwE62TVbpu+8dC71j/rnHjrfXqk7Qar8N1WmFY0n6RviidT rFAQ73K6cxRPKX6YRu6tEzTCMxcpVdpJyT4qxX4fYa4hJXhwRJl7owBF6yEpFGyodP qJlYkqSQOkSRYAmPrpZ2VOhqxDxuVuJSP8kO+Xc1ssMbdos05Sk4jX5dlqureN0CBq VrHZC5i6ZW6Pw== X-Authentication-Warning: roadkill.tharned.org: Host [IPv6:2001:470:1f11:107f:fc23:b4f4:b79d:a329] claimed to be flake.tharned.org From: Greg Rivers To: freebsd-current@freebsd.org Cc: Johannes Lundberg Subject: Re: Inconsistent behavior with wpa / devd / network interfaces Date: Thu, 30 May 2019 11:37:50 -0500 Message-ID: <2836877.0P3pStmDMi@no.place.like.home> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (roadkill.tharned.org [IPv6:2001:470:1f10:107f:0:0:0:2]); Thu, 30 May 2019 11:37:51 -0500 (CDT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Thu, 30 May 2019 16:37:53 -0000 On Thursday, May 30, 2019 10:31:45 AM CDT Johannes Lundberg wrote: > Hi > > I have a bridge and an ethernet/wifi lagg failover like this: > > # First define all cloned interfaces > cloned_interfaces="bridge0 lagg0" > > # bhyve bridge > ifconfig_bridge0="inet 192.168.8.1/24 addm lagg0 up" > > # Ethernet/WiFi failvoer > ifconfig_em0="up" > wlans_iwm0="wlan0" > ifconfig_wlan0="WPA up" > create_args_wlan0="wlanaddr xx:xx:xx:xx:xx:xx" > ifconfig_lagg0="laggproto failover laggport em0 laggport wlan0 DHCP up" > > When I move between home and work networks and plug in the network cable > it sometimes reconfigure and sometimes (mostly) not. Looking at devd > output from a failed occasion and I can see that it calls dhclient on > em0 and not lagg0. But it since it works sometimes I don't know if this > is correct or not (I would expect lagg0 and not em0 but manually running > this command with either em0 or lagg0 doesn't do anything)... > > devd log: Executing 'service dhclient quietstart $'em0'' > > In addition to this, I often have to run ifconfig wlan0 scan (or service > netif restart) or to have the it reconnect to a different wifi. It > doesn't seem to be doing any periodical scanning and reconnecting at all > (but maybe that's a different issue). > > For sometime now I usually have to run service netif restart to get > network working after switching location, followed by adding all my VM > tap interfaces to the bridge manually, and restarting bhyve guests > because they lose connectivity.. It's getting a bit tiring and I would > like to find a solution. > > Do I have something weird in my setup causing this? I don't recall ever > having this issue when not using failover lagg. Running recent 13-CURRENT. > I think there's a (unknown?) problem that makes lagg(4) incompatible with bridge(4). I've never been unable to make a lagg interface work as a member of a bridge. Lacking the time to pursue it, I've resorted to NATing instead. Also, wlan interfaces tend to break if you change their MAC address. So in a lagg consisting of a wlan interface and a ethernet interface (without a bridge), I always set the MAC of the ethernet to match the native MAC of the wlan, and not vice versa. -- Greg From owner-freebsd-current@freebsd.org Thu May 30 17:22:27 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 116DA15A5865 for ; Thu, 30 May 2019 17:22:27 +0000 (UTC) (envelope-from johalun@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A9843954F4; Thu, 30 May 2019 17:22:26 +0000 (UTC) (envelope-from johalun@FreeBSD.org) Received: from [10.46.14.95] (wsip-72-212-151-146.ph.ph.cox.net [72.212.151.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: johalun) by smtp.freebsd.org (Postfix) with ESMTPSA id 408C6A3F7; Thu, 30 May 2019 17:22:26 +0000 (UTC) (envelope-from johalun@FreeBSD.org) Subject: Re: Inconsistent behavior with wpa / devd / network interfaces To: Greg Rivers , freebsd-current@freebsd.org References: <2836877.0P3pStmDMi@no.place.like.home> From: Johannes Lundberg X-Tagtoolbar-Keys: D20190530102224943 Message-ID: <85a5bf45-231e-1bb4-4c26-677e414af96f@FreeBSD.org> Date: Thu, 30 May 2019 10:22:24 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <2836877.0P3pStmDMi@no.place.like.home> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: A9843954F4 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.993,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[freebsd-current]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Thu, 30 May 2019 17:22:27 -0000 On 5/30/19 9:37 AM, Greg Rivers wrote: > On Thursday, May 30, 2019 10:31:45 AM CDT Johannes Lundberg wrote: >> Hi >> >> I have a bridge and an ethernet/wifi lagg failover like this: >> >> # First define all cloned interfaces >> cloned_interfaces="bridge0 lagg0" >> >> # bhyve bridge >> ifconfig_bridge0="inet 192.168.8.1/24 addm lagg0 up" >> >> # Ethernet/WiFi failvoer >> ifconfig_em0="up" >> wlans_iwm0="wlan0" >> ifconfig_wlan0="WPA up" >> create_args_wlan0="wlanaddr xx:xx:xx:xx:xx:xx" >> ifconfig_lagg0="laggproto failover laggport em0 laggport wlan0 DHCP up" >> >> When I move between home and work networks and plug in the network cable >> it sometimes reconfigure and sometimes (mostly) not. Looking at devd >> output from a failed occasion and I can see that it calls dhclient on >> em0 and not lagg0. But it since it works sometimes I don't know if this >> is correct or not (I would expect lagg0 and not em0 but manually running >> this command with either em0 or lagg0 doesn't do anything)... >> >> devd log: Executing 'service dhclient quietstart $'em0'' >> >> In addition to this, I often have to run ifconfig wlan0 scan (or service >> netif restart) or to have the it reconnect to a different wifi. It >> doesn't seem to be doing any periodical scanning and reconnecting at all >> (but maybe that's a different issue). >> >> For sometime now I usually have to run service netif restart to get >> network working after switching location, followed by adding all my VM >> tap interfaces to the bridge manually, and restarting bhyve guests >> because they lose connectivity.. It's getting a bit tiring and I would >> like to find a solution. >> >> Do I have something weird in my setup causing this? I don't recall ever >> having this issue when not using failover lagg. Running recent 13-CURRENT. >> > I think there's a (unknown?) problem that makes lagg(4) incompatible with > bridge(4). I've never been unable to make a lagg interface work as a member of > a bridge. Lacking the time to pursue it, I've resorted to NATing instead. > > Also, wlan interfaces tend to break if you change their MAC address. So in a > lagg consisting of a wlan interface and a ethernet interface (without a > bridge), I always set the MAC of the ethernet to match the native MAC of the > wlan, and not vice versa. > Hi Thanks for the reply! I could try to reverse the MAC address setting to see if that helps. I'm also running NAT like this for bhyve guests % cat /etc/pf.conf nat on lagg0 from {192.168.8.0/24} to any -> (lagg0) The "bhyve bridge" bridge0's members are lagg0 and the tapX interfaces. This setup works great as long as external connection doesn't change. I have full connectivity between host<->guests and guests can access internet as well (with seamless switching between ethernet/wifi *). The bhyve guests are configured with static IP addresses 192.168.8.X. * Sometimes seamless, sometimes not so much... From owner-freebsd-current@freebsd.org Thu May 30 19:38:08 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C96F15A8F5F for ; Thu, 30 May 2019 19:38:08 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A363F6B12A; Thu, 30 May 2019 19:38:06 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id WQsDhAFxDGusjWQsEhMI33; Thu, 30 May 2019 13:38:04 -0600 X-Authority-Analysis: v=2.3 cv=fOdHIqSe c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=kj9zAlcOel0A:10 a=E5NmQfObTbMA:10 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=uAulVrp6mufAFwu96jAA:9 a=UJXRCHpk5MLBRmAW:21 a=_FIolvARWdt5fk_x:21 a=CjuIK1q_8ugA:10 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from slippy.cwsent.com (slippy8 [10.2.2.6]) by spqr.komquats.com (Postfix) with ESMTPS id EF086E37; Thu, 30 May 2019 12:37:59 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id x4UJbxfE065143; Thu, 30 May 2019 12:37:59 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id x4UJbxtB065140; Thu, 30 May 2019 12:37:59 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201905301937.x4UJbxtB065140@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Johannes Lundberg cc: Greg Rivers , freebsd-current@freebsd.org Subject: Re: Inconsistent behavior with wpa / devd / network interfaces In-Reply-To: Message from Johannes Lundberg of "Thu, 30 May 2019 10:22:24 -0700." <85a5bf45-231e-1bb4-4c26-677e414af96f@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 May 2019 12:37:59 -0700 X-CMAE-Envelope: MS4wfCsc5MBqZkjiLYuSGfZfdFRjQ0duJ/ftxChomfa0oj6n9xBy6+nELVqd0A8EgLjs2SDFG6qVoKf7ufMANnEWAgHesksltPwIxDn+eSy13y3QF6Kn3Dmg J4e4qu7NG5UEUvqlyy/XfwqE7LDBNAEYNC+y9We2amwoArp8Ea+YiCt/3CB18ujvyL13eMLRT303Hr3kO90YncXIJDVl2pzOGQ/6lw6ZDGlVPif79ObofbuK hUuu8L1VidamBOViQRamzzAzTTJQJqcicjc6ejLmqs8= X-Rspamd-Queue-Id: A363F6B12A X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-5.07 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[Cy.Schubert@cschubert.com]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; HAS_XAW(0.00)[]; MX_GOOD(-0.01)[cached: spqr.komquats.com]; NEURAL_HAM_SHORT(-0.98)[-0.980,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[139.136.59.64.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; MIME_TRACE(0.00)[0:+]; RECEIVED_SPAMHAUS_PBL(0.00)[17.125.67.70.zen.spamhaus.org : 127.0.0.11]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; RCVD_COUNT_FIVE(0.00)[5]; REPLYTO_EQ_FROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[freebsd-current]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[]; IP_SCORE(-2.38)[ip: (-6.05), ipnet: 64.59.128.0/20(-3.26), asn: 6327(-2.52), country: CA(-0.09)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Thu, 30 May 2019 19:38:08 -0000 In message <85a5bf45-231e-1bb4-4c26-677e414af96f@FreeBSD.org>, Johannes Lundber g writes: > > On 5/30/19 9:37 AM, Greg Rivers wrote: > > On Thursday, May 30, 2019 10:31:45 AM CDT Johannes Lundberg wrote: > >> Hi > >> > >> I have a bridge and an ethernet/wifi lagg failover like this: > >> > >> # First define all cloned interfaces > >> cloned_interfaces="bridge0 lagg0" > >> > >> # bhyve bridge > >> ifconfig_bridge0="inet 192.168.8.1/24 addm lagg0 up" > >> > >> # Ethernet/WiFi failvoer > >> ifconfig_em0="up" > >> wlans_iwm0="wlan0" > >> ifconfig_wlan0="WPA up" > >> create_args_wlan0="wlanaddr xx:xx:xx:xx:xx:xx" > >> ifconfig_lagg0="laggproto failover laggport em0 laggport wlan0 DHCP up" > >> > >> When I move between home and work networks and plug in the network cable > >> it sometimes reconfigure and sometimes (mostly) not. Looking at devd > >> output from a failed occasion and I can see that it calls dhclient on > >> em0 and not lagg0. But it since it works sometimes I don't know if this > >> is correct or not (I would expect lagg0 and not em0 but manually running > >> this command with either em0 or lagg0 doesn't do anything)... > >> > >> devd log: Executing 'service dhclient quietstart $'em0'' > >> > >> In addition to this, I often have to run ifconfig wlan0 scan (or service > >> netif restart) or to have the it reconnect to a different wifi. It > >> doesn't seem to be doing any periodical scanning and reconnecting at all > >> (but maybe that's a different issue). > >> > >> For sometime now I usually have to run service netif restart to get > >> network working after switching location, followed by adding all my VM > >> tap interfaces to the bridge manually, and restarting bhyve guests > >> because they lose connectivity.. It's getting a bit tiring and I would > >> like to find a solution. > >> > >> Do I have something weird in my setup causing this? I don't recall ever > >> having this issue when not using failover lagg. Running recent 13-CURRENT. > >> > > I think there's a (unknown?) problem that makes lagg(4) incompatible with > > bridge(4). I've never been unable to make a lagg interface work as a member > of > > a bridge. Lacking the time to pursue it, I've resorted to NATing instead. > > > > Also, wlan interfaces tend to break if you change their MAC address. So in > a > > lagg consisting of a wlan interface and a ethernet interface (without a > > bridge), I always set the MAC of the ethernet to match the native MAC of th > e > > wlan, and not vice versa. > > > Hi > > Thanks for the reply! I could try to reverse the MAC address setting to > see if that helps. > > I'm also running NAT like this for bhyve guests > > % cat /etc/pf.conf > nat on lagg0 from {192.168.8.0/24} to any -> (lagg0) > > The "bhyve bridge" bridge0's members are lagg0 and the tapX interfaces. > This setup works great as long as external connection doesn't change. I > have full connectivity between host<->guests and guests can access > internet as well (with seamless switching between ethernet/wifi *). The > bhyve guests are configured with static IP addresses 192.168.8.X. > > * Sometimes seamless, sometimes not so much... I use a similar configuration except to use $cloned_interfaces. The caveat is, if on the same network switching from wired to wireless and back again is seamless. However if the wired and wireless networks are on different segments, because dhclient isn't recycled one needs to restart dhclient manually. The problem is that when switching from wired to wireless or back you are on another network, there is no way to know what network you're on until dhclient is killed and restarted. OK, so we automatically restart dhclient every time then: Problem: this is highly disruptive when you happen to be connected to the same network don't need dhclient restarted but is restarted anyway, e.g. the network address is the same. The trade-off is take a hit every time there is a reconnect and leave it to the user to do what is best. Example: I use one of my networks is no problem but use my wife's wireless network on a different segment there is a problem. A laptop doesn't know what network it's on merely by associating to a network. Sure, this can be scripted but that opens another can of worms, that being any solution would be site-specific to one degree or another. Regardless, changing the behaviour would be a POLA violation, unless the behaviour is a user selectable option. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Thu May 30 20:10:57 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 31DF615A97EA for ; Thu, 30 May 2019 20:10:57 +0000 (UTC) (envelope-from johalun@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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BE5106BEF9; Thu, 30 May 2019 20:10:56 +0000 (UTC) (envelope-from johalun@FreeBSD.org) Received: from [10.46.14.144] (wsip-72-212-151-146.ph.ph.cox.net [72.212.151.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: johalun) by smtp.freebsd.org (Postfix) with ESMTPSA id 3E17BB6CC; Thu, 30 May 2019 20:10:56 +0000 (UTC) (envelope-from johalun@FreeBSD.org) Subject: Re: Inconsistent behavior with wpa / devd / network interfaces To: Cy Schubert Cc: Greg Rivers , freebsd-current@freebsd.org References: <201905301937.x4UJbxtB065140@slippy.cwsent.com> From: Johannes Lundberg X-Tagtoolbar-Keys: D20190530131054840 Message-ID: Date: Thu, 30 May 2019 13:10:54 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <201905301937.x4UJbxtB065140@slippy.cwsent.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: BE5106BEF9 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.91 / 15.00]; TAGGED_RCPT(0.00)[freebsd-current]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_SHORT(-0.91)[-0.907,0]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; ASN(0.00)[asn:11403, ipnet:96.47.64.0/20, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Thu, 30 May 2019 20:10:57 -0000 On 5/30/19 12:37 PM, Cy Schubert wrote: > In message <85a5bf45-231e-1bb4-4c26-677e414af96f@FreeBSD.org>, Johannes > Lundber > g writes: >> On 5/30/19 9:37 AM, Greg Rivers wrote: >>> On Thursday, May 30, 2019 10:31:45 AM CDT Johannes Lundberg wrote: >>>> Hi >>>> >>>> I have a bridge and an ethernet/wifi lagg failover like this: >>>> >>>> # First define all cloned interfaces >>>> cloned_interfaces="bridge0 lagg0" >>>> >>>> # bhyve bridge >>>> ifconfig_bridge0="inet 192.168.8.1/24 addm lagg0 up" >>>> >>>> # Ethernet/WiFi failvoer >>>> ifconfig_em0="up" >>>> wlans_iwm0="wlan0" >>>> ifconfig_wlan0="WPA up" >>>> create_args_wlan0="wlanaddr xx:xx:xx:xx:xx:xx" >>>> ifconfig_lagg0="laggproto failover laggport em0 laggport wlan0 DHCP up" >>>> >>>> When I move between home and work networks and plug in the network cable >>>> it sometimes reconfigure and sometimes (mostly) not. Looking at devd >>>> output from a failed occasion and I can see that it calls dhclient on >>>> em0 and not lagg0. But it since it works sometimes I don't know if this >>>> is correct or not (I would expect lagg0 and not em0 but manually running >>>> this command with either em0 or lagg0 doesn't do anything)... >>>> >>>> devd log: Executing 'service dhclient quietstart $'em0'' >>>> >>>> In addition to this, I often have to run ifconfig wlan0 scan (or service >>>> netif restart) or to have the it reconnect to a different wifi. It >>>> doesn't seem to be doing any periodical scanning and reconnecting at all >>>> (but maybe that's a different issue). >>>> >>>> For sometime now I usually have to run service netif restart to get >>>> network working after switching location, followed by adding all my VM >>>> tap interfaces to the bridge manually, and restarting bhyve guests >>>> because they lose connectivity.. It's getting a bit tiring and I would >>>> like to find a solution. >>>> >>>> Do I have something weird in my setup causing this? I don't recall ever >>>> having this issue when not using failover lagg. Running recent 13-CURRENT. >>>> >>> I think there's a (unknown?) problem that makes lagg(4) incompatible with >>> bridge(4). I've never been unable to make a lagg interface work as a member >> of >>> a bridge. Lacking the time to pursue it, I've resorted to NATing instead. >>> >>> Also, wlan interfaces tend to break if you change their MAC address. So in >> a >>> lagg consisting of a wlan interface and a ethernet interface (without a >>> bridge), I always set the MAC of the ethernet to match the native MAC of th >> e >>> wlan, and not vice versa. >>> >> Hi >> >> Thanks for the reply! I could try to reverse the MAC address setting to >> see if that helps. >> >> I'm also running NAT like this for bhyve guests >> >> % cat /etc/pf.conf >> nat on lagg0 from {192.168.8.0/24} to any -> (lagg0) >> >> The "bhyve bridge" bridge0's members are lagg0 and the tapX interfaces. >> This setup works great as long as external connection doesn't change. I >> have full connectivity between host<->guests and guests can access >> internet as well (with seamless switching between ethernet/wifi *). The >> bhyve guests are configured with static IP addresses 192.168.8.X. >> >> * Sometimes seamless, sometimes not so much... > I use a similar configuration except to use $cloned_interfaces. > > The caveat is, if on the same network switching from wired to wireless > and back again is seamless. However if the wired and wireless networks > are on different segments, because dhclient isn't recycled one needs to > restart dhclient manually. > > The problem is that when switching from wired to wireless or back you > are on another network, there is no way to know what network you're on > until dhclient is killed and restarted. > > OK, so we automatically restart dhclient every time then: Problem: this > is highly disruptive when you happen to be connected to the same > network don't need dhclient restarted but is restarted anyway, e.g. the > network address is the same. The trade-off is take a hit every time > there is a reconnect and leave it to the user to do what is best. > Example: I use one of my networks is no problem but use my wife's > wireless network on a different segment there is a problem. A laptop > doesn't know what network it's on merely by associating to a network. > Sure, this can be scripted but that opens another can of worms, that > being any solution would be site-specific to one degree or another. > > Regardless, changing the behaviour would be a POLA violation, unless > the behaviour is a user selectable option. > Thanks! That makes sense. At work they are different segments I think, but at home it's the same. It wouldn't be so bad if I could just restart dhclient but often nothing but 'service netif restart' helps. It's like it locked up somewhere... Maybe the solution is not to use lagg at all, but have wlan and em connected at the same time with separate ip addresses and a script that set default route to that of the wlan when unplugging ethernet (and override it when plugged in).. From owner-freebsd-current@freebsd.org Thu May 30 20:25:29 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4EDE315A9CB5 for ; Thu, 30 May 2019 20:25:29 +0000 (UTC) (envelope-from SRS0=kAX8=T6=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C3D506C4E6 for ; Thu, 30 May 2019 20:25:28 +0000 (UTC) (envelope-from SRS0=kAX8=T6=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 8B58D28411; Thu, 30 May 2019 22:25:25 +0200 (CEST) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 3B09A28422; Thu, 30 May 2019 22:25:23 +0200 (CEST) Subject: Re: Inconsistent behavior with wpa / devd / network interfaces To: Greg Rivers , freebsd-current@freebsd.org References: <2836877.0P3pStmDMi@no.place.like.home> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: Date: Thu, 30 May 2019 22:25:22 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <2836877.0P3pStmDMi@no.place.like.home> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: C3D506C4E6 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[freebsd-current]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.991,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Thu, 30 May 2019 20:25:29 -0000 Greg Rivers wrote on 2019/05/30 18:37: [...] >> Do I have something weird in my setup causing this? I don't recall ever >> having this issue when not using failover lagg. Running recent 13-CURRENT. >> > I think there's a (unknown?) problem that makes lagg(4) incompatible with > bridge(4). I've never been unable to make a lagg interface work as a member of > a bridge. Lacking the time to pursue it, I've resorted to NATing instead. lagg and bridge can work together. I am running machine with FreeBSD 11.2 with 2 Intel NICs: em0 and em1 combined in to lagg0 lagg0 has 4 static IP addresses There is also bhyve VM on tap20, this VM has another 2 static IP addresses tap20 and lagg0 are members of the bridge. This bridge is renamed to "vm-public" vm-public: flags=8843 metric 0 mtu 1500 ether da:ae:ba:75:53:ce nd6 options=1 groups: bridge vm-switch viid-4c918@ id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: tap20 flags=143 ifmaxaddr 0 port 5 priority 128 path cost 2000000 member: lagg0 flags=143 ifmaxaddr 0 port 4 priority 128 path cost 2000000 Everything works without any problem. The only problem in the beginning was PF rules. I added rule to allow traffic to the VM IP addresses. Miroslav Lachman From owner-freebsd-current@freebsd.org Thu May 30 20:41:01 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7739E15AA4AA for ; Thu, 30 May 2019 20:41:01 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 220EC6CD9F for ; Thu, 30 May 2019 20:40:58 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (v-critter.freebsd.dk [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 7BAE22025651 for ; Thu, 30 May 2019 20:40:52 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id x4UKeqRl084648 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Thu, 30 May 2019 20:40:52 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id x4UKep9d084640; Thu, 30 May 2019 20:40:51 GMT (envelope-from phk) To: FreeBSD Current Subject: Re: Inconsistent behavior with wpa / devd / network interfaces In-reply-to: From: "Poul-Henning Kamp" References: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <84633.1559248851.1@critter.freebsd.dk> Date: Thu, 30 May 2019 20:40:51 +0000 Message-ID: <84636.1559248851@critter.freebsd.dk> X-Rspamd-Queue-Id: 220EC6CD9F X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [3.60 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.63)[0.635,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[freebsd.dk]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[4]; IP_SCORE(0.07)[ip: (0.12), ipnet: 130.225.0.0/16(0.06), asn: 1835(0.16), country: EU(-0.01)]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[phk.freebsd.dk]; NEURAL_SPAM_LONG(0.76)[0.761,0]; NEURAL_SPAM_MEDIUM(0.85)[0.848,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[phk@phk.freebsd.dk,phk@critter.freebsd.dk]; RCVD_NO_TLS_LAST(0.10)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:1835, ipnet:130.225.0.0/16, country:EU]; FROM_NEQ_ENVFROM(0.00)[phk@phk.freebsd.dk,phk@critter.freebsd.dk] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Thu, 30 May 2019 20:41:01 -0000 -------- This sounds like handbook material ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@freebsd.org Thu May 30 22:07:01 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B25A415AC2B1 for ; Thu, 30 May 2019 22:07:01 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-qk1-x742.google.com (mail-qk1-x742.google.com [IPv6:2607:f8b0:4864:20::742]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) 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 98C0F709A1 for ; Thu, 30 May 2019 22:07:00 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-qk1-x742.google.com with SMTP id s22so2935970qkj.12 for ; Thu, 30 May 2019 15:07:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:openpgp:autocrypt:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=xOjShiq3lEEVGb3L2lLeMHHCCXTCu4rrxSLG8oVN8R4=; b=lR44jUG5Rbn7fR/Vu0OetgRQTFi/rFVIB4xujpw2Jk+Jw9N4j9hTk1Q/AKoaHSY+r/ /q/moBWh8O/O0WT+fX0W0rNUgwRP+6ynBXImagRDTw/u2q9SPvra4lVGQGF+21yhFp35 i5aSpUBozNK7C7dl4dhktSMquyIhC793tgrZfgPYFSqhG4v+B6FUTNvGofvbqD8WzlUJ uMHY4ugfHev40FUdZ7u9gBmJ+yZEYbP1jJcLQ7it2IcMppcfCr6Stul3ILZh2YE+Ge4V MT8Ld3W7UzWJktnZs8ynnZ3lesy5VPEpAMoFQQIozz62WTAy35Uie3NlO9SmTKLCa8Dl fjvw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding:content-language; bh=xOjShiq3lEEVGb3L2lLeMHHCCXTCu4rrxSLG8oVN8R4=; b=iASckf18aE87VmeNhjxiZlVIegYTmUAoUMz74OGUPHXubN7poOAwBs6nRDb1Oc9b/p zmKQxrCSHHMSmWZCy7W4msJpAjIaiB3eNI2QHeV7lAS9O9+tqDKqLtYAOPo5yzGIl3iu sjSQ7OOm+LwYWvcOOEXLWOawX/rcZ22ZbzZDC3+NOuumU7mpMuGNZ3pAbZDHChE0KOR0 viELCw+Ejjgj+C4URk+VelfY6tSQlBXV0YR6UGygKKJPBL1iscPRQf24XxrCrKVFCG9D FlLKw+OWxFXSAZZ4x+Eu1Cpg4ji7aJNCE0dqAODDJO8CkB9JYH2vkw9LCxmgkkuzBnLF KBzw== X-Gm-Message-State: APjAAAXYVLnlwMkHE6RBlLVLytzZLVQPja48SDjAHzgrH+9aBh03QvCx 8DyX+TezpbbDcriEzwT5N0MZZx/JVIU= X-Google-Smtp-Source: APXvYqzrmAAMHPcYL4nvBEZ94uUNyc4uLyRzDdE1qHQRjve5+qQr8Csbv6Db67b67utFsZBJSO6zdw== X-Received: by 2002:a37:5cc6:: with SMTP id q189mr5458118qkb.166.1559254019610; Thu, 30 May 2019 15:06:59 -0700 (PDT) Received: from [10.46.14.95] (wsip-72-212-151-146.ph.ph.cox.net. [72.212.151.146]) by smtp.gmail.com with ESMTPSA id o185sm2047210qkd.64.2019.05.30.15.06.58 for (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Thu, 30 May 2019 15:06:58 -0700 (PDT) Subject: Re: Inconsistent behavior with wpa / devd / network interfaces To: freebsd-current@freebsd.org References: <2836877.0P3pStmDMi@no.place.like.home> From: Johannes Lundberg Openpgp: preference=signencrypt Autocrypt: addr=johalun0@gmail.com; keydata= mQINBFxFmoIBEADoFO5jY+Fmsg44KiZjufEmpEf4kt7nCOfxNG9SruWpoXUaq0B296F+fIZC hNZqv1v7lGTsfoWRusxJmLd5CQgHHxEyruZbbPpNsQ/JKoDY3GGmrmWfN/SX3y0t0kdB9HsW mJcvZhK7we52f4gxddIVBS9nQoVoONX+hzXf8zwOAa0ik0EPgEwpIKS4j9lLq4bU+mqVKdRR bPeDujEA/qbsCKhaFJkPzXZtzEe6srq4RK1doEztwnKz02b+8gs642TRkWDQeTRZputrAaoN Un4R76A1QpXWyrFG1dQu48IGHi3KbkrvNyq6R1aUBIA0+CG1npIbxmc2mtSjoyvdipmDRbBD +mhECIxmYfBT6818zuj91XjrfOyfVdV2BryBvqFkJLkS3N3QElBIiVdDgdrqiNFWiOlDMxNI tdP16oQBNo8IB27/0YHpnQEw1MafZv5gG5DO0zLtLy88ASAfL7BYf90JP19rT4JIwnxsXxyv kEJnzhsXf0QVObEiAu1MqeFyWfZ8PpunmvEmJ0VChOL+v/kIx1E9cxhhzMZhqiMXfyM4zx2+ BF1FwAwJYPuJLu2B3L0uVBu+M1YvSOmKAbXPDP8PsqPjgSBTYI51MUjuuxN6jSsHDuK6G5k4 pUWR8axa+wafhd6Vz8zVwdTJZ9LdxgLLVg0kprBgccPHhPAZVQARAQABtCZKb2hhbm5lcyBM dW5kYmVyZyA8am9oYWx1bjBAZ21haWwuY29tPokCVAQTAQgAPhYhBIl1Pb3+hI60ivmRSULn yG4BGvSeBQJcRZqCAhsjBQkJZgGABQsJCAcCBhUKCQgLAgQWAgMBAh4BAheAAAoJEELnyG4B GvSe9O0P/RzeQAu1R37RlONZTXNn+qIAHvHbZEhzrCibzaZnwYdC31wGrYmXNDyiQIqOngFf QJuufQtH/+95OESJsjR+42L/pNfFdaEWxiI003qE7uCMzLK5UWUXd/5d5vYY0CaPyNCj1tyM ZIq7x4CaR3QLTh/Fw4zMUI/ZPH2S5SxVFGv0ZZFAdNYILD3qCkAS/9HmXsqufBWbfutA8TTf wyJfywmvf7ENjlZ4QOjb242ZY9NndqbmqTgWVAws+PN5e9AT8HkadscCTCSkYnxJyYG2El27 DpAAkekYplb/C0j82KSz2fy9RgwD+tTqt88DJOeFbIbrYt44u7KLHpzaZeqyUtn0reHCkE0W lnKH2kXXbuswFB4sONxI/J5+qSmOsAm5ItO3voyjm/swpmFR1yBlxo4th26gbO5NfBOK9YsY zHKgiRDv6ZdnHo+htphRxcCDHsFPzkQe5jouI25dvMZYl1LaTS/09lwYVwVIB2SFmMtFZ7rB N4NBSzPlpsg+g4dJNqiw6Rfa2Q/wUv+MzTJgLtHjDccXlpm33Nc09UytHFtNn26PO/zrM39r TwzdLu1mg0x2WWEWTIqe4CaczQU9SIg49BSyJNoPSZx3V7nMhTKbOeQKR5aV3dXI66aENw86 pa1tipuUKCPmope/GTJatUgPiD3JkyiD+7c1zQX2UAGmuQINBFxFmoIBEACb55RAkM59huAx 4Ddd8WBjsw25qf7rzxeRKAQ7or/8LvJBYQDPXZy0RhkRiu+P+MjxwGb6HVh+LDyAYDn9d8Mt ZqCP/dOGNcl7pkb6IhfRc3i5neckXCYfbm0cigiX9JkqZSt3KT96zbjCxsFZKyIyEFsMl46q 7wKWK5Irj3zxV/Z51JNTJyMLcIRWhY8G6qlMNFgZkz2Hv63w6BRekKVImOmOdThLAscy5ybq 2CIUeAwPG7lMYG9rgcPdn3tMPeWlLmUmi5pSwOQ3AKg3xFrW3WfegjRHdqpeuXoeTjYPPCW4 gyl59uv6E12a6eivItCxj67vlBXgOr4um+zoPyXG/WfidIFtWaEgyBrlGR1Klk7SIcqjEHUA FdiM+PweY4opHXXKn60NOZCqBJ59K43drOQgRouz8E2T3yEoYg40xAfY3lhJV/Vx5+kSTjmy sT2xotlPn/GzfaAEvNuJDK+Mec3LvfbbDoOWFolNyEvoMQqF5Q3A8eGqYsoVGBPxyzNvF2iY LkymxiXpgrSN0Q/LOK7pFlWwbVC8Z6g5I0J9ecgD55dGLoX2luLir787XX/JxGffzbRnP9NE ifenJGrQmx4CyEaz/CHQqSbROm5Uo/YFUX9J7OfUO4mtu90j773j32I3psey/Fz3EC/A2PHv Ghb0KsWYpS3Pj5TV1gGyswARAQABiQI8BBgBCAAmFiEEiXU9vf6EjrSK+ZFJQufIbgEa9J4F AlxFmoICGwwFCQlmAYAACgkQQufIbgEa9J7qOQ//YG/4e69YTSjtiYLXzBI8tRU2Sx+NFByx zx+C/r0EBThLtgRwCqEUZRB7iIDSO8aZ0Qa3vwWRohlD1tn/LBdDFfMmuQkNVdLIrjBoGBB9 B5xHdZJ9xnTZEwpTtk6IWolT4j+8rpGemGKKiFo3X6l02On4Qb4iM7h6rcDb76mfwooNYzB3 8PPcLvyOWb/9iCXAb5N7doo5zmOl15DVwvIF04eXU0q1FFj/iS1zNmtZ5Got82O1TQFV+de4 Rb3YA80IZhhhCiHHJqkMKeKQogRqU+UNDBARUBxfUtKsJtQzTQ2JUGwkb6X6bx53FTLP6O9q hDoODVweE1LdB1k1H5Nn+gawPdRMBqj43Y2amK7KEgoTBrwU04CLpKiaAC0S+EcJFfJcwtpK k3F+uTtP/hnhFnWbn8SgRkHKXKWqSCt63NstXhMzAJut1gEzV+CcPNKqa/sFgQaYEvzCS5Kl F/PXj0++f3TIFqT+2ZNNp8Bz8dT7gh8RPPg5oYQiCHH8K1RAmq7gKqmwyg0qgOazHnped+od X4f3qx320JAP6NP9wglDm6eht48NJzb0sffN8z34wrP66oz8oPKtS5CFV0m/384hEg0lmi3W wo2Hno7rA1etTPJX0dI6/GLlQDtNTHvKQ077HQdWVOMQVWC9j7YH7Zr9NjtOvxcNVRX3fxpJ 6CE= X-Tagtoolbar-Keys: D20190530150656877 Message-ID: <2fce7476-2329-ea9f-ea26-4c3fdf9aa4b0@gmail.com> Date: Thu, 30 May 2019 15:06:56 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 98C0F709A1 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=lR44jUG5; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of johalun0@gmail.com designates 2607:f8b0:4864:20::742 as permitted sender) smtp.mailfrom=johalun0@gmail.com X-Spamd-Result: default: False [-4.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.98)[-0.984,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-0.51)[ip: (3.09), ipnet: 2607:f8b0::/32(-3.28), asn: 15169(-2.28), country: US(-0.06)]; RCVD_IN_DNSWL_NONE(0.00)[2.4.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Thu, 30 May 2019 22:07:02 -0000 On 5/30/19 1:25 PM, Miroslav Lachman wrote: > Greg Rivers wrote on 2019/05/30 18:37: > > [...] > >>> Do I have something weird in my setup causing this? I don't recall ever >>> having this issue when not using failover lagg. Running recent >>> 13-CURRENT. >>> >> I think there's a (unknown?) problem that makes lagg(4) incompatible >> with >> bridge(4). I've never been unable to make a lagg interface work as a >> member of >> a bridge. Lacking the time to pursue it, I've resorted to NATing >> instead. > > lagg and bridge can work together. > I am running machine with FreeBSD 11.2 with 2 Intel NICs: em0 and em1 > combined in to lagg0 > > lagg0 has 4 static IP addresses > > There is also bhyve VM on tap20, this VM has another 2 static IP > addresses > > tap20 and lagg0 are members of the bridge. This bridge is renamed to > "vm-public" > > vm-public: flags=8843 metric 0 > mtu 1500 >         ether da:ae:ba:75:53:ce >         nd6 options=1 >         groups: bridge vm-switch viid-4c918@ >         id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 >         maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 >         root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 >         member: tap20 flags=143 >                 ifmaxaddr 0 port 5 priority 128 path cost 2000000 >         member: lagg0 flags=143 >                 ifmaxaddr 0 port 4 priority 128 path cost 2000000 > > Everything works without any problem. > > The only problem in the beginning was PF rules. I added rule to allow > traffic to the VM IP addresses. > > Miroslav Lachman Hi Thanks for the feedback. This setup works great for me too. The problem is when switching external network on lagg0 (DHCP)... Once I'm connected and nothing changes, it works perfectly. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Fri May 31 10:49:12 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0AF6A15B9184 for ; Fri, 31 May 2019 10:49:12 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8BE618DB35 for ; Fri, 31 May 2019 10:49:11 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by home.opsec.eu with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hWf60-000AQ6-14 for freebsd-current@freebsd.org; Fri, 31 May 2019 12:49:12 +0200 Date: Fri, 31 May 2019 12:49:11 +0200 From: Kurt Jaeger To: FreeBSD Current Subject: Crash on very recent CURRENT if using poudriere Message-ID: <20190531104911.GA39925@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Fri, 31 May 2019 10:49:12 -0000 Hi! [panic] non-zero write count during poudriere run https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238031 Ideas on how to proceed ? -- pi@opsec.eu +49 171 3101372 One year to go ! From owner-freebsd-current@freebsd.org Fri May 31 17:04:53 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5DA8415C1B2F for ; Fri, 31 May 2019 17:04:53 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 244B074D7A; Fri, 31 May 2019 17:04:52 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id x4VH4huV021105 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 31 May 2019 20:04:46 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua x4VH4huV021105 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id x4VH4hER021104; Fri, 31 May 2019 20:04:43 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 31 May 2019 20:04:43 +0300 From: Konstantin Belousov To: Kurt Jaeger Cc: FreeBSD Current Subject: Re: Crash on very recent CURRENT if using poudriere Message-ID: <20190531170443.GD27392@kib.kiev.ua> References: <20190531104911.GA39925@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190531104911.GA39925@home.opsec.eu> User-Agent: Mutt/1.12.0 (2019-05-25) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Fri, 31 May 2019 17:04:53 -0000 On Fri, May 31, 2019 at 12:49:11PM +0200, Kurt Jaeger wrote: > Hi! > > [panic] non-zero write count during poudriere run > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238031 > > Ideas on how to proceed ? Try this. diff --git a/sys/fs/nullfs/null_vnops.c b/sys/fs/nullfs/null_vnops.c index f92383179a9..b663d8d718d 100644 --- a/sys/fs/nullfs/null_vnops.c +++ b/sys/fs/nullfs/null_vnops.c @@ -810,6 +810,8 @@ null_reclaim(struct vop_reclaim_args *ap) */ if (vp->v_writecount > 0) VOP_ADD_WRITECOUNT(lowervp, -vp->v_writecount); + else if (vp->v_writecount < 0) + vp->v_writecount = 0; VI_UNLOCK(vp); diff --git a/sys/fs/tmpfs/tmpfs_subr.c b/sys/fs/tmpfs/tmpfs_subr.c index f9db5f99e50..9fe58cd4c13 100644 --- a/sys/fs/tmpfs/tmpfs_subr.c +++ b/sys/fs/tmpfs/tmpfs_subr.c @@ -488,6 +488,8 @@ tmpfs_destroy_vobject(struct vnode *vp, vm_object_t obj) VI_LOCK(vp); vm_object_clear_flag(obj, OBJ_TMPFS); obj->un_pager.swp.swp_tmpfs = NULL; + if (vp->v_writecount < 0) + vp->v_writecount = 0; VI_UNLOCK(vp); VM_OBJECT_WUNLOCK(obj); } From owner-freebsd-current@freebsd.org Sat Jun 1 01:56:51 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5831515A7D30; Sat, 1 Jun 2019 01:56:51 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:300:2185:123::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 76C468D7AF; Sat, 1 Jun 2019 01:56:50 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [104.207.135.49]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id x511ugkQ052164; Sat, 1 Jun 2019 02:56:43 +0100 (BST) (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id x511ufxu051982; Sat, 1 Jun 2019 02:56:42 +0100 (BST) (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <201906010156.x511ufxu051982@donotpassgo.dyslexicfish.net> Date: Sat, 01 Jun 2019 02:56:41 +0100 Organization: Dyslexic Fish To: voidanix@420blaze.it, rainer@ultra-secure.de Cc: owner-freebsd-current@freebsd.org, freebsd-current@freebsd.org Subject: Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option References: In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [104.207.135.49]); Sat, 01 Jun 2019 02:56:44 +0100 (BST) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Sat, 01 Jun 2019 01:56:51 -0000 rainer@ultra-secure.de wrote: > I have a 32bit FreeBSD 6 binary that I'll need for a bit until the > department who is technically responsible for the service gets around > redoing that service. >From my understanding from reading the bug (though it's not entirely clear in this thread), this relates to removing the options from the generic (et al.) kernels, not deleting the code itself. You'd therefore be able to just keep the options enabled in your own config.. , or is this just the first stage of full deprecation? Cheers, Jamie From owner-freebsd-current@freebsd.org Sat Jun 1 06:04:45 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC77515ABB8E for ; Sat, 1 Jun 2019 06:04:44 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6CFC5749CA for ; Sat, 1 Jun 2019 06:04:44 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x5164WqJ033058; Fri, 31 May 2019 23:04:32 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x5164UIl033057; Fri, 31 May 2019 23:04:30 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201906010604.x5164UIl033057@gndrsh.dnsmgr.net> Subject: Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option In-Reply-To: <201906010156.x511ufxu051982@donotpassgo.dyslexicfish.net> To: Jamie Landeg-Jones Date: Fri, 31 May 2019 23:04:30 -0700 (PDT) CC: voidanix@420blaze.it, rainer@ultra-secure.de, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 6CFC5749CA X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.96 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.96)[-0.956,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Sat, 01 Jun 2019 06:04:45 -0000 > rainer@ultra-secure.de wrote: > > > I have a 32bit FreeBSD 6 binary that I'll need for a bit until the > > department who is technically responsible for the service gets around > > redoing that service. > > >From my understanding from reading the bug (though it's not entirely clear > in this thread), this relates to removing the options from the generic (et al.) > kernels, not deleting the code itself. That would make GENERIC less than GENERIC as you can not load these changes as modules, nor would it be easy to make them modules. > You'd therefore be able to just keep the options enabled in your own > config.. , or is this just the first stage of full deprecation? And that too, if you take stuff out of GENERIC it gets built less often and that often leads to bit rot and that often leads to deprecation because it "must not be used it has rotted and look no one has complained." (Which, imho, is a rotton support model.) > Cheers, Jamie -- Rod Grimes rgrimes@freebsd.org