Me too.
> On May 5, 2018, at 7:36 AM, Paul Spooren wrote:
>
> Are there any updates on this issue? I'd really like to see squasfs 5.0 used
> in OpenWrt!
>
> On Sat, May 27, 2017 at 8:51 PM, Hauke Mehrtens wrote:
>> On 05/26/2017 06:13 PM, Alexander Couzens wrote:
>>> squashfs is quite long u
Inline
> On Apr 4, 2018, at 5:28 PM, Luiz Angelo Daros de Luca
> wrote:
>
> When '-k' is used, sysupgrade inserts into backup a new file
> /etc/sysupgrade.installed which contains pkgname and
> origin (rom, overlay, unknown).
>
> It's maily used to reinstall all extra packages:
>
> # opkg upd
Inline
> On Apr 4, 2018, at 5:28 PM, Luiz Angelo Daros de Luca
> wrote:
>
> When '-k' is used, sysupgrade inserts into backup a new file
> /etc/sysupgrade.installed which contains pkgname and
> origin (rom, overlay, unknown).
>
> It's maily used to reinstall all extra packages:
>
> # opkg upd
Is there a downside to forcing AMD to also do early firmware updates?
> On Apr 17, 2018, at 12:50 PM, Tomasz Maciej Nowak wrote:
>
> Create initrd enries for x86 images, that'll load intel microcode as
> early as possible. Also restrict the late load of microcode to AMD
> processors.
>
> Sign
Inline
> On Apr 9, 2018, at 2:11 PM, Tomasz Maciej Nowak wrote:
>
> W dniu 09.04.2018 o 21:05, Philip Prindeville pisze:
>> Inline
>>> On Apr 3, 2018, at 7:13 AM, Tomasz Maciej Nowak wrote:
>>>
>>> Create initrd image with packed microcode. This
> On Feb 16, 2018, at 1:32 PM, Philip Prindeville
> wrote:
>
>
>
>> On Feb 16, 2018, at 5:46 AM, John Crispin wrote:
>>
>> Hi,
>>
>> whats on the critical todo list for the upcoming release ? i still have a
>> few minor things that I
“guest” or “salon”?
> On Apr 3, 2018, at 8:51 AM, Alin Nastac wrote:
>
> From: Alin Nastac
>
> Reproduction scenario:
> - use 3 interfaces with 3 different zones - lan, wan and guest
> - configure firewall to allow forwarding from lan to wan
> - add DROP rule to prevent forwarding from lan t
Inline
> On Apr 3, 2018, at 7:13 AM, Tomasz Maciej Nowak wrote:
>
> Create initrd image with packed microcode. This'll allow to load it at
> early boot stage. Unfortunately the package can't install files directly
> to /boot directory, therefore additional installation hooks are placed
> for sta
Inline. Has this been tested with UEFI?
> On Apr 3, 2018, at 7:13 AM, Tomasz Maciej Nowak wrote:
>
> Create initrd enries for x86 images, that'll load intel microcode as
> early as possible. Also restrict the late load of microcode to AMD
> processors.
>
> Signed-off-by: Tomasz Maciej Nowak
Hi all,
What do people think of (a) rewriting ipcalc.sh to be in C instead, and (b)
allowing it to perform multiple operations either with flags or perhaps with
symlinks and examining argv[0] a la busybox?
It isn’t used in too many places so any sort of change won’t have too many
repercussions
> On Mar 31, 2018, at 12:57 PM, Eric Luehrsen wrote:
>
> It seems I have static-stub wrong for its purpose. dhcpd and bind do work
> together. To accomplish this, the bind instance needs to be master for the
> domain zone and ptr zone where DHCP records will be entered. This master zone
> ne
> On Mar 31, 2018, at 9:03 AM, Eric Luehrsen wrote:
>
> On 03/25/2018 03:27 AM, Philip Prindeville wrote:
>> Thinking Bind, probably.
>>
>>
>>
>>> On Mar 23, 2018, at 5:38 PM, Eric Luehrsen wrote:
>>>
>>> What do you w
“recent”? I thought APU2’s had been discontinued a while ago.
> On Mar 26, 2018, at 8:20 AM, Sebastian Fleer wrote:
>
> In recent firmware releases the board names changed from "apuX" to "PC
> Engines apuX"
>
> Signed-off-by: Sebastian Fleer
> ---
> package/kernel/leds-apu2/src/leds-apu2.c
Anyone else seeing this issue with Bind?
Collected errors:
* check_data_file_clashes: Package bind-check wants to install file
/home/philipp/lede/build_dir/target-x86_64_musl/root-x86/usr/sbin/named-checkconf
But that file is already provided by package * bind-tools
* check_data_file_c
> On Mar 25, 2018, at 2:38 PM, Noah Meyerhans wrote:
>
> On Sun, Mar 25, 2018 at 02:24:57PM -0600, Philip Prindeville wrote:
>> Collected errors:
>> * check_data_file_clashes: Package bind-check wants to install file
>> /home/philipp/lede/build_dir/target-x86_64_m
Thinking Bind, probably.
> On Mar 23, 2018, at 5:38 PM, Eric Luehrsen wrote:
>
> What do you want to serve your dns then? Unbound or Bind?
>
> - Eric
>
> On Fri, Mar 23, 2018, 1:31 PM Philip Prindeville
> wrote:
> Hi all,
>
> As the ISC-DHCP maintainer,
Hi all,
As the ISC-DHCP maintainer, I need to eat my own dogfood so I run that here,
before anyone quips, “Why don’t you just run dnsmasq instead?”
So… I have some internal names that I want to be able to resolve internally,
but I also need to provide DNS service for all of my DHCP clients.
Is
> On Mar 4, 2018, at 6:26 PM, Alif M. Ahmad wrote:
>
> On Fri, Feb 16, 2018 at 01:46:31PM +0100, John Crispin wrote:
>> Hi,
>>
>> whats on the critical todo list for the upcoming release ? i still have
>> a few minor things that I'll be adding shortly, apart from that I am
>> currently not a
> On Feb 18, 2018, at 11:25 AM, Philip Prindeville
> wrote:
>
>
>
>> On Feb 18, 2018, at 2:27 AM, John Crispin wrote:
>>
>>
>>
>>> On 20/06/17 19:13, Stefan Tomanek wrote:
>>> While sshd should be favoured over telnetd, having a te
Why did we even do this to begin with?
> On Feb 15, 2018, at 3:52 PM, Hauke Mehrtens wrote:
>
> Remove this old patch which prevents showing the xfrm ports for SCTP
>
> This was added in commit 60c1f0f64d23 ("finally move buildroot-ng to trunk")
> ---
> .../network/utils/iproute2/patches/006-n
> On Feb 18, 2018, at 2:27 AM, John Crispin wrote:
>
>
>
>> On 20/06/17 19:13, Stefan Tomanek wrote:
>> While sshd should be favoured over telnetd, having a telnet client on the
>> router is useful for connecting to other devices in the same LAN.
>>
>> Signed-off-by: Stefan Tomanek
>
> sor
> On Feb 16, 2018, at 5:46 AM, John Crispin wrote:
>
> Hi,
>
> whats on the critical todo list for the upcoming release ? i still have a few
> minor things that I'll be adding shortly, apart from that I am currently not
> aware of any huge problems. the release will be a mix between 4.9 and
> On Feb 14, 2018, at 3:00 PM, Magnus Kroken wrote:
>
> On 14.02.2018 22.13, Michelle Sullivan wrote:
>> FWIW, I had misunderstood the intent of the original comments... OpenSSH
>> server vs Dropbear - if someone is using OpenSSH server they already
>> went in with advanced config as Dropbear is
> On Feb 14, 2018, at 3:00 PM, Magnus Kroken wrote:
>
> On 14.02.2018 22.13, Michelle Sullivan wrote:
>> FWIW, I had misunderstood the intent of the original comments... OpenSSH
>> server vs Dropbear - if someone is using OpenSSH server they already
>> went in with advanced config as Dropbear i
> On Feb 14, 2018, at 1:25 AM, Stijn Segers wrote:
>
> Yousong Zhou schreef op 14 februari 2018 09:06:11 CET:
>>
>> No, it's just complicating things up. When people really cares about
>> the default settings' security, the will override the default by also
>> specifying files/etc/ssh/sshd_c
> On Feb 14, 2018, at 1:06 AM, Yousong Zhou wrote:
>
> On 14 February 2018 at 11:53, Philip Prindeville
> wrote:
>>
>>> On Feb 11, 2018, at 3:54 AM, Yousong Zhou wrote:
>>>
>>> On 9 February 2018 at 08:28, Philip Prindeville
>>> wro
> On Feb 13, 2018, at 9:14 PM, Michelle Sullivan wrote:
>
> [snip]
> Personally - my thoughts
>
> There should be an option to enable passwords (default off...)
> A warning should be placed on the checkbox to inform the user it is not a
> good idea to enable them.
> SSH should be disable
> On Feb 11, 2018, at 3:54 AM, Yousong Zhou wrote:
>
> On 9 February 2018 at 08:28, Philip Prindeville
> wrote:
>> From: Philip Prindeville
>>
>> Allowing password logins leaves you vulnerable to dictionary
>> attacks. We disable password-based authentic
> On Feb 11, 2018, at 3:54 AM, Yousong Zhou wrote:
>
> On 9 February 2018 at 08:28, Philip Prindeville
> wrote:
>> From: Philip Prindeville
>>
>> Allowing password logins leaves you vulnerable to dictionary
>> attacks. We disable password-based authentic
> On Feb 11, 2018, at 3:54 AM, Yousong Zhou wrote:
>
> On 9 February 2018 at 08:28, Philip Prindeville
> wrote:
>> From: Philip Prindeville
>>
>> Allowing password logins leaves you vulnerable to dictionary
>> attacks. We disable password-based authentic
> On Feb 11, 2018, at 4:23 AM, Alberto Bursi wrote:
>
>
>
> On 02/11/2018 11:54 AM, Yousong Zhou wrote:
>> On 9 February 2018 at 08:28, Philip Prindeville
>> wrote:
>>> From: Philip Prindeville
>>>
>>> Allowing password logins leaves
Sent from my iPhone
> On Feb 11, 2018, at 4:11 AM, Torbjorn Jansson
> wrote:
>
>> On 2018-02-11 11:54, Yousong Zhou wrote:
>> On 9 February 2018 at 08:28, Philip Prindeville
>> wrote:
>>> From: Philip Prindeville
>>>
>>> Allowi
> On Feb 10, 2018, at 6:03 PM, Michelle Sullivan wrote:
>
> Paul Oranje wrote:
>> Your aptness for seeing the possible attack vectors warrants your judgement
>> ...
>>
>>> Op 10 feb. 2018, om 17:07 heeft Philip Prindeville
>>> het volgende ges
r (ie run a password attack).
Not substantially more secure...
-Philip
>
>> Op 9 feb. 2018, om 01:28 heeft Philip Prindeville
>> het volgende geschreven:
>>
>> From: Philip Prindeville
>>
>> Allowing password logins leaves you vulnerable to dictiona
> On Jan 18, 2018, at 2:15 PM, Hauke Mehrtens wrote:
>
> On 01/18/2018 01:51 PM, Nick Lowe wrote:
>> Does an update to the Kernel, 4.9.77 and 4.14.14 need to be made to
>> properly address this? There are fixes to mitigate Spectre.
>
> We even need a patch for GCC which will be in GCC 8 and 7.
LGTM
Been using it here for a few days.
> On Feb 1, 2018, at 5:57 PM, Daniel Golle wrote:
>
> When sourcing /sys/class/block/*/uevent values have to be quoted as
> they may contain spaces (e.g. in PARTNAME).
> Fix this by pre-processing with sed before sourcing.
>
> Signed-off-by: Daniel Goll
From: Philip Prindeville
Allowing password logins leaves you vulnerable to dictionary
attacks. We disable password-based authentication, limiting
authentication to keys only which are more secure.
Note: You'll need to pre-populate your image with some initial
keys. To do this:
1. Creat
Hi all,
I’m trying to proceed with:
https://github.com/lede-project/source/pull/1485
which extends the xtables-addons package by adding the subpackage iptgeoip
which retrieves the GeoIP by-country database and processes it into files
suitable for use with xt_geoip (otherwise this netfilter plu
> On Dec 9, 2017, at 1:33 AM, Arjen de Korte wrote:
>
> Citeren Philip Prindeville :
>
>> Jo and others:
>>
>> Is there an easy way to extend firewall rules? I’d like to add support to
>> blocking on a per-country basis, possibly with qualified
Jo and others:
Is there an easy way to extend firewall rules? I’d like to add support to
blocking on a per-country basis, possibly with qualified exceptions.
For instance, if I wanted to block all ISP’s from RU, but allow email from
Kaspersky’s servers in Russia.
I’d like to do something like
afflict clients (especially
roaming WiFi clients) being an LEDE router than LEDE itself.
-Philip
> On Jul 3, 2017, at 2:04 PM, Philip Prindeville
> wrote:
>
> For everyone who has ever wondered why they need to stop and restart long
> running services when they move from one net
> On Nov 5, 2017, at 7:55 PM, Yousong Zhou wrote:
>
> On 6 November 2017 at 06:28, Philip Prindeville
> wrote:
>> I’m seeing the following when trying to build a Geode image:
>>
>> [snip]
>
> Hi, I have just pushed a change to disable ssp with libunw
> On Nov 5, 2017, at 3:28 PM, Philip Prindeville
> wrote:
>
> I’m seeing the following when trying to build a Geode image:
>
>
> make[6]: Entering directory
> '/home/philipp/bertram/lede3/build_dir/target-i386_pentium_musl/libunwind-1.2.1/src'
> /bin/ba
I’m seeing the following when trying to build a Geode image:
make[6]: Entering directory
'/home/philipp/bertram/lede3/build_dir/target-i386_pentium_musl/libunwind-1.2.1/src'
/bin/bash ../libtool --tag=CC --mode=link i486-openwrt-linux-musl-gcc -Os
-pipe -march=pentium-mmx -fno-caller-saves
> On Nov 4, 2017, at 3:14 AM, Petr Štetiar wrote:
>
> Hans Dedecker [2017-11-03 13:46:14]:
>
> Hi,
>
>> By default dropbear logs to syslog which discloses info about account names
>> when doing connection attempts (e.g. "Bad password attempt for 'engineer'
>> from x.x.x.x:y")
>
> I don't get
NAK, inline:
> On Nov 3, 2017, at 6:46 AM, Hans Dedecker wrote:
>
> By default dropbear logs to syslog which discloses info about account names
> when doing connection attempts (e.g. "Bad password attempt for 'engineer' from
> x.x.x.x:y")
> As this facilitates brute force attempts against accou
> On Nov 2, 2017, at 3:54 PM, Felix Fietkau wrote:
>
> On 2017-11-02 22:50, Philip Prindeville wrote:
>>
>> Okay, great.
>>
>> When will this show up in LEDE?
> Pushed just now.
>
> - Felix
Tested and confirmed!
> On Nov 2, 2017, at 3:03 PM, Felix Fietkau wrote:
>
> On 2017-11-02 19:23, Philip Prindeville wrote:
>> From: Philip Prindeville
>>
>> When uclient-fetch is called with multiple URL's, it derives the
>> first filename based on the URL. When it then hand
From: Philip Prindeville
When uclient-fetch is called with multiple URL's, it derives the
first filename based on the URL. When it then handles the 2nd and
subsequent URLs, it assumes that it was called with a -O filename
argument as the output file, because it tries to overload the
var
> On Nov 2, 2017, at 4:24 AM, edgar.sol...@web.de wrote:
>
> hey Phillip,
>
> On 02.11.2017 03:36, Philip Prindeville wrote:
>> Can someone else please try to reproduce this?
>
> yes, not exactly but wrong resulting file name nonetheless. it's obviously a
&g
> On Nov 1, 2017, at 8:36 PM, Philip Prindeville
> wrote:
>
> Can someone else please try to reproduce this?
>
> I’m using busybox’s wget on x86_64 hardware, and when I do a “wget” of 2
> http: URI’s, it mangles the second URI’s derived filename:
>
>
>
Can someone else please try to reproduce this?
I’m using busybox’s wget on x86_64 hardware, and when I do a “wget” of 2 http:
URI’s, it mangles the second URI’s derived filename:
root@lede:/tmp/x# wget
http://geolite.maxmind.com/download/geoip/database/GeoIPv6.csv.gz
http://geolite.maxmind.co
> On Oct 3, 2017, at 3:27 AM, Stijn Tintel wrote:
>
> On 03-10-17 03:31, David Lang wrote:
>> note that the kernel currently under development (4.14) is tagged to
>> be a LTS kernel (6 years of support), so it would be good to work on
>> that if possible.
> I would prefer to have a release based
Inline…
> On Oct 31, 2017, at 3:56 AM, Baptiste Jonglez
> wrote:
>
> From: Baptiste Jonglez
>
> This patch is marked [RFC] because this is such a huge change, and some
> dependent packages now fail to build because of API changes. Also, there
> is no parallel build for now, but this was alre
> On Oct 22, 2017, at 11:57 PM, Felix Fietkau wrote:
>
> On 2017-10-23 05:50, Yousong Zhou wrote:
>> On 23 October 2017 at 04:21, Zoltan HERPAI wrote:
>>> From: Philip Prindeville
>>>
>>> Signed-off-by: Philip Prindeville
>>>
Hi all,
Does it seem to anyone else that we’re making this more complicated than it
needs to be?
If one of the goals we’re going for from here on out is “equality”, then a
basic litmus test to be applied to any action might be “does this get us closer
to a level playing field, or further away”
> On Oct 25, 2017, at 8:32 PM, Yousong Zhou wrote:
>
> On 26 October 2017 at 08:08, Philip Prindeville
> wrote:
>> Hi.
>>
>> I was recently working on updating Perl 5.26.1 which required making
>> machine-specific parameters for cross-builds (because Per
Heads up that Perl has been updated to 5.26.1. Please notify me of any ensuing
related issues.
Thanks
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Hi.
I was recently working on updating Perl 5.26.1 which required making
machine-specific parameters for cross-builds (because Perl doesn’t use
autoconf), and was able to test for x86_64 on KVM/libvirt, but have not tried
any other platforms (well, I built armvirt but haven’t run anything in a
> On Oct 17, 2017, at 4:36 PM, Philip Prindeville
> wrote:
>
> [snip]
>
> Since there ARE known and remedied CVE’s, I’d like to move quickly on this.
>
I should have qualified that. I’m going to commit 48 hours after sending out
that last email unless any
Hi.
We’re currently at Perl 5.24.1 but there are some known CVE’s in that version.
5.26.1 was recently released with fixes.
New architecture specific parameters were added with 5.26.1 to the
configuration, as well as a couple of new functions which (as best I can tell),
both MUSL and glibc ei
> On Oct 10, 2017, at 3:44 PM, Val Kulkov wrote:
>
> What is the most appropriate forum for discussing issues related to
> the community management of openwrt/packages?
>
> Unless I am missing something, there is no forum, no wiki nor any
> other place for discussing openwrt/packages other than
Hi all,
I’m available for LEDE/OpenWrt contracting work (platform bring-up, adding new
packages, porting applications to the LEDE environment, customization, etc) if
there’s such a need.
I’m on LinkedIn: https://www.linkedin.com/in/philipprindeville/ and GitHub as
pprindeville, of course.
Ple
> On Sep 29, 2017, at 7:18 PM, Florian Fainelli wrote:
>
>
>
> On 09/29/2017 06:01 PM, Philip Prindeville wrote:
>>
>> [snip]
>> Tested on x86_64. Seems to work.
>
> To avoid patching mored packages in the future, would it make sense to
>
> On Sep 29, 2017, at 3:49 AM, Matthias May wrote:
>
> The link from Philip Prindeville shows quite well why this removal was
> required:
> [quote]
> check-response-ttl= Takes a boolean value ("yes" or "no"). If set to "yes",
> an additional
> On Sep 29, 2017, at 4:39 AM, Felix Fietkau wrote:
>
> On 2017-09-29 12:20, Felix Fietkau wrote:
>> On 2017-09-11 02:33, Philip Prindeville wrote:
>>> Changing the subject from the previous thread as it turned out to not have
>>> to do with sysupgrade at all.
Inline…
> On Sep 28, 2017, at 2:32 AM, Martin Schiller wrote:
>
> If you rename a network interface, there is a move uevent
> invoked instead of remove/add.
>
> This patch adds support for this kind of event.
>
> Signed-off-by: Martin Schiller
> ---
> system-linux.c | 31
> On Sep 28, 2017, at 4:04 PM, Russell Senior wrote:
>
>>>>>> "Philip" == Philip Prindeville
>>>>>> writes:
>
> Philip> Hi. I’m trying to update Perl from 5.24.1 to 5.26.1 but running
> Philip> into some issues.
>
>
Hi.
I’m trying to update Perl from 5.24.1 to 5.26.1 but running into some issues.
We don’t use ./Configure to build the target versions (just the host version),
so when new settings are added, we need to figure out what they are… and what
the appropriate settings are for all processors.
And wo
> On Sep 28, 2017, at 2:32 PM, Christian Lamparter
> wrote:
>
>> On Thursday, September 28, 2017 1:36:52 PM CEST Philip Prindeville wrote:
>> Why was this test there and equally why are we removing it?
> I guess it was there so umdns would ignore any forwarded mdns?
&g
Why was this test there and equally why are we removing it?
> On Sep 28, 2017, at 1:09 AM, Philipp Meier wrote:
>
> Signed-off-by: Philipp Meier
> ---
> interface.c | 6 --
> 1 file changed, 6 deletions(-)
>
> diff --git a/interface.c b/interface.c
> index 3904c89..7f814d2 100644
> --- a/in
Inline
Sent from my iPhone
> On Sep 28, 2017, at 1:09 AM, Philipp Meier wrote:
>
> Signed-off-by: Philipp Meier
> ---
> service.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/service.c b/service.c
> index 0a9e25d..97b6f91 100644
> --- a/service.c
> +++ b/service.c
That’s what the -p flag to sysupgrade is for.
Also, there’s not much point in resizing the rootdisk partition: even applying
several upgrades and maybe adding some new packages, the amount of used space
isn’t going to grow significantly.
You’re better off creating a 3rd EXT4 partition as /var o
> On Sep 11, 2017, at 1:33 PM, Philip Prindeville
> wrote:
>
> I was wondering why the loggers (except ubox) are all started as priority 20
> (same as “network”):
>
> $ grep START= package/system/ubox/files/log.init
> feeds/packages/net/ulogd/files/ulogd.init
>
I was wondering why the loggers (except ubox) are all started as priority 20
(same as “network”):
$ grep START= package/system/ubox/files/log.init
feeds/packages/net/ulogd/files/ulogd.init
feeds/packages/net/rsyslog/files/rsyslog.init
feeds/packages/admin/syslog-ng/files/syslog-ng.init
packag
Changing the subject from the previous thread as it turned out to not have to
do with sysupgrade at all.
What I can tell is this, having added some tracing to fstools.
We get to the call to system() in rootdisk_volume_init():
https://git.lede-project.org/?p=project/fstools.git;a=blob;f=libfstoo
alled an image.
No more issues with sysupgrade or rebooting.
> On Sep 5, 2017, at 10:19 PM, Ryan Mounce wrote:
>
> The culprit is
> e505f59 utils/util-linux: Update to 2.30.1
>
> On 6 September 2017 at 12:24, Philip Prindeville
> wrote:
>>
>> Thanks.
>>
> On Sep 5, 2017, at 8:50 PM, Ryan Mounce wrote:
>
> On 31 August 2017 at 04:11, Philip Prindeville
> wrote:
>> Looking a little further into the console logging, what I’m seeing after a
>> “dd” directly onto the flash is this:
>>
>> Press the [f] key an
Looking a little further into the console logging, what I’m seeing after a “dd”
directly onto the flash is this:
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[6.299598] mount_root: loading kmods from inte
> On Aug 29, 2017, at 9:16 AM, Philip Prindeville
> wrote:
>
>> On Aug 29, 2017, at 1:19 AM, Stijn Tintel wrote:
>>
>>> On 29-08-17 09:09, Philip Prindeville wrote:
>>> Hi all,
>>>
>>> I don’t know if sysupgrade is the problem,
Hi.
I was wondering about why the network interfaces stay up during a sysupgrade.
No services are available, so about all you can do is ping the box or have your
connections reset if you try to connect to it.
Would it make more sense to bring all network interfaces down?
Worst case scenario is
> On Aug 29, 2017, at 1:19 AM, Stijn Tintel wrote:
>
>> On 29-08-17 09:09, Philip Prindeville wrote:
>> Hi all,
>>
>> I don’t know if sysupgrade is the problem, or if this is where things
>> manifest.
>>
>> But I recently (within the last
Hi all,
I don’t know if sysupgrade is the problem, or if this is where things manifest.
But I recently (within the last week, but I only rebase once or twice a week)
started seeing issues with doing sysupgrade on x86_64 hardware.
The sysupgrade will appear to go okay, but then when the machine
> On Aug 28, 2017, at 6:17 PM, Zoltan Gyarmati
> wrote:
>
> On 08/28/2017 01:52 PM, Zoltan Gyarmati wrote:
>> Dear All,
>>
>> i'm fighting with an odd build error on my build server VPS, using
>> current master and the RT5350F-OLINUXINO profile:
>>
>> When trying to re-build the LEDE tree (af
> On Aug 28, 2017, at 6:15 AM, rpj...@crashcourse.ca wrote:
>
> do the LEDE admins look for that stuff like that
> and upstream it automatically?
No, as it’s your patch, you need to be the one presenting it so you can answer
questions about it, make changes if asked to do so, etc.
_
> On Aug 22, 2017, at 1:56 PM, Arjen de Korte wrote:
>
> Citeren Philip Prindeville :
>
>> Found the issue, and posted PR #1308 to fix it. One-line fix.
>>
>>
>>> On Aug 19, 2017, at 3:06 PM, Philip Prindeville
>>> wrote:
>>>
>&
Found the issue, and posted PR #1308 to fix it. One-line fix.
> On Aug 19, 2017, at 3:06 PM, Philip Prindeville
> wrote:
>
> And it looks like Hannu is way ahead of me:
>
> https://bugs.lede-project.org/index.php?do=details&task_id=969
>
>
>> O
> On Aug 22, 2017, at 4:01 AM, Kevin Darbyshire-Bryant
> wrote:
>
> Drop 300-mips_Os_cpu_rtx_cost_model.patch for gcc 7.2
>
> This was causing mis-compilation of dropbear with the default '-Os' size
> optimization as reported in FS#814
>
> Tested on ar71xx, archer C7 v2. For size comparison
And it looks like Hannu is way ahead of me:
https://bugs.lede-project.org/index.php?do=details&task_id=969
> On Aug 19, 2017, at 2:59 PM, Philip Prindeville
> wrote:
>
> I rebased about an hour ago and then tried to rebuild everything. Now I’m
> seeing what’s below.
&
I rebased about an hour ago and then tried to rebuild everything. Now I’m
seeing what’s below.
I looked at the commit logs, though, and nothing stands out as a likely
culprit… except maybe the bump from 4.9.40 to 4.9.44.
If I rebase back to
d9564d7 bcm53xx: backport DTS commits that setup USB
Github is trying to CI test a change to PHP7 and it’s never completing, even
after 50 minutes of build time:
https://travis-ci.org/openwrt/packages/builds/266325516?utm_source=github_status&utm_medium=notification
Is this a known issue from the recent round of changes?
It seems that a LOT of pa
> On Aug 16, 2017, at 7:04 PM, Florian Fainelli wrote:
>
> On 08/16/2017 12:03 PM, Philip Prindeville wrote:
>> Hi.
>>
>> This was a bit of an issue with OpenWrt and I’m not sure if it’s starting to
>> be a problem with LEDE or if August is just the month when
Hi.
This was a bit of an issue with OpenWrt and I’m not sure if it’s starting to be
a problem with LEDE or if August is just the month when all of Europe shuts
down and nothing gets done…
I’m hoping it’s the latter.
Can we formalize what the procedures are for someone submitting a PR, how long
Hi,
There are times when the default module parameters are suboptimal for
OpenWrt/LEDE, for instance NICs may have defaults which are optimized for
end-systems (hosts) and not transit-systems (routers).
This bug is outline in FS#935:
https://bugs.lede-project.org/index.php?do=details&task_id=9
> On Aug 7, 2017, at 3:48 PM, Rafał Miłecki wrote:
>
> On 7 August 2017 at 21:20, Philip Prindeville
> wrote:
>>> On Jul 31, 2017, at 10:11 AM, John Crispin wrote:
>>>
>>> Hi,
>>>
>>> I rebased my ages old kernel patch cleanup series
> On Aug 7, 2017, at 6:37 PM, Matthias Schiffer
> wrote:
>
> On 08/07/2017 06:14 PM, Philip Prindeville wrote:
>> I’m seeing the following when building bind:
>>
>> OpenWrt-libtool: link: x86_64-openwrt-linux-musl-gcc -Os -pipe
>> -fno-caller-saves -fno-
> On Jul 31, 2017, at 10:11 AM, John Crispin wrote:
>
> Hi,
>
> I rebased my ages old kernel patch cleanup series. It can be found here [1].
>
> the series annotates all patches and splits them up into 3 folders
> backports/pending/hacks.
What’s the criteria for each?
And isn’t “hacks” kin
I’m seeing the following when building bind:
OpenWrt-libtool: link: x86_64-openwrt-linux-musl-gcc -Os -pipe
-fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable
-Wno-error=unused-result
-iremap/home/philipp/bertram/lede/build_dir/target-x86_64_musl_powercode-bmu/bind-9.1
I’m working on Issue #4588 (ntpd needs UCI parsing comparable to sysntpd) and I
had a question…
ntpd ships with the canned /etc/ntp.conf from the distro, but if we specify:
config timeserver ntp
list server ‘ntp.redfish-solutions.com’
then the /etc/ntp.conf file needs to be rewritten
Am I the only one who would prefer all of the virtualization support to be
selected and default to off?
All the fuss we have about not burdening images with unnecessary functionality,
yet no one blinks at this...
> On Jul 15, 2017, at 10:48 AM, Baptiste Jonglez
> wrote:
>
> From: Baptiste Jo
1 - 100 of 197 matches
Mail list logo