From: James Miller <jamtat@mailsnare.net>
To: linux-newbie@vger.kernel.org
Subject: Re: auto start WM on second VT
Date: Fri, 8 Apr 2005 20:27:17 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0504082010160.5555@localhost.localdomain> (raw)
In-Reply-To: <5.1.0.14.1.20050408102653.02048aa8@celine>
On Fri, 8 Apr 2005, Ray Olszewski wrote:
> First, let's clear up a bit of terminology.
<snip>
Thanks for those clarifications. They clarify both how the terminology is
used as well as what the computer is doing--much needed gap-filling
information for someone like me.
> You *might* be better served by switching to (what I think of as) the
> Slackware approach, adding lines to /etc/inittab for consoles 7 and 8 that
> run xdm (or actual X logins), and removing the xdm script symlink from your
> default runlevel directory. If you want to take this approach, any Slackware
> user here should be able to give you a sample of what the inittab entry
> should look like ... I *think* is is just --
>
> 7:23:respawn:/usr/bin/X11/xdm
>
> -- but I can't be certain because I don't have a working system here that
> uses this method of starting xdm, so I'm drawing on a memory that is years
> old.
I picked around a bit further in /etc/X11/xdm and /usr/X11R6 trying to
figure out how all this works. It's rather mind-boggling trying to puzzle
out how all the relevant files relate to one another, not to mention how
each is supposed to work on its own. Your slackwarish suggestion seems
worth trying. My problem with it the way it stands, though, is that it
invokes xdm, which doesn't give me any sort of menu for chosing between
WM's. It's just a bare login window. If I log into it, I'll get another
Gnome session (my main WM on this machine) rather than the ion3 session I
want. I'll attempt now to puzzle out if there's a way to add other WM's to
some sort of menu, starting with the man page.
> PS - Did you give up on the sound card, or get it working? Or are you still
> in the process of trying?
I've pretty much given up since it managed to completely stump me as well
as the experts via me. It seems to me that, were I finally to succeed with
this card, it would be by defeating the BIOS's settings somehow. And that
would be a lesson likely applicable only to this particular computer/mobo.
That doesn't seem to justify further effort. Before going out and buying a
PCI card though, I do want to try out a real SoundBlaster (16) someone is
sending me. Since these are more clearly Linux-compatible, if it also will
not work, I can rest more fully assured that the BIOS is the source of my
problems with the Soundman card. Thanks for your help on that.
James
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2005-04-09 1:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 13:24 auto start WM on second VT James Miller
2005-04-08 17:47 ` Ray Olszewski
2005-04-09 1:27 ` James Miller [this message]
2005-04-09 2:00 ` Ray Olszewski
2005-04-09 2:38 ` James Miller
2005-04-09 3:22 ` Ray Olszewski
2005-04-09 3:51 ` Peter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.61.0504082010160.5555@localhost.localdomain \
--to=jamtat@mailsnare.net \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox