What are /r/openbsd's favorite Products & Services?

From 3.5 billion Reddit comments

Besides the ones mentioned,

• hv3 (requires Tk)
• w3m is a terminal browser, but it can display images and is sensitive to some style attributes

> ... I have no way to respond to the bug report...

Yes, you do. This bug report reply is on the bugs@ mailing list.

There is a Majordomo server at https://lists.openbsd.org where, if you subscribe, you may request this archived Email be sent directly to your Email address, where you can then reply to the list, or the author.

Addition info on Project mailing lists may be found at http://www.openbsd.org/mail.html

CVS has worked well for the developers for the last ~18 years. You don't replace something proven just because there's something new and shiny.

OpenBSD was one of the first open source projects to make available their source repositories to the public, you can read more about it in Chuck Cranor and Theo de Raadt's paper on Anonymous CVS.

http://www.openbsd.org/papers/anoncvs-paper.pdf
http://www.openbsd.org/papers/anoncvs-slides.pdf

you are running snapshots then.

to upgrade download a new bsd.rd into /

reboot and type bsd.rd at the boot prompt "boot> bsd.rd"

instead of i for install chose u for upgrade

after upgrade reboot and run sysmerge(8) and then run pkg_add -u

also always look at http://www.openbsd.org/faq/current.html before upgrading

I’ve just launched the site and—what a coincidence—Reyk Flöter has started looking for a developer for a new project (in Zurich, non-remote). Please contact Reyk, if you’re available or can recommend a friend.

Thank you!

See also https://lobste.rs/s/qbynme/launching_bsdjobs_com

> Here we have a serious article about keeping OpenBSD modern done in ... Comic Sans?

It looks like the plan to draw out the people who don't even scroll down TFA before complaining worked!

imo, the web site is wonderful. It has a beautiful feel to it, an aesthetic, if you will, or perhaps a statement on design and fashion (see the recent rush to move from shiny to flat design because it's become the cool thing to do). It's also accessible and doesn't rely on dangerous JavaScript VMs to function. Katherine Prio's artwork is just stunning and unlike anything any other operating system is doing.

(also, it may offend your nerd cred, but after a quick comparison I actually find the serif font my browser gives the paper after scrolling down less readable than Comic Sans...)

If OP’s Mac mini is from 2005, it is macppc, and cannot use syspatch. The first Mac mini with an x86 processor was released in 2006.

>Note that binary patches are only available for the amd64, i386, and arm64 architectures.

From http://www.openbsd.org/faq/upgrade55.html#time_t (emphasis added):

> OpenBSD 5.5 is year 2038 ready on all platforms, but this required a change to a 64 bit time type, which should cover us for the next 290 billion years...

looking at the internet archive seems to hint towards that webpage not being updated in at least 4 years.

it's probably better to look at the release pages to see what the latest is on the crypto stuff: http://www.openbsd.org/54.html and if you really want to dig deeper the changelog: http://www.openbsd.org/plus54.html

as for why they dont use SSL on their website.. i cant speak for them, but i dont really see that theres much need to.

edit: oh yeah. more than that: $OpenBSD: crypto.html,v 1.135 2009/05/11 08:42:15 jsg Exp $

Reading through the upgrade guides, I found this:

> * IPsec HMAC-SHA2 incompatibility: > > Two bugs in IPsec/HMAC-SHA2 were fixed, resulting in an incompatibility with the HMAC-SHA-256/384/512 hash algorithms with previous versions of OpenBSD and other IPsec implementations sharing the bugs. In particular the default authentication algorithm HMAC-SHA-256 is affected. Upgrade both sides together, or switch to another authentication algorithm during the transition.

Source: http://www.openbsd.org/faq/upgrade47.html#hmac-sha2

Here's an article on this subject:

http://bsdly.blogspot.com/2012/12/ddos-bots-are-people-or-manned-by-some.html

You can also rate limit with PF: http://www.openbsd.org/faq/pf/filter.html#stateopts

Ultimately, mitigating DDoS'ing is difficult. Cloudflare can do it because they have the infrastructure for it.

Hi,

You can create it by running :

$ cd /dev $ sudo ./MAKEDEV video2

There is a small utility in base to record / display webcam, see video(1)

You'll want to trunk the three ports together using LACP, then assign the trunk interface to the VLAN.

Just make sure your switchports have the same configuration.

(EDIT: Typo)

Same response as elsewhere: check out more details about the library being bound.

In particular, problems in PHP do not shed light on the OCaml runtime any more than problems in Lotus 1-2-3 shed light on the OpenBSD kernel.

Depends on how you like to read them. You can set up Tiny Tiny RSS as a web-based RSS reader (even if you only serve locally). You can use newsboat if you like to read them from the CLI (which also has tt-rss integrations).

I personally run rss2email from a cron job so that my RSS feeds get sent to my email. I don't need to learn a new UI (and I have all the filtering power of my MUA to auto-delete ones I know I don't want), I can forward them to share, I can control polling frequency, it stays in sync across machines thanks to IMAP, works offline thanks to offlineimap/mbsync, can be easily searched with notmuch, etc.

While Reddit isn't necessarily the best place to report a problem, the same sort of information would be needed here as any other communication channel.

This guidance on problem reporting is from the FAQ: http://www.openbsd.org/faq/faq1.html#Bugs

And here is additional detail on reporting problems: http://www.openbsd.org/report.html

This is pretty much exactly the wrong way around. OpenBSD is easy to set up for either desktop or server use, because it's easy to set up. While FreeBSD has PC-BSD to make desktop use easier, OpenBSD is easy enough on its own that it doesn't need that.

The FreeBSD Handbook is full of awesome and win, and I highly recommend it. No "but" to that at all. OpenBSD does have its FAQ, which is also really good. To say there's no hand-holding is misleading.

For someone like OP who has installed tons of Linux distros (including Arch), having the OpenBSD FAQ and the man pages should be more than enough to get going easily.

you also need to edit /etc/ttys to spawn getty on tty00.

tty00 "/usr/libexec/getty std.9600" vt220 on secure

basically turn the 'status' column from 'off' to 'on'.

edit:

http://www.openbsd.org/faq/faq7.html#SerCon

The package you're referring to called wireguard-tools and is optional on OpenBSD. The kernel implementation wg(4) does not require them to be installed. The official documentation is available on their website, but the package contains the man pages wg-quick(1), wg(8) in addition to a pkg-readme in /usr/local/share/doc/pkg-readmes/wireguard-tools.

My understand is that the wireguard utilities originally supported a userland implementation of the protocol written in Go, which was used on OpenBSD previously, but they also exists for configuration compatibility with other systems.

I am currently using uBlock Origin on the Firefox that comes with OBD 6.4. I might of installed it on 6.3.

I have used this hosts file with some success:

• https://github.com/StevenBlack/hosts

If the man page doesn't list the card as being supported then it's probably safe to assume that it isn't. The OpenBSD documentation has always been excellent from my experience.

I don't know what country you're from so I'm not sure about the pricing where you are. But from a quick check on Amazon UK, the cheapest passively cooled GPU seems to be the 1GB Radeon HD 5450. Though to be honest, it seems a little puny. If I were going to buy a passive card I would probably go for the 2GB Radeon HD 6450. Still not too pricey, but a bit more powerful. Both cards are supported by the Radeon driver. Though I must point out that I have no experience with either card, so buyer beware, as always.

Yeah, one of these (supported by urtwn) in one of these. Not ideal, but hopefully temporary.

> I am wanting to show the current volume in tint2 for whichever device is being used (IE: master or headphones, etc) as well as whether it is muted or not. I am unsure how to show all this. Has anyone done so?

Here is a starting point. I assume that tint2 has the ability to display the output of a shell script, since most status bars have this ability.

A comment by qbit at lobste.rs shows that NetworkManager in Linux has 841045 lines of code, but ifconfig(1) in OpenBSD has 5848 lines of code, so Linux has 143 times more code than OpenBSD to configure the network!

This doesn't count any code in the kernels of Linux or OpenBSD. Most of the auto-join code is in OpenBSD's kernel, in files like src/sys/net80211/ieee80211_node.c

There is no assigned $MAINTAINER at this time, so the port is supported by the Project solely through the ports@ mailing list. You can:

• Ask the list if anyone is currently working on the port. (There's a Github project for work-in-progress ports, and I looked to see if there was anything for gn3 found there before posting this. Nothing there at this time.)

• Use the port as the basis for starting work on an updated port. The Porter's Handbook is a great place to get started.

If you're successful at updating the port, you can post your patches to the ports@ mailing list for review and consideration. If you wish to support the port for others, you could also offer to become the port's $MAINTAINER.

This is something you could have very easily confirmed for yourself..

6.0 snapshots: http://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/

early work-in-progress 6.0 release page: http://www.openbsd.org/60.html

Turning on softupdates will speed filesystem access, which will make the system feel faster. All versions of Linux use async mounts by default, so writes are not synchronised with reads. OpenBSD uses sync mounts by default.

Good luck and welcome to the OpenBSD family.

Current versions of OpenBSD use this syntax for setting priority. You set packet priority as part of the rule instead of a queue definition.

pass in proto tcp to port 22 set prio (2, 5)

There is more detail in the pf.conf man page. Just search for "set prio" on the page and you'll find the details.

"Would be" a more appropriate name, except it is already taken by some other project.

You are encouraged to use libtls[0] anyway, which is a sane wrapper around LibreSSL.

[0] http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man3/tls_accept_fds.3?query=tls_init&sec=3

I don't know all the answers to your questions, but the OpenBSD man pages are the official documentation and are generally very good. They should give you all the info you need:

http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/relayd.8?query=relayd

http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/httpd.8?query=httpd

If httpd isn't sufficient, nginx is available as a package install.

Everyone else has good applicable advice, but I'd just like to drop this here. I see some people advocating running -current but I always advice -release for new users, and for most everyone else actually. From their FAQ,

> Most users should be running either -stable or -release. That being said, many people do run -current on production systems, and it is important that people do so to identify bugs and test new features. However, if you don't know how to properly describe, diagnose and deal with a problem, don't tell yourself (or anyone else) that you are "helping the project" by running -current. "It didn't work!" is not a useful bug report. "The recent changes to the pciide driver broke compatibility with my Slugchip-based IDE interface, dmesg of working and broken systems follow..." might be a useful report.

> Having to rebuild user land on each upgrade.

Correct me if I'm wrong, but if you're updating from a release, you don't have to rebuild userland. You should be able to follow the upgrade guide.

http://www.openbsd.org/faq/upgrade56.html

But I don't know if it would apply from a previous stable release to the next release. It's also a very manual process. Contrast that to FreeBSD: https://www.freebsd.org/releases/10.0R/installation.html

You can donate to the OpenBSD Foundation, which is a registered Canadian not-for-profit.. they use the money to fund the project in various ways (..see their site), or you can donate more directly to the project (..Theo) using the second link.

The method you use is up to you, a business for example may be more inclined to donate to the Foundation.. or an individual with some /r/BitCoin, which Theo himself doesn't accept.

It is also possible to donate hardware to developers, who often need replacement laptops, and other expensive parts.. people with the most skill to work on drivers may not be in the financial position to afford it.

http://www.openbsd.org/want.html

Hi there,

This behavior seems to be related to xdm. For some reason it fails to initialize the default X session, to prompt you for graphical login, and tries to re-start X each time.

Try the following and see if it helps

• boot -s
• disable xdm by commenting out xdm_flags="" from your /etc/rc.conf.local
• Restart the system
• Login
• run X -configure if it works follow the instructions displayed by the command, if not, report back :)

PS: Subscribe to misc (instructions http://www.openbsd.org/mail.html) you will get much faster and more accurate information about your problem.

That's handled by virtio.

http://www.openbsd.org/cgi-bin/man.cgi?query=virtio&manpath=OpenBSD%20Current&sektion=4&format=html

More specifically, viomb:

http://www.openbsd.org/cgi-bin/man.cgi?query=viomb&sektion=4&arch=&apropos=0&manpath=OpenBSD+Current

I'm not sure if it actually works on VMware, however, because it doesn't seem to show up in dmesg. I don't overallocate memory so I've never looked into it before.

You shouldn't need the official VMware tools. OpenBSD should show up as "3rd-party/Independent" without anything having to be installed because of its own vmt driver. It can poll IPs, shutdown/restart guest, etc just like using the proprietary tools.

http://i.imgur.com/NtQsh6X.png

I run tons of OpenBSD VMs using a mix of i386 and amd64. Both work the same way.

Edit: http://www.openbsd.org/cgi-bin/man.cgi?query=vmt&sektion=4

the FAQ gives a little insight. but it all comes down to your needs. i, myself, run nothing that requires or would benefit greatly from 64bit, so i just run the i386 version. lots of support, binaries and such for it, too.

I'm posting this to /r/OpenBSD, because OpenBSD has been famous to be in the protest of the Raspberry PI hypocrisy in regards to claiming to be an open platform; and an OpenBSD port was specifically out-of-the-question, since other platforms, like the BeagleBone, weren't as closed-source as the rpi.

Raspberry PI also has a piece: http://www.raspberrypi.org/archives/6299.

However, it remains to be seen what other components of the Raspberry PI are still proprietary.

I'm only an occasional user of OpenBSD, but if you want to learn C I recommend "The C Programming Language" by Kernighan and Ritchie and "The Practice of Programming" by Kernighan and Pike. "Advanced Programming in the Unix Environment" is my favourite book about Unix programming. I think those are good starting points for becoming a C programmer, if that is what you want.

That said, learning how to code gives nothing to the project. I always wanted to become involved with FreeBSD, but never found the time beyond a little port and some assistance to another porter. Don't get too focused on learning how to program up front, just get involved and pick up what you need on the way.

There is CVSImport bridge which allows git to be used with CVS repos. I haven't tried this particular bridge, so I can't give any tips. https://git-scm.com/docs/git-cvsimport

This StackOverflow posts looks pretty comprehensive. https://stackoverflow.com/questions/584522/how-to-export-revision-history-from-mercurial-or-git-to-cvs/586225#586225

Then there is setting up your own git repo.

Of course now that I'm trying to reproduce the issue, it's working fine... debugging intermittent problems is the worst. No EE messages in /var/log/Xorg*, and nothing in ~/.xsession-errors seemed suspicious, but here is a link to it in case anyone else with more experience can see anything interesting.

The next time the issue recurs, I will grab copies of all those files for closer inspection. I will also try disabling TPM and see if that helps.

Thanks for your help, and also for writing the guide originally - because of it I gave CWM a try, and decided I like it better than i3.

Thanks this is helpful but I think this is just for programs integrated into the OpenBSD os. openbsd_lsblk is a standalone. I think their coding style is similar to the Linux Kernel coding style . but I contribute to project called radare2 (coding style) so I am used to programming their way (except for the space before () in functions that is quite annoying).

No no, I can't handle IDEs. A lot of Emacs users prefer to do everything from within Emacs, but for me, I only chose it over Vim because I keep forgetting to hit insert mode when entering a commit message... that, and it was an excuse to learn Lisp. :-)

On macOS, I still use Atom, but only because I've yet to start work on an editor that's closer to my vision of how web technologies should be used for building graphical applications. It'll take my favourite parts of Vim, Emacs, Atom, and TextMate, so I can finally have a text-editor I can use for the rest of my life.

Rendering HTML and CSS for terminal display is the part I'm most looking forward to. Mainly because nobody's using this perfectly-good CSS feature to style documents rendered by a TTY, because no text browser ever bothered to support it.

/derailing

Okay, fellow vault dwellers and nuka-colics, here's a challenge:

pcgamingwiki mentions that the digital release Mac version of Fallout 2 was actually a DOS version with dosbox.

Is that true? And if so, where can I find it?

https://pcgamingwiki.com/wiki/Fallout_2 (mentioned in section "Availability")

Its good that you ruled out the ram as a potential issue. Sounds like the Braswell bug you mentioned is still happening. I'm assuming you've tried booting without disabling inteldrm? Ultimately this may be a legitimate bug and you should consider filing a problem report.

Sorry, but "apt" doesn't exist on OpenBSD. A vmm(4) guest can certainly operate graphics over a network, whether X, or vnc. I've run webservers in vmm(4) guests.

OpenBSD has vnc packages in its package system, such as ssvnc, x11vnc, and x2vnc.

Want a pain-free experience, older ThinkPad, up to the X1 carbon AFAIK. I prefer the T400 or the R60e (nostalgia for that IBM logo), OpenBSD does also work with libreboot ThinkPads too. I know it's a meme around here, but other computers may make you hate OpenBSD. This will help http://www.openbsd.org/amd64.html

It just depends if your video card is supported or not. Without proper firmware support for your hardware, all operating systems will have laggy video playback, period. http://www.openbsd.org/amd64.html I have a ati radeon 6450 pci express and it is fully supported, OBSD will use the radeondrm firmware and then the ATI driver. The ATI driver will default to a low performance mode, you then write a config to optimize it (see the radeon man page). The same method works with Intel. You can give it a shot, if you device is hooked into ethernet, the rc firsttime script will automatically install all the firmware, if nothing install for you card. Then you are S.O.L. unless you want to get down with assembly language and write custom firmware (you just need to contact the manufacturer and ask them to give you a full device documentation for reference). Good luck ;-)

Use compton to fix choppiness.

compton --backend glx --vsync opengl-mswc --glx-no-stencil

Also as for porting your favorite programs. Check out www.openports.se and see what's available. There may be OpenBSD friendly alternatives to what your trying to do. Trying to compile linux stuff into an OpenBSD enviroment is really tricky and requires alot of knowhow and patching. You can always check the porters handbook too http://www.openbsd.org/faq/ports/index.html

Also qt4/qt5 does work in OpenBSD - i.e. qt-creator, ninja-ide, lumina, qutebrowser

On second thought, you might have mixed up a self compiled -current kernel, with a -release userland.

Be careful. What did you install? What did you upgrade? What did you compile yourself? And how?

http://www.openbsd.org/faq/faq5.html#Flavors

The FAQ is heavily worked on right now, but 5.1 explains it pretty nice. You started with 5.8-release and by applying the errata patches you now following 5.8-stable. http://www.openbsd.org/faq/faq5.html How-to-patch is mostly described in the patch files itself, althought sometimes the directions are "buggy", but because those patches are signed, most times they won't be changed after they got posted to http://www.openbsd.org/errata58.html

A trunk is only applicable if you want three ports on the same VLAN connected to the same device (ie. a switch), thus (somewhat) aggregating the throughput of three links.

My take on the request was to add three interfaces to the same VLAN while connecting them to different devices, which should be done with a bridge.

Both valid answers, but for different circumstances :-)

If you're on current, all you need to know is located at http://www.openbsd.org/faq/current.html

Basically, you fetch the new bsd.rd, move it to / and boot it. Choose option U (upgrade), reboot normally. Run sysmerge and then pkg_add -u. That's it.

-current is usually for devs and/or experienced users. I think -stable is perhaps more suitable for you.

This "gotcha" is only a consideration when multibooting, and when OpenBSD is not the first OS installed, or when the boot partition is unintentionally oversized and the second stage bootloader is moved during an upgrade.

The OpenBSD bootloader depends upon the BIOS for I/O services before the kernel is operating. The kernel must be located in sectors that are addressable by the BIOS. This limit varies, and is specific to the hardware deployed. FAQ 14.8 gives the details.

-- edited for clarity

http://www.openbsd.org/faq/faq5.html#Flavors

Correct, if you checkout -rOPENBSD_5_7 I believe that is the -stable branch which includes all the patches listed in the errata, so you don't need to apply them manually.

The FAQ addresses working on the site. If you find something on the site that is incorrect, im sure the developers would accept a patch, but I would not recommend spending time on much else.

http://www.openbsd.org/faq/faq8.html#wwwnotstd

There seem to be two ways to donate:

• Through the OpenBSD Foundation, which is the topic of the posted mail.
• Through the OpenBSD site, as a "contribution of funds".

Can anybody shed some light on the difference? In particular, is the second way the best way to contribute to "the rest of the system"? My feeling is that the first way distributes somehow evenly between OpenSSH, LibreSSL, ... and (last) OpenBSD as a whole. In any event, although these projects are to some degree autonomous I find this sort of duplication puzzling.

Thanks in advance.

If you refer to character size while using the monitor in console mode you may find guidance in FAQ section 7.5. If you refer to fonts while using the X Windows System, font control and font size selection are discussed as components of the Anti-aliasing and TrueType Fonts section of the FAQ: 8.20. Font management in X is a subject all its own, but that section can get you started.

stable via src with cvs provides you with security updates, current is for developers; things might break. If you know your way around there's nothing wrong with current though, sometimes you'll get asked to install it when you have problems with stable.

following stable

getting started with cvs

When you use current you should also follow the current ports tree. Xenorcara (x windows, the windowing system) is also a seperate repository. Keep things in sync.

This might be of interest to you.

Regrettably, this combination is starting to look iffy. If you insist on sticking with Gumstix, I think it would be best to go with their Linux specs. Otherwise, I would try some other type of hardware.

Further investigation reveals a page about the armish platform, which shows exactly four platforms. However, the release notes for 4.5 show initial ports to the Gumstix and other xscale processors, but I'm not sure what arch those are under.

This question is probably more appropriately asked somewhere else, as it is not specific to OpenBSD.

That said, it looks like the terminfo file for xterm-kitty is not recognized by default, you'll need to set it up yourself. There's some hints in their FAQ.

/u/thfrw is the port maintainer, they might know why it's not mentioned in a pkg-readme or pkg DESCR.

Just look at something like debian security advisories for 2015. Besides some things like maybe libreoffice, iceweasel (firefox), wireshark a lot of obscure programs (ports) aren't common attack vectors.

If you're doing something like running squid on OpenBSD, you should be keeping track of how that is going on. People get paid to do just this.

I can see why vulnerable ports are a concern, but it really isn't a huge deal if you're willing to put in a bit of effort to secure you system. Ports really isn't some of wild west, and even then OpenBSD has lots of exploit mitigation technology to handle issues, although thats a whole nother discussion.

Could you please re-write the USB image with something more adequate than Win32 Disk Imager and try again.

Use Rufus https://rufus.ie/ or whatever else reliable to create your bootable USB. Also, when you exit Windows 10 before booting from USB, click Shift+Power Off instead of just Power Off (this will ensure Win10 really powers off instead of "fast reboot" trick with hibernation.

I'm not the OP here (obviously) but I am considering migrating my current website (Dokuwiki on Debian 10 with Apache) to OpenBSD in the near future. Thought it would be better to post in this existing topic rather than litter the subreddit with another similar post.

Dokuwiki has an install guide for OpenBSD with httpd, as well as URL rewriting. The site has around 1500-2000 monthly unique visitors according to Google Analytics, and being a wiki is almost entirely PHP with some JS thrown in as well. The Dokuwiki instance has a lot of plugins and tweaks. There's a SQLite DB, but Dokuwiki itself does not rely on a database to serve page content.

The existing Debian install is on a 1 core, 1GB cloud VM (Azure B1s) and does not seem to have any capacity issues.

My questions are:

• Do you think httpd would be suitable for serving such a PHP-heavy site? Would NGINX on OpenBSD be a better choice?

• Considering that OpenBSD is more security and less performance-focused than Debian, would the same spec of VM hold up?

• Has anyone used OpenBSD in Azure, and are there any "gotchas?"

I'm testing a local VM on my personal machine to test configs, but of course that's not the same as migrating a production site. Thanks for your insights!

check seccomp-pledge (openbsd pledge for linux using seccomp) ... it would be an awesome project to grow out... developer is busy with other stuff. someone should totally finish it and merge it upstream with seccomp.

https://notabug.org/rain1/linux-seccomp-pledge/

As another alternative if you're just looking to kick the tires and familiarize yourself w/OpenBSD, Vultr.com has both their own instances of OpenBSD and also the ability to upload .iso files of the latest releases.

The downside of the Vultr instances is they break from the conventions of OpenBSD partitioning, which is a lousy way to do things, IMHO and why I use real ISOs.

Regardless, you can have a basic instance in Vultr running for ~$5/mo.

In the four years I've had stuff there, I've had one outage that was more than the time for a reboot of their host OS, and it was only a few minutes.

Support is ticket-only but generally merits a 9/10 from me.

Bit late but Tox had an issue within the project with a member, resulting in a new website and some changes in how the project operates. Here's the new blog explaining it and here's the new official site. It's advised not to use any of the old sites (tox.im) as they are no longer under the control of the tox project

Amazon sells this for nearly $28.

https://www.amazon.com/Creative-Portable-Bluetooth-Transceiver-Nintendo/dp/B00ZYYPFHU/

On sale through woot for 40% discount.

Lenovo ThinkPad L14 (AMD processor) works great for me. Only thing that is not supported is the wifi card. The RTL8192EU wifi dongle solved that part. The L14 is reasonably priced (starting at around 700 dollars), and the RAM can be upgraded to 64GB.

There is apparently a VirtualBox utility that can change the default EFI video mode for the VM, although their documentation claims it should be 1024x768 by default and it clearly is not..

https://www.virtualbox.org/manual/ch03.html#efividmode

It's really frustrating that the only way is reinstalling everything.

>efifb0 at mainbus0: 3840x2160, 32bpp

I've tried to modify this in so many ways 1, 2

My question is if anyone knows how to change EFI resolution because there must be a way apart from those I just checked.

Desktop or Laptop? If you want wifi in a desktop there are several supported usb adapters. Intel processors have microcode updates but not AMD yet. Old server platforms seem to work quite well. I have a dual Xeon socket 2011 system that runs OpenBSD no problem. The only problem is grahphics. Integrated Intel or AMD are the only real supported option. Team green Nvidia only a few really old options are supported with the nv driver. The folks at Nvidia don't think much of OpenBSD to provide a binary driver like they do FreeBSD and nouveau is not ported to OpenBSD. I've never asked why nouveau isn't ported but I would guess because things either work perfectly in OpenBSD or not at all- there is not middle ground. Check out Zanny on Youtube he tries out OpenBSD on desktop hardware and had a quite new AMD card working earlier in the year on 7.0.

Tl;dr - avoid Nvidia graphics, Intel processors have more support in terms of updates, wifi will probably want a usb dongle. This https://www.amazon.com/dp/B00762YNMG/ dongle uses the RUN(4) driver so doesn't need any firmware according to this post: https://www.reddit.com/r/openbsd/comments/og2giv/usb_wifi_dongle_compatible_with_openbsd/

OpenBSD can see the device, but if it doesn't attach as run0 then the exact device you have isn't supported.

The ugen driver provides support for all USB devices that do not have a special driver. It supports access to all parts of the device, but not in a way that is as convenient as a special purpose driver.

This one works for sure if you want to try another inexpensive USB NIC:

[https://www.amazon.com/Plugable-Wireless-802-11n-Network-RTL8188EUS/dp/B00H28H8DU/(https://www.amazon.com/Plugable-Wireless-802-11n-Network-RTL8188EUS/dp/B00H28H8DU/)

> Just bemused why I need to netstart.

> Surely the NIC should just come online again when the cable gets put back in?

Not knowing anything about the rge(4) driver, I could only guess that there may be something in the way the underlying PHY attaches to the NIC. You could consider posting your dmesg(8) here, perhaps someone might get a clue from this information.

If you believe this is a bug, producing driver debugging output with that dmesg may help a developer understand driver state as cables disconnect and reconnect.

• You can enable debugging output with ifconfig(8).
• You can submit problem reports formally to the bugs@ mailing list with sendbug(1), or post them informally to the misc@ mailing list.
• If you have some interest and some C skills, this debugging output may help you work up a fix to the driver yourself. If so, patches in unified diff(1) format are always welcome for review on the tech@ mailing list.

For more on problem reporting, see http://www.openbsd.org/report.html.

I'm not really skilled about openbsd, but one thing I know is that openbsd if focused on security. That's mean that some features like performance and desktop usability take less care by the developer team. Also openbsd team is much more little than the same on linux and of course a lot of things are less advanced. But to be honest the linux kernel is extremely less secure than the openbsd's one. Everything depends of what is important for you. For me on the top of my needs there is security, especially about the kernel.
If for you security is not on the top I suggest you to use linux or if you want try an other unix freebsd could be nice choice. Even osx it's nice.. To show you how much I'm paranoid I tell you my current configuration. I'm using openbsd from inside a virtual macchine. The hypervisor is a freebsd with virtualbox. I use openbsd vm just for browsing by firefox. I use freebsd host for other things like watching movie, listen music, pdf, documents and so on. Sometimes I run a linux or windows virtual machine to do other things. It's something like qubes os but with a bsd kernel.

I've never used Arch but, from what I gather, it isn't representative of majority of Linux distributions - most are still the kernel + packages, albeit the latter being essential, important, etc..

Ah, wasn't aware of this, could be related to to the DST Root CA X3 problem with letsencrypt and in the end with this strange xmpp-test-results ...

https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/

But when reading this, i'am asking myself: OpenBSD-7.0 + syspatch + acme-client (Base) + letsencrypt = DST Root CA X3 (issued in 2000 and EOL in 09/2021). Why not “ISRG Root X1” or “ISRG Root X2” as Root CA’s and “Let’s Encrypt R3” as an intermediate certificate.

I own a 'old' device, or was this EOL-date not clear? Hm, in the end, my nrain is small and i don't understand enough, so i will keep my mouth until i have time to read and understand again.

This here is an appealing, easy way to start tinkering with programming:

https://scratch.mit.edu/

It's primarily graphical, so need to stumble over syntax, typos, semicolons.

It should run in a modern browser on OpenBSD, e.g. Chromium, Firefox...

> zerrors_openbsd_amd64

That seems more like the guts of golang itself. If the i386 constants are out of sync with amd64/arm64 counterparts.

Also is it so gross how they have various scripts to parse the output of system headers (by getting gcc (?) to dump them) after preprocessing. This whole thing seems just as fragile as their per-OS syscall tables.

https://golang.org/src/syscall/mkerrors.sh

https://golang.org/src/syscall

This is the one I have but it looks like it's not being made anymore. It was like $130 or something when I bought it. https://www.amazon.com/ASRock-Motherboard-J3455-ITX-Quad-Core-Mini-ITX/dp/B01MPWDCLE/ref=sr_1_1

Something like this looks like it would work well, though you're paying for Windows 10 and potentially a small SSD you don't use if you intend to swap that out: https://www.amazon.com/Computer-AWOW-AK34-Ethernet-Bluetooth/dp/B082KR9KX5/ref=sr_1_5

That was like the top result I'm sure there's better choice out there. Long story short, what you picked is overkill but if $$$ is no object, it looks fun.

This is the one I have but it looks like it's not being made anymore. It was like $130 or something when I bought it. https://www.amazon.com/ASRock-Motherboard-J3455-ITX-Quad-Core-Mini-ITX/dp/B01MPWDCLE/ref=sr_1_1

Something like this looks like it would work well, though you're paying for Windows 10 and potentially a small SSD you don't use if you intend to swap that out: https://www.amazon.com/Computer-AWOW-AK34-Ethernet-Bluetooth/dp/B082KR9KX5/ref=sr_1_5

That was like the top result I'm sure there's better choice out there. Long story short, what you picked is overkill but if $$$ is no object, it looks fun.

You can follow brynet's advice and get a usb wifi adapter that is supported. For example: https://www.amazon.com/gp/product/B06Y24GDR8/ This is one that I just bought, and now my 2011 MBA is up and runnning OpenBSD. The OpenBSD firmware site had what you need. If you can gunzip and tar a file, and mount a USB drive, you have plenty of options.

I'm pretty sure most laptops use mini-pcie wifi cards.

My 7year old, $300-at-the-time Acer does. You can change it to whatever you want. Get one that's supported.

This one is supported by the iwm driver, and is only $18

https://www.amazon.com/dp/B09H5C7J1Z/ref=cm_sw_r_apan_glt_i_72DDA0XHY0205J3TKDF7?_encoding=UTF8&psc=1

cgit doesn't support push at all. You could look into git-http-backend for that. Here's the relevant part of my setup.

​

# httpd.conf

server "git.example.com" { listen on 127.0.0.1 port 8080 root "/cgi-bin/cgit.cgi" fastcgi socket "/run/slowcgi.sock" authenticate with "/conf/htpasswd"

location match ".*%.git/?" { root "/cgi-bin/git-http-backend"
fastcgi param GIT_PROJECT_ROOT "/git" fastcgi param GIT_HTTP_EXPORT_ALL "true" #fastcgi param GIT_TRACE "2" }

location "/cgit.*" { root "/cgit" no fastcgi } }

​

# cgitrc

enable-http-clone=0 clone-url=https://$HTTP_HOST$SCRIPT_NAME/$CGIT_REPO_URL.git remove-suffix=1

Make sure git and all it's linked libraries are available inside the chroot for git-http-backend to work. Write permission for the user www are needed as well of course.

OpenWRT is the same, you flash new firmware, but IIRC, you can import backup of configuration from older firmware and it should work.

There is doc about that: https://openwrt.org/docs/guide-user/installation/generic.sysupgrade

which states that some directories (those with config files) are preserved during update.

I have never used DD-WRT so I can't say anything about it.

On Arch Linux, gcr does require gtk3, but gst-plugins-base does not require gvfs, gvfs does not require gcr, and qt4 does not require gst-plugins-base.

You could use those PKGBUILD bash scripts to see which configure options you need to change to break that chain wherever you like.

https://www.archlinux.org/packages/

That seems like a fairly inexpensive thing to fund-raise for. How would one donate hardware to OpenBSD?

You can get hardware from SiFive for fairly cheap: https://www.wikipedia.org/wiki/SiFive#Products

See how you decided to delete your account minutes after posting this, I'm guessing you don't care about a reply.. but by default, VirtualBox doesn't boot in UEFI mode.. so it makes sense that you wouldn't be able to set any other modes, so no efifb(4), and there is no X DDX driver for VirtualBox.

It does autodetect, but you need to use supported hardware to begin with. You can blame the developers all you want, or you could try to do a little work to begin.

Maybe give this a shot: https://www.virtualbox.org/manual/ch03.html#efi

I have this one and it works great with OpenBSD and other OS too, currently $12 USD on Amazon.

https://www.amazon.com/Plugable-Wireless-802-11n-Network-RTL8188EUS/dp/B00H28H8DU

> missing separator error

This is but the first of many hurdles in building OpenBSD on anything other than a recent version of OpenBSD. Your Linux system has GNU make. The BSDs use BSD make. BSD make (usually called bmake on Linux) and GNU make and System V make are are mutually incompatible when you get past very basic rules. They all evolved in parallel to solve the same problems in different ways.

You're also going to his problems with assumptions about the exact compiler, assembler, and linker used. For building a standalone executable like the loader and kernel, that's mostly where the problems end, but if you want to build the userland, you're going to need the OpenBSD C library to link against; another operating system's C library isn't going to know how to map system call stubs through the syscall gate. Also, depending on the architecture you're targeting, you native OS and OpenBSD might not even use the same calling convention.

You can, absolutely, tackle each of those problems in turn, starting by installing BSD make and building a cross-compiler toolchain using the LLVM 11. Every step will be unsupported and undocumented, but you can launch a garden shed into low earth orbit if you have enough thrust.

But spinning up an OpenBSD virtual machine to host your build environment will be much less hassle, which is why the FAQ tells you not just to build using OpenBSD, but to use a version <em>really</em> close to what you're trying to build.

The legacy nv(4) driver is basically unmaintained and is still a UMS (userland modsetting) driver, what this means is if the X server crashes the hardware can be left in broken state and the console framebuffer might not be restored properly.

> I can't even use Ctrl-Alt-F* to get a VT.

Switching consoles isn't supported on macppc.

I rent the whole thing not even my hw. so can't tell you about co-location. As said, new ones are expensive but used ones are still available. I mostly use Strato, because they have good remote console support. Which is very good for getting OpenBSD installed with minimal fuzzing.

https://www.strato.de/server/limited-hardware/ https://www.hetzner.com/sb

True, but the OpenBSD ksh was initially based on the Public Domain ksh. The following description from 1999 states that the "PD-ksh' is a clone of the AT&T Korn shell. At the moment, it has most of the ksh88 features, not much of the ksh93 features, and a number of its own features. It is quite portable and should compile easily on any *nix box. The vi editing mode is better (as per the developer) than that of ksh88 or ksh93." (https://directory.fsf.org/wiki/Pdksh) With ksh93, the ksh – as well as its scripting language – was heavily altered. Hence the oksh and ksh93 are akin, but actually not the same shell.

As a regular git user, i very much agree with this comment:

>The semantic operations make sense. The UI/UX exposed to do those operations does not. The confusion around git’s interface isn’t because it’s a graph editing tool. It’s because it uses inconsistent naming, inconsistent flags, and almost zero safety net.

(Oblig link to git man page generator)

You may need to pkg_add git gmake and possibly other packages. Also, I assume you have doas configured.

swinny$ git clone https://github.com/richardgv/skippy-xd

swinny$ cd skippy-xd

swinny$ nano Makefile

change the line that says

"PACKAGES = x11 xft xrender xcomposite xdamage xfixes"

to

"PACKAGES = x11 xft xrender xcomposite xdamage xfixes libjpeg"

CTL + x to exit nano, and y to save changes.

swinny$ gmake

swinny$ doas gmake install

And then clean up

swinny$ cd ..

swinny$ rm -Rf skippy-xd

> 149GB aren't much for a HDD and a strange size for a SSD. How old is the laptop and did you select UEFI, BIOS or both bootloaders? Some laptops (e.g. Sandy Bridge Thinkpads) have broken UEFI legacy boot support and won't boot from GPT formatted disks in legacy without workarounds.

It is quite an old computer: ASUS K53U with an AMD E-450. Regarding UEFI, when I enter the firmware options to boot from a USB, in the USB option it says UEFI: Sandisk. That would mean that the laptop is capable of booting from UEFI, right? I'll try installing FreeBSD again but I'll choose MBR this time.

Here is the dmesg output (booting from a USB).

you'd probably want Cygwin running on your Windows machine ... and compile bonnie++ (exists in OpenBSD ports), or get fio source. of the two bonnie++ is more well know.

everything will be IO bound so Cygwin won't really matter (???) and affect the actual measurement of the underlying filesystem (NTFS vs FFS) and disk.

I think a package/port which sets up a DE and a few necessary applications would be nice.

CrunchBang Linux and BunsenLabs Linux have very nice OpenBox setups.

Slax has a nice FluxBox implementation.

BunsenLabs Linux: https://www.bunsenlabs.org/ Slax: https://www.slax.org/

You'll need to use rEFInd to get a menu. You'll even get a pretty OpenBSD logo.

Though EFI support is still not 100%, so the bootloader may not be able to find your disk properly, or the kernel might not boot.