Thursday, 22 December 2011

QEMU/KVM All projects abort with internal compiler error

QEMU/KVM All projects abort with internal compiler error

Hello,

I have setup a system consisting of the host on AMD Athlon64. On it several VMs are running. Either SuSE 11.4 or 12.1.

When I try to compile any source project (with gcc 4.5.1 or 4.6.2), lately bacula, the 'make' is sooner or later aborted by "internal compiler error". Sometimes I am lucky with tinkering with compiling options like setting -O2 to -O0. Currently I am running the gcc testsuite. It looks like all test fail.
All projects I tried so far ran without error with the same options on the host.

So I think it is connected with the fact that the compilation is done within a VM. But I don't know how to get an angle on this. Maybe the compiler does not know with processorshould be compiled for?

I do not know what information to post to help you analyze the problem, so please ask.

Thank you,

Tobi

Monitoring iptables processes

Monitoring iptables processes

Hello there.

I'm looking for a way to monitoring iptables processes.
Since iptables acts directly into the kernel (correct me if I'm wrong), I tried to look into /proc to search for something interesting but found nothing.

Sometimes, some rules just don't work and I cannot know why, I need some monitoring tool, something like a grep, to see exactly what is iptables doing with some packet.

Using grep and sed

Using grep and sed

Hi everyone. I'm having trouble using these commands to their full extent. Here is my problem:

I'm dumping a log to the terminal and only want a specific set of lines that start with
Code:

V/ CONTENT ( [some number]):
But I want these lines without that junk in front of it. To display only the parts I want, I'm doing the log command piped with grep and sed

Code:

./adb logcat | grep CONTENT | sed -e 's/CONTENT ( [some number]):/ /g'
This leaves me with V/(stuff I want). I'm just not sure how to sed the V/ part out of it because in the sed command '/' symbols are used to separate fields. Anybody have an idea? :D

using fopen and fread with /dev/sda

using fopen and fread with /dev/sda

Last night I accidentally deleted quite a few files I had been working on for the past month or so. So, after freaking out for a little while and after trying unsuccessfully to use grep on the unmounted partition (it ran out of memory...haha) I decided I may as well learn something from this and so I am using another computer to write a program (in c) to read directly from my hard drive (/dev/sda) and search for a specific string while using only a reasonable amount of memory (grep was using all 8GB). I now have my computer I deleted the files on running off of a flash drive so that it doesn't harm the data on the hard drive, but I have a few questions about using fopen and fread to read data from /dev/sda (sorry if I have too many questions...I just want to be certain this will work):

Would fopen treat /dev/sda just like any other file?

When using fread on a /dev/sd* file will it return less than the requested bytes when it gets to the end of the hard drive?

Would fread read directly from /dev/sda or would it try to copy it into memory first? Do I have to worry about memory problems if I try to read another 100MB after already reading 8GB (the amount of memory I have on my computer) even though I have free'd the memory that I had it read into?

My program as I have it functions more or less as follows:
Code:

FILE* inputStream = fopen("/dev/sda", "rb");
//...stuff to check to make sure it actually opened it

//...

//...the following is inside of a loop...
char* memoryChunk = malloc(100000000); //allocate 100mb for the chunk to be read
unsigned long int actualReadBytes = fread(memoryChunk, 1, 100000000, inputStream);
//...memoryChunk is processed...
free(memoryChunk);
if (actualReadBytes < 100000000)
{
      //...exit the loop since that means the last chunk read was the end of /dev/sda
}

//...after the loop and everything
fclose(inputStream);

Booting Linux Mint 12

Booting Linux Mint 12

When booting LM 12 a dark rectangular box is displayed at the bottom of the screen with "HP Media Drive" displayed and a choice of "open with files" and "eject". If I select eject the system hangs. This display has just started happening and I have no idea why. I also want to stop the box itself from being displayed. Suggestions?

Desktop Fork for GNOME; Yet Another One Bites the Dust...!

Desktop Fork for GNOME; Yet Another One Bites the Dust...!

Been reading some interesting news and stumbled across several sites referencing to the founder of Linux Mint forking from the GNOME Desktop. I don't know if this is just rumour or if there is an actual backing behind the new forked desktop.

Just look up "Cinnamon Desktop"
or Links here:
Cinnamon: GNOME Shell Fork With A GNOME2-Like Layout ~ Web Upd8: Ubuntu / Linux blog

Gnome Shell Looks Like Gnome 2 – Cinnamon Desktop | Smashing Web

Sounds like the Cinnamon Desktop will be a further improvement on GNOME MGSE. A new hybrid desktop of GNOME 3 and 2. I was always curious and wondered what Mint's Gnome extensions would do, sorta had that gut feeling it might be the start of a fork.

Yet Another one, it appears as though GNOME's new route is quickly losing followers and supporters.

On my count it is up to 3 forks since GNOME 3's release. (The Magic number being 3)
You've got Unity Desktop, MATE, and Cinnamon (if this holds to be true)
That seriously suggests something concerning...! 3 forks from what used to be the Top Desktop Environment in just a few months. That should be ringing alarm bells for GNOME developers.

External USB Drive Will Not Mount

External USB Drive Will Not Mount

Recently my external Western Digital USB drive will not mount. The unmounted disk icon shows up on the desktop when I plug in the USB drive and then when I try to mount via the GUI (right click mouse and choose "mount") it says operation failed. I am also unable to mount via command line - I get a message that says the partition is busy or already mounted. This is a production web server (SLES10-SP3) that has been running for six years with the same Western Digital USB external drive ( used to back up my web root). I am not sure if this is a sign of the external drive on its last leg or not.

I was thinking of deleting the lines referencing the Western Digital external drive in /etc/fstab and then rebooting. Is that okay to do? Thanks.

Here is my /etc/fstab


Code:

/dev/disk/by-id/scsi-SATA_WDC_WD1600YS-18_WD-WCAP01651022-part2 /                    reiserfs  acl,user_xattr        1 1
/dev/disk/by-id/scsi-SATA_WDC_WD1600YS-18_WD-WCAP01651022-part1 swap                swap      defaults              0 0
proc                /proc                proc      defaults              0 0
sysfs                /sys                sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts              /dev/pts            devpts    mode=0620,gid=5      0 0