From: SourceForge.net <no...@so...> - 2007-01-19 18:12:23
|
Feature Requests item #1421120, was opened at 2006-02-01 04:09 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1421120&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: Xuefer (xuefer) Assigned to: Nobody/Anonymous (nobody) Summary: [cofs] vim fsync failed, FSYNC support need Initial Comment: /e is a cofs mount from windows e:\ in vim, write file to /e/ issue error: "/e/a" E667: Fsync failed WARNING: Original file may be lost or damaged don't quit the editor until the file is successfully written! looks like fsync is not implemented. neither many other fs requests ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2007-01-19 19:12 Message: Logged In: YES user_id=579204 Originator: NO I know, cofs has some limits. But my vim works. Opened a file on cofs (is a NTFS) and exit vim with command "wq". No problems, no warnings. hn@colinux:~> vim --version VIM - Vi IMproved 6.2 (2003 Jun 1, compiled Sep 23 2003 23:25:02) How you have mounted cofs? hn@colinux:~> mount | grep cofs0: cofs0:/ on /media/cofs0 type cofs (rw,noexec,nosuid,nodev,uid=500,gid=100,fmask=0664,dmask=0775) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1421120&group_id=98788 |
From: SourceForge.net <no...@so...> - 2007-01-21 01:30:11
|
Feature Requests item #1421120, was opened at 2006-01-31 19:09 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1421120&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: Xuefer (xuefer) Assigned to: Nobody/Anonymous (nobody) Summary: [cofs] vim fsync failed, FSYNC support need Initial Comment: /e is a cofs mount from windows e:\ in vim, write file to /e/ issue error: "/e/a" E667: Fsync failed WARNING: Original file may be lost or damaged don't quit the editor until the file is successfully written! looks like fsync is not implemented. neither many other fs requests ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-01-20 17:30 Message: Logged In: NO cofs3 on /e type cofs (rw,uid=1000,gid=100) what if u do "vim --noplugin"? i'd like to see if i can tune fsync off. i may be faster than patching cofs ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-01-19 10:12 Message: Logged In: YES user_id=579204 Originator: NO I know, cofs has some limits. But my vim works. Opened a file on cofs (is a NTFS) and exit vim with command "wq". No problems, no warnings. hn@colinux:~> vim --version VIM - Vi IMproved 6.2 (2003 Jun 1, compiled Sep 23 2003 23:25:02) How you have mounted cofs? hn@colinux:~> mount | grep cofs0: cofs0:/ on /media/cofs0 type cofs (rw,noexec,nosuid,nodev,uid=500,gid=100,fmask=0664,dmask=0775) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1421120&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-02-26 13:27:05
|
Feature Requests item #1421120, was opened at 2006-02-01 04:09 Message generated for change (Comment added) made by miguillo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1421120&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: Xuefer (xuefer) Assigned to: Nobody/Anonymous (nobody) Summary: [cofs] vim fsync failed, FSYNC support need Initial Comment: /e is a cofs mount from windows e:\ in vim, write file to /e/ issue error: "/e/a" E667: Fsync failed WARNING: Original file may be lost or damaged don't quit the editor until the file is successfully written! looks like fsync is not implemented. neither many other fs requests ---------------------------------------------------------------------- Comment By: Loris-Guillaume Minoia (miguillo) Date: 2008-02-26 14:27 Message: Logged In: YES user_id=244345 Originator: NO I got same problem (in a brand new installed colinux 0.7.2, was already not working with 0.7.1) Solution: a (good) solution is to type the following command in vim: ":set nofsync". It deactivate the vim's fsync feature that force flush to disk (:help fsync), but as you system is stable, it should not be a problem ;-). You can also put it in your .vimrc file. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-01-21 02:30 Message: Logged In: NO cofs3 on /e type cofs (rw,uid=1000,gid=100) what if u do "vim --noplugin"? i'd like to see if i can tune fsync off. i may be faster than patching cofs ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-01-19 19:12 Message: Logged In: YES user_id=579204 Originator: NO I know, cofs has some limits. But my vim works. Opened a file on cofs (is a NTFS) and exit vim with command "wq". No problems, no warnings. hn@colinux:~> vim --version VIM - Vi IMproved 6.2 (2003 Jun 1, compiled Sep 23 2003 23:25:02) How you have mounted cofs? hn@colinux:~> mount | grep cofs0: cofs0:/ on /media/cofs0 type cofs (rw,noexec,nosuid,nodev,uid=500,gid=100,fmask=0664,dmask=0775) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1421120&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-02-26 23:11:41
|
Feature Requests item #1421120, was opened at 2006-02-01 04:09 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1421120&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: Xuefer (xuefer) Assigned to: Nobody/Anonymous (nobody) Summary: [cofs] vim fsync failed, FSYNC support need Initial Comment: /e is a cofs mount from windows e:\ in vim, write file to /e/ issue error: "/e/a" E667: Fsync failed WARNING: Original file may be lost or damaged don't quit the editor until the file is successfully written! looks like fsync is not implemented. neither many other fs requests ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2008-02-27 00:11 Message: Logged In: YES user_id=579204 Originator: NO Fixed in branch devel (SVN revision 896). Please test todays snapshot or autobuild. If that works, we put it into the stable release. ---------------------------------------------------------------------- Comment By: Loris-Guillaume Minoia (miguillo) Date: 2008-02-26 14:27 Message: Logged In: YES user_id=244345 Originator: NO I got same problem (in a brand new installed colinux 0.7.2, was already not working with 0.7.1) Solution: a (good) solution is to type the following command in vim: ":set nofsync". It deactivate the vim's fsync feature that force flush to disk (:help fsync), but as you system is stable, it should not be a problem ;-). You can also put it in your .vimrc file. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-01-21 02:30 Message: Logged In: NO cofs3 on /e type cofs (rw,uid=1000,gid=100) what if u do "vim --noplugin"? i'd like to see if i can tune fsync off. i may be faster than patching cofs ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-01-19 19:12 Message: Logged In: YES user_id=579204 Originator: NO I know, cofs has some limits. But my vim works. Opened a file on cofs (is a NTFS) and exit vim with command "wq". No problems, no warnings. hn@colinux:~> vim --version VIM - Vi IMproved 6.2 (2003 Jun 1, compiled Sep 23 2003 23:25:02) How you have mounted cofs? hn@colinux:~> mount | grep cofs0: cofs0:/ on /media/cofs0 type cofs (rw,noexec,nosuid,nodev,uid=500,gid=100,fmask=0664,dmask=0775) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1421120&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-02-28 21:31:54
|
Feature Requests item #1421120, was opened at 2006-02-01 04:09 Message generated for change (Comment added) made by miguillo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1421120&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: Xuefer (xuefer) Assigned to: Nobody/Anonymous (nobody) Summary: [cofs] vim fsync failed, FSYNC support need Initial Comment: /e is a cofs mount from windows e:\ in vim, write file to /e/ issue error: "/e/a" E667: Fsync failed WARNING: Original file may be lost or damaged don't quit the editor until the file is successfully written! looks like fsync is not implemented. neither many other fs requests ---------------------------------------------------------------------- Comment By: Loris-Guillaume Minoia (miguillo) Date: 2008-02-28 22:31 Message: Logged In: YES user_id=244345 Originator: NO > Please test todays snapshot or autobuild. > If that works, we put it into the stable release. Fsync functions with vim with kernel, modules and daemons from r897 if believing changelog.txt in http://www.henrynestler.com/colinux/autobuild/devel-20080226/. Some comments: It's the first time I try 0.8.x but my eth0/eth1 are now eth4/eth5, even after rebooting. My config is one slirp and ont tap'ed interfaces. ifconfig -a give nothing else except loopback (distribution is an Ubuntu with startup scripts modified for coLinux, perhaps a bug from it, but I can't imagine where). conet0: irq 10, HWAddr 00:ff:57:71:00:00 conet1: irq 10, HWAddr 00:ff:87:60:68:00 I really liked the lines: about alsa (but I didn't managed to make it running) Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC). ALSA device list: #0: coaudio: Cooperative Audio Device using irq 5 and about fuse which I didn't tried yet. Could you put some informations on 0.8.0 new features on the wiki, I didn't found it. Thanks for you work and have a nice week end. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-02-27 00:11 Message: Logged In: YES user_id=579204 Originator: NO Fixed in branch devel (SVN revision 896). Please test todays snapshot or autobuild. If that works, we put it into the stable release. ---------------------------------------------------------------------- Comment By: Loris-Guillaume Minoia (miguillo) Date: 2008-02-26 14:27 Message: Logged In: YES user_id=244345 Originator: NO I got same problem (in a brand new installed colinux 0.7.2, was already not working with 0.7.1) Solution: a (good) solution is to type the following command in vim: ":set nofsync". It deactivate the vim's fsync feature that force flush to disk (:help fsync), but as you system is stable, it should not be a problem ;-). You can also put it in your .vimrc file. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-01-21 02:30 Message: Logged In: NO cofs3 on /e type cofs (rw,uid=1000,gid=100) what if u do "vim --noplugin"? i'd like to see if i can tune fsync off. i may be faster than patching cofs ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-01-19 19:12 Message: Logged In: YES user_id=579204 Originator: NO I know, cofs has some limits. But my vim works. Opened a file on cofs (is a NTFS) and exit vim with command "wq". No problems, no warnings. hn@colinux:~> vim --version VIM - Vi IMproved 6.2 (2003 Jun 1, compiled Sep 23 2003 23:25:02) How you have mounted cofs? hn@colinux:~> mount | grep cofs0: cofs0:/ on /media/cofs0 type cofs (rw,noexec,nosuid,nodev,uid=500,gid=100,fmask=0664,dmask=0775) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1421120&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-02-28 22:05:18
|
Feature Requests item #1421120, was opened at 2006-02-01 04:09 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1421120&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: Xuefer (xuefer) Assigned to: Nobody/Anonymous (nobody) Summary: [cofs] vim fsync failed, FSYNC support need Initial Comment: /e is a cofs mount from windows e:\ in vim, write file to /e/ issue error: "/e/a" E667: Fsync failed WARNING: Original file may be lost or damaged don't quit the editor until the file is successfully written! looks like fsync is not implemented. neither many other fs requests ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2008-02-28 23:05 Message: Logged In: YES user_id=579204 Originator: NO The incrasing eth0, eth1, ... is known and solved from this bug report : https://sourceforge.net/tracker/index.php?func=detail&aid=1861876&group_id=98788&atid=622063 You should read (better ;-) ) "NOTES ON UPGRADING" from http://www.colinux.org/snapshots/devel-RUNNING Sound and Video are not usable. Only the pci id was shown. Steve is working on. Such things is not for wiki at this time. All usable news can read from http://www.colinux.org/snapshots/devel-NEWS or http://colinux.svn.sourceforge.net/svnroot/colinux/branches/devel/NEWS ---------------------------------------------------------------------- Comment By: Loris-Guillaume Minoia (miguillo) Date: 2008-02-28 22:31 Message: Logged In: YES user_id=244345 Originator: NO > Please test todays snapshot or autobuild. > If that works, we put it into the stable release. Fsync functions with vim with kernel, modules and daemons from r897 if believing changelog.txt in http://www.henrynestler.com/colinux/autobuild/devel-20080226/. Some comments: It's the first time I try 0.8.x but my eth0/eth1 are now eth4/eth5, even after rebooting. My config is one slirp and ont tap'ed interfaces. ifconfig -a give nothing else except loopback (distribution is an Ubuntu with startup scripts modified for coLinux, perhaps a bug from it, but I can't imagine where). conet0: irq 10, HWAddr 00:ff:57:71:00:00 conet1: irq 10, HWAddr 00:ff:87:60:68:00 I really liked the lines: about alsa (but I didn't managed to make it running) Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC). ALSA device list: #0: coaudio: Cooperative Audio Device using irq 5 and about fuse which I didn't tried yet. Could you put some informations on 0.8.0 new features on the wiki, I didn't found it. Thanks for you work and have a nice week end. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-02-27 00:11 Message: Logged In: YES user_id=579204 Originator: NO Fixed in branch devel (SVN revision 896). Please test todays snapshot or autobuild. If that works, we put it into the stable release. ---------------------------------------------------------------------- Comment By: Loris-Guillaume Minoia (miguillo) Date: 2008-02-26 14:27 Message: Logged In: YES user_id=244345 Originator: NO I got same problem (in a brand new installed colinux 0.7.2, was already not working with 0.7.1) Solution: a (good) solution is to type the following command in vim: ":set nofsync". It deactivate the vim's fsync feature that force flush to disk (:help fsync), but as you system is stable, it should not be a problem ;-). You can also put it in your .vimrc file. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-01-21 02:30 Message: Logged In: NO cofs3 on /e type cofs (rw,uid=1000,gid=100) what if u do "vim --noplugin"? i'd like to see if i can tune fsync off. i may be faster than patching cofs ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-01-19 19:12 Message: Logged In: YES user_id=579204 Originator: NO I know, cofs has some limits. But my vim works. Opened a file on cofs (is a NTFS) and exit vim with command "wq". No problems, no warnings. hn@colinux:~> vim --version VIM - Vi IMproved 6.2 (2003 Jun 1, compiled Sep 23 2003 23:25:02) How you have mounted cofs? hn@colinux:~> mount | grep cofs0: cofs0:/ on /media/cofs0 type cofs (rw,noexec,nosuid,nodev,uid=500,gid=100,fmask=0664,dmask=0775) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1421120&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-02-28 22:09:12
|
Feature Requests item #1421120, was opened at 2006-02-01 04:09 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1421120&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: Xuefer (xuefer) Assigned to: Nobody/Anonymous (nobody) Summary: [cofs] vim fsync failed, FSYNC support need Initial Comment: /e is a cofs mount from windows e:\ in vim, write file to /e/ issue error: "/e/a" E667: Fsync failed WARNING: Original file may be lost or damaged don't quit the editor until the file is successfully written! looks like fsync is not implemented. neither many other fs requests ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2008-02-28 23:09 Message: Logged In: YES user_id=579204 Originator: NO The "fuse..." here was the "cofs" host file system. The code based on fuse, but is not the fuse you perhaps thinks to know. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-02-28 23:05 Message: Logged In: YES user_id=579204 Originator: NO The incrasing eth0, eth1, ... is known and solved from this bug report : https://sourceforge.net/tracker/index.php?func=detail&aid=1861876&group_id=98788&atid=622063 You should read (better ;-) ) "NOTES ON UPGRADING" from http://www.colinux.org/snapshots/devel-RUNNING Sound and Video are not usable. Only the pci id was shown. Steve is working on. Such things is not for wiki at this time. All usable news can read from http://www.colinux.org/snapshots/devel-NEWS or http://colinux.svn.sourceforge.net/svnroot/colinux/branches/devel/NEWS ---------------------------------------------------------------------- Comment By: Loris-Guillaume Minoia (miguillo) Date: 2008-02-28 22:31 Message: Logged In: YES user_id=244345 Originator: NO > Please test todays snapshot or autobuild. > If that works, we put it into the stable release. Fsync functions with vim with kernel, modules and daemons from r897 if believing changelog.txt in http://www.henrynestler.com/colinux/autobuild/devel-20080226/. Some comments: It's the first time I try 0.8.x but my eth0/eth1 are now eth4/eth5, even after rebooting. My config is one slirp and ont tap'ed interfaces. ifconfig -a give nothing else except loopback (distribution is an Ubuntu with startup scripts modified for coLinux, perhaps a bug from it, but I can't imagine where). conet0: irq 10, HWAddr 00:ff:57:71:00:00 conet1: irq 10, HWAddr 00:ff:87:60:68:00 I really liked the lines: about alsa (but I didn't managed to make it running) Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC). ALSA device list: #0: coaudio: Cooperative Audio Device using irq 5 and about fuse which I didn't tried yet. Could you put some informations on 0.8.0 new features on the wiki, I didn't found it. Thanks for you work and have a nice week end. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-02-27 00:11 Message: Logged In: YES user_id=579204 Originator: NO Fixed in branch devel (SVN revision 896). Please test todays snapshot or autobuild. If that works, we put it into the stable release. ---------------------------------------------------------------------- Comment By: Loris-Guillaume Minoia (miguillo) Date: 2008-02-26 14:27 Message: Logged In: YES user_id=244345 Originator: NO I got same problem (in a brand new installed colinux 0.7.2, was already not working with 0.7.1) Solution: a (good) solution is to type the following command in vim: ":set nofsync". It deactivate the vim's fsync feature that force flush to disk (:help fsync), but as you system is stable, it should not be a problem ;-). You can also put it in your .vimrc file. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-01-21 02:30 Message: Logged In: NO cofs3 on /e type cofs (rw,uid=1000,gid=100) what if u do "vim --noplugin"? i'd like to see if i can tune fsync off. i may be faster than patching cofs ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-01-19 19:12 Message: Logged In: YES user_id=579204 Originator: NO I know, cofs has some limits. But my vim works. Opened a file on cofs (is a NTFS) and exit vim with command "wq". No problems, no warnings. hn@colinux:~> vim --version VIM - Vi IMproved 6.2 (2003 Jun 1, compiled Sep 23 2003 23:25:02) How you have mounted cofs? hn@colinux:~> mount | grep cofs0: cofs0:/ on /media/cofs0 type cofs (rw,noexec,nosuid,nodev,uid=500,gid=100,fmask=0664,dmask=0775) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1421120&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-03-01 18:37:30
|
Feature Requests item #1421120, was opened at 2006-02-01 04:09 Message generated for change (Settings changed) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1421120&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Priority: 5 Private: No Submitted By: Xuefer (xuefer) Assigned to: Nobody/Anonymous (nobody) Summary: [cofs] vim fsync failed, FSYNC support need Initial Comment: /e is a cofs mount from windows e:\ in vim, write file to /e/ issue error: "/e/a" E667: Fsync failed WARNING: Original file may be lost or damaged don't quit the editor until the file is successfully written! looks like fsync is not implemented. neither many other fs requests ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2008-03-01 19:37 Message: Logged In: YES user_id=579204 Originator: NO cofs sync fixed in branch stable now. Available from http://www.colinux.org/snapshots/ ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-02-28 23:09 Message: Logged In: YES user_id=579204 Originator: NO The "fuse..." here was the "cofs" host file system. The code based on fuse, but is not the fuse you perhaps thinks to know. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-02-28 23:05 Message: Logged In: YES user_id=579204 Originator: NO The incrasing eth0, eth1, ... is known and solved from this bug report : https://sourceforge.net/tracker/index.php?func=detail&aid=1861876&group_id=98788&atid=622063 You should read (better ;-) ) "NOTES ON UPGRADING" from http://www.colinux.org/snapshots/devel-RUNNING Sound and Video are not usable. Only the pci id was shown. Steve is working on. Such things is not for wiki at this time. All usable news can read from http://www.colinux.org/snapshots/devel-NEWS or http://colinux.svn.sourceforge.net/svnroot/colinux/branches/devel/NEWS ---------------------------------------------------------------------- Comment By: Loris-Guillaume Minoia (miguillo) Date: 2008-02-28 22:31 Message: Logged In: YES user_id=244345 Originator: NO > Please test todays snapshot or autobuild. > If that works, we put it into the stable release. Fsync functions with vim with kernel, modules and daemons from r897 if believing changelog.txt in http://www.henrynestler.com/colinux/autobuild/devel-20080226/. Some comments: It's the first time I try 0.8.x but my eth0/eth1 are now eth4/eth5, even after rebooting. My config is one slirp and ont tap'ed interfaces. ifconfig -a give nothing else except loopback (distribution is an Ubuntu with startup scripts modified for coLinux, perhaps a bug from it, but I can't imagine where). conet0: irq 10, HWAddr 00:ff:57:71:00:00 conet1: irq 10, HWAddr 00:ff:87:60:68:00 I really liked the lines: about alsa (but I didn't managed to make it running) Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC). ALSA device list: #0: coaudio: Cooperative Audio Device using irq 5 and about fuse which I didn't tried yet. Could you put some informations on 0.8.0 new features on the wiki, I didn't found it. Thanks for you work and have a nice week end. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-02-27 00:11 Message: Logged In: YES user_id=579204 Originator: NO Fixed in branch devel (SVN revision 896). Please test todays snapshot or autobuild. If that works, we put it into the stable release. ---------------------------------------------------------------------- Comment By: Loris-Guillaume Minoia (miguillo) Date: 2008-02-26 14:27 Message: Logged In: YES user_id=244345 Originator: NO I got same problem (in a brand new installed colinux 0.7.2, was already not working with 0.7.1) Solution: a (good) solution is to type the following command in vim: ":set nofsync". It deactivate the vim's fsync feature that force flush to disk (:help fsync), but as you system is stable, it should not be a problem ;-). You can also put it in your .vimrc file. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-01-21 02:30 Message: Logged In: NO cofs3 on /e type cofs (rw,uid=1000,gid=100) what if u do "vim --noplugin"? i'd like to see if i can tune fsync off. i may be faster than patching cofs ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-01-19 19:12 Message: Logged In: YES user_id=579204 Originator: NO I know, cofs has some limits. But my vim works. Opened a file on cofs (is a NTFS) and exit vim with command "wq". No problems, no warnings. hn@colinux:~> vim --version VIM - Vi IMproved 6.2 (2003 Jun 1, compiled Sep 23 2003 23:25:02) How you have mounted cofs? hn@colinux:~> mount | grep cofs0: cofs0:/ on /media/cofs0 type cofs (rw,noexec,nosuid,nodev,uid=500,gid=100,fmask=0664,dmask=0775) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1421120&group_id=98788 |