rampke.de Archive

Technikfashionvictimhipster

20 June 2011

Mein Telefon ist ein Motorola Milestone – als ich mir das Ende 2009 geholt habe hat sich das gerade auch mein halber Bekanntenkreis angeschafft und (damals) für gut befunden. Sonst hätte ich’s auch wahrscheinlich nicht genommen.

Mein UPTÄCKA-Rucksack ist unglaublich praktisch – zuerst gesehen habe ich ihn bei Philip, der ihn gekauft hat, weil er ihn bei Julian gesehen hat.

Heute verschickt wird mein nächster MP3-Player, mal sehen ob er meinen leider etwas zu grob behandelten iPod ersetzen können wird. Darauf, dass er dafür geeignet sein könnte, hat mich Svenja gebracht.

Ich kaufe, was ich bei anderen Leuten gesehen und für interessant gefunden habe. Bin ich ein Technikfashionvictim?

Wenn jemensch Klamotten anzieht, die er_sie irgendwo gesehen und für schön befunden hat, ist er_sie dann ein Fashion victim? Hört doch einfach auf, Leute nach euren Ansprüchen an Originalität und Individualität zu messen, und lasst sie einfach machen, ja? Bittedanke.

First_post

17 June 2011

This is the first post to this example blog. To add new posts, just add This is the first post to this example blog. To add new posts, just add files to the posts/ subdirectory, or use the web form.

Wege

29 May 2011

Durch Berlin geht eine Linie. Meistens ist sie unsichtbar, an einigen Stellen ist sie durch eine Doppelreihe Kopfsteinpflaster markiert, hier und da eine Infotafel. Durch Berlin geht eine Linie. Meistens ist sie unsichtbar, an einigen Stellen ist sie durch eine Doppelreihe Kopfsteinpflaster markiert, hier und da eine Infotafel.

Die Straßenbahn endet an der Björnsonstraße. Es ist Nacht, da kommt das vor. Es ist nicht mehr weit, auf die nächste, die durchfährt, zu warten lohnt nicht. Ein paar Meter, eine Infotafel. Einmal nicht vorbeigehen, lesen, obwohl Du die ganze Geschichte eigentlich schon kennst.

Kurz innehalten.

Weitergehen, bewusster. Über die Bösebrücke, mit jedem Schritt wissend, dass es nicht selbstverständlich ist, dass Du hier mit einem Sterni in der Hand in deine Westberliner Wohnung gehst.

Patient

21 February 2011

1

1

We both signed our forms in large, clumsy letters and handed them over. It was the only legal act still required to be spelt out on paper and signed in handwriting: The Death Wish, the only escape from the endless cycle of Rebirth and Rejuvenation.

2

Thirty-eight years later, our bodies were long past the point at which they would—normally—have been replaced and recycled. I decided to end it, then and there.

“We did it. We grew old together.” There was no need to say any more. We had talked about this moment, long and often.

3

You don’t take luggage on your last journey. We arrived at the rooftop in time to see the sunset, a sight now seen far too rarely by anyone. When the first towers were built, they offered the most amazing view, the almost black sky above, the earth curving away, thinly veiled by the athmosphere. Now it’s all just metal, concrete and fog.

Nowadays, almost no one ever goes to the roofs, except for those who come to jump. There were a few, but they kept to themselves. Dying is a very personal experience, even after you’ve done it a dozen times.

Twelve hundred stories is a long drop.

4

I woke up in the Tank and began inspecting my new body, female this time. Small, sturdy butches were all the rage lately, so I had chosen to be tall, slender, feminine. It works better when you stand out.

I pushed the button. The fluid was drained and I started to breathe air again. I checked out at the reception, but—as always—refused to disclose my former identity. Only one thing knew whom I had been: the Core, the central computer managing all those deaths, resurrections, reformations and changes. It is a dumb machine, a leftover from the old days. No one would have it any other way, it is tried and true technology—the only piece of equipment on which all our lives really depend. Artificial Intelligences make our lives easy, but you cannot trust a machine that is smarter than all of humanity combined. The Core can be trusted because it has no will, only programming.

And somewhere in its database I am marked as suicidal. Barely anyone remembers what it once meant, because only a few of us remain: the few old enough to remember the time when death was so common and life was so precious you were not allowed to end your own.

The Core would just silently disregard all my Death Wishes, forever.

5

I’m not suicidal any more. I have a hobby now: I am a murderer. And every murder is perfect, because no one remembers that concept either. Sometimes it takes thirty-eight years, but I’m patient. Compared to eternity, thirty-eight years is not so long.

Dank an zis und eFrane für Anregungen und Korrekturlesen!

NetBSD-6: modules and system upgrades

20 January 2011

NetBSD 6 (which is right now at NetBSD-CURRENT version 5.99.44) will be the next release of the NetBSD operating system. Among other changes, the kernel has been heavily modularized for some architectures (including i386, but not amd64 – if you’re on 64 bit Intel/AMD, this doesn’t concern you (yet), on 32 bit Intel/AMD it does). NetBSD 6 (which is right now at NetBSD-CURRENT version 5.99.44) will be the next release of the NetBSD operating system. Among other changes, the kernel has been heavily modularized for some architectures (including i386, but not amd64 – if you’re on 64 bit Intel/AMD, this doesn’t concern you (yet), on 32 bit Intel/AMD it does).

In practice, this especially means that your beloved GENERIC kernel won’t be bootable in and of itself as it can’t read ffs (or any other file system) unless it’s modules are present and loaded. The modules are being installed with the userland via ./build.sh install=/. The NetBSD Guide demands installing the userland only after you’ve booted into the new kernel. We have a problem here.

There are two possible ways out of this dilemma:

  • build a MONOLITHIC kernel, boot it, install the userland and then re-boot into GENERIC
  • install the modules separately from the rest of the userland

The procedure involving the MONOLITHIC (i.e. classic, non-modularized) kernel is described here. I don’t really like it because it involves building two kernels and rebooting twice. On the other hand, it’s probably a good idea to keep a monolithic kernel around anyway, just in case anything goes wrong.

There is no simple make installmodules or ./build.sh installmodules=/ (yet?) but there is a workaround for that (credit goes here): make install USETOOLS=no DESTDIR=/ in sys/modules.

So here’s the full procedure for upgrading either from NetBSD-5 or from NetBSD-CURRENT with an older kernel version to NetBSD-CURRENT. # assuming your sources are in /usr/src and up to date cd /usr/src # build everything ./build.sh distribution kernel=GENERIC # install the modules cd sys/modules; make install USETOOLS=no DESTDIR=/; cd - #save the old kernel cp /netbsd /netbsd.`date +%Y%m%d` #put the new kernel in place cp obj/sys/arch/i386/compile/GENERIC/netbsd /netbsd The next two steps only need to be done once when upgrading from monolithic to modularied kernels: # update the boot loader cp obj/sys/arch/i386/stand/boot/biosboot/boot /boot # and configure it to load the root filesystem module # modules for other filesystems will be loaded later automatically echo "load=ffs" >> /boot.cfg Back to the regular procedure: #reboot shutdown -r now "Kernel upgrade" and after the reboot cd /usr/src ./build.sh install=/ etcupdate -al postinstall fix as usual.

No guarantees of course, and this is work in progress. (Maybe) I’ll update this post when I know more or things changed. Nudge me.

Update:

asau proposes building the sets and installing them: # build everything and the sets ./build.sh distribution kernel=GENERIC sets # install the modules cd /; pax -rzpe -f /usr/obj/releasedir/i386/binary/sets/modules.tgz and after the reboot cd / # unpack everything except etc (will be handled by etcupdate) and modules (already done) for m in base comp games man misc tests text; do pax -rzpe -f /usr/obj/releasdir/i386/binary/sets/${m}.tgz; done etcupdate -al -s /usr/obj/releasedir/i386/binary/sets/etc.tgz Everything else just as above.

Update 2:

Shouldn’t forget about etcupdate and postinstall.