schmonz.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
I just want to take a moment to appreciate the #Purescript team members that turned around a fix for my #NetBSD issue faster than I expected. https://github.com/purescript/spago/issues/1418
boostedToday I tried to install #NetBSD 11 on an old Acer E15 laptop that I had been using as a #Debian CLI-only system.
The install was a little dicey. First one failed, but the second time I was able to go all the way through and configure WiFi on the Edimax N150 USB. I kept getting errors in the console about the BIOS (likely related to the battery, which is pretty dodgy).
X started but really didn't run. I could try messing with it, but I'll probably go to #OpenBSD next.
boosted"Target Linux APIs exclusively, ignore everything else existing" allowed exerting power over a large ecosystem. It is hard to get people to believe in things if their employer benefits from them not believing in them.
But honestly this is a bit of a trap, because once you start thinking this way, you're writing POSIX compliant C89 code that can run on a Motorola 68000 and be compiled with PCC. And inventing stuff like rump kernels.
But maybe that's fine. #netbsd
From the point of view of a package creator, it's a bit of a toss-up. #NetBSD's package system has some things that #FreeBSD's does not, and vice versa.
Two examples:
1. FreeBSD some years ago introduced a new +MANIFEST file format based upon the Universal Configuration Language. It can (and does) contain SHA256 hashes of the individual files in a package. NetBSD uses an older +MANIFEST format.
1. NetBSD includes +BUILD_INFO in packages, displayable with pkg_info -B. FreeBSD's +MANIFEST system does not have an equivalent.
That's the same problem that @jaypatelani was having with #NetBSD and a #Thinkpad.
The full dmesg shows the NetBSD problem that wasn't in the screenshot:
ihidev0 at iic1 addr 0x2c: vendor 0x6cb product 0xce67, TPD0
ihidev0: 14 report ids
acpi_gpio_get_int: translate failed: AE_NO_HANDLER
ihidev0: autoconfiguration error: can't find gpioint resource
Vendor 06cb is Synaptic.
That and the Elan are idiosyncratic PS/2 keyboards and mice, on machines with 9 USB root hubs, that also talk a special extension of the PS/2 protocol in order to be touchpads, and that *also* talk over I2C.
There's a Synaptic fingerprint reader to go with it on your second USB hub.
ugen1 at uhub1 port 5
ugen1: vendor 06cb (0x06cb) product 00f9 (0x00f9), rev 2.00/0.00, addr 4
https://mastodonapp.uk/@JdeBP/117393118010891531
#netbsd boostedAn external USB keyboard should work. Everything that I can find indicates that on Thinkpad E14s the keyboard is actually a PS/2 keyboard (sic!). So look at the part of dmesg that scrolled off your screen that deals with PS/2 device enumeration.
There's also some bizarre extra PS/2 stuff related to that Elan USB device, but that's to do with your fingerprint reader/trackpad.
Maybe pressure the @netbsd to fund a developer to look into #NetBSD's I2C and PS/2 drivers and make it recognize and handle these oddball old PS/2 things that #Lenovo decides to use in machines with 9 USB hubs. (-:
I've no idea whom one would even talk to. But if you ever find someone, that's at least what to point them at.
I saw that when @robpumphrey pointed at it. Of course, you *are* one of those people. (-:
Several of those I don't depend from. I have doas, too, for instance. But some I indirectly depend from. #FreeBSD's and #NetBSD's packaging systems use SQLite. #Debian's packages are compressed with xz.
They render just fine in mine, which does not use BDF in the first place, nor PCF.
It's supposed to be a drop-in upgrade for FreeBSD's, #Linux's, #NetBSD's, & others's kernel #VirtualTerminals; so I wrote it to re-use #FreeBSD's vt font format.
That format has no trouble with the supplementary planes, as it uses 32 bits for code point values, albeit that it is limited in some other ways (which I avoided since I allowed multiple font files to be used in concert).
Boring Teams’ meeting happening so let’s play cool kid.
#NetBSD 11.0 on the #ThinkPad P14s Gen 5 AMD. Unfortunately, this fairly recent machine seems to not be well supported: no DRM (1024x768 in vesa mode), no WiFi, no Touchpad, no suspend/resume (needs the S0ix thing). Looks like a no-go on this particular one 🤷♂️
Full dmesg is there https://dmesgd.nycbug.org/dmesgd?do=view&id=9184. Bad news are still news.
Also: I am most displeased that I haven't worked and learned on my #NetBSD IdeaPad netbook since its installation.
Work has a way of interfering with my natural geek tendencies of 'ooooh! here is a shiny new thing to play with!' and that, dear friends, is simply unacceptable.
I need to reactivate my geek to do list, and that includes learning #emacs on #NetBSD 11...
Fortunately, Friday is work from home day, because next week is workshop week. For the whole week. At Accenture.
the funny thing is that I wanted this machine to be headless. Well, I guess that at least it will detect when a screen is plugged 😀
Day 27
New blog post!
For the past few weeks I've been exploring the use of NetBSD as a desktop OS. If the X sets are chosen during install, an X server and the CTWM window manager are integrated into its base system.
There is, however, another window manager I've long had a soft spot for, and that is Openbox. Its very bare bones to start with, but its an excellent foundation for crafting a desktop just the way I like it!
boostedUpdated binary packages on my T430 #NetBSD Laptop yesterday using #pkgsrc 2026Q3. All went great.
Note one minor thing, if you move to #emacs31 you may need to add this exact line to the very first line of ~/.emacs and any other personal .el files:
;; -*- lexical-binding: nil -*-
This will avoid an error prompt about lexical-binding on statrup.
Highly motivated to seek folks with Whistle InterJets -- late-90s 486 SOHO Internet appliance on FreeBSD 2.2.x, resold by ISPs in the US, Europe, and Asia (IBM bought and sunsetted it, and sold off the whistle.com domain). People with long ISP memories may remember it because it was resold by ISPs in US /Europe / Asia (especially Japan).
I'm building a comprehensive info resource (and tailoring modern NetBSD to run on it). We need to find folks with hardware, ephemera, or memories. The software (on 30yo) IDE drives is especially endangered.
Rough site, in all its 1995-grade (but secretly HTML5) "glory":
https://www.alaska.net/~royce/interjet/
(That tilde account is also endangered -- I've also registered a domain and will be moving to it when ready)
Reddit post:
https://www.reddit.com/r/vintagecomputing/comments/1x0kbcs/seeking_folks_with_whistle_interjets/
DM me or hit the email on the page.
Please boost, especially if you have overlap in the retrocomputing or vintage ISP space!
boostedOn #NetBSD I've had issues keeping pkgin (binary packages) and pkgsrc (building libraries from source) synced up with each other so they try to install the same package versions and don't conflict. Is there a good way to do this?
I inadvertently killed my #NetBSD VM in GNOME Boxes. I tried to shrink the disk size, and I guess that's a no-go.
No problem because I installed a new one.
For any Linux or Unix, getting more experience with the installer is always a good thing.
boosted@justine So I've got CoW working on River.
Please test the `ta/netbsd-debug` branch in the CoW repo (this is also PR 416).
There were two things happening here:
1. memfd/mmap page alignmeent changes (padding).
2. CoW was filling up the main buffer when talking to River which blocked on #netbsd.
I do have a wayland patch for this which I will send through to the maintainer of wayland.
But we should be OK without it for now.
There is a sister commit to this, in #river, to increase the buffer which river and the WM use -- this will also help with some of the messaging, but I've fixed CoW to be more sensible about what it sends over.
For those of you who are using NetBSD, and can test this for me, I'd appreciate it.
As always if you have any questions, come and find me on IRC: #cow-wayland on libera.chat
Special thanks goes to @sborrill for allowing me access to a NetBSD VM over which I could debug this. Stephen, I'll let you know when I'm finished with your VM. :)
Day 26
Created an account on @Codeberg and uploaded my Openbox and X11 configs.
https://codeberg.org/dwarmstrong/dotfiles/src/branch/main/.config/openbox
@EnercoConseils
"La Document Foundation a clarifié sa position sur l’IA. Si elle n’a rien contre les LLM par principe"
Ca commence et termine pas bien, ça veux donc dire que c'est juste un détail technique, une question de temps .. Bref la slopisation de l'écosystème libre (linux, debian..) me rends triste.
C'est la fin de l'ère où le logiciel libre se voulait avoir une portée humaine et sociale, une ère où parler d'éthique était normal.
*team vieux con ;)*
s'en retourne étudier l'informatique décoloniale du futur #permacomputing qui permettra dans un premier temps de travailler sur presque n'importe quelle machine déjà construite (team #netbsd #uxn :)
boostedWas thinking if,when #NetBSD would do on-demand populating of "/dev" as current FreeBSD versions do. Then found ...
Re: FreeBSD's /dev on NetBSD, response 20050813,
by Hans P S,
https://mail-index.netbsd.org/tech-kern/2005/08/13/0006.html
... I ask as see the nodes in "/dev" in NetBSD v11 for the bits that are missing from the system, or some that are not used yet.
Also, due to ...
https://hachyderm.io/@oxy@bsdlab.au/117387881101207127
... So ... has there been any (improve|move)ment since c 2005?
Improving and Stabilizing the Racoon2 IKE Daemon in NetBSD