I'm attaching the package I created to my workstation for the tivoli storage manager client. There is one problem with this package. It doesn't have a license. This isn't my fault. The TSM client doesn't come with one and I looked and grepped pretty hard. The client is free and the server has the license. At first I used "as-is" but that isn't techinically correct though I think it's the best choice. I don't see one called "none". The package is useless without the server component so I don't know if it needs one. Reproducible: Always Steps to Reproduce: Once installed the package puts the config files in /etc/tivoli/ and there is an init.d script at /etc/init.d/tivoli. I've been using this package for over a month and figued I'd better give it to you before I completely forgot about it.
Created attachment 11365 [details] Ebuild, config, and init.d files for the TSM client $ tar tzf tivoli-storage-manager.tar.gz tivoli-storage-manager/ tivoli-storage-manager/files/ tivoli-storage-manager/files/digest-tivoli-storage-manager-5.1.5 tivoli-storage-manager/files/tivoli.conf.d tivoli-storage-manager/files/tivoli.init.d tivoli-storage-manager/tivoli-storage-manager-5.1.5.ebuild
This has a bug in the ebuild in the src_install() line. I'll upload a new version in the next week.
Created attachment 15553 [details] well tested ebuild and init scripts for Tivoli Storage Manger I think this should go in to the app-admin group. $ tar tzf /usr/local/portage/app-admin/tsm-ba.tar.gz tsm-ba/ tsm-ba/files/ tsm-ba/files/digest-tsm-ba-5.1.6 tsm-ba/files/dsmc.init.d tsm-ba/files/dsmc.conf.d tsm-ba/Manifest tsm-ba/tsm-ba-5.1.6.ebuild This does not include the developement API, I'll provide a seperate package for that.
New ebuild for TSM 5.2.2 (which we are running). You now need the TIVsm-API.rpm as well. I also stripped all the language stuff out. Maybe we need an internationalization USE flag? =) Just for the sake of doing it, I changed RESTRICT to include fetch. I plan on making a few ebuild of the various products for my company's internal use. The init files are the same, but I'm attaching them as well as the ebuild in seperate files per the "ebuild common mistakes" document.
Created attachment 31070 [details] Ebuild for TSM-BA 5.2.2
Created attachment 31071 [details] Conf.d file for TSM-BA 5.2.2
Created attachment 31072 [details] init.d file for TSM-BA 5.2.2
Created attachment 31073 [details] Digest for TSM-BA 5.2.2
Forgot the attachments
John, (Sorry for the long delay) I have no way to test these ebuilds other than to check for correctness and so on, and William is no longer a gentoo dev as far as I can tell. The 5.2.2 ebuild looks fine, though. Question, why the fetch restriction? Because of the absent license? Did you notice that in the mean time, the 5.2.3 version is out? Do you happen to have an ebuild for that? Version bumping doesn't work, since the programs now seem to have been released as a tarball. Since I can't test it, and the ebuild doesn't work for the next version, I would like to hear from you or anybody else interested in providing feedback on the installed program before I put it in the tree. Sounds fair? Thanks for the efforts so far! Wout.
Wout, I had someone send me a private message about using custom ebuilds and realized that you had actually updated the bug! Sorry for MY long delay. The reason for the file flag is mainly the license. The client is TOTALLY useless without a TSM server and a node registration but I didn't want to take any chances. I just realized the other day when installing a new TSM server that 5.2.3 was indeed out. I haven't updated my ebuild for it yet as we're still using 5.2.2 on our production server. Since I've installed 5.2.3 on this new setup and I have a gentoo server so I would have probably updated it soon enough. I'll work on it this weekend and get an updated ebuild out there.
I've also written ebuilds for the TSM client and server (see http://dev.gentoo.org/ebuilds) as I didn't realise at the time that there was a client ebuild pending. The client is functionally equivalent to Williams, there might be parts that are worth importing into his ebuild (please ignore the fact that the executables are installed with a insinto rather than a exeinto. Since theres a working ebuild theres no point me fixing it). Feel free to have a look and burgle any bits that seem useful. As for the server ebuild, I'll open a new bug if its deemed worthwhile. Currently the server is for version 5.2.2 as I haven't received the media for 5.3 yet. The license with the server may also be an issue as there isn't one in portage that is suitable.
Created attachment 44635 [details] ebuild and related files for TSM 5.2.3: tsm.tar.gz TSM 5.2.3 This release builds on John's version. In addition to the version bump it fixes some bugs in the previous two ebuilds. This also renames the package from 'tsm-ba' to 'tsm'. Previously I had planned to provide a 'tsm-api' but since the API is required for the client to run it doesn't make sense to keep them seperate. This is a tarball of all relevant files. Note that the 'gSOAP' file is a licence file and should be moved to portage/licenses/gSOAP. Since TSM 5.2.3 actually declares it's licences in the download I've removed the 'fetch' restriction. IMO the 'fetch' restriction didn't make any sense, 'nomirror' could have but I still don't think it's needed. Files (I'll also submit the ebuild serperatly in a moment): # tar tzf tsm.tar.gz tsm/ tsm/files/ tsm/files/dsmc.init.d tsm/files/dsmc.conf.d tsm/files/digest-tsm-5.2.3 tsm/tsm-5.2.3.ebuild tsm/ChangeLog tsm/metadata.xml tsm/Manifest gSOAP (dsmc.init.d and dsmc.conf.d remain unchanged since the originial versions.) It is expected you will untar this in /usr/local/portage/app-admin or similar directory.
Created attachment 44636 [details] tsm-5.2.3.ebuild This file is also available in the 5.2.3 tsm.tar.gz tarball. It needs the dsmc.conf.d and dsmc.init.d files also attached to this bug or available in said tarball.
Just noticed the typo in the URL I posted the other day, it should read http://dev.gentoo.org/~baz/ebuilds. Probably a bit late to be useful now 8).
wmertens/baz/vorlon: would you like to join app-backup?
I don't mind maintaining the TSM server, license and and IBM tape ebuilds, as I do this for our local site anyway. The main problem at the moment is that the IBM tape driver, http://bugs.gentoo.org/show_bug.cgi?id=74335, depends on a redhat kernel being installed for which I've posted an ebuild, http://bugs.gentoo.org/show_bug.cgi?id=74336, but have not had much response from the kernel herd.
Did someone try to install TSM 5.3? Since it needs the IBM GPFS I'm a bit lost...
What is happening with this? The ebuilds attached to this bug aren't the ones on ~baz devspace. Also, 5.3.0 is now out. Is someone maintaining this package? 5.3.0 also comes with a LICENSE.TXT if this is the reason this package hasn't made the tree.
puggy: I'm waiting on recruiters to bring in a new developer, and I haven't heard ANYTHING at all from them.
Robin: Who's the new guy/gal?
David (see bug 101795) is a storage consultant in Sweden, who actively deploys TSM on a variety of systems, including Gentoo.
I'll see about updating the TSM client ebuild that I wrote later today.
Created attachment 79243 [details] ebuild and related files for TSM 5.3.2: tsm.tar.gz This includes an updated ebuild for TSM 5.3.2 client. Contents: $ tar tzf tsm.tar.gz tsm/ tsm/tsm-5.3.2.ebuild tsm/Manifest tsm/files/ tsm/files/digest-tsm-5.2.3 tsm/files/digest-tsm-5.2.4 tsm/files/digest-tsm-5.3.0 tsm/files/digest-tsm-5.3.2 tsm/files/dsmc.conf.d tsm/files/dsmc.init.d tsm/tsm-5.2.3.ebuild tsm/tsm-5.3.0.ebuild tsm/ChangeLog tsm/metadata.xml tsm/tsm-5.2.4.ebuild SNIA-2.2
Created attachment 79245 [details] tsm-5.3.2.ebuild
Created attachment 79246 [details] init.d file for tsm 5.3.2 Use the exiting 5.2.2 conf.d file with this.
Hello, Have anyone ever managed to run TSM client on Linux on Sparc? I have one such machine (With Gentoo Linux SPARC) and I intend to install additional one on SunFire 280R. Any help/ideas? Regards, Leon
Created attachment 104812 [details] tsm-5.3.4-r3 ebuild Slight modifications to the 5.2.3 ebuild posted here
Created attachment 107481 [details] tsm-5.3.4-r3.ebuild Hans Halvorson's ebuild worked, but the web interface dsmcad was broken, looking for libraries. The libraries from /usr/lib has to be installed (which are basically just links back to the libraries in /opt). Here's a modified ebuild to fix it. I also uncommented the part that puts the startup script in /etc/init.d.
I am using tsm-5.3.4-r3.ebuild. The backup is working but I'm getting complains about /dev/fsm. Is there a fix for this?
I found a solution in the forum. I changed the line TSM_HSM="TIVsm-HSM.i386.rpm" to #TSM_HSM="TIVsm-HSM.i386.rpm" Now it works.
i tried the tsm-5.3.4-r3 ebuild from troy but creating the digest failed with fetching TSM534C_FIX3_LINUX86.tar. i searched in google and found another source: http://fresh.t-systems-sfr.com/linux/src/TSM534C_FIX3_LINUX86.tar/. after manually downloading the file from that site the digest went fine. btw, has anybody the mood or need the create a new ebuild for 5.4.1 (out since june 2007)?
(In reply to comment #31) > I found a solution in the forum. I changed the line > > TSM_HSM="TIVsm-HSM.i386.rpm" > > to > > #TSM_HSM="TIVsm-HSM.i386.rpm" > > Now it works. > I did the same thing and that fixed all error messages I would get. I also set my BASE_URI to this: BASE_URI="ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r3/Linux/Linux86/v${MY_PV}/" I'll try to update the ebuild to the latest version of tsm client when I get the chance.
Created attachment 132564 [details] Updated ebuild for current version of TSM
Created attachment 156565 [details] tsm-5.5.0-r6.ebuild Here is a 5.5.0-r6 ebuild. I'm using the x86 non-hsm version in production. I've made a few changes to the ways the original ebuilds that were posted here do things, particularly, I'm using versionator for version manipulation, the BASE_URI is more dynamic now, I added an "hsm" use flag, so it won't extract the HSM rpm unless you define that use flag, and I'va added ~amd64 to the KEYWORDS, since there are 64-bit libraries included in 5.5. Gotchas: I haven't tested the 64-bit stuff, nor have I even thought about installing the 64-bit libraries. We'd probably need some more library symlinking with the 64-bit libraries. I also haven't tested the HSM stuff. I don't even know what HSM is, all I know is that it's bloated and I don't need it.
Troy's ebuild for 5.5.0-r6 works fine under amd64, but you have to change DEPEND and RDEPEND to the following: DEPEND="x86? ( sys-libs/lib-compat ) app-arch/rpm" RDEPEND="x86? ( sys-libs/lib-compat )"
Just FYI, it is a royal pain to get dsmc running on hardened. I did not know about this ebuild and went on manually- effectively you have to strip all the protection bits from the dsmc binary with paxctl.
(In reply to comment #37) > Just FYI, it is a royal pain to get dsmc running on hardened. > > I did not know about this ebuild and went on manually- effectively you have to > strip all the protection bits from the dsmc binary with paxctl. > indeed. But i'll try to commit the ebuild i'm currently using within the next few weeks to gentoo-x86.
Created attachment 215572 [details] ebuild with sys-libs/libstdc++-v3 dependency lib-compat doesn't provide libstdc++.so.5 anymore. see http://bugs.gentoo.org/show_bug.cgi?id=51221 So I added sys-libs/libstdc++-v3 to RDEPEND and removed lib-compat from DEPEND and RDEPEND I'm not sure if lib-compat is necessary tought, as I only use admistrative command-line
Created attachment 217015 [details] Version bump with a lot of improvements in ebuild * Version bump to current version * Introduced group "tsm" for users that are allowed to use the client * Fixed the version numbering (not abusing -rx anymore) * Use app-arch/rpm2targz to unpack the files (instead of rpm) Please test!
(In reply to comment #40) > Created an attachment (id=217015) [details] > Version bump with a lot of improvements in ebuild > > * Version bump to current version > * Introduced group "tsm" for users that are allowed to use the client > * Fixed the version numbering (not abusing -rx anymore) > * Use app-arch/rpm2targz to unpack the files (instead of rpm) > > Please test! Added to CVS as app-backup/tsm.
Wow, Tobias! I can't believe it! You added it to Portage! Yay!