Example output of decode-dimms:

# decode-dimms version 5733 (2009-06-09 13:13:41 +0200)

Memory Serial Presence Detect Decoder
By Philip Edelbrock, Christian Zuckschwerdt, Burkart Lingner,
Jean Delvare, Trent Piepho and others

Decoding EEPROM: /sys/bus/i2c/drivers/eeprom/0-0054
Guessing DIMM is in                             bank 5

—=== SPD EEPROM Information ===—
EEPROM Checksum of bytes 0-62                   OK (0x6F)
# of bytes written to SDRAM EEPROM              128
Total number of bytes in EEPROM                 256
Fundamental Memory type                         SDR SDRAM
SPD Revision                                    18

—=== Memory Characteristics ===—
Size                                            256 MB
tCL-tRCD-tRP-tRAS                               3-2-2-6
Number of Row Address Bits                      12
Number of Col Address Bits                      10
Number of Module Rows                           2
Data Width                                      64
Voltage Interface Level                         LVTTL (not 5V tolerant)
Module Configuration Type                       No Parity
Refresh Type                                    Self Refreshing
Refresh Rate                                    Normal (15.625 us)
Primary SDRAM Component Bank Config             No Bank2 OR Bank2 = Bank1 width
Primary SDRAM Component Widths                  8
Error Checking SDRAM Component Bank Config      No Bank2 OR Bank2 = Bank1 width
Error Checking SDRAM Component Widths           Undefined!
Min Clock Delay for Back to Back Random Access  1
Supported Burst Lengths                         1, 2, 4, 8, Page
Number of Device Banks                          4
Supported CAS Latencies                         3T, 2T
Supported CS Latencies                          0
Supported WE Latencies                          0
Cycle Time                                      7.5 ns at CAS 3
7.5 ns ns at CAS 2
Access Time                                     5.4 ns at CAS 3
5.4 ns ns at CAS 2
SDRAM Module Attributes                         (None Reported)
SDRAM Device Attributes (General)               Supports Auto-Precharge
Supports Precharge All
Supports Write1/Read Burst
Lower VCC Tolerance: 10%
Upper VCC Tolerance: 10%
Minimum Row Precharge Time                      15 ns
Row Active to Row Active Min                    15 ns
RAS to CAS Delay                                15 ns
Min RAS Pulse Width                             45 ns
Row Densities                                   128 MByte
Command and Address Signal Setup Time           1.5 ns
Command and Address Signal Hold Time            0.8 ns
Data Signal Setup Time                          1.5 ns
Data Signal Hold Time                           0.8 ns

—=== Manufacturing Information ===—
Manufacturer                                    Hyundai Electronics
Manufacturing Location Code                     0×02
Part Number                                     71V32635HCT8P-K
Revision Code                                   0×4141
Manufacturing Date                              2009-W67
Assembly Serial Number                          0x80E1211B

—=== Intel Specification ===—
Frequency                                       100MHz or 133MHz
Details for 100MHz Support                      Intel Concurrent Auto-precharge
CAS Latency = 2
CAS Latency = 3
Junction Temp A (100 degrees C)
CLK 3 Connected
CLK 2 Connected
CLK 1 Connected
CLK 0 Connected
Double-sided DIMM

Decoding EEPROM: /sys/bus/i2c/drivers/eeprom/0-0055
Guessing DIMM is in                             bank 6

—=== SPD EEPROM Information ===—
EEPROM Checksum of bytes 0-62                   OK (0x9F)
# of bytes written to SDRAM EEPROM              128
Total number of bytes in EEPROM                 256
Fundamental Memory type                         SDR SDRAM
SPD Revision                                    18

—=== Memory Characteristics ===—
Size                                            128 MB
tCL-tRCD-tRP-tRAS                               3-3-3-6
Number of Row Address Bits                      12
Number of Col Address Bits                      9
Number of Module Rows                           2
Data Width                                      64
Voltage Interface Level                         LVTTL (not 5V tolerant)
Module Configuration Type                       No Parity
Refresh Type                                    Self Refreshing
Refresh Rate                                    Normal (15.625 us)
Primary SDRAM Component Bank Config             No Bank2 OR Bank2 = Bank1 width
Primary SDRAM Component Widths                  8
Error Checking SDRAM Component Bank Config      No Bank2 OR Bank2 = Bank1 width
Error Checking SDRAM Component Widths           Undefined!
Min Clock Delay for Back to Back Random Access  1
Supported Burst Lengths                         1, 2, 4, 8, Page
Number of Device Banks                          4
Supported CAS Latencies                         3T, 2T
Supported CS Latencies                          0
Supported WE Latencies                          0
Cycle Time                                      7.5 ns at CAS 3
10 ns ns at CAS 2
Access Time                                     5.4 ns at CAS 3
6 ns ns at CAS 2
SDRAM Module Attributes                         (None Reported)
SDRAM Device Attributes (General)               Supports Auto-Precharge
Supports Precharge All
Supports Write1/Read Burst
Lower VCC Tolerance: 10%
Upper VCC Tolerance: 10%
Minimum Row Precharge Time                      20 ns
Row Active to Row Active Min                    15 ns
RAS to CAS Delay                                20 ns
Min RAS Pulse Width                             45 ns
Row Densities                                   64 MByte
Command and Address Signal Setup Time           1.5 ns
Command and Address Signal Hold Time            0.8 ns
Data Signal Setup Time                          1.5 ns
Data Signal Hold Time                           0.8 ns

—=== Manufacturing Information ===—
Manufacturer                                    Hyundai Electronics
Manufacturing Location Code                     0×01
Part Number                                     7V631601BTFG-75
Revision Code                                   0×4241
Manufacturing Date                              2052-W00
Assembly Serial Number                          0xA202C14B

—=== Intel Specification ===—
Frequency                                       100MHz or 133MHz
Details for 100MHz Support                      Intel Concurrent Auto-precharge
CAS Latency = 2
CAS Latency = 3
Junction Temp B (90 degrees C)
CLK 3 Connected
CLK 2 Connected
CLK 1 Connected
CLK 0 Connected
Double-sided DIMM

Decoding EEPROM: /sys/bus/i2c/drivers/eeprom/0-0056
Guessing DIMM is in                             bank 7

—=== SPD EEPROM Information ===—
EEPROM Checksum of bytes 0-62                   OK (0xE1)
# of bytes written to SDRAM EEPROM              128
Total number of bytes in EEPROM                 256
Fundamental Memory type                         SDR SDRAM
SPD Revision                                    18

—=== Memory Characteristics ===—
Size                                            128 MB
tCL-tRCD-tRP-tRAS                               3-2-2-5
Number of Row Address Bits                      12
Number of Col Address Bits                      9
Number of Module Rows                           2
Data Width                                      64
Voltage Interface Level                         LVTTL (not 5V tolerant)
Module Configuration Type                       No Parity
Refresh Type                                    Self Refreshing
Refresh Rate                                    Normal (15.625 us)
Primary SDRAM Component Bank Config             No Bank2 OR Bank2 = Bank1 width
Primary SDRAM Component Widths                  8
Error Checking SDRAM Component Bank Config      No Bank2 OR Bank2 = Bank1 width
Error Checking SDRAM Component Widths           Undefined!
Min Clock Delay for Back to Back Random Access  1
Supported Burst Lengths                         1, 2, 4, 8, Page
Number of Device Banks                          4
Supported CAS Latencies                         3T, 2T
Supported CS Latencies                          0
Supported WE Latencies                          0
Cycle Time                                      10 ns at CAS 3
10 ns ns at CAS 2
Access Time                                     6 ns at CAS 3
6 ns ns at CAS 2
SDRAM Module Attributes                         (None Reported)
SDRAM Device Attributes (General)               Supports Auto-Precharge
Supports Precharge All
Supports Write1/Read Burst
Lower VCC Tolerance: 10%
Upper VCC Tolerance: 10%
Minimum Row Precharge Time                      20 ns
Row Active to Row Active Min                    16 ns
RAS to CAS Delay                                20 ns
Min RAS Pulse Width                             45 ns
Row Densities                                   64 MByte
Command and Address Signal Setup Time           2 ns
Command and Address Signal Hold Time            1 ns
Data Signal Setup Time                          2 ns
Data Signal Hold Time                           1 ns

—=== Manufacturing Information ===—
Manufacturer                                    Infineon (former Siemens)
Custom Manufacturer Data                        49 4E 46 49 4E 45 4F (“INFINEO”)
Manufacturing Location Code                     0×08
Part Number                                     HYS64V16220GU-8
Revision Code                                   0×0102
Manufacturing Date                              2000-W14
Assembly Serial Number                          0x0102BE2E

—=== Intel Specification ===—
Frequency                                       100MHz or 133MHz
Details for 100MHz Support                      Intel Concurrent Auto-precharge
CAS Latency = 2
CAS Latency = 3
Junction Temp A (100 degrees C)
CLK 3 Connected
CLK 2 Connected
CLK 1 Connected
CLK 0 Connected
Double-sided DIMM

Number of SDRAM DIMMs detected and decoded: 3

console=tty0 console=ttyS0,115200n8

to kernel’s boot parameters (e.g. kernel /boot/vmlinuz-2.6.37-slitaz-serial root=/dev/sda1 panic=60 lang=de_DE console=tty0 console=ttyS0,115200n8) in /boot/grub/menu.lst (legacy grub) If you’d like to see grub’s output on serial console add

serial –unit=0 –speed=115200 –word=8 –parity=no –stop=1 terminal –timeout=10 serial console

to /boot/grub/menu.lst (legacy grub). It’s a good choice to enable a getty listening on the serial line after the kernel has booted yo you schould add the line

ttyS0::respawn:/sbin/getty -L 115200 ttyS0 vt102

to /etc/inittab

My main idea was to integrate the door phone into my exisiting SIP (VOIP) environment which is reachable by WiFi (WLAN). There exist door phones with so called a/b interfaces that can be connected like any other phone to a PBX (private branch exchange, =telephone system).
Based on this I thought it should be possible to connect the door phone to an ATA (analog telephone adapter) that connects to the SIP server via WiFi connection.

Unfortunately these adapters are very expensive so I looked around for an alternative solution and finally found one: BCM96348GW based ADSL-Router (sold as Targa WR500 VOIP and the Speedport Deutsche Telekom W500V) can be used as ATAs by installing an alternative firmware. With a little patience I got one on ebay for 1€.
After installing the new firmware I put it into the arbor next to the gate (of course you need power jack at the place you’d like to install the door phone and the ATA to get the whole installation working!)

Now you can ring my door and I could answer even if I’m far away since I am connected with my mobile to the PBX via 3G.

…but as I said this was not my main attention but not to rip the court.

• Kernel
• udhcp default script

Kernel

Recompile the kernel (as described here):

• call “tazpkg get-install linux-source”, this will install get-linux-source and all the kernel patches
• call “tazpkg get-install slitaz-toolchain”, this will install the binaries needed for compiling kernels
• call “tazpkg get-install ncurses-dev”, this will install ncurses files needed for the make target “menuconfig”
• call “tazpkg get-install perl”, needed by kernel malefiles
• call “get-linux-source”, this will download the kernel sources and patch them
• cd into /usr/src/linux-$(version)
• call “make menuconfig”
• activate “IP: kernel level autoconfiguration” (CONFIG_IP_PNP)
• activate “IP: DHCP support” (CONFIG_IP_PNP_DHCP)
• activate “Root file system on NFS” (CONFIG_ROOT_NFS)
• call “make bzImage”
• copy the resulting kernel (arch/x86/boot/bzImage) beside the exisiting kernel and add it to grub’s menu.lst or copy it over the existing kernel (not prefered since it would be overwritten when doing a kernel package update).

Patch /usr/share/udhcpc/default.script

Since udhcp would pull down the exisiting ethernet connection on the device used for the NFS mount we have to check for the NFS mount. The format defininition of the /proc/mounts changed in lately kernels so there are two possible regexps, the version active works on SliTaz cooking. I’m not sure on which kernel version the format did change.

Please patch the included /usr/share/udhcpc/default.script using the patch attached

@@ -9,9 +9,19 @@
[ -n "$broadcast" ] && BROADCAST=”broadcast $broadcast”
[ -n "$subnet" ] && NETMASK=”netmask $subnet”

+# return 0 if root is mounted on a network filesystem
+root_is_nfs() {
+        ## old style
+        # grep -qe ‘^/dev/root.*\(nfs\|smbfs\|ncp\|coda\) .*’ /proc/mounts
+        ## new style
+        grep -qe ‘^.*:.* / \(nfs\|smbfs\|ncp\|coda\) .*’ /proc/mounts
+}
+
case “$1″ in
deconfig)
-               /sbin/ifconfig $interface 0.0.0.0
+               if ! root_is_nfs ; then
+                       /sbin/ifconfig $interface 0.0.0.0
+               fi
for i in /etc/ipdown.d/*; do
[ -x $i ] && $i $interface
done
@@ -22,9 +32,11 @@

if [ -n "$router" ] ; then
echo “deleting routers”
-                       while route del default gw 0.0.0.0 dev $interface ; do
-                               :
-                       done
+                       if ! root_is_nfs ; then
+                               while route del default gw 0.0.0.0 dev $interface ; do
+                                       :
+                               done
+                       fi

metric=0
for i in $router ; do

Boot and have fun!

This should be possible using not an ISO (loop/cloop) based filesystem but also an ext2/3/4 filesystem. A short google search showed me http://wiki.ubuntuusers.de/Nur-Lesen_Root-Dateisystem_mit_aufs which is exactly the solution I was looking for. I only had to adopt it on SliTaz.

The Slitaz way is more complicated since I don’t know of a SliTaz package that offers initrd creation functionality so you have to do this all by your own, please follow these  instructions:

• extract an exisiting initrd (use the one that comes with any SliTaz ISO)  “cat rootfs.gz | lzma -d -c | cpio -i”
• install aufs kernel module (tazpkg install linux-aufs)
• remove all module branches from the initrd (rm -rf lib/modules/*)
• copy all kernel modules of the running kernel to it (cp -ax /lib/modules`uname -r` lib/modules)
• copy the attached init (see below) into initrd
• make it executable (chmod 0755 init)
• repack it (find . -print | cpio -o -H newc | lzma -c –best >../aufsrootfs.gz)
• modify the bootloader by passing the initrd and adding aufs=tmpfs to the kernel parameters

Init comes with two scripts that allows you to remount the underlying root partition rw. So you’re able to change the content of the filesystem (e.g. for running updates) but beware: If you’ll upgrade the kernel you have to repack the initrd!

Have fun!

This is the init you have to use instead of the existing one:

#! /bin/sh

export aufs

mount -t proc proc /proc
mount -t sysfs sysfs /sys

for x in $(cat /proc/cmdline); do
case $x in
root=*)
ROOTNAME=${x#root=}
;;
aufs=*)
aufs=${x#aufs=}
case $aufs in
tmpfs-debug)
aufs=tmpfs
aufsdebug=1
;;
esac
;;
esac
done

echo
echo “root-aufs: Setting up aufs on ${ROOTNAME} as root file system “
echo

modprobe -q aufs || insmod /lib/modules/`uname -r`/kernel/fs/aufs/aufs.ko.gz
if [ $? -ne 0 ]; then
echo    root-aufs error: Failed to load aufs module
exit 0
fi

#make the mount points on the init root file system
mkdir /aufs
mkdir /rw
mkdir /ro

# mount the temp file system and move real root out of the way
mount -t tmpfs aufs-tmpfs /rw
mount ${ROOTNAME} /ro
if [ $? -ne 0 ]; then
echo “root-aufs error: ${ROOTNAME}  failed to move to /ro”
exit 0
fi

mount -t aufs -o dirs=/rw:/ro=ro aufs /aufs
if [ $? -ne 0 ]; then
echo    root-aufs error:      Failed to mount /aufs files system
exit 0
fi

#test for mount points on aufs file system
[  -d /aufs/ro ] || mkdir /aufs/ro
[  -d /aufs/rw ] || mkdir /aufs/rw

# the real root file system is hidden on /ro of the init file system.  move it to /ro
mount -omove /ro /aufs/ro
if [ $? -ne 0 ]; then
echo    root-aufs error:      Failed to move /ro /aufs/ro
exit 0
fi

# tmpfs file system is hidden on /rw
mount -omove /rw /aufs/rw
if [ $? -ne 0 ]; then
echo    root-aufs error:      Failed to move /rw /aufs/rw
exit 0
fi

#Add the comment block to fstab
cat <<EOF >/aufs/etc/fstab
#
#  $0 has mounted the root file system in ram
#
#  This fstab is in ram and the real fstab can be found /ro/etc/fstab
#  The root file system ‘ / ‘ has been removed.
EOF

#remove root from fstab
cat /aufs/ro/etc/fstab|grep -v ‘ / ‘ >>/aufs/etc/fstab

# add the read only file system to fstab
#ROOTTYPE=$(cat /proc/mounts|grep ${ROOT}|cut -d’ ‘ -f3)
#ROOTOPTIONS=$(cat /proc/mounts|grep ${ROOT}|cut -d’ ‘ -f4)
#echo ${ROOT} /ro $ROOTTYPE $ROOTOPTIONS 0 0 >>/aufs/etc/fstab

# S22mount on debian systems is not mounting  /ro correctly after boot
# add to rc.local to correct what you see from df
#replace last case of exit with #exit
#cat /aufs/ro/etc/rc.local|sed ‘s/\(.*\)exit/\1\#exit/’ >/aufs/etc/rc.local
#echo mount -f  /ro >>/aufs/etc/rc.local

# add back the root file system. mtab seems to be created by one of the init proceses.
#echo “echo aufs / aufs rw,xino=/rw/.aufs.xino,br:/rw=rw:/ro=ro 0 0 >>/etc/mtab” >>/aufs/etc/rc.local
#echo “echo aufs-tmpfs /rw tmpfs rw 0 0 >>/etc/mtab” >>/aufs/etc/rc.local
#echo exit 0 >>/aufs/etc/rc.local

#fix permissions
chmod 755 /aufs

#build remountrw
echo \#!/bin/sh >/aufs/bin/remountrw
echo mount -o remount,rw ${ROOT} >>/aufs/usr/bin/remountrw
chmod 0700 /aufs/bin/remountrw

#build remountro
echo \#!/bin/sh >/aufs/bin/remountro
echo mount -o remount,ro ${ROOT} >>/aufs/usr/bin/remountro
chmod 0700 /aufs/bin/remountro

umount /sys
umount /proc

# remount ro
mount -oremount,ro /aufs

echo -e “\33[70G[ \33[1;33mOK\33[0;39m ]“
exec /sbin/switch_root /aufs /sbin/init

For reference, this is my grub menu.lst with the old (normal boot) and the new (aufs read only boot) entry:

[...]

title SliTaz GNU/Linux (Kernel 2.6.37-slitaz)
root (hd0,0)
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/hda1

title SliTaz GNU/Linux (Kernel 2.6.37-slitaz) (AUFS)
root (hd0,0)
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/hda1 aufs=tmpfs
initrd /boot/aufsrootfs.gz

-It’s not part of your business logic but a kind of optimization

-The code becomes less readable

-When you change the loglevel you also have to change the isXXXEnabled call (error prune)

-…and at least: This is a very boring job

Boring job!? Why don’t let some optimizer do this work for us!? And here comes http://sourceforge.net/projects/just4log/files/

This project comes with and AntTask adding the “missing” statements for us:

a();

logger.debug(“Got ” + input + “, will return ” + output);

b();

becomes

a();

if (logger.isDebugEnabled())

logger.debug(“Got ” + input + “, will return ” + output);

b();

Didn’t I say the isXXXEnabled statements are not needed? No! I didn’t! They are very very useful. I just said that they shouldn’t be written by the programmer itself.

Oh! The project is dead since 6 years, see forum (http://sourceforge.net/projects/just4log/forums/forum/288112/topic/1354439)

Because of that and that the project did not support SLF4J (Simple Logging Fascade for Java) I decided to relaunch the whole project: Tataaaaa, here it is: http://sourceforge.net/projects/just4log-ng/

You might say: “Hey! You don’t have to check the loglevel using SLF4J!”. Unfortunately this is not the truth:

Of couse you can use the parameterized messages SLF4J is supporting

logger.debug(“The new entry is {}.”, entry);

but if you’d like to log more than two arguments you have to use the vararg method which will create an Object[] holding your parameters (this is done automatically by the compiler). Another thing is autoboxing of primitive values:

int a=5, b=7, c=a+b;

logger.debug(“Sum of {} and {} is {}.”, sum, a, b);

What will happen here? The compiler will transform this under the hood into:

logger.debug(“Sum of {} and {} is {}.”, new Object[] { Integer.valueOf(sum), Integer.valueOf(a), Integer.valueOf(b) });

So there are 4 objects created you won’t see in your source code (3 Integers and one Object[])

Let me repeat myself:  The code should be wrapped by isXXXEnabled to prevent the Object[] creation.

I recommited the code found in the old repository and did a lot of optimizations (general rework, Java5 migration, command line support, fixed some bugs)

This is a common mistake! If you have concurrent modifying access to collections you have either to synchronize all methods accessing the collection or to use a collection which is designed for this purpose (see java.util.concurrent or Collections.synchronized… if you are using a JDK version < 5).

A small example to illustrate this:

import java.util.HashMap;
import java.util.Map;
import java.util.Random;

public class StandardCollectionsAreNOTThreadSafe {

@SuppressWarnings(“nls”)
public static void main(String[] args) {
final Random random = new Random(System.currentTimeMillis());
final Map<String, Integer> m = new HashMap<String, Integer>();
Integer expected = Integer.valueOf(4711);
m.put(“foo”, expected);
new Thread() {
@Override
public void run() {
for (;;) {
int nextInt = random.nextInt();
m.put(String.valueOf(nextInt), Integer.valueOf(nextInt));
}

}
}.start();

for (;;) {
Integer actual = m.get(“foo”);
if (actual != expected) {
throw new RuntimeException(“Got ” + actual + ” (map size is ” + m.size() + “)”);
}

}
}

}

The code puts the value 4711 for key “foo” and continously retrieves the value for key “foo” from the Map while another thread puts dummy data to it. If the value retrieved from the map is not 4711 the method will throw an Exception.

Copy & compile this code if you are sure that java’s standard collections (like HashMap/ArrayList/…) are thread-safe.

But what you can see very often is that the close-call is surrounded by a catch block catching IOExceptions and irgnoring them, e.g.

OutputStream os = …
try {
while (…) {
os.write(…);
}
} finally {
try {
os.close();
} catch (IOException e) { /* ignore it */  }

}

What’s wrong with that code?

When getting the Outputstream/Writer as argument (or even explicitly intantiating your own) you have most of the time a BufferedOutputStream/BufferedWriter. These classes write the data to the underlying Stream/Writer if their buffers are filled or flush() or close() is called on them.

That means that the remaining data in the buffer would be written when calling flush()/close().

So in the example above you’d have a corrupted file wothout noticing it.

So what’s the solution? You should never catch and ignore IOExceptions when writing to resources because they indicate that your file does not contain all the data you intended to write to it.

The resulting code will be 10 times better than code using Apache Commons CLI (never use Findbugs/PMD or any other static software analyse tool on Commons CLI and never, really never take a look at the sources! :-/).

Example code and description can be found here. http://weblogs.java.net/blog/kohsuke/archive/2005/05/parsing_command.html

Arg4J takes full use of and supports  Java5 language features (annotations and enums)

public final class Main {

public static void main(String[] args) throws  CmdLineException {
new Main().doMain(args);
}

@Option(name = “-h”, aliases = { “-help” }, usage = “print this message”)
private boolean help = false;

@Option(name = “-i”, required = true, usage = “input from this file”, metaVar = “/path/to/your.class”)
private File in = new File(“.”);

@Option(name = “-o”, required = true, usage = “output to this dir”, metaVar = “/tmp/bin”)
private File out = new File(“.”);

[...]

Parsing is done easily by invoking the Parser:

private void doMain(String[] args) throws CmdLineException {
CmdLineParser parser = new CmdLineParser(this);
parser.setUsageWidth(130);
try {
parser.parseArgument(args);
} catch (CmdLineException e) {
System.err.println(e.getMessage());
showHelpAndExit(parser);
}

/**
* Returns a new Date that is <code>workingDays</code> working days in the
* future based on <code>start</code>.
*
* @param start the base date
* @param workingDays count of working days
* @return newly created Date that is <code>workingDays</code> working days
*         in the future based on <code>start</code>
*/
public static Date addWorkingDays(Date start, int workingDays) {
Calendar cal = Calendar.getInstance();
cal.setTime(start);
int base = workingDays + (cal.get(Calendar.DAY_OF_WEEK) – cal.get(Calendar.DAY_OF_MONTH) + 32) % 7;
cal.add(Calendar.DAY_OF_MONTH, base – 7 + (base + 4) / 5 * 2);
return cal.getTime();
}