Hi there!
On Mon, 02 May 2011 03:03:51 +0200, Fernando Lemos wrote:
2011/5/1 Miroslav Suchý miros...@suchy.cz:
Dne 3.4.2011 18:08, Fernando Lemos napsal(a):
* It doesn't have a good command-line interface
It does have CLI interface. Those commands are bundled directly in
NetworkManager:
Dne 3.4.2011 18:08, Fernando Lemos napsal(a):
* It doesn't have a good command-line interface
It does have CLI interface. Those commands are bundled directly in
NetworkManager:
nm-cli
nm-tool
nm-online
I'm not sure if this qualify as good command-line interface :)
Miroslav Suchy
--
To
2011/5/1 Miroslav Suchý miros...@suchy.cz:
Dne 3.4.2011 18:08, Fernando Lemos napsal(a):
* It doesn't have a good command-line interface
It does have CLI interface. Those commands are bundled directly in
NetworkManager:
nm-cli
nm-tool
nm-online
I'm not sure if this qualify as good
Fernando Lemos fernando...@gmail.com writes:
On Fri, Apr 15, 2011 at 6:50 PM, Felipe Sateler fsate...@debian.org wrote:
Preparing to replace network-manager 0.8.3.999-1 (using .../network-
manager_0.8.3.999-1_amd64.deb) ...
Unpacking replacement network-manager ...
Setting up network-manager
On Sat, Apr 16, 2011 at 07:40:33PM +0200, Stephan Seitz wrote:
On Fri, Apr 15, 2011 at 03:23:32PM +0200, Josselin Mouette wrote:
NM may be good for laptops, so put it in the laptop task and leave the
rest alone in the default installation.
And keep the installer unable to do things as
Hello,
On Fri, 15 Apr 2011 15:47:18 +0200
Stig Sandbeck Mathisen s...@debian.org wrote:
My major gripe with ifupdown is the lack of CIDR in address, but I
can live with that. :)
ifupdown 0.7 does support CIDR.
--
WBR, Andrew
signature.asc
Description: PGP signature
Martin Wuertele m...@debian.org writes:
iface ethX inet static
address x.x.x.x
netmask x.x.x.x
gateway x.x.x.x
up ip rule add
downip rule del
This means that I need to bring the interface down to change routing? Currently
I have
post-up
On Fri, Apr 15, 2011 at 03:32:18PM +0200, Josselin Mouette wrote:
This was stated in the original proposal: ifupdown is not event-based
and does not integrate correctly with modern boot systems.
So what? ifupdown is working on most setups without problems with VLANs
bonds, or bridges out of
On Fri, Apr 15, 2011 at 03:23:32PM +0200, Josselin Mouette wrote:
NM may be good for laptops, so put it in the laptop task and leave the
rest alone in the default installation.
And keep the installer unable to do things as widespread as WPA?
And keep it unable to generate a proper configuration
On Wed, Apr 13, 2011 at 09:47:54PM +0200, Bjørn Mork wrote:
protocols. I would have preferred something like some routers do:
iface eth0
address ..
ipv6address ..
I think this is a very good idea, because you don’t have to duplicate
bridge configurations. If the configuration
Le jeudi 14 avril 2011 à 08:00 +1000, Ben Finney a écrit :
I think it is wrong, based on the fact expressed in these threads that
NetworkManager can, by default during upgrade, bring down the network
connection.
This argument has been rehashed again and again, without ever
confronting it to a
Le mercredi 13 avril 2011 à 11:39 +0200, Stephan Seitz a écrit :
My first (and last) contact with NM was not a good one.
This is another misconception about Network-Manager: since version 0.6
(the first one with which people have been in contact to) was very badly
designed, the current version
Maybe if there was a version number greater than 0.8 people might be more
willing to try network manager again. A rewrite seems like a good reason to
have version 1.0 or maybe 2.0.
The idea of basing version numbers on technical issues only was given up a long
time ago.
--
My blog
On pe, 2011-04-15 at 08:27 +0200, Josselin Mouette wrote:
Le mercredi 13 avril 2011 à 11:39 +0200, Stephan Seitz a écrit :
My first (and last) contact with NM was not a good one.
This is another misconception about Network-Manager: since version 0.6
(the first one with which people have
On 04/13/2011 08:53 PM, Jon Dowland wrote:
Or in other words, if a server user does an attended install via d-i, doesn't
trigger expert mode and accepts the defaults for most questions, is it wrong
if they end up with NetworkManager?
Yes. That is what we have things like the 'Desktop' task
On Fri, Apr 15, 2011 at 08:27:03AM +0200, Josselin Mouette wrote:
Since it was completely redesigned, almost from scratch, this doesn’t
apply for 0.8. Its system daemon is able to manage connections without
anyone logged on, and with a number of features that makes ifupdown look
like a baby toy.
On Fri, Apr 15, 2011 at 05:06:00PM +1000, Russell Coker wrote:
Maybe if there was a version number greater than 0.8 people might be more
willing to try network manager again. A rewrite seems like a good reason to
have version 1.0 or maybe 2.0.
I appreciate your point, but this is
On Fri, Apr 15, 2011 at 08:22:53AM +0200, Josselin Mouette wrote:
Le jeudi 14 avril 2011 à 08:00 +1000, Ben Finney a écrit :
I think it is wrong, based on the fact expressed in these threads that
NetworkManager can, by default during upgrade, bring down the network
connection.
This
On Wed, 13 Apr 2011 19:53:02 +0100, Jon Dowland j...@debian.org wrote:
...
Having said all of the above, and the thread being where it is now, I have to
admit I can't remember what the value proposition was in the first place. Time
to re-read...
So, you just failed to provide any justification
Hi,
On Fri, Apr 15, 2011 at 10:03:40AM +0100, Jon Dowland wrote:
For the record, this was (at least) bugs #432322 and #439917, and I'm
extremely
pleased that the issues have been resolved. Well done and thank you to all
involved.
AIUI they weren't resolved, but the scope of the problem was
Josselin Mouette j...@debian.org writes:
Since it was completely redesigned, almost from scratch, this doesn’t
apply for 0.8. Its system daemon is able to manage connections without
anyone logged on, and with a number of features that makes ifupdown look
like a baby toy.
So Network-Manager
setups
The former works just fine without network-manager, even without any manual
configuration at all. The latter has alternatives that don't mess with
non-wlan interfaces. Thus, what exactly are you trying to fix by installing
network-manager by default?
--
1KB // Microsoft
Bjørn Mork bj...@mork.no writes:
So Network-Manager has finally gained basic features like the ability to
set a lower than default MTU?
How about bridging? VLANs? Unnumbered interfaces? DHCPv6-PD?
Disabling IPv6 SLAAC on a specific interface? Multiple uplinks?
Multiple routing tables?
* Timo Juhani Lindfors timo.lindf...@iki.fi [2011-04-15 14:18]:
ip rule show | grep -Ev '^(0|32766|32767):|iif lo' \
| while read PRIO NATRULE; do
ip rule del prio ${PRIO%%:*} $( echo $NATRULE | sed 's|all|0/0|' )
done
iface ethX inet static
address x.x.x.x
netmask
Martin Wuertele m...@debian.org writes:
* Timo Juhani Lindfors timo.lindf...@iki.fi [2011-04-15 14:18]:
ip rule show | grep -Ev '^(0|32766|32767):|iif lo' \
| while read PRIO NATRULE; do
ip rule del prio ${PRIO%%:*} $( echo $NATRULE | sed 's|all|0/0|' )
done
iface ethX inet static
Hi,
On Fri, Apr 15, 2011 at 02:01:06PM +0200, Bjørn Mork wrote:
Josselin Mouette j...@debian.org writes:
Since it was completely redesigned, almost from scratch, this doesn’t
apply for 0.8. Its system daemon is able to manage connections without
anyone logged on, and with a number of
Stephan Seitz wrote:
NM may be good for laptops, so put it in the laptop task and leave the
rest alone in the default installation.
And keep the installer unable to do things as widespread as WPA?
And keep it unable to generate a proper configuration for laptops?
No thanks.
--
Joss
--
To
On Fri, Apr 15, 2011 at 10:04 AM, Patrick Schoenfeld
schoenf...@debian.org wrote:
I've always believed that peoply chose NM for simplicity. And I can
understand that. It's simple because it doesn't support anything
complex, including common VPN setups.
ifupdown does not support any VPN setup
Philip Hands wrote:
On the other hand, nobody from the Isn't N-M great camp seems willing
to explain why I'd want it in preference to ifupdown on a server,
particularly a co-lo remotely admined server.
This was stated in the original proposal: ifupdown is not event-based and
does not integrate
Timo Juhani Lindfors wrote:
Bjørn Mork bj...@mork.no writes:
How about bridging? VLANs? Unnumbered interfaces? DHCPv6-PD?
Disabling IPv6 SLAAC on a specific interface? Multiple uplinks?
Multiple routing tables? Creating tap interfaces connected to virtual
swiches? Different types of
Björn Mork wrote:
Martin Wuertele m...@debian.org writes:
up ip rule add
downip rule del
The power of the pre-up/up/down/post-down scripting is tremendous.
So is that of NM dispatcher scripts.
What is your gripe, again?
--
Joss
--
To UNSUBSCRIBE, email to
Patrick Schoenfeld schoenf...@debian.org writes:
On Fri, Apr 15, 2011 at 02:01:06PM +0200, Bjørn Mork wrote:
Josselin Mouette j...@debian.org writes:
Since it was completely redesigned, almost from scratch, this doesn’t
apply for 0.8. Its system daemon is able to manage connections without
Björn Mork wrote:
- without reliance on external commands (such as the ip command or shell
scripts) for basic stuff
Which is bad because of what?
Using the ip command or shell scripts is an important feature to me.
I don't want grep, cp, ls etc unified to a single file handling
program
Josselin Mouette j...@debian.org writes:
Björn Mork wrote:
Martin Wuertele m...@debian.org writes:
up ip rule add
downip rule del
The power of the pre-up/up/down/post-down scripting is tremendous.
So is that of NM dispatcher scripts.
And this is documented
Timo Juhani Lindfors timo.lindf...@iki.fi writes:
I'd be interested in seeing real-life ifupdown configurations that
handle these.
Here's an example from one of my servers that handles _some_ of them.
(Addresses rewritten to rfc3330 space, and no explicit IPv6 config):
* Two bonded ethernet
Josselin Mouette wrote:
For a machine with an IP address assigned by DHCP, which is a very common
setup even on servers,
... I have to ask: What sort of overall network setup would you be
using, where server IP addresses are assigned by DHCP?
I'm having trouble imagining any remotely
* Fernando Lemos fernando...@gmail.com [110415 15:26]:
On Fri, Apr 15, 2011 at 10:04 AM, Patrick Schoenfeld
schoenf...@debian.org wrote:
I've always believed that peoply chose NM for simplicity. And I can
understand that. It's simple because it doesn't support anything
complex, including
]] Kris Deugau
| Josselin Mouette wrote:
| For a machine with an IP address assigned by DHCP, which is a very common
| setup even on servers,
|
| ... I have to ask: What sort of overall network setup would you be
| using, where server IP addresses are assigned by DHCP?
Any kind of
On Fri, 15 Apr 2011 10:03:40 +0100, Jon Dowland wrote:
On Fri, Apr 15, 2011 at 08:22:53AM +0200, Josselin Mouette wrote:
Le jeudi 14 avril 2011 à 08:00 +1000, Ben Finney a écrit :
I think it is wrong, based on the fact expressed in these threads
that NetworkManager can, by default during
On Fri, Apr 15, 2011 at 6:50 PM, Felipe Sateler fsate...@debian.org wrote:
Could those thread participants who have gripes from their last NM
experience many years ago please confirm that their gripes still apply
before continuing with the discussion?
felipe@pcfelipe:supercollider% apt-cache
On 04/04/2011 12:56 PM, Jon Dowland wrote:
On Sun, Apr 03, 2011 at 07:22:47PM +0300, Faidon Liambotis wrote:
It also can't do VLANs (.1q), bridges, bonds and all possible
permutations of the above. I'd speculate that it also wouldn't be able
to do things like 1k (or more) interfaces. It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2011-04-13 10:53, Bernd Zeimetz wrote:
Yes. For a distribution which is targeted to support servers properly, yes,
definitely. For everything else there is Ubuntu.
The universal OS is only running on servers. Check.
- --
brother
On Mon, Apr 04, 2011 at 11:56:23AM +0100, Jon Dowland wrote:
On Sun, Apr 03, 2011 at 07:22:47PM +0300, Faidon Liambotis wrote:
It also can't do VLANs (.1q), bridges, bonds and all possible
permutations of the above. I'd speculate that it also wouldn't be able
to do things like 1k (or
On Wed, Apr 13, 2011 at 11:11:27AM +0200, sean finney wrote:
Did i miss the part where somebody explained what the user benefit of
having network-manager on a server was? (apart from then it's the same
as your desktop[1], anyway).
I don’t even know why NM should be on a normal desktop.
My
On 04/13/2011 10:56 AM, Martin Bagge / brother wrote:
On 2011-04-13 10:53, Bernd Zeimetz wrote:
Yes. For a distribution which is targeted to support servers properly, yes,
definitely. For everything else there is Ubuntu.
The universal OS is only running on servers. Check.
Get your facts
On Wed, 13 Apr 2011 10:53:13 +0200, Bernd Zeimetz wrote:
On 04/04/2011 12:56 PM, Jon Dowland wrote:
On Sun, Apr 03, 2011 at 07:22:47PM +0300, Faidon Liambotis wrote:
It also can't do VLANs (.1q), bridges, bonds and all possible
permutations of the above. I'd speculate that it also wouldn't be
On Wed, Apr 13, 2011 at 11:26:06AM +, Felipe Sateler wrote:
On Wed, 13 Apr 2011 10:53:13 +0200, Bernd Zeimetz wrote:
Yes. For a distribution which is targeted to support servers properly,
yes, definitely. For everything else there is Ubuntu.
Surely a person managing a server can do
On 13/04/2011 10:53, Bernd Zeimetz wrote:
On 04/04/2011 12:56 PM, Jon Dowland wrote:
On Sun, Apr 03, 2011 at 07:22:47PM +0300, Faidon Liambotis wrote:
It also can't do VLANs (.1q), bridges, bonds and all possible
permutations of the above. I'd speculate that it also wouldn't be
able to do
On Wed, Apr 13, 2011 at 01:42:43PM +0200, Mehdi Dogguy wrote:
On 13/04/2011 10:53, Bernd Zeimetz wrote:
On 04/04/2011 12:56 PM, Jon Dowland wrote:
On Sun, Apr 03, 2011 at 07:22:47PM +0300, Faidon Liambotis wrote:
It also can't do VLANs (.1q), bridges, bonds and all possible
permutations of
On Wed, 13 Apr 2011 11:26:06 + (UTC), Felipe Sateler fsate...@debian.org
wrote:
On Wed, 13 Apr 2011 10:53:13 +0200, Bernd Zeimetz wrote:
On 04/04/2011 12:56 PM, Jon Dowland wrote:
On Sun, Apr 03, 2011 at 07:22:47PM +0300, Faidon Liambotis wrote:
It also can't do VLANs (.1q), bridges,
On Wed, Apr 13, 2011 at 01:39:38PM +0100, Philip Hands wrote:
Surely a person managing a server can do aptitude install ifupdown
network-manager-?
You appear to want to inflict extra work on large swathes of our
users. If that is the case, I'd like to see some sort of justification
for
Stephan Seitz stse+deb...@fsing.rootsland.net writes:
The only thing that I miss from ifupdown (and I configured bonds,
bridges and vlans) is a good IPv6 support. I can’t separately activate
or deactivate IPv4 or IPv6 parts of an interface.
I have seen several requests for this feature, but I
Jon Dowland j...@debian.org writes:
Does the following assumption hold?
Desktop users favour fewer prompts at install time and more sane
default choices. Server users want fine control over the nuances of
installation, but harness additional technologies/options to help with
installations
On Thu, Apr 07, 2011 at 02:11:38PM +0200, Michelle Konzack wrote:
Installing NM by default will break systems which where running the last
12 years without flaws.
No, it will not. It will not impact *running* systems at all. It will only
impact newly installed systems.
--
To UNSUBSCRIBE,
On Thu, Apr 07, 2011 at 02:18:38PM +0200, Michelle Konzack wrote:
This is Exacly what I mean with NM. I do not wan to be bothered with
reading some hours documentations on how to tweek NM to work with my
four 10GE NICs.
And you wouldn't be - because, once again - you are not forced to
Hello Jon Dowland,
Am 2011-04-11 10:37:54, hacktest Du folgendes herunter:
On Thu, Apr 07, 2011 at 02:11:38PM +0200, Michelle Konzack wrote:
Installing NM by default will break systems which where running the last
12 years without flaws.
No, it will not. It will not impact *running*
with the same set of misconceptions and
misunderstandings. Please carefully read the thread again before re-iterating
any more mistakes!
This thread is talking about network-manager as default which is
definitively no go.
Thanks, Greetings and nice Day/Evening
Michelle Konzack
, that would lead to NM being
installed by default on both cases.
This thread is talking about network-manager as default which is
definitively no go.
*shrug*
--
.''`. Josselin Mouette
: :' :
`. `'
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject
Zitat von Stanislav Maslovski stanislav.maslov...@gmail.com:
On Wed, Apr 06, 2011 at 10:51:08PM +0200, Hendrik Sattler wrote:
Am Mittwoch 06 April 2011, 19:05:11 schrieb Stanislav Maslovski:
On Wed, Apr 06, 2011 at 07:29:05AM +0200, Josselin Mouette wrote:
Then you can stack all soft of
Hello Philip Hands,
Am 2011-04-06 10:13:19, hacktest Du folgendes herunter:
I think this is the vital difference -- those that prefer ifupdown do so
because they prefer to be in tight control of what is happening on their
systems, whereas those that prefer NM don't want to be bothered about
Hello Hendrik Sattler,
Am 2011-04-07 12:56:33, hacktest Du folgendes herunter:
I am also not totally happy about network-manager but I still use it
as it gives me a working wireless network on my laptop without
having to spend hours reading endless documentation and writing
multiple
Hello,
On Wed, 06 Apr 2011 07:29:05 +0200
Josselin Mouette j...@debian.org wrote:
Your limited knowledge is like jam. The less you have, the more you
spread it.
Well, you have just confirmed this statement.
What you actually like about ifupdown is that it cannot do anything
but extremely
On 06 Apr 09:10, Andrew O. Shadoura wrote:
Hello,
On Wed, 06 Apr 2011 07:29:05 +0200
Josselin Mouette j...@debian.org wrote:
Your limited knowledge is like jam. The less you have, the more you
spread it.
Well, you have just confirmed this statement.
What you actually like about
On Wed, 06 Apr 2011 07:29:05 +0200, Josselin Mouette j...@debian.org wrote:
... and since it’s not event-based you have to hard-code the way your
network is set up.
I think this is the vital difference -- those that prefer ifupdown do so
because they prefer to be in tight control of what is
Hi,
On 2011-04-05 20:37:39 +0300, Andrew O. Shadoura wrote:
Hello,
On Tue, 5 Apr 2011 14:31:40 +0200
Vincent Lefevre vinc...@vinc17.net wrote:
[About the general problem of documentation]
The problem is to find the correct tools and the correct
documentation. For instance, imagine
On 2011-04-06 07:24:30 +0200, Josselin Mouette wrote:
There are several hacks to do that (like guessnet or laptop-net), but I
don’t think this can work correctly in the general case with IPv4.
FYI, I had used laptop-net in the past, but it has been removed
from Debian:
On Wed, Apr 06, 2011 at 02:11:35PM +0200, Vincent Lefevre wrote:
On 2011-04-06 07:24:30 +0200, Josselin Mouette wrote:
There are several hacks to do that (like guessnet or laptop-net), but I
don’t think this can work correctly in the general case with IPv4.
FYI, I had used laptop-net in
Brett Parker idu...@sommitrealweird.co.uk writes:
Everything that you can do with ifupdown you can do with network
manager,
That's simply not true.
You cannot use n-m remotely without having some out-of-band access.
For a start. Fix that, and I'll come back with the next issue. You
don't
Stanislav Maslovski stanislav.maslov...@gmail.com (Sun Apr 3 12:37:26 2011):
On Sun, Apr 03, 2011 at 10:11:03AM +0200, martin f krafft wrote:
But if network-manager would become default and ifupdown an optional
replacement, I would question Debian's capacity to make technically
excellent
Hello,
On Wed, 6 Apr 2011 13:40:43 +0200
Vincent Lefevre vinc...@vinc17.net wrote:
That's not sufficient, because if a DHCP client is still running (e.g.
because the previous configuration used DHCP), one needs to kill it
before using a fixed IP address (in eth-home).
If you do `ifdown`,
On Wed, Apr 6, 2011 at 9:45 AM, Heiko Schlittermann h...@schlittermann.de
wrote:
Stanislav Maslovski stanislav.maslov...@gmail.com (Sun Apr 3 12:37:26
2011):
On Sun, Apr 03, 2011 at 10:11:03AM +0200, martin f krafft wrote:
But if network-manager would become default and ifupdown
* 2011-04-06T16:45:03+02:00 * Heiko Schlittermann wrote:
Stanislav Maslovski stanislav.maslov...@gmail.com (Sun Apr 3
12:37:26 2011):
On Sun, Apr 03, 2011 at 10:11:03AM +0200, martin f krafft wrote:
But if network-manager would become default and ifupdown an optional
replacement, I would
On Wed, Apr 06, 2011 at 07:29:05AM +0200, Josselin Mouette wrote:
Le mardi 05 avril 2011 à 02:08 +0400, Stanislav Maslovski a écrit :
Well, that is not the question of how many, that is the question of
can you do a given task or not with a given tool. NM is limited in all
possible ways I
On Wed, Apr 06, 2011 at 07:29:05AM +0200, Josselin Mouette wrote:
Then you can stack all soft of stuff on top of it, and get them to
work manually for your specific setup, and since it’s not event-based
you have to
Am Mittwoch 06 April 2011, 19:05:11 schrieb Stanislav Maslovski:
On Wed, Apr 06, 2011 at 07:29:05AM +0200, Josselin Mouette wrote:
Then you can stack all soft of stuff on top of it, and get them to
work manually for your specific setup, and since it’s not event-based
On 2011-04-06 18:26:45 +0300, Andrew O. Shadoura wrote:
If you do `ifdown`, either manually or by unplugging the cable, the
problem doesn't appear to exist. Calling ifupdown may be inserted into
the suspend/resume scripts.
I wonder why this isn't done by default.
--
Vincent Lefèvre
On Wed, Apr 06, 2011 at 10:51:08PM +0200, Hendrik Sattler wrote:
Am Mittwoch 06 April 2011, 19:05:11 schrieb Stanislav Maslovski:
On Wed, Apr 06, 2011 at 07:29:05AM +0200, Josselin Mouette wrote:
Then you can stack all soft of stuff on top of it, and get them to
work manually for your
* Josselin Mouette j...@debian.org [110404 14:05]:
It seems to be a common belief between some developers that users should
have to read dozens of pages of documentation before attempting to do
anything.
You mix two things up here: Almost noone demands a system that is only
configurable after
In other news for Tue, Apr 05, 2011 at 08:15:55AM +0200, Bernhard R. Link has
been seen typing:
But what many people[1] want is that you can make it work if you read some
dozen pages of documentation.
Personally, what I want is a setup that does not drop all active network
interfaces during a
Jon Dowland wrote:
On Sun, Apr 03, 2011 at 07:22:47PM +0300, Faidon Liambotis wrote:
It also can't do VLANs (.1q), bridges, bonds and all possible
permutations of the above. I'd speculate that it also wouldn't be able
to do things like 1k (or more) interfaces. It also doesn't support hooks
to
On 2011-04-04 17:31:18 +0400, Stanislav Maslovski wrote:
On Mon, Apr 04, 2011 at 05:35:10PM +0530, Josselin Mouette wrote:
It seems to be a common belief between some developers that users should
have to read dozens of pages of documentation before attempting to do
anything.
I’m happy
On Tue, Apr 05, 2011 at 02:31:40PM +0200, Vincent Lefevre wrote:
On 2011-04-04 17:31:18 +0400, Stanislav Maslovski wrote:
On Mon, Apr 04, 2011 at 05:35:10PM +0530, Josselin Mouette wrote:
It seems to be a common belief between some developers that users should
have to read dozens of pages
Hello,
On Tue, 5 Apr 2011 14:31:40 +0200
Vincent Lefevre vinc...@vinc17.net wrote:
[About the general problem of documentation]
The problem is to find the correct tools and the correct
documentation. For instance, imagine the average user who wants for
Ethernet (eth0), to do the following
On 2011-04-05, Andrew O. Shadoura bugzi...@tut.by wrote:
Of course, man guessnet. Just few lines.
Last time I looked guessnet was orphaned, though.
Kind regards
Philipp Kern
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hi,
Am Dienstag, den 05.04.2011, 17:48 + schrieb Philipp Kern:
On 2011-04-05, Andrew O. Shadoura bugzi...@tut.by wrote:
Of course, man guessnet. Just few lines.
Last time I looked guessnet was orphaned, though.
but still very useful and allowing me to have a great network setup
that,
#include hallo.h
* Kelly Clowers [Mon, Apr 04 2011, 02:06:01PM]:
On Mon, Apr 4, 2011 at 07:29, Sune Vuorela nos...@vuorela.dk wrote:
I don't consider myself 'stupid user', but I haven't yet been able to
put my laptop on wpa network without the use of network manager.
I never did get nm or
Le mardi 05 avril 2011 à 14:31 +0200, Vincent Lefevre a écrit :
For instance, imagine the average user who wants for Ethernet (eth0),
to do the following automatically (for a laptop):
1. use some fixed IP address if there's some peer 192.168.0.1
with some given MAC address;
There are
Le mardi 05 avril 2011 à 02:08 +0400, Stanislav Maslovski a écrit :
Well, that is not the question of how many, that is the question of
can you do a given task or not with a given tool. NM is limited in all
possible ways I can imagine, and also buggy. On the contrary, with
ifupdown, one for
On 08:18 Mon 04 Apr , Raphael Hertzog wrote:
RH Hi,
RH On Mon, 04 Apr 2011, Dmitry E. Oboukhov wrote:
Stupid scheme (intended for stupid users) should be based on ifupdown
but shouldn't replace it.
RH Please refrain from calling people stupid users just because they use a
RH software that
On Mon, Apr 04, 2011 at 10:52:33AM +0400, Dmitry E. Oboukhov wrote:
On 08:18 Mon 04 Apr , Raphael Hertzog wrote:
RH Hi,
RH On Mon, 04 Apr 2011, Dmitry E. Oboukhov wrote:
Stupid scheme (intended for stupid users) should be based on ifupdown
but shouldn't replace it.
RH Please refrain
On Mon, 4 Apr 2011 00:00:01 -0700
Steve Langasek vor...@debian.org wrote:
There was a way User can do anything, the way was replaced by the way
User can do something in list. Obviously that this action has been
done for stupid users.
Yes, a user can do anything with ifconfig if his time
On Mon, Apr 04, 2011 at 12:00:01AM -0700, Steve Langasek wrote:
On Mon, Apr 04, 2011 at 10:52:33AM +0400, Dmitry E. Oboukhov wrote:
Yes, a user can do anything with ifconfig if his time has no value. I am
happily using network manager on my laptop, because unlike ifconfig it's
easy to
In other news for Sun, Apr 03, 2011 at 07:20:18PM +0200, Patrick Matthäi has
been seen typing:
Am 03.04.2011 18:22, schrieb Faidon Liambotis:
And, above all, losing the network configuration, even for a second,
just because you restarted a daemon (or that daemon died) shouldn't be
On Mon, Apr 04, 2011 at 12:00:01AM -0700, Steve Langasek wrote:
On Mon, Apr 04, 2011 at 10:52:33AM +0400, Dmitry E. Oboukhov wrote:
On 08:18 Mon 04 Apr , Raphael Hertzog wrote:
RH Hi,
RH On Mon, 04 Apr 2011, Dmitry E. Oboukhov wrote:
Stupid scheme (intended for stupid users) should
On Sun, Apr 03, 2011 at 07:22:47PM +0300, Faidon Liambotis wrote:
It also can't do VLANs (.1q), bridges, bonds and all possible
permutations of the above. I'd speculate that it also wouldn't be able
to do things like 1k (or more) interfaces. It also doesn't support hooks
to be able to do
On Mon, Apr 04, 2011 at 01:11:15AM +0400, Stanislav Maslovski wrote:
Why on earth would I do that? It does not match my needs at all. For
instance, this laptop sometimes connects to a couple of remote LANs
through VPNs, so that I have to set up routing in a not completely
trivial manner.
I
On Mon, 4 Apr 2011, Neil Williams codeh...@debian.org wrote:
There needs to be a simple tool with few dependencies and there needs
to be a complex solution with all the power that some users need. One
tool does not suit all here. It's not just about daemon vs GUI frontend
or whether to use
Le lundi 04 avril 2011 à 11:55 +0400, Stanislav Maslovski a écrit :
Well, actually configuring a wireless network with wpa_supplicant and
ifupdown is not hard at all and does not require too much time, _if_ a
user has developed a good habbit of reading documentation first.
It seems to be a
On Mon, Apr 04, 2011 at 09:59:43PM +1000, Russell Coker wrote:
On Mon, 4 Apr 2011, Neil Williams codeh...@debian.org wrote:
There needs to be a simple tool with few dependencies and there needs
to be a complex solution with all the power that some users need. One
tool does not suit all
Well, actually configuring a wireless network with wpa_supplicant and
ifupdown is not hard at all and does not require too much time, _if_ a
user has developed a good habbit of reading documentation first.
JM It seems to be a common belief between some developers that users should
JM have to
1 - 100 of 143 matches
Mail list logo
