Your message dated Tue, 2 Dec 2008 23:32:28 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: linux-image-2.6.15-1-686-smp: file lock not working over 
nfs
has caused the Debian Bug report #352013,
regarding linux-image-2.6.15-1-686-smp: file lock not working over nfs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
352013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=352013
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: linux-image-2.6.15-1-686-smp
Version: 2.6.15-4
Severity: normal

Eclipse does not start on this machine running
linux-image-2.6.15-1-686-smp. It complains about an I/O error while
locking a certain file accessed over nfs. This works on my custom 2.6.14
and on previous versions of linux-image-2.6.15-1-686-smp (at least
2.6.15-1)

Best regards,
Erhard


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14.4
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)

Versions of packages linux-image-2.6.15-1-686-smp depends on:
ii  module-init-tools             3.2.2-1    tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-3   Yet Another mkInitRD

Versions of packages linux-image-2.6.15-1-686-smp recommends:
ii  libc6-i686                    2.3.5-13   GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.15-1-686-smp/preinst/elilo-initrd-2.6.15-1-686-smp: true
  linux-image-2.6.15-1-686-smp/postinst/create-kimage-link-2.6.15-1-686-smp: 
true
  linux-image-2.6.15-1-686-smp/postinst/bootloader-test-error-2.6.15-1-686-smp:
  
linux-image-2.6.15-1-686-smp/prerm/would-invalidate-boot-loader-2.6.15-1-686-smp:
 true
  linux-image-2.6.15-1-686-smp/postinst/depmod-error-initrd-2.6.15-1-686-smp: 
false
  linux-image-2.6.15-1-686-smp/postinst/old-dir-initrd-link-2.6.15-1-686-smp: 
true
  linux-image-2.6.15-1-686-smp/preinst/lilo-initrd-2.6.15-1-686-smp: true
  linux-image-2.6.15-1-686-smp/postinst/old-system-map-link-2.6.15-1-686-smp: 
true
  linux-image-2.6.15-1-686-smp/postinst/old-initrd-link-2.6.15-1-686-smp: true
  linux-image-2.6.15-1-686-smp/preinst/overwriting-modules-2.6.15-1-686-smp: 
true
  linux-image-2.6.15-1-686-smp/prerm/removing-running-kernel-2.6.15-1-686-smp: 
true
  linux-image-2.6.15-1-686-smp/postinst/kimage-is-a-directory:
  linux-image-2.6.15-1-686-smp/preinst/lilo-has-ramdisk:
  linux-image-2.6.15-1-686-smp/preinst/failed-to-move-modules-2.6.15-1-686-smp:
* linux-image-2.6.15-1-686-smp/preinst/already-running-this-2.6.15-1-686-smp:
  linux-image-2.6.15-1-686-smp/preinst/abort-overwrite-2.6.15-1-686-smp:
  linux-image-2.6.15-1-686-smp/preinst/abort-install-2.6.15-1-686-smp:
  linux-image-2.6.15-1-686-smp/postinst/bootloader-error-2.6.15-1-686-smp:
  linux-image-2.6.15-1-686-smp/preinst/initrd-2.6.15-1-686-smp:
  linux-image-2.6.15-1-686-smp/preinst/bootloader-initrd-2.6.15-1-686-smp: true
  linux-image-2.6.15-1-686-smp/postinst/depmod-error-2.6.15-1-686-smp: false



--- End Message ---
--- Begin Message ---
Erhard Weinell wrote:
> Moritz Muehlenhoff schrieb:
> > On Thu, Feb 09, 2006 at 09:23:48AM +0100, Erhard Schultchen wrote:
> > > Package: linux-image-2.6.15-1-686-smp
> > > Version: 2.6.15-4
> > > Severity: normal
> > >
> > > Eclipse does not start on this machine running
> > > linux-image-2.6.15-1-686-smp. It complains about an I/O error while
> > > locking a certain file accessed over nfs. This works on my custom
> > > 2.6.14 and on previous versions of linux-image-2.6.15-1-686-smp (at
> > > least 2.6.15-1)
> >
> > Does this error still occur with more recent kernel versions?
> 
> No, I think the bug can be considered closed.

Ok, doing so.

Cheers,
        Moritz


--- End Message ---

Reply via email to