On Thu, May 31, 2007 at 10:14:15PM +0600, Luis Hidalgo wrote: > > I've managed to fix most of the problems, it seems there was some trouble > with some packages that were installed (like fglrx-driver and > nspluginwrapper) that > had some dependency conflicts that prevented gdm and some other programs to > work correctly (I was in the middle of the upgrade). The minimal install > comment > was from the release notes, they call one of the steps that way, it was an > upgrade. The problem I have now is with eth0 and eth1. There was only one > eth (eth0) before > the upgrade. I read the part that said that udev could rename the > interfaces, but the fact is that I don't recall reading anything about > adding a new interface, so I'm looking > into it.
If you happen to have a firewire port, udev will assign it an eth* name since apparently its possible to network with firewire. Use dmesg |grep eth to see what's what. > > With the Network Connection applet there is another issue: it says > SIOCGIFFLAGS error: No such device (I'm not really sure what device it's > talking about anyway) > and it mentions contacting my system administrator (read: me). > I have a well documented (on this list) aversion to using an X app to do system configuration. Also, from past threads, network-manager (whatever it is) can cause contension between the standard config files (what you want) and what it wants (which is what you get). > Doug: > > I don't really understand what you mean when you talk about reconfiguring > debconf (if by that you mean #dpkg-reconfigure debconf) and using redline or > what you said about a serial console (if you could elaborate I'd be very > grateful). What I mean is that if for some reason, messages are flying by before you can read them, and you are already using a console with dialog, and/or you want to log everything, then yes dpkg-reconfigure debconf to priority low and readline (text only like a teletype) interface will be useful. Since the output is plain text with none of the formatting of dialog, you can tee it off to a log file. As for serial console, if you need that log to be on a remote box you have a couple of choices: if the local console screen is OK you can just T the output to the serial port and, using a real null-modem cable, capture it on a spare computer. If you also are having problems with the local console (vt) then you can also set up a getty on that same serial console and use a terminal emulator on a spare computer to access the troubled box and log everything at the same time. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
