Sponsored Content
Full Discussion: BSD: Getting the WM loaded
Operating Systems BSD BSD: Getting the WM loaded Post 302932641 by sea on Friday 23rd of January 2015 03:46:54 AM
Old 01-23-2015
BSD: Getting the WM loaded

Heyas

Since freebsd has set TERM to xterm when in terminal mode, i'm very curious what its value will be in GUI mode - seems its xterm (in x11/twm) as well.. how smart Smilie Smilie

So i've installed: awesome and xorg, but when calling awesome, it talks something about invalid display.
So i've set it to set DISPLAY = :0 and tried again, but still no luck.
startx works though, brabbling about freebsd:0, so i changed DISPLAY accordingly, and retried with awesome - still no luck Smilie

Currently i'm looking for both, the systemwide awesome configuration, AND the pendant of RedHats /etc/sysconfig/desktop, which defines wich Login Manager & DE to load.

Guess i've found the 'source' folder (/usr/ports/x11-wm/awesome), but not the installed folder.

Finaly found 'a' xinitrc in /usr/local/etc/X11/xinit/xinitrc.
Where i've replaced twm & with awesome &, sadly without luck, though there was a change - not for the better anyway...

To summarize, i tried:
manual call
startx
xinitrc
{/etc , /usr/local/etc} /sysconfig/desktop could not be found

Even installed slim, enabled it, and when started it shows the 'session' as awesome, but when logging in, i get a naked X11, no menu, no gui, no mouse action but moving.

Curious, there is no lua package to install, but awesome is based on lua?!
Might that be related?
- No its not, package was named lua52 Smilie

What do i have to do to get AwesomeWM working on FreeBSD?

Thank you

Last edited by sea; 01-23-2015 at 08:28 AM..
 

We Also Found This Discussion For You

1. BSD

for linux and BSD users interested in Unix system V/bsd

for all you unix/linux interested heres an online book for free that covers the basics of BSD SysV Unix commands and applications . giving the average linux user a perspective on the differences in context of the two operating systems and for BSD users covers material as a refernce guide. ... (0 Replies)
Discussion started by: moxxx68
0 Replies
STARTX(1)						      General Commands Manual							 STARTX(1)

NAME
startx - initialize an X session SYNOPSIS
startx [ [ client ] options ... ] [ -- [ server ] [ display ] options ... ] DESCRIPTION
The startx script is a front end to xinit that provides a somewhat nicer user interface for running a single session of the X Window Sys- tem. It is often run with no arguments. Arguments immediately following the startx command are used to start a client in the same manner as xinit(1). The special argument '--' marks the end of client arguments and the beginning of server options. It may be convenient to specify server options with startx to change on a per-session basis the default color depth, the server's notion of the number of dots-per-inch the display device presents, or take advantage of a different server layout, as permitted by the Xorg(1) server and specified in the xorg.conf(5) file. Some examples of specifying server arguments follow; consult the manual page for your X server to determine which arguments are legal. startx -- -depth 16 startx -- -dpi 100 startx -- -layout Multihead To determine the client to run, startx first looks for a file called .xinitrc in the user's home directory. If that is not found, it uses the file xinitrc in the xinit library directory. If command line client options are given, they override this behavior and revert to the xinit(1) behavior. To determine the server to run, startx first looks for a file called .xserverrc in the user's home directory. If that is not found, it uses the file xserverrc in the xinit library directory. If command line server options are given, they override this behavior and revert to the xinit(1) behavior. Users rarely need to provide a .xserverrc file. See the xinit(1) manual page for more details on the arguments. The system-wide xinitrc and xserverrc files are found in the /usr/local/lib/X11/xinit directory. The .xinitrc is typically a shell script which starts many clients according to the user's preference. When this shell script exits, startx kills the server and performs any other session shutdown needed. Most of the clients started by .xinitrc should be run in the back- ground. The last client should run in the foreground; when it exits, the session will exit. People often choose a session manager, window manager, or xterm as the ''magic'' client. EXAMPLE
Below is a sample .xinitrc that starts several applications and leaves the window manager running as the ''last'' application. Assuming that the window manager has been configured properly, the user then chooses the ''Exit'' menu item to shut down X. xrdb -load $HOME/.Xresources xsetroot -solid gray & xbiff -geometry -430+5 & oclock -geometry 75x75-0-0 & xload -geometry -80-0 & xterm -geometry +0+60 -ls & xterm -geometry +0-100 & xconsole -geometry -0+0 -fn 5x7 & exec twm ENVIRONMENT VARIABLES
DISPLAY This variable gets set to the name of the display to which clients should connect. Note that this gets set, not read. XAUTHORITY This variable, if not already defined, gets set to $(HOME)/.Xauthority. This is to prevent the X server, if not given the -auth argument, from automatically setting up insecure host-based authentication for the local host. See the Xserver(1) and Xsecurity(7) manual pages for more information on X client/server authentication. FILES
$(HOME)/.xinitrc Client to run. Typically a shell script which runs many programs in the background. $(HOME)/.xserverrc Server to run. The default is X. /usr/local/lib/X11/xinit/xinitrc Client to run if the user has no .xinitrc file. /usr/local/lib/X11/xinit/xserverrc Server to run if the user has no .xserverrc file. SEE ALSO
xinit(1), Xserver(1), Xorg(1) X Version 11 xinit 1.1.1 STARTX(1)
All times are GMT -4. The time now is 01:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy