Table des matières
- 2026:
- 2025:
4 billet(s) pour septembre 2026
| Notes HTTP Strict Transport Security - HSTS | 2026/09/18 11:04 | Jean-Baptiste |
| Notes GNU Linux GPU carte graphiques | 2026/09/08 15:49 | Jean-Baptiste |
| Notes GNU Linux graphique | 2026/09/08 15:42 | Jean-Baptiste |
| Notes urlencoding - passer des mots de passe en HTTPS | 2026/09/03 17:58 | Jean-Baptiste |
Cloud Pulumi
Voir aussi :
- Terraform / OpenTofu
- Crossplane / Kubevela
- Winglang / Darklang
Voir :
- Deskypus
Pulumi
openssl rand -base64 32 | sed -e "y/\\/+/\$_/" -e "s/=//g" > ~/.pulumi/passphrase.cfg chmod 600 ~/.pulumi/passphrase.cfg export PULUMI_CONFIG_PASSPHRASE_FILE=~/.pulumi/passphrase.cfg pulumi login --local pulumi stack init pulumi stack ls pulumi config set cloud:provider aws pulumi config set aws:region us-west-2 pulumi stack up curl $(pulumi stack output url) pulumi logs -f pulumi destroy --yes pulumi stack rm --yes
Pb yum - L'appel à la commande yum reset la conf yum.repos.d
podman run -ti aah.acme.local/ee-minimal-rhel8:latest /bin/bash cat /etc/yum.repo.d/redhat.repo microdnf update error: package python3-pathspec-0.6.0-1.el8.noarch cannot be verified and repo Default_Organization_EPEL8_EPEL8_x86_64 is GPG enabled: /var/cache/yum/metadata/Default_Organization_EPEL8_EPEL8_x86_64-8-x86_64/packages/python3-pathspec-0.6.0-1.el8.noarch.rpm could not be verified. /var/cache/yum/metadata/Default_Organization_EPEL8_EPEL8_x86_64-8-x86_64/packages/python3-pathspec-0.6.0-1.el8.noarch.rpm: digest: SIGNATURE
A l'intérieur d'un conteneur à chaque appel à la commande microdnf le fichier /etc/yum.repo.d/redhat.repo est réécrasé.
La conf provient de Satellite.
/etc/rhsm-host/rhsm.conf
[server] hostname = lb-capsule.acme.local [rhsm] baseurl = https://lb-capsule.acme.local/pulp/repos
Je test
sed -i -e 's/^gpgcheck=true/gpgcheck=false/g' /etc/yum.repos.d/redhat.repo
Mais la conf est réécrasée, il n'y a pas de persistance.
Solution
mkdir /var/lib/rhsm
Pb YubiKey FIDO
sudo apt-get install fido2-tools
$ fido2-token -L /dev/hidraw2: vendor=0x1050, product=0x0407 (Yubico YubiKey OTP+FIDO+CCID) $ fido2-token -I /dev/hidraw2 proto: 0x02 major: 0x05 minor: 0x02 build: 0x07 caps: 0x05 (wink, cbor, msg) version strings: U2F_V2, FIDO_2_0, FIDO_2_1_PRE extension strings: credProtect, hmac-secret transport strings: nfc, usb algorithms: es256 (public-key), eddsa (public-key) aaguid: 2fc0579f811347eab116bb5a8db9202a options: rk, up, noplat, clientPin, credentialMgmtPreview maxmsgsiz: 1200 maxcredcntlst: 8 maxcredlen: 128 maxlargeblob: 0 fwversion: 0x0 pin protocols: 1 pin retries: 5 uv retries: undefined $ FIDO_DEBUG=1 fido2-token -C /dev/hidraw0 fido_hid_unix_open: open /dev/hidraw0: Permission denied fido_dev_open_tx: dev->io.open fido2-token: fido_dev_open /dev/hidraw0: FIDO_ERR_INTERNAL $ ls -l /dev/hidraw0 crw------- 1 root root 244, 0 Aug 3 19:45 /dev/hidraw0
curl https://raw.githubusercontent.com/Yubico/libu2f-host/master/70-u2f.rules | sudo tee /etc/udev/rules.d/70-u2f.rules sudo systemctl restart udev fido2-token -L
$ pamu2fcfg >> ~/.config/Yubico/u2f_keys Enter PIN for /dev/hidraw2:
Changer le PIN pour FIDO
sudo apt-get install yubikey-manager
ykman fido access change-pin
Pb wrong fs type bad option bad superblock
Suite à ddrescue /dev/sdc1 sur /dev/sdd1 avec destination plus petit que original.
# mount -o ro /dev/sdd1 /mnt/
mount: wrong fs type, bad option, bad superblock on /dev/sdd1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
# dmesg
[2416788.550500] EXT4-fs (sdd1): bad geometry: block count 244190390 exceeds size of device (244182016 blocks)
# lsblk
sdd 8:48 0 931,5G 0 disk
└─sdd1 8:49 0 931,5G 0 part
# fdisk -s /dev/sdd
976729088
# fdisk -s /dev/sdd1
976728064
sfdisk -d /dev/sdd >sdd.txt #dd if=/dev/zero of=/dev/sdd bs=512 count=1 #sfdisk /dev/sdd <sdd.txt
sdd.txt
# partition table of /dev/sdd unit: sectors /dev/sdd1 : start= 2048, size=1953456128, Id=83 /dev/sdd2 : start= 0, size= 0, Id= 0 /dev/sdd3 : start= 0, size= 0, Id= 0 /dev/sdd4 : start= 0, size= 0, Id= 0
Règle de trois :
1 953 456 128 / 244 182 016 = 8 \ 244 190 390 * 8 = 1 953 523 120
fsck.ext4 /dev/sdd
Autres
http://wiki.linuxquestions.org/wiki/Resize2fs
umount /dev/myGroup/myVol e2fsck -f /dev/myGroup/myVol resize2fs -M /dev/myGroup/myVol lvreduce /dev/myGroup/myVol mount /dev/myGroup/myVol
Pb windows error 7B HAL
Pb de AHCI
https://fr.wikipedia.org/wiki/Advanced_Host_Controller_Interface http://www.tplpc.com/faq/passer-de-ide-ahci-sans-reinstaller-windows-7-02240.html
Pb de HAL
L'erreur STOP 7B c'est un classique pb de HAL (hardware abstraction layer) Jadis sous XP, 2003 il fallait extraire le fichier hal.dll du CD ouindoze.
Ça me rappel des souvenirs.
windows 7 - P2V
Comme ça ne fonctionnait toujours pas, j'ai activé les drivers suivants :
- aliide
- amdide
- atapi
- cmdide
- iastor
- iastorV
- intelide
- LSI_SAS
- msahci
- pciide
- viaide
Comme mentionné ici https://superuser.com/questions/1023131/virtualbox-windows-raw-disk-guest-blue-screen-error-0x0000007b-at-boot/1032769
Puis j'ai passé les disques en IDE.