binary upgrade problems (8.1-RELEASE-p5 - 8.2-RELEASE-p3)
I'm having some problems after doing a: freebsd-update -r 8.2-RELEASE upgrade (I had also done an upgrade from 8.1-p5 to p6 without rebooting; not sure if that's part of the problem). I did the update, merged the config files, ran freebsd-update install, rebooted, and then ran freebsd-update install; despite /boot/kernel and /boot/kernel.old both having a recently updated kernel, one which has FreeBSD 8.2-RELEASE-p3 #0: Tue Sep 27 18:45:57 UTC 2011 if I run strings on it, uname and sysctl report 8.1-RELEASE-p5 FreeBSD 8.1-RELEASE-p5 #0: Tue Sep 27 16:49:00 UTC 2011 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 As you can see, I'm just running the generic kernel. The system boots and most services run, though ipfw isn't loading because of the kernel version mismatch. Trying to either rollback or re-upgrade using freebsd-update isn't working (the update list it builds is wrong -- specifically, the fetch_make_patchlist() function isn't working right and is missing the filenames, so it wants to delete all my files). Any thoughts on the simplest way to get everything synced up and happy again without doing a binary upgrade from sysinstall? kernel and kernel.old are currently the same thing; I did try doing a nextboot -k kernel.old, but that doesn't change anything. If it matters, my first reboot after the upgrade was to single user mode (to do a fsck) rather than standard - wondering if this prevented some automatic thing that happens on the first boot after the binary upgrade from running It has been rebooted normally several times since then, though. I've tried moving /var/db/freebsd-update out of the way and re-creating it, but that didn't help (I've since moved the old one back). w ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: binary upgrade problems (8.1-RELEASE-p5 - 8.2-RELEASE-p3)
Sorry for the self-follow-up, but I did eventually fix it - I thought I had tried this already, but the machine seems to have been booting from the inactive component of a gmirror array; doing a gmirror forget gm0 and a reboot fixed the problem. w ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
7.0-RELEASE Upgrade problems
I'm new to FreeBSD and installed a base 7.0-RELEASE system and have been running it for a while with ZFS and gmirror partitions. I've never updated since install, so I'm attempting to do so now, but I'm having no luck. I'm following the upgrade instructions in the 7.2-RELEASE release notes, but I get an error I don't know what to do with. I'm doing: # freebsd-update upgrade -r 7.2-RELEASE Answer a few questions # freebsd-update install Installing updates...chflags: ///usr/bin/CC: Operation not supported I tried updating to the latest 7.0-RELEASE thinking there was a fix, but got: # freebsd-update fetch Answer a few questions # freebsd-update install Installing updates...chflags: ///usr/bin/dig: Operation not supported Am I doing something wrong? I haven't found any reference to this error, and while being very experienced with linux systems am new (as previously stated) to FreeBSD and am not sure where to start to track this down. Does anyone have any suggestions? Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 7.0-RELEASE Upgrade problems
Rob wrote: I'm new to FreeBSD and installed a base 7.0-RELEASE system and have been running it for a while with ZFS and gmirror partitions. I've never updated since install, so I'm attempting to do so now, but I'm having no luck. I'm following the upgrade instructions in the 7.2-RELEASE release notes, but I get an error I don't know what to do with. I'm doing: # freebsd-update upgrade -r 7.2-RELEASE Answer a few questions # freebsd-update install Installing updates...chflags: ///usr/bin/CC: Operation not supported I tried updating to the latest 7.0-RELEASE thinking there was a fix, but got: # freebsd-update fetch Answer a few questions # freebsd-update install Installing updates...chflags: ///usr/bin/dig: Operation not supported Am I doing something wrong? I haven't found any reference to this error, and while being very experienced with linux systems am new (as previously stated) to FreeBSD and am not sure where to start to track this down. Does anyone have any suggestions? Rob chflags is not supported on ZFS. See this thread for possible workaround: http://forums.freebsd.org/archive/index.php/t-3786.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 7.0-RELEASE Upgrade problems
The work around in that thread did the trick. I'm ashamed I didn't find that thread myself. Thanks! Rob Brent Bloxam wrote: Rob wrote: I'm new to FreeBSD and installed a base 7.0-RELEASE system and have been running it for a while with ZFS and gmirror partitions. I've never updated since install, so I'm attempting to do so now, but I'm having no luck. I'm following the upgrade instructions in the 7.2-RELEASE release notes, but I get an error I don't know what to do with. I'm doing: # freebsd-update upgrade -r 7.2-RELEASE Answer a few questions # freebsd-update install Installing updates...chflags: ///usr/bin/CC: Operation not supported I tried updating to the latest 7.0-RELEASE thinking there was a fix, but got: # freebsd-update fetch Answer a few questions # freebsd-update install Installing updates...chflags: ///usr/bin/dig: Operation not supported Am I doing something wrong? I haven't found any reference to this error, and while being very experienced with linux systems am new (as previously stated) to FreeBSD and am not sure where to start to track this down. Does anyone have any suggestions? Rob chflags is not supported on ZFS. See this thread for possible workaround: http://forums.freebsd.org/archive/index.php/t-3786.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
After upgrade problems with many open files
Hi, After I recently update my 7.0 Freebsd Box I have now a small problem with performance and many open files. This has not een an issue before so I don't know what a nornal level is, but at the moment I have increased the kern.maxfiles from 12.000 to 60.000, and the system uses between 22.000 to 30.000 open files. On the box I is samba, MySQL (with no real activity only installed not used yet), gnome, interfaces I have I have 5 thin clients attached to this server, they get X via xdmcp from thin clienter that boots up with there own os (Elux). After the upgrade of application every thing seems to be slow, could it be related to the many open files are there other places to look for tunning I have tried to use lsof but I do'not find 2 lines when listed. Any help/guidience to solve this would be apriciated. /Klaus -- Klaus ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
upgrade problems
Hello, I have a botched upgrade from 6.3 to 7.0-release on my hands. I followed the handbook instructions, but I I think I forgot to drop into single-user mode to install the new kernel. Two relevant files: dmesg(mod).out and fstab. The fstab doesn't show that this machine has one 70gb drive and two 286gb drives, which are supposed to be in software raid 1 (duplex). The raid was broken before I started the upgrade and I was hoping that the updgrade might fix the raid. See more on gmirror below. The 'make buildworld' and 'make installkernel' went fine - see the log file 'make buildworld, buildkernel and install kernel.out' attached. There were many error messages in 'make installkernel' - see attached. The error messages are basically: kldxref /boot/kernel kldxref: file isn't dynamically-linked I see from the errata that this might be unrelated to the problems below: [20080307] Source upgrades from FreeBSD 6./X/ to FreeBSD 7.0-RELEASE will generate warnings from kldxref(8) http://www.FreeBSD.org/cgi/man.cgi?query=kldxrefsektion=8manpath=FreeBSD+7.0-stable during the installkernel step. These warnings are harmless and can be ignored. Dropping into single-user mode per handbook 24.4.5, I received these error messages: # fsck -p /dev/ad0s1a: NO WRITE ACCESS /dev/ad0s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. The attached file fsck2.out is the output from fsck. On reboot, there was a kernel panic. I tried to use dumpon but the crash occurred too early in the boot process. Here are the error messages transcribed by hand: ad0ata0master ad1ata0slave acd0 cdrwata1 master ad3 ata1 ata1 slave geom_mirror: component ad3 (device gm0) broken, skipping geom_mirror: device mirror /gm0 launched 1/2 geom_mirror: upgrading metadata on ad3 (v3 - v4) fatal trap 12: page fault while in kernel mode [misc error messages] panic panic: page fault cpuid=0 I can reboot in safe mode. Here is the boot sequence text in safe mode: ad3: 286,168 MB at ata1_slave PI04 geom_mirror: component ad3 (device gm0) broken, skipping geom_mirror: device mirror/gm0 launched (1/2) geom_mirror: upgrading metadata on ad3 (v3 - v4) geom_mirror: cannot write metadata on ad3 (device=gm0) geom_mirror: cannot update metadata on disk ad3 (error=1) trying to mount root from ufs: /dev/ad0s1a [etc] I can't proceed further with the installation nor can I mount disks in single-user mode: #make installworld make: don't know how to make installworld. Stop I can't re-do the 'make buildworld' sequence - see error messages in makeworld_b.out, attached. In trying to clean up the duplex, gmirror is now giving me the following message: server# gmirror remove gm0 ad3 Userland and kernel parts are out of sync. server# exit Blech. I've floundered about without success. How can I clean up this mess? All comments and thoughts welcome. I have not tried a binary upgrade. Will re-install but as a last option. Many thanks, Cam Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-RELEASE-p5 #0: Tue Oct 14 10:16:32 CDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.00GHz (1993.54-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf24 Stepping = 4 Features=0x3febfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real memory = 536608768 (511 MB) avail memory = 511205376 (487 MB) ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Oct 14 2008 10:15:55) cpu0 on motherboard p4tcc0: CPU Frequency Thermal Control on cpu0 pcib0: Host to PCI bridge pcibus 0 on motherboard pir0: PCI Interrupt Routing Table: 10 Entries on motherboard pci0: PCI bus on pcib0 agp0: Intel 82845 host to AGP bridge on hostb0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 vgapci0: VGA-compatible display mem 0xfd00-0xfdff,0xe800-0xefff irq 5 at device 0.0 on pci1 pcib2: PCIBIOS PCI-PCI bridge at device 30.0 on pci0 pci2: PCI bus on pcib2 [snipped ohci0, usb0, uhub0, ohci1, usb1, uhub1, ohci2, usb2, uhub2, ehci0, usb3, uhub3] rl0: RealTek 8139 10/100BaseTX port 0xd800-0xd8ff mem 0xfeaff800-0xfeaff8ff irq 11 at device 10.0 on pci2 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface PHY 0 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:c0:a8:7b:f6:77 rl0: [ITHREAD] isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH2 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0 ata0: ATA channel 0 on atapci0 ata0:
Re: libcdio upgrade problems
Thank you :-) Unfortunatly I took someone elses advice and upgraded to 7.0, which created it's own problem :-( But the libcdio thing did get fixed, at least! Jen --- On Wed, 6/18/08, Lowell Gilbert [EMAIL PROTECTED] wrote: From: Lowell Gilbert [EMAIL PROTECTED] Subject: Re: libcdio upgrade problems To: Dr. Jennifer Nussbaum [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Date: Wednesday, June 18, 2008, 12:57 PM Dr. Jennifer Nussbaum [EMAIL PROTECTED] writes: Lowell Gilbert [EMAIL PROTECTED] wrote: Dr. Jennifer Nussbaum writes: Im trying to upgrade some ports, and have a problem with libcdio. At least i think i do. When i try to upgrade, say, Nautilus (or a buncha other things), it dies in the end with a libcdio-0.78.2_2 is already installed. You may wish to make deinstall etc. message. But i did go to /usr/ports/sysytils/libcdio and make deinstall and make reinstall, and this was successful. I sync'd the ports collection again, but no luck. Nothing in UPDATING about this. Sounds like the dependencies are confused. pkgdb(1) may help with that. If not, the brute force approach would be to remove the affected ports all the way back to (and including) libcdio, and build them over. I havent been able to figure out how to fix things with pkgdb. And i have tried, over and over, to remove the affected ports and build them from scratch but it hasnt been working. So i went to libcdio and did a make deinstall, deleted the work files, and did a make install clean, and it installed fine. Then i tried to build gvfs, also by doing a make install clean, and it died in the same way--telling me to make deinstall and make reinstall of libcdio. Ive tried this several times with no luck. If theres an even more brute force way id like to know what it is so i can do that. This is preventing a lot of other upgrades to GNOME, which i need. I found it. I think you need to reset the options on libcdio to re-enable the cdparanoia option. Some gnome ports seem to depend on the library specifically with the paranoia option, and I've seen some systems get the options jammed. Something like: (cd /usr/ports/sysutils/libcdio ; make rmconfig ; portupgrade -f libcdio) -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libcdio upgrade problems
Dr. Jennifer Nussbaum [EMAIL PROTECTED] writes: Lowell Gilbert [EMAIL PROTECTED] wrote: Dr. Jennifer Nussbaum writes: Im trying to upgrade some ports, and have a problem with libcdio. At least i think i do. When i try to upgrade, say, Nautilus (or a buncha other things), it dies in the end with a libcdio-0.78.2_2 is already installed. You may wish to make deinstall etc. message. But i did go to /usr/ports/sysytils/libcdio and make deinstall and make reinstall, and this was successful. I sync'd the ports collection again, but no luck. Nothing in UPDATING about this. Sounds like the dependencies are confused. pkgdb(1) may help with that. If not, the brute force approach would be to remove the affected ports all the way back to (and including) libcdio, and build them over. I havent been able to figure out how to fix things with pkgdb. And i have tried, over and over, to remove the affected ports and build them from scratch but it hasnt been working. So i went to libcdio and did a make deinstall, deleted the work files, and did a make install clean, and it installed fine. Then i tried to build gvfs, also by doing a make install clean, and it died in the same way--telling me to make deinstall and make reinstall of libcdio. Ive tried this several times with no luck. If theres an even more brute force way id like to know what it is so i can do that. This is preventing a lot of other upgrades to GNOME, which i need. I found it. I think you need to reset the options on libcdio to re-enable the cdparanoia option. Some gnome ports seem to depend on the library specifically with the paranoia option, and I've seen some systems get the options jammed. Something like: (cd /usr/ports/sysutils/libcdio ; make rmconfig ; portupgrade -f libcdio) -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libcdio upgrade problems
Im trying to upgrade some ports, and have a problem with libcdio. At least i think i do. When i try to upgrade, say, Nautilus (or a buncha other things), it dies in the end with a libcdio-0.78.2_2 is already installed. You may wish to make deinstall etc. message. But i did go to /usr/ports/sysytils/libcdio and make deinstall and make reinstall, and this was successful. I sync'd the ports collection again, but no luck. Nothing in UPDATING about this. Thanks! I've run into similar experiences with other ports, and what I have done to get it to work is to deinstall the complaining port (in this instance libcdio), and let the original port install it as a dependency instead of doing a make reinstall. -- Im afraid this didnt work either--whether libcdio is installed or not (and installing it seems to work fine), any other port that requires it tells me that it is installed and need to be make deinstalled and make reinstalled. Yet this doesnt work. Is there any other brute-force way to get around this? This is getting difficult. Thanks again, everyone. Jen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libcdio upgrade problems
Dr. Jennifer Nussbaum [EMAIL PROTECTED] writes: Im trying to upgrade some ports, and have a problem with libcdio. At least i think i do. When i try to upgrade, say, Nautilus (or a buncha other things), it dies in the end with a libcdio-0.78.2_2 is already installed. You may wish to make deinstall etc. message. But i did go to /usr/ports/sysytils/libcdio and make deinstall and make reinstall, and this was successful. I sync'd the ports collection again, but no luck. Nothing in UPDATING about this. Sounds like the dependencies are confused. pkgdb(1) may help with that. If not, the brute force approach would be to remove the affected ports all the way back to (and including) libcdio, and build them over. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libcdio upgrade problems
Lowell Gilbert [EMAIL PROTECTED] wrote: Dr. Jennifer Nussbaum writes: Im trying to upgrade some ports, and have a problem with libcdio. At least i think i do. When i try to upgrade, say, Nautilus (or a buncha other things), it dies in the end with a libcdio-0.78.2_2 is already installed. You may wish to make deinstall etc. message. But i did go to /usr/ports/sysytils/libcdio and make deinstall and make reinstall, and this was successful. I sync'd the ports collection again, but no luck. Nothing in UPDATING about this. Sounds like the dependencies are confused. pkgdb(1) may help with that. If not, the brute force approach would be to remove the affected ports all the way back to (and including) libcdio, and build them over. I havent been able to figure out how to fix things with pkgdb. And i have tried, over and over, to remove the affected ports and build them from scratch but it hasnt been working. So i went to libcdio and did a make deinstall, deleted the work files, and did a make install clean, and it installed fine. Then i tried to build gvfs, also by doing a make install clean, and it died in the same way--telling me to make deinstall and make reinstall of libcdio. Ive tried this several times with no luck. If theres an even more brute force way id like to know what it is so i can do that. This is preventing a lot of other upgrades to GNOME, which i need. Thanks! Jen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libcdio upgrade problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dr. Jennifer Nussbaum wrote: | | Lowell Gilbert [EMAIL PROTECTED] wrote: Dr. Jennifer Nussbaum writes: | | Im trying to upgrade some ports, and have a problem with libcdio. At least i | think i do. | | When i try to upgrade, say, Nautilus (or a buncha other things), it dies in the | end with a libcdio-0.78.2_2 is already installed. You may wish to make deinstall | etc. message. | | But i did go to /usr/ports/sysytils/libcdio and make deinstall and make reinstall, | and this was successful. I sync'd the ports collection again, but no luck. Nothing | in UPDATING about this. | | Sounds like the dependencies are confused. pkgdb(1) may help with | that. If not, the brute force approach would be to remove the | affected ports all the way back to (and including) libcdio, and build | them over. | I havent been able to figure out how to fix things with pkgdb. And i have tried, over and over, to remove the affected ports and build them from scratch but it hasnt been working. | | So i went to libcdio and did a make deinstall, deleted the work files, and did a make install clean, and it installed fine. Then i tried to build gvfs, also by doing a make install clean, and it died in the same way--telling me to make deinstall and make reinstall of libcdio. | | Ive tried this several times with no luck. If theres an even more brute force way id like to know what it is so i can do that. This is preventing a lot of other upgrades to GNOME, which i need. Not to point out the obvious, but you're sure your port tree is up-to-date? | | Thanks! | | Jen | | | ___ | freebsd-questions@freebsd.org mailing list | http://lists.freebsd.org/mailman/listinfo/freebsd-questions | To unsubscribe, send any mail to [EMAIL PROTECTED] - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkhOjCcACgkQwMJqmJVx944niQCeMNdtOQOfePqCiys0RFK1xg20 nnMAnRpHOqMO4BiSTpO+KY5ZBuRPT1Ok =nNAK -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libcdio upgrade problems
Pietro Cerutti [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dr. Jennifer Nussbaum wrote: | | Lowell Gilbert wrote: Dr. Jennifer Nussbaum writes: | | Im trying to upgrade some ports, and have a problem with libcdio. At least i | think i do. | | When i try to upgrade, say, Nautilus (or a buncha other things), it dies in the | end with a libcdio-0.78.2_2 is already installed. You may wish to make deinstall | etc. message. | | But i did go to /usr/ports/sysytils/libcdio and make deinstall and make reinstall, | and this was successful. I sync'd the ports collection again, but no luck. Nothing | in UPDATING about this. | | Sounds like the dependencies are confused. pkgdb(1) may help with | that. If not, the brute force approach would be to remove the | affected ports all the way back to (and including) libcdio, and build | them over. | I havent been able to figure out how to fix things with pkgdb. And i have tried, over and over, to remove the affected ports and build them from scratch but it hasnt been working. | | So i went to libcdio and did a make deinstall, deleted the work files, and did a make install clean, and it installed fine. Then i tried to build gvfs, also by doing a make install clean, and it died in the same way--telling me to make deinstall and make reinstall of libcdio. | | Ive tried this several times with no luck. If theres an even more brute force way id like to know what it is so i can do that. This is preventing a lot of other upgrades to GNOME, which i need. Not to point out the obvious, but you're sure your port tree is up-to-date? Yes as i said in my first post i resynced ports before this, and just did it again to make sure. No changes to this port or any of the others involved. Jen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libcdio upgrade problems
Dr. Jennifer Nussbaum wrote: Hi, Im trying to upgrade some ports, and have a problem with libcdio. At least i think i do. When i try to upgrade, say, Nautilus (or a buncha other things), it dies in the end with a libcdio-0.78.2_2 is already installed. You may wish to make deinstall etc. message. But i did go to /usr/ports/sysytils/libcdio and make deinstall and make reinstall, and this was successful. I sync'd the ports collection again, but no luck. Nothing in UPDATING about this. Thanks! Jen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I've run into similar experiences with other ports, and what I have done to get it to work is to deinstall the complaining port (in this instance libcdio), and let the original port install it as a dependency instead of doing a make reinstall. Best regards, Greg Groth ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
libcdio upgrade problems
Hi, Im trying to upgrade some ports, and have a problem with libcdio. At least i think i do. When i try to upgrade, say, Nautilus (or a buncha other things), it dies in the end with a libcdio-0.78.2_2 is already installed. You may wish to make deinstall etc. message. But i did go to /usr/ports/sysytils/libcdio and make deinstall and make reinstall, and this was successful. I sync'd the ports collection again, but no luck. Nothing in UPDATING about this. Thanks! Jen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
gettext upgrade problems
Hi, As a result of the upgrade to gettext-0.16.1, I am rebuilding ports on a desktop machine. I received an error with the port OpenEXR after hours of rebuilding the ports. My first question is what caused the OpenEXR port to fail and most importantly do I have to restart building all the ports over because of this failure. Initial portmaster command was portmaster -Gv -B -u -d -r gettext Any help would be very much appreciated. v/r Derrick then mv -f .deps/ImfChannelListAttribute.Tpo .deps/ImfChannelListAttribute.Plo; else rm -f .deps/ImfChannelListAttribute.Tpo; exit 1; fi c++ -DHAVE_CONFIG_H -I. -I. -I../config -I.. -I../Half -I../Iex -I../Imath -I../IlmThread -I../config -pipe -O2 -fno-strict-aliasing -pipe -D_THREAD_SAFE -MT ImfChannelListAttribute.lo -MD -MP -MF .deps/ImfChannelListAttribute.Tpo -c ImfChannelListAttribute.cpp -fPIC -DPIC -o .libs/ImfChannelListAttribute.o c++ -DHAVE_CONFIG_H -I. -I. -I../config -I.. -I../Half -I../Iex -I../Imath -I../IlmThread -I../config -pipe -O2 -fno-strict-aliasing -pipe -D_THREAD_SAFE -MT ImfChannelListAttribute.lo -MD -MP -MF .deps/ImfChannelListAttribute.Tpo -c ImfChannelListAttribute.cpp -o ImfChannelListAttribute.o /dev/null 21 gmake[1]: *** [ImfChannelListAttribute.lo] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/OpenEXR/work/openexr-1.4.0/IlmImf' gmake: *** [all-recursive] Error 1 *** Error code 2 Stop in /usr/ports/graphics/OpenEXR. === make failed for graphics/OpenEXR === Aborting update === Update for OpenEXR-1.2.2_1 failed === Aborting update === Update for kdelibs-3.5.6 failed === Aborting update === Update for kdebase-kompmgr-3.5.6 failed === Aborting update === Update for kdebase-3.5.6 failed === Aborting update === Update for amarok-1.4.5_3 failed === Aborting update ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gettext upgrade problems
Dantavious wrote: Hi, As a result of the upgrade to gettext-0.16.1, I am rebuilding ports on a desktop machine. I received an error with the port OpenEXR after hours of rebuilding the ports. My first question is what caused the OpenEXR port to fail and most importantly do I have to restart building all the ports over because of this failure. Initial portmaster command was portmaster -Gv -B -u -d -r gettext Any help would be very much appreciated. v/r Derrick then mv -f .deps/ImfChannelListAttribute.Tpo .deps/ImfChannelListAttribute.Plo; else rm -f .deps/ImfChannelListAttribute.Tpo; exit 1; fi c++ -DHAVE_CONFIG_H -I. -I. -I../config -I.. -I../Half -I../Iex -I../Imath -I../IlmThread -I../config -pipe -O2 -fno-strict-aliasing -pipe -D_THREAD_SAFE -MT ImfChannelListAttribute.lo -MD -MP -MF .deps/ImfChannelListAttribute.Tpo -c ImfChannelListAttribute.cpp -fPIC -DPIC -o .libs/ImfChannelListAttribute.o c++ -DHAVE_CONFIG_H -I. -I. -I../config -I.. -I../Half -I../Iex -I../Imath -I../IlmThread -I../config -pipe -O2 -fno-strict-aliasing -pipe -D_THREAD_SAFE -MT ImfChannelListAttribute.lo -MD -MP -MF .deps/ImfChannelListAttribute.Tpo -c ImfChannelListAttribute.cpp -o ImfChannelListAttribute.o /dev/null 21 gmake[1]: *** [ImfChannelListAttribute.lo] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/OpenEXR/work/openexr-1.4.0/IlmImf' gmake: *** [all-recursive] Error 1 *** Error code 2 Stop in /usr/ports/graphics/OpenEXR. === make failed for graphics/OpenEXR === Aborting update === Update for OpenEXR-1.2.2_1 failed === Aborting update === Update for kdelibs-3.5.6 failed === Aborting update === Update for kdebase-kompmgr-3.5.6 failed === Aborting update === Update for kdebase-3.5.6 failed === Aborting update === Update for amarok-1.4.5_3 failed === Aborting update ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I have same problem: cc -DHAVE_CONFIG_H -I. -I. -I.. -DG_LOG_DOMAIN=\GLib-GObject\ -I.. -I../glib -I.. -DG_DISABLE_CAST_CHECKS -DG_DISABLE_DEPRECATED -DGOBJECT_COMPILATION -DG_DI SABLE_CONST_RETURNS -I/usr/local/include -D_REENTRANT -O2 -fno-strict-aliasing - pipe -Wall -MT gparam.lo -MD -MP -MF .deps/gparam.Tpo -c gparam.c -fPIC -DPIC - o .libs/gparam.o cc -DHAVE_CONFIG_H -I. -I. -I.. -DG_LOG_DOMAIN=\GLib-GObject\ -I.. -I../glib -I.. -DG_DISABLE_CAST_CHECKS -DG_DISABLE_DEPRECATED -DGOBJECT_COMPILATION -DG_DI SABLE_CONST_RETURNS -I/usr/local/include -D_REENTRANT -O2 -fno-strict-aliasing - pipe -Wall -MT gparam.lo -MD -MP -MF .deps/gparam.Tpo -c gparam.c -o gparam.o / dev/null 21 gmake[3]: *** [gparam.lo] Error 1 gmake[3]: se sale del directorio `/usr/ports/devel/glib20/work/glib-2.12.11/gobj ect' gmake[2]: *** [all] Error 2 gmake[2]: se sale del directorio `/usr/ports/devel/glib20/work/glib-2.12.11/gobj ect' gmake[1]: *** [all-recursive] Error 1 gmake[1]: se sale del directorio `/usr/ports/devel/glib20/work/glib-2.12.11' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/devel/glib20. === make failed for devel/glib20 === Aborting update === Update for glib-2.12.11 failed === Aborting update === Update for ORBit2-2.14.7 failed === Aborting update -- PGP KeyID: 0xC730A079 Key fingerprint = F626 3C47 02F5 E43C 6620 8A1B E7A8 533B C730 A079 gpg --keyserver pgp.mit.edu --recv-keys C730A079 /\ \ /ASCII Ribbon Campaign X against HTML e-mail vCards / \ signature.asc Description: OpenPGP digital signature
Re: gettext upgrade problems
On Sun, 25 Mar 2007 10:46:06 -0400 Dantavious [EMAIL PROTECTED] wrote: Hi, As a result of the upgrade to gettext-0.16.1, I am rebuilding ports on a desktop machine. I received an error with the port OpenEXR after hours of rebuilding the ports. My first question is what caused the OpenEXR port to fail and most importantly do I have to restart building all the ports over because of this failure. Initial portmaster command was portmaster -Gv -B -u -d -r gettext What I would suggest you do is pkg_delete gettext, and do a pkg_add of the old version (you might need to use a release branch, if you're tracking stable), and then use *portupgrade* to rebuild just gettext. This wont solve your build problem, but it it will prevent your system becoming flakey and then failing to boot into a working desktop, as happened to me. Portupgrade, unlike portmaster, preserves a copy of old libraries, so software build against the old version will continue to work. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
package upgrade problems
Lately I have been having a lot of trouble installing packages from the FreeBSD packages-6-stable packages collection. Often it ends with error messages like this: portupgrade -PP -R -N inkscape --- Skipping 'x11-toolkits/libgnomeprintui' (libgnomeprintui-2.10.2) because a requisite package 'libgnomecanvas-2.12.0' (graphics/libgnomecanvas) failed (specify -k to force) --- Skipping 'textproc/gtkspell2' (gtkspell2-2.0.10_1) because a requisite package 'gtk-2.8.9' (x11-toolkits/gtk20) failed (specify -k to force) --- Skipping 'graphics/inkscape' because a requisite port 'devel/gconf2' failed (specify -k to force) ** Listing the failed packages (*:skipped / !:failed) ! x11-toolkits/gtk20 (gtk-2.8.9) (package not found) * devel/gconf2 (gconf2-2.12.1) * devel/gnomevfs2 (gnomevfs2-2.12.2) * misc/gnome-icon-theme (gnome-icon-theme-2.12.1_2) * devel/libglade2 (libglade2-2.5.1_3) ! print/libgnomeprint (libgnomeprint-2.10.3_1) (package not found) * graphics/libgnomecanvas (libgnomecanvas-2.12.0) * x11-toolkits/libgnomeprintui (libgnomeprintui-2.10.2) * textproc/gtkspell2 (gtkspell2-2.0.10_1) * graphics/inkscape --- Packages processed: 0 done, 54 ignored, 8 skipped and 2 failed Apparently, some of the packages that inkscape depends on have not been built yet, or, these dependancy packages have been deleted and replaced with new versions, but inkscape has not been rebuilt yet to use them and requires the old versions still. I have a brilliant solution to this problem. Why not simply rebuild all prerequisite packages before rebuilding the package that depends on them? Also, when building a new version of a library package for instance, in addition to placing the new version on ftp, also leave the old version there, if the old version is still being used by a another package that has not been rebuilt yet to use the new version. This would prevent new packages from being installed and replacing older packages until all dependancies have been built, and would also make sure that when a dependancy is rebuilt, the old version of the dependancy remians as well for any packages that have not been rebuilt yet to use the new version of the dependancy. This means that multiple versions of the same dependancy would be present in the FTP directory, until the old version is no longer need by any other packages. __ 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]
Subversion upgrade problems (1.1.3 to 1.2.0)
I have been running subversion 1.1.3 for about a month with no problems. I just upgraded to 1.2.0 and now I can't connect the the server anymore. I am using svnserve on FreeBSD 5.4. When I try and connect, I get: svn: Can't connect to host 'xx.net': Connection refused I have tried connecting from my XP machine and from the local machine and I get the same error. I can connect from the local machine using file://. I have tried creating a new repository and a new project to make sure it is not a compatibility issue with my 1.1.3 repositories, but I get the same error. I've tried anon-access as well as auth-access with the same results. I have verified that the server is running (via ps). I can't see any place that svnserve is writing error logs. I am starting svnserve via: svnserve -d -r /home/svn/repository I've tried running svnserve using --foreground and nothing is printed to the screen. I sounds like the connection is never even getting to svnserve. Did something change from 1.1.3? Port? Nothing has changed on the machine. It was working. I upgraded (using ports) and now it doesn't work. Any suggestions? Ron ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
xorg/dri-6.2_1,2 upgrade problems
On 12/30/04 22:18:32, Ned Harrison wrote: The upgrade to 5.3 fixed the Dri build problems. Thanks for the hint, Jason. It is much appreciated. I had to run xorgconfig to make a new config file in order to get the X server going again. My kde desktop keeps crashing but the Windowmaker desktop I installed runs. It doesn't run perfectly but at least I know X works.I will try using the force switch on portupdate to redo those ports I originally I upgraded in 5.2.As for your p pro question. It must be a default in some makefile. I'm too much of a newbie to even know what p pro is. :-) Sorry about not including the prior message. But I'm still working off a Knoppix disk. Thanks Ned ___ freebsd-questions at freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- unsubscribe at freebsd.org Your'e welcome. I think you have somethings not fully upgraded to have some of those problems. I hear it is kind of a comman problem with big ports like kde for some of the dependancies not to be built. Portmanager is a new program I have found and like it. It is not as full featured as portupgrade, but it is nice. Install it, it is a very quick compile, less than a min. Then run portmanager -s | grep OLD as root. It ill tell you everything that is out of date, be sure to cvsup ports and cd /usr/ports make fetchindex first. Did you rebuild x after you update to 5.3? You will need to. Try portupgrade -fRr xorg. If you want to optimize you programs have a look at /etc/make.conf. You can check out /usr/share/example/make.conf first. The p pro stands for pentium pro. It is very old, pre pII. It is also a default setting to optimise for that can help most modern x86 processors. If you want to set some make options here is mine, note you may need to change the processor type. CPUTYPE=athlon-xp CFLAGS= -O2 -pipe -fschedule-insns2 -fomit-frame-pointer -funroll-loops COPTFLAGES=-O2 -pipe -funroll-loops -fschedule-insns2 It turned out to be the kdemultimedia package. It would not update nor could I build it from the ports. I wiped it out with pkg_delete -f. Can't play my tunes but I'm back on line! :-) Jason, Thanks again for the hints. Ned ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg/dri-6.2_1,2 upgrade problems
On Mon, Jan 03, 2005 at 07:49:43PM +, Ned Harrison wrote: CPUTYPE=athlon-xp CFLAGS= -O2 -pipe -fschedule-insns2 -fomit-frame-pointer -funroll-loops COPTFLAGES=-O2 -pipe -funroll-loops -fschedule-insns2 It turned out to be the kdemultimedia package. It would not update nor could I build it from the ports. I wiped it out with pkg_delete -f. Can't play my tunes but I'm back on line! :-) This is usually because of a conflict with some other already-installed piece of software (perhaps even an earlier version of kde or one of its support library). The way to fix it is to: * Carefully check /usr/ports/UPDATING and follow relevant advice * Make sure all installed ports are up-to-date (portupgrade -a) * Make sure that you don't have random stale files installed (see pkg_which(1)) Kris pgpTf2Qy6PXid.pgp Description: PGP signature
xorg/dri-6.2_1,2 upgrade problems
Thanks again. I'll try the portmanager. I read through a discussion of it in freebsd-questions, but didn't have a command example to try. (Thanks for your command suggestion for portmanager.) For portupgrade I have paper copies of the man page and paper copy of an article which I cross reference before running it. You are right on dependencies not being built. I had to pkg_delete qt and rebuild it from ports in order to upgrade kde. Before seeing your message I ran portupgrade on xorg using the -frR switch. X seams to be working now, somewhat. I use windowmaker as the desktop windowmanager for the root. Entering the command startx as root, windowmaker starts up and looks fine. However, I can't open a terminal window in it. The default twm windowmanager crashes. No error messages go to the log but I get a line: Xauth: (argv):1 bad display name nedsbsd.cox.net:0 in list command and two others of like nature as messages after x crashes. I entered nedsbsd as a display name when I initially installed FreeBSD several months ago. I had no clue what it the install program was asking for at that time and figured I could change it later. It didn't seam to cause any problems so I neglected to change it. I generally cvsup my ports and fetch the index right before I do any upgrading. Even if it's just the next day. Never know when something new is going to pop in that could cause a make to crash. I took down the optimizations you suggested. The lines currently have no meaning to me, so I'll need to read up a bit. I've been running FreeBSD for less than a year and I've had no computer experience or training outside very basic MS windows. So many things are new and many are incomprehensible at first look. Dispite that I feel far more comfortable and secure using FreeBSD than I ever did using Windows. That's why I'll keep plugging away. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg/dri-6.2_1,2 upgrade problems
On 12/30/04 22:18:32, Ned Harrison wrote: The upgrade to 5.3 fixed the Dri build problems. Thanks for the hint, Jason. It is much appreciated. I had to run xorgconfig to make a new config file in order to get the X server going again. My kde desktop keeps crashing but the Windowmaker desktop I installed runs. It doesn't run perfectly but at least I know X works.I will try using the force switch on portupdate to redo those ports I originally I upgraded in 5.2.As for your p pro question. It must be a default in some makefile. I'm too much of a newbie to even know what p pro is. :-) Sorry about not including the prior message. But I'm still working off a Knoppix disk. Thanks Ned ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] Your'e welcome. I think you have somethings not fully upgraded to have some of those problems. I hear it is kind of a comman problem with big ports like kde for some of the dependancies not to be built. Portmanager is a new program I have found and like it. It is not as full featured as portupgrade, but it is nice. Install it, it is a very quick compile, less than a min. Then run portmanager -s | grep OLD as root. It will tell you everything that is out of date, be sure to cvsup ports and cd /usr/ports make fetchindex first. Did you rebuild x after you update to 5.3? You will need to. Try portupgrade -fRr xorg. If you want to optimize you programs have a look at /etc/make.conf. You can check out /usr/share/example/make.conf first. The p pro stands for pentium pro. It is very old, pre pII. It is also a default setting to optimise for that can help most modern x86 processors. If you want to set some make options here is mine, note you may need to change the processor type. CPUTYPE=athlon-xp CFLAGS= -O2 -pipe -fschedule-insns2 -fomit-frame-pointer -funroll-loops COPTFLAGES=-O2 -pipe -funroll-loops -fschedule-insns2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
xorg/dri-6.2_1,2 upgrade problems
The upgrade to 5.3 fixed the Dri build problems. Thanks for the hint, Jason. It is much appreciated. I had to run xorgconfig to make a new config file in order to get the X server going again. My kde desktop keeps crashing but the Windowmaker desktop I installed runs. It doesn't run perfectly but at least I know X works.I will try using the force switch on portupdate to redo those ports I originally I upgraded in 5.2.As for your p pro question. It must be a default in some makefile. I'm too much of a newbie to even know what p pro is. :-) Sorry about not including the prior message. But I'm still working off a Knoppix disk. Thanks Ned ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
xorg/dri-6.2_1,2 upgrade problems
I'm currently running Release 5.2.1. which has just reciently been updated to the security branch. I was upgrading xorg to version 6.8.1. with portupgrade when it crashed with an Error Code 1. I traced the crash to failure to upgrade dri-5.0.2,2 to dri-6.2_1,2. I've attempted to build dri-6.2_1,2 but it keeps crashing with an Error code 2. I didn't see any notes in the ports UPDATING file regarding this issue nor did I find any similar issues in the archives. I ran cvsup to update the ports this morning and done the prtsdb -Uu to creat an index. The make in dri still has the same problem. I piped my last attempt to make dri to a file. The last lines of the output are below. Sorry about the lack of additional information. My xserver crashed so i am stuck in the command line mode. I'm running my computer off Knoppix disk so I can send this information to freebsd-questions. So any suggestions on what I should do or attempt to do to get my system back up and running would be appreciated. Output of the Make command in the dri port: -mcpu=pentiumpro -DDRI_NEW_INTERFACE_ONLY -Wmissing-prototypes -g -std=c9x -Wundef -fPIC -ffast-math -I/usr/local/include -I/usr/X11R6/include -I/usr/X11R6/include/X11/extensions -DGLX_DIRECT_RENDERING i810tris.c -o i810tris.o cc -c -I. -I../../../../../src/mesa/drivers/dri/common -Iserver -I../../../../../../drm/shared -I../../../../../../drm/linux -I../../../../../include -I../../../../../include/GL/internal -I../../../../../src/mesa -I../../../../../src/mesa/main -I../../../../../src/mesa/glapi -I../../../../../src/mesa/math -I../../../../../src/mesa/transform -I../../../../../src/mesa/shader -I../../../../../src/mesa/swrast -I../../../../../src/mesa/swrast_setup -I../dri_client -I../dri_client/imports -O -pipe -mcpu=pentiumpro -DDRI_NEW_INTERFACE_ONLY -Wmissing-prototypes -g -std=c9x -Wundef -fPIC -ffast-math -I/usr/local/include -I/usr/X11R6/include -I/usr/X11R6/include/X11/extensions -DGLX_DIRECT_RENDERING i810vb.c -o i810vb.o rm -f ../../../../../lib/i810_dri.so gcc -o ../../../../../lib/i810_dri.so -shared ../../common/driverfuncs.o ../common/mm.o ../common/utils.o ../common/texmem.o ../common/vblank.o ../common/dri_util.o ../common/glcontextmodes.o ../common/xmlconfig.o i810context.o i810ioctl.o i810render.o i810screen.o i810span.o i810state.o i810tex.o i810texmem.o i810texstate.o i810tris.o i810vb.o ../../../../../src/mesa/mesa.a ../dri_client/dri.a -L/usr/local/lib -lm -lpthread -lexpat gmake[6]: Leaving directory `/usr/ports/graphics/dri/work/Mesa/src/mesa/drivers/dri/i810' gmake[5]: Leaving directory `/usr/ports/graphics/dri/work/Mesa/src/mesa/drivers/dri' gmake[4]: Leaving directory `/usr/ports/graphics/dri/work/Mesa/src/mesa' gmake[3]: Leaving directory `/usr/ports/graphics/dri/work/Mesa/src/mesa' gmake[2]: Leaving directory `/usr/ports/graphics/dri/work/Mesa/src' gmake[1]: Leaving directory `/usr/ports/graphics/dri/work/Mesa' *** Error code 2 Stop in /usr/ports/graphics/dr Thank you for your consideration, Ned ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg/dri-6.2_1,2 upgrade problems
On 12/26/04 16:16:02, Ned Harrison wrote: I'm currently running Release 5.2.1. which has just reciently been updated to the security branch. I was upgrading xorg to version 6.8.1. with portupgrade when it crashed with an Error Code 1. I traced the crash to failure to upgrade dri-5.0.2,2 to dri-6.2_1,2. I've attempted to build dri-6.2_1,2 but it keeps crashing with an Error code 2. I didn't see any notes in the ports UPDATING file regarding this issue nor did I find any similar issues in the archives. I ran cvsup to update the ports this morning and done the prtsdb -Uu to creat an index. The make in dri still has the same problem. I piped my last attempt to make dri to a file. The last lines of the output are below. Sorry about the lack of additional information. My xserver crashed so i am stuck in the command line mode. I'm running my computer off Knoppix disk so I can send this information to freebsd-questions. So any suggestions on what I should do or attempt to do to get my system back up and running would be appreciated. Output of the Make command in the dri port: Part of the dri stuff(the drivers) are in the base system and not upgraded with the dri port(I think). That could be causing you pain, but the more likely cause may be that pthread and other libs. In 5.3 some of the libs were bumped and there have been threading changes. Maybe you should update your system too? BTW, do you have a p pro, or is that some default in some makefile? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Upgrade problems
sorry, I didnt change rc.conf. It has to be something related to kernel , cause it didnt work only after upgrade (even with generic kernel, it doesnt work) thanks _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgrade problems
Does anyone here had recently updated succecefully to -stable ?? Cause i'm trying for 5 days now, and i cant... All the update process runs well, except the boot, that runs normally to: Mounting NFS file systems:. after these, it blocks, ctrl-c and ctrl-t doesnt work, i have to force halt... no one with these same problem ?? It's impossible, i've updated 6 times _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade problems
On Monday 06 December 2004 01:21 pm, Marta Resende wrote: Does anyone here had recently updated succecefully to -stable ?? Cause i'm trying for 5 days now, and i cant... All the update process runs well, except the boot, that runs normally to: Mounting NFS file systems:. after these, it blocks, ctrl-c and ctrl-t doesnt work, i have to force halt... no one with these same problem ?? It's impossible, i've updated 6 times Which stable? 5-stable requires NFSCLIENT and 4-stable requires NFS. Did you update your kernel config file before you built your new kernel. Upgrades with old config's are bound to cause problems. I have NFS built into both 4-stable and 5-stable. They boot without any problems. I also as a matter of principal don't permit auto mounts of nfs systems. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade problems
5-stable, after i cvsup, i make buidlworld and build a new kernel from GENERIC . 5-stable. I compile with NFS Client, and all nfs stuff to try :) doesnt work. weird From: Kent Stewart [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: Marta Resende [EMAIL PROTECTED] Subject: Re: Upgrade problems Date: Mon, 6 Dec 2004 13:55:07 -0800 On Monday 06 December 2004 01:21 pm, Marta Resende wrote: Does anyone here had recently updated succecefully to -stable ?? Cause i'm trying for 5 days now, and i cant... All the update process runs well, except the boot, that runs normally to: Mounting NFS file systems:. after these, it blocks, ctrl-c and ctrl-t doesnt work, i have to force halt... no one with these same problem ?? It's impossible, i've updated 6 times Which stable? 5-stable requires NFSCLIENT and 4-stable requires NFS. Did you update your kernel config file before you built your new kernel. Upgrades with old config's are bound to cause problems. I have NFS built into both 4-stable and 5-stable. They boot without any problems. I also as a matter of principal don't permit auto mounts of nfs systems. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade problems
On Mon, Dec 06, 2004 at 10:03:50PM +, Marta Resende wrote: 5-stable, after i cvsup, i make buidlworld and build a new kernel from GENERIC . 5-stable. I compile with NFS Client, and all nfs stuff to try :) doesnt work. weird 1) Don't top-post. 2) Please show us your kernel configuration and rc.conf files, so we can check whether you have something misconfigured. Kris From: Kent Stewart [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: Marta Resende [EMAIL PROTECTED] Subject: Re: Upgrade problems Date: Mon, 6 Dec 2004 13:55:07 -0800 On Monday 06 December 2004 01:21 pm, Marta Resende wrote: Does anyone here had recently updated succecefully to -stable ?? Cause i'm trying for 5 days now, and i cant... All the update process runs well, except the boot, that runs normally to: Mounting NFS file systems:. after these, it blocks, ctrl-c and ctrl-t doesnt work, i have to force halt... no one with these same problem ?? It's impossible, i've updated 6 times Which stable? 5-stable requires NFSCLIENT and 4-stable requires NFS. Did you update your kernel config file before you built your new kernel. Upgrades with old config's are bound to cause problems. I have NFS built into both 4-stable and 5-stable. They boot without any problems. I also as a matter of principal don't permit auto mounts of nfs systems. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] pgpJbM3tyzVsd.pgp Description: PGP signature
Re: Upgrade problems
Basiclly, i disable all that i dont need, and keep all first options , cause i didnt new at the first if it was any commented option that was provocing these block in boot. there's anything i commented that i shouldn't?? because the only option is a bad kernel config, because it stops working after upgrading. At the first i think at pseudo-devices, but i just commented sl pp and tun, wich is needed only for ppp and i have cable connection, thanks: kernel config: -- machine i386 cpu I686_CPU ident MYKERNEL options SCHED_4BSD options INET options INET6 options FFS options SOFTUPDATES options UFS_ACL options UFS_DIRHASH options MD_ROOT options NFSCLIENT options NFSSERVER options NFS_ROOT options MSDOSFS options CD9660 options PROCFS options PSEUDOFS options GEOM_PT options COMPAT_43 options COMPAT_FREEBSD4 options SCSI_DELAY=15000 options KTRACE options SYSVSHM options SYSVMSG options SYSVSEM options _KPOSIX_PRIORIY_SCHEDULING options KBD_INSTALL_CDEV options AHC_REG_PRETTY_PRINT options AHD_REG_PRETTY_PRINT options ADAPTIVE_GIANT device isa device pci device ata device atadisk device ataraid device atapicd device atapifd device ATA_STATIC_ID device atkbdc device atkbd device psm device vga device splash device sc device agp device npx device pmtimer device sio device device ppc device ppbus device plip device vpo device miibus device rl device loop device mem device io device random device ether device pty device md device gif device faith device bpf . From: Kris Kennaway [EMAIL PROTECTED] To: Marta Resende [EMAIL PROTECTED] CC: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Upgrade problems Date: Mon, 6 Dec 2004 14:15:45 -0800 On Mon, Dec 06, 2004 at 10:03:50PM +, Marta Resende wrote: 5-stable, after i cvsup, i make buidlworld and build a new kernel from GENERIC . 5-stable. I compile with NFS Client, and all nfs stuff to try :) doesnt work. weird 1) Don't top-post. 2) Please show us your kernel configuration and rc.conf files, so we can check whether you have something misconfigured. Kris From: Kent Stewart [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: Marta Resende [EMAIL PROTECTED] Subject: Re: Upgrade problems Date: Mon, 6 Dec 2004 13:55:07 -0800 On Monday 06 December 2004 01:21 pm, Marta Resende wrote: Does anyone here had recently updated succecefully to -stable ?? Cause i'm trying for 5 days now, and i cant... All the update process runs well, except the boot, that runs normally to: Mounting NFS file systems:. after these, it blocks, ctrl-c and ctrl-t doesnt work, i have to force halt... no one with these same problem ?? It's impossible, i've updated 6 times Which stable? 5-stable requires NFSCLIENT and 4-stable requires NFS. Did you update your kernel config file before you built your new kernel. Upgrades with old config's are bound to cause problems. I have NFS built into both 4-stable and 5-stable. They boot without any problems. I also as a matter of principal don't permit auto mounts of nfs systems. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] attach3 _ Don't just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade problems
*Please* don't top-post. Marta Resende [EMAIL PROTECTED] writes: Basiclly, i disable all that i dont need, and keep all first options , cause i didnt new at the first if it was any commented option that was provocing these block in boot. there's anything i commented that i shouldn't?? because the only option is a bad kernel config, because it stops working after upgrading. At the first i think at pseudo-devices, but i just commented sl pp and tun, wich is needed only for ppp and i have cable connection, thanks: kernel config: -- machine i386 cpu I686_CPU ident MYKERNEL options SCHED_4BSD options INET options INET6 options FFS options SOFTUPDATES options UFS_ACL options UFS_DIRHASH options MD_ROOT options NFSCLIENT options NFSSERVER options NFS_ROOT options MSDOSFS options CD9660 options PROCFS options PSEUDOFS options GEOM_PT options COMPAT_43 options COMPAT_FREEBSD4 options SCSI_DELAY=15000 options KTRACE options SYSVSHM options SYSVMSG options SYSVSEM options _KPOSIX_PRIORIY_SCHEDULING options KBD_INSTALL_CDEV options AHC_REG_PRETTY_PRINT options AHD_REG_PRETTY_PRINT options ADAPTIVE_GIANT device isa device pci device ata device atadisk device ataraid device atapicd device atapifd device ATA_STATIC_ID device atkbdc device atkbd device psm device vga device splash device sc device agp device npx device pmtimer device sio device device ppc device ppbus device plip device vpo device miibus device rl device loop device mem device io device random device ether device pty device md device gif device faith device bpf This doesn't compile, even after fixing the obvious typos, so it clearly is not the kernel configuration file you were using. If the GENERIC kernel works, you can always use that. If you really want to cut unnecessary configuration elements, you can do them a few at a time until you start having problems, and then you'll have a pretty good idea where the problems came from. If you want to experiment with NFS, the GENERIC kernel contains everything you need. . From: Kris Kennaway [EMAIL PROTECTED] To: Marta Resende [EMAIL PROTECTED] CC: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Upgrade problems Date: Mon, 6 Dec 2004 14:15:45 -0800 On Mon, Dec 06, 2004 at 10:03:50PM +, Marta Resende wrote: 5-stable, after i cvsup, i make buidlworld and build a new kernel from GENERIC . 5-stable. I compile with NFS Client, and all nfs stuff to try :) doesnt work. weird 1) Don't top-post. 2) Please show us your kernel configuration and rc.conf files, so we can check whether you have something misconfigured. Kris From: Kent Stewart [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: Marta Resende [EMAIL PROTECTED] Subject: Re: Upgrade problems Date: Mon, 6 Dec 2004 13:55:07 -0800 On Monday 06 December 2004 01:21 pm, Marta Resende wrote: Does anyone here had recently updated succecefully to -stable ?? Cause i'm trying for 5 days now, and i cant... All the update process runs well, except the boot, that runs normally to: Mounting NFS file systems:. after these, it blocks, ctrl-c and ctrl-t doesnt work, i have to force halt... no one with these same problem ?? It's impossible, i've updated 6 times Which stable? 5-stable requires NFSCLIENT and 4-stable requires NFS. Did you update your kernel config file before you built your new kernel. Upgrades with old config's are bound to cause problems. I have NFS built into both 4-stable and 5-stable. They boot without any problems. I also as a matter of principal don't permit auto mounts of nfs systems. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] attach3 _ Don't just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ [EMAIL PROTECTED] mailing list http
Re: Upgrade problems
On Mon, Dec 06, 2004 at 10:59:11PM +, Marta Resende wrote: Basiclly, i disable all that i dont need, and keep all first options , cause i didnt new at the first if it was any commented option that was provocing these block in boot. there's anything i commented that i shouldn't?? because the only option is a bad kernel config, because it stops working after upgrading. At the first i think at pseudo-devices, but i just commented sl pp and tun, wich is needed only for ppp and i have cable connection, 1) You're still top-posting. http://www.caliburn.nl/topposting.html 2) You only gave me half of what I asked for. Kris thanks: kernel config: -- machine i386 cpu I686_CPU ident MYKERNEL options SCHED_4BSD options INET options INET6 options FFS options SOFTUPDATES options UFS_ACL options UFS_DIRHASH options MD_ROOT options NFSCLIENT options NFSSERVER options NFS_ROOT options MSDOSFS options CD9660 options PROCFS options PSEUDOFS options GEOM_PT options COMPAT_43 options COMPAT_FREEBSD4 options SCSI_DELAY=15000 options KTRACE options SYSVSHM options SYSVMSG options SYSVSEM options _KPOSIX_PRIORIY_SCHEDULING options KBD_INSTALL_CDEV options AHC_REG_PRETTY_PRINT options AHD_REG_PRETTY_PRINT options ADAPTIVE_GIANT device isa device pci device ata device atadisk device ataraid device atapicd device atapifd device ATA_STATIC_ID device atkbdc device atkbd device psm device vga device splash device sc device agp device npx device pmtimer device sio device device ppc device ppbus device plip device vpo device miibus device rl device loop device mem device io device random device ether device pty device md device gif device faith device bpf . From: Kris Kennaway [EMAIL PROTECTED] To: Marta Resende [EMAIL PROTECTED] CC: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Upgrade problems Date: Mon, 6 Dec 2004 14:15:45 -0800 On Mon, Dec 06, 2004 at 10:03:50PM +, Marta Resende wrote: 5-stable, after i cvsup, i make buidlworld and build a new kernel from GENERIC . 5-stable. I compile with NFS Client, and all nfs stuff to try :) doesnt work. weird 1) Don't top-post. 2) Please show us your kernel configuration and rc.conf files, so we can check whether you have something misconfigured. Kris From: Kent Stewart [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: Marta Resende [EMAIL PROTECTED] Subject: Re: Upgrade problems Date: Mon, 6 Dec 2004 13:55:07 -0800 On Monday 06 December 2004 01:21 pm, Marta Resende wrote: Does anyone here had recently updated succecefully to -stable ?? Cause i'm trying for 5 days now, and i cant... All the update process runs well, except the boot, that runs normally to: Mounting NFS file systems:. after these, it blocks, ctrl-c and ctrl-t doesnt work, i have to force halt... no one with these same problem ?? It's impossible, i've updated 6 times Which stable? 5-stable requires NFSCLIENT and 4-stable requires NFS. Did you update your kernel config file before you built your new kernel. Upgrades with old config's are bound to cause problems. I have NFS built into both 4-stable and 5-stable. They boot without any problems. I also as a matter of principal don't permit auto mounts of nfs systems. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] attach3 _ Don't just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] pgpgHBkj3c0Da.pgp Description: PGP signature
Binary Upgrade Problems 4.3 --- 4.9
I'm having trouble doing a binary upgrade from 4.3 to 4.9. Existing 4.3 was installed with 'all' distributions selected, and takes up about 636M on an old Pentium. When I tried the upgrade to 4.9 the first time (selecting 'all' again) the process bombed, and complained about unwillingness to upgrade /src, suggesting CTM or CVSup - which was fair enough, since this was supposed to be a 'binary' upgrade. (Does this always happen??) Re-installed 4.3 again and re-tried the upgrade - this time with all distributions chosen (except sources). Bombed out again, complaining about 'unable to extract stuff into /usr/X11R6 directory'. However, even with this outcome, the system seems to be working (almost) OK. Boots OK with 4.9 kernel and 'uname -a' shows Version 4.9. All of the files seem to be there (now takes up 822M), and all of the files I've checked have dates of Oct 27 (which I assume is when 4.9 was built). However, all of my old configuration files are still stuck in /usr/tmp/etc and have not been copied back into /etc - only 'new' unmodified versions of the files are there, also with dates of Oct 27. And, I assume, there are troubles in the X11R6 directory, since that's where it was when it bombed. So, it appears that the upgrade went almost to completion, but ran into trouble towards the end. Any suggestions?? I'm beginning to believe that binary upgrades are more trouble than a 'real' one - even though it 'appears' to be easier. Cal Cornils Napa Valley College Beautiful Napa Valley ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Binary Upgrade Problems 4.3 --- 4.9
On Mon, 8 Dec 2003 16:44:19 -0800, Cal Cornils wrote: I'm having trouble doing a binary upgrade from 4.3 to 4.9. Existing 4.3 was installed with 'all' distributions selected, and takes up about 636M on an old Pentium. When I tried the upgrade to 4.9 the first time (selecting 'all' again) the process bombed, and complained about unwillingness to upgrade /src, suggesting CTM or CVSup - which was fair enough, since this was supposed to be a 'binary' upgrade. (Does this always happen??) Re-installed 4.3 again and re-tried the upgrade - this time with all distributions chosen (except sources). Bombed out again, complaining about 'unable to extract stuff into /usr/X11R6 directory'. However, even with this outcome, the system seems to be working (almost) OK. Boots OK with 4.9 kernel and 'uname -a' shows Version 4.9. All of the files seem to be there (now takes up 822M), and all of the files I've checked have dates of Oct 27 (which I assume is when 4.9 was built). However, all of my old configuration files are still stuck in /usr/tmp/etc and have not been copied back into /etc - only 'new' unmodified versions of the files are there, also with dates of Oct 27. And, I assume, there are troubles in the X11R6 directory, since that's where it was when it bombed. So, it appears that the upgrade went almost to completion, but ran into trouble towards the end. Any suggestions?? I'm beginning to believe that binary upgrades are more trouble than a 'real' one - even though it 'appears' to be easier. to be honest with you, I've _never_ had good luck with binary upgrade. I've never got one to work. If you can, patch everything up, install cvsup, and follow the build world tuturiol on the main website (www.freebsd.org). It will take a little time on an old pentium to recompile the SRC, but on my K6-450, I can build the entire 5.1 src in under a few hrs (like 2-3), the 4.x series is a lot faster. --- doug reynolds | the maverick | [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Continued 4.9-5.x upgrade problems.
On Sat, Nov 29, 2003 at 09:45:56PM -0800, Minnesota Slinky wrote: Also, does anyone know why my emails continue to be rejected from my laptop with the following error: Hi. This is the qmail-send program at radicalv.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. [EMAIL PROTECTED]: 216.136.204.125 failed after I sent the message. Remote host said: 550 Error: Message content rejected You've been blacklisted in SPEWS: http://www.openrbl.org/ip/216/118/91/17.htm http://www.openrbl.org/zones/SPEWS?216.118.91.17 Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Continued 4.9-5.x upgrade problems.
Ok all, I've been working on this 4.9-5.x upgrade for over a week now, and I'm at my wit's end. I've been doing the make -NOLIBPTHREAD=true buildworld, etc. Everything works great until I do the make NOLIBPTHREAD=true installworld. It ends with the error that my kernel is not fresh enough and I get a core dump. I've tried a few different things, as listed below. I tried everything suggested by Mr. Stewart by doing the following sequence of events: 1) make NOLIBPTHREAD=true buildworld 2) make NOLIBPTHREAD=true buildkernel 3) make NOLIBPTHREAD=true installkernel 4) make NOLIBPTHREAD=true installworld I get an error on the installworld about my kernel not being fresh enough. So, I try the following: 1) make NOLIBPTHREAD=true buildworld 2) make NOLIBPTHREAD=true buildkernel 3) make NOLIBPTHREAD=true installkernel 4) reboot system, attempt to load /boot/kernel, failure Can someone tell me what I'm doing wrong? Would it just be easier to do a binary upgrade via sysinstall? Is there a howto somewhere? Once I complete this, would it help if I write one? TIA, I won't have any hair left, soon, and I'm only in my early 20's. Also, does anyone know why my emails continue to be rejected from my laptop with the following error: Hi. This is the qmail-send program at radicalv.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. [EMAIL PROTECTED]: 216.136.204.125 failed after I sent the message. Remote host said: 550 Error: Message content rejected Thanks, again, in advance. Eric F Crist President AdTech Integrated Systems, Inc (952) 403-9000 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: openssl upgrade problems - newbie stuck
On Wed, 18 Sep 2002 13:41:49 +0100, [EMAIL PROTECTED] (Roman Neuhauser) wrote: hmmm, i got to http://people.freebsd.org/~jdp/s1g/ read this page. you have a kind of chicken and egg problem: you need to update cvsup, but it's too old, and will get kicked from cvsup servers. try using the package listed there. you'll want the non-gui version. How about pkg_delete -x cvsup and pkg_add -r cvsup-without-gui, or will this fall foul of the change of package format from gzip to bzip2? In which case I guess manually download the package for cvsup-without-gui from ftp.freebsd.org and pkg_add the downloaded file. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
openssl upgrade problems - newbie stuck
Hi, I'm a complete BSD ports newbie. I've inherited a BSD production machine and am belatedly trying to upgrade openssl to the 9.6g version. I'm trying to do this through the ports collection, which originally had 9.6a installed, but which had a partial (broken) installation of a later version over the top. I've tried to override things manually to allow the upgrade (definitely a mistake) but am unable to complete the installation. make install gives me: - === Patching for openssl-0.9.6g === Applying FreeBSD patches for openssl-0.9.6g Ignoring previously applied (or reversed) patch. 2 out of 2 hunks ignored--saving rejects to Makefile.org.rej Patch patch-ab failed to apply cleanly. *** Error code 1 Stop in /usr/ports/security/openssl. *** Error code 1[repeated 5 times] --- is there any clean way to continue (or to back out and restart)? The box is a live one; I can't easily take everything off-line to experiment. thanks for any advice Graham To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: openssl upgrade problems - newbie stuck
# [EMAIL PROTECTED] / 2002-09-18 10:23:08 +0100: make install gives me: - === Patching for openssl-0.9.6g === Applying FreeBSD patches for openssl-0.9.6g Ignoring previously applied (or reversed) patch. 2 out of 2 hunks ignored--saving rejects to Makefile.org.rej Patch patch-ab failed to apply cleanly. *** Error code 1 # cd /usr/ports/security/openssl # make clean build if that fails, cvsup your ports *), and try again. *) if the system is configured well, this will suffice: # cd /usr/ports # make update index -- begin 666 nonexistent.vbs FreeBSD 4.7-RC 12:56PM up 20:11, 13 users, load averages: 2.76, 2.24, 2.09 end To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: openssl upgrade problems - newbie stuck
# [EMAIL PROTECTED] / 2002-09-18 12:54:32 +0100: On Wed, 18 Sep 2002, Roman Neuhauser wrote: # cd /usr/ports/security/openssl # make clean build ... Patch patch-ac failed to apply cleanly. Stop in /usr/ports/security/openssl. *** Error code 1 (as before) if that fails, cvsup your ports *), and try again. *) if the system is configured well, this will suffice: # cd /usr/ports # make update index /usr/ports# make update index Error: Please define either SUP_UPDATE or CVS_UPDATE first. ok, so it's not configured. this is the relevant part of my /etc/make.conf, you'll want to adjust SUPHOST: SUP=/usr/local/bin/cvsup SUPFLAGS= -g -L 2 SUPHOST=cvsup.cz.FreeBSD.org PORTSSUPFILE= /usr/local/etc/cvsup/supfiles/ports-supfile and this is the ports-supfile: *default base=/usr/local/etc/cvsup *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress ports-all try again with this. -- begin 666 nonexistent.vbs FreeBSD 4.7-RC 2:05PM up 21:20, 13 users, load averages: 2.00, 2.00, 2.02 end To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: openssl upgrade problems - newbie stuck
On Wed, 18 Sep 2002, Roman Neuhauser wrote: ok, so it's not configured. this is the relevant part of my /etc/make.conf, you'll want to adjust SUPHOST: and this is the ports-supfile: snip try again with this. -- Running /usr/local/bin/cvsup -- Parsing supfile /usr/local/etc/cvsup/supfiles/ports-supfile Connecting to cvsup.uk.FreeBSD.org Connected to cvsup.uk.FreeBSD.org Protocol negotiation failed: See http://www.polstra.com/projects/freeware/CVSup/s1g/ for upgrading information *** Error code 1 Stop in /usr/ports. --- but the url given above just redirects to the cvsup.org front page. and there's nothing I can see in the FAQ. Graham To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: openssl upgrade problems - newbie stuck
# [EMAIL PROTECTED] / 2002-09-18 13:23:59 +0100: Parsing supfile /usr/local/etc/cvsup/supfiles/ports-supfile Connecting to cvsup.uk.FreeBSD.org Connected to cvsup.uk.FreeBSD.org Protocol negotiation failed: See http://www.polstra.com/projects/freeware/CVSup/s1g/ for upgrading information *** Error code 1 Stop in /usr/ports. --- but the url given above just redirects to the cvsup.org front page. and there's nothing I can see in the FAQ. hmmm, i got to http://people.freebsd.org/~jdp/s1g/ read this page. you have a kind of chicken and egg problem: you need to update cvsup, but it's too old, and will get kicked from cvsup servers. try using the package listed there. you'll want the non-gui version. -- begin 666 nonexistent.vbs FreeBSD 4.7-RC 2:38PM up 21:53, 13 users, load averages: 2.00, 2.00, 2.00 end To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: openssl upgrade problems - newbie stuck
On Wed, 18 Sep 2002, Roman Neuhauser wrote: # cd /usr/ports/security/openssl # make clean build Patch patch-ac failed to apply cleanly. Stop in /usr/ports/security/openssl. *** Error code 1 (as before) if that fails, cvsup your ports *), and try again. *) if the system is configured well, this will suffice: # cd /usr/ports # make update index /usr/ports# make update index Error: Please define either SUP_UPDATE or CVS_UPDATE first. So I tried export SUP_UPDATE=yes Now: /usr/ports# make update index Error: Please define PORTSSUPFILE before doing make update. I found an example port-supfile, edited it just to get ports-all and ports-security, and ran again. Now I get: /usr/ports# make update index -- Running -- *default: not found *default: not found *default: not found *default: not found *default: not found *default: not found ports-base: not found ports-security: not found *** Error code 127 and thought I'd better stop before doing any more damage failing around like this... Thanks for the help Graham -- begin 666 nonexistent.vbs FreeBSD 4.7-RC 12:56PM up 20:11, 13 users, load averages: 2.76, 2.24, 2.09 end To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
