Re: upgrade 6.2.7 to 7.0.0-rc2

Am 06.10.2020 um 04:29 schrieb Timothy Wegner:
....
> 
> Erich, I checked the docs and apparently there's both a command line
> upgrade and one accessible via Webconf. Are these basically the same thing,
> and is that what you are talking about?

Yes, the webconf is mostly a wrapper around the CLI version.

 Would I have to go back to 6.2.7
> and then upgrade?

No, if you have a 7.0.0-xx running just let it run. If you are upgrading
from a real old version then sometimes upgrade is not foolproof, it has
evolved over the last few years.

 (I would think so). Can the upgrade tool upgrade to
> 7.0.0-rc2, or does it look for the release version? 7.0.0?

If you start upgrade with the --help option you will see the usage.

It will typicall look for the 'stable' version.

leafinstaller# upgrade -c
6.2.7
upgrade: upgrade terminated successfully

For example, for 7.0.0-rc2 you can use

upgrade -c --latest

leafinstaller# upgrade -c --latest
7.0.0-rc2
upgrade: upgrade terminated successfully

or

leafinstaller# upgrade -c --release 7.0.0-rc2
7.0.0-rc2
upgrade: upgrade terminated successfully

to check for the files. If you leave away the -c option it will go and
start the upgrade.

Usage: upgrade [-c][ -s | -v | --verbose][--stable | --latest |
--release x.y.z][-u | --use_apkg]

   -c                     just check the version on the server
   -s | --silent          run quietly
   -v | --verbose         be chatty about the progress
   --stable               upgrade to stable release
   --latest               upgrade to latest release
   --release x.y.z        upgrade to release x.y.z
   -u | --use_apkg        use apkg -u to handle modified packages
                          instead of the internal routines
   -h | --help            show this page

Mind you, upgrade relies heavily on the presence of patch.lrp on the
system.

> 
> The reason  I haven't tried the upgrade capability is that my simple minded
> approach of adding leaf.cfg and configdb.lrp to the new Leaf packages
> leaves my old configuration intact on the old usb, so if my upgrade doesn't
> work I just plug in the old usb, and I am back where I was. Of course I
> could always copy the old usb first and then upgrade.

I recommend a three partition set up on the media. Partition 1 for the
boot code, partition 2 for the standard set up and partition 3 for a
copy of the set up which can be selected from the console and be used
for either a backup copy or an alternative configuration.

> 
> I also appreciated Marko's and Bob's comments. It would be a good thing to
> start with the new packages and modify them as Marko does for a new major
> version (I have done this in the past). 

upgrade tries hard to do that for you, sometimes it fails on shorewall
but it leaves the affected files for inspection in /tmp. You can use
these files to find out what you need to correct manually.

If upgrade terminates without errors it will save the current
configuration. You can then reboot the box and check. If it detects
errors it _does_not_ save the configuration. This is basically what
would happen if you just keep leaf.cfg and configdb,lrp.

 I don't have Bob's problem of
> maintaining off-site boxes, my firewall is here in my office. I just need
> to mess with it when my wife is not using her computer!

Well, upgrade has been written with Bob's problem in mind.

> 
> Thanks again. I have been using Leaf since the Dave Cinege LRP days and
> appreciate it very much.

In that case you know all internals.

cheers

ET


-- 
Diese E-Mail wurde von AVG auf Viren geprüft.
http://www.avg.com



------------------------------------------------------------------------
leaf-user mailing list: [email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/