Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
Lots of information in these forums regarding SBC DSL with dynamic IP that I have read. I have 2 hdd's and like the rest, trying to acquire a dual boot setup with SBC dsl on both.
I followed the posts I have read thus far concerning dual boot with 2 HDDS, and this is what I have done. I wiped out 80GB HDD and partitioned in a 70/30 format to use for Windows. The 70 for NTFS and the 30 for Fat32 to be shared data by Linux. I setup Win2k and it boots fine as a single drive. I then took my 2nd HDD which is 40GB and installed Suse 9.0 and it boots fine by itself. I kept the 40GB Suse drive as master, and hooked the Win2k 80GB drive as slave. Both are recognized in CMOS.
I went into /boot/grub and edited the menu.lst to include these parameters at the end of the file:
If I remove the Suse drive, I can still boot to Win2K normally. With a dual boot setup as above, I can boot to Suse 9.0 fine. The problem is, I still get this error when choosing Windows from the Grub gui when trying to dual boot:
rootnoverify (hd1, 0)
Filesystem type unknown, partition type 0x7
Wondering what I may have done wrong...
If that's not bad enough, the other issue is getting DSL with SBC to work in Suse. I have an A7N8X Deluxe motherboard with 2 ethernet onboard ports. The 3com(Eth0) module is loaded, but Yast finds an unconfigured DSL device. The other ethernet port onboard is a Realtek. Do I have to also load a module for the 2nd NIC? Or can the DSL be configured on just the one 3Com?
I have gone to the DSL option in Yast, and entered my user information, but it still cannot connect. I have tried to run adsl-setup, but apparently the SUSE distro doesn't have that. SBC uses 184.108.40.206, 220.127.116.11 and 18.104.22.168 as DNS. I know I may have to add these manually to the resolv.conf, but wasn't sure if I have to have the 2nd(Realtek) NIC module loaded first. I guess my next step may be to try the Roaring Penquin software I have read; or purchase a 4-port Linksys router to configure DHCP for me.
I'm a newb, but I'm learning a lot really quick(thanks to this forum). Thank you all for the time you contribute to the rookies : )
Distribution: RH 6.2, Gen2, Knoppix, 98,2000 + various
it would be easier to set the machine up with both drives in how you're going to use
them from the start.
if you're leaving the windows drive as the primary master, you don't need to remap
anything to boot it. if you're installing linux as the primary master, then moving it to
slave, you don't need to remap anything. you need to edit your /etc/fstab and change
the /dev/hda entries to /dev/hdb. then change your grub conf entries for linux.
you'll then need to do something of your choice to get the machine to boot the
second hard drive. freebsd's booteasy is simple. so would be adding an entry for
linux in boot.ini in windows.
there are several multi-boot howto's on the web you could look at to see what appeals
i don't know enough about the dsl to help you there, but the realtek would use a
different module. you might couldload that and plug your dsl into there and try
If either of you guys were doing this again tonight, how would you set it up? I guess I'm confused with the mbr stuff. I will try it again when I get home, but I really want to understand it all.
If you guys had 2 blank drives in front of you, how would you do it? Would you hook up both drives to pc as master/slave then install the Os? Hook one drive up as single, install Win2k then remove and install Suse as single, making sure both drives boot up correctly to their respective Os's, THEN make a change either to NTLDR or Grub/Lilo? If so, which OS would you have be the master?
Which OS would you make the master? Seems I can either have Win or Lin boot (with both options).
Distribution: RH 6.2, Gen2, Knoppix, 98,2000 + various
>>>Windows must believe that it owns the MBR, or it freaks. I am more partial to the NTLDR >>>method described above, but, it's personal preference.
windows just uses a simple mbr that points to the active partition. that's where the
ntldr is set up. i've been using freebsd's booteasy in my mbr for 6 years. it's really
a partition booter. so i'm going booteasy>ntldr>lilo.
ntldr is a bootsector loader.
i just meant that windows can handle not having the mbr, but it is very jealous,
and will overwrite any other mbr any time you install it.
If I had two HDD's in front of me, and had to do it from scratch with both windows, and linux? I would do what I have.
I have two HDD's, as follows:
30G 7200 RPM Western Digital stock HDD
IDE Master - connected to position one.
Windows XP NTFS System Partition with Win-bootable MBR
80G 7200 RPM Western Digital Add. Drive
IDE Slave - connected to position two.
Partition One - 70G NTFS Windows File Drive (mp3's, web stuff, etc)
Partition Two - 100MB Boot partition mounted at /boot
Partition Three - 512MB Linux Swap
Partition Four - 9+G Slackware Root Partition
I would install lilo to the Superblock of Partition Four (root partition)
I would then do the following:
fdformat -fat /dev/fd0
mount /dev/fd0 /floppy
//* /dev/hdb7 is Partition 4
dd if=/dev/hdb7 bs=512 count=1 of=/bootsect.lin
cp /bootsect.lin /floppy
I would then reboot, into Win XP. Right click on My Computer, and choose properties.
Click the Advanced Tab
Click the Startup and Recovery Options Button
Check the box "Display a list of Operating Systems"
Click the nearby Edit button.
Add the following to the bottom of that file
Now, copy the bootsect.lin file off of your floppy to C:\
You now have a dual boot system that will allow you to keep windows on the MBR, but still have a lilo-like choice.....
The directions are the same for Grub, just install it to the Superblock, and follow the rest accordingly - because we don't have to bother messing with the bootloader - it really doesn't matter which you use - the first 512 of the root drive will still contain enough to boot the OS from the bootsect.lin file.
HEY!!! By the way!!!!! If you for any reason change your boot config AT ALL FOR ANY REASON - you must repeat this process, begiinning at the first command - the whole dd thing - again. If the bootsect.lin file in Windows is even a byte off of what is on the superblock, you will get errors, and the machine will not start - a good rule of thumb, is to do this, right after you change the boot process, and before you restart, otherwise, you may lock yourself out of the machine....
Last edited by PenguinPwrdBox; 02-20-2004 at 11:53 AM.