We don't really have anything that corresponds to netpoll's
connections at higher levels.
I'm tempted to say we should make this work more like the dummy
network device. ie:
modprobe netconsole -o netcon1 [params]
modprobe netconsole -o netcon2 [params]
The configuration of netconsole's looks like the configuration of routes.
Granted you probably have more routes than netconsoles, but the interface
issues are similar. Netlink with a small application wouldn't be nice.
And having /proc/net/netconsole (read-only) would be good for the netlink
impaired.
Do you say that we had better use procfs instead of sysfs to show the
configurations of netconsole?
If so, I have a question.
I thought that "procfs use things related to process as far as possible".
Is it no problem to use procfs here?
--
Keiichi KII
NEC Corporation OSS Promotion Center
E-mail: [email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
