| 1 |
Dale <rdalek1967@×××××.com> writes: |
| 2 |
|
| 3 |
> The problem I ran into when I copied the old way, cp |
| 4 |
> arch/i386/boot/bzImage /boot, that wasn't the kernel but was a link to |
| 5 |
> the kernel in the x86 directory tree. When I copied the link then the |
| 6 |
> link got broke and then it appeared red on my screen. I thought I was |
| 7 |
> going nuts for a bit. I hadn't heard anything about the kernel being |
| 8 |
> moved and it had been a while. I'm old and I do forget sometimes. |
| 9 |
|
| 10 |
Dale, from one old `f..t' to another.. here is a little tip I use |
| 11 |
dozens of ways to aid my sorry failing memory. |
| 12 |
|
| 13 |
In ~/.inputrc |
| 14 |
|
| 15 |
Something like (verbatim): |
| 16 |
|
| 17 |
"\M-f": "ls -l `find ./ -iname 'bzimage'`" |
| 18 |
|
| 19 |
after saving ~/.inputrc, type C-x C-r to make readline re-read |
| 20 |
it. |
| 21 |
|
| 22 |
Then anytime you press Atl-f readline will put that command on the |
| 23 |
cmdline for you. |
| 24 |
|
| 25 |
So inside /usr/src/linux, Alt-f <enter> will dig up bzimage and show |
| 26 |
any deceitful symlinks for what they are... hehe. |
| 27 |
|
| 28 |
May not be that useful .. at least until someone sneaks in and moves |
| 29 |
bzimage again, but I guess you can imagine the many ways putting |
| 30 |
things in .inputrc will free you from remembering stuff. |
Archives