Yea - it looks right, is it executable

Just "echo $QTDIR" and "echo $CPLUS_INCLUDE_PATH"
and you see if that script is called

Hmmm...looks like it's not working. I got this:

And it *is* executable. So something, somewhere is messed up, right?

But for everyone?
The file should have these attributes!

Yes, it's executable for everyone. I got the same thing you did:

Not good, huh?

Try to source the script, and see if you get errors, or the variables are set

If this works, then the script is OK,
but for some reason it is not used, when you login

I am wondering, what about all the other scripts in that directory,
do they also not work, f.ex. lang.sh?

They are all sourced from /etc/profile

What shell do you use - Bourne (and related) shells?

Okay, here's what I got:

So it seems *that* is working somehow for some reason.

What should I do to see if any of the other scripts are working in /etc/profile.d?

As for shell I use...uuummmm....all I know is I open konsole (same within Krusader, just a konsole)...both use bash (isn't that bourne again shell?).

Hello again irgunII :-)

This found on Gentoo forum:
They advice one solution:

This would do it:
Or if you can find where konsole is called, add the option --ls to it

This make it a login shell, and so the /etc/profile is sourced!

I do not use KDE, so it is not tested - it is just what They on the big net say!

Enjoy

Or, to change Konsole to always open a login shell, open Konsole and find Settings / Edit current profile. On the General tab change Command from /bin/bash to This has the advantage that it doesn't change things for _all_ bash invocations, only the one from Konsole.

If you're using XFCE Terminal the procedure is a little different. Edit / Preferences / General / check Run command as login shell

For xterm you have to change the xterm.desktop file. When I use it I just do

@jamesf - Well, I use KDE, and really don't need the login shell, so I have it so I use the gui login screen and goes straight to X. But thanks for the idea and assistance!

@ml4711 - lol...Hi again to you too friend!

Thank you for that information. I'll give that a try and see how things go. I didn't even have enough of an idea what was wrong to ask it on a search engine, so I'm glad you found it. Thanks again too for all the help you've provided. If I ever win the lotto, I'll come over to Denmark, rent me a Harley (I'm disabled and it's the only thing I can get around on that doesn't give me extreme pain, plus, I'm a biker from all the way back in the 70's and hate cages, heh) and buy you a beer...or 20!

Um, my suggestions were for the GUI. Changing to a login shell will cause /etc/profile to execute. So, you make those mods and only the Konsole and Terminal apps cause the shell to be a login shell, leaving other shell modes alone.

@irgunII

This advice from jamesf is actually what you need, and it's also the least intrusive solution!

You still have Your GUI Login :-)

The only change You see, is that /etc/profile is sourced, when you start a konsole!

Enjoy

Okay...seems I have the idea of what a 'shell' is completely wrong (that really shouldn't be surprising if you guys knew me better, lol), so I've deleted the bash.rc and done it the way jamesf said to do.

Thank you both again for helping me 'fix my stuff', you're good people.

Really off-topic here, but whatevs. ;vD The best discussions are often free-ranging.

A shell, or Command Line Interface (CLI) in this discussion is a command interpreter / user interface. For this definition Slackware comes with multiple shells like csh, tzsh, bash, sh, bsh(?). Then you get a terminal emulator like Konsole, XFCE Terminal, rxvt, urxvt, etc. to provide the 'wrapper' around the shell while in the GUI. There are also GUI shells, but they're basically point-and-click interfaces to the computer. I won't be addressing GUI shells.

For UNIX/Linux shells in general there is the ones I mentioned above, and others listed at http://en.wikipedia.org/wiki/Unix_shell

A discussion of the different types (login, non-login, interactive, non-login interactive) can be found at https://unix.stackexchange.com/quest...on-login-shell

Basically interactive login shells are set up more for human use and as the basis for a GUI environment to start (like KDE, Gnome, etc.) and non-interactive non-login shells are more for script use.

For interactive software development (editing, compiling, linking, installing, testing, repeat) you use an interactive login shell. That usually gives you the rich set of commands like gcc, make, qmake, cmake, etc. in your path that you don't want in the other types of shells.

An example: not making compiler and linker commands available to non-login shells can help prevent some methods of malware spreading because they
compile the malware and then install it. Granted, this was more true years ago, but hey - a good practice is a good practice.

Hope this helps!

1 members found this post helpful.

That's a bit far-fetched. Why wouldn't the malware come pre-compiled ? What if the malware is written in assembly ? Technically you can type in the malware using octal or hex without even an assembler. There are better ways to prevent malware.

Scramdisk seems to be Linux-only, so I don't see how this will save truecrypt as the whole point of truecrypt was its cross-platform nature. I mean I use cryptsetup because I don't use Windoze, but people that do need something cross-platform.

No argument, notice that I said that this was more true years ago. The famous Robert Morris worm, considered the first such on the internet (see http://en.wikipedia.org/wiki/Robert_Tappan_Morris) that brought big attention to malware would compile parts of itself if it found itself on a system that the compiled version didn't support. For that to work I'd guess that two parts were downloaded, scripts that checked for a friendly environment and compiled source if needed and a pre-compiled binary for those machines that would support it.

However, it is still good computing practice to compartmentalize permissions. If Bob doesn't need to compile stuff, then Bob can't. If Carol shouldn't 'make install' then she can't. If I don't need into your bank account, then I can't.

Is everyone a member of the root or wheel groups? Same general principle. I was just simplifying a bit for a new user.

P.S. This google search returns multiple recent hits about malware that compiles itself https://www.google.com/#q=malware+%22compiles+itself%22 When I looked the first page of results had hits for Linux, Windows, and Mac OS X. Granted many hits were about the C compiler that inserts a backdoor/malware, but each major OS was represented.