#beos

10 posts · Last used 10d

Back to Timeline
Eugenia L @eugenialoli@mastodon.social · Aug 04, 2026
Successfully loading Haiku from Grub now (I used to use reFind). Awesome! #beos #haiku #grub #linux #opensource #foss
27
0
6
The 500 Hats of LambdaCalculus @lambdacalculus@masto.hackers.town · Aug 04, 2026
Sad fact: When Be, Inc. was purchased by Palm in 2001, it seemed like #BeOS technology would live on in #PalmOS, and Palm OS 6 would incorporate portions of BeOS into it. Instead, PalmSource (who was developing Palm OS 6, got acquired by ACCESS Co, a Japanese software house, who proceeded to... simply sit on BeOS and Palm OS. While we have #Haiku continuing the BeOS spirit, nothing is continuing the Palm OS spirit. We need that mobile diversity back. A modern Palm OS would rock so hard.
0
0
0
sergio_101 @sergio_101@social.sixdegreesofohio.com · Jul 24, 2026
This weekend, I really need to check into running #HaikuOS on a #MacBookPro. I really loved #BeOS back in the day, and it seems like this would be a fun little plafform to develop apps for fun.
0
0
0
David Cantrell 🏏 @DrHyde@fosstodon.org · Jul 15, 2026
Replying to @rl_dane@polymaths.social
@rl_dane@polymaths.social I used to have #BeOS as my main desktop. On a real #BeBox. I’m sorry to say that #Haiku just ain’t quite right.
7
1
0
Atomozero @atomozero@mastodon.uno · Jul 14, 2026
Haiku just gave beta6 a date: mid-August. Yet the June report still surfaces foundational bugs: an I/O scheduler flaw that could corrupt data on modern SSDs, a memory control register misinitialized at EFI boot, and Haiku Inc.'s 2025 financial report still missing. Technical accounting is punctual, financial accounting is a year behind. https://www.desktoponfire.com/haiku_inc/913/haiku-beta6-data-corruption-bug/ #HaikuOS #BeOS #OpenSource
0
0
0
TomAoki @TomAoki@mastodon.bsd.cafe · Jun 19, 2026
Boosted by oxy ::openbsd:: ::freebsd:: ::runbsd:: @oxy@social.bsdlab.au
Replying to on mastodon.social
@FreeBSDFoundation@mastodon.social I've started investigating #FreeBSD at (maybe) since 2.1.6 in conjunction with several other OS'es including #BeOS, #WinNT4, #超漢字(kinda proprietary package of #BTRON with huge font set) with several #Linux distros (Yggdrasil, Vine and Turbo as far as I can recall now). At the era, my personal daily driver was #OS/2. After IBM discontinued OS/2 and the successor, eComStation, didn't actually released Japanese edition (ordered one and obtained English version for temporary use until it's ready, but never happened), I needed to decide which OS to make my NeXT^H^H^H^Hnext daily driver, and switched to FreeBSD, which seemed to be most familiar with me. I've used several GPUs for XFree86 (and Xorg after it landed) on FreeBSD. At first, VGA/SVGA driver was too slow, so I purchased a license of AcceleratedX to use S3 GPUs (and then, Power9000, Matrox MGA,...) and some ATIs(!). When I've switched my daily driver hardware to notebooks, driver for new GPUs were mostly unavailable after AcceleratedX has gone. But fortunately, found that NVIDIA is providing FreeBSD version of drivers for their cutting edge GPUs and ports were already available. After that, I choose PCs having NVIDIA GPUs everytime I need to purchase one. I was happy for a while, but introduction of iGPUs caused headaches. There were too many screams that graphics/drm-*-kmod at their early phase was quite unstable and often broken. So I've always been looking for notebooks that can disable iGPU via BIOS / UEFI, but it became harder and harder. Now I'm using Minisforum MS-01 that allows installing half size, half height PCIeX16 card which doesn't require additional power supply with RTX A400. And noticed that I'm now one of the maintainers for #NVIDIA driver #ports on FreeBSD. Today, latest Production Branch of NVIDIA GPU drivers 595.84 landed onto ports tree at commit ec6b356f6328. https://cgit.freebsd.org/ports/commit/?id=ec6b356f63289da87c9fbb52cdf558805383caf6
3
0
1

You've seen all posts