linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Glynn Clements <glynn@gclements.plus.com>
To: Sion Khalaf <Sion@bitband.com>
Cc: linux-admin@vger.kernel.org
Subject: RE: Quota for root ?
Date: Wed, 8 Mar 2006 01:53:07 +0000	[thread overview]
Message-ID: <17422.14595.177825.355357@cerise.gclements.plus.com> (raw)
In-Reply-To: <83CA05F64804AF43B8F733C4ABDFAA51010DEB32@mail1.bitband.com>


Sion Khalaf wrote:

> There is no possibility to do the first solution.
> The second, regarding drive  mounting, is it ram drive?

No, loopback filesystem.

> If so, How to mount it ?

	mount -o loop <filename> <mount point>

To create the file, first create a suitably-sized file with e.g.:

	dd if=/dev/zero out=loopfile.dat bs=1m count=100	#100Mb

then create a filesystem on it with:

	mke2fs -F loopfile.dat

> Anyway, I am looking for a way to make my file system read only.
> That will surely, be the best solution.
> 
> My application is writing into certain folder, not on the physically /
> File system,
> So I can make the / FS read only, Do you have an idea how can I do that
> ?

Normally, directories which need to be writable, e.g. /var and /tmp,
would use separate partitions. Those partitions would be writable (but
probably using the noexec and nodev options), but the root filesystem
would be read-only.

The most common issue with making the root filesystem read-only is
that "mount" tries to write to /etc/mtab, which will fail. Either use
the -n option to mount or recompile mount to use e.g. /var/run/mtab
instead.

-- 
Glynn Clements <glynn@gclements.plus.com>

  reply	other threads:[~2006-03-08  1:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08  0:03 Quota for root ? Sion Khalaf
2006-03-08  1:53 ` Glynn Clements [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-08  6:12 Sion Khalaf
2006-03-08 12:36 ` hackmiester (Hunter Fuller)
2006-03-07 19:00 Sion Khalaf
2006-03-07 19:16 ` David Fierbaugh

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=17422.14595.177825.355357@cerise.gclements.plus.com \
    --to=glynn@gclements.plus.com \
    --cc=Sion@bitband.com \
    --cc=linux-admin@vger.kernel.org \
    /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).