#tyndur · 2010-01-20

172 Nachrichten · Seite 1 von 1 · Original-CSV herunterladen

  1. kwolfMoin
  2. pcmattmanHi kwolf
  3. FreakyPenguinMoin kwolf
  4. kwolfFinally got back a usable X configuration. Never do distribution upgrades...
  5. pcmattmanUgh, X
  6. kwolfIf you got a laptop with closed lid and an external monitor, what do you want?
  7. kwolfRight, a desktop spanning both internal and external monitor
  8. kwolf*argh*
  9. FreakyPenguinWell then, just dont use X ;-)
  10. quokeveryone knows X is shit :)
  11. kwolfAnd then I had to get the DPI right again
  12. kwolfThe only thing still missing now is the KDE 2 style window decoration ;-)
  13. FreakyPenguin*g*
  14. kwolfProduces only random noise in the title bar for me with F12
  15. pcmattmanEvery time I try and do anything in X I reboot and find myself stuck at a shell
  16. kwolfWell, it's not to hard to get it starting anymore. The hard part is to make it do what you want...
  17. FreakyPenguinkwolf: Shouldn't the monitor config just be a oneliner with xrandr?
  18. kwolfThat's basically what I ended up doing, yes
  19. quokwait.. that works? :P
  20. pcmattmanA one-liner for monitor config?
  21. quokI've never had luck getting multimonitor stuff to work in X that easily
  22. FreakyPenguinWell it works for me ;-)
  23. pcmattmanMultiple monitors and X usually ends up taking hours on my end with lots of time on a shell
  24. FreakyPenguinwtf? ;-)
  25. quokthe easiest time I had getting multimonitor to work with X, I had 9 monitors all the same size arranged in a 3x3 grid
  26. kwolfThere is no reasonable GUI, but xrandr has always worked fine for me until now
  27. kwolfOnly two monitors, though ;-)
  28. quokI jsut moved them around physically until I got the layout that X gave me into something reasonable :)
  29. pcmattmanSee, I just open Windows display properties, move the little screen, press "OK", and it's done ;)
  30. pcmattmanMy last X config I ended up handwriting the xorg.conf because none of the tools did it right
  31. kwolfSee, I don't even need the mouse ;-)
  32. FreakyPenguinpcmattman: And I type xrandr ... and it's done too ;-)
  33. kwolfFirst I tried to use xorg.conf, too - old habit
  34. kwolfBut using xrandr in a new X init script turned out to be much easier
  35. pcmattmanWell, I used everything *else* (the video driver tools, x's tools) and then gave up and wrote it myself
  36. pcmattmanI will certainly look at xrandr now though, I'm interested in this concept
  37. FreakyPenguinI just have a set of scripts for my different configs at home and at work so that I don't have to read the manpage every morning. *g*
  38. kwolfNacked-by: Kevin Wolf <kwolf@tyndur.org>
  39. quokhaha
  40. pcmattmanActually, you'd be more likely to commit suicide first
  41. kwolfOops, wrong address ;-)
  42. quokokay well it's after 3am here
  43. quokI'm going to head to bed
  44. FreakyPenguingn8 ;-)
  45. pcmattmanNight quok
  46. quokgn8 :)
  47. kwolfgn8 quok
  48. pcmattmanAlthough, if there's any time where porting X might work, it'd be 3 am
  49. pcmattmanYou'd be thinking straight otherwise ;)
  50. kwolf*lol*
  51. quokpcmattman: even at 3am, I'm not crazy enough to try porting X :)
  52. pcmattmanMore alchohol then
  53. pcmattman;)
  54. quokI want to live to see my kids grow up and have their own kids.
  55. quokfriends don't let friends port X
  56. pcmattmanSo very true
  57. quokthat should be a new meme of some kind
  58. pcmattmanHow many of the original X devs are still alive?
  59. kwolfpcmattman: Hm, looks like nobody wants to discuss with us on cdi-devel
  60. pcmattmanI'd say that means everyone loves the idea ;)
  61. kwolfI guess so
  62. kwolfI mean it's obvious that everyone must love it, it's _our_ idea after all
  63. pcmattmanHaha, true :)
  64. quokHmmm, 3 hours later I shall respond
  65. quokI want
  66. quok:)
  67. kwolfquok, what are you doing here? You should sleep!
  68. FreakyPenguinWho needs more than 3 hours of sleep? ;-)
  69. FreakyPenguin3.5? ;-)
  70. kwolfWell, you were saying "need", not "get", right? ;-)
  71. FreakyPenguin*g*
  72. kwolfAnd I seem to remember that you didn't sleep much less than I did last time ;-)
  73. quokOn call for work... got a call, had to work an issue
  74. kwolfMay I ask what work you do?
  75. quokI work for Sprint / Nextel as Tier 3 tech support
  76. quokon the text messaging team
  77. quokit's horrible horrible work. They're taking away my RHEL and moving me to OpenVMS :(
  78. quokon the bright side, I do get to work with clusters, and that's always fun.
  79. quokand "tier 3 tech support" isn't really right, as it's more network engineering and sysadmin work than tech support.
  80. kwolfObviously I can't approve of moving away from RHEL ;-)
  81. quokwell, we are in the middle of switching from an old messaging platform to a new one.
  82. quokthe old one all ran on Solaris and RHEL. The only real reason for switching is the old vendor and Sprint couldn't reach an agreement on support costs and all.
  83. kwolfDoes it happen often that you need to be on call?
  84. quokactually, this new vendor replaces two old vendors. The other vendor it is replacing used a combo of RHEL and OpenVMS. There is still a very little bit of RHEL involved with the new vendor, but it's mostly OpenVMS :(
  85. quokonce week of day on call and one week of night on call every 10 weeks
  86. kwolfCould probably be worse, but still sounds annoying
  87. quokit use to be that the day and night on calls were handled by the same person, but it got to be too much to handle. Too many people were getting sick from losing too much sleep. It wasn't uncommon to work over 120 hours those weeks.
  88. quokwhen I joined the team, I said there was no way in hell I'd do that. If I hit 60 hours during on-call week, I'd just stop answering the phone. I can't go without that much sleep.
  89. quokwell, I use to be able to as I've had bad insomnia for years, but I've recently been diagnosed with restless leg syndrome. The treatments for that allow me to sleep peacefully again. :)
  90. kwolf120h/week? Wait, how many hours does a week have again? 178h or something?
  91. kwolfOnly 168 even
  92. kwolfIs having to work that much even legal?
  93. kwolfOh well, I guess in the US it might actually be...
  94. quokquite unfortunately, yes
  95. quokgot things all wrapped up for work now though, so I'm heading to bed again
  96. kwolfIt's this kind of stuff why I'm actually quite happy to live in socialist Europe ;-)
  97. kwolfOk, good night again
  98. quokwe should just push the continents all back together again, name the whole thing Europe, and let everyone live there
  99. quokExcept those pesky Australians. We'll conveniently forget to include them in our new super continent, and make it a penal colony again. ;)
  100. kwolf*lol*
  101. kwolfpcmattman seems to sleep already
  102. taljethMoin moin
  103. taljeth(for a change ;-))
  104. XanClicMoin, moin, taljeth
  105. Homixwenn ich ein zeichen übergeben muss in C, der Parameter aber char* ist, dann muss ich "N" schreiben, wenn es nur char ist, dann 'N' oder?
  106. XanClicJop
  107. taljethHm, "N" ist dasselbe wie (const char[]) { 'N', '\0' }, oder?
  108. taljethEigentlich hab ich mir noch nie näher Gedanken drüber gemacht, was das ganz genau ist
  109. XanClicIch hätte eigentlich eher const char* gesagt
  110. XanClicUnd nicht const char[]
  111. taljethAber const char* kann ich nicht so initialisieren
  112. taljethOder?
  113. XanClicNicht?
  114. XanClicAso
  115. XanClicHm
  116. taljethWeiß ich doch nicht
  117. taljethAber wieso sollte ich einen Pointer so initialisieren können?
  118. XanClicAber bei einem const char[] muss man normalerweise & benutzen, um die Adresse bekommen
  119. XanClic+zu
  120. XanClicUnd das muss man bei "" nicht
  121. FreakyPenguinHm? :/
  122. XanClicAlso wenn es global ist
  123. taljethLern C, Max...
  124. XanClicZumindest meckert mein GCC dann immer ;-)
  125. taljethArrays und Pointer sind doch mehr oder weniger dasselbe
  126. XanClicJo, klar
  127. XanClicDas hab ich auch versucht, unserem Übungsleiter zu erklären *g*
  128. taljethWenn du ein Array deklarierst, brauchst du da doch kein & mehr, um einen Pointer zu bekommen?
  129. XanClicHm, ich hatte das so in Erinnerung...
  130. XanClicWenn nicht, ist ja alles OK
  131. taljethWenn du einen Pointer auf das erste Element brauchst, kannst du höchstens noch &foo[0] machen
  132. XanClicHm, stimmt
  133. taljethWas halt dasselbe wie foo ist
  134. XanClicGCC hält nicht zu mir
  135. XanClicEs fällt mir in den Rücken
  136. taljethDas Compiler?
  137. taljethDu machst das nur, um quok zu irritieren, gib's zu
  138. XanClicNein, das Collection ;-)
  139. taljethAutsch. Das war kein schöner Zug, XanClic.
  140. taljethDann müsste es ja die GCC sein. Das geht doch mal gar nicht. ;-)
  141. XanClic*g*
  142. taljethObwohl, für die Collection geht es eigentlich schon. Aber für den Compiler halt nicht.
  143. XanClicIch meinte halt "das Programm" ;-)
  144. Homixhm ok ich mach jetzt einfach ein pointer auf ein char ;) aber es funktioniert trotzdem noch nicht ...
  145. taljethXanClic: Die Collection ist aber nicht nur ein Programm ;-)
  146. XanClicHomix: Nullbyte bedacht?
  147. XanClictaljeth: Meh ;-)
  148. Homixna ja char* kann ja wirklich nur ein Pointer auf ein einziges Zeichen sein
  149. Homixdabei steht ja folgende beschreibung: CHARACTER*1
  150. taljethWas hast du denn genau vor, Homix?
  151. Homixdie intel mkl benutzen für eine sparse matrix - vektor multiplikation :)
  152. XanClicchar* kann schon auf mehr Zeigen
  153. XanClic*zeigen
  154. XanClicvoid* zeigt ja auch nicht auf nichts ;-)
  155. Homixhttp://www.intel.com/software/products/mkl/docs/webhelp/bla/functn_mkl_dcsrgemv.html#functn_mkl_dcsrgemv
  156. taljethXanClic: Manchmal schon, vor allem auf externes Nichts ;-)
  157. XanClic*g*
  158. Homixdie funktion wird zwar schön ausgeführt (und auch entsprechend schnell), aber die internet check-funktion meint, das ergebnis sei fehlerhaft :/
  159. XanClicWird überbewertet ;-)
  160. Homixdas ist doof
  161. Homixich mein, die check-funktion kann ich locker aus dem source verschwinden lassen ... aber ich will trotzdem sichergehen ... nicht dass die funktion für was ganz anderes da ist, oder für einen anderen anwendungsfall ;)
  162. Homixeh irgendwie komisch
  163. Homixparameter m : INTEGER. Number of rows of the matrix A.
  164. Homixaber wird nicht direkt übergeben, sondern ein pointer darauf? : int *m ^^
  165. taljethSind wir hier übrigens nicht ein bisschen ECHAN?
  166. Homixnein ;)
  167. Homixich will jetzt reden und frust abbauen ;)
  168. XanClicGeht auch in #lost ;-)
  169. XanClicAber quok freut sich über jedes bisschen Deutsch, das er bekommt, da bin ich mir sicher ;-)
  170. Homixachso lol, hab ich gar nicht gemerkt dass ich nicht in #lost bin ... :)
  171. taljethHm, ist ein komisches Interface
  172. taljethAber wenn es Call by Reference sein soll vielleicht...