Re: panic: vm_fault_copy_wired
On 14/05/12 17:08, Steven Chamberlain wrote: Hi, This problem came back after an unclean, forced reset of a crashed VM. This time I managed to log startup messages via serial console. After this problem occurred, it would persist between resets. I had to boot d-i, drop to a shell, run fsck.ufs -y on the root partition (this just marked it clean; no modifications were needed), and after that it would boot normally again. I have no swaps configured in /etc/fstab. I've set VERBOSE=yes in /etc/default/rcS for next time... Truly unbelieavable ! I was exactly on this very same instant dealing with exactly *this very issue*! Thanks a lt! You saved me hours! Cheers, D -- BOFH excuse #358: struck by the Good Times virus signature.asc Description: OpenPGP digital signature
Bug#662140: [zfsutils] Broken cron.d task
Package: zfsutils Version: 9.0-1 Severity: normal Tags: patch I got this morning a failure report on some kfreebsd boxes: From: root@somebox (Cron Daemon) To: root@somebox Subject: Cron root@somebox if [ $(date +%d) -le 7 ]; then zpool list -H -o name | xargs zpool scrub; fi Content-Type: text/plain; charset=UTF-8 X-Cron-Env: SHELL=/bin/sh X-Cron-Env: HOME=/root X-Cron-Env: PATH=/usr/bin:/bin X-Cron-Env: LOGNAME=root Message-Id: someid Date: Sun, 4 Mar 2012 00:57:01 -0300 (ART) /bin/sh: 1: zpool: not found xargs: zpool: No such file or directory Tracking it down, the reason behind it is because either full path to zpool wasn't specified or because PATH doesn't include :/sbin on the array, as you can see on the ENV report. Please either provide a fullpath to the script or export /sbin on PATH environment value for this cron task. Cheers, Dererk -- BOFH excuse #373: Suspicious pointer corrupted virtual machine BOFH excuse #307: emissions from GSM-phones signature.asc Description: OpenPGP digital signature
Bug#658677: [kfreebsd-image-9] Please enable pflog device by default
On 10/02/12 16:57, Robert Millan wrote: 2012/2/6, Dererk der...@debian.org: That was easy! :-) As you mention, removing the patch did work as expected and nicely! Thanks! I'll let tcpdump guys know about this so we can, altogether when this issue is solved, this quite relevant kbsd feature working in time for wheezy. So what else is needed? Is a kernel config option missing? Hi Robert Millan! Yes, it's just missing the activation of the pflog device option on the network options list block. In what respects to whether it works or not, I've been running an amd64 node for longer than 10 days now, with just this little change performed over the stock kernel pkg and it appears to be pretty stable, no errors have appeared so far and the functionality is working greatly. It totally appears to be safe to enable it by default. Cheers, Dererk -- BOFH excuse #125: we just switched to Sprint. -- 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/4f358051.6050...@debian.org.ar
Bug#658677: [kfreebsd-image-9] Please enable pflog device by default
On 10/02/12 16:57, Robert Millan wrote: 2012/2/6, Dererk der...@debian.org: That was easy! :-) As you mention, removing the patch did work as expected and nicely! Thanks! I'll let tcpdump guys know about this so we can, altogether when this issue is solved, this quite relevant kbsd feature working in time for wheezy. So what else is needed? Is a kernel config option missing? Hi Robert Millan! Yes, it's just missing the activation of the pflog device option on the network options list block. In what respects to whether it works or not, I've been running an amd64 node for longer than 10 days now, with just this little change performed over the stock kernel pkg and it appears to be pretty stable, no errors have appeared so far and the functionality is working greatly. It totally appears to be safe to enable it by default. Cheers, Dererk -- BOFH excuse #307: emissions from GSM-phones signature.asc Description: OpenPGP digital signature
Bug#658677: [kfreebsd-image-9] Please enable pflog device by default
On 06/02/12 05:04, Petr Salinger wrote: Petr, since you're listed as patch author, do you know if this feature worked in the past? tcpdump worked somehow, but I do not remember exactly, it is 4 years ago, see #448695. Probably, the net/pfvar.h used to need net/if_pflog.h. It is not needed any longer. It looks like the proper fix is just to discard 50_kfreebsd.diff (after quilt pop -a -f) from series. Dererk, please could you test such tcpdump with your custom kernel ? Cheers Petr Hi Petr! That was easy! :-) As you mention, removing the patch did work as expected and nicely! Thanks! I'll let tcpdump guys know about this so we can, altogether when this issue is solved, this quite relevant kbsd feature working in time for wheezy. Thanks a _lot_! Cheers, Dererk -- BOFH excuse #403: Sysadmin didn't hear pager go off due to loud music from bar-room speakers. signature.asc Description: OpenPGP digital signature
Re: [kfreebsd-image-9] Please enable pflog device by default
owner 658677 debian-bsd@lists.debian.org thanks On 05/02/12 02:23, Dererk wrote: As a side note, current archive's tcpdump version is unable to recognize the pseudo interface type[1][2], but using openbsd's provided tcpdump does read kbsd's captured dumps. If this patch is accepted, I'll try to see how possible it is for debian's tcpdump to adopt pflog pseudodevice-handling patch. Hi once again! FTR, further inspection shows that, in fact, there appears to be a patch to address PFLOG pseudodevice present on tcpdump debian's pkg, but for some reason its falling back on /missing/. Judging from this[1][2], it leads me think that it's simple not being applied configured/applied on building time. Petr, since you're listed as patch author, do you know if this feature worked in the past? Cheers, Dererk 1. https://buildd.debian.org/status/fetch.php?pkg=tcpdumparch=kfreebsd-amd64ver=4.2.1-1stamp=1325535367 2. https://buildd.debian.org/status/fetch.php?pkg=tcpdumparch=kfreebsd-i386ver=4.2.1-1stamp=1325535434 -- BOFH excuse #403: Sysadmin didn't hear pager go off due to loud music from bar-room speakers. signature.asc Description: OpenPGP digital signature
Re: Please test zfsutils 9.0~svn226163-1
Hello Arno! I can confirm that the changes do work nicely (with the same symbol lookup errors you described). In case it helps, I've notice an increase in the cpu usage when upgrading to 28 zfs pool version. Although it's not higher than 5-10% (running on a 4-cored amd64), It's noticeable on monitoring. I do suspect this to be a direct cause of deduplication, since the upgraded zpool handle thousand of files. Thanks! :-) Cheers, Dererk -- BOFH excuse #331: those damn raccoons! signature.asc Description: OpenPGP digital signature
Re: Bug#615152: grub2: Cannot recognize FS format any more under kfreebsd ports
On 25/03/11 20:10, Vladimir 'φ-coder/phcoder' Serbinenko wrote: The problem comes from DIOCGDINFO which apparently is broken on FreeBSD (and this is just one way it misbehaves). So I rewrote it with geom. Patch attached. Was tested on IRC and it fixed the problem. Needs to be tested on GPT. Hi. Indeed, I've patched grub version 1.99~rc1-5 and tested on kfreebsd-amd64 (running 8.2 too). Pkg information: This patch introduces a build-dep on geom headers (libgeom-dev) Worked nicely for my using geom version 8.1-5. Thanks a lot Vladimir for your time and patience! Cheers, Dererk -- BOFH excuse #149: Dew on the telephone lines. signature.asc Description: OpenPGP digital signature
Re: grub2: Cannot recognize FS format any more under kfreebsd ports
Hi. For the sake of anyone out there looking for a clue, I'm dropping some lines about how I got my system to boot from grub issues, running a kFreeBSD port. I have to first boot my system in some way to downgrade grub2 package, 1.98+20100804-14 was good enough. Few ways for getting the defective system to boot: 1. Boot using an already running freebsd system, overriding grub boot loader with freebsd's native boot loader. Works, but takes some time. 2. Use another grub installation and override your boot sector. Works, but takes some time. 3. Get an already working grub from another installation (can be any OS with grub running, not only kbsd), and use the regular grub console (not rescue mode) to boot your system through it. Have to know partitioning schema and stuff, little painful loading them in but backup-ready. Once you get on running, downgrade grub2, grub-pc and grub-common to whatever version worked for you before, as I already mention, 1.98+20100804-14 works. Then, use tell dpkg to hold them for any future upgrade you might perform (echo «pkgname» hold | dpkg --set-selections). That should put you right on the road again. Cheers, Dererk -- BOFH excuse #127: Sticky bits on disk. signature.asc Description: OpenPGP digital signature
Re: firewall?
On 04/02/11 11:19, Anton Andreev wrote: Hi, How to configure a firewall on Debian / kFreeBSD. Cheers, Anton FreeBSD, consequently Debian kFreeBSD, replaced their old packet filter (luckily) with a ported OpenBSD's PF, most flexible and powerful packet filter you'll find out there, IMO. One of the most relevant and complete guides you could find about: http://www.openbsd.org.ar/faq/pf/index.html Enjoy! Greetings, Dererk -- BOFH excuse #422: Someone else stole your IP address, call the Internet detectives! signature.asc Description: OpenPGP digital signature
Re: request for test build on kFreeBSD machine
On 10/12/10 16:36, Hans-Christoph Steiner wrote: I'm trying to fix bugs 605821-605830 in my packages, and since I am not a DD or DM, I don't have access to the Debian build machines. Could someone please try a test build to see if I have indeed fixed the problem? Then I'll request an upload. (I'm not on this list, so please keep me cc'ed). The easiest way is using git-buildpackage: apt-get install git-buildpackage puredata debhelper quilt git clone \ https://alioth.debian.org/anonscm/git/pkg-multimedia/pd-pmpd.git cd pd-pmpd git-buildpackage Thanks! .hc Built successfully (Log attached). Cheers, Dererk -- BOFH excuse #222: I'm not sure. Try calling the Internet's head office -- it's in the book. pd-pmpd.buildd.log.gz Description: application/gzip signature.asc Description: OpenPGP digital signature
Bug#583848: Please enable pfdev to be loaded by default
Source: kfreebsd-8 Version: 8.0-5 Severity: normal User: debian-bsd@lists.debian.org Usertags: kfreebsd Hi! Please enable pf device to be loaded by default, just as kfreebsd-7 did. # pfctl -f /etc/pf.conf pfctl: /dev/pf: No such file or directory. # kldload pf pfctl -f /etc/pf.conf ; echo $? 0 Greetings, Dererk -- BOFH excuse #408: Computers under water due to SYN flooding. signature.asc Description: OpenPGP digital signature
Re: rm -rf doesn't work as expected?
On 08/05/10 20:55, The Anarcat wrote: Anybody else is having this issue? I'm on a recent squeeze with FreeBSD 7.2 and coreutils 8.4-2. A. Right, it's a known issue on 7.2 kernel compilation http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573940. As suggested there, switching to a 8-branch kernel is a possible solution. Greetings, Dererk -- BOFH excuse #449: greenpeace free'd the mallocs signature.asc Description: OpenPGP digital signature
[bind9] Please apply patch for kfreebsd port to work
Package: bind9 Version: 1:9.7.0.dfsg.P1-1 Severity: normal Tags: patch Usertags: kfreebsd Hello! Please find attached the patch for Bind9 to work under kFreeBSD port. It just disables linux capacities and threads, both conceived under Linux. It has been already tested under kFreeBSD-i386. Please apply it as soon as possible Greetings, Dererk -- BOFH excuse #110: The rolling stones concert down the road caused a brown out bind9-kfreebsd.patch.gz Description: Binary data signature.asc Description: Digital signature
Problems upgrading sysv-rc
Hello there! I've some issues while upgrading sysv-rc, and before filing a bug against it, I wanted to know If it's a known problem/there's something to worry about. What do you think? (sorry about the formating, I was running debconf on Dialog while I got the message :-S ) Configuring sysv-rc Unable to migrate to dependency based boot system Tests have determined that problems in the boot system exist which prevent migration to dependency based boot sequencing. It is recommended to migrate for the following reasons x * the order of boot and shutdown is calculated dynamically, using x xdependency information declared within each init.d script, which x xensures optimum and correct boot sequence for the set of installed x xpackages x x * protection against problems introduced by new or upgraded packages x xby preserving the boot sequence when problems are detected; the boot x xsequence is only modified if it is safe to do so x If the reported problem is a local modification it needs to be fixed manually. x If it's a bug in the package it should be reported to the BTS and fixed in the package. See x http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for more information about how to x fix the problems preventing migration. To reattempt the migration process after the problems have been x fixed, run 'dpkg-reconfigure sysv-rc'. x The following problems were detected: package util-linux left obsolete init.d script behind, package util-linux left obsolete init.d script behind x error: Unable to migrate to dependency based boot sequencing. error: Problems detected: package util-linux left obsolete init.d script behind, package util-linux left obsolete init.d script behind grep: /var/lib/update-rc.d/*: No such file or directory Thanks in advance! Greetings, Dererk -- BOFH excuse #267: The UPS is on strike. signature.asc Description: OpenPGP digital signature
Re: Missing /sys after installation
Aurelien Jarno escribió: On Sun, Jun 14, 2009 at 01:59:07AM +0200, Cyril Brulebois wrote: Hi folks, I've just installed kfreebsd-i386 with qemu (on amd64), and noticed the following bug after installation: freebsd-utils's init script mounts /proc, /sys, etc., but /sys is missing at this point. I guess this problem would be best solved within the installer, but in the meanwhile, I guess that freebsd-utils's postinst could make sure this directory exists before starting freebsd-utils? I have fixed freebsd-utils in the SVN to create this directory if it doesn't exists. On GNU/Linux, this directory is provided by initscripts. I think we should do the same on GNU/kFreeBSD. I'll file a bug report about that. Hi there! I noticed that some time ago and already reported but got no feedback #525787. Greetings, Dererk -- vlady at Melee: ~$ grep -ir 'power in your hands' /proc/ /proc/version: Debian GNUine Perception BOFH excuse #356: the daemons! the daemons! the terrible daemons!. signature.asc Description: OpenPGP digital signature
Re: kFreeBSD question
Haidut escribió: Hi, I have a question about kFeeBSD. As the website says, the latest version of kFreeBSD is based on the FreeBSD 6.x kernel. My first question is - once I install kFreeBSD would it possible for me to download the sources for a more recent FreeBSD kernel (i.e. the 7.0 branch) and compile it, so that I can have my custom kFreeBSD based on FreeBSD 7.0? Second question - I was trying to find a binary package for MySQL server in the apt-get repositories provided on the website but couldn't find one. I was able to find PostgreSQL server versions 7.4 and 8.0 but there was nothing for MySQL DB server. Is there currently a binary MySQL server package for kFreeBSD? You help is greatly appreciated. Thanks. About the second point: DbCluster13:~# uname -a GNU/kFreeBSD DbCluster13 6.2-1-486 #0 Thu May 3 16:18:55 CEST 2007 i686 i386 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ GNU/kFreeBSD DbCluster13:~# /etc/init.d/mysql status /usr/bin/mysqladmin Ver 8.41 Distrib 5.0.45, for pc-kfreebsd-gnu on i486 DbCluster13:~# apt-cache policy mysql-server-5.0 mysql-server-5.0: Installed: 5.0.45-1 Candidate: 5.0.45-1 Version table: *** 5.0.45-1 0 500 http://ftp.gnuab.org unstable/main Packages 100 /var/lib/dpkg/status It is :) I come across a locale issue when using initscripts, but used POSIX one, and fired it up :-) Good luck! -- [EMAIL PROTECTED]: ~$ grep -ir 'power in your hands' /proc/ /proc/version: Debian GNUine Perception BOFH excuse #295: The Token fell out of the ring. Call us when you find it.. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
