Comments for Dirk-Jan's blog

Comment on Windows wireless driver for Amilo Li 2727 by david_mkd

david_mkd — Sun, 05 Feb 2012 14:19:47 +0000

I hope this works, I’m getting tired of fujitsu’s crappy drivers.

Comment on A green home server by Dirk-Jan's blog » Server upgrade

Dirk-Jan's blog » Server upgrade — Sun, 15 Jan 2012 17:54:18 +0000

[...] my home server. The main reasons, lack of 64-bit support and virtualization technology (VT-x) in my existing setup. The performance gain was also a nice side effect. I have come up with the following new [...]

Comment on Windows wireless driver for Amilo Li 2727 by Jonuz SERBIA

Jonuz SERBIA — Sun, 15 Jan 2012 16:20:33 +0000

MAN, REALLY THANK YOU. SPENT 2 DAYS FINDING WLAN FOR WIN7 AND FINALLY THIS !!!
thankS thanks thanks thanks thanks thanks thanks thanks thanks thanks thanks thanks thanks thanks thanks thanks thanks thanks thanks thanks thanks thanks thanks thanks

Comment on Install SCOM agent on Red Hat Linux by Chris

Chris — Tue, 20 Dec 2011 16:51:20 +0000

Correction:
I did the following:
# rm /dev/random
# mknod -m 666 /dev/random c 1 8
# chown root:root /dev/random

Comment on Install SCOM agent on Red Hat Linux by Chris

Chris — Tue, 20 Dec 2011 16:46:21 +0000

@Greg
I tried the workaround and then read your reply on it. I want to make sure I have a correct /dev/random file on the concerning system (centos 5). I think I have set things the way they were but I want to make sure.

I remove the /dev/random file and created it back again by:

# rm /dev/random
# mknod -m 666 /dev/random c 1 9
# chown root:root /dev/random

Is that correct?

Thanx in advance.

Regards,
Chris

Comment on License to rdesktop by amolik

amolik — Fri, 09 Dec 2011 12:48:23 +0000

THANKS ..It`s HELPS ME in my computer example like this:
/home/WORKGROUP/MICHAEL/.rdesktop# rm licence.MICH001

Comment on Home server HDD upgrade by Greg

Greg — Fri, 02 Dec 2011 21:30:36 +0000

You can hot-swap the disks, too For /dev/sdb, it’s probably:

echo “remove-single-device 0 1 0 0″ > /proc/scsi/scsi

cat /proc/scsi/scsi to make sure it’s removed. You can then yank the disk out (provided you have sleds).

insert your new disk

then run “echo – - – > /sys/class/scsi_host/host*/scan”

No shutdowns required.

Comment on Install SCOM agent on Red Hat Linux by Greg

Greg — Fri, 02 Dec 2011 19:44:28 +0000

To answer my own question….the certificates are kept in /etc/opt/microsoft/scx/ssl.

Comment on Install SCOM agent on Red Hat Linux by Greg

Greg — Fri, 02 Dec 2011 19:43:24 +0000

Sorry — this article is misleading and incomplete. On Linux systems, /dev/random and /dev/urandom are world-readable devices with world-writable permissions and different minor numbers (8 vs. 9). /dev/random is blocking — meaning that the entropy you need for /dev/random to output data is seeded by system activity (disk reads, network scans, etc.). Few systems are busy enough to keep /dev/random’s entropy “buffer” full. /dev/urandom is non-blocking, meaning less entropy and more “fudged” random data. It’s less secure but few people care.

Furthermore the RPM install just generates a warning that it’s falling back to /dev/urandom because it couldn’t get enough data from /dev/random. All you’re doing is “tricking” the RPM installer into using /dev/urandom in the first place by creating — incorrectly — a /dev/random special file that actually uses the urandom driver. To make matters worse, you are recreating the /dev/random special file with 0644 permissions, not 0666. You have just broken your system.

The incomplete part is:

“It is possile to install the agent, copy the unsigned client-side generated certificate to the SCOM server, sign the certificate on the SCOM server and copy the signed certificate back to the client.”

It would be nice to know what you mean by this statement. Where is this certificate kept?

Comment on 877W wireless config by Charles

Charles — Wed, 02 Nov 2011 01:47:12 +0000

Hi,

When I get to the line below it says that it will overlap with my Vlan1
Our network is 192.168.0.0 255.255.255.0 and the router address that i am working on is 192.168.0.249.

interface Dot11Radio0.1
description WLAN vlan2
encapsulation dot1Q 2
=================> ip address 192.168.2.1 255.255.255.0 <==========

Charles