Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Enable serial console on the server. Then you can attach your laptop to the server using a null-modem cable, and log in through there. If you're laptop doesnt' have a serial port, there are usb to serial adaptors available. You probably have documentation available on how to set this up in /usr/src/linux/Documentation/serial-console.txt. Alternatively, you could write a script that checks for certain bad situations on your server (sshd down, no interface, etc), and have it run on a regular basis. If you do something stupid, the script might fix it... assuming it's one of the bad things you programmed it to know about. On Wed, 2003-05-14 at 18:58, Duane Morin wrote: > When I take the laptop in to the office I execute an "ifdown eth0" > before going home so that I dont accidentally try to fire up some > net-sensitive app and have to wait for a timeout. > > Today I did that from a terminal window and found myself saying > "Why is it taking so long?" before realizing that i had accidentally > done it in a window where I was ssh'd in to the server. That smarts. > > What do people do in a situation like that? The machine in my > basement has no head, and the only monitor in the house is my > flatscreen up in the office. So doing stuff local on the server > means having to take apart my Windows machine and lug the monitor > downstairs, possibly just to issue a 3 second command. > > Duane > > > _______________________________________________ > Discuss mailing list > Discuss at blu.org > http://www.blu.org/mailman/listinfo/discuss
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |