From: Jeff Davis <reiser-list@empires.org>
To: reiserfs-list@namesys.com
Subject: Re: reiser4 as module
Date: Wed, 21 Jul 2004 21:22:10 -0700 [thread overview]
Message-ID: <1090470129.1676.56.camel@jeff> (raw)
In-Reply-To: <40FF397C.1000402@slaphack.com>
> I don't know how to get UML to work with reiser4, but I'm sure it can be
> done, as I've heard Namesys people say they use that to develop under.
> So there, yes, you'd have to reboot your UML kernel, but you could be
> doing other things while that happened -- and it wouldn't take long for
> it to reboot anyway.
>
Thanks. I think I'll try UML, I've been meaning to try that for a while.
> Possible, and may have some other uses. But why would anyone want to
> put config files in a database? With reiser4's handling of small files
> and things like NFS, I can't find a single reason. Also, if you're
My idea was more from concern about duplicating data. Let's say it's DNS
data that you already have in a SQL database, and you just want the
named.conf to reflect the data without using update scripts.
> going to start python, run a python script which accesses a database,
> take the results and send them to kernel space, then back to user space,
> you're talking about serious performance issues vs. just leaving the
> config files alone, as flat text.
Yeah, which sometimes matters, and sometimes doesn't (like when reading
a config file).
> cd /path/to
> mkfifo script.pipe
> while true; do
> ./script.py > script.pipe;
> done
Wow. I feel dumb. That pretty much takes care of my problems right
there. Thanks for educating me.
Regards,
Jeff
next prev parent reply other threads:[~2004-07-22 4:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 23:17 rip? Dirk Wetter
2004-07-22 2:00 ` reiser4 as module Jeff Davis
2004-07-22 3:50 ` David Masover
2004-07-22 4:22 ` Jeff Davis [this message]
2004-07-22 10:13 ` mjt
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=1090470129.1676.56.camel@jeff \
--to=reiser-list@empires.org \
--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.