From: Tim Tassonis <timtas@cubic.ch>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Swap doesn't work
Date: Sun, 27 Oct 2002 21:13:00 +0100 [thread overview]
Message-ID: <E185tmO-0002mu-00@trivadis.com> (raw)
In-Reply-To: <20021027200308.A26047@infradead.org>
> Sorry, tons of people that have absolute no clue about the package
> internals set up their systems themselves and make mistakes. nothing
> spectacular, but they just don't have those people who know the
> packages in detail and can notice and fix the bugs. Just get binary
> rpm/deb whatever of the toolchain and reproduce.
As I said, I can't reproduce it even on my lfs system, maybe because my
disks are scsi. So reproducing on my Red Hat wouldn't really help, would
it?
> > lfs has a manual with clearly specified package versions, patches and
> > order of "toolchaining". It might well be a bug in that chain, but
> > other distros have bugs, too. Signing software doesn't make it
> > superior, after all.
>
> but having people who understand the software maintain the
> packages sometimes helps :)
As far as I know, lfs does not maintain the packages. binutils and gcc are
maintained by FSF to my knowledge.
Bye
Tim
next prev parent reply other threads:[~2002-10-27 20:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-27 19:41 Swap doesn't work Tim Tassonis
2002-10-27 20:03 ` Christoph Hellwig
2002-10-27 20:13 ` Tim Tassonis [this message]
2002-10-27 21:17 ` Alan Cox
2002-10-28 12:22 ` Tim Tassonis
2002-10-29 12:15 ` kernel BUG in page_alloc.c (rmqueue function) Steffen Persvold
-- strict thread matches above, loose matches on Subject: below --
2002-10-27 11:07 Swap doesn't work Vladimír Třebický
2002-10-27 12:50 ` Alex Riesen
2002-10-27 13:12 ` Alan Cox
2002-10-27 14:48 ` Vladimír Třebický
2002-10-27 15:21 ` Alan Cox
2002-10-26 15:14 Vladimír Třebický
2002-10-26 15:44 ` Alan Cox
2002-10-27 9:23 ` Alex Riesen
2002-10-27 8:51 ` Vladimír Trebický
2002-10-27 9:34 ` Alexander Puchmayr
2002-10-27 10:28 ` Alex Riesen
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=E185tmO-0002mu-00@trivadis.com \
--to=timtas@cubic.ch \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.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