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.
so there are two little things wrong with the line you posted. The process is fine, just two minor details:
1. it should be 'tar Jx' not 'tar xz' after the pipe, because the data archive you extracted before the pipe has *.tar.xz format.
2. Make sure you have permission to write to /tmp folder. You can overcome this by either doing 'sudo tar' after the pipe, or extract to somewhere in your home directory (eg ~/.tmp)
As an example, I just put the following in my command line and it worked (after making sure that /tmp/google-chrome exists):
Code:
ar -p google-chrome-stable_current_amd64.deb data.tar.xz | sudo tar Jx -C /tmp/google-chrome/
so there are two little things wrong with the line you posted. The process is fine, just two minor details:
1. it should be 'tar Jx' not 'tar xz' after the pipe, because the data archive you extracted before the pipe has *.tar.xz format.
2. Make sure you have permission to write to /tmp folder. You can overcome this by either doing 'sudo tar' after the pipe, or extract to somewhere in your home directory (eg ~/.tmp)
As an example, I just put the following in my command line and it worked (after making sure that /tmp/google-chrome exists):
Code:
ar -p google-chrome-stable_current_amd64.deb data.tar.xz | sudo tar Jx -C /tmp/google-chrome/
I ran your command and it worked. So now I see three folders in /tmp/google-chrome/. Etc, opt, and usr. So do I just copy the folders to where they should be in /?
I ran your command and it worked. So now I see three folders in /tmp/google-chrome/. Etc, opt, and usr. So do I just copy the folders to where they should be in /?
Yes, the reason why I put it in /tmp/google-chrome is for packaging/archiving purposes (This is how slackpkg works), also to audit the files to see if everything looks fine. If you don't care about it you could just do:
Code:
ar -p google-chrome-stable_current_amd64.deb data.tar.xz | sudo tar Jx -C /
and it would extract the files into the root directory.
Yes, the reason why I put it in /tmp/google-chrome is for packaging/archiving purposes (This is how slackpkg works), also to audit the files to see if everything looks fine. If you don't care about it you could just do:
Code:
ar -p google-chrome-stable_current_amd64.deb data.tar.xz | sudo tar Jx -C /
and it would extract the files into the root directory.
How would I know the what applications I need for the program?
How would I know the what applications I need for the program?
I'm not sure what you mean? When you extract the files to root directory it's all in place. Google Chrome executable is /usr/bin/google-chrome-stable, which is a symlink to /opt/google/chrome/google-chrome
I'm not sure what you mean? When you extract the files to root directory it's all in place. Google Chrome executable is /usr/bin/google-chrome-stable, which is a symlink to /opt/google/chrome/google-chrome
In /tmp/google-chrome/usr/share there is a folder called gnome-control-center and in my /usr/share I don't have a gnome-control-center folder. Also in /tmp/google-chrome/etc there is a folder called cron.daily, which I don't have in my /etc.
In /tmp/google-chrome/usr/share there is a folder called gnome-control-center and in my /usr/share I don't have a gnome-control-center folder. Also in /tmp/google-chrome/etc there is a folder called cron.daily, which I don't have in my /etc.
What should I do?
Just ignore/delete them. If you don't have Gnome DE, then you're not using gnome-control-center. I believe the files under that directory adds Chrome preference tab in gnome-control-center (Never used it myself). You can safely delete the cron file too. Slackbuilds comment says the cron job is only for Debian/Ubuntu.
Just ignore/delete them. If you don't have Gnome DE, then you're not using gnome-control-center. I believe the files under that directory adds Chrome preference tab in gnome-control-center (Never used it myself). You can safely delete the cron file too. Slackbuilds comment says the cron job is only for Debian/Ubuntu.
So I deleted the cron.daily folder in /etc and gnome-control-center in /usr/share. When I type google-chrome-stable I get an error saying I need libgconf, but in BLFS there is no libgconf? What do I do?
EDIT: I got Google Chrome running by install GConf for the BLFS list of packages
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.