Re: Re: Hardware support for AMD Geode CS5536 audio?
To All, I finally have a working CS5536 audio driver for FreeBSD 6.2. The filename is snd_amd5536.ko and I will be making it available shortly. I have been using an ALIX-1C motherboard for my testing. Anyone have other hardware that they want to test it on? Another question. How does one get the FreeBSD people to put this driver into their OS? Andrew Gray ancelgray "A T" y a h o o "D O T" c o m -- This message was sent on behalf of [EMAIL PROTECTED] at openSubscriber.com http://www.opensubscriber.com/message/freebsd-hackers@freebsd.org/9623264.html ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Re: Hardware support for AMD Geode CS5536 audio?
To All, I finally have a working CS5536 audio driver for FreeBSD 6.2. The filename is snd_amd5536.ko and I will be making it available shortly. I have been using an ALIX-1C motherboard for my testing. Anyone have other hardware that they want to test it on? Another question. How does one get the FreeBSD people to put this driver into their OS? Andrew Gray ancelgray "A T" y a h o o "D O T" c o m -- This message was sent on behalf of [EMAIL PROTECTED] at openSubscriber.com http://www.opensubscriber.com/message/freebsd-hackers@freebsd.org/9623264.html ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SSH Brute Force attempts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rich Healey wrote: > Recently I'm getting a lot of brute force attempts on my server, in the > past I've used various tips and tricks with linux boxes but many of them > were fairly linux specific. > > What do you BSD guys use for this purpose? > > If this belongs on -security let me know and I'll ask over there. > > Cheers > > > Rich ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]" Personally I find that changing the port to anything other than 22 stops a lot of the skiddie brute force attacks. Thats not to say you shouldn't use something else as well - but it is something. P.S. Can someone please let me know if the mailing list got this message - some of my messages have not been getting replies for some reason. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkjkNo4ACgkQtl8kq+nCzNGUKQCeN/bmzWuYr+Xc8i/iXufayd3l LWYAnRcdVWTQe4t/EXDxBYpC+QlEO1CD =4rKm -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Sched_ule.c - 8.0
Hello All, I was browsing the ULE 8.0 scheduler code and happen to find something interesting. This might be intentional; since I don't think it is that big a deal and is certainly not a bug. In the implementation of sched_affinity - which from what I understand gets called when the cpuset mask for a thread or a process is setup and threads need to potentially migrated. The code is pretty straightforward and one of the checks it does is if (!TD_IS_RUNNING(td)) return; I initially read this to mean, if the thread isn't running, it's probably inhibited and that's okay because when it wanders into sched_add eventually and since its cpuset mask is setup, it'll make its way to the runq of one of the "legal" cpus. However the very next thought I had was this thread could be on a runq right now and the macro will return the fact that the thread isn't running. In such a case we would probably end up running on the wrong CPU for a while before realizing that we aren't allowed to do so. Thanks Ravi ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Major SMP problems with lstat/namei
On Thursday 25 September 2008 07:00:04 pm Jeff Wheelhouse wrote: > > On Sep 24, 2008, at 12:12 PM, John Baldwin wrote: > > Shared lookups only work on the NFS client in 6.x. I'm about to > > turn them on > > for UFS in HEAD (8.x) and will backport the needed fixes to 7.x > > after 7.1 > > (too risky to merge to 7.x this close to a release). > > OK, given all the patches you referenced, I did make a decent effort > at backporting to 7.0. It sounds like you missed some of the dirhash changes somehow, as dirhash no longer has any lockmgr stuff in it (and only ever did in HEAD). I've generated a patch though using svn. You can grab it from http://www.FreeBSD.org/~jhb/patches/ufs_lookup7.patch Note that you will have to set vfs.lookup_shared=1 to enable shared locks (either loader tunable or sysctl). Also, I found a few other changes I had missed earlier that needed to be included. -- John Baldwin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: svn rev. number
> small catch, i'm using svk, but i guess I'll look into current's newvers.sh. > and running -stable. > >> If that's the case, newvers.sh will add the output of it to uname: >> >> "FreeBSD fbsd8 8.0-CURRENT FreeBSD 8.0-CURRENT #4 r180876:183019M:..." How about $FreeBSD$ svn tag. Some binaries include rcsids in them. Shell scripts and config files in /etc will be with empt revision string?! You should really use subversion-freebsd. -- regards, Artis Caune <. CCNA <| <' didii FreeBSD ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FW: i386/127710: My driver PCI probe is not called for my correspondingdevice ID and Vendor ID
On Wednesday 01 October 2008 08:50:15 am Bagavathy Kumar Mahendran wrote: > > Dear All, > Iam writing a new driver for a SAS/SATA Controller having a > Class ID -0x01 > Sub Class - 0x07 > Programming Interface - 0x00 > > Hence instead of my probe function the Static build Card Bus Driver cbb > is attaching just by simply checking sub class 0x07 and programming > interface 0x00.hence my probe gets failed. Kindly help me in resolving > this .what I thought is to add the card bus driver a checking of CLASS > ID in its pci probe function. The pccbb driver returns BUS_PROBE_DEFAULT (it should probably return GENERIC in the case where it matches only on class codes). Your driver just needs to return a numerically higher value (but still < 0) to claim the device. You can probably use BUS_PROBE_VENDOR or BUS_PROBE_DEFAULT + 1. -- John Baldwin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: i386/127710: My driver PCI probe is not called for my correspondingdevice ID and Vendor ID
My PCI Express card has Class ID is 0x1 Sub Class ID is 0x7 Programming Interface is 0x0 How a card bus driver can attach my PCI Express Card. The Card Bus driver gets attached with out checking the Class ID. How he can take Sub Class ID & Programming Interface alone for Attaching it. Thanks for your replay. regards, Bagavathy kumar.M -Original Message- From: Remko Lodder [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 01, 2008 5:48 PM To: Bagavathy Kumar Mahendran Cc: [EMAIL PROTECTED] Subject: Re: i386/127710: My driver PCI probe is not called for my correspondingdevice ID and Vendor ID Bagavathy kumar . M wrote: Please submit this question to the [EMAIL PROTECTED] mailinglist. This is not a PR (yet), you might have done something wrong to your code or are missing logic(s) which are needed in that case. I will close the ticket because of that. Thanks for taking the time to report this and for using FreeBSD, it's appreciated! -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. --- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FW: i386/127710: My driver PCI probe is not called for my correspondingdevice ID and Vendor ID
Dear All, Iam writing a new driver for a SAS/SATA Controller having a Class ID -0x01 Sub Class - 0x07 Programming Interface - 0x00 Hence instead of my probe function the Static build Card Bus Driver cbb is attaching just by simply checking sub class 0x07 and programming interface 0x00.hence my probe gets failed. Kindly help me in resolving this .what I thought is to add the card bus driver a checking of CLASS ID in its pci probe function. Thanks With Regards, Bagavathy kumar .M -Original Message- From: Remko Lodder [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 01, 2008 5:48 PM To: Bagavathy Kumar Mahendran Cc: [EMAIL PROTECTED] Subject: Re: i386/127710: My driver PCI probe is not called for my correspondingdevice ID and Vendor ID Bagavathy kumar . M wrote: Please submit this question to the [EMAIL PROTECTED] mailinglist. This is not a PR (yet), you might have done something wrong to your code or are missing logic(s) which are needed in that case. I will close the ticket because of that. Thanks for taking the time to report this and for using FreeBSD, it's appreciated! -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. --- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: svn rev. number
> On Wednesday 01 October 2008 14:04:20 Danny Braniss wrote: > > Hi, > > Now that freebsd is under svn, I decided to try what I failed > > with cvs, and actually using svn/svk/svnsync I have a mirror and a local > > branch in sync! > > Since the date reported by uname is not that relevant, is it possible to > > add the svn-revision # ala build-...? This could make finding problems > > easier, instead of kernel from 'date' one could say date/revision... just a > > thought. > > We are doing that - for quite some time now. (see r179637 & r179655). The > requirements are that: > great! > 1) svnversion is executable in /bin, /usr/bin or /usr/local/bin > 2) there is a .svn directory in your SRCDIR > small catch, i'm using svk, but i guess I'll look into current's newvers.sh. and running -stable. > If that's the case, newvers.sh will add the output of it to uname: > > "FreeBSD fbsd8 8.0-CURRENT FreeBSD 8.0-CURRENT #4 r180876:183019M:..." ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: svn rev. number
On Wednesday 01 October 2008 14:04:20 Danny Braniss wrote: > Hi, > Now that freebsd is under svn, I decided to try what I failed > with cvs, and actually using svn/svk/svnsync I have a mirror and a local > branch in sync! > Since the date reported by uname is not that relevant, is it possible to > add the svn-revision # ala build-...? This could make finding problems > easier, instead of kernel from 'date' one could say date/revision... just a > thought. We are doing that - for quite some time now. (see r179637 & r179655). The requirements are that: 1) svnversion is executable in /bin, /usr/bin or /usr/local/bin 2) there is a .svn directory in your SRCDIR If that's the case, newvers.sh will add the output of it to uname: "FreeBSD fbsd8 8.0-CURRENT FreeBSD 8.0-CURRENT #4 r180876:183019M:..." -- /"\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: svn rev. number
On 1 Oct 2008, at 13:04, Danny Braniss wrote: Hi, Now that freebsd is under svn, I decided to try what I failed with cvs, and actually using svn/svk/svnsync I have a mirror and a local branch in sync! Since the date reported by uname is not that relevant, is it possible to add the svn-revision # ala build-...? This could make finding problems easier, instead of kernel from 'date' one could say date/revision... just a thought. That was already done weeks ago: [EMAIL PROTECTED] ~ % uname -v FreeBSD 8.0-CURRENT #2 r182964: Sat Sep 13 17:32:57 WEST 2008 [EMAIL PROTECTED] :/home/rpaulo/freebsd/obj/home/rpaulo/freebsd/base/head/sys/ALPHA `ident /boot/kernel/kernel' also works. Regards, -- Rui Paulo -- Rui Paulo ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
svn rev. number
Hi, Now that freebsd is under svn, I decided to try what I failed with cvs, and actually using svn/svk/svnsync I have a mirror and a local branch in sync! Since the date reported by uname is not that relevant, is it possible to add the svn-revision # ala build-...? This could make finding problems easier, instead of kernel from 'date' one could say date/revision... just a thought. danny ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
