Re: Linux kernel history from 0.0.1
On 12/12/07, Dave Jones <[EMAIL PROTECTED]> wrote: > Sadly there doesn't seem to be any online archives of the period between > Linux-activists ending in 1993 and Linux Kernel from 1998. Anyone? > (I find it amazing that five whole years of history have disappeared > from the net). I have mail archives from ~1.3.30 through around 2000 that I'm in the process of recovering. They won't be complete, but they'll include any and all release announcements and patches Linus and Alan posted to the list. You're welcome to whatever I have when I get it back. -sb -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [RFT] Port 0x80 I/O speed
On 12/11/07, Rene Herman <[EMAIL PROTECTED]> wrote: > Good day. > > Would some people on x86 (both 32 and 64) be kind enough to compile and run > the attached program? This is about testing how long I/O port access to port > 0x80 takes. It measures in CPU cycles so CPU speed is crucial in reporting. model name : Intel(R) Pentium(R) 4 CPU 3.20GHz cpu MHz : 3201.345 cycles: out 3026, in 2204 cycles: out 3031, in 2182 cycles: out 3019, in 2196 cycles: out 3030, in 2201 cycles: out 3013, in 2186 -sb -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [RFT] Port 0x80 I/O speed
On 12/11/07, Rene Herman [EMAIL PROTECTED] wrote: Good day. Would some people on x86 (both 32 and 64) be kind enough to compile and run the attached program? This is about testing how long I/O port access to port 0x80 takes. It measures in CPU cycles so CPU speed is crucial in reporting. model name : Intel(R) Pentium(R) 4 CPU 3.20GHz cpu MHz : 3201.345 cycles: out 3026, in 2204 cycles: out 3031, in 2182 cycles: out 3019, in 2196 cycles: out 3030, in 2201 cycles: out 3013, in 2186 -sb -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux kernel history from 0.0.1
On 12/12/07, Dave Jones [EMAIL PROTECTED] wrote: Sadly there doesn't seem to be any online archives of the period between Linux-activists ending in 1993 and Linux Kernel from 1998. Anyone? (I find it amazing that five whole years of history have disappeared from the net). I have mail archives from ~1.3.30 through around 2000 that I'm in the process of recovering. They won't be complete, but they'll include any and all release announcements and patches Linus and Alan posted to the list. You're welcome to whatever I have when I get it back. -sb -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 1/6] Suppress A.OUT library support if !CONFIG_BINFMT_AOUT [try #5]
On 11/12/07, David Howells <[EMAIL PROTECTED]> wrote:
> SL Baur <[EMAIL PROTECTED]> wrote:
>
> > (push '("/Kbuild" . makefile-mode) auto-mode-alist)
>
> Does that work for Kbuild.asm too, more to the point?
Of course. It works for any filename beginning with the string "Kbuild". Major
mode rules are on a first match basis, so you have to make sure this rule is
ahead of the .asm rule. I'll push a patch to the XEmacs guys so it works this
way by default, someone else can deal with Stallman.
Please take the emacsism out of the file as it bothers Andrew and others.
-sb
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 1/6] Suppress A.OUT library support if !CONFIG_BINFMT_AOUT [try #5]
On 11/12/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Mon, 12 Nov 2007 15:34:40 + David Howells <[EMAIL PROTECTED]> wrote:
>
> > Andrew Morton <[EMAIL PROTECTED]> wrote:
> >
> > > > +# -*- makefile -*-
> > >
> > > what's that?
> >
> > Ah... That tells emacs that it's a makefile. In Kbuild.asm emacs thinks
> > its
> > an Assembly file and not a makefile. This causes it to attempt to do
> > automatic indentation on it. Do you want me to drop these annotation
> > comments?
>
> Doesn't worry me, but I'd suggest that such annotation be added to all such
> files in a single separate patch.
>
> otoh it'd be pretty dumb of emacs if there wasn't some way of telling it
> the type of a file external from that file itself.
(push '("/Kbuild" . makefile-mode) auto-mode-alist)
-sb
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 1/6] Suppress A.OUT library support if !CONFIG_BINFMT_AOUT [try #5]
On 11/12/07, Andrew Morton [EMAIL PROTECTED] wrote: On Mon, 12 Nov 2007 15:34:40 + David Howells [EMAIL PROTECTED] wrote: Andrew Morton [EMAIL PROTECTED] wrote: +# -*- makefile -*- what's that? Ah... That tells emacs that it's a makefile. In Kbuild.asm emacs thinks its an Assembly file and not a makefile. This causes it to attempt to do automatic indentation on it. Do you want me to drop these annotation comments? Doesn't worry me, but I'd suggest that such annotation be added to all such files in a single separate patch. otoh it'd be pretty dumb of emacs if there wasn't some way of telling it the type of a file external from that file itself. (push '(/Kbuild . makefile-mode) auto-mode-alist) -sb - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 1/6] Suppress A.OUT library support if !CONFIG_BINFMT_AOUT [try #5]
On 11/12/07, David Howells [EMAIL PROTECTED] wrote: SL Baur [EMAIL PROTECTED] wrote: (push '(/Kbuild . makefile-mode) auto-mode-alist) Does that work for Kbuild.asm too, more to the point? Of course. It works for any filename beginning with the string Kbuild. Major mode rules are on a first match basis, so you have to make sure this rule is ahead of the .asm rule. I'll push a patch to the XEmacs guys so it works this way by default, someone else can deal with Stallman. Please take the emacsism out of the file as it bothers Andrew and others. -sb - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: false positive in checkpatch.pl (complex macro values)
On 8/24/07, SL Baur <[EMAIL PROTECTED]> wrote: > I think the > error message is wrong. I mean the error message is badly worded. That's bad C and the macro needs deletion a lot more than it needs an extra set of parens. Been chasing a heisen bug too long. Need sleep. Sorry. -sb - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: false positive in checkpatch.pl (complex macro values)
On 8/24/07, Andy Whitcroft <[EMAIL PROTECTED]> wrote:
> Mike Frysinger wrote:
> > in some code that does like:
> > #define foo { a, b, c, \
> > d, e, f, g }
> > ...
> > int boo[] = foo;
> > ...
> >
> > checkpatch.pl throws a fit:
> > ERROR: Macros with complex values should be enclosed in parenthesis
> > #10: FILE: ...
> > +#define foo {a, b, c, d}
> >
> > perhaps the check should also allow {...} ? or ignore lists like this ...
> > -mike
>
> Ok, we can add that to the check. Next update will allow that.
>
> Thanks for the report.
I sent a reply accidentally only to Mike and not the list. I think the
error message is wrong. That is really ugly code. Linux Kernel code
believes in C not preprocessor tricks, so why would you need this?
Who uses code like this, by the way?
-sb
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: false positive in checkpatch.pl (complex macro values)
On 8/24/07, Andy Whitcroft [EMAIL PROTECTED] wrote:
Mike Frysinger wrote:
in some code that does like:
#define foo { a, b, c, \
d, e, f, g }
...
int boo[] = foo;
...
checkpatch.pl throws a fit:
ERROR: Macros with complex values should be enclosed in parenthesis
#10: FILE: ...
+#define foo {a, b, c, d}
perhaps the check should also allow {...} ? or ignore lists like this ...
-mike
Ok, we can add that to the check. Next update will allow that.
Thanks for the report.
I sent a reply accidentally only to Mike and not the list. I think the
error message is wrong. That is really ugly code. Linux Kernel code
believes in C not preprocessor tricks, so why would you need this?
Who uses code like this, by the way?
-sb
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: false positive in checkpatch.pl (complex macro values)
On 8/24/07, SL Baur [EMAIL PROTECTED] wrote: I think the error message is wrong. I mean the error message is badly worded. That's bad C and the macro needs deletion a lot more than it needs an extra set of parens. Been chasing a heisen bug too long. Need sleep. Sorry. -sb - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] update checkpatch.pl to version 0.08
On 7/24/07, Adrian Bunk <[EMAIL PROTECTED]> wrote: There are more important things than exploiting the corner cases of codingstyle, e.g. could you teach checkpatch.pl to give exactly two errors for the following code? while (a); for (b = 0; b < 50; b++); for (c = 0; c < sizeof(struct module); c++) d = e; There are three errors there. The while (a) busy wait needs a cpu_relax() or something, the first for is at the wrong level of indentation and the second for is at the wrong level of indentation relative to the first one. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] update checkpatch.pl to version 0.08
On 7/24/07, Adrian Bunk [EMAIL PROTECTED] wrote: There are more important things than exploiting the corner cases of codingstyle, e.g. could you teach checkpatch.pl to give exactly two errors for the following code? while (a); for (b = 0; b 50; b++); for (c = 0; c sizeof(struct module); c++) d = e; There are three errors there. The while (a) busy wait needs a cpu_relax() or something, the first for is at the wrong level of indentation and the second for is at the wrong level of indentation relative to the first one. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
On 6/19/07, Dave Neuer <[EMAIL PROTECTED]> wrote: It was Apache. Apache showed corporate users and small businesses desperate to cash in on the Interweb c. 1995-1998 ... Right time period ... Linux was a tool for UNIX sysadmins and admin wannabes to practice their UNIX chops at home - or a conveniently inexpensive platform on which to run Apache. Companies -- other than Linux distributors -- didn't bet their business on it. Wrong conclusion. Been there, done that, helped bet the company on networks based on Linux servers. Apache's success greatly contributed to the corporate acceptance of Linux, IMHO. Wrong again. Apache was not allowed to distribute strong encryption for e-commerce servers over that time frame. The solution we bought was O/S agnostic. And to quote your next message, you have given all the reasons why NetBSD has already taken over the world. By the time of Linux 2.0.x, it could stay up for years at a time even if it was running on garbage. There was no alternative even *close*. -sb - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
Sure, but was it Linux in embedded devices that made Linux what it is today, or was it GNU/Linux? No, it was the fact that Linux has always been able to run on garbage. My introduction to Linux was in 1995 when I was given a network of computers made out of back-laboratory garbage and US$0 software budget and told to make it work. None of the BSDs could cut it, but Linux could. User space Unix tool rewrites all of which I could have gotten from *BSD had absolutely nothing to do with it. I doubt that I am typical. -sb - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
Sure, but was it Linux in embedded devices that made Linux what it is today, or was it GNU/Linux? No, it was the fact that Linux has always been able to run on garbage. My introduction to Linux was in 1995 when I was given a network of computers made out of back-laboratory garbage and US$0 software budget and told to make it work. None of the BSDs could cut it, but Linux could. User space Unix tool rewrites all of which I could have gotten from *BSD had absolutely nothing to do with it. I doubt that I am typical. -sb - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
On 6/19/07, Dave Neuer [EMAIL PROTECTED] wrote: It was Apache. Apache showed corporate users and small businesses desperate to cash in on the Interweb c. 1995-1998 ... Right time period ... Linux was a tool for UNIX sysadmins and admin wannabes to practice their UNIX chops at home - or a conveniently inexpensive platform on which to run Apache. Companies -- other than Linux distributors -- didn't bet their business on it. Wrong conclusion. Been there, done that, helped bet the company on networks based on Linux servers. Apache's success greatly contributed to the corporate acceptance of Linux, IMHO. Wrong again. Apache was not allowed to distribute strong encryption for e-commerce servers over that time frame. The solution we bought was O/S agnostic. And to quote your next message, you have given all the reasons why NetBSD has already taken over the world. By the time of Linux 2.0.x, it could stay up for years at a time even if it was running on garbage. There was no alternative even *close*. -sb - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
