mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: sarcarsh@gmail.com
Cc: "Marek Kierdelewicz" <marek@piasta.pl>,
	"Gustavo Guillermo Pérez" <gustavo@compunauta.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Corrupted Hard Drive after activating intel I/oat dma
Date: Fri, 28 Dec 2007 21:10:56 -0500	[thread overview]
Message-ID: <24730.1198894256@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sat, 29 Dec 2007 04:21:44 +0530." <47757E00.1040905@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 872 bytes --]

On Sat, 29 Dec 2007 04:21:44 +0530, Shourya Sarcar said:
> Marek Kierdelewicz wrote:
> 
> > 
> > I'm a gentoo@laptop user myself. This distro is very disk-demanding
> > because of the frequent compilations. In my opinion it's not the best
> > distro for a mobile system. No wonder your disk gave out :(.
> 
> Can you substantiate "distro is very disk-demanding
> because of the frequent compilations" ?

As I understand it, the gentoo philosophy is 'update by patching the source,
then compiling it'.  So basically, the way the kernel is updated with a
"patch/make/make install", you apply *all* updates that way.  This can suck
if you have things like OpenOffice and Firefox on your machine, and you get
to recompile them to update. And even if you don't, all it takes is one update
to the wrong /usr/include file, and you end up recompiling 3/4 of the binaries
in /usr.

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  reply	other threads:[~2007-12-29  2:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-28  1:49 Gustavo Guillermo Pérez
2007-12-28  3:03 ` Marek Kierdelewicz
2007-12-28 22:51   ` Shourya Sarcar
2007-12-29  2:10     ` Valdis.Kletnieks [this message]
2008-01-07 17:57   ` Gustavo Guillermo Pérez
2007-12-29  2:12 ` Shannon Nelson

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=24730.1198894256@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=gustavo@compunauta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marek@piasta.pl \
    --cc=sarcarsh@gmail.com \
    /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

all inboxes | Powered by JetHome®