Answer 1:
You're using DHCP to obtain your IP information. One of the things that's happening at the "Bringing up Interface eth0" point in the boot process is that the DHCP client daemon is trying to contact the DHCP server, which will assign your computer a valid IP address for the card (among other things). The daemon will query the network for a specified amount of time before it gives up and returns the "Failed" error. When you're not connected to a network, the daemon is obviously not going to find the server, but it will still keep trying until it reaches the timeout period, hence the hang.
You can take jdevanand's advice about disabling the "on boot" option for your NIC (eth0); it won't affect your modem.
If your modem is a Winmodem (also called software modem, HCF, HSF, or controllerless modem), you're going to have problems. Those modems are designed such that they need to pass off a large part of their processing load to the operating system and CPU. This makes them cheaper to manufacture, but unfortunately, they were designed to work specifically with Windows. This doesn't mean that it's impossible to get a Winmodem to work under Linux, but it's usually a painful proposition. You can go to
linmodems.prg for more details, compatibility info, resurce links, etc.
Answer 2: The Mandrake installer should detect your existing Win partition and automagically put an entry for it in the grub (or lilo) config. file. The install
might let you choose the default OS; if not, the default will be Mandy. As for actually changing the default OS, it's easy enough to find the (simple) instructions on how to do it, so I won't rehash them here.
Answer 3: I'm not even going to touch that one. Let's just say that people have, um, diferring opinions on the subject.
Answer 4: Power management (ACPI/APM) needs to be enabled in both your BIOS and your kernel. You also need to enable the APM daemon (apmd). Your kernel probably has power management support enabled, but if not I'm pretty sure the only option is to recompile the kernel. Assuming the BIOS and kernel do have support enabled, have a look at these
instructions for controlling services in Rh 7.2 to enable apmd.
Answer 5: These are a few ways you can "configure" the kernel:
- pass parameters/options to it at boot time to force certain settings
- install loadable (external) modules to extend it's funtionality.
- recompile it to build in new features and functions.
As for bash, what it is, and what it does, the
Bash Reference Manual sums it up better than I can.
*The best (and fastest) tool for finding Linux resources, answers to questions, etc. is the
Google search engine. Learn how to concisely craft your search keywords and you'll be able get all of the info you need in a very short time.*
