'su' command in MATE Terminal gives me a 'Slack (32 Bit)$' bash prompt (14.2 Multilib)
I have installed 64-bit Slackware 14.2 on a laptop (iGPU). It is a very new installation (reinstalled yesterday), and the most relevant thing I have done to my install is probably that I enabled multilib support (through slackpkg+) as instructed in the Slackware beginner guide. I am also using MATE.
Regular bash prompt works perfectly both as regular and root user. When I use the su or su - commands, however, the (bash) shell prompt goes from Code:
ygtoz@Slack:~$ Code:
root@Slack (32bit):~# Opening a Root Terminal through MATE, I can switch to the 'ygtoz' account (su - ygtoz or su ygtoz) and get the regular shell prompt I expect (without any mentions of 32bit), which is the only exception to this behavior that I can find. This happens regardless of whether or not the Root Termnal is run as a login shell. I have changed the prompt color through ~/.bashrc (for both my ygtoz and root accounts), and the only time this is sustained in a su environment is when, as above, I open a MATE Root Terminal and su (-) to my regular ygtoz account. This also prints /dev/pts/1: Operation not permitted before displaying the (correct) prompt. When I run the Root Terminal as a login shell, this is still true (the original prompt has (32bit) and the su environment prompt does not), and then I also get the error /dev/pts/3: Operation not permitted . I have also realized that whenever I run my MATE Root Terminal as a login shell, it starts with the Code:
root@Slack (32bit):~# My questions: 1. Am I somehow running a 32-bit build of bash through su? 2. If so (or if not), should I be worried about anything? As you might have guessed, the 'lfs' user is for Linux from Scratch. 3. How can I fix this? Even after changing and exporting $PATH so that /bin is the first directory in it, this behavior repeats. 4. Does this mean I borked my multilib install and need to remove/change things on that front? slackpkg upgrade-all shows some gcc/glibc packages for updating, but slackpkg upgrade multilib shows nothing so perhaps I messed something up there. |
I think you made /etc/profile.d/32dev.sh executable. That is wrong.
|
Quote:
Are there any other files in that directory (in a default full Slackware install) that must not be set as executable, or a place where I could find that information? |
All times are GMT -5. The time now is 08:23 PM. |