[-] Ooops@feddit.org 1 points 11 hours ago* (last edited 11 hours ago)

Dass das der Plan ist, ist offensichtlich. Darauf bezog sich mein Kommentar aber nicht.

Weder der Bayrische Rundfunk noch der hier zitierte Energieökonom gehören der C*U (oder meinerwegen auch allgemein der Regierung) an. Also nochmal... Wie kommt der von unseren Gebühren finanzierte ÖRR mit einer expliziten Pflicht Menschen objektiv zu informieren dazu das offensichtliche Lügenmärchen von den verfügbaren Bio-Brennstoffen weiter zu verbreiten? Das ist ja nicht mal mehr nur regierungfreundliches Framing, sondern eiskalte Desinformation. Müssen die wirklich zwanghaft jedes Narrativ des rechten Abschaums bestätigen und wollen sich die Bezeichnung Lügenpresse jetzt redlich verdienen? Daher: Dumm oder korrupt? Ich hätte halt gern Antworten, wieso man sich dermaßen selbst zerlegen sollte solchen Müll zu verbreiten.

[-] Ooops@feddit.org 1 points 11 hours ago

Wenige werden davon mitbekommen haben

Und in wie fern passt das nicht in die oben genannten Kategorien?

[-] Ooops@feddit.org 2 points 22 hours ago* (last edited 21 hours ago)

Note that Windows will boot just fine on a disk with multiple ESPs

Nice for Windows to support this theoretically but the UEFI standard does not require support for multiple ESPs on a disk, so you will easily find hardware that in fact will simply discover the first ESP then stop. Because actual implementations matter and a lot of them are bad.

Speaking of bad implementations. We got several manufacturers a few years ago where their UEFI implementation broke and bricked the whole device after editing the EFI entries via efibootmgr exactly as defined by standard. Oh, you wanted to install Linux? Your device is now done because no one ever tested them without anything but the Windows pre-installs.

Yet two other cases of totally coincidental "This should work but doesn't, must be a Linux issue" artificially created by Microsoft (who after all were one of the driving forces behind UEFI development, also the reason we are still stuck with FAT32 ESPs - the only file system ESPs are required to support by the standard with everything else optional).

Windows never touched the main EFI entry in my cases

In the end positive anecdotal experiences don't matter much. If a relevant fraction of users has issues that should not exist when installing Linux (and that obviously don't exist with Windows because here OEMs actually do proper testing here... or it's Windows/Microsoft itself causing the issues (pre-installed key, fast boot shenanigans, hardware that should be supported but randomly isn't etc.)) that's helping to prevent a lot of people from trying it in the first place. And that's by design.

[-] Ooops@feddit.org 2 points 22 hours ago* (last edited 22 hours ago)

Why would Russia react differently knowing that the majority of Europeans are brain-washed idiots easily manipulated by bots.

Russia sells <10% of their (already deminished, too) exports to Europe, yet an idiotic article without any actual references makes you believe that Europe is failing and has to be blamed. Sanctions totally demolished Russian imports, yet for years we get articles hallucinating how the import increases in neighbouring countries obviously circumvent those sanctions - even when in reality those increases make up less than 1% in total of what Russia lost, so the actual story should have been that they are 99%+ effective.

It's always the same pattern: "Look, big number! Be angry!! Europe bad!!!" And it works -as can be seen by all the comments here- every single time. Or did you actually stop one second to check those numbers in relation to former imports? Or in relation to Russia's output? Or did you even notice that the article very much avoids to give any reference for their numbers in the first place?

Being obviously unable to annex Ukraine, not even in the planned few days but at all, did not stop them from continuing. But losing about 5% of their already failing economy that is now basically tailored to producing weapons for the war exclusively would totally have made them stop. Sure...

[-] Ooops@feddit.org 2 points 22 hours ago

Interesting... I get a different post on mobile than on desktop where the exact same link somehow leads me here WTF?

[-] Ooops@feddit.org 4 points 22 hours ago

An seine Stelle tritt die sogenannte Bio-Treppe ab 2029. "Schrittweise fährt man den Anteil von klimafreundlichen Brennstoffen hoch, bis man in die Klimaneutralität kommt".

Wie verwirrt (oder wahlweise korrupt) muss man sein, um dieses Märchen einfach so weiter zu erzählen, ohne die Miene zu verziehen? Es wird genauso wenig klimafreundliche Brennstoffe zum Heizen in benötigten Mengen geben wie eFuels zum Weiterbetrieb von Verbrennen, egal wie hart man Realität und Naturgesetze leugnet.

[-] Ooops@feddit.org 5 points 1 day ago* (last edited 1 day ago)

For example:

We have two storages (e.g., SSD): /dev/sda and /dev/sdb.

Install Windows on /dev/sdb (so it creates its own ESP);

Install Linux on /dev/sda (so it creates its own ESP), with a normal/manual partitioning:
- /boot/ (for Kernels I have 4 GiB+);
- /boot/efi/ (commonly, from 128 to 512 MiB is enough);
- Here I normally also have a swap partition, and separate: /home/, /var/;
- Select Grub to be installed on the /dev/sda;

Boot the Grub in /dev/sda;

Update Grub within Linux, so it finds the Windows EFI on another drive via its os-prober.

Here, I believe efibootmgr should show the existing EFI, or you could check it manually in /boot/efi after.

Windows should operate on its own ESP it created on its own storage, and don’t overwrite the Grub.

At voila!

Then Windows will fuck up your EFI entries. Which is not a big deal if you know what you are doing but a completely different story for the audience you are explicitly addressing here when you even explain how to check those entries in the first place.

Also you did not actually mention that fastboot needs to be disabled in Windows, thus a clueless person will not understand the random hardware errors on Linux caused by not properly initialized devices and will blame Linux.

(And let's not even talk about some of the really insane stuff like pre-installed Microsoft SecureBoot keys that brick you whole system when removed because idiotic OEMs signed their own hardware's EFI drivers with the keys already pre-installed just because they can...)

So no, it's not "quite odd to see so many people having the issue when Windows". That's what Windows is causing, often intentionally so. Is most of this easily fixable? Sure... But it's a very effective deterrent for many people, so they never reach the point where they understand and be able to fix that stuff.

[-] Ooops@feddit.org 3 points 1 day ago* (last edited 1 day ago)

Then Windows will fuck up the EFI entry itself. Easy to fix of course but a pain in the ass when you are just starting with Linux and have barely any idea other than reinstalling for the 10th time in a few weeks.

[-] Ooops@feddit.org 6 points 1 day ago

It is also really important to just be honest with where the German economy stands right now

Exactly where most of it stands for decades. It's based on constant lobbying of "We want back to the 1980 at the very latest. Give public money so we can refuse any innovation and adapt legislation to stifle any competition for us. Thx, here are some board meberships in exchange."

[-] Ooops@feddit.org 22 points 1 day ago

Welt-Pommes-Tag ist im August.

Der 13. Juli ist French-Fry-Day in den USA. Tun wir schon wieder so als wären die die Welt?

[-] Ooops@feddit.org 13 points 1 day ago

That's an improvement over always being the dedicated tech support anyway, no matter how often you explain to them that you have not bothered to take a look at Windows and all its specific issues for a decade or more...

[-] Ooops@feddit.org 11 points 1 day ago

What does "getting caught" mean? They do it quite openly with everyone knowing and zero real consequences.

35
submitted 1 month ago by Ooops@feddit.org to c/unixporn@lemmy.world

25
submitted 3 months ago* (last edited 3 months ago) by Ooops@feddit.org to c/selfhosted@lemmy.world

As this will -thanks to me being quite clueless- be a very open question I will start with the setup:

One nginx server on an old Raspi getting ports 80 and 443 routed from the access point and serving several pages as well as some reverse proxies for other sevices.

So a (very simplified) nginx server-block that looks like this:

# serve stuff internally (without a hostname) via http
server {
	listen 80 default_server;
	http2 on;
	server_name _; 
	location / {
		proxy_pass http://localhost:5555/;
                \# that's where all actual stuff is located
	}
}
# reroute http traffic with hostname to https
server {
	listen 80;
	http2 on;
	server_name server_a.bla;
	location / {
		return 301 https://$host$request_uri;
	}
}
server {
	listen 443 ssl default_server;
	http2 on;
	server_name server_a.bla;
   	ssl_certificate     A_fullchain.pem;
    	ssl_certificate_key A_privkey.pem;
	location / {
		proxy_pass http://localhost:5555/;
	}
}
#actual content here...
server {
	listen 5555;
	http2 on;
    	root /srv/http;
	location / {
        	index index.html;
   	} 
    	location = /page1 {
		return 301 page1.html;
	}
    	location = /page2 {
		return 301 page2.html;
	}
        #reverse proxy for an example webdav server 
	location /dav/ {
		proxy_pass        http://localhost:6666/;
	}
}

Which works well.

And intuitively it looked like putting Anubis into the chain should be simple. Just point the proxy_pass (and the required headers) in the "port 443"-section to Anubis and set it to pass along to localhost:5555 again.

Which really worked just as expected... but only for server_a.bla, server_a.bla/page1 or server_a.bla/page2.

server_a.bla/dav just hangs and hangs, to then time out, seemingly trying to open server_a.bla:6666/dav.

So long story short...

How does proxy_pass actually work that the first setup works, yet the second breaks? How does a call for localhost:6666 (already behind earlier proxy passes in both cases) somehow end up querying the hostname instead?

And what do I need to configure -or what information/header do I need to pass on- to keep the internal communication intact?

view more: next ›

Ooops

0 post score
0 comment score
joined 2 years ago