Allan McRae schrieb:

From experience... not necessarily. I got into X without doing that although I had no tty's. But exactly how do we deal with this? Post a new item before the move?

Fix it: apply a cool sed line that seds vc/$NUMBER to tty$NUMBER on inittab. This will not destroy anything, but potentially fix it.

On Sat, Jul 18, 2009 at 16:22, Dan McGee wrote:

On Sat, Jul 18, 2009 at 8:02 AM, Thomas Bächler wrote:

...

Allan McRae schrieb:

...

 From experience...  not necessarily.  I got into X without doing that although I had no tty's. But exactly how do we deal with this?  Post a new item before the move?

Fix it: apply a cool sed line that seds vc/$NUMBER to tty$NUMBER on inittab. This will not destroy anything, but potentially fix it.

Those of us not using X on certain machines would get burned here, so its definitely worth attempting to fix...

I'm not a fan of automatically fixing users' config files, post_upgrade message seems enough to me. Anyway, we've got the first bugreport about a broken system: http://bugs.archlinux.org/task/15567 Seems like some users don't really pay much attention to upgades. -- Roman Kyrylych (Роман Кирилич)