Hi,

I have Suse 9.2 Pro installed and was playing around a little with Linux from scratch. After one false start I deleted the lfs user and group and the binutils+gcc packages (the only two I had installed) because I wanted to start this thing from scratch. Now when I did an su the root user didn't goto /root. it stayed in my directory. When I typed 'groupadd lfs' it couldn't find the command! I had to do a whereis and type it from the directory. The same thing now for init, I had to go into the sbin directory and do a ./init

When I tried to do the configure for binutils using the new lfs user it said /bin/sh: Bad interpreter

What have I done?!? I ran Suse system check and it's still broke.

What has lfs (or me) done to the system to do this, and how can I fix it? Besides a full reinstall (not the end of the world, but I don't feel like redoing mplayer, quake3 and Nvidia).

My original user still seems to work fine, I ran a ./configure on mplayer with no issues.

Dave.

Sounds like when you were entering commands as root that you weren't properly chrooted into the LFS environment so the commands you typed were applying themselves to your base SuSE system. Wouldn't be the first time I've seen that happen this week..Just a guess but it sure sounds like it.../p

Hmm, the only thing is I followed the instructions in the book to the letter, one weird thing was when I added the lfs user with the command in the book -k /dev/null it said copy of skeleton directory failed.

I assumed that meant that it had worked, since we are trying to prevent that. Guess not, any ideas as to what went wrong?

Well, yea, you are correct that you don't want the skeleton copied. Let me think on this a little more and i will let ya know what i come up with../p

It sounds like you have just installed SuSE.

Why not just reinstall?

Dave, after looking over this post again, I think that you are assuming some things are wrong when they are not. When you say
"Now when I did an su the root user didn't goto /root. it stayed in my directory. "

That is the default behavior of <su>.

When you say:

"When I typed 'groupadd lfs' it couldn't find the command! I had to do a whereis and type it from the directory. The same thing now for init, I had to go into the sbin directory and do a ./init"

This sounds like a PATH issue and nothing more. If you try to run these commands as anyone other than root, they will behave EXACTLY as you describe.

You said:

"When I tried to do the configure for binutils using the new lfs user it said /bin/sh: Bad interpreter"

This can happen for a few reasons. Do you have a link between sh and bash?Try typing this:

sh ./configure

And tell me what happens.

Good Luck.../p