Handling time. Will usually ship within 1 business day of receiving cleared payment - opens in a new window or tab. Taxes may be applicable at checkout. Learn more. Return policy. Refer to eBay Return policy for more details. You are covered by the eBay Money Back Guarantee if you receive an item that is not as described in the listing. Payment details. Payment methods.
Other offers may also be available. Interest will be charged to your account from the purchase date if the balance is not paid in full within 6 months. Minimum monthly payments are required. Subject to credit approval. See terms - opens in a new window or tab. Back to home page. Listed in category:. Email to friends Share on Facebook - opens in a new window or tab Share on Twitter - opens in a new window or tab Share on Pinterest - opens in a new window or tab Add to Watchlist.
Opens image gallery Image not available Photos not available for this variation.
Learn more - opens in new window or tab Seller information thrift. See all thrift. Sellers set the item's declared value and must comply with customs declaration laws.
In this index, a classroom pay or few product below is each Valuation with the talkative and SA format contents Aboriginal for elective request with talented servers. Many variations were subsequently developed, and they are collectively referred to as Unix-like operating systems. Beginning the Installation. John Bambenek Agnieszka Klus. Sluit venster Stel een vraag Van:. Introducing Mozilla. Working with OpenOffice Calc.
Buyers may be subject to additional charges for customs clearance. For additional information, see the Global Shipping Program terms and conditions - opens in a new window or tab No additional import charges on delivery Delivery: Estimated between Mon.
Payments: Special financing available. An error occurred, please try again. Good : A book that has been read but is in good condition. Linux is an operating system, based on Unix, that has become a viable desktop system for many users, especially those involved with system and network administration. This book covers all the most important topics for the reader who wants to get Linux up and running and to become productive with the operating system as quickly as possible. The book covers topics such as installing, setting up, and negotiating the new desktop environment, and also includes: An explanation of what is happening behind the scenes - the reader learns how the system works as well as what to do, in simple, layman's language.
Special attention to new features of the latest release, especially tools that make tasks that used to be difficult easier. Instruction on troubleshooting practices and debugging tools. A comprehensive list of all major places to get Linux support and answers. Hour 1. Preparing to Install Fedora. Taking a Hardware Inventory. Evaluating Your Hardware. Making Space for Linux. Launching the Fedora Installer. Hour 2. Installing Fedora.
Linux is an operating system, based on Unix, that has become a viable desktop system for many users, especially those involved with system and network administration. This book covers all the most important topics for the reader who wants to get Linux up and running and to become. Sams Teach Yourself Red Hat Linux Fedora in 24 Hours. HOUR 8: Networking Without Graphics. Browsing the Web at the Console.
Starting the Fedora Installer. Beginning the Installation. Hour 3. Booting, Logging In, and Configuring. Booting Fedora. Welcome to Fedora Core! Configuring Your Printer and Internet Service. Hour 4. Navigating Linux at the Console. Why Learn to Use Linux at the Console? Understanding Virtual Consoles. Introducing the Shell. Working with the File System. Understanding Permissions. Hour 5. Making the Console Work for You. Creating, Editing, and Saving Text Files. Grouping Files for Efficient File Management.
Searching Files and Directories Quickly. Using Command Output for Complex Tasks. Hour 6. Getting Help at the Console. Introducing Manual Pages. Using the GNU info System. Getting Help from the Commands. Hour 7. Working Without the Mouse. Printing at the Command Line. Creating and Sorting Lists of Data. Hour 8. Networking Without Graphics. Browsing the Web at the Console. Managing Email at the Console. Exchanging Files with Windows Hosts Using smbclient. Hour 9. Harnessing the Power of the Shell.
Adding to Your Command Repertoire. Using Shell Variables and Quoting. Hour Introducing the Fedora Desktop. Logging In to the Desktop. Navigating the Desktop. Working with Multiple Windows. Understanding Virtual Workspaces. Working with Files on the Desktop. Using the File Manager.
Working with Files and Directories. Manipulating Files Using Drag and Drop. Working with Trash Contents. Development versions of Debian ship with more recent versions of these popular desktop environments. Debian follows a much longer release schedule than most other Linux distributions, and Debian 3.
The latest incarnation, 3. Fortunately, although Debian hasn't changed its major version number in quite some time, the Debian developers do a good job of keeping their packages updated, at least in terms of major bug fixes and the like. Still, if you want the latest and greatest versions of packages, you may want to pass on Debian unless of course a newer version is available by the time you read this.
Fedora Core is essentially a new name for the low-end, freely-redistributable Red Hat product.
As such, it has the same basic strengths and weaknesses as Red Hat. Because Red Hat has changed substantially in recent years, I'm providing a new and separate review of Fedora for this page. I've run Fedora Core 1 on x86 and AMD64 platforms, and found the experience to be quite similar on both. The installation process is GUI-based, assuming the installer can correctly identify the video chipset.
I therefore had to install in text mode. Aside from the SiS video card, the installer correctly identified all the major hardware components on all three of the systems on which I installed it, even including an SATA hard disk on the Athlon Once installed, Fedora runs smoothly, but the default configuration is a memory hog, due largely to the fact that it uses GNOME as the standard user interface.
KDE isn't really any better. Although GNOME and KDE have both become much more useable in the past year or two, I ultimately ditched them both in favor of XFce, which is much less bloated than the more popular desktop environments. I had to download and install XFce from links on its Web page, though; it doesn't ship with Fedora. Gentoo uses the 0. In fairness, this isn't really a Fedora-specific issue; it's one of XFree86 and my video card. I had the same problem with Mandrake 9. I had no problems with the ATI drivers for my two x86 test systems. Fedora and recent versions of Red Hat include GUI tools to help keep your system software up to date.
These tools work, but I've never really liked them very much. On my xbased systems, I installed apt4rpm and used it instead, with good results. I haven't yet gotten around to installing it on my Athlon 64 system, though. Fedora's system administration tools are more-or-less identical to those in Red Hat 9, and so have the same problems and benefits. It also performs the same annoying ownership changes on certain key device files as Red Hat.
Red Hat 9 books should be helpful, as well. A few details are different, but Fedora 1 looks and feels a lot like Red Hat 9.
Gentoo Linux is one of the most atypical Linux distributions in existence. This isn't to say that Gentoo is bad or even weird in any absolute sense; it's just not like other Linux distributions. Perhaps Gentoo's most striking unique feature is its package management. Rather than use RPMs, Debian packages, or even binary tarballs, Gentoo uses a system called Portage, which enables relatively painless package installation from source code. Portage is quite similar to the ports system of FreeBSD. To use it, you type the emerge command followed by various options and the package name.
The system then downloads the source code from the Internet, compiles it, and installs it. You can also uninstall packages with emerge , but the tool lacks some of the features of rpm or dpkg for handling other distributions' packages. For instance, I don't know of any way to discover what files are associated with any given package.
Portage also won't complain if you try to remove a package that's depended upon by other packages. Furthermore, the Portage system has the obvious drawback that it takes more time to install a package; Gentoo must compile it, after all. The emerge utility does provide options to install precompiled binaries, but aside from the basic system files, precompiled Gentoo packages are hard to find. On the other hand, Portage enables you to customize compilation options for your system -- the target CPU, compiler speed optimizations, libraries to be included, and so on.
In theory, this should result in a modest speed boost over a "generic" distribution, and it can certainly help to work around the tangled mess of dependencies that too often plague RPMs and Debian packages. Another unusual Gentoo feature is its handling of startup scripts. Most Linux distributions use numbered runlevels and rely upon links with specific filenames in runlevel directories to control what processes start up at system boot time. Gentoo, though, uses a named runlevel system, so you can give runlevels descriptive names, which can be handy if you need to regularly switch between several environments, as for instance when linking a notebook to different networks.
The Gentoo startup scripts also support an automatic dependency-checking system, so if you try to start a subsystem that relies on another that's not yet running, there's no problem -- Gentoo automatically starts the depended-upon subsystem. My experience with Gentoo began a few months ago, when I installed a prerelease version of Gentoo 1. Unfortunately, I didn't get around to using it much. More recently, I've installed the latest version Gentoo, like Debian, is released simultaneously on several platforms; this gives it an edge over most other distributions for non-x86 users.
In part because of its use of Portage, Gentoo installation is atypical. It's text-based and requires you to type assorted Linux commands to partition the disk, install core system files, and so on. I chose to do a stage 3 install, which means that many of the most common packages were installed in binary form.
herbinez.com/2944.php My install proceeded smoothly, with the help of the online Gentoo installation instructions. It also took only a couple of hours, although it required constant interaction. Despite the excellent installation instructions, I don't think most Linux newbies would be comfortable installing Gentoo.
Those familiar with other UNIX versions, or with a strong technical bent, might be happy with it, though. Seasoned Linux users shouldn't have problems installing Gentoo. In use, Gentoo has performed quite well. In fact, as noted in the reviews of Fedora and Mandrake, the Gentoo XFree86 installation worked with my SiS based video card, whereas these other distributions didn't. I particularly like the Gentoo startup script system, and I appreciate its extreme configurability -- you can easily select which of several alternative packages you want to use, such as inetd vs.
The ability to tweak compile options is theoretically nice, but unless you have a deep understanding of the options, they can be overwhelming. In this respect, Gentoo definitely falls into the same camp as Debian and Slackware. I don't know of any books on Gentoo Linux, and the distribution is unique enough that no other distribution-specific book is likely to be of much help.
Fortunately, the online Gentoo documentation is quite good, although at times it's a bit too detailed for the type of user who's most likely to want to run Gentoo. This distribution's goal is to provide a viable alternative to Microsoft Windows on desktop PCs. As such, it attempts to be easy to install and use, and makes certain design decisions that deviate more than usual from the typical.
These design decisions have the effect of making the distribution simpler to configure but less flexible than is typical. I tried installing Lindows 4. Neither install went smoothly, although I suspect the reason for the problems was the fact that I tried installing to systems with hard disks that were configured in a decidedly atypical for a target Lindows user way. Specifically, both systems had multiple partitions with multiple OSs. My problems began when I selected install partitions. The Lindows installer misidentified the OSs on several partitions for instance, it called a FreeBSD partition a Linux partition , and presented partitions in a strange order.
I had a hard time picking the correct target partition. The installer also presented very few options; for instance, I saw no way to tell Lindows where to install the boot loader it uses LILO, and installs it in the hard disk's MBR. When I rebooted, Lindows didn't start. Unfortunately, Lindows doesn't present an option to show verbose startup messages similar to the options in recent versions of Fedora and Mandrake. It does offer a troubleshooting option in its LILO configuration, though, and that presents a typical text-mode kernel message startup.
When I selected this option on my notebook, it revealed that Lindows was attempting to fsck an ext3fs partition it had detected and tried to mount. Overall, then, Lindows earned very low marks on its installation procedures. The problems I encountered could be overcome, but probably not by the distribution's target audience.
On the other hand, that audience wouldn't be likely to have pre-existing Linux partitions or so many other OSs' partitions on their hard disks, so the problem might not crop up for them, either. Also, Lindows is being marketed heavily as an alternative pre-load option, and users who buy a PC with Lindows installed obviously won't need to deal with these issues.
Once booted, Lindows caused more problems. During installation, it asked for a password the root password, although it wasn't identified as such. The Lindows KDM login screen is modified to not ask for a username; type the root password and you're in. An advanced configuration option enables you to create user accounts, but that option is well hidden. Even after creating a user account, I couldn't see any way to specify the account to use at the KDM login prompt, thus effectively necessitating the use of root for ordinary tasks. As any experienced Linux or Unix user knows, requiring users to operate as root is a security no-no of the highest order; this is, in my view, an inexcusable design flaw in Lindows, and should single-handedly disqualify the distribution for use by anybody.
Throwing caution to the wind, I logged in as root. Lindows then launched a multimedia tour of the system. What I saw of it seemed well-produced. I didn't want to sit through the whole thing, but that was difficult; apparently the designers assumed that users would have a screen larger than the x display on my old laptop, and the button to exit from the presentation described early on in the presentation was off the edge of my screen. I ultimately logged into the console and killed it. The desktop is based on KDE, and presents friendly menus for performing various tasks. Windows users shouldn't have any trouble navigating the Lindows desktop.
Because of the severe security flaw of an inability to log in as anything but root , I decided to stop my evaluation of Lindows at this point. I didn't try running Windows programs an early selling point of the distribution, but one that's been downplayed more recently or otherwise evaluate it. Of course, I'm certain that I could have worked around the security flaws in the OS, but members of its target market probably couldn't -- and might not know that they should.
If you're a member of that target market, I strongly urge you to give Lindows a miss. More mainstream distributions, such as Fedora, Mandrake, and SUSE, can be almost as user-friendly as Lindows and much more secure, thanks to their use of Linux accounts. The Xandros distribution is also aimed at this group, and does a much better job than Lindows. Mandrake Linux is an offshoot of Red Hat Linux. The package is available in at least four forms: A downloadable edition, a "PowerPack" version, a "Pro Suite" version, a "Corporate Server" version, and a "Discovery" version.
The Powerpack edition includes extra software compared to the downloadable edition, and the Pro Suite includes still more. The Discovery version appears to be a stripped-down version intended for home use. Mandrake provides a comparison page summarizing the differences between versions.
Previous versions were available with other names and in other packages, such as the version 8. As I write, Mandrake 9. Version 9. Mandrake 9. Mandrake distinguishes itself from Red Hat in its Pentium optimizations on all packages -- Red Hat, like most Linux distributions, is compiled with optimizations. In terms of installation and administration, these distributions are similar, although they're not as similar as they once were. Mandrake suffers from many of Red Hat's peculiarities, as described in that section. Mandrake uses its own GUI administration tools, which work reasonably well, for the most part.
They do tend to be a bit "over-enthusiastic," though; they may overwrite working configurations that don't match their expectations. Unfortunately, MenuDrake tends to overwrite working configurations that you've hand-tweaked -- an annoyance I've found so bad that I've completely removed MenuDrake from my system. Mandrake features a nice X-based installation tool. I used Mandrake 7. I've run Mandrake 9.
Of these two, the The 9. As with Fedora, these are more XFree86 issues than they are distribution issues, and they're not likely to occur for users of other video cards. This tendency makes the distribution almost impossible to use if you rely on the afflicted programs. Fortunately, the Amazon does list a couple of Mandrake 9. In addition, Red Hat books are partially applicable to Mandrake -- but be aware that the two distributions use different GUI configuration tools and provide some different software defaults, such as Postfix vs. Red Hat Linux is one of the oldest and most popular of today's Linux distributions.
In the past, it was available in two product lines, each with its own unique focus. It's marketed towards businesses with lots of money to throw at their big servers. Red Hat provides a Web page summarizing the differences between these software families.
If you're devoted to the Red Hat name, you can still find the Personal and Professional versions of Red Hat 9 in stores, but for the most part, if you want a low-cost Red Hat, you must now go with Fedora. Historically, there have been variants for several non-x86 CPUs, including the new IA Itanium ; but some of these variants are substantially older than version 9. Although the options for low-cost Red Hat have now shifted to Fedora, I'm leaving this section on Red Hat for historical purposes. I've used Red Hat versions 4.
Red Hat works quite well, for the most part, but as I customized my 6. This seems fine initially, but if you switch from X to a text console and log on as root for some reason, suddenly you have no access to sound as an ordinary user.
For me personally, a static and permissive setting on the audio devices is preferable, although others might prefer Red Hat's approach.