Re: CVSup update or upgrade
On Thu, Jan 31, 2008 at 07:57:49PM -0600, Chris typed: NOTE: I don't use mergemaster unless I go from say 6.3 to 7.0 Not wise. New features and fixes are applied to configuration files and rc scripts regu;arly. You'll probably miss them. STABLE is the security fix branch. Wrong. According to the handbook: 23.2.2.1 What Is FreeBSD-STABLE? FreeBSD-STABLE is our development branch from which major releases are made. Changes go into this branch at a different pace, and with the general assumption that they have first gone into FreeBSD-CURRENT for testing. This is still a development branch, however, and this means that at any given time, the sources for FreeBSD-STABLE may or may not be suitable for any particular purpose. It is simply another engineering development track, not a resource for end-users. RELENG_6 is STABLE RELENG_6_3 is for security fixes regards, Ruben ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVSup update or upgrade
On Fri, Feb 01, 2008 at 07:41:24AM -0500, Gerard wrote: On Thu, 31 Jan 2008 19:57:49 -0600 Chris [EMAIL PROTECTED] wrote: Assuming you went from 6.3-RELEASE to 6.3-STABLE and also assuming you do not have customization in /etc - here's what I do... After a cvsup of the src tree (ensuring I want the STABLE branch (*default release=cvs tag=RELENG_6) # cd /usr/src # make buildworld # make buildkernel KERNCONF=GENERIC (Assuming you use GENERIC) # make installkernel KERNCONF=GENERIC (Assuming you use GENERIC) # shutdown -r now (no need for Single-User Mode if YOU are the only user) You can just type: shutdown now to go into single user mode. It avoids the reboot sequence. Going to single user mode is the less important part of rebooting. The other part is that after the reboot you will be running the *new* kernel which might possibly be needed for a successful installworld. It is also a good test that the new kernel actually work. If the new kernel should fail to work it is fairly easy to use the old kernel instead. If you have already overwritten all userland programs with ones which require the new (non-working) kernel it can be difficult to recover from. Just going to single user mode without rebooting misses the point. The important thing is not to go into single user mode, it is to *reboot* into single user mode (or even into multi-user mode if you want to, but there are fewer things that can go wrong when going to single user mode.) # cd /usr/src # make installworld I prefer to use the following after make installworld mergemaster -i -v -U Read the man pages for mergemaster for further details. # shutdown -r now After rebooting, you might want to cd to the /usr/src directory and run: make delete-old-libs to clear out any garbage. It is not actually required however. -- Gerard [EMAIL PROTECTED] In the long run we are all dead. John Maynard Keynes -- 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: CVSup update or upgrade
On Fri, Feb 01, 2008 at 09:45:30AM -0500, Gerard wrote:
On Fri, 1 Feb 2008 15:14:59 +0100
Erik Trulsson [EMAIL PROTECTED] wrote:
{snip]
Going to single user mode is the less important part of rebooting.
The other part is that after the reboot you will be running the *new*
kernel which might possibly be needed for a successful installworld.
It is also a good test that the new kernel actually work. If the new
kernel should fail to work it is fairly easy to use the old kernel
instead. If you have already overwritten all userland programs with
ones which require the new (non-working) kernel it can be difficult
to recover from.
Just going to single user mode without rebooting misses the point.
The important thing is not to go into single user mode, it is to
*reboot* into single user mode (or even into multi-user mode if you
want to, but there are fewer things that can go wrong when going to
single user mode.)
From:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
From the same document:
23.4.9 Reboot into Single User Mode
You should reboot into single user mode to test the new kernel works. Do
this by following the instructions in Section 23.4.5
/usr/src/UPDATING (which contains the really official instructions for how
to upgrade) also tells you to reboot.
Just going into single user mode without rebooting is not very useful.
The section of the handbook you quote below should probably be rewritten
somewhat.
23.4.5 Drop to Single User Mode
You may want to compile the system in single user mode. Apart from the
obvious benefit of making things go slightly faster, reinstalling the
system will touch a lot of important system files, all the standard
system binaries, libraries, include files and so on. Changing these on
a running system (particularly if you have active users on the system
at the time) is asking for trouble.
Another method is to compile the system in multi-user mode, and then
drop into single user mode for the installation. If you would like to
do it this way, simply hold off on the following steps until the build
has completed. You can postpone dropping to single user mode until you
have to installkernel or installworld.
As the superuser, you can execute:
# shutdown now
from a running system, which will drop it to single user mode.
--
Gerard
[EMAIL PROTECTED]
The greatest productive force is human selfishness.
Robert Heinlein
--
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: CVSup update or upgrade
On Fri, 1 Feb 2008 15:14:59 +0100
Erik Trulsson [EMAIL PROTECTED] wrote:
{snip]
Going to single user mode is the less important part of rebooting.
The other part is that after the reboot you will be running the *new*
kernel which might possibly be needed for a successful installworld.
It is also a good test that the new kernel actually work. If the new
kernel should fail to work it is fairly easy to use the old kernel
instead. If you have already overwritten all userland programs with
ones which require the new (non-working) kernel it can be difficult
to recover from.
Just going to single user mode without rebooting misses the point.
The important thing is not to go into single user mode, it is to
*reboot* into single user mode (or even into multi-user mode if you
want to, but there are fewer things that can go wrong when going to
single user mode.)
From:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
23.4.5 Drop to Single User Mode
You may want to compile the system in single user mode. Apart from the
obvious benefit of making things go slightly faster, reinstalling the
system will touch a lot of important system files, all the standard
system binaries, libraries, include files and so on. Changing these on
a running system (particularly if you have active users on the system
at the time) is asking for trouble.
Another method is to compile the system in multi-user mode, and then
drop into single user mode for the installation. If you would like to
do it this way, simply hold off on the following steps until the build
has completed. You can postpone dropping to single user mode until you
have to installkernel or installworld.
As the superuser, you can execute:
# shutdown now
from a running system, which will drop it to single user mode.
--
Gerard
[EMAIL PROTECTED]
The greatest productive force is human selfishness.
Robert Heinlein
signature.asc
Description: PGP signature
Re: CVSup update or upgrade
On Thu, 31 Jan 2008 19:57:49 -0600 Chris [EMAIL PROTECTED] wrote: Assuming you went from 6.3-RELEASE to 6.3-STABLE and also assuming you do not have customization in /etc - here's what I do... After a cvsup of the src tree (ensuring I want the STABLE branch (*default release=cvs tag=RELENG_6) # cd /usr/src # make buildworld # make buildkernel KERNCONF=GENERIC (Assuming you use GENERIC) # make installkernel KERNCONF=GENERIC (Assuming you use GENERIC) # shutdown -r now (no need for Single-User Mode if YOU are the only user) You can just type: shutdown now to go into single user mode. It avoids the reboot sequence. # cd /usr/src # make installworld I prefer to use the following after make installworld mergemaster -i -v -U Read the man pages for mergemaster for further details. # shutdown -r now After rebooting, you might want to cd to the /usr/src directory and run:make delete-old-libs to clear out any garbage. It is not actually required however. -- Gerard [EMAIL PROTECTED] In the long run we are all dead. John Maynard Keynes signature.asc Description: PGP signature
Re: CVSup update or upgrade
On Friday 01 February 2008 00:47:12 Allen wrote: Now, this wouldn't work for some reason or another, but the system seemed to be doing just fine. I did uname -a and sure enough I had 6.3 Stable going. However, when typing kdm to load up that so I can use a gui, it no longer loads, at all, it pops up for a split second to just stop totally, and then gives me a message about the hostname. I thought it was odd, and XDM actually loads, but won't load X itself as it too goes out with errors about hostname. So the hostname isn't set, the clue would be that machine presents itself as amnesia. Check /etc/rc.conf so see if you set a hostname or if you use DHCP, check if the dhcp server gives you one. How this got lost in the upgrade, I don't know. mergemaster doesn't touch /etc/rc.conf, only /etc/defaults/rc.conf. I've been looking on FreeBSD.org but I don't fnid anything about this, but when did FreeBSD go from .tgz files to .tbz? I'm just wondering what happened as I thought it was atypo at first and realized every one of my books said .tbz and so did my screen heh. When libbz2 was brought into the base system, don't recall when exactly, somewhere around 5.0 I guess. tgz use gzip compression, tbz use bzip2 compression, which generally compresses better, but uses more CPU-time. FreeBSD can still read both though, it's just a change of default. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVSup update or upgrade
On Fri, 1 Feb 2008 14:12:43 +0100 Ruben de Groot [EMAIL PROTECTED] wrote: On Thu, Jan 31, 2008 at 07:57:49PM -0600, Chris typed: 23.2.2.1 What Is FreeBSD-STABLE? FreeBSD-STABLE is our development branch from which major releases are made. Changes go into this branch at a different pace, and with the general assumption that they have first gone into FreeBSD-CURRENT for testing. This is still a development branch, however, and this means that at any given time, the sources for FreeBSD-STABLE may or may not be suitable for any particular purpose. It is simply another engineering development track, not a resource for end-users. RELENG_6 is STABLE RELENG_6_3 is for security fixes I stand corrected. -- Best regards, Chris Emperor Palpatine: Everything that has transpired has done so according to my design. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
CVSup update or upgrade
Hello, I've been reading over my library of FreeBSD books, which I may add is impressive due to me buying EVERY book available on Freebsdmall and also buying the PowerPak to make sure my Library is complete, and also I've been reading the freebsd.org docs because I'm working on getting an upgrade to work properly. Here is what happened: I did as the website said and changed the cvsup example file which is the one I'm using, to a FreeBSD cvsup server, left most of it alone, because I wanted to use most packages, so I wanted basically every app available, and when rebooting, after doing this: # make buildworld # make buildkernel # make installkernel # reboot I booted in single user mode and tried this: # mergemaster -p # make installworld # mergemaster # reboot Now, this wouldn't work for some reason or another, but the system seemed to be doing just fine. I did uname -a and sure enough I had 6.3 Stable going. However, when typing kdm to load up that so I can use a gui, it no longer loads, at all, it pops up for a split second to just stop totally, and then gives me a message about the hostname. I thought it was odd, and XDM actually loads, but won't load X itself as it too goes out with errors about hostname. I don't have the exact message which I know is bad form on my part, but I decided to just try updating again as I was kind of wondering what RELEASE is like instead of stable. This is perfectly fine because the machine is NOT used as a server really, and is mainly for me to test out stuff and use FreeBSD more so I'm not worried about it breaking, or reinstalling the OS, it's no big deal, my reaqson for doing this the first time was mainly because pkg_add -r wouldn't work, I have 6.0 on the CDs I bought from the mall site, and I also have another 6.0 install disk as I bought a second copy, may seem odd but I like having more than one on CD (or in thie case 4 copies) but I like to help support the BSD people, so I do it. Anyway, does anyone have any idea? I'm using the web site for docs as my books seem to have different instructions all together which is odd but I also know that books coming up vs software coming out, you can't really keep books coming out at the same rate, so I decided to use the web docs for something like this to have more up to date info, so here it is since this message si looking rather sloppy: --I have install disks for FreeBSD 6.0 -- I don't mind reinstalling but would rather fix it and learn how -- I'm currently running an update again with cvsup as it says this is a better choice and option --I'm not a Unix wizard but I DO know enough to get around and dream of one day being a Unix hacker, that's a dream for now though, I came from using Windows and Linux, and still use both heh --IF I've borked up the system bad enough that a reinstall is the best option I really don't mind, I'd just like to know how to at least prevent this from happening again so I can stay up to date in FreeBSD I followed the instructions pretty much to the letter here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html The system has nothing really important on it yet as I set it up to learn more with so I can start using FreeBSD the way I do Linux, as a desktop to do my work and tests on. Thanks very much, and as I said, if I really screwed up or something, I can just reinstall. also, one more thing: Does anyone know how to make pkg_add -r package work again in a fresh install of FreeBSD 6.0? When I ran it after the install to grab something it said it didn't work and couldn't be found, and so I decided to investigate and found the reason to be the host it looks up is no longer there, so I just went to Freebsd.org and looked and found the server was renamed since 6.0 was released, and so I just updated everything for it to work better. Also, one last question: I've been looking on FreeBSD.org but I don't fnid anything about this, but when did FreeBSD go from .tgz files to .tbz? I'm just wondering what happened as I thought it was atypo at first and realized every one of my books said .tbz and so did my screen heh. Any info on that would be neat too :) Thanks VERY much! -Allen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVSup update or upgrade
On Thu, 31 Jan 2008 18:47:12 -0500 Allen [EMAIL PROTECTED] wrote: Hello, I've been reading over my library of FreeBSD books, which I may add is impressive due to me buying EVERY book available on Freebsdmall and also buying the PowerPak to make sure my Library is complete, and also I've been reading the freebsd.org docs because I'm working on getting an upgrade to work properly. Here is what happened: I did as the website said and changed the cvsup example file which is the one I'm using, to a FreeBSD cvsup server, left most of it alone, because I wanted to use most packages, so I wanted basically every app available, and when rebooting, after doing this: # make buildworld # make buildkernel # make installkernel # reboot Assuming you went from 6.3-RELEASE to 6.3-STABLE and also assuming you do not have customization in /etc - here's what I do... After a cvsup of the src tree (ensuring I want the STABLE branch (*default release=cvs tag=RELENG_6) # cd /usr/src # make buildworld # make buildkernel KERNCONF=GENERIC (Assuming you use GENERIC) # make installkernel KERNCONF=GENERIC (Assuming you use GENERIC) # shutdown -r now (no need for Single-User Mode if YOU are the only user) # cd /usr/src # make installworld # shutdown -r now NOTE: I don't use mergemaster unless I go from say 6.3 to 7.0 I booted in single user mode and tried this: # mergemaster -p # make installworld # mergemaster # reboot Now, this wouldn't work for some reason or another, but the system seemed to be doing just fine. I did uname -a and sure enough I had 6.3 Stable going. However, when typing kdm to load up that so I can use a gui, it no longer loads, at all, it pops up for a split second to just stop totally, and then gives me a message about the hostname. See above for your RELENG Tag I thought it was odd, and XDM actually loads, but won't load X itself as it too goes out with errors about hostname. You may need to update your ports tree and your installed packages since you went to STABLE I don't have the exact message which I know is bad form on my part, but I decided to just try updating again as I was kind of wondering what RELEASE is like instead of stable. STABLE is the security fix branch. *snip* Someone else may follow up the rest with you. -- Best regards, Chris Someone is standing on the ethernet cable, causeing a kink in the cable ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVSup update or upgrade
On Fri, 1 Feb 2008 02:21:42 + (UTC) Jona Joachim [EMAIL PROTECTED] wrote: On 2008-02-01, Chris [EMAIL PROTECTED] wrote: On Thu, 31 Jan 2008 18:47:12 -0500 Allen [EMAIL PROTECTED] wrote: Hello, I've been reading over my library of FreeBSD books, which I may add is impressive due to me buying EVERY book available on Freebsdmall and also buying the PowerPak to make sure my Library is complete, and also I've been reading the freebsd.org docs because I'm working on getting an upgrade to work properly. Here is what happened: I did as the website said and changed the cvsup example file which is the one I'm using, to a FreeBSD cvsup server, left most of it alone, because I wanted to use most packages, so I wanted basically every app available, and when rebooting, after doing this: # make buildworld # make buildkernel # make installkernel # reboot Assuming you went from 6.3-RELEASE to 6.3-STABLE and also assuming you do not have customization in /etc - here's what I do... After a cvsup of the src tree (ensuring I want the STABLE branch (*default release=cvs tag=RELENG_6) # cd /usr/src # make buildworld # make buildkernel KERNCONF=GENERIC (Assuming you use GENERIC) # make installkernel KERNCONF=GENERIC (Assuming you use GENERIC) # shutdown -r now (no need for Single-User Mode if YOU are the only user) Sorry but you're giving wrong advice here. *Always* drop to single user mode. You are almost never the only user on your machine when you're in multiuser mode. There will at least be root an your user account and probably others. I'm not giving advice - I'm simply stating what *I* do. See my words below. Assuming you went from 6.3-RELEASE to 6.3-STABLE and also assuming you do not have customization in /etc - here's what I do... Note the here's what I do... That does not sound like I'm advising any user to do what I do - only stating things based on my experiences. ... as to Single-User mode and mergemaster, here again, I can only comment on what I do and my experiences. I myself have never had a system failure due to not running mergemaster. Furthermore, I have never had issues not booting into Single-User mode to update my boxen. Of course, your mileage may vary. -- Best regards, Chris The lines are all busy (busied out, that is -- why let them in to begin with?). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVSup update or upgrade
On 2008-02-01, Chris [EMAIL PROTECTED] wrote: On Thu, 31 Jan 2008 18:47:12 -0500 Allen [EMAIL PROTECTED] wrote: Hello, I've been reading over my library of FreeBSD books, which I may add is impressive due to me buying EVERY book available on Freebsdmall and also buying the PowerPak to make sure my Library is complete, and also I've been reading the freebsd.org docs because I'm working on getting an upgrade to work properly. Here is what happened: I did as the website said and changed the cvsup example file which is the one I'm using, to a FreeBSD cvsup server, left most of it alone, because I wanted to use most packages, so I wanted basically every app available, and when rebooting, after doing this: # make buildworld # make buildkernel # make installkernel # reboot Assuming you went from 6.3-RELEASE to 6.3-STABLE and also assuming you do not have customization in /etc - here's what I do... After a cvsup of the src tree (ensuring I want the STABLE branch (*default release=cvs tag=RELENG_6) # cd /usr/src # make buildworld # make buildkernel KERNCONF=GENERIC (Assuming you use GENERIC) # make installkernel KERNCONF=GENERIC (Assuming you use GENERIC) # shutdown -r now (no need for Single-User Mode if YOU are the only user) Sorry but you're giving wrong advice here. *Always* drop to single user mode. You are almost never the only user on your machine when you're in multiuser mode. There will at least be root an your user account and probably others. # cd /usr/src # make installworld # shutdown -r now NOTE: I don't use mergemaster unless I go from say 6.3 to 7.0 *Always* use mergemaster. Default configuration is constantly changing slightly. It never happened to me that mergemaster had nothing to and I upgrade somewhat regularly. Not running mergemaster will sooner or later result in a broken system. It can be argued whether `mergemaster -p` has to be run everytime but just run it, it will never hurt you. I really recommend following the handbook step by step for this task unless you know exactly what you're doing. I booted in single user mode and tried this: # mergemaster -p # make installworld # mergemaster # reboot Now, this wouldn't work for some reason or another, but the system seemed to be doing just fine. I did uname -a and sure enough I had 6.3 Stable going. However, when typing kdm to load up that so I can use a gui, it no longer loads, at all, it pops up for a split second to just stop totally, and then gives me a message about the hostname. See above for your RELENG Tag I thought it was odd, and XDM actually loads, but won't load X itself as it too goes out with errors about hostname. You may need to update your ports tree and your installed packages since you went to STABLE I don't have the exact message which I know is bad form on my part, but I decided to just try updating again as I was kind of wondering what RELEASE is like instead of stable. STABLE is the security fix branch. *snip* Someone else may follow up the rest with you. Best regards, Jona -- I am chaos. I am the substance from which your artists and scientists build rhythms. I am the spirit with which your children and clowns laugh in happy anarchy. I am chaos. I am alive, and tell you that you are free. Eris, Goddess Of Chaos, Discord Confusion ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
