Re: freebsd-update upgrade -r 7.4-RELEASE-p12
On Wed, Oct 9, 2013, at 8:36, Eduardo Morras wrote: On Tue, 8 Oct 2013 21:32:39 -0600 (MDT) Mike Brown m...@skew.org wrote: alexus wrote: ok, I just did fetch install and got bumped from p5 to p9 # uname -a FreeBSD XX.X.org 7.4-RELEASE-p9 FreeBSD 7.4-RELEASE-p9 #0: Mon Jun 11 19:47:58 UTC 2012 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # can I take it all the way to -p12? -p10 through -p12 probably didn't involve any kernel changes. Bumping the reported patchlevel isn't considered important enough to warrant building a new kernel. That there's no kernel changes doesn't mean that uname -a info is not updated. You are incorrect. The output of uname -a is taken from the kernel and cannot be updated without installing a new kernel. The good news is that FreeBSD 10 will ship with a new utility called freebsd-version which will provide a better way of identifying if your system is up to date. From the commit message: Introduce the /libexec/freebsd-version script, which is intended to be used by auditing tools to determine the userland patch level when it differs from what `uname -r` reports. This can happen when the system is kept up-to-date using freebsd-update and the last SA did not touch the kernel, or when a new kernel has been installed but the system has not yet rebooted. http://svnweb.freebsd.org/base/head/bin/freebsd-version/ By the way, it will be /bin/freebsd-version as it has been relocated since the import into head. ___ 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: 9.1 - 9.2 upgrade
On 8 October 2013, at 16:40, Polytropon free...@edvax.de wrote: On Tue, 8 Oct 2013 11:20:40 -0700, Doug Hardie wrote: I tried downloading the src with: svn co https://svn0.us-west.FreeBSD.org/base/releng/9.2 /mnt/usr/src I didn't get Release 9.2. The first entry in UPDATING is: 20130705: hastctl(8)'s `status' command output changed to terse one-liner format. Scripts using this should switch to `list' command or be rewritten. There is an entry earlier for Release 9.1. but no entry for Release 9.2. You could try downloading and extracting the src distribution: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/9.2-RELEASE/src.txz Before I saw this I built from the src obtained via svn. The system now boots. I still have no idea what was preventing it from booting. It was something between displaying the Beastie menu and waiting for user input. There had to be at least 2 issues as the messages changed after the first attempt to rebuild the system. I tried to chase down the boot code for the first error message and it appears to be generated when there is a problem with a directory. I couldn't find any further diagnostic info to identify the directory. I have not yet tried to chase down the second set of messages in the source. The system now says its 9.2. UPDATING still looks the same. Interestingly enough, on another system that I updated earlier to 9.2 via freebsd-update, UPDATING there is identical to the one on this system. There is no 9.2 entry. Also of note is that most of the ports/packages are still present. However SASL2 vanished without a trace. Its easily replaced, but why is certainly interesting. I have no ideas at this point. ___ 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: freebsd-update upgrade -r 7.4-RELEASE-p12
On Tue, Oct 8, 2013, at 22:32, Mike Brown wrote: alexus wrote: ok, I just did fetch install and got bumped from p5 to p9 # uname -a FreeBSD XX.X.org 7.4-RELEASE-p9 FreeBSD 7.4-RELEASE-p9 #0: Mon Jun 11 19:47:58 UTC 2012 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # can I take it all the way to -p12? -p10 through -p12 probably didn't involve any kernel changes. Bumping the reported patchlevel isn't considered important enough to warrant building a new kernel. If your sources are in /usr/src, do this: grep -v # /usr/src/sys/conf/newvers.sh | head -4 If he had sources on the box he probably would have just compiled the fixes himself. The version number shouldn't be embedded in the kernel like that so it's easier for people to audit their systems. I have VMs right now in Xen that report different FreeBSD versions and it's confusing for other sysadmins who aren't intimately familiar with FreeBSD. Some were updated by freebsd-update, some were updated by src. But they don't report the same OS version so I get asked why we haven't updated those servers yet ___ 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: freebsd-update upgrade -r 7.4-RELEASE-p12
On Tue, 8 Oct 2013 21:32:39 -0600 (MDT) Mike Brown m...@skew.org wrote: alexus wrote: ok, I just did fetch install and got bumped from p5 to p9 # uname -a FreeBSD XX.X.org 7.4-RELEASE-p9 FreeBSD 7.4-RELEASE-p9 #0: Mon Jun 11 19:47:58 UTC 2012 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # can I take it all the way to -p12? -p10 through -p12 probably didn't involve any kernel changes. Bumping the reported patchlevel isn't considered important enough to warrant building a new kernel. That there's no kernel changes doesn't mean that uname -a info is not updated. If you update the system from p5 to current (p12), and it shows p9 instead p12 the first thing you think is that something on the system update went wrong, not that everything was fine except the update of the file that uname -a reads. If release info patch is p12, it must update the whole system to p12. If you update an app from 2.24.1 to 2.24.2 and doing 'app -v' shows 2.24.1 it means something went wrong, not that update only modified config files and not the binary. If your sources are in /usr/src, do this: grep -v # /usr/src/sys/conf/newvers.sh | head -4 No, uname -a should give the correct answer. Has uname other utility than show information about the operating system implementation? No, and it must be accurate. --- --- 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: freebsd-update upgrade -r 7.4-RELEASE-p12
Mike Brown: $ grep ^BRANCH /usr/src/sys/conf/newvers.sh BRANCH=RELEASE-p12 $ then again, I used freebsd-update and not /usr/src, but it makes sense what you said with kernel, so I guess I _AM_ on the latest -p12 and kernel is on -p9 as there was no changes after that to kernel. thank you. On Tue, Oct 8, 2013 at 11:32 PM, Mike Brown m...@skew.org wrote: alexus wrote: ok, I just did fetch install and got bumped from p5 to p9 # uname -a FreeBSD XX.X.org 7.4-RELEASE-p9 FreeBSD 7.4-RELEASE-p9 #0: Mon Jun 11 19:47:58 UTC 2012 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # can I take it all the way to -p12? -p10 through -p12 probably didn't involve any kernel changes. Bumping the reported patchlevel isn't considered important enough to warrant building a new kernel. If your sources are in /usr/src, do this: grep -v # /usr/src/sys/conf/newvers.sh | head -4 -- http://alexus.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
Upgrade 9.1 - 9.2
I used 'freebsd-update upgrade -r 9.2-RELEASE' to upgrade a test system. All went well, until the point at which it said: Kernel updates have been installed. Please reboot and run /usr/sbin/freebsd-update install again to finish installing updates. Stupidly, I did NOT reboot, but started the /usr/sbin/freebsd-update install without rebooting first. As soon as I realised my mistake (a few minutes later), I issued ctrl-c to exit, rebooted and ran /usr/sbin/freebsd-update install again. It appeared to finish successfuly. Have I screwed up my system, or am I OK? ___ 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: freebsd-update upgrade -r 7.4-RELEASE-p12
Eduardo Morras wrote: [...] uname -a should give the correct answer. Has uname other utility than show information about the operating system implementation? No, and it must be accurate. That's what I thought, but when I asked about it here last year, I was told that this is the way things are; our expectations of uname are at fault. I believe if he were to compile his own kernel, it would say -p12. Suggestions were made for how to deal with it, but I don't know if they were ever followed up on. They wouldn't affect 7.x in any case. Start reading the thread here: http://lists.freebsd.org/pipermail/freebsd-questions/2012-May/240666.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: 9.1 - 9.2 upgrade
On 5 October 2013, at 05:08, Polytropon free...@edvax.de wrote: On Fri, 4 Oct 2013 21:49:18 -0700, Doug Hardie wrote: On 4 October 2013, at 20:03, Polytropon free...@edvax.de wrote: On Fri, 4 Oct 2013 19:42:15 -0700, Doug Hardie wrote: On 4 October 2013, at 19:08, Polytropon free...@edvax.de wrote: On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: The exact sequence was: Step 1: freebsd-update from 9.1 to 9.2 Have you verified in /etc/freebsd-update.conf that src is definitely part of what should be updated? System is not bootable - can't verify anything… Does the system (or better, its enclosure, software-wise) allow booting a rescue system or an emergency media, such as a FreeBSD v9 live system? Yes - but there is no one there who can successfully be told how to run it. Not even inserting a USB stick (with the FreeBSD memstick data) or a CD? We have serious communications issues - they want to use back slashes and have no idea what a slash is. Maybe that is the result of many years of administration on Windows PCs. :-) Even if you tell them which key to use, they know better and use a back slash cause thats what Windoze uses. Uh... knowing better would disqualify them as maintainers of a server installation. The inability to learn (or even to read and follow instructions) is a dangerous thing. The disk should be in the mail to me now. I will be able to work with it when it arrives. Okay, that's also a possible alternative. To be honest, that's the first time I hear about this procedure. But doable. The file /etc/freebsd-update.conf should contain the line Components src world kernel if you want to make sure the source is properly updated, along with the world and kernel (GENERIC). As indicated before, I don't think all the source got updated. The kernel showed 9.2 after recompilation. However UPDATING was not updated. Thats as much as I could check before. I assume that this could be possible by inconsistently updated sources. It would be a good start to remove /usr/src and download the sources of the correct version via SVN _or_ freebsd-update again. Before the next installation attempt, /usr/obj should be removed as well, just to be sure. Step 5: reboot Attention: Into single-user mode. Not possible since the system is located over 100 miles away. Everything has to be done via remote console. Does this mean SSH only or do you have a _real_ console transmission by which you can access the system _prior_ to the OS providing the SSH access? I'm mentioning this because the traditional approach requires (few) steps done in the single-user mode where no SSH connectivity is provided in the normal way… I have a telnet box that has serial connections to the console ports. That approach has been used without any issues since FreeBSD 2.5. I do disable all ports during the process via an reduced rc.conf file. A serial console should also work, but even though I've been using serial consoles (and _real_ serial terminals), one thing I'm not sure about: Is it possible to interrupt (!) the boot process at an early stage to get to the loader prompt and boot into single user mode from there? Ok boot -s If not, do you have the beastie menu (or whatever it is called today) enabled to go to SUM to perform the make installworld step? Anyway, if you can install everything is required with the disk at home, and then send it back to that datacenter (according to your characterization, the quotes are deserved), that should solve the problems and make sure everything works as intended. The Thick Plottens… I received the drives and installed them on a working system. The failed system is structured with a single partition for the system and another for swap. For some unknown reason, the BIOS got left configured to boot the extra disk if its powered up. That turns out to be handy. I can boot a working system with the corrupt drive powered off. Booting from the corrupt drive yields the normal hardware info followed by the Beastie image and immediately by a multitude of lines (repeated many times): Consoles: internal video/keyboard serial port BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS 639kB/1037824kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (d...@zool.lafn.org, Thu Oct 3 04:23:13 PDT 2013) Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: I was able to capture these by using a serial console connected to another computer. The lines only appear on the serial console once. They scroll by on the real console many time - all too fast to read anything. Then after a few seconds of that, the screen goes black, and the system reboots. The cycle then repeats… Pressing any key does nothing. I even filled the keyboard buffer with spaces
Re: 9.1 - 9.2 upgrade
On 10/08/2013 4:27 am, Doug Hardie wrote: On 5 October 2013, at 05:08, Polytropon free...@edvax.de wrote: On Fri, 4 Oct 2013 21:49:18 -0700, Doug Hardie wrote: On 4 October 2013, at 20:03, Polytropon free...@edvax.de wrote: On Fri, 4 Oct 2013 19:42:15 -0700, Doug Hardie wrote: On 4 October 2013, at 19:08, Polytropon free...@edvax.de wrote: On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: The exact sequence was: Step 1: freebsd-update from 9.1 to 9.2 Have you verified in /etc/freebsd-update.conf that src is definitely part of what should be updated? System is not bootable - can't verify anything… Does the system (or better, its enclosure, software-wise) allow booting a rescue system or an emergency media, such as a FreeBSD v9 live system? Yes - but there is no one there who can successfully be told how to run it. Not even inserting a USB stick (with the FreeBSD memstick data) or a CD? We have serious communications issues - they want to use back slashes and have no idea what a slash is. Maybe that is the result of many years of administration on Windows PCs. :-) Even if you tell them which key to use, they know better and use a back slash cause thats what Windoze uses. Uh... knowing better would disqualify them as maintainers of a server installation. The inability to learn (or even to read and follow instructions) is a dangerous thing. The disk should be in the mail to me now. I will be able to work with it when it arrives. Okay, that's also a possible alternative. To be honest, that's the first time I hear about this procedure. But doable. The file /etc/freebsd-update.conf should contain the line Components src world kernel if you want to make sure the source is properly updated, along with the world and kernel (GENERIC). As indicated before, I don't think all the source got updated. The kernel showed 9.2 after recompilation. However UPDATING was not updated. Thats as much as I could check before. I assume that this could be possible by inconsistently updated sources. It would be a good start to remove /usr/src and download the sources of the correct version via SVN _or_ freebsd-update again. Before the next installation attempt, /usr/obj should be removed as well, just to be sure. Step 5: reboot Attention: Into single-user mode. Not possible since the system is located over 100 miles away. Everything has to be done via remote console. Does this mean SSH only or do you have a _real_ console transmission by which you can access the system _prior_ to the OS providing the SSH access? I'm mentioning this because the traditional approach requires (few) steps done in the single-user mode where no SSH connectivity is provided in the normal way… I have a telnet box that has serial connections to the console ports. That approach has been used without any issues since FreeBSD 2.5. I do disable all ports during the process via an reduced rc.conf file. A serial console should also work, but even though I've been using serial consoles (and _real_ serial terminals), one thing I'm not sure about: Is it possible to interrupt (!) the boot process at an early stage to get to the loader prompt and boot into single user mode from there? Ok boot -s If not, do you have the beastie menu (or whatever it is called today) enabled to go to SUM to perform the make installworld step? Anyway, if you can install everything is required with the disk at home, and then send it back to that datacenter (according to your characterization, the quotes are deserved), that should solve the problems and make sure everything works as intended. The Thick Plottens… I received the drives and installed them on a working system. The failed system is structured with a single partition for the system and another for swap. For some unknown reason, the BIOS got left configured to boot the extra disk if its powered up. That turns out to be handy. I can boot a working system with the corrupt drive powered off. Booting from the corrupt drive yields the normal hardware info followed by the Beastie image and immediately by a multitude of lines (repeated many times): Consoles: internal video/keyboard serial port BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS 639kB/1037824kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (d...@zool.lafn.org, Thu Oct 3 04:23:13 PDT 2013) Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: I was able to capture these by using a serial console connected to another computer. The lines only appear on the serial console once. They scroll by on the real console many time - all too fast to read anything. Then after a few seconds of that, the screen goes black, and the system reboots. The cycle then repeats… Pressing any key does nothing. I even filled the keyboard buffer with spaces hoping to stop boot, but nothing seems to stop
Re: 9.1 - 9.2 upgrade
On 8 October 2013, at 06:22, dweimer dwei...@dweimer.net wrote: On 10/08/2013 4:27 am, Doug Hardie wrote: On 5 October 2013, at 05:08, Polytropon free...@edvax.de wrote: On Fri, 4 Oct 2013 21:49:18 -0700, Doug Hardie wrote: On 4 October 2013, at 20:03, Polytropon free...@edvax.de wrote: On Fri, 4 Oct 2013 19:42:15 -0700, Doug Hardie wrote: On 4 October 2013, at 19:08, Polytropon free...@edvax.de wrote: On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: The exact sequence was: Step 1: freebsd-update from 9.1 to 9.2 Have you verified in /etc/freebsd-update.conf that src is definitely part of what should be updated? System is not bootable - can't verify anything… Does the system (or better, its enclosure, software-wise) allow booting a rescue system or an emergency media, such as a FreeBSD v9 live system? Yes - but there is no one there who can successfully be told how to run it. Not even inserting a USB stick (with the FreeBSD memstick data) or a CD? We have serious communications issues - they want to use back slashes and have no idea what a slash is. Maybe that is the result of many years of administration on Windows PCs. :-) Even if you tell them which key to use, they know better and use a back slash cause thats what Windoze uses. Uh... knowing better would disqualify them as maintainers of a server installation. The inability to learn (or even to read and follow instructions) is a dangerous thing. The disk should be in the mail to me now. I will be able to work with it when it arrives. Okay, that's also a possible alternative. To be honest, that's the first time I hear about this procedure. But doable. The file /etc/freebsd-update.conf should contain the line Components src world kernel if you want to make sure the source is properly updated, along with the world and kernel (GENERIC). As indicated before, I don't think all the source got updated. The kernel showed 9.2 after recompilation. However UPDATING was not updated. Thats as much as I could check before. I assume that this could be possible by inconsistently updated sources. It would be a good start to remove /usr/src and download the sources of the correct version via SVN _or_ freebsd-update again. Before the next installation attempt, /usr/obj should be removed as well, just to be sure. Step 5: reboot Attention: Into single-user mode. Not possible since the system is located over 100 miles away. Everything has to be done via remote console. Does this mean SSH only or do you have a _real_ console transmission by which you can access the system _prior_ to the OS providing the SSH access? I'm mentioning this because the traditional approach requires (few) steps done in the single-user mode where no SSH connectivity is provided in the normal way… I have a telnet box that has serial connections to the console ports. That approach has been used without any issues since FreeBSD 2.5. I do disable all ports during the process via an reduced rc.conf file. A serial console should also work, but even though I've been using serial consoles (and _real_ serial terminals), one thing I'm not sure about: Is it possible to interrupt (!) the boot process at an early stage to get to the loader prompt and boot into single user mode from there? Ok boot -s If not, do you have the beastie menu (or whatever it is called today) enabled to go to SUM to perform the make installworld step? Anyway, if you can install everything is required with the disk at home, and then send it back to that datacenter (according to your characterization, the quotes are deserved), that should solve the problems and make sure everything works as intended. The Thick Plottens… I received the drives and installed them on a working system. The failed system is structured with a single partition for the system and another for swap. For some unknown reason, the BIOS got left configured to boot the extra disk if its powered up. That turns out to be handy. I can boot a working system with the corrupt drive powered off. Booting from the corrupt drive yields the normal hardware info followed by the Beastie image and immediately by a multitude of lines (repeated many times): Consoles: internal video/keyboard serial port BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS 639kB/1037824kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (d...@zool.lafn.org, Thu Oct 3 04:23:13 PDT 2013) Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: I was able to capture these by using a serial console connected to another computer. The lines only appear on the serial console once. They scroll by on the real console many time - all too fast to read anything. Then after a few seconds of that, the screen goes black, and the system reboots. The cycle then repeats… Pressing any key does nothing. I even filled the
Re: 9.1 - 9.2 upgrade
Doug Hardie wrote: The Thick Plottens… I received the drives and installed them on a working system. The failed system is structured with a single partition for the system and another for swap. For some unknown reason, the BIOS got left configured to boot the extra disk if its powered up. That turns out to be handy. I can boot a working system with the corrupt drive powered off. Booting from the corrupt drive yields the normal hardware info followed by the Beastie image and immediately by a multitude of lines (repeated many times): Consoles: internal video/keyboard serial port BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS 639kB/1037824kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (d...@zool.lafn.org, Thu Oct 3 04:23:13 PDT 2013) Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: I was able to capture these by using a serial console connected to another computer. The lines only appear on the serial console once. They scroll by on the real console many time - all too fast to read anything. Then after a few seconds of that, the screen goes black, and the system reboots. The cycle then repeats… Pressing any key does nothing. I even filled the keyboard buffer with spaces hoping to stop boot, but nothing seems to stop it. I checked and the freebsd-update.conf include world sys and src. I rebuild everything after removing /obj just for grins and giggles. I have installed the kernel and world using DESTDIR to put it on the corrupt drive. Same messages again. I now have the corrupt drive mounted on /mnt and am trying to update the src again. Using: freebsd-update -b /mnt fetch updated files list show /usr/src/sys… and updating to 9.1-RELEASE-p7 freebsd-update -b /mnt install This is running slower than molasses in January. Its run for almost 30 minutes and only 3 files have been updated. There must be network issues between me and the server. I'll let it run tonight but I am going to crash now. Long day. More tomorrow. -- Doug Have you checked the dmesg output, specifically to see if there are any disk errors, perhaps the hard drive is about dead. If you are planning to rebuild world and kernel form source, why not just use svn or extract the source from the 9.2-RELEASE disk onto the system. There are no hardware errors logged. The drive is only a couple months old. Smart drive status is good. I tried downloading the src with: svn co https://svn0.us-west.FreeBSD.org/base/releng/9.2 /mnt/usr/src I didn't get Release 9.2. The first entry in UPDATING is: 20130705: hastctl(8)'s `status' command output changed to terse one-liner format. Scripts using this should switch to `list' command or be rewritten. There is an entry earlier for Release 9.1. but no entry for Release 9.2. ___ 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 Hello Doug, Here is a more recent version of the file on svn: http://svnweb.freebsd.org/base/stable/9/UPDATING?revision=255900view=markup Earlier today I also checked out base for releng/9.2 from the same mirror, svn0.us-west. My UPDATING file is outdated too. Time of the last entry is 20130705. The mirror told me that I had checked out revision 256150. When running freebsd-update upgrade -r RELEASE-9.2 last night it gave : WARNING: This system is running a customcl kernel, which is not a kernel configuration distributed as part of FreeBSD 9.1-RELEASE. This kernel will not be updated: you MUST update the kernel manually before running /usr/sbin/freebsd-update install. That might have been expected, but I have read on this list that freebsd-update will sometimes automatically replace a custom kernel with a generic, and in /etc/freebsd-update.conf I had the line: Components src world kernel . HTH, Cary -- c...@sdf.org SDF Public Access UNIX System - http://sdf.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: 9.1 - 9.2 upgrade
On Tue, 8 Oct 2013 11:20:40 -0700, Doug Hardie wrote: I tried downloading the src with: svn co https://svn0.us-west.FreeBSD.org/base/releng/9.2 /mnt/usr/src I didn't get Release 9.2. The first entry in UPDATING is: 20130705: hastctl(8)'s `status' command output changed to terse one-liner format. Scripts using this should switch to `list' command or be rewritten. There is an entry earlier for Release 9.1. but no entry for Release 9.2. You could try downloading and extracting the src distribution: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/9.2-RELEASE/src.txz -- 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: 9.1 - 9.2 upgrade
Polytropon wrote: On Tue, 8 Oct 2013 11:20:40 -0700, Doug Hardie wrote: I tried downloading the src with: svn co https://svn0.us-west.FreeBSD.org/base/releng/9.2 /mnt/usr/src I didn't get Release 9.2. The first entry in UPDATING is: 20130705: hastctl(8)'s `status' command output changed to terse one-liner format. Scripts using this should switch to `list' command or be rewritten. There is an entry earlier for Release 9.1. but no entry for Release 9.2. You could try downloading and extracting the src distribution: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/9.2-RELEASE/src.txz Yes, that might have been simpler. Knew there had to be some other way. :) -- c...@sdf.org SDF Public Access UNIX System - http://sdf.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: freebsd-update upgrade -r 7.4-RELEASE-p12
alexus wrote: ok, I just did fetch install and got bumped from p5 to p9 # uname -a FreeBSD XX.X.org 7.4-RELEASE-p9 FreeBSD 7.4-RELEASE-p9 #0: Mon Jun 11 19:47:58 UTC 2012 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # can I take it all the way to -p12? -p10 through -p12 probably didn't involve any kernel changes. Bumping the reported patchlevel isn't considered important enough to warrant building a new kernel. If your sources are in /usr/src, do this: grep -v # /usr/src/sys/conf/newvers.sh | head -4 ___ 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-update upgrade -r 7.4-RELEASE-p12
bash-4.2# freebsd-update upgrade -r 7.4-RELEASE-p12 Looking up update.FreeBSD.org mirrors... 5 mirrors found. Fetching metadata signature for 7.4-RELEASE from update4.freebsd.org... done. Fetching metadata index... 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/lib32 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 7.4-RELEASE-p12 from update4.freebsd.org... failed. Fetching metadata signature for 7.4-RELEASE-p12 from update5.freebsd.org... failed. Fetching metadata signature for 7.4-RELEASE-p12 from update6.freebsd.org... failed. Fetching metadata signature for 7.4-RELEASE-p12 from update2.freebsd.org... failed. Fetching metadata signature for 7.4-RELEASE-p12 from update3.freebsd.org... failed. No mirrors remaining, giving up. bash-4.2# uname -a FreeBSD XX.X.org 7.4-RELEASE-p5 FreeBSD 7.4-RELEASE-p5 #0: Fri Dec 23 17:36:54 UTC 2011 r...@xx.x.org:/usr/obj/usr/src74/sys/GENERIC amd64 bash-4.2# Is there a way to upgrade 7.4-RELEASE-p5 to 7.4-RELEASE-p12 using freebsd-update now? -- http://alexus.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: freebsd-update upgrade -r 7.4-RELEASE-p12
On Mon, 7 Oct 2013 15:22:17 -0400 alexus ale...@gmail.com wrote: bash-4.2# freebsd-update upgrade -r 7.4-RELEASE-p12 Is there a way to upgrade 7.4-RELEASE-p5 to 7.4-RELEASE-p12 using freebsd-update now? What about: # freebsd-update fetch # freebsd-update install http://www.freebsd.org/security/ Andreas -- Andreas Rudisch a...@sectorbyte.de ___ 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: freebsd-update upgrade -r 7.4-RELEASE-p12
On Mon, Oct 7, 2013, at 14:22, alexus wrote: bash-4.2# freebsd-update upgrade -r 7.4-RELEASE-p12 Just freebsd-update fetch freebsd-update install is all you should have to run. The -r flag is for jumping major releases (from 7.x to 8.x, for example). I can't comment on whether or not the freebsd-update data for 7.x is still on the servers, though. ___ 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: freebsd-update upgrade -r 7.4-RELEASE-p12
ok, I just did fetch install and got bumped from p5 to p9 # uname -a FreeBSD XX.X.org 7.4-RELEASE-p9 FreeBSD 7.4-RELEASE-p9 #0: Mon Jun 11 19:47:58 UTC 2012 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # can I take it all the way to -p12? (I'm running fetch again, hoping it will do that) On Mon, Oct 7, 2013 at 4:16 PM, Mark Felder f...@freebsd.org wrote: On Mon, Oct 7, 2013, at 14:22, alexus wrote: bash-4.2# freebsd-update upgrade -r 7.4-RELEASE-p12 Just freebsd-update fetch freebsd-update install is all you should have to run. The -r flag is for jumping major releases (from 7.x to 8.x, for example). I can't comment on whether or not the freebsd-update data for 7.x is still on the servers, though. ___ 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 -- http://alexus.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: freebsd-update upgrade -r 7.4-RELEASE-p12
it didn't help.. # freebsd-update fetch Looking up update.FreeBSD.org mirrors... 5 mirrors found. Fetching metadata signature for 7.4-RELEASE from update6.freebsd.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. The following files are affected by updates, but no changes have been downloaded because the files have been modified locally: /var/db/mergemaster.mtree No updates needed to update system to 7.4-RELEASE-p12. WARNING: FreeBSD 7.4-RELEASE-p9 HAS PASSED ITS END-OF-LIFE DATE. Any security issues discovered after Fri Mar 1 00:00:00 UTC 2013 will not have been corrected. # freebsd-update install No updates are available to install. Run '/usr/sbin/freebsd-update fetch' first. # On Mon, Oct 7, 2013 at 5:13 PM, alexus ale...@gmail.com wrote: ok, I just did fetch install and got bumped from p5 to p9 # uname -a FreeBSD XX.X.org 7.4-RELEASE-p9 FreeBSD 7.4-RELEASE-p9 #0: Mon Jun 11 19:47:58 UTC 2012 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # can I take it all the way to -p12? (I'm running fetch again, hoping it will do that) On Mon, Oct 7, 2013 at 4:16 PM, Mark Felder f...@freebsd.org wrote: On Mon, Oct 7, 2013, at 14:22, alexus wrote: bash-4.2# freebsd-update upgrade -r 7.4-RELEASE-p12 Just freebsd-update fetch freebsd-update install is all you should have to run. The -r flag is for jumping major releases (from 7.x to 8.x, for example). I can't comment on whether or not the freebsd-update data for 7.x is still on the servers, though. ___ 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 -- http://alexus.org/ -- http://alexus.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: Problem completing a 9.1 release to 9.2 release upgrade
On 05/10/2013 21:41, Polytropon wrote: On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote: I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just be able to do a cd /usr/src make buildworld make installworld reboot and I'll be running up on the 9.2 kernel and then I'll be all set? No. You should follow the procedure mentioned in the comment header of /usr/src/Makefile. From my (old) b-STABLE system: # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. 4. can be combined by using the kernel target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster'(you may wish to use -i, along with -U or -F). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) Pick what you need to do. When kernel and world sources are in sync, a new kernel can always be installed in multi-user mode. To install world, you should drop to single-user mode to avoid interferences with a full-featured system running in the background. This procedure (or parts of it) will also work when you have been using freebsd-update to modify your kernel, world, and sources. Errrmm... The OP is maintaining his system using freebsd-update -- just building and installing a replacement kernel from the source tree installed via freebsd-update is in fact perfectly OK and a supported way to manage a FreeBSD system. While you are quoting the official instructions from /usr/src/UPDATING here (so they are completely correct in that sense) these are the instructions to do something rather different to what the OP intended. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Problem completing a 9.1 release to 9.2 release upgrade
On Sun, 06 Oct 2013 08:08:42 +0100, Matthew Seaman wrote: On 05/10/2013 21:41, Polytropon wrote: On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote: I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just be able to do a cd /usr/src make buildworld make installworld reboot and I'll be running up on the 9.2 kernel and then I'll be all set? No. You should follow the procedure mentioned in the comment header of /usr/src/Makefile. From my (old) b-STABLE system: # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. 4. can be combined by using the kernel target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster'(you may wish to use -i, along with -U or -F). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) Pick what you need to do. When kernel and world sources are in sync, a new kernel can always be installed in multi-user mode. To install world, you should drop to single-user mode to avoid interferences with a full-featured system running in the background. This procedure (or parts of it) will also work when you have been using freebsd-update to modify your kernel, world, and sources. Errrmm... The OP is maintaining his system using freebsd-update -- just building and installing a replacement kernel from the source tree installed via freebsd-update is in fact perfectly OK and a supported way to manage a FreeBSD system. That is true. But if I understand the question (as quoted above) correctly, installing world from source has been involved, that's why my suggestion of following the instructions (or a subset of them, as it applies). While you are quoting the official instructions from /usr/src/UPDATING here (so they are completely correct in that sense) these are the instructions to do something rather different to what the OP intended. I've copied the the instructions from the comment header of /usr/src/Makefile (at least on my outdated system at home they're there). Of course if the _only_ problem of the initial question is to install a custom kernel, with an otherwise updated system using freebsd-update (with world, kernel and sources in sync), just installing a custom kernel from within multi-user mode is fully supported by the system. This implies that only a small subset of the quoted instructions would apply here (steps 1 and 3 - 5), after freebsd-update has been finished successfully. -- 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: Problem completing a 9.1 release to 9.2 release upgrade
On 06/10/2013 04:51, Eric Feldhusen wrote:
I figured I'd walk through those steps from start to finish and just
correct my main problem and any other little glitches I might have.
I'm on step 6 and when I run mergemaster -p, I get the following error.
*** Creating the temporary root environment in /var/tmp/temproot
*** /var/tmp/temproot ready for use
*** Creating and populating directory structure in /var/tmp/temproot
/usr/bin/install: Undefined symbol gid_from_group
*** FATAL ERROR: Cannot copy files to the temproot environment
I found this thread on the Freebsd forums
http://forums.freebsd.org/showthread.php?t=41779 with the same error and if
I do the same diagnostic steps of
truss install -d -g wheel ~/testdirectory
I find an error of
lstat(/usr/local/etc/libmap.d,0x7fffb990) ERR#2 'No such file or
directory'
Any suggestions? Thank you for the help thus far.
The 'undefined symbol' error means you have a binary which is somehow
not dynamically linking against the shared libraries it was compiled to
use. As install(1) has pretty simple dynamic library usage -- just
libmd and libc:
# ldd /usr/bin/install
/usr/bin/install:
libmd.so.5 = /lib/libmd.so.5 (0x800822000)
libc.so.7 = /lib/libc.so.7 (0x800a33000)
... and libmd.so just contains code for computing various checksums,
nothing to do with groups and GIDs. This suggests that your libc.so is
somehow incompatible with your /usr/bin/install. Which really shouldn't
be the case given that you'ld previously used freebsd-update to upgrade
your userland to 9.2-RELEASE.
Things to double check:
* you haven't been faffing about with /etc/libmap.conf -- that file
or any file it includes should basically be empty except in quite
unusual circumstances. Remember folks: libmap is not your
solution of choice. It's what you turn to when there are no other
viable alternatives.
* Your freebsd-update really has been updating the source tree you
attempted to upgrade from. Check /etc/freebsd-update.conf. By
default it contains:
# Components of the base system which should be kept updated.
Components src world kernel
If you don't have src in there your buildworld procedure will at
best be trying to take you back down to 9.1-RELEASE-p???, and at
worst trying to create some unholy mixture of 9.2 kernel with
earlier bits of the system.
I think you should be able to recover to a system managed via
freebsd-update by something like:
# vi /etc/freebsd-update.conf
{ Make sure you're getting 'src world kernel' components as shown
above }
# freebsd-update fetch
# freebsd-update install
but I haven't tested that so ICBW. In any case, this should get you
back to the state where you have a 9.2-RELEASE world but your modified
9.1-RELEASE kernel. If you still need a custom kernel then you can
build and install it like so:
# cd /usr/src
# make KERNCONF=MYKERNEL buildkernel
# make KERNCONF=MYKERNEL installkernel
and reboot. Otherwise, I'm not sure exactly how you'ld revert from a
custom kernel to the standard generic kernel you'ld normally get via
freebsd-update. What I'd try is moving aside my customized kernel and
re-running freebsd-update:
# cd /boot
# mv kernel kernel-MYKERNEL
# freebsd-update install
If that creates a new /boot/kernel and populates with a new kernel and
many loadable modules then you're golden. If not, move your saved
kernel back into place (mv kernel-MYKERNEL kernel) and ask here again.
The 'no such file or directory' error for /usr/local/etc/libmap.d thing
is a false problem: /usr/local/etc/libmap.d is an optional directory --
all you are seeing is install(1) trying to open it and discovering that
it doesn't exist.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
JID: matt...@infracaninophile.co.uk
signature.asc
Description: OpenPGP digital signature
Problem completing a 9.1 release to 9.2 release upgrade
I have a server that was/is running 9.1 release that I tried to upgrade to 9.2 release. I missed the step of updating to the latest 9.1 patches by doing freebsd-update fetch freebsd-update install I went right to freebsd-update upgrade -r 9.2-RELEASE freebsd-update install rebooot freebsd-update install reboot again But my system still comes up as 9.1 release. Any suggestions on the steps to fix my goof? Eric Feldhusen ___ 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 completing a 9.1 release to 9.2 release upgrade
On 05/10/2013 20:11, Eric Feldhusen wrote: I have a server that was/is running 9.1 release that I tried to upgrade to 9.2 release. I missed the step of updating to the latest 9.1 patches by doing freebsd-update fetch freebsd-update install I went right to freebsd-update upgrade -r 9.2-RELEASE freebsd-update install rebooot freebsd-update install reboot again But my system still comes up as 9.1 release. Any suggestions on the steps to fix my goof? Did you replace the generic kernel from 9.1-RELEASE with something you compiled yourself? If so, you may well have caused freebsd-update to ignore any modifications to the kernel. You can fix that by re-compiling a kernel using the 9.2-RELEASE sources and basically the same kernel configuration as for 9.1 (you will need to check for 9.2 related differences to the configuration, but these are likely to be pretty minor or not needed at all.) If you aren't using a customized kernel, then has the kernel in the standard location on your system actually been updated? You can tell if it's a 9.2 kernel by running strings(1) against the kernel binary, like so: # strings /boot/kernel/kernel | grep RELEASE If that's clearly a 9.2 kernel, then are you actually booting up from a different kernel somewhere else on your system? First of all, are there any other copies of FreeBSD kernels around anywhere -- on memsticks, or on split mirrors perhaps? You may need to fiddle with the bios settings or interrupt the boot sequence and type things directly at the loader if so. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Problem completing a 9.1 release to 9.2 release upgrade
Ah, yes, when this particular box was a 9.0-release, I had compiled a custom kernel to enable ipsec. When I check the strings, it's a 9.1 release kernel. I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just be able to do a cd /usr/src make buildworld make installworld reboot and I'll be running up on the 9.2 kernel and then I'll be all set? Thanks for the help. Eric On Sat, Oct 5, 2013 at 3:34 PM, Matthew Seaman matt...@freebsd.org wrote: On 05/10/2013 20:11, Eric Feldhusen wrote: I have a server that was/is running 9.1 release that I tried to upgrade to 9.2 release. I missed the step of updating to the latest 9.1 patches by doing freebsd-update fetch freebsd-update install I went right to freebsd-update upgrade -r 9.2-RELEASE freebsd-update install rebooot freebsd-update install reboot again But my system still comes up as 9.1 release. Any suggestions on the steps to fix my goof? Did you replace the generic kernel from 9.1-RELEASE with something you compiled yourself? If so, you may well have caused freebsd-update to ignore any modifications to the kernel. You can fix that by re-compiling a kernel using the 9.2-RELEASE sources and basically the same kernel configuration as for 9.1 (you will need to check for 9.2 related differences to the configuration, but these are likely to be pretty minor or not needed at all.) If you aren't using a customized kernel, then has the kernel in the standard location on your system actually been updated? You can tell if it's a 9.2 kernel by running strings(1) against the kernel binary, like so: # strings /boot/kernel/kernel | grep RELEASE If that's clearly a 9.2 kernel, then are you actually booting up from a different kernel somewhere else on your system? First of all, are there any other copies of FreeBSD kernels around anywhere -- on memsticks, or on split mirrors perhaps? You may need to fiddle with the bios settings or interrupt the boot sequence and type things directly at the loader if so. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey ___ 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 completing a 9.1 release to 9.2 release upgrade
On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote: I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just be able to do a cd /usr/src make buildworld make installworld reboot and I'll be running up on the 9.2 kernel and then I'll be all set? No. You should follow the procedure mentioned in the comment header of /usr/src/Makefile. From my (old) b-STABLE system: # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. 4. can be combined by using the kernel target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster'(you may wish to use -i, along with -U or -F). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) Pick what you need to do. When kernel and world sources are in sync, a new kernel can always be installed in multi-user mode. To install world, you should drop to single-user mode to avoid interferences with a full-featured system running in the background. This procedure (or parts of it) will also work when you have been using freebsd-update to modify your kernel, world, and sources. -- 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: Problem completing a 9.1 release to 9.2 release upgrade
I figured I'd walk through those steps from start to finish and just correct my main problem and any other little glitches I might have. I'm on step 6 and when I run mergemaster -p, I get the following error. *** Creating the temporary root environment in /var/tmp/temproot *** /var/tmp/temproot ready for use *** Creating and populating directory structure in /var/tmp/temproot /usr/bin/install: Undefined symbol gid_from_group *** FATAL ERROR: Cannot copy files to the temproot environment I found this thread on the Freebsd forums http://forums.freebsd.org/showthread.php?t=41779 with the same error and if I do the same diagnostic steps of truss install -d -g wheel ~/testdirectory I find an error of lstat(/usr/local/etc/libmap.d,0x7fffb990) ERR#2 'No such file or directory' Any suggestions? Thank you for the help thus far. Eric On Sat, Oct 5, 2013 at 4:41 PM, Polytropon free...@edvax.de wrote: On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote: I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just be able to do a cd /usr/src make buildworld make installworld reboot and I'll be running up on the 9.2 kernel and then I'll be all set? No. You should follow the procedure mentioned in the comment header of /usr/src/Makefile. From my (old) b-STABLE system: # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. 4. can be combined by using the kernel target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster'(you may wish to use -i, along with -U or -F). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) Pick what you need to do. When kernel and world sources are in sync, a new kernel can always be installed in multi-user mode. To install world, you should drop to single-user mode to avoid interferences with a full-featured system running in the background. This procedure (or parts of it) will also work when you have been using freebsd-update to modify your kernel, world, and sources. -- 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: 9.1 - 9.2 upgrade
On 10/04/2013 1:36 am, Doug Hardie wrote: On 3 October 2013, at 11:48, Doug Hardie bc...@lafn.org wrote: On 3 October 2013, at 10:49, Doug Hardie bc...@lafn.org wrote: I just did an upgrade using freebsd-update to 9.2. This system uses a custom kernel so I am rebuilding everything after the update completed. However, I noticed that /usr/src/UPDATING has not been updated. The first entry still says: 9.1-RELEASE. Is this correct? Well, it just got worse - The last reboot now fails: I am using a remote console and it shows: -- Press a key on the console to reboot -- Rebooting... Consoles: internal video/keyboard serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 639kB/2087360kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (d...@zool.lafn.org, Thu Oct 3 04:23:13 PDT 2013) Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: panic: free: guard1 fail @ 0x7f481ed0 from /usr/src/sys/boot/i386/loader/../../common/module.c:1004 -- Press a key on the console to reboot -- I can enter a string as it doesn't try to reboot again till the return is entered. I've tried b disk1, but it still only tries disk0. The system rebooted fine after the reboot after make kernel. Mergemaster didn't seem to affect anything dealing with boot. Don't know what make delete-old does but the descriptions lead me to not believe it could cause this. This system is on the other side of LA from me so its a major trip timewise. Any ideas how this can be recovered remotely? Booting off the live CD didn't find anything obviously wrong. I replaced the kernel with the old one and still the same error. I am having the drive mailed to me and will work with it here. However, it appears a new install is going to be required. The old sysinstall had the capability to skip over the formatting of the disk by just entering quit. It would then just replace the system components and leave everything else alone. I don't see any obvious way to do the same thing with bsdinstall. Is there a way to do that. I don't want to have to completely rebuild the drive, but just replace the 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 Just want to clarify the steps that started this if I read everything right: Step 1: freebsd-update from 9.1 to 9.2 Step 2: compile from source ? Was this world, or just the custom kernel?? Step 3: make delete-old Step 4: mergemaster Step 5: reboot oops, something went wrong.. If my suspicions are correct, the source was still 9.1 patch 7, but the system was running 9.2 from the binary update. This may have caused the make delete-old to delete things it shouldn't have The very first thing I would do is bring the disk up in another system and make a backup copy of the data. I have never tried this process, I am basically just taking the steps I use for updating a zfs system using boot environments, and applying them in order to build a new kernel and world to an alternate directory, as a method of recovering the system. The next step I would take is to then mount the file systems in an alternate location, /mnt for example make MAKEOBJDIRPREFIX /mnt/usr/obj make DESTDIR /mnt cd /mnt/usr/src rm -r * .svn rm -r /usr/obj/* svn co https://svn0.us-west.freebsd.org/base/releng/9.2 make buildwolrd make buildkernel make installkernel make installworld make -DBATCH_DELETE_OLD_FILES delete-old make -DBATCH_DELETE_OLD_FILES delete-old-libs mergemaster -Ui /mnt/usr/src -D /mnt With some luck the file system will now contain a boot-able FreeBSD install, that will still have all the settings in place, except it will be the generic kernel. You should then just be able to build and install the custom kernel, from the booted system as you normally would. -- 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
Re: 9.1 - 9.2 upgrade
On 4 October 2013, at 09:22, dweimer dwei...@dweimer.net wrote: On 10/04/2013 1:36 am, Doug Hardie wrote: On 3 October 2013, at 11:48, Doug Hardie bc...@lafn.org wrote: On 3 October 2013, at 10:49, Doug Hardie bc...@lafn.org wrote: I just did an upgrade using freebsd-update to 9.2. This system uses a custom kernel so I am rebuilding everything after the update completed. However, I noticed that /usr/src/UPDATING has not been updated. The first entry still says: 9.1-RELEASE. Is this correct? Well, it just got worse - The last reboot now fails: I am using a remote console and it shows: -- Press a key on the console to reboot -- Rebooting... Consoles: internal video/keyboard serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 639kB/2087360kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (d...@zool.lafn.org, Thu Oct 3 04:23:13 PDT 2013) Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: panic: free: guard1 fail @ 0x7f481ed0 from /usr/src/sys/boot/i386/loader/../../common/module.c:1004 -- Press a key on the console to reboot -- I can enter a string as it doesn't try to reboot again till the return is entered. I've tried b disk1, but it still only tries disk0. The system rebooted fine after the reboot after make kernel. Mergemaster didn't seem to affect anything dealing with boot. Don't know what make delete-old does but the descriptions lead me to not believe it could cause this. This system is on the other side of LA from me so its a major trip timewise. Any ideas how this can be recovered remotely? Booting off the live CD didn't find anything obviously wrong. I replaced the kernel with the old one and still the same error. I am having the drive mailed to me and will work with it here. However, it appears a new install is going to be required. The old sysinstall had the capability to skip over the formatting of the disk by just entering quit. It would then just replace the system components and leave everything else alone. I don't see any obvious way to do the same thing with bsdinstall. Is there a way to do that. I don't want to have to completely rebuild the drive, but just replace the 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 Just want to clarify the steps that started this if I read everything right: Step 1: freebsd-update from 9.1 to 9.2 Step 2: compile from source ? Was this world, or just the custom kernel?? Step 3: make delete-old Step 4: mergemaster Step 5: reboot oops, something went wrong.. If my suspicions are correct, the source was still 9.1 patch 7, but the system was running 9.2 from the binary update. This may have caused the make delete-old to delete things it shouldn't have The very first thing I would do is bring the disk up in another system and make a backup copy of the data. I have never tried this process, I am basically just taking the steps I use for updating a zfs system using boot environments, and applying them in order to build a new kernel and world to an alternate directory, as a method of recovering the system. The next step I would take is to then mount the file systems in an alternate location, /mnt for example make MAKEOBJDIRPREFIX /mnt/usr/obj make DESTDIR /mnt cd /mnt/usr/src rm -r * .svn rm -r /usr/obj/* svn co https://svn0.us-west.freebsd.org/base/releng/9.2 make buildwolrd make buildkernel make installkernel make installworld make -DBATCH_DELETE_OLD_FILES delete-old make -DBATCH_DELETE_OLD_FILES delete-old-libs mergemaster -Ui /mnt/usr/src -D /mnt With some luck the file system will now contain a boot-able FreeBSD install, that will still have all the settings in place, except it will be the generic kernel. You should then just be able to build and install the custom kernel, from the booted system as you normally would. The exact sequence was: Step 1: freebsd-update from 9.1 to 9.2 Step 2: make buildworld Step 3: make build_kernel KERNCONF=LAFN Step 4: make install_kernel KERNCONF=LAFN Step 5: reboot Step 6: mergemaster -p Step 7: make installworld Step 8: mergemaster -i Step 9: make delete-old Step 10: reboot oops, something went wrong.. After step 5, uname -a still showed 9.2 but now it listed the kernel I built rather than generic. ___ 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: 9.1 - 9.2 upgrade
On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: The exact sequence was: Step 1: freebsd-update from 9.1 to 9.2 Have you verified in /etc/freebsd-update.conf that src is definitely part of what should be updated? Step 2: make buildworld Step 3: make build_kernel KERNCONF=LAFN Step 4: make install_kernel KERNCONF=LAFN I assume the correct targets buildkernel and installkernel have been used. ;-) Step 5: reboot Attention: Into single-user mode. Step 6: mergemaster -p Step 7: make installworld Step 8: mergemaster -i Step 9: make delete-old Step 10: reboot Into multi-user mode again. oops, something went wrong.. After step 5, uname -a still showed 9.2 but now it listed the kernel I built rather than generic. Again, verify your configuration. Compare your steps with the comment header of /usr/src/Makefile which illustrates the exact procedure; from a (dated) 8-STABLE installation: 1. `cd /usr/src' (or to the directory containing your source tree). 2. `make buildworld' 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). [steps 3. 4. can be combined by using the kernel target] 5. `reboot'(in single user mode: boot -s from the loader prompt). 6. `mergemaster -p' 7. `make installworld' 8. `make delete-old' 9. `mergemaster'(you may wish to use -i, along with -U or -F). 10. `reboot' 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) -- 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: 9.1 - 9.2 upgrade
On 4 October 2013, at 19:08, Polytropon free...@edvax.de wrote: On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: The exact sequence was: Step 1: freebsd-update from 9.1 to 9.2 Have you verified in /etc/freebsd-update.conf that src is definitely part of what should be updated? System is not bootable - can't verify anything… Step 2: make buildworld Step 3: make build_kernel KERNCONF=LAFN Step 4: make install_kernel KERNCONF=LAFN I assume the correct targets buildkernel and installkernel have been used. ;-) Yes Step 5: reboot Attention: Into single-user mode. Not possible since the system is located over 100 miles away. Everything has to be done via remote console. Step 6: mergemaster -p Step 7: make installworld Step 8: mergemaster -i Step 9: make delete-old Step 10: reboot Into multi-user mode again. oops, something went wrong.. After step 5, uname -a still showed 9.2 but now it listed the kernel I built rather than generic. Again, verify your configuration. Compare your steps with the comment header of /usr/src/Makefile which illustrates the exact procedure; from a (dated) 8-STABLE installation: 1. `cd /usr/src' (or to the directory containing your source tree). 2. `make buildworld' 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). [steps 3. 4. can be combined by using the kernel target] 5. `reboot'(in single user mode: boot -s from the loader prompt). 6. `mergemaster -p' 7. `make installworld' 8. `make delete-old' 9. `mergemaster'(you may wish to use -i, along with -U or -F). 10. `reboot' 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) -- 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: 9.1 - 9.2 upgrade
On Fri, 4 Oct 2013 19:42:15 -0700, Doug Hardie wrote: On 4 October 2013, at 19:08, Polytropon free...@edvax.de wrote: On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: The exact sequence was: Step 1: freebsd-update from 9.1 to 9.2 Have you verified in /etc/freebsd-update.conf that src is definitely part of what should be updated? System is not bootable - can't verify anything… Does the system (or better, its enclosure, software-wise) allow booting a rescue system or an emergency media, such as a FreeBSD v9 live system? The file /etc/freebsd-update.conf should contain the line Components src world kernel if you want to make sure the source is properly updated, along with the world and kernel (GENERIC). Step 5: reboot Attention: Into single-user mode. Not possible since the system is located over 100 miles away. Everything has to be done via remote console. Does this mean SSH only or do you have a _real_ console transmission by which you can access the system _prior_ to the OS providing the SSH access? I'm mentioning this because the traditional approach requires (few) steps done in the single-user mode where no SSH connectivity is provided in the normal way... -- 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: 9.1 - 9.2 upgrade
On 4 October 2013, at 20:03, Polytropon free...@edvax.de wrote: On Fri, 4 Oct 2013 19:42:15 -0700, Doug Hardie wrote: On 4 October 2013, at 19:08, Polytropon free...@edvax.de wrote: On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: The exact sequence was: Step 1: freebsd-update from 9.1 to 9.2 Have you verified in /etc/freebsd-update.conf that src is definitely part of what should be updated? System is not bootable - can't verify anything… Does the system (or better, its enclosure, software-wise) allow booting a rescue system or an emergency media, such as a FreeBSD v9 live system? Yes - but there is no one there who can successfully be told how to run it. We have serious communications issues - they want to use back slashes and have no idea what a slash is. Even if you tell them which key to use, they know better and use a back slash cause thats what Windoze uses. The disk should be in the mail to me now. I will be able to work with it when it arrives. The file /etc/freebsd-update.conf should contain the line Components src world kernel if you want to make sure the source is properly updated, along with the world and kernel (GENERIC). As indicated before, I don't think all the source got updated. The kernel showed 9.2 after recompilation. However UPDATING was not updated. Thats as much as I could check before. Step 5: reboot Attention: Into single-user mode. Not possible since the system is located over 100 miles away. Everything has to be done via remote console. Does this mean SSH only or do you have a _real_ console transmission by which you can access the system _prior_ to the OS providing the SSH access? I'm mentioning this because the traditional approach requires (few) steps done in the single-user mode where no SSH connectivity is provided in the normal way… I have a telnet box that has serial connections to the console ports. That approach has been used without any issues since FreeBSD 2.5. I do disable all ports during the process via an reduced rc.conf file. -- 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: 9.1 - 9.2 upgrade
On Fri, 4 Oct 2013 21:49:18 -0700, Doug Hardie wrote: On 4 October 2013, at 20:03, Polytropon free...@edvax.de wrote: On Fri, 4 Oct 2013 19:42:15 -0700, Doug Hardie wrote: On 4 October 2013, at 19:08, Polytropon free...@edvax.de wrote: On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: The exact sequence was: Step 1: freebsd-update from 9.1 to 9.2 Have you verified in /etc/freebsd-update.conf that src is definitely part of what should be updated? System is not bootable - can't verify anything… Does the system (or better, its enclosure, software-wise) allow booting a rescue system or an emergency media, such as a FreeBSD v9 live system? Yes - but there is no one there who can successfully be told how to run it. Not even inserting a USB stick (with the FreeBSD memstick data) or a CD? We have serious communications issues - they want to use back slashes and have no idea what a slash is. Maybe that is the result of many years of administration on Windows PCs. :-) Even if you tell them which key to use, they know better and use a back slash cause thats what Windoze uses. Uh... knowing better would disqualify them as maintainers of a server installation. The inability to learn (or even to read and follow instructions) is a dangerous thing. The disk should be in the mail to me now. I will be able to work with it when it arrives. Okay, that's also a possible alternative. To be honest, that's the first time I hear about this procedure. But doable. The file /etc/freebsd-update.conf should contain the line Components src world kernel if you want to make sure the source is properly updated, along with the world and kernel (GENERIC). As indicated before, I don't think all the source got updated. The kernel showed 9.2 after recompilation. However UPDATING was not updated. Thats as much as I could check before. I assume that this could be possible by inconsistently updated sources. It would be a good start to remove /usr/src and download the sources of the correct version via SVN _or_ freebsd-update again. Before the next installation attempt, /usr/obj should be removed as well, just to be sure. Step 5: reboot Attention: Into single-user mode. Not possible since the system is located over 100 miles away. Everything has to be done via remote console. Does this mean SSH only or do you have a _real_ console transmission by which you can access the system _prior_ to the OS providing the SSH access? I'm mentioning this because the traditional approach requires (few) steps done in the single-user mode where no SSH connectivity is provided in the normal way… I have a telnet box that has serial connections to the console ports. That approach has been used without any issues since FreeBSD 2.5. I do disable all ports during the process via an reduced rc.conf file. A serial console should also work, but even though I've been using serial consoles (and _real_ serial terminals), one thing I'm not sure about: Is it possible to interrupt (!) the boot process at an early stage to get to the loader prompt and boot into single user mode from there? Ok boot -s If not, do you have the beastie menu (or whatever it is called today) enabled to go to SUM to perform the make installworld step? Anyway, if you can install everything is required with the disk at home, and then send it back to that datacenter (according to your characterization, the quotes are deserved), that should solve the problems and make sure everything works as intended. -- 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
9.1 - 9.2 upgrade, clang question
When upgrading from 9.1 to 9.2 using source, is there any benefit to rebuilding twice, due to the clang version change? So that the second buildworld/kernel is done from the updated clang 3.3, instead of the clang 3.1 that was in FreeBSD 9.1? -- 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
Re: 9.1 - 9.2 upgrade, clang question
03.10.2013 17:36, dweimer wrote: When upgrading from 9.1 to 9.2 using source, is there any benefit to rebuilding twice, due to the clang version change? So that the second buildworld/kernel is done from the updated clang 3.3, instead of the clang 3.1 that was in FreeBSD 9.1? During the buildworld first new compiler is built and then this new compiler is used to build everything else. There may be other reasons to double build though... Maybe after cleaning system with `make delete-old`/`make delete-old-libs`? -- Sphinx of black quartz, judge my vow. ___ 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
9.1 - 9.2 upgrade
I just did an upgrade using freebsd-update to 9.2. This system uses a custom kernel so I am rebuilding everything after the update completed. However, I noticed that /usr/src/UPDATING has not been updated. The first entry still says: 9.1-RELEASE. Is this correct? ___ 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: 9.1 - 9.2 upgrade
On 3 October 2013, at 10:49, Doug Hardie bc...@lafn.org wrote: I just did an upgrade using freebsd-update to 9.2. This system uses a custom kernel so I am rebuilding everything after the update completed. However, I noticed that /usr/src/UPDATING has not been updated. The first entry still says: 9.1-RELEASE. Is this correct? Well, it just got worse - The last reboot now fails: I am using a remote console and it shows: -- Press a key on the console to reboot -- Rebooting... Consoles: internal video/keyboard serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 639kB/2087360kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (d...@zool.lafn.org, Thu Oct 3 04:23:13 PDT 2013) Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: panic: free: guard1 fail @ 0x7f481ed0 from /usr/src/sys/boot/i386/loader/../../common/module.c:1004 -- Press a key on the console to reboot -- I can enter a string as it doesn't try to reboot again till the return is entered. I've tried b disk1, but it still only tries disk0. The system rebooted fine after the reboot after make kernel. Mergemaster didn't seem to affect anything dealing with boot. Don't know what make delete-old does but the descriptions lead me to not believe it could cause this. This system is on the other side of LA from me so its a major trip timewise. Any ideas how this can be recovered remotely? ___ 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: 9.1 - 9.2 upgrade
On 10/03/2013 1:48 pm, Doug Hardie wrote: On 3 October 2013, at 10:49, Doug Hardie bc...@lafn.org wrote: I just did an upgrade using freebsd-update to 9.2. This system uses a custom kernel so I am rebuilding everything after the update completed. However, I noticed that /usr/src/UPDATING has not been updated. The first entry still says: 9.1-RELEASE. Is this correct? Well, it just got worse - The last reboot now fails: I am using a remote console and it shows: -- Press a key on the console to reboot -- Rebooting... Consoles: internal video/keyboard serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 639kB/2087360kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (d...@zool.lafn.org, Thu Oct 3 04:23:13 PDT 2013) Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: panic: free: guard1 fail @ 0x7f481ed0 from /usr/src/sys/boot/i386/loader/../../common/module.c:1004 -- Press a key on the console to reboot -- I can enter a string as it doesn't try to reboot again till the return is entered. I've tried b disk1, but it still only tries disk0. The system rebooted fine after the reboot after make kernel. Mergemaster didn't seem to affect anything dealing with boot. Don't know what make delete-old does but the descriptions lead me to not believe it could cause this. This system is on the other side of LA from me so its a major trip timewise. Any ideas how this can be recovered remotely? ___ 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 I wonder if your source update didn't correctly download, mine starts with: Updating Information for FreeBSD current users ...[snip]... Items affecting the ports and packages system can be found in /usr/ports/UPDATING. Please read that file before running portupgrade. 20130705: hastctl(8)'s `status' command output changed to terse one-liner format. Scripts using this should switch to `list' command or be rewritten. 20130618: Fix a bug that allowed a tracing process (e.g. gdb) to write ...[snip]... 20121218: With the addition of auditdistd(8), a new auditdistd user is now depended on during installworld. mergemaster -p can be used to add the user prior to installworld, as documented in the handbook. 20121205: 9.1-RELEASE. ...[snip]... I haven't a clue how to fix your non booting system short of booting off a FreeBSD disc, going to live CD, mounting the filesystems in a temp location and doing a buildworld/kernel over again with correct source tree. -- 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
Re: 9.1 - 9.2 upgrade
On 3 October 2013, at 11:58, dweimer dwei...@dweimer.net wrote: On 10/03/2013 1:48 pm, Doug Hardie wrote: On 3 October 2013, at 10:49, Doug Hardie bc...@lafn.org wrote: I just did an upgrade using freebsd-update to 9.2. This system uses a custom kernel so I am rebuilding everything after the update completed. However, I noticed that /usr/src/UPDATING has not been updated. The first entry still says: 9.1-RELEASE. Is this correct? Well, it just got worse - The last reboot now fails: I am using a remote console and it shows: -- Press a key on the console to reboot -- Rebooting... Consoles: internal video/keyboard serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 639kB/2087360kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (d...@zool.lafn.org, Thu Oct 3 04:23:13 PDT 2013) Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: panic: free: guard1 fail @ 0x7f481ed0 from /usr/src/sys/boot/i386/loader/../../common/module.c:1004 -- Press a key on the console to reboot -- I can enter a string as it doesn't try to reboot again till the return is entered. I've tried b disk1, but it still only tries disk0. The system rebooted fine after the reboot after make kernel. Mergemaster didn't seem to affect anything dealing with boot. Don't know what make delete-old does but the descriptions lead me to not believe it could cause this. This system is on the other side of LA from me so its a major trip timewise. Any ideas how this can be recovered remotely? ___ 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 I wonder if your source update didn't correctly download, mine starts with: Updating Information for FreeBSD current users ...[snip]... Items affecting the ports and packages system can be found in /usr/ports/UPDATING. Please read that file before running portupgrade. 20130705: hastctl(8)'s `status' command output changed to terse one-liner format. Scripts using this should switch to `list' command or be rewritten. 20130618: Fix a bug that allowed a tracing process (e.g. gdb) to write ...[snip]... 20121218: With the addition of auditdistd(8), a new auditdistd user is now depended on during installworld. mergemaster -p can be used to add the user prior to installworld, as documented in the handbook. 20121205: 9.1-RELEASE. ...[snip]... I haven't a clue how to fix your non booting system short of booting off a FreeBSD disc, going to live CD, mounting the filesystems in a temp location and doing a buildworld/kernel over again with correct source tree. I have been using freebsd-update for quite awhile now and this is the first time it has failed. However, I am not convinced the kernel is bad. It never gets to the point of trying to load the kernel. Something has failed in the bootstrap process itself and I have not figured out what is the right thing to enter at that prompt. Being on-site is not a viable alternative… ___ 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
New system - go for 9.1+upgrade - or go for 9.2-RC4?
Hi, Since I'm about to set up a new system from scratch I'm thinking whether I should install 9.1 and upgrade it to 9-STABLE or to install 9.2-RC4 right away. To be specific: o) Will upgrading kernel/system using svn co svn://svn.freebsd.org/base/stable/9/ /usr/src bring a 9.2-RC4 installed system up to date once 9.2 final is released? o) Is it possible to install ports using portsnap fetch extract and pkg_add -r... on a system that was installed using the 9.2-RC4-CDs? Thanks much in advance for your help, -ewald ___ 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: New system - go for 9.1+upgrade - or go for 9.2-RC4?
On 25. sep. 2013, at 09.00, Ewald Jenisch wrote: o) Will upgrading kernel/system using svn co svn://svn.freebsd.org/base/stable/9/ /usr/src bring a 9.2-RC4 installed system up to date once 9.2 final is released? Two options: base/stable/9 - track 9-STABLE base/releng/9.2 - track 9.2-security branch The former is more of a moving target, while the latter is 9.2-RELEASE, but gets security updates. Also, rather than using svn://, I'd use https://, and pick a server from this list: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/svn-mirrors.html Terje ___ 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: New system - go for 9.1+upgrade - or go for 9.2-RC4?
On Wed, Sep 25, 2013 at 09:16:01AM +0200, Terje Elde wrote: Two options: ... Thanks - helps alot. -ewald ___ 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
Shared library not found after upgrade to 9.2-PRERELEASE
I recently upgraded a system to FreeBSD t42.umpquanet.com 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0 r254977: Wed Aug 28 19:58:37 PDT 2013 r...@t42.umpquanet.com:/usr/obj/usr/src/sys/GENERIC i386 I then deleted all the installed ports, and am rebuilding the ones I still use. I've encountered several instances where although a required port is already installed, a dependent port build will claim that the required library isn't found, and attempt a (re-)install of that port. In this example, jbig2dec claims that shared library libpng15.so is not found, although 'ls' says it is in /usr/local/lib, and 'make missing' reports no uninstalled dependencies. What can I do to remedy this, short of setting FORCE_PKG_REGISTER and spending a lot of time rebuilding ports that are already installed? Please Cc: me on replies. Thank you! Jim # cd /usr/ports/graphics/jbig2dec # ls -l /usr/local/lib/libpng15* -rw-r--r-- 1 root wheel 202762 Sep 1 16:10 /usr/local/lib/libpng15.a lrwxr-xr-x 1 root wheel 14 Sep 1 16:10 /usr/local/lib/libpng15.so@ - libpng15.so.15 -rwxr-xr-x 1 root wheel 175596 Sep 1 16:10 /usr/local/lib/libpng15.so.15* # make clean === Cleaning for png-1.5.17 === Cleaning for jbig2dec-0.11_1 # make missing # make === License GPLv3 accepted by the user === Found saved configuration for jbig2dec-0.11 === Fetching all distfiles required by jbig2dec-0.11_1 for building === Extracting for jbig2dec-0.11_1 = SHA256 Checksum OK for jbig2dec-0.11.tar.xz. === Patching for jbig2dec-0.11_1 === Applying extra patch /usr/ports/graphics/jbig2dec/files/simpler-test-patch === Applying FreeBSD patches for jbig2dec-0.11_1 /usr/bin/sed -i.bak -E 's|SHA1_Final\( *([^,]+), *([^\)]+)\)|SHA1_Final(\2, \1)|' /usr/ports/graphics/jbig2dec/work/jbig2dec-0.11/jbig2dec.c /usr/ports/graphics/jbig2dec/work/jbig2dec-0.11/sha1.c === jbig2dec-0.11_1 depends on shared library: libpng15.so - not found ===Verifying for libpng15.so in /usr/ports/graphics/png === Found saved configuration for png-1.5.12 === Fetching all distfiles required by png-1.5.17 for building === Extracting for png-1.5.17 = SHA256 Checksum OK for libpng-1.5.17.tar.xz. = SHA256 Checksum OK for libpng-1.5.17-apng.patch.gz. /bin/cp /usr/ports/distfiles//libpng-1.5.17-apng.patch.gz /usr/ports/graphics/png/work/libpng-1.5.17/ /usr/bin/gzip -nf -9 -d /usr/ports/graphics/png/work/libpng-1.5.17/libpng-1.5.17-apng.patch.gz === Patching for png-1.5.17 === Applying extra patch /usr/ports/graphics/png/work/libpng-1.5.17/libpng-1.5.17-apng.patch === Applying FreeBSD patches for png-1.5.17 /usr/bin/sed -i.bak -e 's|RELEASE}.0|RELEASE}|' -e 's|LIBDIR}/pkgconfig|LIBDIR}data/pkgconfig|' /usr/ports/graphics/png/work/libpng-1.5.17/CMakeLists.txt === png-1.5.17 depends on file: /usr/local/bin/cmake - found === Configuring for png-1.5.17 === Performing in-source build /bin/mkdir -p /usr/ports/graphics/png/work/libpng-1.5.17 -- The C compiler identification is GNU 4.2.1 ... snip ... [100%] Built target pngvalid /usr/local/bin/cmake -E cmake_progress_start /usr/ports/graphics/png/work/libpng-1.5.17/CMakeFiles 0 Running tests... /usr/local/bin/ctest --force-new-ctest-process Test project /usr/ports/graphics/png/work/libpng-1.5.17 Start 1: pngtest 1/2 Test #1: pngtest .. Passed0.02 sec Start 2: pngvalid 2/2 Test #2: pngvalid . Passed 43.20 sec 100% tests passed, 0 tests failed out of 2 Total Test time (real) = 43.23 sec === Installing for png-1.5.17 === Generating temporary packing list === Checking if graphics/png already installed === png-1.5.17 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of graphics/png without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** [check-already-installed] Error code 1 Stop in /usr/ports/graphics/png. *** [lib-depends] Error code 1 Stop in /usr/ports/graphics/jbig2dec. ___ 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: [Bulk] FreeBSD upgrade woes (8.3 - 8.4)
Perhaps make buildkernel was compiled with -j 1, it's known to create a buggy kernel. Check your make configuration. Adding a -B, like make -B -j N buildkernel may work and is fast if -j is set to number or processors, but it's safer do a make -j 1 buildkernel, same for buildworld. I replaced the kernel with the one on the 8.4 memstick and it booted just fine. I then built and installed a kernel without using the j flag to test Eduardo's theory. It booted without problem. Maybe there's something to this -j 1 causing buggy kernels rumor. -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: [Bulk] FreeBSD upgrade woes (8.3 - 8.4)
On Fri, 19 Jul 2013, David Noel wrote: Perhaps make buildkernel was compiled with -j 1, it's known to create a buggy kernel. Check your make configuration. Adding a -B, like make -B -j N buildkernel may work and is fast if -j is set to number or processors, but it's safer do a make -j 1 buildkernel, same for buildworld. I replaced the kernel with the one on the 8.4 memstick and it booted just fine. I then built and installed a kernel without using the j flag to test Eduardo's theory. It booted without problem. Maybe there's something to this -j 1 causing buggy kernels rumor. It's possible. But again, I've been using -j 1 for years on a variety of processors, mostly Intel, without problems. That's with buildworld and kernel (which is buildkernel plus installkernel), but not with installworld. Are you using clang instead of gcc? That could be very different. ___ 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: [Bulk] FreeBSD upgrade woes (8.3 - 8.4)
It's possible. But again, I've been using -j 1 for years on a variety of processors, mostly Intel, without problems. That's with buildworld and kernel (which is buildkernel plus installkernel), but not with installworld. Are you using clang instead of gcc? That could be very different. These are Intel's too. I'm using the default compiler for 8.4. I believe that's gcc? ___ 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
Is pkgng supposed to upgrade a dependency of a locked package?
I am using pkgng 1.1.4_1 on RELENG_9 (r252725), operating on a local repo I maintain using poudriere 3.0.4. Recently, I wanted to upgrade all packages on a client except two whose update I want to defer for now as they potentially impact locally-developed applications. I figured I would use the pkgng lock functionality on those two packages (apache-solr and py27-Jinja2) to prevent them from being updated. I ran pkg upgrade on the client and, as expected, the locked packages weren't upgraded. However, I was surprised to see that packages upon which the locked packages depended were upgraded. Unless I'm misunderstanding something, the man page for pkg-lock states this should not happen: = The impact of locking a package is wider than simply preventing modifica- tions to the package itself. Any operation implying modification of the locked package will be blocked. This includes: [[...]] o Deletion, up- or downgrade of any package the locked package depends upon, either directly or as a consequence of installing or upgrading some third package. = In my case, the following dependencies of apache-solr were updated, even though apache-solr is locked: java-zoneinfo: 2013.c - 2013.d; libXi: 1.7.1_1,1 - 1.7.2,1; libXrender: 0.9.7_1 - 0.9.8; and openjdk: 7.21.11 - 7.25.15. In the case of the locked py27-Jinja2, these dependencies were updated: gettext: 0.18.1.1_1 - 0.18.3; and py27-MarkupSafe: 0.15 - 0.18. Dependency information in the two locked packages was updated to reflect these new, upgraded dependencies. Is this a bug, or am I misreading the man page? Cheers, Paul. ___ 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: Is pkgng supposed to upgrade a dependency of a locked package?
On 18/07/2013 13:42, Paul Mather wrote: I am using pkgng 1.1.4_1 on RELENG_9 (r252725), operating on a local repo I maintain using poudriere 3.0.4. Recently, I wanted to upgrade all packages on a client except two whose update I want to defer for now as they potentially impact locally-developed applications. I figured I would use the pkgng lock functionality on those two packages (apache-solr and py27-Jinja2) to prevent them from being updated. I ran pkg upgrade on the client and, as expected, the locked packages weren't upgraded. However, I was surprised to see that packages upon which the locked packages depended were upgraded. Unless I'm misunderstanding something, the man page for pkg-lock states this should not happen: = The impact of locking a package is wider than simply preventing modifica- tions to the package itself. Any operation implying modification of the locked package will be blocked. This includes: [[...]] o Deletion, up- or downgrade of any package the locked package depends upon, either directly or as a consequence of installing or upgrading some third package. = In my case, the following dependencies of apache-solr were updated, even though apache-solr is locked: java-zoneinfo: 2013.c - 2013.d; libXi: 1.7.1_1,1 - 1.7.2,1; libXrender: 0.9.7_1 - 0.9.8; and openjdk: 7.21.11 - 7.25.15. In the case of the locked py27-Jinja2, these dependencies were updated: gettext: 0.18.1.1_1 - 0.18.3; and py27-MarkupSafe: 0.15 - 0.18. Dependency information in the two locked packages was updated to reflect these new, upgraded dependencies. Is this a bug, or am I misreading the man page? That's a bug, definitely. The way the man page describes the effect of locking is what should happen -- nothing a locked package depends on should be modified by pkg without some extra input from the administrator to allow the change to happen. Cheers, Matthew ___ 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 upgrade woes (8.3 - 8.4)
I have 4 servers I'm upgrading from 8.3 to 8.4. Two of them went without a hitch, two of them blew up in my face. The only difference between the two is the ones that worked have a 2-disk ZFS mirror and the ones that didn't have a 4-disk ZFS striped mirror configuration (RAID10). They both use the GPT. After installworld installkernel they made it through boot, but right before the login prompt I'm getting a panic and stack dump. The backtrace looks something like this (roughly): 0 kdb_backtrace 1 panic 2 trap_fatal 3 trap_pfault 4 trap 5 calltrap 6 vdev_mirror_child_select 7 vdev_mirror_io_start 8 zio_vdev_io_start 9 zio_execute 10 arc_read 11 dbuf_read 12 dbuf_findbp 13 dbuf_hold_impl 14 dbuf_hold 15 dnode_hold_impl 16 dmu_buf_hold 17 zap_lockdir Does anyone have any idea what went wrong? Does anyone have any suggestions on how to get past this? Many thanks, -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: [Bulk] FreeBSD upgrade woes (8.3 - 8.4)
On Thu, Jul 11, 2013 at 11:04 AM, David Noel david.i.n...@gmail.com wrote: I have 4 servers I'm upgrading from 8.3 to 8.4. Two of them went without a hitch, two of them blew up in my face. The only difference between the two is the ones that worked have a 2-disk ZFS mirror and the ones that didn't have a 4-disk ZFS striped mirror configuration (RAID10). They both use the GPT. After installworld installkernel they made it through boot, but right before the login prompt I'm getting a panic and stack dump. The backtrace looks something like this (roughly): 0 kdb_backtrace 1 panic 2 trap_fatal 3 trap_pfault 4 trap 5 calltrap 6 vdev_mirror_child_select 7 vdev_mirror_io_start 8 zio_vdev_io_start 9 zio_execute 10 arc_read 11 dbuf_read 12 dbuf_findbp 13 dbuf_hold_impl 14 dbuf_hold 15 dnode_hold_impl 16 dmu_buf_hold 17 zap_lockdir Does anyone have any idea what went wrong? Does anyone have any suggestions on how to get past this? Many thanks, -David Hi David, You wrote you execute the commands make installworld make installkernel but the first command is wrong. You must execute first make buildworld. All the steps are explained in /usr/src/Makefile Regards, Alexandre ___ 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: [Bulk] FreeBSD upgrade woes (8.3 - 8.4)
On 7/11/13, Alexandre axel...@ymail.com wrote: On Thu, Jul 11, 2013 at 11:04 AM, David Noel david.i.n...@gmail.com wrote: I have 4 servers I'm upgrading from 8.3 to 8.4. Two of them went without a hitch, two of them blew up in my face. The only difference between the two is the ones that worked have a 2-disk ZFS mirror and the ones that didn't have a 4-disk ZFS striped mirror configuration (RAID10). They both use the GPT. After installworld installkernel they made it through boot, but right before the login prompt I'm getting a panic and stack dump. The backtrace looks something like this (roughly): 0 kdb_backtrace 1 panic 2 trap_fatal 3 trap_pfault 4 trap 5 calltrap 6 vdev_mirror_child_select 7 vdev_mirror_io_start 8 zio_vdev_io_start 9 zio_execute 10 arc_read 11 dbuf_read 12 dbuf_findbp 13 dbuf_hold_impl 14 dbuf_hold 15 dnode_hold_impl 16 dmu_buf_hold 17 zap_lockdir Does anyone have any idea what went wrong? Does anyone have any suggestions on how to get past this? Many thanks, -David Hi David, You wrote you execute the commands make installworld make installkernel but the first command is wrong. You must execute first make buildworld. All the steps are explained in /usr/src/Makefile Regards, Alexandre I didn't include the make buildworld or make buildkernel for the sake of brevity but yes, I executed them prior to installworld and installkernel. ___ 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: [Bulk] FreeBSD upgrade woes (8.3 - 8.4)
On Thu, 11 Jul 2013 04:40:38 -0500 David Noel david.i.n...@gmail.com wrote: I didn't include the make buildworld or make buildkernel for the sake of brevity but yes, I executed them prior to installworld and installkernel. Perhaps make buildkernel was compiled with -j 1, it's known to create a buggy kernel. Check your make configuration. Adding a -B, like make -B -j N buildkernel may work and is fast if -j is set to number or processors, but it's safer do a make -j 1 buildkernel, same for buildworld. HTH --- --- 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: [Bulk] FreeBSD upgrade woes (8.3 - 8.4)
Ah. That very well might be it. I did call buildkernel with j 1. I'll boot an 8.4 memstick and replace the kernel. Thanks, -David On 7/11/13, Eduardo Morras emorr...@yahoo.es wrote: On Thu, 11 Jul 2013 04:40:38 -0500 David Noel david.i.n...@gmail.com wrote: I didn't include the make buildworld or make buildkernel for the sake of brevity but yes, I executed them prior to installworld and installkernel. Perhaps make buildkernel was compiled with -j 1, it's known to create a buggy kernel. Check your make configuration. Adding a -B, like make -B -j N buildkernel may work and is fast if -j is set to number or processors, but it's safer do a make -j 1 buildkernel, same for buildworld. HTH --- --- 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: [Bulk] FreeBSD upgrade woes (8.3 - 8.4)
On Thu, 11 Jul 2013 05:00:39 -0500, Eduardo Morras emorr...@yahoo.es wrote: Perhaps make buildkernel was compiled with -j 1, it's known to create a buggy kernel. This is not true to my knowledge. If buildkernel produced bad kernels with -j1 we'd not allow you to do that without jumping through hoops. ___ 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: [Bulk] FreeBSD upgrade woes (8.3 - 8.4)
On Thu, 11 Jul 2013, Eduardo Morras wrote: On Thu, 11 Jul 2013 04:40:38 -0500 David Noel david.i.n...@gmail.com wrote: I didn't include the make buildworld or make buildkernel for the sake of brevity but yes, I executed them prior to installworld and installkernel. Perhaps make buildkernel was compiled with -j 1, it's known to create a buggy kernel. Check your make configuration. Adding a -B, like make -B -j N buildkernel may work and is fast if -j is set to number or processors, but it's safer do a make -j 1 buildkernel, same for buildworld. Is this version-specific? I've been using -j4 or -j8 for years for buildworld and kernel (buildkernel + installkernel) on FreeBSD 8 and 9 with no problems. Probably on FreeBSD 7 also, but I don't recall. installworld is a different matter, always do that with a single job. ___ 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: [Bulk] FreeBSD upgrade woes (8.3 - 8.4)
On 7/11/13, Mark Felder f...@feld.me wrote: On Thu, 11 Jul 2013 05:00:39 -0500, Eduardo Morras emorr...@yahoo.es wrote: Perhaps make buildkernel was compiled with -j 1, it's known to create a buggy kernel. This is not true to my knowledge. If buildkernel produced bad kernels with -j1 we'd not allow you to do that without jumping through hoops. If this is the case replacing the kernel should have no effect. But what then? Any thoughts? ___ 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: [Bulk] FreeBSD upgrade woes (8.3 - 8.4)
On Thu, Jul 11, 2013, at 14:37, David Noel wrote: If this is the case replacing the kernel should have no effect. But what then? Any thoughts? I'd contact freebsd-fs@ and see what they have to say ___ 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 can't mount /usr after 9.1-release upgrade
a freebsd box doesn't boot normally since upgrading from 9.1-rc3 to 9.1-release. it boots to the point that /usr is mounted, then errors mount: /usr: unknown special file or file system if i boot to single user, zfs mount -a manually, then it comes up fine. what function key do i gotta press to make that not happen again? 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: zfs can't mount /usr after 9.1-release upgrade
On 7/10/13 1:50 PM, Michael Sierchio ku...@tenebras.com wrote: On Wed, Jul 10, 2013 at 12:34 PM, Tom Worster f...@thefsb.org wrote: # mount -p /etc/fstab thanks for answering, michael. i have now spotted the problem. the zfs_enable line in rc.conf was fubar. i must have done some bad vi on it around the time i upgraded the base 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: upgrade qjail
Guys! I have a similar problem. But from your answer I don't
understand, is it needed to create all jails from scratch?!! Or it
possible recreate existed jails with qjail-3.0?
Tell me please how to do that procedure without reinstalling all jails
from scratch.
09.06.2013, 07:55, Fbsd8 fb...@a1poweruser.com:
Masayoshi Fujimoto wrote:
Hi.
Could you tell me how to upgrade qjail-1.7 to qjail-3.0 ?
I can not start www. So I have to use qjail-1.7 now. _
root@freebsd:/root # pkg_info | grep qjail
qjail-1.7 Utility to quickly deploy and manage jails
root@freebsd:/root # jls
JID IP Address Hostname Path
1 192.168.0.20 www /usr/jails/www
root@freebsd:/root # portmaster qjail
root@freebsd:/root # rehash
root@freebsd:/root # pkg_info | grep qjail
qjail-3.0 Utility to quickly deploy and manage jails
root@freebsd:/root # reboot
I got the following message.
jail: qjail: path : not an absolute pathname
Error: /usr/sbin/jail failed to start jail www.
because of errors in jail.conf file.
root@freebsd:/root # cat /etc/jail.conf
qjail {
host.hostname = qjail;
path = ;
mount.fstab = ;
exec.start = /bin/sh /etc/rc;
exec.stop = /bin/sh /etc/rc.shutdown;
exec.consolelog = /var/log/qjail.qjail.console.log;
devfs_ruleset = 4;
allow.mount.devfs;
}
So I edited /etc/jail.conf :
www {
host.hostname = www;
path = /usr/jails/www;
mount.fstab = ;
exec.start = /bin/sh /etc/rc;
exec.stop = /bin/sh /etc/rc.shutdown;
exec.consolelog = /var/log/qjail.qjail.console.log;
devfs_ruleset = 4;
allow.mount.devfs;
ip4.addr = 192.168.0.20;
interface = alc0;
}
root@freebsd:/root # /usr/local/etc/rc.d/qjail.bootime restart
jail: qjail: path : not an absolute pathname
Error: /usr/sbin/jail failed to start jail www.
because of errors in jail.conf file.
I got same massage.
My /etc/jail.conf has been changed default one.
qjail-1.7 is way out of date.
you have to delete all your 1.7 jails
then do pkg_delete qjail-1.7
then
portsnap fetch
portsnap extract
cd /usr/ports/sysutils/qjail
ee Makefile and make sure it says qjail-3.0
make install clean
man qjail
recreate your jails
___
[1]freebsd-questions@freebsd.org mailing list
[2]http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[3]freebsd-questions-unsubscr...@freebsd.org
References
1. mailto:freebsd-questions@freebsd.org
2. http://lists.freebsd.org/mailman/listinfo/freebsd-questions
3. mailto: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: XDM cannot start desktop after Xorg upgrade
2013-06-09 07:46, Leslie Jensen skrev: 2013-06-08 17:28, Polytropon skrev: On Sat, 08 Jun 2013 12:20:56 +0200, Leslie Jensen wrote: I've been using XDM as login manager for years. Since the latest Xorg upgrade, XDM cannot start XFCE4 as it used to. Strange that this happens after an upgrade. What initalization mechanism do you use for your X session? Do you use the chained approach, i. e., ~/.xsession containing #!/bin/csh source ~/.cshrc exec ~/.xinitrc and all your session startup stuff in ~/xinitrc? (I'm using this approach for many years with XDM successfully.) Disabling XDM and starting X manually works. In this case, ~/.xinitrc will be processed. XDM does use ~/.xsession instead (same content can be used). This seems to indicate that the upgrade did not affect the programs called. I've done like this lrwxr-xr-x 1 user user 9 31 Dec 17:53 .xinitrc@ - .xsession These are the contents of .xsession # LANG=sv_SE.ISO8859-1; export LANG /usr/local/bin/startxfce4 ___ 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 I've disabled XDM for now starting X manually. When I exit X I see this on the console: Thanks /Leslie onStopListening called for active ServerSocket... (xfce4-session:2440): GLib-WARNING **: GError set over the top of a previous GEr ror or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Failed to connect to socket /var/run/dbus/sys tem_bus_socket: Filen eller katalogen finns ej (xfce4-session:2440): GLib-WARNING **: GError set over the top of a previous GEr ror or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Failed to connect to socket /var/run/dbus/sys tem_bus_socket: Filen eller katalogen finns ej xfce4-session: Querying suspend failed: Failed to connect to socket /var/run/dbu s/system_bus_socket: Filen eller katalogen finns ej xinit: connection to X server lost waiting for X server to shut down xfsettingsd: Fatal IO error 35 (Resursen är t illfälligt otillgänglig) on X server :0.0. .failed to unset mtrr: No such file or directory ___ 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
XDM cannot start desktop after Xorg upgrade
I've been using XDM as login manager for years. Since the latest Xorg upgrade, XDM cannot start XFCE4 as it used to. What happens is that after I've given my password and hit enter, the screen goes black and after a while it returns to the XDM log in dialogue. I've attached the users .xsession-errors and the system xdm.log Disabling XDM and starting X manually works. Of and on logging in via XDM works but there's no pattern to when it does and does not. Thanks /Leslie xdm info (pid 2391): Starting xdm info (pid 2391): Starting X server on :0 X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 9.1-RELEASE amd64 Current Operating System: FreeBSD bljbsd01.no-ip.org 9.1-RELEASE-p3 FreeBSD 9.1-RELEASE-p3 #0: Mon Apr 29 18:27:25 UTC 2013 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 Build Date: 29 January 2013 05:30:35PM Current version of pixman: 0.28.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sat Jun 8 11:50:02 2013 (==) Using config file: /etc/X11/xorg.conf failed to set mtrr: Invalid argument The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server xdm info (pid 2396): sourcing /usr/local/lib/X11/xdm/Xsetup_0 must specify a background color xdm info (pid 2396): sourcing /usr/local/lib/X11/xdm/GiveConsole xdm info (pid 2408): executing session /usr/local/lib/X11/xdm/Xsession xdm info (pid 2396): sourcing /usr/local/lib/X11/xdm/TakeConsole xdm info (pid 2391): Starting X server on :0 The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server xdm info (pid 2424): sourcing /usr/local/lib/X11/xdm/Xsetup_0 must specify a background color xdm info (pid 2424): sourcing /usr/local/lib/X11/xdm/GiveConsole xdm info (pid 2438): executing session /usr/local/lib/X11/xdm/Xsession xdm info (pid 2424): sourcing /usr/local/lib/X11/xdm/TakeConsole xdm info (pid 2391): Starting X server on :0 The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server xdm info (pid 2454): sourcing /usr/local/lib/X11/xdm/Xsetup_0 must specify a background color xdm info (pid 2454): sourcing /usr/local/lib/X11/xdm/GiveConsole xdm info (pid 2468): executing session /usr/local/lib/X11/xdm/Xsession xdm info (pid 2454): sourcing /usr/local/lib/X11/xdm/TakeConsole xdm info (pid 2391): Starting X server on :0 The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server xdm info (pid 2484): sourcing /usr/local/lib/X11/xdm/Xsetup_0 must specify a background color .xsession-errors Description: Binary data ___ 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: XDM cannot start desktop after Xorg upgrade
On Sat, 08 Jun 2013 12:20:56 +0200, Leslie Jensen wrote: I've been using XDM as login manager for years. Since the latest Xorg upgrade, XDM cannot start XFCE4 as it used to. Strange that this happens after an upgrade. What initalization mechanism do you use for your X session? Do you use the chained approach, i. e., ~/.xsession containing #!/bin/csh source ~/.cshrc exec ~/.xinitrc and all your session startup stuff in ~/xinitrc? (I'm using this approach for many years with XDM successfully.) Disabling XDM and starting X manually works. In this case, ~/.xinitrc will be processed. XDM does use ~/.xsession instead (same content can be used). This seems to indicate that the upgrade did not affect the programs called. -- 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
upgrade qjail
Hi.
Could you tell me how to upgrade qjail-1.7 to qjail-3.0 ?
I can not start www. So I have to use qjail-1.7 now. _
root@freebsd:/root # pkg_info | grep qjail
qjail-1.7 Utility to quickly deploy and manage jails
root@freebsd:/root # jls
JID IP Address Hostname Path
1 192.168.0.20www /usr/jails/www
root@freebsd:/root # portmaster qjail
root@freebsd:/root # rehash
root@freebsd:/root # pkg_info | grep qjail
qjail-3.0 Utility to quickly deploy and manage jails
root@freebsd:/root # reboot
I got the following message.
jail: qjail: path : not an absolute pathname
Error: /usr/sbin/jail failed to start jail www.
because of errors in jail.conf file.
root@freebsd:/root # cat /etc/jail.conf
qjail {
host.hostname = qjail;
path= ;
mount.fstab = ;
exec.start = /bin/sh /etc/rc;
exec.stop = /bin/sh /etc/rc.shutdown;
exec.consolelog = /var/log/qjail.qjail.console.log;
devfs_ruleset = 4;
allow.mount.devfs;
}
So I edited /etc/jail.conf :
www {
host.hostname = www;
path= /usr/jails/www;
mount.fstab = ;
exec.start = /bin/sh /etc/rc;
exec.stop = /bin/sh /etc/rc.shutdown;
exec.consolelog = /var/log/qjail.qjail.console.log;
devfs_ruleset = 4;
allow.mount.devfs;
ip4.addr = 192.168.0.20;
interface = alc0;
}
root@freebsd:/root # /usr/local/etc/rc.d/qjail.bootime restart
jail: qjail: path : not an absolute pathname
Error: /usr/sbin/jail failed to start jail www.
because of errors in jail.conf file.
I got same massage.
My /etc/jail.conf has been changed default one.
___
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: upgrade qjail
Masayoshi Fujimoto wrote:
Hi.
Could you tell me how to upgrade qjail-1.7 to qjail-3.0 ?
I can not start www. So I have to use qjail-1.7 now. _
root@freebsd:/root # pkg_info | grep qjail
qjail-1.7 Utility to quickly deploy and manage jails
root@freebsd:/root # jls
JID IP Address Hostname Path
1 192.168.0.20www /usr/jails/www
root@freebsd:/root # portmaster qjail
root@freebsd:/root # rehash
root@freebsd:/root # pkg_info | grep qjail
qjail-3.0 Utility to quickly deploy and manage jails
root@freebsd:/root # reboot
I got the following message.
jail: qjail: path : not an absolute pathname
Error: /usr/sbin/jail failed to start jail www.
because of errors in jail.conf file.
root@freebsd:/root # cat /etc/jail.conf
qjail {
host.hostname = qjail;
path= ;
mount.fstab = ;
exec.start = /bin/sh /etc/rc;
exec.stop = /bin/sh /etc/rc.shutdown;
exec.consolelog = /var/log/qjail.qjail.console.log;
devfs_ruleset = 4;
allow.mount.devfs;
}
So I edited /etc/jail.conf :
www {
host.hostname = www;
path= /usr/jails/www;
mount.fstab = ;
exec.start = /bin/sh /etc/rc;
exec.stop = /bin/sh /etc/rc.shutdown;
exec.consolelog = /var/log/qjail.qjail.console.log;
devfs_ruleset = 4;
allow.mount.devfs;
ip4.addr = 192.168.0.20;
interface = alc0;
}
root@freebsd:/root # /usr/local/etc/rc.d/qjail.bootime restart
jail: qjail: path : not an absolute pathname
Error: /usr/sbin/jail failed to start jail www.
because of errors in jail.conf file.
I got same massage.
My /etc/jail.conf has been changed default one.
qjail-1.7 is way out of date.
you have to delete all your 1.7 jails
then do pkg_delete qjail-1.7
then
portsnap fetch
portsnap extract
cd /usr/ports/sysutils/qjail
ee Makefile and make sure it says qjail-3.0
make install clean
man qjail
recreate your jails
___
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: XDM cannot start desktop after Xorg upgrade
2013-06-08 17:28, Polytropon skrev: On Sat, 08 Jun 2013 12:20:56 +0200, Leslie Jensen wrote: I've been using XDM as login manager for years. Since the latest Xorg upgrade, XDM cannot start XFCE4 as it used to. Strange that this happens after an upgrade. What initalization mechanism do you use for your X session? Do you use the chained approach, i. e., ~/.xsession containing #!/bin/csh source ~/.cshrc exec ~/.xinitrc and all your session startup stuff in ~/xinitrc? (I'm using this approach for many years with XDM successfully.) Disabling XDM and starting X manually works. In this case, ~/.xinitrc will be processed. XDM does use ~/.xsession instead (same content can be used). This seems to indicate that the upgrade did not affect the programs called. I've done like this lrwxr-xr-x 1 user user 9 31 Dec 17:53 .xinitrc@ - .xsession These are the contents of .xsession # LANG=sv_SE.ISO8859-1; export LANG /usr/local/bin/startxfce4 ___ 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 with port upgrade consistency using portsnap
Hello, I am using portsnap to update my port collection on FreeBSD 9.1 the first time I ran it a few weeks ago I did| || |||portsnap fetch| || |and then portsnap exctract then I did a crontab script to update ports every night 0 3 * * * /usr/sbin/portsnap -I cron update pkg_version -vIL= Now after a few weeks pkg_version is reporting me a lot of ports which needs updating dbus-glib-0.100.1 needs updating (index has 0.100.2) desktop-file-utils-0.18needs updating (index has 0.21) dokuwiki-20121013 needs updating (index has 20130510) freetype2-2.4.11 needs updating (index has 2.4.12_1) intltool-0.41.1needs updating (index has 0.50.2) p5-HTML-Parser-3.70needs updating (index has 3.71) p5-LWP-Protocol-https-6.03 needs updating (index has 6.04) php5-5.4.14needs updating (index has 5.4.15) php5-dom-5.4.14needs updating (index has 5.4.15) php5-exif-5.4.14 needs updating (index has 5.4.15) php5-fileinfo-5.4.14 needs updating (index has 5.4.15) php5-gd-5.4.14 needs updating (index has 5.4.15) php5-iconv-5.4.14 needs updating (index has 5.4.15) php5-json-5.4.14 needs updating (index has 5.4.15) php5-ldap-5.4.14 needs updating (index has 5.4.15) php5-mbstring-5.4.14 needs updating (index has 5.4.15) php5-mcrypt-5.4.14 needs updating (index has 5.4.15) php5-mysql-5.4.14 needs updating (index has 5.4.15) php5-openssl-5.4.14needs updating (index has 5.4.15) php5-session-5.4.14needs updating (index has 5.4.15) php5-xml-5.4.14needs updating (index has 5.4.15) php5-zlib-5.4.14 needs updating (index has 5.4.15) py27-sqlite3-2.7.3_3 needs updating (index has 2.7.5_3) python27-2.7.3_6 needs updating (index has 2.7.5) roundcube-0.8.6,1 needs updating (index has 0.9.0,1) sendmail+tls+sasl2+db42-8.14.7 needs updating (index has 8.14.7_1) sendmail+tls+sasl2-8.14.7 needs updating (index has 8.14.7_1) shared-mime-info-1.0_2 needs updating (index has 1.1) wget-1.14 needs updating (index has 1.14_2) if I use portmaster to upgrade my ports collection it is telling me all packages are up to date... so there is something not working for example py27-sqlite3-2.7.3_3 needs updating (index has 2.7.5_3) but if I go into /usr/ports/lang/python27 and I look in Makefile, it reports PORTNAME= python27 PORTVERSION=2.7.3 PORTREVISION= 6 while it should be PORTNAME= python27 PORTVERSION=2.7.5 PORTREVISION= 3 Looks like the ports database is updated but the ports tree it is not... anyone could give me a hint on why this may happen ? I actually am unable to update my ports collection. thank you very much Rick || ___ 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 with port upgrade consistency using portsnap
On 19/05/2013 15:49, fddi wrote: Hello, I am using portsnap to update my port collection on FreeBSD 9.1 the first time I ran it a few weeks ago I did| || |||portsnap fetch| || |and then portsnap exctract then I did a crontab script to update ports every night 0 3 * * * /usr/sbin/portsnap -I cron update pkg_version -vIL= Now after a few weeks pkg_version is reporting me a lot of ports which needs updating py27-sqlite3-2.7.3_3 needs updating (index has 2.7.5_3) python27-2.7.3_6 needs updating (index has 2.7.5) That is correct. You are confusing two different things. portsnap updates the ports tree, which contains the files needed to compile the programs you install. It is only information about the programs and version with instructions to compile. portsnap does not install the programs for you. pkg_version is telling you that the ports tree has information on new versions available of programs you have installed. if I use portmaster to upgrade my ports collection it is telling me all packages are up to date... so there is something not working portmaster installs the binary programs for you. Look into this later if the later info doesn't fix it. for example py27-sqlite3-2.7.3_3 needs updating (index has 2.7.5_3) This is a python library to add access to sqlite db files. Don't confuse it with python itself. The Makefile for this will be in databases/py-sqlite3 but if I go into /usr/ports/lang/python27 and I look in Makefile, it reports PORTNAME= python27 PORTVERSION=2.7.3 PORTREVISION= 6 While this isn't the Makefile for py-sqlite3, pkg_version is telling you it knows about python 2.7.5 so this is not the Makefile that pkg_version is looking at, but it would appear to be the file that portmaster is looking at. It looks like you have two copies of the ports tree. Check /etc/portsnap.conf you may have an odd setting for PORTSDIR. Another possibility is you have an odd PORTSDIR defined in your environment, what does echo $PORTSDIR show? You may also have bad settings in cron - run portsnap fetch update manually and see if python27/Makefile changes Start by sorting out why pkg_version and portmaster are using different files before you progress further. ___ 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 with port upgrade consistency using portsnap
hello, here is from portsnap.conf # PORTSDIR=/usr/ports so it is /usr/ports instead in my environment $PORTSDIR is undefined. Here is /usr/ports/lang/python27/Makefile PORTNAME= python27 PORTVERSION=2.7.3 PORTREVISION= 6 after I did portsnap fetch update everythign looks up to date so ther is something wrong in my crontab 0 3 * * * /usr/sbin/portsnap -I cron update pkg_version -vIL= the problem was in portsnap -I which updates only thr index files... thanks for helping me to identify the issue cheers Rick On 5/19/13 11:04 AM, Shane Ambler wrote: On 19/05/2013 15:49, fddi wrote: Hello, I am using portsnap to update my port collection on FreeBSD 9.1 the first time I ran it a few weeks ago I did| || |||portsnap fetch| || |and then portsnap exctract then I did a crontab script to update ports every night 0 3 * * * /usr/sbin/portsnap -I cron update pkg_version -vIL= Now after a few weeks pkg_version is reporting me a lot of ports which needs updating py27-sqlite3-2.7.3_3 needs updating (index has 2.7.5_3) python27-2.7.3_6 needs updating (index has 2.7.5) That is correct. You are confusing two different things. portsnap updates the ports tree, which contains the files needed to compile the programs you install. It is only information about the programs and version with instructions to compile. portsnap does not install the programs for you. pkg_version is telling you that the ports tree has information on new versions available of programs you have installed. if I use portmaster to upgrade my ports collection it is telling me all packages are up to date... so there is something not working portmaster installs the binary programs for you. Look into this later if the later info doesn't fix it. for example py27-sqlite3-2.7.3_3 needs updating (index has 2.7.5_3) This is a python library to add access to sqlite db files. Don't confuse it with python itself. The Makefile for this will be in databases/py-sqlite3 but if I go into /usr/ports/lang/python27 and I look in Makefile, it reports PORTNAME= python27 PORTVERSION=2.7.3 PORTREVISION= 6 While this isn't the Makefile for py-sqlite3, pkg_version is telling you it knows about python 2.7.5 so this is not the Makefile that pkg_version is looking at, but it would appear to be the file that portmaster is looking at. It looks like you have two copies of the ports tree. Check /etc/portsnap.conf you may have an odd setting for PORTSDIR. Another possibility is you have an odd PORTSDIR defined in your environment, what does echo $PORTSDIR show? You may also have bad settings in cron - run portsnap fetch update manually and see if python27/Makefile changes Start by sorting out why pkg_version and portmaster are using different files before you progress further. ___ 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: problems with port upgrade consistency using portsnap
fddi wrote: [snip] so ther is something wrong in my crontab 0 3 * * * /usr/sbin/portsnap -I cron update pkg_version -vIL= See man portsnap, section TIPS - it shows example of correct way: 0 3 * * * root /usr/sbin/portsnap cron The TIPS section contains more details. [snip] -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
upgrade packages
Hi all! I come from linux os and I read a lot documentations about freebsd. I've a doubt: when I've some packages installed and I need upgrade it, I need to recompile those packages or there's another (fast) way to do this? thanks! Pol ___ 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: upgrade packages
On Thu, 25 Apr 2013 15:05:25 +0200, Pol Hallen wrote: Hi all! I come from linux os and I read a lot documentations about freebsd. I've a doubt: when I've some packages installed and I need upgrade it, I need to recompile those packages or there's another (fast) way to do this? With the new pkgng (the replacement for the traditional pkg infrastructure that handles precompiled binary packages) this won't be a problem, as long as the default compile options and settings are fine for you. If not, today's PCs have multiple plenticore CPUs with tons of RAM and endless hard disks, so running portmaster -a won't be a big deal. :-) On FreeBSD, it's _your_ choice. It's already in The FreeBSD Handbook: http://www.freebsd.org/doc/en/books/handbook/pkgng-intro.html Soon, it will be the system's default. -- 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
perl-after-upgrade mistakenly thinks nothing needs to be done
Hi all, I'm running 8.3-RELEASE and thought I'd update Perl from 5.12 to 5.16. Silly me. I updated my ports snapshot, and as per UPDATING, ran portmaster -o lang/perl5.16 lang/perl5.12 This went OK, so I then ran perl-after-upgrade, with and without -f. It scans the packages and finds everything it should, but insists nothing needs to be done, saying 0 moved, 0 modified, 0 adjusted for every one of them. At the end it says Fixed 0 packages (0 files moved, 0 files modified). Well of course this isn't right; all my modules are still sitting in the 5.12.4 directory and are not getting moved over to the 5.16.2 one. This naturally breaks everything depending on those modules. What's going wrong? Sorry if this is a novice question. Please let me know what I need to check. Thanks, 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: perl-after-upgrade mistakenly thinks nothing needs to be done
Thanks for the replies; I really appreciate it. Alexandre wrote: Have you followed steps described in perl-after-upgrade man page? $ man perl-after-upgrade Yes, except for the last step (deleting old CONTENTS backups), since the previous steps didn't seem to do what they should. As I said, perl-after-upgrade thinks there's nothing to do. It doesn't report any packages it can't handle. It handles them, but for some reason determines that they are OK, despite the fact that the modules are all still sitting in the old installation. Anton Shterenlikht wrote: Have you done portmaster 5-? If not, do it. I hadn't done that. (portmaster 5- doesn't work, but portmaster p5- does.) UPDATING makes mention of this, but I didn't understand that it was saying it was a required step. Specifically, this is what it says: - 20120630: AFFECTS: users of lang/perl* AUTHOR: s...@freebsd.org lang/perl5.16 is out. If you want to switch to it from, for example lang/perl5.12, that is: Portupgrade users: 0) Fix pkgdb.db (for safety): pkgdb -Ff 1) Reinstall new version of Perl (5.16): env DISABLE_CONFLICTS=1 portupgrade -o lang/perl5.16 -f perl-5.12.\* 2) Reinstall everything that depends on Perl: portupgrade -fr perl Portmaster users: portmaster -o lang/perl5.16 lang/perl5.12 Conservative: portmaster p5- Comprehensive (but perhaps overkill): portmaster -r perl- Note: If the perl- glob matches more than one port you will need to specify the name of the Perl directory in /var/db/pkg explicitly. The default version for Perl has also been changed from 5.12 to 5.14. - Because of the way the portupgrade section is numbered, I thought the portmaster section was giving me 3 options: regular, conservative, comprehensive -- not two steps (1. portmaster -o, then 2. choose either the conservative or comprehensive option). ...partly my reading comprehension failure, I guess. It makes no mention of perl-after-upgrade, though. My understanding is that perl-after-upgrade looks at what perl-dependent packages are installed. As I can see by its output, this includes not just the application packages like SpamAssassin and mrtg, but their requisite Perl module packages as well, like HTML::Parser. Then, as these packages are found, perl-after-upgrade moves things from the old Perl installation over to the new, and does some other cleanup. Maybe that's a flawed assumption, because it seems rather weird to me that before running perl-after-upgrade, I'm expected to *first* to do a *full upgrade or reinstall* of the modules. Isn't that exactly what we're trying to avoid by running perl-after-upgrade? Nothing in the perl-after-upgrade man page suggests this is necessary; in fact, the intro implies the opposite. After this is done, how much have you got left under 5.12.4? Not much of anything, just a man page, a few mrtg .pm files... Naturally, running perl-after-upgrade at this point yields the same results as before (0 moved, 0 modified, 0 adjusted for everything). But this time, that's the expected output, I believe, given that I just reinstalled everything. I guess I'm just completely confused about what perl-after-upgrade was actually supposed to do, so it's difficult to suggest documentation updates. At the very least, though, maybe change UPDATING to clarify that the portmaster steps are a sequence, and mention perl-after-upgrade. ___ 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
pkgng: ignoring some papckaes in 'pkg upgrade'
Hello, is possible to ignore some packages with the 'pkg upgrade' command ? In particular I don't want the upgrade of the 'conky' package, because it is compiled with a non-standard options. Thanks Maurizio ___ 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: Upgrade devel/py-setuptools
On 27/03/2013 17:43, Volodymyr Kostyrko wrote: 2013-03-27 18:37, Loic Capdeville wrote: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) Looks like py-distribute is not installed at all. what was the outcome of portupgrade -fo devel/py-distribute devel/py-setuptools? Can you try running that again? It hasn't printed anything since the first time I tried to run it... and still print nothing. So here is a main problem. If it prints nothing it doesn't work. Do you have portupgrade or portmaster installed? Did it yield at least one line? Some errors? If it doesn't that's surely a sign that something is going wrong. I use portupgrade regularly to upgrade my ports, and usually everything goes right. If fails only with that particular operation (or these portupgrade options) Do I have to install devel/py-distribute separately, or should the portupgrade -fo command do everything itself (uninstall py-setuptools and install py-distribute) ? This command should forcefully deintsall second package and replace it with first one. I'm not using portupgrade, I switched to portmaster long time ago so I can't help you with it. If you want to make the switch by hand I think you should: pkg_delete -f py27-setuptools-0.6c11_3 # now write down the whole list of dependent packages cd /usr/ports/devel/py-distribute ; make install clean portupgrade -f ..list of packages that require setuptools.. If finally did it by hand. Note: upgrading packages that require setuptools isn't necessary, since py-distribute is backward compatible with py-setuptools. Thanks for your help. Loic ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Upgrade devel/py-setuptools
Hi ! I'm trying to update devel/py-setuptools which has been replaced by devel/py-distribute. As mentioned in /usr/ports/UPDATING I did portupgrade -fo devel/py-distribute devel/py-setuptools since I'm using ports, but nothing happens. Output of pkg_version -vIL= : py27-setuptools-0.6c11_3 succeeds index (index has 0.6.35) I already tried to fix the package registry using pkgdb -F. I've been trying to fix this for days, but still can't find a solution. Any idea ? Thanks. Loic ___ 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: Upgrade devel/py-setuptools
On Wed, 27 Mar 2013 13:22:19 +0100 Loic Capdeville articulated: I'm trying to update devel/py-setuptools which has been replaced by devel/py-distribute. As mentioned in /usr/ports/UPDATING I did portupgrade -fo devel/py-distribute devel/py-setuptools since I'm using ports, but nothing happens. Output of pkg_version -vIL= : py27-setuptools-0.6c11_3 succeeds index (index has 0.6.35) I already tried to fix the package registry using pkgdb -F. I've been trying to fix this for days, but still can't find a solution. I have the same problem. However, since everything is apparently working I just chose to ignore it. It probably should get corrected though. -- 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: Upgrade devel/py-setuptools
2013-03-27 14:22, Loic Capdeville wrote: Hi ! I'm trying to update devel/py-setuptools which has been replaced by devel/py-distribute. As mentioned in /usr/ports/UPDATING I did portupgrade -fo devel/py-distribute devel/py-setuptools since I'm using ports, but nothing happens. Output of pkg_version -vIL= : py27-setuptools-0.6c11_3 succeeds index (index has 0.6.35) I already tried to fix the package registry using pkgdb -F. I've been trying to fix this for days, but still can't find a solution. Any idea ? Can you post contents of /usr/local/lib/python2.7/site-packages/easy-install.pth* files? -- Sphinx of black quartz, judge my vow. ___ 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: Upgrade devel/py-setuptools
On 27/03/2013 13:50, Volodymyr Kostyrko wrote: 2013-03-27 14:22, Loic Capdeville wrote: Hi ! I'm trying to update devel/py-setuptools which has been replaced by devel/py-distribute. As mentioned in /usr/ports/UPDATING I did portupgrade -fo devel/py-distribute devel/py-setuptools since I'm using ports, but nothing happens. Output of pkg_version -vIL= : py27-setuptools-0.6c11_3 succeeds index (index has 0.6.35) I already tried to fix the package registry using pkgdb -F. I've been trying to fix this for days, but still can't find a solution. Any idea ? Can you post contents of /usr/local/lib/python2.7/site-packages/easy-install.pth* files? Thanks for your quick response. Here is what you requested: -rw-r--r-- 1 root wheel 395 Mar 13 04:50 /usr/local/lib/python2.7/site-packages/easy-install.pth -rw-r--r-- 1 root wheel 215 Dec 30 15:04 /usr/local/lib/python2.7/site-packages/easy-install.pth.dist ___ 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: Upgrade devel/py-setuptools
On 27/03/2013 14:00, Loic Capdeville wrote: On 27/03/2013 13:50, Volodymyr Kostyrko wrote: 2013-03-27 14:22, Loic Capdeville wrote: Hi ! I'm trying to update devel/py-setuptools which has been replaced by devel/py-distribute. As mentioned in /usr/ports/UPDATING I did portupgrade -fo devel/py-distribute devel/py-setuptools since I'm using ports, but nothing happens. Output of pkg_version -vIL= : py27-setuptools-0.6c11_3 succeeds index (index has 0.6.35) I already tried to fix the package registry using pkgdb -F. I've been trying to fix this for days, but still can't find a solution. Any idea ? Can you post contents of /usr/local/lib/python2.7/site-packages/easy-install.pth* files? Thanks for your quick response. Here is what you requested: -rw-r--r-- 1 root wheel 395 Mar 13 04:50 /usr/local/lib/python2.7/site-packages/easy-install.pth -rw-r--r-- 1 root wheel 215 Dec 30 15:04 /usr/local/lib/python2.7/site-packages/easy-install.pth.dist ___ 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 ... and the files content: /usr/local/lib/python2.7/site-packages/easy-install.pth: import sys; sys.__plen = len(sys.path) ./setuptools-0.6c11-py2.7.egg ./Pygments-1.5-py2.7.egg ./Babel-0.9.6-py2.7.egg ./MarkupSafe-0.15-py2.7-freebsd-9.0-RELEASE-amd64.egg ./Jinja2-2.6-py2.7.egg ./Sphinx-1.1.3-py2.7.egg ./virtualenv-1.9.1-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) /usr/local/lib/python2.7/site-packages/easy-install.pth.dist: import sys; sys.__plen = len(sys.path) ./setuptools-0.6c11-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) ___ 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: Upgrade devel/py-setuptools
2013-03-27 15:06, Loic Capdeville wrote: /usr/local/lib/python2.7/site-packages/easy-install.pth: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg ../Pygments-1.5-py2.7.egg ../Babel-0.9.6-py2.7.egg ../MarkupSafe-0.15-py2.7-freebsd-9.0-RELEASE-amd64.egg ../Jinja2-2.6-py2.7.egg ../Sphinx-1.1.3-py2.7.egg ../virtualenv-1.9.1-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) /usr/local/lib/python2.7/site-packages/easy-install.pth.dist: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) Looks like py-distribute is not installed at all. what was the outcome of portupgrade -fo devel/py-distribute devel/py-setuptools? Can you try running that again? -- Sphinx of black quartz, judge my vow. ___ 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: Upgrade devel/py-setuptools
On 27/03/2013 14:27, Volodymyr Kostyrko wrote: 2013-03-27 15:06, Loic Capdeville wrote: /usr/local/lib/python2.7/site-packages/easy-install.pth: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg ../Pygments-1.5-py2.7.egg ../Babel-0.9.6-py2.7.egg ../MarkupSafe-0.15-py2.7-freebsd-9.0-RELEASE-amd64.egg ../Jinja2-2.6-py2.7.egg ../Sphinx-1.1.3-py2.7.egg ../virtualenv-1.9.1-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) /usr/local/lib/python2.7/site-packages/easy-install.pth.dist: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) Looks like py-distribute is not installed at all. what was the outcome of portupgrade -fo devel/py-distribute devel/py-setuptools? Can you try running that again? It hasn't printed anything since the first time I tried to run it... and still print nothing. ___ 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: Upgrade devel/py-setuptools
2013-03-27 15:33, Loic Capdeville wrote: On 27/03/2013 14:27, Volodymyr Kostyrko wrote: 2013-03-27 15:06, Loic Capdeville wrote: /usr/local/lib/python2.7/site-packages/easy-install.pth: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg ../Pygments-1.5-py2.7.egg ../Babel-0.9.6-py2.7.egg ../MarkupSafe-0.15-py2.7-freebsd-9.0-RELEASE-amd64.egg ../Jinja2-2.6-py2.7.egg ../Sphinx-1.1.3-py2.7.egg ../virtualenv-1.9.1-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) /usr/local/lib/python2.7/site-packages/easy-install.pth.dist: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) Looks like py-distribute is not installed at all. what was the outcome of portupgrade -fo devel/py-distribute devel/py-setuptools? Can you try running that again? It hasn't printed anything since the first time I tried to run it... and still print nothing. So here is a main problem. If it prints nothing it doesn't work. Do you have portupgrade or portmaster installed? Did it yield at least one line? Some errors? If it doesn't that's surely a sign that something is going wrong. -- Sphinx of black quartz, judge my vow. ___ 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: Upgrade devel/py-setuptools
On 27/03/2013 17:30, Volodymyr Kostyrko wrote: 2013-03-27 15:33, Loic Capdeville wrote: On 27/03/2013 14:27, Volodymyr Kostyrko wrote: 2013-03-27 15:06, Loic Capdeville wrote: /usr/local/lib/python2.7/site-packages/easy-install.pth: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg ../Pygments-1.5-py2.7.egg ../Babel-0.9.6-py2.7.egg ../MarkupSafe-0.15-py2.7-freebsd-9.0-RELEASE-amd64.egg ../Jinja2-2.6-py2.7.egg ../Sphinx-1.1.3-py2.7.egg ../virtualenv-1.9.1-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) /usr/local/lib/python2.7/site-packages/easy-install.pth.dist: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) Looks like py-distribute is not installed at all. what was the outcome of portupgrade -fo devel/py-distribute devel/py-setuptools? Can you try running that again? It hasn't printed anything since the first time I tried to run it... and still print nothing. So here is a main problem. If it prints nothing it doesn't work. Do you have portupgrade or portmaster installed? Did it yield at least one line? Some errors? If it doesn't that's surely a sign that something is going wrong. I use portupgrade regularly to upgrade my ports, and usually everything goes right. If fails only with that particular operation (or these portupgrade options) Do I have to install devel/py-distribute separately, or should the portupgrade -fo command do everything itself (uninstall py-setuptools and install py-distribute) ? ___ 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: Upgrade devel/py-setuptools
2013-03-27 18:37, Loic Capdeville wrote: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) Looks like py-distribute is not installed at all. what was the outcome of portupgrade -fo devel/py-distribute devel/py-setuptools? Can you try running that again? It hasn't printed anything since the first time I tried to run it... and still print nothing. So here is a main problem. If it prints nothing it doesn't work. Do you have portupgrade or portmaster installed? Did it yield at least one line? Some errors? If it doesn't that's surely a sign that something is going wrong. I use portupgrade regularly to upgrade my ports, and usually everything goes right. If fails only with that particular operation (or these portupgrade options) Do I have to install devel/py-distribute separately, or should the portupgrade -fo command do everything itself (uninstall py-setuptools and install py-distribute) ? This command should forcefully deintsall second package and replace it with first one. I'm not using portupgrade, I switched to portmaster long time ago so I can't help you with it. If you want to make the switch by hand I think you should: pkg_delete -f py27-setuptools-0.6c11_3 # now write down the whole list of dependent packages cd /usr/ports/devel/py-distribute ; make install clean portupgrade -f ..list of packages that require setuptools.. -- Sphinx of black quartz, judge my vow. ___ 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: Upgrade devel/py-setuptools
On 27-3-2013 17:37, Loic Capdeville wrote: I use portupgrade regularly to upgrade my ports, and usually everything goes right. If fails only with that particular operation (or these portupgrade options) Do I have to install devel/py-distribute separately, or should the portupgrade -fo command do everything itself (uninstall py-setuptools and install py-distribute) ? I had some problems with this one as well. I eventually ended up by pkg_deleting -f the package, delete manually some file portinstall complaints about, and after that it worked. Peter -- http://www.boosten.org - Geen virus gevonden in dit bericht. Gecontroleerd door AVG - www.avg.com Versie: 2013.0.2904 / Virusdatabase: 2641/6206 - datum van uitgifte: 03/26/13 ___ 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: Upgrade from 6.4 to 9.1?
On 3/16/2013 3:46 PM, Fbsd8 wrote: Dan Nelson wrote: In the last episode (Mar 16), Drew Tomlinson said: I have an old system happily running 6.4 but am finding that it can no longer download or build a ports index. Thus I guess it's time to upgrade. What gotchas do I need to look out for? In the past my upgrades have always been simply downloading new source, reviewing kernel config file, and then rebuilding the system. Any ports that didn't work after that I would just rebuild as well. However I've never waited this long to upgrade. Do I need to do anything different? You won't be able to do a straight source build from 6.4 to 9.1; too many low-level changes like Makefile syntax and compiler options have changed. If you are comfortable with temporarily disabling non-essential things that fail to build, it is definitely possible to do a long jump to 9.1, but it'd be safer to either hop from 6.4 - (7-stable or 8-stable) - 9 doing buildkernels and buildworlds, or just do a binary upgrade of kernel and base system to 9.1. The best approach is to backup your user data and do a fresh install from 9.1 cdrom. You will bypass a bunch of headaches which may in the end force you to do a fresh install anyway. And it will save you a lot of compile time. It's alway a good feeling to know you have a pristine system when you start having problems. Thanks for the suggestions. I'll give these a try. Cheers, Drew -- Like card tricks? Visit The Alchemist's Warehouse to learn card magic secrets for free! http://alchemistswarehouse.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
Upgrade from 6.4 to 9.1?
I have an old system happily running 6.4 but am finding that it can no longer download or build a ports index. Thus I guess it's time to upgrade. What gotchas do I need to look out for? In the past my upgrades have always been simply downloading new source, reviewing kernel config file, and then rebuilding the system. Any ports that didn't work after that I would just rebuild as well. However I've never waited this long to upgrade. Do I need to do anything different? Thanks, Drew -- Like card tricks? Visit The Alchemist's Warehouse to learn card magic secrets for free! http://alchemistswarehouse.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: Upgrade from 6.4 to 9.1?
In the last episode (Mar 16), Drew Tomlinson said: I have an old system happily running 6.4 but am finding that it can no longer download or build a ports index. Thus I guess it's time to upgrade. What gotchas do I need to look out for? In the past my upgrades have always been simply downloading new source, reviewing kernel config file, and then rebuilding the system. Any ports that didn't work after that I would just rebuild as well. However I've never waited this long to upgrade. Do I need to do anything different? You won't be able to do a straight source build from 6.4 to 9.1; too many low-level changes like Makefile syntax and compiler options have changed. If you are comfortable with temporarily disabling non-essential things that fail to build, it is definitely possible to do a long jump to 9.1, but it'd be safer to either hop from 6.4 - (7-stable or 8-stable) - 9 doing buildkernels and buildworlds, or just do a binary upgrade of kernel and base system to 9.1. -- Dan Nelson dnel...@allantgroup.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: Upgrade from 6.4 to 9.1?
Dan Nelson wrote: In the last episode (Mar 16), Drew Tomlinson said: I have an old system happily running 6.4 but am finding that it can no longer download or build a ports index. Thus I guess it's time to upgrade. What gotchas do I need to look out for? In the past my upgrades have always been simply downloading new source, reviewing kernel config file, and then rebuilding the system. Any ports that didn't work after that I would just rebuild as well. However I've never waited this long to upgrade. Do I need to do anything different? You won't be able to do a straight source build from 6.4 to 9.1; too many low-level changes like Makefile syntax and compiler options have changed. If you are comfortable with temporarily disabling non-essential things that fail to build, it is definitely possible to do a long jump to 9.1, but it'd be safer to either hop from 6.4 - (7-stable or 8-stable) - 9 doing buildkernels and buildworlds, or just do a binary upgrade of kernel and base system to 9.1. The best approach is to backup your user data and do a fresh install from 9.1 cdrom. You will bypass a bunch of headaches which may in the end force you to do a fresh install anyway. And it will save you a lot of compile time. It's alway a good feeling to know you have a pristine system when you start having problems. ___ 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 and 9.1 upgrade
Hi All Upgraded 3 machines today from 9.0 to 9.1 all three run ZFS as a storage but not as a boot file system. One machine out of the three ended up with a very sick looking ZFS pool, not a big deal as this machine is a backup mirror for another system. So I did a zpool destroy tank then zpool create tank raidz ada1 ada2 ada3 ada4 ZFS tells me that ada1 might be part of an active pool and use -f to override this. zpool create -f tank raidz ada1 ada2 ada3 ada4 cannot create 'tank': no such pool or dataset Any clues anyone? Regards ___ 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 and 9.1 upgrade
Em Sex, 2013-03-01 às 17:40 +, Graeme Dargie escreveu: Hi All Upgraded 3 machines today from 9.0 to 9.1 all three run ZFS as a storage but not as a boot file system. One machine out of the three ended up with a very sick looking ZFS pool, not a big deal as this machine is a backup mirror for another system. So I did a zpool destroy tank then zpool create tank raidz ada1 ada2 ada3 ada4 ZFS tells me that ada1 might be part of an active pool and use -f to override this. zpool create -f tank raidz ada1 ada2 ada3 ada4 cannot create 'tank': no such pool or dataset Any clues anyone? make sure the operating system really upgraded without errors from 9.0 to 9.1 sometimes the kernel modules are not in sync with the zfs modules on the filesystem. ZAP the data on ada1 (will erase all data on ada1) dd bs=64k if=/dev/zero of=/dev/ada1 count=1 restart the machine, should work Sergio ___ 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: Upgrade causes loss of all firefox settings (?)
On Wed, Feb 13, 2013 at 11:35 AM, Bernt Hansson b...@bananmonarki.se wrote: A blind Linux user's homepage: http://juliencoder.de/ The homepage of my provider: http://www.o2online.de/ What site is more pleasant ;)? The first one. Agree, it contains more information than the second one which is picture-flash based and I cannot see ~80% of its content :-) Anyway the best thing in BSD is that you can do ANYTHING from the commandline with a simple command set, including full system configuration, package creation, kernel build, etc :-) Best regards :-) Tomek Cedro -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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
OT: Upgrade causes loss of all firefox settings (?)
On Wed, 2013-02-13 at 11:39 +0100, CeDeROM wrote: Agree, it contains more information than the second one which is picture-flash based and I cannot see ~80% of its content :-) And the biggest evil is, that those web pages hide important things and they don't add a site map. I can't find the current location to download the bill and already clicked through billions of advertisings, that are nothing but a PITA. No FreeBSD browser and no Linux browser until now is able to open mails by the interface of the homepage, if I try to contact them, by their contact forms, I'm linked to the logout. In the past it already was hard to download the bill. No action for a click and right click, to download was banned. I had to close and open several browsers, to log out and in, out and in ... and when doing this for half an hour I was able to download the bill. Since I've got VBox with XP for a while, next time I'll test to access the homepage with XP. Regards, Ralf PS: Regarding to the topic: Does renaming the config dir work? ___ 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: Upgrade causes loss of all firefox settings (?)
On 12/02/2013 21:38, Ronald F. Guilmette wrote: In general, I don't upgrade my ports very often, so up until recently I was running a fairly old version of firefox (firefox-15.0.1,1). But over the weekend, I moved everything over to a new drive containing the latest 9.1-RELEASE FreeBSD, and with a complete set of freshly rebuilt ports, including the latest firefox 18.0.1. (As part of this process, I copied my entire /home directory over to the new drive.) So anway, mostly everything is still working ok, however at some time during this process, firefox apparently lost track of all of my personal settings... my start page, all of my bookmarks, and all of my saved web site user IDs an passwords. I looked in the /usr/ports/UPDATING file for some clue as to why this might have happened and found none. Looking into this issue a bit deeper, I've now learned that all of one's personal settings are stored in a directory having a name which has the following general form: ~/.mozilla/firefox/.default where the part is some eight character apparently random combination of lower case letters and digits. The odd thing is that it appears that all of my old firefox setting are still alive and well and living under a subdirectory of the ~/.mozilla/firefox directory called 4up9dkb1.default. However it does also appear that my execution of firefox, for the first time, on this new system I've been putting together has resulted in the creation of a brand new parallel subdirectory, located in the same directory as my original personal settings .default directory, but this new one is named nh2ykiym.default. And now, firefox is apparently saving and retrieving my (new set of) personal settings out of that new directory. So, um, what gives? Why did this happen? And more to the point, can I get back all of my personal settings just via the following seemingly intutive commands: rm -fr nh2ykiym.default mv 4up9dkb1.default nh2ykiym.default or will that break something else in some obscure but annoying way? Is there a file .mozilla/firefox/profiles.ini? If so it should list which profile to use. Just change it to the one you want and it should just work. I'm using an older version so don't know how the latest works Chris Regards, rfg ___ 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: Upgrade causes loss of all firefox settings (?)
On Wed, 2013-02-13 at 13:13 +, Chris Whitehouse wrote: Is there a file .mozilla/firefox/profiles.ini? If so it should list which profile to use. Just change it to the one you want and it should just work. I'm using an older version so don't know how the latest works Good point Chris! I've forgotten, that there is such a file, when using profiles. Btw. they are formated like this: spinymouse@precise:~$ ls -l /mnt/archlinux/home/spinymouse/.mozilla/firefox total 8 lrwxrwxrwx 1 spinymouse users 18 Dec 13 2011 archfox - /mnt/data2/archfox drwx-- 13 spinymouse users 4096 Oct 31 15:11 ndos9d6q.default -rw-r--r-- 1 spinymouse users 143 Apr 18 2012 profiles.ini spinymouse@precise:~$ cat /mnt/archlinux/home/spinymouse/.mozilla/firefox/profiles.ini [General] StartWithLastProfile=1 [Profile0] Name=d IsRelative=1 Path=ndos9d6q.default Default=1 [Profile1] Name=x IsRelative=1 Path=archfox ___ 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: Upgrade causes loss of all firefox settings (?)
In message CAFYkXjmA_DTP=Bzf=D+QSw890tbrz0+ZNTiLaWNj=dmr749...@mail.gmail.com CeDeROM cede...@tlen.pl wrote: On Tue, Feb 12, 2013 at 10:38 PM, Ronald F. Guilmette r...@tristatelogic.com wrote: Looking into this issue a bit deeper, I've now learned that all of one's personal settings are stored in a directory having a name which has the following general form: ~/.mozilla/firefox/.default Hey Ronald, are you sure there is no corruption on the disk? I have no reason whatsoever to suspect that there is. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Upgrade causes loss of all firefox settings (?)
In general, I don't upgrade my ports very often, so up until recently I was running a fairly old version of firefox (firefox-15.0.1,1). But over the weekend, I moved everything over to a new drive containing the latest 9.1-RELEASE FreeBSD, and with a complete set of freshly rebuilt ports, including the latest firefox 18.0.1. (As part of this process, I copied my entire /home directory over to the new drive.) So anway, mostly everything is still working ok, however at some time during this process, firefox apparently lost track of all of my personal settings... my start page, all of my bookmarks, and all of my saved web site user IDs an passwords. I looked in the /usr/ports/UPDATING file for some clue as to why this might have happened and found none. Looking into this issue a bit deeper, I've now learned that all of one's personal settings are stored in a directory having a name which has the following general form: ~/.mozilla/firefox/.default where the part is some eight character apparently random combination of lower case letters and digits. The odd thing is that it appears that all of my old firefox setting are still alive and well and living under a subdirectory of the ~/.mozilla/firefox directory called 4up9dkb1.default. However it does also appear that my execution of firefox, for the first time, on this new system I've been putting together has resulted in the creation of a brand new parallel subdirectory, located in the same directory as my original personal settings .default directory, but this new one is named nh2ykiym.default. And now, firefox is apparently saving and retrieving my (new set of) personal settings out of that new directory. So, um, what gives? Why did this happen? And more to the point, can I get back all of my personal settings just via the following seemingly intutive commands: rm -fr nh2ykiym.default mv 4up9dkb1.default nh2ykiym.default or will that break something else in some obscure but annoying way? Regards, rfg ___ 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
