Elektrine
Log in Register

#netbsd

12 posts · Last used 11d

Back to Timeline
Thread context 2 posts in path
Parent @JdeBP@mastodonapp.uk Open
@JdeBP@mastodonapp.uk
In case people wanted a 2nd chance to object to a compulsory user account age recording + reporting law (the only people who objected in #California that I have found being only interested in 'gratis'
Current reply
@JdeBP@mastodonapp.uk · Mar 05, 2026
Another 2nd chance to tell legislators that the mechanisms that we have inherited from #Unix, and used in loads of #FreeSoftware operating systems from #NetBSD to #Tribblix, do not have date of birth/age fields for user accounts, is #Illinois, where HB5511 is the very same text as #California's, too. https://my.ilga.gov/Legislation/BillStatus?DocTypeID=HB&DocNum=5511&GAID=18&LegID=167486 It really does seem at this point that this is model legislation. Sponsors in Illionois are Jennifer Gong-Gershowitz, Margaret Croke, Janet Yang, Rohr, Kimberly Du Buclet, Natalie A. Manley, Angelica Guerrero-Cuellar, Rick Ryan, Michelle Mussman, Martha Deuter and Tracy Katz Muhl. The bill is in the judiciary–civil committee as of yesterday. It was introduced last month, 1 day after it was introduced in Colorado. I wonder in what other states it has just turned up. A lobby organization handing pre-drafted bills to multiple sets of legislators is not unknown. @nileane@nileane.fr @RunxiYu@social.treehouse.systems #CaliforniaLaw #USLaw #IllinoisLaw #FreeSoftware #AgeVerification
View full thread on mastodonapp.uk
0
0
0
Thread context 2 posts in path
Parent @reallyflygreg@mstdn.ca Open
on mstdn.ca
Open ancestor post
Current reply
@JdeBP@mastodonapp.uk · Mar 02, 2026
@reallyflygreg@mstdn.ca @toddalio@mstdn.ca I'm inclined to believe that it is indeed the people who don't understand technology (specifically: they think that everything works like their smart 'phone or Microsoft Windows 11 PC do) making policy; or that they did understand the technology and were just crap at drafting legislation such that it could distinguish the Microsoft Store, Google Play, the Apple App Store, et al. from #Ubuntu's package repository and #OpenBSD's ports tree. And that distinguishing criterion is not #FreeSoftware. Given the aims, the #California legislators would want #FDroid to be required to hand over #AgeVerification data to free-software apps that F-Droid allows, that themselves want to impose age restrictions (on, say, showing certain content to minors) via the route of getting the account holder's age (bracket) information from the operating system via a 'signal' from the 'store'. https://monitor.f-droid.org/anti-features #FreeBSD #NetBSD #Debian #CaliforniaLaw #USLaw
View full thread on mastodonapp.uk
0
0
0
@hbrpgm@adalta.social · Feb 12, 2026
📺 https://peer.adalta.social/w/qce11wDNyBC78tLqnRKmds 🔗 [🇩🇪🇺🇸🇫🇷](https://p4u.xyz/ID__FKNQB6R/1) La configuration d'un système NetBSD en lecture seule atténue un point de vulnérabilité critique souvent négligé : la corruption du système de fichiers sur des supports de stockage peu fiables. #vulnerability #netbsd #runbsd #ownyourdata #itnotes
View on adalta.social
0
0
0
@hbrpgm@adalta.social · Feb 12, 2026
📺 https://peer.adalta.social/w/nQCwqAv8Gf7ahWVFEfdz2R 🔗 [🇩🇪🇺🇸🇫🇷](https://p4u.xyz/ID__FKNQB6R/1) A practical guide to hardening embedded systems by eliminating file system write vulnerabilities through a memory-backed root configuration. #vulnerability #netbsd #runbsd #ownyourdata #itnotes
View on adalta.social
0
0
0
@hbrpgm@adalta.social · Feb 12, 2026
📺 https://peer.adalta.social/w/bG7GEPHbVSBzsFmeoM1LAD 🔗 [🇩🇪🇺🇸🇫🇷](https://p4u.xyz/ID__FKNQB6R/1) Die Absicherung des Dateisystems als kritische Maßnahme gegen Datenkorruption und Ausfälle #vulnerability #netbsd #runbsd #ownyourdata #itnotes
View on adalta.social
0
0
0
Thread context 2 posts in path
Parent @cks@mastodon.social Open
on mastodon.social
Open ancestor post
Current reply
@JdeBP@mastodonapp.uk · Feb 12, 2026
@cks@mastodon.social OpenWatcom vi is source available. https://mastodonapp.uk/@JdeBP/116052015020764901 Ritter's Heirloom #vi is in #FreeBSD ports today, coming from the same place that it has for a long time. https://freshports.org/editors/2bsd-vi/ It was dropped from #ArchLinux because it did not compile and hadn't changed in 20 years. Ironically, this is because the (GNU) C language had changed, and it has to nowadays be compiled forcing an older GNU C language version. https://bbs.archlinux.org/viewtopic.php?pid=2285124#p2285124 Several people have independently discovered the Makefile patch that gets it to build on #Debian and the like. https://forums.debian.net/viewtopic.php?p=629775 https://gist.github.com/cwfoo/01abac5c39f398b7e7b16a2b87aa518b #elvis, the precursor to #nvi, is packaged for both #NetBSD/#pkgsrc and #OpenBSD. https://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/editors/elvis/index.html https://github.com/openbsd/ports/tree/master/editors/elvis #retrocomputing #ComputerHistory #Watcom #OpenWatcom
Quoting
JdeBP @JdeBP@mastodonapp.uk
On #Illumos, Jov vi is in /usr/src/cmd/vi: https://github.com/illumos/illumos-gate/tree/master/usr/src/cmd/vi On #OpenBSD, Bostic #nvi is in /usr/src/usr.bin/vi/vi; #NetBSD having it in /usr/src/external/bsd/nvi; and #FreeBSD in /usr/src/contrib/nvi: https://github.com/freebsd/freebsd-src/tree/main/contrib/nvi FreeBSD has an nvi2 in ports: https://freshports.org/editors/nvi2/ OpenBSD has elvis in ports: https://github.com/openbsd/ports/blob/master/editors/elvis/pkg/DESCR Ritter's Heirloom vi is on SourceForge: https://ex-vi.sourceforge.net STEVIE was posted to comp.sources.unix in 1988: https://sources.vsta.org/comp.sources.unix/volume15/stevie/ Unfortunately, Sven Guckes's vi Clones WWW site was never completed with some of this, notably lacking Heirloom vi, for example. https://guckes.net/vi/clones.html But it does mention oft-overlooked commercial clones such as Watcom's vi, a from-scratch implementation started in 1983 that is also now source-available: https://github.com/open-watcom/owp4v1copy/tree/master/bld/vi #vi #retrocomputing #ComputerHistory #STEVIE #elvis #VIM #NeoVIM #Watcom #OpenWatcom
View full thread on mastodonapp.uk
0
0
1
Thread context 2 posts in path
Parent @JdeBP@mastodonapp.uk Open
@JdeBP@mastodonapp.uk
People waxing lyrical about using 'original vi', both nowadays in 2026 and back in 2006, haven't a clue what that is. There's only one family of operating systems where 'vi' will actually run the orig
Current reply
@JdeBP@mastodonapp.uk · Feb 11, 2026
On #Illumos, Jov vi is in /usr/src/cmd/vi: https://github.com/illumos/illumos-gate/tree/master/usr/src/cmd/vi On #OpenBSD, Bostic #nvi is in /usr/src/usr.bin/vi/vi; #NetBSD having it in /usr/src/external/bsd/nvi; and #FreeBSD in /usr/src/contrib/nvi: https://github.com/freebsd/freebsd-src/tree/main/contrib/nvi FreeBSD has an nvi2 in ports: https://freshports.org/editors/nvi2/ OpenBSD has elvis in ports: https://github.com/openbsd/ports/blob/master/editors/elvis/pkg/DESCR Ritter's Heirloom vi is on SourceForge: https://ex-vi.sourceforge.net STEVIE was posted to comp.sources.unix in 1988: https://sources.vsta.org/comp.sources.unix/volume15/stevie/ Unfortunately, Sven Guckes's vi Clones WWW site was never completed with some of this, notably lacking Heirloom vi, for example. https://guckes.net/vi/clones.html But it does mention oft-overlooked commercial clones such as Watcom's vi, a from-scratch implementation started in 1983 that is also now source-available: https://github.com/open-watcom/owp4v1copy/tree/master/bld/vi #vi #retrocomputing #ComputerHistory #STEVIE #elvis #VIM #NeoVIM #Watcom #OpenWatcom
View full thread on mastodonapp.uk
0
0
1
@JdeBP@mastodonapp.uk · Feb 11, 2026
People waxing lyrical about using 'original vi', both nowadays in 2026 and back in 2006, haven't a clue what that is. There's only one family of operating systems where 'vi' will actually run the original vi program by Joy, Horton, et al.: #Illumos and its derivatives #Tribblix, #OmniOS, and #SmartOS. *Everyone else* uses one of the ground-up clones. On #FreeBSD, #OpenBSD, and #NetBSD, it's Bostic's early 1990s #nvi, which was derived from Kirkendall's elvis, a clone written some time around 1990. On Linux-based operating systems, vi either is Bostic nvi, or is one of the derivatives of STEVIE (the middle-1980s vi clone for the Atari ST that inspired Kirkendall to write elvis in the first place): Moolenaar's VIM or NeoVIM. On none of those will you get original Joy+Horton vi in base, or indeed packaged/in ports. Yes, Heirloom vi exists, which is Ritter's 2002 fork of 1985 Joy+Horton vi. But it's not even available in Arch Linux nowadays. #vi #retrocomputing #ComputerHistory
View on mastodonapp.uk
0
1
0
@xhr@infosec.exchange · Jan 31, 2026
I wrote a small article on how to backup Unix servers using tar and age. Nothing fancy, just the script and concept I use for all my servers. https://xosc.org/backup-server.html #openbsd #freebsd #netbsd #linux
View on infosec.exchange
7
0
4
@bentsukun@mastodon.sdf.org · Jan 31, 2026
#NetBSD peeps! There is a (mostly) working #Valgrind implementation for NetBSD at https://github.com/paulfloyd/valgrind-netbsd It would be great if we could get a (binary) package for it!
View on mastodon.sdf.org
0
0
1
@JdeBP@mastodonapp.uk · Jan 29, 2026
@pu@ieji.de That's difficult to answer without a concrete idea of what a dependency is. If it's who develops it, then #GhostBSD's major developers are in Canada, and #MirBSD's major developers are in the E.U./Switzerland. If it's which BSDs would be unaffected if Microsoft-owned GitHub decided to pull the rug out from underneath them, then the answer is rather different. Financial dependencies, and WWW/mail/other hosting dependencies, are different again. #FreeBSD #OpenBSD #MidnightBSD #DragonFlyBSD #NetBSD
View on mastodonapp.uk
0
0
0
Boosted by CM Harrington @octothorpe@mastodon.online
@stefano@mastodon.bsd.cafe · Jan 03, 2026
AI models don’t really 'get' the BSDs. As a result, they often provide incomplete, imprecise, or flat-out wrong answers by defaulting to Linux paradigms. When it comes to illumos-based systems, they just completely lose the plot. This is becoming a serious issue for the BSDs and illumos ecosystems. We are seeing entire websites flooded with AI-generated tutorials and guides that are totally incorrect. Most people don't realize this; they follow the instructions, fail, and then assume that the BSDs doesn't work well or are 'unstable' because they have supposedly changed since the guide was written. Luckily, some people eventually find my blog, reach out, and finally understand what's actually going on. Others, unfortunately, end up on major social sites or comments, claiming that these systems are broken. In 2026, one of our greatest challenges will be teaching people how to vet their sources and filter information. And I see this as a very, very uphill battle. #IT #SysAdmin #FreeBSD #NetBSD #OpenBSD #illumos #News #UnderstandingText #Disinformation
View on mastodon.bsd.cafe
187
0
142

You've seen all posts