Re: auto laptop interfaces [ was: apt-get update: Could not connect...]

2001-12-17 Thread Chris Halls
On Thu, Dec 13, 2001 at 06:39:15PM -0500, dman wrote: > On Thu, Dec 13, 2001 at 03:30:09PM -0800, Greg Wiley wrote: > | On Thursday, December 13, 2001 1:58 PM, dman wrote: > | > or not). I don't think that can be automated (GPS ;-)?). What I > | > really need to do is configure dhcpd at home some

Re: auto laptop interfaces [ was: apt-get update: Could not connect...]

2001-12-13 Thread dman
On Thu, Dec 13, 2001 at 03:30:09PM -0800, Greg Wiley wrote: | On Thursday, December 13, 2001 1:58 PM, dman wrote: | | > The only problem left (for me) is : how can it automatically | > determine whether or not to use DHCP (that is, is the link from home | > or not). I don't think that can be aut

Re: auto laptop interfaces [ was: apt-get update: Could not connect...]

2001-12-13 Thread Martin Emrich
If anyone is interested - This is my Script to do this job (I've linked it into rc2.d/): (Sorry for the german messages) it detects if my LAN PC Card is plugged in, and if it is, is sets up the network to my Linux Router at home. It also restores the resolv.conf file, because dhclient overwrit

Re: auto laptop interfaces [ was: apt-get update: Could not connect...]

2001-12-13 Thread Greg Wiley
On Thursday, December 13, 2001 1:58 PM, dman wrote: > The only problem left (for me) is : how can it automatically > determine whether or not to use DHCP (that is, is the link from home > or not). I don't think that can be automated (GPS ;-)?). What I > really need to do is configure dhcpd at h

Re: auto laptop interfaces [ was: apt-get update: Could not connect...]

2001-12-13 Thread dman
On Thu, Dec 13, 2001 at 12:51:19PM -0800, Greg Wiley wrote: | On Thursday, December 13, 2001 12:26 PM, dman wrote: | | > Usually this means your network interface isn't up. (like if I turn | > on the laptop, but forget to "sudo ifup eth0" first) | | In case you're interested, here's a strategy

Re: auto laptop interfaces [ was: apt-get update: Could not connect...]

2001-12-13 Thread Greg Wiley
On Thursday, December 13, 2001 12:26 PM, dman wrote: > Usually this means your network interface isn't up. (like if I turn > on the laptop, but forget to "sudo ifup eth0" first) In case you're interested, here's a strategy to configure laptop ethernics automatically--even if you have a hardware

Re: apt-get update: Could not connect...

2001-12-13 Thread dman
On Thu, Dec 13, 2001 at 01:49:50PM -0500, Rudolf Dovicin wrote: | Hello. | When I want to update Packages.gz files by "apt-get update", | I can see messages like: | | Could not connect to http://ftp ... | Err http://ftp ... | Something wicked happend resolving 'ftp ... | Err http://ftp ... Us

apt-get update: Could not connect...

2001-12-13 Thread Rudolf Dovicin
Hello. When I want to update Packages.gz files by "apt-get update", I can see messages like: Could not connect to http://ftp ... Err http://ftp ... Something wicked happend resolving 'ftp ... Err http://ftp ... but I can browse on these servers by lynx. Where is a problem? My /etc/apt/app.con