1. Download jre-6u20-linux-x64.bin
2. ./jre-6u20-linux-x64.bin
3. ln -s /tmp/jre1.6.0_21/lib/amd64/libjavaplugin_jni.so /usr/lib/mozilla/plugins/libjavaplugin.so
4. ls -al /usr/lib/mozilla/plugins/libjavaplugin.so
nothing is impossible!!!!
Tuesday, June 15, 2010
Monday, June 14, 2010
update rhel4 packages
You can use "update -u" to update the packages on RHEL4.
If it does not give you any indication of package updation try to clear cache (rm -rf /var/spool/up2date/*) and fire above command again.
Even if above method doesnt work. Login to your respective rhn satellite.
1. Select Critical, Non-critical packages.
2. Select All.
3. at the bottom, select update packages
4. then confirm.
5. ssh to the respective system, and run "rhn_update -vvv". It should show updating package details.
If it does not give you any indication of package updation try to clear cache (rm -rf /var/spool/up2date/*) and fire above command again.
Even if above method doesnt work. Login to your respective rhn satellite.
1. Select Critical, Non-critical packages.
2. Select All.
3. at the bottom, select update packages
4. then confirm.
5. ssh to the respective system, and run "rhn_update -vvv". It should show updating package details.
Monday, April 26, 2010
Good article on iscsi
http://www.idevelopment.info/data/Unix/Linux/LINUX_ConnectingToAniSCSITargetWithOpen-iSCSIInitiatorUsingLinux.shtml#About%20the%20Author
Thursday, April 15, 2010
How to select specific storage ?
What is largest amount of data do you manage?
How much data is significant for you?
have you planned about deletion of data?
how ofter will you delete data? schedule?
Who is gone access your data? ex. applications, servers ?
are you planning to host your applications as well?
how must data application gone consume?
how much your application data may grow?
How busy will be your storage?
applications future plans?
How much data may grow in future?
If data not available, how does unavailability cost your org?
are you planning to archive data?
Why do you want to archive data?
how ofter are you planning to archive data?
for how long will you keep archive data?
existing data managements issues?
data center to manage data storage equipment?
Enough space in datacenter?
How much data is significant for you?
have you planned about deletion of data?
how ofter will you delete data? schedule?
Who is gone access your data? ex. applications, servers ?
are you planning to host your applications as well?
how must data application gone consume?
how much your application data may grow?
How busy will be your storage?
applications future plans?
How much data may grow in future?
If data not available, how does unavailability cost your org?
are you planning to archive data?
Why do you want to archive data?
how ofter are you planning to archive data?
for how long will you keep archive data?
existing data managements issues?
data center to manage data storage equipment?
Enough space in datacenter?
Tuesday, April 13, 2010
kickstart fully automatic installtion for rhel
Note: Please remember options may vary depend on OS, network settings, os update version etc.
This fully automatic installation cfg is for RedHat 5 OS.
This fully automatic installation cfg is for RedHat 5 OS.
install
text
nfs --server=192.168.1.9 --opts=tcp --dir=/pub/rhel/released/RHEL-5-Client/U5/i386/os
keyboard us
lang en_US
key --skip
reboot --eject
selinux --disabled
firewall --disabled
rootpw redhat
timezone --utc Asia/Kolkata
network --onboot yes --bootproto dhcp --gateway 192.168.1.1 --nameserver 192.168.1.10
#Setup default services
services --disabled=cups,messagebus,ip6tables,isdn,pcmcia,hidd,bluetooth --enabled=ntpd,nscd
# Disk Setup
bootloader --location=mbr --append="rhgb console=tty0 console=ttyS0,9600"
clearpart --all
# auto disk partition
part /boot --fstype ext3 --size=100
part swap --fstype swap --size=2048
part pv.1 --size=0 --grow
volgroup AutoVolGroup pv.1
logvol / --vgname=AutoVolGroup --name=root --size=1 --grow
%packages
@core
@system-tools
%post
cat <> /etc/motd
Lab automatic kickstart installation.
Installed `date`
EOF
cat /etc/motd >> /root/ks.cfg
Subscribe to:
Posts (Atom)