Laz (He/Him)

@laz000.bsky.social

Widower. Dad. Blue Gen X. Philly sports fan. Tech guy. Please no Crypto, no Adult pic(don't want a gf),no Illuminati, etc in my DMs. #AA and #ACOA welcome. Always try to be nice, never fail to be kind... #Slackware #FreeBSD #BlackSky #LGBTQIA #Feminist

The Trump administration is testing a secretive, never-before-used deportation court for alleged alien terrorists with a case concerning the Afghan mother of a convicted terrorist, with the Justice Department accusing the Texas-based woman of having ISIS sympathies. https://cnn.it/3U385sg

Bild

Live update on the Iran war! The US resumes attacks against Iran. This war is being fought at the expense of higher prices at the pump and grocery stores to the benefit of Trump's ego. I'll link petitions you can sign below if you live in the US and can share if you do not. #Iran #US #Peace

US bombs Iran over attack on Jordan base; Iraq condemns US-Saudi attacks

Threat comes as Iranian media report that four Iranians were killed in joint US-Saudi attacks in Iraq.

aljazeera.com

[lien] FreeBSD ports frozen after someone commits the entire 150MB Linux Copilot binary – OSnews #gik #bsd #wtf #git #ai

FreeBSD ports frozen after someone commits the entire 150MB Linux Copilot binary

A rather unusual announcement was made late last night: the FreeBSD project has frozen their ports repository. For more than 48 hours now, no changes have been accepted or made to the tree, and here’s why. > A 150MB binary file was recently committed to the ports tree and, as a result, core@ made the decision to implement a temporary freeze of the ports tree in order to implement some clean up efforts. The commit in question severed our ports tree mirroring to github.com due to their filesize hard limit of 100MB, and introduced a blob of questionable licensing into the repository history. > > ↫ Kyle Evans in freebsd-announce While FreeBSD’s ports tree is not hosted by GitHub – it’s merely mirrored there – the FreeBSD team believes the community values the GitHub mirror too much, and as such, steps had to be taken to fix this. Ports has not been compromised and users’ systems do not appear to be at risk in any way due to this occurrence, which is good news. Curiously, the official announcement makes no mention of which 150MB file, exactly, was committed to ports, but it didn’t take for people long to pinpoint the offending commit (screenshot). It turns out someone committed the entire github-copilot-cli Linux binary to ports, as part of the github-copilot-cli port. This FreeBSD port is effectively a way to easily install and run this tool on FreeBSD using Linuxulator, FreeBSD’s Linux compatibility layer that allows you to run unmodified Linux binaries on FreeBSD. It’s important to note this FreeBSD port is not actually a _port_ of the Linux version of github-copilot-cli to FreeBSD; the FreeBSD “port” merely acts as a setup script to run the unmodified Linux binary using Linuxulator. It’s not a “real” port because the tool isn’t open source and its license doesn’t allow for modifications. That’s why the announcement specifically mentions “questionable licensing” – github-copilot-cli is licensed under some custom license specifically made for this tool, and is not open source. Anyway, for whatever reason, the maintainer of this FreeBSD port accidentally made a commit that added the actual, full 150MB Linux binary to FreeBSD ports. I’m assuming that under normal circumstances, building and installing the github-copilot-cli FreeBSD port would merely download the binary off GitHub and set Linuxulator up so that it could run it. Mistakes happen, and since there’s clearly nothing malicious going on, there’s not much to worry about. In fact, this may lead to new checks and balances to prevent this from happening in the future, which would be good news. The FreeBSD team is working on rolling back, fixing the issue, and investigating how this could have happened. Ports is still frozen at the time of writing, but I’m sure we’ll have a more detailed account soon.

osnews.com

History is littered with projects that discovered the hard part wasn’t writing new code: it was inheriting the web of trust, maintenance, compatibility, incentives, and legitimacy surrounding the old code.

I still find myself occasionally thinking about this "call his bluff and fork the kernel" "I'm not even a programmer, I'm an arts major whose understanding of software development originates from being raised by a programmer"

People should very definitely call his bluff and fork the kernelI'm not even a programmer, I'm an arts major whose understanding of software development originates from being raised by a programmer

Because REPUBLICANS. They confirmed RFK Jr, Secretary Serial Killer. Honorary mention to Senator Bill Cassidy, an actual physician 👀 Our country has become a pit of disease and parasites. Bring out your dead.

BildBildBild

Wow, never thought I'd see Linus go the way of so many Tech "Visionaries". A young man wanting to do something because there was nothing else available (so to speak) and start what is (despite his protestations to the contrary) A political and Religious quake in tech.

The OG Baumster@ogbaumster.bsky.social · 3w ago

incredibly fucking lame move to intentionally ruin a great thing you made guy. thankfully slackware 15 is rock solid so I won't need anything else for quite a while. see you when the ai bubble bursts chud