<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article10_01_18_0257232</id>
	<title>Next Linux Kernel Due Early March</title>
	<author>timothy</author>
	<datestamp>1263840000000</datestamp>
	<htmltext>swandives writes <i>"The Linux.conf.au is in full-swing in Wellington, New Zealand, and Computerworld Australia has an <a href="http://www.computerworld.com.au/article/332802/linux\_conf\_au\_latest\_linux\_kernel\_release\_due\_early\_march/">interview with Jon Corbet</a> in the leadup to his Kernel Report. The latest kernel release is due early March and will include reversed-engineered drivers for Nvidia chipsets."</i></htmltext>
<tokenext>swandives writes " The Linux.conf.au is in full-swing in Wellington , New Zealand , and Computerworld Australia has an interview with Jon Corbet in the leadup to his Kernel Report .
The latest kernel release is due early March and will include reversed-engineered drivers for Nvidia chipsets .
"</tokentext>
<sentencetext>swandives writes "The Linux.conf.au is in full-swing in Wellington, New Zealand, and Computerworld Australia has an interview with Jon Corbet in the leadup to his Kernel Report.
The latest kernel release is due early March and will include reversed-engineered drivers for Nvidia chipsets.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805484</id>
	<title>Re:huh?</title>
	<author>Anonymous</author>
	<datestamp>1263847800000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Yes, and?  NZ is just an island of the continent of Australia.  It'd be like having a Linux North America conference in Canada, or Hawaii.  mmm.. Hawaii.</p></htmltext>
<tokenext>Yes , and ?
NZ is just an island of the continent of Australia .
It 'd be like having a Linux North America conference in Canada , or Hawaii .
mmm.. Hawaii .</tokentext>
<sentencetext>Yes, and?
NZ is just an island of the continent of Australia.
It'd be like having a Linux North America conference in Canada, or Hawaii.
mmm.. Hawaii.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805318</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805214</id>
	<title>Early march?</title>
	<author>Anonymous</author>
	<datestamp>1263757440000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I expect it mid-February.</p></htmltext>
<tokenext>I expect it mid-February .</tokentext>
<sentencetext>I expect it mid-February.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805704</id>
	<title>Re:huh?</title>
	<author>dakameleon</author>
	<datestamp>1263808620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Except it's more like Linux.conf.us being held in Cuba. Just a little bit wrong.</p></htmltext>
<tokenext>Except it 's more like Linux.conf.us being held in Cuba .
Just a little bit wrong .</tokentext>
<sentencetext>Except it's more like Linux.conf.us being held in Cuba.
Just a little bit wrong.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805484</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805718</id>
	<title>Re:huh?</title>
	<author>Anonymous</author>
	<datestamp>1263808920000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>The only time I want to go to the linux conference, they move it a two hour flight away to new zealand. </p><p>what the fuck idiot decides to have it there? </p><p>There is nothing in new zealand at least Australia has women and nice clubs for after. All new zealand has is rubber boots.</p></htmltext>
<tokenext>The only time I want to go to the linux conference , they move it a two hour flight away to new zealand .
what the fuck idiot decides to have it there ?
There is nothing in new zealand at least Australia has women and nice clubs for after .
All new zealand has is rubber boots .</tokentext>
<sentencetext>The only time I want to go to the linux conference, they move it a two hour flight away to new zealand.
what the fuck idiot decides to have it there?
There is nothing in new zealand at least Australia has women and nice clubs for after.
All new zealand has is rubber boots.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805318</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805552</id>
	<title>Re:Reverse engineered nVidia drivers?</title>
	<author>Anonymous</author>
	<datestamp>1263805740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Noveau is included in staging (which means that it comes with the kernel, but is not considered stable). Nv isn't a kernel driver at all, but merely an X.org driver from nvidia. Though the noveau kernel and X.org drivers are more fully featured than the nv offering, they still don't support 3D-acceleration very well.</p></htmltext>
<tokenext>Noveau is included in staging ( which means that it comes with the kernel , but is not considered stable ) .
Nv is n't a kernel driver at all , but merely an X.org driver from nvidia .
Though the noveau kernel and X.org drivers are more fully featured than the nv offering , they still do n't support 3D-acceleration very well .</tokentext>
<sentencetext>Noveau is included in staging (which means that it comes with the kernel, but is not considered stable).
Nv isn't a kernel driver at all, but merely an X.org driver from nvidia.
Though the noveau kernel and X.org drivers are more fully featured than the nv offering, they still don't support 3D-acceleration very well.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805556</id>
	<title>Re:Thank goodness for those drivers</title>
	<author>l2718</author>
	<datestamp>1263805800000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><blockquote><div><p>I have such a chipset and I've been cursing NVIDIA on a regular basis.</p></div></blockquote><p>

You must be new to this "Linux" thing.  That your Hardware OEM is providing Linux drivers at all is highly unusual.  That the drivers are effective is astounding -- that the installer provided the drivers is rudimentary is not worth complaining over.  In any case if you really mind I'm sure you can write a replacement installer.</p></div>
	</htmltext>
<tokenext>I have such a chipset and I 've been cursing NVIDIA on a regular basis .
You must be new to this " Linux " thing .
That your Hardware OEM is providing Linux drivers at all is highly unusual .
That the drivers are effective is astounding -- that the installer provided the drivers is rudimentary is not worth complaining over .
In any case if you really mind I 'm sure you can write a replacement installer .</tokentext>
<sentencetext>I have such a chipset and I've been cursing NVIDIA on a regular basis.
You must be new to this "Linux" thing.
That your Hardware OEM is providing Linux drivers at all is highly unusual.
That the drivers are effective is astounding -- that the installer provided the drivers is rudimentary is not worth complaining over.
In any case if you really mind I'm sure you can write a replacement installer.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805532</id>
	<title>no such problem with Fedora</title>
	<author>Errtu76</author>
	<datestamp>1263805440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I'm running Fedora (12) and with the rpmfusion(-nonfree*) repository added, i don't need to run nvidia's installer. I just update my entire system, including the nvidia driver. If you're fed up by your way of updating, give Fedora a chance.</p></htmltext>
<tokenext>I 'm running Fedora ( 12 ) and with the rpmfusion ( -nonfree * ) repository added , i do n't need to run nvidia 's installer .
I just update my entire system , including the nvidia driver .
If you 're fed up by your way of updating , give Fedora a chance .</tokentext>
<sentencetext>I'm running Fedora (12) and with the rpmfusion(-nonfree*) repository added, i don't need to run nvidia's installer.
I just update my entire system, including the nvidia driver.
If you're fed up by your way of updating, give Fedora a chance.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806720</id>
	<title>Linux Kernel? Not important. Linux Scheduler?</title>
	<author>Anonymous</author>
	<datestamp>1263821880000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><b>IMPORTANT</b>.</p><p>Why? Because the Linux Kernel is already the best in existence, nothing else comes close. The Windows and OSX kernels are toys in comparison, like something by Fisher Price.</p><p>What Linux needs is the new scheduler written by Meatloaf. Its very efficient, very fast, and very intelligent - probably the most advanced scheduler ever written. Like most people, I was suprised to find out that Meatloaf was an expert Linux hacker, but it turns out he is, and I can't wait to see his code go live.</p></htmltext>
<tokenext>IMPORTANT.Why ?
Because the Linux Kernel is already the best in existence , nothing else comes close .
The Windows and OSX kernels are toys in comparison , like something by Fisher Price.What Linux needs is the new scheduler written by Meatloaf .
Its very efficient , very fast , and very intelligent - probably the most advanced scheduler ever written .
Like most people , I was suprised to find out that Meatloaf was an expert Linux hacker , but it turns out he is , and I ca n't wait to see his code go live .</tokentext>
<sentencetext>IMPORTANT.Why?
Because the Linux Kernel is already the best in existence, nothing else comes close.
The Windows and OSX kernels are toys in comparison, like something by Fisher Price.What Linux needs is the new scheduler written by Meatloaf.
Its very efficient, very fast, and very intelligent - probably the most advanced scheduler ever written.
Like most people, I was suprised to find out that Meatloaf was an expert Linux hacker, but it turns out he is, and I can't wait to see his code go live.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805224</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805628</id>
	<title>Re:Thank goodness for those drivers</title>
	<author>timbo234</author>
	<datestamp>1263807180000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>I haven't had to do that for a few years now, modern distributions (Mandriva and OpenSuse for eg.) automatically setup DKMS or use some other mechanism to update the NVIDIA drivers automagically when a new kernel boots.</p><p>That said however it'd be better to have a working NVIDIA driver in the kernel, as these solutions are a bit hacky and potentially an open-source driver would have a faster pace of development (instead of being the poor cousin to the Windows drivers in NVIDIA's internal development priorities).</p></htmltext>
<tokenext>I have n't had to do that for a few years now , modern distributions ( Mandriva and OpenSuse for eg .
) automatically setup DKMS or use some other mechanism to update the NVIDIA drivers automagically when a new kernel boots.That said however it 'd be better to have a working NVIDIA driver in the kernel , as these solutions are a bit hacky and potentially an open-source driver would have a faster pace of development ( instead of being the poor cousin to the Windows drivers in NVIDIA 's internal development priorities ) .</tokentext>
<sentencetext>I haven't had to do that for a few years now, modern distributions (Mandriva and OpenSuse for eg.
) automatically setup DKMS or use some other mechanism to update the NVIDIA drivers automagically when a new kernel boots.That said however it'd be better to have a working NVIDIA driver in the kernel, as these solutions are a bit hacky and potentially an open-source driver would have a faster pace of development (instead of being the poor cousin to the Windows drivers in NVIDIA's internal development priorities).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806424</id>
	<title>Re:huh?</title>
	<author>laptop006</author>
	<datestamp>1263818160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Yes.</p><p>Seriously you could put a bid in to have it in a field in Texas, and, if you're the best bid they'd give you the conf.</p><p>I was on the 2008 team, and putting on a conf to the level LCA does is a huge amount of work, so if you can bid and do it you have a real chance.</p><p>Of course not being in Australia (or New Zealand) makes it very expensive for those people to attend, so unless you can find a sponsor for flights you really aren't likely win for LCA2012 in Texas.</p></htmltext>
<tokenext>Yes.Seriously you could put a bid in to have it in a field in Texas , and , if you 're the best bid they 'd give you the conf.I was on the 2008 team , and putting on a conf to the level LCA does is a huge amount of work , so if you can bid and do it you have a real chance.Of course not being in Australia ( or New Zealand ) makes it very expensive for those people to attend , so unless you can find a sponsor for flights you really are n't likely win for LCA2012 in Texas .</tokentext>
<sentencetext>Yes.Seriously you could put a bid in to have it in a field in Texas, and, if you're the best bid they'd give you the conf.I was on the 2008 team, and putting on a conf to the level LCA does is a huge amount of work, so if you can bid and do it you have a real chance.Of course not being in Australia (or New Zealand) makes it very expensive for those people to attend, so unless you can find a sponsor for flights you really aren't likely win for LCA2012 in Texas.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805318</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30807574</id>
	<title>Re:Thank goodness for those drivers</title>
	<author>Skater</author>
	<datestamp>1263828360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Yeah, I buy NVidia cards because I know they are supported under Linux.  My one experience with an ATI card was not very good (although it was in a laptop).  However, I hope the kernel dual-head support is better than NVidia's for my current card - mine will shut off the primary monitor (which gives an "out of range" error message) from time to time.  VERY annoying, and I know it's not the monitor because I've had the same problem with two totally different monitors (two CRTs vs. two LCDs, running at different resolutions and clock speeds).</htmltext>
<tokenext>Yeah , I buy NVidia cards because I know they are supported under Linux .
My one experience with an ATI card was not very good ( although it was in a laptop ) .
However , I hope the kernel dual-head support is better than NVidia 's for my current card - mine will shut off the primary monitor ( which gives an " out of range " error message ) from time to time .
VERY annoying , and I know it 's not the monitor because I 've had the same problem with two totally different monitors ( two CRTs vs. two LCDs , running at different resolutions and clock speeds ) .</tokentext>
<sentencetext>Yeah, I buy NVidia cards because I know they are supported under Linux.
My one experience with an ATI card was not very good (although it was in a laptop).
However, I hope the kernel dual-head support is better than NVidia's for my current card - mine will shut off the primary monitor (which gives an "out of range" error message) from time to time.
VERY annoying, and I know it's not the monitor because I've had the same problem with two totally different monitors (two CRTs vs. two LCDs, running at different resolutions and clock speeds).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805816</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374</id>
	<title>Thank goodness for those drivers</title>
	<author>Anonymous</author>
	<datestamp>1263846000000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>I have such a chipset and I've been cursing NVIDIA on a regular basis. After updating to any new kernel, I must boot into no-X mode, then run the proprietary driver installer.</p></htmltext>
<tokenext>I have such a chipset and I 've been cursing NVIDIA on a regular basis .
After updating to any new kernel , I must boot into no-X mode , then run the proprietary driver installer .</tokentext>
<sentencetext>I have such a chipset and I've been cursing NVIDIA on a regular basis.
After updating to any new kernel, I must boot into no-X mode, then run the proprietary driver installer.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805518</id>
	<title>Re:Thank goodness for those drivers</title>
	<author>amRadioHed</author>
	<datestamp>1263805260000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>You'll still need to do that if you want 3D support. nouveau is replacing the old nv driver, but it's not ready to replace the proprietary driver.</p></htmltext>
<tokenext>You 'll still need to do that if you want 3D support .
nouveau is replacing the old nv driver , but it 's not ready to replace the proprietary driver .</tokentext>
<sentencetext>You'll still need to do that if you want 3D support.
nouveau is replacing the old nv driver, but it's not ready to replace the proprietary driver.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30807484</id>
	<title>Re:Reverse engineered nVidia drivers?</title>
	<author>V!NCENT</author>
	<datestamp>1263827640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It's a reverse engineered driver, but instead of copying it, the devs went to convert it to Gallium3D driver architecture. There are two components. One is the Direct Rendering Manager component (lives in the kernel) and the second one is in Mesa (the free OpenGL implementation) as a state tracker.</p><p>A Gallium3D driver is making the graphics card visible to the system by means of an API. On top of that API features can be written (like OpenGL, OpenCL, vector graphics acceleration, etc) which are called state trackers. Mesa is now such a state tracker.</p><p>When a OpenGL 3.x state tracker has been written, for example, it will work on all graphics cards that have a Gallium3D driver. So now all graphics drivers in Linux will get the same feature set. When sobody writes a feature for his ATI card, you as an nVidia users will also get to have that feature and vise versa...<nobr> <wbr></nobr>;)</p></htmltext>
<tokenext>It 's a reverse engineered driver , but instead of copying it , the devs went to convert it to Gallium3D driver architecture .
There are two components .
One is the Direct Rendering Manager component ( lives in the kernel ) and the second one is in Mesa ( the free OpenGL implementation ) as a state tracker.A Gallium3D driver is making the graphics card visible to the system by means of an API .
On top of that API features can be written ( like OpenGL , OpenCL , vector graphics acceleration , etc ) which are called state trackers .
Mesa is now such a state tracker.When a OpenGL 3.x state tracker has been written , for example , it will work on all graphics cards that have a Gallium3D driver .
So now all graphics drivers in Linux will get the same feature set .
When sobody writes a feature for his ATI card , you as an nVidia users will also get to have that feature and vise versa... ; )</tokentext>
<sentencetext>It's a reverse engineered driver, but instead of copying it, the devs went to convert it to Gallium3D driver architecture.
There are two components.
One is the Direct Rendering Manager component (lives in the kernel) and the second one is in Mesa (the free OpenGL implementation) as a state tracker.A Gallium3D driver is making the graphics card visible to the system by means of an API.
On top of that API features can be written (like OpenGL, OpenCL, vector graphics acceleration, etc) which are called state trackers.
Mesa is now such a state tracker.When a OpenGL 3.x state tracker has been written, for example, it will work on all graphics cards that have a Gallium3D driver.
So now all graphics drivers in Linux will get the same feature set.
When sobody writes a feature for his ATI card, you as an nVidia users will also get to have that feature and vise versa... ;)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806094</id>
	<title>Re:Thank goodness for those drivers</title>
	<author>Kjella</author>
	<datestamp>1263814200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>|. Switch to nv driver<br>2. Upgrade kernel<br>3. Switch to nvidia driver</p><p>Not that I've ever done that, I use a distro that packages the kernel and binary driver for me. Maybe if you want a userfriendly solution you should get one instead of trying to do everything manually, then complain about having to do everything manually?</p><p>Nouveau will be much closer to nv than nvidia in pretty much everything. They got no specs, and even with specs writing a good open source 3D driver is tough, as AMD has shown us. So expect no 3D acceleration, no video acceleration, no nothing. The only thing you get is 2D modesetting in the kernel instead of xorg, big whoop. If you don't use KMS for anything else, the only thing it'll do it make your boot a little prettier.</p></htmltext>
<tokenext>| .
Switch to nv driver2 .
Upgrade kernel3 .
Switch to nvidia driverNot that I 've ever done that , I use a distro that packages the kernel and binary driver for me .
Maybe if you want a userfriendly solution you should get one instead of trying to do everything manually , then complain about having to do everything manually ? Nouveau will be much closer to nv than nvidia in pretty much everything .
They got no specs , and even with specs writing a good open source 3D driver is tough , as AMD has shown us .
So expect no 3D acceleration , no video acceleration , no nothing .
The only thing you get is 2D modesetting in the kernel instead of xorg , big whoop .
If you do n't use KMS for anything else , the only thing it 'll do it make your boot a little prettier .</tokentext>
<sentencetext>|.
Switch to nv driver2.
Upgrade kernel3.
Switch to nvidia driverNot that I've ever done that, I use a distro that packages the kernel and binary driver for me.
Maybe if you want a userfriendly solution you should get one instead of trying to do everything manually, then complain about having to do everything manually?Nouveau will be much closer to nv than nvidia in pretty much everything.
They got no specs, and even with specs writing a good open source 3D driver is tough, as AMD has shown us.
So expect no 3D acceleration, no video acceleration, no nothing.
The only thing you get is 2D modesetting in the kernel instead of xorg, big whoop.
If you don't use KMS for anything else, the only thing it'll do it make your boot a little prettier.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805308</id>
	<title>O!  Version  2.6.4.8 and a half!</title>
	<author>Anonymous</author>
	<datestamp>1263845220000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext><p>So Exciting!</p><p>I wish I was a lemix too!</p></htmltext>
<tokenext>So Exciting ! I wish I was a lemix too !</tokentext>
<sentencetext>So Exciting!I wish I was a lemix too!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806178</id>
	<title>Re:Will the kernel ever get to 3?</title>
	<author>vadim\_t</author>
	<datestamp>1263815100000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><blockquote><div><p>Are we ever going to see major new features (along the lines of the USB implementation, or SMP), or a major re-think? Or is this basically as good as it will ever get?</p></div></blockquote><p>USB and SMP are things the kernel implemented, but weren't created inside it. The kernel can't add implementation for a bus that doesn't exist, so it's not going to get more things like that, unless new standards get created.</p><p>But, new things get added all the time, just watch the kernel reports at <a href="http://lwn.net/" title="lwn.net">LWN</a> [lwn.net].</p></div>
	</htmltext>
<tokenext>Are we ever going to see major new features ( along the lines of the USB implementation , or SMP ) , or a major re-think ?
Or is this basically as good as it will ever get ? USB and SMP are things the kernel implemented , but were n't created inside it .
The kernel ca n't add implementation for a bus that does n't exist , so it 's not going to get more things like that , unless new standards get created.But , new things get added all the time , just watch the kernel reports at LWN [ lwn.net ] .</tokentext>
<sentencetext>Are we ever going to see major new features (along the lines of the USB implementation, or SMP), or a major re-think?
Or is this basically as good as it will ever get?USB and SMP are things the kernel implemented, but weren't created inside it.
The kernel can't add implementation for a bus that doesn't exist, so it's not going to get more things like that, unless new standards get created.But, new things get added all the time, just watch the kernel reports at LWN [lwn.net].
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805610</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805224</id>
	<title>Year of the linux desktop</title>
	<author>Anonymous</author>
	<datestamp>1263757620000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext><p>So this is the year of the linux desktop? Yeehaw kernel 2.7!</p></htmltext>
<tokenext>So this is the year of the linux desktop ?
Yeehaw kernel 2.7 !</tokentext>
<sentencetext>So this is the year of the linux desktop?
Yeehaw kernel 2.7!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805596</id>
	<title>Re:huh?</title>
	<author>Paua Fritter</author>
	<datestamp>1263806760000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>0</modscore>
	<htmltext><p>Australia, aka the "West Island" of NZ</p></htmltext>
<tokenext>Australia , aka the " West Island " of NZ</tokentext>
<sentencetext>Australia, aka the "West Island" of NZ</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805318</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30815060</id>
	<title>Re:huh?</title>
	<author>Trogre</author>
	<datestamp>1263824040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It could be worse, they could have put it in Perth.  Oh wait, they already did.</p></htmltext>
<tokenext>It could be worse , they could have put it in Perth .
Oh wait , they already did .</tokentext>
<sentencetext>It could be worse, they could have put it in Perth.
Oh wait, they already did.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805718</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30807134</id>
	<title>Re:Will the kernel ever get to 3?</title>
	<author>Kjella</author>
	<datestamp>1263825060000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>Actually, I hope the kernel will contain less. Let's take USB for example, do we really need all sorts of various connectors? Or would we rather just use USB, teach the kernel to do low level read/write to USB devices and then do keyboards and mice and printers and scanners and digicams and webcams and external hdds and whatnot over USB in userspace? In fact, much the same applies to drivers in general, there's no reason why so many printers are paperweights under Linux. Can't there at least be one universal idiot mode where we feed it uncompressed raster data and it prints? Seriously.</p><p>Kernels are best at being mediators, be it of CPU time, GPU time, IO bandwidth, network bandwidth, whatever. Something offers resources, something consumes resources and the OS is that gray glue in the middle. Whatever killer feature you want, you probably don't want it in the kernel. You want to write a desktop environment or an application or something, and the kernel will make sure it runs gracefully together with everything else. There's a quite a few more bits to the kernel, but they're just adoptees brought into the kernel for performance reasons.</p></htmltext>
<tokenext>Actually , I hope the kernel will contain less .
Let 's take USB for example , do we really need all sorts of various connectors ?
Or would we rather just use USB , teach the kernel to do low level read/write to USB devices and then do keyboards and mice and printers and scanners and digicams and webcams and external hdds and whatnot over USB in userspace ?
In fact , much the same applies to drivers in general , there 's no reason why so many printers are paperweights under Linux .
Ca n't there at least be one universal idiot mode where we feed it uncompressed raster data and it prints ?
Seriously.Kernels are best at being mediators , be it of CPU time , GPU time , IO bandwidth , network bandwidth , whatever .
Something offers resources , something consumes resources and the OS is that gray glue in the middle .
Whatever killer feature you want , you probably do n't want it in the kernel .
You want to write a desktop environment or an application or something , and the kernel will make sure it runs gracefully together with everything else .
There 's a quite a few more bits to the kernel , but they 're just adoptees brought into the kernel for performance reasons .</tokentext>
<sentencetext>Actually, I hope the kernel will contain less.
Let's take USB for example, do we really need all sorts of various connectors?
Or would we rather just use USB, teach the kernel to do low level read/write to USB devices and then do keyboards and mice and printers and scanners and digicams and webcams and external hdds and whatnot over USB in userspace?
In fact, much the same applies to drivers in general, there's no reason why so many printers are paperweights under Linux.
Can't there at least be one universal idiot mode where we feed it uncompressed raster data and it prints?
Seriously.Kernels are best at being mediators, be it of CPU time, GPU time, IO bandwidth, network bandwidth, whatever.
Something offers resources, something consumes resources and the OS is that gray glue in the middle.
Whatever killer feature you want, you probably don't want it in the kernel.
You want to write a desktop environment or an application or something, and the kernel will make sure it runs gracefully together with everything else.
There's a quite a few more bits to the kernel, but they're just adoptees brought into the kernel for performance reasons.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805610</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805404</id>
	<title>It's official</title>
	<author>Laser\_iCE</author>
	<datestamp>1263846540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>According to sources in the US (slashdot: <a href="http://linux.slashdot.org/article.pl?sid=10/01/18/0257232" title="slashdot.org" rel="nofollow">http://linux.slashdot.org/article.pl?sid=10/01/18/0257232</a> [slashdot.org]), Australia has finally taken over New Zealand in a bloodless coup.</htmltext>
<tokenext>According to sources in the US ( slashdot : http : //linux.slashdot.org/article.pl ? sid = 10/01/18/0257232 [ slashdot.org ] ) , Australia has finally taken over New Zealand in a bloodless coup .</tokentext>
<sentencetext>According to sources in the US (slashdot: http://linux.slashdot.org/article.pl?sid=10/01/18/0257232 [slashdot.org]), Australia has finally taken over New Zealand in a bloodless coup.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805772</id>
	<title>Re:Thank goodness for those drivers</title>
	<author>Anonymous</author>
	<datestamp>1263809760000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>yeah. thank goodness </p><p>now we have a new set of buggy drivers to curse at...excellent</p></htmltext>
<tokenext>yeah .
thank goodness now we have a new set of buggy drivers to curse at...excellent</tokentext>
<sentencetext>yeah.
thank goodness now we have a new set of buggy drivers to curse at...excellent</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805816</id>
	<title>Re:Thank goodness for those drivers</title>
	<author>Anonymous</author>
	<datestamp>1263810600000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><i>So, Nvidia writes drivers for your system, and those drivers work. What's the problem?</i> <br> <br>
Indeed, I have no problem with that. I've been using Linux or long enough to remember having to spend a lot of time getting around issues of hardware compatibility. Nvidia was in there quite early on providing good drivers for its chipsets at a time when just about every other manufacturer just shrugged its shoulders and told us to "Fuck off, We don't support Linux."<br> <br>
That alone has promoted a lot of goodwill as far as I'm concerned, and so nVidia chipsets are right at the top of my preferred brands list. So I get very tired of hearing people badmouthing nVidia without giving an adequate reason why.</htmltext>
<tokenext>So , Nvidia writes drivers for your system , and those drivers work .
What 's the problem ?
Indeed , I have no problem with that .
I 've been using Linux or long enough to remember having to spend a lot of time getting around issues of hardware compatibility .
Nvidia was in there quite early on providing good drivers for its chipsets at a time when just about every other manufacturer just shrugged its shoulders and told us to " Fuck off , We do n't support Linux .
" That alone has promoted a lot of goodwill as far as I 'm concerned , and so nVidia chipsets are right at the top of my preferred brands list .
So I get very tired of hearing people badmouthing nVidia without giving an adequate reason why .</tokentext>
<sentencetext>So, Nvidia writes drivers for your system, and those drivers work.
What's the problem?
Indeed, I have no problem with that.
I've been using Linux or long enough to remember having to spend a lot of time getting around issues of hardware compatibility.
Nvidia was in there quite early on providing good drivers for its chipsets at a time when just about every other manufacturer just shrugged its shoulders and told us to "Fuck off, We don't support Linux.
" 
That alone has promoted a lot of goodwill as far as I'm concerned, and so nVidia chipsets are right at the top of my preferred brands list.
So I get very tired of hearing people badmouthing nVidia without giving an adequate reason why.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805500</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805368</id>
	<title>Re:huh?</title>
	<author>Anonymous</author>
	<datestamp>1263845940000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Haven't been to australia recently, have you?<nobr> <wbr></nobr>:P</p></htmltext>
<tokenext>Have n't been to australia recently , have you ?
: P</tokentext>
<sentencetext>Haven't been to australia recently, have you?
:P</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805318</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806468</id>
	<title>Or just use a decent distribution</title>
	<author>Zero\_\_Kelvin</author>
	<datestamp>1263818640000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><blockquote><div><p>"I have such a chipset and I've been cursing NVIDIA on a regular basis. After updating to any new kernel, I must boot into no-X mode, then run the proprietary driver installer."</p></div></blockquote><p>Or you could get one of the many, many, many Linux distributions that handle this automatically.  Mandriva comes the mind since it has handled this stuff for years and is extremely user friendly, but as I say there are <b> <i>many</i></b>  other options as well.</p></div>
	</htmltext>
<tokenext>" I have such a chipset and I 've been cursing NVIDIA on a regular basis .
After updating to any new kernel , I must boot into no-X mode , then run the proprietary driver installer .
" Or you could get one of the many , many , many Linux distributions that handle this automatically .
Mandriva comes the mind since it has handled this stuff for years and is extremely user friendly , but as I say there are many other options as well .</tokentext>
<sentencetext>"I have such a chipset and I've been cursing NVIDIA on a regular basis.
After updating to any new kernel, I must boot into no-X mode, then run the proprietary driver installer.
"Or you could get one of the many, many, many Linux distributions that handle this automatically.
Mandriva comes the mind since it has handled this stuff for years and is extremely user friendly, but as I say there are  many  other options as well.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805610</id>
	<title>Will the kernel ever get to 3?</title>
	<author>Anonymous</author>
	<datestamp>1263806880000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>Most releases seem to be minor improvements: a few bug fixes, re-porting to another architecture, some new drivers and tweaks to (or reimplementations of) existing features such as VM or filesystems.
<p>
Are we ever going to see major new features (along the lines of the USB implementation, or SMP), or a major re-think? Or is this basically as good as it will ever get?
</p><p>
It does appear to me that all the kernel is doing these days is mimicking the features and support found in "other" operating systems - rather than pushing the boundaries of innovation and novelty, itself.It would be a shame if Linux just fell into line and became a follower in a world of <i>twisty little O/S's, all the same</i> rather than producing some killer features, unique to it's implementation, that made people WANT to run Linux on their desktops and enterprise systems.</p></htmltext>
<tokenext>Most releases seem to be minor improvements : a few bug fixes , re-porting to another architecture , some new drivers and tweaks to ( or reimplementations of ) existing features such as VM or filesystems .
Are we ever going to see major new features ( along the lines of the USB implementation , or SMP ) , or a major re-think ?
Or is this basically as good as it will ever get ?
It does appear to me that all the kernel is doing these days is mimicking the features and support found in " other " operating systems - rather than pushing the boundaries of innovation and novelty , itself.It would be a shame if Linux just fell into line and became a follower in a world of twisty little O/S 's , all the same rather than producing some killer features , unique to it 's implementation , that made people WANT to run Linux on their desktops and enterprise systems .</tokentext>
<sentencetext>Most releases seem to be minor improvements: a few bug fixes, re-porting to another architecture, some new drivers and tweaks to (or reimplementations of) existing features such as VM or filesystems.
Are we ever going to see major new features (along the lines of the USB implementation, or SMP), or a major re-think?
Or is this basically as good as it will ever get?
It does appear to me that all the kernel is doing these days is mimicking the features and support found in "other" operating systems - rather than pushing the boundaries of innovation and novelty, itself.It would be a shame if Linux just fell into line and became a follower in a world of twisty little O/S's, all the same rather than producing some killer features, unique to it's implementation, that made people WANT to run Linux on their desktops and enterprise systems.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806508</id>
	<title>Re:Will the kernel ever get to 3?</title>
	<author>Zero\_\_Kelvin</author>
	<datestamp>1263819060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>"Are we ever going to see major new features (along the lines of the USB implementation, or SMP), or a major re-think?"</p></div></blockquote><p>Sure.  Just get a time machine and you can go back to the day before Linux was the first to implement USB 3<nobr> <wbr></nobr>;-)  As far as a "major re-think", the purpose of thinking things through seriously and thoroughly in the first place (before diving in) is so that you won't <b> <i>have</i></b>  to do major re-think.  Major re-thinks are a bad thing unless you didn't do it right the first time.</p></div>
	</htmltext>
<tokenext>" Are we ever going to see major new features ( along the lines of the USB implementation , or SMP ) , or a major re-think ? " Sure .
Just get a time machine and you can go back to the day before Linux was the first to implement USB 3 ; - ) As far as a " major re-think " , the purpose of thinking things through seriously and thoroughly in the first place ( before diving in ) is so that you wo n't have to do major re-think .
Major re-thinks are a bad thing unless you did n't do it right the first time .</tokentext>
<sentencetext>"Are we ever going to see major new features (along the lines of the USB implementation, or SMP), or a major re-think?"Sure.
Just get a time machine and you can go back to the day before Linux was the first to implement USB 3 ;-)  As far as a "major re-think", the purpose of thinking things through seriously and thoroughly in the first place (before diving in) is so that you won't  have  to do major re-think.
Major re-thinks are a bad thing unless you didn't do it right the first time.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805610</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805722</id>
	<title>Re:Thank goodness for those drivers</title>
	<author>Brebs</author>
	<datestamp>1263808920000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>This is what startup scripts are for:

<a href="http://www.fedoraforum.org/forum/showthread.php?p=1047697#post1047697" title="fedoraforum.org" rel="nofollow">http://www.fedoraforum.org/forum/showthread.php?p=1047697#post1047697</a> [fedoraforum.org]</htmltext>
<tokenext>This is what startup scripts are for : http : //www.fedoraforum.org/forum/showthread.php ? p = 1047697 # post1047697 [ fedoraforum.org ]</tokentext>
<sentencetext>This is what startup scripts are for:

http://www.fedoraforum.org/forum/showthread.php?p=1047697#post1047697 [fedoraforum.org]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30811230</id>
	<title>Re:Thank goodness for those drivers</title>
	<author>l2718</author>
	<datestamp>1263846360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Having been a unix sysadmin for 15 years, I'm quite aware of package managers.  Unfortunately not all OEM drivers come nicely packaged, so you have to install them by hand.  Yes, I know I could make an RPM file around the driver, but it's far simpler to write a shellscript that automates the tasks the OP wanted (shut down X, shut down the display, replace kernel modules and X drivers, restart display, restart X).  And yes, I call such a script an "installer".  It doesn't display fancy graphics, but it sure does install the driver.</htmltext>
<tokenext>Having been a unix sysadmin for 15 years , I 'm quite aware of package managers .
Unfortunately not all OEM drivers come nicely packaged , so you have to install them by hand .
Yes , I know I could make an RPM file around the driver , but it 's far simpler to write a shellscript that automates the tasks the OP wanted ( shut down X , shut down the display , replace kernel modules and X drivers , restart display , restart X ) .
And yes , I call such a script an " installer " .
It does n't display fancy graphics , but it sure does install the driver .</tokentext>
<sentencetext>Having been a unix sysadmin for 15 years, I'm quite aware of package managers.
Unfortunately not all OEM drivers come nicely packaged, so you have to install them by hand.
Yes, I know I could make an RPM file around the driver, but it's far simpler to write a shellscript that automates the tasks the OP wanted (shut down X, shut down the display, replace kernel modules and X drivers, restart display, restart X).
And yes, I call such a script an "installer".
It doesn't display fancy graphics, but it sure does install the driver.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30808418</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805394</id>
	<title>Reverse engineered nVidia drivers?</title>
	<author>Anonymous</author>
	<datestamp>1263846300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>By that vague statement do they mean that nouvea will be included or is someone else making yet another set of nvidia drivers? (nv is from nVidia right?)</htmltext>
<tokenext>By that vague statement do they mean that nouvea will be included or is someone else making yet another set of nvidia drivers ?
( nv is from nVidia right ?
)</tokentext>
<sentencetext>By that vague statement do they mean that nouvea will be included or is someone else making yet another set of nvidia drivers?
(nv is from nVidia right?
)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30808508</id>
	<title>Re:Year of the linux desktop</title>
	<author>Darth Sdlavrot</author>
	<datestamp>1263833340000</datestamp>
	<modclass>Troll</modclass>
	<modscore>0</modscore>
	<htmltext><p>This is Open Source.</p><p>It's up to you to fix it and send the fix to X.Org.</p></htmltext>
<tokenext>This is Open Source.It 's up to you to fix it and send the fix to X.Org .</tokentext>
<sentencetext>This is Open Source.It's up to you to fix it and send the fix to X.Org.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806542</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805876</id>
	<title>Re:huh?</title>
	<author>rubycodez</author>
	<datestamp>1263811560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>New Zealand is part of a continent called Zealandia, not Australia.  but by all means pull some more "facts" out of your ass, it's more interesting than reality.</p><p><a href="http://en.wikipedia.org/wiki/Zealandia\_(continent)" title="wikipedia.org">http://en.wikipedia.org/wiki/Zealandia\_(continent)</a> [wikipedia.org]</p></htmltext>
<tokenext>New Zealand is part of a continent called Zealandia , not Australia .
but by all means pull some more " facts " out of your ass , it 's more interesting than reality.http : //en.wikipedia.org/wiki/Zealandia \ _ ( continent ) [ wikipedia.org ]</tokentext>
<sentencetext>New Zealand is part of a continent called Zealandia, not Australia.
but by all means pull some more "facts" out of your ass, it's more interesting than reality.http://en.wikipedia.org/wiki/Zealandia\_(continent) [wikipedia.org]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805484</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30808372</id>
	<title>Re:Thank goodness for those drivers</title>
	<author>webheaded</author>
	<datestamp>1263832620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I'm surprised no one mentioned this but um...you can just reinstall the driver before you reboot after installing a new kernel.  The symbolic links should be changed pretty much immediately and after that is done, the installer throws the modules where they're supposed to be for the new stuff.  I've been doing this forever.  I mean don't get me wrong, it's silly that it has to be done and most nubs are going to "OMG WTF" when their PC reboots with no nvidia driver, but at least the damn driver is there, right?  Anyway, not sure why no one has mentioned this yet.  I've been doing that for Gentoo since the dawn of existence and I still do it in Arch just in case.  You don't need to boot into "No X mode" or whatever if you know what you're doing, unless your distro is somehow completely retarded.</htmltext>
<tokenext>I 'm surprised no one mentioned this but um...you can just reinstall the driver before you reboot after installing a new kernel .
The symbolic links should be changed pretty much immediately and after that is done , the installer throws the modules where they 're supposed to be for the new stuff .
I 've been doing this forever .
I mean do n't get me wrong , it 's silly that it has to be done and most nubs are going to " OMG WTF " when their PC reboots with no nvidia driver , but at least the damn driver is there , right ?
Anyway , not sure why no one has mentioned this yet .
I 've been doing that for Gentoo since the dawn of existence and I still do it in Arch just in case .
You do n't need to boot into " No X mode " or whatever if you know what you 're doing , unless your distro is somehow completely retarded .</tokentext>
<sentencetext>I'm surprised no one mentioned this but um...you can just reinstall the driver before you reboot after installing a new kernel.
The symbolic links should be changed pretty much immediately and after that is done, the installer throws the modules where they're supposed to be for the new stuff.
I've been doing this forever.
I mean don't get me wrong, it's silly that it has to be done and most nubs are going to "OMG WTF" when their PC reboots with no nvidia driver, but at least the damn driver is there, right?
Anyway, not sure why no one has mentioned this yet.
I've been doing that for Gentoo since the dawn of existence and I still do it in Arch just in case.
You don't need to boot into "No X mode" or whatever if you know what you're doing, unless your distro is somehow completely retarded.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806808</id>
	<title>Re:Thank goodness for those drivers</title>
	<author>Anonymous</author>
	<datestamp>1263822540000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>So, linux gets reverse-engineered NVIDIA chipset drivers just in time to see NVIDIA pull out of the chipset market... I guess it is useful for those using older hardware, as there are a ton of NVIDIA chipset motherboards out there, but at the moment NVIDIA chipset business is pretty much dead.</p></htmltext>
<tokenext>So , linux gets reverse-engineered NVIDIA chipset drivers just in time to see NVIDIA pull out of the chipset market... I guess it is useful for those using older hardware , as there are a ton of NVIDIA chipset motherboards out there , but at the moment NVIDIA chipset business is pretty much dead .</tokentext>
<sentencetext>So, linux gets reverse-engineered NVIDIA chipset drivers just in time to see NVIDIA pull out of the chipset market... I guess it is useful for those using older hardware, as there are a ton of NVIDIA chipset motherboards out there, but at the moment NVIDIA chipset business is pretty much dead.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805514</id>
	<title>Dtrace for Linux?</title>
	<author>fibrewire</author>
	<datestamp>1263805200000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Tell me more about this dynamic ftrace. Are there any "how-to" basic scripts to fire off a SNMP trap when ftrace picks up something of importance? It's nice for debugging, but more importantly to tie this into some network monitoring system like Nagios to be used for clustering and high availability systems. This could easily be integrated to prevent runaway virtual machines, and actually see whats robbing a system of CPU cycles - perfect for performance tuning a VM stack.</p></htmltext>
<tokenext>Tell me more about this dynamic ftrace .
Are there any " how-to " basic scripts to fire off a SNMP trap when ftrace picks up something of importance ?
It 's nice for debugging , but more importantly to tie this into some network monitoring system like Nagios to be used for clustering and high availability systems .
This could easily be integrated to prevent runaway virtual machines , and actually see whats robbing a system of CPU cycles - perfect for performance tuning a VM stack .</tokentext>
<sentencetext>Tell me more about this dynamic ftrace.
Are there any "how-to" basic scripts to fire off a SNMP trap when ftrace picks up something of importance?
It's nice for debugging, but more importantly to tie this into some network monitoring system like Nagios to be used for clustering and high availability systems.
This could easily be integrated to prevent runaway virtual machines, and actually see whats robbing a system of CPU cycles - perfect for performance tuning a VM stack.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30809922</id>
	<title>Re:Year of the linux desktop</title>
	<author>Sir\_Lewk</author>
	<datestamp>1263839880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>A 2.7 kernel would not be for general consumption, it'd be used for development during a transition to 2.8.  I believe Linus has publicly stated that he has no intention of going to 2.8 anytime in the forseeable future though.</p></htmltext>
<tokenext>A 2.7 kernel would not be for general consumption , it 'd be used for development during a transition to 2.8 .
I believe Linus has publicly stated that he has no intention of going to 2.8 anytime in the forseeable future though .</tokentext>
<sentencetext>A 2.7 kernel would not be for general consumption, it'd be used for development during a transition to 2.8.
I believe Linus has publicly stated that he has no intention of going to 2.8 anytime in the forseeable future though.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805224</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805318</id>
	<title>huh?</title>
	<author>Anonymous</author>
	<datestamp>1263845340000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>1</modscore>
	<htmltext>the linux australia conference is in new zealand?</htmltext>
<tokenext>the linux australia conference is in new zealand ?</tokentext>
<sentencetext>the linux australia conference is in new zealand?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30809494</id>
	<title>Re:Year of the linux desktop</title>
	<author>Anonymous</author>
	<datestamp>1263838080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>One question... why does one plug/unplug a usb keyboard several times?</p></htmltext>
<tokenext>One question... why does one plug/unplug a usb keyboard several times ?</tokentext>
<sentencetext>One question... why does one plug/unplug a usb keyboard several times?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806542</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30808150</id>
	<title>Re:Thank goodness for those drivers</title>
	<author>Zantetsuken</author>
	<datestamp>1263831300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>do you use Ubuntu? If so and you didn't know about it already, use: <a href="https://launchpad.net/~nvidia-vdpau/+archive/ppa" title="launchpad.net">NVidia Launchpad PPA</a> [launchpad.net]</htmltext>
<tokenext>do you use Ubuntu ?
If so and you did n't know about it already , use : NVidia Launchpad PPA [ launchpad.net ]</tokentext>
<sentencetext>do you use Ubuntu?
If so and you didn't know about it already, use: NVidia Launchpad PPA [launchpad.net]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30815990</id>
	<title>Re:Will the kernel ever get to 3?</title>
	<author>Randle\_Revar</author>
	<datestamp>1263834300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>In November Greg K-H <a href="http://howsoftwareisbuilt.com/2009/11/18/interview-with-greg-kroah-hartman-linux-kernel-devmaintainer/" title="howsoftwareisbuilt.com">said</a> [howsoftwareisbuilt.com] "We change something like 5,000 lines a day, which is just scary. Fifty percent of that change will be in the drivers, and five percent will be in the core kernel."</p><p><a href="http://lwn.net/Articles/363456/" title="lwn.net">According to LWN</a> [lwn.net] "2.6.32 is the result of 10,767 non-merge changesets sent in by 1,229 developers. This changes added a total of 1.17 million lines, while removing 611,000 lines, for a net growth of 559,000 lines of code." This isn't out of the ordinary, either (e.g. " 2.6.31 development cycle had seen the incorporation of 10,663 non-merge changesets from 1,146 individual developers. These patches added almost 903,000 lines of code and removed just over 494,000 lines, for a net growth of just over 408,000 lines.").</p><p>As for this stuff all being minor, read LWN, or the Kernel Newbies changelog, and see how long you keep that illusion.</p><p>Since the 2.4 -&gt; 2.6 transition was so bad, Linus is unlikely to ever again do a "break the world" change, either with or without a long lived dev branch like 2.5. And really there is no need, short of switching to a microkernel or a managed language, everything can be done as a series of gradual changes (see: the ongoing TTY rework, KMS/DRI2, the relatively recent power-saving/suspend work, the gradual removal of the big kernel lock, the<nobr> <wbr></nobr>/x86\_64/ -&gt;<nobr> <wbr></nobr>/x86/ merge, the addition of mutexes (~2006Q1), someday the realtime stuff will probably be merged without a major version bump, etc)</p></htmltext>
<tokenext>In November Greg K-H said [ howsoftwareisbuilt.com ] " We change something like 5,000 lines a day , which is just scary .
Fifty percent of that change will be in the drivers , and five percent will be in the core kernel .
" According to LWN [ lwn.net ] " 2.6.32 is the result of 10,767 non-merge changesets sent in by 1,229 developers .
This changes added a total of 1.17 million lines , while removing 611,000 lines , for a net growth of 559,000 lines of code .
" This is n't out of the ordinary , either ( e.g .
" 2.6.31 development cycle had seen the incorporation of 10,663 non-merge changesets from 1,146 individual developers .
These patches added almost 903,000 lines of code and removed just over 494,000 lines , for a net growth of just over 408,000 lines .
" ) .As for this stuff all being minor , read LWN , or the Kernel Newbies changelog , and see how long you keep that illusion.Since the 2.4 - &gt; 2.6 transition was so bad , Linus is unlikely to ever again do a " break the world " change , either with or without a long lived dev branch like 2.5 .
And really there is no need , short of switching to a microkernel or a managed language , everything can be done as a series of gradual changes ( see : the ongoing TTY rework , KMS/DRI2 , the relatively recent power-saving/suspend work , the gradual removal of the big kernel lock , the /x86 \ _64/ - &gt; /x86/ merge , the addition of mutexes ( ~ 2006Q1 ) , someday the realtime stuff will probably be merged without a major version bump , etc )</tokentext>
<sentencetext>In November Greg K-H said [howsoftwareisbuilt.com] "We change something like 5,000 lines a day, which is just scary.
Fifty percent of that change will be in the drivers, and five percent will be in the core kernel.
"According to LWN [lwn.net] "2.6.32 is the result of 10,767 non-merge changesets sent in by 1,229 developers.
This changes added a total of 1.17 million lines, while removing 611,000 lines, for a net growth of 559,000 lines of code.
" This isn't out of the ordinary, either (e.g.
" 2.6.31 development cycle had seen the incorporation of 10,663 non-merge changesets from 1,146 individual developers.
These patches added almost 903,000 lines of code and removed just over 494,000 lines, for a net growth of just over 408,000 lines.
").As for this stuff all being minor, read LWN, or the Kernel Newbies changelog, and see how long you keep that illusion.Since the 2.4 -&gt; 2.6 transition was so bad, Linus is unlikely to ever again do a "break the world" change, either with or without a long lived dev branch like 2.5.
And really there is no need, short of switching to a microkernel or a managed language, everything can be done as a series of gradual changes (see: the ongoing TTY rework, KMS/DRI2, the relatively recent power-saving/suspend work, the gradual removal of the big kernel lock, the /x86\_64/ -&gt; /x86/ merge, the addition of mutexes (~2006Q1), someday the realtime stuff will probably be merged without a major version bump, etc)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805610</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30807014</id>
	<title>Re:Thank goodness for those drivers</title>
	<author>jaminJay</author>
	<datestamp>1263823920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>
I started with nVidia on my first Linux-powered box and, at most, was a couple of days out between Fedora release and stable nVidia driver release (one went to a week before I found the 'ignore ABI' switch on a forum).
</p><p>
That card eventually died and I replaced it with an ATI card, supposedly superior.  I never got it to work with Compiz.  Ever.  I struggled to get the open source drivers to do dual-head mode.  I even tried Win7 RC1 in the hope that that would at least allow me to benefit from my hardware investment.  Nope.
</p><p>
Needless to say, my new box has an nVidia card and RPMFusion-packaged closed-source drivers (which I just check are out before updating the kernel, unless it's critical.  I'll invest in nVidia because they invest in their customers.
</p></htmltext>
<tokenext>I started with nVidia on my first Linux-powered box and , at most , was a couple of days out between Fedora release and stable nVidia driver release ( one went to a week before I found the 'ignore ABI ' switch on a forum ) .
That card eventually died and I replaced it with an ATI card , supposedly superior .
I never got it to work with Compiz .
Ever. I struggled to get the open source drivers to do dual-head mode .
I even tried Win7 RC1 in the hope that that would at least allow me to benefit from my hardware investment .
Nope . Needless to say , my new box has an nVidia card and RPMFusion-packaged closed-source drivers ( which I just check are out before updating the kernel , unless it 's critical .
I 'll invest in nVidia because they invest in their customers .</tokentext>
<sentencetext>
I started with nVidia on my first Linux-powered box and, at most, was a couple of days out between Fedora release and stable nVidia driver release (one went to a week before I found the 'ignore ABI' switch on a forum).
That card eventually died and I replaced it with an ATI card, supposedly superior.
I never got it to work with Compiz.
Ever.  I struggled to get the open source drivers to do dual-head mode.
I even tried Win7 RC1 in the hope that that would at least allow me to benefit from my hardware investment.
Nope.

Needless to say, my new box has an nVidia card and RPMFusion-packaged closed-source drivers (which I just check are out before updating the kernel, unless it's critical.
I'll invest in nVidia because they invest in their customers.
</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805816</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30808418</id>
	<title>Re:Thank goodness for those drivers</title>
	<author>Hurricane78</author>
	<datestamp>1263832800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>What you two completely ignored, probably with your minds fully in the windows world:</p><p>A <em>installer</em>?? For <em>Linux?</em>??<br>How sick is that?</p><p>Linux has <em>package managers</em>. The package belongs into the repository, just like any other software.<br>Installers are Windows speak.</p><p>And those packages are a source package (e.g. source or binaries in tar.bz2), and a description file. Sometimes wrapped in one (e.g. RPM.)<br>This ensures comfortable installation, uninstallation, dependency management, updates/patches, etc.</p><p>Installers... silly, silly, silly...<br>And whining about &ldquo;having to use&rdquo; the CLI. As if that was a bad thing...<br>Oh boy, when minds are constrained, it&rsquo;s hard to free them...</p></htmltext>
<tokenext>What you two completely ignored , probably with your minds fully in the windows world : A installer ? ?
For Linux ? ?
? How sick is that ? Linux has package managers .
The package belongs into the repository , just like any other software.Installers are Windows speak.And those packages are a source package ( e.g .
source or binaries in tar.bz2 ) , and a description file .
Sometimes wrapped in one ( e.g .
RPM. ) This ensures comfortable installation , uninstallation , dependency management , updates/patches , etc.Installers... silly , silly , silly...And whining about    having to use    the CLI .
As if that was a bad thing...Oh boy , when minds are constrained , it    s hard to free them.. .</tokentext>
<sentencetext>What you two completely ignored, probably with your minds fully in the windows world:A installer??
For Linux??
?How sick is that?Linux has package managers.
The package belongs into the repository, just like any other software.Installers are Windows speak.And those packages are a source package (e.g.
source or binaries in tar.bz2), and a description file.
Sometimes wrapped in one (e.g.
RPM.)This ensures comfortable installation, uninstallation, dependency management, updates/patches, etc.Installers... silly, silly, silly...And whining about “having to use” the CLI.
As if that was a bad thing...Oh boy, when minds are constrained, it’s hard to free them...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805556</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805500</id>
	<title>Re:Thank goodness for those drivers</title>
	<author>rastilin</author>
	<datestamp>1263848160000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>So, Nvidia writes drivers for your system, and those drivers work. What's the problem? This is hardly a new situation, so presumably you knew this when you bought your Nvidia chipset.</p></htmltext>
<tokenext>So , Nvidia writes drivers for your system , and those drivers work .
What 's the problem ?
This is hardly a new situation , so presumably you knew this when you bought your Nvidia chipset .</tokentext>
<sentencetext>So, Nvidia writes drivers for your system, and those drivers work.
What's the problem?
This is hardly a new situation, so presumably you knew this when you bought your Nvidia chipset.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30819576</id>
	<title>Re:Thank goodness for those drivers</title>
	<author>bill\_mcgonigle</author>
	<datestamp>1263918420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>So, Nvidia writes drivers for your system, and those drivers work. What's the problem? </i></p><p>They blow in several directions.</p><p>I had an nVidia card in my MythTV box for the TV-out.  I upgraded my motherboard because the Intel mobo blew in other ways (it's fine in a server now, doing mundane server things, but don't try to push 'fancy' PCI cards with it).   The new mobo had an nVidia graphics chip built in.</p><p>Well, it turns out that the nVidia card I bought the year before was now a 'legacy' card.  It has a separate driver.  That driver can't be on the same machine with the new driver that's needed for the mobo.  So, I got a new nVidia TV-out card that is compatible with the mobo chipset.  Oh, well, they haven't bothered implementing TVOverscan for the 'new' driver yet, that's only available in the legacy driver, so my MythTV menus are off the screen.  Etc.</p><p>This kind of stuff is laughed at in the open source community.  Now, granted, nouveaux doesn't have TVOut support, yet, but when it does, it won't have random conflicts with other drivers.</p><p>With the next kernel I should be able to go back to the old TV out card and legacy driver and run the open source driver on the internal display.  Hurray, for getting back to square one.</p></htmltext>
<tokenext>So , Nvidia writes drivers for your system , and those drivers work .
What 's the problem ?
They blow in several directions.I had an nVidia card in my MythTV box for the TV-out .
I upgraded my motherboard because the Intel mobo blew in other ways ( it 's fine in a server now , doing mundane server things , but do n't try to push 'fancy ' PCI cards with it ) .
The new mobo had an nVidia graphics chip built in.Well , it turns out that the nVidia card I bought the year before was now a 'legacy ' card .
It has a separate driver .
That driver ca n't be on the same machine with the new driver that 's needed for the mobo .
So , I got a new nVidia TV-out card that is compatible with the mobo chipset .
Oh , well , they have n't bothered implementing TVOverscan for the 'new ' driver yet , that 's only available in the legacy driver , so my MythTV menus are off the screen .
Etc.This kind of stuff is laughed at in the open source community .
Now , granted , nouveaux does n't have TVOut support , yet , but when it does , it wo n't have random conflicts with other drivers.With the next kernel I should be able to go back to the old TV out card and legacy driver and run the open source driver on the internal display .
Hurray , for getting back to square one .</tokentext>
<sentencetext>So, Nvidia writes drivers for your system, and those drivers work.
What's the problem?
They blow in several directions.I had an nVidia card in my MythTV box for the TV-out.
I upgraded my motherboard because the Intel mobo blew in other ways (it's fine in a server now, doing mundane server things, but don't try to push 'fancy' PCI cards with it).
The new mobo had an nVidia graphics chip built in.Well, it turns out that the nVidia card I bought the year before was now a 'legacy' card.
It has a separate driver.
That driver can't be on the same machine with the new driver that's needed for the mobo.
So, I got a new nVidia TV-out card that is compatible with the mobo chipset.
Oh, well, they haven't bothered implementing TVOverscan for the 'new' driver yet, that's only available in the legacy driver, so my MythTV menus are off the screen.
Etc.This kind of stuff is laughed at in the open source community.
Now, granted, nouveaux doesn't have TVOut support, yet, but when it does, it won't have random conflicts with other drivers.With the next kernel I should be able to go back to the old TV out card and legacy driver and run the open source driver on the internal display.
Hurray, for getting back to square one.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805500</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30807358</id>
	<title>Re:Thank goodness for those drivers</title>
	<author>Anonymous</author>
	<datestamp>1263826620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I don't consider having to run<br>"nvidia-settings -a PixmapCache=0"<br>everytime my computer boots as meaning that the driver works.</p></htmltext>
<tokenext>I do n't consider having to run " nvidia-settings -a PixmapCache = 0 " everytime my computer boots as meaning that the driver works .</tokentext>
<sentencetext>I don't consider having to run"nvidia-settings -a PixmapCache=0"everytime my computer boots as meaning that the driver works.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805500</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806654</id>
	<title>Re:Thank goodness for those drivers</title>
	<author>Xeleema</author>
	<datestamp>1263821160000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Hm, to quote a near-forgotten troll; "You Do It Wrong"</p><p> <b>ProTip:</b>  Hit <a href="http://linuxquestions.org/" title="linuxquestions.org" rel="nofollow">linuxquestions.org</a> [linuxquestions.org] and post a detailed outline of your problem.  Be sure to include things like versions, names of distributions, and how many servers^H^H^H^H^H^H^H desktops you're having this issue on.</p><p>I'm sure you're not running X on bootup on a <i>server</i>, right?</p></div>
	</htmltext>
<tokenext>Hm , to quote a near-forgotten troll ; " You Do It Wrong " ProTip : Hit linuxquestions.org [ linuxquestions.org ] and post a detailed outline of your problem .
Be sure to include things like versions , names of distributions , and how many servers ^ H ^ H ^ H ^ H ^ H ^ H ^ H desktops you 're having this issue on.I 'm sure you 're not running X on bootup on a server , right ?</tokentext>
<sentencetext>Hm, to quote a near-forgotten troll; "You Do It Wrong" ProTip:  Hit linuxquestions.org [linuxquestions.org] and post a detailed outline of your problem.
Be sure to include things like versions, names of distributions, and how many servers^H^H^H^H^H^H^H desktops you're having this issue on.I'm sure you're not running X on bootup on a server, right?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805340</id>
	<title>Re:huh?</title>
	<author>Anonymous</author>
	<datestamp>1263845640000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>0</modscore>
	<htmltext>New Zealand is just a state of Australia, didn't you know?</htmltext>
<tokenext>New Zealand is just a state of Australia , did n't you know ?</tokentext>
<sentencetext>New Zealand is just a state of Australia, didn't you know?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805318</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30810732</id>
	<title>Re:Thank goodness for those drivers</title>
	<author>MSG</author>
	<datestamp>1263843720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>So I get very tired of hearing people badmouthing nVidia without giving an adequate reason why.</p></div><p>Here's mine: Times have changed.  The Free Software community has successfully convinced the large majority of those other vendors to support Free Software properly by releasing specifications.  Once upon a time, NVidia's support was "good" relative to other vendors (but, to be clear, no good in terms of the Free Software community's goals), but today better support is available from the other vendors.  Since NVidia's support for Linux and the Free Software community's goals is less good then their competitors, it is absolutely appropriate for users to say so.</p></div>
	</htmltext>
<tokenext>So I get very tired of hearing people badmouthing nVidia without giving an adequate reason why.Here 's mine : Times have changed .
The Free Software community has successfully convinced the large majority of those other vendors to support Free Software properly by releasing specifications .
Once upon a time , NVidia 's support was " good " relative to other vendors ( but , to be clear , no good in terms of the Free Software community 's goals ) , but today better support is available from the other vendors .
Since NVidia 's support for Linux and the Free Software community 's goals is less good then their competitors , it is absolutely appropriate for users to say so .</tokentext>
<sentencetext>So I get very tired of hearing people badmouthing nVidia without giving an adequate reason why.Here's mine: Times have changed.
The Free Software community has successfully convinced the large majority of those other vendors to support Free Software properly by releasing specifications.
Once upon a time, NVidia's support was "good" relative to other vendors (but, to be clear, no good in terms of the Free Software community's goals), but today better support is available from the other vendors.
Since NVidia's support for Linux and the Free Software community's goals is less good then their competitors, it is absolutely appropriate for users to say so.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805816</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805390</id>
	<title>Re:huh?</title>
	<author>maharius</author>
	<datestamp>1263846300000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>0</modscore>
	<htmltext>Ah so thats why Prince William went to NZ.</htmltext>
<tokenext>Ah so thats why Prince William went to NZ .</tokentext>
<sentencetext>Ah so thats why Prince William went to NZ.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805318</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806542</id>
	<title>Re:Year of the linux desktop</title>
	<author>Anonymous</author>
	<datestamp>1263819540000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Not yet, I have a problem when I plug/unplug an USB keyboard (usually after several times) and the Xorg server will crash.</p></htmltext>
<tokenext>Not yet , I have a problem when I plug/unplug an USB keyboard ( usually after several times ) and the Xorg server will crash .</tokentext>
<sentencetext>Not yet, I have a problem when I plug/unplug an USB keyboard (usually after several times) and the Xorg server will crash.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805224</parent>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806808
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805532
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805628
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30807484
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805394
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30807574
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805816
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805500
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805340
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805318
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30807134
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805610
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805876
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805484
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805318
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805722
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805552
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805394
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806178
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805610
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30811230
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30808418
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805556
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806508
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805610
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30815060
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805718
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805318
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30808372
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30808150
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806654
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30807358
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805500
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805368
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805318
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30819576
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805500
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806424
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805318
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805704
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805484
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805318
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806094
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30807014
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805816
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805500
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805596
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805318
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806720
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805224
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30808508
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806542
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805224
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805390
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805318
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30810732
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805816
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805500
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805772
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30809494
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806542
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805224
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805518
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806468
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30809922
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805224
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_0257232_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30815990
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805610
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_18_0257232.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805404
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_18_0257232.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805394
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805552
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30807484
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_18_0257232.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805318
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806424
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805596
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805484
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805704
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805876
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805390
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805340
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805718
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30815060
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805368
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_18_0257232.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805610
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30815990
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30807134
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806508
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806178
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_18_0257232.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805224
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806720
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806542
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30809494
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30808508
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30809922
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_18_0257232.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805214
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_18_0257232.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805374
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30808150
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805532
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30808372
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805518
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805556
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30808418
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30811230
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805722
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806808
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805628
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805772
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806094
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805500
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30805816
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30810732
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30807574
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30807014
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30819576
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30807358
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806468
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_0257232.30806654
</commentlist>
</conversation>
