From: Jeff Dike <jdike@addtoit.com>
To: Erik Walthinsen <omega@temple-baptist.com>
Cc: UML User list <user-mode-linux-user@lists.sourceforge.net>,
UML Devel list <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] Re: bug in COW? - Re: [uml-user] uml 2.6.0-test9 crash
Date: Fri, 05 Dec 2003 19:05:34 -0500 [thread overview]
Message-ID: <200312060005.hB605YAv008283@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Thu, 27 Nov 2003 17:28:59 PST." <Pine.LNX.4.53L0.0311271721550.27408@alpha.temple-baptist.com>
omega@temple-baptist.com said:
> I've also run into the fact that something (either UML or the shell)
> seems to cause any symlinks in the path to be factored out as well.
It's UML. I didn't want backing file paths to be invalidated by a component
of a symlink going away when the backing file is still perfectly accessible.
> This means that any images I try to locate in the same place at all
> times, regardless of physical location, still end up being stored as
> their physical location.
I don't parse that at all. Can you try again, maybe with an example or two?
Jeff
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2003-12-06 0:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5.1.0.14.2.20031127102518.02675b90@mail.inboxprotection.com>
2003-11-27 21:06 ` [uml-devel] uml 2.6.0-test9 crash roland
2003-11-27 21:33 ` [uml-devel] Re: [uml-user] " Sven 'Darkman' Michels
2003-11-27 21:54 ` roland
2003-11-27 23:50 ` Henrik Nordstrom
2003-11-28 1:18 ` [uml-devel] bug in COW? - " roland
2003-11-28 1:28 ` [uml-devel] " Erik Walthinsen
2003-11-28 2:11 ` [uml-devel] How to copy COW files to another machine across the network? Shao-Lin Joseph Chung
2003-11-28 8:49 ` Henrik Nordstrom
2003-11-30 21:22 ` roland
2003-11-30 21:37 ` Henrik Nordstrom
2003-11-30 23:31 ` Nigel Cunningham
2003-12-01 9:12 ` roland
2003-12-06 0:04 ` [uml-user] " Jeff Dike
2003-12-06 0:05 ` Jeff Dike
2003-11-28 9:13 ` Geert Uytterhoeven
2003-11-29 9:24 ` Richard Potter
2003-12-06 0:05 ` Jeff Dike [this message]
2003-11-28 8:39 ` [uml-devel] Re: bug in COW? - Re: [uml-user] uml 2.6.0-test9 crash Henrik Nordstrom
2003-11-28 20:42 ` roland
2003-11-28 21:35 ` Henrik Nordstrom
2003-11-30 2:29 ` roland
2003-11-30 7:47 ` Henrik Nordstrom
2003-11-30 8:23 ` Lynn Kerby
2003-11-30 11:36 ` roland
2003-12-06 0:05 ` Jeff Dike
2003-12-06 9:41 ` Henrik Nordstrom
2003-12-06 18:18 ` Jeff Dike
2003-12-06 23:32 ` Henrik Nordstrom
2003-12-08 1:20 ` roland
2003-12-08 19:21 ` Jeff Dike
2003-12-07 10:53 ` [uml-devel] updating 2.6 to merge 2.4 changes(was: Re: bug in COW? - Re: [uml-user] uml 2.6.0-test9 crash) BlaisorBlade
2003-12-08 20:42 ` Jeff Dike
2003-12-08 21:32 ` Henrik Nordstrom
2003-12-08 23:50 ` Jeff Dike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200312060005.hB605YAv008283@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=omega@temple-baptist.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox