GNU rejected TUI, for the moment

Hello everyone

As TUI can show its true power only when it is already installed on your system, so one could simply share the scripts that  rely on TUI, just like one shares any bash or other shell script, I wanted to become part of GNU.

That is no easy task, specialy if you come from a 4 year old project that hasnt had this goal from start.
So, for the past 10 months, its been in the GNU Evaluation queue and just until a day ago it look very promising.

However, it got rejected for the moment, as more user feedback is wanted for them to evaluate the need/profit of making TUI part of the GNU family.

With one of the arguments beeing that we would need some user feedback for further evaluation.

That is, because TUI has a new approach to the terminal...
An approach mainwhile quite the same, but also quite different.

In the beginning, I wanted the 'ultimate' dir/menu browser for (a single specific) directory based script project/s.
In the end I extracted those functions as I wanted to have the scripts provided in named directories to look/match the containing 'ultimate' menu, so I made them individual commands.

Due to this change, one can also create great (single file) wizzards or wrappers around other cli/clu applications or make tools that act (but dont look like) 'ip' or 'iw' commands, just for your custom directory-tree structure.

It comes with many commands/functions for often used tasks, such as tui-yesno, tui-select, tui-read, as well as nice optical commands such as tui-header and tui-title.

As it is a command and line-based-output framework, it might look weird if you just try a single command.
To get started - once installed, you might want to check:

tuirc samples
tuirc provides

To get the manual, please check either:

info tui
tuirc info
tuirc html  # Only if you used "make install all"

I'm asking here for this required feedback:

• Which OS/Distro?
• Does Installer work?
• Does running 'tuirc' raise any, and if - what kind of - error messages? (Besides initial creating of user configuration)
• Any other errors/bugs/unexpected behaviour you came along?

Additionally according to your skill, time and preferences:

• What are our thoughts about the 'tuirc samples'  and info page?
• Did you find any security bugs? - have any advice how to fix them?

Get it from: https://savannah.nongnu.org/projects/tui/

Issue is, all i can say for sure is that it runs well on my system.
I'd very much like to have confirmed reports on which OS or Distro it installs and runs well or not.
That is also required to get it working for that OS/Distro, eventhough most of them work alike, there are differences i might not be aware to catch and handle (properly) without reports and hints how its done on your OS.

Thank you in advance for sharing your thoughts about TUI.

YASSI 1.0.1 - Final release

I'm happy to announce the final release of YASSI.

YASSI does not need to be installed, unless you want to 'info yassi'.
The project name and version 'yassi'/1.0.1, and both lines with 'Report bugs...' are read from the configuration file,
and therefor will adjust to your project settings.

Not even 2 months ago I had started with this project, and it already provides all the functions i've wanted for it.While I initially started it for another project of mine where i needed to focus on the duty, i wanted to have it as its own project, to use with ther projects.

I do hope you helps you as much as it does for me.

What is YASSI again?

Yet Another Simple Script Installer

What is it for?

It requires a single file to provide all information for an installation custom to your needs,
while staying easy change-able by the end user.

Get it

• Projectpage: https://github.com/sri-arjuna/yassi
• Release: https://github.com/sri-arjuna/yassi/releases/tag/v1.0.2

Howto: Connect BSD to WIFI spot

Heyas

So i've just installed FreeBSD on my computer.

Preparation:

So, to get started for WIFI, i first need to plug in a wire, and install some of the tools required to enable WIFI.

pkg install -y wpa_supplicant 

Once this is installed, lets remove the wire, so we can be sure the next internet connection will be using the WIFI.

Saving the WIFI config

Is quite simple, we're using the just installed wpa_password tool, passing the AP-Name and its password, and redirect the output to a file:

wpa_password APNAME PaSSwoRd >> /etc/wpa_supplicant.conf

Enable WIFI for startup

Basicly, you just need to get the device from the output of:

ifconfig | grep -B3 -i wireless

And save it to: /etc/rc.conf

wlans_ath0="wlan0"
ifconfig_wlan0="WPA SYNCDHCP"

Or you cold type this:

WLAN=`ifconfig | grep -B3 -i wireless | grep ^[ai]|awk '{print $1}'`

echo "wlans_${WLAN/:}=wlan0
ifconfig_wlan0=\"WPA SYNCDHCP\"" >> /etc/rc.conf

Enable WIFI

To get it right away:

service netif restart

Or simply reboot to verify everything worked well.

Sources:

https://www.freebsd.org/doc/handbook/network-wireless.html
http://www.wonkity.com/~wblock/docs/html/wireless.html