From: Jeff Garzik <jeff@garzik.org>
To: Gene Heskett <gene.heskett@gmail.com>
Cc: linux-kernel@vger.kernel.org, Olaf Hering <olaf@aepfle.de>,
Dave Dillow <dave@thedillows.org>, Dave Jones <davej@redhat.com>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: I give up
Date: Tue, 10 Apr 2007 04:19:44 -0400 [thread overview]
Message-ID: <461B48A0.5010009@garzik.org> (raw)
In-Reply-To: <200704100351.33699.gene.heskett@gmail.com>
Gene Heskett wrote:
> On Tuesday 10 April 2007, Olaf Hering wrote:
>> On Mon, Apr 09, Dave Dillow wrote:
>>> It's not /dev he's backing up -- its /home, /usr, and others. GNU tar
>>> saves the device and inode numbers from the {,l}stat() call on each
>>> file and decides it is a new file if either number changes from run to
>>> run.
>> So fix tar to not do silly things.
>> Kernel major:minor numbers are not stable.
>
> YOU Tell that to the tar/star people, they are flabbergasted that its not
> stable. It apparently is for every other OS tar can be run on.
It's just the new world that we live in.
I don't see us ever going back to 100% static major/minors.
Though as a point of history, Linux has /always/ supported dynamic
major/minor numbers, even back in 0.99 days. We avoided the problem
then because the dynamic major/minors were only used by drivers that had
not yet had static numbers assigned, or their author chose to avoid
LANANA for some other reason.
Jeff
next prev parent reply other threads:[~2007-04-10 8:19 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 14:07 I give up Gene Heskett
2007-04-09 14:47 ` Jeff Garzik
2007-04-09 15:37 ` Gene Heskett
2007-04-09 16:49 ` Jan Engelhardt
2007-04-09 17:03 ` H. Peter Anvin
2007-04-09 18:36 ` Gene Heskett
2007-04-09 19:38 ` Gene Heskett
2007-04-09 21:35 ` Jan Engelhardt
2007-04-09 22:22 ` Dave Dillow
2007-04-10 1:27 ` Dave Jones
2007-04-10 1:40 ` Dave Dillow
2007-04-10 2:01 ` Dave Jones
2007-04-10 7:12 ` Olaf Hering
2007-04-10 7:51 ` Gene Heskett
2007-04-10 8:19 ` Jeff Garzik [this message]
2007-04-10 16:08 ` Olaf Hering
2007-04-10 17:29 ` David Lang
2007-04-10 16:14 ` Jan Engelhardt
2007-04-11 3:54 ` Gene Heskett
2007-04-11 15:39 ` Jan Engelhardt
2007-04-11 15:51 ` John Stoffel
2007-04-11 19:29 ` Gene Heskett
2007-04-11 20:27 ` John Stoffel
2007-04-11 21:16 ` Gene Heskett
2007-04-11 21:26 ` John Stoffel
2007-04-11 19:27 ` Gene Heskett
2007-04-10 7:53 ` Gene Heskett
2007-04-10 12:24 ` John Anthony Kazos Jr.
2007-04-10 20:45 ` Gene Heskett
2007-04-10 19:05 ` Phillip Susi
2007-04-11 4:01 ` Gene Heskett
2007-04-11 14:46 ` Phillip Susi
2007-04-11 15:07 ` Gene Heskett
2007-04-11 15:12 ` John Anthony Kazos Jr.
2007-04-11 16:43 ` Krzysztof Halasa
2007-04-11 17:03 ` Jan Engelhardt
2007-04-10 3:47 ` Gene Heskett
2007-04-10 3:41 ` Gene Heskett
2007-04-09 17:11 ` John Stoffel
2007-04-09 19:49 ` Gene Heskett
2007-04-09 20:08 ` John Stoffel
2007-04-09 20:11 ` Jeff Garzik
2007-04-09 20:08 ` Jeff Garzik
2007-04-09 20:32 ` Ralf Baechle
2007-04-09 20:44 ` Jeff Garzik
2007-04-09 20:51 ` H. Peter Anvin
2007-04-09 20:33 ` Valdis.Kletnieks
2007-04-09 20:47 ` Jeff Garzik
2007-04-10 3:34 ` Gene Heskett
2007-04-10 3:38 ` John Stoffel
2007-04-10 6:50 ` Jeff Garzik
2007-04-10 6:59 ` CaT
2007-04-10 17:52 ` H. Peter Anvin
2007-04-11 3:57 ` Gene Heskett
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=461B48A0.5010009@garzik.org \
--to=jeff@garzik.org \
--cc=dave@thedillows.org \
--cc=davej@redhat.com \
--cc=gene.heskett@gmail.com \
--cc=hpa@zytor.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox