I have two computers, an old single core AMD (ati video) and a newer duel core AMD (nvidia).

I use LFScript to automate the build process. I build it with the C flag so that each package is only build against the dependencies I choose. This allows me to build the LFS and all my BLFS choices at once.

I first built the latest book on my old single core AMD because I'm crazy like that. Everything seems to be working good with the new build.

Copy my files over to the newer duel core AMD box and everything builds fine. I can also just copy all my files over and just rebuild the kernel. Tried it both ways.

When I run the new build on my newer duel core AMD, a lot of little things don't work. I use the Xfce as my desktop. Restretto doesn't see PNGs and JPEGS as images. Some right-click menu options are missing like "extract here". I'm logged in as root but I can only "log out". Restart and Shut Down is greyed out. Viewing files in Thunar does not recognize file types like PNG, JPG, tar.bz. It assumes most files are text files and tried to load them in gedit.

So from one machine to the next, even with the exact same build files from the working system, many things are broken on the duel core. Could this be a SysInit problem? Not sure why it's so different from one computer to the next.

+654It's time to duel! Anyways, combining Nvidia and AMD - I also like to live dangerously.

This seems like an issue with mime types. Check your mime database and desktop file database.

update-mime-database /usr/share/mime
update-desktop-database

As for the buttons, you need to have at least ConsoleKit or systemd-logind to be able to shut down/hibernate/suspend.

As for the right click, I'm not really sure. Xfce's default archive manager is squeeze and I'm not sure if that's in the book. If it is however, make sure it was installed before Thunar, so the integration module is built.

I don't see how sysvinit could be a culprit for something wrong in a desktop environment configuration.

Thanks Krejzi!

Everything is now working as expected due to your observations. You helped me figure out where to look. My xfce4-session script was missing the items you suggested (update-mime-database, update-desktop-database & ConsoleKit).

I am using LFScript as well. I updated the complete lfs to match LFS-7.7, great stuff!

Do you build your entire system or add stuff later with a package manager, like I do?

I build my entire system except for Firefox, Java and Steam. As much as I like and appreciate polished distros, the software in their repositories are extremely old. There's just something cool about building and using the latest versions.

I used the LFScript factory to generate new LFS scripts from the latest book in development. There's a bug with the script generation but I have a work around. So far, generating new LFS scripts is pretty solid and builds without a problem. The BLFS factory is broken and the author isn't responding. Even if that wasn't the case, you still need to edit many of them to work because BLFS is the wild west. So I hand edit the BLFS scripts that I use based on the newest versions listed in BLFS.

So what package manager are you using and how does that work?

I use pkgutils. I have updated the latest lfscripts to 7.7 with a few modifications and build up to Xorg and make sure I have libarchive.
When I am done, I install pkgutils (CRUX'package manager). The only dependency for it is libarchive and then I use Pkgfiles from CRUX, Nutyx or create my own, they are very similar to what is in the LFS/BLFS book.
My latest experiments are trying to add buildscripts for LFScript so I can build all the stuff I need. I reuse the created binaries on other machines.
To succesfully build firefox, you will need to add openssl 1.0.2a to the buildbase file, otherwise the script will build python2 before openssl, I tried a lot of combinations.

We could share our updated scripts, I tried to contact the author as well.

I gave up on trying to build Firefox. It's a huge beast that takes all day to compile and it only takes one problem for you to start all over. I just copy the latest version down and untar it in /opt. done. I do the same with java and flash. I setup a scrip to do this.

Yes, it would be fun to share our updated scripts. Adding new scripts is easy. Just use the existing scripts as examples of what you need. I put them in the "contrib" folder. When adding something brand new and it's not listed on the LFS site, I first start with the basic script. Then I look at the log generated when it's build to see what ./configure generated. This will tell you what dependencies you need to add to your script. This is most evident when the build fails and says it's looking for X. You add X and try again until it completely compiles. Even if the compile is a success, I look to see if there are any dependencies it's looking for that it bypassed. That dependency could unlock additional functionality.

I was thinking about this and I'm confused as to why you need pkgutils? LFScript already does this for you.

I use pkgutils as a package manager because that way I can reuse binaries on other machines easily.
Pkgutils only needs libarchive and you can use Pkgfiles/buildscripts from CRUX, NutyX, MIX or make your own, very similar to the build instructions from the LFS-books.
There are some binaries you can find too. You can even use archlinux-binaries by renaming the binary and optionally removing some files like .MTREE and .PKGINFO that archlinux uses.