j’ai tapé la commande et ca n’a rien changé niveau espce disque…
root@jeedom:~# du -s /var/* | sort -rn
1282184 /var/www
799468 /var/lib
234944 /var/cache
87852 /var/log
7356 /var/backups
32 /var/spool
8 /var/tmp
4 /var/opt
4 /var/mail
4 /var/local
0 /var/run
0 /var/lock
root@jeedom:~#
Essaye ça:
sudo apt-get clean
merci je ne sais pas ce que ca a supprimé mais j’ai recupéré 3%
Ça a effacé les archives de tous les paquets dans /var/cache/apt/archives
Bonjour,
En regardant ce que j’ai /var/cache/apt/archives avec FileZilla
Ton mail veut dire que l’on peut tout supprimer sans risque ?
Merci
Supprimer à la main je ne sais pas, execute simplement la commande.
Si ça laisse des trucs c’est qu’il faut les laisser surement
c’est une réponse de « sage » …
Surtout pas effacer à la main.
Uniquement passer par les commandes UNIX poir faire le ménage.
ouf !
Je vous aime … 
J’ai une question concernant un orange pi avec jeedom dessus. il est en 9.9. Je peux faire ces 2 commandes également ?
apt-get update
apt-get upgrade
ca ne met a jour que linux ? sur cet orange pi j’ai aussi mosquito nodered ca va les mettre a jour aussi ?
Merci encore en tout cas pour la smart ca a fonctionné et depuis la 4.1 en beta le swap diminue beaucoup moins vite
Ces deux commandes réalisent chacune des actions bien spécifiques.
L’instruction update va rechercher les mises à jour disponibles pour le système et les programmes déjà installés, en se basant sur les sources (appelées techniquement des dépots) définies par défaut dans
/etc/apt/source.list
et de manière particulière dans tous fichiers .list contenus dans le répertoire
/etc/apt/sources.list.d/
Un fichier d’index est créé pour lister les mises à jour disponibles. Il servira de référence pour l’installation de nouvelles mises à jour.
Cette instruction ne met donc pas à proprement parler à jour le système lui même mais met à jour l’index des mises à jour (tu suis encore ?)
L’option upgrade installe les mises à jour identifiées avec apt-get update sans supprimer les paquets installés . S’il y a de nouvelles dépendances à installer, les paquets seront installés.
C’est une méthode recommandée puisque seuls les programmes déjà installés sont mis à jour.
En conclusion : ne seront mis à jour avec ces commandes que le système et les programmes déjà installés et dont les sources de mises à jour sont décrites dans le fichier /etc/apt/source.list et dans les éventuels fichiers xxx.list contenus dans le dossier /etc/apt/sources.list.d/
En espérant avoir répondu à ta question.
Oui donc ca risque de me mettre a jour nodered et mosquito et j’ai peur que ca mette le bazar. Je vais chercher comment cloner l’emmc de l’orange pi avant de mettre a jour.
Merci
Très récemment il y a eu une demande sur ce forum sur le clonage de l’eMMC et même de son remplacement par un eMMC de plus grande capacité.
En cherchant avec le mot clef emmc tu devrais trouver sans peine
oui j’ai ouvert un poste sur ce sujet. je vais me pencher sur la question des que j’ai un peu de temps.
Sujet ici sinon
J’ai encore une question concernant la mise a jour de la smart, lorsque j’ai fait ces commandes tout s’est bien déroulé mais 2 ou 3 fois il m’a demandé des confirmation de mise a jour mais dans le doute j’ai mis No. J’aurais du mettre Yes ?
Ben mettre no c’est ne pas updater…
Ca s’est mis a jour quand meme mais pas tout je pense. MAis je ne sais plus ce qu’il m’a demandé
apt-get update donne ceci
root@jeedom:~# apt-get update
Hit:2 https://deb.nodesource.com/node_12.x stretch InRelease
Ign:3 http://ftp.debian.org/debian stretch InRelease
Get:4 http://phoscon.de/apt/deconz stretch InRelease [2,859 B]
Hit:5 http://www.deb-multimedia.org stretch InRelease
Get:6 http://security.debian.org stretch/updates InRelease [53.0 kB]
Get:7 http://ftp.debian.org/debian stretch-updates InRelease [93.6 kB]
Get:1 https://repo.jeedom.com/odroid stable InRelease [1,640 B]
Get:8 http://ftp.debian.org/debian stretch-backports InRelease [91.8 kB]
Get:9 http://ftp.debian.org/debian stretch-proposed-updates InRelease [96.3 kB]
Hit:10 http://ftp.debian.org/debian stretch Release
Get:11 https://oph.mdrjr.net/meveric all InRelease [19.4 kB]
Get:12 https://oph.mdrjr.net/meveric stretch InRelease [4,141 B]
Ign:4 http://phoscon.de/apt/deconz stretch InRelease
Get:13 http://security.debian.org stretch/updates/main Sources [270 kB]
Get:14 http://security.debian.org stretch/updates/main arm64 Packages [589 kB]
Get:15 http://security.debian.org stretch/updates/main Translation-en [271 kB]
Get:17 https://oph.mdrjr.net/meveric stretch/main arm64 Packages [121 kB]
Fetched 1,614 kB in 4s (375 kB/s)
Reading package lists... Done
W: GPG error: http://phoscon.de/apt/deconz stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C9A78F88720A
W: The repository 'http://phoscon.de/apt/deconz stretch InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@jeedom:~#
et en faisant apt-get upgrade :
C’est ici qu’il me demande pour les 7 paquets que je n’ai pas osé mettre à jour
root@jeedom:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
libcurl3-gnutls linux-headers-arm64-odroid-c2 mariadb-client mariadb-client-10.1 mariadb-server mariadb-server-10.1
mariadb-server-core-10.1
The following packages will be upgraded:
bluetooth bluez curl gir1.2-packagekitglib-1.0 libapache2-mod-php7.0 libcurl3 libdbi-perl libfreetype6 liblua5.3-0 libmariadbclient18
libpackagekit-glib2-18 libsndfile1 libssl1.0.2 linux-libc-dev mariadb-client-core-10.1 mariadb-common nodejs php7.0 php7.0-cli
php7.0-common php7.0-curl php7.0-dev php7.0-fpm php7.0-gd php7.0-gmp php7.0-imap php7.0-intl php7.0-json php7.0-ldap php7.0-mbstring
php7.0-mcrypt php7.0-mysql php7.0-opcache php7.0-readline php7.0-snmp php7.0-soap php7.0-sqlite3 php7.0-xml php7.0-xmlrpc php7.0-zip
setup-odroid
41 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
Need to get 34.8 MB of archives.
After this operation, 2,176 kB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.
j’ai retrouvé le message, j’ai plusieurs fois ce panneau
Et j’ai aussi des probleme avec le fichier boot.ini
GNU sed home page: <http://www.gnu.org/software/sed/>.
General help using GNU software: <http://www.gnu.org/gethelp/>.
cat: /boot/boot.ini: No such file or directory
sed: can't read /boot/boot.ini: No such file or directory
sed: can't read /boot/boot.ini: No such file or directory
sed: can't read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can't read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can't read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can't read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can't read /boot/boot.ini: No such file or directory
sed: can't read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can't read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can't read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can't read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can't read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can't read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can't read /boot/boot.ini: No such file or directory
sed: can't read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can't read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can't read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can't read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
/var/lib/dpkg/info/setup-odroid.postinst: line 234: [: -lt: unary operator expected
patching file c2_init.sh
Hunk #1 succeeded at 37 (offset -1 lines).
/boot/initrd.img-3.14.29+ does not exist. Cannot update.
grep: /boot/boot.ini: No such file or directory
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/boot.ini b/boot.ini
|index 1bfe00b..97c5ba1 100755
|--- a/boot.ini 2016-03-19 13:37:36.000000000 +0100
|+++ b/boot.ini 2016-05-06 19:46:52.966733237 +0200
--------------------------
File to patch:
Skip this patch? [y] y
Skipping patch.
2 out of 2 hunks ignored
grep: /boot/boot.ini: No such file or directory
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/boot.ini b/boot.ini
|index 1bfe00b..97c5ba1 100755
|--- a/boot.ini
|+++ b/boot.ini
--------------------------
File to patch:
Skip this patch? [y] y
Skipping patch.
2 out of 2 hunks ignored
grep: /boot/boot.ini: No such file or directory
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/boot.ini b/boot.ini
|index 97c5ba1..1fd71fc 100755
|--- a/boot.ini
|+++ b/boot.ini
--------------------------
File to patch:
Skip this patch? [y] y
Skipping patch.
3 out of 3 hunks ignored
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/boot.ini b/boot.ini
|index 1fd71fc..c24642d 100755
|--- a/boot.ini
|+++ b/boot.ini
--------------------------
File to patch:
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- ./boot.ini 2016-06-10 10:23:48.000000000 +0200
|+++ ./boot-20160608.ini 2016-06-10 10:17:32.000000000 +0200
--------------------------
File to patch: y
y: No such file or directory
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
grep: /boot/boot.ini: No such file or directory
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/boot.ini b/boot.ini
|index c24642d..963b93e 100755
|--- a/boot.ini
|+++ b/boot.ini
--------------------------
File to patch:
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
grep: /boot/boot.ini: No such file or directory
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/boot.ini b/boot.ini
|index d96826b..7a697ca 100755
|--- a/boot.ini
|+++ b/boot.ini
--------------------------
File to patch:
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
grep: /boot/boot.ini: No such file or directory
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/boot.ini b/boot.ini
|index 7a697ca..4d6bcc2 100755
|--- a/boot.ini
|+++ b/boot.ini
--------------------------
File to patch:
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
grep: /boot/boot.ini: No such file or directory
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- boot/boot-20160911-2.ini 2016-09-11 12:32:40.000000000 +0200
|+++ boot/boot.ini 2016-09-11 12:34:02.000000000 +0200
--------------------------
File to patch:
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
grep: /boot/boot.ini: No such file or directory
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/boot.ini 2016-09-26 13:59:04.000000000 +0200
|+++ b/boot.ini 2016-09-26 14:39:44.000000000 +0200
--------------------------
File to patch:
Skip this patch? [y] y
Skipping patch.
2 out of 2 hunks ignored
grep: /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- boot/boot.ini.bak-20161228 2016-12-28 22:08:52.000000000 +0100
|+++ boot/boot.ini 2016-12-28 22:09:52.000000000 +0100
--------------------------
File to patch:
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
grep: /boot/boot.ini: No such file or directory
/var/lib/dpkg/info/setup-odroid.postinst: line 499: [: -lt: unary operator expected
grep: /boot/boot.ini: No such file or directory
/var/lib/dpkg/info/setup-odroid.postinst: line 499: [: -lt: unary operator expected
grep: /boot/boot.ini: No such file or directory
/var/lib/dpkg/info/setup-odroid.postinst: line 499: [: -lt: unary operator expected
grep: /boot/boot.ini: No such file or directory
/var/lib/dpkg/info/setup-odroid.postinst: line 502: [: -ge: unary operator expected
grep: /boot/boot.ini: No such file or directory
/var/lib/dpkg/info/setup-odroid.postinst: line 505: [: -lt: unary operator expected
grep: /boot/boot.ini: No such file or directory
/var/lib/dpkg/info/setup-odroid.postinst: line 508: [: -lt: unary operator expected
grep: /boot/boot.ini: No such file or directory
/var/lib/dpkg/info/setup-odroid.postinst: line 511: [: -lt: unary operator expected
Setting up libopenmpt0:arm64 (0.2.7386~beta20.3-3+deb9u4) ...
Setting up vim (2:8.0.0197-4+deb9u3) ...
Setting up libcurl3:arm64 (7.52.1-5+deb9u12) ...
Setting up libarchive13:arm64 (3.2.2-2+deb9u2) ...
Setting up apache2-utils (2.4.25-3+deb9u9) ...
Setting up libldb1:arm64 (2:1.1.27-1+deb9u1) ...
Setting up libpython3.5-stdlib:arm64 (3.5.3-1+deb9u2) ...
Setting up gnupg (2.1.18-8~deb9u4) ...
Setting up libx11-6:arm64 (2:1.6.4-3+deb9u3) ...
Setting up apache2-bin (2.4.25-3+deb9u9) ...
Setting up libdns-export162 (1:9.10.3.dfsg.P4-12.3+deb9u7) ...
Setting up libdpkg-perl (1.18.25) ...
Setting up libsox-fmt-alsa:arm64 (14.4.1-5+deb9u2) ...
Setting up python2.7 (2.7.13-2+deb9u4) ...
Setting up libgd3:arm64 (2.2.4-2+deb9u5) ...
Setting up php7.0-mcrypt (7.0.33-0+deb9u10) ...
Setting up php7.0-curl (7.0.33-0+deb9u10) ...
Setting up file (1:5.30-1+deb9u3) ...
Setting up python3.5-minimal (3.5.3-1+deb9u2) ...
Setting up php7.0-zip (7.0.33-0+deb9u10) ...
Setting up php7.0-xmlrpc (7.0.33-0+deb9u10) ...
Setting up dpkg-dev (1.18.25) ...
Setting up libxcursor1:arm64 (1:1.1.14-1+deb9u2) ...
Setting up openssh-sftp-server (1:7.4p1-10+deb9u7) ...
Setting up php7.0-sqlite3 (7.0.33-0+deb9u10) ...
Setting up php7.0-imap (7.0.33-0+deb9u10) ...
Setting up php7.0-json (7.0.33-0+deb9u10) ...
Setting up libpython2.7:arm64 (2.7.13-2+deb9u4) ...
Setting up python3-pip (9.0.1-2+deb9u2) ...
Setting up libexpat1-dev:arm64 (2.2.0-2+deb9u3) ...
Setting up libpython2.7-dev:arm64 (2.7.13-2+deb9u4) ...
Setting up libjpeg62-turbo-dev:arm64 (1:1.5.1-2+deb9u1) ...
Setting up dbus (1.10.32-0+deb9u1) ...
A reboot is required to replace the running dbus-daemon.
Please reboot the system when convenient.
Setting up libvorbisenc2:arm64 (1.3.5-4+deb9u2) ...
Setting up python-pip (9.0.1-2+deb9u2) ...
Setting up bluez (5.43-2+deb9u3) ...
Installing new version of config file /etc/bluetooth/input.conf ...
Setting up python2.7-dev (2.7.13-2+deb9u4) ...
Setting up python3.5 (3.5.3-1+deb9u2) ...
Setting up samba-libs:arm64 (2:4.5.16+dfsg-1+deb9u2) ...
Setting up apache2 (2.4.25-3+deb9u9) ...
Installing new version of config file /etc/init.d/apache-htcacheclean ...
insserv: warning: current start runlevel(s) (empty) of script `apache-htcacheclean' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache-htcacheclean' overrides LSB defaults (0 1 6).
Setting up libavutil55:arm64 (7:3.2.15-0+deb9u1) ...
Setting up curl (7.52.1-5+deb9u12) ...
Setting up php7.0-gd (7.0.33-0+deb9u10) ...
Setting up php7.0-cli (7.0.33-0+deb9u10) ...
Setting up libswresample2:arm64 (7:3.2.15-0+deb9u1) ...
Setting up php7.0-fpm (7.0.33-0+deb9u10) ...
Installing new version of config file /etc/php/7.0/fpm/pool.d/www.conf ...
NOTICE: Not enabling PHP 7.0 FPM by default.
NOTICE: To enable PHP 7.0 FPM in Apache2 do:
NOTICE: a2enmod proxy_fcgi setenvif
NOTICE: a2enconf php7.0-fpm
NOTICE: You are seeing this message because you have apache2 package installed.
Setting up libsmbclient:arm64 (2:4.5.16+dfsg-1+deb9u2) ...
Setting up libsndfile1:arm64 (1.0.27-3+deb9u1) ...
Setting up openssh-server (1:7.4p1-10+deb9u7) ...
Setting up smbclient (2:4.5.16+dfsg-1+deb9u2) ...
Setting up libjpeg-dev (1:1.5.1-2+deb9u1) ...
Setting up bluetooth (5.43-2+deb9u3) ...
Setting up libswscale4:arm64 (7:3.2.15-0+deb9u1) ...
Setting up libpostproc54:arm64 (7:3.2.15-0+deb9u1) ...
Setting up libsox-fmt-base:arm64 (14.4.1-5+deb9u2) ...
Setting up php7.0-dev (7.0.33-0+deb9u10) ...
Setting up libavresample3:arm64 (7:3.2.15-0+deb9u1) ...
Setting up php7.0 (7.0.33-0+deb9u10) ...
Setting up libapache2-mod-php7.0 (7.0.33-0+deb9u10) ...
libapache2-mod-php7.0: not switching MPM - already enabled
Setting up libavcodec57:arm64 (7:3.2.15-0+deb9u1) ...
Setting up libavformat57:arm64 (7:3.2.15-0+deb9u1) ...
Setting up sox (14.4.1-5+deb9u2) ...
Setting up libavfilter6:arm64 (7:3.2.15-0+deb9u1) ...
Setting up libavdevice57:arm64 (7:3.2.15-0+deb9u1) ...
Setting up ffmpeg (7:3.2.15-0+deb9u1) ...
Setting up libav-tools (7:3.2.15-0+deb9u1) ...
Processing triggers for libc-bin (2.24-11+deb9u4) ...
Processing triggers for ca-certificates (20200601~deb9u1) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Processing triggers for systemd (232-25+deb9u12) ...