|
OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|
|||
EDIT: I see 6.2 in your sig, are you following snapshots? Then read my upgrading section.
For release and stable: Understand that OpenBSD does not do rolling releases like Linux distros. The focus is on a stable release plus security patches. Also OpenBSD does not package the abse OS in the same way as 3rd part ports applications. Unlike Linux where everything is available as package. So you have two processes to learn. Security updates to your running system, and updating to a new release. And within that, you have the base system and ports which are maintained separately. To start off simply, apply security updates to the base system with syspatch. 'man syspatch' and https://www.openbsd.org/faq/faq10.html#Patches OpenBSD does not have the resources to package security updates to ports. You can either build them yourself or use a 3rd party such as m:tier. https://stable.mtier.org/ Upgrading to a new releaes is a similar process as the installation. The easist way to download the new release's bsd.rd file to /, reboot and at the boot> prompt, type 'b bsd.rd' to boot the new installer and choose [U]pgrade. Then 'sysmerge' if needed and 'pkg_add -u'. The 6.2 release is right around the corner so we can get into those details if you need them then. Meanwhile, read the man pages for pkg_add, pkg_delete, pkg_info. |
|
||||
Quote:
The contents of /etc/doas.conf should be: permit yourusername For example my /etc/doas.conf is: permit hitest Save and exit. Then when you run doas syspatch with a properly configured /etc/installurl it will update your system.
__________________
hitest |
|
||||
I just added https://mirrors.sonic.net/pub/OpenBSD but same thing
Code:
$ doas syspatch doas (open@open.my.domain) password: $ |
|
||||
Quote:
P.S. Do you have a working internet connection on your openbsd unit?
__________________
hitest Last edited by hitest; 6th October 2017 at 01:58 AM. Reason: addition |
|
|||
Quote:
If you want to track snapshots, it's a different process as I stated in my first post. |
|
||||
Quote:
Is it same with OpenBSD ? |
|
||||
Welcome back.
No, OpenBSD's development and release process is not the same as Linux. The process is outlined in the OpenBSD FAQ, here. The OpenBSD FAQ is a key resource for new users. Spending time with it will help you understand more about this OS. |
|
||||
Quote:
Quote:
|
|
||||
No. OpenBSD -current is a constantly moving target, as *ALL* development occurs on -current, including the preparation for -release, which, for simplicity, can be considered a very carefully prepared snapshot, that is published separately from -current, and once published never changes.
As it happens, 6.2-release has been "tagged" in CVS just this week. So, any particular snapshot of -current you might be running right now is either older than -release, or newer than -release. Not -release, as it is unpublished and will be published separately. And as you update from snapshot to snapshot, your system will be newer and newer than 6.2-release. |
|
||||
Quote:
So if I use 6.2 and do snapshot to snapshot is security an issue ? The main reason I am using OpenBSD is security. |
|
||||
I have no answer, because the word "security" here is undefined, and even if you try to define it you will likely have multiple definitions.
So instead of answering an unanswerable question, I'll try to provide you with some context. --- As oft repeated, -current is the development branch. It is where new features are added, new functionality tested, and therefore it is where risks are taken. And as any software developer will tell you, any development effort can introduce flaws or bugs. And as any OpenBSD developer will tell you, a design flaw or a bug may have unintended consequences. -current is where development and testing of the OS and of ports occur. But there are additional users who run -current, and some may do so because they want access to the latest/greatest versions of ports or packages. (But as noted above, development introduces flaws and bugs. So a higher version number isn't always better.) The project will publish a -release twice per year. It is never changed after publication. A -release is maintained and supported for 1 year, through the publication of errata patches, or through the syspatch(8) binary patch management subsystem for i386 and amd64, and additionally through the -stable branch of CVS. --- I run both -current and patched -release systems. I use -current on a workstation, as I am a port maintainer and occasional port tester, and -current is a requirement for this. I use patched -release on all of my production servers.[1] I do so because it eliminates introducing any new features which might disrupt stability, and it is also a much lower workload to maintain than a -current system, which requires frequent updates in order to stay relatively up-to-date with the constantly churning -current developments. [1] Prior to syspatch, I maintained -stable branches on all my servers as it was operationally simpler than applying individual errata patches across them. The -stable branch will occasionally have patches committed that are not published as errata, and in the years I ran -stable I did once have the need for a patch from that category of committed patches. Last edited by jggimi; 6th October 2017 at 03:58 AM. Reason: clarity |
|
|||
If only openBSD had some sort of documentation for all this.
__________________
Want to bash FreeBSD and promote Linux? Go to https://forums.freebsd.org! It's allowed. Even encouraged by the mods! |
|
||||
Quote:
Quote:
|
|
||||
Quote:
I dont want to upgrade instead I want to do a fresh install when 6.2 reaches its EOL. Thanks a lot for replying. Last edited by bsd007; 6th October 2017 at 02:12 PM. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Most software already has a “golden key” backdoor: the system update | J65nko | News | 0 | 27th February 2016 10:31 PM |
Installed OpenBSD 5.7.Need update help | Itproman | OpenBSD Installation and Upgrading | 18 | 19th August 2015 02:57 PM |
Ran make update and the system decided to install Gnome? | sparky | NetBSD Package System (pkgsrc) | 6 | 22nd April 2013 02:53 PM |
Clonezilla Live clone system update | J65nko | News | 0 | 28th September 2011 05:53 PM |
how update openbsd 4.8 | craze | OpenBSD Installation and Upgrading | 6 | 6th March 2011 03:20 PM |