April 27th, 2010 by elizar
Here’s another Kernel patching of Solaris. I know there are tons of this type of post in the internet but another reference for the one who needs it, is I guess ok.
To be honest, this is the steps that really made me understood the steps and procedure and the concept behind the 10_Recommended patch for solaris kernel.
Read the rest of this entry »
April 23rd, 2010 by elizar
Just deleted tons of stale, unsused user accounts. Here are some KSH shell basics and special shell variable. I need to Google them up myself to get reminded that ‘$?’ is the output variable for script execution. That is, it’s 0 for successful execution and 1 if there is any error.
Read the rest of this entry »
April 20th, 2010 by elizar
J1708 or by it’s complete name SAE J1708, is a standard used for serial communications between ECUs on a heavy duty vehicle and also between a computer and the vehicle.
If you’re familiar with data communication or networking, the SAE J1708 is categorized in the Physical layer of the Open System Interconnection model (OSI).
Common higher layer protocols that operate on top of J1708 are SAE J1587 and SAE J1922.
This post is under ‘gadget’ since I was looking for a way to interconnect my GPS device to my car a few months back.
The standard defines a 2-wire 18 gauge wire cable that can run up to 130 feet (40 m) and operates at 9600 bit/s. A message is composed of up to 21 characters, unless the engine is stopped and the vehicle is not moving in which case transmitters are allowed to exceed the 21 byte max message length. Messages start with a Message ID (MID) character and finish with a checksum at the end. Characters are transmitted in the common 8N1 format.
April 5th, 2010 by elizar
A quick post on how to setup a public-key authentication on an SSH client server, product by SSH Tectia.
Summary: User instruction on how to setup public-key authentication.
In setting up the ssh public-key authentication between servers, local and remote, we have to generate the key pairs and transfer it to the remote/server.
The publickey authentication method is enabled by the SSHtectia package by default. A functional ID’s key pair can be generated using the ‘generate_keys’ script (may be located in /export/opt/SSHtectia//util/ or depending on your installation). That script, ‘generate_keys’, is use to generate user key pairs: id_dsa_2048_a and id_dsa_2048_a.pub (default names) in the centralized key location:
The script also creates an ‘identification’ file in /etc/opt/SSHtectial/keys/ that contains the name of the private keys:
# more identification
# SSH Tectia private key
# OpenSSH private key
Don’t forget to substitute the private key filename for ‘id_dsa_2048_a’ or ‘id_dsa’ if you are using a different naming convention. If several key pairs are used, list private keys on a separate lines.
The publickey authentication method is enabled for functional IDs ONLY by the SSHtectia package (how do we know if an account is such?).
Copy the public key file (i.e. id_dsa_2048_a.pub) to the server, to the centralized key location. You can use sftp, copy paste or any other method to do this.
Also copy the ‘authorization’ file (created by the ‘generate_keys’ script) from the cliet to the server’s centralized key location.
Test the connection.. it should work.. It worked on mine.