| 1 |
On Thu, 2006-07-20 at 22:29 +0000, Alex wrote: |
| 2 |
> You said the code was wrong. does it mean it does now auto-login? (or is |
| 3 |
> it an interpretation failure again?) |
| 4 |
|
| 5 |
Yes and no. |
| 6 |
|
| 7 |
What it *should* do is auto-login to the command line as root, just like |
| 8 |
a CD that is not X-based will do. However, root's /root/.bashrc should |
| 9 |
be setup to do the following: |
| 10 |
|
| 11 |
#1. Determine if "nox" appears on the command line, if it does, abort |
| 12 |
#2. Determine if X is even installed |
| 13 |
#3. Look for /etc/startx (created by catalyst automatically for the |
| 14 |
"generic-livecd" livecd/type |
| 15 |
#4. Remove /etc/startx, so it doesn't try to auto-start X repeatedly |
| 16 |
#5. Start X as the first user defined in livecd/users using "su" |
| 17 |
#6. Spit out the MOTD again so you can see it when you switch back to |
| 18 |
the console |
| 19 |
|
| 20 |
Now, this is what it is *designed* to do. If it doesn't do this, then |
| 21 |
it's a bug and it needs to be fixed in the code. |
| 22 |
|
| 23 |
What this will *not* do is setup any kind of auto-login via any display |
| 24 |
manager. If you want the display manager configured, you need to do so |
| 25 |
yourself. The reason for this is actually pretty simple, we've found |
| 26 |
that people's tastes when it comes to how their display manager looks is |
| 27 |
much more rabid than we'd like. Using "startx" and allowing the user to |
| 28 |
customize via *either* livecd/xsession to start a particular session or |
| 29 |
livecd/xinitrc to start something that isn't even defined by a session |
| 30 |
gives the user the maximum flexibility, without making it overly |
| 31 |
complex. |
| 32 |
|
| 33 |
-- |
| 34 |
Chris Gianelloni |
| 35 |
Release Engineering - Strategic Lead |
| 36 |
x86 Architecture Team |
| 37 |
Games - Developer |
| 38 |
Gentoo Linux |
Archives