From nobody Mon Jul 28 15:52:08 2025 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 4brNJm38qDz63Cf8 for ; Mon, 28 Jul 2025 15:52:08 +0000 (UTC) (envelope-from ivy@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 "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4brNJm2XJYz3VX6; Mon, 28 Jul 2025 15:52:08 +0000 (UTC) (envelope-from ivy@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1753717928; 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=krr7M+NxCnKLW0mDqSFJFRL+eDntBziQ+wFkyWWqOVQ=; b=O07kSqjhHGyOLcS+Q6EI4MNoEowVWQcKLcRaqVfCQd4flQxlrrjatcHbzIsISEPNG6Dr8g F/hWeyozDIKHhvbqQQNWFURYGFc6Pa4f5unELau8YedAuDls59JHPVA1eJ1uTgKPN53TPh GpEpyA0BHR5Wt+GtRSDwqYz9jJf8rPsXLtQ2BlhVhM10tYqFFbRTQ4sa7Iu1AlcssKNhy0 z81tZ0k2EmDOCv/jqdCLTcjNl8fLNLowR+yGSFZRib6kfkQ2KKvQR8q+zTV0VmsFunN5TG Q0B0WAuGoVByr3lKPMygWb7wmEWj3LN1UvTrtKQf5rt0xM6nEbANU4VRds1qDg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1753717928; 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=krr7M+NxCnKLW0mDqSFJFRL+eDntBziQ+wFkyWWqOVQ=; b=xkRBUu0RBL0x09UbsIeC7P6cnieoy3vFMP4lXSBPHhRS5VN1/HXruTu4wkSe5gZpo5yYBT 1oFsbZAo3teRZ9iDql76qZxfF9VAduvTaJ2OzKjzFOe/+YBfbB5doD5XviXU+miSVK3n64 AoIIFF6CCaM9CoKWaAurtQrcPDNJ1TjH3zD448td9jSuAVk8toohwcP1l4raIXSIIui2ux 9aZR2HF/64+WusINWympkPE26NWEdjjMKjjDA0rBQxZelxjoCOmzvx75NIqWB7KDZIus/p WqY1AbKQxMmQFeFe5C5VAuUztdoe85Fzrs2wxvnv3GuFHlA1tii4tITJ/kYnfw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1753717928; a=rsa-sha256; cv=none; b=Qg8v3To9t7DHbU1XUr+GXgBGD4admN+yXzN5yVG59BPmiBVDDQOkYxRdIMvALUuTCJXI03 92FtQW94B2GnVRXxlrQVrrnkPx2vLC+H+s59Pz4h+temXpDldwBHjjLmXxXrzw02oIJmlF +QuNgn/riGclEZuSFevbIT2zXcKPWx8jUcyxRgAKyEbnBZBmchsDiRD8hc9qjXZ/vdt6JU XaLvAgcEzG7RZjhCfP5bwNpvLHbIuEyAXjAzIf/D09fnp2zQi6QywrC4tjYS+itjErYLZu ZX36y5GVcJQFk2URNQv452afOVPHukU5OukmOb1A9EIiupVVmG/xAXEyUK/14w== Received: by freefall.freebsd.org (Postfix, from userid 1532) id 45CB4180A3; Mon, 28 Jul 2025 15:52:08 +0000 (UTC) Date: Mon, 28 Jul 2025 16:52:08 +0100 From: Lexi Winter To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= Cc: Adrian Chadd , qroxana , "freebsd-current@freebsd.org" Subject: Re: epair(4) Message-ID: Mail-Followup-To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= , Adrian Chadd , qroxana , "freebsd-current@freebsd.org" References: <45d0f49d-229b-46b4-af95-6e8c4c856661@plan-b.pwste.edu.pl> <932111f8-f5ca-46d1-9f66-983f80f6116b@protected-networks.net> <8DCF0DAB-5EE5-4FEF-8CCC-1D7AF971BA8C@hausen.com> <86ms8zbz6w.fsf@ltc.des.dev> 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: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Ap8BfU+0nQ/QKHKO" Content-Disposition: inline In-Reply-To: <86ms8zbz6w.fsf@ltc.des.dev> --Ap8BfU+0nQ/QKHKO Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Dag-Erling Sm=F8rgrav: > Adrian Chadd writes: > > qroxana writes: > > > What's the best practice for setting up bridge0 on a NFS root > > > system? [...] > > That's an interesting problem that I don't think was even thought > > about when bridge(4) was added to FreeBSD. [...] I /think/ the tftp > > boot path configures the interface addressing via kernel APIs, and > > we'll need to undo it and flip it to a bridge. =20 > This is not the only scenario where you might want to add a bridge to a > configured system. I think it would be useful to have a setting that > causes all of an interface's addresses and routes to be moved to the > bridge when the interface is added to it. i'm not opposed to this and i think the idea is reasonable, but i will not have time to look at this prior to 15.0 and to be honest, it will be fairly low on my list of tasks after that. so i encourage anyone who needs this functionality to write the code :-) --Ap8BfU+0nQ/QKHKO Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQSyjTg96lp3RifySyn1nT63mIK/YAUCaIecpAAKCRD1nT63mIK/ YOcmAP9rO5G5hXQ7ONuMTG3meiz7MM/cNE49cVQgJV/3mlii4AD/ZBFA6XhHCyB2 19IYdvIXpZQ8F7lcATupID30sdQ3NAM= =UWW3 -----END PGP SIGNATURE----- --Ap8BfU+0nQ/QKHKO--