326
points
secure
Joined 5,199 karma
- No, the company has not always referred to itself in all capitals.
https://forums.tomshardware.com/threads/nvidias-name-change....
When I got to know their products, they were nVidia.
- 2 points
- 252 points
- Was it vroom by any chance? A slot car racing game in space: https://nixdoc.net/man-pages/irix/man6/vroom.6.html
Video:
- Thanks for your reply!
Can I suggest that we ask todsacerdoti to add a filter to their cross-posting thingie that skips articles that the author posted to HN?
I’m asking because todsacerdoti’s posts of my content always seem to be the ones that get traction, no matter if I post first on HN or lobsters. In fact, I’m wondering how he can even submit when I have already submitted — why isn’t his post marked a dupe? (To be clear: this was for my prior submissions, not this particular one.)
- > If OP's CPU cooler (Noctua NH-D15 G2) wasn't able to cool down his CPU below 100C, he must have been (intentionally or unintentionally with Asus multi core enhancement) overclocked his CPU. Or he didn't apply thermal paste properly or didn't remove the cooler plastic sticker?
I did not overclock this CPU. I pay attention to what I change in the BIOS/UEFI firmware, and I never select any overclocking options.
Also, I have applied thermal paste properly: Noctua-supplied paste, following Noctua’s instructions for this CPU socket.
- HN mods, can we please finally ban this cross-posting bot called https://news.ycombinator.com/user?id=todsacerdoti?
This is my post, and my own submission got marked as a “dupe” (https://www.hackerneue.com/item?id=45155986).
On every blog post I post, todsacerdoti steals my post. It’s a bot. Why isn’t it banned?
- 345 points
- SuSE Linux (around since the 90s) had such a single-layer-manages-everything approach, so yes, it’s not a new concept.
I used to think that you don’t need Nix to get most of the benefits that Nix/NixOS are known for. And to a certain extent, that’s true — you can achieve much in other scenarios. But by now, I think the reason why Nix/NixOS work well and deliver these powerful abstractions is because they are Nix all the way down, giving you an unparalleled level of integration/reach for your declarative layer.
- Yes, I use this same config snippet throughout my installs and haven’t gotten around to managing my home with Nix yet.
Later, I refactored this config snippet into a Flake that I include: https://github.com/stapelberg/nix/ …but that’s for a follow-up blog post :)
- Welcome to Linux!
I agree that through the lens of “how much time do you save?”, automating a NixOS installation is not worth it. As you describe, it’s just a few interactive commands in the upstream installer.
But from the perspective of “how much effort is it to spin up a new VM for this new project / task?”, spending the extra few minutes on building the fully automated installation path is well worth it. Also consider the perspective of “how many steps does it take to recover this VM in a disaster scenario?”, where reducing the manual steps to a minimum is very helpful.
BTW, the maintenance of the installer is virtually free: The configuration I show is the configuration I use in NixOS as well, so that needs to be updated anyway. Aside from that, to rebase my installer from NixOS 24.11 to NixOS 25.05, I just changed a number. When setting up a new machine, I can either download the upstream installer and write it to a USB stick, or I can change a number, rebuild (< 2 minutes) and write to a USB stick. Really not much difference.
- > Almost none of the packages the author listed get used, including zsh
Just to clarify: the point of having packages like lshw and zsh available is not for the case of performing the automated installation (where, yes, they are not used), but for the case where I want to interactively poke around in a booted installer to inspect the target system.
- Yes. I also submitted my article myself (https://www.hackerneue.com/item?id=44148997), but the upvotes came in on this duplicate submission.
I don’t know who todsacerdoti is, but looking at their submission history, it looks like this account automatically cross-posts from other sites (maybe lobsters?)
- 164 points
- > It isn't clear to me but is the author indicating that Linux kernel support for 2.5GbE is still early stages, would it be better to wait a while before getting a motherboard with 2.5?
If you want to play it safe, waiting longer before buying new hardware is always a good strategy. As I wrote, though, aside from needing a new firmware package, I did not notice any issues with the 2.5G support in the end.
> There's a diff being presented between two lshw outputs? How is that diff shown?
I ran lshw > lshw-intel-285k-asrock.txt when I used the ASRock board and lshw > lshw-intel-285k-asus.txt when I used the ASUS board. Then I ran diff -u lshw-intel-285k-asrock.txt lshw-intel-285k-asus.txt and copy&pasted (parts of) the output into the blog post.
- 26 points
- Thanks for the advice. I try switching to Wayland every year, but it has never worked without heavy graphics artifacts / flickering / glitches on any of my machines (I use an nVidia GPU so that I can drive my Dell UP3218K monitor).
Meanwhile, X11 works really well for me. No tearing, no artifacts, no breakages on upgrades. Really can’t complain.
Maybe next year.
> By the way, when I mentioned that GNOME successfully configures the native resolution, that doesn’t mean the monitor is usable with GNOME! While GNOME supports tiled displays, the updates of individual tiles are not synchronized, so you see heavy tearing in the middle of the screen, much worse than anything I have ever observed under X11. GNOME/mutter merge request !4822 should hopefully address this.