bsd is a big pain in my ash

V

vaderj

so i have a decent background in linux and was a dbadmin for a sco sysV system for a few years but have played with bsd to the point of installing it, getting frustrated and putting linux back on; this process usually finishes its cycle in about 12 hours, once a year, for the past decade or so.
I am determined now though. I will get X working on my tester, but wtf, how am i suposed to kill a process when on a fresh freebsd install, X starts with no WM, ctrl-alt-backspace is disabled, and ctl-alt-Fx (1,2,etc) do absolutely nothing. I have looked around but I am just frustrated right now and am about to just write off FreeBSD again for another year until it maybe gets mature enough to be able to start Xorg without being a supreme PITA. Slackware was my first distro back in '96 BUT it actually has always worked. I am sure there are many little secrets to Freebsd that are different just for the sake of being different, but there is no place (and yes I have browsed the unix rosetta stone many times) that documents all/most/any of these.
 
ctrl+alt+fn
where fn is 1 to 8 (ro something like that)
this will switch you to console
run top and kill process or on console you started x (with startx) Ctrl+C

Easy
 
vaderj said:
I will get X working on my tester
Click to expand...
Version (pkg_info -Ix xorg-7 xorg-server) ?

vaderj said:
X starts with no WM
Click to expand...
Which WM do you want? Is it installed? FreeBSD has not a "default WM/DE" as most linux do.
For example, if you want to start fluxbox, type echo '/usr/local/bin/fluxbox' >> .xinitrc and then run startx.
If you want gnome, have a look at http://www.freebsd.org/gnome/docs/faq2.html#full-gnome

vaderj said:
ctrl-alt-backspace is disabled
Click to expand...
If you have xorg-7.4/xorg-server-1.6 as, it seems, many people were "accidentally" pressing the keys combination (!!!) and complaining about their xorg dying.
To return to the good old behaviour, add this to your xorg.conf
Code: 
Section "ServerFlags"
        Option  "DontZap" "false"
EndSection


vaderj said:
and ctl-alt-Fx (1,2,etc) do absolutely nothing.
Click to expand...
Is the mouse working?
Again, if you have xorg-7.4/xorg-server-1.6, this could be caused by the fact that now xorg by default depends on hal (which depends on dbus) to have the keyboard and mouse detected. So, unless you have built it using WITHOUT_HAL, you have to start them adding the following lines to /etc/rc.conf
Code: 
dbus_enable="YES"
hald_enable="YES"
And if you have a keyboard with a different layout than "us", look at this [post=19423]post[/post] and at the whole thread.
As you can see from that thread, the new changes in the last xorg version caused problems to many people, and the xorg chapter in the handbook is not really updated (maybe after 7.2).
 
So why are you blaming FreeBSD for Xorg problems? You do realize that Xorg has absolutely nothing to do with FreeBSD?

As said, start reading the handbook.
 
SirDice said:
So why are you blaming FreeBSD for Xorg problems? You do realize that Xorg has absolutely nothing to do with FreeBSD?

As said, start reading the handbook.
Click to expand...
I agree with you about the fact that that are xorg problems.
I don't know if it's the cause of the OP troubles, but unfortunately, the handbook still doesn't consider xorg-7.4.
 
ale said:
I agree with you about the fact that that are xorg problems.
I don't know if it's the cause of the OP troubles, but unfortunately, the handbook still doesn't consider xorg-7.4.
Click to expand...

I saw a proposal to update the Handbook with information updated to new Xorg version. Might be a good idea for the OP to browse this week's doc-freebsd.org mailing list.
 
You must log in or register to reply here.
Back
Top