I’m the administrator of kbin.life, a general purpose/tech orientated kbin instance.
I boot into windows every time that one NTFS partition I never converted gets locked for needing a check… Come on kernel 7.1. I need that new ntfs with the fsck tool!
Yeah I could convert it. But there’s some stuff on there I might want to run from windows, once every 1.5 years or something.
The only RGB things I have is an NVidia 3080, and the RGB ram. Unplugging those would cause me a problem. I could set them to off. But, they’re there now. So I make them Borg green.
But if either of them (or the case) cost me more to have the RGB/Glass I’d not have gotten them. It’s absolutely not something I care about.
You’re not kidding. I have no real interest in RGB. But it was cheaper to buy a case with a glass panel and the RGB ram of the same spec was cheaper than non RGB… I just made all the LEDs Borg green and left it that way.
Hey, it was really better times when you could have your computer in any colo(u)r you wanted, so long as it was beige.
Way way back. I was given a 486 (when pentium 90/100s were normal) at work to run the experimental internet connection on (the head of the company at the time didn’t think this internet fad would last). So I installed some magazine coverdisk linux and connected the office to the internet via a single modem.
I think it had a peak uptime of 550 days before it was replaced.
windows is crashing linux is flowering, with linux there is no old pc only bad OS.
Unless it is a 486 and you want to stay current :P
If you set the ip of the router to fe80::1 then anything directly connected should be fine to connect using that address.
The thing is. Any year can be the year of IPv6. Google is on ipv6, youtube is on ipv6, facebook is on ipv6. Pretty much every datacentre I’ve used (OK limited to Europe) give you IPv6 for free by default. Deploying a web site to be IPv4 and IPv6 is trivial and people that use automation should be able to quite easily apply ipv6 to those scripts.
It’s really just the ISPs (more so in the US as I understand it), lazy IT people and the FUD myths holding us back at this point.
IPv6. No. Badly configured IPv6 routers, yes. But that’s something that would fix itself if it became the only protocol in use. And most routers now are pretty good at it from what I’ve seen. But it used to be the case it was easy to find bad routers.
The myth seems to be that NAT provides security. But a good default configuration for consumer routers would give the same security as NAT while providing the advantages and extra security IPv6 provides.
IPv6 usually has privacy extensions enabled. Which means it will generate throwaway IP addresses that rotate regularly for your outgoing connections, these IPs do not accept incoming connections. So someone cannot nmap you to find open ports based on the IP you connected to their server with.
Not to mention that most ISPs give each user more IPs than the whole IPv4 internet has. So, port scanning an entire /64 is not going to be fun.
Well you could accept the default generated one, or set it to fe80::1 manually. Don’t most good routers now have a DNS server in? So you could make it router.local or something?
I think some even by default make a DNS entry call router.local or similar pointing to themselves. This isn’t a real problem and if IPv6 were adopted fully, then all routers would likely come with something like this setup anyway.
However, my understanding is that this could be exploited only by authenticated users with permission to add new media. Not like that’s a risk to ignore, but it’s not like it could be exploited by anyone on the Internet.
I wonder if that’s the reason for setting the default live TV management permission to false. Since that permission might well the the route to adding your own malicious m3u link for that second change.
Reverse proxy will let anyone connect to it. VPN, you can create keys/logins for your intended users only. Having said that, from what I could see, nothing in the security fixes were to do with authentication. I think (just from a cursory look), they could only be exploited, if at all from an authenticated user session.
But personally, something like jellyfin where the number of people I want to be able to access it is very limited, stays behind a VPN. Better to limit your potential attack surface as much as you can.
From a cursory look at just the security commits. Looks like the following:
I’m not really sure how serious any of these are, or how they could be exploited however. Well aside from the local file in stream files one.
Not sure what you mean. I just saw asterisks.
If you want to go super de-centralised. Just remove the internet and go for a mesh network :P
I’d say the ideal situation is that tools are developed library first, then cli or gui as preferred allowing others to pick up the slack and make the other tool (or tools) using the functions in the library.
One of the reasons automation is so much easier on linux than windows is because there are many more cli tools to do things. On windows many tools are gui first and cannot easily be automated.
That’s weird. Whenever I’ve had gpu drivers fail the environment didn’t come up and I would be left at a terminal.
But, they shouldn’t need rescue. The issue is no nvidia driver, but you can still login from the text terminals. Ctrl + Alt + F3, F4 etc etc. In fact when the window environment fails to load it should drop back to terminal.
I have a 3080, so 590 is fine for me. But, I’m sure the legacy one is a dkms. But the process of installing that should be done as part of the install. E.g. you install, reboot
What does lspci -k show for the card in terms of Kernel driver in use, and kernel modules?
Also what does dkms status say?
If the module is installed and showing in dkms status and showing as used in lspci -k, it should be available for desktop environments.
I do agree in terms of effort when things go wrong though. I remember when I was a lot younger and I had no problems just sitting in front of my keyboard finding whatever the latest problem is. Now, I want to be doing things with my PC.
But, a bit of debugging might be worthwhile before doing a new installation.
Going to show my age again now.
I think post 1990, they were rare. Essentially there was a time before that though, when computers often didn’t have a hard drive. Because they were like 10MB and cost thousands of whatever your currency may be.
So in those days (8088/8086 based systems largely), it was common for there to be 2x5.25" drives. A: and B:. C: was a status symbol, the lambo of the early computer era.
As hard drives became more affordable (for levels of affordability), there was also the rise of the new disk type. 3.5". In that case it wasn’t too uncommon to have a 3.5" drive, a 5.25" drive and a hard disk. So you’d have A:, B: and C:.
I think after the mid 90s the much more common setup was a single high density 3.5" drive A: and a hard disk C:. In the office we also had an F: drive (Novell netware network drive).
A: and B: were by and large kept free out of that history. I am pretty sure you can map HDDs/SSDs to them these days though if you want to.