[LEDE-DEV] [PATCH] pages: add FAQ page
Hauke Mehrtens
hauke at hauke-m.de
Sat May 7 03:41:51 PDT 2016
On 05/06/2016 10:04 AM, Bruno Randolf wrote:
> Hi,
>
> Taking this from lede-adm to lede-dev where I'm allowed to post...
no problem.
> On 06/05/16 02:33, Alexander Couzens wrote:
>>> +== What devices does LEDE targets?
>>> +
>>> +LEDE mainly targets embedded devices capable of running Linux.
>> I agree.
>>
>>> In
>>> most cases wireless routers. This has not changed compared to
>>> OpenWrt.
>> I don't agree.
>>
>> "In most cases wireless routers. This has not changed
>> compared to OpenWrt".
>>
>> I would like to see LEDE supporting all cases of embedded systems like
>> routers, nas, kitchen radios :), [...]. IMHO it's changed it's
>> target compared to OpenWrt. But includes OpenWrt's use cases.
I do not think LEDE has changed its targeted devices from OpenWrt. I
have also seen OpenWrt on a desk phone, but this is not the normal use
case. The main use case is something that routes IP traffic. I have no
problem in supporting NAS devices and so on.
> I agree that OpenWRT has grown out of being just a distribution for
> wireless routers and the LEDE split is a good moment to make that clear.
> Also "wireless" more or less has become a standard component of many
> embedded devices.
>
> But more importantly: With the introduction of libubox, ubus, procd,
> UCI, netifd, etc OpenWRT has become more than a linux distribution, it
> has become a *platform*. What I mean with this that there are programs
> which depend on these libraries and components, especially ubus, and
> therefore can only meaningfully run on a OpenWRT/LEDE system. I have
> written several of those (one is https://github.com/br101/pingcheck) and
> I think this is a major difference to many linux distributions.
With this answer I wanted to point out that nothing really changed about
the targeted devices from OpenWrt to LEDE, because I was asked this
question. There were some changes, but they also apply to recent OpenWrt
versions and are not only related to LEDE.
Hauke
More information about the Lede-dev
mailing list