DeVO's thoughts

서마이의 생각들을 담는 곳입니다…

Browsing Posts published in June, 2009

I had few cases, where customer won't mention anything but send me a DVD of VMCore.
To debug, I would need the kernel version to find system.map and everything else.
The way to do is;

$ strings vmcore | grep "Linux version"

It is possible to add or remove a SCSI device explicitly, or to re-scan an entire SCSI bus without rebooting a running system. Please see the Online Storage Reconfiguration Guide for a complete overview of this topic on Red Hat Enterprise Linux 5.

For Red Hat Enterprise Linux 5

With fibre attached storage, it is possible to issue a LIP (loop initialization primitive) on the fabric:

echo “1″ > /sys/class/fc_host/host#/issue_lip

Issuing a LIP (above) on Red Hat Enterprise Linux 5 is all that is needed to rescan fibre

attached storage. Once the LIP is issued, the bus scan may take a few seconds to complete.

Although present on previous releases, this feature is only fully supported in Red Hat Enterprise Linux 5.

For Red Hat Enterprise Linux 4 and 5

With other SCSI attached storage, a rescan can be issued:

echo “- – -” > /sys/class/scsi_host/host#/scan

Replace the # with the number of the SCSI bus to be rescanned.

In addition to re-scanning the entire bus, a specific device can be added or deleted for some

versions or Red Hat Enterprise Linux as specified below.

For Red Hat Enterprise Linux 4 or 5

To remove a single existing device explicitly

# echo 1 > /sys/block//device/delete

For Red Hat Enterprise Linux 3, 4, or 5

To add a single device explicitly:

# echo “scsi add-single-device ” > /proc/scsi/scsi

To remove a device explicitly:

# echo “scsi remove-single-device ” > /proc/scsi/scsi

Where are the host, bus, target, and LUN numbers for the device,as reported in /sys (2.6 kernels only) or /proc/scsi/scsi or dmesg.

These numbers are sometimes refered to as “Host”, “Channel”, “Id”, and “Lun” in Linux tool output and documentation.

Have you tried to install an extension on the firefox3 lately?
Especially, if the extension is written for previous version or it was written as a internal tool?

Then for about 90% of time, you will see following error message;

Firefox extension secure updates error

Firefox extension secure updates error

The intention is to ensure that extensions are from the secure source. But for internal solutions, this becomes a pain in the back side.

To resolve this, the best answer would be to contact the person who wrote the extension and ask to rewrite it :)
But, if you don’t have time for it, or just need to get it work then follow these steps;
1. Start Firefox.
2. In the Address Bar type “about:config” and press Enter.
3. Right-Click and select New->Boolean.
4. A box requesting the Preference Name will popup and you should enter “extensions.checkUpdateSecurity” (without the quotes). Press OK to continue.
5. Select “False” from the box and press OK again.

Well, I guess, due to the lack of interests and what so ever, I have been putting this off for last 2 years.

Finally, I have a proper domain name and proper website+hosting.
Thanks to “Seha”, I stole a part of her domain name :)
But I am so happy whit this.

I will try to write everything in ENG, but I guess there will be few bits and pieces poping up in Korean.

“packet receive errors” usually means:
1) data is truncated, error in checksum while copying
2) udp queue is full, so it needs to be dropped
3) unable to receive udp package from encapsulated socket
4) sock_queue_rcv_skb() failed with -ENOMEM
5) it is a short packet
6) no space for header in udp packet when validating packet
7) xfrm6_policy_check() fails

many times it means the checksum is not right.