So
Linux does not have a “PATH” while booting? I have brctl in the
/bin and the /sbin directory.
I looked
at the /etc/init.d/network script and there is mention of bridges but no
direct call to brctl.
Do you
think I would be better of recompiling the Kernel with bridging built in?
Well...
You need to determine what script the error is coming from...
Probably /etc/rc.d/init.d/network
(or it could be /etc/init.d/network)
Bert
Hubbs wrote:
> " That sounds like you
need the full path to brctl in your script."
>
> What script?
>
>
>
> Bert Hubbs
> McGlinchey Stafford and
> Youngblood & Bendalin,
PLLC
> 2711 N. Haskell Ave.
> Suite 2700, LB 25
> Dallas, TX 75204
> 214-257-1817 (direct dial)
> 469-235-1817 (mobile)
> 214-257-1881 (fax)
>
>
> -----Original Message-----
> From: Bruce Ferrell [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 05, 2004
9:41 PM
> To: Bert Hubbs
> Cc: [EMAIL PROTECTED]
> Subject: Re: [Bridge] Bridge support unavailable
>
> That sounds like you need the
full path to brctl in your script.
>
> Which leads me to MY question
for the list. I'm having problem getting
> bridge.o to build correctly on
2.4.25 (linus). Is this a case where I'd
>
> be better off with it built
static?
>
> Bert Hubbs wrote:
>
>>When I start Linux I get an
error:
>>
>>"Bridge support unavailable: brctl not found".
>>
>>And then eth0 - 2 load with
no problems. After system is up I can
>
> build
>
>>the bridge but it does not
survive a reboot. Do I need a startup
>
> script
>
>>or should it build from
the:
>>
>>/etc/init.d/bridge
>>/etc/sysconfig/network-scripts/ifcfg-bro
>>/etc/sysconfig/network-scripts/ifcfg-eth0
>>/etc/sysconfig/network-scripts/ifcfg-eth1
>>/etc/sysconfig/network-scripts/ifcfg-eth2
>>
>>
>>
>>I am using Core2
>>
>>
>>
>>Bert Hubbs
>>McGlinchey Stafford and
>>Youngblood & Bendalin,
PLLC
>>2711 N. Haskell Ave.
>>Suite 2700, LB 25
>>Dallas, TX 75204
>>214-257-1817 (direct dial)
>>469-235-1817 (mobile)
>>214-257-1881 (fax)
>>
>>
>>
>>The information contained
in this e-mail message is intended only for
>
> the personal and confidential
use of the recipient(s) named above. This
> message may be an
attorney-client communication and/or work product and
> as such is privileged and
confidential. If the reader of this message is
> not the intended recipient or
an agent responsible for delivering it to
> the intended recipient, you
are hereby notified that you have received
> this document in error and
that any review, dissemination, distribution,
> or copying of this message is
strictly prohibited. If you have received
> this communication in error,
please notify us immediately by e-mail, and
> delete the original message.
>
>>
>>
>>
>
------------------------------------------------------------------------
>
>>_______________________________________________
>>Bridge mailing list
>>[EMAIL PROTECTED]
>>http://lists.osdl.org/mailman/listinfo/bridge
>
>
>
> The information contained in
this e-mail message is intended only for the personal and confidential use of
the recipient(s) named above. This message may be an attorney-client
communication and/or work product and as such is privileged and confidential.
If the reader of this message is not the intended recipient or an agent
responsible for delivering it to the intended recipient, you are hereby
notified that you have received this document in error and that any review,
dissemination, distribution, or copying of this message is strictly prohibited.
If you have received this communication in error, please notify us immediately
by e-mail, and delete the original message.
>
