1) Topics covering the middle ground between Unix OS (Administration/Internals) books and Unix Programming books.
I would like to see a book in the line of 'Advanced Programming in the Unix Environment' that would document ld and ar and nm usages, for example, when and why do you use 'ld' to specify runtime search directories, or how do you use shared object versioning effectively. What does all of the output from 'nm' really mean. I think it could also go into the elf object format (perhaps others too). I would also like it to go into the specializations required for shared objects, covering topics such as implicit dependency etc. Dynamic loading is another topic that often falls through the cracks.
2) Automake/Autoconf/libtool
It would be really nice if these tools had some nice documentation on how to use them effectively for complex projects. It should probably contain an introduction to m4 macros. I have used these tools on a few projects and written some custom tests, but I don't know enough about them to fully utilize their capabilities. The best doc I have found on the subject is a book in progress called 'Developing software with GNU' by Eleftherios Gkioulekas. It is a good introduction/tutorial, but not completed. I would like to see an in depth reference work done on these tools.
Wouldn't having the trade mark used as the name fo an IETF standard dilute the mark? Doesn't the fact that the protocol has become so popular and that there are multiple implementations of it prove and that the ssh protocol is possibly refered to more than the ssh product establish dilution?
A software liscense grants users the right to use a piece of software in a specified manner. Once granted it can't be taken away. There is no way to remove the rights a person has already been granted by the copyright holder. Subsequent releases need not be released under the same terms. A case in point is the 'commercialization' of UNIX by AT&T. All prior work remained in the public domain and became BSD unix.
I have never been a mac person, so while knowing who woz was, I never knew much more about the man. After seeing the movie (I've not seen any mention of notable innacuracies with regards to Woz.) I am rather impressed. I'm only posting out of respect but *gratitude* as well. Wow!
We have here a guy who actually had in hand 'all the money'. Someone who had in fact 'made it'. What did he do? Distributed it among the deserving by sharing his stock with those original employees who had no stocks at all. Wether or not he said it, the line from the movie 'I don't think rich' impressed me. And, wether it was said or not, Woz walked the talk.
I think to myself, if woz had made an amount like what bill has made, I would have no problem with it. I would feel good about contributing to a fortune founded on integrity. That is what our economy is supposed to be about. Value, inginuity, integrity.
To woz himself, I would say, "Thank you, and well done. Your work has put all of us in a place farther along than we would have otherwise been. Kudos.
CmdrTaco for president!
on
Quickielanche
·
· Score: 1
Or . . . Jesse, as soon as he is done here in Minnesota.
Slashdot Mirror
sed 's/^echo/#echo/' /etc/inetd.conf >/etc/inetd.new /etc/inetd.new /etc/inetd.conf
mv
kill -HUP $(ps -ef |grep root.*inetd|grep -v grep|awk '{print $2}')
no more echo
1) Topics covering the middle ground between Unix OS (Administration/Internals) books and Unix Programming books.
I would like to see a book in the line of 'Advanced Programming in the Unix Environment' that would document ld and ar and nm usages, for example, when and why do you use 'ld' to specify runtime search directories, or how do you use shared object versioning effectively. What does all of the output from 'nm' really mean. I think it could also go into the elf object format (perhaps others too). I would also like it to go into the specializations required for shared objects, covering topics such as implicit dependency etc. Dynamic loading is another topic that often falls through the cracks.
2) Automake/Autoconf/libtool
It would be really nice if these tools had some nice documentation on how to use them effectively for complex projects. It should probably contain an introduction to m4 macros. I have used these tools on a few projects and written some custom tests, but I don't know enough about them to fully utilize their capabilities. The best doc I have found on the subject is a book in progress called 'Developing software with GNU' by Eleftherios Gkioulekas. It is a good introduction/tutorial, but not completed. I would like to see an in depth reference work done on these tools.
How is this different than an Xbox?
Um, so Ted is the largest *private* land owner, what corporations are included in the group of *private* land owners?
Wouldn't having the trade mark used as the name fo an IETF standard dilute the mark? Doesn't the fact that the protocol has become so popular and that there are multiple implementations of it prove and that the ssh protocol is possibly refered to more than the ssh product establish dilution?
Read the other articles, there was a man named Sellers who was held on a million dollars for misdemeanor charges.
for a portable unit check out
http://www.mambox.com/products.htm. There is also the CD/DVD/VCD/MP3 player posted a while ago. The Apex AD600A. Check out http://64.45.6.252/apex/.
A software liscense grants users the right to use a piece of software in a specified manner. Once granted it can't be taken away. There is no way to remove the rights a person has already been granted by the copyright holder. Subsequent releases need not be released under the same terms. A case in point is the 'commercialization' of UNIX by AT&T. All prior work remained in the public domain and became BSD unix.
Phone, phone . . . real hackers don't have phones, they are way too analogue
I have never been a mac person, so while knowing who woz was, I never knew much more about the man. After seeing the movie (I've not seen any mention of notable innacuracies with regards to Woz.) I am rather impressed. I'm only posting out of respect but *gratitude* as well. Wow!
We have here a guy who actually had in hand 'all the money'. Someone who had in fact 'made it'. What did he do? Distributed it among the deserving by sharing his stock with those original employees who had no stocks at all. Wether or not he said it, the line from the movie 'I don't think rich' impressed me. And, wether it was said or not, Woz walked the talk.
I think to myself, if woz had made an amount like what bill has made, I would have no problem with it. I would feel good about contributing to a fortune founded on integrity. That is what our economy is supposed to be about. Value, inginuity, integrity.
To woz himself, I would say, "Thank you, and well done. Your work has put all of us in a place farther along than we would have otherwise been. Kudos.
Or . . . Jesse, as soon as he is done here in Minnesota.