Go back to fronty page View most popular entries View latest additions Submit tutorials to UnixTutorials.info
UnixTutorials logo

Search results for Working with gmirror on a Sun Fire X2100


Connecting to a Wireless LAN with Linux, Part 2

Post date: April 13, 2005, 19:04 Category: Hardware Views: 4271 Comments
Tutorial quote: In Part 1 we reviewed hardware options, which wireless utilities should be present, how to use Windows drivers, and how to be open to connect to any available wireless access point. Today we'll cover configurations on Red Hat- and Debian-type systems, basic security, and hardware discovery.

Wireless connectivity can be rather overly friendly, allowing connections from anyone. This howto assumes you have a wireless access point on a LAN, which can be all wireless or mixed wired and wireless. You don't want it wide open to just any random person with a desire to snoop on your network or "borrow" your bandwidth, but you want some access controls and security. Your access point should have a unique SSID (service set identifier), WEP (wireless equivalent privacy) or WPA/WPA2 (Wi-fi protected access) set up and working, and either a DHCP server or a pool of assigned IP addresses for clients.

Grub From the Ground Up

Post date: April 12, 2005, 17:04 Category: Software Views: 3270 Comments
Tutorial quote: Grub is a world-class boot loader with insufficient documentation. In many ways it blows the doors of LILO. For instance, it's MUCH easier to use Knoppix to rebuild a grub boot loader than to rebuild a LILO boot loader. However, until you're comfortable with grub, it might seem just the opposite. All too often grub dumps you at a grub> prompt with no hint of what you should do. You might have heard that a successful reboot is just three commands away, but which commands? The state of grub's documentation is such that you can't figure it out unless you already know grub.

That catch 22 is the very purpose of this document. This document will to give you enough grub expertise that you can create a grub boot floppy on a working machine with grub installed (not necessarily as the bootloader, just installed), and use that floppy to bust back into a Linux machine with a blown bootloader, and then use that floppy to actually install grub as the bootloader.

This document does not discuss using grub to boot or dual boot Windows, mach, BSD, or other non-Linux operating systems. I might write on that subject later. But in the meantime, once you're familiar with the principles and practices of grub, given some study of existing documentation you'll probably be able to use grub to boot non-Linux operating systems.

The PartImage Handbook

Post date: May 21, 2005, 15:05 Category: Software Views: 3021 Comments
Tutorial quote: - Partition Image is a Linux/UNIX partition imaging utility: it saves partitions formatted using the Ext2FS (the linux standard), ReiserFS (a new journaled and powerful file system), JFS IBM journaled file systems from AIX, NTFS (Windows NT File System), FAT16/32 (DOS & Windows file systems), or HPFS (OS/2 file system) file system formats to an image file. Only used blocks are copied. The image file can be compressed in the GZIP/BZIP2 formats to save disk space, and split into multiple files to be copied on removable media (ZIP for example), or burned on a CD-R ...

- This allows the user to save a full Linux/Windows system, with a single operation. When problems occur (viruses, crash, error, ...), you just have to restore, and after several minutes, all your system is restored (boot, files, ...), and fully working.

- This is very useful when installing the same software on many machines: just install one of them, create an image, and then restore the image on all other machines. After the first one, each subsequent installation can be made automaticaly, and only requires a few minutes.

Keeping Your Life in Subversion

Post date: October 2, 2005, 16:10 Category: Software Views: 3919 Comments
Tutorial quote: I keep my life in a Subversion repository. For the past five years, I've checked every file I've created and worked on, every email I've sent or received, and every config file I've tweaked into revision control. Five years ago, when I started doing this using CVS, people thought I was nuts to use revision control in this way. Today it's still not a common practice, but thanks to my earlier article "CVS homedir" (Linux Journal, issue 101), I know I'm not alone. In this article I will describe how my new home directory setup is working now that I've switched from CVS to Subversion.

Subversion is a revision-control system. Like the earlier and much cruftier CVS, its purpose is to manage chunks of code, such as free software programs with multiple developers, or in-house software projects involving several employees. Unlike CVS, Subversion handles directories and file renaming reasonably, which is more than sufficient reason to switch to it if you're already using CVS. It also fixes most of CVS's other misfeatures. Subversion still has its warts, though, such as an inability to store symbolic links and some file permissions, and its need for twice as much disk space as you'd expect thanks to the copies of everything in those .svn directories. These problems can be quite annoying when you're keeping your whole home directory in svn. Why bother?

Tunneling the hard way: using slirp, pppd and socat

Post date: January 29, 2006, 13:01 Category: Network Views: 12663 Comments
Tutorial quote: Every now and then you might come across a "bad" ISP. The one I have at home for example is dropping UDP packets ever so often when I try to play online games -- and it tends to drop random packets while I try to log onto a gameserver too which makes a certain game I like to play crash during the loading phase so it can't recover. I also heard of other ISPs blocking certain ports on external servers -- universities for example seem to like blocking p2p network ports and the school i was attending till last august blocked everything but port 80 for http -- including ftp which made even on-topic "research" a pita at times.
Usually there's three ways of working around this problem if "giving up" is not an option to you: a) change your ISP, b) use ssh to redirect ports, c) connect to an external VPN to route for you. a) can be tricky -- it's impossible if you're sharing the link with your parents and they insist on their email addresses or in the university/workplace/school scenario. b) will only work with single port/host combinations and for c) you will need a full-fledged rootbox idling around on the internet -- which tend to be expensive and "virtual servers" might not work because those often don't include tun/tap devices and/or kernel-level ppp support if you rent them and in case you rented them you probably can't fiddle around with its kernel to enable it (that was my problem at least). If any of this rings a bell to you, read on and discover method d)
Web-based applications and online marketing solutions - LumoLink