To set your application’s look and feel to Nimbus:

Right-click on your project in the Projects pane on the left side of the screen and select “Properties” on the pop-up menu. Project Properties window will appear. Click “Application” and click “Desktop App” in the Categories pane. You will see Look & Feel drop-down menu. Select “com.sun.java.swing.plaf.nimbus.NimbusLookAndFeel” and click “OK” button.

To set you Netbeans deafult look and feel to Nimbus:

Open netbeans.conf file. It is usualy located at;

(for Linux)

/usr/local/netbeans-6.5/etc/netbeans.conf

(for Windows)

C:\Program Files\NetBeans 6.5\etc\netbeans.conf

and add this parameter –laf com.sun.java.swing.plaf.nimbus.NimbusLookAndFeel to netbeans_default_options section in netbeans.conf

It should look something like this;

netbeans_default_options=”-J-client -J-Xverify:none -J-Xss2m -J-Xms32m -J-XX:PermSize=32m -J-XX:MaxPermSize=200m -J-Dapple.laf.useScreenMenuBar=true -J-Dsun.java2d.noddraw=true –laf com.sun.java.swing.plaf.nimbus.NimbusLookAndFeel”

Also, Sridhar Reddy has released an introductory screencast, Introduction to NetBeans IDE 6.5,  here.

Download from here.

• Download 64-bit Adobe Flash Player for Linux (TAR.GZ, 3.54 MB)

To read the entire story:

http://labs.adobe.com/downloads/flashplayer10.html

Step 2.

yum install fuse fuse-ntfs-3g dkms dkms-fuse

Step 3.
Mount your ntfs volume. /dev/sdc5 is my ntfs partition.

mount -t ntfs-3g /dev/sdc5 /mnt/win_c

Enjoy!

Thanks to Ibrahim for this quick tip.

Step 1.
You need to have rpmforge-release package installed. You can download it from DAG (http://dag.wieers.com/rpm/packages/rpmforge-release/).

Step 2.

yum install ipw3945d ipw3945-firmware dkms dkms-ipw3945 wpa_supplicant

Step 3.

vi /etc/sysconfig/wpa_supplicant

It should look like this;

# wlan0 and wifi0
# INTERFACES=”-iwlan0 -iwifi0″
#INTERFACES=”-iwlan0″
INTERFACES=”-ieth1″
# ndiswrapper and prism
# DRIVERS=”-Dndiswrapper -Dprism”
#DRIVERS=”-Dndiswrapper”
DRIVERS=”-Dwext”
~

Step 4.
Edit wpa_supplicant.conf. On this example, there are two network configured and both of them are WPA-1

vi /etc/wpa_supplicant/wpa_supplicant.conf

ctrl_interface=/var/run/wpa_supplicant
#ctrl_interface_group=wheel
eapol_version=1
ap_scan=1
fast_reauth=1

#Work WPA-1
network={
ssid=”Fredi”
psk=”mysecretpassword” #Pre-shared key here
priority=1
}

#Home WPA-1
network={
ssid=”StarDust”
psk=”mysecretpassword” #Pre-shared key here
priority=2
}

Step 5.
Create your wireless interface configuration file.

vi /etc/sysconfig/network-scripts/ifcfg-eth1

DEVICE=eth1
BOOTPROTO=dhcp
HWADDR=00:00:00:00:00:00 # Your wireless adapters’s MACid
ONBOOT=no
~

Tip:

To learn your wireless adapter’s MACid:
start ipw3945d service with service ipw3945d start then use ifconfig -a

Step 6.
Start required services on boot;

chkconfig ipw3945d on
chkconfig wpa_supplicant on

Step 7.
You should modify the startup scripts to change the boot order that work with wpa_supplicant

vi /etc/init.d/ipw3945d
# chkconfig: 345 10 90

vi /etc/init.d/network
# chkconfig: 2345 13 87

vi /etc/init.d/wpa_supplicant
# chkconfig: - 14 88

To use the new boot order, first disable services then re-enable

To disable:

chkconfig network off
chkconfig ipw3945d off
chkconfig wpa_supplicant off

To enable the new boot order;

chkconfig network on
chkconfig ipw3945d on
chkconfig wpa_supplicant on

Step 8.
Also, disable NetworkManager and NetworkManagerDispatcher services

chkconfig NetworkManager off
chkconfig NetworkManagerDispatcher off

Step 9.
Install dhclient package.

yum install dhclient

Step 10.
Install wpa_gui package. It is an easy to use network configuration application.

yum install wpa_supplicant-gui

Step 11.
Run wpa_gui application and connect to the network.

wpa_gui &

Step 12.
Try to request an IP address from the network.

dhclient eth1

You should see your IP address on wpa_gui’s main window.

Tip: To scan wireless networks, use;

iwlist eth1 scan

Enjoy!

First of all, If you want to know what LVM is,  there are many documents on the internet. (e.g. http://tldp.org/HOWTO/LVM-HOWTO/)

In this example we will learn how to extend a Volume Group size.

Assume that, we have 30GB hard disk and partitioned as follows:

# fdisk /dev/sda

The number of cylinders for this disk is set to 3916.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/sda: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   83  Linux
/dev/sda2              14        2563    20482875   8e  Linux LVM

We have two partition;

/dev/sda1 is a non-LVM partition (Type: 0×83)
/dev/sda2 is a LVM partition (Type: 0×8e)

And we have some unpartitioned free space (3916 - 2563 = 1353 cylinders)

And this is our Volume Group Info:

# vgdisplay

— Volume group —
VG Name               VolGroup00
System ID
Format                lvm2
Metadata Areas        1
Metadata Sequence No  3
VG Access             read/write
VG Status             resizable
MAX LV                0
Cur LV                2
Open LV               2
Max PV                0
Cur PV                1
Act PV                1
VG Size               19.53 GB
PE Size               32.00 MB
Total PE              625
Alloc PE / Size       625 / 19.53 GB
Free  PE / Size       0 / 0
VG UUID               hx8M0U-TMkp-M0cB-eQpb-Avge-UddS-M0ZCc0

We allocated every PE.So, we don’t have any free PE. Our goal is to extend VolGroup00 with this unpartitioned free space.

1. Use fdisk and create a new partition and change the type of it to 8e.

# fdisk /dev/sda

The number of cylinders for this disk is set to 3916.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/sda: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   83  Linux
/dev/sda2              14        2563    20482875   8e  Linux LVM
/dev/sda3            2564        3916    10867972+  8e  Linux

Command (m for help): t
Partition number (1-3): 3
Hex code (type L to list codes): 8e

Command (m for help): p

Disk /dev/sda: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   83  Linux
/dev/sda2              14        2563    20482875   8e  Linux LVM
/dev/sda3            2564        3916    10867972+  8e  Linux LVM

Command (m for help): w

#

Your new partition table should looks like above.

2. Now, we should create a new PV to use this new partition. To do this use pvcreate command. (i.e. pvcreate /dev/sda3)

# pvcreate /dev/sda3

Physical volume “/dev/sda3″ successfully created

Okay, we have a new PV. Let’s look at it.

# pvdisplay

— Physical volume —
PV Name               /dev/sda2
VG Name               VolGroup00

PV Size               19.53 GB / not usable 2.81 MB
Allocatable           yes (but full)

PE Size (KByte)       32768
Total PE              625
Free PE               0
Allocated PE          625
PV UUID               vRmmoI-0cM9-AFRS-1ruI-1b7S-IKCn-gO35nl

“/dev/sda3″ is a new physical volume of “10.36 GB”
— NEW Physical volume —
PV Name               /dev/sda3
VG Name
PV Size               10.36 GB
Allocatable           NO
PE Size (KByte)       0
Total PE              0
Free PE               0
Allocated PE          0
PV UUID               EQ2sdZ-b2a3-OThW-8TE5-LyQS-SYg4-DOmykI

3. The final step we have to extend VolGroup00 with this new PV. To do this use pvextend command. (i.e. pvextend /dev/VolGroup00 /dev/sda3). You will see something like this;

# vgextend /dev/VolGroup00 /dev/sda3

Volume group “VolGroup00″ successfully extended

Let’s look at what we have.

# vgdisplay

— Volume group —
VG Name               VolGroup00
System ID
Format                lvm2
Metadata Areas        2
Metadata Sequence No  8
VG Access             read/write
VG Status             resizable
MAX LV                0
Cur LV                2
Open LV               2
Max PV                0
Cur PV                2
Act PV                2
VG Size               29.88 GB
PE Size               32.00 MB
Total PE              956
Alloc PE / Size       625 / 19.53 GB
Free  PE / Size       331 / 10.34 GB
VG UUID               hx8M0U-TMkp-M0cB-eQpb-Avge-UddS-M0ZCc0

We did it. We have 331 Free PE in VolGroup00.

That’s all. You see that using LVM is most comfortable way of volume management. But, be careful using lvm commands. Using incorrect parameter can make your files inaccessible.