Live data from Hacker News

OpenBSD 6.6

openbsd.org

11–20 of 92 posts

Re: OpenBSD 6.6

#11
post #2

Announcement email: https://marc.info/?l=openbsd-announce&m=157132045926047&w=2

o Added regular expression support for the format search, match andsubstitute modifiers in tmux(1). o Added a -v flag to source-file in tmux(1) to show the commands and line numbers. o Added simple menus usable with mouse or keyboard in tmux(1). o Introduced the command "display-menu" to show a menu bound to the mouse on status line by default, and added menus in tree, client and buffer modes. o Changed the behavior…

Are they new features, or new to OpenBSD?

Re: OpenBSD 6.6

#12
post #7

> Fixed support for amd64 machines with greater than 1023GB physical memory. Don't I wish. What would be the memory test time for something like that?

By linear extrapolation, about 7 minutes per terabyte on an EPYC 7402, which can handle up to 4 TB.

Attempts to justify new init software by "it boots much faster" fall flat.

Re: OpenBSD 6.6

#14

Earlier quoted context omitted.

o Added regular expression support for the format search, match andsubstitute modifiers in tmux(1). o Added a -v flag to source-file in tmux(1) to show the commands and line numbers. o Added simple menus usable with mouse or keyboard in tmux(1). o Introduced the command "display-menu" to show a menu bound to the mouse on status line by default, and added menus in tree, client and buffer modes. o Changed the behavior…

Are they new features, or new to OpenBSD?

I suspect new, since tmux (like OpenSSH) is developed as part of OpenBSD.

Re: OpenBSD 6.6

#15
post #3

I read about the "sysupgrade" tool and concluded that the upgrade to 6.7 in another 6 months will be awfully seamless... But I see from this that they backported the tool as a syspatch for 6.5! So from 6.5 we will be able to do syspatch && sysupgrade to get to 6.6. Sounds nice.

Tried on one of my machines. Seems to work fine. You still do the delete file step manually but that's minor. This is going to save a lot of effort on certain machines.

How does it handle sysmerge? Do you need to do that after it finishes? Or does it do the merges before reboot?

I will play around with it in a few hours.

Re: OpenBSD 6.6

#17
post #12
post #7

> Fixed support for amd64 machines with greater than 1023GB physical memory. Don't I wish. What would be the memory test time for something like that?

By linear extrapolation, about 7 minutes per terabyte on an EPYC 7402, which can handle up to 4 TB. Attempts to justify new init software by "it boots much faster" fall flat.

OSEs aren’t limited to running on physical hardware, fast startup for VMs is still beneficial.

Re: OpenBSD 6.6

#18

> Disabled gcc in base on armv7 and i386. Is gcc disabled in base on amd64? Are the OpenBSD distributions for amd64 compiled with gcc or clang?

gcc is still included in base on amd64 for now, but the default system compiler on amd64 (and i386) has been clang since OpenBSD 6.2. If you use the /usr/bin/{cc,c++} symlinks, you get clang. Nothing uses the base-gcc now, but it being kept as a convenience for porters to test with as some architectures have yet to switch to clang.

The change mentioned is only that gcc4 (base-gcc) will no longer been installed alongside clang on i386 and armv7. If you need gcc, you can install ports gcc 8.3.0 from packages.

Re: OpenBSD 6.6

#19
post #3

I read about the "sysupgrade" tool and concluded that the upgrade to 6.7 in another 6 months will be awfully seamless... But I see from this that they backported the tool as a syspatch for 6.5! So from 6.5 we will be able to do syspatch && sysupgrade to get to 6.6. Sounds nice.

You can also do sysupgrade -s to follow current snapshots, and then you get a rolling release OpenBSD without build world.
Post reply on HN