codys

9 ms·

61.
by codys 1y ago
Were there any Microsoft XP security issues caused by "Easter eggs" prior to that policy change? Or was this just put in place as a policy because it was easy to put in place?
62.
by codys 1y ago
I agree that there are problems when laying multiple build systems on top of one another, and I see that often as a user of nix (it's also bad with rust projects that use cargo, and though there are a variety of options folks have writ
63.
by codys 1y ago
True. That isn't something the compiler can do. That said, that (determining the c flags and ld flags for dependencies) is something that might be able to be mixed into compilation a bit more than it is now. Could imagine that if we an
64.
by codys 1y ago
yep. C's really come a long way with the special operators for checking if attributes exist, if builtins exist, if headers exist, etc. Covers a very large part of what is needed, making fewer and fewer things need to end up in configur
65.
by codys 1y ago
I did something like the system described in this article a few years back. [1] Instead of splitting the "configure" and "make" steps though, I chose to instead fold much of the "configure" step into the "
66.
by codys 2y ago
On audio sync issues, I unfortunately see them with jellyfin rather frequently on apple tv when using homepods as audio output. I end up having to enable the "native player" in the experimental settings to get the audio in-sync. I
67.
by codys 2y ago
This is a fundamental misunderstanding of the structure of the linux kernel, the nature of kernels in general, and the ways one performs automated verification of computer code. Automated verification (including as done by rust in it's
68.
by codys 2y ago
If it was a good approach, the C folks would have copied around C files instead of having common core code. They did not do that though, because it'd be counter productive due to increasing maintenance burden. Everyone knows it would i
69.
by codys 2y ago
It's not charitable to construct a contrived situation no one is talking about and place that into the mouth of a commenter.
70.
by codys 2y ago
The commenter appears to have been referring to a specific law in the netherlands without stating this.
71.
by codys 2y ago
The original Firefox sync worked like this (with a unique code and pairing instead of an explicit account) (this is so on the nose I suspect you may know this). This blog post goes over some of that history: https://blog.mozilla.
72.
by codys 2y ago
> Finally, as I imagine it, mixing 32- and 64-bit time_t ABIs would be prohibited — implicitly, as 64-bit time_t symbols aren't ever visible to 32-bit time_t code and vice versa — with code that needs to support non-native time_t va
73.
by codys 2y ago
Presumably one wouldn't throw away the built packages if some other build fails just because we're delaying installing the packages to `/` until later.
74.
by codys 2y ago
Huh. If it's OK to have instructions like those for users to run through, then I guess I don't understand what's holding up switching to 64-bit time_t for gentoo. Seems like they could make a new profile and tell folks to dea
75.
by codys 2y ago
Before getting into the details here about why we need to read `libA.so` at build time: Perhaps the documentation gentoo provides about `ROOT` that was noted by rini17 is incorrect/misleading and `ROOT` is used as the source of build t
76.
by codys 2y ago
Fat binaries (packing together 2 entirely different objects and picking one of them) could potentially work here, though I suspect we'd run into issues of mixed 32-bit/64-bit time_t things. Another option that's closer to how
77.
by codys 2y ago
No, what rini17 pointed out is a problem here, and I think my previous comments that setting ROOT might be "part of a solution" are less accurate (as it seems `ROOT` is even less of a complete solution here). Lets consider this hy
78.
by codys 2y ago
Simply changing `ROOT` doesn't magically enable us to have `emerge` update our normal `ROOT=/`. There's extra steps here (the syncing, the bind mounting, etc) for the `emerge` with a custom `ROOT` to do an update to `/`
79.
by codys 2y ago
It's true that Gentoo has some pieces of what they need to build an implementation of option 1 (build packages that depend on other packages before completeing an install), but it's currently the case that that is not what happens
80.
by codys 2y ago
nixos is an example of a distro that is source based and can do the atomic rebuild here because it has a way to build packages against other packages that aren't "installed". In nixos, this is because there are very few thing
81.
by codys 2y ago
Yep, agreed. Though it does expose an option here which would be "have glibc provide a mechanism for other libraries (likely more core/widely used libs) to support both ABIs simultaneously. Presumably if that had been done in glib
82.
by codys 2y ago
Nixos has it easier here because they don't require packages to be "installed" before building code against them. For Gentoo, none of their build scripts (ebuilds) are written to support that. It's plausible that they mi
83.
by codys 2y ago
There are a few options for Gentoo not discussed in the post, possibly because for Gentoo they would be a larger amount of work due to the design of their system: 1. Allow building against packages without installing them. The core issue he
84.
by codys 2y ago
> there would be inconveniences like libc.so has 64-bit off_t glibc specifically has support for the 32-bit and 64-bit time_t abi simultaneously. From the post: > What’s important here is that a single glibc build remains compatible w
85.
by codys 3y ago
iOS has limited extra settings for notifications that are "time sensitive" and "direct messages", mostly to allow excluding them from notifications summaries and sending them immediately. It doesn't have the same ri
86.
by codys 3y ago
One thing to be cautious about with cake/fq_codel is that many consumer routers aren't fast enough to run it at line rate for current "fast" networks, so that enabling it those routers effectively caps the throughput low
87.
by codys 3y ago
> But I recall reading elsewhere a discussion about some userspace program which did depend on holes being present in the filesystem as actual holes (visible to SEEK_HOLE and so on) and not as runs of zeros. "treatment of on-disk se
88.
by codys 3y ago
The things you've described are either not required or often considered bad style in C even though they are valid C. Casting to/from `void *` isn't needed in C, and is commonly against coding conventions, like those used by t
89.
by codys 3y ago
Sure, you're right, it's just not really relevant here.
90.
by codys 3y ago
Nothing stops that. You'll end up getting a message full of 0 bytes (messages are fixed size) if it closes between the `closed()` check and the `receive()` operation. Common designs in this space instead indicate if the receive call ha

More ›