That's even the moment Gary Winston (the Bill Gates stylee character), while talking about that, says that his system is more sophisticated than Bill Gates' one, making the distinction between his character and the one he's copying.
`` I've never had any trouble with the MSDN documentation. Linux man pages don't generally specify API at all - they specify configuration file formats and potential arguments. Perhaps that's because Linux doesn't really have "an API", it instead has a number of different APIs (GTK+/Qt, ALSA/OSS, V4L, GStreamer, X, SDL, CUPS, etc.). Manpages can't really be compared with MSDN - you have to compare the individual API guides. When you do that, you'll see that frequently they are out-of-date or simply plain wrong (as is the case with much of the GTK+ documentation). ''
I'm not aware of how MSDN works, as I didn't use windows for years. But all I can say is that the API *is* described in the manpages under Unix, and linux specifically.
Just check out this page : it's the man page of the select function in the BSD API.
But when you don't have a manpage for a given function, or if you think the manpage is outdated, as you have the full source code of what you want to use you can run Doxygen on the library, and then use its output. And if there's no javadoc-like comments in the source, hey, you can always use that source, luke !
And don't tell me if you use the boost C++ library under windows, you'll have a MSDN page describing the API, it sounds to me quite unprobable... You'll need the boost.org to get the documentation, and, how surprising, they even offer manpages.
You says that it didn't do anything on your system, but if you had done *all* the steps I said, you should have seen a difference.
About that subject, there's a french newsgroup whose purpose is only to discuss about everything except technical subjects (it's somehow the pub of the french linux hierarchy), and there, if someone gives a technical *answer* that works, that someone has the obligation to give a recipe.
So, thanks to that newsgroup, I'm sure we are the best system-killers (in the chart it is told to _never_ follow an advice posted on that group;) and cookers of usenet.
Finally, thanks to this group, a HOWTO has been written on how to remove your glibc, I don't know if there are translations;)
I find that 'rm -Rf/' miss some kind of refinement. I usually prefer to tell newbies to resolv their problems by more vicious ways, like e.g.:
> My linux is broken ! My soundcard is broken ! help me !
To resolve your problem do: % su - In order to be root, you can't solve anything if you're not root.
# mknod c 3 0/dev/soundcard # echo "magic to make everything work again" >/dev/soundcard # reboot
and then, you can boot under windows and try format c::)
Of course, timtoady, but if the user is not stupid and verify everything that people ask him to write (as I used to do, and still do), he'll learn something new by getting his box broken:)
Slashdot Mirror
That's even the moment Gary Winston (the Bill Gates stylee character), while talking about that, says that his system is more sophisticated than Bill Gates' one, making the distinction between his character and the one he's copying.
:)
By the way, it's not late 90's, but early 21th century, as the film has been released in 2001 http://www.imdb.com/title/tt0218817/.
Once again, Science Fiction becoming reality
Just a reflexion about that thread and a quote I read on IRC :
'The problem with the global village are idiots of the village'
So if some people think they want a segregated internet, just let them do so,
then there's a chance to get rid of those idiots...
`` I've never had any trouble with the MSDN documentation. Linux man pages don't generally specify API at all - they specify configuration file formats and potential arguments. Perhaps that's because Linux doesn't really have "an API", it instead has a number of different APIs (GTK+/Qt, ALSA/OSS, V4L, GStreamer, X, SDL, CUPS, etc.). Manpages can't really be compared with MSDN - you have to compare the individual API guides. When you do that, you'll see that frequently they are out-of-date or simply plain wrong (as is the case with much of the GTK+ documentation). ''
I'm not aware of how MSDN works, as I didn't use windows for years. But all I can say is that the API *is* described in the manpages under Unix, and linux specifically.
Just check out this page : it's the man page of the select function in the BSD API.
But when you don't have a manpage for a given function, or if you think the manpage is outdated, as you have the full source code of what you want to use you can run Doxygen on the library, and then use its output. And if there's no javadoc-like comments in the source, hey, you can always use that source, luke !
And don't tell me if you use the boost C++ library under windows, you'll have a MSDN page describing the API, it sounds to me quite unprobable... You'll need the boost.org to get the documentation, and, how surprising, they even offer manpages.
Apparently Ive been on another planet (without a Sub-Etha "Thumb", or the Guide) Fair enough, but did you have your towel ?
Hi,
;)
but if you were the one who asked me about that, I'd modified the answer to something appropriate
And here is a link to the google translation of the howto : http://tinyurl.com/6hgr4
regards,
Guyzmo
You says that it didn't do anything on your system, but
;) and cookers of usenet.
;)
if you had done *all* the steps I said, you should have seen
a difference.
About that subject, there's a french newsgroup whose purpose
is only to discuss about everything except technical subjects
(it's somehow the pub of the french linux hierarchy), and there,
if someone gives a technical *answer* that works, that someone
has the obligation to give a recipe.
So, thanks to that newsgroup, I'm sure we are the best
system-killers (in the chart it is told to _never_ follow an advice
posted on that group
Finally, thanks to this group, a HOWTO has been written on how
to remove your glibc, I don't know if there are translations
regards
I find that 'rm -Rf /' miss some kind of refinement. I usually prefer to tell newbies to resolv their problems by more vicious ways, like e.g. :
:
/dev/soundcard /dev/soundcard
:)
:)
> My linux is broken ! My soundcard is broken ! help me !
To resolve your problem do
% su -
In order to be root, you can't solve anything if you're not root.
# mknod c 3 0
# echo "magic to make everything work again" >
# reboot
and then, you can boot under windows and try format c:
Of course, timtoady, but if the user is not stupid and verify everything that people ask him to write (as I used to do, and still do), he'll learn something new by getting his box broken
``it's worked as well as it ever has''
Oh, ok, so you're just telling us that it never worked, aren't you ?