| Latest revision |
Your text |
| Line 8: |
Line 8: |
| | :::: It appears that explainxkcd.com is using Cloudflare, so all the wiki edits are probably logged as coming from Cloudflare's proxies. A WHOIS search confirms that the IPs 108.162.192.0 to 108.162.255.255 are part of Cloudflare's network --[[Special:Contributions/108.162.228.167|108.162.228.167]] 22:22, 9 May 2016 (UTC) | | :::: It appears that explainxkcd.com is using Cloudflare, so all the wiki edits are probably logged as coming from Cloudflare's proxies. A WHOIS search confirms that the IPs 108.162.192.0 to 108.162.255.255 are part of Cloudflare's network --[[Special:Contributions/108.162.228.167|108.162.228.167]] 22:22, 9 May 2016 (UTC) |
| | ::::: I had thought explainxkcd was anonymizing IP addresses to some carefully chosen ranges. Apparently that's just a helpful side effect. Does Cloudflare always assign the same proxy to a particular source address? [[User:.42|.42]] ([[User talk:.42|talk]]) 23:34, 9 May 2016 (UTC) | | ::::: I had thought explainxkcd was anonymizing IP addresses to some carefully chosen ranges. Apparently that's just a helpful side effect. Does Cloudflare always assign the same proxy to a particular source address? [[User:.42|.42]] ([[User talk:.42|talk]]) 23:34, 9 May 2016 (UTC) |
| − | :::::: There are collisions. Someone else has edited via the same proxy I use, so now there is another [[User:.42|.42]] ([[User talk:.42|talk]]) 21:11, 18 May 2016 (UTC)
| |
| | : Note that it says "limits" in plural, i.e. both upper and lower. --[[Special:Contributions/108.162.218.209|108.162.218.209]] 19:28, 9 May 2016 (UTC) | | : Note that it says "limits" in plural, i.e. both upper and lower. --[[Special:Contributions/108.162.218.209|108.162.218.209]] 19:28, 9 May 2016 (UTC) |
| − | :: There are several "upper limits" -- one for turn on the fan, then speedup the fan, then start making sounds to alarm the user and the final one for doing a hard-shutdown of the computer before it burn out -- so assuming that anybody want to disable the lower is a stretch [[Special:Contributions/162.158.255.219|162.158.255.219]] 04:00, 11 May 2016 (UTC)
| |
| | | | |
| | | | |
| Line 52: |
Line 50: |
| | | | |
| | I originally interpreted "clean reinstall keybinding" as meaning that his keybindings were so entirely screwed that he wanted to do a clean reinstall of the keybinding system, but the other interpretation is funnier. [[Special:Contributions/108.162.219.74|108.162.219.74]] 16:24, 9 May 2016 (UTC) | | I originally interpreted "clean reinstall keybinding" as meaning that his keybindings were so entirely screwed that he wanted to do a clean reinstall of the keybinding system, but the other interpretation is funnier. [[Special:Contributions/108.162.219.74|108.162.219.74]] 16:24, 9 May 2016 (UTC) |
| − |
| |
| − | I interpreted this to mean that he created a keybinding that automatically performs a clean reinstall of the OS [[Special:Contributions/173.245.54.46|173.245.54.46]]
| |
| | | | |
| | ;FSCK | | ;FSCK |
| Line 62: |
Line 58: |
| | | | |
| | :Yes, that's what fsck refers to here. I've run it many a time on my old Red Hat installation that somehow kept corrupting itself. --[[User:PsyMar|PsyMar]] ([[User talk:PsyMar|talk]]) 16:54, 9 May 2016 (UTC) | | :Yes, that's what fsck refers to here. I've run it many a time on my old Red Hat installation that somehow kept corrupting itself. --[[User:PsyMar|PsyMar]] ([[User talk:PsyMar|talk]]) 16:54, 9 May 2016 (UTC) |
| − |
| |
| − | Can some wonderful person provide an explanation for this? "This is probably a search for an interface to the Unix filesystem checker fsck via third-party software added to Chrome. Repairing a filesystem this way would be inadvisable. [citation needed]" It jokingly says "citation needed", but ironically, some sort of citation (well, explanation) really is needed... it's not obvious at all why it would be inadvisable, or what the joke actually means. [[Special:Contributions/108.162.250.158|108.162.250.158]] 00:21, 11 May 2016 (UTC)
| |
| − |
| |
| − | : I added the line "fsck is a program for checking your filesystem for corruption." based on the discussion immediately above, but an explanation for why a Chrome extension to execute this program is funny/weird would be helpful to people like me. The lines immediately after it (about Chromium etc.) seem unrelated to the joke, and only make it more confusing... if a Unix user could spell it out maybe... [[Special:Contributions/108.162.250.158|108.162.250.158]] 00:28, 11 May 2016 (UTC)
| |
| − |
| |
| − | ::As long as you are not trying to run the fsck on ROOT filesystem (or /home, or anything other currently mounted), it doesn't matter if it's chrome extension. But it's true that usually fsck is run as part of system boot, when no filesystem is mounted in read/write mode, and it is not possible to run Chrome in such situation. -- [[User:Hkmaly|Hkmaly]] ([[User talk:Hkmaly|talk]]) 03:57, 16 May 2016 (UTC)
| |
| − |
| |
| − | : [Extended explanation] Information about files often occur in multiple places on the disk. This redundancy increase the chance of repairing a corrupt file system. Fsck will read data from the disk, and if it finds inconsistencies, write new corrected data back. When a file system is mounted, a file system driver will read and write data of the disk in normal operation. If the two processes are simultaneous and unaware of each other, they may be confused and even create inconsistencies that wasn't there to begin with. E.g. original research: A file system driver may have cached data in working memory. If fsck updates that data on disk, the cache will be out of sync. The file system driver may be confused by this, or, if it writes back the cache to the disk, the fsck fix will be undone, and possibly a new different inconsistency would be created. Or, while fsck is comparing different parts of the file system, it will read one block at one point in time and another block at another point in time. At a time in between, normal operation may have created, changed or removed a file. Fsck then may think it has found an inconsistency (that does not exists) and try to fix it, possibly creating an inconsistency. Therefor, the fsck command will detect if a file system is mounted and issue a really scary warning against proceeding. /David A [[Special:Contributions/141.101.80.33|141.101.80.33]] 21:22, 24 September 2016 (UTC)
| |
| | | | |
| | ;Predictable touchpad | | ;Predictable touchpad |
| Line 101: |
Line 89: |
| | | | |
| | : I think you're assuming that keybinding is about setting up new shortcuts (which the explanation used to seem to be saying); I think the jokes actually about the keyboard being functional at all... [[Special:Contributions/108.162.250.158|108.162.250.158]] 00:08, 11 May 2016 (UTC) | | : I think you're assuming that keybinding is about setting up new shortcuts (which the explanation used to seem to be saying); I think the jokes actually about the keyboard being functional at all... [[Special:Contributions/108.162.250.158|108.162.250.158]] 00:08, 11 May 2016 (UTC) |
| | + | |
| | + | maybe it's just me, but does google actually do this anymore? it certainly used to. now all i get is nothing until i start typing, when i get a list of the most popular results for other people's searches. if you have to turn javascript (or something else) off to see this, maybe it should be mentioned. --[[Special:Contributions/141.101.98.84|141.101.98.84]] 12:36, 10 May 2016 (UTC) |
| | | | |
| | Idea for Turing-complete hardlinks: get an old UNIX that allows hardlinks to directories. With those, you can create loops in the filesystem (it's now an arbitrary directed graph, not a tree). Write an interpreter repeatedly calls link, chdir, mkdir, or rmdir based on some pattern matching on the existing names. It could terminate when it finds itself in an empty directory. Now you write programs on top of that interpreter by carefully setting up a tangle of directories and launching the interpreter at the right starting point. [[Special:Contributions/162.158.60.53|162.158.60.53]] 00:13, 11 May 2016 (UTC) | | Idea for Turing-complete hardlinks: get an old UNIX that allows hardlinks to directories. With those, you can create loops in the filesystem (it's now an arbitrary directed graph, not a tree). Write an interpreter repeatedly calls link, chdir, mkdir, or rmdir based on some pattern matching on the existing names. It could terminate when it finds itself in an empty directory. Now you write programs on top of that interpreter by carefully setting up a tangle of directories and launching the interpreter at the right starting point. [[Special:Contributions/162.158.60.53|162.158.60.53]] 00:13, 11 May 2016 (UTC) |
| − |
| |
| − | ;whoooooosh
| |
| − | maybe it's just me, but does google actually do this any more? it certainly used to. now all i get is nothing until i start typing, when i get a list of the most popular results for other people's searches. if you have to turn javascript (or something else) off to see this, maybe it should be mentioned. --[[Special:Contributions/141.101.98.84|141.101.98.84]] 12:36, 10 May 2016 (UTC)
| |
| − | :still having problems with this. i think i understand the joke, but the comic seems to rely on something which i'm pretty sure doesn't happen. i'm old enough to remember when google would allow the default browser behaviour for textboxes, which is to cache the values you entered in this box and display them to you as a dropdown when you started typing. pressing alt-down would open the list unfiltered and unsorted. this is, i'm guessing, what randall is alluding to. which means that the list is hist search history in google. which makes the text of the joke funny. unfortunately google doesn't do this any more. i've tried it in chrome, firefox, ie and edge and it just doesn't, even if i'm logged in as me. alt-down has no effect. if you start typing it does open a dropdown to autocomplete, but from very scant research this isn't in any way tailored to the user. it just gives you the most popular searches that complete the text you type, with no regard for your search history. i could be wrong about that. if i am, and google does tailor it to your particular search history, then that does make the joke funny again. since not only does randall search for these things enough that google noticed that he likes them (possibly because this is all he searches for) but people search for these ridiculous things enough that google thinks that they are popular. which, even if true is a little remote a possibility. and undermines the joke about randall being special in breaking his computer. maybe i'm overthinking it. or not. did i miss something obvious? this is supposed to explain the comics and i need a little help. --[[Special:Contributions/141.101.98.84|141.101.98.84]] 12:57, 13 May 2016 (UTC)
| |
| − |
| |
| − | I might be wrong, but I think the explanation for "Google docs from bootloader" is missing the point entirely - I believe this is not referring to the application from Google but instead means having the bootloader access Google document files (note that "docs" is lower case here) in order to somehow control or modify the bootloader behavior. These document files might be created and maintained through Google Docs (the application) and then accessed from within the bootloader later. While this may be technically infeasible and extremely unwise for a variety of reasons, if it could be done, it would fit the subject of this comic perfectly - the result would be the potential for severe bootup problems! --[[User:Ianrbibtitlht|Ianrbibtitlht]] ([[User talk:Ianrbibtitlht|talk]]) 17:02, 4 June 2017 (UTC)
| |
| − |
| |
| − | : I see now that the text within the comic is all upper case, but the thought is still valid. --[[User:Ianrbibtitlht|Ianrbibtitlht]] ([[User talk:Ianrbibtitlht|talk]]) 17:08, 4 June 2017 (UTC)
| |
| − |
| |
| − |
| |
| − |
| |
| − | Here is a link to font names "recursive": https://www.recursive.design/ [[Special:Contributions/172.68.154.88|172.68.154.88]] 18:10, 24 October 2019 (UTC)
| |
| − |
| |
| − | The "autoexec" may be used to force others to follow the user. I'm not certain. [[User:Unreliable Connection|2659: Unreliable Connection]] ([[User talk:Unreliable Connection|talk]]) 06:14, 9 April 2023 (UTC)
| |
