Comments for Svoccblog

Comment on CPU feature flags and their meanings by CPU flags | Freedom Interface

CPU flags | Freedom Interface — Wed, 02 Jun 2010 19:58:31 +0000

[...] As mais comuns que vi referências foram: PAE (Physical Address Extensions) que permite endereçamento de memória acima de 2GB; HT (Hyper Threading) que permite um núcleo de processador possuir duas filhas de processamento, simulando assim processamento paralelo; LM (Long Mode) que indica presença de instruções x86_64; entre outros que podem ser encontrados neste endereço. [...]

Comment on CPU feature flags and their meanings by links for 2010-01-25 | 小李贼

links for 2010-01-25 | 小李贼 — Mon, 25 Jan 2010 13:34:52 +0000

[...] CPU feature flags and their meanings » Svoccblog (tags: kvm) [...]

Comment on ATmega16 controller and DOG-M LCD module – can’t get it to work right by sven

sven — Fri, 24 Jul 2009 07:05:39 +0000

Well, I can’t help you there as I never worked with graphical displays yet, but perhaps someone else can. If you do get it to work, I would be very thankful if you could share the code.

Comment on ATmega16 controller and DOG-M LCD module – can’t get it to work right by Srinu

Srinu — Thu, 23 Jul 2009 17:21:34 +0000

Hello

Iam working on atmega16 controller. the project is to get graphical display on avr. for this iam using lgm12864b lcd display and AVR studio for compiling. can anyone help me in source code for that??

thank you

regards
srinu

Comment on RHEL/CentOS bi-arch problems by sven

sven — Wed, 08 Jul 2009 07:35:01 +0000

Unfortunately, I agree with you. However, in medium to big companies, you really need the guarantee for commercial support. Be it for software like Oracle which is only officially supported on certain operating systems or for hardware like fibre channel adapters which only has official drivers for certain versions of certain operating systems….
So all in all, there isn’t much choice there…

Comment on RHEL/CentOS bi-arch problems by Anonymous

Anonymous — Tue, 07 Jul 2009 16:14:23 +0000

RHEL barely supports *one* architecture at a time.

Comment on RHEL/CentOS bi-arch problems by sven

sven — Tue, 07 Jul 2009 13:32:05 +0000

No, I didn’t really have this issue for the first time, but I also had the problem of two packages sharing a file with different content (though it was a whitespace-only change in a text based configuration – and no, whitespace was not relevant to syntax) not being installed side-by-side because of that differing content.
Perhaps overwriting is only done when installing the exact same package (name and version), with just the architecture differing, but if package names differ, the contents are checked for differences…
Stupid in many ways IMHO. Though I can’t offer a less stupid, working solution. Except such packages to declare some conflict with other architecture versions of themself. Not sure how conflicts get resolved in the RPM world though, I just know dpkg/deb is rock-solid in this regard.

Comment on RHEL/CentOS bi-arch problems by Roguelazer

Roguelazer — Tue, 07 Jul 2009 11:46:06 +0000

I’m surprised that this is the first time you’ve run into this. Many libraries (e.g., tclx) come in both 32- and 64-bit versions, try to install both in /usr/lib/, and use the same exact filename. rpm seems to have no problems with installing both and just silently overwriting whichever one is installed first. >.<

Comment on Another link collection 2009-06-22 by Jon

Jon — Mon, 22 Jun 2009 09:03:21 +0000

And 100% of those links were syndicated on planet debian! I worry we might become a monoculture

Comment on Link collection 2009/03 by sven

sven — Tue, 31 Mar 2009 19:53:44 +0000

Yep, indentation was eaten. Anyway, your approach works fine as long as you have control over how the commandline arguments are processed. But at times you just want to leave the pre-existing commandline parsing alone or even use some sort of library function for this. In that case, your approach won’t work. But it is a really nice idea for own scripts that are fully under ones control. Thanks for sharing the idea.

Comment on Link collection 2009/03 by Patrick

Patrick — Tue, 31 Mar 2009 19:33:50 +0000

Hi,
the link to the lost+found article is broken. It also points to Seans blog entry.
Regards,
Patrick

Comment on Link collection 2009/03 by Anonymous

Anonymous — Tue, 31 Mar 2009 16:16:49 +0000

OK, the indentation got eaten, but otherwise that came through fine. Anyway, the above approach works with any whitespace or strange symbols you want to put into the parameters, without having to escape them.

Comment on Link collection 2009/03 by Anonymous

Anonymous — Tue, 31 Mar 2009 16:13:48 +0000

Regarding the approach to saving and restoring parameters, a much easier solution (which hopefully won’t get mangled in this comment):

echo Original $# arguments: “$@”

echo Processing arguments one at a time…
n=$#
set “$@” “$@”
while [ "$#" -gt "$n" ]; do
echo Processing argument “$1″
shift
done

echo Back to the original $# arguments: “$@”

Comment on Link collection 2009/03 by Cuetzpallin

Cuetzpallin — Tue, 31 Mar 2009 15:05:39 +0000

Nice and useful links, thanks for your share

Comment on Apache SSL oddity by sven

sven — Sat, 28 Mar 2009 12:24:39 +0000

Was I really this misunderstandable? I was neither talking about name-based virtual hosts (mine are purely IP/port based) nor about SSL server name indication!
I will not approve any more comments which talk about those unless they show how they are related to my problem (IP/port based virtual hosts with the same ServerName).