Discover and read the best of Twitter Threads about #OpenBSD
Most recents (4)
Autoinstall #OpenBSD 6.3 on #ThinkPad X1C5 with full disk encryption in five minutes!
1. Turn you computer on
2. Press F1
1. Turn you computer on
2. Press F1
3. Wait a second...
4. Select "Security > I/O Port Access"
@romanzolotarev My T450s is still awesome on OpenBSD. If you pick up a large-capacity battery as well, you can hot-swap the removable battery, and OpenBSD rignning lightweight software can go 12 hours minimum before swapping out the big battery for the slim battery to get a few more hours.
@romanzolotarev I hear great things about the X220 as well, but the T450s is pretty light/small already, so I never considered an X this time around, when I bought it new.
In any case, I'd definitely suggest a ThinkPad. They're half of what they were, but still the best (by a smaller margin).
In any case, I'd definitely suggest a ThinkPad. They're half of what they were, but still the best (by a smaller margin).
@romanzolotarev #OpenBSD also gives me the longest usable lifetime I've ever gotten out of laptops. It doesn't start feeling slow in six months on Windows, in a year on popular Linux crap, two years on mercilessly tuned Linux, or four on FreeBSD. I expect seven or more, total, out of this.
#OpenBSD is great for web development. It's fast, consistent, reliable, well documented. Works great on hardware with limited resources.
disk usage:
- server (base, no packages installed) 1GB
- desktop (200 packages) 5GB
memory usage:
- server 200-400MB
- desktop 2-4GB
disk usage:
- server (base, no packages installed) 1GB
- desktop (200 packages) 5GB
memory usage:
- server 200-400MB
- desktop 2-4GB
Memory: 75M/533M
xenodm + cwm + xterm + httpd
Right after reboot.
xenodm + cwm + xterm + httpd
Right after reboot.
With all my web dev environment running:
... + firefox + tmux + vi
Memory: 634M/1306M
... + firefox + tmux + vi
Memory: 634M/1306M
From what I understand, the latest #OpenBSD vs #Intel thing went a little bit like that:
- OpenBSD: Can we be a part of this rumored Intel bug embargo?
- Intel: No. Go away.
- OpenBSD: Can we be a part of this rumored Intel bug embargo?
- Intel: No. Go away.
- OpenBSD: dev do their homework, fix FPU bug, publish patch.
- Theo (at @BSDCan): we are worried, we don't have access to info. Please help us.
- Intel: publishes official advisory: intel.com/content/www/us…
- Theo (at @BSDCan): we are worried, we don't have access to info. Please help us.
- Intel: publishes official advisory: intel.com/content/www/us…
Now everybody and their dogs are going crazy over #OpenBSD developpers doing their jobs , correcting stuff and "violating"an embargo... That they were *never* a part of. Because Intel did not want them to receive information!
