Open Source patching or scripting patch installs

Has anyone implemented Scripts to Automate patching of a Solaris Server. I am interested in Open Source solution rather than the one provided by SUN. I am mostly interested in Solaris 8/9/10 on SPARC.
I have seen a few scripts in perl, want to know if anyone else has seen more and/or implementing any such solution in Production?
Please let me know. Thanks
-GGR

I dont think somebody has done what you want. But if I has to do it, I think I'll use 2 servers. One server with the Webservices and the access to the COM in a windows server, and the second one, the apache and php.
That way, you can use the webservices as in any web application, and dont worry about the COM.
good luck!
Harold Gómez

Similar Messages

ANN: Open Source Flash Player Scripting Engine

Mozilla bekommt den Quellcode fÃ¼r die
ActionScriptâ¢ Virtual Machine
Das OS-Projekt heiÃt "Tamarin". DÃ¼rfte
spannend werden.
http://www.adobe.com/aboutadobe/pressroom/pressreleases/200611/110706Mozilla.html
http://www.mozilla.org/projects/tamarin/
GrÃ¼Ãe, JÃ¶rg
AdobeÂ® Community Expert
Sicher ist sicher:
http://mm-exporter.joexx.de

Oh ja. Das sieht vielversprechend aus.
danke fÃ¼r den link
hil
JÃ¶rg Schmalenberger *ACE* schrieb:
> Mozilla bekommt den Quellcode fÃ¼r die
ActionScriptâ¢ Virtual Machine
> Das OS-Projekt heiÃt "Tamarin".
DÃ¼rfte spannend werden.
>
>
http://www.adobe.com/aboutadobe/pressroom/pressreleases/200611/110706Mozilla.html
>
http://www.mozilla.org/projects/tamarin/
>

Bridge cc will not open after trying to add patch aom package (adobe output module) to workspace

bridge cc will not open after trying to add patch aom package (adobe output module) to workspace. this patch was recommended by adobe help to allow creating pdf presentations. the help stated bridge cc was shipped without this and to download aom package win 64. I tried that, and either did something wrong or? I deleted bridge cc 64 bit, then went to cc and downloaded bridge cc (not sure if it is 32 or 64) and the program still does not open. any ideas?

There are lots of threads on this. Do a web search.

Can't open pdf. files something about patch package

Can't open PDF files something about patch package verification.error.

I am having the same issue. Unable to open ANYTHING related to adobe (PDF, downloads), as well as unable to delete and reinstall or even change or correct.

Do I need to pay anything to Adobe if I inject java script using some open source library?

Hello,
I want to restrict PDF reader to achieve Digital Rights Management (DRM).
Do I need to pay anything to Adobe if I inject java script to achieve so using some open source library?
Basically I want my PDF documents to be restricted such that I can:
Limit printing
Prevent screenshots
Restrict access by license expiry date
Restrict distribution of downloaded PDF (i.e. the document should run on specific machine only)
Restrict copy and paste within PDF document
I came across below links from which I suspect Adobe expects one to pay if he/she attempts to restrict reader functionality in some way?
http://www.adobe.com/devnet/reader/topic_drm.html
http://www.adobe.com/devnet/acrobat/overview.html
Am I correct in my assumption?

I think it is a vain hope to imagine you could implement DRM via JavaScript. Remember it can be turned off.
Printing is either enabled or disabled according to document security.
Working with PDFs does not require permission from Adobe but
* adding functionality to Adobe Reader definitely does; a DRM development license is a major investment.
* if the file is Reader-enabled, all third party tools will disable that.

Installing Current patch set after SAP installation

Hi,
We are installing SAP ECC6.0 on Solaris x64. We installed the Oracle RDBMS software and missed installing the Oracle Current patch set. We have proceeded with the SAP installation. Can we install the Patches after the SAP installation or do i need to uninstall SAP and do t all over again. Please help asap as i need to complete it..
Regards
Dee

Hello Dee,
> Can we install the Patches after the SAP installation or do i need to uninstall SAP and do t all over again
Of course you can install the patchset after the SAP installation. The current patchset is the 10.2.0.4.
After applying the current patchset - please install also the "on-top" patches - check sapnote #1137346 for this. Also check sapnote #830576 for setting the corresponding database parameters after the patchset installation.
Regards
Stefan

Open Source releasing best practices?

Hello,
When creating open source software, I don't really know what the best way to release it (what kind of makefile, versioning system, etc...) is. It's also hard to find this info online, is there any good online info or book about this?
Here are some of my questions...
-How many operating systems should your makefile support? Should I make special cases for every single Linux distro and other OS in the makefile, or can I just put a generic "g++ *.cpp" in the makefile, and let each OS and distro's own package managers take care of tailoring it to their OS?
-For makefile complexity, I guess there is a scale ranging from a hack like just typing "g++ *.cpp" in it, through having nice sections, groups of files and definitions like "CFLAGS", all the way up to projects which have 20 different makefiles in them like "Makefile.in", "Makefile.pandora", etc.... Where on that scale should you ideally be?
-Makefiles of many projects look incredibly complex, why?
-What versioning system to use? When to make a 1.0.0? When to append "rc" at the end?
-When to tag stable versions? And when you change something in head, do you need to change version number every single time?
-When creating a dynamic library, and you tagged a stable version, and you then change something in head. Should in the makefile the version number of the library name be changed to something? If so, should it be changed to a next minor version, or to something with "-rc" at the end?
-What names should be used for tags of versions?
-Does there need to be both a zipped version of the source code and one under VCS, and if so why is that zipped version needed?
-Are there any naming conventions for output binaries and libraries?
-Are you supposed to let your makefile clean up .o files after compilation or not?
-Are there any conventions for makefiles for names of sections and variables in it? E.g. is it a good idea to have a "clean:" in your makefile to remove everything?
-When depending on another library which is hosted somewhere else, how to handle that? What when statically depending on it?
-Any other things I should know?
Thanks!
Last edited by aardwolf (2013-05-07 12:32:57)

aardwolf wrote:Hello,
Many of your questions have no single correct response. I'll reply with my own opinions and experiences, based on my release of two open source projects (GPT fdisk and rEFInd).
-How many operating systems should your makefile support? Should I make special cases for every single Linux distro and other OS in the makefile, or can I just put a generic "g++ *.cpp" in the makefile, and let each OS and distro's own package managers take care of tailoring it to their OS?
Ideally, a Makefile should build a package under every OS on the planet. In practice, this isn't always practical. Many developers use programs like Autotools to create Makefiles that are suited to a particular build environment. Other developers (myself included) create a handful of Makefiles for different environments -- for instance, my GPT fdisk has Makefiles for Linux, FreeBSD, OS X, and Windows. My rEFInd officially supports building only under Linux, although it supports two EFI toolkits (GNU-EFI and TianoCore EDK II) via a cascading set of Makefiles. Any of these Makefiles can require changes depending on the distribution and development environment in use, but that's not really my concern.
If a distribution requires changes, that type of change is generally best left to a build system like Autotools or to the person who builds or packages the program. IMHO, it's unreasonable to ask a developer to make minor tweaks to a static Makefile to support every minor Linux variant on the planet.
-For makefile complexity, I guess there is a scale ranging from a hack like just typing "g++ *.cpp" in it, through having nice sections, groups of files and definitions like "CFLAGS", all the way up to projects which have 20 different makefiles in them like "Makefile.in", "Makefile.pandora", etc.... Where on that scale should you ideally be?
This is very much a matter of personal preference and project complexity. Autotools or something similar will make it easy for users and distribution maintainers, but can be tricky to use for the developer. If your program is a simple single-file C program, you might forego a Makefile completely; but for something on the scale of the Linux kernel, a Makefile (or something equivalent) is absolutely required.
-Makefiles of many projects look incredibly complex, why?
Some projects are very complex, as in the Linux kernel itself. Other times, the Makefiles generated by automated systems like Autotools can be more complex than they might be if they were hand-crafted. In still other cases the developers like complexity or are barely competent at creating Makefiles and so create something that's more complex than it needs to be.
-What versioning system to use? When to make a 1.0.0? When to append "rc" at the end?
AFAIK, there are no standards on this. A 1.0 release denotes that something has moved beyond "beta test" status -- in other words, you think it's stable and usable for the masses. Open source software authors tend to be conservative in making that judgment, so pre-1.0 releases in the open source world are often as good as post-1.0 releases of commercial software. The bottom line, though, is that it is a judgment call -- what I consider "1.0" software you might consider well beyond that point and something else might consider pre-beta.
As to release candidate (RC), not all projects use that designation at all. It seems to me to be more common among large projects as they approach major release milestones, to denote something that is close to being finalized, but not quite -- essentially a sort of very late beta stage, even if the initial 1.0 release was made some time before.
-When to tag stable versions? And when you change something in head, do you need to change version number every single time?
If the code changes, you should definitely change the version number. Most developers accumulate several changes before making a new official release, though. Personally, I make full releases with three-digit numbers (like 0.8.6 or 0.6.10), and I upload minor changes to my project's git repository with four-digit numbers (like 0.8.6.1 or 0.6.10.2), but don't do full releases with tarballs and RPMs and whatnot for these, except in a limited way if I want specific people to test a recent change because they filed a bug report. Others have other systems.
-When creating a dynamic library, and you tagged a stable version, and you then change something in head. Should in the makefile the version number of the library name be changed to something? If so, should it be changed to a next minor version, or to something with "-rc" at the end?
The key difference with dynamic libraries is that the interfaces should not change with minor changes. IIRC, the second digit (like "2" in 1.2.3) is the cutoff point. In other words, a program that uses library version 1.2.3 should continue to work without changes or recompilation with library 1.2.4 or 1.2.2 (assuming no bugs). This enables users to upgrade the library (from 1.2.3 to 1.2.4 or the like) without upgrading every binary that relies on it. With version 1.3.0, though, the interface to the library might change in a way that would require recompilation of the program or even changes to the source code. Thus, changing the library from 1.2.4 to 1.3.0 will require the user to upgrade all the programs that use that dynamic library (or keep the old version around along with the new one). Note that I've never created a publicly-released library, and it's been a while since I've read up on this, so I might be a little off on these details.
-What names should be used for tags of versions?
I'm not sure what you mean by this.
-Does there need to be both a zipped version of the source code and one under VCS, and if so why is that zipped version needed?
You can do it any way you want; but as a general rule, you should provide source code in a tarball or .zip file because that's easier to download. Some package systems, such as RPM, require that a source package filename be specified, and so not providing source in such a package just complicates matters for packagers and therefore makes it less likely that they'll bother packaging your program at all. This in turn makes it harder for your users to use the program.
Note that most Linux programs' source code is provided as tarballs rather than as .zip files. Some cross-platform programs can be exceptions to this rule. For instance, I used .zip for rEFInd (a boot loader) because .zip is a little more common in Windows -- although I'm sure either would have worked fine, in practice.
You should probably provide binary builds of your software -- although in some cases this can be tricky because a binary built for Distribution A may not work on Distribution B because of library differences. The OpenSUSE Build Service (OBS) can help with this, although it's a bit of a pain to use.
-Are there any naming conventions for output binaries and libraries?
Not AFAIK, except of course for filename extensions like .so and .a.
-Are you supposed to let your makefile clean up .o files after compilation or not?
No, except for the "clean" target and anything else that's supposed to do this.
-Are there any conventions for makefiles for names of sections and variables in it? E.g. is it a good idea to have a "clean:" in your makefile to remove everything?
The "all" target builds everything, "clean" cleans up, "install" installs everything, and "uninstall" uninstalls everything. There's no law that says you have to have all of these, but they're common, particularly with big projects.
-When depending on another library which is hosted somewhere else, how to handle that? What when statically depending on it?
This type of thing is generally handled by packaging programs (pacman, rpm, dpkg, etc.), not by developers' Makefiles. That said, Makefile builders like Autotools should check for the relevant development libraries and stop if they aren't present. That will handle the static linking issue, as well as other problems. On another level, when using RPM, a source RPM will include dependencies on the relevant development libraries, and Debian source files have a similar feature. Putting these files together is the responsibility of distribution maintainers, not of program authors.
-Any other things I should know?
There's a huge range of acceptable practices on these issues. As a general rule, though, the smaller the package the more likely you are to find a simple Makefile that builds the whole project. Bigger projects are more likely to rely on multiple Makefiles, Autotools, or other complex pre-build software. More standardization emerges at the distribution level, in the form of source and binary RPMs, Debian packages, etc. You shouldn't need to worry too much about that. So long as your package builds with few or no changes on a variety of distributions, the distribution packagers can handle the rest. Build systems always support patches so that minor changes to Makefiles or whatnot can be incorporated. This frees you up to worry about other things rather than trying to support every minor variant distribution in existence.

EngLab - Open source mathematical/engineering platform

Hello all,
I'm new to Archlinux and quite exited with it. Anyway, some colleagues of mine from the University and me have created an engineering platform for the Linux platform, although Windows builds are also available. If you like check it out, but be aware that it's still on an early development stage.
(I hope this is the right board to post this )
Website: http://englab.sourceforge.net/
Now that I am into Arch I'm going to make some research and create a build system for it to run on Arch and with your help maybe enter the AUR.
Here is our press presentation for the first big release (now we're on 0.2.1alpha):
We are pleased to inform you that the 0.2alpha release of the open-source program EngLab has been published.
Our site is located to englab.sourceforge.net . You can download it from https://sourceforge.net/project/showfil … _id=206384
EngLab is a cross-compile mathematical platform with a C like syntax, intended to be used both by engineers and users with little programming knowledge. The initiative has been taken from a group of students a year ago.
Our goal is to develop an easy-to-use computaion and simulation platform with a C++ like syntax. We have adopted Matlab's structure philoshophy and C++ 's structured language syntax. There are various toolboxes (packages of functions relative to a certain scientific field), which depend on open-source libraries.
The EngLab distribution is available in two ways: there are two basic Englab releases, EngLab Console and EngLab GUI. EngLab Console allows EngLab's execution through the console(Linux or Windows). EngLab GUI gives the opportunity of using EngLab through a graphical user interface. EngLab GUI is implemented with the use of the open-source library wxWidgets 2.8, providing additional usability compared to EngLab Console edition. EngLab GUI is independent, so there is no need for EngLab Console to be installed, in order to properly install and execute EngLab GUI.
Toolboxes are distributed as seperate packages. Their installation is possible either through EngLab Console or EngLab GUI. The reason is that those toolboxes depend on open-source libraries that have to be previously installed. So as the user not to be forced to install those libraries directly, user can install packages and toolboxes at his/her own will.
For the time being, EngLab Console edition is available for Windows and Linux and Englab GUI is available for Linux only.
Until now EngLab has the following features :
- 16 types of variable declaration (int, float, ...)
- Variable declaration with unlimited number of dimensions.
- Loop structures (for, while, ...)
- Arithmetic, logical and binary operations
- Constant number declaration (pi, phi, ...)
- Graphical manipulation of variable values of any dimension (Englab GUI)
- Adjustable graphical environment (Englab GUI)
- Editor for writing *.eng functions (Englab GUI)
- Command history for the last 5 sessions
- Immediate access to variables, constants and functions (EngLab GUI)
- Recent files opened through EngLab (EngLab GUI)
Toolboxes that have been fully or partially implemented:
- a package containing fundamental functions of C (trigonemetric, hyperbolic trigonometrical, ...)
- a package containing some statistic functions
- a package containing functions that allow convertions of the variable type
All these toolboxes accompany the basic two EngLab editions, since they do not depend on another open-source library. Moreover, some other toolboxes have been partially implemented:
- a package that contains functions for the manipulation of 2-D matrices (determinant, inverse array, ...). This package depends on the open-source library NewMat10.
- a package that contains functions for image processing. This package depends on the open-source library CImg.
- a package that contains functions for image processing. This package depends on the open-source library OpenCV.
Also, we develop
- a toolbox for visual data representation(plots etc)
- a toolbox that contains functins for manipulating polyonymials, root detection, computation of integrals and derivatives, special functions and more.
Those two toolboxes will be available in the next releases.
The disadvantage is the number of EngLab developers, which does not allow EngLab's quick development. Thus, helping us would be welcomed.
You can help us with the following two ways:
- By reporting bugs, which you have observed during EngLab execution. You can report bugs in https://sourceforge.net/tracker/?group_ … tid=997443 . Moreover, you can suggest new features that would improve EngLab's usability and performance. New features can be suggested in https://sourceforge.net/tracker/?group_ … tid=997446 .
- If you would like to get more into EngLab, you can become EngLab developers and help us. That requires C++ knowledge.
If you have read till here, that's a good sign. Wink
You could ask questions in the mailing list [email protected] or in the forum .
EngLab development team :
Bugfest development team :
Serenis Charalampos - PhD student of the Department of Electrical and Computer Engineering of Aristotle University of Thessaloniki(Greece).
Tsardoulias Emmanouil - PhD student of the Department of Electrical and Computer Engineering of Aristotle University of Thessaloniki(Greece).
Gavves Efstratios - Dipl. Engineer of the Department of Electrical and Computer Engineering of Aristotle University of Thessaloniki(Greece).
Parastatidis Nikolas - Postgraduate student of the Department of Electrical and Computer Engineering of Aristotle University of Thessaloniki(Greece).
Also contributed:
Gkekas Christos - Dipl. Engineer of the Department of Electrical and Computer Engineering of Aristotle University of Thessaloniki(Greece).
Vogianou Thanassis - PhD student of the Department of Electrical and Computer Engineering of Aristotle University of Thessaloniki(Greece).

We are glad to announce that version 0.3 of Englab has been released. The new version contains several bug fixes and improvements in the kernel, a new and advanced GUI based on the Qt toolkit and toolboxes with several functions. Amongst the featured toolboxes are:
- cimgbox, image processing and manipulation toolbox
- plotbox, toolbox for plotting graphs and figures
- dspbox, toolbox for Digital Signal Processing and audio processing
as dynamic (external) toolboxes and:
- analogfilters, toolbox for analog filter design
- unit conversions toolboxes, complex numbers toolbox, polynomials toolbox, stats toolbox etc.
as static (internal) toolboxes.
Englab is available for GNU/Linux, Unix (not tested) and Windows32 platforms.
For GNU/Linux
- Platform-independent
The source tarballs are available at:
http://sourceforge.net/project/showfile … _id=206384
- Debian/Ubuntu (and other Debian-based distributions)
Precompiled deb packages are available for download here:
http://sourceforge.net/project/showfile … _id=292500
or to use our Debian repository, simply add it to your package sources by appending the following lines to /etc/apt/sources.list
deb http://englab.bugfest.net/debian unstable main
deb-src http://englab.bugfest.net/debian unstable main
(Please note that you need to have root permission in order to edit the sources.list file)
- Archlinux
PKGBUILD scripts are available in AUR:
http://aur.archlinux.org/packages.php?O … _Search=Go
or in sourceforge:
http://sourceforge.net/project/showfile … _id=292585
and also precompiled Arch packages exist in our Archlinux repository. In your /etc/pacman.conf add the following lines for the i686 architecture:
[englab]
Server = http://englab.bugfest.net/arch/i686
and for the x86_64 architecture:
[englab]
Server = http://englab.bugfest.net/arch/x86_64
then execute:
# pacman -Syu
to allow pacman to synchronize with the repository and:
# pacman -Ss englab
to see all the available packages.
- Fedora
RPM packages can be downloaded from sourceforge:
http://sourceforge.net/project/showfile … _id=324683
For Windows
Download the zip from sourceforge:
http://sourceforge.net/project/showfile … _id=324502
and unzip it to the directory of your choice.
For possible bugs, feature requests and any comments you may have please send us an e-mail at:
[email protected]
Thank you!

New Open Source Broadcom WIFI driver, where to start?

Hello I want to install new Broadcom Open Source driver brcm80211 for my Broadcom BCM43225 WIFI card but I'm kinda confused where to start. First of all this driver is not available in Arch repositories nor AUR, so I guess there's only GIT way in which I'm not too much familiar. At the moment only Debian has this driver available in it's backports kernel but that is useless for Arch Linux user, except for the firmware loading instructions. So please help me, I have exported the whole 500MB+ git "next staging" tree, and now I would like to figure it out how to compile brcm80211 module and eventually use it with Arch kernel. Thanks in advance.
Last edited by Riot777 (2010-09-28 23:00:45)

I spent close to an hour shortly after it was added to the staging-next branch and managed to compile it against 2.6.35.4 (not sure about the .4 part however). Unfortunately, it wasn't especially stable and got some kernel oops on suspend. After that, I went back to using the wl module.
Recent changes don't look like they could have improved the stability of the driver by much, so I'd advise against using it for now.
With the above said, if you're feeling adventurous you can build the driver as follows:
0. Make sure you have the `base-devel' group installed, along with `kernel26-headers' (preferably version 2.6.35.6-2 as 2.6.35.6-1 had some issues) and `linux-firmware' 20100911-1 (the one in [core] doesn't contain the firmware files for brcm80211 AFAIK).
1. Grab just the brcm80211 directory from the staging-next branch by clicking the `snapshot' link on this page.
2. Extract the compressed tarball and then open a terminal inside the staging-next-2.6-x directory that gets created.
3. Change the Makefile a little by running `curl -s http://ompldr.org/vNW82NA/Makefile.patch | patch -Np0'. After that, run `make'.
4. Now, you should have the compiled module `brcm80211.ko' in the current directory, which you can copy into `/lib/modules/2.6.35-ARCH/updates/'. (Create the updates directory if it doesn't exist.)
I didn't test the above steps thoroughly and I'm not certain this is the correct way to build the driver. However, I believe it'll get you a working kernel module.

Who here thinks that sound diver should be open sourced?

wouldn't it be cool if sound diver was open sourced so that it could be continued?

well. i am a stupid when it comes to that kinda thing. i thought about unisys, but i doubt it will work. i am in the middle of sampling patches into the exs. i bet i am doing that wrong as well. thought about autosampler from redmatica, but needed to save the $135 that it would cost me. so i am rudely doing it myself. i have sound diver for windows, and that works well, but i have to get some of this gear out of my way. i am sick of having to step over things to get to the computer, and well to tell you the truth most of it isn't hooked up. i haven't built my dream home yet so i don't have a dedicated area for recording and booth. blah blah blah.. LOL
just had a thought, and wanted to see who shared it.

Installing Sirius open-source intelligent assistant for Ubuntu on Arch

I'm looking to install Sirius an open-source intelligent personal assistance similar to Apple's Siri or Microsoft Cortana http://sirius.clarity-lab.org/. As of now all of the install scripts and packages are set for Ubuntu. What would be the best way to install this on Arch?

karol wrote:
legolas558 wrote:
dcc24 wrote:
So, let me get this straight. You have a precompiled binary for Windows and a source package for Arch. And you are wondering why does compiling take time? If an Arch binary existed, which you can obtain by compiling, installation would be fast in Arch too.
Also, this is not about "FreeCAD not being for Arch newbies", it is about knowing the binary/source difference and if you are having problems comprehending that, then I suggest you do some reading before putting the blame on Arch.
I am specifically complaining about the lack of a pre-compiled binary package for freecad (and its dependencies, like the huge opencascade) in Arch Linux. I regularly use Arch Linux, Gentoo, Debian and Ubuntu so, yes, I know the difference. I am just saying that Arch Linux + binary package for freecad is better than Arch Linux without it, so I'd like to know why it was excluded and/or nobody ever tried to submit it for the [community] repo.
Too many packages, to few people maintaining them.
This is the information I needed. Thanks. I have asked because I really didn't know the reason nor could find why it was not on [community]. I thought about non-free dependencies, security issues or whatever, but I really didn't know.
karol wrote:Please, just because the package *you* care about is not in the [community] you have to start a thread?
I don't care particularly for this package or for any other...I just picked up an use case which (partially) fails because (1) you can't know in advance how long it will take, (2) system can hangup (it just did!) and then you loose the partially compiled package, (3) the future upgrades will be bloody as well.

Interim patch vs database patch

Hi,
I want to know the exact difference between Interim patch and database patches.
First of all my understanding is that ,Database patches are applied for some ORA-related errorrs as suggested by document id.where as interim patches are applied on ORA_HOME.
plz correct me if i am wrong?and give me complete details about them.
Also i want to know,is there any database patch for ORA-1555 error?
Thnx

791902 wrote:
Hi,
I want to know the exact difference between Interim patch and database patches.
First of all my understanding is that ,Database patches are applied for some ORA-related errorrs as suggested by document id.where as interim patches are applied on ORA_HOME.
plz correct me if i am wrong?and give me complete details about them.All patches are applied on binaries i.e. ORACLE_HOME and some patches also have some scripts to be run to update data dictionaries.
For interim patch explanation please refer to MOS :
Oracle Data Server Interim Patch Installation (OPatch) [ID 189489.1]
Also i want to know,is there any database patch for ORA-1555 error?ORA-155 occurs due to undo tablespace.
check MOS note :
TROUBLESHOOTING GUIDE (TSG) - ORA-1555 [ID 467872.1]
You can also check :
http://www.dba-oracle.com/t_ora_01555_snapshot_old.htm
Regards
Rajesh
Edited by: Rajesh on Sep 7, 2010 4:29 PM

ATI Radeon drivers problems (both open-source and proprietary)

Hi 2 All!!
I have a problem with my ATI Radeon 9000-series. The open source drivers (xf86-video-ati) don't work very good for me, my monitor's fresh rate isn't "at-top" and the monitor projection is slightly translated to the right (say 8-12 pixels). So I've tried to build the official drivers with ABS, all is gone successfully, except for some worrying warnings, but I thought that it's normal. I have a customized kernel, build through ABS... So, when I've tried to load the fglrx module it says:
# modprobe fglrx
FATAL: Error inserting fglrx (/lib/modules/2.6.27-ARCH/video/fglrx.ko): Cannot allocate memory
Please, help me! My machine is slow, I can't run any OpenGL-accelerated application, even Quake III!!! If you can suggest me how to improve the performance and how to resolve problems with open-source drivers, it also would be very good... Thank you and sorry for my poor English please.

I had some problems with installing ATI drivers recently (could not build fglrx module, not even manually, I had to change some installation script), but with latest driver version (8.11 I think) from ati.amd.com was everything fine (I have Radeon 9600 Pro)
Try to do this (and write here the output)
glxinfo | grep vendor
fglrxinfo
In both cases, it should write something like OpenGL...: ATI... if there will be MESA or DRI, that means that you don't have loaded your fglrx module.
If fglrxinfo output will be something like: no permission for...(should be first or second line of the output), then write this somewhere in your xorg.conf:
Section "DRI"
Mode 0666
EndSection
run:
modprobe -a fglrx - and give here the output. If there will be none, run:
lsmod | grep fglrx - to see wheter fglrx module is really loaded in kernel
if you will have no module, you can install one, type:
cd /lib/modules/fglrx/build_mod
sh make.sh
cd ../
sh make_install.sh (as root)
and post any warning or error here at forum, drivers (but not fglrx module) are installed at /usr/share/ati
After installing drivers, you also need to configure your system (notice your system that it's there), commands:
aticonfig --initial (for editing your xorg.conf)
aticonfig --overlay-type=Xv (acceleration support in xorg.conf)
Showing your xorg.conf file here is also good idea, here is mine (sections Device and Screen):
Section "Device"
#VideoRam 262144
# Insert Clocks lines here if appropriate
Identifier "** ATI Radeon (generic) [radeon]"
Driver "radeon"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen 1"
Device "** ATI Radeon (generic) [radeon]"
Monitor "My Monitor"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
Monitor "aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

[ANN] XINS 2.1 open source Web Services framework release

XINS 2.1 Web Services Framework has been released.
XINS is an open source Web Services Framework based on simple specifications of the Web Service in XML and
generation of code and documentation from the specification.
The generation includes Client JAR with its Javadoc, Server side template with its Javadoc, documentation in OpenDocument Format,
documentation in HTML including the test forms, WSDL file, unit tests (JUnit) and stubs.
The Web Services accept several protocols including REST, SOAP, XML-RPC, XML, JSON Yahoo! and JSON-RPC.
What's new:
* Start the API with java -jar <api name>.war
* Improved generated specification in OpenDocument Format
* Include/exclude calling convention with ACLs
* New calling convention that maps SOAP request and response as the wsdl2api command mapping.
* Smaller generated build.xml
* Added possibility to include other runtime properties files
* The runtime property location can be a URL
* Swing Graphical User Interface
* New tools: emma, glean, webstart
* New target: javadoc-test-<api name>, javadoc-apis
* Bug fixes and small RFEs
Download XINS 2.1:
Windows installer: http://prdownloads.sf.net/xins/xins-2.1.exe?download
TAR GZ archive: http://prdownloads.sf.net/xins/xins-2.1.tgz?download
Resources:
Web site: http://xins.sourceforge.net/
XINS demos: http://xins.sourceforge.net/demo.html
Documentation: http://xins.sourceforge.net/documentation.html
User guide: http://xins.sourceforge.net/docs/index.html

I recommend you implement your web service with JAX-WS 2.0
Axis (both version) are good but why do you want to use something that is not included in JEE API, when Java provide same thing with better performance.
personally try to prevent non standard technologies despite they can be better than core java implementation sometimes.
I don't know Xfire.
the good:
-JAX-WS performance is better than axis,
- you can create your web service simply with annotation.(this means write class and then make it as a service easily)
- support every kind of service invocation(callback,Asynchronous,...)
- architecture is nice (you can operate on SOAP level)
the Bad:
- It is JEE 5 or JSE 6 dependent.
- there is seriously lack of documentation and examples for it, on java web sites and internet.

DBAShell - New Open Source Project for Oracle DBA's

I'd like to have this project included in the Open Source Oracle tools list at: http://www.oracle.com/technology/community/opensource_projects.html
I've been an Oracle DBA for quite some time (since 7.0.13) and a developer for many years. One of the things I've always wished for was an easier way to set up environment variables for different Oracle Homes and a way to provide passwords to scripts without embedding them in plain-view.
About 3 years ago, I started a set of functions and scripts at my company that did exactly just that and provided many more functions for things like checking database status, running scripts quietly unless errors are detected, running actions in parallel (like fast shutdowns at once, or multiple analyzes), restarting databases in a guaranteed fashion, aliases to common folder locations, etc..
About a month ago, after putting all this time and effort into these scripts and using them in production all this time, I realized I wanted more out of the scripts like support for other databases and thought that it would be best if I gave it new life as an Open Source project.
So that is how http://sourceforge.net/projects/dbashell/ was started. Now its in a second release (DBAShell 0.85) that is more modular and would allow other people to easily add support for other OSs, other Shells, and other Databases.
Here is a description of the project from the latest news item:
DBAShell is a project based around Shell functions and scripts designed to make it easy for DBA's to use Databases in a command line environment. Currently supported is Oracle with ksh and bash on AIX, Solaris, Linux. The code base itself is 3 years old and has been in use in Production environments all of that time.
Features include:
* Automatic setting of all environment variables based on SID requested.
* Manage PATH's and other path like variables for each ORACLE_HOME needed.
* Run scripts with stored passwords (no more hard-coding of passwords!!)
* Automatically set SID based on Script location (makes it easier to share scripts between SID's)
* manage temporary script output and check for oracle errors in output
* check database status and versions from scripts
* stop/start databases in parallel (faster startup)
* compile all database objects
* analyze objects in parallel (Faster analyzes)
* set aliases and variables for common SID areas, etc..
* many helpful commands for common Oracle tasks
Over a thousand people have already downloaded the prior release and more are downloading every hour.
I'm seeking feedback from anybody that would be willing to take a look at the project, trying it out, give me any feedback you have on it, and perhaps even direct me to where I could best promote this project.
I wrote a tutorial that shows at a glance some of the more useful features of DBAShell:
http://sourceforge.net/docman/display_doc.php?docid=34041&group_id=170224
Main site:
http://sourceforge.net/projects/dbashell/
Documentation: http://sourceforge.net/docman/display_doc.php?docid=33704&group_id=170224
Download:
http://prdownloads.sourceforge.net/dbashell/dbashell-0.85.tar.gz?download

Always glad to have people thinking about the poor DBA's. Usually, the developers get most of the attention in open source.

Open Source patching or scripting patch installs

Similar Messages

Maybe you are looking for