14 ms·
OpenBSD 7.3
- higherhalf 4y agoThere's something mildly charming about fixes to ed(1) in software released today. > Fixed ed(1) to print bytes read/written and the ? prompt to stdout, not stderr.
- hestefisk 4y agoed is still the standard editor.
- VWWHFSfQ 4y agowhat do you mean by standard editor
- mstevens 4y agoProbably a reference to https://www.gnu.org/fun/jokes/ed-msg.html https://www.gnu.org/fun/jokes/ed-msg.html
- mrweasel 4y agoThe POSIX standard defines ed as one of the editors that must be present for a system to be standard complaint, the other being vi I believe. You can always expect ed to be available to you on a Unix system.
- doubled112 4y agoThis was initially why I learned enough of the vi keybinds to get by. You can expect it to be there.
- znpy 4y agoYou can expect that on a unix system that has applied, paid and received the unix certification. Most linux distros (and most BSDs afaik) are not unix certified. MacOS is, for that matter.
- zinekeller 4y agoPOSIX != Unix (the certification) It is true that all certified Unix systems follows POSIX, but it doesn't mean that non-certified systems are forbidden to follow POSIX. Most Linux distributions have ways to turn to 98% compliant, and BSDs have always strive to follow POSIX. Weird fact: POSIX was actually named by RMS.
- chungy 4y agoOpenBSD was fairly anti-POSIX in the past. I don't know if that's relaxed at all, but they very much do not chase after it.
- krylon 4y agoBut they do have ed, vi (plus ex), and mg (which is not standard but nice to have) in their base system.
- chungy 4y agoTwo of those programs predate POSIX and do not indicate that OpenBSD follows POSIX. They are making their operating system to the design they like best. Some of it happens to coincide with what POSIX asks for, but it is merely coincidental.
- krylon 4y agoI vaguely recall some interview with or blog post / talk by an OpenBSD developer, where they said that POSIX tended towards adopting whatever GNU/Linux did, and that the BSD crowd's interests were not taken into consideration that much. I don't know much about the process behind POSIX/SUS, but I can understand how OpenBSD developers wouldn't be super enthusiastic about POSIX compliance if they felt their input was falling on deaf ears. FWIW, I did use the SUS as my main reference when writing a few hobby projects, and OpenBSD gave me no problems whatsoever. macOS, on the other hand, which is a certified Unix, did not support barriers at the time (that was ~10 years ago, I have no idea if Apple added support since). (I know barriers are optional, but come on.)
- zinekeller 4y agoed: https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/utilities/ed.html https://pubs.opengroup.org/onlinepubs/9699919799.2018edition... vi: https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/utilities/vi.html https://pubs.opengroup.org/onlinepubs/9699919799.2018edition...
- chasil 4y agoYou can see all of the utilities this way. The ex editor is also standard. https://pubs.opengroup.org/onlinepubs/9699919799/utilities/ https://pubs.opengroup.org/onlinepubs/9699919799/utilities/
- madars 4y agoTIL: busybox has ed and vi but not ex. https://www.busybox.net/downloads/BusyBox.html https://www.busybox.net/downloads/BusyBox.html (so ex might be nice to learn but it might be not available on common systems like OpenWRT)
- wahern 4y agoTechnically, vi and ex are part of the User Portability Utilities extension.
- 64operator 4y agoEven DOS and VMS had ed, I'm sure other OSs too.
- deleted 4y ago[deleted]
- adl 4y agoHere: https://www.gnu.org/fun/jokes/ed-msg.en.html https://www.gnu.org/fun/jokes/ed-msg.en.html
- cperciva 4y agoAnd there's even a book about it, in case anyone has trouble figuring out how to use ed: https://www.tiltedwindmillpress.com/product/ed/ https://www.tiltedwindmillpress.com/product/ed/
- codetrotter 4y agoLove the books by mwl. Have physical copies of several of them, and the whole bunch of the ebook versions. Currently reading one of the physical copies. The one about Ed I have in ebook format only and didn’t read it yet. Will get to that one after I finish reading the physical books that I have from him.
- nixcraft 4y agoIn the old days, Unix rescue boot floppy disk to fix workstations or servers only included minimal text editors such as ed (i think vi was added later). So if you were a Unix admin or power user, you need to know ed to fix the dam system. The 'ed' text editor was available everywhere. These days rescue disks boot from USB or CD/DVD-ROM and may have a full desktops or operating systems running. A little bit of history, I guess. BTW, I prefer https://www.system-rescue.org/ https://www.system-rescue.org/ these days to fix Linux bare metals.
- kjs3 4y agoPerhaps more important, as a line editor, 'ed' would often work when your terminal was otherwise too borked up for vi or pico to work.
- anyfoo 4y agoThough in most cases, you can just type “reset” to reset your terminal to a sane state. If the problem is not the terminal’s state, but how software is trying to talk to it, setting TERM=vt100 (with a “reset” for good measure afterwards) usually works for most if not all terminals nowadays.
- kjs3 4y agoI used 'stty sane' or mucked with 'tset' directly. To many possibilities of 'reset' being aliased to something I might not want. setting TERM=vt100 (with a “reset” for good measure afterwards) usually works for most if not all terminals nowadays Kids these days and their 'everything is a vt100'. Perhaps true nowadays, but certainly not always (looks at his HP700/96).
- vbezhenar 4y agoLast time I checked, OpenBSD installer didn't have any editors but ed.
- cylinder714 4y ago
- ianai 4y agoIs there much that absolutely can’t be ran on OpenBSD without dropping into code? With its history of sane security it might offer some useful applications now.
- 5e92cb50239222b 4y ago"Modern" .NET is not compatible with it (or as Microsoft would say, "OpenBSD is not compatible with .NET"), and there doesn't seem to be much interest in resolving that. For comparison, it is available from official repositories at least on Ubuntu, Fedora, RHEL, and Arch Linux, and I use it daily to build and host stuff for $DAYJOB.
- clort 4y agoI don't know about .NET or OpenBSD specifically but Mono claims to be available on all BSD platforms -> https://www.mono-project.com/docs/about-mono/supported-platforms/bsd/Mono https://www.mono-project.com/docs/about-mono/supported-platf...
- daneel_w 4y agoIs there a huge difference between that and what Mono offers?
- dvzk 4y agoYes, and this is tantamount to suggesting that Python developers should be satisfied with Python 2.0 (arguably 1.0 if you do F# development). Mono is effectively dead and abandoned, and it only exists now for historical reasons.
- daneel_w 4y ago>"Yes, and this is tantamount to suggesting that Python developers should be satisfied with Python 2.0 (arguably 1.0 if you do F# development). Mono is effectively dead and abandoned, and it only exists now for historical reasons." There's no suggestion being made here, directly or implied. I'm asking because I have no experience with .NET and am for the most part unfamiliar with both it and Mono, but my colleagues recently spent a fair bit of time to "de-dotNETify" a large chunk of our platform and move it towards running entirely on Mono, and I figured they knew what they were doing.
- j_not_j 4y agoEvery six months for the last 24 or 25 years (the web pages came after the early releases so a bit of uncertainty there. Explore for yourself at https://cvsweb.openbsd.org/www/ https://cvsweb.openbsd.org/www/) And even vi gets fixes these days (Fixed handling of escaped backslashes in vi(1) ex_range).
- mattl 4y agoAlmost 28 years. 6.8 was released Oct 18, 2020. (OpenBSD's 25th anniversary) https://www.openbsd.org/68.html https://www.openbsd.org/68.html
- gladiatr72 4y agoNice. I ran into an nvi bug years ago... if ":set numbers" and ":set noleftright" and then loaded a file of more than several kilobytes it would go into a malloc loop and segfault. We tracked it down and submitted a patch (this was to FreeBSD) and was told patches to src/contrib were not accepted (nvi was still "owned" by sleepycat). Good to know that at a certain point, function can overtake form!
- MobiusHorizons 4y agoExciting to see some initial work to support the rk3588 soc. It has a lot of potential for use as a NAS or router or home server.
- neodypsis 4y agoCould it support the PinePhone?
- Panino 4y agoNot yet, but see this: https://news.ycombinator.com/item?id=30019823 https://news.ycombinator.com/item?id=30019823
- Arnavion 4y agoYour link is about the PinePhone (AllWinner SoC). neodypsis is presumably asking about the PinePhone Pro (Rockchip SoC, though not the rk3588).
- ninjin 4y agoFrom what I understand, at least two OpenBSD developers have their hands on PinePhone Pro devices. Not sure about any progress, but at least it shows that there is interest from the developer base.
- ninjin 4y agoProbably [1], but it certainly needs more hands on deck last time I talked to Crystal. [1]: https://research.exoticsilicon.com/series/pinephone_openbsd https://research.exoticsilicon.com/series/pinephone_openbsd
- jmclnx 4y agoAbout to upgrade my amd64 system. I already upgraded my very old i386 (R51e), no issues and very easy. I am getting some mystery core dumps, will look at that later. I suspect the new "Permissions (RWX, MAP_STACK, etc.) on address space regions". but only guessing :) On the i386 I am planning on using a new "old" disk since the old disk is getting tight. Then I will worry about the dumps after an install. edit: Fully updated to 7.3 on amd64, no issues all working perfect. Again easy no no manual configs for me.
- somat 4y agoRelease engineering: Verb see OpenBSD
- unethical_ban 4y agoWhen I was in college I followed FreeBSD and Solaris for a bit just to dabble outside Ubuntu and Fedora. I remember looking for info on FreeBSD versions and wondering what the heck RELENG was.
- sillywalk 4y agoTheo DeRaat (OpenBSD leader) did a talk on the OpenBSD release process back in 2009 [0] [0] https://www.openbsd.org/papers/asiabsdcon2009-release_engineering/ https://www.openbsd.org/papers/asiabsdcon2009-release_engine...
- alberth 4y agoI've always found building/running your app code on OpenBSD (even if it's not your target OS) - makes for a better app overall because of how strict OpenBSD is - it forces your app to run "correctly" more than any other OS. I've been able to find and fix way more app bugs, than when I ran my software on other OS'es
- darknavi 4y agoAny specific examples? I don't daily drive Linux but that sounds interesting. Somewhat related, for Minecraft (Bedrock, C++) we compile with a ton of different tool chains and I really appreciate Clang versus MSVC for how strict the compiler can be (even with /-permissive).
- ninjin 4y agoTed Unangst’s “Developing Software in a Hostile Environment” talk from EuroBSDcon 2019 is a good start. Controlling malloc(3) behaviour with malloc.conf to catch initialisation and Use After Free bugs is a great example from there. Personally, a different userland and directory structure usually also beats out Linux-isms.
- synack 4y agoI wish I could run OpenBSD on the arm64 EC2 instances. Last I checked, there's no driver for Amazon's ENA network interface.
- pedrow 4y agoI have an OpenBSD install in a VM for the reason cited by ninjin: > Personally, a different userland and directory structure usually also beats out Linux-isms. I just upgraded from 7.2 with sysupgrade then pkg_add -u and it worked perfectly without any intervention from me. In the past I remember it needing a bit of tweaking and finger-crossing. Bravo OpenBSD!