A little feedback

[lwfitz]

Ive been using VSIDO as my main OS from day one (Sept. maybe?) and have found it to be 100% stable from my first install. Now MANY MANY installations later and Im even more on board. Ive installed on everything from a dual thread P4 to a 6 core AMD FX-6200 and on systems with Intel, ATI and Nvidia video cards and had 99% out of the box functionality. In my experience this is unheard of in a new distro.
Out of the box hardware support is fantastic but even more than that, this community is top shelf. And that is why I have stuck around like I have. Whether its artwork, conky or troubleshooting a fix for VastOne to add into the next ISO you all have blown me away in how you communicate and feed off of one another.

So, now I am running VSIDO on 3 machines and this weekend will be installing on a fourth that is my office server which at the moment is running CentOS. 

The only thing I would like to see added in one of these days is

gvfs-backends

and

libbluetooth3   

These are required to use samba shares directly through Thunar.  At one point I was working on sharing with SpaceFM but it didnt seem nearly as stable or fast so I stick with what works.

Thanks VastOne and everone else who makes VSIDO and this community so amazing!

[VastOne]

Thank you lwfitz!  That is a glowing review and good luck with your server update

gvfs-backends and libbluetooth3 will be added to the next ISO build

Thanks!

[lwfitz]

AWESOME! Thank you! Ive installed on a similar machine with no issue at all so it should be pretty simple. Ill update after its up and running

[Sector11]

I only have one machine, but I have installed it so many times here, with quad booting VSIDO at times;

Liquorix kernel - NVIDIA graphic driver (my default)
Liquorix kernel - nouveau graphic driver
Debian kernel - NVIDIA graphic driver
Debian kernel - nouveau graphic driver

It's never failed me yet.

Awesome distro isn't saying enough.

[jefsview]

I couldn't agree more. I have 2 installs, one just Xfce and the other Fluxbox and both are lightning fast and so much fun to play with.

Just a bit of feedback on my part: WICD is still listed under Xfce's Start-up, and there's a nice little TODO list in the Fluxbox config folder. I found it interesting.

Also, could you place in folders the extra tint2 configs, since it's difficult to find which one does what, especially since they're in at least 2 separate directories.

BTW, I really like the Fluxbox menu editor. Very similar to the Openbox root menu editor, and simple to use.

Keep up the great work. Been loving it.

-- Jeff

[VastOne]

I'll take care of the WICD in Xfce.. one I overlooked, thanks

What do you mean by the TODO in the FB Config folder?

The tint2 files in /usr/local/bin are basically the same, the differences being what one is being used for OB or Xfce/Fluxbox.  I am not sure what you are asking here.. 

I included a mass collection of tint2 configs that I had played with for several months for people to use as a guide on what can be done with tint2

Thanks for the feedback!  I appreciate it! 

[VastOne]

The WICD in Xfce is a phantom startup that does nothing and what is strange is I cannot delete it or find where it is stored at.  I know where the correct ones are stored but this one and several other old ones are not there nor can they be deleted.

I will continue looking

Thanks!

[jefsview]

I'll take care of the WICD in Xfce.. one I overlooked, thanks

What do you mean by the TODO in the FB Config folder?

The tint2 files in /usr/local/bin are basically the same, the differences being what one is being used for OB or Xfce/Fluxbox.  I am not sure what you are asking here.. 

I included a mass collection of tint2 configs that I had played with for several months for people to use as a guide on what can be done with tint2

Thanks for the feedback!  I appreciate it! 

Re: Tint2 config files. It just took me a while to suss out which one was being used. They're all just in the tint2 folder, but there's one in the home directory and one in like etc or usr. Guess I just need to hone up on tint2; just haven't had time.

The TODO file in the fluxbox folder are like notes of what you want done, where there are bugs and how you want to it to look/work. Perhaps it's not yours, but the Fluxbox devs. Oh, it's in the flux menu folder. I'll attach it. It was just something I found, and thought was rather strange.

[VastOne]

Right, the TODO is a fluxmenu dev to do list

Anytime you need to see what app is running you can do one of these

xfce4-taskmanager from any of the menus, it will tell you

grc is one of the aliases that does a grep of what ever you enter as grc appname

in this case

grc tint2

htop also lists everything running

I wanted to keep all the tint2 files in every /home directories but tint2 does not recognize $HOME or $USER parameters and must have a direct path to it's files.  Because of this they are in /user/local/bin

[Sector11]

Since my #! days tint2 has always resided in ~/.config/tint2.  The installed defaults and all the extra ones I have made, including any that {cough cough}"borrowed" from VSIDO /user/local/bin

I keep them there, ~/.config/tint2, because I don't want to have to be root to edit them.

What is different with VSIDO that they can't be there?

[jst_joe]

What is different with VSIDO that they can't be there?

That's where I copied them to and just pointed autostart.sh there.
Everything has been working fine on OB.

[VastOne]

You can run them from anywhere. My intention is to localize them in /usr/local/bin so that when they are called from anything that cannot handle $HOME and $USERS I do not have to worry about where they are.

It is either Xfce (most likely the culprit), OB or FB or all that cannot handle the tint2 files being called unless it is a direct path.  If it is in the /home directory of every user and I cannot use $HOME or ~/.config/tint2 or $USER variables, they will not run

If anyone has a solution to the issue, I am all ears

[Sector11]

From my autostart.sh for Openbox:

Code Select Expand

## Launch panel
(sleep 1s && tint2 -c  ~/.config/tint2/tint2rc) &
# (sleep 3s && tint2 -c  ~/.config/tint2/1_tint2rc) &
# (sleep 3s && tint2 -c  ~/.config/tint2/t2launchrc) &
# (sleep 2s && tint2 -c  ~/.config/tint2/tint2rc_top) &
# (sleep 2s && tint2 -c  ~/.config/tint2/tint2rc_bot) &


And I have this in my OB Menu:

Code Select Expand


<menu id="tint2config" label="tint2">
<item label="Edit config file">
<action name="Execute">
<execute>geany ~/.config/tint2/tint2rc</execute>
</action>
</item>
<item label="Restart tint2">
<action name="Execute">
<execute>~/bin/tint2restart</execute>
</action>
</item>
<item label="Restart t2rs">
<action name="Execute">
<execute>~/bin/t2rs</execute>
</action>
</item>
<item label="VO T2 TEST">
<action name="Execute">
<execute>~/bin/VO_tint2</execute>
</action>
</item>

~/bin/tint2restart

Code Select Expand

#!/bin/bash
# ----------
# Simple script to restart tint2

if [ "$(pidof tint2)" ]; then
    killall tint2 && sleep 1s && tint2 &
    exit 0
else
    tint2 &
    exit 0
fi

~/bin/t2rs

Code Select Expand

#!/bin/bash
# ----------
# Simple script to restart tint2

# if [ "$(pidof tint2)" ]; then
#     killall tint2 && sleep 1s && tint2 &
#     exit 0
# else
#     tint2 &
#     exit 0
# fi


if [ "$(pidof tint2)" ]; then
    killall tint2 &
    (sleep 1s && tint2 -c  ~/.config/tint2/t2launchrc) &
    (sleep 1s && tint2 -c  ~/.config/tint2/tint2rc_bot) &
    exit 0
else
    (sleep 1s && tint2 -c  ~/.config/tint2/t2launchrc) &
    (sleep 1s && tint2 -c  ~/.config/tint2/tint2rc_bot) &
    exit 0
fi

~/bin/VO_tint2

Code Select Expand

#!/bin/bash
COMMENT_BLOCK=
if [ $COMMENT_BLOCK ]; then

Simple script to re-start:

~/.config/tint2/VSIDO/tint2
fi  ## comment ends


if [ "$(pidof tint2)" ]; then
    killall tint2 &
    (sleep 1s && tint2 -c  ~/.config/tint2/VSIDO/tint2rc) &
#    (sleep 1s && tint2 -c  ~/.config/tint2/VSIDO/tint2rcall) &
#    (sleep 1s && tint2 -c  ~/.config/tint2/VSIDO/tint2rcallbtm) &
#    (sleep 1s && tint2 -c  ~/.config/tint2/VSIDO/tint2rcalltiny) &
#    (sleep 1s && tint2 -c  ~/.config/tint2/VSIDO/tint2rcalltop) &
#    (sleep 1s && tint2 -c  ~/.config/tint2/VSIDO/tint2rcallvert) &
    (sleep 1s && tint2 -c  ~/.config/tint2/VSIDO/tint2rcallvertleft) &
    (sleep 1s && tint2 -c  ~/.config/tint2/VSIDO/tint2rctotal) &
    exit 0
else
    (sleep 1s && tint2 -c  ~/.config/tint2/VSIDO/tint2rc) &
#    (sleep 1s && tint2 -c  ~/.config/tint2/VSIDO/tint2rcall) &
#    (sleep 1s && tint2 -c  ~/.config/tint2/VSIDO/tint2rcallbtm) &
#    (sleep 1s && tint2 -c  ~/.config/tint2/VSIDO/tint2rcalltiny) &
#    (sleep 1s && tint2 -c  ~/.config/tint2/VSIDO/tint2rcalltop) &
#    (sleep 1s && tint2 -c  ~/.config/tint2/VSIDO/tint2rcallvert) &
    (sleep 1s && tint2 -c  ~/.config/tint2/VSIDO/tint2rcallvertleft) &
    (sleep 1s && tint2 -c  ~/.config/tint2/VSIDO/tint2rctotal) &
    exit 0
fi

So if OpenBox can use ~/  I'd guess $HOME will work.  Not sure about $USER though, I'll have to test that.

ALL of the above worked at one time ... I'd need to recheck everything, but the ones in my OB menu work perfectly, I used them within the past few days to talk about your genius with tweaking tiint2!

[VastOne]

^ Right, OB is not the issue, it is Xfce that causes the headache

Since I have no control over what a user decides to use between Xfce/FB/OB, /usr/local/bin is the logical choice for it.  It works OOTB, and that is what is relevant...

Anybody can move them to where ever they want after the install

[lwfitz]

Your absolutely correct about it being Xfce. Both OB and Fluxbox use a editable start up script which will allow you to use $HOME or ~/ but xfce (to the best of my knowledge)  is limited to adding startup scripts/programs through a gui which needs a physical path.

That being said its pretty easy to

Code Select Expand

sudo thunar /usr/local/bin

or

Code Select Expand

sudo spacefm /usr/local/bin

and then edit the tint2 configs to your liking

Or as someone mentions just change the startup to the configs in ~/.config/tint2

Hey VastOne can you add Gnome3 or KDE to the next ISO?