Package installation from Thunar:
The problem is due to my overzealous removal of scripts from vasm-legacy. I plead that this aggressive removal helps identify what needs to be done before vasm-legacy is replaced with the forthcoming new vasm (which is on hold so this release can be concentrated on). The needed scripts have been returned. Unless you're using this feature, no real need, but updating vasm-legacy to the latest in untested solves this problem. That's the only change in the new version, so most should probably just wait for the next ISO. Thanks to overthere for catching this, I'dve missed it otherwise.vliloconf missing:
This is also an omission from vasm-legacy, but for now it's intentional. There's still some discussion on how bootloader configuration will be done post-install. Some users, mostly new to VL, were having problems with the scripts in certain situations. So they're absent until the method is decided on and the scripts can be edited and returned. So yes, for now reconfiguring the bootloader will be done by manual edit of lilo or grub configuration.
Although this was an issue known in advance, THANKS TO VINCENT2 FOR REMINDING ME OF IT.
One more thing of note is missing from vasm-legacy right now. There's no means to "automatically" configure terminal keyboard, x-keyboard, and locale. The main problem with the previous scripts was the naming conflict between x-keyboard and terminal keyboard layouts for many locales. I think there's a way to do it all at once, smoothly. If I'm wrong, this ability will return to vasm-legacy anyway with an additional step to choose terminal keyboard separately from x-keyboard. Top of the list, but may take the longest.