Posts
1971
Following
226
Followers
2463
Director of Linux Foundation IT. Currently in charge of kernel.org infra.

This account is for Linux/Kernel/FOSS topics in general: #linux, #kernel, #foss, #git, #sysadmin, #infrastructure.

For my personal account, please follow @monsieuricon@castoranxieux.ca.

Montréal, Québec, Canada 🇨🇦🇺🇦
monsieuricon

K. Ryabitsev 🍁

I received feedback to the patches I sent with b4. Hooray, this is actually not guaranteed (but that's a different problem).

In this follow-up video I show how to work with feedback and submit a v2 of your patch.

(I moved my mic stand, so your ears should be okay this time, even in headphones.)

https://youtu.be/-Vld9aoFPwU
0
2
6
monsieuricon

K. Ryabitsev 🍁

Weird fact about me: I'm a certified baseball umpire.
1
0
3
monsieuricon

K. Ryabitsev 🍁

Should I switch to akkoma on social.kernel.org?
24% yes, go akkoma!
9% no, stick with pleroma!
66% No opinion, I just like voting in polls!
1
1
2
monsieuricon

K. Ryabitsev 🍁

Bah, I've recorded the video of submitting the patch using "b4 send", but I didn't think to check what the mic picks up when I'm typing on the keyboard. I apologize for any headaches caused to those listening via headphones.

If you wait a bit, there will be a text write-up on people.kernel.org that you can follow instead of watching the video.

https://www.youtube.com/watch?v=QBR06ml2YLQ
0
4
9
monsieuricon

K. Ryabitsev 🍁

Not entirely surprisingly, attempting to record a "sending a Linux patch from scratch" tutorial video identified a couple of annoying crashers in b4 when some configuration parameters are missing (like, a [sendemail] section -- not identified in previous testing because everyone obviously has a [sendemail] section in their .gitconfig :)).

I'll release b4 0.11.1 with more helpful error messages tomorrow and try to re-record the video again.
0
0
3
monsieuricon

K. Ryabitsev 🍁

Are you someone who has a simple fix for something in the Linux kernel, but haven't bothered submitting a patch because you find the email workflow daunting? Can be a bugfix, spelling correction, anything at all.

If so, I want to talk to you! I have tools that simplify this process quite a bit, but I need more feedback from people who aren't long-term Linux maintainers.

Please reach out, either via here or by emailing mricon@kernel.org.
9
426
333
monsieuricon

K. Ryabitsev 🍁

Um... whoever is running the "bluez test bot" on bugzilla.kernel.org should probably exclude bugs older than a certain age. Just sayin'.

https://bugzilla.kernel.org/show_bug.cgi?id=7
0
3
5
monsieuricon

K. Ryabitsev 🍁

Santa: So, have you been naughty or nice?
Me: Oh, I've been naughty, Santa.
Santa: Oh, really? And how so?
Me: When replying to emails, I've been writing below the "Please do not write below this line".
Santa: What kind of monster are you?
0
3
5
monsieuricon

K. Ryabitsev 🍁

b4 0.11.0 is available

Many improvements to the contributor-oriented features (b4 prep, b4 trailers, b4 send). If you haven't tried those out yet, please check them out, they are documented here:

https://b4.docs.kernel.org/en/stable-0.11.y/contributor/overview.html

Release announcement:

https://lore.kernel.org/tools/20221219213715.2qozw5emt5j7t3xr@nitro.local/

#b4
0
3
8
monsieuricon

K. Ryabitsev 🍁

Would #JohnMastodon be considered a megafounder? 🤔
0
2
7
monsieuricon

K. Ryabitsev 🍁

PSA: just having a DKIM-Signature: header in your email isn't really enough, unless it has a d= part matching your From: address.

E.g., this is good:

From: foo@example.com
DKIM-Signature: v=1; d=example.com; [...]

This, on the other hand, serves no real purpose outside of Google:

From: foo@example.com
DKIM-Signature: v=1; d=example-com.20210112.gappssmtp.com; [...]

When there is no DKIM alignment, DMARC-enforcing servers will fall back to only using the SPF record, which doesn't work at all with mailing lists unless they rewrite the From: header.

So, please-please properly set up your DKIM infrastructure if you send messages to mailing lists. Or at the very least don't put p=reject into your DMARC policy.
0
0
5
monsieuricon

K. Ryabitsev 🍁

Does the Tesla executive board loudly beep at you when everyone's asleep at the wheel? I think we're at the point where they have to consider cordoning off the Twitter dumpster fire.
0
0
2
monsieuricon

K. Ryabitsev 🍁

I need a "don't blame me, I bought this car before Elon went gaga" sticker.
0
0
5
monsieuricon
repeated
LinuxSecSummit

Linux Security Summit 🐧

📢

The #LinuxSecuritySummit announcement channel has moved here, to social.kernel.org, from Twitter (previously: https://twitter.com/LinuxSecSummit).


#kernel #linux #security #infosec #selinux #apparmor #smack #landlock #lsm #linuxfoundation #lf #conference
0
10
8
monsieuricon

K. Ryabitsev 🍁

Why is Google Groups "Collaborative Inbox" *SO BAD*? It feels like a summer intern project that was abandoned 10 years ago.
0
0
0
monsieuricon

K. Ryabitsev 🍁

I did a lot of tweaking and then a lot of untweaking to social.k.o database and elixir backends this morning. Hopefully, this had a net positive result -- many queries are a lot faster now.

Sorry if you had a rough ride in the past few hours. #meta
0
0
0
monsieuricon

K. Ryabitsev 🍁

Desire to switch to akkoma increasing.
0
0
2
monsieuricon

K. Ryabitsev 🍁

Apparently, running some of the "database maintenance tasks" can seriously peg pleroma's database backend. I think I managed to fix most of the problems that caused. Sorry if you've been getting 500 errors.
0
0
0
monsieuricon

K. Ryabitsev 🍁

I didn't end up releasing b4-0.11 today, since I ended up rewriting some hurky code in it and it needs to go for another round of testing.

Hopefully, 0.11 will be out on Tuesday.

#b4
0
1
1
monsieuricon

K. Ryabitsev 🍁

Sometimes you write a piece of code that is "hacky," but kinda clever. Well done.

Other times, you write a piece of code that is both a nasty hack and really quite terrible to look at. That code isn't just hacky, it's downright "hurky." It's called that, because that's the sound you make at the back of your throat when you look at it.

I may be the only person who says "hurky," but now you can start saying that, too.

You're welcome.

(Hopefully in the context of fixing hurky code, not writing it.)
2
2
3
Show older
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: