My last mail is waiting for the mailing list approval.
But it was already some days, so I sent it again.
--- Patrick Dung <[EMAIL PROTECTED]> 內容：>
--- Lowell Gilbert
> <[EMAIL PROTECTED]> 內容：>
> Patrick Dung <[EMAIL PROTECTED]> writes:
> >
> > > Only /dev/bpf0 is there at boot time
> > > But when
--- Lowell Gilbert
<[EMAIL PROTECTED]> 內容：>
Patrick Dung <[EMAIL PROTECTED]> writes:
>
> > Only /dev/bpf0 is there at boot time
> > But when I run tcpdump, it automatically create
> > /dev/bpf1 (I have multiple NIC).
> > Running devfs at boot time cannot set the
> /dev/bpf1,
> > which is not prese
Patrick Dung <[EMAIL PROTECTED]> writes:
> Only /dev/bpf0 is there at boot time
> But when I run tcpdump, it automatically create
> /dev/bpf1 (I have multiple NIC).
> Running devfs at boot time cannot set the /dev/bpf1,
> which is not present.
Running devfs(8) at boot time will set rules that wil
In the last episode (Jul 07), Patrick Dung said:
> Only /dev/bpf0 is there at boot time
> But when I run tcpdump, it automatically create
> /dev/bpf1 (I have multiple NIC).
> Running devfs at boot time cannot set the /dev/bpf1,
> which is not present.
Devfs rules use wildcard matches:
path pat
Only /dev/bpf0 is there at boot time
But when I run tcpdump, it automatically create
/dev/bpf1 (I have multiple NIC).
Running devfs at boot time cannot set the /dev/bpf1,
which is not present.
--- Lowell Gilbert
<[EMAIL PROTECTED]> 內容：>
Patrick Dung <[EMAIL PROTECTED]> writes:
>
> > There is no w
Patrick Dung <[EMAIL PROTECTED]> writes:
> There is no way to decided the user/group and
> permission of the device created. (/etc/devfs.conf can
> be used, but it had to be start after the device is
> created, where it is not created at boot time).
devfs(8) rules should be automatically applied
