A detailed description of the Arbortext 5.1 XSL FO support is
available at:
https://www.arbortext.com/support/html/arbortext51/ati_xsl.htm
October 25, 2005
Arbortext XSL Support
October 23, 2005
Starting at Runlevel 3 instead of Runlevel 5
If you do not want to start X automatically edit the /etc/inittab
file like this:
id:3:initdefault:
What wireless networks are available
Wireless support in Linux is still an area that needs work. Currently
there is no reliable UI like in Windows that lists all of the networks
that are available, however there is a way to get the information from
the command line.
Use the following procedure to determine what wireless networks
are avilable:
- Open a terminal and switch to the root user
- Issue the command /sbin/iwlist scan
- The results should list all of the ESSID's available as well as
information on Channel and Encryption information.
October 18, 2005
Adding Additional RPM sites to yum search
To add additional sites that have RPMs for Linux:
1) Add the site to the yum config file under /etc/yum.conf
Example:
[atrpms]
name=ATrpms for Fedora Core $releasever
baseurl=http://apt.atrpms.net/fedora/$releasever/en/$basearch/at-stable
2) Find the sites public signing key
Example:
rpm --import http://ATrpms.net/RPM-GPG-KEY.atrpms
Now when you do a yum install or update that site is added to sites
searched for RPMs. A note, be very careful with sites that have RPMs at
what's called RPMS.at-bleeding since these tend to be the raw
development builds and can lead to "bad things".....
October 16, 2005
Patch available for VMWare 5 on Fedora Core 4
VMWare 5 will not run on FC4 without running the vmware-any-any-update
after installation.
Instructions:
- Install VMWare 5
- Grab the latest vmware patch from http://knihovny.cvut.cz/ftp/pub/vmware
- Extract the files into a temporary directory.
- CD into the directory and run the runme.pl script.
- This replaces two files in the VMWare installation with updated
version for FC4. - Run vmware-config.pl
REFERENCES
- https://www.vmware.com/community/thread.jspa?threadID=18088&tstart=0
October 6, 2005
ACID Test & Transactions Defined
Acid test is a phrase that can also refer to a foolproof test that will accurately determine the validity of something. The origins come from the gold rush in the United States. Gold does not react to most acids (unlike most metals) but does to nitric acid. The acid test was then used to confirm if gold was indeed found.[1]
Transactions provide several important properties, referred to as the ACID properties: [2]
- Atomicity:
A transaction is either successful or unsuccessful. Either all of the operations that make up a transaction take effect or none take effect. A successful transaction is said to commit. An unsuccessful transaction is said to abort. Any operations performed by an aborted transaction are undone (rolled back) so that its effects are not visible. - Consistency:
A transaction transforms distributed data from one consistent state to another. The application program is responsible for ensuring consistency. - Isolation:
Each transaction appears to run independently of other transactions that are running concurrently. The effects of a transaction are not visible to others until the transaction completes (commits or aborts). The transactions appear to be serialized, with two or more transactions acting as though one completed before the other began, even though they are executed concurrently. - Durability:
Also known as permanence, this property ensures that once completed, the effects of a transaction are permanent. A subsequent failure (such as abnormal program termination, communications failure, or hardware failure) does not cause the effects to be undone. Transactions are often used to control and moderate access to a centralized database. Typical uses for transaction processing systems include database-oriented applications such as airline reservation systems and automatic bank-teller machines.
[1] From Wikipedia
[2] Red Hat Web Application Framework Developer Guide