Mailing List Archive

On Tue, 2023-04-11 at 18:21 -0600, thelma@sys-concept.com wrote:
> What is the correct way of updating remote system?
> I'll need to update the kernel + world
>
> 1.) Update all packages in world first, reboot and update kernel
> 2.) Update kernel first, reboot and update world
>
> It seems to me logical choice is 2.) as I'll need new kernel to
> update to new VirtualBox.
> Right now remote system is running linux-5.10.103-gentoo and I think
> new VirtualBox need kerenl-5.13 or higher.
>



--
Julien

On Tue, 2023-04-11 at 20:24 -0400, julien@jroy.ca wrote:
> On Tue, 2023-04-11 at 18:21 -0600, thelma@sys-concept.com wrote:
> > What is the correct way of updating remote system?
> > I'll need to update the kernel + world
> >
> > 1.) Update all packages in world first, reboot and update kernel
> > 2.) Update kernel first, reboot and update world
> >
> > It seems to me logical choice is 2.) as I'll need new kernel to
> > update to new VirtualBox.
> > Right now remote system is running linux-5.10.103-gentoo and I
> > think
> > new VirtualBox need kerenl-5.13 or higher.
> >
>
>
>
> --

It seems my message got sent empty...
Let's try again:

I usually update world first, then the kernel, and finally reboot.


--
Julien

Le mer. 12 avr. 2023, 02:26, julien@jroy.ca <julien@jroy.ca> a écrit :
>
> On Tue, 2023-04-11 at 20:24 -0400, julien@jroy.ca wrote:
> > On Tue, 2023-04-11 at 18:21 -0600, thelma@sys-concept.com wrote:
> > > What is the correct way of updating remote system?
> > > I'll need to update the kernel + world
> > >
> > > 1.) Update all packages in world first, reboot and update kernel
> > > 2.) Update kernel first, reboot and update world
> > >
> > > It seems to me logical choice is 2.) as I'll need new kernel to
> > > update to new VirtualBox.
> > > Right now remote system is running linux-5.10.103-gentoo and I
> > > think
> > > new VirtualBox need kerenl-5.13 or higher.
> > >
> >
> >
> >
> > --
>
> It seems my message got sent empty...
> Let's try again:
>
> I usually update world first, then the kernel, and finally reboot.
>
>
> --
> Julien

Hi

I don't know if it's correct, I'd proceed this way:
1. Update world first, because some updated packages may be involved
in kernel building
2. Reboot with the current working kernel and check everything else works
3. Update the kernel and reboot (keeping the old kernel for a while)

That's two reboots, but for a remote system I'd keep on the safe side.

Have a nice compile time !

Mickaël

On Wednesday, 12 April 2023 08:16:05 BST Micka?l Bucas wrote:

> I don't know if it's correct, I'd proceed this way:
> 1. Update world first, because some updated packages may be involved
> in kernel building
> 2. Reboot with the current working kernel and check everything else works
> 3. Update the kernel and reboot (keeping the old kernel for a while)

Perhaps you missed the point that some of the world update requires the
updated kernel.

I'd do the same as Thelma.

--
Regards,
Peter.

On Wednesday, 12 April 2023 10:27:29 BST Peter Humphrey wrote:
> On Wednesday, 12 April 2023 08:16:05 BST Mickaël Bucas wrote:
> > I don't know if it's correct, I'd proceed this way:
> > 1. Update world first, because some updated packages may be involved
> > in kernel building
> > 2. Reboot with the current working kernel and check everything else works
> > 3. Update the kernel and reboot (keeping the old kernel for a while)
>
> Perhaps you missed the point that some of the world update requires the
> updated kernel.
>
> I'd do the same as Thelma.

Typically, Portage will take care of its own and arrive at a suitable order of
updates without breaking things. If there is some Blocking situation other
steps would be necessary, but I suspect in this instance just one package will
be held back (VBox), until prerequisites have been updated first.

Since @system will contain the toolchain, it will be enough to update this set
before building the kernel, then @world to finish things off.

Le mer. 12 avr. 2023 à 11:27, Peter Humphrey <peter@prh.myzen.co.uk> a écrit :
>
> On Wednesday, 12 April 2023 08:16:05 BST Mickaël Bucas wrote:
>
> > I don't know if it's correct, I'd proceed this way:
> > 1. Update world first, because some updated packages may be involved
> > in kernel building
> > 2. Reboot with the current working kernel and check everything else works
> > 3. Update the kernel and reboot (keeping the old kernel for a while)
>
> Perhaps you missed the point that some of the world update requires the
> updated kernel.
Thanks for pointing this out, I missed what Thelma stated clearly.

> I'd do the same as Thelma.
With VBox needs, I agree
There may be more elaborate moves like Michael explains, though I'm
not able to give more advice.

>
> --
> Regards,
> Peter.

Best regards
Mickaël