From nobody Mon Oct 25 15:40:13 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 EB9F3180E71C for ; Mon, 25 Oct 2021 15:40:27 +0000 (UTC) (envelope-from eduardo@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 4HdK0W6JhLz4tmn for ; Mon, 25 Oct 2021 15:40:27 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: from mail-lf1-f48.google.com (mail-lf1-f48.google.com [209.85.167.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) (Authenticated sender: eduardo) by smtp.freebsd.org (Postfix) with ESMTPSA id B1F8359BF for ; Mon, 25 Oct 2021 15:40:27 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: by mail-lf1-f48.google.com with SMTP id bi35so5874893lfb.9 for ; Mon, 25 Oct 2021 08:40:27 -0700 (PDT) X-Gm-Message-State: AOAM531IIuRdKl+QupIv5Yqggi2+Ls6pYLbgMF7ddAKQ7r6vJUGzYFvF XV44cg0vTqp2mwIIt1/BJP+8/mpNb3itpcwz8l0= X-Google-Smtp-Source: ABdhPJzYa46yTs/hRLlBqweF5Zgc/AV93u0P2LWRCdeORsSQd+08FLgiPnNda/IT9aCbibR3GkzLABauQIyHQQOCcU8= X-Received: by 2002:ac2:4543:: with SMTP id j3mr13768785lfm.391.1635176426196; Mon, 25 Oct 2021 08:40:26 -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: <69bedb7d-373f-fd59-9a66-f0d602d84f64@protected-networks.net> In-Reply-To: <69bedb7d-373f-fd59-9a66-f0d602d84f64@protected-networks.net> From: Nuno Teixeira Date: Mon, 25 Oct 2021 16:40:13 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: what does "failed to read progbits" mean? To: imb@protected-networks.net Cc: freebsd-current Content-Type: multipart/alternative; boundary="00000000000007535305cf2f2e8c" X-ThisMailContainsUnwantedMimeParts: Y --00000000000007535305cf2f2e8c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Same here: kldxref /boot/kernel failed to read progbits But kernel failed to install. I will include log tomorrow, I'm doing a clean build with /usr/obj/.. deleted. Michael Butler via freebsd-current escreveu no dia quinta, 21/10/2021 =C3=A0(s) 20:14: > Well this is different .. I did a full rebuild (after "rm -rf > /usr/obj/*") this morning and now see .. > > =3D=3D=3D> linux_common (install) > install -T release -o root -g wheel -m 555 linux_common.ko /boot/kernel= / > install -T dbg -o root -g wheel -m 555 linux_common.ko.debug > /usr/lib/debug/boot/kernel/ > =3D=3D=3D> linuxkpi (install) > install -T release -o root -g wheel -m 555 linuxkpi.ko /boot/kernel/ > install -T dbg -o root -g wheel -m 555 linuxkpi.ko.debug > /usr/lib/debug/boot/kernel/ > kldxref /boot/kernel > failed to read progbits > failed to read progbits > failed to read progbits > failed to read progbits > failed to read progbits > failed to read progbits > failed to read progbits > kldxref: /boot/kernel/kernel: cannot load DT_RELA section > -------------------------------------------------------------- > >>> Installing kernel TOSHI completed on Thu Oct 21 15:05:00 EDT 2021 > -------------------------------------------------------------- > > Is something broken or just cosmetic noise? > > imb > > --00000000000007535305cf2f2e8c-- From nobody Mon Oct 25 15:46:49 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 62C351811F15 for ; Mon, 25 Oct 2021 15:46:59 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (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 "mail.protected-networks.net", Issuer "R3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HdK831db7z3Cmv; Mon, 25 Oct 2021 15:46:59 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding:content-type :content-type:in-reply-to:from:from:references:content-language :subject:subject:user-agent:mime-version:date:date:message-id; s=201508; t=1635176810; bh=evqOoNfxsKd2Id8Ksv5A9Z751/5g0dD2HMlG wMx9Mi0=; b=BdtwIf7shy0r9g+rJyWr+zbcbr/KkeCRdNEwqMLhuGtk4cTxX/FM mVxtfADcIJtY50VxIIHtgM17iroypC61De/9F7FKXtFfaVmk6mxTn+c5f6vU2gLS I4jN4OK9ej6X/4qwoV9Qh1pR23vXe5FZiK/2udiDiIu9Z9LLfTuuncQ= Received: from [192.168.1.10] (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 34BD24DD32; Mon, 25 Oct 2021 11:46:50 -0400 (EDT) Message-ID: <9b059d64-9141-1537-194e-69c6dcd3d081@protected-networks.net> Date: Mon, 25 Oct 2021 11:46:49 -0400 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 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 Subject: Re: what does "failed to read progbits" mean? Content-Language: en-NZ To: Nuno Teixeira Cc: freebsd-current References: <69bedb7d-373f-fd59-9a66-f0d602d84f64@protected-networks.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4HdK831db7z3Cmv X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Reply-To: imb@protected-networks.net From: Michael Butler via freebsd-current X-Original-From: Michael Butler X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: N This seems to have gone away after https://freshbsd.org/freebsd/src/commit/70f51f0e474ffe1fb74cb427423a2fba3637544d Not sure if the bug that commit fixes was the underlying cause, Michael On 10/25/21 11:40, Nuno Teixeira wrote: > Same here: > kldxref /boot/kernel > failed to read progbits > > But kernel failed to install. I will include log tomorrow, I'm doing a > clean build with /usr/obj/.. deleted. > > Michael Butler via freebsd-current > escreveu no dia quinta, 21/10/2021 > à(s) 20:14: > > Well this is different .. I did a full rebuild (after "rm -rf > /usr/obj/*") this morning and now see .. > > ===> linux_common (install) > install -T release -o root -g wheel -m 555   linux_common.ko > /boot/kernel/ > install -T dbg -o root -g wheel -m 555   linux_common.ko.debug > /usr/lib/debug/boot/kernel/ > ===> linuxkpi (install) > install -T release -o root -g wheel -m 555   linuxkpi.ko /boot/kernel/ > install -T dbg -o root -g wheel -m 555   linuxkpi.ko.debug > /usr/lib/debug/boot/kernel/ > kldxref /boot/kernel > failed to read progbits > failed to read progbits > failed to read progbits > failed to read progbits > failed to read progbits > failed to read progbits > failed to read progbits > kldxref: /boot/kernel/kernel: cannot load DT_RELA section > -------------------------------------------------------------- >  >>> Installing kernel TOSHI completed on Thu Oct 21 15:05:00 EDT 2021 > -------------------------------------------------------------- > > Is something broken or just cosmetic noise? > >         imb > From nobody Mon Oct 25 15:51: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 4D22D181336C for ; Mon, 25 Oct 2021 15:51:40 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HdKFS1Cfgz3FjM; Mon, 25 Oct 2021 15:51:40 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qt1-x835.google.com with SMTP id w2so10730986qtn.0; Mon, 25 Oct 2021 08:51:40 -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:content-transfer-encoding:in-reply-to; bh=0iuVC/cVsAcGINebdouJ/PAPwrUiyyJshiQApnfcKZo=; b=PCW7UMvFmlCDiCF5EURfaWax/397a2wn7QZ3XBkjcJ+Z+elUas8E/Sm+v/jlWzXm5K 8lx2s4J/tUSjHw465eZh9PNYZ49yKO9u16E5gCNma6M+aE7BePrm9XdkkyduPIYuL6m+ ilmYPwINFiZYNkMn5fpNtuLTu1asy45qujRknGXD1ZS28tTy0PBMu+o3PPI92xYz6ep1 p9W8Qp8G35iaEIZKWd6czhI5aZdsn9mxvgYWjuqZsvRTKr8qAmYAk7mT7hUHednJmbdr +UYSxFdv/TsF3SWboFnyfCpk/kX2lfbsfdba/9GKgD5r19uuCo/CYCMMVvh4ltj5pVGY KfkQ== 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 :content-transfer-encoding:in-reply-to; bh=0iuVC/cVsAcGINebdouJ/PAPwrUiyyJshiQApnfcKZo=; b=JQjYWkWnVkmbw5JqP3vbiCr9puviBWWdJPgRoCydXJPdFTlswEnfFVqarw8c9tcVTk d2DAFr1WEXTBNKIRTN8Izbvivv8sDggoyhUtFVQl8yRCzEKX/MhJevq6ew0Kq8fD4GfD tp916My2YPcaUFLFSFQ3YrgsL8tnZz+M9ZP9O67Y9V/15hzUHmc/gWpChjws3sGZzV6M 44+bhhkOpXPuCD2nrlTXVIPyeoqQd9RK94aK+6Zsr2TlUMyTOcj3I36yJgFsD17Csx09 4KMsyVRi+T/Qv4KLHKhLphZ76OIdaJUckp7AtDrmCWaPiUJVNCvfXiO6BbNiXGwkVMI0 8EXg== X-Gm-Message-State: AOAM532AMEzde07Z5+M3Rw5Sqs+EWN6FHCHXeOUHHnQRy43WAFJh6K+N 5Mf2rLGL1pUZr4gZyTkdbpUvLPqtMwc= X-Google-Smtp-Source: ABdhPJw08Qzn/FD+5Ks4RhSn3MUMQBlA2kOCI/JR/kp1GAajVU3NBt2qlMVQ/Gu9nLlaTQL8fiR8Fg== X-Received: by 2002:ac8:7617:: with SMTP id t23mr18591444qtq.316.1635177099719; Mon, 25 Oct 2021 08:51:39 -0700 (PDT) Received: from nuc ([142.126.186.191]) by smtp.gmail.com with ESMTPSA id n23sm8545583qkh.134.2021.10.25.08.51.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 25 Oct 2021 08:51:39 -0700 (PDT) Date: Mon, 25 Oct 2021 11:51:37 -0400 From: Mark Johnston To: imb@protected-networks.net Cc: Nuno Teixeira , freebsd-current Subject: Re: what does "failed to read progbits" mean? Message-ID: References: <69bedb7d-373f-fd59-9a66-f0d602d84f64@protected-networks.net> <9b059d64-9141-1537-194e-69c6dcd3d081@protected-networks.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=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <9b059d64-9141-1537-194e-69c6dcd3d081@protected-networks.net> X-Rspamd-Queue-Id: 4HdKFS1Cfgz3FjM X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: N On Mon, Oct 25, 2021 at 11:46:49AM -0400, Michael Butler via freebsd-current wrote: > This seems to have gone away after > https://freshbsd.org/freebsd/src/commit/70f51f0e474ffe1fb74cb427423a2fba3637544d > > Not sure if the bug that commit fixes was the underlying cause, Yes, that commit fixes the underlying problem, which manifested for me as kldxref errors among other things. > On 10/25/21 11:40, Nuno Teixeira wrote: > > Same here: > > kldxref /boot/kernel > > failed to read progbits > > > > But kernel failed to install. I will include log tomorrow, I'm doing a > > clean build with /usr/obj/.. deleted. > > > > Michael Butler via freebsd-current > > escreveu no dia quinta, 21/10/2021 > > à(s) 20:14: > > > > Well this is different .. I did a full rebuild (after "rm -rf > > /usr/obj/*") this morning and now see .. > > > > ===> linux_common (install) > > install -T release -o root -g wheel -m 555   linux_common.ko > > /boot/kernel/ > > install -T dbg -o root -g wheel -m 555   linux_common.ko.debug > > /usr/lib/debug/boot/kernel/ > > ===> linuxkpi (install) > > install -T release -o root -g wheel -m 555   linuxkpi.ko /boot/kernel/ > > install -T dbg -o root -g wheel -m 555   linuxkpi.ko.debug > > /usr/lib/debug/boot/kernel/ > > kldxref /boot/kernel > > failed to read progbits > > failed to read progbits > > failed to read progbits > > failed to read progbits > > failed to read progbits > > failed to read progbits > > failed to read progbits > > kldxref: /boot/kernel/kernel: cannot load DT_RELA section > > -------------------------------------------------------------- > >  >>> Installing kernel TOSHI completed on Thu Oct 21 15:05:00 EDT 2021 > > -------------------------------------------------------------- > > > > Is something broken or just cosmetic noise? > > > >         imb > > > > From nobody Mon Oct 25 16:47: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 A4F54180AAEE for ; Mon, 25 Oct 2021 16:47:38 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from mail-ed1-f45.google.com (mail-ed1-f45.google.com [209.85.208.45]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HdLV16hxSz4pQK for ; Mon, 25 Oct 2021 16:47:37 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: by mail-ed1-f45.google.com with SMTP id j10so2095352eds.12 for ; Mon, 25 Oct 2021 09:47:37 -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=Tk1YkY5FN5UxYvpS120Bs2/pv6LOzW1Bt9+Hlxe5vog=; b=6JsSKN3FpkA1yvHrOL3ffeoaMVHnBDFNCJoQd2+BbJ3Vn1fhB+BlMUhj7YzZo41bRz ahVqmpqX3YiQMoZpuAgkOWctiHsiO4TqwwCWYvCABspgtXp/l6+FlIJjZg+TePDrikq+ UNwbpxurINOfr+YfEpJinrcqXSlwkTPMuKEsTcVD7dRw8av8E06TnBkvgPza7bJTFWhE AaVLs0xCNai5jqj4zgRoVGDyoYrTfsFmd5AajwPIUgNKZVPcL8GsvIwlzWUaQawXzres PrvVgkYMLAihJIgMq6Zr9xjSA1GQ6xeXhTxd0JQMaPmY00QjkyMa4EHzmeVgUkJyJrqI KL6g== X-Gm-Message-State: AOAM531l8uxRZxgKiXZEsgEYbhlPdRDvrSGKKly0EwLLet2j5X+h45gE JrDZJ6WNbv/tZdvVM/N1JlSUxBG0WP+RRHf2zITMMuyQPUxqH3Fw X-Google-Smtp-Source: ABdhPJw3pmiWp/6Nz3IXFaP/8+77Rsf+kFE2ABHVGb181r4icpiCN6tpg5lMHEmW4D+OtzE9IR6O6lLvCgyag/JO+Fc= X-Received: by 2002:a17:906:5e55:: with SMTP id b21mr16387782eju.58.1635180449335; Mon, 25 Oct 2021 09:47:29 -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: <20211022212947.GA59184@troutmask.apl.washington.edu> In-Reply-To: <20211022212947.GA59184@troutmask.apl.washington.edu> From: Maxim Sobolev Date: Mon, 25 Oct 2021 09:47:18 -0700 Message-ID: Subject: Re: Future of ident(1) To: Steve Kargl Cc: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000d39ea705cf301df7" X-Rspamd-Queue-Id: 4HdLV16hxSz4pQK X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of sobomax@sippysoft.com designates 209.85.208.45 as permitted sender) smtp.mailfrom=sobomax@sippysoft.com X-Spamd-Result: default: False [-0.76 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; FREEFALL_USER(0.00)[sobomax]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-0.29)[-0.289]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; NEURAL_SPAM_SHORT(0.52)[0.525]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[209.85.208.45:from]; FORGED_SENDER(0.30)[sobomax@freebsd.org,sobomax@sippysoft.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.208.45:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[sobomax@freebsd.org,sobomax@sippysoft.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: Y --000000000000d39ea705cf301df7 Content-Type: text/plain; charset="UTF-8" Just in case someone thinks this is something useful, I've got a PR filed against git to implement custom $Id$. There are no technical issues with the change but Git developers are not very keen on merging it in, since they see this as an obscure feature, no one needs. :-/ So if anyone wants to chime in on GitHub or git mailing list please do so. https://github.com/git/git/pull/1074 Thanks! -Max On Fri, Oct 22, 2021 at 2:30 PM Steve Kargl < sgk@troutmask.apl.washington.edu> wrote: > All, > > With the new world order, what is the future of ident(1)? > Should it be removed from base? Given a compiled binary > in base, how does one find the equivalent git info that > ident(1) used to perform? > > Having a few minutes to dust off old patchs for libm, should > I remove $FreeBSD$ tags in files I touch? For new files, is > it expected that useless $FreeBSD$ tags should be added? > > -- > Steve > > --000000000000d39ea705cf301df7-- From nobody Tue Oct 26 13:53:19 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 A76831822CD9 for ; Tue, 26 Oct 2021 13:53:29 +0000 (UTC) (envelope-from filippomore@yahoo.com) Received: from sonic315-20.consmr.mail.ne1.yahoo.com (sonic315-20.consmr.mail.ne1.yahoo.com [66.163.190.146]) (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 4HdtZc5pg9z3NGn for ; Tue, 26 Oct 2021 13:53:28 +0000 (UTC) (envelope-from filippomore@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1635256401; bh=f320D049J8wL//D4Jwsn+IcuCTMpuPv/Cc6LzgeDKv4=; h=Date:From:To:Subject:References:From:Subject:Reply-To; b=B+CD0wuMujukmiz/uQJ8VUHuh++NgE+SaKEj395ex/jNxB7GhuetkrwBftprbPt+NHE2Yijs4Y39yEHlFKgtyMGBkoU6BM0Lls2T2xJYhxEtoK4G+pzeT6822exkjEB4fokRR4n2trNrg9wHm4aNdE3ddM5rlP17/sRF05pJfIVcvL7yvR7NMplvJfsfQLFBNvmACLEBurC6KU84otfU5mSpOE2u1GbZOBxiWlZRlWSGM8KOhyNriqsHSLaFNm51in1QkryIQ7ZiEXq1WEBl4aYeBzvqFr9EUmkBp4CZ1hH0T/oIeZ1GAs5C0CSk/XTafidrqMg5nIt0yAfnt8Vt6Q== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1635256401; bh=t9ojJFhZr/y130SoKqiCXCbfq0btJtuRGAnaN1uOIOt=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=Azuu/q58uDtnhGnQD5a5TmV2+Y5sLyebVxy1AjpUYxVA1nb+5HeM4cTccIQEWeC+6eeVy0xMEq4m4UFdckr0LbHXH1ptbnFtPkO+tFE1goSDYnFWCbAlzlCYtEGVc+ClZF0OHZYDq1Ygk2TwbS7yxmlAcAZIKjNohgIyJDUgW7yTlo5wbNEab/t9Qo7ANsMjh1MCJXLpIJYb/Maj7QbgHaveuPnMCDT1XtY8oUGMVMC/1daAg6scEw2niXjUMV6O3rJej0X+r0D1MvdYqiYOHE2lZkAuevw3qtzorYIaxMVoIdSCT7/nLdnz3MTRZaBogWVtDACmXKN/SugXCbOAuw== X-YMail-OSG: FHKae80VM1l1FiYEE08Lk4Q0OcA7qdGz67b2Uox7FFa7jbux2GInOBg7qiYUJTG .RBU.iOXhcohY7LD8HN1Iw8TvLxRf_sj.1apUWSxLwizqRkNOHaTtoDlPB_J3tsDg7Lde92lEcJm FYX4BDJUyMO6Q5mAOfjLT2Ngmz8hHvE5qd_96DWzHdz2zlCXEW7YPbzTWcHYK3PwDklWFtrNi__n cFrhbymvfMqpzYSqXjCovi.EjIjSEOGfbxy2NgB1Cv2Ps89Gkjux8T5eHeEJJQfme4RczE_bAl4E rLFYhaSiPlRUb2NAdUOILGm_4j8CiRfgk.sPmWBjesIaZNIh53.YjpPj3K3BSWjVPp9xR7axEttK v1HZ3qYaTYEut03MGnY7Fk1PQTtTNs0KMLzyWMNWcavl9QmRXuL2Wl49mVtAZAlTnGtFE053HdWZ QOxKP1gklSqfjF0YcYi7gAafueIzoKRRD_e8ZV.SOx4byx6n7.jOSjvPHSMRH6hoWhZsLMoXMka3 LzJUe1G7N8ichFDplNRV5eCQ.p.1JenglN3Ve0_ITHtDkbAfy.LZ1ZHwpMwYR9ijd03Q8afjiySW yJiNYVzshstVcXIdiIzXdRaw_0uq7DuzwdcHHbVobQXXF5CQJFMf8tLRigi1f0MNK9GPLDAUBupz jz9UTXXGVxyyFcSVFGnCrv9etGFeQIUzPCOeDu2gJwVmd4ql4v2MtYZGpVV.ekt77sKFxwNaqtzR AyiEkK1jA8AxYlOZiU5Xh.6n_2nW4U_1KQzcFSgRpCVXmNg9187Y1y52bDv_S1tDTE5dtKo7Zkq9 Kw.VTNzfRyXo1gTgFM7zbO8tChuj_bpriyC27TXlSMf2dzMFGGhQc4aMcNxjB5YGKFG86Unxuult rovEZJ55fmlT.83s7mK8mXQJOJSW_HcMB1GQ2F7mf5T28McDyyBSRNTiX6usLvvMeVIvYm.01eD5 dvqmVt4ZwPhFsRnPS6axPB4VTTIzVcrORBdOapEZ91_fy0s_eboaldWJfQl1QmS3JJ1joocolBvh Zi669tsareZlHGJBKyLfIxao1KzyJWmwijzUezy9mQjbZ1AJw7Cezdq9nYbg31h2W08C3OdQMf0W 4SjGjG.rXQFSOPHGm_uDEhPomNVbW4N7gM7BOjuKFJWas368tnIhIwRSc02xqQkvroZGL1LOzAEy WDakKAkCX1_ati_T3c9SbGdlQSST9FPWOal9kywlC2CmmCzuGd3.5fpTeLBT1wvPoCAMAQwYw93V 4pNLonKvpv1Uc0RFX8UEW.hHpIr2CQ3DyXNDSD3FEHQeRejPx47WCDsFE0Qka4jz72rFCkbw5C4_ 666eKzY4CQSJoKKgvoCVQPMY_kmA92oOu.c6FH1xLE_If5.S9ts2cdGjqfREcJUXK9S4gvwJnMx5 xk15xmU_cc0KBB77tbZtJmCbYrSydCfJxXUa3qECyEGtMfvUpSY3J2PcqStI.hsg49FP6M8vqpsD zc.IMGRyFSV4ZAc6kTwGj0QUNwcJgtq2v_dXhbJ0BD8nRzZiz9l64l9x8Z39AGzM3mw5nH9GyIka D0dp_rLTf_8jRNvAqQZEnAibndvDH3aFi57SfQs9GiBznr0AuckFOkaDxrvxbPRVpdj9WtYYfFe0 tPAq8EuXkBnA.cOi8qurp.KM2w2QhRiQHuFsh3EoYIgH1r1IewQEKL1cub5i19i1oCeMr.AYe9F8 4U1qUJfzqgxILxNZy3tXMPkszU7Uh3haSoDMqA4.2TNt7JzIdUiKJVYYCOtD.nSn8CXqGCT07JTI GIzOKUyTw4cC1tkDRzM6ySU06Xwhnz5GLMKQkHYOESYgyp6R9yHYZ6gRh1.UUwFjSZTO7Ag.o9cV o1vmZq21aK_ezRf5c9Yvysz7oRqYlufiMygSWL4BPBPARVvdLLg50ROv2nmNXPg_8qrHy10o8DVe vc0UFn5kC4MaLNdwnuuSnesUF2CVQf.eTLXLO.V5mBe1R5tlptr7SOrUx88V46UOqLJFxUKxGfA. nBI9fx_UNuqxegMz44l0dGS1filRXrlEWiSMgnPWppxwLuEsKOcRZE0obtkHKOnXTAqyCXVhz6hL 0JvrT6nQp5IAXIgXL1ClKopN1VDH.25Ni_KKQJ41b9QmXV_h0oPDyyD_mMr.CWtLKzC9VY3FlvGa 6nbc_nKkoRCyGMoXg7vv6HUz8.c1K_n_FfkRaBV0ogdZxazapj2xasA-- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.ne1.yahoo.com with HTTP; Tue, 26 Oct 2021 13:53:21 +0000 Date: Tue, 26 Oct 2021 13:53:19 +0000 (UTC) To: FreeBSD Current Message-ID: <293177224.1764301.1635256399076@mail.yahoo.com> Subject: Error during installkernel 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/alternative; boundary="----=_Part_1764300_243476421.1635256399075" References: <293177224.1764301.1635256399076.ref@mail.yahoo.com> X-Mailer: WebService/1.1.19198 YMailNorrin X-Rspamd-Queue-Id: 4HdtZc5pg9z3NGn X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=B+CD0wuM; dmarc=pass (policy=reject) header.from=yahoo.com; spf=pass (mx1.freebsd.org: domain of filippomore@yahoo.com designates 66.163.190.146 as permitted sender) smtp.mailfrom=filippomore@yahoo.com X-Spamd-Result: default: False [-4.00 / 15.00]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; FREEMAIL_FROM(0.00)[yahoo.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; RCVD_IN_DNSWL_NONE(0.00)[66.163.190.146:from]; NEURAL_HAM_SHORT(-1.00)[-0.997]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36646, ipnet:66.163.184.0/21, country:US]; RCVD_COUNT_TWO(0.00)[2]; RWL_MAILSPIKE_POSSIBLE(0.00)[66.163.190.146:from] Reply-To: filippomore@yahoo.com From: Filippo Moretti via current X-Original-From: Filippo Moretti X-ThisMailContainsUnwantedMimeParts: Y ------=_Part_1764300_243476421.1635256399075 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I tried to update my system today everything fine but installkernel:=3D=3D>= zlib (install)install -T release -o root -g wheel -m 555 zlib.ko /boot/ker= nel/install -T dbg -o root -g wheel -m 555 zlib.ko.debug /usr/lib/debug/boo= t/kernel/kldxref /boot/kernelfailed to read progbitsef_read_entry failed***= Signal 11Stop.make[3]: stopped in /usr/src/sys/modules*** Error code 1Stop= .make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/STING*** Error code 1= Stop.make[1]: stopped in /usr/src*** Error code 1Stop.make: stopped in /usr= /src[root@sting /usr/src]#=C2=A0 [root@sting /usr/src]# uname -aFreeBSD sting 14.0-CURRENT FreeBSD 14.0-CURR= ENT #57 heads/main-n250195-6ba2210ee03: Thu Oct 21 21:19:23 CEST 2021 filip= po@sting:/usr/obj/usr/src/amd64.amd64/sys/STING amd64=C2=A0Filippo ------=_Part_1764300_243476421.1635256399075-- From nobody Tue Oct 26 14:16:01 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 E4FBF182D3D2 for ; Tue, 26 Oct 2021 14:16:13 +0000 (UTC) (envelope-from felix@palmen-it.de) Received: from stef.palmen-it.de (stef.palmen-it.de [IPv6:2001:470:1f0b:bbb:1::1]) (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 4Hdv4s0rN0z3mKc for ; Tue, 26 Oct 2021 14:16:13 +0000 (UTC) (envelope-from felix@palmen-it.de) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=palmen-it.de; s=20200414; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:To:From:Date:Sender:Reply-To:Cc: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=6ScngX7m8Du0GAOqXPGQ+tvyv9OER3Xx89LWgVhjt9M=; b=D2f4fzdricAsYuSAIhnpcPkrAT NUL0LJ1Ygzxm07qC7lzbRBW35n83EYUJ1IAgqO+AFOQE9cRud+ik765tcAP3GrVBNidR6L+4ylSzZ WFjEnMEw6EAoWCcsk0OS2c2EoZd7QY6W4l06ZvNp4KSZNKJ+ymcn3GUrRauKflcrvtB057MuCjL25 NeXJuV5xokFK2WY8oKThMU/rjb1M8GVaAJ0LdNF2T7WOEGLPOFwyu4OZyfA4fa2hDVWkJ6kv8Xnnh r6Z3s25wsoJWC1X8Ds+GdKLIi/QvB0uAYxrIeiPGtcDVrCRE9EA+hu2hyWcXz7ZAyKkj9Yb6rVBV5 lj58VeIg==; Received: from [192.168.71.101] (helo=mail.home.palmen-it.de) by stef.palmen-it.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1mfNFE-0004jM-LW for freebsd-current@freebsd.org; Tue, 26 Oct 2021 16:16:04 +0200 Received: from nexus.home.palmen-it.de ([192.168.99.2]) by mail.home.palmen-it.de with esmtpsa (TLS1.3) tls TLS_CHACHA20_POLY1305_SHA256 (Exim 4.94.2 (FreeBSD)) (envelope-from ) id 1mfNFD-000Cx6-ES for freebsd-current@freebsd.org; Tue, 26 Oct 2021 14:16:03 +0000 Date: Tue, 26 Oct 2021 16:16:01 +0200 From: Felix Palmen To: freebsd-current@freebsd.org Subject: Re: Error during installkernel Message-ID: <20211026141601.rjuuaurnbwuq325w@nexus.home.palmen-it.de> Mail-Followup-To: freebsd-current@freebsd.org X-Face: /1K@t"h.}e~pR@]c7HorQ!T`F^RJCa'BCr#e>IKA{>C/9OTGB4|xh"y2{?1Z5M i2w"AH^pN_LlHR^{+f',_Np~;.B;!M/bL}*qk]p5*r7F5vW};{:@4u5S?T&f0$7BJ-71Q5SV]:v$`5 A0[DZ:=?S52x8HJ~5@^P_\T@MsjG{R( Organization: palmen-it.de References: <293177224.1764301.1635256399076.ref@mail.yahoo.com> <293177224.1764301.1635256399076@mail.yahoo.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 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="uxmy2qxvgujkzqd5" Content-Disposition: inline In-Reply-To: <293177224.1764301.1635256399076@mail.yahoo.com> User-Agent: NeoMutt/20210205 X-Rspamd-Queue-Id: 4Hdv4s0rN0z3mKc X-Spamd-Bar: -------- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=palmen-it.de header.s=20200414 header.b=D2f4fzdr; dmarc=pass (policy=none) header.from=palmen-it.de; spf=pass (mx1.freebsd.org: domain of felix@palmen-it.de designates 2001:470:1f0b:bbb:1::1 as permitted sender) smtp.mailfrom=felix@palmen-it.de X-Spamd-Result: default: False [-8.80 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[palmen-it.de:s=20200414]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_MED(-2.00)[palmen-it.de:dkim]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2001:470:1f0b:bbb:1::1]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; TO_DN_NONE(0.00)[]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; RCPT_COUNT_ONE(0.00)[1]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[2001:470:1f0b:bbb:1::1:from]; DKIM_TRACE(0.00)[palmen-it.de:+]; DMARC_POLICY_ALLOW(-0.50)[palmen-it.de,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N --uxmy2qxvgujkzqd5 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Filippo Moretti via current [20211026 13:53]: > I tried to update my system today everything fine but installkernel:=3D= =3D> zlib (install)install -T release -o root -g wheel -m 555 zlib.ko /boot= /kernel/install -T dbg -o root -g wheel -m 555 zlib.ko.debug /usr/lib/debug= /boot/kernel/kldxref /boot/kernelfailed to read progbitsef_read_entry faile= d*** Signal 11Stop.make[3]: stopped in /usr/src/sys/modules*** Error code 1= Stop.make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/STING*** Error co= de 1Stop.make[1]: stopped in /usr/src*** Error code 1Stop.make: stopped in = /usr/src[root@sting /usr/src]#=A0 >=20 > [root@sting /usr/src]# uname -aFreeBSD sting 14.0-CURRENT FreeBSD 14.0-CU= RRENT #57 heads/main-n250195-6ba2210ee03: Thu Oct 21 21:19:23 CEST 2021 fil= ippo@sting:/usr/obj/usr/src/amd64.amd64/sys/STING amd64=A0Filippo Ignore it. The new kernel should boot anyways, and after installworld, installkernel will finish successfully. It seems kldxref again needs some new feature, but it's not part of the temporary tools built, so the host's (old) kldxref is used. --=20 Dipl.-Inform. Felix Palmen ,.//.......... {web} http://palmen-it.de {jabber} [see email] ,//palmen-it.de {pgp public key} http://palmen-it.de/pub.txt // """"""""""" {pgp fingerprint} A891 3D55 5F2E 3A74 3965 B997 3EF2 8B0A BC02 DA2A --uxmy2qxvgujkzqd5 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEqJE9VV8uOnQ5ZbmXPvKLCrwC2ioFAmF4DZsACgkQPvKLCrwC 2irnvAf/SzBVdNpCmOhnC5ALRl9E/p0jZt0yDxvintdK2yFJ4KFYStnbVMhB9hoB wwNBWAh25KdaILvw79tTjPMF4bBuwvBZfhZvMP8cl5zqsk30xOtTDFJ04g2T3Ocb OTtA6n0I3kWgThZzjhYx/crcZdy4sTXbJ5Kx8XPKlQxzG2oG3KUjhYsSXdEGKAww Gmd6oetuXrg2FX4ozAszn7MBlT0wbT+qe/FrlsGUMtcOOd5slaSm7MOIm3/NXiu1 5l8gD6YCfe6F97aJPCLQuPHI2tvLa/4aayTpYsgdBxb1hW4YtDHpUJ61BIHL07VL 5RyrpbNtDsutSAM/6TK4nDpfxh8mjg== =iM0W -----END PGP SIGNATURE----- --uxmy2qxvgujkzqd5-- From nobody Wed Oct 27 08:50:29 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 A0C451825DCB for ; Wed, 27 Oct 2021 08:50:42 +0000 (UTC) (envelope-from eduardo@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 4HfMpp3hXfz3jX4 for ; Wed, 27 Oct 2021 08:50:42 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: from mail-lj1-f175.google.com (mail-lj1-f175.google.com [209.85.208.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) (Authenticated sender: eduardo) by smtp.freebsd.org (Postfix) with ESMTPSA id 5D8A929E5B for ; Wed, 27 Oct 2021 08:50:42 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: by mail-lj1-f175.google.com with SMTP id i26so1561894ljg.7 for ; Wed, 27 Oct 2021 01:50:42 -0700 (PDT) X-Gm-Message-State: AOAM532EFeKQQD4l7v2OrBVRUs+shyU7F40+jZ3JVMsUEl4mdmDmAuTm uBTq4av3KUkWjDwoy8430Balk+0CpRTIqXE6yFQ= X-Google-Smtp-Source: ABdhPJy4uWyOLzyZqo7pOQkvw0iQqruJAEvmMqfenkwluS0OSBj29CgG8v6Iu71VnG5ZAAxYm75XZFhtZeoe3DkUc5o= X-Received: by 2002:a05:651c:2328:: with SMTP id bi40mr31620979ljb.121.1635324640669; Wed, 27 Oct 2021 01:50:40 -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: <293177224.1764301.1635256399076.ref@mail.yahoo.com> <293177224.1764301.1635256399076@mail.yahoo.com> <20211026141601.rjuuaurnbwuq325w@nexus.home.palmen-it.de> In-Reply-To: <20211026141601.rjuuaurnbwuq325w@nexus.home.palmen-it.de> From: Nuno Teixeira Date: Wed, 27 Oct 2021 09:50:29 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Error during installkernel To: FreeBSD CURRENT Content-Type: multipart/alternative; boundary="0000000000004cb75805cf51b03a" X-ThisMailContainsUnwantedMimeParts: Y --0000000000004cb75805cf51b03a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Same here: --- kldxref /boot/testing failed to read progbits failed to read progbits failed to read progbits failed to read progbits failed to read progbits ef_read_entry failed *** Signal 11 Stop. make[3]: stopped in /usr/src/sys/modules *** Error code 1 Stop. make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG *** Error code 1 Stop. make[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src --- Felix Palmen escreveu no dia ter=C3=A7a, 26/10/2021 = =C3=A0(s) 15:18: > * Filippo Moretti via current [20211026 13:53]: > > I tried to update my system today everything fine but installkernel:=3D= =3D> > zlib (install)install -T release -o root -g wheel -m 555 zlib.ko > /boot/kernel/install -T dbg -o root -g wheel -m 555 zlib.ko.debug > /usr/lib/debug/boot/kernel/kldxref /boot/kernelfailed to read > progbitsef_read_entry failed*** Signal 11Stop.make[3]: stopped in > /usr/src/sys/modules*** Error code 1Stop.make[2]: stopped in > /usr/obj/usr/src/amd64.amd64/sys/STING*** Error code 1Stop.make[1]: stopp= ed > in /usr/src*** Error code 1Stop.make: stopped in /usr/src[root@sting > /usr/src]# > > > > [root@sting /usr/src]# uname -aFreeBSD sting 14.0-CURRENT FreeBSD > 14.0-CURRENT #57 heads/main-n250195-6ba2210ee03: Thu Oct 21 21:19:23 CEST > 2021 filippo@sting:/usr/obj/usr/src/amd64.amd64/sys/STING amd64 Filippo > > Ignore it. The new kernel should boot anyways, and after installworld, > installkernel will finish successfully. > > It seems kldxref again needs some new feature, but it's not part of the > temporary tools built, so the host's (old) kldxref is used. > > -- > Dipl.-Inform. Felix Palmen ,.//.......... > {web} http://palmen-it.de {jabber} [see email] ,//palmen-it.de > {pgp public key} http://palmen-it.de/pub.txt // """"""""""" > {pgp fingerprint} A891 3D55 5F2E 3A74 3965 B997 3EF2 8B0A BC02 DA2A > --0000000000004cb75805cf51b03a-- From nobody Wed Oct 27 10:21:36 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 0B5A0182A2CE for ; Wed, 27 Oct 2021 10:21:47 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 4HfPqs6k3Rz4dTp; Wed, 27 Oct 2021 10:21:45 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1mfg3s-00005n-6A; Wed, 27 Oct 2021 13:21:36 +0300 Date: Wed, 27 Oct 2021 13:21:36 +0300 From: Slawa Olhovchenkov To: Maxim Sobolev Cc: Steve Kargl , freebsd-current@freebsd.org Subject: Re: Future of ident(1) Message-ID: <20211027102136.GC77338@zxy.spb.ru> References: <20211022212947.GA59184@troutmask.apl.washington.edu> 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: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-Rspamd-Queue-Id: 4HfPqs6k3Rz4dTp X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of slw@zxy.spb.ru has no SPF policy when checking 195.70.199.98) smtp.mailfrom=slw@zxy.spb.ru X-Spamd-Result: default: False [-0.99 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zxy.spb.ru]; AUTH_NA(1.00)[]; NEURAL_SPAM_SHORT(0.11)[0.113]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:5495, ipnet:195.70.192.0/19, country:RU]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N On Mon, Oct 25, 2021 at 09:47:18AM -0700, Maxim Sobolev wrote: > Just in case someone thinks this is something useful, I've got a PR filed > against git to implement custom $Id$. There are no technical issues with > the change but Git developers are not very keen on merging it in, since > they see this as an obscure feature, no one needs. :-/ So if anyone wants > to chime in on GitHub or git mailing list please do so. > > https://github.com/git/git/pull/1074 Or temporary put one file into devel/git/files? > Thanks! > > -Max > > On Fri, Oct 22, 2021 at 2:30 PM Steve Kargl < > sgk@troutmask.apl.washington.edu> wrote: > > > All, > > > > With the new world order, what is the future of ident(1)? > > Should it be removed from base? Given a compiled binary > > in base, how does one find the equivalent git info that > > ident(1) used to perform? > > > > Having a few minutes to dust off old patchs for libm, should > > I remove $FreeBSD$ tags in files I touch? For new files, is > > it expected that useless $FreeBSD$ tags should be added? > > > > -- > > Steve > > > > From nobody Wed Oct 27 22:21:29 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 302C7182E927 for ; Wed, 27 Oct 2021 22:21:43 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic303-25.consmr.mail.gq1.yahoo.com (sonic303-25.consmr.mail.gq1.yahoo.com [98.137.64.206]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4HfjpZ0vnFz4sTG for ; Wed, 27 Oct 2021 22:21:42 +0000 (UTC) (envelope-from marklmi@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1635373294; bh=0U2WnItN8KrEHHntfcE1QVVz7jImdQO4+hmas8MCyoo=; h=From:Subject:Date:To:References:From:Subject:Reply-To; b=VjyfcinFpggaocqVTvNMxepBeR02Y/AHe0QgT28il0skcTQ/NcWOUJr+S4rqv2iuVg4XVOj7eNaMML1go3rde4b68JRwqfmCFFcvXQqFx+LSLRCBX9Fj+7kh9vcNj+gE5pEn0vFGhqQn2bhgvEXsitbuj62KMouyT6YuLKFKPrxNr/MsT8XRnLsfwbPdHouLXGg/UiqFmIjRJS/ACjE8PrFxa7mYCCesKTAXEQ93UVncLKRS8S6p+jagzMPUqqHbKkb27Er741aN0FzW/vMTeElY7PRvZxKS7yR9wZ9MAdpsdwO8bBI0vA+LcRnmpUb616tV0mq3FeVaw/u5zlAA5g== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1635373294; bh=8hByU5zy76u0FYGdH3oMdo6+CwJXMGnEwthm7trrxM3=; h=X-Sonic-MF:From:Subject:Date:To:From:Subject; b=SUS98Hv2LJQ3LXuOW6FH0OBiBPZkebCRyn44cHSI6tdUGbXvu1JT2bV+ACbBmUx48XEstdd930cK1M/BjbkBWQYmR8uPHLWRuQhPC3g2AdiIf27YkqPhl5etpNGvYClKYCMJ4vxTc+YGfMBweeVdYQJzXBZ12yHkg1Zy4a93Zom7zI6lc1qGQCgf8QBiYV38qReM0aXDIPZHicoiFnZAHXjYoHGaneYy7ZREYhMwxx/wfEfLTYcwmbep8XZfD2fJcQcTOn+B5zIVAd6QUjP6MhCwGygMKAitTISIErgFLYk7vI6QHwvMPD6eqbbn/BdxDbISNiUkNTIoR8gGLjgvrA== X-YMail-OSG: gnMIV_QVM1m3rrfjytZVgi.NdEayF6AN6A6GeMlDUKCXdSIFHgTpGg5rX9YXL.q VkGrDI_opoT6F5SL8n5lN36FpXu7YX8c.xTTjise4wCnBlFiWssfb6_V7xLoMJJjJKjP9BU_DYku 2b4.mS47.8MCrzyeFSEj7C14OrjEmouNWDPt7pM5iZJJH13O44vWxR5xeyL98RwFwXS3QI_g.RtD Tkd9wSz2HlDqUrZ3nuQRY1J_4Pt43dpxDbUX643DOHWuY6nq_sBQ505gzFcOquNIjzifa7UR2MRg G4R672Y0z0FWeoxN4P8VJ28cXx8jUS4DanrgKsL5zZieSY24Y2zqLzOubelSPyRS.AqF8x9UyNv2 Nmjj_dKqbvCBJS3H9imoQvowuHxvbbDRWYfcmkJBIbNuNwU78p2.m1ELHfWR5NWXSRA18SVQgQRc 1NRsaOXk7ZFt2C0UFjp5Rh3fYjbkCpBFdMLMAk15N52SCbPBhgSTp5Uv_mNAdqKWYqoIgjNzdDom JOwsJ1aUU315mZ4_3zIeurACUiK.0KrQdQtQY8OMJePYZrERS1bH.I0nzsm5Lijnc5xtQlzfBZ0w dSG_E8R6KLN28WdO4ZbU.ZAYEISX0_Rb.i.7Q28NPaCItEuFMjC_xBP0xCnnvU4A9ffRGK6jVZdX iyRMkQdccveDpCscnhz4aKLb0NXrcosYp.pKHaJv5FmqmKLyfCrRn2TA24LuFm.U1s1HOE.R98JH mlSiTJpqT.o2Bq6ag18IFcwNX1cRG3E6zwaJcYfjflsN5EMkqEjtEB.0EYu3P1QcsU7HImzKikeU 2PpTM8Gxa6HsOkOguH9yMYQJmCTzABVxTEMyjX3wn_3pS_cHhdGEJxsoG9E657Odi8kB6h9hZKDb O8qin5ZD7ZR9lMPrvs4rRmLuOa5Se5XRp8MjfI4mzX1CAeu03Lc5z.PIbOVrr.0DnULf2VX1XtnP 9hx.Za._GR1BD2DjAt6iUhCgBsK.B6I3cBaW32DSafm_lG.YmjZrwBftXowj3yRYCL4j_6ulr6.9 xJZRnBDBxqCYLKe0t_L9yN5O4.3ZO3FKVRhdu8bTgTz.NKOzn3xxHhlOPuaVR40wayabCexavB4w PeJz5wm2mdbVa2elCcSFcUWbEEx1GFsd5Qs3u3YX127zRIhuQOlFhZT1DWbKdbzzmMYJgzzggnXs 1hdV7csEw1a6QfCOMshvR5k9wnXwTxzETlyJON7vyVf3SdXYjzgXu46zTHQBUqhrbPQH0Gd_gPDm GTyHjFncvfcz5tapA.KIHMMnmH2yp7sj1ZCN1s.eTAnEryGb8nDBITLVnlUMS_9mrCigF5dr98Mp UOmGExnTwNUxqmlm8FMndtsjE.ib4xfs6VI0SRzSU6vZomoGtPIGjbVgOt_ZeuxNZaX66Ve0nhqv VrjQTVDGSMNrCEGLN.M_Ehpz43r_pZQ0ooX3_lhKWSymshPNYu7f2SVr67C2suF9zhOqOhNh19Mi vBJBKw4SXzoK51QRD.RAG4OwLWJ3cABnnjt7Bbk_eubRTM7GcOr3UE7Ecqr9w6SXw9pIc50uOpDX pZqgGuQc3IrdxLS5E4K8qeIWNc3tSlvk.1AqEBQOB4fDgbmXZYDhda8aOhGttB8L8Re.UvwTydnH El0vRtTW8lonFklK2_VEa9IxPBz21tspYEIjrbt4h_JM4lh_pt1y_MCEFENG7TE0CUvx9fgAPJ1l 7yGkn4hiWKKlv_CD9Gdp.AAtrn3rA28umg0TwbICMmfSBVVs2aLjU98BduH9aUkrHauQMdQz4AW3 7cQF4GEf6QTbhLwGPZK1JpN..3ygsqRnFVreed1qEicXisfcMG7qRBBk2OuGDW99sz6kW6lGr3Bm JV0oq.HjpPELPTkXDN9Ba1gJxi1ZHMZn4F24_rVEGKRKefBgDi7ln9h2Kcv.PyvJamsqfx5Q_3lN LQFFuRWkU7JfJvZU.y.zGUpxUeTkeEUc_PSSD051ftryQ36AHY1jJV8RlXDj_nfV55yE4T4g_h30 0DcHf1vL2MCVigLWhRlR56dFgKKVAGrw0Lma4q7VRJCjqEWJoZy4aaPUT4ACN5qOsfmPfDPQ8fLA Uf49HeQNJ1wS4OYTFdGJ0FwXoAW5tIeBu86rCHidHao40lanf6cuMhem5XLPtyeKe9ITdyHrqwVF epN6NMxgb9rB68sorxKI1dyUNecJcSit3usGOEfAYy6acgdhWL2yUCYc20Rmog.sWAnsAyHP8Vnt jAJh5h8PvfR82k_UUniI2Vx_5tQdOd2DLQyOHBVLkt1zPPN.YgrTXFxXsl4pyStOBwNW.2v7ekU5 waZWpmS9OiC3ELzWNBBnJ4MI- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic303.consmr.mail.gq1.yahoo.com with HTTP; Wed, 27 Oct 2021 22:21:34 +0000 Received: by kubenode511.mail-prod1.omega.ne1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 3325a61143b91b65808fabae9aa1c10e; Wed, 27 Oct 2021 22:21:30 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable 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: git: 2f7f8995367b - main - libdialog: Bump shared library version to 10. [ the .so.10 is listed in mk/OptionalObsoleteFiles.inc ?] Message-Id: <1628B613-808D-4217-B7B9-FC649E42A81D@yahoo.com> Date: Wed, 27 Oct 2021 15:21:29 -0700 To: John Baldwin , freebsd-current X-Mailer: Apple Mail (2.3654.120.0.1.13) References: <1628B613-808D-4217-B7B9-FC649E42A81D.ref@yahoo.com> X-Rspamd-Queue-Id: 4HfjpZ0vnFz4sTG X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=VjyfcinF; dmarc=pass (policy=reject) header.from=yahoo.com; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.64.206 as permitted sender) smtp.mailfrom=marklmi@yahoo.com X-Spamd-Result: default: False [-3.50 / 15.00]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.64.206:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.64.206:from]; RCVD_COUNT_TWO(0.00)[2] Reply-To: marklmi@yahoo.com From: Mark Millard via freebsd-current X-Original-From: Mark Millard X-ThisMailContainsUnwantedMimeParts: N Unfortunately(?) this update added the .so.10 to = mk/OptionalObsoleteFiles.inc : diff --git a/tools/build/mk/OptionalObsoleteFiles.inc = b/tools/build/mk/OptionalObsoleteFiles.inc index a8b0329104c4..91822aac492a 100644 --- a/tools/build/mk/OptionalObsoleteFiles.inc +++ b/tools/build/mk/OptionalObsoleteFiles.inc _at__at_ -1663,11 +1663,11 _at__at_ OLD_FILES+=3Dusr/bin/dialog . . . OLD_FILES+=3Dusr/lib/libdialog.so -OLD_FILES+=3Dusr/lib/libdialog.so.8 +OLD_FILES+=3Dusr/lib/libdialog.so.10 . . . Looks to my like that +line should have been: +OLD_FILES+=3Dusr/lib/libdialog.so.9 (presuming the original .so.8 was correct during .so.9 's time frame). =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From nobody Wed Oct 27 22:23:22 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 63312182FDEE for ; Wed, 27 Oct 2021 22:23:33 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic315-55.consmr.mail.gq1.yahoo.com (sonic315-55.consmr.mail.gq1.yahoo.com [98.137.65.31]) (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 4Hfjrh3D9Kz4ttN for ; Wed, 27 Oct 2021 22:23:32 +0000 (UTC) (envelope-from marklmi@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1635373405; bh=o8cRrASrRR+iivx97DZLxyKd03tfqiE6XdYB4k77CMs=; h=From:Subject:Date:References:To:In-Reply-To:From:Subject:Reply-To; b=RPWphyVymzgOzYTHrz22oCeRUYwuAt74/SWyYvi+/67HGrzM+TGkE1hAedqXfm0VJ2ZC91lDFwZeU7u6uoNxacNRgr02JjigzpSFgaA2RjO5OYz7behN+om8e+CnyoZnj4JTLMEYCqV3tJFOZ0a93E9RUXGF64bgvN9KFSo8qpiYhCcMxJXhIYZhbcXHu/NhF2L9NY6ug5pR1HO1U0ILVokkStWqlQcP6h0TXJ3KjsGvxG+sWN3XiqpfWRs+Kxgjn7a1r9AnCgceWMWxeySS0YBQI+/dyI2SY/pXkyB9fCY5xuBpelQYy0TBUDmXhaGWMs3RFa9DmIQ8pr0Fw0athQ== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1635373405; bh=iOQAjYciR6bZ4Mnqirx2GVQ8HCYOO/lhjxYqiSwOnPx=; h=X-Sonic-MF:From:Subject:Date:To:From:Subject; b=ar32kGDvYIEU8TD65UKUfLRMKfIOx2Pbw5uiFjBOo7muhB1dQ3ciFxs0SqFArV+acWYrWqv1fEQyJjPL2VriDtY76U603oDJACBvAZ+G8Gdm01+quZhmm7tlExpFZ9SLrH3OaiNhwMww+x3WZlVeEMvxqi2R9NBYb654n7dFx6W4XAq4DIFYBFynkGwtgwoLApRSXi2d/xPtkiEcVq/9LFGa8XSrGn6TiYfqsdo9mn9IUxvsOx1wL7lHQVBGoWyxU5V0MzVh4f4HvdYT2tO/eV1YoF9fHXdatiB2NAnOwXQ6cuHYYPRF+6moyE5+NXk6UnN40X5ALQrUXTetPUJn6Q== X-YMail-OSG: wgp0cYMVM1mE7hv6Lc4hq12bOV0xK914Kbvy2eEU_b0UZGAHubsICnlKRr2m0Ev YJoSVwtjEK9cTRBPsCJn759SpKFj8noIA8Z4NMDf2mRkNBu3qAdO1N1YTCRsqjKAQTLu88lC5H5p a37CRfzMszUifnLQ2piHMj98oru5MPT6lb77afzJ_m8cwOAyb2XJjcToolpWB6yDoRVmIrmzULUX KiGeSsut77crx40z1KIjLEiqAmK1ZME_HbfUeglHZcAdDE4rw7Yf4H5kZaVKgYcabiWA50xnRzbg S1_DXmq5jE8LAqNXoFTO1SSqPkSgpyW0sGekYbG9yxUfwGesyWVXABCT4rWqS5nnd447Qo67HjUB 1y_SBwlIc8FB7mVyIxmeRJqWAW5xaP2qa2LfLxXNfhIvzXuIQqwecismN.OE1SxEMyGRtmCggumr qScLymrPjV.9Z_UT5lVfWKyMWpfQbkXfiEFeW9EH5gCDhNVDLfLwlrw2TrjBYClJa58nhZ4hE_E7 uRiJUJ_atNBkOpns9N1ET9Tie9yH15pGocHlmSuW8J4qQJ0b45rRD27aP.OF6EjA71VJ4SdmnrVs dfX14DclvAMwoDMh4r2f0bxSeFkcapirLjsjT2XqelvyE_mU48p99aAopUQxZHHCL9AyqYSL2AgL FylwL1trvZKsOtkzyUtlJucdilMyVTH7DpFBAMkHXI9UQ4WW8__5f0mc07pPCuoStLzohd8KDSM7 O1d6OhEFze8aet8qu.z0G.3TwtVNM8h1dfC15tsrMfxW0bYXSjchI60p6_PWo0o5W.IHMlCF3O9o Rsz2yAF2h9Nz5PVP_gaWz0PjnI.bpFsl2Izumk1scSP.u8Kg0TJ5VnJM.qV4n3pCWIqjnX3ncqzi RMyBzVmbPTcwMuojiWfKruGeFgAJCn0wP4mfFq4Pgbfqf5FWA2JD3etN.xlmYPCRSQoxbOCUEiey fzs_KCk0L53OARjuacTm9MJzsXo6XiQZK2KiqQVpbGjIa7m9XtBHg0mGgAS4u2yEhJb7JLdo3RK. b8TRDWWIzmc4fs21.sQgZc3.5ZPeWns6_JA_ey2YRB_ieWp3rF55nRObTarKlNX2QHMSd4JhOkML pR8LjXfcmN8Vu5FLv59I4yB0Q0YXlHRXiOLVPthQlj0eZasx.4yzwSh35gYr9gCotvG42GMqwUSQ 5nLP4Olm13Y1_k1esNcPjAk3zcM59mnsdBVn6iCB0Wk7TVjUGddTBOIUp8VXPdpnYgDpXJ0O5UNz gekwCyVN9ii02NxfRNnuIFsoMtK4NFP7Wj.QLI9kkh7FBKZDsGjVxxmhEq0fuAmw8MaPdyM6W6dt PR5m6UMwOO9ZPLi8lyZ304PwLnGwgcwhzrlH7m4TGIVaGooPjKZ3zlFu3yCkZhwl2DSSrpR3SBsv hWdbTrBdzEwDlPXi0ZNm0npuv1rRz1USqGaCFCav.0H2tZjggS0gifx_sZRZEnqEJX4k4nx6.Ij2 o5fWk9QUfa90wMYHHzYkADMpu5xCCQodIzku0hUSGhrEPmwH13inOWPG.PBeygmzUKYracER6bnA rzhP.jG45xyF6qArT6Mat1XNkZzyd8VcLvMve16oueK0E7jjdIpC.mzfv3hgY8BNepWm_GltbzMu NWVIXOTNHMWf_o6hZ40CWOnIl.qXDbpLMKgABkFwrSmWlemurtmpryb8DtBpqZSTNR2h3rM86uH0 FoC.h82iMMneXb0f8pqBHpeTmM9TGmZuanvOLG8Hgc7EwfiEyrkHGu283sHhSTYjmNoO6CuOKOi7 HcyKn_f.3gR6zjygm9ZEATIpMQg9fvFsKGpEfUZzYX3HLjYWD1BSqNjWN8ACuqsMAjP6fm8V6fSW YPhXNgsqBVObVk8iCmM13x4wyJZ8epk6ZuRjfthD2sm81G3yhz9hPqpfviOw750DVl1xaO_ASRVN B7FIYQ6d7GLsIaDViEJ7GiJ24MO7oCzwUC40j0LgLuUAzCP41MWj_oznTLOPOfcBjvFOcvfD3Byx RNpwhNt8Mis9moayu8MO3o8SVYNfhg46XbQK1s5HwegM72RU1Rm7uAMwtbPeWAKg.9q9J0ZJs8iE 4mA44wCQfjbbBcyUs4v8vrkiidrmA8iYGSMHndbFKBUX4RGK7YULtNNPcsNMDsn5BZujafghY.Ss SNGcm7Wotb6dwkIP9VoQYa_nLYhlVwQPI.2tBitp7ALdCCGhJb89LNT7Da_FxT45_xyMhakAdocn ldgIFZjd9uyvo7r3KxRcCPSBVsFXzgJbDVQ1PWcG8.sI- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.gq1.yahoo.com with HTTP; Wed, 27 Oct 2021 22:23:25 +0000 Received: by kubenode550.mail-prod1.omega.gq1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID f0697d1bf094d327394e179ce0c7bb4d; Wed, 27 Oct 2021 22:23:22 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable 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: git: 2f7f8995367b - main - libdialog: Bump shared library version to 10. [ the .so.10 is listed in mk/OptionalObsoleteFiles.inc ?] Date: Wed, 27 Oct 2021 15:23:22 -0700 References: <1628B613-808D-4217-B7B9-FC649E42A81D@yahoo.com> To: John Baldwin , freebsd-current In-Reply-To: <1628B613-808D-4217-B7B9-FC649E42A81D@yahoo.com> Message-Id: <18C5538D-74CF-460A-9809-BD025ED15A3D@yahoo.com> X-Mailer: Apple Mail (2.3654.120.0.1.13) X-Rspamd-Queue-Id: 4Hfjrh3D9Kz4ttN X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=RPWphyVy; dmarc=pass (policy=reject) header.from=yahoo.com; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.65.31 as permitted sender) smtp.mailfrom=marklmi@yahoo.com X-Spamd-Result: default: False [-3.50 / 15.00]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.65.31:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.65.31:from]; RCVD_COUNT_TWO(0.00)[2] Reply-To: marklmi@yahoo.com From: Mark Millard via freebsd-current X-Original-From: Mark Millard X-ThisMailContainsUnwantedMimeParts: N On 2021-Oct-27, at 15:21, Mark Millard wrote: > Unfortunately(?) this update added the .so.10 to = mk/OptionalObsoleteFiles.inc : >=20 > diff --git a/tools/build/mk/OptionalObsoleteFiles.inc = b/tools/build/mk/OptionalObsoleteFiles.inc > index a8b0329104c4..91822aac492a 100644 > --- a/tools/build/mk/OptionalObsoleteFiles.inc > +++ b/tools/build/mk/OptionalObsoleteFiles.inc > _at__at_ -1663,11 +1663,11 _at__at_ OLD_FILES+=3Dusr/bin/dialog > . . . > OLD_FILES+=3Dusr/lib/libdialog.so > -OLD_FILES+=3Dusr/lib/libdialog.so.8 > +OLD_FILES+=3Dusr/lib/libdialog.so.10 > . . . >=20 > Looks to my like that +line should have been: >=20 > +OLD_FILES+=3Dusr/lib/libdialog.so.9 >=20 > (presuming the original .so.8 was correct during > .so.9 's time frame). Looks like: +OLD_FILES+=3Dusr/lib/libdpv.so.3 is the same sort of issue and possibly should have been: +OLD_FILES+=3Dusr/lib/libdpv.so.2 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From nobody Wed Oct 27 23:58:45 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 38C531810736 for ; Wed, 27 Oct 2021 23:58:47 +0000 (UTC) (envelope-from jhb@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 4Hflyb15nbz3tyY; Wed, 27 Oct 2021 23:58:47 +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 B601A12C7; Wed, 27 Oct 2021 23:58:46 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Subject: Re: git: 2f7f8995367b - main - libdialog: Bump shared library version to 10. [ the .so.10 is listed in mk/OptionalObsoleteFiles.inc ?] To: marklmi@yahoo.com, freebsd-current References: <1628B613-808D-4217-B7B9-FC649E42A81D@yahoo.com> <18C5538D-74CF-460A-9809-BD025ED15A3D@yahoo.com> From: John Baldwin Message-ID: <3124d17b-42a0-3e40-2041-571f8fca4db6@FreeBSD.org> Date: Wed, 27 Oct 2021 16:58:45 -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: <18C5538D-74CF-460A-9809-BD025ED15A3D@yahoo.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: N On 10/27/21 3:23 PM, Mark Millard via freebsd-current wrote: > > > On 2021-Oct-27, at 15:21, Mark Millard wrote: > >> Unfortunately(?) this update added the .so.10 to mk/OptionalObsoleteFiles.inc : >> >> diff --git a/tools/build/mk/OptionalObsoleteFiles.inc b/tools/build/mk/OptionalObsoleteFiles.inc >> index a8b0329104c4..91822aac492a 100644 >> --- a/tools/build/mk/OptionalObsoleteFiles.inc >> +++ b/tools/build/mk/OptionalObsoleteFiles.inc >> _at__at_ -1663,11 +1663,11 _at__at_ OLD_FILES+=usr/bin/dialog >> . . . >> OLD_FILES+=usr/lib/libdialog.so >> -OLD_FILES+=usr/lib/libdialog.so.8 >> +OLD_FILES+=usr/lib/libdialog.so.10 >> . . . >> >> Looks to my like that +line should have been: >> >> +OLD_FILES+=usr/lib/libdialog.so.9 >> >> (presuming the original .so.8 was correct during >> .so.9 's time frame). > > > Looks like: > > +OLD_FILES+=usr/lib/libdpv.so.3 > > is the same sort of issue and possibly should have been: > > +OLD_FILES+=usr/lib/libdpv.so.2 No, these lines are for removing the current versions of the libraries if you do 'make delete-old WITHOUT_DIALOG=yes'. They weren't bumped previously when I bumped them for ncurses (probably my fault). -- John Baldwin From nobody Thu Oct 28 02:47:19 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 167A51812A10 for ; Thu, 28 Oct 2021 02:47:30 +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 4HfqjF0vKfz3q5P; Thu, 28 Oct 2021 02:47:28 +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 19S2lKEQ097629; Wed, 27 Oct 2021 19:47:20 -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 19S2lJF9097628; Wed, 27 Oct 2021 19:47:19 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <202110280247.19S2lJF9097628@gndrsh.dnsmgr.net> Subject: Re: Future of ident(1) In-Reply-To: To: Maxim Sobolev Date: Wed, 27 Oct 2021 19:47:19 -0700 (PDT) CC: Steve Kargl , freebsd-current@FreeBSD.org 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: 4HfqjF0vKfz3q5P X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-rwg@gndrsh.dnsmgr.net has no SPF policy when checking 69.59.192.140) smtp.mailfrom=freebsd-rwg@gndrsh.dnsmgr.net X-Spamd-Result: default: False [-0.31 / 15.00]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_SHORT(0.79)[0.786]; TO_MATCH_ENVRCPT_SOME(0.00)[]; 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:13868, ipnet:69.59.192.0/19, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Has anyone considered that ident(1) works on all the binaries produced by FreeBSD for the first 25 years it existed? Ie, you can run ident on a FreeBSD 1.0 binary... I also believe it can be run on binaries from many other systems. So though we have lost the data in FreeBSD 14, the other data still exists, and though some might call this obscure, others of us find this data pricessless in figuring out from which a binary was made. Regards, Rod > Just in case someone thinks this is something useful, I've got a PR filed > against git to implement custom $Id$. There are no technical issues with > the change but Git developers are not very keen on merging it in, since > they see this as an obscure feature, no one needs. :-/ So if anyone wants > to chime in on GitHub or git mailing list please do so. > > https://github.com/git/git/pull/1074 > > Thanks! > > -Max > > On Fri, Oct 22, 2021 at 2:30 PM Steve Kargl < > sgk@troutmask.apl.washington.edu> wrote: > > > All, > > > > With the new world order, what is the future of ident(1)? > > Should it be removed from base? Given a compiled binary > > in base, how does one find the equivalent git info that > > ident(1) used to perform? > > > > Having a few minutes to dust off old patchs for libm, should > > I remove $FreeBSD$ tags in files I touch? For new files, is > > it expected that useless $FreeBSD$ tags should be added? > > > > -- > > Steve > > > > -- Rod Grimes rgrimes@freebsd.org From nobody Thu Oct 28 14:44: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 6F6EA1819999; Thu, 28 Oct 2021 14:45:18 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f46.google.com (mail-io1-f46.google.com [209.85.166.46]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Hg7dT47qcz3kqT; Thu, 28 Oct 2021 14:45:17 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io1-f46.google.com with SMTP id d63so8443708iof.4; Thu, 28 Oct 2021 07:45:17 -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:from:date:message-id:subject:to; bh=zfpPey5TjcpLI+WDp1UlCDbBe50UA4QULCo25k6u6UM=; b=2GGfr4dKUp464nYckWMpVq1BJ1lnvGBDk7XAAIXTX5qokIHmM+CBOc18XGNOEWtw7/ S9BQCR6PLs8mZmxYjIYUWMx7XJRtHItxDvEha+1Wo7336QMw/H46RpQIssuodRn4BcvZ 694TcFrg4K/KPapENpLqeInTN0jcaBWmdr/i8RCfS44tkMKvVEXSnGbZtIUQ1YGmSZdp Z5NG99QL4jkb6Rf4Q60BAvRuYlciBtepg0CB3MzCRlqjEbiIOD/BckTJ7yhri54NapOU ta+GLkL/BeMtHoOEgoCZWH+JxW03m6k9RRIxtfA5MWg3n5RJAoUC8l81vZjjFzlVXTtU VbAA== X-Gm-Message-State: AOAM532r9UxutFSNEqoyGRnImtlltVGJkZa6dZ/8lp7Me28l7/dXhqJE raoR8k+h1Vy+x6XwKppr9ByJduq+D4i8mK7Njf9R/8hpDsk= X-Google-Smtp-Source: ABdhPJwtFj/iwJ8hZQoyItxZpg5b8I11qGVp+TMZN0gWT8ssfAIqvuQs1cJEQZazEhAT/dD/9RTtjTasSuPIkfFMlII= X-Received: by 2002:a05:6638:1311:: with SMTP id r17mr1607142jad.76.1635432311105; Thu, 28 Oct 2021 07:45:11 -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 From: Ed Maste Date: Thu, 28 Oct 2021 10:44:56 -0400 Message-ID: Subject: Deprecating smbfs(5) and removing it before FreeBSD 14 To: FreeBSD Current , freebsd-stable stable Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4Hg7dT47qcz3kqT X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.46 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-1.26 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[carpeddiem]; 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]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_SPAM_SHORT(0.68)[0.678]; NEURAL_HAM_MEDIUM(-0.94)[-0.938]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[209.85.166.46:from]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.166.46: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)[emaste@freebsd.org,carpeddiem@gmail.com]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N The smbfs(5) filesystem supports only the obsolete SMBv1 protocol, and I propose removing it for FreeBSD 14. I know the CHERI folks have been using it but they plan to migrate away from it. It was broken for months before they fixed it, so I suspect nobody is using it on contemporary releases. I have review D32707 (https://reviews.freebsd.org/D32707) open to add this deprecation notice to the man page: The smbfs filesystem driver supports only the obsolete SMBv1 protocol. smbfs and userspace counterparts smbutil(1) and mount_smbfs(8) are not present in FreeBSD 14 and above. Users are advised to evaluate the sysutils/fusefs-smbnetfs port instead. A similar notice would be added to the smbutil and mount_smbfs man pages, and manu@ suggested having the userland utilities emit a warning when they are used. I am interested in comments, objections, or reports that anyone is in fact using smbfs. From nobody Thu Oct 28 15:26:42 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 39E9B182BFF7 for ; Thu, 28 Oct 2021 15:26:44 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Hg8YJ0pwHz4VNb for ; Thu, 28 Oct 2021 15:26:44 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-qt1-x82d.google.com with SMTP id c28so6030316qtv.11 for ; Thu, 28 Oct 2021 08:26:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=gPS3xPMGEVxYoF0zKCE1MuXrrGeEl5ey8sqot95Cxcs=; b=TpiVFZvpsZgBqrUhG5G3ZP1nBvDsjbGiEADg6Ib1x500vYTb1lycuC0ShqEeSlSE8C GYhmxy9o58IuMkRSYWtUKCWzAsjS5G5f+fe4sQ6vVu/eWQSNtdZwpbsXDeiH0aYVPnxJ oEytLsq69xs0iDAds0FqozePg0adPvGjVaymNGtctl14pfebtXQZye4NUWYWrh7eXoQu FbCf1pWO+GLSzOaaaueOfmD2GwL7vU6E/Xw+YXsk1R37RuCpWeT1BQOwUnh3BNqwZL/N VEOacjLVBVj3mwgChLvKKU4HJTs/5Oz0gdiClsPYUXftmCtH8hl8Q5+rwbpxsdmuw6Gs I5CQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=gPS3xPMGEVxYoF0zKCE1MuXrrGeEl5ey8sqot95Cxcs=; b=eL7Uev+r/sztaC0WwVI4Dn/bTq3Uj6ol1irG3j8PJhagAa5nSW4uYvVygRCYPfecyQ 1iMRjpvlwc8ibY4/SISLUuGktmm0jHk/Ng60dR/Sb31QAbyUYppeubce8ZteOZGZcMJ+ 8izuqjlFcTvhvv6KV3MsC4YJg1yXr/FUvUL/MsLr05unJnQeGEU31S4TC7D5iy/n+SOG ZYAnE9h2fjD1LxMSjn8aOqmrjeUZgBftyIivm5URER2Ej1LFMVrGRjsgN6aEvJ2nPOE5 wny1g8f9R9kgs6x9F2QiWeutrW5JGo2Lt0l8pkZPhBvBbKttIkdW0jT5kHdDYBHwXk9X kVVw== X-Gm-Message-State: AOAM530PEPI0203DVaIjUGo8NEyNftinySEh5JtuIT9GO8xwnxFZ4ySB jUsMXZpL+NoOHNBeILJYT1J6waHgSiieKsQx X-Google-Smtp-Source: ABdhPJykr/ITrKvlrVSLzCzMQmKYdg1BWVYmPBgPL84KtZzI8v/spFxGLFBU7JQwbBoo90b3oRdJhg== X-Received: by 2002:ac8:5613:: with SMTP id 19mr5563986qtr.100.1635434803551; Thu, 28 Oct 2021 08:26:43 -0700 (PDT) Received: from mutt-hbsd (pool-100-16-224-136.bltmmd.fios.verizon.net. [100.16.224.136]) by smtp.gmail.com with ESMTPSA id y8sm2215073qko.36.2021.10.28.08.26.42 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 28 Oct 2021 08:26:43 -0700 (PDT) Date: Thu, 28 Oct 2021 11:26:42 -0400 From: Shawn Webb To: Ed Maste Cc: FreeBSD Current , freebsd-stable stable Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 Message-ID: <20211028152642.ejvwewkztewotln4@mutt-hbsd> X-Operating-System: FreeBSD mutt-hbsd 14.0-CURRENT-HBSD FreeBSD 14.0-CURRENT-HBSD X-PGP-Key: https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/blob/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc References: 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-sha256; protocol="application/pgp-signature"; boundary="brkcv3d7hvmd7n7w" Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4Hg8YJ0pwHz4VNb X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N --brkcv3d7hvmd7n7w Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 28, 2021 at 10:44:56AM -0400, Ed Maste wrote: > The smbfs(5) filesystem supports only the obsolete SMBv1 protocol, and > I propose removing it for FreeBSD 14. I know the CHERI folks have been > using it but they plan to migrate away from it. It was broken for > months before they fixed it, so I suspect nobody is using it on > contemporary releases. >=20 > I have review D32707 (https://reviews.freebsd.org/D32707) open to add > this deprecation notice to the man page: > The smbfs filesystem driver supports only the obsolete SMBv1 protoco= l. > smbfs and userspace counterparts smbutil(1) and mount_smbfs(8) are n= ot > present in FreeBSD 14 and above. Users are advised to evaluate the > sysutils/fusefs-smbnetfs port instead. >=20 > A similar notice would be added to the smbutil and mount_smbfs man > pages, and manu@ suggested having the userland utilities emit a > warning when they are used. >=20 > I am interested in comments, objections, or reports that anyone is in > fact using smbfs. >=20 It seems that smbfs might be used with some level of frequency in virtualized environments. I wonder if providing a 9pfs client would be a good step in helping deprecate smbfs. Thanks, --=20 Shawn Webb Cofounder / Security Engineer HardenedBSD https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A= 4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc --brkcv3d7hvmd7n7w Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEA6TL67gupaZ9nzhT/y5nonf44foFAmF6wTAACgkQ/y5nonf4 4fpoXw//Q04ZLd66de+3d5PpWib5YDiJrHexiDyqahYGhhWcj3fLl3sMdkNoQ46L GVtqo4yeh6qs4EnUSSvNkXk0bO7R3nvaMORUWk3zHnxh98V5mj/O7abxn4DSnXkH Lk2CwoGMozizWL8Ht+s1Xsppl3QeUc1QwaXIFwf6blsmjU/+Gzusg9nVoPuaOhQm lurbEzXZJg2akXaG3apJJcB9MKBLGZV3adjFJpnyCnOa8pP/xOmc4ipsAHAUGQ82 pwAj4OM68MN3uUH3lTirn2l8Bm4+EbQXF104yc3BErEP7qpPAu/kcMvqTfKMDd9m R8zwSbh6x9FsK/qczVpqKP0nwQt8Nb9a6cVpA4/Oo0+uSrZMjNBzbWlnAscz0tW0 x4/WWfniT8wt4qDUwl20muwH8cWQaqhvIPfxruYQuBLnxyPejcwAffEX4IfkC3D9 LPGszuAkfXm1+zTQc8SHjC34x5hgK89b4vnZV7yh//uj/onMOI6pKBeyxU9EEu2U gMD+oreHXD+6G+r09tQa1E24ish/4U8Ap9LnyE0898Tr/XzmIo385D7Rp3MsJZlS 31m3Mv7EdyCPTo0l2AGHYt+YRq9FvibSh4h3ZUVEZrkcpbYVTavDQiEUv+GGMirU bPkIcIzhzpEIdaxIRVdPnID0G073U1hI2ipDqvGHq9/vHtMVqFw= =9HE4 -----END PGP SIGNATURE----- --brkcv3d7hvmd7n7w-- From nobody Thu Oct 28 15:37:33 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 CEB291832A3C; Thu, 28 Oct 2021 15:37:46 +0000 (UTC) (envelope-from SRS0=oNTo=PQ=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Hg8p229Srz4c8F; Thu, 28 Oct 2021 15:37:46 +0000 (UTC) (envelope-from SRS0=oNTo=PQ=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 5010928417; Thu, 28 Oct 2021 17:37:38 +0200 (CEST) Received: from illbsd.quip.test (ip-78-45-215-131.net.upcbroadband.cz [78.45.215.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 708F728411; Thu, 28 Oct 2021 17:37:36 +0200 (CEST) Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 To: Ed Maste , FreeBSD Current , freebsd-stable stable References: From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <8d25d2f4-24e2-5b19-5c81-2fe12dc937b7@quip.cz> Date: Thu, 28 Oct 2021 17:37:33 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.10.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: 7bit X-Rspamd-Queue-Id: 4Hg8p229Srz4c8F 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 28/10/2021 16:44, Ed Maste wrote: > The smbfs(5) filesystem supports only the obsolete SMBv1 protocol, and > I propose removing it for FreeBSD 14. I know the CHERI folks have been > using it but they plan to migrate away from it. It was broken for > months before they fixed it, so I suspect nobody is using it on > contemporary releases. > > I have review D32707 (https://reviews.freebsd.org/D32707) open to add > this deprecation notice to the man page: > The smbfs filesystem driver supports only the obsolete SMBv1 protocol. > smbfs and userspace counterparts smbutil(1) and mount_smbfs(8) are not > present in FreeBSD 14 and above. Users are advised to evaluate the > sysutils/fusefs-smbnetfs port instead. > > A similar notice would be added to the smbutil and mount_smbfs man > pages, and manu@ suggested having the userland utilities emit a > warning when they are used. > > I am interested in comments, objections, or reports that anyone is in > fact using smbfs. I am working for one company where smbfs is heavily used to connect Windows / MacOS / Linux / FreeBSD (12.2) machines and we are really sad that FreeBSD's mount_smbfs does not support SMBv2 / SMBv3 protocols (so we are using SMBv1 with all the risk). I tried fusefs alternatives from the ports tree in the past but it never worked as is needed. From our point of view smbnetfs cannot replace mount_smbfs. I cannot found any good examples of how to configure it to mount about 20 shares from /etc/fstab on boot as user root from different hosts with different login, passwords and mount options to defined mount points. Everything seems to be very differently designed to work for non-root user with configuration in users home, not system wide and mounting in some strange hierarchy. (and bad performance was cited by many on other platforms too) It was discussed in the past in some other FreeBSD mailinglist that it is not so easy to implement SMBv2 in to mount_smbfs. But is there any possibility to make it as some sponsored work? What about FreeBSD Foundation? There were some paid projects in the past. Or some other bounty program. Is there anybody who have the skill to implement it if there is good amount of $? If I am "well informed" FreeBSD is the only widely used OS not supporting SMBv2. (MacOS, Linux, Solaris have it supported) I will be really glad "if somebody can fix it" in the base. (or at least document how to use smbnetfs the way mount_smbfs is used) Kind regards Miroslav Lachman From nobody Thu Oct 28 16:25:52 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 30A6B1829941; Thu, 28 Oct 2021 16:26:14 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f41.google.com (mail-io1-f41.google.com [209.85.166.41]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Hg9sx6Bdfz3CND; Thu, 28 Oct 2021 16:26:13 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io1-f41.google.com with SMTP id m184so8945552iof.1; Thu, 28 Oct 2021 09:26:13 -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=r5ZRlgox9oMC33IfcuWqruXKYidbGZ99/43wZj8Rqo0=; b=gYGzinSB4qYeY4c2r2JrA+djQD8IdLD1pBpGit56pE9uUO81OZupjFTyWyPlT3NPrP jl0bgYTK9EJEAIBpKssmPGrKaoO8mvVbk9roMb4Yb8jLvJuwiL2hK3JZaIhxZnRL+zfz J89ZmcbLxQl8ELDUn/0kCggdLWUpfOKMayzFM0+eue/I5ITZlYce0TMrkbxUfZ14uBWL ahEisPkJxyv92soJ9rdHK11QQGdBpFFBM2k7uzHp6emnT1sfPYVZkmF3Lv29+Hm7AhKW yT1dssqA7WCdY0rpjx9z6WITXnrqfzUGykA53189q+krcSOcBH+JL46b8AfbnwFzRZ+a O/tQ== X-Gm-Message-State: AOAM533278wYiQj2cNQwyzBz1sfif0ojkiKub1Zf21uas1abRWcs/Plh 8ONsWsk3ImW4P27JPkijQnb10hiJI4Lv+m8BhTlas9b61Yc= X-Google-Smtp-Source: ABdhPJwV9EXKWQpDDm2bJJ3pqVR2rt6S3SccvqOuvtJS5kvCJw+YWAV+bTdWUlXYhIlG51lpFgeuWH1FWOMypfYk3tU= X-Received: by 2002:a5d:9416:: with SMTP id v22mr3729483ion.96.1635438367414; Thu, 28 Oct 2021 09:26:07 -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: In-Reply-To: From: Ed Maste Date: Thu, 28 Oct 2021 12:25:52 -0400 Message-ID: Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 To: Eugene Grosbein Cc: FreeBSD Current , freebsd-stable stable Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4Hg9sx6Bdfz3CND 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 Thu, 28 Oct 2021 at 11:05, Eugene Grosbein wrote: > > Please do not remove what is not broken. That is exactly the problem though: it was broken. It was fixed only because the CHERI folks found that it wasn't working and fixed it, and they are not going to be using it much longer. If nobody else regularly tests it in -CURRENT it will break again, and will end up broken in a release. That said, since it does seem that several folks are still currently using i I'll avoid trying to remove it in the near future. A caveat for the man pages may instead be something like: The smbfs filesystem driver supports only the obsolete SMBv1 protocol. smbfs is unmaintained and may not function correctly in FreeBSD 14 or later. Users are advised to evaluate the sysutils/fusefs-smbnetfs port instead. From nobody Thu Oct 28 16:32: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 7FC22182C4DE; Thu, 28 Oct 2021 16:32:53 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-il1-f170.google.com (mail-il1-f170.google.com [209.85.166.170]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HgB1d39rvz3Grb; Thu, 28 Oct 2021 16:32:53 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-il1-f170.google.com with SMTP id s3so7627499ild.0; Thu, 28 Oct 2021 09:32:53 -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=cscR72H3Vrjj8pWvcZ1kHUDXVpYQeFA6RNMEwXj+hng=; b=sbOE4P8SVdXOjkbjP3Epf4AB5w4fr3aatuSUNSSIG4dnfm6AhSrhedaE+Ly9R9dBjO HvKx639JdQNSJ4C+GtEgPOQpQgvxe7+fsuZQTgJZ3GszbYI46+8/jWhtDVJaShGGsWLN VjinLaO+E+GoDUZHvA3BlOX5+GXbsTSSgLzeNC+wOivlLqnGI/bc5s/1v5sRCPZhLSZs C/1fIQwL8c6e021yRPps2/wVUHbW5Nff9igssknO+h5oDnfApT3MC+CWByXrwGFlzydg S+5ljsTSZ8u36ZJJ1nV85j108t+4rN16VkXw8dF01xQ77eBm3jNBmozWZJSJCfRd+2TL qKQQ== X-Gm-Message-State: AOAM533fn2xNAsSsZFHJWu+GCMxGIL1KnJuqgi5tt61tGv8B+gZ072Os 0saLAkQpgKzHMWsozXAGAXMG+5Q7Yl1coSqcmlSlL4Do X-Google-Smtp-Source: ABdhPJwLSc0AauL4O6NDI5LyWPnZ8ISytbuPIuezZdJ4SNLpTL1vtSzuK9ANWs9UsHqXlbgNWmDl3lm8NuLfifI/gGM= X-Received: by 2002:a92:d7c3:: with SMTP id g3mr3865072ilq.35.1635438767292; Thu, 28 Oct 2021 09:32:47 -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: <20211028152642.ejvwewkztewotln4@mutt-hbsd> In-Reply-To: <20211028152642.ejvwewkztewotln4@mutt-hbsd> From: Ed Maste Date: Thu, 28 Oct 2021 12:32:31 -0400 Message-ID: Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 To: Shawn Webb Cc: FreeBSD Current , freebsd-stable stable Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4HgB1d39rvz3Grb 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 Thu, 28 Oct 2021 at 11:26, Shawn Webb wrote: > > It seems that smbfs might be used with some level of frequency in > virtualized environments. I wonder if providing a 9pfs client would be > a good step in helping deprecate smbfs. Indeed, that addresses one of the primary reasons it is still being used, including by CHERI. Their plan to migrate away from smbfs is based on moving to 9pfs. From nobody Thu Oct 28 17:22:00 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 9BC971819176; Thu, 28 Oct 2021 17:22:28 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: from mail-lj1-f172.google.com (mail-lj1-f172.google.com [209.85.208.172]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HgC6r3Wsdz3nSj; Thu, 28 Oct 2021 17:22:28 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: by mail-lj1-f172.google.com with SMTP id 17so8811245ljq.0; Thu, 28 Oct 2021 10:22:28 -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=heYUqypMGQ1rKmpGipzpGq6k1yYodmntY/C6BinHDts=; b=zYBCeRoOLGL8/x0/iXWgurI6j+kwDElo3pe0aGWzbMc6SPXmP+x4rizPBEujTqYfcW SqZTJVkSlWzOR2uJ8PWFU2RoryahsMs9jHAkfBa8kzhruAooknpDIqQ/bU1s3Xj/AgBz 0oii/9Y9iAVxkoytlEcU1TEd0W78FtiwqRThCpBMH4igZrkTpkfjk0f00OZyNQ+PBM9Z JD5wUvueAyDVTBeDujw5XwbHkjMOBnfv8PFRIKJCx/6DlJIFz0lnPNoMd8RKnoPGkpeY YAjaTpiObSgbFSJjna6i8OkwCK4Mkdz1wsGkPKfmweQAYHnnc6Hg154ZrdMsHNJCcVp3 7SdA== X-Gm-Message-State: AOAM531izvfikdcAWEXZQP1vfLqF5UZCZa7HjRZNh6G6cT3jwbzHTDsF VnLm3gbydaIv17klb/bizsWgfvtFzYY18Q== X-Google-Smtp-Source: ABdhPJyQLxhcTR90gr9EjYmTP+HB9Kzvtsz38OWWvI2gco7nXcGxHApjkLocJIIi7+q0njc0CnU4sw== X-Received: by 2002:a2e:81cb:: with SMTP id s11mr5996490ljg.222.1635441746990; Thu, 28 Oct 2021 10:22:26 -0700 (PDT) Received: from mail-lj1-f170.google.com (mail-lj1-f170.google.com. [209.85.208.170]) by smtp.gmail.com with ESMTPSA id h4sm368811lft.184.2021.10.28.10.22.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 28 Oct 2021 10:22:26 -0700 (PDT) Received: by mail-lj1-f170.google.com with SMTP id 1so6044539ljv.2; Thu, 28 Oct 2021 10:22:26 -0700 (PDT) X-Received: by 2002:a2e:a554:: with SMTP id e20mr6189528ljn.500.1635441746690; Thu, 28 Oct 2021 10:22:26 -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: <8d25d2f4-24e2-5b19-5c81-2fe12dc937b7@quip.cz> In-Reply-To: <8d25d2f4-24e2-5b19-5c81-2fe12dc937b7@quip.cz> From: Gleb Popov Date: Thu, 28 Oct 2021 20:22:00 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 To: Miroslav Lachman <000.fbsd@quip.cz> Cc: FreeBSD Current , freebsd-stable stable Content-Type: multipart/alternative; boundary="0000000000005cc94d05cf6cf465" X-Rspamd-Queue-Id: 4HgC6r3Wsdz3nSj X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --0000000000005cc94d05cf6cf465 Content-Type: text/plain; charset="UTF-8" On Thu, Oct 28, 2021 at 6:39 PM Miroslav Lachman <000.fbsd@quip.cz> wrote: > I am working for one company where smbfs is heavily used to connect > Windows / MacOS / Linux / FreeBSD (12.2) machines and we are really sad > that FreeBSD's mount_smbfs does not support SMBv2 / SMBv3 protocols (so > we are using SMBv1 with all the risk). I tried fusefs alternatives from > the ports tree in the past but it never worked as is needed. From our > point of view smbnetfs cannot replace mount_smbfs. > I cannot found any good examples of how to configure it to mount about > 20 shares from /etc/fstab on boot as user root from different hosts with > different login, passwords and mount options to defined mount points. > Everything seems to be very differently designed to work for non-root > user with configuration in users home, not system wide and mounting in > some strange hierarchy. (and bad performance was cited by many on other > platforms too) > It was discussed in the past in some other FreeBSD mailinglist that it > is not so easy to implement SMBv2 in to mount_smbfs. But is there any > possibility to make it as some sponsored work? What about FreeBSD > Foundation? There were some paid projects in the past. Or some other > bounty program. Is there anybody who have the skill to implement it if > there is good amount of $? > > If I am "well informed" FreeBSD is the only widely used OS not > supporting SMBv2. (MacOS, Linux, Solaris have it supported) > I will be really glad "if somebody can fix it" in the base. > > (or at least document how to use smbnetfs the way mount_smbfs is used) > > Kind regards > Miroslav Lachman > > I'm also aware of a local company that actively uses smbfs. Removing it would probably cause them to switch to Linux, which is a pity. --0000000000005cc94d05cf6cf465-- From nobody Thu Oct 28 19:33: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 A09991834027; Thu, 28 Oct 2021 19:33:22 +0000 (UTC) (envelope-from SRS0=oNTo=PQ=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4HgG1t3MTVz3JyD; Thu, 28 Oct 2021 19:33:22 +0000 (UTC) (envelope-from SRS0=oNTo=PQ=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 7B4D928411; Thu, 28 Oct 2021 21:33:20 +0200 (CEST) Received: from illbsd.quip.test (ip-78-45-215-131.net.upcbroadband.cz [78.45.215.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 20A0A28417; Thu, 28 Oct 2021 21:33:18 +0200 (CEST) Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 To: Ed Maste , Eugene Grosbein Cc: FreeBSD Current , freebsd-stable stable References: From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: Date: Thu, 28 Oct 2021 21:33:18 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.10.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: 7bit X-Rspamd-Queue-Id: 4HgG1t3MTVz3JyD 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 28/10/2021 18:25, Ed Maste wrote: > On Thu, 28 Oct 2021 at 11:05, Eugene Grosbein wrote: >> >> Please do not remove what is not broken. > > That is exactly the problem though: it was broken. It was fixed only > because the CHERI folks found that it wasn't working and fixed it, and > they are not going to be using it much longer. If nobody else > regularly tests it in -CURRENT it will break again, and will end up > broken in a release. Can this problem be covered by some automated tests to catch it sooner - before release? > That said, since it does seem that several folks > are still currently using i I'll avoid trying to remove it in the near > future. > > A caveat for the man pages may instead be something like: > > The smbfs filesystem driver supports only the obsolete SMBv1 protocol. > smbfs is unmaintained and may not function correctly in FreeBSD 14 or > later. Users are advised to evaluate the sysutils/fusefs-smbnetfs port > instead. Kind regards Miroslav Lachman From nobody Thu Oct 28 20:49:14 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 7FB871832A29; Thu, 28 Oct 2021 20:49:21 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (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 4HgHjY32Q4z3vP3; Thu, 28 Oct 2021 20:49:21 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id E7A363C0199; Thu, 28 Oct 2021 20:49:14 +0000 (UTC) Date: Thu, 28 Oct 2021 20:49:14 +0000 From: Brooks Davis To: Miroslav Lachman <000.fbsd@quip.cz> Cc: Ed Maste , Eugene Grosbein , FreeBSD Current , freebsd-stable stable Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 Message-ID: <20211028204914.GC81740@spindle.one-eyed-alien.net> References: 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-sha1; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-Rspamd-Queue-Id: 4HgHjY32Q4z3vP3 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 28, 2021 at 09:33:18PM +0200, Miroslav Lachman wrote: > On 28/10/2021 18:25, Ed Maste wrote: > > On Thu, 28 Oct 2021 at 11:05, Eugene Grosbein wrot= e: > >> > >> Please do not remove what is not broken. > >=20 > > That is exactly the problem though: it was broken. It was fixed only > > because the CHERI folks found that it wasn't working and fixed it, and > > they are not going to be using it much longer. If nobody else > > regularly tests it in -CURRENT it will break again, and will end up > > broken in a release. >=20 > Can this problem be covered by some automated tests to catch it sooner -= =20 > before release? FWIW, any testing at all would have caught this. It paniced on unmount in a kernel with INVARIANTS. The awkward thing about testing it is that it requires a server. We'd have caught it sooner if we hadn't had a major stall in merging FreeBSD head to CheriBSD. We're hoping to stop using it because it's slow, server support will eventually go away, etc. We don't really have an opinion about it staying or going. -- Brooks --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJhewzKAAoJEKzQXbSebgfARbEH/iI3XIthG+cIYUq6XtOd25r0 XvJQ6fjnbXZElLI/BDLTXe4gND04RCla/YtmJPPip0ykjTr7rsGzouLdLzXy2Gvz ojyUTH2ubq8bHniD9vefGpqWheYwBmewTedoN1vpleXIcGQyGsjouMB7M04ZEKsB FgHlKgCbo+zlUiKFUYqVImmh22zKHV7UzVkeZOg7BTvFY3WBQVYtDJArxwwgubJZ z9MasqxngVQ69Jk+4lIKmNESEr+0ixaOs2LhHFJqRrDxWZcRnf0ZZzYBLiYOvyZm Aoia3PZK0ZdUSJTbxygEIZT+lFxONS95A3omB+JyyLJT8g88lDKgoOTxitOdTts= =NXlm -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o-- From nobody Thu Oct 28 22:28: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 D683918334E9 for ; Thu, 28 Oct 2021 22:28:58 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HgKwV02Wkz4sqb for ; Thu, 28 Oct 2021 22:28:57 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.16.1/8.16.1) with ESMTPS id 19SMSpiI024162 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Thu, 28 Oct 2021 15:28:51 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.16.1/8.16.1/Submit) id 19SMSpum024161 for freebsd-current@freebsd.org; Thu, 28 Oct 2021 15:28:51 -0700 (PDT) (envelope-from sgk) Date: Thu, 28 Oct 2021 15:28:51 -0700 From: Steve Kargl To: freebsd-current@freebsd.org Subject: access to ld128 system Message-ID: <20211028222851.GA24101@troutmask.apl.washington.edu> 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 X-Rspamd-Queue-Id: 4HgKwV02Wkz4sqb X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=washington.edu (policy=none); spf=none (mx1.freebsd.org: domain of sgk@troutmask.apl.washington.edu has no SPF policy when checking 128.95.76.21) smtp.mailfrom=sgk@troutmask.apl.washington.edu X-Spamd-Result: default: False [-1.00 / 15.00]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; 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)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_SPAM_SHORT(1.00)[1.000]; 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:73, ipnet:128.95.0.0/16, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[washington.edu : No valid SPF, No valid DKIM,none] X-ThisMailContainsUnwantedMimeParts: N kib@ recently committed my implementations of cospi[fl], sinpi[fl], and tanpi[fl]. These functions have been extensively tested for float, double, and long double where long double is the Intel 80-bit long double (e.g., msun/ld80/s_sinpil.c). The 128-bit versions of these routines have not been tested (e.g., msun/ld128/s_sinpil.c) kib pointed me to a system in the FreeBSD, which I have access to. Unfortunately, that system has double == long double, and can only test the support for the weak references. Is there a system with 128-bit long double that I can have access for some testing? -- Steve From nobody Thu Oct 28 22:47: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 73251181C78F; Thu, 28 Oct 2021 22:47:16 +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 4HgLKc07nZz3GGr; Thu, 28 Oct 2021 22:47: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 19SMl3es004849; Fri, 29 Oct 2021 07:47:04 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Fri, 29 Oct 2021 07:47:02 +0900 From: Tomoaki AOKI To: freebsd-stable@freebsd.org Cc: freebsd-current@freebsd.org, Miroslav Lachman <000.fbsd@quip.cz>, Ed Maste Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 Message-Id: <20211029074702.d69cba39a643f3f912f8ec81@dec.sakura.ne.jp> In-Reply-To: <8d25d2f4-24e2-5b19-5c81-2fe12dc937b7@quip.cz> References: <8d25d2f4-24e2-5b19-5c81-2fe12dc937b7@quip.cz> 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: 4HgLKc07nZz3GGr 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 Thu, 28 Oct 2021 17:37:33 +0200 Miroslav Lachman <000.fbsd@quip.cz> wrote: > On 28/10/2021 16:44, Ed Maste wrote: > > The smbfs(5) filesystem supports only the obsolete SMBv1 protocol, and > > I propose removing it for FreeBSD 14. I know the CHERI folks have been > > using it but they plan to migrate away from it. It was broken for > > months before they fixed it, so I suspect nobody is using it on > > contemporary releases. > > > > I have review D32707 (https://reviews.freebsd.org/D32707) open to add > > this deprecation notice to the man page: > > The smbfs filesystem driver supports only the obsolete SMBv1 protocol. > > smbfs and userspace counterparts smbutil(1) and mount_smbfs(8) are not > > present in FreeBSD 14 and above. Users are advised to evaluate the > > sysutils/fusefs-smbnetfs port instead. > > > > A similar notice would be added to the smbutil and mount_smbfs man > > pages, and manu@ suggested having the userland utilities emit a > > warning when they are used. > > > > I am interested in comments, objections, or reports that anyone is in > > fact using smbfs. > > I am working for one company where smbfs is heavily used to connect > Windows / MacOS / Linux / FreeBSD (12.2) machines and we are really sad > that FreeBSD's mount_smbfs does not support SMBv2 / SMBv3 protocols (so > we are using SMBv1 with all the risk). I tried fusefs alternatives from > the ports tree in the past but it never worked as is needed. From our > point of view smbnetfs cannot replace mount_smbfs. > I cannot found any good examples of how to configure it to mount about > 20 shares from /etc/fstab on boot as user root from different hosts with > different login, passwords and mount options to defined mount points. > Everything seems to be very differently designed to work for non-root > user with configuration in users home, not system wide and mounting in > some strange hierarchy. (and bad performance was cited by many on other > platforms too) I, as an end-user who need to access local NAS, tried it a few yearsago (when it once broken by struct sockbuf issue that I finally sent patch) and had concluded smbnetfs is unusable for me. Additionally, it was quite unstable ATM. Sudden forcible unmount and failing remount. If it worked as expected, I wouldn't have tried digging into and sent Bug 182963. BTW, current in-tree code is broken for me and mandated patch proposed on Bug 90815. There are 3 patches uploaded and I use second one for years. Third one worked, too when I tried, but not continually using. The first one would no longer applicable. > It was discussed in the past in some other FreeBSD mailinglist that it > is not so easy to implement SMBv2 in to mount_smbfs. But is there any > possibility to make it as some sponsored work? What about FreeBSD > Foundation? There were some paid projects in the past. Or some other > bounty program. Is there anybody who have the skill to implement it if > there is good amount of $? +1 for FreeBSD Foundation project. But possibly we need to delete current smbfs code from base and switch to ports (sysutils/*?) if it require some code having incompatible license for base. Anyway, please don't remove it unless usable alternative appears. > If I am "well informed" FreeBSD is the only widely used OS not > supporting SMBv2. (MacOS, Linux, Solaris have it supported) > I will be really glad "if somebody can fix it" in the base. > > (or at least document how to use smbnetfs the way mount_smbfs is used) > > Kind regards > Miroslav Lachman > -- Tomoaki AOKI From nobody Fri Oct 29 06:29:25 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 76177181F4FE for ; Fri, 29 Oct 2021 06:29:29 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.netfence.it (mailserver.netfence.it [78.134.96.152]) (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 "mailserver.netfence.it", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HgXZw2s5Lz4vFR for ; Fri, 29 Oct 2021 06:29:28 +0000 (UTC) (envelope-from ml@netfence.it) Received: from [10.1.2.18] (alamar.local.netfence.it [10.1.2.18]) (authenticated bits=0) by soth.netfence.it (8.17.1/8.16.1) with ESMTPSA id 19T6TPLg022060 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO) for ; Fri, 29 Oct 2021 08:29:25 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.netfence.it: Host alamar.local.netfence.it [10.1.2.18] claimed to be [10.1.2.18] Message-ID: <940c9341-6938-05a1-d0b3-f20f07f9d3de@netfence.it> Date: Fri, 29 Oct 2021 08:29:25 +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 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 Content-Language: en-US To: freebsd-current@freebsd.org References: <8d25d2f4-24e2-5b19-5c81-2fe12dc937b7@quip.cz> <20211029074702.d69cba39a643f3f912f8ec81@dec.sakura.ne.jp> From: Andrea Venturoli In-Reply-To: <20211029074702.d69cba39a643f3f912f8ec81@dec.sakura.ne.jp> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4HgXZw2s5Lz4vFR X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=netfence.it; spf=pass (mx1.freebsd.org: domain of ml@netfence.it designates 78.134.96.152 as permitted sender) smtp.mailfrom=ml@netfence.it X-Spamd-Result: default: False [-1.80 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(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:78.134.96.152]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_SPAM_SHORT(1.00)[1.000]; DMARC_POLICY_ALLOW(-0.50)[netfence.it,none]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:35612, ipnet:78.134.0.0/17, country:IT]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 10/29/21 00:47, Tomoaki AOKI wrote: > But possibly we need to delete current smbfs code from base and switch > to ports (sysutils/*?) if it require some code having incompatible > license for base. I normally favour ports over things in base. In this case, however, as I said before, I needed it several times in emergency while booting the install key as live media. If it's a port, it won't be there. Perhaps my use case is rare. Also, probably there are other tools that can do this. OTOH having a port is not in any way worse as having a broken piece of base. bye av. From nobody Fri Oct 29 10:59:40 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 7ED79182250B for ; Fri, 29 Oct 2021 10:59:45 +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 4HgfZn39bBz3P4V for ; Fri, 29 Oct 2021 10:59:45 +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 477D422FCE for ; Fri, 29 Oct 2021 10:59:45 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from [192.168.1.202] (host86-153-41-4.range86-153.btcentralplus.com [86.153.41.4]) by smtp.theravensnest.org (Postfix) with ESMTPSA id E0A3A2D350 for ; Fri, 29 Oct 2021 11:59:42 +0100 (BST) Message-ID: <157d6222-0a89-230d-8e54-ec0b785af6a3@FreeBSD.org> Date: Fri, 29 Oct 2021 11:59:40 +0100 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 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 Content-Language: en-GB To: freebsd-current@freebsd.org References: <20211028152642.ejvwewkztewotln4@mutt-hbsd> From: David Chisnall In-Reply-To: <20211028152642.ejvwewkztewotln4@mutt-hbsd> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: N On 28/10/2021 16:26, Shawn Webb wrote: > I wonder if providing a 9pfs client would be > a good step in helping deprecate smbfs. Note: WSL2 uses 9p-over-VMBus, but most of the Linux world is moving away from 9p-over-VirtIO to FUSE-over-VirtIO. This has a few big advantages: - The kernel already has solid FUSE support so this isn't a completely new code path. - FUSE is designed around POSIX filesystem semantics, 9p isn't and this mismatch causes problems in places. - FUSE filesystems can be exposed almost directly to the guest. For example, if you have a networked filesystem you can run the FUSE FS in an unprivileged userspace process and remove the entire host kernel storage stack from the attack surface for the guest. - FUSE allows exposing buffer cache pages. The FUSE-over-VirtIO mechanism makes it fairly easy to expose read-only root filesystem images to guests. The last point is especially important for container workloads where you may have hundreds of containers in lightweight VMs on a single node all using the same base layer. David From nobody Fri Oct 29 15:27: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 C13D7181B755 for ; Fri, 29 Oct 2021 15:27:34 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HgmWp4fMFz3KvD for ; Fri, 29 Oct 2021 15:27:34 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-io1-xd32.google.com with SMTP id g8so11666993iob.10 for ; Fri, 29 Oct 2021 08:27:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=yLrSCfndzw6iL8fIz0Vz+7b1zPlbw2di7kmyVEOrQO0=; b=VqXiuUrC4RhC5pSqOMuQlIYpXrFEts7K4eZPYTdn8cwKrs5ysZ/ilEKv5E76mYTT0z b1/zQwFhoFzHHx0MQNM0VYgBKbxivjYtw7ZvLwxhDI41Zi6M1kUuTjxaO5vLY4J5psVV cJTmy1jp2BZkKvpDVg98YHdOsjn/RCq9BUfty/5DYDFvoOE4kf/UfO+uX/ZsCeQ4cRLK 2/mMWzz+u+ckrPmf0eg9WlEVi9DxZE06/WR2hROQ8AUor90yEyMQbAA5OTg+N+2pVg3t P2cqqKK/T1SYSm9/wW8gMgMb8GaakmV24u2bagoFz5BwUXcnzgAQ8XvfG2ZjnXhhQ5nr 9giw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=yLrSCfndzw6iL8fIz0Vz+7b1zPlbw2di7kmyVEOrQO0=; b=UeodlpJTjA5Ejj6lj0LWaZiNiak5sh+JFXZa8kzOExOz6GBsGELX+vWG+T6cTAlZUF qiBYLPE9EDLxDGgzEK4jrccOBfzQ0b4b2VkBthPqQQToXV/m/rvgPw16ERtMOZ0TtXkD 8hQmb49PV4EoRrVSKCEoZ9VEvKo723AWjny6j5k+9aqwwJZVwDmtDYXdlucdB9+0148S 5qwvQnLRZr9TQIHUzRNUVZBQy3aJctXOEX7HbvlnJXwa8VCWeX0U/bJa4rUd2OJ/JniL nBqNSel94qGnlzlo/4Rt+wt8yxh6vcCFWvVCRSX/rrth9EG1Qa2Qtz2Aua62tu1zN47U MKvA== X-Gm-Message-State: AOAM531O3GAznavfpXjwye0b5h9wf0F79xrA5AoYhRuibjy49mtrlq4W RiL54qqwHYDMBPQtutBQTSakvQIqkmvqcfnU X-Google-Smtp-Source: ABdhPJwaNJZ3bhRx+Gbl53AU72ttrHliF2mRNVLpTcwutPghRZS/ca0y9xm06rkKdmk44LubMDWhzQ== X-Received: by 2002:a05:6602:342a:: with SMTP id n42mr8431906ioz.136.1635521248423; Fri, 29 Oct 2021 08:27:28 -0700 (PDT) Received: from mutt-hbsd ([38.140.209.220]) by smtp.gmail.com with ESMTPSA id r14sm2625795iov.14.2021.10.29.08.27.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 29 Oct 2021 08:27:27 -0700 (PDT) Date: Fri, 29 Oct 2021 11:27:27 -0400 From: Shawn Webb To: David Chisnall Cc: freebsd-current@freebsd.org Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 Message-ID: <20211029152727.z2spglz42epu3ftm@mutt-hbsd> X-Operating-System: FreeBSD mutt-hbsd 14.0-CURRENT-HBSD FreeBSD 14.0-CURRENT-HBSD X-PGP-Key: https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/blob/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc References: <20211028152642.ejvwewkztewotln4@mutt-hbsd> <157d6222-0a89-230d-8e54-ec0b785af6a3@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: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="4z55ztnv2sz7wolt" Content-Disposition: inline In-Reply-To: <157d6222-0a89-230d-8e54-ec0b785af6a3@FreeBSD.org> X-Rspamd-Queue-Id: 4HgmWp4fMFz3KvD X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N --4z55ztnv2sz7wolt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 29, 2021 at 11:59:40AM +0100, David Chisnall wrote: > On 28/10/2021 16:26, Shawn Webb wrote: > > I wonder if providing a 9pfs client would be > > a good step in helping deprecate smbfs. >=20 > Note: WSL2 uses 9p-over-VMBus, but most of the Linux world is moving away > from 9p-over-VirtIO to FUSE-over-VirtIO. This has a few big advantages: >=20 > - The kernel already has solid FUSE support so this isn't a completely n= ew > code path. >=20 > - FUSE is designed around POSIX filesystem semantics, 9p isn't and this > mismatch causes problems in places. >=20 > - FUSE filesystems can be exposed almost directly to the guest. For > example, if you have a networked filesystem you can run the FUSE FS in an > unprivileged userspace process and remove the entire host kernel storage > stack from the attack surface for the guest. >=20 > - FUSE allows exposing buffer cache pages. The FUSE-over-VirtIO mechani= sm > makes it fairly easy to expose read-only root filesystem images to guests. >=20 > The last point is especially important for container workloads where you = may > have hundreds of containers in lightweight VMs on a single node all using > the same base layer. That's really cool. I hadn't heard about FUSE-over-VirtIO before. Thanks for the info! --=20 Shawn Webb Cofounder / Security Engineer HardenedBSD https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A= 4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc --4z55ztnv2sz7wolt Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEA6TL67gupaZ9nzhT/y5nonf44foFAmF8Et0ACgkQ/y5nonf4 4fqmZg/9GFPjdFgnYtr5jS0dvtsTTDdCSg53ZibB+5FGN0+kcixMWn59yeKjZ+uu gho1XaXPeggyirJOGlF8nvvLepBXMvfYWrzEgHhWjNWRygvlDa8ljFwJcrr/D4VM m7ngg4bKGcQwQJ1A65XEVmTBBEPQbOxFE/2aUpHIZYX+K2/a+CGHQ4lJk0jVXJyF cpIS5n6/u9ZNxjF3T9ASOgRoRbodj1sVIRUiP/bcNVMAE8FzFh2poCW3OJI1wTdm F2nSFofwqGaRUg53x66T0ZmI256pE/5hRrHZS48S7YqSHfh8IifA13SORZPkZcq6 xOePWNwaEUZNR9+PpCLEnKDbaGt3vx/e472Wac285iIf2Skwl744aioRkLQlhHau QaPe0/WMGomfoAhDwPVyFBO28rxILAAtm6tQr8GYQA1q32L6dG8B/m0n0ZYo+dzK vgNwN5RNC6roI88NhZt3ppMjZ9+BVguJN/7wk5sfGeaRGnnAl3ocerZFAl/HrPcH sqOjHziOIewPaQxNW6x0iCS/u3iA8of7ubYm/PRXhmYg6xQ/aE8YG7FZmLwq7KnZ 57DFRA12BkxoMfoS7Dp3KGz++RkKKrrxTobfBAF6i5CPBEn5x38rITBfmxyeq/GZ 2ShHqTvnjwmR/0x0XMCc+1kV+0YKtYUuv0+uSqu6dMLYUdrfDiY= =wzY0 -----END PGP SIGNATURE----- --4z55ztnv2sz7wolt-- From nobody Fri Oct 29 18:15:10 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 A6F90181A55D for ; Fri, 29 Oct 2021 18:15:17 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:300:2185:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4HgrFJ5PLKz4vfg for ; Fri, 29 Oct 2021 18:15:16 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [104.207.135.49]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 19TIFAGi072517 for ; Fri, 29 Oct 2021 19:15:10 +0100 (BST) (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 19TIFARt072516 for freebsd-current@freebsd.org; Fri, 29 Oct 2021 19:15:10 +0100 (BST) (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202110291815.19TIFARt072516@donotpassgo.dyslexicfish.net> Date: Fri, 29 Oct 2021 19:15:10 +0100 Organization: Dyslexic Fish To: freebsd-current@freebsd.org Subject: stat(1) isn't honouring locale User-Agent: Heirloom mailx 12.4 7/29/08 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-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [104.207.135.49]); Fri, 29 Oct 2021 19:15:10 +0100 (BST) X-Rspamd-Queue-Id: 4HgrFJ5PLKz4vfg X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=catflap.org; spf=pass (mx1.freebsd.org: domain of jamie@catflap.org designates 2001:19f0:300:2185:123::1 as permitted sender) smtp.mailfrom=jamie@catflap.org X-Spamd-Result: default: False [-3.70 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FREEFALL_USER(0.00)[jamie]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx:dyslexicfish.net]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; HAS_ORG_HEADER(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[catflap.org,none]; NEURAL_HAM_SHORT(-1.00)[-0.999]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:20473, ipnet:2001:19f0::/38, country:US] X-ThisMailContainsUnwantedMimeParts: N stat(1) isn't honouring locale. The manual page says: -t timefmt Display timestamps using the specified format. This format is passed directly to strftime(3). strftime(3) says: %+ is replaced by national representation of the date and time (the format is similar to that produced by date(1)). However: ----------------------------- % date Fri Oct 29 00:14:12 BST 2021 % date +%+ Fri Oct 29 00:14:19 BST 2021 % stat -t%+ -f '%Sm' . Fri Oct 29 00:13:38 BST 2021 ----------------------------- % setenv LANG en_GB.UTF-8 % date Fri 29 Oct 2021 00:14:57 BST % date +%+ Fri 29 Oct 2021 00:15:05 BST % stat -t%+ -f '%Sm' . Fri Oct 29 00:13:38 BST 2021 ----------------------------- Including and adding: (void) setlocale(LC_TIME, ""); before the call to strftime() in usr.bin/stat/stat.c fixes this Is there any reason this isn't in place? Cheers, Jamie From nobody Fri Oct 29 19:24:01 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 C2F781837823; Fri, 29 Oct 2021 19:24:09 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Hgsmm5sWpz3nh4; Fri, 29 Oct 2021 19:24:08 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id 19TJO1vx084225 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 29 Oct 2021 12:24:01 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id 19TJO1Es084224; Fri, 29 Oct 2021 12:24:01 -0700 (PDT) (envelope-from jmg) Date: Fri, 29 Oct 2021 12:24:01 -0700 From: John-Mark Gurney To: Ludovit Koren Cc: freebsd-current@freebsd.org, freebsd-net@freebsd.org Subject: Re: LAN ure interface problem Message-ID: <20211029192401.GN74427@funkthat.com> Mail-Followup-To: Ludovit Koren , freebsd-current@freebsd.org, freebsd-net@freebsd.org References: <86sfwt88il.fsf@gmail.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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86sfwt88il.fsf@gmail.com> X-Operating-System: FreeBSD 11.3-STABLE amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Fri, 29 Oct 2021 12:24:01 -0700 (PDT) X-Rspamd-Queue-Id: 4Hgsmm5sWpz3nh4 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of jmg@gold.funkthat.com has no SPF policy when checking 208.87.223.18) smtp.mailfrom=jmg@gold.funkthat.com X-Spamd-Result: default: False [0.20 / 15.00]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[jmg]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[funkthat.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_SHORT(1.00)[1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_TO(0.00)[gmail.com]; FORGED_SENDER(0.30)[jmg@funkthat.com,jmg@gold.funkthat.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:32354, ipnet:208.87.216.0/21, country:US]; FROM_NEQ_ENVFROM(0.00)[jmg@funkthat.com,jmg@gold.funkthat.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N Ludovit Koren wrote this message on Fri, Oct 22, 2021 at 16:00 +0200: > I have installed FreeBSD 14.0-CURRENT #1 main-n250134-225639e7db6-dirty > on my notebook HP EliteBook 830 G7 and I am using RealTek usb LAN > interface: > > ure0 on uhub0 > ure0: on usbus1 > miibus0: on ure0 > rgephy0: PHY 0 on miibus0 > rgephy0: OUI 0x00e04c, model 0x0000, rev. 0 > rgephy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, 1000baseT-FDX-master, auto > ue0: on ure0 > ue0: bpf attached > ue0: Ethernet address: 00:e0:4c:68:04:20 > > > When there is bigger load on the interface, for example rsync of the big > directory, the carrier is lost. The only solution I found is to remove > and insert the usb interface; ifconfig ue0 down, ifconfig ue0 up did not > help. The output of the ifconfig: > > ue0: flags=8843 metric 0 mtu 1500 > options=68009b > ether 00:e0:4c:68:04:20 > inet 192.168.1.18 netmask 0xffffff00 broadcast 192.168.1.255 > media: Ethernet autoselect (100baseTX ) > status: active > nd6 options=29 > > I do not know and did not find anything relevant, if the driver is buggy > or the hardware has some problems. Please, advice. I have seen similar behavior, and unable to get an vendor support, so have stopped working on the driver. I have not found a reliable way to reset the hardware to a working state, even via power_off/power_on commands. Sorry that I don't have a solution for you. The closest that I could suggest is to try to drop the USB id from the ure driver or switch it's mode to try the ucdce driver instead. I've seen that it's been more reliable, but it could be because it also runs MUCH slower, and doesn't hit the same bug. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From nobody Sat Oct 30 07:15:19 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 C1E9018198E4 for ; Sat, 30 Oct 2021 07:15:24 +0000 (UTC) (envelope-from se@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 4Hh9YS4z5cz4h3n; Sat, 30 Oct 2021 07:15:24 +0000 (UTC) (envelope-from se@freebsd.org) Received: from [IPV6:2003:cd:5f11:ee00:4d98:a069:45f1:9a6] (p200300cd5f11ee004d98a06945f109a6.dip0.t-ipconnect.de [IPv6:2003:cd:5f11:ee00:4d98:a069:45f1:9a6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: se/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 097DD2C732; Sat, 30 Oct 2021 07:15:23 +0000 (UTC) (envelope-from se@freebsd.org) Message-ID: <6d01974e-216f-b218-06e8-83d055fdc33a@freebsd.org> Date: Sat, 30 Oct 2021 09:15:19 +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 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 Subject: Re: stat(1) isn't honouring locale Content-Language: en-US To: Jamie Landeg-Jones References: <202110291815.19TIFARt072516@donotpassgo.dyslexicfish.net> From: Stefan Esser Cc: freebsd-current@freebsd.org, re@freebsd.org In-Reply-To: <202110291815.19TIFARt072516@donotpassgo.dyslexicfish.net> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------P5JrzA0NKxqomD2i6Y54Ucv2" X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------P5JrzA0NKxqomD2i6Y54Ucv2 Content-Type: multipart/mixed; boundary="------------p30cGKCSNZTlPLN3r0mUVJ01"; protected-headers="v1" From: Stefan Esser To: Jamie Landeg-Jones Cc: freebsd-current@freebsd.org, re@freebsd.org Message-ID: <6d01974e-216f-b218-06e8-83d055fdc33a@freebsd.org> Subject: Re: stat(1) isn't honouring locale References: <202110291815.19TIFARt072516@donotpassgo.dyslexicfish.net> In-Reply-To: <202110291815.19TIFARt072516@donotpassgo.dyslexicfish.net> --------------p30cGKCSNZTlPLN3r0mUVJ01 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am 29.10.21 um 20:15 schrieb Jamie Landeg-Jones: > stat(1) isn't honouring locale. >=20 > The manual page says: >=20 > -t timefmt > Display timestamps using the specified format. This = format is passed directly to strftime(3). >=20 > strftime(3) says: >=20 > %+ is replaced by national representation of the date and time (t= he format is similar to that produced by date(1)). >=20 > However: >=20 > ----------------------------- > % date > Fri Oct 29 00:14:12 BST 2021 >=20 > % date +%+ > Fri Oct 29 00:14:19 BST 2021 >=20 > % stat -t%+ -f '%Sm' . > Fri Oct 29 00:13:38 BST 2021 > ----------------------------- >=20 > % setenv LANG en_GB.UTF-8 >=20 > % date > Fri 29 Oct 2021 00:14:57 BST >=20 > % date +%+ > Fri 29 Oct 2021 00:15:05 BST >=20 > % stat -t%+ -f '%Sm' . > Fri Oct 29 00:13:38 BST 2021 > ----------------------------- >=20 > Including and adding: >=20 > (void) setlocale(LC_TIME, ""); >=20 > before the call to strftime() in usr.bin/stat/stat.c fixes this >=20 > Is there any reason this isn't in place? Hi Jamie, thank you for reporting this issue and suggesting a fix. I have committed your proposed fix to -CURRENT as Git commit 20f8331aca89= 2ff8 and plan to MFC it to 13-STABLE in a few days. I'm CCing to the release engineer, since this might be a change that we w= ant to include in the upcoming 12.3 release (currently in beta). Regards, STefan --------------p30cGKCSNZTlPLN3r0mUVJ01-- --------------P5JrzA0NKxqomD2i6Y54Ucv2 Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAmF88QcFAwAAAAAACgkQR+u171r99UQp mAgAqoBPdVVblATP2yDSx3y51bLmDgRwWnU43lrQ6jyJDHpjLHVpMiVZVyB5qfK5y6dVu1AjJKET emAofZK1d3Y9HVtt2lyJbCQV3+tIm4VYESD+fMJIA/cDermKEpXtAssLKZun9+y6VedoLSfNpw9s LFd1cYhkzZl9U1ldnbF4BSQElyI2BIdqSVm/CSgwEQCe/I2Xm4eYo/kXplMwbhuETrbDUNHvlqRV i7H0Pdv1KBZ/E1e3Q6QzOT5wD5raaguI3lsX1XOSya8Szv8LC6sFUFepDgmXa+etn4fwJc45Zl4u 2K8ICtmBhpkvGQAvZGuWkmahuVdhBYvcVBmpYYjVsg== =JrbL -----END PGP SIGNATURE----- --------------P5JrzA0NKxqomD2i6Y54Ucv2-- From nobody Sat Oct 30 12:12:53 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 7F5B1182B696 for ; Sat, 30 Oct 2021 12:12:54 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:300:2185:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4HhJ8k3GZ6z3Hk7; Sat, 30 Oct 2021 12:12:54 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [104.207.135.49]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 19UCCrP0048038; Sat, 30 Oct 2021 13:12:53 +0100 (BST) (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 19UCCr9V048037; Sat, 30 Oct 2021 13:12:53 +0100 (BST) (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202110301212.19UCCr9V048037@donotpassgo.dyslexicfish.net> Date: Sat, 30 Oct 2021 13:12:53 +0100 Organization: Dyslexic Fish To: se@freebsd.org, jamie@catflap.org Cc: re@freebsd.org, freebsd-current@freebsd.org Subject: Re: stat(1) isn't honouring locale References: <202110291815.19TIFARt072516@donotpassgo.dyslexicfish.net> <6d01974e-216f-b218-06e8-83d055fdc33a@freebsd.org> In-Reply-To: <6d01974e-216f-b218-06e8-83d055fdc33a@freebsd.org> User-Agent: Heirloom mailx 12.4 7/29/08 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-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [104.207.135.49]); Sat, 30 Oct 2021 13:12:54 +0100 (BST) X-Rspamd-Queue-Id: 4HhJ8k3GZ6z3Hk7 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N Stefan Esser wrote: > > % date +%+ > > Fri 29 Oct 2021 00:15:05 BST > > > > % stat -t%+ -f '%Sm' . > > Fri Oct 29 00:13:38 BST 2021 > > ----------------------------- > thank you for reporting this issue and suggesting a fix. > > I have committed your proposed fix to -CURRENT as Git commit 20f8331aca892ff8 > and plan to MFC it to 13-STABLE in a few days. > > I'm CCing to the release engineer, since this might be a change that we want > to include in the upcoming 12.3 release (currently in beta). Thanks, and thanks for the quick response! I wasn't sure if it was an oversight, or if there was something I missed. Cheers, Jamie P.S. Thanks for not mentioning that when I editted the order of my example commands above to appear in a more logical order, I managed to make it look as if I'd gone back in time.... Ooops! From nobody Sat Oct 30 18:31: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 6DCB418331A9 for ; Sat, 30 Oct 2021 18:31:35 +0000 (UTC) (envelope-from se@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 4HhSYg2Jwlz4dY1; Sat, 30 Oct 2021 18:31:35 +0000 (UTC) (envelope-from se@freebsd.org) Received: from [IPV6:2003:cd:5f11:ee00:fd88:d6c6:43fd:9b20] (p200300cd5f11ee00fd88d6c643fd9b20.dip0.t-ipconnect.de [IPv6:2003:cd:5f11:ee00:fd88:d6c6:43fd:9b20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: se/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 9C72126A6; Sat, 30 Oct 2021 18:31:34 +0000 (UTC) (envelope-from se@freebsd.org) Message-ID: <6f3d4cfe-23aa-24ae-f027-aa8b7c7cd19c@freebsd.org> Date: Sat, 30 Oct 2021 20:31:31 +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 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 Subject: Re: stat(1) isn't honouring locale Content-Language: en-US To: Jamie Landeg-Jones Cc: re@freebsd.org, freebsd-current@freebsd.org References: <202110291815.19TIFARt072516@donotpassgo.dyslexicfish.net> <6d01974e-216f-b218-06e8-83d055fdc33a@freebsd.org> <202110301212.19UCCr9V048037@donotpassgo.dyslexicfish.net> From: Stefan Esser In-Reply-To: <202110301212.19UCCr9V048037@donotpassgo.dyslexicfish.net> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------HDZ9TdMNUPRRcnCLKXcFOW4b" X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------HDZ9TdMNUPRRcnCLKXcFOW4b Content-Type: multipart/mixed; boundary="------------09F7jSZkwMKC7x6kfSfI8Yug"; protected-headers="v1" From: Stefan Esser To: Jamie Landeg-Jones Cc: re@freebsd.org, freebsd-current@freebsd.org Message-ID: <6f3d4cfe-23aa-24ae-f027-aa8b7c7cd19c@freebsd.org> Subject: Re: stat(1) isn't honouring locale References: <202110291815.19TIFARt072516@donotpassgo.dyslexicfish.net> <6d01974e-216f-b218-06e8-83d055fdc33a@freebsd.org> <202110301212.19UCCr9V048037@donotpassgo.dyslexicfish.net> In-Reply-To: <202110301212.19UCCr9V048037@donotpassgo.dyslexicfish.net> --------------09F7jSZkwMKC7x6kfSfI8Yug Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am 30.10.21 um 14:12 schrieb Jamie Landeg-Jones:> Stefan Esser wrote: > >>> % date +%+ >>> Fri 29 Oct 2021 00:15:05 BST >>> >>> % stat -t%+ -f '%Sm' . >>> Fri Oct 29 00:13:38 BST 2021 >>> ----------------------------- > >> thank you for reporting this issue and suggesting a fix. >> >> I have committed your proposed fix to -CURRENT as Git commit >> 20f8331aca892ff8 >> and plan to MFC it to 13-STABLE in a few days. >> >> I'm CCing to the release engineer, since this might be a change that >> we want to include in the upcoming 12.3 release (currently in beta). > > Thanks, and thanks for the quick response! I wasn't sure if it was an > oversight,> or if there was something I missed. The man page does not mention a locale dependency, and strftime() without setting a locale just returns the date for the POSIX locale. But I think that it was an oversight, since the date command respects the locale by default and with the change you suggested, it is possible to get the stat output in the locale specific format but also in the format previously displayed. This might be a change that violates POLA, since a format changes in an existing application, and I'm not sure whether a MFC to 12.3 might be too large a change at that time of the release cycle. If it is merged to 13-STABLE I'll add a "add to release notes" marker. But I do think that this is a worthwhile change that has just been forgotten when other utilities have been made locale aware. Regards, STefan --------------09F7jSZkwMKC7x6kfSfI8Yug-- --------------HDZ9TdMNUPRRcnCLKXcFOW4b Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAmF9j4MFAwAAAAAACgkQR+u171r99UTZ ZAgAq+0EyopfBELD2GqTaacNa1FnE8EpJfGeuXo413SJzV9iWVeBExUeinB+FfiIRPLG1wAcCak7 rgDPid+FgKHMvYd0gkx/BbdhsWuWJ6wgdOQUoy+Tb2vkHV5AC+sCuS8O03P2l/TU05L5OnkTV992 QEKPSsFILkDW1HRheQlxCtL//ngWESCKmK3n69j3P8cyBLEFCQvzLsiCKaKrRz49VR1gsIgeIE2/ KKz1I++U8mRU8WTZhm1ResgjBDBANm9sl/8v+70mY3Twvk9LIuR9fj9vgwJxvD6U7fumzYTBhm5w 4dmknVfm1n3NHWZ1EoyhTgzBM5PE8SBW+NekYoRuQA== =QyXl -----END PGP SIGNATURE----- --------------HDZ9TdMNUPRRcnCLKXcFOW4b-- From nobody Sun Oct 31 17:15:25 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 8F80318283DD for ; Sun, 31 Oct 2021 17:15:37 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (plan-b.pwste.edu.pl [IPv6:2001:678:618::40]) (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 "plan-b.pwste.edu.pl", Issuer "GEANT OV RSA CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Hj2qX3kpDz4XLQ for ; Sun, 31 Oct 2021 17:15:36 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from [192.168.7.70] (dom.potoki.eu [62.133.140.50]) (authenticated bits=0) by plan-b.pwste.edu.pl (8.17.1/8.17.1) with ESMTPSA id 19VHFPS7073916 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO) for ; Sun, 31 Oct 2021 18:15:25 +0100 (CET) (envelope-from zarychtam@plan-b.pwste.edu.pl) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=plan-b.pwste.edu.pl; s=plan-b-mailer; t=1635700526; bh=CC+Pff5Ww88C+raFEHcjT5I4/JSYklrA3+46amccFn8=; h=Date:To:References:From:Subject:In-Reply-To; b=LUHSw3es3lWzkkyeo5sbkkFnrdJNyomiLjlayd42R7QLQbFjBHx2479o7FVngyLGK f+SEPxeReiLGiqB9zqNnM/Ywp8z/5ktb9PxmAqcnpbBDA1QCJH2ZuE4uKGV1/y8OZd gBDw89w2pjdqFYrxMtt3pYLXfvQEKAp/ajc2WRqCb8BONf5NobBRJLckyDrSl/6xbW ku3N+1IPf9CpVXQriP3nwbmn8Ie26C7AOUHVdLh6g2zSQnCsS7/8XJ7UNwKgPAl7S4 CeMMAPNRDaI2xUTpK/2CkQ27TALvfG/HNzUNVppDOuJArhOa8hC60pK/l3k8AXTW9J 4TuprN6WmiYqQ== X-Authentication-Warning: plan-b.pwste.edu.pl: Host dom.potoki.eu [62.133.140.50] claimed to be [192.168.7.70] Message-ID: Date: Sun, 31 Oct 2021 18:15:25 +0100 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 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 Content-Language: en-US To: freebsd-current@freebsd.org References: <8d25d2f4-24e2-5b19-5c81-2fe12dc937b7@quip.cz> <20211029074702.d69cba39a643f3f912f8ec81@dec.sakura.ne.jp> <940c9341-6938-05a1-d0b3-f20f07f9d3de@netfence.it> From: Marek Zarychta Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 In-Reply-To: <940c9341-6938-05a1-d0b3-f20f07f9d3de@netfence.it> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4Hj2qX3kpDz4XLQ X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=plan-b.pwste.edu.pl header.s=plan-b-mailer header.b=LUHSw3es; dmarc=pass (policy=none) header.from=plan-b.pwste.edu.pl; spf=none (mx1.freebsd.org: domain of zarychtam@plan-b.pwste.edu.pl has no SPF policy when checking 2001:678:618::40) smtp.mailfrom=zarychtam@plan-b.pwste.edu.pl X-Spamd-Result: default: False [-1.69 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[plan-b.pwste.edu.pl:s=plan-b-mailer]; NEURAL_HAM_MEDIUM(-0.89)[-0.892]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_SPAM_SHORT(1.00)[0.999]; DKIM_TRACE(0.00)[plan-b.pwste.edu.pl:+]; DMARC_POLICY_ALLOW(-0.50)[plan-b.pwste.edu.pl,none]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:206006, ipnet:2001:678:618::/48, country:PL]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N W dniu 29.10.2021 o 08:29, Andrea Venturoli pisze: > > On 10/29/21 00:47, Tomoaki AOKI wrote: > >> But possibly we need to delete current smbfs code from base and switch >> to ports (sysutils/*?) if it require some code having incompatible >> license for base. > +1 for removing smbfs(5) from the base and eventually moving it to the ports tree. I know some people are still using it with a bit of duct tape and baling twine to workaround  SMBv{2,3) incompatibility. With SMBv1 support, only our smbfs(5) became useless a few years ago. Unfortunately, there is no replacement in the ports tree. To mount SMB shares for Nextcloud the port net/pecl-smbclient can be used, but definitely deploying Nextcloud to mount only SMB shares is overkill. > OTOH having a port is not in any way worse as having a broken piece of > base. It sounds reasonable. Moreover, the story of net/wireguard-kmod has proven that moving some modules into ports, where the software development is done in a more flexible way, can be beneficial for both: the developers and the community. My opinion is only the opinion of the FreeBSD user, but I believe that sometimes the feedback from the userbase is important, especially that a few months I was told by one of the younger *NIX admins that our (FreeBSD) community is the best and he is willing to make a transition of some services to FreeBSD as soon as he gets permission from the management. With kind regards, -- Marek Zarychta From nobody Sun Oct 31 22:06:40 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 00FA5182617F; Sun, 31 Oct 2021 22:06:53 +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 4Hj9Hb3XYrz55xg; Sun, 31 Oct 2021 22:06:50 +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 19VM6fFQ021901; Mon, 1 Nov 2021 07:06:41 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Mon, 1 Nov 2021 07:06:40 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Cc: freebsd-stable@freebsd.org Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 Message-Id: <20211101070640.247345226b0dc84717c3ee0b@dec.sakura.ne.jp> In-Reply-To: References: <8d25d2f4-24e2-5b19-5c81-2fe12dc937b7@quip.cz> <20211029074702.d69cba39a643f3f912f8ec81@dec.sakura.ne.jp> <940c9341-6938-05a1-d0b3-f20f07f9d3de@netfence.it> 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=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Hj9Hb3XYrz55xg 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 [0.40 / 15.00]; HAS_REPLYTO(0.00)[junchoon@dec.sakura.ne.jp]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; REPLYTO_ADDR_EQ_FROM(0.00)[]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; DMARC_NA(0.00)[sakura.ne.jp]; HAS_ORG_HEADER(0.00)[]; RCVD_TLS_LAST(0.00)[]; NEURAL_SPAM_SHORT(1.00)[1.000]; NEURAL_HAM_LONG(-1.00)[-0.998]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; 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:7684, ipnet:153.125.128.0/18, country:JP]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[123.48.130.181:received] X-ThisMailContainsUnwantedMimeParts: N On Sun, 31 Oct 2021 18:15:25 +0100 Marek Zarychta wrote: > W dniu 29.10.2021 o$B".(B08:29, Andrea Venturoli pisze: > > > > On 10/29/21 00:47, Tomoaki AOKI wrote: > > > >> But possibly we need to delete current smbfs code from base and switch > >> to ports (sysutils/*?) if it require some code having incompatible > >> license for base. > > > +1 for removing smbfs(5) from the base and eventually moving it to the > ports tree. I know some people are still using it with a bit of duct > tape and baling twine to workaround$B".(B SMBv{2,3) incompatibility. Keeping this in base as long as possible should be preferred, as changes throuout all filesystems would be easier to be missed that on ports. But borrowing GPL'ed (or any other BSD-incompatible licensed) codes would disallow it. > With SMBv1 support, only our smbfs(5) became useless a few years ago. No. It's much better than nothing. For example, DSM on Synology NAS disabled support for SMB1 and NTLM1 by default, but admin can easily enable them again through control panel. So it's usable (for local networks) at least for now. > Unfortunately, there is no replacement in the ports tree. To mount SMB > shares for Nextcloud the port net/pecl-smbclient can be used, but > definitely deploying Nextcloud to mount only SMB shares is overkill. > > > OTOH having a port is not in any way worse as having a broken piece of > > base. > > It sounds reasonable. Moreover, the story of net/wireguard-kmod has > proven that moving some modules into ports, where the software > development is done in a more flexible way, can be beneficial for both: > the developers and the community. > > My opinion is only the opinion of the FreeBSD user, but I believe that > sometimes the feedback from the userbase is important, especially that a > few months I was told by one of the younger *NIX admins that our > (FreeBSD) community is the best and he is willing to make a transition > of some services to FreeBSD as soon as he gets permission from the > management. > > With kind regards, > > -- > Marek Zarychta > > -- Tomoaki AOKI