Forwarded from Phoronix News
Phoronix
FreeBSD 13.1-RC1 Pulls In OpenZFS 2.1, WiFi Updates
FreeBSD 13.1 continues working its way towards release later in April...
FreeBSD 13.1-RC1 Pulls In OpenZFS 2.1, WiFi Updates
FreeBSD 13.1 continues working its way towards release later in April...
Phoronix
FreeBSD 13.1-RC1 Pulls In OpenZFS 2.1, WiFi Updates
FreeBSD 13.1 continues working its way towards release later in April.
BSD Tips
soft-updates journaling.pdf
This paper describes the work to add ‘‘journaling lite’’ to soft updates and its incorporation intothe FreeBSD fast filesystem. Because soft updates prevent most inconsistencies, the journal needonly track those inconsistencies that soft updates fails to address. Specifically, the journal con-
tains the information needed to recover the block and inode resources that have been freed butwhose freed status failed to make it to disk before a system failure. After a crash, a variant of thevenerable fsck program runs through the journal to identify and free the lost resources. Only ifan inconsistency between the log and filesystem is detected is it necessary to run fsck. The journal is tiny, 16Mb is usually enough independent of filesystem size. Although journal processing needs to be done before restarting, the processing time is typically just a few seconds and in theworst case a minute. It is not necessary to build a new filesystem to use soft-updates journaling.
The addition or deletion of soft-updates journaling to existing fast filesystems is done using thetunefs program.
tains the information needed to recover the block and inode resources that have been freed butwhose freed status failed to make it to disk before a system failure. After a crash, a variant of thevenerable fsck program runs through the journal to identify and free the lost resources. Only ifan inconsistency between the log and filesystem is detected is it necessary to run fsck. The journal is tiny, 16Mb is usually enough independent of filesystem size. Although journal processing needs to be done before restarting, the processing time is typically just a few seconds and in theworst case a minute. It is not necessary to build a new filesystem to use soft-updates journaling.
The addition or deletion of soft-updates journaling to existing fast filesystems is done using thetunefs program.
BSD Tips
GBDE - GEOM Based Disk Encryption.pdf
GBDE - GEOM Based Disk Encryption
The ever increasing mobility of computers has made protection of data on digital storage media an important requirement in a number of applications and situations. GBDE is a strong cryptographic facility for denying unauthorised access to data stored on a ‘‘cold’’ disk for decades and longer. GBDE operates on the disk(-partition) level allowing any type of file system or database to be protected. A significant focus has been put on the practical aspects in order to make it possible to deploy GBDE in the real world.
The ever increasing mobility of computers has made protection of data on digital storage media an important requirement in a number of applications and situations. GBDE is a strong cryptographic facility for denying unauthorised access to data stored on a ‘‘cold’’ disk for decades and longer. GBDE operates on the disk(-partition) level allowing any type of file system or database to be protected. A significant focus has been put on the practical aspects in order to make it possible to deploy GBDE in the real world.
Journaling versus Soft Updates: Asynchronous Meta-data Protection in File Systems
The UNIX Fast File System (FFS) is probably the most widely-used file system for performance comparisons. However, such comparisons frequently overlook many of the performance enhancements that have been added over the past decade. In this paper, we explore the two most commonly used approaches for improving the performance of meta-data operations and recovery: journaling and Soft Updates. Journaling systems use an auxiliary log to record meta-data operations and Soft Updates uses ordered writes to ensure meta-data consistency.
The commercial sector has moved en masse to journaling file systems, as evidenced by their presence on nearly every server platform available today: Solaris, AIX, Digital UNIX, HP-UX, Irix, and Windows NT. On all but Solaris, the default file system uses journaling. In the meantime, Soft Updates holds the promise of providing stronger reliability guarantees than journaling, with faster recovery and superior performance in certain boundary cases.
In this paper, we explore the benefits of Soft Updates and journaling, comparing their behavior on both micro-benchmarks and workload-based macrobenchmarks. We find that journaling alone is not sufficient to "solve" the meta-data update problem. If synchronous semantics are required (i.e., meta-data operations are durable once the system call returns), then the journaling systems cannot realize their full potential. Only when this synchronicity requirement is relaxed can journaling systems approach the performance of systems like Soft Updates (which also relaxes this requirement). Our asynchronous journaling and Soft Updates systems perform comparably in most cases. While Soft Updates excels in some meta-data intensive microbenchmarks, the macrobenchmark results are more ambiguous. In three cases Soft Updates and journaling are comparable. In a file intensive news workload, journaling prevails, and in a small ISP workload, Soft Updates prevails.
Paper: https://www.seltzer.com/assets/publications/Journaling-versus-Soft-Updates-Asynchronous-Metadata-Protection-in-File-Systems.html
The UNIX Fast File System (FFS) is probably the most widely-used file system for performance comparisons. However, such comparisons frequently overlook many of the performance enhancements that have been added over the past decade. In this paper, we explore the two most commonly used approaches for improving the performance of meta-data operations and recovery: journaling and Soft Updates. Journaling systems use an auxiliary log to record meta-data operations and Soft Updates uses ordered writes to ensure meta-data consistency.
The commercial sector has moved en masse to journaling file systems, as evidenced by their presence on nearly every server platform available today: Solaris, AIX, Digital UNIX, HP-UX, Irix, and Windows NT. On all but Solaris, the default file system uses journaling. In the meantime, Soft Updates holds the promise of providing stronger reliability guarantees than journaling, with faster recovery and superior performance in certain boundary cases.
In this paper, we explore the benefits of Soft Updates and journaling, comparing their behavior on both micro-benchmarks and workload-based macrobenchmarks. We find that journaling alone is not sufficient to "solve" the meta-data update problem. If synchronous semantics are required (i.e., meta-data operations are durable once the system call returns), then the journaling systems cannot realize their full potential. Only when this synchronicity requirement is relaxed can journaling systems approach the performance of systems like Soft Updates (which also relaxes this requirement). Our asynchronous journaling and Soft Updates systems perform comparably in most cases. While Soft Updates excels in some meta-data intensive microbenchmarks, the macrobenchmark results are more ambiguous. In three cases Soft Updates and journaling are comparable. In a file intensive news workload, journaling prevails, and in a small ISP workload, Soft Updates prevails.
Paper: https://www.seltzer.com/assets/publications/Journaling-versus-Soft-Updates-Asynchronous-Metadata-Protection-in-File-Systems.html
What every IT person needs to know about OpenBSD
*.- [PART-1]: How it all started
*.- [PART-2]: Why use OpenBSD?
*.- [PART-3]: That packet filter
- - - - - - - - - - - - - - - - -
*.- OpenBSD has been around for more than 25 years (started October 1995).
*.- OpenBSD is proactively secure with only two remote holes in default install in all those years.
*.- OpenBSD pioneered using strong cryptography, the first free system to ship with IPSec (entangling itself in US export regulations in the process).
*.- OpenBSD pioneered and is still leading in code audit, fixing similar bugs tree-wide when found.
*.- OpenBSD has all security enhancements enabled by default, which are hard, going on impossible, to disable.
*.- OpenBSD is open-source, free software and the project actively encourages independent verification of code quality and security.
*.- Today, OpenBSD is used in many network-centric roles, even though it is a general-purpose operating system albeit with a particular emphasis on security.
*.- OpenBSD has a high profile quality image based on actual code quality and proven performance in real-world use.
*.- OpenBSD is the upstream (origin) for several widely used pieces of software such as OpenSSH, OpenBGPD, PF, OpenSMTPd, LibreSSL, iked, mandoc and several others. For a complete list, please see the OpenBSD Innovations page on the OpenBSD website.
*.- OpenBSD has been ‘growing up in the public’ with code generally accessible via anonymous CVS (the first of its kind) since 1995 (transparent process, development discussions on public tech@ mailing list).
*.- Developers would do well to study high quality (mainly) C-source and how the project runs a six-month release cycle like clockwork (with only a few notable exceptions).
*.- [PART-1]: How it all started
*.- [PART-2]: Why use OpenBSD?
*.- [PART-3]: That packet filter
- - - - - - - - - - - - - - - - -
*.- OpenBSD has been around for more than 25 years (started October 1995).
*.- OpenBSD is proactively secure with only two remote holes in default install in all those years.
*.- OpenBSD pioneered using strong cryptography, the first free system to ship with IPSec (entangling itself in US export regulations in the process).
*.- OpenBSD pioneered and is still leading in code audit, fixing similar bugs tree-wide when found.
*.- OpenBSD has all security enhancements enabled by default, which are hard, going on impossible, to disable.
*.- OpenBSD is open-source, free software and the project actively encourages independent verification of code quality and security.
*.- Today, OpenBSD is used in many network-centric roles, even though it is a general-purpose operating system albeit with a particular emphasis on security.
*.- OpenBSD has a high profile quality image based on actual code quality and proven performance in real-world use.
*.- OpenBSD is the upstream (origin) for several widely used pieces of software such as OpenSSH, OpenBGPD, PF, OpenSMTPd, LibreSSL, iked, mandoc and several others. For a complete list, please see the OpenBSD Innovations page on the OpenBSD website.
*.- OpenBSD has been ‘growing up in the public’ with code generally accessible via anonymous CVS (the first of its kind) since 1995 (transparent process, development discussions on public tech@ mailing list).
*.- Developers would do well to study high quality (mainly) C-source and how the project runs a six-month release cycle like clockwork (with only a few notable exceptions).
APNIC Blog
What every IT person needs to know about OpenBSD Part 1: How it all started | APNIC Blog
OpenBSD remains a crucial yet largely unacknowledged player in the open-source field.
Forwarded from OpenBSD
FreeBSD vs OpenBSD: Which is Right for You?
FreeBSD vs OpenBSD. Which is more secure? Which is faster? Which is generally superior? Both have their strengths and weaknesses, and both appeal to different audiences depending on needs.
https://www.ateamsystems.com/tech-blog/freebsd-vs-openbsd-which-is-right-for-you/
#system
FreeBSD vs OpenBSD. Which is more secure? Which is faster? Which is generally superior? Both have their strengths and weaknesses, and both appeal to different audiences depending on needs.
https://www.ateamsystems.com/tech-blog/freebsd-vs-openbsd-which-is-right-for-you/
#system
Description:
why-openbsd.rocks presents facts about OpenBSD.
Reference:
*.- https://why-openbsd.rocks
Acknowlegments:
*.- @zzzzCsbalx
why-openbsd.rocks presents facts about OpenBSD.
Reference:
*.- https://why-openbsd.rocks
Acknowlegments:
*.- @zzzzCsbalx
why-openbsd.rocks
Why OpenBSD rocks
FreeBSD 13.1-RELEASE Announcement
Some of the highlights:
• OpenSSH has been updated to version v8.8p1.
• OpenSSL has been updated to version 1.1.1o.
• The use of FIDO/U2F hardware authenticators has been enabled in ssh, using the new public key types ecdsa-sk and ed25519-sk, along with corresponding certificate types.
• The ice(4) driver has been updated to 1.34.2-k, adding firmware logging and initial DCB support.
• The iwlwifi(4) driver along with a LinuxKPI 802.11 compatibility layer was added to supplement iwm(4) for newer Intel Wireless chipsets.
• ZFS has been upgraded to OpenZFS release 2.1.4.
• EC2 images are now built by default to boot using UEFI instead of legacy BIOS.
• And much more…
Reference: https://www.freebsd.org/releases/13.1R/announce
Some of the highlights:
• OpenSSH has been updated to version v8.8p1.
• OpenSSL has been updated to version 1.1.1o.
• The use of FIDO/U2F hardware authenticators has been enabled in ssh, using the new public key types ecdsa-sk and ed25519-sk, along with corresponding certificate types.
• The ice(4) driver has been updated to 1.34.2-k, adding firmware logging and initial DCB support.
• The iwlwifi(4) driver along with a LinuxKPI 802.11 compatibility layer was added to supplement iwm(4) for newer Intel Wireless chipsets.
• ZFS has been upgraded to OpenZFS release 2.1.4.
• EC2 images are now built by default to boot using UEFI instead of legacy BIOS.
• And much more…
Reference: https://www.freebsd.org/releases/13.1R/announce
The FreeBSD Project
FreeBSD 13.1-RELEASE Announcement
FreeBSD is an operating system used to power modern servers, desktops, and embedded platforms.
mfsbsd: una derivado de FreeBSD que se ejecuta desde la memoria
mfsBSD es un conjunto de scripts que generan una imagen booteable, un archivo ISO o simplemente archivos de booteo, con la finalidad de crear una instalación mínima y personalizada de FreeBSD la cual es ejecutada completamente en memoria.
mfsBSD es una excelente alternativa a la imagen de FreeBSD completa, no solo por el poco espacio en almacenamiento, no solo porque se ejecuta en la memoria, sino por su alta personalización. mfsBSD nos permite personalizar una imagen sin necesidad de compilarla, aunque también permite hacerlo por si alguien lo desea. Mayormente cuando vemos proyectos de código abierto/software libre derivados tenemos dos problemas frecuentes: o no está actualizado con la rama principal del proyecto, o su principal fuente de atracción se reduce a una perdida de funcionalidad y herramientas imperdonables.
mfsBSD no es así. Si deseas crear una imagen con ciertos paquetes pre-compilados, mfsBSD puede hacerlo por ti. Si deseas hacer un despliegue de múltiples servidores, pero eres tan perezoso que no deseas ejecutar bsdinstall(8), mfsBSD puede hacerlo por ti. Si deseas tener los archivos base como kernel.txz o base.txz en un servidor web o FTP dentro de tu misma red local para ahorrar ancho de banda descargándolo desde la página web oficial, mfsBSD puede hacerlo por ti. Si deseas tener un sistema que solo correrá en memoria con herramientas de diagnostico y reparación, mfsBSD puede hacerlo por ti.
El límite es la imaginación de la persona, y como son sólo un conjunto de scripts escritos en sh o archivos Makefile, su estudio, personalización, y si deseas, contribución, es realmente sencilla.
*.- https://underc0de.org/foro/gnulinux/non-linux-mfsbsd-una-derivado-de-freebsd-que-se-ejecuta-desde-la-memoria
~ DtxdF
mfsBSD es un conjunto de scripts que generan una imagen booteable, un archivo ISO o simplemente archivos de booteo, con la finalidad de crear una instalación mínima y personalizada de FreeBSD la cual es ejecutada completamente en memoria.
mfsBSD es una excelente alternativa a la imagen de FreeBSD completa, no solo por el poco espacio en almacenamiento, no solo porque se ejecuta en la memoria, sino por su alta personalización. mfsBSD nos permite personalizar una imagen sin necesidad de compilarla, aunque también permite hacerlo por si alguien lo desea. Mayormente cuando vemos proyectos de código abierto/software libre derivados tenemos dos problemas frecuentes: o no está actualizado con la rama principal del proyecto, o su principal fuente de atracción se reduce a una perdida de funcionalidad y herramientas imperdonables.
mfsBSD no es así. Si deseas crear una imagen con ciertos paquetes pre-compilados, mfsBSD puede hacerlo por ti. Si deseas hacer un despliegue de múltiples servidores, pero eres tan perezoso que no deseas ejecutar bsdinstall(8), mfsBSD puede hacerlo por ti. Si deseas tener los archivos base como kernel.txz o base.txz en un servidor web o FTP dentro de tu misma red local para ahorrar ancho de banda descargándolo desde la página web oficial, mfsBSD puede hacerlo por ti. Si deseas tener un sistema que solo correrá en memoria con herramientas de diagnostico y reparación, mfsBSD puede hacerlo por ti.
El límite es la imaginación de la persona, y como son sólo un conjunto de scripts escritos en sh o archivos Makefile, su estudio, personalización, y si deseas, contribución, es realmente sencilla.
*.- https://underc0de.org/foro/gnulinux/non-linux-mfsbsd-una-derivado-de-freebsd-que-se-ejecuta-desde-la-memoria
~ DtxdF
Underc0de
[Non-Linux] mfsbsd: una derivado de FreeBSD que se ejecuta desde la memoria
mfsBSD es un conjunto de scripts que generan una imagen booteable, un archivo ISO o simplemente archivos de booteo, con la finalidad de crear una instalación mínima y personalizada de FreeBSD la cual es ejecutada completamente en memoria.mfsBSD es una excelente…
Notas de sistemas operativos
Este proyecto está enfocado en preservar información, que generalmente no está presente en la documentación oficial, o, en algunos casos, no está detallada como para resolver un problema muy específico.
La idea principal es tener un espacio o un lugar donde almacenar nuestras notas sobre problemas a los cuales nos hemos enfrentado con determinado sistema operativo, y que le podría servir a la comunidad de Internet.
Actualmente, dado que el proyecto es reciente, tiene algunas notas, como tutoriales y tips de FreeBSD, pero dentro de un futuro cercano se tiene pensado agregar más información sobre FreeBSD y OpenBSD. También se es libre de documentar sobre otro sistema operativo, sea linux, BSD, o cualquier otro.
*.- Índice del proyecto: https://github.com/DtxdF/OS-NOTES
*.- Índice de las notas: https://github.com/DtxdF/OS-NOTES/blob/main/os-notes/index.md
~ DtxdF
Este proyecto está enfocado en preservar información, que generalmente no está presente en la documentación oficial, o, en algunos casos, no está detallada como para resolver un problema muy específico.
La idea principal es tener un espacio o un lugar donde almacenar nuestras notas sobre problemas a los cuales nos hemos enfrentado con determinado sistema operativo, y que le podría servir a la comunidad de Internet.
Actualmente, dado que el proyecto es reciente, tiene algunas notas, como tutoriales y tips de FreeBSD, pero dentro de un futuro cercano se tiene pensado agregar más información sobre FreeBSD y OpenBSD. También se es libre de documentar sobre otro sistema operativo, sea linux, BSD, o cualquier otro.
*.- Índice del proyecto: https://github.com/DtxdF/OS-NOTES
*.- Índice de las notas: https://github.com/DtxdF/OS-NOTES/blob/main/os-notes/index.md
~ DtxdF
GitHub
GitHub - DtxdF/OS-NOTES: Notas de sistemas operativos
Notas de sistemas operativos. Contribute to DtxdF/OS-NOTES development by creating an account on GitHub.