blog/tags/debian/debian.rss

   1 <?xml version="1.0" encoding="utf-8"?>
   2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
   3         <channel>
   4                 <title>Petter Reinholdtsen - Entries tagged debian</title>
   5                 <description>Entries tagged debian</description>
   6                 <link>../../</link>
   7
   8
   9         <item>
  10                 <title>The sorry state of multimedia browser plugins in Debian</title>
  11                 <link>../../The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
  12                 <guid isPermaLink="true">../../The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
  13                 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
  14                 <description>
  15 &lt;p&gt;Recently I have spent some time evaluating the multimedia browser
  16 plugins available in Debian Lenny, to see which one we should use by
  17 default in Debian Edu.  We need an embedded video playing plugin with
  18 control buttons to pause or stop the video, and capable of streaming
  19 all the multimedia content available on the web.  The test results and
  20 notes are available on
  21 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
  22 Debian wiki&lt;/a&gt;.  I was surprised how few of the plugins are able to
  23 fill this need.  My personal video player favorite, VLC, has a really
  24 bad plugin which fail on a lot of the test pages.  A lot of the MIME
  25 types I would expect to work with any free software player (like
  26 video/ogg), just do not work.  And simple formats like the
  27 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
  28 totem and vlc plugins.  I hope the situation will improve soon.  No
  29 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
  30
  31 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin.  It seem to
  32 be the only one fitting our needs. :/&lt;/p&gt;
  33 </description>
  34         </item>
  35
  36         <item>
  37                 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
  38                 <link>../../Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
  39                 <guid isPermaLink="true">../../Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
  40                 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
  41                 <description>
  42 &lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
  43 Oslo.  Most of Saturday was used for the general assemly for the
  44 member organization, but the rest of the weekend I used to tune the
  45 LTSP installation.  LTSP now work out of the box on the 10-network.
  46 Acer Aspire One proved to be a very nice thin client, with both
  47 screen, mouse and keybard in a small box.  Was working on getting the
  48 diskless workstation setup configured out of the box, but did not
  49 finish it before the weekend was up.&lt;/p&gt;
  50
  51 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
  52 the Brazilian group, so that will have to wait for the next
  53 development gathering.  Would love to have the Debian Edu installer
  54 automatically detect and configure a multiseat setup when it find one
  55 of these cards.&lt;/p&gt;
  56 </description>
  57         </item>
  58
  59         <item>
  60                 <title>Endelig er Debian Lenny gitt ut</title>
  61                 <link>../../Endelig_er_Debian_Lenny_gitt_ut.html</link>
  62                 <guid isPermaLink="true">../../Endelig_er_Debian_Lenny_gitt_ut.html</guid>
  63                 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
  64                 <description>
  65 &lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
  66 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
  67 Et langt steg videre for Debian-prosjektet, og en rekke nye
  68 programpakker blir nå tilgjengelig for de av oss som bruker den
  69 stabile utgaven av Debian.  Neste steg er nå å få
  70 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
  71 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
  72 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
  73 slippes løs på skolene.  Takk til alle debian-utviklerne som har
  74 gjort dette mulig.  Endelig er f.eks. fungerende avhengighetsstyrt
  75 bootsekvens tilgjengelig i stabil utgave, vha pakken
  76 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
  77 </description>
  78         </item>
  79
  80         <item>
  81                 <title>Time for new  LDAP schemas replacing RFC 2307?</title>
  82                 <link>../../Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
  83                 <guid isPermaLink="true">../../Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
  84                 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
  85                 <description>
  86 &lt;p&gt;The state of standardized LDAP schemas on Linux is far from
  87 optimal.  There is RFC 2307 documenting one way to store NIS maps in
  88 LDAP, and a modified version of this normally called RFC 2307bis, with
  89 some modifications to be compatible with Active Directory.  The RFC
  90 specification handle the content of a lot of system databases, but do
  91 not handle DNS zones and DHCP configuration.&lt;/p&gt;
  92
  93 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
  94 we would like to store information about users, SMB clients/hosts,
  95 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
  96 and LTSP configuration in LDAP.  These objects have a lot in common,
  97 but with the current LDAP schemas it is not possible to have one
  98 object per entity.  For example, one need to have at least three LDAP
  99 objects for a given computer, one with the SMB related stuff, one with
 100 DNS information and another with DHCP information.  The schemas
 101 provided for DNS and DHCP are impossible to combine into one LDAP
 102 object.  In addition, it is impossible to implement quick queries for
 103 netgroup membership, because of the way NIS triples are implemented.
 104 It just do not scale.  I believe it is time for a few RFC
 105 specifications to cleam up this mess.&lt;/p&gt;
 106
 107 &lt;p&gt;I would like to have one LDAP object representing each computer in
 108 the network, and this object can then keep the SMB (ie host key), DHCP
 109 (mac address/name) and DNS (name/IP address) settings in one place.
 110 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
 111
 112 &lt;p&gt;I would also like to have a quick way to map from a user or
 113 computer and to the net group this user or computer is a member.&lt;/p&gt;
 114
 115 &lt;p&gt;Active Directory have done a better job than unix heads like myself
 116 in this regard, and the unix side need to catch up.  Time to start a
 117 new IETF work group?&lt;/p&gt;
 118 </description>
 119         </item>
 120
 121         <item>
 122                 <title>Returning from Skolelinux developer gathering</title>
 123                 <link>../../Returning_from_Skolelinux_developer_gathering.html</link>
 124                 <guid isPermaLink="true">../../Returning_from_Skolelinux_developer_gathering.html</guid>
 125                 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
 126                 <description>
 127 &lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
 128 Edu/Skolelinux development gathering.  I got a bit done tuning the
 129 desktop, and looked into the dynamic service location protocol
 130 implementation avahi.  It look like it could be useful for us.  Almost
 131 30 people participated, and I believe it was a great environment to
 132 get to know the Skolelinux system.  Walter Bender, involved in the
 133 development of the Sugar educational platform, presented his stuff and
 134 also helped me improve my OLPC installation.  He also showed me that
 135 his Turtle Art application can be used in standalone mode, and we
 136 agreed that I would help getting it packaged for Debian.  As a
 137 standalone application it would be great for Debian Edu.  We also
 138 tried to get the video conferencing working with two OLPCs, but that
 139 proved to be too hard for us.  The application seem to need more work
 140 before it is ready for me.  I look forward to getting home and relax
 141 now. :)&lt;/p&gt;
 142 </description>
 143         </item>
 144
 145         <item>
 146                 <title>Standardize on protocols and formats, not vendors and applications</title>
 147                 <link>../../Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
 148                 <guid isPermaLink="true">../../Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
 149                 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
 150                 <description>
 151 &lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
 152 very good one to form a long lived computer infrastructure.  It is the
 153 simple one, lost by many in todays computer industry: Standardize on
 154 open network protocols and open exchange/storage formats, not applications.
 155 Applications come and go, while protocols and files tend to stay, and
 156 thus one want to make it easy to change application and vendor, while
 157 avoiding conversion costs and locking users to a specific platform or
 158 application.&lt;/p&gt;
 159
 160 &lt;p&gt;This approach make it possible to replace the client applications
 161 independently of the server applications.  One can even allow users to
 162 use several different applications as long as they handle the selected
 163 protocol and format.  In the normal case, only one client application
 164 is recommended and users only get help if they choose to use this
 165 application, but those that want to deviate from the easy path are not
 166 blocked from doing so.&lt;/p&gt;
 167
 168 &lt;p&gt;It also allow us to replace the server side without forcing the
 169 users to replace their applications, and thus allow us to select the
 170 best server implementation at any moment, when scale and resouce
 171 requirements change.&lt;/p&gt;
 172
 173 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
 174 open formats, but I would never recommend standardizing on a single
 175 application that do not use open network protocol or open formats.&lt;/p&gt;
 176 </description>
 177         </item>
 178
 179         </channel>
 180 </rss>