From owner-freebsd-questions@freebsd.org Thu Mar 25 10:19:46 2021 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5719C5B84B5 for ; Thu, 25 Mar 2021 10:19:46 +0000 (UTC) (envelope-from pstreem@gmail.com) Received: from mail-io1-xd30.google.com (mail-io1-xd30.google.com [IPv6:2607:f8b0:4864:20::d30]) (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 4F5h1F4sSMz4rGw for ; Thu, 25 Mar 2021 10:19:45 +0000 (UTC) (envelope-from pstreem@gmail.com) Received: by mail-io1-xd30.google.com with SMTP id j26so1325415iog.13 for ; Thu, 25 Mar 2021 03:19:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9gVnqVrrUA1mr0k46HEMKibQCwArc3D/s7fZlpVclMo=; b=CJqbTWubPnbWeN26WkfbFmxk/zoGdLOlTDWUIUA9PfII1wMW1ZEEnU97m0JX00J0lM mPplmY5wZOEDtZ8vsODtqRBsjT8RS26IroA8ceGqA0qX2invRAscxHkRyWDu8nBgXSJ2 JiIr1AP3bEFiiY9lq2WsXbA4JgTTLH+SnHPLaN2UQ3/7jHK9/rfpeO4lLK2KDXbKL/yR pPdmPoe+bPpRh69FjR8by+Ci7lOJgC0g4FM5KeLOGu+/mqx5QD3V5wTw+u6D91Td8x4E 4d10fPHHLEeTMXjdqof0fNvbjnJs5rxmq+V8lJkPSSdE/rHgrOT1/Gwdj8OKj2rhztKo yIug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9gVnqVrrUA1mr0k46HEMKibQCwArc3D/s7fZlpVclMo=; b=HOTxAJRkIfDxgtrb0xSM7nGZQR1BbxQbAZNUbSHqcbytcdQqdws/GkUt64k4kDVWZk YVfyuMVRljaQt6MMNaHd9KlQTUFR2NfJeCqfu1xniCP0Z/i1O3irrUHITEVqxEXyO637 baKdeEaaxUV3Ke/UqngoaWkBIpev5d9LbOo0ySdk3Rjw5o3vIUJWQE0cMVahJCh4AUAw a+cxq9JneQSVXQskhkPD4BK0S/Qwkf58iIgGRZ1ImVQaXEmI/prMzQ+8yqzh1P/4KhOP u/g3nyTeG9eBX1rsFK0tUbHLB7wwmc0E/S1PiIQlr5UiCNGdBVz61IgPpII2Ckt3X5Tc sWlQ== X-Gm-Message-State: AOAM530qf0Hja8qc45oM6vwftjK151ra8q3jS4sRrf/boJOSQFZkmkBq xEIDsKn2HxvLp5KrKKW+Zr5fhXjI4fb8ncIM5NQ= X-Google-Smtp-Source: ABdhPJxKnh/w2TfJGWjTMPh4hWQF1Clhd7BiCjBbwGm0XnLrl+iTMwwvALRo/3vmYRTa7KAy0cbdkRTJEfnwjDOfpVw= X-Received: by 2002:a02:c002:: with SMTP id y2mr6821740jai.107.1616667583371; Thu, 25 Mar 2021 03:19:43 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: PstreeM China Date: Thu, 25 Mar 2021 18:19:32 +0800 Message-ID: Subject: Re: Adding /usr/src using freebsd-update To: Kevin Oberman Cc: Doug Denault , Valeri Galtsev , "freebsd-questions@freebsd.org" X-Rspamd-Queue-Id: 4F5h1F4sSMz4rGw X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=CJqbTWub; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of pstreem@gmail.com designates 2607:f8b0:4864:20::d30 as permitted sender) smtp.mailfrom=pstreem@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::d30:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::d30:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::d30:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-questions] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Mar 2021 10:19:46 -0000 Just download the src.txz from official site. Then tar -C / xfvz src.txz will add the src component into the system. Then, I think you can use the FreeBSD-update to update the src code tree. On Wed, Mar 24, 2021 at 12:12 Kevin Oberman wrote: > On Tue, Mar 23, 2021 at 8:45 AM Doug Denault wrote: > > > On Sat, 20 Mar 2021, Valeri Galtsev wrote: > > > > > > > > > > >> On Mar 20, 2021, at 9:42 PM, Doug Denault wrote: > > >> > > >> My motivation for wanting to do this is basically because updating > > >> 11.3-->12.2 broke my Lenovo Ideapad. This is a "well known" and > > >> apparently has a workaround but I could not find a combination that > > >> worked following the very helpful suggestion out of the X11 mailing > > list > > >> or google. What did work was 13.0-RC2. Out of the box following > > UPDATING > > >> and pkg notes. Whatever the issue was it was obviously complex > > involving > > >> the interaction of several components in Xorg, FreeBSD and whether or > > >> nor EFI booting was used. All except the last one are perfectly > > obvious. > > >> I only mention this as background for why not use git or subversion > > (for > > >> a while anyway). > > >> > > >> The fix required that kernel sources be available. On the Lenovo that > > >> happened not to be a problem. On another laptop I did not have > /usr/src > > >> so freebsd-update did not add/update it and I saw no option to add > > >> /usr/src. The conf file apparently says take care of it if it is > there. > > > > > > Did you try to use svn? Something in lines > > > > > > svn co https://svn0.us-east.freebsd.org/base/releng/12.2 /usr/src > > > > > > (confessing: I?m lazy guy, and about a week or so ago I still used svn, > > > successfully). > > > > First Thank you for the suggestion. Re Lazy, me too, hence looking for an > > "easy" answer. The svn port had similar [non]success. On the system in > > question this was an "I wonder if this works". I have 500+ packages on > > this > > workstation and have not yet added gimp, yet so there is no need for more > > interlocking dependencies. On a Lenovo laptop src was required to install > > the drm package required in 13.0 to make it work. Happily it was already > > there. > > > > >> On my HP no /usr/src. I did a package add for git adding 32 required > > >> packages and the installed failed to deliver a working git command. So > > >> on to subversion with similar results. This with 12.2. > > >> > > >> As I had already updated to 12.2 and it was working I removed all > > >> packages, copied a 12.1 /usr/src from another server and did a fetch. > > >> This added in the files new to 12.2 and did report doing anything > else, > > >> so I rather doubt this is a "good" version of the src tree. > > >> > > >> All of the above for my real question. since I had a number of 11.3 > > >> /usr/src trees, if I had just added that before doing an upgrade I > > think > > >> that will work. Correct? > > >> > > > > > > I would just move existing /usr/src off the way (rename) and pull fresh > > > new of the release you need (say, using svn command if git doesn?t work > > > on that machine for whatever reason). > > > > Probably a good idea. On the servers we go the poudriere route. On > > workstations I have never gotten xorg to build and usually do not have > the > > time to see if it will work this time. I will probably continue my > thought > > experiement when the workstation morphs to 13. > > > > I will learn git going forward. I would be nice if for the non internals > > folks if this could just be done via the browser. I have no idea if > that's > > even possible > > > > > Valeri > > > > > > > > > _____ > > Douglas Denault > > http://www.safeport.com > > doug@safeport.com > > Voice: 301-217-9220 > > Fax: 301-217-9277 > > > Your point is exactly the one I made back when the last security advisory > came out. That led to a long discussion which led to the addition of the > sequence number to the hash. All future security and erratas will show the > sequence number to resolve the issue. Search for a thread on the stable@ > mail archive with a subject of "How do I know if my 13-stable has security > patches?" It was the discussion and includes several ways at determining > the answer from just the hashes. None are pretty though all are clever, > but they won't be needed in the future. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" >