Killexams.com VCS-257 Dumps and actual Questions
100% actual Questions - Exam Pass Guarantee with lofty Marks - Just Memorize the Answers
VCS-257 exam Dumps Source : Administration of Veritas InfoScale Storage 7.1 for UNIX/Linux
Test Code : VCS-257
Test designation : Administration of Veritas InfoScale Storage 7.1 for UNIX/Linux
Vendor designation : Veritas
: 90 actual Questions
VCS-257 actual exam questions and Answers!
i gain renewed my membership this time for VCS-257 examination. I breathe given my involvement with killexams.com is so vital it isnt always feasible capitulation through not having a membership. im able to simply disagree with killexams.com exams for my examination. just this web site can aid me obtain my VCS-257 accredition and assist me in getting above ninety five% marks inside the examination. You entire are certainly making an outstanding displaying. preserve it up!
it's miles first-rate best to prepare VCS-257 examination with actual test questions.
It turned into very encourging revel in with killexams.Com group. They told me to attempt their VCS-257 examination questions once and neglect failing the VCS-257 examination. First I hesitated to apply the fabric because I horrified of failing the VCS-257 examination. But when I instructed by route of my pals that they used the examination simulator for thier VCS-257 certification exam, i purchased the preparation p.C.. It changed into very cheap. That became the first time that I satisfied to apply killexams.Com training cloth when I were given a hundred% marks in my VCS-257 exam. I simply recognize you killexams.Com team.
Is there a shortcut to lucid VCS-257 exam?
I surpassed VCS-257 certification with ninety one percent marks. Your brain dumps are very much relish actual examination. Thanks in your terrific assist. I will withhold to utilize your dumps for my subsequent certifications. When i used to breathe hopeless that i cant halt up an IT certified; my friend instructed me about you; I tried your on line Training Tools for my VCS-257 examination and become capable of congregate a 91 bring about Exam. I own route to killexams.
I necessity Latest and updated dumps of VCS-257 exam.
I passed this exam VCS-257 today with a 92% score. killexams.com was my main preparation resource, so if you plot to retract this exam, you can totally signify on this VCS-257 questions source. entire information is relevant, the VCS-257 questions are correct. I am very elated with Killexams.com. This is the first time I used it, but now Im confident Ill further back to this website for entire my VCS-257 certification exams
I necessity present day dumps modern-day VCS-257 examination.
I got numerous inquiries timehonored from this aide and made an astounding 88% in my VCS-257 exam. At that point, my companion proposed me to retract after the Dumps aide of killexams.com as a expeditiously reference. It carefully secured entire the core through short answers that were helpful to remember. My next advancement obliged me to select killexams.com for entire my future exams. I was in an issue how to blanket entire the core inside 3-week time.
It is mighty to gain VCS-257 actual exam questions.
The inquiries are legitimate. Basically indistinguishable to the VCS-257 exam which I passed in just 30 minutes of the time. If not indistinguishable, a mighty deal of stuff is very much alike, so you can overcome it provided for you had invested enough planning energy. I was a bit wary; however killexams.com and Exam Simulator has turned out to breathe a solid hotspot for exam readiness illumination. Profoundly proposed. thanks so much.
am i able to find actual exam Q & A of VCS-257 exam?
I passed this examination VCS-257 today with a ninety two% score. killexams.com changed into my primary preparation aid, so if you plot to retract this exam, you may absolutely assume this VCS-257 questions supply. entire data is relevant, the VCS-257 questions are correct. im very joyous with Killexams.com. this is the primary time I used it, but now Im confident ill further back to this website for entire my VCS-257 certification checks
Do you necessity actual qustions and answers of VCS-257 exam to pass the exam?
VCS-257 Exam was my goal for this year. A very long current Years resolution to allot it in replete VCS-257 . I actually thought that studying for this exam, preparing to pass and sitting the VCS-257 exam would breathe just as crazy as it sounds. Thankfully, I found some reviews of killexams.com online and decided to utilize it. It ended up being totally worth it as the bundle had included every question I got on the VCS-257 exam. I passed the VCS-257 totally stress-free and came out of the testing heart satisfied and relaxed. Definitely worth the money, I believe this is the best exam suffer possible.
extraordinary source of first rate VCS-257 intelligence dumps, amend answers.
In the wake of attempting a few aids, I at eventual halted at Dumps and it contained exact answers introduced in a basic route that was precisely what I required. I was battling with topics, when my exam VCS-257 was only 10 day away. I was horrified that I would not gain the capacity to score passing score the basis pass imprints. I at eventual passed with 78% marks without much inconvenience.
Get those VCS-257 actual exam questions and answers! achieve not congregate ripptoday'sf
while my VCS-257 examination became proper beforehand of me, I had no time left and i used to breathe freaking out. i was cursing myself for losing so much time earlier on nugatory cloth however I had to achieve something and therefore I could only considerone component that might store me. Google informed that, the aspect turned into killexams.com. I knew that it had the entire lot that a candidate could require for VCS-257 examination of Veritas and that helped me in accomplishing precise ratingsinside the VCS-257 exam.
Obviously it is arduous assignment to pick solid certification questions/answers assets concerning review, reputation and validity since individuals congregate sham because of picking incorrectly benefit. Killexams.com ensure to serve its customers best to its assets concerning exam dumps update and validity. The vast majority of other's sham report objection customers further to us for the brain dumps and pass their exams cheerfully and effectively. They never trade off on their review, reputation and trait because killexams review, killexams reputation and killexams customer certainty is vital to us. Uniquely they deal with killexams.com review, killexams.com reputation, killexams.com sham report grievance, killexams.com trust, killexams.com validity, killexams.com report and killexams.com scam. In the event that you behold any erroneous report posted by their rivals with the designation killexams sham report grievance web, killexams.com sham report, killexams.com scam, killexams.com dissension or something relish this, simply recollect there are constantly terrible individuals harming reputation of generous administrations because of their advantages. There are a mighty many fulfilled clients that pass their exams utilizing killexams.com brain dumps, killexams PDF questions, killexams hone questions, killexams exam simulator. Visit Killexams.com, their specimen questions and test brain dumps, their exam simulator and you will realize that killexams.com is the best brain dumps site.
Back to Braindumps Menu
200-710 dumps | C9560-656 study guide | P2080-088 study guide | A2180-607 exercise test | HP2-E60 sample test | HP2-B22 exercise exam | JN0-690 questions and answers | 1Z0-450 questions answers | 1T6-303 exam prep | IQ0-100 actual questions | 644-344 free pdf | IBMSPSSMBPDM brain dumps | 9A0-409 exam questions | HP0-242 test prep | 650-304 exercise questions | CLSSYB test questions | HP0-D04 free pdf | NREMT-NRP cheat sheets | 920-352 actual questions | HPE0-J80 VCE |
VCS-257 exam questions | VCS-257 free pdf | VCS-257 pdf download | VCS-257 test questions | VCS-257 real questions | VCS-257 practice questions
Pass4sure VCS-257 Administration of Veritas InfoScale Storage 7.1 for UNIX/Linux exam braindumps with actual questions and exercise software.
killexams.com give latest and avant-garde Pass4sure exercise Test with Actual Exam Questions and Answers for fresh out of the box current syllabus of Veritas VCS-257 Exam. exercise their actual Questions and Answers to help your insight and pass your exam with lofty Marks. They guarantee your pass inside the Test Center, covering each one of the points of exam and enhance your knowledge of the VCS-257 exam. Pass with no doubt with their actual questions.
Are you looking for Veritas VCS-257 Dumps of actual test questions for the Administration of Veritas InfoScale Storage 7.1 for UNIX/Linux test prep? they present most updated and nice VCS-257 Dumps. Detail is at https://killexams.com/pass4sure/exam-detail/VCS-257. they gain got compiled an information of VCS-257 Dumps from actual tests thus allow you to organize and pass VCS-257 exam on the first attempt. simply memorize their VCS-257 and relax. you will pass the test.
killexams.com Discount Coupons and Promo Codes are as under;
WC2017 : 60% Discount Coupon for entire exams on website
PROF17 : 10% Discount Coupon for Orders additional than $69
DEAL17 : 15% Discount Coupon for Orders larger than $99
SEPSPECIAL : 10% Special Discount Coupon for entire Orders
If you are looking for VCS-257 exercise Test containing actual Test Questions, you are at prerogative place. They gain compiled database of questions from Actual Exams in order to aid you prepare and pass your exam on the first attempt. entire training materials on the site are Up To Date and verified by their experts.
killexams.com provide latest and updated exercise Test with Actual Exam Questions and Answers for current syllabus of Veritas VCS-257 Exam. exercise their actual Questions and Answers to help your knowledge and pass your exam with lofty Marks. They ensure your success in the Test Center, covering entire the topics of exam and build your knowledge of the VCS-257 exam. Pass 4 positive with their accurate questions.
100% Pass Guarantee
Our VCS-257 Exam PDF contains Complete Pool of Questions and Answers and Brain dumps checked and verified including references and explanations (where applicable). Their target to assemble the Questions and Answers is not only to pass the exam at first attempt but Really help Your knowledge about the VCS-257 exam topics.
VCS-257 exam Questions and Answers are Printable in lofty trait Study pilot that you can download in your Computer or any other device and start preparing your VCS-257 exam. Print Complete VCS-257 Study Guide, carry with you when you are at Vacations or Traveling and prize your Exam Prep. You can access updated VCS-257 Exam from your online account anytime.
nside seeing the bona fide exam material of the brain dumps at killexams.com you can without a lot of an extend develop your pretension to fame. For the IT specialists, it is basic to enhance their capacities as showed by their drudgery need. They bear it basic for their customers to carry certification exam with the aid of killexams.com confirmed and honest to goodness exam material. For an awesome future in its domain, their brain dumps are the best decision.
A best dumps creating is a basic segment that makes it straightforward for you to retract Veritas certifications. In any case, VCS-257 braindumps PDF offers settlement for candidates. The IT assertion is a faultfinding troublesome attempt if one doesnt find genuine course as obvious resource material. Thus, they gain genuine and updated material for the arranging of certification exam.
It is fundamental to collect to the pilot material in case one needs toward deliver time. As you require packs of time to peek for revived and genuine exam material for taking the IT certification exam. If you find that at one place, what could breathe better than this? Its simply killexams.com that has what you require. You can deliver time and maintain a strategic distance from inconvenience in case you buy Adobe IT certification from their site.
killexams.com Huge Discount Coupons and Promo Codes are as under;
WC2017 : 60% Discount Coupon for entire exams on website
PROF17 : 10% Discount Coupon for Orders greater than $69
DEAL17 : 15% Discount Coupon for Orders greater than $99
OCTSPECIAL : 10% Special Discount Coupon for entire Orders
Download your Administration of Veritas InfoScale Storage 7.1 for UNIX/Linux Study pilot immediately after buying and Start Preparing Your Exam Prep prerogative Now!
VCS-257 Practice Test | VCS-257 examcollection | VCS-257 VCE | VCS-257 study guide | VCS-257 practice exam | VCS-257 cram
Killexams HP0-003 exercise questions | Killexams HCE-5710 free pdf download | Killexams 1Z0-895 examcollection | Killexams C2180-275 brain dumps | Killexams TB0-120 braindumps | Killexams 000-347 cheat sheets | Killexams HPE6-A43 sample test | Killexams 000-773 study guide | Killexams 9L0-610 dump | Killexams COG-122 mock exam | Killexams 9L0-010 study guide | Killexams 920-803 free pdf | Killexams AVA questions answers | Killexams 156-727.77 pdf download | Killexams HP3-029 exercise test | Killexams HP2-K09 free pdf | Killexams HP0-A16 study guide | Killexams 9A0-394 exercise questions | Killexams 000-101 exam prep | Killexams EE0-011 test prep |
killexams.com huge List of Exam Braindumps
Killexams C2020-011 examcollection | Killexams 642-889 study guide | Killexams HP2-B103 free pdf | Killexams 3X0-104 exercise questions | Killexams HP3-C40 exercise test | Killexams S90-01A braindumps | Killexams 922-089 exercise exam | Killexams 650-293 pdf download | Killexams 250-722 exam prep | Killexams 000-614 free pdf | Killexams HP2-T17 brain dumps | Killexams 156-910-70 free pdf download | Killexams 190-522 mock exam | Killexams 500-801 brain dumps | Killexams 70-680 dump | Killexams 000-163 test questions | Killexams 250-251 exam questions | Killexams MB6-894 exercise questions | Killexams CAT-020 actual questions | Killexams 1Z0-599 questions and answers |
Administration of Veritas InfoScale Storage 7.1 for UNIX/Linux
Pass 4 positive VCS-257 dumps | Killexams.com VCS-257 actual questions | https://www.textbookw.com/
January 24, 2000Web posted at: 12:11 p.m. EST (1711 GMT)
by John Bass and James Robinson, Network World Test Alliance
(IDG) -- It entire boils down to what you're looking for in a network operating system (NOS).
Do you want it spare and resilient so you can install it any route you please? Perhaps administration bells and management whistles are what you necessity so you can deploy several hundred servers. Or maybe you want an operating system that's robust enough so that you sleep relish a baby at night?
The generous tidings is that there is a NOS waiting just for you. After the rash of recent software revisions, they took an in-depth peek at four of the major NOSes on the market: Microsoft's Windows 2000 Advanced Server, Novell's NetWare 5.1, Red Hat Software's Linux 6.1 and The Santa Cruz Operation's (SCO) UnixWare 7.1.1. Sun declined their invitation to submit Solaris because the company says it's working on a current version.
Microsoft's Windows 2000 edges out NetWare for the Network World Blue Ribbon Award. Windows 2000 tops the domain with its management interface, server monitoring tools, storage management facilities and security measures.
However, if it's performance you're after, no product came near to Novell's NetWare 5.1's numbers in their exhaustive file service and network benchmarks. With its lightning-fast engine and Novell's directory-based administration, NetWare offers a mighty basis for an enterprise network.
We found the latest release of Red Hat's commercial Linux bundle led the list for flexibility because its modular design lets you pare down the operating system to suit the job at hand. Additionally, you can create scripts out of multiple Linux commands to automate tasks across a distributed environment.
While SCO's UnixWare seemed to lag behind the pack in terms of file service performance and NOS-based administration features, its scalability features bear it a tough candidate for running enterprise applications.
The numbers are in
Regardless of the job you saddle your server with, it has to effect well at reading and writing files and sending them across the network. They designed two benchmark suites to measure each NOS in these two categories. To reflect the actual world, their benchmark tests deem a wide range of server conditions.
NetWare was the hands-down leader in their performance benchmarking, taking first dwelling in two-thirds of the file tests and earning top billing in the network tests.
Red Hat Linux followed NetWare in file performance overall and even outpaced the leader in file tests where the read/write loads were small. However, Linux did not effect well handling great loads - those tests in which there were more than 100 users. Under heavier user loads, Linux had a inclination to desist servicing file requests for a short epoch and then start up again.
Windows 2000 demonstrated impecunious write performance across entire their file tests. In fact, they found that its write performance was about 10% of its read performance. After consulting with both Microsoft and Client/Server Solutions, the author of the Benchmark Factory testing instrument they used, they determined that the impecunious write performance could breathe due to two factors. One, which they were unable to verify, might breathe a possible performance problem with the SCSI driver for the hardware they used.
More significant, though, was an issue with their test software. Benchmark Factory sends a write-through flag in each of its write requests that is suppositious to reason the server to update cache, if appropriate, and then obligate a write to disk. When the write to disk occurs, the write muster is released and the next request can breathe sent.
At first glance, it appeared as if Windows 2000 was the only operating system to homage this write-through flag because its write performance was so poor. Therefore, they ran a second round of write tests with the flag turned off.
With the flag turned off, NetWare's write performance increased by 30%. This test proved that Novell does indeed homage the write-through flag and will write to disk for each write request when that flag is set. But when the write-through flag is disabled, NetWare writes to disk in a more efficient manner by batching together contiguous blocks of data on the cache and writing entire those blocks to disk at once.
Likewise, Red Hat Linux's performance increased by 10% to 15% when the write-through flag was turned off. When they examined the Samba file system code, they found that it too honors the write-through flag. The Samba code then finds an optimum time during the read/write sequence to write to disk.
This second round of file testing proves that Windows 2000 is matter on its file system cache to optimize write performance. The results of the testing with the write-through flag off were much higher - as much as 20 times faster. However, Windows 2000 silent fell behind both NetWare and RedHat Linux in the file write tests when the write-through flag was off.
SCO honors the write-through flag by default, since its journaling file system is constructed to maximize data integrity by writing to disk for entire write requests. The results in the write tests with the write-through flag on were very similar to the test results with the write-through flag turned off.
For the network benchmark, they developed two tests. Their long TCP transaction test measured the bandwidth each server can sustain, while their short TCP transaction test measured each server's capacity to wield great numbers of network sessions with diminutive file transactions.
Despite a impecunious showing in the file benchmark, Windows 2000 came out on top in the long TCP transaction test. Windows 2000 is the only NOS with a multithreaded IP stack, which allows it to wield network requests with multiple processors. Novell and Red Hat impart they are working on integrating this capability into their products.
NetWare and Linux besides registered tough long TCP test results, coming in second and third, respectively.
In the short TCP transaction test, NetWare came out the lucid winner. Linux earned second dwelling in spite of its necessity of advocate for abortive TCP closes, a method by which an operating system can quickly split down TCP connections. Their testing software, Ganymede Software's Chariot, uses abortive closes in its TCP tests.
Moving into management
As enterprise networks grow to require more servers and advocate more halt users, NOS management tools become crucial elements in keeping networks under control. They looked at the management interfaces of each product and drilled down into how each handled server monitoring, client administration, file and print management, and storage management.
We found Windows 2000 and NetWare provide equally useful management interfaces.
Microsoft Management Console (MMC) is the glue that holds most of the Windows 2000 management functionality together. This configurable graphical user interface (GUI) lets you snap in Microsoft and third-party applets that customize its functionality. It's a two-paned interface, much relish Windows Explorer, with a nested list on the left and selection details on the right. The console is easy to utilize and lets you configure many local server elements, including users, disks, and system settings such as time and date.
MMC besides lets you implement management policies for groups of users and computers using lively Directory, Microsoft's current directory service. From the lively Directory management instrument inside MMC, you can configure users and change policies.
The network configuration tools are found in a sunder application that opens when you click on the Network Places icon on the desktop. Each network interface is listed inside this window. You can add and change protocols and configure, enable and disable interfaces from here without rebooting.
NetWare offers several interfaces for server configuration and management. These tools present duplicate functionality, but each is useful depending from where you are trying to manage the system. The System Console offers a number of tools for server configuration. One of the most useful is NWConfig, which lets you change start-up files, install system modules and configure the storage subsystem. NWConfig is simple, intuitive and predictable.
ConsoleOne is a Java-based interface with a few graphical tools for managing and configuring NetWare. Third-party administration tools can plug into ConsoleOne and let you manage multiple services. They believe ConsoleOne's interface is a bit unsophisticated, but it works well enough for those who must gain a Windows- based manager.
Novell besides offers a Web-accessible management application called NetWare Management Portal, which lets you manage NetWare servers remotely from a browser, and NWAdmin32, a relatively simple client-side instrument for administering Novell Directory Services (NDS) from a Windows 95, 98 or NT client.
Red Hat's overall systems management interface is called LinuxConf and can sprint as a graphical or text-based application. The graphical interface, which resembles that of MMC, works well but has some layout issues that bear it difficult to utilize at times. For example, when you sprint a setup application that takes up a lot of the screen, the system resizes the application larger than the desktop size.
Still, you can manage pretty much anything on the server from LinuxConf, and you can utilize it locally or remotely over the Web or via telnet. You can configure system parameters such as network addresses; file system settings and user accounts; and set up add-on services such as Samba - which is a service that lets Windows clients congregate to files residing on a Linux server - and FTP and Web servers. You can apply changes without rebooting the system.
Overall, Red Hat's interface is useful and the underlying tools are powerful and flexible, but LinuxConf lacks the polish of the other vendors' tools.
SCO Admin is a GUI-based front halt for about 50 SCO UnixWare configuration and management tools in one window. When you click on a tool, it brings up the application to manage that particular in a sunder window.
Some of SCO's tools are GUI-based while others are text-based. The server required a reboot to apply many of the changes. On the plus side, you can manage multiple UnixWare servers from SCOAdmin.
SCO besides offers a useful Java-based remote administration instrument called WebTop that works from your browser.
An eye on the servers and clients
One principal administration job is monitoring the server itself. Microsoft leads the pack in how well you can withhold an eye on your server's internals.
The Windows 2000 System Monitor lets you view a real-time, running graph of system operations, such as CPU and network utilization, and reminiscence and disk usage. They used these tools extensively to determine the sequel of their benchmark tests on the operating system. Another instrument called Network Monitor has a basic network packet analyzer that lets you behold the types of packets coming into the server. Together, these Microsoft utilities can breathe used to compare performance and capacity across multiple Windows 2000 servers.
NetWare's Monitor utility displays processor utilization, reminiscence usage and buffer utilization on a local server. If you know what to peek for, it can breathe a powerful instrument for diagnosing bottlenecks in the system. Learning the sense of each of the monitored parameters is a bit of a challenge, though.
If you want to peek at performance statistics across multiple servers, you can tap into Novell's Web Management Portal.
Red Hat offers the standard Linux command-line tools for monitoring the server, such as iostat and vmstat. It has no graphical monitoring tools.
As with any Unix operating system, you can write scripts to automate these tools across Linux servers. However, these tools are typically cryptic and require a lofty even of proficiency to utilize effectively. A suite of graphical monitoring tools would breathe a mighty addition to Red Hat's Linux distribution.
UnixWare besides offers a number of monitoring tools. System Monitor is UnixWare's simple but limited GUI for monitoring processor and reminiscence utilization. The sar and rtpm command-line tools together list real-time system utilization of buffer, CPUs and disks. Together, these tools give you a generous overall idea of the load on the server.
Along with managing the server, you must manage its users. It's no flabbergast that the two NOSes that ship with an integrated directory service topped the domain in client administration tools.
We were able to configure user permissions via Microsoft's lively Directory and the directory administration instrument in MMC. You can group users and computers into organizational units and apply policies to them.
You can manage Novell's NDS and NetWare clients with ConsoleOne, NWAdmin or NetWare Management Portal. Each can create users, manage file space, and set permissions and rights. Additionally, NetWare ships with a five-user version of Novell's ZENworks tool, which offers desktop administration services such as hardware and software inventory, software distribution and remote control services.
Red Hat Linux doesn't present much in the route of client administration features. You must control local users through Unix leave configuration mechanisms.
UnixWare is similar to Red Hat Linux in terms of client administration, but SCO provides some Windows binaries on the server to remotely set file and directory permissions from a Windows client, as well as create and change users and their settings. SCO and Red Hat present advocate for the Unix-based Network Information Service (NIS). NIS is a store for network information relish logon names, passwords and home directories. This integration helps with client administration.
Handling the staples: File and print
A NOS is nothing without the capacity to participate file storage and printers. Novell and Microsoft collected top honors in these areas.
You can easily add and maintain printers in Windows 2000 using the print administration wizard, and you can add file shares using lively Directory management tools. Windows 2000 besides offers Distributed File Services, which let you combine files on more than one server into a single share.
Novell Distributed Print Services (NDPS) let you quickly incorporate printers into the network. When NDPS senses a current printer on the network, it defines a Printer Agent that runs on the printer and communicates with NDS. You then utilize NDS to define the policies for the current printer.
You define NetWare file services by creating and then mounting a disk volume, which besides manages volume policies.
Red Hat includes Linux's printtool utility for setting up server-connected and networks printers. You can besides utilize this GUI to create printcap entries to define printer access.
Linux has a set of command-line file system configuration tools for mounting and unmounting partitions. Samba ships with the product and provides some integration for Windows clients. You can configure Samba only through a cryptic configuration ASCII file - a staid drawback.
UnixWare provides a resilient GUI-based printer setup instrument called Printer SetUp Manager. For file and volume management, SCO offers a instrument called VisionFS for interoperability with Windows clients. They used VisionFS to allow their NT clients to access the UnixWare server. This service was easy to configure and use.
Windows 2000 provides the best tools for storage management. Its graphical Manage Disks instrument for local disk configuration includes software RAID management; you can dynamically add disks to a volume set without having to reboot the system. Additionally, a signature is written to each of the disks in an array so that they can breathe moved to another 2000 server without having to configure the volume on the current server. The current server recognizes the drives as members of a RAID set and adds the volume to the file system dynamically.
NetWare's volume management tool, NWConfig, is easy to use, but it can breathe a dinky confusing to set up a RAID volume. Once they knew what they were doing, they had no problems formatting drives and creating a RAID volume. The instrument looks a dinky primitive, but they give it lofty marks for functionality and ease of use.
Red Hat Linux offers no graphical RAID configuration tools, but its command line tools made RAID configuration easy.
To configure disks on the UnixWare server, they used the Veritas Volume Manager graphical disk and volume administration instrument that ships with UnixWare. They had some problems initially getting the instrument to recognize the drives so they could breathe formatted. They managed to drudgery around the disk configuration problem using an assortment of command line tools, after which Volume Manager worked well.
While they did not probe these NOSes extensively to expose any security weaknesses, they did peek at what they offered in security features.
Microsoft has made significant strides with Windows 2000 security. Windows 2000 supports Kerberos public key certificates as its primary authentication mechanism within a domain, and allows additional authentication with smart cards. Microsoft provides a Security Configuration instrument that integrates with MMC for easy management of security objects in the lively Directory Services system, and a current Encrypting File System that lets you designate volumes on which files are automatically stored using encryption.
Novell added advocate for a public-key infrastructure into NetWare 5 using a public certificate schema developed by RSA Security that lets you tap into NDS to generate certificates.
Red Hat offers a basic Kerberos authentication mechanism. With Red Hat Linux, as with most Unix operating systems, the network services can breathe individually controlled to augment security. Red Hat offers Pluggable Authentication Modules as a route of allowing you to set authentication policies across programs running on the server. Passwords are protected with a shadow file. Red Hat besides bundles firewall and VPN services.
UnixWare has a set of security tools called Security Manager that lets you set up varying degrees of intrusion protection across your network services, from no restriction to turning entire network services off. It's a generous management time saver, though you could manually modify the services to achieve the identical result.
Stability and foible tolerance
The most feature-rich NOS is of dinky value if it can't withhold a server up and running. Windows 2000 offers software RAID 0, 1 and 5 configurations to provide foible tolerance for onboard disk drives, and has a built-in network load-balancing feature that allows a group of servers to peek relish one server and participate the identical network designation and IP address. The group decides which server will service each request. This not only distributes the network load across several servers, it besides provides foible tolerance in case a server goes down. On a lesser scale, you can utilize Microsoft's Failover Clustering to provide basic failover services between two servers.
As with NT 4.0, Windows 2000 provides reminiscence protection, which means that each process runs in its own segment.
There are besides backup and restore capabilities bundled with Windows 2000.
Novell has an add-on product for NetWare called Novell Cluster Services that allows you to cluster as many as eight servers, entire managed from one location using ConsoleOne, NetWare Management Portal or NWAdmin32. But Novell presently offers no clustering products to provide load balancing for applications or file services. NetWare has an elaborate reminiscence protection scheme to segregate the reminiscence used for the kernel and applications, and a Storage Management Services module to provide a highly resilient backup and restore facility. Backups can breathe all-inclusive, cover parts of a volume or store a differential snapshot.
Red Hat provides a load-balancing product called piranha with its Linux. This package provides TCP load balancing between servers in a cluster. There is no arduous limit to the number of servers you can configure in a cluster. Red Hat Linux besides provides software RAID advocate through command line tools, has reminiscence protection capabilities and provides a rudimentary backup facility.
SCO provides an optional feature to cluster several servers in a load-balancing environment with Non-Stop Clustering for a lofty even of fault-tolerance. Currently, Non-Stop Clustering supports six servers in a cluster. UnixWare provides software RAID advocate that is managed using SCO's On-Line Data Manager feature. entire the standard RAID levels are supported. Computer Associates' bundled ArcServeIT 6.6 provides backup and restore capabilities. UnixWare has reminiscence protection capabilities.
Because their testing was conducted before Windows 2000's general availability ship date, they were not able to evaluate its hard-copy documentation. The online documentation provided on a CD is extensive, useful and well-organized, although a Web interface would breathe much easier to utilize if it gave more than a couple of sentences at a time for a particular aid topic.
NetWare 5 comes with two manuals: a circumstantial manual for installing and configuring the NOS with generous explanations of concepts and features along with an overview of how to configure them, and a diminutive spiral-bound booklet of quick start cards. Novell's online documentation is very helpful.
Red Hat Linux comes with three manuals - an installation guide, a getting started pilot and a reference manual - entire of which are easy to follow.
Despite being the most difficult product to install, UnixWare offers the best documentation. It comes with two manuals: a system handbook and a getting started guide. The system handbook is a reference for conducting the installation of the operating system. It does a generous job of reflecting this painful experience. The getting started pilot is well-written and well-organized. It covers many of the tools needed to configure and maintain the operating system. SCO's online documentation looks nice and is easy to follow.
The bottom line is that these NOSes present a wide range of characteristics and provide enterprise customers with a mighty deal of selection regarding how each can breathe used in any given corporate network.
If you want a good, general purpose NOS that can deliver enterprise-class services with entire the bells and whistles imaginable, then Windows 2000 is the strongest contender. However, for lofty performance, enterprise file and print services, their tests account for that Novell leads the pack. If you're willing to pay a higher cost for scalability and reliability, SCO UnixWare would breathe a safe bet. But if you necessity an inexpensive alternative that will give you bare-bones network services with decent performance, Red Hat Linux can certainly meet the bill.
The selection is yours.
Bass is the technical director and Robinson is a senior technical staff member at Centennial Networking Labs (CNL) at North Carolina situation University in Raleigh. CNL focuses on performance, capacity and features of networking and server technologies and equipment.
Debate will focus on Linux vs. LinuxJanuary 20, 2000Some Windows 2000 PCs will jump the gunJanuary 19, 2000IBM throws Linux lovefestJanuary 19, 2000Corel Linux will sprint Windows appsJanuary 10, 2000Novell's eDirectory spans platformsNovember 16, 1999New NetWare embraces Web appsNovember 2, 1999Microsoft sets a date for Windows 2000October 28, 1999
RELATED IDG.net STORIES:
Fusion's Forum: Square off with the vendors over who has the best NOS(Network World Fusion)How they did it: Details of the testing(Network World Fusion)Find out the tuning parameters(Network World Fusion)Download the Config files(Network World Fusion)The Shootout results(Network World Fusion)Fusion's NOS resources(Network World Fusion)With Windows 2000, NT grows up(Network World Fusion)Fireworks expected at NOS showdown(Network World Fusion)
Note: Pages will open in a current browser window
External sites are not endorsed by CNN Interactive.
Novell, Inc.Microsoft Corp.The Santa Cruz Operation, Inc. (SCO)Red Hat, Inc.
Note: Pages will open in a current browser window
External sites are not endorsed by CNN Interactive.
MOUNTAIN VIEW, CA--(Marketwire - 03/15/11) - Symantec Corp. (NASDAQ:SYMC - News) today announced enhancements to NetBackup 7 that simplify data protection in virtual environments. The latest release introduces Virtual Machine bright Policy technology for VMware environments to automate the discovery and protection of virtual machines while enforcing existing data protection policies. Unlike other data protection solutions, this technology will accelerate the transition to a virtual environment for enterprise organizations deploying a great number of virtual machines or pile a private cloud infrastructure."Virtualization has changed how organizations back up data, and NetBackup continues to evolve to protect their customers' information within virtual environments," said Brian Dye, vice president of product management, Symantec NetBackup. "NetBackup 7 eases the management of protecting and recovering data within physical and virtual environments through a single solution, while reducing data stores with integrated deduplication at the source or media server using NetBackup or NetBackup appliances."Click to Tweet: Symantec @NetBackup expands award-winning advocate for virtual and physical machines with a single solution: http://bit.ly/eZPhBwFor deeper dive into what's current with NetBackup 7, read the following blog post:
In addition to award-winning advocate for virtual machines, NetBackup 7 delivers simplified reporting, faster catastrophe recovery when using NetBackup deduplication, and further supports Oracle and MySQL database applications. Symantec besides offers an easy "one-step" upgrade to NetBackup 7 from older versions, including NetBackup 6.0 and 6.5 to meet the needs of its customers. Symantec NetBackup appliances provide organizations with a expeditiously and proven alternative to upgrade their environment to NetBackup 7.New Features and Benefits:
A faster path to the virtual datacenter: Virtual Machine bright Policy technology adds automation to the discovery and protection of virtual machines and minimizes the administration effort required for lofty performance VMware virtual machine backups through greater awareness of VMware vSphere® resource usage.
50 Percent Faster Virtual Machine Backup: Patented Granular Recovery Technology (GRT), which supports instant file or folder recovery from virtual machine image backups, is now available for Linux systems in VMware environments. This allows customers to reduce comparable virtual machine backup times by up to 50 percent, simplify administration and help the speed of recovery for individual files.
On-Demand Recovery From Anywhere: current auto image replication technology allows customers who replicate data between multiple sites or NetBackup domains to bear the backup data at an alternate site instantly available to NetBackup for faster catastrophe recovery.
Accelerate Recovery: NetBackup RealTime, which provides customers with continuous data protection, now supports VMware environments to purge the backup window, reduce repercussion for very great VMware hosts and enable near-instant recovery of entire systems.
Meet Compliance and Regulatory Requirements: NetBackup 7 now has greater audit trail capabilities to aid backup administrators advocate compliance and regulatory requirements.
Central Control: NetBackup OpsCenter, which delivers a single management view of any Symantec data protection environment, adds improved reports for storage lifecycle policies, audit trails and licensing. current tools, such as the workload analyzer, allow customers to better tailor operations to maximize hardware usage.
Deduplication for Oracle: Enhanced Oracle database agent further improves backup and deduplication performance.
MySQL Support: NetBackup adds a current agent to centralize and automate backup and recovery of MySQL databases.
Client Upgrades Simplified: Improvements to the LiveUpdate capability allow client upgrades for UNIX, Linux and Windows from version NetBackup 6.5 and later from a single policy controlled by the NetBackup administrator.
Connect with Symantec
About Storage from Symantec Symantec helps organizations secure and manage their information-driven world with storage management, email archiving and backup & recovery solutions.About Symantec Symantec is a global leader in providing security, storage and systems management solutions to aid consumers and organizations secure and manage their information-driven world. Their software and services protect against more risks at more points, more completely and efficiently, enabling self-confidence wherever information is used or stored. More information is available at www.symantec.com.NOTE TO EDITORS: If you would relish additional information on Symantec Corporation and its products, please visit the Symantec tidings margin at http://www.symantec.com/news. entire prices famed are in U.S. dollars and are telling only in the United States.Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may breathe trademarks of their respective owners.
This chapter is from the book
If they deem filesystems as a mechanism for both storing and locating data, then the two key elements for any filesystem are the items being stored and the list of where those items are. The deeper details of how a given filesystem manipulates its data and meta-information evanesce beyond the scope of this chapter but are addressed further in Appendix B, "Anatomy of a Filesystem."
Filesystem Components That the Admin Needs to Know About
As always, they necessity to congregate a wield on the vocabulary before they can understand how the elements of a filesystem drudgery together. The next three sections portray the basic components with which you, as a sysadmin, necessity to breathe familiar.
The most intuitively obvious components of a filesystem are, of course, its files. Because everything in UNIX is a file, special functions are differentiated by file type. There are fewer file types than you might imagine, as Table 3.2 shows.
Table 3.2 File Types and Purposes, with Examples
Maintains information for directory structure
Buffered device file
Raw device file
UNIX domain socket
Interprocess communication (IPC)
See output of commands for files Linux: netstat –x Solaris: netstat -f unix
Named pipe special (FIFO device)
First-in-first-out IPC mechanism, Invoked by name
Linux: /dev/initctl Solaris: /etc/utmppipe/etc/cron.d/FIFO
Pointer to another file (any type)
/usr/tmp -> ../var/tmp
All other files; holds data of entire other types
Text files remonstrate files Database files Executables/binaries
Notice that directories are a kind of file. The key is that they gain a specific kind of format and contents (see Appendix B for more details). A directory holds the filenames and index numbers (see the following section, "Inodes") of entire its constituent files, including subdirectories.
Directory files are not flat (or regular) files, but are indexed (like a database), so that you can silent locate a file quickly when you gain a great number of files in the identical directory.13
Even though file handling is generally transparent, it is principal to recollect that a file's data blocks14 may not breathe stored sequentially (or even in the identical general disk region). When data blocks are widely scattered in an uncoordinated manner, it can move access times and augment I/O overhead.
Meta-information about files is stored in structures called index nodes, or inodes. Their contents vary based on the particular filesystem in use, but entire inodes hold the following information about the file they index:15
Inode identification number
Owners: user and group
ctime: eventual file status change time
mtime: eventual data modification time16
atime: eventual access time
Physical location information for data blocks
Notice that the filename is not stored in the inode, but as an entry in the file's closest parent directory.
All other information about a file that ls displays is stored in an inode somewhere. With a few handy options, you can tow out lots of useful information. Let's impart that you want to know the inode number of the Solaris kernel.17 You just give the –i option, and voilá:
[sun:10 ~]ls -i /kernel/genunix
Of course, ls –l is an antediluvian friend, telling you most everything that you want to know. Looking at the Solaris kernel again, you congregate the output in figure 3.4.
Figure 3.4 Diagrammed Output of ls on a File
Notice that the timestamp shown by default in a long listing is mtime. You can pass various options to ls to view ctime and atime instead. For other nifty permutations, behold the ls man page.
File Permissions and Ownership Refresher
Because UNIX was designed to advocate many users, the question naturally arises how to know who can behold what files. The first and simplest reply is simply to permit users to examine only their own files. This, of course, would bear it difficult, if not impossible, to share, creating mighty difficulties in collaborative environments and causing a string of other problems: Why can't I sprint ls? Because the system created it, not you, is only the most obvious instance of such problems.
Users and Groups
UNIX uses a three-part system to determine file access: There's what you, as the file owner, are allowed to do; there's what the group is allowed to do; and there's what other people are allowed to do. Let's behold what Elvis's permissions peek like:
[ elvis@frogbog elvis ]$ ls -l
drwxr-xr-x 5 elvis users 4096 Dec 9 21:55 Desktop
drwxr-xr-x 2 elvis users 4096 Dec 9 22:00 Mail
-rw-r--r-- 1 elvis users 36 Dec 9 22:00 README
-rw-r--r-- 1 elvis users 22 Dec 9 21:59 ThisFile
drwxr-xr-x 2 elvis users 4096 Dec 12 19:57 arc
drwxr-xr-x 2 elvis users 4096 Dec 10 00:40 songs
-rw-r--r-- 1 elvis users 46 Dec 12 19:52 tao.txt
-rw-r--r-- 1 elvis users 21 Dec 9 21:59 thisfile
-rw-r--r-- 1 elvis users 45 Dec 12 19:52 west.txt
As long as we're here, let's wreck down exactly what's being displayed. First, they gain a 10-character string of letters and hyphens. This is the representation of permissions, which I'll wreck down in a minute. The second particular is a number, usually a single digit. This is the number of arduous links to that directory. I'll discuss this later in this chapter. The third thing is the username of the file owner, and the fourth is the designation of the file's group. The fifth column is a number representing the size of the file, in bytes. The sixth contains the date and time of eventual modification for the file, and the final column shows the filename.
Every user on the system has a username and a number that is associated with that user. This number generally is referred to as the UID, short for user ID. If a user has been deleted but, for some reason, his files remain, the username is replaced with that user's UID. Similarly, if a group is deleted but silent owns files, the GID (group number) shows up instead of a designation in the group field. There are besides other circumstances in which the system can't correlate the designation and the number, but these should breathe relatively rare occurrences.
As a user, you can't change the owner of your files: This would open up some staid security holes on the system. Only root can chown files, but if he makes a mistake, you can now question root to chown the files to you. As a user, you can chgrp a file to a different group of which you are a member. That is, if Elvis is a member of a group named users and a group named elvis, he can chgrp elvis west.txt or chgrp users west.txt, but because he's not a member of the group beatles, he can't chgrp beatles west.txt. A user can belong to any number of groups. Generally (although this varies to some extent by flavor), files created belong to the group to which the directory belongs. On most modern UNIX variants, the group that owns files is whatever group is listed as your primary group by the system in the /etc/passwd file and can breathe changed via the newgrp command. On these systems, Elvis can chgrp users if he wants his files to belong to the users group, or he can chgrp elvis if he wants his files to belong to the elvis group.
So, what were those comic strings of letters and hyphens at the nascence of each long directory listing? I already said that they represented the permissions of the file, but that's not especially helpful. The 10 characters of that string represent the leave bits for each file. The first character is separate, and the eventual nine are three very similar groups of three characters. I'll account for each of these in turn.
If you peek back to Elvis's long listing of his directory, you'll behold that most of the files simply gain a hyphen as the first character, whereas several possess a d in this field. The more astute reader might note that the files with a d in that first domain entire betide to breathe directories. There's a generous reason for this: The first permissions character denotes whether that file is a special file of one sort or another.
What's a special file? It's either something that isn't really a file (in the sense of a sequential stream of bytes on a disk) but that UNIX treats as a file, such as a disk or a video display, or something that is really a file but that is treated differently. A directory, by necessity, is a stream of bytes on disk, but that d means that it's treated differently.
The next three characters represent what the user who owns the file can achieve with it. From left to right, these permissions are read, write, and execute. Read leave is just that—the capability to behold the contents of a file. Write leave implies not only the prerogative to change the contents of a file, but besides the prerogative to delete it. If I achieve not possess write leave to a file, rm not_ permitted.txt fails.
Execute leave determines whether the file is besides a command that can breathe sprint on the system. Because UNIX sees everything as a file, entire commands are stored in files that can breathe created, modified, and deleted relish any other file. The computer then needs a route to inform what can and can't breathe run. The execute bit does this.
Another principal reason that you necessity to worry about whether a file is executable is that some programs are designed to breathe sprint only by the system administrator: These programs can modify the computer's configuration or can breathe perilous in some other way. Because UNIX enables you to specify permissions for the owner, the group, and other users, the execute bit enables the administrator to restrict the utilize of perilous programs.
Directories deal the execute leave differently. If a directory does not gain execute permissions, that user (or group, or other users on the system) can't cd into that directory and can't peek at information about the files in that directory. (You usually can find the names of the files, however.) Even if you gain permissions for the files in that directory, you generally can't peek at them. (This varies to some extent by platform.)
The second set of three characters is the group permissions (read, write, and execute, in that order), and the final set of three characters is what other users on the system are permitted to achieve with that file. Because of security concerns (either due to other users on your system or due to pervasive networks such as the Internet), giving write access to other users is highly discouraged.
Great, you can now read the permissions in the directory listing, but what can you achieve with them? Let's impart that Elvis wants to bear his directory readable only by himself. He can chmod go-rwx ~/songs: That means remove the read, write, and execute permissions for the group and others on the system. If Elvis decides to let Nashville artists retract a peek at his material but not change it (and if there's a group nashville on the system), he can first chgrp nashville songs and then chmod g+r songs.
If Elvis does this, however, he'll find that (at least, on some platforms) members of group nashville can't peek at them. Oops! With a simple chmod g+x songs, the problem is solved:
[ elvis@frogbog elvis ]$ ls -l
drwxr-xr-x 5 elvis users 4096 Dec 9 21:55 Desktop
drwxr-xr-x 2 elvis users 4096 Dec 9 22:00 Mail
-rw-r--r-- 1 elvis users 36 Dec 9 22:00 README
-rw-r--r-- 1 elvis users 22 Dec 9 21:59 ThisFile
drwxr-xr-x 2 elvis users 4096 Dec 12 19:57 arc
drwxr-x--- 2 elvis nashvill 4096 Dec 15 14:21 songs
-rw-r--r-- 1 elvis users 46 Dec 12 19:52 tao.txt
-rw-r--r-- 1 elvis users 21 Dec 9 21:59 thisfile
-rw-r--r-- 1 elvis users 45 Dec 12 19:52 west.txt
In addition to the read, write, and execute bits, there exists special permissions used by the system to determine how and when to suspend the timehonored leave rules. Any thorough understanding of UNIX requires an understanding of the setuid, setgid, and sticky bits. For timehonored system users, only a general understanding of these is necessary, and this discussion is thus brief. generous documentation on this matter exists elsewhere for budding system administrators and programmers.
The setuid bit applies only to executable files and directories. In the case of executable programs, it means that the given program runs as though the file owner were running it. That is, xhextris, a variant on Tetris, has the following permissions on my system:
1 games games 32516 May 18 1999 /usr/X11R6/bin/xhextris
There's a pseudouser called games on the system, which can't breathe logged into and has no home directory. When the xhextris program executes, it can read and write to files that only the game's pseudouser normally would breathe permitted. In this case, there's a high-score file stored on the system that writeable only by that user. When Elvis runs the game, the system acts as though he were the user games, and thus he is able to store the high-score file. To set the setuid bit on a file, you can inform chmod to give it mode u+s. (You can believe of this as uid set, although this isn't technically accurate.)
The setgid bit, which stands for "set group id," works almost identically to setuid, except that the system acts as though the user's group is that of the given file. If xhextris had used setgid games instead of setuid games, the lofty score would breathe writeable to any directory owned by the group games. It is used by the system administrator in ways fundamentally similar to the setuid permission.
When applied to directories on Linux, Irix, and Solaris (and probably most other POSIX-compliant UNIX flavors as well), the setgid bit means that current files are given the parent directory's group rather than the user's primary or current group. This can breathe useful for, say, a directory for fonts built by (and for) a given program. Any user might generate the fonts via a setgid command that writes to a setgid directory. setgid on directories varies by platform; check your documentation. To set the setgid bit, you can inform chmod to utilize g+s (gid set).
Although a file in a group or world-writeable directory without the sticky bit can breathe deleted by anyone with write leave for that directory (user, group, or other), a file in a directory with the sticky bit set can breathe deleted only by either the file's owner or root. This is particularly useful for creating temporary directories or scratch space that can breathe used by anyone without one's files being deleted by others. You can set leave +t in chmod to give something the sticky bit.
Like almost everything else on UNIX, permissions gain a number associated with them. It's generally considered that permissions are a group of four digits, each between 0 and 7. Each of those digits represents a group of three permissions, each of which is a yes/no answer. From left to right, those digits represent special permissions, user permissions, group permissions, and other permissions.
So, About Those leave Bits...
Most programs reading leave bits hope four digits, although often only three are given. Shorter numbers are filled in with leading zeros: 222 is treated as 0222, and 5 is treated as 0005. The three rightmost digits are, as previously mentioned, user (owner) permissions, group permissions, and other permissions, from prerogative to left.
Each of these digits is calculated in the following manner: read leave has a value of 4, write leave has a value of 2, and execute leave has a value of 1. Simply add these values together, and you've got that leave value. Read, write, and execute would breathe 7, read and write without execute would breathe 6, and no leave to achieve anything would breathe 0. Read, write, and execute for the file owner, with read and execute for the group and nothing at entire for anyone else, would breathe 750. Read and write for the user and group, but only read for others, would breathe 664.
The special permissions are 4 for setuid, 2 for setgid, and 1 for sticky. This digit is prepended to the three-digit numeric permission: A temporary directory with sticky read, write, and execute leave for everyone would breathe mode 1777. A setuid root directory writeable by nobody else would breathe 4700. You can utilize chmod to set numeric permissions directly, as in chmod 1777 /tmp.
In addition to a more precise utilize of chmod, numeric permissions are used with the umask command, which sets the default permissions. More precisely, it "masks" the default permissions: The umask value is subtracted from the maximum possible settings.* umask deals only with the three-digit permission, not the full-fledged four-digit value. A umask of 002 or 022 is most commonly the default. 022, subtracted from 777, is 755: read, write, and execute for the user, and read and execute for the group and others. 002 from 777 is 775: read, write, and execute for the user and group, and read and execute for others. I minister to set my umask to 077: read, write, and execute for myself, and nothing for my group or others. (Of course, when working on a group project, I set my umask to 007: My group and I can read, write, or execute anything, but others can't achieve anything with their files.)
You should note that the umask assumes that the execute bit on the file will breathe set. entire umasks are subtracted from 777 rather than 666, and those extra ones are subtracted later, if necessary. (See Appendix B for more details on leave bits and umask workings.)
*Actually, the leave bits are XORed with the maximum possible settings, if you're a computer science type.
Also notice that the first bit of output prepended to the permissions string indicates the file type. This is one handy route of identifying a file's type. Another is the file command, as shown in Table 3.3.
Table 3.3 ls File Types and file Output Sample
ls File kind Character
File parade Example
[either:1 ~]file /usr/usr: directory
Block special device
[linux: 10 ~] file /dev/hda1/dev/hda1: bury special (3/1)[sun:10 root ~]file /dev/dsk/c0t0d0s0/dev/dsk/c0t0d0s0: bury special(136/0)
Character special device
[linux:11 ~] file /dev/tty0/dev/tty0: character special (4/0)
[ensis:11 ~]file /dev/rdsk/c0t0d0s0/dev/rdsk/c0t0d0s0: character special (136/0)
UNIX domain socket
[linux:12 ~] file /dev/log/dev/log: socket
[sun:12 ~]file /dev/ccv/dev/ccv: socket
Named pipe special (FIFO device)
[linux:13 ~] file /dev/initctl/dev/initctl: fifo (named pipe)
[sun:13 ~]file /etc/utmppipe/etc/utmppipe: fifo
[linux:14 ~] file /usr/tmp/usr/tmp: symbolic link to ../var/tmp
[sun:14 ~]file -h /usr/tmp/usr/tmp: symbolic link to ¬../var/tmp
[linux:15 ~] file /etc/passwd/etc/passwd: ASCII text
[linux:15 ~] file /boot/vmlinux-2.4.2-2/boot/vmlinux-2.4.2-2: ELF 32-bit LSB executable,
¬Intel 80386, version 1,statically linked, not stripped
[linux:15 ~] file /etc/rc.d/init.d/sshd/etc/rc.d/init.d/sshd: Bourne-Again shell script text executable
[sun:15 ~]file /etc/passwd
/etc/passwd: ascii text
[sun:15 ~]file /kernel/genunix
-/kernel/genunix: ELF 32-bit MSB relocatable
¬SPARC Version 1
[sun:15 ~]file /etc/init.d/sshd
Notice the in-depth information that file gives—in many cases, it shows details about the file that no other command will readily parade (such as what kindly of executable the file is). These low-level details are beyond the scope of their discussion, but the man page has more information.
Important Points about the file ommand
file tries to figure out what kind a file is based on three types of test:
The file kind that the ls –l command returns.
-The presence of a magic number at the nascence of the file identifying the file type. These numbers are defined in the file /usr/share/magic in Red Hat Linux 7.1 and /usr/lib/locale/locale/LC_MESSAGES/magic (or /etc/magic) in Solaris 8. Typically, only binary files will gain magic numbers.
-In the case of a regular/text file, the first few bytes are tested to determine the kind of text representation and then to determine whether the file has a recognized purpose, such as C code or a Perl script.
file actually opens the file and changes the atime in the inode.
Inode lists are maintained by the filesystem itself, including which ones are free for use. Inode allocation and manipulation is entire transparent to both sysadmins and users.
Inodes become significant at two times for the sysadmin: at filesystem creation time and when the filesystem runs out of free inodes. At filesystem creation time, the total number of inodes for the filesystem is allocated. Although they are not in use, space is set aside for them. You cannot add any more inodes to a filesystem after it has been created. When you sprint out of inodes, you must either free some up (by deleting or moving files) or migrate to another, larger filesystem.
Without inodes, files are just a random assortment of ones and zeros on the disk. There is no guarantee that the file will breathe stored sequentially within a sector or track, so without an inode to point the route to the data blocks, the file is lost. In fact, every file is uniquely identified by the combination of its filesystem designation and inode number.
See Appendix B for more circumstantial information on the exact content of inodes and their structure.
Linux has a very useful command called stat that dumps the contents of an inode in a tidy format:
[linux:9 ~]stat .
Size: 16384 Filetype: Directory
Mode: (0755/drwxr-xr-x) Uid: (19529/ robin) Gid:(20/users)
Device: 0,4 Inode: 153288707 Links: 78
Access: Sun Jul 22 13:58:29 2001(00009.04:37:59)
Modify: Sun Jul 22 13:58:29 2001(00009.04:37:59)
Change: Sun Jul 22 13:58:29 2001(00009.04:37:59)
Boot bury and Superblock
When a filesystem is created, two structures are automatically created, whether they are immediately used or not. The first is called the boot block, where boot-time information is stored. Because a partition may breathe made bootable at will, this structure needs to breathe available at entire times.
The other structure, of more interest here, is the superblock. Just as an inode contains meta-information about a file, a superblock contains metainformation about a filesystem. Some of the more faultfinding contents are listed here:18
Timestamp: eventual update
Superblock situation flag
Filesystem situation flag: clean, stable, active
Number of free blocks
List of free blocks
Pointer to next free block
Size of inode list
Number of free inodes
List of free inodes
Pointer to next free inode
Lock fields for free blocks and inodes
Summary data block
And you thought inodes were complex.
The superblock keeps track of free file blocks and free inodes so that the filesystem can store current files. Without these lists and pointers, a long, sequential search would gain to breathe performed to find free space every time a file was created.
In much the identical route that files without inodes are lost, filesystems without intact superblocks are inaccessible. That's why there is a superblock situation flag—to witness whether the superblock was properly and completely updated before the disk (or system) was eventual taken offline. If it was not, then a consistency check must breathe performed for the entire filesystem and the results stored back in the superblock.
Again, more circumstantial information about the superblock and its role in UNIX filesystems may breathe found in Appendix B.
Both Red Hat and Solaris recognize a host of different filesystem types, although you will generally halt up using and supporting just a few. There are three standard types of filesystem—local, network, and pseudo—and a fourth "super-filesystem" kind that is actually losing ground, given the size of modern disks.
Local filesystems are common to every system that has its own local disk.19 Although there are many instances of this kind of filesystem, they are entire designed to drudgery within a system, managing the components discussed in the eventual section and interfacing with the physical drive(s).
Only a few local filesystems are specifically designed to breathe cross-platform (and sometimes even cross–OS-type). They further in handy, though, when you gain a nondisk hardware failure; you can just retract the disk and allot it into another machine to retrieve the data.20 The UNIX File System, or ufs, was designed for this; both Solaris and Red Hat Linux machines can utilize disks with this filesystem. Note that Solaris uses ufs filesystems by default. Red Hat's default local filesystem is ext2.
Another local, cross-platform filesystem is ISO9660, the CD-ROM standard. This is why you can read your Solaris CD in a Red Hat box's reader.
Local filesystems further in two related but several flavors. The original, standard model filesystem is silent in broad utilize today. The newer journaling filesystem kind is just nascence to really further into its own. The major inequity between the two types is the route they track changes and achieve integrity checks.
Standard, nonjournaling filesystems reckon on flags in the superblock for consistency regulation. If the superblock flag is not set to "clean," then the filesystem knows that it was not shut down properly: not entire write buffers were flushed to disk, and so on. Inconsistency in a filesystem means that allocated inodes could breathe overwritten; free inodes could breathe counted as in use—in short, rampant file corruption, mass hysteria.
But there is a filesystem integrity checker to deliver the day: fsck. This command is usually invoked automatically at boot-time to verify that entire filesystems are clean and stable. If the / or /usr filesystems are inconsistent, the system might prompt you to start up a miniroot shell and manually sprint fsck. A few of the more faultfinding items checked and corrected are listed here:
Unclaimed blocks and inodes (not in free list or in use)
Unreferenced but allocated blocks and inodes
Multiply claimed blocks and inodes
Bad inode formats
Bad directory formats
Bad free bury or inode list formats
Incorrect free bury or inode counts
Superblock counts and flags
Note that a filesystem should breathe unmounted before running fsck (see the later section "Administering Local Filesystems"). Running fsck on a mounted filesystem might reason a system panic and crash, or it might simply rebuff to sprint at all. It's besides best, though not required, that you sprint fsck on the raw device, when possible. behold the man page for more details and options.
So where does fsck allot orphans, the blocks and inodes that are clearly in utilize but aren't referenced anywhere? Enter the lost+found directories. There is always a /lost+found directory on every system; other directories accrue them as fsck finds orphans in their purview. fsck automatically creates the directories as needed and renames the lost blocks into there by inode number. behold the man pages "mklost+found" on Red Hat and "fsck_ufs" on Solaris.
Journaling filesystems achieve away with fsck and its concomitant superblock structures. entire filesystem situation information is internally tracked and monitored, in much the identical route that databases systems set up checkpoints and self-verifications.
With journaling filesystems, you gain a better desultory of replete data recovery in the event of a system crash. Even unsaved data in buffers can breathe recovered thanks to the internal log.21 This kindly of foible tolerance makes journaling filesystems useful in high- availability environments.
The drawback, of course, is that when a filesystem relish this gets corrupted somehow, it presents major difficulties for recovery. Most journaling filesystems provide their own salvaging programs for utilize in case of emergency. This underscores how faultfinding backups are, no matter what kindly of filesystem software you've invested in. behold Chapter 16, "Backups," for more information.
One of the earliest journaling filesystems is silent a commercial venture: VxFS by Veritas. Another pioneer has decided to release its software into the public domain under GPL22 licensing: JFS23 by IBM. SGI's xfs journaling filesystem has been freely available under GPL since about 1999, although it is only designed to drudgery under IRIX and Linux.24
Maintenance of filesystem situation incurs an overhead when using journaling filesystems. As a result, these filesystems effect suboptimally for diminutive filesystem sizes. Generally, journaling filesystems are usurp for filesystem sizes of 500Mb or more.
Network-based filesystems are really add-ons to local filesystems because the file server must gain the actual data stored in one of its own local filesystems.25 Network file- systems gain both a server and client program.
The server usually runs as a daemon on the system that is sharing disk space. The server's local filesystems are unaffected by this extra process. In fact, the daemon generally only puts a few messages in the syslog and is otherwise only visible through ps.
The system that wants to access the server's disk space runs the client program to mount the shared filesystems across the network. The client program handles entire the I/O so that the network filesystem behaves just a relish a local filesystem toward the client machine.
The antediluvian standby for network-based filesystems is the Network File System (NFS). The NFS standard is currently up to revision 3, though there are quite a number of implementations with their own version numbers. Both Red Hat and Solaris further standard with NFS client and server packages. For more details on the inner workings and configuration of NFS, behold Chapter 13, "File Sharing."
Other network-based filesystems comprehend AFS (IBM's Andrew File System) and DFS/DCE (Distributed File System, participate of the Open Group's Distributed Computing Environment). The mechanisms of these advanced filesystems evanesce beyond the scope of this book, although their goal is silent the same: to efficiently participate files across the network transparently to the user.
Pseudofilesystems are an spicy evolution in that they are not actually related to disk-based partitions. They are instead purely analytic constructs that represent information and meta-information in a hierarchical structure. Because of this structure and because they can breathe manipulated with the mount command, they are silent referred to as filesystems.
The best instance of pseudofilesystems exists on both Red Hat and Solaris systems: /proc. Under Solaris, /proc is restricted to just managing process information:
[sun:1 ~]ls /proc
0 145 162 195 206 230 262 265 272 286 299 303 342 370 403 408 _672 752
1 155 185 198 214 243 263 266 278 292 3 318 360 371 404 52 _674
142 157 192 2 224 252 264 268 280 298 302 319 364 400 406 58 _678
Note that these directories are entire named according to the process numbers corresponding to what you would find in the output of ps. The contents of each directory are the various meta-information that the system needs to manage the process.
Under Red Hat, /proc provides information about processes as well as about various system components and statistics:
[linux:1 ~] ls /proc
1 18767 23156 24484 25567 28163 4 493 674 8453 ksyms _stat
13557 18933 23157 24486 25600 3 405 5 675 9833 loadavg _swaps
13560 18934 23158 24487 25602 3050 418 5037 676 9834 locks _sys
13561 18937 23180 24512 25603 3051 427 5038 7386 9835 mdstat _tty
1647 19709 23902 24541 25771 3052 441 5054 7387 bus meminfo _uptime
1648 19730 23903 24775 25772 30709 455 5082 7388 cmdline misc _version
1649 19732 23936 25494 25773 30710 473 510 7414 cpuinfo modules
16553 19733 24118 25503 25824 30712 485 5101 7636 devices mounts
18658 2 24119 25504 25882 30729 486 524 7637 dma mtrr
18660 21450 24120 25527 25920 320 487 558 7638 filesystems net
18661 21462 24144 25533 26070 335 488 6 7662 fs _partitions
18684 21866 24274 25534 26071 337 489 670 8426 interrupts pci
18685 21869 24276 25541 26072 338 490 671 8427 ioports scsi
18686 21870 24277 25542 28161 339 491 672 8428 kcore self
18691 21954 24458 25543 28162 365 492 673 8429 kmsg slabinfo
Again they behold the directories named for process numbers, but they besides behold directories with indicative names such as cpuinfo and loadavg. Because this is a hierarchical filesystem, you can cd into these directories and read the various files for their system information.
The most spicy thing about /proc is that it allows even processes to breathe treated relish files.26 This means that pretty much everything in UNIX, whether it is something that just exists or something that actually happens, can now breathe considered a file.
For more information under Red Hat, kind man proc. For more information under Solaris, kind man –s 4 proc.
Finally, there are the "super-filesystems" or analytic volumes that achieve what the other major types of filesystem cannot: surmount the barriers of partitions. You may well question why anyone would want to achieve that. There are two reasons. First, because disks used to breathe a lot smaller and more costly, you used what you had at hand. If you needed a great pool of disk space, analytic volumes allowed you to aggregate remnants into something useable. Second, even with larger disks, you silent might not breathe able to achieve the kindly of disk space required by a particular researcher or program. Once again, analytic volumes allow you to aggregate partitions across disks to contour one great filesystem.
Crossing disk boundaries with a analytic volume is referred to as disk spanning. Once you gain analytic volumes, you can besides gain some fairly tangled data management methods and performance-enhancing techniques. Disk striping, for example, is a performance booster. Instead of sequentially filling one disk and then the next in series, it spreads the data in discrete chunks across disks, allowing better I/O response through parallel operations.
RAID27 implements analytic volumes at 10 several levels, with various features at each level. This implementation can breathe done either in hardware or in software, although the nomenclature for both is the same.28
Table 3.4 RAID Levels
-Requires extra drives for data duplication
(Very similar to RAID-3)
Requires sunder parity disk
Requires sunder parity disk
(Very similar to RAID-5)
Slowest for writes, but
Rotating parity array
good for reads
Requires three to five sunder parity disks
Reconstruction by parity data (not duplication)
RAID-5 + secondary
Not in broad use
RAID-5 + real-time embedded controller
Not in broad use
-RAID-0 array duplicated (mirrored)
-Each stripe is RAID-1 (mirrored) array
Array of parity stripes
Each stripe is RAID-3 array
Clearly, the kindly of complexity inherent in entire analytic volume systems requires some kindly of back-end management system. Red Hat offers the analytic Volume Manager (LVM) as a kernel module. While the details of LVM are beyond the scope of this book, it is spicy to note that you can allot any filesystem that you want on top of the analytic volume. Start at http://www.linuxdoc.org/HOWTO/LVM-HOWTO.htmlfor more details.
Although Sun offers analytic volume management, it is through a for-pay program called "Solstice DiskSuite." The filesystem on DiskSuite analytic volumes must breathe ufs. For more information, start at http://docs.sun.com/ab2/coll.260.2/DISKSUITEREF.
Another commercial analytic volume manager for Solaris comes from Veritas; see: http://www.veritas.com/us/products/volumemanager/faq.html#a24
The beauty of entire analytic volumes is that they appear to breathe just another local filesystem and are completely transparent to the user. However, analytic volumes achieve add some complexity for the systems administrator, and the schema should breathe carefully documented on paper, in case it needs to breathe re-created.
Normally, a file server's disks are directly attached to the file server. With network-attached storage (NAS), the file server and the disks that it serves are sunder entities, communicating over the local network. The storage disks require an aggregate controller that arbitrates file I/O requests from the external server(s). The server(s) and the aggregate controller each gain several network IP addresses. To serve the files to clients, a file (or application) server sends file I/O requests to the NAS aggregate controller and relays the results back to client systems.
NAS is touched on here for completeness—entire books can breathe written about NAS design and implementation. NAS does not really represent a kind of filesystem, but rather it is a mechanism to assuage the file server from the details of hardware disk access by isolating them in the network-attached storage unit.
Red Hat Filesystem Reference Table
Table 3.5 lists major filesystems that currently advocate (or are supported by) Red Hat.29 The filesystem types that are currently natively supported are listed in /usr/src/linux/ fs/filesytems.c.
Table 3.5 Filesystem Types and Purposes, with Examples (Red Hat)
Specific Instances (as Used in /etc/fstab)
Red Hat default filesystem
Journaling filesystem from IBM
Journaling filesystem from SGI
Windows compatibility: DOS
Windows compatibility: NT
Windows compatibility: FAT-32
Adfs hfs romfs
Affs hpfs smbfs
Coda mnix udf
devpts ncpfs umsdos
Deprecated, pre-kernel 2.1.21
Network-based remote communication
Store process (and other system) meta-information
Solaris Filesystem Reference Table
Table 3.6 lists major filesystems that currently advocate (or are supported by) Solaris. The filesystem types that currently are natively supported are listed as directories under /usr/lib/fs.
Table 3.6 Filesystem Types and Purposes, with Examples (Solaris)
Specific Instances (as Used in /etc/vfstab)
Solaris default filesystem; Red Hat-compatible
Journaling filesystem from IBM
Network-based remote communication
Store process metainformation
Fdfs swapfs tmpfs
Mount metainformation areas as filesystems
mntfs cachefs lofs
fifofs specfs udfs namefs