Quote from: PackRat on July 01, 2017, 08:07:43 PM
^ It's arrived in Sid.

I wasn't watching that close; but hot on the heels of the last kernel upgrade, I think.

Yes it has...and like yesterday I think.

GCC7 may soon become the Debian default and there needs to be one compiler version that rules them all as keeping around several versions of gcc can get old fast.

A good opportunity to see the lightweight WM's such as fluxbox, openbox and JWM get more traction.  These WM's are fast and light and stable without all the unnecessary frills.

Quote from: VastOne on December 29, 2016, 06:12:14 PM
... and Fuck You to anyone who is snickering that I am just padding my thread/message count

Busted

Quote from: Snap on February 03, 2016, 07:59:44 AM

QuoteIf you elect to change the root pw from the installer, it will fail as it is designed to work with sudo enabled.  I would hear more about su-to-root as a possible replacement specific to vsido-welcome needs (and anything/everything else related to sudo)

Yeah, my fault. Rushing and not reading everything. I always use different passwords for root and users. I asummed on the fly it was just that, setting a root pasword instead of disabling sudo.

I don't like the current (rather global) tendency of comodity at the cost of security/privacy. In the case of sudo and Linux, enabling sudo for everything even without a password. I prefer to allow sudo to just logout and shutdown passwordless. The rest is in charge of su-to-root set as su. I totally favor su-to-root into the welcome script.

PS, if the root password remains unchanged and left as live default ie; vsido. IMHO, a warning in the installer should be needed. Just in case.

To me, I use sudo only for my main user account. Other accounts I create on my system won't necessarily be set up with sudo access. I do set sudo to prompt for password while letting shutdown/reboot be the only operations that can be done w/o any password via sudo.

Quote from: Snap on July 05, 2016, 05:33:32 AM

QuoteWhy aare the GTK3 devs breaking things that have worked well!!!!???!!!

Because their "we only care about Gnome, f*** the rest" attitude.

That sure is the wrong attitude for the GNOME devs to have, which sounds much like Microsoft 

I saw that roxterm has been removed from Debian...sad to see it go. Haven't seen a decent terminal like roxterm, and the tabs are great.

Quote from: PackRat on July 04, 2016, 04:28:43 PM
pcmanfm-qt - Qt port of pcmanfm - I have never tried this, and not recommending it for vsido inclusion; just tossing it out there for y'all.

That would be something to consider as well in event the GTK build ever gets abandoned as GTK3 right now is a bit of a mess.

Muhammad Ali was the one who's brought boxing to the forefront...he will be missed 

Also that picture would make a fine wallpaper

GTK 3.20 has been breaking so many things and it sure is ridiculous I say. Do they read all the bug reports and mailing lists that point out the issues this update brings? It sure is sad when the GTK3 devs lose touch with the user base and application developers.

Lilyterm has promise but GTK3 and VTE 2.91 also broke that one as well. Why aare the GTK3 devs breaking things that have worked well!!!!???!!!

FYI HexChat is a great XChat replacement so you should have that app, VastOne.

Thanks VastOne, and think I've seen your nick on some forums like the #! forum. Currently I have an HP EliteBook 8460p laptop as well as a trusty old IBM Thinkpad T42 (which I use as a netbook when I travel). Also have a custom built Asus rig that has an AMD X2 CPU along with 8GB RAM.

Sure, I gladly will reach out if I have questions or issues with using VSIDO

Hello I am DeepDayze and I am a Linux fanatic who's been out checking various distros on all kinds of hardware that I own. I've been using Siduction, AntiX, Semplice and now taking a good look at VSIDO as I am a Debian Sid user

Thanks for letting me join!