From: Rob Landley <rob@landley.net>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Gerd Knorr <kraxel@bytesex.org>
Subject: Re: [uml-devel] SIGSEGV and SA_NODEFER
Date: Tue, 25 Jan 2005 14:30:26 -0500 [thread overview]
Message-ID: <200501251430.26927.rob@landley.net> (raw)
In-Reply-To: <200501252034.25668.blaisorblade@yahoo.it>
On Tuesday 25 January 2005 02:34 pm, Blaisorblade wrote:
> > Once I get /dev on ramfs managed by udev? Not really, no. I need the
> > permissions to be right, but just about everything else should belong to
> > root. (Yeah, there are a couple fun tricks where files change their
> > ownership to some variant of "nobody" to do chroot jails and stuff, but
> > they do that at runtime...)
>
> I don't expect chown to work at all - i.e. it's not "it forgets it at
> reboot", it's "it forgets it immediately"... If you see it working, maybe
> you are seeing the more precise behaviour "it forgets it As Soon as the
> file is closed".
Actually, I don't think I've tried to do a chown on UML at all. As I said,
the files I care about the ownership of being right (the /dev directory) are
all in a ramfs. Everything else should belong to root, I just care that the
permissions are right. (A user can set the suid bit on their own files,
right?)
And what I meant to say earlier is that some programs chuser (like bind and
httpd and such), which they do at runtime
Still, good point. I'm doing a rebuild without UML and I'll run "find . -not
-uid 0" on the result to see what comes up...
> > I've probably missed one or two instances, but I expect I can work around
> > 'em...
> >
> > > I'm not at all happy with this, but I don't want someone using hostfs
> > > over its possibilities. NFS is much better, anyway.
> >
> > NFS gives me hives
>
> ?? What's hives?
An NFS server can't be exposed to the internet securely. (To add insult to
injury, for _years_ Red Hat exposed portmap and such to the outside world and
there was absolutely no way to tell it not to install/run that crud, and you
had to go in by hand and rip them out of each new install if you wanted it on
the net.)
NFS was designed to be a stateless protocol, yet the point of a filesystem is
to maintain state. It DIDN'T just do a TCP/IP connection to a client,
instead it did weird UDP stuff so the server doesn't have to know which files
the client has open and 8 gazillion other strange corner cases that I stopped
trying to pay attention to more than 5 years ago.
I'm told the most recent version of NFS has been redesigned to work like
Samba: a client that mounts one of these things opens a TCP/IP session, and
if it gets closed the client re-opens it. I should look into that, but the
last time I did support for the new way of doing it it wasn't in the kernel
yet.
> > > And somebody says it's also
> > > faster (and since hostfs does limited caching, it makes sense - hostfs
> > > must avoid having any inode cache, since it closes the host fd only
> > > when the inode is evicted from the cache; I don't think it's possible
> > > to cache data without an inode to link to, so it's clear it's slow).
> >
> > Since the host is cacheing the data for us, not having a redundant cache
> > sounds like a good idea to me. Admittedly, it's more syscalls, but less
> > memory consumption...
>
> The problem is that its slower than NFS!
Okay, remember how my build process is designed to be packaged up, exported to
some random Linux system out there, and run as a normal user without root
access? HostFS is exactly what I need. Even assuming an NFS server is
installed on the target system, a normal user can't run nfsd if it isn't
already running on the system, and can't control what it exports if it is.
Maybe I'll profile it and look at speeding it up later, but not anytime
soon...
Rob
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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:[~2005-01-25 20:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 21:28 [uml-devel] SIGSEGV and SA_NODEFER Jeff Dike
2005-01-20 0:07 ` Blaisorblade
2005-01-20 3:52 ` Rob Landley
2005-01-21 12:35 ` Blaisorblade
2005-01-21 18:18 ` Rob Landley
2005-01-21 19:58 ` Blaisorblade
2005-01-22 16:34 ` Rob Landley
2005-01-24 19:45 ` Blaisorblade
2005-01-25 1:38 ` Rob Landley
[not found] ` <20050125084506.GA562@bytesex>
2005-01-25 10:16 ` Blaisorblade
2005-01-25 10:16 ` Rob Landley
2005-01-25 11:40 ` Blaisorblade
2005-01-25 17:30 ` Rob Landley
2005-01-25 19:34 ` Blaisorblade
2005-01-25 19:30 ` Rob Landley [this message]
2005-01-25 20:50 ` Blaisorblade
2005-01-25 22:43 ` Rob Landley
2005-01-21 13:09 ` Blaisorblade
2005-01-21 16:56 ` 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=200501251430.26927.rob@landley.net \
--to=rob@landley.net \
--cc=blaisorblade@yahoo.it \
--cc=kraxel@bytesex.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.