Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When I do su - binutils and I want to open a new terminal from prompt every command I know of opening a new terminal tells me command not found.
I tried xterm, terminal.
Makes no difference. Also in chroot as root I can't get a terminal from prompt.
See this :
Code:
root:/# echo $PATH
/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin
root:/# xterm
bash: xterm: command not found
root:/# terminal
bash: terminal: command not found
root:/# su - binutils
package binutils:/usr/src/binutils> echo $PATH
/usr/lib/pkgusr:/bin:/usr/bin:/tools/bin
package binutils:/usr/src/binutils> xterm
-bash: xterm: command not found
package binutils:/usr/src/binutils> terminal
-bash: terminal: command not found
package binutils:/usr/src/binutils>
What exactly is the question at this point? Is it the xterm issue? Or is it still the original question from post #1? If so, then at which point did the error occur? Was it after the configure, make ...?
And having no ptys is definitely not good. When you say you have no problems with that as root, are you still root in the chroot environment or your 'normal' environment?
What is the output of
in chroot as root I can't get a terminal from prompt
You can't because you haven't installed xterm into chroot. But you don't have to. Start xterm from the host system as non-root and then do what you need.
I just wanted to report that I have the same issue as well. No errors were reported when I ran the `expect -c "spawn ls"` command as root.
I was able to run the check as root; the tests were successfully completed. I just changed my build script to bypass the checks, and install the package anyway.
The response provided in the LFS FAQ about this issue [1] is out of date; this is because the material references an obsolete kernel option.
According to the Linux Kernel Driver Database [2], the kernel option for enabling the devpts filesystem ("CONFIG_DEVPTS_FS=y") is obsolete. The functionality is available via the pt_chown program, which is included in glibc, the GNU C Library.
The solution to this issue is to adjust permissions for the program. If using the user-based package management scheme [3], the following should fix the issue:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.