-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Blaisorblade" == Blaisorblade <blaisorblade@...> writes:
>> I'm running 2.4.26-um3. I happen to be running hostfs with NFS
>> underneath. I get core dumps from my application, and I want to
>> gdb them outside of the UML.
>> I had to switch from core dump to NFS (which seems to fail now)
>> to putting them in /tmp (which is ramdisk), and then move them to
>> /var/tmp, which is hostfs.
Blaisorblade> Hmm - were you putting the core dumps inside a hostfs
Blaisorblade> mount, right? This has been reported to fail badly
Blaisorblade> with 2.4.26-3um... the hostfs contained in 2.4.24-1um
Blaisorblade> and 2.4.27-1bs (this tree is from me, on my homepage)
Blaisorblade> is stable, while the one in 2.4.24-2um and subsequent
Blaisorblade> releases isn't.
I'll try it on my next compile.
>> Is there some way to defeat the caching that is occuring? or
>> even to just flush it? (other than umount)
Blaisorblade> Hmmm, I don't know this... probably giving "sync"
Blaisorblade> inside UML should work. I remember that Jeff said
Blaisorblade> that he made hostfs asynchronous in those releases on
Blaisorblade> purpose (for performance, IIRC), and this is not bad.
I actually wonder if there is really any advantage.
I'd like to be convinced.
It seems that for executables, mapping hostfs files straight into the
guest address space wouldn't care. I'd have thought that for stdio
things, that any buffering done by guest kernel would be really just
wasted. glibc has already buffered pretty much everything...
However, I'd like to be able to turn it off.
] ON HUMILITY: to err is human. To moo, bovine. | firewalls [
] Michael Richardson, Xelerance Corporation, Ottawa, ON |net architect[
] mcr@... http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys
-----END PGP SIGNATURE-----