Your message to PyKDE awaits moderator approval
Your mail to 'PyKDE' with the subject [VIRUSMAIL] Delivery reports about your e-mail Is being held until the list moderator can review it for approval. The reason it is being held: Post by non-member to a members-only list Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://mats.imk.fraunhofer.de/mailman/confirm/pykde/f705652f62fa87198cae9886cd140d4d49cb8354 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
What is wrong in my conf file?
Hi, a attached my kernel configuration file, can you find the problem, please? config command went OK make depend - error code 1 thank you for help SROT Description: Binary data ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ntfs-3g for FreeBSD?
Wondering what's the status on NTFS-3G for FreeBSD? http://digg.com/linux_unix/NTFS-3G_-_Full_NTFS_read_write_support_for_Linux Thanks, Kyrre ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What is wrong in my conf file?
mr thooL wrote: Hi, a attached my kernel configuration file, can you find the problem, please? config command went OK make depend - error code 1 thank you for help No one can help you with this limited information: 1) attachments are not allowed on questions@ so no-one can see your kernel. If you can make it available on a web site that is much better than posting the whole thing here. And without 2) below it will be less than useful. 2) error code 1 is worthless - it is just an exit status. Please start by showing the actual error. The 10 or so lines leading up to this message would probably do as long as they show what was *actually happening*. And tell us what version of FreeBSD you are doing this on. You might also try summarising the changes you made to the generic kernel. 3) Didn't the config/make depend way of building a kernel go out with 4.something? See the handbook for the correct make buildkernel KERNCONF=MYKERNEL procedure for a modern FreeBSD. Of course, with a bad config file, that will fail the same way so see 2) first. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What is wrong in my conf file?
mr thooL [EMAIL PROTECTED] wrote: a attached my kernel configuration file, can you find the problem, please? config command went OK make depend - error code 1 I only had a quick look at your kernel configuration, one problem is that you disabled device wlan but kept device ural enabled. Please quote the exact error message next time. Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Re: What is wrong in my conf file?
Alex Zbyslaw wrote: mr thooL wrote: Hi, a attached my kernel configuration file, can you find the problem, please? config command went OK make depend - error code 1 thank you for help No one can help you with this limited information: 1) attachments are not allowed on questions@ so no-one can see your kernel. If you can make it available on a web site that is much better than posting the whole thing here. And without 2) below it will be less than useful. Apparently it was attached, but the error is still more important. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
building new kernel failed
Hi, here is my conf file: == # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.3.2.1 2005/10/28 19:22:41 jhb Exp $ machine i386 cpu I686_CPU ident GENERIC # To statically compile in device wiring instead of /boot/device.hints #hints GENERIC.hints # Default places to look for devices. makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols #optionsSCHED_ULE # ULE scheduler options EXT2FS options SCHED_4BSD # 4BSD scheduler options TCPDEBUG options QUOTA options PREEMPTION # Enable kernel thread preemption options VESA options INET# InterNETworking options INET6 # IPv6 communications protocols options SC_PIXEL_MODE options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT# NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_GPT# GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic# I/O APIC # Bus support. device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI Controllers device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices device ahd # AHA39320/29320 and onboard AIC79xx devices device amd # AMD 53C974 (Tekram DC-390(T)) device isp # Qlogic family #device ispfw # Firmware for QLogic HBAs- normally a module device mpt # LSI-Logic MPT-Fusion #device ncr # NCR/Symbios Logic device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') device trm # Tekram DC395U/UW/F DC315U adapters device adv # Advansys SCSI adapters device adw # Advansys wide SCSI adapters device aha # Adaptec 154x SCSI adapters device aic #
Re: building new kernel failed
mr thooL wrote: Hi, here is my conf file: [snip] # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! #devicemiibus# MII bus support Read the note :-) You have to keep miibus. Cheers, Jorn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: building new kernel failed
mr thooL [EMAIL PROTECTED] wrote: here is my conf file: # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! This comment exists for a reason ... #device miibus # MII bus support devicere # RealTek 8139C+/8169/8169S/8110S devicerl # RealTek 8129/8139 and here is the error message: == linking kernel.debug if_re.o(.text+0x19a7): In function `re_attach': /usr/src/sys/dev/re/if_re.c:1193: undefined reference to `mii_phy_probe' if_re.o(.text+0x2759): In function `re_tick': ... you just found it. Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Re: building new kernel failed
# PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! [...] devicere# RealTek 8139C+/8169/8169S/8110S devicerl# RealTek 8129/8139 But no device miibus as the notes say there must be. Of course, once you get past this one, there may be more errors. If there are, can I suggest that you first go back to the GENERIC kernel and start again, this time being a bit more conservative about taking things out. You should also make a copy of GENERIC called something else. Your kernel is simply not GENERIC any more, and may get overwritten by the real GENERIC when you cvsup. From the file it looks like you are editing GENERIC in place which is a very bad idea and definitely not what the handbook recommends. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DWL-650 Revision M
Brian Henning [EMAIL PROTECTED] writes: Hello All, If someone could help me out that would be great. I currently own a wireless card Dlink (DWL-650 Revision M) and I am not able to get FreeBSD 6.1 to load the wi driver. I perused the wi man pages and found that the D-Link DWL-650 is on the list of supported cards. I question whether or not this includes all revisions of the DWL-650. Can someone please confirm that the DWL-650 Revision M is or is NOT supported? Does it use a Atheros AR521x chip? Have you tried ath(4)? Regards, loader ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
MBR and slices
After reintalling windows i want to install FreeBSD boot loader (/boot/boot0), after the second operation of record of the loader is carried out writes about the following (precisely I do not remember that wrote fdisk): MBR not write Invalid Geom Esteemed handbook and has tried by means of boot0cfg to put, i wrote the following: # boot0cfg -s 2 ad0 Has not helped too though the loader was, but the chosen system was not loaded. I tried to replace number of slice: # boot0cfg -s 1 ad0 Besides the loader was, but the chosen system was not loaded. Has then found out that sections on slice at disk ad0 have flied all, on this disk the system has been installed. Whether it is possible to restore a disk or even the information therefrom? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AVI to MPEG conversion
mplayer is very powerful and it's manpage is overwhelming. Once you get started with it mplayer's features become less inaccessible. Here is a pretty good article that I think answers your question and provides sufficient examples to make your quest to better understand mplayer a good start. http://applications.linux.com/article.pl?sid=06/04/17/2058219tid=39 == Now I, Nebuchadnezzar, praise and extol and honor the King of heaven, for all his works are truth, and his ways are justice; and he is able to bring low those who walk in pride. Daniel 4:37 __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AVI to MPEG conversion
Neil Short wrote: mplayer is very powerful and it's manpage is overwhelming. Once you get started with it mplayer's features become less inaccessible. Or you may try gmencoder which offers a GTK interface to the basic functionality of mencoder. It will be largely sufficient for your needs. Jona ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port for Perl modules
On 7/14/06, Gerard Seibert [EMAIL PROTECTED] wrote: Sorry if I asked this before, but does anyone know if there is a port for the following Perl modules: 1) Net-SMTP-SSL 2) Bundle Libnet http://www.freebsd.org/cgi/ports.cgi?query=p5stype=all -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
DL360 G4 shared network iLo and FreeBSD
I'm trying to setup a DL360 G4 for use in a colo environment with FreeBSD. I've run into one problem: I've setup the iLo to use the shared network option, which allows the iLo to share the same network interface as the host computer. But the iLo hangs whenever the FreeBSD kernel loads. When booting the system, it gets this far before the ilo is hangs: ? Select option, [Enter] for default ? ? or [Space] to pause timer 2 ? ??? Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-RELEASE-p2 #0: Sat Jul 15 01:36:17 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP ACPI APIC Table: HP 0083 The system continues to boot OK, so I can provide further information as needed. When the ilo is hung, it no longer responds to pings/ssh. As soon as FreeBSD is rebooted, the iLo becomes responsive again without any intervention. I've also tried loading a test linux installation, to see if the same thing happens. The iLo continues to function normally (doesn't hang) when running linux. Anybody have an idea what FreeBSD is doing to hang the iLo in this situation, and how to keep it from doing so? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
hpijs, foomatic-rip, and CUPS
Hello, I cannot get hpijs to install. The full install log of it is attached to this email with a small snippet towards the bottom of this message. Does anyone have any ideas/ suggestions? I am running FreeBSD 6.1-STABLE with the latest CUPS infrastructure. For some time, I have been having issues with my printer (hp LaserJet 1160Le) ever since the CUPS update to 1.2.0. The latest problem I have been having was with foomatic-rip (I would get the error message /usr/local/libexec/cups/filter/foomatic-rip failed). So, per E.J. Cerejo's suggestion, I uninstalled and reinstalled my entire printing infrastructure (this was to make sure that there were no oddities with the CUPS and gnutls upgrade). Everything managed to install _except_ hpijs. Without hpijs installed, I have no foomatic-rip file in that folder. Ergo, hpijs is my number one chance for fixing this issue. It also happens to be the recommended driver for my printer on www.linuxprinting.org. I installed hplip to see if that would work (since it shows support for the printer on their site), however my printer does not show up in any of the drop-down menus. Thank you so much for your assistance with this. -Anthony snip === Installing for hpijs-2.1.4 === hpijs-2.1.4 depends on file: /usr/local/bin/perl5.8.8 - found === hpijs-2.1.4 depends on executable: gs - found === hpijs-2.1.4 depends on shared library: jpeg.9 - found === hpijs-2.1.4 depends on shared library: cups.2 - found === Generating temporary packing list === Checking if print/hpijs already installed test -z /usr/local/bin || /usr/ports/print/hpijs/work/hpijs-2.1.4/ install-sh -d /usr/local/bin install -s -o root -g wheel -m 555 'hpijs' '/usr/local/bin/hpijs' test -z /usr/local/bin || /usr/ports/print/hpijs/work/hpijs-2.1.4/ install-sh -d /usr/local/bin install -o root -g wheel -m 555 'foomatic-rip' '/usr/local/bin/ foomatic-rip' /usr/ports/print/hpijs/work/hpijs-2.1.4/install-sh -d /usr/local/ share/ppd/HP rm -f /usr/local/share/ppd/HP/HP*.ppd* rm -f /usr/local/share/ppd/HP/hp*.ppd* install -o root -g wheel -m 444 ppd/* /usr/local/share/ppd/HP gzip -f /usr/local/share/ppd/HP/* gzip: /usr/local/share/ppd/HP/fax is a directory -- ignored *** Error code 2 Stop in /usr/ports/print/hpijs/work/hpijs-2.1.4. *** Error code 1 Stop in /usr/ports/print/hpijs. *** Error code 1 Stop in /usr/ports/print/hpijs. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/ portinstall922.0 make reinstall ** Fix the installation problem and try again. ** Listing the failed packages (*:skipped / !:failed) ! print/hpijs (install error) --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed /snip hpijsInstall.txt.bz2 Description: Binary data ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port for Perl modules
Nikolas Britton wrote: On 7/14/06, Gerard Seibert [EMAIL PROTECTED] wrote: Sorry if I asked this before, but does anyone know if there is a port for the following Perl modules: 1) Net-SMTP-SSL 2) Bundle Libnet http://www.freebsd.org/cgi/ports.cgi?query=p5stype=all That was probably the first thing I did. Unfortunately, the ports tree does not list Perl modules as they are listen on CPAN. Consequently, finding the exact module can sometimes be a challenge. In this particular case, I have not been able to isolate either of the two modules list above. I find it hard to believe that neither of them has been ported however, especially since so many obscure modules do reside in the ports tree. -- Gerard Seibert [EMAIL PROTECTED] Why does the bride always wear white? Because it is good for the dishwasher to match the stove and refrigerator. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port for Perl modules
On 7/15/06, Gerard Seibert [EMAIL PROTECTED] wrote: Nikolas Britton wrote: On 7/14/06, Gerard Seibert [EMAIL PROTECTED] wrote: Sorry if I asked this before, but does anyone know if there is a port for the following Perl modules: 1) Net-SMTP-SSL 2) Bundle Libnet http://www.freebsd.org/cgi/ports.cgi?query=p5stype=all That was probably the first thing I did. Unfortunately, the ports tree does not list Perl modules as they are listen on CPAN. Consequently, finding the exact module can sometimes be a challenge. In this particular case, I have not been able to isolate either of the two modules list above. I find it hard to believe that neither of them has been ported however, especially since so many obscure modules do reside in the ports tree. I donno... try: http://www.freebsd.org/cgi/url.cgi?ports/mail/p5-Net-SMTP-TLS/pkg-descr http://www.freebsd.org/cgi/url.cgi?ports/net/libnet10/pkg-descr -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port for Perl modules
On Sat, 15 Jul 2006, Gerard Seibert wrote: Nikolas Britton wrote: On 7/14/06, Gerard Seibert [EMAIL PROTECTED] wrote: Sorry if I asked this before, but does anyone know if there is a port for the following Perl modules: 1) Net-SMTP-SSL 2) Bundle Libnet http://www.freebsd.org/cgi/ports.cgi?query=p5stype=all That was probably the first thing I did. Unfortunately, the ports tree does not list Perl modules as they are listen on CPAN. Consequently, finding the exact module can sometimes be a challenge. In this particular case, I have not been able to isolate either of the two modules list above. I find it hard to believe that neither of them has been ported however, especially since so many obscure modules do reside in the ports tree. The names are formatted a little differently, but they seem to be consistent. CPAN's Net::SMTP would be p5-Net-SMTP in ports. Replace the double colon with a dash; the search will work without the p5. You can use CPAN directly, of course; the main reason not to is the ports make updating and deinstalling easier. There's also CPANPLUS (/usr/ports/devel/p5-CPANPLUS) which is supposed to be the new way to deal with CPAN, at least for the non-FreeBSD world. I haven't tried it. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SMP, KDE3 and OpenOffice
Dear All, I'm trying to set up FreeBSD on my box, which has an Intel D945GNT motherboard, two 3.2GHz processors, 1GB memory. The system installs OK and I've been able to use cvsup to upgrade everything, remake the kernel (for SMP), build OpenOffice.org 2.0.2 KDE 3.5. However, three problems remain unsolved in spite of all of these things: 1. Only one processor seems to be used. The output from top -S is: PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 11 root 1 171 52 0K 8K CPU1 0 0:00 99.02% idle: cpu1 12 root 1 171 52 0K 8K RUN0 139:40 98.34% idle: cpu0 2. KDE 3.5 does not like to run any screensaver. They all run OK on test, and if I run the actual programs themselves, there is no problem. However, KDE will not start them up automatically. 3. OpenOffice.org does not like any of the files produced from anywhere else. I have stuff written in StarOffice 5.2 and in MS Word, but none of these will open. Even stuff written using OpenOffice.org 2 on a MS system is not acceptable. The error is always General I/O Error. OpenOffice will read files that it has written quite OK and permissions, ownership, etc all seem to be OK. Neither the KDE nor the OpenOffice problem has altered by upgrading these two systems and the SMP problem is also the same as with the GENERIC kernel. uname -a gives: FreeBSD grandpa.connect-a.com.au 6.1-RELEASE-p3 FreeBSD 6.1-RELEASE-p3 #0: Sat Jul 15 16:46:44 EST 2006 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/SMP i386 Any pointers to any of these problems would be most welcome. Thank you. Cheers, Rob Hurle (It's called grandpa temporarily - it'll take the place of the real grandpa when it's ready ;-) - Rob Hurle Faculty of Asian Studies, ANU Home address and contacts: Tel: +61 2 6247 2397 PO Box 4013Fax: +61 2 6247 2397 AinslieCell phone: 0417 293 603 Australia e-mail: [EMAIL PROTECTED] - ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
