Re: Microsoft and Xenix.
Beehive -- there's a name I haven't heard in a long time! The ones I remember had dual floppy drives and ran CP/M. I last saw one in about 1985. Wayne [EMAIL PROTECTED] on 06/25/2001 12:11:01 PM To: William T Wilson <[EMAIL PROTECTED]> cc: Rob Landley <[EMAIL PROTECTED]>, "Eric W. Biederman" <[EMAIL PROTECTED]>, Alan Chandler <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (bcc: Wayne Brown/Corporate/Altec) Subject: Re: Microsoft and Xenix. Hi, I first used Unix on a PDP11/44 whilst studying for my Computer Engineering degree at Heriot-Watt University in Edinburgh. I think they and Queen Margaret College, London were the first folk running Unix version 6 outside Bell Labs. If anyone knows where Patrick O'Callaghan is now (ask him). Another Unix like OS was Cromemco Cromix running on bank switched Z80 S-100 kit.(later 68000). I then used SCO Xenix 286 on early Compaq 286 PC's. Companies like Chase, Specialix and Stallion grew up as suppliers of intelligent RS-232 boards. As a result of all these Xenix machines, Wyse sold a hell of a lot of WY50 terminals. Who remembers terminals from Lear Siegler and Beehive. All this was before networking came about. Then the Chase Iolan to connect these same Wyse terminals to the SCO box but through one bit of co-ax instead of multi-core cables. Also you could get 100m away from your SCO box with co-ax. -- Andrew Smith in Edinburgh - 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: Microsoft and Xenix.
Beehive -- there's a name I haven't heard in a long time! The ones I remember had dual floppy drives and ran CP/M. I last saw one in about 1985. Wayne [EMAIL PROTECTED] on 06/25/2001 12:11:01 PM To: William T Wilson [EMAIL PROTECTED] cc: Rob Landley [EMAIL PROTECTED], Eric W. Biederman [EMAIL PROTECTED], Alan Chandler [EMAIL PROTECTED], [EMAIL PROTECTED] (bcc: Wayne Brown/Corporate/Altec) Subject: Re: Microsoft and Xenix. Hi, I first used Unix on a PDP11/44 whilst studying for my Computer Engineering degree at Heriot-Watt University in Edinburgh. I think they and Queen Margaret College, London were the first folk running Unix version 6 outside Bell Labs. If anyone knows where Patrick O'Callaghan is now (ask him). Another Unix like OS was Cromemco Cromix running on bank switched Z80 S-100 kit.(later 68000). I then used SCO Xenix 286 on early Compaq 286 PC's. Companies like Chase, Specialix and Stallion grew up as suppliers of intelligent RS-232 boards. As a result of all these Xenix machines, Wyse sold a hell of a lot of WY50 terminals. Who remembers terminals from Lear Siegler and Beehive. All this was before networking came about. Then the Chase Iolan to connect these same Wyse terminals to the SCO box but through one bit of co-ax instead of multi-core cables. Also you could get 100m away from your SCO box with co-ax. -- Andrew Smith in Edinburgh - 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: Microsoft and Xenix.
Sorry, but I'm hanging on to my old computer manuals. The AIX manuals in particular have sentimemtal value for me. OTOH, I have quite a few old computer magazines (from the 80's) like Byte, Infoworld, etc. I've been intending to get rid of them for some time now, but hated just to throw them away. They're in storage in a neighboring state right now, but my wife probably will be driving there in the next couple of weeks to pick up a few things. If you're interested, she could bring back the magazines and I can tell you exactly what I have. You're welcome to them if you want them. Wayne Rob Landley <[EMAIL PROTECTED]> on 06/24/2001 09:32:43 AM Please respond to [EMAIL PROTECTED] To: Wayne Brown/Corporate/Altec@Altec, John Adams <[EMAIL PROTECTED]> cc: [EMAIL PROTECTED] Subject: Re: Microsoft and Xenix. On Saturday 23 June 2001 22:41, [EMAIL PROTECTED] wrote: > Ah, yes, the RT/PC. That brings back some fond memories. My first > exposure to Unix was with AIX on the RT. I still have some of those > weird-sized RT AIX manuals around somewhere... > > Wayne Ooh! Old manuals! Would you be willing to part with them? I am collecting old manuals, and old computing magazines. I even pay for postage, with a bit of warning that they're coming... Rob - 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: Microsoft and Xenix.
Sorry, but I'm hanging on to my old computer manuals. The AIX manuals in particular have sentimemtal value for me. OTOH, I have quite a few old computer magazines (from the 80's) like Byte, Infoworld, etc. I've been intending to get rid of them for some time now, but hated just to throw them away. They're in storage in a neighboring state right now, but my wife probably will be driving there in the next couple of weeks to pick up a few things. If you're interested, she could bring back the magazines and I can tell you exactly what I have. You're welcome to them if you want them. Wayne Rob Landley [EMAIL PROTECTED] on 06/24/2001 09:32:43 AM Please respond to [EMAIL PROTECTED] To: Wayne Brown/Corporate/Altec@Altec, John Adams [EMAIL PROTECTED] cc: [EMAIL PROTECTED] Subject: Re: Microsoft and Xenix. On Saturday 23 June 2001 22:41, [EMAIL PROTECTED] wrote: Ah, yes, the RT/PC. That brings back some fond memories. My first exposure to Unix was with AIX on the RT. I still have some of those weird-sized RT AIX manuals around somewhere... Wayne Ooh! Old manuals! Would you be willing to part with them? I am collecting old manuals, and old computing magazines. I even pay for postage, with a bit of warning that they're coming... Rob - 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: Microsoft and Xenix.
Ah, yes, the RT/PC. That brings back some fond memories. My first exposure to Unix was with AIX on the RT. I still have some of those weird-sized RT AIX manuals around somewhere... Wayne John Adams <[EMAIL PROTECTED]> on 06/23/2001 07:49:42 PM To: [EMAIL PROTECTED] cc:(bcc: Wayne Brown/Corporate/Altec) Subject: Re: Microsoft and Xenix. On Saturday 23 June 2001 10:07, Rob Landley wrote: > Here's what I'm looking for: > > AIX was first introduced for the IBM RT/PC in 1986, which came out of the > early RISC research. It was ported to PS/2 and S/370 by SAA, and was > based on unix SVR2. (The book didn't specify whether the original > version or the version ported to SAA was based on SVR2, I'm guessing both > were.) You are partially correct. AIX (Advanced Interactive eXecutive) was built by the Boston office of Interactive Systems under contract to IBM. We had a maximum of 17 people in the effort which shipped on the RT in January 1986. Prior to that time, Interactive Systems had produced a port of System III running on the PC/XT called PC/IX which was sold via IBM. I used PC/IX to produce the software only floating point code in the first version of AIX. johna - 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/ - 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: Microsoft and Xenix.
I have a complete set of the "XENIX System V" manuals and diskettes (User's Guide, User's Reference, Runtime Operating System, and Development System) for the AT Personal Computer 6300. The slipcases have the AT "Death Star" logo on the spines, and the manuals have separate copyrights listed for AT (1985), Microsoft (1983, 1984, 1985), and the Santa Cruz Operation (1984, 1985). I never had a 6300, but I did try booting the install diskette once on a Leading Edge Model D (PC/XT clone) and to my surprise it booted OK. Wayne "Mike Jagdis" <[EMAIL PROTECTED]> on 06/23/2001 12:57:37 PM To: "Alan Chandler" <[EMAIL PROTECTED]>, [EMAIL PROTECTED] cc: "Rob Landley" <[EMAIL PROTECTED]> (bcc: Wayne Brown/Corporate/Altec) Subject: RE: Microsoft and Xenix. > I hope the following adds a more direct perspective on this, as I > was a user at the time. I was _almost_ at university :-). However I do have a first edition of the IBM Xenix Software Development Guide from december 1984. It has '84 IBM copyright and '83 MS copyright. The SCO stuff I have goes back to '83 - MS copyrights on it go back to '81 but that's probably just the compiler and DOS compatibility. Basically Xenix was the first MS/IBM attempt at a "real OS" for the PC. MS realised that multiuser/multitasking was less important than colour graphics for PC owners and decided to pull out of the Xenix business. IBM licensed it under their name to keep their desktop computer concept alive while the Xenix team emerged from the shake out to form SCO. Mike -- Chief Network Architect Mobile:+44 7780 608 368 Kokua Communications Ltd Office: +44 20 7292 1680 52-53 Conduit Street Fax: +44 20 7292 1681 London W1S 2YX - 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/ - 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: Microsoft and Xenix.
I have a complete set of the XENIX System V manuals and diskettes (User's Guide, User's Reference, Runtime Operating System, and Development System) for the ATT Personal Computer 6300. The slipcases have the ATT Death Star logo on the spines, and the manuals have separate copyrights listed for ATT (1985), Microsoft (1983, 1984, 1985), and the Santa Cruz Operation (1984, 1985). I never had a 6300, but I did try booting the install diskette once on a Leading Edge Model D (PC/XT clone) and to my surprise it booted OK. Wayne Mike Jagdis [EMAIL PROTECTED] on 06/23/2001 12:57:37 PM To: Alan Chandler [EMAIL PROTECTED], [EMAIL PROTECTED] cc: Rob Landley [EMAIL PROTECTED] (bcc: Wayne Brown/Corporate/Altec) Subject: RE: Microsoft and Xenix. I hope the following adds a more direct perspective on this, as I was a user at the time. I was _almost_ at university :-). However I do have a first edition of the IBM Xenix Software Development Guide from december 1984. It has '84 IBM copyright and '83 MS copyright. The SCO stuff I have goes back to '83 - MS copyrights on it go back to '81 but that's probably just the compiler and DOS compatibility. Basically Xenix was the first MS/IBM attempt at a real OS for the PC. MS realised that multiuser/multitasking was less important than colour graphics for PC owners and decided to pull out of the Xenix business. IBM licensed it under their name to keep their desktop computer concept alive while the Xenix team emerged from the shake out to form SCO. Mike -- Chief Network Architect Mobile:+44 7780 608 368 Kokua Communications Ltd Office: +44 20 7292 1680 52-53 Conduit Street Fax: +44 20 7292 1681 London W1S 2YX - 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/ - 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: Microsoft and Xenix.
Ah, yes, the RT/PC. That brings back some fond memories. My first exposure to Unix was with AIX on the RT. I still have some of those weird-sized RT AIX manuals around somewhere... Wayne John Adams [EMAIL PROTECTED] on 06/23/2001 07:49:42 PM To: [EMAIL PROTECTED] cc:(bcc: Wayne Brown/Corporate/Altec) Subject: Re: Microsoft and Xenix. On Saturday 23 June 2001 10:07, Rob Landley wrote: Here's what I'm looking for: AIX was first introduced for the IBM RT/PC in 1986, which came out of the early RISC research. It was ported to PS/2 and S/370 by SAA, and was based on unix SVR2. (The book didn't specify whether the original version or the version ported to SAA was based on SVR2, I'm guessing both were.) You are partially correct. AIX (Advanced Interactive eXecutive) was built by the Boston office of Interactive Systems under contract to IBM. We had a maximum of 17 people in the effort which shipped on the RT in January 1986. Prior to that time, Interactive Systems had produced a port of System III running on the PC/XT called PC/IX which was sold via IBM. I used PC/IX to produce the software only floating point code in the first version of AIX. johna - 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/ - 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: The latest Microsoft FUD. This time from BillG, himself.
On 06/20/2001 at 05:33:45 PM Larry McVoy <[EMAIL PROTECTED]> wrote: >You can scream all you want that "it isn't free software" but the fact >of the matter is that you all scream that and then go do your slides for >your Linux talks in PowerPoint. Not I. The slides for my last meeting were done as TIFF files and I used xv to display them. Plus, the most recent documentation I wrote for one of our mainframe applications was done with vi and LaTeX. "What, in addition to the printed copies, you want a copy of the Word document? There is no Word document. But I'll convert it to Rich Text for you and you can take it from there." If my employer didn't require me to use them occasionally, I'd delete every Microsoft product on my laptop. It's not that I have anything against proprietary software. It's just Microsoft that I despise. - 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: The latest Microsoft FUD. This time from BillG, himself.
On 06/20/2001 at 05:33:45 PM Larry McVoy [EMAIL PROTECTED] wrote: You can scream all you want that it isn't free software but the fact of the matter is that you all scream that and then go do your slides for your Linux talks in PowerPoint. Not I. The slides for my last meeting were done as TIFF files and I used xv to display them. Plus, the most recent documentation I wrote for one of our mainframe applications was done with vi and LaTeX. What, in addition to the printed copies, you want a copy of the Word document? There is no Word document. But I'll convert it to Rich Text for you and you can take it from there. If my employer didn't require me to use them occasionally, I'd delete every Microsoft product on my laptop. It's not that I have anything against proprietary software. It's just Microsoft that I despise. - 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 2.4.5-ac7
2.4.5-ac7 fixes the cs46xx problems I had with my ThinkPad 600X in 2.4.5-ac[456]. It works great now. Many thanks to Frank Davis and Alan Cox! Wayne - 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 2.4.5-ac7
2.4.5-ac7 fixes the cs46xx problems I had with my ThinkPad 600X in 2.4.5-ac[456]. It works great now. Many thanks to Frank Davis and Alan Cox! Wayne - 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: Warning in ac6
Sean Jones <[EMAIL PROTECTED]> on 06/02/2001 01:17:15 PM To: Linux Kernel Mailing List <[EMAIL PROTECTED]> cc: (bcc: Wayne Brown/Corporate/Altec) Subject: Warning in ac6 >Also the file /proc/sys/fs/binfmt_misc seems to be missing on my >machine. How would I remedy this problem? To answer one of your questions: /proc/sys/fs/binfmt_misc is a directory, not a file. If you mean that this directory is present but empty, try this: mount -t binfmt_misc none /proc/sys/fs/binfmt_misc and see if the register and status files appear in it. If the directory isn't there at all, make certain you have CONFIG_BINFMT_MISC=y in your .config file. Wayne - 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: Warning in ac6
Sean Jones [EMAIL PROTECTED] on 06/02/2001 01:17:15 PM To: Linux Kernel Mailing List [EMAIL PROTECTED] cc:(bcc: Wayne Brown/Corporate/Altec) Subject: Warning in ac6 Also the file /proc/sys/fs/binfmt_misc seems to be missing on my machine. How would I remedy this problem? To answer one of your questions: /proc/sys/fs/binfmt_misc is a directory, not a file. If you mean that this directory is present but empty, try this: mount -t binfmt_misc none /proc/sys/fs/binfmt_misc and see if the register and status files appear in it. If the directory isn't there at all, make certain you have CONFIG_BINFMT_MISC=y in your .config file. Wayne - 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 2.4.5-ac6
The oops problem with the cs46xx in my ThinkPad 600X under -ac4 and -ac5 has
changed now. It no longer gives an oops; instead the program trying to access
the sound card hangs (until I kill it). Subsequent attempts to access the sound
card get a "Device or resource busy" error. There are no messages on the screen
or sent to syslog (or messages or debug) when the hang occurs. I don't know if
it will help or not, but here are the last few lines of an strace of the hanging
process:
stat("/usr/bin/sox", {st_mode=S_IFREG|0755, st_size=120744, ...}) = 0
rt_sigprocmask(SIG_BLOCK, ~[], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [INT CHLD], [], 8) = 0
fork() = 186
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigaction(SIGINT, {0x806c04c, [], 0x400}, {SIG_DFL}, 8) = 0
wait4(-1, 0xb744, 0, NULL) = ? ERESTARTSYS (To be restarted)
--- SIGTERM (Terminated) ---
+++ killed by SIGTERM +++
At the point of the hang, the output stops at "wait4(-1, " and the rest of that
line (and the next two lines) appears after I kill the process.
Here are the last few lines of another strace of the same program under
2.4.5-ac3, which works fine:
stat("/usr/bin/sox", {st_mode=S_IFREG|0755, st_size=120744, ...}) = 0
rt_sigprocmask(SIG_BLOCK, ~[], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [INT CHLD], [], 8) = 0
fork() = 435
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigaction(SIGINT, {0x806c04c, [], 0x400}, {SIG_DFL}, 8) = 0
wait4(-1, [WIFEXITED(s) && WEXITSTATUS(s) == 0], 0, NULL) = 435
rt_sigprocmask(SIG_BLOCK, [CHLD TTOU], [CHLD], 8) = 0
rt_sigprocmask(SIG_SETMASK, [CHLD], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [CHLD], 8) = 0
rt_sigprocmask(SIG_SETMASK, [CHLD], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
--- SIGCHLD (Child exited) ---
wait4(-1, 0xb438, WNOHANG, NULL)= -1 ECHILD (No child processes)
sigreturn() = ? (mask now [])
rt_sigaction(SIGINT, {SIG_DFL}, {0x806c04c, [], 0x400}, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD TTOU], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
read(255, "", 4472) = 0
_exit(0)= ?h
-
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 2.4.5-ac6
The oops problem with the cs46xx in my ThinkPad 600X under -ac4 and -ac5 has
changed now. It no longer gives an oops; instead the program trying to access
the sound card hangs (until I kill it). Subsequent attempts to access the sound
card get a Device or resource busy error. There are no messages on the screen
or sent to syslog (or messages or debug) when the hang occurs. I don't know if
it will help or not, but here are the last few lines of an strace of the hanging
process:
stat(/usr/bin/sox, {st_mode=S_IFREG|0755, st_size=120744, ...}) = 0
rt_sigprocmask(SIG_BLOCK, ~[], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [INT CHLD], [], 8) = 0
fork() = 186
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigaction(SIGINT, {0x806c04c, [], 0x400}, {SIG_DFL}, 8) = 0
wait4(-1, 0xb744, 0, NULL) = ? ERESTARTSYS (To be restarted)
--- SIGTERM (Terminated) ---
+++ killed by SIGTERM +++
At the point of the hang, the output stops at wait4(-1, and the rest of that
line (and the next two lines) appears after I kill the process.
Here are the last few lines of another strace of the same program under
2.4.5-ac3, which works fine:
stat(/usr/bin/sox, {st_mode=S_IFREG|0755, st_size=120744, ...}) = 0
rt_sigprocmask(SIG_BLOCK, ~[], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [INT CHLD], [], 8) = 0
fork() = 435
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigaction(SIGINT, {0x806c04c, [], 0x400}, {SIG_DFL}, 8) = 0
wait4(-1, [WIFEXITED(s) WEXITSTATUS(s) == 0], 0, NULL) = 435
rt_sigprocmask(SIG_BLOCK, [CHLD TTOU], [CHLD], 8) = 0
rt_sigprocmask(SIG_SETMASK, [CHLD], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [CHLD], 8) = 0
rt_sigprocmask(SIG_SETMASK, [CHLD], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
--- SIGCHLD (Child exited) ---
wait4(-1, 0xb438, WNOHANG, NULL)= -1 ECHILD (No child processes)
sigreturn() = ? (mask now [])
rt_sigaction(SIGINT, {SIG_DFL}, {0x806c04c, [], 0x400}, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD TTOU], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
read(255, , 4472) = 0
_exit(0)= ?h
-
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: cs46xx oops in 2.4.5-ac4
This problem is still present in 2.4.5-ac5. Here's the latest oops: ksymoops 2.4.1 on i686 2.4.5-ac5. Options used -v /usr/src/linux-2.4.5-ac5/vmlinux (specified) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.5-ac5/ (default) -m /usr/src/linux/System.map (default) Unable to handle kernel NULL pointer dereference at virtual address *pde = Oops: 0002 CPU:0 EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010086 eax: cfa78e84 ebx: ecx: 0286 edx: cc961f2c esi: cc961f24 edi: cfa78e80 ebp: cc961f24 esp: cc961f08 ds: 0018 es: 0018 ss: 0018 Process sox (pid: 195, stackpage=cc961000) Stack: cfa78e78 cc96 c0105938 ffea cc9ce560 1000 cfa78df0 0001 cc96 cfa78e84 c0105aa8 cfa78e78 cfa78dc0 cc9ce580 d0c676b4 ffea cc9ce560 1000 b830 cfa78df0 c0267c40 Call Trace: [] [] [] [] [] [] Code: 89 13 51 9d 5b 5e c3 90 9c 58 fa 8b 4a 0c 8b 52 08 89 4a 04 >>EIP; c0111f54<= Trace; c0105938 <__down+4c/a8> Trace; c0105aa8 <__down_failed+8/c> Trace; d0c676b4 <[cs46xx].text.end+74/1e0> Trace; c0119baa Trace; c012dd86 Trace; c0106b27 Code; c0111f54 <_EIP>: Code; c0111f54<= 0: 89 13 mov%edx,(%ebx) <= Code; c0111f56 2: 51push %ecx Code; c0111f57 3: 9dpopf Code; c0111f58 4: 5bpop%ebx Code; c0111f59 5: 5epop%esi Code; c0111f5a 6: c3ret Code; c0111f5b 7: 90nop Code; c0111f5c 8: 9cpushf Code; c0111f5d 9: 58pop%eax Code; c0111f5e a: facli Code; c0111f5f b: 8b 4a 0c mov0xc(%edx),%ecx Code; c0111f62 e: 8b 52 08 mov0x8(%edx),%edx Code; c0111f65 11: 89 4a 04 mov%ecx,0x4(%edx) - 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/
cs46xx oops in 2.4.5-ac4
Since upgrading to 2.4.5-ac4 the Crystal Soundfusion card in my Thinkpad 600X has stopped working. Trying to play an audio file (with /usr/bin/play from sox 12.16) gives me an oops. Here is the init stuff from dmesg for the sound card: Crystal 4280/46xx + AC97 Audio, version 1.27.32, 13:05:58 May 29 2001 cs46xx: Card found at 0x5010 and 0x5000, IRQ 11 cs46xx: Thinkpad 600X/A20/T20 (1014:0153) at 0x5010/0x5000, IRQ 11 ac97_codec: AC97 Audio codec, id: 0x4352:0x5913 (Cirrus Logic CS4297A rev A) And here is the oops info from ksymoops (apologies if my email program wraps any lines; I intend to start using a decent mail program Real Soon Now): ksymoops 2.4.1 on i686 2.4.5-ac4. Options used -v /usr/src/linux-2.4.5-ac4/vmlinux (specified) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.5-ac4/ (default) -m /usr/src/linux/System.map (default) Unable to handle kernel NULL pointer dereference at virtual address *pde = Oops: 0002 CPU:0 EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010086 eax: ccf7d884 ebx: ecx: 0286 edx: cca43f2c esi: cca43f24 edi: ccf7d880 ebp: cca43f24 esp: cca43f08 ds: 0018 es: 0018 ss: 0018 Process sox (pid: 186, stackpage=cca43000) Stack: ccf7d878 cca42000 c0105938 ffea cdcf7a20 1000 ccf7d7f0 0001 cca42000 ccf7d884 c0105aa8 ccf7d878 ccf7d7c0 cdcf7a40 d0c75678 ffea cdcf7a20 1000 b870 ccf7d7f0 0001 0018 Call Trace: [] [] [] [] [] [] Code: 89 13 51 9d 5b 5e c3 90 9c 58 fa 8b 4a 0c 8b 52 08 89 4a 04 >>EIP; c0111f34<= Trace; c0105938 <__down+4c/a8> Trace; c0105aa8 <__down_failed+8/c> Trace; d0c75678 <[cs46xx].text.end+74/1dc> Trace; c01225cb Trace; c012dd66 Trace; c0106b27 Code; c0111f34 <_EIP>: Code; c0111f34<= 0: 89 13 mov%edx,(%ebx) <= Code; c0111f36 2: 51push %ecx Code; c0111f37 3: 9dpopf Code; c0111f38 4: 5bpop%ebx Code; c0111f39 5: 5epop%esi Code; c0111f3a 6: c3ret Code; c0111f3b 7: 90nop Code; c0111f3c 8: 9cpushf Code; c0111f3d 9: 58pop%eax Code; c0111f3e a: facli Code; c0111f3f b: 8b 4a 0c mov0xc(%edx),%ecx Code; c0111f42 e: 8b 52 08 mov0x8(%edx),%edx Code; c0111f45 11: 89 4a 04 mov%ecx,0x4(%edx) - 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/
cs46xx oops in 2.4.5-ac4
Since upgrading to 2.4.5-ac4 the Crystal Soundfusion card in my Thinkpad 600X has stopped working. Trying to play an audio file (with /usr/bin/play from sox 12.16) gives me an oops. Here is the init stuff from dmesg for the sound card: Crystal 4280/46xx + AC97 Audio, version 1.27.32, 13:05:58 May 29 2001 cs46xx: Card found at 0x5010 and 0x5000, IRQ 11 cs46xx: Thinkpad 600X/A20/T20 (1014:0153) at 0x5010/0x5000, IRQ 11 ac97_codec: AC97 Audio codec, id: 0x4352:0x5913 (Cirrus Logic CS4297A rev A) And here is the oops info from ksymoops (apologies if my email program wraps any lines; I intend to start using a decent mail program Real Soon Now): ksymoops 2.4.1 on i686 2.4.5-ac4. Options used -v /usr/src/linux-2.4.5-ac4/vmlinux (specified) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.5-ac4/ (default) -m /usr/src/linux/System.map (default) Unable to handle kernel NULL pointer dereference at virtual address *pde = Oops: 0002 CPU:0 EIP:0010:[c0111f34] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010086 eax: ccf7d884 ebx: ecx: 0286 edx: cca43f2c esi: cca43f24 edi: ccf7d880 ebp: cca43f24 esp: cca43f08 ds: 0018 es: 0018 ss: 0018 Process sox (pid: 186, stackpage=cca43000) Stack: ccf7d878 cca42000 c0105938 ffea cdcf7a20 1000 ccf7d7f0 0001 cca42000 ccf7d884 c0105aa8 ccf7d878 ccf7d7c0 cdcf7a40 d0c75678 ffea cdcf7a20 1000 b870 ccf7d7f0 0001 0018 Call Trace: [c0105938] [c0105aa8] [d0c75678] [c01225cb] [c012dd66] [c0106b27] Code: 89 13 51 9d 5b 5e c3 90 9c 58 fa 8b 4a 0c 8b 52 08 89 4a 04 EIP; c0111f34 add_wait_queue_exclusive+1c/24 = Trace; c0105938 __down+4c/a8 Trace; c0105aa8 __down_failed+8/c Trace; d0c75678 [cs46xx].text.end+74/1dc Trace; c01225cb generic_file_read+63/80 Trace; c012dd66 sys_write+8e/c4 Trace; c0106b27 system_call+33/38 Code; c0111f34 add_wait_queue_exclusive+1c/24 _EIP: Code; c0111f34 add_wait_queue_exclusive+1c/24 = 0: 89 13 mov%edx,(%ebx) = Code; c0111f36 add_wait_queue_exclusive+1e/24 2: 51push %ecx Code; c0111f37 add_wait_queue_exclusive+1f/24 3: 9dpopf Code; c0111f38 add_wait_queue_exclusive+20/24 4: 5bpop%ebx Code; c0111f39 add_wait_queue_exclusive+21/24 5: 5epop%esi Code; c0111f3a add_wait_queue_exclusive+22/24 6: c3ret Code; c0111f3b add_wait_queue_exclusive+23/24 7: 90nop Code; c0111f3c remove_wait_queue+0/14 8: 9cpushf Code; c0111f3d remove_wait_queue+1/14 9: 58pop%eax Code; c0111f3e remove_wait_queue+2/14 a: facli Code; c0111f3f remove_wait_queue+3/14 b: 8b 4a 0c mov0xc(%edx),%ecx Code; c0111f42 remove_wait_queue+6/14 e: 8b 52 08 mov0x8(%edx),%edx Code; c0111f45 remove_wait_queue+9/14 11: 89 4a 04 mov%ecx,0x4(%edx) - 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: cs46xx oops in 2.4.5-ac4
This problem is still present in 2.4.5-ac5. Here's the latest oops: ksymoops 2.4.1 on i686 2.4.5-ac5. Options used -v /usr/src/linux-2.4.5-ac5/vmlinux (specified) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.5-ac5/ (default) -m /usr/src/linux/System.map (default) Unable to handle kernel NULL pointer dereference at virtual address *pde = Oops: 0002 CPU:0 EIP:0010:[c0111f54] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010086 eax: cfa78e84 ebx: ecx: 0286 edx: cc961f2c esi: cc961f24 edi: cfa78e80 ebp: cc961f24 esp: cc961f08 ds: 0018 es: 0018 ss: 0018 Process sox (pid: 195, stackpage=cc961000) Stack: cfa78e78 cc96 c0105938 ffea cc9ce560 1000 cfa78df0 0001 cc96 cfa78e84 c0105aa8 cfa78e78 cfa78dc0 cc9ce580 d0c676b4 ffea cc9ce560 1000 b830 cfa78df0 c0267c40 Call Trace: [c0105938] [c0105aa8] [d0c676b4] [c0119baa] [c012dd86] [c0106b27] Code: 89 13 51 9d 5b 5e c3 90 9c 58 fa 8b 4a 0c 8b 52 08 89 4a 04 EIP; c0111f54 add_wait_queue_exclusive+1c/24 = Trace; c0105938 __down+4c/a8 Trace; c0105aa8 __down_failed+8/c Trace; d0c676b4 [cs46xx].text.end+74/1e0 Trace; c0119baa tqueue_bh+16/1c Trace; c012dd86 sys_write+8e/c4 Trace; c0106b27 system_call+33/38 Code; c0111f54 add_wait_queue_exclusive+1c/24 _EIP: Code; c0111f54 add_wait_queue_exclusive+1c/24 = 0: 89 13 mov%edx,(%ebx) = Code; c0111f56 add_wait_queue_exclusive+1e/24 2: 51push %ecx Code; c0111f57 add_wait_queue_exclusive+1f/24 3: 9dpopf Code; c0111f58 add_wait_queue_exclusive+20/24 4: 5bpop%ebx Code; c0111f59 add_wait_queue_exclusive+21/24 5: 5epop%esi Code; c0111f5a add_wait_queue_exclusive+22/24 6: c3ret Code; c0111f5b add_wait_queue_exclusive+23/24 7: 90nop Code; c0111f5c remove_wait_queue+0/14 8: 9cpushf Code; c0111f5d remove_wait_queue+1/14 9: 58pop%eax Code; c0111f5e remove_wait_queue+2/14 a: facli Code; c0111f5f remove_wait_queue+3/14 b: 8b 4a 0c mov0xc(%edx),%ecx Code; c0111f62 remove_wait_queue+6/14 e: 8b 52 08 mov0x8(%edx),%edx Code; c0111f65 remove_wait_queue+9/14 11: 89 4a 04 mov%ecx,0x4(%edx) - 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: The difference between Linus's kernel and Alan Cox's kernel
It really ought to be Linus and/or Alan who answers this, but from my own observations, here's the way I think it goes: Alan and Linus don't always agree on what should be in the kernel; and even when they do, they sometimes disagree on when something is ready to be included. Alan may think a particular set of patches are ready, while Linus thinks they need to mature a bit more; or perhaps he thinks the whole approach is wrong and should be scrapped. So Alan puts it in his kernel, and Linus leaves it out of his. (Of course, sometimes it's Linus who adds something that Alan rejects.) It sometimes happens that one of these new ideas turns out better than expected (especially after going through a few bug report/new patch cycles), and the person who rejected it changes his mind and includes it later; or maybe it doesn't work out and gets dropped altogether. Also, as you've already observed, Alan regularly resyncs major parts of his tree with Linus' so they don't get too far apart, and Linus occasionally does the same. It used to bother me, too, to have to keep up with two different kernel trees. But I've come to realize that this is a Good Thing. It provides a way for people with different viewpoints to approach an idea from more than one direction. If the two kernels are trying to solve a particular problem in different ways, we get to see how each approach works in the real world, rather than just in a theoretical discussion. If the two kernels branch too far apart it could be a problem, but Linus and Alan have been diligent about keeping that from happening. I think the interplay (is "competition" too strong a word?) between the two branches has helped make the "official" kernel better than it might have been otherwise. Wayne - 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: The difference between Linus's kernel and Alan Cox's kernel
It really ought to be Linus and/or Alan who answers this, but from my own observations, here's the way I think it goes: Alan and Linus don't always agree on what should be in the kernel; and even when they do, they sometimes disagree on when something is ready to be included. Alan may think a particular set of patches are ready, while Linus thinks they need to mature a bit more; or perhaps he thinks the whole approach is wrong and should be scrapped. So Alan puts it in his kernel, and Linus leaves it out of his. (Of course, sometimes it's Linus who adds something that Alan rejects.) It sometimes happens that one of these new ideas turns out better than expected (especially after going through a few bug report/new patch cycles), and the person who rejected it changes his mind and includes it later; or maybe it doesn't work out and gets dropped altogether. Also, as you've already observed, Alan regularly resyncs major parts of his tree with Linus' so they don't get too far apart, and Linus occasionally does the same. It used to bother me, too, to have to keep up with two different kernel trees. But I've come to realize that this is a Good Thing. It provides a way for people with different viewpoints to approach an idea from more than one direction. If the two kernels are trying to solve a particular problem in different ways, we get to see how each approach works in the real world, rather than just in a theoretical discussion. If the two kernels branch too far apart it could be a problem, but Linus and Alan have been diligent about keeping that from happening. I think the interplay (is competition too strong a word?) between the two branches has helped make the official kernel better than it might have been otherwise. Wayne - 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] struct char_device
[EMAIL PROTECTED] on 05/23/2001 08:34:44 AM To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] cc:(bcc: Wayne Brown/Corporate/Altec) Subject: Re: [PATCH] struct char_device >> But I don't want an initrd. > >Don't be afraid of words. You wouldnt notice - it would do its >job and disappear just like piggyback today. So nothing in the boot scripts would have to change? (Not that it would be a big problem if it was necessary. However, I prefer to keep things in /etc/rc.d as close to the distribution defaults as possible, just in case I ever need to reinstall the distribution.) Wayne - 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] struct char_device
[EMAIL PROTECTED] on 05/23/2001 08:34:44 AM To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] cc:(bcc: Wayne Brown/Corporate/Altec) Subject: Re: [PATCH] struct char_device But I don't want an initrd. Don't be afraid of words. You wouldnt notice - it would do its job and disappear just like piggyback today. So nothing in the boot scripts would have to change? (Not that it would be a big problem if it was necessary. However, I prefer to keep things in /etc/rc.d as close to the distribution defaults as possible, just in case I ever need to reinstall the distribution.) Wayne - 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: Background to the argument about CML2 design philosophy
On 05/21/2001 at 12:58:57 [EMAIL PROTECTED] wrote: >CML2 drops its configuration results in the same place, in the same >formats, as CML1. So you should in fact be able to type `make menuconfig' >and `make oldconfig' with good results. Have you actually tried this? No, I haven't tried it yet. I usually wait for things like this to be included in Linus' or Alan's kernels before trying them. In this case, I might have tried it by now but I only have Python 1.5.2 on my system and don't want to upgrade it until/unless it's absolutely necessary. So I probably won't see CML2 until Linus puts it in 2.5. My comments have been based on your descriptions of it on lkml. Wayne - 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: Background to the argument about CML2 design philosophy
On 05/21/2001 at 05:04:40 AM [EMAIL PROTECTED] wrote: >See, I've already written off the chronic bellyachers. Since I can't >please them without scrapping the whole plan, I'm going to ignore >them. In particular, anybody who repeated "fsck Python..." after Linus >ruled that Python is not an issue and Greg Banks announced the C >implementation of CML2 has got a sufficiently severe case of >rectocranial insertion that they've defined themselves out of the >conversation. I probably qualify as one of the bellyachers. If so, I apologize. It was not my intention to disparage the work of Eric or anyone else involved in this project. Speaking from the perspective of a user of the CML tools, rather than as a developer, all I've been trying to say is this: When I type "make menuconfig" or "make oldconfig" in the future, I want to see the same interface and the same results that I've always seen, because it's always worked for me in the past. It really doesn't matter to me if, down underneath, this is being done by CML1, CML2, or a little man in my computer who slaughters chickens and reads their entrails for omens to determine dependencies. Right now I can grab a new -pre or -ac patch, use oldconfig, and have a compile going in a few minutes, without knowing or caring about the details of the config process. In the rare case that a patch breaks an existing driver, it takes only a couple of minutes with menuconfig to disable that driver and compile without it, and then put it back in when it's fixed. And when, every once in a great while, I decide to scrap my .config and start over, I can fly through all the menuconfig options very quickly and make my customary selections almost without thinking about it. I just want to be able to keep using the tools in this way. If that's not going to be possible... well, I'll adapt. But from my point of view, learning a new set of tools just to keep doing the same things I've always done isn't a pleasant prospect. I understand that changes may be necessary to meet others' needs, but I'd like to see those changes made without affecting the way my own needs are met. I'm off my soapbox now and won't bellyache about it any further. Wayne - 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: Background to the argument about CML2 design philosophy
On 05/21/2001 at 05:04:40 AM [EMAIL PROTECTED] wrote: See, I've already written off the chronic bellyachers. Since I can't please them without scrapping the whole plan, I'm going to ignore them. In particular, anybody who repeated fsck Python... after Linus ruled that Python is not an issue and Greg Banks announced the C implementation of CML2 has got a sufficiently severe case of rectocranial insertion that they've defined themselves out of the conversation. I probably qualify as one of the bellyachers. If so, I apologize. It was not my intention to disparage the work of Eric or anyone else involved in this project. Speaking from the perspective of a user of the CML tools, rather than as a developer, all I've been trying to say is this: When I type make menuconfig or make oldconfig in the future, I want to see the same interface and the same results that I've always seen, because it's always worked for me in the past. It really doesn't matter to me if, down underneath, this is being done by CML1, CML2, or a little man in my computer who slaughters chickens and reads their entrails for omens to determine dependencies. Right now I can grab a new -pre or -ac patch, use oldconfig, and have a compile going in a few minutes, without knowing or caring about the details of the config process. In the rare case that a patch breaks an existing driver, it takes only a couple of minutes with menuconfig to disable that driver and compile without it, and then put it back in when it's fixed. And when, every once in a great while, I decide to scrap my .config and start over, I can fly through all the menuconfig options very quickly and make my customary selections almost without thinking about it. I just want to be able to keep using the tools in this way. If that's not going to be possible... well, I'll adapt. But from my point of view, learning a new set of tools just to keep doing the same things I've always done isn't a pleasant prospect. I understand that changes may be necessary to meet others' needs, but I'd like to see those changes made without affecting the way my own needs are met. I'm off my soapbox now and won't bellyache about it any further. Wayne - 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: Background to the argument about CML2 design philosophy
On 05/21/2001 at 12:58:57 [EMAIL PROTECTED] wrote: CML2 drops its configuration results in the same place, in the same formats, as CML1. So you should in fact be able to type `make menuconfig' and `make oldconfig' with good results. Have you actually tried this? No, I haven't tried it yet. I usually wait for things like this to be included in Linus' or Alan's kernels before trying them. In this case, I might have tried it by now but I only have Python 1.5.2 on my system and don't want to upgrade it until/unless it's absolutely necessary. So I probably won't see CML2 until Linus puts it in 2.5. My comments have been based on your descriptions of it on lkml. Wayne - 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: [kbuild-devel] Re: CML2 design philosophy heads-up
On 05/18/2001 at 03:56:50 PM Mike Castle <[EMAIL PROTECTED]> wrote: >On Fri, May 18, 2001 at 03:04:43PM -0500, [EMAIL PROTECTED] wrote: >> 1. Some of us are perfectly satisfied with the existing tools and don't want >> them to be yanked out from under us. > >Then stay with 2.4.x > Since doing kernel upgrades is my whole reason for using the tools, that's not a very helpful suggestion. It's a little like saying, "If you don't like the way the air smells, just stop breathing." >> 2. Some of us have no interest in Python and don't like being forced to deal >> with installing/upgrading it just for CML2. > > >Some don't like installing/upgrading the following just for a kernel: > >gcc >binutils >modutils >mount >Not to mention netfilter. I don't especially like upgrading these things, either, and don't do it unless I absolutely have to (that's why I'm still on egcs-2.91.66), but the kernel is important enough to be worth the trouble. If I have to use CML2 to move into 2.5.x, then I will. However, upgrading a programming language I don't use, just so I can replace a perfectly good tool with one I don't want, in order to do a job that's always been easy to accomplish with the existing tools... well, that seems a lot like a solution in search of a problem. Fortunately, Alan's response about someone re-writing CML2 in C offers hope for at least part of the issue. Wayne - 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: [kbuild-devel] Re: CML2 design philosophy heads-up
On 05/18/2001 at 11:45:40 AM [EMAIL PROTECTED] wrote: >I hereby volunteer to maintain at least make oldconfig and make config, >and perhaps make menuconfig. THANK YOU THANK YOU THANK YOU!!! I'm quite happy with the current form of oldconfig and menuconfig, and will continue to use them as long as they're available. Wayne - 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: [kbuild-devel] Re: CML2 design philosophy heads-up
On 05/18/2001 at 11:45:40 AM [EMAIL PROTECTED] wrote: I hereby volunteer to maintain at least make oldconfig and make config, and perhaps make menuconfig. THANK YOU THANK YOU THANK YOU!!! I'm quite happy with the current form of oldconfig and menuconfig, and will continue to use them as long as they're available. Wayne - 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: [kbuild-devel] Re: CML2 design philosophy heads-up
On 05/18/2001 at 03:56:50 PM Mike Castle [EMAIL PROTECTED] wrote: On Fri, May 18, 2001 at 03:04:43PM -0500, [EMAIL PROTECTED] wrote: 1. Some of us are perfectly satisfied with the existing tools and don't want them to be yanked out from under us. Then stay with 2.4.x Since doing kernel upgrades is my whole reason for using the tools, that's not a very helpful suggestion. It's a little like saying, If you don't like the way the air smells, just stop breathing. 2. Some of us have no interest in Python and don't like being forced to deal with installing/upgrading it just for CML2. Some don't like installing/upgrading the following just for a kernel: gcc binutils modutils mount Not to mention netfilter. I don't especially like upgrading these things, either, and don't do it unless I absolutely have to (that's why I'm still on egcs-2.91.66), but the kernel is important enough to be worth the trouble. If I have to use CML2 to move into 2.5.x, then I will. However, upgrading a programming language I don't use, just so I can replace a perfectly good tool with one I don't want, in order to do a job that's always been easy to accomplish with the existing tools... well, that seems a lot like a solution in search of a problem. Fortunately, Alan's response about someone re-writing CML2 in C offers hope for at least part of the issue. Wayne - 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: Not a typewriter
On 05/13/2001 at 08:03:30 PM Horst von Brand <[EMAIL PROTECTED]> wrote: >The old C compiler/old Unix linker guaranteed 6 chars in an external symbol >name only, and C functions got an underscore prepended: _creat. I guess >this is the reason for this wart. As to why 6 chars only, I'd guess some >data structure in the linker was laid out that way. Machines had a few >dozen Kbs of RAM then, space was precious. I've always thought it was just an arbitrary decision, based on the general Unix custom of shortnening names by removing vowels, especially since Ken Thompson later said he'd spell it "create" if he had it to do over again. But your explanation sounds more likely. I really should have thought of this, since I used to run into problems with non-unique names under the Minix linker (which, IIRC, had the same 6 char limit). - 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: Not a typewriter
On 05/13/2001 at 08:03:30 PM Horst von Brand [EMAIL PROTECTED] wrote: The old C compiler/old Unix linker guaranteed 6 chars in an external symbol name only, and C functions got an underscore prepended: _creat. I guess this is the reason for this wart. As to why 6 chars only, I'd guess some data structure in the linker was laid out that way. Machines had a few dozen Kbs of RAM then, space was precious. I've always thought it was just an arbitrary decision, based on the general Unix custom of shortnening names by removing vowels, especially since Ken Thompson later said he'd spell it create if he had it to do over again. But your explanation sounds more likely. I really should have thought of this, since I used to run into problems with non-unique names under the Minix linker (which, IIRC, had the same 6 char limit). - 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: Not a typewriter
On 05/11/2001 at 04:43:13 PM Hacksaw <[EMAIL PROTECTED]> wrote: >Well, I can't disagree. Unix's biggest turn off was the stupid command names. >It's a big reason why Unixoid systems aren't more commonplace. I only learned >it because I was stuck at a desk with a Wyse terminal. Otherwise I probably >would have played with the Autocad machines more. Once I understood the >basics, I understood the power of the system. My first exposure to Unix came in 1987 when I was assigned to write a datacomm package in C on a Unix (AIX) workstation the company had just bought. I was the only one in our shop who knew C, and no one else there had ever dealt with Unix either. (I had heard of Unix, but didn't know anything about it.) My training consisted of my boss handing me the manuals and saying, "Figure it out." For the first two weeks I absolutely HATED that system; nothing made sense, vi seemed insane, and I was stumbling blindly through the documentation (I'd never seen a permuted index before). Then suddenly something clicked, it all started to make sense, and I fell in love with it. That's why I think it's so important for people to learn the Unix mindset before trying to deal with Unix systems. It's also why I have so little patience with people who don't have the patience to work through the learning curve. >But first we need a better help system. The absolute most stupid convention of >Unix is the man command. The fact that SCCS before, and now Bash usurp the >keyword "help" is beyond the pale. I guess we'll just have to agree to disagree, because we have exactly opposite opinions on all this. I love the short, cryptic command names, and I think man is the best help system ever devised. (The GNU Info system, however, is the spawn of Satan. :-) In case you haven't guessed, I love vi, too, and use it whenever possible. If Unix (or Linux) ever gets to the point of losing things like this, I'll have no desire to use it. Wayne - 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 2.4.4-ac8 now with added correct EXTRAVERSION
This fixed the problem with unresolved symbols in nfs.o. Wayne - 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 2.4.4-ac7
My modules/filemap.ver has the same in it as yours. Wayne Alan Cox <[EMAIL PROTECTED]> on 05/11/2001 01:52:18 PM To: Wayne Brown/Corporate/Altec@Altec cc: [EMAIL PROTECTED] (Alan Cox), [EMAIL PROTECTED] (Marek P tlicki), [EMAIL PROTECTED] Subject: Re: Linux 2.4.4-ac7 > I always make mrproper after applying your patches, and I still got exactly the > same problem with nfs that Marek found. There were no errors or warnings during > the compile of the objects in the fs/nfs directory or the linking of nfs.o. > Curious : my build has #define __ver_filemap_fdatasyncf18ce7a1 #define filemap_fdatasync _set_ver(filemap_fdatasync) #define __ver_filemap_fdatawaitd4250148 #define filemap_fdatawait _set_ver(filemap_fdatawait) in modules/filemap.ver I'll have a look
Re: Linux 2.4.4-ac7
I always make mrproper after applying your patches, and I still got exactly the same problem with nfs that Marek found. There were no errors or warnings during the compile of the objects in the fs/nfs directory or the linking of nfs.o. Wayne Alan Cox <[EMAIL PROTECTED]> on 05/11/2001 12:53:03 PM To: [EMAIL PROTECTED] (Marek P tlicki) cc: [EMAIL PROTECTED] (Alan Cox), [EMAIL PROTECTED] (bcc: Wayne Brown/Corporate/Altec) Subject: Re: Linux 2.4.4-ac7 > is the EXTRAVERSION set properly in Makefile? I use the http://www.bzim= > age.org > intermediate diff (chosen ~40K to ~2M) from ac6 nd I still have > 2.4.4-ac6 login prompt (and Makefile says: EXTRAVERSION =3D -ac6). I forgot to change it > The other thing I noticed is: > /lib/modules/2.4.4-ac6/kernel/fs/nfs/nfs.o: unresolved symbol filemap_f= > datawait_Rd4250148 > /lib/modules/2.4.4-ac6/kernel/fs/nfs/nfs.o: unresolved symbol filemap_f= > datasync_Rf18ce7a1 cp .config ..; make mrproper; cp ../.config .config I suspect its an unclean build and the exports didnt get done right. At least I think I fixed these right 8) - 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: Not a typewriter
On 05/11/2001 at 12:03:43 PM Joel Jaeggli <[EMAIL PROTECTED]> wrote: >it's not clear to me that that textsearch is a more accurate description >than Get Regular ExPression It's not more accurate. But Hacksaw's original point was that a new user would not know what "not a typewriter" meant. My point was that a newbie wouldn't be likely to guess that "grep" means "search for text" either; in both cases he'd have to look it up if he'd never seen it before. BTW, grep does not stand for "Get Regular ExPression." It comes from an often-used command in the ed (and ex and vi) editor: g/re/p. The "g" means "global," the "re" is a regular expression, and the "p" means "print." So to search for all lines containing the word "foo" in a file you were editing, you would type g/foo/p. This was such a useful function that it was packaged in a standalone program that could be used to search multiple files. Wayne - 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: Not a typewriter
On 05/10/2001 at 06:20:34 PM Hacksaw <[EMAIL PROTECTED]> wrote: >Heaven help us when tradition is more important than clarity. > If clarity is the most important consideration, then other things should be changed as well. For instance, the command we use to search for text strings in files should be called "textsearch." That's a lot more clear than "grep." >Typewriter has always been wrong. I'd agree that "Not a teletypewriter" would >suffice. > But the original message said "typewriter." (The "wrongness" is part of its charm.) If the wording is going to be changed, then it's better to abandon the tradition altogether and use one of the more descriptive and "correct" messages you and others have proposed. >On the other hand "Inappropriate ioctl for device" is also not very clear. > >I'd like to see "Not a serial or character device" or "Not a serial device" if >that's more appropriate. Something like that... My point is that someone who sees the "typewriter" message and doesn't understand it will have to dig a bit to find out what it means. Finding it almost certainly will involve uncovering some of the history and folklore of Unix. In the "Intro to Unix" classes I've taught over the years, I've always made a point of explaining the background of things like this -- such as the relation of grep to the g/re/p expression of ed, ex and vi; where biff got its name; what the letters stand for in awk; why creat doesn't end in an "e;" and so forth. I tell the class that Unix has quirky, eccentric, whimsical elements because many of the things in it were written by quirky, eccentric, or whimsical people. The comment at the bottom of some versions of the tunefs man page (such as the HP-UX version) is an example I like to use: "You can tune a file system, but you can't tune a fish." I tell them they'll understand the Unix way of thinking faster if they approach it with an inquisitive, playful spirit rather than as a stuffy business system. It's supposed to be correct; it's supposed to be efficient; but it's also supposed to be fun, and sometimes the fun is worth sacrificing a little of the other qualities in trivial areas. I guess what I'm trying to say is that "Life With Unix" should be required reading for anyone who goes near a Unix (or Linux) system. Wayne - 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: Not a typewriter
On 05/10/2001 at 06:20:34 PM Hacksaw [EMAIL PROTECTED] wrote: Heaven help us when tradition is more important than clarity. If clarity is the most important consideration, then other things should be changed as well. For instance, the command we use to search for text strings in files should be called textsearch. That's a lot more clear than grep. Typewriter has always been wrong. I'd agree that Not a teletypewriter would suffice. But the original message said typewriter. (The wrongness is part of its charm.) If the wording is going to be changed, then it's better to abandon the tradition altogether and use one of the more descriptive and correct messages you and others have proposed. On the other hand Inappropriate ioctl for device is also not very clear. I'd like to see Not a serial or character device or Not a serial device if that's more appropriate. Something like that... My point is that someone who sees the typewriter message and doesn't understand it will have to dig a bit to find out what it means. Finding it almost certainly will involve uncovering some of the history and folklore of Unix. In the Intro to Unix classes I've taught over the years, I've always made a point of explaining the background of things like this -- such as the relation of grep to the g/re/p expression of ed, ex and vi; where biff got its name; what the letters stand for in awk; why creat doesn't end in an e; and so forth. I tell the class that Unix has quirky, eccentric, whimsical elements because many of the things in it were written by quirky, eccentric, or whimsical people. The comment at the bottom of some versions of the tunefs man page (such as the HP-UX version) is an example I like to use: You can tune a file system, but you can't tune a fish. I tell them they'll understand the Unix way of thinking faster if they approach it with an inquisitive, playful spirit rather than as a stuffy business system. It's supposed to be correct; it's supposed to be efficient; but it's also supposed to be fun, and sometimes the fun is worth sacrificing a little of the other qualities in trivial areas. I guess what I'm trying to say is that Life With Unix should be required reading for anyone who goes near a Unix (or Linux) system. Wayne - 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: Not a typewriter
On 05/11/2001 at 12:03:43 PM Joel Jaeggli [EMAIL PROTECTED] wrote: it's not clear to me that that textsearch is a more accurate description than Get Regular ExPression It's not more accurate. But Hacksaw's original point was that a new user would not know what not a typewriter meant. My point was that a newbie wouldn't be likely to guess that grep means search for text either; in both cases he'd have to look it up if he'd never seen it before. BTW, grep does not stand for Get Regular ExPression. It comes from an often-used command in the ed (and ex and vi) editor: g/re/p. The g means global, the re is a regular expression, and the p means print. So to search for all lines containing the word foo in a file you were editing, you would type g/foo/p. This was such a useful function that it was packaged in a standalone program that could be used to search multiple files. Wayne - 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 2.4.4-ac7
I always make mrproper after applying your patches, and I still got exactly the same problem with nfs that Marek found. There were no errors or warnings during the compile of the objects in the fs/nfs directory or the linking of nfs.o. Wayne Alan Cox [EMAIL PROTECTED] on 05/11/2001 12:53:03 PM To: [EMAIL PROTECTED] (Marek P tlicki) cc: [EMAIL PROTECTED] (Alan Cox), [EMAIL PROTECTED] (bcc: Wayne Brown/Corporate/Altec) Subject: Re: Linux 2.4.4-ac7 is the EXTRAVERSION set properly in Makefile? I use the http://www.bzim= age.org intermediate diff (chosen ~40K to ~2M) from ac6 nd I still have 2.4.4-ac6 login prompt (and Makefile says: EXTRAVERSION =3D -ac6). I forgot to change it The other thing I noticed is: /lib/modules/2.4.4-ac6/kernel/fs/nfs/nfs.o: unresolved symbol filemap_f= datawait_Rd4250148 /lib/modules/2.4.4-ac6/kernel/fs/nfs/nfs.o: unresolved symbol filemap_f= datasync_Rf18ce7a1 cp .config ..; make mrproper; cp ../.config .config I suspect its an unclean build and the exports didnt get done right. At least I think I fixed these right 8) - 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 2.4.4-ac7
My modules/filemap.ver has the same in it as yours. Wayne Alan Cox [EMAIL PROTECTED] on 05/11/2001 01:52:18 PM To: Wayne Brown/Corporate/Altec@Altec cc: [EMAIL PROTECTED] (Alan Cox), [EMAIL PROTECTED] (Marek P tlicki), [EMAIL PROTECTED] Subject: Re: Linux 2.4.4-ac7 I always make mrproper after applying your patches, and I still got exactly the same problem with nfs that Marek found. There were no errors or warnings during the compile of the objects in the fs/nfs directory or the linking of nfs.o. Curious : my build has #define __ver_filemap_fdatasyncf18ce7a1 #define filemap_fdatasync _set_ver(filemap_fdatasync) #define __ver_filemap_fdatawaitd4250148 #define filemap_fdatawait _set_ver(filemap_fdatawait) in modules/filemap.ver I'll have a look
Re: Linux 2.4.4-ac8 now with added correct EXTRAVERSION
This fixed the problem with unresolved symbols in nfs.o. Wayne - 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: Not a typewriter
On 05/11/2001 at 04:43:13 PM Hacksaw [EMAIL PROTECTED] wrote: snip Well, I can't disagree. Unix's biggest turn off was the stupid command names. It's a big reason why Unixoid systems aren't more commonplace. I only learned it because I was stuck at a desk with a Wyse terminal. Otherwise I probably would have played with the Autocad machines more. Once I understood the basics, I understood the power of the system. My first exposure to Unix came in 1987 when I was assigned to write a datacomm package in C on a Unix (AIX) workstation the company had just bought. I was the only one in our shop who knew C, and no one else there had ever dealt with Unix either. (I had heard of Unix, but didn't know anything about it.) My training consisted of my boss handing me the manuals and saying, Figure it out. For the first two weeks I absolutely HATED that system; nothing made sense, vi seemed insane, and I was stumbling blindly through the documentation (I'd never seen a permuted index before). Then suddenly something clicked, it all started to make sense, and I fell in love with it. That's why I think it's so important for people to learn the Unix mindset before trying to deal with Unix systems. It's also why I have so little patience with people who don't have the patience to work through the learning curve. snip But first we need a better help system. The absolute most stupid convention of Unix is the man command. The fact that SCCS before, and now Bash usurp the keyword help is beyond the pale. I guess we'll just have to agree to disagree, because we have exactly opposite opinions on all this. I love the short, cryptic command names, and I think man is the best help system ever devised. (The GNU Info system, however, is the spawn of Satan. :-) In case you haven't guessed, I love vi, too, and use it whenever possible. If Unix (or Linux) ever gets to the point of losing things like this, I'll have no desire to use it. Wayne - 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: Not a typewriter
On 05/10/2001 at 05:38:32 PM [EMAIL PROTECTED] (H. Peter Anvin) wrote: >Sounds like someone has just clarified what the heck it means. "tty" >and "typewriter" aren't exactly the same thing (even though "tty" >stands for "teletypewriter" it has come to mean something completely >different in a Unix context)... "not a typewriter" is just a >completely confusing error message for the uninitiated. I disagree. "Not a typewriter" is part of Unix tradition, and ought to be retained as a historical reference. It's also an opportunity for "the uninitiated" to learn a little more and move a little closer to becoming "the initiated." Wayne - 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: Not a typewriter
On 05/10/2001 at 05:38:32 PM [EMAIL PROTECTED] (H. Peter Anvin) wrote: Sounds like someone has just clarified what the heck it means. tty and typewriter aren't exactly the same thing (even though tty stands for teletypewriter it has come to mean something completely different in a Unix context)... not a typewriter is just a completely confusing error message for the uninitiated. I disagree. Not a typewriter is part of Unix tradition, and ought to be retained as a historical reference. It's also an opportunity for the uninitiated to learn a little more and move a little closer to becoming the initiated. Wayne - 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: [Solved ?] Re: pcmcia problems after upgrading from 2.4.3-ac7 to 2.4.4
The thing that confused me here was the help text in menuconfig. The help for CONFIG_I82365 says, "Say Y here to include support for PCMCIA and CardBus host bridges that are register compatible with the Intel i82365 and/or the Yenta specification: this includes virtually all modern PCMCIA bridges." Also, the help text for both this option and CONFIG_CARDBUS say, "If unsure, say Y," so I selected both of them. It wasn't until Jeff Garzik set me straight recently that I began disabling CONFIG_I82365 and using CONFIG_CARDBUS alone. Wayne David Woodhouse <[EMAIL PROTECTED]> on 05/07/2001 03:58:00 AM To: "Martin.Knoblauch" <[EMAIL PROTECTED]> cc: Alan Cox <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (bcc: Wayne Brown/Corporate/Altec) Subject: Re: [Solved ?] Re: pcmcia problems after upgrading from 2.4.3-ac7 to 2.4.4 [EMAIL PROTECTED] said: > > I am not sure whether this should be closed alltogether. Maybe > i82365 was not the proper choice for my hardware in the first place. > Anyway, the module seems to be retired as of 2.4.3-ac10/ac11. Maybe a > hint should go into the changes document. i82365 is for use only on PCMCIA bridges, not CardBus. It should not be 'retired' but should probably have the config option renamed to prevent confusion. -- dwmw2 - 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/ - 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: [Solved ?] Re: pcmcia problems after upgrading from 2.4.3-ac7 to 2.4.4
The thing that confused me here was the help text in menuconfig. The help for CONFIG_I82365 says, Say Y here to include support for PCMCIA and CardBus host bridges that are register compatible with the Intel i82365 and/or the Yenta specification: this includes virtually all modern PCMCIA bridges. Also, the help text for both this option and CONFIG_CARDBUS say, If unsure, say Y, so I selected both of them. It wasn't until Jeff Garzik set me straight recently that I began disabling CONFIG_I82365 and using CONFIG_CARDBUS alone. Wayne David Woodhouse [EMAIL PROTECTED] on 05/07/2001 03:58:00 AM To: Martin.Knoblauch [EMAIL PROTECTED] cc: Alan Cox [EMAIL PROTECTED], [EMAIL PROTECTED] (bcc: Wayne Brown/Corporate/Altec) Subject: Re: [Solved ?] Re: pcmcia problems after upgrading from 2.4.3-ac7 to 2.4.4 [EMAIL PROTECTED] said: I am not sure whether this should be closed alltogether. Maybe i82365 was not the proper choice for my hardware in the first place. Anyway, the module seems to be retired as of 2.4.3-ac10/ac11. Maybe a hint should go into the changes document. i82365 is for use only on PCMCIA bridges, not CardBus. It should not be 'retired' but should probably have the config option renamed to prevent confusion. -- dwmw2 - 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/ - 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: binfmt_misc on 2.4.3-ac14
<[EMAIL PROTECTED]> wrote: >thank you very much :-) > >is it going to become the default in future kernel releases? You're welcome. It's been that way in the -ac kernels for a while now, but Linus hasn't put it into his kernels yet. Perhaps he's waiting until work begins on 2.5, rather than break an existing interface in 2.4. Anyway, it's entirely up to Linus, so I'm just guessing here. :-) Wayne - 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: binfmt_misc on 2.4.3-ac14
Marek P tlicki <[EMAIL PROTECTED]> wrote: >The directory /proc/sys/fs/binfmt_misc/ exists, but nothing in it. Try this: mount -t binfmt_misc none /proc/sys/fs/binfmt_misc In the recent -ac versions, binfmt_misc must be mounted separately. I have the following in my /etc/rc.d/rc.local so that it will work with both Linus' and Alan's kernels (the third variation was for an older -ac kernel that didn't create the binfmt_misc directory either; it's really not needed anymore but I left it in just in case): # # Register entries in binfmt_misc # if [ -f /proc/sys/fs/binfmt_misc/register ] ; then echo ':DOSWin:M::MZ::/usr/local/bin/wine:' > /proc/sys/fs/binfmt_misc/register elif [ -d /proc/sys/fs/binfmt_misc ] ; then mount -t binfmt_misc none /proc/sys/fs/binfmt_misc echo ':DOSWin:M::MZ::/usr/local/bin/wine:' > /proc/sys/fs/binfmt_misc/register else mount -t binfmt_misc none /etc/binfmt_misc echo ':DOSWin:M::MZ::/usr/local/bin/wine:' > /etc/binfmt_misc/register fi Wayne
Re: binfmt_misc on 2.4.3-ac14
Marek P tlicki [EMAIL PROTECTED] wrote: The directory /proc/sys/fs/binfmt_misc/ exists, but nothing in it. Try this: mount -t binfmt_misc none /proc/sys/fs/binfmt_misc In the recent -ac versions, binfmt_misc must be mounted separately. I have the following in my /etc/rc.d/rc.local so that it will work with both Linus' and Alan's kernels (the third variation was for an older -ac kernel that didn't create the binfmt_misc directory either; it's really not needed anymore but I left it in just in case): # # Register entries in binfmt_misc # if [ -f /proc/sys/fs/binfmt_misc/register ] ; then echo ':DOSWin:M::MZ::/usr/local/bin/wine:' /proc/sys/fs/binfmt_misc/register elif [ -d /proc/sys/fs/binfmt_misc ] ; then mount -t binfmt_misc none /proc/sys/fs/binfmt_misc echo ':DOSWin:M::MZ::/usr/local/bin/wine:' /proc/sys/fs/binfmt_misc/register else mount -t binfmt_misc none /etc/binfmt_misc echo ':DOSWin:M::MZ::/usr/local/bin/wine:' /etc/binfmt_misc/register fi Wayne
Re: binfmt_misc on 2.4.3-ac14
[EMAIL PROTECTED] wrote: thank you very much :-) is it going to become the default in future kernel releases? You're welcome. It's been that way in the -ac kernels for a while now, but Linus hasn't put it into his kernels yet. Perhaps he's waiting until work begins on 2.5, rather than break an existing interface in 2.4. Anyway, it's entirely up to Linus, so I'm just guessing here. :-) Wayne - 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: compile error 2.4.4pre6: inconsistent operand constraints in an
With the __builtin_expect patch [EMAIL PROTECTED] posted, both 2.4.4-pre6 and 2.4.3-ac12 compile with egcs-2.91.66. Also, 2.4.3-ac13 builds without any further patches needed. Wayne Alan Cox <[EMAIL PROTECTED]> on 04/23/2001 05:58:47 PM To: [EMAIL PROTECTED] (axel) cc: [EMAIL PROTECTED] (bcc: Wayne Brown/Corporate/Altec) Subject: Re: compile error 2.4.4pre6: inconsistent operand constraints in an > after having had trouble with compilation due to old gcc version, i have > updated to gcc 3.0 and received the following error: 2.4.4pre6 only builds with gcc 2.96. If you apply the __builtin_expect fixes it builds and runs fine with 2.95. Not tried egcs. The gcc 3.0 asm constraints one I've yet to see a fix for. - 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/ - 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: Current status of NTFS support
Thanks to all who offered suggestions, both on the list and privately. Rather than answer them all individually, I'm going to respond in this one message. Unfortunately the upgrade is not going to be done by me, but by our PC support team. Our laptops originally were set up with two FAT32 partitions: a small one for Win98 and applications, and a large one for data files. I used FIPS to carve off most of the large one for a swap partition and an ext2 partition. Now, because of the larger space requirements of Win2000, they're going to wipe out everything on the drives and start from scratch. They'll be doing all our laptops in a short period of time, and want to do all of them the same way. >From everything I've been told here, it sounds like my best bet is to try and talk them into replacing the two FAT32 partitions (which are contiguous) with one big one and leave my Linux partitions alone. That way I won't have to deal with NTFS at all. Fortunately, one of the PC support guys ought to be sympathetic; he runs Linux at home and has asked me for advice in getting it set up on his laptop, too. I'll see if I can talk him into doing my machine differently from the others. I have to be careful, though; my Linux use at work is tolerated, but not (yet) encouraged, and I don't want to rock the boat too much. Thanks again to everyone. Wayne - 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/
Current status of NTFS support
Where does write support for NTFS stand at the moment? I noticed that it's still marked "Dangerous" in the kernel configuration. This is important to me because it looks like I'll have to start using it next week. My office laptop is going to be "upgraded" from Windows 98 to 2000. Of course, I hardly ever boot into Windows any more since installing a Linux partition last year. But our corporate email standard forces me to use Lotus Notes, which I run under Wine. The Notes executables and databases are installed on my Windows partition. The upgrade, though, will involve wiping the hard drive, allocating the whole drive to a single NTFS partition, and reinstalling Notes after installing Windows 2000 . That means bye-bye FAT32 partition and hello NTFS. I can't mount it read-only because I'll still have to update my Notes databases from Linux. So how risky is this? Also, I'll have to recreate my Linux partitions after the upgrade. Does anyone know if FIPS can split a partition safely that was created under Windows 2000/NT? It worked fine for Windows 98, but I'm a little worried about what might happen if I try to use it on an NTFS partition. I'd appreciate any advice or help anyone can give me. There's just no way I can stand going back to using anything but Linux for my daily work. Wayne - 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/
PCMCIA problem in 2.4.4-pre5
Since upgrading to 2.4.4-pre5 my PCMCIA wireless network card no longer works. Here's a snippet of the dmesg output from 2.4.4-pre5: Linux PCMCIA Card Services 3.1.22 options: [pci] [cardbus] [pm] Intel PCIC probe: not found. ds: no socket drivers loaded! However, it works fine in both 2.4.4-pre4 and 2.4.3-ac10. Here's the relevant portion of the dmesg output from 2.4.3-ac10: Linux PCMCIA Card Services 3.1.22 options: [pci] [cardbus] [pm] Intel PCIC probe: Intel i82365sl B step ISA-to-PCMCIA at port 0x3e0 ofs 0x00, 2 sockets host opts [0]: none host opts [1]: none ISA irqs (scanned) = 3,4,5,7,9,10 polling interval = 1000 ms after which comes a series of cs IO port and memory probes. BTW, I'm using pcmcia-cs-3.1.25. Wayne - 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/
PCMCIA problem in 2.4.4-pre5
Since upgrading to 2.4.4-pre5 my PCMCIA wireless network card no longer works. Here's a snippet of the dmesg output from 2.4.4-pre5: Linux PCMCIA Card Services 3.1.22 options: [pci] [cardbus] [pm] Intel PCIC probe: not found. ds: no socket drivers loaded! However, it works fine in both 2.4.4-pre4 and 2.4.3-ac10. Here's the relevant portion of the dmesg output from 2.4.3-ac10: Linux PCMCIA Card Services 3.1.22 options: [pci] [cardbus] [pm] Intel PCIC probe: Intel i82365sl B step ISA-to-PCMCIA at port 0x3e0 ofs 0x00, 2 sockets host opts [0]: none host opts [1]: none ISA irqs (scanned) = 3,4,5,7,9,10 polling interval = 1000 ms after which comes a series of cs IO port and memory probes. BTW, I'm using pcmcia-cs-3.1.25. Wayne - 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/
Current status of NTFS support
Where does write support for NTFS stand at the moment? I noticed that it's still marked "Dangerous" in the kernel configuration. This is important to me because it looks like I'll have to start using it next week. My office laptop is going to be "upgraded" from Windows 98 to 2000. Of course, I hardly ever boot into Windows any more since installing a Linux partition last year. But our corporate email standard forces me to use Lotus Notes, which I run under Wine. The Notes executables and databases are installed on my Windows partition. The upgrade, though, will involve wiping the hard drive, allocating the whole drive to a single NTFS partition, and reinstalling Notes after installing Windows 2000 . That means bye-bye FAT32 partition and hello NTFS. I can't mount it read-only because I'll still have to update my Notes databases from Linux. So how risky is this? Also, I'll have to recreate my Linux partitions after the upgrade. Does anyone know if FIPS can split a partition safely that was created under Windows 2000/NT? It worked fine for Windows 98, but I'm a little worried about what might happen if I try to use it on an NTFS partition. I'd appreciate any advice or help anyone can give me. There's just no way I can stand going back to using anything but Linux for my daily work. Wayne - 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: Current status of NTFS support
Thanks to all who offered suggestions, both on the list and privately. Rather than answer them all individually, I'm going to respond in this one message. Unfortunately the upgrade is not going to be done by me, but by our PC support team. Our laptops originally were set up with two FAT32 partitions: a small one for Win98 and applications, and a large one for data files. I used FIPS to carve off most of the large one for a swap partition and an ext2 partition. Now, because of the larger space requirements of Win2000, they're going to wipe out everything on the drives and start from scratch. They'll be doing all our laptops in a short period of time, and want to do all of them the same way. From everything I've been told here, it sounds like my best bet is to try and talk them into replacing the two FAT32 partitions (which are contiguous) with one big one and leave my Linux partitions alone. That way I won't have to deal with NTFS at all. Fortunately, one of the PC support guys ought to be sympathetic; he runs Linux at home and has asked me for advice in getting it set up on his laptop, too. I'll see if I can talk him into doing my machine differently from the others. I have to be careful, though; my Linux use at work is tolerated, but not (yet) encouraged, and I don't want to rock the boat too much. Thanks again to everyone. Wayne - 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: badly punctuated parameter list in `#define' (2.4.3-ac5 and 2 .4.4 -pre2)
Drat, I just noticed my #$@%&$ email program word-wrapped some of the long
lines. The four lines that contain just while(0) should be appended (preceded
by a space) to the lines just previous to them.
Wayne
Christoph Hellwig <[EMAIL PROTECTED]> on 04/12/2001 03:16:38 PM
To: Wayne Brown/Corporate/Altec@Altec
cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: badly punctuated parameter list in `#define' (2.4.3-ac5 and 2 .4.4
-pre2)
On Thu, Apr 12, 2001 at 03:08:28PM -0500, [EMAIL PROTECTED] wrote:
> >old compiler. The right ifdef seems to be:
>
> >
> > #if __GNUC__ == 2 && __GNUC_MINOR__ < 95
> >
> >Could you test it this way?
>
> Yes, that works for me. Is this the sort of thing you had in mind?
Yes.
Linus any chance to apply the following patch?
Christoph
>
> Wayne
>
>
> --- include/asm-i386/rwsem.h.old Thu Apr 12 14:50:08 2001
> +++ include/asm-i386/rwsem.h Thu Apr 12 14:54:14 2001
> @@ -20,18 +20,24 @@
> #include
> #include
>
> +#if __GNUC__ == 2 && __GNUC_MINOR__ < 95
> +
> +/* old gcc */
> #if RWSEM_DEBUG
> -#define rwsemdebug(FMT,...) do { if (sem->debug) printk(FMT,__VA_ARGS__); }
> while(0)
> +#define rwsemdebug(FMT, ARGS...) do { if (sem->debug) printk(FMT,##ARGS); }
> while(0)
> #else
> -#define rwsemdebug(FMT,...)
> +#define rwsemdebug(FMT, ARGS...)
> #endif
>
> -/* old gcc */
> +#else
> +
> #if RWSEM_DEBUG
> -//#define rwsemdebug(FMT, ARGS...) do { if (sem->debug) printk(FMT,##ARGS); }
> while(0)
> +#define rwsemdebug(FMT,...) do { if (sem->debug) printk(FMT,__VA_ARGS__); }
> while(0)
> #else
> -//#define rwsemdebug(FMT, ARGS...)
> +#define rwsemdebug(FMT,...)
> #endif
> +
> +#endif /* __GNUC__ == 2 && __GNUC_MINOR__ < 95 */
>
> #ifdef CONFIG_X86_XADD
> #include /* use XADD based semaphores if possible */
>
---end quoted text---
--
Of course it doesn't work. We've performed a software upgrade.
-
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: badly punctuated parameter list in `#define' (2.4.3-ac5 and 2.4.4 -pre2)
Christoph Hellwig <[EMAIL PROTECTED]> wrote:
>So the /* old gcc */ part should probably be enabled based on a define for the
>old compiler. The right ifdef seems to be:
>
> #if __GNUC__ == 2 && __GNUC_MINOR__ < 95
>
>Could you test it this way?
Yes, that works for me. Is this the sort of thing you had in mind?
Wayne
--- include/asm-i386/rwsem.h.old Thu Apr 12 14:50:08 2001
+++ include/asm-i386/rwsem.h Thu Apr 12 14:54:14 2001
@@ -20,18 +20,24 @@
#include
#include
+#if __GNUC__ == 2 && __GNUC_MINOR__ < 95
+
+/* old gcc */
#if RWSEM_DEBUG
-#define rwsemdebug(FMT,...) do { if (sem->debug) printk(FMT,__VA_ARGS__); }
while(0)
+#define rwsemdebug(FMT, ARGS...) do { if (sem->debug) printk(FMT,##ARGS); }
while(0)
#else
-#define rwsemdebug(FMT,...)
+#define rwsemdebug(FMT, ARGS...)
#endif
-/* old gcc */
+#else
+
#if RWSEM_DEBUG
-//#define rwsemdebug(FMT, ARGS...) do { if (sem->debug) printk(FMT,##ARGS); }
while(0)
+#define rwsemdebug(FMT,...) do { if (sem->debug) printk(FMT,__VA_ARGS__); }
while(0)
#else
-//#define rwsemdebug(FMT, ARGS...)
+#define rwsemdebug(FMT,...)
#endif
+
+#endif /* __GNUC__ == 2 && __GNUC_MINOR__ < 95 */
#ifdef CONFIG_X86_XADD
#include /* use XADD based semaphores if possible */
-
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/
badly punctuated parameter list in `#define' (2.4.3-ac5 and 2.4.4-pre2)
When compiling 2.4.3-ac5 (and also 2.4.4-pre2) I get this:
/usr/src/linux-2.4.3-ac5/include/asm/rwsem.h:26: badly punctuated parameter list
in `#define'
This appears to be due to some code in rwsem.h that is written for a different
version of gcc. (I'm still using gcc-2.91.66 as specified in
Documentation/Changes.) It works for me if I replace it with the code in the
section labeled /* old gcc */. Here's a patch to do that:
--- include/asm-i386/rwsem.h.old Thu Apr 12 13:47:00 2001
+++ include/asm-i386/rwsem.h Thu Apr 12 13:48:04 2001
@@ -21,16 +21,16 @@
#include
#if RWSEM_DEBUG
-#define rwsemdebug(FMT,...) do { if (sem->debug) printk(FMT,__VA_ARGS__); }
while(0)
+//#define rwsemdebug(FMT,...) do { if (sem->debug) printk(FMT,__VA_ARGS__); }
while(0)
#else
-#define rwsemdebug(FMT,...)
+//#define rwsemdebug(FMT,...)
#endif
/* old gcc */
#if RWSEM_DEBUG
-//#define rwsemdebug(FMT, ARGS...) do { if (sem->debug) printk(FMT,##ARGS); }
while(0)
+#define rwsemdebug(FMT, ARGS...) do { if (sem->debug) printk(FMT,##ARGS); }
while(0)
#else
-//#define rwsemdebug(FMT, ARGS...)
+#define rwsemdebug(FMT, ARGS...)
#endif
#ifdef CONFIG_X86_XADD
-
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/
badly punctuated parameter list in `#define' (2.4.3-ac5 and 2.4.4-pre2)
When compiling 2.4.3-ac5 (and also 2.4.4-pre2) I get this:
/usr/src/linux-2.4.3-ac5/include/asm/rwsem.h:26: badly punctuated parameter list
in `#define'
This appears to be due to some code in rwsem.h that is written for a different
version of gcc. (I'm still using gcc-2.91.66 as specified in
Documentation/Changes.) It works for me if I replace it with the code in the
section labeled /* old gcc */. Here's a patch to do that:
--- include/asm-i386/rwsem.h.old Thu Apr 12 13:47:00 2001
+++ include/asm-i386/rwsem.h Thu Apr 12 13:48:04 2001
@@ -21,16 +21,16 @@
#include linux/wait.h
#if RWSEM_DEBUG
-#define rwsemdebug(FMT,...) do { if (sem-debug) printk(FMT,__VA_ARGS__); }
while(0)
+//#define rwsemdebug(FMT,...) do { if (sem-debug) printk(FMT,__VA_ARGS__); }
while(0)
#else
-#define rwsemdebug(FMT,...)
+//#define rwsemdebug(FMT,...)
#endif
/* old gcc */
#if RWSEM_DEBUG
-//#define rwsemdebug(FMT, ARGS...) do { if (sem-debug) printk(FMT,##ARGS); }
while(0)
+#define rwsemdebug(FMT, ARGS...) do { if (sem-debug) printk(FMT,##ARGS); }
while(0)
#else
-//#define rwsemdebug(FMT, ARGS...)
+#define rwsemdebug(FMT, ARGS...)
#endif
#ifdef CONFIG_X86_XADD
-
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: badly punctuated parameter list in `#define' (2.4.3-ac5 and 2.4.4 -pre2)
Christoph Hellwig [EMAIL PROTECTED] wrote:
So the /* old gcc */ part should probably be enabled based on a define for the
old compiler. The right ifdef seems to be:
#if __GNUC__ == 2 __GNUC_MINOR__ 95
Could you test it this way?
Yes, that works for me. Is this the sort of thing you had in mind?
Wayne
--- include/asm-i386/rwsem.h.old Thu Apr 12 14:50:08 2001
+++ include/asm-i386/rwsem.h Thu Apr 12 14:54:14 2001
@@ -20,18 +20,24 @@
#include linux/spinlock.h
#include linux/wait.h
+#if __GNUC__ == 2 __GNUC_MINOR__ 95
+
+/* old gcc */
#if RWSEM_DEBUG
-#define rwsemdebug(FMT,...) do { if (sem-debug) printk(FMT,__VA_ARGS__); }
while(0)
+#define rwsemdebug(FMT, ARGS...) do { if (sem-debug) printk(FMT,##ARGS); }
while(0)
#else
-#define rwsemdebug(FMT,...)
+#define rwsemdebug(FMT, ARGS...)
#endif
-/* old gcc */
+#else
+
#if RWSEM_DEBUG
-//#define rwsemdebug(FMT, ARGS...) do { if (sem-debug) printk(FMT,##ARGS); }
while(0)
+#define rwsemdebug(FMT,...) do { if (sem-debug) printk(FMT,__VA_ARGS__); }
while(0)
#else
-//#define rwsemdebug(FMT, ARGS...)
+#define rwsemdebug(FMT,...)
#endif
+
+#endif /* __GNUC__ == 2 __GNUC_MINOR__ 95 */
#ifdef CONFIG_X86_XADD
#include asm/rwsem-xadd.h /* use XADD based semaphores if possible */
-
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: badly punctuated parameter list in `#define' (2.4.3-ac5 and 2 .4.4 -pre2)
Drat, I just noticed my #$@%$ email program word-wrapped some of the long
lines. The four lines that contain just while(0) should be appended (preceded
by a space) to the lines just previous to them.
Wayne
Christoph Hellwig [EMAIL PROTECTED] on 04/12/2001 03:16:38 PM
To: Wayne Brown/Corporate/Altec@Altec
cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: badly punctuated parameter list in `#define' (2.4.3-ac5 and 2 .4.4
-pre2)
On Thu, Apr 12, 2001 at 03:08:28PM -0500, [EMAIL PROTECTED] wrote:
old compiler. The right ifdef seems to be:
#if __GNUC__ == 2 __GNUC_MINOR__ 95
Could you test it this way?
Yes, that works for me. Is this the sort of thing you had in mind?
Yes.
Linus any chance to apply the following patch?
Christoph
Wayne
--- include/asm-i386/rwsem.h.old Thu Apr 12 14:50:08 2001
+++ include/asm-i386/rwsem.h Thu Apr 12 14:54:14 2001
@@ -20,18 +20,24 @@
#include linux/spinlock.h
#include linux/wait.h
+#if __GNUC__ == 2 __GNUC_MINOR__ 95
+
+/* old gcc */
#if RWSEM_DEBUG
-#define rwsemdebug(FMT,...) do { if (sem-debug) printk(FMT,__VA_ARGS__); }
while(0)
+#define rwsemdebug(FMT, ARGS...) do { if (sem-debug) printk(FMT,##ARGS); }
while(0)
#else
-#define rwsemdebug(FMT,...)
+#define rwsemdebug(FMT, ARGS...)
#endif
-/* old gcc */
+#else
+
#if RWSEM_DEBUG
-//#define rwsemdebug(FMT, ARGS...) do { if (sem-debug) printk(FMT,##ARGS); }
while(0)
+#define rwsemdebug(FMT,...) do { if (sem-debug) printk(FMT,__VA_ARGS__); }
while(0)
#else
-//#define rwsemdebug(FMT, ARGS...)
+#define rwsemdebug(FMT,...)
#endif
+
+#endif /* __GNUC__ == 2 __GNUC_MINOR__ 95 */
#ifdef CONFIG_X86_XADD
#include asm/rwsem-xadd.h /* use XADD based semaphores if possible */
---end quoted text---
--
Of course it doesn't work. We've performed a software upgrade.
-
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: goodbye
David Woodhouse <[EMAIL PROTECTED]> wrote: >"self-appointed" > >Are you implying that the people who run ORBS and the other RBL lists >actually hacked into vger.kernel.org and changed the MTA configuration to >use those lists? I was of the opinion that it was a free choice made by the >administrators of that machine. OK, "self-appointed" was too strong a term. What ORBS and its ilk do is provide a simple, easy-to-use method of blocking large chunks of the net from communicating with other large chunks, regardless of whether the systems blocked are assisting in spam propagation or not. The *possibility* of someday being guilty is enough to quarantine them. Granted, it requires the cooperation of other administrators to accomplish that. I'm not denying that the administrators of mailing lists have the right to control what happens on their lists. It's just that I'm personally opposed to spam-blocking methods that go above the level of a single system, or maybe even a single user. My primary email account gets tons of spam every day. Often I get three or more copies of the same spam, demonstrating both that my address has been harvested from multiple locations and that the spammers are clueless about managing their own mailing lists. Yet the only defense I use is my delete key (and a personal resolve never to do business with any of those companies under any circumstances). I just accept the fact that only one out of every dozen or so emails I receive will be of any interest to me. The rest vanish without wasting more than a few seconds of my day. It's not even worth setting up killfiles, although that would eliminate most of my repeat offenders. If individual mailing list administrators want to block email from certain sites because of spam concerns, fine. But I still hold organizations like ORBS, that encourage such things and make it easy, in contempt. They conjure up an image for me of those annoying "hall monitors" in grade school who were always hoping to find someone breaking a rule, so they could tattle on them. >Can we take this pointlessness off l-k now please? Your message included l-k in the headers, so my response does also. But I have no intention of carrying on this discussion any further, in public or private, so this is the last post you'll see from me on the subject. Wayne - 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: goodbye
Joseph Carter <[EMAIL PROTECTED]> wrote: >Let's see, ORBS takes out the ISP route, DUL takes out the direct one. Is >it any wonder people are hostile toward those two lists? Exactly. I hate spam, but I hate ORBS and DUL even more. If I'm going to get the shaft, I'd rather it be from the "bad guys" (spammers) than from self-appointed net.cops. Wayne - 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: goodbye
Joseph Carter [EMAIL PROTECTED] wrote: Let's see, ORBS takes out the ISP route, DUL takes out the direct one. Is it any wonder people are hostile toward those two lists? Exactly. I hate spam, but I hate ORBS and DUL even more. If I'm going to get the shaft, I'd rather it be from the "bad guys" (spammers) than from self-appointed net.cops. Wayne - 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: goodbye
David Woodhouse [EMAIL PROTECTED] wrote: "self-appointed" Are you implying that the people who run ORBS and the other RBL lists actually hacked into vger.kernel.org and changed the MTA configuration to use those lists? I was of the opinion that it was a free choice made by the administrators of that machine. OK, "self-appointed" was too strong a term. What ORBS and its ilk do is provide a simple, easy-to-use method of blocking large chunks of the net from communicating with other large chunks, regardless of whether the systems blocked are assisting in spam propagation or not. The *possibility* of someday being guilty is enough to quarantine them. Granted, it requires the cooperation of other administrators to accomplish that. I'm not denying that the administrators of mailing lists have the right to control what happens on their lists. It's just that I'm personally opposed to spam-blocking methods that go above the level of a single system, or maybe even a single user. My primary email account gets tons of spam every day. Often I get three or more copies of the same spam, demonstrating both that my address has been harvested from multiple locations and that the spammers are clueless about managing their own mailing lists. Yet the only defense I use is my delete key (and a personal resolve never to do business with any of those companies under any circumstances). I just accept the fact that only one out of every dozen or so emails I receive will be of any interest to me. The rest vanish without wasting more than a few seconds of my day. It's not even worth setting up killfiles, although that would eliminate most of my repeat offenders. If individual mailing list administrators want to block email from certain sites because of spam concerns, fine. But I still hold organizations like ORBS, that encourage such things and make it easy, in contempt. They conjure up an image for me of those annoying "hall monitors" in grade school who were always hoping to find someone breaking a rule, so they could tattle on them. Can we take this pointlessness off l-k now please? Your message included l-k in the headers, so my response does also. But I have no intention of carrying on this discussion any further, in public or private, so this is the last post you'll see from me on the subject. Wayne - 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: Larger dev_t
Ingo Oeser <[EMAIL PROTECTED]> wrote: >Yes: Let "mknod /dev/foo [bc] x y" die! I hope this never happens. Improving the major/minor device scheme is reasonable; abandoning it would be a sad occurrence. It would make Linux too "un-UNIXish" (how's THAT for an an ugly neologism!) for my tastes. Wayne - 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: Larger dev_t
Ingo Oeser [EMAIL PROTECTED] wrote: Yes: Let "mknod /dev/foo [bc] x y" die! I hope this never happens. Improving the major/minor device scheme is reasonable; abandoning it would be a sad occurrence. It would make Linux too "un-UNIXish" (how's THAT for an an ugly neologism!) for my tastes. Wayne - 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: kernel crash
I hope you were using a scratch monkey... - 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: New directions for kernel development
Linus Torvalds wrote: >Virtually all users of Linux (and all other >forms of Un*x) are unkempt, longhaired, beast-bearded dirty GNU hippies, and >I am sick and tired of having to deal with them. I just wish you'd bothered to make all this public sooner. Here I am, having spent the last couple of months growing a beard to enhance my hackerhood, and now, just when it's starting to look good, you want me to shave it off! That's the whole problem with Linux. It's about time you stopped using these undocumented hygiene interfaces and published some solid standards! (And don't give me that old excuse about having your pictures right in front of us -- "A real hacker wouldn't need documentation, he'd just read my face.") Wayne - 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: New directions for kernel development
Linus Torvalds wrote: Virtually all users of Linux (and all other forms of Un*x) are unkempt, longhaired, beast-bearded dirty GNU hippies, and I am sick and tired of having to deal with them. I just wish you'd bothered to make all this public sooner. Here I am, having spent the last couple of months growing a beard to enhance my hackerhood, and now, just when it's starting to look good, you want me to shave it off! That's the whole problem with Linux. It's about time you stopped using these undocumented hygiene interfaces and published some solid standards! (And don't give me that old excuse about having your pictures right in front of us -- "A real hacker wouldn't need documentation, he'd just read my face.") Wayne - 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: kernel crash
I hope you were using a scratch monkey... - 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: Modem and sound support question..
Try http://walbran.org/sean/linux/stodolsk/ for the Lucent Winmodem driver. Wayne JorgP <[EMAIL PROTECTED]> on 03/23/2001 03:33:30 PM Please respond to [EMAIL PROTECTED] To: Linux Kernel Mailing List <[EMAIL PROTECTED]> cc: (bcc: Wayne Brown/Corporate/Altec) Subject: Modem and sound support question.. Lucent Microelectronics 56k WinModem s (rev 01) VIA Technologies, Inc. VT82C686 [Apollo Super AC97/Audio] (rev 50) are either or both support by 2.4 kernel? If so, what modules need to be loaded? -- Thanks Jorg - 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/ - 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: Modem and sound support question..
Try http://walbran.org/sean/linux/stodolsk/ for the Lucent Winmodem driver. Wayne JorgP [EMAIL PROTECTED] on 03/23/2001 03:33:30 PM Please respond to [EMAIL PROTECTED] To: Linux Kernel Mailing List [EMAIL PROTECTED] cc:(bcc: Wayne Brown/Corporate/Altec) Subject: Modem and sound support question.. Lucent Microelectronics 56k WinModem s (rev 01) VIA Technologies, Inc. VT82C686 [Apollo Super AC97/Audio] (rev 50) are either or both support by 2.4 kernel? If so, what modules need to be loaded? -- Thanks Jorg - 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/ - 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: How to mount /proc/sys/fs/binfmt_misc ?
Thanks for the quick response. I took your suggestion (a) and created
/etc/binfmt_misc, and set up a test in my rc.local to mount it and register my
usual entries there if /proc/sys/fs/binfmt_misc doesn't exist. So now it works
with both 2.4.3-pre4 and 2.4.2-ac20.
Wayne
Alexander Viro <[EMAIL PROTECTED]> on 03/16/2001 09:37:49 AM
To: Wayne Brown/Corporate/Altec@Altec
cc: [EMAIL PROTECTED]
Subject: Re: How to mount /proc/sys/fs/binfmt_misc ?
On Fri, 16 Mar 2001 [EMAIL PROTECTED] wrote:
> The release notes specify this:
>
> mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
>
> but this doesn't work because
>
> mount: mount point /proc/sys/fs/binfmt_misc does not exist
Grr... OK, I've been an overoptimistic idiot and missed that ugliness.
Solutions:
a) mount it on some real place. And write there to register
entries instead of the bogus /proc/sys/fs/binfmt_misc
b) add a couple of proc_mkdir() into fs/proc/root.c
That is, add
proc_mkdir("sys/fs", 0):
proc_mkdir("sys/fs/binfmt_misc", 0);
after the line that says
proc_mkdir("sys", 0);
I would strongly recommend (a). In the long run we'll need to go that
way.
-
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/
How to mount /proc/sys/fs/binfmt_misc ?
OK, I've been struggling with this (off and on) since Tuesday, and I give up. Since going from 2.4.3-pre4 to 2.4.2-ac20 I have been unable to use binfmt_misc. Thanks to a hint from Michael Meissner, I found a mention in the release notes for 2.4.2-ac12 that binfmt_misc should be mounted separately. However, I still have a problem. The release notes specify this: mount -t binfmt_misc none /proc/sys/fs/binfmt_misc but this doesn't work because mount: mount point /proc/sys/fs/binfmt_misc does not exist And if I try to mkdir -p /proc/sys/fs/binfmt_misc with /proc mounted I get mkdir: cannot create directory `/proc/sys/fs/binfmt_misc': No such file or directory which makes sense, I guess, because proc isn't a "real" filesystem. So how do I get binfmt_misc mounted? Wayne - 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/
How to mount /proc/sys/fs/binfmt_misc ?
OK, I've been struggling with this (off and on) since Tuesday, and I give up. Since going from 2.4.3-pre4 to 2.4.2-ac20 I have been unable to use binfmt_misc. Thanks to a hint from Michael Meissner, I found a mention in the release notes for 2.4.2-ac12 that binfmt_misc should be mounted separately. However, I still have a problem. The release notes specify this: mount -t binfmt_misc none /proc/sys/fs/binfmt_misc but this doesn't work because mount: mount point /proc/sys/fs/binfmt_misc does not exist And if I try to mkdir -p /proc/sys/fs/binfmt_misc with /proc mounted I get mkdir: cannot create directory `/proc/sys/fs/binfmt_misc': No such file or directory which makes sense, I guess, because proc isn't a "real" filesystem. So how do I get binfmt_misc mounted? Wayne - 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: How to mount /proc/sys/fs/binfmt_misc ?
Thanks for the quick response. I took your suggestion (a) and created
/etc/binfmt_misc, and set up a test in my rc.local to mount it and register my
usual entries there if /proc/sys/fs/binfmt_misc doesn't exist. So now it works
with both 2.4.3-pre4 and 2.4.2-ac20.
Wayne
Alexander Viro [EMAIL PROTECTED] on 03/16/2001 09:37:49 AM
To: Wayne Brown/Corporate/Altec@Altec
cc: [EMAIL PROTECTED]
Subject: Re: How to mount /proc/sys/fs/binfmt_misc ?
On Fri, 16 Mar 2001 [EMAIL PROTECTED] wrote:
The release notes specify this:
mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
but this doesn't work because
mount: mount point /proc/sys/fs/binfmt_misc does not exist
Grr... OK, I've been an overoptimistic idiot and missed that ugliness.
Solutions:
a) mount it on some real place. And write there to register
entries instead of the bogus /proc/sys/fs/binfmt_misc
b) add a couple of proc_mkdir() into fs/proc/root.c
That is, add
proc_mkdir("sys/fs", 0):
proc_mkdir("sys/fs/binfmt_misc", 0);
after the line that says
proc_mkdir("sys", 0);
I would strongly recommend (a). In the long run we'll need to go that
way.
-
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 2.4.2ac20
I've just noticed with 2.4.2-ac20 that /proc/sys/fs/binfmt_misc is no longer being created. I have CONFIG_BINFMT_MISC=y in my .config. This was working fine in 2.4.3-pre4. Wayne - 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 2.4.2ac20
I've just noticed with 2.4.2-ac20 that /proc/sys/fs/binfmt_misc is no longer being created. I have CONFIG_BINFMT_MISC=y in my .config. This was working fine in 2.4.3-pre4. Wayne - 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: Microsoft begining to open source Windows 2000?
No, the Linux way is to send the patch to everyone else who's developing or testing the kernel. Even if Linus doesn't accept it into the "official" kernel, there's nothing to stop you (or anyone else) from using it yourself or distributing it to others. The Microsoft agreement prevents you from changing the source, and if they decide to ignore your bug report, there's nothing you can do about it. Oh, and you have to pay (at least 1500 licenses' worth) for the "privilege" of doing their debugging work for them. That's about as far from the Linux way of doing things as you can get. Wayne Venkatesh Ramamurthy <[EMAIL PROTECTED]> on 03/08/2001 10:04:25 AM To: 'Alan Cox' <[EMAIL PROTECTED]> cc: [EMAIL PROTECTED] (bcc: Wayne Brown/Corporate/Altec) Subject: RE: Microsoft begining to open source Windows 2000? My initial thought after seeing this article was that microsoft was testing its waters on open sourcing. If i have 1500 licenses then i would get the source. If i find any bug in thier source , i would report to microsoft or send a patch and they would put it in thier next version. Is this not the same way Linux Kernel is developed?. Only thing microsoft does not want to immediately go full open sourcing and get embarrased at the hands of linux people. - 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: Microsoft begining to open source Windows 2000?
No, the Linux way is to send the patch to everyone else who's developing or testing the kernel. Even if Linus doesn't accept it into the "official" kernel, there's nothing to stop you (or anyone else) from using it yourself or distributing it to others. The Microsoft agreement prevents you from changing the source, and if they decide to ignore your bug report, there's nothing you can do about it. Oh, and you have to pay (at least 1500 licenses' worth) for the "privilege" of doing their debugging work for them. That's about as far from the Linux way of doing things as you can get. Wayne Venkatesh Ramamurthy [EMAIL PROTECTED] on 03/08/2001 10:04:25 AM To: 'Alan Cox' [EMAIL PROTECTED] cc: [EMAIL PROTECTED] (bcc: Wayne Brown/Corporate/Altec) Subject: RE: Microsoft begining to open source Windows 2000? My initial thought after seeing this article was that microsoft was testing its waters on open sourcing. If i have 1500 licenses then i would get the source. If i find any bug in thier source , i would report to microsoft or send a patch and they would put it in thier next version. Is this not the same way Linux Kernel is developed?. Only thing microsoft does not want to immediately go full open sourcing and get embarrased at the hands of linux people. - 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: [acme@conectiva.com.br: Re: mke2fs /dev/loop0]
What is the current version of ncpfs, and where can it be found? The most recent I could find (at www.ibiblio.org) was ncpfs-2.2.0 which dates back to May 1998, and I ran into the problem with select when trying to compile it on a current system. I got it to work by compiling it on an old 2.0.x box that I haven't upgraded in several years, then moved it to my 2.4.x system. It's been working fine for several months, but I'd like to be able to compile it on a current system without hacking the source. Wayne "Petr Vandrovec" <[EMAIL PROTECTED]> on 03/05/2001 05:41:47 AM To: "Holluby IstvBetan [EMAIL PROTECTED]" <[EMAIL PROTECTED]> cc: [EMAIL PROTECTED], [EMAIL PROTECTED] (bcc: Wayne Brown/Corporate/Altec) Subject: Re: [[EMAIL PROTECTED]: Re: mke2fs /dev/loop0] On 5 Mar 01 at 12:27, Holluby Istv ßn istvan.holluby wrote: > On Wed, 28 Feb 2001, Arnaldo Carvalho de Melo wrote: > > The problem was simply, that I couldn't cd to a directory. > "File exist, but couldn't be stat-ed" or something similar was the > message. Reasonable recent kernels should display ':' instead of unknown characters on ncpfs. Of course it requires that codepage->unicode translation table does not contain disallowed translations. > > Can you be more specific? ncpfs should (and AFAIK does) compile out > > of the box > > On glibc-2.2.2 header files of select changed. So it does not > compile cleanly. If I remember well, a define called number_of_open or > similar was also missing. I am not sure in it thou. It might have been > some other program. You are using some really old ncpfs. Petr Vandrovec [EMAIL PROTECTED] - 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: [acme@conectiva.com.br: Re: mke2fs /dev/loop0]
What is the current version of ncpfs, and where can it be found? The most recent I could find (at www.ibiblio.org) was ncpfs-2.2.0 which dates back to May 1998, and I ran into the problem with select when trying to compile it on a current system. I got it to work by compiling it on an old 2.0.x box that I haven't upgraded in several years, then moved it to my 2.4.x system. It's been working fine for several months, but I'd like to be able to compile it on a current system without hacking the source. Wayne "Petr Vandrovec" [EMAIL PROTECTED] on 03/05/2001 05:41:47 AM To: "Holluby IstvBetan [EMAIL PROTECTED]" [EMAIL PROTECTED] cc: [EMAIL PROTECTED], [EMAIL PROTECTED] (bcc: Wayne Brown/Corporate/Altec) Subject: Re: [[EMAIL PROTECTED]: Re: mke2fs /dev/loop0] On 5 Mar 01 at 12:27, Holluby Istv n istvan.holluby wrote: On Wed, 28 Feb 2001, Arnaldo Carvalho de Melo wrote: The problem was simply, that I couldn't cd to a directory. "File exist, but couldn't be stat-ed" or something similar was the message. Reasonable recent kernels should display ':' instead of unknown characters on ncpfs. Of course it requires that codepage-unicode translation table does not contain disallowed translations. Can you be more specific? ncpfs should (and AFAIK does) compile out of the box On glibc-2.2.2 header files of select changed. So it does not compile cleanly. If I remember well, a define called number_of_open or similar was also missing. I am not sure in it thou. It might have been some other program. You are using some really old ncpfs. Petr Vandrovec [EMAIL PROTECTED] - 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 stifles innovation...
Actually, in today's "User Friendly" comic strip (http://www.userfriendly.org) one of the characters asks exactly that same question. Wayne "Andrew Scott" <[EMAIL PROTECTED]> on 02/16/2001 08:25:20 AM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Wayne Brown/Corporate/Altec) Subject: Re: Linux stifles innovation... On 15 Feb 2001, at 9:49, fsnchzjr wrote: > Watch Microsoft's Jim Allchin go Linux-bashing!!! > Nice little article on how we're all going to die of herpes from our > repeated exposition to Linux... > http://news.cnet.com/investor/news/newsitem/0-9900-1028-4825719-RHAT.html?ta > g=ltnc That's about as self-serving a statement as I've ever seen. If this 'Jim Alchin' actually believes what he's saying, he's got to be one of the worlds biggest fools, and if he doesn't believe what he's saying, well there aren't too many words that would accurately describe what he is. It's pretty funny in some ways, e.g. "We can build a better product than Linux...", which begs the question, "Well, why don't you?". Perhaps it costs too much? --Mailed via Pegasus 3.12c & Mercury 1.48--- [EMAIL PROTECTED]Fax (617)373-2942 Andrew Scott Tel (617)373-5278 _ Northeastern University--138 Meserve Hall / \ / College of Arts & Sciences-Deans Office / \ \ / Boston, Ma. 02115 / \_/ - 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/ - 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 stifles innovation...
Actually, in today's "User Friendly" comic strip (http://www.userfriendly.org) one of the characters asks exactly that same question. Wayne "Andrew Scott" [EMAIL PROTECTED] on 02/16/2001 08:25:20 AM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Wayne Brown/Corporate/Altec) Subject: Re: Linux stifles innovation... On 15 Feb 2001, at 9:49, fsnchzjr wrote: Watch Microsoft's Jim Allchin go Linux-bashing!!! Nice little article on how we're all going to die of herpes from our repeated exposition to Linux... http://news.cnet.com/investor/news/newsitem/0-9900-1028-4825719-RHAT.html?ta g=ltnc That's about as self-serving a statement as I've ever seen. If this 'Jim Alchin' actually believes what he's saying, he's got to be one of the worlds biggest fools, and if he doesn't believe what he's saying, well there aren't too many words that would accurately describe what he is. It's pretty funny in some ways, e.g. "We can build a better product than Linux...", which begs the question, "Well, why don't you?". Perhaps it costs too much? --Mailed via Pegasus 3.12c Mercury 1.48--- [EMAIL PROTECTED]Fax (617)373-2942 Andrew Scott Tel (617)373-5278 _ Northeastern University--138 Meserve Hall / \ / College of Arts Sciences-Deans Office / \ \ / Boston, Ma. 02115 / \_/ - 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/ - 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: [LK] Re: lkml subject line
"Mike A. Harris" <[EMAIL PROTECTED]> wrote: >What is right: > >1) not putting the thing in the subject from the list side >2) If an end user wants it in the subject, they can set up a mail >filter to PUT it in the subject. > >:0 fwh >* ^Sender:.*owner-linux-kernel >| sed -e 's/^Subject: /Subject: [lkml]/' >:0 A: >lkml > >The above filter should add [lkml] to your subject line. So why >try to force it on everyone? The other lists to which I subscribe (SAG-L and HP3000-L) don't force it on everyone. Each subscriber can turn the extra subject tags on or off whenever they please. I have them turned on, so the listserver tacks them on each message that is mailed to me. People who have this option turned off (the default) never see them. >If the above procmail filter doesn't work (untested) let me know >and I will MAKE it work. Windows users - tough luck - procmail >is open source - hire someone to port it... My employer chose Lotus Notes for our email system. All incoming messages go to a Notes server. In order to read them, I have to run a Notes client to connect to the server. As far as I know, there is no way to use another mail reader to access the Notes email database on the server. So, although I run Linux on my laptop, I have to run Notes (under wine) to access my mail. There is no way to filter on headers; in fact, the ONLY headers I can see are To, cc, and Subject. (OK, I can, after opening a message, select "Delivery Information" from a menu, and then scroll through the other headers in a four line by 50 character window; but I have to do this for each message, one at a time, after they reach my inbox. There's no way to search for text in any of these headers, either.) Even if I save the messages to disk (by "exporting" them), I still get only those three headers. I can sort the list of messages in my inbox by sender or by date, but not by subject. So I usually just read everything in FIFO order, without even looking at the subject, hitting the delete key within a couple of seconds for any message that doesn't interest me. After finishing with all the messages, I use the extra tags in the Subject line to (visually) separate the messages I want to keep and move them into separate folders for each mailing list. I always leave the lkml messages till last, because without the extra tags I have to pay special attention to keep them separate from my regular (non-mailing-list) email. As far as I'm concerned, Notes is a lousy mail client. Very little can be configured by the user. The only option for quoted replies simply appends the entire message to the bottom of the reply. (I had to cut and paste your text and add the ">" characters and the "Mike Harris wrote:" line manually.) I can't even set it to automatically forward my mail to my personal email account if I'm out of town. That requires a request to a Notes administrator to do it for me, and I have to ask him to change it back when I return. Plus, when the mail is auto-forwarded it is deleted from my Notes inbox, so if the administrator is slow about turning off auto-forwarding then I don't see any of my business email at work and have to wait until I can access my personal account from home. I haven't complained about any of this on the list until now, because I know I'm in the minority and I don't expect most people to care about my problems. But it bothered me seeing the criticism Mike Harrold has gotten for his request. Not everyone has problems because they're lazy. Some of us are boxed in by decisions that are beyond our control. For my part, if anyone can tell me a method (that doesn't require Notes administrator assistance) to get my mail, with headers intact, out of Notes and into elm or pine, I'd be ecstatic. Wayne - 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: [LK] Re: lkml subject line
"Mike A. Harris" [EMAIL PROTECTED] wrote: What is right: 1) not putting the thing in the subject from the list side 2) If an end user wants it in the subject, they can set up a mail filter to PUT it in the subject. :0 fwh * ^Sender:.*owner-linux-kernel | sed -e 's/^Subject: /Subject: [lkml]/' :0 A: lkml The above filter should add [lkml] to your subject line. So why try to force it on everyone? The other lists to which I subscribe (SAG-L and HP3000-L) don't force it on everyone. Each subscriber can turn the extra subject tags on or off whenever they please. I have them turned on, so the listserver tacks them on each message that is mailed to me. People who have this option turned off (the default) never see them. If the above procmail filter doesn't work (untested) let me know and I will MAKE it work. Windows users - tough luck - procmail is open source - hire someone to port it... My employer chose Lotus Notes for our email system. All incoming messages go to a Notes server. In order to read them, I have to run a Notes client to connect to the server. As far as I know, there is no way to use another mail reader to access the Notes email database on the server. So, although I run Linux on my laptop, I have to run Notes (under wine) to access my mail. There is no way to filter on headers; in fact, the ONLY headers I can see are To, cc, and Subject. (OK, I can, after opening a message, select "Delivery Information" from a menu, and then scroll through the other headers in a four line by 50 character window; but I have to do this for each message, one at a time, after they reach my inbox. There's no way to search for text in any of these headers, either.) Even if I save the messages to disk (by "exporting" them), I still get only those three headers. I can sort the list of messages in my inbox by sender or by date, but not by subject. So I usually just read everything in FIFO order, without even looking at the subject, hitting the delete key within a couple of seconds for any message that doesn't interest me. After finishing with all the messages, I use the extra tags in the Subject line to (visually) separate the messages I want to keep and move them into separate folders for each mailing list. I always leave the lkml messages till last, because without the extra tags I have to pay special attention to keep them separate from my regular (non-mailing-list) email. As far as I'm concerned, Notes is a lousy mail client. Very little can be configured by the user. The only option for quoted replies simply appends the entire message to the bottom of the reply. (I had to cut and paste your text and add the "" characters and the "Mike Harris wrote:" line manually.) I can't even set it to automatically forward my mail to my personal email account if I'm out of town. That requires a request to a Notes administrator to do it for me, and I have to ask him to change it back when I return. Plus, when the mail is auto-forwarded it is deleted from my Notes inbox, so if the administrator is slow about turning off auto-forwarding then I don't see any of my business email at work and have to wait until I can access my personal account from home. I haven't complained about any of this on the list until now, because I know I'm in the minority and I don't expect most people to care about my problems. But it bothered me seeing the criticism Mike Harrold has gotten for his request. Not everyone has problems because they're lazy. Some of us are boxed in by decisions that are beyond our control. For my part, if anyone can tell me a method (that doesn't require Notes administrator assistance) to get my mail, with headers intact, out of Notes and into elm or pine, I'd be ecstatic. Wayne - 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: spelling of disc (disk) in /devfs
To confuse things even more, I have a "Hewlett-Packard 9114 Disc Drive," which is really a 720K 3.5-inch diskette drive. Wayne "Michael B. Trausch" <[EMAIL PROTECTED]> on 01/31/2001 05:00:34 PM To: "Jeremy M. Dolan" <[EMAIL PROTECTED]> cc: Alan Chandler <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (bcc: Wayne Brown/Corporate/Altec) Subject: Re: spelling of disc (disk) in /devfs On Thu, 1 Feb 2001, Jeremy M. Dolan wrote: > > On Thu, 01 Feb 2001 00:19:56 +, Alan Chandler wrote: > > The thing that struck me most was the spelling of disc with a 'c'. As > > an Englishman this is the correct spelling for me most of the time, > > but I have come to accept "as a technical term" disk (as in American) > > is the right name for these devices. > > Disk is spelled 'disk' except for Compact Disc and Digital Versatile > Disc. If it wasn't 3:30 in the morning, a patch would be attached. > Anymore, even I refer to everything as discs, I used to be hardcore in establishing the difference between disks, discs, and diskettes. However, it's really useless, given that nobody even understands "diskette" in the general public when I say it, I wind up explaining it. - Mike === Michael B. Trausch[EMAIL PROTECTED] Avid Linux User since April, '96! AIM: ML100Smkr Contactable via IRC (DALNet) or AIM as ML100Smkr === - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: spelling of disc (disk) in /devfs
To confuse things even more, I have a "Hewlett-Packard 9114 Disc Drive," which is really a 720K 3.5-inch diskette drive. Wayne "Michael B. Trausch" [EMAIL PROTECTED] on 01/31/2001 05:00:34 PM To: "Jeremy M. Dolan" [EMAIL PROTECTED] cc: Alan Chandler [EMAIL PROTECTED], [EMAIL PROTECTED] (bcc: Wayne Brown/Corporate/Altec) Subject: Re: spelling of disc (disk) in /devfs On Thu, 1 Feb 2001, Jeremy M. Dolan wrote: On Thu, 01 Feb 2001 00:19:56 +, Alan Chandler wrote: The thing that struck me most was the spelling of disc with a 'c'. As an Englishman this is the correct spelling for me most of the time, but I have come to accept "as a technical term" disk (as in American) is the right name for these devices. Disk is spelled 'disk' except for Compact Disc and Digital Versatile Disc. If it wasn't 3:30 in the morning, a patch would be attached. Anymore, even I refer to everything as discs, I used to be hardcore in establishing the difference between disks, discs, and diskettes. However, it's really useless, given that nobody even understands "diskette" in the general public when I say it, I wind up explaining it. - Mike === Michael B. Trausch[EMAIL PROTECTED] Avid Linux User since April, '96! AIM: ML100Smkr Contactable via IRC (DALNet) or AIM as ML100Smkr === - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linmodem????
I haven't, and in fact keep a 2.2.14 kernel available (and in my lilo config) just so I can use the linmodem binary. It's a pain having to reboot when I want to use the modem, but it's the only solution I've found. Wayne Jeff Chua <[EMAIL PROTECTED]> on 01/15/2001 08:20:57 AM To: [EMAIL PROTECTED] cc: [EMAIL PROTECTED] (bcc: Wayne Brown/Corporate/Altec) Subject: linmodem Does anyone have any success in using Lucent winmodem under Linux 2.4.0? There's a binary at http://www.linmodems.org/linux568.zip but it only works under 2.2 Thanks, Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linmodem????
I haven't, and in fact keep a 2.2.14 kernel available (and in my lilo config) just so I can use the linmodem binary. It's a pain having to reboot when I want to use the modem, but it's the only solution I've found. Wayne Jeff Chua [EMAIL PROTECTED] on 01/15/2001 08:20:57 AM To: [EMAIL PROTECTED] cc: [EMAIL PROTECTED] (bcc: Wayne Brown/Corporate/Altec) Subject: linmodem Does anyone have any success in using Lucent winmodem under Linux 2.4.0? There's a binary at http://www.linmodems.org/linux568.zip but it only works under 2.2 Thanks, Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Change of policy for future 2.2 driver submissions
Cool! I remember reading about the --dry-run option in the patch man page once, and thinking it would be useful, but then I forgot all about it without ever using it. (Patch is one of those programs I've been using for so many years that my fingers type it automatically and I never think to check out other options.) Thanks for reminding me. I always rename my directories to the current patchlevel, too. But in this case it didn't help me, because I wasn't sure whether the prerelease-to-final was supposed to be applied to 2.4.0-prerelease INSTEAD OF prerelease-diff or IN ADDITION to it. (After all, -test1 through test-12 all had to be applied in order, but the various -testX-pre1, -pre2, etc. patches we've seen always had to be reversed before the next one could be applied.) Rather than take the time to investigate, I took a guess, and obviously guessed wrong about this one. :-) Wayne David Weinehall <[EMAIL PROTECTED]> on 01/08/2001 05:07:08 AM To: Wayne Brown/Corporate/Altec@Altec cc: Nick Holloway <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: Change of policy for future 2.2 driver submissions You know, there are reasons why patch has an option called --dry-run... bzcat patch-2.4.0.bz2 | patch -p1 --dry-run [and if everything goes well] bzcat patch-2.4.0.bz2 | patch -p1 [will be relatively painless, as the files will be cached by now...] Is the way I usually apply patches. Oh, and after applying a patch I always rename the directory to match the version of the patch. This way I always know if I have to unapply any pre-patches/test-patches/whatever. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
No Subject
Free speech means you can say anything you want, but it doesn't mean you can force anyone to listen. If I don't want to hear it, I can forbid you from coming into my house to tell me about it. I can configure my software to reject your messages if I don't want to see them. If I own a newsserver I can refuse to propagate your articles through it -- just as, if I owned a newspaper, I could refuse to print your "letters to the editor." In short, I can't stop you from saying whatever you want, but I don't have to listen, nor do I have to help you spread your message to anyone else. Matt Beland <[EMAIL PROTECTED]> on 01/07/2001 11:07:30 PM To: Dan Hollis <[EMAIL PROTECTED]>, Gregory Maxwell <[EMAIL PROTECTED]> cc: "Pedro M. Rodrigues" <[EMAIL PROTECTED]>, "John O'Donnell" <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (bcc: Wayne Brown/Corporate/Altec) Subject: Re: [OT] Re: [OT] Re: .br blacklisted ? On Sunday 07 January 2001 21:24, Dan Hollis wrote: > *This message was transferred with a trial version of CommuniGate(tm) Pro* > > On Sun, 7 Jan 2001, Gregory Maxwell wrote: > > You are suggesting that it is acceptable to implement technological > > barriers to a minority expressing speech that is unacceptable to the > > majority. This is not acceptable. > > See Rowan v. United States Post Office. > > *Your* right to free speech stops at *my* property. Does it now? How interesting. You can prohibit people from saying things you don't like. Hmmm. I suppose that could be useful. I don't like (just as an example) any speech from or about people named Dan. Please cease and desist immediately or I will blackhole you, your server, your domain, and everyone and everything associated with it until the people rise up and kill everyone named Dan, or as an acceptable compromise, remove their ability to speak and or type, or force them to change their names. That's my right, it's my property. Morally wrong? Bah. Your right to prattle on about morality stops at my property. Point 1: Laws mean jack squat in this case. The lawmakers know little about the internet, and until they learn, the laws they pass will continue to be irrelevant, confusing, or contradictory. Even when they aren't, no society has ever managed a foolproof "unjust law filter". The existence of a law does not make that law good, correct, or even legal; reference prohibition, slave ownership, women's sufferage or the lack thereof, and roughly 40% of the US Tax Code referencing income tax. Point 2: Either "information wants to be free", has no physical existence or worth, and cannot be controlled, or it has existense, worth, and can be controlled as property. You can't have it both ways; either Spam is an undesirable side effect of the free flow of information, or information is not free and can be controlled. Isn't it amazing how some of the people who are so quick to yell when Microsoft or Oracle or the government of infringes on their rights/privacy/information are the first to block the flow of information in the name of the same? > > Under no circumstances does your right to free speech trump the rights of > the unwilling recipient. Full Stop. End of story. > > -Dan > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
No Subject
Free speech means you can say anything you want, but it doesn't mean you can force anyone to listen. If I don't want to hear it, I can forbid you from coming into my house to tell me about it. I can configure my software to reject your messages if I don't want to see them. If I own a newsserver I can refuse to propagate your articles through it -- just as, if I owned a newspaper, I could refuse to print your "letters to the editor." In short, I can't stop you from saying whatever you want, but I don't have to listen, nor do I have to help you spread your message to anyone else. Matt Beland [EMAIL PROTECTED] on 01/07/2001 11:07:30 PM To: Dan Hollis [EMAIL PROTECTED], Gregory Maxwell [EMAIL PROTECTED] cc: "Pedro M. Rodrigues" [EMAIL PROTECTED], "John O'Donnell" [EMAIL PROTECTED], [EMAIL PROTECTED] (bcc: Wayne Brown/Corporate/Altec) Subject: Re: [OT] Re: [OT] Re: .br blacklisted ? On Sunday 07 January 2001 21:24, Dan Hollis wrote: *This message was transferred with a trial version of CommuniGate(tm) Pro* On Sun, 7 Jan 2001, Gregory Maxwell wrote: You are suggesting that it is acceptable to implement technological barriers to a minority expressing speech that is unacceptable to the majority. This is not acceptable. See Rowan v. United States Post Office. *Your* right to free speech stops at *my* property. Does it now? How interesting. You can prohibit people from saying things you don't like. Hmmm. I suppose that could be useful. I don't like (just as an example) any speech from or about people named Dan. Please cease and desist immediately or I will blackhole you, your server, your domain, and everyone and everything associated with it until the people rise up and kill everyone named Dan, or as an acceptable compromise, remove their ability to speak and or type, or force them to change their names. That's my right, it's my property. Morally wrong? Bah. Your right to prattle on about morality stops at my property. Point 1: Laws mean jack squat in this case. The lawmakers know little about the internet, and until they learn, the laws they pass will continue to be irrelevant, confusing, or contradictory. Even when they aren't, no society has ever managed a foolproof "unjust law filter". The existence of a law does not make that law good, correct, or even legal; reference prohibition, slave ownership, women's sufferage or the lack thereof, and roughly 40% of the US Tax Code referencing income tax. Point 2: Either "information wants to be free", has no physical existence or worth, and cannot be controlled, or it has existense, worth, and can be controlled as property. You can't have it both ways; either Spam is an undesirable side effect of the free flow of information, or information is not free and can be controlled. Isn't it amazing how some of the people who are so quick to yell when Microsoft or Oracle or the government of insert nation name here infringes on their rights/privacy/information are the first to block the flow of information in the name of the same? Under no circumstances does your right to free speech trump the rights of the unwilling recipient. Full Stop. End of story. -Dan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
