Nothing to see here - wget stdout
Posted on Saturday, 8th December, 2007 in Life
Actually there’s nothing to see here. It’s just to get it somewhere more obvious then my irc logs …
$ wget -q http://www.kernel.org/pub/linux/kernel/v2.6/incr/patch-2.6.23.8-9.gz -O - | \ gunzip | patch -p1
Life as God it wrote
Posted on Wednesday, 5th December, 2007 in Life
Well, some of you know I’m a bit clumsy. Ok, I went buying some stuff for Saint Nicholas for the ones I love, which came to me about ten minutes before the shops are closing. Navigated my butt into the car, drove the ~6km to the nearest store (which still had open, that was around 20:00).
Got all I wanted, went back to my car (you know, this one) and put the stuff into the trunk. When closing the trunk, I felt some opposition, so I closed it a bit harder. “Closed” I thought and went back into my car. When turning on the ignition the bord computer suddenly complained “trunk open“, so I went back out, trying to open the trunk. *WTF* .. I couldn’t get it open. So I tried again, still nothing.
Okay I thought, since it was kinda closed and I couldn’t get it open with some brute force, I decided to go back home. On the way back home I remembered the parking lot of one of the DIY superstore’s had rather good lighting. So I went by.
On the parking lot, after parking my car, I went over the back seats below the trunk deck into the trunk, removed the trunk deck and saw that I somehow stuffed one of those plastic cooling bags into the lock of the trunk. I went *WTF* and tried brute force again opening the trunk. Still a no-no.
Ripped out the cooling bag (eventually everything of it), went back onto the back seats and tried to open the left rear door, but that didn’t work. Again *WTF*. Toggled the central locking system with the appropriate switch on the front panel. Still *WTF* it didn’t open. So I crawled onto the front seats, where I saw a tiny red light glowing, which is where I figured that the child safety lock for the rear doors was still on .. that at least explained why I couldn’t open the rear door from the inside.
Finally back outside, I went around the car to the trunk, tried to open it. Nothing, again with some force, *TADA* and I got it open. Removed the remaining parts (what was left of the cooling bag), and finally could close the trunk like it’s supposed to close. *pfew*
Device CAL’s ain’t no Device CAL’s ?
Posted on Tuesday, 4th December, 2007 in Life
I stumbled upon a *real* weird problem. Apparently the terminal server licenses called “per Device” ain’t a real per device. From reading on it Microsoft states it like this:
Device-based versus User-based Terminal Server CALs
Two types of Terminal Server Client Access Licenses are available: TS Device CAL or TS User CAL.
- A TS Device CAL permits one device (used by any user) to conduct Windows Sessions on any of your servers.
- A TS User CAL permits one user (using any device) to conduct Windows Sessions on any of your servers.
You may choose to use a combination of TS Device CALs and TS User CALs simultaneously with the server software.
If I take the above and take a closer look at my terminal server license server I’ll see something like this:
Terminal services license manager
As you can see, I *do* have devices with more than a single license (in fact, several of them do have more then four), which from my understanding ain’t what Microsoft had in mind.
After noticing this, I initially thought my terminal servers had the wrong license mode, but as you can see below, they are using “per Device“.
Terminal service license settings
Which means, I am completely clueless at this point, as they *really* should be using just a single license, and not multiple ones.
Update:
Ok, after experimenting a bit with it, it seems that a license seems to be tied to the SSID. Which would explain, why I see different CAL’s for a single device. We reflashed the thin clients in between (and within that process, the SSID is freshly generated), so that’d be the only explanation I’ve got for what I’m seeing.