Re: SSH Chroot FreeBSD 10.1 and 10.2

2015-08-22 Thread Roger Leigh
On 22/08/2015 15:01, Brandon Allbery wrote: On Sat, Aug 22, 2015 at 10:54 AM, Rainer Duffner rai...@ultra-secure.de wrote: I found it’s much easier to have actual chroot’ed ssh users once the users themselves are in an LDAP-directory. Also, for doing anything useful on that shell, it turned

Re: Ephemeral /var/run and creating port-specific subdir at service startup time

2016-08-31 Thread Roger Leigh
On 01/09/16 00:12, Mark Martinec wrote: I prefer to have a /var/run file system reside on a tmpfs as its contents is small and ephemeral in its nature (like pid files, lock files, sockets), need not be preserved across reboots, and should not have to depend on any physical disk. The problem is

Re: dmesg submission service -- please submit today

2018-10-07 Thread Roger Leigh
On 07/10/2018 05:40, Warner Losh wrote: I'd like to request as many people as possible submit their current dmesg to the service at http://dmesgd.nycbug.org/index.cgi so that we have a better basis for future preliminary lists of drivers for other parts of the tree. This one-liner works to

Re: FreeBSD 12.0-BETA2 Now Available

2018-10-29 Thread Roger Leigh
On 29/10/2018 13:40, Mark Dixon wrote: On Mon, 29 Oct 2018 at 13:24, Lars Engels wrote: On Mon, Oct 29, 2018 at 07:59:32AM +, Mark Dixon wrote: Same, FreeBSD update doesn't seem to be working: $ sudo freebsd-update upgrade -r 12.0-BETA2 IIRC freebsd-update only works for RCs, not

Re: UEFI boot failure with VMware Workstation 16 and 12.2Beta3

2020-09-30 Thread Roger Leigh
On 30/09/2020 17:44, Roger Leigh wrote: Hi folks, I've been testing FreeBSD 12.2Beta3 (amd64) with VMware Workstation 16 on Windows 10, and encountered an issue which looks to be related to the UEFI console (see attached screenshot). It's quite possible this is a VMware UEFI bug rather

UEFI boot failure with VMware Workstation 16 and 12.2Beta3

2020-09-30 Thread Roger Leigh
Hi folks, I've been testing FreeBSD 12.2Beta3 (amd64) with VMware Workstation 16 on Windows 10, and encountered an issue which looks to be related to the UEFI console (see attached screenshot). It's quite possible this is a VMware UEFI bug rather than a FreeBSD bug, and I've mentioned this