Fatal trap 12 after upgrading from 8.2 to 8.4
I've got a system running on a VPS that I'm trying to upgrade from 8.2 to 8.4. It has a ZFS root. After booting the new kernel, I get: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x40 fault code = supervisor read data, page not present instruction pointer = 0x20:0x810d7691 stack pointer = 0x28:0xff81ba60 frame pointer = 0x28:0xff81ba90 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 1 (kernel) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0x8066cb96 at kdb_backtrace+0x66 #1 0x8063925e at panic+0x1ce #2 0x809c21d0 at trap_fatal+0x290 #3 0x809c255e at trap_pfault+0x23e #4 0x809c2a2e at trap+0x3ce #5 0x809a9624 at calltrap+0x8 #6 0x810df517 at vdev_mirror_child_select+0x67 #7 0x810dfacc at vdev_mirror_io_start+0x24c #8 0x810f7c52 at zio_vdev_io_start+0x232 #9 0x810f76f3 at zio_execute+0xc3 #10 0x810f77ad at zio_wait+0x2d #11 0x8108991e at arc_read+0x6ce #12 0x8109d9d4 at dmu_objset_open_impl+0xd4 #13 0x810b4014 at dsl_pool_init+0x34 #14 0x810c7eea at spa_load+0x6aa #15 0x810c90b2 at spa_load_best+0x52 #16 0x810cb0ca at spa_open_common+0x14a #17 0x810a892d at dsl_dir_open_spa+0x2cd Uptime: 3s Cannot dump. Device not defined or unavailable. I've booted back into the 8.2 kernel without any problems, but I'm wondering if anyone can suggest what I should try to get this working? I used freebsd-update to upgrade, and this was after the first freebsd-update install where it installs the kernel. My /boot/loader.conf has: zfs_load=YES vfs.root.mountfrom=zfs:zroot Patrick ___ 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
[Solved] Error upgrading sysutils/nepomuk-core - Could not find parser plugin for encoding trig
On Friday 12 Jul 2013 18:15:18 Mike Clarke wrote: Could anyone advise how to get round this problem? [ 3%] Generating nie.h, nie.cpp cd /usr/ports/sysutils/nepomuk-core/work/.build/libnepomukcore /usr/local/bin/onto2vocabularyclass --name NIE --encoding trig --namespace Nepomuk2::Vocabulary --export-module nepomuk /usr/local/share/ontology/nie/nie.trig Could not find parser plugin for encoding trig The original problem arose when I ran portmaster -r apr -r kdelibs-4\*. It turned out that raptor is a dependency of kdelibs but for some reason portmaster had not selected it for upgrading. After manually running portmaster raptor I was able to build nepomuk-core and continue the mega update with portmaster -R -r apr -r kdelibs-4\* -- Mike Clarke ___ 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
Error upgrading sysutils/nepomuk-core - Could not find parser plugin for encoding trig
Could anyone advise how to get round this problem? [ 3%] Generating nie.h, nie.cpp cd /usr/ports/sysutils/nepomuk-core/work/.build/libnepomukcore /usr/local/bin/onto2vocabularyclass --name NIE --encoding trig --namespace Nepomuk2::Vocabulary --export-module nepomuk /usr/local/share/ontology/nie/nie.trig Could not find parser plugin for encoding trig *** [libnepomukcore/nie.h] Error code 1 Stop in /usr/ports/sysutils/nepomuk-core/work/.build. *** [libnepomukcore/CMakeFiles/nepomukcore.dir/all] Error code 1 Stop in /usr/ports/sysutils/nepomuk-core/work/.build. *** [all] Error code 1 Stop in /usr/ports/sysutils/nepomuk-core/work/.build. *** [do-build] Error code 1 Stop in /usr/ports/sysutils/nepomuk-core. -- Mike Clarke ___ 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
Upgrading from 8.0 to 8.4 with freebsd-update?
Is it possible to skip point releases using freebsd-update so that I can go from 8.0 to 8.4, or do I need to go 8.0 - 8.1 - 8.2 - 8.3 - 8.4? Patrick ___ 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: Upgrading from 8.0 to 8.4 with freebsd-update?
On Thu, Jun 27, 2013 at 8:05 PM, Patrick gibblert...@gmail.com wrote: Is it possible to skip point releases using freebsd-update so that I can go from 8.0 to 8.4 Yes. http://www.freebsd.org/releases/8.4R/relnotes-detailed.html#upgrade -- Adam Vande More ___ 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
Perl error in Munin after upgrading Perl
Dear All, Munin stopped working after I switched to Perl 5.16 on FreeBSD 9.1. I rebuilt all ports that depend on Perl. What did I do wrong? Can't locate IO/Socket/INET6.pm in @INC (@INC contains: /usr/local/lib/perl5/5.16/BSDPAN /usr/local/lib/perl5/site_perl/5.16/mach /usr/local/lib/perl5/site_perl/5.16 /usr/local/lib/perl5/5.16/mach /usr/local/lib/perl5/5.16 .) at /usr/local/lib/perl5/site_perl/5.16/Munin/Master/Node.pm line 18. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.16/Munin/Master/Node.pm line 18. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.16/Munin/Master/UpdateWorker.pm line 17. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.16/Munin/Master/UpdateWorker.pm line 17. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.16/Munin/Master/Update.pm line 17. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.16/Munin/Master/Update.pm line 17. Compilation failed in require at /usr/local/share/munin/munin-update line 14. BEGIN failed--compilation aborted at /usr/local/share/munin/munin-update line 14. Kees Jan ___ 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
Upgrading from 8.3 to 9.1 zfs pool can't attach
I've upgraded a machine with freebsd-update from 8.3 to 9.1. After the first restart I edited /etc/fstab in single user mode because the names on the disks had changed. But the zpool I have seem to have a problem and I'm not sure on how to recover it. May 22 12:00:39 kernel: ZFS WARNING: Unable to attach to ada0. May 22 12:00:39 kernel: ZFS WARNING: Unable to attach to ada1. May 22 12:00:39 kernel: ZFS WARNING: Unable to attach to ada4. May 22 12:00:40 kernel: ZFS WARNING: Unable to attach to ada5. camcontrol devlist ST3320620AS 3.AAEat scbus0 target 0 lun 0 (ada0,pass0) ST3320620AS 3.AAEat scbus1 target 0 lun 0 (ada1,pass1) WDC WD360GD-00FNA0 35.06K35 at scbus2 target 0 lun 0 (ada2,pass2) WDC WD360GD-00FNA0 35.06K35 at scbus2 target 1 lun 0 (ada3,pass3) ST3320620AS 3.AAEat scbus3 target 0 lun 0 (ada4,pass4) ST3320620AS 3.AAEat scbus3 target 1 lun 0 (ada5,pass5) ada2 and ada3 are configured as raid/r0 holding the system. ada0, ada1, ada4 and ada5 should be a zpool with /storage cat /etc/fstab # DeviceMountpoint FStype Options Dump Pass# /dev/raid/r0s1b noneswapsw 0 0 /dev/raid/r0s1a / ufs rw 1 1 /dev/raid/r0s1e /tmpufs rw 2 2 /dev/raid/r0s1f /usrufs rw 2 2 /dev/raid/r0s1d /varufs rw 2 2 Can I recover it? Thanks /Leslie ___ 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
Upgrading from 7.4 to 9.1
Hi, I wanted to know if you would consider updating from 7.4 to 9.1 directly ? Has anyone tried that with success ? I plan to use the freebsd-update method. Thanks for your feedback. G.B. «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ BSD - BSD - BSD - BSD - BSD - BSD - BSD - BSD - «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ PGP ID -- 0x1BA3C2FD ___ 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: Upgrading from 7.4 to 9.1
On Sat, 27 Apr 2013, b...@todoo.biz wrote: Hi, I wanted to know if you would consider updating from 7.4 to 9.1 directly ? Has anyone tried that with success ? I plan to use the freebsd-update method. Thanks for your feedback. G.B. If you are not a developer (I am not), I think the short answer don't do it. I think the issue is leaving stuff behind that might hurt. Eventually would be much worse than immediate problems, especially for a remote server. My experience with freebsd-update has been if a mirror has the diff, then it will work. That said, I have never skipped a version. Earlier threads on this topic suggest its better to go to 8.0-rel then to the latest 8.x then to 9. For me I used CD/DVD even though it meant a drive. I would not be too suprised if freebsd-update balked at skipping 8. If you are physically with the system, it will not take too much time to try it. The process of a minimal install from CD then freebsd-update is not very long. If you are running Xorg, it is the only way IMO. ___ 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: Upgrading from 7.4 to 9.1
Le 27 avr. 2013 à 18:11, Robert Huff roberth...@rcn.com a écrit : b...@todoo.biz writes: I wanted to know if you would consider updating from 7.4 to 9.1 directly ? Has anyone tried that with success ? Someone, somewhere. :-) I plan to use the freebsd-update method. Less sure about this. While it is certainly possible, many (myself included) will recommend a clean install. Doing so has the following advantages: 1) while it requires an unused disk, the old disk is still available if anything Goes Horribly Wrong(tm). 2) once the 9.1 system is fully functional, you can mount the 7.4 disk read-only and copy any needed files. 3) it will also de-clutter the file systems. 4) speaking of file systems, you can add/delete/change partitions to implement lessons learned since the 7.4 system was installed. Well to tell you the truth, the main reason I was asking is that I'll have to visit my datacenter in order to do a clean install… as opposed to remote upgrade. So I was wondering if that could be ok. But I'll stick to your advice. Unless someone else tells me that It is a painless rapid update. Thx. Respectfully, Robert Huff «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ BSD - BSD - BSD - BSD - BSD - BSD - BSD - BSD - «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ PGP ID -- 0x1BA3C2FD ___ 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: Upgrading from 7.4 to 9.1
b...@todoo.biz writes: I wanted to know if you would consider updating from 7.4 to 9.1 directly ? Has anyone tried that with success ? While it is certainly possible, many (myself included) will recommend a clean install. Doing so has the following advantages: Well to tell you the truth, the main reason I was asking is that I'll have to visit my datacenter in order to do a clean install as opposed to remote upgrade. If you know your hardware, you can build a disk /here/, send it /there/, and have someone swap disks. Usually - but not always - one can simply copy the kernel configuration file and rebuild kernel+world. (Read /usr/src/UPDATING before doing so,) Unless someone else tells me that It is a painless rapid update. It's painless ... except when it isn't. :-) Robert trust in Allah, but tie up your camel Huff ___ 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: Upgrading from 7.4 to 9.1
Hi, On Sat, 27 Apr 2013 17:32:53 +0200 b...@todoo.biz b...@todoo.biz wrote: Hi, I wanted to know if you would consider updating from 7.4 to 9.1 directly ? you might will face the same problem I face when trying to upgrade 7.x to 8.x on old hardware. The USB controller was not supported anymore. I have had to keep the machine on 7 until it got hit by a lightning. Has anyone tried that with success ? I plan to use the freebsd-update method. I never did this. I always use custom kernels. Erich ___ 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: pkg_add problems after upgrading to 9.1-RELEASE and a fix
The problem is the November compromise, search for that in the mailing list. There are still no packages available for 9.1-RELEASE. Cheers 2013/2/15 Eduardo Morras emorr...@yahoo.es Hi all, yesterday i updated my server to 9.1-RELEASE from 8.3. After that, while recompiling the ports and packages i get a lot off errors trying to get 9.1-RELESASE packages and all recompiled from ports. The problem is that there's no 9.1-RELEASE directory in ftp.freebsd.orgserver. I solved it after changing the path to fetch from 9-STABLE instead. A better fix i think it's to add that directory or make a ln to stable. The url where add the fault directory is: ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/ the fault directoy is : ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/ An example of the error is: root@camibar:/usr/ports/www # pkg_add -r zen-cart Error: Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/Latest/zen-cart.tbz: File unavailable (e.g., file not found, no access) pkg_add: unable to fetch ' ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/Latest/zen-cart.tbz' by URL I made the recompilation of ports with portmaster as noted in 'man portmaster' with this options (from memory, it's not a cp) #portmaster -P -R -D `cat /root/installed_ports_list` Thanks In Advance --- --- Eduardo Morras emorr...@yahoo.es ___ 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 -- Demelier David ___ 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: pkg_add problems after upgrading to 9.1-RELEASE and a fix
And there was an unofficial pkg repository, I can't find where, it was mentioned recently. On Fri, 2013-02-15 at 11:03 +0100, Eduardo Morras wrote: Hi all, yesterday i updated my server to 9.1-RELEASE from 8.3. After that, while recompiling the ports and packages i get a lot off errors trying to get 9.1-RELESASE packages and all recompiled from ports. The problem is that there's no 9.1-RELEASE directory in ftp.freebsd.org server. I solved it after changing the path to fetch from 9-STABLE instead. A better fix i think it's to add that directory or make a ln to stable. The url where add the fault directory is: ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/ the fault directoy is : ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/ An example of the error is: root@camibar:/usr/ports/www # pkg_add -r zen-cart Error: Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/Latest/zen-cart.tbz: File unavailable (e.g., file not found, no access) pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/Latest/zen-cart.tbz' by URL I made the recompilation of ports with portmaster as noted in 'man portmaster' with this options (from memory, it's not a cp) #portmaster -P -R -D `cat /root/installed_ports_list` Thanks In Advance --- --- Eduardo Morras emorr...@yahoo.es ___ 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
Re: pkg_add problems after upgrading to 9.1-RELEASE and a fix
On 02/20/2013 12:20 PM, paranormal wrote: And there was an unofficial pkg repository, I can't find where, it was mentioned recently. There was a message on the stable list http://lists.freebsd.org/pipermail/freebsd-stable/2013-February/072037.html On Fri, 2013-02-15 at 11:03 +0100, Eduardo Morras wrote: Hi all, yesterday i updated my server to 9.1-RELEASE from 8.3. After that, while recompiling the ports and packages i get a lot off errors trying to get 9.1-RELESASE packages and all recompiled from ports. The problem is that there's no 9.1-RELEASE directory in ftp.freebsd.org server. I solved it after changing the path to fetch from 9-STABLE instead. A better fix i think it's to add that directory or make a ln to stable. The url where add the fault directory is: ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/ the fault directoy is : ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/ An example of the error is: root@camibar:/usr/ports/www # pkg_add -r zen-cart Error: Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/Latest/zen-cart.tbz: File unavailable (e.g., file not found, no access) pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/Latest/zen-cart.tbz' by URL I made the recompilation of ports with portmaster as noted in 'man portmaster' with this options (from memory, it's not a cp) #portmaster -P -R -D `cat /root/installed_ports_list` Thanks In Advance --- --- Eduardo Morras emorr...@yahoo.es ___ 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
pkg_add problems after upgrading to 9.1-RELEASE and a fix
Hi all, yesterday i updated my server to 9.1-RELEASE from 8.3. After that, while recompiling the ports and packages i get a lot off errors trying to get 9.1-RELESASE packages and all recompiled from ports. The problem is that there's no 9.1-RELEASE directory in ftp.freebsd.org server. I solved it after changing the path to fetch from 9-STABLE instead. A better fix i think it's to add that directory or make a ln to stable. The url where add the fault directory is: ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/ the fault directoy is : ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/ An example of the error is: root@camibar:/usr/ports/www # pkg_add -r zen-cart Error: Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/Latest/zen-cart.tbz: File unavailable (e.g., file not found, no access) pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/Latest/zen-cart.tbz' by URL I made the recompilation of ports with portmaster as noted in 'man portmaster' with this options (from memory, it's not a cp) #portmaster -P -R -D `cat /root/installed_ports_list` Thanks In Advance --- --- Eduardo Morras emorr...@yahoo.es ___ 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: Upgrading 8.2 to 9.1, Gnome issue
Hi , Forgive my stupidity. Yes, i was getting so many shared library issue. So I deleted to rebuild the pkgdb using #portupgrade. Now I am able to do #portupgrade gnome2. I followed both the following links to upgrade Xorg and Gnome2 . On command prompt Mouse and key board functionality is proper, but when i switched to GUI using #startx , then mouse and key stopped working. I have included HLAD and DBUS to the rc.conf . /etc/rc.conf -- - keymap=us.iso gdm_enable=YES gnome_enable=YES hald_enable=YES dbus_enable=YES sshd_enable=YES moused_port=/dev/psm0 Now I installed wireshark , but I am getting a Gtk-warning **: cannot open display. Please help me what are ports used to upgrade mouse and Key Board functionality with X terminal. I think few libraries are getting linked when I switched from Command prompt to GUI terminal. Please let me know if there is any command used to rebuild all the installed ports and update pkgdb. I am new to this freebsd . Please help me out to set up this system properly. On Tue, Jan 22, 2013 at 4:12 AM, Joe Altman free...@chthonixia.net wrote: On Mon, Jan 21, 2013 at 01:02:17PM +0530, Hrisikesh sahu wrote: # portupgrade -fr gnome-session But I am facing a problem shared object libz.so.5 not found freebsd I see libz.so.6 in my /usr/lib on: 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r245243: Wed Jan 9 18:25:14 EST 2013 r...@whisperer.chthonixia.net:/usr/obj/usr/src/sys/WHISPERER amd64 Remind me: did you buildworld and installworld prior to upgrading ports? I did all these steps to upgrade the ports Code: #pkgdb -fF # rm /var/db/pkg/pkgdb.db # portupgrade -arRn While I wonder why you deleted your pkgdb.db, more to the point: did you rebuild it? but i am facing a issue with - Code: /usr/local/sbin/portupgrade:1473:in `get_pkgname': Makefile broken (MakefileBrokenError) My guess is that you did not rebuild the pkgdb.db... Please help me how to come out from this Makefile broken and shared object libz.so.5 not found freebsd. and I'd do that before trying to solve fixing the libz.so.5 issue. Joe ___ 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
Re: Upgrading 8.2 to 9.1, Gnome issue
On Tue, 22 Jan 2013 15:52:04 +0530, Hrisikesh sahu wrote: On command prompt Mouse and key board functionality is proper, but when i switched to GUI using #startx , then mouse and key stopped working. This looks like a typical configuration error, not quite uncommon today. :-) Note that you shouldn't run startx from your root account (which I assume you do because of #startx). For your local user account, make sure you've configured Gnome 2 to start automatically via ~/.xinitrc or ~/.xsession respectively. Refer to the FreeBSD Gnome FAQ for details. As you're also using GDM (Gnome display manager) for login, your ~/.xsession should contain exec gnome2-session (which I think to remember is the name of the Gnome desktop executable, but check the documentation to be sure). I have included HLAD and DBUS to the rc.conf . /etc/rc.conf -- - keymap=us.iso gdm_enable=YES gnome_enable=YES hald_enable=YES dbus_enable=YES sshd_enable=YES moused_port=/dev/psm0 Looks correct. Now I installed wireshark , but I am getting a Gtk-warning **: cannot open display. You can only run this program when in X (e. g. calling it from an X terminal). Please help me what are ports used to upgrade mouse and Key Board functionality with X terminal. Check your X configuration: If both input methods work in text mode, but not within X, that's often the error. Please let me know if there is any command used to rebuild all the installed ports and update pkgdb. If I remember correctly, it's portupgrade -arf, but as you're using portupgrade, see man portupgrade, the EXAMPLES section should show the proper options. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: Upgrading 8.2 to 9.1, Gnome issue
On Tue, 22 Jan 2013 11:22:04 +0100, Hrisikesh sahu hrisikeshs...@gmail.com wrote: #portupgrade gnome2 Is there a future for GNOME 2 on FreeBSD? GNOME 2 forks http://en.wikipedia.org/wiki/MATE_(desktop_environment) http://en.wikipedia.org/wiki/Cinnamon_(user_interface) GNOMER 3 fallback mode fork http://solusos.com/blog/2013/01/the-consort-desktop-environment/ OT: KDE 3 fork: https://wiki.archlinux.org/index.php/Trinity I didn't read it myself, I've got my information from Linux mailing lists. Regards, Ralf ___ 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: Upgrading 8.2 to 9.1, Gnome issue
On Tue, 22 Jan 2013 13:59:44 +0100, Ralf Mardorf wrote: On Tue, 22 Jan 2013 11:22:04 +0100, Hrisikesh sahu hrisikeshs...@gmail.com wrote: #portupgrade gnome2 Is there a future for GNOME 2 on FreeBSD? I assume -- on the _long_ run -- Gnome 2 will be dead, just as Gnome 1, KDE 1 and 2, and XFCE (capitals, so it obviously means version 3). MATE and Cinnamon are still maintained, and if there will be FreeBSD ports, they will probably work for some time, until eventually the required support libraries at certain levels of abstraction will not work (or even build) anymore, or when security concerns grow enough to abolish the port. Infrastructures are moving on, and backwards compatibility isn't the biggest strength of desktop environments. :-( -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: Upgrading 8.2 to 9.1, Gnome issue
On Tue, 22 Jan 2013 14:09:52 +0100, Polytropon free...@edvax.de wrote: Infrastructures are moving on, and backwards compatibility isn't the biggest strength of desktop environments. :-( Full ACK with the smiley ;) ... :(. ___ 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: Upgrading 8.2 to 9.1, Gnome issue
On Tue, 22 Jan 2013 11:33:17 +0100, Polytropon free...@edvax.de wrote: Note that you shouldn't run startx from your root account I've still tons of issues to solve, one issue is to get GDM run or to directly start x without a display manager. It didn't work as described in the handbook, perhaps it would work now, after the ports tree upgrade, however, I start x from tty after login in as user ... $ startx ... IIRC, if you start x as root, Thunar will warn you, that you run the session as root. I'll do an experiment now, Ctrl + Alt + F1 [snip] ... Don't worry, I'm back in a user session, but I run a root session and got Warning, you are using the root account, you may harm your system. by Thunar 1.6.2. Regards, Ralf ___ 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: Error upgrading Chromium
I worked around this by reconfiguring the port so that it doesn't use pulseadio, recompiled, and it finished OK. Kurt On Thu, Jan 17, 2013 at 7:25 PM, Kurt Buff kurt.b...@gmail.com wrote: Just updated from 8.3 to FreeBSD 9.0-RELEASE-p3, and am reinstalling ports. Chromium is giving me two errors and bombing out. The errors are: media/audio/pulst/pulse_output.cc:89L28: error: use of undeclared identifier 'kChannelOrderings'; did you mean 'ChannelOrder'? int channel_position = kChannelOrderings[channel_layout][channel]; ^ ChannelOrder ./media/base/channel/_layout.h:121:18: note: 'ChannelOrder' declared here MEDIA_EXPORT int ChannelOrder(ChannelLayout layout, Channels, channel); ^ media/audio/pulse_output.cc:89:45: error: type 'int (media::ChannelLayout, media::Channels)' does not provide a subscript operator int channel_position = kChannelOrderings[channel_layout][channel]; 2 errors generated. gmake: *** [out/Release/obj.target/media/media/audio/pulse/pulse_output.0] Error 1 I've googled trying to see what if anyting this might be, and see nothing... Anyone have thoughts on this? Thanks, Kurt ___ 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: Error upgrading Chromium
On Mon, 2013-01-21 at 08:30 -0800, Kurt Buff wrote: I worked around this by reconfiguring the port so that it doesn't use pulseadio, recompiled, and it finished OK. IIUC Google doesn't like to add pulseaudio and/or jackd support to their software. Because you need to be subscribed to Jack devel mailing list to read the archive, I copied an Email from another person who also is subscribed to this list. As a follow up on the original topic the Chromium developers have already implemented CRAS. Their main reason is that they are seeking to minimise energy usage in the OS and not latency or audio routing issues as described in the webpage. Apparently even though Pulseaudio is fine for Palm's/HP's webOS it is not good enough for ChromeOS. I have yet to get to the bottom of how badly they have screwed up JACK integration but it is highly likely that ChromeBooks will not be able to integrate into a netjack system. So, I guess we can expect a new round of pissed off audio users complaining about the lack of JACK integration with ChromeOS in the coming years. Probably the easiest answer will be for them to stick within their Chrome eco system in much the same way that Android users have to now. - http://lists.jackaudio.org/private.cgi/jack-devel-jackaudio.org/2013-January/010592.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: Error upgrading Chromium
On Mon, Jan 21, 2013 at 8:51 AM, Ralf Mardorf ralf.mard...@rocketmail.com wrote: On Mon, 2013-01-21 at 08:30 -0800, Kurt Buff wrote: I worked around this by reconfiguring the port so that it doesn't use pulseadio, recompiled, and it finished OK. IIUC Google doesn't like to add pulseaudio and/or jackd support to their software. Because you need to be subscribed to Jack devel mailing list to read the archive, I copied an Email from another person who also is subscribed to this list. As a follow up on the original topic the Chromium developers have already implemented CRAS. Their main reason is that they are seeking to minimise energy usage in the OS and not latency or audio routing issues as described in the webpage. Apparently even though Pulseaudio is fine for Palm's/HP's webOS it is not good enough for ChromeOS. I have yet to get to the bottom of how badly they have screwed up JACK integration but it is highly likely that ChromeBooks will not be able to integrate into a netjack system. So, I guess we can expect a new round of pissed off audio users complaining about the lack of JACK integration with ChromeOS in the coming years. Probably the easiest answer will be for them to stick within their Chrome eco system in much the same way that Android users have to now. - http://lists.jackaudio.org/private.cgi/jack-devel-jackaudio.org/2013-January/010592.html Good to know! Since ATM I'm only using Chromium on a netbook (Asus Aspire One - about 3 years old), and it doesn't have much of an audio system, I'm not too worked up about it, but I've got a new Dell laptop coming, and I suppose I'll just have to use one of the other web browsers for that. Thanks, Kurt ___ 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: Error upgrading Chromium
On Mon, 2013-01-21 at 10:43 -0800, Kurt Buff wrote: On Mon, Jan 21, 2013 at 8:51 AM, Ralf Mardorf ralf.mard...@rocketmail.com wrote: On Mon, 2013-01-21 at 08:30 -0800, Kurt Buff wrote: I worked around this by reconfiguring the port so that it doesn't use pulseadio, recompiled, and it finished OK. IIUC Google doesn't like to add pulseaudio and/or jackd support to their software. Because you need to be subscribed to Jack devel mailing list to read the archive, I copied an Email from another person who also is subscribed to this list. As a follow up on the original topic the Chromium developers have already implemented CRAS. Their main reason is that they are seeking to minimise energy usage in the OS and not latency or audio routing issues as described in the webpage. Apparently even though Pulseaudio is fine for Palm's/HP's webOS it is not good enough for ChromeOS. I have yet to get to the bottom of how badly they have screwed up JACK integration but it is highly likely that ChromeBooks will not be able to integrate into a netjack system. So, I guess we can expect a new round of pissed off audio users complaining about the lack of JACK integration with ChromeOS in the coming years. Probably the easiest answer will be for them to stick within their Chrome eco system in much the same way that Android users have to now. - http://lists.jackaudio.org/private.cgi/jack-devel-jackaudio.org/2013-January/010592.html Good to know! Since ATM I'm only using Chromium on a netbook (Asus Aspire One - about 3 years old), and it doesn't have much of an audio system, I'm not too worked up about it, but I've got a new Dell laptop coming, and I suppose I'll just have to use one of the other web browsers for that. I'm not sure if it's an issue for the *NIX browser, or just for a GoogleOS. As far as I know, there's a browser called Chrom and Chromium, but there are also operating systems with this name. So some research still is needed. Regards, Ralf ___ 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: Upgrading 8.2 to 9.1, Gnome issue
On Mon, Jan 21, 2013 at 01:02:17PM +0530, Hrisikesh sahu wrote: # portupgrade -fr gnome-session But I am facing a problem shared object libz.so.5 not found freebsd I see libz.so.6 in my /usr/lib on: 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r245243: Wed Jan 9 18:25:14 EST 2013 r...@whisperer.chthonixia.net:/usr/obj/usr/src/sys/WHISPERER amd64 Remind me: did you buildworld and installworld prior to upgrading ports? I did all these steps to upgrade the ports Code: #pkgdb -fF # rm /var/db/pkg/pkgdb.db # portupgrade -arRn While I wonder why you deleted your pkgdb.db, more to the point: did you rebuild it? but i am facing a issue with - Code: /usr/local/sbin/portupgrade:1473:in `get_pkgname': Makefile broken (MakefileBrokenError) My guess is that you did not rebuild the pkgdb.db... Please help me how to come out from this Makefile broken and shared object libz.so.5 not found freebsd. and I'd do that before trying to solve fixing the libz.so.5 issue. Joe ___ 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
Upgrading 8.2 to 9.1, Gnome issue
Hi All, I followed this following link to upgrade from 8.2 RELEASE to 9.1 RELEASE. *http://www.freebsd.org/releases/9.0R/installation.html* After Code: # freebsd-update fetch # freebsd-update install Now the freebsd-update(8) http://man.freebsd.org/freebsd-update/8 utility can fetch bits belonging to 9.1-RELEASE. During this process freebsd-update(8) http://man.freebsd.org/freebsd-update/8 will ask for help in merging configuration files. Code: # freebsd-update upgrade -r 9.1-RELEASE # freebsd-update install The system must now be rebooted with the newly installed kernel before the non-kernel components are updated. Code: # shutdown -r now I followed the following command to upgrade Ports - # portupgrade -fr gnome-session But I am facing a problem shared object libz.so.5 not found freebsd I did all these steps to upgrade the ports Code: #pkgdb -fF # rm /var/db/pkg/pkgdb.db # portupgrade -arRn but i am facing a issue with - Code: /usr/local/sbin/portupgrade:1473:in `get_pkgname': Makefile broken (MakefileBrokenError) Please help me how to come out from this Makefile broken and shared object libz.so.5 not found freebsd. Regards Hrisikesh ___ 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
Error upgrading Chromium
Just updated from 8.3 to FreeBSD 9.0-RELEASE-p3, and am reinstalling ports. Chromium is giving me two errors and bombing out. The errors are: media/audio/pulst/pulse_output.cc:89L28: error: use of undeclared identifier 'kChannelOrderings'; did you mean 'ChannelOrder'? int channel_position = kChannelOrderings[channel_layout][channel]; ^ ChannelOrder ./media/base/channel/_layout.h:121:18: note: 'ChannelOrder' declared here MEDIA_EXPORT int ChannelOrder(ChannelLayout layout, Channels, channel); ^ media/audio/pulse_output.cc:89:45: error: type 'int (media::ChannelLayout, media::Channels)' does not provide a subscript operator int channel_position = kChannelOrderings[channel_layout][channel]; 2 errors generated. gmake: *** [out/Release/obj.target/media/media/audio/pulse/pulse_output.0] Error 1 I've googled trying to see what if anyting this might be, and see nothing... Anyone have thoughts on this? Thanks, Kurt ___ 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
SOLVED: Problem upgrading to 9.1-Release
I found the problem. Somehow /usr/obj was not successfully exported and hence was completely empty. There must have been some error message in that process that I missed. Anyway, correcting that problem so that /usr/obj was available fixed the problem. On 4 January 2013, at 15:38, Doug Hardie wrote: I have upgraded my development system to 9.1 without any problems. This system maintains kernel source and I build a new kernel with a couple extra options there. The other systems mount /usr/src and /usr/obj from it and do the install. The first one to be upgraded had no problem with make installkernel. Rebooted and ran mergemaster -p just fine. However make installworld dies within a couple seconds with the following error: install -o root -g wheel -m 444 libc_pic.a /usr/lib gencat be_BY.UTF-8.cat /usr/src/lib/libc/nls/be_BY.UTF-8.msg gencat: No such file or directory *** [be_BY.UTF-8.cat] Error code 1 /usr/bin/gencat exists. However, ktrace of the make shows: 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /usr/obj/usr/src/tmp/legacy/usr/sbin/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /usr/obj/usr/src/tmp/legacy/usr/bin/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /usr/obj/usr/src/tmp/legacy/usr/games/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /usr/obj/usr/src/tmp/usr/sbin/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /usr/obj/usr/src/tmp/usr/bin/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /usr/obj/usr/src/tmp/usr/games/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /tmp/install.CuIzLuBX/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL write(0x2,0x28c48c00,0x6) 3347 make GIO fd 2 wrote 6 bytes gencat Obviously its not in any of those places. How can I fix this? ___ 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
Problem upgrading to 9.1-Release
I have upgraded my development system to 9.1 without any problems. This system maintains kernel source and I build a new kernel with a couple extra options there. The other systems mount /usr/src and /usr/obj from it and do the install. The first one to be upgraded had no problem with make installkernel. Rebooted and ran mergemaster -p just fine. However make installworld dies within a couple seconds with the following error: install -o root -g wheel -m 444 libc_pic.a /usr/lib gencat be_BY.UTF-8.cat /usr/src/lib/libc/nls/be_BY.UTF-8.msg gencat: No such file or directory *** [be_BY.UTF-8.cat] Error code 1 /usr/bin/gencat exists. However, ktrace of the make shows: 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /usr/obj/usr/src/tmp/legacy/usr/sbin/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /usr/obj/usr/src/tmp/legacy/usr/bin/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /usr/obj/usr/src/tmp/legacy/usr/games/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /usr/obj/usr/src/tmp/usr/sbin/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /usr/obj/usr/src/tmp/usr/bin/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /usr/obj/usr/src/tmp/usr/games/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL execve(0xbfbfd1c8,0x28c35f14,0x28421180) 3347 make NAMI /tmp/install.CuIzLuBX/gencat 3347 make RET execve -1 errno 2 No such file or directory 3347 make CALL write(0x2,0x28c48c00,0x6) 3347 make GIO fd 2 wrote 6 bytes gencat Obviously its not in any of those places. How can I fix this? ___ 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
Upgrading from 9.0-STABLE to 9.1-RELEASE with freebsd-update?
I've used STABLE for years, but with csup going away, I don't want to deal with adding extra packages, and keeping them unbroken, just to stay up date. Running freebsd-update doesn't work for people running STABLE, and I'm not sure freebsd-update will work properly anyway if I compile world for myself. What's the best way to switch from running STABLE to running the RELEASE channel? ___ 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: Upgrading FreeBSD 8.3 amd64
Hi, I've done the upgrade yesterday. It was a clean 8.3 install, I only set up PPPoE and then run the following commands. # cd /usr/ports/misc/mc make install clean # uname -r 8.3-RELEASE # freebsd-update -r 9.1-RELEASE upgrade # freebsd-update install # shutdown -r now # freebsd-update install # cd /usr/ports/ports-mgmt/portupgrade make install clean # /usr/local/sbin/portupgrade -f ruby # rm /var/db/pkg/pkgdb.db # /usr/local/sbin/portupgrade -f ruby18-bdb # rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db # /usr/local/sbin/portupgrade -af # freebsd-update install # shutdown -r now # freebsd-update IDS outfile.ids This is the content of outfile.ids: Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 9.1-RELEASE from update5.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. /boot/kernel/linker.hints has SHA256 hash ebf78144f48f13af88e5e3752735a709b084d7e6aaee10b05e57f2a117cbc366, but should have SHA256 hash 07b927068b34c4671a323e6a8aaa80ad22dc5fc4b3741b8a4060da1764510350. /etc/group has SHA256 hash 108de8653d4a6d451cc3f018780277d2fe2d770df7a7d984f5160dc753e06678, but should have SHA256 hash d788718c25a04a14cc1818ac2afa8b76a3fd899583691972d0d5127947e3504f. /etc/hosts has SHA256 hash 9684014402be7ecd32b9047181f595d124df6cf6a79dd323b0bd5685dccc2a81, but should have SHA256 hash f795387981b68599c3df984f2ce4ac4a32bf420d57faf1fb55f249b885414d64. /etc/master.passwd has SHA256 hash cd9046284ac3e571eb9f0273f9bfc118e7094e0b9312fd1789f6385e43a26cd3, but should have SHA256 hash 6f1da238cc0a55ed360a215039bc6cb5ce5369d20b8fbceb8a1941c5124e6a4e. /etc/motd has SHA256 hash fa311ce1a08aea0c818d57b904c979941dabb726d1fb2ddaa368102bd6f2fb95, but should have SHA256 hash 98f082efc89da5e887e72bc4dcfa3e5fc8bada9d19db4bdbba9a32692a7c82a7. /etc/passwd has SHA256 hash e4bcb10c66a0440efb58591daadaeec894e75e5392da9e00f3881822d0647a11, but should have SHA256 hash 3135de169a0ff94c0c97aeb525a07ea10e5ed81c9b825e219f7eea8deb97c444. /etc/ppp/ppp.conf has 0755 permissions, but should have 0600 permissions. /etc/ppp/ppp.conf has SHA256 hash 623683de09ab97394221c64ccdec3569aa240854d907a4811f91c9ed92253dd4, but should have SHA256 hash f3dd3d0da252bd47681a261a1f0d46a8fc6ae84ff3cbd34b81b586bc87e49655. /etc/pwd.db has SHA256 hash 62eb1eafbfa8fe718e68bf784e542d09ccdc09012ef43d254ae48e9846a1df4d, but should have SHA256 hash bf86739ee052821992412b61a6673811588c382fa63ab38cc47c1a59305376eb. /etc/shells has SHA256 hash 4c25fb7c79fe5057217a70cfa1c27f41959bb7daa703a94774ec5ac9d29a9266, but should have SHA256 hash beab7e474ee12b051b98889f368bbd490340a908f6f2287f9238e818b830a1fd. /etc/spwd.db has SHA256 hash b25126503c347feb67b76a5f27f44c318a675ddc82f4984b5ec0d2fc5a45fd30, but should have SHA256 hash 1cbfbea78d316e4e8d29f53f0770b8ff1f3a731e993c3ae717f36304715d7a5b. When I run ppp -ddial alice now, I get warnings Bad label in /etc/ppp/ppp.conf (line x) - missing colon, but PPPoE still works. Why are the checksums bad? FWIW snd_hdspe now is available. Regards, Ralf ___ 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: Upgrading FreeBSD 8.3 amd64
Hi, On Thu, 20 Dec 2012 05:13:39 +0100 Ralf Mardorf ralf.mard...@rocketmail.com wrote: ok, so FreeBSD release is the version of the kernel and not a labelling for the collection of all the software. yes. It is even so that the ports work on all 'current' FreeBSD versions but not the packages. With other words, you will download always the same source files for 7.4, 8.3, 9.0, 9.1 and 10.0 but compile it then for your version. For Linux major distros there usually is a labelling for the collection of the software, independent of the kernel version. On Linux I usually install binaries for the base system and desktop environment, but for important software, in my case it's audio, compiling from source is very important. This does not really matter here. It is only that you might do not have the options compiled in you will need when using the binary. The author of the snd_hdspe driver for FreeBSD seems to need testers. I never have heard of this driver. It seems to be that nobody ever tested if ADAT is working and I'll test it. OTOH I suspect bug fixes for the driver have to be added by recompiling the kernel or at least the driver for the kernel, so I still could use binaries for the applications. Using sources for the kernel is then the way to go. Binaries could work if the required options are compiled in. You can mix binaries and source within the applications. I do this all the while. I install very often the binary and compile later from sources. Since audio on FreeBSD seems to be a niche, I wonder if it's more promising, to go the source or to go the binary rout. Source is the more promissing route here as niches are not supported by default. There are some rare cases in which options exclude each other. So, if you have strange hardware, source is the only route. I suspect if it's impossible or at least less good to mix binaries and from source build software for FreeBSD, I should chose to build from source. You can mix. If it works, it works. If not, it is most likely an option not compiled in you would need. Erich ___ 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: Upgrading FreeBSD 8.3 amd64
On Thu, 2012-12-20 at 05:29 +0100, Polytropon wrote: I'd say: Use the source Luke. :-) :) Strange question: Is the FreeBSD handbook available as iBook? At the moment I've got plenty of time, unfortunately not in front of my desktop computer. Some time ago I won an iPad2, it's a dust catcher, nice hardware, but odd software. I wonder if its possible to use it as a reader. The problem is, that I can't connect the iPad to the Internet and using iTunes (a disgusting application) in a virtual machine until now I'm only able to use iBooks, but I don't know how to transmit plain txt, pdf, html or what ever from the PC to the iPad. If somebody should know how I can get the FreeBSD handbook on my iPad that would be a help, so I could spend more time in reading how to handle FreeBSD. On VirtualBox (it doesn't work with wine) I run Win XP + iTunes and I connect the PC and iPad by USB. No jailbreake, but if it would help I would jailbraeke it. I tried to set up Linux to do ad-hoc by an USB WiFi stick, but it never worked. It would be nice to run Linux or FreeBSD on the iPad ;). Regards, Ralf ___ 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: Upgrading FreeBSD 8.3 amd64
On Dec 20, 2012, at 10:51 AM, Ralf Mardorf wrote: On Thu, 2012-12-20 at 05:29 +0100, Polytropon wrote: I'd say: Use the source Luke. :-) :) Strange question: Is the FreeBSD handbook available as iBook? You can get it as a PDF at ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/handbook/ and you can then view that on your iPad. Look for the Bookshelf or some such, I use an iPod Touch and while similar, they are not identical to the iPad. -- Paul Kraus Deputy Technical Director, LoneStarCon 3 Sound Coordinator, Schenectady Light Opera Company ___ 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: Upgrading FreeBSD 8.3 amd64
On Thu, 2012-12-20 at 15:52 +0700, Erich Dollansky wrote: The author of the snd_hdspe driver for FreeBSD seems to need testers. I never have heard of this driver. It's a new driver for FreeBSD for some cards of the vendor RME, AFAIK they only sell really professional audio cards, used for broadcasting and by professional audio studios. I never heard of professional audio studios using FreeBSD, so it's very likely that FreeBSD users seldom spend that much money for cards, that ship with all kinds of audio interfaces, that aren't needed for averaged audio usage. I was a professional audio and video engineer, but for my home studio I only bought a relatively cheap RME card, the HDSPe AIO. http://www.rme-audio.de/en_products_hdspe_aio.php It comes with stereo AD/DA converters only, every elCheapo on-board audio device has got more AD/DA IOs. Costs around 500,- EUR / 650,- USD. Other RME gear is much more expensive. Regards, Ralf ___ 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: Upgrading FreeBSD 8.3 amd64
On Thu, 2012-12-20 at 10:57 -0500, Paul Kraus wrote: On Dec 20, 2012, at 10:51 AM, Ralf Mardorf wrote: On Thu, 2012-12-20 at 05:29 +0100, Polytropon wrote: I'd say: Use the source Luke. :-) :) Strange question: Is the FreeBSD handbook available as iBook? You can get it as a PDF at ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/handbook/ and you can then view that on your iPad. Look for the Bookshelf or some such, I use an iPod Touch and while similar, they are not identical to the iPad. ftp://ftp.freebsd.org/pub/FreeBSD/doc/de/books/handbook/book.pdf.bz2 ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/handbook/book.pdf.bz2 iBookshelf Lite 2.12.4 has got a file sharing option, so I added the above extracted archives by renamed PDFs (FreeBSD Handbook de.pdf, FreeBSD Handbook en.pdf), but after sync they still are not available. I renamed the files (bsdde.pdf, bsden.pdf), added them and synced again, but they are still not available. The PDFs can be opened by Linux. VBox, resp. iTunes has got access to the files and sync between VBox and the iPad does work for other data. However, it's OT for this list. Anyway, thank you :) Ralf ___ 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: Upgrading FreeBSD 8.3 amd64
On Fri, 2012-12-21 at 07:35 +0100, Ralf Mardorf wrote: On Thu, 2012-12-20 at 10:57 -0500, Paul Kraus wrote: On Dec 20, 2012, at 10:51 AM, Ralf Mardorf wrote: On Thu, 2012-12-20 at 05:29 +0100, Polytropon wrote: I'd say: Use the source Luke. :-) :) Strange question: Is the FreeBSD handbook available as iBook? You can get it as a PDF at ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/handbook/ and you can then view that on your iPad. Look for the Bookshelf or some such, I use an iPod Touch and while similar, they are not identical to the iPad. ftp://ftp.freebsd.org/pub/FreeBSD/doc/de/books/handbook/book.pdf.bz2 ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/handbook/book.pdf.bz2 iBookshelf Lite 2.12.4 has got a file sharing option, so I added the above extracted archives by renamed PDFs (FreeBSD Handbook de.pdf, FreeBSD Handbook en.pdf), but after sync they still are not available. I renamed the files (bsdde.pdf, bsden.pdf), added them and synced again, but they are still not available. The PDFs can be opened by Linux. VBox, resp. iTunes has got access to the files and sync between VBox and the iPad does work for other data. However, it's OT for this list. Anyway, thank you :) Ralf PS: I installed two other gratis apps. Offline Reader ! 2.0 and PDF Reader Lite 1.2.3, the first app seems to be useless and when I downloaded it, I was asked if I'm = 17 years old :D, but the second app does receive and display the handbooks named bsdde.pdf, bsden.pdf :) Regards, Ralf ___ 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: Upgrading FreeBSD 8.3 amd64
Hi :) this isn't a request, just a note about the handbook, from the point of view a newbie has got. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html We also assume that you have already obtained the sources to a newer system. If the sources available on the particular system are old too, see Section 25.6 for detailed help about synchronizing them to a newer version. I know svn from Linux, but I don't know what I should update using svn ;). Yes, the ports, but to get knowledge were the ports are, I have to google ;). This howto is more confusing for a newbie and seems to need more reboots, so I started with http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html but it's not described how to do the following: Note that setting the BATCH environment variable to yes will answer yes to any prompts during this process, removing the need for manual intervention during the build process. regarding to google it's env BATCH=yes, I'll test it next time I'll reboot into FreeBSD. Another issue is, that the portupgrade command isn't found. However, pppoe does work, but using vi never is fun for me :). I guess I'll read how to install software, IOW how to install portupgrade and continue with the portupgrade method ASAP, later today, or tomorrow. Regards, Ralf ___ 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: Upgrading FreeBSD 8.3 amd64
Ralf, On Wed, Dec 19, 2012 at 10:04 AM, Ralf Mardorf ralf.mard...@rocketmail.com wrote: Hi :) this isn't a request, just a note about the handbook, from the point of view a newbie has got. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html We also assume that you have already obtained the sources to a newer system. If the sources available on the particular system are old too, see Section 25.6 for detailed help about synchronizing them to a newer version. I know svn from Linux, but I don't know what I should update using svn ;). Yes, the ports, but to get knowledge were the ports are, I have to google ;). This howto is more confusing for a newbie and seems to need more reboots, so I started with http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html but it's not described how to do the following: Note that setting the BATCH environment variable to yes will answer yes to any prompts during this process, removing the need for manual intervention during the build process. regarding to google it's env BATCH=yes, I'll test it next time I'll reboot into FreeBSD. Another issue is, that the portupgrade command isn't found. Check in /usr/ports/ports-mgmt/ directory: Become super user, $ su - passwd: then as super user: # cd /usr/ports/ports-mgmt/portupgrade then from that directory # make install clean and you should have the portugrade command :) You may also use at your discretion the portmaster tool? It works very well and a nice example is given by W. Block: http://www.wonkity.com/~wblock/docs/html/portupgrade.html Best Regards, Antonio However, pppoe does work, but using vi never is fun for me :). I guess I'll read how to install software, IOW how to install portupgrade and continue with the portupgrade method ASAP, later today, or tomorrow. Regards, Ralf ___ 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
Re: Upgrading FreeBSD 8.3 amd64
On Wed, 2012-12-19 at 10:14 -0600, Antonio Olivares wrote: You may also use at your discretion the portmaster tool? It works very well and a nice example is given by W. Block: http://www.wonkity.com/~wblock/docs/html/portupgrade.html Thank you Antonio :) because I can't install FreeBSD by the 9.0 DVD, for what reason ever this doesn't work, I installed it by the 8.3 DVD and will now make a release upgrade. IIUC a release upgrade will rebuild everything, hence there should be no dependency issues. My FreeBSD 8.3 is a fresh install, I only set up PPPoE, anything else is default. IIUC I need to take care about it to keep dependencies up to date, when I don't upgrade the complete release, but just upgrade some software. So, can I upgrade from 8.3 to 9.0, without taking care about dependencies and take care about the link, when 9.0 is installed, instead of doing it right now? My apologize for the terrible English, I'm in a hurry, but wanted to rely immediately and this makes broken English not better ;). Regards, Ralf ___ 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: Upgrading FreeBSD 8.3 amd64
Ralf, On Wed, Dec 19, 2012 at 11:09 AM, Ralf Mardorf ralf.mard...@rocketmail.com wrote: On Wed, 2012-12-19 at 10:14 -0600, Antonio Olivares wrote: You may also use at your discretion the portmaster tool? It works very well and a nice example is given by W. Block: http://www.wonkity.com/~wblock/docs/html/portupgrade.html Thank you Antonio :) because I can't install FreeBSD by the 9.0 DVD, for what reason ever this doesn't work, I installed it by the 8.3 DVD and will now make a release upgrade. IIUC a release upgrade will rebuild everything, hence there should be no dependency issues. My FreeBSD 8.3 is a fresh install, I only set up PPPoE, anything else is default. IIUC I need to take care about it to keep dependencies up to date, when I don't upgrade the complete release, but just upgrade some software. So, can I upgrade from 8.3 to 9.0, without taking care about dependencies and take care about the link, when 9.0 is installed, instead of doing it right now? Yes, you can do it. You can update to 9.0 with freebsd-update tool and then install/reinstall the ports. # freebsd-update -r 9.1-RELEASE or # freebsd-update -r 9.0-RELEASE in case that 9.1 is not there yet*? then run # freebsd-update fetch # freebsd-update install to get security updates as is documented : http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html This should work well to get newer RELEASE, but some ports may be needed to be rebuilt/reinstalled. Hope this helps, Antonio My apologize for the terrible English, I'm in a hurry, but wanted to rely immediately and this makes broken English not better ;). Regards, Ralf ___ 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
Re: Upgrading FreeBSD 8.3 amd64
Hi, On Wed, 19 Dec 2012 18:09:16 +0100 Ralf Mardorf ralf.mard...@rocketmail.com wrote: On Wed, 2012-12-19 at 10:14 -0600, Antonio Olivares wrote: You may also use at your discretion the portmaster tool? It works very well and a nice example is given by W. Block: http://www.wonkity.com/~wblock/docs/html/portupgrade.html Thank you Antonio :) because I can't install FreeBSD by the 9.0 DVD, for what reason ever this doesn't work, I installed it by the 8.3 DVD and will now make a release upgrade. IIUC a release upgrade will rebuild everything, hence one way was already shown to you. The other route would lead you via the sources. I prefer the sources over the binary upgrade. If the new kernel will not boot, you can boot the old kernel which will then be under kernel.old. there should be no dependency issues. My FreeBSD 8.3 is a fresh Dependencies come in when it comes to ports. I would like to suggest the you first make a decision whether you want the ports as binaries or via source. Both routes work. Only the sources allow you to specify options. I would also recommend to download first the sources or the binaries and start the upgrade only after all files are downloaded. As you already know, portupgrade is the tool of choice here. If you have problems with 9.1, you might consider a move to 10. I have done this too for the same reason when I got a new machine which has had problems with 9.0. 10.0 is not recommended for production. Me and many other still do this. You might will run occassionally into problems. So, think twice before doing this. install, I only set up PPPoE, anything else is default. IIUC I need to take care about it to keep dependencies up to date, when I don't upgrade the complete release, but just upgrade some software. So, can I upgrade from 8.3 to 9.0, without taking care about dependencies and take care about the link, when 9.0 is installed, instead of doing it right now? FreeBSD and the ports have 'nothing' to do with each other. You have to upgrade FreeBSD first and then upgrade the ports. Most likely, all applications will continue to work without upgrade. If I remember right, even after an upgrade from 8.3 to 10.0 on one of my machines, all applications continued to work. I still upgraded them as fast as possible. My apologize for the terrible English, I'm in a hurry, but wanted to rely immediately and this makes broken English not better ;). Do not worry about this here. I think, while you have been pretty clear on the rest, the last line does not make real sense to me. Erich ___ 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: Upgrading FreeBSD 8.3 amd64
Thank you Erich :) ok, so FreeBSD release is the version of the kernel and not a labelling for the collection of all the software. For Linux major distros there usually is a labelling for the collection of the software, independent of the kernel version. On Linux I usually install binaries for the base system and desktop environment, but for important software, in my case it's audio, compiling from source is very important. The author of the snd_hdspe driver for FreeBSD seems to need testers. It seems to be that nobody ever tested if ADAT is working and I'll test it. OTOH I suspect bug fixes for the driver have to be added by recompiling the kernel or at least the driver for the kernel, so I still could use binaries for the applications. Since audio on FreeBSD seems to be a niche, I wonder if it's more promising, to go the source or to go the binary rout. I suspect if it's impossible or at least less good to mix binaries and from source build software for FreeBSD, I should chose to build from source. Regards, Ralf ___ 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: Upgrading FreeBSD 8.3 amd64
On Thu, 20 Dec 2012 05:13:39 +0100, Ralf Mardorf wrote: Thank you Erich :) ok, so FreeBSD release is the version of the kernel and not a labelling for the collection of all the software. No. The version specification refers to the version of the kernel _and_ the operating system (which form a unit maintained by the FreeBSD team). Those typically have to be in sync. Depending on what branch you follow, this can be: a) a static release number, e. g. 8.2-RELEASE b) a release, enriched by security updates, e. g. 8.2-RELEASE-p2 c) a stable version, e. g. 8-STABLE of a specific date (this is work in progress that has been considered working) d) a development version, e. g. 10-CURRENT (this may or _may not_ even compile, it's experimental) Depending on what branch you follow, updating techniques may differ: freebsd-update (the binary way) can be used for a) and b); for c) and d) you update from source. For Linux major distros there usually is a labelling for the collection of the software, independent of the kernel version. Linux doesn't know the differentiation between the operating system (consisting of the OS kernel and the OS programs, the world in FreeBSD terminology) and everything else (third party contributed applications, in FreeBSD provided by the ports collection). On Linux I usually install binaries for the base system and desktop environment, but for important software, in my case it's audio, compiling from source is very important. The ports collection allows both binary installation and by source. There are tools that help managing them. Note that unlike Linux, FreeBSD draws a line between the OS and installed applications - you need to install and update them separately. This is a big benefit as a failed program installation can never harm your OS. The author of the snd_hdspe driver for FreeBSD seems to need testers. It seems to be that nobody ever tested if ADAT is working and I'll test it. OTOH I suspect bug fixes for the driver have to be added by recompiling the kernel or at least the driver for the kernel, so I still could use binaries for the applications. Of course. The separation I've mentioned explicitely allows this method to function. What you need to do is to update your sources in /usr/src and then recompile the kernel and, if required, the world, as explained in /usr/src/Makefile's comment header. Since audio on FreeBSD seems to be a niche, I wonder if it's more promising, to go the source or to go the binary rout. I'd say: Use the source Luke. :-) Experimental changes and bleeding edge updates are typically a domain of source installations. With svn you can track smallest changes very quickly, apply them to your system and have a test run. Doesn't work? Undo the change, or wait for a new version. I suspect if it's impossible or at least less good to mix binaries and from source build software for FreeBSD, I should chose to build from source. Basically there is no problem. One thing you have to pay attention to is dependency versions, but that's what port management tools like portmaster can do for you. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: Upgrading FreeBSD 8.3 amd64
On Tue, 2012-12-18 at 18:42 +0100, Ralf Mardorf wrote: I want to test snd_hdspe. How can I upgrade from 8.2 to a version ^^^8.3 including the driver or something similar to get the driver? Btw. I didn't test, if the driver is part of 8.3 until now :D, but if IIUC I need = 9.0. I'll read http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html can I assume that because I didn't install or updated and configured anything until now, there won't be issues for a version upgrade, if I only configure PPPoE, followed by a release upgrade and after that I'll install software and set up FreeBSD completely? ___ 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: Upgrading FreeBSD 8.3 amd64
On Tue, 18 Dec 2012 18:42:41 +0100, Ralf Mardorf wrote: I want to test snd_hdspe. How can I upgrade from 8.2 to a version including the driver or something similar to get the driver? Btw. I didn't test, if the driver is part of 8.3 until now :D, but if IIUC I need = 9.0. It would probably be the easiest way to update your source tree (using svn as this is the default method today) and re-install from that. I'm not sure freebsd-update can cross the major version border without trouble (never tried). See 25.7 for details: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html But also note that freebsd-update supports a -r version option as explained in 25.2.3: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html But as I said, I've never personally tried that. This approach keeps all your partition settings and doesn't require any other work to be done on that level. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: Upgrading FreeBSD 8.3 amd64
On Tue, 2012-12-18 at 18:57 +0100, Polytropon wrote: On Tue, 18 Dec 2012 18:42:41 +0100, Ralf Mardorf wrote: I want to test snd_hdspe. How can I upgrade from 8.2 to a version including the driver or something similar to get the driver? Btw. I didn't test, if the driver is part of 8.3 until now :D, but if IIUC I need = 9.0. It would probably be the easiest way to update your source tree (using svn as this is the default method today) and re-install from that. I'm not sure freebsd-update can cross the major version border without trouble (never tried). See 25.7 for details: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html But also note that freebsd-update supports a -r version option as explained in 25.2.3: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html But as I said, I've never personally tried that. This approach keeps all your partition settings and doesn't require any other work to be done on that level. Thank you :) I'll read and test it later. Regards, Ralf ___ 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: Upgrading FreeBSD 8.3 amd64
On Tue, 18 Dec 2012 18:54:29 +0100, Ralf Mardorf wrote: On Tue, 2012-12-18 at 18:42 +0100, Ralf Mardorf wrote: I want to test snd_hdspe. How can I upgrade from 8.2 to a version ^^^8.3 including the driver or something similar to get the driver? Btw. I didn't test, if the driver is part of 8.3 until now :D, but if IIUC I need = 9.0. I'll read http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html can I assume that because I didn't install or updated and configured anything until now, there won't be issues for a version upgrade, if I only configure PPPoE, followed by a release upgrade and after that I'll install software and set up FreeBSD completely? Sounds like a valid approach. I've been doing this many times, i. e. first install base system from installation media without additional packages, setup networking (PPPoE in former times, DHCP today), then update the system to the desired version or branch (e. g. -STABLE via source), and then start installing the applications from ports (also updated). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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
Some thoughts about upgrading from 8.3 to 9.1
I just read in another post about disklayout _ According to the manual as of 9.0-RELEASE the default fragment and block sizes for newfs are 4k and 32k, so provided your partitions/slices are 4k aligned everything Should Just Work. Before 9.0 fragments and blocks were 2k and 16k which doesn't play so well with 4k drives. I started thinking about the choices I have for upgrading my running 8.3 systems. I'm aware about of the procedure with freebsd-upgrade and rebuilding all ports according to man portmaster. Would you just do the upgrade or would you consider reinstalling? Would it be beneficial to make a fresh installation? Thanks /Leslie ___ 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: Some thoughts about upgrading from 8.3 to 9.1
Hi, On Tue, 13 Nov 2012 14:00:15 +0100 Leslie Jensen les...@eskk.nu wrote: I just read in another post about disklayout _ According to the manual as of 9.0-RELEASE the default fragment and block sizes for newfs are 4k and 32k, so provided your partitions/slices are 4k aligned everything Should Just Work. Before 9.0 fragments and blocks were 2k and 16k which doesn't play so well with 4k drives. I started thinking about the choices I have for upgrading my running 8.3 systems. I'm aware about of the procedure with freebsd-upgrade and rebuilding all ports according to man portmaster. Would you just do the upgrade or would you consider reinstalling? Would it be beneficial to make a fresh installation? let me phrase it this way: I upgrade always via source but I am prepared to hit a wall between. The number of walls are very low meanwhile. The advantage of a normal upgrade via sources are so many that I always risk it. But I make sure that I have the option of re-installation at hand. Erich ___ 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: Some thoughts about upgrading from 8.3 to 9.1
Leslie Jensen wrote: I just read in another post about disklayout _ According to the manual as of 9.0-RELEASE the default fragment and block sizes for newfs are 4k and 32k, so provided your partitions/slices are 4k aligned everything Should Just Work. Before 9.0 fragments and blocks were 2k and 16k which doesn't play so well with 4k drives. I started thinking about the choices I have for upgrading my running 8.3 systems. I'm aware about of the procedure with freebsd-upgrade and rebuilding all ports according to man portmaster. Would you just do the upgrade or would you consider reinstalling? Would it be beneficial to make a fresh installation? Thanks /Leslie I all ways reinstall from scratch using disc1.iso burned to cdrom as each new OS Release becomes available to the public. Followed by pkg-add -r for all my ports. I even use the pkg versions of dependents that are required by php because I have to recompile the php port to turn on the apache module and turn off everything else. This way I only compile php and not its dependents. I have the pkg_add -r commands embedded in a script that automates the whole procedures. The installed packages stay at whatever version they are at as of new OS Release time. I do not update running packages during the life of the installed OS Release. Been doing this since Release 3.0 without any problems. Install process takes about 30 minutes. Time for downloading disc1.iso and burning it is not included in that 30 minutes. ___ 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: Some thoughts about upgrading from 8.3 to 9.1
On 11/13/12 13:00, Leslie Jensen wrote: I just read in another post about disklayout _ According to the manual as of 9.0-RELEASE the default fragment and block sizes for newfs are 4k and 32k, so provided your partitions/slices are 4k aligned everything Should Just Work. Before 9.0 fragments and blocks were 2k and 16k which doesn't play so well with 4k drives. I wrote that. It's only relevant if you have recent disks with 4k hardware blocks. If you have, you ought to use 4k/16k filesystems whatever your OS rev. If you haven't, it doesn't matter. If it's not broken, don't fix it, is a very good principle. I started thinking about the choices I have for upgrading my running 8.3 systems. I'm aware about of the procedure with freebsd-upgrade and rebuilding all ports according to man portmaster. Would you just do the upgrade or would you consider reinstalling? Would it be beneficial to make a fresh installation? Like Erich Dollansky, I prefer to upgrade via source, but that's because I like tweaking my system in mildly non-standard ways. (More a habit than a necessity, but I've been doing it since 6th Edition Unix. :-) If you're running a vanilla install with GENERIC kernel freebsd-upgrade is probably going to be quicker even if you've got a multicore monster to recompile on. Just make sure you can reinstall if something goes bad during the upgrade and *back up anything vital first*. ___ 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: Some thoughts about upgrading from 8.3 to 9.1
On 11/13/12 14:21, Arthur Chance wrote: Oops, sent this off too quickly. I wrote that. It's only relevant if you have recent disks with 4k hardware blocks. If you have, you ought to use 4k/16k filesystems whatever your OS rev. That should be 4k/32k. As man newfs says: The optimal block:fragment ratio is 8:1. Other ratios are possible, but are not recommended, and may produce poor results. ___ 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
Upgrading Using FreeBSD Update
Hi there, I am going to upgrade my FreeBSD 8.2-RELEASE to 9.1-RELEASE according to http://www.freebsd.org/releases/9.0R/installation.html However, I don't know how to follow the step below: ##start here## # freebsd-update install At this point, users of systems being upgraded from FreeBSD 8.2-RELEASE or earlier will be prompted by freebsd-update(8) to rebuild all third-party applications (e.g., ports installed from the ports tree) due to updates in system libraries. After updating installed third-party applications (and again, only if freebsd-update(8) printed a message indicating that this was necessary), run freebsd-update(8) again so that it can delete the old (no longer used) system libraries: ##end here## My questions is: how to rebuild all third-party applications? I have kept the ports tree up to date using # portsnap fetch update and # portmaster -Ga every day. Any help will be really appreciated. Regards, Jinsong ___ 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: Upgrading Using FreeBSD Update
Jinsong Zhao jszhao at yeah.net writes: ... My questions is: how to rebuild all third-party applications? I have kept the ports tree up to date using # portsnap fetch update and # portmaster -Ga every day. ... I would advise you to drop -G option and use these entries: # portsnap fetch update # portmaster -f portmaster # portmaster -a -f Ref: PORTMASTER(8) Examples. jb ___ 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: Upgrading Using FreeBSD Update
Hi, My questions is: how to rebuild all third-party applications? I have kept the ports tree up to date using # portsnap fetch update and # portmaster -Ga every day. ... I would advise you to drop -G option and use these entries: # portsnap fetch update # portmaster -f portmaster # portmaster -a -f Ref: PORTMASTER(8) Examples. jb Thank you very much for your reply and the Ref to PORTMASTER(8). The last example in the man page may be what I want during the upgrade to FreeBSD 9.0-RELEASE. Regards, Jinsong ___ 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: ZFS / Boot Environments / Jails / Upgrading form Source Code
On 19/10/2012 07:44, dweimer wrote: First step replace the usr/src within the jail with new source using svn, easy enough. Then start make buildworld... oops, I have a problem now, the usr/obj/usr stuff is now under /usr/obj/usr/jails/release91rc2..., However I want it to be under /usr/jails/release91rc2/usr/obj/usr. If the jails base dir is /usr/obj/usr/jails/release91rc2 then it can only access files below that base dir. That is part of the jails security. If your jail is based at /usr/obj/usr/jails/release91rc2 then the jail by default will buildworld into /usr/obj of the jail system which translates to /usr/obj/usr/jails/release91rc2/usr/obj on the base system. You can adjust the settings within the jail but it will always be within the release91rc2 dir so you can't use the jail to install into /usr/jails of the base system. From looking at the usr/src/Makefile It looks like I need to set the MAKEOBJDIRPREFIX=/usr/jails/relase91rc2/usr/obj/usr/src/tmp environment variable, but is that the best solution here? There's also a /usr/obj/lib32 directory (system is running amd64, I assume this is for 32 bit libraries), so I would likely need to do something here as well, that I haven't gotten to yet. lib32 is part of the final system - you don't need to handle it separately. See man src.conf if you want to turn off the creation of 32bit libs. You can set MAKEOBJDIRPREFIX (default /usr/obj ) to define where the binary files are made. You can also set DESTDIR (default is / ) for the installworld step to define where they get installed. When you start a buildworld or buildkernel the compiled binaries are stored within MAKEOBJDIRPREFIX. When that is complete the installworld or installkernel steps install the files from MAKEOBJDIRPREFIX into DESTDIR to create a workable system. That prevents a failed build from destroying part of your running system. If you want to experiment with different versions then you can also try- mkdir /usr/jails cd /usr/jails svn co http://svn0.us-west.FreeBSD.org/base/releng/9.0 9.0-src cd 9.0-src set MAKEOBJDIRPREFIX = /usr/jails/9.0-obj set DESTDIR = /usr/jails/9.0-base make buildworld make installworld cd /usr/jails svn co http://svn0.us-east.FreeBSD.org/base/releng/9.1 9.1-src cd 9.1-src set MAKEOBJDIRPREFIX = /usr/jails/9.1-obj set DESTDIR = /usr/jails/9.1-base make buildworld make installworld I know the /usr/obj/usr directory can be deleted after the installation of the source, does the same go for the /usr/obj/lib32 directory? if so Anything in MAKEOBJDIRPREFIX (/usr/obj) can be deleted after you have installed it, including lib32 which are libs to allow running 32bit programs on a 64bit system. ___ 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: ZFS / Boot Environments / Jails / Upgrading form Source Code
On 2012-10-19 02:48, Shane Ambler wrote: On 19/10/2012 07:44, dweimer wrote: First step replace the usr/src within the jail with new source using svn, easy enough. Then start make buildworld... oops, I have a problem now, the usr/obj/usr stuff is now under /usr/obj/usr/jails/release91rc2..., However I want it to be under /usr/jails/release91rc2/usr/obj/usr. If the jails base dir is /usr/obj/usr/jails/release91rc2 then it can only access files below that base dir. That is part of the jails security. If your jail is based at /usr/obj/usr/jails/release91rc2 then the jail by default will buildworld into /usr/obj of the jail system which translates to /usr/obj/usr/jails/release91rc2/usr/obj on the base system. You can adjust the settings within the jail but it will always be within the release91rc2 dir so you can't use the jail to install into /usr/jails of the base system. The base of the Jail, is /usr/jails/release91rc2, however, I did forget to mention that I was running the buildworld and buildkernel from the base system, with the intent to install using the DESTDIR=/usr/jails/release91rc2 command line option From looking at the usr/src/Makefile It looks like I need to set the MAKEOBJDIRPREFIX=/usr/jails/relase91rc2/usr/obj/usr/src/tmp environment variable, but is that the best solution here? There's also a /usr/obj/lib32 directory (system is running amd64, I assume this is for 32 bit libraries), so I would likely need to do something here as well, that I haven't gotten to yet. lib32 is part of the final system - you don't need to handle it separately. See man src.conf if you want to turn off the creation of 32bit libs. Got it, Fine with leaving it there, just wanted to know if there was a separate option to define where it ended up. You can set MAKEOBJDIRPREFIX (default /usr/obj ) to define where the binary files are made. You can also set DESTDIR (default is / ) for the installworld step to define where they get installed. It appears I went to deep on my definition of the MAKOBJDIRPREFIX, made the above path after seeing some output at the start of one of my buildworld attempts, which is what led me to believe there would be a second choice. When you start a buildworld or buildkernel the compiled binaries are stored within MAKEOBJDIRPREFIX. When that is complete the installworld or installkernel steps install the files from MAKEOBJDIRPREFIX into DESTDIR to create a workable system. That prevents a failed build from destroying part of your running system. If you want to experiment with different versions then you can also try- mkdir /usr/jails cd /usr/jails svn co http://svn0.us-west.FreeBSD.org/base/releng/9.0 9.0-src cd 9.0-src set MAKEOBJDIRPREFIX = /usr/jails/9.0-obj set DESTDIR = /usr/jails/9.0-base make buildworld make installworld cd /usr/jails svn co http://svn0.us-east.FreeBSD.org/base/releng/9.1 9.1-src cd 9.1-src set MAKEOBJDIRPREFIX = /usr/jails/9.1-obj set DESTDIR = /usr/jails/9.1-base make buildworld make installworld Here was the key information I needed, found several examples searching but none stated the MAKEOBJDIRPREFIX=, as you state below they are not needed for the running system, guessing most people clean them up afterwards so they aren't concerned they don't exist in the same boot environment in the end. I prefer to keep them in the same boot environment if possible, just so that if I delete a boot environment I know I got rid of everything that belonged to it and don't end up uselessly eating up extra disk space. I do delete the /usr/obj/usr directory prior to any rebuild, from old documentation I read when I first started doing source upgrades as a method of improving the speed of the buildworld. I am sure those were written for a 32bit system, which is why the lib32 directory wasn't included in those instructions. I know the /usr/obj/usr directory can be deleted after the installation of the source, does the same go for the /usr/obj/lib32 directory? if so Anything in MAKEOBJDIRPREFIX (/usr/obj) can be deleted after you have installed it, including lib32 which are libs to allow running 32bit programs on a 64bit system. Looks like I am on the right path, now time to give it a try with the new environment variables, thanks for your help Shane. If all goes well on this step, only things I have left to figured out and test is creating zfs snapshots by hand of volumes outside my boot environment, and mounting those read write within the jailed systems base so that I can fully test my applications against the latest live data without changing the actual data. Don't expect to have any trouble with this one. And then last of all need to test removing a HD from my Virtual Machine, adding a replacement, and rebuilding the mirror, again don't expect this to be a problem, just need to work my way through them and get the steps down before I am comfortable doing these procedures on a system that
Re: Problem upgrading
On Wed, Oct 17, 2012 at 02:14:10PM -0700, Timothy Snowberger wrote: On 10/17/2012 7:27 AM, Jim Trigg wrote: Any suggestions on how to fix this? --- argent(1) /usr/ports/ports-mgmt/portmaster# freebsd-update -r 9.0-RELEASE upgrade Does this look reasonable (y/n)? y ... Fetching metadata signature for 9.0-RELEASE from update5.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. The update metadata is correctly signed, but failed an integrity check. Cowardly refusing to proceed any further. sed -i '' -e 's/=_/=%@_/' /usr/sbin/freebsd-update See http://lists.freebsd.org/pipermail/freebsd-stable/2011-October/064321.html First, a minor change must be made to the freebsd-update code in order for it to accept file names appearing in FreeBSD 9.0 which contain the '%' and '@' characters; without this change, freebsd-update will error out with the message The update metadata is correctly signed, but failed an integrity check. This fixed it. Thanks, Jim ___ 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
ZFS / Boot Environments / Jails / Upgrading form Source Code
I have been playing around with different build layouts etc trying to come up with a plan to make updates smoother and more easily recoverable if it goes horribly wrong. I think I have almost figured things out, just have a couple things left to figure out, one of which I am hoping someone on this list can help em out with, to save me some trial an error. Steps already figured out, mount new boot environment (using 9.1rc2 to test with) in /usr/jails/release91rc2, added the necessary settings to rc.conf, started jail, so far so good. I now know I can run the boot environment from within the jail, stop the jail and begin the upgrade from source. First step replace the usr/src within the jail with new source using svn, easy enough. Then start make buildworld... oops, I have a problem now, the usr/obj/usr stuff is now under /usr/obj/usr/jails/release91rc2..., However I want it to be under /usr/jails/release91rc2/usr/obj/usr. From looking at the usr/src/Makefile It looks like I need to set the MAKEOBJDIRPREFIX=/usr/jails/relase91rc2/usr/obj/usr/src/tmp environment variable, but is that the best solution here? There's also a /usr/obj/lib32 directory (system is running amd64, I assume this is for 32 bit libraries), so I would likely need to do something here as well, that I haven't gotten to yet. I know the /usr/obj/usr directory can be deleted after the installation of the source, does the same go for the /usr/obj/lib32 directory? if so perhaps it is a better option to make a new zfs data set outside the boot environments to mount under /usr/obj directory, let the default prefixes handle which sub directory to use, and just delete the directories when I am done working with the boot environment. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ 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
Problem upgrading
Any suggestions on how to fix this? --- argent(1) /usr/ports/ports-mgmt/portmaster# freebsd-update -r 9.0-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 8.2-RELEASE from update5.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata files... done. Inspecting system... done. The following components of FreeBSD seem to be installed: kernel/generic src/base src/bin src/cddl src/contrib src/crypto src/etc src/games src/gnu src/include src/krb5 src/lib src/libexec src/release src/rescue src/sbin src/secure src/share src/sys src/tools src/ubin src/usbin world/base world/dict world/doc world/games world/info world/manpages world/proflibs The following components of FreeBSD do not seem to be installed: world/catpages Does this look reasonable (y/n)? y Fetching metadata signature for 9.0-RELEASE from update5.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. The update metadata is correctly signed, but failed an integrity check. Cowardly refusing to proceed any further. --- Thanks, Jim ___ 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: Problem upgrading
On 10/17/2012 7:27 AM, Jim Trigg wrote: Any suggestions on how to fix this? --- argent(1) /usr/ports/ports-mgmt/portmaster# freebsd-update -r 9.0-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 8.2-RELEASE from update5.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata files... done. Inspecting system... done. The following components of FreeBSD seem to be installed: kernel/generic src/base src/bin src/cddl src/contrib src/crypto src/etc src/games src/gnu src/include src/krb5 src/lib src/libexec src/release src/rescue src/sbin src/secure src/share src/sys src/tools src/ubin src/usbin world/base world/dict world/doc world/games world/info world/manpages world/proflibs The following components of FreeBSD do not seem to be installed: world/catpages Does this look reasonable (y/n)? y Fetching metadata signature for 9.0-RELEASE from update5.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. The update metadata is correctly signed, but failed an integrity check. Cowardly refusing to proceed any further. --- Thanks, Jim ___ 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 sed -i '' -e 's/=_/=%@_/' /usr/sbin/freebsd-update See http://lists.freebsd.org/pipermail/freebsd-stable/2011-October/064321.html First, a minor change must be made to the freebsd-update code in order for it to accept file names appearing in FreeBSD 9.0 which contain the '%' and '@' characters; without this change, freebsd-update will error out with the message The update metadata is correctly signed, but failed an integrity check. ___ 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: problems upgrading from 7.2-RELEASE-p8 to 7.4 or 9.0-RELEASE
[ Greg Larkin wrote on Thu 11.Oct'12 at 20:49:19 -0400 ] Hi Stuart, If you click the link in this mailing list article (http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218554.html), then follow the rest of the threaded messages, you should be able fix the problem once you upgrade to 7.4. The issue is that freebsd-update cannot update the ld-elf.so.1 binary on a running system, so after the upgrade to 7.4 (or higher), the system is not completely updated. This message (http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218884.html) has a fix, but it involves booting from a liveCD and replacing the binary manually. Would it be easier to do an update by building from source? I've never used freebsd-update myself so not had to troubleshoot these issues before. ___ 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: problems upgrading from 7.2-RELEASE-p8 to 7.4 or 9.0-RELEASE
On 10/12/2012 10:53 AM, Jamie Paul Griffin wrote: [ Greg Larkin wrote on Thu 11.Oct'12 at 20:49:19 -0400 ] Hi Stuart, If you click the link in this mailing list article (http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218554.html), then follow the rest of the threaded messages, you should be able fix the problem once you upgrade to 7.4. The issue is that freebsd-update cannot update the ld-elf.so.1 binary on a running system, so after the upgrade to 7.4 (or higher), the system is not completely updated. This message (http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218884.html) has a fix, but it involves booting from a liveCD and replacing the binary manually. Would it be easier to do an update by building from source? I've never used freebsd-update myself so not had to troubleshoot these issues before. That's probably the best way. Bit I am wondering about this. I upgraded several systems (physical and virtual machines) with freebsd-update from 7.1 - 7.3 - 8.1 - 8.3 and also one system from 7.1 - 7.4 (with custom kernels) and did not encounter this. Did I just get lucky then? This e-mail message, including any attachment(s), is intended solely for the addressee or addressees. Any views or opinions presented herein are solely those of the author and do not necessarily represent those of OSE. If you are not the intended recipient of this communication please return this e-mail message and the attachment(s) to the sender and delete and destroy all copies. ___ 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: problems upgrading from 7.2-RELEASE-p8 to 7.4 or 9.0-RELEASE
[ Bas Smeelen wrote on Fri 12.Oct'12 at 11:02:47 +0200 ]
On 10/12/2012 10:53 AM, Jamie Paul Griffin wrote:
[ Greg Larkin wrote on Thu 11.Oct'12 at 20:49:19 -0400 ]
Hi Stuart,
If you click the link in this mailing list article
(http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218554.html),
then follow the rest of the threaded messages, you should be able fix
the problem once you upgrade to 7.4.
The issue is that freebsd-update cannot update the ld-elf.so.1 binary
on a running system, so after the upgrade to 7.4 (or higher), the
system is not completely updated.
This message
(http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218884.html)
has a fix, but it involves booting from a liveCD and replacing the
binary manually.
Would it be easier to do an update by building from source? I've never used
freebsd-update myself so not had to troubleshoot these issues before.
That's probably the best way.
Bit I am wondering about this.
I upgraded several systems (physical and virtual machines) with
freebsd-update from 7.1 - 7.3 - 8.1 - 8.3 and also one system from 7.1 -
7.4 (with custom kernels) and did not encounter this. Did I just get lucky
then?
I couldn't comment on the freebsd-update(8) procedure as I've never used it.
But I'd personally upgrade the system by building from source. You can then
easily integrate your custom kernel and I would *imagine* you'd avoid the
issues you've encountered so far.
Make sure you read /usr/src/UPDATING thoroughly, and also check your customer
kernel options. Some changes have been made to more recent versions of FreeBSD,
such as the ata(4) driver. I believe in the past certain elements could be (and
still can be) added in a modular fasion, explicitly setting each element. Now,
you only need to have: device scbus, device ata and options ATA_CAM. Already
present in the GENERIC kernel config now. See man 4 ata for details. I hope
i've got that right, hopefully others will correct my comments if necessary but
in any case, reading the appropriate files will provide all the information
needed. For example: /usr/src/sys/conf/NOTES and
/usr/src/sys/{i386,amd64}/NOTES have more information about kernel options that
might be helpful and of interest to you.
___
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: problems upgrading from 7.2-RELEASE-p8 to 7.4 or 9.0-RELEASE
Hi Greg, Thanks for the tips. I'll be able to retry the upgrade this weekend. - Stu On 10/11/2012 5:49 PM, Greg Larkin wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/11/12 2:43 PM, Stuart Matthews wrote: Hi everyone, I am including as much information in here as I think will be useful. Since I can do snapshots on VMWare, I am happy to try any solution or diagnostics. Steps I took to upgrade FreeBSD: Using freebsd-update, I upgraded from 7.2-RELEASE to 7.2-RELEASE-p8 Then, to upgrade to 9.0-RELEASE, I ran the following commands, using http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html as my guide: freebsd-update -r 9.0-RELEASE upgrade freebsd-update install reboot freebsd-update install portupgrade -f ruby rm /var/db/pkg/pkgdb.db portupgrade -f ruby18-bdb rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db portupgrade -af freebsd-update install reboot I noticed that lots of things weren't working, and specifically that I was getting lots of complaints about /libexec/ld-elf.so.1. I also noticed that when I ran freebsd-update IDS, it seemed to report that every single file had the wrong signature. So, this being a VMWare guest, I reluctantly reverted to a previous snapshot, putting me back at 7.2-RELEASE-p8. I decided to try this time to go from 7.2-RELEASE-p8 to 7.4-RELEASE to 8.0-RELEASE to 8.3-RELEASE. I only got to 7.4-RELEASE before I had the same issues as above. As a specific example of errors I would get, I try to run sudo and I get: [stuart@richelieu ~]$ sudo bash /libexec/ld-elf.so.1: sudo: invalid PT_PHDR This seems to be the most relevant thread to the problem I'm having: http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218443.html However, I'd be more comfortable using an official upgrade path, like freebsd-update, exclusively. That thread involves replacing a file from a FreeBSD liveCD. Also, with freebsd-update IDS reporting so many files with incorrect signatures, I feel like my problem is bigger than fixing one file. Right now I am back on 7.2-RELEASE-p8 eager to get my OS upgraded to something that is under current support by the security team. Optimally I'd like to be on 8.3 after looking at the EOL dates. Also, I did see one other post _somewhere_ mentioning a similar proble also on a VMWare guest. So I am suspicious that the problem might be related to VMWare. Thanks, everyone. - Stuart Matthews Hi Stuart, If you click the link in this mailing list article (http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218554.html), then follow the rest of the threaded messages, you should be able fix the problem once you upgrade to 7.4. The issue is that freebsd-update cannot update the ld-elf.so.1 binary on a running system, so after the upgrade to 7.4 (or higher), the system is not completely updated. This message (http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218884.html) has a fix, but it involves booting from a liveCD and replacing the binary manually. Hope that helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlB3aQ8ACgkQ0sRouByUApAj2QCgjZZKHLHa04PM3qhtKfwuzJpq D0MAn3uolwsr/ukwGSxLXK42410IfMt8 =JiOa -END PGP SIGNATURE- ___ 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
problems upgrading from 7.2-RELEASE-p8 to 7.4 or 9.0-RELEASE
Hi everyone, I am including as much information in here as I think will be useful. Since I can do snapshots on VMWare, I am happy to try any solution or diagnostics. Steps I took to upgrade FreeBSD: Using freebsd-update, I upgraded from 7.2-RELEASE to 7.2-RELEASE-p8 Then, to upgrade to 9.0-RELEASE, I ran the following commands, using http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html as my guide: freebsd-update -r 9.0-RELEASE upgrade freebsd-update install reboot freebsd-update install portupgrade -f ruby rm /var/db/pkg/pkgdb.db portupgrade -f ruby18-bdb rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db portupgrade -af freebsd-update install reboot I noticed that lots of things weren't working, and specifically that I was getting lots of complaints about /libexec/ld-elf.so.1. I also noticed that when I ran freebsd-update IDS, it seemed to report that every single file had the wrong signature. So, this being a VMWare guest, I reluctantly reverted to a previous snapshot, putting me back at 7.2-RELEASE-p8. I decided to try this time to go from 7.2-RELEASE-p8 to 7.4-RELEASE to 8.0-RELEASE to 8.3-RELEASE. I only got to 7.4-RELEASE before I had the same issues as above. As a specific example of errors I would get, I try to run sudo and I get: [stuart@richelieu ~]$ sudo bash /libexec/ld-elf.so.1: sudo: invalid PT_PHDR This seems to be the most relevant thread to the problem I'm having: http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218443.html However, I'd be more comfortable using an official upgrade path, like freebsd-update, exclusively. That thread involves replacing a file from a FreeBSD liveCD. Also, with freebsd-update IDS reporting so many files with incorrect signatures, I feel like my problem is bigger than fixing one file. Right now I am back on 7.2-RELEASE-p8 eager to get my OS upgraded to something that is under current support by the security team. Optimally I'd like to be on 8.3 after looking at the EOL dates. Also, I did see one other post _somewhere_ mentioning a similar problem, also on a VMWare guest. So I am suspicious that the problem might be related to VMWare. Thanks, everyone. - Stuart Matthews ___ 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: problems upgrading from 7.2-RELEASE-p8 to 7.4 or 9.0-RELEASE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/11/12 2:43 PM, Stuart Matthews wrote: Hi everyone, I am including as much information in here as I think will be useful. Since I can do snapshots on VMWare, I am happy to try any solution or diagnostics. Steps I took to upgrade FreeBSD: Using freebsd-update, I upgraded from 7.2-RELEASE to 7.2-RELEASE-p8 Then, to upgrade to 9.0-RELEASE, I ran the following commands, using http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html as my guide: freebsd-update -r 9.0-RELEASE upgrade freebsd-update install reboot freebsd-update install portupgrade -f ruby rm /var/db/pkg/pkgdb.db portupgrade -f ruby18-bdb rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db portupgrade -af freebsd-update install reboot I noticed that lots of things weren't working, and specifically that I was getting lots of complaints about /libexec/ld-elf.so.1. I also noticed that when I ran freebsd-update IDS, it seemed to report that every single file had the wrong signature. So, this being a VMWare guest, I reluctantly reverted to a previous snapshot, putting me back at 7.2-RELEASE-p8. I decided to try this time to go from 7.2-RELEASE-p8 to 7.4-RELEASE to 8.0-RELEASE to 8.3-RELEASE. I only got to 7.4-RELEASE before I had the same issues as above. As a specific example of errors I would get, I try to run sudo and I get: [stuart@richelieu ~]$ sudo bash /libexec/ld-elf.so.1: sudo: invalid PT_PHDR This seems to be the most relevant thread to the problem I'm having: http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218443.html However, I'd be more comfortable using an official upgrade path, like freebsd-update, exclusively. That thread involves replacing a file from a FreeBSD liveCD. Also, with freebsd-update IDS reporting so many files with incorrect signatures, I feel like my problem is bigger than fixing one file. Right now I am back on 7.2-RELEASE-p8 eager to get my OS upgraded to something that is under current support by the security team. Optimally I'd like to be on 8.3 after looking at the EOL dates. Also, I did see one other post _somewhere_ mentioning a similar proble also on a VMWare guest. So I am suspicious that the problem might be related to VMWare. Thanks, everyone. - Stuart Matthews Hi Stuart, If you click the link in this mailing list article (http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218554.html), then follow the rest of the threaded messages, you should be able fix the problem once you upgrade to 7.4. The issue is that freebsd-update cannot update the ld-elf.so.1 binary on a running system, so after the upgrade to 7.4 (or higher), the system is not completely updated. This message (http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218884.html) has a fix, but it involves booting from a liveCD and replacing the binary manually. Hope that helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlB3aQ8ACgkQ0sRouByUApAj2QCgjZZKHLHa04PM3qhtKfwuzJpq D0MAn3uolwsr/ukwGSxLXK42410IfMt8 =JiOa -END PGP SIGNATURE- ___ 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
Serial console getty broken after upgrading to 9.1-RC2
Hello all, I had a working serial console setup on Freebsd 9.0 for remote access via my HP server's BMC serial console. I recently built and installed 9.1-RC2 on a separate dataset on this machine's ZFS pool and merged in my existing configuration from 9.0. On 9.1-RC2 I no longer get a login prompt. However, I still do have access to the loader prompt and can see the kernel boot messages on the serial console. I built my GENERIC kernel and world using clang with default flags. I see that the kernel identifies the serial port getty has spawned on the port. # dmesg |grep uart uart0: 16550 or compatible port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: console (115200,n,8,1) # ps axl|grep ttyu0 0 54051 0 20 0 11996 1416 ttyinIs+ u00:00.00 /usr/libexec/getty std.115200 ttyu0 Here are the relevant configuration bits I copied over from 9.0 setup that works: /etc/ttys: ttyu0 /usr/libexec/getty std.115200 screen-256color on secure /boot/loader.conf: boot_multicons=YES boot_serial=YES comconsole_speed=115200 console=comconsole,vidconsole # kenv |grep uart.0 hint.uart.0.at=isa hint.uart.0.flags=0x10 hint.uart.0.irq=4 hint.uart.0.port=0x3F8 Have there been any changes to the serial console setup in 9.1 or has anybody else experienced similar problems? __ Thanks, Ziyan. ___ 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
Problem upgrading misc/help2man: missing language files
I am unable to upgrade misc/help2man, required by autoconf and other ports that I want to upgrade that depend on perl and/or png. Currently installed version of help2man is 1.40.12 and new version is 1.40.13 I get a bundle of error messages like Extracting help2man (with variable substitutions) === Creating a backup package for old version help2man-1.40.12 tar: lib/bindtextdomain.so: Cannot stat: No such file or directory tar: share/locale/de/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/el/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/eo/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/fi/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/fr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/hr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/it/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/pl/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/pt_BR/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/ru/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/sr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/sv/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/uk/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/vi/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/ja/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: man/de/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/el/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/eo/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/fi/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/fr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/hr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/it/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/pl/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/pt_BR/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/ru/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/sr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/sv/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/uk/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/vi/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/ja/man1/help2man.1.gz: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 So here I am stuck. I don't know whether the fault is with my installed help2man-1.40.12 or the distfile for 1.40.13. How do I get past this impasse? I suppose I could use -x misc/help2man in portmaster commands, but don't really want to do that if 1.40.13 is good but my installation of 1.40.12 is corrupted. Tom ___ 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: Problem upgrading misc/help2man: missing language files
On 10/02/2012 10:59 AM, Thomas Mueller wrote: I am unable to upgrade misc/help2man, required by autoconf and other ports that I want to upgrade that depend on perl and/or png. Currently installed version of help2man is 1.40.12 and new version is 1.40.13 I get a bundle of error messages like Extracting help2man (with variable substitutions) === Creating a backup package for old version help2man-1.40.12 tar: lib/bindtextdomain.so: Cannot stat: No such file or directory tar: share/locale/de/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/el/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/eo/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/fi/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/fr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/hr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory Hi Tom Isn't this just the creation of the backup package that fails? I encounter errors like this sometimes, but portmaster goed on installing the newer version. tar: share/locale/it/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/pl/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/pt_BR/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/ru/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/sr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/sv/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/uk/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/vi/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/ja/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: man/de/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/el/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/eo/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/fi/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/fr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/hr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/it/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/pl/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/pt_BR/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/ru/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/sr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/sv/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/uk/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/vi/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/ja/man1/help2man.1.gz: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 So here I am stuck. I don't know whether the fault is with my installed help2man-1.40.12 or the distfile for 1.40.13. Stuck? Or does portmaster continue as it should? How do I get past this impasse? I suppose I could use -x misc/help2man in portmaster commands, but don't really want to do that if 1.40.13 is good but my installation of 1.40.12 is corrupted. Tom ___ 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 -- Systeembeheerder OverNite Software Europe BV Dr. Nolenslaan 157 6136 GM Sittard THE NETHERLANDS phone: +31464200933 fax: +31464200934 web: http://www.ose.nl Disclaimer: http://www.ose.nl/email ___ 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: Problem upgrading misc/help2man: missing language files
On 10/02/2012 10:59 AM, Thomas Mueller wrote: I am unable to upgrade misc/help2man, required by autoconf and other ports that I want to upgrade that depend on perl and/or png. Currently installed version of help2man is 1.40.12 and new version is 1.40.13 I get a bundle of error messages like Extracting help2man (with variable substitutions) === Creating a backup package for old version help2man-1.40.12 Below it looks like the creation of the backup package fails, which get's deleted by default after the new port is installed. I Just update ports on a CURRENT server with csup from cvsup4.nl.FreeBSD.org and the help2man version is still 1.40.12 I will go ahead and update from cvsup9.freebsd.org . . . No help2man-1.40.13 yet. Maybe csup the portstree again and retry portmaster misc/help2man? Did portmaster end with lines like Upgrade of help2man-1.40.11 to help2man-1.40.12 But then help2man-1.40.12 to help2man-1.40.13 instead of the above? The it should be OK. ** http://lists.freebsd.org/mailman/listinfo/svn-ports-all tar: lib/bindtextdomain.so: Cannot stat: No such file or directory tar: share/locale/de/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/el/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/eo/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/fi/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/fr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/hr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/it/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/pl/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/pt_BR/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/ru/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/sr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/sv/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/uk/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/vi/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/ja/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: man/de/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/el/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/eo/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/fi/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/fr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/hr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/it/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/pl/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/pt_BR/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/ru/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/sr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/sv/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/uk/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/vi/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/ja/man1/help2man.1.gz: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 So here I am stuck. I don't know whether the fault is with my installed help2man-1.40.12 or the distfile for 1.40.13. How do I get past this impasse? I suppose I could use -x misc/help2man in portmaster commands, but don't really want to do that if 1.40.13 is good but my installation of 1.40.12 is corrupted. Tom ___ 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 -- Systeembeheerder OverNite Software Europe BV Dr. Nolenslaan 157 6136 GM Sittard THE NETHERLANDS phone: +31464200933 fax: +31464200934 web: http://www.ose.nl Disclaimer: http://www.ose.nl/email ___ 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
Problem upgrading fbsd-7.4 -- 8.3
Am trying to upgrade fbsd-7.4 to 8.3. I get all the way through the usual procedure using sources, including installworld, when I attempt to run mergemaster as the final step, I get this fatal error. I've searched the list and google, but don't find the right answer. What am I possibly doing wrong and what should I do to get around this? The error: mail# mergemaster -viF *** Creating the temporary root environment in /var/tmp/temproot *** /var/tmp/temproot ready for use *** Creating and populating directory structure in /var/tmp/temproot *** Press the [Enter] or [Return] key to continue *** FATAL ERROR: Cannot 'cd' to /usr/src and install files to the temproot environment -- -- All the best, Jack ___ 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
SOLVED: Re: Error after upgrading to php 5.4.6
This is now solved after an update to pecl-APC-3.1.13 Disclaimer: http://www.ose.nl/email ___ 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: Error after upgrading to php 5.4.6
On 09/04/2012 04:18 AM, Michael Powell wrote: Paul Macdonald wrote: On 03/09/2012 12:26, Darrell Betts wrote: My php pages will no longer render in a web browser after upgrading to php 5.4.6. Used port upgrade to do this. Running apache 2.2.22_6. Checked the error log and this is what I receive [notice] child pid 38232 exit signal Segmentation fault (11) This does this on all php pages. Any idea how to fix this error? [snip] try editing your /usr/local/etc/php/extensions.ini, comment out all extensions (restart apache) and see if it stops seg faulting. If it works, add in the modules one by one until it stops. Previously i've seen people posting about the order being important Some while back I thought portupgrading PHP caused the extensions.ini to be edited after each and every extension rebuild/reinstall, causing a shuffle like effect. Since I do a backup before, including all configs, I got into the habit of just copying my old extensions.ini back into place afterwards prior to restarting PHP and/or web servers. -Mike Well with pkg_delete -f php5\* , removing all of php's config files in /usr/local/etc (keeping a backup of course) and then installing php-5.4.6 extensions resolved the problem. It does not happen too often that this goes wrong, but somehow php can be troublesome at times. Thanks Bas Disclaimer: http://www.ose.nl/email ___ 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: Error after upgrading to php 5.4.6
On 09/04/2012 04:18 AM, Michael Powell wrote: Paul Macdonald wrote: On 03/09/2012 12:26, Darrell Betts wrote: My php pages will no longer render in a web browser after upgrading to php 5.4.6. Used port upgrade to do this. Running apache 2.2.22_6. Checked the error log and this is what I receive [notice] child pid 38232 exit signal Segmentation fault (11) This does this on all php pages. Any idea how to fix this error? [snip] try editing your /usr/local/etc/php/extensions.ini, comment out all extensions (restart apache) and see if it stops seg faulting. If it works, add in the modules one by one until it stops. Previously i've seen people posting about the order being important Some while back I thought portupgrading PHP caused the extensions.ini to be edited after each and every extension rebuild/reinstall, causing a shuffle like effect. Since I do a backup before, including all configs, I got into the habit of just copying my old extensions.ini back into place afterwards prior to restarting PHP and/or web servers. -Mike My previous response was sent too early :( I still get errors in apache [Tue Sep 04 08:14:42 2012] [error] [client 192.168.1.189] PHP Warning: Unknown: Unable to allocate memory for pool. in Unknown on line 0, referer: http://sys.ose.nl/cacti/graph_view.php?action=treetree_id=1leaf_id=21 [Tue Sep 04 08:14:43 2012] [notice] child pid 56172 exit signal Segmentation fault (11) [Tue Sep 04 08:14:43 2012] [notice] child pid 56163 exit signal Segmentation fault (11) [Tue Sep 04 08:14:53 2012] [error] [client 192.168.1.189] PHP Warning: Unknown: Unable to allocate memory for pool. in Unknown on line 0, referer: http://sys.ose.nl/cacti/graph_view.php?action=treetree_id=1leaf_id=7 [Tue Sep 04 08:15:59 2012] [notice] child pid 56169 exit signal Segmentation fault (11) So now I will comment out all extensions and start investigating. Well it turns out to be apc.so, this comes with core php I guess? For completeness: The php manual states this is for alternative php cache. http://php.net/manual/en/book.apc.php With apc.so commented out and testing with cacti and mediawiki all seems to go well. My extensions.ini follows below extension=pdf.so extension=imagick.so ;extension=apc.so extension=hash.so extension=phar.so extension=zip.so extension=zlib.so extension=iconv.so extension=mysql.so extension=pdo.so extension=pdo_sqlite.so extension=sqlite3.so extension=json.so extension=tokenizer.so extension=filter.so extension=posix.so extension=ctype.so extension=dom.so extension=simplexml.so extension=xml.so extension=xmlreader.so extension=xmlwriter.so extension=session.so Disclaimer: http://www.ose.nl/email ___ 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: Error after upgrading to php 5.4.6
Bas Smeelen wrote: [snip] My previous response was sent too early :( I still get errors in apache [Tue Sep 04 08:14:42 2012] [error] [client 192.168.1.189] PHP Warning: Unknown: Unable to allocate memory for pool. in Unknown on line 0, referer: http://sys.ose.nl/cacti/graph_view.php?action=treetree_id=1leaf_id=21 [Tue Sep 04 08:14:43 2012] [notice] child pid 56172 exit signal [Segmentation fault (11) [Tue Sep 04 08:14:43 2012] [notice] child pid 56163 exit signal [Segmentation fault (11) [Tue Sep 04 08:14:53 2012] [error] [client 192.168.1.189] PHP Warning: Unknown: Unable to allocate memory for pool. in Unknown on line 0, referer: http://sys.ose.nl/cacti/graph_view.php?action=treetree_id=1leaf_id=7 [Tue Sep 04 08:15:59 2012] [notice] child pid 56169 exit signal [Segmentation fault (11) So now I will comment out all extensions and start investigating. Well it turns out to be apc.so, this comes with core php I guess? For completeness: The php manual states this is for alternative php cache. http://php.net/manual/en/book.apc.php I use xcache. However, whenever I rebuild PHP I also rebuild xcache. Sometimes when the change is very small you may get away with not doing it, but whenever updating between major versions it is a must. I had this happen one time too many and just got into the habit of whenever I rebuild/update PHP I rebuild xcache as well. I believe it pulls in includes form PHP during it's build process so if PHP changes too much xcache will segfault, or just outright refuse to load. [snip] ___ 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
SOLVED: Re: Error after upgrading to php 5.4.6
On 09/04/2012 09:02 AM, Michael Powell wrote: Bas Smeelen wrote: [snip] My previous response was sent too early :( I still get errors in apache [Tue Sep 04 08:14:42 2012] [error] [client 192.168.1.189] PHP Warning: Unknown: Unable to allocate memory for pool. in Unknown on line 0, referer: http://sys.ose.nl/cacti/graph_view.php?action=treetree_id=1leaf_id=21 [Tue Sep 04 08:14:43 2012] [notice] child pid 56172 exit signal [Segmentation fault (11) [snip] Well it turns out to be apc.so, this comes with core php I guess? [snip] I have found that the faults are present because www/pecl-APC was not recompiled/reinstalled. So I reinstalled www/pecl-APC with portmaster -f and this also reinstalled the following ports: Re-install pecl-APC-3.1.12 Re-install autoconf-2.69 Re-install autoconf-wrapper-20101119 Re-install gmake-3.82_1 Re-install gettext-0.18.1.1 Re-install libiconv-1.14 Re-install libtool-2.4.2 Re-install m4-1.4.16_1,1 Re-install perl-5.12.4_4 Re-install help2man-1.40.11 Re-install p5-Locale-gettext-1.05_3 Re-install php5-5.4.6 Re-install pcre-8.31 Re-install pkgconf-0.8.7_2 Re-install libxml2-2.7.8_3 Re-install apache-2.2.22_6 Re-install apr-ipv6-devrandom-gdbm-db42-1.4.5.1.3.12_1 Re-install db42-4.2.52_5 Re-install gdbm-1.9.1 Re-install automake-1.12.3 Re-install automake-wrapper-20101119 Re-install python27-2.7.3_3 Re-install expat-2.0.1_2 There is nothing about this in UPDATING, should there? This solved the problem anyway. Bas Disclaimer: http://www.ose.nl/email ___ 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
SOLVED: Re: Error after upgrading to php 5.4.6
On 09/04/2012 09:02 AM, Michael Powell wrote: Bas Smeelen wrote: [snip] My previous response was sent too early :( I still get errors in apache [Tue Sep 04 08:14:42 2012] [error] [client 192.168.1.189] PHP Warning: Unknown: Unable to allocate memory for pool. in Unknown on line 0, referer: http://sys.ose.nl/cacti/graph_view.php?action=treetree_id=1leaf_id=21 [Tue Sep 04 08:14:43 2012] [notice] child pid 56172 exit signal [Segmentation fault (11) [snip] Well it turns out to be apc.so, this comes with core php I guess? [snip] Sorry, this just delays the error but it eventually comes back so I'll keep apc.so commented. I have found that the faults are present because www/pecl-APC was not recompiled/reinstalled. So I reinstalled www/pecl-APC with portmaster -f and this also reinstalled the following ports: Re-install pecl-APC-3.1.12 Re-install autoconf-2.69 Re-install autoconf-wrapper-20101119 Re-install gmake-3.82_1 Re-install gettext-0.18.1.1 Re-install libiconv-1.14 Re-install libtool-2.4.2 Re-install m4-1.4.16_1,1 Re-install perl-5.12.4_4 Re-install help2man-1.40.11 Re-install p5-Locale-gettext-1.05_3 Re-install php5-5.4.6 Re-install pcre-8.31 Re-install pkgconf-0.8.7_2 Re-install libxml2-2.7.8_3 Re-install apache-2.2.22_6 Re-install apr-ipv6-devrandom-gdbm-db42-1.4.5.1.3.12_1 Re-install db42-4.2.52_5 Re-install gdbm-1.9.1 Re-install automake-1.12.3 Re-install automake-wrapper-20101119 Re-install python27-2.7.3_3 Re-install expat-2.0.1_2 There is nothing about this in UPDATING, should there? This solved the problem anyway. Bas Disclaimer: http://www.ose.nl/email ___ 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
Error after upgrading to php 5.4.6
My php pages will no longer render in a web browser after upgrading to php 5.4.6. Used port upgrade to do this. Running apache 2.2.22_6. Checked the error log and this is what I receive [notice] child pid 38232 exit signal Segmentation fault (11) This does this on all php pages. Any idea how to fix this error? Thanks___ 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: Error after upgrading to php 5.4.6
On 09/03/2012 01:26 PM, Darrell Betts wrote: My php pages will no longer render in a web browser after upgrading to php 5.4.6. Used port upgrade to do this. Running apache 2.2.22_6. Checked the error log and this is what I receive [notice] child pid 38232 exit signal Segmentation fault (11) This does this on all php pages. Any idea how to fix this error? Thanks___ I had the same issue on a 8.3-STABLE machine. On other machines php is still at 5.4.3 and does not have this problems. On the machine where 5.4.6 gave the problems I completely removed php and installed lang/php53 (5.3.16) which solved the issue If you are using portmaster -b to update ports, then a backup of the previous port will be in /usr/ports/packages and you can reinstall the previous version Disclaimer: http://www.ose.nl/email ___ 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: Error after upgrading to php 5.4.6
On Mon, 03 Sep 2012 13:52:45 +0200 Bas Smeelen articulated: On 09/03/2012 01:26 PM, Darrell Betts wrote: My php pages will no longer render in a web browser after upgrading to php 5.4.6. Used port upgrade to do this. Running apache 2.2.22_6. Checked the error log and this is what I receive [notice] child pid 38232 exit signal Segmentation fault (11) This does this on all php pages. Any idea how to fix this error? I had the same issue on a 8.3-STABLE machine. On other machines php is still at 5.4.3 and does not have this problems. On the machine where 5.4.6 gave the problems I completely removed php and installed lang/php53 (5.3.16) which solved the issue If you are using portmaster -b to update ports, then a backup of the previous port will be in /usr/ports/packages and you can reinstall the previous version I completely removed all traces of PHP from my system, including configuration files, made sure to run make config in each PHP port I intended to install and then installed the latest version of PHP without a single problem. I believe, although I can not prove it, that the problem is not in the PHP port but rather in the update process. Running portmanager with the -p option might take care of some ports not being updated correctly with PHP also. Again, there is nothing wrong with the latest version but rather in the way it is presently running on your system. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: Error after upgrading to php 5.4.6
On 09/03/2012 03:23 PM, Jerry wrote: On Mon, 03 Sep 2012 13:52:45 +0200 Bas Smeelen articulated: On 09/03/2012 01:26 PM, Darrell Betts wrote: My php pages will no longer render in a web browser after upgrading to php 5.4.6. Used port upgrade to do this. Running apache 2.2.22_6. Checked the error log and this is what I receive [notice] child pid 38232 exit signal Segmentation fault (11) This does this on all php pages. Any idea how to fix this error? I had the same issue on a 8.3-STABLE machine. On other machines php is still at 5.4.3 and does not have this problems. On the machine where 5.4.6 gave the problems I completely removed php and installed lang/php53 (5.3.16) which solved the issue If you are using portmaster -b to update ports, then a backup of the previous port will be in /usr/ports/packages and you can reinstall the previous version I completely removed all traces of PHP from my system, including configuration files, made sure to run make config in each PHP port I intended to install and then installed the latest version of PHP without a single problem. I believe, although I can not prove it, that the problem is not in the PHP port but rather in the update process. Running portmanager with the -p option might take care of some ports not being updated correctly with PHP also. Again, there is nothing wrong with the latest version but rather in the way it is presently running on your system. OK thanks voor the insight, I only checked the extensions.ini file after updating I will go ahead and try it the clean way with version 5.4.6 Disclaimer: http://www.ose.nl/email ___ 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: Error after upgrading to php 5.4.6
On 03/09/2012 12:26, Darrell Betts wrote: My php pages will no longer render in a web browser after upgrading to php 5.4.6. Used port upgrade to do this. Running apache 2.2.22_6. Checked the error log and this is what I receive [notice] child pid 38232 exit signal Segmentation fault (11) This does this on all php pages. Any idea how to fix this error? Thanks___ 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 try editing your /usr/local/etc/php/extensions.ini, comment out all extensions (restart apache) and see if it stops seg faulting. If it works, add in the modules one by one until it stops. Previously i've seen people posting about the order being important Paul. -- - Paul Macdonald IFDNRG Ltd Web and video hosting - t: 0131 5548070 m: 07970339546 e: p...@ifdnrg.com w: http://www.ifdnrg.com - IFDNRG 40 Maritime Street Edinburgh EH6 6SA - ___ 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: Error after upgrading to php 5.4.6
Hi! After any upgrade of php i'm use one script that was founded on
freebsd.org
$ cd /usr/local/etc/php
$ cat fixphpextorder.sh
#!/bin/sh
# =
# Fix php/extensions.ini order
#
# Script based on the idea and information(s) of
# - http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround
# - http://nerdstock.org/php_extensions
#
# Please copy your original php/extensions.ini to a save place before
# running this script!
#
# There is no guaranty the script is working for you or don't damage
# your system. Use at own Risk!
#
# 2011-04-03 olli hauer
#
# License: BSD
# http://www.freebsd.org/copyright/freebsd-license.html
#
#
# Updates:
# 2011-12-26:
# Make sed expression more explicit.
# Reported by Kartsten Schmidt
#
INI=/usr/local/etc/php/extensions.ini
EXT=session.so fileinfo.so crack.so ssh2.so imagick.so ldap.so
simplexml.so dba.so ctype.so apc.so ftp.so mbstring.so tokenizer.so
filter.so pgsql.so gmp.so mcrypt.so tidy.so xmlwriter.so mhash.so gd.so
ncurses.so readline.so gettext.so iconv.so dbase.so calendar.so exif.so
zlib.so curl.so mailparse.so xmlrpc.so bz2.so sysvmsg.so pdf.so openssl.so
ming.so dom.so hash.so xmlreader.so gnupg.so bcmath.so pcre.so xsl.so
wddx.so memcache.so soap.so spl.so sqlite.so recode.so pdo.so pdo_mysql.so
pdo_sqlite.so mysqli.so mysql.so imap.so sockets.so pspell.so xml.so
if [ ! -e ${INI} ] ; then
echo cannot find ${INI}
exit 1
fi
# cleanup previous run
[ -e ${INI}.new ] rm -f ${INI}.new
cp -f ${INI} ${INI}.work
for e in ${EXT}; do
if egrep -q ^extension=${e} ${INI}.work ; then
echo extension=${e} ${INI}.new
sed -i '' -e /^extension=${e}/d ${INI}.work
fi
done
if [ -s ${INI}.work ]; then
echo ; additional extension(s) not known by $(basename $0) ${INI}.new
# sybase_ct needs to be loaded last.
grep ^extension ${INI}.work | grep -v sybase_ct.so ${INI}.new
grep ^extension=sybase_ct.so ${INI}.work ${INI}.new
AE=1
fi
[ -e ${INI}.work ] rm -f ${INI}.work
if cmp -s ${INI} ${INI}.new ; then
echo No changes found, remove ${INI}.new
rm -f ${INI}.new
AE=0
fi
if [ ${AE} -ne 0 ]; then
cat _EOF
==
New INI is saved as ${INI}.new
Additional extension(s) not known by $(basename $0)
are added to the end of new INI file.
Please review the new INI, and replace it on your own!
Do some Basic tests:
php -V
php -m
php -i
apachectl graceful
...
_EOF
fi
cat _EOF
If the segfault issue is not gone, or you cannot find the issue
- ask on the ports@ mailing list
or
- open a PR:
Synopsys: lang/php5 Segmentation fault.
Additional try debugging with command:
gdb php ./php.core
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/debugging.html
_EOF
Best regards,
Vladimir
Unix Sysadmin
03.09.2012 15:26, Darrell Betts пишет:
My php pages will no longer render in a web browser after upgrading to php
5.4.6. Used port upgrade to do this. Running apache 2.2.22_6.
Checked the error log and this is what I receive
[notice] child pid 38232 exit signal Segmentation fault (11)
This does this on all php pages.
Any idea how to fix this error?
Thanks___
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
Re: Error after upgrading to php 5.4.6
Paul Macdonald wrote: On 03/09/2012 12:26, Darrell Betts wrote: My php pages will no longer render in a web browser after upgrading to php 5.4.6. Used port upgrade to do this. Running apache 2.2.22_6. Checked the error log and this is what I receive [notice] child pid 38232 exit signal Segmentation fault (11) This does this on all php pages. Any idea how to fix this error? [snip] try editing your /usr/local/etc/php/extensions.ini, comment out all extensions (restart apache) and see if it stops seg faulting. If it works, add in the modules one by one until it stops. Previously i've seen people posting about the order being important Some while back I thought portupgrading PHP caused the extensions.ini to be edited after each and every extension rebuild/reinstall, causing a shuffle like effect. Since I do a backup before, including all configs, I got into the habit of just copying my old extensions.ini back into place afterwards prior to restarting PHP and/or web servers. -Mike ___ 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: Upgrading 9.1-BETA1 - 9.1-RC1
On 08/31/12 01:17, warchild wrote: Hi That is wrong, this worked for me on one of my servers since I did it straight away (as soon as I saw the release for rc1. FreeBSD warsol 9.1-RC1 FreeBSD 9.1-RC1 #0: Tue Aug 14 04:25:06 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 that was beta1, and I used freebsd-update to upgrade it! Now, on another server i would like to do I have the same error as the OP. Go to: http://update3.freebsd.org/ Simple put, someone has deleted the whole BETA1 directory/brach!? WHY!? is there another way we can accept the key. or is that data needed.. Can we get the branch restored? It does work. Rebuilding world is so painful. thanks -- View this message in context: http://freebsd.1045724.n5.nabble.com/Upgrading-9-1-BETA1-9-1-RC1-tp5737452p5739453.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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 There is a stupid way to upgrade FreeBSD: http://forums.freebsd.org/archive/index.php/t-1280.html % su # env UNAME_r=7.1-PRERELEASE freebsd-update upgrade -r 7.1 i use # env UNAME_r=8.2 freebsd-update upgrade -r 9.1-RC1 But it doesn't help me with tool [, so i can't update with csup. :( Greetings ___ 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: Upgrading 9.1-BETA1 - 9.1-RC1
Hi That is wrong, this worked for me on one of my servers since I did it straight away (as soon as I saw the release for rc1. FreeBSD warsol 9.1-RC1 FreeBSD 9.1-RC1 #0: Tue Aug 14 04:25:06 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 that was beta1, and I used freebsd-update to upgrade it! Now, on another server i would like to do I have the same error as the OP. Go to: http://update3.freebsd.org/ Simple put, someone has deleted the whole BETA1 directory/brach!? WHY!? is there another way we can accept the key. or is that data needed.. Can we get the branch restored? It does work. Rebuilding world is so painful. thanks -- View this message in context: http://freebsd.1045724.n5.nabble.com/Upgrading-9-1-BETA1-9-1-RC1-tp5737452p5739453.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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: Upgrading perl
Jack Stone ja...@sage-american.com writes: uname -a FreeBSD mail.sagedata.net 7.0-RELEASE-p9 FreeBSD 7.0-RELEASE-p9 #2: Sun Jan 18 19:59:27 CST 2009 Running perl5.10 (yeah, old!) This is a production server. Been playing catchup on ports including perl as UPDATING recommends: portupgrade -o lang/perl5.12 -f perl-5.10.\* That has worked on other servers, but not this one. Anyone know what I need to do to clean this up?? But, can't get past this fatal error: mail# portupgrade -o lang/perl5.12 -f perl-5.10.\* /usr/ports/Mk/bsd.options.mk, line 231: Error in archive specification: WITHOUT_ /usr/ports/Mk/bsd.options.mk, line 231: Error in archive specification: WITHOUT_ make: fatal errors encountered -- cannot continue ** Makefile possibly broken: lang/perl5.12: You're almost four years past the end-of-life on the release you're running, so it's been left behind in terms of support. In this case it looks (based on a *very* quick look) that you may be running into changes in how make(1) actually works, in which case backporting the ports functionality will be more work than it's worth. If the machine can't be updated, and assuming it's secure (which hard to be sure about with old software on the Internet), you may be best off leaving it alone. Good luck. ___ 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: Upgrading perl
On 8/29/2012 8:27 AM, Lowell Gilbert wrote: Jack Stone ja...@sage-american.com writes: uname -a FreeBSD mail.sagedata.net 7.0-RELEASE-p9 FreeBSD 7.0-RELEASE-p9 #2: Sun Jan 18 19:59:27 CST 2009 Running perl5.10 (yeah, old!) This is a production server. Been playing catchup on ports including perl as UPDATING recommends: portupgrade -o lang/perl5.12 -f perl-5.10.\* That has worked on other servers, but not this one. Anyone know what I need to do to clean this up?? But, can't get past this fatal error: mail# portupgrade -o lang/perl5.12 -f perl-5.10.\* /usr/ports/Mk/bsd.options.mk, line 231: Error in archive specification: WITHOUT_ /usr/ports/Mk/bsd.options.mk, line 231: Error in archive specification: WITHOUT_ make: fatal errors encountered -- cannot continue ** Makefile possibly broken: lang/perl5.12: You're almost four years past the end-of-life on the release you're running, so it's been left behind in terms of support. In this case it looks (based on a *very* quick look) that you may be running into changes in how make(1) actually works, in which case backporting the ports functionality will be more work than it's worth. If the machine can't be updated, and assuming it's secure (which hard to be sure about with old software on the Internet), you may be best off leaving it alone. Good luck. Thanks for the reply. Actually, on other servers with the same upgrading needs, perl-5.12 installed without any issue. My intention is to upgrade perl in increments to get well past EOL. Wonder if I just deinstalled the old perl5-5.10 and then installed the perl5-12 would work. I can do that right from the port: make perl5-12 first to see if that works, then: # make deinstall (perl-5.10) then: make install clean What do you think? I've got to move up because an important perl program requires a minimum 5.12. -- -- All the best, Jack ___ 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: Upgrading perl
On 8/29/12 8:08 AM, Jack Stone wrote: On 8/29/2012 8:27 AM, Lowell Gilbert wrote: Jack Stone ja...@sage-american.com writes: uname -a FreeBSD mail.sagedata.net 7.0-RELEASE-p9 FreeBSD 7.0-RELEASE-p9 #2: Sun Jan 18 19:59:27 CST 2009 Running perl5.10 (yeah, old!) This is a production server. Been playing catchup on ports including perl as UPDATING recommends: portupgrade -o lang/perl5.12 -f perl-5.10.\* That has worked on other servers, but not this one. Anyone know what I need to do to clean this up?? But, can't get past this fatal error: mail# portupgrade -o lang/perl5.12 -f perl-5.10.\* /usr/ports/Mk/bsd.options.mk, line 231: Error in archive specification: WITHOUT_ /usr/ports/Mk/bsd.options.mk, line 231: Error in archive specification: WITHOUT_ make: fatal errors encountered -- cannot continue ** Makefile possibly broken: lang/perl5.12: You're almost four years past the end-of-life on the release you're running, so it's been left behind in terms of support. In this case it looks (based on a *very* quick look) that you may be running into changes in how make(1) actually works, in which case backporting the ports functionality will be more work than it's worth. If the machine can't be updated, and assuming it's secure (which hard to be sure about with old software on the Internet), you may be best off leaving it alone. Good luck. Thanks for the reply. Actually, on other servers with the same upgrading needs, perl-5.12 installed without any issue. My intention is to upgrade perl in increments to get well past EOL. Wonder if I just deinstalled the old perl5-5.10 and then installed the perl5-12 would work. I can do that right from the port: make perl5-12 first to see if that works, then: # make deinstall (perl-5.10) then: make install clean If you're using portmaster, you should be able to do something like the following from /usr/ports: portmaster -o lang/perl5.16 lang/perl5.10 portmaster p5- and perl automagically will upgrade. This is from /usr/ports/UPDATING. You can also find instructions for portupgrade there. Don't know about dependencies with 7.0, though. dn What do you think? I've got to move up because an important perl program requires a minimum 5.12. ___ 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: Upgrading perl
On 8/29/12 10:59 AM, David Newman wrote: On 8/29/12 8:08 AM, Jack Stone wrote: On 8/29/2012 8:27 AM, Lowell Gilbert wrote: Jack Stone ja...@sage-american.com writes: uname -a FreeBSD mail.sagedata.net 7.0-RELEASE-p9 FreeBSD 7.0-RELEASE-p9 #2: Sun Jan 18 19:59:27 CST 2009 Running perl5.10 (yeah, old!) This is a production server. Been playing catchup on ports including perl as UPDATING recommends: portupgrade -o lang/perl5.12 -f perl-5.10.\* That has worked on other servers, but not this one. Anyone know what I need to do to clean this up?? But, can't get past this fatal error: mail# portupgrade -o lang/perl5.12 -f perl-5.10.\* /usr/ports/Mk/bsd.options.mk, line 231: Error in archive specification: WITHOUT_ /usr/ports/Mk/bsd.options.mk, line 231: Error in archive specification: WITHOUT_ make: fatal errors encountered -- cannot continue ** Makefile possibly broken: lang/perl5.12: You're almost four years past the end-of-life on the release you're running, so it's been left behind in terms of support. In this case it looks (based on a *very* quick look) that you may be running into changes in how make(1) actually works, in which case backporting the ports functionality will be more work than it's worth. If the machine can't be updated, and assuming it's secure (which hard to be sure about with old software on the Internet), you may be best off leaving it alone. Good luck. Thanks for the reply. Actually, on other servers with the same upgrading needs, perl-5.12 installed without any issue. My intention is to upgrade perl in increments to get well past EOL. Wonder if I just deinstalled the old perl5-5.10 and then installed the perl5-12 would work. I can do that right from the port: make perl5-12 first to see if that works, then: # make deinstall (perl-5.10) then: make install clean If you're using portmaster, you should be able to do something like the following from /usr/ports: portmaster -o lang/perl5.16 lang/perl5.10 portmaster p5- and perl automagically will upgrade. Sorry, I'd missed that you'd tried this and it isn't working. make has changed since the 7.0 days. I agree with Jack that you're better off leaving well enough alone. If you really need perl5.16+ capabilities you're much better off moving your program to a more recent version of FreeBSD. dn This is from /usr/ports/UPDATING. You can also find instructions for portupgrade there. Don't know about dependencies with 7.0, though. dn What do you think? I've got to move up because an important perl program requires a minimum 5.12. ___ 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
Re: Upgrading perl
Jack Stone ja...@sage-american.com writes: Actually, on other servers with the same upgrading needs, perl-5.12 installed without any issue. My intention is to upgrade perl in increments to get well past EOL. You're somewhat on your own, then; I can't test any of my ideas before suggesting them to you. Wonder if I just deinstalled the old perl5-5.10 and then installed the perl5-12 would work. I can do that right from the port: make perl5-12 first to see if that works, then: # make deinstall (perl-5.10) then: make install clean I would be surprised if the perl-5.12 port will build for you; I think you'll get the same error. If not, then yes, it should work. What do you think? I've got to move up because an important perl program requires a minimum 5.12. Well, it's also possible that there's a local problem on that machine. You indicated that you used portupgrade for similar updates on similarly-aged machines, but I'll guess that they were only roughly similar. I'll guess that you built your own INDEX file; if not, you probably should (and the associated database for portupgrade). Compare the infrastructure in ports/Mk (and maybe /usr/share/mk) with the similar machines that succeeded, and look at the Makefile in perl5.12 to make sure it sets options properly. Good luck. ___ 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: Upgrading perl
On 8/29/2012 1:32 PM, Lowell Gilbert wrote: Jack Stone ja...@sage-american.com writes: Actually, on other servers with the same upgrading needs, perl-5.12 installed without any issue. My intention is to upgrade perl in increments to get well past EOL. You're somewhat on your own, then; I can't test any of my ideas before suggesting them to you. Wonder if I just deinstalled the old perl5-5.10 and then installed the perl5-12 would work. I can do that right from the port: make perl5-12 first to see if that works, then: # make deinstall (perl-5.10) then: make install clean I would be surprised if the perl-5.12 port will build for you; I think you'll get the same error. If not, then yes, it should work. What do you think? I've got to move up because an important perl program requires a minimum 5.12. Well, it's also possible that there's a local problem on that machine. You indicated that you used portupgrade for similar updates on similarly-aged machines, but I'll guess that they were only roughly similar. I'll guess that you built your own INDEX file; if not, you probably should (and the associated database for portupgrade). Compare the infrastructure in ports/Mk (and maybe /usr/share/mk) with the similar machines that succeeded, and look at the Makefile in perl5.12 to make sure it sets options properly. Good luck. Hi Lowell and thanks for the good wishes! Yes, on the other servers which upgraded without issue are running the same freebsd-7.x, and the make files are identical for the perl-5.12. I just now ran a test on a test server of same vintage and it did build directly in the port just using make to see if it would work. It did. The trick is to DISABLE_CONFLICTS=YES in the /etc/make.conf. This still doesn't mean the important production server will cooperatebut will have to take a risk and try it. That server has a bootable clone that is run every day so I can rescue the server. I will just to make a fresh clone right before I try the perl upgradeso to minimize any loss of data. -- All the best, Jack ___ 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: Upgrading perl
On 8/29/2012 1:32 PM, Lowell Gilbert wrote: Jack Stone ja...@sage-american.com writes: Actually, on other servers with the same upgrading needs, perl-5.12 installed without any issue. My intention is to upgrade perl in increments to get well past EOL. You're somewhat on your own, then; I can't test any of my ideas before suggesting them to you. Wonder if I just deinstalled the old perl5-5.10 and then installed the perl5-12 would work. I can do that right from the port: make perl5-12 first to see if that works, then: # make deinstall (perl-5.10) then: make install clean I would be surprised if the perl-5.12 port will build for you; I think you'll get the same error. If not, then yes, it should work. What do you think? I've got to move up because an important perl program requires a minimum 5.12. Well, it's also possible that there's a local problem on that machine. You indicated that you used portupgrade for similar updates on similarly-aged machines, but I'll guess that they were only roughly similar. I'll guess that you built your own INDEX file; if not, you probably should (and the associated database for portupgrade). Compare the infrastructure in ports/Mk (and maybe /usr/share/mk) with the similar machines that succeeded, and look at the Makefile in perl5.12 to make sure it sets options properly. Good luck. AHAH! This just came out in ports UPDATING and maybe helps: 20120820: AFFECTS: users of ports-mgmt/portupgrade-devel AUTHOR: bdrew...@freebsd.org Due to a bug introduced in 20120601, portupgrade is unable to upgrade itself on FreeBSD 7.x. This has been fixed in 20120820. ports-mgmt/portupgrade is not affected. To upgrade, execute the following: # cd /usr/ports/ports-mgmt/portupgrade-devel make deinstall install clean -- -- All the best, Jack ___ 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
Upgrading perl
uname -a FreeBSD mail.sagedata.net 7.0-RELEASE-p9 FreeBSD 7.0-RELEASE-p9 #2: Sun Jan 18 19:59:27 CST 2009 Running perl5.10 (yeah, old!) This is a production server. Been playing catchup on ports including perl as UPDATING recommends: portupgrade -o lang/perl5.12 -f perl-5.10.\* That has worked on other servers, but not this one. Anyone know what I need to do to clean this up?? But, can't get past this fatal error: mail# portupgrade -o lang/perl5.12 -f perl-5.10.\* /usr/ports/Mk/bsd.options.mk, line 231: Error in archive specification: WITHOUT_ /usr/ports/Mk/bsd.options.mk, line 231: Error in archive specification: WITHOUT_ make: fatal errors encountered -- cannot continue ** Makefile possibly broken: lang/perl5.12: ** Please report this to the maintainer for lang/perl5.12 No closing parenthesis in archive specification No closing parenthesis in archive specification /usr/local/sbin/portupgrade:1560:in `get_pkgname': Makefile broken (MakefileBrokenError) from /usr/local/sbin/portupgrade:631:in `block (4 levels) in main' from /usr/local/sbin/portupgrade:615:in `each' from /usr/local/sbin/portupgrade:615:in `block (3 levels) in main' from /usr/local/sbin/portupgrade:588:in `catch' from /usr/local/sbin/portupgrade:588:in `block (2 levels) in main' from /usr/local/lib/ruby/1.9/optparse.rb:1404:in `call' from /usr/local/lib/ruby/1.9/optparse.rb:1404:in `block (2 levels) in parse_in_order' from /usr/local/lib/ruby/1.9/optparse.rb:1399:in `catch' from /usr/local/lib/ruby/1.9/optparse.rb:1399:in `block in parse_in_order' from /usr/local/lib/ruby/1.9/optparse.rb:1347:in `catch' from /usr/local/lib/ruby/1.9/optparse.rb:1347:in `parse_in_order' from /usr/local/lib/ruby/1.9/optparse.rb:1341:in `order!' from /usr/local/lib/ruby/1.9/optparse.rb:1334:in `order' from /usr/local/sbin/portupgrade:565:in `block in main' from /usr/local/lib/ruby/1.9/optparse.rb:882:in `initialize' from /usr/local/sbin/portupgrade:236:in `new' from /usr/local/sbin/portupgrade:236:in `main' from /usr/local/sbin/portupgrade:2344:in `main' All the best, Jack ___ 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: Upgrading 9.1-BETA1 - 9.1-RC1
from Maarten Billemont lhun...@lyndir.com: I've installed a FreeBSD server using the BETA1 release because RC1 was delayed. I notice the 9.1-RC1 is available now, so I thought I'd upgrade ASAP. The following command, however, fails me: freebsd-update -r 9.1-RC1 upgrade Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 9.1-BETA1 from update4.FreeBSD.org... failed. Fetching metadata signature for 9.1-BETA1 from update3.FreeBSD.org... failed. Fetching metadata signature for 9.1-BETA1 from update5.FreeBSD.org... failed. No mirrors remaining, giving up. Upon inspection of the code, it appears BETA1's ssl.pub cannot be found at any of the mirrors, and as such the process aborts. The release notes for RC1 specifically mention freebsd-update. How do I perform a correct update to RC1, and why is the freebsd-update flow failing me or not supported? Thanks! I believe freebsd-update only works, to and from, on supported releases; this would not include betas. Tom ___ 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: Upgrading 9.1-BETA1 - 9.1-RC1
[ Thomas Mueller wrote on Sat 25.Aug'12 at 2:51:38 -0400 ] from Maarten Billemont lhun...@lyndir.com: I've installed a FreeBSD server using the BETA1 release because RC1 was delayed. I notice the 9.1-RC1 is available now, so I thought I'd upgrade ASAP. The following command, however, fails me: freebsd-update -r 9.1-RC1 upgrade Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 9.1-BETA1 from update4.FreeBSD.org... failed. Fetching metadata signature for 9.1-BETA1 from update3.FreeBSD.org... failed. Fetching metadata signature for 9.1-BETA1 from update5.FreeBSD.org... failed. No mirrors remaining, giving up. Upon inspection of the code, it appears BETA1's ssl.pub cannot be found at any of the mirrors, and as such the process aborts. The release notes for RC1 specifically mention freebsd-update. How do I perform a correct update to RC1, and why is the freebsd-update flow failing me or not supported? Thanks! I believe freebsd-update only works, to and from, on supported releases; this would not include betas. Tom I built it from sources yesterday using the stable-supfile and csup. I've had no issues using that method. It took a heck of a long time to compile world though, ~2-3 hours in single user mode with -j5 option to make(1) ___ 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
