ISA Memory hole at 15-16 MB
Hi! While I was going through the Linux Device Drivers book by Allessandro Rubini, I came to know that at the time of 286 computers, ISA memory was mapped between 15 and 16MB for RAM. Since at that time nobody had more than 1-2 MB of RAM, people had no problems accessing the ISA memory. But now, as everybody has around 64MB RAM, so when we access that memory between 15 and 16MB (the ISA memory hole), are we referring to physical RAM or to ISA card's memory? Where can I get more details on this? Thanks Regards, Abhishek Khaitan
Re: FAQ
Gregory Leblanc wrote: snip 2.4. How do I apply the patch to a kernel that I just downloaded from ftp.kernel.org? Put the downloaded kernel in /usr/src. Change to this directory, and move any directory called linux to something else. Then, type tar -Ixvf kernel-2.2.16.tar.bz2, replacing kernel-2.2.16.tar.bz2 with your kernel. Then cd to /usr/src/linux, and run patch -p1 raid-2.2.16-A0. Then compile the kernel as usual. My tar cannot use bz2-compressed unless used with --use-compress-program=bzip2. so that line sould probably read "bzcat kernel-2.2.16.tar.bz2 | tar xf -". Also the only tar I saw that knows bzip2 is slackware's and it uses the '-y' switch for that. I never saw the '-I' switch for tar and my 'info tar' does not list it. Bottomline: Your tar is too customized to be in a FAQ. Marc -- Marc Mutz [EMAIL PROTECTED]http://marc.mutz.com/Encryption-HOWTO/ University of Bielefeld, Dep. of Mathematics / Dep. of Physics PGP-keyID's: 0xd46ce9ab (RSA), 0x7ae55b9e (DSS/DH)
Re: FAQ
Marc Mutz wrote: My tar cannot use bz2-compressed unless used with --use-compress-program=bzip2. so that line sould probably read "bzcat kernel-2.2.16.tar.bz2 | tar xf -". Also the only tar I saw that knows bzip2 is slackware's and it uses the '-y' switch for that. I never saw the '-I' switch for tar and my 'info tar' does not list it. Bottomline: Your tar is too customized to be in a FAQ. How about both options? The tar that comes with RH6.2 does this just fine... Ed -- Edward Schernau,mailto:[EMAIL PROTECTED] Network Architect http://www.schernau.com RC5-64#: 243249 e-gold acct #:131897
Re: FAQ
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Marc , On Thu, 3 Aug 2000, Marc Mutz wrote: Gregory Leblanc wrote: snip 2.4. How do I apply the patch to a kernel that I just downloaded from ftp.kernel.org? Put the downloaded kernel in /usr/src. Change to this directory, and move any directory called linux to something else. Then, type tar -Ixvf kernel-2.2.16.tar.bz2, replacing kernel-2.2.16.tar.bz2 with your kernel. Then cd to /usr/src/linux, and run patch -p1 raid-2.2.16-A0. Then compile the kernel as usual. My tar cannot use bz2-compressed unless used with ...snip... Your tar is too customized to be in a FAQ. Unless you want to provide a URL: to the modified sources ? OR Just goto ftp.gnu.org grab the original stick to just "it's" available options . Just my unneeded opinion . JimL ++ | James W. Laferriere | System Techniques | Give me VMS | | NetworkEngineer | 25416 22nd So | Give me Linux | | [EMAIL PROTECTED] | DesMoines WA 98198 | only on AXP | ++ -BEGIN PGP SIGNATURE- Version: PGP 6.5.1i iQA/AwUBOYmfU9bsrYDRJjJBEQIx3QCgshT14eDujACAdVPKvrqLLWIKsbsAoPGk cIZjEZFNbygVQHJfqYBJNzMI =j3v9 -END PGP SIGNATURE-
Re: raid-2.2.17-A0 cleanup for LVM
On Aug 2, 7:12pm, Andrea Arcangeli wrote: } Subject: raid-2.2.17-A0 cleanup for LVM This patch cleanups the new raid code so that we have a chance that LVM on top of RAID will keep working. It's untested at the moment. ftp://ftp.*.kernel.org/pub/linux/kernel/people/andrea/patches/v2.2/2.2.17pre13/raid-2.2.17-A0/raid-lvm-cleanup-1 What are people using for LVM code on 2.2.1[67]? The only thing that I have found reliable was a port of the 8i stuff that a gentleman created which he said he was submitting to Heinz for approval. I had to couple this with the 2/10/1999 toolset in order to get a complete system. I have been using this in a limited production environment but considering the pathway to it I have been reluctant to really put the system under stress. The LVM code looks very promising and well-done and essential to those of us in production environments. There doesn't appear to be a clear path to follow for those of us working with late 2.2.x kernels. I tried merging the LVM patches that I am using with the 2.2.16 RAID patchset but there is a massive collision in ll_rw_blk.c file that doesn't appear to be straight forward in its resolution. Andrea Greg }-- End of excerpt from Andrea Arcangeli As always, Dr. G.W. Wettstein, Ph.D. Enjellic Systems Development, LLC. 4206 N. 19th Ave. Specializing in information infra-structure Fargo, ND 58102development. PH: 701-281-4950WWW: http://www.enjellic.com FAX: 701-281-3949 EMAIL: [EMAIL PROTECTED] -- "If you think nobody cares if you're alive, try missing a couple of car payments." -- Earl Wilson
Re: FAQ
[Marc Mutz] 2.4. How do I apply the patch to a kernel that I just downloaded from ftp.kernel.org? Put the downloaded kernel in /usr/src. Change to this directory, and move any directory called linux to something else. Then, type tar -Ixvf kernel-2.2.16.tar.bz2, replacing kernel-2.2.16.tar.bz2 with your kernel. Then cd to /usr/src/linux, and run patch -p1 raid-2.2.16-A0. Then compile the kernel as usual. Your tar is too customized to be in a FAQ. there is no bzip2 standard in gnu tar, so let's be intelligent and avoid the issue by going with the .gz tarball as a recommendation. -z is standard. Also, none of the tarballs will start with "kernel-" but "linux-" anyway, so that needs fixing. Also, I'd add "/path/to/" before the raid in the patch command, since otherwise we'd need to tell them to move the patch over to that directory (pedantic, yes, but still) oh, and "move any directory called linux to something else" seems to miss the possibility of a symlink, where renaming the symlink would be kind of pointless. Whether tar would just kill the symlink at extract time anyway is worth a check. -- James Manning [EMAIL PROTECTED] GPG Key fingerprint = B913 2FBD 14A9 CE18 B2B7 9C8E A0BF B026 EEBB F6E4
Re: raid-2.2.17-A0 cleanup for LVM
On Thu, 3 Aug 2000, G.W. Wettstein wrote: On Aug 2, 7:12pm, Andrea Arcangeli wrote: } Subject: raid-2.2.17-A0 cleanup for LVM This patch cleanups the new raid code so that we have a chance that LVM on top of RAID will keep working. It's untested at the moment. ftp://ftp.*.kernel.org/pub/linux/kernel/people/andrea/patches/v2.2/2.2.17pre13/raid-2.2.17-A0/raid-lvm-cleanup-1 What are people using for LVM code on 2.2.1[67]? Grab 2.2.15aa1 or 2.2.17pre11aa2, they have completly reliable LVM (I also switch between it and 2.4.x stock without changing anything). It can be used for production. You can find the separate patches that compose that kernel in the ftp site as well. Andrea
Re: ISA Memory hole at 15-16 MB
Abhishek Khaitan [EMAIL PROTECTED] writes: Hi! While I was going through the Linux Device Drivers book by Allessandro Rubini, I came to know that at the time of 286 computers, ISA memory was mapped between 15 and 16MB for RAM. Since at that time nobody had more than 1-2 MB of RAM, people had no problems accessing the ISA memory. But now, as everybody has around 64MB RAM, so when we access that memory between 15 and 16MB (the ISA memory hole), are we referring to physical RAM or to ISA card's memory? Where can I get more details on this? Abhishek, Nowaday BIOS'es have an option for this. If enabled, your RAM is reduced to 15 MB. Off is the default value, but I don't know how the ISA bus is adressed in this mode. Johannes Nieß
Re: FAQ
On Thu, Aug 03, 2000 at 01:34:33PM -0400, James Manning wrote: there is no bzip2 standard in gnu tar, so let's be intelligent and avoid the issue by going with the .gz tarball as a recommendation. -z is standard. from the info page from gnu tar 1.13.17: `--bzip2' `-I' This option tells `tar' to read or write archives through `bzip2'. -- Luca Berra -- [EMAIL PROTECTED] Communication Media Services S.r.l.
Re: raid-2.2.17-A0 cleanup for LVM
On Thu, Aug 03, 2000 at 07:55:18PM +0200, Andrea Arcangeli wrote: On Thu, 3 Aug 2000, G.W. Wettstein wrote: Grab 2.2.15aa1 or 2.2.17pre11aa2, they have completly reliable LVM (I also switch between it and 2.4.x stock without changing anything). It can be used for production. You can find the separate patches that compose that kernel in the ftp site as well. strange i was never able to run lvm on top ov raid with 2.4 the lvm tools just don't guess what an md device is :( L. -- Luca Berra -- [EMAIL PROTECTED] Communication Media Services S.r.l.
Re: FAQ
[Luca Berra] from the info page from gnu tar 1.13.17: `--bzip2' `-I' This option tells `tar' to read or write archives through `bzip2'. As mentioned previously, this is a distro-specific hack. I have it in my tar as well, but trusting it to be part of core GNU tar just because it works on your system is silly. version 1.13 is the latest at ftp://ftp.gnu.org/pub/gnu/tar/ and specifically mentions the bzip2 situation in its NEWS file: +++ * An interim GNU tar alpha had new --bzip2 and --ending-file options, but they have been removed to maintain compatibility with paxutils. Please try --use=bzip2 instead of --bzip2. +++ Checking the ChangeLog shows bzip2 support added 1999-02-01 (in the form of -y, --bzip2, and --bunzip2) and then removed 1999-06-16 In any case, it certainly is true that we can trust -z to be around on any standard Linux install, and as such it is the correct answer to this thread. -- James Manning [EMAIL PROTECTED] GPG Key fingerprint = B913 2FBD 14A9 CE18 B2B7 9C8E A0BF B026 EEBB F6E4
RE: FAQ
-Original Message- From: James Manning [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 03, 2000 10:35 AM To: [EMAIL PROTECTED] Subject: Re: FAQ [Marc Mutz] 2.4. How do I apply the patch to a kernel that I just downloaded from ftp.kernel.org? Put the downloaded kernel in /usr/src. Change to this directory, and move any directory called linux to something else. Then, type tar -Ixvf kernel-2.2.16.tar.bz2, replacing kernel-2.2.16.tar.bz2 with your kernel. Then cd to /usr/src/linux, and run patch -p1 raid-2.2.16-A0. Then compile the kernel as usual. Your tar is too customized to be in a FAQ. there is no bzip2 standard in gnu tar, so let's be intelligent and avoid the issue by going with the .gz tarball as a recommendation. -z is standard. It's going to be changed to the POSIX tar and GNU gzip invoked separately, because everybody felt the need to bitch, and because people aren't smart enough to not send me two copies of the message. :-) Also, none of the tarballs will start with "kernel-" but "linux-" anyway, so that needs fixing. Also, I'd add "/path/to/" before the raid in the patch command, since otherwise we'd need to tell them to move the patch over to that directory (pedantic, yes, but still) ok, cool, I'll fix those. oh, and "move any directory called linux to something else" seems to miss the possibility of a symlink, where renaming the symlink would be kind of pointless. Whether tar would just kill the symlink at extract time anyway is worth a check. Tar likes to clobber things when I give it half a chance. I'll mention about the symlink a bit more, although perhaps I should just tell people that they're expected to be familiar with downloading, unpacking, and building kernels before they read this document. Greg
RE: FAQ
Can;t we use bunzip2 instead of playing with tar? And after bunzip2, try tar -x kernel-2.2.16.tar ? -Original Message- From: James Manning [SMTP:[EMAIL PROTECTED]] Sent: Thursday, August 03, 2000 10:35 AM To: [EMAIL PROTECTED] Subject: Re: FAQ [Marc Mutz] 2.4. How do I apply the patch to a kernel that I just downloaded from ftp.kernel.org? Put the downloaded kernel in /usr/src. Change to this directory, and move any directory called linux to something else. Then, type tar -Ixvf kernel-2.2.16.tar.bz2, replacing kernel-2.2.16.tar.bz2 with your kernel. Then cd to /usr/src/linux, and run patch -p1 raid-2.2.16-A0. Then compile the kernel as usual. Your tar is too customized to be in a FAQ. there is no bzip2 standard in gnu tar, so let's be intelligent and avoid the issue by going with the .gz tarball as a recommendation. -z is standard. Also, none of the tarballs will start with "kernel-" but "linux-" anyway, so that needs fixing. Also, I'd add "/path/to/" before the raid in the patch command, since otherwise we'd need to tell them to move the patch over to that directory (pedantic, yes, but still) oh, and "move any directory called linux to something else" seems to miss the possibility of a symlink, where renaming the symlink would be kind of pointless. Whether tar would just kill the symlink at extract time anyway is worth a check. -- James Manning [EMAIL PROTECTED] GPG Key fingerprint = B913 2FBD 14A9 CE18 B2B7 9C8E A0BF B026 EEBB F6E4
