Re: Problem with make buildworld during upgrade from 7.0-RELEASE to 7.2-RELEASE
Great response! There's a lot of good info here. Thanks, and I will check out the SSH keepalive settings. To update, I did finally solve my problem, although I was in a pickle there for a bit. Ironically, it's more intuitive to me to just do the install the old way (using make buildworld): I decided to attempt to install cvsup from my ports tree and thankfully it worked fine: cd /usr/ports/net/cvsup make install && make clean [Then, I just did:] tar -cyv /usr/home/myuser/7.2-RELEASE-src.tar.bz2 /usr/src/ rm -r /usr/src mkdir /usr/src rm -r /usr/obj cvsup my-supfile that gave me a fresh copy of the FreeBSD RELEASE-7.2 source tree (my-supfile had the correct release engine specified), and cleaned out any garbage that might have been in the /usr/obj directory [then:] mergemaster -pv env -i make buildworld nextboot -k GENERIC make buildkernel make installkernel shutdown -r now [log back in as su, then] mergemaster make installworld shutdown -r now [log back in as su, then] uname -a and get a nice listing that I'm running FreeBSD 7.2-RELEASE-p2 I'm guessing this method will work no matter what as long as you can install cvsup. Nice that I can do it over SSH too! Now to build a custom kernel! Thanks again, Joe On Tue, Jul 14, 2009 at 1:36 PM, Mel Flynn < mel.flynn+fbsd.questi...@mailing.thruhere.net > wrote: > On Tuesday 14 July 2009 11:51:40 Mel Flynn wrote: > > On Monday 13 July 2009 13:40:31 Joseph Bashe wrote: > > > I am going thru my first FreeBSD upgrade and it's not going too > smoothly. > > > I originally started the upgrade using the "freebsd-update" method. > This > > > is what I've done so far (all as root user): > > > > There's a few misconceptions in your understanding of the upgrade > process, > > which I'll try to address below. However, you're also using the wrong > > sequence of events. You *first* want to update your kernel and base > system, > > only then your ports. > > > > > PS. I am using a custom kernel. > > > > As such, freebsd-update cannot upgrade your kernel. > > That should be ", without the intermediate use of a GENERIC kernel.". > > -- > Mel > ___ > 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" > -- Joe Bashe ___ 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 with make buildworld during upgrade from 7.0-RELEASE to 7.2-RELEASE
On Tuesday 14 July 2009 11:51:40 Mel Flynn wrote: > On Monday 13 July 2009 13:40:31 Joseph Bashe wrote: > > I am going thru my first FreeBSD upgrade and it's not going too smoothly. > > I originally started the upgrade using the "freebsd-update" method. This > > is what I've done so far (all as root user): > > There's a few misconceptions in your understanding of the upgrade process, > which I'll try to address below. However, you're also using the wrong > sequence of events. You *first* want to update your kernel and base system, > only then your ports. > > > PS. I am using a custom kernel. > > As such, freebsd-update cannot upgrade your kernel. That should be ", without the intermediate use of a GENERIC kernel.". -- Mel ___ 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 with make buildworld during upgrade from 7.0-RELEASE to 7.2-RELEASE
On Monday 13 July 2009 13:40:31 Joseph Bashe wrote:
> I am going thru my first FreeBSD upgrade and it's not going too smoothly. I
> originally started the upgrade using the "freebsd-update" method. This is
> what I've done so far (all as root user):
There's a few misconceptions in your understanding of the upgrade process,
which I'll try to address below. However, you're also using the wrong sequence
of events. You *first* want to update your kernel and base system, only then
your ports.
> PS. I am using a custom kernel.
As such, freebsd-update cannot upgrade your kernel.
> 1. ran "portsnap fetch update" - [success]
>
> 2. ran "portupgrade -va" ["portupgrade"not found - i hadn't installed it
> yet"
>
> 3. ran "freebsd-update fetch" [success] (i know this was out of sequence
> from the guide)
>
> 4. installed portupgrade ("make install clean" from the dir in ports) [ssh
> connection dropped, so i had to login again]
>
> 5. installed portupgrade ("make install") [success] then "make clean"
> [success]
>
> 6. ran "portupgrade -va" [long process begins... strangely, several X
> components install although this is not desired]
echo WITHOUT_X11=yes >>/etc/make.conf
> 7. ran "freebsd-update fetch" again [success]
>
> 8. ran "freebsd-update upgrade -r 7.2-RELEASE" [ssh connection dies during
> "preparing to download files", so i log in again]
>
> 9. ran "freebsd-update upgrade -r 7.2-RELEASE" [~27,000 updates..] and of
> course ssh connection dies during "Fetching 3060 files" although "applying
> patches" succeeds. A note: these disconnects are not at all common during a
> normal ssh connection to this computer, it seems due to the
> resource-intense operations required for updating freebsd.
More likely to be bad queuing in the gateway or you're hitting the default
session timeout of 5 minutes of inactivity. See man ssh_config for
ServerAliveInteral and TCPKeepAlive.
> 10. log back in, ran "freebsd-update upgrade -r 7.2-RELEASE" [..success]
>
> 11. ran "freebsd-update install" [and of course ssh dies during "Installing
> updates..."]
>
> 12. log back in, ran "freebsd-update install".
>
> 13. Then i ran nextboot -k GENERIC and got "/boot/GENERIC doesn't exist".
> so, i copied kernel.old to /boot/GENERIC
This is out of sequence and likely the cause for some problems. First of all,
you must be sure that kernel.old is really a GENERIC 7.0-RELEASE kernel.
Secondly, this step /should/ have been run /before/ freebsd-update install.
> 14. Ok, maybe this was the problem. for some reason at this point i decide
> to run "freebsd-update install" again, and get "no updates are available".
>
> 15. Then I run "freebsd-update -r 7.2-RELEASE upgrade" again.. it downloads
> some patches, but then i get this error: "/usr/sbin/freebsd-update: cannot
> open files/.gz: No such file or directory" about 100 times.. plus, i get
> questions like
Running an upgrade again, without a rollback is generally not a good idea.
> "The following file will be removed, as it no longer exists in
> FreeBSD 7.2-RELEASE: /boot/device.hints
> Does this look reasonable (y/n)?"
>
> which doesn't look very good.
>
> 16. so, i issued a shutdown -r now command and crossed my fingers.. the
> system is still up, but it hasn't been upgraded (uname still reports
> 7.0-p11 for booting form the GENERIC kernel, and 7.0-p9 for the custom
> kernel). on top, make buildworld fails with:
>
> "Stop in /usr/src/secure/lib/libssh.
> *** Error code 1 "
>
> every time.
>
> and worse,
>
> any csup command dies with "/libexec/ld-elf.so.1: /lib/libc.so.7: version
> FBSD_1.1 required by /lib/libthr.so.3 not found" along with a lot of other
> commands... any ideas??
Your world and kernel are out of sync, because of loading a not upgraded
kernel with a freebsd-update'd 7.2 world. I would try fetching the 7.2 livefs
ISO, mount it as a vnode and install the GENERIC kernel from there to get your
system back in working order.
Example steps:
$ sha256 /data/isos/7.2-RELEASE-i386-livefs.iso
SHA256 (/data/isos/7.2-RELEASE-i386-livefs.iso) =
4faa7b9d78d125f9b28521247e32e1f0bef3b0b0f21b654ba22c6e79ca3301ce
$ sudo mdconfig -a -t vnode -f /data/isos/7.2-RELEASE-i386-livefs.iso -u 0
$ sudo mount -t cd9660 /dev/md0 /mnt
$ sudo mv /boot/kernel /boot/kernel.bogus
$ sudo cp -Rp /mnt/boot/kernel /boot/
$ shutdown -r now # may need sudo if you're not in operator group
If you still have problems after this, it's likely you need single user mode
to get back into working order. Given the number of errors given by the second
freebsd-update upgrade command I wouldn't trust a freebsd-update rollback.
This would be where I'd restore the backups using a livecd and restart the
freebsd-update process, this time sticking verbatim to the handbook, but
skipping the "portupgrade test run".
--
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freeb
Problem with make buildworld during upgrade from 7.0-RELEASE to 7.2-RELEASE
Hello,
I am going thru my first FreeBSD upgrade and it's not going too smoothly. I
originally started the upgrade using the "freebsd-update" method. This is
what I've done so far (all as root user):
PS. I am using a custom kernel.
1. ran "portsnap fetch update" - [success]
2. ran "portupgrade -va" ["portupgrade"not found - i hadn't installed it
yet"
3. ran "freebsd-update fetch" [success] (i know this was out of sequence
from the guide)
4. installed portupgrade ("make install clean" from the dir in ports) [ssh
connection dropped, so i had to login again]
5. installed portupgrade ("make install") [success] then "make clean"
[success]
6. ran "portupgrade -va" [long process begins... strangely, several X
components install although this is not desired]
7. ran "freebsd-update fetch" again [success]
8. ran "freebsd-update upgrade -r 7.2-RELEASE" [ssh connection dies during
"preparing to download files", so i log in again]
9. ran "freebsd-update upgrade -r 7.2-RELEASE" [~27,000 updates..] and of
course ssh connection dies during "Fetching 3060 files" although "applying
patches" succeeds. A note: these disconnects are not at all common during a
normal ssh connection to this computer, it seems due to the resource-intense
operations required for updating freebsd.
10. log back in, ran "freebsd-update upgrade -r 7.2-RELEASE" [..success]
11. ran "freebsd-update install" [and of course ssh dies during "Installing
updates..."]
12. log back in, ran "freebsd-update install".
13. Then i ran nextboot -k GENERIC and got "/boot/GENERIC doesn't exist".
so, i copied kernel.old to /boot/GENERIC
14. Ok, maybe this was the problem. for some reason at this point i decide
to run "freebsd-update install" again, and get "no updates are available".
15. Then I run "freebsd-update -r 7.2-RELEASE upgrade" again.. it downloads
some patches, but then i get this error: "/usr/sbin/freebsd-update: cannot
open files/.gz: No such file or directory" about 100 times.. plus, i get
questions like
"The following file will be removed, as it no longer exists in
FreeBSD 7.2-RELEASE: /boot/device.hints
Does this look reasonable (y/n)?"
which doesn't look very good.
16. so, i issued a shutdown -r now command and crossed my fingers.. the
system is still up, but it hasn't been upgraded (uname still reports 7.0-p11
for booting form the GENERIC kernel, and 7.0-p9 for the custom kernel). on
top, make buildworld fails with:
"Stop in /usr/src/secure/lib/libssh.
*** Error code 1 "
every time.
and worse,
any csup command dies with "/libexec/ld-elf.so.1: /lib/libc.so.7: version
FBSD_1.1 required by /lib/libthr.so.3 not found" along with a lot of other
commands... any ideas??
Just want to note that I log every keystroke on my servers so just let me
know any specifics would help you in diagnosing the problem.
Many thanks!
--
Joe Bashe
___
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 with make config and OPTIONS
Aurélien Ansel writes: > Hi, > (sorry for my poor english) > > I have a problem, I'm trying to upgrade an existing port (net/scapy) , > I have done some changes in the Makefile but when I test the command > make config' I have : > >===> Options unchanged > > I haven't the dialog box with the differents kinds of Options that are > written in the Makefile, i have try the 'make rmconfig' but no change. > I am working on my personnal directory, not in /usr/ports/... I tried the same thing with the original makefile, and couldn't reproduce it. Are you sure that's exactly what you typed? -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem with make config and OPTIONS
On Wed, Apr 29, 2009 at 10:20 AM, Aurélien Ansel
wrote:
> Hi,
> (sorry for my poor english)
>
> I have a problem, I'm trying to upgrade an existing port (net/scapy) , I
> have done some changes in the Makefile but when I test the command 'make
> config' I have :
>
> ===> Options unchanged
>
> I haven't the dialog box with the differents kinds of Options that are
> written in the Makefile, i have try the 'make rmconfig' but no change.
> I am working on my personnal directory, not in /usr/ports/...
>
> The Makefile is:
>
> # New ports collection makefile for: scapy
> # Date created: 08 dec 2005
> # Whom: vanhu
> #
> # $FreeBSD: ports/net/scapy/Makefile,v 1.6 2008/11/19 20:41:56 lwhsu Exp $
> #
> # TODO: - configurable --enable-xxx for various additional dependancies
>
> PORTNAME= scapy
> PORTVERSION= 2.0.0.10
> CATEGORIES= net
> MASTER_SITES= http://secdev.org/projects/scapy/files/
>
> MAINTAINER= va...@netasq.com
> COMMENT= Powerful interactive packet manipulation program in python
>
> RUN_DEPENDS= ${PYTHON_SITELIBDIR}/dnet.so:${PORTSDIR}/net/py-libdnet \
> ${PYTHON_SITELIBDIR}/pcap.py:${PORTSDIR}/net/py-pcap
>
> MAN1= scapy.1
> MANCOMPRESSED= yes
>
> USE_PYTHON= 2.5+
> USE_PYDISTUTILS=yes
>
> OPTIONS= PYX "Support for PostScript and PDF graphs drawing" off \
> PYCRYPTO "Support for py-crypto for WEP decoding" off \
> PYGNUPLOT "Support for py-gnuplot wrapper to plot graphs" off \
> P0F_BASE "Support for p0f OS signatures database" off \
> QUESO_BASE "Support for queso OS signatures database" off \
> NMAP "Support for nmap OS signatures database" off \
> MANUF "Support for wireshark's MANUF MAC database" off
>
> .include
>
> .if defined(WITH_PYX)
> RUN_DEPENDS+=
> ${PYTHON_SITELIBDIR}/pyx/__init__.py:${PORTSDIR}/graphics/py-PyX
> .endif
>
> .if defined(WITH_PYCRYPTO)
> RUN_DEPENDS+=
> ${PYTHON_SITELIBDIR}/Crypto/__init__.py:${PORTSDIR}/security/py-pycrypto
> .endif
>
> .if defined(WITH_PYGNUPLOT)
> RUN_DEPENDS+=
> ${PYTHON_SITELIBDIR}/Gnuplot/__init__.py:${PORTSDIR}/math/py-gnuplot
> .endif
>
> .if defined(WITH_P0F_BASE)
> RUN_DEPENDS+= ${LOCALBASE}/etc/p0f/p0f.fp:${PORTSDIR}/net-mgmt/p0f
> .endif
>
> .if defined(WITH_QUESO_BASE)
> RUN_DEPENDS+= ${LOCALBASE}/etc/queso.conf:${PORTSDIR}/net/queso
> .endif
>
> .if defined(WITH_NMAP)
> RUN_DEPENDS+=
> ${LOCALBASE}/share/nmap/nmap-os-fingerprints:${PORTSDIR}/security/nmap
> .endif
>
> .if defined(WITH_MANUF)
> RUN_DEPENDS+=
> ${LOCALBASE}/share/wireshark/manuf:${PORTSDIR}/net/wireshark
> .endif
>
> SCAPY_MODULES= nmap.py p0f.py queso.py
>
> post-patch:
> @${REINPLACE_CMD} "s,share/man/man1,man/man1," ${WRKSRC}/setup.py
> @${REINPLACE_CMD} "s,%%LOCALBASE%%,${LOCALBASE}," \
> ${SCAPY_MODULES:S,^,${WRKSRC}/scapy/modules/,} \
> ${WRKSRC}/scapy/config.py \
> ${WRKSRC}/scapy/utils6.py
>
> .include
>
>
>
>
> - Aurélien Ansel
The port options are stored in /var/db/ports. You can delete the
"options" file for your package from that dir. There's also ways to
force the configuration of files using portupgrade/portmaster. For
portmaster, the command is "portmaster --force-config". I don't know
about portupgrade.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Problem with make config and OPTIONS
Hi,
(sorry for my poor english)
I have a problem, I'm trying to upgrade an existing port (net/scapy) , I
have done some changes in the Makefile but when I test the command 'make
config' I have :
===> Options unchanged
I haven't the dialog box with the differents kinds of Options that are
written in the Makefile, i have try the 'make rmconfig' but no change.
I am working on my personnal directory, not in /usr/ports/...
The Makefile is:
# New ports collection makefile for:scapy
# Date created:08 dec 2005
# Whom:vanhu
#
# $FreeBSD: ports/net/scapy/Makefile,v 1.6 2008/11/19 20:41:56 lwhsu Exp $
#
# TODO: - configurable --enable-xxx for various additional dependancies
PORTNAME=scapy
PORTVERSION=2.0.0.10
CATEGORIES=net
MASTER_SITES=http://secdev.org/projects/scapy/files/
MAINTAINER=va...@netasq.com
COMMENT=Powerful interactive packet manipulation program in python
RUN_DEPENDS=${PYTHON_SITELIBDIR}/dnet.so:${PORTSDIR}/net/py-libdnet \
${PYTHON_SITELIBDIR}/pcap.py:${PORTSDIR}/net/py-pcap
MAN1=scapy.1
MANCOMPRESSED=yes
USE_PYTHON=2.5+
USE_PYDISTUTILS=yes
OPTIONS=PYX "Support for PostScript and PDF graphs drawing" off \
PYCRYPTO "Support for py-crypto for WEP decoding" off \
PYGNUPLOT "Support for py-gnuplot wrapper to plot graphs" off \
P0F_BASE "Support for p0f OS signatures database" off \
QUESO_BASE "Support for queso OS signatures database" off \
NMAP "Support for nmap OS signatures database" off \
MANUF "Support for wireshark's MANUF MAC database" off
.include
.if defined(WITH_PYX)
RUN_DEPENDS+=
${PYTHON_SITELIBDIR}/pyx/__init__.py:${PORTSDIR}/graphics/py-PyX
.endif
.if defined(WITH_PYCRYPTO)
RUN_DEPENDS+=
${PYTHON_SITELIBDIR}/Crypto/__init__.py:${PORTSDIR}/security/py-pycrypto
.endif
.if defined(WITH_PYGNUPLOT)
RUN_DEPENDS+=
${PYTHON_SITELIBDIR}/Gnuplot/__init__.py:${PORTSDIR}/math/py-gnuplot
.endif
.if defined(WITH_P0F_BASE)
RUN_DEPENDS+=${LOCALBASE}/etc/p0f/p0f.fp:${PORTSDIR}/net-mgmt/p0f
.endif
.if defined(WITH_QUESO_BASE)
RUN_DEPENDS+=${LOCALBASE}/etc/queso.conf:${PORTSDIR}/net/queso
.endif
.if defined(WITH_NMAP)
RUN_DEPENDS+=
${LOCALBASE}/share/nmap/nmap-os-fingerprints:${PORTSDIR}/security/nmap
.endif
.if defined(WITH_MANUF)
RUN_DEPENDS+=
${LOCALBASE}/share/wireshark/manuf:${PORTSDIR}/net/wireshark
.endif
SCAPY_MODULES=nmap.py p0f.py queso.py
post-patch:
@${REINPLACE_CMD} "s,share/man/man1,man/man1," ${WRKSRC}/setup.py
@${REINPLACE_CMD} "s,%%LOCALBASE%%,${LOCALBASE}," \
${SCAPY_MODULES:S,^,${WRKSRC}/scapy/modules/,} \
${WRKSRC}/scapy/config.py \
${WRKSRC}/scapy/utils6.py
.include
- Aurélien Ansel
___
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 with make
On Wed, Jan 18, 2006 at 11:00:13AM +0300, Ronnie Napster Tash wrote: > Hi list i just installed freeBSD 5.4 and i have tried to make buildworld but > if fails. > > Anybody who has faced this before? > > these are the errors it generates > > After setting up my firewall > cd /usr/src > make buildworld > > error make: don't know how to make buildworld. Stop You don't have the source code installed. Please see the handbook. Kris pgpEy7doGfXWl.pgp Description: PGP signature
Re: problem with make
Hi list i just installed freeBSD 5.4 and i have tried to make buildworld but if fails. Anybody who has faced this before? these are the errors it generates After setting up my firewall cd /usr/src make buildworld error make: don't know how to make buildworld. Stop -- Ronnie Tash Everything can be achieved as long you can do what it takes to achieve it! A wise man will seek an opportunity in every problem; A foolish man will see a problem in every opportunity. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problem with 'make installkernel' over NFS on FreeBSD 5.4
Oops, Forgot to mention that after mounting /usr/src and /usr/obj on the client machine, that I had issued the 'shutdown' command, as per the Handbook Thanks! --- Stuart Chalmers <[EMAIL PROTECTED]> wrote: > Hi, > > I am in the process of trying to do an update of > kernel and world on an old machine (machine A), > using > a newer, faster, machine (machine B). Machine B is > set up as an NFS server for machine A. > > The /etc/exports file on machine B inculdes: > > /usr -maproot=root:0 -alldirs -network 192.168.0.0 > -mask 255.255.255.0. > > Mahine A currently has address 192.168.0.197. > Machine > B has /usr mounted on a device, not, say, /usr/src. > > I have followed the following process. > > While logged onto machine B: > cvsup /usr/src > cd /usr/src > make buildworld > make buildkernel KERNCONF= > > Once this is complete, I then log onto machine A and > mount /usr/src and /usr/obj via NFS. The /etc/fstab > contains: > > 192.168.0.2:/usr/src /usr/src nfs ro,-i,noauto > 192.168.0.2:/usr/obj /usr/obj nfs rw,-i,noauto > > (Machine B has 192.168.0.2 assigned to it's internal > interface). The KERNCONF file is visible on machine > A, and the /etc/make.conf files are pretty similar, > speifically: > > CPUTYPE?=pentium > CFLAGS= -O2 -fno-strict-aliasing -pipe > COPTFLAGS= -O2 -fno-strict-aliasing -pipe > NOPROFILE=true > COMPAT4X=true > KERNCONF= > > However, when I cd to (the NFS mounted) /usr/src on > machine A and enter ... > > --> shutdown --> > > make installkernel KERNCONF= > > ... the install fails. > > From what I can see, the program /usr/bin/install > core > dumps with exit status 4. Looking at the man page > for > install(1) it seems that there is an issue with > fchflags(2) over NFS. > > The questions are then, is my guess correct, and is > there a work around? > > Also, for info, I'm trying to install 5.4-RELEASE-P7 > onto A, while B has 5.4-RELEASE-p6 as it's kernel, > but > DOES have the FreeBSD-SA-05:20.cvsbug update. > > Any help gratefully received ... > > Thanks. > > PS. I did use machine B as the client and machine A > as the server, mounted and installed using DESTDIR, > but there were a whole lot of warnings about (I > think) > chflags which certainly didn't look right! > > > > > > ___ > > Yahoo! Messenger - NEW crystal clear PC to PC > calling worldwide with voicemail > http://uk.messenger.yahoo.com > ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
problem with 'make installkernel' over NFS on FreeBSD 5.4
Hi, I am in the process of trying to do an update of kernel and world on an old machine (machine A), using a newer, faster, machine (machine B). Machine B is set up as an NFS server for machine A. The /etc/exports file on machine B inculdes: /usr -maproot=root:0 -alldirs -network 192.168.0.0 -mask 255.255.255.0. Mahine A currently has address 192.168.0.197. Machine B has /usr mounted on a device, not, say, /usr/src. I have followed the following process. While logged onto machine B: cvsup /usr/src cd /usr/src make buildworld make buildkernel KERNCONF= Once this is complete, I then log onto machine A and mount /usr/src and /usr/obj via NFS. The /etc/fstab contains: 192.168.0.2:/usr/src /usr/src nfs ro,-i,noauto 192.168.0.2:/usr/obj /usr/obj nfs rw,-i,noauto (Machine B has 192.168.0.2 assigned to it's internal interface). The KERNCONF file is visible on machine A, and the /etc/make.conf files are pretty similar, speifically: CPUTYPE?=pentium CFLAGS= -O2 -fno-strict-aliasing -pipe COPTFLAGS= -O2 -fno-strict-aliasing -pipe NOPROFILE=true COMPAT4X=true KERNCONF= However, when I cd to (the NFS mounted) /usr/src on machine A and enter ... make installkernel KERNCONF= ... the install fails. >From what I can see, the program /usr/bin/install core dumps with exit status 4. Looking at the man page for install(1) it seems that there is an issue with fchflags(2) over NFS. The questions are then, is my guess correct, and is there a work around? Also, for info, I'm trying to install 5.4-RELEASE-P7 onto A, while B has 5.4-RELEASE-p6 as it's kernel, but DOES have the FreeBSD-SA-05:20.cvsbug update. Any help gratefully received ... Thanks. PS. I did use machine B as the client and machine A as the server, mounted and installed using DESTDIR, but there were a whole lot of warnings about (I think) chflags which certainly didn't look right! ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange problem with "make clean"
On Sat, 14 Jun 2003 00:06:50 +0300, Ruslan Ermilov wrote: >On Fri, Jun 13, 2003 at 03:59:06PM +0200, Alessandro de Manzano wrote: [...] >This means that either /usr/obj/usr/src/secure/usr.bin/openssl >or /usr/src/secure/usr.bin/openssl have the "openssl" file, >where it's supposed to be a directory in /usr/obj/... > >rm -r /usr/obj/usr/src/secure/usr.bin/openssl Great, it worked fine on all my machines :) >Note that "make clean" is only guaranteed to work if the >object tree was populated using this same sources; everything So I should have made at least a "buildworld" before ? >else is not guaranteed to work, and "make cleandir" is >advised instead, though even this may break when the types >of some files change from "file" to "directory", like has >happened with /usr/obj/usr/src/secure/usr.bin/openssl/openssl. good, well to know :) Many thanks again! Alessandro de Manzano Senior Network Manager Playstos - TIMA S.p.A. Corso Sempione 63 20149 Milano, Italy tel.: +39-023314153 fax: +39-02315678 email: [EMAIL PROTECTED] http://www.playstos.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange problem with "make clean"
On Sat, Jun 14, 2003 at 12:06:50AM +0300, Ruslan Ermilov wrote: > > Stop in /usr/src/secure/usr.bin/openssl. > > *** Error code 1 > > > This means that either /usr/obj/usr/src/secure/usr.bin/openssl > or /usr/src/secure/usr.bin/openssl have the "openssl" file, > where it's supposed to be a directory in /usr/obj/... ... > > rm -r /usr/obj/usr/src/secure/usr.bin/openssl Oh, I really did not think about it ! I should know that "make clean" would remove _object_ files, not source ! sigh! ;( Good, on next monday I'll try it ;) > Note that "make clean" is only guaranteed to work if the > object tree was populated using this same sources; everything > else is not guaranteed to work, and "make cleandir" is > advised instead, though even this may break when the types > of some files change from "file" to "directory", like has > happened with /usr/obj/usr/src/secure/usr.bin/openssl/openssl. ah ok. However my obj tree should have been correctly populated since I did a cvsup-build-install before trying clean. > Are you perhaps downgrading from 5.x? Nope, these are 4.0-rel binary-installed machines upgraded time after time via cvsup to 4.8 :-) (oh I really *love* FreeBSD for this :)) ) Many thanks for your answer! I'll try it and I'll report the result for the archives :-) -- bye! Ale [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange problem with "make clean"
On Fri, Jun 13, 2003 at 03:59:06PM +0200, Alessandro de Manzano wrote: > Hello, > > I'm experiencing a weird problem doing "make clean" in "/usr/src". > > It happens on a couple of FreeBSD 4.8-RELEASE machines (RELENG_4_8 to > be precise). > > Cvsup, build & install phases all went fine, just "make clean" went > wrong. > > I tried rm-ing the incriminated subdirectory and even rm-ing the > checkout.cvs:RELENG_4_8 file and re-cvsupping but nothing changes. > > > Here is the error log: > > [...] > rm -f telnet authenc.o commands.o main.o network.o ring.o sys_bsd.o > telnet.o terminal.o utilities.o telnet.1.gz telnet.1.cat.gz > ===> secure/usr.bin/openssl > rm -f buildinf.h openssl/opensslconf.h openssl/evp.h xopenssl > app_rand.o apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o > dhparam.o dsa.o dsaparam.o enc.o engine.o errstr.o gendh.o gendsa.o > genrsa.o nseq.o ocsp.o openssl.o passwd.o pkcs12.o pkcs7.o pkcs8.o > rand.o req.o rsa.o rsautl.o s_cb.o s_client.o s_server.o s_socket.o > s_time.o sess_id.o smime.o speed.o spkac.o verify.o version.o x509.o > CA.pl.1.gz asn1parse.1.gz ca.1.gz ciphers.1.gz crl.1.gz crl2pkcs7.1.gz > dgst.1.gz dhparam.1.gz dsa.1.gz dsaparam.1.gz enc.1.gz gendsa.1.gz > genrsa.1.gz nseq.1.gz ocsp.1.gz openssl.1.gz passwd.1.gz pkcs12.1.gz > pkcs7.1.gz pkcs8.1.gz rand.1.gz req.1.gz rsa.1.gz rsautl.1.gz > s_client.1.gz s_server.1.gz sess_id.1.gz smime.1.gz speed.1.gz > spkac.1.gz verify.1.gz version.1.gz x509.1.gz CA.pl.1.cat.gz > asn1parse.1.cat.gz ca.1.cat.gz ciphers.1.cat.gz crl.1.cat.gz > crl2pkcs7.1.cat.gz dgst.1.cat.gz dhparam.1.cat.gz dsa.1.cat.gz > dsaparam.1.cat.gz enc.1.cat.gz gendsa.1.cat.gz genrsa.1.cat.gz > nseq.1.cat.gz ocsp.1.cat.gz openssl.1.cat.gz passwd.1.cat.gz > pkcs12.1.cat.gz pkcs7.1.cat.gz pkcs8.1.cat.gz rand.1.cat.gz > req.1.cat.gz rsa.1.cat.gz rsautl.1.cat.gz s_client.1.cat.gz > s_server.1.cat.gz sess_id.1.cat.gz smime.1.cat.gz speed.1.cat.gz > spkac.1.cat.gz verify.1.cat.gz version.1.cat.gz x509.1.cat.gz > rm: openssl/opensslconf.h: Not a directory > rm: openssl/evp.h: Not a directory > *** Error code 1 > > Stop in /usr/src/secure/usr.bin/openssl. > *** Error code 1 > This means that either /usr/obj/usr/src/secure/usr.bin/openssl or /usr/src/secure/usr.bin/openssl have the "openssl" file, where it's supposed to be a directory in /usr/obj/... rm -r /usr/obj/usr/src/secure/usr.bin/openssl What "make clean" is trying to do is equivalent to trying to "rm /COPYRIGHT/foo". Note that "make clean" is only guaranteed to work if the object tree was populated using this same sources; everything else is not guaranteed to work, and "make cleandir" is advised instead, though even this may break when the types of some files change from "file" to "directory", like has happened with /usr/obj/usr/src/secure/usr.bin/openssl/openssl. Are you perhaps downgrading from 5.x? Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software Ltd, [EMAIL PROTECTED] FreeBSD committer pgp0.pgp Description: PGP signature
Strange problem with "make clean"
Hello, I'm experiencing a weird problem doing "make clean" in "/usr/src". It happens on a couple of FreeBSD 4.8-RELEASE machines (RELENG_4_8 to be precise). Cvsup, build & install phases all went fine, just "make clean" went wrong. I tried rm-ing the incriminated subdirectory and even rm-ing the checkout.cvs:RELENG_4_8 file and re-cvsupping but nothing changes. Here is the error log: [...] rm -f telnet authenc.o commands.o main.o network.o ring.o sys_bsd.o telnet.o terminal.o utilities.o telnet.1.gz telnet.1.cat.gz ===> secure/usr.bin/openssl rm -f buildinf.h openssl/opensslconf.h openssl/evp.h xopenssl app_rand.o apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o dhparam.o dsa.o dsaparam.o enc.o engine.o errstr.o gendh.o gendsa.o genrsa.o nseq.o ocsp.o openssl.o passwd.o pkcs12.o pkcs7.o pkcs8.o rand.o req.o rsa.o rsautl.o s_cb.o s_client.o s_server.o s_socket.o s_time.o sess_id.o smime.o speed.o spkac.o verify.o version.o x509.o CA.pl.1.gz asn1parse.1.gz ca.1.gz ciphers.1.gz crl.1.gz crl2pkcs7.1.gz dgst.1.gz dhparam.1.gz dsa.1.gz dsaparam.1.gz enc.1.gz gendsa.1.gz genrsa.1.gz nseq.1.gz ocsp.1.gz openssl.1.gz passwd.1.gz pkcs12.1.gz pkcs7.1.gz pkcs8.1.gz rand.1.gz req.1.gz rsa.1.gz rsautl.1.gz s_client.1.gz s_server.1.gz sess_id.1.gz smime.1.gz speed.1.gz spkac.1.gz verify.1.gz version.1.gz x509.1.gz CA.pl.1.cat.gz asn1parse.1.cat.gz ca.1.cat.gz ciphers.1.cat.gz crl.1.cat.gz crl2pkcs7.1.cat.gz dgst.1.cat.gz dhparam.1.cat.gz dsa.1.cat.gz dsaparam.1.cat.gz enc.1.cat.gz gendsa.1.cat.gz genrsa.1.cat.gz nseq.1.cat.gz ocsp.1.cat.gz openssl.1.cat.gz passwd.1.cat.gz pkcs12.1.cat.gz pkcs7.1.cat.gz pkcs8.1.cat.gz rand.1.cat.gz req.1.cat.gz rsa.1.cat.gz rsautl.1.cat.gz s_client.1.cat.gz s_server.1.cat.gz sess_id.1.cat.gz smime.1.cat.gz speed.1.cat.gz spkac.1.cat.gz verify.1.cat.gz version.1.cat.gz x509.1.cat.gz rm: openssl/opensslconf.h: Not a directory rm: openssl/evp.h: Not a directory *** Error code 1 Stop in /usr/src/secure/usr.bin/openssl. *** Error code 1 Stop in /usr/src/secure/usr.bin. *** Error code 1 Stop in /usr/src/secure. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Note that those files really does not exists.. Any hints and suggestions are really welcome! :-) Many thanks in advance! Alessandro de Manzano Senior Network Manager Playstos - TIMA S.p.A. Corso Sempione 63 20149 Milano, Italy tel.: +39-023314153 fax: +39-02315678 email: [EMAIL PROTECTED] http://www.playstos.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problem with "make installworld"
I got a problem with "make installworld" upgrading from 4.4 Release to 4.6.2 Release. "make buildworld" and compiling a new kernel worked fine, but installing world doesn't work. I always get the following error: install -c -o root -g wheel -m 444 /usr/src/share/termcap/map3270 /usr/share/misc/map3270 TERM=dumb ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder ex: not found *** Error code 127 Stop in /usr/src/share/termcap. *** Error code 1 [ ... ] Would it help if I'd compile ex manually? - Moritz To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
