1 |
On Mon, 26 Sep 2011 18:43:13 -0700 |
2 |
Mark Knecht <markknecht@×××××.com> wrote: |
3 |
|
4 |
> On Mon, Sep 26, 2011 at 5:14 PM, Alan McKinnon |
5 |
> <alan.mckinnon@×××××.com> wrote: |
6 |
> > On Tue, 27 Sep 2011 07:08:05 +0700 |
7 |
> > Pandu Poluan <pandu@××××××.info> wrote: |
8 |
> > |
9 |
> >> On Sep 27, 2011 5:11 AM, "Mark Knecht" <markknecht@×××××.com> |
10 |
> >> wrote: |
11 |
> >> > |
12 |
> >> |
13 |
> >> [-- snip --] |
14 |
> >> |
15 |
> >> > Speaking as someone experienced in running Gentoo but certainly |
16 |
> >> > not a power user - I don't write scripts or program at all - I |
17 |
> >> > gotta say I don't like that way this is all working on my system |
18 |
> >> > so far. TO BE CLEAR, I am SURE that I don't have everything |
19 |
> >> > configured as well as it could possibly be, but I also suspect |
20 |
> >> > that would be true for the majority of new wireless users on |
21 |
> >> > Gentoo after only a day or two. |
22 |
> >> > |
23 |
> > |
24 |
> > Just to throw a small spanner in the works.... |
25 |
> > |
26 |
> > All my wpa issues were solved long ago by dumping the gentoo net |
27 |
> > scripts, then installing and running wicd where it all |
28 |
> > JustWorks(TM). |
29 |
> > |
30 |
> > init.d scripts work great for static servers. |
31 |
> > wicd works great for mobile laptops. |
32 |
> > There's very little overlap between these two. |
33 |
> > |
34 |
> > Have you considered using wicd at all? |
35 |
> > |
36 |
> |
37 |
> Alan, |
38 |
> I haven't seriously considered wicd because I don't understand what |
39 |
> it is, how it links into everything else on the system. |
40 |
> |
41 |
> For a user type the idea of dumping init scripts in favor of |
42 |
> something else is a _really_ foreign idea to me. As someone who has |
43 |
> used Gentoo for at least a decade please understand that I've never |
44 |
> done _anything_ like that before. I'm sure I can figure out more or |
45 |
> less how the scripts work, but there are other things I'd worry about |
46 |
> like some some system update deleting them, etc. |
47 |
> |
48 |
> Reading the wicd homepage it looks like it could help, but how many |
49 |
> hours am I going to have to invest to get it running? Understand that |
50 |
> I've already dumped maybe 10 hours into getting here. I figure I'll |
51 |
> need another 10 hours of work - reading web pages, trying things out |
52 |
> and failing - before I feel like I should ask a question here, so |
53 |
> that's 20 hours minimum. Please understand that wireless was working |
54 |
> on this machine in Windows in under 10 minutes - not 20 hours! |
55 |
|
56 |
Windows does it the right way for a mobile workstation, and wicd |
57 |
follows the same general idea. |
58 |
|
59 |
At boot-up , a wicd daemon starts, this is the thing that does the |
60 |
heavy lifting and runs as root. |
61 |
|
62 |
When the user's DE starts, you run the wicd-client. It comes with a |
63 |
sensible config dialog where you set sensible stuff like |
64 |
|
65 |
wired interface takes priority over wireless |
66 |
use wireless APs that have been sen before in preference to new ones |
67 |
buttons to define pre-and post-connect scripts if you need them |
68 |
|
69 |
when the client has decided what it's gonna do with your connections, |
70 |
it requests the daemon to do it. It's all very well-thought out and |
71 |
obviously designed with the needs of laptop users in mind. Sort of like |
72 |
NetworkManager working properly without the issues of NetworkManager. |
73 |
|
74 |
For me, it all just worked out of the box and connected every time to |
75 |
all APS - WEP, WPA, even the weird funky corporate BS thingy someone |
76 |
installed at work. Took about 10 minutes :-) |
77 |
|
78 |
|
79 |
|
80 |
> |
81 |
> The wicd homepage makes it all look so painless so I guess I should |
82 |
> go give it a try. |
83 |
> |
84 |
> Cheers, |
85 |
> Mark |
86 |
> |
87 |
|
88 |
|
89 |
|
90 |
-- |
91 |
Alan McKinnnon |
92 |
alan.mckinnon@×××××.com |