On Tuesday, January 25, 2022 7:43:10 AM EST Greg Wooledge wrote: > On Tue, Jan 25, 2022 at 09:12:52AM +0100, Urs Thuermann wrote: > > Greg Wooledge <g...@wooledge.org> writes: > > > On Mon, Jan 24, 2022 at 05:01:21AM -0500, gene heskett wrote: > > > > gene@coyote:~/Debian-arm/linux$ patch -p1 ../patches/*.patch > > > > > > That's not how you do it. patch(1) can only accept one patch at a > > > time, and it expects to see it on standard input. > > > > > > for p in ../patches/*.patch; do patch -p1 < "$p"; done > > > > You can even do the somewhat easier > > > > cat ../patches/*.patch | patch -p1 > > > > which will do the same. > > > > However, often the order of patches is important when some patch > > depends on another being applied before. Then *.patch will probably > > not work since it applies patches in alphabetical order. > > It will work if whoever distributed the patches has half a clue. Any > such individual will name the patches with a sortable prefix, like > 00- 01- 02- . Or *something* similar, so that the glob returns the > patches in the correct order. > > If this hasn't been done, then the end user would somehow have to > deduce the correct order in which to apply the patches. How an end > user would guess this is beyond me. > > . Now, now, all we have to do it learn how to use quilt. So sudo apt install quilt.
The man page isn't very explicit, other than giving you an ascii graphic of the directory tree it expects to run in. But does point you at the .pdf site, and after re-reading it several times and putting the directory full of unpacked patches where it wants it to be, it got simple. The secret is that the patches.xz file when unpacked, contains a "series" file as the whole archive was created by quilt in the first place. This file gives the order to apply them in. quilt push up arrow, hit return, does it one at a time in the correct order until its out of patches and complains, or from further reading quilt push -a would have done them all in the same order. But I wasn't that brave. So now the newest, bleeding edge kernel has been built, on the pi running uptodate buster, and I've written 2 cards with the raspios release image, edited both of those images to add a fallback net config to /etc/ dhcpdp.conf so I stand a small chance of having a working network on the first boot, and will hand carry those cards to my rpi4b and test them in the next hour or so. Theoretically, all _I_ should have to do once its booted is open a shell, and sudo mkdir /mnt/sdb1 sudu mount -text4 /dev/sdb1 /mnt/sdb1 cd to /mnt/sdb1/arm.src/apt-rt.stf/linux sudo make modules_install dtbs_install install look to see if it did. and then reboot the pi. In my case, and a reboot works, a uname -a should show a v5.16.3-rt kernel is running. Theoretically... But have a 12 gauge loaded with 00 buck handy in case that guy Murphy has snuck around and drunk your last beer. :-( Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
