#openbsd — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #openbsd, aggregated by home.social.
-
A new, unpatched local privilege escalation (LPE) vulnerability impacting the Linux kernel.
Linux Kernel Dirty Frag LPE Exploit Enables Root Access Across Major Distributions.
https://thehackernews.com/2026/05/linux-kernel-dirty-frag-lpe-exploit.html
Well, after reading "Integrated By Design", Vivian Voss's book...
...it's clear why. IMO the book is a must if you are working with #linux
or starting with #bsd #freeBSD #openbsd #ghostbsd -
Announcing #BSDCan 2026 Travel Grants
Deadline: Friday the 19th!
To encourage and enable more first-time and returning attendees at BSDCan 2026, this year’s travel grant is a free room for up to five nights in a shared-bathroom private suite at the 90U residences.
Full details:
https://blog.bsdcan.org/2026/05/14/announcing-bsdcan-2026-travel-grants
-
Init vs SystemD
This subject was highlighted in an interesting manner by the author.
The article is also very informative. You will learn a few to a lot of things about both systems.From my perspective the author seems to have forgotten one important thing.
He stated himself that Init follows the UNIX, not Linux, principle of doing one thing good.
The UNIX principle is way older than Linux itself, which makes me think that the author has not been around long enough, to know how interesting of a monstrosity systemD has become.
Regardless whether you like Init or systemD, you have to know that they have totally different concepts with similar final goals but in different manners.
The philosophies coding styles, modus operandi & configuration, differ so wildly from one to another, that you should not compare them, AT ALL
Never compare systemD with Init!
Realize one thing, if you do not want to see systemD, ever you have to migrate to one of the more advanced Open Source environments.
You shall be safe in freeBSD, openBSD, netBSD, ghostBSD, Open Indiana, Tribblix, Illumos, or any of the others which have been around much longer than Linus Torvalds was even an ID {idea} in the balls of his father.
You can even go for Open DOS, sinds that's single tasking no Init is neededYou should also not forget that you can always, write & program your own Init system or modify the current Init system itself, if you are stuck on a Linux flavor.
Stop bitching about which system is better.
They are totally different.
Live with one of them or write your own
Init is Open Source
systemD is Open SourceUse the power, choose or fork your favourite
Sources:
https://en.wikipedia.org/wiki/Systemd
https://en.wikipedia.org/wiki/Init
https://linuxtldr.com/init-vs-systemd/
#Init #systemD #Linux #POST #freeBSD #openBSD #netBSD #ghostBSD #programming #sh #C #Lang
-
Init vs SystemD
This subject was highlighted in an interesting manner by the author.
The article is also very informative. You will learn a few to a lot of things about both systems.From my perspective the author seems to have forgotten one important thing.
He stated himself that Init follows the UNIX, not Linux, principle of doing one thing good.
The UNIX principle is way older than Linux itself, which makes me think that the author has not been around long enough, to know how interesting of a monstrosity systemD has become.
Regardless whether you like Init or systemD, you have to know that they have totally different concepts with similar final goals but in different manners.
The philosophies coding styles, modus operandi & configuration, differ so wildly from one to another, that you should not compare them, AT ALL
Never compare systemD with Init!
Realize one thing, if you do not want to see systemD, ever you have to migrate to one of the more advanced Open Source environments.
You shall be safe in freeBSD, openBSD, netBSD, ghostBSD, Open Indiana, Tribblix, or any of the others which have been around much longer than Linus Torvalds was even an ID {idea} in the balls of his father.
You can even go for Open DOS, sinds that's single tasking no Init is neededYou should also not forget that you can always, write & program your own Init system or modify the current Init system itself, if you are stuck on a Linux flavor.
Stop bitching about which system is better.
They are totally different.
Live with one of them or write your own
Init is Open Source
systemD is Open SourceUse the power, choose or fork your favourite
Sources:
https://en.wikipedia.org/wiki/Systemd
https://en.wikipedia.org/wiki/Init
https://linuxtldr.com/init-vs-systemd/
#Init #systemD #Linux #POST #freeBSD #openBSD #netBSD #ghostBSD #programming #sh #C #Lang
-
Init vs SystemD
This subject was highlighted in an interesting manner by the author.
The article is also very informative. You will learn a few to a lot of things about both systems.From my perspective the author seems to have forgotten one important thing.
He stated himself that Init follows the UNIX, not Linux, principle of doing one thing good.
The UNIX principle is way older than Linux itself, which makes me think that the author has not been around long enough, to know how interesting of a monstrosity systemD has become.
Regardless whether you like Init or systemD, you have to know that they have totally different concepts with similar final goals but in different manners.
The philosophies coding styles, modus operandi & configuration, differ so wildly from one to another, that you should not compare them, AT ALL
Never compare systemD with Init!
Realize one thing, if you do not want to see systemD, ever you have to migrate to one of the more advanced Open Source environments.
You shall be safe in freeBSD, openBSD, netBSD, ghostBSD, Open Indiana, Tribblix, or any of the others which have been around much longer than Linus Torvalds was even an ID {idea} in the balls of his father.
You can even go for Open DOS, sinds that's single tasking no Init is neededYou should also not forget that you can always, write & program your own Init system or modify the current Init system itself, if you are stuck on a Linux flavor.
Stop bitching about which system is better.
They are totally different.
Live with one of them or write your own
Init is Open Source
systemD is Open SourceUse the power, choose or fork your favourite
Sources:
https://en.wikipedia.org/wiki/Systemd
https://en.wikipedia.org/wiki/Init
https://linuxtldr.com/init-vs-systemd/
#Init #systemD #Linux #POST #freeBSD #openBSD #netBSD #ghostBSD #programming #sh #C #Lang
-
Init vs SystemD
This subject was highlighted in an interesting manner by the author.
The article is also very informative. You will learn a few to a lot of things about both systems.From my perspective the author seems to have forgotten one important thing.
He stated himself that Init follows the UNIX, not Linux, principle of doing one thing good.
The UNIX principle is way older than Linux itself, which makes me think that the author has not been around long enough, to know how interesting of a monstrosity systemD has become.
Regardless whether you like Init or systemD, you have to know that they have totally different concepts with similar final goals but in different manners.
The philosophies coding styles, modus operandi & configuration, differ so wildly from one to another, that you should not compare them, AT ALL
Never compare systemD with Init!
Realize one thing, if you do not want to see systemD, ever you have to migrate to one of the more advanced Open Source environments.
You shall be safe in freeBSD, openBSD, netBSD, ghostBSD, Open Indiana, Tribblix, or any of the others which have been around much longer than Linus Torvalds was even an ID {idea} in the balls of his father.
You can even go for Open DOS, sinds that's single tasking no Init is neededYou should also not forget that you can always, write & program your own Init system or modify the current Init system itself, if you are stuck on a Linux flavor.
Stop bitching about which system is better.
They are totally different.
Live with one of them or write your own
Init is Open Source
systemD is Open SourceUse the power, choose or fork your favourite
Sources:
https://en.wikipedia.org/wiki/Systemd
https://en.wikipedia.org/wiki/Init
https://linuxtldr.com/init-vs-systemd/
#Init #systemD #Linux #POST #freeBSD #openBSD #netBSD #ghostBSD #programming #sh #C #Lang
-
Init vs SystemD
This subject was highlighted in an interesting manner by the author.
The article is also very informative. You will learn a few to a lot of things about both systems.From my perspective the author seems to have forgotten one important thing.
He stated himself that Init follows the UNIX, not Linux, principle of doing one thing good.
The UNIX principle is way older than Linux itself, which makes me think that the author has not been around long enough, to know how interesting of a monstrosity systemD has become.
Regardless whether you like Init or systemD, you have to know that they have totally different concepts with similar final goals but in different manners.
The philosophies coding styles, modus operandi & configuration, differ so wildly from one to another, that you should not compare them, AT ALL
Never compare systemD with Init!
Realize one thing, if you do not want to see systemD, ever you have to migrate to one of the more advanced Open Source environments.
You shall be safe in freeBSD, openBSD, netBSD, ghostBSD, Open Indiana, Tribblix, or any of the others which have been around much longer than Linus Torvalds was even an ID {idea} in the balls of his father.
You can even go for Open DOS, sinds that's single tasking no Init is neededYou should also not forget that you can always, write & program your own Init system or modify the current Init system itself, if you are stuck on a Linux flavor.
Stop bitching about which system is better.
They are totally different.
Live with one of them or write your own
Init is Open Source
systemD is Open SourceUse the power, choose or fork your favourite
Sources:
https://en.wikipedia.org/wiki/Systemd
https://en.wikipedia.org/wiki/Init
https://linuxtldr.com/init-vs-systemd/
#Init #systemD #Linux #POST #freeBSD #openBSD #netBSD #ghostBSD #programming #sh #C #Lang
-
@fionescu @daftaupe @cienmilojos
I wonder if #OpenBSD will ever get a modern fs. They even jettisoned FFS softdeps because IIRC they said that Kirk McCusick was the only one who understood the code (which very well may be true).
I don't think we'll ever see #ZFS on OpenBSD; the resource usage and code complexity is kind of anathema to them, and I totally get it.
I wonder if HAMMER2 would be a good fit, then? I must confess that don't know anything about it.
-
:tux: Während wir gerade alle feiern, wie geil #Linux inzwischen ist und ich gerade ein butterweich laufendes Resident Evil Requiem auf meinem Linux-PC zu Ende gespielt habe, flutet #Apple den #Notebook-Markt mit billigen Macbooks, auf denen Linux nicht läuft, lassen #Samsung, #Xiaomi und Co keine alternativen Systeme auf ihren Smartphones mehr zu, läuft Linux auf #Microsoft #Surface Geräten allenfalls nach übelstem Rumgefrickel und wirft #Google eine #Chromebook-Nachfolge mit #Android auf den Markt, das auch immer mehr zugenagelt wird.
Die Großen haben Angst um ihre Ökosysteme und den drohenden Verlust ihrer Kundenbindung und tun entsprechend alles dafür, dass wir es zukünftig schwerer haben, freie Alternativen zu wählen.
⚠️ Bitte achtet darauf, was für Hardware ihr kauft, und wählt Systeme, die euch keinen Riegel vorschieben.
#Macbook #MacbookNeo #Windows #FOSS #FreeSoftware #OpenBSD #FreeBSD #FreieSoftware #Laptop #PC #Smartphone
-
:tux: Während wir gerade alle feiern, wie geil #Linux inzwischen ist und ich gerade ein butterweich laufendes Resident Evil Requiem auf meinem Linux-PC zu Ende gespielt habe, flutet #Apple den #Notebook-Markt mit billigen Macbooks, auf denen Linux nicht läuft, lassen #Samsung, #Xiaomi und Co keine alternativen Systeme auf ihren Smartphones mehr zu, läuft Linux auf #Microsoft #Surface Geräten allenfalls nach übelstem Rumgefrickel und wirft #Google eine #Chromebook-Nachfolge mit #Android auf den Markt, das auch immer mehr zugenagelt wird.
Die Großen haben Angst um ihre Ökosysteme und den drohenden Verlust ihrer Kundenbindung und tun entsprechend alles dafür, dass wir es zukünftig schwerer haben, freie Alternativen zu wählen.
⚠️ Bitte achtet darauf, was für Hardware ihr kauft, und wählt Systeme, die euch keinen Riegel vorschieben.
#Macbook #MacbookNeo #Windows #FOSS #FreeSoftware #OpenBSD #FreeBSD #FreieSoftware #Laptop #PC #Smartphone
-
:tux: Während wir gerade alle feiern, wie geil #Linux inzwischen ist und ich gerade ein butterweich laufendes Resident Evil Requiem auf meinem Linux-PC zu Ende gespielt habe, flutet #Apple den #Notebook-Markt mit billigen Macbooks, auf denen Linux nicht läuft, lassen #Samsung, #Xiaomi und Co keine alternativen Systeme auf ihren Smartphones mehr zu, läuft Linux auf #Microsoft #Surface Geräten allenfalls nach übelstem Rumgefrickel und wirft #Google eine #Chromebook-Nachfolge mit #Android auf den Markt, das auch immer mehr zugenagelt wird.
Die Großen haben Angst um ihre Ökosysteme und den drohenden Verlust ihrer Kundenbindung und tun entsprechend alles dafür, dass wir es zukünftig schwerer haben, freie Alternativen zu wählen.
⚠️ Bitte achtet darauf, was für Hardware ihr kauft, und wählt Systeme, die euch keinen Riegel vorschieben.
#Macbook #MacbookNeo #Windows #FOSS #FreeSoftware #OpenBSD #FreeBSD #FreieSoftware #Laptop #PC #Smartphone
-
:tux: Während wir gerade alle feiern, wie geil #Linux inzwischen ist und ich gerade ein butterweich laufendes Resident Evil Requiem auf meinem Linux-PC zu Ende gespielt habe, flutet #Apple den #Notebook-Markt mit billigen Macbooks, auf denen Linux nicht läuft, lassen #Samsung, #Xiaomi und Co keine alternativen Systeme auf ihren Smartphones mehr zu, läuft Linux auf #Microsoft #Surface Geräten allenfalls nach übelstem Rumgefrickel und wirft #Google eine #Chromebook-Nachfolge mit #Android auf den Markt, das auch immer mehr zugenagelt wird.
Die Großen haben Angst um ihre Ökosysteme und den drohenden Verlust ihrer Kundenbindung und tun entsprechend alles dafür, dass wir es zukünftig schwerer haben, freie Alternativen zu wählen.
⚠️ Bitte achtet darauf, was für Hardware ihr kauft, und wählt Systeme, die euch keinen Riegel vorschieben.
#Macbook #MacbookNeo #Windows #FOSS #FreeSoftware #OpenBSD #FreeBSD #FreieSoftware #Laptop #PC #Smartphone
-
:tux: Während wir gerade alle feiern, wie geil #Linux inzwischen ist und ich gerade ein butterweich laufendes Resident Evil Requiem auf meinem Linux-PC zu Ende gespielt habe, flutet #Apple den #Notebook-Markt mit billigen Macbooks, auf denen Linux nicht läuft, lassen #Samsung, #Xiaomi und Co keine alternativen Systeme auf ihren Smartphones mehr zu, läuft Linux auf #Microsoft #Surface Geräten allenfalls nach übelstem Rumgefrickel und wirft #Google eine #Chromebook-Nachfolge mit #Android auf den Markt, das auch immer mehr zugenagelt wird.
Die Großen haben Angst um ihre Ökosysteme und den drohenden Verlust ihrer Kundenbindung und tun entsprechend alles dafür, dass wir es zukünftig schwerer haben, freie Alternativen zu wählen.
⚠️ Bitte achtet darauf, was für Hardware ihr kauft, und wählt Systeme, die euch keinen Riegel vorschieben.
#Macbook #MacbookNeo #Windows #FOSS #FreeSoftware #OpenBSD #FreeBSD #FreieSoftware #Laptop #PC #Smartphone
-
Automatic expiry at timeout for pf(4) overload tables https://undeadly.org/cgi?action=article;sid=20260513064948 #openbsd #pf #packetfilter #overload #overloadtables #statetracking #timeout #expiry #autoexpiry #autotimeout #networking #networktrickery
-
Automatic expiry at timeout for pf(4) overload tables https://undeadly.org/cgi?action=article;sid=20260513064948 #openbsd #pf #packetfilter #overload #overloadtables #statetracking #timeout #expiry #autoexpiry #autotimeout #networking #networktrickery
-
Automatic expiry at timeout for pf(4) overload tables https://undeadly.org/cgi?action=article;sid=20260513064948 #openbsd #pf #packetfilter #overload #overloadtables #statetracking #timeout #expiry #autoexpiry #autotimeout #networking #networktrickery
-
Automatic expiry at timeout for pf(4) overload tables https://undeadly.org/cgi?action=article;sid=20260513064948 #openbsd #pf #packetfilter #overload #overloadtables #statetracking #timeout #expiry #autoexpiry #autotimeout #networking #networktrickery
-
Automatic expiry at timeout for pf(4) overload tables https://undeadly.org/cgi?action=article;sid=20260513064948 #openbsd #pf #packetfilter #overload #overloadtables #statetracking #timeout #expiry #autoexpiry #autotimeout #networking #networktrickery
-
New #blog #post: Package Manager Tier List
https://rldane.space/package-manager-tier-list.html
1521 words
Note: this is a very off-the-cuff tier list, using speed as the main qualifier, but the article explains exceptions to that as it goes on.
cc: my wonderful #chorus: @joel @dm @sotolf @thedoctor @pixx @orbitalmartian @adamsdesk @krafter @roguefoam @clayton @giantspacesquid @Twizzay @stfn
(I will happily add/remove you from the chorus upon request! :)
#rlDaneWriting #blost #DeadLikeMe #Linux #BSD #RunBSD #FreeBSD #OpenBSD #NetBSD #Debian #Arch #pacman #AUR #Fedora #homebrew #flatpak #snap #OpenSuSE #RPM
-
New #blog #post: Package Manager Tier List
https://rldane.space/package-manager-tier-list.html
1521 words
Note: this is a very off-the-cuff tier list, using speed as the main qualifier, but the article explains exceptions to that as it goes on.
cc: my wonderful #chorus: @joel @dm @sotolf @thedoctor @pixx @orbitalmartian @adamsdesk @krafter @roguefoam @clayton @giantspacesquid @Twizzay @stfn
(I will happily add/remove you from the chorus upon request! :)
#rlDaneWriting #blost #DeadLikeMe #Linux #BSD #RunBSD #FreeBSD #OpenBSD #NetBSD #Debian #Arch #pacman #AUR #Fedora #homebrew #flatpak #snap #OpenSuSE #RPM
-
New #blog #post: Package Manager Tier List
https://rldane.space/package-manager-tier-list.html
1521 words
Note: this is a very off-the-cuff tier list, using speed as the main qualifier, but the article explains exceptions to that as it goes on.
cc: my wonderful #chorus: @joel @dm @sotolf @thedoctor @pixx @orbitalmartian @adamsdesk @krafter @roguefoam @clayton @giantspacesquid @Twizzay @stfn
(I will happily add/remove you from the chorus upon request! :)
#rlDaneWriting #blost #DeadLikeMe #Linux #BSD #RunBSD #FreeBSD #OpenBSD #NetBSD #Debian #Arch #pacman #AUR #Fedora #homebrew #flatpak #snap #OpenSuSE #RPM
-
New #blog #post: Package Manager Tier List
https://rldane.space/package-manager-tier-list.html
1521 words
Note: this is a very off-the-cuff tier list, using speed as the main qualifier, but the article explains exceptions to that as it goes on.
cc: my wonderful #chorus: @joel @dm @sotolf @thedoctor @pixx @orbitalmartian @adamsdesk @krafter @roguefoam @clayton @giantspacesquid @Twizzay @stfn
(I will happily add/remove you from the chorus upon request! :)
#rlDaneWriting #blost #DeadLikeMe #Linux #BSD #RunBSD #FreeBSD #OpenBSD #NetBSD #Debian #Arch #pacman #AUR #Fedora #homebrew #flatpak #snap #OpenSuSE #RPM
-
New #blog #post: Package Manager Tier List
https://rldane.space/package-manager-tier-list.html
1521 words
Note: this is a very off-the-cuff tier list, using speed as the main qualifier, but the article explains exceptions to that as it goes on.
cc: my wonderful #chorus: @joel @dm @sotolf @thedoctor @pixx @orbitalmartian @adamsdesk @krafter @roguefoam @clayton @giantspacesquid @Twizzay @stfn
(I will happily add/remove you from the chorus upon request! :)
#rlDaneWriting #blost #DeadLikeMe #Linux #BSD #RunBSD #FreeBSD #OpenBSD #NetBSD #Debian #Arch #pacman #AUR #Fedora #homebrew #flatpak #snap #OpenSuSE #RPM
-
Let's find out how to get predictable IPv6 addresses assigned to OpenBSD VMs https://undeadly.org/cgi?action=article;sid=20260512115225 #openbsd #networking #ipv6 #predictable #dynamic #autoconf #development #freesoftware #libresoftware
-
Beneath the Linux surface: the UNIX legacy, a lively ecology
https://club.unix.rocks/commentary/under-linux/An open invitation to Linux users across the board, offering a closer look at the penguin and its iceberg, a walk across the ecosystems that make it possible, an exploration beyond one’s biome.
#linux #bsd #solaris #unix #openbsd #freebsd #netbsd #illumos #plan9
-
Beneath the Linux surface: the UNIX legacy, a lively ecology
https://club.unix.rocks/commentary/under-linux/An open invitation to Linux users across the board, offering a closer look at the penguin and its iceberg, a walk across the ecosystems that make it possible, an exploration beyond one’s biome.
#linux #bsd #solaris #unix #openbsd #freebsd #netbsd #illumos #plan9
-
Beneath the Linux surface: the UNIX legacy, a lively ecology
https://club.unix.rocks/commentary/under-linux/An open invitation to Linux users across the board, offering a closer look at the penguin and its iceberg, a walk across the ecosystems that make it possible, an exploration beyond one’s biome.
#linux #bsd #solaris #unix #openbsd #freebsd #netbsd #illumos #plan9
-
Beneath the Linux surface: the UNIX legacy, a lively ecology
https://club.unix.rocks/commentary/under-linux/An open invitation to Linux users across the board, offering a closer look at the penguin and its iceberg, a walk across the ecosystems that make it possible, an exploration beyond one’s biome.
#linux #bsd #solaris #unix #openbsd #freebsd #netbsd #illumos #plan9
-
Beneath the Linux surface: the UNIX legacy, a lively ecology
https://club.unix.rocks/commentary/under-linux/An open invitation to Linux users across the board, offering a closer look at the penguin and its iceberg, a walk across the ecosystems that make it possible, an exploration beyond one’s biome.
#linux #bsd #solaris #unix #openbsd #freebsd #netbsd #illumos #plan9
-
RE: https://mstdn.social/@osnews/116558432757099143
»For all we know, this patch of slop or the next one contains a bunch of #GPL code because it just so happens that’s where the ball tumbling down the developer’s pachinko machine ended up.« 🔥
-
RE: https://mstdn.social/@osnews/116558432757099143
»For all we know, this patch of slop or the next one contains a bunch of #GPL code because it just so happens that’s where the ball tumbling down the developer’s pachinko machine ended up.« 🔥
-
RE: https://mstdn.social/@osnews/116558432757099143
»For all we know, this patch of slop or the next one contains a bunch of #GPL code because it just so happens that’s where the ball tumbling down the developer’s pachinko machine ended up.« 🔥
-
RE: https://mstdn.social/@osnews/116558432757099143
»For all we know, this patch of slop or the next one contains a bunch of #GPL code because it just so happens that’s where the ball tumbling down the developer’s pachinko machine ended up.« 🔥
-
RE: https://mstdn.social/@osnews/116558432757099143
»For all we know, this patch of slop or the next one contains a bunch of #GPL code because it just so happens that’s where the ball tumbling down the developer’s pachinko machine ended up.« 🔥
-
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟲/𝟬𝟱/𝟭𝟭 (Valuable News - 2026/05/11) available.
https://vermaden.wordpress.com/2026/05/11/valuable-news-2026-05-11/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
-
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟲/𝟬𝟱/𝟭𝟭 (Valuable News - 2026/05/11) available.
https://vermaden.wordpress.com/2026/05/11/valuable-news-2026-05-11/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
-
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟲/𝟬𝟱/𝟭𝟭 (Valuable News - 2026/05/11) available.
https://vermaden.wordpress.com/2026/05/11/valuable-news-2026-05-11/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
-
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟲/𝟬𝟱/𝟭𝟭 (Valuable News - 2026/05/11) available.
https://vermaden.wordpress.com/2026/05/11/valuable-news-2026-05-11/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
-
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟲/𝟬𝟱/𝟭𝟭 (Valuable News - 2026/05/11) available.
https://vermaden.wordpress.com/2026/05/11/valuable-news-2026-05-11/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
-
Just installed #OpenBSD on my #Thinkpad #X60 - a very old #32bit laptop. Works fine, still usable for everything except web browsing. OpenBSD has no #firefox or #Chromium in the official repos. For modern web browsing #Dillo or #Netsurf just can't handle the job. I use #suckless #surf web browser but it crashes very often :blobugh:
-
Just installed #OpenBSD on my #Thinkpad #X60 - a very old #32bit laptop. Works fine, still usable for everything except web browsing. OpenBSD has no #firefox or #Chromium in the official repos. For modern web browsing #Dillo or #Netsurf just can't handle the job. I use #suckless #surf web browser but it crashes very often :blobugh:
-
My Sunday challenge: installing #Devuan in place of #OpenBSD on my laptop so I can install #postmarketOS on an old tablet, because for some reason I only have a blue USB port on that laptop (my SFF PC has a whole bunch of USB ports, but none are blue). Let's see how well restoring the backup will work once I reinstall OpenBSD.
I wonder how many years worth of work would it take to create a #NetBSD / #smolBSD based mobile distro after #postmarketOS has done more progress...
-
My experiment of using only base install of #OpenBSD in console, has yielded joy and insights. Returned to #Perl, which was my first professional programming language in the 90s, learning how capable #vi is (not vim or neovim) and appreciating #tmux.
I have a cli http get command, but no https yet since the needed Perl modules are not installed. This led to me using FTP to download all the RFCs in txt, and starting an implementation in C.
The OpenBSD man pages are indeed great. Without a browser, I am relying upon them and my Harbeson and Steele C book. I will have to download the openbsd src soon tho, to get some example C code.
I’m not a good C programmer, having to unlearn alot of habits from using higher order languages, and am still exploring good patterns for C functions wrt memory management and error handling. I keep trying to write with mathematical types, not bytes in memory.
But, it’s fun, and I fell aseep last night thinking about my project, and looking forward to finding some time to continue it today.
-
My experiment of using only base install of #OpenBSD in console, has yielded joy and insights. Returned to #Perl, which was my first professional programming language in the 90s, learning how capable #vi is (not vim or neovim) and appreciating #tmux.
I have a cli http get command, but no https yet since the needed Perl modules are not installed. This led to me using FTP to download all the RFCs in txt, and starting an implementation in C.
The OpenBSD man pages are indeed great. Without a browser, I am relying upon them and my Harbeson and Steele C book. I will have to download the openbsd src soon tho, to get some example C code.
I’m not a good C programmer, having to unlearn alot of habits from using higher order languages, and am still exploring good patterns for C functions wrt memory management and error handling. I keep trying to write with mathematical types, not bytes in memory.
But, it’s fun, and I fell aseep last night thinking about my project, and looking forward to finding some time to continue it today.
-
My experiment of using only base install of #OpenBSD in console, has yielded joy and insights. Returned to #Perl, which was my first professional programming language in the 90s, learning how capable #vi is (not vim or neovim) and appreciating #tmux.
I have a cli http get command, but no https yet since the needed Perl modules are not installed. This led to me using FTP to download all the RFCs in txt, and starting an implementation in C.
The OpenBSD man pages are indeed great. Without a browser, I am relying upon them and my Harbeson and Steele C book. I will have to download the openbsd src soon tho, to get some example C code.
I’m not a good C programmer, having to unlearn alot of habits from using higher order languages, and am still exploring good patterns for C functions wrt memory management and error handling. I keep trying to write with mathematical types, not bytes in memory.
But, it’s fun, and I fell aseep last night thinking about my project, and looking forward to finding some time to continue it today.
-
My experiment of using only base install of #OpenBSD in console, has yielded joy and insights. Returned to #Perl, which was my first professional programming language in the 90s, learning how capable #vi is (not vim or neovim) and appreciating #tmux.
I have a cli http get command, but no https yet since the needed Perl modules are not installed. This led to me using FTP to download all the RFCs in txt, and starting an implementation in C.
The OpenBSD man pages are indeed great. Without a browser, I am relying upon them and my Harbeson and Steele C book. I will have to download the openbsd src soon tho, to get some example C code.
I’m not a good C programmer, having to unlearn alot of habits from using higher order languages, and am still exploring good patterns for C functions wrt memory management and error handling. I keep trying to write with mathematical types, not bytes in memory.
But, it’s fun, and I fell aseep last night thinking about my project, and looking forward to finding some time to continue it today.
-
My experiment of using only base install of #OpenBSD in console, has yielded joy and insights. Returned to #Perl, which was my first professional programming language in the 90s, learning how capable #vi is (not vim or neovim) and appreciating #tmux.
I have a cli http get command, but no https yet since the needed Perl modules are not installed. This led to me using FTP to download all the RFCs in txt, and starting an implementation in C.
The OpenBSD man pages are indeed great. Without a browser, I am relying upon them and my Harbeson and Steele C book. I will have to download the openbsd src soon tho, to get some example C code.
I’m not a good C programmer, having to unlearn alot of habits from using higher order languages, and am still exploring good patterns for C functions wrt memory management and error handling. I keep trying to write with mathematical types, not bytes in memory.
But, it’s fun, and I fell aseep last night thinking about my project, and looking forward to finding some time to continue it today.
-
Until now I've never bothered to look into the internals of keyboard software support and whatnot, but for a long time I somehow put up with #Alpine #Linux (or maybe it was a #KDE / #Wayland issue?) not enabling by default key repeat - or however you call holding a button and have it register as continuous holding instead of a single press.
Lo and behold, on #OpenBSD that just works (I just passed by the conf where key repeat is explicitly defined, so you know real people put real effort into this system). On the other hand, changing the language on my keyboard when using cwm instead of something like KDE?...
setxkbmap -layout ro does not output an error, but still doesn't mean it actually switched me to Romanian (however, something like French actually just works). wsconsctl keyboard.encoding=ro outputs the error that ro is not a valid encoding. According to the documentation, encodings are apparently listed in /usr/include/dev/wscons/wsksymdef.h - and indeed, there seems to be no "ro" in there. Changing locale didn't seem to help either.
Then I took a deep dive into the man page of wsconsctl(8). There it says: "The current mapping can be printed with wsconsctl keyboard.map. The value for each keycode specifies the keysym that is output when each of Key, Shift + Key, AltGr + Key, or Shift + AltGr + Key is pressed" A magic thing then happens... I test wsconsctl keyboard.map+="keycode 15 = l L at" - afterwards, I see in the keyboard mapping "l L at at"; the output is a Polish l=L with slash. I decide to test AltGr with every other key on my keyboard...
I burst into laughter when I realized that I do have now Romanian characters: they were hidden in plain sight, usable with AltGr as modifier. I can't seem to spot them in keyboard.map, where according to the documentation all keysyms should be specified. Maybe setxbkmap did the magic on top? At least I am grateful I can type ăâșîț and not have to copy paste the characters.
