Skip to main content

Timeline for Shortest code for infinite disk I/O

Current License: CC BY-SA 3.0

13 events
when toggle format what by license comment
Jun 17, 2020 at 9:04 history edited CommunityBot
Commonmark migration
Apr 4, 2016 at 13:33 comment added Daniel The script only contains these bytes. Since it's bash there's no compiler or anything fancy needed.
Apr 4, 2016 at 4:08 comment added vsz If it only works if put into a script, than the script should also be taken into consideration when calculating the size. Just when I access external resources, it also adds to the code size.
Apr 3, 2016 at 20:50 comment added MathuSum Mut Alright bro, enjoy
Apr 3, 2016 at 20:50 vote accept MathuSum Mut
Apr 11, 2016 at 20:37
Apr 3, 2016 at 20:45 comment added Daniel @MathuSumMut I made an edit. Personally I feel that mine should be counted simply as the bash code itself for the bytecount. Every other entry here must be executed as a script in a file, so how is mine different?
Apr 3, 2016 at 16:34 comment added MathuSum Mut hmm...I think it qualifies as good rule circumventing, although the winner was already announced, but you can still post it if you like. :)
Apr 3, 2016 at 13:29 history edited Daniel CC BY-SA 3.0
added 18 characters in body
Apr 3, 2016 at 13:29 comment added Daniel If that qualifies @HenningMakholm then I'll put it in.
Apr 3, 2016 at 12:17 comment added hmakholm left over Monica Is the first w needed here? For me simply >w creates an empty file w, and doing that in a loop will create infinite I/O because the mtime metadata needs to be updated continually.
Apr 2, 2016 at 8:30 comment added muru I prefer using exec (or . $0). I think this will run out of PIDs.
Apr 2, 2016 at 3:09 comment added Daniel Looks like it's a tie between me and @isaacg - who wins?
Apr 1, 2016 at 20:12 history answered Daniel CC BY-SA 3.0