CRITICAL WARNING ABOUT CERTAIN OPERATING SYSTEM

Fulk Upuntoo.

A word of warning if you're like me, own a Dell, Lenovo/IBM or HP notebook.
Do not install any version, variation or anything related to Ubuntu on it.
It WILL fulk your machine good and proper.

The as-of-yet unfixed bug# 43745343802 in Linux kernel for Ubuntu which
corrupts the real-time clock, and causes your machine to boot simply with
the message "Time-of-day clock stopped", leaving you unable to get into the
BIOS, boot from external sources, or do anything even remotely useful with
your notebook - effectively bricking it.

The fix? You can rip open your notebook and extract the CMOS battery, or
call manufacturer to see how good warranty is. The awesome thing about that
bug? It's in Dapper, as you can see.. but I just got it in Edgy, and
according to the comments, it was there back in Breezy as well.
The next cu**nt who even breathes Ubuntu in my presence will receive a punch
in the face. Jesus fluking Christ. In my entire 23 year history of fluking
with PC operating systems, not ONCE have I ever come across one capable of
bricking your hardware. I'd like to support the Ubuntu developers, because
from their mission statements and other crap, it sounds like they're trying
to do the right thing - but folk me, a bug this serious possibly spans three
releases and still isn't fixed? One that, to date, doesn't appear in other
Linux distro's? Get your fluking act together!

 

STAN STARINSKI wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Fulk Upuntoo.
>
> A word of warning if you're like me, own a Dell, Lenovo/IBM or HP
> notebook. Do not install any version, variation or anything related to
> Ubuntu on it. It WILL fulk your machine good and proper.
>
> The as-of-yet unfixed bug# 43745343802 in Linux kernel for Ubuntu which
> corrupts the real-time clock, and causes your machine to boot simply
> with the message "Time-of-day clock stopped", leaving you unable to get
> into the BIOS, boot from external sources, or do anything even remotely
> useful with your notebook - effectively bricking it.
>
> The fix? You can rip open your notebook and extract the CMOS battery, or
> call manufacturer to see how good warranty is. The awesome thing about
> that bug? It's in Dapper, as you can see.. but I just got it in Edgy,
> and according to the comments, it was there back in Breezy as well.
> The next cu**nt who even breathes Ubuntu in my presence will receive a
> punch in the face. Jesus fluking Christ. In my entire 23 year history of
> fluking with PC operating systems, not ONCE have I ever come across one
> capable of bricking your hardware. I'd like to support the Ubuntu
> developers, because from their mission statements and other crap, it
> sounds like they're trying to do the right thing - but folk me, a bug
> this serious possibly spans three releases and still isn't fixed? One
> that, to date, doesn't appear in other Linux distro's? Get your fluking
> act together!
> <!--colorc--><!--/colorc-->

Try using the latest Ubuntu instead of a three year old distro.

Alias

 

STAN STARINSKI wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> One such incident is worth 100000 soft incidents with Windows.
> In this case hardware was semi-permanently damaged.
>
> Microsoft has a long way to learn from Upuntoo how to damage BIOS
> integrated circuits.
> Bravo :LeeNux. Next time try to fry my display.<!--colorc--><!--/colorc-->

Why are you using such dated releases?

Oh, nevermind ... time is something you can't comprehend.

 

One such incident is worth 100000 soft incidents with Windows.
In this case hardware was semi-permanently damaged.

Microsoft has a long way to learn from Upuntoo how to damage BIOS integrated
circuits.
Bravo :LeeNux. Next time try to fry my display.