From: Manuel Krause <manuelkrause@netscape.net>
To: reiserfs-list <reiserfs-list@namesys.com>
Subject: BTW: 2.4.19-patches-to-come?
Date: Tue, 07 May 2002 03:15:29 +0200 [thread overview]
Message-ID: <3CD72AB1.6010607@netscape.net> (raw)
Hi!
BTW, for 2.4.19-final it would be very nice to have...
1.) the deleted/truncated/completed-files-on-mount at least
printed in the kernel logs, at best with the real filename
-- as afterwards they are not retrievable --
That's a security reason -- whoever can trigger a crash
with various methods (I know the admin should take care
against this case... but on my home sytem I'd like to know
that info, too) but to get back the file from backups in
case... who knows it before a
crash... ? Am I missing something?
2.) a disk/drive/partition distinction in reiserfs related
messages -- Oleg, you promised it to get real and best
would be a real "patch" !
3.) a hint on how to turn on/off data-journaling for "some"
of our existing reiserfs partitions if it exists at all
for now and why it could be needed in some cases?!.
4.) a hint why there is iicache code in the latest
speedup-compound-patch (so that the latest iicache patch
would not apply)
Best regards for your stable ReiserFS, at all,
even under "settings" with 2.4.19-pre7 +reiserfs.pending +latest
reiserfs.compound-speedup +aa.vm-for-2.4.19-pre7 +akpm.read-latency-2
+rml.preempt-kernel + rml.lock-break +some-more nice aa.patches...
That's a valuably fast & interactive experience!
Manuel
next reply other threads:[~2002-05-07 1:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 1:15 Manuel Krause [this message]
2002-05-07 5:22 ` BTW: 2.4.19-patches-to-come? Oleg Drokin
2002-05-07 14:02 ` Yury Yu. Rupasov
2002-05-07 19:35 ` Manuel Krause
2002-05-08 5:30 ` Oleg Drokin
2002-05-08 13:04 ` Chris Mason
2002-05-08 13:08 ` Oleg Drokin
2002-05-08 13:16 ` Chris Mason
2002-05-08 13:20 ` Oleg Drokin
2002-05-08 13:34 ` Chris Mason
2002-05-17 1:49 ` Manuel Krause
2002-05-17 4:56 ` Oleg Drokin
2002-05-17 9:47 ` Pierre Etchemaite
2002-05-17 9:47 ` Oleg Drokin
2002-05-07 13:52 ` Yury Yu. Rupasov
2002-05-07 20:41 ` Manuel Krause
-- strict thread matches above, loose matches on Subject: below --
2002-05-17 15:36 Dieter Nützel
2002-05-17 15:47 ` Chris Mason
2002-05-17 18:20 ` Dieter Nützel
2002-05-17 18:26 ` Dieter Nützel
2002-05-17 15:54 ` Oleg Drokin
2002-05-17 17:05 ` Dieter Nützel
2002-05-17 18:28 ` Oleg Drokin
2002-05-17 19:44 ` Dieter Nützel
2002-05-18 5:44 ` Oleg Drokin
2002-05-18 13:18 ` Dieter Nützel
2002-05-18 16:29 ` Oleg Drokin
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=3CD72AB1.6010607@netscape.net \
--to=manuelkrause@netscape.net \
--cc=reiserfs-list@namesys.com \
/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.