
Novell Inc offering the fress stuff when their launching the SuSe Linux Enterprise 11.
From: Novell
Hey, we’ve got a little budget, and we like to have fun (all work, no play makes [your name here] a dull….yada, yada….) and we’re excited about the SLE 11 launch so we’re hoping you will play along. We’ll make it worth your time and effort by giving you a GOOD chance to get a T-Shirt, and at least a chance of getting something better. We’ve come up a couple of fun activities we’re hoping you’ll participate in if you get the chance. Get started with these and stay tuned for more:
SUSE Linux Enterprise 11 Geocaching
What do you do with Linux? (Create a Video)

Did you all here this before about this company koenig-solutions
This company are base in India. It provide a lot of training/certification. The best this is.. if you dont have the place to stay when doing the training.. they can provided it.. It include in the training/cert price… Most of the training is boot camp ,RHCE, NCLE, Solaris, CCNA, CCNP, MCSE, LP1,LP12, to many…
Here i provided same example of the training including the price and accomondation.
Source: koenig-solutions
CLP/CLE
Contact:
Delhi Centre
Koenig Solutions Pvt. Ltd.
20-A, IInd Floor, Shivaji Marg, Moti Nagar
New Delhi, Postal Code – 110015, (India)
Shimla (Himalaya Mountains) Centre
Koenig Solutions Pvt. Ltd.
Sunbreeze Inn building
Main Bus Stand
Sanjauli, Shimla-171006.
Himachal Pradesh (India)
Goa Centre
Koenig Solutions Pvt. Ltd.
3rd Floor, B/T1,
Campal Trade Centre,
Opp. Kala Akademy,
Panjim, Goa – 403001, (India)
Dehradun Centre
Koenig Solutions Pvt Ltd,
Plot # 22, IT Park,
Sahashdhara Road,
Dehradun, (India)
Fax: +91 11 25886909
Email: info@koenig-solutions.com
Telephone 24 x 7 : +91 98102 64199
(only from outside India)

For those who are using the SLES.. i got the mail from Novell.. Currently got the 10 patch available now.. but i only for the OS that registed with Novell only
— On Sat, 20/12/08, Novell Patchbuilder Notification <patchbuilder_noreply@novell.com> wrote:
From: Novell Patchbuilder Notification <patchbuilder_noreply@novell.com>
Subject: 19 Dec 2008 Novell Customer Center (10 New Patches)
To: “XXXXXXXXXXXXXXXXXXXX” <hackers_125@yahoo.com>
Date: Saturday, 20 December, 2008, 7:00 AM
19 Dec 2008 Novell Customer Center (10 New Patches)
|
|
 |
Patch Updates
19 Dec 2008
The latest updates to your SUSE Linux Enterprise software are now available. By installing updates regularly, you will keep your operating system at peak performance, remove known security vulnerabilities and software defects, improve stability, and add the newest features and functionality.
To download, simply click the URL(s) that correspond to your version and log in to the Novell download site. You can then install the updates with YaST or your preferred installation tool. Please note: You must have a registered SUSE Linux Enterprise product with upgrade protection in order to access the patch downloads.
Technorati Profile

OMG.. this Sunday i will start working on Shift.. after my validation today..8am to 8pm…On friday is my NCLP exam.. oh.. my head full of UNIX Command now..how about SLES… hahaha…dont mix it up..dont close the YAST… use the rcxxxx …xxxx is service…dont forget about the syslog.ng… troubleshoot the user permission access.
My last project at Intel already success DQ45CB, DQ45CB SYSTEM & DG41Ty
This is my First SLED/SLES Project at Intel DG35EC

Ah damm.. yesterday i make the phone call to the NCLP exam centre @ CSA to postpone my exam coz i think i unable to take the exam on that date. My time to tight.. how to sit the exam.. i need to rushing… then need to take my offer later… then going back at late night…and next day need to work again… damm… I’m have give 150% preparation for this exam. I’m ready to take it..but i need time.. i think no need to rush to get this exam ASAP.. because i got the new job at KL. so its easy to me to schedule the exam and sit the exam.
From: practicum@novell.com
Subject: Scheduled Exam: Certified Linux Professional 10
To: XXXXXXXXX@yahoo.com
Date: Wednesday, October 22, 2008, 3:55 PM
This eMail has been sent to confirm your scheduled date to take the followingexam:
Certified Linux Professional 10
SCHEDULED FOR: Friday, November 28th at 10:30 AMTO BE TAKEN AT: Computer Systems Advisers Malaysia Berhad - Petaling Jaya
Point your web-browser to http://practicum.novell.com and read the FAQ (underthe "main menu") for more information on login access to your exam.
***************************************************************KHAIRUL ADI JOHARI TAJUL ALINovell Candidate ID: XXXXXXXXXeMail: XXXXXXXXX@yahoo.com

Yes i already confirmed to sit the exam .. 10.30 am GMT 08:00
Wish me luck on this exam
.

da1:~ # fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 1959 15735636 83 Linux
/dev/sda2 1960 2482 4200997+ 82 Linux swap / Solaris
/dev/sda3 2483 2495 104422+ 83 Linux
/dev/sda4 2496 19457 136247265 5 Extended
/dev/sda5 2496 2508 104391 8e Linux LVM
/dev/sda6 2509 2521 104391 8e Linux LVM
/dev/sda7 2522 2534 104391 8e Linux LVM
/dev/sda8 2535 2547 104391 fd Linux raid autodetect
/dev/sda9 2548 2560 104391 fd Linux raid autodetect
/dev/sda10 2561 2573 104391 fd Linux raid autodetect
/dev/sda11 2574 2586 104391 83 Linux
da1:~ # clear
da1:~ # mdadm –hlp
mdadm: unrecognized option `–hlp’
Usage: mdadm –help
for help
da1:~ # mdadm –help
mdadm is used for building, managing, and monitoring
Linux md devices (aka RAID arrays)
Usage: mdadm –create device options…
Create a new array from unused devices.
mdadm –assemble device options…
Assemble a previously created array.
mdadm –build device options…
Create or assemble an array without metadata.
mdadm –manage device options…
make changes to an existing array.
mdadm –misc options… devices
report on or modify various md related devices.
mdadm –grow options device
resize/reshape an active array
mdadm –incremental device
add a device to an array as appropriate
mdadm –monitor options…
Monitor one or more array for significant changes.
mdadm device options…
Shorthand for –manage.
Any parameter that does not start with ‘-’ is treated as a device name
or, for –examine-bitmap, a file name.
The first such name is often the name of an md device. Subsequent
names are often names of component devices.
For detailed help on the above major modes use –help after the mode
e.g.
mdadm –assemble –help
For general help on options use
mdadm –help-options
da1:~ # mdadm –create /dev/md0 –level=1 –raid-devices=2 /dev/sda8 /dev/sda9
mdadm: array /dev/md0 started.
da1:~ # array /dev/md
md0 md11 md14 md17 md2 md22 md25 md28 md30 md5 md8
md1 md12 md15 md18 md20 md23 md26 md29 md31 md6 md9
md10 md13 md16 md19 md21 md24 md27 md3 md4 md7
da1:~ # more /proc/partitions
major minor #blocks name
8 0 156290904 sda
8 1 15735636 sda1
8 2 4200997 sda2
8 3 104422 sda3
8 4 1 sda4
8 5 104391 sda5
8 6 104391 sda6
8 7 104391 sda7
8 8 104391 sda8
8 9 104391 sda9
8 10 104391 sda10
8 11 104391 sda11
9 0 104320 md0
da1:~ # mdadm –misc–query /dev/md0
mdadm: unrecognized option `–misc–query’
Usage: mdadm –help
for help
da1:~ # mdadm –misc –query /dev/md0
/dev/md0: 101.88MiB raid1 2 devices, 0 spares. Use mdadm –detail for more detai l.
da1:~ # mdadm –misc –details /dev/md0
mdadm: unrecognized option `–details’
Usage: mdadm –help
for help
da1:~ # mdadm –misc –detail /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Tue Aug 5 13:57:12 2008
Raid Level : raid1
Array Size : 104320 (101.89 MiB 106.82 MB)
Used Dev Size : 104320 (101.89 MiB 106.82 MB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Tue Aug 5 13:57:15 2008
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : 10d82e2a:61ed1aa3:59a6c3d9:358f3540
Events : 0.2
Number Major Minor RaidDevice State
0 8 8 0 active sync /dev/sda8
1 8 9 1 active sync /dev/sda9
da1:~ # more /proc/partitions
major minor #blocks name
8 0 156290904 sda
8 1 15735636 sda1
8 2 4200997 sda2
8 3 104422 sda3
8 4 1 sda4
8 5 104391 sda5
8 6 104391 sda6
8 7 104391 sda7
8 8 104391 sda8
8 9 104391 sda9
8 10 104391 sda10
8 11 104391 sda11
9 0 104320 md0
da1:~ # mdadm –manage /dev/md0 –fail /dev/sda8
mdadm: set /dev/sda8 faulty in /dev/md0
da1:~ # mdadm –misc –query /dev/md0
/dev/md0: 101.88MiB raid1 2 devices, 0 spares. Use mdadm –detail for more detai l.
da1:~ # mdadm –misc –detail /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Tue Aug 5 13:57:12 2008
Raid Level : raid1
Array Size : 104320 (101.89 MiB 106.82 MB)
Used Dev Size : 104320 (101.89 MiB 106.82 MB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Tue Aug 5 14:00:22 2008
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 1
Spare Devices : 0
UUID : 10d82e2a:61ed1aa3:59a6c3d9:358f3540
Events : 0.3
Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 9 1 active sync /dev/sda9
2 8 8 – faulty spare /dev/sda8
da1:~ # mdadm –manage /dev/md0 –fail /dev/sda9
mdadm: set /dev/sda9 faulty in /dev/md0
da1:~ # mdadm –manage /dev/md0 –remove /dev/sda8
mdadm: hot removed /dev/sda8
da1:~ # mdadm –misc –detail /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Tue Aug 5 13:57:12 2008
Raid Level : raid1
Array Size : 104320 (101.89 MiB 106.82 MB)
Used Dev Size : 104320 (101.89 MiB 106.82 MB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Tue Aug 5 14:03:07 2008
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : 10d82e2a:61ed1aa3:59a6c3d9:358f3540
Events : 0.4
Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 9 1 active sync /dev/sda9
da1:~ # mdadm –manage /dev/md0 –remove /dev/sda9
mdadm: hot remove failed for /dev/sda9: Device or resource busy
da1:~ # mdadm –stop /dev/md0
mdadm: stopped /dev/md0
da1:~ # more /proc/partitions
major minor #blocks name
8 0 156290904 sda
8 1 15735636 sda1
8 2 4200997 sda2
8 3 104422 sda3
8 4 1 sda4
8 5 104391 sda5
8 6 104391 sda6
8 7 104391 sda7
8 8 104391 sda8
8 9 104391 sda9
8 10 104391 sda10
8 11 104391 sda11
da1:~ # mdadm –create /dev/md1 –level=5 –raid-devices=3 /d
ev/sda8 /dev/sda9 / dev/sda10 –spare-devices=1 /dev/sda11
mdadm: /dev/sda8 appears to be part of a raid array:
level=raid1 devices=2 ctime=Tue Aug 5 13:57:12 2008
mdadm: /dev/sda9 appears to be part of a raid array:
level=raid1 devices=2 ctime=Tue Aug 5 13:57:12 2008
Continue creating array? y
mdadm: array /dev/md1 started.
da1:~ # mdadm –misc –detail /dev/md1 /dev/md1:
Version : 00.90.03
Creation Time : Tue Aug 5 14:07:37 2008
Raid Level : raid5
Array Size : 208640 (203.78 MiB 213.65 MB)
Used Dev Size : 104320 (101.89 MiB 106.82 MB)
Raid Devices : 3
Total Devices : 4
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Tue Aug 5 14:07:44 2008
State : clean
Active Devices : 3
Working Devices : 4
Failed Devices : 0
Spare Devices : 1
Layout : left-symmetric
Chunk Size : 64K
UUID : ec1fadec:c6148148:b00cbf42:a733e2d8
Events : 0.2
Number Major Minor RaidDevice State
0 8 8 0 active sync /dev/sda8
1 8 9 1 active sync /dev/sda9
2 8 10 2 active sync /dev/sda10
3 8 11 – spare /dev/sda11
da1:~ # mdadm –manage /dev/md0 –fail /dev/sda10 mdadm: cannot get array info for /dev/md0
da1:~ # mdadm –manage /dev/md1 –fail /dev/sda10
mdadm: set /dev/sda10 faulty in /dev/md1
da1:~ # mdadm –misc –detail /dev/md1
/dev/md1:
Version : 00.90.03
Creation Time : Tue Aug 5 14:07:37 2008
Raid Level : raid5
Array Size : 208640 (203.78 MiB 213.65 MB)
Used Dev Size : 104320 (101.89 MiB 106.82 MB)
Raid Devices : 3
Total Devices : 4
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Tue Aug 5 14:09:00 2008
State : clean, degraded, recovering
Active Devices : 2
Working Devices : 3
Failed Devices : 1
Spare Devices : 1
Layout : left-symmetric
Chunk Size : 64K
Rebuild Status : 74% complete
UUID : ec1fadec:c6148148:b00cbf42:a733e2d8
Events : 0.3
Number Major Minor RaidDevice State
0 8 8 0 active sync /dev/sda8
1 8 9 1 active sync /dev/sda9
4 8 11 2 spare rebuilding /dev/sda11
3 8 10 – faulty spare /dev/sda10
da1:~ # mdadm –manage /dev/md1 –add /dev/sda
sda sda10 sda2 sda4 sda6 sda8
sda1 sda11 sda3 sda5 sda7 sda9
da1:~ # mdadm –manage /dev/md1 –add /dev/sda
mdadm: Cannot open /dev/sda: Device or resource busy
da1:~ # clear
da1:~ # cd /etc/
da1:/etc # ll mdadm.conf
/bin/ls: mdadm.conf: No such file or directory
da1:/etc # echo ‘DEVICE /dev/sda8 /dev/sda9 /dev/sda10′ > mdadm.conf
da1:/etc # more mdadm.conf
DEVICE /dev/sda8 /dev/sda9 /dev/sda10
da1:/etc # mdadm –details –scan >> mdadm.conf
mdadm: unrecognized option `–details’
Usage: mdadm –help
for help
da1:/etc # mdadm –detail –scan >> mdadm.conf
da1:/etc # more mdadm.conf
DEVICE /dev/sda8 /dev/sda9 /dev/sda10
ARRAY /dev/md1 level=raid5 num-devices=3 UUID=ec1fadec:c6148148:b00cbf42:a733e2d
8
da1:/etc #

Yes I already register for this exam and scheduled in on October 2008. I hope that the instructor and the exam center can handle the exam on that time. I left than 1 month to do some revision. After this i can hold my first Pro Certificate. NCLP then try get the NCLE. I wish that i can pass it with the higher mark.


Register your exam here: Novell Exam Registration