1 <?xml version=
"1.0" encoding=
"ISO-8859-1"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/'
>
4 <title>Petter Reinholdtsen - Entries from June
2010</title>
5 <description>Entries from June
2010</description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
10 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
11 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
12 <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>
13 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
15 <p
>It is strange to watch how a bug in Debian causing KDM to fail to
16 start at boot when an NVidia video card is used is handled. The
17 problem seem to be that the nvidia X.org driver uses a long time to
18 initialize, and this duration is longer than kdm is configured to
21 <p
>I came across two bugs related to this issue,
22 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
23 against initscripts and passed on to nvidia-glx when it became obvious
24 that the nvidia drivers were involved, and
25 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
26 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
28 <p
>To me, it seem that no-one is interested in actually solving the
29 problem nvidia video card owners experience and make sure the Debian
30 distribution work out of the box for these users. The nvidia driver
31 maintainers expect kdm to be set up to wait longer, while kdm expect
32 the nvidia driver maintainers to fix the driver to start faster, and
33 while they wait for each other I guess the users end up switching to a
34 distribution that work for them. I have no idea what the solution is,
35 but I am pretty sure that waiting for each other is not it.
</p
>
37 <p
>I wonder why we end up handling bugs this way.
</p
>
42 <title>Togsatsing på norsk, mot sykkel
</title>
43 <link>http://people.skolelinux.org/pere/blog/Togsatsing_p___norsk__mot_sykkel.html
</link>
44 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Togsatsing_p___norsk__mot_sykkel.html
</guid>
45 <pubDate>Wed,
2 Jun
2010 23:
45:
00 +
0200</pubDate>
47 <p
>Det står dårlig til med toget når en finner på å la det
48 <a href=
"http://www.aftenposten.no/nyheter/iriks/article3677060.ece
">kappkjøre
49 med sykkel
</a
>... Jeg tror det trengs strukturendringer for å få
50 fikset på togproblemene i Norge.
</p
>
52 <p
>Mon tro hva toglinje mellom Narvik og Tromsø ville hatt slags
53 effekt på området der?
</p
>
58 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
59 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
60 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
61 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
63 <p
>When using sitesummary at a site to track machines, it is possible
64 to get a list of the machine types in use thanks to the DMI
65 information extracted from each machine. The script to do so is
66 included in the sitesummary package, and here is example output from
67 the Skolelinux build servers:
</p
>
69 <blockquote
><pre
>
70 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
72 Dell Computer Corporation
1
75 eserver xSeries
345 -[
8670M1X]-
1
79 </pre
></blockquote
>
81 <p
>The quality of the report depend on the quality of the DMI tables
82 provided in each machine. Here there are Intel machines without model
83 information listed with Intel as vendor and mo model, and virtual Xen
84 machines listed as [no-dmi-info]. One can add -l as a command line
85 option to list the individual machines.
</p
>
87 <p
>A larger list is
88 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
89 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
90 provide the basic sitesummary report publicly. In their report there
91 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
92 their machines, and as sitesummary is available in both distributions,
93 it is trivial to get all of them to report to the same central
99 <title>A manual for standards wars...
</title>
100 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
101 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
102 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
105 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
106 of Rob Weir
</a
> I came across the very interesting essay named
107 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
108 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
109 following the standards wars of today.
</p
>