1. Forum
  2. Usenet
  3. LINUX.GENTOO.USER

  • [gentoo-user] updating remote system

    From thelma@sys-concept.com@21:1/5 to All on Wed Apr 12 02:30:01 2023
    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.

    --
    Thelma

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From julien@jroy.ca@21:1/5 to julien@jroy.ca on Wed Apr 12 02:30:01 2023
    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

    -----BEGIN PGP SIGNATURE-----

    iQGTBAABCgB9FiEEUri1ZrRDZASH+Q0NvvIpdEiEiEIFAmQ1+qBfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDUy QjhCNTY2QjQ0MzY0MDQ4N0Y5MEQwREJFRjIyOTc0NDg4NDg4NDIACgkQvvIpdEiE iEKj4Qf/UQ8PmSMeUL9gsADhlgrGBOuW+q4uKv20tSfA85wAmPuHb0pYINn9G1Wf X7QCtV/RSpPAGV4FxtBAIabXnheisK8lUyjflKQfQEaiXLTjTmlSKGc5fbWBNU7N pStglgwdDDcfyRFJzTx/7yqwgehb+2FATuFzQV+lBJNSOnthzKoKHqzmu1LxV9qp RoyY1uXid/LuLUNq27BJmWUKIXaT+q1Kee575YRGVggF2lm7WbncJFO4+3H6dDLz biBg7cKEblqOvsbKLwO2rbw3JoWnU2uY1rGAYaVmdWVzTtZ37q+MGOha//rMvMDX V6gVrXB+bXcNdJWe7UtmKMahl9G06Q==
    =lJDa
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From julien@jroy.ca@21:1/5 to thelma@sys-concept.com on Wed Apr 12 02:30:01 2023
    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

    -----BEGIN PGP SIGNATURE-----

    iQGTBAABCgB9FiEEUri1ZrRDZASH+Q0NvvIpdEiEiEIFAmQ1+jBfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDUy QjhCNTY2QjQ0MzY0MDQ4N0Y5MEQwREJFRjIyOTc0NDg4NDg4NDIACgkQvvIpdEiE iELdLwgAhKuUExhQwNlZDHzWacO2ogMAUUnUDT41cGbDq++ifHOLSUCI9YcHH5Tc VztFKZwFqr6mGeEsYqqJ2ZD7Nj7Gq+oOGAFGJQnXquWg1ohO3NwTKgDtZ40/jJj7 56KD6Wi7BMVB2zi9a3K9dxH/ttidZT6UsqmkKpLzl2GrfA9jhPQIHnoYWy5oV5PL q2St+AXPKw4gbT5NBkKZgNnWJAinV6tnziHHP2T80YXo2K/YoT9DGjHwbT8gxB/0 p9EQFZ36Zjo977OmOmQ5JkKSgC3W2VVuW5nTOmyzw2O3d59i6ogzDj/3NRbx7TVC 2BSzNpXGmQgwpILsD0Ry1No+eidw4Q==
    =Tv/E
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Micka=C3=ABl_Bucas?=@21:1/5 to All on Wed Apr 12 09:20:01 2023
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter Humphrey@21:1/5 to All on Wed Apr 12 11:30:01 2023
    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.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael@21:1/5 to All on Wed Apr 12 13:40:01 2023
    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.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Micka=C3=ABl_Bucas?=@21:1/5 to All on Wed Apr 12 16:20:02 2023
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)