From: Kenneth Johansson <ken@kieraypc01.tn.sw.ericsson.se>
To: Wolfgang Denk <wd@denx.de>
Cc: Jean-Denis Boyer <jdboyer@mediatrix.com>,
Rod Boyce <rod_boyce@stratexnet.com>,
LinuxPPC-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Creating RAM disks as a non root user.
Date: 05 Feb 2003 11:47:53 +0100 [thread overview]
Message-ID: <1044442073.3146.87.camel@spawn> (raw)
In-Reply-To: <20030204215206.CA7D2C608E@atlas.denx.de>
On Tue, 2003-02-04 at 22:52, Wolfgang Denk wrote:
>
> In message <2702075D4DE2B043BF5EB82E9CFAD45B093BBB@mail1.mediatrix.com> you wrote:
> >
> > Here is the recipe we use to mount ramdisk images without being a root user.
> ...
> > Note that the option 'user' in fstab allows any user to mount/unmount this specific entry.
>
> Just _mounting_ ramdisk images is not the problem...
>
> > You can either create new ramdisk images, or mount already existing ones (very useful!).
>
> ...but to create a useful ramdisk image you will usually also have to
> create the device nodes in the /dev directory. And this is something
> that really _requires_ root permissions (or it would otherwise open
> huge security issues).
>
If you want full control over owner and group on a file by file basis
you can run fakeroot while creating the image/tar or whatever.
I don't know if fakeroot exist anywhere else than in debian but it
should not be hard to port.
--
Kenneth Johansson
Ericsson AB Tel: +46 8 404 71 83
Tellusborgsvägen 94 Fax: +46 8 404 72 72
126 25 Stockholm ken@switchboard.ericsson.se
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-02-05 10:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 21:24 Creating RAM disks as a non root user Jean-Denis Boyer
2003-02-04 21:52 ` Wolfgang Denk
2003-02-05 10:47 ` Kenneth Johansson [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-04 16:30 Kerl, John
2003-02-04 2:03 James Don
2003-02-04 2:00 Rod Boyce
2003-02-04 2:14 ` Wolfgang Denk
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=1044442073.3146.87.camel@spawn \
--to=ken@kieraypc01.tn.sw.ericsson.se \
--cc=jdboyer@mediatrix.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rod_boyce@stratexnet.com \
--cc=wd@denx.de \
/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;
as well as URLs for NNTP newsgroup(s).