| 1 |
On 09/07/14 01:58, João Jerónimo wrote: |
| 2 |
> |
| 3 |
> Em 08/07/2014 21:39, J. Roeleveld escreveu: |
| 4 |
>> On 8 July 2014 18:49:19 CEST, "João Jerónimo" <joao.jeronimo.89@×××××.com> |
| 5 |
>> wrote: |
| 6 |
>>> I installed the uclibc stage3 tarball no a x86 machine (I chose uclibc |
| 7 |
>>> because the PC has only 256 MB of RAM). I'm currently trying to install |
| 8 |
>>> NetworkManager, but I ran into a problem, which is: NetworkManager |
| 9 |
>>> needs 'policykit' USE flag to be applyed to consolekit package. This |
| 10 |
>>> pulls-in policykit package as a dependency of consolekit, which in turn |
| 11 |
>>> doesn't compile because it calls some funcions that uclibc doesn't |
| 12 |
>>> implement. |
| 13 |
>>> |
| 14 |
>>> Can't I install networkmanager in uclibc systems, then? |
| 15 |
>> Didn't check the ebuilds, but with what you described. I don't think you can |
| 16 |
>> use NetworkManager with uclibc. |
| 17 |
>> |
| 18 |
>> Apart from that. With only 256MB memory. I would be reluctant to use tools |
| 19 |
>> with large dependencies. |
| 20 |
> Thanks. |
| 21 |
> But... That sucks... |
| 22 |
> Can you tell me if there is an alternative to NetworkManager? |
| 23 |
> Or else, can wpa_supplicant connect to networks that are not statically |
| 24 |
> configured in config files? |
| 25 |
> |
| 26 |
> JJ |
| 27 |
> |
| 28 |
> |
| 29 |
wpa_supplicant[qt4] has an interface, wpa_gui. To use it, add yourself to the |
| 30 |
wheel group (or any relevant group of your choice) and prepend the following |
| 31 |
lines in your /etc/wpa_supplicant/wpa_supplicant.conf file: |
| 32 |
|
| 33 |
ctrl_interface=/var/run/wpa_supplicant |
| 34 |
ctrl_interface_group=wheel |
| 35 |
update_config=1 |
| 36 |
|
| 37 |
After logging in and out you should be able to easily add and connect to any |
| 38 |
network via wpa_gui. What you do not get to change via that interface is how |
| 39 |
the IP address is resolved, but that should not be an issue if you are OK with |
| 40 |
using DHCP. |
Archives