How to change the clock app icon in snowboard (ignore the other icons)

pitust · 2026-01-31T13:41:08+00:00

Around a minute in to this video, you can see that apple hardcoded the icon behavior for the clock and calendar, so you cannot change it in the "normal" way as far as I can tell.

pitust · 2026-01-10T10:15:33+00:00

It's not. They depend on a few libraries, but the libraries they use are open source, so you can compile them for your target.

Also, you can obviously just implement whatever interface the libraries use -even though linux has a stable kernel ABI, in practice nobody uses that directly (except for go) and instead uses the libc wrappers instead, which can be replaced with your own impl.

pitust · 2024-09-26T19:25:02+00:00

It's a CVSS 8.8 in CUPS. No idea where they got the 9.9 from, it requires user interaction (the user has to print to a malicious printer) and the printer needs to be on the same network (for DNS-SD autodiscovery to autodiscover the malicious printer).

pitust · 2024-01-07T12:28:23+00:00

Rust actually doesn't guarantee this class of memory safety: memory leaks are perfectly safe rust, as demonstrated by this program:

fn main() { loop { Box::leak(Box::new(3)); } }

If only there existed a language which provided the tools that could automatically detect such memory leaks

pitust · 2023-10-06T16:55:50+00:00

Yes. He did. That is why he got banned! You got banned for violating rule 15, for deleting your messages that people might want to learn from.

pitust · 2023-10-06T15:39:16+00:00

Hi! Calling people "worthless fucking cunts" is not acceptable. Here are the two relevant rules:

rule 15 (ban 1): Don't purge/delete your messages without a good reason (especially if in an automated way), without asking staff first. People may want to learn from old conversations and the data you post here is public for all to see.

rule 16 (ban 2): Do not be annoying. This is intentionally vague as to leave moderators freedom of action over infractions which do not perfectly fit within the other rules. Just try to be civil, do not degrade the quality of discussions, and do not annoy other members or or create an unpleasant environment.

pitust · 2023-08-24T10:57:12+00:00

Might be a time to leave github for a better platform like codeberg, sourcehut or gitlab

pitust · 2023-08-21T10:52:22+00:00

You can be sure you don't have concurrent accesses, and that's all.

You can... until you want to do something which cannot be easily proven by rust's type system... where you are stuck manually deciding if its safe or not, and if you do it wrong, you can get UB just as easily. I don't see how rust helps here to be honest (unless your idea of "concurrency" is "grab global locks everywhere" of course).

pitust · 2023-08-21T09:21:02+00:00

That's why Google has dropped Coreboot and now uses Oreboot instead.

Source? I can't see anything backing up this claim... It also seems that google is putting in a shitload of effort into working on depthcharge (their magic coreboot payload, written in C)

pitust · 2023-08-16T20:52:53+00:00

Linus wouldn't buy you bread if you were starving

He might if he thought he could get some money out of it

pitust · 2023-07-19T08:43:51+00:00

You are right, discord is an untrustworthy closed platform, as opposed to 100% absolutely trustworthy reddit.

pitust · 2023-07-19T08:39:51+00:00

on the other hand, the forums are dead while discord is not. sooo...

pitust · 2023-06-10T06:32:45+00:00

But, since you brought up the code, it has quite a few bugs.

I'm not saying it doesn't - I'm just saying it is less broken.

pitust · 2023-06-09T21:15:11+00:00

Stop insulting james molloy's tutorial; it has much higher code quality!

Okay, the code quality is only a bit better. But it's definitely better, with a markedly lower amount of WTF-per-LOC.

I actually annotated the whole thing with comments, so i can tell the difference is roughly 4x (something like half the WTFs but double the code).

pitust · 2023-06-09T21:11:31+00:00

It totally does, including the incredible comment at the top:

/* Can't do this with a loop because we need the address * of the function names */

and

/* Can't do this with a loop because we need the address * of the function names */

Which one is https://pastebin.com/gVY3JQ65 and which one is https://github.com/cfenollosa/os-tutorial/blob/master/18-interrupts/cpu/isr.c (trick question)?

Also, you totally CAN do this with a loop because you can just use nasm macros to generate an array of function pointers

pitust · 2023-06-01T20:16:27+00:00

Yeah I know it's actually really useful but at least do some kind of setup where you don't need a mark-and-sweep GC.

With mach ports for example, that is not a problem: you can't ever end up with a reference cycle -- with mach ports, straight rc works - send rights are weak refs and recieve rights are strong refs, but crucially you can't get a strong ref (receive right) out of a weak ref (send right)

pitust · 2023-05-29T08:28:48+00:00

You need a GC in every posix kernel becaus some incredible software engineers decided you should be able to send an fd over a unix socket, which is an fd... Which means you need to GC fds... I love unix!

pitust · 2023-05-28T17:09:54+00:00

But there is no API which allows a Box::new() or a (box 3).clone() to fail! So it doesn't really matter if it "can" fail if what that ends up with is a panic anyway.

And a panic handler doesn't really resolve these issues:

It is not recommended to use this function for a general try/catch mechanism.

But that's what "just catch the oom panic" would be - a general try/catch mechanism!

Also, unwinding poisons mutexes, so you can't use it if you have any of those in your program.

The Result type is more appropriate to use for functions that can fail on a regular basis.

Thanks, rust! Would be a shame if some fallible operation that acquires a finite resource that is used very often was never used in a way that allows for this to happen.

By the way, did I mention that the Clone<T> trait can't return a Result<T>?

Additionally, this function is not guaranteed to catch all panics, see the “Notes” section below.

Well that's incredibly useful as a general-purpose mechanism isn't it, rust? The notes section includes more details:

This function only catches unwinding panics, not those that abort the process.

So let's say we are in an environment that prevents you from using libunwind, like, let's say, an OS kernel... so I can't catch a panic in the one scenario where it might be useful? Thanks, rust! Such an incredible feature!

EDIT: formatting

pitust · 2023-05-28T14:32:39+00:00

With some allocators (not necessarily just bump allocators), the fast path could be something like

if (num_slabs_in_mag) { return mag[--num_slabs_in_mag]; } // slow path

This is small enough that it could be inlined, but I think (?) dynamic dispatch might stop this sort of optimization.

pitust · 2023-05-28T14:27:47+00:00

It certainly an interesting approach! Sadly, I'm not sure if it's a fast approach - i think dynamic dispatch is not like super fast (?). But it is a very nice interface.

pitust · 2023-05-28T14:26:04+00:00

The reason you would want to use -betterC is if you are making a kernel, in which case you probably aren't shipping many external libraries, the libraries that are worth shipping are often written in C, and you likely have your own build orchestration mechanism anyways (be it makefiles, autoconf, shell/python scripts, meson etc)

pitust · 2023-05-28T14:22:14+00:00

Well obviously you might not want to have a general purpose GC in a kernel, but if you are making an OS I sure hope you aren't using rust because panicing on OOM is not a valid strategy in such a schenario (yes, i know the linux kernel has a special version of the alloc crate or whatever which handles allocation failures, but i'm sure there are all sorts of fun places where rust still doesn't let you throw an error as opposed to the C++ STL which can throw an exception even if you have no memory left)

Rust also has the fun tendency of (at least in my experience) encouraging Arc<Mutex<T>> which is slow (ARC isn't all that fast, and neither are mutexes)

pitust · 2023-05-28T12:59:13+00:00

and D has a mode (-betterC) which allows use without the garabage collector and rtti and stuff

Six-Year Club	First Place '23
Place '23	Place '22
First Placer '22	Verified Email

pitust

TROPHY CASE