wrong description
In the file /kde/core/kdebase.xml at line 163 and following i found this description: termcommandkdeprint/command/term listitem parais a dialog box for managing diagnostic messages at runtime./para Maybe is better the one from the KDE website, like: KDEPrint is the printing module in KDE. It manages the actual printing from KDE applications, handles print job administration and handles printer and print system management At line 237 in the description of kioslaves there is certian instead of certain Giulio -- ++ | LFS user #11031 | ++ -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Bisogno di liquidità? Non devi spiegare per cosa. Fino a 4.000 a casa tua Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=2291d=20050223 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: wrong description
Giulio Daprelà wrote: In the file /kde/core/kdebase.xml at line 163 and following i found this description: termcommandkdeprint/command/term listitem parais a dialog box for managing diagnostic messages at runtime./para Maybe is better the one from the KDE website, like: KDEPrint is the printing module in KDE. It manages the actual printing from KDE applications, handles print job administration and handles printer and print system management At line 237 in the description of kioslaves there is certian instead of certain Fixed. Thanks. It always helps to have more eyes spotting errors. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Linux-PAM nitpicks
Jack Brown wrote: Here's how I look at it: You go to compile something, it decides that it want's libm and starts off looking at /usr/lib to see what it can find. It comes across a file /usr/lib/libm.so which is linked to a file called /lib/libm.so.6. based on this it tells the linker to link the resulting binary to a file named /lib/libm.so.6. When you run the program it sees that it need to load up the file /lib/libm.so.6 and in doing so ends up following the symlink and ends up actually loading /lib/libm.2.3.4.so in the process. One small correction, Actually it tells the linker to hardcode libm.so.6 without the full path (whoops). Then it looks for libm.so.6 starting in /usr/lib, then in /lib. (and then I guess it starts searching through /etc/ld.so.cache for libs that are in directories specified in /etc/ld.so.conf, assuming ldconfig has been run since they were installed) Jack Brown -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
