On Tue, Apr 24, 2001 at 02:14:40PM -0700, Aaron Lehmann wrote:
> On Wed, Apr 25, 2001 at 12:33:25AM +1000, Craig Sanders wrote:
> > On Tue, Apr 24, 2001 at 07:30:47PM +1000, Herbert Xu wrote:
> > >
> > > Kernel-headers-2.4.2 is built with the default config file, and the
> > > other ones are built
On Wed, Apr 25, 2001 at 09:05:42AM +1000, Herbert Xu wrote:
> On Tue, Apr 24, 2001 at 02:10:48PM -0700, Aaron Lehmann wrote:
> > If they're binary-only, I doubt much compilation will be necessary.
>
> They don't just come out of nowhere you know...
"Binary-only" is a misnomer, since one could tra
On Wed, Apr 25, 2001 at 09:06:21AM +1000, Herbert Xu wrote:
> Bullshit. Why don't you do a diff instead of talking about something that
> you have no idea about?
Do you deny that the file named autoconf.h contains precicely what I
suggested? I did not attempt to present an exhaustive description
On Tue, Apr 24, 2001 at 03:34:40PM -0400, Sam Hartman wrote:
>
> placed by this scheme. My assumption is that there will be different
> modversions for each kernel configuration and that as such, I will
That's correct.
> then my module-specific concerns go away. Even if you accept that the
> b
On Tue, Apr 24, 2001 at 04:14:18PM -0700, Aaron Lehmann wrote:
> On Wed, Apr 25, 2001 at 09:06:21AM +1000, Herbert Xu wrote:
> > Bullshit. Why don't you do a diff instead of talking about something that
> > you have no idea about?
>
> Do you deny that the file named autoconf.h contains precicely
On Tue, Apr 24, 2001 at 04:10:51PM -0700, Aaron Lehmann wrote:
>
> "Binary-only" is a misnomer, since one could translate them to ASCII
> or EBDIC if they wanted to. I'm not quite sure whether you're
> describing non-free kernel modules or kernel modules distributed in
> precompiled form (or both
On Wed, Apr 25, 2001 at 09:19:29AM +1000, Herbert Xu wrote:
> I'm actually referring to all binary modules. But for binary-only modules
> in particular, since you don't have the luxuary of being able to recompile
> them, it's even more important to supply the builder with enough information
> assu
On Wed, Apr 25, 2001 at 09:17:35AM +1000, Herbert Xu wrote:
> > One file, composing of a few kilobytes, is an autogenerated header
> > consisting of #define correctives enumerating the configuration.
>
> I think it's fairly clear that you were trying suggest that this is the
> ONLY difference betw
On Tue, Apr 24, 2001 at 04:32:03PM -0700, Aaron Lehmann wrote:
>
> But if I could ask a favor from you, why don't you post a list of
> affected files, and hopefully some description of these and why they
> are changed? There seems to be much confusion about the differences
I won't bore everyone h
Michael Stone <[EMAIL PROTECTED]> wrote:
> On Wed, Apr 25, 2001 at 09:19:29AM +1000, Herbert Xu wrote:
>> I'm actually referring to all binary modules. But for binary-only modules
>> in particular, since you don't have the luxuary of being able to recompile
>> them, it's even more important to sup
On Wed, Apr 25, 2001 at 09:47:14AM +1000, Herbert Xu wrote:
> No, but they can at least compile one for i386 easily as we're providing
> matching kernel-headers. You're in exactly the same situation
> (i.e., without binary modules) anyway if you compile your own kernel so
> IMHO it's a moot point.
On Wed, Apr 25, 2001 at 09:15:09AM +1000, Herbert Xu wrote:
> I think your concerns are not well-founded. If you have a sane build
> system, then building them is as simple as a for loop. Have look at the
> way kernel-image-i386 is built if you don't understand what I'm talking
> about.
Not ever
On Tue, Apr 24, 2001 at 05:26:27PM -0700, Aaron Lehmann wrote:
>
> Ok, so why did this come up at all in the discussion of the kernel
> package bloat? It seems to me that providing optimized kernels is a
Because someone asked why the kernel-headers necessary. Their presence
allows both our modul
On Wed, Apr 25, 2001 at 10:31:06AM +1000, Daniel Stone wrote:
> On Wed, Apr 25, 2001 at 09:15:09AM +1000, Herbert Xu wrote:
> > I think your concerns are not well-founded. If you have a sane build
> > system, then building them is as simple as a for loop. Have look at the
> > way kernel-image-i38
On Wed, 25 Apr 2001, Daniel Stone wrote:
> On Wed, Apr 25, 2001 at 09:15:09AM +1000, Herbert Xu wrote:
> > I think your concerns are not well-founded. If you have a sane build
> > system, then building them is as simple as a for loop. Have look at the
> > way kernel-image-i386 is built if you do
Previously Daniel Stone wrote:
> Linux Kernel Developer
I love this.. the only mention of 'daniel.*stone' in the entire
kernel is a trivial patch to drivers/sound/sb_card.c..
Wichert.
--
/ Generally uninteresting signature - i
On Tue, Apr 24, 2001 at 09:33:13AM -0500, Adam Heath wrote:
> On Wed, 25 Apr 2001, Daniel Stone wrote:
>
> > On Wed, Apr 25, 2001 at 09:15:09AM +1000, Herbert Xu wrote:
> > > I think your concerns are not well-founded. If you have a sane build
> > > system, then building them is as simple as a fo
On Wed, Apr 25, 2001 at 02:40:27AM +0200, Wichert Akkerman wrote:
> Previously Daniel Stone wrote:
> > Linux Kernel Developer
>
> I love this.. the only mention of 'daniel.*stone' in the entire
> kernel is a trivial patch to drivers/sound/sb_card.c..
Plus, numerous Netfilter things, which I have
Someone, please create a
[EMAIL PROTECTED] list.
The rest, get over it.
--
Daniel Stone
Linux Kernel Developer
[EMAIL PROTECTED]
Daniel Stone,
You need to update your people skills. Given your present arrogance and
attitude, maybe you shouldn't be a debian maint. Why should you be trusted?
-Jim
On Tue, Apr 24, 2001 at 10:05:00AM -0500, John Goerzen wrote:
> Again, I'm not ranting that NMUs occured. I'm ranting that they were
> not done correctly.
Fair enough. It is irresponsible for developers to be using
any packages which aren't in the archive to build packages,
as happened in this ca
On Wed, 25 Apr 2001, Daniel Stone wrote:
> > Who says you have to compile debian packages on only machines you own?
>
> So tell elmo to get me through, and not, not do anything for 2 months. The
> only other faster machines I have access to, run RedHat or Mandrake, and I
> can't afford anything be
On Wed, 25 Apr 2001, Daniel Stone wrote:
> Someone, please create a
> [EMAIL PROTECTED] list.
s/daniel-stone-is-not-really-a-Linux-Kernel-Developer/daniel-stone-is-looking-to-make-trouble-with-the-listmasters-and-alienate-even-more-people/
Hamish Moffatt <[EMAIL PROTECTED]> wrote:
> Personally I think the best way to avoid the problem is never
> to install non-official/pre-release packages.
Which is good but then how are you supposed to test them :) Just install
them in a chroot and you won't have to worry about it.
--
Debian GNU/
Hello,
when I tried to upgrade libc6 with apt-get 0.5.3, I encountered a
number of problems. As I am not sure what packages are at fault, I
will post here, as maybe some other debian developers can comment.
I think resolving these problems is very important if the freeze is to
take place any time
Is it possible to get make-kpkg adding A note to a kernel-image-package
which is displayed when the kernel-image is installed?
so long...
David
--
__ _ | David "netzwurm" Spreen Kiel, Germany
/ _|___ ___| |__ __ _ _ _ | http://www.netzwurm.cc/ [EMAIL PROTECTE
Brian May <[EMAIL PROTECTED]> wrote:
> when I tried to upgrade libc6 with apt-get 0.5.3, I encountered a
> Preparing to replace libdb2 2:2.4.14-2.7.7.1.c (using
> .../libdb2_2%3a2.7.7-7_i386.deb) ...
> Unpacking replacement libdb2 ...
> Replacing files in old package libc6 ...
At this point any
101 - 127 of 127 matches
Mail list logo
