On Friday 10 April 2009 22:50:44 Reinhard Tartler wrote:
> kelmo writes:
>
> >> https://launchpad.net/~cjwatson/+archive/ppa
> >>
> >> ... to install the wpasupplicant package from there, and report whether
> >> it fixes this bug? This test is only valid if you're already running up-
> >> to-d
kelmo writes:
>> https://launchpad.net/~cjwatson/+archive/ppa
>>
>> ... to install the wpasupplicant package from there, and report whether
>> it fixes this bug? This test is only valid if you're already running up-
>> to-date Jaunty.
>>
>
> Any chance I could see a diff so that divergence be
On Thursday 09 April 2009 02:37:37 Colin Watson wrote:
> Could people affected by this bug who are running up-to-date Jaunty
> systems please follow the directions at:
>
> https://launchpad.net/~cjwatson/+archive/ppa
>
> ... to install the wpasupplicant package from there, and report whether
>
On Friday 27 February 2009 20:51:41 Colin Watson wrote:
> Having reviewed the whole bug, I have to say that this all seems like an
> order of magnitude more work than is really required. The suggested
> approaches involve lots of complex interface definition, strict ordering
> constraints, and the
On Friday 05 December 2008 05:13:10 Soren Hansen wrote:
> kelmo, you wouldn't read about this bug on Debian's BTS, because it's an
> Ubuntu specific bug. Last I checked Debian hasn't changed its boot
> process to do all this stuff dynamically, i.e. attempt configuration of
> everything you possibly
On Thursday 04 December 2008 20:29:26 Soren Hansen wrote:
> > I disagree to an extent, the problem doesn't sound specific to
> > wpa_supplicant's shell glue at all,
>
> If wpasupplicant tells ifupdown that it's done configuring the
> interface, and that everything went fine, but it that's not actu
On Friday 05 December 2008 00:25:02 Reinhard Tartler wrote:
> Soren Hansen <[EMAIL PROTECTED]> writes:
>
> > Glancing at its pre-up script, I'm guessing your problem is this:
> >
> > # quit if executables are not installed
> > if [ ! -x "$WPA_SUP_BIN" ] || [ ! -x "$WPA_CLI_BIN" ]; then
> >
Soren Hansen <[EMAIL PROTECTED]> writes:
> Glancing at its pre-up script, I'm guessing your problem is this:
>
> # quit if executables are not installed
> if [ ! -x "$WPA_SUP_BIN" ] || [ ! -x "$WPA_CLI_BIN" ]; then
> exit 0
> fi
This is a perfectly valid use case when the wpasupplicant pa
Soren Hansen <[EMAIL PROTECTED]> writes:
>> but rather, the inflexibility of the statically maintained ifupdown
>> software on an ever evolving Debian/Ubuntu software ecosystem.
>
> What exactly do you mean by "statically maintained"?
WPA keys written to /etc/network/interfaces as outlined in
/us
On Tuesday 02 December 2008 16:52:21 Reinhard Tartler wrote:
> Mathias Gug <[EMAIL PROTECTED]> writes:
>
> > Waiting until S40networking is run brings up an issue with iscsi
> > devices. The current way of handling iscsi devices is to treat them as
> > local devices by making sure that all iscsi d
Hi Reinhard,
On Mon, Dec 01, 2008 at 10:49:52PM +0100, Reinhard Tartler wrote:
> Reporters claim this bug to be fixed. What symptoms did recently arise?
>
On the wpa_supplicant front, none. However it raises issue with iscsi
devices as outlined below.
> > It seems that the issue is with the ifup
Mathias Gug <[EMAIL PROTECTED]> writes:
> Reopening this bug in wpa_supplicant.
Reporters claim this bug to be fixed. What symptoms did recently arise?
> It seems that the issue is with the ifupdown script from
> wpa_supplicant.
What is the issue?
> If the script cannot be run early in the boo
captain haddock <[EMAIL PROTECTED]> writes:
> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/40763
> is a (partial) duplicate and confirms the problem for a current Hardy
> Heron install.
It does not. bug #40763 is about an issue in ipw2200. Later in the
bugtrail some user see
Alessio Gaeta <[EMAIL PROTECTED]> writes:
> maybe there is some odd interaction with udev rule ifupdown.rules?
> Udev is started before than Networking in the init process and (as far
> as I understood) tries to configure the interfaces it found. So, when
> Networking starts, interfaces are already
14 matches
Mail list logo
