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.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

I'm running the test for Bash as stated in LFS 6.9; ch_6.29 after changing the ownership of the bash source folder to 'nobody' and the results come back as "permission denied". The Instructions say to do:

I'm running the test for Bash as stated in LFS 6.9; ch_6.29 after changing the ownership of the bash source folder to 'nobody' and the results come back as "permission denied". The Instructions say to do:

Assuming you meant LFS 6.8 (Stable) instead of LFS 6.9 (which doesn't exist yet): If I read the above correctly you get a permission denied message as a result of executing the chown command. If that is the case then something is definitely wrong and there is no point in running the su-tools ... and the rest of the commands.

Did you check the following:
- Are you inside the chrooted environment (6.4. Entering the Chroot Environment)
- Are you root user?
- Have you tried removing the /sources/bash-4.2 directory and redo this chapter?

If all that didn't come up with something, can you post the output of the following command (after running the chown -Rv nobody . command):

I woke up today & started going through your steps of repeating the chapter. After I'd removed the folder, and again un-tared the archive to repeat the chapter, the test suite worked, and the install continued through. Thank you.

I'm not sure where I went wrong exactly.. I was muddled with sleep.. most likely a repeating typo.

I wasn't clear on the description of symptoms though, and will attempt to clarify for anyone else that may encounter this:
The "permission denied" occurred *during* the tests for each individual test output, and during make install for all access entries (though did not happen for root by just doing make tests).

The chown command had executed as expected, changing the ownership (recursively) of all files in .(that directory) of the bash source directory, as nobody:root (or nobody:nogroup where the original permission was 286:80 instead of root:root).