From nobody Mon Sep 27 06:05:46 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id C868D17E292C for ; Mon, 27 Sep 2021 06:06:01 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic315-8.consmr.mail.gq1.yahoo.com (sonic315-8.consmr.mail.gq1.yahoo.com [98.137.65.32]) (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 4HHsZd36yzz4RNl for ; Mon, 27 Sep 2021 06:06:01 +0000 (UTC) (envelope-from marklmi@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1632722754; bh=sR1OHu7Ybi6xz8qSAv0qJOMPDma3lwPiazG3/R5R+HE=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=dDyjOWgzq3+TuRcfuHJWCWnHEVJ3IUuXMx5tJ8XSySzWUi91CIDvd8BzrfBLCMPcQZaCvkBmqOTzM7YF1OzZ3lOXQYiYFd7/66+u+bWTGJZ+UtcizwT22N7+j2b2OvVZwujF88/qz2Mv89P2RnVSVTasDPFppHUPsVkstTNbMLEVyvtFxFtU+IjdHF07A0KGeMAd9rT0mwj2E5TVn3knXQTjbggsnfSx/OPAoaIgU0kesHQR1N6rygkPAmOogHr+MRFh+t4TQe3ys/wy3Nb5rbLzVsCU/Z36UKwBza98Nq+PPCiNPVzt9UgvjiBG3oKefTFJLdDVvD68VfoCRND5Wg== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1632722754; bh=8w1Jh5bGTbxKKW4EpOSux+T+xta6ULDiwPmnU65WcT7=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=PUUfyXxr6NxjcUP5KlvfTYb0vPMBcmKER41HpsGAt6UdMoJU0WUvC4pbrT0s9f+asaRSfgZWPTQeAGp/xln7MRuOk195M/XNFpOp33s2yjlsfyy0hUpkU2VdXPW/4AKhGFVSaNHKVtmEZu/FHpdU1TjQIc3rPytnWGPCd8EeuhXcVUkCuFYLeb8unHPlyYPUMgUQksEtyOsTHe2uTm5q4wt7Ki42Q9dpGAfmPBBIw8caKuWqIwAR/ICO68SMJ4bUapu1ZatwP7XzjVDishzG6z/g96ucHXb0ECgwelQgyE0NPnyILNhHYzQtMAAc+b30/99qd4ige5O3FLgbf3EcsA== X-YMail-OSG: wmVI8EAVM1mFBixHwfuFiAkmBBqra.Ym7Gl8VDxG9DnbQaRG6xUuaCu55TV44aX dcnlmhxp3_xbyf6jGudvasMPakOaY5LdreKr8ba67MRkvyq.F0Pmz0Q0bFasR.OoC3XI4A7HMDCB 7Zt2LXslgub3djJ7mU1ho3GcBdEz7OiuDkSifnCJ48hzIQNLBt7RDouzTGIfcAsyfdmLEEe2pNZl aYp7_HDZU5_zDfKI_QKROJAA.9YjxKr7R4Dr4ZWu9Hr7E1Ht2DWPrwllcEENxu5Eq7BH6VikbBsn 9Ew_U7l418hgEJIDwrTaGL81xYENuYZP7grpkM1PZAz31zy7bZUiTtYvPmr7UWauB0sGVOmBCzw3 cPid82nNKn8MXcaGSCo2gBjJ8kZ.2uIpKU1WXTEci_FxQJOsofSTahGmQF_OkJGtjUVauG3J1EeB W3qkpi9zuTfHOlyFxDeVvcjC8PcmxnRNKLmg98z4jmEodTCwhhgsf9PpaIeXus8nyyLc7VeHFxtc eL9jV0CodYwSghoPNNS7HJ2oTC0ceY9EzV_5DLyTsbEaTsnqokrgy82XLLjA7swqdksPYt2J0G0R _0TYAFscnmkADLmZg_u9rYxVu0IpzvHEQrgM61UNSHsiWCzAWhOwBCWSED8NMXuqdMS5G2xPaO3x 41pJfRrtQQ8L0ZWIYo_gUiLze8xcFsZ0GEmslpy21QUrNgmvK.mXjbWX2r01OO5deoHcj3NY8.dv kbwsA9VQSyAJTgoxB1a832UsbRa2Vif8cGOkaZQrCIqcb3gjtbMWkadpmxcPJHZsW_A_7MbHOVCc 4clHHter4rTGbxi3RNRv7XSxm8_WKe1v_2UYN99KyrZXrL6cDJPKkOUA0RJlmocvbJRLzNBgkjkO CjOy9Imfwe.YhbvHG5knG0TlasNwCevugSbLQGcpPau9NNMO_XrMP4d9kXt9lA_X2lSNz7ps1m9m eppflE.Ts7VSIdSESFhEBp_am3lZuGKcK_w35KE5I5c8XB6PAD9SxPFIuAG4Egb4wsB1Cd7pORgd DKRDUlaMmdQVTWrgIovOf2bukF4c5pMzNxm3mMSs4mt3PjA5HbOUqVGeA8QIg68O_BjDQdqPJnkY qc_VQglKEJ0hOg4MJMVaKwcaRTbQzl5SCFmxhcS7Iep442m_l612s9BKBjMDh1paBj3bISJqnGSq ovR_3DUFVRs.3DqidN.gl_GFim4V2cPlMV3xipf2ThV7mVT1dZCn.R8pexnJMdL3FAnJwOnlonOD XGCgjpeupuiYW45eSm8OuqoWisNesKXign2djADXfS04hEvI.qLGHUCII7CG4dX0EnwWc258UIdF fzom1j4jkXHug6LsWOFDxXpfqXFKg3PBijz3ENwB30UdwEpAyE7LXjwcH_Mwyay_c4ZHTEKueGhV yj93iP2Uk.8KocgXztZNggO98OqrhROSYMwgkNhK5aqqtYifvfdkCZwW0P4h6i1sR5d15CPhJrEd vKNBJkMK3KPoWeh9mlTk3QReKS5hvQkUBPz0iATyb2HYjWbnpNuDE35UN2xUMEuaCJiiSxvrK.Xi lcXAiLXyI1.3FogfOZ6huWQc_rYTosEG0L6OwyO4U5QNwAFfYfaHUGJoVjahUk6a5_RcUh61UYWK L_9zpppMMeUYQRq7A8YdL90fghwOh4L.mm6MnGKAfV3878OSoAEHZMSokD7JKSU4wyxn7rSlJycn wX1Ryx7rz76vGCDHmjHikfdDL15b5k6iFeoq3y4UclWuOUDAtrzOfIvkHjOUK9qCZ5KMRyOFt9Zq WRIHP_V.8ZHFpxDB.MRQXNlrx_.g5SVPGzo6kPI2kJSiqjikDzNSsT9uAlwvZAXXWDcpsZ2gRQnP 6bmaTgtBgxOCaAymPuW.xWM7Yet0m95C58cv3MSTBlpmXgkAo9KvTBUTd0LR7mT1ZtrQVTKe.9cR raPUI0KxqeO7gaB1d90SV9Op3rH0hGWq6W6DKdQS6m3Njg6WRICPgLsHnxpDvZ47Q2dqn1F83Ntb JPQjEj6yi1wXGQ2upLKdbzJkh_iEvTzVu9yclCXrHupBRf0IPajwZWgiM4lLFPwPqePPbrXx78wt v1DbCqm7KnMSZDSo3kwr.AckiHXWMa_IcCJPpBNHLf6t5kHzsXF73W_iiEQcOQeIzWJv8VpWBbWh b6xQHMN_a7wQds2qI3CONcTGT2ZPw.LtwCcXc71SEBcQ8279s6KbDr3ZRPWlwcCFZvc0GLO031Jx Hgz203SsfoiUwTiGezAD_jKrzcntARRW36pH43ynqvvF9ePCcffLUBcnDXiqcb5zGUXIsZoHeiyU v_81nuYUkB_1OG9sTejtnd8fs X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.gq1.yahoo.com with HTTP; Mon, 27 Sep 2021 06:05:54 +0000 Received: by kubenode586.mail-prod1.omega.bf1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 2b4e69c12d193289e757e74478fe0d69; Mon, 27 Sep 2021 06:05:49 +0000 (UTC) Content-Type: text/plain; charset=us-ascii List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Subject: Re: I get odd time reports from poudriere on armv7 system, under a (non-debug) main [so: 14] FreeBSD. In-Reply-To: Date: Sun, 26 Sep 2021 23:05:46 -0700 Cc: freebsd-ports@freebsd.org, freebsd-current , Free BSD Content-Transfer-Encoding: quoted-printable Message-Id: <0FE65CAD-EDFF-4CE8-8750-BD4F6971CAA0@yahoo.com> References: <187B69AF-9465-41DE-BFD0-A4AA0F7F9068@yahoo.com> To: Ian Lepore , Bryan Drewery X-Mailer: Apple Mail (2.3654.120.0.1.13) X-Rspamd-Queue-Id: 4HHsZd36yzz4RNl X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Reply-To: marklmi@yahoo.com From: Mark Millard via freebsd-ports X-Original-From: Mark Millard X-ThisMailContainsUnwantedMimeParts: N On 2021-Sep-26, at 10:02, Ian Lepore wrote: > On Sun, 2021-09-26 at 02:27 -0700, Mark Millard via freebsd-current > wrote: >> On 2021-Sep-25, at 23:25, Mark Millard wrote: >>=20 >>=20 >> [...] >> if (argc =3D=3D 3 && strcmp(argv[2], "-nsec") =3D=3D 0) >> printf("%ld.%ld\n", ts.tv_sec, ts.tv_nsec); >=20 > There are two problems with this, both the seconds and nanos are > printed incorrectly. The correct incantation would be >=20 > printf("%jd.%09ld\n", (intmax_t)ts.tv_sec, ts.tv_nsec); >=20 Thanks Ian for looking into more than I did last night. Based on the following (up to possible e-mail white space issues), poudriere-devel seems t be working for reporting times: # more /usr/ports/ports-mgmt/poudriere-devel/files/patch-clock=20 --- src/libexec/poudriere/clock/clock.c.orig 2021-09-26 = 22:24:54.735485000 -0700 +++ src/libexec/poudriere/clock/clock.c 2021-09-26 11:46:12.076362000 = -0700 @@ -24,6 +24,7 @@ * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. */ =20 +#include #include #include #include @@ -71,8 +72,8 @@ } else usage(); if (argc =3D=3D 3 && strcmp(argv[2], "-nsec") =3D=3D 0) - printf("%ld.%ld\n", ts.tv_sec, ts.tv_nsec); + printf("%jd.%09ld\n", (intmax_t)ts.tv_sec, ts.tv_nsec); else - printf("%ld\n", ts.tv_sec); + printf("%jd\n", (intmax_t)ts.tv_sec); return (EXIT_SUCCESS); } =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From nobody Mon Sep 27 08:05:06 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 824A617CC364; Mon, 27 Sep 2021 08:10:16 +0000 (UTC) (envelope-from naddy@mips.inka.de) Received: from mail.inka.de (mail.inka.de [IPv6:2a04:c9c7:0:1073:217:a4ff:fe3b:e77c]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4HHwKz5h81z4b02; Mon, 27 Sep 2021 08:10:15 +0000 (UTC) (envelope-from naddy@mips.inka.de) Received: from mips.inka.de (naddy@[127.0.0.1]) by mail.inka.de with uucp (rmailwrap 0.5) id 1mUliA-00Gmun-DJ; Mon, 27 Sep 2021 10:10:06 +0200 Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.16.1/8.16.1) with ESMTP id 18R8560C086116; Mon, 27 Sep 2021 10:05:06 +0200 (CEST) (envelope-from naddy@lorvorc.mips.inka.de) Received: (from naddy@localhost) by lorvorc.mips.inka.de (8.16.1/8.16.1/Submit) id 18R856n8086115; Mon, 27 Sep 2021 10:05:06 +0200 (CEST) (envelope-from naddy) Date: Mon, 27 Sep 2021 10:05:06 +0200 From: Christian Weisgerber To: current@freebsd.org, arch@freebsd.org Subject: Re: [HEADSUP] making /bin/sh the default shell for root Message-ID: References: <20210922083645.4vnoajyvwq6wfhdf@aniel.nours.eu> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4HHwKz5h81z4b02 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of naddy@mips.inka.de has no SPF policy when checking 2a04:c9c7:0:1073:217:a4ff:fe3b:e77c) smtp.mailfrom=naddy@mips.inka.de X-Spamd-Result: default: False [-1.30 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.94)[-0.938]; FREEFALL_USER(0.00)[naddy]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.27)[-0.265]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[inka.de]; AUTH_NA(1.00)[]; RCVD_COUNT_THREE(0.00)[3]; MID_RHS_MATCH_FROMTLD(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:202113, ipnet:2a04:c9c7::/32, country:DE]; RCVD_TLS_LAST(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Dirk Meyer: > Migration of aliase will be painful as ">&" and "|&" is not supoported. csh sh >& foo >foo 2>&1 |& foo 2>&1 | foo -- Christian "naddy" Weisgerber naddy@mips.inka.de From nobody Mon Sep 27 14:40:39 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 7E0E317EC69A for ; Mon, 27 Sep 2021 14:40:42 +0000 (UTC) (envelope-from gardask@gmail.com) Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HJ50V05pSz3Mxg for ; Mon, 27 Sep 2021 14:40:42 +0000 (UTC) (envelope-from gardask@gmail.com) Received: by mail-wm1-x32c.google.com with SMTP id v127so722535wme.5 for ; Mon, 27 Sep 2021 07:40:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:from:subject:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=44Lig+6QQbFy5lI6uokyUSIrdkT8NYuWyrCw2jiAwRk=; b=V4OYvfSEY2CL76ClI86xBOTZGuwZjTuzXm3LWtfwV/+q7AHsZXcEvdQqAgPRAtrECH CGeCrZAfM4HTxzdFMjchr1x6lEDSIXnhQ/3fQR0VpL28eWnODNze8wWMZI6OgepUErRb /OJp/Ds8UEB+kQt9ev8DXqtiwnf6QNg4MQEg7CrOVDBJOl82STmtzX727X5DQLNA3+ez eJGKoS0LJ4+sZ/QccmFc2fWfmhtXAAxACNgxqQ8RHryE42rb02wycpYeokN/5D0EOfl6 0vdYu1LK58h71pRZlWWLwR7N8bV2t5rXPTZjMprV5ml1DHdMzVzcUiGpfM9jAvH/+ymP suLg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=44Lig+6QQbFy5lI6uokyUSIrdkT8NYuWyrCw2jiAwRk=; b=uumjSq203WvE4eh9HXO4JpxWBw7QEvNo15YStWdcMu/87c/RtVttvF0LmRZHdwWTcl mWEzqjnZDPpMJ+m6IOCzZjqeiQGlN9kBBMjXgLTuFQQq85K48ir2xJUwYN8EzpBjBtdR wZPUm9vusnCMiNg2eSJmxSbLuCoTR3n901+C5P+NZpxqRIvG54Koy8H1WUCK8HinqaSz bLm5gQWQFkwSNEoWBlq+CI4NuBa9zxMOjCdnRgIivGHElEYIPHeXiNQtituUNW6maRFN D6J4GA+WVOnWMe35gp/j2FbezsM8Pa5IT5g+Sa0Ym71kX/Br46cEcxJfn4j+QO984UgR iExg== X-Gm-Message-State: AOAM5301JQbDxDQ2UFCe+M+rdfo8lPO4X9cDMMuZqICsn6WeItxa6oYd WNq7rcVfOpxklzDHAA7TPp1FXnZ8/Nw= X-Google-Smtp-Source: ABdhPJznAR0N1v1i7QMCZA+hdmmMYIrjdROe9i5q+rmxyiqNxKLwLaKOhIfjrSckw6xooXeEbmO1zA== X-Received: by 2002:a7b:cd0d:: with SMTP id f13mr16031929wmj.183.1632753640884; Mon, 27 Sep 2021 07:40:40 -0700 (PDT) Received: from [10.0.30.5] ([31.47.99.1]) by smtp.gmail.com with ESMTPSA id z79sm17697194wmc.17.2021.09.27.07.40.40 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 27 Sep 2021 07:40:40 -0700 (PDT) To: current@freebsd.org From: Karel Gardas Subject: ELF binary type "0" not known. (while compiling buildworld on risc-v/qemu) Message-ID: Date: Mon, 27 Sep 2021 16:40:39 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4HJ50V05pSz3Mxg X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=V4OYvfSE; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of gardask@gmail.com designates 2a00:1450:4864:20::32c as permitted sender) smtp.mailfrom=gardask@gmail.com X-Spamd-Result: default: False [-4.00 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::32c:from]; NEURAL_HAM_SHORT(-1.00)[-0.999]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: N Hello, I'm playing with compiling freebsd 13 (releng/13.0 2 days ago) and current (git HEAD as of today) on qemu-5.1.0/qemu-6.1.0 on risv64 platform. The emulator invocation is: qemu-system-riscv64 -machine virt -smp 8 -m 16G -nographic -device virtio-blk-device,drive=hd -drive file=FreeBSD-14.0-CURRENT-riscv-riscv64.qcow2,if=none,id=hd -device virtio-net-device,netdev=net -netdev user,id=net,hostfwd=tcp::2233-:22 -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf -kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -object rng-random,filename=/dev/urandom,id=rng -device virtio-rng-device,rng=rng -nographic -append "root=LABEL=rootfs console=ttyS0" and the host is Ubuntu 20.04.x LTS. Both qemu 5.1.0 and qemu 6.1.0 are compiled from, source, but both OpenSBI and u-boot for risc-v are Ubuntu packages provided (to accompany ubuntu provided qemu 4.2.1) My issue while compiling both 13 and current is that compilation after some time fails with: root@freebsd:/usr/src # time make -j8 buildworld > /tmp/build-j8-2.txt ELF binary type "0" not known. 17784.134u 21388.907s 1:50:13.83 592.2% 30721+572k 10+2177io 0pf+0w I'm curious if this is a know issue either in Qemu or in FreeBSD for risc-v or if I'm doing anything wrong here? Thanks! Karel From nobody Mon Sep 27 15:13:07 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 54A0E17EF60E for ; Mon, 27 Sep 2021 15:13:19 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (cross.sbone.de [195.201.62.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HJ5k6468zz3h87 for ; Mon, 27 Sep 2021 15:13:18 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 31F738D4A156 for ; Mon, 27 Sep 2021 15:13:11 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id CA41EE707FF for ; Mon, 27 Sep 2021 15:13:09 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id 3ZLGbpjM64rQ for ; Mon, 27 Sep 2021 15:13:08 +0000 (UTC) Received: from nv.sbone.de (nv.sbone.de [IPv6:fde9:577b:c1a9:31::2013:138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 61D54E707D9 for ; Mon, 27 Sep 2021 15:13:08 +0000 (UTC) Date: Mon, 27 Sep 2021 15:13:07 +0000 (UTC) From: "Bjoern A. Zeeb" To: freebsd-current@FreeBSD.org Subject: BTX halted (pxeboot) Message-ID: X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Rspamd-Queue-Id: 4HJ5k6468zz3h87 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of bzeeb-lists@lists.zabbadoz.net designates 195.201.62.131 as permitted sender) smtp.mailfrom=bzeeb-lists@lists.zabbadoz.net X-Spamd-Result: default: False [-3.27 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:195.201.62.131]; MIME_GOOD(-0.10)[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]; DMARC_NA(0.00)[zabbadoz.net]; NEURAL_HAM_SHORT(-0.97)[-0.973]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:195.201.0.0/16, country:DE]; RCVD_TLS_LAST(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Hi, plain old-style pxeboot on amd64 (no EFI) gives me this with a tree at 2e79a216329f62a78dbbc72256e782353e220968 (Sep 16). It seems indepdent of the other issue we are seeing with EFI/arm64 netbooting (and the fix from there doesn't help here). Is anyone else seeing this or can repro? I'd love to avoid debugging two issues at the same time and would hope someone else can help with this one as essentially none of my Lab machines netboot anymore with a plain CURRENT now. /bz Intel(R) Boot Agent GE v1.3.65 Copyright (C) 1997-2010, Intel Corporation CLIENT MAC ADDR: ... CLIENT IP: 192.0.2.102 MASK: 255.255.255.0 DHCP IP: 192.0.2.1 PXE Loader 1.00 Building the boot loader arguments Relocating the loader and the BTX Starting the BTX loader BTX loader 1.00 BTX version is 1.02 int=00000006 err=00000000 efl=00010006 eip=830c4592 eax=0000000d ebx=00032b36 ecx=00000001 edx=00062058 esi=3d22d750 edi=00000000 ebp=00079b90 esp=00079b6c cs=002b ds=0033 es=0033 fs=0033 gs=0033 ss=0033 cs:eip=db fd f2 db af de f7 b6-f9 f6 7f 73 fd 5f f8 ff 1c ba 9f f7 ba 9c d3 ed-ff f6 ff 9d fd ff e9 d9 ss:esp=8c 7f 03 00 4b 20 06 00-50 d7 22 3d 9c 2c 03 00 1a 00 00 00 00 00 00 00-1a 00 00 00 41 1a 03 00 BTX halted -- Bjoern A. Zeeb r15:7 From nobody Mon Sep 27 15:59:13 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id CA9CB17CBA9E for ; Mon, 27 Sep 2021 15:59:18 +0000 (UTC) (envelope-from rollingbits@gmail.com) Received: from mail-qv1-xf34.google.com (mail-qv1-xf34.google.com [IPv6:2607:f8b0:4864:20::f34]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HJ6lB0VC4z3lnJ for ; Mon, 27 Sep 2021 15:59:18 +0000 (UTC) (envelope-from rollingbits@gmail.com) Received: by mail-qv1-xf34.google.com with SMTP id a12so11452382qvz.4 for ; Mon, 27 Sep 2021 08:59:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=sP7zHTaTQg6943XDmKKTT9rGh71s2S5rzQmEANrjvUU=; b=NoqtF6ZJ1yVW1MpjpZBJYpuEAHUGDQMwyF1r8yK/UYhO8FopL7jR7WXY7SroVDdG+w nV+X5Du1wB2Wd8wELu2quhnWmpNUQTMpGByy/+HPIK2wCVZJqjAlVpmWxRAWE44PaapT xlvd2Q2ggOTkYbAx06lEZGUP2yw2yonSRc4cPUjEYnCUTAhraa/iEEU34YpbZF8SA/ar B1Tv2qEVNRC15l6BEVN+/ERmZKRyB+kBaFGVuYVedLUduJ71aYpwOFnnie5QPJoSk+XF SHLW39NNpUQR2Ext5Tb+nb8KpKpTdX6P7eZxrlVsHbqmlhpACNkaSMGp9vKuEQ+IvTpa XK5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=sP7zHTaTQg6943XDmKKTT9rGh71s2S5rzQmEANrjvUU=; b=uXGWExcfrEGIVn/oUeP69N4yIpep0FQwq/2i/fwNAlSHoDq+0XNtz7TSYAIdTo/X6e zEM9KQCbzhD1HogIpB2LRvG9bjP2ayZohjMnFk7ChuOoTw1PDdcxQP+DRr7ywctCEkYw fYJAdKCaYGlnpsrlT5CCeDUlx3admS/n440WHqW2f7SdH02qJI0pzs3lOmhaqO66sDSw 4/QcN/tYhLMR/97yCB3xYcN7iaPvXjkU1ApZIFIFFuaUYiIP5C9+jshIDGsrXnQRSgO0 TKRR+lGQKcZzoman530UdgRKo6cVpa2Bgz/XLrNapEY15BIPq4mG4xEgbZtTEcFCfT+u PlDA== X-Gm-Message-State: AOAM530hyKo9hB4uh3c/0UmO4HZi2nShi/zH6G3ak2YJHZzBkxyt1sC3 Jq6tj9NkUiBh1HOALegP2Vef4uZ0Ll0= X-Google-Smtp-Source: ABdhPJwKnszkWFxDoVzc6viL6fZC7THzab+z5rQ3lKS+rW82oRU4Fr39cxRLUtX+X3ruciEBRa6VPA== X-Received: by 2002:a0c:f20b:: with SMTP id h11mr568299qvk.66.1632758356392; Mon, 27 Sep 2021 08:59:16 -0700 (PDT) Received: from smtpclient.apple ([2804:389:2046:e38b:5ca9:34:ef73:3d04]) by smtp.gmail.com with ESMTPSA id w17sm6959886qkf.97.2021.09.27.08.59.15 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 27 Sep 2021 08:59:15 -0700 (PDT) Content-Type: multipart/alternative; boundary=Apple-Mail-EF56CAA5-AC96-4BB2-83DE-C1C440BB5554 Content-Transfer-Encoding: 7bit From: =?utf-8?Q?Lucas_Nali_de_Magalh=C3=A3es?= List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (1.0) Subject: Re: [HEADSUP] making /bin/sh the default shell for root Date: Mon, 27 Sep 2021 12:59:13 -0300 Message-Id: References: Cc: current@freebsd.org In-Reply-To: To: Christian Weisgerber X-Mailer: iPhone Mail (19A346) X-Rspamd-Queue-Id: 4HJ6lB0VC4z3lnJ X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --Apple-Mail-EF56CAA5-AC96-4BB2-83DE-C1C440BB5554 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > On Sep 27, 2021, at 5:11 AM, Christian Weisgerber wro= te: >=20 > =EF=BB=BFDirk Meyer: >=20 >> Migration of aliase will be painful as ">&" and "|&" is not supoported. >=20 > csh sh >> & foo >foo 2>&1 > |& foo 2>&1 | foo >=20 Actually, the man page of csh says that this part isn't equivalent to the sh= counterpart but this issue have no relation to the original problem in this thread. --=20 rollingbits =E2=80=94 =F0=9F=93=A7 rollingbits@icloud.com =F0=9F=93=A7 rolli= ngbits@gmail.com =F0=9F=93=A7 rollingbits@yahoo.com From nobody Mon Sep 27 19:22:09 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 9C70317DD9A5 for ; Mon, 27 Sep 2021 19:22:11 +0000 (UTC) (envelope-from jhb@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) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HJCFH48Q6z4bWc; Mon, 27 Sep 2021 19:22:11 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from John-Baldwins-MacBook-Pro.local (ralph.baldwin.cx [66.234.199.215]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: jhb) by smtp.freebsd.org (Postfix) with ESMTPSA id 1CEAD56D7; Mon, 27 Sep 2021 19:22:11 +0000 (UTC) (envelope-from jhb@FreeBSD.org) To: Karel Gardas References: Cc: current@freebsd.org, Jessica Clarke From: John Baldwin Subject: Re: ELF binary type "0" not known. (while compiling buildworld on risc-v/qemu) Message-ID: Date: Mon, 27 Sep 2021 12:22:09 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-ThisMailContainsUnwantedMimeParts: N On 9/27/21 7:40 AM, Karel Gardas wrote: > > Hello, > > I'm playing with compiling freebsd 13 (releng/13.0 2 days ago) and > current (git HEAD as of today) on qemu-5.1.0/qemu-6.1.0 on risv64 > platform. The emulator invocation is: > > qemu-system-riscv64 -machine virt -smp 8 -m 16G -nographic -device > virtio-blk-device,drive=hd -drive > file=FreeBSD-14.0-CURRENT-riscv-riscv64.qcow2,if=none,id=hd -device > virtio-net-device,netdev=net -netdev user,id=net,hostfwd=tcp::2233-:22 > -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf -kernel > /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -object > rng-random,filename=/dev/urandom,id=rng -device > virtio-rng-device,rng=rng -nographic -append "root=LABEL=rootfs > console=ttyS0" > > and the host is Ubuntu 20.04.x LTS. Both qemu 5.1.0 and qemu 6.1.0 are > compiled from, source, but both OpenSBI and u-boot for risc-v are Ubuntu > packages provided (to accompany ubuntu provided qemu 4.2.1) > > My issue while compiling both 13 and current is that compilation after > some time fails with: > > root@freebsd:/usr/src # time make -j8 buildworld > /tmp/build-j8-2.txt > ELF binary type "0" not known. > 17784.134u 21388.907s 1:50:13.83 592.2% 30721+572k 10+2177io 0pf+0w > > I'm curious if this is a know issue either in Qemu or in FreeBSD for > risc-v or if I'm doing anything wrong here? It is a known issue with how we brand FreeBSD/riscv binaries. Jess (cc'd) has a WIP review with a possible fix IIRC. -- John Baldwin From nobody Mon Sep 27 19:24:48 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 0B29417DE4B1 for ; Mon, 27 Sep 2021 19:24:57 +0000 (UTC) (envelope-from jrtc27@jrtc27.com) Received: from mail-wm1-f52.google.com (mail-wm1-f52.google.com [209.85.128.52]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HJCJS6QPwz4cbW for ; Mon, 27 Sep 2021 19:24:56 +0000 (UTC) (envelope-from jrtc27@jrtc27.com) Received: by mail-wm1-f52.google.com with SMTP id 136-20020a1c048e000000b0030d05169e9bso1553755wme.4 for ; Mon, 27 Sep 2021 12:24:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=WNJTNE7UD/cLSAp0LzO8sGgt7LHVlrZc8o2nHA+AV/0=; b=FAViQLV9a5FGsC92XW+QV3i0UQmGOtiLvZCsGEM1oXM7aw8xUk0u551/vbpTS/MtBF RMlFX2MTkrxs/mx0VIS3PPTNPdts8yO39I4mYBW8cKlUwqVAi3bb801HRA64udhqdAj9 fXkaalD8Fglc6wasbRPZ1qkL8Ff+wI377wCIP5XIZroGU6ID2hx2ln30CqVo52On3qi7 br65RLBIe8PpEHLj7MLLJbhUotckaRhwS4pzgwfD5kJMEDvHc7GSp8HSy2g+wRXn2M9x qMxalcG9F1x8zPi5amjWdxIHrkhU3hdoEdbfB/ovXIQuZNS5VdRRHtpuZe2wpvKn/Kpx F3ow== X-Gm-Message-State: AOAM5300P1rhJiILafjwqR4GTfhUPCikYNkmBRm4aPHURXtPn4Vy0YLL IZ8NhMNBiMvDi+oTPvntYhJ+XQ== X-Google-Smtp-Source: ABdhPJynaRVg5TsLXhNMEBaZ2b7rRFebxQl47wZA9K0BLkTZ+RNa3PxnDbodjY6cnjtPo0vFEiK0Jw== X-Received: by 2002:a1c:3586:: with SMTP id c128mr799197wma.78.1632770690018; Mon, 27 Sep 2021 12:24:50 -0700 (PDT) Received: from smtpclient.apple (global-5-143.nat-2.net.cam.ac.uk. [131.111.5.143]) by smtp.gmail.com with ESMTPSA id b7sm21347950wrm.9.2021.09.27.12.24.49 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Sep 2021 12:24:49 -0700 (PDT) Content-Type: text/plain; charset=utf-8 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Subject: Re: ELF binary type "0" not known. (while compiling buildworld on risc-v/qemu) From: Jessica Clarke In-Reply-To: Date: Mon, 27 Sep 2021 20:24:48 +0100 Cc: Karel Gardas , current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: John Baldwin X-Mailer: Apple Mail (2.3654.120.0.1.13) X-Rspamd-Queue-Id: 4HJCJS6QPwz4cbW X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On 27 Sep 2021, at 20:22, John Baldwin wrote: >=20 > On 9/27/21 7:40 AM, Karel Gardas wrote: >> Hello, >> I'm playing with compiling freebsd 13 (releng/13.0 2 days ago) and >> current (git HEAD as of today) on qemu-5.1.0/qemu-6.1.0 on risv64 >> platform. The emulator invocation is: >> qemu-system-riscv64 -machine virt -smp 8 -m 16G -nographic -device >> virtio-blk-device,drive=3Dhd -drive >> file=3DFreeBSD-14.0-CURRENT-riscv-riscv64.qcow2,if=3Dnone,id=3Dhd = -device >> virtio-net-device,netdev=3Dnet -netdev = user,id=3Dnet,hostfwd=3Dtcp::2233-:22 >> -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf -kernel >> /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -object >> rng-random,filename=3D/dev/urandom,id=3Drng -device >> virtio-rng-device,rng=3Drng -nographic -append "root=3DLABEL=3Drootfs >> console=3DttyS0" >> and the host is Ubuntu 20.04.x LTS. Both qemu 5.1.0 and qemu 6.1.0 = are >> compiled from, source, but both OpenSBI and u-boot for risc-v are = Ubuntu >> packages provided (to accompany ubuntu provided qemu 4.2.1) >> My issue while compiling both 13 and current is that compilation = after >> some time fails with: >> root@freebsd:/usr/src # time make -j8 buildworld > = /tmp/build-j8-2.txt >> ELF binary type "0" not known. >> 17784.134u 21388.907s 1:50:13.83 592.2% 30721+572k 10+2177io 0pf+0w >> I'm curious if this is a know issue either in Qemu or in FreeBSD for >> risc-v or if I'm doing anything wrong here? >=20 > It is a known issue with how we brand FreeBSD/riscv binaries. Jess > (cc'd) has a WIP review with a possible fix IIRC. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D258358 and https://reviews.freebsd.org/D31323. The latter needs reworking because GCC doesn=E2=80=99t use all of our CSU files and instead provides its = own that we have no control over. The bug report documents a one-line workaround. Jess From nobody Mon Sep 27 19:54:28 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 11EC917E18B9 for ; Mon, 27 Sep 2021 19:54:30 +0000 (UTC) (envelope-from markjdb@gmail.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) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HJCyY1SyMz4hLq; Mon, 27 Sep 2021 19:54:29 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qk1-x72e.google.com with SMTP id q81so34503434qke.5; Mon, 27 Sep 2021 12:54:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=gwd5ulBngkneS2j0AB8Vq4VQ9mIkA+8CvVv6ljMjz1o=; b=Ukv5aTzZt+1pRKjWgMxybq+9rOJdSYh4xg7uEQu9mAxa52lP/+vflOdqOWb6ACN6kN i06vzYQkcueIHJAD8yH2cWtFrwXA3qfQ8LE4VCo093E6PEMgnLeyHFmJRPw1ZIIoQse3 WAocKB/bKm+Mal1HAu6da4FMVOmMLgWYI/oADfxNg3vVw4qyG6X07IDkOCFjvC3yuTSS l8/vc9t+UieSnA85I521fNFmlDExi+mEK40RPAv5bCaaYq3ZwjIZNvCGQeqAds0/HsYG Wx4q+dyl8TapbaXe3ALDTaR5PHp9OG2uBKg+/ZK1Z2NsL5OHaxpuVLNc5b4w6f/vfk4f +2Qg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to; bh=gwd5ulBngkneS2j0AB8Vq4VQ9mIkA+8CvVv6ljMjz1o=; b=XlZ6zqNaWzjDtKCo2p8rRD3QAI+hzbjtdQzunLHdKzCo8GWmJuFDsFyfYPeAUYXGbd YIIpriyLygschAnZzJVDB4/Yh4Ced+b/D/p86efK432qzD404iV3wg8XN2zt5htHolq4 MVK1v37f8Xg4qFEpfjQ01oiiJtZ9sZL+9wRkeVJLmIrdM5CO5oC8Ad3lemtyOLliLluX 1seUWsYJbBucf7E32HdjatufU71dG6M2WZzPhh8UfeaUtEgz8U2Kzxk/iDTBr4VXpi9v PLNun4F+fRw/OJlvdHkF5rWyzqVR1OfArDtkcm0wEh1/NfLwgJ9OKqfvW+8TtmHuMtix uI7g== X-Gm-Message-State: AOAM530u/RL3rls8r5LhnWnpEKs57SwftaTbdaWDI8uBDp6ZM3Jbgvcz oJgea7B8NQWIjs+DmsDqqZHRqWpkV/ea7A== X-Google-Smtp-Source: ABdhPJwgfGlkbi9c0Ypd3caqbcY9L5ZcK88F8MQZU/l3vHvb3Pk7UtG2aszzdCV0juPN2iyD1QkTUQ== X-Received: by 2002:a37:a155:: with SMTP id k82mr1723004qke.349.1632772468570; Mon, 27 Sep 2021 12:54:28 -0700 (PDT) Received: from nuc ([142.126.175.192]) by smtp.gmail.com with ESMTPSA id i67sm13156905qkd.90.2021.09.27.12.54.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 27 Sep 2021 12:54:28 -0700 (PDT) Date: Mon, 27 Sep 2021 15:54:28 -0400 From: Mark Johnston To: Alan Somers Cc: David Chisnall , freebsd-current Subject: Re: Building ZFS disk images Message-ID: References: <16473d5f-1727-233a-7a95-a21c5b48b9ce@FreeBSD.org> <8ab3d440-889e-25d4-71f9-e7ae2386daeb@FreeBSD.org> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4HJCyY1SyMz4hLq X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=Ukv5aTzZ; dmarc=none; spf=pass (mx1.freebsd.org: domain of markjdb@gmail.com designates 2607:f8b0:4864:20::72e as permitted sender) smtp.mailfrom=markjdb@gmail.com X-Spamd-Result: default: False [-2.70 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::72e:from]; FORGED_SENDER(0.30)[markj@freebsd.org,markjdb@gmail.com]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[markj@freebsd.org,markjdb@gmail.com]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: N On Thu, Aug 05, 2021 at 10:54:19AM -0500, Alan Somers wrote: > There's this: > https://openzfs.github.io/openzfs-docs/man/8/zpool-reguid.8.html . I > haven't used it myself. Would it be useful to have an rc.d script that can run this, probably just on the root pool? It could be configured to run only upon the first boot, like growfs already does. > On Thu, Aug 5, 2021, 9:29 AM David Chisnall wrote: > > > On 05/08/2021 13:53, Alan Somers wrote: > > > I don't know of any way to do it using the official release scripts > > > either. One problem is that every ZFS pool and file system is supposed > > > to have a unique GUID. So any kind of ZFS release builder would need to > > > re-guid the pool on first boot. > > > > Is there a tool / command to do this? I've hit this problem in the > > past: I have multiple FreeBSD VMs that are all created from the same > > template and if one dies I can't import its zpool into another because > > they have the same UUID. > > > > It doesn't matter for modern deployments where the VM is stateless and > > reimaged periodically but it's annoying for classic deployments where I > > have things I care about on the VM. > > > > David From nobody Mon Sep 27 20:09:48 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 8C44117E3126 for ; Mon, 27 Sep 2021 20:10:06 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi1-f173.google.com (mail-oi1-f173.google.com [209.85.167.173]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HJDJZ3G6rz4jvW; Mon, 27 Sep 2021 20:10:06 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi1-f173.google.com with SMTP id v10so27068599oic.12; Mon, 27 Sep 2021 13:10:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=na784F3UyqRHdXCn3gq/5fp+MrnRNd/s6YJvxI+zlI0=; b=YVjkJCMyKg4jdW49Wa8+YtsbdZAJ1QzjpvS36KI5NmzjJ5GniYoEKgMZdCvcR945fo KXFBW4+yg7k2ZIJk7Q5cpu6GuvlvEvvPHXlj0DVyZZYZmi8JtShRropG5wdqfoqgF63f gWmI4PjGAlJIelB0zW7kU2/oyhmJVNSpL5S70Pb4Wv4O4XkQ67CtEJmGm7t0QuipULcy RUXQbcJ2OB/Yq7CHhuiqlXO+cpx4lBkYRogGAiJmW0xssxoSJZfPdBCCfYHtRiem6A6b swlowpCgMCLiwWSlrd6eBEfMSytzu9ubheyk4yeiaAJwo2nFqkWsVqi5MhiiZIusDZSc paFg== X-Gm-Message-State: AOAM532M34o7VIKgm0pSK1c1kLV7DnXqXqVbY+AjR9I5bIgK0ZB0B4Ge nQ8UDjXJVl0amnTHlME9EP4vjG1zlUSXrW7r3CumACwa X-Google-Smtp-Source: ABdhPJyjadRJfWfOpXNXYGxZnX7oFI3pLmDn3gBTL8Ac0asNkIHXgWF8f/dhkFvuVQHrxEiQRQMuAbBNYh8JcpXdAAs= X-Received: by 2002:a05:6808:302c:: with SMTP id ay44mr725349oib.73.1632773399932; Mon, 27 Sep 2021 13:09:59 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <16473d5f-1727-233a-7a95-a21c5b48b9ce@FreeBSD.org> <8ab3d440-889e-25d4-71f9-e7ae2386daeb@FreeBSD.org> In-Reply-To: From: Alan Somers Date: Mon, 27 Sep 2021 14:09:48 -0600 Message-ID: Subject: Re: Building ZFS disk images To: Mark Johnston Cc: David Chisnall , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4HJDJZ3G6rz4jvW X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Mon, Sep 27, 2021 at 1:54 PM Mark Johnston wrote: > > On Thu, Aug 05, 2021 at 10:54:19AM -0500, Alan Somers wrote: > > There's this: > > https://openzfs.github.io/openzfs-docs/man/8/zpool-reguid.8.html . I > > haven't used it myself. > > Would it be useful to have an rc.d script that can run this, probably > just on the root pool? It could be configured to run only upon the > first boot, like growfs already does. Absolutely! > > > On Thu, Aug 5, 2021, 9:29 AM David Chisnall wrote: > > > > > On 05/08/2021 13:53, Alan Somers wrote: > > > > I don't know of any way to do it using the official release scripts > > > > either. One problem is that every ZFS pool and file system is supposed > > > > to have a unique GUID. So any kind of ZFS release builder would need to > > > > re-guid the pool on first boot. > > > > > > Is there a tool / command to do this? I've hit this problem in the > > > past: I have multiple FreeBSD VMs that are all created from the same > > > template and if one dies I can't import its zpool into another because > > > they have the same UUID. > > > > > > It doesn't matter for modern deployments where the VM is stateless and > > > reimaged periodically but it's annoying for classic deployments where I > > > have things I care about on the VM. > > > > > > David From nobody Tue Sep 28 12:41:03 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 41E4317C9851 for ; Tue, 28 Sep 2021 12:41:17 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4HJfJC5lQvz4scT; Tue, 28 Sep 2021 12:41:15 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from kalamity.joker.local (123-48-130-181.area1b.commufa.jp [123.48.130.181]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 18SCf4rC007059; Tue, 28 Sep 2021 21:41:05 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Tue, 28 Sep 2021 21:41:03 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Cc: Konstantin Belousov , Alexander Motin , joh.hendriks@gmail.com Subject: Re: latest current fails to boot. Message-Id: <20210928214103.32b36a3b627b51700389970a@dec.sakura.ne.jp> In-Reply-To: <9a9a43f9-0474-0c32-afb9-13c2f7c33e51@FreeBSD.org> References: <20210922230905.79a494a4ddbecd7d6b8179ea@dec.sakura.ne.jp> <36221848-2b85-4a60-fd27-d4bf83d4571e@FreeBSD.org> <20210926102347.c538169dddec5f2ff50d8e4c@dec.sakura.ne.jp> <9a9a43f9-0474-0c32-afb9-13c2f7c33e51@FreeBSD.org> Reply-To: junchoon@dec.sakura.ne.jp Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4HJfJC5lQvz4scT X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp X-Spamd-Result: default: False [1.67 / 15.00]; HAS_REPLYTO(0.00)[junchoon@dec.sakura.ne.jp]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; HAS_ORG_HEADER(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[123.48.130.181:received]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; MID_RHS_MATCH_FROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_SPAM_SHORT(0.77)[0.772]; NEURAL_HAM_LONG(-1.00)[-1.000]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[sakura.ne.jp]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_CC(0.00)[gmail.com,FreeBSD.org]; RCVD_COUNT_TWO(0.00)[2]; SUSPICIOUS_RECIPS(1.50)[] X-ThisMailContainsUnwantedMimeParts: N On Sun, 26 Sep 2021 12:16:55 -0400 Alexander Motin wrote: > Thank you for the notification. 08063e9f98a should fix the hang. Thanks for the fix! Rebuilt, Several reboots with varying 0, 1, commented out whole line for kern.sched.steal_thresh and all went fine. > I just want to add that lowering kern.sched.steal_thresh below 2 should > not be a proper fix for any problem, but only a workaround. I guess > either some CPU can't wake up from sleep for too long, or the wakeup > interrupt is not properly sent to it when the load is assigned. In such > case stealing makes other CPU to do the work instead. It would be good > to find and fix the real problem. For me (with Core i7-8750H), lowering kern.sched.steal_thresh didn't made significant improvement but had no reason to go back to default. *As sched_ule got modified now, I'm trying default kern.sched.steal_thresh value now. In the other hand, at least some Ryzen users seem to have much more severe problem than me and the workaround make significant imrovement. > On 25.09.2021 21:47, Konstantin Belousov wrote: > > On Sun, Sep 26, 2021 at 10:23:47AM +0900, Tomoaki AOKI wrote: > >> On Sat, 25 Sep 2021 23:46:48 +0300 > >> Andriy Gapon wrote: > >> > >>> On 25/09/2021 19:10, Johan Hendriks wrote: > >>>> For me i had kern.sched.steal_thresh=1 in my sysctl as i use this machine mainly > >>>> for tests and so on. > >>>> By removing this sysctl the system boots again. I already used the latest > >>>> snapshot and that booted fine. > >>> > >>> Might have something to do with > >>> https://cgit.FreeBSD.org/src/commit/?id=bd84094a51c4648a7c97ececdaccfb30bc832096 > >>> > >>> -- > >>> Andriy Gapon > >> > >> Commenting out kern.sched.steal_thresh=0 line in /etc/sysctl.conf let > >> me boot fine. No other setting of kern.sched.* affected. > >> I've introduced the setting by reading posts [1] and [2] on > >> freebsd-current ML. Thanks for the hint, Jan! > >> > >> Andriy, I took time to bi-sect and determined the commit triggered > >> this issue was e745d729be60. [3] > >> Worked OK even with kern.sched.steal_thresh=0 at a342ecd326ee. [4] > >> > >> Tested commits are as below (tested order, not using git bisect): > >> 0b79a76f8487: [Known to be OK] > >> 8db1669959ce: [Problematic rev I first encountered] > >> 0f6829488ef3: OK > >> df8dd6025af8: OK > >> 4f917847c903: OK > >> e745d729be60: NG! > >> bd84094a51c4: OK > >> a342ecd326ee: OK > >> > >> Konstantin, no more chance to get into ddb on hang up until my previous > >> post. ^T never worked on hang up situation. Sory. But does info above > >> help? > > Let the author of the commit look. > > > >> > >> > >> [1] > >> https://lists.freebsd.org/pipermail/freebsd-current/2021-March/079237.html > >> > >> [2] > >> https://lists.freebsd.org/pipermail/freebsd-current/2021-March/079240.html > >> > >> [3] > >> https://lists.freebsd.org/pipermail/dev-commits-src-main/2021-September/007513.html > >> > >> [4] > >> https://lists.freebsd.org/pipermail/dev-commits-src-main/2021-September/007512.html > >> > >> -- > >> Tomoaki AOKI > > -- > Alexander Motin > -- Tomoaki AOKI From nobody Tue Sep 28 15:48:35 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 7298617DD65B for ; Tue, 28 Sep 2021 15:48: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 4HJkSX00CDz3lHH; Tue, 28 Sep 2021 15:48:43 +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 18SFmZn8075723; Tue, 28 Sep 2021 08:48:35 -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 18SFmZjp075722; Tue, 28 Sep 2021 08:48:35 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <202109281548.18SFmZjp075722@gndrsh.dnsmgr.net> Subject: Re: Building ZFS disk images In-Reply-To: To: Alan Somers Date: Tue, 28 Sep 2021 08:48:35 -0700 (PDT) CC: Mark Johnston , David Chisnall , freebsd-current X-Mailer: ELM [version 2.4ME+ PL121h (25)] List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 4HJkSX00CDz3lHH X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N > On Mon, Sep 27, 2021 at 1:54 PM Mark Johnston wrote: > > > > On Thu, Aug 05, 2021 at 10:54:19AM -0500, Alan Somers wrote: > > > There's this: > > > https://openzfs.github.io/openzfs-docs/man/8/zpool-reguid.8.html . I > > > haven't used it myself. > > > > Would it be useful to have an rc.d script that can run this, probably > > just on the root pool? It could be configured to run only upon the > > first boot, like growfs already does. > > Absolutely! Ewwwwwwwwww! :-) > > > > > On Thu, Aug 5, 2021, 9:29 AM David Chisnall wrote: > > > > > > > On 05/08/2021 13:53, Alan Somers wrote: > > > > > I don't know of any way to do it using the official release scripts > > > > > either. One problem is that every ZFS pool and file system is supposed > > > > > to have a unique GUID. So any kind of ZFS release builder would need to ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > > re-guid the pool on first boot. Isnt the proper place to solve this lack of Unique UUID creation in the tool(s) that are creating the zfs pool in the first place. Fixing it "post boot" seems to be a far to late hack and doesnt fix any of the situations where one might import these pools between creation and first boot. > > > > > > > > Is there a tool / command to do this? I've hit this problem in the > > > > past: I have multiple FreeBSD VMs that are all created from the same > > > > template and if one dies I can't import its zpool into another because > > > > they have the same UUID. > > > > > > > > It doesn't matter for modern deployments where the VM is stateless and > > > > reimaged periodically but it's annoying for classic deployments where I > > > > have things I care about on the VM. > > > > > > > > David > > -- Rod Grimes rgrimes@freebsd.org From nobody Tue Sep 28 15:58:56 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id A195517DF669 for ; Tue, 28 Sep 2021 15:59:14 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi1-f175.google.com (mail-oi1-f175.google.com [209.85.167.175]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HJkhf44jQz3n8n; Tue, 28 Sep 2021 15:59:14 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi1-f175.google.com with SMTP id a3so30517520oid.6; Tue, 28 Sep 2021 08:59:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=NRT2BSr1FViiQJ0NCCoaJO1CdkQkYYlkr2HiipwDxAM=; b=UUIRo3fNl9lOUQVNiJopKfKde0zktPejhqdhJmOXRX9UuL3jNaaMb5UMuso6FXxQWP zl2IRY3ic4IYiA9jOe+I1ADr17FN8250vIIOvzz8AxrRniH0ijCbeSiRnw9myTesZ+Y6 i6/dQxJbyp0/oA7YF+PHWilpQKT5chmF/QjrynPbvy7N1bVbKd1mLWWnsr8xJXthWYHL c67X/4IgrUNzMol7FrEYRSIxaUvDBvPotlV2yaSg7z6rl5Nofqj35AQKj1XPM+6zqerp Bth4jzqfP/tPsJeL1ZLPlcS2y2Qn/+13Cq9V0V1szNYjSDwFy5aYvru/TkzFD+L2rfDQ VbSA== X-Gm-Message-State: AOAM531B0DxHMKpMYcRbVF28ad5Hz1lG/uc0XYQFHEhlGumZQpNospKE tOrFDC03NIp+w7FvQxXUYDQgw1Eh/yOv03XDdFAD1cpa X-Google-Smtp-Source: ABdhPJy1rOoTH1YMTUgAVAJa+N9KHU5JUZNoFMEmH7NA76L3OkkYLSJWu5i04vfyH5XRu1RQwh9EClP1MJzQJO0uVFM= X-Received: by 2002:aca:1b09:: with SMTP id b9mr4226041oib.55.1632844748037; Tue, 28 Sep 2021 08:59:08 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <202109281548.18SFmZjp075722@gndrsh.dnsmgr.net> In-Reply-To: <202109281548.18SFmZjp075722@gndrsh.dnsmgr.net> From: Alan Somers Date: Tue, 28 Sep 2021 09:58:56 -0600 Message-ID: Subject: Re: Building ZFS disk images To: "Rodney W. Grimes" Cc: Alan Somers , Mark Johnston , David Chisnall , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4HJkhf44jQz3n8n X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Tue, Sep 28, 2021 at 9:48 AM Rodney W. Grimes wrote: > > > On Mon, Sep 27, 2021 at 1:54 PM Mark Johnston wrote: > > > > > > On Thu, Aug 05, 2021 at 10:54:19AM -0500, Alan Somers wrote: > > > > There's this: > > > > https://openzfs.github.io/openzfs-docs/man/8/zpool-reguid.8.html . I > > > > haven't used it myself. > > > > > > Would it be useful to have an rc.d script that can run this, probably > > > just on the root pool? It could be configured to run only upon the > > > first boot, like growfs already does. > > > > Absolutely! > > Ewwwwwwwwww! :-) > > > > > > > > On Thu, Aug 5, 2021, 9:29 AM David Chisnall wrote: > > > > > > > > > On 05/08/2021 13:53, Alan Somers wrote: > > > > > > I don't know of any way to do it using the official release scripts > > > > > > either. One problem is that every ZFS pool and file system is supposed > > > > > > to have a unique GUID. So any kind of ZFS release builder would need to > ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > > > re-guid the pool on first boot. > > Isnt the proper place to solve this lack of Unique UUID creation > in the tool(s) that are creating the zfs pool in the first place. > > Fixing it "post boot" seems to be a far to late hack and doesnt > fix any of the situations where one might import these pools > between creation and first boot. No, because you might create a VM image once, then instantiate it dozens or thousands of times. The firstboot solution is great because it lets you reuse the same image file. > > > > > > > > > > > Is there a tool / command to do this? I've hit this problem in the > > > > > past: I have multiple FreeBSD VMs that are all created from the same > > > > > template and if one dies I can't import its zpool into another because > > > > > they have the same UUID. > > > > > > > > > > It doesn't matter for modern deployments where the VM is stateless and > > > > > reimaged periodically but it's annoying for classic deployments where I > > > > > have things I care about on the VM. > > > > > > > > > > David > > > > > > -- > Rod Grimes rgrimes@freebsd.org From nobody Tue Sep 28 16:15:51 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 3B4A917E1368 for ; Tue, 28 Sep 2021 16:15:54 +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 4HJl3s5dKGz3qFG; Tue, 28 Sep 2021 16:15:53 +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 18SGFpjN075923; Tue, 28 Sep 2021 09:15:51 -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 18SGFpkl075922; Tue, 28 Sep 2021 09:15:51 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <202109281615.18SGFpkl075922@gndrsh.dnsmgr.net> Subject: Re: Building ZFS disk images In-Reply-To: To: Alan Somers Date: Tue, 28 Sep 2021 09:15:51 -0700 (PDT) CC: "Rodney W. Grimes" , Mark Johnston , David Chisnall , freebsd-current X-Mailer: ELM [version 2.4ME+ PL121h (25)] List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 4HJl3s5dKGz3qFG X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N > On Tue, Sep 28, 2021 at 9:48 AM Rodney W. Grimes > wrote: > > > > > On Mon, Sep 27, 2021 at 1:54 PM Mark Johnston wrote: > > > > > > > > On Thu, Aug 05, 2021 at 10:54:19AM -0500, Alan Somers wrote: > > > > > There's this: > > > > > https://openzfs.github.io/openzfs-docs/man/8/zpool-reguid.8.html . I > > > > > haven't used it myself. > > > > > > > > Would it be useful to have an rc.d script that can run this, probably > > > > just on the root pool? It could be configured to run only upon the > > > > first boot, like growfs already does. > > > > > > Absolutely! > > > > Ewwwwwwwwww! :-) > > > > > > > > > > > On Thu, Aug 5, 2021, 9:29 AM David Chisnall wrote: > > > > > > > > > > > On 05/08/2021 13:53, Alan Somers wrote: > > > > > > > I don't know of any way to do it using the official release scripts > > > > > > > either. One problem is that every ZFS pool and file system is supposed > > > > > > > to have a unique GUID. So any kind of ZFS release builder would need to > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > > > > re-guid the pool on first boot. > > > > Isnt the proper place to solve this lack of Unique UUID creation > > in the tool(s) that are creating the zfs pool in the first place. > > > > Fixing it "post boot" seems to be a far to late hack and doesnt > > fix any of the situations where one might import these pools > > between creation and first boot. > > No, because you might create a VM image once, then instantiate it > dozens or thousands of times. The firstboot solution is great because > it lets you reuse the same image file. I would continue to argue that the place to fix this is in the "instantiate tool". ESXI vmfs deals with this all the time when you clone a disk. And again the "fix at boot" does not deal with the problem in that if I "instatiate" 10 copies of a zpool for VM's and then try to mount 2 of them at once on the host this problem rares it head. Fix the problem as close to point of creation as possible for minimal issues in all operations for everyone. > > > > > > > > > > > > > > > Is there a tool / command to do this? I've hit this problem in the > > > > > > past: I have multiple FreeBSD VMs that are all created from the same > > > > > > template and if one dies I can't import its zpool into another because > > > > > > they have the same UUID. > > > > > > > > > > > > It doesn't matter for modern deployments where the VM is stateless and > > > > > > reimaged periodically but it's annoying for classic deployments where I > > > > > > have things I care about on the VM. > > > > > > > > > > > > David > > > > > > > > > > -- > > Rod Grimes rgrimes@freebsd.org > -- Rod Grimes rgrimes@freebsd.org From nobody Tue Sep 28 16:23:28 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 7A0A417E2AD8 for ; Tue, 28 Sep 2021 16:23:45 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi1-f177.google.com (mail-oi1-f177.google.com [209.85.167.177]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HJlDx31SZz3rJc; Tue, 28 Sep 2021 16:23:45 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi1-f177.google.com with SMTP id n64so11298466oih.2; Tue, 28 Sep 2021 09:23:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=q28fKIXUCz+xxA/4OpsflrnQCMUjCB6Szp9ePyHL61U=; b=eCr01voUkRDrhVqxyOjNB9uUAkNuVP+9MTgLZY5m1ZVepbZzqu2LxceWifRSkNWPRm tgY0AKzl0nETdNfi+uxcP8uyQqbUEQ7WGF6GNhAcHlzsJlYVvG/s6YQnlQNFy/hRu8zK p2QzaN81xOJN+jaTKuL/+ukGh4Ej4nwKwsNSTSyc0UOvPBcauzCb+jgzJxfPs2CQJ7ex NzEsnbyih+Tk29bXnrkh2zfFqY5lLT7WCnyErdQxM5pxUabf5/D4IaR6OpkAXVfu4TEC rgHNSPGn0F7hMSd+Nil+LFCSuEtXvHcoSUE80lL6Vu/6VFE2TG8j3x/HlFhQ2GC9yyQ1 cIEg== X-Gm-Message-State: AOAM532ewfYMVVlPuuRThJxTdfuI/IuL5jJeD6mUuk+oaFf7Q8CW+9j4 IA4w7FLPJcBNVJNsRyDYR71ltxGQ5bSzHFo/a+V9Civt X-Google-Smtp-Source: ABdhPJww581kvglamxRQbTsc0I9MEoCOE60PTNy2BmXHZn48H91KB3LDTTzV1VWTG7JXkhgDeiGyt6vg+YPvA70K6r4= X-Received: by 2002:a54:4e94:: with SMTP id c20mr4249737oiy.57.1632846219307; Tue, 28 Sep 2021 09:23:39 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <202109281615.18SGFpkl075922@gndrsh.dnsmgr.net> In-Reply-To: <202109281615.18SGFpkl075922@gndrsh.dnsmgr.net> From: Alan Somers Date: Tue, 28 Sep 2021 10:23:28 -0600 Message-ID: Subject: Re: Building ZFS disk images To: "Rodney W. Grimes" Cc: Mark Johnston , David Chisnall , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4HJlDx31SZz3rJc X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Tue, Sep 28, 2021 at 10:15 AM Rodney W. Grimes wrote: > > > On Tue, Sep 28, 2021 at 9:48 AM Rodney W. Grimes > > wrote: > > > > > > > On Mon, Sep 27, 2021 at 1:54 PM Mark Johnston wrote: > > > > > > > > > > On Thu, Aug 05, 2021 at 10:54:19AM -0500, Alan Somers wrote: > > > > > > There's this: > > > > > > https://openzfs.github.io/openzfs-docs/man/8/zpool-reguid.8.html . I > > > > > > haven't used it myself. > > > > > > > > > > Would it be useful to have an rc.d script that can run this, probably > > > > > just on the root pool? It could be configured to run only upon the > > > > > first boot, like growfs already does. > > > > > > > > Absolutely! > > > > > > Ewwwwwwwwww! :-) > > > > > > > > > > > > > > On Thu, Aug 5, 2021, 9:29 AM David Chisnall wrote: > > > > > > > > > > > > > On 05/08/2021 13:53, Alan Somers wrote: > > > > > > > > I don't know of any way to do it using the official release scripts > > > > > > > > either. One problem is that every ZFS pool and file system is supposed > > > > > > > > to have a unique GUID. So any kind of ZFS release builder would need to > > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > > > > > re-guid the pool on first boot. > > > > > > Isnt the proper place to solve this lack of Unique UUID creation > > > in the tool(s) that are creating the zfs pool in the first place. > > > > > > Fixing it "post boot" seems to be a far to late hack and doesnt > > > fix any of the situations where one might import these pools > > > between creation and first boot. > > > > No, because you might create a VM image once, then instantiate it > > dozens or thousands of times. The firstboot solution is great because > > it lets you reuse the same image file. > > I would continue to argue that the place to fix this is in the > "instantiate tool". ESXI vmfs deals with this all the time > when you clone a disk. And again the "fix at boot" does not > deal with the problem in that if I "instatiate" 10 copies of > a zpool for VM's and then try to mount 2 of them at once on > the host this problem rares it head. Fix the problem as close > to point of creation as possible for minimal issues in all > operations for everyone. But that requires ESXI, or whatever VM system you're using, to know about ZFS and GPT, and to know to look for a zpool on the 3rd partition, right? That seems like a lot to ask, especially since the logic would have to be duplicated for ESXI, vm-bhyve, OpenNebula, etc etc. > > > > > > > > > > > > > > > > > > > > Is there a tool / command to do this? I've hit this problem in the > > > > > > > past: I have multiple FreeBSD VMs that are all created from the same > > > > > > > template and if one dies I can't import its zpool into another because > > > > > > > they have the same UUID. > > > > > > > > > > > > > > It doesn't matter for modern deployments where the VM is stateless and > > > > > > > reimaged periodically but it's annoying for classic deployments where I > > > > > > > have things I care about on the VM. > > > > > > > > > > > > > > David > > > > > > > > > > > > > > -- > > > Rod Grimes rgrimes@freebsd.org > > > > -- > Rod Grimes rgrimes@freebsd.org From nobody Tue Sep 28 17:46:07 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 03C4817EAD42 for ; Tue, 28 Sep 2021 17:46:16 +0000 (UTC) (envelope-from me+freebsd@igalic.co) Received: from mail1.protonmail.ch (mail1.protonmail.ch [185.70.40.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HJn475xKcz4VxP; Tue, 28 Sep 2021 17:46:15 +0000 (UTC) (envelope-from me+freebsd@igalic.co) Date: Tue, 28 Sep 2021 17:46:07 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=igalic.co; s=protonmail; t=1632851167; bh=/QNh6cQLetrvqZ95vmKXWdEubDY1s9SWwXQ+g4Haids=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=PBDhi5xQqgeNCMlas8N+TXihEirjdshNWBoQQmrwfSzGaSWlUszo8vsrY5kinBtgK QvlRU17NhFHD22o0c/NnHryJ76NW1z9rG22EvfhwOj6hzpQmprD2GM3NlQpLCl7+C/ Q/KXWoUEojnnnQ+44LzDhd17syjgrXlKUUdwwwzRept/bGlsJmVZAxTOJEWIvXssS0 /TsxXRROvmofJCyOKriOyWGTv5Ps9EwuYjp6xvS8/MPMBR1EuustbUDN1gP2oyKDup Ev9h5biGTCXt+sn+nCG37HnVQexQcN5X8qjpCT2uLbK0vHI+z8Sp0SVv8H0as80Mvn 0lzBYfPxJ2ang== To: "Rodney W. Grimes" From: =?utf-8?Q?Mina_Gali=C4=87?= Cc: Alan Somers , Mark Johnston , David Chisnall , freebsd-current Reply-To: =?utf-8?Q?Mina_Gali=C4=87?= Subject: Re: Building ZFS disk images Message-ID: In-Reply-To: <202109281615.18SGFpkl075922@gndrsh.dnsmgr.net> References: <202109281615.18SGFpkl075922@gndrsh.dnsmgr.net> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=10.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mailout.protonmail.ch X-Rspamd-Queue-Id: 4HJn475xKcz4VxP X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[freebsd] X-ThisMailContainsUnwantedMimeParts: N =E2=80=90=E2=80=90snip--- *puts on cloud-init contributor hat* > > No, because you might create a VM image once, then instantiate it > > dozens or thousands of times. The firstboot solution is great because > > it lets you reuse the same image file. > > I would continue to argue that the place to fix this is in the > "instantiate tool". ESXI vmfs deals with this all the time > when you clone a disk. And again the "fix at boot" does not > deal with the problem in that if I "instatiate" 10 copies of > a zpool for VM's and then try to mount 2 of them at once on > the host this problem rares it head. Fix the problem as close > to point of creation as possible for minimal issues in all > operations for everyone. a lot of folks use cloud-init for provisioning different Unices onto different virtualisation (cloud) platforms. We could fix it there. We already extend paritions, filesystems and ZFS pools in cloud-init. now, again, one could argue that's the wrong place to do any of that, and we should just be using firstboot. But the problem seems to be that a lot folks out there got into the habit of creating and publishing (FreeBSD) images, seem to have forgotten or never knew about firstboot, and don't to set it. Mina Gali=C4=87 Web: https://igalic.co/ PkgBase: https://alpha.pkgbase.live/ From nobody Tue Sep 28 18:04:18 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 2B7E617ECA7E for ; Tue, 28 Sep 2021 18:04:32 +0000 (UTC) (envelope-from mpp302@gmail.com) Received: from mail-ed1-f48.google.com (mail-ed1-f48.google.com [209.85.208.48]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HJnTC0Jcfz4YGw for ; Tue, 28 Sep 2021 18:04:31 +0000 (UTC) (envelope-from mpp302@gmail.com) Received: by mail-ed1-f48.google.com with SMTP id l8so37489639edw.2 for ; Tue, 28 Sep 2021 11:04:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:to:references:from:subject:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=YqndLEacGhJC3lvY6/3tADQhFGANOZtfKgeny8GEz+A=; b=txutaRB+HCMGnDURuGLjPKtLxd1elTj1DcJzL4AXOd4ctKZiF+b0pViBSUoduRjbRa vGVMOlk3THBWPUSvOs06kKYchpIDqLWw9IvCy/84MGQH3oZr+6JyXNOGVJE3bLy2p40v 6cV96uG1YOoUM77S16kXOJWv8MXMl9aFHJljfsltdY7hRiAd2Fcyltuiz/VuX2+xRMn9 HxpQb8ZPbBadtuKDvZCth4AFJdg56THerh+4TAsao78SO0FNcpKDutJVIJ9ZgmnwuV0O CauXkslSMrqIfBIPANEdAYt9WsMObKduwdreVsOPrvbiwxgbs9J+WIFEyzdWecrVaE/u V4tQ== X-Gm-Message-State: AOAM533XpYE6l3xp3cMP0OmURIOveI92zgXN3XwFiLZJLjEJ1P8vOBpA Yl9eK9P4v9NSUYX5OM3dnzaRfublp5VLLA== X-Google-Smtp-Source: ABdhPJzxt7zyTQOWbOPh3Fq9RPn6CEckltRWwWWBM/AjnQudlDGXhnu4jhlyxwnZTAXGXsxVEnpTTA== X-Received: by 2002:a50:9d07:: with SMTP id v7mr8953716ede.185.1632852262100; Tue, 28 Sep 2021 11:04:22 -0700 (PDT) Received: from ?IPv6:2a02:8109:9880:1d70:5e5f:67ff:fef4:ffd8? ([2a02:8109:9880:1d70:5e5f:67ff:fef4:ffd8]) by smtp.gmail.com with ESMTPSA id la1sm11004517ejc.48.2021.09.28.11.04.20 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 28 Sep 2021 11:04:21 -0700 (PDT) To: freebsd-current@freebsd.org References: <20210922083645.4vnoajyvwq6wfhdf@aniel.nours.eu> <97ebc390-a19e-3203-7016-ce541796eb18@beastielabs.net> From: Mateusz Piotrowski <0mp@FreeBSD.org> Subject: Re: [HEADSUP] making /bin/sh the default shell for root Message-ID: Date: Tue, 28 Sep 2021 20:04:18 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 In-Reply-To: <97ebc390-a19e-3203-7016-ce541796eb18@beastielabs.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Language: en-US X-Rspamd-Queue-Id: 4HJnTC0Jcfz4YGw X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of mpp302@gmail.com designates 209.85.208.48 as permitted sender) smtp.mailfrom=mpp302@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[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]; RCVD_COUNT_THREE(0.00)[3]; ARC_NA(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_IN_DNSWL_NONE(0.00)[209.85.208.48:from]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FORGED_SENDER(0.30)[0mp@FreeBSD.org,mpp302@gmail.com]; DMARC_NA(0.00)[FreeBSD.org]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.208.48:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[0mp@FreeBSD.org,mpp302@gmail.com]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TO_DOM_EQ_FROM_DOM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 23/09/2021 10:55, Hans Ottevanger wrote: > As you mention elsewhere in this thread, usage in scripts is not affect= ed by these changes. And=20 > for interactive use it could be a POLA violation, but the astonishment = would be a positive one. Unfortunately, the switch from csh to sh is going to affect scripts. Take= a look at this (examples=20 below assume that toor uses /bin/sh): # su root -c 'echo $1' abc def abc # su toor -c 'echo $1' abc def def Another example: # ssh -p 2222 root@xxx -- '$@' echo 1 2 3 Illegal variable name. # ssh -p 2222 toor@xxx -- '$@' echo 1 2 3 1 2 3 I've been bitten by this a couple of times when working with some product= ion scripts. I'm afraid=20 changing the default shell to csh may cause a bit of hard-to-debug proble= ms there in the wild. Otherwise, I'd be happy with having sh(1) as the default shell for root. = =46rom my perspective, sh(1)=20 was far more forgiving to my colleagues when they started with FreeBSD. Best, Mateusz Piotrowski From nobody Tue Sep 28 19:08:09 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 2498F17CB7BA; Tue, 28 Sep 2021 19:08:13 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HJptj00jjz4gnP; Tue, 28 Sep 2021 19:08:13 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1632856093; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wZLg+E6l+h1wpdB41WKf0iR2T/NaX5cnRq0KZ2MnNl4=; b=ISFbTzGw383wDbXwQ0IkBbXhz5py5xiQpnj6Bn9D0JCodG6OpPc95YjhFXbLirG2pLnZ8l fr0P50lo8Ys4nhB1YAs6xU/KeyR1HWCGqKeUAvbcHA6gnf2i5EIpH0/BVrQ5Dp/XK6ljfA Pft54cKm3SM71hrgth2c4R0iyFL7LYcJU+wcJjeWAx+VwjfjPJqG8IehB81MRR8e7gwJ4q /0Ra72+MKQdD6Rzc1MsMDq7TSoZ0tlW4sZTv661Ay63ey8jIOE/lsvC+0h7mE1d9X73+Jh 7eHht6mN9xPaxrxBenbkw125Kc9q8hWgWHYaJMkR97Z2jHTmj2xoaVJ3glu5QQ== Received: from mail.xzibition.com (unknown [127.0.1.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id B5575E718; Tue, 28 Sep 2021 19:08:12 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id C629AF9A; Tue, 28 Sep 2021 12:08:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id 65SQQPzdXWq8; Tue, 28 Sep 2021 12:08:09 -0700 (PDT) To: Mark Millard , Ian Lepore DKIM-Filter: OpenDKIM Filter v2.10.3 mail.xzibition.com F2184F89 Cc: freebsd-ports@freebsd.org, freebsd-current , Free BSD References: <187B69AF-9465-41DE-BFD0-A4AA0F7F9068@yahoo.com> <0FE65CAD-EDFF-4CE8-8750-BD4F6971CAA0@yahoo.com> From: Bryan Drewery Organization: FreeBSD Subject: Re: I get odd time reports from poudriere on armv7 system, under a (non-debug) main [so: 14] FreeBSD. Message-ID: <5fe9294c-aabb-57ff-73e0-d9ad2d8efcf5@FreeBSD.org> Date: Tue, 28 Sep 2021 12:08:09 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 In-Reply-To: <0FE65CAD-EDFF-4CE8-8750-BD4F6971CAA0@yahoo.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="4PUY2Owcn9dc6SBJCFPer7297t2JnOLNg" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1632856093; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wZLg+E6l+h1wpdB41WKf0iR2T/NaX5cnRq0KZ2MnNl4=; b=ZaAog1V3dq6omVLasewmf5iWGG0gSOd/i7KOg9jD9+APzEfHe7Bd0EhsKVqzly63AAecXk 6xT+PL+8YzL9stbxBlELIGfp3mdki93cuSa4a6yDVXSy91szR1ZvjuORtpma9nBBfz+2C7 2X1lS/CR/oxQrmsmRz6OaR23LG8LtHpp6zeku8t5D/ZApo9V3CuNxFvEMJdCVVwezFlZ3J 6m+oG5CvUBUcc3FcAtJ0l2LlbbWuyXjSmKZ3b0Yyty5U+TdNV7waMiZAx6Bt2KLMpw71IT zDnruaOftlnzH5mdexeQd+RYvA/szqfaW560kJSNYz+2RylLKm2TlWPCpDPRBA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1632856093; a=rsa-sha256; cv=none; b=jtl0yIsghlmwDetHR2NYIYdgB5Y55m0iJ21HW0+qqXxc4zmwa34qoVYocifitNUbl4qOBA WrIzavU4SR9kOpA79GvHxD5JosJ+43mNrP+Z0kZoFV9ArpeRYGRTZcIn3glmKc2yXf6PkR Zfd8ax5IoXfxKxLd6yO7v6bdd8kf3qcZQdLW6cG9lFvzpPpv+w6M5OfstJglZk5qPw0w1D 7M/22ERoi8z8jXEuqS15psNVOnwyeQgiKEIj8cd8tmOqeM7A2ZX1BEjDiJG0dpGkIboRxq RndZQxZVLNQngkW9MZ65ILh9V4/EgQ9hKuyNlgSeM2BjFwk8Rk/BLWjs9SEnNQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --4PUY2Owcn9dc6SBJCFPer7297t2JnOLNg Content-Type: multipart/mixed; boundary="s2lqJLBhwxirULgNtF0GmsE6sRTJO2DTm"; protected-headers="v1" From: Bryan Drewery To: Mark Millard , Ian Lepore Cc: freebsd-ports@freebsd.org, freebsd-current , Free BSD Message-ID: <5fe9294c-aabb-57ff-73e0-d9ad2d8efcf5@FreeBSD.org> Subject: Re: I get odd time reports from poudriere on armv7 system, under a (non-debug) main [so: 14] FreeBSD. References: <187B69AF-9465-41DE-BFD0-A4AA0F7F9068@yahoo.com> <0FE65CAD-EDFF-4CE8-8750-BD4F6971CAA0@yahoo.com> In-Reply-To: <0FE65CAD-EDFF-4CE8-8750-BD4F6971CAA0@yahoo.com> --s2lqJLBhwxirULgNtF0GmsE6sRTJO2DTm Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 9/26/2021 11:05 PM, Mark Millard wrote: > On 2021-Sep-26, at 10:02, Ian Lepore wrote: >=20 >> On Sun, 2021-09-26 at 02:27 -0700, Mark Millard via freebsd-current >> wrote: >>> On 2021-Sep-25, at 23:25, Mark Millard wrote: >>> >>> >>> [...] >>> if (argc =3D=3D 3 && strcmp(argv[2], "-nsec") =3D=3D 0) >>> printf("%ld.%ld\n", ts.tv_sec, ts.tv_nsec); >> >> There are two problems with this, both the seconds and nanos are >> printed incorrectly. The correct incantation would be >> >> printf("%jd.%09ld\n", (intmax_t)ts.tv_sec, ts.tv_nsec); >> >=20 > Thanks Ian for looking into more than I did last night. >=20 > Based on the following (up to possible e-mail white space issues), > poudriere-devel seems t be working for reporting times: >=20 > # more /usr/ports/ports-mgmt/poudriere-devel/files/patch-clock=20 > --- src/libexec/poudriere/clock/clock.c.orig 2021-09-26 22:24:54.735= 485000 -0700 > +++ src/libexec/poudriere/clock/clock.c 2021-09-26 11:46:12.076362000 -= 0700 > @@ -24,6 +24,7 @@ > * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. > */ > =20 > +#include > #include > #include > #include > @@ -71,8 +72,8 @@ > } else > usage(); > if (argc =3D=3D 3 && strcmp(argv[2], "-nsec") =3D=3D 0) > - printf("%ld.%ld\n", ts.tv_sec, ts.tv_nsec); > + printf("%jd.%09ld\n", (intmax_t)ts.tv_sec, ts.tv_nsec);= > else > - printf("%ld\n", ts.tv_sec); > + printf("%jd\n", (intmax_t)ts.tv_sec); > return (EXIT_SUCCESS); > } Thanks, I've committed it in my local git. Will push out later. --=20 Bryan Drewery --s2lqJLBhwxirULgNtF0GmsE6sRTJO2DTm-- --4PUY2Owcn9dc6SBJCFPer7297t2JnOLNg Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEE+Rc8ssOq6npcih8JNddxu25Gl88FAmFTaBkFAwAAAAAACgkQNddxu25Gl8/W SwgAjhDhlXXll8wRF30GUWY7TZYYW8Gg079tNVnPksEVKk+XxI0FfzQSpYH+vA2igpFVLEiP2tvN DJHzJwiwZiKC32IsmkHledL79uU45jL/6jlGRbM061p+w0aRpKcYRBTmSNjZJXrGoVAdZBWOqyH1 bNPVtA2Yn0Zs3VhTBof0SJHsAEh/OqtVj3b5dMc6aB7RYvbYlcImacg3oktUp4zKgWl1MSw7/ZBF MU87AKZqtPJFVo6d9wVFI6gdbod0ODmorepZxABn2NRss1NLBVY1pRoj8OLi89FuSc36qHQwmprK wtmroOyJSXD5WsQxsjuwt+4bLL1sNjNeChh8R3qsvQ== =VXtP -----END PGP SIGNATURE----- --4PUY2Owcn9dc6SBJCFPer7297t2JnOLNg-- From nobody Wed Sep 29 06:38:50 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 1024A17E5E3B; Wed, 29 Sep 2021 06:38:52 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HK6Cb2bYDz4ZQw; Wed, 29 Sep 2021 06:38:51 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: by mail-vs1-xe2c.google.com with SMTP id h30so1733115vsq.3; Tue, 28 Sep 2021 23:38:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ECLFz+Gxcq/pZ14kUFy8+ArIT1MZ5u+TDZdUJj204AM=; b=E6m29RH/HNWJPCbC5ZV6GFrw9PFqvzm4bV3ZL4D+QlnQt2qruMUX+Ux6cH2/Ty6/M2 mIYMtbF2FBMu7TTYSjl/zgBEYpzph8LpXWs0shUmuNwB8EQvmQ9lWr6Rz4BJ557E+lYM 5xwWLtiBCv1J9FE90fDOyC5OQXn6SE0rym1PTDlKYiM6gyjAd1pXW1uMHz8gihhCAuBN o3ANOkgXOAd36aBnPCuyu+Z1WT5zZRi9mqD0x1RRjxGqPBcGLHJiSJ3MGSZOJHjaw59a T0bsS1RmShwhg/hGIia1ZuX2jdskxeNmghA0VdzL+aoPdL5l1b5g4cQFKRVP0F4x9p+a cDDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ECLFz+Gxcq/pZ14kUFy8+ArIT1MZ5u+TDZdUJj204AM=; b=AwEtD6T9WWTC1OqDcacHa7goAQE7y3qOtI4NkwbZRYYE5V0YgRyjBIZfTQBvEWDS4s pU5/Y6WbvRmDmQPg06dfWTyTe3z+Vk+zsIhUH4Sdr8lm897qCsJ1JpeyCj360Qwhv19k SwTaOe3fBHtLFQZaD0iYVnSVEPnI0yDegGRY6vXkR0x8X3BmsgxBuNtisdzPvLlJ5myv EkiY3noccSvpceYwPNMSWf5ogD8gpoCqqGrM9uYz+1D3lubCxDYSJ/g4BsRbIqZWtp4x lWwMxm7xK6UnQx1TpcDDWS01Eumv7zlr1TpoZARVeV7zOZupbVfaJ5bsw+fhWpFtD0qc g7fQ== X-Gm-Message-State: AOAM531c9Qj5ojGm9aJASV4weUOJ1c+wjzR7V+XQMkM2T1am88MSVvSd /PITO53ovk04q2l2acSiD7efYKCfZnTl63Uj33cA6iyCYKqQHdbA X-Google-Smtp-Source: ABdhPJzOXBO6oVbcuKr26qnhaukSY+rdk3+MBqNcuaZA5PwyP8NF2WphK5XnlS+y+NiBF6c/nBqO/mn7HLXxwwTdxQQ= X-Received: by 2002:a67:f7c4:: with SMTP id a4mr9293715vsp.35.1632897530732; Tue, 28 Sep 2021 23:38:50 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Received: by 2002:a59:5706:0:b0:231:f367:1438 with HTTP; Tue, 28 Sep 2021 23:38:50 -0700 (PDT) In-Reply-To: References: <20210922083645.4vnoajyvwq6wfhdf@aniel.nours.eu> <97ebc390-a19e-3203-7016-ce541796eb18@beastielabs.net> From: grarpamp Date: Wed, 29 Sep 2021 02:38:50 -0400 Message-ID: Subject: Re: [HEADSUP] making /bin/sh the default shell for root To: freebsd-current@freebsd.org Cc: arch@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4HK6Cb2bYDz4ZQw X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b="E6m29RH/"; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of grarpamp@gmail.com designates 2607:f8b0:4864:20::e2c as permitted sender) smtp.mailfrom=grarpamp@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; NEURAL_SPAM_SHORT(1.00)[1.000]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::e2c:from]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: N The system shell really only need to support the language of the shipped scripts of the base tooling such as rc subsystem. If those were someday written in Greek, then the shell serves alone, the most common expectation of any "unix" to have there seems to be an "sh", from which users can further customize the box in whatever ways. Base's simplicity, perhaps that is in part why 14 would go with sh, and no longer litter the password file with any other shells, else base must really add and carry them all... zoor zsh toor tcsh coor csh qoor sql poor python boor bash goor go plus the entire rest of world of shellish thingies just to satisfy. Which is obviously untenable and absurd and causes futher legacies, maintenance, dependencies. Where does it stop, what is the limiting definition. Moving to just one, some type of an "sh", seems best to resolve the question. > The little help you get on the command line to search and repeat commands is very useful compared to plain "sh". That is in part why the sh UI appears to be getting some nice improvements as noted in the HEADSUP / thread. BSD users could contribute more to that effort, or run on the systems whichever shells are preferred. > change "Charlie &" in the gecos field to something more > sensible, e.g. just "Superuser" Seconded. It seems somewhat against good idea to have expandos in and downstream with a passwd file. This update can also help users minimize parsing and gotcha bugs by removing some possible escaping/AND/backgrounding interpretation problems, and reducing complexity and surface. There's actually been a good bit of stepwise cleaning and organization of the passwd/group file, and UID/GID to filesystem/daemons, etc over the years. It's good to view this as part of that effort as well. Another problem and lost opportunity cost and burnt cycles this update finally fixes is the decades worth of N times a year debate on this issue. It's a cumulative friction and waste of time. By selecting just one and sh, that goes away, and can move forward there now too :) > More bashism and linuxism in BSD world, > you are waking the devil. It was meant to say 'sh-like', bash is GPL so it shouldn't be in BSD base, the two shells just have some common than with *csh. Let the beastie daemon... and its more free copyright and unique approach to the "unix", its ongoing "pros" "innovatives" and much more that make bsd good... boil the waterparks of linux into vaporware ;) > Like https://github.com/shellspec/shellbench ? Interesting tool and data :) From nobody Wed Sep 29 08:28:05 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 5785C17EE5C8 for ; Wed, 29 Sep 2021 08:28:28 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp1.goneo.de (smtp1.goneo.de [IPv6:2001:1640:5::8:30]) (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 4HK8f32P0Rz4jh1 for ; Wed, 29 Sep 2021 08:28:27 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from freyja (p4fc0ab99.dip0.t-ipconnect.de [79.192.171.153]) by smtp1.goneo.de (Postfix) with ESMTPSA id 769272040673 for ; Wed, 29 Sep 2021 10:28:19 +0200 (CEST) Date: Wed, 29 Sep 2021 10:28:05 +0200 From: FreeBSD User To: freebsd-current@freebsd.org Subject: FreeBSD base pkg (packaging) and critical ports build alongside Message-ID: <20210929102805.1ac3a59d@freyja> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4HK8f32P0Rz4jh1 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd@walstatt-de.de has no SPF policy when checking 2001:1640:5::8:30) smtp.mailfrom=freebsd@walstatt-de.de X-Spamd-Result: default: False [0.30 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[79.192.171.153:received]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_NOT_FQDN(0.50)[]; NEURAL_SPAM_SHORT(1.00)[0.999]; DMARC_NA(0.00)[walstatt-de.de]; NEURAL_HAM_MEDIUM(-1.00)[-0.997]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25394, ipnet:2001:1640::/32, country:DE]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[2001:1640:5::8:30:from] X-ThisMailContainsUnwantedMimeParts: N Hello, I use FreeBSD-base packages built on self hosted systems to update 13-STABLE and CURRENT hosts. I run into the problem, that the packages of the FreeBSD base, built via the FreeBSD framework and from most recent 13-STABLE sources, are often oit of synchronisation with our poudriere packaging builders, that is especially true for critical ports with kernel modules, like i915 drm, virtualbox and so on. The problem is, obviously, barehanded: 13-STABLE sources and probably the API changes more rapidly than those of the appropriate builder hosts for poudriere and since it takes a bunch of days to build a whole poudriere packages repository, there is often a gap between the revision of the kernel and the port containing kernel modules. So, the question is: how can I add ports to the building process of the FreeBSD sources tree in the way they get build every time I build the FreeBSD-base packages alongside the OS? Thanks in advance, oh From nobody Wed Sep 29 08:40:02 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 5447A17EF5DB for ; Wed, 29 Sep 2021 08:40:11 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mail.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HK8vb072Pz4lRK for ; Wed, 29 Sep 2021 08:40:10 +0000 (UTC) (envelope-from manu@bidouilliste.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1632904802; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=X9eM/fQ4U14m4YNt1UhJ72itSrVUJXoM1F2AZfeUqmo=; b=LP6pv9DEeZx6wsmzygKErv5ie0ETqS8OY75R2hZEWswmq4IT+mzyHtFcWSzbu0ctFfVKB+ gaqDJjkblmFBHyEMSzt+c4+N7bcboHGlPeOdcKz+82LaNB2HcHLHGX5VqIhNHjfxpN+tl0 FcM61GCQCdFNfOyAwqaHzFqkVBuriSc= Received: from amy (lfbn-idf2-1-644-191.w86-247.abo.wanadoo.fr [86.247.100.191]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 19059686 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Wed, 29 Sep 2021 08:40:02 +0000 (UTC) Date: Wed, 29 Sep 2021 10:40:02 +0200 From: Emmanuel Vadot To: FreeBSD User Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD base pkg (packaging) and critical ports build alongside Message-Id: <20210929104002.5a3221882165fba1c90713ad@bidouilliste.com> In-Reply-To: <20210929102805.1ac3a59d@freyja> References: <20210929102805.1ac3a59d@freyja> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4HK8vb072Pz4lRK X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N Hello, On Wed, 29 Sep 2021 10:28:05 +0200 FreeBSD User wrote: > Hello, > > I use FreeBSD-base packages built on self hosted systems to update 13-STABLE > and CURRENT hosts. I run into the problem, that the packages of the FreeBSD > base, built via the FreeBSD framework and from most recent 13-STABLE sources, > are often oit of synchronisation with our poudriere packaging builders, that is > especially true for critical ports with kernel modules, like i915 drm, > virtualbox and so on. The problem is, obviously, barehanded: 13-STABLE sources > and probably the API changes more rapidly than those of the appropriate builder > hosts for poudriere and since it takes a bunch of days to build a whole > poudriere packages repository, there is often a gap between the revision of the > kernel and the port containing kernel modules. > > So, the question is: how can I add ports to the building process of the FreeBSD > sources tree in the way they get build every time I build the FreeBSD-base > packages alongside the OS? > > Thanks in advance, > > oh > What I do to have packages (from ports) and pkgbase in sync is that I use poudriere to also build pkgbase. It's available in poudriere-devel using -B when creating the jail. Then I simply cpdup the packages and pkgbase at the same time at the end of the package build. poudriere knows how to do make update-package for pkgbase so your machine will just update the modified packages (provided that you are on a RELEASE/STABLE branch or have WITH_REPRODUCIBLE_BUILD=yes in your jail src.conf for CURRENT). There is still one problem with that approch for kernel modules, they will be recompiled but as the version isn't bumped it will not be upgraded, so I just pkg install -f drm-devel-kmod from time to time. Cheers, -- Emmanuel Vadot From nobody Wed Sep 29 08:42:46 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4BA461788DFB for ; Wed, 29 Sep 2021 08:42:53 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HK8yj1W5fz4mrn for ; Wed, 29 Sep 2021 08:42:53 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtp.theravensnest.org (smtp.theravensnest.org [45.77.103.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: theraven) by smtp.freebsd.org (Postfix) with ESMTPSA id 1319227D3D for ; Wed, 29 Sep 2021 08:42:53 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from [192.168.1.202] (host86-148-130-214.range86-148.btcentralplus.com [86.148.130.214]) by smtp.theravensnest.org (Postfix) with ESMTPSA id 94C362CDE2 for ; Wed, 29 Sep 2021 09:42:51 +0100 (BST) Subject: Re: FreeBSD base pkg (packaging) and critical ports build alongside To: freebsd-current@freebsd.org References: <20210929102805.1ac3a59d@freyja> From: David Chisnall Message-ID: <74afb0a9-be7f-c797-bd15-a96022188d9a@FreeBSD.org> Date: Wed, 29 Sep 2021 09:42:46 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 In-Reply-To: <20210929102805.1ac3a59d@freyja> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: N Hi, I think your best option would be to do the opposite of what you suggest. Poudriere can build pkgbase sets from a source tree and populate a jail from them. The flow that I'd suggest is: - Poudriere jail to build a jail from an existing source tree. - If there are kernel changes, install the packages on the package builder and reboot. - Poudriere bulk in the new jail to build the new package set. Note: You can *normally* skip the second step (drm ports, for example, will be built against the new kernel sources in the jail, though they might not be loadable on the host) but there's no guarantee that you can run a newer userland on an older kernel so things may break. If you enable reproduceable builds in the src.conf that you use for building the jail then you should be able to just diff the kernel binary to see if anything has changed. If you have bhyve or are running on a cloud platform then you can replace the second step with a poudriere image invocation to build a VM image containing poudriere and your newly-built base system and deploy this to build the packages. I'm planning on working on some tooling to do this in Azure with GitHub Actions. Note that poudriere uses packages installed on the host system to build a jail. If you have, for example, installed llvm12 then you can put a line in your src-env.conf for the jail to tell it to use that as an external toolchain and skip the toolchain-bootstrap phase of the build. This means that the base-build is fairly fast even on quite modest hardware (it still builds clang, but at least it does it only once). David On 29/09/2021 09:28, FreeBSD User wrote: > Hello, > > I use FreeBSD-base packages built on self hosted systems to update 13-STABLE > and CURRENT hosts. I run into the problem, that the packages of the FreeBSD > base, built via the FreeBSD framework and from most recent 13-STABLE sources, > are often oit of synchronisation with our poudriere packaging builders, that is > especially true for critical ports with kernel modules, like i915 drm, > virtualbox and so on. The problem is, obviously, barehanded: 13-STABLE sources > and probably the API changes more rapidly than those of the appropriate builder > hosts for poudriere and since it takes a bunch of days to build a whole > poudriere packages repository, there is often a gap between the revision of the > kernel and the port containing kernel modules. > > So, the question is: how can I add ports to the building process of the FreeBSD > sources tree in the way they get build every time I build the FreeBSD-base > packages alongside the OS? > > Thanks in advance, > > oh > From nobody Wed Sep 29 08:56:31 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 5CCD4178ACBE for ; Wed, 29 Sep 2021 08:56:33 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mail.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HK9GT00gJz4pHB; Wed, 29 Sep 2021 08:56:32 +0000 (UTC) (envelope-from manu@bidouilliste.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1632905791; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=U+K8YGv6BGY8fI7A0Pc7Q50tMBg6dgAJiev0biRuJh8=; b=U0IMfkVJEO69KxGi4Cp4IMVEOQEuzyWSfJ0hW9xFqdWldyQXi9HyrH/VNTbYCsBvvqR7hy +cRKJ1qZ+6XYlIQPFL2eKYtCkyNHAv9743RwIIyhRmPstTlsrOqLRtWinwG/xctIADDPc0 U85AlTOiTC+hy+TVnms/YhkfWokoEVA= Received: from amy (lfbn-idf2-1-644-191.w86-247.abo.wanadoo.fr [86.247.100.191]) by mx.blih.net (OpenSMTPD) with ESMTPSA id ebec6fea (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Wed, 29 Sep 2021 08:56:31 +0000 (UTC) Date: Wed, 29 Sep 2021 10:56:31 +0200 From: Emmanuel Vadot To: David Chisnall Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD base pkg (packaging) and critical ports build alongside Message-Id: <20210929105631.f9cba69265edcab0a05b25d6@bidouilliste.com> In-Reply-To: <74afb0a9-be7f-c797-bd15-a96022188d9a@FreeBSD.org> References: <20210929102805.1ac3a59d@freyja> <74afb0a9-be7f-c797-bd15-a96022188d9a@FreeBSD.org> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4HK9GT00gJz4pHB X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Wed, 29 Sep 2021 09:42:46 +0100 David Chisnall wrote: > Hi, > > I think your best option would be to do the opposite of what you > suggest. Poudriere can build pkgbase sets from a source tree and > populate a jail from them. No it doesn't populate the jail from the pkgbase sets, the jail will still be populated using make installworld and friends. I still need to add the possibility to create a jail (and update it) just from a pkgbase but haven't got time yet for this. > The flow that I'd suggest is: > > - Poudriere jail to build a jail from an existing source tree. > - If there are kernel changes, install the packages on the package > builder and reboot. > - Poudriere bulk in the new jail to build the new package set. > > Note: You can *normally* skip the second step (drm ports, for example, > will be built against the new kernel sources in the jail, though they > might not be loadable on the host) but there's no guarantee that you can > run a newer userland on an older kernel so things may break. > > If you enable reproduceable builds in the src.conf that you use for > building the jail then you should be able to just diff the kernel binary > to see if anything has changed. > > If you have bhyve or are running on a cloud platform then you can > replace the second step with a poudriere image invocation to build a VM > image containing poudriere and your newly-built base system and deploy > this to build the packages. I'm planning on working on some tooling to > do this in Azure with GitHub Actions. > > Note that poudriere uses packages installed on the host system to build > a jail. If you have, for example, installed llvm12 then you can put a > line in your src-env.conf for the jail to tell it to use that as an > external toolchain and skip the toolchain-bootstrap phase of the build. > This means that the base-build is fairly fast even on quite modest > hardware (it still builds clang, but at least it does it only once). > > David > > > On 29/09/2021 09:28, FreeBSD User wrote: > > Hello, > > > > I use FreeBSD-base packages built on self hosted systems to update 13-STABLE > > and CURRENT hosts. I run into the problem, that the packages of the FreeBSD > > base, built via the FreeBSD framework and from most recent 13-STABLE sources, > > are often oit of synchronisation with our poudriere packaging builders, that is > > especially true for critical ports with kernel modules, like i915 drm, > > virtualbox and so on. The problem is, obviously, barehanded: 13-STABLE sources > > and probably the API changes more rapidly than those of the appropriate builder > > hosts for poudriere and since it takes a bunch of days to build a whole > > poudriere packages repository, there is often a gap between the revision of the > > kernel and the port containing kernel modules. > > > > So, the question is: how can I add ports to the building process of the FreeBSD > > sources tree in the way they get build every time I build the FreeBSD-base > > packages alongside the OS? > > > > Thanks in advance, > > > > oh > > > -- Emmanuel Vadot From nobody Wed Sep 29 15:13:12 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4801A17D6CF3 for ; Wed, 29 Sep 2021 15:13:27 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "ultimatedns.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HKKdM0dBZz3t0v for ; Wed, 29 Sep 2021 15:13:26 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 18TFDCut078888; Wed, 29 Sep 2021 08:13:18 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Date: Wed, 29 Sep 2021 08:13:12 -0700 From: Chris To: FreeBSD User Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD base pkg (packaging) and critical ports build alongside In-Reply-To: <20210929102805.1ac3a59d@freyja> References: <20210929102805.1ac3a59d@freyja> User-Agent: UDNSMS/17.0 Message-ID: <7a1b54d367fddd1b21aa800d640be862@bsdforge.com> X-Sender: bsd-lists@bsdforge.com Content-Type: multipart/mixed; boundary="=_088815167e1bca597100aad75db25386" X-Rspamd-Queue-Id: 4HKKdM0dBZz3t0v X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N --=_088815167e1bca597100aad75db25386 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed On 2021-09-29 01:28, FreeBSD User wrote: > Hello, > > I use FreeBSD-base packages built on self hosted systems to update 13-STABLE > and CURRENT hosts. I run into the problem, that the packages of the FreeBSD > base, built via the FreeBSD framework and from most recent 13-STABLE > sources, > are often oit of synchronisation with our poudriere packaging builders, that > is > especially true for critical ports with kernel modules, like i915 drm, > virtualbox and so on. The problem is, obviously, barehanded: 13-STABLE > sources > and probably the API changes more rapidly than those of the appropriate > builder > hosts for poudriere and since it takes a bunch of days to build a whole > poudriere packages repository, there is often a gap between the revision of > the > kernel and the port containing kernel modules. > > So, the question is: how can I add ports to the building process of the > FreeBSD > sources tree in the way they get build every time I build the FreeBSD-base > packages alongside the OS? The simple answer is; by keeping/getting both trees where you want them before you initiate a build. This is what I do; Pick some point in time, or in git(1) parlance; hash/revision. I then git co/clone git hash/revision for both trees. I then fire off a build for both. Creating $BASE install(s)/images && packages. Since I'm subscribed to the freebsd-security-notifications ML. I get announcements whenever FreeBSD pushes security patches. I then check the git log for when the patch(s) was/were pushed/committed. Then update the affected tree to that hash/revision, and update the ports tree to the same place in time. Then build both trees and update the affected boxes (servers/hosts). You probably will also want to monitor the commit list (WARNING it's a high volume list) for CVE notices. So as to keep your ports tree safe. Simply do the same -- update the ports tree that contains the CVE commit && build up/deploy your packages from it. Customization (adding ports drivers to your $BASE (src) build: Simply add PORTS_MODULES= to your make.conf(5). For instance; your i915 driver. That pretty much covers it I think. :-) See also; man make(1) man make.conf(5) && man ports(7) HTH --Chris > > Thanks in advance, > > oh --=_088815167e1bca597100aad75db25386 Content-Transfer-Encoding: 7bit Content-Type: application/pgp-keys; name=0xBDE49540.asc Content-Disposition: attachment; filename=0xBDE49540.asc; size=5028 -----BEGIN PGP PUBLIC KEY BLOCK----- mQENBGDTzGEBCADHlXdS4V57s2soaEK2wi3o9rr9zo7to/giBSxCpFYJxOnPkL5A 2ibbvflrL8sWvAczx47wgDS7iIhzICBBRdnXtcFGnoeeriV27LSn+PcpnIB+DaWZ xe+6TDC0Z0JUJ7qDTjUBFzhnQGYlrVvc4WbnWTjJaB1LEwgIX8JqX5S3SX0/oXgs +OtqDuENZ4/a5te5xPnspTv/5NJHjqYGxjHP0Vw0KjRKS1AoJ1SBPSMQV5373AX9 5NzFS+CjqeQhjfHFPeRajQ8t4T6eqhKA7LtKMO1egeAwNehk9ZoEqEBT2+ojuKUd oSuzqvhhx+eUIYLFqoPSzMKR+YbStzergsbnABEBAAG0KUNocmlzIEh1dGNoaW5z b24gPGNocmlzaEB1bHRpbWF0ZWRucy5uZXQ+iQFrBBABCABVBgsJBwgDAgQVCAoC AxYCAQIZAQIbAwIeARgYaGtwczovL2tleXMub3BlbnBncC5vcmcWIQQGJAsyyBlk cuwsSYsYdR58veSVQAUCYNQl+wUJA8LAmgAKCRAYdR58veSVQN3NB/sFTeXrZeDk ml/dshET8QbkOPgXlnibk8+Mauf+y9LjS9WT7R8EmqhK7T7aw115JQ1RWTM6kpQM jyDBjYF7piJEpNKI9YDeSnODKir1fWQqm9+wd68wAKGvV4m8kg9uOHCvXG4J++MG zDFH+PuGVxKirFnaz46DpS0Zw7wTtjNiNFvCooYov3IeYGfqcchd3hwBuXgWLexZ vI8JW7lL9oXl7B/wcbSxg9rwy6/QLYGg6sEtYRcFYyvQWefSMJaLWjU/pZN2iSxM lXm55iZv1BXHupfeD1ldRiGs6ejrcpa8+U1ju291WbLzcIsU8IDljeW9/WB2dLFT hJmY1wRk158AtB5DaHJpcyA8YnNkLWxpc3RzQGJzZGZvcmdlLmNvbT6JAWgEEAEI AFIGCwkHCAMCBBUICgIDFgIBAhsDAh4BGBhoa3BzOi8va2V5cy5vcGVucGdwLm9y ZxYhBAYkCzLIGWRy7CxJixh1Hny95JVABQJg1CX7BQkDwsCaAAoJEBh1Hny95JVA aI0H/AlJAOfc5TcMKa479Itw31mwccKb+u0DPN9Gkm/RfWIBjeqqozxCM8G8jVFr dt/J6KmBO3dQtRZHlXdD57RAfDDl5Vm3uws0s+UIFOxMiua/YxyuDcKLsE8Bjkzx z+vuJ8f6cg4WlygPr3bo3l81AOuU/wOsTrNkQvVJxgATlooATSVxs0yNn2uoso9f nhMGUYsmT4c35JYh0k6Lq7Z2LS+ELipMTQ7M7iCWSP1O/zSEvPD4NBo52xCvjLka KcL4fRl7UN+6ouwGr5aUn83tztE/IR0AK45gFvL5yxI4g/zm1t3j2+hhhW1pBU8w uQWkD2DyLTWy7xs1uVF5m1ojHp60H0NocmlzIDxrbm90QHRhY29tYXdpcmVsZXNz Lm5ldD6JAWgEEAEIAFIGCwkHCAMCBBUICgIDFgIBAhsDAh4BGBhoa3BzOi8va2V5 cy5vcGVucGdwLm9yZxYhBAYkCzLIGWRy7CxJixh1Hny95JVABQJg1CX7BQkDwsCa AAoJEBh1Hny95JVA5m8H/iENaTD4j5QHfaHfiDIdxGx36GnETyRK0vAzr2b6pzG+ 7VHNCm4ZfuMsXDJ1ZD8fjTipvg0f4w31xCQI0NgNdAqudBqE075Jwcr9pE9j8VN1 Nvejto01cgLHODbLPhokrkFz1K023VjCdy5RaVuCZ6ajTif7Kq+BEOE8TumYx4ly zdhnh/9ICohqfVvEMh347wI36D7HuezHB773hOsHdqTy9T+0Qu0Vu+wud45MUy1f vRF11OkJFtKL0bh4yMSGVY1xte1Mt/qC6rd43TDtAW3ekw1o/exh764kp7XXQsmP wwe4Y040PZafcygJlEW9bBtjjxKnzDTvqeb5dMi6d7a0GENocmlzIDxvaWRldkBz dW5vcy5pbmZvPokBaAQQAQgAUgYLCQcIAwIEFQgKAgMWAgECGwMCHgEYGGhrcHM6 Ly9rZXlzLm9wZW5wZ3Aub3JnFiEEBiQLMsgZZHLsLEmLGHUefL3klUAFAmDUJfsF CQPCwJoACgkQGHUefL3klUB74wf8DSvT36bYZp7oqZ+35HNhTekJ2dbTzUhauF0S +Z9R1AGnNnINgua75CyQGdNCIgcZxo4qG9sePl7SllQ9i0qhmiw0mzmvky8bAZQV V/2Coc1C/81b+PI19VczYrbZC20jApsnbAIkKZgSh9XQoiLd3meY7G2lX2k6CXYL xSeBEh+N3BU8vLxExm82U71Qzm43u0kA1TlbTSqpBvg/tfAzTCsYQLSlB6b4ZL2W D6U7b7ZYF5oZNonVNWSHxpjUN3Evkta9xWS2+cgYQdlP1/ku5w5ZWwzmYG7awh0J /YuSNIp6Ks6D/PSBduu6XbH+FJHaXmq+ZCKpNBh5EKH+GhOfq7QfQ2hyaXMgPHBv cnRtYXN0ZXJAYnNkZm9yZ2UuY29tPokBaAQQAQgAUgYLCQcIAwIEFQgKAgMWAgEC GwMCHgEYGGhrcHM6Ly9rZXlzLm9wZW5wZ3Aub3JnFiEEBiQLMsgZZHLsLEmLGHUe fL3klUAFAmDUJfwFCQPCwJoACgkQGHUefL3klUC3GggAo4Y+hslaoV7Namp7qWYZ Vei4ZwPfsYW7/HtmFORSGV8C8xR+LSkwzN1Hc7Qxvwv+DXuk7Hzd1Ag/xe8XhbNG /NMrXENY/8ym9TRbxtrBIhQyhkyShSUT+N+g16GRNZKuNL2MOIHc/RCS/YyyaTtu TzIxFbP7Gb2LO1LiiZsFVOGirHfxyiww7CAm3HXY2K4smOiKs6swZMpStVy3dd6A BcB1LPGs3ywDglFfKCRbVmjsPgsi61r4kUBVO6ML7lAmPDXLXOa+7iAtBN479QxC MVeH3Y3SMrvu61Vyf1xL79rIznU3u8C34zfxqsoIV0zCZe2YDLbFfLhZYqatYYEo e7QjImNocmlzLmgiIDxjaHJpcy5oQHVsdGltYXRlZG5zLm5ldD6JAWgEEAEIAFIG CwkHCAMCBBUICgIDFgIBAhsDAh4BGBhoa3BzOi8va2V5cy5vcGVucGdwLm9yZxYh BAYkCzLIGWRy7CxJixh1Hny95JVABQJg1CX8BQkDwsCaAAoJEBh1Hny95JVAkUEH /jkzYrRh7muqoebwEgVeULzPbAs/nYJm9SMME2ypB2FS8kusO7lE+33UJO7PhHkJ 0nJ+tPfP8UV+fCzVjKjabzpvUGuiMWKRZEK9xNoxwi/epOrRw87msHA2LPqEob+F sVh09Nc58s75koUgSYp5h0FjsLK0+fwsQ6PtTfpY5W6JJVJRQnMwGKk5czrukBSM 79kJvphgul2xuzqo5K7rM98dL75AwCJmJZnbyXpUJIhtY/G01nURupBiQGgNixYs Zeo6OR669TFrMRWxueXtlHD0WaX7JNSlR5uyzpVaDCH0Kxa6ozmZtD+a6dAXg630 zbLGHg51JIm38Uvi1i47Jaa0KCJILlIuIENvbW11bmljYXRpb25zIiA8ZG5zQGRu c3dhdGNoLmNvbT6JAWgEEAEIAFIGCwkHCAMCBBUICgIDFgIBAhsDAh4BGBhoa3Bz Oi8va2V5cy5vcGVucGdwLm9yZxYhBAYkCzLIGWRy7CxJixh1Hny95JVABQJg1CX8 BQkDwsCaAAoJEBh1Hny95JVAABoH/iOWA+9BKxLIAIFgW2nxTFDrGvbxXL/mVSFt SOInKX8UqqfLCcikfpWLsj2D7mg5rKFMCu+31UYYlnrXl4YY1qruq0vh41L72qNy yHYol+xW4BSbZXf2q2ph7+lnPsFoodw7acVun5F8M8NH0roo5AOSbgRlK69ZFIcq fDEJdtk4oul7pqGArdeTCCdrSaeR3zrRN8P0PDOkGKSdlpeOE6XHnbbmAPZIhr/9 KsSpX1BGyipda3k5kOB4TsGVo+cRJMkK+GMpsZ+lJ7ZzRbjHbC+b52TiAIjMtXCK 3A3LrDUeMoJwvRKoO1tzquF6HqHJSg0ArZOvAB3BHlwUyUtA/o25AQ0EYNPMYQEI ANFpucNRdYEOubTNluoK97N9JmDb0WRXPPow+3XfBom6ZBSrWqNBgqDbjxSsLB00 QXbA8EB5W/Oolp/0epwEtgNAxyKVPowE/un+rY1PqvGjeAR4gBhY9Za1Lg1Q3vnR /WzsY7RIQCqhWUbfdGn1u6r/EgTBVrwUp4U/3ggfSz/PcUt4pUhlgxfYvjSjOgEZ wbqaQIwWud11FKMARNAUJzvJL/fDGeKLMvgRUwynIDGzCq7e67hhEEo5jwkZ0gEl 8RxXHKFuYkbb/q7rpdifXYYT6QCFlEZhiRbtH5Us7kgKuRD2XUFEQnN4U/rxuydH 4XOP6iOhiZfYnK/y9HBeRCMAEQEAAYkBPAQYAQgAJgIbDBYhBAYkCzLIGWRy7CxJ ixh1Hny95JVABQJg1CYkBQkDwsDDAAoJEBh1Hny95JVApBsH/iEg2ANRkHByfXB+ sH3PMf2Jsg5NSuj8OiNeKKGGIKCJkSAPjtv5rvKLNcvIcTR5Vnhr0e6AteFcK2te iFWDmj0QuFoQNvIOHQ3nHBPSpai2Ubq12nvYfg4bYK28AMi4xPMssgQ8awFgAI2V k9okq5XwC0Cc1MGhupEWYYSaFLIDQvFvRRSw1Lyc/W3SKa4d2dgesIPnB/rdv0Zq u8ftsSmurKxA2hQeNIcn06Ew7AbWUIjFX/bDXJlg/3Sj/spU2ur23TmaADBKhT5P DvfdaFTkk0SBfpN1j2S0DNXBHSrWvRp15zZmU4hwELiUY/H2/j/XpOGV3Q0i2iob 1hJ30C8= =aMQi -----END PGP PUBLIC KEY BLOCK----- --=_088815167e1bca597100aad75db25386-- From nobody Wed Sep 29 16:49:27 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 1615A17CFD12 for ; Wed, 29 Sep 2021 16:49:37 +0000 (UTC) (envelope-from rollingbits@gmail.com) Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HKMmJ6wyBz4V68 for ; Wed, 29 Sep 2021 16:49:36 +0000 (UTC) (envelope-from rollingbits@gmail.com) Received: by mail-qt1-x831.google.com with SMTP id r16so2894074qtw.11 for ; Wed, 29 Sep 2021 09:49:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:subject:from:in-reply-to:cc :date:message-id:references:to; bh=piI+3YlpVlM6qIBAQM6TFtNfoQ0nn1aLWTIJkNmg8iY=; b=Vhh9nbRIjywmbevpv0pYIICSpnufIV1EZGvgiccOdhA4Cunmv8xlVRlbcMcgZ+oySJ I2bm1bL4NUQRgfPQ7HmwLlaQ7NJHenPazehfdF7S9vxJCF2TNkX83cF2KbAaURIm6n4L lJv6l4nSR1NL8e5BIplpcQVadX+5a6P2qCHGBHdTD6TJP3VlQXsB//47A5iiR7LTUctA Be+Ag5C8rbKddn6YeXkDFRApuxG88//6bhA0mRrU2is6ZyQnbDPXrXwyFtd4PHRgmBXo VkK9ym+LGgb0EwIXThb3EqLetApZDkXrUOM16lEDtrAZ3U55WY13utsAZNI5X67Y7j/J 3oiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:content-transfer-encoding:mime-version:subject :from:in-reply-to:cc:date:message-id:references:to; bh=piI+3YlpVlM6qIBAQM6TFtNfoQ0nn1aLWTIJkNmg8iY=; b=B5hVtKC5cXxGL78IF38BRFFTulwUAhU5yR4xkDITnmg7nh+ejjP8/SAaG39u8sWm8U Iszh0teBt6tfGDHarDdvj9q/XcuwO2JSVrAmpCq4KtdtAYatW5RYCY0G9trFpEizIstH jkIwR3VHrL5fTsr3gbUUMcxHv++dVJOmGEQB8JnNlk1wRl8cXSe8nTZxTRUE2k6lsOy6 SNUkh8mWD32u/o/rEL/lnGkEUWY5Zp17U0IP6Czt/5PSV9m0cxiy5LQ63gxch2u7DNcz gq+dAE+uobL8MJIGamTrrrzH45XODWztxQXlRd/bbijh4atJRltSlPxU8X5oCgBSkU7P xUrQ== X-Gm-Message-State: AOAM530InIvk8gQWbL1rsho/kjWbfkQcAGJgQsVljmahjtB+CTrqC9p9 hlegfUOKSJiLgdsmVYJWRcaGSU5I1K0= X-Google-Smtp-Source: ABdhPJwcK4a+kyQEPhdDIZQDcmzDqI5K5Ucp2yZemytSEDpYHE/rPkrtCB+40pTMKK++dHV9UoEfqw== X-Received: by 2002:ac8:4089:: with SMTP id p9mr980310qtl.363.1632934170348; Wed, 29 Sep 2021 09:49:30 -0700 (PDT) Received: from smtpclient.apple ([2804:389:2046:e38b:e900:e36f:24f5:a3]) by smtp.gmail.com with ESMTPSA id u189sm202024qkh.14.2021.09.29.09.49.29 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 29 Sep 2021 09:49:29 -0700 (PDT) Content-Type: multipart/alternative; boundary=Apple-Mail-178C6322-9FE5-49CC-B9BB-E0E1B7F45EF5 Content-Transfer-Encoding: 7bit List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (1.0) Subject: Re: [HEADSUP] making /bin/sh the default shell for root From: =?utf-8?Q?Lucas_Nali_de_Magalh=C3=A3es?= In-Reply-To: Cc: freebsd-current@freebsd.org Date: Wed, 29 Sep 2021 13:49:27 -0300 Message-Id: <6B2E21D5-0DF1-4BCC-A27C-DFFBB201FB52@gmail.com> References: To: grarpamp X-Mailer: iPhone Mail (19A346) X-Rspamd-Queue-Id: 4HKMmJ6wyBz4V68 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --Apple-Mail-178C6322-9FE5-49CC-B9BB-E0E1B7F45EF5 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable It looks like every time I correct an error, someone tries to hack my accoun= t=E2=80=A6 odd. > On Sep 29, 2021, at 3:40 AM, grarpamp wrote: > =EF=BB=BFThe system shell really only need to support the > language of the shipped scripts of the base tooling > such as rc subsystem. No. The system shell is supposed to make the system usable by the users. Actually, the real problem is that the easiest way to shoot one's own foot is by changing the language (say, the shell) spoken by default by FreeBSD. > zoor zsh > toor tcsh > coor csh > qoor sql > poor python > boor bash > goor go > plus the entire rest of world of shellish thingies just > to satisfy. Which is obviously untenable and absurd and > causes futher legacies, maintenance, dependencies. > Where does it stop, what is the limiting definition. > Moving to just one, some type of an "sh", seems best > to resolve the question. This is non-sense. Every unix user should know that it's possible to changing the used shell by using chsh and this includes root. BTW, toor default to sh, not tcsh. --=20 rollingbits =E2=80=94 =F0=9F=93=A7 rollingbits@icloud.com =F0=9F=93=A7 rolli= ngbits@gmail.com =F0=9F=93=A7 rollingbits@yahoo.com From nobody Wed Sep 29 23:35:06 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 0B03E17D1B82; Wed, 29 Sep 2021 23:35:12 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta001.cacentral1.a.cloudfilter.net (omta001.cacentral1.a.cloudfilter.net [3.97.99.32]) (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 4HKXmG2k2Zz3JdM; Wed, 29 Sep 2021 23:35:10 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from shw-obgw-4003a.ext.cloudfilter.net ([10.228.9.183]) by cmsmtp with ESMTP id VifcmmNVJczbLVj6TmkCIo; Wed, 29 Sep 2021 23:35:09 +0000 Received: from spqr.komquats.com ([70.66.148.124]) by cmsmtp with ESMTPA id Vj6SmppZycHSBVj6TmtBD5; Wed, 29 Sep 2021 23:35:09 +0000 X-Authority-Analysis: v=2.4 cv=I4EG+Psg c=1 sm=1 tr=0 ts=6154f82d a=Cwc3rblV8FOMdVN/wOAqyQ==:117 a=Cwc3rblV8FOMdVN/wOAqyQ==:17 a=kj9zAlcOel0A:10 a=7QKq2e-ADPsA:10 a=w16vAm4-AAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=ZIg2hF9TDmgWk9H5LNoA:9 a=CjuIK1q_8ugA:10 a=eWus_ag6ds_90y4h1ov8:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=LK5xJRSDVpKd5WXXoEvA:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 1717E13D; Wed, 29 Sep 2021 16:35:07 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.16.1/8.16.1) with ESMTP id 18TNZ6cc006285; Wed, 29 Sep 2021 16:35:06 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <202109292335.18TNZ6cc006285@slippy.cwsent.com> X-Mailer: exmh version 2.9.0 11/07/2018 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: Baptiste Daroussin cc: current@freebsd.org, arch@FreeBSD.org Subject: Re: [HEADSUP] making /bin/sh the default shell for root In-reply-to: <20210922083645.4vnoajyvwq6wfhdf@aniel.nours.eu> References: <20210922083645.4vnoajyvwq6wfhdf@aniel.nours.eu> Comments: In-reply-to Baptiste Daroussin message dated "Wed, 22 Sep 2021 10:36:45 +0200." List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Sep 2021 16:35:06 -0700 X-CMAE-Envelope: MS4xfBtAys6I7cbW0UMERcztIE/xLuLIthrlO0BFLjdG//OcKpQ69SOChQnmb3trdK0ajR5RbOi7ajlztu/kFVHiG8Dv8ytFYfLd+O57B9N3jLgX2V0KCufb /BIJXoHge4TaUWHEPO62K+gWzOf781UcJg9d5wq/LjOhwLMrezNHOpo6rqlQHN6WB/GePNeXCGDLU0pbg8ZmHBm2P5R7+p/hVIrH6qZBOd0S/z1oIbs1U1Db dzfYk9LbeWD25cGaj4cZyw== X-Rspamd-Queue-Id: 4HKXmG2k2Zz3JdM X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of cy.schubert@cschubert.com has no SPF policy when checking 3.97.99.32) smtp.mailfrom=cy.schubert@cschubert.com X-Spamd-Result: default: False [0.19 / 15.00]; HAS_REPLYTO(0.00)[Cy.Schubert@cschubert.com]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MV_CASE(0.50)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[cschubert.com: no valid DMARC record]; ARC_NA(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_MEDIUM(0.79)[0.793]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_IN_DNSWL_NONE(0.00)[3.97.99.32:from]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16509, ipnet:3.96.0.0/15, country:US]; RCVD_TLS_LAST(0.00)[]; RWL_MAILSPIKE_VERYGOOD(0.00)[3.97.99.32:from]; RECEIVED_SPAMHAUS_PBL(0.00)[70.66.148.124:received] X-ThisMailContainsUnwantedMimeParts: N In message <20210922083645.4vnoajyvwq6wfhdf@aniel.nours.eu>, Baptiste Daroussin writes: > Hello, > > TL;DR: this is not a proposal to deorbit csh from base!!! > > For years now, csh is the default root shell for FreeBSD, csh can be confusin > g > as a default shell for many as all other unix like settled on a bourne shell > compatible interactive shell: zsh, bash, or variant of ksh. > > Recently our sh(1) has receive update to make it more user friendly in > interactive mode: > * command completion (thanks pstef@) > * improvement in the emacs mode, to make it behave by default like other shel > ls > * improvement in the vi mode (in particular the vi edit to respect $EDITOR) > * support for history as described by POSIX. > > This makes it a usable shell by default, which is why I would like to propose > to > make it the default shell for root starting FreeBSD 14.0-RELEASE (not MFCed) > > If no strong arguments has been raised until October 15th, I will make this > proposal happen. > > Again just in case: THIS IS NOT A PROPOSAL TO REMOVE CSH FROM BASE! Having used /bin/sh as my root shell on all my FreeBSD machines, here and at $JOB, except for only one, I feel this is perfectly reasonable. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. From nobody Fri Oct 1 10:13:33 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 8272717DE23A for ; Fri, 1 Oct 2021 10:13:37 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HLQtT3Hywz3hpX for ; Fri, 1 Oct 2021 10:13:37 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from [192.168.0.88] (unknown [195.64.148.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: avg/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 1C470F6C2 for ; Fri, 1 Oct 2021 10:13:37 +0000 (UTC) (envelope-from avg@FreeBSD.org) To: FreeBSD Current From: Andriy Gapon Subject: NO_ROOT+DESTDIR: Permission denied? Message-ID: <770b3b52-015a-0d5c-bf48-1fccccd0dc84@FreeBSD.org> Date: Fri, 1 Oct 2021 13:13:33 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.14.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-ThisMailContainsUnwantedMimeParts: N When installing world with NO_ROOT and DESTDIR set I see a handful of permission denied errors like below: -------------------------------------------------------------- >>> Installing everything started on Fri Oct 1 13:09:32 EEST 2021 -------------------------------------------------------------- make[3]: "/usr/obj/apu2c4/usr/devel/git/apu2c4/amd64.amd64/toolchain-metadata.mk" line 1: Using cached toolchain metadata from build at trant on Mon 27 Sep 2021 16:29:14 EEST ===> lib (install) ===> bin (install) ===> cddl (install) ===> libexec (install) ===> gnu (install) make[4] warning: /bin: Permission denied. ===> include (install) make[4] warning: /lib: Permission denied. make[4] warning: /libexec: Permission denied. installworld works despite those and the result looks fine, but the messages a re little bit concerning. Perhaps, DESTDIR is not honored in some place? The able is for installing CURRENT on a stable/13 host. -- Andriy Gapon From nobody Fri Oct 1 15:20:44 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 9230F17F5E20 for ; Fri, 1 Oct 2021 15:21:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ua1-x930.google.com (mail-ua1-x930.google.com [IPv6:2607:f8b0:4864:20::930]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HLYj93NWyz4Zp4 for ; Fri, 1 Oct 2021 15:21:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ua1-x930.google.com with SMTP id b34so6930972uad.8 for ; Fri, 01 Oct 2021 08:21:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Ear0QXm4/MMCi8UVY2vYEkNTSjzKVBOquvnf8nDwLTg=; b=OGOU2SfhQwuTimmGmawLb1mmEX0LfdWpSd/Fll1xq3+Uf/t0U4Y1GnivDzGLi1B3H6 e8tSkFjbqBhKw198dYBlhRToRo3jOMuMrW4BS7Y44otrD7+krUeEkb+PQjF2jUoLClnw tdDosyeijZbwE/tkYPi/OPR9vik6Y84mu5CxKt7BXlSdRgYVNcNKa6YUr4+fbCjXjsc+ Z3vzxECJpYH5HljwYAEcKBpDDPtwru1gCfj0NZ+7+HWeD0FB4tkNDqpPuTO6UTB98b60 5BJrcjj2tCENdCyShSO554yas6ki8JcaLcHcjIQtWOCOGIOA3caBf5+WCntn127QERRN crTw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Ear0QXm4/MMCi8UVY2vYEkNTSjzKVBOquvnf8nDwLTg=; b=ppkGa7sjcQ7JYOiB10fU/1BnE2qPIHeA4ebYGiCZBBaYAMwVahEe2lbl/9z/RTMD7k 6XdhtkP8h7ErWTDHGELOUbqX+3WesBjxZH1/3fJube+DNadP0P8SQO49NxXDgkSL5z3z DW3AFwrxMW+5Qi8asgEX8D6a6K2zxc8Mf0NuGvBeumzdKz3b+EQyYAYPrGDKA+Pda0m2 nuLwYTOooC7MnEj1MV4lYVE/+kzYzLurhYaaohisDzWwlr50KIBzAxW8i0RggMBNd13a LUGmoijd/8AkesEcCENU/6uoGJaildjbX/YwqOpG6iQGT79RtFd4ZyQzE9jZRv13096X 0mGw== X-Gm-Message-State: AOAM5322aVTCm5spXJQcjExklMNNPVkQu5DSGZ1aeJ/Sv8EkJ9z7AZ4Z 6WX5KQNAFbCUDrt470A5PSho93EeAc5/PigJ3qGDrw== X-Google-Smtp-Source: ABdhPJySlkQc1un/2MJo4q/rJpq/GmtA8pkO1KnFqOQsuxf5Hck3v1v9ZUX3M9p1BTH4yBwhKHMiOKH5tg8ZjoA6fxM= X-Received: by 2002:ab0:471d:: with SMTP id h29mr10768322uac.11.1633101655602; Fri, 01 Oct 2021 08:20:55 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <770b3b52-015a-0d5c-bf48-1fccccd0dc84@FreeBSD.org> In-Reply-To: <770b3b52-015a-0d5c-bf48-1fccccd0dc84@FreeBSD.org> From: Warner Losh Date: Fri, 1 Oct 2021 09:20:44 -0600 Message-ID: Subject: Re: NO_ROOT+DESTDIR: Permission denied? To: Andriy Gapon Cc: FreeBSD Current , Jessica Clarke Content-Type: multipart/alternative; boundary="000000000000108b5205cd4c1cdb" X-Rspamd-Queue-Id: 4HLYj93NWyz4Zp4 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --000000000000108b5205cd4c1cdb Content-Type: text/plain; charset="UTF-8" On Fri, Oct 1, 2021 at 4:14 AM Andriy Gapon wrote: > > When installing world with NO_ROOT and DESTDIR set I see a handful of > permission > denied errors like below: > > -------------------------------------------------------------- > >>> Installing everything started on Fri Oct 1 13:09:32 EEST 2021 > -------------------------------------------------------------- > make[3]: > "/usr/obj/apu2c4/usr/devel/git/apu2c4/amd64.amd64/toolchain-metadata.mk" > line 1: > Using cached toolchain metadata from build at trant on Mon 27 Sep 2021 > 16:29:14 EEST > ===> lib (install) > ===> bin (install) > ===> cddl (install) > ===> libexec (install) > ===> gnu (install) > make[4] warning: /bin: Permission denied. > ===> include (install) > make[4] warning: /lib: Permission denied. > make[4] warning: /libexec: Permission denied. > > installworld works despite those and the result looks fine, but the > messages a > re little bit concerning. > > Perhaps, DESTDIR is not honored in some place? > > The able is for installing CURRENT on a stable/13 host. > Does the following code review help? https://reviews.freebsd.org/D30990 Warner --000000000000108b5205cd4c1cdb-- From nobody Sat Oct 2 01:19:37 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 9D6A617E07F6 for ; Sat, 2 Oct 2021 01:19:47 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HLq024Vd8z3tSJ; Sat, 2 Oct 2021 01:19:46 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wm1-x32a.google.com with SMTP id g193-20020a1c20ca000000b0030d55f1d984so1302433wmg.3; Fri, 01 Oct 2021 18:19:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=WmOYxNIpnMa+YDmKHEpx4zwPRBHww0S9RJ7S3GuYx+Q=; b=GgPrN2J5iyulsYolGCyHCAlKDfmj0P9OLHZflF/aTPMs5cxkuG89EpnPomgwPQDBg5 sJo3MwSG6eA1XZYefKb0fcscf2u7SkC5Im8+HsWzjhrCZqDiuHAA7Zyep5dE6+5uaOwK P7BAuUW9KNi6zlQZK6kXP0gPueyyu8eyyRSiSmUZUXRtli48XCTzVqcCeiZqwteonSuJ qN9+gFFpi/X81IrsofOtomOIm2TKUJXd2qE0Xb7hhXfTxIKgJksFij3afVm4zOEX4mTZ D6B6oBqrfymYkZPil3tofWvgngyTaOB5NYje666yzVof1sMUZDr6jJAvgiJMQthZ9XXc 55Dg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=WmOYxNIpnMa+YDmKHEpx4zwPRBHww0S9RJ7S3GuYx+Q=; b=6yOQE2f/f1mMlqgisSEA7sXOwrJCLReq8C9Z5XKHw6S7emCAYdePxuHqG9+IwUJtnC dEjT3ANF4nST+FwX11YqLWORU7GHJWPDBNy1YzQUrV4zFgM2HwiWHEem2PLXYXbqX4ch 5YRJ0kQw9Op1SfA9E0T+m3Bv6Xpm9uXXv0jITxUM4S+VxZucudVNtKI7nqW5UgJWhIDm yOF875j3F3yGcSvCKlHNS9Ue5Br1UkJArBu9n0ac3z06zruZyL/CDgit01e1WY95Xap8 f6SjQSMkq6oF6Ggp3r+vOah2+YJWeiiY7GG0OCDzZ0pk8anmsP9YfLATtLWqU20aJzHV KPOA== X-Gm-Message-State: AOAM5302M+rkKuxxsBjDjqLZOB3gG31Evb4dXEKJJAZYIK5UJwFh3ACA jbfIY1SauZkmiFxlnkGqRRM= X-Google-Smtp-Source: ABdhPJz+d4ThgIp3jHMeXLjI6sMm5tO1ewEEht35PGsPerSa7Wxh/QxvVvUhBi3IuDd8Q8W4Tu9eRg== X-Received: by 2002:a1c:2904:: with SMTP id p4mr7230450wmp.49.1633137579337; Fri, 01 Oct 2021 18:19:39 -0700 (PDT) Received: from [192.168.1.10] (79-66-158-223.dynamic.dsl.as9105.com. [79.66.158.223]) by smtp.gmail.com with ESMTPSA id w18sm7218767wrt.79.2021.10.01.18.19.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 01 Oct 2021 18:19:38 -0700 (PDT) X-Priority: 5 (Lowest) To: FreeBSD CURRENT From: Graham Perrin Subject: AMD64 UEFI loader: staging area: seeking a summary overview of D31121 and related bug reports Message-ID: Date: Sat, 2 Oct 2021 02:19:37 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB X-Rspamd-Queue-Id: 4HLq024Vd8z3tSJ X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=GgPrN2J5; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of grahamperrin@gmail.com designates 2a00:1450:4864:20::32a as permitted sender) smtp.mailfrom=grahamperrin@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RECEIVED_SPAMHAUS_PBL(0.00)[79.66.158.223:received]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; NEURAL_SPAM_MEDIUM(1.00)[0.998]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::32a:from]; HAS_X_PRIO_FIVE(0.00)[5]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Amongst the related bug reports, : * suspects some kind of "special behaviour" with ASUS UEFI * also observes a regression in FreeBSD. Given other related bugs, which include (mostly HP, one Samsung): * please, can anyone offer a summary overview of the underlying situations? Something not-too-technical will be ideal. In particular, I'd like to counter an (off-list) implication that bugs such as these are simply the result of computer manufacturers' products not following "the standards". (Re: and so on, I do understand that complexities exist, however "the standards" is, for me, too sweeping a phrase; it's non-specific.) TIA, thanks also to everyone who is helping towards the fixes.