Re: how to edit the kernel....make menuconfig???
On Sat, Mar 24, 2001 at 12:52:17PM -0800, Krzys Majewski wrote: > ktb <[EMAIL PROTECTED]> writes: > > > > If these Debian patches are so great, why aren't they in the official > > > kernel source? > > > > > > > Because the patches didn't exist when 2.2 was released. That is the > > nature of a patch. For the most part patches are created to fix > > bugs that were unknown when the original was released. > > OK, so these are official kernel.org patches then? Or something else? > Yes, official. > > > There's too many Unixes as it is, why have more than one Linux? > > > > > > > Unix/Linux is a tool. Do you use only one tool when fixing a car? No, you > > use the right tool for the right job. > > kent > > Hm, not sure I buy this comparison. When fixing a car it's usually > pretty clear whether you need an Allen key or a Philips screwdriver or > whatever. The choice between Redhat and Debian, or even the choice > between Solaris and GNU/Linux, is nowhere near this clear. I guess > Unix is like a toolbox, except there are many different brands of > tools and the various brands are only vaguely compatible with each > other. If only it were possible, as you suggest, to pick and choose > tools from various brands of toolboxes.. unfortunately, this doesn't > work: you wouldn't normally take a Solaris box and add the Debian > package manager to it, for example. > Things become much more clear after you have researched and used the various flavors. It is very clear to me why I use OpenBSD for firewalls and very clear to me why I use Debian instead of Redhat for my workstations. Just as clear as when I look at a screw and know I need an Allen wrench or a Philips screwdriver. Some of these reasons are technical, some are personal or more subjective. I did not suggest picking tools from various brands of toolboxes. I suggested picking the tool. OpenBSD is a good security "tool." Debian is a good workstation "tool." You say that it is 'unfortunate that you can't add the Debian package manager to Solaris.' This wish is partially why there are so many flavors of unix out there. People build a new distro of Linux because they feel that what is out there is less than what they want. Your very wish to "pick and choose tools from various brands of toolboxes" is what has created your frustration of wading through the various nuances of unix. kent -- From seeing and seeing the seeing has become so exhausted First line of "The Panther" - R. M. Rilke
Re: how to edit the kernel....make menuconfig???
Well, OK.. I guess *somebody* has to patch the kernels, so it may as well be the people who "sell" them, i.e. distribution "vendors" like Debian and RedHat.. as long as the patches aren't forking the kernel source tree, official or effective, I'm happy - chris On Sat, 24 Mar 2001, Shawn Yarbrough wrote: > Krzys Majewski wrote: > > > > OK, so these are official kernel.org patches then? Or something else? > > > > > Here is the README.Debian file from kernel-source-2.2.18pre21: > (yes it looks like somebody forgot to update the title) > > > kernel-source-2.2.17 for DEBIAN > --- > > These patches were appllied: > > * Big Physical Area (2.2.5) > > http://www.uni-paderborn.de/fachbereich/AG/heiss/linux/bigphysarea.html > > These modifications were also made: > > * Don't align the stack by 16 bytes on i386. > * Fixed a typo in tgafb.c. > * Added CONFIG_APM_DISABLE_BY_DEFAULT. > * Fixed a typo in aha152x.c. > * __asm__ fixes for egcs (hfmodem/refclock.c). > * Fixed a couple of argument processing bugs in main.c (Eric Delaunay). > * Added tulip.c from NetGear. > > Herbert Xu <[EMAIL PROTECTED]> > $Id: README.Debian,v 1.34 2000/11/18 02:14:23 herbert Exp $ >
Re: how to edit the kernel....make menuconfig???
Krzys Majewski wrote: > > OK, so these are official kernel.org patches then? Or something else? > Here is the README.Debian file from kernel-source-2.2.18pre21: (yes it looks like somebody forgot to update the title) kernel-source-2.2.17 for DEBIAN --- These patches were appllied: * Big Physical Area (2.2.5) http://www.uni-paderborn.de/fachbereich/AG/heiss/linux/bigphysarea.html These modifications were also made: * Don't align the stack by 16 bytes on i386. * Fixed a typo in tgafb.c. * Added CONFIG_APM_DISABLE_BY_DEFAULT. * Fixed a typo in aha152x.c. * __asm__ fixes for egcs (hfmodem/refclock.c). * Fixed a couple of argument processing bugs in main.c (Eric Delaunay). * Added tulip.c from NetGear. Herbert Xu <[EMAIL PROTECTED]> $Id: README.Debian,v 1.34 2000/11/18 02:14:23 herbert Exp $
Re: how to edit the kernel....make menuconfig???
ktb <[EMAIL PROTECTED]> writes: > > If these Debian patches are so great, why aren't they in the official > > kernel source? > > > > Because the patches didn't exist when 2.2 was released. That is the > nature of a patch. For the most part patches are created to fix > bugs that were unknown when the original was released. OK, so these are official kernel.org patches then? Or something else? > > There's too many Unixes as it is, why have more than one Linux? > > > > Unix/Linux is a tool. Do you use only one tool when fixing a car? No, you > use the right tool for the right job. > kent Hm, not sure I buy this comparison. When fixing a car it's usually pretty clear whether you need an Allen key or a Philips screwdriver or whatever. The choice between Redhat and Debian, or even the choice between Solaris and GNU/Linux, is nowhere near this clear. I guess Unix is like a toolbox, except there are many different brands of tools and the various brands are only vaguely compatible with each other. If only it were possible, as you suggest, to pick and choose tools from various brands of toolboxes.. unfortunately, this doesn't work: you wouldn't normally take a Solaris box and add the Debian package manager to it, for example. My main problem with software, and especially free software, is that there's too *much* choice -- which suggests to me that none of options are really very good. Sort of like, say, Christianity: there are hundreds of different flavours, they all claim to be The Right One, and they all disagree with each other. (This argument doesn't necessarily hold in reverse: for example, there is only one Microsoft Windows, and yet public opinion suggests it's far from perfect.) With software, I'm hoping this is something that will improve over time. For example, if you type 'ls' at a Solaris box and a GNU/Linux box, you can expect to get the same result. Presumably this is because 'ls' has been around for 30 years, and has more or less stabilized. Some things have not stabilized yet: 'tar', for example, will give different results on Solaris and GNU/Linux. The Linux kernel is a tool that is good for one particular job: running a Unix workstation. (It is not so good for other jobs, like real-time heart monitoring, for example.) For all I know, the Debian kernel patches may be a A Good Thing (TM). The reason I bristled at the idea, in my previous post, is this: the Linux kernel strikes me as a Good Tool (TM), and I like to see Good Tools standardize, rather than fork into many competing flavours. I like to be able to compile my Linux kernel and my friend's Linux kernel, and get that same warm fuzzy compatibility feeling that I get from typing 'ls' on different kinds of Unix boxes. *That's* security. Forget about protecting your box from imaginary teenage hackers. The real threat is in the form of legions of benevolent programmers, wielding the power to make your computer forever incompatible with anybody else's. -chris
Re: how to edit the kernel....make menuconfig???
On Sat, Mar 24, 2001 at 08:53:46AM -0800, Krzys Majewski wrote: > On Sat, 24 Mar 2001, Shawn Yarbrough wrote: > > > Use the 'kernel-source' packages and you will get extra features and > > bugfixes patched in by Debian which are not in stock Linux. For example > > 'kernel-source-2.2.18pre21'. When installed the archive gets put into > > Is this anything like RedHat's customized kernels? My experience with > those was that the headers were broken in a subtle but deep way, > so that third-party kernel module source, for example, would not > compile. > No. > If these Debian patches are so great, why aren't they in the official > kernel source? > Because the patches didn't exist when 2.2 was released. That is the nature of a patch. For the most part patches are created to fix bugs that were unknown when the original was released. > There's too many Unixes as it is, why have more than one Linux? > Unix/Linux is a tool. Do you use only one tool when fixing a car? No, you use the right tool for the right job. kent -- From seeing and seeing the seeing has become so exhausted First line of "The Panther" - R. M. Rilke
Re: how to edit the kernel....make menuconfig???
On Sat, 24 Mar 2001, Shawn Yarbrough wrote: > Use the 'kernel-source' packages and you will get extra features and > bugfixes patched in by Debian which are not in stock Linux. For example > 'kernel-source-2.2.18pre21'. When installed the archive gets put into Is this anything like RedHat's customized kernels? My experience with those was that the headers were broken in a subtle but deep way, so that third-party kernel module source, for example, would not compile. If these Debian patches are so great, why aren't they in the official kernel source? There's too many Unixes as it is, why have more than one Linux? -chris
Re: how to edit the kernel....make menuconfig???
Krzys Majewski wrote: > > There is an official debian way to recompile kernels, but I don't > bother.. download the kernel source from debian.org or kernel.org Use the 'kernel-source' packages and you will get extra features and bugfixes patched in by Debian which are not in stock Linux. For example 'kernel-source-2.2.18pre21'. When installed the archive gets put into '/usr/src/'. You must 'bunzip2' it and 'tar xvf' it before you can finally cd to the Linux source tree. At that point you can do the 'make' commands you listed. Or you can try the 'kernel-package' package which has some nice features. It does the build commands for you plus it builds a nice .deb package in '/usr/src' containing your kernel, any modules compiled for your kernel, and installation scripts. But if you do use 'kernel-package' be sure to 'zless /usr/doc/kernel-package/README.gz' and search on 'Brave' for instructions. Ignore the 'kernel-package' man pages which are useless for beginners. Shawn Yarbrough [EMAIL PROTECTED] Krzys Majewski wrote: > > There is an official debian way to recompile kernels, but I don't > bother.. download the kernel source from debian.org or kernel.org > (avoid minor versions which are not divisible by 2, like 2.1.* or > 2.3.*) read the README in /usr/src/linux, and you're go. Basically > > make menuconfig > make dep > make clean > make bzImage > make modules > make modules_install > # run lilo > # reboot > > -chris > > "Mike Egglestone" <[EMAIL PROTECTED]> writes: > > > Hi all... > > > > I'm having a tough time finding info on how to > > edit the kernel so I can add "transparent_proxy" support. > > Isn't there some utility to do this? > > I'm running potato > > If someone could help me out.. that would be great!! > > > > Thanks > > Mike > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how to edit the kernel....make menuconfig???
There is an official debian way to recompile kernels, but I don't bother.. download the kernel source from debian.org or kernel.org (avoid minor versions which are not divisible by 2, like 2.1.* or 2.3.*) read the README in /usr/src/linux, and you're go. Basically make menuconfig make dep make clean make bzImage make modules make modules_install # run lilo # reboot -chris "Mike Egglestone" <[EMAIL PROTECTED]> writes: > Hi all... > > I'm having a tough time finding info on how to > edit the kernel so I can add "transparent_proxy" support. > Isn't there some utility to do this? > I'm running potato > If someone could help me out.. that would be great!! > > Thanks > Mike > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how to edit the kernel....make menuconfig???
From: Mike Egglestone <[EMAIL PROTECTED]> > I'm having a tough time finding info on how to > edit the kernel so I can add "transparent_proxy" support. > Isn't there some utility to do this? You want to recompile the kernel with transparent_proxy? If so, see http://www.chowells.uklinux.net/files/kernel.shtml. Chris Howells
