X on tty1 in Rawhide/F10

[Dan Nicholson]

2008/10/28 Will Woods <wwoods at redhat.com>:
> On Mon, 2008-10-27 at 17:07 -0400, Will Woods wrote:
>> Hi folks,
>>
>> If you're running F10Beta/Rawhide, you may have noticed already, but I
>> wanted to make sure everyone knows this is intentional:
>>
>> X HAS MOVED FROM VT7 TO VT1.
>
> OK look. If you absolutely cannot deal with this DRASTIC change in
> behavior:
>
> 1) add "start on started prefdm" to /etc/event.d/tty1
> 2) (GNOME) edit /etc/gdm/custom.conf and add
>     FirstVT=7
>   to the top of the file. Or:
>   (KDE) edit /etc/kde/kdm/kdmrc and set
>     ServerVTs=-7
>     ConsoleTTYs=tty1,tty2,tty3,tty4,tty5,tty6
> 3) Sigh contentedly at the restoration of your precious tradition.
>
> If you use runlevel 3 + startx, nothing has changed.

I don't think this is quite how it works in the plymouth/gdm new world
order. Especially since newer gdm doesn't support FirstVT anymore.

plymouth drops a file /var/spool/gdm/force-display-on-active-vt, which
gdm checks for when starting its slave. Instead, I think this can all
be handled from upstart with a preference FORCEACTIVEVT in
/etc/sysconfig/desktop (names/files open for suggestion).

Attached is an untested patch which:

1. Writes /var/spool/gdm/force-display-on-active-vt from prefdm if
$FORCEACTIVEVT = yes
2. Starts getty on tty1 in rc5 if $FORCEACTIVEVT=no

So, you can get the old behavior back with

echo 'FORCEACTIVEVT=no' >> /etc/sysconfig/desktop

This requires that writing /var/spool/gdm/force-display-on-active-vt
is removed from plymouth.

--
Dan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: initscripts-old-active-vt.patch
Type: text/x-diff
Size: 1109 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-devel-list/attachments/20081028/078b72d4/attachment.bin>