Linux

It is a kernel version that enables realtime.

The Linux kernel itself does not include a GUI. However, most Linux distributions have one.

Yes, Linux have a GUI.Today many kind of vendor available in Linux Like Redhat fedora,Ubuntu,Suse, Mandriva and many more. Those Linux version provide Cmd and GUI mode for work.

Microsoft

While any unassigned and high level port could be used for SSH it is typically assigned to port 22 on a standard setup.

You would need to set up forwarding on that port on your router to the internal IP address in question.

The default runlevel is specified in /etc/inittab. There is no universally accepted runlevel that is specified as the "default." Red Hat and Fedora use 3 or 5, Ubuntu uses 2, Mandriva and SUSE use 5, and Gentoo uses 3. Some (a relatively small number) Linux distros do not use a SysV init style, and thus have no runlevels at all.

Linux began its life in mid-1991, and reached 1.0 in 1994.

The current version of the Linux kernel is 2.6, which came to its first release in 2003, though the most up to date 2.6 kernels don't resemble the original 2.6 kernel much. To the point the first two version numbers are pretty meaningless. As for the rest... the third number increments and the kernel gets a feature release every 3 months, which will introduce some new features, change others, and remove some. The fourth number will release frequently, but with no set pattern aside from the patch being "ready." Patch releases are purely for bug fixes.

There are older versions of the kernel available effectively for long term support purposes. They are often considered very stable and will generally only be used on servers and distributions without a very rapid release schedule.

Current stable kernel version: 2.6.38.5.

Most applications are available at your distribution's repositories, however depending on the kind of distribution, you may have the option to use user-created repositories that allow you to use applications or dependencies that offer features the official packages do not have, or that the official packages are not offered due to legal issues (some distributions have a strict policy against including non-free/proprietary software in their repositories).

Windows costs money, but Ubuntu is Linux-based and free. Ubuntu is one of many distributions, or versions, of Linux. Personally, I like Linux better than Windows but Windows programs can't run natively on Linux (and vice versa) so many Linux users still use windows because they need to run certain programs. Compatibility/"emulation" (in quotes because it isn't true emulation) is available in the form of the Linux program WINE (stands for WINE Is Not an Emulator). Linux, in general, is not intended for those who are not experienced with computers, and the sterotypical Linux users are computer programmers. However, several more recent distributions have broken this mold, including Ubuntu. Ubuntu is a very user-friendly distribution, and an excellent place for someone curious about starting with Linux to start. Personally, I prefer the distribution openSuSe, but it requires a slightly higher experience level with Linux to use effectively.

Yes. The KDE 4 desktop includes desktop widgets / gadgets.

There are a few differences.

1. In Windows, each seperate filesystem is accessed independently of the other through drive letters. In Linux, each seperate filesystem gets mounted and integrated into one unified filesystem tree.

2. Windows only really supports a few filesystems, primarily NTFS. Linux supports a wide range of filesystems: ext2, ext3, ext4, btrfs, zfs, jfs, reiserfs, ntfs, etc.

3. Both are capable of supporting loadable filesystem drivers, but Linux has better support for it by far. Also, Linuxhas a filesystem driver called "FUSE" which allows filesystems to be made available through userspace.

4. Linux makes use of pseudofilesystems. Windows doesn't. Because Linux follows the Unix philosophy of everything being a file, Linux can abstract a great deal of things into filesystems, and already does for /dev, /proc, and /sys.

5. Linux core file permissions are more simple but usually more effective than Windows'. The vanilla Linux permissions have three contexts: User, Group, and Others, with three permissions for each: Read, write, and execute. Furthere, three special permissions applied to the file globally, sticky, suid, and guid.

6. Linux has full linking capability, both hard and soft links. Windows has a pretty limted linking capability, bt most users will end up using the "shortcuts" system instead, which is not so capable. With Linux, soft links behave for all intents and purposes as if they *are* the file or directory they point to, meaning even most software apps will make use of them as if they are the real thing, something that cannot be said for Windows shortcuts, which for the most part are almost completely ignored by most software. Finally, a note on hard links: Hard links are different from soft links in that they actually ARE the file itself. Hard links are an actual inode (Filesystem metadata.) reference to the file data itself, virtually indistinguishible from the "original" file. This is not the same as a copy, as a copy actually is that, a copy, where the data is actually duplicated. In this case it quite literally is the file or directing existing in multiple places at the same time on the filesystem. The disadvantage is that hard links do not work across filesystems, largely because an inode cannot really know the contents of another filesystem without a lot of outside help, such as RAID.

7. Windows fragments a lot. Linux hardly fragments unless there's chronic space problems or lots of saving and deleting. This is largely based on how the two operating systems format their filesystems. For the most part, no OS really has the same sort of control over where any data is physically placed on a disk, as the hard disk controller itself, but an OS can influence where the data is placed based on the data structures they specify to the hard disk controller. This problem is far less pronounced in Windows as it used to be, however.

8. Windows doesn't provide any real native loop interfacing with virtual media, such as disk images. Linux does, in the "loop" driver, allowing one to store an entire filesystem in a normal file and mount it as if it were a disk. Windows has third party utilities that can do this, but most of them only support ISO images. This allows Linux to give users handy ways to encrypt and store data in ways Windows can't even begin to approach.

9. Finally, swap space: Windows and Linux approach this in fundamentally different ways. Windows uses a file to store swap data right on the system partition, allowing it to grow and shrink, contributing to overall fragmentation. Linux, on the other hand, Makes an entire partition for swap data. Though in many cases with RAM being as large as it is today and the level in which Linux kees its memory usage down many Linux users don't use swap at all. Linux *can* deploy a swap file like Windows using the loop interface mentioned above, but it's really just better to set aside about 5 GiB of your hard disk to swap (Hard disks are large and cheap, so dedicated swap space is hardly costly to most users.

The source of the Linux kernel, as well as most programs that run on it, is publicly available. You can edit the source with any text editor, although you may prefer one with syntax highlighting. The configuration files necessary to actually operate Linux are also editable with a standard text editor.

GNU doesn't regulate anything.

The GPL, on the other hand, requires that if you redistribute Linux with your modifications, that you make the source code of your modifications available as well.

Keep in mind this only applied to DISTRIBUTION. In-house/personal-use stuff you are literally unrestricted and can even keep modifications to yourself.

To make this a little less confusing, consider this:

1. Distributor X makes Y modification to Linux.

2. X sends out Linux with Y modification and has to make Y available openly without restriction.

3. End user Z gets Linux with Y.

4. Z modifies Linux with Y with further modification W.

5. Because Z is not sharing Linux with modifications Y and W, he doesn't have to share W at all.

A more real world example:

1. nVidia makes an excellent proprietary driver for their video cards on Linux.

2. Because the driver is proprietary, this driver cannot be included with the kernel tree itself.

3. Instead, the end user typically has Linux installed with a kernel and has to download and install the driver themselves, typically over their distribution's repositories.

There used to be a debate about whether this driver violates the GPL anyway over "derived works" clauses, though even the FSF (Responsible for the GPL and its terms.) has pretty much held there is no such violation.

Further, the GPL, being a license and not a law, cannot take away the rights of the OWNER of the copyright. If I am the sole owner of code I have licensed under the GPL, the GPL can't stop me at all from relicensing the whole shebang under a proprietary commercial license. Some companies, such as Canonical, even have "copyright reassignment" agreements with contributors that legally transfers copyright from the modder to Canonical and it won't violate the GPL, however a lot of people find this shady and against the spirit of free software.

Still, because of this, if you're sole copyright holder and want to include proprietary code with your work, you won't be able to use the GPL without violating it, though technically a copyright holder cannot violate their own copyright. I am unsure if the GPL can stop a copyright holder from including proprietary software of their own creation directly into GPL code of their own creation, but it would definitely stop anyone else from redistributing the whole package themselves unless they remove the proprietary parts.

Linus Torvalds wanted a Unix operating system for his new 80386 PC. Almost all versions of Unix cost several thousand dollars, and only a couple could really use the features of the 80386 processor. So he decided to write his own.

TCP/IP v4

TCP/IP v6

IPX

AppleTalk

If you mean on the command line, then the command is:

clear

Of course, if your encoding's been messed up, you can also clear up this little problem with the command:

reset

ifconfig

Using man ls will open the manual page for the ls command. The ls command lists the files and folders in the current directory.

First, you "unmount" it, but leave it plugged in. This is the equivalent of "Safely Remove Device" in Windows. you can unmount it using the command

umount /dev/sdx

"x" can be any letter, but it will usually be "f" for the first Flash drive plugged in. You can view the mounted devices by using the command

mount

This will return a result like:

/dev/sdf on /media/disk type vfat (rw,nosuid,nodev,uhelper=hal,uid=1000,codepage=437,iocharset=utf8)

for the Flash drive.

To format it, execute the command

mkfs.vfat /dev/sdx

You can then remount the device.

It would really depend on the machine you are using. If it has an x86-compatible processor, probably. Otherwise, no. The ASUS Eee PC would be an example of a device that often comes with Linux, but can run Windows as well. A cell phone or PDA would be an example of a device that this would probably not be possible for.

That depends on what you are using to download them, and where said program is specified to download them to. Mozilla Firefox, for instance, usually defaults to the desktop (/home/username/Desktop).

First, open terminal (bash prompt).

You must be login as root user to run any one of the following command.

Remove Software under Red Hat / RHEL / Fedora / CentOS Linux

Use rpm or yum command to delete the software.

To list the installed software type

rpm -qa | less

rpm -qa {software-name}

yum list | less

yum list {software-name}

To get information about httpd package, enter:

rpm -qa httpd

yum list httpd

To remove a software use rpm or yum command as follows

rpm -e {software-name}

yum remove {software-name}

To delete a package called httpd, enter:

rpm -e httpd

yum remove httpd

Delete / Uninstall Software Under Debian / Ubuntu Linux

To list installed software type:

dpkg --list

dpkg --list | less

dpkg --list | grep apache

To delete the software, enter:

sudo apt-get remove {package-name}

sudo apt-get remove apache