Karel Kulhavy <[EMAIL PROTECTED]> writes: > How do I figure out what local changes I did? Is there something > like the cvs diff command?
cvs diff would give you some useful info. I tend to use mergemaster plus pay attention to the upgrade notes. > I have the system over a year and if I needed to change something in > the config files then I just changed it and forgot it. one other way to do it is to untar etc.tgz somewhere else and run a diff on each file you may have changed. > "If you installed any packages on your system, you should upgrade > them after completing the upgrade of the base system." - I installed > a lot of packages on my system and have no idea what is their > complete list. pkg_info will give you a complete list of installed packages. > How do I figure that out and how do I discern between packages that > were already pre-installed by default and the ones I installed > explicitly? Then, how do I upgrade a package XXX? No packages are preinstalled by default. There's the base system and there's packages. I tend to set PKG_PATH to something sensible like the relevant packages directory on a nearby mirror and then use pkg_add -u (and possibly some other parameters) to upgrade the packages. If there are packages pkg_add doesn't find upgrade candidates for it will tell you. Typically that's about ports that you need to build locally such as some java related ones, acroread, opera and possibly others. > "Check with the application's upgrade guide for details." - is the > application upgrade guide something the application author publishes > or something that the OpenBSD project publishes? Where is it? That could be a number of differen things depending on the application and package. Packages that need some attention after an upgrade tend to display a message about what needs to be done at the end of upgrade/install. But then if there's a lot of packages to upgrade, those messages could scroll off the top of your screen too quickly for you to notice, so doing the upgrades from a script(1) session (producing a record of what happens on your terminal in a text file) is usually a good idea. When you no longer need the typescript file, rm is your friend too :) - P -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.datadok.no/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
