how to autologin in xdm?
Dan Jacobson
and passwd each session?
Vincent Zweije
<jid...@jidanni.org> wrote:
|| How can one do autologin in xdm so one doesn't have to type username
|| and passwd each session?
You don't.
You run an X session of your choice using startx (or straight xinit)
from an rc script.
However, since this is about security, don't do it unless you know what
you're doing. And given your question, you probably shouldn't. But it's
impossible to tell for lack of background information.
Ciao. Vincent.
--
Vincent Zweije <zwe...@xs4all.nl> | "If you're flamed in a group you
<http://www.xs4all.nl/~zweije/> | don't read, does anybody get burnt?"
[Xhost should be taken out and shot] | -- Paul Tomblin on a.s.r.
Thomas Otto
> <jid...@jidanni.org> wrote:
>
> || How can one do autologin in xdm so one doesn't have to type username
> || and passwd each session?
>
> You don't.
But you can if you use kdm instead of xdm (break you system on your own
risk!) Allow this by hacking the kdmrc directy or via kcontrol.
> You run an X session of your choice using startx (or straight xinit)
> from an rc script.
>
> However, since this is about security, don't do it unless you know what
> you're doing. And given your question, you probably shouldn't. But it's
> impossible to tell for lack of background information.
I can only second that!
Well, I'm just giving you what you asked for - "more rope" :)
-Thomas
Dan Jacobson
> || and passwd each session?
> You don't.
< But you can if you use kdm instead of xdm (break you system on your own
< risk!) Allow this by hacking the kdmrc directy or via kcontrol.
But since I am just a humble icewm user, I already apt-got xdm and
banished all the kde glitz away because I never use it.
Plus keeping it up to date is modem overflow.
> You run an X session of your choice using startx (or straight xinit)
> from an rc script.
All I know is ~/.xsession is run after login.
> However, since this is about security, don't do it unless you know what
> you're doing. And given your question, you probably shouldn't. But it's
> impossible to tell for lack of background information.
< I can only second that!
< Well, I'm just giving you what you asked for - "more rope" :)
On my island hilltop, no other linux users are near.
Must I accept the glitz of "gdm" as the only other choice?
Hugo Lovhoiden
What I don't get is why you want to use xdm when you aren't going to use
it? I mean, having xdm auto-login is precisely the opposite of what it was
designed to do: Give you a graphical login prompt.
Use runlevel 3 and add 'su - <your user> -c startx' to
/etc/init.d/rc.local or (if using inittab) change
"x:5:respawn:/etc/X11/prefdm -nodaemon" to "x:5:respawn:su - <your user>
-c startx".
--
Mvh Hugo
Wayne Throop
: What I don't get is why you want to use xdm when you aren't going to
: use it? I mean, having xdm auto-login is precisely the opposite of
: what it was designed to do: Give you a graphical login prompt.
Not quite; the man page says
Xdm provides services similar to those provided by init, getty and
login on character terminals: prompting for login name and password,
authenticating the user, and running a ``session.''
So. One of the things it does is "running a session".
It doesn't seem to strange to expect it to be able to
arrange an initial default session when first started,
and present a login pompt when that session ends.
Mind you, getty doesn't provide this either; nevertheless,
it seems a reasonablething to want to do, and part of xdm's
job is to "run a session".
Right now, you'd have to do the initial session by running the server
and various session setup miscelania/administrivia from an RC file,
and then start xdm when that session ends. I imagine most folks
didn't mind typing "foo\nbar\n" one "extra" time every boot, so
the demand wasn't there until more recent muble-dm tools.
Wayne Throop thr...@sheol.org http://sheol.org/throopw
Hugo Lovhoiden
> : "Hugo Lovhoiden" <hu...@office-center.nospam.invalid> What I don't get
> : is why you want to use xdm when you aren't going to use it? I mean,
> : having xdm auto-login is precisely the opposite of what it was
> : designed to do: Give you a graphical login prompt.
>
> Not quite; the man page says
>
> Xdm provides services similar to those provided by init, getty and
> login on character terminals: prompting for login name and password,
> authenticating the user, and running a ``session.''
>
> So. One of the things it does is "running a session".
Precisely. _One_ of the things. It is also supposed to prompt you for a
username and a password first. Which it does. 'Cause if you don't need a
login prompt you could run xinit directly (or using the startx shell
wrapper, which is easier) and you wouldn't need xdm.
I am aware that both gdm and kdm provides such services in this day and
age, but I still find it a bit much to ask from bare bones xdm. Like the
man page says, it's only supposed to mimick getty, but on an X server.
> Mind you, getty doesn't provide this either; nevertheless, it seems a
> reasonablething to want to do, and part of xdm's job is to "run a
> session".
>
> Right now, you'd have to do the initial session by running the server
> and various session setup miscelania/administrivia from an RC file, and
> then start xdm when that session ends. I imagine most folks didn't mind
> typing "foo\nbar\n" one "extra" time every boot, so the demand wasn't
> there until more recent muble-dm tools.
Where xdm came from you didn't reboot much. You had servers and you had
X-terminals. Next to no one logged in at a console for anything but
systems maintenance. But I'd better stop now, I'm starting to sound old
and nostalgic (and getting a nasty suspicion that I actually am both...). Thing
is, gdm is kinda supposed to give you just that extra level of both flash
and customization-- so xdm won't have to...
I still think startx would do the trick...
--
Mvh Hugo
Dan Jacobson
but Xlib: connection to ":0.0" refused by server is what I got.