From: Dave Dillow <dave@thedillows.org>
To: Dave Jones <davej@redhat.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Gene Heskett <gene.heskett@gmail.com>,
linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: I give up
Date: Mon, 09 Apr 2007 21:40:46 -0400 [thread overview]
Message-ID: <1176169246.3193.2.camel@obelisk.thedillows.org> (raw)
In-Reply-To: <20070410012754.GD1994@redhat.com>
On Mon, 2007-04-09 at 21:27 -0400, Dave Jones wrote:
> On Mon, Apr 09, 2007 at 06:22:10PM -0400, Dave Dillow wrote:
> > On Mon, 2007-04-09 at 23:35 +0200, Jan Engelhardt wrote:
> > > On Apr 9 2007 15:38, Gene Heskett wrote:
> > > >On Monday 09 April 2007, H. Peter Anvin wrote:
> > > >>Jan Engelhardt wrote:
> > > >>> dm is on 254 for me.. in opensuse with a 2.6.20 that is. I wonder why
> > > >>> it even moves around. However, even then, those who use udev and
> > > >>> device names rather than (major,minor) tuples should not have any
> > > >>> problem.
> > > >>
> > > >>It moves around because someone at some point thought it was a great
> > > >>idea to assign dynamic majors to core functionality.
> > > >>
> > > >What were they smoking, I want some of that!
> > >
> > > Do you actually use udev?
> >
> > udev doesn't help the problem he is having (and he is using it, since he
> > is using Fedora).
>
> However, it also doesn't explain what the point is of backing up /dev
> when it's dynamically created.
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.
You are correct about /dev -- who'd back it up if it is dynamically
created? But that is also not the problem Gene is having.
next prev parent reply other threads:[~2007-04-10 1:40 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 14:07 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 [this message]
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
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=1176169246.3193.2.camel@obelisk.thedillows.org \
--to=dave@thedillows.org \
--cc=davej@redhat.com \
--cc=gene.heskett@gmail.com \
--cc=hpa@zytor.com \
--cc=jeff@garzik.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®