From nobody Fri Apr 8 22:32:06 2022 X-Original-To: freebsd-questions@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 5BF871A872E7 for ; Fri, 8 Apr 2022 22:33:11 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oi1-x235.google.com (mail-oi1-x235.google.com [IPv6:2607:f8b0:4864:20::235]) (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 4KZtLZ4l4cz3G0F for ; Fri, 8 Apr 2022 22:33:10 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-oi1-x235.google.com with SMTP id v75so10283848oie.1 for ; Fri, 08 Apr 2022 15:33:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=uA7EQpbNYXuvupu02CvDnh0c5JQgfkhhQFrqFuTc4Ys=; b=kGCRPO6DFO2wdBb4hJ8lJxmLdwNCFM4QpKXtmn/SoOov1yZtkIa1HW5xz0HZLwflbA P4ciPS2njAsPzRBl3B3V6FuY6AdbdDvc+d/8t5bpuJRVfEhA3/9me+XtLMeaib1eI8Wo hOEboeDVw0lb7zSafDYV2sSVFEIWTBSG9vfLo0UXKvrJPlKK9X/j1GYOXhDtsaXwQPKp 3h9KrQ5C79FYR2GuVq4zrJlG+JMqPF9Ggt1MeMhhYsR8qA4YNYKAArYwoW8A+TV7bDCj qkA+kHa3Z6ebJFe6BaJrnbWggV2BKF6Jg8NKTqVpZYBuBAdHY09nX1DxdI0Yuz4Vp4nR e6Ig== 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; bh=uA7EQpbNYXuvupu02CvDnh0c5JQgfkhhQFrqFuTc4Ys=; b=LiPvvU18mGe76abJSeudKcO9aYETFfXf89+rV2k0jrnwk4LLiX7CdDSa3OV0gssyQY yA0xX0j14v3wC3UTdb3H7b4pJgf0brNAwGKRcYeyAq0nZ/XmuOScInJiYun+4iNWs4KW k5TARUBgMwxDI2/SEHRAKxWvi/tRcs/Shqs/43Ttq9A401+5PNW+2hamp20V/WfZ4MGU DtGqBqVXFd9OOZ4Qjq5Xv30YT5tcXgWmLs1Hie2UB/prgHp2x4tHzRAR4J8qFMsIVTOS 10o0TXnx69PbY1L0pFbonDgCOMKga6S18+8CyBbjgJaIRrQafH5DoGRCyX2/WTTSHEmc THMQ== X-Gm-Message-State: AOAM533ZZxTaxopKQeSVa0x+SEoKINgPQmtQ2DiH3KC+ha3w6eMh+Npl xhE4JitPXai/B/7J0eqZ/oPW+cby6132f51AnWiv5wes X-Google-Smtp-Source: ABdhPJzuXpy0ed/lg1+mno5aX4mgVUIZK0elAgsmgFXXy4R0ZeVaLd4tkS38hlBmiDc9Yiko05tzieRLloNlaptkSUQ= X-Received: by 2002:a05:6808:1591:b0:2f9:c5b5:7970 with SMTP id t17-20020a056808159100b002f9c5b57970mr941573oiw.142.1649457183972; Fri, 08 Apr 2022 15:33:03 -0700 (PDT) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Kevin Oberman Date: Fri, 8 Apr 2022 15:32:06 -0700 Message-ID: Subject: Re: nvidia-driver and no update in /usr/ports/UPDATING To: Mailinglists FreeBSD Content-Type: multipart/alternative; boundary="00000000000085e65b05dc2c2d4d" X-Rspamd-Queue-Id: 4KZtLZ4l4cz3G0F X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=kGCRPO6D; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of kob6558@gmail.com designates 2607:f8b0:4864:20::235 as permitted sender) smtp.mailfrom=kob6558@gmail.com X-Spamd-Result: default: False [-3.70 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FORGED_SENDER(0.30)[rkoberman@gmail.com,kob6558@gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[rkoberman@gmail.com,kob6558@gmail.com]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::235:from]; MLMMJ_DEST(0.00)[freebsd-questions]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N --00000000000085e65b05dc2c2d4d Content-Type: text/plain; charset="UTF-8" On Thu, Apr 7, 2022 at 4:01 PM tech-lists wrote: > Hi, > > Trying to be a good sysadmin, i like to regularly update. Imagine my > surprise when my desktop wouldn't load xorg. I mean, I checked > in /usr/ports/UPDATING, and to be sure, /usr/src/UPDATING, > *nothing* about nvidia to be found for around this time. As I'm > sure everyone here is aware, we are exhorted to check UPDATING > so we're not caught out. > > So *WHY* were the consequences of PR 261666 not in /usr/ports/UPDATING? > nvidia-driver was updated to (560) i think. 5-something.. the instance > before > was moved to nvidia-driver-470 as it's now legacy. That's great and all, > but *WHY* the *F**K* isn't in *UPDATING??!??!?!?!* > > Why have /usr/ports/UPDATING at all if you're not, like, gonna update it?! > > This isn't the first or second time, with other widely-used ports. > > I don't use a whole load of ports. This is a desktop, so ~1500 ports or so. > It ain't just me using freebsd as a desktop, and it ain't just me using > nvidia-driver. > > Lots of ppl might be disinclined to fire off an email like this. > "Install linux, at least it works", theyll say. And they'll delete FreeBSD. > > Great job. Not. > -- > J. > First, this issue does not belong in /usr/src/UPDATING. X and all graphics is not a part of the base system in FreeBSD. It is in many ports, though, so any such information belongs in /usr/ports/UPDATING. I will also say that I have been annoyed several times by changes that impacted operations that were not mentioned in UPDATING. I don't go yell obscenely to the world about it. I drop a note to the maintainer ( freebsd-x11@freebsd.org in this case) reminding them that this change really needs to be documented so people will not have very irritating problems. If this does not work, I open a ticket which will, at least, annoy the maintainer(s) into taking some action. Much of the work done to make FreeBSD progress is by volunteers, although more and more is paid for by donations (FreeBSD Foundation) or by employees of companies that depend on it for their products/services. The volunteers are likely to just get mad and stop helping if this sort of thing comes very often. Please excuse me (or don't) the next time you have a question to which I know the answer and just ignore it. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --00000000000085e65b05dc2c2d4d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Apr 7, 2022 at 4:01 PM = tech-lists <tech-lists@zyxst.net= > wrote:
Hi,

Trying to be a good sysadmin, i like to regularly update. Imagine my
surprise when my desktop wouldn't load xorg. I mean, I checked
in /usr/ports/UPDATING, and to be sure, /usr/src/UPDATING,
*nothing* about nvidia to be found for around this time. As I'm
sure everyone here is aware, we are exhorted to check UPDATING
so we're not caught out.

So *WHY* were the consequences of PR 261666 not in /usr/ports/UPDATING?
nvidia-driver was updated to (560) i think. 5-something.. the instance befo= re
was moved to nvidia-driver-470 as it's now legacy. That's great and= all,
but *WHY* the *F**K* isn't in *UPDATING??!??!?!?!*

Why have /usr/ports/UPDATING at all if you're not, like, gonna update i= t?!

This isn't the first or second time, with other widely-used ports.

I don't use a whole load of ports. This is a desktop, so ~1500 ports or= so.
It ain't just me using freebsd as a desktop, and it ain't just me u= sing
nvidia-driver.

Lots of ppl might be disinclined to fire off an email like this.
"Install linux, at least it works", theyll say. And they'll d= elete FreeBSD.

Great job. Not.
--
J.

First, this issue does not b= elong in /usr/src/UPDATING. X and all graphics is not a part of the base sy= stem in FreeBSD. It is in many ports, though, so any such information belon= gs in /usr/ports/UPDATING.

I will also s= ay that I have been annoyed several times by changes that impacted operatio= ns that were not mentioned in UPDATING. I don't go yell obscenely to th= e world about it. I drop a note to the maintainer (freebsd-x11@freebsd.org in this case) reminding them= that this change really needs to be documented so people will not have ver= y irritating problems. If this does not work, I open a ticket which will, a= t least, annoy the maintainer(s) into taking some action.

Much of the work done to make FreeBSD progress is by= volunteers, although more and more is paid for by donations (FreeBSD Found= ation) or by employees of companies that depend on it for their products/se= rvices. The volunteers are likely to just get mad and stop helping if this = sort of thing comes very often.

Ple= ase excuse me (or don't) the next time you have a question to which I k= now the answer and just ignore it.
--
Kevin Oberman, Part time kid herder and reti= red Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB9= 8AFA78E3B78C1694B318AB39EF1B055683
--00000000000085e65b05dc2c2d4d--