It-Jokes compilated via Twitter (#protolol)
56@mckeay The sad thing about IPv6 jokes is that almost no one understands them and no one is using them yet.
@dildog What’s up with the jokes… Give it a REST, guys…
@ChrisJohnRiley: The worst thing about #protolol is that you get the broadcast even if you really don’t give a shit!
@mdreid: The best thing about proprietary protocol jokes is REDACTED.
@maradydd: The bad thing about Turing machine jokes is you never can tell when they’re over #protolol
@UWTravis: RFC1918 jokes are inside jokes #protolol
@dakami The worst part of SSH jokes is that, even when they’re not funny, you suck it up and just pretend they were anyway. #protolol
@zhov I tried to come up with an IPv4 joke, but the good ones were all already exhausted. #protolol
@toastido: The best thing about UDP jokes is that I don’t care if you get them or not. #protolol
? The worst thing about Perl jokes is that next morning you can.t understand why they seemed so funny.
@thornmaker My favorite are DOM XSS jokes… so subtle that most people never get them #protolol
@Complex360: I don’t make SQLi jokes myself, I get them FROM USERS #protolol
@toastido The bad thing about HTML DOM jokes is that everyone has their own interpretations, so you have to tell them 9000 different ways. #protolol
@spikelynch: The problem with GIS jokes is that you really had to be there #protolol
@dasfiregod The worst part about token ring jokes is that if someone starts telling one while you are telling yours, all joking stops. #protolol
@jwgoerlich What did the one smtp server say to the other? … You had me at EHLO! #protolol
@alexdgardner The issue with IPv6 jokes is that no one is using them yet #protolol
@toastido The awesome thing about BGP jokes is that the intended audience will likely get them, one way or another. #protolol
@LnxPrgr3 The bad thing about RIP jokes is they often leave everyone near you in a stunned silence. #protolol
@thornmaker Everybody loves MitM jokes. Well, everybody except Alice and Bob that is. #protolol
@toastido The great thing about SQL transaction jokes is that once you BEGIN, you can ROLLBACK if nobody gets them. #protolol
@OhMeadhbh: the SYN flood attack #protolol: “knock knock. who’s there? knock knock. who’s there? knock knock. who’s there? …”
@yoshicool: People who tell routing jokes always exceed their time-to-live. #protolol
@spikelynch The problem with mutex jokes is that they’re race-ist. #protolol
@toastido The sweet thing about PXE jokes: 10.10.34.2/pxelinux.0 #protolol
@xntrik The problem with Ruby jokes is they ask to not be repeated. #protolol
@yoz: order best is tell that The you thing can about jokes BitTorrent them in any. #protolol
@thealuc: #protolol the problem with RSA jokes is, they get stolen before one can tell ‘em (corrected the typo)
@thornmaker: I would tweet a joke about CSRF if you hadn’t just done so yourself #protolol
@JohnBumgarner The problem with telling a boolean joke is that everyone wants to know if it’s true or false. #protolol
@xntrik The problem with SWIFT jokes is that they can be so damn expensive if you screw them up. #protolol
@quinnweaver: The lame thing about script kid comedy is that someone else writes all their jokes for them; they just deliver the lines. #protolol
@silentlennie: The great thing about BGP jokes ? Anyone can claim they are their own, all you can do is hope your neighbours like them
@xntrik The problem with git jokes is everyone has their own version. #protolol
@bonsaiviking Every Inception joke was a TOR joke first. #protolol
@mikepuchol Who wants serial killers when you can have much faster parallel killers? With Centronics ports! #protolol
@oising: IGMP joke; please retweet. #protolol
@jacobwcarlson How do you keep a UDP client in suspense? #protolol
@thingspeak There’s more than one way to tell a Perl joke, but only one of the ways actually is understandable. #protolol
@mrhodes You won’t find an IPX joke funny unless its framed correctly #protolol
@dispensa There… There is… There is nothing… There is nothing funny about path MTU detection. #protolol
@toastido The trouble with GSM jokes is finding the right frequency in which to tell them. #protolol
@pingudownunder The problem with SPML jokes is that Google, Salesforce and Ping think they can create a simpler version #protolol
@jwgoerlich Spy vs spy. RS-232 vs MI6. Who you going to call? Baud, James Baud. #protolol
@pingudownunder The problem with TCPIP jokes is that when I tell them, all I want is an ACK but usually get FINs and RSTs #protolol
@yoshicool LPR jokes are always on the line #protolol
@oasisbob ARP jokes are often gratuitous. #protolol
@neuropunks Bad thing about BGP jokes is you never know if its a joke #protolol
@yoshicool RAID joke are always redundant #protolol
@yoshicool PPP jokes are always between two people #protolol
@yoshicool NTP jokes are always on time #protolol
@toastido ASCII jokes need no ANSI. #protolol
@yoshicool Everyone gets a broadcast joke #protolol
@eigenrick: The problem with TCP jokes is that people keep retelling them slower until you get them. #protolol
@toastido SLIP jokes are always told in order. #protolol
@yoshicool VPN jokes are virtually private #protolol
@DamienMcKenna PHP is to slapstick as Java is to black comedy. #protolol
@reconbot: WHO HAS ANY ARP JOKES? #protolol
@yoshicool TTL jokes are short lived. #protolol
@toastido CHAP jokes are difficult to tell, because you have to perform a handshake, followed by a password, before they will be accepted. #protolol
@securitygen I’d make a joke about UDP, but I don’t know if anyone’s actually listening… #protolol
@yoshicool NNTP jokes are news to me! #protolol
@switchingtoguns the worst thing about Tor jokes is that no one gets where you’re coming from #protolol
@thornmaker I tried to tell a SSL rebinding joke, but twitter just displayed the punchline… #protolol
@alexdgardner I was telling a WEP joke once, but everyone already knew it #protolol
@yoshicool HELO I.am.an.SMTP.joke. #protolol
@toastido The problem with NetBIOS jokes is “HI I AM A PRINTER!” #protolol
@rsynnott The worst thing about endianism jokes is that ……… #protolol
@yoshicool Fragmentation jokes… #protolol
@yoshicool …are always… #protolol
@yoshicool …told in parts. #protolol
@securitygen Let me speak out in the open: Telnet IS a joke! #protolol
@olix0r: The problem with PGP jokes is that you have to tell them to everyone individually #protolol
@LnxPrgr3 The bad thing about #protolol jokes is they’ve jumped the Wireshark.
@toastido The bad thing about bluetooth jokes is they can only be told to people you’ve paired up with. #protolol
@yoshicool GOPHER #protolol
@poundifdef Too many people telling #protolol jokes at a cocktail party make it hard to focus on one conversation.
@eigenrick: The problem with TCP jokes is that people keep retelling them slower until you get them. #protolol
@mramsmeets: ICMP echo request called. He wants his reply back #protolol
@TimelessP: The best thing about SCADA jokes is that everyone gets to screw in the lightbulb. #protolol
@KippiHax I was promised a three way and all I got was a TCP handshake. #protolol
@pozorvlak: The best thing about mathematical jokes is left as an exercise for the reader. #protolol
@bovil The problem with basic jokes is 10 goto punchline error line 10 punchline not found #protolol
@laen: Did you hear the one about the Jumbo frames? It takes a long time to tell it. #protolol
@thornmaker I hate Blind SQL injection jokes. The punchlines are always funny but they take too damn long to be delivered. #protolol
@bovil I want to do an APL joke, but I don’t have the character set. Besides, who needs 140 characters of code? #protolol
@mattepp The great thing about asynchronous jokes is you can forget all about timing. #daylate
@thornmaker I used to tell this really good joke about One Time Pads. No one got it the first time but everyone got it on the 2nd go around… #protolol
@thornmaker I must have heard the SDL joke told at least a hundred times now… and no one has got it right yet. #protolol
@thezub The best thing about CSS jokes is that they are misunderstood and taken incorrectly by Internet Explorer. #protolol
@thornmaker Someone told me an AppScan joke the other day but they had to restart it 9 times and they skipped over all the important parts… #protolol
@vogon: The great thing about ASLR jokes is you never know where they’re going. #protolol
@itgirljs: The best thing about script jokes is that they start with a bang. #protolol
@mramsmeets: ICMP echo request called. He wants his reply back #protolol
@thezub The best thing about Gambas jokes is that in benchmarks it’s faster to tell them vs. Python and Pearl jokes. http://is.gd/yw5gWs #protolol
@mynickisnick The best thing about Linux jokes is that new and improved versions of them keep popping up… #protolol
@mynickisnick The best thing about Windows jokes is that the number of them is proportional to the number of crashes… #protolol
@mynickisnick The best thing about Windows Phone jokes is… wait a moment, Windows Phone IS the joke! #protolol
@dfreamon The best part about WAF jokes is there are a hundred ways to tell them, and everyone is sure to get them. #protolol
@luispedrocoelho The great thing about rsync jokes is that it only tells them if you haven’t heard them before. #protolol
@ADoug The punchline to this SCADA joke has been censored by the DHS. #protolol
@andreasdotorg: The good thing about OTR jokes is that you forget the punchline afterwards. #protolol
@goodbadwolf: The problem with IPV6 jokes is that they are hard to remember #protolol
@mramsmeets: The good thing with rainbow table jokes is that you have all posible outcomes before the joke itself #protolol #notrealprotothough
@zhov: The problem with MIME type jokes is that most people don’t know how to handle them. #protolol
@jnsq The great thing about CDMA jokes is that 8 people can tell them at the same time, and the audience understands all of them. #protolol
@duckie37 I had a funny UDP joke to tell, but I lost it somewhere… #protolol
@skovatch When I worked at CompuServe we liked to tell ANPA jokes, but they quickly became yesterday’s news. #protolol
@rickasaurus: The problem with token ring jokes is you need to wait your turn to laugh #protolol
@dwf The great thing about IPP jokes is that you always end up with a paper record of the joke in question. #protolol
@spikelynch: The problem with GIS jokes is that you really had to be there #protolol
@dwf The great thing about Zeroconf jokes is that you can just walk up to strangers and tell them, no introduction necessary. #protolol
@Tomalak The worst part about HTTP jokes is that you can never remember in which state you heard the last one. #protolol
@chiussi The best thing about packet delivery jokes is that they are best effort. #protolol
@RichGibson Everyone gets snmp jokes but only some people understand them #protolol
@RichGibson DHCP jokes only work when there is only one person telling them. #protolol
@jnsq The great thing about Infiniband jokes is that people can start retelling them before you’ve finished. #protolol
@RichGibson ping and traceroute jokes are only funny in groups #protolol
@RichGibson Do you know what is funny about X25 jokes? Absolutely nothing. #protolol
@RichGibson WMS jokes let you check the joke capabilities before you hear them #protolol
@xcbsmith An IPv4 address space walks in to a bar, “A strong CIDR please. I’m exhausted.” #protolol
@RichGibson A properly implemented WMS joke lets you span today and tomorrow #protolol
@dakami: The best thing about Skype jokes is the ridiculous lengths they’ll go to, to be told at all. #protolol
@yoz: The best thing about Skype jooooookkkkess iiiii not bu agai *poink* #protolol
@jwgoerlich: I’ve been sitting here telling IPX jokes. Just realized that none of them can get onto the Internet. #protolol
@preed: Python jokes are usually funny, even though the format is always the same… /cc @spikelynch #protolol
@jnsq The great thing about SMTP jokes is thousands of people who don’t know you will retell them to whoever you want if you ask nicely. #protolol
@jnsq The great thing about WebDAV jokes is you can tell many different versions of the same joke and people will still listen. #protolol
@RichGibson OSPF jokes are nice because they are never negative. #protolol
@jnsq The great thing about IP over Avian Carrier jokes is that if your joke gets fragmented, you at least get free dinner. #protolol
@RichGibson If you aren’t careful @dakami will take your nice DNS joke and cram a whole extra punchline on the end. #protolol
@JimPurbrick: The worst thing about non-HTTP jokes is that no matter how good they are, nobody cares #protolol
@RichGibson You can hide a whole filesystem in the time between telling a TCP joke and when people get it. #protolol
@RobertWinkel The problem with #protolol jokes is that they are too self-referencial. #protolol
@RichGibson AT command modems are funny when ATHO <no carrier> #protolol
@shazow The best thing about Bitcoin jokes is that they’re always funnier the next time you tell them. #protolol
@RichGibson SUDO lets laugh at everyone’s jokes #protolol
@RichGibson Multicast jokes are great, but you have to be paying attention #protolol
@K0nsp1racy: The ___ thing about Microsoft jokes is ____ you need to patch them all ___ time for them ___ work. #protolol
@RichGibson bittorrent jokes are only funny if you get the whole thing. #protolol
@RichGibson Xanadu jokes are funny because – Wait, did you back attribute that correctly? #protolol
@voqo: The worst thing about HTML jokes is that your audience doesn’t always GET it. #protolol
@RichGibson Only the odd numbered ROT13 jokes have a chance of working #protolol
@RichGibson ISTABU jokes are mostly funny in Finland. #protolol
@hindentristan The problem with SILC jokes is VqaxMz9JY+hDkRjrYJeeDKcdknIyxVtyBo+oywA+nvJPHEBOQ1fJ36LAgEwcGchFK/HDo5InJgl/vC6vlONkgmuR1.
@RichGibson Sticks and stones may break your bones, but Gamma Ray jokes can really get under your skin. #protolol
@RichGibson wikileaks jokes are only really funny after a real news outlets tells us we can laugh. #protolol
@MorrayeM: The problem with FTP jokes is that everyone can get them. #protolol
@seccubus The problem with modbus jokes is that they don’t register with everyone. But if they do you coil up with lauchter #protolol
@SeanRuetschi The funny thing about HTTP jokes is that everyone is POSTing them at the moment. #protolol
@RichGibson gigapan jokes are best when you forget to take down the postit with your password on it. #protolol
@RichGibson tilecache jokes just build and build until you either laugh or just clear the cache. #protolol+
@RichGibson Twitter jokes are, oh, look at this pretty picture of a freaking whale. #protolol
@missmcj A TCP packet walks into a bar “I want a beer.” Bartender responds “You want a beer?” Packet responds “I want a beer.” #protolol
@sylvander IPoAC will be viable when pigs fly – which will, in turn, add to existing capacity (if the pigs are of the homing kind). #protolol
@mitchblevins: I had an Ethernet joke, but somebody else told it at the same time. So I exponentially backed off and tried again. #protolol
@splattne: Error 404. The requested punchline was not found in this tweet. #protolol
@hvcco #protolol the problem with XML jokes is that if they’re not well formed you don’t get the ending
@ADoug OSI model jokes work on so many levels. #protolol
@peerlessdeepak The best thing about #protolol jokes is that they are #protolol jokes:)
@loell I wish wed go back to a time where everybody enjoyed fingering each other. #protolol
@RichGibson All the humor in a Java joke has been encapsulated and abstracted into a base library written in c. #protolol
@RichGibson COBOL jokes perform varying humor #protolol
@ADoug You might not laugh at this #protolol about ipv4-in-ipv6 encapsulation because it’s an inside joke.
@akujobi: My HEAD hurts because I don.t GET all the HTTP jokes y.all PUT on my timeline. I have to DELETE some of them POST-haste
@securitygen: I received a Tor joke from someone. have no idea who they are though.
@RichGibson ssh -D jokes just pop up where they are not expected. #protolol
@RichGibson TOR jokes start and end almost anywhere. #protolol
@tristanwatkins These networking jokes are great, but with SharePoint people you need handle the protocol a bit differently #protolol
@RichGibson If you freeze a joke in RAM it will still be there when you take the computer apart. #protolol
@virtualblackfox The worst thing about GPIB jokes is that you must *WAI for the punchline #protolol
@RichGibson The problem with PtP jokes is that everyone has to decide how much to laugh themselves. #protolol
@RichGibson kickstarter jokes are all or nothing #protolol
@RichGibson nobody gets micropayment jokes #protolol
@behets Worst thing about PHP jokes, no matter how good or bad, everyone laughs. Almost #protolol
@manicsocratic A packet header walks into a bar, the bartender holds up a gun to the packet, statefully. #protolol
@RichGibson few people understand a Douglas Englebart joke until after the patents have run out. #protolol
@manicsocratic An RADIUS server once asked me for some lip balm because he was feeling a CHAP. #protolol
@RichGibson Considering how queer tolerant SF is people are mighty upset my MitM jokes #protolol
@RichGibson Tweet, tweet, tweet. Doesn’t anybody finger anymore? #protolol
@manicsocratic What’s a pirate’s favorite method of remote access? – ARRRRRRRRDP #protolol
@yvesvanlaer Having a good laugh with #protolol. ‘MySQL is angry with me, “did you break it?” she asks; “yes” I said, “I DROP DATABASE”‘.
@loell Mr. OAuth tries to cash out a cheuqe, it bounced! Teller said. Invalid signature. #protolol
@RichGibson Even if you don’t get a multicast joke, the bloke next to you can explain it. #protolol
@manicsocratic Ever since I converted to ReiserFS I can’t seem to find those pictures of my wife. #protolol
@tristanwatkins Someone could make a packet out of these networking jokes #protolol
@tristanwatkins .@weshackett just told me to go easy on the #protolol. I must have missed that cable
@protolol “DNS servers must feel sad, nobody calls them by their name.” http://goo.gl/Ph2lR #protolol
@iamtef: I have a #protolol joke about fermat but alas; 140 characters is not enough to tell it.
@toastido: The bad thing about XML jokes is that they take too long to tell, and sometimes are completely valueless. #protolol
@lispcat Standup comedy is like UDP: if they didn’t get it the first time, don’t bother trying again. It’s the tell-and-pray #protolol
@lensassaman: “The problem with DRM jokes is that you can’t share them with your friends.” #protolol
@pozorvlak: What’s the best thing about Prolog jokes? No. #protolol
@protolol There. There is. There is nothing. There is nothing funny about path MTU detection. http://goo.gl/paa4i #protolol
@pietercolpaert The problem with SIP-jokes is that you need to be invited first #protolol
@maleadt The problem with PGP jokes is that you need to gain everybody’s trust before they can laugh with it. #protolol
@preed: Python jokes are usually funny, even though the format is always the same…
@BatistLeman Good thing about a Serial-joke is people won’t interrupt you when telling it #protolol
@pletterpet Best #protolol joke I have heard: An IPv4 address walks into a bar and says: “Quick, give me a drink. I am exhausted!”
@letharion The problem with Drupal jokes is that there are 10000 to choose from, and only a few are funny, but you don’t know which ones #protolol
@RichGibson: The problem with PtP jokes is that everyone has to decide how much to laugh themselves. #protolol
@fpletz: The bad thing about Haskell jokes is that let understood = map (isJust . understand) $ repeat joke in or understood == False #protolol
@gveloper: I’m working on a bittorrent joke, but I only have about 30% and nobody’s seeding! #protolol
@quinnweaver: The great thing about a SIGKILL joke is, there’s no way you can’t get it (there’s no ignoring it). #protolol
@quinnweaver: Thus bad thing about SQL injection jokes is when people take them literally. #protolol
@quinnweaver: The bad thing about an embedded systems joke is, if you tell it wrong, you’re done. You’ll never get a chance to re-tell it. #protolol
@kroosec: The bad thing about IPv6 jokes is that nobody wants to tell them first. #protolol
@thecoolroomie The best part about these #protolol jokes is that you want to hear as many as you can once you get the first one. ![]()
@peter_tonoli Chuck Norris has only one OSI layer – Physical #protolol
@peter_tonoli I tried to tell a rlogin joke, but no one listens any more #protolol
@lensassaman: The good thing about Twitter jokes is they’re so short. (ht/@maradydd) #meta #protolol
@dcept905 The worst thing about #protolol jokes is the ridiculous TTL ![]()
@mikesherov #protolol TheGoodThingAboutDomainNameJokesISThatAllTheGoodShortOnesHaveBeenTold.com unless you’re being creati.ve
@AVGP Chuck Norris doesn’t do #tcp handshake – he does #tcp roundhouse-kick to initiate the connection. #protolol
@mikesherov #protolol The best thing about Linux command line jokes is that they’re easier to understand if you use a pipe.
@chucksparrow The bad thing about RTS jokes is, you must first get ready to get them told #protolol
@Nero_Impala DHCP jokes are leased #protolol
@dummybert the bad thing about KERBEROS jokes is: You can’t understand them if your clock is wrong. #protolol
@kaiengert The Problem with SSL jokes is that you must get someone else to vouch for you before you can tell the joke. #protolol
@kbh01 the problem with UDP jokes: I don’t get half of them #protolol
@Nero_Impala OSI Layer-8 jokes are infinite. #protolol
@krnlde One great thing about XSD jokes is that you’ll get a warning for every inappropriate content. #protolol
@dummybert SSH 1.33 and/or 1.5 protocol jokes are useless. #protolol
@metaphox the best GFW jokes are inaccessible from China. #protolol
@mattbing Nobody likes a Debian SSH joke. Everyone can guess the punchline. #protolol
@d3rp3t3r the good thing about bitcoin jokes is you can mine them yourself #protolol
@murphy_karasu At least Ruby jokes have class. #protolol
[Fixed] Interkommunikations-Problem bei Jira und Confluence unter Ubuntu Server 10.04
63Bei Stage 4 – Step 5 des Atlassian DragonQuest geht es darum, die Interkommunikation zwischen JIRA (Version 4.2.2 Enterprise) und Confluence (Version 3.4.6) zu konfigurieren.
Unter Ubuntu Server 10.04 i386 hatte ich das Problem, dass weder das Confluence-Gadget im JIRA-Dashboard, noch die JIRA-Graphen im Wiki-Artikel innerhalb von Confluence funktioniert haben.
Die folgende Lösung fand sich in diesem Thread des Atlassian-Forums:
Befindet man sich im “Trusted Apps”-Dialog in Confluence (Browser -> Confluence Admin -> Administration -> Trusted Apps), löscht man den vorher hinzugefügten Eintrag für JIRA wieder und legt ihn, wie in der Anleitung, mit der JIRA-URL neu an.
Nun ändert man die Adresse im Feld “Name” wieder in JIRA, lässt das Feld “IP Address Matched” allerdings leer. Zuvor fiel mir schon auf, dass er jedes mal nach dem Speichern die Zeilenumbrüche verloren und die IP-Adressen am Stück gespeichert hat.
Hat man dies befolgt, sollten sowohl die Confluence-Gadgets als auch die JIRA-Graphen in der jeweils anderen Applikation wieder funktionieren.
[Fixed] Fehler mit Bamboo 2.7.3 unter Ubuntu Server 10.04
77Während dem Atlassian DragonQuest für die Installation der kompletten Atlassian-Suite um Jira, Confluence, etc., stieß ich auf ein Problem mit Bamboo (Stage 8).
Nach der Installation von Version 2.7.3. auf Ubuntu Server 10.04 (i386) bekam ich eine Fehlermeldung, ähnlich der folgenden, als ich mich das erste mal in Bamboo einloggen wollte:
Could not instantiate bean class [com.octo.captcha.service.image.DefaultManageableImageCaptchaService]: Constructor threw exception; nested exception is java.lang.Error: Probable fatal error:No fonts found.
Die Lösung, welche sich in diesem Kommentar unter "Bamboo Standalone Installation Guide (Linux)" fand, ist die Installation der Pakete msttcorefonts, gsfonts und gsfonts-x11.
Installiert man diese einfach mittels apt-get aus dem Repository nach, sollte der Rest der Installation und Konfiguration von Bamboo ohne Probleme sein.
Was ist eigentlich… Defragmentierung?
45Geht es darum, immer schlechter werdender Performance eines Windows-PCs entgegen zu wirken, wird in der Regel als erstes die Defragmentierung vorgeschlagen. Nun kennt man als Laie diesen Begriff wahrscheinlich nicht aus dem Alltag und kann sich dementsprechend keinen Reim darauf machen, was dieser Begriff bedeutet. Um dies nachvollziehen zu können, muss man sich kurz vor Augen führen, wie der Speicherbereich einer Festplatte aufgeteilt ist und wie Daten darauf gespeichert werden. Das Dateisystem einer Festplatte ist für die bessere Adressierbarkeit (Direktes lokalisieren von Datenblöcken mittels gespeicherter Adresse) der Daten in einzelne Bereiche eingeteilt. In diese Bereiche wird die komplette Festplatte eingeteilt und deren Größe beträgt bei aktuellen Betriebssystemen meist 4 Megabyte (4096KB). Ist die Festplatte frisch formatiert (Der Inhalt der Festplatte komplett auf Dateisystem-Ebene gelöscht), werden Dateien, die man auf die Festplatte kopiert, an einem Stück in fortlaufende Blöcke geschrieben:
| Datenblock: | 1 | 2 | 3 | 4 | 5 |
| Datei: | DSC0001.jpg | Freier Speicherplatz | |||
In diesem Beispiel schreibt man die Datei DSC0001.jpg auf die Festplatte, die auf die Blöcke 1 und 2 aufgeteilt wird. Im Laufe des Betriebs eines PC schreibt man allerdings nicht nur neue Dateien, sondern löscht auch welche oder erweitert bestehende (Die dann zusätzliche Blöcke einnehmen müssen). Zur Fragmentierung kommt es, weil durch die unterschiedlichen Dateigrößen beim Löschen verschieden große Lücken zwischen belebten Blöcken besteht. Folgende Beispiele stellen diesen Ablauf dar: Weitere Dateien werden geschrieben:
| Datenblock: | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| Datei: | DSC0001.jpg | Aufnahme.mp3 | Video.avi | Frei | ||||||
Die Datei Aufnahme.mp3 wird um Daten (z.B. Angaben für Künstler, Album, usw. erweitert) erweitert und benötigt jetzt mehr Speicherplatz als 2 Datenblöcke beinhalten können (Also mehr als 2x 4096). Es ist nun also ein weiterer Datenblock nötig. Da allerdings die nachfolgenden 4 bereits von der Datei “Video.avi” belegt sind, werden die neuen Daten von “Aufnahme.mp3″ in Block 10 weitergeschrieben:
| Datenblock: | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| Datei: | DSC0001.jpg | Aufnahme.mp3 | Video.avi | Rest von Aufnahme.mp3 | ||||||
Dies ist in einem derartig kleinen Szenario noch unproblematisch, vervielfacht sich jedoch mit der Betriebsdauer und damit verbundenen Schreib, Änder- sowie Löschprozessen auf dem jeweiligen Datenträger.
Jede “Teilung” und “Verstreuung” der Einzelsegmente einer Datei, verlangsamt das Zugreifen auf diese. Betrifft dies zu viele Dateien, kann die Geschwindigkeit des ganzen Systems dadurch negativ beeinflusst werden.
Bei der Defragmentierung werden die Segmente von einzelnen Dateien so gut wie möglich wieder zusammen gebracht.
In unserem Beispiel würde dabei folgendes gemacht werden:
- Video.avi wird temporär in die Sektoren am Ende des Dateisystems verschoben
- Der Inhalt von Block 10 (Gehörend zu Datei Aufnahme.mp3) würde in Block 6 verschoben werden
- Video.avi wird wieder in den Bereich zurückverschoben – genau genommen nach Block 7-10
Dadurch wird die Ordnung wieder hergestellt und Dateien wieder zusammenhängend im Dateisystem gespeichert:
| Datenblock: | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| Datei: | DSC0001.jpg | Aufnahme.mp3 | Video.avi | |||||||
Folgende Animation veranschaulicht diese “Aufräumarbeiten” auf Block-Basis sehr gut (Quelle: Wikipedia):
Soviel zur Fragmentierung und Defragmentierung.
Vielen Dank für’s Lesen und wenn ihr Fragen, Anregungen oder Kritik habt, schickt doch einen Kommentar rein.
