DragonFly kernel List (threaded) for 2005-03
Re: Journaling layer update - any really good programmer want to start working on the userland journal scanning utility ? You need to have a LOT of time available!
IMHO it's not necessary to seperate journaling options/config from fstab
unless they are making fstab very hard to maintain or there are tech
difficulties in doing so etc.
For a user who is familiar with unix or unix-like systems but new to
dflybsd, the first thing he may be trying is 'man mount' or 'man fstab'
if he wants to look for any fs-related options he doesn't know.
mountctl.conf sounds relevant and neat too :)
On Tue, Mar 08, 2005 at 10:23:48AM +0800, Bill Hacker wrote:
> Date: Tue, 08 Mar 2005 10:23:48 +0800
> From: Bill Hacker <wbh@xxxxxxxxxxxxx>
> To: kernel@xxxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: Journaling layer update - any really good programmer want to
> start working on the userland journal scanning utility ? You need to have
> a LOT of time available!
> Message-Id: <422d0cb5$0$717$415eb37d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
> Newsgroups: dragonfly.kernel
> Matthew Dillon wrote:
> >:Since journals aren't persistant across reboots, this would be of
> >:limited use now. So, what are you going to do about that? Having some
> >:kind of /etc/rc.d/journal script that will mountctl the partitions,
> >:perhaps reading the data from e.g. /etc/mountctl.conf, or are you going
> >:to store the journal info in the filesystem, perhaps in the superblock?
> > I think we'd want something like an /etc/mountctl.conf, yes. I'd
> > integrate
> > it into /etc/fstab if I could, but /etc/fstab is already too full of
> > junk.
> > -Matt
> How about creating:
> '/etc/jfstab' - or '/etc/dfjstab'
> ..specifically, and only, for the purpose of managing this
> Keeps it out of potential confusion with non-DragonFly tools...