Page 1 of 1

sns-tool experimental version

Posted: 02 Jan 2011, 03:40
by francois
From fanthom on old slax-remix thread:

@all
seems that i was damn wrong about WPA and WPA2 :)
WPA can use CCMP and TKIP
WPA2 can use CCMP and TKIP

i have merged both options together - please try this version:
http://www.mediafire.com/?2x8riy8q8fy4dx8
sns-tool is also trying to determine encryption and suggest correct choice now.

feedback is very welcome :)

Posted after 1 minute 46 seconds:


I have tried the sns-tool experimental version. It works great with wpa2, except that the sns-tool-configs.sq4.lzm that it generates does not seem to load wifi at next boot. Are there other testers with the same result?

Re: sns-tool experimental version

Posted: 02 Jan 2011, 03:46
by Ahau
I believe I had the same issue where the module was not loaded properly, and that was the version of sns-tool included in Porteus V.09. I had to manually copy the files per the instructions given at the end of the sns-tool script.

Thanks!

Re: sns-tool experimental version

Posted: 02 Jan 2011, 08:15
by fanthom
Moved from 'i486 lzm modules' to 'Development' as this version is not stable.

Posted after 1 minute 5 seconds:
i dont have such problems (tried static and dhcp), please make sure that nothing overrides config files.

Re: sns-tool experimental version

Posted: 02 Jan 2011, 14:40
by francois
What do you mean? You want me to run the experimental package from a remix installation with no other module in it? And with a brand new save change file? If this is what is wanted, I will be glad to do it.
Mes respects.

Re: sns-tool experimental version

Posted: 02 Jan 2011, 15:59
by fanthom
@francois
this is the queue of files (sometimes archived and compressed as modules) from which live system is assembled:

Code: Select all

1. modules in alphabetical order from /porteus/base
2. modules in alphabetical order from /porteus/modules
3. modules in alphabetical order from /porteus/optional (when 'load' cheatcode is used)
4. changes saved on device/folder/slaxsave.dat (when 'changes=' chaetcode is used)
5. files stored in /rootcopy dir
6. files copied from initrd to live system (/etc/fstab)
so if you put sns-tool configs in something above number 5, then there is a chance of overriding the files. Please make sure that lzm module made from config files has a big number, for example 9999-sns-tool-configs.lzm so it will be activated as the very last.
I will tweak sns-tool script to add '9999' number to generated lzm.

Re: sns-tool experimental version

Posted: 02 Jan 2011, 22:26
by francois
Good. I forgot about that one: numbering modules. I try it immediately and report.

Finally, the module order did not made the difference. However, as I work with the hdd install, I was able to go around the problem by eliminating the old save folder from the menu.lst:
changes=/slaxremix_612_v07cfg

There might be to many files in there. Would you have a cue as to which folder I should delete or is is too trivial an issue?

Would you say I should rebuild the hole OS installation to fit with remix09 (for example it seems that virtualbox module does not work no more under 09 from 08)?

Re: sns-tool experimental version

Posted: 03 Jan 2011, 04:30
by fanthom
If it's only the sns-tool problem then you dont need to wipe off everything, just use /rootcopy dir or delete following files from your saved changes:
/etc/wpa_supplicant.conf
/etc/rc.d/rc.inet1
/etc/rc.d/rc.local
If there's more discrepancies, then the best idea is to start from a scratch and port most valuable settings from v08.

vbox wont work for sure as it was compiled against different kernel version.

Re: sns-tool experimental version

Posted: 06 Jan 2011, 14:00
by Ahau
One other piece of feedback on sns-tool--in the version that comes with Porteus v09 (and your experimental version), there are a couple of calls to dolphin at the end of the script (dolphin /root and dolphin $dir &). In 32-bit Porteus, Dolphin is not installed as the file manager, so sns-tool should be calling konqueror in 32 bit and dolphin in 64.

The experimental version worked fine for me :)

Re: sns-tool experimental version

Posted: 09 Jan 2011, 13:31
by francois
fanthom wrote:If it's only the sns-tool problem then you dont need to wipe off everything, just use /rootcopy dir or delete following files from your saved changes:
/etc/wpa_supplicant.conf
/etc/rc.d/rc.inet1
/etc/rc.d/rc.local
If there's more discrepancies, then the best idea is to start from a scratch and port most valuable settings from v08.
...
This was not enough to do the job. I will have to start from scratch.

Re: sns-tool experimental version

Posted: 14 Jan 2011, 00:07
by wread
In Porteus V09 32bits I am using kwifimanager with 2 configurations (work, home), and it works for me, just as it was with SR 09, too. That was not the case with SR V08, there I had to use the sns-tool of fanthom.

The new kernels do this job ok. I just don't know why I have to press the "Activate" button twice -not doubleclick- to get a response by the second press. Now I have kwifimanager configured in rootcopy.

Re: sns-tool experimental version

Posted: 14 Jan 2011, 06:48
by fanthom
I have to press the "Activate" button twice -not doubleclick- to get a response by the second press.
have no idea (never used kwifimanager - to be honest).
---------------------------------------------------------------------
closing as this version is included in Porteus-v09 and no more experimental (and renamed to pns-tool).