On Sun, 15 Jul 2018, Robert Elz wrote:
> Date:Sat, 14 Jul 2018 11:14:19 -0500 (CDT)
> From:"John D. Baker"
>
> | I also needed to set "use-host-decl-names true;" in "dhcpcd.conf".
>
> In dhcpd.conf I assume.
Yes. I added that to "/etc/dhcpd.conf", i.e., the DHCP serv
Date:Sat, 14 Jul 2018 11:14:19 -0500 (CDT)
From:"John D. Baker"
Message-ID:
| On Sat, 14 Jul 2018, Robert Elz wrote:
|
| > env force_hostname=YES
|
| Yes, that's the ticket.
Good.
| I also needed to set "use-host-decl-names true;" in "dhcpcd.conf".
I
I have a working configuration for NetBSD on bhyve. It's not a problem with
vm-bhyve https://github.com/churchers/vm-bhyve
NetBSD 7.1.2 does not initiate the bge0 nor wm0 at all under bhyve, as I
wrote earlier.
It seems to run perfectly fine other than that.
The "normal" vioif0 works fine.
I trie
On Sat, 14 Jul 2018, Robert Elz wrote:
> env force_hostname=YES
Yes, that's the ticket.
I also needed to set "use-host-decl-names true;" in "dhcpcd.conf". Some
netbooted hosts would get their hostname without this, but most would
not, ending up with "localhost". The same hosts always got
Date:Sat, 14 Jul 2018 13:12:29 +0200
From:Martin Husemann
Message-ID: <20180714111229.gf3...@mail.duskware.de>
| In userland, dhcpcd hooks should set the full name by default, if I read
| /libexec/dhcpcd-hooks/30-hostname correctly, not sure what goes wrong here
On Sat, 14 Jul 2018, Martin Husemann wrote:
> On Sat, Jul 14, 2018 at 06:40:49AM -0400, Greg Troxel wrote:
> > My guess, without reading specs, is that the right thing to do is to
> > change the in-kernel dhcp client to construct fqdn and use it.
>
> The in-kernel dhcp client is minimalistic and
On Sat, Jul 14, 2018 at 06:40:49AM -0400, Greg Troxel wrote:
> My guess, without reading specs, is that the right thing to do is to
> change the in-kernel dhcp client to construct fqdn and use it.
The in-kernel dhcp client is minimalistic and only extracts enough
data to mount /, and it should not
"John D. Baker" writes:
> So far, I can only get an FQDN for netbooted machines if I make the
> "host" entries:
>
> host foo.example.com {
> ...
> }
>
> group bar {
> option host-name "bar.example.com";
> ...
> }
>
> which is a lot of duplication for all the potential netboot
On Fri, Jul 13, 2018 at 03:21:21PM -0400, jmitchel wrote:
> a) The device requires UEFI
Have you seen this?
http://wiki.netbsd.org/Installation_on_UEFI_systems/
Martin
