Q. If the file name is lengthy can it allow your file to become corrupt? Also do spaces open it up for corruption? IE - "01 15 2008 Red table cloth on wooden desk" as opposed to "01152008Redtableclothonwoodendesk"?
A. I'm a network engineer with 30 years of experience. The answer is YES.
It does depend on a lot of factors. The OS, the version of the OS and the network type (if involved) and the version of the network client (again if a network is involved).
If we go back to MS DOS 4 or Novell Netware 4.0x then you can create a condition which believe it or not was knows as the worlds first NATURALLY BORN computer virus. This was done by creating a file with the extended ascii character number 255 (the DEL character). What happens is the older OS's and NOS's would read the characters as ASCII instead of binary. Everytime a virus scanner would attempt to read the file, or backup software would attempt to back it up, it would treat it as ASCII and would actually delete data that followed it. Just like typing to the screen ascii character 7 will play a bell sound.
In the more modern OS's and NOS's there is a maximum length to a filename, and the entire path is considdered part of the filename. this is why you can do a CUT/PASTE operation very quickly. It in effect simply renames the file/path if its on the same volume. But a copy operation or a paste to another volume must duplicate all the information. Just because your filename is only 20 characters, you can still be over the limit if the full length of the path combined with the filename is over the max, which I believe is currently 252 characters. Spaces are just as valid as characters as any letter or number so they DO contrinute to the problem.
The good news is, that this can usually be corrected by renaming it, or shortening the path. This can be tricky sometimes, but work with your network administrator and they can help out.
I hope this helped.
It does depend on a lot of factors. The OS, the version of the OS and the network type (if involved) and the version of the network client (again if a network is involved).
If we go back to MS DOS 4 or Novell Netware 4.0x then you can create a condition which believe it or not was knows as the worlds first NATURALLY BORN computer virus. This was done by creating a file with the extended ascii character number 255 (the DEL character). What happens is the older OS's and NOS's would read the characters as ASCII instead of binary. Everytime a virus scanner would attempt to read the file, or backup software would attempt to back it up, it would treat it as ASCII and would actually delete data that followed it. Just like typing to the screen ascii character 7 will play a bell sound.
In the more modern OS's and NOS's there is a maximum length to a filename, and the entire path is considdered part of the filename. this is why you can do a CUT/PASTE operation very quickly. It in effect simply renames the file/path if its on the same volume. But a copy operation or a paste to another volume must duplicate all the information. Just because your filename is only 20 characters, you can still be over the limit if the full length of the path combined with the filename is over the max, which I believe is currently 252 characters. Spaces are just as valid as characters as any letter or number so they DO contrinute to the problem.
The good news is, that this can usually be corrected by renaming it, or shortening the path. This can be tricky sometimes, but work with your network administrator and they can help out.
I hope this helped.
Whats the difference between Linux and Windows?
Q. Whats the difference between Linux and Windows?
Would you highly reccomend Linux?
What are some of the features?
Would you highly reccomend Linux?
What are some of the features?
A. 1: Full access vs. no accessHaving access to the source code is probably the single most significant difference between Linux and Windows. The fact that Linux belongs to the GNU Public License ensures that users (of all sorts) can access (and alter) the code to the very kernel that serves as the foundation of the Linux operating system. You want to peer at the Windows code? Good luck. Unless you are a member of a very select (and elite, to many) group, you will never lay eyes on code making up the Windows operating system.
#2: Licensing freedom vs. licensing restrictionsAlong with access comes the difference between the licenses. Iâm sure that every IT professional could go on and on about licensing of PC software. But letâs just look at the key aspect of the licenses (without getting into legalese). With a Linux GPL-licensed operating system, you are free to modify that software and use and even republish or sell it (so long as you make the code available). Also, with the GPL, you can download a single copy of a Linux distribution (or application) and install it on as many machines as you like. With the Microsoft license, you can do none of the above. You are bound to the number of licenses you purchase, so if you purchase 10 licenses, you can legally install that operating system (or application) on only 10 machines.
#3: Online peer support vs. paid help-desk supportThis is one issue where most companies turn their backs on Linux. But itâs really not necessary. With Linux, you have the support of a huge community via forums, online search, and plenty of dedicated Web sites. And of course, if you feel the need, you can purchase support contracts from some of the bigger Linux companies (Red Hat and Novell for instance).
However, when you use the peer support inherent in Linux, you do fall prey to time.
On the other side of the coin is support for Windows.
#4: Full vs. partial hardware supportOne issue that is slowly becoming nonexistent is hardware support. Years ago, if you wanted to install Linux on a machine you had to make sure you hand-picked each piece of hardware or your installation would not work 100 percent. I can remember, back in 1997-ish, trying to figure out why I couldnât get Caldera Linux or Red Hat Linux to see my modem. After much looking around, I found I was the proud owner of a Winmodem. So I had to go out and purchase a US Robotics external modem because that was the one modem I knew would work. This is not so much the case now. You can grab a PC (or laptop) and most likely get one or more Linux distributions to install and work nearly 100 percent. But there are still some exceptions. For instance, hibernate/suspend remains a problem with many laptops, although it has come a long way.
With Windows, you know that most every piece of hardware will work with the operating system. Of course, there are times (and I have experienced this over and over) when you will wind up spending much of the day searching for the correct drivers for that piece of hardware you no longer have the install disk for. But you can go out and buy that 10-cent Ethernet card and know itâll work on your machine (so long as you have, or can find, the drivers). You also can rest assured that when you purchase that insanely powerful graphics card, you will probably be able to take full advantage of its power.
#5: Command line vs. no command lineNo matter how far the Linux operating system has come and how amazing the desktop environment becomes, the command line will always be an invaluable tool for administration purposes. Nothing will ever replace my favorite text-based editor, ssh, and any given command-line tool. I canât imagine administering a Linux machine without the command line. But for the end user â not so much. You could use a Linux machine for years and never touch the command line. Same with Windows. You can still use the command line with Windows, but not nearly to the extent as with Linux. And Microsoft tends to obfuscate the command prompt from users. Without going to Run and entering cmd (or command, or whichever it is these days), the user wonât even know the command-line tool exists. And if a user does get the Windows command line up and running, how useful is it really?
#6: Centralized vs. noncentralized application installationThe heading for this point might have thrown you for a loop. But letâs think about this for a second. With Linux you have (with nearly every distribution) a centralized location where you can search for, add, or remove software. Iâm talking about package management systems, such as Synaptic. With Synaptic, you can open up one tool, search for an application (or group of applications), and install that application without having to do any Web searching (or purchasing).
Windows has nothing like this. With Windows, you must know where to find the software you want to install, download the software (or put the CD into your machine), and run setup.exe o
#2: Licensing freedom vs. licensing restrictionsAlong with access comes the difference between the licenses. Iâm sure that every IT professional could go on and on about licensing of PC software. But letâs just look at the key aspect of the licenses (without getting into legalese). With a Linux GPL-licensed operating system, you are free to modify that software and use and even republish or sell it (so long as you make the code available). Also, with the GPL, you can download a single copy of a Linux distribution (or application) and install it on as many machines as you like. With the Microsoft license, you can do none of the above. You are bound to the number of licenses you purchase, so if you purchase 10 licenses, you can legally install that operating system (or application) on only 10 machines.
#3: Online peer support vs. paid help-desk supportThis is one issue where most companies turn their backs on Linux. But itâs really not necessary. With Linux, you have the support of a huge community via forums, online search, and plenty of dedicated Web sites. And of course, if you feel the need, you can purchase support contracts from some of the bigger Linux companies (Red Hat and Novell for instance).
However, when you use the peer support inherent in Linux, you do fall prey to time.
On the other side of the coin is support for Windows.
#4: Full vs. partial hardware supportOne issue that is slowly becoming nonexistent is hardware support. Years ago, if you wanted to install Linux on a machine you had to make sure you hand-picked each piece of hardware or your installation would not work 100 percent. I can remember, back in 1997-ish, trying to figure out why I couldnât get Caldera Linux or Red Hat Linux to see my modem. After much looking around, I found I was the proud owner of a Winmodem. So I had to go out and purchase a US Robotics external modem because that was the one modem I knew would work. This is not so much the case now. You can grab a PC (or laptop) and most likely get one or more Linux distributions to install and work nearly 100 percent. But there are still some exceptions. For instance, hibernate/suspend remains a problem with many laptops, although it has come a long way.
With Windows, you know that most every piece of hardware will work with the operating system. Of course, there are times (and I have experienced this over and over) when you will wind up spending much of the day searching for the correct drivers for that piece of hardware you no longer have the install disk for. But you can go out and buy that 10-cent Ethernet card and know itâll work on your machine (so long as you have, or can find, the drivers). You also can rest assured that when you purchase that insanely powerful graphics card, you will probably be able to take full advantage of its power.
#5: Command line vs. no command lineNo matter how far the Linux operating system has come and how amazing the desktop environment becomes, the command line will always be an invaluable tool for administration purposes. Nothing will ever replace my favorite text-based editor, ssh, and any given command-line tool. I canât imagine administering a Linux machine without the command line. But for the end user â not so much. You could use a Linux machine for years and never touch the command line. Same with Windows. You can still use the command line with Windows, but not nearly to the extent as with Linux. And Microsoft tends to obfuscate the command prompt from users. Without going to Run and entering cmd (or command, or whichever it is these days), the user wonât even know the command-line tool exists. And if a user does get the Windows command line up and running, how useful is it really?
#6: Centralized vs. noncentralized application installationThe heading for this point might have thrown you for a loop. But letâs think about this for a second. With Linux you have (with nearly every distribution) a centralized location where you can search for, add, or remove software. Iâm talking about package management systems, such as Synaptic. With Synaptic, you can open up one tool, search for an application (or group of applications), and install that application without having to do any Web searching (or purchasing).
Windows has nothing like this. With Windows, you must know where to find the software you want to install, download the software (or put the CD into your machine), and run setup.exe o
What kinds of jobs can I realistically expect to get with an A+ Certification?
Q. I'm 27 years old and I'm already up to my eyeballs in debt. I don't have a lot of time or money to go to school, so I'd just like to know what kinds of jobs are available with an A+ Certification. I'd also be willing to get Network+ or CCNA as well, but I can afford neither the time, nor the money to go to school for two whole years.
A. For an A+ you can usually get a tech support or help-desk job to start out. Network+ is a big help too. My experience has been that a CCNA is great to get but you will have a hard time competing with other CCNA's already out there working. If you like to write software you are more likely to get a programming job with less experience (believe it or not) Get a C# or Java book and start cramming. I have been in IT for almost 15 years. A+ then Novell CNA, MCSE, Domino development, PeopleSoft, SQL, C# etc. You are almost better off figuring out what you like to do and then going after it by learning from books or on YouTube. (bunch of good videos)
Hope this helps.
Hope this helps.
Powered by Yahoo! Answers
No comments:
Post a Comment