Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: richardgao on October 29, 2009, 09:50:00 PM
-
Hi all,
I am working on rebuilding NetworkManager(provide by gnome) source to work on Tinycore,but meet a lot of problems~~~ ??? ??? :'( :'(~~~
Has anyone successfully rebuild NetworkManager(Gnome) for Tinycore? Would you please be kindly to show me some info ?
3Q for your time!!
info about gnome NetworkManager:http://projects.gnome.org/NetworkManager/developers/
-
nobody has done the work ? :'( :'( :'(
my mail :gaodehua1985@163.com
-
I haven't looked at this, but it's more than likely it will have a lot of dependencies for not a lot of functionality - did you try to compile it?
-
I haven't looked at this, but it's more than likely it will have a lot of dependencies for not a lot of functionality - did you try to compile it?
yes ,i am trying to rebuild it ,but as you said ,i meet a lot of dependencies~~~
I am on the way~~~if succeed ,i will share info~~~~
-
Before I created wifiradar extension looked around for a usable network manager. After a short try I gave up NetworkManager due to it's dependencies and also I was not sure that it will bring any benefit compared to wifiradar or WICD, wich was working at that time.
-
benefits could be for 3G
-
WICD is definitely a viable option for all your networking needs and its really lightweight compared to networkmanager.
-
what's better in wicd compared to wifi-radar which is already on the repo?
-
what's better in wicd compared to wifi-radar which is already on the repo?
1) WPA setup is built-in, no need to edit wpasuplicant config file
2) Can manage wired setup, not only wireless
-
./configure --prefix=/usr/local --with-distro=none
...
Your distribution (none) is not yet supported! (patches welcome)
-
As far as i know, WICD uses wpa_supplicant as its backend. And also writes its own config file for each connection that you set up (it's been a while since i've used it though, it may have changed now).
-
Another GUI network manager is wpa_gui from wpa supplicant; I hear it's both good and, being from the same author, supports WPA perfectly.
-
Just took a closer look on NetworkManager. It looks really good and feature reach. There are few missing dependencies which I already solved. The main issue, it depends on HAL and require PolicyKit installed and it can not be disabled. HAL is compiled with no PolicyKit, and adding PolicyKit to HAL and TC is causing other issues. For examply PolicyKit need PAM, PAM need ... So, it is not an easy and fast job.
-
You're a braver man than me - I had a look and gave up...
-
:) Wether you like HAL or not, sooner or later you just need it to get certain applications up and running. Problem is that many application writers simply expect HAL is already there. This whole PolicyKit, ConsoleKit and HAL stuff is overcomplicated and targeting multiuser desktop systems (corporate ?) and doesn't fit to TC or other small systems. J
ust tried FEDORA 12 LXDE spin. It is a 450MByte installable LIVE! CD with LXDE. It comes with NetworkManager by default...
-
Nokia's connman is made as an alternative to networkmanager - should be easier with the deps.
edit: BlueZ, wpa_supplicant and udhcpc as required deps, plus udev, policykit, resolvconf as optional.
-
Sounds interesting. According to README
In order to compile Connection Manager you need following software packages:
- GCC compiler
- GLib library
- D-Bus library
- udev library (optional)
- PolicyKit (optional)
- PPP support (optional)
BlueZ can be enabled or disabled at compile time as many other options.
-
I just read the web page :)