Add fosdem talks summaries

8 files changed, 42 insertions, 1 deletions

diff --git a/community/meetings/fosdem_2014.mdwn b/community/meetings/fosdem_2014.mdwn
index b68a907d..46f7c4f1 100644
--- a/community/meetings/fosdem_2014.mdwn
+++ b/community/meetings/fosdem_2014.mdwn
@@ -36,6 +36,10 @@ Bruxelles.
 
   * {{$thibault_hurd}}
 
+We will explain how userland drivers are implement in GNU/Hurd thanks to the DDE layer, and what kernel support is needed for that. We will also show the flexibility this brings for the user.
+
+A longer version of this talk (incl video) is also available at [GHM 2013 archive](https://www.gnu.org/ghm/2013/paris/)
+
 [[!ymlfront data="""
 
 thibault_hurd:
diff --git a/community/meetings/fosdem_2015.mdwn b/community/meetings/fosdem_2015.mdwn
index 03c2009d..2c365aca 100644
--- a/community/meetings/fosdem_2015.mdwn
+++ b/community/meetings/fosdem_2015.mdwn
@@ -38,6 +38,17 @@ Bruxelles.
 
   * {{$thibault_hurd}}
 
+
+
+It is not so obvious to newcomers to the Hurd project how to follow execution path from their application to actual behavior in the Hurd translators. This talk will guide them through the involved RPCs, thus providing a starting guide into the GNU Hurd architecture, and hopefully, to contributing fixes or new features!
+
+With monolithic kernels, the path from application source code to actual implementation in the kernel is very simple: only the system call layer needs to be understood. In a multiserver system such as the GNU Hurd, this is not so simple, since one for a start has to understand which server one is actually talking to, and how RPCs work. Once this is cleared up, it becomes way easier to know where to contribute fixes and features!
+
+This talk will thus take a few examples of typical application operations (opening and reading a file, opening and working with a socket) and go through the RPC path, to illustrate how translators are involved and where the eventual implementations actually reside.
+
+It will also be an opportunity to give the latest news about the GNU/Hurd project.
+
+
 [[!ymlfront data="""
 
 thibault_hurd:
diff --git a/community/meetings/fosdem_2016.mdwn b/community/meetings/fosdem_2016.mdwn
index 62348bea..8c78c0b1 100644
--- a/community/meetings/fosdem_2016.mdwn
+++ b/community/meetings/fosdem_2016.mdwn
@@ -36,6 +36,10 @@ Bruxelles.
   * {{$ragkousis_guix_hurd}}
 
 
+This presentation will be a guided tour of porting Guix and its package collection to a new platform, with the specifics of GNU/Hurd. We will discuss the current status of the project. Next we will raise the problems we faced and how we solved them. Finally we wiil present a road map for porting GuixSD, the standalone system distribution on GNU/Hurd.
+
+
+
 # Microkernels devroom
 
 <https://fosdem.org/2016/schedule/track/microkernels/>
@@ -43,6 +47,10 @@ Bruxelles.
   * {{$thibault_hurd}}
 
 
+
+The Hurd recently saw some experimental work to add sound support. This was done thanks to the Rump kernel, embedded in a library. As a first-working implementation the library is directly linked into mplayer, but of course we plan to make this much more flexible by moving the Rump sound driver into a separate translator, very much like we did for network drivers with netdde. This however poses design questions. The other hardware bit missing on the Hurd is USB support, which we should be able to add a similar way. This poses yet more design questions, as to the shape of the hird of translators we should start for this. This will of course also be the opportunity to give the now-traditional yearly latest news about the Hurd.
+
+
 [[!ymlfront data="""
 
 ragkousis_guix_hurd:
diff --git a/community/meetings/fosdem_2017.mdwn b/community/meetings/fosdem_2017.mdwn
index d281e279..c78ac13f 100644
--- a/community/meetings/fosdem_2017.mdwn
+++ b/community/meetings/fosdem_2017.mdwn
@@ -24,6 +24,8 @@ Bruxelles.
   * {{$ragkousis_guix_hurd}}
 
 
+This presentation will be a guided tour of porting Guix and its package collection to a new platform, with the specifics of GNU/Hurd. We will discuss the current status of the project. Next we will raise the problems we faced and how we solved them. Finally we will present the current status and a road map of porting GuixSD, the standalone system distribution on GNU/Hurd.
+
 
 # Microkernels devroom
 
@@ -31,6 +33,9 @@ Bruxelles.
 
   * {{$winter_hurd}}
 
+Virtualization is one aspect of our everyday life where multiserver operating systems can shine. Given the right underlying architecture, one gets robust and fine-grained virtualization with little effort and code. Achieving the same on conventional monolithic systems requires careful and invasive changes to the whole system, and the security merely depends on the implementation at hand.
+
+This talk describes and demos how both fine- and coarse-grained virtualization is implemented on the Hurd, and how virtualization helps users gain freedom #0, i.e. the freedom to shape her computation environment anyway she wants.
 
 [[!ymlfront data="""
 
diff --git a/community/meetings/fosdem_2018.mdwn b/community/meetings/fosdem_2018.mdwn
index eaac07bb..96ac6e51 100644
--- a/community/meetings/fosdem_2018.mdwn
+++ b/community/meetings/fosdem_2018.mdwn
@@ -25,6 +25,9 @@ Bruxelles.
 
   * {{$thibault_hurd}}
 
+One of Hurd's goals is to isolate hardware drivers, to provide flexibility and safety, by isolating drivers' possibly erratic behavior, delegating driving hardware to unprivileged users, etc.
+
+We are thus currently working on a PCI arbiter, which allows to let different userland drivers access PCI devices concurrently, while paving the way for fine-grain per-user, per-session, etc. permission management over PCI access, the use of IOMMUs allowing to do that very safely.
 
 [[!ymlfront data="""
 
diff --git a/community/meetings/fosdem_2019.mdwn b/community/meetings/fosdem_2019.mdwn
index 257bc00c..621908e1 100644
--- a/community/meetings/fosdem_2019.mdwn
+++ b/community/meetings/fosdem_2019.mdwn
@@ -25,6 +25,11 @@ Bruxelles.
 
   * {{$thibault_hurd}}
 
+Most people don't realize it, but the Hurd system is actually well established. About 75% of Debian official packages do build fine, it has mainstream gcc/glibc/llvm support, go and rust ports are ongoing, it can be installed with the Debian installer and GuixSD and Arch ports are ongoing...
+
+Yet not so much has been happening within the Hurd itself in the past couple of years. We have notably added a PCI arbiter, which allows for both flexible and safe PCI access for end users, and some basic ACPI support is ongoing. But many exciting features could be achieved with a bit of work.
+
+This talk will discuss some of these promising features, to give a sort of ideas roadmap for contributions. Some have implementation sketches which just need to be polished to be more production-ready, such as httpfs, mboxfs, or writing translators in more high-level languages than C. Other features are at early stage, such as adding sound support through rump, getting complete rid of disk drivers from the kernel by moving them to userland, or also getting valgrind support. I will also discuss some promising ideas, such as using rump to get support for more filesystems.
 
 [[!ymlfront data="""
 
diff --git a/community/meetings/fosdem_2022.mdwn b/community/meetings/fosdem_2022.mdwn
index 221ef612..29ab333e 100644
--- a/community/meetings/fosdem_2022.mdwn
+++ b/community/meetings/fosdem_2022.mdwn
@@ -24,6 +24,7 @@ FOSDEM has taken place on February 5th/6th online
 
   * {{$zammit_hurd}}
 
+GNU/Hurd is the original Free Software operating system started in the 1980s. Its microkernel design has been evolving over the years and the project has not quite hit mainstream use. I believe this is due to one main reason: the lack of drivers for peripherals and hardware. In this talk, I explain how NetBSD kernel drivers have been reused in a microkernel setting and demonstrate their use to boot up a GNU/Hurd system via a userspace rump disk driver, with a driverless Hurd kernel, gnumach. The ACPI management, PCI management, and actual driver are in separate processes with RPC interfaces between them, which separates out their debugging, licencing concerns and execution. I believe this aligns with the original vision for the operating system, (as a Hurd of servers).
 
 [[!ymlfront data="""
 
diff --git a/community/meetings/fosdem_2026.mdwn b/community/meetings/fosdem_2026.mdwn
index 4690a992..c4157a85 100644
--- a/community/meetings/fosdem_2026.mdwn
+++ b/community/meetings/fosdem_2026.mdwn
@@ -11,7 +11,7 @@ License|/fdl]]."]]"""]]
 
 [[!meta title="FOSDEM 2026"]]
 
-<http://fosdem.org/2022>
+<http://fosdem.org/2026>
 
 FOSDEM has taken place on January 31th / February 1st at the Université Libre de Bruxelles.
 
@@ -24,6 +24,10 @@ FOSDEM has taken place on January 31th / February 1st at the Université Libre d
 
   * {{$thibault_hurd}}
 
+It has been a while since the last FOSDEM update on GNU/Hurd, so we have a lot to talk about :)
+
+Driver support improvement is on its way through using netbsd's rump layer, now being used in production although there are a few things left to fix. Some SMP support has been added, which should allow at least compilation to be run in parallel. Hurd support was added to the rust ecosystem, which became more and more a necessity due to various software now requiring it. The x86_64 port is essentially complete, which mostly required fixing the MIG RPC layer, and telling various software that it exists. To bootstrap the Debian GNU/Hurd x86_64 distribution, many of the crossbuilding, rebootstrapping and build profiles tools were used to make it relatively smooth. Additionally, the Guix/Hurd distribution is also on its way, as well as an Alpine/Hurd distribution. And more to discover during the talk!
+
 
 [[!ymlfront data="""