![]() Stephen's posting is purely factual and also suggests a lot about his personality. It took longer than expected, but finally Microsoft decided to do the right thing and release the drivers. Since Novell has a (too) close association with Microsoft, my expectation was that Greg could prod the right people to get the issue resolved. ![]() Rather than creating noise, my goal was to resolve the problem, so I turned to Greg Kroah-Hartman. The GPL does not permit mixing of closed and open source parts, so this was an obvious violation of the license. The driver had both open-source components which were under GPL, and statically linked to several binary parts. A little googling found the necessary drivers, but on closer examination there was a problem. This saga started when one of the user's on the Vyatta forum inquired about supporting Hyper-V network driver in the Vyatta kernel. It turns out that Stephen was the one who got this whole thing moving. On Monday, after seeing Greg Kroah-Hartman's posting to the Linux kernel mailing list announcing that Microsoft had opened its Hyper-V drivers, Stephen Hemminger, a principle engineer here at Vyatta, created a blog post that provided a little background for what happened. In this post, I'll try to set the record straight. For the past few days, we have remained largely silent, but in the last 24-hours or so, news stories have started to circulate that have bordered on putting words into the mouths of both Vyatta and its employees. Unexpectedly, Vyatta found itself in the middle of this story. That was big news, and all this week the open source community and tech-industry as a whole have been trying to fully process it. In this case, if there are no files matching the glob *.txt, then Bash does not pass any filename to AWK.This week, Microsoft announced that it would be releasing the optimized virtualization drivers for Hyper-V under the GPLv2 license and had submitted them for inclusion into the mainline Linux kernel tree. You can prevent this common problem by enabling glob extension verification: shopt -s nullglob txt file in the current directory and Bash uses *.txt as the filename passed to AWK. If the error message is: awk: fatal: cannot open file `*.txt' for reading (No such file or directory) ![]() ![]() So, you should use "$f" in your for loop, and if it still doesn't work, the error must be somewhere else. "$f": works in any case and is the only right way to dereference (i.e.In general avoid by all means dereferencing a variable without enclosing it in double quotes. $f: works, if the filenames contain no whitespace characters, no globbing characters (such as * and ?), and no other expandable characters (such as ~).'$f': clearly doesn't work, because the single quotes prevent the variable substitution, and you literally pass $f as a filename to AWK.%f: clearly doesn't work, because % is not a Bash operator at all, and you literally pass %f as a filename to AWK.Regarding your proposed options for the variable f: txt files with AWK, you can do: awk '.' *.txt
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |