MediaMotion c/o
Ubuntu – Kubuntu – Edubuntu
Postbus 3174
The Netherlands

Yup, itu adalah kiriman yang berisi paket CD Ubuntu 8.04 Desktop Edition dan Desktop Edition (64-bit). Hanya butuh 3 minggu dan CD sampai di tempat tujuan dengan rapih. Karna di dalam pembungkus kertasnya menggunakan plastik udara sehingga CD-CD tersebut dijamin aman.

Biayanya pemesanan pun gratis ! betapa baiknya mereka… . Aku hanya dikenakan biaya bea cukai Rp 3000 kepada si pengantar.

Ada 2 paket yang aku pesan yaitu CD Ubuntu 8.04 Desktop Edition untuk system berbasis x86 (berwarna merah) untuk Intel Pentium, Intel Core, dan AMD Athlon dan satu lagi Ubuntu Desktop Edition 64-bit ( berwarna kuning) untuk komputer berbasis AMD64 dan Intel64 (termasuk AMD Athlon64 dan Intel Core 2). Aku memesan 5 keping dari tiap Versinya. Jadi aku memiliki 10 keping CD Ubuntu 8.04 :)

Bagi kamu yang ingin memesan CD-CD tersebut, kamu bisa memesan di situs shipit ubuntu. Dan tentu saja Gratis !!!

Happy Ubunting !!

Diantara software yang disediakan di Linux untuk merekam layar desktop adalah recordmydesktop, sebuah program berbasis command line namun juga memiliki antarmuka front end berupa aplikasi gui.

Pertama kali harus diintal recordmydesktop

sudo apt-get install recordmydesktop

Setelah itu

Install gtk-recordmydesktop.

sudo apt-get install gtk-recordmydesktop

Maka recordmydesktop siap digunakan

Related articles:

1. gtk-recordmydesktop's tutorial
2. recordmydesktop's website.
3. Dokumentasi recordmydesktop.

For a Customer of mine, I had to setup a HAdr for WebSphere MQ.

Since there are many ways that lead to Rome, I had a look at several possibilities.

1. High Availability with the synchronisation possibility from WebSphere MQ, automated with heartbeat

2. High Availability with RH GFS

3. High Availability with DRBD and Heartbeat

It also needs to be noted that all of this is done on two virtual machines (vmware esx 3), and that we are dealing with a split site.I know that there are a lot of other possibilities when dealing with virtual machines, but it was decided (before I came to this project), that it had to be a fail-over on OS level.At first, the idea was to handle the whole setup with RedHat Cluster Suite, but as it turned out, the CS is not complete enough for what we were going to do (We would of needed RedHat Global File-system, but more about that later on.)The choice I made was for DRBD/Heartbeat. DRBD for the real time replication, and Heartbeat for the automation.

As said earlier, to set this whole thing up, we had two vm’s, both installed with RHEL4 update 6. We installed Websphere MQ series 6.0.2, which installes the application in /opt/mqm and the data is held in /var/mqm. To have MQ seperated from the OS, we also created two (extra) logical volumes: /dev/vg01/appvol and /dev/vg01/datavol, mounted on respectivly on /opt/mqm and /var/mqm.Then I started setting up DRBD.

What is DRBD

DRBD is a block device which is designed to build high availability clusters. This is done by mirroring a whole block device via (a dedicated) network. You could see it as a network raid-1.

DRBD takes over the data, writes it to the local disk and sends it to the other host. On the other host, it takes it to the disk there.

The other components needed are a cluster membership service, which is supposed to be heartbeat, and some kind of application that works on top of a block device.

Examples:

A filesystem & fsck.

A journaling FS.

A database with recovery capabilities.

How does it work ?

Each device (DRBD provides more than one of these devices) has a state, which can be 'primary' or 'secondary'. On the node with the primary device the application is supposed to run and to access the device (/dev/drbdX). Every write is sent to the local 'lower level block device' and to the node with the device in 'secondary' state. The secondary device simply writes the data to its lower level block device. Reads are always carried out locally.

If the primary node fails, heartbeat is switching the secondary device into primary state and starts the application there. (If you are using it with a non-journaling FS this involves running fsck)

If the failed node comes up again, it is a new secondary node and has to synchronise its content to the primary. This, of course, will happen whithout interruption of service in the background.

And, of course, we only will resynchronize those parts of the device that actually have been changed. DRBD has always done intelligent resynchronization when possible.

How is DRBD related to current HA clusters ?

Most current HA clusters (HP, Compaq, RHGFS,...) are using shared storage devices, thus the storage devices are connected to more than one node (Fibre Channel for example).

DRBD gives you about the same semantics as a shared device, but it does not need any uncommon hardware. It runs on top of IP networks, which are to my impression less expensive than special storage networks.

Installation

If you install via tarball, you want to read the README and INSTALL notes first.

You want to also read the upgrade*.txt files in the drbd src directory, or online in the drbd subversion repository.

Along with the DRBD tarball or your installed DRBD package, you should find a well commented example configuration file. In the tarball this is in ./scripts/drbd.conf, in installed binary packages it most likely ends up in /usr/share/doc/drbd, /usr/share/doc/packages/drbd, or similar.

You edit that to your needs, copy it to /etc/drbd.conf on both nodes, and check that the meta-disk points to the right location.

DRBD meta data

DRBD allows you to either place its meta data on the same backing device where it puts the actual usable production data (internal meta data), or on a separate block device (external meta data). Before DRBD 8, the space required for DRBD meta data was fixed at 128MB, regardless of device size. Starting with DRBD 8, you may refer to this table for estimates of DRBD meta data sizes:

Block device size

DRBD meta data

1 GB

2 MB

100 GB

5 MB

1 TB

33 MB

4 TB

128 MB

Make sure you don't direct DRBD to write its meta data to a place where you already have existing data you still need. Also, if you are using internal meta data on an existing block device with a file system on it, make sure you shrink that file system first!

Bringing up your DRBDs

Now that we have that drbd.conf, copy it to /etc/drbd.conf on both nodes. Then, on both nodes, do a drbdadm up all. It should come up as both nodes Secondary and Inconsistent.

The latter is because the underlying storage is not yet synchronized, and DRBD has no way of knowing whether you want the initial sync from left-to-right, or right-to-left. So you have to tell it. If you have no data in the underlying block devices, it does not matter. But if you have an existing filesystem on the lower level device, and now you sync in the wrong direction, you'd need to get your latest backup ready afterwards...

Performing the initial device synchronization

You choose which node shall become Primary for the first time (the one with the good data, if you have some), then you do drbdadm -- --overwrite-data-of-peer primary all. The result is a full synchronization of the underlying devices (we call this the initial full sync).

The device is usable right away, so if you have no file system already, you should create one now.

The latter is because the underlying storage is not yet synchronized, and DRBD has no way of knowing whether you want the initial sync from left-to-right, or right-to-left. So you have to tell it. If you have no data in the underlying block devices, it does not matter. But if you have an existing filesystem on the lower level device, and now you sync in the wrong direction, you'd need to get your latest backup ready afterwards...

Change from versions prior to DRBD 8

Prior to DRBD 8, what is now the --overwrite-data-of-peer option used to be --do-what-I-say. We changed the option because we found out that people mistakenly believed --do-what-I-say could be used to force any drbdadm command, regardless of its implications.

To be completed........

1. Install apache
2. Install mysql-server and configure it.
3. install phpmyadmin sudo apt-get install phpmyadmin
4. Edit the /etc/apache2/apache2.conf
5. Make new alias to refer "phpmyadmin" and redirect it to /usr/share/phpmyadmin

I don't tell you the detail, if you are a newbie, you could browse on Google to know the details of steps above.

1. Pastikan modem sudah dalam posisi bridged, kalau ternyata belum dalam posisi bridged, silakan hubungi para CS Telkom yang katanya selalu commited to u('r money) untuk lebih jelasnya. hehehe. Tahu kan nomor sakti CS: 147. Jangan lupa untuk meninggalkan pesan omelan kepada para CS kesayangan kita tersebut demi memuaskan kejengkelan anda agar anda tidak stress, kan mereka dibayar untuk sebagai tempat pelampiasan emosi, betul!!
2. Oke, sekarang setting ip anda ethernet card anda agar 24 bit pertamanya sama dengan modem. Misalnya modem 192.168.1.1 maka setting ip eth0 anda pada (contohnya) 192.168.1.10. caranya dengan mengetikkan perintah:

   sudo ifconfig eth0 192.168.1.10

3. coba akses apakah web dari modem bisa diakses, dengan cara membuka firefox kemudian mengetikkan http://192.168.1.1
4. Setelah itu aktifkan pppoeconf dengan cara ketikkan perintah berikut:

   # pppoeconf

5. Ikuti aja langkah-langkah selanjutnya.
6. Di akhir tahapan pppoeconf, anda akan diberitahukan cara mengaktifkan dial up yaitu dengan mengetikkan perintah

   # pon dsl-provider

7. Sementara untuk mematikan dapat digunakan perintah

   # poff

7 langkah di atas belum sempurna, dan disinilah inti puyengnya. Ketika menggunakan teknik di atas, ip WAN sudah dapat, namun ternyata belum bisa membuka halaman web (bisanya cuma telkomspeedy.com).  Hal ini disebabkan DNS server belum ditentukan.
Untuk menentukannya anda bisa memasukkan alamat-alamat nameserver dari DNS telkom di file /etc/resolv.conf. caranya dengan membuka file /etc/resolv.conf dengan vi atau gedit sebagai root kemudian mengisikan daftar DNS berikut ini:

nameserver 203.130.196.6
nameserver 202.134.2.5
nameserver 202.134.1.10
nameserver 202.134.0.62
nameserver 203.130.196.5
nameserver 202.134.0.155
nameserver 203.130.196.5
nameserver 203.130.196.155
nameserver 202.134.1.10

Features are:

1. v2.8 (64-bit only, use v2.7.1 for 32 -it CPUs)
2. /home and /root are NFS exported, which makes it possible to add users
3. advanced users can mount a storage device at /home, for increased space and to save work between sessions
4. Linux kernel 2.6.23.8
5. Open MPI 1.2.4, Octave 2.9.14, SciPy 0.60, NumPy 1.0.3.1, Parallel Python 2.5rc, KDE 3.5.8
6. Cloop 2.0622 (thanks Klaus Knopper)
7. Aufs cvs 17-10-07.

To know more, just visit Parallel's Knoppix homepage.

Tags: Parallel Knoppix, Knoppix Derivatives

Rank Distribution H.P.D*
1 PCLinuxOS 2913<
2 Ubuntu 2301<
3 openSUSE 1516<
4 Fedora 1341>
5 Sabayon 1171<
6 Mint 1108>
7 Debian 836<
8 Mandriva 782>
9 MEPIS 729<
10 Damn Small 671=
11 Slackware 559=
12 CentOS 467<
13 Puppy 447=
14 Zenwalk 442>
15 Gentoo 426=
16 Kubuntu 421<
17 KNOPPIX 388=
18 Arch 381<
19 FreeBSD 363=
20 Freespire 339

I think, i'm gonna learn about PCLinuxOS since now.

Tags: Distrowatch, Popular Linux, Linux

Bahasa Java meminjam banyak syntax dari C dan C++ namun memiliki keunggulan berupa model objek yang lebih sederhana dan fasilitas low-level yang lebih sedikit. Bagian kompiler, mesin virtual dan pustaka klas mulai dikembangkan oleh Sun Microsystem dari tahun 1995. Pihak ketiga juga ada yang mengembangkan implementasi alternatif milik Sun Technologies, yang paling terkenal antara lain GNU Compiler for Java dan GNU Classpath.

In the end, however, I am not ready to call this a victory.  It's premature.  For the record, I have been using Linux for about 4 years now as my primary OS (I still have an XP partition for those moments, like tax season, when it has me by the cojones).  I see four problems.

The first is that Linux will be exposed for what it doesn't do well.  Yes, a user can browse the web just like a Windows user.  But for an inexperienced user, the integration of components is not very smooth (embedded video, lack of most recent flash support, poor plugin support).  This is not so much a fault of Linux developers as much as it is the closed nature of some of these codecs, applications, and add-ons.  Reverse engineering and legal restrictions really put a damper on development.

Second, the learning curve may turn people off.  Even for a casual user, understanding a new file system structure and hierarchy, permissions, root or sudo access, clumsy application naming, and others make for the potential to be turned off from the start.  It's not that they can't learn it, it's probably that most people just don't want to bother.  They just want it to work the way they're used to.  To a certain extent, it is getting much better: Ubuntu has really ramped up the pace of user-friendliness and plain old common sense on Linux boxes.  If, as some have suggested, Dell chooses this distribution, they would be on the right path.

Thirdly, Linux needs to simplify.  I know that having a plethora of distributions is appealing to some, myself included at one point in time, it really just confuses people.  Remember when critics were claiming that Vista's new hierarchy of different versions was too tiered?  Well, the same might apply to Linux with a factor of 100.  Maybe for pre-installed Linux, they'll never have to delve into that too much, but if they're looking for support on the web, they'll have to know exactly what they're looking for.  And if they can't find it with their distro, chances are the answer is out there somewhere, but they may never understand that under the hood, Linux is pretty much all the same.

And finally, the Linux elitist attitude.  It is getting much much better.  But Linux and Mac enthusiasts tend to have this attitude of superiority.  I generally dislike Mac-only users for this reason (I use Macs too, for the record).  Some Linux users have certainly rubbed me the wrong way at the beginning of my experience.  How many times have you seen advice in the form of "RTFM"?  I completely understand the reasoning behind it; after all, you can't help someone who doesn't even want to help him or herself (and you likely don't even want to help someone like that).  But that is precisely the kind of experience that can turn someone off for good.

Let's hope I'm wrong.  These are just my honest, unbiased observations.  I love what Linux does and what it stands for on a philosophical level; to leave politics or philosophy out of the equation because 'it's the economy, stupid' is absurd in my mind.  Technology profoundly affects life, and it's important that it reflects a normative view of what we expect humanity to be.  The Linux model comes closer to that ideal than any other modern licensing scheme, and that's why this move by Dell is important.  It's not a victory yet.  But still a significant step in the right direction.

In essence, the deal allows users of Novell's Linux flavour, SuSE, to be indemnified; if Microsoft decides to sue Linux users for patent infringement, it promises that those who use Novell will be protected from lawsuits. This is a classic divide and conquer tactic at work, and the FSF is not pleased. For years, MS has been threatening to sue over patent infrinement, but not once has it disclosed exactly which patents are being violated, even at the request of the open source community. And why would they disclose it? By keeping large corporate customers, governments, educational institutions, and NGOs in a state of fear, uncertainty, and doubt (FUD), Microsoft can hang on to their business that much longer. The fear of being sued outweighs the heavy Microsoft licensing costs.

In all reality, this amounts to harrassment. The open source community is being continually threatened over things it does not know and can do nothing about. The proof, as they say, is in the pudding. It doesn't look like Microsoft will be handing out pudding anytime soon.

Over the years, Ubuntu has seen many derivatives spring up: Kubuntu (KDE-centric instead of Gnome-centric version of Ubuntu), Edubuntu (for schools and those focused on education), and even Ubuntu CE (Christian Edition), among many others.

It is no surprise, then, that a new derivative, based on Ubuntu's upcoming Feisty Fawn (the next version of Ubuntu), has sprung up. Ubuntu Studio will focus on packaging the best multimedia tools that the FOSS world has to offer: graphic tools, video editing, audio production. According to their site, there will be a base install, and various metapackages (packages that point to a group of packages to be installed for a specific purpose) will be easily installable through apt-get. For example, there will be an audio production metapackage, a video metapackage, and so on.

I've tried to get information on the kernel, but wasn't able to find it (admittedly, I didn't spend a ton of time looking for it). I would hope that it includes the multimedia real-time patch for low latency audio, which is a must.

In any case, this is an exciting development. There are other multimedia-focused and audio-focused distributions, but when one comes from the solid and polished base of Ubuntu, it can't be anything but good news. I recently tried 64 Studio and was not even able to install it (it died looking for openbsd-inetd packages). Support was sparse, and the screenshots didn't demonstrate any polish or cohesion that Ubuntu Studio promises to have.

They are aiming for an April release, likely coinciding with the new version of Ubuntu due during the same month.

I will post more info (and possibly a review) in the near future.

One of the biggest concerns and barriers to implementation came from the blind community. They claimed, and rightly so, that ODF and the applications that support it do not yet support screen magnifiers to assist the legally blind in reading documents on screen. Therefore, the state has decided to push back the implementation date to June 2007. This is a smart move by the state. People with disabilities too often get left out in the cold as a result of government policy. Treated as an afterthought, they must often wait several years to gain access to technologies that others take for granted.

The ODF initiative is a great one; in fact, more states should follow suit. We need more government accountability and less dependence on a single vendor. But this cannot come at the expense of certain users.

More on this when it becomes available.