Julien Blache +claim that no +patch is better than a useless patch. I completely disagree, as a +patch allow one to discuss a concrete and proposed solution, and also +prove that the issue at hand is important enough for someone to spent +time on fixing it. No patch do not provide any of these positive +properties.
+Slashdot melder at EU-parlamentet har vedtatt +å +øke vernetiden for musikkopptak fra 50 til 70 år, og dermed rane +fellesskapet for 20 år med musikk som ville vært tilgjengelig uten +bruksbegresninger. Mon tro hvor mye musikk som vil gå tapt pga. at +ingen tar vare på den (opphavsrettsinnehaver er forsvunnet), mens +ingen andre har lov til å kopiere og distribuere den. Mon tro hvor +mange musikkstykker som ikke kan brukes uten bruksbegresninger av +folket, som skulle falt i det fri men som i stedet forblir under +rettighetshavers monopol. Opphavsrettslovgivingen blir mer og mer +urimelig. Tenke seg til at vernetiden startet i USA med 7 år og +mulighet for forlengelse med 7 år. Nå er den 95 år der, og en stor +mengde verk blir foreldreløse og umulig å få tak i. Har ikke lykkes +med å finne ut hvor lang opphavsretten var i utgangspunktet i Norge. +I dag er den 70 år.
+ +Jeg er glad det finnes så mye +musikk tilgjengelig uten bruksbegresninger at en kan klare seg +uten musikk med bruksbegresninger.
+Dagens nyhet er at omsetningen til Microsoft for første gang er +synkende. Ikke spesielt uventet med den generelle nedgangen i +økonomien som vi ser verden over. Det fikk meg dog til å tenke på en +ting fra noen år tilbake.
+ +Da jeg besøkte en kamerat i Beijing sommeren 2000, ble jeg fortalt +at påstanden til Microsoft om at de brakte inn enorme pengesummer til +USA nok var litt overdrevet, da de fleste inntektene fra lisenssalg +rundt om i verden ble kanalisert inn til skatteparadiset +Cayman +Island. Jeg har aldri lykkes med å få bekreftet dette påstanden, +men tok i dag en titt på hvilke selskaper som eier de norske delene av +Microsoft som jeg kjenner til, dvs. +Microsoft +Norge AS og +FAST, +A Microsoft Subsidiary (tidligere FAST Search & Transfer ASA).
+ +Førstnevnte er eid av "Microsoft International Holdings Spain +S.R.L.", mens sistnevnte i følge Wikipedia nå eies av +Microsoft-underselskapet "MACS Holdings Limited". Jeg har ikke klart +å finne mer informasjon om noen av disse. Mon tro om noen av dem +sender pengene til Cayman Island? Finner det jeg tror er +informasjon +om spaniaselskapet på spansk, men jeg kan ikke lese spansk. :(
+Where I work at the University of Oslo, one decision stand out as a -very good one to form a long lived computer infrastructure. It is the -simple one, lost by many in todays computer industry: Standardize on -open network protocols and open exchange/storage formats, not applications. -Applications come and go, while protocols and files tend to stay, and -thus one want to make it easy to change application and vendor, while -avoiding conversion costs and locking users to a specific platform or -application.
- -This approach make it possible to replace the client applications -independently of the server applications. One can even allow users to -use several different applications as long as they handle the selected -protocol and format. In the normal case, only one client application -is recommended and users only get help if they choose to use this -application, but those that want to deviate from the easy path are not -blocked from doing so.
- -It also allow us to replace the server side without forcing the -users to replace their applications, and thus allow us to select the -best server implementation at any moment, when scale and resouce -requirements change.
- -I strongly recommend standardizing - on open network protocols and -open formats, but I would never recommend standardizing on a single -application that do not use open network protocol or open formats.
-I'm sitting on the train going home from this weekends Debian -Edu/Skolelinux development gathering. I got a bit done tuning the -desktop, and looked into the dynamic service location protocol -implementation avahi. It look like it could be useful for us. Almost -30 people participated, and I believe it was a great environment to -get to know the Skolelinux system. Walter Bender, involved in the -development of the Sugar educational platform, presented his stuff and -also helped me improve my OLPC installation. He also showed me that -his Turtle Art application can be used in standalone mode, and we -agreed that I would help getting it packaged for Debian. As a -standalone application it would be great for Debian Edu. We also -tried to get the video conferencing working with two OLPCs, but that -proved to be too hard for us. The application seem to need more work -before it is ready for me. I look forward to getting home and relax -now. :)
-The state of standardized LDAP schemas on Linux is far from -optimal. There is RFC 2307 documenting one way to store NIS maps in -LDAP, and a modified version of this normally called RFC 2307bis, with -some modifications to be compatible with Active Directory. The RFC -specification handle the content of a lot of system databases, but do -not handle DNS zones and DHCP configuration.
- -In Debian Edu/Skolelinux, -we would like to store information about users, SMB clients/hosts, -filegroups, netgroups (users and hosts), DHCP and DNS configuration, -and LTSP configuration in LDAP. These objects have a lot in common, -but with the current LDAP schemas it is not possible to have one -object per entity. For example, one need to have at least three LDAP -objects for a given computer, one with the SMB related stuff, one with -DNS information and another with DHCP information. The schemas -provided for DNS and DHCP are impossible to combine into one LDAP -object. In addition, it is impossible to implement quick queries for -netgroup membership, because of the way NIS triples are implemented. -It just do not scale. I believe it is time for a few RFC -specifications to cleam up this mess.
- -I would like to have one LDAP object representing each computer in -the network, and this object can then keep the SMB (ie host key), DHCP -(mac address/name) and DNS (name/IP address) settings in one place. -It need to be efficently stored to make sure it scale well.
- -I would also like to have a quick way to map from a user or -computer and to the net group this user or computer is a member.
- -Active Directory have done a better job than unix heads like myself -in this regard, and the unix side need to catch up. Time to start a -new IETF work group?
-