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 <div class="entry">
 273  <div class="title">
 274  <a href="../../No_patch_is_not_better_than_a_useless_patch.html">No patch is not better than a useless patch</a>
 275  </div>
 276  <div class="date">
 277   2009-04-28 09:30
 278  </div>
 279
 280  <div class="body">
 281
 282 <p>Julien Blache
 283 <a href="http://blog.technologeek.org/2009/04/12/214">claim that no
 284 patch is better than a useless patch</a>.  I completely disagree, as a
 285 patch allow one to discuss a concrete and proposed solution, and also
 286 prove that the issue at hand is important enough for someone to spent
 287 time on fixing it.  No patch do not provide any of these positive
 288 properties.</p>
 289
 290  </div>
 291  <div class="tags">
 292
 293
 294
 295   Tags: <a href="../../tags/debian">debian</a>, <a href="../../tags/english">english</a>, <a href="../../tags/nuug">nuug</a>.
 296
 297  </div>
 298 </div>
 299 <div class="padding"></div>
 300
 301 <div class="entry">
 302  <div class="title">
 303  <a href="../../Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html">Two projects that have improved the quality of free software a lot</a>
 304  </div>
 305  <div class="date">
 306   2009-05-02 15:00
 307  </div>
 308
 309  <div class="body">
 310
 311 <p>There are two software projects that have had huge influence on the
 312 quality of free software, and I wanted to mention both in case someone
 313 do not yet know them.</p>
 314
 315 <p>The first one is <a href="http://valgrind.org/">valgrind</a>, a
 316 tool to detect and expose errors in the memory handling of programs.
 317 It is easy to use, all one need to do is to run 'valgrind program',
 318 and it will report any problems on stdout.  It is even better if the
 319 program include debug information.  With debug information, it is able
 320 to report the source file name and line number where the problem
 321 occurs.  It can report things like 'reading past memory block in file
 322 X line N, the memory block was allocated in file Y, line M', and
 323 'using uninitialised value in control logic'.  This tool has made it
 324 trivial to investigate reproducible crash bugs in programs, and have
 325 reduced the number of this kind of bugs in free software a lot.
 326
 327 <p>The second one is
 328 <a href="http://en.wikipedia.org/wiki/Coverity">Coverity</a> which is
 329 a source code checker.  It is able to process the source of a program
 330 and find problems in the logic without running the program.  It
 331 started out as the Stanford Checker and became well known when it was
 332 used to find bugs in the Linux kernel.  It is now a commercial tool
 333 and the company behind it is running
 334 <a href="http://www.scan.coverity.com/">a community service</a> for the
 335 free software community, where a lot of free software projects get
 336 their source checked for free.  Several thousand defects have been
 337 found and fixed so far.  It can find errors like 'lock L taken in file
 338 X line N is never released if exiting in line M', or 'the code in file
 339 Y lines O to P can never be executed'.  The projects included in the
 340 community service project have managed to get rid of a lot of
 341 reliability problems thanks to Coverity.</p>
 342
 343 <p>I believe tools like this, that are able to automatically find
 344 errors in the source, are vital to improve the quality of software and
 345 make sure we can get rid of the crashing and failing software we are
 346 surrounded by today.</p>
 347
 348  </div>
 349  <div class="tags">
 350
 351
 352
 353   Tags: <a href="../../tags/debian">debian</a>, <a href="../../tags/english">english</a>.
 354
 355  </div>
 356 </div>
 357 <div class="padding"></div>
 358
 359 <div class="entry">
 360  <div class="title">
 361  <a href="../../Kryptert_harddisk___naturligvis.html">Kryptert harddisk - naturligvis</a>
 362  </div>
 363  <div class="date">
 364   2009-05-02 15:30
 365  </div>
 366
 367  <div class="body">
 368
 369 <p><a href="http://www.dagensit.no/trender/article1658676.ece">Dagens
 370 IT melder</a> at Intel hevder at det er dyrt å miste en datamaskin,
 371 når en tar tap av arbeidstid, fortrolige dokumenter,
 372 personopplysninger og alt annet det innebærer.  Det er ingen tvil om
 373 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
 374 til at jeg har kryptert harddisken på både kontormaskinen og min
 375 bærbare.  Begge inneholder personopplysninger jeg ikke ønsker skal
 376 komme på avveie, den første informasjon relatert til jobben min ved
 377 Universitetet i Oslo, og den andre relatert til blant annet
 378 foreningsarbeide.  Kryptering av diskene gjør at det er lite
 379 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
 380 av dem.  Maskinene låses automatisk etter noen minutter uten bruk,
 381 og en reboot vil gjøre at de ber om passord før de vil starte opp.
 382 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
 383 gjør det trivielt å sette opp krypterte disker.  Jeg har LVM på toppen
 384 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
 385 Jeg anbefaler alle å kryptere diskene på sine bærbare.  Kostnaden når
 386 det er gjort slik jeg gjør det er minimale, og gevinstene er
 387 betydelige.  En bør dog passe på passordet.  Hvis det går tapt, må
 388 maskinen reinstalleres og alt er tapt.</p>
 389
 390 <p>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
 391 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
 392 krypteringsnøklene.  Kostnaden med å forsvare seg mot slike angripere
 393 er for min del høyere enn gevinsten.  Jeg tror oddsene for at
 394 f.eks. etteretningsorganisasjoner har glede av å titte på mine
 395 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
 396 gjøre det vanskeligere for angripere med kompetanse og ressurser er
 397 betydelige.</p>
 398
 399  </div>
 400  <div class="tags">
 401
 402
 403
 404   Tags: <a href="../../tags/debian">debian</a>, <a href="../../tags/norsk">norsk</a>, <a href="../../tags/nuug">nuug</a>, <a href="../../tags/sikkerhet">sikkerhet</a>.
 405
 406  </div>
 407 </div>
 408 <div class="padding"></div>
 409
 410 <div class="entry">
 411  <div class="title">
 412  <a href="../../IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html">IDG mener linux i servermarkedet vil vokse med 21% i 2009</a>
 413  </div>
 414  <div class="date">
 415   2009-05-07 22:30
 416  </div>
 417
 418  <div class="body">
 419
 420 <p>Kom over
 421 <a href="http://news.cnet.com/8301-13505_3-10216873-16.html">interessante
 422 tall</a> fra IDG om utviklingen av linuxservermarkedet.  Fikk meg til
 423 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
 424 jobber til daglig.  En rask opptelling forteller meg at vi har 490
 425 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
 426 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere.  Med den
 427 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.</p>
 428
 429  </div>
 430  <div class="tags">
 431
 432
 433
 434   Tags: <a href="../../tags/debian">debian</a>, <a href="../../tags/norsk">norsk</a>, <a href="../../tags/nuug">nuug</a>.
 435
 436  </div>
 437 </div>
 438 <div class="padding"></div>
 439
 440 <div class="entry">
 441  <div class="title">
 442  <a href="../../BSAs_p__stander_om_piratkopiering_m__ter_motstand.html">BSAs påstander om piratkopiering møter motstand</a>
 443  </div>
 444  <div class="date">
 445   2009-05-17 23:05
 446  </div>
 447
 448  <div class="body">
 449
 450 <p>Hvert år de siste årene har BSA, lobbyfronten til de store
 451 programvareselskapene som Microsoft og Apple, publisert en rapport der
 452 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
 453 ulike land rundt om i verden.  Resultatene er tendensiøse.  For noen
 454 dager siden kom
 455 <a href="http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf">siste
 456 rapport</a>, og det er flere kritiske kommentarer publisert de siste
 457 dagene.  Et spesielt interessant kommentar fra Sverige,
 458 <a href="http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror">BSA
 459 höftade Sverigesiffror</a>, oppsummeres slik:</p>
 460
 461 <blockquote>
 462 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
 463 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
 464 företag. "Man bör nog kanske inte se de här siffrorna som helt
 465 exakta", säger BSAs Sverigechef John Hugosson.
 466 </blockquote>
 467
 468 <p>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge?  To andre kommentarer er <a
 469 href="http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality">BSA
 470 piracy figures need a shot of reality</a> og <a
 471 href="http://www.michaelgeist.ca/content/view/3958/125/">Does The WIPO
 472 Copyright Treaty Work?</a></p>
 473
 474 <p>Fant lenkene via <a
 475 href="http://tech.slashdot.org/article.pl?sid=09/05/17/1632242">oppslag
 476 på Slashdot</a>.</p>
 477
 478  </div>
 479  <div class="tags">
 480
 481
 482
 483   Tags: <a href="../../tags/debian">debian</a>, <a href="../../tags/debian edu">debian edu</a>, <a href="../../tags/fildeling">fildeling</a>, <a href="../../tags/norsk">norsk</a>, <a href="../../tags/nuug">nuug</a>, <a href="../../tags/opphavsrett">opphavsrett</a>, <a href="../../tags/personvern">personvern</a>.
 484
 485  </div>
 486 </div>
 487 <div class="padding"></div>
 488
 489 <div class="entry">
 490  <div class="title">
 491  <a href="../../Debian_boots_quicker_and_quicker.html">Debian boots quicker and quicker</a>
 492  </div>
 493  <div class="date">
 494   2009-06-24 21:40
 495  </div>
 496
 497  <div class="body">
 498
 499 <p>I spent Monday and tuesday this week in London with a lot of the
 500 people involved in the boot system on Debian and Ubuntu, to see if we
 501 could find more ways to speed up the boot system.  This was an Ubuntu
 502 funded
 503 <a href="https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint">developer
 504 gathering</a>. It was quite productive.  We also discussed the future
 505 of boot systems, and ways to handle the increasing number of boot
 506 issues introduced by the Linux kernel becoming more and more
 507 asynchronous and event base.  The Ubuntu approach using udev and
 508 upstart might be a good way forward.  Time will show.</p>
 509
 510 <p>Anyway, there are a few ways at the moment to speed up the boot
 511 process in Debian.  All of these should be applied to get a quick
 512 boot:</p>
 513
 514 <ul>
 515
 516 <li>Use dash as /bin/sh.</li>
 517
 518 <li>Disable the init.d/hwclock*.sh scripts and make sure the hardware
 519    clock is in UTC.</li>
 520
 521 <li>Install and activate the insserv package to enable
 522    <a href="http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot">dependency
 523    based boot sequencing</a>, and enable concurrent booting.</li>
 524
 525 </ul>
 526
 527 These points are based on the Google summer of code work done by
 528 <a href="http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/">Carlos
 529 Villegas</a>.
 530
 531 <p>Support for makefile-style concurrency during boot was uploaded to
 532 unstable yesterday.  When we tested it, we were able to cut 6 seconds
 533 from the boot sequence.  It depend on very correct dependency
 534 declaration in all init.d scripts, so I expect us to find edge cases
 535 where the dependences in some scripts are slightly wrong when we start
 536 using this.</p>
 537
 538 <p>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
 539 introduced by Raphael Geissert today, one that could affect the
 540 startup speed as well.  Instead of starting some scripts concurrently
 541 from rcS.d/ and another set of scripts from rc2.d/, it would be
 542 possible to run a of them in the same process.  A quick way to test
 543 this would be to enable insserv and run 'mv /etc/rc2.d/S* /etc/rcS.d/;
 544 insserv'.  Will need to test if that work. :)</p>
 545
 546  </div>
 547  <div class="tags">
 548
 549
 550
 551   Tags: <a href="../../tags/debian">debian</a>, <a href="../../tags/english">english</a>.
 552
 553  </div>
 554 </div>
 555 <div class="padding"></div>
 556
 557 <div class="entry">
 558  <div class="title">
 559  <a href="../../Taking_over_sysvinit_development.html">Taking over sysvinit development</a>
 560  </div>
 561  <div class="date">
 562   2009-07-22 23:00
 563  </div>
 564
 565  <div class="body">
 566
 567 <p>After several years of frustration with the lack of activity from
 568 the existing sysvinit upstream developer, I decided a few weeks ago to
 569 take over the package and become the new upstream.  The number of
 570 patches to track for the Debian package was becoming a burden, and the
 571 lack of synchronization between the distribution made it hard to keep
 572 the package up to date.</p>
 573
 574 <p>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
 575 and my Debian co-maintainer Kel Modderman.  About 10 days ago, I made
 576 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
 577 and Fedora), based on the patches currently in use in these
 578 distributions.  We Debian maintainers plan to move to this tarball as
 579 the new upstream as soon as we find time to do the merge.  Since the
 580 new tarball was created, we agreed with Werner at SuSe to make a new
 581 upstream project at <a href="http://savannah.nongnu.org/">Savannah</a>, and continue
 582 development there.  The project is registered and currently waiting
 583 for approval by the Savannah administrators, and as soon as it is
 584 approved, we will import the old versions from svn and continue
 585 working on the future release.</p>
 586
 587 <p>It is a bit ironic that this is done now, when some of the involved
 588 distributions are moving to upstart as a syvinit replacement.</p>
 589
 590  </div>
 591  <div class="tags">
 592
 593
 594
 595   Tags: <a href="../../tags/debian">debian</a>, <a href="../../tags/english">english</a>, <a href="../../tags/nuug">nuug</a>.
 596
 597  </div>
 598 </div>
 599 <div class="padding"></div>
 600
 601 <div class="entry">
 602  <div class="title">
 603  <a href="../../Debian_has_switched_to_dependency_based_boot_sequencing.html">Debian has switched to dependency based boot sequencing</a>
 604  </div>
 605  <div class="date">
 606   2009-07-27 23:50
 607  </div>
 608
 609  <div class="body">
 610
 611 <p>Since this evening, with the upload of sysvinit version 2.87dsf-2,
 612 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
 613 have been migrated to using dependency based boot sequencing.  This
 614 conclude work me and others have been doing for the last three days.
 615 It feels great to see this finally part of the default Debian
 616 installation.  Now we just need to weed out the last few problems that
 617 are bound to show up, to get everything ready for Squeeze.</p>
 618
 619 <p>The next step is migrating /sbin/init from sysvinit to upstart, and
 620 fixing the more fundamental problem of handing the event based
 621 non-predictable kernel in the early boot.</p>
 622
 623  </div>
 624  <div class="tags">
 625
 626
 627
 628   Tags: <a href="../../tags/debian">debian</a>, <a href="../../tags/english">english</a>, <a href="../../tags/nuug">nuug</a>.
 629
 630  </div>
 631 </div>
 632 <div class="padding"></div>
 633
 634  <p style="text-align: right;"><a href="debian.rss"><img src="../../xml.gif" alt="RSS Feed" width="36" height="14"></a></p>
 635
 636
 637
 638
 639 <div id="sidebar">
 640
 641 <h2>Archive</h2>
 642 <ul>
 643
 644 <li>2010
 645 <ul>
 646
 647 <li><a href="../../archive/2010/01/">January (1)</a></li>
 648
 649 </ul></li>
 650
 651 <li>2009
 652 <ul>
 653
 654 <li><a href="../../archive/2009/01/">January (8)</a></li>
 655
 656 <li><a href="../../archive/2009/02/">February (8)</a></li>
 657
 658 <li><a href="../../archive/2009/03/">March (12)</a></li>
 659
 660 <li><a href="../../archive/2009/04/">April (10)</a></li>
 661
 662 <li><a href="../../archive/2009/05/">May (9)</a></li>
 663
 664 <li><a href="../../archive/2009/06/">June (3)</a></li>
 665
 666 <li><a href="../../archive/2009/07/">July (4)</a></li>
 667
 668 <li><a href="../../archive/2009/08/">August (3)</a></li>
 669
 670 <li><a href="../../archive/2009/09/">September (1)</a></li>
 671
 672 <li><a href="../../archive/2009/10/">October (2)</a></li>
 673
 674 <li><a href="../../archive/2009/11/">November (3)</a></li>
 675
 676 <li><a href="../../archive/2009/12/">December (3)</a></li>
 677
 678 </ul></li>
 679
 680 <li>2008
 681 <ul>
 682
 683 <li><a href="../../archive/2008/11/">November (5)</a></li>
 684
 685 <li><a href="../../archive/2008/12/">December (7)</a></li>
 686
 687 </ul></li>
 688
 689 </ul>
 690
 691
 692
 693 <h2>Tags</h2>
 694 <ul>
 695
 696  <li><a href="../../tags/3d-printer">3d-printer (11)</a></li>
 697
 698  <li><a href="../../tags/amiga">amiga (1)</a></li>
 699
 700  <li><a href="../../tags/aros">aros (1)</a></li>
 701
 702  <li><a href="../../tags/debian">debian (14)</a></li>
 703
 704  <li><a href="../../tags/debian edu">debian edu (10)</a></li>
 705
 706  <li><a href="../../tags/english">english (18)</a></li>
 707
 708  <li><a href="../../tags/fiksgatami">fiksgatami (1)</a></li>
 709
 710  <li><a href="../../tags/fildeling">fildeling (5)</a></li>
 711
 712  <li><a href="../../tags/kart">kart (2)</a></li>
 713
 714  <li><a href="../../tags/lenker">lenker (1)</a></li>
 715
 716  <li><a href="../../tags/ltsp">ltsp (1)</a></li>
 717
 718  <li><a href="../../tags/multimedia">multimedia (5)</a></li>
 719
 720  <li><a href="../../tags/norsk">norsk (61)</a></li>
 721
 722  <li><a href="../../tags/nuug">nuug (63)</a></li>
 723
 724  <li><a href="../../tags/opphavsrett">opphavsrett (10)</a></li>
 725
 726  <li><a href="../../tags/personvern">personvern (10)</a></li>
 727
 728  <li><a href="../../tags/reprap">reprap (10)</a></li>
 729
 730  <li><a href="../../tags/rss">rss (1)</a></li>
 731
 732  <li><a href="../../tags/sikkerhet">sikkerhet (5)</a></li>
 733
 734  <li><a href="../../tags/standard">standard (9)</a></li>
 735
 736  <li><a href="../../tags/stavekontroll">stavekontroll (1)</a></li>
 737
 738  <li><a href="../../tags/video">video (10)</a></li>
 739
 740  <li><a href="../../tags/vitenskap">vitenskap (1)</a></li>
 741
 742  <li><a href="../../tags/web">web (5)</a></li>
 743
 744 </ul>
 745
 746 </div>
 747 </body>
 748 </html>