Salix Forums

ikke wrote:When trying

Code: Select all

startx

as root I got even a very kind message from Salix "Go away!". Wondering who put it there and why? Because I am so stupid?? Should I stop using Salix?

Salix is configured to strongly discourage you from using the root account like that!

Why do you want to run X as root?

If you keep running startx as root you will get different messages. The messages are not informative (and I don't think they're meant to be)! The main point is that if you don't know why what you are trying is a bad idea, you won't be able to do it.

I'm sorry I can't be more help with your original problem, but others have given you things to try.

Why there is a message in Salix which says "Go away!", couldn't you write it in a specific and a detailed manner which in my opinion is a more appropriate way to indicate on situations of this sort?

zAchAry wrote:There should be a component that will identify such problems and will correct them automatically. It is unfortunate that because of situations like this (the glibc issue is the only one that I know) users may leave Salix OS.

Actually ldconfig is run by the package tools. It appears that this fails sometimes for an glibc update, but it's hard to reproduce. So the error could not be fixed yet.

Thank you for your reaction.

aurlaent wrote:Salix is configured to strongly discourage you from using the root account like that!

Sound principle. Agree 100%.

Why do you want to run X as root?

Most of the time I know what I am doing. Feel that sometimes you can have your reasons.

I'm sorry I can't be more help with your original problem.

Thanks anyway.

thenktor wrote:Actually ldconfig is run by the package tools. It appears that this fails sometimes for an glibc update, but it's hard to reproduce. So the error could not be fixed yet.

Ok!

Any way to solve the module problem : 'updates.salt'? When booting got a lot of error messages concerning missing groups. Couldn't reach X because the "gdm" group was also missing. How to avoid these groups to be deleted in the module? Or how to restore them?

Thank you.

Is this a problem with an installed system, or a live system?

gapan wrote:Is this a problem with an installed system, or a live system?

Am using self made modules only with a live system.
Up to now didn't experience any problems with that updates.salt module. Only now when trying to upgrade to the latest 'glibc'.

Thank you for attention.

I'm not sure if it's possible to upgrade glibc in a live system. The way modules are created and unpacked, I'm thinking it isn't. Not unless you recreate the entire live iso from scratch.

gapan wrote:I'm not sure if it's possible to upgrade glibc in a live system. The way modules are created and unpacked, I'm thinking it isn't. Not unless you recreate the entire live iso from scratch.

Thank you for reaction.

Was able to upgrade in a module from glibc-4 to glibc-5. It is only glibc-6 now which is causing a lot of trouble.

I don't know, maybe you can't upgrade it twice then. Try upgrading from 4 to 6 directly. There is nothing wrong with the 6 package itself.