On Sat, 16 Jun 2012 13:47:38 -0400, Gilbert Sullivan wrote: > On 06/16/2012 01:28 PM, Camaleón wrote:
>>> Matthew pointed out that my use of netscript 2.4 is sort of >>> non-standard for a regular Debian desktop. >> >> (...) >> >> And he is right. >> >> The first thing I would do is removing that package if you don't need >> it at all (I don't have it installed, BTW, and running "apt-cache >> rdepends netscript" returns void so no other package seems to depend on >> it). >> >> > Well, I'm in the situation of not being sure whether or not it's a good > idea for me to remove netscript 2.4 and go back to ifupdown. You have to ask yourself if you really need that package in your system. I never heard of it before nor read about it is needed for running VB nor any other virtual machine :-? > Apparently, netscript was pulled in by virtualbox. You have to check this because at a first glance, I see no hard requirements for netscript to be pulled with virtualbox. > I installed that weeks ago so that I could do some testing of a couple > of other GNU/Linux operating systems, and also so that I could fire up > an old database analysis package in a DOS VM. If and when I actually > create them, I'm going to want to use networking for some of those VMs, > and I'm not sure how well that will work without netscript. It looks rather a complex package that integrates within your host networking settings so unless you really need it and you know how to configure to play nice with your current setup, I would ditch it. Sorry but if I had to choose between the host or the guest, first comes the host. And the network stack is vital for any system, it has to be solid as a rock and you have to know how to deal with it when things like this happen. If that's not the case, return to the well-known networking method. > Anyway, the previous version of netscript never seemed to cause me any > problems. It was the new one (version 2.4) that appears to have made > things go a little weird on this system. (...) Yes, it can be. But to my taste, the description¹ for that package leads me to think is not aimed for beginners (meaning: I would not install it in my systems unless I really really know what I'm doing :-P). "(...) DON'T use this on a pure server - it is VERY useful for a Virtual Machine server with complex networking needs. This is because of its comprehensive network configuration capabilities. Thus it is a tempting replacement when you have to rip out NetworkManager on a server." It's scaring :-} ¹http://packages.debian.org/wheezy/netscript-2.4 Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jrihqs$tm4$1...@dough.gmane.org
