Re: Mergemaster Problem
On Fri, 24 Apr 2009, Giorgos Keramidas wrote:
On Thu, 23 Apr 2009 14:54:25 -0700 (PDT), Annelise Anderson
wrote:
I'm running mergemaster as root (-v -i -c) on an upgrade to
stable (I rebooted with the new kernel but have not done
the install) and can't run mergemaster, with result as follows:
Default is to use /var/tmp/temproot as is
How should I deal with this? [Use the existing /var/tmp/temproot] d
*** Deleting the old /var/tmp/temproot
*** Creating the temporary root environment in /var/tmp/temproot
*** /var/tmp/temproot ready for use
*** Creating and populating directory structure in /var/tmp/temproot
*** Press the [Enter] or [Return] key to continue
"/usr/src/etc/Makefile", line 34: Malformed conditional (${MK_AMD} != "no")
"/usr/src/etc/Makefile", line 36: if-less endif
[...]
*** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to
the temproot environment
Any suggestions?
Hi Annelise,
It seems you are running mergemaster with a new kernel but with the old
make(1) binary across a major release update. Since part of the update
process spawned by mergemaster depends on `make' and the `/usr/share/mk'
files, you have to installworld before you can use the new megemaster
script.
The pre-buildworld mode of mergemaster (`mergemaster -p') should run
fine even with an old userland and old `/usr/share/mk' files. But you
should install everything before you run a full mergemaster update of
all files in `/etc'.
Right you are. Thanks. Now I understand what I was reading in UPDATING.
Annelise
___
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: Mergemaster Problem
On Thu, 23 Apr 2009 14:54:25 -0700 (PDT), Annelise Anderson
wrote:
> I'm running mergemaster as root (-v -i -c) on an upgrade to
> stable (I rebooted with the new kernel but have not done
> the install) and can't run mergemaster, with result as follows:
>
> Default is to use /var/tmp/temproot as is
>
> How should I deal with this? [Use the existing /var/tmp/temproot] d
>
>*** Deleting the old /var/tmp/temproot
>
> *** Creating the temporary root environment in /var/tmp/temproot
> *** /var/tmp/temproot ready for use
> *** Creating and populating directory structure in /var/tmp/temproot
>
> *** Press the [Enter] or [Return] key to continue
> "/usr/src/etc/Makefile", line 34: Malformed conditional (${MK_AMD} != "no")
> "/usr/src/etc/Makefile", line 36: if-less endif
[...]
>
> *** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to
> the temproot environment
>
> Any suggestions?
Hi Annelise,
It seems you are running mergemaster with a new kernel but with the old
make(1) binary across a major release update. Since part of the update
process spawned by mergemaster depends on `make' and the `/usr/share/mk'
files, you have to installworld before you can use the new megemaster
script.
The pre-buildworld mode of mergemaster (`mergemaster -p') should run
fine even with an old userland and old `/usr/share/mk' files. But you
should install everything before you run a full mergemaster update of
all files in `/etc'.
___
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"
Mergemaster Problem
I'm running mergemaster as root (-v -i -c) on an upgrade to
stable (I rebooted with the new kernel but have not done
the install) and can't run mergemaster, with result as follows:
Default is to use /var/tmp/temproot as is
How should I deal with this? [Use the existing /var/tmp/temproot] d
*** Deleting the old /var/tmp/temproot
*** Creating the temporary root environment in /var/tmp/temproot
*** /var/tmp/temproot ready for use
*** Creating and populating directory structure in /var/tmp/temproot
*** Press the [Enter] or [Return] key to continue
"/usr/src/etc/Makefile", line 34: Malformed conditional (${MK_AMD} !=
"no")
"/usr/src/etc/Makefile", line 36: if-less endif
"/usr/src/etc/Makefile", line 38: Malformed conditional (${MK_APM} !=
"no")
"/usr/src/etc/Makefile", line 40: if-less endif
"/usr/src/etc/Makefile", line 42: Malformed conditional (${MK_BSNMP} !=
"no")
"/usr/src/etc/Makefile", line 44: if-less endif
"/usr/src/etc/Makefile", line 46: Malformed conditional
(${MK_FREEBSD_UPDATE} != "no")
"/usr/src/etc/Makefile", line 48: if-less endif
"/usr/src/etc/Makefile", line 50: Malformed conditional (${MK_LOCATE} !=
"no")
"/usr/src/etc/Makefile", line 52: if-less endif
"/usr/src/etc/Makefile", line 58: Malformed conditional (${MK_MAIL} !=
"no")
"/usr/src/etc/Makefile", line 60: if-less endif
"/usr/src/etc/Makefile", line 79: Malformed conditional (${MK_PORTSNAP} !=
"no")
"/usr/src/etc/Makefile", line 81: if-less endif
"/usr/src/etc/Makefile", line 218: Malformed conditional (${MK_PPP} !=
"no")
"/usr/src/etc/Makefile", line 221: if-less endif
"/usr/src/etc/Makefile", line 222: Malformed conditional (${MK_MAIL} !=
"no")
"/usr/src/etc/Makefile", line 230: if-less endif
make: fatal errors encountered -- cannot continue
*** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to
the temproot environment
Any suggestions?
Annelise
___
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: mergemaster problem
Jack Raats wrote: after upgrade 6.3 to 7.0 mergemaster didn't do the job properly After a normal reboot I get a lot of Warnings like /etc/rc: WARNING: $variable_enable is not set properly - see rc.conf(5) HOw to solve this problem??? Thanks Jack Rerun mergemaster. When it asks you to [i]nstall the new /etc/defaults/rc.conf, [m]erge it or leave it for later. Choose i. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mergemaster problem
after upgrade 6.3 to 7.0 mergemaster didn't do the job properly After a normal reboot I get a lot of Warnings like /etc/rc: WARNING: $variable_enable is not set properly - see rc.conf(5) HOw to solve this problem??? Thanks Jack ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mergemaster problem
On 03/14/05 00:02:43, masterkev28 masterkev28 wrote: Hi, I didn't rebuild world, or kernel, however just some regular routine portupgrade -a. The problem is that no matter what I do with mergemaster, I get this error( also the same error occurs on another box of mine), and it started happening about a week ago after I did cvsup. It keeps complaining the line 76~80 in /usr/src/etc/Makefile, where I have no idea what's wrong with this file. Thanks, Kev Cvsup! Cvsup what, the stanard file to upgrade your base system? You don't need mergemaster unless you cvsup your base system, and if you did that and merged the new files, thats bad. You should rebuild the world and the kernel then install them. And don't cvsup unless you intend to upgrade your base system. That can put things out of sink. On Mon, 14 Mar 2005 02:29:10 +, Jason Henson <[EMAIL PROTECTED]> wrote: > On 03/13/05 17:08:56, masterkev28 masterkev28 wrote: > > Hello everyone, > > When I do mergemaster -ia, I get the following errors: > > > > *** The directory specified for the temporary root environment, > > /var/tmp/temproot, exists. This can be a security risk if > > untrusted > > users have access to the system. > > > > Why are you using -ia, they are th opposit in the man page. You > should: > > # make buildworld > # make buildkernel > # make installkernel > # reboot > After installkernel finishes successfully, you should boot in single > user mode (i.e. using boot -s from the loader prompt). Then run: > # mergemaster -p > # make installworld > # mergemaster > # reboot > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions- [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: mergemaster problem
Hi, I didn't rebuild world, or kernel, however just some regular routine portupgrade -a. The problem is that no matter what I do with mergemaster, I get this error( also the same error occurs on another box of mine), and it started happening about a week ago after I did cvsup. It keeps complaining the line 76~80 in /usr/src/etc/Makefile, where I have no idea what's wrong with this file. Thanks, Kev On Mon, 14 Mar 2005 02:29:10 +, Jason Henson <[EMAIL PROTECTED]> wrote: > On 03/13/05 17:08:56, masterkev28 masterkev28 wrote: > > Hello everyone, > > When I do mergemaster -ia, I get the following errors: > > > > *** The directory specified for the temporary root environment, > > /var/tmp/temproot, exists. This can be a security risk if > > untrusted > > users have access to the system. > > > > Why are you using -ia, they are th opposit in the man page. You > should: > > # make buildworld > # make buildkernel > # make installkernel > # reboot > After installkernel finishes successfully, you should boot in single > user mode (i.e. using boot -s from the loader prompt). Then run: > # mergemaster -p > # make installworld > # mergemaster > # reboot > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[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: mergemaster problem
On 03/13/05 17:08:56, masterkev28 masterkev28 wrote: Hello everyone, When I do mergemaster -ia, I get the following errors: *** The directory specified for the temporary root environment, /var/tmp/temproot, exists. This can be a security risk if untrusted users have access to the system. Why are you using -ia, they are th opposit in the man page. You should: # make buildworld # make buildkernel # make installkernel # reboot After installkernel finishes successfully, you should boot in single user mode (i.e. using boot -s from the loader prompt). Then run: # mergemaster -p # make installworld # mergemaster # reboot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mergemaster problem
Hello everyone,
When I do mergemaster -ia, I get the following errors:
*** The directory specified for the temporary root environment,
/var/tmp/temproot, exists. This can be a security risk if untrusted
users have access to the system.
*** Creating the temporary root environment in /var/tmp/temproot.0313.15.35.39
*** /var/tmp/temproot.0313.15.35.39 ready for use
*** Creating and populating directory structure in
/var/tmp/temproot.0313.15.35.39
"Makefile", line 76: Could not find bsd.endian.mk
"Makefile", line 77: Malformed conditional (${TARGET_ENDIANNESS} == "1234")
"Makefile", line 77: Need an operator
"Makefile", line 80: if-less elif
"Makefile", line 80: Need an operator
"Makefile", line 83: if-less else
"Makefile", line 83: Need an operator
"Makefile", line 85: if-less endif
"Makefile", line 85: Need an operator
make: fatal errors encountered -- cannot continue
*** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to
the temproot environment
And I checked the /usr/src/etc/Makefile( version: 1.341 2005/03/03),
starting at line 76, it has:
.include
.if ${TARGET_ENDIANNESS} == "1234"
CAP_MKDB_ENDIAN= -l
PWD_MKDB_ENDIAN= -L
.elif ${TARGET_ENDIANNESS} == "4321"
CAP_MKDB_ENDIAN= -b
PWD_MKDB_ENDIAN= -B
.else
CAP_MKDB_ENDIAN=
.endif
I believe it's the source of error, I tried commenting them out, but
mergemaster failed at some point.
The file bsd.endian.mk (version 1.2 2005/02/25) is in the path
/usr/src/share/mk/ as well.
Any idea?
Thanks.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mergemaster problem
Toomas Aas wrote: Hi! Date: Tue, 22 Oct 2002 11:57:44 -0700 From: Kent Stewart <[EMAIL PROTECTED]> Subject: Re: mergemaster problem [... about upgrading the world ...] If they fix a security related buffer overflow problem in one of the system libraries, you need to update all ports that use that library. Isn't that the case only with statically linked binaries? Yes! The problem is knowing which method they use. The normal assumption would be dynamic because it is less trouble and can be more efficient with respect to memory usage. The paranoid side of me, which worrys about security, would assume static unless told otherwise. Since I haven't rebuilt all of my old ports, I haven't worried about it too much :). I have never got that involved with a port make file with the exception of Code Crusader and I didn't pay attention to it. The port make files are so much more involved than anything I used on a vendor maintained OS. There was always a generator that you passed a directory and it created the basic make files for me. The first one I created on FreeBSD had 277 modules and was really painful to create. I think I did everything that I could do wrong first. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: mergemaster problem
At 01:43 PM 10/23/2002 +0300, you wrote: Hi! > Date: Tue, 22 Oct 2002 11:57:44 -0700 > From: Kent Stewart <[EMAIL PROTECTED]> > Subject: Re: mergemaster problem [... about upgrading the world ...] > If they fix a security related buffer overflow problem in one of the > system libraries, you need to update all ports that use that library. Isn't that the case only with statically linked binaries? I don't know exactly how that works, but after the upgrade (quite successful) all proggies work fine (I hope). I figure that any further updates to the programs will be taken care of by portupgrade. It always worked for me before :)) PJ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: mergemaster problem
Hi! > Date: Tue, 22 Oct 2002 11:57:44 -0700 > From: Kent Stewart <[EMAIL PROTECTED]> > Subject: Re: mergemaster problem [... about upgrading the world ...] > If they fix a security related buffer overflow problem in one of the > system libraries, you need to update all ports that use that library. Isn't that the case only with statically linked binaries? -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * Yes means No and No means Yes. Delete all files [Y]? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: mergemaster problem
I chanced it and it looks like it all worked. mergemaster seems to have worked ok. I was too lazy to do things manually. V. 4.7 booted up ok. Now to see if there are any quirks I have to fix. Thanks very much for your help. PJ. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: mergemaster problem
[EMAIL PROTECTED] wrote: At 10:01 AM 10/22/2002 -0700, you wrote: I must say, as I often have remarked, that the handbook is rather foggy - you often have to read a whole slew of things that are urelated before you get to the main point - I was trying to follow the manual, step by step - but it sure doesn't seem to work quite that way. :(( Part of the problem with the Handbook is that it covers most of the versions. I did vipw with the restored backed-up files and now I have passwd and will probably be ok. So, as I understand it, I should just run make buildwold from /usr/src, then build the new kernel and then do make installworld, then update the files not updated by make world etc, etc. as in the handbook. That, then, will upgrade my system to 4.7. Right? After you have installed the kernel, installed the world, and run mergemaster, you have the current release. Many people don't reboot into single user mode. I always do that. I want to know the kernel works before I do the installworld. I could probably exit from single user mode after I ran mergemaster but I do a reboot at that point. If I have added some new devices, I want the kernel to see them. As I need no changes to the programs I have installed (they're all up-to-date with portupgrade), I should just verify that the /etc/group, passwd and master.passwd files are conforming to the newer version. And this, as I understand, can be done by the mergemaster. I don't use mergemaster to update master.passwd but I do copy the header info from the location in /usr/tmp and insert it into the files I modify by hand. Once you have rebooted and are running the new version, you can run mergemaster again and it will tell you what files it wants to update. Some of that is results from a comparison of the cvs header information. You can make mergemaster ignore that file by updating the header information. I use information from mergemaster to update them manually. It tells you where all of the files are located and that makes it really easy to upgrade a file manually. If you have port programs that depend on system libraries, you need to rebuild the ports so they link to the new version. This is not always important. The port lsof is an exception that comes to mind. It knows when you have updated the system and not rebuilt lsof. It tells you about this everytime you run it. If they fix a security related buffer overflow problem in one of the system libraries, you need to update all ports that use that library. I haven't seen announcents that cover this kind of problem. I don't know if this is a problem. I know I have gone more than a release on some of my ports. Whether I should have rebuilt some of them was something I do not know. Some people do level upgrades by doing clean installs. They wipe the disks and reinstall everything. I use cvsup to follow RELENG_4 and know I have some old stuff still available. Portupgrade makes some of this really simple. It is sort of the mergemaster of the port world. I do a portsdb -uU after every cvsup of ports-all. There are programs that tell you what is out of date on your system. I just finished checking 4 machines and making sure they were all running the latest versions of the ports. I didn't rebuild everything. Keeping your ports current is important. The question is one of timing and I don't have an answer to that. I have started building packages as part of the make install. Checking the date in /usr/ports/packages/All will tell me which ports I haven't updated for a long time. The ones I use very often are also updated often. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: mergemaster problem
At 10:01 AM 10/22/2002 -0700, you wrote: I must say, as I often have remarked, that the handbook is rather foggy - you often have to read a whole slew of things that are urelated before you get to the main point - I was trying to follow the manual, step by step - but it sure doesn't seem to work quite that way. :(( I did vipw with the restored backed-up files and now I have passwd and will probably be ok. So, as I understand it, I should just run make buildwold from /usr/src, then build the new kernel and then do make installworld, then update the files not updated by make world etc, etc. as in the handbook. That, then, will upgrade my system to 4.7. Right? As I need no changes to the programs I have installed (they're all up-to-date with portupgrade), I should just verify that the /etc/group, passwd and master.passwd files are conforming to the newer version. And this, as I understand, can be done by the mergemaster. Thanks much. PJ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: mergemaster problem
[EMAIL PROTECTED] wrote: I want to upgrade FreeBSD from 4.62 to 4.7 so I can use openoffice. I find the instructions in the handbook incomplete: 21.4 Using make world In trying to use mergemaster, I find it incomprehensible as to what the program actually does and what I am supposed to direct it to do. It is not clear as to what is done with the master.passwd and group files and where they are installed or how they are modified. I tried to be ultra conservative and backed up the /etc/group and /etc/master.passwd files to *.old and then ran mergemaster. It was thereafter not clear who(what process or program) would use the new file (which, where) or how the files would be merged. I chose the 'm' option to merge the files, assuming that the existing passwords, users and groups would be merged into the new file. Then to verify, I entered the 'v' option; but this produced nothing. Thinking that the backups would be insurance, I then opted for 'i'. On exiting mergemaster, I chose to leave the temp files. I did not run the pwd_mkdb -p as suggested until after verifying the /etc directory and the /var/tmp/temproot/etc directories: SURPRISE the /etc/group, /etc/passwd and /etc/master.passwd files are empty. And there is nothintg in the /var/tmp/temproot/etc directory What in the world is going on here? I have not closed down or rebooted as I am afraid that the whole installation will be lshot to hell. What do I do? Will restoring the saved group and master.passwd files do anything? Then there is the empty passwd file. I suppose that running vipw and adduser might fix things... Also, there was no /etc/make.conf file. The installation has been pretty much "by the book" using portupgrade" ... Everything works just fine - Xfree86-4.2; cups, kde3; I just want to upgrade to 4.7 for openoffice. Please help You might read section "21.4.10 Update Files Not Updated by make world" of the Handbook. Mergemaster does the compares and produces a list for you to see that represents the diff between your current file and the new one produced by your buildworld. Vipw, for example, will update your password files and also update the password data base. People used to update /dev and not run MAKEDEV when they finished. The result was nothing changed and their system did not have the new devices. Mergemaster knows about most of these programs that need to be run after /etc has been updated and asks you if you want to finish the update. The normal choice is "y". If you change the version of sendmail, for example, and don't update the configuration files, you may not have a running sendmail when you have rebooted into your latest version of FreeBSD. My first encounter with mergemaster was, I think, in the FreeBSD-3.1 to 3.2 world. I was trying to follow the transition from one release level to the next. I was also updating /etc manually. They were introducing fixes faster than I could update /etc. Then, I discovered mergemaster and a typical installword session on my fast machines, which includes running mergemaster, requires less than 5 minutes of uptime. It is worth learning how to use it :). I think I am one of the few that won't let mergemaster modify master.passwd, groups, printcap, hosts*, and maybe a couple of other files. When it gets into the merge mode, I feel like I have funnel vision and can't cope with it. So, I read about changes for new users and etc. and add them before I run the buildworld. Some of this you can do with the -p option, but I still prefer looking at the files in 2 windows side by side on a different computer. You can do this from 2 x-window console sessions but I have 2 computers that don't run X and have gotten used to doing this from one central computer. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
mergemaster problem
I want to upgrade FreeBSD from 4.62 to 4.7 so I can use openoffice. I find the instructions in the handbook incomplete: 21.4 Using make world In trying to use mergemaster, I find it incomprehensible as to what the program actually does and what I am supposed to direct it to do. It is not clear as to what is done with the master.passwd and group files and where they are installed or how they are modified. I tried to be ultra conservative and backed up the /etc/group and /etc/master.passwd files to *.old and then ran mergemaster. It was thereafter not clear who(what process or program) would use the new file (which, where) or how the files would be merged. I chose the 'm' option to merge the files, assuming that the existing passwords, users and groups would be merged into the new file. Then to verify, I entered the 'v' option; but this produced nothing. Thinking that the backups would be insurance, I then opted for 'i'. On exiting mergemaster, I chose to leave the temp files. I did not run the pwd_mkdb -p as suggested until after verifying the /etc directory and the /var/tmp/temproot/etc directories: SURPRISE the /etc/group, /etc/passwd and /etc/master.passwd files are empty. And there is nothintg in the /var/tmp/temproot/etc directory What in the world is going on here? I have not closed down or rebooted as I am afraid that the whole installation will be lshot to hell. What do I do? Will restoring the saved group and master.passwd files do anything? Then there is the empty passwd file. I suppose that running vipw and adduser might fix things... Also, there was no /etc/make.conf file. The installation has been pretty much "by the book" using portupgrade" ... Everything works just fine - Xfree86-4.2; cups, kde3; I just want to upgrade to 4.7 for openoffice. Please help PJ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
