On Sun, 17 Sep 2017 21:56:39 +
Chavdar Ivanov wrote:
> One small addition to the previous - after taking a checkpoint and
> shutting the session manager out - which is just a logout - on the
> next login I got xconsole running, but with a login prompt. Had to
> set 'console' to 'off' and 'cons
On Mon, 18 Sep 2017 08:48:16 +0100
Patrick Welche wrote:
> On Sun, Sep 10, 2017 at 07:43:04PM +0300, Erkki Ruohtula wrote:
> > I did a fresh installation with NetBSD-7.1-amd64.iso in VirtualBox
> > 5.1.26, mostly using defaults. I did enable xdm in the installer.
> > Everything appeared to go smoo
On Sun, Sep 10, 2017 at 07:43:04PM +0300, Erkki Ruohtula wrote:
> I did a fresh installation with NetBSD-7.1-amd64.iso in VirtualBox
> 5.1.26, mostly using defaults. I did enable xdm in the installer.
> Everything appeared to go smoothly, and the system now starts nicely
> X11, and shows the xdm lo
One small addition to the previous - after taking a checkpoint and shutting
the session manager out - which is just a logout - on the next login I got
xconsole running, but with a login prompt. Had to set 'console' to 'off'
and 'constty' to 'on' in /etc/ttys.
Chavdar
On Sun, 17 Sep 2017 at 22:48
I have been bitten by this quite a few times before, so I started preparing
in advance a .xsession file. Looking at this thread, I decided to check how
things are now with -current and installed a fresh overnight build under
VirtualBox with full configuration during sysinstall, enabling xdm and
cre
On Sun 17 Sep 2017 at 22:43:38 +0300, Erkki Ruohtula wrote:
> Tried it. It does not help. In any case xsm gets run in
> the same enviroment as .xsession would be run, and the latter
> has no trouble starting twm and xterm.
A pity.
> I wonder if everyone using X11 on NetBSD does it by setting
> up
On Sun, 17 Sep 2017 20:24:41 +0200
Rhialto wrote:
> On Sun 17 Sep 2017 at 18:37:45 +0300, Erkki Ruohtula wrote:
> > twm
> > smproxy
> > xterm
> >
> > but apparently it fails to do so. (All these programs do exist
> > in the installation).
>
> Maybe at the time that xsm tries to execute those p
On Sun 17 Sep 2017 at 18:37:45 +0300, Erkki Ruohtula wrote:
> twm
> smproxy
> xterm
>
> but apparently it fails to do so. (All these programs do exist
> in the installation).
Maybe at the time that xsm tries to execute those programs, they are not
in $PATH? In that case, specifying full paths mig
On Sun, 10 Sep 2017 19:43:04 +0300
Erkki Ruohtula wrote:
> I did a fresh installation with NetBSD-7.1-amd64.iso in VirtualBox
> 5.1.26, mostly using defaults. I did enable xdm in the installer.
> Everything appeared to go smoothly, and the system now starts nicely
> X11, and shows the xdm login sc
Hi,
I did a fresh installation with NetBSD-7.1-amd64.iso in VirtualBox
5.1.26, mostly using defaults. I did enable xdm in the installer.
Everything appeared to go smoothly, and the system now starts nicely
X11, and shows the xdm login screen. The problem is I cannot get
past that. If I enter the us
10 matches
Mail list logo
