MINIX 3: local bindery service

Autores
Pessolani, Pablo Andrés
Año de publicación
2011
Idioma
inglés
Tipo de recurso
documento de conferencia
Estado
versión publicada
Descripción
MINIX 3 is an open-source operating system designed to be highly reliable, flexible, and secure. The kernel is small and user processes, specialized servers and device drivers runs as user-mode isolated processes. MINIX uses message transfers paradigm to communicate user processes, servers, and device drivers. System Calls use Interprocess Communication (IPC) primitives to send messages requesting services from the Process Manager Server (PM) or the File System Server (FS), and to wait for reply messages. The request messages refer to destination processes with fixed endpoint numbers for each server. MINIX 3 kernel could use a Local Bindery Service to get the endpoint number of a desired service, therefore System Calls could be provided by processes other than FS or MM, without changes in the user’s program source code. This article describes that problem, presents a solution approach, and sketches kernel source code changes as a proof of concept.
Sociedad Argentina de Informática e Investigación Operativa
Materia
Ciencias Informáticas
Operating System
microkernel
IPC
message transfer
Nivel de accesibilidad
acceso abierto
Condiciones de uso
http://creativecommons.org/licenses/by-nc-sa/4.0/
Repositorio
SEDICI (UNLP)
Institución
Universidad Nacional de La Plata
OAI Identificador
oai:sedici.unlp.edu.ar:10915/125334
Acceder
id SEDICI_ccc1664caaade260504a012e6e839466
oai_identifier_str oai:sedici.unlp.edu.ar:10915/125334
network_acronym_str SEDICI
repository_id_str 1329
network_name_str SEDICI (UNLP)
spelling MINIX 3: local bindery servicePessolani, Pablo AndrésCiencias InformáticasOperating SystemmicrokernelIPCmessage transferMINIX 3 is an open-source operating system designed to be highly reliable, flexible, and secure. The kernel is small and user processes, specialized servers and device drivers runs as user-mode isolated processes. MINIX uses message transfers paradigm to communicate user processes, servers, and device drivers. System Calls use Interprocess Communication (IPC) primitives to send messages requesting services from the Process Manager Server (PM) or the File System Server (FS), and to wait for reply messages. The request messages refer to destination processes with fixed endpoint numbers for each server. MINIX 3 kernel could use a Local Bindery Service to get the endpoint number of a desired service, therefore System Calls could be provided by processes other than FS or MM, without changes in the user’s program source code. This article describes that problem, presents a solution approach, and sketches kernel source code changes as a proof of concept.Sociedad Argentina de Informática e Investigación Operativa2011-08info:eu-repo/semantics/conferenceObjectinfo:eu-repo/semantics/publishedVersionObjeto de conferenciahttp://purl.org/coar/resource_type/c_5794info:ar-repo/semantics/documentoDeConferenciaapplication/pdf1-10http://sedici.unlp.edu.ar/handle/10915/125334enginfo:eu-repo/semantics/altIdentifier/issn/1850-2806info:eu-repo/semantics/openAccesshttp://creativecommons.org/licenses/by-nc-sa/4.0/Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0)reponame:SEDICI (UNLP)instname:Universidad Nacional de La Platainstacron:UNLP2025-09-17T10:12:53Zoai:sedici.unlp.edu.ar:10915/125334Institucionalhttp://sedici.unlp.edu.ar/Universidad públicaNo correspondehttp://sedici.unlp.edu.ar/oai/snrdalira@sedici.unlp.edu.arArgentinaNo correspondeNo correspondeNo correspondeopendoar:13292025-09-17 10:12:53.97SEDICI (UNLP) - Universidad Nacional de La Platafalse
dc.title.none.fl_str_mv MINIX 3: local bindery service
title MINIX 3: local bindery service
spellingShingle MINIX 3: local bindery service
Pessolani, Pablo Andrés
Ciencias Informáticas
Operating System
microkernel
IPC
message transfer
title_short MINIX 3: local bindery service
title_full MINIX 3: local bindery service
title_fullStr MINIX 3: local bindery service
title_full_unstemmed MINIX 3: local bindery service
title_sort MINIX 3: local bindery service
dc.creator.none.fl_str_mv Pessolani, Pablo Andrés
author Pessolani, Pablo Andrés
author_facet Pessolani, Pablo Andrés
author_role author
dc.subject.none.fl_str_mv Ciencias Informáticas
Operating System
microkernel
IPC
message transfer
topic Ciencias Informáticas
Operating System
microkernel
IPC
message transfer
dc.description.none.fl_txt_mv MINIX 3 is an open-source operating system designed to be highly reliable, flexible, and secure. The kernel is small and user processes, specialized servers and device drivers runs as user-mode isolated processes. MINIX uses message transfers paradigm to communicate user processes, servers, and device drivers. System Calls use Interprocess Communication (IPC) primitives to send messages requesting services from the Process Manager Server (PM) or the File System Server (FS), and to wait for reply messages. The request messages refer to destination processes with fixed endpoint numbers for each server. MINIX 3 kernel could use a Local Bindery Service to get the endpoint number of a desired service, therefore System Calls could be provided by processes other than FS or MM, without changes in the user’s program source code. This article describes that problem, presents a solution approach, and sketches kernel source code changes as a proof of concept.
Sociedad Argentina de Informática e Investigación Operativa
description MINIX 3 is an open-source operating system designed to be highly reliable, flexible, and secure. The kernel is small and user processes, specialized servers and device drivers runs as user-mode isolated processes. MINIX uses message transfers paradigm to communicate user processes, servers, and device drivers. System Calls use Interprocess Communication (IPC) primitives to send messages requesting services from the Process Manager Server (PM) or the File System Server (FS), and to wait for reply messages. The request messages refer to destination processes with fixed endpoint numbers for each server. MINIX 3 kernel could use a Local Bindery Service to get the endpoint number of a desired service, therefore System Calls could be provided by processes other than FS or MM, without changes in the user’s program source code. This article describes that problem, presents a solution approach, and sketches kernel source code changes as a proof of concept.
publishDate 2011
dc.date.none.fl_str_mv 2011-08
dc.type.none.fl_str_mv info:eu-repo/semantics/conferenceObject
info:eu-repo/semantics/publishedVersion
Objeto de conferencia
http://purl.org/coar/resource_type/c_5794
info:ar-repo/semantics/documentoDeConferencia
format conferenceObject
status_str publishedVersion
dc.identifier.none.fl_str_mv http://sedici.unlp.edu.ar/handle/10915/125334
url http://sedici.unlp.edu.ar/handle/10915/125334
dc.language.none.fl_str_mv eng
language eng
dc.relation.none.fl_str_mv info:eu-repo/semantics/altIdentifier/issn/1850-2806
dc.rights.none.fl_str_mv info:eu-repo/semantics/openAccess
http://creativecommons.org/licenses/by-nc-sa/4.0/
Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0)
eu_rights_str_mv openAccess
rights_invalid_str_mv http://creativecommons.org/licenses/by-nc-sa/4.0/
Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0)
dc.format.none.fl_str_mv application/pdf
1-10
dc.source.none.fl_str_mv reponame:SEDICI (UNLP)
instname:Universidad Nacional de La Plata
instacron:UNLP
reponame_str SEDICI (UNLP)
collection SEDICI (UNLP)
instname_str Universidad Nacional de La Plata
instacron_str UNLP
institution UNLP
repository.name.fl_str_mv SEDICI (UNLP) - Universidad Nacional de La Plata
repository.mail.fl_str_mv alira@sedici.unlp.edu.ar
_version_ 1843532748437848064
score 13.001348

Publicaciones similares