Come on ... you know what I meant ;). It was no flame,
it was just reaction to 'if you feel you need to leave
SuSE, do it now' stuff. I'm in development/support
business too but never said anybody anything like this
just because I felt it aint my job to support
particular issue.
As far as watching my back and using tricks I meant
I'm in no way SuSE expert so I used his help and it
took him some time to figure all that wireless pain
out.
Wouldn't you expect more 'expert' answer from somebody
so close to the source as SuSE guy? Ehh, my wireless
interface has never been named wlan0 but rather eth1
so go and figure :).
Anyway, you're right this is open list ...
Martin
--- Anders Johansson
On Thursday 08 May 2003 18:44, Martin wrote:
If you think this answer is any better you're awfully WRONG my friend! Why don't you at least point out some useful url addressing wireless install stuff as we all know it's pain in a neck anyway. It took me few days to make built in wireless card work on my laptop and I had SuSE expert watching my back and I can't say what tricks he had to pull to make that happen anyway.
pull tricks to watch your back?
What's with the bullying? Michael offered that the name of the network device was wlan0, which would be a stumbling block for most newbies (yes, one year is a newbie). That alone was worth the post, IMNSHO
In Brian's case, it looks like the modules are misbuilt, so I don't think any URL would help him. I think he needs to recompile something, but since I don't have any laptops or wireless cards around, I can't really say for certain. Does that mean I shouldn't post this?
This is an open list. "Works for me" posts are perhaps less than useful, but they shouldn't cause flames.
__________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com