SearchFAQMemberlist Log in
Reply to topic Page 1 of 2
Goto page 1, 2  Next
Bacula 2.0.3-1 released for SuSE 10.1 and 10.2 (x86_64)
Author Message
Post Bacula 2.0.3-1 released for SuSE 10.1 and 10.2 (x86_64) 
Attachments: Message as HTML

Bacula 2.0.3-1 released for SuSE 10.1 and 10.2 (x86_64) - see
sourceforge.net rpms-contrib-psheaffer or (soon to be) the sbarnin repo.

Thanks,
PattiMichelle

Post Bacula 2.0.3-1 released for SuSE 10.1 and 10.2 (x86_64) 
Fedora {5,6} + EL 4 RPMs are released, too.

Please note that there are efforts getting bacula into mainline Fedora. Andreas
Thienemann did a great job there. I think that these RPMs (once accepted in
Fedora) will find their way into Enterprise Extras which is good news to all EL
users out there.

If you like to participate/follow the package creation process, have a look at
bug 230344: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=230344

Building Andreas' srpm works with:
rpmbuild -ba --define "fedora 6" SPECS/bacula.spec

fs

Post Bacula 2.0.3-1 released for SuSE 10.1 and 10.2 (x86_64) 
Attachments: Message as HTML

Congratulations to him (and surely the others) and thanks a lot to you Wink
Great Job guys !

Franck

2007/3/13, Felix Schwarz <Felix.Schwarz < at > we...>:


Fedora {5,6} + EL 4 RPMs are released, too.

Please note that there are efforts getting bacula into mainline Fedora.
Andreas
Thienemann did a great job there. I think that these RPMs (once accepted
in
Fedora) will find their way into Enterprise Extras which is good news to
all EL
users out there.

If you like to participate/follow the package creation process, have a
look at
bug 230344: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=230344

Building Andreas' srpm works with:
rpmbuild -ba --define "fedora 6" SPECS/bacula.spec

fs


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users < at > li...
https://lists.sourceforge.net/lists/listinfo/bacula-users


Post Bacula 2.0.3-1 released for SuSE 10.1 and 10.2 (x86_64) 
On Tue, 13 Mar 2007, Xeos Laenor wrote:

Congratulations to him (and surely the others) and thanks a lot to you Wink
Great Job guys !

Seconded.

Has anyone built a bacula-fd for suse-9 at all?

Post Bacula 2.0.3-1 released for SuSE 10.1 and 10.2 (x86_64) 
Hi,

On 3/14/2007 11:30 AM, Alan Brown wrote:
On Tue, 13 Mar 2007, Xeos Laenor wrote:

Congratulations to him (and surely the others) and thanks a lot to you Wink
Great Job guys !

Seconded.

Has anyone built a bacula-fd for suse-9 at all?

Yes. No rpms here, though.

I'm quite sure someone else will have an rpm soon for the FD at least.
This would be for the SLES 9, but I'm quite sure SuSE 9.2 and SLES 9 are
similar enough to use the same binaries.

I could create rpms myself, but I'm sure others can do it better :-)

Arno



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users < at > li...
https://lists.sourceforge.net/lists/listinfo/bacula-users

--
IT-Service Lehmann al < at > it...
Arno Lehmann http://www.its-lehmann.de

Post Bacula 2.0.3-1 released for SuSE 10.1 and 10.2 (x86_64) 
On Fri, 16 Mar 2007, Arno Lehmann wrote:

Has anyone built a bacula-fd for suse-9 at all?

Yes. No rpms here, though.

All I need is a bacula-fd-static...

Thanks
AB

Post Bacula 2.0.3-1 released for SuSE 10.1 and 10.2 (x86_64) 
On Friday 16 March 2007 12:45, Arno Lehmann wrote:
Hi,

On 3/14/2007 11:30 AM, Alan Brown wrote:
On Tue, 13 Mar 2007, Xeos Laenor wrote:

Congratulations to him (and surely the others) and thanks a lot to
you Wink
Great Job guys !

Seconded.

Has anyone built a bacula-fd for suse-9 at all?

Yes. No rpms here, though.

I'm quite sure someone else will have an rpm soon for the FD at least.

Hopefully the above is true, but if I recall correctly, the Bacula project
(i.e. Scott) is no longer supporting SuSE 9.

This would be for the SLES 9, but I'm quite sure SuSE 9.2 and SLES 9 are
similar enough to use the same binaries.

I could create rpms myself, but I'm sure others can do it better :-)

Arno



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users < at > li...
https://lists.sourceforge.net/lists/listinfo/bacula-users

--
IT-Service Lehmann al < at > it...
Arno Lehmann http://www.its-lehmann.de

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users < at > li...
https://lists.sourceforge.net/lists/listinfo/bacula-users


Post Bacula 2.0.3-1 released for SuSE 10.1 and 10.2 (x86_64) 
On Sat, 17 Mar 2007, Kern Sibbald wrote:

Has anyone built a bacula-fd for suse-9 at all?

Yes. No rpms here, though.

I'm quite sure someone else will have an rpm soon for the FD at least.

Hopefully the above is true, but if I recall correctly, the Bacula project
(i.e. Scott) is no longer supporting SuSE 9.

I've previously discussed with Scott about making bacula-fd-static
binaries available (where possible) for use on obsolete systems.

While I realise it's not always possible to make a full -static set, 99%
of the time the filedaemon is the only thing needed - in order to keep
backing up older systems until they're replaced.

Right now I can imagine several people asking why I don't just update and
the answer is simple - we are a space lab, supporting projects which may
run for a decade or more and a lot of the time the software is binary-only
and keyed to a particular machine and/or OS(*) - which means we are locked
into using that machine or OS until the probe in question (somewhere
around the solar system) finally dies.

(*) Sometimes we have sources and find that the person who wrote the code
is long gone, or the code is very tightly coded to the OS - but more often
it's just so incredibly badly written that it's totally non-portable.
Rocket Scientists are some of the lousiest programmers on the planet.

Post Bacula 2.0.3-1 released for SuSE 10.1 and 10.2 (x86_64) 
Hi,

On 3/19/2007 11:14 AM, Alan Brown wrote:
On Sat, 17 Mar 2007, Kern Sibbald wrote:

Has anyone built a bacula-fd for suse-9 at all?
Yes. No rpms here, though.

I'm quite sure someone else will have an rpm soon for the FD at least.
Hopefully the above is true, but if I recall correctly, the Bacula project
(i.e. Scott) is no longer supporting SuSE 9.

I've previously discussed with Scott about making bacula-fd-static
binaries available (where possible) for use on obsolete systems.

While I realise it's not always possible to make a full -static set, 99%
of the time the filedaemon is the only thing needed - in order to keep
backing up older systems until they're replaced.

Ok, I have an FD for SuSE 9.2 which should also work on SLES9.
Statically linking was not possible, after some playing around, I always
ended up with:

elf:/srv/nfsexport/bacula/bacula-2.0.2 > grep Static ./config.out
Statically Linked Tools: no
Statically Linked FD: yes
Statically Linked SD: no
Statically Linked DIR: no
Statically Linked CONS: no
elf:/srv/nfsexport/bacula/bacula-2.0.2 > ldd src/filed/bacula-fd
linux-gate.so.1 => (0xffffe000)
libacl.so.1 => /lib/libacl.so.1 (0x4002f000)
libz.so.1 => /lib/libz.so.1 (0x40035000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x40047000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x40059000)
libm.so.6 => /lib/tls/libm.so.6 (0x40116000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40139000)
libc.so.6 => /lib/tls/libc.so.6 (0x40141000)
libattr.so.1 => /lib/libattr.so.1 (0x40257000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
elf:/srv/nfsexport/bacula/bacula-2.0.2 >

I can not find static .a libraries for linux-gate (whatever that is) and
libattr, so I assume these might be one reason for not having a static
FD possible.

Anyway, as far as I can see the FD should run on minimal
SLES9-installation, perhaps even when running a recovery version from
DVD and accessing the FD binary and configuration via nfs or similar.

I can mail the FD, or put it onto a web site if there is need for it.
244k stripped, and here is a checksum:
f2333e592204ae69800b265936ccfac05aa08c79 src/filed/bacula-fd-stripped

Right now I can imagine several people asking why I don't just update

No need to explain that - I still have SuSE 8.1 running my Bacula server :-)

and
the answer is simple

My answer would be even simpler :-)

- we are a space lab, supporting projects which may
run for a decade or more and a lot of the time the software is binary-only
and keyed to a particular machine and/or OS(*) - which means we are locked
into using that machine or OS until the probe in question (somewhere
around the solar system) finally dies.

Which would be the time when you don't need a FD for it any more, any
suppose...


(*) Sometimes we have sources and find that the person who wrote the code
is long gone, or the code is very tightly coded to the OS - but more often
it's just so incredibly badly written that it's totally non-portable.
Rocket Scientists are some of the lousiest programmers on the planet.

That's because you don't have to be a rocket scientist to write code ;-)

Arno


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users < at > li...
https://lists.sourceforge.net/lists/listinfo/bacula-users

--
IT-Service Lehmann al < at > it...
Arno Lehmann http://www.its-lehmann.de

Post Bacula 2.0.3-1 released for SuSE 10.1 and 10.2 (x86_64) 
On Tue, 20 Mar 2007, Arno Lehmann wrote:

Ok, I have an FD for SuSE 9.2 which should also work on SLES9.
Statically linking was not possible, after some playing around, I always
ended up with:

I can not find static .a libraries for linux-gate (whatever that is) and
libattr, so I assume these might be one reason for not having a static
FD possible.

The joy of static binaries is that they aren't library dependent, so they
can be compiled on any available distribution, etc and then copied into
the machine in question... :-)

And that reminded me to look in /etc/bacula/rescue/linux/cdrom/bacula/bin/
....

Right now I can imagine several people asking why I don't just update

No need to explain that - I still have SuSE 8.1 running my Bacula server :-)

It's always awkward when one can't upgrade, especially when the solution
becomes "upgrade your OS"

AB

Post Bacula 2.0.3-1 released for SuSE 10.1 and 10.2 (x86_64) 
On Tuesday 20 March 2007 11:12, Alan Brown wrote:
On Tue, 20 Mar 2007, Arno Lehmann wrote:

Ok, I have an FD for SuSE 9.2 which should also work on SLES9.
Statically linking was not possible, after some playing around, I always
ended up with:

I can not find static .a libraries for linux-gate (whatever that is) and
libattr, so I assume these might be one reason for not having a static
FD possible.

The joy of static binaries is that they aren't library dependent, so they
can be compiled on any available distribution, etc and then copied into
the machine in question... :-)

And that reminded me to look in /etc/bacula/rescue/linux/cdrom/bacula/bin/
....

Right now I can imagine several people asking why I don't just update

No need to explain that - I still have SuSE 8.1 running my Bacula
server :-)

It's always awkward when one can't upgrade, especially when the solution
becomes "upgrade your OS"


What I don't understand is why you don't build your own current (non-static)
version of Bacula on your older systems.

Post Bacula 2.0.3-1 released for SuSE 10.1 and 10.2 (x86_64) 
On Tue, 20 Mar 2007, Kern Sibbald wrote:

What I don't understand is why you don't build your own current (non-static)
version of Bacula on your older systems.

Because in several cases they won't compile - lack of libraries, etc.

These are old boxes and they're "frozen" - no updates of core software
allowed in case it breaks the running software.

Post Bacula 2.0.3-1 released for SuSE 10.1 and 10.2 (x86_64) 
Hi,

On 3/20/2007 2:15 PM, Alan Brown wrote:
On Tue, 20 Mar 2007, Kern Sibbald wrote:

What I don't understand is why you don't build your own current (non-static)
version of Bacula on your older systems.

Because in several cases they won't compile - lack of libraries, etc.

These are old boxes and they're "frozen" - no updates of core software
allowed in case it breaks the running software.

I'll add my results here - they seem to fit :-)

Bad luck, Alan: I can't get a static FD even under SuSE 8.1. Seems to be
some problem with the acl library. I tried to disable ACLS during
configure, but --disable-acl was accepted but did not work.

In case someone knows how to tell configure to not include ACL support
please tell me - I'm sure Alan would be grateful ;-)

I'll try to rename the acl header file during configure otherwise, but
that will have to wait until the evening...

Arno


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users < at > li...
https://lists.sourceforge.net/lists/listinfo/bacula-users

--
IT-Service Lehmann al < at > it...
Arno Lehmann http://www.its-lehmann.de

Post Bacula 2.0.3-1 released for SuSE 10.1 and 10.2 (x86_64) 
On Tuesday 20 March 2007 14:51, Arno Lehmann wrote:
Hi,

On 3/20/2007 2:15 PM, Alan Brown wrote:
On Tue, 20 Mar 2007, Kern Sibbald wrote:

What I don't understand is why you don't build your own current
(non-static)
version of Bacula on your older systems.

Because in several cases they won't compile - lack of libraries, etc.

These are old boxes and they're "frozen" - no updates of core software
allowed in case it breaks the running software.

I'll add my results here - they seem to fit :-)

Bad luck, Alan: I can't get a static FD even under SuSE 8.1. Seems to be
some problem with the acl library. I tried to disable ACLS during
configure, but --disable-acl was accepted but did not work.

In case someone knows how to tell configure to not include ACL support
please tell me - I'm sure Alan would be grateful ;-)

I'll try to rename the acl header file during configure otherwise, but
that will have to wait until the evening...

Do the ./configure, then edit src/config.h and turn off ACL support. The tag
is named HAVE_ACL. Currently there is no way to disable it with an option.

You might also have to modify the Makefile and remove the -lacl
(and/or -lsec).


Arno


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users < at > li...
https://lists.sourceforge.net/lists/listinfo/bacula-users

--
IT-Service Lehmann al < at > it...
Arno Lehmann http://www.its-lehmann.de

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users < at > li...
https://lists.sourceforge.net/lists/listinfo/bacula-users


Post Bacula 2.0.3-1 released for SuSE 10.1 and 10.2 (x86_64) 
On Tuesday 20 March 2007 14:15, Alan Brown wrote:
On Tue, 20 Mar 2007, Kern Sibbald wrote:

What I don't understand is why you don't build your own current
(non-static)
version of Bacula on your older systems.

Because in several cases they won't compile - lack of libraries, etc.

Well, I would say that they have a *serious* oversight in their procedures. I
am not talking about the fact that the system is "frozen*, which makes a lot
of sense, but as a *minimum* precaution, they should assure that there is a
similar system in standby or that they can re-create the *full* system on
another machine, load any needed libraries and rebuilt any piece that starts
failing.


These are old boxes and they're "frozen" - no updates of core software
allowed in case it breaks the running software.

Yes, and they have thus assured that the system cannot be maintained for the
desired lifetime -- see my comments above on how to resolve this.

Display posts from previous:
Reply to topic Page 1 of 2
Goto page 1, 2  Next
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB