On Fri, Oct 21, 2022 at 12:55:49PM +0100, Jason McIntyre wrote: > On Fri, Oct 21, 2022 at 09:30:08AM +0000, Klemens Nanni wrote: > > Using -n does not require an interface: > > > > # sh /etc/netstart -n ; echo $? > > ifconfig lo0 inet 127.0.0.1/8 > > route -qn add -inet6 fe80:: -prefixlen 10 ::1 -reject > > ... > > 0 > > > > OK? > > > > ok. > jmc >
i was going to incliude this in my answer, but eventually thought it looks like a seperate diff: the text currently reads as though only a singular interface is specified, and -n is kind of hidden. so i reworked the text. i went with an example which basically mirrors synopsis, because it works with the -n text, and i wanted to avoid marking up interface, but not doing so added other ambiguities. so is this better? it's as unobtrusive as i could make it. jmc Index: netstart.8 =================================================================== RCS file: /cvs/src/share/man/man8/netstart.8,v retrieving revision 1.28 diff -u -p -r1.28 netstart.8 --- netstart.8 21 Oct 2022 12:04:51 -0000 1.28 +++ netstart.8 21 Oct 2022 17:36:32 -0000 @@ -88,19 +88,21 @@ and .Xr wg 4 . .El .Pp -After the system is completely initialized, it is possible to start a -newly created interface or bridges or apply the configuration from a +After the system is completely initialized +it is possible to start newly created interfaces or bridges, +or apply the configuration from .Xr hostname.if 5 -file to an existing interface, by invoking the following, where -.Ar foo0 -is the interface or bridge name: +files to existing interfaces, +by invoking +.Nm +in this fashion: .Pp -.D1 # sh /etc/netstart foo0 +.D1 # sh /etc/netstart [-n] [interface] .Pp Using the .Fl n option reports the steps that would be taken, -without actually configuring the interface. +without actually configuring anything. .Sh SEE ALSO .Xr multicast 4 , .Xr defaultdomain 5 ,
