Strictly speaking the file still has not moved. The data bits are still on the same part of the disk where they were in the first place originally. The file specification ( the-directory-path plus the filename) that you use to talk about the file is diffirent so that it appears to have moved , whereas it has not in actuality.
In early versions of Unix , the users were not allowed to use mv to move a file from one disk partition to another , you could only copy it ny using the cp(1) command. Linux allows you to use the mv command to move a file anyplace. Normally , mv leaves the data in place and just changes the file name or the directory where the name is placed. But when the file is moved across the disk partitions ( for example form /usr to /home in a lot of Linux systems) , the data is copied to the new disk partition, the new name is put in place. In that partition’s directory structure, and the name and file data are removed from the old disk partition.
The command for moving and opying directories and files are mv for moving and cp for copy. If you want to rename a file, you can use the move command . No you are not really moving the file, but in both Linux and Unix , the developers realized that renaming something was a lot like moving it .
Hence the format of the move command is my < source> <destination>
With the example files, you could move the file named stupidkirk to a file named evenmorestupid by executing the following command
mv stupidkirk evenmorestupid
This leaves the file in the same directory, but changes its name to evenmorestupid .
Hence the file is not moved - it is just simply renamed .
Next you can try moving the evenmorestupid file to the top of the stupidpeople directory. To do this you first have to move the file up and then move it to the stupidpeople directory.
This can be done with one simple command :
mv evenmorestupid ../ stupidpeople
Lastly note that the destination file uses the ..( or parent) directory designation. This tells Linux to go up one directory level and look for a directory called stupidpeople . and then put the file into that directory with the name stupidpeople, as you did not specify any other name.
Theme hotel rooms are a fun way to add a twist to your next vacation. With a little research, you can find hotel rooms decked out in any number of motifs. From romantic fantasies to family friendly, theme hotel rooms are a popular way to create a very memorable trip.
To find a theme room, do a quick Internet search and consult online travel sites or guidebooks from your local bookstore. You can also find customer reviews for many hotels online. Many travelers find it extremely helpful to read about the experiences of people who have stayed at the hotels they are considering booking.
Some of the most popular theme hotel rooms are centered on romance. For instance, most hotels have special honeymoon suites that are reserved for newly married couples or vacationing lovebirds. These special rooms often come with deluxe amenities such as plush beds with top of the line linens, matching his and her bathrobes, Jacuzzi tubs, complimentary champagne and toasting flutes, fresh flowers, turn down service and even breakfast in bed.
If you’re looking for a fun experience, some hotels and motels offer wacky touches like heart-shaped beds, black lights, and whirlpool tubs in the middle of the room. If you can dream it up, it’s probably out there.
For family fun, consider booking theme rooms that the kids will get a kick out of. You can find everything from hotel rooms decorated like pirate ships to rooms featuring favorite children’s cartoon characters.
If you’re traveling to a tropical resort location, you can probably find hotels that offer island themed rooms, adorned with wicker furniture, stuffed parrots and nautical artifacts. Many kids love staying in these rooms because it feels like more of an adventure, and parents love it because it keeps the children entertained and also educates them about their surroundings.
If you want to book a theme room, you might want to seek out hotels that also offer themed entertainment. Mom and dad can enjoy a relaxing day at the beach while the kids join a treasure hunt, participate in a dance contest, or enjoy some other organized activity.
Many decisions and opinions in the Linux world are justified by the idea that the decision will help attract new users to Linux, but why should anyone care at all if other people use Linux? KillaGeorge recently posed the question directly in response to a recent post, titled “A Simple Feature of Ubuntu 8.04 That Could Be So Important:”
“I always wondered why linux users are always trying to convert microsoft users. Whats the deal with that? Who cares what other people use. I use linux and i’m happy with it. If my friends dont want to use it then no sweat of my back. Who cares?”
The main reason for wanting more users to switch to Linux is that the more people use an operating system, the better it will be supported by hardware and software companies and, in the case of open-source software, there will also be more people to develop the operating system. In fact, a good example of this showed up earlier today.
With AMD open-sourcing their graphics drivers, many people are looking to nVidia to see if they will follow suit. Earlier today, an open letter to nVidia was posted that has already received 547 signatures at this time, yet even if this number grows to 1,000 or more, nVidia may still never respond. With Linux’s current market share, nVidia can continue to ignore people for as long as they want. That does not mean they will, but even if nVidia listens, they are only one of many companies that do not have open-source drivers or do not have Linux drivers at all. If Linux had a larger market share, companies would finally have to pay attention to the Linux world and release drivers for Linux.
Unfortunately, the issue is not as simple as more users being better. If Linux ever achieved a large market share, it would become the target of viruses, much like Windows is now. The question is how to find the perfect balance, so that Linux is widely supported, but not the target of viruses and spyware. Right now, Windows is obviously far over that perfect marketshare and Linux is way under. The closest may be the Mac, since most companies do support OS X, but, so far, there are no viruses for OS X in the wild. If you think I am advocating everyone switch to OS X, however, you are wrong. Apple has no intention of stopping their growth. Any day now the viruses will start to come for the Mac and each day it just gets more and more likely.
Hopefully this will not happen to Linux, but it seems hard to escape. Once an operating system gains enough momentum to make it to a significant market share, it is unlikely to stop and no matter what you tell me about the security of Linux, someone will find a way around that security. Perhaps Linux will really find a way to avoid this .
In my last post, I showed how the vulnerability counts for Ubuntu Dapper LTS were lower than Windows Vista. However, I also mentioned that this should be used only to counter Microsoft FUD, and not as a measure of security. What, then, shows that Linux is actually more secure than Windows.
To answer this, we first have to look at what security actually is. Too many people make the mistake of calling a product secure, e.g Linux is more secure than Windows, Opera is more secure than IE etc. Now, security is not a product. It is a process with the user in a central role. Security is a state to be actively attained by proper interaction of the user and the software. Vulnerability patch management is just an important part of this process. What are perhaps more important are proper tools for patch management, stronger defaults and a multilayered approach to security keeping in mind the practical security scenario for that particular software, with the user forming both the first and last line of defence.
With this is mind, I turn to the reasons why an educated user using a Linux distro is in general more secure than while using Windows:
Much better patch management tools: In Windows, the automated update procedure just updates the components supplied by Microsoft. No third party applications are patched. Now, third party applications make up the bulk of the security vulnerabilities. Using Real player? You have to update separately. Using Flash? Update separately. So, for all applications, you have to regularly check for updates for each and every software. This is extremely cumbersome, (though, fortunately, this experience is made tolerable by use of the Secunia PSI) and most users just forget to do it. In Linux, you have automated update system which will update all your software. In Ubuntu, any product you have downloaded, if present in the repository, will be updated at the single click of a mouse. In other distros, if the downloaded software is not present in the repository provided by the distro, adding the product repository is a one time process. This greatly increases user compliance in staying fully updated.
Much stronger default configuration: Linux was designed to be a multi-user system. Therefore, the underlying system files will remain protected even if the user is compromised. If, unfortunately, any remote code execution takes place, it will only take place locally. This is to be contrasted to Windows XP, where the user logs in as administrator by default, and any compromise takes on a system wide character. Windows Vista has also moved to a limited user account by default, and therefore is more secure than its predecessor.
Modular Design: Linux is modular by design, that is, any system component may be removed if unnecessary. As a result, if the user feels that a part of the system is more insecure, he or she may remove that component. The same cannot be said of the Windows system. e.g If I feel that Firefox is the most vulnerable part of my Linux distro, I may remove it completely and replace it with another browser, say, Opera. In Windows, I cannot remove Internet Explorer.
Better tools to protect against zero-day attacks: It is not always sufficient to keep oneself fully patched. Zero-day attacks (an attack where the exploit code is released before the vendor patches the vulnerability) are increasingly becoming common. One study has also shown that it takes only six days for crackers to release exploits, it takes vendors much longer to release them. Therefore, a sensible security policy will make provisions for zero-day attacks. Windows XP has no such provision. Vista, in protected mode, though useful, provides only limited protection to Internet Explorer Attacks. Contrast it to the protection provided by AppArmor or SELinux, both of which provide finely granular protection against any types of remote code execution attacks. It is increasingly becoming common for Distros to ship with AppArmor (e.g SuSE, Ubuntu Gutsy) or SELinux(Fedora, Debian Etch, Yellow Dog) by default. In others, they can be downloaded from the repositories (e.g AppArmor in Mandriva 2008)
Open Source Architecture: In Linux, it is mostly “What you see is what you get” as far as security is concerned. The Open code means that vulnerabilities are seen by “many eyes” and fixed as fast as possible. What, more importantly, this also means, is that there is no scope to hide the patched vulnerabilities, there are no hidden fixes. The user, if motivated, may find out the security issues known for his Operating System, and take precautionary measures against potential exploits, even if the vulnerabilities are not patched. In the Windows world, however, many security issues are hidden. Internally found flaws are not publicly released, and the vendor waits for a major update or service pack to patch silently. While this may lead to lesser vulnerability counts, and better publicity using flawed statistics, this keeps the user in ignorance. As a result, an user may not patch a system if he finds that he is not vulnerable to the reported vulnerabilities, while he may, in reality, be affected by a hidden patch.
Diverse Environment: The Windows environment has been likened to a monoculture. There is great homogeneity which makes it easier for crackers to write exploit code, viruses and the like. Compare this to the Linux world. Here, a program can be a .deb, .rpm, or source code, to name a few. This heterogeneity makes it difficult for crackers to have the widespread impact that is possible on Windows
The basis of the planning was to lay the foundation for a Linux that could deliver complete customer orientated solutions - across a range of vendors and suppliers. In essence many of these same vendors were competitors either for product software applications or services. That was both a challenge and a bonus. It was all in their best interests - both from a software flexibility , development and customer satisfaction viewpoint to provide the most stable , flexible and modifiable Linux base platform.
This is the situation that a United Linux framework came into play. The aim of the United Linux project was to address all of these crucial areas of software and customer satisfaction areas of concerns as well as to provide base flexibility and stability of the Linux operating system , systems and applications. Linux had to be all thing to all people and customers as well as provide a most stable , and secure application level standards.
The aim was to provide a mechanism of a single point contact by which IHV’s and ISV’s could get dependent drivers , utilities into a commercial LSB compliant OS implementation.
OEM Software Shack - Offers discount prices on OEM, license, upgrade, and retail versions of software from brand names like Microsoft, Corel, Symantec, and Adobe.
A minimum set of functionality and the mode of implementation was needed to be shared with all Linux compliant platforms. What the LSB specification which was set for linux distributions was set up to define was a common specification for Linux institutions for all the major Linux distributions and applications. THE LSB had the support of all the major distribution makers.
What the LSB did not do what to define how the semantics of installation and additional functionality should have been delivered and then provide a framework as how additional functionality was to be planned for and delivered . It was to provide a complete customer orientated solution. If Linux was to serve the mainstream business and corporate business client it had to have a solid foundation to be built upon which specifically tailored solutions , for either specific industries , applications or clients could be developed upon.
It had to be solid , substantial and rock solid whatever programs and applications were to devised and developed.
If this sounded very familiar , it is because this point had been reached in Linux to some degrees. At the heart of the United Linux project as well as other Linux distro projects was the Linux Standard Base (LSB) which was set up to define common specifications for Linux distributions ( Linux distros) and Linux application programs. The LSB had the support of all the major Linux makers. Its stated aim was to develop and promote a set of standards that would promote compatibility among Linux distributions and enable the software applications to run on any compliant Linux systems. The stage was set for a major computer OS software platform for functionality and some standardizations.
This was a fairly big overlap , for the United Linux project, but it went a lot further. The LSB specification covered the Linux application programming interface with a view to allowing software and project developers to create applications that could well be deployed across all LSB compliant operating system platforms.
On top of this the United Linux participants were to include supplementary media which would of provided easy opportunities which would allow easy configuration and even branding of the distributions look feel install applications and value added services. The obvious point in this was - apart from the branding is that each of partners could produce task or region or regions specific offerings that still adhered to the United Linux overall specifications and specs .
The first part of the plan was for the four partners to pool their development resources to create the U.I. ( United Linux) core. This was a single CD containing the basics of the operating system drivers and at that time a state of the art linux installation program. The whole distro was meant to be an enterprise grade solution , which as a start was based around SUSE’s enterprise Linux Server product of the time. The core application itself was based on work already completed by the Linux Standard Base of that time and was to be compliant of the then current standards for things like web services. authentication and file system hierarchy , it was intended in the first instance on x86-32 , IA64 , and X86-64 platforms and was aimed predominantly at business users and useage