From: <alnsn@yandex.ru>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Hostfs doesn't work - digging the kernel
Date: Sun, 23 May 2004 14:26:02 +0400 [thread overview]
Message-ID: <20040523102602.GA4034@x1000.localdomain> (raw)
In-Reply-To: <20040523093605.GA2223@x1000.localdomain>
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
Alexander Nasonov wrote:
> Even with -o option I can't mount. Function hostfs_init_file composes a
> path beginning with jail_dir (/ in my case), then go mount and file.
> const char *path[] = { jail_dir, mount, file, NULL };
> In my case path is either // or //tmp. The open64 function can't open both.
> If I do these transformations:
> "//" -> ""
> "//tmp" -> "/tmp"
> they are mounted but I can't read files.
> I suggest always transform path like this. What do you think?
Opps, it doesn't work. I wonder how it worked before. I need more digging :)
--
Alexander Nasonov
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-23 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-23 9:36 [uml-devel] Hostfs doesn't work - digging the kernel alnsn
2004-05-23 10:26 ` alnsn [this message]
2004-05-23 19:51 ` Henrik Nordstrom
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=20040523102602.GA4034@x1000.localdomain \
--to=alnsn@yandex.ru \
--cc=user-mode-linux-devel@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