From: "C. Brewer" <cbrewer@stealthaccess.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] USE Linux 2.6.x
Date: Tue, 21 Oct 2003 20:44:23 -0700 [thread overview]
Message-ID: <200310212044.30947.cbrewer@stealthaccess.net> (raw)
In-Reply-To: <20031022002531.1bfc861b.spider@gentoo.org>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 2763 bytes --]
On Tuesday 21 October 2003 3:25, Spider wrote:
> begin quote
> Then fix pcmcia-cs and alsa-driver before you suggest anything. as it
> is, my machine won't boot properly without pcmcia-cs -and- alsa, as they
> IRQ conflict unless loaded in a certain order.
Excuse me? "I" should fix these?
> They are both dependant on the target module, and theres no way in a
> gnomes purple hell you are going to get me into a state where I can
> reboot first, and then rebuild the modules, only to reboot again so I
> have a working boot session. uh-oh- NO.
Under those conditions likely not.....
> And no, you won't get me to emerge it with SLOT="purple-gnomes-2.4.44"
> either, Just because I sat down and got my own kerneltree installed into
> usr/src/testkernelwithextraJFSpatches , and then loose my existing ,
> working, tried kernelset.
Okay, this part comes across barely intelligible, but if it helps substitute
TARGET= for SLOT=.. of course I did point out it was a suggestion, not a
solution, and you have offered up what counterproposal?
> When you get this set to -automagically- detect the target kernel.,
> build modules and fix. then ok.
Again with the when "i" thing...
> if you want it to depend on the running kernel, erm... No. theres a few
> things already that do so, and that is -BROKEN- behaviour. I don't even
> -HAVE- the sources for my running kernel at most times. What? No I
> don't need them. I shouldn't need to have my sources for the hard
> compiled and working copy of 2.4.18-saviour with extra everything that I
> know boots all my machines and I have in a .tar stored away for working
> order.
"I" don't want to have it depend on a running kernel, or on a symlink, All I
was saying is that in most cases it'd probably be just easier to boot into a
running kernel and build your non-essential mod package, I realize that this
is not always the case.
> Yes, this thread invoked a lot of hot emotions from my side.
>
>
> // Spider
Well, guess what? I was pretty pissed off _before_ I saw your mail, so you
can imagine where I'm at now, especially since I've asked a couple of times
why this symlink is necessary, when it's highly discouraged. If a package
needs this symlink, mask it, get it fixed upstream or dont carry it at all
ffs. I point out the bad ones when I see them, and I atleast proffered a
suggestion. I was civil when this was a discussion, but turning this into a
pissing match was sheer stupidity. But I guess I'm just the stupid end user
with no say, I guess? Atleast when I'm being a prick, I only represent me.
--
Chuck Brewer
Registered Linux User #284015
Get my gpg public key at pgp.mit.edu!! Encrypted e-mail preferred.
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-22 3:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 12:48 [gentoo-dev] USE Linux 2.6.x Dhruba Bandopadhyay
2003-10-21 12:58 ` Mike Frysinger
2003-10-21 15:39 ` C. Brewer
2003-10-21 16:25 ` Thomas de Grenier de Latour
2003-10-21 17:44 ` C. Brewer
2003-10-21 20:15 ` Grant Goodyear
2003-10-22 3:11 ` C. Brewer
2003-10-21 20:53 ` Martin Schlemmer
2003-10-21 22:25 ` Spider
2003-10-22 3:44 ` C. Brewer [this message]
2003-10-22 8:15 ` Chris Smith
2003-10-22 8:17 ` Paul de Vrieze
2003-10-22 18:27 ` C. Brewer
2003-10-22 18:46 ` Brian Jackson
2003-10-22 19:23 ` Paul de Vrieze
2003-10-22 19:47 ` C. Brewer
2003-10-22 20:06 ` Spider
2003-10-22 10:40 ` Spider
2003-10-22 18:07 ` C. Brewer
2003-10-22 19:01 ` Spider
2003-10-22 11:20 ` Patrick Lauer
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=200310212044.30947.cbrewer@stealthaccess.net \
--to=cbrewer@stealthaccess.net \
--cc=gentoo-dev@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