• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

epic bug on github

Ha, that's some hilarious crap right there. I feel sorry for the committer.
 
687474703a2f2f692e696d6775722e636f6d2f7937486d392e6a7067


I lost it about there. 😀 That's some good stuff that hits way too close to home.
 
This is why I like Windows. Protects you from your own stupidity.

I remember I've done something similar but it wasn't entirely my fault.

Working on a website and I was told the current worksite was the development environment so I made some sweeping changes for debugging and messaging and published so I could run some analysis.

Yeah, it was the production environment so people saw all the crap I was doing to it for a good 6 hours (and I use naughty words for my debug messages).
 
KIAman said:
This is why I like Windows. Protects you from your own stupidity.

I remember I've done something similar but it wasn't entirely my fault.

Working on a website and I was told the current worksite was the development environment so I made some sweeping changes for debugging and messaging and published so I could run some analysis.

Yeah, it was the production environment so people saw all the crap I was doing to it for a good 6 hours (and I use naughty words for my debug messages).
Click to expand...

Using Windows wouldn't have helped you with something like this because you would've clicked Ok on the UAC dialog to let the installer do whatever it wanted to do. Sure, a lot of files in C:\Windows would've failed to delete because they're in use, but I'm sure enough would've succeeded to make the system fail to boot next.
 
oh my, i bet he feels like an ass.

surely a rm -rf is not the correct procedure for doing something like this.
 
It would have been fine had he quoted the path like a normal person should when releasing code. But he didn't so now the world will Lulz at his mistake.
 
KIAman said:
Dealing with Windows interdependencies and security is a lot easier than most people realize. All it takes is a little understanding of how user and group level permissions work and how to work with credentials.
Click to expand...

But it's still more convoluted than the unix side. And like I mentioned before, if a similar typo existed in a MSI pre/post install script it would've had an equally destructive effect on Windows. It would've been slightly more limited in scope because Windows is more strict with file locking, but I'd bet money you'd still have to do at least a repair from the installer CD if not a full restore/reinstall.
 
Nothinman said:
But it's still more convoluted than the unix side. And like I mentioned before, if a similar typo existed in a MSI pre/post install script it would've had an equally destructive effect on Windows. It would've been slightly more limited in scope because Windows is more strict with file locking, but I'd bet money you'd still have to do at least a repair from the installer CD if not a full restore/reinstall.
Click to expand...

Windows system files and folders and owned by "TrustedInstaller" that not even an administrator can delete.

You have to take several steps in transfering ownership and applying permissions before you could even get started.

Next, windows locks files in use so even if you went through the trouble of changing ownership and applying permissions through all child elements, you will succeed in removing non critical files.

How much money you willing to bet? LOL.
 
ObscureCaucasian said:
Wouldn't removing /usr be more analogous to removing C:/Program\ Files as opposed to C:/windows?
Click to expand...

Not really. /usr doesn't really have a good fit. For example, in windows you can delete "Program Files" and still have a gui system, a window manager, update manager etc. Deleting /usr gets rid of all of that. Whats worse, it also gets rid of the package management system. That means there is no simple way to repair things. You pretty much have to do a full system reinstall to get things back to the way they were.

On windows, deleting Program files would be quite annoying, but not the end of the world. You lose all of your software, but the system will still put along as if nothing had changed. The worst thing that would happen is all the applications set to run at startup will have windows reporting to you that "Hey, you don't have the program any more!"
 
Cogman said:
Not really. /usr doesn't really have a good fit. For example, in windows you can delete "Program Files" and still have a gui system, a window manager, update manager etc. Deleting /usr gets rid of all of that. Whats worse, it also gets rid of the package management system. That means there is no simple way to repair things. You pretty much have to do a full system reinstall to get things back to the way they were.

On windows, deleting Program files would be quite annoying, but not the end of the world. You lose all of your software, but the system will still put along as if nothing had changed. The worst thing that would happen is all the applications set to run at startup will have windows reporting to you that "Hey, you don't have the program any more!"
Click to expand...

You would lose X but you can still get to a bash shell.
 
ObscureCaucasian said:
You would lose X but you can still get to a bash shell.
Click to expand...

True, but you also lose your entire package management systems (at least, most of the common ones are installed here). That means you can't just redownload all the missing programs, not without reinstalling the package manager from an installation disk. You essentially lose your entire connection to the internet and your ability to create one. You're system becomes all but useless.

The death of Program Files, on the other hand, kills a lot (though, windows doesn't allow everything in program files to be deleted at any level). but not everything. You can still access the internet (explorer has internet capabilities), see your files. Heck, you still have the use of some simple text editors (notepad and wordpad). You have the ability to install programs still without ever having to reinsert a windows disk.

In short, your system is still usable and workable.
 
Cogman said:
True, but you also lose your entire package management systems (at least, most of the common ones are installed here). That means you can't just redownload all the missing programs, not without reinstalling the package manager from an installation disk. You essentially lose your entire connection to the internet and your ability to create one. You're system becomes all but useless.

The death of Program Files, on the other hand, kills a lot (though, windows doesn't allow everything in program files to be deleted at any level). but not everything. You can still access the internet (explorer has internet capabilities), see your files. Heck, you still have the use of some simple text editors (notepad and wordpad). You have the ability to install programs still without ever having to reinsert a windows disk.

In short, your system is still usable and workable.
Click to expand...

Now this sounds like a challenge 😉
 
Cogman said:
😀 time to fire up the 'ole virtual machine!
Click to expand...

I setup a quick chrooted environment on my Debian laptop and proceeded to blow away my /usr folder. I was playing around with making network requests with netcat, and while possible, I'll admit it's not the slightest bit practical.

However if you do throw in the installation medium then it should be a lot easier to recover once you have your package manager installed, since you package lists are stored elsewhere (/var/lib/dpkg/status for debian systems).
 
KIAman said:
Windows system files and folders and owned by "TrustedInstaller" that not even an administrator can delete.

You have to take several steps in transfering ownership and applying permissions before you could even get started.

Next, windows locks files in use so even if you went through the trouble of changing ownership and applying permissions through all child elements, you will succeed in removing non critical files.

How much money you willing to bet? LOL.
Click to expand...

I stand corrected, it fails to boot but still kicks in the automated repair stuff which seems to actually fix it. I guess having the entire installer cached on the disk has some advantages after all =)
 
Nothinman said:
I stand corrected, it fails to boot but still kicks in the automated repair stuff which seems to actually fix it. I guess having the entire installer cached on the disk has some advantages after all =)
Click to expand...

Disk is cheap!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top