I'm compiling blfs 8.3 and had a problem when trying to install OpenJPEG-2.3.0.
I've configured sudo to let me run as root without a password because it
takes too long to enter a password every time I install something.
I get this problem:
tells me pushd command not found. I know it's not a command but
a bash builtin but I don't know how to make it work. The book does
not say what to do in this case. I've seen this problem in the past
but I've forgotten what I did to make it work. I finally got this
software installed by lots of going back and forth from console
to xterm but it was time-consuming and annoying. I got fluxbox running
and I'm doing installing from two xterm windows from there, copying
and pasting from one xterm running links to another doing the compiling.
Does anyone know the solution to making pushd work in this case?
Oh, and I've already done lots of googling. No solution found.

Ok. I've figured out a solution. I've got to fully become root with:
to make the pushd stuff work. I don't know if that's the only way but
it works so I'll stick with it until I find something else.
Typing "exit" afterwards returns me to my regular user. I'll mark this
solved.

I believe you can also use as your limited user:

It runs an interactive shell with root privileges.

1 members found this post helpful.

Thanks. I think that's what I was looking for.

sudo su is deprecated.
sudo is completely enough to be root. there is no such thing: "fully become root".
pushd is a shell built-in, and sudo cannot be used that way. sudo is used to execute binary commands, not a bash function, alias or built-ins.
As it was already mentioned sudo -i will run a shell and that shell (bash) will understand (and will be able to execute) functions, aliases and/or built-in commands.
see man sudo for details.

I don't care if it's deprecated or not as long as it gets me to where I can
copy and paste instructions from the book.
Why are you nitpicking me over the words I used? Yes I realized pushd wouldn't
work that's why I asked for help.
You are not helpful. Why did you even comment except to be a smartass?

Basically I wanted to give you some additional info. Some details, probably to understand better. But you don't care about that. That is ok. You do not have to understand.

While sudo works, why not write your script with the goal of running it as root? Sudo isn't meant to be used for everything like many guides recommend and often will not provide you with full root privs to carry out your tasks. Often it is better to simply log directly into your root account (from the log in prompt or with su), do whatever work you need to do, then log out.

It's the writers of the BLFS-8.3 book who've written the installation
instructions. I use sudo because it works 99 percent of the time
when copying and pasting these installation instructions as root.
It takes hours to compile this software and any shortcuts to doing it
are a help. The pushd popd thing was an unexpected obstacle to what
had been smooth sailing up to that point.
Thanks again for the "sudo -i" tip.

I do that kind of thing this way...
You don't need to be root to do the pushd and popd; just the install command. And in a script, get rid of the ampersands.


P.S.: I looked at that page in the BLFS book, and it's written that way expecting us to change to the root user in a terminal to do all that stuff being discussed here. But if you instead prefer to use sudo, or if you are writing a build script that will use sudo, then the book's line-by-line steps may not work with sudo exactly as written following anywhere it says "now as the root user:". In this particular case, the pushd, popd, and for-do loop do not need to be run as root. Only the command inside the for-do loop. The book authors are not going to bother writing about that. There probably are other examples of this or similar situations in the book. Some examples where the book intends for us to use sudo and is written in a special way to allow that are the Xorg libraries, applications, and fonts.

1 members found this post helpful.

Thanks for this idea. This is what I'm looking for. Ways to make this work.