A Bit of A Puzzlement

The Doctor did, indeed, make it in late yesterday evening, just as I was beginning to move forward with actually trying to use the toolchain I have spent the last few days creating.

---

Synopsis:  A bit of a puzzlement occurred during an attempt to execute a sed command to supposedly suppress the installation of header files into /usr/include/scsi in preparation for exposing the Linux kernel's API to Glibc, the system's C library.  (We're working in Section 6.7 of the documentation.)

---

At this point, I had plowed through the first six sections of Chapter 6, where all the preparations are made for installing the basic system software, when I got to Section 6.7.  The synopsis already states the problem well enough, so I won't repeat that here except to give the command in question and the error it throws:

root:/$ sed -i '/scsi/d' include/Kbuild

root:/$ sed: can't read include/Kbuild: No such file or directory

Evidently I've missed something, so back through the whole thing I go again, rebooting the system, and doing everything except building the toolchain again (because it's already there).

It's worth noting that in the issuance of the above command, I was logged in as root into a chroot environment per the settings in Section 6.4, and had gone through all the preparations from Chapter 4 in general except as already mentioned.

Meanwhile, the Doctor, now peering over my shoulder as I try this command again with the same results opines, "You've got to be in the wrong directory or missing a symlink."  Genius.

If I knew more about how sed is supposed to work and what it is supposed to be doing here, and if I could shake that feeling that I've missed some trivial detail in Chapter Six (possibly in Section 6.3 dealing with package management, which is [as far as I can tell] apropos of exactly nothing here), I'd feel a good bit better.  Time to hit the books some more and figure this out.

I'm afraid this is one of those learning experiences the Doctor is only too happy to let me have now and then.  It may be a while before further progress is made.

A Late Note:  What a lost goose I've been!  It turns out I was supposed to follow the instructions for building each package in similar fashion to that of Chapter 5, and cd into the build directory before attempting this little substitution!   Onward!