1 <?xml version=
"1.0" encoding=
"utf-8"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/'
>
4 <title>Petter Reinholdtsen - Entries tagged debian
</title>
5 <description>Entries tagged debian
</description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
10 <title>The sorry state of multimedia browser plugins in Debian
</title>
11 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
13 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
15 <p
>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 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
22 Debian wiki
</a
>. 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
'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.
</p
>
31 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
32 be the only one fitting our needs. :/
</p
>
37 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
38 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
39 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
40 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
42 <p
>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.
</p
>
51 <p
>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.
</p
>
60 <title>Endelig er Debian Lenny gitt ut
</title>
61 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
62 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
63 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
65 <p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
66 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> 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 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
71 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> 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 <tt
>insserv
</tt
>.
</p
>
81 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
82 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
83 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
84 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
86 <p
>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.
</p
>
93 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
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.
</p
>
107 <p
>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.
</p
>
112 <p
>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.
</p
>
115 <p
>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?
</p
>
122 <title>Returning from Skolelinux developer gathering
</title>
123 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
124 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
125 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
127 <p
>I
'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
146 <title>Standardize on protocols and formats, not vendors and applications
</title>
147 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
148 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
149 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
151 <p
>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.
</p
>
160 <p
>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.
</p
>
168 <p
>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.
</p
>
173 <p
>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.
</p
>
180 <title>No patch is not better than a useless patch
</title>
181 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
182 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
183 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
185 <p
>Julien Blache
186 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
187 patch is better than a useless patch
</a
>. I completely disagree, as a
188 patch allow one to discuss a concrete and proposed solution, and also
189 prove that the issue at hand is important enough for someone to spent
190 time on fixing it. No patch do not provide any of these positive
191 properties.
</p
>
196 <title>Two projects that have improved the quality of free software a lot
</title>
197 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
198 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
199 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
201 <p
>There are two software projects that have had huge influence on the
202 quality of free software, and I wanted to mention both in case someone
203 do not yet know them.
</p
>
205 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
206 tool to detect and expose errors in the memory handling of programs.
207 It is easy to use, all one need to do is to run
'valgrind program
',
208 and it will report any problems on stdout. It is even better if the
209 program include debug information. With debug information, it is able
210 to report the source file name and line number where the problem
211 occurs. It can report things like
'reading past memory block in file
212 X line N, the memory block was allocated in file Y, line M
', and
213 'using uninitialised value in control logic
'. This tool has made it
214 trivial to investigate reproducible crash bugs in programs, and have
215 reduced the number of this kind of bugs in free software a lot.
217 <p
>The second one is
218 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
219 a source code checker. It is able to process the source of a program
220 and find problems in the logic without running the program. It
221 started out as the Stanford Checker and became well known when it was
222 used to find bugs in the Linux kernel. It is now a commercial tool
223 and the company behind it is running
224 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
225 free software community, where a lot of free software projects get
226 their source checked for free. Several thousand defects have been
227 found and fixed so far. It can find errors like
'lock L taken in file
228 X line N is never released if exiting in line M
', or
'the code in file
229 Y lines O to P can never be executed
'. The projects included in the
230 community service project have managed to get rid of a lot of
231 reliability problems thanks to Coverity.
</p
>
233 <p
>I believe tools like this, that are able to automatically find
234 errors in the source, are vital to improve the quality of software and
235 make sure we can get rid of the crashing and failing software we are
236 surrounded by today.
</p
>
241 <title>Kryptert harddisk - naturligvis
</title>
242 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
243 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
244 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
246 <p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
247 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
248 når en tar tap av arbeidstid, fortrolige dokumenter,
249 personopplysninger og alt annet det innebærer. Det er ingen tvil om
250 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
251 til at jeg har kryptert harddisken på både kontormaskinen og min
252 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
253 komme på avveie, den første informasjon relatert til jobben min ved
254 Universitetet i Oslo, og den andre relatert til blant annet
255 foreningsarbeide. Kryptering av diskene gjør at det er lite
256 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
257 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
258 og en reboot vil gjøre at de ber om passord før de vil starte opp.
259 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
260 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
261 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
262 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
263 det er gjort slik jeg gjør det er minimale, og gevinstene er
264 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
265 maskinen reinstalleres og alt er tapt.
</p
>
267 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
268 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
269 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
270 er for min del høyere enn gevinsten. Jeg tror oddsene for at
271 f.eks. etteretningsorganisasjoner har glede av å titte på mine
272 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
273 gjøre det vanskeligere for angripere med kompetanse og ressurser er
274 betydelige.
</p
>
279 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
280 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
281 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
282 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
285 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
286 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
287 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
288 jobber til daglig. En rask opptelling forteller meg at vi har
490
289 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
290 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
291 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
296 <title>BSAs påstander om piratkopiering møter motstand
</title>
297 <link>http://people.skolelinux.org/pere/blog/BSAs_p__stander_om_piratkopiering_m__ter_motstand.html
</link>
298 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p__stander_om_piratkopiering_m__ter_motstand.html
</guid>
299 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
301 <p
>Hvert år de siste årene har BSA, lobbyfronten til de store
302 programvareselskapene som Microsoft og Apple, publisert en rapport der
303 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
304 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
306 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
307 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
308 dagene. Et spesielt interessant kommentar fra Sverige,
309 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
310 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
313 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
314 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
315 företag.
"Man bör nog kanske inte se de här siffrorna som helt
316 exakta
", säger BSAs Sverigechef John Hugosson.
319 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
320 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
321 piracy figures need a shot of reality
</a
> og
<a
322 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
323 Copyright Treaty Work?
</a
></p
>
325 <p
>Fant lenkene via
<a
326 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
327 på Slashdot
</a
>.
</p
>
332 <title>Debian boots quicker and quicker
</title>
333 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
334 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
335 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
337 <p
>I spent Monday and tuesday this week in London with a lot of the
338 people involved in the boot system on Debian and Ubuntu, to see if we
339 could find more ways to speed up the boot system. This was an Ubuntu
341 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
342 gathering
</a
>. It was quite productive. We also discussed the future
343 of boot systems, and ways to handle the increasing number of boot
344 issues introduced by the Linux kernel becoming more and more
345 asynchronous and event base. The Ubuntu approach using udev and
346 upstart might be a good way forward. Time will show.
</p
>
348 <p
>Anyway, there are a few ways at the moment to speed up the boot
349 process in Debian. All of these should be applied to get a quick
354 <li
>Use dash as /bin/sh.
</li
>
356 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
357 clock is in UTC.
</li
>
359 <li
>Install and activate the insserv package to enable
360 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
361 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
365 These points are based on the Google summer of code work done by
366 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
369 <p
>Support for makefile-style concurrency during boot was uploaded to
370 unstable yesterday. When we tested it, we were able to cut
6 seconds
371 from the boot sequence. It depend on very correct dependency
372 declaration in all init.d scripts, so I expect us to find edge cases
373 where the dependences in some scripts are slightly wrong when we start
374 using this.
</p
>
376 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
377 introduced by Raphael Geissert today, one that could affect the
378 startup speed as well. Instead of starting some scripts concurrently
379 from rcS.d/ and another set of scripts from rc2.d/, it would be
380 possible to run a of them in the same process. A quick way to test
381 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
382 insserv
'. Will need to test if that work. :)
</p
>
387 <title>Taking over sysvinit development
</title>
388 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
389 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
390 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
392 <p
>After several years of frustration with the lack of activity from
393 the existing sysvinit upstream developer, I decided a few weeks ago to
394 take over the package and become the new upstream. The number of
395 patches to track for the Debian package was becoming a burden, and the
396 lack of synchronization between the distribution made it hard to keep
397 the package up to date.
</p
>
399 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
400 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
401 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
402 and Fedora), based on the patches currently in use in these
403 distributions. We Debian maintainers plan to move to this tarball as
404 the new upstream as soon as we find time to do the merge. Since the
405 new tarball was created, we agreed with Werner at SuSe to make a new
406 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
407 development there. The project is registered and currently waiting
408 for approval by the Savannah administrators, and as soon as it is
409 approved, we will import the old versions from svn and continue
410 working on the future release.
</p
>
412 <p
>It is a bit ironic that this is done now, when some of the involved
413 distributions are moving to upstart as a syvinit replacement.
</p
>
418 <title>Debian has switched to dependency based boot sequencing
</title>
419 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
420 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
421 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
423 <p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
424 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
425 have been migrated to using dependency based boot sequencing. This
426 conclude work me and others have been doing for the last three days.
427 It feels great to see this finally part of the default Debian
428 installation. Now we just need to weed out the last few problems that
429 are bound to show up, to get everything ready for Squeeze.
</p
>
431 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
432 fixing the more fundamental problem of handing the event based
433 non-predictable kernel in the early boot.
</p
>
438 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
439 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
440 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
441 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
443 <p
>These days, the init.d script dependencies in Squeeze are quite
444 complete, so complete that it is actually possible to run all the
445 init.d scripts in parallell based on these dependencies. If you want
446 to test your Squeeze system, make sure
447 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
448 based boot sequencing
</a
> is enabled, and add this line to
449 /etc/default/rcS:
</p
>
451 <blockquote
><pre
>
453 </pre
></blockquote
>
455 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
456 scripts in parallel using the dependency information stored in
457 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
458 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
459 to try to start the kdm and gdm scripts as early as possible, and will
460 start the facilities required by kdm or gdm as early as possible to
461 make this happen.
</p
>
463 <p
>Give it a try, and see if you like the result. If some services
464 fail to start properly, it is most likely because they have incomplete
465 init.d script dependencies in their startup script (or some of their
466 dependent scripts have incomplete dependencies). Report bugs and get
467 the package maintainers to fix it. :)
</p
>
469 <p
>Running scripts in parallel could be the default in Debian when we
470 manage to get the init.d script dependencies complete and correct. I
471 expect we will get there in Squeeze+
1, if we get manage to test and
472 fix the remaining issues.
</p
>
474 <p
>If you report any problems with dependencies in init.d scripts to
475 the BTS, please usertag the report to get it to show up at
476 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
477 list of usertagged bugs related to this
</a
>.
</p
>
482 <title>systemd, an interesting alternative to upstart
</title>
483 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
484 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
485 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
487 <p
>The last few days a new boot system called
488 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
490 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
492 to the free software world. I have not yet had time to play around
493 with it, but it seem to be a very interesting alternative to
494 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
495 a good alternative for Debian when we are able to switch to an event
496 based boot system. Tollef is
497 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
498 systemd into Debian, and I look forward to seeing how well it work. I
499 like the fact that systemd handles init.d scripts with dependency
500 information natively, allowing them to run in parallel where upstart
501 at the moment do not.
</p
>
503 <p
>Unfortunately do systemd have the same problem as upstart regarding
504 platform support. It only work on recent Linux kernels, and also need
505 some new kernel features enabled to function properly. This means
506 kFreeBSD and Hurd ports of Debian will need a port or a different boot
507 system. Not sure how that will be handled if systemd proves to be the
508 way forward.
</p
>
510 <p
>In the mean time, based on the
511 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
512 on debian-devel@
</a
> regarding parallel booting in Debian, I have
513 decided to enable full parallel booting as the default in Debian as
514 soon as possible (probably this weekend or early next week), to see if
515 there are any remaining serious bugs in the init.d dependencies. A
516 new version of the sysvinit package implementing this change is
517 already in experimental. If all go well, Squeeze will be released
518 with parallel booting enabled by default.
</p
>
523 <title>Sitesummary tip: Listing MAC address of all clients
</title>
524 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
525 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
526 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
528 <p
>In the recent Debian Edu versions, the
529 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
530 system
</a
> is used to keep track of the machines in the school
531 network. Each machine will automatically report its status to the
532 central server after boot and once per night. The network setup is
533 also reported, and using this information it is possible to get the
534 MAC address of all network interfaces in the machines. This is useful
535 to update the DHCP configuration.
</p
>
537 <p
>To give some idea how to use sitesummary, here is a one-liner to
538 ist all MAC addresses of all machines reporting to sitesummary. Run
539 this on the collector host:
</p
>
541 <blockquote
><pre
>
542 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
543 </pre
></blockquote
>
545 <p
>This will list all MAC addresses assosiated with all machine, one
546 line per machine and with space between the MAC addresses.
</p
>
548 <p
>To allow system administrators easier job at adding static DHCP
549 addresses for hosts, it would be possible to extend this to fetch
550 machine information from sitesummary and update the DHCP and DNS
551 tables in LDAP using this information. Such tool is unfortunately not
552 written yet.
</p
>
557 <title>Parallellized boot is now the default in Debian/unstable
</title>
558 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
559 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
560 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
562 <p
>Since this evening, parallel booting is the default in
563 Debian/unstable for machines using dependency based boot sequencing.
564 Apparently the testing of concurrent booting has been wider than
565 expected, if I am to believe the
566 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
567 on debian-devel@
</a
>, and I concluded a few days ago to move forward
568 with the feature this weekend, to give us some time to detect any
569 remaining problems before Squeeze is frozen. If serious problems are
570 detected, it is simple to change the default back to sequential boot.
571 The upload of the new sysvinit package also activate a new upstream
574 More information about
575 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
576 based boot sequencing
</a
> is available from the Debian wiki. It is
577 currently possible to disable parallel booting when one run into
578 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
580 <blockquote
><pre
>
582 </pre
></blockquote
>
584 <p
>If you report any problems with dependencies in init.d scripts to
585 the BTS, please usertag the report to get it to show up at
586 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
587 list of usertagged bugs related to this
</a
>.
</p
>
592 <title>More flexible firmware handling in debian-installer
</title>
593 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
594 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
595 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
597 <p
>After a long break from debian-installer development, I finally
598 found time today to return to the project. Having to spend less time
599 working dependency based boot in debian, as it is almost complete now,
600 definitely helped freeing some time.
</p
>
602 <p
>A while back, I ran into a problem while working on Debian Edu. We
603 include some firmware packages on the Debian Edu CDs, those needed to
604 get disk and network controllers working. Without having these
605 firmware packages available during installation, it is impossible to
606 install Debian Edu on the given machine, and because our target group
607 are non-technical people, asking them to provide firmware packages on
608 an external medium is a support pain. Initially, I expected it to be
609 enough to include the firmware packages on the CD to get
610 debian-installer to find and use them. This proved to be wrong.
611 Next, I hoped it was enough to symlink the relevant firmware packages
612 to some useful location on the CD (tried /cdrom/ and
613 /cdrom/firmware/). This also proved to not work, and at this point I
614 found time to look at the debian-installer code to figure out what was
615 going to work.
</p
>
617 <p
>The firmware loading code is in the hw-detect package, and a closer
618 look revealed that it would only look for firmware packages outside
619 the installation media, so the CD was never checked for firmware
620 packages. It would only check USB sticks, floppies and other
621 "external
" media devices. Today I changed it to also look in the
622 /cdrom/firmware/ directory on the mounted CD or DVD, which should
623 solve the problem I ran into with Debian edu. I also changed it to
624 look in /firmware/, to make sure the installer also find firmware
625 provided in the initrd when booting the installer via PXE, to allow us
626 to provide the same feature in the PXE setup included in Debian
629 <p
>To make sure firmware deb packages with a license questions are not
630 activated without asking if the license is accepted, I extended
631 hw-detect to look for preinst scripts in the firmware packages, and
632 run these before activating the firmware during installation. The
633 license question is asked using debconf in the preinst, so this should
634 solve the issue for the firmware packages I have looked at so far.
</p
>
636 <p
>If you want to discuss the details of these features, please
637 contact us on debian-boot@lists.debian.org.
</p
>
642 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
643 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
644 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
645 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
647 <p
>A few days ago, parallel booting was enabled in Debian/testing.
648 The feature seem to hold up pretty well, but three fairly serious
649 issues are known and should be solved:
653 <li
>The wicd package seen to
654 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
655 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
656 parallel booting is enabled. No idea why, but the wicd maintainer
657 seem to be on the case.
</li
>
659 <li
>The nvidia X driver seem to
660 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
661 triggered more easily when parallel booting is in effect. The
662 maintainer is on the case.
</li
>
664 <li
>The sysv-rc package fail to properly enable dependency based boot
665 sequencing (the shutdown is broken) when old file-rc users
666 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
667 sysv-rc. One way to solve it would be for file-rc to create
668 /etc/init.d/.legacy-bootordering, and another is to try to make
669 sysv-rc more robust. Will investigate some more and probably upload a
670 workaround in sysv-rc to help those trying to move from file-rc to
671 sysv-rc get a working shutdown.
</li
>
673 </ul
></p
>
675 <p
>All in all not many surprising issues, and all of them seem
676 solvable before Squeeze is released. In addition to these there are
677 some packages with bugs in their dependencies and run level settings,
678 which I expect will be fixed in a reasonable time span.
</p
>
680 <p
>If you report any problems with dependencies in init.d scripts to
681 the BTS, please usertag the report to get it to show up at
682 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
683 list of usertagged bugs related to this
</a
>.
</p
>
685 <p
>Update: Correct bug number to file-rc issue.
</p
>
690 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
691 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
692 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</guid>
693 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
695 <p
>It is strange to watch how a bug in Debian causing KDM to fail to
696 start at boot when an NVidia video card is used is handled. The
697 problem seem to be that the nvidia X.org driver uses a long time to
698 initialize, and this duration is longer than kdm is configured to
701 <p
>I came across two bugs related to this issue,
702 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
703 against initscripts and passed on to nvidia-glx when it became obvious
704 that the nvidia drivers were involved, and
705 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
706 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
708 <p
>To me, it seem that no-one is interested in actually solving the
709 problem nvidia video card owners experience and make sure the Debian
710 distribution work out of the box for these users. The nvidia driver
711 maintainers expect kdm to be set up to wait longer, while kdm expect
712 the nvidia driver maintainers to fix the driver to start faster, and
713 while they wait for each other I guess the users end up switching to a
714 distribution that work for them. I have no idea what the solution is,
715 but I am pretty sure that waiting for each other is not it.
</p
>
717 <p
>I wonder why we end up handling bugs this way.
</p
>
722 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
723 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
724 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
725 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
727 <p
>When using sitesummary at a site to track machines, it is possible
728 to get a list of the machine types in use thanks to the DMI
729 information extracted from each machine. The script to do so is
730 included in the sitesummary package, and here is example output from
731 the Skolelinux build servers:
</p
>
733 <blockquote
><pre
>
734 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
736 Dell Computer Corporation
1
739 eserver xSeries
345 -[
8670M1X]-
1
743 </pre
></blockquote
>
745 <p
>The quality of the report depend on the quality of the DMI tables
746 provided in each machine. Here there are Intel machines without model
747 information listed with Intel as vendor and mo model, and virtual Xen
748 machines listed as [no-dmi-info]. One can add -l as a command line
749 option to list the individual machines.
</p
>
751 <p
>A larger list is
752 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
753 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
754 provide the basic sitesummary report publicly. In their report there
755 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
756 their machines, and as sitesummary is available in both distributions,
757 it is trivial to get all of them to report to the same central
763 <title>A manual for standards wars...
</title>
764 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
765 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
766 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
769 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
770 of Rob Weir
</a
> I came across the very interesting essay named
771 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
772 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
773 following the standards wars of today.
</p
>
778 <title>Upstart or sysvinit - as init.d scripts see it
</title>
779 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
780 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
781 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
783 <p
>If Debian is to migrate to upstart on Linux, I expect some init.d
784 scripts to migrate (some of) their operations to upstart job while
785 keeping the init.d for hurd and kfreebsd. The packages with such
786 needs will need a way to get their init.d scripts to behave
787 differently when used with sysvinit and with upstart. Because of
788 this, I had a look at the environment variables set when a init.d
789 script is running under upstart, and when it is not.
</p
>
791 <p
>With upstart, I notice these environment variables are set when a
792 script is started from rcS.d/ (ignoring some irrelevant ones like
795 <blockquote
><pre
>
801 UPSTART_EVENTS=startup
803 UPSTART_JOB=rc-sysinit
804 </pre
></blockquote
>
806 <p
>With sysvinit, these environment variables are set for the same
809 <blockquote
><pre
>
810 INIT_VERSION=sysvinit-
2.88
815 </pre
></blockquote
>
817 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
818 sysvinit are not set by upstart. Not sure if it is intentional or not
819 to not be compatible with sysvinit in this regard.
</p
>
821 <p
>For scripts needing to behave differently when upstart is used,
822 looking for the UPSTART_JOB environment variable seem to be a good