public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jakob Østergaard" <jakob@unthought.net>
To: Ville Herva <vherva@twilight.cs.hut.fi>,
	Alexander Viro <viro@math.psu.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: [STATUS 2.5]  January 18, 2002
Date: Sat, 19 Jan 2002 23:24:55 +0100	[thread overview]
Message-ID: <20020119232455.D12692@unthought.net> (raw)
In-Reply-To: <3C477B7F.22875.11D4078A@localhost> <Pine.GSO.4.21.0201180546310.296-100000@weyl.math.psu.edu> <3C488E84.A1453ED2@zip.com.au> <20020119184259.GE135220@niksula.cs.hut.fi>
In-Reply-To: <20020119184259.GE135220@niksula.cs.hut.fi>; from vherva@niksula.hut.fi on Sat, Jan 19, 2002 at 08:43:00PM +0200

On Sat, Jan 19, 2002 at 08:43:00PM +0200, Ville Herva wrote:
> Alexander Viro wrote:
> > 
> > Merged: Per-process namespaces, late-boot cleanups.
> > Ready: switch to ->get_super() as primary file_system_type method.
> > Ready: ->getattr() handling and changes of ->setattr()/->permission()
> > prototypes.
> > Pending: proper UFS fixes, ext2 cleanups and locking
> > changes.
> > Pending: per-mountpoint read-only, union-mounts and unionfs.
> > Pending: lifting limitations on mount(2)
> > In progress: killing kdev_t for block devices (switch to struct block_device *)
> > Started: UMSDOS rewrite (the damn thing blocks struct inode trimming)
> > Planned: new mount API.
> 
> All this seems very neat. One question: what about forced umount / forced
> remount readonly stuff? Any plans on that?
> 

That would be *very* nice indeed.  Even if it was only for things like NFS
and SMBFS.

And even if it is unsafe - it's a lot better to be able to say "screw those
pending writes", than to have to say "screw the pending writes by rebooting the
system".

Just my 0.02 Euro

-- 
................................................................
:   jakob@unthought.net   : And I see the elder races,         :
:.........................: putrid forms of man                :
:   Jakob Østergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............:

  reply	other threads:[~2002-01-19 22:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-18  6:33 [STATUS 2.5] January 18, 2002 Guillaume Boissiere
2002-01-18  7:26 ` Tomasz Kłoczko
2002-01-18  7:29 ` Jens Axboe
2002-01-18  7:53 ` hjb
2002-01-18 10:00   ` Russell King
2002-01-18 10:20 ` Alan Cox
2002-01-18 15:09   ` Arnaldo Carvalho de Melo
2002-01-18 15:17     ` Arnaldo Carvalho de Melo
2002-01-18 10:57 ` Alexander Viro
2002-01-18 21:07   ` Andrew Morton
2002-01-19 18:43     ` Ville Herva
2002-01-19 22:24       ` Jakob Østergaard [this message]
2002-01-19 22:42         ` Ville Herva
2002-01-19 22:53         ` Alexander Viro
2002-01-23 11:31           ` Pavel Machek
2002-01-23 22:55             ` Alexander Viro
2002-01-24 12:29               ` force umount [was Re: [STATUS 2.5] January 18, 2002] Pavel Machek
2002-01-24 17:00                 ` Denis Vlasenko
2002-01-23 22:57             ` [STATUS 2.5] January 18, 2002 Alexander Viro
2002-01-18 11:21 ` Dave Jones
2002-01-20 12:02 ` Eric W. Biederman
2002-01-20 12:37   ` David Weinehall
2002-01-20 22:57     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2002-01-19  9:17 Rick A. Hohensee

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=20020119232455.D12692@unthought.net \
    --to=jakob@unthought.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vherva@twilight.cs.hut.fi \
    --cc=viro@math.psu.edu \
    /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