From: "J García" <jyo.garcia@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] initial compile time
Date: Mon, 28 Aug 2017 23:50:38 -0600 [thread overview]
Message-ID: <CAGQH77fGY2oddX_K=KW=uFMPXHrSZiRGJ0qtLarugZAD2XSVTg@mail.gmail.com> (raw)
In-Reply-To: <KseV39C--3-0@tutanota.com>
2017-08-28 14:20 GMT-06:00 <mad.scientist.at.large@tutanota.com>:
>
> used about 3 lines of USE flags, actually it was less than a half hour, which doesn't surprise me if the stage 3 is compiled. i am using a fairly quick drive ;(and i was watching vid) had 2 small problems but i'll try again off the live dvd.
You mean 3 lines of ~80 characters of USE flags in make.conf?
That is a lot and shurely will come and bite you in the future.
I guess most of us learn a sane way to handle use flags the hard way,
just sharing,
these days my USE flags in make.conf are less than one line even less
than 8 flags,
I would say a good aproach is to select the right profile for your
need is the most important, check the flags that it has(emerge
--info), and then only the flags that you really really want on
*every* package you put in make.conf, everything else goes to
/etc/portage/package.use/my.use on a per package basis, and everything
else portage finds out it needs to build what i want goes to
/etc/portage/package.use/zzz_auto.use.
And keep your world to only what you need, learn about --oneshot as
soon as you can.
i got an error with the rbind "mount --rbind /sys /mnt/gentoo/sys" i
should have guessed the stage3 was just compressed,
> and it also couldn't find a "sane" /dev. probably both due to centos not playing nice (and my mounting and unmounting of a couple partitions).
I would recomed using something like the base livecd or systemrescuecd
for an install with OpenRC. and only use something like CentOS(if you
are talking about 7) if you want to use systemd, and then make use of
systemd-nspawn and not chroot and bind mounts, and the systemd stage3.
next prev parent reply other threads:[~2017-08-29 5:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 11:41 [gentoo-user] initial compile time mad.scientist.at.large
2017-08-28 16:08 ` Alan McKinnon
2017-08-28 16:47 ` Rich Freeman
2017-08-28 16:48 ` Alan McKinnon
2017-08-28 18:37 ` allan gottlieb
2017-08-28 18:45 ` J. Roeleveld
2017-08-28 20:34 ` mad.scientist.at.large
2017-08-28 18:55 ` Rich Freeman
2017-08-28 20:31 ` mad.scientist.at.large
2017-08-29 0:18 ` allan gottlieb
2017-08-28 20:20 ` mad.scientist.at.large
2017-08-29 5:50 ` J García [this message]
2017-08-29 11:17 ` Rich Freeman
2017-08-29 11:08 ` Alan McKinnon
2017-08-29 16:47 ` Mick
2017-08-29 19:30 ` Dale
2017-08-30 22:05 ` Alan McKinnon
2017-08-30 22:03 ` Alan McKinnon
2017-08-28 16:55 ` John Blinka
2017-08-28 20:09 ` Alan McKinnon
2017-08-28 20:25 ` mad.scientist.at.large
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGQH77fGY2oddX_K=KW=uFMPXHrSZiRGJ0qtLarugZAD2XSVTg@mail.gmail.com' \
--to=jyo.garcia@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox