Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 07 Aug 2019 02:44:20 +0200
From:      hw <hw@adminart.net>
To:        MJ <mafsys1234@gmail.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: how to install into a directory
Message-ID:  <87lfw5pzx7.fsf@toy.adminart.net>
In-Reply-To: <18a2c14c-0767-534a-dc48-dbd167180e1b@gmail.com> (MJ's message of "Mon, 5 Aug 2019 12:17:44 %2B1000")
References:  <871ry05xea.fsf@toy.adminart.net> <18a2c14c-0767-534a-dc48-dbd167180e1b@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
MJ <mafsys1234@gmail.com> writes:

> The archives contained here:
>
> https://download.freebsd.org/ftp/releases/amd64/amd64/12.0-RELEASE/
>
>
> Assuming you're amd64 based. Extract them into that directory.

Yes, thanks!  It can't get any easier :)

I got it to work today, so I can PXE boot FreeBSD and kinda *jump* users
into an xfreerdp session on the xrdp server right after they logged in
at the console, abusing startx as login shell and a suitable .xinitrc in
their home directories mounted via NFS.

What I couldn't get to work is XDM doing that for me, which seemed to be
the way it ought to be done.  Like a machine would PXE boot and show XDM
and a user logs in and instead of XDM starting a window manager, it
starts xfreerdp --- which also raises the question how I could avoid
requiring the user to log in twice after getting XDM to work somehow.


For the record, the Thinstation stuff didn't work at all.  It was
impossible to create a bootable image (perhaps Fedora is an incompatible
host system), and even the VM image they supply to make images is not
bootable (which otherwise should be compatible so that bootable images
can be made ...).  So save your time and go to FreeBSD instead.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87lfw5pzx7.fsf>