On Thu, Sep 16, 2004 at 02:48:47PM -0400, Tom Bryan wrote: > On Thursday 16 September 2004 12:13 pm, Mike M wrote: > > > > I had the initial install CD and tried a network install, but the > > > installer was having trouble with name resolution (DNS). I found the > > > network configuration screens confusing (they didn't seem to support > > > DHCP), but perhaps I just have an old copy of the install CD. > > > > > > Anyway, since it's my first Debian install, a set of CDs would be much > > > easier. I'd like to avoid having to order a set if someone in the Raleigh > > > area has them already. I can make it to just about any spot in and > > > around Raleigh tomorrow morning or evening. > > > You can wget CD1 and burn a CD faster than driving to pick one up. > > > > http://www.linuxiso.org/distro.php?distro=4 > > I've got an old Woody CD1 that a friend gave me. Perhaps I need to get a more > recent copy? Does Debian update the installer CDs for their older, more > stable distributions? How do I tell if I have the most recent?
I use an old Woody for initial loading. Use only CD1. You'll get the latest Woody when you complete the load from http (or ftp if you prefer; recall reading http was better for some reason). > > > Boot from CD1 and then choose to load from http during the load > > procedure. > > That was my original intention. > > > You will be loading "stable". Then, depending on what you want to do > > (server or workstation, etc.) you decide to upgrade to "testing" > > or "unstable" (aka, Sid). > > I want "stable" for this box, so no problem there. Then you'll be done a little earler. > > > Loading Debian is more hands-on than FCx, RHx, or the others. The > > payoff is in the (I think) large and consistent repository of > > applications. I have never had a problem with dependency > > conflicts. > > Well, I've used Red Hat since I started running Linux (back with Red Hat 5.2), > but I'm not concerned about the "hands on" nature of the install. My first > few Red Hat installs involved writing an XF86Config file by hand for an > unsupported monitor, creating logical partitions in such a way that the > Windows install on the box could no longer read the partition table, etc. > I've built my own RPMs and written RPM spec files by hand, and I currently > have some time to waste, so....bring it on. You should be comfortable with partioning a HDD for Linux and you'll be fine. > > > Post problems here and we'll help you get through. > > I'm trying to install on the box that will be acting as my firewall and IP > masquerading/forwarding machine at home. It has 2 NICs. I tried to pick the > right drivers during the install, but then I was somewhat baffled by the > network configuration. I was presented with two network interface choices > (tun10 and dummy0, I think), and when I tried to configure one, there was no > "configure via DHCP." The installer wanted an IP address, a gateway machine, > etc. I tried a few combinations (boot from Knoppix and see what IP and DNS > servers Road Runner is assigning to the machine and use those, use an address > on the cable modem's subnet and point to the cable modem's configuration > interface's IP as the "gateway," etc.), but all the installer ever said after > that phase was that it couldn't resolve the DNS name for the Debian > repository on the 'Net. > > I haven't started digging hard for how to get the Debian network install to > the network interface's IP, netmask, DNS servers, etc. from DHCP. I figured > it might be a shorter path to installation if I could get the full CD set as > recommended at http://www.debian.org/distrib/. > > But if you point me to the docs on using DHCP during the installation, I'll > try again. :-) Hang on. I'll fire up an install and report back. I always do static IP but IIRC there is a DHCP option. Ok. Using Deb3.0r1 I get to point where it lets you load device drivers. I enter this menu and then exit. The next screen asks about configuring the network and I enter the hostname. The next screen is entitled "Automatic Netowrk Configuration" where I can choose either DHCP/BOOTP or not. I have an rtl8139 nic in my machine and that driver is built in to the kernel at boot time. That's why I didn't have to do anything in the drive. Your cable modem is probably a DHCP server. My router is a DHCP server and satisfied the installer. I would start out using a single NIC and get the machine loaded. After you have a basic system up and running then you can build your router. refs: ----------------------------------------------------------------------- http://www.debian.org/releases/stable/i386/install http://www.debian.org/doc/manuals/reference/ch-gateway.en.html#s-net-router > > ---Tom > > -- > TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug > TriLUG Organizational FAQ : http://trilug.org/faq/ > TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ > TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc -- Mike Moving forward in pushing back the envelope of the corporate paradigm. -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
