What's the longest PC uptime you've ever had?


What's the longest PC uptime you've ever had?  

123 members have voted

  1. 1. Longest uptime before restarting

    • 1 Week or Less
      33
    • 1-2 Weeks
      19
    • 2-3 Weeks
      8
    • 3-4 Weeks
      9
    • Longer than 4 Weeks (Specify in reply if you like)
      54


Recommended Posts

Prolly a month at the most. I usually restart to go back to XP and vice versa.

My old P2 print server had nearly 2 years uptime. Only crashed once, and I was able to recover it by SSH'ing into it and killing a rogue process. It must've survived a fair few power cuts and physical moves too (a P2 doesn't put much strain on a UPS designed for a P4 :p).

Shame it's been made redundant by my new printer.

Edit - just powered it up again and the never-updated installation of Vector Linux still works :D

uptime == Anyone who posts an uptime of a Windows Based box.. that is showing over 30 days is basically saying My system can be exploited. Since Microsoft has been releasing Criticals every 2nd Tuesday of the month for over a year now. So don't be proud of your high uptime, cause I'm going to root your box.

Three years ago I had my old P3 667Mhz system running for 72 days straight until a power cut during a thunderstorm shut it off.

I had it running as a general file dump and a torrent and printer server. The computer was 5 years old at the time. It still runs well today and even has the original 20Gb Seagate HD.

uptime == Anyone who posts an uptime of a Windows Based box.. that is showing over 30 days is basically saying My system can be exploited. Since Microsoft has been releasing Criticals every 2nd Tuesday of the month for over a year now. So don't be proud of your high uptime, cause I'm going to root your box.
While I think it is unwise to not update (and reboot to apply, if necessary) your system, it is absurd to say you can be rooted if your uptime is over 30 days old.
  1. Not all patches involve exploits that are remote
  2. Even if the exploit is remote, it may not involve a system level compromise
  3. Even the remote/system exploits may rely on other factors, like use of the Microsoft JET engine or such.

And finally, those are only known/patched vulnerabilities. So, at any time, any system could potentially be compromised by a non-public exploit.

That totally removes significance to the "30 day" rule. ;)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft's fast coding model MAI-Code-1-Flash comes to Copilot Business and Enterprise by Karthik Mudaliar Microsoft’s recently announced MAI-Code-1-Flash model is now generally available to GitHub Copilot Business and Copilot Enterprise customers. With this support, organizations can have more centralized policy controls and billing while finally being able to use Microsoft’s lightweight, first-party coding model. According to GitHub’s announcement, Business and Enterprise plan administrators must enable the MAI-Code-1-Flash policy in Copilot settings before developers can access the model. Microsoft says that MAI-Code-1-Flash is for fast, iterative coding work rather than the most demanding architectural or debugging tasks. GitHub’s official model comparison page says that the model is great for "general-purpose coding and writing," while it excels at fast, accurate code completions and explanations Microsoft introduced MAI-Code-1-Flash on June 2 as part of a broader collection of internally developed MAI models. GitHub subsequently expanded support to Copilot CLI, the Copilot cloud agent, GitHub.com chat, GitHub Mobile, Visual Studio, JetBrains IDEs, Eclipse, and Xcode, but said support for managed Business and Enterprise customers was still on the way. In Microsoft’s own benchmark testing, MAI-Code-1-Flash scored 51.2% on SWE-Bench Pro, compared with 35.2% for Anthropic’s Claude Haiku 4.5. Microsoft also claimed that the model used up to 60% fewer tokens on SWE-Bench Verified. Do note that these are vendor-run results rather than independent measurements. The model is billed at provider list pricing under GitHub’s usage-based system. GitHub currently lists MAI-Code-1-Flash at $0.75 per million input tokens, $0.075 per million cached input tokens, and $4.50 per million output tokens. For organizations, the main incentive to use MAI-Code-1-Flash is likely to be efficiency rather than maximum capability. A smaller model that responds quickly and limits unnecessary output is quite useful for repetitive agent tasks at scale, especially after GitHub Copilot’s move toward usage-based billing. The "Flash" model is recommended for fast work and not necessarily for huge repositories with loads of context. It's better if teams compare their output with other larger models, especially if they're working on security-sensitive changes and complex, multi-file work.
    • yes AND no the "original" or plain/normal Optiplex 7010 won't be getting any more new firmware updates BUT the Optiplex SFF/SFF Plus {small form factor}, Micro/Micro Plus & Tower/Tower Plus 7010 editions DO get new updates such as this new one   and here are similar guides from the Dell web site for Dell systems: https://www.dell.com/support/kbdoc/en-us/000390990/secure-boot-transition-faq https://www.dell.com/support/kbdoc/en-us/000347876/microsoft-2011-secure-boot-certificate-expiration
    • AT&T has been spying on US citizens with the NSA for decades.. they just know how to keep it more under wraps.. the evil level is still there.
  • Recent Achievements

    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      462
    2. 2
      +Edouard
      213
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      72
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!