NB John Nielsen har lavet en artikel om samme sag.

LTT video:

Transcript behandlet i mistral: Her er teksten delt op i pæne afsnit og let redigeret, så overgangslyde og transcript-markeringer (">>", gentagelser osv.) er ryddet væk:

En AI-klon af Photoshop vækker opsigt

So, I'm lying in bed last night and my phone absolutely blows up with everyone talking about the same thing: there's an AI clone of Photoshop that is basically feature complete, costs $70 one time, and works across Windows, Mac, and Linux.

My initial reaction was: yeah, sure, I've heard that before. But then I dug a little deeper, and my whole perspective changed. This isn't another basic "Claude, make me my own version of Photoshop with some basic tools X, Y, and Z." And it's not just Photoshop. Through what appears to be a combination of decompiling original applications and straight-up vibe coding, we're seeing projects as diverse as free clones of the entire Adobe Creative Suite to game mashups — where you can rip around on a skateboard in Modern Warfare 2, or play a hardcore Tarkov-style extraction shooter in the world of Skyrim.

Piracy eller fremskridt?

Naturally, this has resulted in an eruption of opinions. Some have been quick to condemn it as piracy, while others have called it a natural step in the evolution towards a future where paid proprietary software is dead and AI-assisted open source reigns supreme. What everyone agrees on, though, is that nothing will ever be the same again.

However, I feel like we might have skipped over an important point here. However this software is made — whatever the moral, ethical, and legal ramifications — none of this matters if these apps are not usable. I mean, Lord knows they're not likely to be maintained. So, I did the right thing and bought the $70 Photoshop clone everyone's talking about.

Wait — it's free now, as of filming. That changed in the last three hours. That's how fast things are moving right now. And the point is: free or $70, I tasked some of our professional users with trying to use this software. And whoa.

Første indtryk hos vores testere

"Oh, that's very slow to open. Just importing the images took a lot longer than usual. With Photoshop it's pretty much instant — this actually had to take a second to load. It seems like Photoshop is a little more well-tuned, right from the get-go."

"Immediately — I've been using this for 5 seconds — it is good enough for me to not notice an immediate difference. The menus… are they supposed to be just like Photoshop's? They seem very similar, if not the same."

"We're getting all sorts of errors. Game over. As someone who would be doing this professionally, having to wait this long for every tweak? I just wouldn't use it."

Hvordan laver man den slags software?

The first question that's got to be on your mind is: what is happening here? There are two main ways to build this kind of clone software.

The first, and the most complete, is decompilation. You take the binary code — the ones and zeros that run on your machine — and turn it back into the kind of human-readable source code that the original developer used. It won't be exactly the same code, but if it swims like a duck and quacks like a duck, it is, for all user purposes, a duck.

Traditionally, decompilation has been extremely labor-intensive and tedious, which made it only make sense for very small projects, very important projects, or very obsessed developers. But AI has completely changed the game. You can tell your AI: "Take this gobbledegook of ones and zeros, of machine instructions with no comments, and turn it back into the source code that created it" — and it'll churn away on it surprisingly effectively, for as long as your bank account allows before it's drained of credits.

It's worth noting, though, that not all types of decompilation are the same. Kingy has a great blog post outlining the different kinds of things we call decompilation, and it's arguable that what Photon Studio is using is probably closer to functional reconstruction — where the new AI-generated source is intended to reproduce the same behavior as the original software, but has completely different bytes from the original source code. So really, it's more like AI slop with an original program as part of the input.

Test af de avancerede funktioner

"We got object selection, quick selection, magic wand… finding objects. That's the one I want. That worked pretty good."

"I usually don't rely on 'select subject' to do the crop 100%, but it gives a good starting point. I'd say that did a pretty good job — it lost the hat a little bit. Photoshop did a lot better with the hat. Right off the hop, Photoshop's automatic selection is so much cleaner. This requires almost no work from me on the Photoshop side; on the other one, a lot of work."

"That is literally the only reason I have subscribed to Photoshop: cutting out subjects from the background."

There were oddities, too: when selecting a subject, the clone grabbed parts of the image underneath the selected layer — something Photoshop doesn't do. RAW editing also fell short: raising shadows with the dedicated slider didn't come anywhere near what Photoshop's exposure adjustment alone could do, and the color mixer either wasn't working or was taking forever to update its preview. Layer moves showed the position updating while the image itself lagged behind, and right-clicks froze the app entirely.

Er det overhovedet lovligt?

Okay, so your next question's got to be: well, this is illegal, right? Maybe, maybe not.

One of the most interesting cases of software reverse engineering didn't even involve decompilation. I'm talking about the time Phoenix Software kicked off the affordable clone-PC revolution by creating an IBM-compatible BIOS without infringing on any of IBM's original source code. They did this by painstakingly studying and documenting the source listings in the IBM PC technical reference manual, then tasking a separate engineer — who had never read the original — with creating their own code that mimicked the APIs. Notably, this was deemed legal because the engineer who wrote it had never seen the source code, and therefore couldn't have stolen it.

Legal carve-outs for reverse engineering software remain to this day. Could that apply here? In the Phoenix case, it didn't matter how similar the result was to the original code, if the writer had never seen it. And the AI has never seen the original source code — at least, not that the data aggregators who created it would ever admit. But patent and copyright law can apply to functions and ideas as well, and all of this varies from one jurisdiction to another anyway. At best, we're in very murky waters.

Konklusion: "I can't believe it's not Photoshop"

So, now that our testers had fiddled with Photoshop and "not-Photoshop" — overall impressions?

"A lot more similar than what I was expecting. 'I Can't Believe It's Not Photoshop' is a good label."

"Hey man, if you want to do Photoshop stuff and you ain't got no money — this is a great alternative."

"I hate how much Photoshop costs. I've been trying Affinity, I've been trying Photomator. When I saw these popping up, I was like: maybe this is it. This one looks really nice — but I feel like it needs a year of tweaks."

Probably the biggest thing to keep in mind in all of this: while we focused on Photon Studio for our own selfish purposes — I hate giving Adobe money as much as anyone, and I would love a $70, excuse me, free alternative — there are numerous other similar projects, some individual efforts, some from groups attempting to do the same thing. Notably, the reaction to them has been more receptive than I expected, given the generally anti-AI stance of the creative community.

It's clear, then, that Adobe's memeworthy quality and ruthless subscription-only model has done enough to antagonize their customers that numerous creators are looking for the exit — even if that means being driven into the arms of Big AI. This is not financial advice, and I probably won't do it, but let me put it this way: I asked my wife today if she knows how to short a stock.

Original rtranscript (via youtube-transcript.io)

So, I'm lying in bed last night and my phone absolutely blows up with everyone talking about the same thing. >> There's an AI clone of Photoshop that is basically feature complete, cost $70 one time, and works across Windows, Mac, and Linux. >> Initial reaction, yeah, sure, I've heard that before. But then I dug a little deeper and my whole perspective changed. This isn't another basic Claude, make me my own version of Photoshop with, I don't know, some basic tools X, Y, and Z. And it's not just Photoshop. Through what appears to be a combination of decompiling original applications and straightup vibe coding, we're seeing projects as diverse as free clones of the entire Adobe Creative Suite to game mashups where you can like rip around on a skateboard in Modern Warfare 2 or play a hardcore Tarov style extraction shooter in the world of Skyrim. Naturally, this has resulted in an eruption of opinions. Exactly. Some have been quick to condemn it as piracy, while others have called it a natural step in the evolution towards a future where paid proprietary software is dead and AI assisted opensource reigns supreme. What everyone agrees on though is that nothing will ever be the same again. However, I feel like we might have skipped over an important point here. However this software is made, whatever the moral, ethical, and legal ramifications, none of this matters if these apps are not usable. I mean, Lord knows they're not likely to be maintained. So, I did the right thing and I bought the $70 Photoshop clone that everyone's talking about. Wait, it's free now as of filming. That changed in the last three hours. That's how fast things are moving right now. And the point is, free or $70. I tasked some of our professional users with trying to use this software and whoa. Hopefully that's just a bug >> immediately. It is good enough for me. >> We're getting all sorts of errors. >> Game over. Like there's I just I wouldn't use it. >> Enjoy. Also enjoy the segue to our sponsor. >> Threat Locker. They make adopting a zero trust framework easier for businesses to navigate and their flagship event Zero Trust World is coming in February. Learn more about Zero Trust World and secure your tickets with the link below. >> Oh, that's very slow to open. Just importing the images in that took a lot longer than usual. Like with Photoshop, it is pretty much instant. This actually had to take a second to load. It seems like Photoshop is a little more welltuned, I would say, right from the get- go. >> Okay, this one just straight up doesn't open. Okay, well, I guess I got to do the the kimono dragon instead. Immediately, I've been using this for 5 seconds, but immediately it is good enough for me to not notice an immediate difference. >> So, the menus, are the menus supposed to be just like Photoshop 2? They seem very similar, if not the same. >> The first question that's got to be on your mind is what is happening here? And there's two main ways to build this kind of clone software. The first and the most complete is decompilation. In this case, you take the binary code, the ones and zeros that run on your machine, and you turn that back into the kind of human readable source code that the original developer used. It won't be exactly the same code, but if it swims like a duck and quacks like a duck, it is for all user purposes a duck. This is so weird. >> Let's give him Terren's eyes. >> Terren's eyes. You know what? This doesn't have to be a perfect job. Oh god, what have we done? What have I done? Dude, this is so cursed. >> It's Italic. Cut out Llin as his head. >> There we go. >> Perfect. >> Oh, there we go. >> Wow. >> Oh, wait. Wait. Where's his eyes? Oh, no. This is not a tearing tongue. Now decompilation traditionally has been extremely labor intensive and tedious making it only make sense for very small projects, very important projects or very obsessed developers. But AI has completely changed the game here. You can tell your AI, hey, take this gobbledegook of zero and one machine instructions with no comments and then try and turn it back into the source code that created it. and it'll sit and churn away on it surprisingly effectively for as long as your bank account allows before it's drained from all the credits you're consuming. It's worth noting though that not all types of decompilation are the same. Kingy has a great blog post outlining some of the different kinds of things that we call decompilation and it's arguable that what photon studio is using is probably closer to functional reconstruction where the new AI generated source is intended to reproduce the same behavior as the original software but has completely different bites from the original source code. So really, it's more like AI slop with an original program as part of the input. >> We got object selection, quick selection, magic wand. Finding objects. That's the one I want. That worked pretty good. >> Usually don't rely on the select subject to do the crop 100%, but it usually gives like a good starting point. And I'd say that did a pretty good job. It lost the hat a little bit. Yeah, Photoshop did a lot better with the hat. I will say right off the hop the Photoshop like automatic selection so much cleaner. Like this requires like almost no work from me on the Photoshop side. On the other one a lot of work. >> That is literally the only reason that I have subscribed to Photoshop is for cutting out subjects from the background. >> Okay, that that's interesting. When you do the select subject or whatever, uh it'll usually just do like whatever layer you have selected. This one has grabbed some of the image underneath, which I don't at least I don't remember Photoshop doing that. Okay, so your next question's got to be, well, this is illegal, right? Well, maybe, maybe not. One of the most interesting cases of software reverse engineering to me right now didn't involve decompilation. I'm talking about the time that Phoenix Software kicked off the affordable clone PC revolution by creating an IBM compatible BIOS without infringing on any of IBM's original source code. They did this by painstakingly studying and documenting the source listings in the IBM PC technical reference manual, then tasking a separate engineer who had never read the original with creating their own code that mimicked the APIs. Notably, this was deemed to be legal because the engineer who wrote it had never seen the source code and therefore couldn't have stolen it. And legal carveouts for reverse engineering software do remain to this day. Could that apply here? It was found in that case that it didn't matter how similar the result was to the original code if the writer had never seen it. And well, the AI has never seen the original source code. At least not that the data aggregators who created it would ever admit. But then also patent and copyright law can apply to functions and ideas and all of this varies from one jurisdiction to another anyway. So at best we're in very murky waters right now. So Ree, you discovered something super interesting about this. When you were raising and lowering the exposure dial. >> Yeah, >> cuz these are both taken in RAW. You should be able to bring up the shadows just like this. >> Yeah. So, if I if I try to do it even there, even if I use the shadows uh slider, it doesn't even bring up the shadows anywhere near where the even just the exposure on Photoshop can can do. >> It's got a color mixer that's always uh extremely handy. >> Yeah. Is that grabbing the correct colors that you expect it to grab? >> It's either not doing it or it's taking forever. Updating preview down here. So, doesn't seem like the color mixer is working that well. Uh Whoa, that's okay. I'm guessing hopefully that's just a bug. So, like this. I'm selecting my face layer right now. I'm There we go. I'm moving it around. It is moving the position of the image, but the actual image itself is not updating. It's like lagging behind. Wow, that was crazy lag. I right clicked and it just was a while until it click. I' I've clicked. I've rightc clicked. There it is. as like someone who would be doing this professionally having to wait this long for every tweak. Game over. Like there's I just I wouldn't use it. >> Okay, so now that you fiddled with Photoshop and not Photoshop overall impressions >> a lot more similar than what I was expecting. Uh and I mean I I think the I can't believe it's not Photoshop is a is a good label. >> Hey man, if you want to want to do Photoshop stuff and you know you ain't got no money. >> No, I think this is a great alternative. >> Yeah. Yeah, >> I hate how much Photoshop costs. I've been trying Affinity. I've been trying Photomator. When I saw these popping up, I was like, maybe this is it. But this this one here, well, it looks really nice. Maybe it I feel like it needs like a year of tweaks. Probably the biggest thing to keep in mind in all of this is that while we decided to focus on Photon Studio for our own selfish purposes, I hate giving Adobe money as much as anyone, and I would love a $70, excuse me, free alternative. There are numerous other similar projects. some individual efforts, some from groups that are attempting to do the same thing. And notably, the reaction to them has been more receptive than I expected given the generally anti-AII stance of the creative community. It's clear then that Adobee's memeworthy quality and ruthless subscription only model has done enough to antagonize their customer group that numerous creators are looking for the exit, even if that means they're going to be driven into the arms of big AI. This is not financial advice and I probably won't do it, but let me put it this way. I asked my wife today if she knows how to short a stock. Now for a short segue to our sponsor, >> Threat Locker. With AI deploying into workplace, new vulnerabilities and exploits being discovered daily, and the speed at which cyber security landscape is changing, it's important to continue to stay on top of how you can keep your business secure. At Zero Trust World, Threat Locker's flagship event, there will be hands-on labs, deep dives into today's most pressing topics, and plenty of opportunities to connect and learn from other cyber security professionals. We've gotten to attend and speak at zero trustworld and the conference continues to grow every year. The sessions are eligible for continuing education credits and attendees will leave with the knowledge and skills to implement zero trust in their organization or get firstirhand experience at a hacking lab going to see how exploits work and how to prevent them. Learn more about zero trust world and secure your tickets with the link in the description. The afterparty is one you don't want to miss. >> You guys enjoyed this video? Why not check out the last time we looked at how much we're paying Adobe and tried to find an alternative? It was a while ago, but it was tough.

Video by Alex Antic:

https://www.facebook.com/reel/1059873890017722

In our once free country, you used to own the things you paid for and didn’t live your life on subscription. The digital prison is closing in. Not just in Australia but globally. Once it’s complete, your freedom will rely on your compliance to big government and big tech who will control the off switch to your participation in society. To hear more from me and stay up to date, signup to my email newsletter here: http://alexantic.com.au/join

Audio transcription

Transcription: Digital Feudalism

(Teksten er bevaret ordret og ikke oversat.)

There's a quiet revolution that's transforming free citizens into something far less free. We're being controlled and we're being turned into vassals, not by armies or kings in the old sense, but by a modern form of digital feudalism that strips ordinary Australians of ownership and makes them permanent renters in their own lives.

It's happening in every aspect of our lives and it even now extends to the physical ownership of shattles.

Consider what's happening, what's already happened in a single generation. Let's take music for example. Compact discs and DVDs sat on our shelves available whenever we chose, but they're being replaced by streaming services that can remove content, raise prices and lock us out at will. Software we once bought and owned forever has now turned into a perpetual subscription. Memory cards and hard drives once owned forever are now being replaced by cloud storage that we must rent every month.

It's not progress, it's the systematic transfer of ownership from the individual to distant corporations and increasingly to an administrative state that partners with them.

In the feudal system, vassals didn't own the land, it was held at the pleasure of the Lord subject to conditions, fees and the constant risk of forfeiture. Today the digital Lord collects the rent in monthly installments and retains the power to revoke access with a single keystroke and that pattern is spreading. Motor vehicles now are increasingly software locked, platforms that property we don't truly control. Works, tools and even data of our own lives has been converted into services that we never actually finally progress.

Now we're told it's modern and efficient, but in truth it's a profound shift in the relationship between individuals and the things that sustain independent life.

Ownership has always been central to a free society and the man who owns his tools, his home and the products of his labour answers first to himself and to his family. The man who merely rents them answers to the landlord. The landlord is a handful of global tech companies, often working hand in glove with governments keen on digital identity systems and programmable money.

The risk is no longer theoretical, it's structural. Australians have already seen the early stages of this control architecture, the push for digital ID, expansion of surveillance powers, the quiet preparation for programmable central bank digital currencies and if you pair those tools with a population that no longer owns its own goods, you have created the perfect condition for modern surfdom. Compliance becomes the price of continued access, descent can be met with deplatforming account suspension or the simple withdrawal with a digital key.

And not that long ago property rights and the dignity of ownership weren't just optional extras, they were the foundation of personal independence and national sovereignty. We're now being invited to trade that inheritance for the temporary convenience of never having to manage our own affairs.

Well I reject that bargain and Australians should be able to buy things once and own them. They should be able to store them on their own data without paying rent to a foreign server farm. They should be able to drive a car without seeking permission from a software update and they should be able to participate in the digital world without surrendering the fundamental right to own rather than to merely access.

We are sleepwalking into a society of permanent renters dependent on the good will of corporate and bureaucratic overlords. And I know which side I'm on. The question is whether this parliament and this government has the will to protect us from it.

WPD.app: Det ægte Privacy Dashboard til Windows – og hvordan det skiller sig ud fra Microsofts

Søger du efter "WPD" eller "Windows Privacy Dashboard", rammer du to helt forskellige ting: det lille, uafhængige værktøj WPD fra wpd.app – og Microsofts egen webbaserede Privacy Dashboard på account.microsoft.com. De deler navn, men de gør fundamentalt forskellige ting for din privatlivsbeskyttelse. I dette opslag kigger vi på forskellen, fremhæver styrkerne ved WPD.app – og ser nærmere på, hvor Microsofts tilgang i værste fald lugter af privacy-washing.

Hvad er WPD.app?

WPD – i daglig tale "Windows Privacy Dashboard" – er en lille, men kraftfuld portabel privatlivsværktøj til Windows, udviklet uafhængigt af Microsoft. Det fylder kun omkring 335 KB i zip-format og kræver ingen installation: du pakker det ud og kører det (wpd.app).

Programmet arbejder direkte gennem Windows' egne API'er – Group Policy, Services og Task Scheduler – og er bygget omkring tre moduler (Neowin):

• Privacy: central oversigt over de gruppepolitikker, tjenester og planlagte opgaver, der styrer dataindsamling og -transmission – telemetri, Advertising ID, Customer Experience Improvement Program, Cortana, input-personalisering m.m.
• Blocker: firewall-regler, der blokerer Microsofts telemetri-IP-adresser (baseret på det velkendte @crazy-max-regelsæt) – og eventuelt også opkald fra Skype, OneDrive, Bing og Office samt Windows Update.
• Apps: en Appx-afinstallerer, der fjerner forudinstallerede Store-apps i én håndbevægelse – Feedback Hub, Get Office, Xbox osv.

Hvert enkelt indstilling har en lille forklaring ved markøren, så man ved, hvad man ændrer, før man ændrer det. Det hele kan rulles tilbage, og WPD opretter gerne et systemgendannelspunkt, inden der rodes med indstillingerne (Hacking Articles). Værktøjet er gratis, men bemærk: det er ikke open source (Awesome Privacy).

Udviklerne er usædvanligt ærlige om begrænsningerne: "Der findes intet værktøj, der kan slå datalæk i Windows 10 helt fra – WPD deaktiverer kun de vigtigste ting, men ødelægger ikke systemet" (CNET Download). Den slags ydmyghed finder man ikke i marketingmaterialet hos dem, der byggede systemet.

Hvad er Microsofts "Privacy Dashboard"?

Microsofts modstykke er en webbaseret dashboard, du når via din Microsoft-konto. Her kan du se, slette og administrere de data, Microsoft har samlet om dig, mens du var logget ind: Bing-søgninger, Microsoft Copilot, Edge-browsing, lokationshistorik, aktivitetshistorik og annonceindstillinger på tværs af Windows, Xbox, Microsoft 365 og Copilot (Microsoft Privacy Report).

Det er et pænt og funktionelt overblik – men læg mærke til, hvad det reelt set er: et vindue ind til data, der allerede er blevet samlet og sendt hjem. Ændringer går kun én vej; man kan slette data, men ikke forhindre selve indsamlingen dérfra (TheWindowsClub).

Sammenligning: WPD.app vs. Microsofts Privacy Dashboard

Styrkerne ved WPD.app

1. Forebyggelse frem for skaderens. WPD stopper datastrømmen ved kilden: tjenester, planlagte opgaver og firewall-regler. Microsofts dashboard lader dig derimod rydde op efter, at dataene er rejst.
2. Ét sted, ét overblik. Windows' privatlivsindstillinger er berømt spredt over dialogbokse, registernøgler og phone-home-tjenester; WPD samler det hele i ét vindue (MSPowerUser).
3. Ingen konto, ingen sky. Værktøjet kører lokalt og kræver ikke, at du skaffer dig en Microsoft-konto – i sig selv en privatlivsforbedring.
4. Transparent og reversibel. Forklaringer ved hver indstilling, gendannelspunkter og mulighed for at genaktivere alt. WPD er designet til ikke at ødelægge systemet (Neowin).
5. Netværksblokering. Firewall-modulet rammer telemetri, hvor den reelt sker: netværkstrafikken – også til Microsofts tredjeparts-apps som Skype og OneDrive (gHacks).
6. Debloating som bonus. Fjernelsen af forudinstallerede apps gør Windows både renere og mere privat – og sparer ressourcer.
7. Ærlig kommunikation. Udviklerne lover ikke "total privacy" – de siger, hvad værktøjet kan, og hvad det ikke kan (CNET Download). Det er mere, end Windows' egen privatlivskommunikation kan sige.

Hvor Microsofts WPD kan lugte af privacy-washing

"Privatliv er vigtigt for os – vi værner om og forsvarer dit privatliv." Sådan lyder tonen i Microsofts Privacy Report (Microsoft Privacy Report). Men dashboardets design rejser nogle fair spørgsmål:

• Transparens i stedet for privatliv. Dashboardet viser dig hvor meget der er samlet – men gør intet for at reducere selve indsamlingen. At vise data for en "betroet part" er ikke det samme som at lade være med at samle dem. Det er selve definitionen på privacy-washing: at kommunikere om privatliv i stedet for at levere det.
• Retrospektiv kontrol. Du kan slette din Edge-historik, dine Bing-søgninger og din lokationshistorik – men kun én ad gangen eller alt på én gang, og du lærer ikke noget om, hvorfor det blev samlet, mens du ikke havde slået det fra (TheWindowsClub).
• Kontoen er en betingelse. Dashboardet gælder kun for data bundet til din Microsoft-konto. Kører du med en lokal konto, eller slettes data på tværs af enheder, er der meget, dashboardet ikke viser (Microsoft Support).
• Indsamlingen vokser. Mens dashboardet signalerer omsorg, tilføjer Microsoft løbende nye dataindsamlende funktioner til Windows – senest AI-funktionerne Recall og Click to Do, som nu er dokumenteret i privatlivserklæringen (Microsoft Privacy Statement – ændringshistorik). Dashboardet følger trop med nye datakilder som Copilot – transparensen vokser altså i takt med selve overvågningen.
• Indstillinger, der bliver ved med at vende tilbage. Erfaringer viser, at funktionsopdateringer og gruppepolitikker kan genaktivere indstillinger, brugeren eksplicit har slået fra (Position Is Everything). Et dashboard, der reelt respekterede dine valg, ville låse dem fast – ikke overskrive dem ved næste opdatering.
• De lokale indstillinger er bevidst spredt. Selve Windows' privatlivsindstillinger ligger stadig spredt over utallige menuer og skærme (Rick's Daily Tips) – hvilket er den direkte grund til, at WPD overhovedet eksisterer. Microsoft centraliserer visningen af data (i skyen), men ikke kontrolen over indsamlingen (på din PC). Det er et bevidst valg.

Anbefalinger

De to værktøjer udelukker ikke hinanden – de løser hver sin opgave:

1. Brug WPD.app til at forebygge: slå telemetri fra, bloker telemetri-IP'er, fjern bloatware – og opret et gendannelspunkt først.
2. Brug Microsofts dashboard til at rydde op: log ind, gennemgå aktivitetshistorik, lokationshistorik, annonceindstillinger og slet, hvad du ikke vil have liggende i skyen.
3. Vær realistisk: intet værktøj lukker samtlige datalækager i Windows (CNET Download), og efter store funktionsopdateringer bør du tjekke, om dine indstillinger har overlevet (Position Is Everything).

Konklusionen er enkel: Microsofts Privacy Dashboard giver dig et indblik i dit dataaftryk – WPD.app giver dig et værktøj til at begrænse det. Én af dem er et spejl, du kan se din datastrøm i; den anden er en hane, du kan skrue for. Gæt, hvilken der faktisk er et dashboard for privatliv.

Kilder

• WPD – officiel hjemmeside
• WPD-funktioner gennemgået – Neowin
• WPD-anmeldelse med Blocker-modulet – gHacks
• WPD som "det rigtige privacy dashboard" – GIGAZINE
• WPD er gratis, men ikke open source – Awesome Privacy
• Udviklernes egne ord om begrænsninger – CNET Download
• Microsoft Privacy Report
• Microsofts privatlivserklæring – ændringshistorik (Recall/Click to Do)
• Microsofts dashboard kræver konto-login – Rick's Daily Tips
• Dashboardet er "envejs" – TheWindowsClub
• Windows' spredte privatlivsindstillinger – Rick's Daily Tips

Hvad hvis fjernarbejde kunne være lige så sikkert som med bigtech – uden at betale bigtech?

Mens andre virksomheder låser sig fast i dyre, lukkede platforme (Entra, Zscaler, Cisco, Citrix …), findes der en anden vej: en komplet, gennemtestet arkitektur bygget på 100 % open source – med SUSE Linux som fundament og moderne zero trust-principper som sikkerhedsmotor.

I denne referencearkitektur viser jeg, hvordan I kan:

• 🔐 Erstatte VPN-boksen med WireGuard-mesh – kryptering og portscans simpelthen afvist
• 🪪 Fjerne phishing-truslen med FIDO2-nøgler, TOTP og Keycloak-SSO
• 💻 Få Styr på hver eneste bærbar automatisk med Salt og Uyuni – ingen patch, ingen adgang
• 🇪🇺 Opnå digital suverænitet – kontrol over al trafik og ingen trafik, data eller logs i udenlandske skyer

Alt sammen med kode, I selv kan læse, ændre og eje. Ingen vendor lock-in. Ingen per-seat-regninger. Ingen lukkede døre.

👉 Læs hele arkitekturen, diagrammet og implementeringsplanen: *Sikker fjernadgang med åben kildekode – en SUSE-baseret referencearkitektur *

Sikkerhed handler ikke om, hvem der har bygget låsen, men om hvem der har nøglen. Den skal være din !

Der sidder nok en ARM-chip tættere på dig, end du tror.

Måske i din kaffemaskine. I din 3D-printer. I den boks ved fjernsynet, der filtrerer hele familiens internet for reklamer, uden at du tænker over det. Og i nat – uden at du bemærker det – kører de samme slags chips i nogle af verdens største datacentre og streamer dine serier, dine backups og dine Teams-møder.

Vidste du ...

• at en computer på størrelse med et kreditkort kan erstatte både annonceblokering, VPN og hjemmeautomation – for få "strømpenge" om måneden?
• at din 3D-printer sandsynligvis har to hjerner: én der tænker (Raspberry Pi) og én der reagerer (ARM-mainboard)?
• at ARM i dag matcher x86 på næsten alt – Docker, Kubernetes, ja selv Ceph-lagring – mens den bruger en brøkdel af strømmen?

Fra hobby-bord til verdensdominans

Det startede som et britisk eksperiment i lavt strømforbrug. I dag er ARM den mest udbredte processorarkitektur på planeten – fra mikrocontrollere til to kroner til 128-kernede serverkræfter, fra kaffeautomater til robotplæneklippere, fra børns første kode-projekt til industrins kvalitetskontrol med AI.

Fællesnævneren: maksimal ydelse per watt. Og det ændrer alt – for din elregning, for industrien og for planetens datacentre.

OG i de fleste systemer sidder der OpenSource/Linux!

Læs den fulde tekniske beskrivelse for at få overblikket over ARM-arkitekturen, Raspberry Pi og Arduino, hjemmesystemer med Pi-hole, 3D-printere og CNC, industri-automatisering – og hvordan ARM i dag bærer Ceph-clusters, Kubernetes-nodes og verdens cloud-infrastruktur.

Fem minutters læsning. Efterfølgende ser du ARM-chips overalt. https://wiki.smarken.dk/doku.php?id=teknik:arm

Transcript fra https://www.youtube.com/watch?v=kcQ7n9-hkRU, Solar Panels Are Doing Something Nobody Expected af "Undecided with Matt Ferrell" 6. oktober 2026

Solpaneler blev bygget til ét formål: at omdanne sollys til elektricitet. Men et team af forskere ved det tyske universitet i Hohenheim mener, at solpaneler kan gøre noget andet. Noget overraskende… De tror, at solpaneler kan hjælpe med at få det til at regne … i ørkenen.

De Forenede Arabiske Emirater har netop givet teamet op til 1,5 millioner dollars til at teste deres teori og har udvalgt dem ud af 120 bidrag fra hele verden. Deres tidligere simuleringer anslår, at den rigtige solcellepark kan få det til at regne nok til at forsyne 125.000 ekstra mennesker med vand om året.

Men før vi griber vores paraplyer og sætter kursen mod Sahara, lad os stoppe op, tænke og hive vores hoveder ud af disse imaginære regnskyer. Det er komplekse ting, og da mit team og jeg dykkede ned i, hvordan solpaneler kan fungere som geoengineering-værktøjer, blev tingene hurtigt rodede. At lave regn fra solpaneler er måske faktisk muligt. Om vi ville have det, er det meget sværere spørgsmål.

Så hvordan kan solpaneler få det til at regne i ørkenen? Hvad har svovludledning fra skibe med det at gøre? Og vil denne overraskende tilgang til geoengineering holde sit løfte?

Jeg er Matt Ferrell … velkommen til Undecided. Denne video er bragt til dig af Surfshark.

Verden bliver tørrere

Verden bliver tørrere. Klimaforandringer, overgræsning og øget vandforbrug har spredt sig til tørre områder. En undersøgelse fra 2024 viste, at der mellem 1960 og 2023 var en samlet stigning på 9,99 millioner km² i tørre områder globalt … det er omtrent et helt Canada med tørhed.

Uden konstant nedbør står folk over for fødevareusikkerhed på grund af dårlige høster og misvægter. I den halvtørre Sahel-region kæmper omkring 1 ud af 13 mennesker med sult og underernæring hver dag. Dette er en humanitær krise. Og det er ikke et problem, vi er immune over for her i Amerika. Langs Colorado-floden har alvorlig tørke netop tvunget en 20% reduktion i det årlige vandforbrug. Manglende nedbør påvirker allerede vores liv.

Sådan blev solceller en vandløsning

Så hvordan bliver solcelleparker en potentiel vandløsning? Efterhånden som solenergi tog fart i løbet af det sidste årti, begyndte forskere at se på, hvordan denne nye og stadig mere massive fysiske infrastruktur påvirker økologien og klimaet. Tænk over det sådan her … Hvis du dækker 400 kvadratkilometer med sorte paneler, der er lavet til at optage lys fra solen og omdanne det til elektricitet, vil der ske NOGET med det omgivende miljø.

Det er ideen, der animerer arbejdet udført af Dr. Oliver Branch og professor Volker Wulfmeyer, som er specialister i jordvidenskab og meteorologi. I en artikel fra 2024 undersøgte de, hvordan varmeabsorberende overflader som solcelleparker utilsigtet kunne generere nedbør.

De kørte en computersimulering, der så på, hvordan spredende lysabsorberende sorte overflader "lavet af sort net, sortmalede eller solcellepaneler (PV)" kunne påvirke regn i De Forenede Arabiske Emirater. Resultaterne var lovende. Med et par sorte overflader på 20 gange 20 km, og antaget at geoenginerede nedbørshændelser sker 10 dage om året, forudsagde deres simulering nok regn til at forsyne mere end 31.000 ekstra mennesker om året i UAE med vand. Et par overflader på 50 gange 50 km øgede det til mere end 125.000 mennesker.

En ting at bemærke er, at de kunstige sorte overflader, eller ABS'er, som de brugte i disse simuleringer, ikke er præcis de samme som en solcellepark. Solpaneler absorberer mindre sollys end en ABS gør. Det er ikke den perfekte model, men de er kommet godt fra start.

For at bringe dette ud i den virkelige verden har teamet modtaget en ny bevilling fra UAE til at tage deres forskning til solcelleparker på den arabiske halvø. Med deres nylige bevilling planlægger Branch og hans kolleger at bruge LiDAR og højopløsningssimuleringer til at bestemme den optimale placering, størrelse og design af solcelleparker for at geoengineere ørkenen. Han siger, at da "solcelleparker bliver så store, især i UAE, har det givet os en fantastisk mulighed for at foretage målinger."

Prisen på regn

På overfladen lyder dette som en genial løsning på vandkrisen. Solenergi er den dominerende kilde til vedvarende energi, og hvert år bygger vi mere. I 2025 forventedes investeringerne i solenergi, både i forsyningsskala og på hustage, at nå 450 milliarder dollars.

Omkostningerne ved at bygge en solcellepark på 21 kvadratkilometer i Abu Dhabi var cirka 1 milliard dollars i 2022. Hvis vi bruger dette som et estimat for en solcellepark, der producerer regn, bliver matematikken hurtigt grim. Et areal på 20 gange 20 km er omkring 19 gange så stort som parken. Kald det 19 milliarder dollars. Du har brug for et par, så det er 38 milliarder dollars. Omkring 8% af de 450 milliarder dollars, som verden investerer i solenergi på et år, bruges på to gårde. Gå op til parret på 50 gange 50 km, og du er nord for 200 milliarder dollars. Regeringer finansierer allerede solcelleanlæg i stor skala, men ikke i nærheden af det, og ikke til regn.

Jeg mener … gig-økonomien boomer lige nu, så hvorfor ikke forvente mere af vores solpaneler? Hvis de kan producere elektricitet, hvorfor skulle de så ikke lave et andet skift i nedbørsbranchen? Jeg hader at få regn på denne parade, eller nogen anden parade egentlig. Men at få regn fra solceller bliver ikke så let, eller så billigt, eller potentielt så harmløst. Men før vi går ind på det, lad os kaste lidt … lys over, hvordan solpaneler overhovedet kan få det til at regne. Hold ud, for svaret starter med varme, vi alle smider ud.

Men utilsigtede konsekvenser er lidt min ting. Noget ser harmløst ud i årevis, og så finder man ud af, at det stille og roligt har lavet noget andet hele tiden. Dine personlige oplysninger fungerer på samme måde. Og det er her, dagens sponsor, Surfshark, kommer ind i billedet.

Jeg bruger meget tid på at tænke på at beskytte mit hjem mod de ting, jeg ikke kan kontrollere. Strømafbrydelser. Prisstigninger. Elnettet har en dårlig dag. Og jeg blev for nylig mindet om, at den digitale side har brug for den samme opmærksomhed. Der var et massivt Brightspeed-databrud, der lækkede personlige oplysninger om mere end 1 million kunder. Ting som navne, e-mails, telefonnumre og mere. Men med Surfshark kan du beskytte dig selv, mens du er online. Når du tilmelder dig nye hjemmesidekonti, kan du bruge Surfsharks alternative ID til at maskere dit navn og dine kontaktoplysninger. Så du stopper med at så det næste brud med dine rigtige oplysninger. De har også en e-mail-svindeltjekker, der bruger AI til at spotte phishing-angreb i din Gmail. Den fungerer gennem deres Chrome-udvidelse og fanger mistænkeligt indhold og ondsindede links, før du klikker på noget farligt. Det er ret fedt. Gå til https://surfshark.com/undecided eller brug koden UNDECIDED ved kassen for at få 4 ekstra måneder med Surfshark VPN! Surfshark tilbyder en 30-dages pengene-tilbage-garanti, så der er ingen risiko ved at prøve det selv. Jeg har brugt Surfshark i årevis og elsker det. Gå ikke glip af dette fantastiske tilbud. Linket er i beskrivelsen nedenfor. Tak til Surfshark og til jer alle for at støtte kanalen.

Sådan laver solpaneler regn

Okay, tilbage til ørkenen og den varme, vi har spildt hele tiden. Mørke overflader er meget bedre til at absorbere lys end lyse overflader. Tænk på at have en mørk skjorte på i stedet for en lys skjorte på en varm sommerdag. Det føles varmere i en mørk skjorte, fordi den absorberer sollyset i stedet for at reflektere det som en lys skjorte. Hvis vi optog disse videoer udenfor, ville du sandsynligvis se mig skifte min garderobe ud. Under alle omstændigheder er det det samme princip i ørkenen. Branch siger, at solparker forårsager en "mørklægning af landoverfladen, og du får en stigning i absorberet stråling."

Solpaneler kan ikke omdanne alt sollys, der rammer dem, til elektricitet. Faktisk er denne tilsyneladende begrænsning den eneste grund til, at denne teori om regndannelse muligvis virker. Det er en vigtig advarsel, og jeg vender tilbage til, hvorfor der er en skjult ironi i teorien senere.

Det meste af sollyset, der rammer et solpanel, omdannes til varme. Denne varme udstråles fra panelerne og danner strømme af varm, mindre tæt luft, der stiger op i atmosfæren. Det er den samme grund til, at opvarmning af luft får varmluftballoner til at svæve. Hvis disse strømme rammer fugtbærende luft, trækker de fugtigheden med sig op. Højt oppe i atmosfæren kondenserer den til skyer. Skyer kan udløse regn.

Det er også værd at bemærke, at fugtbærende luft er nødvendig for, at dette kan fungere. Derfor fokuserer Branch på at skabe regn i kystørkener, ikke bare en hvilken som helst ørken, hvor som helst. Regn kommer kun, hvis der genereres nok varme til at danne disse stigende luftstrømme for at ændre konvektionsmønstre … og med tilstrækkelig jorddækning er det, hvad Branchs team fandt ud af kunne ske. Da et par kunstige sorte overflader på 10 gange 10 km blev brugt, bemærkede de meget lille indflydelse på nedbøren. Men da de skalerede op til 20 gange 20 km, så de en mærkbar stigning i nedbør. Det er 400 kvadratkilometer mørk overflade. Hver.

Med henvisning til varmeeffekten på solpaneler siger Branch, at eksisterende solcelleparker "muligvis ikke er store nok til at opretholde den effekt længe nok til at skabe konvektionsinitiering." Lige nu er der ikke mange steder, hvor dette kunne ske. Ifølge Global Energy Monitor (GEM) er der pr. februar 2026 mere end 81.000 solcellefaser i drift i forsyningsskala rundt om i verden. Næsten ingen kommer i nærheden af 400 kvadratkilometer. Kun to gør, Hobq og Talatan, begge i Kina, og ingen af dem ligger i en kystørken, hvor havbrisen bærer fugtigheden. Dette kan være en af grundene til, at vi ikke rigtig har set nogen nedbørshændelser udløst af solcelleparker … endnu. De er bare ikke store nok, og de få, der kommer tæt på, er på det forkerte sted. Derfor mener Branch, at en stor nok solcellepark i en havbrises bane kan udløse nedbør i en kystørken.

Vi har geoengineeret før

Denne plan lyder usandsynlig, og det forstår jeg godt, men vi har allerede ved et uheld geoengineeret planeten. I 2020 satte den internationale maritime organisation et loft over, hvor meget svovl der måtte frigives fra skibe, og der var en uventet stigning i de globale temperaturer. Det viser sig, at alt det svovl, der forurenede luften, afbøjede sollyset og hjalp med at afkøle planeten. De små svovlpartikler fungerede som mikroskopiske spejle i luften. De reflekterede indkommende sollys tilbage i rummet, før det overhovedet opvarmede Jorden. Uden denne svovlskærm steg temperaturerne.

Denne utilsigtede geoengineering får ideen om solpanelinduceret regn til at virke mindre skør. Men det er også en advarsel. Én ændring i atmosfæren, som vi kan lide, kan resultere i mange, som vi ikke kan lide. Det er de utilsigtede konsekvenser, der bekymrer mig. De potentielle effekter kan mærkes på lokal og global skala … og de kan endda gøre solpaneler mindre effektive.

Utilsigtede konsekvenser

Solpanelers indvirkning på den lokale vegetation er ikke definitiv, selvom de fleste kilder peger på en forbedring af det lokale mikroklima. En simulering foretaget af forskere fra Lunds Universitet i Sverige undersøgte, hvad der ville ske, hvis 20% af Sahara-ørkenen var dækket af solpaneler. Lad os huske et øjeblik, at Sahara-ørkenen er omtrent på størrelse med det kontinentale USA, så det er *lidt* usandsynligt. Alligevel forudsagde modellen en positiv feedback-loop, der tilskyndede til mere nedbør.

Positive feedback-loops er lidt ligesom at holde en mikrofon for tæt på en højttaler. Højttaleren forstærker mikrofonen, mikrofonen opfanger den, og hver cyklus bygger sig op, indtil du får den skrig. I ørkenen forstærker den samme loop regn og vegetation. Mere regn betyder flere planter. Flere planter frigiver mere fugt. Mere fugt betyder mere regn.

Men hvad der er godt for Sahara, er måske ikke så godt for verden. Forskerne fandt ud af, at 20% solpaneldækning på Sahara kunne forårsage betydelige ændringer i det globale vejr. Svarende til hvad der skete, efter at skibe reducerede deres svovludledning. De forventede globale effekter af den imaginære Sahara-dækning forstærkede uforudsigelige klimamønstre. Simuleringen forudsagde stigende globale temperaturer, reduceret nedbør i Amazonas-regnskoven og flere tropiske cykloner på den nordlige halvkugle. Jeg kan godt lide ideen om at gøre ørkenen grøn, men jeg er ikke vild med udsigten til alt dette kaos andre steder.

Igen, at dække en femtedel af Sahara med solpaneler kommer ikke til at ske lige foreløbig … eller nogensinde. Et projekt af den størrelse ville producere cirka 4,7 gange mere energi, end verden har brug for i øjeblikket. Men undersøgelsen peger på en grænse for, hvor langt vi kan skubbe denne teknologi og dens potentielle indflydelse.

Solpanelernes skjulte ironi

En anden ting at overveje er ændringerne i solstrålingen, hvis vi har flere regnvejrsdage i ørkenen. En senere simuleringsundersøgelse af solpanelers indflydelse på tværs af Sahara viste, at med øget skydække vil mængden af sollys, som solpaneler er i stand til at absorbere, blive reduceret. Det er indlysende, når man tænker over det. Når solpaneler får det til at regne, kan den regn gøre dem mindre effektive til at producere elektricitet. Man kan sige, at solpaneler er ret solbeskyttende over for deres omgivelser. Ja, undskyld … jeg var nødt til at gøre det … til minde om min mor, der elskede et godt ordspil.

Undersøgelsen forudsagde, at med mere skydække ville solstrålingen falde i regioner som Mellemøsten, Indien, det østlige Kina og det sydvestlige USA. Ironisk nok er det regioner, der sigter mod at øge deres solproduktion. Men med mindre indkommende sollys vil øget solpanelers effektivitet være løsningen … ikke sandt? Men hvis solpaneler bliver betydeligt mere effektive, vil de ikke være i stand til at få det til at regne! Husk, at solpaneler ikke omdanner alt det sollys, de absorberer. Typisk bliver kun 15% til elektricitet. Resten bliver til varme. Gør panelerne mere effektive, og den varme forsvinder sammen med den konvektion, der driver regnen. Hele teorien fungerer kun, fordi solpaneler ikke er *så* gode til deres daglige arbejde. På den anden side, hvis solcelleparker bliver rigtig gode til at producere regn, hvor der er brug for det, kan vi måske klare os fint med paneler, der producerer mindre elektricitet. Det er ironien. At arbejde to job er udmattende, og solpaneler er ligesom resten af os.

Hvad skal vi tænke?

Så hvordan skal vi tænke på dette? Selvom solpanel-vejrmaskiner måske er mulige, kan de i stor nok skala producere uforudsigelige og uønskede resultater. Den igangværende forskning i UAE er blot et lille skridt i den retning. Men det er et skridt, vi skal overveje meget nøje. Verdens klimasystem er som en kæmpe, våd Rube-Goldberg-maskine. Hvis man starter én begivenhed på ét sted, kan en række ustabile interaktioner ende med at påvirke nogen på den modsatte side af kloden.

Professor Eloise Marais, en atmosfærisk kemiker fra University College London, har sagt, at geoengineering ikke rigtig er blevet udført i stor skala, fordi "der er så mange utilsigtede konsekvenser". Hun siger, at "omhyggelig etisk fremsyn er nødvendig, før vi indfører geoengineering." Omhyggelig planlægning er heller ikke let. Det tager år at indsamle så mange data fra den virkelige verden, hvilket er grunden til, at næsten alt, hvad vi ved om dette, kommer fra simuleringer. De bruger virkelige data, men de indfanger ikke fuldt ud, hvordan vejret rent faktisk opfører sig.

Og det er ikke fordi, vi ikke har alternativer til at hjælpe mennesker, der bor i ørkenen. Der er mindre radikale tilgange til at reducere ørkendannelse, der allerede virker. For eksempel har ændringer i landbrugspraksis i Sahel ført til en forbedring af høsten i de sidste 30 år. Men endnu vigtigere er det, at vi ved, at solcelleparker kan bidrage til at forbedre livet i ørkenmiljøer uden eksplicit at forsøge at ændre vejret. Tag for eksempel solcelleparken Talatan i Kina. Parkens paneler fungerer som vindbarrierer, der reducerer fugtfordampning på overfladen. Resultatet? En stigning i vegetation omkring panelerne. Jeg har en video om agrivolatik, som du måske vil se for at lære mere om den slags systemer.

Det er værd at påpege, at disse løsninger fokuserer på at øge vegetationen og ikke direkte adresserer manglen på vand. Alligevel viser de, at vi har muligheder ud over geoengineering af skyer, selv i ørkenen.

Et spørgsmål, der bliver hængende

At bruge solpaneler til at lave regn lyder som science fiction … og det er måske bedre stillet på den måde for nu. Klimaforandringer har allerede gjort vejret uforudsigeligt for os alle, og hvis vi blander endnu en spiller ind i blandingen, bider vi måske mere i, end vi kan tygge. Jeg mener, hvem ville have troet, at hvis vi reducerede svovleidmissioner for at skabe mindre forurening, ville vi opvarme planeten? Men samtidig ville virkningerne af ikke at foretage den ændring være langt værre.

Hvis Branch og hans kolleger kan finde et optimalt sted, hvor solpaneler kan geoengineere mere nedbør uden at forværre de globale klimaforandringer, bør vi virkelig være opmærksomme. Men det er langt ude i fremtiden. Lige nu indsamler de bare data for bedre at modellere muligheden for at skabe regn i kystørkenen i et lille land. Det er ikke for meget grund til bekymring. Men igen, jeg er ikke sikker på, at solpaneler behøver at få det til at regne for at gøre ørkenen bedre.

Husker du solcellefarmene i Talatan i Kina, som jeg lige nævnte? Solpanelerne var så effektive til at genforvilde jorden, at de lokale myndigheder bragte 20.000 "fotovoltaiske" får ind for at græsse, hvilket forhindrede ukrudt i at blokere solpanelerne. Dette har været gode nyheder for lokalsamfundet og dets økonomi. En lokal hyrde plejede at gå 10 km for at finde foder, men tjener nu omkring 14.000 dollars om året på at passe de solcelledrevne får. For mig virker det som en langt mere solrig udsigt end at bruge solpaneler til at rode med vejret.

Her er spørgsmålet, jeg bliver ved med at gå i ring om. Hvis en solcellefarm kan få det til at regne for folk, der har hårdt brug for vandet, men modellerne siger, at det måske tørrer ud et andet sted, bygger du den så? Og hvem får lov til at træffe den beslutning, landet med solcelleparken eller folkene i vinden?

Systemd på openSUSE Linux – Komplet Guide

Baséret på videoen "The Linux Lighthouse" – en guide til systemd på openSUSE Linux, fra grundlæggende kommandoer til avanceret tilpasning.

Hvad er systemd?

Systemd er Linux' system- og service-manager, som initialiserer og administrerer systemprocesser, efter kernen er indlæst. Den erstatter det gamle SysV-init-system. Systemd er kendt for paralleliseret opstart og on-demand-aktivering af dæmoner, hvilket gør den hurtigere og mere effektiv.

Systemd's vigtigste funktioner:

• Paralleliseret opstart af tjenester
• Socket- og D-Bus-aktivering for on-demand-tjenester
• cgroup-baseret proces-sporing
• Oprettelse af snapshots og systemgendannelse
• Fleksibel afhængighedsstyring

Tjenestestyring med systemctl

Det primære værktøj til at administrere systemd er systemctl. Her er de grundlæggende kommandoer, du får brug for hele tiden (eksemplerne bruger sshd – SSH-tjenesten til sikker fjernlogin).

Oversigt over aktive enheder

systemctl list-units

Viser alle aktuelt aktive enheder med deres status og beskrivelser.

Start og stop af en tjeneste

# Start en tjeneste
sudo systemctl start sshd

# Stop en tjeneste
sudo systemctl stop sshd

Tjek status

systemctl status sshd

Giver detaljeret information om tjenestens aktuelle tilstand, inklusive fejl.

Genstart og genindlæs

# Genstart en tjeneste
sudo systemctl restart sshd

# Genindlæs konfiguration uden afbrydelse
sudo systemctl reload sshd

Start automatisk ved boot (enable/disable)

# Start automatisk ved boot
sudo systemctl enable sshd

# Undgå start ved boot
sudo systemctl disable sshd

# Tjek om tjenesten er enabled
systemctl is-enabled sshd

Targets

I systemd erstatter targets det gamle runlevel-koncept med mere fleksible opstartssekvenser.

Vis og sæt default target

# Vis nuværende default target
systemctl get-default

# Sæt nyt default target (kræver sudo)
sudo systemctl set-default graphical.target   # eller multi-user.target / rescue.target

Efter en reboot starter systemet i det target, du lige har sat.

Skift target med det samme

sudo systemctl isolate multi-user.target

Skifter straks systemet til det valgte target (f.eks. multi-user eller rescue).

Enheder (units) og egne unit-filer

Systemd-enheder defineres af unit-filer, som ligger i:

• /usr/lib/systemd/system – standard-enheder
• /etc/systemd/system – egne/tilpassede konfigurationer

Sådan opretter du en tilpasset unit-fil (eksempel med sshd.service):

# 1. Kopiér en standard-unit-fil til /etc/systemd/system
sudo cp /usr/lib/systemd/system/sshd.service /etc/systemd/system

# 2. Redigér filen efter behov

# 3. Genindlæs systemd
sudo systemctl daemon-reload

# 4. Start/enable din tilpassede tjeneste
sudo systemctl start sshd

Oversigt og fejlfinding

Vis alle indlæste unit-filer

systemctl list-unit-files --type=service

Vis kun feilede tjenester

systemctl --failed

Analysér opstartstider

# Tjenester sorteret efter opstartstid
systemd-analyze blame

# Grafisk rapport som PNG
systemd-analyze plot > startup.png

blame viser tjenester sorteret efter opstartstid; plot genererer et PNG-diagram med en visuel opdeling af opstartstiderne.

Snapshots – et forbehold

Den officielle openSUSE-reference- og administrationsguide beskriver systemd-snapshots: sudo systemctl snapshot <navn>.snapshot, som gemmer systemets aktuelle tilstand og muliggør nem gendannelse (oprettelse, sletning, liste og isolate).

Bemærk: Denne funktionalitet virker ikke i praksis. systemctl snapshot og systemctl list-snapshots findes ikke længere – sandsynligvis er funktionen fjernet fra systemd til fordel for Snapper. Funksjonen er dog stadig omtalt i den officielle manual. Videens skaber efterlyser information, hvis nogen kender nærmere detaljer.

Timer-units (jobscheduling)

Systemd-timer-units bruges til jobplanlægning ligesom cron, men med flere fordele:

• Jobs kan afhænge af andre systemd-tjenester
• Timers håndteres som almindelige systemd-tjenester via systemctl
• Timers kan være real-time (kalenderbaserede) eller monotonic (relative)
• Timers logges i systemd-journalen, hvilket gør overvågning og fejlfinding lettere

Opret en service-fil

Opret filen /etc/systemd/system/mytask.service (navnet skal slutte på .service):

[Unit]
Description=My scheduled task

[Service]
ExecStart=/usr/local/bin/mytask.sh

Opret en timer-fil

Opret filen /etc/systemd/system/mytask.timer:

[Unit]
Description=Run my task every hour

[Timer]
OnCalendar=hourly
Persistent=true

[Install]
WantedBy=timers.target

Aktivér og start timeren

sudo systemctl enable mytask.timer
sudo systemctl start mytask.timer

# Tjek at timeren er aktiv
systemctl list-timers

Tip: Hvis timeren fejler med "bad unit file setting", så tjek statussen med systemctl status mytask.timer – ofte er det en tastefejl i unit-filen (f.eks. en forkert nøgle).

Temp-files (tmpfiles.d)

Systemd understøtter regelmæssig oprydning i midlertidige mapper via tmpfiles.d, som læser sin konfiguration fra (i prioriteret rækkefølge):

1. /etc/tmpfiles.d – egne indstillinger (overtrumfer de andre)
2. /run/tmpfiles.d
3. /usr/lib/tmpfiles.d – pakkenes standardkonfiguration

Konfigurationsformatet er én linje pr. post: type, path, action samt evt. mode, ownership, age og argument-felter.

Eksempel: automatisk oprydning i /tmp

Opret filen /etc/tmpfiles.d/cleanup.conf:

sudo vi /etc/tmpfiles.d/cleanup.conf

Med følgende indhold (sletter filer ældre end 10 dage i /tmp):

d /tmp 1777 root root 10d

Tjek derefter timeren, der håndterer oprydningen:

systemctl status systemd-tmpfiles-clean.timer

Tip: Der findes mange parameterkombinationer til forskellige use cases – læs manualen (man tmpfiles.d) for en fuld forklaring.

Logstyring med journalctl

journalctl giver adgang til at forespørge logbeskeder:

# Vis alle logs for en bestemt tjeneste
sudo journalctl -u sshd

# Følg logs i real time
sudo journalctl -u sshd -f

# Begræns antal viste linjer
sudo journalctl -n 50

-f er praktisk til realtids-overvågning (f.eks. mens du logger ind via SSH på en anden maskine) – afslut med Ctrl+C.

Opsummering

Denne guide har dækket:

• Grundlæggende systemctl-kommandoer (start, stop, status, genstart, genindlæs, enable/disable)
• Targets og hvordan du skifter mellem dem
• Oprettelse af egne unit-filer
• Fejlfinding og opstartsanalyse (--failed, systemd-analyze)
• Timer-units som cron-alternativ
• Oprydning af midlertidige filer med tmpfiles.d
• Loganalyse med journalctl

Af LivingLinux - https://www.youtube.com/@LivingLinux - https://bsky.app/profile/livinglinux.bsky.social

https://www.youtube.com/watch?v=8SNym6Pea-o

https://invidious.nerdvpn.de/?v=8SNym6Pea-o

Opensuse hardware page : https://en.opensuse.org/Portal:Hardware

openSUSE announced that you can start testing an image on the Raspberry Pi 5. Not everything is working, but it's probably usable for server tasks and you can start a desktop environment. 3D acceleration is not fully implemented, so I'm not doing my usual tests.

https://news.opensuse.org/2025/11/04/raspberrypi5-opensuse/

https://en.opensuse.org/HCL:Raspberry_Pi5

Default user is root and password is linux.

Make sure you have a recent installation of the Raspberry Pi firmware (I have 2025.04).

You can use YaST to create a new user, so you don't have to login as root. And you can use YaST to install additional software.

I look forward to a new image with 3D support.

00:00 Intro 00:12 openSUSE Announcement 01:04 System Information 01:46 Boot Issue (Fixed) 02:10 Images 02:30 Known Issues 02:54 YaST2 (Setup Tool) 04:54 vkCube 05:25 Future of YaST2 06:34 Closing Thoughts

If this video was helpful, please like, comment and subscribe!

(pæn) transcript : (fixed med mistral)

Kapitel 1: Intro Welcome to my channel Living Linux. In this video, I want to have a quick look at Open Soua on the Raspberry Pi 5.

Kapitel 2: openSUSE Announcement So, you can see that early November, they announced that they support the Raspberry Pi 5 and it took them quite some time to get it booting. And it looks like that they are upstreaming their changes to Uboot. Now, there's still a lot of work to be done, but I'm creating uh this video on a Raspberry Pi 5, or at least you see the desktop running on a Raspberry Pi 5. There are still a lot of things missing, but of course, they're working hard on it. And it might be that you have to update your EPROM. And yeah, I can show you that I have the firmware from April.

Kapitel 3: System Information So that one is good enough to get started with Open Soua. And yeah, here you see unfortunately at the moment graphics is software rendering and I'm more of a desktop person not really a server person. So that means that my uh use cases will be limited for the time being. Good thing is is that it has kernel 6.17.8.

Kapitel 4: Boot Issue (Fixed) Now there was an issue that booting uh could hang. Um but it looks like that that one has been fixed. So here is let's just say the main page for open sus on the Raspberry Pi 5.

Kapitel 5: Images So you can download different images and it's if you want to have a desktop image uh better skip KDE for now because it seems it has a graphic problem at the moment. You have to boot from micro SD. No other option.

Kapitel 6: Known Issues No support for I2S, ADC, I2C. Well, some more things. 3D acceleration not fully supported, but as you can see, you are able to get a working desktop.

Kapitel 7: YaST2 (Setup Tool) Now, one of the things that I've heard uh a lot of complaints about is that with Linux, people say that you have to use the terminal. Now, uh yeah, the default login is root with this password. And the only thing I did on the command line was change the password for root. But for instance, uh creating a user you can do with uh yast. That is yet another setup tool. So here you have a guey for editing a user, adding a user or even deleted. So that makes things a lot easier. One other thing is also that um a lot of the software you can just install it with y um so and even let's just say the software that you use on the command line that can also be installed with y with a guey. So here you can see that for instance vk cube uh falcon info you can just install it with this guey.

Kapitel 8: vkCube Now as I as they said uh 3D acceleration it's not yet implemented or at least not fully implemented. So if we have a look at VK cube then you can see that it's using a lot of CPU. It does work but it's using a lot of CPU.

Kapitel 9: Future of YaST2 Now one more thing about Yust. Uh it seems uh they want to phase it out and I think one of the reasons is that it was written in Ruby and not that many people use Ruby anymore or develop in Ruby anymore. So yeah, I think that there's not really something that really replaces Yust completely, but there are of course other things. For instance, the package manager, you can try to use Mirlin. Uh I also see that for instance like the administration part that they say that you can try soua multi Linux manager those kind of things but to be honest I never really used open soua before so it's still a lot of uh homework that I have to do but I think the good part is that you and start testing it on a Raspberry Pi 5.

Kapitel 10: Closing Thoughts And for the boot process, they're upstreaming it to Uboot. So perhaps other distributions can also make use of this in the future. So yeah, I would say anyone that is interested, give it a try. Um, first boot process can take a while. uh let it boot for a couple of minutes before giving up. And remember that you need to have a recent firmware. So this is all for now and hope to see you again in my next video.

(Rå) Transcription : Kapitel 1: Intro 0.010 sekunderWelcome to my channel Living Linux. 0.040 sekunderIn this video, I want to have a quick look at Open Soua on the Raspberry Pi 5. Kapitel 2: openSUSE Announcement 0.120 sekunderSo, you can see that early November, they announced that they support the Raspberry Pi 5 0.200 sekunderand it took them quite some time to get it booting. And it looks like that they are upstreaming their changes to Uboot. 0.340 sekunderNow, there's still a lot of work to be done, but I'm creating uh this video on a 0.410 sekunderRaspberry Pi 5, or at least you see the desktop running on a Raspberry Pi 5. There are still a 0.500 sekunderlot of things missing, but of course, they're working hard on it. 0.560 sekunderAnd it might be that you have to update your EPROM. 1.021 sekundAnd yeah, I can show you that I have the firmware from April. Kapitel 3: System Information 1.111 sekundSo that one is good enough to get started with Open Soua. 1.181 sekundAnd yeah, here you see unfortunately at the moment graphics is software rendering and I'm more of a desktop 1.261 sekundperson not really a server person. So that means that my uh use cases will be limited for 1.341 sekundthe time being. Good thing is is that it has kernel 6.17.8. Kapitel 4: Boot Issue (Fixed) 1.461 sekundNow there was an issue that booting uh could hang. 1.541 sekundUm but it looks like that that one has been fixed. 2.032 sekunderSo here is let's just say the main page for open sus on the Raspberry Pi 5. Kapitel 5: Images 2.102 sekunderSo you can download different images and it's if you want to 2.172 sekunderhave a desktop image uh better skip KDE for now because it seems it has a graphic 2.262 sekunderproblem at the moment. You have to boot from micro SD. No other option. Kapitel 6: Known Issues 2.362 sekunderNo support for I2S, ADC, I2C. Well, some more things. 3D 2.422 sekunderacceleration not fully supported, but as you can see, you are able to get a working desktop. Kapitel 7: YaST2 (Setup Tool) 2.542 sekunderNow, one of the things that I've heard uh a lot of complaints about is that with 3.033 sekunderLinux, people say that you have to use the terminal. 3.083 sekunderNow, uh yeah, the default login is root with this password. 3.193 sekunderAnd the only thing I did on the command line was change the password for root. 3.273 sekunderBut for instance, uh creating a user you can do with uh yast. 3.393 sekunderThat is yet another setup tool. 3.513 sekunderSo here you have a guey for editing a user, adding a user or even deleted. 4.014 sekunderSo that makes things a lot easier. One other thing is also that um a lot of the software 4.104 sekunderyou can just install it with y um 4.234 sekunderso and even let's just say the software that you use on the command 4.334 sekunderline that can also be installed with y with a guey. So here you can see that for 4.414 sekunderinstance vk cube uh falcon info you can just install it with this guey. Kapitel 8: vkCube 4.544 sekunderNow as I as they said uh 3D acceleration it's not yet implemented or at least not fully implemented. 5.045 sekunderSo if we have a look at VK cube then you can see that it's using a lot of CPU. 5.135 sekunderIt does work but it's using a lot of CPU. Kapitel 9: Future of YaST2 5.255 sekunderNow one more thing about Yust. 5.295 sekunderUh it seems uh they want to phase it out and I think one of the reasons is that 5.375 sekunderit was written in Ruby and not that many people use Ruby anymore or develop in Ruby anymore. 5.485 sekunderSo yeah, I think that there's not really something that 5.555 sekunderreally replaces Yust completely, but there are of course other things. For instance, the package manager, you can try to use Mirlin. 6.086 sekunderUh I also see that for instance like the administration part that they say that 6.166 sekunderyou can try soua multi Linux manager those kind of things but to be honest I 6.256 sekundernever really used open soua before so it's still a lot of uh homework that I 6.336 sekunderhave to do but I think the good part is is that you and start testing it on a Raspberry Pi Kapitel 10: Closing Thoughts 6.406 sekunder5. And for the boot process, they're upstreaming it to Uboot. So perhaps other distributions can also make use of this in the future. 6.526 sekunderSo yeah, I would say anyone that is interested, give it a try. Um, first boot process 7.027 sekundercan take a while. uh let it boot for a couple of minutes before giving up. 7.097 sekunderAnd remember that you need to have a recent firmware. 7.157 sekunderSo this is all for now and hope to see you again in my next video.