Stripping kernel/uboot source to 10% for code reading
baohaojun.github.io
Stripping kernel/uboot source to 10% for code reading
1–10 of 15 posts
Re: Stripping kernel/uboot source to 10% for code reading
#2[deleted]
Re: Stripping kernel/uboot source to 10% for code reading
#3> git ls-tree HEAD -r |pn 4|xargs touch
What's pn? I've never heard of it, I don't have it, and simple searches don't tell me anything about it. It looks like it might be a simple replacement for awk argument parsing, but I'm unsure...
Re: Stripping kernel/uboot source to 10% for code reading
#4I do love me some strace. It's one of those commands I talk about when asked why I prefer Linux as a developer/hacker.
Re: Stripping kernel/uboot source to 10% for code reading
#5I do love me some strace. It's one of those commands I talk about when asked why I prefer Linux as a developer/hacker.
Do you mean you prefer Linux over Windows?
If so, then watch this talk: http://www.youtube.com/watch?v=TgmA48fILq8
Now you will prefer Solaris/BSD to Linux :)
Re: Stripping kernel/uboot source to 10% for code reading
#6> git ls-tree HEAD -r |pn 4|xargs touch What's pn? I've never heard of it, I don't have it, and simple searches don't tell me anything about it. It looks like it might be a simple replacement for awk argument parsing, but I'm unsure...
Good question! Since they have such a comprehensive archive I searched Debian, but it's not there.
Re: Stripping kernel/uboot source to 10% for code reading
#7> git ls-tree HEAD -r |pn 4|xargs touch What's pn? I've never heard of it, I don't have it, and simple searches don't tell me anything about it. It looks like it might be a simple replacement for awk argument parsing, but I'm unsure...
I think it's along the lines of::
cut -d' ' -F 4
git ls-tree HEAD -r | sed 's/[[:space:]]\+/ /g' | cut -d' ' -f 4
git ls-tree HEAD -r | tr -s ' ' | cut -d' ' -f 4Re: Stripping kernel/uboot source to 10% for code reading
#8I do love me some strace. It's one of those commands I talk about when asked why I prefer Linux as a developer/hacker.
Do you mean you prefer Linux over Windows? If so, then watch this talk: http://www.youtube.com/watch?v=TgmA48fILq8 Now you will prefer Solaris/BSD to Linux :)
Cool thanks!
Edit: I'm listening to it now and it's excellent.
Re: Stripping kernel/uboot source to 10% for code reading
#9> touch all source code files (this step is mandatory, or else the atime won't update correctly, I don't know why, but guess it's an optimization).
On a filesystem mounted with the "relatime" option, it's necessary to touch each file so that the next access is guaranteed to bump the atime.
It used to be common to update the access time every time a file was accessed. That turned every read into a read+write, which is expensive. Linux filesystems are now commonly mounted with either the "relatime" or "noatime" options. "noatime" does what you'd expect. "relatime" is a compromise. It updates the atime on access only if it's the same as the mtime -- in other words, only once after a write. I think some mail or news readers consider a message to be read only if atime > mtime. They won't work right with "noatime".
http://serverfault.com/questions/47466/drawbacks-of-mounting...
Re: Stripping kernel/uboot source to 10% for code reading
#10"For e.g." -> just e.g.