From nbd at nbd.name  Thu Jun  1 04:14:17 2017
From: nbd at nbd.name (Felix Fietkau)
Date: Thu, 1 Jun 2017 10:14:17 +0200
Subject: [OpenWrt-Devel] USB or SD card not mounted in Omega2+ router
	with LEDE iamge
In-Reply-To: <CAO4+10MiDibmT2m83h8yZ1TWbazujZj3SYhU0+qZsXijaom9Aw@mail.gmail.com>
References: <CAO4+10MiDibmT2m83h8yZ1TWbazujZj3SYhU0+qZsXijaom9Aw@mail.gmail.com>
Message-ID: <04d03866-aa8f-3ace-148e-bc76565db235@nbd.name>

On 2017-05-31 21:58, Arun Kumar wrote:
> Hi All,
> 
> I am facing an error where I can't find my USB or SD card and hence cant
> upgrade to a new image.
> 
> SD Card or USB device plugged in would be usually automounted at
> /tmp/mounts
> But after sysupgrading to the latest LEDE image, the Omega2+ router
> detects the USB device getting plugged in but doesnt display anywhere.
> Not even in /dev/sdaX location.
> 
> When I plugin a USB device, I get this message:
> [ 6382.201671] usb 1-1: new high-speed USB device number 3 using
> ehci-platform
Is kmod-usb-storage installed?

> Tried with both USB 1 and USB 2.0 devices. So tried to connect to Wifi
> and download new image. But iwconfig is not working.
> 
> root at Omega-FB25:/# iwconfig
> /bin/ash: iwconfig: not found
> 
> Note: This was working fine earlier and I did multiple image swaps
> between my personal built ones and official images. I upgraded image
> from Omega2+ image to LEDE image[1].
iwconfig is not part of the standard installation, you're not supposed
to use it to connect to networks anyway.
Changing /etc/config/wireless and using reload_config should be used
instead.
Please keep in mind that the wifi driver for mt7688 is still quite
buggy, so it won't work very well.
In latest snapshots it might work a bit better, but I don't think it's
stable yet.

- Felix
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From philipp_subx at redfish-solutions.com  Fri Jun  2 18:24:25 2017
From: philipp_subx at redfish-solutions.com (Philip Prindeville)
Date: Fri, 2 Jun 2017 16:24:25 -0600
Subject: [OpenWrt-Devel] [LEDE-DEV]    Remerge logo ideas
In-Reply-To: <018C9DAD-564F-4EC4-B08F-8ECD92DEF826@onebillion.org>
References: <018C9DAD-564F-4EC4-B08F-8ECD92DEF826@onebillion.org>
Message-ID: <29E82BDC-96DA-4E9A-ADF1-40CF33966499@redfish-solutions.com>

Can we add ?Powered by LEDE? in little tiny letters underneath?  ;-)


> On May 29, 2017, at 4:11 AM, Jamie Stuart <jamie at onebillion.org> wrote:
> 
> Hi,
> First of all, I?m glad to hear the process of remerging LEDE with OpenWrt is moving forward.
> For what it?s worth, if prefer the LEDE name (it?s friendlier - ?leddy? - and not tied to the name of an old router!)
> 
> However, it seems the consensus is that the OpenWrt name should remain. I thought that maybe we should take this opportunity to at least give the project an updated look?
> Maybe a new logo? I?m personally not one for mascots, so I had a quick go at a few simple text-based designs:
> 
> http://i.imgur.com/9zyXSYR.png
> 
> What are you thoughts?
> 
> Jamie, onebillion
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From carlosmf.pt at gmail.com  Sun Jun  4 20:57:10 2017
From: carlosmf.pt at gmail.com (Carlos Ferreira)
Date: Mon, 5 Jun 2017 01:57:10 +0100
Subject: [OpenWrt-Devel] [LEDE-DEV] Remerge logo ideas
In-Reply-To: <29E82BDC-96DA-4E9A-ADF1-40CF33966499@redfish-solutions.com>
References: <018C9DAD-564F-4EC4-B08F-8ECD92DEF826@onebillion.org>
 <29E82BDC-96DA-4E9A-ADF1-40CF33966499@redfish-solutions.com>
Message-ID: <CAJpYY6UrxhQFZe3FMGdJ9ZNmpkk57cAwu2pGn3H9KJ-O-EqS-Q@mail.gmail.com>

Julian, thank you for the correction. I truly thought that WRT was
from Wireless Router. I stand corrected :)

Bill, I understand that it would be a risk to change the name. I don't
mind that the project continues to use the OpenWRT brand. I just was
pointing out that it doesn't truly reflects what it is being used
today.

Let me give you an example.

About 3-4 years ago, when I was starting my PhD, I decided to use
OpenWRT to power about 32 VM's inside my computer. I wanted to test a
distributed network protocol that I had been developing for some time
in Python. Since OpenWRT has such a low memory footprint, It was the
perfect environment for me. I could test the network protocol with a
real linux kernel in a virtual network environment, having only 8GB of
RAM on the host.

I got to test the protocol and it worked. Then I used it in some SBC's
also with OpenWRT.



On 2 June 2017 at 23:24, Philip Prindeville
<philipp_subx at redfish-solutions.com> wrote:
> Can we add ?Powered by LEDE? in little tiny letters underneath?  ;-)
>
>
>> On May 29, 2017, at 4:11 AM, Jamie Stuart <jamie at onebillion.org> wrote:
>>
>> Hi,
>> First of all, I?m glad to hear the process of remerging LEDE with OpenWrt is moving forward.
>> For what it?s worth, if prefer the LEDE name (it?s friendlier - ?leddy? - and not tied to the name of an old router!)
>>
>> However, it seems the consensus is that the OpenWrt name should remain. I thought that maybe we should take this opportunity to at least give the project an updated look?
>> Maybe a new logo? I?m personally not one for mascots, so I had a quick go at a few simple text-based designs:
>>
>> http://i.imgur.com/9zyXSYR.png
>>
>> What are you thoughts?
>>
>> Jamie, onebillion
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel at lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel



-- 

Carlos Miguel Ferreira
Researcher at Telecommunications Institute
Aveiro - Portugal
Work E-mail - cmf at av.it.pt
Skype & GTalk -> carlosmf.pt at gmail.com
LinkedIn -> http://www.linkedin.com/in/carlosmferreira
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From david at lang.hm  Sun Jun  4 21:08:18 2017
From: david at lang.hm (David Lang)
Date: Sun, 4 Jun 2017 18:08:18 -0700 (PDT)
Subject: [OpenWrt-Devel] [LEDE-DEV] Remerge logo ideas
In-Reply-To: <CAJpYY6UrxhQFZe3FMGdJ9ZNmpkk57cAwu2pGn3H9KJ-O-EqS-Q@mail.gmail.com>
References: <018C9DAD-564F-4EC4-B08F-8ECD92DEF826@onebillion.org>
 <29E82BDC-96DA-4E9A-ADF1-40CF33966499@redfish-solutions.com>
 <CAJpYY6UrxhQFZe3FMGdJ9ZNmpkk57cAwu2pGn3H9KJ-O-EqS-Q@mail.gmail.com>
Message-ID: <nycvar.QRO.7.76.6.1706041807420.10272@qynat-yncgbc>

the vote on the name was held several months ago, please stop trying to re-do 
the vote just because it didn't come out the way you wanted it to.
k
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From carlosmf.pt at gmail.com  Sun Jun  4 23:06:03 2017
From: carlosmf.pt at gmail.com (Carlos Ferreira)
Date: Mon, 5 Jun 2017 04:06:03 +0100
Subject: [OpenWrt-Devel] [LEDE-DEV] Remerge logo ideas
In-Reply-To: <nycvar.QRO.7.76.6.1706041807420.10272@qynat-yncgbc>
References: <018C9DAD-564F-4EC4-B08F-8ECD92DEF826@onebillion.org>
 <29E82BDC-96DA-4E9A-ADF1-40CF33966499@redfish-solutions.com>
 <CAJpYY6UrxhQFZe3FMGdJ9ZNmpkk57cAwu2pGn3H9KJ-O-EqS-Q@mail.gmail.com>
 <nycvar.QRO.7.76.6.1706041807420.10272@qynat-yncgbc>
Message-ID: <CAJpYY6UxeFuJx_JP2redNQLdmnuKmyCxGC=+i7S5=-4fVE3XNw@mail.gmail.com>

I understand that and I had no intention to restart such discussion.
I'm sorry if what I wrote was misinterpreted as such. I didn't mean to.



On 5 June 2017 at 02:08, David Lang <david at lang.hm> wrote:
> the vote on the name was held several months ago, please stop trying to
> re-do the vote just because it didn't come out the way you wanted it to.
> k



-- 

Carlos Miguel Ferreira
Researcher at Telecommunications Institute
Aveiro - Portugal
Work E-mail - cmf at av.it.pt
Skype & GTalk -> carlosmf.pt at gmail.com
LinkedIn -> http://www.linkedin.com/in/carlosmferreira
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From feitingen at gmail.com  Tue Jun  6 08:13:14 2017
From: feitingen at gmail.com (Audun)
Date: Tue, 6 Jun 2017 14:13:14 +0200
Subject: [OpenWrt-Devel] [LEDE-DEV] Remerge logo ideas
In-Reply-To: <0a7315a0-f07d-3106-eb70-5cbaf10e2814@openwrt.org>
References: <018C9DAD-564F-4EC4-B08F-8ECD92DEF826@onebillion.org>
 <7d06a557-8732-30a1-285a-80af4651b3f2@phrozen.org>
 <CA4BD962-CB07-4DF0-B0D7-CAF55E596020@onebillion.org>
 <0a7315a0-f07d-3106-eb70-5cbaf10e2814@openwrt.org>
Message-ID: <CAMOt2ApSUVXwRLaHmgyzyY5tKE7CO60ekVmFJ_in9AQTd+XwBQ@mail.gmail.com>

On 29 May 2017 at 13:45, Imre Kaloz <kaloz at openwrt.org> wrote:

> On 2017-05-29 13:10, Jamie Stuart wrote:
>
>> See another iteration, with:
>>
>> - correct capitalisation
>> - antenna to the side (will not work with lowercase ?n?)
>> - open sans typeface (open source)
>> - mockups of website header
>> - accent colours
>>
>> http://i.imgur.com/ZKtcFXo.png
>>
>
> Nice :) Personally I like the darker color set of the last, but the layout
> of the first the most (when the "signal" is at the end).
>
>
> Imre
>
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel at lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>

That is a nice logo, I agree that the "signal" looks better on the end.

Personally, I like the colored schemes as well, perhaps they can be
implemented as themes in luci?

I've been wondering why there isn't more themes, is it because it's
particularly difficult, or is it because most people use the CLI anyways?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20170606/c3db282c/attachment.htm>
-------------- next part --------------
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From feitingen at gmail.com  Tue Jun  6 08:18:08 2017
From: feitingen at gmail.com (Audun)
Date: Tue, 6 Jun 2017 14:18:08 +0200
Subject: [OpenWrt-Devel] [LEDE-DEV] Remerge logo ideas
In-Reply-To: <0a7315a0-f07d-3106-eb70-5cbaf10e2814@openwrt.org>
References: <018C9DAD-564F-4EC4-B08F-8ECD92DEF826@onebillion.org>
 <7d06a557-8732-30a1-285a-80af4651b3f2@phrozen.org>
 <CA4BD962-CB07-4DF0-B0D7-CAF55E596020@onebillion.org>
 <0a7315a0-f07d-3106-eb70-5cbaf10e2814@openwrt.org>
Message-ID: <CAMOt2ArbFN12s6JoQZC88YDtva7YkAJFFEwb2nr8Y=eK1p0HRQ@mail.gmail.com>

On 29 May 2017 at 13:45, Imre Kaloz <kaloz at openwrt.org> wrote:
> On 2017-05-29 13:10, Jamie Stuart wrote:
>>
>> See another iteration, with:
>>
>> - correct capitalisation
>> - antenna to the side (will not work with lowercase ?n?)
>> - open sans typeface (open source)
>> - mockups of website header
>> - accent colours
>>
>> http://i.imgur.com/ZKtcFXo.png
>
>
> Nice :) Personally I like the darker color set of the last, but the layout
> of the first the most (when the "signal" is at the end).
>
>
> Imre
>

That is a nice logo, I agree that the "signal" looks better on the end.

Personally, I like the colored schemes as well, perhaps they can be
implemented as themes in luci?

I've been wondering why there isn't more themes, is it because it's
particularly difficult, or is it because most people use the CLI
anyways?
--
Best Regards,

Audun Gangsto
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From wigyori at uid0.hu  Tue Jun  6 09:43:46 2017
From: wigyori at uid0.hu (Zoltan HERPAI)
Date: Tue, 06 Jun 2017 15:43:46 +0200
Subject: [OpenWrt-Devel] [OpenWrt-Hackers] openwrt and lede - remerge
	proposal V3
In-Reply-To: <b3c97320-c241-606b-bdc5-560d3d026d67@phrozen.org>
References: <b3c97320-c241-606b-bdc5-560d3d026d67@phrozen.org>
Message-ID: <5936B192.4090105@uid0.hu>

Hi,

John Crispin wrote:
>
> Hi,
>
> here is a V3 of the remerge proposal, I tried to fold all the comments 
> people made into it, if anything is missing let me know. Please 
> remeber that post remerge anything can be voted on, so cluttering the 
> proposal with many details will delay the remerge even more.
>
> Ideally we manage to vote during this week.
[snip]

As this seems to have turned into a voting thread as discussed on IRC 
with John, an ACK from me as well on this v3.

Regards,
Zoltan H
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From liam at wiemax.net  Fri Jun  9 07:48:02 2017
From: liam at wiemax.net (Liam Dennehy)
Date: Fri, 09 Jun 2017 13:48:02 +0200
Subject: [OpenWrt-Devel] [PATCH] OpenVPN: Add TLS minimum and maximum version
Message-ID: <1497008882.12667.6.camel@wiemax.net>

OpenVPN Hardening Guide suggests limiting the TLS versions available to
clients. https://community.openvpn.net/openvpn/wiki/Hardening
This patch allows the OpenVPN init script to recognise tls-version-min
and tls-version-max configuration options in UCI for the generated config
file.

Signed-off-by: Liam Dennehy <liam at wiemax.net>
---
 package/network/services/openvpn/files/openvpn.init | 1 +
 1 file changed, 1 insertion(+)

diff --git a/package/network/services/openvpn/files/openvpn.init b/package/network/services/openvpn/files/openvpn.init
index 861d0d62b3..2e0f6e0696 100644
--- a/package/network/services/openvpn/files/openvpn.init
+++ b/package/network/services/openvpn/files/openvpn.init
@@ -123,6 +123,7 @@ start_instance() {
 		route_metric route_up rport script_security secret server server_bridge setenv shaper sndbuf \
 		socks_proxy status status_version syslog tcp_queue_limit tls_auth \
 		tls_cipher tls_remote tls_timeout tls_verify tmp_dir topology tran_window \
+		tls_version_min tls_version_max \
 		tun_mtu tun_mtu_extra txqueuelen user verb down push up \
 		ifconfig_ipv6 route_ipv6 server_ipv6 ifconfig_ipv6_pool ifconfig_ipv6_push iroute_ipv6
 
-- 
2.13.0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20170609/b3a756b8/attachment.htm>
-------------- next part --------------
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From Matthias.Strubel at aod-rpg.de  Fri Jun  9 10:52:36 2017
From: Matthias.Strubel at aod-rpg.de (Matthias Strubel)
Date: Fri, 9 Jun 2017 16:52:36 +0200
Subject: [OpenWrt-Devel] Future of opkg -d ; broken in BB, CC & LEDE17
Message-ID: <646cefd9-9199-cd0a-1d30-3b5cf346c23c@aod-rpg.de>

Hi OpenWrt developers,
I am writing this email to the OpenWrt-Dev mailing list only because I have the hope OpenWrt & LEDE will merge soon.. both versions are affected of the following.

On PirateBox & LibraryBox we are not using extroot techniques to enhance the firmware space, but we make use of the command

  opkg -d <dest>

We put the extended space into a file on the mounted FAT-USB stick, which is mounted via a looback device. The advantage for the Linux inexperienced PirateBox/LibraryBox users (focused group) is that they can easily exchange the USB stick (copy & paste) instead of dd'ing partitions or handling ext4 filesystems.

Yes, not every package has support for this, so I created a bunch of packages which bring those packages to life and it worked quite well on AA. 
I created shell extension to honour additional lib folder and extended PATH variable.. in additional to various linking from the rootfs to the extended space (/usr/local).
Mostly all of this handling was done in the postinst package step.

opkg propagates the -d destination to the package via the environment variable PKG_ROOT , not IPKG_INSTROOT . 
The package relevant information (opkg/info folder) is stored in $PKG_ROOT/usr/lib/opkg/info/

As far as I traced back the changes, with BB (or CC) a change was introduced and the package-postinst step was divided into postinst and postinst.pkg. 

How the default postinst function is written, it does not use PKG_ROOT in any case.
This change broke the -d function nearly completely, because

 a) PKG_ROOT is not used for the access to the info & control files
 b) postinst.pkg scripts are only executed from the / folder and $IPKG_INSTROOT  ; but the 


BTW: in current trunk (https://dev.openwrt.org/browser/trunk/package/base-files/files/lib/functions.sh)is a merge error @line 223 ; the section is duplicated in the source.


I am close to manually patch the file during our imagebuilder processing to solve the issues for the LibraryBox & PirateBox projects... but I am willing to provide a proper solution upstream.

Question: 
Does it makes sense for you to fix that, or is "opkg -d" more like an unwanted feature which will be removed in the future? 
(because classical extroot is "more convenient") 


Thank you,
Best regards
Matthias Strubel

BTW2: In addition, the default_postinst automatically enables new init.d .. even this is an unwanted behaviour, there is no way to avoid the auto-activation :-/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20170609/9059cd1d/attachment.sig>
-------------- next part --------------
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From yonhan at cisco.com  Fri Jun  9 16:13:58 2017
From: yonhan at cisco.com (Yongkui Han (yonhan))
Date: Fri, 9 Jun 2017 20:13:58 +0000
Subject: [OpenWrt-Devel] how to commit a diff to openwrt
Message-ID: <bf4c265b658e4cca8b3fcc218623605c@XCH-RTP-010.cisco.com>

Hi openwrt community,

I have tried to reach Steven Barth (cyrus at openwrt.org<mailto:cyrus at openwrt.org>) for a diff to enable ASLR PIE support for openwrt. I did not get response, instead I got the below reject message.

550 5.1.1 <cyrus at openwrt.org<mailto:cyrus at openwrt.org>>: Recipient address rejected: User unknown in virtual mailbox table

So I would like to try this mailing list to seek advices on how to proceed. Your help would be greatly appreciated.

I have read the below two wiki links:

https://wiki.openwrt.org/doc/howto/submittingpatches
https://dev.openwrt.org/wiki/SubmittingPatches

as long as I follow the steps in the above links, that is, to send my patches to the openwrt-devel at lists.openwrt.org<mailto:openwrt-devel at lists.openwrt.org> mailing list, then it should be fine, right?

Thanks,
Yongkui

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20170609/57f8bab2/attachment.htm>
-------------- next part --------------
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From wigyori at uid0.hu  Fri Jun  9 16:43:23 2017
From: wigyori at uid0.hu (Zoltan HERPAI)
Date: Fri, 09 Jun 2017 22:43:23 +0200
Subject: [OpenWrt-Devel] how to commit a diff to openwrt
In-Reply-To: <bf4c265b658e4cca8b3fcc218623605c@XCH-RTP-010.cisco.com>
References: <bf4c265b658e4cca8b3fcc218623605c@XCH-RTP-010.cisco.com>
Message-ID: <593B086B.8050103@uid0.hu>

Hello Yongkui,

Yongkui Han (yonhan) wrote:
>
> Hi openwrt community,
>
>  
>
> I have tried to reach Steven Barth (cyrus at openwrt.org 
> <mailto:cyrus at openwrt.org>) for a diff to enable ASLR PIE support for 
> openwrt. I did not get response, instead I got the below reject message.
>
>  
>
> 550 5.1.1 <cyrus at openwrt.org <mailto:cyrus at openwrt.org>>: Recipient 
> address rejected: User unknown in virtual mailbox table
>
>  
>
> So I would like to try this mailing list to seek advices on how to 
> proceed. Your help would be greatly appreciated.
>
>  
>
> I have read the below two wiki links:
>
>  
>
> https://wiki.openwrt.org/doc/howto/submittingpatches
>
> https://dev.openwrt.org/wiki/SubmittingPatches
>
>  
>
> as long as I follow the steps in the above links, that is, to send my 
> patches to the openwrt-devel at lists.openwrt.org 
> <mailto:openwrt-devel at lists.openwrt.org> mailing list, then it should 
> be fine, right?
>
>  
>
Correct, if you have a larger patchset, please send it to openwrt-devel 
so people on the list could comment on it and it'll be picked up by the 
patchwork. If you have smaller patchset (f.e. trivial fixes), you can 
also send pull requests against the OpenWrt github tree 
(https://github.com/openwrt/openwrt). I've added Steven into cc, too.

Thanks,
Zoltan H
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From yonhan at cisco.com  Fri Jun  9 16:47:51 2017
From: yonhan at cisco.com (Yongkui Han (yonhan))
Date: Fri, 9 Jun 2017 20:47:51 +0000
Subject: [OpenWrt-Devel] how to commit a diff to openwrt
In-Reply-To: <593B086B.8050103@uid0.hu>
References: <bf4c265b658e4cca8b3fcc218623605c@XCH-RTP-010.cisco.com>
 <593B086B.8050103@uid0.hu>
Message-ID: <19acbdfc42114c2ca486a1d7df7db3a8@XCH-RTP-010.cisco.com>

Hi Zoltan,

Thanks for your quick response. My patch is a trivial diff, so I think it is easier to create a pull request. I will contact Steven with his new email address for more details.

Thanks,
Yongkui


-----Original Message-----
From: Zoltan HERPAI [mailto:wigyori at uid0.hu] 
Sent: Friday, June 09, 2017 4:43 PM
To: Yongkui Han (yonhan) <yonhan at cisco.com>
Cc: openwrt-devel at lists.openwrt.org; steven at midlink.org
Subject: Re: [OpenWrt-Devel] how to commit a diff to openwrt

Hello Yongkui,

Yongkui Han (yonhan) wrote:
>
> Hi openwrt community,
>
>  
>
> I have tried to reach Steven Barth (cyrus at openwrt.org
> <mailto:cyrus at openwrt.org>) for a diff to enable ASLR PIE support for 
> openwrt. I did not get response, instead I got the below reject message.
>
>  
>
> 550 5.1.1 <cyrus at openwrt.org <mailto:cyrus at openwrt.org>>: Recipient 
> address rejected: User unknown in virtual mailbox table
>
>  
>
> So I would like to try this mailing list to seek advices on how to 
> proceed. Your help would be greatly appreciated.
>
>  
>
> I have read the below two wiki links:
>
>  
>
> https://wiki.openwrt.org/doc/howto/submittingpatches
>
> https://dev.openwrt.org/wiki/SubmittingPatches
>
>  
>
> as long as I follow the steps in the above links, that is, to send my 
> patches to the openwrt-devel at lists.openwrt.org 
> <mailto:openwrt-devel at lists.openwrt.org> mailing list, then it should 
> be fine, right?
>
>  
>
Correct, if you have a larger patchset, please send it to openwrt-devel so people on the list could comment on it and it'll be picked up by the patchwork. If you have smaller patchset (f.e. trivial fixes), you can also send pull requests against the OpenWrt github tree (https://github.com/openwrt/openwrt). I've added Steven into cc, too.

Thanks,
Zoltan H
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From hauke at hauke-m.de  Sat Jun 10 09:13:25 2017
From: hauke at hauke-m.de (Hauke Mehrtens)
Date: Sat, 10 Jun 2017 15:13:25 +0200
Subject: [OpenWrt-Devel] LEDE call for vote on remerge proposal V3
In-Reply-To: <88bfa9e9-634f-f504-bdc3-e01185c4acaa@phrozen.org>
References: <88bfa9e9-634f-f504-bdc3-e01185c4acaa@phrozen.org>
Message-ID: <19048138-1a1f-f243-4fc1-b8c5163709a8@hauke-m.de>

Hi,

As many already acknowledged this proposal I would like to call for an
official vote among the LEDE committers till 14.6.2017 on this proposal.
I counted the following replays to the proposal already as an
acknowledgment:
Steven, Matthias, Stijn, Hauke, Florian, Daniel, Hans, John, Rafa?,
Felix, Alexander, Piotr
If you till ack it, you do not have to do it again.

I haven't seen any NACK among the LEDE committers till now.

If this will get accepted by the LEDE committers and also the OpenWrt
core developers accept it, I would like the OpenWrt core developers
start with migrating the openwrt.org domain to the SPI as a first step.

Hauke

On 05/29/2017 09:03 AM, John Crispin wrote:
> (resend, this time as plain text)
> 
> Hi,
> 
> here is a V3 of the remerge proposal, I tried to fold all the comments
> people made into it, if anything is missing let me know. Please remeber
> that post remerge anything can be voted on, so cluttering the proposal
> with many details will delay the remerge even more.
> 
> Ideally we manage to vote during this week.
> 
> 
>         John
> 
> *) rules
> - owrt will adopt the lede rules and voting system
> 
> *) branding
> - the owrt side sees no option of using the lede brand
> - a (minor) majority voted for openwrt as a name over lede whilst most
> people said they did not care
> - as the last vote had a 100% ACK for a remerge using the owrt brand is
> the only feasible option
> 
> *) domain
> - transfer owner ship to SPI for openwrt.org and lede-project.org
> - add them to the pool of urls at digital ocean
> - post remerge build a setup where we have several DNS servers in
> various locations
> - point git.openwrt.org at the lede git server
> - point bugs.openwrt.org to the lede flyspray instance
> - keep both wikis and forums as is (we should decide post remerge how to
> proceed to avoid these issues blocking the progress)
> - update the lede domain entries for build/download/rsync/... servers so
> that the openwrt domain also points at them
> 
> *) SPI
> - nominate a new liaison team (imre and john offer to do this, if anyone
> else is interested let us know)
> - inform SPI of the new liaisons, voters and project rules
> - this should be done early in the remerge process s.t. the domains can
> be handed over
> 
> *) github
> - start pushing to the openwrt organisation
> - cleanup the list of owners in the openwrt organisation
> - obsolete all issues on the openwrt organisation and close the issue
> tracker
> - go through the open openwrt and lede PRs, pickup whats useful and
> close the rest, asking people to repost (things wont be rebasable anyhow)
> - close the lede PR tracker
> - obsolete the lede github org after a grace period of 3-6 months
> 
> *) landing page
> - add a letter of intent / notice to both current landing pages
> announcing the remerge
> - update the lede landing page to represent the openwrt name
> - update the landing page to have the same look & feel as the current
> openwrt landing page
> - point openwrt.org at the lede landing page
> - try to find some design guru that will transform the owrt theme to one
> appropriate to this century
> 
> *) trac
> - trac is already readonly, keep content so that search engines can
> still find the it
> - edit the trac html templates, adding a note pointing at the
> bug.openwrt.org instance
> 
> *) IRC
> - add back cloaking
> - give people channel ownership/admin rights
> 
> *) email accounts
> - currently there are around ~20 active openwrt.org mail accounts (the 3
> owrt devs would like to keep theirs active)
> - turn all the webmaster@, hostmaster@, ... accounts into aliases that
> anyone with voting rights can be subscribed to
> - ask those people that are no longer active to voluntarily give up
> their accounts
> - mail addresses may under no conditions be used for any personal
> business, consultancy, applying for jobs, ... purposes
> - any mail sent from an openwrt.org account needs to adhere the
> trademark policy and should only be used for FOSS purposes
> 
> *) wiki / forum
> - TBD
> - asking in either forum/wiki will get a biased vote so keep them both
> around
> - start a separate discussion regarding these post remerge
> 
> *) LF
> - find out what doubts folks have about LF
> - find out benefits - we would have their hosting and sponsorship ?!
> - start a separate discussion regarding these post remerge
> 
> *) git trees
> - rebrand the lede tree to openwrt
> - work out what has happened inside the openwrt tree since the reboot
> and pick up the useful bits (zoltan has done some prior work on this
> already)
> 
> *) mailing list
> - ask david to add the openwrt-adm and openwrt lists
> - send out invitation mails to the new list
> - setup redirect/auto-reply for the existing lists
> 
> *) trademark policy
> - review/ack imres trademark policy (https://openwrt.org/trademark)
> 
> *) timeline
> - vote / agree on the proposal within the next week
> - work on the action items in the 4 weeks after that
> 
>     John
> 
> 
> 
> _______________________________________________
> Lede-dev mailing list
> Lede-dev at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev
> 
> 
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel at lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> 
> 
> _______________________________________________
> lede-adm mailing list
> lede-adm at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-adm
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From zajec5 at gmail.com  Mon Jun 12 07:24:53 2017
From: zajec5 at gmail.com (=?UTF-8?q?Rafa=C5=82=20Mi=C5=82ecki?=)
Date: Mon, 12 Jun 2017 13:24:53 +0200
Subject: [OpenWrt-Devel] [PATCH packages] minidlna: update to 1.2.0
Message-ID: <20170612112453.7225-1-zajec5@gmail.com>

From: Rafa? Mi?ecki <rafal at milecki.pl>

It contains compatibility/support for few more clients (including Kodi)
and introduces rescan support (useful for devices with limited CPU
power).

Signed-off-by: Rafa? Mi?ecki <rafal at milecki.pl>
---
 multimedia/minidlna/Makefile | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/multimedia/minidlna/Makefile b/multimedia/minidlna/Makefile
index 2eef5e50..e007af3c 100644
--- a/multimedia/minidlna/Makefile
+++ b/multimedia/minidlna/Makefile
@@ -8,15 +8,13 @@
 include $(TOPDIR)/rules.mk
 
 PKG_NAME:=minidlna
-PKG_VERSION:=1.1.6+git-8a996b
+PKG_VERSION:=1.2.0
 PKG_RELEASE:=1
 
-PKG_SOURCE_PROTO:=git
-PKG_SOURCE_URL=http://git.code.sf.net/p/minidlna/git
+PKG_SOURCE_URL:=@SF/minidlna
 PKG_SOURCE_SUBDIR=$(PKG_NAME)-$(PKG_VERSION)
-PKG_SOURCE_VERSION:=8a996b4b624ef45538a5de10730b8e94c55e7768
-PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.xz
-PKG_MIRROR_HASH:=fddbb7c96b40e335a251b919ff5c674519f266a59b8a43011761ba952c0df1b6
+PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
+PKG_HASH:=8d34436580c4c44be25976d5e46bc5b71af69bf441c4492774eac001164c4433
 
 PKG_LICENSE:=GPL-2.0 BSD-3-Clause
 PKG_LICENSE_FILES:=COPYING LICENCE.miniupnpd
-- 
2.11.0
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From zajec5 at gmail.com  Mon Jun 12 08:13:08 2017
From: zajec5 at gmail.com (=?UTF-8?q?Rafa=C5=82=20Mi=C5=82ecki?=)
Date: Mon, 12 Jun 2017 14:13:08 +0200
Subject: [OpenWrt-Devel] [PATCH V2 packages] minidlna: update to 1.2.0
In-Reply-To: <20170612112453.7225-1-zajec5@gmail.com>
References: <20170612112453.7225-1-zajec5@gmail.com>
Message-ID: <20170612121308.21801-1-zajec5@gmail.com>

From: Rafa? Mi?ecki <rafal at milecki.pl>

It contains compatibility/support for few more clients (including Kodi)
and introduces rescan support (useful for devices with limited CPU
power).

Signed-off-by: Rafa? Mi?ecki <rafal at milecki.pl>
---
V2: Refresh patches
---
 multimedia/minidlna/Makefile                                   | 10 ++++------
 .../001-group-videos-by-directory-for-panasonic-tvs.patch      | 10 +++++-----
 multimedia/minidlna/patches/002-dont-build-po-files.patch      |  3 +--
 3 files changed, 10 insertions(+), 13 deletions(-)

diff --git a/multimedia/minidlna/Makefile b/multimedia/minidlna/Makefile
index 2eef5e50..e007af3c 100644
--- a/multimedia/minidlna/Makefile
+++ b/multimedia/minidlna/Makefile
@@ -8,15 +8,13 @@
 include $(TOPDIR)/rules.mk
 
 PKG_NAME:=minidlna
-PKG_VERSION:=1.1.6+git-8a996b
+PKG_VERSION:=1.2.0
 PKG_RELEASE:=1
 
-PKG_SOURCE_PROTO:=git
-PKG_SOURCE_URL=http://git.code.sf.net/p/minidlna/git
+PKG_SOURCE_URL:=@SF/minidlna
 PKG_SOURCE_SUBDIR=$(PKG_NAME)-$(PKG_VERSION)
-PKG_SOURCE_VERSION:=8a996b4b624ef45538a5de10730b8e94c55e7768
-PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.xz
-PKG_MIRROR_HASH:=fddbb7c96b40e335a251b919ff5c674519f266a59b8a43011761ba952c0df1b6
+PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
+PKG_HASH:=8d34436580c4c44be25976d5e46bc5b71af69bf441c4492774eac001164c4433
 
 PKG_LICENSE:=GPL-2.0 BSD-3-Clause
 PKG_LICENSE_FILES:=COPYING LICENCE.miniupnpd
diff --git a/multimedia/minidlna/patches/001-group-videos-by-directory-for-panasonic-tvs.patch b/multimedia/minidlna/patches/001-group-videos-by-directory-for-panasonic-tvs.patch
index 5380d8a3..f36edde4 100644
--- a/multimedia/minidlna/patches/001-group-videos-by-directory-for-panasonic-tvs.patch
+++ b/multimedia/minidlna/patches/001-group-videos-by-directory-for-panasonic-tvs.patch
@@ -11,7 +11,7 @@ Subject: [PATCH] Add support for grouping videos by directory for Panasonic
 
 --- a/upnpsoap.c
 +++ b/upnpsoap.c
-@@ -1052,6 +1052,15 @@ callback(void *args, int argc, char **ar
+@@ -1095,6 +1095,15 @@ callback(void *args, int argc, char **ar
  						add_res(size, duration, bitrate, sampleFrequency, nrAudioChannels,
  						        resolution, dlna_buf, mime, detailID, ext, passed_args);
  					}
@@ -27,7 +27,7 @@ Subject: [PATCH] Add support for grouping videos by directory for Panasonic
  					break;
  				case ESamsungSeriesCDE:
  				case ELGDevice:
-@@ -1314,8 +1323,11 @@ BrowseContentDirectory(struct upnphttp *
+@@ -1357,8 +1366,11 @@ BrowseContentDirectory(struct upnphttp *
  		if (!where[0])
  			sqlite3_snprintf(sizeof(where), where, "PARENT_ID = '%q'", ObjectID);
  
@@ -40,13 +40,13 @@ Subject: [PATCH] Add support for grouping videos by directory for Panasonic
  		ret = 0;
  		if (SortCriteria && !orderBy)
  		{
-@@ -1354,14 +1366,16 @@ BrowseContentDirectory(struct upnphttp *
+@@ -1397,14 +1409,16 @@ BrowseContentDirectory(struct upnphttp *
  			SoapError(h, 709, "Unsupported or invalid sort criteria");
  			goto browse_error;
  		}
 -
  		sql = sqlite3_mprintf("SELECT %s, %s, %s, " COLUMNS
- 		                      "from OBJECTS o left join DETAILS d on (d.ID = o.DETAIL_ID)"
+ 				      "from OBJECTS o left join DETAILS d on (d.ID = o.DETAIL_ID)"
 -				      " where %s %s limit %d, %d;",
 +				      " where %s order by d.date limit %d, %d;",
  				      objectid_sql, parentid_sql, refid_sql,
@@ -60,7 +60,7 @@ Subject: [PATCH] Add support for grouping videos by directory for Panasonic
  	}
  	if( (ret != SQLITE_OK) && (zErrMsg != NULL) )
  	{
-@@ -1795,7 +1809,7 @@ SearchContentDirectory(struct upnphttp *
+@@ -1838,7 +1852,7 @@ SearchContentDirectory(struct upnphttp *
  	                      (*ContainerID == '*') ? NULL :
  	                      sqlite3_mprintf("UNION ALL " SELECT_COLUMNS
  	                                      "from OBJECTS o left join DETAILS d on (d.ID = o.DETAIL_ID)"
diff --git a/multimedia/minidlna/patches/002-dont-build-po-files.patch b/multimedia/minidlna/patches/002-dont-build-po-files.patch
index c0c02358..38623246 100644
--- a/multimedia/minidlna/patches/002-dont-build-po-files.patch
+++ b/multimedia/minidlna/patches/002-dont-build-po-files.patch
@@ -9,10 +9,9 @@
  
  sbin_PROGRAMS = minidlnad
  check_PROGRAMS = testupnpdescgen
- 
 --- a/configure.ac
 +++ b/configure.ac
-@@ -633,6 +633,8 @@ case "$target_os" in
+@@ -644,6 +644,8 @@ case "$target_os" in
  esac
  
  
-- 
2.11.0
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From yonhan at cisco.com  Mon Jun 12 09:26:34 2017
From: yonhan at cisco.com (Yongkui Han (yonhan))
Date: Mon, 12 Jun 2017 13:26:34 +0000
Subject: [OpenWrt-Devel] [PATCH] [packages] Support for building a hardened
 OpenWRT with ASLR PIE support
Message-ID: <95fe7a1257cb470aaa5380224024d785@XCH-RTP-010.cisco.com>

From: Yongkui Han <yonhan at cisco.com>

Introduce a configuration option to build a "hardened" OpenWRT with ASLR PIE support.

A new option PKG_ASLR_PIE to enable Address Space Layout Randomization (ASLR)
Position Independent Executables (PIE) support has been introduced.
This new option protects against "return-to-text" attacks.

Tested with GCC 4.4.7, uClibc and a subset of the available packages.

Signed-off-by: Yongkui Han <yonhan at cisco.com>
---
config/Config-build.in    |   15 +++++++++++++++
include/hardened-build-ld |    2 ++
include/hardening.mk      |    7 +++++++
3 files changed, 24 insertions(+)

diff --git a/config/Config-build.in b/config/Config-build.in
index 23cf83b..fa7ecfb 100644
--- a/config/Config-build.in
+++ b/config/Config-build.in
@@ -221,6 +221,21 @@ menu "Global build settings"
                     this per package by adding PKG_CHECK_FORMAT_SECURITY:=0 in the package
                     Makefile.
+        config PKG_ASLR_PIE
+                  bool
+                  prompt "User space ASLR PIE compilation"
+                  default n
+                  help
+                    Add -fPIC to CFLAGS and -specs=hardened-build-ld to LDFLAGS.
+                    This enables package build as Position Independent Executables (PIE)
+                    to protect against "return-to-text" attacks. This belongs to the
+                    feature of Address Space Layout Randomisation (ASLR), which is
+                    implemented by the kernel and the ELF loader by randomising the
+                    location of memory allocations. This makes memory addresses harder
+                    to predict when an attacker is attempting a memory-corruption exploit.
+                    You can disable this per package by adding PKG_ASLR_PIE:=0 in the package
+                    Makefile.
+
         choice
                   prompt "User space Stack-Smashing Protection"
                   depends on USE_MUSL
diff --git a/include/hardening.mk b/include/hardening.mk
index c277081..7b09c3e 100644
--- a/include/hardening.mk
+++ b/include/hardening.mk
@@ -6,6 +6,7 @@
#
 PKG_CHECK_FORMAT_SECURITY ?= 1
+PKG_ASLR_PIE ?= 1
PKG_SSP ?= 1
PKG_FORTIFY_SOURCE ?= 1
PKG_RELRO ?= 1
@@ -15,6 +16,12 @@ ifdef CONFIG_PKG_CHECK_FORMAT_SECURITY
     TARGET_CFLAGS += -Wformat -Werror=format-security
   endif
endif
+ifdef CONFIG_PKG_ASLR_PIE
+  ifeq ($(strip $(PKG_ASLR_PIE)),1)
+    TARGET_CFLAGS += -fPIC
+    TARGET_LDFLAGS += -specs=$(INCLUDE_DIR)/hardened-build-ld
+  endif
+endif
ifdef CONFIG_PKG_CC_STACKPROTECTOR_REGULAR
   ifeq ($(strip $(PKG_SSP)),1)
     TARGET_CFLAGS += -fstack-protector
diff --git a/include/hardened-build-ld b/include/hardened-build-ld
new file mode 100644
index 0000000..97dbd92
--- /dev/null
+++ b/include/hardened-build-ld
@@ -0,0 +1,2 @@
+*self_spec:
++ %{!static:%{!shared:-pie}}

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20170612/f748c461/attachment.htm>
-------------- next part --------------
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From jo at mein.io  Tue Jun 13 05:36:51 2017
From: jo at mein.io (Jo-Philipp Wich)
Date: Tue, 13 Jun 2017 11:36:51 +0200
Subject: [OpenWrt-Devel] openwrt and lede - remerge proposal V3
In-Reply-To: <b3c97320-c241-606b-bdc5-560d3d026d67@phrozen.org>
References: <b3c97320-c241-606b-bdc5-560d3d026d67@phrozen.org>
Message-ID: <c6e7bef5-5ebe-34ea-3ee8-e3a05a45884d@mein.io>

Hi,

NACK from me - not that it makes a difference but I do not like to
operate under the OpenWrt name.

~ Jo
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From f.fainelli at gmail.com  Tue Jun 13 15:58:17 2017
From: f.fainelli at gmail.com (Florian Fainelli)
Date: Tue, 13 Jun 2017 12:58:17 -0700
Subject: [OpenWrt-Devel] openwrt and lede - remerge proposal V3
In-Reply-To: <b3c97320-c241-606b-bdc5-560d3d026d67@phrozen.org>
References: <b3c97320-c241-606b-bdc5-560d3d026d67@phrozen.org>
Message-ID: <238f7d2c-3b90-7c5b-0eb4-76c0fc27280e@gmail.com>

On 05/28/2017 11:56 PM, John Crispin wrote:
> Hi,
> 
> here is a V3 of the remerge proposal, I tried to fold all the comments
> people made into it, if anything is missing let me know. Please remeber
> that post remerge anything can be voted on, so cluttering the proposal
> with many details will delay the remerge even more.
> 
> Ideally we manage to vote during this week.

ACK from me.
-- 
Florian
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From john at phrozen.org  Wed Jun 14 01:43:29 2017
From: john at phrozen.org (John Crispin)
Date: Wed, 14 Jun 2017 07:43:29 +0200
Subject: [OpenWrt-Devel] openwrt and lede - remerge proposal V3
In-Reply-To: <238f7d2c-3b90-7c5b-0eb4-76c0fc27280e@gmail.com>
References: <b3c97320-c241-606b-bdc5-560d3d026d67@phrozen.org>
 <238f7d2c-3b90-7c5b-0eb4-76c0fc27280e@gmail.com>
Message-ID: <41558b03-574e-42b0-b24d-bd16dcb16fae@phrozen.org>



On 13/06/17 21:58, Florian Fainelli wrote:
> On 05/28/2017 11:56 PM, John Crispin wrote:
>> Hi,
>>
>> here is a V3 of the remerge proposal, I tried to fold all the comments
>> people made into it, if anything is missing let me know. Please remeber
>> that post remerge anything can be voted on, so cluttering the proposal
>> with many details will delay the remerge even more.
>>
>> Ideally we manage to vote during this week.
> ACK from me.
ACK from me also.
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From mbm at openwrt.org  Thu Jun 15 01:23:07 2017
From: mbm at openwrt.org (Mike Baker)
Date: Wed, 14 Jun 2017 22:23:07 -0700
Subject: [OpenWrt-Devel] [OpenWrt-Hackers] openwrt and lede - remerge
 proposal V3
In-Reply-To: <41558b03-574e-42b0-b24d-bd16dcb16fae@phrozen.org>
References: <b3c97320-c241-606b-bdc5-560d3d026d67@phrozen.org>
 <238f7d2c-3b90-7c5b-0eb4-76c0fc27280e@gmail.com>
 <41558b03-574e-42b0-b24d-bd16dcb16fae@phrozen.org>
Message-ID: <bbcee7f3-3f60-39d0-6fb5-a3ef7ed189d5@openwrt.org>

On 6/13/2017 10:43 PM, John Crispin wrote:
> On 13/06/17 21:58, Florian Fainelli wrote:
>> On 05/28/2017 11:56 PM, John Crispin wrote:
>>> Hi,
>>>
>>> here is a V3 of the remerge proposal, I tried to fold all the comments
>>> people made into it, if anything is missing let me know. Please remeber
>>> that post remerge anything can be voted on, so cluttering the proposal
>>> with many details will delay the remerge even more.
>>>
>>> Ideally we manage to vote during this week.
>> ACK from me.
> ACK from me also.
ACK.
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From jonas.gorski at gmail.com  Thu Jun 15 05:20:33 2017
From: jonas.gorski at gmail.com (Jonas Gorski)
Date: Thu, 15 Jun 2017 11:20:33 +0200
Subject: [OpenWrt-Devel] openwrt and lede - remerge proposal V3
In-Reply-To: <88bfa9e9-634f-f504-bdc3-e01185c4acaa@phrozen.org>
References: <88bfa9e9-634f-f504-bdc3-e01185c4acaa@phrozen.org>
Message-ID: <CAOiHx==atPBo2sZBCvpvb05-ovfacjNww=T8GgmAzBFsPTKcfA@mail.gmail.com>

On 29 May 2017 at 09:03, John Crispin <john at phrozen.org> wrote:
> (resend, this time as plain text)
>
>
> Hi,
>
> here is a V3 of the remerge proposal, I tried to fold all the comments
> people made into it, if anything is missing let me know. Please remeber that
> post remerge anything can be voted on, so cluttering the proposal with many
> details will delay the remerge even more.
>
> Ideally we manage to vote during this week.
>
>
>         John
>
> *) rules
> - owrt will adopt the lede rules and voting system
>
> *) branding
> - the owrt side sees no option of using the lede brand
> - a (minor) majority voted for openwrt as a name over lede whilst most
> people said they did not care
> - as the last vote had a 100% ACK for a remerge using the owrt brand is the
> only feasible option
>
> *) domain
> - transfer owner ship to SPI for openwrt.org and lede-project.org
> - add them to the pool of urls at digital ocean
> - post remerge build a setup where we have several DNS servers in various
> locations
> - point git.openwrt.org at the lede git server
> - point bugs.openwrt.org to the lede flyspray instance
> - keep both wikis and forums as is (we should decide post remerge how to
> proceed to avoid these issues blocking the progress)
> - update the lede domain entries for build/download/rsync/... servers so
> that the openwrt domain also points at them
>
> *) SPI
> - nominate a new liaison team (imre and john offer to do this, if anyone
> else is interested let us know)
> - inform SPI of the new liaisons, voters and project rules
> - this should be done early in the remerge process s.t. the domains can be
> handed over
>
> *) github
> - start pushing to the openwrt organisation
> - cleanup the list of owners in the openwrt organisation
> - obsolete all issues on the openwrt organisation and close the issue
> tracker
> - go through the open openwrt and lede PRs, pickup whats useful and close
> the rest, asking people to repost (things wont be rebasable anyhow)
> - close the lede PR tracker
> - obsolete the lede github org after a grace period of 3-6 months
>
> *) landing page
> - add a letter of intent / notice to both current landing pages announcing
> the remerge
> - update the lede landing page to represent the openwrt name
> - update the landing page to have the same look & feel as the current
> openwrt landing page
> - point openwrt.org at the lede landing page
> - try to find some design guru that will transform the owrt theme to one
> appropriate to this century
>
> *) trac
> - trac is already readonly, keep content so that search engines can still
> find the it
> - edit the trac html templates, adding a note pointing at the
> bug.openwrt.org instance
>
> *) IRC
> - add back cloaking
> - give people channel ownership/admin rights
>
> *) email accounts
> - currently there are around ~20 active openwrt.org mail accounts (the 3
> owrt devs would like to keep theirs active)
> - turn all the webmaster@, hostmaster@, ... accounts into aliases that
> anyone with voting rights can be subscribed to
> - ask those people that are no longer active to voluntarily give up their
> accounts
> - mail addresses may under no conditions be used for any personal business,
> consultancy, applying for jobs, ... purposes
> - any mail sent from an openwrt.org account needs to adhere the trademark
> policy and should only be used for FOSS purposes
>
> *) wiki / forum
> - TBD
> - asking in either forum/wiki will get a biased vote so keep them both
> around
> - start a separate discussion regarding these post remerge
>
> *) LF
> - find out what doubts folks have about LF
> - find out benefits - we would have their hosting and sponsorship ?!
> - start a separate discussion regarding these post remerge
>
> *) git trees
> - rebrand the lede tree to openwrt
> - work out what has happened inside the openwrt tree since the reboot and
> pick up the useful bits (zoltan has done some prior work on this already)
>
> *) mailing list
> - ask david to add the openwrt-adm and openwrt lists
> - send out invitation mails to the new list
> - setup redirect/auto-reply for the existing lists
>
> *) trademark policy
> - review/ack imres trademark policy (https://openwrt.org/trademark)
>
> *) timeline
> - vote / agree on the proposal within the next week
> - work on the action items in the 4 weeks after that
>
>     John

ACK from me.


Regards
Jonas
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From kaloz at openwrt.org  Tue Jun 20 16:49:28 2017
From: kaloz at openwrt.org (Imre Kaloz)
Date: Tue, 20 Jun 2017 22:49:28 +0200
Subject: [OpenWrt-Devel] [OpenWrt-Hackers] openwrt and lede - remerge
 proposal V3
In-Reply-To: <41558b03-574e-42b0-b24d-bd16dcb16fae@phrozen.org>
References: <b3c97320-c241-606b-bdc5-560d3d026d67@phrozen.org>
 <238f7d2c-3b90-7c5b-0eb4-76c0fc27280e@gmail.com>
 <41558b03-574e-42b0-b24d-bd16dcb16fae@phrozen.org>
Message-ID: <7651b777-b434-842a-adb0-195cfab4e057@openwrt.org>

On 2017-06-14 07:43, John Crispin wrote:
> 
> 
> On 13/06/17 21:58, Florian Fainelli wrote:
>> On 05/28/2017 11:56 PM, John Crispin wrote:
>>> Hi,
>>>
>>> here is a V3 of the remerge proposal, I tried to fold all the comments
>>> people made into it, if anything is missing let me know. Please remeber
>>> that post remerge anything can be voted on, so cluttering the proposal
>>> with many details will delay the remerge even more.
>>>
>>> Ideally we manage to vote during this week.
>> ACK from me.
> ACK from me also.
ACK from me, too.
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From c.lobrano at gmail.com  Thu Jun 22 03:40:37 2017
From: c.lobrano at gmail.com (Carlo Lobrano)
Date: Thu, 22 Jun 2017 09:40:37 +0200
Subject: [OpenWrt-Devel] [PATCH] uqmi_add_command: fixed command argument
	assignment
Message-ID: <20170622074037.14512-1-c.lobrano@gmail.com>

The char *arg passed to uqmi_add_command was not assigned to cmd[idx].arg.

---

Hi,

I saw this little bug. Hope this is the right place to submit the patch

Best regards,
Carlo

---

 commands.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/commands.c b/commands.c
index f9545a9..8e9810d 100644
--- a/commands.c
+++ b/commands.c
@@ -193,7 +193,7 @@ void uqmi_add_command(char *arg, int cmd)
 
 	cmds = realloc(cmds, n_cmds * sizeof(*cmds));
 	cmds[idx].handler = &uqmi_cmd_handler[cmd];
-	cmds[idx].arg = optarg;
+	cmds[idx].arg = arg;
 }
 
 static void uqmi_print_result(struct blob_attr *data)
-- 
2.9.3
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From hauke at hauke-m.de  Mon Jun 26 17:59:52 2017
From: hauke at hauke-m.de (Hauke Mehrtens)
Date: Mon, 26 Jun 2017 23:59:52 +0200
Subject: [OpenWrt-Devel] [LEDE-DEV] LEDE call for vote on remerge
	proposal V3
In-Reply-To: <19048138-1a1f-f243-4fc1-b8c5163709a8@hauke-m.de>
References: <88bfa9e9-634f-f504-bdc3-e01185c4acaa@phrozen.org>
 <19048138-1a1f-f243-4fc1-b8c5163709a8@hauke-m.de>
Message-ID: <331ff812-7bc2-9384-001e-0f02924723f5@hauke-m.de>

On 06/10/2017 03:13 PM, Hauke Mehrtens wrote:
> Hi,
> 
> As many already acknowledged this proposal I would like to call for an
> official vote among the LEDE committers till 14.6.2017 on this proposal.
> I counted the following replays to the proposal already as an
> acknowledgment:
> Steven, Matthias, Stijn, Hauke, Florian, Daniel, Hans, John, Rafa?,
> Felix, Alexander, Piotr
> If you till ack it, you do not have to do it again.
> 
> I haven't seen any NACK among the LEDE committers till now.
> 
> If this will get accepted by the LEDE committers and also the OpenWrt
> core developers accept it, I would like the OpenWrt core developers
> start with migrating the openwrt.org domain to the SPI as a first step.
> 
> Hauke

Sorry it took me longer to count the votes. ;-)

The remerge proposal was acknowledged by the following LEDE developers:
Steven, Matthias, Stijn, Hauke, Florian, Daniel, Hans, John, Rafa?,
Felix, Alexander, Piotr and Jonas (13)

In addition it was acknowledged by the following OpenWrt hackers:
Zoltan, Miken, Imre and Matteo (4)

The following people I was unable to put into one of these groups also
acknowledged it: ;-)
Koen, Vincenzo, Alexandru and Eric (4)

I counted one Not acknowledge:
Jow (1)

I used this list for the LEDE developers:
https://lede-project.org/about#people

With that vote the remerge is officially approved by the LEDE developers
and also by the OpenWrt hackers.


As a first step I would like to see the openwrt.org domain being
transfered to the Software in the Public Interest, Inc (SPI) so the SPI
can take the ownership of the domain in the name of the project, like
they do for the debian.org domain name.
Imre will you take care of this please.

Imre and John volunteered to represent us at the SPI. As I haven't read
anybody having a problem with that in the mail threads, I assume that
this is ok with everyone. Imre and John can you please also work on this
topic. If anyone wants a formal vote on this or would like to have other
people representing us please speak up now.

Hauke

> 
> On 05/29/2017 09:03 AM, John Crispin wrote:
>> (resend, this time as plain text)
>>
>> Hi,
>>
>> here is a V3 of the remerge proposal, I tried to fold all the comments
>> people made into it, if anything is missing let me know. Please remeber
>> that post remerge anything can be voted on, so cluttering the proposal
>> with many details will delay the remerge even more.
>>
>> Ideally we manage to vote during this week.
>>
>>
>>         John
>>
>> *) rules
>> - owrt will adopt the lede rules and voting system
>>
>> *) branding
>> - the owrt side sees no option of using the lede brand
>> - a (minor) majority voted for openwrt as a name over lede whilst most
>> people said they did not care
>> - as the last vote had a 100% ACK for a remerge using the owrt brand is
>> the only feasible option
>>
>> *) domain
>> - transfer owner ship to SPI for openwrt.org and lede-project.org
>> - add them to the pool of urls at digital ocean
>> - post remerge build a setup where we have several DNS servers in
>> various locations
>> - point git.openwrt.org at the lede git server
>> - point bugs.openwrt.org to the lede flyspray instance
>> - keep both wikis and forums as is (we should decide post remerge how to
>> proceed to avoid these issues blocking the progress)
>> - update the lede domain entries for build/download/rsync/... servers so
>> that the openwrt domain also points at them
>>
>> *) SPI
>> - nominate a new liaison team (imre and john offer to do this, if anyone
>> else is interested let us know)
>> - inform SPI of the new liaisons, voters and project rules
>> - this should be done early in the remerge process s.t. the domains can
>> be handed over
>>
>> *) github
>> - start pushing to the openwrt organisation
>> - cleanup the list of owners in the openwrt organisation
>> - obsolete all issues on the openwrt organisation and close the issue
>> tracker
>> - go through the open openwrt and lede PRs, pickup whats useful and
>> close the rest, asking people to repost (things wont be rebasable anyhow)
>> - close the lede PR tracker
>> - obsolete the lede github org after a grace period of 3-6 months
>>
>> *) landing page
>> - add a letter of intent / notice to both current landing pages
>> announcing the remerge
>> - update the lede landing page to represent the openwrt name
>> - update the landing page to have the same look & feel as the current
>> openwrt landing page
>> - point openwrt.org at the lede landing page
>> - try to find some design guru that will transform the owrt theme to one
>> appropriate to this century
>>
>> *) trac
>> - trac is already readonly, keep content so that search engines can
>> still find the it
>> - edit the trac html templates, adding a note pointing at the
>> bug.openwrt.org instance
>>
>> *) IRC
>> - add back cloaking
>> - give people channel ownership/admin rights
>>
>> *) email accounts
>> - currently there are around ~20 active openwrt.org mail accounts (the 3
>> owrt devs would like to keep theirs active)
>> - turn all the webmaster@, hostmaster@, ... accounts into aliases that
>> anyone with voting rights can be subscribed to
>> - ask those people that are no longer active to voluntarily give up
>> their accounts
>> - mail addresses may under no conditions be used for any personal
>> business, consultancy, applying for jobs, ... purposes
>> - any mail sent from an openwrt.org account needs to adhere the
>> trademark policy and should only be used for FOSS purposes
>>
>> *) wiki / forum
>> - TBD
>> - asking in either forum/wiki will get a biased vote so keep them both
>> around
>> - start a separate discussion regarding these post remerge
>>
>> *) LF
>> - find out what doubts folks have about LF
>> - find out benefits - we would have their hosting and sponsorship ?!
>> - start a separate discussion regarding these post remerge
>>
>> *) git trees
>> - rebrand the lede tree to openwrt
>> - work out what has happened inside the openwrt tree since the reboot
>> and pick up the useful bits (zoltan has done some prior work on this
>> already)
>>
>> *) mailing list
>> - ask david to add the openwrt-adm and openwrt lists
>> - send out invitation mails to the new list
>> - setup redirect/auto-reply for the existing lists
>>
>> *) trademark policy
>> - review/ack imres trademark policy (https://openwrt.org/trademark)
>>
>> *) timeline
>> - vote / agree on the proposal within the next week
>> - work on the action items in the 4 weeks after that
>>
>>     John
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From hauke at hauke-m.de  Tue Jun 27 16:55:05 2017
From: hauke at hauke-m.de (Hauke Mehrtens)
Date: Tue, 27 Jun 2017 22:55:05 +0200
Subject: [OpenWrt-Devel] [LEDE-DEV] LEDE call for vote on remerge
	proposal V3
In-Reply-To: <331ff812-7bc2-9384-001e-0f02924723f5@hauke-m.de>
References: <88bfa9e9-634f-f504-bdc3-e01185c4acaa@phrozen.org>
 <19048138-1a1f-f243-4fc1-b8c5163709a8@hauke-m.de>
 <331ff812-7bc2-9384-001e-0f02924723f5@hauke-m.de>
Message-ID: <a7e69b5c-f684-00d1-6770-0e493faa031a@hauke-m.de>

On 06/26/2017 11:59 PM, Hauke Mehrtens wrote:
> On 06/10/2017 03:13 PM, Hauke Mehrtens wrote:
>> Hi,
>>
>> As many already acknowledged this proposal I would like to call for an
>> official vote among the LEDE committers till 14.6.2017 on this proposal.
>> I counted the following replays to the proposal already as an
>> acknowledgment:
>> Steven, Matthias, Stijn, Hauke, Florian, Daniel, Hans, John, Rafa?,
>> Felix, Alexander, Piotr
>> If you till ack it, you do not have to do it again.
>>
>> I haven't seen any NACK among the LEDE committers till now.
>>
>> If this will get accepted by the LEDE committers and also the OpenWrt
>> core developers accept it, I would like the OpenWrt core developers
>> start with migrating the openwrt.org domain to the SPI as a first step.
>>
>> Hauke
> 
> Sorry it took me longer to count the votes. ;-)
> 
> The remerge proposal was acknowledged by the following LEDE developers:
> Steven, Matthias, Stijn, Hauke, Florian, Daniel, Hans, John, Rafa?,
> Felix, Alexander, Piotr and Jonas (13)
> 
> In addition it was acknowledged by the following OpenWrt hackers:
> Zoltan, Miken, Imre and Matteo (4)

John told me that OpenWrt is currently only represented by Imre, Luka
und Zoltan, so Matteo and Mike then probably go into the next category,
but this does not change the end result.

> The following people I was unable to put into one of these groups also
> acknowledged it: ;-)
> Koen, Vincenzo, Alexandru and Eric (4)
> 
> I counted one Not acknowledge:
> Jow (1)
> 
> I used this list for the LEDE developers:
> https://lede-project.org/about#people
> 
> With that vote the remerge is officially approved by the LEDE developers
> and also by the OpenWrt hackers.
> 
> 
> As a first step I would like to see the openwrt.org domain being
> transfered to the Software in the Public Interest, Inc (SPI) so the SPI
> can take the ownership of the domain in the name of the project, like
> they do for the debian.org domain name.
> Imre will you take care of this please.

Transferring the openwrt.org domain to the SPI is seen as a prerequisite
before the next steps will be taken by the LEDE developers.

@Imre: I assume this needs multiple steps, could you please update us on
the status of transferring the openwrt.org domain to the SPI please.

> Imre and John volunteered to represent us at the SPI. As I haven't read
> anybody having a problem with that in the mail threads, I assume that
> this is ok with everyone. Imre and John can you please also work on this
> topic. If anyone wants a formal vote on this or would like to have other
> people representing us please speak up now.

John said that he would represent the merged project at the SPI.

Hauke
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From giometti at linux.it  Wed Jun 28 04:49:00 2017
From: giometti at linux.it (Rodolfo Giometti)
Date: Wed, 28 Jun 2017 10:49:00 +0200
Subject: [OpenWrt-Devel] add support for sysfs settings at boot
Message-ID: <20170628084901.640-1-giometti@linux.it>

This patch adds support for sysfs settings at boot into package
sysfsutils as the same name Debian package does.
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

From giometti at linux.it  Wed Jun 28 04:49:01 2017
From: giometti at linux.it (Rodolfo Giometti)
Date: Wed, 28 Jun 2017 10:49:01 +0200
Subject: [OpenWrt-Devel] [PATCH 1/1] package sysfsutils: add support for
	sysfs settings at boot
In-Reply-To: <20170628084901.640-1-giometti@linux.it>
References: <20170628084901.640-1-giometti@linux.it>
Message-ID: <20170628084901.640-2-giometti@linux.it>

This patch is based on sysfsutils package's behaviour on Debian OS.

Signed-off-by: Rodolfo Giometti <giometti at linux.it>
---
 package/libs/sysfsutils/Makefile         | 12 ++++++++
 package/libs/sysfsutils/files/local.conf |  1 +
 package/libs/sysfsutils/files/sysfs.conf | 22 +++++++++++++++
 package/libs/sysfsutils/files/sysfsutils | 48 ++++++++++++++++++++++++++++++++
 4 files changed, 83 insertions(+)
 create mode 100644 package/libs/sysfsutils/files/local.conf
 create mode 100644 package/libs/sysfsutils/files/sysfs.conf
 create mode 100644 package/libs/sysfsutils/files/sysfsutils

diff --git a/package/libs/sysfsutils/Makefile b/package/libs/sysfsutils/Makefile
index 9ee76a0362..6d74d0bbfc 100644
--- a/package/libs/sysfsutils/Makefile
+++ b/package/libs/sysfsutils/Makefile
@@ -65,9 +65,21 @@ define Package/libsysfs/install
 endef
 
 define Package/sysfsutils/install
+	$(INSTALL_DIR) $(1)/etc/init.d
+	$(INSTALL_BIN) ./files/sysfsutils $(1)/etc/init.d/
+
+	$(INSTALL_DATA) ./files/sysfs.conf $(1)/etc/
+	$(INSTALL_DIR) $(1)/etc/sysfs.d
+	$(INSTALL_DATA) ./files/local.conf $(1)/etc/sysfs.d/
+
 	$(INSTALL_DIR) $(1)/usr/bin
 	$(CP) $(PKG_INSTALL_DIR)/usr/bin/systool $(1)/usr/bin/
 endef
 
+define Package/sysfsutils/conffiles
+/etc/sysfs.conf
+/etc/sysfs.d/local.conf
+endef
+
 $(eval $(call BuildPackage,libsysfs))
 $(eval $(call BuildPackage,sysfsutils))
diff --git a/package/libs/sysfsutils/files/local.conf b/package/libs/sysfsutils/files/local.conf
new file mode 100644
index 0000000000..891da73df8
--- /dev/null
+++ b/package/libs/sysfsutils/files/local.conf
@@ -0,0 +1 @@
+# local sysctl settings can be stored in this directory
diff --git a/package/libs/sysfsutils/files/sysfs.conf b/package/libs/sysfsutils/files/sysfs.conf
new file mode 100644
index 0000000000..f03246284f
--- /dev/null
+++ b/package/libs/sysfsutils/files/sysfs.conf
@@ -0,0 +1,22 @@
+#
+# /etc/sysfs.conf - Configuration file for setting sysfs attributes.
+#
+# The sysfs mount directory is automatically prepended to the attribute paths.
+#
+# Syntax:
+# attribute = value
+# mode attribute = 0600 # (any valid argument for chmod)
+# owner attribute = root:wheel # (any valid argument for chown)
+#
+# Examples:
+#
+# Always use the powersave CPU frequency governor
+# devices/system/cpu/cpu0/cpufreq/scaling_governor = powersave
+#
+# Use userspace CPU frequency governor and set initial speed
+# devices/system/cpu/cpu0/cpufreq/scaling_governor = userspace
+# devices/system/cpu/cpu0/cpufreq/scaling_setspeed = 600000
+#
+# Set permissions of suspend control file
+# mode power/state = 0660
+# owner power/state = root:power
diff --git a/package/libs/sysfsutils/files/sysfsutils b/package/libs/sysfsutils/files/sysfsutils
new file mode 100644
index 0000000000..0305ca82a9
--- /dev/null
+++ b/package/libs/sysfsutils/files/sysfsutils
@@ -0,0 +1,48 @@
+#!/bin/sh /etc/rc.common
+# Copyright (C) 2017 Rodolfo Giometti <giometti at enneenne.com>
+#
+# Based on Debian's script /etc/init.d/sysfsutils by
+# Martin Pitt <mpitt at debian.org>
+
+load_conffile() {
+	FILE="$1"
+	sed  's/#.*$//; /^[[:space:]]*$/d;
+	  s/^[[:space:]]*\([^=[:space:]]*\)[[:space:]]*\([^=[:space:]]*\)[[:space:]]*=[[:space:]]*\(.*\)/\1 \2 \3/' \
+	  $FILE | {
+	while read f1 f2 f3; do
+		if [ "$f1" = "mode" -a -n "$f2" -a -n "$f3" ]; then
+			if [ -f "/sys/$f2" ] || [ -d "/sys/$f2" ]; then
+				chmod "$f3" "/sys/$f2"
+			else
+				echo "unknown attribute $f2"
+			fi
+		elif [ "$f1" = "owner" -a -n "$f2" -a -n "$f3" ]; then
+			if [ -f "/sys/$f2" ]; then
+				chown "$f3" "/sys/$f2"
+			else
+				echo "unknown attribute $f2"
+			fi
+		elif [ "$f1" -a -n "$f2" -a -z "$f3" ]; then
+			if [ -f "/sys/$f1" ]; then
+				# Some fields need a terminating newline, others
+				# need the terminating newline to be absent :-(
+				echo -n "$f2" > "/sys/$f1" 2>/dev/null ||
+					echo "$f2" > "/sys/$f1"
+			else
+				echo "unknown attribute $f1"
+			fi
+		else
+			echo "syntax error in $CONFFILE: '$f1' '$f2' '$f3'"
+			exit 1
+		fi
+	done
+	}
+}
+
+START=11
+start() {
+	for file in /etc/sysfs.conf /etc/sysfs.d/*.conf; do
+		[ -r "$file" ] || continue
+		load_conffile "$file"
+	done
+}
-- 
2.11.0
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

