[arch-dev-public] [signoff] vc/* -> tty* transition
Signoffs needed for the following packages: filesystem 2009.07-1 initscripts 2009.07-2 (what I tagged as -1 did not shutdown correctly) syslog-ng 3.0.3-2 udev 141-4 Allan
Allan McRae schrieb:
Signoffs needed for the following packages:
filesystem 2009.07-1 initscripts 2009.07-2 (what I tagged as -1 did not shutdown correctly) syslog-ng 3.0.3-2 udev 141-4
The static nodes in /lib/udev/devices do not match the rules: /lib/udev/devices has loop/0 and a symlink loop0 -> loop/0, while the rules generate loop0 as a block device. I commited the necessary PKGBUILD changes to the udev trunk.
Allan McRae schrieb:
Signoffs needed for the following packages:
filesystem 2009.07-1 initscripts 2009.07-2 (what I tagged as -1 did not shutdown correctly) syslog-ng 3.0.3-2 udev 141-4
There's another problem: If the user doesn't change vc/? to tty? in inittab, a reboot will fail.
Thomas Bächler wrote:
Allan McRae schrieb:
Signoffs needed for the following packages:
filesystem 2009.07-1 initscripts 2009.07-2 (what I tagged as -1 did not shutdown correctly) syslog-ng 3.0.3-2 udev 141-4
There's another problem: If the user doesn't change vc/? to tty? in inittab, a reboot will fail.
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? Allan
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 8:02 AM, Thomas Bächler<thomas@archlinux.org> 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... -Dan
On Sat, Jul 18, 2009 at 16:22, Dan McGee<dpmcgee@gmail.com> wrote:
On Sat, Jul 18, 2009 at 8:02 AM, Thomas Bächler<thomas@archlinux.org> 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 (Роман Кирилич)
participants (4)
-
Allan McRae
-
Dan McGee
-
Roman Kyrylych
-
Thomas Bächler