From: Ookhoi <ookhoi@humilis.net>
To: Oleg Drokin <green@namesys.com>
Cc: Ookhoi <ookhoi@humilis.net>, Nikita Danilov <Nikita@namesys.com>,
Reiserfs mail-list <Reiserfs-List@namesys.com>,
Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>
Subject: Re: [reiserfs-dev] Re: [ANNOUNCE]: reiser4 snapshot
Date: Thu, 16 Jan 2003 09:31:19 +0100 [thread overview]
Message-ID: <20030116093119.H7526@humilis> (raw)
In-Reply-To: <20030116112254.A7254@namesys.com>
Oleg Drokin wrote (ao):
> On Thu, Jan 16, 2003 at 09:14:20AM +0100, Ookhoi wrote:
> > Is there also a BK repository with the reiserfs4-progs?
>
> Sure.
> bk://thebsh.namesys.com/bk/reiser4progs
Thanks :-)
> > And what is the right way to integrate reiser4 into the kernel? At
> > the moment I pull reiser4 and linux-2.5, patch linux-2.5 with the
> > reiser4.diff out of the snapshots dir, and replace fs/reiser4 with
> > the BK reiser4.
> > This works*, but I think the patch part is not the right way.
>
> Well. It is most right way actually. (besides pulling from our kernel
> repository, but we have different UML-related stuff in there so that
> might not be very good idea for you).
> Probably starting with next snapshot there will be separate kernel
> patch for people who would like to pull our tree directly out of
> bitkeeper.
Owh, cool!.
> > * I can compile a 2.5 kernel, boot it, and mkfs.reiser4 a partition.
>
> Great success at our side! ;)
> Though I see you have not tried to mount that?
Ehm, sorry, I can also mount it. But the last few times I tried to wget
base2_2.tar (debian base) on it, it oopses immediately. As the system is
a kernel plus initrd on a floppy, I can't catch the oops.
At the moment I try to build a kernel which decodes the oops by itself
and provide it to you (if it still oopses). Problem is that the kernel
gets too big, so now I try to wget the big kernel and boot it from out
of the initrd.
It is really great to be able to pull latest versions from BK and play
with it. I'll report success or failure.
Thanks again!
next prev parent reply other threads:[~2003-01-16 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-24 16:40 [ANNOUNCE]: reiser4 snapshot Nikita Danilov
2003-01-16 8:14 ` Ookhoi
2003-01-16 8:22 ` [reiserfs-dev] " Oleg Drokin
2003-01-16 8:31 ` Ookhoi [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-17 10:33 Nikita Danilov
2003-01-17 12:09 ` Ookhoi
2003-01-17 12:12 ` [reiserfs-dev] " Oleg Drokin
2003-01-17 12:14 ` Ookhoi
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=20030116093119.H7526@humilis \
--to=ookhoi@humilis.net \
--cc=Nikita@namesys.com \
--cc=Reiserfs-Dev@namesys.com \
--cc=Reiserfs-List@namesys.com \
--cc=green@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.