Re: Qmail install success on 1.4; possible package bug?
On Sun, Jan 08, 2006 at 09:12:38PM -0700, Tim Darby wrote: Anyway, I think I've either found a package bug or it's just me being clueless, probably the latter. As part of the Qmail install, I installed the package daemontools-0.76. After I setup the service folders and rebooted, I got boot errors from svscan telling me that it couldn't start the 'supervise' processes. After some poking around, I think the problem is that the supervise program is installed by the package in /usr/pkg/bin, however that folder is not in the path of the shell command that the included /usr/local/etc/rc.d/svscan.sh script runs. When I copied supervise to /usr/sbin and rebooted, it worked fine. Here's the only command that the svscan.sh script runs: Please fill a NetBSD/pkgsrc PR against either daemontools or qmail, whatever is more appropiate. RC scripts and related things MUST NOT depend on PATH. Joerg
Debugging device drivers
Hi all, i'm trying to understand why my SB16 soundcard isn't recognized by DragonFly, though working alright under FBSD 5.4: i already had a long-standing problem with ips(4) and as i've got no other controller to boot from, i had to go through a painful cycle (put printf everywhere, rebuild on another host, scp install the new kernel, reboot, try to understand anything at all...). As a sound card isn't that critical to the boot process, i'd like to know if an easier way of debugging exists: would it be possible to build a kernel without any sound support, instrument and somewhat hack bits of snd_sbc and friends and then use kldload/kldunload to investigate ? I mean: will the probe routines get called as they would during normal kernel initialization ? Thanks for any tips, Francis. PS: though the device names changed a little bit in kernel config files between FBSD and DFly, i'm still using the same parameters in both case (same irq, port, etc.)
Re: Debugging device drivers
On 2006-01-11, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: First of all, get a console to play sound like mad123 or so. Second, do you have your device settings (IRQ, DMA, ...)? You need to add two entries your kernel config: device pcm device snd_sbc0 at isa? ... where ... are the configuration parameters. You can change them via the kernel config (boot -c). Joerg OK, i'm trying this way at the moment. As a side note, what confused me is the following: - pcm(4), aka snd(4) states: For a card with bridge driver support, and a PnP card: device pcm For a card without bridge driver support, and a non-PnP card: device pcm0 at isa? port? irq 5 drq 1 flags 0x15 - sbc(4) on the other hand: For PnP cards: device sbc For non-PnP cards: device sbc0 at isa? port 0x220 irq 5 drq 1 flags 0x15 - and the last comes straight from LINT: # Basic PCM support, needed for all sound card: device pcm # For PnP/PCI sound cards: device snd # For non-pnp sound cards: device snd0 at isa? irq 10 drq 1 flags 0x0 Is there something seriously outdated on my system, or does the tree need a bit of a clean-up ? Francis.
Subversion for DF sources
A week or so ago, a discussion rattled around about cvsup being written in c++. What about launching into it, and moving to subversion instead? That way, the updater could be included in the base system, as it's c++ AND BSD licenced. Probably great scads or work, but it might be a good idea. N. Nigel Weeks Tech Support Systems Developer [EMAIL PROTECTED] www.examiner.com.au 71 - 75 Paterson Street Launceston Tasmania 7250 Australia Phone: 03 6336 7234
