public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: <burlingk@cv63.navy.mil>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] A Theoretical install Question
Date: Wed, 23 May 2007 09:13:18 +0900	[thread overview]
Message-ID: <AA0639A1EB70AE409130258CE7BDC3183237E9@messenger.cv63.navy.mil> (raw)



> -----Original Message-----
> From: Dan Farrell [mailto:dan@spore.ath.cx] 
> Sent: Wednesday, May 23, 2007 12:27 AM
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] A Theoretical install Question
> 
> 
> Not to mention you will spend much longer waiting for 
> everything to download then you'd have to wait for everything 
> do download on demand. It would probably be more desirable 
> for you to keep a network-shared distfiles than mirror the 
> servers.  Then there's the age-old 'static hosts file' 
> problem - just like the giant host file describing everyone 
> took longer to transfer than to become outdated back in the 
> glorious days of UNIX, it will also probably take longer to 
> dowload all distfiles ever than it will for those distfiles 
> to become outdated.  In conclusion, I think this is a rather 
> silly idea. 
> -- 

You are right I think.
If nothing else the handbook says that Gentoo etiquite says not
to rsync your portage tree more than once a day.  For the average
distro, once a week or even once a month is more than sufficient
to keep up with the packages in the main branch.

I think that I will probably be better off doing a stage three
install, then doing an 'emerge -euD world' or similar before
moving on from there.  After that, I can just make sure to watch
the FAQ's and walkthroughs when I install Xorg to make sure that
I do it right.  ^_^

Hopefully by the time I build the machine, either A) I can get
a decent nVidia card, or B) the ATI drivers will be released. ^_^

I preffer nVidia, but if the ATI drivers go open source (crossing
my fingers but not holding my breath), then that will be a good
option as well.

^_^

--
gentoo-user@gentoo.org mailing list



             reply	other threads:[~2007-05-23  0:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23  0:13 burlingk [this message]
2007-05-23  0:21 ` [gentoo-user] A Theoretical install Question Bo Ørsted Andresen
2007-05-23  8:25   ` Neil Bothwick
2007-05-23  0:25 ` Hemmann, Volker Armin
2007-05-23  0:46   ` Dale
2007-05-23  0:57     ` Hemmann, Volker Armin
2007-05-23  2:37       ` Dale
2007-05-23  8:22       ` Neil Bothwick
  -- strict thread matches above, loose matches on Subject: below --
2007-05-23  1:40 burlingk
2007-05-22  7:42 burlingk
2007-05-22  8:18 ` Neil Bothwick
2007-05-22  7:13 burlingk
2007-05-22  7:26 ` Dan Farrell
2007-05-22  6:47 burlingk
2007-05-22  7:02 ` Hemmann, Volker Armin
2007-05-22  5:13 burlingk
2007-05-22  4:55 burlingk
2007-05-22  4:06 burlingk
2007-05-22  4:30 ` Iain Buchanan
2007-05-22  5:01 ` Naga
2007-05-22  5:23   ` Dale
2007-05-22  5:39   ` Iain Buchanan
2007-05-22  6:30     ` Naga
2007-05-22 13:03       ` Bo Ørsted Andresen
2007-05-22  6:34 ` Hemmann, Volker Armin
2007-05-22 15:27   ` Dan Farrell

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=AA0639A1EB70AE409130258CE7BDC3183237E9@messenger.cv63.navy.mil \
    --to=burlingk@cv63.navy.mil \
    --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