Articles
Destroy Twitter
Destroy Twitter 1.7.2 Beta
This application built using Adobe AIR, many features to access you twitter account for you tweet, upcoming twitte, massages, replies, also you access search and groups.
I was using Gwibber for a while for multi using for different social network such as ” FaceBook, Friendfeed, Twitter,…”
But I liked Twitter on “Destroy Twitter” more than Gwibber, also there are many application for Twitter Social Network.
Also you can customize your own themes for Destroy Twitter.
Here some screenshots for it and Downloading instruction
Before Downloading you will need to install Adobe AIR Package Here
Website Themes Theme Builder Download
Peace out 
Virtualization on Linux
It’s the best way to run multiple operating systems at same time on your running operating system, in this article I will talk linux virtualization only, but some of these application I will mention works on many operating systems such as “Linux, Macintosh,Windows, …”
Virtualization not just for these operating systems only, also virtualization works on mobile and pocket PCs and I will talk about that on other article.
- Why I want to use virtual machines ?
It’s a really good way run multiple operating system at same time, I use it a lot to try new distributions release like this one I reviewed for ubuntu 10.04 alpha 3 Lucid I was using sun virtual box.
Some users want to use Windows and any linux distribution on same time, not for testing, with complete installation on virtual machine.
Used to use sun virtualbox, KVM, and Virtual machine manager.
1. Sun Virtual Box
VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Not only is VirtualBox an extremely feature rich, high performance product for enterprise customers, it is also the only professional solution that is freely available as Open Source Software under the terms of the GNU General Public License (GPL). See “About VirtualBox” for an introduction.
2. VMWare including “VMware server and player”
VMWare is a commercial virtualization platform that currently offers two free products: VMWare Player and VMWare Server (the latter with a free renewable yearly license). VMWare Player can play virtual appliances that have already been created, whereas VMWare Server (which has a broader range of features) allows the creation of virtual machines. In general, VMWare Server is recommended unless you only need to play an appliance. (Appliances will also run in VMWare Server). Users that wish to run servers (or processes) that need to be available to a network from within the virtual machine should use VMServer. If you wish to install a new OS within a virtual machine (other than in an appliance), you will need VMWare Server.
3. KVM
KVM (for Kernel-based Virtual Machine) is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V). It consists of a loadable kernel module, kvm.ko, that provides the core virtualization infrastructure and a processor specific module, kvm-intel.ko or kvm-amd.ko. KVM also requires a modified QEMU although work is underway to get the required changes upstream.
4. Xen
The Xen® hypervisor, the powerful open source industry standard for virtualization, offers a powerful, efficient, and secure feature set for virtualization of x86, x86_64, IA64, ARM, and other CPU architectures. It supports a wide range of guest operating systems including Windows®, Linux®, Solaris®, and various versions of the BSD operating systems. More
5. QEMU
QEMU is a generic and open source machine emulator and virtualizer.
When used as a machine emulator, QEMU can run OSes and programs made for one machine (e.g. an ARM board) on a different machine (e.g. your own PC). By using dynamic translation, it achieves very good performances.
When used as a virtualizer, QEMU achieves near native performances by executing the guest code directly on the host CPU. QEMU supports virtualization when executing under the Xen hypervisor or using the KVM kernel module in Linux. When using KVM, QEMU can virtualize x86, server and embedded PowerPC, and S390 guests.
http://wiki.qemu.org/Main_Page
6. Virtual machine manager
The “Virtual Machine Manager” application (virt-manager for short package name) is a desktop user interface for managing virtual machines. It presents a summary view of running domains, their live performance & resource utilization statistics. The detailed view graphs performance & utilization over time. Wizards enable the creation of new domains, and configuration & adjustment of a domain’s resource allocation & virtual hardware. An embedded VNC client viewer presents a full graphical console to the guest domain.
A Fresh Look for Ubuntu 10.04 LTS
New fresh look for ubuntu
New themes. Logos, community logos, and boot splash coming soon with next release of ubuntu 10.04 LTS
The new style of Ubuntu is driven by the theme “Light”. We’ve developed a comprehensive set of visual guidelines and treatments that reflect that style, and are updating key assets like the logo accordingly. The new theme takes effect in 10.04 LTS and will define our look and feel for several years.
Files System Directories “Hierarchy” Part 2
Hello guys,
here is the second part of Files system Directories
so here we go:
5. lib
The /lib directory contains those shared library images needed to boot the system and run the commands in the root filesystem, ie. by binaries in /bin and /sbin.
| File | Description |
|---|---|
| libc.so.* | The dynamically-linked C library (optional) |
| ld* | The execution time linker/loader (optional) |
6. media
/media This directory contains subdirectories which are used as mount points for removeable media such as floppy disks, cdroms and zip disks.
Historically there have been a number of other different places used to mount removeable media such as /cdrom, /mntor /mnt/cdrom. Placing the mount points for all removeable media directly in the root directory would potentially result in a large number of extra directories in /. Although the use of subdirectories in /mnt as a mount point has recently been common, it conflicts with a much older tradition of using /mnt directly as a temporary mount point.
| Directory | Description |
|---|---|
| floppy | Floppy drive (optional) |
| cdrom | CD-ROM drive (optional) |
| cdrecorder | CD writer (optional) |
| zip | Zip drive (optional) |
On systems where more than one device exists for mounting a certain type of media, mount directories can be created by appending a digit to the name of those available above starting with ’0′, but the unqualified name must also exist.
7. mnt
Mount point for a temporarily mounted filesystem
/mnt This directory is provided so that the system administrator may temporarily mount a filesystem as needed. The content of this directory is a local issue and should not affect the manner in which any program is run.
This directory must not be used by installation programs: a suitable temporary directory not in use by the system must be used instead.
8. opt
/opt is reserved for the installation of add-on application software packages.
A package to be installed in /opt must locate its static files in a separate /opt/<package> or /opt/<provider> directory tree, where <package> is a name that describes the software package and<provider> is the provider’s LANANA registered name.
9. root
/root Home directory for the root user
The root account’s home directory may be determined by developer or local preference, but this is the recommended default location.
10. sbin
/sbin System binaries
Utilities used for system administration (and other root-only commands) are stored in /sbin, /usr/sbin, and /usr/local/sbin. /sbin contains binaries essential for booting, restoring, recovering, and/or repairing the system in addition to the binaries in /bin. Programs executed after /usr is known to be mounted (when there are no problems) are generally placed into /usr/sbin. Locally-installed system administration programs should be placed into /usr/local/sbin.
11. srv
Data for services provided by this system
/srv contains site-specific data which is served by this system.
This main purpose of specifying this is so that users may find the location of the data files for particular service, and so that services which require a single tree for readonly data, writable data and scripts (such as cgi scripts) can be reasonably placed. Data that is only of interest to a specific user should go in that users’ home directory.
The methodology used to name subdirectories of /srv is unspecified as there is currently no consensus on how this should be done. One method for structuring data under /srv is by protocol, eg. ftp, rsync, www, and cvs. On large systems it can be useful to structure /srv by administrative context, such as /srv/physics/www, /srv/compsci/cvs, etc. This setup will differ from host to host. Therefore, no program should rely on a specific subdirectory structure of /srv existing or data necessarily being stored in /srv. However /srv should always exist on FHS compliant systems and should be used as the default location for such data.
Distributions must take care not to remove locally placed files in these directories without administrator permission.
12. tmp
The /tmp directory must be made available for programs that require temporary files.
Programs must not assume that any files or directories in /tmp are preserved between invocations of the program.
IEEE standard P1003.2 (POSIX, part 2) makes requirements that are similar to the above section.
Although data stored in /tmp may be deleted in a site-specific manner, it is recommended that files and directories located in /tmp be deleted whenever the system is booted.
FHS added this recommendation on the basis of historical precedent and common practice, but did not make it a requirement because system administration is not within the scope of this standard.
13. usr
/usr is the second major section of the filesystem. /usr is shareable, read-only data. That means that /usr should be shareable between various FHS-compliant hosts and must not be written to. Any information that is host-specific or varies with time is stored elsewhere.
Large software packages must not use a direct subdirectory under the /usr hierarchy.
14. var
/var contains variable data files. This includes spool directories and files, administrative and logging data, and transient and temporary files.
Some portions of /var are not shareable between different systems. For instance, /var/log, /var/lock, and /var/run. Other portions may be shared, notably /var/mail, /var/cache/man,/var/cache/fonts, and /var/spool/news.
/var is specified here in order to make it possible to mount /usr read-only. Everything that once went into /usr that is written to during system operation (as opposed to installation and software maintenance) must be in /var.
If /var cannot be made a separate partition, it is often preferable to move /var out of the root partition and into the /usrpartition. (This is sometimes done to reduce the size of the root partition or when space runs low in the root partition.) However, /var must not be linked to /usr because this makes separation of /usr and /var more difficult and is likely to create a naming conflict. Instead, link /var to /usr/var.
Applications must generally not add directories to the top level of /var. Such directories should only be added if they have some system-wide implication, and in consultation with the FHS mailing list.
——————-
that’s it for now
and i will include graphic chart later
Files System Directories “Hierarchy” Part 1
Hello Guys,
In this article I will explain what’s files system directories also it know as Hierarchy.
This article will be really helpful for beginners to know what’s the purpose of each directory and command inside Hierarchy.
So let’s begin,
| Directory | Description |
|---|---|
| bin | Essential command binaries |
| boot | Static files of the boot loader |
| dev | Device files |
| etc | Host-specific system configuration |
| lib | Essential shared libraries and kernel modules |
| media | Mount point for removeable media |
| mnt | Mount point for mounting a filesystem temporarily |
| opt | Add-on application software packages |
| sbin | Essential system binaries |
| srv | Data for services provided by this system |
| tmp | Temporary files |
| usr | Secondary hierarchy |
| var | Variable data |
1. bin
/bin contains commands that may be used by both the system administrator and by users, but which are required when no other filesystems are mounted (e.g. in single user mode). It may also contain commands which are used indirectly by scripts.
2. boot
/boot This directory contains everything required for the boot process except configuration files not needed at boot time and the map installer. Thus /boot stores data that is used before the kernel begins executing user-mode programs. This may include saved master boot sectors and sector map files.
3. dev
The /dev directory is the location of special or device files.
Devices treated like files to read and write it
Example:
- /dev/cdrom
- /dev/hda for first hard driver IDE
If it is possible that devices in /dev will need to be manually created, /dev must contain a command named MAKEDEV, which can create devices as needed. It may also contain a MAKEDEV.local for any local devices.
If required, MAKEDEV must have provisions for creating any device that may be found on the system, not just those that a particular implementation installs.
4. etc
The /etc hierarchy contains configuration files. A “configuration file” is a local file used to control the operation of a program; it must be static and cannot be an executable binary.
It can be edited by hand : ex:
- /etc/fstab
- /et
No binaries may be located under /etc.
The following directories, or symbolic links to directories are required in /etc:
| Directory | Description |
|---|---|
| opt | Configuration for /opt |
| X11 | Configuration for the X Window system (optional) |
| sgml | Configuration for SGML (optional) |
| xml | Configuration for XML (optional) |
Will explain other ten directories on next post
Enter your email address to receive LinuxNov updates
