The patch did it --- that -p1. Something "simple" .. It was as I hoped,
although I burned a LOT of hours on it last night. The friggin patch
program bit me. Had to put in a -p0 or -p1. No one said that, and it
certainly isn't obvious that patch defaults to ignoring subdirectories when
it is writing but not when it is reading a file..??
Thanks for the help! Got it up. I suspect it will be reliable, but I'll
burn things in, pull wires, etc. to see what it does in the meantime. BTW,
I was able to apply 2.2.4 patches but not 2.2.5 patches on top of it, not
that it matters. Thanks again -- a bunch!!!! -- Joe B.
At 04:43 PM 4/13/99 +0300, you wrote:
>cd /usr/src
>tar zxf linux-2.2.3.tar.gz
>cd linux
>zcat ../raid0145-2.2.3-19990309.gz | patch -p1
>cd ..
>mv linux linux-2.2.3-raid0145-19990309
>ln -s linux-2.2.3-raid0145-19990309 linux
>cd linux
>make mrproper
>make menuconfig (...)
>make bzImage modules
>make install modules_install
>
>then make and install raidtools-0.90-19990309.
>
>Your problem probably was that you don't install the patch
>correctly. It's more than happy to create the raid driver files into a
>directory other than the one you actually want if you don't pay
>attention to the paths.
>
>Joe Beauchamp <[EMAIL PROTECTED]> writes:
>> OK, here it is from the get-go, I ln /usr/src/linux to a new area
>> linux-2.2.3, tar -xzf lin*2.3*z to create the area. This will build, etc.
>> Then apply patch raid*2.2.3 via "gzip -d <raid*2.2.3*z |patch" no complaint
>> -- seems successful, however, a build now causes main.c to not find
>> linux/raid/mh.d (which isn't there) and raid_setup is undeclared. I
>> wrestled with these a lot yesterday, patch things, fudging things -- spent
>> hours -- figured I must be really doing something wrong.
>>
>> How do I get this thing built? After the patch, things just aren't there.
>> For instance, a grep shows nothing useful about this new routine
>> raid_setup..??
>>
>> So, how do I apply the patches and have a buildable kernel afterward?
>> Thanks!!! -- Joe B.
>>
>> At 09:05 AM 4/13/99 +0300, you wrote:
>> >Joe Beauchamp <[EMAIL PROTECTED]> writes:
>> >> I built 2.2.5 (and 2.2.3, and 2.0.35 and 2.0.36) and am having no luck
>> >> getting started. With 2.2.5 (no kernel patches -- can't find any that
>> >> apply or can be applied -- in fact all patching of these kernels
failed for
>> >> me..??) So, what am I doing wrong? It must be something simple since I
>> >> haven't even started yet, right??? Thanks for all help and suggestions!
>> >
>> >Use 2.2.3 patched with raid0145-2.2.3-19990309 and
>> >raidtools-0.90-19990309. While 2.2.x kernels contain RAID0/1 code,
>> >it's a really, really old version, raidtools-0.90 won't work with it,
>> >and you're generally better off running the 0.90 code.
>> >
>> >Once you've managed that, here's the basic layout:
>> >1. figure out which partitions you want to run RAID on (the config
>> > you pasted made no sense, you get no benefit (the opposite,
>> > actually) from running RAID over two partitions on the same disk).
>> > Write the /etc/raidtab accordingly.
>> >2. fdisk your RAID disks but DO NOT set the partition types to 0xfd yet!
>> >3. reboot to kernel with recent RAID patches
>> >4. mkraid with your /etc/raidtab set up
>> >5. mkfs -t ext2 /dev/md0
>> >6. raidstop /dev/md0
>> >7. fdisk and set up the partition types to 0xfd
>> >8. raidstart /dev/md0, mount /dev/md0
>> >9. proceed with your new filesystem..
>> >
>> >the point is that sometimes mkraid fails if you've already set up the
>> >partitions to the 0xfd RAID-autostart type (and rebooted, at which
>> >point the kernel RAID code would have tried to autostart the devices).
>> >
>> >On the next reboot /dev/md0 will automatically activate (assuming you
>> >have the RAID support compiled into the kernel, and not as a
>> >module). You can even use it as the root filesystem as long as you
>> >load your kernel image from somewhere else.
>> >
>> >--
>> >Osma Ahvenlampi
>> >
>> >
>> ___________________________________________________________________
>> Joe Beauchamp -- CIO, Interactive Commerce Group -- (610) 768-1444
>
>
___________________________________________________________________
Joe Beauchamp -- CIO, Interactive Commerce Group -- (610) 768-1444
