Is there any programs i can use to install .exe files to Fedora 13? Investigator, Embassy Investigations. -- users mailing list users(a)lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Is there any programs i can use to install .exe files to Fedora 13? Investigator, Embassy Investigations.

On Saturday, July 31, 2010 06:13:21 pm D. VITELLIUS REGULUS did opine: > Is there any programs i can use to install .exe files to Fedora 13? > > Investigator, Embassy Investigations. I get the impression this one came from a hacker, looking for some way to exploit linux. If you come back again, please come back with a believable name, and a believable return address. This msg sets off all sorts of red lights and alarms.

Hi listers i got file system errors on a new machine (hw errors should therefore not be an issue, also smartctl does not indicate any errors), which holds two disks on SATA controllers. Both disks contain a fully fleged Fedora 13, so that i can boot from either of them. i usually boot from the first disk, and i take care not to cross-mount the second disk or to unmount cross-mounts before hibernating. [root at myws ~]# uname -a Linux myws.lan 2.6.33.5-124.fc13.x86_64 #1 SMP Fri Jun 11 09:38:12 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux [root at myws ~]# The complete log of a boot cycle follows in the next message. The file systems error manifests itself as follows in /var/log/messages: Jul 5 07:04:59 myws kernel: EXT4-fs error (device dm-0): ext4_free_inode: bit already cleared for inode 136802 Jul 5 07:04:59 myws kernel: EXT4-fs error (device dm-0): ext4_free_inode: bit already cleared for inode 136803 When this error occurs i can no longer do such simple things as touch /tmp/abcd.txt which at this time gives me "No such file or directory" to shut down the system, i usually use the hibernate function (i.e. save to the swap space), i mostly do not reboot the system. But then, after some resume/thaw cycles from the swap space, the above error happens, and i have to reboot. when rebooting, the system goes through one ore two fsck cycles whith "File System has been modified, reboot needed" and reboots itself. when the system comes up after that, the above error does not happen anymore, but i am not sure, whether the system is in the same state as before, i.e. i am not sure, whether i have lost data.

As you can see from the boot-log, the system has 4 CPUs, which made me think that this is a "write barriers" issue, but from kernel 2.6.31 on, write barriers in multi processor systems should pose no problems any

questions: 1. is this a heavy issue, i.e. does this "error" corrupt my system with time? 2. what can i do to avoid this ext4 error, it it were an error? going back to ext3 is considered no solution. thanks for any hints.