Problems during Arch64 installation and configuration

Before installing Arch64, the 32-bit Arch/etc and/srv are backed up with tar. www.2cto. com1: the fstab for backing up 32-bit Arch is different from the UUID on the new system, which leads to an error in the configuration file content of grub2, but grub2 is correctly installed on MBR, so let's see...
Before installing Arch64, the 32-bit Arch/etc and/srv are backed up with tar. at www.2cto.com 1, the fstab for backing up 32-bit Arch is different from the UUID on the new system, which leads to an error in the configuration file content of grub2, but grub2 is correctly installed on MBR, so we can see the grub2 boot menu, but after selecting it, we will not find the kernel file and file system, and then use the installation disc to generate a copy with genfstab again, use grub-mkconfig to generate a new grub. solve the problem after cfg. 2. release/etc/passwd,/etc/shadow,/etc/group,/etc/gshadow in the backup file to the new system, saving effort on creating users and groups. 3,/etc/rc. conf is also backed up. the Daemon line has a few software not installed. temporarily add '! 'In front. 4. xorg does not need to be configured. after openbox and related software are installed, mount the previous/home, startx directly enters the desktop www.2cto.com 5, and fcitx environment variables are written in. xinitrc,/etc/gtk-2.0/gtk. the immodules file has also been modified. fcitx is written in. config/openbox/autostart. sh, the GTK program cannot use fcitx when entering the desktop, and there is no problem when the QT software starts fcitx. fcitx is written in. in xinitrc, the fcitx icon on the tint2 taskbar cannot be correctly displayed, but can be used. or it is not started in these two files. it is okay to use gmrun (Alt + F2) or run fcitx on the openbox desktop. this is inconvenient. 6. you can delete/etc/fonts/conf if the flash code on firefox is garbled. d/49-sans-serif.conf. you can also edit and modify the file, but it is easier to delete it.