sorted by: new top controversial old
PackageKit - Typical User Profiles in c/linuxmemes@lemmy.world
AfD’s Alice Weidel to unveil plan to downsize the EU in c/europe@feddit.org
[–] 1 point 3 hours ago*

it doesn’t mean that everyone who dislikes the EU is a MAGA republican or Russian bot

No, but 99 out of 100 times someone disliking the EU and then whining about "bottle caps" and "paper straws" got their talking points from one of those bots directly or from one of the far-right culture-war bullshit influencers who get their instructions from the same source. Because that's one of their popular topics, which is not surprising given that any actually substantial criticism of the EU would need more context, basic political understanding and in-depth reasoning than what those propaganda tools just pushing simpke narratives allow.

  • permalink
  • fedilink
  • source
  • parent
  • context
    • Informationsfreiheitsgesetz: Regierung hat keine Belege für angebliche Gefahren in c/dach@feddit.org
    What Linux distros feature a graphical update tool by default? in c/linux@lemmy.ml
    [–] 1 point 3 hours ago* (last edited 3 hours ago)

    When config files change with an update pacman writes the new one as a .pacnew file instead of overwriting the existing one. That's always an issue with updates on config files (although one less severe on slow updating distros). Do you keep the old config to keep your changes intact while ignoring new default options that should be in there or do you replace the old config with a recent one but risk using manual edits?

    pacdiff basically just searches for .pacnew files and then queries you what to do with each.

    You can define a viewer via a DIFFPROG= variable (I simply use vim -d because that's already my editor of choice but the package pulls diffutils as a dependency so just diff works, too) and compare the new default config file with the existing one side-by-side (with differences highlighted), so you can either copy your personal edits to the new one or copy additional or changed default options to your old one, whatever is easier. After that you have the option to dismiss/delete the .pacnew file or rename it to replace the old one.

    PS: pacdiff is part of the pacman-contrib package. That package also provides checkupdates.

    Running pacman -Syu updates your package list to the recent one, then updates all your outdated packages. You are not actually supposed to update the list, then abort the update of packages or just update some of them because Archlinux always assumes up-to-date systems (see: unsupported partial upgrades). So pacman should not be used to just check for available updates without updating. That's where checkupdates comes in, simulating pacman -Syu without actually touching your system and just getting a list of available updates.

    PPS: the AUR has a similiar aur-check-updates tools to do the same for AUR packages.

  • permalink
  • fedilink
  • source
  • parent
  • context
    • Qnetic testing flywheel to compete with lithium-ion for grid-connected energy storage in c/energy@slrpnk.net
    [–] 3 points 10 hours ago* (1 child)

    "If flywheels seem like an exotic energy storage solution, that’s largely because they have generally been relegated to niche applications. A spokesperson for Qnetic told pv magazine USA that grid-connected flywheel pioneer Beacon Power deployed 400 of its 100 kW (25 kWh) units at two utility sites in New York and Pennsylvania between 2011 and 2014 to provide fast-responding frequency regulation. Each location had 200 units with a nameplate capacity of 20 MW (5 MWh), and both are still providing frequency regulation service and generating revenue."

    I would assume that flywheels are exotic because their niche (short- to mid-term storage, quick reaction times) wasn't much needed so far in a grid dominated by non-renewables. This will probably change in the future.

    But for the same reason I don't get all that talk about competing with lithium-ion batteries. Flywheels don't really fit the same category as batteries. And lithium-ion batteries in particular are not well suited for grid-level storage anyway. Their benefit at the moment is basically just availability because that's the type of battery that was produced and optimised at scale for –at least– the last decade.

  • permalink
  • fedilink
  • source
    •
    Abkehr vom Verbrenner-Aus: Unterhändler im Europaparlament finden Kompromiss in c/dach@feddit.org
    Abkehr vom Verbrenner-Aus: Unterhändler im Europaparlament finden Kompromiss in c/dach@feddit.org
    [–] 3 points 11 hours ago*

    Du versteht das falsch herum. Der Verbrennerverkauf und die damit verbundene weitere Vernachlässigung von Elektroautos wird DER Grund sein, warum sie nicht wirtschaftlich erfolgreich sind. Denn wenn man nicht in den nötigen Stückzahlen baut und keine eigene Versorgungskette aufbaut, sondern nur die Teile bei der Konkurrenz kauft, kann man halt langfristig zumachen. Oder –wie es unsere Unternehmen versuchen werden– laut heulen, damit stattdessen der Staat einen finanziert, um die mutwillig gefährdeten Arbeitsplätze zu erhalten.

  • permalink
  • fedilink
  • source
  • parent
  • context
    • tja in c/tja@feddit.org
    What Linux distros feature a graphical update tool by default? in c/linux@lemmy.ml
    [–] 4 points 12 hours ago*

    All the Archlinux based ones, too. (Although I don't accept the buggy mess that is Manjaro's Pamac as an actual tool.)

    The only way to get a distro with no graphical updater by default nowadays is using one that does not come with a graphical desktop by default (so archlinux and some server installations...).

  • permalink
  • fedilink
  • source
  • parent
  • context
    • What Linux distros feature a graphical update tool by default? in c/linux@lemmy.ml
    [–] 5 points 12 hours ago* (last edited 3 hours ago) (3 children)

    As the "graphical update tool" is just a basic wrapper for the normal updater, I would be very surprised if any distro coming with a desktop environment by default has none...

    So the answer would be "every single one but Archlinux (nothing by default but the base system) and server installations"

    (PS: My "graphical" updater on Archlinux is a handful of very small scripts that a) runs checkupdates and flatpak remote-ls --updates from time to time writing the result into a temp file, b) displays an indicator if that file isn't empty, c) prints out the file as a notification on clicking that indicator and d) runs pacman -Syu && paru -Syu -a && flatpak update && pacdiff in a terminal window when I right click the notification.)

    (PPS: Small correction... Manjaro doesn't have graphical updater but a buggy abomination prone to fucking the AUR instead.)

  • permalink
  • fedilink
  • source
    •
    Frankreich-Proteste: "Macron hat nicht die richtigen Antworten gefunden" in c/europa@feddit.org
    [–] 3 points 12 hours ago* (1 child)

    Die wahnhafte neoliberale Zerstörung von Sozialstaat und Zivilgesellschaft, um möglichst alles zu privatisieren, damit auf Kosten der Mehrheit eine Hand voll überreicher Menschen noch viel reicher werden kann, hat keine Lösungen für die Zerstörung von Sozialstaat und Zivilgesellschaft bei gleichzeitiger ständiger Enshittification durch Privatunternehmen und Verarmung fast aller und den daraus resultierenden gesellschaftlichen Widerstand und Protest gefunden?

    Wie kann das nur sein???

    (Oder wie es hierzulande gerne als "Lösung" erschallt: "Wir müssen die 'Reformen' nur radikaler durchdrücken, dann versehen die idiotischen Wähler es sicher auch!")

  • permalink
  • fedilink
  • source
    •
    Bund unterzeichnet KI-Absichtserklärung mit Chiphersteller Nvidia in c/dach@feddit.org
    [–] 6 points 17 hours ago

    Tagtäglich zum eignen Vorteil Entscheidungen gegen Deutschland treffen, während die Wählerherde so verdummt wurde, das sie immer noch ständig von Dummheit oder Inkompetenz redet, statt von Bosheit und Korruption, ist durchaus beeindruckend.

  • permalink
  • fedilink
  • source
  • parent
  • context
    • 25
    Need some ELI5 on proxy_pass in Nginx, in particular regarding having Anubis in the chain (feddit.org)
    submitted 6 months ago* (last edited 6 months ago) by to c/selfhosted@lemmy.world
    11 comments fedilink
     

    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 ›