Thanks Ben. This is worth trying just for the education. However, I don't even have an old /etc/hosts that lists the machine's IP. I'd have to try a range... easy to shell script I guess. Other problem: now that I see it has two NIC cards, I don't even remember which one the system is listening to (to plug the cable in). For the time it'd take to figur it out I could just go find a monitor and be done with it.
Someone should come up with a laptop that can serve as keyboard/monitor/mouse for another machine, directly hooked up with the usual cables. Maybe there's a software solution possible for that. Judah On Thu, 21 Jun 2007, Ben Stern wrote: > On Wed, Jun 20, 2007 at 01:11:01AM -0400, [EMAIL PROTECTED] wrote: > > RAM unknown. I can't log into it right now because I reconfigured my > > network since the last time I played with it. I don't have a monitor > > here to put on it. > > If you know the old network number and an unused IP in that range, you can > still connect, although I don't know how much you care. It might be helpful > in future, too. Plug the box into the network, and presuming that this > computer's IP is 192.168.1.5/24, on another box where you have root, > > ifconfig eth0:1 192.168.1.108 netmask 255.255.255.0 > > Then you can ssh to 192.168.1.5 to your heart's content. When you're done, > as root, I've found the most reliable way to get rid of virtual interfaces > is to reconfigure them as: > > ifconfig eth0:1 0.0.0.0 > > ifconfig returns an error and the interface is gone. [Everything else has > caused problems in the past for me.] > > Ben >
