[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Différences

Ci-dessous, les différences entre deux révisions de la page.

Lien vers cette vue comparative

fr:howtos:slackware-admin:systemupgrade [2012/09/26 14:58 (UTC)] – créée desideriusfr:howtos:slackware-admin:systemupgrade [2014/07/10 19:58 (UTC)] (Version actuelle) – [System Upgrade using SlackPkg] gegechris99
Ligne 42: Ligne 42:
   * When slackpkg has updated its internal database we can let it update the computer to the new Slackware release: <code>   * When slackpkg has updated its internal database we can let it update the computer to the new Slackware release: <code>
 # slackpkg install-new # slackpkg install-new
-sl/code>+slackpkg upgrade-all 
 +# slackpkg clean-system 
 +</code>
     * The first of those three commands (''slackpkg install-new'') will install every package which is marked in the Slackware ChangeLog.txt file with the string "''Added.''" This command will **not** install any other packages which are not yet installed. \\ For instance if you did not have KDE installed before, the "''slackpkg install-new''" command will not add KDE packages to your computer all of a sudden.     * The first of those three commands (''slackpkg install-new'') will install every package which is marked in the Slackware ChangeLog.txt file with the string "''Added.''" This command will **not** install any other packages which are not yet installed. \\ For instance if you did not have KDE installed before, the "''slackpkg install-new''" command will not add KDE packages to your computer all of a sudden.
     * The second command (''slackpkg upgrade-all'') will compare every official Slackware package which you currently have installed, with the package list on your Slackware mirror. If a different version is available, that version will be (downloaded and) upgraded. ((Slackware's package manager does not work with the concept of "lower version" and "higher version". The package tools only look at "//different version//" and thus downgrading packages (reverting to an earlier version) is just as easy as upgrading to a newer version!))     * The second command (''slackpkg upgrade-all'') will compare every official Slackware package which you currently have installed, with the package list on your Slackware mirror. If a different version is available, that version will be (downloaded and) upgraded. ((Slackware's package manager does not work with the concept of "lower version" and "higher version". The package tools only look at "//different version//" and thus downgrading packages (reverting to an earlier version) is just as easy as upgrading to a newer version!))
-    * The third commmand (''slackpkg clean-system'') will shoision 1.45+    * The third commmand (''slackpkg clean-system'') will show you an overview of all packages that you currently have installed and are not part of the Slackware Linux release you are upgrading to. 
 + 
 +  * You should probably decide at this moment to use a generic kernel, especially if you are using LVM or RAID, or installed Slackware to a LUKS-encrypted disk. This is also being recommended in the Slackware README on the DVD/CD. On the other hand - if your system setup is straight-forward and your hardware is fairly new, you could decide to stick with a "huge" kernel. \\ //Remember that you **cannot** use an initial ramdisk in combination with a "huge" kernel, but you **have** to create a new initial ramdisk if you are going to use a generic kernel!// \\ If you are uncertain at this point how that must be accomplished, then you should make sure that you are booting a "huge" kernel which won't require an initial ramdisk. \\ However, the "''mkinitrd_command_generator.sh''" script can help you here. Run this script with the //new// kernel version as a parameter and it will show you an example "''mkinitrd''" command which will work for your particular hardware setup and system configuration: <code> 
 +# /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 3.2.29 
 +</code> will give this as output (the kernel version 3.2.29 is that of Slackware 14)<code> 
 +
 +# mkinitrd_command_generator.sh revision 1.45
 # #
 # This script will now make a recommendation about the command to use # This script will now make a recommendation about the command to use
Ligne 54: Ligne 62:
  
 mkinitrd -c -k 3.2.29 -f ext4 -r /dev/sdb2 -m usb-storage:pcmcia_core:pcmcia:mmc_core:ssb:modprobe:usbhid:ehci-hcd:ohci-hcd:mbcache:jbd2:ext4 -u -o /boot/initrd.gz mkinitrd -c -k 3.2.29 -f ext4 -r /dev/sdb2 -m usb-storage:pcmcia_core:pcmcia:mmc_core:ssb:modprobe:usbhid:ehci-hcd:ohci-hcd:mbcache:jbd2:ext4 -u -o /boot/initrd.gz
-</code> You can copy and paste this command line in your console, and let it create an initial ramdisk for you.\\+</code>  You can copy and paste this command line in your console, and let it create an initial ramdisk for you.\\
 <note warning>If you were already running a generic kernel and therefore already have an initrd, we strongly advise you to create a **new** initrd with a **new** unique name! For instance, you can copy the above example and modify the name of the initrd file as follows: <code>mkinitrd -c -k 3.2.29 -f ext4 -r /dev/sdb2 -m usb-storage:pcmcia_core:pcmcia:mmc_core:ssb:modprobe:usbhid:ehci-hcd:ohci-hcd:mbcache:jbd2:ext4 -u -o /boot/initrd_3.2.29.gz</code></note> <note warning>If you were already running a generic kernel and therefore already have an initrd, we strongly advise you to create a **new** initrd with a **new** unique name! For instance, you can copy the above example and modify the name of the initrd file as follows: <code>mkinitrd -c -k 3.2.29 -f ext4 -r /dev/sdb2 -m usb-storage:pcmcia_core:pcmcia:mmc_core:ssb:modprobe:usbhid:ehci-hcd:ohci-hcd:mbcache:jbd2:ext4 -u -o /boot/initrd_3.2.29.gz</code></note>
  
 fr:howtos:slackware-admin:systemupgrade ()