02-23-2009
May I suggest an alternative route to that end: Build a small network containing those OSs and applications that you have in production, plus a dedicated server to roll out updates. When the distributor puts new updates online, apply them to the test environment first. If they still behave well after a certain period (eg. 2 weeks), put them on your internal update server, from which your other machines can automatically update. Those that don't work just get skipped.
As for the test environment: if you don't have any special hardware needs, virtualization works just fine (VirtualBox, VMware, ...)
8 More Discussions You Might Find Interesting
1. AIX
given any specific fix, how can I determine if the machine will require a reboot? (I don't have a window for downtime)
obvious fix's to the kernel / lvm will require a reboot ... bos.rte files etc...
is there a tool or command that I am able to run against a specific IY that will inform me... (4 Replies)
Discussion started by: A Stewart
4 Replies
2. Solaris
Hi - How can I determine the time my system was last booted when my "wtmp" file is broken? (It is being cleaned out incorrectly, I'mm working on that issue)
ie
uptime shows invalid details and who -b shows "nothing at all"
is there a shutdown log somewhere that may indicat the last re-boot? (3 Replies)
Discussion started by: Andrek
3 Replies
3. Solaris
Hi Folks,
Is there anyway I can determine the package set (or SIP) that a package belongs to. It doesn't seem that pkginfo does it?? I'm trying to remove a whole lot of unecessary packages, and it would be far more convenient if I could remove whole sets at a time instead of indivdual packages.... (0 Replies)
Discussion started by: brizrobbo
0 Replies
4. Linux
have following package installed
rpm -qa |grep ADMIN
It will give the following package installed:
ADMIN-4.0.0.1
Now I will upgrade the ADMIN package using the following command.
rpm --upgrade ADMIN-4.1.0.1
It will upgrade the ADMIN packagge to ADMIN-4.1.0.1
Now I want that... (0 Replies)
Discussion started by: amitpansuria
0 Replies
5. UNIX for Dummies Questions & Answers
Dear linux-unix users,
I hope that one of you will be able to help me.
How can I determine to which package a file or binary belongs to.
With solaris/linux package managers you can easely determine this but i cant find the way how to do this on tru64.
Any help would greatly be appreciated.... (0 Replies)
Discussion started by: Crazy_lenny
0 Replies
6. UNIX for Advanced & Expert Users
Friends,
Please let meknow, How we can find the dependancies of .dstream package & .rpm package before installation ?
For AIX, We can use the inutoc . command to create the .toc file for the bff package, What about Solaris & Linux ? (0 Replies)
Discussion started by: yb4779
0 Replies
7. UNIX for Dummies Questions & Answers
Hello,
i have downloaded an rpm package "hadoop-0.20.205.0-1.amd64.rpm"
in /usr/local/ directory.
I'm trying to install the rpm package in a new path/location (/usr/local/hadoop-0.20.205), but i can't.
I did:
1st try: Didn't work
sudo rpm -i --prefix=/usr/local/hadoop-0.20.205... (1 Reply)
Discussion started by: g_p
1 Replies
8. Emergency UNIX and Linux Support
Hello,
i have installed a package by using the command
sudo rpm -i filepackage.rpm
package filepackage is already installed
when i try to remove it, i get an error saying "is not installed":
sudo rpm -e filepackage.rpm
error: package filepackage is not installed
How can... (4 Replies)
Discussion started by: g_p
4 Replies
apt(1) General Commands Manual apt(1)
NAME
apt - annotation processing tool
SYNOPSIS
apt [ -classpath classpath ] [ -sourcepath sourcepath ] [ -d directory ] [ -s directory ] [ -factorypath path ] [ -factory class ] [ -print
] [ -nocompile ] [ -A [ key [ =val ] ] ] [ javac option ] sourcefiles [ @files ]
DESCRIPTION
The tool apt, annotation processing tool, includes a set of new reflective APIs and supporting infrastructure to process program annota-
tions. The apt reflective APIs provide a build-time, source-based, read-only view of program structure. These reflective APIs are designed
to cleanly model the JavaTM programming language's type system after the addition of generics. First, apt runs annotation processors that
can produce new source code and other files. Next, apt can cause compilation of both original and generated source files, easing develop-
ment. The reflective APIs and other APIs used to interact with the tool are subpackages of com.sun.mirror.
A fuller discussion of how the tool operates as well as instructions for developing with apt are in Getting Started with apt at
http://java.sun.com/j2se/1.5.0/docs/guide/apt/GettingStarted.html.
PARAMETERS
Options may be in any order. For a discussion of parameters which apply to a specific option, see OPTIONS below.
sourcefiles Zero or more source files to be processed.
@files One or more files that list source files or other options.
OPTIONS
apt specific options
-s dir Specify the directory root under which processor-generated source files will be placed; files are placed in subdirectories
based on package namespace.
-nocompile Do not compile sources files to class files.
-print Print out textual representation of specified types; perform no annotation processing or compilation.
-A[key[=val]] Options to pass to annotation processors -- these are not interpreted by apt directly, but are made available for use by
individual processors
-factorypath path
Specify where to find annotation processor factories; if this option is used, the classpath is not searched for factories.
-factory classname
Name of annotation processor factory to use; bypasses default discovery process
Options shared with javac
-d dir Specify where to place processor and javac generated class files
-cp path or
-classpath path
Specify where to find user class files and annotation processor factories. If -factorypath is given, the classpath is not
searched for factories.
Consult the javac(1) man page for information on javac options.
NOTES
The apt tool and its associated APIs may be changed or superseded in future j2se releases.
SEE ALSO
javac(1) java(1)
13 June 2004 apt(1)