Unified Package Manager/Format

I know that this topic is not a new one, but I thought it might be interesting to bring it up once again.
The reason that I'm suddenly interested in a unified package manager/format, is that I just saw Bryan Lunduke rant about it, and I thought to my self: "Hey, that makes sense!"
Bryan Lunduke is not someone I usually hold in high regard, but I was intrigued and started googling. To my surprise I found that there wasn't much interest in the subject.
Now, to you that may make perfect sence, but to me it's absolutely mindboggling. After all, the only reason I'm still sticking with Arch Linux, is the ABS. Not that I don't care for Arch, I really do, but I spend far to much time configuring it, rather than using it.
So what are the arguments for and against?
The arguments against is easy if you ask me:
PRIDE
Yes I said it: "We're happy with out system and it works damn you!"
So, it works... Well, so does a bike, but quite often you'd probably like to take your car instead. Maybe it's raining, maybe the distance is great. Who cares, the point is that the fact that it works, doesn't mean that it could not potentially work quite a lot better.
Back on topic.
Arguments for, is a bit harder, not least because I'm not as much of an expert on the subject as I'd like to be, but I think they're plentiful.
I would assume that developers would appreciate this.
If a set of tools, like the ABS, was included by default, that would indeed make me happy.
Maintenance of packages for multiple platforms would become quite a lot easier, if not trouble free.
And so on and so forth.
I suspect you will be more than able to help filling out the list.
In the end though, my biggest problem is that people ask for a reason to begin work on such a thing. My counter argument of course it: "Why the hell not?!" Arch Linux already provide the perfect foundation, i.e. pacman and ABS. Of course for cross platform compatibility, some work has to be done, but the greatest problem, I believe, is convincing the community that this is a worth while effort.
Oh well, enough ranting I suppose. I really just wanted to revive this debate, as I personally find it rather important. I don't have all the answers, but I dare you to come up with a problem that I cannot provide a theoretical solution to. To me it all seem so simple, and it's a mystery that this feat has not been achieved many years ago.
Best regards.
NB:
I'm not so arrogant that I do not appreciate that I may be entirely on the wrong track, but please, if that is indeed the case, do try to enlighten me rather than something uncomfortable.

Trilby wrote:
You beat me to that XKCD comic.  It's good for a chuckle, but hopefully that doesn't make anyone think that's all it's good for.  That comic captures the primary (and perhaps only) reason I'd never have any hope in such a cause.
Just look at attempts an universal language.  You'd be hard pressed to find a handful of people in your day to day interactions who ever really learned esperanto, for example (I think I know one, but I haven't seen him in years).  Now we can set standards, though.  The arch linux forums have selected English as our default language - and in a sense we force speakers of other languages to use English ... in a sense, but not in another sense.  There are various arch linux online communities in other languages, where some other language is the default.  So one community can set a standard and try to enforce it, but that can't stop another community from springing up and using something different.
So if we say Arch linux's package format is the one package format to rule them all, fine.  But then we have to convince others.  Even if we convinced a lot of debian and red hat people, for example, we'd probably have to compromise a bit and we'd end up with an arch-pm-deb package.  I'm sure some debian and redhat developers would fork their project or start new distros that continued to use .deb/.rpm, and some archers would conclude that this compromise was just a failure and they'd go on using pkg.tar.gz.  And then we have the exact situation of the XKCD comic.
Sure, the world would be much simpler if one person could make an arbitrary decision based on their own preference and have everyone else in the world follow it.  But that's not our world - and I'm glad it's not.
I'm usually not much for compromises (more on that on another occasion), but in this case I'm all for it, as long as it's sensible compromises. I have no illusions that the Arch way is the perfect way, and in any case, certain changes would need to be make to make it work.
I would suggest that some may misunderstand my intentions. I see no reason my the average Debian, OpenSuse, Mint, *buntu, Fedora, Gentoo (etc.) user should experience any change. A Debian user would still use apt-get install package, or whatever graphical front end he or she desires, as with most other distributions, possibly excluding Gentoo and such.
My interests are limited to the back end system end the tools that are provided by default, like something similar to ABS.
Last edited by zacariaz (2013-08-17 15:09:31)

Similar Messages

  • ABS as an universal package manager

    I've just had a rather interesting thought. I'm lately entertaining (and discussing) the idea of universal package management, self contained packages etc. As I've recently switched to Arch again, I thought about ABS as a system which actually reduces dependence on a single repository, a single rule-set so to speak and adds a great amount of flexibility. It may very well be the best way of utilizing the one universal packaging format that there currently is: source tarballs.
    What if other distros started packaging and maybe even pre-installing ABS, or something similar? Any user of any other distro would only need a tool like yaourt to check up a mirror of all PKGBUILD's available in the whole GNU/Linux universe and initiate an install where the system would just follow the instructions laid down in the PKGBUILD.
    Now, considering the flexibility of PKGBUILD's, you don't even need to have them all compile a given program on the user's computer. Instead of fetching a source tarball it could just fetch a binary tarball. The dependencies are still all pretty much the same (and stated and taken care of by the PKGBUILD instructions), the biggest difference is just that instead of compiling the user gets a pre-compiled package and the whole process is done much faster.
    Anyway, I wonder what you think and if anyone has discussed this before. I think the PKGBUILD's may very well contain one possible solution to coming up with universal package management system, at least as an add-on to a given distro's base packaging system. And even as an add on, and especially with the ability to install binary and not just source tarballs (much like pacman in fact) may add a great amount of flexibility to a given distro's user that they may currently be missing.
    Cheers
    Last edited by libervisco (2008-07-04 02:25:39)

    Stythys wrote:what's the point of having different distros if they all start trying to be the same?
    There's no point at all there because that's not my point. The idea of universal package management is merely meant to increase compatibility, to provide a way to easily install the same piece of software using the same process on any distro. Imagine the benefits this could have for newbie users once such an option was further developed and polished. You could tell someone how to install a given program and it would work no matter what distro you run. As it is right now you have specific instructions per distro, not to mention that one distro has some software which another just doesn't.
    It is not meant to replace the existing package management in these distros, just add a way to easily install software even without it, when it doesn't have what you need or when it's simply simpler for you to do it this way.
    Stythys wrote:Anyways I seriously doubt other distros are just gonna start using ABS if asked. If you want pacman/ABS on a different system, just compile it yourself
    Well, I agree they wont just adopt it. It would all be gradual. Someone starts compiling it for other distros and distributing it through a web site or where possible through community contributed repositories. If people like what they see they start using it more and more until some distros decide to include it by default. Depending on its success the extreme end result would be for it to be a common feature of *every* GNU/Linux system.
    But yes, it does start with someone compiling it.
    Stythys wrote:but then why not just use arch
    Why aren't all GNU/Linux users the users of Arch?
    ABS is by far not the only thing which differentiates Arch from others so it's not like putting ABS on other distros would result in them becoming exactly like Arch. That said, people have different preferences. Not everyone wants nor is knowledgeable enough to go through Arch's install process, for example.
    Cheers

  • Cisco Unified Communications Manager Business Edition

    Hi,
    As per my understanding this is only one server solution and you can not have more than one server i.e no sub only Pub. Is this correct?
    Thanks
    Ati

    Hi Ati,
    You are most correct :) This is is "single server" solution for small to medium sized businesses up to 500 users. It comes packaged with Unity Connection for Voicemail.
    Here is a clip;
    "Cisco Unified Communications Manager Business Edition is an easy-to-manage solution that combines voice, video, mobility, and messaging on a single server to simplify system administration and reduce hardware and operating expenses. This solution provides cost-effective deployment options for medium-sized organizations with smaller IT staffs that require all the advanced capabilities of Cisco Unified Communications Manager (formerly Cisco Unified CallManager), Cisco Unity Connection, Cisco Unified Mobility (formerly Cisco Unified MobilityManager), and integrated management on a single server to expedite migration to unified communications."
    From this good doc;
    http://www.cisco.com/en/US/products/ps7273/products_data_sheet0900aecd805e6985.html
    Hope this helps!
    Rob

  • Cisco Unified Communications Manager Version 8.6(2.24106)

    Hi,
    Cisco has released a new software update for Cisco Unified Communications Manager Version 8.6 Release Version:8.6(2.24106). I have been trying to find the release notes for bugs/fixes resolved in this version and open caveats but the documentation for this release does not mention them. Any idea what does this release covers ?
    Software Updates for Cisco Unified Communications Manager Version 8.6
    Product Name :
    Cisco Unified Communications   Manager Version 8.6
    Release Version:
    8.6(2.24106)
    Alert Type:
    New File
    File Name:
    cmterm-devicepack8.6.2.24106-2.cop.sgn
    File Description:
    Cisco   Unified Communications Manager 8.6(2.24106) Device Package - Compatible UCM   Version: 8.6
    File Release Date:
    10-DEC-2013
    Regards
    Robin Thomas

    Hi Robin,
    This is actually a "new" Device Pack for CUCM 8.6(2) rather than
    a new CUCM version release. See below
    Cisco Unified Communications Manager Device Package 8.6(2)
    (24106-2) Release Notes
    http://www.cisco.com/web/software/282074299/108461/CiscoUnifiedCommunicationsManagerDevicePackage8.6.2.pdf
    The latest CUCM release for 8.6(2) is;
    8.6(2a)su3  US Export Restricted - full encryption capabilities (non-bootable) -  For upgrade from 8.x+. Upgrades from 6.1(4)+, 7.1(3), 7.1(5) need to be  requested via PUT (www.cisco.com/upgrade) or purchased to obtain  necessary license
    UCSInstall_UCOS_8.6.2.23900-10.sgn.iso
    Cheers!
    Rob
    "When it comes to luck you make your own  " 
    - Springsteen

  • Important Updates Required for CIsco Unified Communications Manager Versions 7.1 - 9.1

                       Folks,
    I recently received an Email our Cisco SE letting us know about a specific security hole in CUCM that I figured that you  might be interested in:
    As your account team, we wanted to make you aware of an important update to Cisco Unified Communications Manager that addresses a security flaw discovered on June 6th.  This flaw, if unpatched, could allow a remote attacker to gain access to your Communications Manager. Cisco has released a Cisco Options Package (COP) file for each of the affected versions to mitigate the vulnerability.  The updated COP file, cmterm-CSCuh01051-2.cop.sgn, is available on CCO for download now and is located under the Utilities section of the software downloads page for each of the affected versions. 
    The full details of this vulnerability can be found in the security advisory page: cisco-sa-20130717-cucm - Multiple Vulnerabilities in Cisco Unified Communications Manager. If you have issues downloading the update file or questions about the vulnerability, please don't hesitate to contact your account team so we can assist in you getting access to this.

    Hi Craig,
    From the ReadMe;
    Installation Instructions:
    As with any installation or upgrade, it is recommended that you apply this Update during off peak hours.
    When applying this Update be advised that a clusterwide reboot is required.
    This update must be installed on all machines in the cluster before the cluster is rebooted.
    Installation to all machines in the cluster is required; you must start with the Publisher. After the Update has been applied
    to all servers you will need to reboot the entire cluster.  See
    Rebooting the Cluster for detailed instructions.
    This package will install on the following System Versions:
    7.1.3.10000
    xx or any higher version starting with 7
    .1.3.xxxxx
    7.1.5.10000
    xx or any higher version starting with 7.1.5.xxxxx
    8.5.1.10000
    xx or any higher version starting with 8.5.1.xxxxx
    8.6.2.10000
    xx or any higher version starting with 8.6.2.xxxxx
    9.1.1.10000
    xx or any higher version startin
    g with 9.1.1.xxxxx
    http://www.cisco.com/web/software/282204704/18582/ReadmeForBlindSQLinjectionCOPfile.pdf
    Cheers!
    Rob

  • Visual Studio 2013 Nuget Package Manager error

    Hello everyone,
    I tried to add and use OpenCV library in my Visual Studio javascript  windows application project,   but I still get the same error.
    This is my Package manager console:
    PM> Install-Package OpenCV
    Installing 'OpenCV 2.4.8'.
    Successfully installed 'OpenCV 2.4.8'.
    Adding 'OpenCV 2.4.8' to BlankSharedApp1.Windows.
    Uninstalling 'OpenCV 2.4.8'.
    Successfully uninstalled 'OpenCV 2.4.8'.
    Install failed. Rolling back...
    Install-Package : Could not install package 'OpenCV 2.4.8'. You are trying to install this package into a project that targets 'Windows,Version=v8.1', but the 
    package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
    At line:1 char:1
    + Install-Package OpenCV
    + ~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [Install-Package], InvalidOperationException
        + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand
    Thanks for answers.

    Hi Fačko,
    Normally, we won't get any errors if we create a new project. Since you get this error when using OpenCV library and it is a third-party product, I think you need to ask in
    OpenCV forum for better response.
    Thank you for your understanding!
    Best regards,
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Ask the Expert: Upgrading Cisco Unified Communications Manager (CUCM) to Version 9.1 (Drive to 9)

    Welcome to the Cisco Support Community Ask the Expert conversation. Learn from experts Vijay Rao and Amit Singh about simplified upgrade process and focused support from Cisco to migrate to version 9.1. 
    This is a continuation of the live Webcast
    Drive to 9 is a comprehensive and holistic program designed to help you upgrade the current Cisco® Unified Communications Manager installed base to version 9.1 or higher. This upgrade will enable customers to have next-generation collaboration experiences.
    During the live event, Cisco subject matter experts Vijay Rao and Amit Singh focussed on the simplified upgrade process and focused support from Cisco to migrate to version 9.1. They also talked about the changes made to the licensing model of User Connect Licensing and Cisco Unified Workspace Licensing.
    Vijay Rao is a Network Consulting Engineer and is currently a unified communications (UC) consultant for Bank of America. He has been providing consulting assistance to the bank for the past 6 years. He helps design complex UC networks for large enterprise customers. He was previously part of Cisco IT in the Asia Pacific, Japan, and China (APJC) region and was instrumental in designing and implementing the Bangalore campus. He has been working with Cisco for 9 years and has 12 years of UC experience. He has a Cisco CCVP® certification. 
    Amit Singh is a customer support engineer at the Cisco Technical Assistance Center in Bangalore, India. He has 7 years of experience in his areas of expertise: wireless, Cisco Unified Communications Manager, multiservices, Cisco Unity®, and Cisco Unified Contact Center Express. He has been involved in various escalation requests from India, Singapore, and Australia and is currently working as a technical lead for the Voice team in Bangalore, India. He is a computer science graduate.
    Remember to use the rating system to let Vijay and Amit know if you have received an adequate response.  
    Vijay and Amit might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Collaboration, Voice and Video sub-community   forum shortly after the event. This event lasts through July 19, 2013. Visit this forum often to view responses to your questions and the questions of other community members.
    Webcast related links:
    Webcast Video
    FAQ from the live webcast
    Slides from the live webcast

    Hello Robert,
    Apologies for a delayed response, some days get very hectic.
    In CallManager, we only define the SRST reference, and CUCM version and SRST version are independent of each other.
    The only thing, which is related and will change with CUCM upgrade is Phone F/w version.
    http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr1.pdf
    You may just want to check your, phone f/w compatibility with the SRST version running on your ISR G1 Gateways:
    http://www.cisco.com/en/US/products/sw/voicesw/ps2169/products_device_support_tables_list.html
    For Example: SRST version 7.1
    http://www.cisco.com/en/US/prod/collateral/voicesw/ps6788/vcallcon/ps2169/data_sheet_c78-520521.html
    You may want to do some lab testing with CUCM 9.1 and an SRST supported f/w on your phones.
    If you decide to run the old Phone/F/w to support the SRST version, you may not be able to take advantage of new features.
    Also, you can try and upgrade your phones(Wih CUCM 9.1) and test them with your SRST version.
    It should work fine, but from a troubleshooting perspective, TAC may request you to come into a Cisco Supported combination.
    Please, let me know if this clarifies your doubt or we can have a quick phone call.
    Regards
    Amit Singh

  • System settings Package management part crashes on open

    Hello all,
    Whenever I open the system settings and then go to "package management" EVERY TIME the screen shows up and inmediatly closes and I get a KDE crash handler window.
    Please note I am using KDEmod repos.
    If I hover over the Package Management icon I get that it contains 2 items, which are "Aqpm global configuration" and "Aqpm databases configuration"
    No idea of what could be happening, I checked and the package kdemod-aqpm is installed
    Any more info you need just ask I will be around.
    cheers

    There'sa forum for kdemod here - you might get a quicker/better answer there.

  • Package Manager console failed to load

    Last night I installed update 3 for Visual Studio 2012 professional (version 11.0.60610.01).  This morning when I started the package manager console I received the following errors.  I did a repair of VS but other than taking a long time
    it did not fix anything.  I also installed all the extension updates, no help either.  The file mention below is where it should be and I can open it.  Tried running in administrator mode, again no help.  All three versions of power shell
    seem to run just fine (64, 86, ISE).  I am running Windows 8 on a 64 bit machine, all updates are installed.
    Any suggestions on how to fix this one?
    The following error occurred while loading the extended type data file: Microsoft.PowerShell.Core, C:\Windows\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml(2977) : Error in type "System.Security.AccessControl.ObjectSecurity": Exception: The getter method should be public, non void, static, and have one parameter of type PSObject.
    The following error occurred while loading the extended type data file: Microsoft.PowerShell.Core, C:\Windows\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml(2984) : Error in type "System.Security.AccessControl.ObjectSecurity": Exception: The getter method should be public, non void, static, and have one parameter of type PSObject.
    The following error occurred while loading the extended type data file: Microsoft.PowerShell.Core, C:\Windows\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml(2991) : Error in type "System.Security.AccessControl.ObjectSecurity": Exception: The getter method should be public, non void, static, and have one parameter of type PSObject.
    The following error occurred while loading the extended type data file: Microsoft.PowerShell.Core, C:\Windows\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml(2998) : Error in type "System.Security.AccessControl.ObjectSecurity": Exception: The getter method should be public, non void, static, and have one parameter of type PSObject.
    The following error occurred while loading the extended type data file: Microsoft.PowerShell.Core, C:\Windows\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml(3005) : Error in type "System.Security.AccessControl.ObjectSecurity": Exception: The getter method should be public, non void, static, and have one parameter of type PSObject.
    The term 'Get-ExecutionPolicy' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
    John J. Hughes II
    Ran Get-ExecutionPolicy from PowerShell (x86) it returns Restricted
    Also looking around... I have on add-in installed or running
    Also tried uninstalling nugget and reinstalling
    I noticed on the NuGet website it calls for PowerShell 2.0. It seems I have PowerShell 3.0, could that be a problem? Can I install PowerShell 2.0/3.0 side by side, is there an update to NuGet?

    Found the following link in stack overflow, added the suggested items to the VS exe config file and it works now without error.
    http://stackoverflow.com/questions/12638289/embedding-powershell-v2-0-in-net-app-on-windows-8-rtm
    Added the following to the devenv.exe.config file in the runtime section
    <dependentAssembly>
    <assemblyIdentity name="System.Management.Automation" publicKeyToken="31bf3856ad364e35" />
    <publisherPolicy apply="no" />
    </dependentAssembly>
    <dependentAssembly>
    <assemblyIdentity name="Microsoft.PowerShell.Commands.Utility" publicKeyToken="31bf3856ad364e35" />
    <publisherPolicy apply="no" />
    </dependentAssembly>
    <dependentAssembly>
    <assemblyIdentity name="Microsoft.PowerShell.ConsoleHost" publicKeyToken="31bf3856ad364e35" />
    <publisherPolicy apply="no" />
    </dependentAssembly>
    <dependentAssembly>
    <assemblyIdentity name="Microsoft.PowerShell.Commands.Management" publicKeyToken="31bf3856ad364e35" />
    <publisherPolicy apply="no" />
    </dependentAssembly>
    <dependentAssembly>
    <assemblyIdentity name="Microsoft.PowerShell.Security" publicKeyToken="31bf3856ad364e35" />
    <publisherPolicy apply="no" />
    </dependentAssembly>
    <dependentAssembly>
    <assemblyIdentity name="Microsoft.PowerShell.Commands.Diagnostics" publicKeyToken="31bf3856ad364e35" />
    <publisherPolicy apply="no" />
    </dependentAssembly>
    John J. Hughes II

  • How to deploy EAR on CE server using Java Support Package Manager

    Hello,
    I am using CE server where I want to deploy EAR file by using JSPM. I run this program in Drive:\usr\sap\CE1\J00\j2ee\JSPM\go.bat
    I have also put the EAR file into the inbox folder Drive:\usr\sap\CE1\SYS\EPS\in but still It does not show me any file to proceed further for deployment.
    Does any one has idea?
    Regards,
    NK

    Hi,
    The Java Support Package Manager is not able to deploy a single .ear file.
    If the *.EAR file is placed inside an SCA (Software Component Archive) then JSPM is able to deploy it.
    You have to create a .SCA from an .EAR file
    SAP note 1223957 contains an attachment (nwpacktool.zip) which can be used to create a .SCA file from the .EAR file.
    Gerd

  • How to import all Support Packages simulteneily support Package Manager EBP

    Can any body tel me how to apply all support package sumultanesoly by using support Package Manager EBP/CRM option in SPAM.
    I could not able to select all pactche at a time.It selecting one patch at a time only
    Regards
    G Sasikanth Reddy

    I solved my self by selecting highest level of patch so that its dependencies can also add to the queue.
    Regards
    Sasikanth Reddy

  • Support Package Manager for EBPCRM

    Hi,
    In CRM/EBP SAP systems there is used special 'Support Package Manager for EBPCRM' to implement Support Packages instead of standard transactions like SPAM/SAINT.
    I'm trying to implement more then one Support Package into the system however this is probably not possible. It seems that it is not possible to create import queue with more then one Support Package? Importing SPs one by one is very time consuming task. SO that's why I'm wondering about this special tool.
    Do you have similar functionality?
    BR
    m./

    Hi Jose,
    Yes I've put all the SPs into '\usr\sap\trans\Eps\in'. But 'Support Package Manager for EBPCRM' asks me for particular one while I'm going to import it. There is no such an functionality to use queue creation.
    BTW: I'm on SAP CRM 4.0 on WIN/MSSQL platform.
    BR
    m./

  • Ordering new 8.6 Unified communications manager

    Hi everybody,
    For the next year I'm going to order a new CUCM 8.6 system as replacement our old CallManager. I trying now to make a order list. We have 300 ip phones 7911,7941,7960,7970. Please help me out here, I've made this list, correct me if i'm wrong.
    1. CUCM-USR-LIC
    2. R-CUCM-USR-LIC
    3. MCS-7816-I5-IPC1
    4. UCM-7816-86
    5. UCM-7816-86-KIT
    6. UCSS-UCM
    I know that it comes with starter license of 50 DLUs. After installation I can find out exactly DLUs number to order. Is it enough for me?
    thanks.

    Guys I've made a list with dynamic configuration tool. Is it correct? Please I need your advice. Is it enough?
    Product
    Description
    Quantity
    CUCM-USR-LIC
    Top Level Sku For User License
    1
    LIC-CUCM-USR-A
    Unified Communications Manager Enhanced Single User-Under 1K
    300
    UCSS-UCM-1-1-A
    UC Manager Enh UCSS Less than 1K users - 1 user - 1 year
    300
    LIC-CUCM-BASIC-A
    Unified Communications Manager Basic Single User-Under 1K
    300
    UCSS-UCM-BAS-1-1-A
    UC Manager Basic UCSS Less than 1K users - 1 user - 1 year
    300
    UCM-7816-86-XU
    CUCM 8.6 7816 Export Unrestricted Media Kit
    2
    CCX-85-CMBUNDLE-K9
    CCX 8.5 Promo Bundle available only with NEW CUCM or BE6000
    1
    CUCM-PAK
    Include PAK Auto-expanding PAK for CUCM
    1
    CUCM-USR
    Include PAK Auto-expanding User for CUCM
    3000
    UCM-7816-86-KIT-XU
    CUCM Auto-Expansion Media Kit
    1
    UCM-7816-NODE
    CUCM 7816 Node
    2
    UCSS-UCM-BASIC-PAK
    Include PAK Auto-expanding UCSS Basic PAK for CUCM
    1
    UCSS-UCM-PAK
    Include PAK Auto-expanding UCSS PAK for CUCM
    1

  • Managing JAVA JDK and JRE with Package Management in Solaris 11.1

    I want to manage Java JDK & JRE in an Solaris environment using Package Management I'm currently running Solaris 11.1 in a VMWare host. My current latest Java release is JDK1.7.0_07 and JRE1.7.0_07. I want to upgrade to JDK1.7.0_17 & JRE1.7.0_17 using Package Management. I've tried on several occasions to upgrade to latest release of Java but I have not been successful. Each time I try using the Package Management GUI or use command line they appear to be successful but the new release does not show.
    What could I be doing wrong?
    Thanks

    I also learned that the READMEs for the following patches in My Oracle Support also describe the downgrave process:
    Patch 18362676: JAVA 6 DOWNGRADE INCORPORATION FOR ORACLE SOLARIS 11.1.15.4.0 AND 11.1.16.5.0
    Patch 18362686: JAVA 7 DOWNGRADE INCORPORATION FOR ORACLE SOLARIS 11.1.15.4.0 AND 11.1.16.5.0
    -- Alan

  • Do i have to configure ssl on cisco unified provisioning manager for it to work. I am running BE6000 9.X

    Do i have to configure ssl on cisco unified provisioning manager for it to work

    Here is the code
    #include <userint.h>
    #include "iface.h"
    #define DAQmxErrChk(functionCall) if( DAQmxFailed(error=(functionCall)) ) goto Error; else    
    int write_onoff(uInt8 HL, const char linename[])
      int         error=0;              // error code (initialized to zero i.e. no error)
      TaskHandle  taskHandle=0;            // task ID for DAQmx
      char        errBuff[2048]={'\0'}; // error message
      // DAQmx Configure Code
      SetWaitCursor(1);
      DAQmxErrChk(DAQmxCreateTask("", &taskHandle));
      DAQmxErrChk(DAQmxCreateDOChan(taskHandle, linename, "", DAQmx_Val_ChanPerLine ));
      // DAQmx Start Code
      DAQmxErrChk(DAQmxStartTask(taskHandle));
      // DAQmx Write Code
      DAQmxErrChk(DAQmxWriteDigitalU8(taskHandle, 1, 1, 10.0, DAQmx_Val_GroupByChannel, &HL, NULL, NULL));
      Error:
        SetWaitCursor(0);
        if (DAQmxFailed(error)) DAQmxGetExtendedErrorInfo(errBuff, 2048);
        if (taskHandle!=0)
          // DAQmx Stop Code
          DAQmxStopTask(taskHandle);
          DAQmxClearTask(taskHandle);
        if (DAQmxFailed(error)) MessagePopup("DAQmx Error", errBuff);  
      return error;  
    } // end write_digital_line
    int CVICALLBACK test (int panel, int control, int event, void *callbackData, int eventData1, int eventData2)
      uInt8 onoff=0;
      if (event==EVENT_COMMIT)
        GetCtrlVal(panel, control, &onoff);
        write_onoff(onoff, "Dev1/port0/line0");
      return 0;  // return 0 to tell the system the message has been handled    

Maybe you are looking for