The parent is actually funny and it gets an offtopic mod, while all the "-1, redundant" jokes about slashdotting and girlfreinds get 5 funny. please join in the jihad against crack moderators, Metamod those jokes unfunny.
This tutorial shows how to combine Samba and GRUB to build a compact, highly adaptable, cross-platform test network, capable of booting and networking a large number of operating systems on a small number of machines. Though Samba and GRUB can manage many different operating systems, this tutorial focuses on Linux and Windows. Who should take this tutorial
page 2 of 4
This is neither a networking tutorial, nor a Linux system administration tutorial. Basic knowledge of running Linux and Windows, including user authentication, installing operating systems, partitioning, and managing user accounts will get you going a lot faster. I'll use values that are valid for my system, such as fd0 and hda. I trust that you will use what is correct for your system. What prerequisites you'll need
page 3 of 4
You'll need reasonably modern hardware: PCs four years old and newer ought to do the job. Running multiboot systems requires large hard drives, and support for Large-Block Addressing (LBA). GRUB can read any part of a hard disk supported by true LBA. Unfortunately, a small number of motherboards that claim to support LBA do not, and the only way to find out which ones they are is to try to boot a system from beyond the 1024 cylinder limit. Also needed are a generic Linux boot/rescue disk, such as tomsrtbt, or H. Peter Anvin's SuperRescue CD, and a Windows 98 rescue disk, which is the all-time most useful Windows disk. GRUB does not yet have the ability to boot a CD; we still need floppy disk
Who wrote this tutorial
page 4 of 4
Carla Schroder is a freelance PC tamer, administering Linux and Windows systems for small businesses, and writes how-tos for real people. Loves computers and high tech, thinks Linux/Open Source/Free Software is the best playground in the world. Carla discovered computers and high-tech in 1994; her first PC was an Apple II. She progressed through DOS/Windows, from 3.1 to XP. Discovered Linux in 1998. Carla is living proof that self-taught middle-aged ladies can be fine computer gurus.
You can contact Carla directly, or click Feedback at the top of any panel.
Cross-platform developers face interesting challenges for building testing environments. In my ideal happy world, computer labs are huge, stocked with every little gadget a person might ever need -- even a Segway to scoot around on. But, as we are all painfully aware, resources are more limited in the real world.
One good option is to use excellent programs like VMWare or User-Mode Linux. These create virtual environments for running several operating systems side-by-side on a single PC. (See the Resources for links to more info on VMWare and User-Mode Linux.)
But for users who prefer completely native environments, the open source/free software world gives us two great tools for packing a lot of operating systems into a small space: Samba and GRUB.
Samba enables file and printer sharing between different operating systems. It can be a primary domain controller or a stand-alone server. It is primarily used to network Linux, UNIX, and Windows. Macintosh, OS X, OS/2, and other platforms are supported with varying degrees of tweakage.
GRUB, the Grand Unified Bootloader, is a most remarkable program. GRUB is capable of booting nearly any OS, and nearly any number of them. This tutorial will focus on multibooting and networking Linux and Windows.
Testing in native environments
page 2 of 2
I use a three-PC test network. Thanks to the combined magic of Samba and GRUB, there is enormous flexibility; you can:
Test applications and application servers (in native environments) Test all manner of networking configurations Use removable drive trays to swap in and out as needed
Boot bare kernels, passing in parameters and modules from the GRUB command line
You have probably already spotted the one flaw in this beautiful scheme: the inconvenience of rebooting (as only
Slashdot Mirror
The parent is actually funny and it gets an offtopic mod, while all the "-1, redundant" jokes about slashdotting and girlfreinds get 5 funny. please join in the jihad against crack moderators, Metamod those jokes unfunny.
/ Most of mine is \ /
\ ASCII cows!
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
Get it before SCO does! Linux is open source, if SCO wasn't after the money, it would of sent patches by now!
< BSD is dead >
\ \_______
v__v \ \ O )
(xx) ||----w |
(__) || || \/\
Im a linux user. My cheap Rage 128 is enough for tuxracer.
What this tutorial covers
page 1 of 4
This tutorial shows how to combine Samba and GRUB to build a compact, highly adaptable, cross-platform test network, capable of booting and networking a large number of operating systems on a small number of machines. Though Samba and GRUB can manage many different operating systems, this tutorial focuses on Linux and Windows.
Who should take this tutorial
page 2 of 4
This is neither a networking tutorial, nor a Linux system administration tutorial. Basic knowledge of running Linux and Windows, including user authentication, installing operating systems, partitioning, and managing user accounts will get you going a lot faster. I'll use values that are valid for my system, such as fd0 and hda. I trust that you will use what is correct for your system. What prerequisites you'll need
page 3 of 4
You'll need reasonably modern hardware: PCs four years old and newer ought to do the job. Running multiboot systems requires large hard drives, and support for Large-Block Addressing (LBA). GRUB can read any part of a hard disk supported by true LBA. Unfortunately, a small number of motherboards that claim to support LBA do not, and the only way to find out which ones they are is to try to boot a system from beyond the 1024 cylinder limit. Also needed are a generic Linux boot/rescue disk, such as tomsrtbt, or H. Peter Anvin's SuperRescue CD, and a Windows 98 rescue disk, which is the all-time most useful Windows disk. GRUB does not yet have the ability to boot a CD; we still need floppy disk
Who wrote this tutorial
page 4 of 4
Carla Schroder is a freelance PC tamer, administering Linux and Windows systems for small businesses, and writes how-tos for real people. Loves computers and high tech, thinks Linux/Open Source/Free Software is the best playground in the world. Carla discovered computers and high-tech in 1994; her first PC was an Apple II. She progressed through DOS/Windows, from 3.1 to XP. Discovered Linux in 1998. Carla is living proof that self-taught middle-aged ladies can be fine computer gurus.
You can contact Carla directly, or click Feedback at the top of any panel.
Cross-platform developers face interesting challenges for building testing environments. In my ideal happy world, computer labs are huge, stocked with every little gadget a person might ever need -- even a Segway to scoot around on. But, as we are all painfully aware, resources are more limited in the real world.
One good option is to use excellent programs like VMWare or User-Mode Linux. These create virtual environments for running several operating systems side-by-side on a single PC. (See the Resources for links to more info on VMWare and User-Mode Linux.)
But for users who prefer completely native environments, the open source/free software world gives us two great tools for packing a lot of operating systems into a small space: Samba and GRUB.
Samba enables file and printer sharing between different operating systems. It can be a primary domain controller or a stand-alone server. It is primarily used to network Linux, UNIX, and Windows. Macintosh, OS X, OS/2, and other platforms are supported with varying degrees of tweakage.
GRUB, the Grand Unified Bootloader, is a most remarkable program. GRUB is capable of booting nearly any OS, and nearly any number of them. This tutorial will focus on multibooting and networking Linux and Windows.
Testing in native environments
page 2 of 2
I use a three-PC test network. Thanks to the combined magic of Samba and GRUB, there is enormous flexibility; you can:
Test applications and application servers (in native environments)
Test all manner of networking configurations
Use removable drive trays to swap in and out as needed
Boot bare kernels, passing in parameters and modules from the GRUB command line
You have probably already spotted the one flaw in this beautiful scheme: the inconvenience of rebooting (as only
< FUCK YOU! >
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
__________ /
/ 1) test \
| 2) MOO! |
\ 3)Profit!
----------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
___________________
< can you decompile this! >
--------------------
\ ^__^
\ (oo)\_______
(__)\ )
||----w |
|| ||
But the user is still stupid.