brynet

40 ms·

421.
by brynet 11y ago
There are many inherent problems with utilities like file(1), however, if people are going to continue using them then we should try to make the best implementation possible. This new implementation was created from scratch, carefully, with
422.
by brynet 11y ago
I posted a portable version on twitter a few hours ago, but this is just something I put together quick without much testing so "YMMV". https://twitter.com/canadianbryan/status/591997995459051520
423.
Brian Callahan's OpenBSD Talk at RPI RCOS(youtube.com)
5 points by brynet 12y ago|0 comments
424.
OpenBSD 5.7 rcctl utility(brynet.biz.tm)
8 points by brynet 12y ago|0 comments
425.
by brynet 12y ago
Marc Espie is who developed the package tools, and has given talks about it. Ted Unangst created signify, which is the basis for the package signing capabilities. You could also check the pkg_add(8), signify(1) and ports(7)/packages(7)
426.
by brynet 12y ago
You might also want to take a look at pkg_check(8). http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/...
427.
by brynet 12y ago
OpenBSD's ports tree is only distantly related to FreeBSD, and the package system is a complete rewrite. Implying that it shares any of the same problems without researching it is being quite disingenuous. Users are only discouraged fr
428.
by brynet 12y ago
OpenBSD's port of GNOME3 does not rely on systemd at all.
429.
by brynet 12y ago
This video was created by the GNOME maintainer for OpenBSD. https://twitter.com/ajacoutot/status/586957762170597376
430.
Puffy in the cloud: ownCloud on OpenBSD(homing-on-code.blogspot.com)
5 points by brynet 12y ago|0 comments
431.
by brynet 12y ago
This is an old Unix utility, OpenBSD versions <=5.5 shipped with a much older version from CSRG times. It was recently updated to the rewrite done by Tony Finch. http://dotat.at/prog/unifdef/
432.
by brynet 12y ago
What isn't a "normal bug"? OpenBSD developers fix a lot of bugs in the course of development, the far reaching security consequences of seemingly innocuous pieces of code are often difficult to evaluate, instead fixes go in a
433.
by brynet 12y ago
And the nginx in ports still maintains at least one significant OpenBSD patch: chroot(2) functionality.
434.
by brynet 12y ago
"[NetBSD's] reallocarray was [just] fixed to behave like OpenBSD. Now it’s a 13 line replacement for a 10 line function. But at least it doesn’t have any code written by an OpenBSD developer."
435.
by brynet 12y ago
A note on Xfce's portability: "All but one of those screenshots were taken on machines running OpenBSD -current, a good proof that Xfce is still portable and friendly to all Unix systems."
436.
by brynet 12y ago
This is an 8-part series of posts by the same author, the link at the top of the page. http://technoquarter.blogspot.ca/p/series.html
437.
by brynet 12y ago
That may be unlikely, considering a few of the things you mentioned are proprietary or not available for OpenBSD. What is more likely is that Alexandre created something new, which makes sense considering he also created the sndio API discu
438.
by brynet 12y ago
If you don't have wired networking configured, fw_update(1) won't be able to fetch firmware on first boot, in that case it needs to be run manually. The timezone and a default user can be created during installation, however yes,
439.
by brynet 12y ago
A lot of people get a bad first impression by trying OpenBSD in virtualization, if you want to see how it really performs then try it out on your laptop. OpenBSD has kernel modesetting (KMS) for Intel and AMD graphics. Here's a video f
440.
by brynet 12y ago
OpenBSD doesn't presume to know how you'll use it. That said, it's understandable to be surprised when things 'just work' with very little configuration.
441.
by brynet 12y ago
OpenBSD has used pdksh as their sh(1)/ksh(1) implementation for over 18 years. It has supported command history since the beginning.. http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man1/...
442.
by brynet 12y ago
OpenBSD packages firmware and handles it automatically on first boot with fw_update(1). There is no "manual tweaking", it just means that some wireless adapters won't function using the ramdisk kernel for installation.
443.
by brynet 12y ago
The recommended and supported way of upgrading the base system is to boot a bsd.rd kernel and type 'U'. If you don't have a console, the manual upgrade guide on the website is an added convenience.
444.
by brynet 12y ago
This is oft-repeated, but how is OpenBSD's package management system "not modern"? It handles upgrades properly, modified configuration in /etc is preserved. Packages are cryptographically signed as of 5.5, files are ind
445.
by brynet 12y ago
I wouldn't be so quick to declare the work done in OpenBSD as hand-waiving, especially when the FreeBSD developers you've been talking to are just as uninformed as you are now. Feel free to point them at the link mlarkin himself h
446.
by brynet 12y ago
That's not true. OpenBSD's package system was rewritten by Marc Espie many years ago in perl, the utility names are inherited from FreeBSD, but are now otherwise unrelated.
447.
by brynet 12y ago
Mike Larkin made a follow-up post to the mailing lists mentioning some upcoming work. http://marc.info/?l=openbsd-tech&m=142122093110713&w=2 OpenBSD/i386 still has to run on systems without PAE, but it should a
448.
by brynet 12y ago
OpenBSD/amd64 does have SMEP/SMAP support, this was committed by Jonathon Gray (jsg@) in 2012, using QEMU. It's still hard to come by in actual hardware. http://freshbsd.org/search?project=openbsd&q=SMEP&a
449.
by brynet 12y ago
OpenBSD has switched it's platforms to using PIE (Position-independent Executables) by default. The 5.7 release will also introduce self-relocating static PIE. http://marc.info/?l=openbsd-cvs&m=141922027318727&w
450.
by brynet 12y ago
For userland, JITs continue work because you can still explicitly request mappings that are both writable and executable. W^X is a default policy.

More ›