>> OK. I still don't think you need any tmp files. If it were me
>> doing it, i'd 1) mark all .o's executable to start. 2) unmark them
>> executable as I copy them. 3) fill misc with the .o's still
>> executable at the end.
> This doesn't work if your kernel tree is read-only. Which'd screw
> me because that's how I distribute kernels. The 'slave'
> workstations just mount my development tree by NFS and run 'make
> modules_install'
How about something along the following lines, with syntax that
assumes the bash shell is in use, and is based on a method I use
extensively in my shell scripts:
1. Initialise an environment variable to contain a list of all
available modules:
TODO="`find . -name '*.o' -type f`"
2. Process modules, and as we allocate them to directories, remove
their names from the contents of the said environment variable:
TODO="`echo $DONE | tr ' ' '\n' | fgrep -v $MODULE`"
3. When we've finished, deal with the remaining modules:
cp -v $TODO /lib/modules/$VERSION/misc/
That should remove any requirement for temporary files.
Best wishes from Riley.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/