Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0000966]: [PARTIAL PATCH] Add support for dump/restore
Date: Mon, 12 Feb 2007 05:34:16 -0800	[thread overview]
Message-ID: <bb62b5f4c0600a56e83074509da4dd3d@bugs.busybox.net> (raw)


The following issue has been ASSIGNED. 
====================================================================== 
http://busybox.net/bugs/view.php?id=966 
====================================================================== 
Reported By:                redhatter
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   966
Category:                   New Features
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             07-21-2006 06:32 PDT
Last Modified:              02-12-2007 05:34 PST
====================================================================== 
Summary:                    [PARTIAL PATCH] Add support for dump/restore
Description: 
The EXT2/3 file system backup utilities, dump & restore, can be made to
successfully compile against ?Clibc, provided a blank 'fstab.h' file is
inserted into the build_${ARCH}/staging_dir/includes directory in
buildroot.

This patch, is a partial update to dump, with modifications to e2fsprogs,
to allow cross-compilation of dump.
====================================================================== 

---------------------------------------------------------------------- 
 redhatter - 07-21-06 06:34  
---------------------------------------------------------------------- 
Almost forgot the Config.in and dump.mk files. ;-)  Naturally, these go in
the packages/dump/ directory. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-21-06 06:32  redhatter      New Issue                                    
07-21-06 06:32  redhatter      Status                   new => assigned     
07-21-06 06:32  redhatter      Assigned To               => uClibc          
07-21-06 06:32  redhatter      File Added: add-dump.diff                    
07-21-06 06:33  redhatter      File Added: Config.in                        
07-21-06 06:33  redhatter      File Added: dump.mk                          
07-21-06 06:34  redhatter      Note Added: 0001547                          
02-12-07 05:34  vapier         Assigned To              uClibc => buildroot 
======================================================================

                 reply	other threads:[~2007-02-12 13:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bb62b5f4c0600a56e83074509da4dd3d@bugs.busybox.net \
    --to=bugs@busybox.net \
    --cc=buildroot@busybox.net \
    /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