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 |
A couple of things. M1X is a bit non-standard. When I initially ran SuSE 6.0, it came up fine, then 6.1 wouldn't come up. I found a solution last summer after I came back from Tenessee. See if you have a file, /var/state/dhcp/dhclient.leases. I'll send you a copy of mine, that yould fix your problem. You set up the IP masq parameters in the RC.CONFIG file through YaST. System Administration/Change Configuration File. For the most part, I have found SuSE to be more complete and stable than Red Hat. David Kramer wrote: > I installed Suse this weekend. I have to say I was disappointed in the > install procedure. Yast2 did not let me change what partitions I wanted > to use for what, so I had to use yast. It wanted to install so many > packages, it would not fit in 2G. I had to pare it down by hand. I > also > see no way of configuring masquerade or firewall within yast or KDE. > > Anyway, dhclient would not get an IP address from M1X. This is, of > course, a showstopper for me. The error message was "no DHCPOFFERs > received". I tried running it in the foreground with -d, and editing > dhclient.conf to increase timeouts, etc. No go. > > I know someone in roadrunner.techtalk.linux replied that it worked fine > for him, but I > don't see how it could work for him but not me. -- Jerry Feldman <gaf at blu.org> Boston Linux and Unix user group http://www.blu.org - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |