Cathy Zhou wrote:
> When the device attaches before dladmd is started, the kernel data-link
> stil be able to be created but will not be able to added into the
> dls_vlan_hash table (keyed by linkid) as it is not able to lookup its
> linkid at that time. But the kernel data-link should still be created
> and added to the dls_vlan_hash_by_dev hash table, so that dld_open is
> able to find the corresponding kernel data-link structure so that other
> DLPI operations will be able to proceed.
>
> But this physical link will not be able to have any vanity naming
> feature (no /dev/net node will be created for it), and the dladm command
> might also act unexpected for this link.
>
> Is this a problem? I see "boot net" is only a temporary state and things
> should go fine after next reboot.
In case the kernel did bring up networking (due to net boot) *and* a
vanity name has been configured, it would be good to have some graceful
failure and not have the system turn itself into a brick.
So it would be good to test this. Perhaps existing checks of "can't
rename a link which is already in use" will do the right thing already.
Erik