Also, this move was publicized in the forums, IRC topic, mailing list and
front-page news.
Seriously, if you're updating a months-old system, you'd better go over the
front-page news, at the very least.
Gesh
On Fri, Mar 15, 2013 at 11:38 PM, Rodrigo Rivas rodrigorivasco...@gmail.com
wrote:
[2013-03-17 15:42:55 +0200] Gesh hseG:
Also, this move was publicized in the forums, IRC topic, mailing list and
front-page news.
Seriously, if you're updating a months-old system, you'd better go over the
front-page news, at the very least.
Top-posting again?!?
Feel free to spend five more
On 03/12/2013 04:13 PM, David C. Rankin wrote:
After working with the chroot error a bit I stumbled across the fact that
link
for /lib was missing. After manually creating the link again, chroot worked
like
a champ. I don't know how much of the system got borked as a result, but a
fresh
On Fri, Mar 15, 2013 at 5:32 PM, David C. Rankin
drankina...@suddenlinkmail.com wrote:
On 03/12/2013 04:13 PM, David C. Rankin wrote:
There needs to be a check in the current update that checks to see whether
the
/lib link can safely be removed -- before it is removed by whatever package
On 13 March 2013 04:07, Martti Kühne mysat...@gmail.com wrote:
as sysadmin of your archlinux system you should take care of pacnew files
in your filesystem. I myself run
# find / -xdev -regextype posix-egrep -regex '.*\.pac(new|old|save)' | less
Regarding .pacnew files, there is an utility
On 03/06/2013 08:24 PM, Ross Hamblin wrote:
On 07/03/13 14:32, David C. Rankin wrote:
Guys,
Attempting to fix the test box that updating left unable to boot, I cannot
chroot to fix the system. I've booted from the install medium and done the
normal mount of the existing system under /mnt:
6 matches
Mail list logo
