[arch-general] login fails after update
Hello all, I did a complete upgrade following the instructions w.r.t. the /lib symlink, and indeed ended up with pacman -Su saying 'nothing to do' and /lib being a symlink. On rebooting I get the login prompt on tty1..6, but after entering a login nothing happens (no passwd prompt) and after a few seconds the screen is cleared and the login prompt returns. Any ideas ? -- FA A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-delusion, nerd hubris and hysterically inflated market opportunities. (Cory Doctorow)
On 15/07/12 at 08:35P, Fons Adriaensen wrote:
Hello all,
I did a complete upgrade following the instructions w.r.t. the /lib symlink, and indeed ended up with pacman -Su saying 'nothing to do' and /lib being a symlink.
On rebooting I get the login prompt on tty1..6, but after entering a login nothing happens (no passwd prompt) and after a few seconds the screen is cleared and the login prompt returns.
Any ideas ?
-- FA
A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-delusion, nerd hubris and hysterically inflated market opportunities. (Cory Doctorow)
Boot into single user mode and look at /var/log/auth.log. It should tell you what the problem is. -- Dave.
On Sun, Jul 15, 2012 at 10:11:28AM +0100, Dave Morgan wrote:
Boot into single user mode and look at /var/log/auth.log. It should tell you what the problem is.
Seemed some things were missing, one of them being login.... Which is *very strange* ... Fortunately I could afford to just dump this system and do a fresh netinstall - all OK now. It was installed something like half a year ago and not used at all before I tried the upgrade. So I really wonder if the late 2011 install image followed by a pacman -Syu still works, as far as I can tell it doesn't, and only a netinstall will. Ciao, -- FA A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-delusion, nerd hubris and hysterically inflated market opportunities. (Cory Doctorow)
On 15/07/12 at 08:40pm, Fons Adriaensen wrote:
On Sun, Jul 15, 2012 at 10:11:28AM +0100, Dave Morgan wrote:
Boot into single user mode and look at /var/log/auth.log. It should tell you what the problem is.
Seemed some things were missing, one of them being login.... Which is *very strange* ... Fortunately I could afford to just dump this system and do a fresh netinstall - all OK now.
It was installed something like half a year ago and not used at all before I tried the upgrade. So I really wonder if the late 2011 install image followed by a pacman -Syu still works, as far as I can tell it doesn't, and only a netinstall will.
Ciao,
-- FA
A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-delusion, nerd hubris and hysterically inflated market opportunities. (Cory Doctorow)
The most likely reason for /bin/login being missing is that the upgrade was forced. -- Dave.
On Mon, Jul 16, 2012 at 04:42:28AM +0100, Dave Morgan wrote:
The most likely reason for /bin/login being missing is that the upgrade was forced.
No, it was not. As already said I followed the instructions which clearly stated not to use --force. Ciao, -- FA A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-delusion, nerd hubris and hysterically inflated market opportunities. (Cory Doctorow)
On Jul 16, 2012 12:17 PM, "Fons Adriaensen" <fons@linuxaudio.org> wrote:
On Mon, Jul 16, 2012 at 04:42:28AM +0100, Dave Morgan wrote:
The most likely reason for /bin/login being missing is that the upgrade was forced.
No, it was not. As already said I followed the instructions which clearly stated not to use --force.
I have no idea how this happened, but reinstalling util-linux should fix it. -t
On Mon, Jul 16, 2012 at 12:20:10PM +0200, Tom Gundersen wrote:
On Jul 16, 2012 12:17 PM, "Fons Adriaensen" <fons@linuxaudio.org> wrote:
On Mon, Jul 16, 2012 at 04:42:28AM +0100, Dave Morgan wrote:
The most likely reason for /bin/login being missing is that the upgrade was forced.
No, it was not. As already said I followed the instructions which clearly stated not to use --force.
I have no idea how this happened, but reinstalling util-linux should fix it.
I completely new netinstall fixed it :-). Maybe the system was just too old, it was the only one not kept up to date. Since the latest core install image (about 11 months ago), there have been several changes that required a manual intervention during a routine update, the /lib thing is just the latest one. Each of them was clearly announced and documented, and usually involved upgrading some packages separately either before the rest, or after it using --ignore first, and at least in one case using --force was the recommended way to go. Each of these upgrades worked well separately and were no big deal for anyone using Arch for some time. But imagine the situation of a new user who has just done a core install, and is told to do -Syu after the first reboot, facing all these manual steps together. I don't think you can expect such a new user to do the right thing, if it is possible at all. Which is not a good thing for Archlinux' name and fame. I suspect we need new install images ASAP. Ciao, -- FA A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-delusion, nerd hubris and hysterically inflated market opportunities. (Cory Doctorow)
On Jul 16, 2012 1:02 PM, "Fons Adriaensen" <fons@linuxaudio.org> wrote:
On Mon, Jul 16, 2012 at 12:20:10PM +0200, Tom Gundersen wrote:
On Jul 16, 2012 12:17 PM, "Fons Adriaensen" <fons@linuxaudio.org> wrote:
On Mon, Jul 16, 2012 at 04:42:28AM +0100, Dave Morgan wrote:
The most likely reason for /bin/login being missing is that the
upgrade
was forced.
No, it was not. As already said I followed the instructions which clearly stated not to use --force.
I have no idea how this happened, but reinstalling util-linux should fix it.
I completely new netinstall fixed it :-).
Maybe the system was just too old, it was the only one not kept up to date.
Since the latest core install image (about 11 months ago), there have been several changes that required a manual intervention during a routine update, the /lib thing is just the latest one. Each of them was clearly announced and documented, and usually involved upgrading some packages separately either before the rest, or after it using --ignore first, and at least in one case using --force was the recommended way to go. Each of these upgrades worked well separately and were no big deal for anyone using Arch for some time.
But imagine the situation of a new user who has just done a core install, and is told to do -Syu after the first reboot, facing all these manual steps together. I don't think you can expect such a new user to do the right thing, if it is possible at all. Which is not a good thing for Archlinux' name and fame. I suspect we need new install images ASAP.
I agree. We are currently in the final stages of testing a new iso. I'm also advocating we drop the core instal as it is causing too many problems in case it is outdated.
Ciao,
-- FA
A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-delusion, nerd hubris and hysterically inflated market opportunities. (Cory Doctorow)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
I agree. We are currently in the final stages of testing a new iso. I'm also advocating we drop the core instal as it is causing too many problems in case it is outdated.
This seems to be a step in the right direction, works smoothly for other rolling release distributions (Gentoo and the likes). The only thing that would kind of prevent the breakage would be the quick release of a new iso. I do not know whether this is possible. Greetings, Christoph -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJQBANXAAoJEOGIwUZuUxpnWbQP/RR8bgShb2Evv0Ly3zQKZHtr BPYZ5zZMARqG7auHbUSR+vp5VdPouDiqfk46PaIhd1CkFWmAa7wYOeZKB71Qu+Ym TlC0TpVOhv0phpo1J3vyyiRNsUKVo1OsO1oSQcLRm593cKEYw7xKT4ymPT3HRQeL R9ktiQmHbMNYmLpYcLICcLGR9cRxoJGZAFVwQ9yz/O65izgPU/h6x0JMh4xyFmow VFW0xSuwbe0VuSB79YS5rZIBIyH1yAoSYSbW2CMOhkkVTwn61rpQtHcfKy82jVtw QasFgKd8k0qlE88YtIb2A5WP4h7acl+zlryQ1N6nxIAUCmqHVaYmUH9Ff/a14tJt UKk8ZUkfpKQ5njeexJ+XPZsjqyoIn0k1aqpsUhDFNSufC524sZGVuvqBLfM8DHpp CYB6FTRsUjmOqihB/RSynz/mkApKvpAapThOQkBJik3lqx7NZuubOm9fSPNMFhX0 Xl2gs6BwkSqfoVbJo9hcz5T+TcJJJuL6hQV/gqzbXce6DmQIISnB/VbMbrS9yOEB hJ5Dwf9iBqd27+zgxGrcfyF/YJpGUG4AwYpnWIwkTITGKqTjrcsySMMnXQkjmCZl 5aGPMEahhJ7OedvCdoxzsvDNghQ1Iqwp4L+Kh1dn4zc2RkWQB3kCGyQEHhg59Lv8 hgOubCfIO4+VKyb1laE/ =k74j -----END PGP SIGNATURE-----
On Mon, Jul 16, 2012 at 2:04 PM, Christoph Vigano <mail@cvigano.de> wrote:
The only thing that would kind of prevent the breakage would be the quick release of a new iso. I do not know whether this is possible.
We hope to have a new process in place so that very frequent iso releases are possible. However, I think we still have the issue that people will be using install media they downloaded some time ago and expecting it (not unreasonably) to work well. -t
I think we still have the issue that people will be using install media they downloaded some time ago and expecting it (not unreasonably) to work well.
Worked fine for me and with AIF auto install on Jun 6th. I guess as with many things it could last days or perhaps a year one time. -- ________________________________________________________ Why not do something good every day and install BOINC. ________________________________________________________
On Mon, Jul 16, 2012 at 6:18 AM, Tom Gundersen <teg@jklm.no> wrote:
I agree. We are currently in the final stages of testing a new iso. I'm also advocating we drop the core instal as it is causing too many problems in case it is outdated.
what if we only built net-install images, and "core" images were simply the netinstall image + appended partition/image containing the repo snapshots (or is this how it's done already)? ... then we can simply append the repos to pacman's CacheDir list: CacheDir = /var/cache/pacman/pkg/ CacheDir = /vmm/org-archlinux-mirror-1/pool/packages/ CacheDir = /vmm/org-archlinux-mirror-1/pool/community/ this has several advantages: - pull updated packages (net available) - use cached packages only (net unavailable) - zero-copy (vs. spinning up a localhost server, etc). - properly cache incoming packages (one CacheDir is r/w) - `/vmm/*` (or whatever) is just a simple squashfs mount my local server/mirror does exactly this -- the above is a verbatim excerpt. in my setup, the cache dirs are read-only --bind mounted into numerous virtual machines. working well for ~18 months, if not longer. -- C Anthony
participants (6)
-
C Anthony Risinger
-
Christoph Vigano
-
Dave Morgan
-
Fons Adriaensen
-
Kevin Chadwick
-
Tom Gundersen