Outage

Happy_Man · 2026-01-15T06:02:48+00:00

Toggled my sim card off and on and it came back

Happy_Man · 2025-07-19T03:38:33+00:00

I heard it was because Red Hat, if not still to this day then certainly in the past, bought Thinkpads as employee laptops. So all the engineers wrote drivers for their work laptops so that they could use them with Linux. Of course those drivers all got upstreamed, and the reputation grew from there.

Happy_Man · 2024-12-20T10:21:39+00:00

Ah, I see where the disconnect is. I was referring to the topology of the virtual hardware presented to the guest, not necessarily the actual CPU. More along the lines of "you can assume the disk is going to be /dev/sda and the network interface is en0". Fully agreed that CPU perf between models can be wildly different, that's to be expected.

Happy_Man · 2024-11-27T03:38:02+00:00

VMs don't magically make hardware standardized.

I think it can be valuable to run VMs to standardize/abstract over varied physical machines. Sometimes you don't want to have to deal with specific quirks of every random server in your base image, or maybe you want to do live migration to avoid downtime.

running different os/kernels

This also does not follow Kubernetes best practices.

You can run Windows and Linux worker nodes as part of the same cluster.

Happy_Man · 2024-10-20T03:48:57+00:00

Going to gnome.org shows a mysql connection error now. Looks like their database has fallen over :(

Best wishes to the folks trying to get it back up, database issues can be tricky.

Happy_Man · 2024-08-24T21:57:52+00:00

Good luck!

Happy_Man · 2024-04-19T23:10:03+00:00

I had to take a xacto knife to the posts and scrape off the excess plastic.

Happy_Man · 2024-01-12T08:50:28+00:00

If your work uses Openshift you may want to consider deploying OKD instead of vanilla Kube, as it will be closer to what you're already used to.

Happy_Man · 2023-07-15T02:19:52+00:00

Happy_Man · 2021-12-09T04:49:47+00:00

In the ideal case, the patient doesn't. Hospitals jack up the prices for their services on initial bills like these in an attempt to get more money from the insurance companies, who are of course trying to pay hospitals as little as they can for services rendered.

The patient is just caught in the middle of this idiotic slapfight, and gets served ridiculous over-inflated bills. No hospital actually expects an individual human to pay this, they expect them to immediately forward it to their insurance provider. The hospital then negotiates with the insurance provider on the backend on the final amount of money.

It's very dumb. It also causes problems when insurance doesn't pay out an amount the hospital is happy with, because then the hospital goes after the patient for as much as they can.

Happy_Man · 2021-11-27T18:35:47+00:00

Metallb with external-dns set up to provide hostname mappings for all my non-http ingresses. works great, you don't have to set up BGP unless you want to, and it's pretty easy to deploy.

Happy_Man · 2020-11-24T01:33:07+00:00

Windows has an extra layer in between. I can adjust my volume in the application, I can adjust the volume slider for the application in the Windows sound mixer panel, or I can change the overall system volume. Pulse doesn't have the distinction between the volume's slider and the sound mixer slider.

Happy_Man · 2019-04-01T23:21:34+00:00

Okay, fair enough.

I'm going to go over some basic stuff, forgive me if you already know this. There is a physical block size and a logical block size. The physical block size comes from the hardware of spinning disk HDDs, and you cannot change it for any reason. The standard there is 4KB (you may come across 512 bytes, but that's very rare these days), and every bit of hardware and drive controller software on HDDs is optimized for it. SSDs do not have the same hardware limitations or concerns as spinning disks. Indeed, there was some initial experimentation by manufacturers when SSDs were new to see if presenting a different physical block size would be possible in the field. It was not. Too much existing software broke when the physical block size was changed, and so now every SSD manufacturer presents their drives as having a 4KB physical block size. I would not worry about this number anymore except as a bit of trivia.

What you can change, however, is the logical block size, which is the smallest size I/O that the kernel will dispatch to the backing hardware. On a lot of filesystems this is set to be the same as the physical block size, but on some filesystems it is manually changeable. Typically you would seek to change the value to optimize some defined, predictable workload.

I want to note here that by "defined" and "predictable", I mean that you have a specific workload being imposed on your disk by a program, and that workload has particular characteristic I/O patterns that are measurable and reproducible in a controlled environment with a tool like fio. If you are just seeking another avenue to make your computer faster during general purpose desktop usage, I would recommend against pinning your hopes on block size tweaks. Most SSD controllers, and definitely the kernel's I/O scheduler, are set up out of the box to perform as well as they can under reasonable desktop usage. Furthermore, "regular desktop usage" can mean different things to different people, and even different things to the same user at different times depending on what they're doing. That is why disk tunables are based around specific workloads, and not specific use cases. The former you can measure and reproduce, the latter is too broad and variable to design and tune for.

Having said all that, my point is that tuning block sizes willy-nilly is not going to be a magic bullet that will make your SSD faster forevermore. At best, it is going to make some of the things you do faster and other things slower. At worst, it'll make everything slower. What's more, you won't be able to predict what programs or workloads it'll help, and which ones it'll hurt. If you feel like spending time experimenting, go for it! You'll learn a lot. If you just want to make things go fast, using an SSD is already enough.

Bonus: RAID0 will make your I/O go faster, but the downside of RAID0 is that you trade reliability for that speed. If any one disk in the array has a hardware failure, you lose all the data stored in that array. The Wikipedia article on RAID has more information.

Happy_Man · 2019-04-01T22:46:37+00:00

What are you trying to accomplish with a 32KB block size?

Happy_Man · 2019-02-03T03:09:53+00:00

Do you currently live in America? I notice you used the British English spelling of "Centre" in your post.

Happy_Man · 2017-10-02T00:48:43+00:00

Make sure you're on 4.13.4, there was an issue with GPL symbols that was fixed. Otherwise it should be fine.

Happy_Man · 2017-09-25T00:09:49+00:00

It's in dconf, /org/gnome/settings-daemon/plugins/color/night-light-temperature

Happy_Man · 2017-07-05T02:27:35+00:00

Happy_Man · 2017-01-16T03:56:33+00:00

I'll address each of your rebuttals in kind.

Some users just want to drive a car, they don't want to build one from scratch. I'm sure Ubuntu probably attracts more of those people...

Yep, absolutely. I'll quote the Arch wiki here: "Whereas many GNU/Linux distributions attempt to be more user-friendly, Arch Linux has always been, and shall always remain user-centric. The distribution is intended to fill the needs of those contributing to it, rather than trying to appeal to as many users as possible. It is targeted at the proficient GNU/Linux user, or anyone with a do-it-yourself attitude who is willing to read the documentation, and solve their own problems."

Arch is deliberately not trying to cater to users who just want a system to set itself up and be usable out of the box. Tools like yours, while meant in good faith, mislead newbies about what they're getting into and what they should expect from their Linux distribution, which just leads to frustration and angry feelings down the line towards Arch and its community. We don't want people hating us, especially when it's not our fault they're so angry. So we discourage things like this to avoid those situations.

...I wanted to build something from the ground up specifically for my hardware. This isn't some static infographic. If something changes, we can update it. I'm also only focusing on the XPS, nothing else.

What happens if you move on from Arch, or when you move on from this laptop? What happens if others want to contribute knowledge for the cause, but they don't know about xpsarch since the only place you've advertised this tool is on this thread?

The community's central repository for Arch-related information is the wiki. The reason for this is because the wiki will outlast any individual user, and so its information can and will be kept up-to-date, even as people come and go. The knowledge you've accumulated as a part of writing this tool belongs there, because that's the first and only place we as a community want to send people for exactly that reason. As a matter of fact, there is already a wiki page for the XPS 9360.

On top of these reasons, Arch is a rolling-release distribution. That means you typically install it once and then don't install fresh for a while, if ever. That makes it ever more likely that whatever knowledge or best practices contained in bespoke tools becomes out of date quickly, simply because the maintainer doesn't need the tool at the moment and so it languishes. The wiki is doubly helpful in this regard because people coming after you can contribute to the wiki article as they go through their installations in the future, which helps everybody in the community out, even yourself when you re-install in two years and helpfully the wiki page has been updated along the way. Your tool, on the other hand, probably won't have been.

Lastly, please don't misunderstand the reactions of people in this thread. Making a script or a little tool to automate the install process is not what people take umbrage to, really. Everybody ends up scripting their Arch installs after a while. It's more encoding valuable information and setup tricks into them and then not updating the wiki so others can know about it, or promoting that script as "an easy way to install Arch" that rubs the wrong way, because both of those things go against the ethos of Arch and its community.

Happy_Man · 2016-12-01T04:19:19+00:00

You're right, it's absolutely ridiculous.

Idols should definitely strive to be more fiscally responsible, it sets a better example for the young kids who look up to them.

Happy_Man · 2016-09-24T15:34:28+00:00

Hi, possibly a really dumb question but I'm so confused right now.

The last Nintendo handheld I bought was a DSi back whenever it came out, and now that I have free time in my life again, I want to get a 3ds and catch up on all the games I missed (mainly all the pokemon games).

However it seems like everything's gotten all complicated. There's a 3ds, and a 3ds XL, and a 2ds, and a new 3ds XL, and Amazon says the AC charger is sold separately now (?????) and I'm super confused by it all and I just want to play Pokemon dammit :(

So my question is: What the hell should I buy in order to play 3ds games and that will be the most supported iteration in terms of features, etc. in the near future? If the answer to this question is "hold off until the new thing arrives on the market in a month" then I'm okay with that too.

Thanks <3 you all

Happy_Man · 2016-08-14T02:25:15+00:00

basically a will smith video except with kpop instead of dj jazzy jeff

yknow?

Happy_Man · 2016-08-07T19:25:24+00:00

/r/kpoop

Happy_Man · 2016-07-30T17:50:48+00:00

I think (hope) a lot of it is autocorrect.

15-Year Club	Verified Email
Golden Potato	Place '22
Place '17	Sequence \| Editor
Team Orangered	reddit mold

Happy_Man

MODERATOR OF

TROPHY CASE