On Tuesday 22 September 2009 01:36:32 pm Xavier wrote:
> On Tue, Sep 22, 2009 at 8:17 PM, David C. Rankin
>
> wrote:
> > Listmates,
> >
> >I have been chasing my tail on the madwifi issue and I think I
> > have found the problem. It's not madwifi at all, it's the timezone
> > handling.
>
On Tuesday 22 September 2009 01:29:03 pm Alessandro Doro wrote:
> On Tue, Sep 22, 2009 at 01:17:55PM -0500, David C. Rankin wrote:
> > Listmates,
> >
> > I have been chasing my tail on the madwifi issue and I think I have
> > found the problem. It's not madwifi at all, it's the timezone handlin
Le Tue, 22 Sep 2009 20:29:03 +0200,
Alessandro Doro a écrit :
> On Tue, Sep 22, 2009 at 01:17:55PM -0500, David C. Rankin wrote:
> > Listmates,
> >
> > I have been chasing my tail on the madwifi issue and I
> > think I have found the problem. It's not madwifi at all, it's the
> > timezone ha
On Tue, Sep 22, 2009 at 2:36 PM, Xavier wrote:
> On Tue, Sep 22, 2009 at 8:17 PM, David C. Rankin
> wrote:
>> Listmates,
>>
>> I have been chasing my tail on the madwifi issue and I think I have
>> found the
>> problem. It's not madwifi at all, it's the timezone handling.
>>
>
> WTF does
On Tue, Sep 22, 2009 at 8:17 PM, David C. Rankin
wrote:
> Listmates,
>
> I have been chasing my tail on the madwifi issue and I think I have
> found the
> problem. It's not madwifi at all, it's the timezone handling.
>
WTF does fsck/recovery console at boot have to do with slow wireless?
On Tue, Sep 22, 2009 at 01:17:55PM -0500, David C. Rankin wrote:
> Listmates,
>
> I have been chasing my tail on the madwifi issue and I think I have
> found the
> problem. It's not madwifi at all, it's the timezone handling.
>
> My box is dual-boot, Arch - Vista. Accordingly, the h
Listmates,
I have been chasing my tail on the madwifi issue and I think I have
found the
problem. It's not madwifi at all, it's the timezone handling.
My box is dual-boot, Arch - Vista. Accordingly, the hardware clock is
set to
localtime:
LOCALE="en_US.utf8"
HARDWARECLOCK="lo
7 matches
Mail list logo
