Re: make installworld fails
Caleb Stein caleb.st...@me.com writes: I am trying to update my FreeBSD 8.0 to FreeBSD 8.1. Here is the order I ran the commands in (all as root): cd /usr/src make buildworld make buildkernel shutdown now make installkernel shutdown -r now adjkerntz -i mount -a -t ufs mergemaster -p cd /usr/src make installworld mergemaster reboot But I didn't get to run the last two. When I run make installworld, I get errors telling me that the filesystem is full. Now, I can assure you it is not. Well, basically, what I am asking is why is the filesystem full after installing the new kernel? The number of kernel modules has been increasing quite quickly, and modules are installed with the kernel (by default). This has led to installkernel filling up the root filesystem increasingly often. It just happened to me yesterday, although in that case snapshots and four or five old kernels were part of the problem. Are you *sure* that the filesystem isn't full? Can you show df(1) output? ___ 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: make installworld fails
On Aug 2, 2010, at 7:34 AM, Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org wrote: Caleb Stein caleb.st...@me.com writes: I am trying to update my FreeBSD 8.0 to FreeBSD 8.1. Here is the order I ran the commands in (all as root): cd /usr/src make buildworld make buildkernel shutdown now make installkernel shutdown -r now adjkerntz -i mount -a -t ufs mergemaster -p cd /usr/src make installworld mergemaster reboot But I didn't get to run the last two. When I run make installworld, I get errors telling me that the filesystem is full. Now, I can assure you it is not. Well, basically, what I am asking is why is the filesystem full after installing the new kernel? The number of kernel modules has been increasing quite quickly, and modules are installed with the kernel (by default). This has led to installkernel filling up the root filesystem increasingly often. It just happened to me yesterday, although in that case snapshots and four or five old kernels were part of the problem. Are you *sure* that the filesystem isn't full? Can you show df(1) output? ___ 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 was wrong, the filesystem was full. I did delete the old kernel modules though, and that fixed the issue. ___ 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: make installworld fails
Am Montag, den 02.08.2010, 08:24 -0700 schrieb Caleb Stein: On Aug 2, 2010, at 7:34 AM, Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org wrote: Caleb Stein caleb.st...@me.com writes: I am trying to update my FreeBSD 8.0 to FreeBSD 8.1. Here is the order I ran the commands in (all as root): cd /usr/src make buildworld make buildkernel shutdown now make installkernel shutdown -r now adjkerntz -i mount -a -t ufs mergemaster -p cd /usr/src make installworld mergemaster reboot But I didn't get to run the last two. When I run make installworld, I get errors telling me that the filesystem is full. Now, I can assure you it is not. Well, basically, what I am asking is why is the filesystem full after installing the new kernel? The number of kernel modules has been increasing quite quickly, and modules are installed with the kernel (by default). This has led to installkernel filling up the root filesystem increasingly often. It just happened to me yesterday, although in that case snapshots and four or five old kernels were part of the problem. Are you *sure* that the filesystem isn't full? Can you show df(1) output? ___ 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 was wrong, the filesystem was full. I did delete the old kernel modules though, and that fixed the issue. This might not be a good idea since you might need your old kernel to boot from if anything went wrong with the new one. Probably you built your kernel with debugging symbols turned on, which will make it _much_ bigger (and slower!) Put the following line into your /etc/make.conf INSTALL_NODEBUG=yes and try again. Greetings Peter. ___ 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
make installworld fails
I am trying to update my FreeBSD 8.0 to FreeBSD 8.1. Here is the order I ran the commands in (all as root): cd /usr/src make buildworld make buildkernel shutdown now make installkernel shutdown -r now adjkerntz -i mount -a -t ufs mergemaster -p cd /usr/src make installworld mergemaster reboot But I didn't get to run the last two. When I run make installworld, I get errors telling me that the filesystem is full. Now, I can assure you it is not. Well, basically, what I am asking is why is the filesystem full after installing the new kernel? ___ 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: make installworld fails
--- On Sun, 8/1/10, Caleb Stein caleb.st...@me.com wrote: From: Caleb Stein caleb.st...@me.com Subject: make installworld fails To: freebsd-questions@freebsd.org freebsd-questions@freebsd.org Date: Sunday, August 1, 2010, 9:43 PM I am trying to update my FreeBSD 8.0 to FreeBSD 8.1. Here is the order I ran the commands in (all as root): cd /usr/src make buildworld make buildkernel shutdown now make installkernel shutdown -r now adjkerntz -i mount -a -t ufs mergemaster -p cd /usr/src make installworld mergemaster reboot But I didn't get to run the last two. When I run make installworld, I get errors telling me that the filesystem is full. Now, I can assure you it is not. Well, basically, what I am asking is why is the filesystem full after installing the new kernel? You are supposed to make installkernel before rebooting to single user. ___ 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: make installworld fails on RELEASE6.4 amd64
I am facing a problem that I cannot solve when trying to reinstall wolrd on 6.4 amd 64. More about this issue. Regarding adjkerntz -i. Places that are ahead of UTC don't need to do the adjkerntz -i after rebooting in single user. Suppose you are in a time zone at UTC +7. Boot in multiuser: Wall clock=7:00 CMOS clock=7:00 TZ time= 7:00 UTC= 0:00 From 7:00 to 7:30 you build world, file created will have a creation date of 0:00 to 0:30 UTC. Reboot in single user: Wall clock=7:30 CMOS clock=7:30 UTC= 7:30 (no adjkerntz) Make install world, the install will be done with a UTC at 7:30, that is after the build time of 0:00 to 0:30. Reboot in multiuser: Wall clock=7:45 CMOS clock=7:45 TZ time= 7:45 UTC= 0:45 Now if you look at the newly installed world, it will be in the future, ahead by 7 hours: a file installed at 7:35 will be listed with a time of 14:35. That is odd, but it works. Hence country ahead of UTC don't need adjkerntz -i Bests, Olivier ___ 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: make installworld fails on RELEASE6.4 amd64
On Tue, 17 Mar 2009 13:05:17 +0700 (ICT) Olivier Nicole o...@cs.ait.ac.th wrote: I am facing a problem that I cannot solve when trying to reinstall wolrd on 6.4 amd 64. More about this issue. Regarding adjkerntz -i. Places that are ahead of UTC don't need to do the adjkerntz -i after rebooting in single user. That's certainly not my experiance here (UTC+11 currently). That got well burnt into my brain after y2k with FreeBSD 2.2.6, having to patch /etc/rc (on advice) to deal with a BIOS that thought 2000 was 1994 :) Suppose you are in a time zone at UTC +7. Boot in multiuser: Wall clock=7:00 CMOS clock=7:00 TZ time= 7:00 UTC= 0:00 Right. It appears that /etc/wall_cmos_clock exists there, yes? From 7:00 to 7:30 you build world, file created will have a creation date of 0:00 to 0:30 UTC. Well yes as UTC, but with wall_cmos_clock everything will show these files as local time (07:xx), just as any other files created multiuser. Reboot in single user: Wall clock=7:30 CMOS clock=7:30 UTC= 7:30 (no adjkerntz) That's exactly WHY you want to run adjkerntz -i then, before anything that creates files is run, ie mergemaster, installworld .. but it only makes any difference if /etc/wall_cmos_clock does exist then of course. So if you'd run adjkerntz -i, times would show the same as in multiuser. Make install world, the install will be done with a UTC at 7:30, that is after the build time of 0:00 to 0:30. Reboot in multiuser: Wall clock=7:45 CMOS clock=7:45 TZ time= 7:45 UTC= 0:45 Now if you look at the newly installed world, it will be in the future, ahead by 7 hours: a file installed at 7:35 will be listed with a time of 14:35. That is odd, but it works. Sorta works, if you don't mind file (and log) timestamps not reflecting reality. I'm fussy about chronology. And then there's that 7 hour wait until those files become dated in the past, and so can be 'updated'. Hence country ahead of UTC don't need adjkerntz -i Sorry, but this demonstrates exactly why you DO need to run that when (ever) working single user, if you want file/log datestamps consistent. I can't comment on i386/amd64 differences, but it's necessary on i386. cheers, Ian ___ 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: make installworld fails on RELEASE6.4 amd64
Hi, I am facing a problem that I cannot solve when trying to reinstall wolrd on 6.4 amd 64. More about this issue. RELEASE_6.4 i386 is imune of this problem. I did a make -d A installworld and it seems that it is all about /usr/obj/usr/src/sys/boot/i386/boot2/machine. It's a link to /usr/src/sys/i386/include. This directory is created at the first installation of FreeBSD. When CMOS clock is the wall clock and when one is located ahead of UTC (Thailand is UTC+7), during the first installation of a distribution, the machine boots with UTC=CMOS clock, hence creating the directory hierarchy 7 hours ahead of time. The link /usr/obj/usr/src/sys/boot/i386/boot2/machine is created by make buildworld, after the first boot of the newly installed system, after the time zone has been set, so it is created with the right time. If one does an installworld between the 7 hours interval, when installing /usr/src/sys/boot/i386/boot2, it detects that the directory /usr/src/sys/i386/include pointed by /usr/obj/usr/src/sys/boot/i386/boot2/machine is newer than the objects being installed, and it tries to rebuild the object. My wild guess is that on i386, make installworld looks at the modification date of the link /usr/obj/usr/src/sys/boot/i386/boot2/machine; while on amd64 make installworld looks at the modification date of the directory /usr/src/sys/i386/include pointed by the link. Hence the different behaviour. This is annoying for people leaving ahead of UTC, that will install a new distribution, cvsup the release, build and installworld, during the interval of 7 hours. I think that users behing UTC will not be affected. What I did is: during the installation of the distrubition I set back the CMOS clock to UTC time, and when FreeBSD was done installing from the CD, I reset the CMOS clock to the wall clock. It worked, but it's not very nice. I am curious to have experts opinion on the different behaviour of make regarding the modification date of the link /usr/obj/usr/src/sys/boot/i386/boot2/machine. Best regards, Olivier ___ 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: make installworld fails on RELEASE6.4 amd64
On Sunday 15 March 2009 01:31:24 am Olivier Nicole wrote: Hi, I am facing a problem that I cannot solve when trying to reinstall wolrd on 6.4 amd 64. More about this issue. RELEASE_6.4 i386 is imune of this problem. I did a make -d A installworld and it seems that it is all about /usr/obj/usr/src/sys/boot/i386/boot2/machine. It's a link to /usr/src/sys/i386/include. This directory is created at the first installation of FreeBSD. When CMOS clock is the wall clock and when one is located ahead of UTC (Thailand is UTC+7), during the first installation of a distribution, the machine boots with UTC=CMOS clock, hence creating the directory hierarchy 7 hours ahead of time. The link /usr/obj/usr/src/sys/boot/i386/boot2/machine is created by make buildworld, after the first boot of the newly installed system, after the time zone has been set, so it is created with the right time. If one does an installworld between the 7 hours interval, when installing /usr/src/sys/boot/i386/boot2, it detects that the directory /usr/src/sys/i386/include pointed by /usr/obj/usr/src/sys/boot/i386/boot2/machine is newer than the objects being installed, and it tries to rebuild the object. My wild guess is that on i386, make installworld looks at the modification date of the link /usr/obj/usr/src/sys/boot/i386/boot2/machine; while on amd64 make installworld looks at the modification date of the directory /usr/src/sys/i386/include pointed by the link. Hence the different behaviour. This is annoying for people leaving ahead of UTC, that will install a new distribution, cvsup the release, build and installworld, during the interval of 7 hours. I think that users behing UTC will not be affected. What I did is: during the installation of the distrubition I set back the CMOS clock to UTC time, and when FreeBSD was done installing from the CD, I reset the CMOS clock to the wall clock. It worked, but it's not very nice. What you did is not necessary if you adjkerntz -i when you boot to single user mode. I am curious to have experts opinion on the different behaviour of make regarding the modification date of the link /usr/obj/usr/src/sys/boot/i386/boot2/machine. Best regards, Olivier ___ 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 -- kent Stewart Richland, WA http://users.owt.com/kstewart/index.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: make installworld fails on RELEASE6.4 amd64
Hi, What I did is: during the installation of the distrubition I set back the CMOS clock to UTC time, and when FreeBSD was done installing from the CD, I reset the CMOS clock to the wall clock. It worked, but it's not very nice. What you did is not necessary if you adjkerntz -i when you boot to single user mode. Sorry, but wrong. I did adjkerntz -i when booting in single user mode; beleive me, I spent 2 days installing from CD and trying to buildworld/installworld in many various ways. But it did not help (never needed it with i386 though) because at the very first install from CD, there is no time zone defined so all the directory structure of /usr/src appeared to be 7 hours ahead of the installation. Best regards, Olivier ___ 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
make installworld fails on RELEASE6.4 amd64
-- 1 root wheel 8192 Mar 14 15:39 boot after the buildworld the date is: Sat Mar 14 16:05:57 ICT 2009 - Reboot as single user after reboot as single user the date is: Sat Mar 14 23:11:02 ICT 2009 Sat Mar 14 16:11:02 UTC 2009 - Adjkerntz -i after adjkerntz -i the date is: Sat Mar 14 16:11:23 ICT 2009 Sat Mar 14 09:11:23 UTC 2009 -- Make installworld: I checked that the files used to make boot2.s are not changing: /usr/src/sys/boot/common/ufsread.c /usr/src/sys/boot/i386/boot2/boot2.c /usr/obj//usr/src/sys/boot/i386/boot2/boot2.h make install produces the following output: === sys/boot/i386/boot2 (install) cc -Os -fno-guess-branch-probability -fomit-frame-pointer -fno-unit-at-a-time -mno-align-long-strings -mrtd -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -DUFS1_AND_UFS2 -DFLAGS=0x80 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/src/sys/boot/i386/boot2/../../common -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -m32 -march=i386 -S -o boot2.s.tmp /usr/src/sys/boot/i386/boot2/boot2.c sed -e '/align/d' -e '/nop/d' boot2.s.tmp boot2.s rm -f boot2.s.tmp as --32 -o boot2.o boot2.s Note: it does not try to rebuild sio.o ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 -o boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o sio.o objcopy -S -O binary boot2.out boot2.bin btxld -v -E 0x2000 -f bin -b /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin btxld:No such file or directory after make installworld fails, the directory /usr/obj/usr/src/sys/boot/i386/boot2 contains: total 188 lrwxr-xr-x 1 root wheel 50 Mar 14 15:26 machine - /usr/src/sys/boot/i386/boot2/../../../i386/include -rw-r--r-- 1 root wheel 23 Mar 14 15:26 boot2.h -rwxr-xr-x 1 root wheel 2345 Mar 14 15:26 boot1.out -rw-r--r-- 1 root wheel 2316 Mar 14 15:26 boot1.o -rw-r--r-- 1 root wheel 2056 Mar 14 15:26 .depend -rw-r--r-- 1 root wheel 1028 Mar 14 15:39 sio.o -rw-r--r-- 1 root wheel276 Mar 14 15:39 boot2.ldr -rw-r--r-- 1 root wheel 7309 Mar 14 15:39 boot2.ld -rw-r--r-- 1 root wheel 7680 Mar 14 15:39 boot2 -rwxr-xr-x 1 root wheel512 Mar 14 15:39 boot1 -rw-r--r-- 1 root wheel 8192 Mar 14 15:39 boot -rw-r--r-- 1 root wheel 26549 Mar 14 16:14 boot2.s -rwxr-xr-x 1 root wheel 8059 Mar 14 16:14 boot2.out -rw-r--r-- 1 root wheel 9080 Mar 14 16:14 boot2.o -rwxr-xr-x 1 root wheel 5369 Mar 14 16:14 boot2.bin --- TIA Olivier ___ 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: make installworld fails
Valentin Bud wrote: Hello, This are the parts from /etc/make.conf regarding system build options: # --- system build options WITHOUT_IPFILTER=yes WITHOUT_IPX=yes WITHOUT_LPR=yes WITHOUT_RCMDS=yes WITHOUT_SENDMAIL=yes I didn't give any arguments to # make buildworld or # make installworld I have ran them as i've typed them above. Is there something wrong in /etc/make.conf ? I should make sure it's mentioned -- FreeBSD 7.x started an /etc/src.conf that are the knobs for FreeBSD world ONLY. This leaves /etc/make.conf available for ports ONLY. I'd update your files, because there's a possibility your WITHOUT_ statements were ignored. --Tim ___ 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: make installworld fails
On Sun, 08 Feb 2009 01:45:59 -0700, Tim Judd taj...@gmail.com wrote: I should make sure it's mentioned -- FreeBSD 7.x started an /etc/src.conf that are the knobs for FreeBSD world ONLY. This leaves /etc/make.conf available for ports ONLY. I'd update your files, because there's a possibility your WITHOUT_ statements were ignored. IIRC, src.conf works in _addition_ to make.conf so having options in either one should be safe I think. The advice of keeping options cleanly separated is very sound though, to avoid confusion when these two files have conflicting options :-) ___ 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: make installworld fails
On Sun, Feb 8, 2009 at 10:45 AM, Tim Judd taj...@gmail.com wrote: Valentin Bud wrote: Hello, This are the parts from /etc/make.conf regarding system build options: # --- system build options WITHOUT_IPFILTER=yes WITHOUT_IPX=yes WITHOUT_LPR=yes WITHOUT_RCMDS=yes WITHOUT_SENDMAIL=yes I didn't give any arguments to # make buildworld or # make installworld I have ran them as i've typed them above. Is there something wrong in /etc/make.conf ? I should make sure it's mentioned -- FreeBSD 7.x started an /etc/src.conf that are the knobs for FreeBSD world ONLY. This leaves /etc/make.conf available for ports ONLY. I'd update your files, because there's a possibility your WITHOUT_ statements were ignored. Thanks for the heads up. I will start right away to move and organize these files. :) a great day, v --Tim ___ 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
make installworld fails
elo list, just updated a newly installed freebsd 7.1 system and it crashed here: === rescue (install) === rescue/librescue (install) === rescue/rescue (install) install -s -o root -g wheel -m 555 rescue /rescue install: rescue: No such file or directory *** Error code 71 Stop in /usr/src/rescue/rescue. *** Error code 1 Stop in /usr/src/rescue. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 I have updated the sources using the csup method then # make buildkernel KERNCONF=CUSTOMISED # make installkernel KERNCONF=CUSTOMISED # mergemaster -p reboot #make installworld # uname -a FreeBSD server.xxx.com 7.1-RELEASE-p2 FreeBSD 7.1-RELEASE-p2 #0: Sat Feb 7 15:47:11 EET 2009 # ls -al / output omitted for brevity ... drwxr-xr-x 2 root wheel 2560 Feb 7 14:54 rescue # ls -al /usr/src/rescue total 12 drwxr-xr-x 4 root wheel 512 Feb 7 13:45 . drwxr-xr-x 22 root wheel 512 Feb 7 13:50 .. -rw-r--r-- 1 root wheel 133 Nov 25 04:59 Makefile -rw-r--r-- 1 root wheel 1603 Nov 25 04:59 README drwxr-xr-x 2 root wheel 512 Feb 7 13:45 librescue drwxr-xr-x 2 root wheel 512 Feb 7 13:45 rescue Now the question is what can i do next? thanks, v ___ 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: make installworld fails
Valentin Bud said: elo list, just updated a newly installed freebsd 7.1 system and it crashed here: === rescue (install) === rescue/librescue (install) === rescue/rescue (install) install -s -o root -g wheel -m 555 rescue /rescue install: rescue: No such file or directory *** Error code 71 Stop in /usr/src/rescue/rescue. *** Error code 1 Stop in /usr/src/rescue. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 I have updated the sources using the csup method then # make buildkernel KERNCONF=CUSTOMISED # make installkernel KERNCONF=CUSTOMISED # mergemaster -p reboot #make installworld Was this during buildworld or installworld? # uname -a FreeBSD server.xxx.com 7.1-RELEASE-p2 FreeBSD 7.1-RELEASE-p2 #0: Sat Feb 7 15:47:11 EET 2009 # ls -al / output omitted for brevity ... drwxr-xr-x 2 root wheel 2560 Feb 7 14:54 rescue # ls -al /usr/src/rescue total 12 drwxr-xr-x 4 root wheel 512 Feb 7 13:45 . drwxr-xr-x 22 root wheel 512 Feb 7 13:50 .. -rw-r--r-- 1 root wheel 133 Nov 25 04:59 Makefile -rw-r--r-- 1 root wheel 1603 Nov 25 04:59 README drwxr-xr-x 2 root wheel 512 Feb 7 13:45 librescue drwxr-xr-x 2 root wheel 512 Feb 7 13:45 rescue Now the question is what can i do next? What does `ls -al /rescue' show? Regards, -- Glen Barber ___ 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: make installworld fails
On Sat, 7 Feb 2009 17:52:09 +0200, Valentin Bud valentin@gmail.com wrote: elo list, just updated a newly installed freebsd 7.1 system and it crashed here: === rescue (install) === rescue/librescue (install) === rescue/rescue (install) install -s -o root -g wheel -m 555 rescue /rescue install: rescue: No such file or directory *** Error code 71 Stop in /usr/src/rescue/rescue. *** Error code 1 You seem to have built only parts of the source tree, i.e. because you completed a buildworld cycle when WITHOUT_RESCUE was defined. Try repeating the buildworld and installworld steps with exactly the *same* options in their environment. ___ 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: make installworld fails
Hello, This are the parts from /etc/make.conf regarding system build options: # --- system build options WITHOUT_IPFILTER=yes WITHOUT_IPX=yes WITHOUT_LPR=yes WITHOUT_RCMDS=yes WITHOUT_SENDMAIL=yes I didn't give any arguments to # make buildworld or # make installworld I have ran them as i've typed them above. Is there something wrong in /etc/make.conf ? thanks, v On Sat, Feb 7, 2009 at 6:05 PM, Giorgos Keramidas keram...@ceid.upatras.grwrote: On Sat, 7 Feb 2009 17:52:09 +0200, Valentin Bud valentin@gmail.com wrote: elo list, just updated a newly installed freebsd 7.1 system and it crashed here: === rescue (install) === rescue/librescue (install) === rescue/rescue (install) install -s -o root -g wheel -m 555 rescue /rescue install: rescue: No such file or directory *** Error code 71 Stop in /usr/src/rescue/rescue. *** Error code 1 You seem to have built only parts of the source tree, i.e. because you completed a buildworld cycle when WITHOUT_RESCUE was defined. Try repeating the buildworld and installworld steps with exactly the *same* options in their environment. ___ 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: make installworld fails
Hello Glen, During installworld. # ls -al /rescue total 451106 drwxr-xr-x2 root wheel 2560 Feb 7 14:54 . drwxr-xr-x 21 root wheel 512 Feb 7 16:17 .. -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 [ -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 atacontrol -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 atmconfig -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 badsect -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 bsdlabel -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 bunzip2 -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 bzcat -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 bzip2 -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 camcontrol -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 cat -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 ccdconfig -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 chflags -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 chio -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 chmod -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 chroot -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 clri -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 cp -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 csh -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 date -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 dd -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 devfs -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 df -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 dhclient -r-xr-xr-x1 root wheel 9478 Jan 1 13:51 dhclient-script -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 disklabel -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 dmesg -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 dump -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 dumpfs -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 dumpon -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 echo -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 ed -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 ex -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 expr -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 fastboot -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 fasthalt -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 fdisk -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 fsck -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 fsck_4.2bsd -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 fsck_ffs -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 fsck_msdosfs -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 fsck_ufs -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 fsdb -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 fsirand -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 gbde -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 getfacl -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 groups -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 gunzip -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 gzcat -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 gzip -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 halt -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 hostname -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 id -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 ifconfig -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 init -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 ipf -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 kenv -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 kill -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 kldconfig -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 kldload -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 kldstat -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 kldunload -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 ldconfig -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 link -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 ln -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 ls -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 md5 -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 mdconfig -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 mdmfs -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 mkdir -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 mknod -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 mount -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 mount_cd9660 -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 mount_msdosfs -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 mount_nfs -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 mount_ntfs -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 mount_nullfs -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 mount_udf -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 mount_unionfs -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 mv -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 newfs -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 newfs_msdos -r-xr-xr-x1 root wheel 910 Jan 1 13:51 nextboot -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 nos-tun -r-xr-xr-x 121 root wheel 3793072 Jan 1 13:51 pax -r-xr-xr-x 121 root
Re: make installworld fails
On Sat, 7 Feb 2009 17:52:09 +0200, Valentin Bud valentin@gmail.com wrote: elo list, just updated a newly installed freebsd 7.1 system and it crashed here: === rescue (install) === rescue/librescue (install) === rescue/rescue (install) install -s -o root -g wheel -m 555 rescue /rescue install: rescue: No such file or directory *** Error code 71 Stop in /usr/src/rescue/rescue. *** Error code 1 On Sat, 7 Feb 2009 18:10:51 +0200, Valentin Bud valentin@gmail.com wrote: Hello, This are the parts from /etc/make.conf regarding system build options: # --- system build options WITHOUT_IPFILTER=yes WITHOUT_IPX=yes WITHOUT_LPR=yes WITHOUT_RCMDS=yes WITHOUT_SENDMAIL=yes I didn't give any arguments to # make buildworld or # make installworld I have ran them as i've typed them above. Is there something wrong in /etc/make.conf ? These options don't seem to affect the build of `/usr/src/rescue'. Can you try running the build commands once more in that directory? # cd /usr/src/rescue # make cleandir ; make cleandir # make obj depend all Then it should be possible to install the newly built /rescue binaries, and your installworld should complete fine. ___ 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: make installworld fails
On Sat, Feb 7, 2009 at 6:16 PM, Giorgos Keramidas keram...@ceid.upatras.grwrote: On Sat, 7 Feb 2009 17:52:09 +0200, Valentin Bud valentin@gmail.com wrote: elo list, just updated a newly installed freebsd 7.1 system and it crashed here: === rescue (install) === rescue/librescue (install) === rescue/rescue (install) install -s -o root -g wheel -m 555 rescue /rescue install: rescue: No such file or directory *** Error code 71 Stop in /usr/src/rescue/rescue. *** Error code 1 On Sat, 7 Feb 2009 18:10:51 +0200, Valentin Bud valentin@gmail.com wrote: Hello, This are the parts from /etc/make.conf regarding system build options: # --- system build options WITHOUT_IPFILTER=yes WITHOUT_IPX=yes WITHOUT_LPR=yes WITHOUT_RCMDS=yes WITHOUT_SENDMAIL=yes I didn't give any arguments to # make buildworld or # make installworld I have ran them as i've typed them above. Is there something wrong in /etc/make.conf ? These options don't seem to affect the build of `/usr/src/rescue'. Can you try running the build commands once more in that directory? # cd /usr/src/rescue # make cleandir ; make cleandir # make obj depend all Then it should be possible to install the newly built /rescue binaries, and your installworld should complete fine. Hello Giorgios, Thanks that worked and the installworld succeeded. Is this a bug? Should i report it? thanks, v ___ 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: make installworld fails
On Sat, 7 Feb 2009 19:19:09 +0200, Valentin Bud valentin@gmail.com wrote: On Sat, Feb 7, 2009 at 6:16 PM, Giorgos Keramidas keram...@ceid.upatras.grwrote: # --- system build options WITHOUT_IPFILTER=yes WITHOUT_IPX=yes WITHOUT_LPR=yes WITHOUT_RCMDS=yes WITHOUT_SENDMAIL=yes I didn't give any arguments to # make buildworld or # make installworld I have ran them as i've typed them above. Is there something wrong in /etc/make.conf ? These options don't seem to affect the build of `/usr/src/rescue'. Can you try running the build commands once more in that directory? # cd /usr/src/rescue # make cleandir ; make cleandir # make obj depend all Then it should be possible to install the newly built /rescue binaries, and your installworld should complete fine. Hello Giorgios, Thanks that worked and the installworld succeeded. Is this a bug? Should i report it? No, that's ok. You somehow managed to botch 'buildworld'. Now that the missing bits are in /usr/obj all is fine. If you start with a *clean* /usr/obj tree and the problem reappears, then please let us know :) ___ 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: make installworld fails
On Sat, Feb 7, 2009 at 7:51 PM, Giorgos Keramidas keram...@ceid.upatras.grwrote: On Sat, 7 Feb 2009 19:19:09 +0200, Valentin Bud valentin@gmail.com wrote: On Sat, Feb 7, 2009 at 6:16 PM, Giorgos Keramidas keram...@ceid.upatras.grwrote: # --- system build options WITHOUT_IPFILTER=yes WITHOUT_IPX=yes WITHOUT_LPR=yes WITHOUT_RCMDS=yes WITHOUT_SENDMAIL=yes I didn't give any arguments to # make buildworld or # make installworld I have ran them as i've typed them above. Is there something wrong in /etc/make.conf ? These options don't seem to affect the build of `/usr/src/rescue'. Can you try running the build commands once more in that directory? # cd /usr/src/rescue # make cleandir ; make cleandir # make obj depend all Then it should be possible to install the newly built /rescue binaries, and your installworld should complete fine. Hello Giorgios, Thanks that worked and the installworld succeeded. Is this a bug? Should i report it? No, that's ok. You somehow managed to botch 'buildworld'. Now that the missing bits are in /usr/obj all is fine. If you start with a *clean* /usr/obj tree and the problem reappears, then please let us know :) Ok, sure do. :) thanks once again, v ___ 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
help, make installworld fails!!!!!!
Gents, I'm about to experience the first problem with FreeBSD after I've tried to upgrade my kernel to the latest sources because of the security advisories. I have a custom kernel running FreeBSD version 6.2 on a amd64 system. My procedure was: step 1) change the src-supfile file to get the version of freebsd you want step 2) Change file /usr/src/sys/amd64/conf/MYKERNEL to get the kernel options you want step 3) cp /usr/src/sys/amd64/conf/MYKERNEL /root/kernels/MYKERNEL (make a backup of the kernel configuration in a seperate directory) step 4) cvsup -g -L 2 src-supfile (check if MYKERNEL is still in /usr/src/sys/amd64/conf directory otherwise copy from /root/kernels directory) step 5) shutdown now and go into single user mode step 6) look at step 11 step 7) cd /usr/src and make buildworld step 8) make buildkernel KERNCONF=MYKERNEL step 9) make installkernel KERNCONF=MYKERNEL step 10) reboot into single user mode step 11) Then, when the system starts a /bin/sh shell instance, type: # adjkerntz -i # fsck -p # mount -u / # mount -a step 12) cd /usr/src step 13) mergemaster -p (pre buildworld mode, look into /usr/src/UPDATING to check if you have to do this before step 7!!) step 14) make installworld step 15) mergemaster -i step 16) exit and reboot *** However, at step 14 I ran out of luck as I got the following error: mkdir -p /tmp/install.gurnx5I7 for prog in [ awk cap_mkdb cat chflags chmod chown date echo egrep find grep install-info ln lockf make mkdir mtree mv pwd_mkdb rm sed sh sysctl test true uname wc zic; do cp `which $prog` /tmp/install.gurnx5I7; done cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=amd64 MACHINE=amd64 CPUTYPE= GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/tmp/install.gurnx5I7 make -f Makefile.inc1 reinstall -- Making hierarchy -- cd /usr/src; make -f Makefile.inc1 hierarchy cd /usr/src/etc;make distrib-dirs mtree -eU -f /usr/src/etc/mtree/BSD.root.dist -p / mtree -eU -f /usr/src/etc/mtree/BSD.var.dist -p /var mtree -eU -f /usr/src/etc/mtree/BSD.usr.dist -p /usr mtree -eU -f /usr/src/etc/mtree/BSD.include.dist -p /usr/include mtree -deU -f /usr/src/etc/mtree/BIND.chroot.dist -p /var/named mtree -deU -f /usr/src/etc/mtree/BSD.sendmail.dist -p / cd /; rm -f /sys; ln -s usr/src/sys sys cd /usr/share/man/en.ISO8859-1; ln -sf ../man* . cd /usr/share/man; set - `grep ^[a-zA-Z] /usr/src/etc/man.alias`; while [ $# -gt 0 ] ; do rm -rf $1; ln -s $2 $1; shift; shift; done cd /usr/share/openssl/man; set - `grep ^[a-zA-Z] /usr/src/etc/man.alias`; while [ $# -gt 0 ] ; do rm -rf $1; ln -s $2 $1; shift; shift; done cd /usr/share/openssl/man/en.ISO8859-1; ln -sf ../man* . cd /usr/share/nls; set - `grep ^[a-zA-Z] /usr/src/etc/nls.alias`; while [ $# -gt 0 ] ; do rm -rf $1; ln -s $2 $1; shift; shift; done -- Installing everything -- cd /usr/src; make -f Makefile.inc1 install === share/info (install) === include (install) creating osreldate.h from newvers.sh touch: not found *** Error code 127 Stop in /usr/src/include. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. So what do I have to do now? How do I proceed next? Hope somebody can help me out, thanks Dino - Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: help, make installworld fails!!
I pay less attention to e-mail messages with lots of exclamation points in the subject (because they're usually spam). You might want to consider that in the future... Dino Vliet [EMAIL PROTECTED] writes: === include (install) creating osreldate.h from newvers.sh touch: not found Try looking at the FreeBSD FAQ entry entitled 'Why does buildworld/installworld die with the message touch: not found?'. You can find that entry at: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#TOUCH-NOT-FOUND [briefly: it's usually a sign that your clocks are off] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: help, make installworld fails!!!!!!
On Sunday 07 October 2007, Dino Vliet wrote: Gents, snip Installing everything -- cd /usr/src; make -f Makefile.inc1 install === share/info (install) === include (install) creating osreldate.h from newvers.sh touch: not found *** Error code 127 Stop in /usr/src/include. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. So what do I have to do now? How do I proceed next? Hope somebody can help me out, Set your system clock to the right time. The only reason make tries to touch anything is when it thinks something needs to be redone. This means something in your source is newer than what it created in the buildworld phase. Kent thanks Dino - Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Kent Stewart Richland, WA http://www.soyandina.com/ I am Andean project. http://users.owt.com/kstewart/index.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make installworld fails error 126
Hello All, I have always had this problem on the one or two (web) servers that I have a separate /tmp partition defined. I found the answer a long time ago to unmount /tmp and try again and that always works.. but I've never found a way to make installworld with a separate /tmp partition on my systems. Is there a way? Is it something I'm doing? Is it the nosuid? or noexec? Can I tell installworld to use /var/tmp instead? ..etc.. Ultimately I am looking to be able to 'make installworld' like I do on my other boxes.. if I need something in /etc/make.conf to tell it not to use /tmp what is it.. b/c I've not found it.. [~]$ 2 grep tmp /etc/fstab /dev/ad0s1f /tmpufs rw,nosuid,noexec2 2 Thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails error 126
B. Cook wrote: Hello All, I have always had this problem on the one or two (web) servers that I have a separate /tmp partition defined. I found the answer a long time ago to unmount /tmp and try again and that always works.. but I've never found a way to make installworld with a separate /tmp partition on my systems. Is there a way? Is it something I'm doing? Is it the nosuid? or noexec? Can I tell installworld to use /var/tmp instead? ..etc.. Ultimately I am looking to be able to 'make installworld' like I do on my other boxes.. if I need something in /etc/make.conf to tell it not to use /tmp what is it.. b/c I've not found it.. [~]$ 2 grep tmp /etc/fstab /dev/ad0s1f /tmpufs rw,nosuid,noexec2 2 ^^ There's your problem. make buildworld needs to be able to execute programs that it writes into /tmp. Simply re-mount /tmp without the noexec flag and all should be well. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. Flat 3 7 Priory Courtyard PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW, UK signature.asc Description: OpenPGP digital signature
make installworld fails on amd64
Hi I am trying to make a installworld on amd64 and I get the following result: --- cc -Os -fno-guess-branch-probability -fomit-frame-pointer -fno-unit-at-a-time -mno-align-long-strings -mrtd -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -DUFS1_AND_UFS2 -DFLAGS=0x80 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/src/sys/boot/i386/boot2/../../common -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -m32 -S -o boot2.s.tmp /usr/src/sys/boot/i386/boot2/boot2.c sed -e '/align/d' -e '/nop/d' boot2.s.tmp boot2.s rm -f boot2.s.tmp as --32 -o boot2.o boot2.s ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 -o boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o sio.o objcopy -S -O binary boot2.out boot2.bin btxld -v -E 0x2000 -f bin -b /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin btxld:No such file or directory *** Error code 1 Stop in /usr/src/sys/boot/i386/boot2. *** Error code 1 Stop in /usr/src/sys/boot/i386. *** Error code 1 Stop in /usr/src/sys/boot. *** Error code 1 Stop in /usr/src/sys. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --- I did a cvsup this morning --- *default host=cvsup.fi.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_6_1 *default delete use-rel-suffix *default compress src-all --- Anyone any idea? Thanks a lot Valerio Daelli ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails on amd64
I corrected /etc/make.conf, I changed CPUTYPE?=opteron to CPUTYPE=opteron and now everything is fixed. Sorry Valerio Daelli ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
6.1-STABLE : make installworld fails
Hi, well, need some help... I have just upgraded my system from 6.1-PRERELEASE to 6.1-STABLE, with cvsup, make buildworld, make buildkernel, make installkernel. The upgrade for the basic system went through, it shows 6.1-STABLE version, and the fresh kernel version works, but: when I (in single-user mode) want to start make installworld (while being in /usr/src) to upgrade the userland, it only gives Installing everything cd /usr/src; make -f Makefile.inc1 install === share info (install) === include (install) Creating osreldate.h from newvers.sh touch not found *** Error code 127 Stop in /usr/src/include. *** Error code 1 No idea what to do now. For any help: thanks in advance! regards Axel -- * Axel Burwitz Phone +49 (0) 6021 570717 Mobile +49 (0) 151 15123177 ICQ 339978580 * * Mozilla Thunderbird 1.5 @ FreeBSD 6.1-PRE * ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1-STABLE : make installworld fails
On Friday 12 May 2006 06:59, Axel Burwitz wrote: Hi, well, need some help... I have just upgraded my system from 6.1-PRERELEASE to 6.1-STABLE, with cvsup, make buildworld, make buildkernel, make installkernel. The upgrade for the basic system went through, it shows 6.1-STABLE version, and the fresh kernel version works, but: when I (in single-user mode) want to start make installworld (while being in /usr/src) to upgrade the userland, it only gives Installing everything cd /usr/src; make -f Makefile.inc1 install === share info (install) === include (install) Creating osreldate.h from newvers.sh touch not found *** Error code 127 Stop in /usr/src/include. *** Error code 1 No idea what to do now. Check your system date. Almost everytime that make thinks it needs to use touch is due to the date on the computer being off. I run local time and have to use adjkerntz -i to set the local time zone. If your date is way off like it looks, you have to update it and then rebuild so that everything is current. You don't have any idea what wasn't built because it was thought to be current. Kent -- Kent Stewart Richland, WA http://www.soyandina.com/ I am Andean project. http://users.owt.com/kstewart/index.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make installworld fails
Hi all, After doing a svsup yesterday and doing a 'make -j4 buildworld' i've (my script that is) tried to proceed with a 'make installworld'. But it failed : www# make installworld ERROR: Required audit group is missing, see /usr/src/UPDATING. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I have checked /usr/src/UPDATING but there isn't any entry new about new groups and 'grep -w audit /etc/group' does not show any audit-group present. I also did a 'rm -rf /usr/obj/* ' and ran 'make -j4 buildworld' again, which endend without errors but the following 'make installworld' stops with the mentioned error again. I am using the '*default release=cvs tag=RELENG_6' in the supfile and am running 6.1-PRERELEASE now. What am I doing wrong ? Any clues are welcome. Beni. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
[EMAIL PROTECTED] wrote: Hi all, After doing a svsup yesterday and doing a 'make -j4 buildworld' i've (my script that is) tried to proceed with a 'make installworld'. But it failed : www# make installworld ERROR: Required audit group is missing, see /usr/src/UPDATING. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I have checked /usr/src/UPDATING but there isn't any entry new about new groups and 'grep -w audit /etc/group' does not show any audit-group present. I also did a 'rm -rf /usr/obj/* ' and ran 'make -j4 buildworld' again, which endend without errors but the following 'make installworld' stops with the mentioned error again. I am using the '*default release=cvs tag=RELENG_6' in the supfile and am running 6.1-PRERELEASE now. What am I doing wrong ? Any clues are welcome. The error message is wrong. There is a new group in '/etc/group' called 'audit:*:77:'. I recommend you don't automate mergemaster operations, and rerun the whole procedure manually. hth lars. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
[EMAIL PROTECTED] wrote: Hi all, After doing a svsup yesterday and doing a 'make -j4 buildworld' i've (my script that is) tried to proceed with a 'make installworld'. But it failed : www# make installworld ERROR: Required audit group is missing, see /usr/src/UPDATING. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I have checked /usr/src/UPDATING but there isn't any entry new about new groups and 'grep -w audit /etc/group' does not show any audit-group present. I also did a 'rm -rf /usr/obj/* ' and ran 'make -j4 buildworld' again, which endend without errors but the following 'make installworld' stops with the mentioned error again. I am using the '*default release=cvs tag=RELENG_6' in the supfile and am running 6.1-PRERELEASE now. What am I doing wrong ? Any clues are welcome. The error message is wrong. There is a new group in '/etc/group' called 'audit:*:77:'. I recommend you don't automate mergemaster operations, and rerun the whole procedure manually. hth lars. Lars, This is the script in question : #!/bin/sh echo Subject: `hostname` weekly cvsup run output /usr/local/bin/cvsup -g -L 2 /root/supfile cd /usr/src echo === echo Make buildworld now... echo === make -j4 buildworld echo === echo Make buildkernel now... echo === make buildkernel KERNCONF=BENI-60 echo === echo Make installkernel now... echo === make installkernel KERNCONF=BENI-60 echo === echo Make installworld now... echo === make installworld echo === echo `date` : Build Completed echo === if [ $? -eq 0 ]; then echo === echo `date` : BENI-60 kernel build completed echo === else echo '**' echo `date`: BENI-60 kernel build failed echo '**' fi echo === echo updating portstree now... echo === /usr/sbin/portsnap fetch update echo === echo These ports need updating... echo === pkg_version -l '' I didn't re-cvsup after doing the 'rm -rf /usr/obj/*', but did a manually 'make -j4 make buildworld' which ended without problems or errors. I don't mergemaster. If I manually add the group 'audit' the problem should be fixed ? Is this a new group or is it needed for some program ? Thanks, Beni. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
On Sat, Mar 11, 2006 at 10:52:01AM +0100, [EMAIL PROTECTED] wrote: [no he didn't; please use a mail client that quotes properly - it is confusing to read your emails otherwise, since Lars wrote some of the below text and not you] The error message is wrong. Actually it's correct, just a bit unclear. UPDATING includes the complete procedure you should always follow when building world. It includes a 'mergemaster -p' step, precisely for the purpose of adding new users and groups when they appear. There is a new group in '/etc/group' called 'audit:*:77:'. I recommend you don't automate mergemaster operations, and rerun the whole procedure manually. Yes, this script is just asking for trouble. Still, I bet you'll stop using it after the first time it destroys your FreeBSD installation :-) This is the script in question : #!/bin/sh echo Subject: `hostname` weekly cvsup run output /usr/local/bin/cvsup -g -L 2 /root/supfile cd /usr/src echo === echo Make buildworld now... echo === make -j4 buildworld echo === echo Make buildkernel now... echo === make buildkernel KERNCONF=BENI-60 echo === echo Make installkernel now... echo === make installkernel KERNCONF=BENI-60 echo === echo Make installworld now... echo === make installworld echo === echo `date` : Build Completed echo === if [ $? -eq 0 ]; then echo === echo `date` : BENI-60 kernel build completed echo === else echo '**' echo `date`: BENI-60 kernel build failed echo '**' fi echo === echo updating portstree now... echo === /usr/sbin/portsnap fetch update echo === echo These ports need updating... echo === pkg_version -l '' I didn't re-cvsup after doing the 'rm -rf /usr/obj/*', but did a manually 'make -j4 make buildworld' which ended without problems or errors. I don't mergemaster. You need to. If you insist on not doing so, any problems that result are your own concern. If I manually add the group 'audit' the problem should be fixed ? Is this a new group or is it needed for some program ? It's needed by parts of FreeBSD, which is why it's there. Kris pgpefc7JHHYDz.pgp Description: PGP signature
Re: make installworld fails
On Sat, Mar 11, 2006 at 10:52:01AM +0100, [EMAIL PROTECTED] wrote: [no he didn't; please use a mail client that quotes properly - it is confusing to read your emails otherwise, since Lars wrote some of the below text and not you] Yes he did, but i don't see the relevance of this remark to the initial question. But to answer your question, this is written via webmail, so any issues your reader has, please contact my provider (dommel.be) so that he can change this webmail program. The error message is wrong. Actually it's correct, just a bit unclear. UPDATING includes the complete procedure you should always follow when building world. It includes a 'mergemaster -p' step, precisely for the purpose of adding new users and groups when they appear. There is a new group in '/etc/group' called 'audit:*:77:'. I recommend you don't automate mergemaster operations, and rerun the whole procedure manually. Yes, this script is just asking for trouble. Still, I bet you'll stop using it after the first time it destroys your FreeBSD installation :-) Until now this script did exactly what is was supposed to do, so I don't see why I should stop now. I didn't re-cvsup after doing the 'rm -rf /usr/obj/*', but did a manually 'make -j4 make buildworld' which ended without problems or errors. I don't mergemaster. You need to. If you insist on not doing so, any problems that result are your own concern. So why didn't the maintainers/programmers add an entry to UPDATING ? That's why the file is for, no ? To explain any changes made and to prevent destroying your fbsd installation I thought... If I manually add the group 'audit' the problem should be fixed ? Is this a new group or is it needed for some program ? It's needed by parts of FreeBSD, which is why it's there. Then it's very recently added, cause I used the same script last week without any problems. But your suggestion to 'mergemaster -p' added the new group and the 'make installworld' completed without any further problems. Thanks. Beni([EMAIL PROTECTED]). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
On Sat, Mar 11, 2006 at 11:39:17AM +0100, [EMAIL PROTECTED] wrote: On Sat, Mar 11, 2006 at 10:52:01AM +0100, [EMAIL PROTECTED] wrote: [no he didn't; please use a mail client that quotes properly - it is confusing to read your emails otherwise, since Lars wrote some of the below text and not you] Yes he did, but i don't see the relevance of this remark to the initial question. It's in your own interests to write easily readable emails, otherwise people won't read them. But to answer your question, this is written via webmail, so any issues your reader has, please contact my provider (dommel.be) so that he can change this webmail program. The error message is wrong. Actually it's correct, just a bit unclear. ?UPDATING includes the complete procedure you should always follow when building world. ?It includes a 'mergemaster -p' step, precisely for the purpose of adding new users and groups when they appear. There is a new group in '/etc/group' called 'audit:*:77:'. I recommend you don't automate mergemaster operations, and rerun the whole procedure manually. Yes, this script is just asking for trouble. ?Still, I bet you'll stop using it after the first time it destroys your FreeBSD installation :-) Until now this script did exactly what is was supposed to do, so I don't see why I should stop now. OK. I hope you remember this conversation when that day comes :-) Kris pgpowimgmpecZ.pgp Description: PGP signature
Re: make installworld fails
Kris Kennaway wrote: The error message is wrong. Actually it's correct, just a bit unclear. UPDATING includes the complete procedure you should always follow when building world. It includes a 'mergemaster -p' step, precisely for the purpose of adding new users and groups when they appear. Dear Kris I have a few questions related to this error message ERROR: Required audit group is missing, see /usr/src/UPDATING I know that updating requires the mergemaster steps because I read the handbook. But I don't understand why this message tells me to look in that file, when there's nothing about that in it. Is /usr/src/UPDATING synonymous to 'the correct updating procedure'? Or is there a file which describes how I can manually insert needed groups and users when I mess up mergemaster runs? Or is that pointless anyway since I could just remove /usr/obj and rerun the whole updating procedure again before I reboot? And finally, is it really necessary to reboot after 'mergemaster -p'? Lately I've skipped that step with no adverse side-effects, saves me one reboot :-) I would be very grateful for any explanations. Thanks lars. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
On Sat, Mar 11, 2006 at 12:28:32PM +0100, [EMAIL PROTECTED] wrote: Kris Kennaway wrote: The error message is wrong. Actually it's correct, just a bit unclear. UPDATING includes the complete procedure you should always follow when building world. It includes a 'mergemaster -p' step, precisely for the purpose of adding new users and groups when they appear. Dear Kris I have a few questions related to this error message ERROR: Required audit group is missing, see /usr/src/UPDATING I know that updating requires the mergemaster steps because I read the handbook. But I don't understand why this message tells me to look in that file, when there's nothing about that in it. Is /usr/src/UPDATING synonymous to 'the correct updating procedure'? Yes, /usr/src/UPDATING does describe the correct updating procedure. If you follow that procedure you should not have any problems with missing groups. Look under COMMON ITEMS at the end of /usr/src/UPDATING. Or is there a file which describes how I can manually insert needed groups and users when I mess up mergemaster runs? Or is that pointless anyway since I could just remove /usr/obj and rerun the whole updating procedure again before I reboot? And finally, is it really necessary to reboot after 'mergemaster -p'? Lately I've skipped that step with no adverse side-effects, saves me one reboot :-) It is sometimes necessary to reboot with the new kernel to have 'make installworld' work correctly (and the recommended procedure is to reboot into single user mode *before* running 'mergemaster -p' (which in turn is to be done before 'make installworld'). I would be very grateful for any explanations. Thanks lars. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
Erik Trulsson wrote: Is /usr/src/UPDATING synonymous to 'the correct updating procedure'? Yes, /usr/src/UPDATING does describe the correct updating procedure. If you follow that procedure you should not have any problems with missing groups. Look under COMMON ITEMS at the end of /usr/src/UPDATING. Right, thanks. And finally, is it really necessary to reboot after 'mergemaster -p'? Lately I've skipped that step with no adverse side-effects, saves me one reboot :-) It is sometimes necessary to reboot with the new kernel to have 'make installworld' work correctly (and the recommended procedure is to reboot into single user mode *before* running 'mergemaster -p' (which in turn is to be done before 'make installworld'). Correct, I forgot since I hadn't been doing it in a while (so much for reading the handbook...). But how do I know when it's necessary? Or should I just reboot twice no matter what? Thanks, Lars. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
[EMAIL PROTECTED] wrote: Erik Trulsson wrote: [ ... ] It is sometimes necessary to reboot with the new kernel to have 'make installworld' work correctly (and the recommended procedure is to reboot into single user mode *before* running 'mergemaster -p' (which in turn is to be done before 'make installworld'). Correct, I forgot since I hadn't been doing it in a while (so much for reading the handbook...). But how do I know when it's necessary? If you know what the differences are between the installed system and what you are updating to, then you can figure out for yourself whether rebooting is necessary. Or should I just reboot twice no matter what? UPDATING is supposed to mention sufficiently important changes that make rebooting necessary, but if you want the process of updating your system to always work properly, you should follow the steps as provided, without taking any shortcuts. But if you get it wrong, boot off the most recent ISO image, and either fix the problem or do a binary upgrade reinstallation... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
On 2006-03-11 12:28, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Kris Kennaway wrote: The error message is wrong. Actually it's correct, just a bit unclear. UPDATING includes the complete procedure you should always follow when building world. It includes a 'mergemaster -p' step, precisely for the purpose of adding new users and groups when they appear. Dear Kris I have a few questions related to this error message ERROR: Required audit group is missing, see /usr/src/UPDATING I know that updating requires the mergemaster steps because I read the handbook. But I don't understand why this message tells me to look in that file, when there's nothing about that in it. Is /usr/src/UPDATING synonymous to 'the correct updating procedure'? By definition, yes. Or is there a file which describes how I can manually insert needed groups and users when I mess up mergemaster runs? The documented procedure in `/usr/src/UPDATING', as Kris has already mentioned includes a run of mergemaster with the -p option. Copying from my CURRENT's version of `UPDATING': % To rebuild everything and install it on the current system. % --- % # Note: sometimes if you are running current you gotta do more than % # is listed here if you are upgrading from a really old current. % % make sure you have good level 0 dumps % make buildworld % make kernel KERNCONF=YOUR_KERNEL_HERE % [1] % reboot in single user [3] % mergemaster -p [5] % make installworld % make delete-old % mergemaster [4] % reboot % % [1] If you have third party modules, such as vmware, you % should disable them at this point so they don't crash your % system on reboot. % % [3] From the bootblocks, boot -s, and then do % fsck -p % mount -u / % mount -a % cd src % adjkerntz -i# if CMOS is wall time % Also, when doing a major release upgrade, it is required that % you boot into single user mode to do the installworld. % % [4] Note: This step is non-optional. Failure to do this step % can result in a significant reduction in the functionality of the % system. Attempting to do it by hand is not recommended and those % that pursue this avenue should read this file carefully, as well % as the archives of freebsd-current and freebsd-hackers mailing lists % for potential gotchas. % % [5] Usually this step is a noop. However, from time to time % you may need to do this if you get unknown user in the following % step. It never hurts to do it all the time. You may need to % install a new mergemaster (cd src/usr.sbin/mergemaster make % install) after the buildworld before this step if you last updated % from current before 20020224 or from -stable before 20020408. Read these instructions. Then read them again. Then throw away that script and start over :) And finally, is it really necessary to reboot after 'mergemaster -p'? No. `UPDATING' mentions running `mergemaster -p' *AFTER* rebooting into single user mode, not *BEFORE*. Lately I've skipped that step with no adverse side-effects, saves me one reboot :-) You'll start booting into single user mode again, when you try to run `make installworld' with an old kernel and have it blow up, leaving you with a half installed base system and a lot of `interesting' work in front of you. Or when you install everything without a reboot, replace your old working userland and then find out that your new kernel is unbootable and your new userland is unusable without a new kernel. Booting into single user mode guarantees that you have verified at least once that the new kernel works. There's a very good reason why this is recommended :) - Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
Giorgos Keramidas wrote: No. `UPDATING' mentions running `mergemaster -p' *AFTER* rebooting into single user mode, not *BEFORE*. Yes, sorry, I'm mixing things up. Lately I've skipped that step with no adverse side-effects, saves me one reboot :-) You'll start booting into single user mode again, when you try to run `make installworld' with an old kernel and have it blow up, leaving you with a half installed base system and a lot of `interesting' work in front of you. Or when you install everything without a reboot, replace your old working userland and then find out that your new kernel is unbootable and your new userland is unusable without a new kernel. Booting into single user mode guarantees that you have verified at least once that the new kernel works. There's a very good reason why this is recommended :) You're right, the time saved with one less reboot is not worth the risk of salvaging a half-updated system. Thanks for the clarification. lars. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
On Sat, Mar 11, 2006 at 12:28:32PM +0100, [EMAIL PROTECTED] wrote: Kris Kennaway wrote: The error message is wrong. Actually it's correct, just a bit unclear. UPDATING includes the complete procedure you should always follow when building world. It includes a 'mergemaster -p' step, precisely for the purpose of adding new users and groups when they appear. Dear Kris I have a few questions related to this error message ERROR: Required audit group is missing, see /usr/src/UPDATING I know that updating requires the mergemaster steps because I read the handbook. But I don't understand why this message tells me to look in that file, when there's nothing about that in it. Is /usr/src/UPDATING synonymous to 'the correct updating procedure'? Yes. -- Updating Information for FreeBSD STABLE users This file is maintained and copyrighted by M. Warner Losh [EMAIL PROTECTED]. See end of file for further details. For commonly done items, please see the COMMON ITEMS: section later in the file. [...] [...special items applicable to special situations...] COMMON ITEMS: General Notes - ... To build a kernel - ... To rebuild everything and install it on the current system. --- # Note: sometimes if you are running current you gotta do more than # is listed here if you are upgrading from a really old current. make sure you have good level 0 dumps make buildworld make kernel KERNCONF=YOUR_KERNEL_HERE [1] reboot in single user [3] mergemaster -p [5] here make installworld make delete-old mergemaster [4] reboot Or is there a file which describes how I can manually insert needed groups and users when I mess up mergemaster runs? I think you can just rerun mergemaster -p. If you mess up a full mergemaster, you can use mergemaster -s to repair it. And finally, is it really necessary to reboot after 'mergemaster -p'? Lately I've skipped that step with no adverse side-effects, saves me one reboot :-) No, it just adds the users/groups, and rebooting won't gain you anything. Kris pgpx4Q68ts7B3.pgp Description: PGP signature
Re: make installworld fails
On Sat, Mar 11, 2006 at 01:04:33PM +0100, [EMAIL PROTECTED] wrote: Erik Trulsson wrote: Is /usr/src/UPDATING synonymous to 'the correct updating procedure'? Yes, /usr/src/UPDATING does describe the correct updating procedure. If you follow that procedure you should not have any problems with missing groups. Look under COMMON ITEMS at the end of /usr/src/UPDATING. Right, thanks. And finally, is it really necessary to reboot after 'mergemaster -p'? Lately I've skipped that step with no adverse side-effects, saves me one reboot :-) It is sometimes necessary to reboot with the new kernel to have 'make installworld' work correctly (and the recommended procedure is to reboot into single user mode *before* running 'mergemaster -p' (which in turn is to be done before 'make installworld'). Correct, I forgot since I hadn't been doing it in a while (so much for reading the handbook...). But how do I know when it's necessary? Or should I just reboot twice no matter what? *Every* *single* *step* in that list is needed in some situations. Some steps are not needed in *every* situation, so the temptation is to skip them to save your fingers some typing. But you'll regret this when you unexpectedly hit a situation in which the step should not have been omitted. In the worst case scenario this can damage or destroy your FreeBSD installation, or at least require some head-scratching and possible hand-holding from the community to help you recover. Here's an example of a worst case scenario: one reason for rebooting into single-user mode is to test whether your new kernel works. If your new kernel doesn't work (e.g. panics during boot), you can back it out at that point and all is well. If you blindly charge on without testing it, and proceed with the installworld, you may then find that your new world cannot be used with your old kernel (e.g. every FreeBSD command crashes when run with the old kernel, because they all now depend on an extra syscall or something). Oops. Since there is no way to back out an installworld, your only recourses at this point are: to fiddle around with /rescue and try to reconstruct a working system by hand (needs expert knowledge); or to remember where you put your install CD and pray that your last backup was up-to-date; This is a very rare situation, and it mostly occurs when updating to a new major version of FreeBSD, or at certain times during the development of -CURRENT. However, it's a real situation that you may encounter depending on how you use FreeBSD. There are other situations that are both more common and less severe. However, with a little discipline in following the instructions you'll never notice them. Kris pgpXVLCqRhkDC.pgp Description: PGP signature
RELENG_5_3 to RELENG_5 make installworld fails
Hello World, Just got 5.3-RELEASE installed yesterday on this system and was cvsup'ing to 5-STABLE today. Used the following process, based on /usr/src/UPDATING (as well as the countless times I've done this before), and got the error below during 'installworld'. I did this same update (from 5.3-RELEASE to 5.4-PRERELEASE) a week ago and it worked fine, however I also noticed that mergemaster -p wanted a few user accounts setup prior to installworld, related to pf/pfauth - that no longer seems to be a requirement so I'm concerned I missed a step or made some other bonehead move that I'm not aware of. cvsup'ed w/ the following basic values in supfile (no, this is not the entirety of the file) *default host=cvsup17.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_5 *default delete use-rel-suffix # cd /usr/src # make buildworld # make buildkernel KERNCONF=GENERIC # mergemaster -p # make installkernel KERNCONF=GENERIC # make installworld At this point - it gets started and then dies here: snip -- Installing everything -- cd /usr/src; make -f Makefile.inc1 install === share/info === include creating osreldate.h from newvers.sh touch: not found *** Error code 127 Stop in /usr/src/include. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. /snip I've check through the archives - not exhaustively - and found a few references to the touch: not found error - but nothing which led me toward getting this fixed. Ideas? Perhaps a better place to ask? At this point - I've got the kernel installed and can't get world installed - I could cvsup back to -RELEASE and get back to a safe state, but I'd rather get this little wrinkle worked out. Thanks, Aaron ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_5_3 to RELENG_5 make installworld fails
On Thursday 03 March 2005 02:21 pm, Aaron Nichols wrote: Hello World, Just got 5.3-RELEASE installed yesterday on this system and was cvsup'ing to 5-STABLE today. Used the following process, based on /usr/src/UPDATING (as well as the countless times I've done this before), and got the error below during 'installworld'. I did this same update (from 5.3-RELEASE to 5.4-PRERELEASE) a week ago and it worked fine, however I also noticed that mergemaster -p wanted a few user accounts setup prior to installworld, related to pf/pfauth - that no longer seems to be a requirement so I'm concerned I missed a step or made some other bonehead move that I'm not aware of. You missed a step. Your system clock is off and that makes the installworld try to use touch. Set your system clock and you may have to remake your world but it should install. Kent cvsup'ed w/ the following basic values in supfile (no, this is not the entirety of the file) *default host=cvsup17.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_5 *default delete use-rel-suffix # cd /usr/src # make buildworld # make buildkernel KERNCONF=GENERIC # mergemaster -p # make installkernel KERNCONF=GENERIC # make installworld At this point - it gets started and then dies here: snip -- Installing everything -- cd /usr/src; make -f Makefile.inc1 install === share/info === include creating osreldate.h from newvers.sh touch: not found *** Error code 127 Stop in /usr/src/include. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. /snip I've check through the archives - not exhaustively - and found a few references to the touch: not found error - but nothing which led me toward getting this fixed. Ideas? Perhaps a better place to ask? At this point - I've got the kernel installed and can't get world installed - I could cvsup back to -RELEASE and get back to a safe state, but I'd rather get this little wrinkle worked out. Thanks, Aaron ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_5_3 to RELENG_5 make installworld fails
On Thu, 3 Mar 2005 14:39:16 -0800, Kent Stewart [EMAIL PROTECTED] wrote: You missed a step. Your system clock is off and that makes the installworld try to use touch. Set your system clock and you may have to remake your world but it should install. Kent Infact it was off - can you give me some detail as to why that matters? Not that I doubt that having my system clock set to a date 8 months prior to the date of files in cvs might cause a problem - but I'm curious about the details. If you can even point me at a URL and I'll read for myself - I'm just curious. If that was the problem (buildworld happenning as I type) then thank you and my apologies for the oversight. New system, didn't bother to make sure the BIOS date was right and ntp wasn't yet setup. Thanks, Aaron ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_5_3 to RELENG_5 make installworld fails
On Thursday 03 March 2005 03:26 pm, Aaron Nichols wrote: On Thu, 3 Mar 2005 14:39:16 -0800, Kent Stewart [EMAIL PROTECTED] wrote: You missed a step. Your system clock is off and that makes the installworld try to use touch. Set your system clock and you may have to remake your world but it should install. Kent Infact it was off - can you give me some detail as to why that matters? Not that I doubt that having my system clock set to a date 8 months prior to the date of files in cvs might cause a problem - but I'm curious about the details. If you can even point me at a URL and I'll read for myself - I'm just curious. Make is used to build files that are out of date. When the buildworld created the file, it was older than the files you downloaded using cvsup. So, it was created out of date and installworld thought it needed to rebuild it. Touch isn't needed in the installworld and it fails. Kent If that was the problem (buildworld happenning as I type) then thank you and my apologies for the oversight. New system, didn't bother to make sure the BIOS date was right and ntp wasn't yet setup. Thanks, Aaron ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make installworld fails
Hello. I am trying to upgrade FreeBSD 5.3 and performed the following steps on a clean install and after upgrading sources: Booted into single-user mode cd /usr/src make buildworld make buildkernel KERNCONF=GENERIC make installkernel KERNCONF=GENERIC Then rebooted the system back into single-user mode cd /usr/src make installworld However this fails and the last few lines on screen are: install -o root -g wheel -m 444 zzz.8.gz /usr/share/man/man8 === etc === etc/sendmail cd /usr/src/etc/../share/man; make makedb makewhatis /usr/share/man pid 17053 (makewhatis), uid 0: exited on signal 11 (core dumped) *** Signal 11 Stop in /usr/src/share/man *** Error code 1 Stop in /usr/src/etc *** Error code 1 Stop in /usr/src *** Error code 1 Stop in /usr/src *** Error code 1 Stop in /usr/src *** Error code 1 Stop in /usr/src I couldn't find a core file on the system. Please help. Thank you. -- Viren Patel Chemistry Biochemistry University of Texas at Austin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make installworld fails at kerberos5
Hello, I'm just learning FreeBSD (Release 4.9). I installed in January and everything seemed fine. On February 12, I did a CVSup. buildworld, make and installkernel produced no errors, but installworld fails, and I can't figure out why. From my script output file: === kerberos5/lib/libvers === kerberos5/lib/libasn1 install -C -C -o root -9 wheel -m 444 libans1.a /usr/lib install -C -C -o root -9 wheel -m 444 libans1_p.a /usr/lib install -C -s -o root -9 whell -m 444 libans1.so.5 /usr/lib ln -fs libans1.so.5 /usr/lib/libasn1.so yacc -d /usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/parse.y cp y.tab.c parse.c cp:No such file or directory *** Error code 1 Stop in /usr/src/kerberos5/lib/libasn1 *** Error code 1 The part I don't understand is that if I look in /usr/src/kerberos5/lib/libasn1, I see the y.tab.c created by installworld. I would appreciate any help. I've been stuck for 10 days now. Thanks, Steve __ Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want. http://antispam.yahoo.com/tools ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails on 4.8 in /usr/src/share/colldef
On Wed, Aug 20, 2003 at 11:36:57PM -0500, Doug Poland wrote: Greetings, I'm attempting to installworld on a 4.8-RELEASE machine. I installed the OS yesterday from CD-ROM. Today I did a cvsup for latest sources. I've successfully built world, built and installed custom kernel. For the archives, I re-ran cvsup then next day, rebuilt the world, then re-ran installworld and everything installed fine. -- Regards, Doug When I attempt to run: # make installworld this is what I see ... ... ... snip ... ... ... === secure/usr.sbin/sshd install -s -o root -g wheel -m 555 sshd /usr/sbin install -o root -g wheel -m 444 sshd.8.gz /usr/share/man/man8 install -o root -g wheel -m 444 sshd_config.5.gz /usr/share/man/man5 === share === share/colldef install -m 644 -o root -g wheel bg_BG.CP1251.out /usr/share/locale/bg_BG.CP1251/LC_COLLATE install -m 644 -o root -g wheel cs_CZ.ISO8859-2.out /usr/share/locale/cs_CZ.ISO8859-2/LC_COLLATE install -m 644 -o root -g wheel de_DE.ISO8859-1.out /usr/share/locale/de_DE.ISO8859-1/LC_COLLATE install -m 644 -o root -g wheel de_DE.ISO8859-15.out /usr/share/locale/de_DE.ISO8859-15/LC_COLLATE install -m 644 -o root -g wheel el_GR.ISO8859-7.out /usr/share/locale/el_GR.ISO8859-7/LC_COLLATE install -m 644 -o root -g wheel es_ES.ISO8859-1.out /usr/share/locale/es_ES.ISO8859-1/LC_COLLATE install -m 644 -o root -g wheel es_ES.ISO8859-15.out /usr/share/locale/es_ES.ISO8859-15/LC_COLLATE install -m 644 -o root -g wheel et_EE.ISO8859-15.out /usr/share/locale/et_EE.ISO8859-15/LC_COLLATE install -m 644 -o root -g wheel hi_IN.ISCII-DEV.out /usr/share/locale/hi_IN.ISCII-DEV/LC_COLLATE install -m 644 -o root -g wheel is_IS.ISO8859-1.out /usr/share/locale/is_IS.ISO8859-1/LC_COLLATE install -m 644 -o root -g wheel is_IS.ISO8859-15.out /usr/share/locale/is_IS.ISO8859-15/LC_COLLATE install -m 644 -o root -g wheel la_LN.ISO8859-1.out /usr/share/locale/la_LN.ISO8859-1/LC_COLLATE install -m 644 -o root -g wheel la_LN.ISO8859-15.out /usr/share/locale/la_LN.ISO8859-15/LC_COLLATE install -m 644 -o root -g wheel la_LN.ISO8859-2.out /usr/share/locale/la_LN.ISO8859-2/LC_COLLATE install -m 644 -o root -g wheel la_LN.ISO8859-4.out /usr/share/locale/la_LN.ISO8859-4/LC_COLLATE install -m 644 -o root -g wheel la_LN.US-ASCII.out /usr/share/locale/la_LN.US-ASCII/LC_COLLATE install -m 644 -o root -g wheel lt_LT.ISO8859-4.out /usr/share/locale/lt_LT.ISO8859-4/LC_COLLATE install -m 644 -o root -g wheel pl_PL.ISO8859-2.out /usr/share/locale/pl_PL.ISO8859-2/LC_COLLATE install -m 644 -o root -g wheel ru_RU.CP1251.out /usr/share/locale/ru_RU.CP1251/LC_COLLATE install -m 644 -o root -g wheel ru_RU.CP866.out /usr/share/locale/ru_RU.CP866/LC_COLLATE install -m 644 -o root -g wheel ru_RU.ISO8859-5.out /usr/share/locale/ru_RU.ISO8859-5/LC_COLLATE install -m 644 -o root -g wheel ru_RU.KOI8-R.out /usr/share/locale/ru_RU.KOI8-R/LC_COLLATE install -m 644 -o root -g wheel sv_SE.ISO8859-1.out /usr/share/locale/sv_SE.ISO8859-1/LC_COLLATE install -m 644 -o root -g wheel sv_SE.ISO8859-15.out /usr/share/locale/sv_SE.ISO8859-15/LC_COLLATE install -m 644 -o root -g wheel uk_UA.ISO8859-5.out /usr/share/locale/uk_UA.ISO8859-5/LC_COLLATE install -m 644 -o root -g wheel uk_UA.KOI8-U.out /usr/share/locale/uk_UA.KOI8-U/LC_COLLATE ln -fs ../la_LN.US-ASCII/LC_COLLATE /usr/share/locale/am_ET.UTF-8/LC_COLLATE ln: /usr/share/locale/am_ET.UTF-8/LC_COLLATE: No such file or directory *** Error code 1 Stop in /usr/src/share/colldef. *** Error code 1 Stop in /usr/src/share. *** Error code 1 I've tried installworld twice but to no avail. Can someone help me out here? Many thanks in advance. -- Regards, Doug ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make installworld fails on 4.8 in /usr/src/share/colldef
Greetings, I'm attempting to installworld on a 4.8-RELEASE machine. I installed the OS yesterday from CD-ROM. Today I did a cvsup for latest sources. I've successfully built world, built and installed custom kernel. When I attempt to run: # make installworld this is what I see ... ... ... snip ... ... ... === secure/usr.sbin/sshd install -s -o root -g wheel -m 555 sshd /usr/sbin install -o root -g wheel -m 444 sshd.8.gz /usr/share/man/man8 install -o root -g wheel -m 444 sshd_config.5.gz /usr/share/man/man5 === share === share/colldef install -m 644 -o root -g wheel bg_BG.CP1251.out /usr/share/locale/bg_BG.CP1251/LC_COLLATE install -m 644 -o root -g wheel cs_CZ.ISO8859-2.out /usr/share/locale/cs_CZ.ISO8859-2/LC_COLLATE install -m 644 -o root -g wheel de_DE.ISO8859-1.out /usr/share/locale/de_DE.ISO8859-1/LC_COLLATE install -m 644 -o root -g wheel de_DE.ISO8859-15.out /usr/share/locale/de_DE.ISO8859-15/LC_COLLATE install -m 644 -o root -g wheel el_GR.ISO8859-7.out /usr/share/locale/el_GR.ISO8859-7/LC_COLLATE install -m 644 -o root -g wheel es_ES.ISO8859-1.out /usr/share/locale/es_ES.ISO8859-1/LC_COLLATE install -m 644 -o root -g wheel es_ES.ISO8859-15.out /usr/share/locale/es_ES.ISO8859-15/LC_COLLATE install -m 644 -o root -g wheel et_EE.ISO8859-15.out /usr/share/locale/et_EE.ISO8859-15/LC_COLLATE install -m 644 -o root -g wheel hi_IN.ISCII-DEV.out /usr/share/locale/hi_IN.ISCII-DEV/LC_COLLATE install -m 644 -o root -g wheel is_IS.ISO8859-1.out /usr/share/locale/is_IS.ISO8859-1/LC_COLLATE install -m 644 -o root -g wheel is_IS.ISO8859-15.out /usr/share/locale/is_IS.ISO8859-15/LC_COLLATE install -m 644 -o root -g wheel la_LN.ISO8859-1.out /usr/share/locale/la_LN.ISO8859-1/LC_COLLATE install -m 644 -o root -g wheel la_LN.ISO8859-15.out /usr/share/locale/la_LN.ISO8859-15/LC_COLLATE install -m 644 -o root -g wheel la_LN.ISO8859-2.out /usr/share/locale/la_LN.ISO8859-2/LC_COLLATE install -m 644 -o root -g wheel la_LN.ISO8859-4.out /usr/share/locale/la_LN.ISO8859-4/LC_COLLATE install -m 644 -o root -g wheel la_LN.US-ASCII.out /usr/share/locale/la_LN.US-ASCII/LC_COLLATE install -m 644 -o root -g wheel lt_LT.ISO8859-4.out /usr/share/locale/lt_LT.ISO8859-4/LC_COLLATE install -m 644 -o root -g wheel pl_PL.ISO8859-2.out /usr/share/locale/pl_PL.ISO8859-2/LC_COLLATE install -m 644 -o root -g wheel ru_RU.CP1251.out /usr/share/locale/ru_RU.CP1251/LC_COLLATE install -m 644 -o root -g wheel ru_RU.CP866.out /usr/share/locale/ru_RU.CP866/LC_COLLATE install -m 644 -o root -g wheel ru_RU.ISO8859-5.out /usr/share/locale/ru_RU.ISO8859-5/LC_COLLATE install -m 644 -o root -g wheel ru_RU.KOI8-R.out /usr/share/locale/ru_RU.KOI8-R/LC_COLLATE install -m 644 -o root -g wheel sv_SE.ISO8859-1.out /usr/share/locale/sv_SE.ISO8859-1/LC_COLLATE install -m 644 -o root -g wheel sv_SE.ISO8859-15.out /usr/share/locale/sv_SE.ISO8859-15/LC_COLLATE install -m 644 -o root -g wheel uk_UA.ISO8859-5.out /usr/share/locale/uk_UA.ISO8859-5/LC_COLLATE install -m 644 -o root -g wheel uk_UA.KOI8-U.out /usr/share/locale/uk_UA.KOI8-U/LC_COLLATE ln -fs ../la_LN.US-ASCII/LC_COLLATE /usr/share/locale/am_ET.UTF-8/LC_COLLATE ln: /usr/share/locale/am_ET.UTF-8/LC_COLLATE: No such file or directory *** Error code 1 Stop in /usr/src/share/colldef. *** Error code 1 Stop in /usr/src/share. *** Error code 1 I've tried installworld twice but to no avail. Can someone help me out here? Many thanks in advance. -- Regards, Doug ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails with install: crypto.ko: No such file or directory
On 2002-11-22 09:32, Tillman [EMAIL PROTECTED] wrote: Howdy, (All sources were CVSUP'd this morning) Here's the actual output of make installkernel: [root@loki src]# make installkernel -DKERNCONF=LOKI === crypto install -o root -g wheel -m 555 crypto.ko /modules install: crypto.ko: No such file or directory *** Error code 71 You probably caught the MFC of Sam Leffler while it was happening. Hoping that you didn't actually start using the broken kernel (although it shouldn't be a problem) ... CVSup again. You should be able to build fine afterwards. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: make installworld fails with install: crypto.ko: No such file or directory
On Fri, Nov 22, 2002 at 08:21:32PM +0200, Giorgos Keramidas wrote: On 2002-11-22 09:32, Tillman [EMAIL PROTECTED] wrote: Howdy, (All sources were CVSUP'd this morning) Here's the actual output of make installkernel: [root@loki src]# make installkernel -DKERNCONF=LOKI === crypto install -o root -g wheel -m 555 crypto.ko /modules install: crypto.ko: No such file or directory *** Error code 71 You probably caught the MFC of Sam Leffler while it was happening. Hoping that you didn't actually start using the broken kernel (although it shouldn't be a problem) ... CVSup again. lol! Nope, as an ipsec gateway box, I figured that if it was complaining about crypto stuff I'd better stop completely until it was happy. You should be able to build fine afterwards. And I was. Thanks! -T -- If any man thinks he slays, and if another thinks he is slain, neither knows the ways of truth. The Eternal in man cannot kill: the Eternal in man cannot die. Bhagavad Gita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Got past installworld, new problems however [WASRe: make installworld fails with mergemaster errors - 4.4Rel upgrade to 4.6 Stable]
Hi Doug, Thanks for getting back to me. I actually got around that problem in the end. However upon completing the upgrade, I noticed a couple of things: 1] startx has stopped working (just XFree86-4.0.2 from the 4.4 CD Set, no gnome of kde installed as yet) typing startx for any user just sits there doing nothing (after 5 mins or so I killed it with cttrl c) 2] All user account except that for root disappeared. 3] During bootup apache failed with unable to find my FQDN. After login (as root) ps waux | grep httpd returns nothing. 4] The box does not ask me to enter a password when logging in as root on the console I'm not sure if this is the right way to get the above queries addressed, but let me know if I should post another to the list. Thanks again for taking the time to respond. Stacey Quoting Doug Barton [EMAIL PROTECTED]: On Wed, 24 Jul 2002 [EMAIL PROTECTED] wrote: Hello, I've just done a fresh install of 4.4Rel, and I'm trying to upgrade to the latest stable. In single user mode [using shutdown now] having dropped from multiuser mode - All went well until I got to make installworld. I hit the issue mentioned in UPDATING 20020404 about the new Sendmail user smmsp. I followed the advice to: cd /usr/src/usr.sbin/mergemaster; make install clean The clean there is the problem. What UPDATING actually says is: cd /usr/src/usr.sbin/mergemaster; make all install [clean] I'll delete that altogether, as it's misleading and potentially dangerous. -- We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory. - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Got past installworld, new problems however [WASRe: make installworld fails with mergemaster errors - 4.4Rel upgrade to 4.6 Stable]
Hello Brian, Thanks for the reply. As I'm actually still going through bringing the up to a usable state, the disappeared user accounts are not too much of a problem at the moment. Its the lack of authentication for root login I'm really concerned with on this point! I'll take a look at XFree86Config and check for anything untoward. I've not used ktrace, nor kdump before. Are they used in the same way as truss? However, as I do intend on upgrading XFree86 to XFree86-4.2.1 today, would it be more effective to re-install (remove install latest version), or simply upgrade the current version (via portupgrade)? ps waux - show process report, [-a: include all process with a tty session] + [-u: report user ID for each process listed] + [-w: show wide output] So, seeing that apache is configured to start on bootup, I would have expected to see a process called httpd running with variou runtime options listed in the returned process table - which of course, I don't. I really am hoping that I could aviod having the reinstall FBSD again here. This install's taken well over two days of debugging already:- initial install took the default XFree86-3.3.6x (didn't want that) The box hung at installation when I included gnome desktop (hence only XFree86-4.0.2 installed this time around) Well., thanks again for taking the time, Brian. Hope that what I've included here lights a few bulbs in a few peoples' heads before too long. Stacey Quoting Brian T. Schellenberger [EMAIL PROTECTED]: On Wednesday 24 July 2002 03:40 am, [EMAIL PROTECTED] wrote: | Hi Doug, |Thanks for getting back to me. I actually got around that problem in the | end. | | However upon completing the upgrade, I noticed a couple of things: | | 1] startx has stopped working (just XFree86-4.0.2 from the 4.4 CD Set, no | gnome of kde installed as yet) Hard to say. Does /etc/X11/XFree86Config look like it always did? Might want to ktrace/kdump and see what it's really calling. | typing startx for any user just sits there doing nothing (after 5 mins or | so I killed it with cttrl c) | | 2] All user account except that for root disappeared. Something went wrong with mergemaster. Perhaps you installed when you should have merged. (Or perhaps the problem is with the weird make stuff you cite below. I don't believe that I ever did anything of the sort and things worked ok for me.) Regardless, the solution is simple: Restore your /etc/passwd /etc/master.passwd from backup. | 3] During bootup apache failed with unable to find my FQDN. After login | (as root) ps waux | grep httpd returns nothing. Sorry, that's Greek to me. | 4] The box does not ask me to enter a password when logging in as root on | the console See [2] above. | I'm not sure if this is the right way to get the above queries addressed, | but let me know if I should post another to the list. This is a good place for . . . well, questions. | Thanks again for taking the time to respond. | | Stacey | | Quoting Doug Barton [EMAIL PROTECTED]: | On Wed, 24 Jul 2002 [EMAIL PROTECTED] wrote: | Hello, | I've just done a fresh install of 4.4Rel, and I'm trying to | | upgrade to | | the latest stable. | | In single user mode [using shutdown now] having dropped from multiuser | | mode - | | All went well until I got to make installworld. I hit the issue | | mentioned in | | UPDATING 20020404 about the new Sendmail user smmsp. I followed the | | advice to: | cd /usr/src/usr.sbin/mergemaster; make install clean | | The clean there is the problem. What UPDATING actually says is: | | cd /usr/src/usr.sbin/mergemaster; make all install [clean] | | I'll delete that altogether, as it's misleading and potentially | dangerous. | | -- | We have known freedom's price. We have shown freedom's power. |And in this great conflict, ... we will see freedom's victory. |- George W. Bush, President of the United States |State of the Union, January 28, 2002 | | Do YOU Yahoo!? | | To Unsubscribe: send mail to [EMAIL PROTECTED] | with unsubscribe freebsd-questions in the body of the message -- Brian, the man from Babble-On . . . . [EMAIL PROTECTED] (personal) http://www.babbleon.org http://www.eff.org http://www.programming-freedom.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Got past installworld, new problems however [WASRe: make installworld fails with mergemaster errors - 4.4Rel upgrade to 4.6 Stable]
On Wednesday 24 July 2002 03:40 am, [EMAIL PROTECTED] wrote: | Hi Doug, |Thanks for getting back to me. I actually got around that problem in the | end. | | However upon completing the upgrade, I noticed a couple of things: | | 1] startx has stopped working (just XFree86-4.0.2 from the 4.4 CD Set, no | gnome of kde installed as yet) Hard to say. Does /etc/X11/XFree86Config look like it always did? Might want to ktrace/kdump and see what it's really calling. | typing startx for any user just sits there doing nothing (after 5 mins or | so I killed it with cttrl c) | | 2] All user account except that for root disappeared. Something went wrong with mergemaster. Perhaps you installed when you should have merged. (Or perhaps the problem is with the weird make stuff you cite below. I don't believe that I ever did anything of the sort and things worked ok for me.) Regardless, the solution is simple: Restore your /etc/passwd /etc/master.passwd from backup. | 3] During bootup apache failed with unable to find my FQDN. After login | (as root) ps waux | grep httpd returns nothing. Sorry, that's Greek to me. | 4] The box does not ask me to enter a password when logging in as root on | the console See [2] above. | I'm not sure if this is the right way to get the above queries addressed, | but let me know if I should post another to the list. This is a good place for . . . well, questions. | Thanks again for taking the time to respond. | | Stacey | | Quoting Doug Barton [EMAIL PROTECTED]: | On Wed, 24 Jul 2002 [EMAIL PROTECTED] wrote: | Hello, | I've just done a fresh install of 4.4Rel, and I'm trying to | | upgrade to | | the latest stable. | | In single user mode [using shutdown now] having dropped from multiuser | | mode - | | All went well until I got to make installworld. I hit the issue | | mentioned in | | UPDATING 20020404 about the new Sendmail user smmsp. I followed the | | advice to: | cd /usr/src/usr.sbin/mergemaster; make install clean | | The clean there is the problem. What UPDATING actually says is: | | cd /usr/src/usr.sbin/mergemaster; make all install [clean] | | I'll delete that altogether, as it's misleading and potentially | dangerous. | | -- | We have known freedom's price. We have shown freedom's power. |And in this great conflict, ... we will see freedom's victory. | - George W. Bush, President of the United States |State of the Union, January 28, 2002 | | Do YOU Yahoo!? | | To Unsubscribe: send mail to [EMAIL PROTECTED] | with unsubscribe freebsd-questions in the body of the message -- Brian, the man from Babble-On . . . . [EMAIL PROTECTED] (personal) http://www.babbleon.org http://www.eff.org http://www.programming-freedom.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Got past installworld, new problems however [WASRe: make installworld fails with mergemaster errors - 4.4Rel upgrade to 4.6 Stable]
Hi Jud, Thanks for the information here. I'll check those files as and when I get the chance. The wrapper port *was* installed, and WORKING before I cvsup'd the system. I'll check .xinitrc files in both root and any of the restored user accounts. Stacey Quoting Jud [EMAIL PROTECTED]: 7/24/2002 4:06:16 AM, [EMAIL PROTECTED] wrote: Hello Brian, Thanks for the reply. As I'm actually still going through bringing the up to a usable state, the disappeared user accounts are not too much of a problem at the moment. Its the lack of authentication for root login I'm really concerned with on this point! I'll take a look at XFree86Config and check for anything untoward. I've not used ktrace, nor kdump before. Are they used in the same way as truss? However, as I do intend on upgrading XFree86 to XFree86-4.2.1 today, would it be more effective to re-install (remove install latest version), or simply upgrade the current version (via portupgrade)? ps waux - show process report, [-a: include all process with a tty session] + [-u: report user ID for each process listed] + [-w: show wide output] So, seeing that apache is configured to start on bootup, I would have expected to see a process called httpd running with variou runtime options listed in the returned process table - which of course, I don't. I really am hoping that I could aviod having the reinstall FBSD again here. This install's taken well over two days of debugging already:- initial install took the default XFree86-3.3.6x (didn't want that) The box hung at installation when I included gnome desktop (hence only XFree86-4.0.2 installed this time around) Well., thanks again for taking the time, Brian. Hope that what I've included here lights a few bulbs in a few peoples' heads before too long. Stacey Quoting Brian T. Schellenberger [EMAIL PROTECTED]: On Wednesday 24 July 2002 03:40 am, [EMAIL PROTECTED] wrote: | Hi Doug, |Thanks for getting back to me. I actually got around that problem in the | end. | | However upon completing the upgrade, I noticed a couple of things: | | 1] startx has stopped working (just XFree86-4.0.2 from the 4.4 CD Set, no | gnome of kde installed as yet) Hard to say. Does /etc/X11/XFree86Config look like it always did? Might want to ktrace/kdump and see what it's really calling. | typing startx for any user just sits there doing nothing (after 5 mins or | so I killed it with cttrl c) | | 2] All user account except that for root disappeared. Something went wrong with mergemaster. Perhaps you installed when you should have merged. (Or perhaps the problem is with the weird make stuff you cite below. I don't believe that I ever did anything of the sort and things worked ok for me.) Regardless, the solution is simple: Restore your /etc/passwd /etc/master.passwd from backup. | 3] During bootup apache failed with unable to find my FQDN. After login | (as root) ps waux | grep httpd returns nothing. Sorry, that's Greek to me. | 4] The box does not ask me to enter a password when logging in as root on | the console See [2] above. Sounds like (after taking Brian's advice) you may want to do /stand/sysinstall (as root) and choose the option to add users. Check the www group in /etc/groups after you do this to add anyone you want to be able to use Apache. Apache is looking for your fully qualified domain name - I'd look in /etc/hosts to see if you need to add back anything there that may have been lost in the upgrade. Re startx, after you have a look at the X11 config and get your users straightened out, you'll want to reinstall wrapper from X11 ports. Oh, and BTW, do you still have .xinitrc files in root and $HOME? Jud To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Got past installworld, new problems however [WASRe: make installworld fails with mergemaster errors - 4.4Rel upgrade to 4.6 Stable]
On Wednesday 24 July 2002 09:27 am, [EMAIL PROTECTED] wrote: | Hi Brain, |Thanks for getting back to me. No problem. | | I'm happy to at last find someone who is willing to at least *say* that | he's blasted and reinstalled a higher version of XFree86-4. | | From what you said here, I'll probably want to go with a packages install | as well. | | I strongly recomemnd deintalling via 'pkg_delete X*' (you can use | pkg_info | first to be sure that this will deinstall what you expect) and then | re-installing. Actually, I'd probably install from packages rather than | | ports, it's a lot quicker. Heck, I *know* I'd do it that way because I | *did* | do it that way just four days ago. The pkg_add -r didn't work right for | | XFree86-4 because it was looking the wrong place, but if you make it | look for | All packages instead of Latest you should be golden. | | How exactly do you specify to pkd_add to look for ALL instead the latest? | And which version would it then return? Check the man page for pkg_add, but there's an environement variable you set for the place to look. I forget what the default is, but just run it with the defaults and if it works, great--somebody fixed something since Saturday. If it fails, then set the environemnt variable to the same as the default path only change the /Latest at the end to /All, and it will install (at least of Saturday) XFree86-4.2.0_1,1. -- Brian, the man from Babble-On . . . . [EMAIL PROTECTED] (personal) http://www.babbleon.org http://www.eff.org http://www.programming-freedom.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
make installworld fails with mergemaster errors - 4.4Rel upgrade to 4.6 Stable
Hello, I've just done a fresh install of 4.4Rel, and I'm trying to upgrade to the latest stable. In single user mode [using shutdown now] having dropped from multiuser mode - All went well until I got to make installworld. I hit the issue mentioned in UPDATING 20020404 about the new Sendmail user smmsp. I followed the advice to: cd /usr/src/usr.sbin/mergemaster; make install clean mergemaster -p I used the i option to install each of the temporary files that appeared. I then ran make installworld, which fails with the following: === usr/sbin/mergemaster install -c -o root -g wheel -m 444 mergemaster8.gz /usr/share/man/man8 install: mergemaster.8.gz : No such file or directory *** Error Code 71 Stop in /usr/src/usr.sbin/mergemaster. *** Error Code 1 Stop in /usr/src/usr.sbin. *** Error Code 1 Can someone help with this please? If its documented in UPDATING, I figure there should be a procedure out of this out there. Stacey To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: make installworld fails with mergemaster errors - 4.4Rel upgradeto 4.6 Stable
On Wed, 24 Jul 2002 [EMAIL PROTECTED] wrote: Hello, I've just done a fresh install of 4.4Rel, and I'm trying to upgrade to the latest stable. In single user mode [using shutdown now] having dropped from multiuser mode - All went well until I got to make installworld. I hit the issue mentioned in UPDATING 20020404 about the new Sendmail user smmsp. I followed the advice to: cd /usr/src/usr.sbin/mergemaster; make install clean The clean there is the problem. What UPDATING actually says is: cd /usr/src/usr.sbin/mergemaster; make all install [clean] I'll delete that altogether, as it's misleading and potentially dangerous. -- We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory. - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message