Quote:
Originally Posted by knc1
It is really strange that something can give a person of your experience so much trouble.
Your the teacher, not the student.
Could you make a copy of the file system and post it somewhere I could grab a copy?
If you don't have a private place to post it handy, PM me the public key of an ssh key-pair and I'll setup a sftp location for you to push it to on one of my servers.
I don't have a K1, but maybe I can learn from the file system what might be causing you so much trouble.
|
Just poking around in the dark. I have often had problems with missing libraries and depedencies when building linux stuff -- I spend too much time in Windows, and doing win32 development. I am somewhat proficient in bash using very basic linux tools, and I have some (linux 2.4) kernel module experience, but building larger linux things from scratch has always been a difficult challenge. Some linuxish things just have not "clicked" for me -- I am still waiting for that "aha!" moment. I have had struggles like this many times over the years (often with eventual success) -- I just did not publish anything about them. What I am doing here now (letting folks look over my shoulder as I do battle with "
unknown unknowns") -- that is a new thing...
I can grab K1 dirs as tarballs, but I have had little success imaging the (useful) partitions. Though I have recently read how the firmware updates build the partitions by sending "cookies" (magic numbers) to the "BL" flash drivers. When partitions are unlocked with those magic cookies, then 'dd' can access them, but some cookies can be very destructive so I am yet wary of that, and it is still not sure what all of them are yet. I just discovered that one of them is the "recovery-kernel".
Poking around is slow and tedious with no terminal support -- I really need to find a 0.5mm ribbon cable so I can connect to the serial port (or order some on ebay and wait a month)...