Disks are becoming cheaper and so it’s becoming common to have on our desk an external (usually USB) hard drive with a size of 1TB or more.
Now, once that we bring at home our new gadget the first question for us is: “which Filesystem should i use with this big disk ?”

Let’s take a look at some options you have to suit your needs.

Multi-Partition solution

A possible solution is to split your hard drive in multiple partitions and dedicate each one to an Operating system, so for example you could have 25% of your disk with a Fat32, 25% with NTFS and 50% with Ext4. Personally i don’t like too much this solution, sure you can use a native file system in every operating system, but you also have all the possible problems in mounting a different FS, and I’m sure that I happen to have the right documents in the wrong partition.

So, for me the best solution is to have 1 partition and 1 big filesystem.

The most common File systems

The most common choices when you think at a USB hard disk are FAT32, NTFS, ext3 and ext4 (well this one is a less common than the others i suppose),, so as first thing let’s take a look at the limits of these filesystems:

File size limit:
FAT32 : 4GiB
NTFS : 16 EB
ext3 : 2 TiB
ext4 : 16 TiB

Partition size limit:
FAT32 : 2TiB
NTFS : 2TiB
ext3 : 32TiB
ext4 : 1 EiB

Taking a quick look at these information i’d discard FAT32, is becoming common to have big files, such as the backup of a Bluray or a DVD and the technology behind this FS is really old, the good thing of this FS is that is well supported by all operating systems.
Note: FAT32 theoretically has a volume limit of 2TB, but Windows won’t let you format a partition larger than ~32GB as FAT32 so you’d have to format it in Linux.

The other FS that at the moment i discard is ext4, This FS is good if you use only Linux, but there is no support on WIndows for ext4.

NTFS

If your primary operating system is windows this is probably the best choice, This FS is compatible with OSX and there is a good read/write support on Linux with the NTFS-3G driver. NTFS-3G supports all operations for writing files: files of any size can be created, modified, renamed, moved, or deleted on NTFS partitions. Transparent compression is supported, but there is no support for encryption.Support to modify access control lists and permissions is available. NTFS partitions are mounted using the Filesystem in Userspace (FUSE) interface.

Ext3

If your primary operating system is Linux ext3 could be your filesystem. It’s reliable and fast enough for a general use and some operations are supported on Windows, thanks to ext2fsd an open source ext3/4 file system driver for Windows (2K/XP/VISTA/WIN7).

Features Ext2Fsd supports:

• ext2/ext3 volume reading & writing
• ext3 journal replay when mounting
• various codepage: utf8, cp936, cp950 …
• mountpoint automatical assignment
• large inode size: 128, 256, …
• CIFS sharing over network
• htree directory indexing

Article sponsored by Ian, owner of the site 1tb external hard drive

» Linuxaria – Everything about GNU/Linux and Open source The Best Filesystem for an external hard disk of 1TB with cross platform support..

This 11 commands make you like a real administrator, even this is very simple but also this will be used many times or even we used it but doesn’t realize it.

Check this “eleven” commands :

1. Save man-page as pdf

 man -t awk | ps2pdf - awk.pdf

2. Duplicate installed packages from one machine to the other (RPM-based systems)

ssh root@remote.host "rpm -qa" | xargs yum -y install

3. Stamp a text line on top of the pdf pages to quickly add some remark, comment, stamp text, … on top of (each of) the pages of the input pdf file

echo "This text gets stamped on the top of the pdf pages." | enscript -B -f Courier-Bold16 -o- | ps2pdf - | pdftk input.pdf stamp - output output.pdf

4. Display the number of connections to a MySQL Database

Count the number of active connections to a MySQL database.
The MySQL command “show processlist” gives a list of all the active clients.
However, by using the processlist table, in the information_schema database, we can sort and count the results within MySQL.

mysql -u root -p -BNe "select host,count(host) from processlist group by host;" information_schema

5- Create a local compressed tarball from remote host directory

ssh user@host "tar -zcf - /path/to/dir" > dir.tar.gz

This improves on #9892 by compressing the directory on the remote machine so that the amount of data transferred over the network is much smaller. The command uses ssh(1) to get to a remote host, uses tar(1) to archive and compress a remote directory, prints the result to STDOUT, which is written to a local file. In other words, we are archiving and compressing a remote directory to our local box.

6. tail a log over ssh

This is also handy for taking a look at resource usage of a remote box.

ssh -t remotebox "tail -f /var/log/remote.log"

7. Print diagram of user/groups

Parses /etc/group to “dot” format and pases it to “display” (imagemagick) to show a usefull diagram of users and groups (don’t show empty groups).

awk 'BEGIN{FS=":"; print "digraph{"}{split($4, a, ","); for (i in a) printf ""%s" [shape=box]n"%s" -> "%s"n", $1, a[i], $1}END{print "}"}' /etc/group|display

8. Draw kernel module dependancy graph.

Parse `lsmod’ output and pass to `dot’ drawing utility then finally pass it to an image viewer

lsmod | perl -e 'print "digraph "lsmod" {";<>;while(<>){@_=split/s+/; print ""$_[0]" -> "$_"n" for split/,/,$_[3]}print "}"' | dot -Tpng | display -

9. Create strong, but easy to remember password

Why remember? Generate!
Up to 48 chars, works on any unix-like system

read -s pass; echo $pass | md5sum | base64 | cut -c -16

10. Find all files larger than 500M and less than 1GB

find / -type f -size +500M -size -1G

11. Limit the cpu usage of a process

This will limit the average amount of CPU it consumes.

sudo cpulimit -p pid -l 50

How do you feel?

11 useful commands for Linux/Unix administrators | Unixmen.

SpaceFM is a new file manager, not mature enough but quite powerfull, even i replace pcmanfm with this.

take a look :

very similiar to pcmanfm right? but this is the difference, pcmanfm now using gvfs, with advantages trash & network device support but also boost the memory usage because it’s mean you need gvfs packages, this application also work like old pcmanfm version 0.5.x which using “hal” even manay distro abandoned it, but hal is very powerfull stable and fast also, little memories usage, but doesn’t give you trash or network storage support like samba, ssh, etc.

If you need the lightweight one this is may be can satisfiy you 🙂

AUR : http://aur.archlinux.org/packages.php?ID=55777
Packages : http://downloads.sourceforge.net/project/spacefm/spacefm-0.6.2.tar.xz

Wireshark is “free software”; you can download it without paying any license fee. The version of Wireshark you download isn’t a “demo” version, with limitations not present in a “full” version; it is the full version.

Wireshark is the world’s foremost network protocol analyzer. It lets you capture and interactively browse with graphical interface the traffic running on a computer network. It is the de facto (and often de jure) standard across many industries and educational institutions.

Wireshark development thrives thanks to the contributions of networking experts across the globe. It is the continuation of a project that started in 1998.

Supports for particular protocols is added to Wireshark as a result of people contributing that support; no formal plans for adding support for particular protocols in particular future releases exist.

If a network analyzer writes out files in a format already supported by Wireshark (e.g., in libpcap format), Wireshark may already be able to read them, unless the analyzer has added its own proprietary extensions to that format.

If a network analyzer writes out files in its own format, or has added proprietary extensions to another format, in order to make Wireshark read captures from that network analyzer, we would either have to have a specification for the file format, or the extensions, sufficient to give us enough information to read the parts of the file relevant to Wireshark, or would need at least one capture file in that format and a detailed textual analysis of the packets in that capture file (showing packet time stamps, packet lengths, and the top-level packet header) in order to reverse-engineer the file format.

Note that there is no guarantee that we will be able to reverse-engineer a capture file format.

Wireshark is almost (but not quite) a fork. Normally a “fork” of an open source project results in two names, web sites, development teams, support infrastructures, etc. This is the case with Wireshark except for one notable exception — every member of the core development team is now working on Wireshark. There has been no active development on Ethereal since the name change. Several parts of the Ethereal web site (such as the mailing lists, source code repository, and build farm) have gone offline.

Wireshark is very similar to tcpdump, but has a graphical front-end, plus some integrated sorting and filtering options.

Wireshark allows the user to put the network interfaces that support promiscuous mode into that mode, in order to see all traffic visible on that interface, not just traffic addressed to one of the interface’s configured addresses and broadcast/multicast traffic. However, when capturing with a packet analyzer in promiscuous mode on a port on a network switch, not all of the traffic traveling through the switch will necessarily be sent to the port on which the capture is being done, so capturing in promiscuous mode will not necessarily be sufficient to see all traffic on the network. Port mirroring or various network taps extend capture to any point on net; simple passive taps are extremely resistant to malware tampering.

On Linux, BSD, and Mac OS X, with libpcap 1.0.0 or later, Wireshark 1.4 and later can also put Wi-Fi adapters into monitor mode.

Wireshark in Ubuntu.

RAID stands for redundant array of independent disks. A RAID appears to the operating system to be a single logical hard disk. RAID employs the technique of disk striping, which involves partitioning each drive’s storage space into units ranging from a sector (512 bytes) up to several megabytes. The stripes of all the disks are interleaved and addressed in order.

I recently change a failed RAID 1 hard drive on our server. This will happened when 1 disk on your RAID configuration has an error. Kernel will inform you when 1 of your disk drive  is failing. You can find this on your log files. See /var/log/messages or /var/log/syslog.

I will not explain each and every one of these types. I will give the definition only, as I will focus and use only the replacing RAID-1 failed hard drive.

Types of RAID:

RAID-0

This technique has striping but no redundancy of data.

RAID-1

This type is also known as disk mirroring and consists of at least two drives that duplicate the storage of data.

RAID-2

This type uses striping across disks with some disks storing error checking and correcting (ECC) information.

RAID-3

This type uses striping and dedicates one drive to storing parity information.

RAID-4

This type uses large stripes, which means you can read records from any single drive.

RAID-5

This type includes a rotating parity array, thus addressing the write limitation in RAID-4.

RAID-6

This type is similar to RAID-5 but includes a second parity scheme that is distributed across different drives and thus offers extremely high fault- and drive-failure tolerance.

RAID-7

This type includes a real-time embedded operating system as a controller, caching via a high-speed bus, and other characteristics of a stand-alone computer.

RAID-10

Combining RAID-0 and RAID-1 is often referred to as RAID-10, which offers higher performance than RAID-1 but at much higher cost.

RAID-50

This type consists of a series of RAID-5 groups and striped in RAID-0 fashion to improve RAID-5 performance without reducing data protection.

RAID-53

This type uses striping (in RAID-0 style) for RAID-3′s virtual disk blocks.

RAID-S

This is an alternate, proprietary method for striped parity RAID from EMC Symmetrix that is no longer in use on current equipment.

For my setup, we use the RAID 1 so that if ever the other disk fails we will always have a back up. RAID 1 is like a mirror, I will write on both disks what is the data on your computer. RAID 1 will appear as 1 disk on your computer.

Requirements for RAID 1:

1. Same hard drive model

2. Same hard drive size

3. Same partition size

This will be the partitioning of the hard drive:

Disk 1 (sda) has two (2) partitions: /dev/sda1 and /dev/sda2

Second disk (sdb) must have the save partition size and number: /dev/sdb1 and /dev/sdb2

/dev/sda1 and /dev/sdb1 make up the RAID1 array /dev/md0.

/dev/sda2 and /dev/sdb2 make up the RAID1 array /dev/md1.

How to tell that your hard drive is failing:

See the following files:

/var/log/messages or /var/log/syslog.

Also please take note of the output of this command:

cat /proc/mdstat

Notice if you have this [U_]  this is a failed disk drive already.

See the output below.

raid@ubuntucommand:~$ sudo cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sdb3[2] sda3[0] [F]
466802552 blocks super 1.2 [2/2] [U_]

md0 : active raid1 sdb1[2] sda1[0] [F]
19626936 blocks super 1.2 [2/2] [U_]

unused devices: <none>

To identify which is the disk drive that is failing:

Install the program hdparm

raid@ubuntucommand:~$ sudo apt-get install hdparm

Note:

Every hard drive has its own unique serial number. In this way we can separate the fail hard drive to the running one.

raid@ubuntucommand:~$ sudo hdparm –I /dev/sda

/dev/sda:

Model=ST3320620NS, FwRev=3.AEG, SerialNo=9QFAP54A
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=16384kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=625142448
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes:  pio0 pio1 pio2 pio3 pio4
DMA modes:  mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=yes: unknown setting WriteCache=enabled
Drive conforms to: Unspecified:  ATA/ATAPI-1,2,3,4,5,6,7

* signifies the current active mode

Mark the drive partition as fail:

Use the command:

mdadm –manage /dev/md0 –fail /dev/sdb1

Remove the drive partition on the RAID drive configuration:

Use the command:

mdadm –manage /dev/md0 –remove /dev/sdb1

raid@ubuntucommand:~$ sudo mdadm –manage /dev/md0 –remove /dev/sdb1
mdadm: hot removed /dev/sdb1

After removing see the check the RAID:

raid@ubuntucommand:~$ sudo cat /proc/mdstat

Personalities : [raid1]

md0 : active raid1 sda1[0]
24418688 blocks [2/1] [U_]

md1 : active raid1 sda2[0] sdb2[1]
24418688 blocks [2/2] [UU]

unused devices: <none>

Remove the second partition on the RAID configuration.

Shutdown the server:

shutdown -h now

Remove the correct fail hard drive; make sure it is the right serial number.

Install the new hard drive make sure it is properly detected.

Create the exact same partition on the new unpartitioned disk drive (sdb).

Use the command below to partition the disk drive.

raid@ubuntucommand:~$ sudo sfdisk -d /dev/sda | sfdisk /dev/sdb

Note:

If it fails………

Sfdisk I don’t like these partitions – nothing changed.

Solution:

-f or –force

Do what I say, even if it is stupid.

I spent 2 hours about this one. This will force the disk drive to be partition if there is an error

raid@ubuntucommand:~$ sudo sfdisk -d /dev/sda | sfdisk –force /dev/sdb

check the partition:

raid@ubuntucommand:~$ sudo fdisk –l

Add the first partition to the RAID configuration:

raid@ubuntucommand:~$ sudo mdadm –manage /dev/md0 –add /dev/sdb1

Output:

raid@ubuntucommand:~$ sudo mdadm –manage /dev/md0 –add /dev/sdb1
mdadm: re-added /dev/sdb1

Check the disk if it is on sync:

raid@ubuntucommand:~$ sudo cat /proc/mdstat

raid@ubuntucommand:~$ sudo cat /proc/mdstat
Personalities : [raid1]

md0 : active raid1 sda1[0] sdb1[1]
24418688 blocks [2/1] [U_]
[=>……………….]  recovery =  9.9% (2423168/24418688) finish=2.8min speed=127535K/sec

md1 : active raid1 sda2[0] sdb2[1]
24418688 blocks [2/1] [U_]
[=>……………….]  recovery =  6.4% (1572096/24418688) finish=1.9min speed=196512K/sec

After a few hours, check the final output.

raid@ubuntucommand:~$ sudo cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sdb3[2] sda3[0]
466802552 blocks super 1.2 [2/2] [UU]

md0 : active raid1 sdb1[2] sda1[0]
19626936 blocks super 1.2 [2/2] [UU]

unused devices: <none>

That’s it we have just successfully change the fail hard drive on a RAID 1 configuration.

Replace failed raid hard drive.

Linux has a lot of filesystems, but two of them (ext4 and btrfs) tend to get most of the attention. In his 2012 linux.conf.au talk, XFS developer Dave Chinner served notice that he thinks more users should be considering XFS. His talk covered work that has been done to resolve the biggest scalability problems in XFS and where he thinks things will go in the future. If he has his way, we will see a lot more XFS around in the coming years.

XFS is often seen as the filesystem for people with massive amounts of data. It serves that role well, Dave said, and it has traditionally performed well for a lot of workloads. Where things have tended to fall down is in the writing of metadata; support for workloads that generate a lot of metadata writes has been a longstanding weak point for the filesystem. In short, metadata writes were slow, and did not really scale past even a single CPU.

How slow? Dave put up some slides showing fs-mark results compared to ext4. XFS was significantly worse (as in half as fast) even on a single CPU; the situation just gets worse up to eight threads, after which ext4 hits a cliff and slows down as well. For I/O-heavy workloads with a lot of metadata changes – unpacking a tarball was given as an example – Dave said that ext4 could be 20-50 times faster than XFS. That is slow enough to indicate the presence of a real problem.

Delayed logging

The problem turned out to be journal I/O; XFS was generating vast amounts of journal traffic in response to metadata changes. In the worst cases, almost all of the actual I/O traffic was for the journal – not the data the user was actually trying to write. Solving this problem took multiple attempts over years, one major algorithm change, and a lot of other significant optimizations and tweaks. One thing that was not required was any sort of on-disk format change – though that may be in the works in the future for other reasons.

Metadata-heavy workloads can end up changing the same directory block many times in a short period; each of those changes generates a record that must be written to the journal. That is the source of the huge journal traffic. The solution to the problem is simple in concept: delay the journal updates and combine changes to the same block into a single entry. Actually implementing this idea in a scalable way took a lot of work over some years, but it is now working; delayed logging will be the only XFS journaling mode supported in the 3.3 kernel.

The actual delayed logging technique was mostly stolen from the ext3 filesystem. Since that algorithm is known to work, a lot less time was required to prove that it would work well for XFS as well. Along with its performance benefits, this change resulted in a net reduction in code. Those wanting details on how it works should find more than they ever wanted in filesystems/xfs-delayed-logging.txt in the kernel documentation tree.

Delayed logging is the big change, but far from the only one. The log space reservation fast path is a very hot path in XFS; it is now lockless, though the slow path still requires a global lock at this point. The asynchronous metadata writeback code was creating badly scattered I/O, reducing performance considerably. Now metadata writeback is delayed and sorted prior to writing out. That means that the filesystem is, in Dave’s words, doing the I/O scheduler’s work. But the I/O scheduler works with a request queue that is typically limited to 128 entries while the XFS delayed metadata writeback queue can have many thousands of entries, so it makes sense to do the sorting in the filesystem prior to I/O submission. “Active log items” are a mechanism that improves the performance of the (large) sorted log item list by accumulating changes and applying them in batches. Metadata caching has also been moved out of the page cache, which had a tendency to reclaim pages at inopportune times. And so on.

How the filesystems compare

So how does XFS scale now? For one or two threads, XFS is still slightly slower than ext4, but it scales linearly up to eight threads, while ext4 gets worse, and btrfs gets a lot worse. The scalability constraints for XFS are now to be found in the locking in the virtual filesystem layer core, not in the filesystem-specific code at all. Directory traversal is now faster for even one thread and much faster for eight. These are, he suggested, not the kind of results that the btrfs developers are likely to show people.

The scalability of space allocation is “orders of magnitude” faster than ext4 offers now. That changes a bit with the “bigalloc” feature added in 3.2, which improves ext4 space allocation scalability by two orders of magnitude if a sufficiently large block size is used. Unfortunately, it also increases small-file space usage by about the same amount, to the point that 160GB are required to hold a kernel tree. Bigalloc does not play well with some other ext4 options and requires complex configuration questions to be answered by the administrator, who must think about how the filesystem will be used over its entire lifetime when the filesystem is created. Ext4, Dave said, is suffering from architectural deficiencies – using bitmaps for space tracking, in particular – that are typical of an 80’s era filesystem. It simply cannot scale to truly large filesystems.

Space allocation in Btrfs is even slower than with ext4. Dave said that the problem was primarily in the walking of the free space cache, which is CPU intensive currently. This is not an architectural problem in btrfs, so it should be fixable, but some optimization work will need to be done.

The future of Linux filesystems

Where do things go from here? At this point, metadata performance and scalability in XFS can be considered to be a solved problem. The performance bottleneck is now in the VFS layer, so the next round of work will need to be done there. But the big challenge for the future is in the area of reliability; that may require some significant changes in the XFS filesystem.

Reliability is not just a matter of not losing data – hopefully XFS is already good at that – it is really a scalability issue going forward. It just is not practical to take a petabyte-scale filesystem offline to run a filesystem check and repair tool; that work really needs to be done online in the future. That requires robust failure detection built into the filesystem so that metadata can be validated as correct on the fly. Some other filesystems are implementing validation of data as well, but that is considered to be beyond the scope of XFS; data validation, Dave said, is best done at either the storage array or the application levels.

“Metadata validation” means making the metadata self describing to protect the filesystem against writes that are misdirected by the storage layer. Adding checksums is not sufficient – a checksum only proves that what is there is what was written. Properly self-describing metadata can detect blocks that were written in the wrong place and assist in the reassembly of a badly broken filesystem. It can also prevent the “reiserfs problem,” where a filesystem repair tool is confused by stale metadata or metadata found in filesystem images stored in the filesystem being repaired.

Making the metadata self-describing involves a lot of changes. Every metadata block will contain the UUID of the filesystem to which it belongs; there will also be block and inode numbers in each block so the filesystem can verify that the metadata came from the expected place. There will be checksums to detect corrupted metadata blocks and an owner identifier to associate metadata with its owning inode or directory. A reverse-mapping allocation tree will allow the filesystem to quickly identify the file to which any given block belongs.

Needless to say, the current XFS on-disk format does not provide for the storage of all this extra data. That implies an on-disk format change. The plan, according to Dave, is to not provide any sort of forward or backward format compatibility; the format change will be a true flag day. This is being done to allow complete freedom in designing a new format that will serve XFS users for a long time. While the format is being changed to add the above-described reliability features, the developers will also add space for d_type in the directory structure, NFSv4 version counters, the inode creation time, and, probably, more. The maximum directory size, currently a mere 32GB, will also be increased.

All this will enable a lot of nice things: proactive detection of filesystem corruption, the location and replacement of disconnected blocks, and better online filesystem repair. That means, Dave said, that XFS will remain the best filesystem for large-data applications under Linux for a long time.

What are the implications of all this from a btrfs perspective? Btrfs, Dave said, is clearly not optimized for filesystems with metadata-heavy workloads; there are some serious scalability issues getting in the way. That is only to be expected for a filesystem at such an early stage of development. Some of these problems will take some time to overcome, and the possibility exists that some of them might not be solvable. On the other hand, the reliability features in btrfs are well developed and the filesystem is well placed to handle the storage capabilities expected in the coming few years.

Ext4, instead, suffers from architectural scalability issues. According to Dave’s results, it is not the fastest filesystem anymore. There are few plans for reliability improvements, and its on-disk format is showing its age. Ext4 will struggle to support the storage demands of the near future.

Given that, Dave had a question of sorts to end his presentation with. Btrfs will, thanks to its features, soon replace ext4 as the default filesystem in many distributions. Meanwhile, ext4 is being outperformed by XFS on most workloads, including those where it was traditionally stronger. There are scalability problems that show up on even smaller server systems. It is “an aggregation of semi-finished projects” that do not always play well together; ext4, Dave said, is not as stable or well-tested as people think. So, he asked: why do we still need ext4?

One assumes that ext4 developers would have a robust answer to that question, but none were present in the room. So this seems like a discussion that will have to be continued in another setting; it should be interesting to watch.

[ Your editor would like to thank the linux.conf.au organizers for their assistance with his travel to the conference. ]

XFS: the filesystem of the future? [LWN.net].

LinuxMint 12 KDE has been released, this edition comes with the latest and recently released KDE 4.7.4. This is the first release of Linux Mint using Hybrid ISO images. Traditionally, tools such as ‘Startup Disk Creator’ or ‘UNetbootin’ were needed to install Linux Mint via USB. With hybrid images, you can simply use the ‘dd’ command or a graphical front-end to make a bootable USB stick with no efforts which acts exactly like a live DVD.

Linux Mint 12 features the following upstream components: Ubuntu 11.10, Linux 3.0, KDE 4.7.4.

Here are some screenshots from this new edition of LinuxMint12 KDE

LinuxMint12 KDE has been released! | Screenshots Tour | Unixmen.

Update kernel 3.2.2 pada archlinux dan beberapa distro membuat wireless atheros based tidak dapat dipakai, wireless memang bisa terdeteksi akan tetapi tidak melakukan apa pun. semoga cepat diperbaiki.

Hal ini terjadi pada saya dan teman-teman saya juga. Jika hal yang terjadi berbeda pada anda, komen disini 🙂

Update status lewat terminal???
bisa sekarang,,, lewat aplikasi ini,…
aplikasi ini membutuhkan setidaknya php5 dan php-cli

1. sudo apt-get install php5 php5-cli
2. lalu ubah setingan PHP harus mengijinkan “allow_url_fopen” Continue reading →

>~/.mpd/mpd.conf

# An example configuration file for MPD
# See the mpd.conf man page for a more detailed description of each parameter.

# Files and directories #######################################################
#
# This setting controls the top directory which MPD will search to discover the
# available audio files and add them to the daemon’s online database. This
# setting defaults to the XDG directory, otherwise the music directory will be
# be disabled and audio files will only be accepted over ipc socket (using
# file:// protocol) or streaming files over an accepted protocol.
#
music_directory        “~/Music”
#
# This setting sets the MPD internal playlist directory. The purpose of this
# directory is storage for playlists created by MPD. The server will use
# playlist files not created by the server but only if they are in the MPD
# format. This setting defaults to playlist saving being disabled.
#
#playlist_directory “/var/lib/mpd/playlists”
#
# This setting sets the location of the MPD database. This file is used to
# load the database at server start up and store the database while the
# server is not up. This setting defaults to disabled which will allow
# MPD to accept files over ipc socket (using file:// protocol) or streaming
# files over an accepted protocol.

#
db_file “~/.mpd/mpd.db”
#
# These settings are the locations for the daemon log files for the daemon.
# These logs are great for troubleshooting, depending on your log_level
# settings.
#
# The special value “syslog” makes MPD use the local syslog daemon. This
# setting defaults to logging to syslog, otherwise logging is disabled.
#
#log_file “/var/log/mpd/mpd.log”
#
# This setting sets the location of the file which stores the process ID
# for use of mpd –kill and some init scripts. This setting is disabled by
# default and the pid file will not be stored.
#
pid_file “~/.mpd/mpd.pid”
#
# This setting sets the location of the file which contains information about
# most variables to get MPD back into the same general shape it was in before
# it was brought down. This setting is disabled by default and the server
# state will be reset on server start up.
#
state_file “/var/lib/mpd/mpdstate”
#
# The location of the sticker database.  This is a database which
# manages dynamic information attached to songs.
#
#sticker_file            “~/.mpd/sticker.sql”
#
###############################################################################

# General music daemon options ################################################
#
# This setting specifies the user that MPD will run as. MPD should never run as
# root and you may use this setting to make MPD change its user ID after
# initialization. This setting is disabled by default and MPD is run as the
# current user.
#
#user “mpd”
#
# This setting specifies the group that MPD will run as. If not specified
# primary group of user specified with “user” setting will be used (if set).
# This is useful if MPD needs to be a member of group such as “audio” to
# have permission to use sound card.
#
#group                “nogroup”
#
# This setting sets the address for the daemon to listen on. Careful attention
# should be paid if this is assigned to anything other then the default, any.
# This setting can deny access to control of the daemon.
#
# For network
bind_to_address        “127.0.0.2”
#
# And for Unix Socket
#bind_to_address        “~/.mpd/socket”
#
# This setting is the TCP port that is desired for the daemon to get assigned
# to.
#
port                “6600”
#
# This setting controls the type of information which is logged. Available
# setting arguments are “default”, “secure” or “verbose”. The “verbose” setting
# argument is recommended for troubleshooting, though can quickly stretch
# available resources on limited hardware storage.
#
#log_level            “default”
#
# If you have a problem with your MP3s ending abruptly it is recommended that
# you set this argument to “no” to attempt to fix the problem. If this solves
# the problem, it is highly recommended to fix the MP3 files with vbrfix
# (available from ), at which
# point gapless MP3 playback can be enabled.
#
gapless_mp3_playback            “yes”
#
# This setting enables MPD to create playlists in a format usable by other
# music players.
#
save_absolute_paths_in_playlists    “no”
#
# This setting defines a list of tag types that will be extracted during the
# audio file discovery process. Optionally, ‘comment’ can be added to this
# list.
#
metadata_to_use    “artist,album,title,track,name,genre,date,composer,performer,disc”
#
# This setting enables automatic update of MPD’s database when files in
# music_directory are changed.
#
auto_update    “yes”
#
# Limit the depth of the directories being watched, 0 means only watch
# the music directory itself.  There is no limit by default.
#
auto_update_depth “3”
#
###############################################################################

# Symbolic link behavior ######################################################
#
# If this setting is set to “yes”, MPD will discover audio files by following
# symbolic links outside of the configured music_directory.
#
#follow_outside_symlinks    “yes”
#
# If this setting is set to “yes”, MPD will discover audio files by following
# symbolic links inside of the configured music_directory.
#
#follow_inside_symlinks        “yes”
#
###############################################################################

# Zeroconf / Avahi Service Discovery ##########################################
#
# If this setting is set to “yes”, service information will be published with
# Zeroconf / Avahi.
#
#zeroconf_enabled        “yes”
#
# The argument to this setting will be the Zeroconf / Avahi unique name for
# this MPD server on the network.
#
#zeroconf_name            “Music Player”
#
###############################################################################

# Permissions #################################################################
#
# If this setting is set, MPD will require password authorization. The password
# can setting can be specified multiple times for different password profiles.
#
#password                        “password@read,add,control,admin”
#
# This setting specifies the permissions a user has who has not yet logged in.
#
#default_permissions             “read,add,control,admin”
#
###############################################################################

# Input #############################
##########################################
#

input {
        plugin “curl”
#       proxy “proxy.isp.com:8080”
#       proxy_user “user”
#       proxy_password “password”
}

#
###############################################################################

# Audio Output ################################################################
#
# MPD supports various audio output types, as well as playing through multiple
# audio outputs at the same time, through multiple audio_output settings
# blocks. Setting this block is optional, though the server will only attempt
# autodetection for one sound card.
#
# See for examples of
# other audio outputs.
#
# An example of an ALSA output:
#
#audio_output {
#    type        “alsa”
#    name        “My ALSA Device”
##    device        “hw:0,0”    # optional
##    format        “44100:16:2”    # optional
##    mixer_type      “hardware”    # optional
##    mixer_device    “default”    # optional
##    mixer_control    “PCM”        # optional
##    mixer_index    “0”        # optional
#}
#
# An example of an OSS output:
#
#audio_output {
#    type        “oss”
#    name        “My OSS Device”
##    device        “/dev/dsp”    # optional
##    format        “44100:16:2”    # optional
##    mixer_type      “hardware”    # optional
##    mixer_device    “/dev/mixer”    # optional
##    mixer_control    “PCM”        # optional
#}
#
# An example of a shout output (for streaming to Icecast):
#
#audio_output {
#    type        “shout”
#    encoding    “ogg”            # optional
#    name        “My Shout Stream”
#    host        “localhost”
#    port        “8000”
#    mount        “/mpd.ogg”
#    password    “hackme”
#    quality        “5.0”
#    bitrate        “128”
#    format        “44100:16:1”
##    protocol    “icecast2”        # optional
##    user        “source”        # optional
##    description    “My Stream Description”    # optional
##    genre        “jazz”            # optional
##    public        “no”            # optional
##    timeout        “2”            # optional
##    mixer_type      “software”        # optional
#}
#
# An example of a recorder output:
#
#audio_output {
#    type        “recorder”
#    name        “My recorder”
#    encoder        “vorbis”        # optional, vorbis or lame
#    path        “/var/lib/mpd/recorder/mpd.ogg”
##    quality        “5.0”            # do not define if bitrate is defined
#    bitrate        “128”            # do not define if quality is defined
#    format        “44100:16:1”
#}
#
# An example of a httpd output (built-in HTTP streaming server):
#
#audio_output {
#    type        “httpd”
#    name        “My HTTP Stream”
#    encoder        “vorbis”        # optional, vorbis or lame
#    port        “8000”
#    bind_to_address    “0.0.0.0”        # optional, IPv4 or IPv6
##    quality        “5.0”            # do not define if bitrate is defined
#    bitrate        “128”            # do not define if quality is defined
#    format        “44100:16:1”
#    max_clients    “0”            # optional 0=no limit
#}
#
# An example of a pulseaudio output (streaming to a remote pulseaudio server)
#
audio_output {
    type        “pulse”
    name        “My Pulse Output”
#    server        “remote_server”        # optional
#    sink        “remote_server_sink”    # optional
}
#
## Example “pipe” output:
#
#audio_output {
#    type        “pipe”
#    name        “my pipe”
#    command        “aplay -f cd 2>/dev/null”
## Or if you’re want to use AudioCompress
#    command        “AudioCompress -m | aplay -f cd 2>/dev/null”
## Or to send raw PCM stream through PCM:
#    command        “nc example.org 8765”
#    format        “44100:16:2”
#}
#
## An example of a null output (for no audio output):
#
#audio_output {
#    type        “null”
#    name        “My Null Output”
#    mixer_type      “none”            # optional
#}
#
# This setting will change
all decoded audio to be converted to the specified
# format before being passed to the audio outputs. By default, this setting is
# disabled.
#
#audio_output_format        “44100:16:2”
#
# If MPD has been compiled with libsamplerate support, this setting specifies
# the sample rate converter to use.  Possible values can be found in the
# mpd.conf man page or the libsamplerate documentation. By default, this is
# setting is disabled.
#
#samplerate_converter        “Fastest Sinc Interpolator”
#
###############################################################################

# Normalization automatic volume adjustments ##################################
#
# This setting specifies the type of ReplayGain to use. This setting can have
# the argument “off”, “album” or “track”. See
# for more details. This setting is off by default.
#
#replaygain            “album”
#
# This setting sets the pre-amp used for files that have ReplayGain tags. By
# default this setting is disabled.
#
#replaygain_preamp        “0”
#
# This setting enables on-the-fly normalization volume adjustment. This will
# result in the volume of all playing audio to be adjusted so the output has
# equal “loudness”. This setting is disabled by default.
#
volume_normalization        “yes”
#
###############################################################################

# MPD Internal Buffering ######################################################
#
# This setting adjusts the size of internal decoded audio buffering. Changing
# this may have undesired effects. Don’t change this if you don’t know what you
# are doing.
#
audio_buffer_size        “2048”
#
# This setting controls the percentage of the buffer which is filled before
# beginning to play. Increasing this reduces the chance of audio file skipping,
# at the cost of increased time prior to audio playback.
#
#buffer_before_play        “10%”
#
###############################################################################

# Resource Limitations ########################################################
#
# These settings are various limitations to prevent MPD from using too many
# resources. Generally, these settings should be minimized to prevent security
# risks, depending on the operating resources.
#
#connection_timeout        “60”
#max_connections        “10”
#max_playlist_length        “16384”
#max_command_list_size        “2048”
#max_output_buffer_size        “8192”
#
###############################################################################

# Character Encoding ##########################################################
#
# If file or directory names do not display correctly for your locale then you
# may need to modify this setting.
#
filesystem_charset        “UTF-8”
#
# This setting controls the encoding that ID3v1 tags should be converted from.
#
id3v1_encoding            “ISO-8859-1”
#
###############################################################################

# SIDPlay decoder #############################################################
#
# songlength_database:
#  Location of your songlengths file, as distributed with the HVSC.
#  The sidplay plugin checks this for matching MD5 fingerprints.
#  See http://www.c64.org/HVSC/DOCUMENTS/Songlengths.faq
#
# default_songlength:
#  This is the default playing time in seconds for songs not in the
#  songlength database, or in case you’re not using a database.
#  A value of 0 means play indefinitely.
#
# filter:
#  Turns the SID filter emulation on or off.
#
#decoder {
#    plugin            “sidplay”
#    songlength_database    “/media/C64Music/DOCUMENTS/Songlengths.txt”
#    default_songlength    “120”
#    filter “true”
#}
#
###############################################################################

~/.ncmpcpp/config

———————————————————
####################################################
## this is example configuration file, copy it to ##
## ~/.ncmpcpp/config and set up your preferences ##
####################################################
#
##### connection settings #####
#
## set it in order to make tag editor and renaming files work properly
#
mpd_host = “127.0.0.2”
#
mpd_port = “6600”
#
mpd_music_dir = “~/Music”
#
#mpd_connection_timeout = “5”
#
mpd_crossfade_time = “2”
#
##### system encoding #####
##
## if you use encoding other than utf8, set it in
## order to handle utf8 encoded strings properly.
##
#
#visualizer_type = “wave” (spectrum/wave)
#visualizer_fifo_path = “/tmp/mpd.fifo”
#
#system_encoding = “”
#
##### delays #####
#
## delay after playlist highlighting will be disabled (0 = don’t disable)
#
#playlist_disable_highlight_delay = “5”
#
## defines how long various messages are supposed to be visible
#
#message_delay_time = “4”
#
##### song format #####
##
## for song format you can use:
##
## %l – length
## %f – short filename
## %F – full filename
## %a – artist
## %t – title
## %b – album
## %y – year
## %n – track number
## %g – genre
## %c – composer
## %p – performer
## %d – disc
## %C – comment
## %r – begin right align
##
## you can also put them in { } and then it will be displayed
## only if all requested values are available and/or define alternate
## value with { }|{ } eg. {%a – %t}|{%f}
##
## text can also have different color than the main window has,
## eg. if you want length to be green, write $3%l$9
##
## available values:
##
## – 0 – default window color (discards all other colors)
## – 1 – black
## – 2 – red
## – 3 – green
## – 4 – yellow
## – 5 – blue
## – 6 – magenta
## – 7 – cyan
## – 8 – white
## – 9 – end of current color
##
## Note: colors can be nested.
##
#
song_list_format = “{$4%a$9 – }{$8%t$9}|{$0%f$9} – {$7(%l)$9}”
#
song_library_format = “{$4%n$9 – }{$0%t$9}|{$4%f$9}”
#
tag_editor_album_format = “{$4(%y)$9 }$7%b$9”
#
browser_playlist_prefix = “$8playlist$9 “
#
selected_item_prefix = “$0”
#
selected_item_suffix = “$9”
#
## colors are not supported for below veriables
#
song_status_format = “{(%f) }{%a – }{%l}”
#
song_window_title_format = “{%f – }{%t}|{%l}”
#
##### columns settings #####
##
## syntax of song columns list format is “column column etc.”
##
## – syntax for each column is:
##
## (width of column in %)[column’s color]{displayed tag}
##
## – color is optional (if you want the default one, type [])
##
#
song_columns_list_format = “(30)[white]{f} (30)[yellow]{a} (30)[white]{b} (10)[yellow]{l}”
#
##### vari
ous settings #####
#
##
## Note: Custom command that will be executed each time song changes.
## It uses the same syntax as song format (for now playing song).
## Useful for notifications etc.
##
#execute_on_song_change = “”
#
#playlist_show_remaining_time = “no”
#
playlist_display_mode = “columns” (classic/columns)
#
browser_display_mode = “classic” (classic/columns)
#
search_engine_display_mode = “columns” (classic/columns)
#
incremental_seeking = “yes”
#
#seek_time = “1”
#
#autocenter_mode = “no”
#
#default_place_to_search_in = “database” (database/playlist)
#
#media_library_left_column = “a” (possible values: a,y,g,c,p, legend above)
#
#default_find_mode = “wrapped” (wrapped/normal)
#
#default_space_mode = “add” (add/select)
#
#default_tag_editor_left_col = “albums” (albums/dirs)
#
#default_tag_editor_pattern = “%n – %t”
#
#header_visibility = “yes”
#
#statusbar_visibility = “yes”
#
#header_text_scrolling = “yes”
#
#fancy_scrolling = “yes”
#
#cyclic_scrolling = “no”
#
follow_now_playing_lyrics = “yes”
#
#ncmpc_like_songs_adding = “no” (enabled – add/remove, disabled – always add)
#
#show_hidden_files_in_local_browser = “no”
#
#display_screens_numbers_on_start = “yes”
#
clock_display_seconds = “yes”
#
#regular_expressions = “basic” (basic/extended)
#
##
## Note: If below is enabled, ncmpcpp will ignore leading
## “The” word while sorting items in browser, tags in
## media library, etc.
##
#ignore_leading_the = “no”
#
#block_search_constraints_change_if_items_found = “yes”
#
mouse_support = “yes”
#
enable_window_title = “no”
#
##
## Note: These triggers will allow you to phisically remove
## files and directories from your hdd in using ncmpcpp’s
## browser screen.
##
#
allow_physical_files_deletion = “no”
#
allow_physical_directories_deletion = “no”
#
##### lyrics support #####
##
## supported lyrics databases:
##
## – 1 – lyricwiki.org
## – 2 – lyricsplugin.com
##
#
lyrics_database = “1”
#
external_editor = “nano”
#
use_console_editor = “yes” (set to yes, if your editor is console app)
#
##### colors definitions #####
#
colors_enabled = “yes”
#
empty_tag_color = “cyan”
#
header_window_color = “white”
#
volume_color = “white”
#
state_line_color = “blue”
#
state_flags_color = “cyan”
#
main_window_color = “white”
#
color1 = “blue”
#
color2 = “cyan”
#
main_window_highlight_color = “red”
#
progressbar_color = “white”
#
statusbar_color = “white”
#
active_column_color = “white”
#
window_border_color = “yellow”
#
active_window_border = “white”
#
——————————————————–

MPC

mpc package use for multimedia keys bindings…
grab here
http://dl.dropbox.com/u/17345407/mpckeybindings