What do you want MX25 to be.?

[Eadwine Rose]

Good idea!! *goes write*

[Mauser]

WOW! When I saw this thread started I figure it would blowup but not to this extent. I will make my answer to this question as respectful and as easy as I can for the Developers. Can you make MX25 a surprise? I hope this is not too much to ask and is possible.

I'll try and see if they can make the default desktop background neon yellow, after that changing every 10 seconds to a different neon color, no mouse support from the getgo (you have to start that yourself) and without any icons at all to simply tab to, so you have to dig for about 5 minutes while enjoying the colors until you keyboard yourself to the configs.

[FullScale4Me]

I'm one of those weirdos - I turn off single-click, set dark with wide borders, and then enable Sync on Firefox. Good to go!

[Jakob77]

vitforlinux

I don't know but it seems very clever to me. :)




user101

My answer to you is almost the same as I gave to txm0523
And congratulation you passed the MX-test. :-)
We only want smart users who are not afraid of doing a little configuration.

* system-wide thicker scrollbars

Oh yes, we have to keep that one.! lol

I don't understand the issue, you wrote about. Do you have a link to the solution.?




CharlesV

Yes, you made me understand the PATH problem was all about the Desktop. :-)
I don't think I have made conclusions about any risks.
I don't see any that we can't defend.

@Jakob77 Why don't you just use /usr/local/bin for your scripts/binaries?

I prefer to use /usr/local for things like that.

Can you make up your mind.? lol
Then you have to tell the newbie to log in as superuser just to edit a simple personal script.
And "/usr/local/bin" is in the beginning of PATH increasing the risk Adrian wrote about.
And you can hardly avoid the script will be available for all users on the computer.
I don't think it is good if KDE users hold back Xfce. ;-)

1) You're asking us to add a known vulnerability into our builds with the /usr/bin path entry

No, that is not where I am. On the contrary I try to move the users away from the sudo zone. :-)
And I don't really know what is "known" here. It is not a surprise to me that a user can damage his own system.

[siamhie]

@Jakob77 Why don't you just use /usr/local/bin for your scripts/binaries?

I prefer to use /usr/local for things like that.

Can you make up your mind.? lol
Then you have to tell the newbie to log in as superuser just to edit a simple personal script.
And "/usr/local/bin" is in the beginning of PATH increasing the risk Adrian wrote about.
And you can hardly avoid the script will be available for all users on the computer.
I don't think it is good if KDE users hold back Xfce. ;-)

@Jakob77 The next time you are going to quote me, make sure to include who I was quoting in response.



This is post #29

@Jakob77 I have not forgotten about helping you. However, I do *not* believe the that should be a 'default' either.

As you have so quickly disregarded... there is a security issue right here and your little 'default path' means that it would be easier for someone to compromise the system. If *you* are not concerned with that then have at it, but I have to vote no for a default path there.

+1

I prefer to use /usr/local for things like that.

[j2mcgreg]

@Jakob77 wrote:

We only want smart users who are not afraid of doing a little configuration.

I take exception to this statement. You are not 'we'. Any user, regardless of skill level, and who is willing to abide by our rules is welcome here in the forums and in the MX community at large.

[Eadwine Rose]

@Jakob77 I suggest creating your own respin and when it is done you can share that.

Continuous posting like this smart users stuff is not helpful on this forum.

You are not part of the team, so you are not going to determine what will happen.

[AVLinux]

Just so people know...

The way MX releases are built package by package every little configuration tweak has to be added into the build script and it's folders often requiring specialized edited files to change the defaults or custom made packages that perform the configuration changes when they install. All of these changes have to be tested by building dozens of test ISO's to ensure that they work properly and even on a very fast machine you're looking at about 20 minutes to build a base ISO and if you forget to dot an 'i' or cross a 't' it's back to building again. It takes a LOT of hours to track down the changes in a new Debian platform and then change the build formula and test the ISOs. On top of that are the dozens and dozens of MX Tools, Utilities and Custom Packages that the MX devs are constantly improving and then re-testing on a new Debian platform. Understandably people have no idea how much tedious work these guys do just to get the damned thing to Boot let alone start going down grocery list of single User preferences.

There is enough hair-loss and devil-in-the-details going into the amazing product we already get, some of these extremely minor configuration preferences are unreasonably asking too much to be handled at the build level (IMHO)

[JmaCWQ]

I would like it to be at least as good as or better than MX-21.3 that I've been using for some time now.
I believe it shall be

[uncle mark]

I would like it to be at least as good as or better than MX-21.3 that I've been using for some time now.
I believe it shall be

Hell, I'll be happy if it's as good as the trusty ol' MX 19 KDE I've been using for some five years now.