From nobody Tue May 27 00:43:43 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 4b5v5V1D1mz5x51X for ; Tue, 27 May 2025 00:43:58 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4b5v5T5syyz3XtB for ; Tue, 27 May 2025 00:43:57 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x52b.google.com with SMTP id 4fb4d7f45d1cf-6049431b409so2619162a12.3 for ; Mon, 26 May 2025 17:43:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1748306636; x=1748911436; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=hXqDrD0RPlQE7VwDMtJyRCwNNvLacUK8nRCs+FsxhXk=; b=IQR3lUp9sXDhpAsvEW/dzPl7KVPo9j0fve9FnrodRjMEQHOj4JtR9PuTwfBY0CHcnu PO5k2vtioIFPjhp0EgnwskH2atc226mKNwDnMuckLDW3zCfvjxG8v/w4t/ALwXRCebh/ zgQ9l9kfWeYO18x7I+Orq14bKFUek3CM/LVBBRPkOQdZTdhnEJzDCvhT9IntVuqCU5F5 lfE/FDmR4M7ICHvicecVpiygQjHosJFJqHiM5DXfu3dTwO/6P31eeT9acoxng5dD55j+ SyuLcMEkHBjKvCwIVXkV2qOc2woFle+rI4dDm0qqnpX75OGUqaSypwwEEX2q4lmu4Qn0 V/xw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1748306636; x=1748911436; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=hXqDrD0RPlQE7VwDMtJyRCwNNvLacUK8nRCs+FsxhXk=; b=iHj/VyDhj+zv1NFfaQsPJwVzg1DFiGQw2Haq1ZXYocZnuqq3WBNUBzTdcjLEF7hwDA xxzMCFSOPzkRJIwu8YE98FIPvxB8FB0dyYVxVIAodwWMu9750pT3Uh2xcrcHkFAM2crB GNEjQbE1QwPH4RRB043jC0jMAA8+5/3Rb63YZ3BxGnxBhZCSevQMO+HdZcSqCw7YXFYN olzdeBMR2lNtt5BuJec5EZYY671z0UOGweKTeRgMnEOh1gwyTLjuTmuK1drx3UiCAlys K+m6Bk1A6iVnoiNqVC5wt+Ixzt4lUgP+0I7HXVj9/rDQI2WBYIlzDdEva76ymKyVhbVX kX4g== X-Forwarded-Encrypted: i=1; AJvYcCXKYa3UF8a9n6Hi1CvGHlsJErllYIiFTNpTr/NgBL1pw0Jt1+Rt7cQ1QxpceUDQsy3d7WLsmb58ToA9MUVi5iM=@freebsd.org X-Gm-Message-State: AOJu0Yy6QxZxv3SZ83VnhmDtKE6nNEP/6O2eIizbbTRddOqNgxJ9BZSk /hCmrZkFxYLLgird0Jbs6NJvyzonJD24xDvzpyxk0qIwu83gzf/nOspj4nQlXv/HiezVPx7t+sb hMEASAsI04Oi0gTOy44v3XlXdl5/XtrIUsMOWDg== X-Gm-Gg: ASbGncu+XY1oSvDQzB1HZyKHMce/gUZJOzRcUaqrVzEjLAOaZxo4N8lC5Lao3ZxySPt H7IWpYym80d+C7xNWbgCYJ+ge2huVPQofTM/NAQLXzoHHjHXZNH5fR6WChZC+rKmfc0xZleY1t8 HxGQxrTXpnkXPPyIlAESCHm7b2CKEScAwW X-Google-Smtp-Source: AGHT+IHNfIDFtFg4IEwcBEzNAByLtvidyXL5u2b17LUwYWcBUGiw9tYMlI6kxIaPv3NIjbK1ZQZYuHXY/FVZn6WNp50= X-Received: by 2002:a05:6402:348a:b0:5f3:857f:2b38 with SMTP id 4fb4d7f45d1cf-602da1e8e0cmr8644336a12.17.1748306635566; Mon, 26 May 2025 17:43: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: <20250526151416.68ff7c09.grembo@freebsd.org> In-Reply-To: From: Rick Macklem Date: Mon, 26 May 2025 17:43:43 -0700 X-Gm-Features: AX0GCFvL0iHSSr1CKStObCd0_1ZhMR2VxdIhZd_MJiklJhX58Jg4Aiiw2UQF0Ns Message-ID: Subject: Re: With poudriere how does one create a jail of a slightly older RELEASE ? To: Warner Losh Cc: Dennis Clarke , freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4b5v5T5syyz3XtB X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Spamd-Bar: ---- On Mon, May 26, 2025 at 7:36=E2=80=AFAM Warner Losh wrote: > > On Mon, May 26, 2025 at 8:14=E2=80=AFAM Dennis Clarke wrote: > > > > On 5/26/25 09:14, Michael Gmelin wrote: > > > > > > > > > On Mon, 26 May 2025 08:25:50 -0400 > > > Dennis Clarke wrote: > > > > > > > >> I have no idea what "MFC" is supposed to mean. > > >> I guess it is a code change that happened somewhere. > > >> > > > > > > Merge From Current =3D Merging or back-porting a base commit from CUR= RENT > > > (main/base/HEAD) to another, usually lower, FreeBSD version branch. > > > > > > https://wiki.freebsd.org/Glossary#MFC_--_Merge_From_Current > > > > > > -m > > > > > > > So many places with special terms and stuff buried somewhere. In the > > last week or so I have discovered https://archive.freebsd.org/ and now > > there is https://wiki.freebsd.org/ which I have not ever seen once in > > five or six years of trying to use FreeBSD. Maybe a link or something > > can be put on the "About" page? https://www.freebsd.org/about/ > > Yes. We have our own Jargon that has evolved over the years. Many > of the terms are used so frequently we forget that people new to the > project might not understand them. > > > Even more crazy is the way in which FreeBSD is changed and/or fixed. > > There are bug reports of course but it seems everything really happens > > in a thing called a Phabricator. > > Well, it's even more complicated than that... We have Bugzilla to get bu= g > reports, which sometimes have patches. Historically, these patches have b= een > neglected, in no small part because many of our developers have a hard > time saying 'no' especially to something that's ambiguously incorrect or > that touches a complicated-to-fix area of the tree. Next up is Phabricato= r, > which developers use to review changes, but sometimes non-developers > use it, but we have had a hard time managing that process, so changes oft= en > get lost. Third, we have github pull requests now that I've been trying t= o > establish as a better-managed place to go to contribute. I will mention that you forgot the mailing lists. If you post something to freebsd-current@ most of the developers see it. Bugzilla is ok for reporting bugs, but not so good when it comes to having a discussion about it. Same goes for phabricator. And, yes, I am not a fan of github, but do suffer through it for things like OpenZFS and Linux kernel patches. But I'm old school (and old;-), rick > > > It really is a great UNIX implementation and runs like a charm as a > > server but the skills required are all over the place and no where and > > everywhere and yeah ... thanks to this mail list I can at least keep a > > few things running. To quote a really cool guy that is an expert at suc= h > > things "If it breaks you can keep both pieces." > > We also do try to document everything in the FreeBSD handbook, but > sometimes it's a bit out of date because there's been lots of change and > innovation over the years. > > Warner >