Re: need perm. fix for monitor/display problem.

On 12/16/22 10:33, home user wrote: I shut down nightly.  So I do notice the long time.  I hear at least 3 long surges of the cooling fans during shutdown.  But I don't know of a way of knowing what's really going on (the screens are blank).  Since this is the first I've seen or heard anything

Re: need perm. fix for monitor/display problem.

On 12/15/22 19:55, home user wrote: Question #1: When I do the fix, should I do it while booted in 5.19.16-200.fc36 or while booted in 6.0.5-200.fc36? Do it from the working kernel. That way there's no chance of it getting removed during the upgrade.

Re: need perm. fix for monitor/display problem.

> On 16 Dec 2022, at 16:26, Joe Zeff wrote: > > On 12/16/2022 02:10 AM, Barry wrote: > [snip] >> I always ask on the rpmfusion dev mailing list if the nvidia driver is an >> issue. >> It is where the person maintaining the packages will see a query. > > Is there a reason that you don't use t

Re: 127.0.0.53 question

On 12/16/2022 11:06 PM, Samuel Sieb wrote: I almost questioned you until I realized what your point was.  It would have helped if you explained what you meant.  Yes, 631 is not a valid IP octet. Exactly. I've been retired for over a decade but I found it obvious the moment I saw that "addres

Re: 127.0.0.53 question

On 12/16/22 22:44, ToddAndMargo via users wrote: On 12/16/22 22:11, Samuel Sieb wrote: On 12/16/22 21:18, ToddAndMargo via users wrote: On 12/16/22 20:23, Mike Wright wrote: 127.0.0.0/8 is the loopback address.  That means that any IP that begins with 127 is a valid loopback address.  The thre

Re: 127.0.0.53 question

Is that Dnsmasq like bind? The only thing I've ever cared to run would be something like rsync and ssh as far as servers. On Sat, Dec 17, 2022, 1:44 AM ToddAndMargo via users < users@lists.fedoraproject.org> wrote: > On 12/16/22 22:11, Samuel Sieb wrote: > > On 12/16/22 21:18, ToddAndMargo via us

Re: 127.0.0.53 question

On 12/16/22 22:11, Samuel Sieb wrote: On 12/16/22 21:18, ToddAndMargo via users wrote: On 12/16/22 20:23, Mike Wright wrote: 127.0.0.0/8 is the loopback address.  That means that any IP that begins with 127 is a valid loopback address.  The three 0's can each be any number from 0 through 255.

Re: 127.0.0.53 question

On 12/16/22 22:06, Samuel Sieb wrote: On 12/16/22 21:33, Jeffrey Walton wrote: On Sat, Dec 17, 2022 at 12:27 AM Tim via users wrote: [...] Both are valid addresses. 127.0.0.631 is *unlikely* to be in use, but is valid. Huh? Citation, please. I almost questioned you until I realized what y

Re: 127.0.0.53 question

On 12/16/22 21:18, ToddAndMargo via users wrote: On 12/16/22 20:23, Mike Wright wrote: 127.0.0.0/8 is the loopback address.  That means that any IP that begins with 127 is a valid loopback address.  The three 0's can each be any number from 0 through 255. So the 127.0.0.53 was the bind guys

Re: 127.0.0.53 question

On 12/16/22 21:33, Jeffrey Walton wrote: On Sat, Dec 17, 2022 at 12:27 AM Tim via users wrote: [...] Both are valid addresses. 127.0.0.631 is *unlikely* to be in use, but is valid. Huh? Citation, please. I almost questioned you until I realized what your point was. It would have helped i

Re: 127.0.0.53 question

On Sat, Dec 17, 2022 at 12:27 AM Tim via users wrote: > [...] > Both are valid addresses. > > 127.0.0.631 is *unlikely* to be in use, but is valid. Huh? Citation, please. Jeff ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send

Re: 127.0.0.53 question

ToddAndMargo: >> So I tried CUPS: 127.0.0.631.  No joy.  CUPS still wanted >> 127.0.0.1:631. Joe Zeff: > That isn't a valid IP address. Both are valid addresses. 127.0.0.631 is *unlikely* to be in use, but is valid. 127.0.0.1:631 is port 631 at 127.0.0.1. Valid addresses, but only on the same

Re: 127.0.0.53 question

On 12/16/22 20:23, Mike Wright wrote: On 12/16/22 20:06, ToddAndMargo via users wrote: On Fri, Dec 16, 2022, 10:31 PM ToddAndMargo via users > wrote:     Hi All,     I am use to seeing 127.0.0.1, but now I am seeing     things like 127.0.0.53.     This i

Re: 127.0.0.53 question

On 12/16/22 20:06, ToddAndMargo via users wrote: On Fri, Dec 16, 2022, 10:31 PM ToddAndMargo via users mailto:users@lists.fedoraproject.org>> wrote:     Hi All,     I am use to seeing 127.0.0.1, but now I am seeing     things like 127.0.0.53.     This is used with my caching named server on

Re: 127.0.0.53 question

It's called the loopback address. The private class of ip is not nonroutable. On Fri, Dec 16, 2022, 11:10 PM Bill C wrote: > 127.0.0.1 is reserved for your machine. There are series of private > addresses in each ip class. 127 series and 192.168 series. They will not > work on the internet. A po

Re: 127.0.0.53 question

127.0.0.1 is reserved for your machine. There are series of private addresses in each ip class. 127 series and 192.168 series. They will not work on the internet. A port of 53 would look like 127.0.0.1:53. On Fri, Dec 16, 2022, 11:06 PM ToddAndMargo via users < users@lists.fedoraproject.org> wrote

Re: 127.0.0.53 question

On Fri, Dec 16, 2022, 10:31 PM ToddAndMargo via users mailto:users@lists.fedoraproject.org>> wrote: Hi All, I am use to seeing 127.0.0.1, but now I am seeing things like 127.0.0.53. This is used with my caching named server on port 53. So I figured that the last digit

Re: 127.0.0.53 question

On 12/16/22 19:32, Jeffrey Walton wrote: On Fri, Dec 16, 2022 at 10:31 PM ToddAndMargo via users wrote: I am use to seeing 127.0.0.1, but now I am seeing things like 127.0.0.53. This is used with my caching named server on port 53. So I figured that the last digit was the (local) port. So I

Re: 127.0.0.53 question

Up to 255 On Fri, Dec 16, 2022, 10:31 PM ToddAndMargo via users < users@lists.fedoraproject.org> wrote: > Hi All, > > I am use to seeing 127.0.0.1, but now I am seeing > things like 127.0.0.53. > > This is used with my caching named server on > port 53. > > So I figured that the last digit was th

Re: 127.0.0.53 question

On 12/16/2022 08:30 PM, ToddAndMargo via users wrote: So I tried CUPS: 127.0.0.631.  No joy.  CUPS still wanted 127.0.0.1:631. That isn't a valid IP address. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to user

Re: 127.0.0.53 question

On Fri, Dec 16, 2022 at 10:31 PM ToddAndMargo via users wrote: > > I am use to seeing 127.0.0.1, but now I am seeing > things like 127.0.0.53. > > This is used with my caching named server on > port 53. > > So I figured that the last digit was the (local) > port. > > So I tried CUPS: 127.0.0.631.

127.0.0.53 question

Hi All, I am use to seeing 127.0.0.1, but now I am seeing things like 127.0.0.53. This is used with my caching named server on port 53. So I figured that the last digit was the (local) port. So I tried CUPS: 127.0.0.631. No joy. CUPS still wanted 127.0.0.1:631. So what exactly is the last f

Re: Named keeps dying on me

On 12/15/22 16:26, Sam Varshavchik wrote: ToddAndMargo via users writes: # cat /etc/resolv.conf nameserver 127.0.0.53 options edns0 trust-ad search . Ummm. This is not bind. This is, most likely, systemd-resolved. The problem happens whenever a network configuration event occurs, such and

Re: need perm. fix for monitor/display problem.

On Fri, 2022-12-16 at 11:33 -0700, home user wrote: > On 12/15/22 4:07 PM, John Pilkington wrote: > > > > > I have no way of knowing what idiosyncrasies your system may have. > > > > I said what works for me.   I use 'atop' to judge when the builds > > have > > completed, and yes, recent shutdo

Re: need perm. fix for monitor/display problem.

On Fri, 2022-12-16 at 10:21 +, John Pilkington wrote: > I prefer to let the akmods complete before rebooting, and have found in > the past that 'sudo systemctl reboot' was more reliable after nvidia > updates than the usual reboot from the GUI. Surely if you did it from the command line, the

Re: need perm. fix for monitor/display problem.

On 12/15/22 16:03, home user wrote: On 12/15/22 9:09 AM, Robert McBroom via users wrote: On 12/14/22 22:45, home user wrote: [... snip ...]  set /etc/dnf.conf to retain the kernels of several updates to give rpmfusion time to catch up to new kernels in a new major grouping. Can take a couple

Re: need perm. fix for monitor/display problem.

On 12/15/22 8:32 PM, Tim via users wrote: I up mine to about 5. That way if there's a flurry of kernel updates (which has happened in the past) and one or more of them cause me a problem, I'll still have an older one to rely on. I haven't run into that yet. As in the current situation, I fir

Re: need perm. fix for monitor/display problem.

On 12/15/22 4:07 PM, John Pilkington wrote: I have no way of knowing what idiosyncrasies your system may have. I said what works for me.   I use 'atop' to judge when the builds have completed, and yes, recent shutdowns (but not today's) have also been affected by a delay timer. (Do you mea

Re: need perm. fix for monitor/display problem.

On 12/16/2022 02:10 AM, Barry wrote: [snip] I always ask on the rpmfusion dev mailing list if the nvidia driver is an issue. It is where the person maintaining the packages will see a query. Is there a reason that you don't use the akmod and get it built automagically? [snip]

Setting up a stable/secure test web server/webapp on a cloud server.

Hi. As a pure test, I'm thinking of putting together a test app on a cloud server. I've seen a bunch of blogs/vids/etc.. But I'm concerned about the security aspects of the test server. So, are there any solid/serious best practices that the list can recommend? In looking over Centos/Ubuntu, from

Re: need perm. fix for monitor/display problem.

On 16/12/2022 03:55, home user wrote: On 12/14/22 8:45 PM, home user wrote: (see bottom if needed) essential background review: * the Nov. 03 "dnf upgrade" that caused the display problem also upgraded the kernel from 5.19.16-200 to 6.0.5-200.fc36. * I've been using the 5.19.16-200 exclusively

Re: need perm. fix for monitor/display problem.

> On 15 Dec 2022, at 23:09, John Pilkington wrote: > > On 15/12/2022 21:17, home user wrote: >>> On 12/15/22 2:56 AM, John Pilkington wrote: On 15/12/2022 03:45, home user wrote: >>> [... snip ...] >>> >>> I just did 'dnf upgrade' on a system with an old Dell monitor and an >>> Android

Re: need perm. fix for monitor/display problem.

> On 15 Dec 2022, at 21:19, home user wrote: > > On 12/15/22 2:56 AM, John Pilkington wrote: >> On 15/12/2022 03:45, home user wrote: > [... snip ...] >> I just did 'dnf upgrade' on a system with an old Dell monitor and an Android >> tv. Graphics card is GT 710 running X11 in KDE. The activ