Date: 17 Oct 2002 19:29:47 -0700 From: swear@attbi.com (Gary W. Swearingen) To: Thanos Tsouanas <thief_grr@yahoo.com> Cc: freebsd-questions@freebsd.org Subject: Re: X problems, please advise helpless newbie Message-ID: <4wlm4w4gys.m4w@localhost.localdomain> In-Reply-To: <20021017185544.20280.qmail@web13505.mail.yahoo.com> References: <20021017185544.20280.qmail@web13505.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanos Tsouanas <thief_grr@yahoo.com> writes:
> i have followed the instructions on the HB and they didnt work, thats why i came up with the
> insecure method... startx gives similar errors to the ones mentioned in the original msg.
> any ideas why?
You can get better control over what's going on by avoiding "startx".
I use something like this (in a script which keeps root from using X):
/usr/X11R6/bin/xinit ~/.xinitrc -- /usr/X11R6/bin/Xwrapper-4
You should try omiting the second filename after ensuring that you don't
have that file (the default) and X should start up an xterm.
That Xwrapper-4 comes from the "x11/wrapper" package/port; it's used to
run X with non-root privileges and it expects your XF86Config to say
which X server module is to be used, etc.
You can probably start a window manager by using it's filename instead
of ~/.xinitrc, but most people use a file like that modeled on
/usr/X11R6/lib/X11/xinit/xinitrc
After you know that X will start, you can just start X after booting to
text mode like many people prefer to do, or go back and learn how to
configure one of the xdm/gdm/kdm gizmos at your leisure.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4wlm4w4gys.m4w>