On 18/07/12 22:32, Wookey wrote:
+++ Andrei POPESCU [2012-07-18 20:56 +0300]:
On Mi, 18 iul 12, 15:01:43, Adam Borowski wrote:
A different idea would be to have NM configured by default to do what it can
do well (wifi) and stay away from all other interfaces, but because it has
thorough assump
On 19.07.2012 13:19, Marvin Renich wrote:
> * Michael Biebl [120718 17:31]:
>> You are probably thinking of "update-rc.d remove", which
>> simply removes the start symlinks, wheres disable renames them from S??
>> to K??. This change is preserved during upgrades and invoke-rc.d
>> correctly hand
* Michael Biebl [120718 17:31]:
> On 18.07.2012 22:54, Matt Zagrabelny wrote:
>
> >> Why are people not a aware of that update-rc.d interface? Is this a
> >> general documentation problem?
> >
> > I've been under the impression that future upgrades to the package
> > would re-enable the symlinks
On Mi, 18 iul 12, 21:32:31, Wookey wrote:
> >
> > One of the reasons I'm using network-manager instead of wicd or even
> > plain ifupdown is the possibility to switch (more or less) seamlessly
> > between wired and wifi.
>
> wicd does this just fine too.
In the past I've had problems with wic
On 2012-07-18 21:32:31 +0100, Wookey wrote:
> +++ Andrei POPESCU [2012-07-18 20:56 +0300]:
> > One of the reasons I'm using network-manager instead of wicd or even
> > plain ifupdown is the possibility to switch (more or less) seamlessly
> > between wired and wifi.
>
> wicd does this just fine t
Michael Biebl writes:
> Why are people not a aware of that update-rc.d interface? Is this a
> general documentation problem?
| windlord:~> update-rc.d
| update-rc.d: using dependency based boot sequencing
| update-rc.d: error: not enough arguments
| usage: update-rc.d [-n] [-f] remove
|
On Miércoles, 18 de julio de 2012 21:46:05 Michael Biebl wrote:
> On 18.07.2012 22:32, Wookey wrote:
> > wicd is easy to disable as it has a ENABLE/DISABLE option in
> > /etc/defaults. N-M doesn't so you either have to remove it properly or
> > resort to nobbling the init script.
>
> Nope, you don
On 18.07.2012 22:54, Matt Zagrabelny wrote:
>> Why are people not a aware of that update-rc.d interface? Is this a
>> general documentation problem?
>
> I've been under the impression that future upgrades to the package
> would re-enable the symlinks whereas /etc/default is not touched by
> upgra
On Wed, Jul 18, 2012 at 3:46 PM, Michael Biebl wrote:
> On 18.07.2012 22:32, Wookey wrote:
>
>> wicd is easy to disable as it has a ENABLE/DISABLE option in
>> /etc/defaults. N-M doesn't so you either have to remove it properly or
>> resort to nobbling the init script.
>
> Nope, you don't have to
On 18.07.2012 22:32, Wookey wrote:
> wicd is easy to disable as it has a ENABLE/DISABLE option in
> /etc/defaults. N-M doesn't so you either have to remove it properly or
> resort to nobbling the init script.
Nope, you don't have to "nobble" the init script.
Use "update-rc.d network-manager disa
+++ Andrei POPESCU [2012-07-18 20:56 +0300]:
> On Mi, 18 iul 12, 15:01:43, Adam Borowski wrote:
> >
> > A different idea would be to have NM configured by default to do what it can
> > do well (wifi) and stay away from all other interfaces, but because it has
> > thorough assumptions that it contr
On Mi, 18 iul 12, 15:01:43, Adam Borowski wrote:
>
> A different idea would be to have NM configured by default to do what it can
> do well (wifi) and stay away from all other interfaces, but because it has
> thorough assumptions that it controls all of networking in the system, this
> is not a ch
Adam Borowski writes:
> wicd is used only on machines that use wifi, this excludes most
> desktops.
wicd works fine with wired networks (although yes, I personally wouldn't
install it and would just use ifupdown for systems that have a simple
wired network).
--
Russ Allbery (r...@debian.org)
Jon Dowland writes:
> On Wed, Jul 18, 2012 at 03:31:37PM +0200, Vincent Lefevre wrote:
>> Still, the check would be useful on laptops where wicd is installed and
>> enabled (the user could have a default ifupdown config and wicd
>> enabled).
> What happens if neither wicd nor network-manager are
On Wed, Jul 18, 2012 at 03:31:37PM +0200, Vincent Lefevre wrote:
> Still, the check would be useful on laptops where wicd is installed
> and enabled (the user could have a default ifupdown config and wicd
> enabled).
What happens if neither wicd nor network-manager are installed, and then both
are
On Wed, Jul 18, 2012 at 03:01:43PM +0200, Adam Borowski wrote:
> wicd is used only on machines that use wifi, this excludes most desktops.
wicd can also be used to "manage" different Ethernet configurations.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
On 2012-07-18 15:01:43 +0200, Adam Borowski wrote:
> On Wed, Jul 18, 2012 at 02:18:12PM +0200, Vincent Lefevre wrote:
> > Sorry for being late in the discussion. I also think that having
> > NetworkManager disabled for those who do not want to use it is
> > a good solution. But I think that if othe
On Wed, Jul 18, 2012 at 02:18:12PM +0200, Vincent Lefevre wrote:
> On 2012-07-14 22:59:35 +0200, Tollef Fog Heen wrote:
> > Due to those drawbacks, I've wondered why people don't just disable
> > NetworkManager on their system instead of bothering with workarounds
> > like the above or dpkg -P --fo
On 2012-07-14 22:59:35 +0200, Tollef Fog Heen wrote:
> Due to those drawbacks, I've wondered why people don't just disable
> NetworkManager on their system instead of bothering with workarounds
> like the above or dpkg -P --force-depends and similar.
Sorry for being late in the discussion. I also
19 matches
Mail list logo
