Início / unix / 问题

All perguntas(unix)

Martin Hope
Eric B
Asked: 2024-11-09 21:26:16 +0800 CST
  • 7

Quero hospedar um servidor web no meu Raspberry Pi 1B na minha rede doméstica, então quero ter certeza de que o software está atualizado para minimizar o risco de segurança. Eu estava pensando em usar o lighttpd e consegui executá-lo, mas só consegui obter a versão 1.4.69 do apt quando a versão mais recente é 1.4.76. Olhando os changelogs, parece haver alguns patches de vulnerabilidade que eu gostaria de ter na minha instalação.

Verifiquei várias fontes e todas parecem concordar que você não pode simplesmente instalar uma nova versão do apt, porque elas precisam ser adicionadas manualmente ao apt do upstream. Eu poderia compilar a partir da fonte, mas seria bom evitar isso. Mas então me deparei com uma resposta para esta pergunta https://askubuntu.com/questions/970267/how-to-upgrade-lighttpd-1-4-33-to-1-4-47-on-ubuntu-14-04 que dizia que você poderia verificar se os patches de segurança são retroportados para a versão mais antiga disponível no apt.

Como posso verificar se as correções de segurança das versões entre 1.4.69 e 1.4.76 foram adicionadas à versão 1.4.69 instalada do apt?

Outras informações potencialmente relacionadas

Linux raspberrypi 6.6.51+rpt-rpi-v6 #1 Raspbian 1:6.6.51-1+rpt3 (2024-10-08) armv6l GNU/Linux

/etc/apt/sources.list:

deb [ arch=armhf ] http://raspbian.raspberrypi.com/raspbian/ bookworm main contrib non-free rpi

pi@raspberrypi:~ $ apt show lighttpd
Package: lighttpd
Version: 1.4.69-1
Priority: optional
Section: httpd
Maintainer: Debian lighttpd maintainers <[email protected]>
Installed-Size: 814 kB
Provides: httpd, httpd-cgi, lighttpd-mod-accesslog, lighttpd-mod-ajp13, lighttpd-mod-auth, lighttpd-mod-authn-file, lighttpd-mod-cgi, lighttpd-mod-dirlisting, lighttpd-mod-extforward, lighttpd-mod-proxy, lighttpd-mod-rrdtool, lighttpd-mod-sockproxy, lighttpd-mod-ssi, lighttpd-mod-status, lighttpd-mod-userdir, lighttpd-mod-vhostdb, lighttpd-mod-wstunnel
Pre-Depends: init-system-helpers (>= 1.54~)
Depends: libc6 (>= 2.36), libcrypt1 (>= 1:4.1.0), libnettle8, libpcre2-8-0 (>= 10.22), libxxhash0 (>= 0.6.5), media-types | mime-support, systemd-sysv | lsb-base
Recommends: spawn-fcgi, perl:any, lighttpd-mod-deflate, lighttpd-mod-openssl
Suggests: openssl, php-cgi, php-fpm (>= 2:7.4), apache2-utils, lighttpd-doc, lighttpd-mod-webdav, lighttpd-modules-dbi, lighttpd-modules-lua
Conflicts: lighttpd-mod-geoip, lighttpd-mod-trigger-b4-dl
Homepage: https://www.lighttpd.net/
Download-Size: 306 kB
APT-Sources: http://raspbian.raspberrypi.com/raspbian bookworm/main armhf Packages
Description: fast webserver with minimal memory footprint
 lighttpd is a small webserver and fast webserver developed with
 security in mind and a lot of features.
 It has support for
   * CGI, FastCGI and SSI
   * virtual hosts
   * URL rewriting
   * authentication (plain files, htpasswd, LDAP)
   * transparent content compression
   * conditional configuration
   * HTTP proxying
 and configuration is straight-forward and easy.
apt
Martin Hope
SekstusEmpiryk
Asked: 2024-11-09 18:36:03 +0800 CST
  • 7

Li em Programação Avançada em Ambiente Unix isto:

O buffer de linha vem com duas ressalvas. Primeiro, o tamanho do buffer que a biblioteca de E/S padrão usa para coletar cada linha é fixo, então a E/S pode ocorrer se preenchermos esse buffer antes de escrever uma nova linha. Segundo, sempre que a entrada for solicitada por meio da biblioteca de E/S padrão de (a) um fluxo sem buffer ou (b) um fluxo com buffer de linha (que requer que os dados sejam solicitados do kernel), todos os fluxos de saída com buffer de linha são liberados. O motivo do qualificador em (b) é que os dados solicitados podem já estar no buffer, o que não requer que os dados sejam lidos do kernel. Obviamente, qualquer entrada de um fluxo sem buffer, item (a), requer que os dados sejam obtidos do kernel.

https://www.gnu.org/software/libc/manual/html_node/Flushing-Buffers.html afirma:

Liberar a saída em um fluxo em buffer significa transmitir todos os caracteres acumulados para o arquivo. Há muitas circunstâncias em que a saída em buffer em um fluxo é liberada automaticamente:

Quando você tenta fazer uma saída e o buffer de saída está cheio.

Quando o fluxo é fechado. Veja Fechando Fluxos.

Quando o programa termina chamando exit. Veja Término Normal. Quando uma nova linha é escrita, se o fluxo for bufferizado por linha.

Sempre que uma operação de entrada em qualquer fluxo realmente lê dados de seu arquivo.

Então eu escrevi um programa para testar isso:

#include <stdio.h>
#include <unistd.h>

int
main()
{
    printf("Hello");
    FILE *fp = fopen("hugefile", "r");
    if (fp == NULL) {
        fprintf(stderr, "Cannot open file\n");
        return -1;
    }
    setvbuf(fp, NULL, _IONBF, 0);
    sleep(2);
    char buf[10];

    while (fread(buf, sizeof(char), 10, fp) == 10) {
    }

    if (ferror(fp)) {
        fprintf(stderr, "Read error\n");
        return -1;
    }; // I expect "Hello" to appear on a screen but it doesn't
    fclose(fp);
    sleep(50);
}

Mas fread() não dispara o flashing da saída. Estou esquecendo de algo?

Não sei o que pode ser relevante aqui, mas eu uso:

gcc versão 14.2.1 20240910

glibc 2.40+r16+gaa533d58ff-2

c
Martin Hope
ZacWolf
Asked: 2024-11-09 06:01:57 +0800 CST
  • 6

Estou tentando extrair a data e o endereço IP da saída delastb

Estou usando:lastb | awk '{print $5,$6,$7,$3}'

O problema é que às vezes a primeira coluna (userID) lastbfica em branco:

Exemplo de dados:

wpsadmin ssh:notty 213.109.202.127 Ter 1 Out 12:07 - 12:07 (00:00)
         ssh:notty 8.219.222.66 Terça, 1º de outubro, 11h48 - 11h48 (00h00)
quser ssh:notty 213.109.202.127 Terça, 1º de outubro, 11h03 - 11h03 (00h00)
udatabas ssh:notty 139.19.117.130 Ter Out 1 10:34 - 10:34 (00:00)
Admin ssh:notty 213.109.202.127 Terça, 1º de outubro, 09:58 - 09:58 (00:00)
         ssh:notty 79.110.62.93 Terça, 1º de outubro, 09:40 - 09:40 (00:00)
udatabas ssh:notty 139.19.117.130 Ter Out 1 09:34 - 09:34 (00:00)

...o que desequilibra minhas variáveis ​​awk em uma.

Então, usar: lastb | awk '{print $5,$6,$7,$3}'para o conjunto de dados acima me dá:

1 de outubro 12:07 213.109.202.127
1 11:48 - Ter
1 de outubro 11:03 213.109.202.127
1 de outubro 10:34 139.19.117.130
1 de outubro 09:58 213.109.202.127
1 09:40 - Ter
1 de outubro 09:34 139.19.117.130

Como retifico isso? Obrigado!

bash
Martin Hope
jsx97
Asked: 2024-11-09 00:39:24 +0800 CST
  • 5

Aqui está uma solução sobre como fazer o cURL retomar automaticamente downloads interrompidos, da postagem do blog de 2013 de Juan Nunez-Iglesias :

export ec=18; while [ $ec -eq 18 ]; do curl -O -C - http://site.xyz/file.zip; export ec=$?; done

Foi postado diversas vezes aqui e no Stack Overflow, tanto na versão original quanto com pequenas alterações dentro do whileloop.

As mudanças dentro do whileloop foram introduzidas por pessoas diferentes para tornar o script mais robusto.

  • "O código de saída que o curl chucks exibe quando um download é interrompido é 18, e $?fornece o código de saída do último comando no bash. Então, enquanto o código de saída for 18, continue tentando baixar o arquivo, mantendo o nome do arquivo ( -O) e continuando de onde o download anterior parou ( -C)." - Juan Nunez-Iglesias
  • "Como Jan aponta nos comentários, dependendo do que está errado com o download, seu código de erro pode ser diferente. Basta alterar 18 para qualquer erro que você esteja vendo para fazê-lo funcionar para você! (Se você estiver se sentindo aventureiro, você pode alterar a condição para while [ $ec -ne 0 ], mas isso parece usar um except simples em Python, o que é ruim. ;)" - Juan Nunez-Iglesias
  • "No meu caso, o curl sai com códigos diferentes, então eu verifico o código de sucesso: while [ $ec -ni 0 ]" - Ilya Belsky, aqui

Em março, Helder Magalhães sugeriu substituir o whileloop na versão original de Juan por until:

Esta solução pode ser ainda mais simplificada usando untilunstead. Veja thread relacionada .

Embora eu não seja muito bom em usar cURL ou scripts de shell, eu tentaria escrevê-los eu mesmo, mas o problema de escrevê-los eu mesmo não é o script em si, mas a falta de compreensão de como testá-lo corretamente.

Alguém poderia mostrar como implementar a ideia do Helder? E isso realmente torna o script mais robusto?

Eu uso Zsh.

zsh
Martin Hope
Chris
Asked: 2024-11-08 17:27:24 +0800 CST
  • 6

Apenas adicionar um pouco de capacidade de armazenamento no meu servidor de armazenamento Openmediavault deu errado. O que devo fazer para recuperar? Você pode me orientar?

Foi isso que eu fiz:

1 conjunto /dev/md2 raid5 criado, correu bem

2 /dev/md2 pv criado, correu bem

3 /dev/md2 pv incluído no grupo de volume datavg correu bem

4 criar um novo sistema de arquivos no volume lógico datalv não foi possível - nenhum dispositivo disponível. Agora sei que apenas um fs por lv é possível, mas não sabia disso quando tentei isso.

5 lvextend no datalv, correu bem - o datalv agora tem capacidade total, incluindo as novas unidades

6. Ainda não é possível criar um novo sistema de arquivos no datalv - nenhum dispositivo disponível.

7 tentando fsgrow, aloquei toda a capacidade de uma só vez - não era o que eu queria...

8 lvreduce em datalv para aproximadamente capacidade original, correu bem

9 lvcreate data2lv, correu bem

10 criando o novo sistema de arquivos no data2lv (XFS) dessa vez, funcionou

Após reiniciar o sistema, o antigo sistema de arquivos (dados) não é montado e não há sinal do novo (XFS).

Eu estava errado ao supor que um lv pode ter mais de um sistema de arquivos, então a etapa 4 é quando as coisas começaram a dar errado. A etapa 5 também estava errada, mas talvez reversível. A etapa 7 foi um grande erro, já que o sistema de arquivos não pode ser encolhido de volta. O resto das etapas ainda está mais errado, mas como posso consertar isso? Desfazer as etapas 8 a 10 e viver com apenas um sistema de arquivos? Achei que deveria perguntar aqui antes de bagunçar as coisas ainda mais.

Eu ficaria muito grato por alguma ajuda sobre isso,

/C

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=be85bbea-6e8b-4710-b1e0-894ad8d34d20 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=035fdb6b-e1bb-46c9-81c5-ff28840063c7 none            swap    sw              0       0
# >>> [openmediavault]
/dev/disk/by-label/data        /srv/dev-disk-by-label-data    ext4    defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl    0 2
/dev/disk/by-uuid/035fdb6b-e1bb-46c9-81c5-ff28840063c7        /srv/dev-disk-by-uuid-035fdb6b-e1bb-46c9-81c5-ff28840063c7    ext2    defaults,nofail,user_xattr,acl    0 2
/srv/dev-disk-by-label-data/data/        /export/data    none    bind,nofail    0 0
/srv/dev-disk-by-label-data/data/Backups/HomeAssistant/        /export/HAss    none    bind,nofail    0 0
/srv/dev-disk-by-label-data/data/Backups/LinHES/        /export/LinHES_backup    none    bind,nofail    0 0
/srv/dev-disk-by-label-data/data/LinHES/        /export/LinHES    none    bind,nofail    0 0
/srv/dev-disk-by-label-data/data/securitycams/        /export/securitycams    none    bind,nofail    0 0
# <<< [openmediavault]

volume group

logical volumes

file system

system log

fim da saída do dmesg:

[    7.009650] mpt2sas_cm0: handle(0x12) sas_address(0x5001e67958f53ffd) port_type(0x1)
[    7.010381] scsi 3:0:8:0: Enclosure         Intel    RES2SV240        0d00 PQ: 0 ANSI: 5
[    7.010385] scsi 3:0:8:0: set ignore_delay_remove for handle(0x0012)
[    7.010388] scsi 3:0:8:0: SES: handle(0x0012), sas_addr(0x5001e67958f53ffd), phy(24), device_name(0x0000000000000000)
[    7.010390] scsi 3:0:8:0: enclosure logical id (0x5001e67958f53fff), slot(24) 
[    7.010392] scsi 3:0:8:0: qdepth(254), tagged(1), scsi_level(6), cmd_que(1)
[    7.013166]  end_device-3:0:8: add: handle(0x0012), sas_addr(0x5001e67958f53ffd)
[    9.745705] mpt2sas_cm0: port enable: SUCCESS
[    9.747042] scsi 2:0:0:0: Direct-Access     ATA      Corsair Force GS 5.07 PQ: 0 ANSI: 5
[    9.747591] scsi 4:0:0:0: Direct-Access     ATA      Corsair Force GS 5.07 PQ: 0 ANSI: 5
[    9.750711] ohci-pci 0000:00:12.0: OHCI PCI host controller
[    9.750787] ohci-pci 0000:00:12.0: new USB bus registered, assigned bus number 5
[    9.750831] ohci-pci 0000:00:12.0: irq 16, io mem 0xfe02e000
[    9.764544] ses 3:0:8:0: Attached Enclosure device
[    9.772078] sd 3:0:0:0: Power-on or device reset occurred
[    9.772102] sd 3:0:1:0: Power-on or device reset occurred
[    9.772361] sd 3:0:4:0: Power-on or device reset occurred
[    9.772413] sd 3:0:5:0: Power-on or device reset occurred
[    9.772487] sd 3:0:2:0: Power-on or device reset occurred
[    9.772540] sd 3:0:7:0: Power-on or device reset occurred
[    9.772555] sd 3:0:6:0: Power-on or device reset occurred
[    9.772646] sd 3:0:3:0: Power-on or device reset occurred
[    9.772671] sd 2:0:0:0: [sdi] 250069680 512-byte logical blocks: (128 GB/119 GiB)
[    9.772681] sd 4:0:0:0: [sdj] 250069680 512-byte logical blocks: (128 GB/119 GiB)
[    9.772686] sd 2:0:0:0: [sdi] Write Protect is off
[    9.772690] sd 2:0:0:0: [sdi] Mode Sense: 00 3a 00 00
[    9.772697] sd 4:0:0:0: [sdj] Write Protect is off
[    9.772701] sd 4:0:0:0: [sdj] Mode Sense: 00 3a 00 00
[    9.772708] sd 3:0:1:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
[    9.772709] sd 2:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    9.772712] sd 3:0:1:0: [sdb] 4096-byte physical blocks
[    9.772716] sd 3:0:0:0: [sda] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
[    9.772721] sd 3:0:0:0: [sda] 4096-byte physical blocks
[    9.772724] sd 4:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    9.772736] sd 2:0:0:0: [sdi] Preferred minimum I/O size 512 bytes
[    9.772757] sd 4:0:0:0: [sdj] Preferred minimum I/O size 512 bytes
[    9.773008] sd 3:0:2:0: [sdc] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[    9.773011] sd 3:0:2:0: [sdc] 4096-byte physical blocks
[    9.773135] sd 3:0:4:0: [sdd] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
[    9.773137] sd 3:0:4:0: [sdd] 4096-byte physical blocks
[    9.773163] sd 3:0:3:0: [sde] 5860531055 512-byte logical blocks: (3.00 TB/2.73 TiB)
[    9.773165] sd 3:0:3:0: [sde] 4096-byte physical blocks
[    9.773188] sd 3:0:5:0: [sdf] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
[    9.773190] sd 3:0:5:0: [sdf] 4096-byte physical blocks
[    9.773310] sd 3:0:6:0: [sdg] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
[    9.773312] sd 3:0:6:0: [sdg] 4096-byte physical blocks
[    9.773556] sd 3:0:7:0: [sdh] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
[    9.773559] sd 3:0:7:0: [sdh] 4096-byte physical blocks
[    9.774714] sd 3:0:7:0: [sdh] Write Protect is off
[    9.774717] sd 3:0:7:0: [sdh] Mode Sense: 7f 00 10 08
[    9.775773] sd 3:0:7:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    9.776271] sd 3:0:0:0: [sda] Write Protect is off
[    9.776275] sd 3:0:0:0: [sda] Mode Sense: 7f 00 10 08
[    9.776336] sd 3:0:1:0: [sdb] Write Protect is off
[    9.776341] sd 3:0:1:0: [sdb] Mode Sense: 7f 00 10 08
[    9.776448]  sdj: sdj1 sdj2 sdj3
[    9.776475]  sdi: sdi1 sdi2 sdi3
[    9.776627] sd 4:0:0:0: [sdj] Attached SCSI disk
[    9.776662] sd 2:0:0:0: [sdi] Attached SCSI disk
[    9.776678] sd 3:0:4:0: [sdd] Write Protect is off
[    9.776681] sd 3:0:4:0: [sdd] Mode Sense: 7f 00 10 08
[    9.776734] sd 3:0:5:0: [sdf] Write Protect is off
[    9.776737] sd 3:0:5:0: [sdf] Mode Sense: 7f 00 10 08
[    9.776872] sd 3:0:6:0: [sdg] Write Protect is off
[    9.776875] sd 3:0:6:0: [sdg] Mode Sense: 7f 00 10 08
[    9.777101] sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    9.777171] sd 3:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    9.777195] sd 3:0:3:0: [sde] Write Protect is off
[    9.777198] sd 3:0:3:0: [sde] Mode Sense: 7f 00 10 08
[    9.777740] sd 3:0:4:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    9.777802] sd 3:0:5:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    9.777908] sd 3:0:6:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    9.778042] sd 3:0:3:0: [sde] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    9.792872] sd 3:0:7:0: [sdh] Attached SCSI disk
[    9.794058] sd 3:0:5:0: [sdf] Attached SCSI disk
[    9.797109] sd 3:0:0:0: [sda] Attached SCSI disk
[    9.797304] sd 3:0:1:0: [sdb] Attached SCSI disk
[    9.799595] sd 3:0:6:0: [sdg] Attached SCSI disk
[    9.800877] sd 3:0:4:0: [sdd] Attached SCSI disk
[    9.803440] sd 3:0:3:0: [sde] Attached SCSI disk
[    9.813710] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.01
[    9.813714] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    9.813717] usb usb5: Product: OHCI PCI host controller
[    9.813719] usb usb5: Manufacturer: Linux 6.1.0-0.deb11.21-amd64 ohci_hcd
[    9.813720] usb usb5: SerialNumber: 0000:00:12.0
[    9.813858] hub 5-0:1.0: USB hub found
[    9.813868] hub 5-0:1.0: 3 ports detected
[    9.814196] ohci-pci 0000:00:12.1: OHCI PCI host controller
[    9.814206] ohci-pci 0000:00:12.1: new USB bus registered, assigned bus number 6
[    9.814228] ohci-pci 0000:00:12.1: irq 16, io mem 0xfe02d000
[    9.854662] sd 3:0:2:0: [sdc] Write Protect is off
[    9.854671] sd 3:0:2:0: [sdc] Mode Sense: 7f 00 10 08
[    9.855445] sd 3:0:2:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    9.877753] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.01
[    9.877757] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    9.877760] usb usb6: Product: OHCI PCI host controller
[    9.877761] usb usb6: Manufacturer: Linux 6.1.0-0.deb11.21-amd64 ohci_hcd
[    9.877763] usb usb6: SerialNumber: 0000:00:12.1
[    9.877897] hub 6-0:1.0: USB hub found
[    9.877907] hub 6-0:1.0: 3 ports detected
[    9.878193] ohci-pci 0000:00:13.0: OHCI PCI host controller
[    9.878199] ohci-pci 0000:00:13.0: new USB bus registered, assigned bus number 7
[    9.878250] ohci-pci 0000:00:13.0: irq 18, io mem 0xfe02b000
[    9.941747] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.01
[    9.941751] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    9.941754] usb usb7: Product: OHCI PCI host controller
[    9.941755] usb usb7: Manufacturer: Linux 6.1.0-0.deb11.21-amd64 ohci_hcd
[    9.941757] usb usb7: SerialNumber: 0000:00:13.0
[    9.941879] hub 7-0:1.0: USB hub found
[    9.941889] hub 7-0:1.0: 3 ports detected
[    9.942167] ohci-pci 0000:00:13.1: OHCI PCI host controller
[    9.942173] ohci-pci 0000:00:13.1: new USB bus registered, assigned bus number 8
[    9.942192] ohci-pci 0000:00:13.1: irq 18, io mem 0xfe02a000
[    9.946582] sd 3:0:2:0: [sdc] Attached SCSI disk
[    9.982793] md/raid1:md1: active with 2 out of 2 mirrors
[    9.982808] md/raid1:md126: active with 2 out of 2 mirrors
[    9.982863] md1: detected capacity change from 0 to 78124928
[    9.983036] md126: detected capacity change from 0 to 156227456
[   10.005696] usb usb8: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.01
[   10.005702] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   10.005704] usb usb8: Product: OHCI PCI host controller
[   10.005706] usb usb8: Manufacturer: Linux 6.1.0-0.deb11.21-amd64 ohci_hcd
[   10.005708] usb usb8: SerialNumber: 0000:00:13.1
[   10.005838] hub 8-0:1.0: USB hub found
[   10.005849] hub 8-0:1.0: 3 ports detected
[   10.006185] ohci-pci 0000:00:14.5: OHCI PCI host controller
[   10.006192] ohci-pci 0000:00:14.5: new USB bus registered, assigned bus number 9
[   10.006214] ohci-pci 0000:00:14.5: irq 18, io mem 0xfe028000
[   10.053689] raid6: sse2x4   gen()  7753 MB/s
[   10.073706] usb usb9: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.01
[   10.073711] usb usb9: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   10.073714] usb usb9: Product: OHCI PCI host controller
[   10.073716] usb usb9: Manufacturer: Linux 6.1.0-0.deb11.21-amd64 ohci_hcd
[   10.073718] usb usb9: SerialNumber: 0000:00:14.5
[   10.073851] hub 9-0:1.0: USB hub found
[   10.073862] hub 9-0:1.0: 2 ports detected
[   10.121687] raid6: sse2x2   gen()  7627 MB/s
[   10.189688] raid6: sse2x1   gen()  6191 MB/s
[   10.189691] raid6: using algorithm sse2x4 gen() 7753 MB/s
[   10.257685] raid6: .... xor() 3661 MB/s, rmw enabled
[   10.257687] raid6: using ssse3x2 recovery algorithm
[   10.258670] xor: automatically using best checksumming function   avx       
[   10.259422] async_tx: api initialized (async)
[   10.271440] md/raid:md0: device sde operational as raid disk 3
[   10.271444] md/raid:md0: device sdb operational as raid disk 1
[   10.271445] md/raid:md0: device sda operational as raid disk 0
[   10.271446] md/raid:md0: device sdc operational as raid disk 2
[   10.271465] md/raid:md2: device sdf operational as raid disk 1
[   10.271469] md/raid:md2: device sdh operational as raid disk 3
[   10.271471] md/raid:md2: device sdg operational as raid disk 2
[   10.271472] md/raid:md2: device sdd operational as raid disk 0
[   10.272715] md/raid:md0: raid level 5 active with 4 out of 4 devices, algorithm 2
[   10.272728] md/raid:md2: raid level 5 active with 4 out of 4 devices, algorithm 2
[   10.274723] md2: detected capacity change from 0 to 58597828608
[   10.302716] md0: detected capacity change from 0 to 17580797952
[   10.314506] usb 5-2: new full-speed USB device number 2 using ohci-pci
[   10.351344] random: crng init done
[   10.478717] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
[   10.478750] device-mapper: uevent: version 1.0.3
[   10.478830] device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: [email protected]
[   10.524723] usb 5-2: New USB device found, idVendor=051d, idProduct=0003, bcdDevice= 1.06
[   10.524729] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   10.524731] usb 5-2: Product: Smart-UPS 1000 FW:UPS 09.3 / ID=18
[   10.524733] usb 5-2: Manufacturer: American Power Conversion 
[   10.524734] usb 5-2: SerialNumber: AS1707331537  
[   10.535479] hid: raw HID events driver (C) Jiri Kosina
[   10.544453] usbcore: registered new interface driver usbhid
[   10.544456] usbhid: USB HID core driver
[   10.546915] hid-generic 0003:051D:0003.0001: hiddev0,hidraw0: USB HID v1.00 Device [American Power Conversion  Smart-UPS 1000 FW:UPS 09.3 / ID=18] on usb-0000:00:12.0-2/input0
[   11.087936] Btrfs loaded, crc32c=crc32c-intel, zoned=yes, fsverity=yes
[   41.958600] EXT4-fs (md126): mounted filesystem with ordered data mode. Quota mode: none.
[   42.013214] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.
[   42.090393] systemd[1]: Inserted module 'autofs4'
[   42.115930] systemd[1]: systemd 247.3-7+deb11u6 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified)
[   42.116051] systemd[1]: Detected architecture x86-64.
[   42.116543] systemd[1]: Set hostname to <bolivar>.
[   42.306079] systemd[1]: /etc/systemd/system/clamav-onaccess.service:13: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
[   42.306476] systemd[1]: /lib/systemd/system/clamav-freshclam.service:11: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
[   42.307153] systemd[1]: /lib/systemd/system/clamav-daemon.service:12: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
[   42.312038] systemd[1]: Queued start job for default target Graphical Interface.
[   42.330323] systemd[1]: Created slice system-getty.slice.
[   42.330620] systemd[1]: Created slice system-modprobe.slice.
[   42.330854] systemd[1]: Created slice system-postfix.slice.
[   42.331079] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[   42.331305] systemd[1]: Created slice User and Session Slice.
[   42.331368] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[   42.331420] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[   42.331575] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[   42.331608] systemd[1]: Reached target Local Encrypted Volumes.
[   42.331652] systemd[1]: Reached target Paths.
[   42.331680] systemd[1]: Reached target Slices.
[   42.331703] systemd[1]: Reached target System Time Set.
[   42.331781] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[   42.331874] systemd[1]: Listening on LVM2 poll daemon socket.
[   42.336222] systemd[1]: Listening on RPCbind Server Activation Socket.
[   42.336356] systemd[1]: Listening on Syslog Socket.
[   42.336470] systemd[1]: Listening on fsck to fsckd communication Socket.
[   42.336541] systemd[1]: Listening on initctl Compatibility Named Pipe.
[   42.336712] systemd[1]: Listening on Journal Audit Socket.
[   42.336827] systemd[1]: Listening on Journal Socket (/dev/log).
[   42.336946] systemd[1]: Listening on Journal Socket.
[   42.337078] systemd[1]: Listening on Network Service Netlink Socket.
[   42.337484] systemd[1]: Listening on udev Control Socket.
[   42.337575] systemd[1]: Listening on udev Kernel Socket.
[   42.338502] systemd[1]: Mounting Huge Pages File System...
[   42.339406] systemd[1]: Mounting POSIX Message Queue File System...
[   42.340365] systemd[1]: Mounting NFSD configuration filesystem...
[   42.341305] systemd[1]: Mounting RPC Pipe File System...
[   42.342485] systemd[1]: Mounting Kernel Debug File System...
[   42.343458] systemd[1]: Mounting Kernel Trace File System...
[   42.343588] systemd[1]: Condition check resulted in Kernel Module supporting RPCSEC_GSS being skipped.
[   42.343753] systemd[1]: Finished Availability of block devices.
[   42.345380] systemd[1]: Starting Set the console keyboard layout...
[   42.346510] systemd[1]: Starting Create list of static device nodes for the current kernel...
[   42.347606] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
[   42.348989] systemd[1]: Starting Load Kernel Module configfs...
[   42.350348] systemd[1]: Starting Load Kernel Module drm...
[   42.351388] systemd[1]: Starting Load Kernel Module fuse...
[   42.351481] systemd[1]: Condition check resulted in OpenVSwitch configuration for cleanup being skipped.
[   42.352694] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
[   42.352730] systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
[   42.354950] systemd[1]: Starting Journal Service...
[   42.357137] systemd[1]: Starting Load Kernel Modules...
[   42.358386] systemd[1]: Starting Remount Root and Kernel File Systems...
[   42.359555] systemd[1]: Starting Coldplug All udev Devices...
[   42.362006] systemd[1]: Mounted Huge Pages File System.
[   42.362148] systemd[1]: Mounted POSIX Message Queue File System.
[   42.362262] systemd[1]: Mounted Kernel Debug File System.
[   42.362373] systemd[1]: Mounted Kernel Trace File System.
[   42.362841] systemd[1]: Finished Create list of static device nodes for the current kernel.
[   42.363275] systemd[1]: [email protected]: Succeeded.
[   42.363694] systemd[1]: Finished Load Kernel Module configfs.
[   42.364942] systemd[1]: Mounting Kernel Configuration File System...
[   42.368675] systemd[1]: Finished Load Kernel Modules.
[   42.368852] systemd[1]: Mounted Kernel Configuration File System.
[   42.370036] systemd[1]: Starting Apply Kernel Variables...
[   42.370843] fuse: init (API version 7.37)
[   42.371752] systemd[1]: [email protected]: Succeeded.
[   42.372144] systemd[1]: Finished Load Kernel Module fuse.
[   42.373401] systemd[1]: Mounting FUSE Control File System...
[   42.376648] systemd[1]: Mounted FUSE Control File System.
[   42.383402] systemd[1]: Finished Apply Kernel Variables.
[   42.384015] EXT4-fs (md126): re-mounted. Quota mode: none.
[   42.385366] systemd[1]: Finished Remount Root and Kernel File Systems.
[   42.387332] systemd[1]: Starting Initial Check File System Quotas...
[   42.387952] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
[   42.388047] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
[   42.389092] systemd[1]: Starting Load/Save Random Seed...
[   42.390273] systemd[1]: Starting Create System Users...
[   42.406816] systemd[1]: Finished Load/Save Random Seed.
[   42.408709] systemd[1]: Condition check resulted in First Boot Complete being skipped.
[   42.410165] systemd[1]: Finished Create System Users.
[   42.412453] systemd[1]: Starting Create Static Device Nodes in /dev...
[   42.418172] systemd[1]: Finished Initial Check File System Quotas.
[   42.429120] systemd[1]: Finished Create Static Device Nodes in /dev.
[   42.430906] systemd[1]: Starting Rule-based Manager for Device Events and Files...
[   42.436223] RPC: Registered named UNIX socket transport module.
[   42.436227] RPC: Registered udp transport module.
[   42.436228] RPC: Registered tcp transport module.
[   42.436229] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   42.449951] ACPI: bus type drm_connector registered
[   42.450404] systemd[1]: Mounted RPC Pipe File System.
[   42.451406] systemd[1]: Starting pNFS block layout mapping daemon...
[   42.451934] systemd[1]: [email protected]: Succeeded.
[   42.452283] systemd[1]: Finished Load Kernel Module drm.
[   42.454355] systemd[1]: Started pNFS block layout mapping daemon.
[   42.466920] systemd[1]: Started Rule-based Manager for Device Events and Files.
[   42.468985] systemd[1]: Starting Network Service...
[   42.482992] systemd[1]: Finished Set the console keyboard layout.
[   42.507752] systemd[1]: Finished Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
[   42.507870] systemd[1]: Reached target Local File Systems (Pre).
[   42.539579] systemd[1]: Started Journal Service.
[   42.553503] acpi_cpufreq: overriding BIOS provided _PSD data
[   42.561672] sd 3:0:0:0: Attached scsi generic sg0 type 0
[   42.565078] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[   42.568531] ACPI: button: Power Button [PWRB]
[   42.568874] sd 3:0:1:0: Attached scsi generic sg1 type 0
[   42.570834] sd 3:0:2:0: Attached scsi generic sg2 type 0
[   42.574606] sd 3:0:3:0: Attached scsi generic sg3 type 0
[   42.576518] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[   42.576551] sd 3:0:4:0: Attached scsi generic sg4 type 0
[   42.577588] sd 3:0:5:0: Attached scsi generic sg5 type 0
[   42.584095] sd 3:0:6:0: Attached scsi generic sg6 type 0
[   42.592174] ACPI: button: Power Button [PWRF]
[   42.595542] sd 3:0:7:0: Attached scsi generic sg7 type 0
[   42.595748] r8169 0000:04:00.0: firmware: direct-loading firmware rtl_nic/rtl8168g-2.fw
[   42.596555] ses 3:0:8:0: Attached scsi generic sg8 type 13
[   42.596684] sd 2:0:0:0: Attached scsi generic sg9 type 0
[   42.599088] sd 4:0:0:0: Attached scsi generic sg10 type 0
[   42.604298] input: PC Speaker as /devices/platform/pcspkr/input/input3
[   42.615393] systemd-journald[798]: Received client request to flush runtime journal.
[   42.619045] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
[   42.621719] Generic FE-GE Realtek PHY r8169-0-400:00: attached PHY driver (mii_bus:phy_addr=r8169-0-400:00, irq=MAC)
[   42.642344] sp5100-tco sp5100-tco: Failed to reserve MMIO or alternate MMIO region
[   42.642395] sp5100-tco: probe of sp5100-tco failed with error -16
[   42.655985] cryptd: max_cpu_qlen set to 1000
[   42.685219] AVX version of gcm_enc/dec engaged.
[   42.685272] AES CTR mode by8 optimization enabled
[   42.800800] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:05.1/sound/card0/input4
[   42.818231] r8169 0000:04:00.0 enp4s0: Link is Down
[   42.888925] [drm] radeon kernel modesetting enabled.
[   42.889075] radeon 0000:01:05.0: vgaarb: deactivate vga console
[   42.889633] Console: switching to colour dummy device 80x25
[   42.889920] [drm] initializing kernel modesetting (RS780 0x1002:0x9616 0x1458:0xD000 0x00).
[   42.890569] ATOM BIOS: B27732
[   42.890585] radeon 0000:01:05.0: VRAM: 512M 0x00000000C0000000 - 0x00000000DFFFFFFF (512M used)
[   42.890590] radeon 0000:01:05.0: GTT: 512M 0x00000000A0000000 - 0x00000000BFFFFFFF
[   42.890598] [drm] Detected VRAM RAM=512M, BAR=256M
[   42.890600] [drm] RAM width 32bits DDR
[   42.890629] [drm] radeon: 512M of VRAM memory ready
[   42.890632] [drm] radeon: 512M of GTT memory ready.
[   42.890641] [drm] Loading RS780 Microcode
[   42.893910] radeon 0000:01:05.0: firmware: direct-loading firmware radeon/RS780_pfp.bin
[   42.894752] radeon 0000:01:05.0: firmware: direct-loading firmware radeon/RS780_me.bin
[   42.896489] radeon 0000:01:05.0: firmware: direct-loading firmware radeon/R600_rlc.bin
[   42.896503] [drm] radeon: power management initialized
[   42.896507] [drm] GART: num cpu pages 131072, num gpu pages 131072
[   42.915405] [drm] PCIE GART of 512M enabled (table at 0x00000000C0040000).
[   42.915440] radeon 0000:01:05.0: WB enabled
[   42.915445] radeon 0000:01:05.0: fence driver on ring 0 use gpu addr 0x00000000a0000c00
[   42.919478] radeon 0000:01:05.0: radeon: MSI limited to 32-bit
[   42.919495] [drm] radeon: irq initialized.
[   42.950634] [drm] ring test on 0 succeeded in 1 usecs
[   42.950879] [drm] ib test on ring 0 succeeded in 0 usecs
[   42.951901] [drm] Radeon Display Connectors
[   42.951903] [drm] Connector 0:
[   42.951905] [drm]   VGA-1
[   42.951906] [drm]   DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
[   42.951909] [drm]   Encoders:
[   42.951909] [drm]     CRT1: INTERNAL_KLDSCP_DAC1
[   42.951911] [drm] Connector 1:
[   42.951912] [drm]   DVI-D-1
[   42.951912] [drm]   HPD1
[   42.951913] [drm]   DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
[   42.951915] [drm]   Encoders:
[   42.951916] [drm]     DFP1: INTERNAL_KLDSCP_LVTMA
[   42.968693] [drm] fb mappable at 0xD0141000
[   42.968699] [drm] vram apper at 0xD0000000
[   42.968701] [drm] size 3145728
[   42.968704] [drm] fb depth is 24
[   42.968705] [drm]    pitch is 4096
[   42.968809] fbcon: radeondrmfb (fb0) is primary device
[   42.993990] Console: switching to colour frame buffer device 128x48
[   42.994982] radeon 0000:01:05.0: [drm] fb0: radeondrmfb frame buffer device
[   43.035372] [drm] Initialized radeon 2.50.0 20080528 for 0000:01:05.0 on minor 0
[   43.064106] EXT4-fs (md1): mounting ext2 file system using the ext4 subsystem
[   43.099664] EXT4-fs (md1): mounted filesystem without journal. Quota mode: none.
[   43.197238] EXT4-fs (dm-0): bad geometry: block count 9522326528 exceeds size of device (2856698880 blocks)
[   43.413872] SVM: TSC scaling supported
[   43.413877] kvm: Nested Virtualization enabled
[   43.413879] SVM: kvm: Nested Paging enabled
[   43.413890] SVM: LBR virtualization supported
[   43.429597] MCE: In-kernel MCE decoding enabled.
[   45.391715] [drm] amdgpu kernel modesetting enabled.
[   45.391813] amdgpu: CRAT table not found
[   45.391816] amdgpu: Virtual CRAT table created for CPU
[   45.391832] amdgpu: Topology: Add CPU node
[   45.737903] r8169 0000:04:00.0 enp4s0: Link is Up - 1Gbps/Full - flow control rx/tx
[   45.737917] IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
[   46.720565] NFSD: Using UMH upcall client tracking operations.
[   46.720571] NFSD: starting 90-second grace period (net f0000000)
[  136.827116] EXT4-fs (dm-0): bad geometry: block count 9522326528 exceeds size of device (2856698880 blocks)
[135143.417824] md: data-check of RAID array md1
[135143.489597] md: delaying data-check of md126 until md1 has finished (they share one or more physical units)
[135340.210882] md: md1: data-check done.
[135340.217461] md: data-check of RAID array md126
[135761.486563] md: md126: data-check done.
root@bolivar:/#
linux
Martin Hope
sloppy
Asked: 2024-11-08 14:12:47 +0800 CST
  • 5

Estou ciente backward-kill-word, mas não faz o que eu quero

hello-world
hello_world
hello/world

Todos os exemplos acima se tornarão linhas vazias depois backward-kill-word, mas eu quero terminar com helloisso.

Isso é possível com o zsh?

zsh
Martin Hope
Idkt
Asked: 2024-11-07 22:54:35 +0800 CST
  • 5

Tenho configurado uma caixa Linux como meu roteador. E minha rede é bem simples neste ponto:

  1. Tenho o roteador conectado à minha caixa de fibra, que autentica com meu ISP usando pppd.
  2. Tenho uma interface ethernet, enp2s0que é o gateway no roteador:
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.1.1.1  netmask 255.255.255.0  broadcast 0.0.0.0
        inet6 fe80::20d:b9ff:fe5a:2f91  prefixlen 64  scopeid 0x20<link>
        ether 00:0d:b9:5a:2f:91  txqueuelen 1000  (Ethernet)
        RX packets 57348511  bytes 31510953543 (29.3 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 116229180  bytes 129467792313 (120.5 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0xf7a00000-f7a1ffff
  1. Tenho uma interface sem fio:
wlp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.1.1.2  netmask 255.255.255.0  broadcast 0.0.0.0
        inet6 fe80::6f0:21ff:fe91:cf90  prefixlen 64  scopeid 0x20<link>
        ether 04:f0:21:91:cf:90  txqueuelen 1000  (Ethernet)
        RX packets 493730  bytes 595814115 (568.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 355275  bytes 344035494 (328.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Com o qual eu gostaria que os clientes se conectassem.

  1. Tenho nftablesalgumas regras básicas de roteamento para direcionar o tráfego.

Meus clientes conseguem se conectar à interface ethernet sem problemas. E internet etc. funcionam como esperado. No entanto, ao conectar à interface sem fio e fazer ping:

-> % ping -I wlp65s0 8.8.8.8
PING 8.8.8.8 (8.8.8.8) from 10.1.1.48 wlp65s0: 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
60 packets transmitted, 0 received, 100% packet loss, time 60428ms

Parece que não recebo nenhuma resposta.

No roteador, vejo o seguinte ao habilitar nftables trace:

trace id 85cd7345 ip filter trace_chain packet: iif "ppp0" ip saddr 8.8.8.8 ip daddr 10.1.1.48 ip dscp af21 ip ecn not-ect ip ttl 61 ip id 0 ip length 84 icmp type echo-reply icmp code net-unreachable icmp id 12 icmp sequence 59 @th,64,96 0xd9d22c6700000000d1790900 
trace id 85cd7345 ip filter forward packet: iif "ppp0" oif "enp2s0" ip saddr 8.8.8.8 ip daddr 10.1.1.48 ip dscp af21 ip ecn not-ect ip ttl 60 ip id 0 ip length 84 icmp type echo-reply icmp code net-unreachable icmp id 12 icmp sequence 59 @th,64,96 0xd9d22c6700000000d1790900 
trace id 3626e73a ip filter trace_chain packet: iif "wlp4s0" ether saddr 48:ad:9a:9d:5e:a4 ether daddr 04:f0:21:91:cf:90 ip saddr 10.1.1.48 ip daddr 8.8.8.8 ip dscp cs0 ip ecn not-ect ip ttl 64 ip id 52040 ip length 84 icmp type echo-request icmp code net-unreachable icmp id 12 icmp sequence 60 @th,64,96 0xdad22c67000000006cd70900 
trace id 3626e73a ip filter forward packet: iif "wlp4s0" oif "ppp0" ether saddr 48:ad:9a:9d:5e:a4 ether daddr 04:f0:21:91:cf:90 ip saddr 10.1.1.48 ip daddr 8.8.8.8 ip dscp cs0 ip ecn not-ect ip ttl 63 ip id 52040 ip length 84 icmp type echo-request icmp code net-unreachable icmp id 12 icmp sequence 60 @th,64,96 0xdad22c67000000006cd70900 
trace id a6c3e760 ip filter trace_chain packet: iif "ppp0" ip saddr 8.8.8.8 ip daddr 10.1.1.48 ip dscp af21 ip ecn not-ect ip ttl 61 ip id 0 ip length 84 icmp type echo-reply icmp code net-unreachable icmp id 12 icmp sequence 60 @th,64,96 0xdad22c67000000006cd70900 
trace id a6c3e760 ip filter forward packet: iif "ppp0" oif "enp2s0" ip saddr 8.8.8.8 ip daddr 10.1.1.48 ip dscp af21 ip ecn not-ect ip ttl 60 ip id 0 ip length 84 icmp type echo-reply icmp code net-unreachable icmp id 12 icmp sequence 60 @th,64,96 0xdad22c67000000006cd70900

O que não consigo entender.

Qualquer dica aqui será muito útil.

Se eu alterar o endereço da interface sem fio para 10.1.2.1, poderei me conectar a outros hosts na LAN/WAN.

networking
Martin Hope
m26a
Asked: 2024-11-07 20:20:47 +0800 CST
  • 7

Considerando o seguinte script:

if [[ -z "$DOWNLOAD_ONLY" || "$DOWNLOAD_ONLY" = *conditions* ]]; then
  function get_condition {
    curl -s "https://conditions.com" | jq '.included[].attributes | select(retracted)' | jq --arg item $2 '. + {item: $item}' > "$1_$2.json"
  }

  function conditions {
    for item in `cat items.json | jq -r '.data[].id'`
    do
      get_condition $1 $item
    done

    jq -s '.' $1_*.json | jq 'reduce .[] as $item (retracted)' > "$1.json"

    rm $1_*.json
  }

  curl "https://items.com" | jq '.' > "items.json"

  for language in cs da de en es fr it nl pl pt sv zh
  do
    conditions $language &
  done

  wait
fi

Posso adicionar &e get_condition $1 $itemligar waitdepois?

bash
Martin Hope
Daniel
Asked: 2024-11-07 14:26:12 +0800 CST
  • 6

Digamos que eu tenha uma partição LUKS que criptografa o sistema de arquivos raiz e cuja chave reside em outro sistema de arquivos.

(mapped-devices (list
    (mapped-device
        (type (luks-device-mapping-with-options #:key-file "/early-mount/luks-key"))
        (source "/dev/sda1")
        (target "operating-system")
    )
))

Como posso instruir o Guix por meio do config.scmarquivo para montar o segundo sistema de arquivos antes da etapa de descriptografia do LUKS?

Tentativa nº 1

Tentei configurar (needed-for-boot? #t)o segundo sistema de arquivos, mas ao inspecionar o script initrd gerado, ele ainda tenta descriptografar antes de montar.

(file-system
    (mount-point "/early-mount")
    (device (file-system-label "early-mount"))
    (type "ext4")
    (needed-for-boot? #t) ; This doesn't move it to #:pre-mount
)

Tentativa nº 2

Também tentei definir a dependência do sistema de arquivos raiz via (filter)e (file-system-mount-point-predicate)mas recebo o erro:

erro: sistemas de arquivos: variável não vinculada

o que faz sentido porque está no meio da definição(file-systems)

(file-systems (cons*
    (file-system ...) ; early-mount definition
    (file-system
        (mount-point "/")
        (device "/dev/mapper/operating-system")
        (type "ext4")
        (dependencies (cons*
            (filter
                (file-system-mount-point-predicate "/early-mount")
                file-systems ; This is currently being defined so it's not available yet
            )
            mapped-devices
        ))
    )
    %base-file-systems
))

Tentativa nº 3

Tentei criar uma variável local via (let)para o segundo sistema de arquivos com a intenção de inseri-la (file-systems)também, (dependencies)mas recebo o erro:

erro: (let ...): especificador de campo inválido

(let
    (
        (early-mount
            (file-system
                (mount-point "/early-mount")
                (device (file-system-label "early-mount"))
                (type "ext4")
                (needed-for-boot? #t)
            )
        )
    )
    (file-systems (cons*
        early-mount
        (file-system
            (mount-point "/")
            (device "/dev/mapper/operating-system")
            (type "ext4")
            (dependencies (cons*
                early-mount
                mapped-devices
            ))
        )
        %base-file-systems
    ))
)

Tentativa nº 4

Em seguida, tentei repetir a segunda (file-system)entrada do sistema de arquivos e isso realmente me permitiu implantar a configuração:

(file-systems (cons*
    (file-system ...) ; early-mount definition
    (file-system
        (mount-point "/")
        (device "/dev/mapper/operating-system")
        (type "ext4")
        (dependencies (cons*
            (file-system ...) ; early-mount definition, copy/pasted
            mapped-devices
        ))
    )
    %base-file-systems
))

no entanto, isso tenta me solicitar a senha durante a inicialização, o que me leva a acreditar que não foi possível montar /early-mountantes de tentar abrir o LUKS.

boot
Prev
Próximo