updating the kernel to CURRENT

2006-02-17 Thread João Salvatti
Hi all,

When updating the kernel to CURRENT (in the case, 3.9), do I have to update
ports and already installed packages?

Thanks.

--
Joco Salvatti
Undergraduating in Computer Science
Federal University of Para - UFPA
web: http://salvatti.expert.com.br
e-mail: [EMAIL PROTECTED]



Re: updating the kernel to CURRENT

2006-02-17 Thread Spruell, Darren-Perot
From: [EMAIL PROTECTED] 
 When updating the kernel to CURRENT (in the case, 3.9), do I 
 have to update
 ports and already installed packages?

Packages and ports should stay in sync with the rest of the userland. The OS
should stay in synch with the kernel since there are important dependencies
on kernel interfaces.

So I would guess if you want to run CURRENT kernel, you will be best served
running CURRENT userland as well, and subsequently ports will need to follow
CURRENT as well.

Maybe you should consider a snapshot.

(hoping I'm not misleading on this...)

DS



Re: updating the kernel to CURRENT

2006-02-17 Thread Nick Holland

Spruell, Darren-Perot wrote:
From: [EMAIL PROTECTED] 
When updating the kernel to CURRENT (in the case, 3.9), do I 
have to update

ports and already installed packages?


I think the OP is using words in non-standard ways.
The kernel is one file, /bsd.
Ports and packages are the add-on stuff.
Missing from the question is the userland -- the utilities and such that 
makes OpenBSD (or any OS) go.


OpenBSD is the combination of the userland and kernel.  I'm going to 
guess that's what the OP meant by kernel.



Packages and ports should stay in sync with the rest of the userland. The OS
should stay in synch with the kernel since there are important dependencies
on kernel interfaces.

So I would guess if you want to run CURRENT kernel, you will be best served
running CURRENT userland as well, and subsequently ports will need to follow
CURRENT as well.

Maybe you should consider a snapshot.

(hoping I'm not misleading on this...)


Technically, you are somewhat wrong, practically, you are mostly correct. :)

The kernel and userland must be kept in sync for a fully functioning 
system (though a brief new kernel, old userland usually works for the 
middle of the remote upgrade process).  Newly installed packages must 
match the rest of the OS.  Packages built from ports must be from a 
ports tree that matches the OS.


HOWEVER... as the upgrade process does not remove the old library files, 
old packages will (usually) continue to run on an UPGRADED system 
(however, don't try to install an old package on a newly-installed (not 
upgraded) system).  So, technically, you are wrong, you could keep using 
old ports on new systems.


Practically, you are right.  Try to live with that concept, you run into 
at least a couple issues:
* Dependancies: new packages may be dependent upon newer versions of 
packages you already have installed.  Might as well upgrade them on your 
schedule.
* Security: third party software seems to have a non-trivial rate of 
security issues.  You probably want to keep it up to date.  You will 
probably have more reason to worry about updating the apps than the OS 
itself.


As long as you are updating the system, just update the ports and packages.

And yes, always use a snapshot (or release, or other prepared binary). 
Compiling is for customizing (which you probably don't need to do) or 
for -stable.  Upgrading is done using binaries.


Nick.