Re: "Pwireless2 now in Quirky"
Posted: Sun 21 Feb 2010, 03:55
Hello, dear Barry!
I haven't to do my posting to your Blog (for "Pwireless2 now in Quirky"). Becase I posts it here.
The Pwireless2 tool, as it's I shown in the assembly Puppy eee-431-b35 (I was tested it; see my report here: http://murga-linux.com/puppy/viewtopic. ... 423#391423), does not allow to users manually settings: do not it for Wi-Fi (for manually entering parameters such as: put a SSID, Channed, Frequency, Mode and others), and also it allows not use a fixed IP and uses manually entered DNS -- but it *need* to many users! Also, this tool does not allow to manually configure the Ethernet.
Pwireless2 may be usuable tools for connecting to 'open wireless networks' such as has in an airport, restourant or 'net-cafe' networks, but not for security powered private wireless networks.
The posting below as wrote mr. bruce, he is absolutely right, when he wrote (Posted on 17 Feb 2010, 8:01 by bruce: http://bkhome.org/blog/?viewDetailed=01403) that it was necessary to allow users to freely use *AND* Pwireless2, *AND* Pwireless tools!
It old network configuration tool is very good for many real cases, and I was do setting network under Pwireless (such as traditional Puppy Network Manager). And I used it for about year, without any complaints.
But the newest tool -- such as Pwireless2 -- haven't many user's needly features. For example, I could not be used It for me networking about testing Puppy 431-b5 at January 2010...
If Pwireless will be excluded from the new assembly of Puppy, -- many users will either have to abandon the new Puppy; or either to alone manually include the Pwireless to newest Puppy, taking it from an old release of Puppy...
Note. Unfortunately I have to admit: in a recent increase in cases where developers of software very uncritically, and without considering all possible consequences -- as roughly "modernist" action -- when alter conditions of use of their products!..
This is evident of many examples. For example, recall the recent case of the erroneous change of value data=writeback onto kernel 2.6.30.5; or remember please most recent cause: with kernel 2.6.33 this is a blatant case of unjustified exceptions are always used before passage of the hardware diagnostic test (for USB -- in this case: http://bkhome.org/blog/?viewDetailed=01404) for PCs devices...
This is not good actions!
I hope that Barry Kauler, as founder the PuppyLinux, fall not into this mental trap. And do not be too eager (as a young foolish people) -- as to do excluding from the OS very reasonable subsystems such is Pwireless tools, which previously worked wery good for many Puppy users.
Because not necessarily in order to introduce new features, and at one time to do exclude from the OS a well-proven technical solutions, pass it is old tools.
Thank you for the opportunity of understanding.
P.S. Excuse me for my poor English, please!
I haven't to do my posting to your Blog (for "Pwireless2 now in Quirky"). Becase I posts it here.
The Pwireless2 tool, as it's I shown in the assembly Puppy eee-431-b35 (I was tested it; see my report here: http://murga-linux.com/puppy/viewtopic. ... 423#391423), does not allow to users manually settings: do not it for Wi-Fi (for manually entering parameters such as: put a SSID, Channed, Frequency, Mode and others), and also it allows not use a fixed IP and uses manually entered DNS -- but it *need* to many users! Also, this tool does not allow to manually configure the Ethernet.
Pwireless2 may be usuable tools for connecting to 'open wireless networks' such as has in an airport, restourant or 'net-cafe' networks, but not for security powered private wireless networks.
The posting below as wrote mr. bruce, he is absolutely right, when he wrote (Posted on 17 Feb 2010, 8:01 by bruce: http://bkhome.org/blog/?viewDetailed=01403) that it was necessary to allow users to freely use *AND* Pwireless2, *AND* Pwireless tools!
It old network configuration tool is very good for many real cases, and I was do setting network under Pwireless (such as traditional Puppy Network Manager). And I used it for about year, without any complaints.
But the newest tool -- such as Pwireless2 -- haven't many user's needly features. For example, I could not be used It for me networking about testing Puppy 431-b5 at January 2010...
If Pwireless will be excluded from the new assembly of Puppy, -- many users will either have to abandon the new Puppy; or either to alone manually include the Pwireless to newest Puppy, taking it from an old release of Puppy...
Note. Unfortunately I have to admit: in a recent increase in cases where developers of software very uncritically, and without considering all possible consequences -- as roughly "modernist" action -- when alter conditions of use of their products!..
This is evident of many examples. For example, recall the recent case of the erroneous change of value data=writeback onto kernel 2.6.30.5; or remember please most recent cause: with kernel 2.6.33 this is a blatant case of unjustified exceptions are always used before passage of the hardware diagnostic test (for USB -- in this case: http://bkhome.org/blog/?viewDetailed=01404) for PCs devices...
This is not good actions!
I hope that Barry Kauler, as founder the PuppyLinux, fall not into this mental trap. And do not be too eager (as a young foolish people) -- as to do excluding from the OS very reasonable subsystems such is Pwireless tools, which previously worked wery good for many Puppy users.
Because not necessarily in order to introduce new features, and at one time to do exclude from the OS a well-proven technical solutions, pass it is old tools.
Thank you for the opportunity of understanding.
P.S. Excuse me for my poor English, please!