Configurations (Linux)

The Force Quit button allows you to click on a window to force an application to quit. This button is useful if you want to terminate an application that does not respond to your commands, if the application has frozen or crashed, for example.

To add a Force Quit button to a panel, right-click on any vacant space on the panel. Choose Add to Panel, then choose Force Quit from the Add to Panel dialog.

To terminate an application, click on the Force Quit button, then click on a window from the application that you want to terminate. If you do not want to terminate an application after you have clicked on the Force Quit button, press Esc.

Procedure to mount remote windows partition (NAS share)

1) Make sure you have following information:
==> Windows username and password to access share name
==> Sharename (such as //server/share) or IP address
==> root level access on Linux

2) Login to Linux as a root user (or use su command)

3) Create the required mount point:
# mkdir -p /mnt/ntserver
4) Use the mount command as follows:
# mount -t cifs //ntserver/download -o username=vivek,password=myPassword /mnt/ntserver

Use following command if you are using Old version such as RHEL <=4 or Debian <= 3:
# mount -t smbfs -o username=vivek,password=D1W4x9sw //ntserver/download /mnt/ntserver

5) Access Windows 2003/2000/NT share using cd and ls command:
# cd /mnt/ntserver; ls -l
Where,

• -t smbfs : File system type to be mount (outdated, use cifs)
• -t cifs : File system type to be mount
• -o : are options passed to mount command, in this example I had passed two options. First argument is password (vivek) and second argument is password to connect remote windows box
• //ntserver/download : Windows 2000/NT share name
• /mnt/ntserver Linux mount point (to access share after mounting)

  Read more

Configure the Network Manually

You can use ip or ifconfig command to configure IP address and other information.

Task: Display the Current Network Configuration

Type the following command:
$ ip address show
Output:

1: lo:  mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc pfifo_fast qlen 100
    link/ether 00:19:d1:2a:ba:a8 brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.1/24 brd 192.168.2.255 scope global eth0
    inet6 fe80::219:d1ff:fe2a:baa8/64 scope link
       valid_lft forever preferred_lft forever
3: ra0:  mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:17:9a:0a:f6:44 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.106/24 brd 192.168.1.255 scope global ra0
    inet6 fe80::217:9aff:fe0a:f644/64 scope link
       valid_lft forever preferred_lft forever
4: ppp0:  mtu 1496 qdisc pfifo_fast qlen 3
    link/ppp
    inet 10.1.3.103 peer 10.0.31.18/32 scope global ppp0

You can also use ifconfig -a command, enter:
$ ifconfig -a
Output:

eth0      Link encap:Ethernet  HWaddr 00:19:D1:2A:BA:A8
          inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::219:d1ff:fe2a:baa8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:15819 errors:0 dropped:0 overruns:0 frame:0
          TX packets:27876 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:1695948 (1.6 MB)  TX bytes:40399983 (38.5 MB)
          Base address:0x1000 Memory:93180000-931a0000 

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:11943 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11943 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:7024449 (6.6 MB)  TX bytes:7024449 (6.6 MB)

ppp0      Link encap:Point-to-Point Protocol
          inet addr:10.1.3.103  P-t-P:10.0.31.18  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1496  Metric:1
          RX packets:34922 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15764 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:50535608 (48.1 MB)  TX bytes:1256881 (1.1 MB)

ra0       Link encap:Ethernet  HWaddr 00:17:9A:0A:F6:44
          inet addr:192.168.1.106  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::217:9aff:fe0a:f644/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:73809 errors:0 dropped:0 overruns:0 frame:0
          TX packets:31332 errors:1 dropped:1 overruns:0 carrier:0
          collisions:27 txqueuelen:1000
          RX bytes:61373519 (58.5 MB)  TX bytes:5007190 (4.7 MB)
          Interrupt:20

Read more

Method-1

# rpm -qa |grep php

 php-common-5.1.6-15.el5.i386
 php-cli-5.1.6-15.el5.i386
 php-5.1.6-15.el5.i386
 php-pdo-5.1.6-15.el5.i386
 php-bcmath-5.1.6-15.el5.i386
 php-ldap-5.1.6-15.el5.i386
 php-devel-5.1.6-15.el5.i386
 php-gd-5.1.6-15.el5.i386
 php-xml-5.1.6-15.el5.i386
 php-mbstring-5.1.6-15.el5.i386
 php-mysql-5.1.6-15.el5.i386
 php-dba-5.1.6-15.el5.i386

 # /etc/yum.repos.d/CentOS-Testing.repo

  # CentOS-Testing:
  # !!!! CAUTION !!!!
  # This repository is a proving grounds for packages on their way to CentOSPlus and CentOS Extras.
  # They may or may not replace core CentOS packages, and are not guaranteed to function properly.
  # These packages build and install, but are waiting for feedback from testers as to
  # functionality and stability. Packages in this repository will come and go during the
  # development period, so it should not be left enabled or used on production systems without due
  # consideration.
  [c5-testing]
  name=CentOS-5 Testing
  baseurl=http://dev.centos.org/centos/$releasever/testing/$basearch/
  enabled=1
  gpgcheck=1
  gpgkey=http://dev.centos.org/centos/RPM-GPG-KEY-CentOS-testing
  includepkgs=php*

you need to start on the command line and in the root users home folder "/root"

Domain Name System

The Domain Name System (DNS) is the crucial glue that keeps computer networks in harmony by converting human-friendly hostnames to the numerical IP addresses computers require to communicate with each other. DNS is one of the largest and most important distributed databases the world depends on by serving billions of DNS requests daily for public IP addresses. Most public DNS servers today are run by larger ISPs and commercial companies but private DNS servers can also be useful for private home networks. This article will explore some advantages of setting up various types of DNS servers in the home network.

Why set up a private DNS server?

This question is valid and the answer may vary depending on your home network environment. Maintaining a host file on each client with IP/hostname mappings in a home network that contains a router and a few machines may be sufficient for most users. If your network contains more than a few machines, then adding a private DNS server may be more attractive and worth the setup effort. Some advantages may include:

• Maintenance: keeping track of the host file for every client in your network can be tedious. In fact, it may not even be feasible for roaming DHCP laptops or your occasional LAN party guests. Maintaining host information in one central area and allowing DNS to manage host names is more efficient.

• Cache performance: DNS servers can cache DNS information, allowing your clients to acquire DNS information internally without the need to access public nameservers. This performance improvement can add up for tasks such as web browsing.

• Prototyping: A private internal DNS server is an excellent first step to eventually setting up a public accessible DNS server to access a web server or other services hosted on your internal network. Learning from mistakes on an internal network can help prevent duplicate errors on a public DNS server that could result in loss of service for external users. Note: Some ISPs require customers to have a static IP or business subscription when hosting services in a home network environment.

• Cool factor: Ok, I may be stretching it, but the "cool" factor did have some influence when I set up my first home network DNS server. Creating an internal domain that reflects an individual's personality without paying a domain registrar and issuing hostnames to your clients is cool. The cool factor doubles when your customized hostname glows from your friend's laptop screen.

Let's start out simply by setting up a caching-only nameserver to handle client DNS requests. A caching-only nameserver won't allow references to internal clients by hostname, but it does allow clients to take advantage of frequently requested domains that are cached.

Read more

Preface:

Some times, we are required to resolve our internal domains on a local nameserver and external (Internet) domains from ISP's nameserver. There are different solutions to this problem, but in this howto, we are going to solve it through configuring a combination of caching-nameserver and BIND 9.

Theory Behind Caching-Namerserver and BIND 9:

Caching-Nameserver is a type of nameserver that will resolve a web addresses (domain names) from its next or master DNS, and will keep those entries in cache, after first time resolution it will resolve DNS queries locally, untill its TTL (Time To Live) is expired. 

BIND 9 is used to resolve domain resolution queries from it own database, as it is SOA (Start Of Authority).

So now it is clear that in our setup the caching-nameserver will be used to resolve domain names externally (internet), while BIND 9 will be used to resolve domain names from our local network (internally).

Now we have caching-nameserver and BIND 9 hammer in our hands, lets start fixing it. 🙂 

Read more

Few Basic Command-

Using 'uname'

uname –m

'uname' more

uname –a

Now something different-

cat /etc/*release

or

cat /etc/*version

SquirrelMail's Apache configuration is in the file /etc/squirrelmail/apache.conf, but this file isn't loaded by Apache because it is not in the /etc/apache2/conf.d/ directory. Therefore we create a symlink called squirrelmail.conf in the /etc/apache2/conf.d/ directory that points to /etc/squirrelmail/apache.conf and reload Apache afterwards:

cd /etc/apache2/conf.d/
ln -s ../../squirrelmail/apache.conf squirrelmail.conf
/etc/init.d/apache2 reload

That's it already – /etc/apache2/conf.d/squirrelmail.conf defines an alias called /squirrelmail that points to SquirrelMail's installation directory /usr/share/squirrelmail.

Now go to the PHP open_basedir field on the Options tab of your web site in ISPConfig and add the directories /usr/share/squirrelmail and /etc/squirrelmail (that's the directory where SquirrelMail's configuration is stored) to the line, e.g. as follows:

"vmware is installed, but it has not been (correctly) configured, for this system. To (re-) configure it, invoke the following command: /usr/bin/vmware-config.pl"

I've been receiving this error since I've been trying to setup VMWare workstation ver 5.0 on my Centos box.

It is now resolve after issueing the command-

VMWARE_DEBUG=yes vmware-config.pl –compile