You are not logged in.
Pages: 1
Just fired up my old laptop that has been sitting dormant for ages and hit pacman -Qi kernel26 to see when I last upgraded, 20 months ago, then hit pacman -Syu.
So far so good. It upgraded pacman first without incident, and once I moved the pacman.conf.pacnew to its proper place and ran pacman -Syu, it was just a question of hitting 'yes' a score of times on replacement packages and conflicting packages, before being faced with a choice to download some 600MB of new packages worth, requiring about 420MB additional space to be up to date.
Currently still downloading. Will post a few screenshots afterwards and let you know how it all went. It's interesting to see though, how much my xfce system has progressed since then. Think I'll start using it again as a test machine and backup.
Offline
Well, it seems all did no go as smooth as hoped. Just did the first reboot and X won't load. GDM crashes with the following output:
WARNING **: failed to acquire org.gnome.DisplayManager
WARNING **: could not acquire name; bailing out
WARNING **: GdmDisplay lasted 1,698960 seconds
WARNING **: GdmDisplayFactory: maximum number of x display failures reachesL check X server log for details
any takers?
Offline
b9anders: don't know the answer to your particular issue, but if you are going to upgrade from a very old system, I suggest reading throug the news entries to then as there will (regrettably) be some issues to sort out...
Offline
I think the OP knows that. This looks to me like more of a fun little experiment, like poking a sleeping bear with a sharp stick.
Offline
anokusa has the right of it. I basically just want to see if I can get it somewhat up and running after such a long time without upgrades (and also knowing there have been some fairly radical changes to how arch works since then).
If not, it's a wipe and start over.
Offline
radical changes...kernel26 to linux
begin of the usr mergin
initcpio aditions and changes
moduleconf (or whatever the name) remplaced by kmod
new base packages and new base-devels
big change in rc.conf
deprecated of hal
begin of udev2
and this is the modt criticals updates..
is possible bur requiere a LOT of user interference and patience
Well, I suppose that this is somekind of signature, no?
Offline
Well your arch setup seems fine, just that godam thing ... I mean that gdm thing is trouble.
If it were me, I'd cut gdm out of "the circuit" and boot to rl 3 and get gnome up and running via startx/xinit. If/when that's working there's only that one problem left with gdm. Solution: get rid of it ;o)
Or get rid of it, and reinstall just that, not the whole system.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Well your arch setup seems fine, just that godam thing ... I mean that gdm thing is trouble.
If it were me, I'd cut gdm out of "the circuit" and boot to rl 3 and get gnome up and running via startx/xinit. If/when that's working there's only that one problem left with gdm. Solution: get rid of it ;o)
Or get rid of it, and reinstall just that, not the whole system.
Although it's more of a workaround for OP's issue, I have to agree. I use xinit/startx too, it's just much simpler and works just as well.
Offline
Now I feel like installing Arch in a VM and letting it lay dormant for two years.
Offline
Now I feel like installing Arch in a VM and letting it lay dormant for two years.
Grabbing an Arch core install from this days and installing it after that time has passed sounds more disk-efficient to me
Best Testing Repo Warning: [testing] means it can eat you hamster, catch fire and you should keep it away from children. And I'm serious here, it's not an April 1st joke.
Offline
Indeed, but half the moon would have to fall from the sky and smash Thailand to make me worry about free disk capacity :-)
Offline
This thread reminds me that I do have an old Arch linux laptop that I haven't updated in 8 months (at least). Should be fun to try updating it now.
Although I use i3 on it - it cannot run xfce let alone gnome (256MB RAM PIII). I think the only issue should be the changes in the i3config file.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
This thread reminds me that I do have an old Arch linux laptop that I haven't updated in 8 months (at least). Should be fun to try updating it now.
Although I use i3 on it - it cannot run xfce let alone gnome (256MB RAM PIII). I think the only issue should be the changes in the i3config file.
I did my office server this afternoon which wasn't updated in about a year, no (serious) problems. :-)
ᶘ ᵒᴥᵒᶅ
Offline
Same here. Updated server after 9 months, no big issues. But I read the old news beforehand, taking away some of the 'fun' .
Offline
b9anders: don't know the answer to your particular issue, but if you are going to upgrade from a very old system, I suggest reading throug the news entries to then as there will (regrettably) be some issues to sort out...
Running "pacman -S base base-devel --needed" would have been a good idea as well.
Offline
Now I feel like installing Arch in a VM and letting it lay dormant for two years.
I suppose another experiment could be to install one of the really, really early Arch ISOs in a VM and try to update it. I'm not even sure if it'd be possible, honestly. Too many drastically huge updates, probably.
Currently running Arch on a Samsung Chromebook Pro (dual booted with ChromeOS), and various VPSes and Docker containers.
Offline
Awebb wrote:Now I feel like installing Arch in a VM and letting it lay dormant for two years.
I suppose another experiment could be to install one of the really, really early Arch ISOs in a VM and try to update it. I'm not even sure if it'd be possible, honestly. Too many drastically huge updates, probably.
"Exercise left to the reader"
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
If you're seeing:
WARNING **: failed to acquire org.gnome.DisplayManager
WARNING **: could not acquire name; bailing out
WARNING **: GdmDisplay lasted 1,698960 seconds
WARNING **: GdmDisplayFactory: maximum number of x display failures reachesL check X server log for details
After an update, do a
df -h
. I bet you'll find your root partition at 100%. The filesystem applies a 'pad' to the declated filesystem sizes to ensure that the system doesn't get completely locked by entirely filling a partition (you can adjust the size by tuning your filesystem). Run as root, pacman will happily eat into this, X won't. Therefore, X can't write to the filesystem and so refuses to start.
It's the new packages in the pacman cache that do it.
This happens to me regularly. Either deleting old packages from the pacman cache or moving it to a partition with more space solves the issue.
D.
Last edited by DanGray (2012-06-24 03:17:20)
Offline
Pages: 1