News for hackers. Stuff that matters.

A comment on Introducing the LEDE project – A reboot of the OpenWrt community. Parent comment

Re:Introducing the LEDE project – A reboot of the OpenWrt co... by stephengillie on Tuesday May 03, 2016 @08:27PM (#11625328)
They could use BSD underneath, like JunOS and Netscaler run on.

But maybe an operating system is too large in scope. You're right that these devices only run one application, why use a tool (operating system) that can run many applications?

It's a bit like running a hypervisor for only one operating system. There are benefits, true.

[ Parent | on HN ]
Re:Introducing the LEDE project – A reboot of the OpenWrt co... by jlgaddis on Tuesday May 03, 2016 @11:20PM (#11625920)
Well, there's the kernel, which handles flinging packets between interfaces, filtering, etc., but your average router has lots of services it provides as well: DHCP, DNS, file/print sharing via USB ports, etc.
[ Parent | on HN ]
Re:Introducing the LEDE project – A reboot of the OpenWrt co... by stephengillie on Wednesday May 04, 2016 @12:47PM (#11629617)
Right, and the Kernel could just provide those. No need to write something to load extra code from storage and run it.
[ Parent | on HN ]
Re:Introducing the LEDE project – A reboot of the OpenWrt co... by easp on Thursday May 05, 2016 @04:49AM (#11634706)
Loading even more functionality into the kernel is at odds with security, stability and maintainability. Its also not going to save much/any in the way of resources.
[ Parent | on HN ]
Re:Introducing the LEDE project – A reboot of the OpenWrt co... by easp on Thursday May 05, 2016 @04:44AM (#11634694)
A big part of the OpenWRT project is hardware support for wireless chipsets and SoCs.

Sure, they could move all that to BSD, but then if they wanted to do that, why didn't they do that in the first place, rather than working on Linux?

[ Parent | on HN ]