lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 10 Apr 2007 10:29:41 -0700 (PDT)
From:	David Lang <david.lang@...italinsight.com>
To:	Olaf Hering <olaf@...fle.de>
cc:	Gene Heskett <gene.heskett@...il.com>,
	linux-kernel@...r.kernel.org, Dave Dillow <dave@...dillows.org>,
	Dave Jones <davej@...hat.com>,
	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	"H. Peter Anvin" <hpa@...or.com>, Jeff Garzik <jeff@...zik.org>
Subject: Re: I give up

On Tue, 10 Apr 2007, Olaf Hering wrote:

> On Tue, Apr 10, 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.
>
> I forgot to add: '.. not stable across reboots.'
>
>> 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.
>
> They probably have a point with the st_dev usage.
> You better find out why your major:minor pairs keep jumping around.
> Simply because the 'not stable across reboot' statement holds only for
> added/removed disks and maybe if the detection order changes.
> If your setup relies on a certain order, make sure the drivers get
> loaded in a fixed order. Its not clear from your other mails what
> exactly caused it. If its only due to a temporary change in
> testkernels, noone can do anything about it.

he's running into problems when he adds additional drivers to the kernel (I 
don't remember which drivers, he's mentioned them earlier in this thread)

David Lang
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ