OpenBSD 7.9 Released as Project's 60th Version, Upgrade Guide Available

·3 views

The OpenBSD project released version 7.9 on May 19, 2026, marking the operating system's 60th release. The upgrade from 7.8 to 7.9 can be performed using the built-in sysupgrade tool, which automates downloading, verifying, and installing the new system sets. Before upgrading, users should ensure the /usr partition has at least 1.1GB of free space and review configuration and package changes, including a major PostgreSQL update to version 18.1. An optional response file, /auto_upgrade.conf, allows users to customize which installation sets are included or excluded during the process. Once sysupgrade is initiated it cannot be stopped, so the system reboots automatically to complete the upgrade and run sysmerge for configuration file handling.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Why Clarifying Your Question Before Using AI Leads to Better Results

A developer reflects on how years of using generative AI have gradually shifted more cognitive work away from the user and toward the tool. Research suggests that people who rely on AI to solve problems tend to retain less information than those who work through problems independently. The author observes that AI works best as a finishing tool — catching errors, refining phrasing, and filling gaps — rather than as a starting point for ideas that require personal opinion or taste. A recurring frustration with AI-generated output, the author notes, often stems not from the tool's limitations but from poorly formed questions on the user's end. The key insight is that articulating a clear, specific question requires doing roughly half the thinking yourself, which in turn makes AI assistance far more effective.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Dev shares hard lessons from building a real-world enterprise app ecosystem

A developer behind 24hours.lk and its companion 24 Eco System mobile suite has shared key engineering lessons learned from building production-grade enterprise applications. The experience revealed that real-world apps, unlike controlled development environments, must handle concurrent requests, partial failures, version mismatches, and large-scale data — often simultaneously. Because both web and mobile clients shared the same backend, even minor API changes carried ecosystem-wide consequences, demanding careful attention to versioning, validation, and backward compatibility. Database design proved equally complex, with seemingly efficient queries becoming costly bottlenecks at scale, requiring deliberate indexing, pagination, and query optimization strategies. The core takeaway was a shift in mindset: enterprise development is less about building features and more about deciding where each feature belongs within a resilient, well-structured architecture.

0 comments Read more at DEV Community

ProgrammingHacker News ·

Critical RCE Vulnerability Actively Exploited Across All Chromium Versions

A critical remote code execution (RCE) vulnerability has been identified in all versions of Chromium, the open-source browser engine powering Google Chrome and other browsers. The flaw, tracked as CVE-2026-85046, allows attackers to escape the browser sandbox and execute arbitrary code on affected systems. The vulnerability is listed in the National Vulnerability Database (NVD) maintained by NIST. Because it is being actively exploited in the wild, users of Chromium-based browsers are considered at immediate risk. Security researchers and the broader community have flagged the issue as high priority, urging prompt patching once a fix becomes available.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

Google to Limit Site Reputation Penalty Impact in EEA From August 2026

Google has announced that from August 30, 2026, manual actions under its Site Reputation Policy will no longer affect search rankings for users within the European Economic Area (EEA), though they will continue to apply outside the region. The change is linked to Google's ongoing discussions with the European Commission and compliance considerations under the Digital Markets Act. The Site Reputation Policy itself remains globally active; only the regional enforcement impact is being altered for EEA search results. Google also indicated that affected portions of a site may be separated in its systems to rank independently over time within the EEA, though the technical details of this process have not been fully disclosed. Site owners will still receive Search Console notifications and can pursue reconsideration requests, meaning a manual action remains a significant signal regardless of the regional carve-out.

0 comments Read more at DEV Community