public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Seemant Kulleen <seemant@gentoo.org>
To: Jeff Breitner <lists@rudn.com>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Boot FSCK
Date: Tue, 13 Jan 2004 15:50:27 -0800	[thread overview]
Message-ID: <1074037827.15540.34.camel@sephora> (raw)
In-Reply-To: <40043AB2.9040705@rudn.com>

[-- Attachment #1: Type: text/plain, Size: 548 bytes --]

On Tue, 2004-01-13 at 10:36, Jeff Breitner wrote:
> I'm trying to track down a problem (submitted to bugzilla) and am having 
> a problem finding where the fsck routines are called in gentoo.  Any 
> help appreciated.
> 
> --
> gentoo-dev@gentoo.org mailing list

/etc/init.d/checkfs
-- 
Seemant Kulleen
Developer and Project Co-ordinator,
Gentoo Linux					http://dev.gentoo.org/~seemant

Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x3458780E
Key fingerprint = 23A9 7CB5 9BBB 4F8D 549B 6593 EDA2 65D8 3458 780E


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-01-13 23:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 18:36 [gentoo-dev] Boot FSCK Jeff Breitner
2004-01-13 23:50 ` Seemant Kulleen [this message]

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=1074037827.15540.34.camel@sephora \
    --to=seemant@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=lists@rudn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox