From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] initial compile time
Date: Tue, 29 Aug 2017 17:47:40 +0100 [thread overview]
Message-ID: <5620842.vzpmVGuN3s@dell_xps> (raw)
In-Reply-To: <6d424668-42e8-1050-30bc-b4520de4487a@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2188 bytes --]
On Tuesday, 29 August 2017 12:08:12 BST Alan McKinnon wrote:
> On 28/08/2017 22:20, mad.scientist.at.large@tutanota.com wrote:
> > |it's not so hard yet, just hard to get by reading it in advance, doing
> >
> > it is fairly straight forward.
>
> It only seems like it might be tricky when reading it.
> Running Gentoo involves steps that you do on almost no other distro, so
> the words on the web page are unfamiliar.
>
> Almost everyone that's done it for the first time in the last 5 years
> and reported up says "Gee, that wasn't so hard! A lot easier than I ever
> thought it would be!"
>
> It's also very obvious what each step actually did, but you have to do
> it yourself once - it's obvious in petrospec.
>
> Welcome to Gentoo-land. May your stay be long and happy and fruitful.
>
> Your next assigned task (to be done sometime in the next year) is to
> repeat the whole process on a test rig and do it from a stage 1. Like we
> all did 15 years ago. If serious street cred brownie points is what you
> are after, that's how you get 'em!
Nope. You need to do a stage 1 on nothing newer than a Pentium 3 or
equivalent for it to count, run out of compile space on PORTAGE_TMPDIR,
reformat and start again.
For extra street cred you would of course install ~arch and have to work-
around every darn bug you came across by the n'th time you had to start
recompiling from scratch, because both gcc and the profile USE flags changed 3
times during the 2 weeks it would invariably take you to finish your install.
In between all this pain, you may also discover your MoBo would hard lock
every time your mismatched RAM modules started paging over to swap ... O_O
but after a hard reboot it would be OK until the next big compile.
I understand this to be an endeavour not dissimilar to climbing Everest during
an avalanche.
PS. Did I mention you would have to do all of the above using a dial-up modem,
which would require off-tree modules, because your PC came with a Winmodem?
PPS. In case you have never been cursed with using a winmodem, check the 2nd
bullet point at the bottom of this page:
http://www.columbia.edu/kermit/winmodem.html
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-08-29 16:48 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
2017-08-29 11:17 ` Rich Freeman
2017-08-29 11:08 ` Alan McKinnon
2017-08-29 16:47 ` Mick [this message]
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=5620842.vzpmVGuN3s@dell_xps \
--to=michaelkintzios@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