HolgerH

Sorry, r3j3s, I have to disagree. M$FT want to be on the first Harddisk, that's true but the first Harddisk is not necessarily the primary master - confusing, eh ? With LILO (or even GRUB) you can define which Disk will be seen by M$FT to be the first. For LILO the sequence is: map-drive = 0x80 to = 0x81 map-drive = 0x81 to = 0x80 This should be part of your Windows Boot section in LILO and it exchanges the first Harddisk with the second. The benefit is that you can install M$FT's chaos on the second Harddisk as danleff described and you will not loose your LILO or GRUB boot-installation (MBR) as otherwise usual. So this way of installing WinX onto the second Harddisk is my preferred one since quite a while. PS The comparable command for GRUB is: map (hd0) (hd1) map (hd1) (hd0) have a lot of fun

Disabling a network interface ? Nothing easier than this: If you want to swich off "eth0", for example, enter "ifconfig eth0 down" in a terminal window and you're done, independent from the distro. But "ifconfig eth0 up" does not necessarily bring it up again... It depends from your distro. Probably the most common way is "/etc/init.d/network start". But please don't take me for guilty, not all distro's are eaqual and thus your mileage may vary. Looking into "/etc/init.d" is always a good idea, of course.

which is better ? it depends, mainly from you ;-) I prefer GRUB very much over LILO because I hate the need for a dedicated install step ( call "lilo" ). And LILO will not accept any modification as soon as the system has been shut down. If you configured somthing wrong then you're lost during the next boot. Trying different boot options may become a nightmare... GRUB is totally different - as long as you understood how it works basically - so it is very much recommended to read the good manual ! After this you just need one small bootpartition where the different GRUB files reside plus the configuration file "menu.lst" and you're done (btw. a separate boot partition is recommended for LILO too). Any misconfiguration happend occasionally ? No prob, boot, go into GRUB's edit-mode ( "ESC" ) and change whatever you need to - then go ahead with "b" for boot. You can even boot a system without a boot entry at all - just a few command line entries. But you need to understand how it works - so if you're not keen to learn too much about it it's probably the best to follow your distro's default. One last remark for GRUB newbies - take special care about the different naming of harddisks used by GRUB in opposit to Linux: GRUB Linux hd0 hda hd0,0 hda1 hd1,1 hdb2 etc. etc. - in the command mode GRUB lists you nearly everything - so make a bootdisk an play a bit with it, you will have a lot of options and flexibility by far much more than with the good old LILO. But one question remains: is it worth ? The answer depends from you.

Hi Jmax3, just a small hint regarding your Grub problem. you're writing about your configuration: rootnoverify (hda1,0) chainloader +1 savedefault assumed this is correct then it's clear why it will not work (I had the same prob several times ...) Grub is using another HD naming convention: Grub Linux hd0 hda hd0,0 hda1 hd1 hdb etc. etc. So your "hdb1" should be called "hd1,0" in the Grub menu.

Hi egorgry, you're right and you're not ;-) The automagicallity behind the fstab is not because it's Debian, it's because Knoppix is originally intended to run from a CD. Thus it cannot know about each and every partition of each and every computer where it may be started. The guy who wrote the "knoppix-install" afterwards probably forgot to change this automatism or he intended to keep it as a feature. The solution is "nofstab" as boot parameter. CU

Hi talkalooniee, what is your status now? In the beginning it may be difficult to understand what's going but you should tell a bit more about your problem. Just "i cant boot ..." doesn't say so much. Does the machine stop? - what message on screen then? Is it rebooting over and over? - probably some messages on screen? - if so, which? Imagine you yourself should answer your questions from remote. CU HolgerH

Hi egorgry, from the point on when you have "nofstab" as a boot parameter, Knoppix will not apply any automatisms on the fstab - it'll keep your fstab as it is then. Any changes from before will stay so you can leave what Knoppix added or change it as well - you're on your own now. In plain words, if you want to use any specific directory, you have to ensure it exists ... (mkdir blablabla) But this can be done whenever you want, after you booted Knoppix with "nofstab" CU HolgerH

Hi LinuxCrusader, put a "nofstab" as kernel option into your bootloader config and the automagically handling of fstab will go. (search the web for -> Knoppix -> cheatcodes) HolgerH