Although to be fair, WSL fixes that issue to a big degree. Maybe even better than OSX, since you get a real Linux with real userspace. WSL(2) might be the only really cool feature Microsoft added to Windows, that actually brings value for the user.
Although to be fair, WSL fixes that issue to a big degree. Maybe even better than OSX, since you get a real Linux with real userspace. WSL(2) might be the only really cool feature Microsoft added to Windows, that actually brings value for the user.
Offlive account during install works only when you are not connected to the internet from that PC. Maybe also only with Win Pro, not Home.
The crap you have to disable are all dark patterns and I hope the EU rips them a few more holes.
“Just update”… I think I went into enough details about what pissed me off in my initial comment.
Almost every Linux distro would have been: boot the installer, select disk, select meta packages, username, password, done. 10 mins later you have an up to date system with no shady online crap.
I remember buying a bunch of old HP ISA 100Mbit NICs to turn an old computer into a router/server combo. Naive as I was I put them all in and nothing worked. Turns out they were all configured to use the same IRQ (since they likely came from independent machines), and that caused them to overwrite each others settings… including the MAC adress. Thankfully I found some nice hacker that worked with these cards before and published a little C tool to rewrite their EEPROMs. I contacted him if he sees a chance to resurrect the cards and that saint indeed hacked the necessary features into his tool so I could rewrite the MAC adresses, change the IRQ one by one and ended up with a working network. Good times.
Heh, yeah. I had to fix that earlier this year on another machine, but that one was ooold and went through a bunch of upgrades so I figured it was due to its age (even though I still didn’t get how they could be so lazy to not automate this process as part of the update or … well… slim down the rescue tools again). But then they apparently didn’t even care enough to release a new installer that prevents the issue. So they either don’t give a crap or even do it deliberately to break Win 10 in favor of Win 11. Either case: that’s not what I pay for.
And that’s exactly what I said: the installer didn’t give me that choice. I had to use a MS account and I had to set up a PIN. Everything else required completely nonintuitive changes (plural!) afterwards.
I know. My point was that I don’t wanted any local auth at all. It should boot right to desktop, no PIN or password asked. The linked MS account is completely worthless and only used to satisfy the installer.
Just this weekend I had the pleasure of installing Win 10 on a blank disk. The install went ok, but then it bothered me logging into the MS Account. After cursing for a while and since it wasn’t my PC, I gave in. I know I can fight it, but it’s not worth it here. Then it continued trying to get me to consent to all kinds of shit. NO, I DON’T WANT FUCKING OFFICE AND I DON’T WANT MY FILES IN ONEDRIVE you assholes!
Then it forces me to choose a PIN for “secure login”. DUDE! That motherfucking PC is used for a bit of office work and gaming. Just let these poor people boot up the machine and use it! 0000? Too simple. 1234 too. Fuck you, MS. Ok, random PIN and a sticky note it is, asshats.
Anyway, after getting it to fuck off, I continue to the desktop. Oh wow, 10 updates and a ton of missing drivers? It’s a fresh install! What the fuck did it install?! Of course the installation of all these updates takes an hour and countless restarts… AFTER A FRESH INSTALL! Not even my overblown super slow Ubuntu server takes that long for updates; and that runs on a HDD not a SSD like that PC I set up.
But wait. One update failed. Why? Ah, the rescue partition is too small… THE ONE THAT DUMB SON-OF-BITCH CREATED ON ITS OWN AS PART OF THE INSTALL! How to fix? Ah, execute a bunch of commandline foo with diskpart
and other tools. Wait, isn’t that exactly the kind of shit that Windows fans laugh about when looking down on us Linux nerds?!
So … ugh … just one simple anecdote of why Windows can fuck off.
I still rank OSX higher, simply because it’s at least consistent. Windows is a fucking mess.
What I find weird about Tumbleweed is, that updating is not integrated into YaST or another UI. You have to use the commandline to keep your system up to date. That makes it exactly as inconvenient as Arch for newcomers, but Arch has a whole philosophy behind this while SuSE is typically very GUI oriented. It’s weird.
Mostly a nitpick, but for that little helper I would have stuck to the stdlib and not pulled in a dependency like echo
.
Otherwise: nice idea. I did something similar but since caddy runs directly on my host, I added permissions for the other services that need the cert and then pointed them directly at it.
If the AppleTV allowed side loading, it would be my dream device. The UX and the speed of Apple devices are just so damn pleasing. But the artificial limits they impose on what you can run on them is damn frustrating.
SiYuan is an opensource Notion alternative. (Not a clone.)
Lookup if the device is supported by LocalTuya though.
I made the mistake thinking that LocalTuya somehow acts like a proxy for a generic protocol, but it actually needs to understand the devices. Now I have a doorbell I can’t use with it.
I am surprised that no one mentioned snikket yet, which is essentially a distribution of Prosody with sane defaults and a custom client.
I meant DNS within your container network. Exposed stuff should be mapped to host ports.
The bigger issue (IMO) is, that you now have a hard requirement on the startup order of your services. If another one happens to get the IP assigned automatically befor your service starts that requests it explicitly, you now have a conflict that you manually have to resolve.
DNS is the only sane solution here.
But everyone does keep their license. A company can not really take over in the sense that you lose your old code. They can stop developing in public but keep using your code, but so can you keep using the last public version and keep developing it. Or you can take your contribution and apply it elsewhere.
Tbf, systemd also makes it relatively easy to sandbox processes. But it’s opt-in, while for containers it’s opt-out.
There is no “maybe” here. With
systemctl suspend
you tell systemd to suspend the whole machine. Most of the hardware will be powered down.Maybe you should generally separate those concerns? Depends entirely on your usecase, but maybe you want your screenlock to do only that… lock the screen. Then you do not want suspend/sleep in there at all.