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]
Message-id: <200704111527.04905.gene.heskett@gmail.com>
Date:	Wed, 11 Apr 2007 15:27:04 -0400
From:	Gene Heskett <gene.heskett@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	Olaf Hering <olaf@...fle.de>,
	Dave Dillow <dave@...dillows.org>,
	Dave Jones <davej@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, Jeff Garzik <jeff@...zik.org>
Subject: Re: I give up

On Wednesday 11 April 2007, Jan Engelhardt wrote:
>On Apr 10 2007 23:54, Gene Heskett wrote:
>>>>>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.
>>>
>>>FreeBSD also seems to be quite "dynamic".
>>>/dev/da0 is (0,92) for the 'fixit shell' -- how about you?
>>
>>I don't have such a beast here.  Whats that supposed to do?
>
>Well I was just pointing out that Linux is not the only one to have
> device numbers (for promiment block-backed storage) that can move
> across reboots.
>
Which is one more argument in favor of fixing tar, Jorg not withstanding.  
Yeah, that Jorg...  AFAIC, time & technology move on, and I believe I see 
a future where the actual device number might not be the same across a 
reboot, for reasons a hell of a lot less clear than what triggered this 
latest 3 week long battle with something so simple as making a backup.

But, its a battle we'll never win with Jorg stirring the pot, he is the 
single, most vociferous opponent of anything labeled progress that I've 
ever had the displeasure to trying to follow in his rants, and that IS 
what they are, on this and on the scsi list when I was subscribed there.

I do think that a reasoned argument could be made to Paul Eggert, for at 
least a command line option to be made available that would cause tar to 
ignore it, process it yes, but ignore it for --listed-incremental in 
particular.  Maybe even make it part of the --listed-incremental as a 
permanent feature.  For us, that would be the ideal.  It is not an issue 
for level 0's of course.

But my single voice is not going to be able to effect a campaign, its 
going to take a general consensus of all the movers and shakers of linux, 
TPTB if you will, all ganging up on Paul.  Or someone doing a patch to 
that effect, then making distro packages out of it, such as debs, rpm's, 
etc, etc.  A fork I think its called.

There is another also listed in the tar ChangeLog, but I haven't rx'd a 
response from that person although he was Cc:'d at the time.

Dave Dillow, you mentioned another routine in tar that might be an 
educational file to walk through, besides the compare.c I tried to play 
with and apparently broke, can you repeat that phrase again?  I might 
take a stick and poke around in that one too.  Maybe I can un-break 
it? :)

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Earn cash in your spare time -- blackmail your friends.
-
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