How to boot headless using a crossover

Post #178,331 by drewk 10/7/04 7:34:40 PM Reply	How to boot headless using a crossover I've got to move files from the old box to the new one. I've got a crossover, but only one monitor and keyboard. I know I should be able to boot the old one headless, connected with a crossover, but I don't know how to get the new one to recognize it. Or rather, I don't know how to get the old one to recognize the connection if I haven't already configured it, or how to configure it headless before it connects. Is this one of those things that I just plug it all in and it works? Asking before I try, because I'll have to unplug the modem to free up the network card to do this. === Implicitly condoning stupidity since 2001.
Post #178,338 by drewk 10/7/04 8:32:19 PM Reply	Well that wasn't what I intended I raided the second nic out of the old box and put it in the new. Plugged the crossover from the (transplanted) second nic into the remaining nic on the old box. Booted, I had no network on the new box. eth0 didn't get a dhcp offer. The just-installed spare nic took over eth0, and I now can't find the original nic. === Implicitly condoning stupidity since 2001.
Post #178,352 by daemon 10/7/04 10:16:31 PM Reply	Re: Well that wasn't what I intended Im confused, you had 2 nics on old, one on new, moved second nic from old to new (assume you took the box down to do this because without a keyboard most bios dont boot, a different issue of course) old nic is now 2nd nic on new eth0 binds to oldnew nic with crossover cable (cant find neworiginal) is the neworiginal nic have a lan cable shoved up its arse? if not the oldnew has a link and so grabs eth0 position? routing? what is pointing at newnew lan route and not applicable to oldnew? regards, daemon
Post #178,376 by drewk 10/7/04 11:49:16 PM Reply	Lemme try again Old box has nic A as eth0 and nic B as eth1. New box has nic C as eth0. I remove nic B from old box and put it in new box. Boot new box and it calls nic B eth0, and I can't get it to recognize that nic C is still there. Doesn't matter what cable I plug into what nic. === Implicitly condoning stupidity since 2001.
Post #178,535 by daemon 10/8/04 8:40:29 PM Reply	Re: Lemme try again Okay, but why do you need 2 nics if you have a crossover cable? plug, put 2 ajacent ip addresses on both boxes and go? regards, daemon
Post #178,539 by drewk 10/8/04 9:22:08 PM Reply	That's not why I did swapped the nics I'm going to be selling the old box to my father-in-law. He won't have any need for two nics. I might, so I'm keeping the spare. The issue of not being able to find the primary nic on the new box is completely separate from the issue of transferring the files. === Implicitly condoning stupidity since 2001.
Post #178,540 by daemon 10/8/04 9:27:50 PM Reply	ROFL, yard it out until after the xfer :-)
Post #178,542 by drewk 10/8/04 9:33:49 PM Reply	Usually I speak ***lish, but that one has me stumped === Implicitly condoning stupidity since 2001.
Post #178,546 by daemon 10/8/04 9:38:50 PM Reply	Re: Usually I speak ***lish, but that one has me stumped If you are only removing the second nic as to deprive the relative of its use, why put in in the box you are keeping until after all other chores (file xfr etc) is done? actually boxlish is fine, I am just avoiding a cursorary inspection regards,
Post #178,583 by drewk 10/9/04 12:28:38 AM Reply	Got it, that was my plan for tomorrow === Implicitly condoning stupidity since 2001.
Post #178,342 by deSitter 10/7/04 9:03:05 PM Reply	Re: How to boot headless using a crossover Null modem, serial to serial, enable serial console support in kernel, set the serial line to 9600,8,n,1 or learn how to pass 38000,8,n,1 on boot. No headless necessary. -drl
Post #178,347 by drewk 10/7/04 9:24:42 PM Reply	Don't have a nullmodem, have a cat5 crossover Besides, I'm trying to do this without hvaing to unplug everything and hook the monitor and keyboard back up to the old one. If I have to configure that one first I will, but I'm asking if there's a way to do this without configuring it first. === Implicitly condoning stupidity since 2001.
Post #178,357 by deSitter 10/7/04 10:49:09 PM 10/7/04 10:51:48 PM Reply	Re: Don't have a nullmodem, have a cat5 crossover The modem is for the console, not the network! You boot headless to the serial console. It's a thing of beauty to watch Linux boot on a VT320. It's almost as good to watch it boot in minicom or Windows telnet :) It's trivial to make a null modem. (Speaking of modem - you should be able to connect a modem to another modem and get a serial connection, though I've never tried it and you'd have to issue the appropriate AT commands to program the modem state.) -drl Edited by deSitter Oct. 7, 2004, 10:51:48 PM EDT Expand All History
Post #178,375 by drewk 10/7/04 11:48:10 PM Reply	I don't have a serial console Or a modem. Or a nullmodem. I'm not going to buy more hardware just to do a one-time data dump. If I can't connect these boxes together through the nics, I'll just boot the old one, tar up what I need, dump it in my yahoo or google accounts, then boot the new machine and grab it. New hardware and making cables is ridiculous. === Implicitly condoning stupidity since 2001.
Post #178,381 by pwhysall 10/8/04 1:47:32 AM Reply	Just remember... ...if your BIOS doesn't support a serial terminal (like pretty much any PC BIOS out there) you'll only pick up the action when getty starts. Peter [link\|http://www.debian.org\|Shill For Hire] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Blog]

Welcome to IWETHEY!