Arch upgrade note

1. Pacman-syu Error
Error: gpgme error: No dataerror: failed to update Community (invalid or synchronized upted database (PGP signature) error: failed to synchronize any databaseserror: failed to init transaction (invalid or invalid upted database (PGP signature ))

Solution: cancel all signatures in/etc/Pacman. conf.
Siglevel = never
After adjustment, it is normal. Of course, this is not a good solution.

2. Proxy Settings
1. Because there is ISA, a second-level proxy needs to be set and cntlm is used to verify Isa.
Set proxy
[Root @ arch-G ~] # Export ftp_proxy = "http: // DS \ gaohu: ***** @ localhost: 3128"
[Root @ arch-G ~] # Export http_proxy = "http: // DS \ gaohu: ***** @ localhost: 3128"
[Root @ arch-G ~] # Export https_proxy = "http: // DS \ gaohu: *** @ localhost: 3128"

If the domain user and password are not added, the ISA 407 error may be triggered.

Then the upgrade is normal.

= 2013.01.26
Sudo RM/etc/passwd accidentally because of updating the pacnew configuration file. pacnew/etc/passwd (the hacker originally wanted a music video), which was hard to generate and cannot be cleaned up.
Very good. It is said that passwd-to passwd can be restored, and there is still a glimmer of life, but sudo or Su-, prompting users who do not know, there is no way to do it.
Restart, edit the grub2 startup item, and add RW init =/bin/Bash to Linux/vmlinuz.... It will start in shell, and then copy passwd-to passwd,
CP/etc/passwd-/etc/passwd, You need to reset the permission here, because passwd-is root RW and others do not have the permission; adjust/etc/passwd, add r permission to everyone, restart, OK,
Be careful. I almost got down...