You can investigate a core dump file using gdb or an IDE to review the
call stack and variables (extra useful if compiled with -g and -O0).
You may need to enable core dumping like so:
http://www.idimmu.net/2013/06/21/enable-linux-core-dump/
http://www.akadia.com/services/ora_enable_core.html
By
Good work, guys! GitHub pull requests with cloud CI integration
(drone.io, travis, etc.), driven by an online distributed review
process and single click merging would really enable scaling of this
project.
On Tue, Nov 10, 2015 at 1:30 AM, koniu wrote:
> wouldn't it been nice to rewrite sign offs
I welcome any input relating
to this topic.
Regards,
bkil
On Tue, Oct 13, 2015 at 5:10 PM, Bastian Bittorf wrote:
> * Daniel Golle [13.10.2015 16:53]:
>> If you want an industry-driven fork, go ahead. But don't force that
>> model upon an existing community without understand
+1 for Designated Driver
When I last checked the Doodle around day 2, Designated Driver was
leading with about 2:1, and I couldn't see much spam at that point. I
guess the mailing list archives are public, so robots and pranksters
could do targeted harvesting of such polling links in short order.
Day Dreaming
Desert Daisy
Diabetic Delight
Dolly Daydream
Drunk Driver
Dusky Decadence
...
On Mon, Apr 6, 2015 at 6:44 PM, Lars wrote:
> On 06.04.2015 18:41, Conor O'Gorman wrote:
>> On 06/04/15 16:50, Imre Kaloz wrote:
>>> On Mon, 06 Apr 2015 12:54:53 +0200, bkil
>>
+1 on Designated Driver. Migrating or upgrading to OpenWrt is the
sober choice. I didn't find the other two meaningful or relevant.
I think community polls should be organized in two phases. The first
one should gather ideas, while the second one should gather votes.
On Mon, Apr 6, 2015 at 12:41
Unfortunately, your patch will never be merged because most developers
are from the USA:
https://dev.openwrt.org/ticket/6923
https://dev.openwrt.org/ticket/
https://dev.openwrt.org/ticket/9678
https://dev.openwrt.org/ticket/12991
https://dev.openwrt.org/ticket/16818
https://dev.openwrt.org/tick
If anyone wants to organize a BattleMesh event in Hungary, I would
vote for that and have a near industrial amount of various compatible
hardware standing by!
On Wed, Mar 25, 2015 at 9:36 PM, Gergely Kiss wrote:
> On 03/21/2015 08:51 PM, valent.turko...@gmail.com wrote:
>> On 10 March 2015 at 21:
I don't think a device knows its own serial number, though that could
depend on your exact make and model. Can you see it displayed on the
OEM web interface?
The TP-Link devices I have just checked only store the model number,
revision, MAC address and QSS PIN at the end of /dev/mtd0 (U-boot). I
h
Actually, I wanted to ask why we were forced to default settings in
the last couple of years. Some forum thread indicated that it was an
FCC imposed restriction regarding distribution in the USA.
The OEM firmware had always allowed country and channel selection from
the dropdown menu, and the EEPR
t
should work the same way and (the most important parts of) the PLCP
header and preamble runs at basic rate anyway.
On Tue, Feb 17, 2015 at 12:07 AM, Fernando Frediani
wrote:
> Hello bkil,
>
> Many thanks for your detailed response.
> I would gladly post it to openwrt-users if that w
Dear Fernando,
You should have posted this question to OpenWrt-User, but I will answer it here.
I haven't personally deployed such a configuration, yet. I don't think
you can do much besides enabling RTS/CTS at every CPE (client). Much
fewer connected clients will be supported compared to a TDMA
12 matches
Mail list logo
