blog/tags/debian/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2         "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html>
   4  <head>
   5   <title>Petter Reinholdtsen: Entries Tagged debian</title>
   6   <link rel="stylesheet" type="text/css" media="screen" href="../../style.css">
   7   <link rel="alternate" title="RSS Feed" href="debian.rss" type="application/rss+xml">
   8  </head>
   9  <body>
  10
  11  <div class="title">
  12   <h1>
  13        <a href="../../">Petter Reinholdtsen</a>
  14
  15   </h1>
  16
  17  </div>
  18
  19  <p>Entries tagged "debian".</p>
  20
  21
  22
  23
  24 <div class="entry">
  25  <div class="title">
  26  <a href="../../The_sorry_state_of_multimedia_browser_plugins_in_Debian.html">The sorry state of multimedia browser plugins in Debian</a>
  27  </div>
  28  <div class="date">
  29   2008-11-25 00:10
  30  </div>
  31
  32  <div class="body">
  33
  34 <p>Recently I have spent some time evaluating the multimedia browser
  35 plugins available in Debian Lenny, to see which one we should use by
  36 default in Debian Edu.  We need an embedded video playing plugin with
  37 control buttons to pause or stop the video, and capable of streaming
  38 all the multimedia content available on the web.  The test results and
  39 notes are available on
  40 <a href="http://wiki.debian.org/DebianEdu/BrowserMultimedia">the
  41 Debian wiki</a>.  I was surprised how few of the plugins are able to
  42 fill this need.  My personal video player favorite, VLC, has a really
  43 bad plugin which fail on a lot of the test pages.  A lot of the MIME
  44 types I would expect to work with any free software player (like
  45 video/ogg), just do not work.  And simple formats like the
  46 audio/x-mplegurl format (m3u playlists), just isn't supported by the
  47 totem and vlc plugins.  I hope the situation will improve soon.  No
  48 wonder sites use the proprietary Adobe flash to play video.</p>
  49
  50 <p>For Lenny, we seem to end up with the mplayer plugin.  It seem to
  51 be the only one fitting our needs. :/</p>
  52
  53  </div>
  54  <div class="tags">
  55
  56
  57
  58   Tags: <a href="../../tags/debian">debian</a>, <a href="../../tags/debian edu">debian edu</a>, <a href="../../tags/english">english</a>, <a href="../../tags/multimedia">multimedia</a>, <a href="../../tags/web">web</a>.
  59
  60  </div>
  61 </div>
  62 <div class="padding"></div>
  63
  64 <div class="entry">
  65  <div class="title">
  66  <a href="../../Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html">Devcamp brought us closer to the Lenny based Debian Edu release</a>
  67  </div>
  68  <div class="date">
  69   2008-12-07 12:00
  70  </div>
  71
  72  <div class="body">
  73
  74 <p>This weekend we had a small developer gathering for Debian Edu in
  75 Oslo.  Most of Saturday was used for the general assemly for the
  76 member organization, but the rest of the weekend I used to tune the
  77 LTSP installation.  LTSP now work out of the box on the 10-network.
  78 Acer Aspire One proved to be a very nice thin client, with both
  79 screen, mouse and keybard in a small box.  Was working on getting the
  80 diskless workstation setup configured out of the box, but did not
  81 finish it before the weekend was up.</p>
  82
  83 <p>Did not find time to look at the 4 VGA cards in one box we got from
  84 the Brazilian group, so that will have to wait for the next
  85 development gathering.  Would love to have the Debian Edu installer
  86 automatically detect and configure a multiseat setup when it find one
  87 of these cards.</p>
  88
  89  </div>
  90  <div class="tags">
  91
  92
  93
  94   Tags: <a href="../../tags/debian">debian</a>, <a href="../../tags/debian edu">debian edu</a>, <a href="../../tags/english">english</a>, <a href="../../tags/ltsp">ltsp</a>.
  95
  96  </div>
  97 </div>
  98 <div class="padding"></div>
  99
 100 <div class="entry">
 101  <div class="title">
 102  <a href="../../Endelig_er_Debian_Lenny_gitt_ut.html">Endelig er Debian Lenny gitt ut</a>
 103  </div>
 104  <div class="date">
 105   2009-02-15 11:50
 106  </div>
 107
 108  <div class="body">
 109
 110 <p>Endelig er <a href="http://www.debian.org/">Debian</a>
 111 <a href="http://www.debian.org/News/2009/20090214">Lenny</a> gitt ut.
 112 Et langt steg videre for Debian-prosjektet, og en rekke nye
 113 programpakker blir nå tilgjengelig for de av oss som bruker den
 114 stabile utgaven av Debian.  Neste steg er nå å få
 115 <a href="http://www.skolelinux.org/">Skolelinux</a> /
 116 <a href="http://wiki.debian.org/DebianEdu/">Debian Edu</a> ferdig
 117 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
 118 slippes løs på skolene.  Takk til alle debian-utviklerne som har
 119 gjort dette mulig.  Endelig er f.eks. fungerende avhengighetsstyrt
 120 bootsekvens tilgjengelig i stabil utgave, vha pakken
 121 <tt>insserv</tt>.</p>
 122
 123  </div>
 124  <div class="tags">
 125
 126
 127
 128   Tags: <a href="../../tags/debian">debian</a>, <a href="../../tags/debian edu">debian edu</a>, <a href="../../tags/norsk">norsk</a>.
 129
 130  </div>
 131 </div>
 132 <div class="padding"></div>
 133
 134 <div class="entry">
 135  <div class="title">
 136  <a href="../../Time_for_new__LDAP_schemas_replacing_RFC_2307_.html">Time for new  LDAP schemas replacing RFC 2307?</a>
 137  </div>
 138  <div class="date">
 139   2009-03-29 20:30
 140  </div>
 141
 142  <div class="body">
 143
 144 <p>The state of standardized LDAP schemas on Linux is far from
 145 optimal.  There is RFC 2307 documenting one way to store NIS maps in
 146 LDAP, and a modified version of this normally called RFC 2307bis, with
 147 some modifications to be compatible with Active Directory.  The RFC
 148 specification handle the content of a lot of system databases, but do
 149 not handle DNS zones and DHCP configuration.</p>
 150
 151 <p>In <a href="http://www.skolelinux.org/">Debian Edu/Skolelinux</a>,
 152 we would like to store information about users, SMB clients/hosts,
 153 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
 154 and LTSP configuration in LDAP.  These objects have a lot in common,
 155 but with the current LDAP schemas it is not possible to have one
 156 object per entity.  For example, one need to have at least three LDAP
 157 objects for a given computer, one with the SMB related stuff, one with
 158 DNS information and another with DHCP information.  The schemas
 159 provided for DNS and DHCP are impossible to combine into one LDAP
 160 object.  In addition, it is impossible to implement quick queries for
 161 netgroup membership, because of the way NIS triples are implemented.
 162 It just do not scale.  I believe it is time for a few RFC
 163 specifications to cleam up this mess.</p>
 164
 165 <p>I would like to have one LDAP object representing each computer in
 166 the network, and this object can then keep the SMB (ie host key), DHCP
 167 (mac address/name) and DNS (name/IP address) settings in one place.
 168 It need to be efficently stored to make sure it scale well.</p>
 169
 170 <p>I would also like to have a quick way to map from a user or
 171 computer and to the net group this user or computer is a member.</p>
 172
 173 <p>Active Directory have done a better job than unix heads like myself
 174 in this regard, and the unix side need to catch up.  Time to start a
 175 new IETF work group?</p>
 176
 177  </div>
 178  <div class="tags">
 179
 180
 181
 182   Tags: <a href="../../tags/debian">debian</a>, <a href="../../tags/debian edu">debian edu</a>, <a href="../../tags/english">english</a>, <a href="../../tags/nuug">nuug</a>.
 183
 184  </div>
 185 </div>
 186 <div class="padding"></div>
 187
 188 <div class="entry">
 189  <div class="title">
 190  <a href="../../Returning_from_Skolelinux_developer_gathering.html">Returning from Skolelinux developer gathering</a>
 191  </div>
 192  <div class="date">
 193   2009-03-29 21:00
 194  </div>
 195
 196  <div class="body">
 197
 198 <p>I'm sitting on the train going home from this weekends Debian
 199 Edu/Skolelinux development gathering.  I got a bit done tuning the
 200 desktop, and looked into the dynamic service location protocol
 201 implementation avahi.  It look like it could be useful for us.  Almost
 202 30 people participated, and I believe it was a great environment to
 203 get to know the Skolelinux system.  Walter Bender, involved in the
 204 development of the Sugar educational platform, presented his stuff and
 205 also helped me improve my OLPC installation.  He also showed me that
 206 his Turtle Art application can be used in standalone mode, and we
 207 agreed that I would help getting it packaged for Debian.  As a
 208 standalone application it would be great for Debian Edu.  We also
 209 tried to get the video conferencing working with two OLPCs, but that
 210 proved to be too hard for us.  The application seem to need more work
 211 before it is ready for me.  I look forward to getting home and relax
 212 now. :)</p>
 213
 214  </div>
 215  <div class="tags">
 216
 217
 218
 219   Tags: <a href="../../tags/debian">debian</a>, <a href="../../tags/debian edu">debian edu</a>, <a href="../../tags/english">english</a>, <a href="../../tags/nuug">nuug</a>.
 220
 221  </div>
 222 </div>
 223 <div class="padding"></div>
 224
 225 <div class="entry">
 226  <div class="title">
 227  <a href="../../Standardize_on_protocols_and_formats__not_vendors_and_applications.html">Standardize on protocols and formats, not vendors and applications</a>
 228  </div>
 229  <div class="date">
 230   2009-03-30 11:50
 231  </div>
 232
 233  <div class="body">
 234
 235 <p>Where I work at the University of Oslo, one decision stand out as a
 236 very good one to form a long lived computer infrastructure.  It is the
 237 simple one, lost by many in todays computer industry: Standardize on
 238 open network protocols and open exchange/storage formats, not applications.
 239 Applications come and go, while protocols and files tend to stay, and
 240 thus one want to make it easy to change application and vendor, while
 241 avoiding conversion costs and locking users to a specific platform or
 242 application.</p>
 243
 244 <p>This approach make it possible to replace the client applications
 245 independently of the server applications.  One can even allow users to
 246 use several different applications as long as they handle the selected
 247 protocol and format.  In the normal case, only one client application
 248 is recommended and users only get help if they choose to use this
 249 application, but those that want to deviate from the easy path are not
 250 blocked from doing so.</p>
 251
 252 <p>It also allow us to replace the server side without forcing the
 253 users to replace their applications, and thus allow us to select the
 254 best server implementation at any moment, when scale and resouce
 255 requirements change.</p>
 256
 257 <p>I strongly recommend standardizing - on open network protocols and
 258 open formats, but I would never recommend standardizing on a single
 259 application that do not use open network protocol or open formats.</p>
 260
 261  </div>
 262  <div class="tags">
 263
 264
 265
 266   Tags: <a href="../../tags/debian">debian</a>, <a href="../../tags/english">english</a>, <a href="../../tags/nuug">nuug</a>, <a href="../../tags/standard">standard</a>.
 267
 268  </div>
 269 </div>
 270 <div class="padding"></div>
 271
 272  <p style="text-align: right;"><a href="debian.rss"><img src="../../xml.gif" alt="RSS Feed" width="36" height="14"></a></p>
 273
 274
 275
 276
 277 <div id="sidebar">
 278
 279 <h2>Archive</h2>
 280 <ul>
 281
 282 <li>2009
 283 <ul>
 284
 285 <li><a href="../../archive/2009/01/">January (8)</a></li>
 286
 287 <li><a href="../../archive/2009/02/">February (8)</a></li>
 288
 289 <li><a href="../../archive/2009/03/">March (12)</a></li>
 290
 291 <li><a href="../../archive/2009/04/">April (2)</a></li>
 292
 293 </ul></li>
 294
 295 <li>2008
 296 <ul>
 297
 298 <li><a href="../../archive/2008/11/">November (5)</a></li>
 299
 300 <li><a href="../../archive/2008/12/">December (7)</a></li>
 301
 302 </ul></li>
 303
 304 </ul>
 305
 306
 307
 308 <h2>Tags</h2>
 309 <ul>
 310
 311  <li><a href="../../tags/3d-printer">3d-printer (9)</a></li>
 312
 313  <li><a href="../../tags/amiga">amiga (1)</a></li>
 314
 315  <li><a href="../../tags/aros">aros (1)</a></li>
 316
 317  <li><a href="../../tags/debian">debian (6)</a></li>
 318
 319  <li><a href="../../tags/debian edu">debian edu (6)</a></li>
 320
 321  <li><a href="../../tags/english">english (10)</a></li>
 322
 323  <li><a href="../../tags/fiksgatami">fiksgatami (1)</a></li>
 324
 325  <li><a href="../../tags/ltsp">ltsp (1)</a></li>
 326
 327  <li><a href="../../tags/multimedia">multimedia (2)</a></li>
 328
 329  <li><a href="../../tags/norsk">norsk (32)</a></li>
 330
 331  <li><a href="../../tags/nuug">nuug (32)</a></li>
 332
 333  <li><a href="../../tags/personvern">personvern (4)</a></li>
 334
 335  <li><a href="../../tags/reprap">reprap (9)</a></li>
 336
 337  <li><a href="../../tags/rss">rss (1)</a></li>
 338
 339  <li><a href="../../tags/standard">standard (2)</a></li>
 340
 341  <li><a href="../../tags/stavekontroll">stavekontroll (1)</a></li>
 342
 343  <li><a href="../../tags/video">video (6)</a></li>
 344
 345  <li><a href="../../tags/vitenskap">vitenskap (1)</a></li>
 346
 347  <li><a href="../../tags/web">web (2)</a></li>
 348
 349 </ul>
 350
 351 </div>
 352 </body>
 353 </html>