And the Unix filth did it. Without moving files to trash can. And there is no way to get anything back, because WORSE IS BETTER and the the shitty Unix unlinks everything even when filesystem has enough free space. Why? Why Unix cant die and be replaced with a good OS?
Name:
Anonymous2012-08-28 5:36
There is an undelete(char *path) syscall, but it wont work. Because Unix is fucking shit.
Name:
Anonymous2012-08-28 5:39
So you just did something and now you're complaining about it? You make me want to commit a hate crime.
>>3 you just did something
Nope. I didnt invented Unix.
Why there is no way to bury Unix,Linux and C/C++? The world will become so much better without them. Killing Unix is like extermination all the Jewish parasites or finding a cure for cancer - it will a major success for humanity.
Name:
Anonymous2012-08-28 5:47
>>4 You deserved it.
I doubt any user deserves a system that shoots him in the foot.
It's funny because since I first linked Xah Lee on here, some /prog/riders keep bashing UNIX and Worse is Better. But yeah, UNIX is shit and GNU and Windows are only barely less evil.
>>7
The problem with flame posts such as yours is that they don't actually try to say anything interesting but usually reflect their own ineptitude. The message that I read goes along these lines: I have a problem and I am too inept to express why this problem is worth your time. Instead I'll just be vague, you're smart enough to know what the problem is.
Name:
Anonymous2012-08-28 6:09
>>7
Well, Windows too has unlink function and it will delete immediately, because it was written by the same worse-is-better faggots, who hate users and want everyone to suffer.
if you don't want to shoot yourself in the foot, then don't kill weeds using a shot gun. Use weed spray instead. But if by chance a wolf surprises you, you may have trouble fending it off with weed spray.
>>18 type command computer does as requested WHYYYYYY, I HATE THIS!!!!! 2012
ISHYGDDT
Name:
Anonymous2012-08-28 9:42
>>16 The problem is that you rewrite `rm` with a safe version only when you already shot yourself. I.e. your foot is already lost.
I added an alias for rm into a command that moves stuff to /tmp/trash when I learnt about it and before I deleted anything important, both feet are still present.
Name:
Anonymous2012-08-28 11:12
http://m.simson.net/ugh.pdf Unix is a computer virus with a user interface.
Unix is a toy OS, created to run a game in a few KB memory. It was a gimped single-user Multics. Any real OS moves the deleted files to a temporary area or has a way to restore deleted files. Even MS-DOS has better file recovery (UNDELETE). Windows NT has good parts, from VMS, and bad parts, from Unix.
Hey guys, I stabbed myself in the hand with a knife and it actually pierced through my hand. Therefore, I'm smart and whoever invented knives are stupid.
Any real OS moves the deleted files to a temporary area or has a way to restore deleted files.
Yeah, wasting several terabytes of disk space with stuff that I wanted to delete is a sensible thing to do.
Name:
Anonymous2012-08-28 14:56
>>25
There's also a way to permanently delete (purge) files. Only a shitty file system (sync; sync; sync) uses the first available space to store files.
Name:
Anonymous2012-08-28 15:06
Can you believe that there's no real OS that saves memory from RAM that was free'd by program, rather than putting it into a trash can for me to examine before, finally, being deleted to the OS trash can to undergo final examinations and then deleted if deemed necessary?
Don't play with daddy's tools if you don't know how to use them. Stick with you Microsoft toys, kid.
Name:
Anonymous2012-08-28 16:44
>>25
Modern flash storage devices will benefit from the circular first deleted - first overwritten scheme. Because there is a limited number of times one can write on a flash.
Name:
Anonymous2012-08-28 16:47
>>30
And, BTW, keeping alive filenames for deleted files will also extend SSD's live. So basically Unix killed my files and raped my SSD with needless writes.
>>31 So basically Unix killed my files and raped my SSD with needless writes.
The other day I put gas in my car so I can drive it. Then I began driving and my car started burning the gas. Whoever invented cars was an idiot. The gas should just stay in the tank so you can drive forever.
>>33
Same thing with hard drives. The OS should never write to the hard drive, because the number of writes are limited. That's why I don't eat food, because there's only a limited number of bites I can take before the food is gone. Eating food is a waste.
Name:
Anonymous2012-08-28 16:58
>>32
Like everything in the Unix World, unlink() works in the worst possible way.
As a rule of thumb: never ever invoke `rm` directly. Especially in your home directory.
Name:
Anonymous2012-08-28 16:59
>>33
That is why U.S. lost cart market with their enormous tanks, while Japanese won.
>>35
You're an idiot. I can rm -rf ~ and I'll be in perfect shape because I have backups. In fact, my home directory is synced across my Thinkpad, my EEEPC, my Mac, my headless in the garage, and partially to my EC2 server/seedbox and my account on my school's network.
Some of us actually know how to use our tools, kid. Go back to /g/ and show everybody your OMG customized Windows desktop.
Name:
Anonymous2012-08-28 17:15
>>38
Yep! When dealing with Unix you ought to do backups. A lot of backups.
>>39
Yes, because as you observed, hard drives fail after a finite number of writes. So what's your excused for not backing up? You think that AVD malware that keeps popping up and promising to protect you is going to shelter your from the harsh reality of hardware failures just like your mommy and daddy do from the ``real world''?
>>38,40
Agreed. UNIX™ is better because it wastes more time and makes me feel like a true UNIX hackerⓇ.
.
..:
Suck it, Win$hit faggots! Im better than U!
It's ironic considering the only time I ever use Windows is to help my roommates troubleshoot their performance problems. Not to mention the constant BSoD that was preventing my landlord from checking his email for three days.
Windows sure is a timesaver !
Name:
Anonymous2012-08-28 17:46
Dear All
Today I accidentaly removed my home directory which contains no. of other directories having my work done in last 3 years.
I used the command rm -rf * .
I am really confused as to what to do.
I looked for the problem in the google got some links pertaining to my problem, but got no solution.
zsh prompts me whenever I do rm *. It's pretty annoying, but I hardly ever do rm * because then I'd be left with a useless empty directory I need to get rid of.
Name:
Anonymous2012-08-28 17:52
>>50
Exactly! "rm *" is completely useless, yet Unix still allows it, just so you can you yourself in the foot.
>>51
It's not completely useless. If you're poking around in a cache directory and decide you want to empty it, rm * is exactly what you want.
Name:
Anonymous2012-08-28 18:01
>>52 poking around in a cache directory...
Yet another design flaw! System should clean its caches itself, when it needs space. I.e. if your webserver has a big log file and storage device is out of space, webserver should wrap log around. But no, a Unix webserver will just crash, damaging the log file in most cases and leaving database inconsistent.
>>51
Yes, Unix ``allows'' me to do what I want. Terrible ! I'd much rather use an OS that tells me ``no, you are no allowed to delete these files because you're probably just a mouthbreathing faggot who doesn't know what the fuck you're doing, like >>1-san ! How about a nice game of solitaire?''
>>53 Yet another design flaw! System should clean its caches itself, when it needs space.
Says the faggot who deleted his home directory trying to clear /tmp, which is managed by the system.
>>55 http://en.wikipedia.org/wiki/Three_Laws_of_Robotics
1. A robot may not injure a human being or, through inaction, allow a human being to come to harm.
2. A robot must obey the orders given to it by human beings, except where such orders would conflict with the First Law.
3. A robot must protect its own existence as long as such protection does not conflict with the First or Second Laws.
>>53
It doesn't have to be a system cache. Programs have their own caches. It might be a program that you're working on (this is a programming board after all). If I'm working on a program and I change the schema of the cache files, I have to clear the old cache files by hand.
Name:
Anonymous2012-08-28 18:15
>>59 It might be a program that you're working on
The program shouldnt reinvent the wheel and just use system's cache API, the same way it uses unlink(), instead of writing directly to HDD, as many older programs did.
>>66
Why not write your own operating system? That way you wouldn't have to use a Unix clone, and we wouldn't have to put up with your whining about operating systems that actually do what you tell them to.
Name:
Anonymous2012-08-28 19:07
>>67
1. I wont find investors.
2. If I find investors, they will be Jewish and I dont want to deal with the Jews.
3. I dont want to spend my whole life, designing an OS. I have more fun stuff to do.
>>29,55
Typical Unixer responses. In the hands of a genius, even a toy like Unix can be useful. Most users aren't geniuses. Most Unixers aren't geniuses either (some just think they are). Unix is full of buffer overflows and gotchas because it was not designed to be used. It was designed to be played with. It's like building a car that falls apart on purpose to attract mechanics. Unix is for people who think it's better to fix other people's bugs in the OS than to work on their own projects, who think it's more fun to edit header files so they can get graphics drivers to work with their kernel than to play an actual game.
Name:
Anonymous2012-08-28 19:36
*THE* classic Unix horror story http://www.lug.wsu.edu/node/414
If these guys used VMS on their VAX instead of Unix, they wouldn't have had this problem.