2013-06-09 07:46, Leslie Jensen skrev:
2013-06-08 17:28, Polytropon skrev:
On Sat, 08 Jun 2013 12:20:56 +0200, Leslie Jensen wrote:
I've been using XDM as login manager for years. Since the latest Xorg
upgrade, XDM cannot start XFCE4 as it used to.
Strange that this happens aft
2013-06-08 17:28, Polytropon skrev:
On Sat, 08 Jun 2013 12:20:56 +0200, Leslie Jensen wrote:
I've been using XDM as login manager for years. Since the latest Xorg
upgrade, XDM cannot start XFCE4 as it used to.
Strange that this happens after an upgrade. What initalization
mechanism d
On Sat, 08 Jun 2013 12:20:56 +0200, Leslie Jensen wrote:
>
> I've been using XDM as login manager for years. Since the latest Xorg
> upgrade, XDM cannot start XFCE4 as it used to.
Strange that this happens after an upgrade. What initalization
mechanism do you use for your X sessi
I've been using XDM as login manager for years. Since the latest Xorg
upgrade, XDM cannot start XFCE4 as it used to.
What happens is that after I've given my password and hit enter, the
screen goes black and after a while it returns to the XDM log in dialogue.
I've att
Hello,
I set up xdm on a server (FreeBSD 9)and I can connect to it from any machine on
the same local network as the server, but not from computers on different
network, for example networks connected via a tunnel. Is there something to be
added in /etc/hosts.allow or in the xdm config files
adding
DisplayManager*authName:MIT-MAGIC-COOKIE-1
solves the problem.
Do you have any data about preparations that gdm do?
The Handbook mentions /proc to be mounted, but that's not
related. The settings
gdm_enable="YES"
gnome_enable="YES"
in /etc/rc.conf would
On Sat, 21 Jul 2012 20:40:44 +0200 (CEST), Wojciech Puchar wrote:
> >> after loggin in it just exits. no .xsession-errors is created. no idea
> >> where to seek error messages at all.
> >
> > Maybe errors are reported to the 1st virtual terminal
> > where the
to the 1st virtual terminal
where the XDM process outputs its messages to (currently
not running xdm, so I can't check).
there are imho nowhere.
Do you have
gdm_enable="YES"
gnome_enable="YES"
in /etc/rc.conf, and /proc mounted, as suggested in the Handboo
On Sat, 21 Jul 2012 19:19:15 +0200 (CEST), Wojciech Puchar wrote:
> i run xdm normally. after logging it runs my $HOME/.xsession that starts
> things like fvwm2
>
> i wanted to run gnome-session once, changed fvwm2 to
> /usr/local/bin/gnome-sessions
i run xdm normally. after logging it runs my $HOME/.xsession that starts
things like fvwm2
i wanted to run gnome-session once, changed fvwm2 to
/usr/local/bin/gnome-sessions
after loggin in it just exits. no .xsession-errors is created. no idea
where to seek error messages at all.
with
and xdm executes ~/.xession. In fact, I have a "cascade"
xdm file specified in xdm-config
default file Xsession try running ~/.xsession otherwise run other
defaults.
nothing is hardwired.
___
freebsd-questions@freebsd.org mailing
On Wed, 4 Jul 2012 10:40:05 +0200, uki wrote:
> 2012/7/4 Polytropon :
> > On Tue, 3 Jul 2012 23:27:21 -0700 (PDT), sw2wolf wrote:
> >> I am using slim to login which can choose Window Manager by pressing F1
> >> key.
> >> Can XDM choose Window Manager when l
2012/7/4 Polytropon :
> On Tue, 3 Jul 2012 23:27:21 -0700 (PDT), sw2wolf wrote:
>> I am using slim to login which can choose Window Manager by pressing F1 key.
>> Can XDM choose Window Manager when loginning ?
>
> No, xdm cannot do this. But as far as I remember, wdm can
On Tue, 3 Jul 2012 23:27:21 -0700 (PDT), sw2wolf wrote:
> I am using slim to login which can choose Window Manager by pressing F1 key.
> Can XDM choose Window Manager when loginning ?
No, xdm cannot do this. But as far as I remember, wdm can -- it has
some look & feel of the original C
I am using slim to login which can choose Window Manager by pressing F1 key.
Can XDM choose Window Manager when loginning ?
Reagrds!
-
e^(π.i) + 1 = 0
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Understanding-XDM-tp5721476p5724072.html
Sent from the freebsd
On Sun, 24 Jun 2012 22:19:54 +0200
Christian Graulund wrote:
>
The others have answered your questions concerning DM v. WM, but if
you are finding XDM annoying to configure, you may possible wish to
take a look at slim, x11/slim.
___
free
On Sun, 24 Jun 2012 22:19:54 +0200, Christian Graulund wrote:
> Hello Guys,
>
> I just install FreeBSD 9, and after compiling Xorg, I started trying to
> figure out how to install a Window Manager.
> When Following the handbook, I suggest installing XDM. I want to use
> some
Christian Graulund writes:
> I just install FreeBSD 9, and after compiling Xorg, I started trying to
> figure out how to install a Window Manager.
> When Following the handbook, I suggest installing XDM.
Assuming we're talking about the same xdm ... your first
probl
On Sun, 24 Jun 2012 22:19:54 +0200, Christian Graulund wrote:
> Hello Guys,
>
> I just install FreeBSD 9, and after compiling Xorg, I started trying to
> figure out how to install a Window Manager.
> When Following the handbook, I suggest installing XDM. I want to use
> somethin
Hello Guys,
I just install FreeBSD 9, and after compiling Xorg, I started trying to
figure out how to install a Window Manager.
When Following the handbook, I suggest installing XDM. I want to use
something like Openbox, as my window manager, and I can't figure out if
Openbox is a replacemen
On Fri, Mar 4, 2011 at 9:34 AM, Polytropon wrote:
> While I found that generic
> UNIX knowledge was applicable everywhere, "Linux knowledge"
> was not, as you could see from file names and locations,
> procedures, and configuration statements which could not
> be transferred 1:1 between the system
Readers will surely see more and more people having
similar reasons why those who happily use FreeBSD do
not want to go back to Linux, or even worse, "Windows".
I may include myself here, with the special case that
I've never been a "Windows" user, so my mind is clean
and healthy and unspoiled of M
On Fri, Mar 04, 2011 at 03:28:10PM +0100, Christopher J. Ruwe wrote:
>
> Later, I tried OpenSolaris and FreeBSD and am now using FreeBSD due to
> the same reasons as Chad Perrin stated: Being a power-user, wanting to
> control things and (now diverting from Chad's reasons) wanting to use
> technol
On Thu, 03 Mar 2011 17:01:10 -0500
"John D. Hendrickson and Sara Darnell" wrote:
> [snip]
> If anyone would like to quickly comment I'd love to hear why bsd
> would be a better choice than ubantu (for what audience it is better).
>
> Thanks all,
>
> John
>
> __
On Thu, 03 Mar 2011 17:01:10 -0500
"John D. Hendrickson and Sara Darnell" wrote:
> Hi. I'm a BSD idiot I use [Debian] linux.
>
> rc.d question
>
> I'm trying to release a project (just below) to the widest possible
> unix audience. I need a line in "/etc/inittab" and to have a
> start/stop in
On Thu, Mar 03, 2011 at 05:01:10PM -0500, John D. Hendrickson and Sara Darnell
wrote:
>
> Hi. I'm a BSD idiot I use [Debian] linux.
[snip]
>
> If anyone would like to quickly comment I'd love to hear why bsd would
> be a better choice than ubantu (for what audience it is better).
FreeBSD is
sure the project is good enough to warrant further testing
/ if the casual user might save time / effort with it. Tell me what you
think if you have time! Who doesn't want feedback?
http://sourceforge.net/projects/xdm-options/
https://sourceforge.net/projects/xdm-options/
(second has ht
On Fri, Dec 31, 2010 at 06:07:34PM +0100, Alain G. Fabry wrote:
> Hi, I'm trying to get my XDMCP to work, but for some reason the XDM daemon
> doesn't reply to XDMCP requests.
>
> I see the XDMCP packet arriving on my xdm server
>
> harley# tcpdump port 177
> tcp
On 31/12/2010 7:07 μ.μ., Alain G. Fabry wrote:
> Hi, I'm trying to get my XDMCP to work, but for some reason the XDM daemon
> doesn't reply to XDMCP requests.
>
> I see the XDMCP packet arriving on my xdm server
>
> harley# tcpdump port 177
> tcpdump: verbose outpu
Hi, I'm trying to get my XDMCP to work, but for some reason the XDM daemon
doesn't reply to XDMCP requests.
I see the XDMCP packet arriving on my xdm server
harley# tcpdump port 177
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on bge0, link-t
Polytropon writes:
> A small addition: In order to be able to use X with an
> initialisation file even when not using XDM (i. e. starting X by
> "startx") AND not having to maintain two startup files (.xsession
> and .xinitrc) AND furthermore incorporating shell settin
On Sat, 06 Mar 2010 00:10:56 -0600, Programmer In Training
wrote:
> On 03/05/10 08:46, Frank Shute wrote:
>
> > If you read the manpage for xdm(1) you will see that the script that
> > is run on login is ~/.xsession
> >
> > Try putting "exec wmaker" in t
On 03/05/10 08:46, Frank Shute wrote:
> If you read the manpage for xdm(1) you will see that the script that
> is run on login is ~/.xsession
>
> Try putting "exec wmaker" in there.
>
> To run xdm from boot, you have to edit /etc/ttys and then:
>
> # kill -
x27;t seem to be the case
> >> anymore.
> >
> > twm is still enabled by default as part of the x11/xorg-apps port.
>
> I can confirm that, and I too have problems with XDM despite having
> 'exec wmaker' in my .xinitrc in my home directory (sometimes
f the x11/xorg-apps port.
I can confirm that, and I too have problems with XDM despite having
'exec wmaker' in my .xinitrc in my home directory (sometimes XDM will
kick me out to the login, sometimes it will just take me to a blank
session wherein I can do nothing). I'd like to use XDM and
On Fri, 5 Mar 2010, Polytropon wrote:
On Thu, 4 Mar 2010 09:30:05 +0100, n dhert wrote:
Installed a fresh FreeBSD-8.0, xorg, configured xorg for my screen,
installed xdm.
After reboot I see a graphical login window. When entering username and
password, it seems to accept it, but immediatly
On Thu, 4 Mar 2010 09:30:05 +0100, n dhert wrote:
> Installed a fresh FreeBSD-8.0, xorg, configured xorg for my screen,
> installed xdm.
> After reboot I see a graphical login window. When entering username and
> password, it seems to accept it, but immediatly present the graphical lo
Installed a fresh FreeBSD-8.0, xorg, configured xorg for my screen,
installed xdm.
After reboot I see a graphical login window. When entering username and
password, it seems to accept it, but immediatly present the graphical login
window again. (In console mode (Ctrl-Alt-F1) I can login at the
On Thu, Jan 21, 2010 at 11:30:47PM +0200, Manolis Kiagias wrote:
> On 21/01/2010 8:54 μ.μ., rhin...@postmail.ch wrote:
> > modifying Xaccess, starting xdm with parameter "udpPort 177".
> >
> > The command "netstat -a" never indicates that a process is list
On Thu, Jan 21, 2010 at 11:30:47PM +0200, Manolis Kiagias wrote:
> On 21/01/2010 8:54 ??.??., rhin...@postmail.ch wrote:
> > Hi All,
> >Is-it possible to run xdm with remote access through XDMCP protocol on
> > freebsd 8 ?
> >
>
> Yes. I have an entire
On 21/01/2010 8:54 μ.μ., rhin...@postmail.ch wrote:
> Hi All,
>Is-it possible to run xdm with remote access through XDMCP protocol on
> freebsd 8 ?
>
Yes. I have an entire lab working this way :)
> I have tried almost anything: commenting line about port 0 in xdm-config
Hi All,
Is-it possible to run xdm with remote access through XDMCP protocol on
freebsd 8 ?
I have tried almost anything: commenting line about port 0 in xdm-config,
modifying Xaccess, starting xdm with parameter "udpPort 177".
The command "netstat -a" never indicat
A little sidenote:
On Tue, 10 Nov 2009 14:06:04 -0800 (PST), Neil Short wrote:
> If I am using xdm and I log out of the window manager and then
> attempt to shut down the computer - by going to tty 0 and typing
> # halt -p - the disk syncs and then the shutdown freezes.
You shoul
So I got Xorg working with Hal. Wahoo.
If I log in from a display manager I encounter some weird stuff.
If I am using xdm and I log out of the window manager and then attempt to shut
down the computer - by going to tty 0 and typing # halt -p - the disk syncs and
then the shutdown freezes.
If I
Hi,
Every time I start xdm I get the following message on ttyv0,
xdm: pam_sm_close_session(): no utmp record for :0
Everything seems to work just fine. I can log in, and everything runs as
expected, so it's basically just an annoyance, especially since I don't
know whether I
up. If the user logs out, he should not
drop to CLI mode; instead, an xdm login should be shown
to allow him (or someone else) to log in and use X.
In the past, I created the auto-login as follows:
First, I create an entry in /etc/gettytab, right after
the "default:" entry; it contai
On Tue, May 5, 2009 at 7:21 PM, Polytropon wrote:
> On Tue, 5 May 2009 18:45:02 -0500, Andrew Gould
> wrote:
> > It's good, general advice. There are UPDATING files in various places
> for
> > various updates, I think, including /usr/src/.
>
> At least according to the history of problems with
On Tue, 5 May 2009 18:45:02 -0500, Andrew Gould
wrote:
> It's good, general advice. There are UPDATING files in various places for
> various updates, I think, including /usr/src/.
At least according to the history of problems with X that
appeared on this list, /usr/ports/UPDATING hasn't receive
Absolutely!
(Sent from my iPhone)
On May 5, 2009, at 7:45 PM, Andrew Gould
wrote:
On Tue, May 5, 2009 at 6:32 PM, Daniel Underwood
wrote:
I thought /usr/ports/UPDATING is only created when you appraise your
ports with a view toward updating. I.e, after a fresh install of 7.2
(not an upg
On Tue, May 5, 2009 at 6:32 PM, Daniel Underwood wrote:
> I thought /usr/ports/UPDATING is only created when you appraise your
> ports with a view toward updating. I.e, after a fresh install of 7.2
> (not an upgrade from 7.1), I didn't think the UPDATING file would be
> very helpful.
>
It's good,
I thought /usr/ports/UPDATING is only created when you appraise your
ports with a view toward updating. I.e, after a fresh install of 7.2
(not an upgrade from 7.1), I didn't think the UPDATING file would be
very helpful.
___
freebsd-questions@freebsd.org
On Wed, 06 May 2009 00:01:47 +0300, Manolis Kiagias wrote:
> Taking this opportunity, allow me to remind to everyone that the
> Handbook is always "work in progress" and it is always useful to check
> again sections that you have already read, as new info is added
> regularly. This latest addition
Andrew Gould wrote:
> On Tue, May 5, 2009 at 3:17 PM, Daniel Underwood wrote:
>
>
>> Yep, that was it! I should have read the Handbook more thoroughly:
>> http://www.freebsd.org/doc/en/books/handbook/x-config.html#AEN6615
>>
>>
>
>
> me too ;-)
>
Taking this opportunity, allow me to r
On Tue, May 5, 2009 at 3:17 PM, Daniel Underwood wrote:
> Yep, that was it! I should have read the Handbook more thoroughly:
> http://www.freebsd.org/doc/en/books/handbook/x-config.html#AEN6615
>
me too ;-)
___
freebsd-questions@freebsd.org mailing l
Yep, that was it! I should have read the Handbook more thoroughly:
http://www.freebsd.org/doc/en/books/handbook/x-config.html#AEN6615
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscrib
On Tue, May 5, 2009 at 2:23 PM, Daniel Underwood wrote:
> Just installed 7.2-RELEASE. After changing my /etc/ttys to default to
> xdm and rebooting, my machine opens xdm, but I cannot type or press
> enter. My keyboard isn't totally unresponsive, however, because I can
> Ctrl+
I don't have an xorg.conf file. When I installed 7.1-RELEASE on this
laptop (exact same machine) I didn't need to configure an xorg.conf
file. But I'll certainly try your advice.
Thanks!
___
freebsd-questions@freebsd.org mailing list
http://lists.free
Hi,
Daniel Underwood wrote:
Just installed 7.2-RELEASE. After changing my /etc/ttys to default to
xdm and rebooting, my machine opens xdm, but I cannot type or press
enter. My keyboard isn't totally unresponsive, however, because I can
Ctrl+Alt+F# to another virtual terminal.
Try a
Just installed 7.2-RELEASE. After changing my /etc/ttys to default to
xdm and rebooting, my machine opens xdm, but I cannot type or press
enter. My keyboard isn't totally unresponsive, however, because I can
Ctrl+Alt+F# to another virtual terminal.
Any ideas?
Thanks,
D
On Tue, 17 Feb 2009, Anton Shterenlikht wrote:
I think the xdm-config file got overwritten during the port upgrade with the
default (secure?) settings. I had to comment out the last setting in xdm-config
% tail -3 /usr/local/lib/X11/xdm/xdm-config
! SECURITY: do not listen for XDMCP or Chooser
On Tue, Feb 17, 2009 at 04:30:49PM +, Anton Shterenlikht wrote:
> On Fri, Feb 13, 2009 at 10:13:08AM +, Anton Shterenlikht wrote:
> > On 6.4-stable alpha I cannot get xdm to become a daemon, it exits
> > immediately with empty /var/log/xdm.log.
> >
> > I trie
On Fri, Feb 13, 2009 at 10:13:08AM +, Anton Shterenlikht wrote:
> On 6.4-stable alpha I cannot get xdm to become a daemon, it exits
> immediately with empty /var/log/xdm.log.
>
> I tried to use -debug option, and this is the output:
>
> # xdm -debug 1
> Displa
On 6.4-stable alpha I cannot get xdm to become a daemon, it exits
immediately with empty /var/log/xdm.log.
I tried to use -debug option, and this is the output:
# xdm -debug 1
DisplayManager.errorLogFile/DisplayManager.ErrorLogFile value /var/log/xdm.log
DisplayManager.daemonMode
On Wed, 11 Feb 2009, Da Rock wrote:
On Wed, 2009-02-11 at 20:32 +1000, Warren Liddell wrote:
AMD64 4gig RAM FreeBSD 7.1 KDE 4.2
I've noticed of late when i have had the misfortune of rebooting this
machine due to severre storms and blackouts, when it boots everything
loads fine, xdm ini
On Wed, 11 Feb 2009, Warren Liddell wrote:
AMD64 4gig RAM FreeBSD 7.1 KDE 4.2
I've noticed of late when i have had the misfortune of rebooting this machine
due to severre storms and blackouts, when it boots everything loads fine, xdm
initates an i get the standard logon screen, however
rms and blackouts, when it boots everything
> > loads fine, xdm initates an i get the standard logon screen, however,
> > you cant do anything an the mouse dosent work. To solve this issue i go
> > to console via CTRL + ALT + F1 kill tthe XDM pid an once it comes back
> >
On Wed, 2009-02-11 at 20:32 +1000, Warren Liddell wrote:
> AMD64 4gig RAM FreeBSD 7.1 KDE 4.2
>
> I've noticed of late when i have had the misfortune of rebooting this
> machine due to severre storms and blackouts, when it boots everything
> loads fine, xdm initates an i ge
On Wed, Feb 11, 2009 at 08:32:20PM +1000, Warren Liddell wrote:
> AMD64 4gig RAM FreeBSD 7.1 KDE 4.2
>
> I've noticed of late when i have had the misfortune of rebooting this
> machine due to severre storms and blackouts, when it boots everything
> loads fine, xdm initates a
AMD64 4gig RAM FreeBSD 7.1 KDE 4.2
I've noticed of late when i have had the misfortune of rebooting this
machine due to severre storms and blackouts, when it boots everything
loads fine, xdm initates an i get the standard logon screen, however,
you cant do anything an the mouse dosent
On Fri, Feb 06, 2009 at 09:39:23PM +0100, Roger Olofsson wrote:
>
>
> Anton Shterenlikht skrev:
> > After upgrades of 23-24 Jan 2009 xdm is not working:
> >
> > # xdm
> > # ps ax|grep xdm
> > 75632 p1 S+ 0:00.01 grep xdm
> > # cat /va
Anton Shterenlikht skrev:
After upgrades of 23-24 Jan 2009 xdm is not working:
# xdm
# ps ax|grep xdm
75632 p1 S+ 0:00.01 grep xdm
# cat /var/log/xdm.log
#
So no xdm daemon.
My system: FreeBSD 6.4-STABLE alpha, xdm-1.1.8_1.
Any ideas
On Thu, Feb 05, 2009 at 08:01:25AM -0500, Robert Huff wrote:
>
> Anton Shterenlikht writes:
>
> > After upgrades of 23-24 Jan 2009 xdm is not working:
> >
> > # xdm
> > # ps ax|grep xdm
> > 75632 p1 S+ 0:00.01 grep xdm
> > # cat /var/log
Anton Shterenlikht writes:
> After upgrades of 23-24 Jan 2009 xdm is not working:
>
> # xdm
> # ps ax|grep xdm
> 75632 p1 S+ 0:00.01 grep xdm
> # cat /var/log/xdm.log
> Any ideas?
1) May we see /var/log/Xorg.0.log?
After upgrades of 23-24 Jan 2009 xdm is not working:
# xdm
# ps ax|grep xdm
75632 p1 S+ 0:00.01 grep xdm
# cat /var/log/xdm.log
#
So no xdm daemon.
My system: FreeBSD 6.4-STABLE alpha, xdm-1.1.8_1.
Any ideas?
--
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Br
Fbsd1 <[EMAIL PROTECTED]> writes:
> My /etc/ttys looks like this
>
> ttyv6 "/usr/libexec/getty Pc" cons25 on secure
> ttyv7 "/usr/libexec/getty Pc" cons25 on secure
> #ttyv8 "/usr/local/bin/xdm -nodaemon" xterm o
My /etc/ttys looks like this
ttyv6 "/usr/libexec/getty Pc" cons25 on secure
ttyv7 "/usr/libexec/getty Pc" cons25 on secure
#ttyv8 "/usr/local/bin/xdm -nodaemon" xterm off secure
#ttyv8 "/usr/local/bin/xdm -nodaemon&quo
On Tue, Nov 11, 2008 at 11:01:44AM -0500, Lowell Gilbert wrote:
> Fbsd1 <[EMAIL PROTECTED]> writes:
>
Hello,
sorry, but I didn't follow the whole thread.
> > Mel wrote:
> >> You first need to get rid of that. xdm can't open /dev/ttyv8 while
> >> ge
Fbsd1 <[EMAIL PROTECTED]> writes:
> Mel wrote:
>> On Tuesday 11 November 2008 11:35:41 Fbsd1 wrote:
>>
>>
>>>>> Still getting error msg
>>>>> init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second
>>
>>
Next question is are the xdm
configuration files suppose to work as delivered by the port install AS IS?
As a default config demo?
Yes. When I said 'range', I did mean range. Not 2 possibilities. Missing
libraries, tainted environment, typos, tied up resources, tight security
On Tue, 11 Nov 2008 19:48:51 +0800, Fbsd1 <[EMAIL PROTECTED]> wrote:
> Startx works ok so not xorg problem. Next question is are the xdm
> configuration files suppose to work as delivered by the port install AS IS?
> As a default config demo?
Ha - "xdm configuration files
t;> init: getty repeating too quickly on port /dev/ttyv8, sleeping 30
> >>>>>> second
> >>>
> >>> You first need to get rid of that. xdm can't open /dev/ttyv8 while
> >>> getty is hammering at it.
> >>
> >> I turned th
On Tuesday 11 November 2008 12:09:01 Fbsd1 wrote:
> Mel wrote:
> > On Tuesday 11 November 2008 11:35:41 Fbsd1 wrote:
> >>>> Still getting error msg
> >>>> init: getty repeating too quickly on port /dev/ttyv8, sleeping 30
> >>>> second
> >
Mel wrote:
On Tuesday 11 November 2008 12:09:01 Fbsd1 wrote:
Mel wrote:
On Tuesday 11 November 2008 11:35:41 Fbsd1 wrote:
Still getting error msg
init: getty repeating too quickly on port /dev/ttyv8, sleeping 30
second
You first need to get rid of that. xdm can't open /dev/ttyv8 while
Mel wrote:
On Tuesday 11 November 2008 11:35:41 Fbsd1 wrote:
Still getting error msg
init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second
You first need to get rid of that. xdm can't open /dev/ttyv8 while getty is
hammering at it.
I turned that off all ready b
On Tuesday 11 November 2008 11:35:41 Fbsd1 wrote:
> >> Still getting error msg
> >> init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second
You first need to get rid of that. xdm can't open /dev/ttyv8 while getty is
hammering at it.
--
Mel
Probl
ething
like this, something I would never had put in any combination
with X...
By the way, in order to try if xdm is working correctly it can be
started directly by the command "xdm" anytime.
I had ~/.xsession spelled correctly in the directory. Just typo error in
email. Changed the
peating too quickly on port /dev/ttyv8, sleeping 30 second
> >
> > Hey, I saw this one... but I'm not sure how I solved it. Is your
> > /etc/hosts and hostname set correctly? I think it was something
> > like this, something I would never had put in any combination
> &g
mbination
with X...
By the way, in order to try if xdm is working correctly it can be
started directly by the command "xdm" anytime.
I had ~/.xsession spelled correctly in the directory. Just typo error in
email. Changed the contents of ~/.xsession as you posted. Still no joy.
ation
with X...
By the way, in order to try if xdm is working correctly it can be
started directly by the command "xdm" anytime.
--
Polytropon
>From Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebs
logging in at command line works and startx works. Now want to use x11
xdm to control logins for virtual terminals 9+
Followed handbook instructions 5.6.2 Using XDM doing this
ttyv8 "/usr/local/bin/xdm -nodaemon" xterm on secure
Then kill -HUP 1 to reread the file.
Also c
On Sat, Nov 24, 2007 at 04:22:48AM -0500, Aryeh Friedman wrote:
> I am in the middle of setting up a new machine and want to get rid of
> the &^&*(*&%*&@ xconsole on xdm (it doesn't go away on login
> either)... how?
/usr/loc
I am in the middle of setting up a new machine and want to get rid of
the &^&*(*&%*&@ xconsole on xdm (it doesn't go away on login
either)... how?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listi
Wojciech Puchar wrote:
pushing aqnd releasing the power button, so the OS shuts down using
ACPI). This happens every time. No matter what window manager I use.
But it only happens when I use xdm. If I start X with startx, it shuts
down cleanly and returns to the tty from which I ran startx
pushing aqnd releasing the power button, so the OS shuts down using ACPI).
This happens every time. No matter what window manager I use. But it only
happens when I use xdm. If I start X with startx, it shuts down cleanly and
returns to the tty from which I ran startx.
how you start xdm?
from
ything works like a charm, except for one small
annoyance. If I run xdm, everything hangs when I log out. The monitor
just turns black and i get no response whatsoever for neither the mouse
nor the keyboard. The only thing that works is shutting the computer off
(by quickly pushing aqnd releasi
On Thu, Aug 23, 2007 at 12:16:10AM +0400, Boris Samorodov wrote:
> On Wed, 22 Aug 2007 12:11:47 -0700 Gary Kline wrote:
>
> > I just rebooted my DNS server and now X fails. I'm pretty sure I
> > did everything re the xorg instructions in UPDATING. The error
> > message in /var/lob/Xo
On Wed, 22 Aug 2007 12:11:47 -0700 Gary Kline wrote:
> I just rebooted my DNS server and now X fails. I'm pretty sure I
> did everything re the xorg instructions in UPDATING. The error
> message in /var/lob/Xorg.0.log says exactly::
> (II) Loader running on freebsd
> (II) Load
On Wed, Aug 22, 2007 at 12:11:47PM -0700, Gary Kline wrote:
>
> I just rebooted my DNS server and now X fails. I'm pretty sure I
> did everything re the xorg instructions in UPDATING. The error
> message in /var/lob/Xorg.0.log says exactly::
>
> (II) Loader running on freebsd
I just rebooted my DNS server and now X fails. I'm pretty sure I
did everything re the xorg instructions in UPDATING. The error
message in /var/lob/Xorg.0.log says exactly::
(II) Loader running on freebsd
(II) LoadModule: "pcidata"
(WW) Warning, couldn't open module pcid
Boris Samorodov schrieb:
On Mon, 16 Apr 2007 15:03:07 +0200 Stevan Tiefert wrote:
I have written an e-mail on 12. April 2007 in
freebsd-questions@freebsd.org and a day later in
[EMAIL PROTECTED] concerning a login-problem with a X-Terminal
to a FreeBSD-6.2-XDM-Server.
The reason for the
1 - 100 of 200 matches
Mail list logo
