Like many, I came to Debian GNU/kFreeBSD when it was a way I could get
Debian and ZFS together.
Early on I contributed some patches (improved thread debugging in gdb,
and a working valgrind port being the two that I recall offhand in which
I had a great deal of pride at the time) which
Package: dovecot-core
Version: 1:2.2.15-1
Severity: important
Dear Maintainer,
After upgrading my Debian kFreeBSD machine from Wheezy to Jessie,
dovecot imap stopped working. The version from experiemental was also
broken in the same way.
After I attempt to sign in with valid information, the
Package: dpkg
Version: 1.17.23+local1
Severity: important
Tags: patch
On a Debian Jessie kFreeBSD system, start-stop-daemon sometimes exits with
an odd error:
$ sudo service nfsd restart
start-stop-daemon: _cpu_tick_frequency: no such symbol
The specific command invocation which was reliably
On Wed, Feb 11, 2015 at 05:36:16PM -0600, Jeff Epler wrote:
Some time ago I prepared patches that allowed me to build and use
[...]
Adam, I tried to Cc: you on this response, but your mail server rejected
the message:
This message was created automatically by mail delivery software
Some time ago I prepared patches that allowed me to build and use
valgrind on kFreeBSD. Unfortunately, this has not been incorporated
into the Debian package. I feel like I still haven't managed to figure
out how to effectively collaborate within the Debian project. I also
have no idea whether
On Debian kFreeBSD, uname -s says GNU/kFreeBSD.
so perhaps you want a second stanza in the Makefile
ifeq ($(shell uname -s),GNU/kFreeBSD)
LIBS += -lrt
endif
Jeff
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
The solution may simply be to link with -lrt.
$ cat shmopen.c
#include sys/mman.h
#include stdio.h
int main() { printf(%p\n, shm_open); return 0; }
$ gcc shmopen.c
/tmp/ccRPQFME.o: In function `main':
shmopen.c:(.text+0x5): undefined reference to `shm_open'
According to
http://pubs.opengroup.org/onlinepubs/7908799/xsh/unistd.h.html
_POSIX_VDISABLE is either undefined, or defined to a value other than
-1. As far as I can tell, no text requires that it be defined to a
valid *preprocessor* number. In fact,
I have a kfreebsd (debian 7 / kernel 9.0) system serving zfs file
systems over nfsv3 to linux (debian 7). It seems to work well, though
there are some user reports of problems using Libre Office document
recovery that I haven't looked into yet. I also failed to use nfsv4.
I manually maintain
Apparently freebsd kernels 9.2 and later have
security.bsd.unprivileged_mlock, which appears to default to permitted.
http://www.freebsd.org/cgi/man.cgi?query=mlocksektion=2manpath=FreeBSD+9.2-RELEASE
http://marc.info/?l=freebsd-archm=134617193210756
Is this test failure happening with kernel
I'm only a kFreeBSD user and don't have any official standing within the
Debian project, but all the same my preferences are
614253
where 6. is the proposed alternative to switch to Upstart if Linux uses
it, otherwise sysvinit.
Jeff
--
To UNSUBSCRIBE, email to
Could it be http://www.freebsd.org/cgi/query-pr.cgi?pr=164445 ?
It looks like that fix from reply 3 is not in kernel 9.0-10+deb70 which
is what I'm running (but I have Wheezy userspace, so I haven't
reproduced a problem either)
Jeff
--
To UNSUBSCRIBE, email to
You might consider doing what I did: Make two zfs partitions per disk.
Create a mirrored zpool from the first, smaller partitions; place files
needed for booting there. Create a raidz(2) pool from the bigger
partitions and use it for bulk storage. In fact, I've convinced myself
that the
upload.
+ * Use autoreconf, as the kfreebsd patch requires rebuilding configure
+
+ -- Jeff Epler jep...@unpythonic.net Thu, 17 Oct 2013 15:38:15 -0500
+
radvd (1:1.9.1-1.1) unstable; urgency=low
* Non-maintainer upload with maintainer approval.
diff -Nru radvd-1.9.1/debian/control radvd
On Thu, May 02, 2013 at 04:26:23PM +0200, Petr Salinger wrote:
Not really. We do not support named semaphores (sem_open),
but we do support (unnamed semaphores) (sem_init).
The named only functions returns ENOSYS.
In Wheezy on kfreebsd? The implementation of sem_open in
OK, this seems crazy to me but I feel obliged to note it:
When I build 3.8.1-3 in /usr/src or /tmp/wat, I can observe the failure when I
subsequently 'make check' in build-2.7/tests. When I build it in /tmp or
/tmp/wat/frugal-bonasfrarfsarfasrfasrf/pygobject-3.8.1 I do not.
However, I also note
valgrind (helgrind) on linux (sid amd64 chroot on wheezy amd64) didn't turn up
anything that looked too useful. There were a number of diagnostics of
this general form:
==12158== Lock at 0x603E5C0 was first observed
==12158==at 0x4C2EB32: pthread_mutex_init (in
Another bug that may be similar:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671785
In that bug I remark that a problem with pthread_mutex_unlock can be
observed on linux with valgrind --tool=helgrind. I haven't tried to
determine whether it's a similar problem here, but it might be worth
Since the reported trigger was an ssh flood, I tried
ssh -T -o 'PreferredAuthentications hostbased' localhost
(which on my system will result in a quick failed ssh because hostbased
authentication is not enabled in the server) in a tight, parallelized loop
with this construct:
for i in
On Thu, Mar 14, 2013 at 06:30:43PM +0100, Alessandro Ghedini wrote:
I'll have a look as soon as I have some free time. I was also thinking that
the
patch may be applied only in the kfreebsd builds, so it wouldn't interfere
with
the linux builds.
That sounds great, but I do not yet have the
I guess
this provides some level of confidence in the result.
Please consider my patch for a future release of mongodb.
Thanks,
Jeff Epler jep...@unpythonic.net
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture
It looks like freebsd9 ports has valgrind-snapshot which is based off of
valgrind 3.8.0:
http://cdn.bitbucket.org/stass/valgrind-freebsd/downloads/valgrind-freebsd-3.8.0.tar.bz2
There are a lot more changes than I would expect between this and the
upstream 3.8.0 tarball:
valgrind-3.8.0/FAQ.txt
I cleaned up the freebsd diffs, added some magic from this thread, and
filed a debbug about it (702729). I'm not 100% confident it won't cause
some debian/linux regression or that it's complete, but it's a step in
the right direction, particularly as it builds off of the version of
valgrind
On Wed, Mar 06, 2013 at 01:10:42PM -0600, Mark Johnson wrote:
I used the kFreeBSD debian installer (wheezy RC1) and I installed the
default desktop (xfce lightdm). Which is currently the most stable desktop:
xfce, kde, gnome, etc? Lightdm is utilizing one of my cores at 100%.
I saw this
Valgrind does appear to be aware of sysarch, implementing
sysarch(AMD64_SET_FSBASE) in
coregrind/m_syswrap/syswrap-amd64-freebsd.c.
Jeff
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
On Thu, Mar 07, 2013 at 09:40:38AM -0600, Jeff Epler wrote:
Valgrind does appear to be aware of sysarch, implementing
sysarch(AMD64_SET_FSBASE) in
coregrind/m_syswrap/syswrap-amd64-freebsd.c.
Aha. eglibc is testing that the syscall succeeds, which is indicated by
setting RAX to 0
On Thu, Mar 07, 2013 at 05:49:55PM +0100, Petr Salinger wrote:
Valgrind does appear to be aware of sysarch, implementing
sysarch(AMD64_SET_FSBASE) in
coregrind/m_syswrap/syswrap-amd64-freebsd.c.
Aha. eglibc is testing that the syscall succeeds, which is indicated by
setting RAX to 0.
On Sun, Mar 03, 2013 at 12:20:57PM +, Steven Chamberlain wrote:
#5 0x000800d21f2c in *__GI___libc_free (mem=optimized out) at
malloc.c:3736
ar_ptr = 0x800ff3240
p = optimized out
#6 0x000800844a79 in gvFreeContext () from /usr/lib/libgvc.so.5
No symbol
On Thu, Feb 28, 2013 at 01:20:18PM -0800, Christoph Egger wrote:
If Jeff doesn't submit it to gdb mainline himself, I'll take care of
that as a kFreeBSD Porter.
Thank you.
Jeff
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Mon, Feb 04, 2013 at 03:00:14PM -0800, Christoph Egger wrote:
Hi!
Thanks for your patch. However gdb with the patch applied dies for me:
I must have attached a wrong patch, or you're applying it to a different gdb.
(I started with 7.4.1-3)
It looks like you're probably dying here, but in
It looks like the problem is the value of MAXHOSTNAMELEN from
sys/param.h--this program prints 64 on linux but 256 on kfreebsd:
#include sys/param.h
#include fcntl.h
#include stdio.h
int main() {
printf(%d\n, (int) MAXHOSTNAMELEN);
return 0;
}
As you can see, the structure sizes won't
Michael,
For now it sounds like there's no consensus that this is a bug in
initgroups(3) in eglibc or setgroups(2) in kfreebsd.
If you're aware of this leading to a bug in a specific Debian package
(particularly if it is a bug with a security impact), please file a bug
against that package.
On Mon, Jan 14, 2013 at 04:46:39PM -0800, Christoph Egger wrote:
(gdb) run
Program received signal 32, LinuxThreads restart signal.
__pthread_sigsuspend () at
../ports/sysdeps/unix/bsd/bsd4.4/kfreebsd/linuxthreads/pt-sigsuspend.S:24
24
This is not yet complete or debugged, but it improves things.
The signals.c patch makes gdb not be confused by the signals that
LinuxThreads(sic) uses internally; you can even 'handle LTRESTART
nostop' if you prefer (you probably do so prefer). This is a slightly
different version of a patch
+ds1-9.1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * Improve reporting of signals = 32
+
+ -- Jeff Epler jepler@localhost Mon, 14 Jan 2013 20:44:54 -0600
+
freebsd-utils (9.0+ds1-9) unstable; urgency=low
[ Steven Chamberlain ]
diff -Nru freebsd-utils-9.0+ds1/debian/patches
On Sun, Dec 30, 2012 at 05:34:10PM -0800, Christoph Egger wrote:
However, I still believe that the problem is either in python-gtk2 or
python-gtk2's FAQ advice on how to use gtk.gdk.threads_init().
Can you be a bit more verbose about that? Also the FAQ might well be
right and what we are
If it's a question of minimal impact to fix the specific crash that
grub-probe encounters, then there are two more minimal ways to fix this
specific problem that come to mind:
replace reallocf with realloc---but in the unlikely case that realloc
fails, it doesn't deallocate the argument (this is
; urgency=low
+
+ * Non-maintainer upload.
+ * Avoid a kFreeBSD crash by telling python-gtk not to hook readline
+Closes: #671785
+
+ -- Jeff Epler jepler@localhost Sat, 22 Dec 2012 10:35:25 -0600
+
reportbug (6.4.3) unstable; urgency=low
* reportbug/debbugs.py
diff -Nru reportbug-6.4.3
It looks like this is the problem, and it exists repeatedly in
freebsd-libs-9.0+ds1-7
geom_getxml.c: In function ‘geom_getxml’:
geom_getxml.c:59:2: warning: implicit declaration of function ‘reallocf’
[-Wimplicit-function-declaration]
geom_getxml.c:59:2: warning: return makes pointer from
silently
+in the future
+
+ -- Jeff Epler jep...@unpythonic.net Fri, 21 Dec 2012 13:20:44 -0600
+
freebsd-libs (9.0+ds1-3) unstable; urgency=low
[ Robert Millan ]
diff -Nru freebsd-libs-9.0+ds1/debian/patches/implicit-declaration
freebsd-libs-9.0+ds1/debian/patches/implicit-declaration
[snipped astute observations about the size of the xml data being important]
On Fri, Dec 21, 2012 at 10:02:45PM +, Steven Chamberlain wrote:
And I'm worried about some of the other packages mentioned, where the
error shows on kfreebsd-* or maybe hurd-*, but not on other arches.
Should they
@@ -1,3 +1,12 @@
+parted (2.3-11.1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * Treat adaN devices as SCSI (cam) devices (Closes: #693510)
+ * Fill out the drive model information for ata adaN devices
+ * Fill out the physical sector size information for ata adaN devices
+
+ -- Jeff
Package: libzfs1
Version: 9.0-3
Severity: normal
Tags: patch
zpool status incorrectly prints raidz vdevs as -0 instead of
raidz1-0, e.g.
$ zpool status mpool
pool: mpool
state: ONLINE
scan: scrub repaired 0 in 0h52m with 0 errors on Sun Dec 16 12:43:40 2012
config:
Tags: patch
Today I filed a bug about this same problem, having found this earlier
report too late. I believe the patch on bug #696119 will address this
problem (which is not seen on freebsd due to libc differences).
As I'm a newbie at the debian bugtracker I'm not sure how to merge the
two
On Mon, Dec 17, 2012 at 02:24:42AM +, Steven Chamberlain wrote:
Originally in #653929 it was said that this bug breaks GRUB in some way,
and could prevent use of RAID-Z as a root filesystem; do you know if
that is true?
Unfortunately, I don't know the answer to this. I am booting from a
45 matches
Mail list logo
