Re: Standard sbc and pcm support in GENERIC kernel?
Mathew Kanner: > I would like to note that kldload'ing the sound modules works >very well and I would prefer that to be standard operating procedure >for sound. The issue with kldloading is that you still need PNPBIOS for many on-board sound devices. Which means that you need to compile your own kernel anyway, or don´t you? Helge ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPC nsswitch implementation
Sounds similar to, but not as functional as, the lookupd in Mac OS X. :) On Mar 5, 2004, at 12:45 AM, Michael Bushkov wrote: We want you to look at this lookupd. It would be great for us to know if you like or not the way we made it. And we also want to know if this project can be added to FreeBSD project. -- Jordan Hubbard Engineering Manager, BSD Technology Group Apple Computer ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Standard sbc and pcm support in GENERIC kernel?
On Fri, 5 Mar 2004 19:06, Helge Oldach wrote: > The issue with kldloading is that you still need PNPBIOS for many > on-board sound devices. Which means that you need to compile your own > kernel anyway, or don´t you? I don't think I've ever seen a motherboard/BIOS where you HAD to compile it in the kernel.. I don't see why kldload'ing is different to static compilation WRT calling the BIOS.. (Then again I don't have any ISA hardware anymore :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
DEVICE_IDENTIFY(9)
The above manpage documents the return values, but it is a void function. Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Reason for LINK_MAX set to 32K?
Is there a technical reason why LINK_MAX is set to 32K? Would anything bad happen if this value was raised? Thanks, -- Stephen J. Roznowski([EMAIL PROTECTED]) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
IPC nsswitch implementation
Hello! Some time ago there was a discussion concerning in-process vs. IPC nsswitch implementation. We agreed that we should develop an example of IPC implementation and ask for a discussion. We are glad to present you sample implementation of the IPC nsswitch model. http://rsu.ru/~bushman/lookupd-0.1.1.tar.gz It currently has many limitations but should be suitable for demonstration of our approach. There is a daemon and client part in this project. After executing make in "daemon" folder you'll get: 1) lookupd daemon - it should be run by root. And (!) you should be in the lookupd folder - daemon will search for it's modules in ./modules. 2) nsswrapper/nss_lookupd.so - a plug-in for current nsswitch implementation. It should be placed as nss_lookupd.so.1 in /usr/local/lib. lookupd.conf is the daemon configuration file. It has the same syntax as nsswitch.conf. It should be placed in /etc. Examples of lookupd.conf and nsswitch.conf (needed to use lookupd) are in the archive. Daemon uses shared modules (dns, files and so on). Currently following function can use lookupd: - passwd functions - files module - group function - files module - gethostby* functions - files and dns module. We took the code for dns modules from current libc. So it's not thread safe and can be buggy, because daemon is multi-threaded. It was made just to show module-structure capabilities. Later, we'll make normal reentrant resolver. When daemon is running, it sends a lot of info to stdout. It's the way to make you able to know, that it works. There is currently no caching functions in daemon. But it's quite easy to add them - and it will be done in the nearest future. We want you to look at this lookupd. It would be great for us to know if you like or not the way we made it. And we also want to know if this project can be added to FreeBSD project. Please keep CC line of the message, so that all of our developers could read your replies. Michael Bushkov Software Engineer, Rostov State University ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Standard sbc and pcm support in GENERIC kernel?
On 3/4/2004, "Brandon D. Valentine" <[EMAIL PROTECTED]> wrote: >On Wed, Mar 03, 2004 at 05:03:40PM +0100, Jorn Argelo wrote: >> >> I've been on the question list for some time, and I have noticed that >> many people do not know how to get sound support up and running in >> FreeBSD 5.X. I know that re-compiling the kernel is easy enough, but >> there are still people not willing to do so, as I have noticed on the >> list. Therefor I thought it might be an idea to put sound support in the >> GENERIC kernel configuration, so that newbies will no longer find >> themselves stuck with that. > >If they'd read pcm(4) they'd know how to get sound support up and >running without recompiling their kernel. Is there something wrong with >requiring that a new user bother to read the documentation? I guess that that is the main problem. Some newbies don't read any documentation at all. They think that installing and configuring FreeBSD is as easy as Bill's software is ... Anyway, I was merely suggesting something, but if the list disagrees with me, then it's alright with me. Thanks for all the responses though, it gave me some insight. Cheers, Jorn. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Standard sbc and pcm support in GENERIC kernel?
Daniel O'Connor: >On Fri, 5 Mar 2004 19:06, Helge Oldach wrote: >> The issue with kldloading is that you still need PNPBIOS for many >> on-board sound devices. Which means that you need to compile your own >> kernel anyway, or don´t you? > >I don't think I've ever seen a motherboard/BIOS where you HAD to >compile it in the kernel.. I have a number of Compaq DeskPro EN K450 here. Rather decent machines for FreeBSD desktops, and for sure not uncommon hardware. But unfortunately the stupid Compaq BIOS doesn't have a knob to turn off PnP, so I have to rely on PNPBIOS to deal with what the Compaq BIOS had detected. With PNPBIOS: FreeBSD Audio Driver (newpcm) Installed devices: pcm0: at io 0x220 irq 5 drq 1:0 bufsz 4096 (1p/1r/0v channels duplex) Without PNPBIOS: no pcm0. Latest BIOS revision, of course. >I don't see why kldload'ing is different to static compilation WRT >calling the BIOS.. It's not. But without PNPBIOS either won't work on these boxes. Helge ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Standard sbc and pcm support in GENERIC kernel?
On Mar 05, Helge Oldach wrote: > Daniel O'Connor: > >On Fri, 5 Mar 2004 19:06, Helge Oldach wrote: > >> The issue with kldloading is that you still need PNPBIOS for many > >> on-board sound devices. Which means that you need to compile your own > >> kernel anyway, or don?t you? > > > >I don't think I've ever seen a motherboard/BIOS where you HAD to > >compile it in the kernel.. > > I have a number of Compaq DeskPro EN K450 here. Rather decent machines > for FreeBSD desktops, and for sure not uncommon hardware. But > unfortunately the stupid Compaq BIOS doesn't have a knob to turn off > PnP, so I have to rely on PNPBIOS to deal with what the Compaq BIOS had > detected. Helge, Are you required to compile sound in the kernel to get it to work? If so, then I will document the fact that in some unsual circumstances that including sound statcily in the kernel is needed, otherwise I intend to de-emphesize it. --Mat --Mat -- The beaver, which has come to represent Canada as the eagle does the United States and the lion Britain, is a flat-tailed, slow-witted, toothy rodent known to bite off it's own testicles or to stand under its own falling trees. - June Callwood ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Standard sbc and pcm support in GENERIC kernel?
On Fri, 5 Mar 2004 23:38, Helge Oldach wrote: > >I don't think I've ever seen a motherboard/BIOS where you HAD to > >compile it in the kernel.. > > I have a number of Compaq DeskPro EN K450 here. Rather decent machines > for FreeBSD desktops, and for sure not uncommon hardware. But > unfortunately the stupid Compaq BIOS doesn't have a knob to turn off > PnP, so I have to rely on PNPBIOS to deal with what the Compaq BIOS had > detected. > > With PNPBIOS: > > FreeBSD Audio Driver (newpcm) > Installed devices: > pcm0: at io 0x220 irq 5 drq 1:0 bufsz 4096 (1p/1r/0v > channels duplex) > > Without PNPBIOS: no pcm0. Ahh, I see.. Sorry I didn't realise you meant the PNPBIOS in the kernel.. duh :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Standard sbc and pcm support in GENERIC kernel?
Mathew Kanner <[EMAIL PROTECTED]> writes: > Are you required to compile sound in the kernel to get it to > work? No, he is required to compile a kernel with the PNPBIOS option (which is not in GENERIC). DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Reason for LINK_MAX set to 32K?
In the last episode (Mar 04), Stephen J. Roznowski said: > Is there a technical reason why LINK_MAX is set to 32K? Would > anything bad happen if this value was raised? Mainly because di_nlink is an int16_t in ufs/dinode.h and ufs/inode.h. I think it could have been bumped up to an int32_t in UFS2, but it's probably too late now. You might be able to change it to a uint16_t to raise the limit to 64K, but I don't know if the kernel ever relies on a negative link count at any time. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Standard sbc and pcm support in GENERIC kernel?
Mathew Kanner: >On Mar 05, Helge Oldach wrote: >> Daniel O'Connor: >> >On Fri, 5 Mar 2004 19:06, Helge Oldach wrote: >> >> The issue with kldloading is that you still need PNPBIOS for many >> >> on-board sound devices. Which means that you need to compile your own >> >> kernel anyway, or don?t you? >> > >> >I don't think I've ever seen a motherboard/BIOS where you HAD to >> >compile it in the kernel.. >> >> I have a number of Compaq DeskPro EN K450 here. Rather decent machines >> for FreeBSD desktops, and for sure not uncommon hardware. But >> unfortunately the stupid Compaq BIOS doesn't have a knob to turn off >> PnP, so I have to rely on PNPBIOS to deal with what the Compaq BIOS had >> detected. > > Are you required to compile sound in the kernel to get it to >work? Yes, that is exactly correct. I am sorry, I just wasn't clear enough with my wording. To be safe, I just tested it: case a) "options PNPBIOS" and "device pcm" in the kernel config => works case b) "options PNPBIOS" in the kernel config and "kldload snd_pcm" => pcm isn't recognized, but the other PnP devices show up during probe case c) *no* "options PNPBIOS" but "kldload snd_pcm" => neither pcm nor other PnP devices are recognized Did I forget one variation? :-) >If so, then I will document the fact that in some unsual >circumstances that including sound statcily in the kernel is needed, >otherwise I intend to de-emphesize it. I suppose the former is adequate. What strikes me is case b). It seems a kldload'ed module cannot recognize its devices when they were probed and attached by the PnP BIOS. Does that sound reasonable? This is 4.9-STABLE of some few days ago (right after the TCP re-assembly queue fix). How will it work with -CURRENT which doesn't have a PNPBIOS option? Can I use sound at all? Helge ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Standard sbc and pcm support in GENERIC kernel?
On Fri, 5 Mar 2004, Helge Oldach wrote: > case b) "options PNPBIOS" in the kernel config and "kldload snd_pcm" => > pcm isn't recognized, but the other PnP devices show up during probe > > case c) *no* "options PNPBIOS" but "kldload snd_pcm" => neither pcm nor > other PnP devices are recognized > > Did I forget one variation? :-) Have you tried kldload snd_driver instead of snd_pcm? This should load all modules, instead of just the pcm module. Unless you're certian that snd_pcm is the correct module for support for your sound card? kldload'ing snd_pcm never did "enough" to make sound work on my systems, I always needed to load snd_driver. --- david raistrick [EMAIL PROTECTED] http://www.expita.com/nomime.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Standard sbc and pcm support in GENERIC kernel?
On Fri, 5 Mar 2004, Helge Oldach wrote: > This is 4.9-STABLE of some few days ago (right after the TCP re-assembly > queue fix). How will it work with -CURRENT which doesn't have a PNPBIOS > option? Can I use sound at all? Ahh, I was refering to 5.x. I've never tried to kldload any pcm drivers in -STABLE. --- david raistrick [EMAIL PROTECTED] http://www.expita.com/nomime.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: DEVICE_IDENTIFY(9)
On Fri, Mar 05, 2004 at 11:52:28AM +0100, Mark Santcroos wrote: > The above manpage documents the return values, but it is a void function. > Fixed, thanks! Cheers, -- Ruslan Ermilov FreeBSD committer [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: Confirmation of change request for the freebsd-hackers mailing list subscription
--- david raistrick [EMAIL PROTECTED] http://www.expita.com/nomime.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Standard sbc and pcm support in GENERIC kernel?
[...Just noticed that we are posting to multiple groups. Sorry everyone, though I not ready to drop them...] On Mar 05, Helge Oldach wrote: > Mathew Kanner: > >On Mar 05, Helge Oldach wrote: > > Yes, that is exactly correct. I am sorry, I just wasn't clear enough > with my wording. To be safe, I just tested it: > > case a) "options PNPBIOS" and "device pcm" in the kernel config => works > > case b) "options PNPBIOS" in the kernel config and "kldload snd_pcm" => > pcm isn't recognized, but the other PnP devices show up during probe > > case c) *no* "options PNPBIOS" but "kldload snd_pcm" => neither pcm nor > other PnP devices are recognized > > Did I forget one variation? :-) Helge, kldloading snd_pcm isn't enough. You need to load the driver for your particular card (the module dependacies should load snd_pcm for you). I think you are going to have to retry your tests. --Mat -- We peer so suspiciously at each other that we cannot see that we Canadians are standing on the mountaintop of human wealth, freedom and privilege. - Pierre Elliott Trudeau ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Standard sbc and pcm support in GENERIC kernel?
On Thu, 4 Mar 2004, Brandon D. Valentine wrote: > If they'd read pcm(4) they'd know how to get sound support up and > running without recompiling their kernel. Is there something wrong with > requiring that a new user bother to read the documentation? pcm(4) only explains the technical details, as well as partially covering the reboot-to-make-it-work scenario. It doesn't cover the kdlload scenario to bring sound online without rebooting. If pcm(4) or the handbook, or something, would give a more end-user oriented (for those who are new to 5.x or new to freebsd entirely) approach, this would be very helpful. pcm(4) also provides no detail on how to determine what "foo" should be for your soundcard. snd_foo_load (``NO'') If set to ``YES'', load driver for card/chipset foo. For example, I have an ALC650 soundcard in my XPC. Where do I look to find out what snd_foo_load I need to enable the sound? I've still not found this information. I use snd_driver_load="YES" which loads /all/ of the pcm drivers, but I cannot tell from kldstat which driver I'm actually using, so I could avoid loading the others. Providing detail on how to kldload "snd_driver_load" or "snd_foo_load" would be nice, so users can test this without rebooting their systems. kldload snd_driver is of course the correct way to do it. FWIW, kldunload snd_driver does /not/ unload all of the modules that kldload snd_driver loads. All of this of course assumes that the modules are even built and installed in /boot/kernel/ which may or may not be the case (in my experiance) with a fresh installation. You may need to make install these... ~shrug~ ...david --- david raistrick [EMAIL PROTECTED] http://www.expita.com/nomime.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Standard sbc and pcm support in GENERIC kernel?
Mathew Kanner: >On Mar 05, Helge Oldach wrote: >> Mathew Kanner: >> >On Mar 05, Helge Oldach wrote: >> case b) "options PNPBIOS" in the kernel config and "kldload snd_pcm" => >> pcm isn't recognized, but the other PnP devices show up during probe > > kldloading snd_pcm isn't enough. You need to load the driver >for your particular card (the module dependacies should load snd_pcm >for you). I think you are going to have to retry your tests. Bingo! kldload snd_ess does in fact also load snd_sbc and snd_pcm, and it all works. Apologies, I was mislead by the fact that in the kernel just has "options pcm" without any further fuzz. So yes: some machines require a kernel with PNPBIOS even when sound modules can be kldload'ed. I presume these are typically boxen without knob to disable the PnP BIOS. Still I wonder whether sound on -CURRENT will do on such a box... Thanks all for sharing! Helge ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPC nsswitch implementation
The Mac OS X lookupd does aggressive caching with cache invalidation support, supports the notion of flushing the cache on certain events (like when you reconfigure your network interfaces or switch authentication plugins), and quite a few other things. No surprise, really, given that it's been around for years. Julian was asking where to find it, and for those who get lost navigating Apple's darwin site, there's also opendarwin's cvsweb interface. Darwin's "nsswitch" implementation lives in Libinfo, of which lookupd is a sub-project: http://cvs.opendarwin.org/index.cgi/src/Libinfo/ - Jordan On Mar 5, 2004, at 6:46 AM, Michael Bushkov wrote: Hello! What do you mean exactly by saying "not as functional"? Michael Bushkov Software Engineer, Rostov State University On Fri, 5 Mar 2004, Jordan K Hubbard wrote: Sounds similar to, but not as functional as, the lookupd in Mac OS X. :) On Mar 5, 2004, at 12:45 AM, Michael Bushkov wrote: We want you to look at this lookupd. It would be great for us to know if you like or not the way we made it. And we also want to know if this project can be added to FreeBSD project. -- Jordan Hubbard Engineering Manager, BSD Technology Group Apple Computer ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-arch To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Jordan Hubbard Engineering Manager, BSD Technology Group Apple Computer ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
A simple question
Hello.. I am super new to this list, and I have a simple question that I don't know why it does that. I have a simple test program. I compile it, and gdb to disassemble main. I got the following.. 0x80481f8 : push %ebp 0x80481f9 : mov%esp,%ebp 0x80481fb : sub$0x8,%esp 0x80481fe : and$0xfff0,%esp 0x8048201 : mov$0x0,%eax 0x8048206 :sub%eax,%esp 0x8048208 :movl $0x804a6ce,0xfff8(%ebp) 0x804820f :movl $0x0,0xfffc(%ebp) 0x8048216 :sub$0x4,%esp 0x8048219 :push $0x0 0x804821b :lea0xfff8(%ebp),%eax 0x804821e :push %eax 0x804821f :pushl 0xfff8(%ebp) 0x8048222 :call 0x804823c 0x8048227 :add$0x10,%esp 0x804822a :mov$0x0,%eax 0x804822f :leave 0x8048230 :ret I don't know if at line 5, we move zero to %eax. why do we need to sub %eax, %esp? why do we need to substract 0 from the stack pointer?? Any help is really appreciated. best regards Chungwei ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Standard sbc and pcm support in GENERIC kernel?
Hi, David Raistrick wrote on Fri, Mar 05, 2004 at 08:27:56AM -0800: [..] > kldload snd_driver > > is of course the correct way to do it. FWIW, kldunload snd_driver does > /not/ unload all of the modules that kldload snd_driver loads. [..] snd_driver is a module that contains _all_ drivers, thus you have the best chance to get sound working. Unloading it, will of course unload the whole module with all drivers. There is no way to leave one of the drivers in the kernel. I agree, that there is not much documentation which driver module supports which sound device (or I was not successful to dig that up). However, you can determine the correct module, by subsequently loading and unloading each individual driver module. The one which attached to your sound device and actually works (check /dev/sndstat as well) is obviously the correct one. Not a very efficient way, but it works. :) Best regards, Daniel -- IRCnet: Mr-Spock - kommst du siehst du, gehst du hast du, weisst du, krass! - Daniel Lang * [EMAIL PROTECTED] * +49 89 289 18532 * http://www.leo.org/~dl/ smime.p7s Description: S/MIME cryptographic signature
Re: Standard sbc and pcm support in GENERIC kernel?
[ Whoa, Nelly. Cc: trimmed. ] On Fri, Mar 05, 2004 at 05:33:47PM +0100, Helge Oldach wrote: > > This is 4.9-STABLE of some few days ago (right after the TCP re-assembly > queue fix). How will it work with -CURRENT which doesn't have a PNPBIOS > option? Can I use sound at all? If you wish to test this you might burn and boot a FreeSBIE LiveCD, which is based on FreeBSD 5.2.1. This should tell you whether ACPI in the 5.x kernel handles your BIOS quirk. HTH, Brandon D. Valentine -- [EMAIL PROTECTED] http://www.geekpunk.net Pseudo-Random Googlism: spring is in the air whether he's pausing for an outdoor lunch or enjoying a bounce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Standard sbc and pcm support in GENERIC kernel?
On Mar 05, Helge Oldach wrote: > [..snip..] > Bingo! kldload snd_ess does in fact also load snd_sbc and snd_pcm, and > it all works. Apologies, I was mislead by the fact that in the kernel > just has "options pcm" without any further fuzz. Yes, this is a confusing aspect. It should be a little better soon. --Mat -- The state has no business in the bedrooms of the nation. - Pierre Elliott Trudeau ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPC nsswitch implementation
The Mac OS X lookupd does aggressive caching with cache invalidation support, supports the notion of flushing the cache on certain events (like when you reconfigure your network interfaces or switch authentication plugins), and quite a few other things. No surprise, really, given that it's been around for years. Julian was asking where to find it, and for those who get lost navigating Apple's darwin site, there's also opendarwin's cvsweb interface. Darwin's "nsswitch" implementation lives in Libinfo, of which lookupd is a sub-project: http://cvs.opendarwin.org/index.cgi/src/Libinfo/ - Jordan The problem of using Darwin's lookupd was discussed some time ago in the freebsd-arch mailing list. It seems to me that the way to port Darwin's lookupd on FreeBSD was not found, was it? Our implementation of lookupd is a demonstration of the approach for the FreeBSD-specific IPC implementation of nsswitch. Its architecture is flexible enough to implement all the features you have mentioned. The version that we have sent isn't a finished project. It's in the development stage and caching is currently our main task. We hope to make caching in the nearest future. We'll try to release stable and quite full version (i mean caching, LDAP module and so on) as soon as we can. Our questions are: 1) What do you think about our whole approach to the IPC implementation development? 2) Is there an opportunity to use our implementation of lookupd in the FreeBSD project? We'll be glad to hear your opinion. Michael Bushkov, Software Engineer, Rostov State University ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A simple question
De: Chungwei Hsiung <[EMAIL PROTECTED]> Fecha: Viernes, Marzo 5, 2004 7:43 pm >I have a simple test program. I compile it, > and > gdb to disassemble main. I got the following.. > > 0x80481f8 : push %ebp > 0x80481f9 : mov%esp,%ebp > 0x80481fb : sub$0x8,%esp > 0x80481fe : and$0xfff0,%esp > 0x8048201 : mov$0x0,%eax > 0x8048206 :sub%eax,%esp > > I don't know if at line 5, we move zero to %eax. why do we need to sub %eax, %esp? > why do we need to subtract 0 from the stack pointer?? I am no really sure, but it maybe be because you don't have any local variable, so it is no necessary to allocate memory in the stack for them. This seems a pattern from the compiler, it subtract the size of local variables from the stack pointer, so when there is none it subtracts zero. But this is just a supposition Regards, Isaac ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPC nsswitch implementation
On Fri, Mar 05, 2004 at 10:41:33PM +0300, Michael Bushkov wrote: > > Our implementation of lookupd is a demonstration > of the approach for the FreeBSD-specific IPC implementation > of nsswitch. Its architecture is > flexible enough to implement all the features you have mentioned. > The version that we have sent isn't a finished project. It's in the > development stage and caching is currently our main task. We hope to make > caching in the nearest future. > We'll try to release stable and quite full version (i mean caching, LDAP > module and so on) as soon as we can. > > Our questions are: > 1) What do you think about our whole approach to the IPC implementation > development? > 2) Is there an opportunity to use our implementation of lookupd in the > FreeBSD project? The thing that I'm most interested in is getting support for the existing NSS modules out there (nss_ldap being my personal interest). Is there a way with the IPC based model to make the existing in-process modules (I'm thinking nss_winbind and nss_ldap) work with the IPC daemon? If not, I doubt you'll get a whole lot of support for the IPC model because it will cause us to incur a maintence cost to make these other very useful modules work. -gordon pgp0.pgp Description: PGP signature
Re: Issues with SSH+LDAP on FreeBSD 5.2
On Thu, Mar 04, 2004 at 07:46:11AM -0500, sybexmy alias wrote: > Hi All, > > I'm attempting to integrate SSH with LDAP and PAM on a FREEBSD 5.2 host. > > However I'm having "access denied" error message when I try to ssh to my ldap server > using PUTTY Release 0.53b. > > I have google around and found several document like > "http://www.cultdeadsheep.org/FreeBSD/docs/Quick_and_dirty_FreeBSD_5_x_and_nss_ldap_mini-HOWTO.html";. > This documentation also does not work. > > I really hope that some body can guide me and give some comment what I have done > wrong in my configuration files. Can you do an id testuser1? Can you login as testuser1 from the console? -gordon pgp0.pgp Description: PGP signature
Re: IPC nsswitch implementation
I understand this. There are some problems in making current nss-modules compatible with our implementation. The main problem is process euid. When you're using current nss-modules they work as part of your program - and geteuid functions work correctly. But when lookupd is used, euid of the process is lookupds' euid. And that's a problem. There are two possible solutions, i think: 1) We can run 2 daemons. One with root euid. And one with "simple user" euid. Client side will choose one or another to connect. But this way is rather expensive. 2) We can try to change geteuid function in modules for our function, which will return thread-specific value, which would be set by daemon. The minus is that we, however, will need to recompile nss-modules. And another thing. When we use lookupd daemon we can optimize it work much. For example, modules can use persistent-connections. It can be very useful. But, returning to your question :) It is possible, i think. There are some disadvantages, but it's possible. Of course, using modules, developed for lookupd would be better, but as "compatibility" decision we can try to implement usage of current nss-modules. Michael Bushkov, Software Engineer, Rostov State University On Fri, 5 Mar 2004, Gordon Tetlow wrote: On Fri, Mar 05, 2004 at 10:41:33PM +0300, Michael Bushkov wrote: > > Our implementation of lookupd is a demonstration > of the approach for the FreeBSD-specific IPC implementation > of nsswitch. Its architecture is > flexible enough to implement all the features you have mentioned. > The version that we have sent isn't a finished project. It's in the > development stage and caching is currently our main task. We hope to make > caching in the nearest future. > We'll try to release stable and quite full version (i mean caching, LDAP > module and so on) as soon as we can. > > Our questions are: > 1) What do you think about our whole approach to the IPC implementation > development? > 2) Is there an opportunity to use our implementation of lookupd in the > FreeBSD project? The thing that I'm most interested in is getting support for the existing NSS modules out there (nss_ldap being my personal interest). Is there a way with the IPC based model to make the existing in-process modules (I'm thinking nss_winbind and nss_ldap) work with the IPC daemon? If not, I doubt you'll get a whole lot of support for the IPC model because it will cause us to incur a maintence cost to make these other very useful modules work. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A simple question
> ISAAC GELADO FERNANDEZ wrote: > > >De: Chungwei Hsiung <[EMAIL PROTECTED]> > >Fecha: Viernes, Marzo 5, 2004 7:43 pm > > > > > >>I have a simple test program. I compile it, > >>and > >>gdb to disassemble main. I got the following.. > >> > >>0x80481f8 : push %ebp > >>0x80481f9 : mov%esp,%ebp > >>0x80481fb : sub$0x8,%esp > >>0x80481fe : and$0xfff0,%esp > >>0x8048201 : mov$0x0,%eax > >>0x8048206 :sub%eax,%esp > >> > >>I don't know if at line 5, we move zero to %eax. why do we need > to sub %eax, %esp? why do we need to subtract 0 from the stack > pointer??>> > >> > > > > I am no really sure, but it maybe be because you don't have any > local variable, so it is no necessary to allocate memory in the > stack for them. This seems a pattern from the compiler, it subtract > the size of local variables from the stack pointer, so when there > is none it subtracts zero. But this is just a supposition > > > > > > > thank you for the reply.. > I try it again to call a function with local variables, but it does > that > as well. I think that line is not a part of a function prologue > because > when I try it with or without local variables, it is always there. > any > ideas?? > btw.. the compiler I use is gcc 3.2.2 I have performed some tests and the "strange" code apperars always. At first I thought the compiler puts the code to align the stack, but if you write a function it doesn't appear. Maybe the compiler puts the subl to set system flags to a known value, but I don't really know. I will try to obtain a good answer, I am really intrigate ;) Regards, Isaac > > best regards > Chungwei > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Standard sbc and pcm support in GENERIC kernel?
On Wednesday 03 March 2004 04:31 pm, Randy Pratt wrote: > On Wed, 3 Mar 2004 17:03:40 +0100 (CET) you wrote: > > I've been on the question list for some time, and I have noticed > > that many people do not know how to get sound support up and > > running in FreeBSD 5.X. I know that re-compiling the kernel is easy > > enough, but there are still people not willing to do so, as I have > > noticed on the list. Therefor I thought it might be an idea to put > > sound support in the GENERIC kernel configuration, so that newbies > > will no longer find themselves stuck with that. > > I think I've read more than one time about problems fitting the > installation on the 1.44M floppies. That's no longer a problem in 5.x. I would like to see pcm(4) added back to GENERIC on 5.x. 4.x has been around long enough that its GENERIC can probably just stay the way it is. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CPU update
On Thursday 04 March 2004 02:04 am, Mark Dixon wrote: > On Wednesday 03 Mar 2004 23:09, John Baldwin wrote: > > On Wednesday 03 March 2004 06:02 pm, Mark wrote: > > > Dear Sirs: > > > > > > I compiled my FreeBSD 4.7R for an AMD XP-2000. If I upgrade to an AMD > > > 64 3200, will my OS still run? The AMD 64 is 32-bit downwards > > > compatible. > > > > Yes. FreeBSD 5.x also supports amd64 natively. > > The next question is then can you rebuild world and ports for amd64, reboot > and run in 64bit mode? You might be able to but you are probably better off just reinstalling to do that type of upgrade. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Strange instructions in compiler output (was: A simple question)
On Friday, 5 March 2004 at 13:43:04 -0500, Chungwei Hsiung wrote: > Hello.. > I am super new to this list, and I have a simple question that I don't > know why it does that. I have a simple test program. I compile it, and > gdb to disassemble main. I got the following.. > > 0x80481f8 : push %ebp > 0x80481f9 : mov%esp,%ebp > 0x80481fb : sub$0x8,%esp > 0x80481fe : and$0xfff0,%esp > 0x8048201 : mov$0x0,%eax > 0x8048206 :sub%eax,%esp > 0x8048208 :movl $0x804a6ce,0xfff8(%ebp) > 0x804820f :movl $0x0,0xfffc(%ebp) > 0x8048216 :sub$0x4,%esp > 0x8048219 :push $0x0 > 0x804821b :lea0xfff8(%ebp),%eax > 0x804821e :push %eax > 0x804821f :pushl 0xfff8(%ebp) > 0x8048222 :call 0x804823c > 0x8048227 :add$0x10,%esp > 0x804822a :mov$0x0,%eax > 0x804822f :leave > 0x8048230 :ret > > I don't know if at line 5, we move zero to %eax. why do we need to sub > %eax, %esp? why do we need to substract 0 from the stack pointer?? > Any help is really appreciated. This is probably because you didn't optimize the output. You'd be surprised how many redundant instructions the compiler puts in under these circumstances. Try optimizing and see what the code looks like. If this *was* done with optimization, let's see the source code. Greg -- Note: I discard all HTML mail unseen. Finger [EMAIL PROTECTED] for PGP public key. See complete headers for address and phone numbers. pgp0.pgp Description: PGP signature
Re: Strange instructions in compiler output
On Friday, 5 March 2004 at 18:43:11 -0500, Chungwei Hsiung wrote: > Greg 'groggy' Lehey wrote: > >> On Friday, 5 March 2004 at 13:43:04 -0500, Chungwei Hsiung wrote: >> >> >>> Hello.. >>> I am super new to this list, and I have a simple question that I don't >>> know why it does that. I have a simple test program. I compile it, and >>> gdb to disassemble main. I got the following.. >>> >>> 0x8048201 : mov$0x0,%eax >>> 0x8048206 :sub%eax,%esp >>> ... >>> >>> I don't know if at line 5, we move zero to %eax. why do we need to sub eax, %esp? why do we need to substract 0 from the stack pointer?? >>> Any help is really appreciated. >> >> This is probably because you didn't optimize the output. You'd be >> surprised how many redundant instructions the compiler puts in under >> these circumstances. Try optimizing and see what the code looks like. >> >> If this *was* done with optimization, let's see the source code. > > Hello.. thank you very much for the reply > I actually don't know how to use the optimization. Use the gcc command line options. See below. >I just compile it with gcc 3.2.2, and use gdb to disassemble main to >get this assembly. Is it possible I can get the non-redundent output? >here is the code I compile.. > > ... The best way to look at the assembly output is to generate it directly from the compiler. I get: $ cc -O -pipe -mcpu=pentiumpro -S exec.c $ cat exec.s .LC0: .string "/bin/sh" ... main: pushl %ebp movl%esp, %ebp subl$24, %esp andl$-16, %esp movl$.LC0, -8(%ebp) leal-8(%ebp), %edx movl$0, 4(%edx) movl-8(%ebp), %eax movl%eax, (%esp) movl%edx, 4(%esp) movl$0, 8(%esp) callexecve movl$0, %eax movl%ebp, %esp popl%ebp ret This doesn't look that much like your code. Without the -O (optimize) flag I get: $ cc -pipe -mcpu=pentiumpro -S exec.c $ cat exec.s ... main: pushl %ebp movl%esp, %ebp subl$24, %esp andl$-16, %esp movl$0, %eax subl%eax, %esp movl$.LC0, -8(%ebp) So yes, it looks as if you're not optimizing. Greg -- Note: I discard all HTML mail unseen. Finger [EMAIL PROTECTED] for PGP public key. See complete headers for address and phone numbers. pgp0.pgp Description: PGP signature
Re: Standard sbc and pcm support in GENERIC kernel?
On Thu, Mar 04, 2004 at 06:26:47PM -0500, Dan Langille wrote: > > If they'd read pcm(4) they'd know how to get sound support up and > > running without recompiling their kernel. Is there something wrong with > > requiring that a new user bother to read the documentation? > > They would first have to know to read man pcm(4). All the have to do is look at the handbook. And if they can't find the link on the *front page* of freebsd.org, under the clearly labelled catagory of "Support", then there is very little we can or should do to help them. After a point, enough is enough. If the user isn't prepared to educate themselves, your attempts will ultimately fail. -- Avleen Vig Systems Administrator Personal: www.silverwraith.com EFnet:irc.mindspring.com (Earthlink user access only) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Standard sbc and pcm support in GENERIC kernel?
On Fri, 5 Mar 2004, Avleen Vig wrote: > On Thu, Mar 04, 2004 at 06:26:47PM -0500, Dan Langille wrote: > > > If they'd read pcm(4) they'd know how to get sound support up and > > > running without recompiling their kernel. Is there something wrong with > > > requiring that a new user bother to read the documentation? > > > > They would first have to know to read man pcm(4). > > All the have to do is look at the handbook. And if they can't find the > link on the *front page* of freebsd.org, under the clearly labelled > catagory of "Support", then there is very little we can or should do to > help them. After a point, enough is enough. If the user isn't prepared > to educate themselves, your attempts will ultimately fail. *That* explanation is vast difference to saying they have to read man pcm(4). The difference is sigficicant. -- Dan Langille - BSDCan: http://www.bsdcan.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Standard sbc and pcm support in GENERIC kernel?
On Fri, 5 Mar 2004, Dan Langille wrote: > *That* explanation is vast difference to saying they have to read man > pcm(4). The difference is sigficicant. In the same breath, someone needs to install a spell checker and verify the grammer. -- Dan Langille - BSDCan: http://www.bsdcan.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Standard sbc and pcm support in GENERIC kernel?
On Fri, Mar 05, 2004 at 09:58:52PM -0500, Dan Langille wrote: > > All the have to do is look at the handbook. And if they can't find the > > link on the *front page* of freebsd.org, under the clearly labelled > > catagory of "Support", then there is very little we can or should do to > > help them. After a point, enough is enough. If the user isn't prepared > > to educate themselves, your attempts will ultimately fail. > > *That* explanation is vast difference to saying they have to read man > pcm(4). The difference is sigficicant. Maybe if I say this here, having it in the archives will help *SOMEONE* at *SOME* point in the future :-) 95% of the questions I see asked about FreeBSD can be answered by reading the Handbook (http://freebsd.org/handbook/) Everyone newbie with a problem should first go there. Hell I'm not even a newbie (haven't been for almost 7 years) but I still go there. -- Avleen Vig Systems Administrator Personal: www.silverwraith.com EFnet:irc.mindspring.com (Earthlink user access only) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Standard sbc and pcm support in GENERIC kernel?
On Fri, 5 Mar 2004, Dan Langille wrote: > On Fri, 5 Mar 2004, Avleen Vig wrote: > > All the have to do is look at the handbook. And if they can't find the > > link on the *front page* of freebsd.org, under the clearly labelled > > catagory of "Support", then there is very little we can or should do > > to help them. After a point, enough is enough. If the user isn't > > prepared to educate themselves, your attempts will ultimately fail. > *That* explanation is vast difference to saying they have to read man > pcm(4). The difference is sigficicant. It also presumes the end user has net access, which is not a given. Jamie Bowden -- "It was half way to Rivendell when the drugs began to take hold" Hunter S Tolkien "Fear and Loathing in Barad Dur" Iain Bowen <[EMAIL PROTECTED]> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPC nsswitch implementation
Why not use a UNIX domain socket as the transport and then use credential passing to pass the credentials lookupd should use to do the lookup? On Mar 5, 2004, at 1:27 PM, Michael Bushkov wrote: When you're using current nss-modules they work as part of your program - and geteuid functions work correctly. But when lookupd is used, euid of the process is lookupds' euid. -- Jordan Hubbard Engineering Manager, BSD Technology Group Apple Computer ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
