Hi,
Currently in pkgsrc DEVOSSAUDIO is /dev/audio and DEVOSSSOUND
is /dev/dsp for DragonFly. Recently I tried a libao based package and got
errors because it followed these and tried to open $DEVOSSAUDIO which
produced a Device not configured error. I hacked the oss.buildlink3.mk
Steve O'Hara-Smith wrote:
This led me to wonder if /dev/audio should have worked with the
current sound setup in DragonFly and what setting should be in
oss.buildlink3.mk.
not sure if/what/when this should be/was changed/ ... - but
depending on the outcome, could this be overridden
On Fri, 14 Mar 2008 09:31:40 -0400
Chris Turner [EMAIL PROTECTED] wrote:
Steve O'Hara-Smith wrote:
This led me to wonder if /dev/audio should have worked with the
current sound setup in DragonFly and what setting should be in
oss.buildlink3.mk.
not sure if/what/when this
On Fri, 14 Mar 2008, Steve O'Hara-Smith wrote:
Currently in pkgsrc DEVOSSAUDIO is /dev/audio and DEVOSSSOUND
is /dev/dsp for DragonFly. Recently I tried a libao based package and got
errors because it followed these and tried to open $DEVOSSAUDIO which
produced a Device not configured
On Fri, 14 Mar 2008 09:15:26 -0500 (CDT)
Jeremy C. Reed [EMAIL PROTECTED] wrote:
I don't have answer for this. Just mentioning that I put those DragonFly
settings in mk/oss.buildlink3.mk per PR #35824
http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=35824
It occurs to me that
On Friday 14 March 2008 Matthias Schmidt wrote:
It is a clean rewrite (in some parts) of the ISC dhclient and contains
nice features like privilege separation. IIRC Hasso also discovered an
issue with our dhclient, but I can't remember what is was :)
It's part of bigger set of issues called
:Mar 13 08:07:13 pos dntpd[627]: Unable to resolve server 0.pool.ntp.org:
:Connection refused
:Mar 13 08:07:13 pos dntpd[627]: Unable to resolve server 1.pool.ntp.org:
:Connection refused
:Mar 13 08:07:13 pos dntpd[627]: Unable to resolve server 2.pool.ntp.org:
:Connection refused
:Mar 13
Hasso Tepper wrote:
It's part of bigger set of issues called DragonFly without net
connection.
yeah..
This is problematic with RCNG - I tried putting a parameter in rc.conf
for something or the other to try and make this modular,
e.g. [ $net_is_enabled ] foo_enable=yes type of things..
