Package: ulogd
Severity: normal

Please note that the less intrusive patch only fixes the issue for
sparc.

It does not fix the unaligned trap for alpha (#348532), but that is
easy to add.

It also does not fix the issue for ppc, s390, i386 (#499607), mips or
mipsel. Those platforms have both 32bit and 64bit kernels in Debian.



An alternative to the intrusive patch would be to build two flavours
of ulogd for relevant platforms. The normal 32bit one as ulogd and a
64bit one as ulogd64. Users would then just have to make sure they
match the ulogd/ulogd64 with their kernel. This would involve keeping
the STRICT_ALIGNMENT part of the less intrusive patch and fixing the
build system to support -m64. There would be no need to patch the
struct ulog_packet_msg and the local include file could be removed.

The biggest obstacle to this is cdbs. I have no idea and no intention
of finding out how to get it to build the source twice.

MfG
        Goswin

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (499, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31.6-xen-2010.02.18 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages ulogd depends on:
ii  debconf [debconf-2.0]         1.5.28     Debian configuration management sy
ii  libc6                         2.10.2-6   Embedded GNU C Library: Shared lib
ii  lsb-base                      3.2-23     Linux Standard Base 3.2 init scrip

ulogd recommends no packages.

Versions of packages ulogd suggests:
pn  ulogd-mysql                   <none>     (no description available)
pn  ulogd-pcap                    <none>     (no description available)
pn  ulogd-pgsql                   <none>     (no description available)
pn  ulogd-sqlite3                 <none>     (no description available)



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to