All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yury Umanets <umka@namesys.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Domenico Andreoli <cavok@tiscali.it>, reiserfs-list@namesys.com
Subject: Re: fsck.reiser4 can't fix 1 fixable corruption
Date: Fri, 23 Apr 2004 10:04:57 +0300	[thread overview]
Message-ID: <1082703897.3616.9.camel@firefly> (raw)
In-Reply-To: <40880F5C.6080207@namesys.com>

On Thu, 2004-04-22 at 21:30, Hans Reiser wrote:
> Domenico Andreoli wrote:
> 
> >On Wed, Apr 21, 2004 at 09:30:07PM +0200, Sander Sweers wrote:
> >  
> >
> >>NOTE: the ebuilds have /--enable-stand-alone/ to have grub build reiser4 
> >>support.
> >>    
> >>
> >
> >how hard is to have reiser4 support built in grub?
> >
> >-----[ Domenico Andreoli, aka cavok
> > --[ http://filibusta.crema.unimi.it/~cavok/gpgkey.asc
> >   ---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50
> >
> >
> >  
> >
> Yury told me it was done....  Yury....
Hello!

Yes, it was done. But probably it is broken now due to lots of last
changes like new plugins, plugin inheritance, interface changes etc.

We should ask Vitaly what is the status of it now...

-- 
umka


  parent reply	other threads:[~2004-04-23  7:04 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-20 14:33 fsck.reiser4 can't fix 1 fixable corruption Raymond A. Meijer
2004-04-20 18:54 ` Sander Sweers
2004-04-21  8:09   ` Raymond A. Meijer
2004-04-21  8:55 ` Vitaly Fertman
2004-04-21  9:11   ` Raymond A. Meijer
2004-04-21  9:59   ` Raymond A. Meijer
2004-04-21 11:51     ` Vitaly Fertman
2004-04-21 12:05       ` Carl-Daniel Hailfinger
2004-04-21 12:09       ` Raymond A. Meijer
2004-04-21 12:19         ` Sander Sweers
2004-04-21 19:30           ` Sander Sweers
2004-04-21 19:44             ` Domenico Andreoli
2004-04-21 20:13               ` Sander Sweers
2004-04-21 20:53                 ` Domenico Andreoli
2004-04-21 21:13                   ` Vitaly Fertman
2004-04-21 21:58                     ` Domenico Andreoli
2004-04-22 10:46                       ` Vitaly Fertman
2004-04-22 11:44                         ` Domenico Andreoli
2004-04-23  9:15                           ` Vitaly Fertman
2004-04-23 20:19                             ` Hans Reiser
2004-04-23 20:59                               ` Vitaly Fertman
2004-04-24  0:00                                 ` Hans Reiser
2004-04-22 12:37                         ` Domenico Andreoli
2004-04-22 17:51                           ` Hans Reiser
2004-04-22 18:30               ` Hans Reiser
2004-04-23  1:22                 ` Domenico Andreoli
2004-04-25 16:31                   ` Hans Reiser
2004-04-25 20:31                     ` Domenico Andreoli
2004-04-30  3:16                       ` Hans Reiser
2004-04-30 10:18                         ` Vitaly Fertman
2004-04-28  9:09                     ` Vitaly Fertman
2004-04-23  7:04                 ` Yury Umanets [this message]
2004-04-23  9:03                   ` Vitaly Fertman
2004-04-23 10:27                     ` Domenico Andreoli
2004-04-23 12:54                       ` Vitaly Fertman
2004-04-23 11:01                     ` Yury Umanets
2004-04-21 13:30       ` reiser4progs 0.5.4 build error (was Re: fsck.reiser4 can't fix 1 fixable corruption) Domenico Andreoli

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=1082703897.3616.9.camel@firefly \
    --to=umka@namesys.com \
    --cc=cavok@tiscali.it \
    --cc=reiser@namesys.com \
    --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.