me wasted. Sorry,
I couldn't help including my $0.02 wrt linux..
Chris Csanady
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Now
all is well--so I can only assume it is some weird interaction between the
linux_base port and my system. Maybe it is related to using XFree86 3.9.15,
but I don't have the time to test that theory right now.
Certainly not a great solution, but if things are broke for you this at least
wor
Garrett Wollman wrote:
>
> < said:
>
> > Yes, it is a SMP box, and yes, the devices work fine. I just thought it was odd
> > that the kernel would report incorrect ones.
>
> They are not incorrect. SMP uses a different interrupt system.
They are on my box, where incorrect is defined as the in
I have been trying to get ssh working in current, but with no luck.
Since I updated recently, all I get is:
ssh: no RSA support in libssl and libcrypto. See ssl(8).
I have been off the lists for a bit, so I apologize if I missed
something, but this has always been confusing. It used to just
wo
>
>
>On Thu, 29 Jun 2000 02:25:50 CDT, Chris Csanady wrote:
>
>> I have been trying to get ssh working in current, but with no luck.
>> Since I updated recently, all I get is:
>>
>> ssh: no RSA support in libssl and libcrypto. See ssl(8).
>
>Thi
>I noticed that NetBSD is switching over to using /etc/nsswitch.conf (like
>Slowlaris, PH-UX, etc.). Would it be a good idea to do this for FreeBSD too
>(when I first started using FreeBSD, it took me a long time to figure out the
>analogous file for hostname lookups was /etc/host.conf) -- it seem
t
s
r
q
Chris Csanady
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
>On Wed, Feb 03, 1999 at 09:53:05PM -0600, Chris Csanady wrote:
>>I unfortunately have a lot of data to type in, and to my surprise
>>the keypad is unuseable in vi. It doesn't even work in vim. Thank
>>god it works on Irix--I thought I would be using ee.
>>
>
packet headers
>1674/1688/2048 mbuf clusters in use (current/peak/max)
>3480 Kbytes allocated to network (97% in use)
>0 requests for memory denied
>0 requests for memory delayed
>0 calls to protocol drain routines
>
>
>Chris Csanady
>
>
>
>
>To Unsubscribe:
>On Thu, 11 Feb 1999 09:15:29 -0800
> "Justin C. Walker" wrote:
>
> > I can say that our implementation doesn't seem to =
> > suffer from this problem. Could be there's an issue in the use of =
> > PRUS_* v. the socket state we use. The code in my kernel looks like:
>
>The NetBSD code looks p
>As of a few minutes ago, a minimal set of changes to bring the so-called
>'new-bus' functionality to the i386 kernel in -current.
This seems to have broken disk wiring for me. Is there some necessary
change in syntax that I am not aware of?
I have the following scsi related stuff in my config
>Chris Piazza wrote:
>> On 17-Apr-99 Brian Feldman wrote:
>> > Both sound drivers are broken with the new-bus code. My SB16, in the old
>> > driver, now gets recognized but sbxvi is never looked for. pcm0, the new
>> > driver, never initializes with the new code :(
>> >
>> > device pcm0 at isa? p
>> Hmm, you might like to try this patch and see what happens, there is
>> a missing old driver wrapper for the pcm stuff. As a result, it's not
>> getting run from the isa probe. Regarding the other driver, I'm not
>> sure what's going on there as the hooks appear to be present.
>
>Right on, th
>> >mp3s aren't playing quite right with x11amp though, little
>> >skips here and there, they work fine with the old kernel.
>> >mpg123 seems fine, as does the sound in FXTV.
>> >I'll try making the world again.
>>
>> Was there ever any resolution/further inspection of this?
>
>Not as far I know;
>>
>> my stock SB16 + freebsd+x11amp hasn't worked right since newbus.
>>
>> sound skips quite a bit.
>>
>>
>>
>
>I noticed the same thing. /usr/ports/audio/gqmpeg is a nice player
>which uses mpg123 as the backend; it plays fine. I think it may have
>just have something to do with x11amp,
15 matches
Mail list logo
