Video

Awesome work.

If the card doesn't want to reinit, why would you try? Set it up the do the initial init, then keep the init-ed instance around under the notion that one use guarantees more use. Just lie to it. Sweet sweet lies.

I enjoyed that a lot , I love Dan's demeanour.

I'm gonna check out `show running-configuration` now

Good talk

He is probably a very knowledgable guy, but presenting and answering questions is a mess.

Thank you for sharing your love! ❤

great , another presentation by a BSD fanboy telling everybody else they are dumb i have wonder what OS is he running on his desktop/laptop 😆

while a FreeBSD user is served at 0kb/s as they can't watch Netflix on their beloved OS.

when i was new to ZFS, i didn't understand the difference between pools and vdevs too. vdevs is where you implement redundancy, either through mirroring or parity (raidz). multiple vdevs is how you expand the usable storage of a pool (until raidz expansion ships). if any vdev fails, all of your data from the pool is inaccessible. besides expansion there is a second reason for why you might want to create a pool from multiple vdevs instead of a single large one: raidz resilvering (i.e. after replacing a faulty drive) is extremely straining on all drives of the faulted drive's vdev. if you put 20 drives into a single vdev for a pool, resilvering will add wear to 20 drives. if you instead do 2 vdevs with 10 drives each, a resilvering will only add wear to 10 drives etc. so vdev arrangements are also relevant for wear and risk management.

"device registers are kind of like locations in memory" the point is that they are _meaningful_ locations in memory, not just bytes to store some software state. So, it is not like an _array_ of ints, it is more like a _struct_ of ints with meaningful names. What's worse, often the meaningful part is the _bitfields_ inside the registers, not the registers themselves. C does not have a nice language semantics to support that.

25:20 can someone explain what he's saying here? it doesn't make much sense to me. To me it sounds like he says, only put your os on zfs and your actual data on other non zfs filesystems. But this is a zfs talk so that doesn't make much sense. Then I looked up UFS and found unix file system, so he's saying to put like a virtual filesystem on top of zfs and boot from that? and what is the HBA he's refering to? also booting from motherboard?????

this was awesome, thanks for sharing!

Good to see Beckhoff here, it's one of the few German tech companies I actually like.

his accent sounds like he's about to cry talking about the absurd audits the entire time

I have the original MINIX book, just because its one of the first OS books in my collection. It started long ago with the 5 1/2" floppies in the back of the book.

This is the most amazing piece of software one person can build in our time. Thank you for this amazing project.👍

Very cool and informative talk. We need more talks like these to create a new generation of developers.

Great to see the man behind the magic! A perl to be sure. BTW do you, Marc, contribute upstream to the Perl language development?

Just started watching this immediately after watching stein's 36c3 talk "A systematic evaluation of OpenBSD's mitigations", in hopes of finding out what had been done since to address the concerns he raised. Perhaps I'm simply too plebeian to see it [or I haven't gotten to it yet - ed.], but it doesn't look like anything's changed. The mitigations discussed here are the exact same as there, and don't appear to have gone through any improvement since 2019.

Amazing presentation. Thanks a lot 👍

👏🏻👏🏻👏🏻

👏🏻👏🏻👏🏻

The audio is incredibly quiet. I almost can't even hear it on my cell phone.

A lot of content for 1 hr. Just wondering...there is a lot of talk about physical hardware and VM specs. How do you reconsider all of these hardware-specific requirements as a partnership between Netflix and AWS? Does Netflix ask AWS to put these machines in their data centers as a collaborative effort exclusively for Netflix, or what is the situation here? Are these hardware configurations just generic configurations AWS has in place for all AWS users? Thanks

uuuuhh muuuu uhhhh mmmmyuuhhh NETBSD nyyuuuuh package source ahhh nuuuuuhhhh this is actually exciting aaaaahhh ummmmmm and NETBSD local socket mmmm ummm uhhh imap client TLS

VAX has done great progress during recent time, we're back on track!

Audio is very low. Please amplify and reload

I'm glad you mentioned the reset bug because I was thinking about spinning up bhyve specifically to test if this bug exists there too because I am having trouble with it over on the KVM side.

Sounds like we need a PCIe ZFS accelerator card.

Nice overview

Excellent talk! I always enjoy seeing Michael talk. He is great fun.

It’s sad this project died

*promosm*

I see a bunch of things mentioned in this presentation, but I'm not seeing any connecting thread or point.

audio is *really* low

I like his accent ^^

era bending release, BSD 13.1. And you know it. either way: I trust compiler manuals over TWG. The *bsd*family is a huge network-blob, guarded by ISO/IEC 27040 - Security while writing... and then 15:00, a Venn diagram with pci device drivers😂😂 without_iscsi (rfc 3720) build option. Theo "webgui"* de Raadt is unstoppable.

Awesome video! Great and very informative!

What desktop to use?

Thanks for the excellent audio.

It's really cool to see this talk and then look at OpenBSD 7.4 and see so much more stuff implemented. Well done Claudio and OpenBSD!

00:00 Lightning Talks -- Opening! 00:45 OpenFest announce + CfP -- Shteryana Shopova 03:58 Towards running a Wayland Compositor on OpenBSD -- Matthieu Herrb 13:45 Subpackages in FreeBSD -- Luca Pizzamiglio 21:12 Let's See How Many Mini Routers We Can Run OpenBSD On! -- Mohammad Moureldin

Thank so much for all the people who gave me a BSD !

This is really cool, I'll be setting up a VM to try all of this. I always wanted a talk like this one. Thanks.

Thanks for sharing! I greatly enjoyed the talks.

Great job! Both on the talk and especially the software.

Hey Albert Servus!

re: ELKE, the FreeBSD (compressed) base boot image can be tweaked down to 37MB, should one really need/want to. PoC image showed in the slides is around 350MB.

Nice, that way I can update data on crappy MicroSD on a file base without wearing it out (or needlessly waiting) by doing tons of random writes or even rewrites. Just do the changes in memory and when done do a sparse linear write to the media.