On Nov 10, Julien Cristau wrote:
> Do you have any details? I skimmed through the 146->147 changes, and
Nevermind, it's inotify-with-flags also in that commit.
> the CLOEXEC flags were the only commit I found that could break on older
> kernels. I might have missed something else though. I th
On Tue, Nov 10, 2009 at 18:05:05 +0100, Marco d'Itri wrote:
> On Nov 10, Julien Cristau wrote:
>
> > commit 26347a4c5538008318188118872490128f43fcd3 looks suspicious. udev
> > should probably keep a fallback for kernel versions without the flags.
> There is also something incompatible related t
On Tue, Nov 10, 2009 at 16:45:03 +0100, Marco d'Itri wrote:
> On Nov 10, Xavier Queralt wrote:
>
> > I can see exactly the same error with a standard kernel from debian
> > repositories.
>
> Looks like 147 requires 2.6.27.
>
commit 26347a4c5538008318188118872490128f43fcd3 looks suspicious. u
On Nov 10, Julien Cristau wrote:
> commit 26347a4c5538008318188118872490128f43fcd3 looks suspicious. udev
> should probably keep a fallback for kernel versions without the flags.
There is also something incompatible related to inotify in 147, upstream
just does not care about supporting old kern
On Tue, Nov 10, 2009 at 07:39:23AM -0700, Gordon Haverland wrote:
> On November 10, 2009, Marco d'Itri wrote:
> > On Nov 10, Gordon Haverland
> wrote:
> > > I don't know, is an initialization error the same as a
> > > creation error? Trying to upgrade udev an hour or so ago, I
> > > get:
> > > se
5 matches
Mail list logo
