O Udev não pode criar regras persistentes, leia somente o sistema de arquivos

1

Depois de atualizar para o 15.04, experimentei drivers diferentes para minha placa wireless, então pensei em atualizar as regras do udev e excluir o arquivo /etc/udev/rules.d/70-persistent-net.rules , pensando que ele seria recriado na inicialização. Não deu e deu o seguinte erro

systemctl status udev-finish.service -l
● udev-finish.service - Copy rules generated while the root was ro
   Loaded: loaded (/lib/systemd/system/udev-finish.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2015-04-26 22:11:29 CEST; 49s ago
  Process: 361 ExecStart=/lib/udev/udev-finish (code=exited, status=2)
 Main PID: 361 (code=exited, status=2)

Apr 26 22:11:29 MacBook systemd[1]: Starting Copy rules generated while the root was ro...
Apr 26 22:11:29 MacBook systemd[1]: udev-finish.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 26 22:11:29 MacBook systemd[1]: Failed to start Copy rules generated while the root was ro.
Apr 26 22:11:29 MacBook systemd[1]: Unit udev-finish.service entered failed state.
Apr 26 22:11:29 MacBook systemd[1]: udev-finish.service failed.
Apr 26 22:11:29 MacBook udev-finish[361]: /lib/udev/udev-finish: 6: /lib/udev/udev-finish: cannot create /etc/udev/rules.d/70-persistent-net.rules: Read-only file system

Então, como posso tornar o sistema gravável novamente?

    
por Peter Raeves 26.04.2015 / 22:17

1 resposta

1

Eu alterei o arquivo /lib/systemd/system/udev-finish.service para incluir basic.target em sua configuração Depois , o que parece fazer o truque para mim:

[Unit]
Description=Copy rules generated while the root was ro
DefaultDependencies=no
After=basic.target systemd-udevd.service systemd-udev-settle.service

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/lib/udev/udev-finish
    
por Carsten Tolkmit 05.05.2015 / 11:32