Vista, New and improved: KSOD replaces BSOD
AZ Nomad
It hangs during bootup with the mouse pointer over the black desktop and
nothing else. Safemode won't fix it. It's the infamous blacK Screen Of
Death.
Found blogs about the subject. Fixes ranged from editing the registry
to fix a RPC setting to renaming a logfile directory in case of logfile
corruption. Nothing works and microsoft says the filesystem is in a deadlock
and the only solution is to blow away the entire volume. They say they fixed
it in fixpack 1 but don't offer any solution.
This is another constant reminder why I don't use microsoft products. What a
steaming piece of shit. A file system that can get into a such a deadlock is
beyond belief. A file system in such a state that can't be repaired is even
more incredible.
Microsoft doesn't even suggest copying off the file system contents,
reinitializing it, and copying it back. Probably wouldn't work because of
all the nasty copy protection going on and physical file pointers.
And of course, per microsoft direction, the user is to lose all applications
and user files.
At least I have linux on a live CD and can retrieve and backup the
user's files. I could see the user's files with the vista install media,
but of course it is crippled and there's no way to save the files except
one by one.
COLA Sucubus Hunter
<snipped>
Needless to say, that you are a *clown* and shouldn't be let near any
computer to do anything but look at one and not touch.
Ezekiel
"AZ Nomad" <azno...@PremoveOBthisOX.COM> wrote in message
news:slrnh4n2is....@ip70-176-155-130.ph.ph.cox.net...
>
> At least I have linux on a live CD and can ....
Somehow you'll manage to corrupt files and destroy the filesystem on your CD
as well.
William Poaster
of the trolls AZ Nomad was heard to say:
> Got a friends laptop to fix that uses vista. It hangs during bootup with
> the mouse pointer over the black desktop and nothing else. Safemode
> won't fix it. It's the infamous blacK Screen Of Death.
>
> Found blogs about the subject. Fixes ranged from editing the registry
> to fix a RPC setting to renaming a logfile directory in case of logfile
> corruption. Nothing works and microsoft says the filesystem is in a
> deadlock and the only solution is to blow away the entire volume. They
> say they fixed it in fixpack 1 but don't offer any solution.
Ah, the registry. Where M$ puts all *your* eggs in *their* basket.
> This is another constant reminder why I don't use microsoft products.
> What a steaming piece of shit. A file system that can get into a such a
> deadlock is beyond belief. A file system in such a state that can't be
> repaired is even more incredible.
>
> Microsoft doesn't even suggest copying off the file system contents,
> reinitializing it, and copying it back. Probably wouldn't work because
> of all the nasty copy protection going on and physical file pointers.
>
> And of course, per microsoft direction, the user is to lose all
> applications and user files.
Err...but you see the user is *only* the user..they don't own the OS.
M$ does & doesn't give a flying f#ck what the (l)user wants.
> At least I have linux on a live CD and can retrieve and backup the
> user's files. I could see the user's files with the vista install
> media, but of course it is crippled and there's no way to save the files
> except one by one.
What a PITA.
--
"The philosophy behind Free, Open Source Software has parallels in several
cultures which practice *ethical* co-operation. Perhaps that's why it
threatens *unethical* business practices which feed on the unknowing."
-- Bassam A. Hassan -- CoFounder of the ILUG.
Hans Lister
Isn't AzNomad the same guy who had millions of *.tmp files under
Vista?
He sure seems to have an awful lot of file corruption problems.
Erik Funkenbusch
> This is another constant reminder why I don't use microsoft products. What a
> steaming piece of shit. A file system that can get into a such a deadlock is
> beyond belief. A file system in such a state that can't be repaired is even
> more incredible.
Well, then you must not like Linux then.
https://listman.redhat.com/archives/ext3-users/2003-November/msg00024.html
"EXT3 deadlock in 2.4.22 and 2.4.23-pre7"
In fact, a search of "ext3 deadlock" returns 31,000 hits.
Not just ext3 either.
http://osdir.com/ml/linux-ext4/2009-03/msg00065.html
"Fix deadlock in ext4_write_begin() and ext4_da_wri"
This can happen in any kind of complex system. So don't act all high and
mighty because Linux has these problems too.
> And of course, per microsoft direction, the user is to lose all applications
> and user files.
You don't lose your user files when you reinstall.. Windows copies
everything to a folder called "Windows.old"
> At least I have linux on a live CD and can retrieve and backup the
> user's files. I could see the user's files with the vista install media,
> but of course it is crippled and there's no way to save the files except
> one by one.
Or you can use bartpe to make a recovery CD for Windows.
Hans Lister
Beat me to it :)
GPS
> On Wed, 01 Jul 2009 11:10:04 -0500, AZ Nomad wrote:
>
>> This is another constant reminder why I don't use microsoft products.
>> What a
>> steaming piece of shit. A file system that can get into a such a
>> deadlock is
>> beyond belief. A file system in such a state that can't be repaired is
>> even more incredible.
>
> Well, then you must not like Linux then.
>
> https://listman.redhat.com/archives/ext3-users/2003-November/msg00024.html
>
> "EXT3 deadlock in 2.4.22 and 2.4.23-pre7"
>
> In fact, a search of "ext3 deadlock" returns 31,000 hits.
>
> Not just ext3 either.
>
> http://osdir.com/ml/linux-ext4/2009-03/msg00065.html
>
> "Fix deadlock in ext4_write_begin() and ext4_da_wri"
>
> This can happen in any kind of complex system. So don't act all high and
> mighty because Linux has these problems too.
I think the progression of this pattern is supposed to be along the lines of
(paraphrase): "Redhat are shills, and in bed with
Novell/Microsoft/NWO/Satan."
Thus, naturally the ext4 file system is evil, and all people that accuse
Linux of having bugs (even known bugs acknowledged by developers) are
shills.
After that the thread is supposed to progress to name calling, and blame
with perhaps some appeals to authority, until it diverges into the nether
regions of each individual shadow.
So now that we know the pattern, I see no reason to post anymore.
Good day, good night, and if I don't see you again, enjoy the voidness.
-GPS
Mart van de Wege
> On Wed, 01 Jul 2009 11:10:04 -0500, AZ Nomad wrote:
>
>> This is another constant reminder why I don't use microsoft products. What a
>> steaming piece of shit. A file system that can get into a such a deadlock is
>> beyond belief. A file system in such a state that can't be repaired is even
>> more incredible.
>
> Well, then you must not like Linux then.
>
> https://listman.redhat.com/archives/ext3-users/2003-November/msg00024.html
>
> "EXT3 deadlock in 2.4.22 and 2.4.23-pre7"
>
And once again it proves to be worth it to follow your link.
That's not an ext3 deadlock. It's a quota deadlock.
Mart
--
"We will need a longer wall when the revolution comes."
--- AJS, quoting an uncertain source.
Mart van de Wege
>
> I think the progression of this pattern is supposed to be along the lines of
> (paraphrase): "Redhat are shills, and in bed with
> Novell/Microsoft/NWO/Satan."
No.
The progression of this pattern is: "Erik got caught lying again."
Erik Funkenbusch
> Erik Funkenbusch <er...@despam-funkenbusch.com> writes:
>
>> On Wed, 01 Jul 2009 11:10:04 -0500, AZ Nomad wrote:
>>
>>> This is another constant reminder why I don't use microsoft products. What a
>>> steaming piece of shit. A file system that can get into a such a deadlock is
>>> beyond belief. A file system in such a state that can't be repaired is even
>>> more incredible.
>>
>> Well, then you must not like Linux then.
>>
>> https://listman.redhat.com/archives/ext3-users/2003-November/msg00024.html
>>
>> "EXT3 deadlock in 2.4.22 and 2.4.23-pre7"
>>
> And once again it proves to be worth it to follow your link.
>
> That's not an ext3 deadlock. It's a quota deadlock.
In the quota support of ext3.. jesus, how can you not read?
AZ Nomad
>Erik Funkenbusch <er...@despam-funkenbusch.com> writes:
>> On Wed, 01 Jul 2009 11:10:04 -0500, AZ Nomad wrote:
>>
>>> This is another constant reminder why I don't use microsoft products. What a
>>> steaming piece of shit. A file system that can get into a such a deadlock is
>>> beyond belief. A file system in such a state that can't be repaired is even
>>> more incredible.
>>
>> Well, then you must not like Linux then.
>>
>> https://listman.redhat.com/archives/ext3-users/2003-November/msg00024.html
>>
>> "EXT3 deadlock in 2.4.22 and 2.4.23-pre7"
>>
>And once again it proves to be worth it to follow your link.
>That's not an ext3 deadlock. It's a quota deadlock.
It's also for a kernel version from 5 years ago.
Gregory Shearman
linux 2.4.x?
2003?
You got anything newer for ext3?
--
Regards,
Gregory.
Gentoo Linux - Penguin Power
Erik Funkenbusch
Yes, Mart disingeuously snipped it out in his reply.
But it doesn't matter, because He's AZ Nomad is complaining about a flaw in
Vista from almost 3 years ago that's already been fixed almost 2 years ago.
So what's the difference?
Erik Funkenbusch
Not the EXT4 one i provided a link to, but Mart snipped.
AZ Nomad
>linux 2.4.x?
>2003?
Erik has always been that pathetic when looking for new assinine
idiotic ways to bitch about linux.
Chris Ahlstrom
this bit o' wisdom:
About four years and a couple kernels.
--
Q: What does a WASP Mom make for dinner?
A: A crisp salad, a hearty soup, a lovely entree, followed by
a delicious dessert.
Chris Ahlstrom
this bit o' wisdom:
> On Wed, 01 Jul 2009 16:37:41 -0500, AZ Nomad wrote:
Very old kernel or very new filesystem, take yer pick.
--
Your fly might be open (but don't check it just now).
AZ Nomad
>After takin' a swig o' grog, Erik Funkenbusch belched out
> this bit o' wisdom:
>> On 1 Jul 2009 21:52:48 GMT, Gregory Shearman wrote:
>>
>>> linux 2.4.x?
>>> 2003?
>>>
>>> You got anything newer for ext3?
>>
>> Yes, Mart disingeuously snipped it out in his reply.
>>
>> But it doesn't matter, because He's AZ Nomad is complaining about a flaw in
>> Vista from almost 3 years ago that's already been fixed almost 2 years ago.
>> So what's the difference?
>About four years and a couple kernels.
And a black screen of death versus a linux system that can be repaired.
Tim Smith
> >
> > https://listman.redhat.com/archives/ext3-users/2003-November/msg00024.html
> >
> > "EXT3 deadlock in 2.4.22 and 2.4.23-pre7"
> >
> And once again it proves to be worth it to follow your link.
>
> That's not an ext3 deadlock. It's a quota deadlock.
Why did you Schestowitz his link to an ext4 deadlock?
--
--Tim Smith
Tim Smith
AZ Nomad <azno...@PremoveOBthisOX.COM> wrote:
>
> >linux 2.4.x?
>
> >2003?
>
> >You got anything newer for ext3?
>
> Erik has always been that pathetic when looking for new assinine
> idiotic ways to bitch about linux.
Perhaps you didn't read the thread carefully. The original poster
complained of a fixed bug in Windows involving a file system deadlock,
and said the existence of such a bug is a reason he doesn't use Windows.
If the original poster was going to be rational, then he would also have
to eliminate Linux, for having fixed deadlock bugs.
If Erik is being pathetic here, than so was the original poster.
--
--Tim Smith
Gregory Shearman
What's the difference? Errr... about 3 years. The quote you used was
from 2003, and on 2.4.x.
Sinister Midget III
But you don't understand. Every fault, bug, lapse of quality and crummy
method of doing anything has stood still for over a decade on Windross.
So that means it had to stop advancing everywhere else, too.
Because Microslop is the Great INNOVA~1®.
--
Never mind the facts - I know what I know.
---------------------------------------------------------------
Eee PC900 16G SSD 2G RAM Ubuntu 9.04
Hans Lister
Because he is dishonest, just like Roy Schestowitz.
DFS
> This is another constant reminder why I don't use microsoft products.
...except to make a living my entire life 'cause I'm a lowlife shameless
hypocrite who couldn't care less about Linux, open source, and "software
freedom".
DFS
> But you don't understand. Every fault, bug, lapse of quality and
> crummy method of doing anything has stood still for over a decade on
> Windross.
More lying idiocy from a Windows-using "advocate". You guys are as
worthless as the tinkertoy slopware you pretend to care about at night.
Erik Funkenbusch
How is that relevant? AZ Nomad complained that the mere ability for a
deadlock bug to appear in a filesystem is grounds to not use the OS.
And I posted a much newer deadlock bug, which was snipped, which you keep
ignoring. Twice now, even after I told you. So what's your point?
Erik Funkenbusch
Just because you're ignorant of the many ways you can repair such a system
in Windows doesn't mean it can't be repaired. You guys love to blame
people for their ignorance, except of course when it's your own.
Erik Funkenbusch
I also provided a quote from earlier this year. Here it is again. Let's
see if Mart snips this again.
Mart van de Wege
Why should I? If the first link once again proves Erik's penchant for
lying, why do you expect me to check the rest?
Mart van de Wege
Erm.
In case you hadn't noticed, ext4 is bleeding edge. It *will* have bugs,
because it hasn't been tested on a wide range of real-world systems yet.
And you complain because I snip out the obviously irrelevant and
concentrate on your obvious lies?
That's really rich.
Mart van de Wege
Erik's articles don't alll appear in my feed, so piggybacking:
Yes, a quota bug is not the same as a filesystem bug. Quotas are an
optional system, that must be explicitly turned on.
But trust a piece of shit liar like Erik to try and weasel his way out
from yet another of his lies.
Erik Funkenbusch
> Gregory Shearman <ZekeG...@netscape.net> writes:
>
>> On 2009-07-01, Erik Funkenbusch <er...@despam-funkenbusch.com> wrote:
>>> On Wed, 01 Jul 2009 22:14:41 +0200, Mart van de Wege wrote:
>>>
>>>> Erik Funkenbusch <er...@despam-funkenbusch.com> writes:
>>>>
>>>>> On Wed, 01 Jul 2009 11:10:04 -0500, AZ Nomad wrote:
>>>>>
>>>>>> This is another constant reminder why I don't use microsoft
>>>>>> products. What a steaming piece of shit. A file system that can
>>>>>> get into a such a deadlock is beyond belief. A file system in such
>>>>>> a state that can't be repaired is even more incredible.
>>>>>
>>>>> Well, then you must not like Linux then.
>>>>>
>>>>> https://listman.redhat.com/archives/ext3-users/2003-November/msg00024.html
>>>>>
>>>>> "EXT3 deadlock in 2.4.22 and 2.4.23-pre7"
>>>>>
>>>> And once again it proves to be worth it to follow your link.
>>>>
>>>> That's not an ext3 deadlock. It's a quota deadlock.
>>>
>>> In the quota support of ext3.. jesus, how can you not read?
>>
>> linux 2.4.x?
>>
>> 2003?
>>
>> You got anything newer for ext3?
>
> Erik's articles don't alll appear in my feed, so piggybacking:
>
> Yes, a quota bug is not the same as a filesystem bug. Quotas are an
> optional system, that must be explicitly turned on.
But still is part of the filesystem. In fact, the relevant patches include
specific filesystem code.
Note the diff command for code in ext3:
diff -ruX ../kerndiffexclude linux-2.4.22-fixstat/fs/ext3/super.c linux-2.4.22-deadlock/fs/ext3/super.c
Specifically, the code needed to be changed in ext3.. and not ext2 or
reiser, or any other fs. So don't pretend that this is code that's
irrelevant to ext3.
> But trust a piece of shit liar like Erik to try and weasel his way out
> from yet another of his lies.
Such a mouth on you. Why don't you try to explain how it's not ext3's
fault (even though changes had to be made to ext3's code and it didn't
affect any other filesystem) instead of cursing like a sailor?
Gregory Shearman
Oh, I get it.... You are *parodying* Linux Advocates...
Oh, how *clever*...
Gregory Shearman
> On 2 Jul 2009 00:56:06 GMT, Gregory Shearman wrote:
>
>> On 2009-07-01, Erik Funkenbusch <er...@despam-funkenbusch.com> wrote:
>>> On 1 Jul 2009 21:52:48 GMT, Gregory Shearman wrote:
>>>
>>>> On 2009-07-01, Erik Funkenbusch <er...@despam-funkenbusch.com> wrote:
>>>>> On Wed, 01 Jul 2009 22:14:41 +0200, Mart van de Wege wrote:
>>>>>
>>>>>> Erik Funkenbusch <er...@despam-funkenbusch.com> writes:
>>>>>>
>>>>>>> On Wed, 01 Jul 2009 11:10:04 -0500, AZ Nomad wrote:
>>>>>>>
>>>>>>>> This is another constant reminder why I don't use microsoft
>>>>>>>> products. What a steaming piece of shit. A file system that can
>>>>>>>> get into a such a deadlock is beyond belief. A file system in such
>>>>>>>> a state that can't be repaired is even more incredible.
>>>>>>>
>>>>>>> Well, then you must not like Linux then.
>>>>>>>
>>>>>>>
>>>>>> And once again it proves to be worth it to follow your link.
>>>>>>
>>>>>> That's not an ext3 deadlock. It's a quota deadlock.
>>>>>
>>>>> In the quota support of ext3.. jesus, how can you not read?
>>>>
>>>> linux 2.4.x?
>>>>
>>>> 2003?
>>>>
>>>> You got anything newer for ext3?
>>>
>>> Yes, Mart disingeuously snipped it out in his reply.
>>>
>>> But it doesn't matter, because He's AZ Nomad is complaining about a flaw in
>>> Vista from almost 3 years ago that's already been fixed almost 2 years ago.
>>> So what's the difference?
>>
>> What's the difference? Errr... about 3 years. The quote you used was
>> from 2003, and on 2.4.x.
>
> How is that relevant? AZ Nomad complained that the mere ability for a
> deadlock bug to appear in a filesystem is grounds to not use the OS.
>
> And I posted a much newer deadlock bug, which was snipped, which you keep
> ignoring. Twice now, even after I told you. So what's your point?
No, you posted a link to a brand new "bleeding edge" filesystem bug...
surprise, surprise... nothing at all to do with ext3.
But of course I'm not really surprised. You pull these dishonest stunts
all the time.
Mart van de Wege
Yes, the quota code has to interact with the filesystem code. Got any
more obvious statements to make? Like 'the earth is round'? Or 'I am a
fucking lying weasel'?
Chris Ahlstrom
this bit o' wisdom:
> In article <slrnh4nr5a.2...@ip70-176-155-130.ph.ph.cox.net>,
So, if the original poster was pathetic, and Erik used that as a jump-off
...?
--
You're at the end of the road again.
Ezekiel
"Mart van de Wege" <mvd...@mail.com> wrote in message
news:86y6r7j...@gareth.avalon.lan...
If there was ever any doubt that the Linux "advocates" in COLA are lying
immoral scumbags then this ought to remove it.
These Linux advocates are the biggest bunch of word-twisting lying weasels
on the planet. Their entire argument boils down to this:
'There was once a filesystem locking bug on Windows. I refuse to run any OS
that has such bugs.'
Two such bugs are then shown in ext3 and ext4.
The freetards then argue 'But that's different. It doesn't count. We have
excuses for our bugs.'
What a bunch of lying scum... every last one of them because not a single
"advocate" has the balls or honesty to admit that Sleazy Gonad shot off his
mouth in ignorance and Linux also has filesystems bugs. But no... each and
every "advocate" must lie, twist-words and argue minutia/semantics rather
than admit that Linux also has filesystem bugs - WHICH IT DOES!!!!!
DFS
> What a bunch of lying scum... every last one of them because not a
> single "advocate" has the balls or honesty to admit that Sleazy Gonad
> shot off his mouth in ignorance and Linux also has filesystems bugs.
> But no... each and every "advocate" must lie, twist-words and argue
> minutia/semantics rather than admit that Linux also has filesystem
> bugs - WHICH IT DOES!!!!!
Linux "advocates" are the dregs of IT.
AZ Nomad
Do you have any idea how moronic you sound when you trot out the
four year old's argument "noimnotyouare" even if you are doing it
on somebody else's behalf?
DFS
Take your beatdown like a man, Nonads.
Hans Lister
AZNomad i sure slinked away when he was asked for proof of his
"millions of tmp files he couldn't figure out how to delete"
under Vista.
Some people should not be allowed near computers.
AZNomad seems to be one of them.
Hans Lister
Ahhh, the old Linux excuse of "it's bleeding edge" or one of
it's variants "it's beta" or "it's free, what do you expect"
etc.
The Linux community has hundreds of such excuses to account for
Linux's failures.
They call them Linux "distributions".
Hans Lister
Yea...
One of my good friends is a director of IT at a Fortune 1000
company.
His staff refers to the Linux geeks as "The Freak Squad".
Hans Lister
Get ready for a thread slink.
DFS
Show him the Stallman foot-skin-eating-fest video.
Erik Funkenbusch
You seem to have a mistaken understanding of what my post was about.
I was not using it as a "jump-off" to say Linux sucks. Far from it.
I was simply pointing out how AZ Nomad was mistaken in his original post by
pointing out that Linux also has had similar bugs, so his excuse as to why
Windows sucks is flawed, because otherwise he's also claiming Linux sucks.
Erik Funkenbusch
>>If Erik is being pathetic here, than so was the original poster.
>
> Do you have any idea how moronic you sound when you trot out the
> four year old's argument "noimnotyouare" even if you are doing it
> on somebody else's behalf?
Do you have any idea how moronic you sound when you make pathetic excuses
as to why your original argument against Windows doesn't apply to Linux,
despite similar problems having affected Linux?
I know you're upset at having your argument turned against you (and you can
always tell, because you guys get so pissed off and start flinging all
kinds of insults when you're caught).. but grow up. You lost the argument.
Erik Funkenbusch
If it was a problem specifically with the quota system, and not the
filesystem, then why is it that ext3 had to be modified? And why is it
that it was the only filesystem that needed to be modified?
The only rational explanation is that it was a bug in both systems, thus
both had to be modified.
Please, don't pretend that it's not a bug in the filesystem when the
filesystem had to be modified.
Hans Lister
I just emailed him the link.
The IT department is full of college interns on summer break,
some of whom are Linux oddballs. I'm sure I'll hear all the gory
details at his party on Saturday.
He had a kid last year who forgot to go home at 5:00PM.
The cleaning crew found him asleep hunched over the keyboard at
2:00AM or so.
They thought he was dead.
He told his boss that he was banging out "crunchy code", got so
involved that he forgot to go home.
He was a Linux oddball of course.
Chris Ahlstrom
this bit o' wisdom:
Nice explanation. All is forgiven.
--
It were not best that we should all think alike; it is difference of opinion
that makes horse-races.
-- Mark Twain, "Pudd'nhead Wilson's Calendar"
Hans Lister
Schestowitz goes away on holiday and Chris returns to the old
Chris we all "knew and loved"....
Interesting....
AZ Nomad
Not really. Linux can be repaired if the file system is readable.
Windows, even though the file system is readable, is damaged beyond repair
in the situation described (black screen of death).
Only booting with a live linux CD will recover such a windows system.
Hans Lister
What's wrong with this picture.....
Argh.....
Erik Funkenbusch
>>> I was simply pointing out how AZ Nomad was mistaken in his original post by
>>> pointing out that Linux also has had similar bugs, so his excuse as to why
>>> Windows sucks is flawed, because otherwise he's also claiming Linux sucks.
>
>>Nice explanation. All is forgiven.
>
> Not really. Linux can be repaired if the file system is readable.
> Windows, even though the file system is readable, is damaged beyond repair
> in the situation described (black screen of death).
>
> Only booting with a live linux CD will recover such a windows system.
Even if that were true (and it's not), it doesn't change the fact that your
argument was flawed. Here, let me quote what you said again.
---------------
This is another constant reminder why I don't use microsoft products. What
a steaming piece of shit. A file system that can get into a such a
deadlock is beyond belief.
---------------
You are clearly claiming a filesystem which can have deadlocks is a
steaming piece of shit. Yet I pointed out two cases (and there are more)
of Linux filesystems having deadlock bugs in the past.
Yes, you did say this:
"A file system in such a state that can't be repaired is even more
incredible."
But that's not true, despite what you seem to think.
Mart van de Wege
No such bug has been shown in ext3. Such a bug has been shown in running
quotas on ext3. This *is* a different thing.
I know you stupid guys like to feel superior to people who are more
intelligent than a brick, but shouting is not going to make a lie more
true.
So fuck off, moron.
Mart van de Wege
> On Thu, 2 Jul 2009 11:39:32 -0400, DFS wrote:
>
>> Hans Lister wrote:
>>> On Thu, 2 Jul 2009 08:19:12 -0400, DFS wrote:
>>>
>>>> Ezekiel wrote:
Oh look.
The doggies are humping each other again. Someone get a bucket!
Mart van de Wege
Here's a hint: if your posts are showing you know as much about filesystem
design as you know about iptables, it's a good idea to slink away like
you usually do.
Now fuck off.
chrisv
>Hans Lister <stym...@yahoo.com> writes:
>
>> On Thu, 2 Jul 2009 11:39:32 -0400, DFS wrote:
>>
>>> Hans Lister wrote:
>>>> On Thu, 2 Jul 2009 08:19:12 -0400, DFS wrote:
>>>>
>>>>> Ezekiel wrote:
>
>Oh look.
>
>The doggies are humping each other again. Someone get a bucket!
Hehe.
AZ Nomad
>So fuck off, moron.
Not only that, but the bug was at the alpha testing level.
If he considers it to be equivelent to the vista black screen of death,
then he is admitting that vista is an alpha release.
We all know that. It is good to hear that the trolls admit that
vista is alpha quality.
Chris Ahlstrom
this bit o' wisdom:
> "Ezekiel" <ze...@some-where.com> writes:
>
>> If there was ever any doubt that the Linux "advocates" in COLA are lying
>> immoral scumbags then this ought to remove it.
>>
>> These Linux advocates are the biggest bunch of word-twisting lying weasels
>> on the planet.
DFS, meet your long-lost twin, Zeke.
--
Q: How many Californians does it take to screw in a light bulb?
A: Five. One to screw in the light bulb and four to share the
experience. (Actually, Californians don't screw in
light bulbs, they screw in hot tubs.)
Q: How many Oregonians does it take to screw in a light bulb?
A: Three. One to screw in the light bulb and two to fend off all
those Californians trying to share the experience.
AZ Nomad
>After takin' a swig o' grog, Mart van de Wege belched out
> this bit o' wisdom:
>> "Ezekiel" <ze...@some-where.com> writes:
>>
>>> If there was ever any doubt that the Linux "advocates" in COLA are lying
>>> immoral scumbags then this ought to remove it.
>>>
>>> These Linux advocates are the biggest bunch of word-twisting lying weasels
>>> on the planet.
>DFS, meet your long-lost twin, Zeke.
scarey thought. that somebody is breeding these trolls
Ardvark Sucubus Hunter
And the cow jumped over the moon too, idiot.
Ardvark Sucubus Hunter
>
> We all know that. It is good to hear that the trolls admit that
> vista is alpha quality.
The only alpha quality is you, you broken down bum that shouldn't be let
near an abacus, let alone a computer.
Ardvark Sucubus Hunter
Nomad the clown, pull your lips off of Ahlstrom's behind.
Hans Lister
You are stuck in a holding pattern Mart...
You put your foot in your mouth.
Then you tell everyone how superior your technical skills are.
And then when you get rope-a-doped, like you have been in this
thread, you tell people to fsck off.
If the fire is too hot for you Mart, get out of the frying pan
because quite frankly you are overdone and starting to stink up
the place.
Mart van de Wege
<snip>
> You are stuck in a holding pattern Mart...
>
> You put your foot in your mouth.
> Then you tell everyone how superior your technical skills are.
> And then when you get rope-a-doped, like you have been in this
> thread, you tell people to fsck off.
Again, repeating lies doesn't make them magically come true.
So fuck off, flatfish.
AZ Nomad
>AZ Nomad wrote:
>> On Wed, 01 Jul 2009 17:01:58 -0700, Tim Smith
>> <reply_i...@mouse-potato.com> wrote:
>>> AZ Nomad <azno...@PremoveOBthisOX.COM> wrote:
>>>>
>>>>
>>>>> 2003?
>>>>
>>>>> You got anything newer for ext3?
>>>>
>>>> idiotic ways to bitch about linux.
>>
>>> Perhaps you didn't read the thread carefully. The original poster
>>> complained of a fixed bug in Windows involving a file system
>>> deadlock, and said the existence of such a bug is a reason he
>>> doesn't use Windows.
>>
>>> If the original poster was going to be rational, then he would also
>>> have to eliminate Linux, for having fixed deadlock bugs.
>>
>>> If Erik is being pathetic here, than so was the original poster.
>>
>> four year old's argument "noimnotyouare" even if you are doing it
>> on somebody else's behalf?
>Take your beatdown like a man, Nonads.
You clearly have no idea how moronic you come across.
You might impress your four year buddies, but you don't impress anybody
here.
AZ Nomad
Get a room.
Hans Lister
Would you like a water view?
Gregory Shearman
> On Thu, 2 Jul 2009 13:45:30 -0400, Chris Ahlstrom wrote:
>>After takin' a swig o' grog, Mart van de Wege belched out this bit o'
>>wisdom:
>
>>> "Ezekiel" <ze...@some-where.com> writes:
>>>
>>>> If there was ever any doubt that the Linux "advocates" in COLA are
>>>> lying immoral scumbags then this ought to remove it.
>>>>
>>>> These Linux advocates are the biggest bunch of word-twisting lying
>>>> weasels on the planet.
>
>>DFS, meet your long-lost twin, Zeke.
>
> scarey thought. that somebody is breeding these trolls
They're not bred. They are extruded.
--
Regards,
Gregory.
Gentoo Linux - Penguin Power
AZ Nomad
you only make it clear to everyone that you're a repressed homosexual
homophobe when you post your fantasies.
Chris Ahlstrom
this bit o' wisdom:
> On 2009-07-02, AZ Nomad <azno...@PremoveOBthisOX.COM> wrote:
>> On Thu, 2 Jul 2009 13:45:30 -0400, Chris Ahlstrom wrote:
>>>After takin' a swig o' grog, Mart van de Wege belched out this bit o'
>>>wisdom:
>>
>>>> "Ezekiel" <ze...@some-where.com> writes:
>>>>
>>>>> If there was ever any doubt that the Linux "advocates" in COLA are
>>>>> lying immoral scumbags then this ought to remove it.
>>>>>
>>>>> These Linux advocates are the biggest bunch of word-twisting lying
>>>>> weasels on the planet.
>>
>>>DFS, meet your long-lost twin, Zeke.
>>
>> scarey thought. that somebody is breeding these trolls
>
> They're not bred. They are extruded.
http://www.ratemyeverything.net/image/8389/0/I_am_Pooping.ashx
Odd extension, must be a Microsoft /thang/.
$ file I_am_Pooping.ashx
I_am_Pooping.ashx: JPEG image data, JFIF standard 1.01
$ strings I_am_Pooping.ashx
Paint.NET v3.07
CREATOR: gd-jpeg v1.0 (using IJG JPEG v62), quality = 100
Embrace. Extend. Extrude.
--
Caution: Keep out of reach of children.
Erik Funkenbusch
>> If it was a problem specifically with the quota system, and not the
>> filesystem, then why is it that ext3 had to be modified?
>
> Here's a hint: if your posts are showing you know as much about filesystem
> design as you know about iptables, it's a good idea to slink away like
> you usually do.
I note you avoided answering the question, because you know the answer
makes you look foolish.
I didn't ask the question because I wanted to know. I already know. I'm
asking it to make you admit you are wrong, which of course you won't do.
> Now fuck off.
The seminal answer of the loser. Can't answer the question, so you can
only cuss.
Hans Lister
You shouldn't have mentioned the word seminal....
Now HPT and Marti are going to crawl out from under their rocks.
Erik Funkenbusch
>>No such bug has been shown in ext3. Such a bug has been shown in running
>>quotas on ext3. This *is* a different thing.
It was in ext3. I showed you the diffs. You want to bury your head in the
sand, fine.
> Not only that, but the bug was at the alpha testing level.
No, it wasn't. It was in both the stable and the alpha testing level.
Let me repeat the title:
"EXT3 deadlock in 2.4.22 and 2.4.23-pre7"
What part of 2.4.22 do you think is "alpha testing level"?
Just keep on making excuses.
Mart van de Wege
> On Thu, 02 Jul 2009 19:26:33 +0200, Mart van de Wege wrote:
>
>>> If it was a problem specifically with the quota system, and not the
>>> filesystem, then why is it that ext3 had to be modified?
>>
>> Here's a hint: if your posts are showing you know as much about filesystem
>> design as you know about iptables, it's a good idea to slink away like
>> you usually do.
>
> I note you avoided answering the question, because you know the answer
> makes you look foolish.
No, I answered the question. It is not my fault you can't distinguish
between core filesystem features and optional subsystems.
Just like it isn't my fault you don't understand iptables.
Mart van de Wege
> On Thu, 02 Jul 2009 12:36:22 -0500, AZ Nomad wrote:
>
>>>No such bug has been shown in ext3. Such a bug has been shown in running
>>>quotas on ext3. This *is* a different thing.
>
> It was in ext3. I showed you the diffs. You want to bury your head in the
> sand, fine.
Yes, and as usual, you didn't read. The quoted e-mail specifically
mentioned that this was an ext3/quota interaction bug. Not an ext3 bug.
Do you have to work at being this stupid?
Erik Funkenbusch
> Erik Funkenbusch <er...@despam-funkenbusch.com> writes:
>
>> On Thu, 02 Jul 2009 12:36:22 -0500, AZ Nomad wrote:
>>
>>>>No such bug has been shown in ext3. Such a bug has been shown in running
>>>>quotas on ext3. This *is* a different thing.
>>
>> It was in ext3. I showed you the diffs. You want to bury your head in the
>> sand, fine.
>
> Yes, and as usual, you didn't read. The quoted e-mail specifically
> mentioned that this was an ext3/quota interaction bug. Not an ext3 bug.
What part of ext3/quota interaction bug doesn't involve ext3?
If it involves ext3, and it's a bug, and ext3 has to be modified to fix it,
it's a fault in ext3. Period.
All of the above are true.
> Do you have to work at being this stupid?
Apparently a lot harder than you do.
Mart van de Wege
> On Sat, 04 Jul 2009 00:32:05 +0200, Mart van de Wege wrote:
>
>> Erik Funkenbusch <er...@despam-funkenbusch.com> writes:
>>
>>> On Thu, 02 Jul 2009 12:36:22 -0500, AZ Nomad wrote:
>>>
>>>>>No such bug has been shown in ext3. Such a bug has been shown in running
>>>>>quotas on ext3. This *is* a different thing.
>>>
>>> It was in ext3. I showed you the diffs. You want to bury your head in the
>>> sand, fine.
>>
>> Yes, and as usual, you didn't read. The quoted e-mail specifically
>> mentioned that this was an ext3/quota interaction bug. Not an ext3 bug.
>
> What part of ext3/quota interaction bug doesn't involve ext3?
>
> If it involves ext3, and it's a bug, and ext3 has to be modified to fix it,
> it's a fault in ext3. Period.
>
No.
But then again, from someone who apparently doesn't know that flushing
an iptables chain closes all open connections, I won't expect any
filesystem knowledge.
You can try to weasel as much as you want, but this post is on a par
with your 'dozens of root exploits'.
Sinister Midget III
> On 1 Jul 2009 21:52:48 GMT, Gregory Shearman wrote:
>
>> On 2009-07-01, Erik Funkenbusch <er...@despam-funkenbusch.com> wrote:
>>> On Wed, 01 Jul 2009 22:14:41 +0200, Mart van de Wege wrote:
>>>
>>>> Erik Funkenbusch <er...@despam-funkenbusch.com> writes:
>>>>
>>>>>
>>>>>> This is another constant reminder why I don't use microsoft
>>>>>> products. What a steaming piece of shit. A file system that can
>>>>>> get into a such a deadlock is beyond belief. A file system in such
>>>>>> a state that can't be repaired is even more incredible.
>>>>>
>>>>> Well, then you must not like Linux then.
>>>>>
>>>>> https://listman.redhat.com/archives/ext3-users/2003-November/msg00024.html
>>>>>
>>>>>
>>>>
>>>> That's not an ext3 deadlock. It's a quota deadlock.
>>>
>>> In the quota support of ext3.. jesus, how can you not read?
>>
>>
>> 2003?
>>
>> You got anything newer for ext3?
>
It was ext4, not ext3. Your link:
http://osdir.com/ml/linux-ext4/2009-03/msg00065.html
Got anything newer for ext3 than 2003 and kernel 2.4.X? Or do you
intend to pretend they're the same thing?
--
----------------------------------------------------------------
I have enough trouble single-tasking!
----------------------------------------------------------------
Eee PC900 16G SSD 2G RAM Ubuntu 9.04
----------------------------------------------------------------
Sinister Midget III
> After takin' a swig o' grog, Erik Funkenbusch belched out
> this bit o' wisdom:
>
>> On Thu, 2 Jul 2009 07:39:55 -0400, Chris Ahlstrom wrote:
>>
>>> After takin' a swig o' grog, Tim Smith belched out
>>> this bit o' wisdom:
>>>
>>>> AZ Nomad <azno...@PremoveOBthisOX.COM> wrote:
>>>>>
>>>>>
>>>>> >2003?
>>>>>
>>>>> >You got anything newer for ext3?
>>>>>
>>>>> idiotic ways to bitch about linux.
>>>>
>>>> Perhaps you didn't read the thread carefully. The original poster
>>>> complained of a fixed bug in Windows involving a file system deadlock,
>>>> and said the existence of such a bug is a reason he doesn't use Windows.
>>>>
>>>> If the original poster was going to be rational, then he would also have
>>>> to eliminate Linux, for having fixed deadlock bugs.
>>>>
>>>> If Erik is being pathetic here, than so was the original poster.
>>>
>>> ...?
>>
>> You seem to have a mistaken understanding of what my post was about.
>>
>> I was not using it as a "jump-off" to say Linux sucks. Far from it.
>>
>> I was simply pointing out how AZ Nomad was mistaken in his original post by
>> pointing out that Linux also has had similar bugs, so his excuse as to why
>> Windows sucks is flawed, because otherwise he's also claiming Linux sucks.
>
> Nice explanation. All is forgiven.
Excpt that's not what the OP said. Read it:
<slrnh4n2is....@ip70-176-155-130.ph.ph.cox.net>
--
----------------------------------------------------------------
Oxymoron: Too Many Taglines.
----------------------------------------------------------------
Eee PC900 16G SSD 2G RAM Linux Mint 7
----------------------------------------------------------------
Sinister Midget III
> On 2 Jul 2009 00:56:06 GMT, Gregory Shearman wrote:
> How is that relevant? AZ Nomad complained that the mere ability for a
> deadlock bug to appear in a filesystem is grounds to not use the OS.
Here's the message ID:
<slrnh4n2is....@ip70-176-155-130.ph.ph.cox.net>
Please show where he made that statement. What he stated, and this is a
direct quote:
Nothing works and microsoft says the filesystem is in a deadlock and
the only solution is to blow away the entire volume. They say they
fixed it in fixpack 1 but don't offer any solution.
What he was bitching about was there being no solid fix for it ("fixes
ranged from editing the registry to fix a RPC setting to renaming a
logfile directory in case of logfile corruption") and the monopoly
didn't have (or offer) a clue about what to do with it except wipe it
and start over.
You simply took the word "deadlock" and used it as a diversion away
from the half-assed product the monopoly pushes on people like drugs on
future addicts.
So, where is a newer deadlock dealing with ext3 (not ext4, as you
already tried to pass off as related)? And while you're at it, try a
different subject diversion because you got caught. Again.
--
----------------------------------------------------------------
I have enough trouble single-tasking!
----------------------------------------------------------------
Eee PC900 16G SSD 2G RAM Ubuntu 9.04
----------------------------------------------------------------
AZ Nomad
><slrnh4n2is....@ip70-176-155-130.ph.ph.cox.net>
You don't understand. Erik pointed out a linux bug associated with
alpha code. He is trying to make us understand that we shouldn't hold
vista to any higher standard. We need to understand that vista is also alpha
quality code. Of couse, we already knew vista is crap.
Sinister Midget III
> On Sat, 4 Jul 2009 18:36:20 -0500, Sinister Midget III <a...@myeeemobile.com> wrote:
>>On 2009-07-02, Chris Ahlstrom <ahls...@launchmodem.com> claimed:
>>> After takin' a swig o' grog, Erik Funkenbusch belched out
>>> this bit o' wisdom:
>>>> You seem to have a mistaken understanding of what my post was about.
>>>>
>>>> I was not using it as a "jump-off" to say Linux sucks. Far from it.
>>>>
>>>> I was simply pointing out how AZ Nomad was mistaken in his original post by
>>>> pointing out that Linux also has had similar bugs, so his excuse as to why
>>>> Windows sucks is flawed, because otherwise he's also claiming Linux sucks.
>>>
>>> Nice explanation. All is forgiven.
>
>>Excpt that's not what the OP said. Read it:
>
>><slrnh4n2is....@ip70-176-155-130.ph.ph.cox.net>
>
> You don't understand. Erik pointed out a linux bug associated with
> alpha code. He is trying to make us understand that we shouldn't hold
> vista to any higher standard. We need to understand that vista is also alpha
> quality code. Of couse, we already knew vista is crap.
That's the other hole in his specious claims. Vista was supposed to be
a finished product. A finished product that took the better part of a
decade to produce. But ext3 was still fairly new. It didn't become
mainstream for awhile after the only link Erkel posted about it.
And he tried to hide from that by producing a link for ext4 which still
isn't what I'd call finished, despite the fact that some distros seem
to want to push it anyway.
At least we got a preview of the new dance routine:
TIPPETY-TIPPETY-TAP-QUOTA TIPPETY-TAP-EXT3 TAP-TAP-TAP-EXT4 TIPPETY-
TIPPETY-LINUX-ALPHA-SOMETIMES-SUCKS-AS-MUCH-AS-WINDOWS-FINISHED
--
"Freedom defined is freedom denied." -The Illuminatus
----------------------------------------------------------------
Eee PC900 16G SSD 2G RAM Linux Mint 7
Friends don't let friends use Windows
William Poaster
of the trolls Sinister Midget III was heard to say:
> On 2009-07-05, AZ Nomad <azno...@PremoveOBthisOX.COM> claimed:
>> On Sat, 4 Jul 2009 18:36:20 -0500, Sinister Midget III
>> <a...@myeeemobile.com> wrote:
>>>On 2009-07-02, Chris Ahlstrom <ahls...@launchmodem.com> claimed:
>>>> After takin' a swig o' grog, Erik Funkenbusch belched out
>>>> this bit o' wisdom:
>
>>>>> You seem to have a mistaken understanding of what my post was about.
>>>>>
>>>>> I was not using it as a "jump-off" to say Linux sucks. Far from it.
>>>>>
>>>>> I was simply pointing out how AZ Nomad was mistaken in his original
>>>>> post by pointing out that Linux also has had similar bugs, so his
>>>>> excuse as to why Windows sucks is flawed, because otherwise he's
>>>>> also claiming Linux sucks.
>>>>
>>>> Nice explanation. All is forgiven.
>>
>>>Excpt that's not what the OP said. Read it:
>>
>>><slrnh4n2is....@ip70-176-155-130.ph.ph.cox.net>
>>
>> You don't understand. Erik pointed out a linux bug associated with
>> alpha code. He is trying to make us understand that we shouldn't hold
>> vista to any higher standard. We need to understand that vista is also
>> alpha quality code. Of course, we already knew vista is crap.
>
> That's the other hole in his specious claims. Vista was supposed to be a
> finished product. A finished product that took the better part of a
> decade to produce.
Um, yeah, *supposed* to be*. However it was just last year that Uncle
Fester declared it to be "Work In Progress".
http://www.crunchgear.com/2008/04/18/ballmer-calls-vista-a-work-in-
progress-during-speech/
Now, is that a euphemism for: We're going to bring out Vista 2 (i.e
Windows 7) & you suckers are have to gonna pay for *that* too!
> But ext3 was still fairly new. It didn't become
> mainstream for awhile after the only link Erkel posted about it.
>
> And he tried to hide from that by producing a link for ext4 which still
> isn't what I'd call finished, despite the fact that some distros seem to
> want to push it anyway.
Yes, but they often give you a *choice* of which fs to use; xfs,
reiserfs, ext3, etc. It's not like good 'ol windoze which slaps you with
a choice of....errr........*one* filesystem!
> At least we got a preview of the new dance routine:
>
> TIPPETY-TIPPETY-TAP-QUOTA TIPPETY-TAP-EXT3 TAP-TAP-TAP-EXT4 TIPPETY-
> TIPPETY-LINUX-ALPHA-SOMETIMES-SUCKS-AS-MUCH-AS-WINDOWS-FINISHED
Heh.
--
This message was sent from a
computer which is guaranteed
100% free of the M$ Windoze virus.
-- 64bit GNU/Linux systems --
Sinister Midget III
> On 2009-07-01, Erik Funkenbusch <er...@despam-funkenbusch.com> claimed:
>> On 1 Jul 2009 21:52:48 GMT, Gregory Shearman wrote:
>>
>> Yes, Mart disingeuously snipped it out in his reply.
>
> It was ext4, not ext3. Your link:
>
> http://osdir.com/ml/linux-ext4/2009-03/msg00065.html
>
> Got anything newer for ext3 than 2003 and kernel 2.4.X? Or do you
> intend to pretend they're the same thing?
--
Computers are not intelligent. They only think they are.
----------------------------------------------------------------
Sinister Midget III
>> After takin' a swig o' grog, Erik Funkenbusch belched out
>> this bit o' wisdom:
>>
>>> On Thu, 2 Jul 2009 07:39:55 -0400, Chris Ahlstrom wrote:
>>>> So, if the original poster was pathetic, and Erik used that as a jump-off
>>>> ...?
>>>
>>> You seem to have a mistaken understanding of what my post was about.
>>>
>>> I was not using it as a "jump-off" to say Linux sucks. Far from it.
>>>
>>> I was simply pointing out how AZ Nomad was mistaken in his original post by
>>> pointing out that Linux also has had similar bugs, so his excuse as to why
>>> Windows sucks is flawed, because otherwise he's also claiming Linux sucks.
>>
>> Nice explanation. All is forgiven.
>
> Excpt that's not what the OP said. Read it:
>
><slrnh4n2is....@ip70-176-155-130.ph.ph.cox.net>
--
Computers are not intelligent. They only think they are.
----------------------------------------------------------------
Eee PC900 16G SSD 2G RAM Linux Mint 7
Sinister Midget III
>> On 2 Jul 2009 00:56:06 GMT, Gregory Shearman wrote:
>
>> How is that relevant? AZ Nomad complained that the mere ability for a
>> deadlock bug to appear in a filesystem is grounds to not use the OS.
>
> Here's the message ID:
>
><slrnh4n2is....@ip70-176-155-130.ph.ph.cox.net>
>
> Please show where he made that statement. What he stated, and this is a
> direct quote:
>
> Nothing works and microsoft says the filesystem is in a deadlock and
> the only solution is to blow away the entire volume. They say they
> fixed it in fixpack 1 but don't offer any solution.
>
> What he was bitching about was there being no solid fix for it ("fixes
> ranged from editing the registry to fix a RPC setting to renaming a
> logfile directory in case of logfile corruption") and the monopoly
> didn't have (or offer) a clue about what to do with it except wipe it
> and start over.
>
> You simply took the word "deadlock" and used it as a diversion away
> from the half-assed product the monopoly pushes on people like drugs on
> future addicts.
>
> So, where is a newer deadlock dealing with ext3 (not ext4, as you
> already tried to pass off as related)? And while you're at it, try a
> different subject diversion because you got caught. Again.
--
Computers are not intelligent. They only think they are.
----------------------------------------------------------------