

Only if you’re working with SCSI hardware. On Linux, SATA (and probably PATA) devices use the same kernel driver as SCSI, and appear on the system as SCSI hosts. You can find them in /sys/class/scsi_disk
or by running lsblk -o NAME,HCTL
.
I take my shitposts very seriously.
Only if you’re working with SCSI hardware. On Linux, SATA (and probably PATA) devices use the same kernel driver as SCSI, and appear on the system as SCSI hosts. You can find them in /sys/class/scsi_disk
or by running lsblk -o NAME,HCTL
.
Broke: /dev/sd*
Woke: /dev/disk/by-id/*
Bespoke: finding the correct device’s SCSI host, detaching everything, then reattaching only the one host to make sure it’s always /dev/sda
.
I’ve had to use all three methods. Fucking around in /sys
feels like I’m wielding a power stolen from the gods.
kill
automatically sends SIGTERM
(15) if no other signal is specified. It’s the gentle way to terminate a process.
I’m going to guess you’ve never been part of a project with complexity and sheer black magic fuckery comparable to Ventoy. The developer (a singular person) had to make a choice between:
I’ve read the original issue thread front to back, and it’s a fucking clown show. I can’t blame the developer for not wanting to engage with those people. Nobody is entitled to the developer’s time or attention. Right now the issue is being worked on, which is more than most of the whiners can say about themselves; if you think that’s still insufficient, do better.
Whichever pocket doesn’t conain the keys.
And the keys go in whichever pocket doesn’t contain my phone.
Yes, but people have concerns. Ventoy is fully open-source, but the build process pulls binary blobs (compiled executables, think of them like blob chips) from other F/OSS projects, which is an issue for some people. They have legitimate concerns about trusting Ventoy because they have to implicitly trust the projects that Ventoy pulls from but can’t verify what is getting pulled. If such a project were to become compromised (the way XZ-Utils was), it would eventually spread to Ventoy.
That being said, the developers (or singular developer, not sure) are taking steps to reduce Ventoy’s dependency on external blobs. It’s a difficult task and they have limited resources, but they have acknowledged that it is an issue and are working on a solution.
I don’t see an egress airlock… wonder what it means.
Sophistry. Reduce everything to the most technically accurate description if you like – slop will still be slop.
As long as it’s not watery diarrhea brown (a.k.a “gruvbox”), I’ll take it.
My immediate reaction was “yeah, that tracks”.
I don’t see how this might be interpreted as misinformation (8) or any attempt to do harm (8.1) either to a prospective user or Nix itself. Nor do I see how this might be an attempt made or supported by the Nix developers to influence the greater community. If you have evidence to the contrary, produce it.
There is no denying that a vocal group of people are promoting immutable/atomic distributions, or that many are fans of Nix’s declarative configuration solution. Still, that makes it no worse than the people who are pushing back against the adoption of Rust in the Linux kernel, or the proliferation of systemd services, or the adoption of Wayland over X11.
What about LCD? Switching the state of a cell results in mechanical changes, which might influence how much sunlight it absorbs (even if it’s minuscule compared to the heat generated by the backlight)
Probably a precision tool, like a bandsaw or angle grinder.
Nice report for “astroturfing”. Please go ahead and point out which rule was violated so I can make a decision.
There was some politically charged drama… I think. There was some drama, anyway. I’m not clear on the details.
It was probably a Twitter-tier disagreement that was blown way out of proportion by a small group of people. If others have details, please don’t enlighten me, I value my ignorance.
It’s a fucking joke, mate.
Yes. Mass deployment using Clonezilla in an extremely heterogenous environment. I had to make sure the OS got installed on the correct SSD, and that it was always named
sda
, otherwise Clonezilla would shit itself. The solution is a hack held together by spit and my own stubbornness, but it works.