Hi Denys,
Applied commit "a4d564ad zcip: fix link-local IP conflict detection" has
introduced wrong
comparison of source IP with our/choosen IP. This again leads to a new IP
being repacked
on every incoming ARP packet.
Please refer patch against current git attached.
Best Regards, Vladislav Grish
Any comments to this patch? It doesn't cause any bloat and allows for
sharing the struct among applets.
On Wed, 2015-03-04 at 18:46 +0200, Ari Sundholm wrote:
> From: Ari Sundholm
>
> This way it can be used by other applets without duplication.
>
> Signed-off-by: Ari Sundholm
> ---
> coreuti
Denys, is this patch acceptable? It has 7 iterations of review behind it
and I find it generally useful. It won't bloat busybox much and is of
course optional even if mainlined.
On Fri, 2015-03-06 at 18:43 +0200, Ari Sundholm wrote:
> From: Ari Sundholm
>
> bloat-o-meter:
>
> function
Le 18/03/2015 18:41, Laurent Bercot a écrit :
On 18/03/2015 18:08, Didier Kryn wrote:
No, you must write to the pipe to detect it is broken. And you won't
try to write before you've got an event from the netlink. This event
will be lost.
I skim over that discussion (because I don't agree wit
Le 18/03/2015 20:01, Harald Becker a écrit :
Do you think it matters losing one more event?
Here we are considering the case when fifosvd is killed (say by
admin's error). I understand lost events can be recovered. However there
is one distinctive advantage in detecting immediately the
This is basically a combination of the default (dump mode) and -f
(follow mode). Specifying -F makes logread first dump the log buffer and
then immediately start following it.
---
Changes since v1:
- help text extended to cover new flag
---
sysklogd/logread.c | 14 +++---
1 file changed, 1
Hi,
I am working on an embedded OS called YOCTO, which apparently includes BusyBox
into its build. YOCTO is currently running on a target board, and I am trying
to integrate an AMD Radeon E8860 GPU into it. This requires installation of a
driver called "fglrx", otherwise also known as AMD Catal
Dear Simon Chen,
This is very poor problem explanation, I am afraid. Please read this:
http://www.catb.org/esr/faqs/smart-questions.html
Best Regards, L.
On Thu, Mar 19, 2015 at 8:34 PM, Chen, Simon (N-DCR SYSTEM HOUSE)
wrote:
> Hi,
>
>
>
> I am working on an embedded OS called YOCTO, which app
On Thu, Mar 19, 2015 at 07:34:18PM +, Chen, Simon (N-DCR SYSTEM
HOUSE) wrote:
> Hi,
>
> I am working on an embedded OS called YOCTO, which apparently
> includes BusyBox into its build. YOCTO is currently running on a target
> board, and I am trying to integrate an AMD Radeon E8860 GPU into
On Wed, Mar 18, 2015 at 02:48 AM, Isaac Dunham said:
> Is this manifested as "the root device never shows up"?
Yes, although we call it the boot device.
> As the one who probably posted this, I can comment further:
> I've heard of one computer where this was an issue, a couple
> years ago; a numb
On Thu, Mar 19, 2015 at 06:02:33PM -0600, James Bowlin wrote:
> On Wed, Mar 18, 2015 at 02:48 AM, Isaac Dunham said:
> > Is this manifested as "the root device never shows up"?
>
> Yes, although we call it the boot device.
>
> > As the one who probably posted this, I can comment further:
> > I've
> On Mon, Mar 16, 2015 at 05:18:27PM +0100, Natanael Copa wrote:
> > Ininitial mdev -i patch for busybox which reads messages from stream
> > (so it should work with your fif manager):
> >
> > http://sprunge.us/ZjLK
> > (also attached)
> >
> > A few notes:
> > - Its completely untested but it com
12 matches
Mail list logo
