All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Matthias Koenig <mkoenig@suse.de>
Cc: linux-ext4@vger.kernel.org, hvogel@suse.de,
	Girish Shilamkar <Girish.Shilamkar@Sun.COM>,
	Eric Sandeen <esandeen@redhat.com>
Subject: Re: Integrating patches in SLES10 e2fsprogs
Date: Mon, 28 Jan 2008 10:38:02 -0500	[thread overview]
Message-ID: <20080128153802.GB17752@mit.edu> (raw)
In-Reply-To: <n7x1w82nf7m.fsf@sor.suse.de>

On Mon, Jan 28, 2008 at 04:26:53PM +0100, Matthias Koenig wrote:
> > Patch6:         e2fsprogs-mdraid.patch
> >
> > This apparently adds a new environment variable,
> > BLKID_SKIP_CHECK_MDRAID, which forces blkid to not detect mdraid
> > devices.  I'm not sure why.
> 
> Workaround for people having stale RAID signature on their disk:
> https://bugzilla.novell.com/show_bug.cgi?id=100530

Hmm... there's got to be a better way around this.

I'm not authorized to look at that BZ entry.  Is there any way you can
make my "tytso" account have access to any e2fsprogs related BZ
entries?  Thanks!

> > Patch12:        e2fsprogs-mkinstalldirs.patch
> >
> > Why?
> 
> Is needed since we recreate the auto* files.
> But I agree that this patch should better set
> MKINSTALLDIRS = @MKDIR_P@
> not to literal "mkdir -p". The @MKINSTALLDIRS@ seems to be
> obsolete in newer gettext (which seems to pull this in).

Are you running aclocal?  That may be causing the issues since I think
that may be causing it to ignore the autoconf macros I've established
in the top-level aclocal.m4 file.

> > Patch22:        e2fsprogs-1.40.4-uuidd_pid_path.patch
> >
> > The problem with this patch is that /var/run is cleared via rm -rf, so
> > it is highly problamtic to put the scratch directory for uuidd in
> > /var/run.
> 
> Are you really sure? My interpretation of FHS is, that files under
> /var/run/ have to be cleared or truncated, but the subdirectories do not
> get deleted.

The problem is that the FHS does not guarantee that the subdirectories
stick around, and a number of distro's are using mounting tmpfs for
/var/run.  Makes sense, it can significantly speed up operations ---
but upon reboot, everything in /var/run is *gone*.


Please let me know when you have a newer OpenSUSE factory RPM ready
for use, and I'll take a look at the remaining patches and see which
ones are ready for merging upstream.  Markus managed to convince me it
was worthwhile to install the latest OpenSUSE on a laptop so I could
see how things are shaping up, and I have to say I'm pretty impressed.
I haven't updated it to try tracking the latest OpenSUSE factory
RPM's, and I still haven't figured out how to easily build my own
custom kernel RPM's on OpenSUSE, but it's quite nice.

On my "one of these days" list is to get another cheap/used laptop so
I can try out the latest Fedora Core Rawhide without having to fire up
a huge (noisy) x86_64 box....

						- Ted

  reply	other threads:[~2008-01-28 15:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24 21:17 Integrating patches in SLES10 e2fsprogs Andreas Dilger
2008-01-24 21:27 ` Eric Sandeen
2008-01-25 15:22 ` Matthias Koenig
2008-01-27  5:05   ` Theodore Tso
2008-01-27 15:06     ` Eric Sandeen
2008-01-27 20:27       ` Theodore Tso
2008-01-28  4:40         ` Eric Sandeen
2008-01-28  5:24           ` Theodore Tso
2008-01-28  5:43             ` Eric Sandeen
2008-01-28 16:01             ` Thierry Vignaud
2008-01-28 16:06               ` Thierry Vignaud
2008-01-28 17:03                 ` Theodore Tso
2008-01-28 17:00               ` Theodore Tso
2008-01-28 15:26     ` Matthias Koenig
2008-01-28 15:38       ` Theodore Tso [this message]
2008-01-28 16:54         ` Eric Sandeen
2008-01-28 20:59           ` Andreas Dilger
2008-01-29 13:52         ` Matthias Koenig
2008-01-29 14:35           ` Theodore Tso

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=20080128153802.GB17752@mit.edu \
    --to=tytso@mit.edu \
    --cc=Girish.Shilamkar@Sun.COM \
    --cc=esandeen@redhat.com \
    --cc=hvogel@suse.de \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mkoenig@suse.de \
    /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.