(RADIATOR) Clarification On Installing V.2.18.1 To V.2.18

[Hugh Irvine]

Hello Ingvar -

I keep the old configuration files too - I just change the sym-link to point 
to the current one. Either approach is fine - I was simply adding other 
alternatives to the discussion.

cheers

Hugh

On Wednesday 09 May 2001 16:58, Ingvar Berg (EIP) wrote:
> Hello Hugh,
>
> Nothing wrong with the wheather nowadays, +20 and sunny. Just about enough
> to keep the polar bears off the streets...
>
> Then to the serious business - the reason for my copying the old raddb
> directory to the new Radiator distribution is just that I like to be able
> to go back to the untouched pre-ugrade situation. And as disk space comes
> free these days, it's a cheap luxury. No big  deal though, as long as you
> know what you're doing you can always roll back...
>
> /Ingvar
>
> -----Original Message-----
> From: Hugh Irvine [mailto:hugh at open.com.au]
> Sent: den 9 maj 2001 08:43
> To: Ingvar Berg (EIP); 'Radiator Tech Support'
> Subject: Re: (RADIATOR) Clarification On Installing V.2.18.1 To V.2.18
>
>
>
> Hello Ingvar -
>
> Has it warmed up a bit since I saw you in Stockholm?
>
> Another approach (that I use) is to use symbolic links for both the
> Radiator release directory and the configuration file, so my start up
> scripts and so on do not have to change.
>
> regards
>
> Hugh
>
> On Wednesday 09 May 2001 15:51, Ingvar Berg (EIP) wrote:
> > An additional thing that I have found useful is to put the raddb
> > directory with config files directly below the ditribution directory.
> > Like F:\Radiator\Radiator-2.18\raddb.
> > This way, you can revert to the old state, including whatever config was
> > required then.
> >
> > /Ingvar
> >
> > -----Original Message-----
> > From: Hugh Irvine [mailto:hugh at open.com.au]
> > Sent: den 27 april 2001 04:57
> > To: Carlos P. Martinez; 'Radiator Tech Support'
> > Subject: Re: (RADIATOR) Clarification On Installing V.2.18.1 To V.2.18
> >
> >
> >
> > Hello Carlos -
> >
> > I have discussed this issue several times on the mailing list
> > (www.starport.net/~radiator). My suggestion is always to create a new
> > directory for every version of Radiator.
> >
> > In your situation I would do this:
> >
> > 	create a top-level directory for Radiator
> >
> > 	mkdir F:\Radiator
> >
> > 	cd to that directory
> >
> > 	cd F:\Radiator
> >
> > 	download the distributions to this directory
> >
> > 	unzip each distribution in this directory
> >
> > This way you will keep the versions seperate and you can change from one
> > to another much more easily.
> >
> > 	cd F:\Radiator\Radiator-2.18
> >
> > 	cd F:\Radiator\Radiator-2.18.1
> >
> > 	etc..
> >
> > hth
> >
> > Hugh
> >
> > On Friday 27 April 2001 04:42, Carlos P. Martinez wrote:
> > > Dear Radiator Community,
> > >
> > > I just saw the announcement from Open Systems and downloaded the new
> > > version of Radiator. However, being that I just start with Radiator
> > > about two weeks ago, I am very concern about what procedure to use in
> > > the upgrading from v2.18 to v2.18.1. I don't want to overwrite any
> > > files that I have already setup and configured to work on my system.
> > >
> > > I looked on Open System's web site for instructions on this process and
> > > I also looked for a readme file in the downloaded package, but I was
> > > not able to find one. On my test machine, I unzipped the v.2.18.1 file
> > > onto my v2.18 directory and found that it only made a Radiator-2.18.1
> > > sub-folder under my Radiator-2.18 folder. Likewise results when I
> > > unzipped the file to my root drive F:\.
> > >
> > > I then renamed my Radiator-2.18 folder to Radiator-2.18.1 and unzipped
> > > Radiator-2.18.1.tgz file to root of my F:\ drive. I checked the folders
> > > and found that the updated files were now in place.
> > >
> > > Question: Using this procedure to upgrade to Radiator -2.18.1, will any
> > > of my already configured files, such as radius.cfg be overwritten? Am I
> > > on target here with this procedure?
> > >
> > > I am very sorry for the long e-mail, but I feel that others in user
> > > community may the same problem(s) and questions.
> > >
> > > I thank the community in advance for its the kind attention and
> > > cooperation.
> > >
> > > Sincerely,
> > >
> > > Carlos
> > >
> > >
> > > Carlos P. Martinez | Microsoft Certified Professional
> > > Network/Systems Manager @
> > > PipeLine BROADBAND
> > > Office: 303-346-2885 | Cell: 720-291-9793
> > > E-mail Address: carlos at pipelinebroadband.com
> > >
> > > "Only those who risk going too far can
> > > possibly find out how far one can go."
> > >
> > > -T.S. Eliot
> > >
> > >
> > > ===
> > > Archive at http://www.starport.net/~radiator/
> > > Announcements on radiator-announce at open.com.au
> > > To unsubscribe, email 'majordomo at open.com.au' with
> > > 'unsubscribe radiator' in the body of the message.

-- 
Radiator: the most portable, flexible and configurable RADIUS server 
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.