Availability of Amanda Solaris10/Open Solaris package

[Paddy Sreenivasan-2]

Solaris package for recent release of Amanda, 2.6.0p2 is available for
download at
http://www.zmanda.com/download-amanda.php

Documentation is available at http://wiki.zmanda.com

thanks,
Paddy

--
Amanda http://amanda.zmanda.com
ZRM for MySQL http://www.zmanda.com/backup-mysql.html

[Nick Smith-5]

Hi Paddy,

It's great that there is a packaged version of Amanda again.

Why are you installing it /usr/libexec/*, /usr/bin & /var/lib/amanda?

I don't mean to be a troll but there are many standard (sic) places to
place third party software on Solaris such as /usr/sfw, /opt/csw,
/usr/local. I know of several sysadmins who would refuse to install the
package on the grounds of lack of separation of OS and third-part apps.

Does anyone know what *Sun* recommends? Personally I'd go for
/opt/<something>/*, /var/opt/amanda/*, /etc/opt/amanda but that's a
*personal* preference before somebody flames me ;-)

Regards,

Nick

p.s. I've also been playing with creating Solaris packages for 2.6.0.pX
  and have made some progress with getting clean installs of SMF
manifests. Let me know if you like me to contribute them.

Paddy Sreenivasan wrote:
> Solaris package for recent release of Amanda, 2.6.0p2 is available for
> download at
> http://www.zmanda.com/download-amanda.php
>
> Documentation is available at http://wiki.zmanda.com
>
> thanks,
> Paddy
>

[Paddy Sreenivasan-2]

On Tue, Sep 16, 2008 at 8:17 AM, Nick Smith <nick.smith@...> wrote:
> Hi Paddy,
>
> It's great that there is a packaged version of Amanda again.
>
> Why are you installing it /usr/libexec/*, /usr/bin & /var/lib/amanda?

I tried to keep the same location as Linux versions. See
http://wiki.zmanda.com/index.php/Amanda_packages_from_Zmanda_downloads_page

>
> I don't mean to be a troll but there are many standard (sic) places to place
> third party software on Solaris such as /usr/sfw, /opt/csw, /usr/local. I
> know of several sysadmins who would refuse to install the package on the
> grounds of lack of separation of OS and third-part apps.

If there is standard location for Solaris, please let us know. We
would be happy to incorporate it.

>
> Does anyone know what *Sun* recommends? Personally I'd go for
> /opt/<something>/*, /var/opt/amanda/*, /etc/opt/amanda but that's a
> *personal* preference before somebody flames me ;-)
>
> Regards,
>
> Nick
>
> p.s. I've also been playing with creating Solaris packages for 2.6.0.pX  and
> have made some progress with getting clean installs of SMF manifests. Let me
> know if you like me to contribute them.

Please feel free to send them to me. We will include it and recognize
you as the contributor in
the changelog file.

thanks,
Paddy

>
> Paddy Sreenivasan wrote:
>>
>> Solaris package for recent release of Amanda, 2.6.0p2 is available for
>> download at
>> http://www.zmanda.com/download-amanda.php
>>
>> Documentation is available at http://wiki.zmanda.com
>>
>> thanks,
>> Paddy
>>
>

--
Amanda http://amanda.zmanda.com
ZRM for MySQL http://www.zmanda.com/backup-mysql.html

[Peter Kunst-2]

Hi amanda users,

On 09/16/2008 06:46 PM, Paddy Sreenivasan wrote:
> On Tue, Sep 16, 2008 at 8:17 AM, Nick Smith <nick.smith@...> wrote:

> If there is standard location for Solaris, please let us know. We
> would be happy to incorporate it.
>
>> Does anyone know what *Sun* recommends? Personally I'd go for
>> /opt/<something>/*, /var/opt/amanda/*, /etc/opt/amanda but that's a
>> *personal* preference before somebody flames me ;-)

i fully agree to Nick's suggestions, doing Solaris admin tasks since
over 12 years ago. Take a look at newer apache installs provided by Sun,
they do it the same way now.

>> p.s. I've also been playing with creating Solaris packages for 2.6.0.pX  and
>> have made some progress with getting clean installs of SMF manifests. Let me
>> know if you like me to contribute them.
>
> Please feel free to send them to me. We will include it and recognize
> you as the contributor in
> the changelog file.

What about inetconv(1M) for fresh/new installs ? It's as simple as
adding another line into standard inetd.conf and then run inetconv, as
well as running e.g. on a client:

 inetadm -m svc:/network/amanda/udp:default \
 "exec=/opt/amanda/libexec/amandad -auth=foobar ..."

whenever upgrading. Don't forget to upgrade amidxtape and amandaidx on a
server.

 Regards,
 Peter

[Chris Hoogendyk]

Paddy Sreenivasan wrote:

> On Tue, Sep 16, 2008 at 8:17 AM, Nick Smith <nick.smith@...> wrote:
>  
>> Hi Paddy,
>>
>> It's great that there is a packaged version of Amanda again.
>>
>> Why are you installing it /usr/libexec/*, /usr/bin & /var/lib/amanda?
>>    
>
> I tried to keep the same location as Linux versions. See
> http://wiki.zmanda.com/index.php/Amanda_packages_from_Zmanda_downloads_page
>  
>> I don't mean to be a troll but there are many standard (sic) places to place
>> third party software on Solaris such as /usr/sfw, /opt/csw, /usr/local. I
>> know of several sysadmins who would refuse to install the package on the
>> grounds of lack of separation of OS and third-part apps.
>>    
>
> If there is standard location for Solaris, please let us know. We
> would be happy to incorporate it.
>  
>> Does anyone know what *Sun* recommends? Personally I'd go for
>> /opt/<something>/*, /var/opt/amanda/*, /etc/opt/amanda but that's a
>> *personal* preference before somebody flames me ;-)

Unfortunately, it isn't very standardized for third party software.

I prefer to stay away from /opt/sfw, because that's where stuff that Sun
chose to include in the Solaris 10 install goes. Patches from Sun also
apply to those.

Sunfreeware, which I have used a fair bit, tends to go almost entirely
with /usr/local, putting things in /usr/local/(bin, doc, info, lib, man,
share and so on).

I've tended to follow Sunfreeware's precedence when I build my own
stuff. Then I can use LD_LIBRARY_PATH, PATH, and crle to control how
things get accessed. By putting /usr/local/lib in front of /usr/sfw/lib,
I get the things I've added as a preference, but still fall back to what
Sun did if I didn't "over-ride" it. In Solaris 10 with the new T2 based
servers such as the T5220, this is particularly critical. Sun has
provided a tie-in from their version of openssl to the on chip
cryptographic accelerators. Anything that is built pointing to their
libraries will get that speed boost (Apache, sendmail, Amanda). If I
tried to build that portion myself, I would either have to know a lot
more about the low level configuration or I would lose that
acceleration. I'm also playing with gccfss from Sun, which is optimized
specifically for the T2 based systems.

I should have feedback to the list soon about Amanda in this build
environment.


---------------

Chris Hoogendyk

-
   O__  ---- Systems Administrator
  c/ /'_ --- Biology & Geology Departments
 (*) \(*) -- 140 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst

<hoogendyk@...>

---------------

Erdös 4

[Chris Hoogendyk]

oops, slight mistake in my posting. -- Chris H.

Chris Hoogendyk wrote:

> Paddy Sreenivasan wrote:
>> On Tue, Sep 16, 2008 at 8:17 AM, Nick Smith <nick.smith@...>
>> wrote:
>>  
>>> Hi Paddy,
>>>
>>> It's great that there is a packaged version of Amanda again.
>>>
>>> Why are you installing it /usr/libexec/*, /usr/bin & /var/lib/amanda?
>>>    
>>
>> I tried to keep the same location as Linux versions. See
>> http://wiki.zmanda.com/index.php/Amanda_packages_from_Zmanda_downloads_page 
>>
>>  
>>> I don't mean to be a troll but there are many standard (sic) places
>>> to place
>>> third party software on Solaris such as /usr/sfw, /opt/csw,
>>> /usr/local. I
>>> know of several sysadmins who would refuse to install the package on
>>> the
>>> grounds of lack of separation of OS and third-part apps.  
>>
>> If there is standard location for Solaris, please let us know. We
>> would be happy to incorporate it.
>>  
>>> Does anyone know what *Sun* recommends? Personally I'd go for
>>> /opt/<something>/*, /var/opt/amanda/*, /etc/opt/amanda but that's a
>>> *personal* preference before somebody flames me ;-)
>
>
> Unfortunately, it isn't very standardized for third party software.

oops, ***** the following should have said /usr/sfw, NOT /opt/sfw *****

> I prefer to stay away from /opt/sfw, because that's where stuff that
> Sun chose to include in the Solaris 10 install goes. Patches from Sun
> also apply to those.
>
> Sunfreeware, which I have used a fair bit, tends to go almost entirely
> with /usr/local, putting things in /usr/local/(bin, doc, info, lib,
> man, share and so on).
>
> I've tended to follow Sunfreeware's precedence when I build my own
> stuff. Then I can use LD_LIBRARY_PATH, PATH, and crle to control how
> things get accessed. By putting /usr/local/lib in front of
> /usr/sfw/lib, I get the things I've added as a preference, but still
> fall back to what Sun did if I didn't "over-ride" it. In Solaris 10
> with the new T2 based servers such as the T5220, this is particularly
> critical. Sun has provided a tie-in from their version of openssl to
> the on chip cryptographic accelerators. Anything that is built
> pointing to their libraries will get that speed boost (Apache,
> sendmail, Amanda). If I tried to build that portion myself, I would
> either have to know a lot more about the low level configuration or I
> would lose that acceleration. I'm also playing with gccfss from Sun,
> which is optimized specifically for the T2 based systems.
>
> I should have feedback to the list soon about Amanda in this build
> environment.
>
>
> ---------------
>
> Chris Hoogendyk
>
> -
>   O__  ---- Systems Administrator
>  c/ /'_ --- Biology & Geology Departments
> (*) \(*) -- 140 Morrill Science Center
> ~~~~~~~~~~ - University of Massachusetts, Amherst
> <hoogendyk@...>
>
> ---------------
> Erdös 4

--
---------------

Chris Hoogendyk

-
   O__  ---- Systems Administrator
  c/ /'_ --- Biology & Geology Departments
 (*) \(*) -- 140 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst

<hoogendyk@...>

---------------

Erdös 4

[Martin.Hepworth]

Chris

Spent the last day or so fighting with amanda and sol 10...so here's an idea.

Is the gnu project "stow" still around? This is/was really useful in splitting out stuff and bringing back to /usr/local.

--
martin

-----Original Message-----
From: Chris Hoogendyk <hoogendyk@...>
Sent: Tuesday, September 16, 2008 7:42 PM
To: AMANDA users <amanda-users@...>
Subject: Re: Availability of Amanda Solaris10/Open Solaris package



Paddy Sreenivasan wrote:

> On Tue, Sep 16, 2008 at 8:17 AM, Nick Smith <nick.smith@...> wrote:
>  
>> Hi Paddy,
>>
>> It's great that there is a packaged version of Amanda again.
>>
>> Why are you installing it /usr/libexec/*, /usr/bin & /var/lib/amanda?
>>    
>
> I tried to keep the same location as Linux versions. See
> http://wiki.zmanda.com/index.php/Amanda_packages_from_Zmanda_downloads_page
>  
>> I don't mean to be a troll but there are many standard (sic) places to place
>> third party software on Solaris such as /usr/sfw, /opt/csw, /usr/local. I
>> know of several sysadmins who would refuse to install the package on the
>> grounds of lack of separation of OS and third-part apps.
>>    
>
> If there is standard location for Solaris, please let us know. We
> would be happy to incorporate it.
>  
>> Does anyone know what *Sun* recommends? Personally I'd go for
>> /opt/<something>/*, /var/opt/amanda/*, /etc/opt/amanda but that's a
>> *personal* preference before somebody flames me ;-)

Unfortunately, it isn't very standardized for third party software.

I prefer to stay away from /opt/sfw, because that's where stuff that Sun chose to include in the Solaris 10 install goes. Patches from Sun also apply to those.

Sunfreeware, which I have used a fair bit, tends to go almost entirely with /usr/local, putting things in /usr/local/(bin, doc, info, lib, man, share and so on).

I've tended to follow Sunfreeware's precedence when I build my own stuff. Then I can use LD_LIBRARY_PATH, PATH, and crle to control how things get accessed. By putting /usr/local/lib in front of /usr/sfw/lib, I get the things I've added as a preference, but still fall back to what Sun did if I didn't "over-ride" it. In Solaris 10 with the new T2 based servers such as the T5220, this is particularly critical. Sun has provided a tie-in from their version of openssl to the on chip cryptographic accelerators. Anything that is built pointing to their libraries will get that speed boost (Apache, sendmail, Amanda). If I tried to build that portion myself, I would either have to know a lot more about the low level configuration or I would lose that acceleration. I'm also playing with gccfss from Sun, which is optimized specifically for the T2 based systems.

I should have feedback to the list soon about Amanda in this build environment.


---------------

Chris Hoogendyk

-
   O__  ---- Systems Administrator
  c/ /'_ --- Biology & Geology Departments
 (*) \(*) -- 140 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst
<hoogendyk@...>

---------------
Erdös 4



**********************************************************************
Confidentiality : This e-mail and any attachments are intended for the
addressee only and may be confidential. If they come to you in error
you must take no action based on them, nor must you copy or show them
to anyone. Please advise the sender by replying to this e-mail
immediately and then delete the original from your computer.
Opinion : Any opinions expressed in this e-mail are entirely those of
the author and unless specifically stated to the contrary, are not
necessarily those of the author's employer.
Security Warning : Internet e-mail is not necessarily a secure
communications medium and can be subject to data corruption. We advise
that you consider this fact when e-mailing us.
Viruses : We have taken steps to ensure that this e-mail and any
attachments are free from known viruses but in keeping with good
computing practice, you should ensure that they are virus free.

Red Lion 49 Ltd T/A Solid State Logic
Registered as a limited company in England and Wales
(Company No:5362730)
Registered Office: 25 Spring Hill Road, Begbroke, Oxford OX5 1RU,
United Kingdom
**********************************************************************

[Nick Smith-5]

Chris Hoogendyk wrote:
>
>
> Paddy Sreenivasan wrote:
>> On Tue, Sep 16, 2008 at 8:17 AM, Nick Smith <nick.smith@...> wrote:
[snip]

>> I tried to keep the same location as Linux versions. See
>> http://wiki.zmanda.com/index.php/Amanda_packages_from_Zmanda_downloads_page 
>>
>>  
>>> I don't mean to be a troll but there are many standard (sic) places
>>> to place
>>> third party software on Solaris such as /usr/sfw, /opt/csw,
>>> /usr/local. I
>>> know of several sysadmins who would refuse to install the package on the
>>> grounds of lack of separation of OS and third-part apps.
>>>    
>>
>> If there is standard location for Solaris, please let us know. We
>> would be happy to incorporate it.
>>  
>>> Does anyone know what *Sun* recommends? Personally I'd go for
>>> /opt/<something>/*, /var/opt/amanda/*, /etc/opt/amanda but that's a
>>> *personal* preference before somebody flames me ;-)
>
>
> Unfortunately, it isn't very standardized for third party software.
>

So true! Isn't just maddening that your have can have three or more
versions of the same shared (sic) libraries in a Solaris 10
installation, in say : /usr/local/lib /usr/sfw/lib /opt/sun/lib
/opt/csw/lib etc??

> I prefer to stay away from /opt/sfw, because that's where stuff that Sun
> chose to include in the Solaris 10 install goes. Patches from Sun also
> apply to those.
>
How would you view putting the install into say /opt/amanda? Yes, it
requires a specialist path setting but Amanda is not for general users
anyway.

> Sunfreeware, which I have used a fair bit, tends to go almost entirely
> with /usr/local, putting things in /usr/local/(bin, doc, info, lib, man,
> share and so on).
>
Agreed! The /usr/local is according to Sun too much BSD like and
*deprecated* but I've also be using it for years.

> I've tended to follow Sunfreeware's precedence when I build my own
> stuff. Then I can use LD_LIBRARY_PATH, PATH, and crle to control how
> things get accessed. By putting /usr/local/lib in front of /usr/sfw/lib,
> I get the things I've added as a preference, but still fall back to what
> Sun did if I didn't "over-ride" it. In Solaris 10 with the new T2 based
> servers such as the T5220, this is particularly critical. Sun has
> provided a tie-in from their version of openssl to the on chip
> cryptographic accelerators. Anything that is built pointing to their
> libraries will get that speed boost (Apache, sendmail, Amanda). If I
> tried to build that portion myself, I would either have to know a lot
> more about the low level configuration or I would lose that
> acceleration. I'm also playing with gccfss from Sun, which is optimized
> specifically for the T2 based systems.
>

I've built Amanda entirely referencing Solaris libraries (with the
exception of libreadline) using Studio 12 (1). Wouldn't this solve your
problem? So are you building Amanda specifically for the T2 processor?

Regards,

Nick

(1) I've promised to document the build environment on zmanda but
haven't got around to it yet.

[Paul Bijnens]

On 2008-09-16 21:41, Martin.Hepworth wrote:
>
> Is the gnu project "stow" still around? This is/was really useful in splitting out stuff and bringing back to /usr/local.


I'm still using "graft" for some packages, especially those where I
need to be able to quickly fall back to a previous version, within
a couple of seconds.  (Like some additional packages on my mailserver
and as a matter of fact, for those servers where I compile amanda
myself instead of using an rpm, and on my Solaris machines).

I switched from "stow" to "graft" long time ago, mainly because
stows assumes it's the only owner of the

http://www.gormand.com.au/peters/tools/graft/graft.html

(there is also a description of similar systems in section, "research")


--
Paul Bijnens, xplanation Technology Services        Tel  [phone]
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM    Fax  [phone]
http://www.xplanation.com/          email:  Paul.Bijnens@...
***********************************************************************
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out          *
***********************************************************************

[Nick Smith-5]

Paddy Sreenivasan wrote:

> On Tue, Sep 16, 2008 at 8:17 AM, Nick Smith <nick.smith@...> wrote:
>> Hi Paddy,
>>
>> It's great that there is a packaged version of Amanda again.
>>
>> Why are you installing it /usr/libexec/*, /usr/bin & /var/lib/amanda?
>
> I tried to keep the same location as Linux versions. See
> http://wiki.zmanda.com/index.php/Amanda_packages_from_Zmanda_downloads_page
>
>> I don't mean to be a troll but there are many standard (sic) places to place
>> third party software on Solaris such as /usr/sfw, /opt/csw, /usr/local. I
>> know of several sysadmins who would refuse to install the package on the
>> grounds of lack of separation of OS and third-part apps.
>
> If there is standard location for Solaris, please let us know. We
> would be happy to incorporate it.
>

Hi Paddy,

I'm not sure that coping the Linux directory structure is the best way
due to the OS specific directory "standards" and also the differing way
that Linux & Solaris are administered.

As you mentioned that there is no magic-bullet standard directory
structure for Solaris but I must sya that personally I don't like things
in /usr/{bin,lib} depending on packages in /opt.

What is the opinion of other Amanda administrators?

>> Does anyone know what *Sun* recommends? Personally I'd go for
>> /opt/<something>/*, /var/opt/amanda/*, /etc/opt/amanda but that's a
>> *personal* preference before somebody flames me ;-)
>>
>> Regards,
>>
>> Nick
[snip]

>
> thanks,
> Paddy
>> Paddy Sreenivasan wrote:
>>> Solaris package for recent release of Amanda, 2.6.0p2 is available for
>>> download at
>>> http://www.zmanda.com/download-amanda.php
>>>
>>> Documentation is available at http://wiki.zmanda.com
>>>
>>> thanks,
>>> Paddy
>>>
>

Anyway, should we move this thread to the amanda-hackers list?

Regards,

Nick

[Nick Smith-5]

Paddy Sreenivasan wrote:

> On Tue, Sep 16, 2008 at 8:17 AM, Nick Smith <nick.smith@...> wrote:
>> Hi Paddy,
>>
>> It's great that there is a packaged version of Amanda again.
>>
>> Why are you installing it /usr/libexec/*, /usr/bin & /var/lib/amanda?
>
> I tried to keep the same location as Linux versions. See
> http://wiki.zmanda.com/index.php/Amanda_packages_from_Zmanda_downloads_page
>
>> I don't mean to be a troll but there are many standard (sic) places to place
>> third party software on Solaris such as /usr/sfw, /opt/csw, /usr/local. I
>> know of several sysadmins who would refuse to install the package on the
>> grounds of lack of separation of OS and third-part apps.
>
> If there is standard location for Solaris, please let us know. We
> would be happy to incorporate it.
>

/usr/local - Sunfreeware -> old deprecated BSD structure but still
functional
/opt/csw - Blastwave / OpenCSW packages
/opt/sun - SUN applications
/opt - mix of SUN and third-party apps (like Collabnet stuff)

I understand your wish to keep the same directory structures as Linux
but I have the following reservations about this issue.

1. Solaris Admins aren't used (or normally) happy about anything getting
  installed into /usr/*. Solaris isn't Linux and most Sys Admins either
use only one of the OSs or then are likely to understand that
differences between the installation structures are necessary.

2. The Amanda packages depend on CSW* packages in /opt - a horrible
reverse dependency in my opinion.

3. The standard OpenSolaris (ZFS) install provides a /opt filesystem
specifically for third-party software such as Amanda. This filesystem is
guaranteed to be unaffected by BE updates (*probably* wouldn't affect
Amanda anyway but you never know...)

4. On machines with virtual machines maybe Admins would want to share
the /opt filesystem between all the VMs and therefore would have only to
update Amanda once on the Dom0 (except for refreshing the amanda service
etc). Can anyone comment as my knowledge of VM administration is slight.

My *personal* suggestion would be to use /opt/amanda/*, /etc/opt/amanda
and /var/opt/amanda.

Please understands these are just my views and suggestions.

What would other users of Solaris think about this? The more comments
the better!

>> Does anyone know what *Sun* recommends? Personally I'd go for
>> /opt/<something>/*, /var/opt/amanda/*, /etc/opt/amanda but that's a
>> *personal* preference before somebody flames me ;-)
>>
>> Regards,
>>
>> Nick
>>
>> p.s. I've also been playing with creating Solaris packages for 2.6.0.pX  and
>> have made some progress with getting clean installs of SMF manifests. Let me
>> know if you like me to contribute them.
>
> Please feel free to send them to me. We will include it and recognize
> you as the contributor in
> the changelog file.
>
> thanks,
> Paddy
>

Regards,

Nick

[Jon LaBadie]

On Tue, Sep 30, 2008 at 05:10:53PM +0200, Nick Smith wrote:

>
> Paddy Sreenivasan wrote:
> >On Tue, Sep 16, 2008 at 8:17 AM, Nick Smith <nick.smith@...> wrote:
> >>Hi Paddy,
> >>
> >>It's great that there is a packaged version of Amanda again.
> >>
> >>Why are you installing it /usr/libexec/*, /usr/bin & /var/lib/amanda?
> >
> >I tried to keep the same location as Linux versions. See
> >http://wiki.zmanda.com/index.php/Amanda_packages_from_Zmanda_downloads_page
> >
> >>I don't mean to be a troll but there are many standard (sic) places to
> >>place
> >>third party software on Solaris such as /usr/sfw, /opt/csw, /usr/local. I
> >>know of several sysadmins who would refuse to install the package on the
> >>grounds of lack of separation of OS and third-part apps.
> >
> >If there is standard location for Solaris, please let us know. We
> >would be happy to incorporate it.
> >
>
> /usr/local - Sunfreeware -> old deprecated BSD structure but still
> functional
> /opt/csw - Blastwave / OpenCSW packages
> /opt/sun - SUN applications
> /opt - mix of SUN and third-party apps (like Collabnet stuff)
>
> I understand your wish to keep the same directory structures as Linux
> but I have the following reservations about this issue.
>
> 1. Solaris Admins aren't used (or normally) happy about anything getting
>  installed into /usr/*. Solaris isn't Linux and most Sys Admins either
> use only one of the OSs or then are likely to understand that
> differences between the installation structures are necessary.
>
> 2. The Amanda packages depend on CSW* packages in /opt - a horrible
> reverse dependency in my opinion.
>
> 3. The standard OpenSolaris (ZFS) install provides a /opt filesystem
> specifically for third-party software such as Amanda. This filesystem is
> guaranteed to be unaffected by BE updates (*probably* wouldn't affect
> Amanda anyway but you never know...)
>
> 4. On machines with virtual machines maybe Admins would want to share
> the /opt filesystem between all the VMs and therefore would have only to
> update Amanda once on the Dom0 (except for refreshing the amanda service
> etc). Can anyone comment as my knowledge of VM administration is slight.
>
> My *personal* suggestion would be to use /opt/amanda/*, /etc/opt/amanda
> and /var/opt/amanda.
>
> Please understands these are just my views and suggestions.
>
> What would other users of Solaris think about this? The more comments
> the better!
>

+1 for all 4 points and your personal suggestion.

jl
--
Jon H. LaBadie                  jon@...
 JG Computing
 12027 Creekbend Drive [phone]
 Reston, VA  20194 [phone] (fax)

[Paddy Sreenivasan-2]

Nick, Jon and others,

I had posted the directory structure question to Open Solaris
discussion list. Many Sun employees read it.
The general answer was to follow filesystem(5) man page.

I read the man page and updated the wiki with the locations being
considered. See
http://wiki.zmanda.com/index.php/Amanda_packages_from_Zmanda_downloads_page#Installation_directories

Next solaris builds will use these locations.

thanks
Paddy

On Tue, Sep 30, 2008 at 8:10 AM, Nick Smith <nick.smith@...> wrote:

>
> Paddy Sreenivasan wrote:
>>
>> On Tue, Sep 16, 2008 at 8:17 AM, Nick Smith <nick.smith@...> wrote:
>>>
>>> Hi Paddy,
>>>
>>> It's great that there is a packaged version of Amanda again.
>>>
>>> Why are you installing it /usr/libexec/*, /usr/bin & /var/lib/amanda?
>>
>> I tried to keep the same location as Linux versions. See
>>
>> http://wiki.zmanda.com/index.php/Amanda_packages_from_Zmanda_downloads_page
>>
>>> I don't mean to be a troll but there are many standard (sic) places to
>>> place
>>> third party software on Solaris such as /usr/sfw, /opt/csw, /usr/local. I
>>> know of several sysadmins who would refuse to install the package on the
>>> grounds of lack of separation of OS and third-part apps.
>>
>> If there is standard location for Solaris, please let us know. We
>> would be happy to incorporate it.
>>
>
> /usr/local - Sunfreeware -> old deprecated BSD structure but still
> functional
> /opt/csw - Blastwave / OpenCSW packages
> /opt/sun - SUN applications
> /opt - mix of SUN and third-party apps (like Collabnet stuff)
>
> I understand your wish to keep the same directory structures as Linux but I
> have the following reservations about this issue.
>
> 1. Solaris Admins aren't used (or normally) happy about anything getting
>  installed into /usr/*. Solaris isn't Linux and most Sys Admins either use
> only one of the OSs or then are likely to understand that differences
> between the installation structures are necessary.
>
> 2. The Amanda packages depend on CSW* packages in /opt - a horrible reverse
> dependency in my opinion.
>
> 3. The standard OpenSolaris (ZFS) install provides a /opt filesystem
> specifically for third-party software such as Amanda. This filesystem is
> guaranteed to be unaffected by BE updates (*probably* wouldn't affect Amanda
> anyway but you never know...)
>
> 4. On machines with virtual machines maybe Admins would want to share the
> /opt filesystem between all the VMs and therefore would have only to update
> Amanda once on the Dom0 (except for refreshing the amanda service etc). Can
> anyone comment as my knowledge of VM administration is slight.
>
> My *personal* suggestion would be to use /opt/amanda/*, /etc/opt/amanda and
> /var/opt/amanda.
>
> Please understands these are just my views and suggestions.
>
> What would other users of Solaris think about this? The more comments the
> better!
>
>>> Does anyone know what *Sun* recommends? Personally I'd go for
>>> /opt/<something>/*, /var/opt/amanda/*, /etc/opt/amanda but that's a
>>> *personal* preference before somebody flames me ;-)
>>>
>>> Regards,
>>>
>>> Nick
>>>
>>> p.s. I've also been playing with creating Solaris packages for 2.6.0.pX
>>>  and
>>> have made some progress with getting clean installs of SMF manifests. Let
>>> me
>>> know if you like me to contribute them.
>>
>> Please feel free to send them to me. We will include it and recognize
>> you as the contributor in
>> the changelog file.
>>
>> thanks,
>> Paddy
>>
>
> Regards,
>
> Nick
>

--
Amanda http://amanda.zmanda.com
ZRM for MySQL http://www.zmanda.com/backup-mysql.html

[Nick Smith-5]

Paddy Sreenivasan wrote:

> Nick, Jon and others,
>
> I had posted the directory structure question to Open Solaris
> discussion list. Many Sun employees read it.
> The general answer was to follow filesystem(5) man page.
>
> I read the man page and updated the wiki with the locations being
> considered. See
> http://wiki.zmanda.com/index.php/Amanda_packages_from_Zmanda_downloads_page#Installation_directories
>
> Next solaris builds will use these locations.
>
> thanks
> Paddy
>

[snip thread history]

Hi Paddy,

Great! I have no issues with the proposed directory structure at all!

Regards & Many Thanks,

Nick

p.s. I'll get around to send you some SMF manifest installation stuff soon.

[Paddy Sreenivasan-2]

I have uploaded latest 2.6.1alpha Solaris 10 packages with new
directory structure at
http://www.zmanda.com/community-builds.php

Please let us know if there are problems.

Paddy

On Thu, Oct 2, 2008 at 5:44 AM, Nick Smith <nick.smith@...> wrote:

>
> Paddy Sreenivasan wrote:
>>
>> Nick, Jon and others,
>>
>> I had posted the directory structure question to Open Solaris
>> discussion list. Many Sun employees read it.
>> The general answer was to follow filesystem(5) man page.
>>
>> I read the man page and updated the wiki with the locations being
>> considered. See
>>
>> http://wiki.zmanda.com/index.php/Amanda_packages_from_Zmanda_downloads_page#Installation_directories
>>
>> Next solaris builds will use these locations.
>>
>> thanks
>> Paddy
>>
> [snip thread history]
>
> Hi Paddy,
>
> Great! I have no issues with the proposed directory structure at all!
>
> Regards & Many Thanks,
>
> Nick
>
> p.s. I'll get around to send you some SMF manifest installation stuff soon.
>

--
Amanda http://amanda.zmanda.com
ZRM for MySQL http://www.zmanda.com/backup-mysql.html