Bug#697003: initscripts: postinst fails: mv /dev/shm/* misses dot (hidden) files
Package: initscripts
Version: 2.88dsf-34
Severity: important
User: debian-bsd@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-bsd@lists.debian.org
Hi,
The initscripts package is failing to upgrade from -32 to -34 in a
GNU/kFreeBSD jailed system:
Preparing to replace initscripts 2.88dsf-32 (using
.../initscripts_2.88dsf-34_kfreebsd-amd64.deb) ...
Unpacking replacement initscripts ...
Processing triggers for man-db ...
Setting up initscripts (2.88dsf-34) ...
Installing new version of config file /etc/init.d/checkroot-bootclean.sh ...
Installing new version of config file /etc/init.d/mountall.sh ...
Installing new version of config file /etc/init.d/mountall-bootclean.sh ...
Installing new version of config file /etc/init.d/mountnfs-bootclean.sh ...
Installing new version of config file /etc/init.d/umountnfs.sh ...
mv: cannot stat `/run/shm/*': No such file or directory
dpkg: error processing initscripts (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
initscripts
E: Sub-process /usr/bin/dpkg returned an error code (1)
There are so many issues here:
+ DEVSHM=d
+ RUN=d
+ RUNSHM=d
+ mountpoint -q /dev/
+ DEV=m
+ mountpoint -q /dev/shm/
+ [ -L /dev/shm ]
+ mountpoint -q /run/
+ mountpoint -q /run/shm/
+ [ -L /run/shm ]
+ RUNSTATE=mddd
+ RUNACTION=NONE
My jailed system's /dev is rather special (a sort of read-only devfs
mount); it doesn't contain a /dev/shm directory or link, and I'm not
even able to create one as root.
+ ls -A /run/shm
+ [ .tmpfs != ]
This command indicates there is a file in this folder, called .tmpfs
(though it isn't really a tmpfs), and so:
+ mv /run/shm/* /dev/shm
mv: cannot stat `/run/shm/*': No such file or directory
The wildcard does not match the .tmpfs file, and since there are no
matching files this is an error. Postinst fails.
On the other hand, if there'd been some non-hidden files/directories
there, they would be moved, but any remaining hidden ones would be
deleted(!).
Another problem is that if /dev/shm doesn't exist, and since a trailing
slash wasn't used; if my /dev had been writable and this command
succeeded, it could place some directory from /run/shm there with
arbitrary ownership/permissions, or some arbitrary link with scary
consequences.
How about doing it this way instead - I think this is safer, complete,
and even avoids races:
# find /run/shm -mindepth 1 -xdev -execdir mv \{\} /dev/shm/ \;
Anyway; why are we doing any of this? In this (awkward) situation we'd
ideally leave /run/shm contents where they are already, and /dev/shm
must stay non-existent.
I think this is a similar scenario to:
- /dev/ is bind mounted, and /dev/shm is a non-bind-mounted
directory. We can't fix this, so we should just create the
/run/shm directory and leave /dev/shm alone.
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: kfreebsd-amd64 (x86_64)
Kernel: kFreeBSD 9.0-2-amd64
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages initscripts depends on:
ii coreutils 8.13-3.4
ii debianutils 4.3.2
ii libc0.1 2.13-37
ii lsb-base4.1+Debian8
ii sysv-rc 2.88dsf-34
ii sysvinit-utils 2.88dsf-34
Versions of packages initscripts recommends:
ii e2fsprogs 1.42.5-1
ii psmisc 22.19-1
initscripts suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50e0.7040...@pyro.eu.org
Re: Bug#697003: initscripts: postinst fails: mv /dev/shm/* misses dot (hidden) files
Hi,
This may have been my fault. I can avoid this by actually mounting /run
as tmpfs (from the host, when constructing the jail). This allows a
successful and sane upgrade:
+ RUNSTATE=mdmd
+ RUNACTION=NONE
+ echo Due to mounts in the chroot, /dev/shm can't be safely symlinked
to /run/shm. Please correct this problem manually.
That said, some of the other problems I mentioned sound serious: the
handling of hidden files in /dev/shm or /run/shm when moving things.
On 30/12/12 18:31, Steven Chamberlain wrote:
# find /run/shm -mindepth 1 -xdev -execdir mv \{\} /dev/shm/ \;
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50e08d57.7010...@pyro.eu.org
Bug#697005: unblock: freebsd-utils/9.0+ds1-9
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package freebsd-utils Fixing several issues, including a failed release upgrade and a segfault. The implicit declarations problem is not fixing any hard known problems, however has a probability that there are problems it fixes (including the rpc.lockd bug #664812) but I can take it out again if you prefer. diff -Nru freebsd-utils-9.0+ds1/debian/changelog freebsd-utils-9.0+ds1/debian/changelog --- freebsd-utils-9.0+ds1/debian/changelog 2012-09-23 08:20:50.0 -0700 +++ freebsd-utils-9.0+ds1/debian/changelog 2012-12-29 16:08:30.0 -0800 @@ -1,3 +1,21 @@ +freebsd-utils (9.0+ds1-9) unstable; urgency=low + + [ Steven Chamberlain ] + * Fix geli initscript to support more than one geli_device as intended. +(Closes: #694374) + * If devfs is unavailable (for example in a jail environment) the +freebsd-utils start action would exit with non-zero status, causing postinst +to fail. Instead, return zero exit status but print a warning. +(Closes: #695679) + + [ Christoph Egger ] + * Import patch from Steven Chamberlain to fix segfault getting bridge +status (Closes: #696514) + * Import patch from Steven Chamberlain fixing implicit declarations + * Upload to unstable + + -- Steven Chamberlain ste...@pyro.eu.org Tue, 11 Dec 2012 20:28:30 + + freebsd-utils (9.0+ds1-8) unstable; urgency=low * Team upload. diff -Nru freebsd-utils-9.0+ds1/debian/freebsd-utils.init freebsd-utils-9.0+ds1/debian/freebsd-utils.init --- freebsd-utils-9.0+ds1/debian/freebsd-utils.init 2012-09-15 14:29:07.0 -0700 +++ freebsd-utils-9.0+ds1/debian/freebsd-utils.init 2012-12-29 14:00:54.0 -0800 @@ -24,13 +24,17 @@ fi log_action_begin_msg Loading devfs rules -devfs ruleset 1 -devfs rule delset -for rule in /etc/devfs.d/*.rules ; do - egrep -v '^[[:space:]]*(#|$)' $rule | devfs rule add - -done -devfs rule applyset -log_action_end_msg $? +if devfs ruleset 1 ; then + devfs rule delset + for rule in /etc/devfs.d/*.rules ; do +egrep -v '^[[:space:]]*(#|$)' $rule | devfs rule add - + done + devfs rule applyset + log_action_end_msg $? +else + # devfs unavailable, probably in a jail environment; no point proceeding + log_end_msg 255 || exit 0 # (warning) +fi log_action_begin_msg Setting up /dev links # setup /dev/cdrom symlink diff -Nru freebsd-utils-9.0+ds1/debian/geom.geli.init freebsd-utils-9.0+ds1/debian/geom.geli.init --- freebsd-utils-9.0+ds1/debian/geom.geli.init 2012-09-15 14:29:07.0 -0700 +++ freebsd-utils-9.0+ds1/debian/geom.geli.init 2012-12-29 14:00:54.0 -0800 @@ -141,8 +141,10 @@ fi count=$((count+1)) done - log_end_msg $RET - exit $RET + if ! [ $RET = 0 ]; then + log_end_msg $RET + exit $RET + fi fi done diff -Nru freebsd-utils-9.0+ds1/debian/patches/044_ifbridge.diff freebsd-utils-9.0+ds1/debian/patches/044_ifbridge.diff --- freebsd-utils-9.0+ds1/debian/patches/044_ifbridge.diff 1969-12-31 16:00:00.0 -0800 +++ freebsd-utils-9.0+ds1/debian/patches/044_ifbridge.diff 2012-12-29 16:06:43.0 -0800 @@ -0,0 +1,13 @@ +Index: freebsd-utils-9.0+ds1/sbin/ifconfig/ifbridge.c +=== +--- freebsd-utils-9.0+ds1.orig/sbin/ifconfig/ifbridge.c2007-11-04 08:32:27.0 + freebsd-utils-9.0+ds1/sbin/ifconfig/ifbridge.c 2012-12-29 20:27:46.888636491 + +@@ -46,6 +46,8 @@ + #include stdlib.h + #include unistd.h + ++#include netinet/ether.h /* for ether_aton, etherntoa */ ++ + #include net/ethernet.h + #include net/if.h + #include net/if_bridgevar.h diff -Nru freebsd-utils-9.0+ds1/debian/patches/045_implicit-declaration.diff freebsd-utils-9.0+ds1/debian/patches/045_implicit-declaration.diff --- freebsd-utils-9.0+ds1/debian/patches/045_implicit-declaration.diff 1969-12-31 16:00:00.0 -0800 +++ freebsd-utils-9.0+ds1/debian/patches/045_implicit-declaration.diff 2012-12-29 16:10:01.0 -0800 @@ -0,0 +1,324 @@ +Index: freebsd-utils-9.0+ds1/usr.sbin/mountd/mountd.c +=== +--- freebsd-utils-9.0+ds1.orig/usr.sbin/mountd/mountd.c2012-12-29 19:56:58.0 + freebsd-utils-9.0+ds1/usr.sbin/mountd/mountd.c 2012-12-29 20:05:01.478673213 + +@@ -80,6 +80,8 @@ + #include stdlib.h + #include string.h + #include unistd.h ++#include bsd/stdio.h ++ + #include pathnames.h + #include mntopts.h + +Index:
Bug#697006: unblock: freebsd-libs/9.0+ds1-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package freebsd-libs This fixes a segfault in grub-probe due to a broken libgeom diff -Nru freebsd-libs-9.0+ds1/debian/changelog freebsd-libs-9.0+ds1/debian/changelog --- freebsd-libs-9.0+ds1/debian/changelog 2012-05-25 09:37:58.0 -0700 +++ freebsd-libs-9.0+ds1/debian/changelog 2012-12-29 15:49:51.0 -0800 @@ -1,3 +1,16 @@ +freebsd-libs (9.0+ds1-4) unstable; urgency=low + + [ Christoph Egger ] + * Upload to unstable + + [ Jeff Epler ] + * Fix 'warning: implicit declaration of function 'reallocf' +(and several other functions) (Closes: 685625) + * Make that warning an error so that it does not pass silently +in the future + + -- Christoph Egger christ...@debian.org Sat, 29 Dec 2012 15:49:19 -0800 + 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 --- freebsd-libs-9.0+ds1/debian/patches/implicit-declaration1969-12-31 16:00:00.0 -0800 +++ freebsd-libs-9.0+ds1/debian/patches/implicit-declaration2012-12-29 15:49:02.0 -0800 @@ -0,0 +1,70 @@ +Description: Fix crashes due to undeclared functions + The consequence of at least one of these (in geom_getxml.c) was a crash + when there was a lot of data in kern.geom.confdml. + . + freebsd-libs (9.0+ds1-3.1) UNRELEASED; urgency=low + . + * Fix 'warning: implicit declaration of function 'reallocf' + (and several other functions) (Closes: 685625) +Author: Jeff Epler jep...@unpythonic.net +Bug-Debian: http://bugs.debian.org/685625 + +--- +The information above should follow the Patch Tagging Guidelines, please +checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here +are templates for supplementary fields that you might want to add: + +Forwarded: no +Last-Update: 2012-12-21 + +--- freebsd-libs-9.0+ds1.orig/lib/libdevstat/devstat.c freebsd-libs-9.0+ds1/lib/libdevstat/devstat.c +@@ -34,6 +34,7 @@ __FBSDID($FreeBSD$); + #include sys/errno.h + #include sys/resource.h + #include sys/queue.h ++#include bsd/stdlib.h + + #include ctype.h + #include err.h +--- freebsd-libs-9.0+ds1.orig/lib/libusbhid/usage.c freebsd-libs-9.0+ds1/lib/libusbhid/usage.c +@@ -36,6 +36,7 @@ __FBSDID($FreeBSD$); + #include stdio.h + #include stdlib.h + #include string.h ++#include bsd/stdio.h + + #include usbhid.h + +--- freebsd-libs-9.0+ds1.orig/lib/libgeom/geom_ctl.c freebsd-libs-9.0+ds1/lib/libgeom/geom_ctl.c +@@ -39,6 +39,7 @@ + #include string.h + #include stdlib.h + #include paths.h ++#include bsd/stdlib.h + + #include sys/queue.h + +--- freebsd-libs-9.0+ds1.orig/lib/libgeom/geom_getxml.c freebsd-libs-9.0+ds1/lib/libgeom/geom_getxml.c +@@ -33,6 +33,8 @@ + #include sys/sysctl.h + #include stdlib.h + #include string.h ++#include bsd/stdlib.h ++ + #include libgeom.h + + char * +--- freebsd-libs-9.0+ds1.orig/sys/netinet/libalias/alias_db.c freebsd-libs-9.0+ds1/sys/netinet/libalias/alias_db.c +@@ -157,6 +157,7 @@ __FBSDID($FreeBSD$); + #include sys/errno.h + #include sys/time.h + #include unistd.h ++#include bsd/stdlib.h + #endif + + #include sys/socket.h diff -Nru freebsd-libs-9.0+ds1/debian/patches/series freebsd-libs-9.0+ds1/debian/patches/series --- freebsd-libs-9.0+ds1/debian/patches/series 2012-05-19 05:26:07.0 -0700 +++ freebsd-libs-9.0+ds1/debian/patches/series 2012-12-29 15:49:02.0 -0800 @@ -18,3 +18,4 @@ libusb_backward.diff libbsd_nlist.diff kvm_size_t_kludge.diff +implicit-declaration diff -Nru freebsd-libs-9.0+ds1/debian/rules freebsd-libs-9.0+ds1/debian/rules --- freebsd-libs-9.0+ds1/debian/rules 2012-05-25 09:34:52.0 -0700 +++ freebsd-libs-9.0+ds1/debian/rules 2012-12-29 15:49:02.0 -0800 @@ -18,7 +18,8 @@ revision := $(shell echo $(full_version) | sed -e 's/^[^+-]*//g') CFLAGS = -Wall -g -pipe -fPIC -I. -I$(CURDIR)/sys -D_GNU_SOURCE \ - -D__va_list=__builtin_va_list + -D__va_list=__builtin_va_list \ +-Werror=implicit-function-declaration ifneq (,$(filter noopt,$(DEB_BUILD_OPTIONS))) CFLAGS += -O0 unblock freebsd-libs/9.0+ds1-3 -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 10.0-0-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121230185618.3133.93818.report...@mitoraj.siccegge.de
Re: Bug#697003: initscripts: postinst fails: mv /dev/shm/* misses dot (hidden) files
Control: severity -1 minor On 30/12/12 19:07, Roger Leigh wrote: Does /dev/shm exist on a standard kFreeBSD install? It gets created by initscripts as symlink to /run/shm. Otherwise it would not be there; apparently Linux 2.6 invented it and it didn't seem too popular with upstream FreeBSD. It's a glibc requirement. I didn't know this. Software running in the jails fortunately seems to be using /run/shm properly. Within jails, I cannot write to /dev (even as root) so shm cannot be created as a directory or symlink. But as an alternative I can create it from the host system before booting, so that will do as a workaround and for compatibility. Jails, and how to use them, are still a bit experimental/undocumented for GNU/kFreeBSD. Thanks for your input on this; I'll make sure this gets written up somewhere. + ls -A /run/shm + [ .tmpfs != ] This command indicates there is a file in this folder, called .tmpfs (though it isn't really a tmpfs), and so: Why does this file exist here? It's timestamped from when the jailed system booted, which would have been with initscripts 2.88dsf-32. It seems to be created by mount_shm in mount-functions.sh. Is it missing from the cleanup here in bootmisc? # Remove bootclean's flag files. # Don't run bootclean again after this! rm -f /tmp/.clean /lib/init/rw/.clean /run/.clean /run/lock/.clean rm -f /tmp/.tmpfs /lib/init/rw/.tmpfs /run/.tmpfs /run/lock/.tmpfs While here - could neaten this up a little: for dir in /lib/init/rw /tmp /run /run/lock /run/shm; do rm -f $dir/.clean $dir/.tmpfs done On the other hand, if there'd been some non-hidden files/directories there, they would be moved, but any remaining hidden ones would be deleted(!). For the use case in question (in chroots) this is by design. There is no use case for dotfiles in /dev/shm. In that case, the ls -A flag is unnecessary? A plain ls would determine if anything in that directory needs keeping. And the error with mv would be avoided. This is certainly safer. However, we should be catering for this already--we shouldn't be doing any modification of /dev if it's a mountpoint of any sort. I'm not sure exactly what you mean by modification, but at least for the mmdd|mddd cases it will try to move files to /dev/shm Maybe it's not a realistic situation, but since there is no trailing slash, if /dev/shm didn't exist, a malicious user could have created in advance: 1. a symlink /run/shm/oops - /etc (which gets placed first as /dev/shm) 2. regular file /run/shm/passwd (which gets written over /etc/passwd) Currently we are making the assumption that it will be present, and I'm not sure if that's a bug or not. I'm not sure either. The above issue poses a security risk, so I'd consider adding a trailing slash (so that mv fails with an error instead); I guess it is unlikely though and so needn't be fixed with any urgency. Thanks! Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50e0a43f.7000...@pyro.eu.org
Bug#697015: imagevis3d: FTBFS[kfreebsd]: error: 'POSIX_FADV_WILLNEED' was not declared in this scope
Package: src:imagevis3d Version: 3.0.0-1 Severity: serious Tags: sid wheezy User: debian-bsd@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-bsd@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: g++ -c -DPACKAGE_MANAGER -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -std=c++0x -fno-strict-aliasing -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -D_REENTRANT -Wall -W -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/glibc-g++ -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4 -I. -I3rdParty/GLEW -IIO/3rdParty/boost -IIO/3rdParty/zlib -IBasics -IIO/exception -I/usr/include/lua5.2 -I/usr/X11R6/include -I. -o Build/objects/LargeFileFD.o Basics/LargeFileFD.cpp g++ -c -DPACKAGE_MANAGER -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -std=c++0x -fno-strict-aliasing -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -D_REENTRANT -Wall -W -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/glibc-g++ -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4 -I. -I3rdParty/GLEW -IIO/3rdParty/boost -IIO/3rdParty/zlib -IBasics -IIO/exception -I/usr/include/lua5.2 -I/usr/X11R6/include -I. -o Build/objects/LargeFileMMap.o Basics/LargeFileMMap.cpp Basics/LargeFileFD.cpp: In member function 'virtual std::shared_ptrconst void LargeFileFD::rd(uint64_t, size_t)': Basics/LargeFileFD.cpp:79:58: error: 'POSIX_FADV_WILLNEED' was not declared in this scope Basics/LargeFileFD.cpp: In member function 'virtual void LargeFileFD::enqueue(uint64_t, size_t)': Basics/LargeFileFD.cpp:130:50: error: 'POSIX_FADV_WILLNEED' was not declared in this scope make[3]: *** [Build/objects/LargeFileFD.o] Error 1 make[3]: *** Waiting for unfinished jobs Full build log at https://buildd.debian.org/status/fetch.php?pkg=imagevis3darch=kfreebsd-amd64ver=3.0.0-1stamp=1351420838 Regards Christoph If you have further questions please mail debian-bsd@lists.debian.org -- -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87zk0vi8dp@mitoraj.siccegge.de
Bug#697015: Acknowledgement (imagevis3d: FTBFS[kfreebsd]: error: 'POSIX_FADV_WILLNEED' was not declared in this scope)
Thank you for filing a new Bug report with Debian. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. As you requested using X-Debbugs-CC, your message was also forwarded to debian-bsd@lists.debian.org (after having been given a Bug report number, if it did not have one). Your message has been sent to the package maintainer(s): Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org If you wish to submit further information on this problem, please send it to 697...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 697015: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697015 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.697015.b.13568326499@bugs.debian.org
Bug#697016: Acknowledgement (vobcopy: FTBFS[kfreebsd]: note: expected 'struct statfs **' but argument is of type 'struct statvfs **')
Thank you for filing a new Bug report with Debian. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. As you requested using X-Debbugs-CC, your message was also forwarded to debian-bsd@lists.debian.org (after having been given a Bug report number, if it did not have one). Your message has been sent to the package maintainer(s): Stephen Birch sgbi...@imsmail.org If you wish to submit further information on this problem, please send it to 697...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 697016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.697016.b.135690023027895@bugs.debian.org
Re: Bug#697003: initscripts: postinst fails: mv /dev/shm/* misses dot (hidden) files
On Sun, Dec 30, 2012 at 08:29:51PM +, Steven Chamberlain wrote: Control: severity -1 minor On 30/12/12 19:07, Roger Leigh wrote: Does /dev/shm exist on a standard kFreeBSD install? It gets created by initscripts as symlink to /run/shm. Otherwise it would not be there; apparently Linux 2.6 invented it and it didn't seem too popular with upstream FreeBSD. It's a glibc requirement. I didn't know this. Software running in the jails fortunately seems to be using /run/shm properly. It won't be; this isn't a Linux thing; it's just the directory used to create POSIX shared memory with the shm_open() function, which is typically a tmpfs mount so it's in-memory. glibc uses /dev/shm still, so you need a symlink /dev/shm-/run/shm or else it won't work at all. Within jails, I cannot write to /dev (even as root) so shm cannot be created as a directory or symlink. But as an alternative I can create it from the host system before booting, so that will do as a workaround and for compatibility. I think this is the best way to do it. Either as a symlink or a mount you share with the jail. + ls -A /run/shm + [ .tmpfs != ] This command indicates there is a file in this folder, called .tmpfs (though it isn't really a tmpfs), and so: Why does this file exist here? It's timestamped from when the jailed system booted, which would have been with initscripts 2.88dsf-32. It seems to be created by mount_shm in mount-functions.sh. Is it missing from the cleanup here in bootmisc? # Remove bootclean's flag files. # Don't run bootclean again after this! rm -f /tmp/.clean /lib/init/rw/.clean /run/.clean /run/lock/.clean rm -f /tmp/.tmpfs /lib/init/rw/.tmpfs /run/.tmpfs /run/lock/.tmpfs While here - could neaten this up a little: for dir in /lib/init/rw /tmp /run /run/lock /run/shm; do rm -f $dir/.clean $dir/.tmpfs done That's much better, thanks. On the other hand, if there'd been some non-hidden files/directories there, they would be moved, but any remaining hidden ones would be deleted(!). For the use case in question (in chroots) this is by design. There is no use case for dotfiles in /dev/shm. In that case, the ls -A flag is unnecessary? A plain ls would determine if anything in that directory needs keeping. And the error with mv would be avoided. I'll have to double check the shm_open API. You probably could abuse it with leading dots in the shared memory names. The main existing abusers were /dev/.udev and /dev/.mdadm, but these only apply to the host system, not to chroots. We should probably cater for it happening for robustness in any case. This is certainly safer. However, we should be catering for this already--we shouldn't be doing any modification of /dev if it's a mountpoint of any sort. I'm not sure exactly what you mean by modification, but at least for the mmdd|mddd cases it will try to move files to /dev/shm Yes. In this case we won't make/mount anything new but we will make use of the existing directories/mounts. And symlink /run/shm to /dev/shm since doing it the other way around is impossible without causing dataloss (chroots only, since we have no control over what was mounted, and we can't risk deleting anything shared with the host). Maybe it's not a realistic situation, but since there is no trailing slash, if /dev/shm didn't exist, a malicious user could have created in advance: 1. a symlink /run/shm/oops - /etc (which gets placed first as /dev/shm) 2. regular file /run/shm/passwd (which gets written over /etc/passwd) It's certainly possible if /dev/shm is missing, which we were assuming would never be the case. Updating the script to take this possibility into account will certainly be done. Currently we are making the assumption that it will be present, and I'm not sure if that's a bug or not. I'm not sure either. The above issue poses a security risk, so I'd consider adding a trailing slash (so that mv fails with an error instead); I guess it is unlikely though and so needn't be fixed with any urgency. This makes sense, and I'll change this, thanks. It'll have to be after new year now, though. Thanks, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121230212606.gw3...@codelibre.net
Bug#697032: Acknowledgement (rcpp: FTBFS[kfreebsd]: #error Rcpp::Timer not supported by your OS.)
Thank you for filing a new Bug report with Debian. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. As you requested using X-Debbugs-CC, your message was also forwarded to debian-bsd@lists.debian.org (after having been given a Bug report number, if it did not have one). Your message has been sent to the package maintainer(s): Dirk Eddelbuettel e...@debian.org If you wish to submit further information on this problem, please send it to 697...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 697032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.697032.b.135691305718903@bugs.debian.org
Bug#697032: rcpp: FTBFS[kfreebsd]: #error Rcpp::Timer not supported by your OS.
Package: src:rcpp Version: 0.10.2-1 Severity: serious User: debian-bsd@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-bsd@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: g++ -I/usr/share/R/include -DNDEBUG -I../inst/include/ -fpic -O2 -pipe -g -c Timer.cpp -o Timer.o Timer.cpp:35:6: error: #error Rcpp::Timer not supported by your OS. Timer.cpp:93:6: error: #error Rcpp::Benchmark::Timer not supported by your OS. make[1]: *** [Timer.o] Error 1 Full build log at https://buildd.debian.org/status/fetch.php?pkg=rcpparch=kfreebsd-amd64ver=0.10.2-1stamp=1356129312 Regards Christoph If you have further questions please mail debian-bsd@lists.debian.org -- -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87k3rzhyaq@mitoraj.siccegge.de
Re: Bug#697032: rcpp: FTBFS[kfreebsd]: #error Rcpp::Timer not supported by your OS.
On 30 December 2012 at 16:15, Christoph Egger wrote: | Package: src:rcpp | Version: 0.10.2-1 | Severity: serious | User: debian-bsd@lists.debian.org | Usertags: kfreebsd | X-Debbugs-Cc: debian-bsd@lists.debian.org | Justification: fails to build from source (but built successfully in the past) | | Hi! | | Your package failed to build on the kfreebsd-* buildds: Yup. Rainer Hurling, an active R user on *BSD, already told me about it and provided a patch for FreeBSD (as I happen to be upstream and Debian maintainer). How do I best get all BSDs at once? Currently we do #elif defined(linux) || defined(__linux) || defined(__FreeBSD__) in two place. If memory serves, there were a) similar handles for NetBSD and OpenBSD I should add. And which one do you guys need for the BSD kernel on Debian? Dirk | | g++ -I/usr/share/R/include -DNDEBUG -I../inst/include/ -fpic -O2 -pipe -g -c Timer.cpp -o Timer.o | Timer.cpp:35:6: error: #error Rcpp::Timer not supported by your OS. | Timer.cpp:93:6: error: #error Rcpp::Benchmark::Timer not supported by your OS. | make[1]: *** [Timer.o] Error 1 | | Full build log at | https://buildd.debian.org/status/fetch.php?pkg=rcpparch=kfreebsd-amd64ver=0.10.2-1stamp=1356129312 | | Regards | | Christoph | | If you have further questions please mail debian-bsd@lists.debian.org | | -- -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20704.56660.249233.434...@max.nulle.part
Re: Bug#697032: rcpp: FTBFS[kfreebsd]: #error Rcpp::Timer not supported by your OS.
Hi! Dirk Eddelbuettel e...@debian.org writes: On 30 December 2012 at 16:15, Christoph Egger wrote: | Package: src:rcpp | Version: 0.10.2-1 | Severity: serious | User: debian-bsd@lists.debian.org | Usertags: kfreebsd | X-Debbugs-Cc: debian-bsd@lists.debian.org | Justification: fails to build from source (but built successfully in the past) | | Hi! | | Your package failed to build on the kfreebsd-* buildds: Yup. Rainer Hurling, an active R user on *BSD, already told me about it and provided a patch for FreeBSD (as I happen to be upstream and Debian maintainer). How do I best get all BSDs at once? Currently we do #elif defined(linux) || defined(__linux) || defined(__FreeBSD__) in two place. If memory serves, there were a) similar handles for NetBSD and OpenBSD I should add. And which one do you guys need for the BSD kernel on Debian? Jep I'm seeing __NetBSD__ and __OpenBSD__ in lots of source. kFreeBSD uses __FreeBSD_kernel__ which -- if memory serves me correctly -- be also defined in newer FreeBSDs. Regards Christoph -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/878v8fhurd@mitoraj.siccegge.de
Re: Bug#697032: rcpp: FTBFS[kfreebsd]: #error Rcpp::Timer not supported by your OS.
Hi Christoph, On 30 December 2012 at 17:31, Christoph Egger wrote: | Hi! | | Dirk Eddelbuettel e...@debian.org writes: | On 30 December 2012 at 16:15, Christoph Egger wrote: | | Package: src:rcpp | | Version: 0.10.2-1 | | Severity: serious | | User: debian-bsd@lists.debian.org | | Usertags: kfreebsd | | X-Debbugs-Cc: debian-bsd@lists.debian.org | | Justification: fails to build from source (but built successfully in the past) | | | | Hi! | | | | Your package failed to build on the kfreebsd-* buildds: | | Yup. Rainer Hurling, an active R user on *BSD, already told me about it and | provided a patch for FreeBSD (as I happen to be upstream and Debian maintainer). | | How do I best get all BSDs at once? Currently we do | | #elif defined(linux) || defined(__linux) || defined(__FreeBSD__) | | in two place. If memory serves, there were a) similar handles for NetBSD and | OpenBSD I should add. And which one do you guys need for the BSD kernel on | Debian? | | Jep I'm seeing __NetBSD__ and __OpenBSD__ in lots of source. kFreeBSD Ok, will add these two but ... | uses __FreeBSD_kernel__ which -- if memory serves me correctly -- be | also defined in newer FreeBSDs. ... you are telling me I also need this? Can't you guys just settle for __WhateverBSD__ and leave the rest of us alone? ;-) Cheers, Dirk -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20704.62255.105601.290...@max.nulle.part
Re: Workaround for kFreeBSD crash in reportbug
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 seeing yet another bug in kfreebsd's pthread implementation. My diagnosis that this is a pygtk bug rather than a kfreebsd bug basically boils down to the fact that on linux, helgrind is giving a diagnostic at the very place that kfreebsd is crashing. Basically, after gdk_enable_threads(), any gtk call must be made with the global lock held (gdk_threads_enter()). In the case of gtk_main(), it very soon calls gtk_threads_leave(), which is the spot where a not-locked pthread mutex is unlocked. That being the case, I suspect that the pygtk faq item is just omitting the gtk.gdk.threads_enter() call before gtk_main for the sake of brevity (but maybe because the error passes silently on Linux). But whether that is the case or not, pygtk really can't impose the additional requirement on users of raw_input() that they have to manipulate a gdk lock before the call; whatever it's doing had better be transparent to users of raw_input. However, on reading the glibc and posix manpages on pthread_mutex_unlock, it should simply return nonzero and set errno to EPERM in the case of unlocking a not-locked mutex, so it is probably equally sensible to pursue this as a bug in the pthreads implementation in debian kfreebsd's userspace... Unfortunately, I've failed to distill what I think gtk is doing into a simple program that segfaults on kfreebsd. Jeff -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121231022130.ga7...@unpythonic.net
Re: Bug#697032: rcpp: FTBFS[kfreebsd]: #error Rcpp::Timer not supported by your OS.
Hi Dirk, On 31/12/12 02:06, Dirk Eddelbuettel wrote: | #elif defined(linux) || defined(__linux) || defined(__FreeBSD__) Sometimes you are really testing for the type of libc on the system, not the kernel. For that, __GLIBC__ is supposed to be defined on all GNU/k*BSD variants. There is a bit more info at: http://glibc-bsd.alioth.debian.org/porting/PORTING | | in two place. If memory serves, there were a) similar handles for NetBSD and | OpenBSD I should add. And which one do you guys need for the BSD kernel on | Debian? | | Jep I'm seeing __NetBSD__ and __OpenBSD__ in lots of source. Plenty of examples of that here: http://codesearch.debian.net/search?q=defined.*BSD.*BSD.*BSD or http://codesearch.debian.net/search?q=defined.*BSD__ Generally you have to list all of them :( But it is probably more portable in the long term to test for specific features that you want to use, wherever it makes sense. | uses __FreeBSD_kernel__ which -- if memory serves me correctly -- be | also defined in newer FreeBSDs. ... you are telling me I also need this? If you are really testing for kernels, I think it is preferred that you test for __FreeBSD_kernel__, instead of just __FreeBSD__ which is a bit ambigious, and only defined on a pure FreeBSD (with BSD libc) system. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50e0f966.7050...@pyro.eu.org
Bug#697042: syslog-ng: should use ttyva not tty10 as virtual console on kfreebsd
Package: syslog-ng
Version: 3.3.5-2
Severity: normal
Hi!
On kfreebsd I'm seeing lots of
Dec 30 07:09:55 hel syslog-ng[18791]: Error opening file for writing;
filename='/dev/tty10', error='Operation not supported (45)'
Dec 30 07:09:55 hel syslog-ng[18791]: Error opening file for writing;
filename='/dev/tty10', error='Operation not supported (45)'
Dec 30 07:09:55 hel syslog-ng[18791]: Error opening file for writing;
filename='/dev/tty10', error='Operation not supported (45)'
in my syslog. this is because syslog-ng.con mentions
# Virtual console.
#
destination d_console_all { file(/dev/tty10); }
while on kfreebsd you probably want ttyva not tty10
Regards
Christoph
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: kfreebsd-amd64 (x86_64)
Kernel: kFreeBSD 9.0-2-amd64
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages syslog-ng depends on:
ii syslog-ng-core 3.3.5-2
ii syslog-ng-mod-json 3.3.5-2
ii syslog-ng-mod-mongodb 3.3.5-2
ii syslog-ng-mod-sql 3.3.5-2
syslog-ng recommends no packages.
syslog-ng suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/20121231034210.92720.78132.report...@hel.hosts.sieglitzhof.net
