Date: Fri, 8 Apr 2022 15:32:06 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Mailinglists FreeBSD <freebsd-questions@freebsd.org> Subject: Re: nvidia-driver and no update in /usr/ports/UPDATING Message-ID: <CAN6yY1srvpX39PepetLCPe8Ri-4SgRDXDnLSUHdxxC_Uv%2B3F7g@mail.gmail.com> In-Reply-To: <Yk9tEmvtQB5JEWoz@cloud9.zyxst.net> References: <Yk9tEmvtQB5JEWoz@cloud9.zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--00000000000085e65b05dc2c2d4d Content-Type: text/plain; charset="UTF-8" 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 > 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 <div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon= t-family:tahoma,sans-serif;font-size:small">On Thu, Apr 7, 2022 at 4:01 PM = tech-lists <<a href=3D"mailto:tech-lists@zyxst.net">tech-lists@zyxst.net= </a>> wrote:<br></div></div><div class=3D"gmail_quote"><blockquote class= =3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg= b(204,204,204);padding-left:1ex">Hi,<br> <br> Trying to be a good sysadmin, i like to regularly update. Imagine my <br> surprise when my desktop wouldn't load xorg. I mean, I checked<br> in /usr/ports/UPDATING, and to be sure, /usr/src/UPDATING,<br> *nothing* about nvidia to be found for around this time. As I'm<br> sure everyone here is aware, we are exhorted to check UPDATING<br> so we're not caught out.<br> <br> So *WHY* were the consequences of PR 261666 not in /usr/ports/UPDATING?<br> nvidia-driver was updated to (560) i think. 5-something.. the instance befo= re<br> was moved to nvidia-driver-470 as it's now legacy. That's great and= all,<br> but *WHY* the *F**K* isn't in *UPDATING??!??!?!?!*<br> <br> Why have /usr/ports/UPDATING at all if you're not, like, gonna update i= t?!<br> <br> This isn't the first or second time, with other widely-used ports.<br> <br> I don't use a whole load of ports. This is a desktop, so ~1500 ports or= so.<br> It ain't just me using freebsd as a desktop, and it ain't just me u= sing <br> nvidia-driver.<br> <br> Lots of ppl might be disinclined to fire off an email like this. <br> "Install linux, at least it works", theyll say. And they'll d= elete FreeBSD.<br> <br> Great job. Not.<br> -- <br> J.<br> </blockquote></div><br clear=3D"all"><div style=3D"font-family:tahoma,sans-= serif;font-size:small" class=3D"gmail_default">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.</div><div style=3D"font-family:tahoma,sans-serif= ;font-size:small" class=3D"gmail_default"><br></div><div style=3D"font-fami= ly:tahoma,sans-serif;font-size:small" class=3D"gmail_default">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 (<a href=3D"mailto:freebs= d-x11@freebsd.org">freebsd-x11@freebsd.org</a> 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. <br></div><div st= yle=3D"font-family:tahoma,sans-serif;font-size:small" class=3D"gmail_defaul= t"><br></div><div style=3D"font-family:tahoma,sans-serif;font-size:small" c= lass=3D"gmail_default">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. <br></div><div style=3D"font-family:tahoma,= sans-serif;font-size:small" class=3D"gmail_default"><br></div><div style=3D= "font-family:tahoma,sans-serif;font-size:small" class=3D"gmail_default">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.<br></div>-- <br><div dir=3D"ltr" class= =3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir= =3D"ltr"><div><div dir=3D"ltr">Kevin Oberman, Part time kid herder and reti= red Network Engineer<br>E-mail: <a href=3D"mailto:rkoberman@gmail.com" targ= et=3D"_blank">rkoberman@gmail.com</a><br></div><div>PGP Fingerprint: D03FB9= 8AFA78E3B78C1694B318AB39EF1B055683</div></div></div></div></div></div></div= ></div></div> --00000000000085e65b05dc2c2d4d--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1srvpX39PepetLCPe8Ri-4SgRDXDnLSUHdxxC_Uv%2B3F7g>