Hello,
As this list can attest, I previously spent a bit of time diving into the way
dynamic linking is supported by L4Re to get shared mode programs working. This
turned out to have a relatively simple fix related to symbols employed by GCC-
generated code.
But during this exercise, I gained some familiarity with the way libraries are
loaded, and this appears to involve the virtual filesystem support, with the
loader perusing the filesystem to access libraries, and with these being
…
[View More]provided as modules by the "rom" filesystem.
Since then, I've spent some time looking at how files are provided by
filesystems and accessed by code that uses the conventional C or POSIX library
interfaces. It raises a few questions about why things are done in a
particular way in L4Re, and which approaches are in use for other L4-based
systems, especially those that seek to provide general-purpose, multi-user
solutions.
What I think I now understand about the virtual filesystem support in L4Re is
as follows. The virtual filesystem itself is a "client-side" construct,
meaning that it resides within any given program. That programs have their own
view of a filesystem is not too different from what the documentation about
systems like the Hurd describes and advocates, and I suppose it is a tempting
approach because it gives each program the flexibility to be customised in
this regard.
However, it seems that beyond the internal "mount tree" representation,
configuration of the namespace hierarchy is largely done using the L4Re
namespace concept, with namespaces acting as directories, and non-namespace
objects within the hierarchy interpreted as particular file types. Apart from
the interpretation of namespaces as directories, it seems that for the most
part, dataspaces are employed to be interpreted as file objects.
I will admit that I didn't really look very hard at how different systems
provide file access before now, but what surprised me slightly was the
apparent lack of delegation in L4Re. As far as I can tell, on systems based on
kernels like Linux, the open library function will employ a system call to
delegate the matter of finding the file and obtaining a way of accessing it to
the familiar monolithic-kernel-plus-filesystems arrangement.
On more "exotic" systems (than Linux) like Minix 3 or the Hurd, it appears
that delegation to a virtual filesystem server [1] or servers [2] occurs to
mediate access to specific files. Some systems like Inferno and Plan 9 employ
protocols [3] to formalise the client-server relationship. I had almost
expected to find similar things in L4Re, but I could only confirm their
absence after reviewing the various VFS abstractions.
One thing I wonder about is whether the current L4Re approach is able to
satisfactorily deal with filesystem content that needs to serve different user
entities, with content having different permission and ownership rights. It
seems that the filesystem logic has to be available as a library within a
program, which is not necessarily a problem.
But to avoid filesystem content being completely exposed to the discretion of
user programs (reminiscent of the problems with early Network File System
implementations), the library would need to call out to other entities, which
doesn't appear to be done with the current L4Re abstractions. One could
implement support for, say, the ext3 filesystem in a library, operating on a
dataspace provided at some kind of mountpoint in a directory (with the
directory being provided by a namespace, of course) but it would be like
giving a user program access to a block device in a traditional Unix-like
system.
Are there any articles about the design of L4Re that might explain the
motivations here? And are there any accessible-but-detailed articles about
other microkernel-based systems and the way in which they structure their
filesystem architectures? I looked around on the TU-Dresden site for
materials, but I didn't immediately find anything obviously relevant.
Paul
[1] https://wiki.minix3.org/doku.php?id=developersguide:vfsinternals
[2] https://www.gnu.org/software/hurd/hurd-talk.html#pat
[3] http://doc.cat-v.org/inferno/4th_edition/styx
[View Less]
[Resent due to wrong Reply-To: header]
FOSDEM 2020 - Microkernels and Component-based OS devroom
CALL FOR PARTICIPATION
The developers of several free and open-source microkernel-based
operating systems will meet at FOSDEM 2020 [1] in Brussels, Belgium
and will share a developer room. The devroom is currently looking for
content in the form of talks and activities related to the area of
microkernel-, unikernel-, and component-based operating systems.
Possible topics include, but are not …
[View More]limited to:
* introduction of a specific OS or framework
* design of subsystems and the general architecture of an OS
* used languages and tools
* enabling support for hardware (architectures, device drivers)
* enabling support for programming languages
* maintenance and testing
* security and robustness
* trends and challenges
* use cases, experiences, lessons learned and demos
The deadline for your proposal is on December 1, 2019. Please use the
Pentabarf [2] system to submit your proposals. You do not need to
create a new account if you already have one.
Make sure to include the following in your proposal:
* title of your talk (will be printed in the FOSDEM booklet)
* your full name (will be printed in the FOSDEM booklet)
* a short abstract (one or two paragraphs)
* duration of your talk (at least 25 and no longer than 55 min)
The official devroom schedule (along with the accepted talks) will be
announced on December 15 on the devroom's mailing list [3] and the
speakers will be notified via e-mail. The schedule will also be
published on the FOSDEM website.
You are invited to send any other suggestions for what you want to see
or do at the devroom to the list. We will also use this list to
organize the traditional devroom dinner that will happen on the first
day of FOSDEM.
About the devroom
Since the first Microkernel devroom at FOSDEM 2012, this devroom has
been part of each following FOSDEM. The focus gradually widened to
include component-based operating systems. By now it has become a
somewhat institutionalized tradition for the community to meet there;
to this date over a dozen projects have participated in one way or
another. Each of the projects face similar challenges but come up with
partially different solutions. Therefore, the goal of the devroom is
to bring the various projects together, let them exchange ideas,
cross-pollinate and socialize.
Social events
It also has become a habit that the microkernel projects dine together
somewhere in Brussels. The year 2020 will not be any different, so
there is going to be a dinner on Saturday night. We try place a
reservation, so we will inform you about the exact location and time
later. Consult the FOSDEM web and other projects for additional
social events such as the famous FOSDEM-organized Friday Beer Event
and the FOSDEM-arranged free sightseeing tours for spouses.
About FOSDEM
FOSDEM is a two-day event organised by volunteers to promote the
widespread use of free and open source software. Taking place in the
beautiful city of Brussels (Belgium), FOSDEM is widely recognised as
the best such conference in Europe. FOSDEM covers a wide spectrum of
free and open source software projects, and offers a platform for
people to collaborate. To this end, FOSDEM has set up developer rooms
(devrooms) with network/internet connectivity and projectors where
teams can meet and showcase their projects. Devrooms are a place for
teams to discuss, hack and publicly present latest directions,
lightning talks, news and discussions. Besides developer rooms, FOSDEM
also offers main tracks, lightning talks, certification exams and
project stands. Every year, FOSDEM hosts more than 5000 developers at
the ULB Solbosch campus. Participation and attendance is totally
free, though the organisers gratefully accept donations and
sponsorship. No registration necessary.
Important dates recap
* 2019-12-01: Deadline for submissions
* 2019-12-15: Schedule published and speakers notified of acceptance
* 2020-02-01: Devroom Dinner (details to be announced)
* 2020-02-01/2020-02-02: The devroom takes places (check the schedule)
Links
[1] https://fosdem.org/
[2] https://penta.fosdem.org/submission/FOSDEM20
[3] https://lists.fosdem.org/listinfo/microkernel-devroom
[View Less]
FOSDEM 2020 - Microkernels and Component-based OS devroom
CALL FOR PARTICIPATION
The developers of several free and open-source microkernel-based
operating systems will meet at FOSDEM 2020 [1] in Brussels, Belgium
and will share a developer room. The devroom is currently looking for
content in the form of talks and activities related to the area of
microkernel-, unikernel-, and component-based operating systems.
Possible topics include, but are not limited to:
* introduction of a specific …
[View More]OS or framework
* design of subsystems and the general architecture of an OS
* used languages and tools
* enabling support for hardware (architectures, device drivers)
* enabling support for programming languages
* maintenance and testing
* security and robustness
* trends and challenges
* use cases, experiences, lessons learned and demos
The deadline for your proposal is on December 1, 2019. Please use the
Pentabarf [2] system to submit your proposals. You do not need to
create a new account if you already have one.
Make sure to include the following in your proposal:
* title of your talk (will be printed in the FOSDEM booklet)
* your full name (will be printed in the FOSDEM booklet)
* a short abstract (one or two paragraphs)
* duration of your talk (at least 25 and no longer than 55 min)
The official devroom schedule (along with the accepted talks) will be
announced on December 15 on the devroom's mailing list [3] and the
speakers will be notified via e-mail. The schedule will also be
published on the FOSDEM website.
You are invited to send any other suggestions for what you want to see
or do at the devroom to the list. We will also use this list to
organize the traditional devroom dinner that will happen on the first
day of FOSDEM.
About the devroom
Since the first Microkernel devroom at FOSDEM 2012, this devroom has
been part of each following FOSDEM. The focus gradually widened to
include component-based operating systems. By now it has become a
somewhat institutionalized tradition for the community to meet there;
to this date over a dozen projects have participated in one way or
another. Each of the projects face similar challenges but come up with
partially different solutions. Therefore, the goal of the devroom is
to bring the various projects together, let them exchange ideas,
cross-pollinate and socialize.
Social events
It also has become a habit that the microkernel projects dine together
somewhere in Brussels. The year 2020 will not be any different, so
there is going to be a dinner on Saturday night. We try place a
reservation, so we will inform you about the exact location and time
later. Consult the FOSDEM web and other projects for additional
social events such as the famous FOSDEM-organized Friday Beer Event
and the FOSDEM-arranged free sightseeing tours for spouses.
About FOSDEM
FOSDEM is a two-day event organised by volunteers to promote the
widespread use of free and open source software. Taking place in the
beautiful city of Brussels (Belgium), FOSDEM is widely recognised as
the best such conference in Europe. FOSDEM covers a wide spectrum of
free and open source software projects, and offers a platform for
people to collaborate. To this end, FOSDEM has set up developer rooms
(devrooms) with network/internet connectivity and projectors where
teams can meet and showcase their projects. Devrooms are a place for
teams to discuss, hack and publicly present latest directions,
lightning talks, news and discussions. Besides developer rooms, FOSDEM
also offers main tracks, lightning talks, certification exams and
project stands. Every year, FOSDEM hosts more than 5000 developers at
the ULB Solbosch campus. Participation and attendance is totally
free, though the organisers gratefully accept donations and
sponsorship. No registration necessary.
Important dates recap
* 2019-12-01: Deadline for submissions
* 2019-12-15: Schedule published and speakers notified of acceptance
* 2020-02-01: Devroom Dinner (details to be announced)
* 2020-02-01/2020-02-02: The devroom takes places (check the schedule)
Links
[1] https://fosdem.org/
[2] https://penta.fosdem.org/submission/FOSDEM20
[3] https://lists.fosdem.org/listinfo/microkernel-devroom
[View Less]