Jarkko Sakkinen
Posts
4564Following
317Followers
476OpenPGP: 3AB05486C7752FE1
@anotherwalther NCC Group actually blog articles only few days ago still available with really good architecture insight on the use of Rust in Linux. It had comparisons to C constructs too, which made the reasoning sound.
I have no idea why they removed this great series but it was with the topic "Rustproofing Linux". I only recently bumped into them. It was kind of material that would be nice if NCC would contribute it to the kernel documentation. At least for me cleared up bunch of things that I did not get before.
I have no idea why they removed this great series but it was with the topic "Rustproofing Linux". I only recently bumped into them. It was kind of material that would be nice if NCC would contribute it to the kernel documentation. At least for me cleared up bunch of things that I did not get before.
1
0
1
Jarkko Sakkinen
jarkko
Good to know enjoyed this article, https://it-notes.dragas.net/2024/08/29/make-your-own-cdn-openbsd/
0
0
0
@anotherwalther Sorry for going over the top with this :-) I think this is still one of the best and easiest ways to improve the situation.
[and even if documentation sucks that does not give right to be asshole]
[and even if documentation sucks that does not give right to be asshole]
1
0
1
Jarkko Sakkinen
jarkko
Yet another audio post. this is my basic "per-channel" use case for tape emulation. I care about the eq curve here mainly. for most sounds you want to soften the top and bottom.
It is like perfect placeholder EQ + saturation for a channel. Then by adjusting mixer gain I can go a long way before doing anything more sophisticated :-)
It is like perfect placeholder EQ + saturation for a channel. Then by adjusting mixer gain I can go a long way before doing anything more sophisticated :-)
1
0
2
@anotherwalther And even some of the existing documentation looks like README for a Github project. Consider e.g.
https://docs.kernel.org/rust/coding-guidelines.html
For a regular kernel developer or maintainer the first question is obviously how do I apply kernel doc comments here? The page neither explicitly state whether RST or MD is used for the function header comments. With the current information I'd be already lost before writing a single line of code because the documentation is not explicit in conventions.
https://docs.kernel.org/rust/coding-guidelines.html
For a regular kernel developer or maintainer the first question is obviously how do I apply kernel doc comments here? The page neither explicitly state whether RST or MD is used for the function header comments. With the current information I'd be already lost before writing a single line of code because the documentation is not explicit in conventions.
1
0
0
@anotherwalther I most blame #Microsoft and #Google for this if any entity because they are key sponsors in Rust specifics. They are handling their kernel teams internally badly. I.e. not blaming the developers themselves.
1
0
0
@anotherwalther OK I get that, BUT my comment is totally orthogonal and almost universal truth. It works everywhere else in the kernel.
Integrate documentation updates as part of the patch review process. Not a big deal.
Obviously toxic behavior is bad but also reach and approachability of Rust-for-Linux is not in a great state, and this only because documentation has not been a priority so far. People tend to evade things that they don't know what they are.
It would not be very educated to think that the problem is only on kernel developers who are not contributing to Rust-for-Linux (which is not same that saying that any bully behavior would be acceptable in any possible situation).
Integrate documentation updates as part of the patch review process. Not a big deal.
Obviously toxic behavior is bad but also reach and approachability of Rust-for-Linux is not in a great state, and this only because documentation has not been a priority so far. People tend to evade things that they don't know what they are.
It would not be very educated to think that the problem is only on kernel developers who are not contributing to Rust-for-Linux (which is not same that saying that any bully behavior would be acceptable in any possible situation).
1
0
0
Jarkko Sakkinen
jarkko
@anotherwalther I really don't know, and I'm not part of that, but I think better integration between documenting and implementing features would help a lot to clear up misconceptions.
Take almost any subsystem, like PCI documentation for instance, and it should be clear that this blocks bi-directional communication: https://docs.kernel.org/rust/
Take almost any subsystem, like PCI documentation for instance, and it should be clear that this blocks bi-directional communication: https://docs.kernel.org/rust/
1
0
0
Jarkko Sakkinen
jarkko
Essential tool with #Storj: https://cyberduck.io/
I guess everyone knows this who has used AWS but I experienced S3 storage first time ever last March :-)
#cyberduck
I guess everyone knows this who has used AWS but I experienced S3 storage first time ever last March :-)
#cyberduck
0
0
0
@jjdavis a classic in this arena is https://github.com/philipl/pifs
0
0
1
Jarkko Sakkinen
jarkkoTo save some time upgrading all U-he plugins I did:
#!/usr/bin/env bash
set -e
wget -q --show-progress -r -np -nd -l1 -A Mac.zip https://uhe-dl.b-cdn.net/releases/ -P dl/
for file in dl/*.zip; do unzip -j -o "$file" -d staging "*.pkg"; done
for file in staging/*.pkg; do sudo installer -pkg "$file" -target /; done
1
0
0
Jarkko Sakkinen
jarkko
Edited 11 months ago
Not a new one but interesting read (also part 2):
https://research.nccgroup.com/2023/02/06/rustproofing-linux-part-1-4-leaking-addresses/
https://research.nccgroup.com/2023/02/06/rustproofing-linux-part-1-4-leaking-addresses/
0
0
0
Jarkko Sakkinen
jarkko
This is great because MPE-parameters can be misused as automation parameters :-) Less automation curves better...
https://u-he.com/news/#mpe-update
https://u-he.com/news/#mpe-update
0
0
0
Jarkko Sakkinen
repeated
repeated
daniel:// stenberg://
bagder@mastodon.social
Edited 11 months ago
Beware, there is an ongoing spambot attack in #GitHub issues in several projects were random people suggest "the fix" is to download a random file from mediafire.com. Like this:
8
9
0