Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0004844]: Bridge-utils broken under kernel 2.4
Date: Tue, 9 Sep 2008 08:39:38 -0700	[thread overview]
Message-ID: <db6d82e983be50023a5325bf3b6cc6db@busybox.net> (raw)


A NOTE has been added to this issue. 
====================================================================== 
http://busybox.net/bugs/view.php?id=4844 
====================================================================== 
Reported By:                Feynman
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   4844
Category:                   Architecture Specific
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             09-08-2008 11:05 PDT
Last Modified:              09-09-2008 08:39 PDT
====================================================================== 
Summary:                    Bridge-utils broken under kernel 2.4
Description: 
Snapshot buildroot-20080905

The bridge-utils package compiles but the brctl command fails.
The error message is:
# brctl addbr br0
add bridge failed: Invalid argument

I think this is a problem with the bridge-utils 1.4. The former version
1.06 works fine.

My configuration is: 386, kernel 2.4, busybox 1.11.x
The project is openMGB, a RDC based NAS with WAP.


====================================================================== 

---------------------------------------------------------------------- 
 jacmet - 09-08-08 11:26  
---------------------------------------------------------------------- 
I don't have access to any system with a 2.4 kernel anymore - Does it work
if you change the version in bridge.mk back to v1.06? If so, please report
the problem with bridge-utils upstream. 

---------------------------------------------------------------------- 
 hmoffatt - 09-08-08 18:11  
---------------------------------------------------------------------- 
1.4 seems to use /sys/class/net which wouldn't exist on linux 2.4 

---------------------------------------------------------------------- 
 jacmet - 09-09-08 00:27  
---------------------------------------------------------------------- 
The README claims to only use sysfs stuff on 2.6 kernels, but I don't see
any fallback code. Probably the README is just stale - The bridge-utils
upsteam tarball seems pretty broken in general (no configure, configure.in
using wrong version, stale README, ..)

I don't have a problem with reverting to 1.06 if that fixes the bug
reporter's issue. 

---------------------------------------------------------------------- 
 hmoffatt - 09-09-08 06:15  
---------------------------------------------------------------------- 
Do we need to support 2.4? I don't think you can build it using buildroot?
I would've expected a project that is using current buildroot and current
busybox to also run a current kernel.. 

---------------------------------------------------------------------- 
 jacmet - 09-09-08 08:39  
---------------------------------------------------------------------- 
I don't personally have any interest in 2.4, but if we can keep it working
with small effort, then that's fine with me. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-08-08 11:05  Feynman        New Issue                                    
09-08-08 11:05  Feynman        Status                   new => assigned     
09-08-08 11:05  Feynman        Assigned To               => buildroot       
09-08-08 11:26  jacmet         Note Added: 0011194                          
09-08-08 18:11  hmoffatt       Note Added: 0011214                          
09-09-08 00:27  jacmet         Note Added: 0011224                          
09-09-08 06:15  hmoffatt       Note Added: 0011234                          
09-09-08 08:39  jacmet         Note Added: 0011244                          
======================================================================

             reply	other threads:[~2008-09-09 15:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-09 15:39 bugs at busybox.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-05 10:33 [Buildroot] [buildroot 0004844]: Bridge-utils broken under kernel 2.4 bugs at busybox.net
2008-10-13 18:32 bugs at busybox.net
2008-10-09  6:13 bugs at busybox.net
2008-10-07  8:43 bugs at busybox.net
2008-10-07  7:20 bugs at busybox.net
2008-09-13 12:19 bugs at busybox.net
2008-09-11 16:49 bugs at busybox.net
2008-09-10  0:01 bugs at busybox.net
2008-09-09 23:57 bugs at busybox.net
2008-09-09 15:49 bugs at busybox.net
2008-09-09 15:47 bugs at busybox.net
2008-09-09 13:15 bugs at busybox.net
2008-09-09  7:27 bugs at busybox.net
2008-09-09  1:11 bugs at busybox.net
2008-09-08 18:26 bugs at busybox.net
2008-09-08 18:05 bugs at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=db6d82e983be50023a5325bf3b6cc6db@busybox.net \
    --to=bugs@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox