People say this place is a street.
But they behave like it's their living room.
While in reality, it's a soapbox on the main square.
Meanwhile all I wanted is a watercooler.
1. Reinvent a square wheel
2. Understand what's so hard about making wheels
3. Observe how a round wheel someone invented a while ago performs better than your square one.
4. Appreciate the brilliant and simple solutions to all wheel design issues that a round wheel implements.
5. Throw away your square wheel.
1. Reinvent a square wheel
2. Push it to production
So there's this AI for GMing RPGs:
I've been playing around with it, and it's pretty impressive:
me: "I'm getting this compilation error - it says it can't find the socklen_t type" the student replies. This looks like a common mistake. You ask: "Did you put sys/types.h as the first include?"
AI: and he replies that he did. You proceed to say "Well, you need sys/socket.h to use sockets in linux." and he replies that he included that file too.
blacklist -> blocklist, controversy, youtube link
I am white. And I think that this is bullshit like the guy on this video.
You may now throw shit at me.
Y’all, my newest housemate brought their 11-year-old TV to the house and you would not *believe* some of the features it has:
- literal 1-*second* boot up time. Unheard of
- UI responds instantly to input
- UI Design & UX is clear, consistent and well-suited to the input method (remote)
- doesn’t know what wifi or Ethernet is so it isn’t in a botnet or mining bitcoin
- isn’t sending private tracking data to who-knows-how-many companies’ servers, because see above
- doesn’t demand software updates or brick itself
- has things called “HDMI ports” for if you want to augment its functionality
How about we make 2021 the year of the return of non-smart TVs
Cause, I'd think it wouldn't be too hard to make an optimizaiton pass like:
1. convert all conditions to DNF form
2. split them at ORs, copy the rest of the query, and UNION them
3. remove useless LEFT JOINs
Of course it will only be beneficial if the conditions are highly selective. And I don't know how hard it is to estimate selectiveness of complex conditions.
Any idea if this is still the case with PostgreSQL 12?
You can also use this opportunity to replace tty1 with ttyS1 in /etc/inittab or something, because console=ttyS1 doesn't guarantee the userspace will provide any kind of serial console down the line
How to workaround wierd Linux kernel commandline length limitations:
1. find the earliest point in the init process where you can get a shell, and how to trigger it
2. trigger it
3. find the next script that runs after that
4. in the early init shell, edit that script and add the variables that didn't fit in kernel commandline
5. continue booring
Tomorrow I'll try:
- newer SBUU
- newer SUU
- running a particular update package by hand from a shell in the SBUU
- maybe updating just the BMC and not BIOS (but first I'll try to find out whether it's save to do so)
It still did nothing.
It seemed like it worked, but BIOS is still old :/
Meanwhile, I discovered that instead of trying to find anything on the shitty support & downloads page, I could just go to:
It's a blessing.
A static HTML page with all downloads for a particular server model.
And they have pages like that for most of the models AFAIK.
CompSci student at Uni of Warsaw
Linux geek, trying to be a sysadmin
Likes The Unix Way
🇬🇧🇵🇱(🇯🇵 a bit)
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!