LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Other *NIX Forums > *BSD
User Name
Password
*BSD This forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.

Notices


Reply
  Search this Thread
Old 04-21-2022, 12:30 PM   #1
jggimi
Member
 
Registered: Jan 2016
Distribution: None. Just OpenBSD.
Posts: 270

Rep: Reputation: 140Reputation: 140
OpenBSD 7.1 has been released


Today, the OpenBSD Project released version 7.1!There will be no more package updates for release 7.0, and no more patches for 6.9. Users on 6.9 should upgrade. Upgrade Guide for 7.0 to 7.1: http://www.openbsd.org/faq/upgrade71.html. Upgrade Guide for 6.9 to 7.0: http://www.openbsd.org/faq/upgrade70.html.

Last edited by jggimi; 04-22-2022 at 04:45 PM. Reason: typo
 
Old 04-22-2022, 03:10 AM   #2
fatmac
Senior Member
 
Registered: Sep 2011
Location: Upper Hale, Surrey/Hants Border, UK
Distribution: Mainly Devuan/Devuan based - with - OpenBSD - NetBSD - Fatdog64 - TinyCorePlus
Posts: 4,628

Rep: Reputation: Disabled
Thanks for the 'heads up'.
 
Old 04-22-2022, 12:19 PM   #3
YesItsMe
Member
 
Registered: Oct 2014
Distribution: Slackware
Posts: 812

Rep: Reputation: 284Reputation: 284Reputation: 284
Syspatch 001 is there: Many wireless network drivers could not scan access points correctly.
 
Old 04-23-2022, 11:16 AM   #4
TheTKS
Member
 
Registered: Sep 2017
Location: The deep south... of Canada
Distribution: Slackware, Xubuntu, OpenBSD, elementary, Raspberry Pi OS, Puppy, TinyCore
Posts: 329

Rep: Reputation: 225Reputation: 225Reputation: 225
Ran a trouble-free sysupgrade from 7.0 to 7.1 arm64 on Raspberry Pi 4 in under 20 minutes, including taking extra time to read a few things in more detail.

Packages took longer: I have xfce4, xfce4-extras and a few other packages installed.

xfce4 screen freezing still (not an OpenBSD problem, an Xfce one) needs action to reimplement a workaround after an OS upgrade followed by pkg_add -u. The way I get around it is:
Code:
# chmod -x /usr/local/bin/xfce4-screensaver*
# chmod -x /usr/local/bin/upower
This allows me to manually lock from the Xfce panel, password protected, but no screensaver runs, I just have a blank screen. I haven't found a real fix yet, just this work around, but it works for me.

Next is to get OpenBSD installed on a desktop or laptop again, after the desktop I had it installed on died.

TKS

Last edited by TheTKS; 04-23-2022 at 11:24 AM.
 
Old 04-23-2022, 11:20 AM   #5
TheTKS
Member
 
Registered: Sep 2017
Location: The deep south... of Canada
Distribution: Slackware, Xubuntu, OpenBSD, elementary, Raspberry Pi OS, Puppy, TinyCore
Posts: 329

Rep: Reputation: 225Reputation: 225Reputation: 225
Quote:
Originally Posted by YesItsMe View Post
Syspatch 001 is there: Many wireless network drivers could not scan access points correctly.
This syspatch was reverted

https://www.openbsd.org/errata71.html
 
Old 04-23-2022, 11:30 AM   #6
YesItsMe
Member
 
Registered: Oct 2014
Distribution: Slackware
Posts: 812

Rep: Reputation: 284Reputation: 284Reputation: 284
Hmm. I sense a decline of quality.

Anyway, I noticed that OpenBSD 7.1 comes with login.conf changes that can affect certain user accounts. Just in case: make sure that all user accounts (including relayd, by the way) have login classes listed in login.conf, or else prepare for strange new observations (in my case, relayd suddenly crashing and my ZNC user not being able to log in).
 
Old 04-23-2022, 12:18 PM   #7
jggimi
Member
 
Registered: Jan 2016
Distribution: None. Just OpenBSD.
Posts: 270

Original Poster
Rep: Reputation: 140Reputation: 140
Quote:
Originally Posted by YesItsMe View Post
Hmm. I sense a decline of quality.

Anyway, I noticed that OpenBSD 7.1 comes with login.conf changes that can affect certain user accounts. Just in case: make sure that all user accounts (including relayd, by the way) have login classes listed in login.conf, or else prepare for strange new observations (in my case, relayd suddenly crashing and my ZNC user not being able to log in).
The login.conf(5) files provided by the Project vary by architecture, under `/usr/src/etc/etc.<arch>/login.conf`. If you believe you have discovered a login.conf(5) bug, please be sure to include your architecture in your problem report.

Additionally, it's my experience that any Project updates to login.conf(5) are merged with local changes through sysmerge(8), allowing the admin to cherry pick which revisions to accept or reject. Were you presented with these choices by sysmerge(8)?
 
2 members found this post helpful.
Old 04-23-2022, 08:21 PM   #8
YesItsMe
Member
 
Registered: Oct 2014
Distribution: Slackware
Posts: 812

Rep: Reputation: 284Reputation: 284Reputation: 284
I was. I might have made a mistake here. I do not assume that it is a bug, more likely it was a misconfiguration in earlier versions.
 
Old 04-23-2022, 09:05 PM   #9
jggimi
Member
 
Registered: Jan 2016
Distribution: None. Just OpenBSD.
Posts: 270

Original Poster
Rep: Reputation: 140Reputation: 140
I have reviewed the amd64 login.conf(5) changes between 7.0-release and 7.1-release, as it's the most commonly used architecture today. The effective changes were:
  • daemon: datasize from infinity to 4GB
  • daemon: maxproc-cur from 384 to 512
  • bgpd: datasize from infinity (courtesy of tc:daemon) to 16 GB
  • unbound: provisioned with tc:daemon defaults
  • vmd: added as a class, with 16GB datasize and tc:daemon defaults
Here's a diff to compare the two commits: https://cvsweb.openbsd.org/cgi-bin/c...1=1.23&r2=1.20

Looking at the diff, I guess that you might have had a private class added after unbound which interfered with the addition of the vmd class. It is just a guess. IIRC, relayd by default will use the daemon class.

Last edited by jggimi; 04-23-2022 at 09:11 PM. Reason: Added guess, corrected typo.
 
2 members found this post helpful.
Old 04-24-2022, 09:28 AM   #10
YesItsMe
Member
 
Registered: Oct 2014
Distribution: Slackware
Posts: 812

Rep: Reputation: 284Reputation: 284Reputation: 284
Currently, it runs with tc=default on the system that behaved weirdly. It may well be that you are right, thank you.
 
Old 04-26-2022, 07:17 AM   #11
hitest
Guru
 
Registered: Mar 2004
Location: Northern Canada
Distribution: Slackware, OpenBSD, FreeBSD
Posts: 7,070

Rep: Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437
On holidays. Looking forward to upgrading in a day or two. Thanks for the heads up, jggimi.
 
Old 04-28-2022, 03:55 PM   #12
hitest
Guru
 
Registered: Mar 2004
Location: Northern Canada
Distribution: Slackware, OpenBSD, FreeBSD
Posts: 7,070

Rep: Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437
Very nice! OpenBSD 7.1 up and running.
 
Old 05-02-2022, 08:10 AM   #13
jggimi
Member
 
Registered: Jan 2016
Distribution: None. Just OpenBSD.
Posts: 270

Original Poster
Rep: Reputation: 140Reputation: 140
The syspatch has just been corrected.

http://www.openbsd.org/errata71.html
 
3 members found this post helpful.
Old 05-02-2022, 02:29 PM   #14
hitest
Guru
 
Registered: Mar 2004
Location: Northern Canada
Distribution: Slackware, OpenBSD, FreeBSD
Posts: 7,070

Rep: Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437Reputation: 3437
Thumbs up

Quote:
Originally Posted by jggimi View Post
The syspatch has just been corrected.

http://www.openbsd.org/errata71.html
Thanks, patch applied.

Code:
bsd$ sudo syspatch
Password: 
Get/Verify syspatch71-001_wifi.tgz 100% |***************|  4423 KB    00:02    
Installing patch 001_wifi
syspatch: updated itself, run it again to install missing patches
Relinking to create unique kernel... done; reboot to load the new kernel
 
Old 05-06-2022, 06:17 AM   #15
YesItsMe
Member
 
Registered: Oct 2014
Distribution: Slackware
Posts: 812

Rep: Reputation: 284Reputation: 284Reputation: 284
Syspatch 002, all architectures: "When using IPsec, the kernel could crash."
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
My LG Stylo 4 Has Been Hijacked by Remote Administrator and OS as Well as Kernel Have Been Modified LongDuckDong_69 Linux - Newbie 3 11-17-2019 03:41 PM
LXer: OBS Studio 20.0 Has Been Released Released | It Brings a Modular User Interface & Stinger Transitions LXer Syndicated Linux News 0 08-11-2017 09:00 AM
My web server has been hacked. SU password has been disabled rcrosoer Linux - Security 11 06-27-2008 02:18 PM
OpenBSD - Where can i get OpenBSD 3.7 ISO CD -- Please help me b:z Linux - Software 5 04-08-2005 07:09 AM
OpenBSD - Where can i get OpenBSD 3.7 ISO CD -- Please help me b:z Linux - Software 1 04-07-2005 08:46 AM

LinuxQuestions.org > Forums > Other *NIX Forums > *BSD

All times are GMT -5. The time now is 02:04 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration