Hi Robert,
I did some tests.
On 2018-03-10 00:01:27 + Robert Elz wrote:
| X does not get "killed" either, I do not return to console.
If it gets killed, that (not returning to console) is expected.
| On this system usually the X driver is decently well-behaved,
Patrick Welche writes:
- Rather than the traditional /etc/ifconfig.vlan0, I thought I would try the
- fancy rc.conf variables:
-
- net_interfaces="vlan0"
- ifconfig_vlan0="create;vlan 1 vlanif wm0;inet 192.168.1.1 netmask 0xff00"
I have a slightly different format on a working system (with 6
Date:Wed, 14 Mar 2018 15:31:23 +
From:Patrick Welche
Message-ID: <20180314153123.GD6381@quark>
| Rather than the traditional /etc/ifconfig.vlan0, I thought I would try the
| fancy rc.conf variables:
|
| net_interfaces="vlan0"
|
Rather than the traditional /etc/ifconfig.vlan0, I thought I would try the
fancy rc.conf variables:
net_interfaces="vlan0"
ifconfig_vlan0="create;vlan 1 vlanif wm0;inet 192.168.1.1 netmask 0xff00"
but after a reboot, no complaints in /var/run/rc.log, but also no vlan0...
(BTW, what does
>Second, I bumped into a problem I have seen other have issues with: upgrading
>of >osabi and x11-links fails, because it says that I have a different
>platform than the >host it was built on. No solution for this? I even thought:
>fine, let me build osabi >from source and try upgrading again,