Re: [LEDE-DEV] procd: cherry-pick kernel watchdog start/stop to lede-17.01 branch

> On Jul 12, 2017, at 12:24 PM, Matthias Schiffer > wrote: > > On 07/12/2017 08:02 PM, Philip Prindeville wrote: >> >>> On Jul 11, 2017, at 3:19 AM, Hans Dedecker wrote: >>> >>> Hi, >>> >>> I would like to cherry-pick the

Re: [LEDE-DEV] procd: cherry-pick kernel watchdog start/stop to lede-17.01 branch

> On Jul 11, 2017, at 3:19 AM, Hans Dedecker wrote: > > Hi, > > I would like to cherry-pick the start/stop kernel watchdog support to > the lede-17.01 procd branch : > > e5e99c4 watchdog: add support for starting/stopping kernel watchdog > > It allows to gracefully stop the kernel watchdog vi

[LEDE-DEV] Procd questions

I came up with the following PR (https://github.com/openwrt/packages/pull/4568) thinking it would be a trivial substitution of the procd primitives for what the old shell script was doing. Turns out, I wasn’t even close. The problem turned out to be that when start_service() had exited, procd h

[LEDE-DEV] glibc finally fixes /etc/resolv.conf handling

For everyone who has ever wondered why they need to stop and restart long running services when they move from one network to another (as is common for laptops using Wifi that are roaming around), this can be quite vexing. The reason was that /etc/resolv.conf would get rewritten by DHCP when you

Re: [LEDE-DEV] Planning v17.01.2

> On May 25, 2017, at 10:59 AM, Lucian Cristian wrote: > > On 24.05.2017 23:34, Jo-Philipp Wich wrote: >> Hi, >> >> I'd like to start preparing the v17.01.2 release during the upcoming >> weekend with the goal to release final binaries within the next week >> (~May 29th till June 3rd). >> >> C

Re: [LEDE-DEV] [OpenWrt-Devel] Remerge logo ideas

Can we add “Powered by LEDE” in little tiny letters underneath? ;-) > On May 29, 2017, at 4:11 AM, Jamie Stuart 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 - ‘le

Re: [LEDE-DEV] [PATCH] add --extend-squasfs to qemustart script

Inline > On May 22, 2017, at 6:23 AM, Paul Spooren wrote: > > scripts/qemustart > > using squashfs results in a "no space left on device" error. You need to > manually extend the new build with a tool like dd. > > This patch adds the --extend-squasfs parameter to enlarge the image to > 64MB. T

Re: [LEDE-DEV] Problem with commit "kernel: add hwmon for W83627EHF and family"

y don't like this one as it's totally unclear why we need this >> change. What's wrong with NCT6775 and the w83627ehf driver? It should >> be well described in the patch. > > Sorry for the lack of a more detailed description. > The problem here is that th

Re: [LEDE-DEV] Scripted builds -- package selections reset by "make defconfig oldconfig"

> On May 17, 2017, at 11:35 AM, Philip Prindeville > wrote: > > [snip] Ignore the title, I forgot to update that: it’s actually the “scripts/feeds update” which is clobbering the .config. ___ Lede-dev mailing list Lede-dev@lists.i

[LEDE-DEV] Scripted builds -- package selections reset by "make defconfig oldconfig"

Hi. I have a requirement to be able to clone a snapshot of an Ubuntu 16.04-2 VM which has all of the appropriate packages already installed on it, scp over a build script, run it, and copy out the $(TOPDIR)/bin/targets/ directory when done and then destroy the VM. From a working (development)

Re: [LEDE-DEV] [PATCH v2 00/19] Universal staged sysupgrade and assorted fixes

> On May 13, 2017, at 1:56 PM, Matthias Schiffer > wrote: > > Text from my RFC mail: > > --- > When talking about > https://bugs.lede-project.org/index.php?do=details&task_id=685 with jow > and lynxis, we came to the conclusion that the best way to fix sysupgrades > would be to generalize the

[LEDE-DEV] Supporting RT linux

I was trying to apply the linux 4.9.20-rt16 patchset… This is as far as I got. I applied it as 000-… Applying /home/philipp/bertram/lede/target/linux/generic/patches-4.9/721-phy_packets.patch using plaintext: patching file include/linux/netdevice.h Hunk #1 succeeded at 1409 (offset 12 lines

Re: [LEDE-DEV] openwrt and lede - remerge proposal

> On May 12, 2017, at 6:02 AM, Edwin van Drunen wrote: > > I understand that the vote is done amongst the developers, the people > actually running the project, this makes sense. > But if the goal of the project is not only to keep yourself busy, but also to > target a larger audience, it make

Re: [LEDE-DEV] openwrt and lede - remerge proposal

> On May 11, 2017, at 10:09 PM, Eric Luehrsen wrote: > > People don't like rules and that could be even more true with open > source work groups. However, a good set of _limited_ rules can make life > easier. You may focus on important work or joyful recreation while not > worrying about acci

Re: [LEDE-DEV] [OpenWrt-Devel] openwrt and lede - remerge proposal

> On May 11, 2017, at 1:06 PM, Philip Prindeville > wrote: > > Yeah, I have to agree with this. You don’t get married, then define your > vows afterwards… Actually, sticking with the “marriage” paradigm a bit longer, what are the assets that the OpenWRT family brings to

Re: [LEDE-DEV] openwrt and lede - remerge proposal

> On May 11, 2017, at 4:53 AM, Stijn Segers > wrote: > > Some of the OpenWrt veterans come across as if they want the re-merge to be > rushed, ignoring the actual issues that caused the fork in the first place. Yeah, I have to agree with this. You don’t get married, then define your vows a

Re: [LEDE-DEV] openwrt and lede - remerge proposal

> On May 8, 2017, at 7:19 AM, John Crispin wrote: > > Hi, > > Felix, Imre and myself had 2 calls last week lasting several hours and > discussed the following proposal of conditions for a remerge that we would > like to propose and have people vote on. > > *) branding > - the owrt side sees

Re: [LEDE-DEV] openwrt and lede - remerge proposal

> On May 8, 2017, at 7:29 AM, David Woodhouse wrote: > > On Mon, 2017-05-08 at 15:19 +0200, John Crispin wrote: >> >> *) mailing list >> - ask david to add the openwrt-adm and openwrt lists >> - announce the switch to the infradead serves, asking people to >> unsubscribe if they have privacy i

[LEDE-DEV] Stalled PR #977 -- patch-kernel.sh: handle broken tarballs w/ 444 mode files

Can I please get closure on this trivial PR? https://github.com/lede-project/source/pull/977 Thanks. -Philip ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/

Re: [LEDE-DEV] [PATCH 5/7] firewall3: add UBUS support for ipset sections

> On May 2, 2017, at 6:15 AM, Pierre Lebleu wrote: > > Hi Philip, > > 2017-04-29 3:11 GMT+02:00 Philip Prindeville > : > Inline… > > > [snip] > > + if (!(ipset = fw3_alloc_ipset(state))) > > > Minor nit… Assignments inside of co

Re: [LEDE-DEV] Asterisk Update

Please fix the “no newline at end-of-file” issue. ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] Asterisk update

Please fix the no newline at end-of-file issue. ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH ubox v2] logread: Add support for output template

Inline… > On Apr 27, 2017, at 5:33 PM, Henry Chang wrote: > > From: Henry Chang > > Signed-off-by: Henry Chang > --- > log/logread.c | 153 -- > 1 file changed, 127 insertions(+), 26 deletions(-) > > diff --git a/log/logread.c b/log/log

Re: [LEDE-DEV] [PATCH 6/7] firewall3: add UBUS support for include scripts

Inline… > On Apr 20, 2017, at 10:05 AM, Pierre Lebleu wrote: > > It gives the ability to include scripts via procd > services and netifd interface firewall data. > > Signed-off-by: Pierre Lebleu > --- > includes.c | 64 +--- > includes.

Re: [LEDE-DEV] [PATCH 5/7] firewall3: add UBUS support for ipset sections

Inline… > On Apr 20, 2017, at 10:05 AM, Pierre Lebleu wrote: > > It gives the ability to create ipset rules via procd > services and netifd interface firewall data. > > Signed-off-by: Pierre Lebleu > --- > ipsets.c | 83 +++--- > ipsets

Re: [LEDE-DEV] [PATCH ubox] Add template support to logread

> On Apr 26, 2017, at 11:23 PM, Henry Chang wrote: > > Hi, > > I would like to integrate logd to the cloud logging service. The > service only accepts special format of syslog, so then I make logread > support template. > > Here's the usage: > > logread -T "<%priority%> %source% %message% %ti

Re: [LEDE-DEV] [PATCH 1/3] Handle SRV questions

> On Apr 26, 2017, at 3:45 AM, Cristian Morales Vega > wrote: > > Signed-off-by: Cristian Morales Vega > --- > dns.c | 14 ++ > 1 file changed, 14 insertions(+) > > diff --git a/dns.c b/dns.c > index d384f58..61ea8e3 100644 > --- a/dns.c > +++ b/dns.c > @@ -390,6 +390,20 @@ parse_q

[LEDE-DEV] modules-boot.d question and indeterminate drive # assignment

Hi. I’m seeing something weird… I’ve been working on adding kexec/kdump support to LEDE, adding some scripts to make this turn-key, etc. and in the process I’ve uncovered something a little bizarre (and unsettling). If I have a box (in this case an x86 box with a CompactFlash [CF]) drive and

Re: [LEDE-DEV] [RFC 01/13] procd: prepare NAND sysupgrade for making upgraded dynamically linked

Inline… > On Apr 24, 2017, at 2:20 PM, Matthias Schiffer > wrote: > > On 04/24/2017 10:05 PM, Philip Prindeville wrote: >> Inline… >> >>> On Apr 23, 2017, at 6:06 PM, Matthias Schiffer >>> wrote: >>> >>> Use install_bin to copy up

Re: [LEDE-DEV] [RFC 07/13] fstools: snapshot: handle jffs2 conversion using upgraded

Inline… > On Apr 23, 2017, at 6:06 PM, Matthias Schiffer > wrote: > > We can reuse the kill_remaining and run_ramfs facilities of the stage2 run > by upgraded. > > Signed-off-by: Matthias Schiffer > --- > package/system/fstools/Makefile | 2 +- > package/system/fstools/files/snapshot |

Re: [LEDE-DEV] [RFC 01/13] procd: prepare NAND sysupgrade for making upgraded dynamically linked

Inline… > On Apr 23, 2017, at 6:06 PM, Matthias Schiffer > wrote: > > Use install_bin to copy upgraded with all dependencies. The old name > /tmp/upgraded is temporarily retained as a symlink to avoid breaking > things. > > Signed-off-by: Matthias Schiffer > --- > package/system/procd/files/n

Re: [LEDE-DEV] update asterisk

> On Apr 19, 2017, at 3:10 PM, Knall Kopf wrote: > > Hello, > can everybody update the feed/telephony.git to the newest Asterisk and Libpri > libary version ? > For security reason it should be always the newest version. > > I have attach a patch where i have do it. > (some Asterisk patches ar

Re: [LEDE-DEV] [PATCH] openssl: Remove RIPEMD-160 from OpenSSL

> On Mar 28, 2017, at 12:09 AM, Alexandru Ardelean > wrote: > > On Tue, Mar 28, 2017 at 1:45 AM, txt.file wrote: >> The topic and patch is about OpenSSL but description is about OpenSSH. >> What has OpenSSL to do with OpenSSH? >> >> kind regards >> txt.file >> -- >> This message is signed. >>

Re: [LEDE-DEV] Removing package overlay functionality

> On Apr 16, 2017, at 9:51 PM, Yousong Zhou wrote: > > On 17 April 2017 at 10:38, Philip Prindeville > wrote: >> commit b044bd5921e9644c9df9655bef10cee0af730724 >> Author: Felix Fietkau >> Date: Mon Apr 3 12:36:35 2017 +0200 >> >>build: rem

[LEDE-DEV] Removing package overlay functionality

commit b044bd5921e9644c9df9655bef10cee0af730724 Author: Felix Fietkau Date: Mon Apr 3 12:36:35 2017 +0200 build: remove package makefile overlay functionality Recent attempts to use it have shown that it does not work properly except for a few undocumented cases. It's better to

Re: [LEDE-DEV] /tmp/sysupgrade

> On Apr 10, 2017, at 6:43 AM, John Crispin wrote: > > > > On 10/04/17 14:25, Kenneth Johansson wrote: >> I found that we touch the file /tmp/sysupgrade in a few places >> >> --- >> >> git grep "tmp/sysupgrade" | grep touch >> package/base-files/files/sbin/sysupgrade:touch /tmp/sysupgrade >>

Re: [LEDE-DEV] MT7621: EdgerouterX

nerator connected and to other is > the reflector connected. > > Thanks Milan > > > On Thu, Mar 30, 2017 at 8:11 PM, Philip Prindeville > wrote: >> What happens if you allocate more buffers and increase your watermarks but >> leave the maximum latency the same? >

Re: [LEDE-DEV] MT7621: EdgerouterX

What happens if you allocate more buffers and increase your watermarks but leave the maximum latency the same? > On Mar 30, 2017, at 11:53 AM, Milan Kočvara wrote: > > Hello. > I have 2 Question, please > 1. It is possible to rewrite the driver for MT761 to allow change the MTU > greather t

Re: [LEDE-DEV] [PATCH] kernel: Add iTCO_wdt watchdog timer module support

Did you look at: https://github.com/openwrt/openwrt/pull/326 it might be easier just to cherry-pick this in. > On Mar 11, 2017, at 3:48 PM, mich...@michaelmarley.com wrote: > > From: Michael Marley > > This supports the Intel TCO Watchdog Timer Device, which has been > nearly ubiquitous in I

Re: [LEDE-DEV] Supporting crashdumps w/ kexec

Inline… > On Mar 9, 2017, at 12:35 PM, monster_phi...@redfish-solutions.com wrote: > > >> On Mar 8, 2017, at 8:32 PM, Luiz Angelo Daros de Luca >> wrote: >> >> 1st: Is where does /boot get unmounted, and is there an easy way to >> keep it around a bit longer, at least until the init.d script

Re: [LEDE-DEV] Using Conflicts:

> On Mar 9, 2017, at 3:25 AM, Jo-Philipp Wich wrote: > > Hi, > >> Is there a reason we don’t use Conflicts: information from the >> packaging to stop overlapping installs from being selected when doing >> a build? > > yes. The buildroot uses Kconfig logic, while Conflicts: is an opkg concept.

[LEDE-DEV] Using Conflicts:

Is there a reason we don’t use Conflicts: information from the packaging to stop overlapping installs from being selected when doing a build? I understand that the buildbots build everything… but it should be possible to differentiate between ’y’ and ‘m’ and detect to packages providing the sam

Re: [LEDE-DEV] Support for more than a single overlay, which is selected at boot time

> On Mar 7, 2017, at 6:15 AM, Jurgen Van Ham wrote: > > Hi all, > > I want to support multiple (currently just two) configurations on a > single device. One of these configurations is chosen at boot time. > Instead of saving and restoring the configuration each time, I came up > with a solution

Re: [LEDE-DEV] [RFC] sysntpd: restore support for peer-less (standalone) mode

> On Mar 6, 2017, at 3:20 PM, Piotr Dymacz wrote: > > ntpd from Busybox supports peer-less (standalone) mode when it's started > with option -l and without any peer provided with option -p. In this > mode ntpd uses local time as reference and acts as stratum 1 server. > > This mode can be used

Re: [LEDE-DEV] Supporting crashdumps w/ kexec

> On Mar 8, 2017, at 10:23 AM, David Woodhouse wrote: > > On Wed, 2017-03-08 at 10:20 -0700, Philip Prindeville wrote: >> >> Then… grub reads the raw file system? > > Well, grub has to load the kernel before the kernel is running…. So, what would be involved in

Re: [LEDE-DEV] Supporting crashdumps w/ kexec

> On Mar 8, 2017, at 1:12 AM, David Woodhouse wrote: > > On Tue, 2017-03-07 at 17:40 -0700, Philip Prindeville wrote: >> >> First, obviously, is that kexec needs access to the boot partition to >> reuse the kernel (since most of our architectures support reloca

Re: [LEDE-DEV] [PATCH 00/12] alternatives support

> On Mar 7, 2017, at 6:47 PM, Yousong Zhou wrote: > > The usefulness of such availability only makes sense when it is going > to at least have an actual user. Feel free to bring it up in another > occasion if you find it necessary to achieve your goals there ;) The "user" in this case is any

Re: [LEDE-DEV] Drumming up more interest in LEDE

> On Mar 3, 2017, at 3:07 PM, Karol Babioch wrote: > > Hi, > > Am 03.03.2017 um 17:55 schrieb Mauro Mozzarelli: >> I would like to suggest, that when a new potential contributor is >> putting forward his proposed change, an expert buddy is assigned to >> guide the new contributor through to get

Re: [LEDE-DEV] [PATCH 00/12] alternatives support

> On Mar 5, 2017, at 8:06 AM, Matthias Schiffer > wrote: > > This could also avoid adding host UCI support to the build system, making the > whole patchset a lot smaller. Host support for UCI is useful to have anyway, for other reasons… not something to avoid doing (not clear if you were ag

[LEDE-DEV] Supporting crashdumps w/ kexec

Hi. I’m trying to add scripting to support crashdumps. I’m on an x86_64 and haven’t been able to get crashlog to work, so this seems like the next best thing. I’ve a few related questions I was hoping I could get answered. First, obviously, is that kexec needs access to the boot partition to

Re: [LEDE-DEV] Can't build gcc (initial) on Ubuntu 16.04

> On Mar 3, 2017, at 2:51 PM, Hauke Mehrtens wrote: > >>> […] > > GCC 5.3.0 was replaced by GCC 5.4.0 in LEDE some months ago. What are > you using? > > Hauke It was 5.3.0. I had copied over a .config from an OpenWRT cloning but apparently that wasn’t a good idea. Got past that, but havi

Re: [LEDE-DEV] Can't build gcc (initial) on Ubuntu 16.04

I dug into this… Problem was with CONFIG_EXTRA_OPTIMIZATION having “-fno-plt” in it. This was being passed into the ‘gcc’ that was being used to bootstrap gcc. Wondering if that’s not a bug. Shouldn’t the build of the cross-gcc ignore target flags? > On Mar 2, 2017, at 11:58 PM, Phi

Re: [LEDE-DEV] [OpenWrt-Devel] Using kdump... persistent logs, etc.

s disabled by default. You may want to enable it yourself. I > don't know why. > > > Best Regards, > Syrone Wong > > > On Fri, Mar 3, 2017 at 2:31 PM, Philip Prindeville > wrote: >> I built an x86_64 image and turned on crash logging, and then forced a crash

[LEDE-DEV] Can't build gcc (initial) on Ubuntu 16.04

Hi. I was trying to build LEDE (HEAD) today after rebasing all of my fixes to it (from OpenWRT), but I couldn’t even get gcc to build. This was on Ubuntu 16.04-2 LTS. Is there a dependency that might have creeped in? I’m seeing the following: … Checking multilib configuration for libgcc... m

Re: [LEDE-DEV] [OpenWrt-Devel] Using kdump... persistent logs, etc.

at 10:27 AM, Philip Prindeville > wrote: > > Thanks for that. > > >> On Feb 22, 2017, at 11:44 PM, Syrone Wong wrote: >> >> According to LEDE's source code: >> >> config KERNEL_CRASHLOG >> bool "Crash logging" >> depe

Re: [LEDE-DEV] [OpenWrt-Devel] Using kdump... persistent logs, etc.

project/source/blob/master/target/linux/generic/patches-4.9/930-crashlog.patch > > > Best Regards, > Syrone Wong > > > On Thu, Feb 23, 2017 at 10:05 AM, Philip Prindeville > wrote: >> Hi, >> >> Has anyone managed to use kdump with OpenWRT/LEDE? >>

[LEDE-DEV] Using kdump... persistent logs, etc.

Hi, Has anyone managed to use kdump with OpenWRT/LEDE? I have a box which periodically panics, and since /var is a link to /tmp/ there are no persistent logs. Which reminds me: is it safe to configure a third partition on my CF card, format it as ext3, and mount that as /var/log in /etc/fstab

Re: [LEDE-DEV] impressed by progress on odhcpd and procd and elsewhere.

> On Feb 11, 2017, at 11:11 PM, Stijn Tintel wrote: > > On 10-02-17 18:11, Dave Taht wrote: >> About the biggest request from the field seems to be supplying RA and >> dhcpv6 dns on a more real IPv6 address than fe80 to make android users >> happier (https://github.com/dtaht/dnsmasq-lede/issues/

Re: [LEDE-DEV] Makefile question

> On Feb 13, 2017, at 11:25 PM, Yousong Zhou wrote: > > On 14 February 2017 at 10:51, Philip Prindeville > wrote: >> >> Hi Yousong, >> >> I’ve been working on both OpenWRT and LEDE and needed to get some hooks >> working in OpenWRT so I focused on

Re: [LEDE-DEV] Observing procd progress

> On Feb 14, 2017, at 2:45 AM, Petr Štetiar wrote: > > Philip Prindeville [2017-02-12 12:57:19]: > > Hi, > >> One thing I was wondering about was, on a headless system, but that does >> have an LCD display, is maybe capturing the progress of procd as it runs an

Re: [LEDE-DEV] Makefile question

> On Feb 12, 2017, at 10:04 PM, Yousong Zhou wrote: > > On 13 February 2017 at 11:23, Philip Prindeville > wrote: >> >>> On Feb 11, 2017, at 8:29 PM, David Lang wrote: >>> >>> On Sat, 11 Feb 2017, Philip Prindeville wrote: >>> >&g

Re: [LEDE-DEV] Makefile question

> On Feb 12, 2017, at 11:20 PM, Philip Prindeville > wrote: > > >> On Feb 12, 2017, at 11:15 PM, David Lang wrote: >> >> On Sun, 12 Feb 2017, Philip Prindeville wrote: >> >>>>>>>> If you look for where the /files/* are copied i

Re: [LEDE-DEV] Makefile question

> On Feb 12, 2017, at 11:15 PM, David Lang wrote: > > On Sun, 12 Feb 2017, Philip Prindeville wrote: > >>>>>>> If you look for where the /files/* are copied into the filesystem, that >>>>>>> is probably the place you would want to add your

Re: [LEDE-DEV] Makefile question

> On Feb 12, 2017, at 10:04 PM, Yousong Zhou wrote: > > On 13 February 2017 at 11:23, Philip Prindeville > wrote: >> >>> On Feb 11, 2017, at 8:29 PM, David Lang wrote: >>> >>> On Sat, 11 Feb 2017, Philip Prindeville wrote: >>> >&g

Re: [LEDE-DEV] Makefile question

> On Feb 11, 2017, at 8:29 PM, David Lang wrote: > > On Sat, 11 Feb 2017, Philip Prindeville wrote: > >>> This can't eliminate the /etc/rc.d/S* files as it only adds files, and it's >>> not as flexibile as adding a user or changing a password (as it

[LEDE-DEV] Observing procd progress

One thing I was wondering about was, on a headless system, but that does have an LCD display, is maybe capturing the progress of procd as it runs and displaying it on that LCD. Looking at /var/log/messages, I see: 2017-02-12T05:49:52+00:00 Powercode kernel:4.660666] procd: - early - 2017-02

Re: [LEDE-DEV] Makefile question

> On Feb 10, 2017, at 10:33 PM, David Lang wrote: > > On Fri, 10 Feb 2017, Philip Prindeville wrote: > >> Hi. >> >> I was wondering if there’s an obvious place to install a hook that’s: >> >> (a) after all the packages have been installed; &g

[LEDE-DEV] Makefile question

Hi. I was wondering if there’s an obvious place to install a hook that’s: (a) after all the packages have been installed; (b) before the root filesystem image gets finalized; I’d like to be able to run some simple sed scripts inside the root-to-be directory to make some changes, maybe do an rm

[LEDE-DEV] Bounty: simplify extracting/restoring kernel .config

Hi. I’m working on a project where I need to be able to force certain kernel configuration parameters from a script, to automate building tailored kernels for performance testing, certification, etc. I love the way that I can use “scripts/diffconfig.sh” to save the deltas into a file… update t

Re: [LEDE-DEV] Syslog-ng Makefile typo

To make things go a little faster, I’ve put up a PR on github: https://github.com/openwrt/packages/pull/3894 > On Jan 18, 2017, at 12:39 AM, John Crispin wrote: > > Hi, > > although the content of the patch looks good the format is incorrect. > you really want to generate the patch using git

[LEDE-DEV] Race condition in openssh build?

I did a “make dirclean” and then “make -j12” and I end up seeing the following (it’s reproducible): ... make[3] -C feeds/packages/utils/bash compile make[3] -C feeds/packages/utils/bc compile make[3] -C feeds/packages/net/bmon compile make[3] -C package/network/utils/iptables compile make[3]

Re: [LEDE-DEV] [PATCH 4/4] x86: Add APU2 LED Driver

> On Jan 14, 2017, at 9:20 AM, Chris Blake wrote: > > The following patch adds LED support for the PC Engines APU2/APU3 board > on LEDE. > > Signed-off-by: Chris Blake > --- > target/linux/x86/64/config-default | 2 + > target/linux/x86/files/drivers/leds/leds-apu2.c| 374

Re: [LEDE-DEV] Syslog-ng Makefile typo

You can also add: Reviewed-by: Philip Prindeville regarding the unix-stream() vs. unix-dgram(), here’s a bug from Debian (which also uses syslog-ng): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384802 > On Jan 18, 2017, at 12:39 AM, John Crispin wrote: > > Hi, > &g

Re: [LEDE-DEV] Syslog-ng Makefile typo

2017-01-18 08:30:30.416247478 +0100 > @@ -1,4 +1,4 @@ > -@version:3.8 > +@version:3.9 > > options { >chain_hostnames(no); > > Dne 17.1.2017 v 19:40 Philip Prindeville napsal(a): >> Actually, I take that back. >> >> Milan, can you please

Re: [LEDE-DEV] Syslog-ng Makefile typo

… like when the log_prefix() filter criteria got replaced by program()). Thanks > On Jan 16, 2017, at 1:45 PM, Philip Prindeville > wrote: > > Looks good to me. > > >> On Jan 16, 2017, at 4:24 AM, Milan Kočvara wrote: >> >> Hello. >> I found typo in s

Re: [LEDE-DEV] Syslog-ng Makefile typo

Looks good to me. > On Jan 16, 2017, at 4:24 AM, Milan Kočvara wrote: > > Hello. > I found typo in syslog-ng makefile. > > I've upgraded to the newest version and I've made correction of the typo. > Patch bellow. > > Sorry for bad format of everything. I did it never :) > > --- Makefile-ori

[LEDE-DEV] PHP at build time

Hi. I’m working on a project (some GUI interfaces and a back end for generating traffic shaping using netfilter/tc) written in PHP7. It uses PHP’s “composer”. I could install composer (it’s only ever run once on a released project) on the target machine, and run it on first boot. But that see

[LEDE-DEV] [PATCH oldpackage/eventlog oldpackage/syslog-ng3] version bump to latest

update-syslog-eventlog.patch Description: Binary data ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] Bug in ipkg?

> On Jan 2, 2017, at 10:08 PM, Philip Prindeville > wrote: > > Okay, resolved…. I needed to change the Package/perl-cgi/install macro in > the Makefile to invoke perlmod/Install/NoStrip instead of perlmod/Install. > Sigh. > > Would it be reasonable to add a global

Re: [LEDE-DEV] Bug in ipkg?

> On Jan 2, 2017, at 9:59 PM, Philip Prindeville > wrote: > > >> On Jan 2, 2017, at 9:32 PM, Philip Prindeville >> wrote: >> >> I just saw something bizarre. >> >> I had a Perl module (CGI v4.35) which contained the following: >> >

Re: [LEDE-DEV] Bug in ipkg?

> On Jan 2, 2017, at 9:32 PM, Philip Prindeville > wrote: > > I just saw something bizarre. > > I had a Perl module (CGI v4.35) which contained the following: > > my $appease_cpants_kwalitee = q/ > use strict; > use warnings; > #/; > > which is just a

[LEDE-DEV] Bug in ipkg?

I just saw something bizarre. I had a Perl module (CGI v4.35) which contained the following: my $appease_cpants_kwalitee = q/ use strict; use warnings; #/; which is just a quoted string containing the lines that some sanity checking code expects to see (albeit as actual code, and not embedded a

Re: [LEDE-DEV] Adding new targets/subtargets

> On Jan 2, 2017, at 1:38 PM, Alberto Bursi wrote: > > > > On 01/02/2017 07:36 PM, Philip Prindeville wrote: >> >> >> Right, this is why I’m trying to create a new target (or subtarget) called >> “xeon” which is optimized for Xeon targets and levera

Re: [LEDE-DEV] Adding new targets/subtargets

> On Jan 2, 2017, at 1:05 PM, Stefan Lippers-Hollmann wrote: > > Hi > > On 2017-01-02, Philip Prindeville wrote: >>> On Jan 2, 2017, at 10:01 AM, Jo-Philipp Wich wrote: >>> >>> Hi, >>> >>>> The x86/64/config-defaul

Re: [LEDE-DEV] Adding new targets/subtargets

> On Jan 2, 2017, at 3:06 PM, Felix Fietkau wrote: > > On 2017-01-02 19:36, Philip Prindeville wrote: >> Right, this is why I’m trying to create a new target (or subtarget) >> called “xeon” which is optimized for Xeon targets and leverages the >> on-chip crypto-accele

Re: [LEDE-DEV] Adding new targets/subtargets

> On Dec 31, 2016, at 6:23 PM, Philip Prindeville > wrote: > > There’s a test for “ifeq ($(ARCH),i386) … endif” but I don’t see code for > x86_64. Do we need something like: > > diff --git a/include/target.mk b/include/target.mk > index 8211ba0..5e3aae6 100644 &

Re: [LEDE-DEV] Adding new targets/subtargets

> On Jan 2, 2017, at 10:01 AM, Jo-Philipp Wich wrote: > > Hi, > >> The x86/64/config-default is missing the following switches: >> >> CONFIG_MCORE2=y > > That would break support for older x86_64 iirc. > >> CONFIG_MDIO=y >> CONFIG_X86_USE_PPRO_CHECKSUM=y > > Those can probably go into x86/6

Re: [LEDE-DEV] Adding new targets/subtargets

> On Jan 2, 2017, at 10:08 AM, Jo-Philipp Wich wrote: > >> Why not instead just add a profile attribute like: >> >> BUILDBOT_BUILD_ME:=no > > Because we want to have complete coverage. Experience has shown that > untested subtargets quickly become stale and broken. > > ~ Jo Then we need mor

Re: [LEDE-DEV] Adding new targets/subtargets

> On Jan 1, 2017, at 8:34 AM, Weedy wrote: > > On 31 December 2016 at 20:23, Philip Prindeville > wrote: >> >> >> Pruning useful subtargets to solve a buildbot resource shortage seems like >> taking a sledgehammer to kill a fly. >> >> W

Re: [LEDE-DEV] Adding new targets/subtargets

> On Dec 31, 2016, at 9:32 AM, Yousong Zhou wrote: > > On 31 December 2016 at 06:13, Philip Prindeville > wrote: >> >>> On Dec 29, 2016, at 7:46 PM, Yousong Zhou wrote: >>> >>> On 30 December 2016 at 03:29, Philip Prindeville >>> wrote:

[LEDE-DEV] Scripting builds... how to?

Hi. I wanted to be able to script building images completely. I understand how to do: cp ../my-saved-config .config make defconfig make oldconfig to generate the .config file in a completely scripted way, by seeding it with the minimum set of relevant parameters (the deltas) per the steps des

[LEDE-DEV] Blackhole routes and other tidbits on the network configuration wiki page

I was going over the “Network configuration” page on the wiki and it’s a little thin on routes. In particular, it implies that for a route you always need interface/target/netmask/gateway… but in the case of type=blackhole, a gateway doesn’t really seem applicable. So would you have: config r

Re: [LEDE-DEV] Adding new targets/subtargets

> On Dec 29, 2016, at 7:46 PM, Yousong Zhou wrote: > > On 30 December 2016 at 03:29, Philip Prindeville > wrote: >> On Dec 28, 2016, at 7:57 PM, Yousong Zhou wrote: >> >> The x86/64/config-default is missing the following switches: >>

Re: [LEDE-DEV] Adding new targets/subtargets

On Dec 28, 2016, at 7:57 PM, Yousong Zhou wrote: > > On 29 December 2016 at 10:04, Philip Prindeville > wrote: >> I wanted to add a new target for x86, or possibly several. >> >> I have an immediate need for an optimized build to run on Xeon-based 1U >> serve

[LEDE-DEV] Adding new targets/subtargets

I wanted to add a new target for x86, or possibly several. I have an immediate need for an optimized build to run on Xeon-based 1U servers for a project that I’m working on. My work in progress is here: https://github.com/pprindeville/openwrt/commit/67a11380ed69351e320a410ec18c04e62fb548d3 but

Re: [LEDE-DEV] [OpenWrt-Devel] Any interest in adding runit to OpenWRT?

> On Dec 25, 2016, at 1:01 PM, Denys Vlasenko wrote: > > In my humble opinion, for distros which can't use systemd because > of the size, or won't use systemd because they don't like it, > a good contender is daemontools or one of its clones. > It is especially suited for a distros which target

Re: [LEDE-DEV] [OpenWrt-Devel] Talks between OpenWrt and LEDE

On Dec 21, 2016, at 10:13 PM, Russell Senior wrote: >> "Florian" == Florian Fainelli writes: > >>> However, I also agree with Dave, Alberto and Stefan that a name >>> change may be a really smart way to communicate the fresh start of >>> the project, a reboot, especially if the new name ri

<    1   2