RE: Upgrading to 6.2-RELEASE from 6.2-STABLE
The mountroot was failing to find and mount /dev/da0s1a. The device /dev/da0s1a is in /etc/fstab. Going to the loader prompt and loading the old kernel booted fine. So the problem appears to lie somewhere in the boot files or I added a option/device I probably should not have in the kernel. > -Original Message- > From: Brian A. Seklecki [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 21, 2007 7:51 AM > To: Mark Stout > Cc: Mark Stout; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > freebsd-questions@freebsd.org > Subject: RE: Upgrading to 6.2-RELEASE from 6.2-STABLE > > > not sure about fbsd but nbsd tries to resolve the BIOS drive ID (hex > 0x80?) that the 1st stage boot loader loaded off of into a candidate to > initialize the file system mount from. > > Then it goes after /etc/fstab, which has to agree . > > ~BAS > > On Wed, 2007-06-20 at 21:25 -0700, Mark Stout wrote: > > Well I got the server up and running on the old kernel. I redid the > > buildworld and buildkernel. I've held off for now on doing > installworld and > > installkernel until I get a better understanding of what caused me to go > > into mountroot. I use the "Escape to loader prompt" prompt to > load the old > > kernel. > > > > Does anyone know what causes one to load into a mountroot prompt? > > > > > > > > > -Original Message- > > > From: Brian A. Seklecki [mailto:[EMAIL PROTECTED] > > > Sent: Wednesday, June 13, 2007 8:52 AM > > > To: Mark Stout > > > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > > > freebsd-questions@freebsd.org > > > Subject: Re: Upgrading to 6.2-RELEASE from 6.2-STABLE > > > > > > > > > entering: > > > > > > mountroot> ufs:da0s1a > > > > > > ...doesn't work > > > > > > What does "?" command list. > > > > > > ~BAS > > > > > > On Tue, 2007-06-12 at 19:37 -0700, Mark Stout wrote: > > > > I couldn't load da0s1a even though /dev/da0s1a is my root > > > drive. Manually load my old kernel from the prompt worked. > > > > > > > > I believe the mountroot is during the boot load. I'm not > > > anywhere near being able to do anything. > > > > > > > > I have no idea what the problem is. > > > > > > > > [EMAIL PROTECTED] wrote: > > > > > > > > no idea, but maybe: > > > > boot /boot/kernel/kernel > > > > or > > > > boot /boot/kernel.old/kernel > > > > > > > > What is 'mountroot' - is that the boot loader or the kernel/system > > > > giving you that? > > > > > > > > try mounting your root drive! > > > > > > > > do a `df -k`, anything already mounted? > > > > > > > > oh! or try: > > > > fsck > > > > > > > > did it ask you to login? > > > > > > > > > > > > Mark Stout wrote: > > > > > I followed all the steps in the handbook as well as UPDATED > > > and after a installworld and mergemaster its booting into > > > 'mountroot>' and nothing I type mounts. This is a production > > > machine so I'm in dire need of assistence. > > > > > > > > > > [EMAIL PROTECTED] wrote: > > > > > On 11/06/07, Mark Stout <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > >>> Following the tasks in Rebuilding "world" in the handbook > > > > >>> > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworl > > > d.html I removed the > > > > >>> /usr/obj directory and did a buildworld. When tryinmg to > > > compile the kernel its failing on > > > > >>> unknown option "MD5". Commenting that out it fails on the > > > line above MD5, options LKM. > > > > >>> What's happening here? These two options papear in the > > > LINT file. I can't find anything > > > > >>> that explains why this would happen. > > > > >>> > > > > >> A follow-up to my last email. I copied GENERIC to RADIUS2 and > > > > >> symlinked to /root/kernel. Then added the various LINT options. > > > > >> > > > > >> I started commenting out what is failing when I try to > compile a new >
RE: Upgrading to 6.2-RELEASE from 6.2-STABLE
not sure about fbsd but nbsd tries to resolve the BIOS drive ID (hex 0x80?) that the 1st stage boot loader loaded off of into a candidate to initialize the file system mount from. Then it goes after /etc/fstab, which has to agree . ~BAS On Wed, 2007-06-20 at 21:25 -0700, Mark Stout wrote: > Well I got the server up and running on the old kernel. I redid the > buildworld and buildkernel. I've held off for now on doing installworld and > installkernel until I get a better understanding of what caused me to go > into mountroot. I use the "Escape to loader prompt" prompt to load the old > kernel. > > Does anyone know what causes one to load into a mountroot prompt? > > > > > -Original Message- > > From: Brian A. Seklecki [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, June 13, 2007 8:52 AM > > To: Mark Stout > > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > > freebsd-questions@freebsd.org > > Subject: Re: Upgrading to 6.2-RELEASE from 6.2-STABLE > > > > > > entering: > > > > mountroot> ufs:da0s1a > > > > ...doesn't work > > > > What does "?" command list. > > > > ~BAS > > > > On Tue, 2007-06-12 at 19:37 -0700, Mark Stout wrote: > > > I couldn't load da0s1a even though /dev/da0s1a is my root > > drive. Manually load my old kernel from the prompt worked. > > > > > > I believe the mountroot is during the boot load. I'm not > > anywhere near being able to do anything. > > > > > > I have no idea what the problem is. > > > > > > [EMAIL PROTECTED] wrote: > > > > > > no idea, but maybe: > > > boot /boot/kernel/kernel > > > or > > > boot /boot/kernel.old/kernel > > > > > > What is 'mountroot' - is that the boot loader or the kernel/system > > > giving you that? > > > > > > try mounting your root drive! > > > > > > do a `df -k`, anything already mounted? > > > > > > oh! or try: > > > fsck > > > > > > did it ask you to login? > > > > > > > > > Mark Stout wrote: > > > > I followed all the steps in the handbook as well as UPDATED > > and after a installworld and mergemaster its booting into > > 'mountroot>' and nothing I type mounts. This is a production > > machine so I'm in dire need of assistence. > > > > > > > > [EMAIL PROTECTED] wrote: > > > > On 11/06/07, Mark Stout <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > >>> Following the tasks in Rebuilding "world" in the handbook > > > >>> > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworl > > d.html I removed the > > > >>> /usr/obj directory and did a buildworld. When tryinmg to > > compile the kernel its failing on > > > >>> unknown option "MD5". Commenting that out it fails on the > > line above MD5, options LKM. > > > >>> What's happening here? These two options papear in the > > LINT file. I can't find anything > > > >>> that explains why this would happen. > > > >>> > > > >> A follow-up to my last email. I copied GENERIC to RADIUS2 and > > > >> symlinked to /root/kernel. Then added the various LINT options. > > > >> > > > >> I started commenting out what is failing when I try to compile a new > > > >> kernel. All are from the LINT file. Is MD5 a default that does not > > > >> need to be specifically added? What about ICMP_BANDLIM? And > > > >> support for IDE drives. Are these already handed elsewhere > > in GENERIC? > > > >> > > > >> # These all failed as unknown options: > > > >> unknown option "MD5" > > > >> unknown option "LKM" > > > >> unknown option "CD9660_ROOTDELAY" > > > >> unknown option "NSWAPDEV" > > > >> unknown option "TCP_COMPAT_42" > > > >> unknown option "ICMP_BANDLIM" (found in Handbook in Chapter > > 14 Securing FreeBSD) > > > >> > > > >> > > > >> # Do not understand why these are fialing > > > >> config: Error: device "acd0" is unknown > > > >> config: Error: device "wfd0" is unknown > > > >> config: Error: devic
RE: Upgrading to 6.2-RELEASE from 6.2-STABLE
Well I got the server up and running on the old kernel. I redid the buildworld and buildkernel. I've held off for now on doing installworld and installkernel until I get a better understanding of what caused me to go into mountroot. I use the "Escape to loader prompt" prompt to load the old kernel. Does anyone know what causes one to load into a mountroot prompt? > -Original Message- > From: Brian A. Seklecki [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 13, 2007 8:52 AM > To: Mark Stout > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > freebsd-questions@freebsd.org > Subject: Re: Upgrading to 6.2-RELEASE from 6.2-STABLE > > > entering: > > mountroot> ufs:da0s1a > > ...doesn't work > > What does "?" command list. > > ~BAS > > On Tue, 2007-06-12 at 19:37 -0700, Mark Stout wrote: > > I couldn't load da0s1a even though /dev/da0s1a is my root > drive. Manually load my old kernel from the prompt worked. > > > > I believe the mountroot is during the boot load. I'm not > anywhere near being able to do anything. > > > > I have no idea what the problem is. > > > > [EMAIL PROTECTED] wrote: > > > > no idea, but maybe: > > boot /boot/kernel/kernel > > or > > boot /boot/kernel.old/kernel > > > > What is 'mountroot' - is that the boot loader or the kernel/system > > giving you that? > > > > try mounting your root drive! > > > > do a `df -k`, anything already mounted? > > > > oh! or try: > > fsck > > > > did it ask you to login? > > > > > > Mark Stout wrote: > > > I followed all the steps in the handbook as well as UPDATED > and after a installworld and mergemaster its booting into > 'mountroot>' and nothing I type mounts. This is a production > machine so I'm in dire need of assistence. > > > > > > [EMAIL PROTECTED] wrote: > > > On 11/06/07, Mark Stout <[EMAIL PROTECTED]> wrote: > > > > > > > > >>> Following the tasks in Rebuilding "world" in the handbook > > >>> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworl > d.html I removed the > > >>> /usr/obj directory and did a buildworld. When tryinmg to > compile the kernel its failing on > > >>> unknown option "MD5". Commenting that out it fails on the > line above MD5, options LKM. > > >>> What's happening here? These two options papear in the > LINT file. I can't find anything > > >>> that explains why this would happen. > > >>> > > >> A follow-up to my last email. I copied GENERIC to RADIUS2 and > > >> symlinked to /root/kernel. Then added the various LINT options. > > >> > > >> I started commenting out what is failing when I try to compile a new > > >> kernel. All are from the LINT file. Is MD5 a default that does not > > >> need to be specifically added? What about ICMP_BANDLIM? And > > >> support for IDE drives. Are these already handed elsewhere > in GENERIC? > > >> > > >> # These all failed as unknown options: > > >> unknown option "MD5" > > >> unknown option "LKM" > > >> unknown option "CD9660_ROOTDELAY" > > >> unknown option "NSWAPDEV" > > >> unknown option "TCP_COMPAT_42" > > >> unknown option "ICMP_BANDLIM" (found in Handbook in Chapter > 14 Securing FreeBSD) > > >> > > >> > > >> # Do not understand why these are fialing > > >> config: Error: device "acd0" is unknown > > >> config: Error: device "wfd0" is unknown > > >> config: Error: device "wst0" is unknown > > >> > > >> # This failed as a syntax error > > >> controller wdc0at isa? port "IO_WD1" bio irq 14 > > >> > > >> > > > > > > Most of the above looks like old, deprecated > > > stuff from 5.x and earlier (the "controller wdc0" > > > line reminds me of 3.x or maybe NetBSD). > > > > > > IDE drive support is all handled by ata(4), all > > > you should need for those in your kernel config > > > is: > > > device ata > > > device atadisk > > > device atapicd > > > (and obviously:) > > > device eisa > > > dev
RE: Upgrading to 6.2-RELEASE from 6.2-STABLE
> -Original Message- > From: Brian A. Seklecki [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 13, 2007 8:52 AM > To: Mark Stout > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > freebsd-questions@freebsd.org > Subject: Re: Upgrading to 6.2-RELEASE from 6.2-STABLE > > > > On Tue, 2007-06-12 at 19:37 -0700, Mark Stout wrote: > > I couldn't load da0s1a even though /dev/da0s1a is my root > drive. Manually load my old kernel from the prompt worked. > > > > I believe the mountroot is during the boot load. I'm not > anywhere near being able to do anything. > > > > I have no idea what the problem is. > > > > [EMAIL PROTECTED] wrote: > > > > no idea, but maybe: > > boot /boot/kernel/kernel > > or > > boot /boot/kernel.old/kernel > > > > What is 'mountroot' - is that the boot loader or the kernel/system > > giving you that? > > > > try mounting your root drive! > > > > do a `df -k`, anything already mounted? > > > > oh! or try: > > fsck > > > > did it ask you to login? > > > > > > Mark Stout wrote: > > > I followed all the steps in the handbook as well as UPDATED > and after a installworld and mergemaster its booting into > 'mountroot>' and nothing I type mounts. This is a production > machine so I'm in dire need of assistence. > > > > > > [EMAIL PROTECTED] wrote: > > > On 11/06/07, Mark Stout <[EMAIL PROTECTED]> wrote: > > > > > > > > >>> Following the tasks in Rebuilding "world" in the handbook > > >>> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworl > d.html I removed the > > >>> /usr/obj directory and did a buildworld. When tryinmg to > compile the kernel its failing on > > >>> unknown option "MD5". Commenting that out it fails on the > line above MD5, options LKM. > > >>> What's happening here? These two options papear in the > LINT file. I can't find anything > > >>> that explains why this would happen. > > >>> > > >> A follow-up to my last email. I copied GENERIC to RADIUS2 and > > >> symlinked to /root/kernel. Then added the various LINT options. > > >> > > >> I started commenting out what is failing when I try to compile a new > > >> kernel. All are from the LINT file. Is MD5 a default that does not > > >> need to be specifically added? What about ICMP_BANDLIM? And > > >> support for IDE drives. Are these already handed elsewhere > in GENERIC? > > >> > > >> # These all failed as unknown options: > > >> unknown option "MD5" > > >> unknown option "LKM" > > >> unknown option "CD9660_ROOTDELAY" > > >> unknown option "NSWAPDEV" > > >> unknown option "TCP_COMPAT_42" > > >> unknown option "ICMP_BANDLIM" (found in Handbook in Chapter > 14 Securing FreeBSD) > > >> > > >> > > >> # Do not understand why these are fialing > > >> config: Error: device "acd0" is unknown > > >> config: Error: device "wfd0" is unknown > > >> config: Error: device "wst0" is unknown > > >> > > >> # This failed as a syntax error > > >> controller wdc0at isa? port "IO_WD1" bio irq 14 > > >> > > >> > > > > > > Most of the above looks like old, deprecated > > > stuff from 5.x and earlier (the "controller wdc0" > > > line reminds me of 3.x or maybe NetBSD). > > > > > > IDE drive support is all handled by ata(4), all > > > you should need for those in your kernel config > > > is: > > > device ata > > > device atadisk > > > device atapicd > > > (and obviously:) > > > device eisa > > > device pci > > > Which are already part of GENERIC. > > > > > > /usr/src/sys//conf/LINT doesn't exist in 6.x. > > > Try looking at /usr/src/sys//conf/NOTES > > > and /usr/src/sys/conf/NOTES for knobs to twist > > > and buttons to push. > > > > > > entering: > > mountroot> ufs:da0s1a > > ...doesn't work > > What does "?" command list. > > ~BAS > It lists all available drives mount points and then some, e.g. fd0, da0, da01, da01s, da0s1a, da0s
Re: Upgrading to 6.2-RELEASE from 6.2-STABLE
entering: mountroot> ufs:da0s1a ...doesn't work What does "?" command list. ~BAS On Tue, 2007-06-12 at 19:37 -0700, Mark Stout wrote: > I couldn't load da0s1a even though /dev/da0s1a is my root drive. Manually > load my old kernel from the prompt worked. > > I believe the mountroot is during the boot load. I'm not anywhere near being > able to do anything. > > I have no idea what the problem is. > > [EMAIL PROTECTED] wrote: > > no idea, but maybe: > boot /boot/kernel/kernel > or > boot /boot/kernel.old/kernel > > What is 'mountroot' - is that the boot loader or the kernel/system > giving you that? > > try mounting your root drive! > > do a `df -k`, anything already mounted? > > oh! or try: > fsck > > did it ask you to login? > > > Mark Stout wrote: > > I followed all the steps in the handbook as well as UPDATED and after a > > installworld and mergemaster its booting into 'mountroot>' and nothing I > > type mounts. This is a production machine so I'm in dire need of > > assistence. > > > > [EMAIL PROTECTED] wrote: > > On 11/06/07, Mark Stout <[EMAIL PROTECTED]> wrote: > > > > > >>> Following the tasks in Rebuilding "world" in the handbook > >>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html > >>> I removed the > >>> /usr/obj directory and did a buildworld. When tryinmg to compile the > >>> kernel its failing on > >>> unknown option "MD5". Commenting that out it fails on the line above > >>> MD5, options LKM. > >>> What's happening here? These two options papear in the LINT file. I > >>> can't find anything > >>> that explains why this would happen. > >>> > >> A follow-up to my last email. I copied GENERIC to RADIUS2 and > >> symlinked to /root/kernel. Then added the various LINT options. > >> > >> I started commenting out what is failing when I try to compile a new > >> kernel. All are from the LINT file. Is MD5 a default that does not > >> need to be specifically added? What about ICMP_BANDLIM? And > >> support for IDE drives. Are these already handed elsewhere in GENERIC? > >> > >> # These all failed as unknown options: > >> unknown option "MD5" > >> unknown option "LKM" > >> unknown option "CD9660_ROOTDELAY" > >> unknown option "NSWAPDEV" > >> unknown option "TCP_COMPAT_42" > >> unknown option "ICMP_BANDLIM" (found in Handbook in Chapter 14 Securing > >> FreeBSD) > >> > >> > >> # Do not understand why these are fialing > >> config: Error: device "acd0" is unknown > >> config: Error: device "wfd0" is unknown > >> config: Error: device "wst0" is unknown > >> > >> # This failed as a syntax error > >> controller wdc0at isa? port "IO_WD1" bio irq 14 > >> > >> > > > > Most of the above looks like old, deprecated > > stuff from 5.x and earlier (the "controller wdc0" > > line reminds me of 3.x or maybe NetBSD). > > > > IDE drive support is all handled by ata(4), all > > you should need for those in your kernel config > > is: > > device ata > > device atadisk > > device atapicd > > (and obviously:) > > device eisa > > device pci > > Which are already part of GENERIC. > > > > /usr/src/sys//conf/LINT doesn't exist in 6.x. > > Try looking at /usr/src/sys//conf/NOTES > > and /usr/src/sys/conf/NOTES for knobs to twist > > and buttons to push. > > > > > > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading to 6.2-RELEASE from 6.2-STABLE
Hi Mark, Some months ago i tried to upgrade my source from 5.2 to 6.1. I did "something" wrong and It took me 2 to 4 weeks to stabilize my system and to be honest i tried so many things that i am not sure what I did exactly and brought it back to normal. I remember re-building and re-installing the kernel and suddenly everything was working properly. I believe that in your case the problem was caused while using mergemaster... In general it is not recommended to update to a major version like this and the procedure is slightly different than when upgrading from a minor version. After what i read and since this is a production machine, i believe it is better that you take a (manual...?) back up of the configuration files (even copy & paste them on paper - if you cannot boot, mount the drive with a CD) and re-install 6.2clean :( You have to take the decision whether this will save you time or not, since after all these it gets confusing, you cannot really remember what you were doing (4 days ago) and you may cause even more problems or waste time if you continue.. It is even more difficult for us to understand what went wrong in your case... Ideally you could use a different machine (or hdd - temporarily) to do this and then if you want sit down quietly and play with the current one. Kind Regards On 12/06/07, Mark Stout <[EMAIL PROTECTED]> wrote: I couldn't load da0s1a even though /dev/da0s1a is my root drive. Manually load my old kernel from the prompt worked. I believe the mountroot is during the boot load. I'm not anywhere near being able to do anything. I have no idea what the problem is. [EMAIL PROTECTED] wrote: no idea, but maybe: boot /boot/kernel/kernel or boot /boot/kernel.old/kernel What is 'mountroot' - is that the boot loader or the kernel/system giving you that? try mounting your root drive! do a `df -k`, anything already mounted? oh! or try: fsck did it ask you to login? Mark Stout wrote: > I followed all the steps in the handbook as well as UPDATED and after a installworld and mergemaster its booting into 'mountroot>' and nothing I type mounts. This is a production machine so I'm in dire need of assistence. > > [EMAIL PROTECTED] wrote: > On 11/06/07, Mark Stout <[EMAIL PROTECTED]> wrote: > > >>> Following the tasks in Rebuilding "world" in the handbook >>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html I removed the >>> /usr/obj directory and did a buildworld. When tryinmg to compile the kernel its failing on >>> unknown option "MD5". Commenting that out it fails on the line above MD5, options LKM. >>> What's happening here? These two options papear in the LINT file. I can't find anything >>> that explains why this would happen. >>> >> A follow-up to my last email. I copied GENERIC to RADIUS2 and >> symlinked to /root/kernel. Then added the various LINT options. >> >> I started commenting out what is failing when I try to compile a new >> kernel. All are from the LINT file. Is MD5 a default that does not >> need to be specifically added? What about ICMP_BANDLIM? And >> support for IDE drives. Are these already handed elsewhere in GENERIC? >> >> # These all failed as unknown options: >> unknown option "MD5" >> unknown option "LKM" >> unknown option "CD9660_ROOTDELAY" >> unknown option "NSWAPDEV" >> unknown option "TCP_COMPAT_42" >> unknown option "ICMP_BANDLIM" (found in Handbook in Chapter 14 Securing FreeBSD) >> >> >> # Do not understand why these are fialing >> config: Error: device "acd0" is unknown >> config: Error: device "wfd0" is unknown >> config: Error: device "wst0" is unknown >> >> # This failed as a syntax error >> controller wdc0at isa? port "IO_WD1" bio irq 14 >> >> > > Most of the above looks like old, deprecated > stuff from 5.x and earlier (the "controller wdc0" > line reminds me of 3.x or maybe NetBSD). > > IDE drive support is all handled by ata(4), all > you should need for those in your kernel config > is: > device ata > device atadisk > device atapicd > (and obviously:) > device eisa > device pci > Which are already part of GENERIC. > > /usr/src/sys//conf/LINT doesn't exist in 6.x. > Try looking at /usr/src/sys//conf/NOTES > and /usr/src/sys/conf/NOTES for knobs to twist > and buttons to push. > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to " [EMAIL PROTECTED]" -- Spiros P. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading to 6.2-RELEASE from 6.2-STABLE
I couldn't load da0s1a even though /dev/da0s1a is my root drive. Manually load my old kernel from the prompt worked. I believe the mountroot is during the boot load. I'm not anywhere near being able to do anything. I have no idea what the problem is. [EMAIL PROTECTED] wrote: no idea, but maybe: boot /boot/kernel/kernel or boot /boot/kernel.old/kernel What is 'mountroot' - is that the boot loader or the kernel/system giving you that? try mounting your root drive! do a `df -k`, anything already mounted? oh! or try: fsck did it ask you to login? Mark Stout wrote: > I followed all the steps in the handbook as well as UPDATED and after a > installworld and mergemaster its booting into 'mountroot>' and nothing I type > mounts. This is a production machine so I'm in dire need of assistence. > > [EMAIL PROTECTED] wrote: > On 11/06/07, Mark Stout <[EMAIL PROTECTED]> wrote: > > >>> Following the tasks in Rebuilding "world" in the handbook >>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html I >>> removed the >>> /usr/obj directory and did a buildworld. When tryinmg to compile the >>> kernel its failing on >>> unknown option "MD5". Commenting that out it fails on the line above MD5, >>> options LKM. >>> What's happening here? These two options papear in the LINT file. I >>> can't find anything >>> that explains why this would happen. >>> >> A follow-up to my last email. I copied GENERIC to RADIUS2 and >> symlinked to /root/kernel. Then added the various LINT options. >> >> I started commenting out what is failing when I try to compile a new >> kernel. All are from the LINT file. Is MD5 a default that does not >> need to be specifically added? What about ICMP_BANDLIM? And >> support for IDE drives. Are these already handed elsewhere in GENERIC? >> >> # These all failed as unknown options: >> unknown option "MD5" >> unknown option "LKM" >> unknown option "CD9660_ROOTDELAY" >> unknown option "NSWAPDEV" >> unknown option "TCP_COMPAT_42" >> unknown option "ICMP_BANDLIM" (found in Handbook in Chapter 14 Securing >> FreeBSD) >> >> >> # Do not understand why these are fialing >> config: Error: device "acd0" is unknown >> config: Error: device "wfd0" is unknown >> config: Error: device "wst0" is unknown >> >> # This failed as a syntax error >> controller wdc0at isa? port "IO_WD1" bio irq 14 >> >> > > Most of the above looks like old, deprecated > stuff from 5.x and earlier (the "controller wdc0" > line reminds me of 3.x or maybe NetBSD). > > IDE drive support is all handled by ata(4), all > you should need for those in your kernel config > is: > device ata > device atadisk > device atapicd > (and obviously:) > device eisa > device pci > Which are already part of GENERIC. > > /usr/src/sys//conf/LINT doesn't exist in 6.x. > Try looking at /usr/src/sys//conf/NOTES > and /usr/src/sys/conf/NOTES for knobs to twist > and buttons to push. > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading to 6.2-RELEASE from 6.2-STABLE
no idea, but maybe: boot /boot/kernel/kernel or boot /boot/kernel.old/kernel What is 'mountroot' - is that the boot loader or the kernel/system giving you that? try mounting your root drive! do a `df -k`, anything already mounted? oh! or try: fsck did it ask you to login? Mark Stout wrote: I followed all the steps in the handbook as well as UPDATED and after a installworld and mergemaster its booting into 'mountroot>' and nothing I type mounts. This is a production machine so I'm in dire need of assistence. [EMAIL PROTECTED] wrote: On 11/06/07, Mark Stout <[EMAIL PROTECTED]> wrote: Following the tasks in Rebuilding "world" in the handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html I removed the /usr/obj directory and did a buildworld. When tryinmg to compile the kernel its failing on unknown option "MD5". Commenting that out it fails on the line above MD5, options LKM. What's happening here? These two options papear in the LINT file. I can't find anything that explains why this would happen. A follow-up to my last email. I copied GENERIC to RADIUS2 and symlinked to /root/kernel. Then added the various LINT options. I started commenting out what is failing when I try to compile a new kernel. All are from the LINT file. Is MD5 a default that does not need to be specifically added? What about ICMP_BANDLIM? And support for IDE drives. Are these already handed elsewhere in GENERIC? # These all failed as unknown options: unknown option "MD5" unknown option "LKM" unknown option "CD9660_ROOTDELAY" unknown option "NSWAPDEV" unknown option "TCP_COMPAT_42" unknown option "ICMP_BANDLIM" (found in Handbook in Chapter 14 Securing FreeBSD) # Do not understand why these are fialing config: Error: device "acd0" is unknown config: Error: device "wfd0" is unknown config: Error: device "wst0" is unknown # This failed as a syntax error controller wdc0at isa? port "IO_WD1" bio irq 14 Most of the above looks like old, deprecated stuff from 5.x and earlier (the "controller wdc0" line reminds me of 3.x or maybe NetBSD). IDE drive support is all handled by ata(4), all you should need for those in your kernel config is: device ata device atadisk device atapicd (and obviously:) device eisa device pci Which are already part of GENERIC. /usr/src/sys//conf/LINT doesn't exist in 6.x. Try looking at /usr/src/sys//conf/NOTES and /usr/src/sys/conf/NOTES for knobs to twist and buttons to push. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading to 6.2-RELEASE from 6.2-STABLE
I followed all the steps in the handbook as well as UPDATED and after a installworld and mergemaster its booting into 'mountroot>' and nothing I type mounts. This is a production machine so I'm in dire need of assistence. [EMAIL PROTECTED] wrote: On 11/06/07, Mark Stout <[EMAIL PROTECTED]> wrote: > > Following the tasks in Rebuilding "world" in the handbook > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html I > > removed the > > /usr/obj directory and did a buildworld. When tryinmg to compile the > > kernel its failing on > > unknown option "MD5". Commenting that out it fails on the line above MD5, > > options LKM. > > What's happening here? These two options papear in the LINT file. I > > can't find anything > > that explains why this would happen. > > A follow-up to my last email. I copied GENERIC to RADIUS2 and > symlinked to /root/kernel. Then added the various LINT options. > > I started commenting out what is failing when I try to compile a new > kernel. All are from the LINT file. Is MD5 a default that does not > need to be specifically added? What about ICMP_BANDLIM? And > support for IDE drives. Are these already handed elsewhere in GENERIC? > > # These all failed as unknown options: > unknown option "MD5" > unknown option "LKM" > unknown option "CD9660_ROOTDELAY" > unknown option "NSWAPDEV" > unknown option "TCP_COMPAT_42" > unknown option "ICMP_BANDLIM" (found in Handbook in Chapter 14 Securing > FreeBSD) > > > # Do not understand why these are fialing > config: Error: device "acd0" is unknown > config: Error: device "wfd0" is unknown > config: Error: device "wst0" is unknown > > # This failed as a syntax error > controller wdc0at isa? port "IO_WD1" bio irq 14 > Most of the above looks like old, deprecated stuff from 5.x and earlier (the "controller wdc0" line reminds me of 3.x or maybe NetBSD). IDE drive support is all handled by ata(4), all you should need for those in your kernel config is: device ata device atadisk device atapicd (and obviously:) device eisa device pci Which are already part of GENERIC. /usr/src/sys//conf/LINT doesn't exist in 6.x. Try looking at /usr/src/sys//conf/NOTES and /usr/src/sys/conf/NOTES for knobs to twist and buttons to push. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading to 6.2-RELEASE from 6.2-STABLE
On 11/06/07, Mark Stout <[EMAIL PROTECTED]> wrote: > Following the tasks in Rebuilding "world" in the handbook > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html I removed the > /usr/obj directory and did a buildworld. When tryinmg to compile the kernel its failing on > unknown option "MD5". Commenting that out it fails on the line above MD5, options LKM. > What's happening here? These two options papear in the LINT file. I can't find anything > that explains why this would happen. A follow-up to my last email. I copied GENERIC to RADIUS2 and symlinked to /root/kernel. Then added the various LINT options. I started commenting out what is failing when I try to compile a new kernel. All are from the LINT file. Is MD5 a default that does not need to be specifically added? What about ICMP_BANDLIM? And support for IDE drives. Are these already handed elsewhere in GENERIC? # These all failed as unknown options: unknown option "MD5" unknown option "LKM" unknown option "CD9660_ROOTDELAY" unknown option "NSWAPDEV" unknown option "TCP_COMPAT_42" unknown option "ICMP_BANDLIM" (found in Handbook in Chapter 14 Securing FreeBSD) # Do not understand why these are fialing config: Error: device "acd0" is unknown config: Error: device "wfd0" is unknown config: Error: device "wst0" is unknown # This failed as a syntax error controller wdc0at isa? port "IO_WD1" bio irq 14 Most of the above looks like old, deprecated stuff from 5.x and earlier (the "controller wdc0" line reminds me of 3.x or maybe NetBSD). IDE drive support is all handled by ata(4), all you should need for those in your kernel config is: device ata device atadisk device atapicd (and obviously:) device eisa device pci Which are already part of GENERIC. /usr/src/sys//conf/LINT doesn't exist in 6.x. Try looking at /usr/src/sys//conf/NOTES and /usr/src/sys/conf/NOTES for knobs to twist and buttons to push. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading to 6.2-RELEASE from 6.2-STABLE
Mark Stout wrote: Thank you, Mark Stout VPM Global Internet Services, Inc. 530-626-4218 x205 Office 530-626-7182 Fax 530-554-9295 VoIP 916-240-2850 Cell www.vpm.com <http://www.vpm.com> This email and any files transmitted with it are confidential and intended solely for the use of the individual to whom they are addressed. If you are not the intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited, and asked to notify us immediately, then delete this email. E-mail transmission cannot be guaranteed to be secure or error-free and VPM Global Internet Services, Inc. does not accept liability for any errors or omissions in the contents of this message. Any views or opinions presented are solely those of the author and do not necessarily represent those of VPM Global Internet Services, Inc. -Original Message- From: Mark Stout [mailto:[EMAIL PROTECTED] Sent: Monday, June 11, 2007 9:24 AM To: Mikhail Goriachev; Abdullah Ibn Hamad Al-Marri Cc: freebsd-questions@freebsd.org Subject: RE: Upgrading to 6.2-RELEASE from 6.2-STABLE -Original Message- From: Mikhail Goriachev [mailto:[EMAIL PROTECTED] Sent: Sunday, June 10, 2007 9:27 AM To: Abdullah Ibn Hamad Al-Marri Cc: Mark Stout; freebsd-questions@freebsd.org Subject: Re: Upgrading to 6.2-RELEASE from 6.2-STABLE Abdullah Ibn Hamad Al-Marri wrote: On 6/10/07, Mark Stout <[EMAIL PROTECTED]> wrote: So how should I fix this? Thank you, Mark Stout cd /usr/src make cleanworld mergemaster -p make buildworld make buildkernel make installkernel reboot cd /usr/src make installworld mergemaster -iU reboot You are done. :) The *correct* procedure is described in: /usr/src/Makefile and even more detailed at: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html Following the tasks in Rebuilding “world” in the handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html I removed the /usr/obj directory and did a buildworld. When tryinmg to compile the kernel its failing on unknown option "MD5". Commenting that out it fails on the line above MD5, options LKM. What's happening here? These two options papear in the LINT file. I can't find anything that explains why this would happen. A follow-up to my last email. I copied GENERIC to RADIUS2 and symlinked to /root/kernel. Then added the various LINT options. I started commenting out what is failing when I try to compile a new kernel. All are from the LINT file. Is MD5 a default that does not need to be specifically added? What about ICMP_BANDLIM? And support for IDE drives. Are these already handed elsewhere in GENERIC? # These all failed as unknown options: unknown option "MD5" unknown option "LKM" unknown option "CD9660_ROOTDELAY" unknown option "NSWAPDEV" unknown option "TCP_COMPAT_42" unknown option "ICMP_BANDLIM" (found in Handbook in Chapter 14 Securing FreeBSD) # Do not understand why these are fialing config: Error: device "acd0" is unknown config: Error: device "wfd0" is unknown config: Error: device "wst0" is unknown # This failed as a syntax error controller wdc0at isa? port "IO_WD1" bio irq 14 Do you really need those options? GENERIC is sufficient for production use. Try running it first and see how it goes. I'd recommend adding/tweaking things only if you understand the outcome and necessity of them. Regards, Mikhail. -- Mikhail Goriachev Webanoide Telephone: +61 (0)3 62252501 Mobile Phone: +61 (0)4 38255158 E-Mail: [EMAIL PROTECTED] Web: www.webanoide.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Upgrading to 6.2-RELEASE from 6.2-STABLE
Thank you, Mark Stout VPM Global Internet Services, Inc. 530-626-4218 x205 Office 530-626-7182 Fax 530-554-9295 VoIP 916-240-2850 Cell www.vpm.com <http://www.vpm.com> This email and any files transmitted with it are confidential and intended solely for the use of the individual to whom they are addressed. If you are not the intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited, and asked to notify us immediately, then delete this email. E-mail transmission cannot be guaranteed to be secure or error-free and VPM Global Internet Services, Inc. does not accept liability for any errors or omissions in the contents of this message. Any views or opinions presented are solely those of the author and do not necessarily represent those of VPM Global Internet Services, Inc. > -Original Message- > From: Mark Stout [mailto:[EMAIL PROTECTED] > Sent: Monday, June 11, 2007 9:24 AM > To: Mikhail Goriachev; Abdullah Ibn Hamad Al-Marri > Cc: freebsd-questions@freebsd.org > Subject: RE: Upgrading to 6.2-RELEASE from 6.2-STABLE > > > > > > -Original Message- > > From: Mikhail Goriachev [mailto:[EMAIL PROTECTED] > > Sent: Sunday, June 10, 2007 9:27 AM > > To: Abdullah Ibn Hamad Al-Marri > > Cc: Mark Stout; freebsd-questions@freebsd.org > > Subject: Re: Upgrading to 6.2-RELEASE from 6.2-STABLE > > > > > > Abdullah Ibn Hamad Al-Marri wrote: > > > On 6/10/07, Mark Stout <[EMAIL PROTECTED]> wrote: > > >> > > >> So how should I fix this? > > >> > > >> Thank you, > > >> Mark Stout > > > > > > cd /usr/src > > > make cleanworld > > > mergemaster -p > > > make buildworld > > > make buildkernel > > > make installkernel > > > reboot > > > > > > cd /usr/src > > > make installworld > > > mergemaster -iU > > > reboot > > > > > > You are done. :) > > > > > > The *correct* procedure is described in: > > > > /usr/src/Makefile > > > > and even more detailed at: > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html > > > > Following the tasks in Rebuilding “world” in the handbook > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html I > removed the > /usr/obj directory and did a buildworld. When tryinmg to compile the kernel > its failing on > unknown option "MD5". Commenting that out it fails on the line above MD5, > options LKM. > What's happening here? These two options papear in the LINT file. I can't > find anything > that explains why this would happen. A follow-up to my last email. I copied GENERIC to RADIUS2 and symlinked to /root/kernel. Then added the various LINT options. I started commenting out what is failing when I try to compile a new kernel. All are from the LINT file. Is MD5 a default that does not need to be specifically added? What about ICMP_BANDLIM? And support for IDE drives. Are these already handed elsewhere in GENERIC? # These all failed as unknown options: unknown option "MD5" unknown option "LKM" unknown option "CD9660_ROOTDELAY" unknown option "NSWAPDEV" unknown option "TCP_COMPAT_42" unknown option "ICMP_BANDLIM" (found in Handbook in Chapter 14 Securing FreeBSD) # Do not understand why these are fialing config: Error: device "acd0" is unknown config: Error: device "wfd0" is unknown config: Error: device "wst0" is unknown # This failed as a syntax error controller wdc0at isa? port "IO_WD1" bio irq 14 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Upgrading to 6.2-RELEASE from 6.2-STABLE
> -Original Message- > From: Mikhail Goriachev [mailto:[EMAIL PROTECTED] > Sent: Sunday, June 10, 2007 9:27 AM > To: Abdullah Ibn Hamad Al-Marri > Cc: Mark Stout; freebsd-questions@freebsd.org > Subject: Re: Upgrading to 6.2-RELEASE from 6.2-STABLE > > > Abdullah Ibn Hamad Al-Marri wrote: > > On 6/10/07, Mark Stout <[EMAIL PROTECTED]> wrote: > >> > >> So how should I fix this? > >> > >> Thank you, > >> Mark Stout > > > > cd /usr/src > > make cleanworld > > mergemaster -p > > make buildworld > > make buildkernel > > make installkernel > > reboot > > > > cd /usr/src > > make installworld > > mergemaster -iU > > reboot > > > > You are done. :) > > > The *correct* procedure is described in: > > /usr/src/Makefile > > and even more detailed at: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html > Following the tasks in Rebuilding “world” in the handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html I removed the /usr/obj directory and did a buildworld. When tryinmg to compile the kernel its failing on unknown option "MD5". Commenting that out it fails on the line above MD5, options LKM. What's happening here? These two options papear in the LINT file. I can't find anything that explains why this would happen. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading to 6.2-RELEASE from 6.2-STABLE
On 10/06/07, Abdullah Ibn Hamad Al-Marri <[EMAIL PROTECTED]> wrote: On 6/10/07, Mark Stout <[EMAIL PROTECTED]> wrote: > > > So how should I fix this? > > Thank you, > Mark Stout cd /usr/src make cleanworld mergemaster -p make buildworld make buildkernel make installkernel reboot cd /usr/src make installworld mergemaster -iU reboot You are done. :) Start with # rm -r /usr/obj/* -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading to 6.2-RELEASE from 6.2-STABLE
Abdullah Ibn Hamad Al-Marri wrote: On 6/10/07, Mark Stout <[EMAIL PROTECTED]> wrote: So how should I fix this? Thank you, Mark Stout cd /usr/src make cleanworld mergemaster -p make buildworld make buildkernel make installkernel reboot cd /usr/src make installworld mergemaster -iU reboot You are done. :) The *correct* procedure is described in: /usr/src/Makefile and even more detailed at: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html Regards, Mikhail. -- Mikhail Goriachev Webanoide Telephone: +61 (0)3 62252501 Mobile Phone: +61 (0)4 38255158 E-Mail: [EMAIL PROTECTED] Web: www.webanoide.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading to 6.2-RELEASE from 6.2-STABLE
On 6/10/07, Mark Stout <[EMAIL PROTECTED]> wrote: So how should I fix this? Thank you, Mark Stout cd /usr/src make cleanworld mergemaster -p make buildworld make buildkernel make installkernel reboot cd /usr/src make installworld mergemaster -iU reboot You are done. :) -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Upgrading to 6.2-RELEASE from 6.2-STABLE
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Saturday, June 09, 2007 7:32 PM > To: Mark Stout > Cc: freebsd-questions@freebsd.org > Subject: Re: Upgrading to 6.2-RELEASE from 6.2-STABLE > > > On 09/06/07, Mark Stout <[EMAIL PROTECTED]> wrote: > > > > > > > > > -Original Message- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > Sent: Friday, June 08, 2007 10:30 PM > > > To: Mark Stout > > > Cc: freebsd-questions@freebsd.org > > > Subject: Re: Upgrading to 6.2-RELEASE from 6.2-STABLE > > > > > > > > > On 08/06/07, Mark Stout <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > I'd prefer to remain at 6.2-STABLE but I can't find where > the problem is > > > > with these IP errors. I'm figuring I've got a mixed code > and that's the > > > > root cause but I'm not sure. > > > > > > Did you remove your object directories before > > > starting the build? > > > Did you build without an /etc/make.conf? > > > > > I did not remove the obj directories and everything in my /etc/make.conf > > file is commented out except for USA_RESIDENT and PERL_VER=5.8.8 and > > PERL_VERSION=5.8.8 > > > > On a mad hunch I would suspect stale files in /usr/obj/ > If they are still there (and the cause of your problems) > they will muss up your build on RELENG_6_2 as well. > > -- > -- So how should I fix this? Thank you, Mark Stout VPM Global Internet Services, Inc. 530-626-4218 x205 Office 530-626-7182 Fax 530-554-9295 VoIP 916-240-2850 Cell www.vpm.com <http://www.vpm.com> This email and any files transmitted with it are confidential and intended solely for the use of the individual to whom they are addressed. If you are not the intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited, and asked to notify us immediately, then delete this email. E-mail transmission cannot be guaranteed to be secure or error-free and VPM Global Internet Services, Inc. does not accept liability for any errors or omissions in the contents of this message. Any views or opinions presented are solely those of the author and do not necessarily represent those of VPM Global Internet Services, Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading to 6.2-RELEASE from 6.2-STABLE
On 09/06/07, Mark Stout <[EMAIL PROTECTED]> wrote: > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, June 08, 2007 10:30 PM > To: Mark Stout > Cc: freebsd-questions@freebsd.org > Subject: Re: Upgrading to 6.2-RELEASE from 6.2-STABLE > > > On 08/06/07, Mark Stout <[EMAIL PROTECTED]> wrote: > > > > > I'd prefer to remain at 6.2-STABLE but I can't find where the problem is > > with these IP errors. I'm figuring I've got a mixed code and that's the > > root cause but I'm not sure. > > Did you remove your object directories before > starting the build? > Did you build without an /etc/make.conf? > I did not remove the obj directories and everything in my /etc/make.conf file is commented out except for USA_RESIDENT and PERL_VER=5.8.8 and PERL_VERSION=5.8.8 On a mad hunch I would suspect stale files in /usr/obj/ If they are still there (and the cause of your problems) they will muss up your build on RELENG_6_2 as well. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading to 6.2-RELEASE from 6.2-STABLE
On 08/06/07, Mark Stout <[EMAIL PROTECTED]> wrote: I'd prefer to remain at 6.2-STABLE but I can't find where the problem is with these IP errors. I'm figuring I've got a mixed code and that's the root cause but I'm not sure. Did you remove your object directories before starting the build? Did you build without an /etc/make.conf? -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Upgrading to 6.2-RELEASE from 6.2-STABLE
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, June 08, 2007 9:12 PM > To: Mark Stout > Cc: freebsd-questions@freebsd.org > Subject: Re: Upgrading to 6.2-RELEASE from 6.2-STABLE > > > On 08/06/07, Mark Stout <[EMAIL PROTECTED]> wrote: > > Hello, > > > > I recently upgraded from 5.4-RELEASE to 6.2-STABLE. Now I'm > having problems > > with the TCP stack. I suspect its because of code differences. > I may have > > some older 5.4 code that was used during the build world process. For > > example, here's a partial ifconfig -a output > > > > fxp0: flags=8843 mtu 1500 > > options=8 > > inet 71.4.48.6 netmask 0xfe00 broadcast 71.4.49.255 > > inet 71.4.48.4 netmask 0x broadcast 71.4.48.4 > > inet 71.4.48.7 netmask 0x broadcast 71.4.48.7 > > inet 71.4.48.9 netmask 0x broadcast 71.4.48.9 > > > > What's interesting is I can ping 71.4.48.6 from the console. > > > > But I get the following whenever I ping any other aliased IP > from the local > > console. I can ping these from other machines. > > [root 6]> ping 71.4.48.4 > > PING 71.4.48.4 (71.4.48.4): 56 data bytes > > ping: sendto: Invalid argument > > ping: sendto: Invalid argument > > > > > > Looking up a domain using dig I get similar errors. It > actually returns the > > info I want but I still get the errors. > > [root 7]> dig www.google.com > > /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1151: > > internal_send: 71.4.48.2#53: Invalid argument > > /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1151: > > internal_send: 71.4.48.3#53: Invalid argument > > > > 71.4.48.2 and 71.4.48.3 are my DNS. > > > > > > So what I thought I'd do is move to 6.2-RELEASE. What I wanted to do is > > install the source code from > > > ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.2-RELEASE/src/* and do a > > build world and build kernel. I assume that's really all I > need to build a > > new system. Are there any caveats to do an upgrade this way? > > Iff you really do want to move back to 6.2-RELEASE, > I would advise building from the security branch, so > in your supfile make sure you have > tag=RELENG_6_2 > I'd prefer to remain at 6.2-STABLE but I can't find where the problem is with these IP errors. I'm figuring I've got a mixed code and that's the root cause but I'm not sure. Thank you, Mark Stout VPM Global Internet Services, Inc. 530-626-4218 x205 Office 530-626-7182 Fax 530-554-9295 VoIP 916-240-2850 Cell www.vpm.com <http://www.vpm.com> This email and any files transmitted with it are confidential and intended solely for the use of the individual to whom they are addressed. If you are not the intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited, and asked to notify us immediately, then delete this email. E-mail transmission cannot be guaranteed to be secure or error-free and VPM Global Internet Services, Inc. does not accept liability for any errors or omissions in the contents of this message. Any views or opinions presented are solely those of the author and do not necessarily represent those of VPM Global Internet Services, Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading to 6.2-RELEASE from 6.2-STABLE
On 08/06/07, Mark Stout <[EMAIL PROTECTED]> wrote: Hello, I recently upgraded from 5.4-RELEASE to 6.2-STABLE. Now I'm having problems with the TCP stack. I suspect its because of code differences. I may have some older 5.4 code that was used during the build world process. For example, here's a partial ifconfig -a output fxp0: flags=8843 mtu 1500 options=8 inet 71.4.48.6 netmask 0xfe00 broadcast 71.4.49.255 inet 71.4.48.4 netmask 0x broadcast 71.4.48.4 inet 71.4.48.7 netmask 0x broadcast 71.4.48.7 inet 71.4.48.9 netmask 0x broadcast 71.4.48.9 What's interesting is I can ping 71.4.48.6 from the console. But I get the following whenever I ping any other aliased IP from the local console. I can ping these from other machines. [root 6]> ping 71.4.48.4 PING 71.4.48.4 (71.4.48.4): 56 data bytes ping: sendto: Invalid argument ping: sendto: Invalid argument Looking up a domain using dig I get similar errors. It actually returns the info I want but I still get the errors. [root 7]> dig www.google.com /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1151: internal_send: 71.4.48.2#53: Invalid argument /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1151: internal_send: 71.4.48.3#53: Invalid argument 71.4.48.2 and 71.4.48.3 are my DNS. So what I thought I'd do is move to 6.2-RELEASE. What I wanted to do is install the source code from ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.2-RELEASE/src/* and do a build world and build kernel. I assume that's really all I need to build a new system. Are there any caveats to do an upgrade this way? Iff you really do want to move back to 6.2-RELEASE, I would advise building from the security branch, so in your supfile make sure you have tag=RELENG_6_2 -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
