You are not logged in.
Ok, I have been testing an arhc linux setup for a cloud webserver setup on AWS for the last month or so. Until now everything went without a hitch. Today I spin up a new instance to test the updates and I can't get it to come up after rebooting. I'm not very well versed in EC2's quirks and couldn't do much in form of debugging the AMI.
The hits on pacman -Syyu are:
Replace libusb with core/libusbxwhich apparently doesn't affect the behavior
and the following packages are marked for update:
apache-2.2.22-4 bison-2.5.1-1 dovecot-2.1.7-4 fakeroot-1.18.4-1
filesystem-2012.6-2 glibc-2.15-11 icu-49.1.2-1
initscripts-2012.06.1-1 krb5-1.10.2-1 libmysqlclient-5.5.25-1
linux-3.3.8-1 linux-api-headers-3.3.8-1 mkinitcpio-0.9.2-1
mysql-5.5.25-1 mysql-clients-5.5.25-1 pinentry-0.8.1-4
psmisc-22.17-1 rsync-3.0.9-3 sqlite-3.7.13-1 systemd-tools-185-1I am aware of the filesystem issue so the actual update command is as advised:
pacman -Syu --ignore filesystem && pacman -S filesystem --forceEDIT: I have done the Linux update separately and it is pretty clear that something crashes the vm in either linux-3.3.8-1 or linux-api-headers-3.3.8-1
Any news on that is welcome.
Last edited by justforgetme (2012-06-13 15:13:30)
$> man life
No manual entry for `life'
$> nvm...
Offline