smkbbs.sch.id

Artikel
File Server using SAMBA on Debian Etch PDF Print E-mail
  
Friday, 01 May 2009 01:40
Install Samba in Debian
#apt-get install samba samba-common samba-client
This will start samba installation and prompted for the following questions
First you need to enter the Workgroup/Domain Name in this example i am using ruchi select ok and press enter
Preparing directories and users
Create directories for Samba to use with Windows
#mkdir windowsshare
Now we need to create users to access this directiory
#useradd david
Now create a password for this user using the following command
#smbpasswd -a david
Samba configuration 
By default samba configuration file located at /etc/samba/smb.conf
In this file main section is Global where you can define all parameters and the example as follows
[global]
workgroup = ruchi
netbios name = fileserver
server string = %h server (Samba %v)
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
Last Updated ( Friday, 01 May 2009 01:41 )
Read more...
 
Update The Source List Debian and Ubuntu PDF Print E-mail
  
Friday, 01 May 2009 01:38
Selamat Datang di SMK BBS Batam....!
Last Updated ( Thursday, 15 October 2009 06:36 )
 
Configure LAN on Debian Etch PDF Print E-mail
  
Friday, 01 May 2009 01:37
Because the Debian Etch installer has configured our system to get its network settings via DHCP, we have to change that now because a server should have a static IP address. Edit /etc/network/interfaces and adjust it to your needs (in this example setup I will use the IP address 192.168.0.100) (please note that I replace allow-hotplug eth0 with auto eth0; otherwise restarting the network doesn't work, and we'd have to reboot the whole system): 
vi /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
#allow-hotplug eth0
#iface eth0 inet dhcp
auto eth0
iface eth0 inet static
  address 192.168.0.100
  netmask 255.255.255.0
  network 192.168.0.0
  broadcast 192.168.0.255
  gateway 192.168.0.1
Then restart your network: 
/etc/init.d/networking restart

Read more...
 
Test Methodology: How Do You Compare Multiple Cores? PDF Print E-mail
  
Thursday, 30 April 2009 08:49

To keep things on an even keel, we chose a quad-core CPU for our test bed--an overclocked Intel Core 2 Quad Q6600 at 2.7 GHz. After we ran all of our benchmarks on the system, we then disabled one of the cores, rebooted, and ran the benchmarks again. We rinsed and repeated until we had results for one to four CPU cores, all running at identical clock speeds on the same CPU.

It turns out that disabling a CPU core in Windows is easy to do. If you’re interested in trying it yourself, simply type "msconfig" in Windows Vista's "Start Search" field and hit enter. This will open up the system-configuration application.

From here, click the "Boot" tab, and then click the "Advanced options" button.

This will bring up the "BOOT Advanced Options" pop-up menu. Simply click the "Number of Processors" check-box and select the number of processors you’d like your system to use from the drop-down menu. It’s that simple.

After clicking "okay," you’ll be prompted to reboot. After the reboot, you can easily see if the proper number of processor cores is available through Windows Task Manager. Open the task manager by simultaneously hitting "Ctrl-Alt-Delete’" and selecting "Task Manager" from the pop-up menu.

Then, select the "Performance" tab. You will see a CPU-usage graph for each enabled processor (whether it's physical, as seen here, or logical, as you'd get from a Core i7 with Hyper-Threading) under "CPU Usage History." Two histograms mean that two cores are enabled, three mean three cores are active, etc.

Now that you know the method to our madness, let’s go over the details of the hardware and software we use for our tests.

 
How Many CPU Cores Do You Need? PDF Print E-mail
  
Thursday, 30 April 2009 08:47

In the early years of the new millennium, with CPU clock speeds finally accelerating past the 1 GHz mark, some folks (Ed.: including Intel itself) predicted that the company's new NetBurst architecture would reach speeds of 10 GHz in the future. PC enthusiasts looked forward to a new world where CPU clocks kept increasing at an accelerating pace. Need more power? Just add clock speed.

Newton’s apple inevitably fell soundly on the heads of those starry-eyed dreamers who looked to MHz as the easiest way to continue scaling PC performance. Physics doesn’t allow for exponential increases in clock rate without exponential increases in heat, and there were a number of other challenges to consider, such as manufacturing technology. Indeed, the fastest commercial CPUs have been hovering between 3 GHz and 4 GHz for a number of years now.

Of course, progress can’t be stopped when money is involved, and with folks willing to shell out cash for more powerful computers, engineers set out to find ways to increase performance by improving efficiency rather than relying solely on clock speed. Parallelism presented itself as a solution--if you can’t make the CPU faster, well, why not add addition compute resources?

The trouble with parallelism is that software has to be specifically written to run in multiple threads--it doesn't offer an immediate return on investment, like clock speed. Back in 2005, when the first dual-core CPUs were seeing the light of day, they didn’t offer much in the way of tangible performance increases because there was so little desktop software available properly supporting them. In fact, most dual-core CPUs were slower than single-core CPUs in a great majority of tasks because single-core CPUs were available at higher clock speeds.

However, that was four years ago and a lot has changed. Many software developers have since been hard at work optimizing their applications to take advantage of multiple cores. Single-core CPUs are actually hard to find and two-, three-, and four-core CPUS are now the norm.

Which begs the question: how many CPU cores are right for me? Is a triple-core processor good enough for gaming, or should you splurge on a quad-core chip? Is a dual-core CPU good enough for the average user, or do more cores really make a difference? Which applications are optimized for multiple cores and which ones react only to specifications like frequency or cache size?

We thought it would be a good time to run some tests with apps from our updated benchmark suite (there are still more to come, too), running the gamut of one, two, three, and quad-core configurations to illustrate what multi-core CPUs really offer in 2009.