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 16:45:18 -0400
From:	Gene Heskett <gene.heskett@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	"John Anthony Kazos Jr." <jakj@...-k-j.com>,
	Olaf Hering <olaf@...fle.de>,
	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 Tuesday 10 April 2007, John Anthony Kazos Jr. wrote:
>> >So fix tar to not do silly things.
>> >Kernel major:minor numbers are not stable.
>>
>> YOU Tell the tar people, they are flabbergasted that linux is
>> apparently the only unstable OS that tar can be run on.
>
>Linux is not unstable. It's developmental! Linux is like one giant
>international research project marching toward the future of computing.
>MacOS (oh, how I miss System 7.5.5), Windows (shoot me, please), BSD
>(wannabe GNU/Linux), and everything else are there just for companies to
>spend money on and idiots to drool over until Linux is ready to stand up
>and say "Yo. It's just bugfixes and improvements from here. You can put
>the Legos down now."

I don't know who you are, but that's not germane to this discussion, what 
is germane is that once the experimental label has been removed from 
something as capable of screwing up the system as the LMV stuff is, then 
there is no excuse not to give it a LANANA compatible address and quit 
screwing up peoples backup systems just because they turned on pktcdvd or 
md or some other similar option in a make xconfig.  FWIW, md, for raid 
users, should get the same treatment since raids often can have 
terrabytes of data to be backed up.

The patch to do that caught tar users totally off-guard, but once we(I) 
understood why it was done, it was obviously a good patch.  But rather 
than explaining WTF it was doing so we/I understood the reason for the 
pain, the *&%^ patch was reverted, starting the backup related screwups 
all over again from scratch.

Now this thread has a life of its own, and the noise it continues to make 
will prevent the re-application of that patch which WILL stabilize 
things, probably until hell freezes over and pigs can use it for a 
takeoff runway.

I have a fix (thanks Dave D.) worked out for MY system, and you guys can 
do as you damned well please, until you break my fix anyway.  In the 
meantime, I have backup.sh, my amdump wrapper, running every 3 hours 
around the clock without a verify stage until it has managed to update 
all 118 (about 20 megs worth) of its reference files.  I expect that to 
take 3 or 4 days.  Hopefully my drives are up to the torture, if not, 
well they aren't that precious & I CAN drop the card for more & might 
even do that yet tonight unless Circuit City or Staples think that a 
500Gb is still worth its weight in gold bar.  Yes, I spend my money 
locally where possible.

-- 
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)
"Don't discount flying pigs before you have good air defense."
-- jvh@...net.FI
-
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